Sms gateway ppt 9 oct

3,656 views

Published on

1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total views
3,656
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
275
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

Sms gateway ppt 9 oct

  1. 1. SMS GatewayDate : 09-10-2012
  2. 2. Agenda Overview Basic Flow Of SMS Different Flows Of SMS Architecture and Interfaces Of SMS Gateway Core Gateway Components Push Server Components External Systems External InterfacesConfidential Slide 2
  3. 3. Overview SMS Gateway is the interface for sending/receiving the SMS and value added services. It receives the requests from the SMSC- [PULL Requests] and it searches the configured URL form the configuration and hits the URL[HTTP-Hits]. Later it fetches the content and sends it in the configured way back to the SMSC. [Pull Response]. It also supports the pushing of bulk messages to the mobile users. [PUSHMessages]. It is an applications that serves the Internet content to the mobile subscriber using SMS messaging.Confidential Slide 3
  4. 4. Basic Flow Of SMS SMS stands for Short Message Service . Using standardized communication protocols the short text messages are exchanged .Confidential Slide 4
  5. 5. Different Flows of SMS1. Handset –Handset SMS flow :  For Same Operator : SMSC SMS Receiver client SMS originator client  For Different Operator : GMSC SMSC SMS SMS Receiver originator client clientConfidential Slide
  6. 6. 2. Handset-Application SMS flow : SMSC SMS Gateway SMS originator client Application SMSC SMS Gateway SMS Receiver client 3. Application-Handset SMS flow : ESME(SMS Push Gateway+ SMSC Initiator Push Server)Confidential Slide
  7. 7. Architecture & InterfacesConfidential Slide
  8. 8. Core Gateway ArchitectureConfidential Slide
  9. 9. Core Gateway Components SMSC Manager : This interface supports both SMPP and CIMD protocol. Responsible for send /receive operations and communication with SMSC. Queue Manager : Request and response of the server are queued differently and handled with the help of queuing mechanism. It is responsible for storing requests/responses and passing the same to different modules. HTTP Manager : Responsible for performing the HTTP – hit operation to fetch the content from the Internet. Handles all HTTP error codes & take appropriate action.Confidential Slide
  10. 10. Contd.. Callback Manager : Responsible for intimating the applications/agents which submit messages to the users. PUSH Receive Manager : Accepts input from different Jataayu push servers. Communication between this module and push server is proprietary. Responsible for any Mobile Terminated push message submission through the Gateway. Gateway Information Manager : Gives information about the SMSC channels to the Push Servers based on the trigger of the eventConfidential Slide
  11. 11. Push Server Components Core component for Push operation. Takes input from external push applications using Push Initiator interface and submits the message to the Gateway. It has two sub modules : Push Initiator Manager : It is responsible for all interaction with the push client. It establishes PI API interface with the external agents. Gateway Manager : Responsible for all its communication with core gateway. It collects SMSC/Channel information from the core gateway and also informs the same to PI Manager, which in turn updates the external applications.Confidential Slide
  12. 12. External Systems SMSC : Store and forward the SMS and deliver the SMS on available of the destination subscriber. Internet Applications/Content Providers : Content for VAS is fetched from Content Providers through HTTP Interface. Callback Applications : Status of the message submission is provided to external callback application through the HTTP interface. CDR Processor : CDR generated by billing engine can not be delivered as it is to operators billing engine hence external component CDR Processor CDR interacts with billing engine on one end and CDRs of core gateway on the other.Confidential Slide
  13. 13. Contd.. Push Applications : Applications can use the API interface provided for pushing the messages. Web Administration : Various Operation and administration like start/stop, edit/update configurations, viewing statistics and product information is available through Web/HTTP Interface.Confidential Slide
  14. 14. External Interfaces SMPP/CIMD are SMS Protocol used for SMSC interfaces. HTTP Interface is used for fetching the content and providing the callback interface. CDR interface used for billing by CDR processor on one end. PI (Push Initiator API) interface is used by external applications to communicate with Push Server.Confidential Slide
  15. 15. Confidential Slide
  16. 16. Confidential Slide
  17. 17. Confidential Slide
  18. 18. Confidential Slide
  19. 19. Confidential Slide
  20. 20. Overview Of SMPP 3.4 Open message-transfer protocol It defines- A set of operations for the exchange of short messages between an ESME and an SMSC. The data that an ESME application must exchange with an SMSC during SMPP operations.Confidential Slide 20
  21. 21. SMPP Session Sequence - ESME TransceiverConfidential Slide 21
  22. 22. Thank youDate: 09-10-2012

×