ETSI TR 118 506-2015 Study of Management Capability Enablement Technologies for Consideration by oneM2M (V1 0 0)《用于oneM2M考量的管理能力实现技术研究 (V1 0 0)》.pdf

《ETSI TR 118 506-2015 Study of Management Capability Enablement Technologies for Consideration by oneM2M (V1 0 0)《用于oneM2M考量的管理能力实现技术研究 (V1 0 0)》.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 118 506-2015 Study of Management Capability Enablement Technologies for Consideration by oneM2M (V1 0 0)《用于oneM2M考量的管理能力实现技术研究 (V1 0 0)》.pdf（58页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 118 506 V1.0.0 (2015-04) Study of Management Capability Enablement Technologies for Consideration by oneM2M TECHNICAL REPORT ETSI ETSI TR 118 506 V1.0.0 (2015-04) 2 Reference DTR/oneM2M-000006 Keywords architecture, IoT, M2M, management, requirements ETSI 650 Route des Lucioles F-06921 Soph

2、ia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The pr

3、esent document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such ver

4、sions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the

5、current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may

6、 be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing r

7、estriction extend to reproduction in all media. European Telecommunications Standards Institute 2015. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit

8、 of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 118 506 V1.0.0 (2015-04) 3 Contents Intellectual Property Rights 7g3Foreword . 7g31 Scope 8g32 References 8g32.1 Normative references . 8g32.2 Infor

9、mative references 8g33 Definitions and abbreviations . 10g33.1 Definitions 10g33.2 Abbreviations . 10g34 Conventions 11g35 Introduction of existing technologies . 12g35.1 Introduction to OMA DM 12g35.1.1 Description 12g35.1.2 Architecture 13g35.1.3 Reference points . 13g35.1.3.1 Introduction . 13g35

10、.1.3.2 DM-1 DM Client-Server Notification . 13g35.1.3.3 DM-2 DM Client-Server Protocol . 13g35.1.3.4 DM-3 DM Bootstrap Profile via Smart Card 14g35.1.3.5 DM-4 DM Bootstrap Profile OTA 14g35.1.3.6 CP-1 CP Bootstrap Profile 14g35.1.3.7 DM-6 DM Server-Server Interface . 14g35.1.3.8 DM-7,8,9 Client API

11、. 14g35.1.3.9 Procedures . 15g35.1.4 Protocols . 15g35.1.4.1 Protocol Stack . 15g35.1.4.2 Application MO 16g35.1.4.3 DM Protocol 16g35.1.4.4 DM Representation . 16g35.1.4.5 Binding to transports and Transports 16g35.1.5 Functions 16g35.1.5.1 Introduction . 16g35.1.5.2 The MO tree 17g35.1.5.2.1 Stand

12、ard Objects 17g35.1.5.2.2 Other Management Objects . 18g35.2 TR-069 Family of Specifications . 18g35.2.1 Description 18g35.2.2 Architecture 18g35.2.2.1 TR-069 Proxy Management 19g35.2.2.1.1 Proxied Device Deployment Archirecture . 20g35.2.3 Reference points . 20g35.2.4 Protocols . 21g35.2.4.1 ACS to

13、 CPE Protocol 21g35.2.4.2 CPE to BSS . 22g35.2.4.2.1 IPDR Reference Points 23g35.2.4.3 CPE to Device Protocol 23g35.2.4.3.1 UPnP DM Proxy 23g35.2.4.3.2 ZigBee Proxy 24g35.2.5 Functions 25g35.3 Introduction to OMA LightweightM2M (LWM2M) . 26g35.3.1 Description 26g35.3.2 Architecture 27g35.3.3 Referen

14、ce Points . 27g35.3.3.1 Functional Components 27g35.3.3.1.1 LWM2M Server 27g3ETSI ETSI TR 118 506 V1.0.0 (2015-04) 4 5.3.3.1.2 LWM2M Client . 27g35.3.3.2 Interfaces . 27g35.3.4 Protocols . 28g35.3.4.1 Protocol Stack . 28g35.3.4.2 Resource Model 28g35.3.4.3 Interface Descriptions . 29g35.3.4.3.1 Boot

15、strap . 29g35.3.4.3.2 Client Registration . 30g35.3.4.3.3 Device Management and Service Enablement 31g35.3.4.3.4 Information Reporting . 31g35.3.5 Functions 32g35.4 Introduction to OMA Device Management 2.0 32g35.4.1 Description 32g35.4.2 Architecture 33g35.4.3 Reference Points . 33g35.4.3.1 Functio

16、nal Components 33g35.4.3.1.1 DM Client 33g35.4.3.1.2 DM Server . 33g35.4.3.1.3 Web Server Component. 33g35.4.3.1.4 Web Browser Component . 34g35.4.3.1.5 Data Repository . 34g35.4.3.2 Interfaces . 34g35.4.4 Protocol . 34g35.4.4.1 DM Packages 34g35.4.4.2 DM Commands . 35g35.4.5 Functions 35g35.4.5.1 I

17、ntroduction . 35g35.4.5.2 Management Objects supported by OMA DM 2.0 . 36g35.4.5.3 Detailed Comparisons with OMA DM 1.x . 36g35.4.5.4 Protocol Examples 37g36 Gap analysis of existing relevant technolgoies 38g36.1 Management related requirements gap analysis reference . 38g36.2 MGR-001 . 38g36.2.1 Re

18、quirement Description 38g36.2.2 OMA DM 1.3 39g36.2.3 BBF TR-069 . 39g36.2.4 OMA LWM2M . 39g36.2.5 OMA DM 2.0 40g36.3 MGR-002 . 40g36.3.1 Requirement Description 40g36.3.2 OMA DM 1.3 and OMA DM 2.0 . 40g36.3.3 BBF TR-069 . 40g36.3.4 OMA LWM2M . 41g36.4 MGR-003 . 41g36.4.1 Requirement Description 41g3

19、6.4.2 OMA DM 1.3 and OMA DM 2.0 . 41g36.4.3 BBF TR-069 . 41g36.4.4 OMA LWM2M . 42g36.5 MGR-004 . 42g36.5.1 Requirement Description 42g36.5.2 OMA DM 1.3 and OMA DM 2.0 . 42g36.5.3 BBF TR-069 . 42g36.5.4 OMA LWM2M . 42g36.6 MGR-005 . 43g36.6.1 Requirement Description 43g36.6.2 OMA DM 1.3 and OMA DM 2.

20、0 . 43g36.6.3 BBF TR-069 . 43g36.6.4 OMA LWM2M . 43g36.7 MGR-006 . 43g36.7.1 Requirement Description 43g36.7.2 OMA DM 1.3 and OMA DM 2.0 . 43g3ETSI ETSI TR 118 506 V1.0.0 (2015-04) 5 6.7.3 BBF TR-069 . 43g36.7.4 OMA LWM2M . 44g36.8 MGR-007 . 44g36.8.1 Requirement Description 44g36.8.2 OMA DM 1.3 and

21、 OMA DM 2.0 . 44g36.8.3 BBF TR-069 . 44g36.8.4 OMA LWM2M . 45g36.9 MGR-008 . 45g36.9.1 Requirement Description 45g36.9.2 OMA DM 1.3 and OMA DM 2.0 . 45g36.9.3 BBF TR-069 . 45g36.9.4 OMA LWM2M . 45g36.10 MGR-009 . 45g36.10.1 Requirement Description 45g36.10.2 OMA DM 1.3 and OMA DM 2.0 . 45g36.10.3 BB

22、F TR-069 . 46g36.10.4 OMA LWM2M . 46g36.11 MGR-010 . 46g36.11.1 Requirement Description 46g36.11.2 OMA DM 1.3 and OMA DM 2.0 . 46g36.11.3 BBF TR-069 . 46g36.11.4 OMA LWM2M . 46g36.12 MGR-011 . 46g36.12.1 Requirement Description 46g36.12.2 OMA DM 1.3 and OMA DM 2.0 . 46g36.12.3 BBF TR-069 . 47g36.12.

23、4 OMA LWM2M . 47g36.13 MGR-012 . 47g36.13.1 Requirement Description 47g36.13.2 OMA DM 1.3 and OMA DM 2.0 . 47g36.13.3 BBF TR-069 . 47g36.13.4 OMA LWM2M . 47g36.14 MGR-013 . 48g36.14.1 Requirement Description 48g36.14.2 OMA DM 1.3 and OMA DM 2.0 . 48g36.14.3 BBF TR-069 . 48g36.14.4 OMA LWM2M . 48g36.

24、15 MGR-014 . 48g36.15.1 Requirement Description 48g36.15.2 OMA DM 1.3 and OMA DM 2.0 . 48g36.15.3 BBF TR-069 . 49g36.15.4 OMA LWM2M . 49g36.16 MGR-015 . 49g36.16.1 Requirement Description 49g36.16.2 OMA DM 1.3 and OMA DM 2.0 . 49g36.16.3 BBF TR-069 . 49g36.16.4 OMA LWM2M . 49g36.17 MGR-016 . 49g36.1

25、7.1 Requirement Description 49g36.17.2 OMA DM 1.3 and OMA DM 2.0 . 50g36.17.3 BBF TR-069 . 50g36.17.4 OMA LWM2M . 50g36.18 MGR-017 . 50g36.18.1 Requirement Description 50g36.18.2 OMA DM 1.3 and OMA DM 2.0 . 50g36.18.3 BBF TR-069 . 50g36.18.4 OMA LWM2M . 51g37 Device Management Deployment Scenarios 5

26、1g37.1 Introduction 51g37.2 Current Management Deployment Scenarios . 51g37.2.1 Managed Device Using Network Operator Management . 51g3ETSI ETSI TR 118 506 V1.0.0 (2015-04) 6 7.2.2 Managed Device Using Service Provider Management . 52g37.3 Possible Future Management Deployment Scenarios 52g37.3.1 Sh

27、ared Managed Device Using Network Operator Management . 52g37.3.2 Shared Managed Device Using Service Provider Management . 53g37.3.3 Shared Managed Device Using Separate Management 54g37.3.4 Federated Managed Device Using Separate Management 55g37.3.5 Conclusions To Guide the Device Management Arch

28、itecture 55g37.4 Architectural Framework Considerations . 55g3Annex A: Guidance for Managing Resource Constrained Devices . 56g3A.1 Classification of Resource Constrained Devices 56g3A.2 Device Classes and Management Technologies . 57g3History 58g3ETSI ETSI TR 118 506 V1.0.0 (2015-04) 7 Intellectual

29、 Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPR

30、s); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been ca

31、rried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Partnership P

32、roject oneM2M (oneM2M). ETSI ETSI TR 118 506 V1.0.0 (2015-04) 8 1 Scope The present document describes and collects the state-of-art of the existing technologies on management capability, evaluates if the technologies can match the requirements defined in oneM2M, analyzes how the technologies can le

33、verage the design of the architecture of oneM2M. 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

34、 latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of pub

35、lication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. Not applicable. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number

36、) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee th

37、eir long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 oneM2M Drafting Rules. NOTE: Available at ftp:/ftp.onem2m.org/Others/Rules_Pages/oneM2M-Drafting-Rules-V1_0.

38、doc. i.2 OMA-AD-DM-V1_3: “Device Management Architecture“. i.3 OMA-TS-DM-Protocol-V1_3: “OMA Device Management Protocol“. i.4 OMA-TS-DM-RepPro-V1_3: “OMA Device Management Representation Protocol“. i.5 OMA-TS-DM-StdObj-V1_3: “OMA Device Management Standardized Objects“. i.6 OMA-TS-DCMO-V1_0: “Device

39、 Capability Management Object“. i.7 OMA-TS-LAWMO-V1_0: “Lock and Wipe Management Object“. i.8 OMA-TS-DM-FUMO-V1_0: “Firmware Update Management Object“. i.9 OMA-TS-DM-SCOMO-V1_0: “Software Component Management Object“, Version 1.0. i.10 OMA-TS-GwMO-V1_0: “Gateway Management Object Technical Specifica

40、tion“, Version 1.0. i.11 OMA-TS-DiagMonFunctions-1_0: “DiagMon Functions Supplemental Specification“, Version 1.0. i.12 OMA-AD-GwMO-V1_1-20130214-D: “Gateway Management Object Architecture“. ETSI ETSI TR 118 506 V1.0.0 (2015-04) 9 i.13 BBF TR-069: “CPE WAN Management Protocol“, Issue: 1 Amendment 4,

41、 July 2011. i.14 BBF MR-239: “Broadband Forum Value Proposition for Connected Home“, Issue: 1, April 2011. i.15 BBF TR-232: “Bulk Data Collection“, Issue: 1, May 2012. i.16 TMForum IPDR Service Specification Design Guide, Version 3.8, Release 1.0, 2009. i.17 OMA-RD-LightweightM2M-V1_0: “OMA Lightwei

42、ght Machine to Machine Requirement“. i.18 OMA-AD-LightweightM2M-V1_0: “OMA Lightweight Machine to Machine Architecture“. i.19 OMA-TS-LightweightM2M-V1_0: “OMA Lightweight Machine to Machine Protocol“ (work on progress). i.20 draft-ietf-core-coap-14 (work in progress), Sept 2012: “Constrained Applica

43、tion Protocol (CoAP)“, Z. Shelby, K. Hartke, C. Bormann and B. Frank. i.21 IETF RFC 6347 (January 2012): “Datagram Transport Layer Security Version 1.2“, E. Rescorla and N. Modadugu. i.22 oneM2M-TS-0002 (V0.5.2): “oneM2M Requirements“. i.23 ETSI TS 103 092 (V2.1.1): “Machine-to-Machine communication

44、s (M2M); OMA DM compatible Management Objects for ETSI M2M“. i.24 OMA-ER-DMClientAPIfw-V1_0: “DM Client Side API Framework (DMClientAPIfw)“. i.25 IETF draft-ietf-lwig-terminology-05 (July 09 2012): “Terminology for Constrained Node Networks“, C. Bormann and M. Ersue. i.26 IEEE Communication Magazine

45、 (Vol.50, Issue.12) (Dec 2012): “Management of Resource Constrained Devices in the Internet of Things“, A. Sehgal, V. Perelman, S Kuryla and J Schonwalder. i.27 BBF TR-131: “ACS Northbound Interface Requirements“, Issue:1, November 2009. i.28 BBF TR-143: “Enabling Network Throughput Performance Test

46、s and Statistical Monitoring“, Corrigendum 1, December 2008. i.29 BBF TR-181: “Device Data Model for TR-069“, Issue 2 Amendment 6, November 2012. i.30 BBF TR-135: “Device Data Model for TR-069 Enabled STB“, Amendment 3, November 2012. i.31 BBF TR-104: “Provisioning Parameters for VoIP CPE“, Septembe

47、r 2005. i.32 BBF TR-140: “TR-069 Data Model for Storage Service Enabled Devices“, Issue 1.1, December 2007. i.33 OMA-TS-DM_Security-V1_2_1: “OMA Device Management Security“. i.34 oneM2M TS-0001: “oneM2M Functional Architecture“. i.35 IETF RFC 2616: “Hypertext Transfer Protocol - HTTP/1.1“. i.36 IETF

48、 RFC 5246: “The Transport Layer Security (TLS) Protocol Version 1.2“. ETSI ETSI TR 118 506 V1.0.0 (2015-04) 10 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions.apply: mc: interface between the management server and the mana

49、gement client NOTE: This interface can be realized by the existing device management technologies such as BBF TR-069 i.13, OMA DM, etc. ms: interface between the management adapter and the management server in the underlying network domain or in the M2M service domain for use by other systems NOTE: Using this interface, systems can perform management operations on devices through the management server. mp: interface that is exposed by the proxy management client in the area network for devices that c