The WAP Roadmap. Short Term Goals for WAP

Similar documents
Wireless Access Protocol(WAP) architecture

The Migration to Ipv6

WAP via ORBCOMM. Andrew R Cardoza, Sias Mostert.

Wireless Internet: layers 3,4,5. Wireless Internet: Layers 3,4,5 Case Study: WAP. WAP: Wireless Application Protocol

Page 1. WAP Overview. An overview of the. Wireless Application Protocol to the IAB. Copyright IBM 2000

Glossary 1. ARPU or Average Revenue per User A method of measuring revenue associated with the delivery of mobile commerce services by MNOs.

Outline. CS5984 Mobile Computing HTTP. HTTP (especially 1.0) Problems 1/2. Dr. Ayman Abdel-Hamid, CS5984. Wireless Web.

M.SARAVANA KARTHIKEYAN

WAP. Bringing the internet to you. Cynthia Luk Marianne Morris Harvey Wong. 4 April, 2002 CMPUT 499

Mobile Wireless working Group

Enabling the Wireless Internet

Basic Profile 1.0. Promoting Web Services Interoperability Across Platforms, Applications and Programming Languages

Enabler Release Definition for Smartcard-Web-Server

WAP TM Architecture WAP-210-WAPArch Proposed Version 17-October-2000

Re: ENERGY STAR Telephony Draft 2 Version 3.0 Telephony Test Method and Data Call

GRAPHICAL SIMULATION OF WIRELESS APPLICATION PROTOCOL

WAP Provisioning Architecture Overview

WIRELESS INTERNET USABILITY AND INTEROPERABILITY

Lecture 11C Mobile Commerce

Chapter 3. Technology Adopted. 3.1 Introduction

Mission Critical Mobile Broadband:

Mobile Devices & Wireless Security. Jack Jania Director Field Marketing Mobile Communications

ITU-T Y Next generation network evolution phase 1 Overview

Wireless Profiled HTTP

WIRELESS APPLICATION PROTOCOL

Dominique Carrega, Emmanuel Fournier, Hervé Muyal (Tecsi).

WIRELESS APPLICATION PROTOCOL (WAP) AND MOBILE WIRELESS ACCESS

GRIDS INTRODUCTION TO GRID INFRASTRUCTURES. Fabrizio Gagliardi

09. Mobile Commerce. Contents. Mobile Computing and Commerce

Govt. of Karnataka, Department of Technical Education Diploma in Computer Science Sixth Semester. Contact Hrs / week: 4 Total hrs: 64

TC32 presentation to ECMA General Assembly, Edinburgh, 22nd June 2000

European Telecommunications Standards Institute. Grid Specialist Task Force. Interoperability Gap Analysis

Customer Managed Connectivity - Milan

Proof of concept AS4. Version 1 Revision ITC-KG AS4 Proof of Concept 16 January 2014 Draft INT

Enabling the Mobile Service Access

Developing Mobile Applications

Canada Life Cyber Security Statement 2018

einfrastructures Concertation Event

Recommendations on residual issues relevant to ecall

ConCert FAQ s Last revised December 2017

Architecture Proposal for an Internet Services Charging Platform

(5) Affiliation (10) XML (15) Web Augmentation (20) Gateways. (4) Kernel (9) ES test (14) SSL. (1) Portal (6) EDI (11) Web Directories (16) W3C

The International Intelligent Network (IN)

Virtual Private Networks (VPNs)

WAP/ WML : Wireless Protocol wireless protocol

WAN Application Infrastructure Fueling Storage Networks

GSM Association (GSMA) Mobile Ticketing Initiative

Class Conformance Requirements

3GPP TS V4.2.0 ( )

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

CITEL s s Focus on Cybersecurity and Critical Infrastructure Protection CITEL

R&D White Paper WHP 018. The DVB MHP Internet Access profile. Research & Development BRITISH BROADCASTING CORPORATION. January J.C.

Mobile Commerce. Electronic Commerce

ENTERPRISE MOBILITY TRENDS

WIRELESS APPLICATION PROTOCOL (WAP)

Standardization mandate addressed to CEN, CENELEC and ETSI in the field of Information Society Standardization

Multimedia Messaging Service Architecture Overview

Meltem Özturan misprivate.boun.edu.tr/ozturan/mis515

IPv6 Task Force - Phase II. Welcome

What is NGN? Hamid R. Rabiee Mostafa Salehi, Fatemeh Dabiran, Hoda Ayatollahi Spring 2011

WAP WINA Process Document WAP-212-WINAProcess Version 04-Feb-2002

Overview. M-commerce vs. E-commerce

Contents. Enterprise Solution 04. Why Samsung? 05 WLAN 06. Voice Solution 08. Mobile Unified Communications 09. Enterprise Security 10

Home Gateway Enabling Evolution of Network Services

SCOTTISH PARLIAMENT WEB AND ONLINE ROADMAP PROJECT (INCLUDING DEVELOPING A NEW IMPROVED WEBSITE PRESENCE FOR THE SCOTTISH PARLIAMENT)

Internet Standards for the Web: Part II

ETSI TR V1.1.1 ( )

Table of Contents. WAP Process. WAP Architecture. Wireless Transport Protocol Overview. Wireless Session Protocol Overview

Cisco Unified Presence 8.0

Introduction to iscsi

GSME proposals regarding mobile theft and IMEI security

Introducing Avaya SDN Fx with FatPipe Networks Next Generation SD-WAN

ETSI TS V (201

ETSI Zero touch network and Service Management (ZSM)

The Go4IT project. Toward a TTCN-3 open environment for IPv6 protocols testing. Project identity card

ETSI Zero touch network and Service Management (ZSM)

SyncML DM: A SyncML Protocol for Device Management

WAP WTAI (GSM) Version 08-Nov-1999

Charted Engineer, Fellow I.E.E. VP Standards & Fora Siemens Mobile Communications S.p.A. Italy. ITU-T SSG Vice Chairman

Custom Connect. All Area Networks. customer s guide to how it works version 1.0

SD-WAN Solution How to Make the Best Choice for Your Business

TN3270 AND TN5250 INTERNET STANDARDS

Submission. to the. Australian Communications and Media Authority. on the. Planning for mobile broadband within the 1.

SyncML Overview. Noel Poore, Psion Computers PLC

Analysis of Effectiveness of Open Service Architecture for Fixed and Mobile Convergence

Electronic Commerce Working Group report

Workshop on the IPv6 development in Saudi Arabia 8 February 2009; Riyadh - KSA

ETSI LI Standards Overview

ETSI TS V5.0.0 ( )

3G Wireless. from an Operator s Perspective. David T. Shimozawa Technology Development. Page 1. June 2001

Computer Networks 2012/2013. Introduction part 1 (01) Dr. Tanir Ozcelebi. Thanks to A. Leon-Garcia & I. Widjaja, & I. Radovanovic & A. S.

CDMA2000 Workshop. Paul Le Rossignol. Nortel Networks, OMA Board Director

Glossary. xii. Marina Yue Zhang and Mark Dodgson Downloaded from Elgar Online at 02/04/ :16:01PM via free access

EUROPEAN COMMISSION Enterprise Directorate-General

DELIVERING MULTIMEDIA CONTENT FOR THE FUTURE GENERATION MOBILE NETWORKS

The challenges, opportunities and setting the framework for 5G EMF and Health

3G Network Convergence

ISO INTERNATIONAL STANDARD. Information and documentation Library performance indicators

WAP Push Message Version 16-August-1999

On Accessing GSM-enabled Mobile Sensors

Transcription:

The WAP Roadmap Authors: Alastair Angwin, WAP Specification Committee / IBM UK Laboratories (alastair_angwin@uk.ibm.com) Bill Coan, WAP Specification Committee / AT&T Wireless Services / Global Operators Forum (bill.coan@attws.com) Contributors: WAP Executive and Specification Committees, Expert and Working Groups Draft Version 0.8, 31 December 1998 The Wireless Application Protocol (WAP) Forum is an industry group dedicated to the goal of enabling sophisticated telephony and information services on hand-held wireless devices such as mobile telephones, pagers, personal digital assistants (PDAs) and other wireless terminals. Recognising the value and utility of the World Wide Web (WWW) architecture, the WAP Forum has chosen to align certain components of its technology very tightly with the Internet and the WWW. The WAP specifications extend and leverage mobile networking technologies (such as digital data networking standards) and Internet technologies (such as IP, HTTP, XML, URLs, scripting and other content formats) to enable sophisticated telephony and information services for hand-held wireless devices. The initial thrust of the WAP Forum has been to deliver a pragmatic set of specifications, thereby enabling potential suppliers to develop WAP enabled products and services for early deployment. The WAP version 1 specifications achieved this goal and were made publicly available in April 1998. These specifications provide the basic functions required for the deployment of WAP clients and applications. However, the work of the WAP Forum is not finished. This WAP Forum has been actively working to ensure initial deployments meet the needs of users and service providers by ensuring interoperable clients, infrastructure and content over a variety of data networks. Further, the WAP Forum recognises that the WAP specifications must evolve as underlying technology changes and user expectations grow. The WAP Forum intends to address these matters through the WAP Roadmap. There are a number of short long- term goals in the WAP Roadmap. These are described in the remainder of this document. Short Term Goals for WAP The short-term direction of the WAP Forum is simple - to deliver the specifications necessary to enhance deployment. This includes the features necessary to deliver a critical mass of bearer independent applications, and to create multiple-vendor handset, server, and application interoperability on any network environment. The WAP Forum is working on a number of items with the intent to deliver updated specifications addressing the requirements of near-term WAP deployments. The main areas of

effort are: Corrections, clarifications and revisions to the existing specifications. Technical specifications of the size and complexity of WAP version 1 may contain omissions and require clarifications. The WAP working groups have, subsequent to the release of version 1, clarified and corrected the existing specifications as such items are found during implementation of WAP products. The corrigenda will be integrated into the specifications as part of a general update of the released specifications. Also, a process of issuing corrigenda will be established for the future. Interoperability. It is important that all WAP client devices, e.g., phones, pagers and smart phones, interact with WAP servers regardless of which commercial supplier provides a given piece of the end-to-end solution. The WAP specification provides flexibility for suppliers to tailor their implementation to suit their perceived customer needs. This in turn makes interoperability a key deliverable from the WAP Forum. The working groups have determined most of the salient features in each specification necessary for compliance. Some additional work is being undertaken to formalise the processes and requirements of interoperability. The outcome of this interoperability work will be a set of compliance criteria, a combination of static checks and dynamic tests, ready for verifying WAP product implementations and deployments. Subsequent efforts will extend this effort to test suites and test house recommendations. WAP will create the specifications and processes necessary for the delivery of interoperable products based on WAP technologies. New features: Security Enhancements. Applications such as e-business, e-commerce and e-banking, where potentially sensitive information is communicated, require particular attention to security. The WAP Forum has previously specified the Wireless Transport Layer Security protocol, permitting transport-level user authentication and encryption of data between the WAP client and the WAP server. Smart card technology is widely used, and provides a means to enhance security. Therefore, WAP will integrate SIM and smart card into the WAP security model to benefit from this technology. Additional use cases have been identified where enhancements to the WAP security model are required to ensure the end-to-end security of user data. WAP will create an end-to-end security model, allowing the secure and private transmission of data between the mobile terminal and the network application server.

Internationalisation. The WAP architecture has addressed many aspects of national language support in version 1, but it has been recognised that the focus has been on European-based character sets and cultural conventions. The WAP Forum recognises the importance of addressing the issues associated with different languages and cultures and is actively working on these issues. WAP will extend its specifications to meet the needs of the Asian cultures in the short term and others as soon as the technical issues have been fully identified. Mobile network bearer support. WAP intends to support all mobile networks, and their associated data bearer services, for which there is identified need warranting the protocol development effort. At the time of the version 1 release, WAP included support for PDC, TDMA (IS-136), GSM, IPv4, CDPD, FLEX, ReFLEX, and iden. Efforts since this release have addressed other networks, bearers and optimisations, all of which will be released formally as soon as approved, followed by inclusion into the next formal release of the specification suite. WAP will continue to identify any additional necessary WDP adaptations and optimisations, and will publish these specifications. Operations and administration. The WAP Forum will address issues of provisioning and billing to ensure successful deployment and operation of services. For the GSM technology, WAP will provide for the storage of microbrowser configuration data in the SIM. Telephony extensions. The WAP specifications released in version 1 did not provide a complete specification of WAP telephony interfaces. The WAP working groups will complete this specification, and an early public release of the specification is anticipated to encourage the realisation of implementations. The WAP Wireless Telephony Application Interface (WTAI) will provide interfaces between the mobile phones telephony functions and WAP Application Environment, allowing the development of sophisticated enhanced telephony applications. Examples services that could be developed using the WTAI include enhanced integrated voice/data services, such as intelligent mailboxes, unified messaging, etc. WAP will complete the first generation of telephony interfaces, and will enable the delivery of WTA applications. Wireless Applications Environment (WAE) functional extensions. Several use cases have identified the need for functional extensions of the application environment. Identified requirements include:

Network initiated content delivery. Network initiated content delivery provides a push application model, whereby new information and/or events in the network are communicated to the client. User agent caching. User agent caching enables better application performance and reduced network loading. Asynchronous application model. The asynchronous application model provides a responsive user experience when operating on high latency bearers or out of network coverage. User agent profiles. User agent profiles enables the generation of device tailored content through knowledge of device capabilities. External working relationships. WAP recognises that proactive working relationships with external organisations are necessary. WAP intends to further working relationships with W3C, IETF, ETSI, ARIB, TIA and other organisations that are active in the area of evolving related technical standards. The WAP Forum intends to deliver the revised WAP version 1.x specifications in April 1999. Longer Term Goals for WAP The technology of wireless networks, mobile phones and the Internet is advancing rapidly. The WAP Forum has long recognised the need for WAP to address the current networks and bearer services, which will be available for some time in the future. In addition, WAP has also recognised the need to ensure an evolutive path to address future developments in networking, handset technologies and applications (e.g., 3rd Generation networks with higher speed connections, packet based services, new network services, future Web content standards, new Internet protocols and much more). For example, even with advances in network technology, there is still a need for cost effective, efficient and reliable use of networks and end user independent access to information services. To achieve these goals, WAP intends to address more fully the issues associated with: E-commerce or e-business, providing secure end-to-end links between client and application whether the application is situated somewhere in the Internet or as an extension of the corporate Intranets. Accessing richer content types to permit WAP to take advantage of emerging Internet developments, more advanced mobile devices and evolving user expectations.

Convergence of WAP and the evolution of the W3C, IETF and other initiatives working on the evolution of Internet standards. The WAP Forum will actively work with these organisations to achieve the WAP Forum s goals using these standards, e.g. HTTP-NG, HTML-NG, ECMAScript, etc. New networks and bearer services and the opportunities these offer, e.g., third-generation wireless networks and next generation service environments. Conclusion The WAP Forum has delivered a pragmatic first release of specifications, and continues with a program to deliver the specifications necessary to permit the successful deployment of WAPbased devices, services and access in the near future. The WAP Forum is also acutely aware of the rapid developments in the fields of the Internet and mobility. It intends to enhance WAP to take advantage of these developments whilst still keeping to its original goals of providing integrated access to wireless telephony and information services over a wide range of networks, network bearers, and device capabilities.