Intel Labs

On-boarding a VNF, the NGIC (EPC), in M-CORD

CORD Build Event - November 7-9th, 2017 – San Jose, CA

Christian Maciocco

Principal Engineer, Director of Telecom Systems Research – Intel Labs

Ashok Sunder Rajan, Sai Edupuganti, Jacob Cooper, Karla Saur – Intel Labs

Pingping Lin, Andy Bavier, Kim Woojoong – Open Networking Foundation

Naresh Sugumar - Spirent

2

Legal Disclaimer

Intel Confidential

• This presentation contains the general insights and opinions of Intel Corporation (“Intel”). The information in this presentation is provided for information only and is not to be relied upon for any other purpose than educational. Use at your own risk! Intel makes no representations or warranties regarding the accuracy or completeness of the information in this presentation. Intel accepts no duty to update this presentation based on more current information. Intel is not liable for any damages, direct or indirect, consequential or otherwise, that may arise, directly or indirectly, from the use or misuse of the information in this presentation.

• Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service activation. Learn more at intel.com, or from the OEM or retailer.

• No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document.

• Intel, the Intel logo and Xeon are trademarks of Intel Corporation in the United States and other countries.

• *Other names and brands may be claimed as the property of others.

• © 2017 Intel Corporation.

Intel Labs3

Agenda

•Next Generation Infrastructure Core (NGIC) - vEPC VNF

•On-boarding NGIC into M-CORD

•Summary / Next Steps

Intel Labs4

• A virtual Evolved Packet Core (vEPC) VNF available at https://gerrit.opencord.org/#/admin/projects/ngic

• Research and collaborations to understand telecom workloads behavior on Intel Architecture

• Released learnings and optimized reference software into open source community (DPDK, CORD)

• S/P-GW, Cuckoo Hash for optimized lookup from collaborations with industry or academic partners

• MME, HSS, PCRF will be released later

• Investigate functionality for new usage models, e.g. Connectionless IOT, Multi-Radio Access Technologies, etc

• NGIC is not a product and will not be a product from Intel

• NGIC detailed presentation on Thursday 11/9 @ 10:00 am, Training Room #2

• NGIC hands-on tutorial on Thursday 11/9 @ 11:15 am, Training Room #2

Next Generation Infrastructure Core (NGIC)

Intel Labs5

NGIC Prerequisites for Thursday Hands-on Tutorial

• Install Docker (1.13 or higher) and Docker Compose

• Docker images for NGIC control, data plane and traffic generationdocker pull ngiccorddemo/ngic-cp

docker pull ngiccorddemo/ngic-dp

docker pull ngiccorddemo/ngic-traffic

• Demo foldergit clone https://github.com/ngiccorddemo/cordbuild2017.git

Intel Labs6

NGIC System’s Components

”Other names and brands may be claimed as the property of others”

MME

(VM)

S/P-GW-c

(VM)

S/P-GW-u

(VM)

Spirent

Application

Server

• NGIC’s system’s components running either on bare-metal, as VMs or containers

• SDN based architecture, disaggregated EPC

• Match/Action semantic data plane

• Independent and scalable control and data

• Next step: Moving NGIC under CORD environment

HSS

Future SW Release

vLSSpirent Landslide

Virtual

SW Available Today

PCRF

M-CORD: Enabling the Programmable 5G Edge Cloud

Open Source

Disaggregation

Virtualization

Cloudification

Programmability

PROGRAMMABLE 5G EDGE CLOUD

Source: Open Networking Foundation

Intel Labs8

Moving NGIC Under CORD Environment (1/2)

”Other names and brands may be claimed as the property of others”

First step: Getting familiar with CORD using CORD-In-a-Box on Cloudlab

• Pros

• Easy setup, don’t have to build a physical POD, don’t have to deal with Corporate Firewall policies

• Enables end-user to get familiar with CORD and its components

• Cons

• CORD-In-a-Box is good for small VNF but limited system resources prevented deployment of NGIC

CORD-In-a-BOX gets your familiar with CORD

Intel Labs9

Moving NGIC Under CORD Environment (2/2)

”Other names and brands may be claimed as the property of others”

Second step: Running CORD on a physical POD

• Phase-1 -- (ONS ’17)

• Using the GUI to create slices, virtual networks, instantiate the VMs

• Phase-2 -- (MWC America ’17)

• Using XOS to automate creation of slices and virtual networks (using TOSCA description files)

• Instantiate the VMs using the GUI

• Phase-3 -- (CORD Build ’17)

• Full automation using XOS to create services on top of previously created slices and networks, provide automation code to instantiate, configure and run the applications in the VMs

NGIC is a fully automated and orchestrated EPC available in M-CORD today

Build

Intel Labs10

Various models and learnings (1/3)

”Other names and brands may be claimed as the property of others”

MME

(VM)

S/P-GW-c

(VM)

S/P-GW-u

(VM)Application

Server

HSS PCRF

vLSSpirent Landslide

Virtual

Infrastructure Virtualization (Openstack)

(OvS/DPDK based)

ONOS

XOS

All System’s Components within CORD Environment

Creating a simple L2 Virtual Network connectivity when everything is orchestrated within CORD

• Default L2 Virtual Network (PRIVATE_TYPE) does additional L3 checks for anti-spoofing, e.g. de-tunneled IP packet will expose inner addresses which will be dropped

• Without this simple L2 Virtual Network the VNF must implement a NAT, could make it harder for legacy VNF

Intel Labs11

Various models and learnings (2/3)

”Other names and brands may be claimed as the property of others”

MME

(VM)

S/P-GW-c

(VM)

S/P-GW-u

(VM)Application

Server

HSS PCRF

vLSSpirent Landslide

Virtual Infrastructure Virtualization (Openstack)

(OvS/DPDK based)

ONOS

XOS

Services, e.g. eNB and Application Servers outside of CORD environment

Need L3 discovery/connectivity with outside world

• How to expose services in CORD publicly Use a PUBLIC network type to expose e.g. MME (S1-AP), S/P_GW (S1U and SGi) to outside world and automatically install forwarding rules in the fabric switches along the path from edge of the deployment to the compute node

• How to add custom routes vRouter to control routing of IP blocks not orchestrated by CORD, e.g. downlink path for UE IP addresses

vRoutervRouter

Need to have the flexibility to combine any model

Build

Intel Labs12”Other names and brands may be claimed as the property of others”

CORD Infrastructure Performance Improvements

Attend the Performance Brigade update Thursday morning @ 9am, Event Hall, to hear the details about how they improved the infrastructure throughput, by an order of magnitude, and reduce latency & jitter

We’d like to hear your feedback on next steps for Performance Improvements

Various models and learnings (3/3)

Intel Labs13

Summary / Next Steps

•A functional, DPDK based, EPC (aka NGIC) operating in bare-metal, virtualized environment or container

• NGIC orchestrated and operating in CORD

•Additional NGIC components, MME, HSS, PCRF, will be made available to CORD over time

Intel Labs14

Thank You

Intel Confidential – Internal Use Only