57 client program in a similar way to other message types such as email. SMS |
57 client program in a similar way to other message types such as email. SMS |
58 MTM uses the SMS interface provided by the Telephony sub-system. This provides |
58 MTM uses the SMS interface provided by the Telephony sub-system. This provides |
59 support for 7, 8, and 16-bit text messages, and message concatenation. </p> <p>The |
59 support for 7, 8, and 16-bit text messages, and message concatenation. </p> <p>The |
60 following figure shows the SMS architecture:</p> <fig id="GUID-F904EC3A-7292-5A57-BC4E-1C736D24223C"> |
60 following figure shows the SMS architecture:</p> <fig id="GUID-F904EC3A-7292-5A57-BC4E-1C736D24223C"> |
61 <title> SMS MTM architecture </title> |
61 <title> SMS MTM architecture </title> |
62 <image href="GUID-97545AEB-0518-5937-AEB6-C97443B449D3_d0e273960_href.jpg" placement="inline"/> |
62 <image href="GUID-97545AEB-0518-5937-AEB6-C97443B449D3_d0e270252_href.jpg" placement="inline"/> |
63 </fig> <p><b>SMS Client MTM</b> </p> <p>The SMS Client MTM implements the |
63 </fig> <p><b>SMS Client MTM</b> </p> <p>The SMS Client MTM implements the |
64 standard set of <xref href="GUID-E180D222-CC4F-5007-93FC-C339BBE708BC.dita#GUID-E180D222-CC4F-5007-93FC-C339BBE708BC/GUID-BCFBE2C5-2C90-5E43-9B21-0D80A469CEAB">Client |
64 standard set of <xref href="GUID-E180D222-CC4F-5007-93FC-C339BBE708BC.dita#GUID-E180D222-CC4F-5007-93FC-C339BBE708BC/GUID-BCFBE2C5-2C90-5E43-9B21-0D80A469CEAB">Client |
65 MTM APIs</xref> described in <xref href="GUID-E180D222-CC4F-5007-93FC-C339BBE708BC.dita">Client |
65 MTM APIs</xref> described in <xref href="GUID-E180D222-CC4F-5007-93FC-C339BBE708BC.dita">Client |
66 MTM</xref>. In addition, it provides the following functionality: </p> <ul> |
66 MTM</xref>. In addition, it provides the following functionality: </p> <ul> |
67 <li id="GUID-8044B9F8-BF51-577B-B99A-7E7598172DD7"><p>Access to the <xref href="GUID-790D9BA9-2FB7-3073-AF2F-FFD049C3FD3D.dita"><apiname>CSmsHeader</apiname></xref> object |
67 <li id="GUID-8044B9F8-BF51-577B-B99A-7E7598172DD7"><p>Access to the <xref href="GUID-790D9BA9-2FB7-3073-AF2F-FFD049C3FD3D.dita"><apiname>CSmsHeader</apiname></xref> object |
160 information</b> </p> <p>The progress information can be obtained for messaging |
160 information</b> </p> <p>The progress information can be obtained for messaging |
161 operations. For SMS operations, progress information includes such things |
161 operations. For SMS operations, progress information includes such things |
162 as type of operation, and number of messages processed. Progress information |
162 as type of operation, and number of messages processed. Progress information |
163 is provided by <xref href="GUID-25FA6A20-1122-3B06-B8AF-59D3FDBDDC76.dita"><apiname>TSmsProgress</apiname></xref>. </p> </section> |
163 is provided by <xref href="GUID-25FA6A20-1122-3B06-B8AF-59D3FDBDDC76.dita"><apiname>TSmsProgress</apiname></xref>. </p> </section> |
164 <section id="GUID-80A5C81E-42C9-4432-A97D-872525E5D468"><title>APIs</title> <fig id="GUID-EABD829F-612D-53DF-BFDF-1F4E27FD4FD8"> |
164 <section id="GUID-80A5C81E-42C9-4432-A97D-872525E5D468"><title>APIs</title> <fig id="GUID-EABD829F-612D-53DF-BFDF-1F4E27FD4FD8"> |
165 <image href="GUID-938C0EB5-D0B3-502E-87A9-7C626642AE4B_d0e274234_href.jpg" placement="inline"/> |
165 <image href="GUID-938C0EB5-D0B3-502E-87A9-7C626642AE4B_d0e270526_href.jpg" placement="inline"/> |
166 </fig> <p>The following are the important classes for SMS Client MTM: </p> <table id="GUID-8C815D5D-0494-5507-8A7D-275641BFF71D"> |
166 </fig> <p>The following are the important classes for SMS Client MTM: </p> <table id="GUID-8C815D5D-0494-5507-8A7D-275641BFF71D"> |
167 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
167 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
168 <tbody> |
168 <tbody> |
169 <row> |
169 <row> |
170 <entry><p> <b>Class</b> </p> </entry> |
170 <entry><p> <b>Class</b> </p> </entry> |