ETSI MEC: Where are we now

Transcription

1 ETSI MEC: Where are we now Presented by: Miltiadis Filippou For: MEC Hackathon and Edge Cloud Italy 2018 Sept. 18 th 2018

2 Part 1: What is MEC Presented by: Miltiadis Filippou For: MEC Hackathon and Edge Cloud Italy 2018 Sept. 18 th 2018

3 Why Edge Computing? as in Real Estate, it s about just 3 things: Location, Location, Location 3

4 ISG MEC Spec: MEC009 API Principles & Guidelines The Value of MEC RESTful based HTTP APIs presented via OpenAPI compliant descriptions ( in YAML & JSON including the full data model Simple to use, well documented APIs, published with OpenAPI Framework Create innovative applications quickly and easily, reducing time-to-revenue New APIs (compliant with the MEC API principles) can be added Increase the Total Addressable Market (TAM) MEC API Framework MEC012 Radio Network Info API MEC013 Location API MEC014 UE Identity API MEC015 Bandwidth Mgmt API MEC016 Device App API MEC Services exposed via individual APIs MEC028 WLAN Info API MEC0xy Your Service API MEC011 Application Enablement API MEC Platform 4

5 MEC paves the road to 5G It s really all about the applications Source: NGMN 5G White Paper 5G to require significant investment RAN, Core Network transformation A 4G déjà vu Invest now for the pot of gold later The pot of gold did not quite materialize Will history repeat itself with 5G??? MEC provides a way out of this Deploy your 5G apps on existing 4G architecture They will work all they need is Edge Presence (i.e. MEC) Tactile Internet with <10 msec latency a possible exception Invest in 5G as you scale i.e. when the revenues are a reality! See MEC 4G-to-5G White Paper for details 5

6 Part 2: ETSI MEC Introduction Presented by: Miltiadis Filippou For: MEC Hackathon and Edge Cloud Italy 2018 Sept. 18 th 2018

7 ETSI Multi-Access Edge Computing Pioneering open standards for Edge Computing since 2014 Still the leading international SDO focused on this space With leadership across ecosystem Broad participation : 7

8 ETSI MEC What we have achieved Where are we now? Foundation for Edge Computing created Fully standardized solution to enable applications in distributed cloud created by ETSI MEC + 3GPP API Framework Selection & re-location of UPF API Principles & Guidelines AF influence on traffic routing Service exposure via standardized APIs Management & Orchestration of Applications + Mobility event notifications from SMF = Concurrent access to local and central DN 82 members - Operators Technology Vendors IT players Application developers 8

9 ETSI MEC Foundation for Edge Computing Focused on application enablement & APIs Application Enablement API Principles Specific service-related Management and (API Framework) APIs Orchestration related APIs A framework for delivering services which may be A set of API principles and guidance for developing and Services expose network and context information via Facilitate the running of applications at the correct consumed or offered by (locally documenting APIs inside or specific service-related APIs. location at the right time, based hosted or remote) authorized applications. It enables: registration, announcement, discovery and notification of services; authentication and outside ETSI which ensures that a consistent set of APIs are used by developers. The work was inspired by the TMF and OMA best practices. A different set of services may be applicable at different locations on technical and business parameters authorization of applications providing and consuming services; The APIs are designed to be application-developer friendly and easy to implement so as to communication support for stimulate innovation and services (query/response foster the development of and notifications). applications. Enables a myriad of new use cases across multiple sectors as well as innovative business opportunities 9

10 ETSI MEC ISG: What Do We Specify? C R A N I O T C O N N. C A R S V R A R We don t make any of this work ETSI MEC We make it all work on your Generic Edge infrastructure And we help you expose the cool new things apps can do on your networks 10

11 ETSI MEC ISG: What Do We Specify? C R A N I O T ETSI MEC C O N N. C A R S V R A R API API API Key Operator Services API API API S V C S V C S V C Platform Functionality Management Orchestration Virtualization Infrastructure API Application Enablement ONM Services, Application LCM 11

12 Let s Make this More Specific Device Application API (GS MEC 016) Based on use case driven Requirements Spec (MEC 002) Platform Mgmt (GS MEC 10-1) Radio Network Information Service (GS MEC 012) Location Service (GS MEC 013) App. LCM (GS MEC 10-2) UE Identity Service (GS MEC 014) BW Mgmt Service (GS MEC 015) App. Enablement (GS MEC 11) We defined an architecture (MEC 003) API Rules for MEC APIs (MEC 009) 12

13 and understand our scope as part of a bigger MEC effort in the industry 3 rd party app APIs (OEC, MobileEdgeX) our customers : EdgeX / 5GAA / SCF / etc our customers : OSM / Akraino 3GPP xran ONF/ P4 3GPP xran OpenStack / Akraino 13

14 ...including, critically, ETSI NFV GR MEC 017 covers the study on MEC in an NFV environment GS MEC 003, the reference architecture v2.0.3, contains the architecture definitions available in the MEC Open Area (09/18) 14

15 Let s reflect on the work status Key overall specification Technical Requirements (MEC 002) Framework and Reference Architecture (MEC 003) MEC Proof of Concept (PoC) Process (MEC-IEG 005) API Framework (MEC 009) Iaas Management APIs (MEC and 010-2) PaaS Service Exposure Required Platform Svcs / App. Enablement (MEC 011) Service APIs (MEC 012, 013, 014, 015) UE Application Interface (MEC 016) Key Studies for Future Work Study on MEC in NFV (MEC 017) Study on Mobility Support (MEC 018) Evolution of Phase 1 and closing open items Application Mobility (MEC 021) Lawful Intercept (MEC 026) Addressing key Industry Segments V2X (MEC 022, MEC 030) Industrial Automation, VR/AR Key use-cases and new requirement Network Slicing (MEC 024) Container Support (MEC 027) Normative work for integration with NFV Incorporate in v2 of existing specs as needed From Mobile to Multi-Access Wi-Fi (MEC 028) Fixed Access (MEC 029) Developer community engagement Open SW engagement (MEC 023) API publication through ETSI Forge (more overleaf) Testing and Compliance (MEC 025) ETSI MEC phase 1 (Published) ETSI MEC phase 2 (in Progress) 15

16 So Back to Specifics Based on use case driven Requirements Spec (MEC 002) User App LCM via Device App API (MEC 016) Support for Mobility (MEC 018 and MEC 021) WLAN Network Information Service (MEC 028) Fixed Access Network Information Service (MEC 029) LCM Evolution -- NFV-integrated Stage 3 (MEC 10-2) -- Container support (MEC 027) -- Support of Mobility (MEC 10-2, 18) -- Support of Network Slicing (MEC 024) Regulatory Support (MEC 026) V2X Service (MEC 022 and MEC 030) We defined an architecture (MEC 003) API Rules for MEC APIs (MEC 009) 16

17 MEC Phase 2 MEC-021 MEC-0022 MEC-0023 MEC-0024 MEC-0025 Application Mobility V2X Support (study) OpenAPI NW Slicing Testing Framework Service&Session Cont. Multi-operator OpenAPIFramework Slicing in Federated Cloud Compliancy Application Relocation Multi-Domain Swagger Multi-Domain Test Cases ETSI Forge MEC-0026 MEC-0027 MEC-0028 MEC-0029 MEC-0030 Lawful Intercept Containers (study) WLAN API Fixed API V2X API Regulatory requirements Support for Containers WLAN Access Information Fixed Access Information V2X service in Multi- on LI and RD exposure exposure operator, -network,-vendor domain From Mobile Edge Computing (Cellular) To Multi-access Edge Computing (Cellular, WLAN, Fixed, etc.) 17

18 MEC Phase 2 Application Mobility (MEC 021) Introduces normative changes for MEC to support mobility of the application/context Applies to stateful applications only Requires application support Study item report GR MEC 018 (finalised 2017) includes key issues, conclusions, recommendations When the location of the application instance is changed, the context needs to be relocated for seamless service continuity Three high level options introduced for the context transfer: 1. Device application assisted 2. MEC system assisted 3. Application self-controlled MEC deployment in 5G system can take benefit from 5G edge computing enablers AF influence on traffic routing, UPF re/selection, event notifications Preferably the AF (MEC) had means to indicate its readiness wrt. target app instance The user context transfer remains in the scope of MEC 18

19 MEC Phase 2 V2X Service API (MEC 030) MEC is a standardised solution for C-V2X edge cloud deployments (5GAA White Paper Dec.2017: Toward fully connected vehicles: Edge computing for advanced automotive communications) Work Item MEC 030 introduces new MEC Service, V2X Information Service (VIS) based on the study report conclusions in MEC GR 022 Automotive use cases involve multiple stakeholders: different car makers, OEM suppliers, network infrastructure vendors, MEC vendors, application/content providers and other stakeholders. Key requirement for V2X Information Service is the support for service exposure and communication ability across participating V2X applications in different MEC systems V2X service continuity is essential across all territory including transition from one operator s area to another and out of coverage areas Web PGW 1 Remote Application Server PGW 2 Low latency is essential in C-V2X edge cloud deployments SGW 1 V2X Service API is to expose PC5 interface configuration parameters of one system to another system Figures illustrate the multi-operator scenario and the optimised path for information exchange and communication UE SGW 2 S1 MEC Host 2 RAN 2 Operator 2 RAN 1 MEC Host 1 UE Operator 1 19

20 MEC Phase 2 WLAN & Fixed Access Service APIs (MEC 28 & 29) MEC as Multi-access Edge Computing supports not only Radio Access (cellular) Information Service but also WLAN and Fixed Access information Services Fixed Access Information Service (FAIS) provides the fixed access information to service consumers, and is discoverable for the authorized MEC applications via the Application Enablement API on the Mp1 reference point FAIS API supports both queries and subscriptions/notifications The FAI service may be used by the MEC applications and the MEC platform to optimize the existing services and to provide new type of services that are based on up to date information from the fixed access Available information includes (Note: work in progress) Available fixed access types in the area Subscriber line status information Device status information 20

21 MEC Phase 2 - Testing and Compliance (MEC 025) Common Test Framework for conformance & interoperability Multi-vendor, multi-network and multi-service environment Harmonised global approach to MEC test standards Testable MEC standards Preventing MEC market fragmentation Testing Methodology Guidelines Joint development with ETSI CTI Based on industry recognized best practices External Special Task Force (STF) team established to define the Test Framework details Test procedures, test architecture, applicable reference points, test specification development procedures Target publication: April

22 MEC Phase 2 Study Items MEC 024, 026, 027 GR MEC 024 MEC Support for Network Slicing: identifies requirements to MEC from network slicing primarily following 3GPP approach to network slicing. The practical question in the study is the slice boundary, what is in and what is out, and what is the resulting impact on MEC management plane Figure shows an example of network slicing with MEC as the edge computing deployment This study item is work in progress, scheduled to be complete early 2019 GR MEC 026 Support for Regulatory Requirements: identifies requirements to MEC from regulatory requirements for Lawful Interception (LI) and Retained Data (RD) Study item is complete with the following conclusion: Except for the deployment scenario over S1 without CUPS feature supported, all MEC deployment scenarios considered in the study support LI as part of the 3GPP standards. ETSI White Paper MEC in 5G Networks (ETSI WP#28) describes how the 5G integrated deployment of MEC supports the LI&RD through UPF GR MEC 027 MEC support for containers: identifies additional support that needs to be provided by MEC when MEC applications run as containers, with the objective of re-using the findings of ETSI ISG NFV on the application of Different Virtualisation Technologies in the NFV Framework So far the MEC onboarding, application description and application Life Cycle Management are based on the assumption that the MEC app runs in a Virtual Machine. This study item is work in progress, scheduled to be complete early

23 OpenAPI description files OpenAPI Specification (aka Swagger Specification) Open source framework for defining & creating RESTful APIs OpenAPI Specification compliant API description file Inherently includes MEC data structure definitions Machine readable facilitating content validation Allows auto-creation of stubs for both service client & server Motivation with ISG Validation Integrity and completeness of the Specifications Accessibility & Adoption Outside of the ISG, i.e. 3 rd party developers Feedback External critical review & feedback Where we are now Future Plans Release of new API descriptions as corresponding specifications published Upgrade to OpenAPI 3.0 (from current 2.0) once associated 3 rd party tooling matures Currently exploring other approaches towards a more extensive engagement with the developer community 3 ETSI Repository: GitHub mirror: MEC 11, 12, 13, 14, 15 & 16 already available Tiger Team: timely updates & resolution of bugs, queries, etc. 23

24 MEC PoCs: Show off YOUR cool Edge These PoCs are currently active (first 8 are done) PoC #10 PoC #11 Service-Aware MEC Platform to Enable Bandwidth Management of RAN Industry Technology Research Institute - Linker Network - FarEasTone Communication Traffic Management for V2x KDDI Corporation - Saguna Networks Ltd. - Hewlett Packard Enterprise We encourage new POC submissions to ETSI MEC! PoC #12 MEC Enabled OTT Business The next PoC IMAGINE YOUR BEST HERE For further details, please see: or contact CTI_Support@etsi.org China Unicom, ZTE, Intel, Tencent, Wo video, UnitedStack Thought Leaders in Edge Computing 24

25 MEC Deployment Trial: MEC in action in Live Networks Next step from MEC PoC to keep engaging the ecosystem in MEC standards based deployments From Proof of Concept to proof of viability in a Live Network environment Follows the proven MEC PoC framework with a new set of acceptance criteria 1. Trial deployed in Live Network 2. Demonstrated to the industry, e.g. in an industry event or in ISG MEC 3. Feedback to MEC standardization; improvement proposals, lessons learnt, next steps MEC Deployment Trial We encourage new MDT submissions to ETSI MEC! MDT #1 <your MEC deployment trial here> MDT Team (at minimum two different stakeholders: Operators, Infra vendors, Application/Content providers) For further details, please see: or contact CTI_Support@etsi.org 5 25

26 MEC Hackathons ETSI ISG MEC Hackathon Framework: Open Call for proposers and hosts interested in organizing a MEC Hackathon Submit on our Wiki page First Hackathons already scheduled ETSI sponsored/organized Hackathon Co-located with Edge Computing Congress ETSI supported hackathons: We encourage new proposals for MEC Hackathons! For further details, please see: or contact CTI_Support@etsi.org Turin: Beijing: 26

27 MEC White Papers: A view of a whole picture Standards are necessarily tools, not solutions Enable interoperability Support a broad range of use cases and system architecture Address only a specific part of the whole picture 7 MEC White Papers: how we help industry see the whole picture Developing SW for MEC CRAN and MEC: A Perfect Pairing: MEC deployment in 4G and towards 5G: MEC in 5G Networks: and many more to come! 27

28 I want to help, what can I do 8 First, join the ISG. You do NOT have to be an ETSI Member Talk to us about the details I am a Telco Industry Operator/Vendor and want to see Edge Cloud deployed Great, help us design and standardize a world-class service framework I am an Application Developer and need my apps to run at the edge Great, help us make what we did available for other developers to use I am an Infrastructure Vendor or a System Test/Integrator Great, come help develop Proof of Concepts for the most innovative 5G system I am an Industry Organization and need Edge to enable my target market Great, we want to partner with you to enable your target market 28

29 9 Epilogue ETSI ISG MEC is the leading voice in standardization and industry alignment around MEC Key building block in the evolution of mobile-broadband networks, complementing NFV and SDN. Key enabler for IoT and mission-critical, vertical solutions. Widely recognized as one of the key architectural concepts and technologies for 5G. Can be used to enable many 5G use cases without a full 5G roll-out (i.e. with 4G networks) Enable a myriad of new use cases across multiple sectors as well as innovative business opportunities. The work on Phase 2 is extending the applicability of the MEC technology and rendering MEC even more attractive to operators, vendors and application developers. 29

30 THANK YOU Contact Details Chair: Alex Reznik, ETSI Support Officer: Chantal Bonardi, Thank you! 0 30

31 Backup slides 1 31

32 3GPP enablers for MEC Selection & re-location of UPF MEC as an AF (Application Function) can request the 5GC to deploy local UPF near to the target (R)AN node use the local UPF for PDU sessions of the target UE(s) control the traffic forwarding from the local UPF so that the UL traffic matching with the traffic filters received from MEC (AF) is diverted towards MEC hosts while other traffic is sent to the Central Cloud Selection & re-location of UPF AF influence on traffic routing Mobility event notifications from SMF Concurrent access to local and central DN NSSF AUSF UDM AMF SMF MEC AF UE RAN UPF UPF DN PCF In case of UE mobility re-select a new local UPF more suitable to handle application traffic identified by MEC (AF) notify the AF about the new serving UPF DN 32

33 3GPP enablers for MEC AF influence on traffic routing MEC as an AF can provide the following to 5GC traffic filters identifying MEC applications deployed locally on MEC hosts in Edge Cloud the target UEs (one UE identified by its IP/MAC address, a group of UE, any UE) information about forwarding the identified traffic further e.g. references to tunnels towards MEC hosts Selection & re-location of UPF AF influence on traffic routing Mobility event notifications from SMF Concurrent access to local and central DN NSSF AUSF UDM AMF SMF PCF MEC AF UE RAN UPF UPF DN DN 33

34 3GPP enablers for MEC Mobility event notifications 5GC allows MEC as an AF subscribe to UE mobility events that may affect traffic forwarding to MEC applications Receive notifications of UE mobility events affecting MEC application instances Selection & re-location of UPF AF influence on traffic routing Mobility event notifications from SMF Concurrent access to local and central DN NSSF AUSF UDM AMF SMF PCF MEC AF UE RAN UPF UPF DN DN 34

35 3GPP enablers for MEC - Concurrent access to local and central DN Concurrent access to services regardless of the location - edge and central Consumer does not have to select where to get the service as the Service Provider decides where to host the contents. Selection & re-location of UPF AF influence on traffic routing NSSF AUSF UDM Mobility event notifications from SMF AMF SMF PCF MEC AF Concurrent access to local and central DN Central Cloud a.k.a. Conventional internet UE RAN UPF UPF DN DN Edge Cloud for Ultra-low latency, high reliability services 35