Wireless Application Protocol CSCI 465 Nathaniel Samson Alison White Steve MacNeil Michael Pyne James Snow

WAP Background Wireless Application Protocol is the merging of two rapidly evolving networking technologies; wireless data and the Internet. Both of which are growing exponentially, and are continuously reaching new customers. Most of the technology developed for the internet has been designed for desktop and larger computers, and for medium to high bandwidth.

Hand-held wireless devices present a more limited computing environment compared to that of desktop computers. Hand-held devices tend to be limited by: - Less Powerful CPUs - Less memory (ROM and RAM) - Restricted power consumption - Smaller Displays - Different input devices (eg. A phone keypad)

In addition to these client-side problems, wireless data networks supply a wealth of problems: - Less Bandwith - More Latency - Less Connection Stability - Less Predictable Availability

On top of all of these demands, a successful commercial application must also meet specific requirements of its operators, such as: - Interoperability - Scaleability - Efficiency - Reliability - Security

How Are These Needs Being Met? The WWW Model: Applications and content are presented in a standard data format, and are then browsed by applications (web browsers).

How Are These Needs Being Met? The WAP Model: - Content and applications are written in a set of well-known formats, based on the WWW (similar to Java, HTML, CGI) - The content is transported using a set of wireless communication protocols, similarto TCP/IP.

WAP content types and protocols have been encoded for use with hand-held devices. The key to this is proxy technology, comprised of 2 stages: - Protocol Gateway: translates requests from the WAP to the WWW - Content Encoders: communicates between WAP gateways to client device. Data is sent in compact encoded formats reducing the size of data over the network

Components of the WAP Architecture

Wireless Application Environment (WAE) - Application environment based on WWW and mobile telephony technology. - Functions to establish an environment that will allow operators to build applications that reach a wide variety of wireless platforms. - Included is a micro-browser environment that contains Wireless Markup Language (WML); WMLS (script) and Wireless Telephony Application (WTA)

Wireless Session Protocol (WSP) Provides the application layer (WAE) with an interface for two session services, separated by their amount of security; - A connection-oriented service that operates with security above the WTP - An insecure service that connects directly to the WDP

Wireless Transaction Protocol (WTP) A protocol that is suitable for the mobile, hand- held clients by providing: - one-way communication - two-way requests - user-to-user reliability In all three, WTP provides confirmation of successfully received packets.

Wireless Transport Layer Security (WTLS) -Protocol based upon the WWW standard ‘Transport Layer Security’ (TLS). -May be bypassed by a direct connection between the WSP and the WDP, avoiding all security.

Wireless Datagram Protocol (WDP) - Analogous to IP - Operates above the bearer services. - Accessed by any above layers (depending on the security)

The secret to the commercial success of the WAP lies with the WDP’s relationship with the bearers. Consumers are provided with all protocols allowing: - operators to make upgrades to gateways/servers - longevity of customer equiqment

Why should I care about WAP? You Shouldn’t!