InApp / Blog /

Basics Of Messaging Platform

June 26, 2012

6:44 am

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)
  • Flash

UTF – 16

Normal English characters come under this category and special characters like semicolons, full stop, etc… are supported. Messages will be of the length of 160 characters and if it goes beyond the 160 character limit it will split into 2 at the 154th character and then get 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, 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.

Flash Message

These are normal messages of the length of 160 characters in English and 60 characters in other languages like French, Spanish, etc… only difference is that these messages will not get saved to the phone memory. The class is set to 0 for generating flash messages.

Flash_Message

The figure displays the transaction process that takes 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 were good. Then the SMSC identifies the originator, destination, sender, text message, etc, and forwards it to the destination address. On receiving a successful delivery from a mobile device SMSC will forward the same to SMPP and SMPP will send a response. After the delivery response has been sent 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.

Architecture_messaging_system

The above diagram explains the general internal architecture of a messaging application and its routing system.

The system consists of:

  • Messaging application at user end for pushing bulk messages
  • Input queue, operator queues, response queues, etc…
  • Data Base to store the messages, responses, and delivery details
  • Operator to which messages are pushed
  • Finally, the 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 a parallel push to the 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, the message falls into the operator queue. From the operator, queue messages are pushed to operators and when the operator receives a successful message it will push a response to the response queue. After pushing the response the operators will send a message to the mobile device. The mobile devices will respond with the reception of messages to operators and the operator will push this delivery response to the delivery response queue and all the statuses will get updated in the database.

Have questions? Contact the technology experts at InApp to learn more.

Insights & News