WAP General Formats Document WAP-188-WAPGenFormats Version 10-Jul-2001

Similar documents
WAP-Sync-Spec. Data Synchronisation Specification Version 30-May Wireless Application Protocol WAP-234-SYNC a

Class Conformance Requirements

Specification Information Note

Cache Operation. Version 31-Jul Wireless Application Protocol WAP-175-CacheOp a

Specification Change Document

Reference Release Definition for Parlay/OSA(Open Service Access) In OMA Service Environment (PIOSE)

Enabler Release Definition for Smartcard-Web-Server

OMA Push Management Object

Lightweight Machine to Machine Architecture

Specification Information Note

Enabler Release Definition for Parlay Service Access

Enabler Validation Plan for the RESTful Network API for OMA Push

Lightweight Machine to Machine Architecture

Standardized Connectivity Management Objects HTTP Proxy Parameters For use with OMA Device Management

Specification Information Note

Wireless Profiled HTTP

Standardized Connectivity Management Objects WAP Proxy Parameters For use with OMA Device Management

OMA Device Management Tree and Description Serialization

Enabler Release Definition for Converged Personal Network Service

Location Protocols. Version 12-Sept Wireless Application Protocol WAP-257-LOCPROT a

OMA-ETS-DL-OTA-v1_ a Page 1 (24)

NGSI Common Definitions

SOAP bindings for Call Notification

Enabler Release Definition for Standard Transcoding Interface

OMA Management Object for MMS

OMA Management Object for Mobile_

Enabler Release Definition for Rich Communication Centre

Client Side Content Screening Framework Architecture

Standardized Connectivity Management Objects 3GPP Circuit-Switched Data Bearer Parameters For use with OMA Device Management

Parlay Service Access Architecture

WAP WTAI (GSM) Version 08-Nov-1999

Enabler Release Definition for Mobile Location Protocol (MLP) Candidate Version Mar 2004

Enabler Release Definition for Application Layer Security Common Functions

Client Profile of OMA Device Management v1.3

Presence SIMPLE Architecture

Enabler Test Specification for RCS Conformance

Point-to-Multipoint Push Requirements

Enabler Release Definition for LPP Extensions (LPPe)

Enabler Test Specification for Device Management

Enabler Release Definition for LPP Extensions (LPPe)

Mobile Search Framework Architecture

Charging Data. Candidate Version Jul Open Mobile Alliance OMA-DDS-Charging_Data-V1_ C

Enabler Test Specification for Device Management

RESTful bindings for Parlay X Web Services - Payment

Software Component Management Object

RESTful Network API for Notification Channel

WAP WTAI WAP-170-WTAI Version 07-Jul-2000

WAP Push Message Version 16-August-1999

OMA PoC Endorsement of OMA IM TS

Push Security Requirements

White Paper on M2M Device Classification

Firmware Update Management Object

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

Enabler Release Definition for MMS

Lightweight M2M Event Log Object (LwM2M Object EventLog)

Continues the Technical Activities Originated in the SyncML Initiative

WAP MMS Client Transactions Version 15-Jan-2002

Security Common Functions Architecture

Software Component Management Object

Push Access Protocol. Version 29-Apr Wireless Application Protocol WAP-247-PAP a

White Paper on UAProf Best Practices Guide

RESTful Network API for Zonal Presence

Category: Standards Track September MIB Textual Conventions for Uniform Resource Identifiers (URIs)

IM XDM Specification. Candidate Version Aug Open Mobile Alliance OMA-TS-IM_XDM-V1_ C

Service Indication. Version 31-July Wireless Application Protocol WAP-167-ServiceInd a

WAP Provisioning Architecture Overview

RESTful Network API for Chat

Parlay Service Access Requirements

Multimedia Messaging Service

EUROPEAN STANDARD Global System for Mobile communication (GSM); Requirements for GSM operation on railways

SIP Forum Copyrights and Trademark Rights in Contributions Policy

WAP Over GSM USSD Version 30-July Wireless Application Protocol WAP-204-WAPOverGSMUSSD a

Jabber, Inc. August 20, 2004

Multimedia Messaging Service Architecture Overview

Enabler Test Specification (Interoperability) for MMS 1.3 Candidate Version 15 Jun 2006

Multimedia Messaging Service Encapsulation Protocol

OASIS - Artifact naming guidelines

Network Working Group Internet-Draft October 27, 2007 Intended status: Experimental Expires: April 29, 2008

NICC ND 1635 V 1.1.1( )

EUROPEAN STANDARD Electronic Signatures and Infrastructures (ESI); Time-stamping protocol and time-stamp profiles

ETSI TS V ( )

ETSI TS V ( )

Request for Comments: 3601 Category: Standards Track September 2003

Enabler Test Specification for Device Management

ETSI TS V8.0.0 ( ) Technical Specification

OneAPI Profile of RESTful Network APIs

ES V1.1.1 ( )

NICC ND 1636 V1.2.2 ( )

Software Component Management Object (SCOMO)

EN V1.2.4 ( )

Continues the Technical Activities Originated in the WAP Forum

Part 5: Protocol specifications

Corporate Registry: Access Code Guide. Corporate Registry

OMA Device Management Bootstrap

OneAPI Profile of RESTful Network APIs

Provisioning Smartcard

ISO/IEC Information technology Open Systems Interconnection The Directory: Protocol specifications

ETSI TS V ( )

Terms of Use. Changes. General Use.

Location in SIP/IP core Architecture Approved Version Jan 2012

Transcription:

WAP General Formats Document WAP-188-WAPGenFormats Version 10-Jul-2001 Wireless Application Protocol General Formats Document Disclaimer: A list of errata and updates to this document is available from the WAP Forum Web site, http://www.wapforum.org/, in the form of SIN documents, which are subject to revision or removal without notice 2001, Wireless Application Protocol Forum, Ltd. All Rights Reserved. Terms and conditions of use are available from the WAP Forum Web site (http://www.wapforum.org/what/copyright.htm).

WAP-188-WAPGenFormats, Version 10-Jul-2001 Page 2 (11) 2001, Wireless Application Protocol Forum, Ltd.. Terms and conditions of use are available from the WAP Forum Web site at http://www.wapforum.org/what/copyright.htm. You may use this document or any part of the document for internal or educational purposes only, provided you do not modify, edit or take out of context the information in this document in any manner. You may not use this document in any other manner without the prior written permission of the WAP Forum. The WAP Forum authorises you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services offered by you. The WAP Forum assumes no responsibility for errors or omissions in this document. In no event shall the WAP Forum be liable for any special, indirect or consequential damages or any damages whatsoever arising out of or in connection with the use of this information. WAP Forum TM members have agreed to use reasonable endeavors to disclose in a timely manner to the WAP Forum the existence of all intellectual property rights (IPR s) essential to the present document. The members do not have an obligation to conduct IPR searches. This information is publicly available to members and non-members of the WAP Forum and may be found on the WAP IPR Declarations list at http://www.wapforum.org/what/ipr.htm. Essential IPR is available for license on the basis set out in the schedule to the WAP Forum Application Form. No representations or warranties (whether express or implied) are made by the WAP Forum TM or any WAP Forum member or its affiliates regarding any of the IPR s represented on this list, including but not limited to the accuracy, completeness, validity or relevance of the information or whether or nt such rights are essential or non-essential. This document is available online in PDF format at http://www.wapforum.org/. Known problems associated with this document are published at http://www.wapforum.org/. Comments regarding this document can be submitted to the WAP Forum in the manner published at http://www.wapforum.org/.

WAP-188-WAPGenFormats, Version 10-Jul-2001 Page 3 (11) Contents 1. SCOPE... 4 2. DOCUMENTS STATUS... 5 2.1 COPYRIGHT NOTICE...5 2.2 ERRATA...5 2.3 COMMENTS...5 3. REFERENCES... 6 3.1 NORMATIVE REFERENCES...6 3.2 INFORMATIVE REFERENCE S...6 4. DEFINITIONS AND ABBREVIATIONS... 7 4.1 DEFINITIONS...7 4.2 ABBREVIATIONS...7 5. INTRODUCTION... 8 6. FORMATS DEFINITION... 9 6.1 SYNTAX DEFINITIONS...9

WAP-188-WAPGenFormats, Version 10-Jul-2001 Page 4 (11) 1. Scope Wireless Application Protocol (WAP) is a result of continuous work to define an industry wide specification for developing applications that operate over wireless communication networks. The scope for the WAP Forum is to define a set of specifications to be used by service applications. The wireless market is growing very quickly and reaching new customers and providing new services. To enable operators and manufacturers to meet the challenges in advanced services, differentiation, and fast/flexible service creation, WAP defines a set of protocols in transport, session and application layers. For additional information on the WAP architecture, refer to Wireless Application Protocol Architecture Specification [WAP]. This document defines a number of common formats that are used throughout the WAP specifications. Defining these formats in one document means that their use will be consistent throughout the specification, and simplifies the updating of formats.

WAP-188-WAPGenFormats, Version 10-Jul-2001 Page 5 (11) 2. Documents Status This document is available online in the following formats: PDF format at URL, http://www.wapforum.org/. 2.1 Copyright Notice Copyright Wireless Application Forum Ltd, 2000. Terms and conditions of use are available from the Wireless Application Protocol Forum Ltd. web site at http://www.wapforum.org/docs/copyright.htm. 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 WAP in the manner published at http://www.wapforum.org/.

WAP-188-WAPGenFormats, Version 10-Jul-2001 Page 6 (11) 3. References 3.1 Normative references [EBNF] W3C, REC-xml-19980210: Extensible Mark-up Language (xml) 1.0, February 10, 1998 [GSM02.90] [GSM03.03] [ITU-T Q.23] [RFC2119] [RFC2396] ETSI European Digital Cellular Telecommunication Systems (phase 2): Unstructured Supplementary Service Data (USSD) - stage 1 (GSM 02.90) "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification", (GSM 03.03 version 7.3.0 Release 1998) ITU-T Recommendation Q.23: Technical Features of Push-Button Telephone Sets, Copyright ITU 1988, 1993 "Key words for use in RFCs to Indicate Requirement Levels", S. Bradner, March 1997. URL: http://www.ietf.org/rfc/rfc2119.txt "Uniform Resource Identifiers (URI): Generic Syntax." T. Berners-Lee, R. Fielding, L. Masinter, et al., August 1998. URL: http://www.ietf.org/rfc/rfc2396.txt 3.2 Informative references [ITUE164] The International Public Telecommunication Numbering Plan, ITU-T Recommendation E.164, May 1997

WAP-188-WAPGenFormats, Version 10-Jul-2001 Page 7 (11) 4. Definitions and Abbreviations All non-trivial abbreviations and definitions used in this document are listed in the following sections. The definition section includes description of general concepts that may be fully defined in other documents. The purpose of this section is to advise the reader on the terminology used in the document. 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 by [RFC2119]. 4.2 Abbreviations For the purposes of this specification, the follo wing abbreviations apply. EBNF DTMF WAP Extended Backus-Naur Form Dual Tone Multi-Frequency Wireless Application Protocol

WAP-188-WAPGenFormats, Version 10-Jul-2001 Page 8 (11) 5. Introduction This document provides definitions of various formats that are used repeatedly throughout the WAP specifications. Specifying all these formats in one place makes the specifications clearer, more consistent and simplifies updating these formats. To date, the only formats specified within this document are telephone numbers, DTMF sequences, and address strings (all specified in section 6.1). In the future other formats may be added.

WAP-188-WAPGenFormats, Version 10-Jul-2001 Page 9 (11) 6. Formats definition This chapter contains the actual definitions of the various general formats. 6.1 Syntax Definitions This section defines a general format for telephone numbers, DTMF-sequences, dial strings, and address strings. The format is given using EBNF [EBNF]. EBNF reserves the hyphen character and does not capitalize non-terminal variables by convention. These rules are followed in the syntax definitions below. Outside of this specification, however, one may refer to variables using capital letters and with hyphens instead of underscores unambiguously, as these devices are not used to distinguish between variables in the definitions. address_string ::= ( phone_number dtmf_sequence pause )* <GPRS_APN> ss_string phone_number ::= international_phone_number national_phone_number international_phone_number ::= global_international_phone_number local_international_phone_number global_international_phone_number ::= global_international_extension national_phone_number global_international_extension ::= + country_code country_code ::= <one element of the country code list> local_international_phone_number ::= local_international_extension national_phone_number local_international_extension ::= DIGIT+ country_code DIGIT ::= 0 1 2 3 4 5 6 7 8 9 national_phone_number ::= DIGIT+ dtmf_sequence dtmf_digit pause one_second_pause ::=, ss_string service_code ::= dtmf_digit+ ::= DIGIT * # A B C D ::= one_second_pause ::= service_code supplementary_information ::= start sc start ::= START_DIGIT? START_DIGIT START_DIGIT START_DIGIT START_DIGIT START_DIGIT START_DIGIT ::= * # sc ::= DIGIT DIGIT DIGIT DIGIT DIGIT supplementary_information ::= # si_list # si_list si ::= si si si si si si ::= * * si_element

WAP-188-WAPGenFormats, Version 10-Jul-2001 Page 10 (11) Notes: si_element ::= <directory number> <basic service group> <no reply condition timer> <uus required option> <password> dialstring ::= pause* ( phone_number dtmf_sequence ) ( pause phone_number dtmf_sequence )* tone_sequence ::= ( pause dtmf_sequence )* 1. The definition of GPRS_APN can be found in [GSM03.03]. 2. In the definition of country_code : one element of the country code list is left undefined in this document. 3. In the definition of si_element : directory number, basic service group, no reply condition timer, uus required option, and password are left undefined in this document. 4. DTMF digits and characters in a dtmf_sequence correspond to the digits and characters along with their associated frequency pairs as defined in [ITU-T Q.23].

WAP-188-WAPGenFormats, Version 10-Jul-2001 Page 11 (11) Appendix A Specification-track Document History Document: WAP General Formats Document Document Identifier: WAP-188 Base Specification Approval Date: February 17 th, 2000 SINs Incorporated in this baseline document: SIN Approval Date August, 2000 April, 2001 SIN Document Identifier WAP-188_100 WAP-188_101