Текущее состояние рынка sdn/nfv и huawei на нём. Взгляд с трех...

Huawei Technologies Co., Ltd

SDN/NFV –current state

2Huawei Technologies Co., Ltd

Contents

Top-Down vs Bottom-Up2

Trends1

Telco proposition3

Enterprise proposition4


What is SDN/NFV

I. The next level in “division of labor” (this time for networking) – decoupling of HW from SW on all stages of life-cycle:• Develop/Test

• Sell/buy

• Provision/Test

• Support

• And even Utilization

II. Automation (again)


X Agile

The advantage of competition will change from “big”(performance, capacity)to “fast” (intelligence, automation): fast innovation, fast provision, fast demarcation…

ALL IP&

Single NWTDM

ATM

SDH

FR

No.7

……

Ethernet

IP carrier everything

IT based on Cloud computing

Apps & Services

SoftWare

Online + offline

New business model

New technique

innovation

Agile development, fast response

New competition

& cooperation

Internet is changing the world

New experience

Real-time

On-demand

All-online

DIY

Social

Structural Changes in Telecom


• vSTB DEMO (F)

• FusionSphere PoC (T)• vIMS PoC (V/D/T)• vEPC PoC (V)• vCPE DEMO (F)• vSTB DEMO (T/K)• Service chain PoC (V)

From Jan to Aug, 2014• FusionSphere PoC (T/D)• MANO DEMO (V)• vIMS Commercial trial (V)• vEPC PoC (D/F)• vCPE DEMO (V)• Service chain PoC Phase 2 for trial (V)

Planed from Aug to Dec, 2014• FusionSphere PoC (V/D/F)• MANO PoC (D/T/V)• vIMS PoC Phase 2 (D/T/M)• vIMS Trial (CMCC)• vIMS Commercialized (V)• vEPC PoC (V/T/M)• vEPC Trial (D)• vSTB trial (K)

Huawei NFV Success Cases

• Huawei has rich data center construction experience Global 400+DC, 120+ Cloud DC

• Huawei practice include : NFV-I, MANO, VNF(vVAS,vIMS, vEPC, vCPE, vSTB)

• Tier 1 carriers are active in POC/Trial and even small-scale commercialPrimarily:

ePC &

IMS/VoLTE


DC-centricChina Unicom Wo Cloud

China Mobile SPTN

China Telecom T-SDN

China Unicom SDN IPRAN

Telefonica UNICA Shanghai Telecom Hyrid Cloud

Tecent DCI

Huawei SDN Success Cases

APP-driven

Experience-oriented

Simplified Network

96 Physical DC to 6 vDC

IT Resource Utilization Improved 30%

Pipe Service to One-stop ICT Service

Service Provisioning 14 Days to 10 Mins

10 Physical DC 1 vDC

IT Resource Utilization Improved 30%

Open NBI to BOD App

Service Apply from Offline to Online

Open NBI to Traffic Optimization APP

Network Resource Utilization Improved to 80%

Service Apply from Offline to Online

Self-service BoD: 30 Days to 15 MinsSelf-Service BoD: 3 Days to 10 Mins

Traffic Optimization: 10 Mins to 10 Secs

Beijing Telecom Traffic Optimization

O&M Efficiency Improved 60%

Planning Efficiency 10 times

Peru IP+Optical TrialImproves Network Availability and Network Efficiency 50%

Time saving on service provisioning 80%

Primarily:

DC &

vE-CPE


SP NFVI HW; $1,3

SP NFV SW & MANO; $6,8

Carrier SDN HW; $1,3

Carrier SDN SW; $1,6

DC & Enterprise;

$19,0

Total SDN/NFV Market Size

(~$30B 2018 Est)Source: Infonetics

0

2

4

6

8

10

12

2012 2013 2014 2015 2016 2017 2018

Ma

rke

t S

ize

($

B)

Service Provider SDN/NFV Market

Infonetics

SDN Central

Doyle Research

Dell'Oro Group

SDN/NFV Market Forecast (HW/SW )


AT&T Domain 2.0: to be a software company

Tier 1 Carrier (Today’s AT&T)

Vendors

Products

Software

/Features SI/PS

$$$$$$$

C

O

UserUserUserUsers

$$$ Carrier-defined ServicesFeatures: limited numbers

WhiteboxVendors

Whitebox

$$

Partner Vendor

BoutiqueVendors

Boutique

HW/SW

$$$

Revenue

Sharing

“Super Carrier”Software Developers

Data Centers (AIC)

UserUserUserUserUserUserUsers

User-defined ServicesFeatures: 1000+

SI/PS

Partner Vendor

PartnerVendors

StartupsStartupsStartupsStartupsStartupsStartups

Innovative

Solutions

“Sandbox”

Partner

Program

Current Future

$$

Telco

Eng.

IT

Apps

OSS

/

BSS

C

OCO

$$$$$$

Virtual

Carrier

UserUserUsers

Special User Groups

Carrier of

carriers

$$$


UNICA Infrastructure Architecture is reference model,

it defines a “Reference Architecture for a service

rooms” with all the functionality that need the Telco and

Service Platforms and shall be cloud oriented.

Key features: Openness for multi-vendor, Multi-

tenancy operation, SDN network, NFV compliance,

Template service automatic deployment, Elastic

scaling, Disaster Redundancy and Multi-Business

operation for public and private cloud.

Unique values: Shorten time to Market, Save cost

for Operation and Maintenance, Improve Efficiency by

Unified Management and Global Governance

Disruptive UNICA Transformation

DC-4

DC-8

DC-3

DC-2 DC-5

DC-6

DC-1

DC-7

DC-n

Scattered DC, low utilization

96Physical DCs

ScatteredDC

vDC

IT Resource Utilization

30%6

vDCs

Consolidate DC resource unified cloud infrastructure


Telecom is a “live being”

Successful Telco is the right combination of

• Services (product)

• Technology

• Business practices

It’s impossible to considerably change one without another.

Change everything at the same time is close to impossible.

Technology

Services

Business

practices

Technology transformation should propose

smooth migration path from the current reality


Most important business considerations

• Operations: service automation (+self-services) is the primary goal (OPEX reduction is more important then CAPEX)

• Management: no one aspect of FCAPS should be omitted

• Self-healing should be considered on all levels of architecture (minimize the amount of interruptions to higher layers)

• Functional blocks structure should promote heterogeneous/multivendor environment

• Architecture should support flexibility for operators and vendors to change distribution of service components between functional block (to account for specific of an operator) – CSP should decide themselves right balance in centralized vsdistributed dilemma

• The current business processes could be assumed (thanks to TMF eTOM) – it reflects current distribution of responsibilities between administrative teams. Future business processes should be developed


IT approach to Telecom Architecture

“Software defined” means that we have to look to telecom architecture from IT point of view:

• Logical view.– Split system to optimal structure of functional blocks (balance between flexibility and

simplicity)

– Specify all APIs between functions (protocols and data models)

• Process view.Define major operational and management processes

• Deployment view.Justify particular infrastructure distribution over geography

It’s mandatory to define IT architecture for WHOLE telecom operator with a small resolution (to reveal biggest blocks).

Every big block could undergo the same architecture exercise, but it’s optional –operator could delegate to vendors internal architecture design of high level functional blocks.


Telecommunication Architecture WG

The industry needs Standardization Organization to take care for high level view of WHOLE telecommunication infrastructure in IT age:

• Define specification of services that should be kept in mind while developing all functional blocks

• Create the reference map for the first level split by functional blocks

• Choose communication protocols between upper functional blocks

• Define Data models for all APIs between functional blocks

• Develop recommendations for transformation of business processes

High level functional blocks should undergo the same treatment (see above), but there is no need to deep dive into all functional blocks under one standardization organization –different high level functions (storage vs network vs power vs conditioning) would have very different specifics, that is difficult to manage under one standardization body.

Is it a good idea to transform TM Forum into TS Forum?

They have exactly right experience for such exercise


CORD - Architecture

Open Source

Software

Core Components – OpenStack

– ONOS

– XOS

– OCP

Access Services – vOLT

– vSG

– vRouter

– …

Other Services – Monitoring

– …


Huawei Contributions to SDN&NFV Standards

2013.9 2014.2 2014.4 2014.7 2015.22014.6

• Services Area Director

• Specifications Area Deputy

Director

• Technical Council

• Chipmaker Advisory Board

• Layer 4-7 Services Chair

• OTWG Vice Chair

• NBI Vice Chair

• FAWG Editor & OF-PI Editor

• Co-chair, infrastructure WG

• Co-editor, Reliability WG

• Co-editor, MANO WG

• Contributed 4 use cases of

total 9

Leading the ONF SDN

joint projects, published

white papers

Leading the I2RS

information model and

data model

OPS Completed

IOT with OpenStack

Proposed 10

groups of Core

API to ONF

10+ SDN

IETF drafts

Leading the joint ONF/

ETSI NFV Proof of

Concept Demonstration

• Author, ALTO Protocol

• 10+ papers on SDN

Applications

• Leading the I2RS

information model and

data model

• Chairman, ITU-T SG11

• Chairman, SG11 WP2

• Q6 Speaker，Q4

Deputy Speaker


Cloud OS/OpenStack

CloudDSL/OLT

Operations

Cloud OS/OpenStack(Local Resource) + Middleware

Cloud OS/OpenStack (Local Resource, IaaS)

Apps & Services

Cloud OS/OpenStack (Local Resource, IaaS)

CloudEdge

Cloud OS/OpenStack

CloudBBRRU

Small Cell

Small Cell

RRU

PartnersOM Team

Consumer

CPE

MxU

MxU

ONT

E2E ICT Resource Orchestration Engine

OpenStack

OSS suits BSS suitsBig Data Suits

Business Orchestration & DevOps Tools

apps for Bizapps for OM APIapps for consumer

RaaS NaaS CaaSPCRF

D

D

D D

D

D

ETH+OTN

(Metro)

Router + WDM

(Backbone)

1

1

1 1

1

1 New Architecture: Datacenter-Centric Networking;

New Service: Digital Services and Public cloud Services;

3

2 New Network: SDN & NFV, Software defined;

4

4

4 New Operation: Internetized, Open Ecosystem, ROADS user experience;

GSM UMTS LTE

RNCSRC

SBCNAT

SDNController

BRASS/PGWGGSN

FWDPI

vCPE

SDNcontroller

SGSNMME

IMSHSS

ADSL VDSL G.Fast

2

2

2

2

ITapps

PaaS

IT apps(SaaS)

Telco appsSMS/IPTV…

Middleware (PaaS)

3 33

SDN

22 SDN

C

C

C

C

C C

Deployment model:How to split functions over CO/POP/Regional DC/Global DC?

Future Telecom Network Architecture Biz Customer


SNC controller (ONOS)

Device Link Host

Topology

FlowRule

Path

Packet

StatisticsIntent

Application

Cluster

Messaging

Lock Leadership

Mastership

Driver

MPLS Label

……

Link Resource

Event

OpenFlow NetConf OVSDB

Core Database

PCEP

ProxyArpSegment Routing L2 Forwarding

REST API GUI CLI

Network Cfg.

SDN IP / BGP Packet / Optical

Tunnel

..….

OSGi / Apache Karaf

VN.Device Cfg.

Security

UI Extension

Graph

DiscoveryOpenStack

Service ……

TL1

Traffic Engineering APPsExternal TE VPN IP+optical


Planning and Integration

Solution I Solution II Solution III Solution IV Solution V

Vendor 4 (Certified)


Vendor 1

Vendor 3

Vendor 3

Vendor 1


Vendor 1

Vendor 1

Vendor 3

Vendor 1

Vendor 1Vendor 1

Vendor 1

Vendor 1

PerformanceReliability

O&M efficiency

Flexibility

Integration

Cost

Adaptability

Vendor policy: How to split system between vendors?

Hardware

Cloud OS

Function

80% TTM Reduction by

Pre-Integration

Orchestrator

Vendor 1

Vendor 1 Vendor 1 Vendor 1 Vendor 1

Vendor 5

Business priorities: CT or IT first?CT: VDF,DT; IT:Telenor; ICT: TLF, AT&T


Enterprise SDN Architecture

Agile Controller

Agile Campus

Cloud Fabric

Agile WAN

Agile Branch

Optimized real-time, mobile, wireless experience

Three-fold lease cost reduction

One-click ICT resource

deployment and zero

local maintenance

Automatic network migration,

easier cloud computing

CE12800

USG9500

Agile SwitchNGFW

Agile Gateway

Speed, experience, efficiency, security

Agile IoT

Most abundant

interfaces, strongest

environmental and

protocol adaptability,

and highest

intelligence


Thanks

Текущее состояние рынка sdn/nfv и huawei на нём. Взгляд с трех...

Presentations & Public Speaking