WAP is being used to develop enhanced forms of existing applications and new versions of today's applications. Existing mobile data software and hardware vendors are adding WAP support to their offerings, either by developing their own WAP interface or by collaborating with WAP Gateway Suppliers.

Personalization, Localization and Push services, are the key factors that help organizations implementing WAP to derive maximum commercial benefits. Jataayu's Identity Server takes a step ahead in addressing the 'personalization' factor in the wireless world. Personalized service is what makes the difference between a successful Mobile Service Provider (MSP) and an unsuccessful one. The MSP needs to have personal information about the caller and communicate this information to specific applications to perform specified tasks.

In a regular WAP services access scenario, a subscriber accesses a WAP service by connecting to the WAP gateway. The call is connected first to the RAS residing at the site of MSP. From there, the information will pass on to RADIUS Server for Authentication, Authorization and Accounting. Once it has been authenticated and authorized, the call will be connected to the WAP gateway and accounting will start.

The RADIUS Server using the Caller Line Identification information will do authentication and authorization. The information cannot be further passed on to the WAP gateway because CLI data is not available beyond the point where the telephone line ends. Without CLI information the WAP gateway cannot provide personalized service, which forms the core of commercial use of WAP applications. The Jataayu Identity Server placed between the RAS and RADIUS Server, captures the CLI information and will pass it on to the WAP Gateway using special proprietary protocol. This information will be passed onto locally hosted applications on the gateway or to the WEB Server through the Internet, if applications are hosted externally. These applications will provide a specific response depending on the CLI information.

Architecture

Key Features

The WAP Gateway residing at the MSP site can be accessed by end users in two manners:

• Using the services of any ISP The user can dial into any ISP and connect to the WAP Gateway at the mobile service provider site using the Internet. In this case the CLI, information is captured by the RAS at the ISP and does not reach the MSP. The ISP may require an agreement with the MSP and a specific software to run on his Servers for passing CLI information for all the wireless data calls going through his RAS services. In practice, this may not be feasible, as the ISP may be bound by his agreements not to pass on confidential information (such as CLI) to other service providers without the explicit permission of the end user.

• Using RAS at MSP When a user dials the RAS at the cellular service provider's site, the call is generally authenticated using a RADIUS Server at the MSP. The RADIUS Server typically performs functions such as Authentication, Authorization, and Accounting. The CLI information required for the WAP application can be captured using Jataayu Identity Server, which analyses the CLI related data for all WAP traffic and redirects the data to the original RADIUS Server for all other functionality. Jataayu CLI Server extracts CLI related information from the IP traffic through the RAS and passes it onto the WAP gateway, without affecting the functionality of the currently used RADIUS Server. It should be noted here that the CLI data is not available beyond the point where telephone line terminates.

Other Issues
Whenever CLI information is extracted from the RAS, it can be passed on to the WAP Gateway. The WAP Gateway, in turn, can pass this information to the other WAP applications to enable personalized services based on CLI data. However, some service providers feel that CLI is personal information of the subscriber and hence should not be made available to wireless applications hosted on other sites, without the prior consent of the subscriber. In such cases, this information can be effectively used by the MSP to host personalized applications on his portal.

Basic infrastructure requirement for implementing CLI on Jataayu WAP Gateway

• RAS with CLI capability.

• A provision (configuration on RAS) to divert all WAP traffic through Jataayu Identity Server.

• Linux Server to host Jataayu Identity Server

• A policy on the use of CLI information with WAP applications hosted on the Internet

Jataayu Multimedia Messaging Center 
Jataayu WAP 2.0 Gateway  
SMS Gateway  

Add-ons:  Personality Server  

Other Mobile Operator Solutions

SyncML Server
SIM Tool Kit Solution (SIMplify)  
jMEMS - Mobile Enterprise Messaging Server  
Over the Air Provisioning - OTA Server  

Other Solutions

• Mobile Device Solutions

• Enterprise Solutions

• Portal Applications