1、 TIA-5022.002 October 2015Requirements (oneM2M TS-0002-v1.0.1) NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assi
2、sting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Standards a
3、nd Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards Institute (ANSI) patent policy. By
4、 such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the
5、responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. Any use of trademarks in this document are for information purposes and do not constitute an endorsement by TIA or this commit
6、tee of the products or services of the company. (From Project No. TIA-PN-5022.002, formulated under the cognizance of the TIA TR-50 M2M- Smart Device Communications.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Technology (b) there is no assurance that the Document will be approved by any C
7、ommittee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectual property rights (“IPR”), including pendin
8、g or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with
9、the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead left to the parties involved, nor will TIA
10、opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. If the Document contains one or mor
11、e Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional
12、 elements (as defined in the TIA Procedures for American National Standards) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary di
13、sclosure (see TIA Procedures for American National Standards Annex C.1.2.3) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim of
14、 Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL W
15、ARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. T
16、IA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN
17、THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
18、 (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUND
19、AMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 2 of 18 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be
20、made available by oneM2M Partners Type 1. About oneM2M The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in th
21、e field with M2M application servers worldwide. More information about oneM2M may be found at: http/www.oneM2M.org Copyright Notification No part of this document may be reproduced, in an electronic retrieval system or otherwise, except as authorized by written permission. The copyright and the fore
22、going restriction extend to reproduction in all media. 2015, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC). All rights reserved. Notice of Disclaimer the final version, if any, will be made available by oneM2M Partners Type 1. Contents 1 Scope 4 2 References 4 2.1 Normative referenc
23、es . 4 2.2 Informative references . 4 3 Definitions and abbreviations . 4 3.1 Definitions . 4 3.2 Abbreviations . 4 4 Conventions . 5 5 Introduction to the M2M ecosystem . 5 5.1 Functional roles description . 5 6 Functional Requirements 6 6.1 Overall System Requirements 6 6.2 Management Requirements
24、 12 6.3 Abstraction and Semantics Requirements . 12 6.3.1 Abstraction Requirements . 12 6.3.2 Semantics Requirements . 13 6.4 Security Requirements . 13 6.5 Charging Requirements 15 6.6 Operational Requirements 16 6.7 Communication Request Processing Requirements 16 7 Non-Functional Requirements (no
25、n-normative) . 17 History 18 oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 4 of 18 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1. 1 Scope The present document contains an informative fu
26、nctional role model and 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-spec
27、ific references, the latest version of the reference document (including any amendments) applies. The following referenced documents are necessary for the application of the present document. 1 3GPP TS 22.368: “Service requirements for Machine-Type Communications (MTC); Stage 1“. 2 oneM2M TR-0008: “
28、Security Analysis“. 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 references, the latest version of the reference documen
29、t (including any amendments) applies. 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:/member.onem2m.org/Static_pages/Others/Rules_Pa
30、ges/oneM2M-Drafting-Rules-V1_0.doc. i.2 oneM2M TS-0011: “Common Terminology“. i.3 3GPP2 S.R0146: “M2M System Requirements”. NOTE: Available at http:/www.3gpp2.org/Public_html/specs/S.R0146-0_v1.0_M2M_System_Requirements_20120829.pdf. 3 Definitions and abbreviations 3.1 Definitions For the purposes o
31、f the present document, the terms and definitions are given in oneM2M TS-0011 i.2. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CHA Continua Health Alliance GSMA Global System for Mobile Communications Association oneM2M Partners Type 1 (ARIB, ATIS,
32、CCSA, ETSI, TIA, TTA, TTC) Page 5 of 18 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1. HSM Hardware Security Module OMA Open Mobile Alliance QoS Quality of Service SMS Short Message Service USSD Unstructured
33、 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. Note: according to oneM2M Drafting Rules i.1 in order to mandate a
34、 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 be able to ”. This does not mandate usage of the required fea
35、ture in a M2M Solution. 5 Introduction to the M2M ecosystem 5.1 Functional roles description M2MA p p l i c a ti o nM2M Co mmo nS e r vi ceM2MA p p l .M2M CSUnd e r l y i ngN e t w o r kM 2MS e r v i ce P r ov i de r sNetw ork O pe r a t or so p e r a t e so p e r a t e so p e r a t e sanM2MSo lu ti
36、 o n.(e nd) use rC o n n ec t i v i t y S er v i c esUnd e r l y i ngN e t w o r kM 2M C o m m o n S er v i c esM 2M A p p l i c a t i o n sA ppl i ca t i on S e r v i ce P r ov i de r sFigure 1: Functional Roles in the M2M Ecosystem 1) The User (individual or company aka: end-user) fulfils all of t
37、he following criteria: - Uses an M2M solution. oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 6 of 18 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1. 2) The Application Service Provider f
38、ulfils all of the 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 o
39、f the following criteria: - 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 im
40、ply business roles or architectural assumptions. 6 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 Applications by using multiple communication means based
41、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, certain WLAN node). Implemented in Rel-1 OSR-002b The oneM2
42、M 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 The oneM2M System shall support the ability to maintain peer-to-peer M2M Session in co
43、ordination 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 session-less application communications for those M2M Applications that require it. Implemented in Rel-1 OSR-005 The oneM2M System shal
44、l 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 restriction based on Network Operators policy. Partially implemented in Re
45、l-1 (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 services are: IP Multimedia communications. Messaging. Location
46、. Charging and billing services. Device information and profiles. Configuration and management of devices. Partially implemented in Rel-1 (see note 10) oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 7 of 18 This is a draft oneM2M document and should not be relied upon; the final
47、 version, if any, will be made available by oneM2M Partners Type 1. Requirement ID Description Release Triggering, monitoring of devices. Small data transmission. Group management. (see note 1). OSR-007 The oneM2M System shall provide a mechanism for M2M Applications to interact with the Application
48、s 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 Applications to communicate with an M2M Device (i.e. application in the device) without the need for the M2M
49、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 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 requesting reliable delivery to decte
