1、 ETSI TS 118 121 V2.0.0 (2016-09) oneM2M; oneM2M and AllJoynInterworking (oneM2M TS-0021 version 2.0.0 Release 2) TECHNICAL SPECIFICATION ETSI ETSI TS 118 121 V2.0.0 (2016-09)2oneM2M TS-0021 version 2.0.0 Release 2Reference DTS/oneM2M-000021 Keywords interworking, IoT, M2M ETSI 650 Route des Luciole
2、s 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.org/standards
3、-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 be
4、tween 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. Infor
5、mation 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
6、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 copyr
7、ight 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 Marks of ETSI re
8、gistered 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 TS 118 121 V2.0.0 (2016-09)3oneM2M TS-0021 version 2.0.0 Release 2Contents Intellectual Property Rights 5g3Foreword . 5g31 Scop
9、e 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions 7g34 Conventions 7g35 Architecture Model. 7g35.1 Reference model . 7g35.2 Composition of the IPE 8g36 Architecture Aspect 8g36.1 Introduction 8g36.2 oneM2M resource mapping structure . 9g36.3 AllJoyn IPE r
10、egistration . 12g36.4 AllJoyn service discovery 13g36.5 AllJoyn service mapping 13g36.5.1 AllJoyn service categorization 13g36.5.2 AllJoyn base service mapping 13g36.5.3 Other framework service mapping 14g36.5.4 AllJoyn app-specific service mapping 14g36.6 AllJoyn access control mapping . 14g37 Inte
11、rworking Procedures 14g37.1 Introduction 14g37.2 IPE initial configuration . 14g37.2.1 Introduction. 14g37.2.2 IPE registration and AllJoyn service discovery 15g37.2.3 AllJoyn Service Resource creation . 15g37.2.4 Subscription creation 18g37.2.4.1 Subscription creation by AE/CSE(s) acting as service
12、 producers . 18g37.2.4.2 Subscription creation by entities acting as service consumers 19g37.3 IPE interworking 20g37.3.1 Introduction. 20g37.3.2 AllJoyn services consumed by AE/CSE(s) . 20g37.3.3 AllJoyn services produced by oneM2M AE/CSE(s) via the IPE 21g37.3.4 AllJoyn services addition and delet
13、ion . 21g3Annex A (informative): oneM2M and AllJoyn technical comparison . 23g3A.1 API styles . 23g3A.2 Service Discovery/Advertisement 27g3Annex B (normative): resource specializations 28g3B.1 Introduction 28g3B.2 Resource Type svcObjWrapper 28g3B.3 Resource Type svcFwWrapper 29g3B.4 Resource Type
14、allJoynApp . 30g3B.5 Resource Type allJoynSvcObject . 33g3B.6 Resource Type allJoynInterface . 35g3ETSI ETSI TS 118 121 V2.0.0 (2016-09)4oneM2M TS-0021 version 2.0.0 Release 2B.7 Resource Type allJoynMethod . 37g3B.8 Resource Type allJoynMethodCall 38g3B.9 Resource Type allJoynProperty . 40g3Annex C
15、 (normative): AllJoyn interface mapping to oneM2M resource structure . 43g3C.1 Notification service 43g3C.1.1 Notification interface 43g3C.1.2 Notification Producer interface 44g3C.1.3 Dismisser interface . 45g3C.2 Control Panel service 46g3C.2.1 Container interface . 46g3C.2.2 Property interface .
16、47g3C.2.3 LabelProperty interface 49g3C.2.4 Action interface 50g3C.2.5 NotificationAction interface . 52g3C.2.6 Dialog interface 53g3C.2.7 ListProperty interface . 56g3C.3 Configuration service . 60g3C.3.1 Config interface 60g3Annex D (informative): Bibliography . 63g3History 64g3ETSI ETSI TS 118 12
17、1 V2.0.0 (2016-09)5oneM2M TS-0021 version 2.0.0 Release 2Intellectual 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, an
18、d 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
19、 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. Fore
20、word This Technical Specification (TS) has been produced by ETSI Partnership Project oneM2M (oneM2M). ETSI ETSI TS 118 121 V2.0.0 (2016-09)6oneM2M TS-0021 version 2.0.0 Release 21 Scope The present document specifies the oneM2M and AllJoyninterworking technologies that enable AllJoynApplications and
21、 oneM2M entities produce/consume services. Clause 5 defines the interworking architecture model that describes where the AllJoynIPE is hosted and how the IPE is composed with. Clause 6 defines the architecture aspects that mainly describes AllJoynservices to oneM2M resource mapping structure and rul
22、es. Furthermore, this explains the IPE registration and AllJoynservice discovery by the IPE. Clause 7 defines the IPE interworking procedures that consists of the initial setup and the service interworking procedures. NOTE: AllJoynis the trade name of a product supplied by the Allseen Alliance, Inc.
23、 This information is given for the convenience of users of the present document and does not constitute an endorsement by ETSI of the product named. Equivalent products may be used if they can be shown to lead to the same results.“ 2 References 2.1 Normative references References are either specific
24、 (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 fou
25、nd 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
26、 application of the present document. 1 ETSI TS 118 101: “oneM2M; Functional Architecture (oneM2M TS-0001)“. 2 ETSI TS 118 104: “oneM2M; Core Protocol (oneM2M TS-0004)“. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version numb
27、er) 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
28、 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:/www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf. i.
29、2 AllJoynSystem Description. NOTE: Available at http:/allseenalliance.org/framework/documentation. i.3 oneM2M TR-0014: “oneM2M and AllJoynInterworking“. ETSI ETSI TS 118 121 V2.0.0 (2016-09)7oneM2M TS-0021 version 2.0.0 Release 2i.4 D-Bus Tutorial. NOTE: Available at https:/dbus.freedesktop.org/doc/
30、dbus-tutorial.html. 3 Definitions For the purposes of the present document, the following terms and definitions apply: AllJoyn application: application that either produces an AllJoyn service or consumes an AllJoyn service AllJoyn consumer application: role of an AllJoyn application that consumes Al
31、lJoyn services provided by other AllJoyn applications AllJoyn producer application: role of an AllJoyn application that produces AllJoyn services consumed by other AllJoyn applications AllJoyn service resources: resources created as children of an resource representing an AllJoyn IPE for the purpose
32、 of exposing services between AllJoyn Consumer/Producer Applications and AE/CSE entities 4 Conventions The key words “Shall“, “Shall not“, “May“, “Need not“, “Should“, “Should not“ in the present document are to be interpreted as described in the oneM2M Drafting Rules i.1. 5 Architecture Model 5.1 R
33、eference model The architecture model followed in the present document is based on the architecture model in annex F of ETSI TS 118 101 1 that describes how interworking between oneM2M CSEs and non-oneM2M systems using specialized Interworking Proxy application Entities (IPE). The present document d
34、escibes the AllJoyn IPE that supports the following reference model. Figure 5.1-1: AllJoyn interworking reference model This reference model describes how the oneM2M AEs can interwork with AllJoyn applications. By the IPE, AllJoyn services are exposed as oneM2M resources and stored in a CSE. AEs acc
35、ess the exposed AllJoyn service resources by the oneM2M APIs. g4g367g367g58g381g455g374g3g4g393g393g367g349g272g258g410g349g381g374g3g18g94g28g3g4g367g367g58g381g455g374g3g87g396g381g410g381g272g381g367g3g4g367g367g58g381g455g374g3g47g87g28g3g68g272g258g3g4g28g3g68g272g258g4g94g69g876g68g69g876g47g6
36、9g3g18g94g28g3g68g272g272g876g68g272g272g859g3g68g69g876g47g69g3ETSI ETSI TS 118 121 V2.0.0 (2016-09)8oneM2M TS-0021 version 2.0.0 Release 25.2 Composition of the IPE The AllJoyn IPE consists of AE and AllJoyn application. To provide the interworking functions to other oneM2M entities, the IPE regis
37、ters to a CSE and communicate with other AllJoyn applications using AllJoyn protocols. The IPE registration is mandatory in oneM2M systems which is not defined in AllJoyn system. AllJoyn discovery and session establishment are needed for the IPE to communicate with other AllJoyn applications. In fig
38、ure 5.2-1, AllJoyn Application on the AllJoyn device and AllJoyn IPE is either AllJoyn Consumer or Producer Application. Depending on the interworking service scenario, AllJoyn Consumer and/or Producer Application is hosted on AllJoyn devices and AllJoyn IPEs. For example, when a AllJoyn service is
39、consumed by oneM2M entities, an AllJoyn devices hosts AllJoyn Producer Application and AllJoyn IPE hosts AllJoyn Consumer Application. In other case, if a oneM2M entity provides data to be consumed by AllJoyn Consumer Application on an AllJoyn device, then the AllJoyn IPE hosts AllJoyn Producer Appl
40、ication and the AllJoyn device hosts AllJoyn Consumer Application. AllJoyn IPEAEAllJoyn DeviceCSEMcaAllJoyn ProtocolAllJoyn ApplicationAllJoyn ApplicationFigure 5.2-1: Composition of the AllJoyn IPE 6 Architecture Aspect 6.1 Introduction oneM2M and AllJoyn have different architecture aspects (annex
41、A oneM2M and AllJoyn technical comparison). The present document specifies the interworking functions for those differences in the following aspects: oneM2M resource mapping structure; AllJoyn IPE registration; AllJoyn service discovery; AllJoyn service mapping; AllJoyn access control mapping. ETSI
42、ETSI TS 118 121 V2.0.0 (2016-09)9oneM2M TS-0021 version 2.0.0 Release 26.2 oneM2M resource mapping structure In this clause, the overall resource mapping structure for exposing service between AllJoyn Applications(either Producer or Consumer) and oneM2M entities is intrtoduced. Since it is difficult
43、 to put the resource tree into a single figure that remains well-readable, the description is split up in multiple figures, In this description, not all specified attributes of the used resource types and not all possible child resources are depicted to keep the figures readable, For example resourc
44、es which may be used to subscribe to some of the depicted resources are not shown. The resource mapping structure uses some specializations of the resource. Each of this specialization is detailed in annex B. The use of each of the resources within the resource mapping structure for consuming or pro
45、ducing services is defined in detail in clause 7. g1005g1005g69g258g373g349g374g336g90g286g400g381g437g396g272g286g3g100g455g393g286g3g876g94g393g286g272g349g258g367g349g460g258g410g349g381g374g448g258g367g437g286g3g381g296g3g367g258g271g286g367g400g400g448g272g75g271g361g286g272g410g400 g296g349g45
46、4g286g282g1092g296g367g286g454g18g381g374g410g258g349g374g286g396g1093g896g400g448g272g75g271g361g116g396g258g393g393g286g396g897“Iwked-Technology:AllJoyn”, “Iwked-Entity-Type:SvcObjectsg400g448g272g38g396g258g373g286g116g381g396g364g400 g296g349g454g286g282g1092g296g367g286g454g18g381g374g410g258g3
47、49g374g286g396g1093g896g400g448g272g38g449g116g396g258g393g393g286g396g897“Iwked-Technology:AllJoyn”, “Iwked-Entity-Type:SvcFrameWorks”g1092g4g28g1093g448g258g396g349g258g271g367g286 g1092g4g28g1093g862g4g367g367g58g381g455g374g882g47g87g28g863g1005g856g856g374g1092g18g94g28g17g258g400g286g1093g448g
48、258g396g349g258g271g367g286 g1092g18g94g28g17g258g400g286g1093g1092g4g28g1093g448g258g396g349g258g271g367g286 g1092g4g28g1093g69g381g410g3g349g374g272g367g437g282g349g374g336g3g862g4g367g367g58g381g455g374g882g47g87g28g863g1004g856g856g374Figure 6.2-1: AllJoyn interworking reseource mapping, part 1
49、In figure 6.2-1, the first part of the resource mapping structure for AllJoyn interworking is depicted. The resource of a CSE that is used for connecting to an AllJoyn proximal network is the root of the resource mapping structure. The IPE responsible for AllJoyn interworking - see the reference model described in clause 5 - will register with that CSE and will create an resource which represents the IPE. This resource shall include the string “AllJoyn-IPE“ in the labels attribute. All other relevant AllJoyn interworking resources will be
