c/u separated and modular architecture for...

Dr. Mo li

Chief Architect of CTO Group, ZTE Corporation

C/U Separated and Modular Architecture for NFV

© ZTE Corporation. All rights reserved 2

C/U Separated Requirement for Multi-tier DC Scenario

Core IP Aggregation

2/3G

4G

Backhaul

Access

enterprise

family

wifi

personal

Edge DC Central DC

Optical Metro Optical Backbone

Service Layer

Internet

Bearing Layer

MICT-OS TM

Elastic Cloud Service TM Cloud RAN

Cloud UniCore-U

Elastic Bearing/

FAN iVAS-U

iVAS Cloud

UniCore

Management Layer Integrated Telecom Operation &

Maintenance System

Elastic Cloud Service TM

Different processing character Different affect on user experience

© ZTE Corporation. All rights reserved

目录 vCN Architecture – TCSA

Application layer

Common layer

Data layer

Mobility Management

Session Management

Authentication

Load Balance

TCSA (Telecom Cloud Service Architecture)

NSL(Network Service logic) - (C-Plane)

CNC(Common Network Component)

CDB(Cloud Database)

Stateless design＋low coupling

Separation from control plane and user plane

Componentization

Packet Forward

Codec

Subscription Data Service Data Resource Data Link Data

Signaling processing

Interface processing

NSL(U-Plane)

Service data: separated + distributed

Highlights • High performance: all modules are active and carry traffic,

higher resource utilization.

• Better experience：ISSU and seamless elasticity

• Easy O&M：fast upgrading and deploy new SW version

• Better expansion：easier to introduce new applications

• Second-level elasticity：VM disaster redundancy and migration without data migration

• Higher reliability：0 service loss/N+K distributed disaster redundancy


目录

vHSS

CDB

HSS Logic

CNC

Service Componentization & the Deployment Flexibility

• TCSA architecture, more reliable and easy for expansion.

• Virtualized NE adopts standard interface for interconnection, construct with traditional network

vMME

CDB

MME Logic

CNC

vGW

CDB

S/P GW Logic

CNC

vCN

CDB

S/P GW Logic

CNC

MME Logic

HSS Logic

vCN-C

CDB

MM

CNC

Access

vCN - U

CDB

U COMP

CNC

Scenario 1：operator market,

large-scale network, legacy traditional/cloudlization / multi vendor hybrid network

Scenario 2：enterprise network

market, small-size network, cloud-lization network

vCN - U

CDB

U COMP

CNC

Scenario 3：large capacity, low cost, multi-tier

DC deployment

• Shared by CDB/CNC, more compact and save resources

• Internal interfaces among service logic components, higher efficiency

SM Auth

Policy

CC

• Function componentization, deploy according to requirements and meet precise customized requirements.

• Distributed deployment, high efficiency of service processing.


目录 Seconds level Elasticity Legacy elasticity service and data is migrated

simultaneously, with slow speed, interrupted

service and bad experience

VM1

VM2

New VM

VM1

VM2

New VM

CDB … …

Data Pull or Push

Highlights

• Seconds level elasticity：Service and data separation, when service layer VM scales in or out, there is no need for complicated data

migration, new VM directly acquires the latest subscriber data from CDB, the elasticity shortens from traditional minutes to second.

• 0 service interrupted：Real-time synchronization of CDB data, after VM handover, VM directly acquires the latest data from CDB via

Push or Pull, thus to guarantee service continuity and improves subscriber experience.


目录 Cloud Redundancy Solution Guarantees High System Reliability

Legacy 1+1 redundancy solution

Active VM

Standby VM

Active VM

Standby VM

Cloud redundancy solution

Active VM

Active VM

Active VM

Active VM

CDB 1

CDB n

1 to 1 backup VM module is not required, when one or more VMs fail, the subscribers access to other VM modules to continue the service processing

Challenges: Discontinuous service：if active module fails, service will be interrupted. Resources with low efficiency: backup module is only used for backup, which cannot be fully used.

Benefits: No loss of service：if the rest of the processing module resources meet existing service requirements, one or more service processing modules failure do not result in service interruption. High efficiency use of resources：service processing modules are all in active status, resources are fully used.

Data Sync

Data Sync

Data Sync

PULL/PUSH

PULL/PUSH

7 © ZTE All rights reserved

C/U Separated Architecture of vEPC

EPC-U

Service IF:

EPC-U

GTPU Stat. IP Policy Enforcing

TCP-OPT DPI …

OCS/ PCRF/ HSS

Other MME/GW

TC-U

Management IF:

SGi/S1-U/ S5-U/ X3

Interface Usage

Service Loading flow policies of traffic processing Load Quota for online charging Reporting usage for offline charging

Management Configuration, KPI, alarming…

Mobility Management

Session Management

Authentication…

(EPC-C logical)

Load Balance

Common Component

Signaling processing

Interface processing

CDB

Cloud Database

EPC-C


目录 vEPC CU Separation Improves transportation Efficiency

Edge data center

Internet

Central data center

EPC-U EPC-U

V M

V M

V M

V M

Edge data center

•Solution :

• CU separation，centralized control plane,

distributed forwarding, select user plane

based on the following strategies:

• Load （load balance）

• location（near offload）

• APN（service guide）

• Benefits：

• Centralized O&M, control plane function is

centralized, fast deployment reduces TCO

• Centralized management of context and

resource control plane, fast self-heal of

forwarding point, better reliability.

• Control plane coordinates the subscriber to

optimize seamless service path during mobile

procedure, with better experience.

About 90Mbps Inter DC transportation is required for 300K subs (based on CMCC traffic model).

Subscriber context and resources

EPC-C EPC-C

EPC-U EPC-U

Internet


目录 VoLTE NFV PoC with China Unicom

ZTE vEPC

Multi-vendor NFV environment NFVO: ZTE (vManager), HP(NFV Director);

VNFM: ZTE (vManager );

VNFs: ZTE (vEPC & vIMS);

EMS: ZTE (NetNumen U31)

VIM: ZTE (TECS) , HP(Helion);

HW: HP (BL460c Gen9)；ZTE (ZXCLOUD E9000).

PoC

E2E VoLTE service verification: LTE service,Voice service, billing

NS&VNF life cycle management: registration, deployment,

expansion, hot migration, upgrade;

Elastic scalability: manual and automatic Scale-in & Scale-out;

User plane acceleration technology: DPDK, SR-IOV;

vGW based iSDN: separate control plane and user plane;

ZTE vIMS

KVM

HP NFVO

ZTE VNFM

ZTE/HP VIM HP Hardware Resource

vGW-U

vEPC-C Helion

TECS

VNFM

vIMS NFVO

vGW-U


Cloud Works – Break Bottleneck of Service Development & Innovation

IaaS

VNF v1.0

Customer

Operator

Vendor

…

•Still service development mode of customized demand development between operator and system provider •Long period, high cost, single cooperation channel

Problem

…

…

VNF v1.x

Demand

Product

Customize

IaaS

GUI Develop

Integration Test Tool

Component Detection

Binding

Service

MQ LB DB DB

LB Voice

MQ Sec

Open API

component library service component combination

Component Library

…

MQ LB DB DB

LB SMS SMS Voice

MQ Sec

•Construct NFV PaaS platform based on component service •Components provide open API interface, development new service based on flexible GUI/template combination and 3rd party integration

Solution

•Any 3rd part can freely combine service component in the component library, not depending on system provider •3rd part customized component supports new service expansion

Highlight

Operator Developer Vendor

Video+UHD

component library service component + enhanced customized component

Voice

SMS

Video

LB

Cloud Works

... VNF v1.x


Cloud Works – Hour-level New Service Development & Deployment Platform

MQ LB DB DB

LB Voice SMS Voice

Sec Sec

Hour-level New Service Development

Automatic Function Performance Verification

Lifecycle Automatic SLA Guarantee

Lifecycle Execution Monitoring

Policy Engine

SLA Library

Network KPI VM Load VNF KPI NS KPI …

Self-healing Migration Shrinkage and expansion …

Developer

Cloud Works

Customer A Customer B

MQ LB DB DB

LB SMS Video Voice

MQ Sec

MQ LB DB DB

LB SMS SMS Voice

MQ Sec

NS A

NS B

Test VM

Engineer Network connection test NS function test VM performance test VNF performance test NS performance test …

Auto test script …


目录

Mobile office

Dev Tool Design

Develop Compile

Test

Visual communication

Family medical care

Multimedia call center

Cloud Works Helps Operator to Build Carrier-class Open Ecosystem with RCS

Cloud Works: Carrier-class

open ecosystem

• Convenient for the operator to

quickly launch new services for

enterprise customers

• Open API to partners,

diversified services

Ops Framework … HA/DR Load

control Elastic scale-

in/out

Lifecycle management

Automatic deploy

Service API capability set Basic API set

ZTE Cloud Works

Self-operated APP Partner APP

IPTV visual communication

Operation API capability set

Signaling Protocol stack

VPN DPI

Access management

Policy routing

… …

Voice Video

SMS Multimedia conference

QoS control Subscriber

management

… …

Big data analysis

Precise marketing

Closed loop control Charging

… …

… …

API Integration Framework

Message

Database

…

…

Ability open layer

Home security

Thank you

c/u separated and modular architecture for...

Documents