1、 TIA-5022.011 October 2015Common Terminology (oneM2M TS-0011-v1.2.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, an
2、d assisting 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 Stand
3、ards and 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 poli
4、cy. By 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 i
5、s the 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
6、committee of the products or services of the company. (From Project No. TIA-PN-5022.011, 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
7、 any Committee 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
8、pending 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
9、 with 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 wil
10、l TIA 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
11、or more 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 op
12、tional 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 volunt
13、ary disclosure (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 cl
14、aim of 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.
15、 ALL WARRANTIES, 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 RIG
16、HTS. TIA 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
17、TO IN 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 D
18、AMAGES (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
19、A FUNDAMENTAL 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 17 This is a draft oneM2M document and should not be relied upon; the final version, if any, wil
20、l be 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
21、in the 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
22、 foregoing 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 5 2 References 5 2.1 Normative ref
23、erences . 5 2.2 Informative references . 5 3 Definitions 6 3.0 General Information . 6 3.1 0-9 . 6 3.2 A 6 3.3 B 7 3.4 C 7 3.5 D 8 3.6 E 8 3.7 F 8 3.8 G 8 3.9 H 8 3.10 I . 8 3.11 J . 9 3.12 K 9 3.13 L 9 3.14 M . 9 3.15 N 9 3.16 O 9 3.17 P 10 3.18 Q 10 3.19 R 10 3.20 S 10 3.21 T 11 3.22 U 11 3.23 V 1
24、2 3.24 W . 12 3.25 X 12 3.26 Y 12 3.27 Z 12 4 Abbreviations . 12 4.1 0-9 . 12 4.2 A 12 4.3 B 12 4.4 C 12 4.5 D 13 4.6 E 13 4.7 F 13 4.8 G 13 4.9 H 13 4.10 I . 13 4.11 J . 13 4.12 K 13 4.13 L 13 4.14 M . 13 4.15 N 13 4.16 O 14 4.17 P 14 4.18 Q 14 4.19 R 14 4.20 S 14 4.21 T 14 OneM2M Partners Type 1 (
25、ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC Page 4 of 17 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. 4.22 U 14 4.23 V 14 4.24 W . 14 4.25 X 14 4.26 Y 14 4.27 Z 15 Annex A (informative): Bibliography . 16 Histor
26、y 17 OneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC Page 5 of 17 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 a collection of specialist technical terms
27、, definitions and abbreviations referenced within the oneM2M specifications. Having a common collection of definitions and abbreviations related to oneM2M documents will: ensure that the terminology is used in a consistent manner across oneM2M documents; provide a reader with convenient reference fo
28、r technical terms that are used across multiple documents. The present document provides a tool for further work on oneM2M technical documentation and facilitates their understanding. The definitions and abbreviations as given in the present document are either externally created and included here,
29、or created internally within oneM2M by the oneM2M TP or its working groups, whenever the need for precise vocabulary is identified or imported from existing documentation. In addition in oneM2M Technical Specifications and Technical Reports there are also clauses dedicated for locally unique definit
30、ions and abbreviations. 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 latest version of the re
31、ference document (including any amendments) applies. 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 version number) or
32、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. The following referenced documents are not necessary for the application of the present document but they assist the us
33、er with regard to a particular subject area. i.1 Recommendation ITU-T X.800 (1991): “Security architecture for open system interconnection for CCIT applications”. i.2 Recommendation ITU-T X.800/Amd.1 (1996): “Security architecture for open systems interconnection for CCITT applications. Amendment 1:
34、 Layer Two Security Service and Mechanisms for LANs”. i.3 ISO/IEC 27001 (2005): “Information technology Security techniques Information security management systems Requirements”. i.4 ISO/IEC 27002 (2005): “Information technology Security techniques Code of practice for information security managemen
35、t”. i.5 IETF RFC 4949 (2007): “Internet Security Glossary, Version 2”. i.6 NIST SP800-57 Part 1 (07/2012): “Recommendation for Key Management General, Rev3”. i.7 NIST SP800-57 Part 1 (05/2011): “Recommendation for Key Management General, Rev3”. OneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TT
36、A, TTC Page 6 of 17 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. i.8 ISO/IEC 13888-1 (07/2009 3rd ed) Information technology Security techniques Non-repudiation Part 1: General”. i.9 ISO/IEC 24760-1 (12/20
37、11 1st edition): “Information technology Security techniques A framework for identity management Part 1: terminology and concepts”. i.10 ISO/IEC 27004 (12/2009 1st edition): “Information technology Security techniques Information security management Measurement”. i.11 ISO/IEC 9798-1 (07/2010 3rd edi
38、tion): “Information technology Security techniques Entity authentication -. Part 1: General”. i.12 ISO/IEC TR 15443-1:2012: “Information technology Security techniques Security assurance framework Part 1: Introduction and concepts”. i.13 IEEE 802.15.4TM-2003: “IEEE Standard for Local and metropolita
39、n area networks Part 15.4: Low-Rate Wireless Personal Area Networks (LR-WPANs)”. 3 Definitions 3.0 General Information NOTE 1: Whenever in the present document a term “M2M Xyz” (e.g. M2M Application, M2M Solution, etc.) is used, then the prefix “M2M” should indicate that unless otherwise indicated t
40、he term identifies an entity Xyz that complies with oneM2M specifications. NOTE 2: For better readability of the present document the prefix “M2M” is ignored when definitions are alphabetically ordered. 3.1 0-9 Void. 3.2 A abstract information model: information Mmdel of common functionalities abstr
41、acted from a set of Device Information Models abstraction: process of mapping between a set of Device Information Models and an Abstract Information Model according to a specified set of rules access control attributes: set of parameters of the originator, target resource, and environment against wh
42、ich there could be rules evaluated to control access NOTE: An example of Access Control Attributes of Originator is a role. Examples of Access Control Attributes of Environment are time, day and IP address. An example of Access Control Attributes of targeted resource is creation time. access control
43、 policy: set of privileges which represents access control rules defining allowed entities for certain operations within specified contexts that each entity has to comply with to grant access to an object access control role: security attribute associated to an entity defining the entitys access rig
44、hts or limitations to allowed operations NOTE: One or more operations can be associated to an Access Control Role. An Access Control Role can be associated to one or more entities and an entity can assume one or more Access Control Roles. access decision: authorization reached when an entitys Privil
45、eges are evaluated analytics: processing which makes use of data to provide actions, insights and/or inference OneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC Page 7 of 17 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available b
46、y oneM2M Partners Type 1. M2M application: applications that run the service logic and use M2M Common Services accessible via a set of oneM2M specified open interfaces NOTE: Specification of M2M Applications is not subject of the current oneM2M specifications. M2M area network: is a form of an Under
47、lying Network that minimally provides data transport services among M2M Gateway(s), M2M Device(s), and Sensing the final version, if any, will be made available by oneM2M Partners Type 1. credentials: data objects which are used to uniquely identify an entity and which are used in security procedure
48、s. credential-ID: A globally unique identifier for a credential that was used to establish a security association between entities (CSEs and/or AEs). NOTE: The Credential-ID can be used to determine the identifying information about the authenticated entity, such as the CSE-ID or AE-ID(s) or App-ID(
49、s). 3.5 D data: in the context of oneM2M the term “Data” signifies digital representations of anything NOTE: Data can or cannot be interpreted by the oneM2M System and/or by M2M Applications. See also Information. M2M device: physical equipment with communication capabilities, providing computing and/or sensing and/or actuation services NOTE: An M2M Device hosts one or more M2M Applications or other applications and can contain implementations of CSE functionalities. EXAMPLE: Physical mapp
