1、 ETSI TR 118 503 V1.0.0 (2015-04) Architecture Part 2: Study for the merging of architectures proposed for consideration by oneM2M TECHNICAL REPORT ETSI ETSI TR 118 503 V1.0.0 (2015-04) 2 Reference DTR/oneM2M-000003 Keywords architecture, IoT, M2M ETSI 650 Route des Lucioles F-06921 Sophia Antipolis
2、 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-search The present docume
3、nt 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
4、 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 stat
5、us 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: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduc
6、ed 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 e
7、xtend to reproduction in all media. European Telecommunications Standards Institute 2015. 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 registered for the benefit of its Memb
8、ers 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 503 V1.0.0 (2015-04) 3 Contents Intellectual Property Rights 4g3Foreword . 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative refer
9、ences 5g33 Abbreviations . 6g34 Conventions 6g35 Analysis of Functional Entities 6g35.1 Existing Functional Entities: ATIS, ETSI, TIA 6g36 Analysis of existing Reference Points 8g36.1 Reference Point analysis 8g36.2 Reference Points vs. Functions . 10g37 Analysis of architecture styles 10g37.1 REST
10、10g37.2 SOAP 11g38 Conclusions 11g3Annex A: Bibliography 12g3History 13g3ETSI ETSI TR 118 503 V1.0.0 (2015-04) 4 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
11、 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
12、 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,
13、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 503 V1.0.0 (2015-04) 5 1 Scope The present document provides an evaluation of existing M2M-related Architecture work undertaken by the
14、 founding partners of oneM2M, including: the Association of Radio Industries and Businesses (ARIB) and the Telecommunication Technology Committee (TTC) of Japan; the Alliance for Telecommunications Industry Solutions (ATIS) and the Telecommunications Industry Association (TIA) of the USA; the China
15、Communications Standards Association (CCSA); the European Telecommunications Standards Institute (ETSI); and the Telecommunications Technology Association (TTA) of Korea. Common Functional Entities and Reference Points are identified, as well as critical differences. New functionality will not be co
16、nsidered as part of this study. The present document is intended to ensure a common understanding of existing M2M Architectural approaches, in order to facilitate future normative work resulting in oneM2M Technical Specifications. The present document has been prepared under the auspices of the oneM
17、2M Technical Plenary, by the oneM2M Architecture Working Group. 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
18、references, the latest version of the reference 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
19、the time of publication, ETSI cannot guarantee their long term validity. 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
20、 version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cann
21、ot 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. i.2 ATIS Machine to Machine (M2M) Committee. i.3 ETSI Machine to Machi
22、ne (M2M) Committee. i.4 IETF draft-ietf-core-coap: “Constrained Application Protocol (CoAP)“. i.5 OMA Lightweight M2M. i.6 OMA-DM (OMA): “OMA Device Management“. i.7 Fielding, R.T., (2000), Dissertation: “Architectural Styles and the Design of Network-based Software Architectures, Chapter 5 - Repres
23、entational State Transfer (REST)“. University of California Irvine. i.8 TIA TR-50 - M2M: “Smart Device Communications“. ETSI ETSI TR 118 503 V1.0.0 (2015-04) 6 3 Abbreviations For the purposes of the present document, the following abbreviations apply: 3GPP 3rdGeneration Partnership Project AAA Auth
24、entication, Authorization and Accounting AAA-SD Authentication, Authorization and Accounting-subscriber device API Application programming Interface ARC oneM2M Architecture Working Group ARIB Association of Radio Industries and Businesses (JP) ASP Application Service provider ATIS Alliance for Telec
25、ommunications Industry Solutions CCSA China Communications Standards Association CoAP Constrained Application Protocol CoRE Constrained Restful Environments DA Device Application DSCL Device Service Capability Layer ETSI European Telecommunications Standards Institute GA Gateway Applications GSCL Ga
26、teway Service Capability Layer HATEOAS Hypermedia As The Engine Of Application State HTTP HyperText Transfer Protocol IETF Internet Engineering Task Force IF Interface M2M Machine to Machine (communications) MAS M2M Authentication Server MSBF M2M Service Bootstrap Function MSP Machine to Machine Ser
27、vice Provider MTC Machine Type Communication NA Network Applications NSCL Network Service Capability Layer NW NetworkOMA LWM2M Open Mobile Alliance - Light Weight M2M OMA Open Mobile Alliance PoA Point of Attachment REST Representational State Transfer is a style of API interface RPC Remote Procedur
28、e Call SOAP Simple Object Access Protocol TIA Telecommunications Industry Association TP oneM2M Technical Plenary TTA Telecommunications Technology Association TTC Telecommunication Technology Committee WSDL Web Service Description Language XML Extensible Markup Language 4 Conventions The key words
29、“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 Analysis of Functional Entities 5.1 Existing Functional Entities: ATIS, ETSI, TIA This clause provides a comparative analysis of existing ATI
30、S M2M i.2, ETSI M2M i.3, and TIA TR-50 i.8, functional architectural entities. Table 5.1 provides a comparative matrix of the functional architectural entities supported by each architecture. ETSI ETSI TR 118 503 V1.0.0 (2015-04) 7 Table 5.1: TIA, ATIS, and ETSI M2M Functional Entity Comparative Mat
31、rix Functional Entity TIA TR-50 ATIS ETSI M2M M2M Service Capability hosted in the network domain Yes Server Container Yes Service Capabilities Yes Network Service Capability Layer (NSCL) M2M Service Capability hosted on an intermediary node Yes PoA Container No Yes Gateway Service Capability Layer
32、(GSCL) M2M Service Capability hosted on an M2M Device Yes PoA Container No Yes Device Service Capability Layer (DSCL) Applications in the network domain Yes home applications Yes Applications Yes Network Applications (NA) Applications in the intermediary node Yes Node Application No Yes Gateway Appl
33、ication (GA) Applications in the M2M Device Yes PoA Application No Yes Device Application (DA) M2M Network Yes Server Yes Network Service Functions Yes Network Domain M2M intermediary node Yes PoA Device No Yes M2M Gateway M2M Device Yes PoA Device Yes Device Yes Device with Service Capabilities (D)
34、 Device without Service Capabilities (D) Legacy non-ETSI Device (d) AAA Server Yes AAA-SD No Yes M2M Authentication Server (MAS), M2M Service Bootstrap function (MSBF) NOTE: Functional Elements depicted in this figure may be placed anywhere, not necessarily outside the Access/Core network. The role/
35、placement of AAA Server is for further study. Figure 5.1: TIA, ATIS, and ETSI M2M Functional Architectural Entities Figure 5.1 provides a high level overview of the common components when examining TIA TR-50 i.8, ETSI M2M i.3, and ATIS M2M i.2 functional architectural entities. ETSI ETSI TR 118 503
36、V1.0.0 (2015-04) 8 6 Analysis of existing Reference Points 6.1 Reference Point analysis This clause provides a comparative analysis of existing TIA TR-50 i.8, ETSI M2M i.3, and ATIS M2M i.2, architectural reference points. Figure 6.1 shows the reference points from each source consolidated into a si
37、ngle functional architecture. Table 6.1 provides a comparative matrix of the reference points supported by each architecture. Figure 6.1: TIA, ATIS, and ETSI M2M Reference Point Analysis Figure 6.1 provides a high level architectural overview with reference points of the common components when exami
38、ning TIA TR-50, ETSI M2M, and ATIS M2M functional architectural entities. Details of the reference points are provided in tables 6.1 and 6.2. Table 6.1 also provides details of 3GPP reference points pertaining to Machine Type Communication (MTC). ETSI ETSI TR 118 503 V1.0.0 (2015-04) 9 Table 6.1: TI
39、A, ETSI, ATIS, and 3GPP Reference Point Analysis for M2M Reference Point/Interface Description Corresponding Reference Point Comment TIA ETSI ATIS 3GPP M2M Device Application M2M Device Application B5 M2M Gateway Application M2M Gateway Application B4 M2M Device Application M2M Gateway Application B
40、3 M2M Device Application M2M Network Application B2 M2M Gateway Application M2M Network Application B1 M2M Device Application M2M Device B9 M2M Gateway Application M2M Device B3 M2M Network Application M2M Device B2 * * ATIS Shows an interface Traffic Flow (Option 2) M2M Network Application Access/C
41、ore Network Provider Gi/Sgi M2M Device Application M2M Device Service Layer dIa M2M Device Application M2M Gateway Service Layer dIa M2M Gateway Application M2M Device Service Layer B8 M2M Gateway Application M2M Gateway Service Layer dIa M2M Network Application M2M Device Service Layer B7 M2M Netwo
42、rk Application M2M Gateway Service Layer B6 M2M Network Application M2M Network Service Layer mIa ASP IF M2M Device Service Layer M2M Network Service Layer mId M2M Gateway Service Layer M2M Network Service Layer mId M2M Network Service Layer M2M Network Service Layer mIm M2M Network Service Layer M2
43、M Device * * ATIS Shows an interfaces Traffic Flow (Option 1) and Device Mangement M2M Network Service Layer Access/Core Network Provider MSP IF TSP M2M Device M2M Device B5 M2M Device Access/Core Network Provider NW IF M2M Network Application AAA Server A1 M2M Gateway Application AAA Server A2 M2M
44、Device Application AAA Server A3 M2M Device AAA Server A3 M2M Network Service Layer AAA Server MAS/ MSBF ETSI ETSI TR 118 503 V1.0.0 (2015-04) 10 6.2 Reference Points vs. Functions Table 6.2 provides a comparative analysis of the reference points defined by TIA TR-50 i.8, ATIS M2M i.2, and ETSI M2M
45、i.3. Table 6.2: TIA, ATIS, and ETSI M2M Comparative Reference Point Feature Matrix Feature TIA TR-50 ATIS M2M ETSI M2M Reference points to support M2M Service Capabilities hosted on a M2M device Yes (B7, B8) No Yes(dIa,mId) Reference points to support an intermediary M2M gateway/node Yes (B1,B4,B6,B
46、3,B3,B8, A2) No Yes(dIa,mId) Reference points to support communication with access/core network entities No Yes (NW IF, MSP IF) No Reference points to support M2M Service Capabilities hosted in the network No Yes(MSP IF, ASP IF) Yes (mIa,mId,mIm) Reference points to support hierarchical M2M Service
47、Capabilities on Device, Gateway and Network No No Yes(mIa,mId,dIa) Reference points to support direct application-to-application communication Yes (B1, B2, B3, B4, B5) No NoReference points to support direct device-to-device communication Yes (B5) No No Reference points to support communication betw
48、een two instances of M2M Service Capabilities hosted in the network No No Yes(mIm) Reference points to support direct communication between network applications and devices and gateways (i.e. bypass M2M Network Service Capabilities) Yes (B2) Yes (Optional Traffic Flow option #2) No Reference points
49、to support direct communication between network applications and M2M Service Capabilities hosted on devices and gateways (i.e. bypass M2M Network Service Capabilities) Yes (B6, B7) No No 7 Analysis of architecture styles 7.1 REST REST stands for Representational State Transfer. It is a style of API interface. When the API of a system qualifies RESTs features, we say the system is RESTful. REST was first described by R.T. Fielding in his Doctor
