2. Introduction and Overview WAP Architecture

3. ©1999 Wireless Application Protocol Forum, Ltd. Web Server Content CGI Scripts etc. WML Decks with WML-Script WAP Gateway WML Encoder WMLScript Compiler Protocol Adapters Client WML WML- Script WTAI Etc. HTTPWSP/WTP The WAP Architecture

4. ©1999 Wireless Application Protocol Forum, Ltd. Internet Comparison between Internet and WAP Technologies HTML JavaScript HTTP TLS - SSL TCP/IP UDP/IP Wireless Application Protocol Wireless Application Environment (WAE) Session Layer (WSP) Security Layer (WTLS) Transport Layer (WDP) Other Services and Applications Transaction Layer (WTP) SMSUSSDCSD IS- 136 CDMA CDPDPDC-P Etc.. Bearers:

5. ©1999 Wireless Application Protocol Forum, Ltd. WAP specifies… zWireless Application Environment lWML Microbrowser lWMLScript Virtual Machine lWMLScript Standard Library lWireless Telephony Application Interface lWAP Content Types zWireless Protocols lWireless Session Protocol (WSP) lWireless Transport Layer Security (WTLS) lWireless Transaction Protocol (WTP) lWireless Datagram Protocol (WDP) lWireless network interface definitions

6. ©1999 Wireless Application Protocol Forum, Ltd. WHY WAP ? zWireless networks and phones lhave specific needs and requirements lnot addressed by existing Internet technologies. zOnly be met by participation from entire industry. zWAP enables any data transport lTCP/IP, UDP/IP, GUTS (IS-135/6), SMS, or USSD. zThe WAP architecture lseveral modular entities ltogether form a fully compliant Internet entity lall WML content is accessed via HTTP 1.1 requests.

7. ©1999 Wireless Application Protocol Forum, Ltd. WHY WAP ? zWAP utilizes standard Internet markup language technology (XML) zThe WML UI components map well onto existing mobile phone user interfaces lno re-education of the end-users lleveraging market penetration of mobile devices zWAP utilizes plain Web HTTP 1.1 servers lleveraging existing development methodologies lCGI, ASP, JAVA, etc.

8. ©1999 Wireless Application Protocol Forum, Ltd. Why is HTTP/HTML not enough? Big pipe - small pipe syndrome Wireless network NNN Interactive NNN Intera ctive Internet Enter name: 010011 010011 110110 010011 011011 011101 010010 011010 Content encoding HTTP/HTML WAP

9. ©1999 Wireless Application Protocol Forum, Ltd. WHY WAP ? zGood relationships with standards lWAP compliance profile for GSM. lWAP is actively working with the W3C and IETF lHTML-NG (HTML Next Generation) lHTTP-NG (HTML Next Generation)

10. WAP Application Environment WML and WMLScript Wireless Telephony Architecture Content Formats

11. ©1999 Wireless Application Protocol Forum, Ltd. WAE Goals zNetwork-neutral application environment; zFor narrowband wireless devices; zWith an Internet/WWW programming model; zAnd a high degree of interoperability.

12. ©1999 Wireless Application Protocol Forum, Ltd. WAE Requirements zInternet standard technology zDevice Independent zNetwork Independent zInternational Support

13. ©1999 Wireless Application Protocol Forum, Ltd. Requirements (cont.) zInitial focus on phones lSlow bearers lSmall memory lLimited CPU lSmall screen lLimited input model

14. ©1999 Wireless Application Protocol Forum, Ltd. WAE First Generation zArchitecture lApplication model lBrowser, Gateway, Content Server zWML lDisplay language zWMLScript lScripting language zWTA lTelephony services API and architecture zContent Formats lData exchange

15. ©1999 Wireless Application Protocol Forum, Ltd. WML Second Generation zExtensions and enhancements lCurrently under development z Performance Enhancements lCaching, etc.

16. ©1999 Wireless Application Protocol Forum, Ltd. GatewayClient Network Application WSP/HTTP Request {URL} WSP/HTTP Reply {Content} WAE Abstract Network Architecture

17. ©1999 Wireless Application Protocol Forum, Ltd. Web Server Content CGI Scripts etc. WML Decks with WML-Script WAP Gateway WML Encoder WMLScript Compiler Protocol Adapters Client WML WML- Script WTAI Etc. HTTPWSP/WTP Network Example #1: WAP Gateway

18. ©1999 Wireless Application Protocol Forum, Ltd. WAP Application Server Content Application Logic WML Decks with WML-Script WML Encoder WMLScript Compiler Protocol Adapters Client WML WML- Script WTAI Etc. WSP/WTP Network Example #2: WAP Application Server

19. ©1999 Wireless Application Protocol Forum, Ltd. WML zTag-based browsing language: lScreen management (text, images) lData input (text, selection lists, etc.) lHyperlinks & navigation support zW3C XML-based language zInherits technology from HDML and HTML

20. ©1999 Wireless Application Protocol Forum, Ltd. WML (cont.) zCard metaphor lUser interactions are split into cards lNavigation occurs between cards zExplicit inter-card navigation model lHyperlinks lUI Event handling lHistory zState management and variables lReduce network traffic lResults in better caching

21. ©1999 Wireless Application Protocol Forum, Ltd. Handling User Input zSelect lists lChoose from a list of options zInput fields lEnter a string of text or numbers zKEY variables lSet by SELECT and INPUT elements lHow user input is passed to other cards and the application server

22. ©1999 Wireless Application Protocol Forum, Ltd. Forecast Berlin Rome New City Forecast 1 Berlin 2 Rome 3>New City ____________ Find The SELECT Element zDisplay a list of options lEach option may set the KEY variable and/or bind a task to the ACCEPT key lTITLE= dynamically sets the label string

23. ©1999 Wireless Application Protocol Forum, Ltd. Other SELECT Attributes zMULTIPLE="TRUE" lAllows user to pick multiple items lUP.Browser reserves soft key for item-picker lKey value is a semicolon-separated list zDEFAULT=key_value lDefault KEY value, if one is not chosen lSets cursor to the default choice entry, if a corresponding OPTION / VALUE exists

24. ©1999 Wireless Application Protocol Forum, Ltd. A Long Select List Addr [1..9] Neil Kurt Jim Natasha Liz Aneesh Jennifer Jesse Dawnell More...

25. ©1999 Wireless Application Protocol Forum, Ltd. <GO URL="?get=person" METHOD="POST" POSTDATA="userid=$ssn"/> Soc Security: Soc. Security: 287-33- _ ____________ NUM Soc. Security: 287-33- 7629 ____________ OK The INPUT Element zPrompts user to enter a string of text lUse FORMAT= to constrain input zUP.Browser reserves soft key for text entry mode, if necessary

26. ©1999 Wireless Application Protocol Forum, Ltd. Other INPUT Attributes zDEFAULT=key_value lDefault KEY variable (displayed to user) zFORMAT=format_specifier lIf omitted, free-form entry is allowed zEMPTYOK="TRUE" lBrowser will accept null input, even with format zTYPE= " PASSWORD" lSpecial entry mode handled by the browser zMAXLENGTH=number lMaximum number of allowed characters

27. ©1999 Wireless Application Protocol Forum, Ltd. FORMAT Control Characters lN Numeric character lA, a Alphabetic character lX, x Numeric or alphabetic character lM, m Any character zLeading backslash specifies forced characters lForced characters included in KEY variable value zLeading * specifies 0 or more characters lPassword: FORMAT=“mmmm*m” zLeading number specifies 0..N characters lZipcode:FORMAT=“NNNNN\-4N”

28. ©1999 Wireless Application Protocol Forum, Ltd. Continue <IMG LOCALSRC="righthand" ALT="forward..."/> <IMG SRC="../images/logo.bmp" ALT="Unwired Planet"/> Welcome! Displaying Images zInsert app images or local icons within display text l1-bit BMP format zImages are ignored by non-bitmapped devices lCheck HTTP_ACCEPT for “image/bmp”

29. ©1999 Wireless Application Protocol Forum, Ltd. Special WML Characters  Use character entities in display text " " && &apos;' < Blank space ­Soft hyphen (discretionary line break)  Replace the “&” character in URL strings URL="query.cgi?first=$fname&last=$lname" zUse “$$” to display a single “$” character

30. ©1999 Wireless Application Protocol Forum, Ltd. Doing more with WML zSetting card styles to create forms zUsing variables to cache user data zUsing card intrinsic events to trigger transparent tasks zUsing timers zSecuring WML decks zBookmarking decks

31. ©1999 Wireless Application Protocol Forum, Ltd. WMLScript zScripting language: lProcedural logic, loops, conditionals, etc. lOptimized for small-memory, small-cpu devices zDerived from JavaScript™ zIntegrated with WML lPowerful extension mechanism lReduces overall network traffic

32. ©1999 Wireless Application Protocol Forum, Ltd. WMLScript (cont.) zBytecode-based virtual machine lStack-oriented design lROM-able lDesigned for simple, low-impact implementation zCompiler in network lBetter network bandwidth use lBetter use of terminal memory/cpu.

33. ©1999 Wireless Application Protocol Forum, Ltd. WMLScript Standard Libraries zLang - VM constants, general-purpose math functionality, etc. zString - string processing functions zURL - URL processing zBrowser - WML browser interface zDialog - simple user interface zFloat - floating point functions

34. ©1999 Wireless Application Protocol Forum, Ltd. WMLScript Example Uses zReduce network round-trips and enhance functionality. zField validation lCheck for formatting, input ranges, etc. zDevice extensions lAccess device or vendor-specific API zConditional logic lDownload intelligence into the device

35. ©1999 Wireless Application Protocol Forum, Ltd. Functions WMLScript Example WMLScript is very similar to JavaScript  Programming Constructs Variables function currencyConvertor(currency, exchRate) { return currency*exchangeRate; } function myDay(sunShines) { var myDay; if (sunShines) { myDay = “Good”; } else { myDay = “Not so good”; }; return myDay; }

36. ©1999 Wireless Application Protocol Forum, Ltd. New WAP Content Formats zNewly defined formats: lWML text and tokenized format lWMLScript text and bytecode format lWBMP image format zBinary format for size reduction lBytecodes/tokens for common values and operators lCompressed headers lData compression (e.g. images) zGeneral-purpose transport compression can still be applied

37. ©1999 Wireless Application Protocol Forum, Ltd. Content Format Example Image Element Hello World! <IMG SRC=“/world.wbmp” ALT=“[Globe]” /> Example Use of an Image:

38. ©1999 Wireless Application Protocol Forum, Ltd. Push zPush is under development zNetwork-push of content lAlerts or service indications lPre-caching of data zGoals: lExtensibility and simplicity lSecurity lUser friendly

39. ©1999 Wireless Application Protocol Forum, Ltd. WAE Technical Collaboration zW3C lTechnical collaboration lCC/PP lHTML-NG lHTTP-NG lEtc.

40. ©1999 Wireless Application Protocol Forum, Ltd. Summary: WAE Status zFirst generation released lImplementations are in progress lSpecifications include: lWAE, WML, WMLScript lWBMP, WTA, WTAI, etc. zSecond generation in development lFocusing on: lPush, Interoperability, UAProf lTelephony, Internationalization, etc.

41. ©1999 Wireless Application Protocol Forum, Ltd. Wireless Transaction Service Access Point Wireless Datagram Protocol Bearer Service D Bearer Service C Bearer Service B Transport Service Access Point (TSAP) Bearer Service A Physical Layer Air Link Technology Wireless Transaction Protocol Wireless Session Protocol Wireless Session Service Access Point WCMP WAP Protocol Layers

42. ©1999 Wireless Application Protocol Forum, Ltd. Enhancements Beyond HTTP zBinary header encoding zSession headers zConfirmed and non-confirmed data push zCapability negotiation zSuspend and resume zFully asynchronous requests zConnectionless service

43. ©1999 Wireless Application Protocol Forum, Ltd. Why Not HTTP? zEncoding not compact enough zNo push facility zInefficient capability negotiation

44. ©1999 Wireless Application Protocol Forum, Ltd. Header Encoding zDefined compact binary encoding of headers, content type identifiers and other well-known textual or structured values lReduces the data actually sent over the network

45. ©1999 Wireless Application Protocol Forum, Ltd. Capabilities zCapabilities are defined for: lMessage Size, client and server lProtocol Options: Confirmed Push Facility, Push Facility, Session Suspend Facility, Acknowledgement headers lMaximum Outstanding Requests lExtended Methods lHeader Code Pages

46. ©1999 Wireless Application Protocol Forum, Ltd. Suspend and Resume zServer knows when client can accept a push zMulti-bearer devices zDynamic addressing zAllows the release of underlying bearer resources

47. ©1999 Wireless Application Protocol Forum, Ltd. Session Context and Push zPush can take advantage of session headers zServer knows when client can accept a push

48. ©1999 Wireless Application Protocol Forum, Ltd. Connection And Connectionless Modes zConnection-mode lLong-lived communication lBenefits of the session state lReliability zConnectionless lStateless applications lNo session creation overhead lNo reliability overhead

49. ©1999 Wireless Application Protocol Forum, Ltd. Wireless Datagram Protocol zPurpose: lProvide consistent interface to a fundamental transport service across all wireless bearer networks. lProvides a connectionless, unreliable datagram service. lWDP is adapted to each particular wireless network to provide the generic datagram transport. lThe basic datagram service is fundamental to all wireless networks and makes it possible to utilize WAP everywhere.

50. ©1999 Wireless Application Protocol Forum, Ltd. WDP Continued lSupports port number addressing lWDP was initially specified for the following networks lIS-136 (GUTS, R-Data, CSD, Packet Data) lGSM (SMS, USSD, GPRS, CSD) lCDPD liDEN lFlex and ReFLEX lWPG has since promoted specs for the following networks lPHS lPDC lCDMA lExample: WDP is UDP when used over an IP network layer.

51. ©1999 Wireless Application Protocol Forum, Ltd. WDP TUNNEL Specification Road Map zInput Papers for Kyoto WAP Forum meeting  zObjectives for Kyoto work: lAgree on scope  lAgree on requirements  lDefine outline specification  zDraft Specification January 99  (working document) zProposed Specification February 99 - on track Ft. Worth zApproved Specification May 99

52. ©1999 Wireless Application Protocol Forum, Ltd. WDP TUNNEL Specification Commitment From Major Industry Players zCMG, Comverse, Logica-Aldiscon, Nokia, SEMA Group Telecoms zOperators, third party vendors, Paging networks, infrastructure suppliers zCross standard development zWorkshop 3 February Fort Worth