1、 ETSI TS 118 102 V1.0.0 (2015-02) Requirements TECHNICAL SPECIFICATION ETSI ETSI TS 118 102 V1.0.0 (2015-02)2Reference DTS/oneM2M-000002 Keywords IoT, M2M, requirements ETSI 650 Route 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
2、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 document may be made available in electronic versions and/or in print. The content of
3、 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 in print, the only prevailing document is the print of the Portable Document F
4、ormat (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/st
5、atus/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 reproduced or utilized in any form or by any means, electronic or mechanical, including
6、 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 extend to reproduction in all media. European Telecommunications Standards Insti
7、tute 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 Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Mar
8、ks registered and owned by the GSM Association. ETSI ETSI TS 118 102 V1.0.0 (2015-02)3Contents Intellectual Property Rights 4g3Foreword . 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviation
9、s . 6g34 Conventions 6g35 Introduction to the M2M ecosystem. 6g35.1 Functional roles description . 6g36 Functional Requirements 7g36.1 Overall System Requirements 7g36.2 Management Requirements 12g36.3 Abstraction and Semantics Requirements 13g36.3.1 Abstraction Requirements . 13g36.3.2 Semantics Re
10、quirements. 13g36.4 Security Requirements . 14g36.5 Charging Requirements 15g36.6 Operational Requirements 16g36.7 Communication Request Processing Requirements . 16g37 Non-Functional Requirements (non-normative) 17g3Annex A (informative): Bibliography . 18g3History 19g3ETSI ETSI TS 118 102 V1.0.0 (
11、2015-02)4Intellectual 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
12、 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
13、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 Specification (TS) has been pr
14、oduced by ETSI Partnership Project oneM2M (oneM2M). ETSI ETSI TS 118 102 V1.0.0 (2015-02)51 Scope The present document contains an informative functional role model and normative technical requirements for oneM2M. 2 References 2.1 Normative references References are either specific (identified by da
15、te 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 reference document (including any amendments) applies. Referenced documents which are not found to be publicly a
16、vailable 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. The following referenced documents are necessary for the application of the p
17、resent document. 1 ETSI TS 122 368: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Service requirements for Machine-Type Communications (MTC); Stage 1 (3GPP TS 22.368)“. 2.2 Informative references References are either specific (identi
18、fied 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 reference document (including any amendments) applies. NOTE: While any hyperlinks included in this cla
19、use were valid at the time of publication, ETSI cannot 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. NOTE: Available at
20、 http:/member.onem2m.org/Static_pages/Others/Rules_Pages/oneM2M-Drafting-Rules-V1_0.doc. i.2 ETSI TS 118 111: “Common Terminology“. i.3 ETSI TR 118 508: “Security Analysis“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions are given
21、in ETSI TS 118 111 i.2. ETSI ETSI TS 118 102 V1.0.0 (2015-02)63.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CHA Continua Health Alliance GSMA Global System for Mobile Communications Association HSM Hardware Security Module OMA Open Mobile Alliance QoS
22、 Quality of Service SMS Short Message Service USSD Unstructured Supplementary Service Data WAN Wide Area Network 4 Conventions The keywords “shall“, “shall not“, “should“, “should not“, “may“, “need not“ in the present document are to be interpreted as described in the oneM2M Drafting Rules i.1. NOT
23、E: 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 formulated like: “The oneM2M System shall support a mechanism function, capability. to “, or “shall
24、 be able to “. This does not mandate usage of the required feature in a M2M Solution. 5 Introduction to the M2M ecosystem 5.1 Functional roles description g68g1006g68g4g393g393g367g349g272g258g410g349g381g374g68g1006g68g3g18g381g373g373g381g374g94g286g396g448g349g272g286g68g1006g68g4g393g393g367g856
25、g68g1006g68g3g18g94g104g374g282g286g396g367g455g349g374g336g69g286g410g449g381g396g364g68g1006g68g94g286g396g448g349g272g286g3g87g396g381g448g349g282g286g396g400g69g286g410g449g381g396g364g3g75g393g286g396g258g410g381g396g400g381g393g286g396g258g410g286g400g381g393g286g396g258g410g286g400g381g393g28
26、6g396g258g410g286g400g258g374g68g1006g68g94g381g367g437g410g349g381g374.g894g286g374g282g895g3g437g400g286g396g18g381g374g374g286g272g410g349g448g349g410g455g3g94g286g396g448g349g272g286g400g104g374g282g286g396g367g455g349g374g336g69g286g410g449g381g396g364g68g1006g68g3g18g381g373g373g381g374g3g94g2
27、86g396g448g349g272g286g400g68g1006g68g3g4g393g393g367g349g272g258g410g349g381g374g400g4g393g393g367g349g272g258g410g349g381g374g3g94g286g396g448g349g272g286g3g87g396g381g448g349g282g286g396g400Figure 1: Functional Roles in the M2M Ecosystem ETSI ETSI TS 118 102 V1.0.0 (2015-02)71) The User (individu
28、al or company - aka: end-user) fulfils all of the following criteria: - Uses an M2M solution. 2) The Application Service Provider fulfils all of the following criteria: - Provides an M2M Application Service. - Operates M2M Applications. 3) The M2M Service Provider fulfils all of the following criter
29、ia: - Provides M2M Services to Application Service Providers. - Operates M2M Common Services. 4) The Network Operator fulfils all of the following criteria: - Provides Connectivity and related services for M2M Service Providers. - Operates an Underlying Network. Such an Underlying Network could e.g.
30、 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 or architectural assumptions. 6 Functional Requirements 6.1 Overall System Requirements Table 1: Overall System Requirements Requirement ID Descriptio
31、n Release OSR-001 The oneM2M System shall allow communication between M2M 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,
32、memory, battery) or communication capabilities (e.g. 2G wireless modem, certain 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 mo
33、dem, wireline). Implemented in Rel-1 OSR-003 The oneM2M System shall support the ability to maintain peer-to-peer M2M Session in coordination with application session for those M2M Applications that require it. Partially implemented in Rel-1 (see note 21) OSR-004 The oneM2M System shall support sess
34、ion-less application communications for those M2M Applications 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.
35、g. Generic Bootstrapping Architecture), etc.),subject to restriction based on Network Operators policy. Partially implemented in Rel-1 (see note 9) ETSI ETSI TS 118 102 V1.0.0 (2015-02)8Requirement ID Description Release OSR-006 The oneM2M System shall be able to reuse the services offered by Underl
36、ying Networks to M2M Applications and/or M2M Services by means of open access models (e.g. OMA, GSMA OneAPI framework).Examples of available services are: IP Multimedia communications. Messaging. Location. Charging and billing services. Device information and profiles. Configuration and management o
37、f devices. Triggering, monitoring of devices. Small data transmission. Group management. (see note 1). Partially implemented in Rel-1 (see note 10) OSR-007 The oneM2M System shall provide a mechanism for M2M Applications to interact with the Applications and data/information managed by a different M
38、2M Service Provider, subject to permissions as appropriate. Implemented in Rel-1 OSR-008 The oneM2M System shall provide the capability for M2M Applications 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 technol
39、ogy 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 single or multiple M2M Applications to interact with a single or multiple M2M Devices/Gateways (application in the device/gateway) (see note 2). I
40、mplemented in Rel-1 OSR-010 The oneM2M System shall support mechanisms for confirmed delivery of a message to its addressee to those M2M Applications requesting reliable delivery to dectect failure of message within a given time interval. Implemented in Rel-1 OSR-011a The oneM2M System shall be able
41、 to request different communication paths, from the Underlying Network based on Underlying Network Operator and/or M2M Service Provider policies, routing mechanisms for transmission failures. Implemented in Rel-1 (see note 12) OSR-011b The oneM2M System shall be able to request different communicati
42、on paths from the Underlying Network based on request from M2M Applications. Not implemented in Rel-1 OSR-012 The oneM2M System shall support communications between M2M Applications and Devices supporting M2M Services by means of continuous or non-continuous connectivity. Implemented in Rel-1 OSR-01
43、3 The oneM2M System shall be aware of the delay 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 De
44、vices, behind an M2M Gateway that supports heterogeneous 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 st
45、reamed communication. Partially implemented in Rel-1 (see 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 N
46、etwork. 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 order to enable
47、 different deployment scenarios, these services shall be made available by the oneM2M System, individually, as a subset or as a complete set of services. Implemented in Rel-1 OSR-018 The oneM2M System shall be able to offer M2M Services to M2M Devices roaming across cellular Underlying Networks,subj
48、ect to restriction based on Network Operators policy (see note 3). Implemented in Rel-1 with some limitations (see note 14) ETSI ETSI TS 118 102 V1.0.0 (2015-02)9Requirement ID Description Release OSR-019 The oneM2M System shall support the capabilities for data repository (i.e. to collect/store) an
49、d for data transfer from one or more M2M Devices or M2M Gateways, for delivery to one or more M2M Gateways, M2M Services Infrastructure, or M2M Application Infrastructure, in ways requested by the M2M Application Infrastructure as listed below: action initiated either by an M2M Device, M2M Gateway, M2M Services Infrastructure, or M2M Application Infrastructure; when triggered by schedule or event; for specified data. Implemented in Rel-1 OSR-020 The oneM2M System shall be able to support policies and their management rega
