Cisco Cisco IOS Software Release 12.2(4)XR

When the client wireless device in Figure 1 initiates a request for WAP content, the request is forwarded 
to the WAP gateway via the wireless network provider that the client is using. Protocols used in the 
communication between the client and the gateway may include Wireless Session Protocol (WSP), 
Wireless Transaction Protocol (WTP), and Wireless Transport Layer Security (WTLS). All these 
protocols are optimized for use with wireless devices.

The WAP gateway in Figure 1 receives the request for WAP content from the wireless device and creates 
or reuses a session to the web server and requests content using HTTP. When the content is supplied to 
the gateway, it uses the WML encoder to compress the information and, if required, the gateway uses the 
WMLS compiler to compile the request before sending the WAP content back to the client device. 
Compression is achieved using a process called tokenization.

The web content server in Figure 1 can be an existing web content server using standard URLs and 
Common Gateway Interface (CGI) scripts, but the content destined for client wireless devices must be 
in WML format. The WAP browser in the wireless device cannot display content written in HTML. 
Communication between the gateway and the web server occurs through conventional protocols such as 
HTTP and the TCP/IP protocol stack.

You can integrate WAP services into your existing IP network infrastructure using existing equipment 
because the WAP gateway can run on the Cisco 3640 and 3660 routers and will even run as part of a 
multifunction router. The WAP gateway software uses new and modified commands at the Cisco IOS 
command-line interface (CLI), but the existing commands for configuring an interface or verifying the 
configuration should be familiar to Cisco customers.

Companies can make intranet services available to employees and partners via the WAP gateway without 
compromising security. The Cisco IOS WAP Gateway with WTLS Class 2 Support feature can run on a 
trusted router within the firewall and access WAP content held on an internal server.

The WAP gateway implements WTLS Class 2 security, which provides an optional cryptographic 
method for clients to authenticate the WAP gateway, and encryption between the wireless device and the 
gateway. 

Customers can implement their own user authentication methods by configuring the wap authentication 
service and associated optional commands.

The Cisco IOS WAP Gateway implements the version 1.2 standards from the WAP Forum and will 
support all WAP microbrowsers that also implement these standards. Current and future WAP-enabled 
wireless devices will work with the gateway if they implement the WAP Forum version 1.2 standards.

Cisco CTE 1400 Series Content Transformation Engine

Cisco IOS Server Load Balancing (SLB)