1999-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 ).
Push Message
Version 22-Mar-2001
Wireless Application Protocol
WAP-251-PushMessage-20010322-a
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.
WAP-251-PushMessage-20010322-a, Version 22-Mar-2001 Page 2 (14)
1999-2001, Wireless Application Protocol Forum, Ltd.
All rights reserved
© 1999-2001, Wireless Application Protocol Forum, Ltd. All rights reserved.
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™ 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™ 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 not 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/.
Document History
WAP-145-PushMessage-19990816-a Approved
WAP-145_100-PushMessage-20001211-a SIN
WAP-145_101-PushMessage-20010614-a (obsoletes WAP-145_100-PushMessage-2001211-1) SIN
WAP-251-PushMessage-20010322-a Current
WAP-251-PushMessage-20010322-a, Version 22-Mar-2001 Page 3 (14)
1999-2001, Wireless Application Protocol Forum, Ltd.
All rights reserved
Contents
1. SCOPE...............................................................................................................................................................................................4
2. REFERENCES ................................................................................................................................................................................4
2.1. NORMATIVE REFERENCES.......................................................................................................................................................4
2.2. INFORMATIVE REFERENCES ...................................................................................................................................................5
3. DEFINITIONS AND ABBREVIATIONS................................................................................................................................6
3.1. DEFINITIONS ..............................................................................................................................................................................6
3.2. ABBREVIATIONS ........................................................................................................................................................................6
4. INTRODUCTION...........................................................................................................................................................................7
5. PUSH MESSAGE DEFINITION...............................................................................................................................................8
5.1. MESSAGE FORMAT...................................................................................................................................................................8
5.2. MESSAGE HEADERS..................................................................................................................................................................8
5.2.1. Generic Headers..................................................................................................................................................................8
5.2.2. WAP Headers......................................................................................................................................................................9
5.2.3. Header Extensions............................................................................................................................................................10
5.3. MESSAGE BODY.......................................................................................................................................................................10
6. PROXY RULES ............................................................................................................................................................................11
APPENDIX A. STATIC CONFORMANCE REQUIREMENTS..................................................................................12
APPENDIX B. CHANGE HISTORY....................................................................................................................................14
WAP-251-PushMessage-20010322-a, Version 22-Mar-2001 Page 4 (14)
1999-2001, Wireless Application Protocol Forum, Ltd.
All rights reserved
1. Scope
This section is informative.
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 specification defines the push message, which is used by a WAP push application to deliver the content to a WAP
client. In particular, it defines the following:
· General format of the push message
· Headers of the push message
· Body of the push message
· Proxy rules for header handling
2. References
2.1. Normative references
[CREQ] “Specification of WAP Conformance Requirements”, WAP-221-CREQ-20010425-a, WAP
Forum Ltd. URL: http://www.wapforum.org/
[HTTP] “Hypertext Transfer Protocol – HTTP/1.1”, R. Fielding, et al. June 1999
URL: http://www.ietf.org/rfc/rfc2616.txt/
[PushOTA]
“Push OTA Specification”, WAP-235-PushOTA-20010308-a, WAP Forum.
URL: http://www.wapforum.org/
[PushPAP]
“Push Access Protocol Specification”. WAP Forum. WAP-247-PAP-20010429-a.
URL: http://www.wapforum.org/
[RFC822] “Standard for the Format of ARPA Internet Text Messages”, D. Crocker, August 1982, URL:
http://www.ietf.org/rfc/rfc822/
[RFC2234] “Augmented BNF for Syntax Specification: ABNF”, D. Crocker, et al., November 1997,
URL: http://www.ietf.org/rfc/rfc2234.txt/
[RFC2396] “Uniform Resource Identifiers (URI): Generic Syntax”, T. Berners-Lee et al., August 1998,
URL: http://www.ietf.org/rfc/rfc2396.txt/
[WAPCache]
“WAP Caching Model”, WAP-120-WAPCachingMod-19990211-a, WAP Forum.
URL: http://www.wapforum.org/
[WINA] “WAP Interim Naming Authority”, WAP Forum,
URL:http://www.wapforum.org/wina/
WAP-251-PushMessage-20010322-a, Version 22-Mar-2001 Page 5 (14)
1999-2001, Wireless Application Protocol Forum, Ltd.
All rights reserved
2.2. Informative references
[PushArch]
“Push Architectural Overview”. WAP Forum. WAP-250-PushArchOverview-20010703-p.
URL: http://www.wapforum.org/
[WAP]
“Wireless Application Protocol Architecture Specification”. WAP Forum.
WAP-210-WAPArch-20010712-a. URL: http://www.wapforum.org/
[WAE]
“Wireless Application Environment Specification”, WAP Forum.
WAP-236-WAESpec-20010210-a. URL: http://www.wapforum.org/
[WSP]
“Wireless Session Protocol”. WAP Forum. WAP-230-WSP-20010705-a.
URL: http://www.wapforum.org/
