OMA Push Management Object

Transcription

1 OMA Push Management Object Candidate Version Oct 2007 Open Mobile Alliance OMA-TS-Push_MO-V1_ C

2 OMA-TS-Push_MO-V1_ C Page 2 (12) Use of this document is subject to all of the terms and conditions of the Use Agreement located at Unless this document is clearly designated as an approved specification, this document is a work in process, is not an approved Open Mobile Alliance specification, and is subject to revision or removal without notice. 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. Information contained in this document may be used, at your sole risk, for any purposes. You may not use this document in any other manner without the prior written permission of the Open Mobile Alliance. The Open Mobile Alliance authorizes 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. The Open Mobile Alliance assumes no responsibility for errors or omissions in this document. Each Open Mobile Alliance member has agreed to use reasonable endeavors to inform the Open Mobile Alliance in a timely manner of Essential IPR as it becomes aware that the Essential IPR is related to the prepared or published specification. However, the members do not have an obligation to conduct IPR searches. The declared Essential IPR is publicly available to members and non-members of the Open Mobile Alliance and may be found on the OMA IPR Declarations list at The Open Mobile Alliance has not conducted an independent IPR review of this document and the information contained herein, and makes no representations or warranties regarding third party IPR, including without limitation patents, copyrights or trade secret rights. This document may contain inventions for which you must obtain licenses from third parties before making, using or selling the inventions. Defined terms above are set forth in the schedule to the Open Mobile Alliance Application Form. NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE MADE BY THE OPEN MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER OR ITS AFFILIATES REGARDING ANY OF THE IPR S REPRESENTED ON THE OMA IPR DECLARATIONS 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. THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY DIRECT, INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS. Used with the permission of the Open Mobile Alliance Ltd. under the terms set forth above.

3 OMA-TS-Push_MO-V1_ C Page 3 (12) Contents 1. SCOPE REFERENCES NORMATIVE REFERENCES INFORMATIVE REFERENCES TERMINOLOGY AND CONVENTIONS CONVENTIONS DEFINITIONS ABBREVIATIONS INTRODUCTION PUSH MANAGEMENT OBJECT MANAGEMENT OBJECT PARAMETERS...8 APPENDIX A. CHANGE HISTORY (INFORMATIVE)...12 A.1 APPROVED VERSION HISTORY...12 A.2 DRAFT/CANDIDATE VERSION 1.0 HISTORY...12

4 OMA-TS-Push_MO-V1_ C Page 4 (12) 1. Scope This document defines the OMA Push Management Object that manages the push whitelist.

5 OMA-TS-Push_MO-V1_ C Page 5 (12) 2. References 2.1 Normative References [PUSH] [DMSTDOBJ] [DM-TND-V1-2] "OMA Push Over The Air, Version 2.2 ". Open Mobile Alliance OMA-TS-PushOTA-V2_2. URL: "OMA Device Management Standardized Objects, Version 1.2". Open Mobile Alliance OMA-TS-DM-StdObj-V1_2. URL: "OMA Device Management Tree and Description, Version 1.2". Open Mobile Alliance OMA-TS-DM_TND-V1_2 URL: [DMBOOT] OMA Device Management Bootstrap, Version 1.2. Open Mobile Alliance. OMA-TS- DM_Bootstrap-V1_2. URL: [DMTNDS] OMA Device Management Tree and Description Serialization Specification, Version 1.2. Open Mobile Alliance. OMA-TS-DM_TNDS-V1_2. URL: [RFC1918] Address Allocation for Private Internets [RFC791] RFC 791, Internet Protocol, DARPA, 1981, URL: [RFC3513] RFC 3513, Internet Protocol Version 6 (IPv6) Addressing Architecture, 2.2, 2.3 The Internet Society, 2003, URL: [RFC2373] IP Version 6 Addressing Architecture [RFC3986] URI Generic Syntax [GENFORM] WAP General Formats Document, WAP Forum_, WAP-188-WAPGenFormats, URL: Informative References [PUSHMO-DDF] Push Management Object Device Description Framework", URL:

6 OMA-TS-Push_MO-V1_ C Page 6 (12) 3. Terminology and Conventions 3.1 Conventions 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 in [RFC2119]. All sections and appendixes, except Scope and Introduction, are normative, unless they are explicitly indicated to be informative. 3.2 Definitions See the DM Tree and Description [DM-TND-V1-2] document for definitions of terms related to the management tree. 3.3 Abbreviations OMA MO SMSC PPG Open Mobile Alliance Management Object Short Message Service Centre Push Proxy Gateway

7 OMA-TS-Push_MO-V1_ C Page 7 (12) 4. Introduction DM group has defined Management Objects where parameters can be easily managed and used by applications. This document describes the OMA Push Management Object syntax that manages the push whitelists.

8 OMA-TS-Push_MO-V1_ C Page 8 (12) 5. Push Management Object Push Management Object (MO) is an object for OMA BAC Push that restricts the accepted push messages depending on the originating PPG address or the originating SMSC address. The MO can be initially provisioned and is used for continuous provisioning to update service configurations. If the Push MO is provisioned together with other management object(s) during bootstrap then [DMTNDS] and [DMBOOT] MUST be used. The OMA BAC Push Management Object consists of relevant parameters required by the PUSH enabler. It is compatible with OMA Device Management protocol specifications, version 1.2, and is defined using the OMA DM Device Description Framework as described in [DM-TND-V1-2] and [DMSTDOBJ]. The Management Object Identifier is: urn:oma:mo:oma-push:1.0 Protocol compatibility: This MO is compatible with OMA DM 1.2. The following figure shows the nodes and leaf objects for the OMA_PUSH Management Object. <X>* Addr AddrType? TrustedPPG Ext? <X> PushWL TrustedSMSC <X>* Addr Ext? 5.1 Management Object parameters This section describes the parameters for the OMA BAC PUSH Management Object. The procedure to validate whether the Push PDU originates from a trusted source or not is defined in [PUSH]. Node: /<X> This interior node acts as a placeholder for one or more accounts for a fixed node. It specifies the object root of a BAC PUSH management object. The purpose of this interior node is to group together the parameters of a single BAC PUSH object. The ancestor elements of this node define the position in the management tree of the BAC PUSH object. But the structure of the DM tree and hence positions in the tree of management objects is out of scope

9 OMA-TS-Push_MO-V1_ C Page 9 (12) of this specification. Occurrence: OneOrMore Format: Node Access Types: Get Values: N/A /<X>/PushWL The PushWL interior node is used to hold a list of PPG Addresses and/or a list of SMSCAddresses. Occurrence: One Format: Node /<X>/PushWL/TrustedPPG The TrustedPPG interior node is used to list the PPG addresses from which push message is trusted. It makes it possible to specify a plurality of addresses. Occurrence: One Format: Node /<X>/PushWL/TrustedSMSC The TrustedSMSC interior node is used to list the SMSC addresses from which push message content is trusted. It makes it possible to specify a plurality of addresses. Occurrence: One Format: Node /<X>/ PushWL/TrustedPPG /<X>* This node contains the instances of authorized Push Proxy Gateway addresses. Occurrence: ZeroOrMore Format: Node /<X>/ PushWL/TrustedSMSC /<X>* This node contains the instances of authorized SMSC addresses. Occurrence: ZeroOrMore Format: Node /<X>/PushWL/TrustedPPG /<X>+/Addr The Addr node holds addresses of different types, for example, an IP address or an URI. The type of address in the field can be determined on the AddrType node.

10 OMA-TS-Push_MO-V1_ C Page 10 (12) Occurrence: One Format: Chr /<X>/PushWL/TrustedPPG/<X>+/AddrType? This leaf node specifies the type of NAP address supplied as the Addr leaf node value. If this node is omitted, the type of the Addr node value MUST be IPv4. AddrType IPv4 IPv6 URI E164 Value of Addr node An IPv4 address [RFC791] represented in string form dotted-decimal CIDR notation Subnetwork addressing using the CIDR notation is allowed (e.g /15) [RFC1918] IPV4 is the default value of the AddrType node An IPv6 address represented in string form as in [RFC3513] Subnetwork addressing using the CIDR notation is allowed [RFC2373] URI formed as in [RFC3986] A phone number according to the E164 scheme [GENFORM] Status: Optional Occurrence: ZeroOrOne Format: Chr Value: IPv4 /<X>/PushWL/TrustedPPG /<X>+/Ext? The Ext is an interior node where the vendor-specific information about the OMA_BAC-PUSH MO is placed ( vendor means application vendor, device vendor etc.). Usually the vendor extension is identified by a vendorspecific name under the ext node. The tree structure under the vendor identified is not defined and can therefore include a non-standardized sub-tree. Status: Optional Occurrence: ZeroOrOne Format: node Access Types: Get Values: N/A /<X>/PushWL/TrustedSMSC/<X>+/Addr The Addr node holds the trusted SMSC E164 address. Occurrence: One Format: Chr /<X>/PushWL/TrustedSMSC/<X>+/Ext? The Ext is an interior node where the vendor-specific information about the OMA_BAC-PUSH MO is placed ( vendor means application vendor, device vendor etc.). Usually the vendor extension is identified by a vendorspecific name under the ext node. The tree structure under the vendor identified is not defined and can therefore include a non-standardized sub-tree. Status: Optional Occurrence: ZeroOrOne Format: node Access Types: Get Values: N/A

11 OMA-TS-Push_MO-V1_ C Page 11 (12) The complete Device Description Framework of this Push management object can be found in [PUSHMO-DDF].

12 OMA-TS-Push_MO-V1_ C Page 12 (12) Appendix A. Change History (Informative) A.1 Approved Version History n/a Reference Date Description A.2 Draft/Candidate Version 1.0 History Document Identifier Date Sections Description Draft Versions 13 Dec 2006 All Document creation OMA-TS-Push_MO-V1_0-14 Dec 2006 Addition of a reference to the DDF file Editorial modifications Candidate Version: OMA-TS-Push_MO-V1_0 22 Jan 2007 Updated after consistency review 05 Jul 2007 All Editorial updates: Cover page and header fixed with correct specification title History box fixed as per template 2007 copyright Cross-References fixed 26 Jul and 5 Bug fix regarding the MO provisioning 02 Oct 2007 N/A Status changed to Candidate by TP: TP ref # OMA-TP R01- INP_Push_V2_2_ERP_for_Candidate_Approval