Appendix C. Setting up a test environment for Push Proxy Gateway

This appendix explains how to set a test environment for PPG. This contains a simulated SMSC, for instance a http server simulation (this is used as example, because it is simplest) and a simulated push initiator. Between them, there is the push proxy gateway to be tested. This means that you must configure

HTTP SMSC.

Creating push content and control document for testing

Here is an example of a push control document, which gives PPG instructions how to do the pushing.

<?xml version="1.0"?>

<!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP//EN" "http://www.wapforum.org/DTD/pap_1.0.dtd">

<pap>

<push-message push-id="9fjeo39jf084@pi.com" deliver-before-timestamp="2001-09-28T06:45:00Z" deliver-after-timestamp="2001-02-28T06:45:00Z" progress-notes-requested="false">

<address address-value="WAPPUSH=+358408676001/TYPE=PLMN@ppg.carrier.com"/> <quality-of-service priority="low"

delivery-method="unconfirmed"

network-required="true"

network="GSM"

bearer-required="true"

bearer="SMS"/>

</push-message> </pap>

Because the push content is sended to the phone over SMS, rigth value for network-requiredand bearer-requiredis true, for network GSM and for bearer SMS. However, you can omit these values alltogether, if you use a phone number as an address. Address value is international phone number and it must start with plus. It is used here as an unique identifier, SMSC, or sendsms script must transform it to an usable phone number.

Here is an example of Service Indication, a type of push content. Essentially, the phone displays, when it receives this SI, the text "Want to test a fetch" and if the user wants, fetches the content located by URL http://wap.iobox.fi.

<?xml version="1.0"?>

<!DOCTYPE si PUBLIC "-//WAPFORUM//DTD SI 1.0//EN" "http://www.wapforum.org/DTD/si.dtd">

<si>

<indication href="http://wap.iobox.fi" si-id="1@wiral.com" action="signal-high" created="1999-06-25T15:23:15Z"

98

Page 104 Page 106
Page 105
Image 105
Nokia WAP and SMS gateway manual Creating push content and control document for testing
Page 104 Page 106

WAP and SMS gateway specifications

Nokia has long been a pivotal player in the telecommunications industry, and its contributions to mobile communication technology are numerous. Among these contributions, the Nokia WAP and SMS Gateway stand out as essential elements in enabling mobile internet access and messaging services in the early days of wireless communication.

The Nokia WAP (Wireless Application Protocol) gateway was introduced to facilitate mobile access to the internet and to allow users to interact with web services through their mobile devices. Built on a client-server architecture, the WAP gateway acted as a bridge between the mobile network and the internet, translating traditional web content into a format that mobile devices could effectively render. This conversion was crucial, given the limitations of early mobile devices regarding screen size, processing power, and network bandwidth.

One of the main features of the Nokia WAP gateway was its ability to provide users with real-time access to information such as weather updates, news, and stock prices. By using a lightweight markup language called WML (Wireless Markup Language), the gateway allowed developers to create mobile-friendly websites that could be accessed via WAP-enabled devices. This marked a significant step toward the mobile internet we know today, creating a new realm of possibilities for developers and users alike.

Another critical aspect of Nokia's offering was the SMS (Short Message Service) gateway. The SMS gateway provided a robust platform for sending and receiving text messages across various mobile networks. It enabled seamless communication between devices, regardless of the underlying technology. This feature made SMS a popular choice for both personal communication and business applications, such as marketing campaigns and customer service notifications.

The Nokia SMS gateway utilized established protocols, such as SMPP (Short Message Peer-to-Peer), to ensure reliable message delivery and efficient interaction between SMS applications and mobile networks. Its characteristics included scalability, allowing service providers to handle large volumes of messages, and flexibility to integrate with existing applications and systems.

In summary, the Nokia WAP and SMS gateway played a vital role in the evolution of mobile communication. With features that enabled mobile internet access and streamlined messaging capabilities, these technologies laid the groundwork for the mobile-centric world we live in today. Their legacy continues to influence mobile application development and the broader telecommunications landscape. As the industry progresses, the innovations introduced by Nokia serve as a reminder of the foundational technologies that paved the way for modern mobile experiences.
Top Page Image Contents