ETSI GS MEC 012-2017 Mobile Edge Computing (MEC) Radio Network Information API (V1 1 1).pdf

1、 ETSI GS MEC 012 V1.1.1 (2017-07) Mobile Edge Computing (MEC); Radio Network Information API Disclaimer The present document has been produced and approved by the Mobile Edge Computing (MEC) ETSI Industry Specification Group (ISG) and represents the views of those members who participated in this IS

2、G. It does not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS MEC 012 V1.1.1 (2017-07) 2 Reference DGS/MEC-0012RnisApi Keywords API, MEC, RNIS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65

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

4、n 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 in print, the only prevailing document is the print of

5、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 of this and other ETSI documents is available at http

6、s:/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 reproduced or utilized in any form or by any means, el

7、ectronic 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 restriction extend to reproduction in all media. ETSI 2017.

8、 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 its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of

9、its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI GS MEC 012 V1.1.1 (2017-07) 3 Contents Intellectual Property Rights 6g3Foreword . 6g3Modal verbs terminology 6g31 Scope 7g32 References 7g32.1 Normative references . 7g32.2 Informative references

10、7g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 Overview 9g35 Description of the service (informative). 9g35.1 RNIS service introduction 9g35.2 Sequence diagrams . 10g35.2.1 Introduction. 10g35.2.2 Sending a request for RAB information . 10g35.2.3 Sending a reques

11、t for PLMN information . 11g35.2.4 Sending a request for S1 bearer information 11g35.2.5 REST based subscribe-notify model . 12g35.2.5.1 Subscribing to RNI event notifications . 12g35.2.5.2 Receiving notification on expiry of RNI event subscription . 12g35.2.5.3 Updating subscription for RNI event n

12、otifications . 13g35.2.5.4 Unsubscribing from RNI event notifications 14g35.2.6 Receiving RNI event notifications about cell changes 14g35.2.7 Receiving RNI event notifications about Radio Access Bearer establishment . 15g35.2.8 Receiving RNI event notifications about Radio Access Bearer modificatio

13、n 16g35.2.9 Receiving RNI event notifications about Radio Access Bearer release 17g35.2.10 Receiving RNI event notifications about UE measurement reports 18g35.2.11 Receiving RNI event notifications about UE timing advance 19g35.2.12 Receiving RNI event notifications about carrier aggregation reconf

14、iguration . 19g35.2.13 Receiving RNI event notifications about S1 bearer 20g36 Data model . 21g36.1 Introduction 21g36.2 Resource data types 21g36.2.1 Introduction. 21g36.2.2 Type: PlmnInfo . 21g36.2.3 Type: RabInfo . 21g36.2.4 Type: S1BearerInfo. 22g36.3 Subscription data types . 23g36.3.1 Introduc

15、tion. 23g36.3.2 Type: CellChangeSubscription . 23g36.3.3 Type: RabEstSubscription 24g36.3.4 Type: RabModSubscription 25g36.3.5 Type: RabRelSubscription 25g36.3.6 Type: MeasRepUeSubscription 26g36.3.7 Type: MeasTaSubscription . 27g36.3.8 Type: CaReconfSubscription 27g36.3.9 Type: S1BearerSubscription

16、 . 28g36.3.10 Type: SubscriptionLinkList 28g36.4 Notification data types 29g36.4.1 Introduction. 29g36.4.2 Type: CellChangeNotification 29g36.4.3 Type: RabEstNotification . 29g3ETSI ETSI GS MEC 012 V1.1.1 (2017-07) 4 6.4.4 Type: RabModNotification . 30g36.4.5 Type: RabRelNotification . 31g36.4.6 Typ

17、e: MeasRepUeNotification . 31g36.4.7 Type: MeasTaNotification 33g36.4.8 Type: CaReConfNotification 33g36.4.9 Type: ExpiryNotification 34g36.4.10 Type: S1BearerNotification 34g36.5 Referenced structured data types 35g36.5.1 Introduction. 35g36.5.2 Type: LinkType 35g36.5.3 Type: TimeStamp . 35g36.5.4

18、Type: AssociateId . 36g36.6 Referenced simple data types and enumerations 36g37 API definition . 36g37.1 Introduction 36g37.2 Global definitions and resource structure . 36g37.3 Resource: rab_info . 37g37.3.1 Description 37g37.3.2 Resource definition . 38g37.3.3 Resource methods . 38g37.3.3.1 GET .

19、38g37.3.3.2 PUT . 39g37.3.3.3 PATCH . 39g37.3.3.4 POST . 39g37.3.3.5 DELETE . 39g37.4 Resource: plmn_info 40g37.4.1 Description 40g37.4.2 Resource definition . 40g37.4.3 Resource methods . 40g37.4.3.1 GET . 40g37.4.3.2 PUT . 41g37.4.3.3 PATCH . 41g37.4.3.4 POST . 41g37.4.3.5 DELETE . 41g37.5 Resourc

20、e: s1_bearer_info . 42g37.5.1 Description 42g37.5.2 Resource definition . 42g37.5.3 Resource methods . 42g37.5.3.1 GET . 42g37.5.3.2 PUT . 43g37.5.3.3 PATCH . 43g37.5.3.4 POST . 43g37.5.3.5 DELETE . 43g37.6 Resource: subscriptions 44g37.6.1 Description 44g37.6.2 Resource definition . 44g37.6.3 Resou

21、rce methods . 44g37.6.3.1 GET . 44g37.6.3.2 PUT . 45g37.6.3.3 PATCH . 45g37.6.3.4 POST . 45g37.6.3.5 DELETE . 45g37.7 Resource: subscriptions/subscriptionType . 46g37.7.1 Description 46g37.7.2 Resource definition . 46g37.7.3 Resource methods . 46g37.7.3.1 GET . 46g37.7.3.2 PUT . 47g37.7.3.3 PATCH .

22、47g37.7.3.4 POST . 47g37.7.3.5 DELETE . 49g3ETSI ETSI GS MEC 012 V1.1.1 (2017-07) 5 7.8 Resource: existing subscription 49g37.8.1 Description 49g37.8.2 Resource definition . 49g37.8.3 Resource methods . 49g37.8.3.1 GET . 49g37.8.3.2 PUT . 50g37.8.3.3 PATCH . 52g37.8.3.4 POST . 52g37.8.3.5 DELETE . 5

23、2g3Annex A (informative): Mapping of permissions for RESTful API and topic based alternative transport . 54g3A.1 Overview 54g3A.2 Mapping of permissions - RESTful and topic based alternative transport . 54g3Annex B (informative): Complementary material for API utilisation 56g3History 57g3ETSI ETSI G

24、S MEC 012 V1.1.1 (2017-07) 6 Intellectual Property Rights IPRs essential or potentially 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 00

25、0 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, 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 investi

26、gation, including IPR searches, has been carried out by ETSI. No guarantee can 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 Group Specificatio

27、n (GS) has been produced by ETSI Industry Specification Group (ISG) Mobile Edge Computing (MEC). Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of

28、 the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI GS MEC 012 V1.1.1 (2017-07) 7 1 Scope The present document focuses on the Radio Network Information mobile edge service.

29、 It describes the message flows and the required information. The present document also specifies the RESTful API with the data model. 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

30、 specific 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/Ref

31、erence. 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. 1 ETSI GS MEC 001: “Mobile Edge Computing (MEC) Terminology“

32、. 2 IETF RFC 6749: “The OAuth 2.0 Authorization Framework“. NOTE: Available at https:/tools.ietf.org/html/rfc6749. 3 IETF RFC 6750: “The OAuth 2.0 Authorization Framework: Bearer Token Usage“. NOTE: Available at https:/tools.ietf.org/html/rfc6750. 4 IETF RFC 5246: “The Transport Layer Security (TLS)

33、 Protocol Version 1.2“. NOTE: Available at https:/tools.ietf.org/html/rfc5246. 5 IETF RFC 2818: “HTTP Over TLS“. NOTE: Available at https:/tools.ietf.org/html/rfc2818. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number

34、) 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 included in this clause were valid at the time of publication, ETSI cannot guarantee t

35、heir 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 ETSI GS MEC 002: “Mobile Edge Computing (MEC); Technical Requirements“. i.2 ETSI GS MEC 003: “Mobile Edge C

36、omputing (MEC) Framework and reference architecture“. i.3 ETSI TS 136 413:“LTE; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (3GPP TS 36 413)“. i.4 ETSI TS 123 401: “LTE; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestria

37、l Radio Access Network (E-UTRAN) access (3GPP TS 23.401)“. ETSI ETSI GS MEC 012 V1.1.1 (2017-07) 8 i.5 ETSI TS 136 214: “LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements (3GPP TS 36 214)“. i.6 ETSI GS MEC 011: “Mobile Edge Computing (MEC) Mobile Edge Platform Ap

38、plication Enablement“. i.7 ETSI TS 136 331:“LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (3GPP TS 36.331)“. i.8 ETSI GS MEC 009: “Mobile Edge Computing (MEC) General principles for Mobile Edge Service APIs“. i.9 OpenAPI Specification.

39、 NOTE 1: Available at https:/ NOTE 2: OpenAPI Specification version 2.0 is recommended as it is the official release at the time of publication. i.10 Protocol Buffers Language Specification. NOTE 1: Available at https:/ NOTE 2: Protocol Buffers Version 3 Language Specification is recommended as it i

40、s the official release at the time of publication. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI GS MEC 001 1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI GS MEC

41、001 1 and the following apply: 3GPP 3rdGeneration Partnership Project API Application Programming Interface ECGI E-UTRAN Cell Global Identifier E-RAB E-UTRAN Radio Access Bearer E-UTRAN Evolved Universal Terrestrial Radio Access Network GTP GPRS Tunnelling Protocol GTP-U GPRS Tunneling Protocol-User

42、 plane GW Gateway HTTP Hypertext Transfer Protocol HTTPS HTTP over TLS IE Information ElementIP Internet Protocol JSON Javascript Object Notation MCC Mobile Country Code MMEC MME Code MNC Mobile Network Code OAI Open API InitiativePLMN Public Land Mobile Network QCI Quality Class Indicator QoS Quali

43、ty of Service RAB Radio Access Bearer REST Representational State Transfer RFC Request For Comments RNI Radio Network Information RNIS Radio Network Information Service ETSI ETSI GS MEC 012 V1.1.1 (2017-07) 9 RSRP Reference Signal Received Power RSRQ Reference Signal Received Quality SGW Serving Gat

44、eway TEID Tunnel End Point Identifier TLS Transport Layer Security TMSI Temporary Mobile Subscriber Entity UE User Equipment URI Uniform Resource Indicator UTC Coordinated Universal Time 4 Overview The present document specifies the Radio Network Information API to support the requirements defined f

45、or Mobile Edge Computing in ETSI GS MEC 002 i.1. Clause 5 introduces how Radio Network Information Service (RNIS) may be used by the mobile edge applications and by the mobile edge platform. It describes the information flows used for RNI. The information that can be exchanged over the RNI API is de

46、scribed in clause 6 which provides detailed description on all information elements that are used for RNI. Clause 7 describes the actual RNI API providing detailed information how information elements are mapped into a RESTful API design. 5 Description of the service (informative) 5.1 RNIS service i

47、ntroduction Mobile Edge Computing allows running the mobile edge applications at the edge of the network where the environment is characterized by low latency, proximity, high bandwidth and exposure to location and up-to-date radio network information. The information on current radio conditions are

48、 shared via the mobile edge platform over Radio Network Information Service. Radio Network Information Service (RNIS) is a service that provides radio network related information to mobile edge applications and to mobile edge platforms. The Radio Network Information Service is available for authoriz

49、ed mobile edge applications and is discovered over the Mp1 reference point i.2. The granularity of the radio network information may be adjusted based on parameters such as information per cell, per User Equipment, per QCI class or it may be requested over period of time. Typical information that may be provided is listed as follows: up-to-date radio network information regarding radio network conditions; measurement information related to the user pl