1. Xiaodong Duan& Weiqiang Cheng
Experience with CORD
Xiaodong Duan& Weiqiang Cheng
China Mobile
Nov, 2017

2. Our Vision of Future Network1 2
Our experience with CORD 3
Summary and suggestions

3. NovoNet – Our Vision of Future Network
New Network
Architecture
Virtualized Network Function
Centralized Control
Programmable Network
Operation
Auto Deployment
Flexible Orchestration
Maximal Usage
Service
More Open
More Agile
On-demand
Future Network need deploy cloud-based DC and Smart schedule of network, formation New DC and New network.
Enabler Technology
NFV
New DC
Enabler Technology
SDN
Orchestrator
New Network
NovoNet has been released officially in 2015 Asia CSMA
该架构的目标是建设面向云业务的网络服务能力，为用户提供泛在接入、高速传输、网络随选、服务云化的业务能力。
New DC(cloud-based DC )，low-cost Generic Hardware , realize edge offload、computing capability ,
New Network ,separation of control plane and data plane,
未来网络引入全新的编排系统，实现全局化的网络编排管理 — —Orchestr
Ner Brain（Globalized Network Orchestrator）,
未来网络将趋于扁平化，实现智能化网络调度

4. Core TIC（with Mgmt. Platform） Core TIC（with Mgmt. Platform）
Re-architected Network
New infrastructure: deploy cloud-based DC as infrastructure pool, carrying various network functions
Centralize control: network control functions is located in the core TIC
Media plane at edge: build edge TIC near access site, steer content to the network edge, fast traffic distribution
Core TIC（with Mgmt. Platform）
Core TIC（with Mgmt. Platform）
Core DC
Edge DC AP
~50 Core-TIC
VNFM
Orchestrator
VNFM
Orchestrator
NFVI
VIM
NFVI
VIM
SDN Ctrl.
SDN Ctrl.
Hardware
SDN Ctrl.
Hardware
SDN Ctrl.
TIC: Telecom Integrated Cloud
Edge TIC
Edge TIC
Edge TIC
NFVI
NFVI/Cloud OS
VNFM
NFVI
NFVI/Cloud OS
VNFM
~3500 Edge-TIC
VIM
VIM
SDN Ctrl.
SDN Ctrl. AP AP
AP: Access Point
Virtualized
Dedicated
Dedicated
>50,000 AP
OLT
OTN
PTN
NFVI/Cloud OS
PTN
BBU
OLT
NFVI
OTN

5. Standard Orchestration Standard Infrastructure
TIC is the Standard Unit for Future Network
TIC is the standard unit for NovoNet. It supports telecom software app based on carrier-grade infrastructure
TIC is based on standard network, infrastructure and orchestrator. It is easy to copy and quickly deployed.
The Telecom Central Office will be re-architected as TIC
Standard Orchestration
Standard Infrastructure
MANO
SDN Controller
Integrated NFV & SDN Orchestration
Unified hardware design with limited number of models suitable for different category of services.
Unified Cloud OS
VNF FW
Power
Cloud OS
Router
Hardware
Standard network
Switch
Strict network plane partition, including Management net, service net, and storage net.
TIC ：Telecom Integrated Cloud

6. Mobile: “Software” 5G based on NFV
5G VNFs can be flexibly deployed in TIC+AP based on the service scenarios
5G leverages cloud technology to achieve network customization, openness, service-oriented, to support huge traffic, large connection and low latency capability to connect everything.

7. Fixed Broadband: C/U Separated vBNG
Separation of control and user plane
Centralized Control Plane : NFV provides flexibility and scalability in TIC-CORE
Distributed User Plane : High performance hardware ensures data forwarding in TIC-EDGE
Advantages
High utilization : Network utilization rises more than 50%
Simple maintenance : Centralized control, reduce 90% device configuration
High performance : 10 times faster dialup speed
Control plane
Data plane
User AAA
Session management
Policy management
BNG-CP
Policy executing
Routing and forwarding
SDN Controller
TIC-Core
RGW
ONU
OLT
BNG-UP
Internet
Residence
Access
TIC-edge

8. Enterprise: E-BoD Service based on SDN/NFV
Combine SDN and NFV technology to support E-BoD ( Enterprise Bandwidth on Demand) service
...
deployment
server a
SITE A
Application & Deployment
Policy Delivery
Internet
Start
End
vMSR
1pm
4pm
uCPE1
Server b
Site B
SPTN/
IP/MPLS
uCPE2
Edge TIC
uCPE3 HQ

9. We are interested in E-CORD And M-CORD NOW
CORD Can Be a good Reference Solution for TIC-edge
In the development of NFV/SDN, open source communities and the standard organizations are the driving force to promote the transformation of the CT industry.
Promote the fulfillment of Carrier-Grade features and reduce difficulties and complexity of software development and Integration of Cloud Central Office
Closed Proprietary
Open Source+Standards
ONIE, ONL, FBOSS,
OVS, OF-DPA, P4, …
OpenStack
ONAP
CORD
With scalability, performance, HA, ease of use & deployment
1. Disaggregation
2. Softwarization
3. Open Source
Open Source
Integrated Solution
Vendor locked-in and
Difficult to innovate
Difficult to consume disaggregated components
We are interested in E-CORD And M-CORD NOW

10. Our Vision of Future Network1 2
Our experience on CORD 3
Summary and suggestions

11. CMCC E-CORD Lab test Plan
Current situation
What to do for the step
Plan in detail for this step
Action
Physical Deployment for Reliable, Scalable and Manageable network E2E service demo
E-CORD
CIAB Deployment
Successfully deployed
Aug. in 2017
Jul. in 2017
E-CORD setup at CMCC Lab Together with ONLAB
Nov. in 2017
Evaluate the stability, performance, reliability, scalability of CORD platform
Work together to push CORD into practice

12. Overview of E-CORD Demon in CMCC Lab
Build E-CORD (with three COs) to evaluate it’s capability of service provisioning
Site to Site: Provide L2/L3 connections between different sites of customer.
Site to Internet: For specific site, can provide access to Internet
Site to DC: Provide L2/L3 connections between customers’ sites with cloud resources

13. Physical CORD setup at CMCC Lab
Global XOS
CORD site1
CORD site2
CORD site3
Local XOS
Local XOS
Local XOS
Open
stack
ONOS
Open
stack
ONOS
Open
stack
ONOS
Spine-leaf
Spine-leaf
Spine-leaf
Computer node
Computer node
Computer node
。。。
Computer node
Computer node
。。。
Computer node

14. Progress: E2E Enterprise service setup in E-CORD
Service features
Automatic and fast service deployment
Branch VPN connection/L2VPN
Dynamic bandwidth allocation at service peak time
Multi path bonding and forwarding
APP visibility\forwarding\SLA/Qos
Personal untrusted apps\trusted cloud app\trusted enterprise dc app
Differentiated service forwarding
Local packet flow breakout
Co-exist SDN-WAN and legacy branch sites
Service Management
self-service for customs
service management for operators

15. Work we have done on M-CORD
Build end-to-end demo at CIAB with CM’s access device(goal by 2018 Q1)
CORD platform from Quanta
Open source vEPC from Intel Lab
Current progress: Demo on CM GPC event in Guangzhou
Future test on M-CORD (4G & 5G scenarios)

16. Our Vision of Future Network1 2
Our experience with CORD 3
Summary and suggestions

17. Suggestions on CORD Platform evolution
Further improve stability and efficiency of building and deployment
easy update cord platform without re-deploying from scratch
More stable process for PXE booted computer nodes
Multiple options for computer node installation: MaaS booted vs. others ways for computer node installation
Distribute architecture of head nodes for practical deployment: De-couple among the cord platform infrasture services
XOS cluster
Openstack cluster
ONOS cluster

18. Thank You！