ETSI GR MEC 018-2017 Mobile Edge Computing (MEC) End to End Mobility Aspects (V1 1 1).pdf

1、 ETSI GR MEC 018 V1.1.1 (2017-10) Mobile Edge Computing (MEC); End to End Mobility Aspects 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.

2、 It does not necessarily represent the views of the entire ETSI membership. GROUP REPORT ETSI ETSI GR MEC 018 V1.1.1 (2017-10) 2Reference DGR/MEC-0018E2EMobility Keywords MEC, mobility ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

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

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

5、table 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:/port

6、al.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, electroni

7、c 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 ri

8、ghts 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 Membe

9、rs. GSM and the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI GR MEC 018 V1.1.1 (2017-10) 3Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Defin

10、itions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Mobility requirements and use cases 7g34.1 Requirements and scenarios for mobility in ME system 7g34.1.1 Requirements for mobility in ME system . 7g34.1.2 Mobility scenarios in ME system . 8g34.2 Use case for optimization of a

11、pplication state relocation . 9g34.3 Use case for prediction of relocation timing. 10g34.4 Use case for mission critical low latency application relocation 11g34.5 Use case for service continuity with the UE moves in/out of ME host serving area 12g34.6 Use case for initial or/and simple deployment .

12、 13g34.7 GW based use case . 13g35 End to end information flows to support mobility . 14g35.1 An overview . 14g35.2 A flow for intra-ME host mobility . 16g35.3 A flow for inter-ME host mobility . 16g35.4 A flow for terminating an application instance 17g35.4.1 Terminate a dedicated service produced

13、by application instance . 17g35.4.2 Terminate a shared service produced by application instance 18g35.4.3 Gaps identified by information flow . 20g35.4.3.1 App instance life cycle change/creation/deletion notification . 20g35.4.3.2 Shared application instance creation and deletion . 20g35.5 Evaluati

14、on of application instance relocation . 21g35.5.1 General 21g35.5.2 Relocation notations . 21g35.5.3 High-level information flows for relocation procedure 22g35.5.4 Overview for a specific relocation method . 22g35.5.5 Evaluation for a specific relocation method 23g35.5.6 Gaps identified by informat

15、ion flow . 23g36 Key issues and potential solutions 24g36.1 Introduction 24g36.1.1 Roles and functions in service provisioning . 24g36.1.2 Problems and Assumptions . 25g36.1.3 Characterization of Service Continuity . 26g36.2 Key Issues 27g36.2.1 Key Issue: The optimization of application state reloc

16、ation . 27g36.2.1.1 Description 27g36.2.1.2 Solution 1: MEH assisted state relocation without RNIS 27g36.2.1.3 Solution 2: MEH assisted proactive state relocation for UE in connected mode 28g36.2.1.4 Solution 3: UE assisted state relocation 29g36.2.1.5 Solution 4: User plane optimization function 30

17、g36.2.1.6 Gaps identified by the key issue 30g36.2.1.6.1 ME application relocation detection 30g36.2.1.6.2 New function of user plane optimization function in MEPM 31g36.2.2 Key Issue: UE IP address change . 31g3ETSI ETSI GR MEC 018 V1.1.1 (2017-10) 46.2.2.1 Description 31g36.2.2.2 Solution 1 31g36.

18、2.2.3 Gaps identified by the key issue 32g36.2.3 Key Issue: Updating downlink traffic rules 32g36.2.3.1 Description 32g36.2.3.2 Solution 1: Update bearer information between different RNIS within one host . 32g36.2.3.3 Solution 2: Update bearer information by RNIS within one host . 33g36.2.3.4 Solut

19、ion 3: Update bearer information between different ME hosts . 34g36.2.3.5 Gaps identified by the key issue 35g36.2.4 Key Issue: Updating forwarding path inter ME host 35g36.2.4.1 Description 35g36.2.4.2 Solution . 35g36.2.4.3 Gaps identified by the key issue 35g36.2.5 Key Issue: Application instance

20、 relocation . 35g36.2.5.1 Description 35g36.2.5.2 Solutions . 36g36.2.5.2.1 Assumption 36g36.2.5.2.2 Solution for stateless application instance relocation 36g36.2.5.2.3 Solution for stateful application instance relocation 38g36.2.5.3 Gaps identified by the key issue 40g36.2.5.3.1 ME application mo

21、bility service 40g36.2.5.3.2 Enhancement of platform application enablement 41g36.2.6 Key Issue: Update traffic routing rules . 41g36.2.6.1 Description 41g36.2.6.2 Solution 1: update traffic routing rules triggered by RNIS . 41g36.2.6.3 Solution 2: update traffic routing rules triggered by UE UL Tra

22、ffic . 43g36.2.6.4 Solution 3: update traffic routing rules triggered by Mobile Edge Orchestrator . 45g36.2.6.5 Gaps identified by the key issue 46g36.2.7 Key Issue: Connectivity architecture 47g36.2.7.1 Description 47g36.2.7.2 Solutions . 48g36.2.8 Key Issue: Session and service continuity mode ind

23、ication to network . 48g36.2.8.1 Description 48g36.2.8.2 Solutions . 49g36.2.8.3 Gaps identified by the key issue 49g36.2.9 Key Issue: Application relocations in case of ping-pong handovers 49g36.2.9.1 Description 49g36.2.9.2 Solutions . 49g37 Gap Analysis and Recommendations . 49g37.1 Gap analysis

24、. 49g37.2 Recommendations 51g3History 52g3ETSI ETSI GR MEC 018 V1.1.1 (2017-10) 5Intellectual Property Rights Essential patents 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 avai

25、lable 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 the ETSI Secretariat. Latest updates are available on the ETSI Web serv

26、er (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 the updates on the ETSI Web server) which are, or may be, or may becom

27、e, 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 indicated as being the property of ETSI, and conveys no right to use or repr

28、oduce 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 Report (GR) has been produced by ETSI Industry Specification Group (ISG) M

29、obile Edge Computing (MEC). Modal verbs terminology In the present document “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must

30、not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI GR MEC 018 V1.1.1 (2017-10) 61 Scope The present document focuses on mobility support provided by Mobile Edge Computing. It documents mobility use cases and end to end information flows to support UE and Applica

31、tion mobility for Mobile Edge Computing. When necessary, the present document describes new mobile edge services or interfaces, as well as changes to existing mobile edge services or interfaces, data models, application rules and requirements. The present document identifies gaps to support mobility

32、 that are not covered by existing WIs, documents these gaps and recommends the necessary normative work to close these gaps. 2 References 2.1 Normative references Normative references are not applicable in the present document. 2.2 Informative references References are either specific (identified by

33、 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 included in this clause we

34、re 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 ETSI GS MEC 001: “Mobile Edge Computing (MEC) T

35、erminology“. i.2 ETSI GS MEC 003: “Mobile Edge Computing (MEC); Framework and Reference Architecture“. i.3 ETSI GS MEC 013: “Mobile Edge Computing (MEC); Location API“. i.4 ETSI GS MEC 010-2: “Mobile Edge Computing (MEC); Mobile Edge Management; Part 2: Application lifecycle, rules and requirements

36、management“. i.5 ETSI GS MEC 011: “Mobile Edge Computing (MEC); Mobile Edge Platform Application Enablement“. i.6 ETSI GS MEC 012: “Mobile Edge Computing (MEC); Radio Network Information API“. i.7 ETSI GS MEC 002: “Mobile Edge Computing (MEC); Technical Requirements“. i.8 3GPP TS 23.501: “System Arc

37、hitecture for the 5G System; Stage 2“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI GS MEC 001 i.1 and the following apply: application instance: realized software program executed in mobile edge host, which can pro

38、vide service to serve consumer(s) ETSI ETSI GR MEC 018 V1.1.1 (2017-10) 7application instance relocation: procedure of moving an application instance running on a mobile edge host to another mobile edge host, to support service continuity over underlying network application instance state transfer:

39、procedure of transferring the operational state of application instance from the source mobile edge host to the instance of the same application in the target host application mobility: part of mobility procedure for mobile edge system NOTE: It relocates an application dedicated to a service consume

40、r or shared by multiple service consumers from one mobile edge host to another. Application mobility may include application instance relocation and/or application instance state transfer from one mobile edge host to another. 3.2 Abbreviations For the purposes of the present document, the abbreviati

41、ons given in ETSI GS MEC 001 i.1 and the following apply: App Application CPN Connectivity Provider Network DP Data Plane GW Gateway FFS For Further Study MAMS ME Application Mobility Service ME Mobile Edge MEH Mobile Edge Host MEO Mobile Edge Orchestrator MEP Mobile Edge Platform MEPM Mobile Edge P

42、latform Manager PDN Packet Data Network RNIS Radio Network Information Service S-DP Date Plane of Source MEH S-MEH Source MEH S-MEP MEP of Source MEH T-DP Data Plane of Target MEH T-MEH Target MEH T-MEP MEP of Target MEH UE User Equipment VIM Virtualization Infrastructure Manager VM Virtual Machine

43、4 Mobility requirements and use cases 4.1 Requirements and scenarios for mobility in ME system 4.1.1 Requirements for mobility in ME system ME mobility is an important Mobile Edge Computing feature in a mobile environment, since UE mobility supported by the underlying network can result in UE moving

44、 to a network entity associated with a different ME host from the current serving ME host. ME system needs to support the following: continuity of the service;g3 mobility of application (VM), i.e. relocation of application instance; andg3 mobility of application-specific user-related information, i.

45、e. transfer application instance state related to UE. ETSI ETSI GR MEC 018 V1.1.1 (2017-10) 8To support ME service continuity, ME application mobility may involve multiple ME functional entities in order to relocate application instances and transfer user and application-specific information within

46、the ME system. Relocation decisions may be based on UE mobility, customer profiles and/or ME infrastructure capability. The requirements related to ME application mobility are listed as Mobility-01, 02, 03, Connectivity-01, 02, 03, 04, Routing-01, 02, 03, 04, 06, 10, 14, SmartReloc-01, 02, 03, 04,05

47、, 06 in ETSI GS MEC 002 i.7. Table 4.1.1-1 summarizes the architecture requirements related to ME mobility in ETSI GS MEC 003 i.2. Table 4.1.1-1: Requirements for ME mobility Numbering Functional requirement description Arch-01 The mobile edge system should support the mobility of application: as a

48、consequence of UE moving within the ME system; or at a certain condition that requires to move the ME applications to different ME host. Arch-02 The mobile edge system should support the ME service continuity of UE as the consequence of the application movement within the ME system, and support the

49、mobility of application-specific and user-related information. Arch-03 The mobile edge system should support application mobility for ME applications not sensitive to UE mobility. See note 1. Arch-04 The mobile edge system should support application mobility for the ME applications sensitive to UE mobility: Maintaining connectivity between UE and mobile edge application instance. Application state relocation. Application instance relocation within the mobile edge system. Arch-05 The mobile edge system should support: application instance