C/U Separated and Modular Architecture for NFV. Dr. Mo li Chief Architect of CTO Group, ZTE Corporation

C/U Separated and Modular Architecture for NFV Dr. Mo li Chief Architect of CTO Group, ZTE Corporation

C/U Separated Requirement for Multi-tier DC Scenario enterprise Different processing character Different affect on user experience MICT-OS TM Integrated Telecom Operation & Maintenance System Management Layer family personal wifi Elastic Cloud Service TM Cloud RAN Elastic Bearing/ FAN Edge DC Cloud UniCore-U ivas-u Elastic Cloud Service TM Cloud UniCore ivas Central DC Service Layer 4G 2/3G Access Backhaul Aggregation Optical Metro Core IP Optical Backbone Internet Bearing Layer 2

目录 vcn Architecture TCSA Application layer Mobility Management TCSA (Telecom Cloud Service Architecture) NSL(Network Service logic) - (C-Plane) Authentication (Common Network Component) Session Management NSL(U-Plane) Packet Forward Codec Stateless design+low coupling Separation from control plane and user plane Componentization Common layer Load Balance Signaling processing Interface processing Data layer (Cloud Database) Subscription Data Service Data Resource Data Link Data 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

目录 Service Componentization & the Deployment Flexibility Scenario 1:operator market, large-scale network, legacy traditional/cloudlization / multi vendor hybrid network vgw S/P GW Logic vmme MME Logic vhss HSS Logic Scenario 2:enterprise network market, small-size network, cloudlization network S/P GW Logic vcn MME Logic HSS Logic Scenario 3:large capacity, low cost, multi-tier DC deployment vcn - U U COMP MM SM vcn-c Access Auth Policy CC U COMP vcn - U TCSA architecture, more reliable and easy for expansion. Virtualized NE adopts standard interface for interconnection, construct with traditional network Shared by /, more compact and save resources Internal interfaces among service logic components, higher efficiency 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 Data Pull or Push VM1 VM2 New VM VM1 VM2 New VM 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, the elasticity shortens from traditional minutes to second. 0 service interrupted:real-time synchronization of data, after VM handover, VM directly acquires the latest data from 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 Cloud redundancy solution Active VM Active VM Data Sync 1 Standby VM Active VM PULL/PUSH Data Sync Active VM Standby VM Active VM Active VM PULL/PUSH Data Sync n 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. 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

C/U Separated Architecture of vepc Other MME/GW (EPC-C logical) Mobility Management Session Management Authentication Service IF: EPC-C Common Component Load Balance Signaling processing Interface processing EPC-U Management IF: OCS/ PCRF/ HSS Cloud Database Interface Service Management Usage Loading flow policies of traffic processing Load Quota for online charging Reporting usage for offline charging Configuration, KPI, alarming EPC-U TC-U DPI TCP-OPT SGi/S1-U/ S5-U/ X3 IP GTPU Stat. Policy Enforcing 7 ZTE All rights reserved

目录 vepc CU Separation Improves transportation Efficiency Central data center Edge data center Subscriber context and resources Internet EPC-C EPC-C V M V M V M EPC-U EPC-U V M EPC-U EPC-U Internet Edge data center Solution : CU separation,centralized control plane, Benefits: distributed forwarding, select user plane based on the following strategies: Load (load balance) location(near offload) APN(service guide) 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).

目录 VoLTE NFV PoC with China Unicom ZTE vims ZTE vepc KVM HP Hardware Resource vims vgw-u vgw-u vepc-c HP NFVO ZTE VNFM ZTE/HP VIM NFVO VNFM TECS Helion 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;

Cloud Works Break Bottleneck of Service Development & Innovation Product Service Vendor Operator Customer Demand Customize VNF v1.0 Problem VNF v1.x IaaS Still service development mode of customized demand development between operator and system provider Long period, high cost, single cooperation channel VNF v1.x Operator Developer Vendor Component Library Voice SMS Video LB Open API Cloud Works Component Detection Binding IaaS Solution GUI Develop Integration Test Tool Construct NFV PaaS platform based on component service Components provide open API interface, development new service based on flexible GUI/template combination and 3 rd party integration component library service component combination Voice LB Sec MQ Voice LB Sec MQ LB MQ... LB MQ SMS SMS Video+UHD DB DB component library service component + enhanced customized component Highlight DB DB Any 3 rd part can freely combine service component in the component library, not depending on system provider 3 rd part customized component supports new service expansion 10

Cloud Works Hour-level New Service Development & Deployment Platform Customer A Cloud Works Developer Customer B Engineer Auto test script Network connection test NS function test VM performance test VNF performance test NS performance test SLA Library Policy Engine Voice LB Sec MQ SMS SMS Voice LB LB MQ Sec MQ NS A DB DB LB MQ Video SMS NS B DB DB Voice LB Sec Sec Test VM LB MQ SMS Voice DB DB Monitoring Network KPI VM Load VNF KPI NS KPI Lifecycle Execution Self-healing Migration Shrinkage and expansion Hour-level New Service Development Automatic Function Performance Verification Lifecycle Automatic SLA Guarantee 11

Cloud 目录 Works Helps Operator to Build Carrier-class Open Ecosystem with RCS Multimedia call center Dev Tool Design Develop Compile Test Ops Framework Mobile office Self-operated APP Basic API set Automatic deploy Message Database Visual communication Signaling VPN Access management Lifecycle management ZTE Cloud Works Ability open layer Service API capability set Protocol stack DPI Policy routing Voice SMS QoS control Elastic scalein/out IPTV visual communication Video Multimedia conference Subscriber management Load control Family medical care Partner APP Operation API capability set Big data analysis Closed loop control Precise marketing HA/DR Charging API Integration Framework Home security Cloud Works: Carrier-class open ecosystem Convenient for the operator to quickly launch new services for enterprise customers Open API to partners, diversified services

Thank you