Messaging services application service
When used by the messaging services, an application service provides direct connection-based access to backend server applications.
An application service defines the protocol that is used between the application server and the messaging services. It identifies a port that is reserved for communication between an application on messaging client devices and the messaging services. The application provides a specific set of header information inside the data stream that the messaging services uses to map the traffic to the backend application server.
Provides traffic flow for applications between backend application servers and messaging client devices. Between the backend application server and the messaging services the traffic flows over UDP, TCP, or TCP by using SSL. Between the messaging client devices and the messaging services, the traffic flows over all MNCs except dial-based MNCs.
For example, a POP3 email client on a messaging device connects to the messaging services through an SMS protocol. The messaging services convert the data stream to the UDP or TCP protocol and forward the requests directly to the POP3 server. When responses are returned from the POP3 server, they are converted back to the SMS protocol and returned to the email client on the messaging device.
A generic application service can be configured to add client device identification information as a header to the application data stream. The application that receives the data stream is responsible for interpreting the header.
This service can also be configured to perform secure TCP transactions.
- Provides traffic flow for applications between backend application servers and messaging client devices, but does not convert the protocol of the data stream. The messaging services keeps accounting records, which it can forward to another server. Pass-through application services are supported on Mobitex and DataTAC-based MNCs only.