<concept xml:lang="en" id="GUID-CBFDD753-BAE3-5C40-B947-EB8CDA11CD23"><title>Types of SMS Message</title><prolog><metadata><keywords/></metadata></prolog><conbody><p>There are four classes of an SMS message. Classes identify the importance of an SMS message and also the location where it must be stored. </p> <ul><li id="GUID-52AD5825-5097-52DD-AFD1-F1FA70EDC589"><p> <b>Class 0</b>  </p> <p>This type of SMS message is displayed on the mobile screen without being saved in the message store or on the SIM card; unless explicitly saved by the mobile user. </p> </li> <li id="GUID-85C0FEFC-3FFE-5700-AA29-373B710935B4"><p> <b>Class 1 </b>  </p> <p>This message is to be stored in the device memory or the SIM card (depending on memory availability). </p> </li> <li id="GUID-9F06A050-74F1-589F-85FC-DE5A42F06DC4"><p> <b>Class 2 </b>  </p> <p>This message class carries SIM card data. The SIM card data must be successfully transferred prior to sending acknowledgment to the service center. An error message is sent to the service center if this transmission is not possible. </p> </li> <li id="GUID-88CEBE65-1E86-5EB2-989A-C22BD2FBC559"><p> <b>Class 3</b>  </p> <p>This message is forwarded from the receiving entity to an external device. The delivery acknowledgment is sent to the service center regardless of whether or not the message was forwarded to the external device. </p> </li> </ul> <section><title>Data flow</title> <p>For an incoming message, the usual route is: </p> <ol id="GUID-22CDEC56-7FB9-510F-B2B2-E2D5A2E20B26"><li id="GUID-DD67BB7A-7180-50D8-8C19-0E2C67831F4A"><p>The phone receives the SMS. The telephony server notifies the SMS stack. </p> </li> <li id="GUID-AE55B6AB-A09D-5CB1-898F-65B6302AA1B8"><p>The SMS stack decodes the message and then notifies the SMS watcher that handles messages of the relevant service center. The watcher creates a new messaging entry in the message store's Inbox. </p> </li> <li id="GUID-499754BF-F736-5950-B6DB-CF1D5EA669DD"><p>Any messaging application that is set as an observer of the message store is notified of the arrival of the new message. The application can then determine whether it should handle the message, and if so, can then read the message and process it appropriately. </p> </li> </ol> <p>For an outgoing message, the route is: </p> <ol id="GUID-11E29E28-5F06-5F85-BD3E-5C299B68A04E"><li id="GUID-0AE8A70D-8DF7-5AD0-A42D-280ECCCBF7CF"><p>A messaging application uses the SMS client MTM APIs to create a message, to set its contents and fields, and to send it </p> </li> <li id="GUID-E451B4D9-9C2E-59E7-BE53-CDAA5FBBD625"><p>The message server passes the send command to the SMS server MTM. This calls the appropriate SMS stack to send the message. </p> </li> <li id="GUID-1E90BB8D-2727-58E4-ACE5-23494B9B25D4"><p>The stack calls the telephony server to send the message. </p> </li> </ol> </section> </conbody><related-links><link href="GUID-F2D86E40-279A-5B48-B91F-922803FEF5DE.dita"><linktext>SMS MTM Overview</linktext> </link> <link href="GUID-8B843382-D27A-5E36-8F60-304903F3AA41.dita"><linktext>Message Type Module</linktext> </link> </related-links></concept>