ETSI TR 118 524-2016 oneM2M 3GPP Release 13 Interworking (V2 0 0 oneM2M TR-0024 version 2 0 0)《onem2M(物联网协议联盟) 3GPP (第三代移动通信合作伙伴项目)发行版本13 互联(V2 0 0 oneM2M TR-0024 版本2 0 0)》.pdf

《ETSI TR 118 524-2016 oneM2M 3GPP Release 13 Interworking (V2 0 0 oneM2M TR-0024 version 2 0 0)《onem2M(物联网协议联盟) 3GPP (第三代移动通信合作伙伴项目)发行版本13 互联(V2 0 0 oneM2M TR-0024 版本2 0 0)》.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 118 524-2016 oneM2M 3GPP Release 13 Interworking (V2 0 0 oneM2M TR-0024 version 2 0 0)《onem2M(物联网协议联盟) 3GPP (第三代移动通信合作伙伴项目)发行版本13 互联(V2 0 0 oneM2M TR-0024 版本2 0 0)》.pdf（50页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 118 524 V2.0.0 (2016-09) oneM2M; 3GPP Release 13 Interworking (oneM2M TR-0024 version 2.0.0) TECHNICAL REPORT ETSI ETSI TR 118 524 V2.0.0 (2016-09) 2oneM2M TR-0024 version 2.0.0Reference DTR/oneM2M-000024 Keywords interworking, IoT, M2M ETSI 650 Route des Lucioles F-06921 Sophia Antipolis C

2、edex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 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

3、 may be made available in electronic versions and/or in print. The content of 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 i

4、n print, the only prevailing document is the print of the Portable Document Format (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

5、 of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx 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

6、reproduced or utilized in any form or by any means, electronic or mechanical, including 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 restr

7、iction extend to reproduction in all media. European Telecommunications Standards Institute 2016. 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

8、its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 118 524 V2.0.0 (2016-09) 3oneM2M TR-0024 version 2.0.0Contents Intellectual Property Rights 5g3Foreword . 5g31 Scope 6g32 References 6g32.1 Normative re

9、ferences . 6g32.2 Informative references 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.3 Abbreviations . 7g34 Conventions 7g35 Introduction to 3GPP Service Capability Exposure . 7g35.1 oneM2M Underlying Network related requirements 7g35.2 3GPP Release 13 MTC features . 8g35.3 3GPP arc

10、hitecture for Service Capability Exposure . 9g35.4 OMA API Program 10g35.4.1 Overview 10g35.4.2 OMA work to be considered by oneM2M for 3GPP IWK . 10g35.4.2.1 OMA Service Exposure Framework (ServiceExposure). 10g35.4.2.2 OMA Exposing Network Capabilities to M2M (ENCap-M) 10g36 Reference architecture

11、 10g37 Potential impact for interworking with oneM2M . 11g38 Potential solutions for interworking with oneM2M . 12g38.1 Interworking Architecture with a 3GPP underlying network . 12g38.1.1 Exclusive Support through 3GPP Reference Points . 12g38.1.2 Exclusive Support through OMA API 12g38.1.3 Hybrid

12、Mode . 13g38.2 Configuration of Device Triggering Recall/Replace 13g38.2.1 Description 13g38.2.2 3GPP Release-13 MTC procedure 14g38.2.3 3GPP Parameters 15g38.2.4 Solution(s). 15g38.2.4.1 Solution1 . 15g38.2.4.1.1 Proposed resource types and attributes 15g38.2.4.1.2 Proposed Flow(s) . 16g38.3 Config

13、uration of Traffic Patterns . 17g38.3.1 Description 17g38.3.2 3GPP Release-13 MTC Procedure 18g38.3.3 3GPP Parameters 19g38.3.4 Solution(s). 20g38.3.4.1 Solution1 . 20g38.3.4.1.1 Proposed resource types and attributes 20g38.3.4.1.2 Proposed Flow . 23g38.4 Configuration of Background Data Transfers .

14、 25g38.4.1 Description 25g38.4.2 3GPP Release-13 MTC procedure 26g38.4.3 3GPP Parameters 27g38.4.4 Solution(s). 28g38.4.4.1 Solution1 . 28g38.4.4.1.1 Proposed resource types and attributes 28g38.4.4.1.2 Proposed Flow(s) . 30g38.5 Support for Group Messaging 32g38.5.1 Description 32g3ETSI ETSI TR 118

15、 524 V2.0.0 (2016-09) 4oneM2M TR-0024 version 2.0.08.5.2 3GPP Release-13 MTC procedure 32g38.5.3 3GPP Parameters 36g38.5.4 Solution(s). 37g38.5.4.1 Solution1 . 37g38.5.4.1.1 Overview . 37g38.5.4.1.2 Proposed resource types and attributes 37g38.5.4.1.3 Proposed Flow(s) . 39g38.6 Support for Network s

16、tatus report 41g38.6.1 Description 41g38.6.2 3GPP Release-13 MTC procedure 42g38.6.2.1 Request procedure for one-time or continuous reporting of network status 42g38.6.2.2 Report procedure for continuous reporting of network status . 43g38.6.2.3 Removal procedure for continuous reporting of network

17、status . 44g38.6.3 3GPP Parameters 45g38.6.4 Solution(s). 45g38.6.4.1 Solution1 . 45g38.6.4.1.1 Proposed resource types and attributes 45g38.6.4.1.2 Proposed Flow(s) . 47g3History 50g3ETSI ETSI TR 118 524 V2.0.0 (2016-09) 5oneM2M TR-0024 version 2.0.0Intellectual Property Rights IPRs essential or po

18、tentially 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 Property Rights (IPRs); Essential, or potentially Essenti

19、al, 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 (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can

20、 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 Report (TR) has been produced by ETSI Partnership Project oneM2M (oneM2M). ETSI ETSI T

21、R 118 524 V2.0.0 (2016-09) 6oneM2M TR-0024 version 2.0.01 Scope The present document is a study of interworking between oneM2M Architecture and 3GPP Rel-13 architecture for Service Capability Exposure as defined in the release 13 version of ETSI TS 123 682 i.5. The key objective and value is analyze

22、d and described. The document also investigates the potential solution in oneM2M by evaluating the existing technical solutions. 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 speci

23、fic references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https:/docbox.etsi.org/Reference

24、/. 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 present document. Not applicable. 2.2 Informative references References are either

25、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 referenced document (including any amendments) applies. NOTE: While any hyperlinks inc

26、luded in this clause 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. N

27、OTE: Available at http:/www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf. i.2 ETSI TS 118 102: “oneM2M; Requirements (oneM2M TS-0002)“. i.3 ETSI TS 122 101: “Service aspects; Service principles (3GPP TS 22.101 Release 13)“. i.4 ETSI TS 122 115: “Service aspects; Charging and billing (3GPP TS 22

28、.115 Release 13)“. i.5 ETSI TS 123 682: “Architecture enhancements to facilitate communications with packet data networks and applications (3GPP TS 23.682 Release 13)“. i.6 OMA API Inventory. NOTE: Available at http:/technical.openmobilealliance.org/Technical/technical-information/oma-api-program. i

29、.7 OMA Service Exposure Framework. NOTE: Available at http:/member.openmobilealliance.org/ftp/Public_documents/ARCH/ServiceExposure. i.8 OMA Exposing Network Capabilities to M2M. NOTE: Available at http:/member.openmobilealliance.org/ftp/Public_documents/ARCH/ENCap-M2M. ETSI ETSI TR 118 524 V2.0.0 (

30、2016-09) 7oneM2M TR-0024 version 2.0.0i.9 ETSI TS 118 101: “oneM2M; Functional Architecture (oneM2M TS-0001)“. i.10 ETSI TS 129 336: “Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications (3GPP TS 29.336 Release 13)“. i.11 ETSI TS 123 203: “Poli

31、cy and charging control architecture (3GPP TS 23.203 Release 13)“. i.12 ETSI TS 122 368: “Service requirements for Machine-Type Communications (MTC); Stage 1 (3GPP TS 22.368)“. i.13 ETSI TS 126 346: “Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs (3GPP TS 26.346)“. i.14 ETSI TS

32、123 468: “Group Communication System Enablers for LTE (GCSE_LTE); Stage 2 (3GPP TS 23.468)“. i.15 ETSI TS 123 246: “Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description (3GPP TS 23.246)“. i.16 ETSI TS 118 111: “oneM2M; Common Terminology (oneM2M TS-0011)“. 3 Definit

33、ions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI TS 118 111 i.16 apply. 3.3 Abbreviations For the purposes of the present document, the abbreviations given in ETSI TS 118 111 i.16 apply. 4 Conventions The keywords “Shall“, “Shal

34、l not“, “May“, “Need not“, “Should“, “Should not“ in the present document are to be interpreted as described in the oneM2M Drafting Rules i.1. 5 Introduction to 3GPP Service Capability Exposure 5.1 oneM2M Underlying Network related requirements Following requirements are defined in ETSI TS 118 102 i

35、.2, but not implemented or partially implemented in release 1. Most of these requirements except OSR-052 can be achieved through the 3GPP features addressed in the subsequent sections, with and without support by OMA API. OSR-006: The oneM2M System should be able to reuse the services offered by Und

36、erlying 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. ETSI ETSI TR 118 524 V2.0.0 (2016-09) 8oneM2M TR-0024 version 2.0.0 Charging and billing se

37、rvices, including sponsoring data flows. Device information and profiles, including configuring expected communication patterns. Configuration and management of devices. Triggering, monitoring of devices. Small data transmission. Group management and group messaging. Configuring QoS. Receiving Repor

38、ts about the condition of the uderlying network. Partially implemented in Rel-1 (see note 1). NOTE 1: Rel-1 covers: Location, Charging and billing services, Configuration and management of devices, Device information and profiles, Triggering. OSR-045a: The oneM2M System should be able to receive and

39、 utilize information provided by the Underlying Network about when an M2M Device can be reached. Not implemented in Rel-1. OSR-051: Depending on availability of suitable interfaces provided by the Underlying Network the oneM2M System should be able to request the Underlying Network to broadcast / mu

40、lticast data to a group of M2M Devices in a specified area. Implemented in Rel-1 - Not implemented in Rel-1. ? OSR-052: The oneM2M System should be able to select an appropriate Underlying Network to broadcast or multicast data depending on the networks broadcast/multicast support and the connectivi

41、ty supported by the targeted group of M2M Devices/Gateways. Not implemented in Rel-1. OPR-004: When suitable interfaces are provided by the Underlying Network, the oneM2M System should have the ability to schedule traffic via the Underlying Network based on instructions received from the Underlying

42、Network. Not implemented in Rel-1. OPR-005: The oneM2M System should be able to exchange information with M2M Applications related to usage and traffic characteristics of M2M Devices or M2M Gateways by the M2M Application. This should include support for the 3GPP feature called: “Time controlled“ (s

43、ee note 2). Not implemented in Rel-1. NOTE 2: “Time controlled“ is equivalent to the MTC Features specified in clause 7.2 of ETSI TS 122 368 i.12. OPR-006: Depending on availability of suitable interfaces provided by the Underlying Network the oneM2M System should be able to provide information rela

44、ted to usage and traffic characteristics of M2M Devices or M2M Gateways to the Underlying Network. Not implemented in Rel-1. 5.2 3GPP Release 13 MTC features In 3GPP Release 13, requirements for “Service exposure with 3rd party service providers“ features are specified in clause 29 of ETSI TS 122 10

45、1 i.3 and the “Charged party selection“ feature is defined in sub-clause 5.1.3 of ETSI TS 122 115 i.4. 3GPP Release 13 architecture supports these features and they can be used to implement the oneM2M requirements as described in the previous clause. ETSI ETSI TR 118 524 V2.0.0 (2016-09) 9oneM2M TR-

46、0024 version 2.0.0These 3GPP features are not only intended for M2M communication, but also for human usable applications such as smartphone applications. 3GPP intends to expose these additional features through the 3GPP Service Capability Exposure Function (SCEF) as described in the following claus

47、e. 5.3 3GPP architecture for Service Capability Exposure The 3GPP architecture for the Service Capability Exposure Function (SCEF) is defined in ETSI TS 123 682 i.5. The specification includes two different architectures. One is for the “MTC Device triggering“ feature and was specified in 3GPP relea

48、se 11. The other one is for 3GPP Service exposure with 3rdparty service providers features newly provided in Release 13 which is the focus of the present document. Refer to the following figure 5.3-1, taken from the release 13 version of ETSI TS 123 682 i.5. g44g94g94 g87g18g90g38 g68g68g28g876g3g94

49、g39g94g69 g68g100g18g882g47g116g38 g94g882g18g94g18g38 g69g286g410g449g381g396g364g3g28g374g410g349g410g455 g94g1010g410 g90g454g853g3g69g410 g100g1010g258g876g3g100g1010g271 g100g400g393 g47g94g18 . g3g3g3g3g1007g39g87g87g3g349g374g410g286g396g296g258g272g286 g1007g39g87g87 g100g90g104g94g100g3g24g75g68g4g47g69 g94g286g396g448g349g272g286g3g18g258g393g258g271g349g367g349g410g455g3g28g454g393g381g400g437g396g286g3g38g437g374g272g410g349g381g374 g4g87g47g3g1005 g4g87g47g3g1006 g4g87g47