|
|
|
|
|
Wireless Data Server 2.1 | Administrator's Guide |
| View in pdf format |
| Go to User's Guide |
Architecture
This chapter offers a general description of Wireless Data Server's architecture, including its interactions with the calendar server and three possible setups for connecting to the wireless network.
- Overview
- Connecting to the calendar server
- Data Circuit-terminating Equipment (DCE)
- Short Message Peer to Peer (SMPP)
- Universal Computer Protocol (UCP)
Overview
Wireless Data Server is an intermediary between the calendar server and the mobile network. It translates and transmits data bi-directionally, "pulling" desired information from the calendar database, and "pushing" configurable reminders and notifications to the phone. It consists of three components: the server core, the smsnotify utility, and any one of a variety of plug-ins for connecting to the Short Message Service Center (SMSC). The functions of these components are described in more detail below.
Connecting to the calendar server
This section describes the two kinds of interactions between Wireless Data Server and calendar server: those that occur when a message originating from the mobile phone is sent through Wireless Data Server to the calendar server, and those that occur when a reminder or notification is sent from the calendar server through Wireless Data Server to the mobile phone.
Mobile-originated messages
When you start Wireless Data Server, it establishes a persistent connection to each node of each calendar server specified in wds.ini (see the [<UNISON>] section). It logs in as SYSOP for all nodes, using the encrypted passwords you set in wds.ini (consult the readme file for details on this procedure).
When Wireless Data Server receives a short message from the wireless network, it interprets the message and translates it into a syntax understood by the calendar server. Wireless Data Server then passes the request on to the calendar server, identifying the sender by the MSISDN of his or her phone. The calendar server handles its requests in exactly the same way as it handles any other client connection. For more information, please see your calendar server's Administrator's Guide.
NOTE:Because users are identified by their phone's MSISDN when making requests through Wireless Data Server, each user must have a unique MSISDN.
Mobile-terminated messages
When the calendar server sends a reminder or notification to a wireless handset, it follows a process similar to that for e-mail notifications, calling an external application for delivery of the calendar information. For wireless reminders and notification, the calendar server calls the smsnotify utility from the /users/unison/bin directory. This program passes the calendar information via SMTP to Wireless Data Server. Wireless Data Server then reformats the information and sends it by SMS over the wireless network to the mobile phone.
The model of Wireless Data Server's connection to the calendar server can be summarized as follows:
Figure 1.1 · WDS / calendar server interactions
![]()
Connecting to the wireless network
Data Circuit-terminating Equipment (DCE)
Wireless Data Server can connect to the wireless network through a modem, using the Data Circuit-terminating Equipment (DCE) plug-in. This plug-in is provided along with the Wireless Data Server core. The modem and Short Message Service Center (SMSC) communicate over the wireless network.
Figure 1.2 · DCE installation
![]()
Short Message Peer to Peer (SMPP)
In this implementation, Wireless Data Server connects directly to the SMSC using the Short Message Peer to Peer (SMPP) protocol, through its SMPP plug-in.
Figure 1.3 · SMPP installation
![]()
Universal Computer Protocol (UCP)
In this implementation, Wireless Data Server connects directly to the SMSC using the Universal Computer Protocol (UCP), through its UCP plug-in.
Figure 1.4 · UCP installation
![]()
| Steltor http://www.steltor.com Voice: (514) 733-8500 Fax: (514) 733-8878 info@steltor.com |
|
|
|
|
|
| Copyright information | |||