Multi-access Edge Computing & Openshift

OpenShift Commons Briefing | 2017.09.20 | Red Hat

Hyde SUGIYAMASenior Principal Technologist NFV | SDN | ICT Vertical

Red Hat APAC Office of Technology

Senior Principal Technologist APAC Office of Technology, Red Hat

Born in Yokohama, Age:52

Driving Technology partnership with Telco R&D and ICT Partners in Open Source NFV, SDN and Edge Computing domain.

29 years experience in the Information Communications Technology industry. (Service Providers: 14 years -> Juniper Networks: 10 years -> RedHat: 5 years)

Hyde SUGIYAMA

WHO AM I ?

2

● What is Edge Computing?

● OpenShift Edge PaaS Adoption

● OpenShift Edge PaaS PoC use case

AGENDA

3

Edge Computing

Edge Computing

2014 (http://www.ntt.co.jp/news2014/1401e/140123a.html): NTT R&D announced an Edge computing technology concept which can reduce the cloud application response time by factor of 100 at most, and demonstrated its first research outcome, the “Edge accelerated Web platform” prototype.

Open Fog Consortium

2015: Cisco, ARM, Dell, Intel, Microsoft and Princeton University established OpenFog Consortium to promote and accelerate adoption of open fong computing.

Mobile Edge Computing

2015: ESTI MEC ISG; Edge computing by placing compute resources on the edge of mobile network. ISG Name has been changed to “Multi-access Edge Computing” in 2016.

Automotive Edge Computing

2017: DENSO, Ericsson, Intel, NTT and Toyota have initiated the formation of the Automotive Edge Computing Consortium which is tasked to develop an ecosystem for connected cars. It aims to support emerging services such as intelligent driving, the creation of maps with real-time data and driving assistance based on cloud computing.

4

MEC / Edge ComputingBefore

5

IoT Edge devices, Automotive Edge

devices, Mobile UE, Home Gateway and

etc

Cloud & Big Data Center

Telco’s Network Service

IoT Edge devices, Automotive Edge

devices, Mobile UE, Home Gateway and

etc

MEC / Edge Computing

Cloud & Big Data Center

6

Edge Computing in Telco Central Offices

■ Reduce Latency and bandwidth ■ Data caching■ Data pre-processing ■ Real-time CEP ■ Industrial IoT, V2X■ Video analytics service■ Optimized local content distribution

service■ Integration of Ent cloud service■ etc3rd Party’s AE(Application Entity) /CSE + SP’s CSE(Common Service Entity) + Telco’s NSE(Network Service Entity)

Telco Central Office (CO)

Central OfficeFixed Cu

(xDSL, HFC)

Fronthaul/Access

AggregationNetwork(s)

Metro/Core NetworkIP/MPLS/Optical

Fixed Optical(xPON, WDM)

Fixed Wireless(WiFi,... )

Mobile( 4G, 5G... )

Location Sensitive“Fixed” Subscribers

Location Insensitive“Mobile” Subscribers

Site

/ Lo

catio

nS

peci

fic N

etw

ork

AA

A D

evic

e / S

ubsc

riber

Spe

cific

Net

wor

k A

AA

RRH BBU

BNGOLT

BBUBBU Mobile Packet Core

CoreNetwork

MNO’s CO

FNO’s CO

CORD / Virtual CO7 MNO: Mobile Network Operator RRH: Remote Radio Head BBU: Base Band Unit CORD: CO Architected as Datacenter

FNO: Fixed Network Operator OLT: Optical Line Terminal BNG: Broadband Network Gateway

Telco nodes

http://denwakyoku.jp/

Base StationOutdoor in rural area

Typical Central Office Base Station in Urban area

8

CO deployment options

Micro Pod Mini Pod Small Pod(Typical Central Office)

Rack space

Self contained – ½ rack of equipment with Compute – xx CPUs, Storage – Up to 10 TB of local storage and Network connectivity – WAN (Ethernet) 2 x 10GE ports (Hyper-converged node)

Self contained – 1-2 rack(s)of equipment with Compute – xx CPUs, Storage – Up to 20 TB of local storage and Network connectivity – WAN (Ethernet) 2 x 10GE ports

Self contained – 5-10 rack(s)of equipment with Compute – xx CPUs, Storage – Up to 50 TB of local storage and Network connectivity – WAN (Ethernet) 4 x 10GE ports

9

Central Office (CO) hierarchical design

Customer siteDistributed CO

(Edge mini/micro DC)

Big Data Center

Consolidated CO(Core small DC)

Access MetroCore

Network

~2..20+ locations~10’s..100’s + locations~1k..10k’s locations~10..100k’s locations

BBU hosteling

Centralized RAN/Cloud RAN

CPRIFronthaul (20km .. )

RRH

10

( < 4km ) ( < 20 km consolidated optical ) < 100 km two-tier ( < 1000 km to closest)

MobileBackhaul

EPC in Main CO

RAN: Radio Access Network RRH: Remote Radio Head CPRI: Common Public Radio Interface BBU: BaseBand Unit EPC:Evolved Packet Core

Edge server co-location site is CO

11

Virtual Central Office demo at OPNFV summit

12

Fixed Network Operator’s Edge PaaS solutionDevOps

Use cases; ● IoT Robotics● V2X● Video Analytics● AR● SmartCity● etc

Many open sources and Enterprise partner’s applications

13

Framework and Reference Architecture (ETSI GS MEC 003)

14Deployment of MEC in NFV environment (ETSI GS MEC 017 draft)

MEC Server

Containerized enterprise application challenge for MEC in NFV environment

15

Edge PaaS possibility in Mobile(4G LTE Advanced Pro)

16

Mobile Edge Platform + Openshift on

OpenStack Platform

GiLAN / MVNOMobile Core site

Enterprise Service Domain

S1 interface

Edge PaaS possibility - Edge Termination(4G LTE Advanced Pro)

Mobile Edge Platform + Openshift on

OpenStack Platform

17

GiLAN / MVNOMobile Core site

S1 interface

Flexible architecture for Multi-access Edge PaaS

DevOps

Use cases; ● IoT Robotics● V2X● Video Analytics● AR● SmartCity● etc

Many open sources and Enterprise partner’s applications

18

19

AService

Service

Service

vBNG

SDN-C/VNF-M

NFVI

Fixed Network Operator

Ingress enhancements for Edge PaaS

A

A

A

A

A

AService

Service

Service

MEP

SDN-C/MEP-M

NFVI

Mobile Network Operator

A

A

A

A

A

NODE1

NODE2

NODE1

NODE2

Edge Computing across multi-COslike a single DC

Containersin Pod

Customer site Data Center

RRH

20 Distributed edge sites Core site

(Edge DC) (Core DC)

Service 1Service 2

vCPE: BNG, FW, Elastic Load Balancer, etc CSE in Infrastructure : IoT GW, AAA, etcUser’s AE: IoT Robotics controller

CSE(Common Service Entity)AE(Application Entity)

NTT NT Lab’s Edge PaaS PoC - IoT Robotics(ongoing)

21

Carrier Edge PaaS strategy for Cloud Native serviceby NTT NT Lab & Red Hat

http://openshiftgathering.com/openshiftgathering/austin?

22

https://github.com/redhat-iot/iot-assettracking-demo

Potential Edge use case: Eclipse IoT projects

https://www.eclipse.org/hono/deployment/openshift/

NFVI/MEChttps://developers.redhat.com/blog/2017/06/06/iot-hackathon-codestarter-red-hat-summit/

23

Potential Edge use case: Connected Car 5G session at MPLS2016http://mpls.jp/2016/presentations/MPLS-Japan2016_Onishi.pdf4G: Centralizing Big Data Center 5G: Exploring for Edge Computing deployment for Geo distribution

24

10 exabytes per month around 2025

25

Edge PaaS in Red HatNFVStack

AE: Application EntityCSE: Common Service EntityNSE: Network Service Entity

CSE CSE

AEAE(NSE) (NSE) (NSE)

Smart NIC

Key Takeaways● Keep flexible architecture in Telco Edge infrastructure by

enhancing Ingress controller, in addition to Cloud infrastructure (AWS, GCE, Azure)○ OpenShift on OpenStack NFV in Mobile Network

Operator’s Edge Computing infrastructure○ OpenShift on OpenStack NFV in Fixed Network

Operator’s Edge Computing infrastructure

● B2B2X Cross-industry collaboration platform○ NTT NT Lab’s Edge PaaS strategy session at OpenShift

Commons Gathering, Dec 5th | Austin TX26

Q&A

hyde@redhat.com

THANK YOU

facebook.com/redhatinc

twitter.com/RedHatNews

youtube.com/user/RedHatVideos

plus.google.com/+RedHat

linkedin.com/company/red-hat