1、 ETSI GS MEC 016 V1.1.1 (2017-09) Mobile Edge Computing (MEC); UE application interface 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 ISG. It
2、 does not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS MEC 016 V1.1.1 (2017-09) 2 Reference DGS/MEC-0016UEappInterface Keywords API, MEC ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47
3、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 in pr
4、int. 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 the
5、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 https:/p
6、ortal.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, electr
7、onic 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. All
8、 rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Me
9、mbers. GSM and the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI GS MEC 016 V1.1.1 (2017-09) 3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 7g33 D
10、efinitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Overview 7g35 Description of the service (informative). 8g35.1 Sequence diagrams . 8g35.1.1 Introduction. 8g35.1.2 User application look-up . 8g35.1.3 Application context create 8g35.1.4 Application context delete 9g35.1.5
11、 Application context update . 9g35.1.6 Receiving notification events 10g36 Data model . 10g36.1 Introduction 10g36.2 Resource data types 11g36.2.1 Introduction. 11g36.2.2 Type: ApplicationList . 11g36.2.3 Type: AppContext 12g36.3 Subscription data types . 12g36.4 Notification data types 13g36.4.1 In
12、troduction. 13g36.4.2 Type: NotificationEvent . 13g36.5 Referenced structured data types 13g37 API definition . 13g37.1 Introduction 13g37.2 Global definitions and resource structure . 13g37.3 Resource: meAppList . 14g37.3.1 Description 14g37.3.2 Resource definition . 14g37.3.3 Resource Methods 14g3
13、7.3.3.1 GET . 14g37.3.3.2 PUT . 15g37.3.3.3 PATCH . 15g37.3.3.4 POST . 15g37.3.3.5 DELETE . 15g37.4 Resource: all ueAppContexts . 16g37.4.1 Description 16g37.4.2 Resource definition . 16g37.4.3 Resource Methods 16g37.4.3.1 GET . 16g37.4.3.2 PUT . 16g37.4.3.3 PATCH . 16g37.4.3.4 POST . 16g37.4.3.5 DE
14、LETE . 17g37.5 Resource: individual ueAppContext . 17g3ETSI ETSI GS MEC 016 V1.1.1 (2017-09) 4 7.5.1 Description 17g37.5.2 Resource definition . 17g37.5.3 Resource Methods 17g37.5.3.1 GET . 17g37.5.3.2 PUT . 18g37.5.3.3 PATCH . 18g37.5.3.4 POST . 18g37.5.3.5 DELETE . 18g38 Authentication, authorizat
15、ion and access control . 19g3Annex A (informative): Complementary material for API utilization 20g3History 21g3ETSI ETSI GS MEC 016 V1.1.1 (2017-09) 5 Intellectual Property Rights Essential patents IPRs essential or potentially essential to the present document may have been declared to ETSI. The in
16、formation 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 Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from t
17、he 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 be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or
18、the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indica
19、ted as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Group Spec
20、ification (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 claus
21、e 3.2 of 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 016 V1.1.1 (2017-09) 6 1 Scope The present document contains the specification for the lifecycle manageme
22、nt of the user applications over the UE application interface. This interface is over the Mx2 reference point between the UE application in the UE and the user application lifecycle management proxy in the mobile edge system. The present document covers the following lifecycle management operations:
23、 user application look-up, request for the user application instantiation, and the request for the user application termination. In addition, a mechanism is specified for the exchange of lifecycle management related information between the mobile edge system and the UE application. The intended key
24、audience of the present document are the application developers for the mobile edge system. NOTE: User application mobility related lifecycle management operations are not covered by the present document. 2 References 2.1 Normative references References are either specific (identified by date of pub
25、lication 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. Referenced documents which are not found to be publicly available
26、 in the expected location might be found at https:/docbox.etsi.org/Reference/. 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
27、 document. 1 ETSI GS MEC 010-2: “Mobile Edge Computing (MEC); Mobile Edge Management; Part 2: Application lifecycle, rules and requirements management“. 2 IETF RFC 2818: “HTTP Over TLS“. NOTE: Available at https:/tools.ietf.org/html/rfc2818. 3 IETF RFC 5246: “The Transport Layer Security (TLS) Proto
28、col Version 1.2“. NOTE: Available at https:/tools.ietf.org/html/rfc5246. 4 ETSI GS MEC 009: “Mobile Edge Computing (MEC); General principles for Mobile Edge Service APIs“. 5 IETF RFC 6749: “The OAuth 2.0 Authorization Framework“. NOTE: Available at https:/tools.ietf.org/html/rfc6749. 6 IETF RFC 6750
29、: “The OAuth 2.0 Authorization Framework: Bearer Token Usage“. NOTE: Available at https:/tools.ietf.org/html/rfc6750. ETSI ETSI GS MEC 016 V1.1.1 (2017-09) 7 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-s
30、pecific. 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 their long
31、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 001: “Mobile Edge Computing (MEC); Terminology“. i.2 ETSI GS MEC 002: “Mobile Edge Computing (MEC); Techn
32、ical Requirements“. i.3 OpenAPI Specification. 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. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and defin
33、itions given in ETSI GS MEC 001 i.1 and the following apply: user application lifecycle management proxy: system level functional element that allows specific and authorized requests from the UE application for the user application lifecycle management 3.2 Abbreviations For the purposes of the prese
34、nt document, the abbreviations given in ETSI GS MEC 001 i.1 apply. 4 Overview The present document specifies the API for the UE application interface to support the corresponding requirements defined for the Mobile Edge Computing in ETSI GS MEC 002 i.2. Clause 5 describes how the UE application inte
35、rface can be used by the UE application and by the mobile edge system. It describes the information flows for the procedures over the UE application interface. The information that is exchanged over the UE application interface is described in clause 6, providing detailed description of all informat
36、ion elements available on that interface. Clause 7 describes the actual API of the UE application interface, providing detailed information how the information elements map into the RESTful API design of the interface. Clause 8 describes the authentication, authorization and access control for the U
37、E application interface. ETSI ETSI GS MEC 016 V1.1.1 (2017-09) 8 5 Description of the service (informative) 5.1 Sequence diagrams 5.1.1 Introduction The following clauses describe how the UE application interacts with the user application lifecycle management proxy over the UE application interface.
38、 The sequence diagrams that are relevant for the UE application interface are presented. 5.1.2 User application look-up The user application look-up is the procedure for requesting the list of available user applications in the mobile edge system to the requesting UE application. The user applicatio
39、n look-up procedure is illustrated in figure 5.1.2-1. Figure 5.1.2-1: User application look-up 1) The UE application submits the GET request to the user application lifecycle management proxy. The user application lifecycle management proxy authorizes the request from UE application. The mobile edge
40、 system retrieves the list of user applications available to the requesting UE application. 2) The user application lifecycle management proxy returns the 200 OK response to the UE application, with the message body containing the data structure for the list of available user applications. 5.1.3 App
41、lication context create The application context create is the procedure to request either to join with an available user application or to instantiate a new user application. The application context create procedure is illustrated in figure 5.1.3-1. ETSI ETSI GS MEC 016 V1.1.1 (2017-09) 9 Figure 5.1
42、.3-1: Application context create 1) The UE application submits the POST request to the user application lifecycle management proxy. The message body contains the data structure for the application context to be created. The user application lifecycle management proxy authorizes the request from the
43、UE application. The request is forwarded to the OSS. The OSS makes the decision on granting the context creation request. The mobile edge orchestrator triggers the creation of the application context in the mobile edge system. 2) The user application lifecycle management proxy returns the 201 Create
44、d response to the UE application with the message body containing the data structure of the created application context. 5.1.4 Application context delete The application context delete is a procedure in which the UE application requests the deletion of the application context. The application contex
45、t delete procedure is illustrated in figure 5.1.4-1. Figure 5.1.4-1: Application context delete 1) The UE application submits the DELETE request to the user application lifecycle management proxy for the resource to be deleted. The user application lifecycle management proxy authorizes the request f
46、rom UE application. The request is forwarded to the OSS. The OSS makes the decision on granting the deletion. The mobile edge orchestrator triggers the deletion of the application context. 2) The user application lifecycle management proxy returns “204 No content“ response. 5.1.5 Application context
47、 update The user application lifecycle management proxy receives an update of the ueAppContext. The procedure is illustrated in figure 5.1.5-1. ETSI ETSI GS MEC 016 V1.1.1 (2017-09) 10 Figure 5.1.5-1: Application context update 1) The UE application updates the ueAppContext. The request includes the
48、 contextId with the modified data structure of AppContext where only the callback reference is allowed to be updated by the UE application. 2) The user application lifecycle management proxy returns a “204 No Content“ response. 5.1.6 Receiving notification events Figure 5.1.6-1 presents the scenario
49、 where the user application lifecycle management proxy sends notification events to the UE application. Figure 5.1.6-1: Flow of receiving notification events Receiving notification events, as illustrated in figure 5.1.6-1, consists of the following steps: 1) The user application lifecycle management proxy sends a POST message to the callback reference address provided within the AppContext with the message body containing the notification event. 2) The UE application sends a “204 No Content“ response to the use
