SMS Gateway/Use case

From n0r1sk software solutions
Revision as of 11:46, 11 August 2010 by Mario (talk | contribs)
Jump to: navigation, search

Description of the components

Overview

SMSGateway UseCase.png

Third Party Application

This behavior will be changed in the future.

In the first version of the SMS Gateway the third party application is the controlling instance that will use the SMS Gateway as webservice. The third party application has to take care about the mobile number range because it has to choose which gateway to use in an multiple SMS Gateway setup.

The communication protocol between the third party application and the SMS Gateway software is a http request that could be secured by using an Apache http deamon as SSL terminator.

SMS Gateway

The SMS Gateway itself is implemented as pure JAVA web application driven by the Apache Tomcat servlet engine.

At this point of the implementation the SMS Gateway does filter the incoming text messages like with “instring” or something similar. Also the SMS Gateways does not check if the mobile number is “correct” or if this SMS Gateway is the right SMS Gateway for sending the current text message (number circle).

The SMS Gateway communicates with the connected mobile phones through telnet and it takes care about that always one text message is computed at one time. The telnet connection could be made over Ethernet or to direct attached devices (serial port or USB).

The SMS Gateway operates parallel on the text message queue (the database) so it scales up with the connected modem devices.

The SMS Gateway will also delegate the text message queue to another configured SMS Gateway in case of all configured local modems gets unresponsively. In this case the incoming connection will be shut down or as an answer of the request of the third party software the SMS Gateway will send ERROR.

It lies in the scope of the third party software to react and to send the next messages to the remaining SMS Gateway.

Modem Device

List of supported devices: