Its provide the basic information about Wireless Application Protocol.

1. Introduction To By Nitin s 

2. WAP Network S tructure. WAP Network Protocol Structure WAP Gateway WAP Server WAP Protocol Layer WAP and INTERNET Protocol WAP Layer Information : WAE , WSP, WTP, WTLS, WDP  Topic :

3. WAP Network Structure.

7. WAP Application Server A WAP Server is nothing more than a normal web server and a WAP gateway -like device built into one.  The web server supports files such as HTML, JavaScript, multimedia and all types of images. The WAP application server stores WML, WMLScript and WBMP (Wireless Bitmap) images. WAP server usually just a WAP application server with gateway functionality added. It will provide the entire services normal origin server provides, but it will also act as a WAP gateway.

10. 1 Wireless Datagram Protocol (WDP) The WDP layer operates above the data capable bearer services supported by the various network types. Architecture :: The Adaptation layer: The layer that maps the protocol functions directly onto a specific bearer. The Adaptation Layer is different for each bearer and deals with the specific capabilities and characteristics Services : Application addressing by port numbers,optional segmentation and reassemble and optional error detection. WDP supports several simultaneous communication instances from a higher layer over a single underlying WDP bearer service.

12. 3 Wireless Transaction Protocol (WTP) WTP has been defined as a light weight transaction oriented protocol. Suitable for implementation in "thin" clients (mobile stations) and operates efficiently over wireless datagram networks.by the use of unique transaction identifiers, acknowledgements, duplicate removal and retransmissions. WTP is message oriented and designed for services oriented towards transactions, such as "browsing". The basic unit of interchange is an entire message and not a stream of bytes. WTP allows for asynchronous transactions. The Responder sends back the result as the data becomes available. There are 3 classes of transaction service: Class 0: Unreliable invoke message with no result message Class 1: Reliable invoke message with no result message Class 2: Reliable invoke message with exactly one reliable result message For reliable invoke messages, both success and failure is reported. If an invoke cannot be handled by the Responder, an abort message will be returned to the Initiator instead of the result