diff -r 43e37759235e -r 51a74ef9ed63 Symbian3/SDK/Source/GUID-CBFDD753-BAE3-5C40-B947-EB8CDA11CD23.dita --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Symbian3/SDK/Source/GUID-CBFDD753-BAE3-5C40-B947-EB8CDA11CD23.dita Wed Mar 31 11:11:55 2010 +0100 @@ -0,0 +1,12 @@ + + + + + +Types of SMS Message

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.

Data flow

For an incoming message, the usual route is:

  1. The phone receives the SMS. The telephony server notifies the SMS stack.

  2. 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.

  3. 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.

For an outgoing message, the route is:

  1. A messaging application uses the SMS client MTM APIs to create a message, to set its contents and fields, and to send it

  2. The message server passes the send command to the SMS server MTM. This calls the appropriate SMS stack to send the message.

  3. The stack calls the telephony server to send the message.

SMS MTM Overview Message Type Module \ No newline at end of file