25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

18.6.4 Service indication<br />

The service indication (SI) content type enables the sending of notifications to<br />

users in an asynchronous manner (for example, new e-mails). An SI contains a<br />

short message <strong>and</strong> a Uniform Resource Identifier (URI), indicating a service.<br />

The message is presented to the user on reception. The user can now select to<br />

either start the service immediately or postpone it for a later execution. If the SI is<br />

postponed, the client stores it in order to enable the user for later SI h<strong>and</strong>ling.<br />

18.6.5 Push over-the-air protocol (OTA)<br />

OTA is responsible for transmitting the content from the PPG to the client’s user<br />

agent over the wireless network.<br />

OTA can use a WSP session to deliver the content. However, a WSP session<br />

works in a connection-oriented mode <strong>and</strong> has to be established by a client prior<br />

to delivery of the pushed content. In this case, where there is no active WSP<br />

session, a session initiation application in the client has to establish the session.<br />

This new function in the client works like a server that listens to session requests<br />

from OTA servers <strong>and</strong> responds by setting up a WSP session for the push<br />

purpose.<br />

The client can verify the identity information of the OTA server against a list of<br />

such servers before attempting any push session.<br />

18.6.6 Client-side infrastructure<br />

A connection-oriented push requires an active WSP session. As explained in<br />

18.6.5, “Push over-the-air protocol (OTA)” on page 668, the client needs a<br />

special session initiation application (SIA) in order to set up the push session<br />

with the PPG. After receiving a session request from PPG, SIA establishes a<br />

session with the PPG <strong>and</strong> reports which client applications accept content over<br />

the newly opened session. SIA can also ignore the session request from the<br />

PPG if there is no suitable application available or installed.<br />

When the client receives pushed content, a dispatcher looks at the push<br />

message header to determine its destination application. This dispatcher is<br />

responsible for rejecting content if the destination application is not installed. It is<br />

also responsible for confirming operations to the PPG.<br />

668 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!