1、 TIA-1059-1E March 2011IP Based Over-the-Air Device Management (IOTA-DM) for cdma2000 Systems Addendum 1 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeabi
2、lity and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling p
3、roducts not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National St
4、andards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all appl
5、icable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From Project No. 3-0187-AD1, formulated under the cognizance of the TIA TR-45 Mobil
6、e (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may in
7、volve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a
8、statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or co
9、nditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as res
10、pects the Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwis
11、e), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative R
12、eference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute iden
13、tification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the
14、contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS
15、INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRO
16、DUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCI
17、DENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOIN
18、G NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. 3GPP2 C.S0064-0 v2.0 Revision History Revision Description Date C.S0064-0 v1.0 Initial Release September 2005 C.S0064-0 v2.0 Point Release for
19、CDMA MO January 2011 3GPP2 C.S0064-0 v2.0 i CONTENTS 1 Forewordvi 2 1 INTRODUCTION .1-1 3 1.1 Scope1-2 4 1.2 Requirements Language 1-2 5 1.3 References1-2 6 1.4 Definitions1-3 7 1.5 General Requirements.1-7 8 1.6 Protocol Requirements.1-8 9 2 ARCHITECTURE2-1 10 3 INTRODUCTION TO DM PROTOCOL 3-1 11 3
20、.1 Management Tree 3-1 12 3.2 Device Description .3-1 13 3.3 Bootstrap Mechanism.3-1 14 3.4 OMA DM Packages and Messages 3-2 15 3.5 OMA DM Commands 3-2 16 3.6 Notification Message 3-3 17 4 CDMA DEVICE MANAGEMENT4-1 18 4.1 Communication with the Mobile Station .4-1 19 4.2 IOTA-DM content.4-1 20 4.2.1
21、 Command Set .4-1 21 4.2.2 XML Specification for OMA DM 4-1 22 4.2.3 OMA DM DTD.4-1 23 4.2.4 OMA DM DTD Elements.4-1 24 4.3 MIME Types and HTTP Headers .4-2 25 4.3.1 MIME Types 4-2 26 4.3.2 Accept Headers for Supported MIME Types 4-2 27 4.3.3 HTTP Bindings4-2 28 4.3.4 Other Transport Bindings 4-3 29
22、 4.4 Network Initiated Scenario.4-3 30 4.5 MS Initiated Scenario.4-5 31 5 CDMA MANAGEMENT TREE.5-1 32 3GPP2 C.S0064-0 v2.0 ii 5.1 CDMA DevInfo 5-1 1 5.1.1 DevId 5-1 2 5.1.2 CDMAProtPref.5-2 3 5.1.3 CDMAProtCap.5-2 4 5.1.4 CDMABandModCap 5-2 5 5.2 CDMA Operational Parameters 5-3 6 5.2.1 CDMA .5-3 7 5
23、.2.2 CMDA OpParam5-4 8 5.2.3 ./CDMA/CDMAOpParam/MobDirNum MobDirNum 5-4 9 5.2.4 ./CDMA/CDMAOpParam/AmpsNam5-4 10 5.2.5 ./CDMA/CDMAOpParam/CdmaNam5-4 11 5.2.6 ./CDMA/CDMAOpParam/CDMANAM/y+ .5-5 12 5.2.7 ./CDMA/CDMAOpParam/ImsiT .5-5 13 5.2.8 ./CDMA/CDMAOpParam/SSPR .5-5 14 5.2.9 ./CDMA/CDMAOpParam/Pr
24、efRoamList .5-5 15 5.2.10 ./CDMA/CDMAOpParam/PrefRoamListDim.5-6 16 5.2.11 ./CDMA/CDMAOpParam/ExPrefRoamList .5-6 17 5.2.12 ./CDMA/CDMAOpParam/ExPrefRoamListDim.5-6 18 5.2.13 ./CDMA/CDMAOpParam/PUZL5-6 19 5.2.14 ./CDMA/CDMAOpParam/SysTag.5-7 20 5.3 MOID for CDMA MO .5-7 21 5.4 CDMA Packet Data Objec
25、ts5-7 22 5.4.1 CDMAAP .5-8 23 5.4.2 ./CDMAAP/3GPD5-9 24 5.4.2.1 ./CDMAAP/3GPD/3GPDOCP5-9 25 5.4.2.2 ./CDMAAP/3GPD/3GPDOMP .5-9 26 5.4.2.3 ./CDMAAP/3GPD/SIP.5-10 27 5.4.2.4 ./CDMAAP/3GPD/MIP5-10 28 5.4.2.5 ./CDMAAP/3GPD/HRPD.5-10 29 5.5 CDMA MMD Management Object.5-10 30 5.5.1 ./CDMA/MMD 5-11 31 5.5.
26、2 ./CDMA/MMD/IMPILength 5-11 32 3GPP2 C.S0064-0 v2.0 iii 5.5.3 ./CDMA/MMD/IMPI5-12 1 5.5.4 ./CDMA/MMD/NumIMPU.5-12 2 5.5.5 ./CDMA/MMD/ImpuEntryIndex+ .5-12 3 5.5.6 ./CDMA/MMD/ImpuEntryIndex+/IMPU5-12 4 5.5.7 ./CDMA/MMD/SIPURILength.5-13 5 5.5.8 ./CDMA/MMD/SIPDomainURI .5-13 6 5.5.9 ./CDMA/MMD/NumPCS
27、CF 5-13 7 5.5.10 ./CDMA/MMD/PCSCFEntryIndex+ .5-13 8 5.5.11 ./CDMA/MMD/PCSCFEntryIndex+/PCSCFAdd.5-14 9 5.6 CDMA System Tag Management Object.5-14 10 5.6.1 ./CDMA/SysTag/HomeSysTag .5-14 11 5.6.2 ./CDMA/SysTag/GroupTagListDim5-15 12 5.6.3 ./CDMA/SysTag/GroupTagList 5-15 13 5.6.4 ./CDMA/SysTag/Specif
28、icTagListDim .5-15 14 5.6.5 ./CDMA/SysTag/SpecificTagList5-15 15 5.6.6 ./CDMA/SysTag/CallPromptListDim5-16 16 5.6.7 ./CDMA/SysTag/CallPromptList 5-16 17 5.7 CDMA MMS Management Object.5-16 18 5.7.1 ./CDMA/MMS.5-17 19 5.7.2 ./CDMA/MMS/NumMMSURI5-17 20 5.7.3 ./CDMA/MMS/MMSURIEntryIndex+ 5-18 21 5.7.4
29、./CDMA/MMS/MMSURIEntryIndex+/MMSURI.5-18 22 5.7.5 ./CDMA/MMS/MMSCap/.5-18 23 5.7.6 ./CDMA/MMS/MMSCap/MaxNumMMSURI.5-18 24 5.7.7 ./CDMA/MMS/MMSCap/MaxMMSURILength .5-19 25 6 IOTA-DM SECURITY.6-1 26 6.1 Access Control and Security.6-1 27 6.2 OTA Update of A-Key and other Critical Parameters6-1 28 6.2.
30、1 A-Key and Root Key Generation.6-1 29 6.2.2 Service Key Generation 6-5 30 6.2.3 SSD Update 6-6 31 6.2.4 Establishing A-Key using DM when OTASP/OTAPA support exists.6-6 32 3GPP2 C.S0064-0 v2.0 iv 6.3 Secure Mode Operation .6-9 1 7 HANDLING OF OTASP/OTAPA MESSAGES.7-1 2 8 IOTA-DM FIRMWARE UPDATE OVER
31、-THE-AIR 8-1 3 8.1 CDMA Specific Security Mechanisms for FOTA8-1 4 ANNEX A DDF DESCRIPTION OF DEVINFO A-1 5 6 3GPP2 C.S0064-0 v2.0 v FIGURES 1 Figure 2-1 Network Architecture. 2-1 2 Figure 2-2 End-to-End Architecture for Device Management . 2-2 3 Figure 3.4-1 OMA DM Message . 3-2 4 Figure 4.4-1 Netw
32、ork Initiated Scenario . 4-4 5 Figure 4.5-1 Client Initiated Scenario. 4-5 6 Figure 5.1-1 CDMA DevInfo Subtree . 5-1 7 Figure 5.2-1 CDMA Operational Parameters Management Objects 5-3 8 Figure 5.3-1 CDMA Packet Data Management Objects. 5-8 9 Figure 5.4-1 CDMA MMD Management Objects 5-11 10 Figure 5.5
33、-1 CDMA System Tag Management Objects 5-14 11 Figure 5.6-1 CDMA MMS Management Objects 5-17 12 Figure 6.2.1-1 Key Generation using DM Protocol 6-2 13 Figure 6.2.1-2 Command in Package #2 6-4 14 Figure 6.2.1-3 Example of Results Command in Package #3 . 6-4 15 Figure 6.2.1-4 Commands in Package #4. 6-
34、5 16 Figure 6.2.1-5 Example of Results Command 6-5 17 Figure 6.2.2-1 Command for Service Key Generation . 6-6 18 Figure 6.2.4-1 Flow Diagram for A-Key Establishment 6-7 19 Figure 7-1 Representation of OTASP/OTAPA Message 7-1 20 Figure 7-2 Message Flow for Handling OTASP/OTAPA Message. 7-2 21 22 3GPP
35、2 C.S0064-0 v2.0 vi FOREWORD 1 (This foreword is not part of this specification.) 2 This specification was prepared by 3GPP2 TSG-C Working Group 1. 3 3GPP2 C.S0064-0 v2.0 vii NOTES 1 1. Compatibility, as used in connection with cdma20001, is understood to mean: 2 any cdma2000 mobile station is able
36、to place and receive calls in cdma2000 and 3 IS-95 systems. Conversely, any cdma2000 system is able to place and receive calls 4 for cdma2000 and IS-95 mobile stations. 5 2. The following verbal forms are used: “Shall” and “shall not” identify requirements 6 to be followed strictly to conform to the
37、 standard and from which no deviation is 7 permitted. “Should” and “should not” indicate that one of several possibilities is 8 recommended as particularly suitable, without mentioning or excluding others; 9 that a certain course of action is preferred but not necessarily required; or that 10 (in th
38、e negative form) a certain possibility or course of action is discouraged but 11 not prohibited. “May” and “need not” indicate a course of action permissible 12 within the limits of the standard. “Can” and “cannot” are used for statements of 13 possibility and capability, whether material, physical,
39、 or causal. 14 3. Footnotes appear at various points in this specification to elaborate and to 15 further clarify items discussed in the body of the specification. 16 4. Unless indicated otherwise, this document presents numbers in decimal form. 17 Binary numbers are distinguished in the text by the
40、 use of single quotation 18 marks. In some tables, binary values may appear without single quotation marks 19 if table notation clearly specifies that values are binary. The character x is used 20 to represent a binary bit of unspecified value. For example xxx00010 represents 21 any 8-bit binary val
41、ue such that the least significant five bits equal 00010. 22 Hexadecimal numbers (base 16) are distinguished in the text by use of the form 23 0xhh where hh represents a string of hexadecimal digits. For example, 24 0x2fa1 represents a number whose binary value is 0010111110100001 and 25 whose decim
42、al value is 12193. Note that the exact number of bits in the binary 26 representation of a hexadecimal number strictly depends on the implementation 27 requirements for the variable being represented. 28 5. “Base station” refers to the functions performed on the fixed network, which are 29 typically
43、 distributed among a cell, a sector of a cell, and a mobile communications 30 switching center. 31 1“cdma2000 is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cd
44、ma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States.” 3GPP2 C.S0064-0 v2.0 viii REFERENCES 1 The following standards are referenced in this text. At the time of publication, the 2 editions indicated were valid. All standards are subject to r
45、evision, and parties to 3 agreements based upon this document are encouraged to investigate the possibility of 4 applying the most recent editions of the standards indicated below. ANSI and TIA 5 maintain registers of currently valid national standards published by them. 6 - Normative References: 7
46、21.3GPP2 C.S0015-B v1.0, Short Message Services for Wideband Spread Spectrum 8 Systems, June 2004. 9 21.3GPP2 C.S0016-C v1.0, Over-the-Air Service Provisioning of Mobile Stations in Spread 10 Spectrum Systems, November 2004. 11 21.3GPP2 C.S0040-0 v1.0, IP Based Over-the-Air Handset Configuration Man
47、agement, 12 July 2003. 13 21.3GPP2 S.R0101-0 1 IOTA Device Management for cdma2000 Systems Stage-1 14 requirements, version 1.0, April 22 2004. 15 21.OMA Device Management Protocol, version 1.2, OMA, June 2005. URL 16 http:/www.openmobilealliance.org/release_program/dm_v12.html 17 21.OMA DM Represen
48、tation Protocol, version 1.2, OMA, June 2005. 18 21.OMA DM Tree and Descriptions, version 1.2, OMA, June 2005. 19 21.OMA DM Bootstrap, version 1.2, OMA, June 2005. 20 21.OMA DM Notification Initiated Session, version 1.2, OMA, June 2005. 21 21.OMA DM Security, version 1.2, OMA, June 2005. 22 21.OMA
49、DM DDF DTD (OMA-DM-DDF-V1_2_0-20050118-D.dtd), version 1.2, OMA, June 23 2005. 24 21.OMA SyncML HTTP Binding, Version 1.2,OMA, June 2005. 25 21.OMA SyncML OBEX Binding, version 1.2, OMA, June 2005. 26 21.OMA SyncML WSP Binding, version 1.2, OMA, June 2005. 27 21.OMA Firmware Update Management Object, Draft Version 1.0, May 2005. 28 http:/member.openmobilealliance.org/ftp/Public_documents/DM/Permanent_docum29 ents/OMA-TS-DM-FUMO-V1_0-20050518-D.zip 30 21.W3C Extensible Markup Language (XML) 1.0 (Second Edition), W3C Recommendation, 31 Version 6, October 2000. 32 21.IETF R
