|
|
Oksijen
WAP Gateway - WAP 2.0 Gateway for Multimedia
Messaging and WAP Browsing Oksijen’s
WAP Gateway is an instrument in enhancing the
connection between the Wireless domain and the
WWW. It is set to revolutionize the WAP user
experience while accessing the Mobile Internet
by handheld devices. The WAP gateway enables
operators to offer enhanced services in the
form of multimedia messaging services, end-to-end-security,
provisioning, location and presence-based services.
The WAP Gateway is necessary to offer Push functionality.
In the regular WAP services access scenario,
a subscriber accesses a WAP service by connecting
to the WAP gateway; the call is connected first
to the server to perform Authentication, Authorization
and Accounting. Once the Push messages has been
authenticated and authorized, call will be connected
to the WAP gateway and accounting starts. This
information is passed onto locally hosted application
on the gateway or to the WEB server through
Internet, if applications are hosted externally.
|
|
Network Provisioning
|
|
WAP
is being used to develop enhanced forms of existing
applications and new versions of today’s
applications. The WAP gateway proposed is for
both GSM-CSD and GSM-GPRS bearers. It comes bundled
with Push Proxy Gateway, which facilitates Push
based services. Apart from backward compatibility
with the earlier WAP 1.X specifications, Oksijen
WAP 2.0 GW supports the enhancements and the new
service features of WAP 2.0.
Personalization,
Localization and Push services, are the key factors
that help organizations implementing WAP to derive
maximum commercial benefits. Oksijen WAP Gateway
takes a step ahead in addressing the ‘Personalization’
factor in the Wireless world.
Personalized service is one, which differentiates
the Mobile Service Providers (MSP) from each other.
MSP needs to have personal information about the
caller and method to communicate this information
to specific applications to perform specified
personal task.
|
| |
Components
of WAP 2.0 Gateway |
|
|
|
|
|
Push Initiator
(PI) :
sends/receives the Push request/response to/from
PPG |
|
|
Push Proxy Gateway
(PPG) :
accepts the request from PI in XML format using
PAP (Push Initiation Protocol) to
authenticate and authorize it. The message is
handled by PPG. After data transformation,
data to be pushed is stored in a shared database.
There are two models of PPG: |
|
|
|
Client/server model (i.e. PPG act as a server
and PI act as a client) |
| Common
Gateway Interface (CGI) script |
|
|
Push
Server :
sends Push data to client. It maps the mobile
number (or client ID) and corresponding
IP address using Identity server |
|
|
|
|
|
|
