Delivery to Mobile Phones

Delivery of the full range of MSP 2.0 supported services to a mobile phone using uncompressed XML with possible variations in the underlying schema is not practical with today's devices. There is often only a few kilobytes (KB) of RAM available and some form of compression is almost certain to be required. In addition, many of today's technologies do not directly support IP and delivery across the wireless link will be circuit-switched along with the voice service. That means even in the case where an application on the phone can interact directly via MSP 2.0 functionality, it will not communicate via MSP 2.0 natively and protocol conversion will take place at a gateway in the MSP. Mobile Information Server can be a good solution to organize the delivery of information from the NSP gateway to the MSP gateway.

NSP Delivery to mobile phone

The MSP 2.0 Framework specification allows for registered compression and encoding schemes. This allows a NSP to deliver information to a mobile phone via an MSP either as native character-encoded XML or under a specific (registered) compression scheme. Because a compression scheme usually takes advantage of the known structure of the information being compressed, it is usually necessary to identify both the scheme and the assumed structure. MSP 2.0 allows the negotiation of schema used to describe the structure of request and response packets so this is especially relevant if the compression is intrinsically schema independent. In such a case the schema must be known in order to recover the information sent across the link.

Mobile devices that operate with compressed MSP 2.0 normally use the compressed form directly so that no decompression is required on the client.

Previous Next