ETSI TR 102 966 V1.1.1 (2014-02)

Machine-to-Machine communications (M2M); Interworking between the M2M Architecture and M2M Area Network technologies

DTR/M2M-00014ed111

General Information

• Status: Published
• Publication Date: 09-Feb-2014
• Technical Committee: SmartM2M - Smart M2M
• Current Stage: 12 - Completion
• Due Date: 10-Feb-2014
• Completion Date: 10-Feb-2014
• Mandate: M/441

Standards Content (Sample)

ETSI TR 102 966 V1.1.1 (2014-02)






Technical Report
Machine-to-Machine communications (M2M);
Interworking between the M2M Architecture
and M2M Area Network technologies

---------------------- Page: 1 ----------------------
2 ETSI TR 102 966 V1.1.1 (2014-02)



Reference
DTR/M2M-00014ed111
Keywords
interworking, M2M, 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 2014.
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 TR 102 966 V1.1.1 (2014-02)
Contents
Intellectual Property Rights . 6
Foreword . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Abbreviations . 8
4 Scenarios for interworking . 9
5 Interworking with legacy devices (d) . 12
5.1 Implementation profile 1 . 12
5.1.1 Entity-relation representation of the M2M area network . 12
5.1.2 Mapping principles . 12
5.1.3 M2M Area Network specific technologies interworking . 17
®
5.1.3.1 ZigBee Alliance . 17
®
5.1.3.1.1 Implementation profile 1 for ZigBee PAN interworking with ETSI M2M . 18
®
5.1.3.1.2 ZigBee Interworking Proxy Application resource structure . 19
®
5.1.3.1.3 ZigBee network resource structure . 19
®
5.1.3.1.4 ZigBee node resource structure . 19
®
5.1.3.1.5 ZigBee application resource structure . 20
®
5.1.3.1.6 Use of mirroring or retargeting for ZigBee interfaces (clusters) . 21
5.1.3.2 UPnP . 21
5.1.3.2.1 Implementation profile 1 for UPnP interworking with ETSI M2M . 23
5.1.3.2.2 UPnP Interworking Proxy Application resource structure . 23
5.1.3.2.3 UPnP network resource structure . 23
5.1.3.2.4 UPnP node resource structure . 24
5.1.3.2.5 UPnP service resource structure . 24
5.1.3.3 KNX™ . 25
5.1.3.3.1 Implementation profile 1 for KNX™ PAN interworking with ETSI M2M . 26
5.1.3.3.2 KNX™ Interworking Proxy resource structure . 26
5.1.3.3.3 KNX™ Network resource structure . 27
5.1.3.3.4 KNX™ Group resource structure . 27
5.1.3.3.5 KNX™ Node resource structure . 27
5.2 Implementation profile 2 . 27
6 Interworking with M2M devices without SCL (D') . 27
6.1 Security considerations . 27
6.1.1 D' devices traffic aggregation by Gateway acting as proxy/concentrator . 28
6.1.2 MAN devices generating traffic with their own identity and security via gateway acting as
multiplexer/funnel . 28
6.1.3 Gateway acting as security mediator between MAN and M2M Core . 29
Annex A: Example of syntax for searchstring Tags . 30
A.1 Category: ETSI.ObjectType . 30
A.2 Category: ETSI.ObjectSemantic . 30
A.3 Category: ETSI.ApplicationProfile . 30
A.4 Category: ZigBee.ApplicationProfile . 31
A.5 Category: ZigBee.DeviceIdentifier . 31
A.6 Category: KNX.DptID . 31
A.7 Category: KNX.AreaID. 31
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TR 102 966 V1.1.1 (2014-02)
A.8 Category: KNX.LineID . 31
Annex B: Example of Application/XML syntax, oBix 1.1 semantic conventions . 32
B.1 Generic Area Network object representations . 32
B.1.1 Generic Interworking Proxy Application resource content structure . 32
B.1.2 Generic Network resource content structure . 32
B.1.3 Generic Device resource content structure . 34
B.1.4 Generic Application resource content structure . 35
B.1.5 GenericInterface resource content structure . 35
B.1.6 Generic Point resource content structure . 36
®
B.2 ZigBee Area Network object representations . 36
®
B.2.1 Mapping of native ZigBee primitive types to oBix types . 36
®
B.2.2 ZigBee Interworking Proxy Application resource content structure . 37
®
B.2.3 ZigBee Network resource content structure . 38
®
B.2.4 ZigBee Device resource content structure . 38
®
B.2.5 ZigBee Application resource content structure . 39
®
B.2.6 ZigBee cluster (Interface) resource content structure . 40
®
B.2.7 ZigBee Point resource content structure . 40
®
B.2.8 ZigBee Application representation examples . 41
B.3 wM-Bus Area Network object representations . 42
B.3.1 Mapping of native wM-Bus primitive types and units to oBix types and units . 42
B.3.2 wM-Bus Interworking Proxy Application resource content structure . 43
B.3.3 WM-Bus Network resource content structure . 43
B.3.4 WM-Bus Device resource content structure . 44
B.3.5 WM-Bus Application resource content structure . 45
B.3.6 WM-Bus profile (Interface) resource content structure . 45
B.3.7 WM-Bus Point resource content structure . 46
B.3.8 WM-Bus Application representation examples . 46
B.4 KNX™ Area Network object representations . 47
B.4.1 Mapping of native KNX™ data point types to oBix types and units . 47
B.4.2 KNX™ Interworking Proxy resource content structure . 57
B.4.3 KNX™ Network resource content structure . 58
B.4.4 KNX™ Group resource content structure (Device) . 59
B.4.5 KNX™ Group resource content structure (Application) . 59
B.4.6 KNX™ Group resource content structure (Interface) . 59
B.4.7 KNX™ Node resource content structure (Device) . 60
B.4.8 KNX™ Node resource content structure (Application) . 61
B.4.9 KNX™ Node resource content structure (Interface) . 61
Annex C: Example of Interworking Using Containers and Subscriptions . 63
C.1 NA/DA Registration to NSCL/DSCL . 64
C.2 Discovery of Announced NA Resource . 64
C.3 NA Creates M2M Container Resource & Announces it to DSCL . 65
C.4 Subscription to "socket1" NSCL Container Resource . 66
C.5 NSCL Sends Notification to SEP2 DA . 67
Annex D: Example of Interworking using aPoC . 69
D.1 GA and DA Registration and Discovery . . 69
D.2 GA and DA Communication via aPoC . 70
D.3 NA and DA Registration and Discovery . . 71
D.4 NA to DA Communication via aPoC . . 73
Annex E: dId interface for limited resource devices . 74
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TR 102 966 V1.1.1 (2014-02)
E.1 Scope . 74
E.2 dId interface . 74
E.2.1 Interworking Proxy Unit . 75
E.2.1.1 CREATE . 75
E.2.1.2 RETRIEVE . 75
E.2.1.3 UPDATE . 75
E.2.1.4 DELETE . 76
E.2.2 Network . 76
E.2.2.1 CREATE . 76
E.2.2.2 RETRIEVE . 76
E.2.2.3 UPDATE . 77
E.2.2.4 DELETE . 77
E.2.3 Device, Application and Interface . 77
E.2.3.1 CREATE . 77
E.2.3.1.1 Case 1: Define an area network device through a well-known device profile . 77
E.2.3.1.2 Case 2: Define an area network device through a set of well-known device application profiles . 78
E.2.3.1.3 Case 2 (variant) . 79
E.2.3.1.4 Case 3: Define an area network device through a set of well-known interface profiles . 79
E.2.3.1.5 Case 3 (variant) . 81
E.2.3.2 RETRIEVE . 81
E.2.3.3 UPDATE . 82
E.2.3.4 DELETE . 82
E.2.4 Data Field reporting. 82
E.2.4.1 CREATE . 82
E.2.4.2 RETRIEVE . 83
E.2.4.3 UPDATE . 83
E.2.4.4 DELETE . 83
E.2.5 Method retargeting . 83
E.2.5.1 CREATE . 83
E.2.5.1.1 IPU, Network, Device and Application level Methods . 84
E.2.5.2 RETRIEVE . 84
E.2.5.3 UPDATE . 84
E.2.5.4 DELETE . 84
E.2.6 Data Field retargeting . 84
E.2.6.1 CREATE . 84
E.2.6.2 RETRIEVE . 84
E.2.6.3 UPDATE . 85
E.2.6.4 DELETE . 85
E.3 CoV configuration . 85
E.3.1 XML element . 85
E.3.2 XML element . 85
E.3.3 XML element . 86
E.3.3.1 CoV configuration . 86
E.3.4 CoV configuration XML schema . 86
E.3.5 Example . 86
E.4 dId over USB . 87
E.4.1 Base URI . 87
E.4.2 Transport over serial link . 88
E.5 dId over IP . 89
Annex F: Bibliography . 90
History . 91

ETSI

---------------------- Page: 5 ----------------------
6 ETSI TR 102 966 V1.1.1 (2014-02)
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 Report (TR) has been produced by ETSI Technical Committee Machine-to-Machine communications
(M2M).
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TR 102 966 V1.1.1 (2014-02)
1 Scope
The present document collects and evaluates implementation profiles for interworking with M2M Area Network
technologies.
An implementation profile is defined, for the purpose of the present document, as the description on how the ETSI
M2M architecture can be used to achieve interworking. Each implementation profile is evaluated against deployment
scenarios and applicable technologies in order to identify the most suitable for the specific conditions.
2 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
http://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.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
Not applicable.
2.2 Informative references
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] ETSI TS 102 690: "Machine-to-Machine communications (M2M); Functional architecture".
[i.2] ETSI TS 102 921: "Machine-to-Machine communications (M2M); mIa, dIa and mId interfaces".
[i.3] IEEE 802.15.4-2003: "IEEE Standard for Information technology - Telecommunications and
information exchange between systems - Local and metropolitan area networks - Specific
requirements Part 15.4: Wireless Medium Access Control (MAC) and Physical Layer (PHY)
Specifications for Low-Rate Wireless Personal Area Networks (LR-WPANs)".
[i.4] CEN EN 13757: "Communication systems for meters and remote reading of meters".
[i.5] CEN EN 13757-3: "Communication systems for and remote reading of meters - Part 3: Dedicated
application layer".
[i.6] ISO 8601:2004: "Data elements and interchange formats -- Information interchange --
Representation of dates and times".
[i.7] IETF RFC 1006: "ISO Transport Service on top of the TCP Version: 3".
[i.8] IETF RFC 5023: "The Atom Publishing Protocol".
[i.9] ISO/IEC 14543-3-10:2012: "Information technology -- Home Electronic Systems (HES) --
Part 3-10: Wireless Short-Packet (WSP) protocol optimized for energy harvesting -- Architecture
and lower layer protocols".
[i.10] OASIS.OBIX_1_1: "OASIS oBix semantic conventions, version 1.1".
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TR 102 966 V1.1.1 (2014-02)
[i.11] ASHRAE.CSML_1_0: "ASHRAE 135 annex am Control System Modelling Language (CSML)
semantic conventions".
[i.12] IETF RFC 4287: "The Atom Syndication Format".
3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AES Advanced Encryption Standard
AN Area Network
ASHRAE American Society of Heating, Refrigeration, and Air-conditioning Engineers
ATOM XML document format defined in RFC 4287 [i.12]
COV Change Of Value
CSML Control System Modelling Language
DA Device Application
DDNS Dynamic DNS
DHCP Dynamic Host Configuration Protocol
DIF Data Information Field
DIP Device Interworking Proxy
DNS Domain Name System
DPT Data Point Type (KNX™ standard)
DSCL Device Service Capability Layer
GA Gateway Application
GENA General Event Notification Architecture
GIP Gateway Interworking Proxy
GSCL Gateway SCL
HAN Home Area Network
IN INPut
IP Internet Protocol
IPA Interworking Proxy Application
IPU Interworking Proxy Unit
ISO International Standard Organization
KNX™ Konnex protocol maintained by the KNX™ Association
LAN Local Area Network
MAC Medium Access Control (Layer)
MAN M2M Area Network
NA Network Application
NA/DA Network Application/Device Application
NIP Network Interworking Proxy
NSCL Network SCL
OASIS Organization for the Advancement
...