ITU-T Y 4500 14-2018 oneM2M C LwM2M interworking (Study Group 20).pdf

1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T Y.4500.14 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2018) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Internet of things an

2、d smart cities and communities Frameworks, architectures and protocols oneM2M LwM2M interworking Recommendation ITU-T Y.4500.14 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES GLOBAL INFORMATIO

3、N INFRASTRUCTURE General Y.100Y.199 Services, applications and middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces and protocols Y.400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTERNET PR

4、OTOCOL ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.1199 Architecture, access, network capabilities and resource management Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation, admin

5、istration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION NETWORKS Frameworks and functional architecture models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.2249 Serv

6、ice aspects: Interoperability of services and networks in NGN Y.2250Y.2299 Enhancements to NGN Y.2300Y.2399 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Packet-based Networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grad

7、e open environment Y.2900Y.2999 FUTURE NETWORKS Y.3000Y.3499 CLOUD COMPUTING Y.3500Y.3999 INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES General Y.4000Y.4049 Definitions and terminologies Y.4050Y.4099 Requirements and use cases Y.4100Y.4249 Infrastructure, connectivity and networks Y.4250Y.4399

8、 Frameworks, architectures and protocols Y.4400Y.4549 Services, applications, computation and data processing Y.4550Y.4699 Management, control and performance Y.4700Y.4799 Identification and security Y.4800Y.4899 Evaluation and assessment Y.4900Y.4999 For further details, please refer to the list of

9、 ITU-T Recommendations. Rec. ITU-T Y.4500.14 (03/2018) i Recommendation ITU-T Y.4500.14 oneM2M LwM2M interworking Summary Recommendation ITU-T Y.4500.14 specifies the interworking capabilities of the machine to machine (M2M) service layer between application service node/infrastructure node/middle n

10、ode (ASN/IN/MN) common services entities (CSEs) and lightweight machine to machine (LWM2M) endpoints. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.4500.14 2018-03-01 20 11.1002/1000/13509 Keywords Interworking, LwM2M, oneM2M. * To access the Recommendation, type the URL

11、 http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Y.4500.14 (03/2018) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in

12、the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to sta

13、ndardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is

14、covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to i

15、ndicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is ach

16、ieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUA

17、L PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether a

18、sserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are caution

19、ed that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. NOTE This Recommendation departs slightly from the usual editorial style of ITU-T Recommendations to preserve existing cross-referencing from ext

20、ernal documents. ITU 2018 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.4500.14 (03/2018) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2

21、 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 Architecture model . 3 6.1 Introduction 3 6.2 Reference model . 3 6.3 Types of interworking 4 6.4 Composition of the interworking proxy entity . 5 7 Architecture aspects 6 7.1 Introduction 6 7.2 LWM2M device a

22、nd endpoint lifecycle . 6 7.3 LWM2M object discovery . 8 7.4 LWM2M object transport and interworking 11 7.5 LWM2M object subscription and notification . 16 7.6 LWM2M object security 18 7.7 LWM2M IPE administration and maintenance 19 7.8 LWM2M client provisioning (Bootstrap) 20 8 Transparent interwor

23、king function . 20 8.1 Introduction 20 8.2 Attribute mapping for the resources 21 9 Semantically enabled interworking function (Informative) . 21 9.1 Introduction 21 9.2 Organization of semantically enabled content sharing resources . 21 9.3 Guidelines for mapping to the base ontology . 23 Annex A o

24、neM2M specification update and maintenance control procedure 25 Appendix I Introduction to OMA LightweightM2M (LWM2M) . 26 I.1 Introduction 26 I.2 Architecture 27 I.3 Terminology . 27 I.4 Reference points . 28 I.5 Protocols . 29 I.6 Functions 33 Bibliography. 34 Rec. ITU-T Y.4500.14 (03/2018) 1 Reco

25、mmendation ITU-T Y.4500.14 oneM2M LwM2M interworking 1 Scope This Recommendation specifies the interworking capabilities of the machine to machine (M2M) service layer between application service node/infrastructure node/middle node (ASN/IN/MN) common services entities (CSEs) and lightweight machine

26、to machine (LWM2M) endpoints using the architecture identified in Annex VI of oneM2M TS-0001 ITU-T Y.4500.1 for the following interworking scenarios: Interworking for transparent transport of encoded LWM2M objects and commands in content sharing resources between LWM2M endpoints and M2M applications

27、. Interworking with full mapping of LWM2M objects in LWM2M endpoints to semantically enabled content sharing resources that are utilized by M2M applications. NOTE The present Recommendation limits content sharing resources to and resources. The Recommendation contains oneM2M Release 2 specification

28、oneM2M LWM2M Interworking V2.0.0 and is equivalent to standards of oneM2M partners including ARIB, ATIS b-ATIS.oneM2M.TS0014, CCSA b-CCSA M2M-TS-0014, ETSI b-ETSI TS 118 114, TIA, TSDSI b-TSDSI STD T1.oneM2M TS-0014, TTA b-TTAT.MM-TS.0014 and TTC b-TTC TS-M2M-0014. 2 References The following ITU-T R

29、ecommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation ar

30、e therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as

31、a stand-alone document, the status of a Recommendation. ITU-T Y.4500.1 Recommendation ITU-T Y.4500.1 (2018), one M2M - Functional architecture. ITU-T Y.4500.11 Recommendation ITU-T Y.4500.11 (2018), one M2M - Common terminology. ETSI TS 118 103 ETSI TS 118 103 (2016), one M2M; Security solutions (on

32、eM2M TS-0003 version 2.4.1 Release 2). OMA TS LwM2M OMA-TS-LightweightM2M-V1-0-20150318-D, Lightweight Machine to Machine Technical Specification, March 2015, Open Mobile Alliance. 3 Definitions For the purposes of the present Recommendation, the terms and definitions given in oneM2M TS-0011 ITU-T Y

33、.4500.11 and oneM2M TS-0001 ITU-T Y.4500.1 apply. 3.1 Terms defined elsewhere This Recommendation uses the following term(s) defined elsewhere: 2 Rec. ITU-T Y.4500.14 (03/2018) 3.1.1 application entity ITU-T Y.4500.11: Represents an instantiation of application logic for end-to-end M2M solutions. 3.

34、1.2 common services entity (CSE) ITU-T Y.4500.11: Represents an instantiation of a set of common service functions of the M2M environments. Such service functions are exposed to other entities through reference points. 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms For t

35、he purposes of the present Recommendation, the abbreviations given in oneM2M TS-0011 ITU-T Y.4500.11 and the following apply: AE Application Entity ASN Application Service Node CoAP Constrained Application Protocol CSE Common Services Entity DTLS Datagram, Transport Layer Security IPE Interworking P

36、roxy application Entity IN Infrastructure Node JSON JavaScript Object Notation LWM2M Lightweight Machine to Machine M2M Machine to Machine MCU Multipoint Control Unit MN Middle Node OMA Open Mobile Alliance RAM Random Access Memory SMS Short Message Service UDP User Datagram Protocol 5 Conventions T

37、he keywords “shall“, “shall not“, “should“, “should not“, “may“, “need not“ in the present Recommendation are to be interpreted as described: Shall/Shall not: Requirements 1) Effect on Standard: Standard needs to describe the required feature (i.e., specify a technical solution for the Requirement);

38、 2) Effect on products: every implementation (M2M Solution that complies to this Standard) must support it; 3) Effect on deployments: every deployment (M2M Service based on this Standard) must use the Standardized feature where applicable otherwise e.g., interoperability problems with other services

39、 could arise. Rec. ITU-T Y.4500.14 (03/2018) 3 Should/Should not: Recommendation 1) Effect on Standard: Standard needs to describe a solution that allows the presence and the absence of the feature; 2) Effect on products: an implementation may or may not support it, however support is recommended; 3

40、) Effect on deployments: a deployment may or may not use it, however usage is recommended. May/Need not: Permission/Option 1) Effect on Standard: Standard needs to describe a solution that allows the presence and the absence of the required feature; 2) Effect on products: an implementation may or ma

41、y not support it; 3) Effect on deployments: A deployment may or may not use it. 6 Architecture model 6.1 Introduction The architecture model followed in the present Recommendation is based on the architecture model in Annex VI of oneM2M TS-0001 ITU-T Y.4500.1 that describes how interworking between

42、CSEs and non-oneM2M solutions and protocol using specialized interworking proxy application entities (IPEs). The present Recommendation describes the LWM2M IPE that supports the interworking scenarios depicted in Figure 6.1-1. Figure 6.1-1 LWM2M interworking scenarios In the scenarios depicted in Fi

43、gure 6.1-1, the hybrid and LWM2M applications represent applications that implement the LWM2M client role defined in the LWM2M protocol OMA TS LwM2M. 6.2 Reference model The LWM2M interworking reference model, shown in Figure 6.2-1, utilizes the functional architectures reference model in oneM2M TS-

44、0001 ITU-T Y.4500.1; augmenting the oneM2M TS-0001 ITU-T Y.4500.1 reference model with capabilities provided by the LWM2M IPE. 4 Rec. ITU-T Y.4500.14 (03/2018) NOTE The application entity (AE) in the reference model could be registered with the same CSE as the LWM2M IPE. Figure 6.2-1 LWM2M reference

45、 model 6.3 Types of interworking LWM2M IPEs provide the following types of interworking: 1) Interworking using the content sharing resource for transparent transport of encoded LWM2M objects that are available to application entities (AEs) as depicted in Figure 6.3-1. 2) Interworking with full mappi

46、ng of the semantics of LWM2M objects to semantically enabled resources that are available to AEs as depicted in Figure 6.3-2. 3) While depicted outside the hosting CSE, the content sharing resources are hosted in a CSE (e.g., CSE1). Figure 6.3-1 LWM2M transparent interworking function In Figure 6.3-

47、1, the LWM2M objects are provided by the LWM2M application to the LWM2M IPE using the LWM2M protocol. The LWM2M IPE then encapsulates the LWM2M objectsLWM2M objects in content sharing resources and then hosts the content sharing resources in a CSE using the Mca reference points for use by AEs. The A

48、E accesses the content sharing resource from the CSE that hosts the resource using the Mca reference point. Once the AE receives the content sharing resource, the AE extracts the LWM2M object from the content sharing resource for the AEs purpose. Clause 7 describes this type of interworking in great

49、er detail. Rec. ITU-T Y.4500.14 (03/2018) 5 Figure 6.3-2 LWM2M semantically enabled interworking function In Figure 6.3-2, the LWM2M objects are provided by the LWM2M Application to the LWM2M IPE using the LWM2M Protocol. The LWM2M IPE then interworks the LWM2M objects into content sharing resources. The content sharing resources are based on the oneM2M defined Semantic Ontology. The LWM2M IPE hosts the content sharing resource in a CSE across the Mca re