Misplaced Pages

#754245

50-578: . Introduced in 1999, WAP allowed at launch users with compatible mobile devices to browse content such as news, weather and sports scores provided by mobile network operators, specially designed for the limited capabilities of a mobile device. The Japanese i-mode system offered another major competing wireless data standard. Before the introduction of WAP, mobile service providers had limited opportunities to offer interactive data services, but needed interactivity to support Internet and Web applications. Although hyped at launch, WAP suffered from criticism. However

100-557: A "build it and they will come" strategy, meaning that they would just provide the transport of data as well as the terminals, and then wait for content providers to publish their services on the Internet and make their investment in WAP useful. However, content providers received little help or incentive to go through the complicated route of development. Others, notably in Japan (cf. below), had

150-420: A bit like UDP to the upper layers by providing unreliable transport of data with two 16-bit port numbers (origin and destination). All the upper layers view WDP as one and the same protocol, which has several "technical realizations" on top of other "data bearers" such as SMS , USSD , etc. On native IP bearers such as GPRS , UMTS packet-radio service, or PPP on top of a circuit-switched data connection, WDP

200-417: A common protocol stack is a spanning layer , a term coined by David Clark Certain protocols are designed with the specific purpose of bridging differences at the lower layers, so that common agreements are not required there. Instead, the layer provides the definitions that permit translation to occur between a range of services or technologies used below. Thus, in somewhat abstract terms, at and above such

250-558: A cut-down version of XHTML with end-to-end HTTP , dropping the gateway and custom protocol suite used to communicate with it. A WAP gateway can be used in conjunction with WAP 2.0; however, in this scenario, it is used as a standard proxy server. The WAP gateway's role would then shift from one of translation to adding additional information to each request. This would be configured by the operator and could include telephone numbers, location, billing information, and handset information. Mobile devices process XHTML Mobile Profile (XHTML MP),

300-543: A layer common standards contribute to interoperation, while below the layer translation is used. Such a layer is called a spanning layer in this paper. As a practical matter, real interoperation is achieved by the definition and use of effective spanning layers. But there are many different ways that a spanning layer can be crafted. In the Internet protocol stack, the Internet Protocol Suite constitutes

350-626: A minimum an <si> element and an <indication> element. An example of a Service Indication: Once a push message is received from the Push Initiator, the PPG has two avenues for delivery. If the IP address of the Mobile Station is known to the PPG, the PPG can deliver directly to the mobile station over an IP bearer. This is known as "Connection Oriented Push". If the IP address of

400-663: A more thorough dialogue with their content-provider community, which was then replicated in modern, more successful WAP services such as i-mode in Japan or the Gallery service in France. The original WAP model provided a simple platform for access to web-like WML services and e-mail using mobile phones in Europe and the SE Asian regions. In 2009 it continued to have a considerable user base. The later versions of WAP, primarily targeting

450-494: A proxy which checks decks for WML syntax correctness and consistency, which improves the user experience in resource-constrained mobile phones. WAP cannot guarantee how content will appear on a screen, because WAP elements are treated as hints to accommodate the capabilities of each mobile device. For example some mobile phones do not support graphics/images or italics. The Wireless Application Environment (WAE) space defines application-specific markup languages. For WAP version 1.X,

500-412: A range of different protocols (SMS, IP over PPP over a circuit switched bearer, IP over GPRS, etc.). This has led to a protocol considerably more complex than an approach directly over IP might have caused. Most controversial, especially for many from the IP side, was the design of WAP over IP. WAP's transmission layer protocol, WTP, uses its own retransmission mechanisms over UDP to attempt to solve

550-477: A spanning layer that defines a best-effort service for global routing of datagrams at Layer 3 . The Internet is the community of interoperation based on this spanning layer. Service Indication A Push Proxy Gateway is a component of WAP Gateways that pushes URL notifications to mobile handsets. Notifications typically include MMS , email, IM, ringtone downloads, and new device firmware notifications. Most notifications will have an audible alert to

SECTION 10

#1732775899755

600-549: A to render and display pages written in WML, WAP's markup language. The WAP standard described a protocol suite or stack allowing the interoperability of WAP equipment and software with different network technologies, such as GSM and IS-95 (also known as CDMA ). The bottom-most protocol in the suite, the Wireless Datagram Protocol (WDP), functions as an adaptation layer that makes every data network look

650-480: A wide range of modified processors, but GPRS activation from the network is not generally supported, so WAP Push messages have to be delivered on top of the SMS bearer. On receiving a WAP Push, a WAP 1.2 (or later) -enabled handset will automatically give the user the option to access the WAP content. This is also known as WAP Push SI ( Service Indication ). A variant, known as WAP Push SL ( Service Loading ), directly opens

700-585: Is extensive, and includes all Android handsets, all versions of the iPhone handset, all Blackberry devices, all devices running Windows Phone, and many Nokia handsets. WAP saw major success in Japan. While the largest operator NTT DoCoMo did not use WAP in favor of its in-house system i-mode , rival operators KDDI ( au ) and SoftBank Mobile (previously Vodafone Japan ) both successfully deployed WAP technology. In particular, ( au )'s chakuuta or chakumovie (ringtone song or ringtone movie) services were based on WAP. Like in Europe, WAP and i-mode usage declined in

750-432: Is in fact exactly UDP. WTLS , an optional layer, provides a public-key cryptography -based security mechanism similar to TLS . WTP provides transaction support adapted to the wireless world. It provides for transmitting messages reliably, similarly to TCP . However WTP is more effective than TCP when packets are lost, a common occurrence with 2G wireless technologies in most radio conditions. WTP does not misinterpret

800-550: Is required to connect them. One could combine the two protocols to form a powerful third, mastering both cable and wireless transmission, but a different super-protocol would be needed for each possible combination of protocols. It is easier to leave the base protocols alone and design a protocol that can work on top of any of them (the Internet Protocol is an example). This will make two stacks of two protocols each. The inter-network protocol will communicate with each of

850-529: Is similar to URLs in HTTP. Relative URLs in WAP are used for navigating within a deck, and Absolute URLs in WAP are used for navigating between decks. WAP was designed to operate in bandwidth-constrained networks by using data compression before transmitting data to users. This protocol suite allows a terminal to transmit requests that have an HTTP or HTTPS equivalent to a WAP gateway ; the gateway translates requests into plain HTTP. WAP decks are delivered through

900-610: The Microsoft Windows and DOS environment. The application-to-transport interface defines how application programs make use of the transport layers. For example, this interface level would define how a web browser program would talk to TCP/IP transport software. Examples of these interfaces include Berkeley sockets and System V STREAMS in Unix-like environments, and Winsock for Microsoft Windows. An important feature of many communities of interoperability based on

950-512: The stack is the software implementation of them. Individual protocols within a suite are often designed with a single purpose in mind. This modularization simplifies design and evaluation. Because each protocol module usually communicates with two others, they are commonly imagined as layers in a stack of protocols. The lowest protocol always deals with low-level interaction with the communications hardware. Each higher layer adds additional capabilities. User applications usually deal only with

1000-642: The 2010s as HTML-capable smartphones became popular in Japan. Adoption of WAP in the US suffered because many cell phone providers required separate activation and additional fees for data support, and also because telecommunications companies sought to limit data access to only approved data providers operating under license of the signal carrier. In recognition of the problem, the US Federal Communications Commission (FCC) issued an order on 31 July 2007 which mandated that licensees of

1050-424: The 22-megahertz wide "Upper 700 MHz C Block" spectrum would have to implement a wireless platform which allows customers, device manufacturers, third-party application developers, and others to use any device or application of their choice when operating on this particular licensed network band. Commentators criticized several shortcomings of Wireless Markup Language (WML) and WAP. However, others argued that, given

SECTION 20

#1732775899755

1100-478: The Internet. However, they also made sure that the first page that clients accessed was their own "wireless portal", which they controlled very closely. Some carriers also turned off editing or accessing the address bar in the device's browser. To facilitate users wanting to go off deck, an address bar on a form on a page linked off the hard coded home page was provided. It makes it easier for carriers to implement filtering of off deck WML sites by URLs or to disable

1150-483: The United States market, were designed by Daniel Tilden of Bell Labs for a different requirement - to enable full web XHTML access using mobile devices with a higher specification and cost, and with a higher degree of software complexity. Considerable discussion has addressed the question whether the WAP protocol design was appropriate. The initial design of WAP specifically aimed at protocol independence across

1200-404: The ability to press '4' to access directly the fourth link in a list) were variously implemented depending on phone models (sometimes with the accesskey number automatically displayed by the browser next to the link, sometimes without it, and sometimes accesskeys were not implemented at all). Constrained user interface capabilities: Terminals with small black-and-white screens and few buttons, like

1250-402: The actual behavior of phones, principally because WAP-service implementers and mobile-phone manufacturers did not obtain a copy of the standards or the correct hardware and the standard software modules. As an example, some phone models would not accept a page more than 1 Kb in size, and some would even crash. The user interface of devices was also underspecified: as an example, accesskeys (e.g.,

1300-416: The address bar in the future if the carrier decides to switch all users to a walled garden model. Given the difficulty in typing up fully qualified URLs on a phone keyboard, most users would give up going "off portal" or out of the walled garden ; by not letting third parties put their own entries on the operators' wireless portal, some contend that operators cut themselves off from a valuable opportunity. On

1350-498: The address value and type. The value is typically a MSISDN and type indicates whether to send to an MSISDN (typical case) or to an IP Address. The TYPE is almost always MSISDN as the Push Initiator (PI) will not typically have the Mobile Station's IP address - which is generally dynamic. In the case of IP Address: TYPE=USER@a.b.c.d Additional capability of PAP can be found in the PAP article. A PUSH Service Indication (SI) contains at

1400-401: The base protocols in their simpler language; the base protocols will not talk directly to each other. A request on computer A to send a chunk of data to C is taken by the upper protocol, which (through whatever means) knows that C is reachable through B . It, therefore, instructs the wireless protocol to transmit the data packet to B . On this computer, the lower layer handlers will pass

1450-401: The browser to display the WAP content, without user interaction. Since this behaviour raises security concerns, some handsets handle WAP Push SL messages in the same way as SI, by providing user interaction. The network entity that processes WAP Pushes and delivers them over an IP or SMS Bearer is known as a Push Proxy Gateway (PPG). A re-engineered 2.0 version was released in 2002. It uses

1500-475: The demands of optimizing for and testing on a wide variety of wireless devices, considerably lengthened the time required to complete most projects. As of 2009, however, with many mobile devices supporting XHTML, and programs such as Adobe Go Live and Dreamweaver offering improved web-authoring tools, it became easier to create content accessible to many more new devices. Lack of user agent profiling tools: Websites adapt content to fit many device models by adapting

1550-401: The early WAP terminals, face difficulties in presenting a lot of information to their user, which compounded the other problems: one would have had to be extra careful in designing the user interface on such a resource-constrained device which was the real concept of WAP. In contrast with web development, WAP development was unforgiving due to the strict requirements of the WML specification and

Wireless Application Protocol - Misplaced Pages Continue

1600-407: The event of an SMS infrastructure outage, and also provide for message throttling. Since a WAP Push message can be larger than a single SMS message can contain, the push message may be broken up into multiple SMS messages, as a multipart SMS. In Connection Oriented pushes (where the device supports it), an SMSC BIND is not required if the gateway is aware of the handsets IP Address. If the gateway

1650-462: The introduction of GPRS networks, offering a faster speed, led to an improvement in the WAP experience.WAP content was accessed using a WAP browser , which is like a standard web browser but designed for reading pages specific for WAP, instead of HTML. By the 2010s it had been largely superseded by more modern standards such as XHTML. Modern phones have proper Web browsers, so they do not need WAP markup for compatibility, and therefore, most are no longer

1700-420: The markup language defined in WAP 2.0. It is a subset of XHTML and a superset of XHTML Basic . A version of Cascading Style Sheets ( CSS ) called WAP CSS is supported by XHTML MP. Multimedia Messaging Service (MMS) is a combination of WAP and SMS allowing for sending of picture messages. The WAP Forum was founded in 1998 by Ericsson, Motorola, Nokia and Unwired Planet. It aimed primarily to bring together

1750-438: The media and transport layers, and one between the transport layers and applications. The media-to-transport interface defines how transport protocol software makes use of particular media and hardware types and is associated with a device driver . For example, this interface level would define how TCP/IP transport software would talk to the network interface controller . Examples of these interfaces include ODI and NDIS in

1800-448: The mobile station is not known to the PPG, the PPG will deliver over an SMS bearer. Delivery over an SMS bearer is known as "Connectionless Push". In Connectionless Push, an SMSC BIND is required for the PPG to deliver its push message to the mobile station. Typically, a PPG will have a local SMS queuing mechanism running locally that it BINDs to, and which in turn BINDs to the carrier's SMSC. This mechanism should allow for queuing in

1850-439: The other hand, some operators argue that their customers would have wanted them to manage the experience and, on such a constrained device, avoid giving access to too many services. Under-specification of terminal requirements: The early WAP standards included many optional features and under-specified requirements, which meant that compliant devices would not necessarily interoperate properly. This resulted in great variability in

1900-430: The packet loss as network congestion, unlike TCP. WAP sites are written in WML, a markup language. WAP provides content in the form of decks, which have several cards: decks are similar to HTML web pages as they are the unit of data transmission used by WAP and each have their own unique URL, and cards are elements such as text or buttons which can be seen by a user. WAP has URLs which can be typed into an address bar which

1950-612: The packet up to the inter-network protocol, which, on recognizing that B is not the final destination, will again invoke lower-level functions. This time, the cable protocol is used to send the data to C . There, the received packet is again passed to the upper protocol, which (with C being the destination) will pass it on to a higher protocol or application on C . In practical implementation, protocol stacks are often divided into three major sections: media, transport, and applications. A particular operating system or platform will often have two well-defined software interfaces: one between

2000-518: The pages to their capabilities based on a provided User-Agent type. However, the development kits which existed for WML did not provide this capability. It quickly became nearly impossible for site hosts to determine if a request came from a mobile device or from a larger more capable device. No useful profiling or database of device capabilities were built into the specifications in the unauthorized non-compliant products. Neglect of content providers by wireless carriers: Some wireless carriers had assumed

2050-594: The primary language of the WAE is Wireless Markup Language (WML). In WAP 2.0, the primary markup language is XHTML Mobile Profile . WAP Push was incorporated into the specification to allow the WAP content to be pushed to the mobile handset with minimal user intervention. A WAP Push is basically a specially encoded message which includes a link to a WAP address. WAP Push was specified on top of Wireless Datagram Protocol (WDP); as such, it can be delivered over any WDP-supported bearer, such as GPRS or SMS. Most GSM networks have

Wireless Application Protocol - Misplaced Pages Continue

2100-409: The problem of the inadequacy of TCP over high-packet-loss networks. Read Networks And Computers Book by Tanenbaum Protocol suite The protocol stack or network stack is an implementation of a computer networking protocol suite or protocol family . Some of these terms are used interchangeably but strictly speaking, the suite is the definition of the communication protocols , and

2150-532: The second part being either a Service Indication or a Service Loading . The POST contains at a minimum the URL being posted to (this is not standard across different PPG vendors), and the content type. An example of a PPG POST: The PAP XML contains at the minimum, a <pap> element, a <push-message> element, and an <address> element. An example of a PAP XML: --someboundarymesg Content-Type: application/xml The important parts of this PAP message are

2200-531: The technological limitations of its time, it succeeded in its goal of providing simple and custom-designed content at a time where most people globally did not have regular internet access. Technical criticisms included: The idiosyncratic WML language cut users off from the conventional HTML Web, leaving only native WAP content and Web-to-WAP proxi-content available to WAP users. Many wireless carriers sold their WAP services as "open", in that they allowed users to reach any service expressed in WML and published on

2250-501: The time of its introduction, leading users to expect WAP to have the performance of fixed (non-mobile) Internet access . BT Cellnet , one of the UK telecoms , ran an advertising campaign depicting a cartoon WAP user surfing through a Neuromancer -like "information space". In terms of speed, ease of use, appearance and interoperability, the reality fell far short of expectations when the first handsets became available in 1999. This led to

2300-529: The topmost layers. Imagine three computers: A , B , and C . A and B both have radio equipment and can communicate via the airwaves using a suitable network protocol (such as IEEE 802.11 ). B and C are connected via a cable, using it to exchange data (again, with the help of a protocol, for example Point-to-Point Protocol ). However, neither of these two protocols will be able to transport information from A to C , because these computers are conceptually on different networks. An inter-network protocol

2350-622: The traditional Web sites and ISPs . According to the Mobile Data Association, WAP traffic in the UK doubled from 2003 to 2004. By the year 2013, WAP use had largely disappeared. Most major companies and websites have since retired from the use of WAP and it has not been a mainstream technology for web on mobile for a number of years. Most modern handset internet browsers now support full HTML, CSS, and most of JavaScript , and do not need to use any kind of WAP markup for webpage compatibility. The list of handsets supporting HTML

2400-558: The user of the device. The notification will typically be a text string with a URL link. Note that only a notification is pushed to the device; the device must do something with the notification in order to download or view the content associated with it. A push message is sent as an HTTP POST to the Push Proxy Gateway. The POST will be a multipart XML document, with the first part being the PAP (Push Access Protocol) Section and

2450-601: The various wireless technologies in a standardised protocol. In 2002, the WAP Forum was consolidated (along with many other forums of the industry) into Open Mobile Alliance (OMA). The first company to launch a WAP site was Dutch mobile phone operator Telfort BV in October 1999. The site was developed as a side project by Christopher Bee and Euan McLeod and launched with the debut of the Nokia 7110 . Marketers hyped WAP at

2500-408: The wide usage of sardonic phrases such as "Worthless Application Protocol", "Wait And Pay", and WAPlash. Between 2003 and 2004 WAP made a stronger resurgence with the introduction of wireless services (such as Vodafone Live! , T-Mobile T-Zones and other easily accessible services). Operator revenues were generated by transfer of GPRS and UMTS data, which is a different business model than used by

#754245