ETSI TS 118 124-2016 oneM2M OIC Interworking (V2 0 0 oneM2M TS-0024 version 2 0 0 Release 2)《oneM2M(物联网协议联盟) OIC 网路互通(V2 0 0 oneM2M TS-0024 版本2 0 0 发行版本2)》.pdf

《ETSI TS 118 124-2016 oneM2M OIC Interworking (V2 0 0 oneM2M TS-0024 version 2 0 0 Release 2)《oneM2M(物联网协议联盟) OIC 网路互通(V2 0 0 oneM2M TS-0024 版本2 0 0 发行版本2)》.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 118 124-2016 oneM2M OIC Interworking (V2 0 0 oneM2M TS-0024 version 2 0 0 Release 2)《oneM2M(物联网协议联盟) OIC 网路互通(V2 0 0 oneM2M TS-0024 版本2 0 0 发行版本2)》.pdf（19页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 118 124 V2.0.0 (2016-09) oneM2M; OIC Interworking (oneM2M TS-0024 version 2.0.0 Release 2) TECHNICAL SPECIFICATION ETSI ETSI TS 118 124 V2.0.0 (2016-09)2oneM2M TS-0024 version 2.0.0 Release 2Reference DTS/oneM2M-000024 Keywords interworking, IoT, M2M 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx 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 N

6、o part may 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 f

7、oregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. 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 t

8、he benefit 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 TS 118 124 V2.0.0 (2016-09)3oneM2M TS-0024 version 2.0.0 Release 2Contents Intellectual Property Rights 4g3Foreword . 4g31 Scope 5g32 Referen

9、ces 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Conventions 6g35 Architecture Model. 6g35.1 Introduction 6g35.2 Interworking Reference Model . 6g35.3 Function of Interworking Proxy Entity 7g35.4 Types

10、 of Interworking 8g36 Architectural Aspects . 9g36.1 Introduction 9g36.2 OIC Device Lifecycle . 9g36.2.1 Introduction. 9g36.2.2 OIC Device Representation 10g36.2.2.1 Introduction . 10g36.2.2.2 OIC Device Identification . 10g36.2.2.3 OIC Device Discovery and Forget 10g36.2.2.4 Configuration of CMDH P

11、olicies . 11g36.3 OIC Resource Discovery 11g36.3.1 Introduction. 11g36.3.2 OIC Resource Representation . 11g36.3.2.1 Introduction . 11g36.3.2.2 OIC Resource Identification 12g36.3.2.3 OIC Resource Discovery and Forget 12g36.4 OIC Interworking Procedure 13g36.4.1 Introduction. 13g36.4.2 Interworked R

12、esource Settings . 13g36.4.3 Further Considerations for Interworking 13g36.4.4 Retrieve Procedure 14g36.5 OIC Resource Subscription and Notification . 15g36.5.1 Introduction. 15g36.5.2 OIC Subscription (Observe Request) Procedure . 15g36.5.3 OIC Notification (Observe Response) Procedure . 16g36.6 OI

13、C Device Management . 16g36.7 OIC Provisioning and Security . 16g36.7.1 Introduction. 16g36.7.2 OIC Interworking Access Control Policy . 16g36.8 IPE Management 17g36.8.1 IPE Administration . 17g36.8.2 Maintaining IPE Context 17g37 Transparent Interworking Function 17g37.1 Introduction 17g37.2 Attrib

14、ute Mapping for the Content Sharing Resources 18g3History 19g3ETSI ETSI TS 118 124 V2.0.0 (2016-09)4oneM2M TS-0024 version 2.0.0 Release 2Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these e

15、ssential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest upd

16、ates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried 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 ser

17、ver) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Partnership Project oneM2M (oneM2M). ETSI ETSI TS 118 124 V2.0.0 (2016-09)5oneM2M TS-0024 version 2.0.0 Release 21 Scope The present document specifies th

18、e interworking technologies for oneM2M and OIC interworking using the architecture identified in annex F of ETSI TS 118 101 2 for the following scenario: Interworking using oneM2M Resource Types for transparent transport of encoded OIC Resources and commands in oneM2M Resource Types between OIC Devi

19、ces and M2M Applications. NOTE: The present document limits Content Sharing Resources to and resources. 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

20、cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https:/docbox.etsi.org/Reference/. NOTE: While any hyperl

21、inks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. 1 ETSI TS 118 111: “oneM2M; Common Terminology (oneM2M TS-0011)“. 2 ETSI TS 118 101: “oneM

22、2M; Functional Architecture (oneM2M TS-0001)“. 3 OIC-Core-Specification-v1.0.0: “OIC Core Specification“. 4 ETSI TS 118 103: “oneM2M; Security Solutions (oneM2M TS-0003)“. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version nu

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

24、ee their 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 http:/www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf.

25、3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI TS 118 111 1, ETSI TS 118 101 2 apply. A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TS 118 111 1 and ETSI

26、 TS 118 101 2. ETSI ETSI TS 118 124 V2.0.0 (2016-09)6oneM2M TS-0024 version 2.0.0 Release 23.2 Abbreviations For the purposes of the present document, the following abbreviations apply: IPE Interworking Proxy Entity OIC Open Interconnect Consortium 4 Conventions The key words “Shall“, “Shall not“, “

27、May“, “Need not“, “Should“, “Should not“ in the present document are to be interpreted as described in the oneM2M Drafting Rules i.1. 5 Architecture Model 5.1 Introduction The architecture model followed in the present document is based on the architecture model in Annex F of ETSI TS 118 101 2. It d

28、escribes interworking using specialized Interworking Proxy application Entity (IPE). The present document describes the OIC IPE that supports the following scenarios. Figure 5.1-1: OIC Interworking Scenarios In the scenarios depicted in Figure 5.1-1, the Hybrid and OIC Applications represent applica

29、tions that implement the OIC Server role defined in the OIC Protocol 3. 5.2 Interworking Reference Model The OIC Interworking reference model utilizes the Functional Architectures reference model in ETSI TS 118 101 2; augmenting the ETSI TS 118 101 2 reference model with capabilities provided by the

30、 OIC IPE. g44g455g271g396g349g282g3g4g393g393g367g349g272g258g410g349g381g374g3g894g75g47g18g3g94g286g396g448g286g396g1085g4g28g895g3g18g94g28g894g400g895g3g75g47g18g3g47g374g410g286g396g296g258g272g286g3g68g272g258g3g75g47g18g3g18g367g349g286g374g410g3g47g87g28g3g68g272g258g3g3g894g374g381g410g286g

31、3g1005g895g3g75g47g18g3g4g393g393g367g349g272g258g410g349g381g374g3g894g75g47g18g3g94g286g396g448g286g396g895g3g75g47g18g3g18g367g349g286g374g410g3g47g87g28g3g68g272g258g3g75g47g18g3g47g374g410g286g396g296g258g272g286g3ETSI ETSI TS 118 124 V2.0.0 (2016-09)7oneM2M TS-0024 version 2.0.0 Release 2NOTE:

32、 The AE in the reference model could be registered with the same CSE as the OIC IPE. Figure 5.2-1: OIC Reference Model 5.3 Function of Interworking Proxy Entity The OIC IPE participation in the OIC Protocol as described in clause 5 does so in the role of an OIC Client to which OIC Applications (OIC

33、Servers) interact. For each OIC Server (Endpoint) that is maintained by the OIC Client in the OIC IPE, the OIC IPE shall instantiate and maintains an instance of a Resource of type . g75g47g18g3g4g393g393g367g349g272g258g410g349g381g374g3g894g75g47g18g3g94g286g396g448g286g396g895g3g18g94g28g3g75g47g

34、18g3g87g396g381g410g381g272g381g367g3g75g47g18g3g18g367g349g286g374g410g3g47g87g28g3g68g272g258g3g4g28g3g68g272g258g4g94g69g876g68g69g876g47g69g3g18g94g28g3g68g272g272g876g68g272g272g859g3g68g69g876g47g69g3ETSI ETSI TS 118 124 V2.0.0 (2016-09)8oneM2M TS-0024 version 2.0.0 Release 2Figure 5.3-1: OIC

35、IPE Architecture Mapping OIC Servers to AEs provides the following: 1) Application Registry: OIC Servers can now be registered as oneM2M Applications. 2) Service Subscriptions: OIC Servers can now be attached to M2M Service Subscriptions just like any other oneM2M Application. 5.4 Types of Interwork

36、ing OIC IPEs provide the following types of interworking in this present document: 1) Interworking using the resource for transparent transport of encoded OIC Resources that are available to AEs as depicted in Figure 5.4-1. ETSI ETSI TS 118 124 V2.0.0 (2016-09)9oneM2M TS-0024 version 2.0.0 Release 2

37、uni004Funi0049uni0043uni0041uni0070uni0070uni006Cuni0069uni0063uni0061uni0074uni0069uni006Funi006Euni0020uni0028uni004Funi0049uni0043uni0020uni0053uni0065uni0072uni0076uni0065uni0072uni0029uni0043uni0053uni0045uni0031uni004Funi0049uni0043uni0020uni0050uni0072uni006Funi0074uni006Funi0063uni006Funi006

38、Cuni004Funi0049uni0043uni0020uni0043uni006Cuni0069uni0065uni006Euni0074uni0049uni0050uni0045uni004Duni0063uni0061uni004Duni0063uni0061uni0043uni0053uni0045uni0032uni004Duni0063uni0063uni002Funi004Duni0063uni0063uni2019uni003Cuni0063uni006Funi006Euni0074uni0061uni0069uni006Euni0065uni0072uni003Euni00

39、4Funi0049uni0043uni0052uni0065uni0073uni006Funi0075uni0072uni0063uni0065uni0073uni0028uni0053uni0065uni0072uni0069uni0061uni006Cuni0069uni007Auni0065uni0064uni0029uni003Cuni0063uni006Funi006Euni0074uni0061uni0069uni006Euni0065uni0072uni003Euni004Funi0049uni0043uni0052uni0065uni0073uni006Funi0075uni0

40、072uni0063uni0065uni0073encapsulatesprovidesusesusesuni0041uni0045Figure 5.4-1: OIC Transparent Interworking Function In Figure 5.4-1, the OIC Resources are provided by the OIC Application to the OIC IPE using the OIC Protocol 3. The OIC IPE then encapsulates the OIC Resources in Content Sharing Res

41、ources and then hosts the Content Sharing Resources in a CSE using the Mca reference points for use by AEs. The AE accesses the Content Sharing Resource from the CSE that hosts the resource using the Mca reference point. Once the AE receives the Content Sharing Resource, the AE extracts the OIC Reso

42、urce from the Content Sharing Resource for the AEs purpose. 6 Architectural Aspects 6.1 Introduction The OIC IPE participation in the OIC Protocol as described in clause 5 does so in the role of an OIC Client to which OIC Applications (OIC Servers) interact. As an OIC Client, the IPE provides the fo

43、llowing Architecture Aspects based on the OIC Protocol Aspects: OIC Device Lifecycle OIC Resource Discovery OIC Interworking Procedure OIC Subscription Notification OIC Device Management OIC Provisioning and Security 6.2 OIC Device Lifecycle 6.2.1 Introduction As the OIC IPE discovers OIC Devices wh

44、en the OIC IPE interacts with the OIC Server over the OIC protocol, the OIC IPE shall maintain the associated resources in the CSE that represents the OIC Device. ETSI ETSI TS 118 124 V2.0.0 (2016-09)10oneM2M TS-0024 version 2.0.0 Release 26.2.2 OIC Device Representation 6.2.2.1 Introduction OIC Dev

45、ice provides the management and control functions for any M2M application. As such, the CSE that hosts the M2M Applications shall represent the OIC Device as a resource (OIC Device resource). The OIC physical Device that hosts the logical OIC Device shall be represented as a resource. The properties

46、 carried by OIC Device (i.e. device type) shall be translated into the labels attribute of the Resource as separate entries with the following format: OIC-DT: Device Type (e.g. oic.d.light) 6.2.2.2 OIC Device Identification OIC Devices are identified by their “di“ property as described in OIC Core S

47、pecification 3. The “di“ property is used as the AE-ID of the associated resource that represents the OIC Device. In most deployment scenarios, OIC physical Devices host one (1) OIC Device. In this scenario the OIC physical Devices resources M2M-Node-ID should be the same as the “di“ property. Also

48、the deviceIdentifier attribute of resource should be same as the “di“ property. When an OIC physical Device hosts more than one (1) OIC Device, the determination of the resources M2M-Node-ID is implementation specific. In all deployment scenarios, the resource is linked with the resource as describe

49、d in ETSI TS 118 101 2. As the OIC Device is represented as an resource and a OIC Resource is represented as a Content Sharing Resource in the M2M Service Layer, a reference shall be made between the resource that represents the OIC Device and the Content Sharing Resources which represents the list of OIC Resources available in that OIC Server. In order to identify interworked entities hosted in a CSE for the OIC technology described in this present document, the resource that represents the OIC Device and the Content