1、 ETSI TR 118 525 V1.0.0 (2016-03) oneM2M; Application Developer Guide (oneM2M TR-0025 version 1.0.0 Release 1) TECHNICAL REPORT ETSI ETSI TR 118 525 V1.0.0 (2016-03) 2oneM2M TR-0025 version 1.0.0 Release 1Reference DTR/oneM2M-000025 Keywords application, interoperability, M2M, testing ETSI 650 Route
2、 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.o
3、rg/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
4、 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 s
5、tatus. 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.asp
6、x 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 ETS
7、I. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Mark
8、s 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 ETSI TR 118 525 V1.0.0 (2016-03) 3oneM2M TR-0025 version 1.0.0 Release 1Contents Intellectual Property Rights 5g3Forewor
9、d . 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Conventions 7g35 Use case 7g36 Architecture 8g37 Procedures 9g37.1 Introduction 9g37.2 Call Flows 10g37.2.1 Application regis
10、tration and Access control policy creation 10g37.2.2 Initial resource creation 11g37.2.3 Discovery of group resources . 12g37.2.4 Discovery and retrieval of contentInstance resources . 13g37.3 Remote control scenarios . 15g37.3.1 Introduction. 15g37.3.2 Single light lamp control . 15g37.3.3 Multiple
11、 light lamps control 15g38 Implementation . 16g38.1 Introduction 16g38.2 Assumptions . 16g38.3 Addressing for Entities . 17g38.4 Modelling for Light State Data . 17g38.5 Resource Structure . 17g38.5.1 Resource Structure of IN-CSE 17g38.5.2 Resource Structure of MN-CSE 17g38.6 Role of Entities . 19g3
12、8.6.1 oneM2M service platform (IN-CSE) 19g38.6.2 Home gateway application (MN-AE) . 19g38.6.3 Light applications (ADN-AE1 and ADN-AE2) 19g38.6.4 Smartphone application (IN-AE) 19g38.7 Implementation Procedures 20g38.7.1 Introduction. 20g38.7.2 MN-CSE registration 20g38.7.3 Access control policy crea
13、tion 20g38.7.4 Application entities registration 21g38.7.4.1 Light application ADN-AE1 . 21g38.7.4.2 Light application ADN-AE2 . 21g38.7.4.3 Home gateway application MN-AE 22g38.7.4.4 Smartphone application IN-AE . 22g38.7.5 Containers creation . 23g38.7.5.1 Create a container of ADN-AE1 . 23g38.7.5
14、.2 Create a container of ADN-AE2 . 23g38.7.6 ContentInstances creation . 23g38.7.6.1 Create a content instance of ADN-AE1 23g38.7.6.2 Create a content instance of ADN-AE2 24g38.7.7 Groups creation . 24g38.7.7.1 Create a group for updating all light states 24g3ETSI ETSI TR 118 525 V1.0.0 (2016-03) 4o
15、neM2M TR-0025 version 1.0.0 Release 18.7.7.2 Create a group for retrieval of all latest light states . 25g38.7.8 Subscriptions creation . 25g38.7.8.1 Subscription to the content instance of ADN-AE1 . 25g38.7.8.2 Subscription to the content instance of ADN-AE2 . 26g38.7.9 Discovery 26g38.7.9.1 Introd
16、uction . 26g38.7.9.2 Discovery of single light registered with MN-CSE 26g38.7.9.3 Discovery of groups located in MN-CSE 27g38.7.10 Latest content instances retrieval 27g38.7.10.1 Introduction . 27g38.7.10.2 Retrieve the latest content instance of ADN-AE1 . 27g38.7.10.3 Retrieve the latest content in
17、stance of ADN-AE2 . 28g38.7.10.4 Retrieve a group of latest content instances for all light states 28g38.7.11 Light state modification 29g38.7.11.1 Introduction . 29g38.7.11.2 Create a content instance under container of ADN-AE1 30g38.7.11.3 Create a content instance under container of ADN-AE2 30g38
18、.7.11.4 Update the state of all lights using group fanout 30g38.7.12 Notifications . 31g38.7.12.1 Introduction . 31g38.7.12.2 Post a notification to ADN-AE1 . 31g38.7.12.3 Post a notification to ADN-AE2 . 32g39 Conclusion 32g3Annex A: Reading Resources . 33g3Annex A.1 Introduction . 33g3Annex A.2 CS
19、E resources . 33g3Annex A.2.1 IN-CSE 33g3Annext A.2.2 MN-CSE . 33g3Annex A.3 Gateway device application MN-AE 34g3Annex A.4. Light device applications . 34g3Annex A.4.1 ADN-AE1 34g3Annex A.4.2 ADN-AE2 35g3Annex A.5 Smartphone application IN-AE . 35g3Annex A.6 Access control policy 36g3Annex A.7 Cont
20、ainers . 36g3Annex A.7.1 Container under ADN-AE1 . 36g3Annex A.7.2 Container under ADN-AE2 . 37g3Annex A.8 ContentInstances . 37g3Annex A.8.1 Latest contentInstance in ADN-AE1 . 37g3Annex A.8.2 Latest contentInstance in ADN-AE2 . 38g3Annex A.9 Subscriptions . 38g3Annex A.9.1 Subscription to containe
21、r in ADN-AE1 . 38g3Annex A.9.2 Subscription to container in ADN-AE2 . 39g3Annex A.10 Groups. 39g3Annex A.10.1 Group1 39g3Annex A.10.2 Group2 40g3History 41g3ETSI ETSI TR 118 525 V1.0.0 (2016-03) 5oneM2M TR-0025 version 1.0.0 Release 1Intellectual Property Rights IPRs essential or potentially essenti
22、al 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
23、 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 t
24、he 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 Partnership Project oneM2M (oneM2M). ETSI ETSI TR 118 525 V1.0.0
25、(2016-03) 6oneM2M TR-0025 version 1.0.0 Release 11 Scope The present document provides a guide for application developers to develop applications using functionalities provided by any oneM2M compliant service platform with thescope of as follows: Objective of the use case, The architecture of the us
26、e case mapped into an oneM2M service platform, The execution procedures for implementation of the use case, and Implementation details of the use case. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or
27、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:/do
28、cbox.etsi.org/Reference/. The following referenced documents are necessary for the application of the present document. Not applicable. 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
29、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 fol
30、lowing 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 i.2 ETSI TS 118 101 (V1.1.0): “oneM2M;
31、 Functional Architecture (oneM2M TS-0001)“. i.3 ETSI TS 118 104 (V1.1.0): “oneM2M; Service Layer Core protocol Specification (oneM2M TS-0004)“. i.4 ETSI TS 118 109 (V1.1.0): “oneM2M; HTTP Protocol Binding (oneM2M TS-0009)“. i.5 ETSI TS 118 111: “oneM2M; Common Terminology (oneM2M TS-0011)“. ETSI ETS
32、I TR 118 525 V1.0.0 (2016-03) 7oneM2M TR-0025 version 1.0.0 Release 13 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI TS 118 111 i.5 and the following apply. NOTE: A term defined in the present document takes precedence
33、 over the definition of the same term, if any, in ETSI TS 118 111 i.5. M2M service provider domain: part of the M2M System that is associated with a specific M2M Service Provider registrar CSE: CSE where an Application or another CSE has registered resource: uniquely addressable entity in oneM2M arc
34、hitecture 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ACP Access Control Policy ADN Application Dedicated Node ADN-AE AE which resides in the Application Dedicated Node AE Application Entity CoAP Constrained Application Protocol CSE Common Services
35、Entity CSE-ID Common Service Entity Identifier DNS Domain Name System FQDN Fully Qualified Domain Name HTTP HyperText Transfer Protocol IN Infrastructure Node IN-AE Application Entity that is registered with the CSE in the Infrastructure Node IN-CSE CSE which resides in the Infrastructure Node IP In
36、ternet Protocol JSON JavaScript Object Notation M2M Machine to Machine Mca Reference Point for M2M Communication with AE Mcc Reference Point for M2M Communication with CSE MN Middle Node MN-AE Application Entity that is registered with the CSE in Middle Node MN-CSE CSE which resides in the Middle No
37、de PoA Point of Access SP Service Provider URI Uniform Resource Identifier XML eXtensible Markup Language 4 Conventions The key words “Shall“, “Shall not“, “May“, “Need not“, “Should“, “Should not“ in this document are to be interpreted as described in the oneM2M Drafting Rules i.1. 5 Use case This
38、clause briefly describes the use case from perspective of service being provided by the oneM2M platform. The physical device components are introduced in the current section. ETSI ETSI TR 118 525 V1.0.0 (2016-03) 8oneM2M TR-0025 version 1.0.0 Release 1The described use case enables the remote contro
39、l of lights via a smartphone or smart tab which embeds an application that gains access to a oneM2M service platform. The overview of the use case of remote lights control is shown in figure 5.1. The main components are introduced as follows: i1 Light lamps shown in the current use case are deployed
40、 at a house and attached to a home gateway. The light lamps are able to interact with a oneM2M platform through a wireless access interface. i1 The home gateway is configured to be able to search and connect light lamps into itself and to communicate with a oneM2M service platform in terms of exchan
41、ging and storing light lamps states between the light lamps and the oneM2M service platform. i1 oneM2M service platform provides vertical application services targeted at different field domains, for instance, home, vehicle, and industry. The oneM2M service platform supports a group of common servic
42、e functionalities such as registration, discovery, data management, group management, subscription/notification etc. i1 The smartphone application is embedded into a smartphone and acts as a remote light controller with capabilities as the follows: square6 Discovery of light lamps deployed into the
43、home gateway. square6 Sending commands to change light states i.e. ON and OFF. square6 Retrieval of light states. g381g374g286g68g1006g68g3g94g286g396g448g349g272g286g3g87g367g258g410g296g381g396g373g94g373g258g396g410g393g346g381g374g286g3g286g373g271g286g282g282g349g374g336g3g449g349g410g346g3g258
44、g393g393g367g349g272g258g410g349g381g374g400g3g258g400g3g258g3g396g286g373g381g410g286g3g367g349g336g346g410g3g272g381g374g410g396g381g367g367g286g396g62g349g336g346g410g951g1006g62g349g336g346g410g951g1005g44g381g373g286g3g39g258g410g286g449g258g455Figure 5.1: Overview of remote lights control use
45、case 6 Architecture This clause describes the architecture of the implemented use case with components represented by the oneM2M entity roles. For instance, a physical device can be modelled as an ADN-AE and the oneM2M service system can be modelled as an IN-CSE, etc. The remote lights control use c
46、ase shown in figure 5.1 can be mapped into the oneM2M functional architecture depicted in figure 6.1. ETSI ETSI TR 118 525 V1.0.0 (2016-03) 9oneM2M TR-0025 version 1.0.0 Release 1g381g374g286g68g1006g68g3g94g286g396g448g349g272g286g3g87g367g258g410g296g381g396g373g94g373g258g396g410g393g346g381g374g
47、286g3g286g373g271g286g282g282g349g374g336g3g449g349g410g346g3g258g393g393g367g349g272g258g410g349g381g374g400g3g258g400g3g258g3g396g286g373g381g410g286g3g367g349g336g346g410g3g272g381g374g410g396g381g367g367g286g396g47g69g882g18g94g28g373g272g272g47g69g882g4g28g373g272g258g62g349g336g346g410g951g100
48、5g62g349g336g346g410g951g1006 g44g381g373g286g3g39g258g410g286g449g258g455g68g69g882g4g28g4g24g69g882g4g28g882g1005g68g69g882g18g94g28g373g272g258g373g272g258g44g381g373g286g3g24g381g373g258g349g374g4g24g69g882g4g28g882g1006Figure 6.1: oneM2M functional architecture of remote lights control use case
49、 In oneM2M functional architecture two entity roles are defined, one is AE and the other is CSE. Application dedicated devices e.g. light lamps are usually acted as an ADN-AE. Smartphone applications that are embedded into smartphone devices and able to communicate directly with oneM2M service platform can also be acted as an ADN-AE. oneM2M service system is acted as an IN-CSE and the home gateway plays a role of MN-CSE. Two reference points, mca and mcc which are defined in the oneM2M functional architecture are used between AE and CSE and betwee
