TIA-5022 005-2015 Management Enablement (OMA) (oneM2M TS-0005-v1 0 1).pdf

1、 TIA-5022.005 October 2015Management Enablement (OMA) (oneM2M TS-0005-v1.0.1) NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of pro

2、ducts, 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 conforming to s

3、uch 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 Institute (ANSI) pa

4、tent 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 regulatory requireme

5、nts. 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. Any use of trademarks in this document are for information purposes and do not constitute an endorsement by TIA

6、 or this committee of the products or services of the company. (From Project No. TIA-PN-5022.005, formulated under the cognizance of the TIA TR-50 M2M- Smart Device Communications.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Technology (b) there is no assurance that the Document will be ap

7、proved 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 intellectual property rights (“IPR”), i

8、ncluding 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 holder thereof is requested, all in a

9、ccordance 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 are instead left to the parties involved

10、, 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 or its contents. If the Document cont

11、ains 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 reference consists of mandatory, altern

12、ate or optional elements (as defined in the TIA Procedures for American National Standards) 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) TIAs policy of encouragement

13、of voluntary disclosure (see TIA Procedures for American National Standards Annex C.1.2.3) 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 TI

14、A 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

15、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 INTELLECTUAL PRO

16、PERTY 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

17、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, INCIDENTAL OR CONSEQ

18、UENTIAL 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 DA

19、MAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 2 of 60 This is a draft oneM2M document and should not be relied upon; the final version, i

20、f any, will be made available by oneM2M Partners Type 1. About oneM2M The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad o

21、f devices in the field with M2M application servers worldwide. More information about oneM2M may be found at: http/www.oneM2M.org Copyright Notification No part of this document may be reproduced, in an electronic retrieval system or otherwise, except as authorized by written permission. The copyrig

22、ht and the foregoing restriction extend to reproduction in all media. 2015, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC). All rights reserved. Notice of Disclaimer the final version, if any, will be made available by oneM2M Partners Type 1. Contents 1 Scope 6 2 References 6 2.1 Nor

23、mative references . 6 2.2 Informative references . 7 3 Definitions 7 4 Conventions . 7 5 OMA DM 1.3 and OMA DM 2.0 . 7 5.1 Mapping of basic data types . 7 5.2 Mapping of Identifiers 8 5.3 Mapping of resources . 8 5.3.1 General Mapping Assumptions . 9 5.3.2 Resource firmware . 9 5.3.3 Resource softwa

24、re 9 5.3.4 Resource memory 9 5.3.5 Resource areaNwkInfo . 10 5.3.6 Resource areaNwkDeviceInfo 10 5.3.7 Resource battery 10 5.3.8 Resource deviceInfo . 11 5.3.9 Resource deviceCapability . 11 5.3.10 Resource reboot . 11 5.3.11 Resource eventLog . 12 5.3.12 Resource cmdhPolicy . 12 5.3.12.1 Resource a

25、ctiveCmdhPolicy . 13 5.3.12.2 Resource cmdhDefaults 13 5.3.12.3 Resource cmdhDefEcValues . 13 5.3.12.4 Resource cmdhEcDefParamValues . 14 5.3.12.5 Resource cmdhLimits . 14 5.3.12.6 Resource cmdhNetworkAccessRules 15 5.3.12.7 Resource cmdhNwAccessRule . 15 5.3.12.8 Resource cmdhBuffer . 16 5.4 Mappin

26、g of procedures for management 16 5.4.1 Mapping for Resource Primitives 16 5.4.1.1 Create Primitive for Resource . 16 5.4.1.1.1 Create Response Status Code Mapping 16 5.4.1.2 Retrieve Primitive for Resource 18 5.4.1.2.1 Retrieve Response Status Code Mapping . 18 5.4.1.3 Update Primitive for Resource

27、 20 5.4.1.3.1 Update Primitive for Replacing Data in the Management Object 20 5.4.1.3.2 Update Primitive for Executing Management Commands 22 5.4.1.4 Delete Primitive for Resource . 24 5.4.1.4.1 Delete Response Status Code Mapping 24 5.4.1.5 Notify Primitive Mapping . 25 5.4.1.5.1 Subscribe Procedur

28、e Mapping for OMA DM 1.3 . 25 5.4.1.5.2 Subscribe Procedure Mapping for OMA DM 2.0 . 25 5.4.1.5.3 Notification Procedure Mapping for OMA DM 1.3 and OMA DM 2.0 26 5.4.2 Management Resource Specific Procedure Mapping . 26 5.4.2.1 Resource firmware 26 5.4.2.2 Resource software 27 5.4.2.3 Resource memor

29、y . 28 5.4.2.4 Resource areaNwkInfo . 28 5.4.2.5 Resource areaNwkDeviceInfo. 28 5.4.2.6 Resource battery . 28 5.4.2.7 Resource deviceInfo . 28 5.4.2.8 Resource deviceCapability 28 5.4.2.9 Resource reboot 29 oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 4 of 60 This is a draft o

30、neM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1. 5.4.2.10 Resource eventLog . 29 5.5 DM Server Interactions 29 5.5.1 Communication Session Establishment . 29 5.5.2 Translation of Requests and Responses between IN-CSE and DM Se

31、rver . 30 5.5.3 Discovery and Subscription for management objects 30 5.5.4 Access Control Management 30 5.6 New Management Objects . 30 5.6.1 M2M CMDH Policies MO (MCMDHMO) . 30 6 OMA Lightweight M2M 1.0 41 6.1 Mapping of basic data types . 41 6.2 Mapping of Identifiers 41 6.2.1 Device identifier .

32、41 6.2.2 Object identifier 41 6.2.3 Object Instance Identifier 41 6.3 Mapping of resources . 42 6.3.1 General Mapping Assumptions . 42 6.3.2 Resource firmware . 42 6.3.3 Resource software 42 6.3.4 Resource memory 43 6.3.5 Resource areaNwkInfo . 43 6.3.6 Resource areaNwkDeviceInfo 44 6.3.7 Resource b

33、attery 44 6.3.8 Resource deviceInfo . 44 6.3.9 Resource deviceCapability . 45 6.3.10 Resource reboot . 45 6.3.11 Resource eventLog . 46 6.3.12 Resource cmdhPolicy . 46 6.3.12.1 Resource activeCmdhPolicy . 47 6.3.12.2 Resource cmdhDefaults 47 6.3.12.3 Resource cmdhDefEcValues . 48 6.3.12.4 Resource c

34、mdhEcDefParamValues . 48 6.3.12.5 Resource cmdhLimits . 49 6.3.12.6 Resource cmdhNetworkAccessRules 49 6.3.12.7 Resource cmdhNwAccessRule . 50 6.3.12.8 Resource cmdhBuffer . 50 6.4 Mapping of procedures for management 51 6.4.1 Create primitive for Resource . 51 6.4.2 Retrieve primitive for Resource

35、51 6.4.3 Update primitive for Resource 52 6.4.3.1 Update primitive for replacing data . 52 6.4.3.2 Update primitive for execution operation. 52 6.4.4 Delete primitive for Resource . 52 6.4.5 Notify Primitive for Resource . 53 6.4.5.1 Notify Primitive mapping for subscription to Resource attributes 5

36、3 6.4.5.2 Notify Primitive mapping for subscription cancellation to Resource attributes 53 6.4.5.3 Notify Primitive mapping for Notification . 53 6.4.6 Management Resource Specific Procedure Mapping . 54 6.4.6.1 Resource firmware 54 6.4.6.2 Resource software 54 6.4.6.3 Resource memory . 54 6.4.6.4 R

37、esource battery . 54 6.4.6.5 Resource deviceInfo . 54 6.4.6.6 Resource deviceCapability 54 6.4.6.7 Resource reboot 55 6.5 LWM2M Server Interactions 55 6.5.1 Communication Session Establishment . 55 6.5.2 Translation of Requests and Responses between IN-CSE and LWM2M Server 55 6.5.3 Discovery and Sub

38、scription for LWM2M Objects 55 6.5.4 Access Control Management 56 6.6 New LWM2M Objects . 56 6.6.1 LwM2M CMDH Policy Objects . 56 oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 5 of 60 This is a draft oneM2M document and should not be relied upon; the final version, if any, will

39、 be made available by oneM2M Partners Type 1. 6.6.1.1 CmdhPolicy Object . 57 6.6.1.2 ActiveCmdhPolicy Object . 57 6.6.1.3 CmdhDefaults Object . 57 6.6.1.4 CmdhDef ECValues Object . 57 6.6.1.5 CmdhDefaultsECParamValues Object 57 6.6.1.6 CmdhLimits Object 58 6.6.1.7 CmdhNetworkAccessRules Object . 58

40、6.6.1.8 CmdhNwAccessRule Object 58 6.6.1.9 CmdhBuffer Object 59 History 60 oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 6 of 60 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1. 1 Scope T

41、he present document specifies the protocol translation and mappings between the oneM2M Service layer and the management technologies specified by OMA such as OMA DM 1.3, OMA DM 2.0 and OMA LightweightM2M. Note that OMA DM 1.3 and OMA DM 2.0 are collectively referenced as OMA DM in the present docume

42、nt. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (in

43、cluding any amendments) applies. The following referenced documents are necessary for the application of the present document. 1 oneM2M TS-0001: “Functional Architecture“. 2 oneM2M TS-0004: “Service Layer Core Protocol Specification“. 3 “OMA Device Management Protocol“, Version 1.3, Open Mobile Alli

44、ance. NOTE: Available at http:/www.openmobilealliance.org/. 4 “OMA Device Management Protocol“, Version 2.0, Open Mobile Alliance. NOTE: Available at http:/www.openmobilealliance.org/. 5 “OMA LightweightM2M“, Version 1.0, Open Mobile Alliance. NOTE: Available at http:/www.openmobilealliance.org/. 6

45、“OMA Diagnostics and Monitoring Management Object Framework“, Version 1.2, Open Mobile Alliance. NOTE: Available at http:/www.openmobilealliance.org/. 7 “OMA Firmware Update Management Object“, Version 1.0.2, Open Mobile Alliance. NOTE: Available at http:/www.openmobilealliance.org/. 8 “OMA Software

46、 Component Management Object“, Version 1.0, Open Mobile Alliance. NOTE: Available at http:/www.openmobilealliance.org/. 9 ETSI TS 103 092: “Machine-to-Machine communications (M2M); OMA DM compatible Management Objects for ETSI M2M“. 10 “OMA Device Capability Management Object “, Version 1.0, Open Mo

47、bile Alliance. NOTE: Available at http:/www.openmobilealliance.org/. 11 “OMA Management Interface to M2M Requirements“, Version 1.0, Open Mobile Alliance. NOTE: Available at http:/www.openmobilealliance.org/. 12 ISO 8601:2000: “Data elements and interchange formats - Information interchange - Repres

48、entation of dates and times“. NOTE: Available at http:/www.iso.ch/. 13 “XML Schema Part 2: Datatypes“, W3C Recommendation 02 May 2001. oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 7 of 60 This is a draft oneM2M document and should not be relied upon; the final version, if any,

49、 will be made available by oneM2M Partners Type 1. NOTE: Available at http:/www.w3.org/XML/Schema/. 14 “A Universally Unique Identifier (UUID) URN Namespace“, P. Leach, et al. July 2005. NOTE: Available at http:/www.ietf.org/rfc/rfc4122.txt. 15 3GPP TS 23.003: “Numbering, addressing and identification“. 16 BBF: “TR-069 CPE WAN Management Protocol“ Issue: 1 Amendment 5, November 2013. 17 IETF RFC 7252: “The Constra