ETSI TS 118 102 V2.7.1 (2016-09)

oneM2M Requirements (oneM2M TS-0002 version 2.7.1 Release 2)

RTS/oneM2M-000002v200

General Information

• Status: Published
• Publication Date: 06-Sep-2016
• Technical Committee: oneM2M - oneM2M
• Current Stage: 12 - Completion
• Due Date: 30-Sep-2016
• Completion Date: 07-Sep-2016

Standards Content (Sample)

ETSI TS 118 102 V2.7.1 (2016-09)






TECHNICAL SPECIFICATION
oneM2M Requirements
(oneM2M TS-0002 version 2.7.1 Release 2)

---------------------- Page: 1 ----------------------
oneM2M TS-0002 version 2.7.1 Release 2 2 ETSI TS 118 102 V2.7.1 (2016-09)



Reference
RTS/oneM2M-000002v200
Keywords
IoT, M2M, requirements

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-0002 version 2.7.1 Release 2 3 ETSI TS 118 102 V2.7.1 (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 Introduction to the M2M ecosystem. 7
5.1 Functional roles description . 7
6 Functional Requirements . 8
6.1 Overall System Requirements . 8
6.2 Management Requirements . 13
6.3 Semantics Requirements . 14
6.3.1 Ontology Related Requirements . 14
6.3.2 Semantics Annotation Requirements . 15
6.3.3 Semantics Query Requirements . 16
6.3.4 Semantics Mashup Requirements . 16
6.3.5 Semantics Reasoning Requirements . 16
6.3.6 Data Analytics Requirements . 16
6.4 Security Requirements . 17
6.5 Charging Requirements . 20
6.6 Operational Requirements . 21
6.7 Communication Management Requirements . 21
6.8 LWM2M Interworking Requirements . 23
7 Non-Functional Requirements (informative) . 23
Annex A (informative): Requirements for the next release . 24
History . 25

ETSI

---------------------- Page: 3 ----------------------
oneM2M TS-0002 version 2.7.1 Release 2 4 ETSI TS 118 102 V2.7.1 (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-0002 version 2.7.1 Release 2 5 ETSI TS 118 102 V2.7.1 (2016-09)
1 Scope
The present document contains an informative functional role model and normative technical requirements for
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 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 122 368: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; Service requirements for Machine-Type
Communications (MTC); Stage 1 (3GPP TS 22.368)".
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://member.onem2m.org/Static_pages/Others/Rules_Pages/oneM2M-Drafting-Rules-
V1_0.doc.
[i.2] ETSI TS 118 111: "oneM2M; Common Terminology (oneM2M TS-0011)".
[i.3] ETSI TR 118 508: "Analysis of Security Solutions for the oneM2M System".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ETSI TS 118 111 [i.2] apply.
ETSI

---------------------- Page: 5 ----------------------
oneM2M TS-0002 version 2.7.1 Release 2 6 ETSI TS 118 102 V2.7.1 (2016-09)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AE Application Entity
API Application Program Interface
BBF BroadBand Forum
CHA Continua Health Alliance
CPU Central Processing Unit
DM Device Management
GBA Generic Bootstrapping Architecture
GSMA Global System for Mobile Communications Association
GW Gateway
HGI Home Gateway Initiative
HSM Hardware Security Module
IP Internet Protocol
MTC Machine Type Communications
OMA Open Mobile Alliance
OSR Overall System Requirements
OWL Web Ontology Language
QoS Quality of Service
RDF Resource Description Framework
SMS Short Message Service
UICC Universal Integrated Circuit Card
USIM UMTS Subscriber Identity Module
USSD Unstructured Supplementary Service Data
WAN Wide Area Network
WLAN Wireless Local Area Network
4 Conventions
The keywords "shall", "shall not", "should", "should not", "may", "need not" in the present document are to be
interpreted as described in the oneM2M Drafting Rules [i.1].
NOTE: According to oneM2M Drafting Rules [i.1] in order to mandate a feature in the oneM2M System but
allow freedom to the individual deployment whether to use it or not subsequently requirements are often
formulated like:
"The oneM2M System shall support a mechanism [function, capability.] to …"; or
"…shall be able to …".
This does not mandate usage of the required feature in a M2M Solution.
ETSI

---------------------- Page: 6 ----------------------
oneM2M TS-0002 version 2.7.1 Release 2 7 ETSI TS 118 102 V2.7.1 (2016-09)
5 Introduction to the M2M ecosystem
5.1 Functional roles description
an
(end) user M2M
Solu tion
M2M
M2M
operates
….
Application
Appl.
Application Service
Providers
M2M Applications
M2M Common
M2M
operates
…
Service
CS
M2M
M2M Common Services
Service Providers
Underlying U nderlying
operates
…
Network Network
Connectivity Services
Network Operators

Figure 1: Functional Roles in the M2M Ecosystem
1) The User (individual or company – aka: end-user) fulfils all of the following criteria:
- Uses an M2M solution.
2) The Application Service Provider fulfils all of the following criteria:
- Provides an M2M Application Service.
- Operates M2M Applications.
3) The M2M Service Provider fulfils all of the following criteria:
- Provides M2M Services to Application Service Providers.
- Operates M2M Common Services.
4) The Network Operator fulfils all of the following criteria:
- Provides Connectivity and related services for M2M Service Providers.
- Operates an Underlying Network. Such an Underlying Network could e.g. be a telecom network.
Any of the above functional roles may coincide with any of the other roles. These functional roles do not imply business
roles or architectural assumptions.
ETSI

---------------------- Page: 7 ----------------------
oneM2M TS-0002 version 2.7.1 Release 2 8 ETSI TS 118 102 V2.7.1 (2016-09)
6 Functional Requirements
6.1 Overall System Requirements
Table 1: Overall System Requirements
Requirement ID Description Release
OSR-001 The oneM2M System shall allow communication between M2M Applications by Implemented
using multiple communication means based on IP access. in Rel-1
OSR-002a The oneM2M System shall support communication means that can Implemented
accommodate devices with constrained computing (e.g. small CPU, memory, in Rel-1
battery) or communication capabilities (e.g. 2G wireless modem, certain WLAN
node).
OSR-002b The oneM2M System shall support communication means that can Implemented
accommodate devices with rich computing capabilities (e.g. large CPU, in Rel-1
memory) or communication (e.g. 3/4G wireless modem, wireline).
OSR-003 The oneM2M System shall support the ability to maintain application-to- Not
See REQ-2015- application communication in coordination with an application session for those implemented
0626R01 M2M Applications that require it.
OSR-004 The oneM2M System shall support session-less application communications for Implemented
those M2M Applications that require it. in Rel-1
OSR-005 The oneM2M System shall be able to expose the services offered by Partially
telecommunications networks to M2M Applications (e.g. SMS, USSD, implemented
localization, subscription configuration, authentication (e.g. Generic (see note 9)
Bootstrapping Architecture), etc.),subject to restriction based on Network
Operator's policy.
OSR-006 The oneM2M System shall be able to reuse the services offered by Underlying Partially
Networks to M2M Applications and/or M2M Services by means of open access implemented
models (e.g. OMA, GSMA OneAPI framework).Examples of available services (see note 10)
are:
• IP Multimedia communications.
• Messaging.
• Location.
• Charging and billing services.
• Device information and profiles.
• Configuration and management of devices.
• Triggering, monitoring of devices.
• Small data transmission.
• Group management.
(see note 1).
OSR-007 The oneM2M System shall provide a mechanism for M2M Applications to Implemented
interact with the Applications and data/information managed by a different M2M in Rel-1
Service Provider, subject to permissions as appropriate.
OSR-008 The oneM2M System shall provide the capability for M2M Applications to Implemented
communicate with an M2M Device (i.e. application in the device) without the in Rel-1
need for the M2M Applications to be aware of the network technology and the (see note 11)
specific communication protocol of the M2M Device.
OSR-009 The oneM2M System shall support the ability for single or multiple M2M Implemented
Applications to interact with a single or multiple M2M Devices/Gateways in Rel-1
(application in the device/gateway) (see note 2).
OSR-010 The oneM2M System shall support mechanisms for confirmed delivery of a Implemented
message to its addressee to those M2M Applications requesting reliable in Rel-1
delivery to dectect failure of message within a given time interval.
OSR-011a The oneM2M System shall be able to request different communication paths, Implemented
from the Underlying Network based on Underlying Network Operator and/or in Rel-1
M2M Service Provider policies, routing mechanisms for transmission failures. (see note 12)
OSR-011b The oneM2M System shall be able to request different communication paths Not
from the Underlying Network based on request from M2M Applications. implemented
OSR-012 The oneM2M System shall support communications between M2M Applications Implemented
and M2M Devices supporting M2M Services by means of continuous or non- in Rel-1
continuous connectivity.
ETSI

---------------------- Page: 8 ----------------------
oneM2M TS-0002 version 2.7.1 Release 2 9 ETSI TS 118 102 V2.7.1 (2016-09)
Requirement ID Description Release
OSR-013 The oneM2M System shall be aware of the delay tolerance acceptable by the Implemented
M2M Application and shall schedule the communication accordingly or request in Rel-1
the Underlying Network to do it, based on policies criteria.
OSR-014 The oneM2M System shall be able to communicate with M2M Devices, behind Implemented
an M2M Gateway that supports heterogeneous M2M Area Networks. in Rel-1
OSR-015 The oneM2M System shall be able to assist Underlying Networks that support Partially
different communication patterns including infrequent communications, small implemented
data transfer, transfer of large file and streamed communication. (see note 13)

OSR-016 The oneM2M System shall provide the capability to notify M2M Applications of Implemented
the availability of, and changes to, available M2M Application/management in Rel-1
information on the M2M Device/Gateway, including changes to the M2M Area
Network.
OSR-017 The oneM2M System shall be able to offer access to different sets of M2M Implemented
Services to M2M Application Providers. The minimum set of services are: in Rel-1
• Connectivity management.
• Device management (service level management).
• Application Data management.
In order to enable different deployment scenarios, these services shall be made
available by the oneM2M System, individually, as a subset or as a complete set
of services.
OSR-018 The oneM2M System shall be able to offer M2M Services to M2M Devices Implemented
roaming across cellular Underlying Networks,subject to restriction based on with some
Network Operator's policy (see note 3). limitations
(see note 14)
OSR-019 The oneM2M System shall support the capabilities for data repository (i.e. to Implemented
collect/store) and for data transfer from one or more M2M Devices or M2M in Rel-1
Gateways, for delivery to one or more M2M Gateways, M2M Services
Infrastructure, or M2M Application Infrastructure, in ways requested by the M2M
Application Infrastructure as listed below:
• action initiated either by an M2M Device, M2M Gateway, M2M
Services Infrastructure, or M2M Application Infrastructure;
• when triggered by schedule or event;
• for specified data.
OSR-020 The oneM2M System shall be able to support policies and their management Implemented
regarding the aspects of storage and retrieval of data/information. in Rel-1
OSR-021 The oneM2M System shall be able to provide mechanisms to enable sharing of Implemented
data among multiple M2M Applications. in Rel-1
OSR-022 When some of the components of a M2M Solution are not available (e.g. WAN Implemented
connection lost), the oneM2M System shall be able to support the normal in Rel-1
operation of components of the M2M Solution that are available.
OSR-023 The oneM2M System shall be able to identify the M2M Services to be used by Implemented
M2M Service Subscriptions (see note 4). in Rel-1
OSR-024 The oneM2M System shall be able to identify the M2M Devices used by M2M Implemented
Service Subscriptions. in Rel-1
OSR-025 The oneM2M System shall be able to identify the M2M Applications used by Implemented
M2M Service Subscriptions. in Rel-1
OSR-026 If provided by the Underlying Network, the oneM2M System shall be able to Implemented
associate the M2M Device used by M2M Service Subscriptions with the device in Rel-1
identifiers offered by the Underlying Network and the device.
OSR-027 The oneM2M System shall provide a generic mechanism to support transparent Not
exchange of information between the M2M Application and the Underlying implemented
Network, subject to restriction based on M2M Service Provider's policy and/or
Network Operator's policy (see note 5).
OSR-028 The oneM2M System shall enable an M2M Application to define trigger Not
conditions in the oneM2M System such that the oneM2M System autonomously implemented
sends a series of commands to actuators on behalf of the M2M Application
when these contitions are met.
OSR-029 The oneM2M System shall be able to support sending common command(s) to Implemented
each actuator or sensor via a group. in Rel-1
OSR-030 The oneM2M System shall be able to support the management (i.e. addition, Implemented
removal, retrieval and update) of the membership of a group. in Rel-1
OSR-031 The oneM2M System shall be able to support a group as a member of another Implemented
group. in Rel-1
ETSI

---------------------- Page: 9 ----------------------
oneM2M TS-0002 version 2.7.1 Release 2 10 ETSI TS 118 102 V2.7.1 (2016-09)
Requirement ID Description Release
OSR-032 The oneM2M System shall be able to support Event Categories (e.g. normal, Implemented
urgency) associated with data for M2M Applications when collecting, storing in Rel-1
and reporting that data (see note 6).
OSR-033 Based on the Dynamic Device/Gateway Context of the M2M Gateway and/or Partially
Device and the defined Event Categories, the oneM2M System shall provide implemented
the capability to dynamically adjust the scheduling of reporting and notification (see note 15)
of the M2M Device/Gateway (see note 17).
OSR-034 The oneM2M System shall support seamless replacement of M2M Devices as Not
well as M2M Gateways (e.g. redirecting traffic, connection, recovery, etc.). implemented
OSR-035 The oneM2M System shall support the exchange of non-M2M Application Not
related relevant information (e.g. Device/Gateway classes) between M2M implemented
Device/Gateway and M2M Service Infrastructure for the purpose of efficient
communication facilitation. This includes the capability for an M2M Device to
report its device class to M2M Service Infrastructure and for the M2M Service
Infrastructure to inform M2M Device of the M2M Service Infrastruture
capabilities.
OSR-036 The oneM2M System should provide mechanisms to accept requests from Not
M2M Application Service Providers for compute/analytics services. implemented
OSR-037 The oneM2M System shall enable an M2M Application to request to send data, Not
in a manner independent of the Underlying Network, to the M2M Applications of implemented
a group of M2M Devices and M2M Gateways in geographic areas that are
specified by the M2M Application.
OSR-038 The oneM2M System shall support the inclusion of M2M Application's QoS Not
preference in service requests to Underlying Networks. implemented
OSR-039 The oneM2M System shall be able to authorize service requests with QoS Not
preference at service level, but shall pass M2M Application's QoS preference in implemented
service requests to Underlying Network for authorization and granting or
negotiation of the service QoS requests.
OSR-040 The oneM2M System shall be able to leverage multiple communication Not
mechanisms (such as USSD or SMS) when available in the Underlying implemented
Networks. (see note 16)
OSR-041 The oneM2M System shall provide a mechanism, which supports the addition Partially
of new M2M Services to the oneM2M System as independent portable modules implemented
by means of the oneM2M interfaces. (see note 21)
OSR-042 The oneM2M System shall be able to support different QoS-levels specifying Not
parameters, such as guaranteed bitrate, delay, delay variation, loss ratio and implemented
error rate, etc.
OSR-043 The oneM2M System shall be able to verify that members of a group support a Implemented
common set of functions. in Rel-1
OSR-044 The oneM2M System shall support communication with M2M Devices which Implemented
are reachable based on defined time schedules (e.g. periodic) as well as M2M in Rel-1
Devices which are reachable in an unpredictable and spontaneous manner.
OSR-045a The oneM2M System shall be able to receive and utilize information provided Not
by the Underlying Network about when an M2M Device can be reached. implemented
OSR-045b The oneM2M System shall be able to utilize reachability schedules generated Partially
by either the M2M Device or the Infrastructure Domain. implemented
(see note 18)
OSR-046 The oneM2M System shall be able to support a capability for the M2M Not
Application to request/disallow acknowledgement for its communication. implemented
OSR-047 The oneM2M System shall be able to support mechanism for the M2M Devices Implemented
and/or Gateways to report their geographical location information to M2M in Rel-1
Applications (see note 7).
OSR-048 The oneM2M System shall provide an M2M Service that allows M2M Devices Implemented
and/or Gateways to share their own or other M2M Devices' geographical in Rel-1
location information (see note 7).
OSR-049 The oneM2M System shall be able to provide the capability for an M2M Implemented
Application to selectively share data (e.g. access control) among applications. in Rel-1
OSR-050 If communication over one communication channel provided by the Underlying Implemented
Network can only be triggered by one side (Infrastructure Domain or Field in Rel-1
Domain), and alternative channel(s) is (are) available in the other direction, the
oneM2M System shall be able to use the alternative channel(s) to trigger
bidirectional communication on the first channel.
OSR-051 Depending on availability of suitable interfaces provided by the Underlying Implemented
Network the oneM2M System shall be able to request the Underlying Network in Rel-1
to broadcast/multicast data to a group of M2M Devices in a specified area.
ETSI

---------------------- Page: 10 ----------------------
oneM2M TS-0002 version 2.7.1 Release 2 11 ETSI TS 118 102 V2.7.1 (2016-09)
Requirement ID Description Release
OSR-052 The oneM2M System shall be able to select an appropriate Underlying Network Not
to broadcast or multicast data depending on the network's broadcast/multicast implemented
support and the connectivity supported by the targeted group of M2M
Devices/Gateways.
OSR-053 The oneM2M System shall provide a means that enables backward Not
compatibility of interfaces among different releases (see note 8). implemented
OSR-054 The oneM2M System shall be able to support an M2M Application, M2M Implemented
Device, or M2M Gateway to obtain access to resources of another M2M in Rel-1
Application, M2M Device, or M2M Gateway.
OSR-055 The oneM2M System shall be able to provide the capability of M2M Implemented
Applications to exchange data with one or more authorized M2M Applications in Rel-1
which are not known in advance. (see note 20)
OSR-056 The oneM2M System shall enable discovery of usable M2M Applications on an Implemented
M2M Gateway or at an M2M Device . in Rel-1
OSR-057 The oneM2M System shall enable discovery of M2M Gateways and M2M Implemented
Devices available to an M2M Application for data exchange. in Rel-1
OSR-058 The oneM2M System shall be able to provide time stamps as needed by Implemented
Common Service Functions. in Rel-1
OSR-059 The oneM2M System shall be able to support Role-Based Access Control Implemented
based on M2M Service Subscriptions. in Rel-1
OSR-060 The oneM2M System should support time synchronization with an external Not
clock source. implemented
OSR-061 M2M Devices and M2M Gateways may support time synchronization within the Not
oneM2M System. implemented
OSR-062 The oneM2M System shall enable means of testing the connectivity towards a Not
set of M2M Applications. implemented
OSR-063 The oneM2M System shall be able to manage the scheduling of M2M Service Implemented
Layer connectivity and messaging between the Infrastracture Domain and M2M in Rel-1
Devices/Gateways.
OSR-064 The oneM2M System shall be able to aggregate messages depending on Implemented
message delay tolerance and/or category. in Rel-1
OSR-065 The oneM2M System shall provide mechanisms that enable a M2M Service
Not
Provider to distribute processing functions to his M2M Devices/Gateways in the implemented
Field Domain
OSR-066 The oneM2M System shall be able to support the placement and operation of Implemented
M2M Applications in selected M2M Nodes per criteria requested by M2M in Rel-1
Application Service Providers, subject to access rights.
OSR-067 The oneM2M System shall be able to take operational and management action Implemented
as requested by M2M Applications. in Rel-1
OSR-068 When available from an Underlying Network, the oneM2M System shall be able Not
to provide the capability to retrieve and report the inform
...