Future Broadband Network Virtualization Cloud Central … Broadba… · · 2018-03-23Huawei...

Future Broadband Network

Virtualization

– Cloud Central Office

Huawei Technologies Co., Ltd. | 2

Contents

• Challenges of current rigid network and transformation towards Cloud-centric network

• The High-level Cloud CO architecture

• Huawei’s understanding on Cloud CO components

• “PNF network” abstraction, slicing and centralized control for multi-access, multi-tenancy

and e2e underlay network

• VNF/VNFC diversity and use cases

• Overlay networking and I/O technologies in NFVI

• Domain abstraction, autonomy and assurance

• Open Ecosystem

• Huawei Vision

• Summary


Challenges of Service Provider

Access Metro BackBone

Hyper-scaleCloud

ONT

CPE

CSG

OLT BNG

PE

RSG IMS

EPC

CRInternet

Mobile

Consumer

Enterprise

• Linear growth of CAPEX&OPEX with expansion of

network

• Slow response for service requirements and long

TTM for new services

• Low utilization and efficiency of network resourcesSkill dependent

troubleshooting

Coupling between Service

and Network

Device-centric & Manual

Operations

with fragmented networks

Invisible & complaint-driven user experience mgmt.

Root Causes

Small CO(~thousands)

Medium CO(~Hundreds)

Large CO(~dozens)


Network & Service Decoupling Brings Huge Benefits to OTT

VS

~ 100 Devices / person in Telco-S network

~ 28 weeks Private Line Service Provisioning

CAPEX 60% Traffic Double Growth

• Network & Service coupling into dedicated HW, difficult to scale out

• Network change with service, difficult to scale up independently

• 30+ protocols, high experience requirement

• Low efficiency by Manual O&M , 80% fault via configuration errors

ASG

PE

SR

BRAS

B2C

B2B

B2H

Service Functions

Transport Functions

Metro NetworkData Center Network

Network

VM VM VM VM

WEB FW APP DB

ServiceVM

WEB

~ 3000 devices / person in Hyper-scale DC

~ 4 hours OTT New Service Provisioning

CAPEX 10% Traffic Double Growth

• Network & Service Decoupling, network is service agnostic

• Spine/Leaf Arch.，elastic scale out，any to any non-blocking

• Simplified protocols, reduce O&M experience requirements

• Automatic service provisioning, O&M visualization


Advantage and Opportunity of Service Provider



Hyper-scaleCloud

ONT

CPE

CSG

OLT


BNG

PE

RSG

Large CO(~dozens)

IMS

EPC

CRInternet

Mobile

Consumer

Enterprise

App AppApp

<10ms <20ms <50ms nondeterministic

• Physical infrastructure close to users is the operator's greatest advantage and assets

• More and more services need delay and bandwidth guarantee to enhance their experience and quality

• Building an open telecom cloud based on CO is the biggest opportunity for operators

• Telecom Cloud first considers network services, and then opens up and builds a telecommunication cloud IAAS. What are the characteristics

of such a telecom cloud? What kind of architecture and design considerations are needed?

Virtual Overlay Network

and

Distributed IAASvCPE

vPE vBNG vIMS vEPC

App AppApp


CloudCO ArchitectureEnd-to-End Service Orchestration /OSS/BSS/Portals (Assurance, … ) (#)

CloudCO Domain Orchestrator

NFVI

Compute Storage Network

Virtual Compute

Virtual Storage

Virtual Network

Virtualization LayerVIM

CloudCO North Bound API(s)

CloudCODomain

PNF VNF VNFM

EMS (#) DC SDN Mngt & Ctrl

VNF SDN Mngt & Ctrl

PNF SDN Mngt & Ctrl

NFVOMCO EngineSDN Management & Control

From BBF TR384

PNF Network

NFVI Network

Domain Orchestrator

VNF


CloudCO -- PNF NetworkEnd-to-End Service Orchestration /OSS/BSS/Portals (Assurance, … ) (#)


NFVI


Virtual Compute

Virtual Storage

Virtual Network



CloudCODomain

PNF VNF VNFM


VNF SDN Mngt & Ctrl

PNF SDN Mngt & Ctrl


From BBF TR384

PNF Network


PNF Network Understanding

CSG

CPE

OLT PE/LSWONT

DPUCPE

PE

PE/BNG-U

Cloud COPOP

MetroCO

AccessCO

OLT

MetroCO


PNFPNF

PNF SDN

Mngt & Ctrl

Cloud COCORE

PE/CR

PNF SDN

Mngt & Ctrl

P/LSW

Focus on PNF SDN “network automation”,

No only devices within CO


Broadband Access Abstraction enabling

NaaD (Network as a Device) and OPEX reduction

Sites × 1 Sites × 10 Sites ×100

Sites ×1000

VDSL/Vectoring/G.fast:

~500M@100~300m

G.fast:

~1G@10

0m

VDSL/Vectoring:

~100M@300~500

m

ADSL:

~16M @1~5km

FTTB

VDSL/Vectoring/G.fast:

~500M@100~300m

FTTD

G.fast:~1

G

@100m

FTTC

VDSL/Vectoring:~1

00M

@300~500m

CO

ADSL:

~16M

@1~5k

m

Access Network Evolution Challenges:

• Management Complexity

Multi-Access media: DSL, PON, Active ETH, HFC etc.

Multi-Access devices: DPU, ONU, OLT,

CMC,CMTS/CCAP, CPE, Access Router, and etc.

• Migration Difficulty

How to migration from VDSL->Vector->G.fast->FTTH

Proposed Solution:

• M & C plane centralized to SDAN controller through BAA

without impacts on OSS

• Applications running on top of BAA: vAN, vCCAP, vCPE,

vCDN, vQAM…

DSL

DIstributed

CCAP

FTTDp

DPUBAA

Cable

Fibre

CMC

vAN vCCAP

5G

IoT

CSG

ONT

OLT

vAN 1

vCCAP

vAN 2

PNF SDN Mngt & Ctrl

Physical

Access

Device

View

...

ONT CMC DPU OLT

Virtual

AN

View


BAA enabling network slicing and new business model

Physical Deployment SP’s logical network view

Virtual network 1

Virtual network n

ONU slice k…nk OLT slice k

Wholesaler

ONU slice 1…n OLT slice 1

open API

Current Wholesale Network as a Service

Pipe wholesaling Multi-tenancy with virtual network

Only BW different, but services similar Self-defined services for different tenant’s network

Fixed network planning Network planning on demand

Unbundling/Bit stream NaaS

Retailer

VNO1

VNO k

ONU 1

ONU n

OLT

…


SDN-PNF : Centralized Control E2E Underlay Network



Large CO(~dozens)

Virtual Overlay Network

and

Distributed IAASvPE

vBNG vIMS

vEPC

Metro and Backbone

ONT

CSG

OLT

CPE

Physical Underlay Network

MPLS

Solution

SR/EVPN

Solution

VLL

L3VPN

VPLSEVPNSegment Routing

Tunnel: RSVP-TE/LDP/GRE/L2TPv3/PPTP… -> SR

VPN: VLL/VPLS/L3VPN…-> EVPN

• >10 complex protocols

• >6000 command line, manual O&M

• >28 weeks provisioning period with

section by section configuration

• 10+ Protocols -> 2 Protocols

• E2E seamless automatic provisioning

& path optimization

• Provisioning period week->hour

• SRv6 for IPv6-oriented evolution

VLL

L3VPN

VPLSQinQ GRE BGP RSVP-TE BGP LDP

SDN

Controller


CloudCO -- VNFEnd-to-End Service Orchestration /OSS/BSS/Portals (Assurance, … ) (#)


NFVI


Virtual Compute

Virtual Storage

Virtual Network



CloudCODomain

PNF VNF VNFM


VNF SDN Mngt & Ctrl

PNF SDN Mngt & Ctrl


From BBF TR384

VNF


VNF@CloudCO Use Case- IMS & EPC

NFV has been adopted in Wireless CN first：

1、IMS and other network functions rely on high computing capability and is easy to transform from dedicated

HW to software based-on COTS server

2、Major VNF are deal with session, same as IT application and relatively easy stateless transformation，EPC is different.

3、Rich service with frequent change

4、High Ntwk layer location, and easy to get the scale effect

5、Commercially available

Cloud for all functions in Core

MANO

NFVO

VNFM

VIM

Cloud OS

DC2 DC1

Cloud

IMS

Cloud

EPC

Other

VNF

Wi-Fi

NB-IoT

Unlicensed

2/3/4/5 G

Access & Metro

Ntwk


VNF@CloudCO Use Case-2B

Solution:

1、Deploy VPN-GW at CO/POP to provide VPN services, connect and

coexist with underlay VPN such as MPLS

2 Virtualize VPN GW is FW VNF and totally different with IT appl:

1）extremely high forwarding performance

2）Pass-through traffic, SA and DA not in DC. VNF is not endpoint and

require many routes outside DC

3）Routing and Forwarding consistent and reliability

Telco 2B services:

Main feature:

1、High ARPU

2、BW high per user but total BW is much less than residential

3、High QoS compared with residential

Challenge:

1、Provisioning too long(about 28 weeks)

2、Not cover all sites of enterprise by one Telco

Cloud OS

DC

vFWVPN-

GWvNAT

Cloud OS

DC

vFWVPN-

GWvNAT

AN&Metro or Barer Ntwk

CloudCO CloudCO

CPE

CPE

CPE

CPE

CPE

CPE

Enterprise SitesEnterprise Sites

Overlay VPNOverlay VPN

Lease Line Lease Line


VNF@CloudCO Use Case-2C vBNG

DHCP

Cloudified Architecture

EMSDHCP

Traditional Architecture

BRAS BRAS BRAS BRAS

EMS

Huge Amount Subscribers, Ultra High Bandwidth,

But Low ARPU

BNG-CP

BNG-UP

CloudCO

X86 Servers Dedicated Hardware

Centralized Control Plane @ Cloud• Improve control plane performance & scalability,

solve CP resource problem.• Sharing control plane resource with multiple

UPs , improve efficiency.• Centralized service provision point to a single

CP, simplify O&M.

High performance User Plane• Ultra high bandwidth but low ARPU, Dedicated

Hardware vs VNF.• Reuse existing BNG hardware, protect

investment


VNF@CloudCO Use Case-2C vRG

SLA

Network

Internet

Service

ParentKids IOTs

OTT

3rd party

Cloud

OLT

ONT (pRG)

NFVI

VAS

Cloud

CO

BNG-U

Metro

vRG

Best Effort

Network

MCA SecurityPolicy

Route

Cache

vRG-CvRG-CvRG-CvRG-CvRG-C

vRG-U

Container based

VM based

vRG : Anchor Point for Residential Value Add Service

• Enrich service for residential customers to increate ARPU

• Traffic dispatch on service demand & policy to improve

experience

• Open environment for integrate 3rd party Application. • Centralized management, control and analysis to simplify

O&M

Challenges• Business: cost sensitive, trivial requirements, killer app?

• Technical: 1000s containers within one server, lifecycle

management & HA

How to raise ARPU of

residential service


VNF@CloudCO Use Case-More

vCDN

vSTB

IOT

5G

AR/VR

V2X

…

NFVI

CloudCO

vBNG vRGvGW …


VNF\VNFC Diversity

Hybrid type VNF

Differences in service features of VNF processing：

1、Management/control/signaling services:

The VNF acts as an Endpoint.

2、Traffic forwarding type service:

VNFs process pass-through traffic, forwarding will consume a lot of

computing resource.

Different types of VNF/VNFC have different

requirements on NFVI

Different types of VNF/VNFC based on the service features:

1、 VNF/VNFC processing management/control/signaling

2、 VNF/VNFC processing traffic forwarding services

3、 VNF/VNFC simultaneously processing both

management/control/signaling and traffic forwarding services

VNF/

VNFC

10.11.100.4

Endpoint

Type VNFC

Payload 10.11.100.4 10.10.23.15

10.11.100.4 10.10.23.15 Payload

VNF/

VNFC

10.10.23.15

10.11.10.5 61.101.1.30Payload 10.11.10.5 61.101.1.30

Endpoint Endpoint

VNF/VNFC vIMS vEPC VPN-GW vBNG-C vBNG-U VRG

Endpoint

Type

Y Y Y Y - Y

Forwarding

type

- Y Y - Y Y

Endpoint

Type VNFC

VNF/

VNFC

Forwarding

type VNFC

Forwarding

type VNFCHybrid type

VNFC

Hybrid type

VNFC


CloudCO – NFVI NetworkEnd-to-End Service Orchestration /OSS/BSS/Portals (Assurance, … ) (#)


NFVI


Virtual Compute

Virtual Storage

Virtual Network



CloudCODomain

PNF VNF VNFM


VNF SDN Mngt & Ctrl

PNF SDN Mngt & Ctrl


From BBF TR384

NFVI Network


Different I/O technologies for VNF/VNFCs

VNF/VNFC VNF/VNFCVNF/VNFC

DCN Fabric

Host OS

VMVM VM

vSwitch(DVR)


Host OS

VMVM VM

SR-IOV


Host OS

VMVM VM

NIC NIC Smart NIC

vSwitch

Throughput VM Mobility Standardization Route coupling ApplicableVNF/VNFC

vSwitch Low(<10Gbps) High High Y Endpoint Type

SR-IOV High(10-100Gbps) Low High N Traffic forwarding type

SmartNIC High(10-100Gbps) High Low Y Endpoint Type?

•The same VNF is often composed of Endpoint-type, traffic-forwarding VNFC. NFVI must support both vSwitch and SR-IOV.

•The Smart NIC is the direction of the forwarding function offload in the future. It mainly offload vSwitch. Is it possible to offload

VNF functions in the future?


DCN Fabric（IP）

DCN Fabric

NFVI Overlay Networking---VXLAN

VNF/VNFC

vSwitch

VNF/VNFC

DCN Fabric（IP)

vSwitch

VNF/VNFC

VNF/VNFC

vSwitch-based VXLAN networking：1、Overlay and underlay (DCN network) completely decoupled, VNF / VNFC can be

dynamically migrated (IP unchanged)

2、 Suitable for Endpoint type VNF/VNFC : vSwitch only needs to handle the routing of

VNF/VNFCVXLAN

VNF/VNFC

TOR

VNF/VNFC

TOR

VNF/VNFC

VNF/VNFCVXLAN

TOR-based VXLAN networking ：1、 Relatively higher performance than vSwitch, but coupled with DCN network,

VNF/VNFC dynamic migration requires DCN network cooperation

2、 Suitable for Endpoint type VNF/VNFC : TOR only needs to handle the routing of

VNF/VNFC

SDN Controller

VNF/VNFC

VNF/VNFC

DCN Fabric

VNF/VNFC

VNF/VNFCVXLAN

VNF-based VXLAN networking ：1、 The overlay is fully decoupled from the underlay (DCN network) forwarding, but the

dynamic migration of VNF/VNFC requires publishing the VTEP address to the DCN

network.

2、Suitable for forwarding VNF/VNFC for high forwarding performance

SDN Controller

vSwitch

VNF/VNFC

VNF/VNFC

TOR

VNF/VNFC

VNF/VNFC

SDN Controller

VNF/VNFC VNF/VNFC

Hybrid Mode •Applicable to different scenarios

•Unified SDN Controller Manages

VXLAN Network


Deployment environment for VNF/VNFC ：VM & Container

•Currently VNF/VNFC is mainly deployed based on VMs. VMs can meet the

needs of most VNFs.

•Future VNF/VNFC will be deployed based on a mixed environment of VMs and

Containers. Coexistence of VMs and Containers should be supported.

•Partial Endpoint type VNF may evolve to pure Container deployment

•NFVI VIM needs to support unified management of VMs and Containers

VNFC

VMVM VM

VNF

VNFC VNFC

VIM(OPS)

VNFC

VMVM

VNFVNFC

Container

VNFC

Container

VNFC

VM

VNF

VNFC

Container

VNFC

Container

VNF

VNFC

Container

VNFC

Container

VNFC

Container

VIM(OPS + K8S)


CloudCO – Domain OrchestrationEnd-to-End Service Orchestration /OSS/BSS/Portals (Assurance, … ) (#)


NFVI


Virtual Compute

Virtual Storage

Virtual Network



CloudCODomain

PNF VNF VNFM


VNF SDN Mngt & Ctrl

PNF SDN Mngt & Ctrl


From BBF TR384

Domain Orchestration


Domain Abstraction Reduce Integration Complexity

NFVI

E2e SO


S-VNFM

VIM

PNF

Controller

DC

Controller

VNF

Controller

VNFPNF

NG OSS

Service Model

Abstract network Service model and state-independent interface

Good Model layering eases CloudCO and OSS integration

1

Complexity hiding via CloudCO Domainabstraction：1、simplify interoperability issue between CloudCO and OSS；2、unaware of domain product change or upgrade；

NB API：~20

SB API:~100

NG OSS(e.g.SDN Controller)

Model-Driven

Vendor1 PNF/VNF Vendor k PNF/VNF

• Multi-vendor Interoperability challenge

• Solution：1. Management and control plane layering: decouple operator OSS and vendor specific domain controller, S-VNFM and interface；2、Model layering: decouple service model, network model and vendor specific model

Cloud CO Domain

Vendor specific

Model and interface

Vendor specific

Model and interface

2


CloudCO – Assurance & Analyzer End-to-End Service Orchestration /OSS/BSS/Portals (Assurance, … ) (#)


NFVI


Virtual Compute

Virtual Storage

Virtual Network



CloudCODomain

PNF VNF VNFM


VNF SDN Mngt & Ctrl

PNF SDN Mngt & Ctrl


From BBF TR384

Assurance & Analyzer


Challenge for Assurance of CloudCO Network

Root Cause Classfication of Service Fault in DC

Configuration Error ofNetwork(43%)

Bug of HW/SW(20%)

Abnormal of ITInfrastructure(30%)

ResourceExhaustion(7%)

30%

Aware via

traditional

approaches

70%Unaware via traditional approaches

Abnormal

Traffic:

3.65%

Issues of service&experience perspective

Connectivity(70%):Interrupt of service

Performance(20%):Bad experience ofservice

Policy(10%):Abnormal serviceaccess

•Lack of data for fault cause analysis• Not coverage completely from chipset, device, network, IT infrastructure, flow and applications• Low sampling frequency, min -> ms;• Lack of historic data, >90% does not support fault playback

•Unaware of abnormal application and network status, majority faults are detected passively•Lack of capability to correlate the issues between network and applications•Capability to predictive resource exhaustion(<7%), bugs of HW/SW(<20%), configuration error(<43%)

Data from some real typical medium DC(5300+ VM, 65 subnet)

Average number of flow:96,545,774/day，among them 3,543,230(3.67%) are abnormal


Data Analyzer improve the assurance of Central CO

Data AnalyzerReal-time data-driven

TraditionalAfterward event-driven

Static topology-based,

focus on device linksDynamic path-based,

focus on app flows

App-oriented black box

network, focus on

management plane

Chipset, Device, Path, and Flow

Flow State DatabaseApp flow, real-time status, and

behavior model Context Data

Data Analyzer

Transparent network, focus on

actual forwarding plane

Imagine You Can Know Everything

about Your Fabric Behavior

Fabric State DatabaseFabric real-time status and

behavior model

Telemetry-based, focus on real-

time fabric status

Polling-based, focus on

device status


Key Capability of Data Analyzer

Precise playback of historical

faults and retrieval of ten billion

data records within seconds

VMVM

!

Correlation

Search Verification

Searches tens of billions of data

records per second

Processes millions of flows per second

Visualizes the network in multiple

dimensions for precise history review

Actual network quality

assessment and proactive risk

prediction

Evaluates the network SLA based

on true flows across the entire

network

Identifies and analyzes abnormal

network flows

Mutual visibility between applications and

networks, facilitating minute-level fault locating

Associates apps with network paths to enable quick issue demarcation

Evaluates network strategies through application dependency mapping (ADM)


Context /Telemetry

Big-data based Analytics

Intent-driven Automation

• Intent-based APIs reduce complexity

• E2E Automation for Hybrid Network

• Real time network state awareness

• Algorithm-based

issues/risks/threats detection

for Predictive Maintenance

Network Infrastructure

Netconf /YANG

Intent-based API Data-driven Insights

Unified Web Portal Open API Gateway

Real-time Telemetry

Cloud Native Platform

Data Analyzer

Manager Controller BigData/AINetwork Info.

OptimizationAdvice

Intent EngineIntelligence Engine

Network Automation

Service Agility Improves 90%

60% Issue Predictable

Introducing Data Analyzer to close loop Central CO

Self-help Portal Service synergist / OSS Applications


Open Ecosystem

Network Architecture

Protocol & Model Linux Foundation

Networking Fund

Standard

Organization Open Source

CommunityCo-operation

Cloud CO


Huawei Vision : IDN Bridges Business Intent and Networks

Network Infrastructure

Business Logic/Policy

• Network-centric

• Fragmented

• Reactive

• Skill-dependent Predictive

maintenance

Intent-driven automation

Real-time awareness

Intent

Digital Twin

Intent Engine

IntelligenceEngine

AutomationEngine

AnalyticsEngine

• User-centric

• Closed-loop

• Predictive

• AI/Automation


Summary

• In Cloud-centric, 5G and IoT era, operators are facing challenges ofcurrent network and transformation towards Cloud-centric network.

• The Cloud CO architecture is the cornerstone of NG broadband networkto enable network & service decoupling, SDN, NFV and cloudtechnologies in order to address multi-access, multi-tenant and fastservice innovation, with various of flexible network modes.

• We present Huawei’s understandings, experiences and learnings from theexecutive projects in the scenarios of access, metro network, overlay VPNand NFVI. The details of network abstraction, slicing and centralizedcontrol, VNF/VNFC diversity and use cases, overlay networking and I/Otechnologies in NFVI, domain orchestration and enhanced assurancebased on data analysis will be discussed.

• Open ecosystem and Huawei vision are shared.

Copyright©2017 Huawei Technologies Co., Ltd. All Rights Reserved.

The information in this document may contain predictive statements including, without

limitation, statements regarding the future financial and operating results, future product

portfolio, new technology, etc. There are a number of factors that could cause actual

results and developments to differ materially from those expressed or implied in the

predictive statements. Therefore, such information is provided for reference purpose

only and constitutes neither an offer nor an acceptance. Huawei may change the

information at any time without notice.

Thank You.

Date post:	03-May-2018
Category:	Documents
Upload:	vuongkien
View:	221 times
Download:	6 times

Future Broadband Network Virtualization Cloud Central … Broadba… · · 2018-03-23Huawei...

Documents