1、 ETSI TS 118 102 V2.7.1 (2016-09) oneM2M Requirements (oneM2M TS-0002 version 2.7.1 Release 2) TECHNICAL SPECIFICATION ETSI ETSI TS 118 102 V2.7.1 (2016-09)2oneM2M TS-0002 version 2.7.1 Release 2Reference RTS/oneM2M-000002v200 Keywords IoT, M2M, requirements ETSI 650 Route des Lucioles F-06921 Sophi
2、a 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-search The pre
3、sent 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 between such vers
4、ions 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. Information on the c
5、urrent 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 Notification No
6、 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 copyright and the fo
7、regoing 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 registered for th
8、e 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 102 V2.7.1 (2016-09)3oneM2M TS-0002 version 2.7.1 Release 2Contents Intellectual Property Rights 4g3Foreword . 4g31 Scope 5g32 Referenc
9、es 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Conventions 6g35 Introduction to the M2M ecosystem. 7g35.1 Functional roles description . 7g36 Functional Requirements 8g36.1 Overall System Requirements
10、 8g36.2 Management Requirements 13g36.3 Semantics Requirements 14g36.3.1 Ontology Related Requirements . 14g36.3.2 Semantics Annotation Requirements 15g36.3.3 Semantics Query Requirements 16g36.3.4 Semantics Mashup Requirements . 16g36.3.5 Semantics Reasoning Requirements . 16g36.3.6 Data Analytics
11、Requirements . 16g36.4 Security Requirements . 17g36.5 Charging Requirements 20g36.6 Operational Requirements 21g36.7 Communication Management Requirements . 21g36.8 LWM2M Interworking Requirements 23g37 Non-Functional Requirements (informative) . 23g3Annex A (informative): Requirements for the next
12、 release 24g3History 25g3ETSI ETSI TS 118 102 V2.7.1 (2016-09)4oneM2M TS-0002 version 2.7.1 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 av
13、ailable 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 se
14、rver (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 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 bec
15、ome, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Partnership Project oneM2M (oneM2M). ETSI ETSI TS 118 102 V2.7.1 (2016-09)5oneM2M TS-0002 version 2.7.1 Release 21 Scope The present document contains an informative functional role model and
16、 normative technical requirements for oneM2M. 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 references, the la
17、test 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:/docbox.etsi.org/Reference/. NOTE: While any hyperlinks included in this clause were valid at the time of pub
18、lication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. 1 ETSI TS 122 368: “Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Service req
19、uirements for Machine-Type Communications (MTC); Stage 1 (3GPP TS 22.368)“. 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 references, only the cited version applies. For non-specific
20、 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 following referenced documents are not necessary for the applic
21、ation 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:/member.onem2m.org/Static_pages/Others/Rules_Pages/oneM2M-Drafting-Rules-V1_0.doc. i.2 ETSI TS 118 111: “oneM2M; Common Terminology (oneM2M TS-0011)“. i
22、.3 ETSI TR 118 508: “Analysis of Security Solutions for the oneM2M System“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI TS 118 111 i.2 apply. ETSI ETSI TS 118 102 V2.7.1 (2016-09)6oneM2M TS-0002 version 2.7.1 Relea
23、se 23.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AE Application Entity API Application Program Interface BBF BroadBand Forum CHA Continua Health Alliance CPU Central Processing Unit DM Device ManagementGBA Generic Bootstrapping Architecture GSMA Glob
24、al System for Mobile Communications Association GW Gateway HGI Home Gateway Initiative HSM Hardware Security Module IP Internet Protocol MTC Machine Type Communications OMA Open Mobile Alliance OSR Overall System Requirements OWL Web Ontology Language QoS Quality of Service RDF Resource Description
25、Framework SMS Short Message Service UICC Universal Integrated Circuit Card USIM UMTS Subscriber Identity Module USSD Unstructured Supplementary Service Data WAN Wide Area Network WLAN Wireless Local Area Network 4 Conventions The keywords “shall“, “shall not“, “should“, “should not“, “may“, “need no
26、t“ in the present document are to be interpreted as described in the oneM2M Drafting Rules i.1. NOTE: According to oneM2M Drafting Rules i.1 in order to mandate a feature in the oneM2M System but allow freedom to the individual deployment whether to use it or not subsequently requirements are often
27、formulated like: square4 “The oneM2M System shall support a mechanism function, capability. to “; or square4 “shall be able to “. This does not mandate usage of the required feature in a M2M Solution. ETSI ETSI TS 118 102 V2.7.1 (2016-09)7oneM2M TS-0002 version 2.7.1 Release 25 Introduction to the M
28、2M ecosystem 5.1 Functional roles description g68g1006g68g4g393g393g367g349g272g258g410g349g381g374g68g1006g68g3g18g381g373g373g381g374g94g286g396g448g349g272g286g68g1006g68g4g393g393g367g856g68g1006g68g3g18g94g104g374g282g286g396g367g455g349g374g336g69g286g410g449g381g396g364g68g1006g68g94g286g396g
29、448g349g272g286g3g87g396g381g448g349g282g286g396g400g69g286g410g449g381g396g364g3g75g393g286g396g258g410g381g396g400g381g393g286g396g258g410g286g400g381g393g286g396g258g410g286g400g381g393g286g396g258g410g286g400g258g374g68g1006g68g94g381g367g437g410g349g381g374.g894g286g374g282g895g3g437g400g286g39
30、6g18g381g374g374g286g272g410g349g448g349g410g455g3g94g286g396g448g349g272g286g400g104g374g282g286g396g367g455g349g374g336g69g286g410g449g381g396g364g68g1006g68g3g18g381g373g373g381g374g3g94g286g396g448g349g272g286g400g68g1006g68g3g4g393g393g367g349g272g258g410g349g381g374g400g4g393g393g367g349g272g2
31、58g410g349g381g374g3g94g286g396g448g349g272g286g3g87g396g381g448g349g282g286g396g400Figure 1: Functional Roles in the M2M Ecosystem 1) The User (individual or company aka: end-user) fulfils all of the following criteria: - Uses an M2M solution. 2) The Application Service Provider fulfils all of the
32、following criteria: - Provides an M2M Application Service. - Operates M2M Applications. 3) The M2M Service Provider fulfils all of the following criteria: - Provides M2M Services to Application Service Providers. - Operates M2M Common Services. 4) The Network Operator fulfils all of the following cr
33、iteria: - Provides Connectivity and related services for M2M Service Providers. - Operates an Underlying Network. Such an Underlying Network could e.g. be a telecom network. Any of the above functional roles may coincide with any of the other roles. These functional roles do not imply business roles
34、 or architectural assumptions. ETSI ETSI TS 118 102 V2.7.1 (2016-09)8oneM2M TS-0002 version 2.7.1 Release 26 Functional Requirements 6.1 Overall System Requirements Table 1: Overall System Requirements Requirement ID Description Release OSR-001 The oneM2M System shall allow communication between M2M
35、 Applications by using multiple communication means based on IP access. Implemented in Rel-1 OSR-002a The oneM2M System shall support communication means that can accommodate devices with constrained computing (e.g. small CPU, memory, battery) or communication capabilities (e.g. 2G wireless modem, c
36、ertain WLAN node). Implemented in Rel-1 OSR-002b The oneM2M System shall support communication means that can accommodate devices with rich computing capabilities (e.g. large CPU, memory) or communication (e.g. 3/4G wireless modem, wireline). Implemented in Rel-1 OSR-003 See REQ-2015-0626R01 The one
37、M2M System shall support the ability to maintain application-to-application communication in coordination with an application session for those M2M Applications that require it. Not implemented OSR-004 The oneM2M System shall support session-less application communications for those M2M Applications
38、 that require it. Implemented in Rel-1 OSR-005 The oneM2M System shall be able to expose the services offered by telecommunications networks to M2M Applications (e.g. SMS, USSD, localization, subscription configuration, authentication (e.g. Generic Bootstrapping Architecture), etc.),subject to restr
39、iction based on Network Operators policy. Partially implemented (see note 9) OSR-006 The oneM2M System shall be able to reuse the services offered by Underlying Networks to M2M Applications and/or M2M Services by means of open access models (e.g. OMA, GSMA OneAPI framework).Examples of available ser
40、vices are: IP Multimedia communications. Messaging. Location. Charging and billing services. Device information and profiles. Configuration and management of devices. Triggering, monitoring of devices. Small data transmission. Group management. (see note 1). Partially implemented (see note 10) OSR-0
41、07 The oneM2M System shall provide a mechanism for M2M Applications to interact with the Applications and data/information managed by a different M2M Service Provider, subject to permissions as appropriate. Implemented in Rel-1 OSR-008 The oneM2M System shall provide the capability for M2M Applicati
42、ons to communicate with an M2M Device (i.e. application in the device) without the need for the M2M Applications to be aware of the network technology and the specific communication protocol of the M2M Device. Implemented in Rel-1 (see note 11) OSR-009 The oneM2M System shall support the ability for
43、 single or multiple M2M Applications to interact with a single or multiple M2M Devices/Gateways (application in the device/gateway) (see note 2). Implemented in Rel-1 OSR-010 The oneM2M System shall support mechanisms for confirmed delivery of a message to its addressee to those M2M Applications req
44、uesting reliable delivery to dectect failure of message within a given time interval. Implemented in Rel-1 OSR-011a The oneM2M System shall be able to request different communication paths, from the Underlying Network based on Underlying Network Operator and/or M2M Service Provider policies, routing
45、 mechanisms for transmission failures. Implemented in Rel-1 (see note 12) OSR-011b The oneM2M System shall be able to request different communication paths from the Underlying Network based on request from M2M Applications. Not implemented OSR-012 The oneM2M System shall support communications betwe
46、en M2M Applications and M2M Devices supporting M2M Services by means of continuous or non-continuous connectivity. Implemented in Rel-1 ETSI ETSI TS 118 102 V2.7.1 (2016-09)9oneM2M TS-0002 version 2.7.1 Release 2Requirement ID Description Release OSR-013 The oneM2M System shall be aware of the delay
47、 tolerance acceptable by the M2M Application and shall schedule the communication accordingly or request the Underlying Network to do it, based on policies criteria. Implemented in Rel-1 OSR-014 The oneM2M System shall be able to communicate with M2M Devices, behind an M2M Gateway that supports hete
48、rogeneous M2M Area Networks. Implemented in Rel-1 OSR-015 The oneM2M System shall be able to assist Underlying Networks that support different communication patterns including infrequent communications, small data transfer, transfer of large file and streamed communication. Partially implemented (se
49、e note 13) OSR-016 The oneM2M System shall provide the capability to notify M2M Applications of the availability of, and changes to, available M2M Application/management information on the M2M Device/Gateway, including changes to the M2M Area Network. Implemented in Rel-1 OSR-017 The oneM2M System shall be able to offer access to different sets of M2M Services to M2M Application Providers. The minimum set of services are: Connectivity management. Device management (service level management). Application Data management. In ord
