1 Generic SMS Gateway for AtLink Enterprise Voice Integration Instructor: Dr. Kwok-Bun Yue, Ph.D Mentor: Mr. Dilhar De Silva Team #6: Dang Nguyen Huy Do Tan Nguyen Thang Nguyen

2 Table of contents  Overview of project  Project requirements  Project design specification  SMS gateway providers  Project plan  References  Questions and Answers

3 Overview of project  This project is sponsored by AtLink company.  Build a HTTP and a SMPP SMS client.  Integrate with a hosted SMS gateway  Capability to bind with any open SMS gateway by customizing required parameters

4 Project requirements Build a web based SMS application that satisfy the following requirements: Support HTTP and SMPP protocols Support Two-Way SMS capabilities. Coverage US and EU Change the binding to any gateway dynamically by changing binding parameters Should integrate with EVI Communication profiles

5 Project requirements Development tool requirements for project as follows: AJAX and HTML for User Interface. JAVA as a development language and Eclipse as a dev environment. MySQL as database server. An open source UML tool (TBD) for analysis & design specifications.

6 Project design specification  Introduction to SMS Messaging  Basic concepts of SMS Technology  SMS gateway protocols  How to send/receive SMS  Project architecture

7 Introduction to SMS Messaging  SMS stands for Short Message Service  Enables the sending and receiving of messages between mobile phones  One SMS message can contain at most 140 bytes 160 characters (7-bit character) 70 characters (16-bit Unicode)  SMS messages can also carry ringtones, pictures, operator logos, wallpapers, animations

8 Applications of SMS  Person-to-Person Text Messaging  Provision of Information  Downloading  Alerts and Notifications , Fax and Voice Message Notifications E-commerce and Credit Card Transaction Alerts Stock Market Alerts Remote System Monitoring  Two-way Interactive Text Messaging Applications  SMS Marketing

9 Basic concepts of SMS Technology  SMS Center: responsible for handling the SMS operations of a wireless network  Intra-operator SMS Messages: involves only one SMS center

10 Basic concepts of SMS Technology  Inter-operator SMS message involves one or more SMS centers

11 Basic concepts of SMS Technology  SMS Gateway: acts as a relay between the two SMSCs. It is needed when two SMSCs does not support a common protocol  An SMS message may need to pass through more than one network entity (e.g. SMSC and SMS gateway) before reaching the destination

12 Basic concepts of SMS Technology  SMS Gateway

13 SMS gateway protocols  HTTP/S API: used in the form of an HTTP/Internet Post  SMTP [ to SMS]: allows messages that are sent via to be converted to SMS.  SMPP: suitable for customers who send large volumes of traffic  XML: XML over HTTP  FTP: Suitable for high volume messaging  COM Object API: Popular with windows-based developer, integrate SMS sending into their programs or ASP pages

14 How to send SMS

15 How to receive SMS

16 Project architecture

17 Project architecture  Web Browser: Running on client-side, it allows users log in and send SMS messages.  EVI (Enterprise Voice Integration) profile: contain the information of customers  SMS Gateway: an SMS gateway can be set up to handle the connections to the SMSCs  SMS Center: A SMS center (SMSC) is responsible for handling the SMS operations of a wireless network  Web Application: Running in the server-side, it handles requests from SMS users for sending and receiving SMS message

18 Use cases

19 SMS gateway providers  Criteria Criteria Cost for sending SMS messages Network coverage Protocols or interfaces supported API documents Number of free SMS messages or credits 2-way SMS messaging Support service

20 SMS gateway providers  SMS Gateway Provider Research SMS Gateway Provider Research  Chosen SMS Gateway Provider Clickatell ( SMS2 ( MXTelecom (

21 Project plan  Detail of the project plan Detail of the project plan

22 References    

23 Thank you