ETSI TS 118 101 V3.22.0 (2021-02)

ETSI TS 118 101 V3.22.0 (2021-02)






TECHNICAL SPECIFICATION
oneM2M;
Functional Architecture
(oneM2M TS-0001 version 3.22.0 Release 3)

---------------------- Page: 1 ----------------------
oneM2M TS-0001 version 3.22.0 Release 3 2 ETSI TS 118 101 V3.22.0 (2021-02)



Reference
RTS/oneM2M-000001v3
Keywords
architecture, IoT, M2M

ETSI
650 Route des Lucioles
F-06921 Sophia 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 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 prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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.

© ETSI 2021.
All rights reserved.

DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
oneM2M TS-0001 version 3.22.0 Release 3 3 ETSI TS 118 101 V3.22.0 (2021-02)
Contents
Intellectual Property Rights . 14
Foreword . 14
1 Scope . 15
2 References . 15
2.1 Normative references . 15
2.2 Informative references . 16
3 Definition of terms, symbols and abbreviations . 17
3.1 Terms . 17
3.2 Symbols . 19
3.3 Abbreviations . 19
4 Conventions . 23
5 Architecture Model. 23
5.1 General Concepts . 23
5.2 Architecture Reference Model . 24
5.2.1 Functional Architecture . 24
5.2.2 Reference Points . 25
5.2.2.0 Overview . 25
5.2.2.1 Mca Reference Point . 25
5.2.2.2 Mcc Reference Point . 25
5.2.2.3 Mcn Reference Point . 25
5.2.2.4 Mcc' Reference Point . 25
5.2.2.5 Other Reference Points and Interfaces . 25
6 oneM2M Architecture Aspects . 26
6.1 Configurations supported by oneM2M Architecture . 26
6.2 Common Services Functions . 28
6.2.0 Overview . 28
6.2.1 Application and Service Layer Management . 28
6.2.1.1 General Concepts . 28
6.2.1.2 Detailed Descriptions . 29
6.2.1.2.0 Overview . 29
6.2.1.2.1 Software Management Function . 29
6.2.2 Communication Management and Delivery Handling . 29
6.2.2.1 General Concepts . 29
6.2.2.2 Detailed Descriptions . 30
6.2.3 Data Management and Repository . 30
6.2.3.1 General Concepts . 30
6.2.3.2 Detailed Descriptions . 31
6.2.4 Device Management . 31
6.2.4.1 General Concepts . 31
6.2.4.1.0 Overview . 31
6.2.4.1.1 Device Management using other existing technologies. 32
6.2.4.2 Detailed Descriptions . 35
6.2.4.2.0 Overview . 35
6.2.4.2.1 Device Configuration Function . 36
6.2.4.2.2 Device Diagnostics and Monitoring Function . 36
6.2.4.2.3 Device Firmware Management Function . 37
6.2.4.2.4 Device Topology Management Function . 37
6.2.5 Discovery . 37
6.2.5.1 General Concepts . 37
6.2.5.2 Detailed Descriptions . 37
6.2.6 Group Management . 38
6.2.6.1 General Concepts . 38
6.2.6.2 Detailed Descriptions . 38
6.2.7 Location . 38
ETSI

---------------------- Page: 3 ----------------------
oneM2M TS-0001 version 3.22.0 Release 3 4 ETSI TS 118 101 V3.22.0 (2021-02)
6.2.7.1 General Concepts . 38
6.2.7.2 Detailed Descriptions . 39
6.2.8 Network Service Exposure, Service Execution and Triggering . 39
6.2.8.1 General Concepts . 39
6.2.8.2 Detailed Descriptions . 39
6.2.9 Registration . 40
6.2.9.1 General Concepts . 40
6.2.9.2 Detailed Descriptions . 40
6.2.10 Security . 41
6.2.10.1 General Concepts . 41
6.2.10.2 Detailed Descriptions . 41
6.2.11 Service Charging and Accounting . 43
6.2.11.1 General Concepts . 43
6.2.11.2 Detailed Descriptions . 43
6.2.12 Subscription and Notification . 44
6.2.12.1 General Concepts . 44
6.2.12.2 Detailed Descriptions . 44
6.2.13 Transaction Management . 44
6.2.13.1 General Concepts . 44
6.2.13.2 Detailed Descriptions . 44
6.2.14 Semantics . 45
6.2.14.1 General Concepts . 45
6.2.14.2 Detailed Descriptions . 45
6.3 Security Aspects . 45
6.4 Intra-M2M SP Communication . 45
6.5 Inter-M2M SP Communication . 46
6.5.1 Inter M2M SP Communication for oneM2M Compliant Nodes . 46
6.5.1.0 Overview . 46
6.5.1.1 Public Domain Names and CSEs . 47
6.5.2 Inter M2M SP Generic Procedures . 47
6.5.2.0 Overview . 47
6.5.2.1 Actions of the Originating M2M Node in the Originating Domain . 47
6.5.2.2 Actions of the Receiving CSE in the Originating Domain . 47
6.5.2.3 Actions in the IN of the Target Domain . 48
6.5.3 DNS Provisioning for Inter-M2M SP Communication . 48
6.5.3.0 Overview . 48
6.5.3.1 Inter-M2M SP Communication Access Control Policies . 48
6.5.4 Conditional Inter-M2M Service Provider CSE Registration . 48
6.6 M2M Service Subscription . 49
7 M2M Entities and Object Identification . 49
7.1 M2M Identifiers . 49
7.1.0 Overview . 49
7.1.1 M2M Service Provider Identifier (M2M-SP-ID) . 49
7.1.2 Application Entity Identifier (AE-ID). 49
7.1.3 Application Identifier (App-ID) . 50
7.1.4 CSE Identifier (CSE-ID) . 50
7.1.5 M2M Node Identifier (M2M-Node-ID) . 50
7.1.6 M2M Service Subscription Identifier (M2M-Sub-ID) . 50
7.1.7 M2M Request Identifier (M2M-Request-ID) . 51
7.1.8 M2M External Identifier (M2M-Ext-ID) . 51
7.1.9 Underlying Network Identifier (UNetwork-ID). 52
7.1.10 Trigger Recipient Identifier (Trigger-Recipient-ID) . 52
7.1.11 Void . 52
7.1.12 Void . 52
7.1.13 M2M Service Profile Identifier (M2M-Service-Profile-ID) . 52
7.1.14 Role Identifier (Role-ID) . 53
7.1.15 Token Identifier (Token-ID) . 53
7.1.16 Local Token Identifier (Local-Token-ID) . 53
7.2 M2M-SP-ID, CSE-ID, App-ID and AE-ID and resource Identifier formats . 53
7.3 M2M Identifiers lifecycle and characteristics . 65
ETSI

---------------------- Page: 4 ----------------------
oneM2M TS-0001 version 3.22.0 Release 3 5 ETSI TS 118 101 V3.22.0 (2021-02)
8 Description and Flows of Reference Points . 67
8.1 General Communication Flow Scheme on Mca and Mcc Reference Points . 67
8.1.0 Overview . 67
8.1.1 Description . 67
8.1.2 Request . 67
8.1.3 Response . 79
8.2 Procedures for Accessing Resources . 83
8.2.0 Overview . 83
8.2.1 Accessing Resources in CSEs - Blocking Requests . 83
8.2.1.0 Overview . 83
8.2.1.1 M2M Requests Routing Policies . 88
8.2.1.2 Inter SP Domain M2M Request Routing . 88
8.2.2 Accessing Resources in CSEs - Non-Blocking Requests . 88
8.2.2.1 Response with Acknowledgement and optional Reference to Request Context and Capturing
Result of Requested Operation . 88
8.2.2.2 Synchronous Case . 88
8.2.2.3 Asynchronous Case . 91
8.3 Procedures for interaction with Underlying Networks . 92
8.3.1 Introduction. 92
8.3.2 Description and Flows on Mcn Reference Point. 93
8.3.3 Device Triggering . 93
8.3.3.1 Definition and scope . 93
8.3.3.2 General Procedure for Device Triggering . 93
8.3.3.2.0 Overview . 93
8.3.3.2.1 Triggering procedure . 94
8.3.3.2.2 Support for device trigger recall/replace procedure. 97
8.3.4 Location Request . 98
8.3.4.1 Definition and Scope . 98
8.3.4.2 General Procedure for Location Request . 99
8.3.5 Configuration of Traffic Patterns . 100
8.3.5.1 Purpose of Configuration of Traffic Patterns . 100
8.3.5.2 Traffic pattern parameters . 101
8.3.5.3 General procedure for Configuration of Traffic Patterns . 103
8.4 Connection Request . 104
8.5 Device Management . 104
9 Resource Management . 104
9.0 Overview . 104
9.1 General Principles . 105
9.2 Resources . 105
9.2.0 Overview . 105
9.2.1 Normal Resources . 105
9.2.2 Virtual Resources . 105
9.2.3 Announced Resources. 105
9.3 Resource Addressing . 106
9.3.1 Generic Principles . 106
9.3.2 Addressing an Application Entity . 106
9.3.2.1 Application Entity Addressing . 106
9.3.2.2 Application Entity Reachability . 107
9.3.2.2.1 CSE Point of Access (CSE-PoA) . 107
9.3.2.2.2 Locating Application Entities . 107
9.3.2.2.3 Usage of CSE-PoA by the M2M System . 107
9.4 Resource Structure . 109
9.4.1 Relationships between Resources . 109
9.4.2 Link Relations . 110
9.5 Resource Type Specification Conventions . 110
9.5.0 Overview . 110
9.5.1 Handling of Unsupported Resources/Attributes/Sub-resources within the M2M System . 113
9.6 Resource Types . 113
9.6.1 Overview . 113
9.6.1.1 Resource Type Summary . 113
9.6.1.2 Resource Type Specializations .
...