- June 26, 2012
- Posted by: InApp
- Category: Testing
There are different types of messages that can be sent using a messaging platform.
Some of these are:
- Text Message
- Multimedia Message
- WAP Message
- Service Messages
Here we can take a deep look into the text messages. There are basically 3 types of text messages:
- UTF -16 Encoded (16-bit Unicode Transformation Format)
- UTF-8 Encoded(8-bit Unicode Transformation Format)
UTF – 16
Normal English characters come under this category and special characters like semicolon, full stop, etc… are supported. Messages will be of length 160 characters and if it goes beyond the 160 character limit it will split into 2 at 154th character and then gets concatenated at the mobile device. These are class 1.
UTF – 8
The purpose of this encoding is to support the international characters; the languages like French, Spanish, Arabic, Hindi, and Malayalam etc… are supported. For UTF-8 encoded messages the length will be 60 characters. Concatenation and slicing take place if the character count goes beyond that limit.
These are normal messages of length is 160 characters if English and 60 characters if in other languages like French, Spanish etc… only difference is that this messages will not get saved to the phone memory. The class is set to 0 for generating flash messages.
The fig: displays the transaction process that take place between the SMPP and SMSC. SMPP sends a bind request to the SMSC and SMSC will respond to the request. If the bind was successful SMPP sends a Submit SM to the SMSC and will receive a successful response if the submits was good. Then the SMSC identifies the originator, destination, sender, text message etc and forward to the destination address. On receiving a successful delivery from mobile device SMSC will forward the same to SMPP and SMPP will send a response. After the delivery response has been send to the SMSC, SMPP sends an unbind request to SMSC on successful reception of the unbind request the SMSC will unbind by sending an unbind response.
The above diagram explains the general internal architecture of a messaging application and its routing system.
The system consist of:
- Messaging application at user end for pushing bulk messages
- Input queue, operator queues, response queues etc…
- Data Base to store the messages, response and delivery details
- Operator to which messages are pushed
- Finally mobile device to which the messages are delivered
The messaging application at the end user side pushes bulk messages into the input queues. From the input queues the messages will get parallel push to database and routing application. The routing application will be responsible for identifying the exact route for each message. Once the route is identified that gets updated in the database. As per the route identified, message falls into the operator queue. From operator queue messages are pushed to operators and when operator receives a successful message it will push response to the response queue. After pushing the response the operators will send message to mobile device. The mobile devices will respond with the reception of message to operators and the operator will push this delivery response to the delivery response queue and all the status will get updated in the database.