ETSI TS 118 124 V2.0.0 (2016-09)

oneM2M; OIC Interworking (oneM2M TS-0024 version 2.0.0 Release 2)

DTS/oneM2M-000024

General Information

• Status: Published
• Publication Date: 13-Sep-2016
• Technical Committee: oneM2M - oneM2M
• Current Stage: 12 - Completion
• Due Date: 03-Oct-2016
• Completion Date: 14-Sep-2016

Standards Content (Sample)

ETSI TS 118 124 V2.0.0 (2016-09)






TECHNICAL SPECIFICATION
oneM2M;
OIC Interworking
(oneM2M TS-0024 version 2.0.0 Release 2)

---------------------- Page: 1 ----------------------
oneM2M TS-0024 version 2.0.0 Release 2 2 ETSI TS 118 124 V2.0.0 (2016-09)



Reference
DTS/oneM2M-000024
Keywords
interworking, IoT, M2M

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present 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 versions 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 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
No 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 foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2016.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the 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

---------------------- Page: 2 ----------------------
oneM2M TS-0024 version 2.0.0 Release 2 3 ETSI TS 118 124 V2.0.0 (2016-09)
Contents
Intellectual Property Rights . 4
Foreword . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions and abbreviations . 5
3.1 Definitions . 5
3.2 Abbreviations . 6
4 Conventions . 6
5 Architecture Model. 6
5.1 Introduction . 6
5.2 Interworking Reference Model . 6
5.3 Function of Interworking Proxy Entity . 7
5.4 Types of Interworking . 8
6 Architectural Aspects . 9
6.1 Introduction . 9
6.2 OIC Device Lifecycle . 9
6.2.1 Introduction. 9
6.2.2 OIC Device Representation . 10
6.2.2.1 Introduction . 10
6.2.2.2 OIC Device Identification . 10
6.2.2.3 OIC Device Discovery and Forget . 10
6.2.2.4 Configuration of CMDH Policies . 11
6.3 OIC Resource Discovery . 11
6.3.1 Introduction. 11
6.3.2 OIC Resource Representation . 11
6.3.2.1 Introduction . 11
6.3.2.2 OIC Resource Identification. 12
6.3.2.3 OIC Resource Discovery and Forget . 12
6.4 OIC Interworking Procedure . 13
6.4.1 Introduction. 13
6.4.2 Interworked Resource Settings . 13
6.4.3 Further Considerations for Interworking . 13
6.4.4 Retrieve Procedure . 14
6.5 OIC Resource Subscription and Notification . 15
6.5.1 Introduction. 15
6.5.2 OIC Subscription (Observe Request) Procedure . 15
6.5.3 OIC Notification (Observe Response) Procedure . 16
6.6 OIC Device Management . 16
6.7 OIC Provisioning and Security . 16
6.7.1 Introduction. 16
6.7.2 OIC Interworking Access Control Policy . 16
6.8 IPE Management . 17
6.8.1 IPE Administration . 17
6.8.2 Maintaining IPE Context . 17
7 Transparent Interworking Function . 17
7.1 Introduction . 17
7.2 Attribute Mapping for the Content Sharing Resources . 18
History . 19

ETSI

---------------------- Page: 3 ----------------------
oneM2M TS-0024 version 2.0.0 Release 2 4 ETSI TS 118 124 V2.0.0 (2016-09)
Intellectual 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 (IPRs); 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 (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
server) 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

---------------------- Page: 4 ----------------------
oneM2M TS-0024 version 2.0.0 Release 2 5 ETSI TS 118 124 V2.0.0 (2016-09)
1 Scope
The present document specifies the 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 Devices 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 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 hyperlinks 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: "oneM2M; 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 number) 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 guarantee
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.
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 TS 118 101 [2].
ETSI

---------------------- Page: 5 ----------------------
oneM2M TS-0024 version 2.0.0 Release 2 6 ETSI TS 118 124 V2.0.0 (2016-09)
3.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", "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 describes interworking using specialized Interworking Proxy application Entity (IPE). The present
document describes the OIC IPE that supports the following scenarios.
Hybrid Application OIC Application
(OIC Server+AE) (OIC Server)
OIC
OIC
Interface
Interface
OIC Client
OIC Client
IPE
IPE
Mca
Mca
Mca
(note 1)
CSE(s)

Figure 5.1-1: OIC Interworking Scenarios
In the scenarios depicted in Figure 5.1-1, the Hybrid and OIC Applications represent applications 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 Architecture's reference model in ETSI TS 118 101 [2];
augmenting the ETSI TS 118 101 [2] reference model with capabilities provided by the OIC IPE.
ETSI

---------------------- Page: 6 ----------------------
oneM2M TS-0024 version 2.0.0 Release 2 7 ETSI TS 118 124 V2.0.0 (2016-09)
OIC Application
AE
(OIC Server)
OIC Protocol
OIC Client
Mca
IPE
Mca
Mcc/Mcc’
CSE CSE
ASN/MN/IN MN/IN

NOTE: 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 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 .
ETSI

---------------------- Page: 7 ----------------------
oneM2M TS-0024 version 2.0.0 Release 2 8 ETSI TS 118 124 V2.0.0 (2016-09)

Figure 5.3-1: OIC 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 Interworking
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

---------------------- Page: 8 ----------------------
oneM2M TS-0024 version 2.0.0 Release 2 9 ETSI TS 118 124 V2.0.0 (2016-09)
OIC
provides
AE
Application
OIC
(OIC Server)
Re sou rce s
uses
OIC Protocol
uses


OIC
OIC Client
Re sour ce s
encapsulates
Mca
(Serialized)
IPE
Mca
Mcc/Mcc’
CSE1 CSE2

Figure 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 Resources 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 Resource from the Content Sharing Resource for the AE's 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 following 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 when 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

---------------------- Page: 9 ----------------------
oneM2M TS-0024 version 2.0.0 Release 2 10 ETSI TS 118 124 V2.0.0 (2016-09)
6.2.2 OIC Device Representation
6.2.2.1 Introduction
OIC Device 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 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 Specification [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
Device's resource's M2M-Node-ID should be the same as the "di" property. Also 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 resource's M2M-Node-ID is implementation specific. In all
deployment scenarios, the resource is linked with the resource as described 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
...