ETSI MEC: An Introduction
ETSI MEC: An Introduction(almost) everything you want to know about ETSI MECETSI MEC Leadership TeamFor: Public consumptionLast update: May 2022
ETSI MEC: Enabling Edge through StandardizationWatch the new video on MEChttps://www.youtube.com/watch?v crnPWql-0ooETSI ISG MECETSI: The Standards PeopleWe produce globally applicable standardsfor ICT-enabled systems, applications andservices deployed across all sectors ofindustry and societyMEC: Multi-access Edge ComputingCloud Computing at the Edge of thenetwork.ISG: Industry Specification Groupopen to all of industry, regardless of ETSImembership and focused on all industry needsStandards ETSI 2022 – All rights reserved Industry Enablement Telco Edge Focus
ETSI MECWhat we doWhereare we–now?Foundation for Edge Computing created – Fully standardized solution to enable applications in distributed cloud created by ETSI MEC 3GPPNFVApplication Life Cycle ManagementMECRESTful based APIs for Runtime Application ServicesLook at the new webpage withthe ISG MEC Leaders andSupport ders-and-Support-Team126 members - Operators – Technology Vendors – IT players – Application developers ETSI 2021 – All rights reserved3
The essence of MECMEC offers to application developers and content providers cloud-computing capabilitiesand an IT service environment at the edge of the networkHow do I reachmy cloud service?What is my QoS?Where am I?What is aroundme?How do I get discovered bymy users?How am I connected to theusers?How many users am Iserving? And whereHow to be sure I am runningwhen and where needed?What if my users move?MEC is focused on existential questions of applications “on the edge” ETSI 2021 – All rights reserved4Img Source: etsi wp20ed2 MEC SoftwareDevelopment.pdf
MEC reference architectureAPIs Application SupportService ManagementRadio Network InformationLocationUE IdentityBandwidth ManagementFixed Access InformationWLAN InformationV2X Information Service Application Packagelifecycle and operationgranting Device applicationinterface ETSI 2021 – All rights reserved5
3rd 3-year Phase of work under way Key overall specification Evolution of Phase 1 and closing open items Application Mobility (MEC 021 – published) Technical Requirements (MEC 002) Framework and Ref. Arch. (MEC 003) MEC PoC Process (MEC-IEG 005) API Framework (MEC 009) IaaS Management APIs Platform mgmt. (MEC 010-1) Application mgmt. (MEC 010-2) Device-triggered LCM operations (MEC 016) PaaS Service Exposure Required Platform Svcs / App. Enablement(MEC 011) Service APIs (MEC 012, 013, 014, 015) Key Studies for Future Work Study on MEC in NFV (MEC 017) Study on Mobility Support (MEC 018)2015ETSI MEC phase 1 (Completed) ETSI 2021 – All rights reserved Lawful Intercept (MEC 026 – published) Addressing key Industry Segments V2X (MEC 022 – published; MEC 030 – published) IoT (MEC 033), Industrial Automation, VR/AR Key use-cases and new requirement Network Slicing (MEC 024 – published) Container Support (MEC 027 – published) Normative work for integration with NFV Incorporate in v2 of existing specs as needed From “Mobile” to “Multi-Access” Wi-Fi (MEC 028 – published) Fixed Access (MEC 029 – published) MEC integration in 5G networks (MEC 031) Developer community engagement API publication through ETSI Forge (more overleaf) Full Phase 3 work started already, while completingoutstanding Phase 2 work. MEC as heterogeneous clouds Expanding traditional cloud and NFV LCM approaches Inter-MEC systems and MEC-Cloud systems coordination:“MEC Federation”(MEC 035 – published / MEC040 -- ongoing) Mobile or intermittently connected components, andresource constrained devices (MEC 036) MEC Security (GR MEC 041) MEC Application Slices (GR MEC 044) MEC deployments MEC in Park enterprises (MEC 038) Continuing emphasis on enabling developers Application Package Format and Descriptor Specification (MEC 037) API Serialization Sandbox development Testing and compliance Maintain completed APIs Testing and Compliance (MEC-DEC 025 – published; Continue to define services that meet industrymultipart specification MEC-DEC 032-x)demand (e.g., GR MEC 043) Hackathons, MEC Delpoyment Trials2018ETSI MEC phase 2 (Completing)2021ETSI MEC phase 3 (ongoing)6
OurStandards ETSI 2021 – All rights reserved
ETSI MEC– Foundationfor EdgeFocusedon applicationenablement& APIsComputingBasic principles: Open standard allowing multiple implementations and ensuring interoperability MEC exploiting ETSI NFV framework and definitions enabling MEC in NFV deployments Alignment with 3GPP based on fruitful collaboration of common member companies enabling MEC in 5G Access-agnostic nature (as per MEC acronym - Multi-access Edge Computing) enabling other accesses Addressing the needs of a wide ecosystem enable multiple verticals (e.g. automotive), federationsIn 2021 5GAA joinedthe MEC membership ETSI 2021 – All rights reserved8
ETSI MEC– Foundationfor EdgeFocusedon applicationenablement& APIsComputingApplication Enablementand FrameworkAPI PrinciplesService definition frameworkand baseline platform servicesauthorized applications.Principles and guidance fordeveloping and documentingAPIs Registration, discovery andnotification; Developer-friendly approachto foster developmentMethodology forauthentication andauthorization of appsproviding/consumingservices; Ensures that a consistentset of APIs are used bydevelopers. Communication support forservices (query/responseand notifications). Defines approach forauthentication andauthorization of appsproviding/consuming servicesSpecific service-relatedAPIsManagement andOrchestration related APIsStandardized service-exposureAPIs for key services thatManagement of MEC hosts eitheras stand-alone entities or part ofa larger NFV-managedframework Expose network andcontext information Allow definition of localized,contextual services Support key use cases (e.g.enterprise, vehicular) Allow fine-grained edgetraffic management Facilitate running of 3rd partyapplication Enable deployment at thecorrect location at the righttime, based on technical andbusiness parameters Integrate into telco operationssystems, e.g. OSS Based on TMF and OMA bestpracticesEnables a myriad of new use cases across multiple sectors as well as innovative business opportunities ETSI 2021 – All rights reserved9
Enabling Global Application Portability Simple to use, well documented APIs,published with OpenAPI Framework Create innovative applications quicklyISG MEC Spec: MEC009API Principles & Guidelinesand easily, reducing time-to-revenue New APIs (compliant with the MECRESTful based HTTP APIs presented via OpenAPI compliant descriptions(https://forge.etsi.org/), in YAML & JSON including the full data modelAPI principles) can be added Increase the Total Addressable Market(TAM)MEC APIFrameworkMEC012Radio NetworkInfo APIMEC013Location APIMEC014UE IdentityAPIMEC015BandwidthMgmt APIMEC028WLAN InfoAPIMEC Services exposed via individual APIs ETSI 2021 – All rights reservedMEC029Fixed AccessInfo APIMEC0xyYour ServiceAPIMEC011ApplicationEnablement APIMEC Platform10
Application portability via the ETSI MEC APIs ecosystemThat’s all you need as a MEC AppdeveloperDiscover network, users,capabilities and local servicesManage traffic, DNS, mobility,V2X, etc.Register your own service anddiscover third party servicesavailable locallyPlus: APIs for interoperabilityamong MEC systems and infra ETSI 2021 – All rights reserved11
MEC and Management: The Killer Use Case for AutomationMEC deployments present challenging environmentUnique requirements and processes (large scale: geography) x (small scale: cloud footprint) Minimize need for human presence Unmanned/lights out location Maximize service time intervals Outside traditional service areas Minimize skills required from those on siteWhile supporting “critical infrastructure”In other words Telco, public safety, etc. Get as close as possible to the web-scale maintenance model “9’s” of availability requirements In a very non-web-scale environment The following ETSI White Papers address the MEC deployment aspects: WP#23: Cloud RAN and MEC: A Perfect PairingWP#24: MEC Deployments in 4G and Evolution Towards 5GWP#28: MEC in 5G networksWP#30: MEC in an Enterprise Setting: A Solution Outline ETSI 2021 – All rights reservedAll white papers are available pers.aspx12
A key part of ETSI Network Automation StandardsInter-MEC &MEC-Cloud(MEC 035 Study)Device-triggeredLCM Enablement(MEC 16)Management ofMEPas a VNF(MEC 10-1)LCM Mgmt of 3rdparty Apps(MEC 10-2)ZSM: overall approach ETSI 2021 – All rights reservedNFV, OSM: managing telco cloudsMEC: managing edge telco clouds13
MEC White Papers: A view of a whole pictureStandards are necessarily tools, not solutionsEnable interoperabilitySupport a broad range of use cases and system architectureAddress only a specific part of the whole pictureMEC White Papers: how we help industry see the whole pictureHarmonizing Standards for Edge Computing: a synergized architecture leveraging ETSI MEC and etsi-isg-mec-and-3gpp-specificationsMEC in an Enterprise Papers/etsi wp30 MEC Enterprise FINAL.pdfMEC in 5G Networks: tsi wp28 mec in 5G FINAL.pdfMEC deployment in 4G and towards s/etsi wp24 MEC deployment in 4G 5G FINAL.pdfCRAN and MEC: A Perfect Papers/etsi wp23 MEC and CRAN ed1 FINAL.pdfDeveloping SW for MEC (2nd ers/etsi wp20ed2 MEC SoftwareDevelopment.pdf ETSI 2021 – All rights reserved14 and many more to come!
New WI on MEC Security(GR MEC 041)MEC security MEC scenarios are characterized by a complex multi-vendor, multi-supplier, multi-set ofequipment including both HW and SW devices. Given this overall level of systemheterogeneity, areas of security, trust, and privacy are key topics for the edge environments. In that perspective, MEC stakeholders should pay attention to the vulnerability and integrityof any third-party elements, and a truly end-to-end approach to MEC security needs toMulti-access Edge Computingconsider not only the current standards in ETSI ISG MEC, but also the other availablestandards that can be applicable to the MEC environment. ETSI white paper, authored by many experts (in the domain of edge computing, security and involved in variousstandard bodies), provides an overview of ETSI MEC standards and current support for security, which is alsocomplemented by a description of other relevant standards in the domain (e.g. ETSI TC CYBER, ETSI ISG NFV,3GPP SA3) and cybersecurity regulation potentially applicable to edge computing. rity ETSI 2021 – All rights reserved15
Focus onMECFederation ETSI 2021 – All rights reserved
MEC Phase 3: expanding the scope to MEC FederationStarting fromIndustry requirements Ref: GSMA White paper: “Telco Edge Cloud: Edge Service Description and Commercial Principles”, Oct 2020 ETSI MEC published a very first work on MEC federationETSI GR MEC 035 v3.1.1: “Multi-access Edge Computing(MEC); Study on Inter-MEC systems and MEC-Cloudsystems coordination ”, June 2021,https://www.etsi.org/deliver/etsi gr/MEC/001 099/035/03.01.01 60/gr mec035v030101p.pdf ETSI 2021 – All rights reservedMEC Federation:“federated model of MEC systems enablingshared usage of MEC services and applications”17
MEC Phase 3: expanding the scope to MEC FederationIntra MECInter MEC host (Intra MEC system)management already supportedby ETSI MECMain scope for MEC 035 studyInter MECMEC - CloudOngoing normative work(e.g. GS MEC 040, MEC 003),in alignment withGSMA OPG requirements ETSI 2021 – All rights reservedRef: ETSI GR MEC 035 v3.1.1, June 2021, https://www.etsi.org/deliver/etsi gr/MEC/001 099/035/03.01.01 60/gr mec035v030101p.pdf18
MEC Study on Inter-MEC systems and MEC-Cloud systemscoordination (MEC 035)Many Use cases#1: MEC federation scenario of V2X services1. Interop. between MNOs2. Interop. between MECvendors/suppliers3. Interop between OEMs(applications)Inspired by 5GAA use casesincluding multi-MNO, multiOEM, multi-MECRequirements for MEC: MEC system discovery MEC platform discovery MEC platform levelinformation exchange ETSI 2021 – All rights reservedRef: ETSI GR MEC 035 v3.1.1, June 2021, https://www.etsi.org/deliver/etsi gr/MEC/001 099/035/03.01.01 60/gr mec035v030101p.pdf19
Study (MEC 035) oninter-MEC system and Cloud-MEC system coordinationMulti-operator agreements enabling MEC Federation for V2X services Type-1 use case - national roaming likescenario: customers of operator A couldaccess the edge infrastructure of operator Bto ensure the best possible service. Type-2 use case: An app developer has acommercial relationship with operator A.Federation agreements could allow the appdeveloper to deploy its App in operator B’sMEC system. Type-3 use case - federation broker: afederation broker has a set of agreementswith several MNOs. ETSI 2021 – All rights reservedRef: ETSI GR MEC 035 v3.1.1, June 2021, https://www.etsi.org/deliver/etsi gr/MEC/001 099/035/03.01.01 60/gr mec035v030101p.pdf20
MEC Study on Inter-MEC systems and MEC-Cloud systemscoordination (MEC 035)Many Use cases#6: MEC federation scenario for immersive AR game ETSI 2021 – All rights reservedRef: ETSI GR MEC 035 v3.1.1, June 2021, https://www.etsi.org/deliver/etsi gr/MEC/001 099/035/03.01.01 60/gr mec035v030101p.pdf21
GSMA OPG (Operator Platform Group) mapping with ETSI MECETSI MEC is aligning alsowith 3GPP to create aconsistent standard andavoid duplication of workNote: GSMA is listed as a MEC Participant, can submit contributions to ISG MEC for Discussion or Decision,and not only for Information. Dually, ETSI MEC nominated 2 observers, to represent the ISG in GSMA OPG.Ref: GSMA Permanent Reference Document, "Operator Platform Telco Edge Requirements", v1.0, Jun. 2021. ETSI 2021 – All rights reservedLink:22
MEC 003 – introducing Architecture variant for MEC federationPhase 3 deliverable published in March 2022MEC federator (MEF): enables a MEC federationbetween MEC systems A MEF interfaces to at least one MEO Each MEF enables information exchangewith at least one other MEF A MEF may serve as a single point of contactfor multiple MEFs in the MEC federationMEF may support the following functionality: ETSI 2021 – All rights reservedregistration of MEC system information by a MEO;MEC system discovery;broker capability acting as a one to manyintermediary between MEFs;information (e.g. MEC system information)exchange;application lifecycle management (e.g. onboarding/instantiation/termination) acrossdifferent MEC systems;application monitoring across different MECsystems.Reference: https://www.etsi.org/deliver/etsi gs/MEC/001 099/003/03.01.01 60/gs MEC003v030101p.pdf23
WG DECODE:Enabling MECDeploymentand EcosystemDevelopment ETSI 2021 – All rights reserved
ETSI ISG MEC DECODE Working Group:MEC Deployment and Ecosystem engagement activities OpenAPI representations: ETSI Forge Testing and Conformance MEC Ecosystem wikihttps://try-mec.etsi.org/ PoCs (proof-of-concepts) MDTs (MEC Deployment Trials) MEC Sandbox Collaborations: Akraino12 Oct 2021,https://www.edgecomputingworld.com/hackathon/ Hackathons1 - 15 Oct 2021NFV&MEC IOPPlugtests 2021 Plugtests MEC Tech Series ETSI 2021 – All rights lhttps://mecwiki.etsi.org/index.php?title MEC Ecosystem
MEC: DECODE Working Group OpenAPI representations: ETSI Forge Testing and Conformance MEC Ecosystem wiki PoCs (proof-of-concepts)Discover the APIs on forge.etsi.org/rep/mecPowered byNews: new STF (Special Task Force)for OpenAPI implementationStatus: accepted by ETSI Boardand work started early Nov 2021 MDTs (MEC Deployment Trials) MEC Sandbox Collaborations: Akraino Hackathons Plugtests MEC Tech Series ETSI 2021 – All rights reservedOperated by26
MEC: DECODE Working GroupNews: new Work Item MEC-DEC0042for Testing an Interoperability OpenAPI representations: ETSI Forge Testing and Conformance MEC Ecosystem wiki PoCs (proof-of-concepts) MDTs (MEC Deployment Trials)FUTTestEnvironmentOpenAPIsMEC APITestSystemGeneral testingframework for MECTechnologies (MEC 0025)Robot MEC SandboxAPI Conformance testingdeveloped for serverimplementations Collaborations: Akraino Hackathons Plugtests MEC Tech Series ETSI 2021 – All rights reservedMEC APIsStandardized test suite (MECDEC 032)Testimplementations in RobotFramework and TTCN-3Openly available andreleased under BSD-3 licenseMEC-DEC03227
MEC: DECODE Working Group OpenAPI representations: ETSI ForgePoCshttps://mecwiki.etsi.org/index.php?title Ongoing PoCs Testing and Conformance MEC Ecosystem wiki PoCs (proof-of-concepts)New MDTsMEC Deployment Trialshttps://mecwiki.etsi.org/index.php?title Ongoing MDTsWe encourage newsubmissions to ETSI MEC ! MDTs (MEC Deployment Trials) MEC Sandbox Collaborations: Akraino HackathonsMEC Ecosystemhttps://mecwiki.etsi.org/index.php?title MEC EcosystemNew implementationsFor further details,please see:http://mecwiki.etsi.org orcontact CTI Support@etsi.org Plugtests MEC Tech Series ETSI 2021 – All rights reserved28
MEC PoCs: Show off YOUR cool EdgeRecent PoCs (9 are complete)PoC #11PoC #10Service-Aware MEC Platformto Enable BandwidthManagement of RANCommunication TrafficManagement for V2xIndustry Technology Research Institute- Linker Network - FarEasToneKDDI Corporation - Saguna Networks Ltd.- Hewlett Packard EnterpriseThe next PoCWe encourage new POCsubmissions to ETSI MEC !IMAGINE YOUR BEST HEREPoC #12MEC Enabled OTT BusinessChina Unicom, ZTE, Intel, Tencent, Wovideo, UnitedStackPoC #13MEC infotainment for smartroads and city hot spotsThought Leaders in EdgeComputingFor further details,please see:http://mecwiki.etsi.org orcontact CTI Support@etsi.orgTIM, Intel, Vivida, ISMB, City of Turin ETSI 2021 – All rights reserved29
MEC Deployment Trial: MEC in action in Live NetworksNext step from MEC PoC to keep engaging the ecosystem in MEC standards based deploymentsFrom Proof of Concept to proof of viability in a Live Network environmentFollows the proven MEC PoC framework with a new set of acceptance criteria1. Trial deployed in Live Network2. Demonstrated to the industry, e.g. in an industry event or in ISG MEC3. Feedback to MEC standardization; improvement proposals, lessons learnt, next stepsWe encourage new MDTsubmissions to ETSI MEC !Currently the following MDTs are active:MEC Deployment TrialMEC Deployment TrialMDT #1CDN at the EdgeChina Mobile, NokiaMDT #2MEC in FactoryNetworkChina Mobile, Huawei ETSI 2021 – All rights reservedMEC Deployment TrialMEC Deployment TrialMDT #3MDT #4Edge-Cloud VR cloudgame scheme basedon 5G networkARVR navigationbased on 5G MECChina Unicom, Huawei,Tencent, IntelFor further details,please see:http://mecwiki.etsi.org orcontact CTI Support@etsi.orgChina Telecom, Huawei,21CN30
MEC: DECODE Working Group OpenAPI representations: ETSI Forge Testing and Conformance MEC Ecosystem wiki PoCs (proof-of-concepts) MDTs (MEC Deployment Trials) MEC SandboxNew features andAPIs implemented Collaborations: Akraino Hackathons Plugtests MEC Tech Series ETSI 2021 – All rights reservedhttps://try-mec.etsi.org/A simulator of a real 4G/5G network as seen via the MEC APIs4G/5G/Wifi access pointsSteady and moving UE ( devices)API Console, integrated Swagger UI, & moreReal MEC Apps can interact with the Sandbox and can register services31
MEC: DECODE Working Group OpenAPI representations: ETSI Forge Testing and ml MEC Ecosystem wiki PoCs (proof-of-concepts) MDTs (MEC Deployment Trials) MEC Sandbox Collaborations: Akraino Hackathons Plugtests MEC Tech Series ETSI 2021 – All rights reserved32
MEC: DECODE Working Group OpenAPI representations: ETSI Forge Testing and ConformancePast MEC Hackathons: MEC Ecosystem wiki MEC SandboxTurin (Italy)17-18 September 2019: 2 parallel events (link) PoCs (proof-of-concepts) MDTs (MEC Deployment Trials)18-19 September 2018: 3 parallel events (link) Berlin (co-located with Edge Computing Congress) Beijing (China)London, UK (co-located with Edge Computing Congress)Shenzen (China) 18 November 2019, in collab. with LF Edge and Akraino (link) San Diego (USA) (with KubeCon CloudNativeCon North America) 25-26 November 2020 2020 Droidcon MEC Hackathon (co-located with Droidcon Italy) Collaborations: Akraino HackathonsMEC Hackathon 2021 Plugtests MEC Tech Series ETSI 2021 – All rights reserved3312 Oct 2021, https://www.edgecomputingworld.com/hackathon/
MEC: DECODE Working Group OpenAPI representations: ETSI Forge Testing and Conformance MEC Ecosystem wiki PoCs (proof-of-concepts) MDTs (MEC Deployment Trials) MEC Sandbox Collaborations: Akraino Hackathons3 – 7 June 20194th NFV Plugtests201915 – 9 June 2020NFV&MECPlugtests 20201 – 28 Feb 2021NFV&MEC APIPlugtests 20212021 editions1 - 15 Oct 2021NFV&MEC IOPPlugtests 2021 Plugtests MEC Tech Series ETSI 2021 – All rights reserved34
MEC: DECODE Working Group OpenAPI representations: ETSI Forge Testing and Conformance MEC Ecosystem wiki PoCs (proof-of-concepts) MDTs (MEC Deployment Trials) MEC Sandbox Collaborations: Akraino Hackathons Plugtests MEC Tech Series ETSI 2021 – All rights reserved35
The largerTelco World:ETSI MEC and 5G ETSI 2021 – All rights reserved
MEC Phase 2 – Study Item MEC in 5G (MEC 031)The ETSI white paper MEC in 5G networks sets the scene for this study itemISG MEC investigates the opportunities offered to MEC by the 5G system and its edge computing enablersThe scope includes the followingNSSFNRFUDMPCFNEFMEC SystemAPI framework,MEC Orchestrator3. Organization of MEC as an AF,4. Pertinent interactions of MEC with ionInfrastructureInfrastructureData Network(LA/DN)ServiceServiceServiceMECMEC PlatformPlatformManagerManager(R)ANAPPMEC PlatformUEN937Distributed HostHost LevelLevelDistributedN4 ETSI 2021 – All rights reservedSystem LevelSystem Level1. C-plane interactions with 5GC,2. Functional split between MEC and 5GC wrt.
3GPP enablers for MEC – Selection & re-location of UPFNSSFAUSFUDMNEFAMFSMFPCFSelection & re-location of UPFMECAFAF influence on traffic routingMobility event notificationsfrom SMFConcurrent access to local andcentral DNUERANUPFDNUPFDN ETSI 2021 – All rights reservedMEC as an AF (Application Function) can request the 5GC to Select a local UPF near 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 matchingwith the traffic filters received from MEC (AF) is diverted towards MEC hostswhile other traffic is sent to the Central Cloud38
3GPP enablers for MEC – Selection & re-location of UPFSelection & re-location of UPFNSSFAUSFUDMNEFAF influence on traffic routingAMFSMFPCFMECAFMobility event notificationsfrom SMFConcurrent access to local andcentral DNUERANUPFDNUERANUPFUPFDNIn case of UE mobility, the 5GC can re-select a new local UPF more suitable tohandle application traffic identified by MEC(AF) notify the AF about the new serving UPFDN ETSI 2021 – All rights reserved39
3GPP enablers for MEC – AF influence on traffic routingNSSFAUSFUDMNEFAMFSMFPCFSelection & re-location of UPFMECAFAF influence on traffic routingMobility event notificationsfrom SMFConcurrent access to local andcentral DNUERANUPFUPFDNDNMEC as an AF can provide the following to 5GC traffic filters identifying MEC applications deployed locallyon MEC hosts in Edge Cloud the target UEs (one UE identified by its IP/MAC address, agroup of UE, any UE) information about forwarding the identified traffic furthere.g. references to tunnels towards MEC hosts ETSI 2021 – All rights reserved40
3GPP enablers for MEC – Mobility event notificationsSelection & re-location of UPFNSSFAUSFUDMNEFAF influence on traffic routingAMFSMFPCFMECAFMobility event notificationsfrom SMFConcurrent access to local andcentral DNUERANUPFDNUERANUPFDN ETSI 2021 – All rights reservedUPFDN5GC allows MEC as an AF subscribe to UE mobility events that may affect trafficforwarding to MEC applications Receive notifications of UE mobility events affecting MECapplication instances41
3GPP enablers for MEC - Concurrent access to local and central DNSame UP session allows the UE to obtain content both from local server and central serverSelection & re-location of UPFService continuity enabled by IP address anchoring at the centralized UPF.No impact on UE in case of Uplink Classifier (ULCL) option is used.NSSFAUSFAMFUERANUPFUDMSMFUPFDNMobility event notificationsfrom SMFNEFPCFAF influence on traffic routingMECAFConcurrent access to local andcentral DNDNCentral Clouda.k.a. Conventional “internet”Edge Cloud for Ultra-low latency,high reliability services ETSI 2021 – All rights reserved42
MEC harmonized architecture with SA6 EDGEAPP Joint white paper (*) from both ETSI and 3GPP officials 3GPP TS 23.558 “Architecture for enabling Edge Applications; (Release 17)” (informative Annex C) Alignment between 3GPP and ETSI MEC is currently in scope of eEDGEAPP in 3GPP SA6 (ref. S6-211858).(*) Ref.ETSI2021White –paper:“Harmonizingstandards for edge computing - A synergized architecture leveraging ETSI ISG MEC and 3GPP specifications”, July 2020, link hereETSIAll rightsreserved43
MEC and NFVa commonapproach tomanagement ETSI 2021 – All rights reserved
MEC and NFV: MANO for the Telco EdgeMEP as a VNF:must be running for anyother VNF/app to runMEPM: EMS for MEPMEPM is (part of) App’sEMSApp can be a VNF: even ifit doesn’t know it ETSI 2021 – All rights reservedMEPM can be App’sVNFM45
MEC management: MEC-specific OperationsMm1 required APIs: Application Package Management Application Lifecycle ManagementMm3 required APIs: Application Package Management Application Lifecycle Management Application Lifecycle Change NotificationThese NFV semi-agnostic ETSI 2021 – All rights reserved Information models designed to be feasible without NFV Data models are NFV-consistent and compatible46
MEC management: MEC-NFV Interaction3 “Hybrid” Reference points identified as shown Mv3: at this point no specific changes to Ve-Vnfm-vnf areexpected (i.e. it can be used as is) Mv2: Necessary changes are being addressed by NFV IFA aspart of FEAT12 work (MECinNFV) Mv1: work identified, coordination plan is on-goingAdditionally, MEC descriptor (AppD) must be linked to NFVdescriptor (VNFD). This has been addressed as part of Rel 3work using Non-MANO artifact capability as defined in Annex Bof ETSI GS NFV-SOL 004 v. 2.5.1 and higher. ETSI 2021 – All rights reserved47
Thank you for your attention ETSI 2022 – All rights reservedFollow us on:48
EpilogueETSI ISG MEC is the leading voice in standardization & industry alignment around MECKey building block in the evolution of mobile-broadband networks, complementing NFV & SDNKey enabler for IoT and mission-critical, vertical solutionsWidely recognized as one of the key architectural concepts and technologies for 5GCan 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
Access-agnostic nature (as per MEC acronym - Multi-access Edge Computing) enabling other accesses Addressing the needs of a wide ecosystem enable multiple verticals (e.g. automotive), federations ETSI MEC -Foundation for Edge Computing News: 5GAA joined the MEC membership
IEC 61326-2-6 EN 61326-2-6 JIS C 1806-1 Radio Communications (Excluding Protocol Testing) ETSI EN 300 086 ETSI EN 300 113 ETSI EN 300 220-1 ETSI EN 300 220-2 ETSI EN 300 220-3-1 ETSI EN 300 220-3-2 ETSI EN 300 220-4 ETSI EN
ETSI NFV, which detail REST APIs for management and orchestration, can be accessed by visiting the following links - ETSI GS NFV-SOL 002 and ETSI GS NFV-SOL 003. ETSI GS NFV-SOL 004, has also been completed, it specifies the format and structure of a VNF Package and is based on the OASIS TOSCA Cloud Service Archive (CSAR) format.
NEC Labs Europe GmbH ETSI ISG CIM Chairman (Industry Specification Group Context Information Management) ETSI Board Member ETSI Delegate for: CEN/CENELEC/ETSI SF-SSCC (Sector Forum on Smart and Sustainable Cities and Communities) CEN/CENELEC/ETSI CG-Smart Energy Grid CEN/CENELEC/ET
Le MEC-A sono pompe centrifughe monogiranti ad asse orizzontale, a semplice aspirazione, dotate di un supporto a sedia ampiamente dimensionato che assicura una grande rigidità alla macchina, indispensabile per l’accoppiamento ai motori termici. Le pompe MEC-A sono frutto di una lunga esperienza di progettazione, costruzione ed
ETSI 2 ETSI GR SAI 004 V1.1.1 (2020-12) Reference DGR/SAI-004 Keywords artificial intelligence, security ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE
ETSI 2 ETSI GS NFV-SOL 003 V2.6.1 (2019-04) Reference RGS/NFV-SOL003ed261 Keywords API, NFV, protocol 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 Siret N 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la
ETSI 2 ETSI GS NFV-SOL 003 V2.4.1 (2018-02) Reference RGS/NFV-SOL003ed241 Keywords API, NFV, protocol 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
Cambridge University Press. Whittaker, J.C. 1994. Flintknapping: Making and Understanding Stone tools. Austin University of Texas Press. The following articles give a good overview of, and references about the topic: Andrefsky, W. Jr. 2009. The analysis of stone tool procurement, production and maintenance. Journal of Archaeological Research 17 .
