Enabling Cloud-Based Mobile Services
The Dialogic® DSI Signaling Web Server (DSI SWS) enables the rapid development of cloud-ready applications using key technologies in the mobile network such as Short Message Service (SMS), Location Based Services (LBS) and Unstructured Supplementary Service Data (USSD). Access to service-specific functionality is offered through a focused RESTful Web Services API using XML payloads for easy integration and a wide choice of programming environments.
DSI SWS can enable a broad range of web-based services, including handset provisioning, subscriber alerts, emergency response, mobile advertising, and mobile payments.
Network Architecture for Cloud Services
Systems with DSI SWS can operate as network interface servers for web-based application server clients. DSI SWS can enable both web services and traditional services because it includes both web server software for HTTP transport and TCP/IP protocol software for connection to application servers.
HTTP and XML open standard conventions enable the use of DSI SWS with service creation environments such as Oracle WebLogic, IBM WebSphere, JBoss, GlassFish, and others.
The illustration “Network Architecture Using DSI SWS” shows DSI SWS in a sample network. Connections are established and requests are initiated to appropriate network elements in support of messaging and location-based services as needed. The application program is not required to manage these lower-level communication layers.

Network Architecture Using DSI SWS
DSI SWS implements a type of Representational State Transfer (REST) architecture for interaction with client applications. All application functions are initiated from the client for both outgoing and incoming messages. For example, a client can directly send messages (PUT) or can initiate a request with a wait for a later response or timeout (GET). This design offers the following benefits:
- The number of active clients can vary
- Load sharing is simple and efficient because clients request their own loads as needed
- Client application flow is simplified because clients do not need to implement a dispatching mechanism