Edge Computing project group:

Ecosystem Investigation presentation

09 Nov 2017
Tiger Team:
BT: Milan Lalovic (prime), Maria Cuevas and Golan Murshed; B.Yond: Paul-Andre Raymond; CableLabs: Don Clarke;
Flex: Jani Dharmesh; IAB: Jeff Tantsura; Nokia: Marko Hokkanen (prime), Nurit Sprecher
Executive Summary
Ecosystem Investigation Executive Summary
Purpose of the tiger team
What is required from edge computing ecosystem that use cases can be deployed commercially on
cost efficient and short GTM way
Key learnings
Edge Computing is use case driven
ETSI MEC is the most comprehensive standard for Edge Computing deployments
ETSI MEC APIs for application developers
The standards landscape is still fragmented, need better focus and alignment.
Improvement proposals
Application Ecosystem
Lawful Interception and Charging solutions for MEC
Common MANO solution
The next steps
Use Common management
E2E Security
Agenda: How to build attractive and sustainable
ecosystem for Network Edge Applications
Vision for edge computing ecosystem
Use Cases and why edge computing is required carrier centric, enterprise
centric, 3rd party applications and End users
Identify edge computing landscape what is currently available in the
market
Identify gaps to growth of ecosystem
Edge Computing implementation in the carrier or the enterprise network
Recommendations to industry
Vision for Edge Computing
Multi-access Edge Computing: Extending the cloud to where users and objects connect

Edge Cloud means to provide data center

and data processing at the edge of the
network.
 Drivers: IoT, AI/ML, VR/AR, Data Analytics, drives low
latency/high bandwidth applications

Cloud Everywhere centralized, core, edge

Vision for Scalability from a few IoT sensors/device to Billions
Edge
Multi Access Support LTE, CBRS, Multefire, 5G, fixed
Computing
Meets Industry, enterprise and regulatory requirements

New Revenue drivers for entire telco ecosystem

Use Cases and why edge computing is required carrier centric,
enterprise centric and 3rd party applications
MEC Use Cases are ready for commercial deployments

Augmented Reality Car2X Campus LTE Edge Video Orchestration

TWICE

Surveillance cameras Object Tracking Live Virtual Reality People finder

What drives edge computing use cases carriers, enterprises, 3rd party applications

Service Providers Enterprises 3rd party Applications End User Benefits

TCO Savings Industry and Low Latency and Improved end

(transport) Enterprise IoT RTT user experience
Enterprise Private LTE High Throughput High Throughput
services and IoT networks LTE, Edge Network High Quality
Enabler CBRS, MulteFire intelligence (big Media Content
New Revenue Enhanced data, AI, ML) (4K video, VR,
opportunities Enterprise AR, MR)
networks
Recommendations to Industry
Recommendations to Industry
Security:
Security by design to prevent and facilitate rapid mitigation of physical
and virtual attacks on the integrity of the edge cloud
Management:
Limit explosion in Opex due to the number of edge cloud locations and as
Working
far as possible future proof Capex by ensuring platform has longevity and
backwards compatibility for evolving applications and software
Collectively
Interworking, Multi Domain and Multi tenant: to navigate
Avoid fragmentation across vendor, technology, domain or generation of
edge clouds. the pitfalls of
Equipment and Standards
Ensure equipment is purpose-designed for physical location of edge
Edge Clouds
instances and references standards where applicable
Making the Edge Cloud Secure
Edge Computing is the new frontier for Cloud deployment. For it to be successful it must be perceived as
secure by users and providers.
This is a topic that must be addressed jointly by ensuring security by design from the outset

Physical Security
Mechanism(s) to ensure that Edge locations cannot be tampered with or that if they are, it will be rapidly
detected and appropriate automated and/or physical measures taken.
Information Security (and privacy)
Apply standard rules and procedures to define how information needs to handled when stored or in
transit at the edge, including addressing regulatory and privacy concerns
Software and configuration security
Secure logging mechanisms to control and monitor operations on remote edge nodes.
State of the art measures for authentication and ACL
Making the Edge Cloud easy to manage
Work for a unified, extensible and automated management approach

Performance Management is important for Edge nodes in terms of latency, capacity, reliability,
assurance. Privacy has specific requirements.
Agreed Performance Benchmarks (KPIs) that all can use and measure themselves against, such as
latency, throughput, round-trip time.

Industry needs to work on defining capabilities of edge.

Agreed reference model(s) are needed
Common APIs are needed to enable own and third party developers to access the platform
Application Orchestration and Deployment mechanism
Edge Node Maintenance mechanisms
Automated fault detection and remediation and enabling deferred maintenance
Unifying Management of Multiple Edge Clouds
The edge cloud should be represented in a unified pool of resources across location, vendors, tenants,
administrative domains for management purposes
In addition the edge cloud would benefit from interworking with other clouds, hybrid clouds, telco
clouds or legacy infrastructure

Agreed reference designs and/or capabilities that span Edge, Data Centers and the network connecting
them

Methods for managing across domains, across clouds and differentiating between tenants need to be
developed.

These cannot be done in isolation and need to work across vendors, or service providers.

Application development guidelines and certification process

Equipment and Standards
Equipment needs to be purpose designed* for edge locations which
typically are not designed to accommodate IT equipment
Equipment form factor
Low power consumption
Cooling requirements
Ease of maintenance, enable deferred maintenance by self-healing and redundancy
mechanisms
Standards apply for physical equipment in network locations
Physical, safety, security, regulation
Software architectures should reference standardized frameworks to avoid
fragmentation, lock-in and to leverage economies of scale
Mapping to availability of evolving skills in the operator space,

* If MEC is installed in network edge data center in the one of transport network aggregation points, requirements are
the same as regular data center
Identify edge computing landscape what is currently
available in the market
Multi-Access Edge deployment locations per ETSI*
*ETSI MEC002 s4.4

User Equipment Radio Access Network Central Office Network Core

BSS

Internet
Distant Cloud

Edge 1 Edge 2 Edge 3

TELCO CLOUD DC Cloud

Number of Subscribers Served

10 100 1,000 10,000

Distance from Subscriber [km]
18
Existing Multi-Access Edge Computing Initiatives

GS MEC 003 GS MEC 002 TS 23.501 v1.4.0 (s5.13)

Framework and reference Proposed system architecture for

Technical Requirements
architecture 5G system
Scope definition
Functional element definition
Use case definition
Requires mobile edge services

GS NFV-PER001
OpenFog Reference Architecture
NFV performance and
portability best practices
Guidelines for ETSI OSM CORD Spec
implementation
On.Lab driven
Central Office as Edge
Multi-Access Edge Compute Standard Architecture
Application Application Application
VM VM VM

TOF RNIS Comm Registry

Application Platform Services

Virtualization Manager
MEC Application Platform

Hypervisor/MEC OS Layer

Compute Storage Power Network MEC hosting infrastructure including the

Connectivity to the radio network element
(eNB or RNC) and/or the network is beyond
Hardware the scope of the work of the MEC initiative

MEC Host Infrastructure

Multi-Access Edge Computing Ecosystem
SW HW

Applications

MEC Application Platform Platform Management

MEC Host Infrastructure: Software MEC Host Infrastructure: Hardware

23
Mobile CORD architecture (M-CORD)
M-CORD Ecosystem
Implementation Gaps in edge computing solutions
Implementation Gaps
Hard Gaps Soft Gaps
Technology Solutions Operations Go-to-Market Regulatory
Traffic congestion Application Network to MEC Monetization
Net Neutrality
management ecosystem architecture strategy
User performance Comprehensive Datacenter Multiple standards
transparency deployment package architecture exist
Integration of
Mobility
different Physical security
management
technologies
Authentication
Virtual security
protocols
Physical
maintenance
Virtual maintenance
MEC Implementation in Carrier and Enterprise Networks
MEC Implementation in Carrier and Enterprise Networks

Operators Perspectives
Explore the benefits of using ETSI MEC APIs (focus on application developers)

Explore the manageability of MEC deployments by using MANO / NFV solution (also including interfaces with OSS
functions including NMS, Security and others)

Demonstrate mission critical application deployment and performance in edge cloud using MEC

In addition, explore the benefits and viability of sharing a common NFVI between MEC Server VNF and other
edge related VNFs, such as vEPC and vRAN

Explore the applicability of Licensed, Unlicensed and shared spectrum (LTE, LTE-LAA, MulteFire, WiFi) to MEC

Develop MEC Ecosystem and provide feedback on current gaps and potential solutions
MEC Architectures and Deployment Scenario

S1 Interface
SGi

End users eNodeB EPC Internet Content

MEC Deployment Scenario
Mobile Edge
Orchestrator

Central Office
Application Developers Operator (OSS)

Mobile Edge Platform

Mobile Edge Host Manager
(MEC Server)

S1 S1
SGi

End users eNodeB EPC Internet Content

Providers
Edge Computing - Operators Perspectives (Primary)
How do I deploy my How do I deploy and
Applications onto MEC manage MEC and
Server using MEC APIs? VNF applications and
Objectives (Primary): services? Mobile Edge
Orchestrator
1. Explore the benefits of using
ETSI MEC APIs

Mm3
Apps
Central Office
2. Explore the manageability of
Application Developers
MEC deployments by using Operator (OSS)
MANO solution Mobile Edge
Platform
3. Demonstrate mission critical Manager
application deployment and
performance in edge cloud ETSI MEC APIs
using MEC

Mobile Edge Host

(MEC Platform)

Apps
Internet

S1 S1 SGi

End users eNodeB NFVI vEPC Content Providers

Edge Computing - Operators Perspective (Extended)
How do I deploy my How do I deploy and
Applications onto MEC
Objectives (Extended): Server using MEC APIs?
manage MEC and
VNF applications and
services? Mobile Edge
1. Explore the benefits and viability of Orchestrator
sharing a common NFVI between
MEC Server VNF and other edge

Mm3
Apps
related VNFs, such as vEPC and
Central Office
vRAN
Application Developers

Or-Vnfm

Or-Vnfm
Operator (OSS)
2. Explore the applicability of Mobile Edge
Licensed, Unlicensed and shared Platform
Manager
(LTE, LTE-LAA, CBRS, MulteFire,
WiFi) spectrum use to MEC
ETSI MEC APIs VNF Managers

Mobile Edge Host

(MEC Platform)

Modular RRU Apps

(LTE, LTE-LAA, MulteFire, WiFi)
Internet

S1 S1 SGi

vRAN (BBU) vEPC as VNFs

as VNF

End users eNodeB (shared NFVI) Content Providers