ETSI TS 102 689 V2.1.1 (2013-07)

Machine-to-Machine communications (M2M); M2M service requirements

RTS/M2M-00001ed211

General Information

• Status: Published
• Publication Date: 30-Jun-2013
• Technical Committee: SmartM2M - Smart M2M
• Current Stage: 12 - Completion
• Due Date: 26-Jul-2013
• Completion Date: 01-Jul-2013
• Mandate: M/441

Standards Content (Sample)

ETSI TS 102 689 V2.1.1 (2013-07)






Technical Specification
Machine-to-Machine communications (M2M);
M2M service requirements

---------------------- Page: 1 ----------------------
2 ETSI TS 102 689 V2.1.1 (2013-07)



Reference
RTS/M2M-00001ed211
Keywords
M2M, requirements, service
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
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the 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
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:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2013.
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 ----------------------
3 ETSI TS 102 689 V2.1.1 (2013-07)
Contents
Intellectual Property Rights . 6
Foreword . 6
Introduction . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 8
2.2 Informative references . 8
3 Abbreviations . 8
4 General requirements . 9
4.1 M2M Application communication principles . 9
4.2 Message Delivery for sleeping devices . 9
4.3 Void . 9
4.4 Message transmission scheduling . 9
4.5 Message communication path selection . 9
4.6 Communication with devices behind a M2M gateway . 9
4.7 Communication failure notification . 9
4.8 Scalability . 10
4.9 Abstraction of technologies heterogeneity . 10
4.10 M2M Service Capabilities discovery and registration . 10
4.11 M2M Trusted Application . 10
4.12 Mobility . 10
4.13 Communications integrity . 10
4.14 Device/Gateway integrity check . 10
4.15 Continuous connectivity . 10
4.16 Confirm . 10
4.17 Void . 11
4.18 Logging . 11
4.19 Void . 11
4.20 Time Stamp . 11
4.21 Device/Gateway failure robustness . 11
4.22 Void . 11
4.23 Operator telco capabilities exposure. 11
4.24 Location reporting support . 11
4.25 Support of multiple M2M Applications . 11
4.26 Support for subscribing to receive notification . 12
4.27 Support for optimizing notification . 12
4.28 Support for store and forward. 12
4.29 Multiple M2M Service Providers . 12
5 Management . 12
5.1 Fault Management . 12
5.1.1 Proactive monitoring. 12
5.1.2 Diagnostics mode . 12
5.1.3 Connectivity test . 12
5.1.4 Fault discovery and reporting . 12
5.1.5 Fault Recovery by Remote Management . 12
5.1.6 Void . 13
5.2 Configuration Management . 13
5.2.1 Pre-provisioning and auto configuration of the M2M Devices and Gateways . 13
5.2.2 M2M Area Network resilience . 13
5.2.3 Time synchronization . 13
5.2.4 Configuration Management . 13
5.3 Accounting . 13
5.3.1 Charging . 13
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 689 V2.1.1 (2013-07)
5.3.1.1 Charging recorded information . 13
5.3.1.2 Offline Charging . 13
5.3.1.3 Online Charging . 13
5.3.1.4 Operational requirement . 13
5.3.1.5 Security for charging . 14
6 Functional requirements for M2M services . 14
6.1 Data collection & reporting . 14
6.2 Remote control of M2M Devices . 14
6.3 Group mechanisms . 14
6.4 Void . 14
6.5 M2M Devices/Gateways type varieties . 14
6.6 Information reception . 14
6.7 Reachability . 15
6.8 Asymmetric flows . 15
6.9 Paths diversity . 15
6.10 Heterogeneous M2M Area Networks . 15
6.11 Information collection & delivery to multiple applications . 15
6.12 Management of multiple M2M Devices/Gateways . 15
6.13 M2M Devices/Gateways description. 15
6.14 Data store and share . 15
6.15 Multiple M2M service providers . 15
7 Security. 16
7.1 Authentication . 16
7.2 Authentication of M2M service layer capabilities or M2M applications . 16
7.3 Void . 16
7.4 Data integrity . 16
7.5 Prevention of abuse of network connection. 16
7.6 Privacy . 16
7.7 Multiple actors . 16
7.8 Device/Gateway Integrity Validation . 16
7.9 Trusted Environment . 17
7.10 Security credential and software upgrade at the Application level . 17
7.11 System protection . 17
7.12 Multiple M2M Service Providers . 17
8 Naming, numbering and addressing . 17
8.1 Naming . 17
8.2 Identification . 17
8.3 Addressing . 18
Annex A (informative): M2M System Overview . 19
A.1 High Level System Architecture . 19
Annex B (informative): M2M use cases . 20
B.1 M2M use cases generalized from SCP UICC . 20
B.1.1 Track and trace use cases . 20
B.1.2 Monitoring use cases . 21
B.1.3 Transaction use cases . 22
B.1.4 Control use cases . 22
B.2 Compensation use cases . 23
B.2.1 Utility account management for prepaid . 23
B.2.2 Micro compensation for sensor readings . 23
B.2.3 Additional areas of applicability . 23
B.2.4 Service capabilities and primitives . 23
B.2.5 Example micro compensation scheme . 23
B.3 Home Automation use cases . 24
B.3.1 Energy efficiency at home . 24
B.4 Other use cases . 25
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 102 689 V2.1.1 (2013-07)
B.4.1 Data from Wireless Sensor Networks . 25
Annex C (informative): Security aspects . 26
C.1 Trusted and secure Environment . 26
Annex D (informative): Rationale texts related to some of the Requirements. 28
D.1 Rationale texts for some of the Requirements of clause 4 . 28
D.1.1 Related to clause 4.1 . 28
D.1.2 Related to clause 4.2 . 28
D.1.3 Related to clause 4.3 . 28
D.1.4 Related to clause 4.4 . 28
D.1.5 Related to clause 4.5 . 28
D.1.6 Related to clause 4.6 . 29
D.1.7 Related to clause 4.7 . 29
D.1.8 Related to clause 4.8 . 29
D.1.9 Related to clause 4.13 . 29
D.1.10 Related to clause 4.15 . 29
D.1.11 Related to clause 4.20 . 29
D.2 Rationale texts for some of the Requirements of clause 5 . 29
D.2.1 Related to clause 5.1.3 . 29
D.2.2 Related to clause 5.1.5 . 30
D.2.3 Related to clause 5.2.1 . 30
D.2.4 Related to clause 5.2.2 . 30
D.2.5 Related to clause 5.2.3 . 30
D.2.6 Related to clause 5.2.4 . 30
D.3 Rationale texts for some of the Requirements of clause 6 . 30
D.3.1 Related to clause 6.1 . 30
D.3.2 Related to clause 6.3 . 31
D.3.3 Related to clause 6.4 . 31
D.3.4 Related to clause 6.5 . 31
D.3.5 Related to clause 6.7 . 32
D.3.6 Related to clause 6.8 . 32
D.3.7 Related to clause 6.9 . 32
D.3.8 Related to clause 6.10 . 32
D.3.9 Related to clause 6.11 . 32
D.3.10 Related to clause 6.12 . 32
D.4 Rationale texts for some of the Requirements of clause 7 . 32
D.4.1 Related to clause 7.1 . 32
D.4.2 Related to clause 7.2 . 33
D.4.3 Related to clause 7.3 . 33
D.4.4 Related to clause 7.4 . 33
D.4.5 Related to clause 7.5 . 33
D.4.6 Related to clause 7.6 . 33
D.4.7 Related to clause 7.8 . 33
D.4.8 Related to clause 7.10 . 34
History . 35

ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 102 689 V2.1.1 (2013-07)
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 (http://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 Technical Committee Machine-to-Machine
communications (M2M).
Introduction
Machine-to-Machine (M2M) communications is the communication between two or more entities that do not
necessarily need any direct human intervention. M2M services intend to automate decision and communication
processes.
The M2M service requirements detailed in the present document enable consistent, cost-effective, communication for
wide-range ubiquitous applications. Examples of such applications include: fleet management, smart metering, home
automation, e-health, etc.
The present document, together with the architecture specification, TS 102 690 [i.1], forms the basis for the M2M
communications detailed technical specifications.
The present document specifies general and functional requirements for M2M communication services.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 689 V2.1.1 (2013-07)
1 Scope
The present document specifies the M2M service requirements aiming at an efficient end-to-end delivery of M2M
services.
It contains the following clauses:
• General requirements - describes communications features necessary for the correct establishment of M2M
communications.
• Management - specifies requirements related to the management modes (malfunction detection,
configuration, accounting, etc.).
• Functional requirements for M2M services - describes functionalities-related requirements for M2M (data
collection & reporting, remote control operations, etc.).
• Security - covers the requirements for M2M device authentication, data integrity, privacy, etc.
• Naming, numbering and addressing - provides the requirements relating to naming, numbering and
addressing schemes specific to M2M.
The M2M requirements in the present document are influenced by the following use cases:
• Smart meter use cases as described in TR 102 691 [i.2].
• eHealth use cases as described in TR 102 732 [i.3].
• Track and Trace use cases as described in annex B.
• Monitoring use cases as described in annex B.
• Transaction use cases as described in a
...