|
|
| (3 intermediate revisions by one user not shown) |
| Line 11: |
Line 11: |
| | | | |
| | The Japanese i-mode system offers another major competing wireless data protocol. | | The Japanese i-mode system offers another major competing wireless data protocol. |
| | + | |
| | + | * WAP supports most wireless networks. These include CDPD, CDMA, GSM, PDC, PHS, TDMA, FLEX, ReFLEX, iDEN, TETRA, DECT, DataTAC, and Mobitex. |
| | + | |
| | + | * WAP is supported by all operating systems. Ones specifically engineered for handheld devices include PalmOS, EPOC, Windows CE, FLEXOS, OS/9, and JavaOS. |
| | + | |
| | + | WAP is supported by all operating systems. Ones specifically engineered for handheld devices include PalmOS, EPOC, Windows CE, FLEXOS, OS/9, and JavaOS. |
| | + | |
| | + | == WML language == |
| | + | WAP is not a language and therefore is not comparable to HTML, however, most WAP implementations use the language [[WML]]. Although WAP supports HTML and XML, the WML language (an XML application) is specifically devised for small screens and one-hand navigation without a keyboard. WML is scalable from two-line text displays up through graphic screens found on items such as smart phones and communicators. WAP also supports WMLScript. It is similar to JavaScript, but makes minimal demands on memory and CPU power because it does not contain many of the unnecessary functions found in other scripting languages. |
| | + | |
| | + | WAP and WML lack good standards specifications, so there are variances across the industry. Certain WML web pages may render best under specific manufacturers phones, which site to which phone varies. |
| | | | |
| | ==Technical specifications== | | ==Technical specifications== |
| Line 39: |
Line 50: |
| | Finally, one can think of [[Wireless Session Protocol|WSP]] initially as a compressed version of [[HTTP]]. | | Finally, one can think of [[Wireless Session Protocol|WSP]] initially as a compressed version of [[HTTP]]. |
| | | | |
| − | 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. | + | 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. |
| | | | |
| | ===Wireless Application Environment (WAE)=== | | ===Wireless Application Environment (WAE)=== |
| | The WAE space defines application-specific markup languages. | | The WAE space defines application-specific markup languages. |
| | | | |
| − | For WAP version 1.X, the primary language of the WAE is [[Wireless Markup Language]] (WML). In WAP 2.0, the primary markup language is [[XHTML Mobile Profile]]. | + | For WAP version 1.X, the primary language of the WAE is Wireless Markup Language (WML). In WAP 2.0, the primary markup language is XHTML Mobile Profile. |
| − | | + | |
| − | ==History==
| + | |
| − | The [[WAP Forum]] dates from 1997. It aimed primarily to bring together the various wireless technologies in a standardised protocol.<ref>
| + | |
| − | {{cite web |title= A brief History of WAP |work= HCI blog |date= December 8, 2004 |url= http://inspiredbloggers.blogspot.com/2004/12/brief-history-of-wap_110252445307049372.html |accessdate= August 5, 2011 }}</ref>
| + | |
| − | | + | |
| − | In 2002 the WAP Forum was consolidated{{By whom|date=October 2009}} (along with many other forums of the industry) into [[Open Mobile Alliance]] (OMA]).<ref>[http://www.openmobilealliance.org/AboutOMA/FAQ.aspx OMA: Frequently Asked Questions]</ref>
| + | |
| − | | + | |
| − | ===WAP Push===
| + | |
| − | [[File:WAP Push Process.jpg|thumb|300px|WAP Push Process]]
| + | |
| − | | + | |
| − | WAP Push was incorporated into the specification to allow WAP content to be pushed to the mobile handset with minimum user intervention. A WAP Push is basically a specially encoded message which includes a link to a WAP address.<ref>[http://www.mxtelecom.com/uk/mmsg/wap MX Telecom: WAP Push]</ref>
| + | |
| − | | + | |
| − | WAP Push was specified on top of [[WAP Datagram Protocol]] (WDP); as such, it can be delivered over any WDP-supported bearer, such as GPRS or SMS.<ref name="wap_push">[http://developer.openwave.com/docs/wappush_tech_overview.pdf Openwave: WAP Push Technology Overview]{{dead link|date=June 2011}}<!--according to http://wapreview.mobi/3733 Openwave pulled all developer support from its site by April 2009--></ref> Most GSM networks have 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]]).<ref name="wap_push"/> A variant, known as WAP Push SL ([[Service Loading]]), directly opens 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).<ref name="wap_push"/>
| + | |
| | | | |
| | ===WAP 2.0=== | | ===WAP 2.0=== |
| − | A re-engineered 2.0 version was released in 2002. It uses 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. | + | A re-engineered 2.0 version was released in 2002. It uses 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), 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 ([[Cascading Style Sheets|CSS]]) called WAP CSS is supported by XHTML MP. | + | Mobile devices process XHTML Mobile Profile (XHTML MP), 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. |
| | | | |
| | ==Commercial status== | | ==Commercial status== |
| − | ===Europe===
| |
| − | Marketers [[hyperbole|hyped]] WAP at the time of its introduction,<ref>[http://www.computing.co.uk/vnunet/analysis/2131787/wap-call-unanswered Will Wap's call go unanswered?] vnunet.com, 2 June 2000</ref> leading users to expect WAP to have the performance of fixed (non-mobile) [[Internet access]]. [[BT Cellnet]], one of the UK [[telephone company|telecoms]], ran an advertising campaign depicting a cartoon WAP user ''surfing'' through a ''[[Neuromancer]]''-like "information space".<ref>[http://networks.silicon.com/mobile/0,39024665,11020593,00.htm Silicon.com: BT Cellnet rapped over 'misleading' WAP ads] Published 3 November 2000, retrieved 17 September 2008</ref> 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.<ref>http://press.nokia.com/PR/199902/777256_5.html Nokia 7110 Press Release</ref><ref>http://www.filibeto.org/mobile/firmware.html Nokia 7110 first public firmware revision date</ref> This led to the wide usage of sardonic phrases such as "Worthless Application Protocol",<ref>[http://www.theglobeandmail.com/servlet/story/RTGAM.20050915.gtsripbutters15/BNStory/Technology/Troubleshooter The Globe and Mail: "Survivor's guide to wireless wonkery", 23 September 2005]</ref> "Wait And Pay",<ref>[http://www.itweb.co.za/sections/interviews/sammichel/michel001114.asp IT Web: "A RIVR runs through it", 14 November 2000]</ref> and so on.
| |
| | | | |
| − | 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 that used by the traditional Web sites and [[ISP]]s. According to the Mobile Data Association, WAP traffic in the UK doubled from 2003 to 2004.<ref>[http://www.builderau.com.au/news/soa/UK-WAP-usage-doubles-in-12-months/0,339028227,339130400,00.htm Builder.au 2004/08/10: UK WAP usage doubles in 12 months]</ref>
| + | The adoption of WAP in the United States suffered because many cell phone providers required separate activation and additional fees for data support, and also because telecommunications companies have sought to limit data access to only approved data providers operating under license of the signal carrier. |
| | | | |
| − | As of 2013, WAP use has largely disappeared. 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 is extensive, and includes all Android handsets, all Blackberry devices, all versions of the iPhone handset, all devices running Windows Phone, and many Nokia handsets. Most major companies and websites have since retired from the use of WAP and it has not been the mainstream technology for web on mobile for a number of years.{{citation needed |date= August 2011}}
| + | In recognition of the problem, the FCC issued an order on 31 July 2007 which mandated that licensees of the 22-megahertz wide "Upper 700 MHz C Block" spectrum will 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. |
| − | | + | |
| − | ===Asia===
| + | |
| − | Unlike in Europe, WAP has seen huge success in Japan. While the largest operator [[NTT DoCoMo]] has famously disdained WAP in favor of its in-house system [[i-mode]], rival operators [[KDDI]] ([[au (mobile phone operator)|au]]) and [[SoftBank Mobile]] (previously [[Vodafone Japan]]) have both successfully deployed WAP technology. In particular, <!--J-Phone's [[Sha-Mail]] picture mail and Java ([[JSCL]]) services{{Citation needed|date=May 2011}}, as well as -->([[au (mobile phone operator)|au]])'s chakuuta/chakumovie (ringtone song/ringtone movie) services are based on WAP. After being shadowed by the initial success of i-mode, the two smaller Japanese operators have been gaining market share from DoCoMo since Spring 2001.<ref>[http://www.icmrindia.org/business%20Updates/micro%20casestudies/Business%20Strategy/MCBS0031.htm IMCR: NTT DoCoMo Inc.: Leadership Position in Japanese Mobile Market under Threat?] Retrieved 17 September 2008</ref>
| + | |
| − | | + | |
| − | ===USA===
| + | |
| − | The adoption of WAP in the [[United States of America|US]] suffered because many cell phone providers required separate activation and additional fees for data support, and also because telecommunications companies have sought to limit data access to only approved data providers operating under license of the signal carrier.{{citation needed |date= August 2011}}
| + | |
| − | | + | |
| − | In recognition of the problem, the U.S. [[Federal Communications Commission]] (FCC) issued an order on 31 July 2007 which mandated that licensees of the 22-megahertz wide "Upper 700 MHz C Block" spectrum will 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.<ref>U.S. Federal Communications Commission.[http://www.fcc.gov/073107/700mhz_news_release_073107.pdf "FCC Revises 700 MHz Rules To Advance Interoperable Public Safety Communications And Promote Wireless Broadband Deployment"], July 31, 2007. Accessed October 8, 2007.</ref>{{Dead link|date=March 2010}} <ref>Alternate link to [http://www.govtech.com/gt/128168 "FCC Revises 700 MHz Rules To Advance Interoperable Public Safety Communications And Promote Wireless Broadband Deployment"]</ref> | + | |
| | | | |
| | ===Spin-off technologies=== | | ===Spin-off technologies=== |
| − | Spin-off technologies, such as [[Multimedia Messaging Service]] (MMS), a combination of WAP and SMS, have further driven the protocol. An enhanced appreciation of device diversity, supported by the concomitant changes to WAP content to become more device-specific rather aiming at a lowest common denominator, allowed for more usable and compelling content. As a result, the adoption rate of WAP technology is rising.{{Citation needed|date=October 2009}} | + | Spin-off technologies, such as Multimedia Messaging Service (MMS), a combination of WAP and SMS, have further driven the protocol. An enhanced appreciation of device diversity, supported by the concomitant changes to WAP content to become more device-specific rather aiming at a lowest common denominator, allowed for more usable and compelling content. As a result, the adoption rate of WAP technology is rising. |
| | | | |
| − | ==Criticism==
| |
| − | Commentators have criticized several aspects of [[Wireless Markup Language]] (WML) and WAP. Technical criticisms include:
| |
| − | *The [[idiosyncrasy|idiosyncratic]] WML language: WML cut users off from the conventional [[HTML]] Web, leaving only native WAP content and Web-to-WAP proxi-content available to WAP users. However, others argue{{Who|date=June 2010}} that technology at that stage would simply not have been able to give access to anything but custom-designed content which was the sole purpose of WAP and its simple, reduced complexity interface as the citizens of many nations are not connected to the web at the present time and have to use government funded and controlled portals to WAP and similar non-complex 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 the actual behavior of phones, principally because WAP-service implementers and mobile-phone manufacturers did not{{Citation needed|date=October 2009}} 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; others would downright crash. The user interface of devices was also underspecified: as an example, accesskeys (e.g., 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 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.
| |
| − | *Lack of good authoring tools: The problems above might have succumbed in the face of a WML authoring tool that would have allowed content providers to easily publish content that would interoperate flawlessly with many models, adapting the pages presented to the [[User-Agent]] type. However, the development kits which existed did not provide such a general capability. Developing for the web was easy: with a text editor and a web browser, anybody could get started, thanks also to the forgiving nature of most desktop browser rendering engines. By contrast, the stringent requirements of the WML specifications, the variability in terminals, and the demands of testing on various wireless terminals, along with the lack of widely available desktop authoring and emulation tools, 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 is becoming easier to create content, accessible by many new devices.
| |
| − | *Lack of user agent profiling tools: It quickly became nearly impossible for web 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.{{citation needed |date= August 2011}}
| |
| | | | |
| − | Other criticisms address the wireless carriers' particular implementations of WAP:
| + | ==References== |
| | + | * Wikipedia - http://en.wikipedia.org/wiki/Wireless_Application_Protocol - Wikipedia was the source for the information on this page prior to contributor modification. |
| | | | |
| − | *Neglect of content providers: Some wireless carriers had assumed 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 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 [http://www.gallery.fr/ Gallery] service in France.
| + | == Related == |
| − | *Lack of openness: Many wireless carriers sold their WAP services as "open", in that they allowed users to reach any service expressed in WML and published on 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 (web)|form]] on a page linked off the hard coded home page page was provided. It makes it easier for carriers to implement filtering of off deck WML sites by URLs or to disable 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 [[Uniform Resource Locator|URL]]s on a phone keyboard, most users would give up going "off portal" or out of the [[Walled garden (media)|walled garden]]; by not letting third parties put their own entries on the operators' wireless portal, some{{Who|date=October 2009}} contend that operators cut themselves off from a valuable opportunity. On the other hand, some operators{{Which?|date=October 2009}} 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.{{citation needed |date= August 2011}}
| + | |
| | | | |
| − | ==Protocol design lessons from WAP==
| + | * [[Text Mode Web Browsers]] |
| − | 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. {{As of| 2009}} it continues with a considerable user base. The later versions of WAP, primarily targeting the United States market, were designed{{By whom|date=October 2009}} 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.
| + | * [[Apache Web Server]] |
| | + | * [[PHP Function Reference]] |
| | | | |
| − | Considerable discussion has addressed the question whether the WAP protocol design was appropriate. Some{{Who|date=June 2010}} have suggested that the bandwidth-sparing simple interface of [[Gopher (protocol)|Gopher]] would be a better match for mobile phones and Personal digital assistants (PDAs).<ref>[http://www.wired.com/news/technology/0,1282,62988,00.html Wired News: Gopher: Underground Technology]</ref>
| + | |
| − | | + | |
| − | The initial design of WAP specifically aimed at protocol independence across a range of different protocols (SMS, IP over [[Point-to-Point Protocol|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 [[User Datagram Protocol|UDP]] to attempt to solve the problem of the inadequacy of TCP over high-packet-loss networks.{{citation needed |date= August 2011}}
| + | |
| − | | + | |
| − | ==See also==
| + | |
| − | * [[.mobi]]
| + | |
| − | * [[i-mode]]
| + | |
| − | * [[Microbrowser]]
| + | |
| − | * [[Mobile development]]
| + | |
| − | * [[Mobile web]]
| + | |
| − | * [[RuBee]]
| + | |
| − | * [[WAP Identity Module]]
| + | |
| − | * [[Wireless Internet Protocol]]
| + | |
| − | * [[Wireless transaction protocol]]
| + | |
| − | * [[WURFL]]
| + | |
| − | * [[Wikipedia:WAP access|Wikipedia access via WAP]]
| + | |
| − | | + | |
| − | ==References==
| + | |
| − | {{Reflist|30em}}
| + | |
| | | | |
| − | ==External links==
| + | |
| − | * [http://www.openmobilealliance.org/ Open Mobile Alliance]
| + | |
| − | * [http://www.openmobilealliance.org/Technical/wapindex.aspx OMA – Wireless Application Protocol Downloads] (specification documents in PDF format)
| + | |
| | | | |
| − | {{Mobile phones}}
| + | [[Category:Android]] |
| − | {{Open Mobile Alliance standards}}
| + | [[Category:Verizon]] |
| | + | [[Category:Mobile Phones]] |
| | + | [[Category:Computer Technology]] |
| | + | [[Category:Programming]] |
| | + | [[Category:HTML]] |
| | | | |
| − | {{FOLDOC}}
| |
| | | | |
| − | [[Category:Open Mobile Alliance standards]]
| + | Keywords: VZW Verizon Wireless ESN Android |
| − | [[Category:Internet protocols]]
| + | |
| − | [[Category:OSI protocols]]
| + | |
| − | [[Category:Mobile telecommunications standards]]
| + | |
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 such as:
The Japanese i-mode system offers another major competing wireless data protocol.
WAP is supported by all operating systems. Ones specifically engineered for handheld devices include PalmOS, EPOC, Windows CE, FLEXOS, OS/9, and JavaOS.
WAP is not a language and therefore is not comparable to HTML, however, most WAP implementations use the language WML. Although WAP supports HTML and XML, the WML language (an XML application) is specifically devised for small screens and one-hand navigation without a keyboard. WML is scalable from two-line text displays up through graphic screens found on items such as smart phones and communicators. WAP also supports WMLScript. It is similar to JavaScript, but makes minimal demands on memory and CPU power because it does not contain many of the unnecessary functions found in other scripting languages.
WAP and WML lack good standards specifications, so there are variances across the industry. Certain WML web pages may render best under specific manufacturers phones, which site to which phone varies.
The WAP standard described a protocol suite 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 WAP Datagram Protocol (WDP), functions as an adaptation layer that makes every data network look a bit like User Datagram Protocol (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 Point-to-Point Protocol (PPP) on top of a circuit-switched data connection, WDP is in fact exactly UDP.
Wireless transaction protocol (WTP) provides transaction support (reliable request/response) adapted to the wireless world. WTP supports more effectively than Transmission Control Protocol (TCP) the problem of packet loss, which occurs commonly in 2G wireless technologies in most radio conditions, but is misinterpreted by TCP as network congestion.
For WAP version 1.X, the primary language of the WAE is Wireless Markup Language (WML). In WAP 2.0, the primary markup language is XHTML Mobile Profile.
A re-engineered 2.0 version was released in 2002. It uses 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), 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.
The adoption of WAP in the United States suffered because many cell phone providers required separate activation and additional fees for data support, and also because telecommunications companies have sought to limit data access to only approved data providers operating under license of the signal carrier.
In recognition of the problem, the FCC issued an order on 31 July 2007 which mandated that licensees of the 22-megahertz wide "Upper 700 MHz C Block" spectrum will 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.
Spin-off technologies, such as Multimedia Messaging Service (MMS), a combination of WAP and SMS, have further driven the protocol. An enhanced appreciation of device diversity, supported by the concomitant changes to WAP content to become more device-specific rather aiming at a lowest common denominator, allowed for more usable and compelling content. As a result, the adoption rate of WAP technology is rising.
