TIA-5022 001-2015 Functional Architecture (oneM2M TS-0001-v1 6 1).pdf

1、 TIA-5022.001 October 2015Functional Architecture (oneM2M TS-0001-v1.6.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 product

2、s, and 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

3、Standards 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

4、 policy. 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.

5、 It is 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

6、this committee of the products or services of the company. (From Project No. TIA-PN-5022.001, 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 approv

7、ed by 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”), inclu

8、ding 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 accor

9、dance 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, no

10、r will 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

11、 one 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

12、or optional 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 v

13、oluntary 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

14、 a claim 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 Docu

15、ment. 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 PROPERT

16、Y RIGHTS. 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 REFE

17、RRED 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 CONSEQUENT

18、IAL DAMAGES (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 DAMAGE

19、S IS 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 321 This is a draft oneM2M document and should not be relied upon; the final version, if a

20、ny, will 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 d

21、evices 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

22、and the 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 11 2 References 11 2.1 Norm

23、ative references . 11 2.2 Informative references . 11 3 Definitions, abbreviations and acronyms . 12 3.1 Definitions . 12 3.2 Abbreviations and Acronyms . 14 4 Conventions . 16 5 Architecture Model 17 5.1 General Concepts . 17 5.2 Architecture Reference Model 17 5.2.1 Functional Architecture 17 5.2.

24、2 Reference Points . 18 5.2.2.1 Mca Reference Point . 18 5.2.2.2 Mcc Reference Point . 18 5.2.2.3 Mcn Reference Point . 18 5.2.2.4 Mcc Reference Point 19 5.2.2.5 Other Reference Points 19 6 oneM2M Architecture Aspects. 19 6.1 Configurations supported by oneM2M Architecture . 19 6.2 Common Services F

25、unctions 21 6.2.1 Application and Service Layer Management . 21 6.2.1.1 General Concepts 21 6.2.1.2 Detailed Descriptions 22 6.2.1.2.1 Software Management Function. 22 6.2.2 Communication Management and Delivery Handling . 22 6.2.2.1 General Concepts 22 6.2.2.2 Detailed Descriptions 23 6.2.3 Data Ma

26、nagement and Repository 23 6.2.3.1 General Concepts 23 6.2.3.2 Detailed Descriptions 23 6.2.4 Device Management . 24 6.2.4.1 General Concepts 24 6.2.4.1.1 Device Management Architecture 24 6.2.4.1.2 Management Server Interaction . 25 6.2.4.1.3 Management Client Interaction 27 6.2.4.1.4 Device Manage

27、ment Resource Lifecycle . 28 6.2.4.2 Detailed Descriptions 28 6.2.4.2.1 Device Configuration Function 29 6.2.4.2.2 Device Diagnostics and Monitoring Function 29 6.2.4.2.3 Device Firmware Management Function 29 6.2.4.2.4 Device Topology Management Function 30 6.2.5 Discovery . 30 6.2.5.1 General Conc

28、epts 30 6.2.5.2 Detailed Descriptions 30 6.2.6 Group Management 30 6.2.6.1 General Concepts 30 6.2.6.2 Detailed Descriptions 30 6.2.7 Location . 31 6.2.7.1 General Concepts 31 6.2.7.2 Detailed Descriptions 31 6.2.8 Network Service Exposure, Service Execution and Triggering 32 6.2.8.1 General Concept

29、s 32 6.2.8.2 Detailed Descriptions 32 oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 4 of 321 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. 6.2.9 Registration 32 6.2.9.1 General Concept

30、s 32 6.2.9.2 Detailed Descriptions 33 6.2.10 Security 33 6.2.10.1 General Concepts 33 6.2.10.2 Detailed Descriptions 34 6.2.11 Service Charging and Accounting . 35 6.2.11.1 General Concepts 35 6.2.11.2 Detailed Descriptions 35 6.2.12 Subscription and Notification . 36 6.2.12.1 General Concepts 36 6.

31、2.12.2 Detailed Descriptions 36 6.3 Security Aspects 36 6.4 Intra-M2M SP Communication 37 6.5 Inter-M2M SP Communication 37 6.5.1 Inter M2M SP Communication for oneM2M Compliant Nodes 37 6.5.1.1 Public Domain Names and CSEs . 38 6.5.2 Inter M2M SP Generic Procedures 38 6.5.2.1 Actions of the Origina

32、ting M2M Node in the Originating Domain 39 6.5.2.2 Actions of the Receiving CSE in the Originating Domain 39 6.5.2.3 Actions in the IN of the Target Domain . 39 6.5.3 DNS Provisioning for Inter-M2M SP Communication 39 6.5.3.1 Inter-M2M SP Communication Access Control Policies 39 6.5.4 Conditional In

33、ter-M2M Service Provider CSE Registration 39 6.6 M2M Service Subscription . 40 7 M2M Entities and Object Identification . 41 7.1 M2M Identifiers . 41 7.1.1 M2M Service Provider Identifier (M2M-SP-ID) . 41 7.1.2 Application Entity Identifier (AE-ID) . 41 7.1.3 Application Identifier (App-ID) 41 7.1.4

34、 CSE Identifier (CSE-ID) . 41 7.1.5 M2M Node Identifier (M2M-Node-ID) 41 7.1.6 M2M Service Subscription Identifier (M2M-Sub-ID) . 42 7.1.7 M2M Request Identifier (M2M-Request-ID) 42 7.1.8 M2M External Identifier (M2M-Ext-ID) . 43 7.1.9 Underlying Network Identifier (UNetwork-ID) . 43 7.1.10 Trigger

35、Recipient Identifier (Trigger-Recipient-ID) 43 7.1.11 M2M Service Identifier (M2M-Serv-ID). 43 7.1.12 Service Role identifier (SRole-ID) 44 7.1.13 M2M Service Profile Identifier (M2M-Service-Profile-ID) . 44 7.2 M2M-SP-ID, CSE-ID, App-ID and AE-ID and resource Identifier formats 44 7.3 M2M Identifie

36、rs lifecycle and characteristics . 50 8 Description and Flows of Reference Points 52 8.1 General Communication Flow Scheme on Mca and Mcc Reference Points 52 8.1.1 Description . 52 8.1.2 Request . 52 8.1.3 Response 59 8.2 Procedures for Accessing Resources 61 8.2.1 Accessing Resources in CSEs - Bloc

37、king Requests . 61 8.2.1.1 M2M Requests Routing Policies . 66 8.2.2 Accessing Resources in CSEs - Non-Blocking Requests . 66 8.2.2.1 Response with Acknowledgement and optional Reference to Request Context and Capturing Result of Requested Operation 66 8.2.2.2 Synchronous Case . 66 8.2.2.3 Asynchrono

38、us Case . 69 8.3 Description and Flows on Mcn Reference Point . 70 8.4 Device Triggering 70 8.4.1 Definition and scope . 70 8.4.2 General Procedure for Device Triggering 70 8.4.2.1 Triggering procedure for targeting ASN/MN-CSE 71 oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 5

39、of 321 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. 8.5 Location Request . 72 8.5.1 Definition and Scope 72 8.5.2 General Procedure for Location Request . 73 8.6 Connection Request . 74 8.7 Device Manageme

40、nt 74 9 Resource Management . 74 9.1 General Principles 74 9.2 Resources . 75 9.2.1 Normal Resources 75 9.2.2 Virtual Resources and Attributes 75 9.3 Resource Addressing 75 9.3.1 Generic Principles 75 9.3.2 Addressing an Application Entity . 76 9.3.2.1 Application Entity Addressing. 76 9.3.2.2 Appli

41、cation Entity Reachability . 76 9.3.2.2.1 CSE Point of Access (CSE-PoA) . 76 9.3.2.2.2 Locating Application Entities. 77 9.3.2.2.3 Usage of CSE-PoA by the M2M System 77 9.3.2.3 Notification Re-targeting . 78 9.3.2.3.1 Application Entity Point of Access (AE-PoA) 78 9.4 Resource Structure . 79 9.4.1 R

42、elationships between Resources 79 9.4.2 Link Relations 80 9.5 Resource Type Specification Conventions 80 9.5.1 Handling of Unsupported Resources/Attributes/Sub-resources within the M2M System . 83 9.6 Resource Types 83 9.6.1 Overview 83 9.6.1.1 Resource Type Summary 83 9.6.1.2 Resource Type Speciali

43、zations 86 9.6.1.3 Commonly Used Attributes . 87 9.6.1.3.1 Universal attributes 87 9.6.1.3.2 Common attributes 88 9.6.2 Resource Type accessControlPolicy . 89 9.6.2.1 accessControlOriginators . 91 9.6.2.2 accessControlContexts 92 9.6.2.3 accessControlOperations 92 9.6.3 Resource Type CSEBase. 92 9.6

44、.4 Resource Type remoteCSE . 95 9.6.5 Resource Type AE 99 9.6.6 Resource Type container 102 9.6.7 Resource Type contentInstance. 104 9.6.8 Resource Type subscription 106 9.6.9 Resource Type schedule . 110 9.6.10 Resource Type locationPolicy 111 9.6.11 Resource Type delivery 114 9.6.12 Resource Type

45、request 115 9.6.13 Resource Type group 118 9.6.14 Resource Type fanOutPoint 120 9.6.15 Resource Type mgmtObj. 120 9.6.16 Resource Type mgmtCmd . 123 9.6.17 Resource Type execInstance . 125 9.6.18 Resource Type node . 126 9.6.19 Resource Type m2mServiceSubscriptionProfile 130 9.6.20 Resource Type ser

46、viceSubscribedNode . 131 9.6.21 Resource Type pollingChannel . 133 9.6.22 Resource Type pollingChannelURI. 133 9.6.23 Resource Type statsConfig . 133 9.6.24 Resource Type eventConfig 134 9.6.25 Resource Type statsCollect . 137 9.6.26 Resource Announcement 138 9.6.26.1 Overview 138 oneM2M Partners Ty

47、pe 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 6 of 321 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. 9.6.26.2 Universal Attributes for Announced Resources . 141 9.6.26.3 Common Attributes for Announced

48、Resources 141 9.6.27 Resource Type latest. 141 9.6.28 Resource Type oldest 142 9.6.29 Resource Type serviceSubscribedAppRule 142 10 Information Flows 143 10.1 Basic Procedures 143 10.1.1 CREATE (C) 143 10.1.1.1 Non-registration related CREATE procedure 144 10.1.1.2 Registration related CREATE proced

49、ure . 146 10.1.1.2.1 CSE Registration procedure . 146 10.1.1.2.2 Application Entity Registration procedure . 148 10.1.2 RETRIEVE (R) 153 10.1.3 UPDATE (U) 154 10.1.4 DELETE (D) 155 10.1.4.1 Non-deregistration related DELETE procedure . 155 10.1.4.2 Deregistration related DELETE procedure 156 10.1.4.2.1 CSE Deregistration procedure 156 10.1.4.2.2 Application Entity Deregistration procedure 157 10.1.5 NOTIFY (N) . 157 10.2 Resource Type-Specific Procedures . 158 10.2.1 Resource Procedures 159 10.2.1.1 Create , aka Application Registration. 159 10.2.1.2 Retrieve 159 10.2.1.3 Upd