19
© 2017 TM Forum | 1 NFV Case Study of China Mobile Wang Ye, Director, Network Management Support, China Mobile

NFV Case Study of China Mobile - TM Forum · How to deploy the MANO (centralized or in province)? How to deploy the VAS service considering that VAS vendor can’t offer VNFM How

  • Upload
    lyhanh

  • View
    214

  • Download
    0

Embed Size (px)

Citation preview

© 2017 TM Forum | 1

NFV Case Study of China Mobile

Wang Ye, Director,

Network Management Support, China Mobile

© 2017 TM Forum | 2

About CMCC

• the leading telecommunications services provider in

Mainland China

• Our services

© 2017 TM Forum | 3

Milestones of CMCC Network Virtualization

2010, initiated the network virtualization R&D

2015, initiated NovoNet program

11/2015,launched NFV trialprogram on the real network

May 2016,OPEN-O at

the Linux foundation

Dec,2016, lanched the NovonetPilot network program

NB-IOT virtualization commercial preparation

April 2017 ONAP at

ONS 2017

July 2015,Release

NovoNet2020

2014,Initiated

OPNFV

2012,involved in

ETSI NFV ISG

© 2017 TM Forum | 4

• Technology :NFV/SDN/Cloud

• Philosphy : Network function virtulization, Resource/Service Sharing, Network Programming

Net

NovoNew

ArchitectureSoftware,

virtualized,Programmed

New

Operation

Centralized, Flexible,

Resource shareble

New

Service

Open, On demand, Agile

Mobile Data CenterIP Network TX Network

Novonet: CMCC next generation nework

© 2017 TM Forum | 5

Chinamobile NFV trial schedule

2017.6-2017.112016.08-2017.12015.10-2016.04

Phase I:Key function PoC trial

Phase II:HW/SW decoupling test

Phase III:IoT EPC、IMS 、SMS service trial for commercial

Software Partners Hardware Partners

© 2017 TM Forum | 6

NFV scenarios of CMCC

2017 Q4, we will complete the validation of vIMS、vSMSC、vNB-IOT and other

VAS(value added service )scenarios

VoLTE NB-IOT SMS

• vIMS CSCF

• VoLTE AS

• vIMS SBC

• vEPC vMME

• vEPC vSGW

1 SIM 2 Numbers

Ringtone Platform

• vSMS

VAS service

© 2017 TM Forum | 7

Achievements through NFV trial

1. Software and hardware

decoupling

2. VNF on-boarding,

update and scaling

3. MANO function ,

interface test with indirect

mode

4. The IOT test of NFVO-

VNFM and NFVO-VIM

Mircro-

Service

VNF

Cloud OS

VNF

(IMS..)

VNF

(EPC、5GS..)Micro-

Service

Virtual Function

Infrastructure

Compute Storage Network

NFVO

VIM

VNFM

© 2017 TM Forum | 8

MANO Solution for the Trial NW

• MANO: NFVO+ + VNFM + VIM

• NFVO+ : FCAPS + Orchestration ;

X Can’t provide NS mgmt. and policy design&mgmt. for

multi-vendor NW.Hypervisor

HW

EMS/OMC

VNFM

NFVO+

VIM

VNF

Legacy OSS

Ve-Vnfm-em

Ve-Vnfm-vnf

Nf-Vi

Vn-Nf Vi-Vnfm

Or-Vnfm

Vi-Ha

Syn

Or-Vi

✓ Provide consistant VNF package format

✓ Provide consistant Mgmt procedure for VNF package

✓ Standard HW mgmt interface

✓ Resource orchestrate in a vendor’s HW pool

✓ Resource allocation with the indirect mode.

✓ FCAPS mgmt. and the VNF lifecycle mgmt.

© 2017 TM Forum | 9

To fully achieve the ability of NFV , we still need …

For the NS orchestration, still much work to do

• HW/SW decoupling to

HW/Hypervisor/VNF decoupling.

• Standard the VNFD

• Build an openness VNF eco-system,

design a standard G-VNFM.

• Standard the NSD based on the

standard VNFD.

The path to glory is always rugged

© 2017 TM Forum | 10

Unify Architecher

Standard VNFD

VNFD: Virtual network function descriptor.

Standard VNFD :

• Benefit the network topology analysis and the display.

• Benefit the technical to understand the NW resource to orchestrate.

• The pre-condition for G-VNFM.

• The pre-condition for standard the NSD.

Standard VNFD in ETSI:

• A plan have been published to standard the VNFD with TOSCA in the SOL001.• The plan allow vendor to expand the definition with TOSCA, differentiate will be introduced.

Unify Model

Languange

Unify Syntax

OASIS TOSCAMulti Vendor VNFM -> G-VNFM

2017-2018 2018-2019 2019-2020

ETSI SOL001

© 2017 TM Forum | 11

G-VNFM: Multi-vendor VNF orchestrate

• VNF life-cycle mgmt. for multi-vendor

VNF use Vn-Vnfm-Vn interface.

• VNF O&M for multi-vendor VNF with

EMS use Vn_Vnfm-em interface.

• Multi-vendor VNF orchestration ,

avoid vendor lock.

NFVI

Generic VNFM

NFVO+

VIM

Legacy OSS

Ve-Vnfm-em

Ve-Vnfm-vnfVi-Vnfm

Or-Vnfm

Or-Vi

VIM

EMS1 EMS3EMS2

VNF1 VNF3VNF2

© 2017 TM Forum | 12

NSD( Network Service Descriptor)

• NSD describe the requirement of network

service, and the relationship of the required

NW resources.

• The VNF will be created follow the

requirement of the NSD.

• The standard of NSD will benefit the

automation service fulfillment.

© 2017 TM Forum | 13

The Way of Orchestraion

No Orch

Vendor Orch

Multi Vendor Orch

VNF Orch

Service Orch

Pre-NFV 2017-2018 2018 2018-2019 2020

HW/Hypervisor/VNFdecoupling

Standard NSD

Standard VNFDG-VNFM

HW/SW Decoupling

Dedicate HW Box

UE(R)AN-

DU

AF

AMF

PCF UDM

DNN6

N1

NG

CPNRFNEF

N3

N2 N4

AUSF

Nausf Namf Nsmf

NpcfNnrfNnef NudmNaf

(R)AN-

CU

SMF

UPF

CO

IMS

EPC CPE

© 2017 TM Forum | 14

OSS architectures must evolve along the following lines:

Evolving of the OSS

▪ Taking a holistic view of operations rather than the current piece-meal approach?

▪ Inheriting terms and definitions from standards rather than creating a separate language?

▪ Flexible architectures rather than static interface definitions?

▪ Full automation of the capacity management,optimization and reconfiguration cycle should be done by

orchestration and cloud management techniques with open and multivendor components rather than

vendor-specific management solutions.

▪ OSS focusing on portfolio management and end-to-end service management

▪ ……..

---------- ETSI ISG

© 2017 TM Forum | 15

FM RM

EOMS

4A

OMC/EMS/Controller

Design

Orchestrator

VIM

+

Capability Openness Platform

PM

IDC Mgmt

Tools: The Next Generation OSS of CMCC

• Centralization

• Visualization

• Openness + Open

source

• Microservices + Cloud

• FCAPS + Orchestrator

• Bigdata + AI

• DevOps

• ……

© 2017 TM Forum | 16

Skills :CT -> CT+IT+DT

ITU,3GPP, IETFCCSA, TMF etc..

SIP, Diameter…

Planning, Procument,RadioOptimiztion,etc.

Testing, Fault Mgmt,etc.

Deployment:Fuel/MCP、Compass、Apex、Juju、cloudera manager 、 ambari

OS:CentOS、Ubuntu

Cloud OS:KVM、VMware、 OpenStack

Code Mgmt:Git, Gerrit

Orchestrator:ONAP、 K8S 、ODL、ONOS

Programming:Python、Java、Shell

Now: CT Skills Future:(CT+IT+DT)Skills

Task Mgmt:Jenkins

Data Processing:hadoop、spark、caffe、tensorflow

Standards

CT

Protocals

Planning

Procument

O&M

© 2017 TM Forum | 17

Process & Culture

Work flow

DevOps

Work

flow

planDesign and

develop

operations

&

Maintenance

feedback

Prey deploy

and release

Deploy and release

• establish Devops cultrue

• Offline design and online operation

Online operation

Offline design

© 2017 TM Forum | 18

To be solved through the trial

Issues to be solved

▪ How to deal with the relationship between the legacy OSS and NFVO?

▪ How to manage the hardware FCAPS( such switches and firewalls) in NFV architecture?

▪ How to deploy the MANO (centralized or in province)?

▪ How to deploy the VAS service considering that VAS vendor can’t offer VNFM

▪ How could we operate the hybrid network (the structure of the organization and operator’s skill)

▪ ……..

© 2017 TM Forum | 19

[email protected]

Fetion Code