TIA-1059-2009 IP Based Over-the-Air Device Management (IOTA-DM) for cdma2000 Systems《cdma2000系统IP基无线设备管理(IOTA-DM)》.pdf

《TIA-1059-2009 IP Based Over-the-Air Device Management (IOTA-DM) for cdma2000 Systems《cdma2000系统IP基无线设备管理(IOTA-DM)》.pdf》由会员分享，可在线阅读，更多相关《TIA-1059-2009 IP Based Over-the-Air Device Management (IOTA-DM) for cdma2000 Systems《cdma2000系统IP基无线设备管理(IOTA-DM)》.pdf（70页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA-1059 March 2009 IP Based Over-the-Air Device Management (IOTA-DM) for cdma2000Systems NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and impro

2、vement 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 products not co

3、nforming 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 Standards Instit

4、ute (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 applicable regulat

5、ory 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, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no

6、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 involve the use of i

7、ntellectual 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 statement from the

8、 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 conditions, which ar

9、e 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 respects the Document

10、 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 otherwise), whether such r

11、eference 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 Reference; (ii) TIA

12、s 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 identification to TIA

13、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 contents of the Do

14、cument. 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 INTELLECTUAL PROPE

15、RTY 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 PRODUCT OR SERVICE RE

16、FERRED 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, INCIDENTAL OR CONSEQUE

17、NTIAL 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 FOREGOING NEGATION OF DAMA

18、GES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-1059 iiiCONTENTS 1 1 Introduction .211-1 2 1.1 Scope221-2 3 1.2 Definitions 231-2 4 1.3 General Requirements.241-5 5 1.4 Protocol Requirements 251-6 6 2 Arch

19、itecture262-1 7 3 Introduction to DM Protocol273-1 8 3.1 Management Tree283-1 9 3.2 Device Description 293-1 10 3.3 Bootstrap Mechanism .303-1 11 3.4 OMA DM Packages and Messages .313-2 12 3.5 OMA DM Commands 323-2 13 3.6 Notification Message .333-3 14 4 CDMA Device Management.344-1 15 4.1 Communica

20、tion with the Mobile Station354-1 16 4.2 IOTA-DM content 364-1 17 4.2.1 Command Set 374-1 18 4.2.2 XML Specification for OMA DM 384-1 19 4.2.3 OMA DM DTD394-1 20 4.2.4 OMA DM DTD Elements.404-1 21 4.3 MIME Types and HTTP Headers 414-2 22 4.3.1 MIME Types.424-2 23 4.3.2 Accept Headers for Supported M

21、IME Types434-2 24 4.3.3 HTTP Bindings.444-2 25 4.3.4 Other Transport Bindings 454-3 26 4.4 Network Initiated Scenario 464-3 27 4.5 MS Initiated Scenario474-5 28 5 CDMA Management Tree 485-1 29 5.1 CDMA DevInfo 495-1 30 5.1.1 DevId .505-1 31 5.1.2 CDMAProtPref515-2 32 TIA-1059 5.1.3 CDMAProtCap . 525

22、-2 1 5.1.4 CDMABandModCap. 535-2 2 5.2 CDMA Operational Parameters . 545-3 3 5.2.1 CMDAOpParam . 555-3 4 5.2.2 ./CDMA/CDMAOpParam/MobDirNum MobDirNum. 565-4 5 5.2.3 ./CDMA/CDMAOpParam/AmpsNam . 575-4 6 5.2.4 ./CDMA/CDMAOpParam/CdmaNam. 585-4 7 5.2.5 ./CDMA/CDMAOpParam/CDMANAM/y+ 595-4 8 5.2.6 ./CDMA

23、/CDMAOpParam/ImsiT 605-5 9 5.2.7 ./CDMA/CDMAOpParam/SSPR 615-5 10 5.2.8 ./CDMA/CDMAOpParam/PrefRoamList 625-5 11 5.2.9 ./CDMA/CDMAOpParam/PrefRoamListDim 635-5 12 5.2.10 ./CDMA/CDMAOpParam/ExPrefRoamList 645-6 13 5.2.11 ./CDMA/CDMAOpParam/ExPrefRoamListDim 655-6 14 5.2.12 ./CDMA/CDMAOpParam/PUZL 665

24、-6 15 5.2.13 ./CDMA/CDMAOpParam/SysTag 675-6 16 5.3 CDMA Packet Data Objects. 685-7 17 5.3.1 CDMAAP 695-8 18 5.3.2 ./CDMAAP/3GPD 705-8 19 5.3.2.1 ./CDMAAP/3GPD/3GPDOCP 715-8 20 5.3.2.2 ./CDMAAP/3GPD/3GPDOMP 725-8 21 5.3.2.3 ./CDMAAP/3GPD/SIP . 735-9 22 5.3.2.4 ./CDMAAP/3GPD/MIP 745-9 23 5.3.2.5 ./CD

25、MAAP/3GPD/HRPD. 755-9 24 5.4 CDMA MMD Management Object 765-9 25 5.4.1 ./CDMA/MMD. 775-10 26 5.4.2 ./CDMA/MMD/IMPILength . 785-10 27 5.4.3 ./CDMA/MMD/IMPI 795-11 28 5.4.4 ./CDMA/MMD/NumIMPU. 805-11 29 5.4.5 ./CDMA/MMD/ImpuEntryIndex+. 815-11 30 5.4.6 ./CDMA/MMD/ImpuEntryIndex+/IMPU. 825-11 31 5.4.7

26、./CDMA/MMD/SIPURILength . 835-12 32 TIA-1059 v5.4.8 ./CDMA/MMD/SIPDomainURI 845-12 1 5.4.9 ./CDMA/MMD/NumPCSCF. 855-12 2 5.4.10 ./CDMA/MMD/PCSCFEntryIndex+ 865-12 3 5.4.11 ./CDMA/MMD/PCSCFEntryIndex+/PCSCFAdd 875-13 4 5.5 CDMA System Tag Management Object. 885-13 5 5.5.1 ./CDMA/SysTag/HomeSysTag.895

27、-13 6 5.5.2 ./CDMA/SysTag/GroupTagListDim . 905-14 7 5.5.3 ./CDMA/SysTag/GroupTagList 915-14 8 5.5.4 ./CDMA/SysTag/SpecificTagListDim . 925-14 9 5.5.5 ./CDMA/SysTag/SpecificTagList 935-14 10 5.5.6 ./CDMA/SysTag/CallPromptListDim .945-15 11 5.5.7 ./CDMA/SysTag/CallPromptList 955-15 12 5.6 CDMA MMS Ma

28、nagement Object 965-15 13 5.6.1 ./CDMA/MMS .975-16 14 5.6.2 ./CDMA/MMS/NumMMSURI 985-16 15 5.6.3 ./CDMA/MMS/MMSURIEntryIndex+ 995-17 16 5.6.4 ./CDMA/MMS/MMSURIEntryIndex+/PCSCFEntryIndex+/MMSURI 1005-17 17 5.6.5 ./CDMA/MMS/MMSCap/1015-17 18 5.6.6 ./CDMA/MMS/MMSCap/MaxNumMMSURI1025-17 19 5.6.7 ./CDMA

29、/MMS/MMSCap/MaxMMSURILength.1035-18 20 6 IOTA-DM Security.1046-1 21 6.1 Access Control and Security1056-1 22 6.2 OTA Update of A-Key and other Critical Parameters1066-1 23 6.2.1 A-Key and Root Key Generation .1076-1 24 6.2.2 Service Key Generation 1086-5 25 6.2.3 SSD Update .1096-6 26 6.2.4 Establis

30、hing A-Key using DM when OTASP/OTAPA support exists 1106-6 27 6.3 Secure Mode Operation.1116-9 28 7 Handling of OTASP/OTAPA Messages.1127-1 29 8 IOTA-DM Firmware UPDATE Over-the-air.1138-1 30 8.1 CDMA Specific Security Mechanisms for FOTA .1148-1 31 ANNEX A DDF DESCRIPTION OF DEVINFO . 115A-1 32 TIA

31、-1059 viFIGURES 1 0Figure 2-1 Network Architecture.1162-1 2 1Figure 2-2 End-to-End Architecture for Device Management 1172-2 3 2Figure 3.4-1 OMA DM Message.1183-2 4 3Figure 4.4-1 Network Initiated Scenario1194-4 5 4Figure 4.5-1 Client Initiated Scenario .1204-5 6 5Figure 5.1-1 CDMA DevInfo Subtree.1

32、215-1 7 6Figure 5.2-1 CDMA Operational Parameters Management Objects 1225-3 8 7Figure 5.3-1 CDMA Packet Data Management Objects 1235-7 9 8Figure 5.4-1 CDMA MMD Management Objects 1245-10 10 9Figure 5.5-1 CDMA System Tag Management Objects. 1255-13 11 10Figure 5.6-1 CDMA MMS Management Objects 1265-1

33、6 12 11Figure 6.2.1-1 Key Generation using DM Protocol 1276-2 13 12Figure 6.2.1-2 Command in Package #2 .1286-4 14 13Figure 6.2.1-3 Example of Results Command in Package #3. 1296-4 15 14Figure 6.2.1-4 Commands in Package #41306-5 16 15Figure 6.2.1-5 Example of Results Command .1316-5 17 16Figure 6.2

34、.2-1 Command for Service Key Generation1326-6 18 17Figure 6.2.4-1 Flow Diagram for A-Key Establishment 1336-7 19 18Figure 7-1 Representation of OTASP/OTAPA Message 1347-1 20 19Figure 7-2 Message Flow for Handling OTASP/OTAPA Message. 1357-2 21 TIA-1059 viiNOTES 1 1. Compatibility, as used in connect

35、ion with cdma200001, is understood to mean: any 2 cdma2000 mobile station is able to place and receive calls in cdma2000 and IS-95 3 systems. Conversely, any cdma2000 system is able to place and receive calls for 4 cdma2000 and IS-95 mobile stations. 5 2. The following verbal forms are used: “Shall”

36、 and “shall not” identify requirements to 6 be followed strictly to conform to the 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; that 9 a cer

37、tain course of action is preferred but not necessarily required; or that (in the 10 negative form) a certain possibility or course of action is discouraged but not 11 prohibited. “May” and “need not” indicate a course of action permissible within the 12 limits of the standard. “Can” and “cannot” are

38、 used for statements of possibility 13 and capability, whether material, physical, or causal. 14 2. Footnotes appear at various points in this specification to elaborate and to further 15 clarify items discussed in the body of the specification. 16 3. Unless indicated otherwise, this document presen

39、ts numbers in decimal form. 17 Binary numbers are distinguished in the text by the use of single quotation marks. 18 In some tables, binary values may appear without single quotation marks if table 19 notation clearly specifies that values are binary. The character x is used to 20 represent a bit of

40、 unspecified value. For example xxx00010 represents any 8-bit 21 binary value 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 h h represents a string of hexadecimal digits. For example, 0x2fa1 24 r

41、epresents a number whose binary value is 0010111110100001 and whose 25 decimal value is 12193. Note that the exact number of bits in the binary 26 representation of a hexadecimal number strictly depends upon the implementation 27 requirements for the variable being represented. 28 1“cdma2000 is the

42、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), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States.” TIA-

43、1059 viii4. “Base station” refers to the functions performed on the fixed network, which are 1 typically distributed among a cell, a sector of a cell, and a mobile communications 2 switching center. 3 TIA-1059 ixREFERENCES 1 The following standards are referenced in this text. At the time of publica

44、tion, the editions 2 indicated were valid. All standards are subject to revision, and parties to agreements 3 based upon this document are encouraged to investigate the possibility of applying the 4 most recent editions of the standards indicated below. ANSI and TIA maintain registers of 5 currently

45、 valid national standards published by them. 6 - Normative References: 7 1. TIA-637-C, Short Message Services for Wideband Spread Spectrum Systems, June 8 2004. 9 2. TIA-683-D, Over-the-Air Service Provisioning of Mobile Stations in Spread Spectrum 10 Systems, November 2004. 11 3. TIA-1010, IP Based

46、 Over-the-Air Handset Configuration Management, July 2003. 12 4. 3GPP2 S.R0101-0 1 IOTA Device Management for cdma2000 Systems Stage-1 13 requirements, version 1.0, April 22 2004. 14 5. OMA Device Management Protocol, version 1.2, OMA, June 2005. URL 15 20http:/www.openmobilealliance.org/release_pro

47、gram/dm_v12.html 16 6. OMA DM Representation Protocol, version 1.2, OMA, June 2005. 17 7. OMA DM Tree and Descriptions, version 1.2, OMA, June 2005. 18 8. OMA DM Bootstrap, version 1.2, OMA, June 2005. 19 9. OMA DM Notification Initiated Session, version 1.2, OMA, June 2005. 20 10. OMA DM Security,

48、version 1.2, OMA, June 2005. 21 11. OMA DM DDF DTD (OMA-DM-DDF-V1_2_0-20050118-D.dtd), version 1.2, OMA, June 22 2005. 23 12. OMA SyncML HTTP Binding, Version 1.2,OMA, June 2005. 24 13. OMA SyncML OBEX Binding, version 1.2, OMA, June 2005. 25 14. OMA SyncML WSP Binding, version 1.2, OMA, June 2005.

49、26 15. OMA Firmware Update Management Object, Draft Version 1.0, May 2005. 27 http:/member.openmobilealliance.org/ftp/Public_documents/DM/Permanent_docum28 ents/OMA-TS-DM-FUMO-V1_0-20050518-D.zip 29 16. W3C Extensible Markup Language (XML) 1.0 (Second Edition), W3C Recommendation, 30 Version 6, October 2000. 31 17. IETF RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax, August 1998. 32 18. IETF RFC 2045, Multipurpose Internet Mail Extensions (MIME) Part One: Format of 33 Internet Message Bodies, November 1996. 34 19. IETF RFC 2246, The TLS Protocol, Version 1.0