throbber
WAP Architecture
`Version 30-Apr-1998
`
`Wireless Application Protocol
`Architecture Specification
`
`Disclaimer:
`
`This document is subject to change without notice.
`
`Petitioner Apple Inc. - Ex. 1039, p. 1
`
`

`
`Version 30-Apr-1998
`
`Page 2 (20)
`
`Contents
`
`1.
`
`2.
`
`SCOPE .............................................................................................................................................................3
`
`DOCUMENT STATUS...................................................................................................................................4
`
`2.1
`2.2
`2.3
`
`COPYRIGHT NOTICE..................................................................................................................................4
`ERRATA ....................................................................................................................................................4
`COMMENTS...............................................................................................................................................4
`
`3.
`
`REFERENCES ................................................................................................................................................5
`
`3.1
`3.2
`
`NORMATIVE REFERENCES ........................................................................................................................5
`INFORMATIVE REFERENCES......................................................................................................................5
`
`4.
`
`DEFINITIONS AND ABBREVIATIONS.....................................................................................................7
`
`4.1
`4.2
`
`DEFINITIONS .............................................................................................................................................7
`ABBREVIATIONS .......................................................................................................................................7
`
`5.
`
`BACKGROUND..............................................................................................................................................9
`
`5.1
`5.2
`
`MOTIVATION.............................................................................................................................................9
`REQUIREMENTS ........................................................................................................................................9
`
`6.
`
`ARCHITECTURE OVERVIEW .................................................................................................................11
`
`6.1
`6.2
`6.3
`6.4
`
`THE WORLD-WIDE WEB MODEL............................................................................................................11
`THE WAP MODEL..................................................................................................................................12
`EXAMPLE WAP NETWORK.....................................................................................................................13
`SECURITY MODEL...................................................................................................................................13
`
`7.
`
`COMPONENTS OF THE WAP ARCHITECTURE.................................................................................15
`
`7.1
`7.2
`7.3
`7.4
`7.5
`7.6
`7.7
`7.8
`
`WIRELESS APPLICATION ENVIRONMENT (WAE) ....................................................................................15
`WIRELESS SESSION PROTOCOL (WSP) ...................................................................................................16
`WIRELESS TRANSACTION PROTOCOL (WTP)..........................................................................................16
`WIRELESS TRANSPORT LAYER SECURITY (WTLS) ................................................................................16
`WIRELESS DATAGRAM PROTOCOL (WDP) .............................................................................................17
`BEARERS ................................................................................................................................................17
`OTHER SERVICES AND APPLICATIONS.....................................................................................................17
`SAMPLE CONFIGURATIONS OF WAP TECHNOLOGY ................................................................................17
`
`COMPLIANCE AND INTEROPERABILITY ..........................................................................................19
`
`FUTURE WORK ITEMS.............................................................................................................................20
`
`8.
`
`9.
`
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 2
`
`

`
`Version 30-Apr-1998
`
`Page 3 (20)
`
`1. Scope
`The Wireless Application Protocol (WAP) is a result of the WAP Forum’s efforts to promote industry-wide
`specifications for technology useful in developing applications and services that operate over wireless
`communication networks. WAP specifies an application framework and network protocols for wireless devices
`such as mobile telephones, pagers, and personal digital assistants (PDAs). The specifications extend and leverage
`mobile networking technologies (such as digital data networking standards) and Internet technologies (such as
`XML, URLs, scripting, and various content formats). The effort is aimed at enabling operators, manufacturers, and
`content developers to meet the challenges in building advanced differentiated services and implementations in a
`fast and flexible manner.
`
`The objectives of the WAP Forum are:
`• To bring Internet content and advanced data services to digital cellular phones and other wireless terminals.
`• To create a global wireless protocol specification that will work across differing wireless network
`technologies.
`• To enable the creation of content and applications that scale across a very wide range of bearer networks
`and device types.
`• To embrace and extend existing standards and technology wherever appropriate.
`
`The WAP Architecture Specification is intended to present the system and protocol architectures essential to
`achieving the objectives of the WAP Forum. The WAP Architecture Specification acts as the starting point for
`understanding the WAP technologies and resulting specifications. As such, it provides an overview of the different
`technologies and references the appropriate specifications for further details.
`
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 3
`
`

`
`Version 30-Apr-1998
`
`Page 4 (20)
`
`2. Document Status
`This document is available online in the following formats:
`
`• PDF format at http://www.wapforum.org/.
`
`2.1 Copyright Notice
`
`© Copyright Wireless Application Protocol Forum, Ltd, 1998. All rights reserved.
`
`2.2 Errata
`
`Known problems associated with this document are published at http://www.wapforum.org/.
`
`2.3 Comments
`
`Comments regarding this document can be submitted to the WAP Forum in the manner published at
`http://www.wapforum.org/.
`
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 4
`
`

`
`Version 30-Apr-1998
`
`Page 5 (20)
`
`3. References
`
`3.1 Normative References
`
`[RFC2119]
`
`[WAEoview]
`
`[WAE]
`
`[WAP]
`
`"Key words for use in RFCs to Indicate Requirement Levels", S. Bradner, March 1997.
`URL: ftp://ftp.isi.edu/in-notes/rfc2119.txt
`
`"Wireless Application Environment Overview", WAP Forum, April 30, 1998. URL:
`http://www.wapforum.org/
`
`"Wireless Application Environment Specification", WAP Forum, April 30, 1998. URL:
`http://www.wapforum.org/
`
`"Wireless Application Protocol Architecture Specification", WAP Forum, April 30, 1998
`URL: http://www.wapforum.org/
`
`[WAPConf]
`
`"Wireless Application Protocol Conformance Statement, Compliance Profile, and Release
`List", WAP Forum, April 30, 1998. URL: http://www.wapforum.org/
`
`[WDP]
`
`[WML]
`
`"Wireless Datagram Protocol Specification", WAP Forum, April 30, 1998. URL:
`http://www.wapforum.org/
`
`"Wireless Markup Language", WAP Forum, April 30, 1998. URL:
`http://www.wapforum.org/
`
`[WMLScript]
`
`"Wireless Markup Language Script", WAP Forum, April 30, 1998. URL:
`http://www.wapforum.org/
`
`[WMLSStdLib]
`
`"Wireless Markup Language Script Standard Libraries", WAP Forum, April 30, 1998.
`URL: http://www.wapforum.org/
`
`[WSP]
`
`[WTA]
`
`[WTAI]
`
`[WTLS]
`
`[WTP]
`
`"Wireless Session Protocol", WAP Forum, April 30, 1998. URL:
`http://www.wapforum.org/
`
`"Wireless Telephony Application Specification", WAP Forum, April 30, 1998. URL:
`http://www.wapforum.org/
`
`"Wireless Telephony Application Interface", WAP Forum, April 30, 1998. URL:
`http://www.wapforum.org/
`
`"Wireless Transport Layer Security Protocol", WAP Forum, April 30, 1998. URL:
`http://www.wapforum.org/
`
`"Wireless Transaction Protocol Specification", WAP Forum, April 30, 1998. URL:
`http://www.wapforum.org/
`
`3.2 Informative References
`
`[ECMAScript]
`
`Standard ECMA-262: "ECMAScript Language Specification", ECMA, June 1997
`
`[HTML4]
`
`[JavaScript]
`
`[RFC1738]
`
`"HTML 4.0 Specification, W3C Recommendation 18-December-1997, REC-HTML40-
`971218", D. Raggett, et al., September 17, 1997. URL: http://www.w3.org/TR/REC-
`html40
`
`"JavaScript: The Definitive Guide", David Flanagan. O’Reilly & Associates, Inc. 1997
`
`"Uniform Resource Locators (URL)", T. Berners-Lee, et al., December 1994. URL:
`ftp://ftp.isi.edu/in-notes/rfc1738.txt
`
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 5
`
`

`
`Version 30-Apr-1998
`
`Page 6 (20)
`
`[RFC1808]
`
`[RFC2045]
`
`[RFC2048]
`
`[RFC2068]
`
`"Relative Uniform Resource Locators", R. Fielding, June 1995. URL: ftp://ftp.isi.edu/in-
`notes/rfc1808.txt
`
`"Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message
`Bodies", N. Freed, et al., November 1996. URL: ftp://ftp.isi.edu/in-notes/rfc2045.txt
`
`"Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", N.
`Freed, et al., November 1996. URL: ftp://ftp.isi.edu/in-notes/rfc2048.txt
`
`"Hypertext Transfer Protocol - HTTP/1.1", R. Fielding, et al., January 1997. URL:
`ftp://ftp.isi.edu/in-notes/rfc2068.txt
`
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 6
`
`

`
`Version 30-Apr-1998
`
`Page 7 (20)
`
`4. Definitions and Abbreviations
`
`4.1 Definitions
`
`The following are terms and conventions used throughout this specification.
`
`The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD
`NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this document are to be interpreted as described in
`[RFC2119].
`
`Author – an author is a person or program that writes or generates WML, WMLScript or other content.
`
`Client – a device (or application) that initiates a request for a connection with a server.
`
`Content – subject matter (data) stored or generated at an origin server. Content is typically displayed or
`interpreted by a user agent in response to a user request.
`
`Content Encoding – when used as a verb, content encoding indicates the act of converting content from one
`format to another. Typically the resulting format requires less physical space than the original, is easier to process
`or store and/or is encrypted. When used as a noun, content encoding specifies a particular format or encoding
`standard or process.
`
`Content Format – actual representation of content.
`
`Device – a network entity that is capable of sending and receiving packets of information and has a unique device
`address. A device can act as both a client or a server within a given context or across multiple contexts. For
`example, a device can service a number of clients (as a server) while being a client to another server.
`
`JavaScript – a de facto standard language that can be used to add dynamic behaviour to HTML documents.
`JavaScript is one of the originating technologies of ECMAScript.
`
`Man-Machine Interface – a synonym for user interface.
`
`Origin Server – the server on which a given resource resides or is to be created. Often referred to as a web server
`or an HTTP server.
`
`Resource – a network data object or service that can be identified by a URL. Resources may be available in
`multiple representations (eg, multiple languages, data formats, size and resolutions) or vary in other ways.
`
`Server – a device (or application) that passively waits for connection requests from one or more clients. A server
`may accept or reject a connection request from a client.
`
`Terminal – a device providing the user with user agent capabilities, including the ability to request and receive
`information. Also called a mobile terminal or mobile station.
`
`User – a user is a person who interacts with a user agent to view, hear, or otherwise use a resource.
`
`User Agent – a user agent is any software or device that interprets WML, WMLScript, WTAI or other resources.
`This may include textual browsers, voice browsers, search engines, etc.
`
`WMLScript – a scripting language used to program the mobile device. WMLScript is an extended subset of the
`JavaScript(cid:212)
` scripting language.
`
`4.2 Abbreviations
`
`For the purposes of this specification, the following abbreviations apply.
`
`HTML
`
`HyperText Markup Language [HTML4]
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 7
`
`

`
`Version 30-Apr-1998
`
`Page 8 (20)
`
`HTTP
`MMI
`PDA
`PICS
`RFC
`SSL
`TLS
`URL
`W3C
`WAE
`WAP
`WDP
`WML
`WSP
`WTA
`WTLS
`WTP
`WWW
`
`HyperText Transfer Protocol [RFC2068]
`Man-Machine Interface
`Personal Digital Assistant
`Protocol Implementation Conformance Statement
`Request For Comments
`Secure Sockets Layer
`Transport Layer Security
`Uniform Resource Locator [RFC1738]
`World Wide Web Consortium
`Wireless Application Environment [WAE]
`Wireless Application Protocol [WAP]
`Wireless Datagram Protocol [WDP]
`Wireless Markup Language [WML]
`Wireless Session Protocol [WSP]
`Wireless Telephony Application [WTA]
`Wireless Transport Layer Security [WTLS]
`Wireless Transaction Protocol [WTP]
`World-Wide Web
`
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 8
`
`

`
`Version 30-Apr-1998
`
`Page 9 (20)
`
`5. Background
`
`5.1 Motivation
`
`WAP is positioned at the convergence of two rapidly evolving network technologies, wireless data and the Internet.
`Both the wireless data market and the Internet are growing very quickly and are continuously reaching new
`customers. The explosive growth of the Internet has fuelled the creation of new and exciting information services.
`
`Most of the technology developed for the Internet has been designed for desktop and larger computers and medium
`to high bandwidth, generally reliable data networks. Mass-market, hand-held wireless devices present a more
`constrained computing environment compared to desktop computers. Because of fundamental limitations of power
`and form-factor, mass-market handheld devices tend to have:
`• Less powerful CPUs,
`• Less memory (ROM and RAM),
`• Restricted power consumption,
`• Smaller displays, and
`• Different input devices (eg, a phone keypad).
`
`Similarly, wireless data networks present a more constrained communication environment compared to wired
`networks. Because of fundamental limitations of power, available spectrum, and mobility, wireless data networks
`tend to have:
`• Less bandwidth,
`• More latency,
`• Less connection stability, and
`• Less predictable availability.
`
`Mobile networks are growing in complexity and the cost of all aspects for provisioning of more value added
`services is increasing. In order to meet the requirements of mobile network operators, solutions must be:
`•
`Interoperable – terminals from different manufacturers communicate with services in the mobile network;
`• Scaleable – mobile network operators are able to scale services to customer needs;
`• Efficient – provides quality of service suited to the behaviour and characteristics of the mobile network;
`• Reliable – provides a consistent and predictable platform for deploying services; and
`• Secure – enables services to be extended over potentially unprotected mobile networks while still
`preserving the integrity of user data; protects the devices and services from security problems such as
`denial of service.
`
`Many of the current mobile networks include advanced services that can be offered to end-users. Mobile network
`operators strive to provide advanced services in a useable and attractive way in order to promote increased usage
`of the mobile network services and to decrease the turnover rate of subscribers. Standard features, like call control,
`can be enhanced by using WAP technology to provide customised user interfaces. For example, services such as
`call forwarding may provide a user interface that prompts the user to make a choice between accepting a call,
`forwarding to another person, forwarding it to voice mail, etc.
`
`The WAP specifications address mobile network characteristics and operator needs by adapting existing network
`technology to the special requirements of mass-market, hand-held wireless data devices and by introducing new
`technology where appropriate.
`
`5.2 Requirements
`
`The requirements of the WAP Forum architecture are to:
`• Leverage existing standards where possible;
`
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 9
`
`

`
`Version 30-Apr-1998
`
`Page 10 (20)
`
`• Define a layered, scaleable and extensible architecture;
`• Support as many wireless networks as possible;
`• Optimise for narrow-band bearers with potentially high latency;
`• Optimise for efficient use of device resources (low memory/CPU usage/power consumption);
`• Provide support for secure applications and communication;
`• Enable the creation of Man Machine Interfaces (MMIs) with maximum flexibility and vendor control;
`• Provide access to local handset functionality, such as logical indication for incoming call;
`• Facilitate network-operator and third party service provisioning;
`• Support multi-vendor interoperability by defining the optional and mandatory components of the
`specifications; and
`• Provide a programming model for telephony services and integration.
`
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 10
`
`

`
`Version 30-Apr-1998
`
`Page 11 (20)
`
`6. Architecture Overview
`
`6.1 The World-Wide Web Model
`
`The Internet World-Wide Web (WWW) architecture provides a very flexible and powerful programming model
`(Figure 1). Applications and content are presented in standard data formats, and are browsed by applications
`known as web browsers. The web browser is a networked application, ie, it sends requests for named data objects
`to a network server and the network server responds with the data encoded using the standard formats.
`
`Request (URL)
`
`Client
`
`User
`Web
`Agent
`Browser
`
`Response (Content)
`
`Web Server
`
`CGI
`Scripts,
`etc.
`
`Content
`
`Figure 1. World-Wide Web Programming Model
`
`The WWW standards specify many of the mechanisms necessary to build a general-purpose application
`environment, including:
`• Standard naming model – All servers and content on the WWW are named with an Internet-standard
`Uniform Resource Locator (URL) [RFC1738, RFC1808].
`• Content typing – All content on the WWW is given a specific type thereby allowing web browsers to
`correctly process the content based on its type [RFC2045, RFC2048].
`• Standard content formats – All web browsers support a set of standard content formats. These include the
`HyperText Markup Language (HTML) [HTML4], the JavaScript scripting language [ECMAScript,
`JavaScript], and a large number of other formats.
`• Standard Protocols – Standard networking protocols allow any web browser to communicate with any web
`server. The most commonly used protocol on the WWW is the HyperText Transport Protocol (HTTP)
`[RFC2068].
`
`This infrastructure allows users to easily reach a large number of third-party applications and content services. It
`also allows application developers to easily create applications and content services for a large community of
`clients.
`
`The WWW protocols define three classes of servers:
`• Origin server – The server on which a given resource (content) resides or is to be created.
`• Proxy – An intermediary program that acts as both a server and a client for the purpose of making requests
`on behalf of other clients. The proxy typically resides between clients and servers that have no means of
`direct communication, eg across a firewall. Requests are either serviced by the proxy program or passed
`on, with possible translation, to other servers. A proxy must implement both the client and server
`requirements of the WWW specifications.
`
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 11
`
`

`
`Version 30-Apr-1998
`
`Page 12 (20)
`
`• Gateway – A server which acts as an intermediary for some other server. Unlike a proxy, a gateway
`receives requests as if it were the origin server for the requested resource.The requesting client may not be
`aware that it is communicating with a gateway.
`
`6.2 The WAP Model
`
`The WAP programming model (Figure 2) is similar to the WWW programming model. This provides several
`benefits to the application developer community, including a familiar programming model, a proven architecture,
`and the ability to leverage existing tools (eg, Web servers, XML tools, etc.). Optimisations and extensions have
`been made in order to match the characteristics of the wireless environment. Wherever possible, existing standards
`have been adopted or have been used as the starting point for the WAP technology.
`
`Client
`
`WAE
`WAE
`User
`User
`Agent
`Agent
`
`Gateway
`
`Origin Server
`
`Encoded Request
`
`Request
`
`Encoders
`Encoders
`and
`and
`Decoders
`Decoders
`
`Encoded Response
`
`Response (Content)
`
`Figure 2. WAP Programming Model
`
`CGI
`Scripts,
`etc.
`
`Content
`
`WAP content and applications are specified in a set of well-known content formats based on the familiar WWW
`content formats. Content is transported using a set of standard communication protocols based on the WWW
`communication protocols. A micro browser in the wireless terminal co-ordinates the user interface and is
`analogous to a standard web browser.
`
`WAP defines a set of standard components that enable communication between mobile terminals and network
`servers, including:
`• Standard naming model – WWW-standard URLs are used to identify WAP content on origin servers.
`WWW-standard URIs are used to identify local resources in a device, eg call control functions.
`• Content typing – All WAP content is given a specific type consistent with WWW typing. This allows
`WAP user agents to correctly process the content based on its type.
`• Standard content formats – WAP content formats are based on WWW technology and include display
`markup, calendar information, electronic business card objects, images and scripting language.
`• Standard communication protocols – WAP communication protocols enable the communication of browser
`requests from the mobile terminal to the network web server.
`
`The WAP content types and protocols have been optimised for mass market, hand-held wireless devices. WAP
`utilises proxy technology to connect between the wireless domain and the WWW. The WAP proxy typically is
`comprised of the following functionality:
`• Protocol Gateway – The protocol gateway translates requests from the WAP protocol stack (WSP, WTP,
`WTLS, and WDP) to the WWW protocol stack (HTTP and TCP/IP).
`• Content Encoders and Decoders – The content encoders translate WAP content into compact encoded
`formats to reduce the size of data over the network.
`
`This infrastructure ensures that mobile terminal users can browse a wide variety of WAP content and applications,
`and that the application author is able to build content services and applications that run on a large base of mobile
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 12
`
`

`
`Version 30-Apr-1998
`
`Page 13 (20)
`
`terminals. The WAP proxy allows content and applications to be hosted on standard WWW servers and to be
`developed using proven WWW technologies such as CGI scripting.
`
`While the nominal use of WAP will include a web server, WAP proxy and WAP client, the WAP architecture can
`quite easily support other configurations. It is possible to create an origin server that includes the WAP proxy
`functionality. Such a server might be used to facilitate end-to-end security solutions, or applications that require
`better access control or a guarantee of responsiveness, eg, WTA.
`
`6.3 Example WAP Network
`
`The following is for illustrative purposes only. An example WAP network is shown in Figure 3.
`
`Web
`Server
`
`HTML
`
`WML
`
`WML
`
`WAP
`Proxy
`
`HTML
`Filter
`
`Wireless
`Network
`
`Binary WML
`
`WTA
`Server
`
`Figure 3. Example WAP Network
`
`In the example, the WAP client communicates with two servers in the wireless network. The WAP proxy
`translates WAP requests to WWW requests thereby allowing the WAP client to submit requests to the web server.
`The proxy also encodes the responses from the web server into the compact binary format understood by the client.
`
`If the web server provides WAP content (e.g., WML), the WAP proxy retrieves it directly from the web server.
`However, if the web server provides WWW content (such as HTML), a filter is used to translate the WWW
`content into WAP content. For example, the HTML filter would translate HTML into WML.
`
`The Wireless Telephony Application (WTA) server is an example origin or gateway server that responds to
`requests from the WAP client directly. The WTA server is used to provide WAP access to features of the wireless
`network provider’s telecommunications infrastructure.
`
`6.4 Security Model
`
`WAP enables a flexible security infrastructure that focuses on providing connection security between a WAP client
`and server.
`
`WAP can provide end-to-end security between WAP protocol endpoints. If a browser and origin server desire end-
`to-end security, they must communicate directly using the WAP protocols. End-to-end security may also be
`
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 13
`
`

`
`Version 30-Apr-1998
`
`Page 14 (20)
`
`achieved if the WAP proxy is trusted or, for example, located at the same physically secure place as the origin
`server.
`
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 14
`
`

`
`Version 30-Apr-1998
`
`Page 15 (20)
`
`7. Components of the WAP Architecture
`The WAP architecture provides a scaleable and extensible environment for application development for mobile
`communication devices. This is achieved through a layered design of the entire protocol stack (Figure 4). Each of
`the layers of the architecture is accessible by the layers above, as well as by other services and applications.
`
`Application Layer (WAE)
`Application Layer (WAE)
`
`Other Services and
`Applications
`
`Session Layer (WSP)
`Session Layer (WSP)
`
`Transaction Layer (WTP)
`Transaction Layer (WTP)
`
`Security Layer (WTLS)
`Security Layer (WTLS)
`
`Transport Layer (WDP)
`Transport Layer (WDP)
`
`Bearers:
`
`GSM
`
`IS-136
`
`CDMA
`
`PHS
`
`CDPD
`
`PDC-P
`
`iDEN
`
`FLEX
`
`Etc...
`
`Figure 4. WAP Architecture
`
`The WAP layered architecture enables other services and applications to utilise the features of the WAP stack
`through a set of well-defined interfaces. External applications may access the session, transaction, security and
`transport layers directly. The following sections provide a description of the various elements of the protocol stack
`architecture.
`
`7.1 Wireless Application Environment (WAE)
`
`The Wireless Application Environment (WAE) is a general-purpose application environment based on a
`combination of World Wide Web (WWW) and Mobile Telephony technologies. The primary objective of the
`WAE effort is to establish an interoperable environment that will allow operators and service providers to build
`applications and services that can reach a wide variety of different wireless platforms in an efficient and useful
`manner. WAE includes a micro-browser environment containing the following functionality:
`
`• Wireless Markup Language (WML) – a lightweight markup language, similar to HTML, but optimised for
`use in hand-held mobile terminals;
`• WMLScript – a lightweight scripting language, similar to JavaScript™;
`• Wireless Telephony Application (WTA, WTAI) – telephony services and programming interfaces; and
`• Content Formats – a set of well-defined data formats, including images, phone book records and calendar
`information.
`
`A much more detailed description of the WAE architecture is provided in [WAEoview].
`
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 15
`
`

`
`Version 30-Apr-1998
`
`Page 16 (20)
`
`7.2 Wireless Session Protocol (WSP)
`
`The Wireless Session Protocol (WSP) provides the application layer of WAP with a consistent interface for two
`session services. The first is a connection-oriented service that operates above the transaction layer protocol WTP.
`The second is a connectionless service that operates above a secure or non-secure datagram service (WDP).
`
`The Wireless Session Protocols currently consist of services suited for browsing applications (WSP/B). WSP/B
`provides the following functionality:
`• HTTP/1.1 functionality and semantics in a compact over-the-air encoding,
`• Long-lived session state,
`• Session suspend and resume with session migration,
`• A common facility for reliable and unreliable data push, and
`• Protocol feature negotiation.
`
`The protocols in the WSP family are optimised for low-bandwidth bearer networks with relatively long latency.
`WSP/B is designed to allow a WAP proxy to connect a WSP/B client to a standard HTTP server. See [WSP] for
`more information.
`
`7.3 Wireless Transaction Protocol (WTP)
`
`The Wireless Transaction Protocol (WTP) runs on top of a datagram service and provides as a light-weight
`transaction-oriented protocol that is suitable for implementation in “thin” clients (mobile stations). WTP operates
`efficiently over secure or non-secure wireless datagram networks and provides the following features:
`
`• Three classes of transaction service:
`• Unreliable one-way requests,
`• Reliable one-way requests, and
`• Reliable two-way request-reply transactions;
`• Optional user-to-user reliability - WTP user triggers the confirmation of each received message;
`• Optional out-of-band data on acknowledgements;
`• PDU concatenation and delayed acknowledgement to reduce the number of messages sent; and
`• Asynchronous transactions.
`
`See [WTP] for more information.
`
`7.4 Wireless Transport Layer Security (WTLS)
`
`WTLS is a security protocol based upon the industry-standard Transport Layer Security (TLS) protocol, formerly
`known as Secure Sockets Layer (SSL). WTLS is intended for use with the WAP transport protocols and has been
`optimised for use over narrow-band communication channels. WTLS provides the following features:
`• Data integrity – WTLS contains facilities to ensure that data sent between the terminal and an application
`server is unchanged and uncorrupted.
`• Privacy – WTLS contains facilities to ensures that data transmitted between the terminal and an application
`server is private and cannot be understood by any intermediate parties that may have intercepted the data
`stream.
`• Authentication – WTLS contains facilities to establish the authenticity of the terminal and application
`server.
`• Denial-of-service protection – WTLS contains facilities for detecting and rejecting data that is replayed or
`not successfully verified. WTLS makes many typical denial-of-service attacks harder to accomplish and
`protects the upper protocol layers.
`
`© Copyright Wireless Application Protocol Forum, Ltd, 1998.
`All rights reserved.
`
`Petitioner Apple Inc. - Ex. 1039, p. 16
`
`

`
`Version 30-Apr-1998
`
`Page 17 (20)
`
`WTLS may also be used for secure communication between terminals, eg, for authentication of electronic business
`card exchange.
`
`Applications are able to selectively enable or disable WTLS features depending on their security requirements and
`the characteristics of the underlying network (eg, privacy may be disabled on networks already providing this
`service at a lower layer).
`
`See [WTLS] for more information.
`
`7.5 Wireless Datagram Protocol (WDP)
`
`The Transport layer protocol in the WAP architecture is referred to as the Wireless Datagram Protocol (WDP).
`The WDP layer operates above the data capable bearer services supported by the various network

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket