The Modern Telco Network: Defining The Telco Cloud

Marco Rodrigues – JuniperContrail Solutions Group

Openstack Seattle – Telcos / NFV Track

Seattle, WA (September 2016)

TelcoVNF(n)

Agenda

1. Why the Telco Cloud?2. What is the Telco Cloud?3. Telco Cloud Requirements4. A Telco Cloud Use-Case (Mobile)

Why the Telco Cloud?

Why The Telco Cloud?Current State of Affairs: IP Transport Commoditization

IP Transport (Internet) Providers

Cloud / XaaS Providers (Centralized)

The Customer Experience

InvestmentThe User: Consumer and Businesses

Why The Telco Cloud?Economics and Growth

• * Networking Facts: 1991-2015• Exponential Internet Growth, no matter what metric is used

Number of users: factor of 3 x 109

Number of devices: factor of 5 x 109

Number of web-sites: factor of 2 x 108

Number of applications: factor of 107

Total Bandwidth: factor of 5 x 107

* OFC 15 Pradeep Sindu Keynote, “The Future of Transport Networks”

Exponential growth is the clearest indication of the Internet’s value.

Why are telco’s being challenged with the continuous monetization of this value?

Customer perception of value is proportional to their immediate experience; which translates into what they’re willing to pay for.

Why The Telco Cloud?Introducing the Telco Cloud in the ’The Value Stack’

Future

SMS

Physical (Copper/Fiber /Radio)

Voice

Data (Internet / IP )

SMS

Physical (Copper/Fiber/Radio)

Voice

Data (Internet / IP)

2000s – 2010s

SMS

Physical (Copper/Fiber/Radio)

Voice

1960s-2000s

Physical (Copper/Fiber/Radio)

Voice

1900s-1990s

Services / ContentSaaS

Centralized PlatformsPaaS, IaaS, etc

SMS

Physical (Copper/Fiber /Radio)

Voice

Data (Internet / IP )

Today

Services / ContentSaaS

Centralized PlatformsPaaS, IaaS,, etc.

Distributed Telco Cloud

ValueThe Real Value:

Value Moving Up The Value Stack and away from Telco’s

Why The Telco Cloud?What’s Next

1. TCO: Reduce CAPEX and OPEX

2. Building NEW Revenue Streams: A New Platform – Telco Cloud

“API’s are fueling the software that’s eating the world and why networks are next” – Me

Why The Telco Cloud?Breaking Vendor Lock-In (Lowering OPEX and CAPEX)

APIs

Data Models

Note: Not the focus of this presentation – but worth mentioning for calibration.

Today: Centralized Public and Private Clouds

Workloads(Containers, LXC, VM, BM)

Workflow Orientated(Open API’s, Automation)

Elastic Resources(Pooled Network, Storage and Compute)

Analytics(Data Driven Delivery of Services/Content)

Centralized(Limited Distribution)

Open(OpenSource)

Workloads(Containers, LXC, VM, BM)

Workflow Orientated(Open API’s, Automation)

Elastic Resources(Pooled Network, Storage and Compute)

Analytics(Data Driven Delivery of Services/Content)

Open (OpenSource)

Future: Distributed Multi Clouds

Highly Distributed(Telco Cloud)

Applications, OTT’s and VNF’s Key Properties of a

Distributed Cloud: Physical Distribution Low Latency High Availability Network Traffic Optimization Seamless Integration of DCs

with brownfield WAN deployments

Why The Telco Cloud?Building NEW Revenue Streams: A New Platform – Telco Cloud

What is the Telco Cloud?

OpenstackNeutron & Neutron Extensions, etc.

IP or MPLS Transports

BGP L3VPN,

BGP EVPN

MPLS, VXLAN Service

Overlays

1. Physical distribution cloud resources close to Telco consumer and business eyeballs.

2. Enables applications to have:1. Low Latency2. High Availability (through

distribution)3. High volume of last mile

throughput; minimizing network wide capacity growth (choke points)

3. Seamless Integration of DC and WAN technologies leveraging existing network and operational procedures.

What is the Telco Cloud?What the hell is it?

Key Properties

~50-250

~250-1000

> 1000

Connectivity Building Blocks

WAN/METROBGP (Control Plane)

MPLS (Service)MPLS (Transport)

DC FabricBGP / OSPF (Control Plane)

IP (Transport)

+

DC OverlaysMPLS, VXLAN, IP, GRE, etc.

+

Telco Cloud

WAN METRO

METROWAN

WAN

WAN

WAN

WAN

WAN

METRO

WAN

Telco Cloud Requirements

Telco Cloud RequirementsSummary of Use-Cases (Not a Complete List)

Use-Case Functional Properties

Mobile (MPC/EPC/5G) SGW, PGW, MME, Probes, ePDG, GiLan GW, MMSC, etc

Networking (L2-L7) Edge Routing/Switching, CPE, etc.

Security Firewall, NAT, IDS/IPS, IPsec/SSLVPN, etc.

Voice VoLTE, SBC, etc.

CDN/Caching Databases, Storage, HaaS (BM), etc.

Access OLT, BNG, RGW’s, etc.

Video Content Management Transcoding, Network DVR, etc.

Telco Cloud RequirementsWhat we know about Telco Cloud VNF(s) (aka. Applications)

1. Similarity to web apps• MME, HSS, Backend Databases, Application/Business

Tiers, PCRF, etc.

2. Packet Forwarding and Manipulation• Network & Security, EPC/MPC, etc.

3. Combination of traditional Networking elements• SBC + Firewall + Load Balancing + SIP

server/management

4. CDN/Proxies5. Transformation Elements

• Transcoding/Encoding/Decoding/Encryption

What We Know

Self Service

Application High Availability

General QoS(IOPS, CPU, Resources)

Brownfield App/VNF Support (Cattle Transition)

Common Cloud and VNF Requirements

Unique Telco Cloud VNF Requirements

Low Latency / Low Jitter(i.e. Voice / Gaming / M2M / Small Packets)

High Packet Per Second Throughput (i.e. DNS, Network I/O)

Network QoS(Marking and Treatment)

Migration of HA pet to midget cow VNFs

(i.e. BGP, HA, VRRP, etc.)

Geo-Dependency of Workloads to Connections

(i.e. Service mobility and network availability)

KPI Measurements of VNF Requirements

(i.e. Rich Network Analytics)

Operational Transitions/Events (Workload and DC Dry Out)

Dynamic/Tiered Topology Creation, Scale Out and Service Chaining

Multi-tenancy(Reservation and Separation)

OrchestrationInventory, Event/Log Management, Config

Management, CI/CD/Testing, Monitoring, ITSM/ITIL/FCAPS/OSS, Probing/CALEA

1. Packet Performance, Aggregate Flows, Peak Flow Rate, Lots Features2. Scale Out Networking for Scaled Out Applications3. Brownfield Enablement (Nothing is ever green with Telco’s…)4. Communicating and Aligning on Telco's Uniqueness

Telco Cloud RequirementsSolving for Unique Telco Cloud VNF Requirements

What Telco VNFs are Asking For:• Packet Performance: (500-1K pps to 50Mpps)• Aggregate Flow Performance: (500-1K flows to 5 Million flows)• Peak Flow Rate (Creation): (500-1K fps to 2 Mfps)• Features: I want all features from the last 15-20 years.

Proposed Solutions1. Build Cloud Native (Micro/Container) VNFs

• .. and if you can’t the real question you need to answer is:• Should I be virtualizing vs. should I be automating this xNF?

2. Judicious use of SR-IOV and traditional Cloud workloads • Governance: A stern reminder to tenants still using SR-IOV:

• The barrier to entry is now removed.• Technical Co-existence

3. Moore's Law (Hardware) to the Rescue• SR-IOV workflow integration into TORs (specialized silicon)• Smart NIC offload of SR-IOV workload properties into (specialized silicon)

4. Software to the Rescue – Where Applicable • Optimized linux kernel, drivers, vR/vS, memory management, etc.

World’s Collide

Cloud Native Apps vs.

Traditional VFs (i.e. appliances)

Telco Cloud RequirementsSolving for Unique Telco Cloud VNF Requirements

• Leverage the network, protocols and tools you already have.• Example of a scale-out platform/solution:

UnderlaySwitch

vRouter

ControlNode

ControlNode

UnderlaySwitch

vRouterVM VM

IBGP

XMPP

MPLS over GRE or VXLAN

ConfigNode

Orchestrator

AnalyticsNode

SDN System

P PPE PE

RouteReflector

RouteReflector

CECE

IBGP

IBGP

MPLS over MPLS

Network Management System (NMS)

DMI

MP-BGP/BGPMPLS L3VPN / EVPN

Gateway (PE)

BGP

More details: http://www.opencontrail.org/opencontrail-architecture-documentation

Telco Cloud RequirementsScale Out Networking for Scaled Out Applications

• Physical Network Functions (PNFs) by nature are legacy and expect certain behaviors around it

• Traditional PNF vendors not incentivized to re-write/port• PNF owners (internal or external) have moved on

• Typical technology solutions needed for PNF to VNF migration:• Liveliness detection and High Availability

• PING, HTTP URI (TCP) level checks, BGP, BFD, etc.• Dynamic Insertion of Network Reachability

• Think SSL/IPSec Tunnel Termination of remote endpoints (UE’s, Small Cell Site, etc.)• i.e. BGPaaS https://blueprints.launchpad.net/juniperopenstack/+spec/bgp-as-a-service

• Live Migration of VNFs supporting legacy behaviors as a crutch• Geo Distributing VNFs where possible

Telco Cloud RequirementsBrownfield Enablement (Nothing is ever green…)

1. Documented Telco Cloud use-cases for operational alignment• OPNFV

2. Documented APIs and Data Models• Openstack• OpenConfig• IETF• OPNFV• Others..

3. Many others I’m Sure…

Telco Cloud RequirementsCommunicating and Aligning on Telco's Uniqueness

A Telco Cloud Use Case(Mobile)

IoT Platform(MVNOs, IoT LoB)

End to End Orchestration

IaaS/PaaS: Openstack & OpenContrail

Heat Orchestration (Northbound Interface)

Telco Cloud Requirements for Mobile

Telco Cloud Use-Case: MobilevEPC, GI-LAN, Line of business (LOB) IOT platform, MVNO(s), etc.

Radio Access Network

MEC CO / POP Data Centers

Telco IP/MPLS Fabric(Spine, Leafs, Gateways)

Internet

Phys

ical

Dist

ribut

ed

IaaS

Compute (x86)

Mob

ile

Apps

IPVPN

LoB

Mob

ile

Enab

lem

ent

1. Performance (Jitter, Latency, PPS per Core) 2. High Availability (HA) - Upgrades and

Service3. Multi-tenancy (5G Network Slicing) / Security4. Dynamic & Tiered Topology Creation5. Scale-Out Connectivity and Service

Chaining across various workload types.6. Service and Network Mobility7. Rich Analytics and KPIs8. Network QoS

vPro

bes

vR / Agent vR / Agent vR / Agent

vePD

G

S\P-

GW

vEPC

GI-L

AN

vMM

E

vMM

SC

Conn

ecte

d Ca

rs(C

onsu

mer

Aut

o)

Smar

t City

(Par

king

, Lam

ps, e

tc.)

MVN

Os

(Goo

gle,

App

le, A

maz

on)

Disr

upte

rs (i

nser

t IoT

alw

ays o

n id

ea

here

)

Asse

t Tra

ckin

g(F

leet

s)

Avia

tion

(Dro

nes,

Priv

ate,

Co

mm

erci

al)

Conn

ecte

d Ho

me

(Alw

ays o

n ne

twor

k re

acha

bilit

y)

Heal

th(P

atien

t Sen

sor)

Policy & Billing

Telco Cloud Use-Case: MobileA vEPC/MVNO Use Case: Functional Building Blocks and Telco Cloud Requirements

eNB

WiFi

HSS

CALEA

OCS

OFC

PCRF

AAA

Evolved Packet CoreMME/ SGSNePDG

Untrusted

P-GW / S-GW / GGSN

WAG/TWAG/Trusted

Security

PAT/NAT

Secure Tunneling

Firewall

Web Malware Protection

Content & MediaSPI, DPI

Video Adap. & MOS

HTTP Proxy / Video Caching

Content Filtering

AnalyticsProbes

(Data and Control)

Network Analytics

IP Backhaul

Heat (Northbound Interface)

Compute(s)

GILan

Medium Sized(Your mileage will vary)

~10-50 VMs across dozens of compute hosts

3-15 networks/subnets per Instance Several to Tens of Interfaces per VM ~100s of IP Endpoints Per Network Multi Tier Connectivity of various

functions Policy / Flow Level Steering to

functional blocks Scaled Out Connectivity for growth

and High Availability ~10K-100K of Flows ~10M of Packets per Second

Technical Requirements

Example Single vEPC Instance (Host Requirements)

EPC Functional Blocks

1. Orchestration• All Host Features via Heat with full API

Support

2. Performance• SR-IOV, DPDK (Mpps), Smart NIC• BM/TOR Overlay Integration• Low Latency, Jitter & QoS

3. Connectivity• Brownfield WAN (BGP L3VPN)• IP Multi-Tenancy (L3VPN)• L3/L2 Connectivity • Single and Multi Tiered Service Chaining• Network Policy (5-tuple) for flow steering• Scaled Out Load Balancing (ECMP)• BGPaaS, BFD, Static Routes, DNS, IPAM

4. Ops. and Monitoring• Rich Network & Flow Analytics / KPIs• Hardened Upgrade Processes with Low Impact

5. Security• Distributed Security Groups & Policy• Floating IP, NAT/PAT

Host

Roaming

IMS

IoT

Internet

Join the OpenContrail Communityhttp://www.opencontrail.org/

Thanks Ya’ll