11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
12 <concept id="GUID-F2D86E40-279A-5B48-B91F-922803FEF5DE" xml:lang="en"><title>SMS |
12 <concept id="GUID-F2D86E40-279A-5B48-B91F-922803FEF5DE" xml:lang="en"><title>SMS |
13 MTM Overview</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
13 MTM Overview</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
14 <p>SMS MTM provides APIs for sending SMS text messages. This section provides |
14 <p>SMS MTM provides APIs for sending SMS text messages. This section provides |
15 an overview of the SMS MTM component. </p> |
15 an overview of the SMS MTM component. </p> |
16 <section><title>Description</title> <p>The Messaging Application module provides |
16 <section id="GUID-6C25C670-C4BF-4BFA-8D3C-D46618AEB5C4"><title>Description</title> <p>The Messaging Application module provides |
17 a SMS MTM for handling SMS messages in the Message Store. For further SMS |
17 a SMS MTM for handling SMS messages in the Message Store. For further SMS |
18 support available the Symbian platform, see <xref href="GUID-34E7AAF2-EC62-5BF6-B9E7-C7D346BCDF93.dita">Cellular |
18 support available on the Symbian platform, see <xref href="GUID-34E7AAF2-EC62-5BF6-B9E7-C7D346BCDF93.dita">Cellular |
19 Baseband Services Guide</xref> documentation. </p> <p><b>Supported functionality</b> </p> <p>SMS |
19 Baseband Services Guide</xref> documentation. </p> <p><b>Supported functionality</b> </p> <p>SMS |
20 MTM provides functionality to create, store and retrieve an SMS message entry |
20 MTM provides functionality to create, store and retrieve an SMS message entry |
21 in the Message Store, send an SMS, reply to a received SMS and forward existing |
21 in the Message Store, send an SMS, reply to a received SMS and forward existing |
22 SMS. A reply to a received SMS may include the original message text, including |
22 SMS. A reply to a received SMS may include the original message text, including |
23 any EMS components. </p> <p>SMS that are received by SMS MTM are stored in |
23 any EMS components. </p> <p>SMS that are received by SMS MTM are stored in |
46 sent, one message is sent for each recipient. </p> <p><b>BIO messages</b> </p> <p>SMS |
46 sent, one message is sent for each recipient. </p> <p><b>BIO messages</b> </p> <p>SMS |
47 MTM is aware of BIO messages and uses the BIO Framework to tag SMS with the |
47 MTM is aware of BIO messages and uses the BIO Framework to tag SMS with the |
48 appropriate BIO type. This includes support for WAP messages. </p> <p><b>Unsupported |
48 appropriate BIO type. This includes support for WAP messages. </p> <p><b>Unsupported |
49 functionality</b> </p> <p>SMS MTM does not support sending and receiving OTA |
49 functionality</b> </p> <p>SMS MTM does not support sending and receiving OTA |
50 (Over The Air) SMS messages. </p> </section> |
50 (Over The Air) SMS messages. </p> </section> |
51 <section><title>Architecture</title> <p>The Messaging Middleware architecture |
51 <section id="GUID-9776B05D-D289-46C0-83C0-BD30E82A65EC"><title>Architecture</title> <p>The Messaging Middleware architecture |
52 defines a framework in which modules (MTMs) can be implemented that provide |
52 defines a framework in which modules (MTMs) can be implemented that provide |
53 support for particular messaging protocols. A client MTM provides the API |
53 support for particular messaging protocols. A client MTM provides the API |
54 for application engines to use the protocol. SMS MTM API provides the client |
54 for application engines to use the protocol. SMS MTM API provides the client |
55 MTM API, server MTM API, and supporting classes for SMS. </p> <p>SMS MTM integrates |
55 MTM API, server MTM API, and supporting classes for SMS. </p> <p>SMS MTM integrates |
56 SMS into the Messaging architecture, so that SMS can be used by a messaging |
56 SMS into the Messaging architecture, so that SMS can be used by a messaging |
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 that Symbian has implemented in |
60 following figure shows the SMS architecture:</p> <fig id="GUID-F904EC3A-7292-5A57-BC4E-1C736D24223C"> |
61 the Symbian platform. </p> <fig id="GUID-F904EC3A-7292-5A57-BC4E-1C736D24223C"> |
|
62 <title> SMS MTM architecture </title> |
61 <title> SMS MTM architecture </title> |
63 <image href="GUID-97545AEB-0518-5937-AEB6-C97443B449D3_d0e457590_href.jpg" placement="inline"/> |
62 <image href="GUID-97545AEB-0518-5937-AEB6-C97443B449D3_d0e478472_href.jpg" placement="inline"/> |
64 </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 |
65 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 |
66 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 |
67 MTM</xref>. In addition, it provides the following functionality: </p> <ul> |
66 MTM</xref>. In addition, it provides the following functionality: </p> <ul> |
68 <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 |
80 SIM parameters. </p> </li> |
79 SIM parameters. </p> </li> |
81 </ul><note> MS receiving is normally done automatically by the Cellular Baseband |
80 </ul><note> MS receiving is normally done automatically by the Cellular Baseband |
82 and messaging components, with received SMS messages placed in the Inbox. |
81 and messaging components, with received SMS messages placed in the Inbox. |
83 Generic message receiving operations are not supported by the MTM. Also, UI |
82 Generic message receiving operations are not supported by the MTM. Also, UI |
84 functionality, such as SMS message viewing and editing, is not provided by |
83 functionality, such as SMS message viewing and editing, is not provided by |
85 Symbian platform.</note> <p>The SMS Client MTM class is <xref href="GUID-C499ABDB-BA30-3D97-A850-D5790FE49634.dita"><apiname>CSmsClientMtm</apiname></xref>. </p> <p id="GUID-752B2A3B-CC1D-50CB-B3BF-113BED635538"><b>SMS Server MTM</b> </p> <p>SMS |
84 the Symbian platform.</note> <p>The SMS Client MTM class is <xref href="GUID-C499ABDB-BA30-3D97-A850-D5790FE49634.dita"><apiname>CSmsClientMtm</apiname></xref>. </p> <p id="GUID-752B2A3B-CC1D-50CB-B3BF-113BED635538"><b>SMS Server MTM</b> </p> <p>SMS |
86 Server MTM implements the <xref href="GUID-963C0F50-A44A-518E-8DB0-42BEBEFD10A2.dita">Server-side |
85 Server MTM implements the <xref href="GUID-963C0F50-A44A-518E-8DB0-42BEBEFD10A2.dita">Server-side |
87 MTM</xref> interface, and primarily provides functionality to handle requests |
86 MTM</xref> interface, and primarily provides functionality to handle requests |
88 from the client MTM to send SMS messages. Incoming SMS messages are handled |
87 from the client MTM to send SMS messages. Incoming SMS messages are handled |
89 by a group of components called SMS watchers. </p> <p>These components provide |
88 by a group of components called SMS watchers. </p> <p>These components provide |
90 a layer over the SMS support provided in the Narrow Band Protocols Stack subsystem. |
89 a layer over the SMS support provided in the Narrow Band Protocols Stack subsystem. |
160 of service settings is provided by <xref href="GUID-A9FE5C23-4F39-345E-873B-682D9807BAA0.dita"><apiname>CSmsSettings</apiname></xref>. </p> <p><b>Progress |
159 of service settings is provided by <xref href="GUID-A9FE5C23-4F39-345E-873B-682D9807BAA0.dita"><apiname>CSmsSettings</apiname></xref>. </p> <p><b>Progress |
161 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 |
162 operations. For SMS operations, progress information includes such things |
161 operations. For SMS operations, progress information includes such things |
163 as type of operation, and number of messages processed. Progress information |
162 as type of operation, and number of messages processed. Progress information |
164 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> |
165 <section><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"> |
166 <image href="GUID-938C0EB5-D0B3-502E-87A9-7C626642AE4B_d0e457862_href.jpg" placement="inline"/> |
165 <image href="GUID-938C0EB5-D0B3-502E-87A9-7C626642AE4B_d0e478746_href.jpg" placement="inline"/> |
167 </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"> |
168 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
167 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
169 <tbody> |
168 <tbody> |
170 <row> |
169 <row> |
171 <entry><p> <b>Class</b> </p> </entry> |
170 <entry><p> <b>Class</b> </p> </entry> |
225 </link> |
224 </link> |
226 <link href="GUID-8B843382-D27A-5E36-8F60-304903F3AA41.dita"><linktext>Message Type |
225 <link href="GUID-8B843382-D27A-5E36-8F60-304903F3AA41.dita"><linktext>Message Type |
227 Module</linktext></link> |
226 Module</linktext></link> |
228 <link href="GUID-E56E21A9-B545-5217-A877-E64D30275157.dita"><linktext>Using the |
227 <link href="GUID-E56E21A9-B545-5217-A877-E64D30275157.dita"><linktext>Using the |
229 Policy Evaluator Plug-in</linktext></link> |
228 Policy Evaluator Plug-in</linktext></link> |
230 <link href="GUID-A2408186-1927-45F4-8972-C9273E5135CF.dita"><linktext>SMS |
229 <link href="GUID-A2408186-1927-45F4-8972-C9273E5135CF.dita"><linktext>SMS |
231 Tutorial</linktext></link> |
230 Tutorial</linktext></link> |
232 </related-links></concept> |
231 </related-links></concept> |