SCF Partners' Day: ETSI Multi-Access Edge Computing
-
Upload
small-cell-forum -
Category
Technology
-
view
508 -
download
4
Transcript of SCF Partners' Day: ETSI Multi-Access Edge Computing
§ Proximity§ Ultra-lowlatency§ Highbandwidth§ Real-timeaccesstoaccessnetworkandcontextinformation§ Locationawareness
Cloud-computingatthenetworkedge.
WhyEdgeComputing?
2
… as in Real Estate, it’s about just 3 things: Location, Location, Location
WhatCanWeDoattheEdge?
QualityofExperience
Contextualizedservices
EfficientutilizationoftheRadioandtheNetworkresources
Innovativeapplicationsandservicestowardsmobilesubscribers,enterprisesandverticalsegments
3
Real time Interactive Analytical Security and privacy Distributed
Businesstransformation
Amyriadofnewusecases
Widercollaborationcanhelptodrivefavorablemarketconditionsforsustainablebusinessforallplayersinthevaluechain.
NewEcosystem/ValueChain
MEC(Multi-Access EdgeComputing)BusinessBenefits
Newmarketsegments(enterprises,verticalsandsubscribers);
shortinnovationcycle;
revenuegenerationanddifferentiation
Videoacceleration,augmentedreality,connectedvehicles,IoTanalytics,enterpriseservices,networkperformanceandutilizationoptimization,retail,eHealth,etc.
4
ETSIMulti-Access EdgeComputing
PioneeringopenstandardsforEdgeComputing• Since2014• Firstandstillonlyinternational
SDOfocusedonthisspace
LeadershipacrossEcosystem
:
BroadParticipation
ETSIMECISG:WhatDoWeSpecify?
6
CRAN
IOT
CONN.
CARS
VR
AR
We don’tmake 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
ETSIMECISG:WhatDoWeSpecify?
7
CRAN
IOT
CONN.
CARS
VR
AR
ETSI MEC
Virtualization Infrastructure
Management Orchestration
SVC
SVC
SVC
API API APIAPI API
API
API
e.g. MANO Services, Application LCM
Key Operator Services…
Platform Functionality
Application Enablement
Let’sMakethisMoreSpecific
8
Based on use case drive Requirements Spec (MEC 002)
We defined an architecture (MEC 003)
Radio Network Information Service
(MEC 012)
Location Service (MEC 013)
UE Identity Service(MEC 014)
BW Mgmt Service(MEC 015)
Platform Mgmt(MEC 10-1)
App. LCM (MEC 10-2)
API Rules for MEC APIs (MEC 009)
App. Enablement (MEC 11)
…andunderstandourscopeaspartofabiggerMECeffortintheindustry
9
OpenStack (FEDMC WG)
OpenFlow
3GPP
RAN
OEC
Including,Critically,ETSINFV
10
CFSportal
UE app User appLCM proxy
Operations support system
Mobile edge appli-cation orchestrator
(MEAO)NFVO
Mobile edge platform manager - NFV
(MEPM-V)
ME app rules &
reqsmgmt
ME platform element mgmt
ME App (VNF)
Service
Data plane NFVI
VNFM (ME
platform LCM)
Mp1
Mx1
Mx2 Mm8
Mm9
Mm2
Mm1
Mm3*
Mv1
Mv3
Mp3
Nf-Vi
Mm5
Vi-Vnfm = Mm6
Virtualization infrastructure manager
Os-Ma-nfvo
Or-Vnfm Or-Vi
Ve-Vnfm-vnf
Ve-Vnfm-em
Nf-Vn Nf-Vn
Mv2
Mp2
NFVreference points MECreference points MEC-NFVreference points
Mv1 – related to Os-Ma-nfvo Mv2 – related to Ve-Vnfm-em Mv3 – related to Ve-Vnfm-vnf
Other mobile edge
platform
VNFM(MEappLCM)
Mobile edge platform(VNF)
* Based on draft of GR MEC 017
Let’s reflect on the work status…
Published§ TechnicalRequirements,includingusecases(MEC002)
§ FrameworkandReferenceArchitecture(MEC003)
§ MECProofofConcept(PoC)Process(MEC-IEG005)
§ ServiceScenarios(MEC-IEG004)§ Metrics(MEC-IEG006)§ APIFramework(MEC009)§ ManagementAPIs(MEC010-2)§ ApplicationEnablement(MEC011)
§ ServiceAPIs(MEC012,013)
ComingSoon§ ManagementAPIs(MEC010-1)§ ServiceAPIs(MEC014,015)§ UEApplicationInterface(MEC016)
§ StudyonNFVAlignment(MEC017)
§ StudyonMobilitySupport(MEC018)
End 2014 End 2016
ETSI MEC phase 1 ETSI MEC phase 2
Phase2§ EvolutionofPhase1andclosingopenitems
§ LawfulIntercept§ Charging§ Mobility
§ NormativeworkforintegrationwithNFV
§ From“Mobile”to“Multi-Access”§ Wi-Fi§ FixedAccess
• FromVMstoContainers• Developercommunityengagement• Supportingpartnerorganizationsastheymovetowardsdeployment
We’ve come a long way in just 2 years!
But there is so much more to do!
OpenAPISpecification:APIdescriptionfiles(akaSwaggerSpecification)
OpenAPISpecification• Opensourceframeworkfordefining&creatingRESTfulAPIs• OpenAPISpecificationcompliantAPIdescriptionfile
• InherentlyincludesMECdatastructuredefinitions• Machinereadablefacilitatingcontentvalidation• Allowsautocreationofstubsforbothserviceclient&server
MotivationwithISG• Specificationaccessibility&validation• Accessibility→Wideradoption:3rd partydevelopers• Adoption→Criticalreview&feedbackWherewearenow• ETSIRepositorytargetedforMay2017• MEC-12,MEC-13&MEC-16availableFuturePlans• CompletesetofAPIsavailableviaETSIRepository• Currentlyexploringotherapproachestowardsamoreextensiveengagementwith
thedevelopercommunity.
13
https://www.openapis.org/
Iwanttohelp,whatcanIdo
First,jointheISG.YoudoNOThavetobeanETSIMember• Talktousaboutthedetails
IamaTelcoIndustryOperator/VendorandwanttoseeEdgeClouddeployed• Great,helpusdesignandstandardizeaworld-classserviceframework
IamanApplicationDeveloperandneedmyappstorunattheedge• Great,helpusmakewhatwedidavailable forotherdeveloperstouse
IamanInfrastructureVendororaSystemTest/Integrator• Great,comehelpdevelopProofofConceptsforthemostinnovative5Gsystem
IamanIndustryOrganization andneedEdgetoenablemytargetmarket• Great,wewanttopartner withyoutoenableyourtargetmarket
14
Areas of MEC/SCF Cooperation:• Active contribution by common membership• As a partner, SCF can contribute directly!• Proven track record of cooperation:
• MEC 013 (Location): essentially adopted SCF APIs (via OMA) (but first determined SCF work fit our needs)• MEC 014 (UE identity): initiated as a result of LS from SCF (but needed company efforts to see it through)
• NOW!!! is the best time to influence direction of Phase 2 – we are in the middle of Use Case and Requirements development for Phase 2
Joint Plugfests are a mutual benefits: Small Cell vendors demonstrate their product capabilities in MEC using standardized APIs, while ETSI MEC highlights industry adoption
Usage of ETSI MEC Specification in SCF Solution White Papers, Plugfests, potential certification efforts?
Injustover2yearsofactivityETSIMECISGgainedsignificantmomentumandisacceleratingtheindustry
Keybuildingblockintheevolutionofmobile-broadbandnetworks,complementingNFVandSDN.
KeyenablerforIoTandmission-critical,verticalsolutions.
Widelyrecognizedasoneofthekeyarchitecturalconceptsandtechnologiesfor5G.
Canbeusedtoenablemany5Gusecaseswithoutafull5Groll-out(i.e.with4Gnetworks)
Enableamyriadofnewusecasesacrossmultiplesectorsaswellasinnovativebusinessopportunities.
•TheworkonRelease2willextendtheapplicabilityoftheMECtechnologyandrendertheMECenvironmentevenmoreattractivetothird-partyapplicationdevelopers.
Epilogue
15
THANKYOU
Chair:AlexReznik,[email protected]:PierreLynch,[email protected]:ChantalBonardi,[email protected]
16
Thankyou!
ContactDetails