Wap01 Mobile 5ex4e

Wireless Application Protocol

Outline          

Mobile applications How are mobile/wireless environments different? What is WAP? WAP Architecture WAE (WML/WMLScript) WTA Framework WAP Push Services WAP Protocol Stack Hype v/s Reality References and Resources

Mobile Applications - 1  Vehicles – transmission of news, road condition etc – ad-hoc network with near vehicles to prevent accidents

 Emergencies – early transmission of patient data to the hospital – ad-hoc network in case of earthquakes, cyclones – military ...

 Traveling salesmen – direct access to central customer files – consistent databases for all agents – mobile office

Mobile Applications - 2  Web access – outdoor Internet access – intelligent travel guide with up-to-date location dependent information

 Information services – push: stock quotes; pull: nearest cash ATM

 Disconnected operations – file-system caching for off-line work – mobile agents, e.g., shopping

 Entertainment – games, etc

Variability of the Mobile Environment Mobility stationary • nomadic (pedestrian speed) • mobile (vehicular speed) • roaming (mobile across networks) •

Connectivity Mobile Device Capability form factor • GUI • multimedia • real-time multimedia •

connected • semi-connected (asymmetric) • weakly connected • disconnected •

World Wide Web and Mobility HTTP/HTML have not been designed for mobile applications/devices

 HTTP 1.0 characteristics – – – – – – –

designed for large bandwidth, low delay stateless, client/server, request/response communication connection oriented, one connection per request T 3-way handshake, DNS lookup overheads big protocol headers, uncompressed content transfer primitive caching (often disabled, dynamic objects) security problems (using SSL/TLS with proxies)

 HTML characteristics – designed for computers with “high” performance, color highresolution display, mouse, hard disk – typically, web pages optimized for design, not for communication; ignore end-system characteristics

System for Mobile WWW  Enhanced browsers – client-aware for mobility

 Proxies – Client proxy: pre-fetching, caching, off-line use – Network proxy: adaptive content transformation for connections – Client and network proxy

 Enhanced servers – server-aware for mobility – serve the content in multiple ways, depending on client capabilities

 New protocols/languages – WAP/WML

Wireless Application Protocol (WAP)  Empowers mobile s with wireless devices to easily access and interact with information and services.  A “standard” created by wireless and Internet companies to enable Internet access from a cellular phone  wapforum.org: – co-founded by Ericsson, Motorola, Nokia, Phone.com – 450 in 2000, comprise of Handset manufacturers, Wireless service providers, ISPs, Software companies in the wireless industry – Goals • deliver Internet services to mobile devices • enable applications to scale across a variety of transport options and device types • independence from wireless network standards • GSM, CDMA IS-95, TDMA IS-136, 3G systems (UMTS, W-CDMA)

WAP: Main Features  Browser – “Micro browser”, similar to existing web browsers

 Markup language – Similar to HTML, adapted to mobile devices

 Script language – Similar to Javascript, adapted to mobile devices

 Gateway – Transition from wireless to wired world

 Server – “Wap/Origin server”, similar to existing web servers

 Protocol layers – Transport layer, security layer, session layer etc.

 Telephony application interface – Access to telephony functions

Internet Model

HTML HTTP TLS/SSL T/IP

WAP Architecture

WML WMLScript WTAI Etc.

Web Server

WAP Gateway WML Encoder

WSP/WTP

WMLScript Compiler

HTTP

Protocol Adapters

CGI Scripts etc.

Content

WML Decks with WML-Script

Client

Common Gateway Interface Source: WAP Forum

WAP Application Server

Client WML WMLScript WTAI

WML Encoder

WSP/WTP

WMLScript Compiler Protocol Adapters

Application Logic

Content

WML Decks with WML-Script

WAP Application Server

Etc.

Source: WAP Forum

WAP Architecture  Another look Key Components • • • • • • •

Origin/Web Server WAP Gateway/Proxy WAP Protocol Stack Micro Browser WML/WML Script Transcoders WTA

Source: WAP Forum

WAP: Network Elements fixed network Internet

HTML

HTML

wireless network WML

filter

WAP proxy

Binary WML

WML HTML

web server

HTML

filter/ WAP proxy

WTA server

Binary WML

Binary WML

PSTN Binary WML: binary file format for clients

Source: Schiller

WAP Specifies  Wireless Application Environment – – – – –

WML Microbrowser WMLScript Virtual Machine WMLScript Standard Library Wireless Telephony Application Interface (WTAI) WAP content types

 Wireless Protocol Stack – – – – –

Wireless Session Protocol (WSP) Wireless Transport Layer Security (WTLS) Wireless Transaction Protocol (WTP) Wireless Datagram Protocol (WDP) Wireless network interface definitions

WAP Stack

MicroBrowser (WML, WMLScript, WTA, WTAI)

Runs on top of WDP Provided lightweight X-oriented service • Unreliable 1-way request • Reliable 1-way/2-way req./response

Lightweight SSL Uses WIM/PKICards Datagram service on different bearers Convergence between bearer services

Different Wireless Tech.

Source: WAP Forum

WAP Stack  WAE (Wireless Application Environment): – Architecture: application model, browser, gateway, server – WML: XML-Syntax, based on card stacks, variables, ... – WTA: telephone services, such as call control, phone book etc.

 WSP (Wireless Session Protocol): – Provides HTTP 1.1 functionality – s session management, security, etc.

 WTP (Wireless Transaction Protocol): – Provides reliable message transfer mechanisms – Based on ideas from T/RPC

 WTLS (Wireless Transport Layer Security): – Provides data integrity, privacy, authentication functions – Based on ideas from TLS/SSL

 WDP (Wireless Datagram Protocol): – Provides transport layer functions – Based on ideas from UDP

Content encoding, optimized for low-bandwidth channels, simple devices

Why is HTTP/HTML not enough? Big pipe - small pipe syndrome Internet HTTP/HTML

<TITLE>NNN Interactive <META HTTP-EQUIV="Refresh" CONTENT="1800, URL=/index.html">

<TITLE >NNN Intera ctive< /TITLE > <META HTTPEQUIV= "Refre sh" CONTEN T="180 0, URL=/i ndex.h tml"> Wireless network WAP <WML> Enter name: Content encoding 010011 010011 110110 010011 011011 011101 010010 011010 Source: WAP Forum WAP: “Killer” Applications  Location-based services – Real-time traffic reporting, Event/restaurant recommendation  Enterprise solutions – Email access, Database access, “global” intranet access – Information updates “pushed” to WAP devices  Financial services – Banking, Bill-paying, Stock trading, Funds transfers  Travel services – Schedules and rescheduling, Reservations  Gaming and Entertainment – Online, real-time, multi-player games – able horoscopes, cartoons, quotes, advice  M-Commerce – Shopping on the go – Instant comparison shopping – Location-based special offers and sales Wireless Application Environment (WAE)  Goals – device and network independent application environment – for low-bandwidth, wireless devices – considerations of slow links, limited memory, low computing power, small display, simple interface (compared to desktops) – integrated Internet/WWW programming model – high interoperability WAE Components  Architecture – Application model, Microbrowser, Gateway, Server  Agents – WML/WTA/Others – content formats: vCard, vCalendar, Wireless Bitmap, WML, ...  WML – XML-Syntax, based on card stacks, variables, ...  WMLScript – procedural, loops, conditions, ... (similar to JavaScript)  WTA – telephone services, such as call control, text messages, phone book, ... (accessible from WML/WMLScript)  Proxy (Method/Push) WAE: Logical Model Origin Servers web server other content server Client Gateway response with content Method proxy encoded response with content Push proxy push content request encoders & decoders encoded push content encoded request WTA agent WML agent other WAE agents WAP Microbrowser      Optimized for wireless devices Minimal RAM, ROM, Display, U and keys Provides consistent service UI across devices Provides Internet compatibility Enables wide array of available content and applications WML: Wireless Markup Language  Tag-based browsing language: – Screen management (text, images) – Data input (text, selection lists, etc.) – Hyperlinks & navigation   Takes into limited display, navigation capabilities of devices XML-based language – describes only intent of interaction in an abstract manner – presentation depends upon device capabilities  Cards and Decks – – – – –  document consists of many cards interactions are split into cards Explicit navigation between cards cards are grouped to decks deck is similar to HTML page, unit of content transmission Events, variables and state mgmt Content (XML) XSL Processor WML Stylesheet WML Browsers HTML StyleSheet HTTP Browser WML   The basic unit is a card. Cards are grouped together into Decks Document ~ Deck (unit of transfer) All decks must contain – Document prologue • XML & document type declaration – <WML> element • Must contain one or more cards WML File Structure <WML> ... WML Content Formats  Common interchange formats, for interoperability  Formats: – – – – Business cards: IMC vCard standard Calendar: IMC vCalendar standard Images: WBMP (Wireless BitMaP) Compiled WML, WMLScript  Newly defined formats: – WML text and tokenized format – WMLScript text and bytecode format – WBMP image format  Binary format for size reduction – Bytecodes/tokens for common values and operators – Compressed headers – Data compression (e.g. images)  General-purpose transport compression can still be applied WML (other features)  Setting card styles to create forms  Using variables to cache data  Using card intrinsic events to trigger transparent tasks  Using timers  Securing WML decks  Bookmarking decks WMLScript  Complement to WML – Derived from JavaScript™  Provides general scripting capabilities – Procedural logic, loops, conditionals, etc. – Optimized for small-memory, small-u devices  Features – local interaction, validity check of input – access to device facilities (phone call, address book etc.) – extensions to the device software • configure device, new functionality after deployment  Bytecode-based virtual machine – Stack-oriented design, ROM-able – Designed for simple, low-impact implementation  WMLScript compiler resides in the network WMLScript Libraries  Lang - VM constants, general-purpose math functionality, etc.  String - string processing functions  URL - URL processing  Browser - WML browser interface  Dialog - simple interface  Float - floating point functions Wireless Telephony Application (WTA)  Collection of telephony specific extensions – designed primarily for network operators  Example – calling a number (WML) wtai://wp/mc;07216086415 – calling a number (WMLScript) WTAPublic.makeCall("07216086415");  Implementation – Extension of basic WAE application model – Extensions added to standard WML/WMLScript browser – Exposes additional API (WTAI) WTA Features  Extension of basic WAE application model – network model for interaction • client requests to server • event signaling: server can push content to the client – event handling • table indicating how to react on certain events from the network • client may now be able to handle unknown events – telephony functions • some application on the client may access telephony functions  WTAI includes: – – – – Call control Network text messaging Phone book interface Event processing  Security model: segregation – Separate WTA browser – Separate WTA port WTA Logical Architecture other telephone networks WTA Origin Server Client WML Scripts WTA & WML server WML decks WTA services network operator trusted domain third party origin servers mobile network WTA agent WAP Gateway WAE services encoders & decoders other WTA servers firewall Source: Schiller WTA Framework Components Source: Heijden WTA Agent  WTA Agent – – – – WML agent with extended functionality can access mobile device’s telephony functions through WTAI can store WTA service content persistently in a repository handles events originating in the mobile network  WTA Agent Context – Abstraction of execution space – Holds current parameters, navigation history, state of agent – Similar to activation record in a process address space  Uses connection-mode and connectionless services offered by WSP  Specific, secure WDP ports on the WAP gateway WTA Events and Repository  WTA Events – – – – Network notifies device of event (such as incoming call) WTA events map to device’s native events WTA services are aware of and able to act on these events example: incoming call indication, call cleared, call connected  WTA Repository – local store for content related to WTA services (minimize network traffic) – Channels: define the service • content format defining a WTA service stored in repository • XML document specifying eventid, title, abstract, and resources that implement a service – Resources: execution scripts for a service • could be WML decks, WML Scripts, WBMP images.. • ed from WTA server and stored in repository before service is referenced – Server can also initiate of a channel WTA Channels and Resources Source: Heijden WTA Interface (public)  WTA Interface – generic, high-level interface to mobile’s telephony functions – setting up phone calls, reading and writing entries in phonebook..  Public WTAI – for third party WML content providers – restricted set of telephony functions available to any WAE Agent – library functions • make call: allows application to setup call to a valid tel number • send DTMF tones: send DTMF tones through the setup call – notified to grant permission for service execution – cannot be triggered by network events – example: Yellow pages service with “make call” feature WTA Interface (network)  Network Common WTAI – WTA service provider is in operator’s domain – all WTAI features are accessible, including the interface to WTA events – library functions • Voice-call control: setup call, accept, release, send DTMF tones • Network text: send text, read text, remove text (SMS) • Phonebook: write, read, remove phonebook entry • Call logs: last dialed numbers, missed calls, received calls • Miscellaneous: terminate WTA agent, protect context – can give blanket permission to invoke a function – example: Voice mail service  Network Specific WTAI – specific to type of bearer network – example: • GSM: call reject, call hold, call transfer, multiparty, send USSD WTA Event Handling  Event occurrence – WTA agent could be executing and expecting the event – WTA agent could be executing and a different event occurs – No service is executing  Event handling – channel for each event defines the content to be processed upon reception of that event  Event binding – association of an event with the corresponding handler (channel) – Global binding: • channel corresponding to the event is stored in the repository • event causes execution of resources defined by the channel • example: voice mail service – Temporary binding: • resources to be executed are defined by the already executing service • example: yellow pages lookup and call establishment Event Handling (no service in execution) Source: Heijden Event Handling (service already execution) 1: Temporary binding exists 2. No temporary binding and context is protected 3: No temporary binding and context is not protected Source: Heijden WTA: Voice mail Example WTA client WTA server push deck display deck; selects wait for call accept call mobile network voice mail server incoming voice message indicate new voice message generate new deck request translate play requested voice message call indication setup call accept call accept call setup call voice connection Source: Schiller WAP Push Services  Web push – Scheduled pull by client (browser) • example: Active Channels – no real-time alerting/response • example: stock quotes  Wireless push – accomplished by using the network itself • example: SMS – limited to simple text, cannot be used as starting point for service • example: if SMS contains news, cannot request specific news item  WAP push – Network ed push of WML content • example: Alerts or service indications – Pre-caching of data (channels/resources) WAP Push Framework Source: Heijden Over the Air (OTA) Protocol  Extends WSP with push-specific functionality  Application ID uniquely identifies a particular application in the client (referenced as a URI)  Connection-oriented mode – client informs proxy of application IDs in a session  Connectionless mode – well known ports, one for secure and other for non-secure push  Session Initiation Application (SIA) – unconfirmed push from proxy to client – request to create a session for a specific agent and bearer WAE Summary  WML – analogous to HTML (optimized for wireless) – event based, microbrowser agent  WMLScript – analogous to JavaScript – features of compiler in the network  WTA – WTAI: different access rights for different applications/agents – WTA Agent (analogy with operating systems) • Context – Activation Record • Channel – Interrupt Handler • Resource – Shared routines invoked by interrupt handlers • Repository – Library of interrupt handlers – feature of dynamically pushing the interrupt handler before the event  Push – no analogy in Internet WAP Gateway Summary  Encoders – translate between binary (WML) and text (HTML/WML)  Filters – transcoding between WML (wireless) and HTML (wired)  Method Proxy – similar to standard proxy services – WAP stack on wireless interface and T/IP stack on Internet interface  Push Proxy – Push Access Protocol with Internet Push Initiator (Web Server) – Over the Air Protocol with mobile device (and WAP Push Initiator) – Performs necessary filtering, translation etc. WAP Servers Summary  Origin Server – Web server with HTML/WML contents – Runs T/IP stack, needs PAP protocol for push, no end-to-end security  WAP Server – Serves WML content – Runs WAP stack, uses OTA protocol for push, end-to-end security possible  WTA Server – Specialized for telephony applications (runs WAP stack, uses push extensively) – Client initiated (make call “hyperlink” from a Yellow pages service) – Server intiated (incoming call from a Voice mail service) WAP: Protocol Stack Internet HTML, Java A-SAP WAP Application Layer (WAE) S-SAP additional services and applications Session Layer (WSP) HTTP TR-SAP Transaction Layer (WTP) SEC-SAP SSL/TLS Security Layer (WTLS) T-SAP T/IP, UDP/IP, media Transport Layer (WDP) WCMP Bearers (GSM, CDPD, ...) WAE comprises WML (Wireless Markup Language), WML Script, WTAI etc. Source: Schiller WDP: Wireless Datagram Protocol  Goals – create a worldwide interoperable transport system by adapting WDP to the different underlying technologies – transmission services, such as SMS in GSM might change, new services can replace the old ones  WDP – Transport layer protocol within the WAP architecture – uses the Service Primitive • T-UnitData.req .ind – uses transport mechanisms of different bearer technologies – offers a common interface for higher layer protocols – allows for transparent communication despite different technologies – addressing uses port numbers – WDP over IP is UDP/IP WDP: Service Primitives T-SAP T-DUnitdata.req (DA, DP, SA, SP, UD) T-SAP T-DUnitdata.ind (SA, SP, UD) T-DUnitdata.req (DA, DP, SA, SP, UD) T-DError.ind (EC) SAP: Service Access Point DA: Destination Address DP: Destination Port SA: Source Address SP: Source Port UD: Data EC: Error Code Source: Schiller Service, Protocol, and Bearer Example WAP Over GSM Circuit-Switched WAP Proxy/Server Mobile WAE WSP IWF ISP/RAS WTP UDP WTP UDP IP PPP CSD-RF WAE Apps on Other Servers WSP IP IP PSTN Subnetwork Circuit Subnetwork PPP CSDRF PSTN Circuit RAS - Remote Access Server IWF - InterWorking Function Source: WAP Forum Service, Protocol, and Bearer Example WAP Over GSM Short Message Service WAP Proxy/Server Mobile WAE WAE Apps on other servers WSP WSP SMSC WTP WDP SMS WTP WDP SMS WDP Tunnel Protocol WDP Tunnel Protocol Subnetwork Subnetwork under development Source: WAP Forum WTLS:Wireless Transport Layer Security  Goals – Provide mechanisms for secure transfer of content, for applications needing privacy, identification, message integrity and non-repudiation – Provide for protection against denial-of-service attacks  WTLS – is based on the TLS/SSL (Transport Layer Security) protocol – optimized for low-bandwidth communication channels – provides • privacy (encryption) • data integrity (MACs) • authentication (public-key and symmetric) – Employs special adapted mechanisms for wireless usage • Long lived secure sessions • Optimised handshake procedures • Provides simple data reliability for operation over datagram bearers WTLS Internal Architecture Transaction Protocol (WTP) WTLS Handshake Protocol Alert Protocol Application Protocol Change Cipher Spec Protocol Record Protocol Record protocol Datagram Protocol (WDP/UDP) Bearer networks Source: WAP Forum WTLS: Secure session, Full handshake originator SEC-SAP SEC-Create.req (SA, SP, DA, DP, KES, CS, CM) peer SEC-SAP SEC-Create.ind (SA, SP, DA, DP, KES, CS, CM) SEC-Create.res (SNM, KR, SID, KES‘, CS‘, CM‘) SEC-Create.cnf (SNM, KR, SID, KES‘, CS‘, CM‘) SEC-Exchange.ind SEC-Exchange.res (CC) SEC-Commit.req SEC-Commit.cnf SEC-Exchange.req KES: Key Exchange Suite CS: Cipher Suite CM: Compression Mode SNM: Sequence Number Mode SEC-Exchange.cnf (CC) SEC-Commit.ind KR: Key Refresh Cycle SID: Session Identifier CC: Client Certificate Source: Schiller WTLS: Transferring Datagrams sender SEC-SAP SEC-Unitdata.req (SA, SP, DA, DP, UD) receiver SEC-SAP SEC-Unitdata.ind (SA, SP, DA, DP, UD) Source: Schiller WTP: Wireless Transaction Protocol  Goals – different transaction services that enable applications to select reliability, efficiency levels – low memory requirements, suited to simple devices (< 10kbyte ) – efficiency for wireless transmission  WTP – – – – s peer-to-peer, client/server and multicast applications efficient for wireless transmission for different communication scenarios class 0: unreliable message transfer • unconfirmed Invoke message with no Result message • a datagram that can be sent within the context of an existing Session – class 1: reliable message transfer without result message • confirmed Invoke message with no Result message • used for data push, where no response from the destination is expected – class 2: reliable message transfer with exactly one reliable result message • confirmed Invoke message with one confirmed Result message • a single request produces a single reply WTP Services and Protocols  WTP (Transaction) – provides reliable data transfer based on request/reply paradigm • no explicit connection setup or tear down • optimized setup (data carried in first packet of protocol exchange) • seeks to reduce 3-way handshake on initial request – s • header compression • segmentation /re-assembly • retransmission of lost packets • selective-retransmission • port number addressing (UDP ports numbers) • flow control – message oriented (not stream) – s an Abort function for outstanding requests – s concatenation of PDUs – s acknowledgement or Stack acknowledgement option • acks may be forced from the WTP (upper layer) • default is stack ack WTP Class 0 Transaction initiator TR-SAP TR-Invoke.req (SA, SP, DA, DP, A, UD, C=0, H) responder TR-SAP Invoke PDU TR-Invoke.ind (SA, SP, DA, DP, A, UD, C=0, H‘) A: Acknowledgement Type (WTP/) C: Class (0,1,2) H: Handle (socket alias) Source: Schiller WTP Class 1 Transaction, no ack & ack initiator TR-SAP TR-Invoke.req (SA, SP, DA, DP, A, UD, C=1, H) Invoke PDU TR-Invoke.ind (SA, SP, DA, DP, A, UD, C=1, H‘) U Ack PD TR-Invoke.cnf (H) initiator TR-SAP responder TR-SAP Invoke PDU U Ack PD TR-Invoke.req (SA, SP, DA, DP, A, UD, C=1, H) TR-Invoke.cnf (H) responder TR-SAP TR-Invoke.ind (SA, SP, DA, DP, A, UD, C=1, H‘) TR-Invoke.res (H‘) Source: Schiller WTP Class 2 Transaction, no ack, no hold on initiator TR-SAP TR-Invoke.req (SA, SP, DA, DP, A, UD, C=2, H) TR-Invoke.cnf (H) responder TR-SAP Invoke P DU Result PDU TR-Invoke.ind (SA, SP, DA, DP, A, UD, C=2, H‘) TR-Result.req (UD*, H‘) TR-Result.ind (UD*, H) TR-Result.res (H) Ack PD U TR-Result.cnf (H‘) Source: Schiller WTP Class 2 Transaction, ack initiator TR-SAP TR-Invoke.req (SA, SP, DA, DP, A, UD, C=2, H) responder TR-SAP Invoke P DU TR-Invoke.res (H‘) TR-Invoke.cnf (H) Ack PD TR-Result.ind (UD*, H) Result PDU TR-Result.res (H) Ack PD TR-Invoke.ind (SA, SP, DA, DP, A, UD, C=2, H‘) U U TR-Result.req (UD*, H‘) TR-Result.cnf (H‘) Source: Schiller WTP Class 2 Transaction, hold on, no ack initiator TR-SAP TR-Invoke.req (SA, SP, DA, DP, A, UD, C=2, H) responder TR-SAP Invoke PDU TR-Invoke.cnf (H) Ack PD TR-Result.ind (UD*, H) Result PDU TR-Result.res (H) Ack PD U U TR-Invoke.ind (SA, SP, DA, DP, A, UD, C=2, H‘) TR-Result.req (UD*, H‘) TR-Result.cnf (H‘) Source: Schiller WSP - Wireless Session Protocol  Goals – HTTP 1.1 functionality • Request/reply, content type negotiation, ... – of client/server transactions, push technology – key management, authentication, Internet security services  WSP Services – – – – – provides shared state between client and server, optimizes content transfer session management (establish, release, suspend, resume) efficient capability negotiation content encoding push  WSP/B (Browsing) – – – – HTTP/1.1 functionality - but binary encoded exchange of session headers push and pull data transfer asynchronous requests WSP Overview  Header Encoding – compact binary encoding of headers, content type identifiers and other well-known textual or structured values – reduces the data actually sent over the network  Capabilities (are defined for): – message size, client and server – protocol options: Confirmed Push Facility, Push Facility, Session Suspend Facility, Acknowledgement headers – maximum outstanding requests – extended methods – header code pages  Suspend and Resume – – – – server knows when client can accept a push multi-bearer devices dynamic addressing allows the release of underlying bearer resources WSP Sessions  Session Context and Push – push can take advantage of session headers – server knows when client can accept a push  Connection-mode – long-lived communication, benefits of the session state, reliability  Connectionless-mode – stateless applications, no session creation overhead, no reliability overhead WSP/B session establishment client S-SAP S-Connect.req (SA, CA, CH, RC) S-Connect.cnf (SH, NC) server S-SAP Conne ct PDU ConnR eply P DU WTP Class 2 transaction S-Connect.ind (SA, CA, CH, RC) S-Connect.res (SH, NC) CH: Client Header RC: Requested Capabilities SH: Server Header NC: Negotiated Capabilities Source: Schiller WSP/B session suspend/resume client S-SAP S-Suspend.req Suspe S-Suspend.ind (R) S-Resume.req (SA, CA) S-Resume.cnf server S-SAP nd PD U S-Suspend.ind (R) WTP Class 0 transaction ~ Resum e PDU Reply PDU ~ R: Reason for disconnection S-Resume.ind (SA, CA) S-Resume.res WTP Class 2 transaction Source: Schiller WAP Stack Summary  WDP – functionality similar to UDP in IP networks  WTLS – functionality similar to SSL/TLS (optimized for wireless)  WTP – – – – Class 0: analogous to UDP Class 1: analogous to T (without connection setup overheads) Class 2: analogous to RPC (optimized for wireless) features of “ acknowledgement”, “hold on”  WSP – WSP/B: analogous to http 1.1 (add features of suspend/resume) – method: analogous to RPC/RMI – features of asynchronous invocations, push (confirmed/unconfirmed) WAP: Ongoing Work  WDP – Tunnel to WAP where no (end-to-end) IP bearer available  WTLS – for end-to-end security (extending WTLS endpoint beyond WAP Gateway) – interoperable between WAP and Internet (public key infrastructure) – integrating Smart Cards for security functions  WTP – efficient transport over wireless links (wireless T) – bearer selection/switching – quality of service definitions  WSP – quality of service parameters – multicast data, multimedia  WAE – agent profiles: personalize for device characteristics, preferences etc – Push architecture, asynchronous applications – Billing WAP: Hype vs Reality  Low-bandwidth wireless links – t/ip over wireless can also address these problems – encoding in http can also reduce data transfer on wireless links  Limited device capabilities – Microbrowser is appropriate to address this problem – WTAI features are not present in t/ip domain  Challenges in WAP – adapting to applications rich in content and interaction – service guarantees – interface design and usability  Other approaches for WWW access through mobiles – i-Mode (from NTT DoCoMo) – WAP is a TRAP (http://www.freeprotocols.org/wapTrap) Related Documents 2w1qw Wap01 Mobile 5ex4e March 2021 0 Mobile 4s1i17 April 2020 20 Mobile Iptv 1b6641 July 2021 0 Mobile Textula 55f3i December 2021 0 Mobile Computing 1q3q4y August 2021 0 Twinstant Mobile 4yi26 November 2022 0 More Documents from "bhawna " 116n44 Case Study- Dhirubhai Ambani 5r661a December 2021 0 Project Report On Stock Exchange 6wu2z November 2019 58 Mcgraw-hill Education 6 Ielts Practice Tests Book.pdf 1k1r December 2020 0 Wap01 Mobile 5ex4e March 2021 0 Asynchronous Chip 124g73 April 2022 0 Big Bazaar Case Study 11.07.10 2o183z December 2019 55 Copyright © 2025 IDOUB.