01 NFV Fundamental Introduction

NFV Fundamental
Introduction
www.huawei.com
Copyright © 2018 Huawei Technologies Co., Ltd. All rights reserved.

Objectives
 Upon completion of this course, you will be able to:
 Understand the Development Trend of IT technology in Telecom Industry Network
 Understand the Basic Concept of the NFV
 Describe the Value and the architecture of the NFV
 Understand the Key of the NFV network design, build, and O&M.
Copyright © 2018 Huawei Technologies Co., Ltd. All rights reserved. Page1
Contents
1. NFV Network Technology Trends
2. Key Capability and Solutions
3. The Key of NFV Network Design, Build , O&M
Contents
Merging Boundary between IT and CT
Past Internet of thing

Present Future
Enterprise Internet
Industrial Internet
Everything is connected
Endless ICT applications
The History Of CT
ALL-IP
Saving & Growing is the
Circuit switching
PON/NG-PON
eternal theme
ADSL / VDSL
GSM/UMTS
LTE/LTE-A
40G/100G
400G/IT
。。。
。。。
。。。
。。。
IMS
CS
OSS/BSS
Growing
Saving
PSTN
GSM
….
IP+
RAN FAN Optical Core
FR NO.7 Ethernet
All-IP
TDM ATM SDH
Future
…
• Supported ICT convergent trend
Now • Lower cost to provide services
• Unified bearer • Flexibility for business agility
Past • Converged within the single domain
• Various bearer • Separated bearer, control & service
• Silo network • Initiating Multi-media services
• Plain service
What is NFV？

NFV (Network Functions Virtualization) From:Coupling of hardware To:Decoupling of hardware
and software and software
 NFV uses IT virtualization technology to
Operator A B C D E
consolidate many network equipment types
Decoupling
onto industry standard high volume servers,
switches, and storage, which could be located
in data centers, network boundaries, or end
Openness
user premises. The network functions are
implemented by software and executed on
physical servers. The industry standard high
volume servers could be migrated, instantiated, Simplifying
and deployed in various positions on networks,

which saves new equipment.
Indentified NFV Architecture and Basic
Requirements
NFVO MANO (NFVO + VNFM + VIM)
(Mange NS • VNFM with open interface for NFVO
Lifecycle) • VNFM seamlessly adapt to multiple VIM from multi-vendor
• Flexibility to lower impact on the existing EMS & OSS
VNFM VNF
• Elasticity Scale service up or down quickly
Virtualized Network Function (Mange VNF
VNF • Runs on Multi-Vendor NFVI with assessed performance
(e.g. vIMS/vEPC) Lifecycle)
NFVI-Cloud OS
• Preferred OpenStack based Cloud OS
• Optimized to minimize performance degradation
Cloud OS VIM
NFVI (Provision
(Hypervisor + Management Module)
virtualized
NFVI-Hardware
Resource) • Breed Chipset- level assisted virtualization technology
Hardware
• High IOPS with High reliability at same time for storage
(Server /Storage/Network) MANO
NFVI: VNF: MANO:
Network Function Virtualized network Management and
Virtualized infrastructure infrastructure Orchestration
Know More about MANO
Legacy OSS/BSS NFV Mgmt Plane（MANO）=Cloud Mgmt+ VNF Mgmt
No real-time、Black Box、 Real-time loop，layered，Distributed，Auto-healing
Element management
OSS OSS 1 Based On CT Experience

NFVO
No real-time No real-time
• Dynamic resource Mgmt
• Cross layer fault Mgmt
EMS VNFM
• Network optimization
VNF service Mgmt VNF Lifecycle Mgmt
EMS
Black Box Fault Mgmt VNF Installation
Function shift Configuration Mgmt Scaling in/out
2 Based On IT Experience
Real time Cross layer fault Mgmt
Performance Mgmt
loop
• Flexible service orchestration
VIM • Open interface
VNF • Open Templates
Network
Virtual resource Mgmt
Element Real time
Infrastructure loop Physical resource Mgmt
NFV Development Background
 At the end of November in 2012, 13 Tier-one operators (including AT&T,
British Telecom, Deutsche Telekom, Orange, Italy Telecom, Telefonica,
Verizon, Vodafone, and CMCC) establish the ETSI Network Functions
Virtualization (NFV) Industry Specification Group (ISG).
 The NFV enables operators to reduce costs, improve efficiency on

management, maintenance as well as service development, and provide great
potential in energy-saving, openness as well as innovation. These advantages
attract operators most.
NFV Integrated the IT gene into the Telecomm
Network
Traditional network
EPC APP
IMS APP
VAS
• Software hardware binding, optimized difficulty
…
…
…
• Hardware proprietary, high cost
• Chimney network, management and maintenance difficulties
Unified the virtualization layer
IT Cutting-edge technology
Unified hardware
Virtualization Technology
Distributed computing
The new network constructed by
CS/IMS
NFV component devices

EPC
VAS
…
• Software and hardware decoupling, Network

function virtualization , easy to optimize General
hardware, share of the mol bonus
• Resource normalization , simplify management
and operation and maintenance
New way, new throttle, new growth
TOP3 NFV Value Traditional network NFV Network
Service deployment Simplify Flexible and fast Fast

Fast TTM, TCO saving, promote innovation
complexity deployment Deployment TTM
Time consuming
process
Infrastructure Automation
O&M complex
Unified management OAM
TCO
Saving
multiple devices Infrastructure Hardware
coexistence Normalization
sharing
For third party Promote

Closed Development innovation
Source:Infonetics (2014.3)
<<SDN and NFV Strategies:Global Service Provider Survey >>
developers
Provide platform
Contents
The Industry Distinguish from Key Capabilities of
NFV System
key capabilities of NFV system
Virtual application software
Basic capabilities：
1 Open 2 Cloud OS
NFV new key competencies：

3 High elasticity
key Carrier-grade competencies:
POC Exploration and Practice 4 High reliability

5 High performance
Cloud OS
Open migration 6 Multivendor integration
High performance
reliability O&M
flexibility
Source:ETSI NFV whitepaper
…
Oct 17, 2013 7 Automation O&M based on MANO
Key Capability 1:Openness
Open lab Existing

MANO
OSS/BSS
Vendor A:
NFVO OSS
Rest
Mainstream Cloud OS
Openstack based Joint
ecosystem Vendor B:
Others Corba
Benchmark Benchmark VNFM
CSCF-SCU VM design:
EMS
(EXSI) 2VM , each with 4core SOAP REST
Hypervisor Multiple Hypervisor 2.49G 8G Memory Adapter Adapter
(C7000)
COTS(Huawei supported 200+vendors) TAS VM design:

Service VM 8 core
16G Memory
LB VM 2 core, 4G VIM VIM
Memory
Key Capability 2:Cloudification ≠ virtualization
VNF internal-view (vCSCF)

VNF(vCSCF） Cloud session Database
Data layer
NW Service Processing
Service and Data
Tightly coupled
Service and Data Service layer
Tightly coupled VM Cloud Session Distribution
Binding Hardware and Decoupled LB layer

Software Decoupled
Key differentiators
Industry • Separation between service, data and interface layer Huawei
Average • “Horizontal” scalability and “Vertical” interaction Present
Key Capability 3:High elasticity
Master Slaver Master Slaver

A A A A
B B B B
Dynamic Context:Register
and established session
C C information C C
… … … …
Restore Dynamic Established Live Traffic will be rebuild in
Context remaining VM immediately
Stateless Stateless
Service Logic Live … Live New Service Logic
…
With With Live Live Live
Traffic Traffic VM
N+M Redundancy N+M Redundancy Traffic Traffic Traffic
Distribute load by Distribute load by LB LB

CPU usage LB LB
CPU usage
Master Slaver Master Slaver
Key Capability 4 :High reliability
HA1：active/stand by
Application
LB LB
Guaranteed
Session
HA2：stateless, N+M redundancy
Process Process Process ”0”Interruption
module module Module
99.999%
Cloud OS
HA 2：VM recreated
Reliability
VM New VM
Guaranteed
HA：Cluster and optional Geo-redundancy
Hardware
Resources always
available
Each layer has independent HA mechanism ，but High complementary for Carrier –grade reliability
Huawei Continually Devotes to NFV Ecosystem
Maturity
Main Contributor for Standard NFV Open Lab
Multi-vendor Partners Joint

System Integration Innovation
Acknowledgement in the Industry First NFV Commercial Case

vAPP System
Integration Multi-vendors
Cloud OS Vertical SI
Carrier-grade SLA
Infra
HUAWEI Make CloudCore Easily Available
•Full openness for mainstream hardware and CloudOS
•Industry advanced Cloud-aware architecture
•99.999% reliability with software robust & IaaS supported
•High elasticity with scale in&out in minutes
•High performance with bare mental forwarding abilities
3rd MANO Integration

vIMS vEPC …
party
Vertical
NFVO integration •E2E integration services practice with operator V
Multi-Vendor Cloud OS •Full tool suite for enhancing efficiency
（ …） Horizontal •Joint ecosystem for off-site optimization
VNFM integration
COTS
( …) VIM Tool suits
•Enable automatic OAM with MANO

•Fast service deployment in hours
*Huawei also provided COTS Hardware and Cloud OS
•Associated multi-layer for E2E troubleshooting
Contents
Contents
3.1 The Key of NFV Network Design
3.2 The Key of NFV Network Build
3.3 The Key of NFV Network O&M
Build NFV Network Gradually
Traditional room Data Center
Hybrid networking
Traditional box equipment Mutual redundancy Whole network data center
Construction of new service
Old service expansion of cloud
Old service of EOL
3 Changes and 4 key points of NFV
 3 Changes of NFV
NFVO
for mange  Purchase mode change:layered purchase
NS lifecycle
 Construction change:Multivendor integration
 Mode of O&M change:from people to tool

Virtualized Network Function VNFM
①
for manage
(e.g. vIMS…vEPC..) VFN lifecycle
 4 key points of NFV

② Cloud OS ③  Key Point 1:Service and network evolution strategy
(Hypervisor + management module)
VIM
for provision  Key Point 2:Cloud layer implementation strategy
virtualized
Hardware resource  Key Point 3:Cloud OS Selection strategy
MANO
(computing /storage /networking)
 Key Point 4:Cloud deployment strategy
Key Point 1:Service and Network Evolution
Strategy Service NE and network Control plane NE Media plane NE
management
Deployment location concentrated，tiny number more concentrated , tiny number edge，more
Resource very high I/O (2~5Gbps/ slot), encoding
logical calculation, large storage, logical calculation, higher I/O
requirements and decoding, encryption and
common I/O (100~300Mbps/ slot) (100~500Mbps/ slot）
decryption
Virtualization
high high low performance
technology maturity
service service service
control control
control
media media media
Cloud service plane NE Cloud control plane NE Cloud whole network
Key Point 2:Cloud Layer Implementation Strategy
Plan A Plan B
Manufacturers A Manufacturers B Manufacturers A Manufacturers B
NE NE NE NE NE NE NE NE
Layering method
Cloud OS Cloud OS Cloud OS
Hardware resource Hardware resource
pool pool Hardware resource pool
★☆☆ For NE and the hardware integration, ☆☆☆ The NE and the cloud platform, cloud
Integration
need to do hardware internal planning platform and hardware needs to be
difficulty
and design integrated
★★☆ Software alarm and hardware alarm ☆☆☆ Alarm all independent, three manufacturers
Fault location independently, two manufacturers responsible
responsible
Resource ★☆☆ Between Cloud platforms cannot be ★★★ Inter Cloud platforms can be shared
utilization ratio shared
Basic principles:Hardware and software decoupling, hardware can be used for different manufacturers
Plan A:Cloud OS Manufacturers, deployment and maintenance is simple，but the resources can not be unified management and unified
scheduling
Plan B:Cloud OS one Manufacturer, deployment and maintenance is complex，but the resources can be unified management and unified
scheduling
Key Point 3:Cloud OS Selection Strategy
OpenStack Cloud OS Not OpenStack Cloud OS
Open:open interface of OpenStack standard Open:private single manufacturer interface

Maturity:mature Maturity:the most mature
Ecosystem:community support, manufacturers Ecosystems:private, manufacturers of products
products Market share:high
Market share:low, steady growth in the Price Price:high
Price:low, and even free
advice
From the perspective of industry developments and trends, Using OpenStack ICT integration cloud platform
architecture has a good opening and the ecosystem, best interest of carriers.
Contents
Challenges For Build(1):NFV Integration
Complexity
EMS/OSS/BSS
Horizontal integration
vertical integration
APPs vEPC,vIMS … …
deploy
MANO
Cloud OS VM Ware, deploy
deploy Open Stack… …
DC/COTS
deploy
Challenges For Build(2):CT Higher Requirements
web/vedio Content
vFW accelerator Optimizer
vDPI ...
&caching
vPCEF vGGSN
S/P-GW
vCPE vSTB
Self owned Biz, SRC IP SBC
3rd apps, Controller EPC
eg. IPTV RNC DPI
IaaS/SaaS… GGSN
BSC (Gi-Lan etc.)
BRAS … FW
IT infrastructure PE CDN
NFVI
Hardware ( COTS) NFV Hardware
Bearing CT service
 Real-time:low  Real-time:high
 Reliability:the single node is low reliability, total  Reliability:the single node is low reliability, total 99.999%
99.9%  Data isolation:complex
 Data isolation:simple (OM and service) (maintenance/monitoring/signaling/traffic//Provisioning/... )
Strategy for The Challenges(1):Considering Point
in Integration Cloud OS feature is the key to system integration
design

CloudOS feature differences

1. Fault-tolerant differential impact on VM design (vCPU)

2. Reliability mechanism of CloudOS impact on
APP APP APP … APP reliability design (dual partition)

3. Hardware acceleration capability impact on
Performance design (network pass-through）
4. … …
CloudOS
vSphere
Clou Platform specifications affect the overall system design
FusionSphe dStac
re k 
CloudOS specifications differences

COTS 1. Maximum number of virtual machines :80000 & 3000

2. Clustering support max number:128 & 32

3. … ...

COTS differences

1. CPU:Intel EP 10, Intel E5

2. Mem:256G, 128G

3. … …
Strategy for The Challenges(2):E2E Integration
Services “Horizontal” “Vertical”
Legacy system integration
OSS & BSS integration
9 Legacy integration
Legacy integration
8
8 OSS/BSS integration
NFVO
9 4 VNF integration
APP1 APP2 7 APP3
5
VNFM(s)
7 VNFs(APPs) integration
6 4 6 VNFs(APPs) integration
3
Cloud OS ( Hypervisor )
VIM(s)
MANO integration
2 NFVI
5 Orchestration integration
COTS COTS COTS
MANO
4 VNFs Mgmt platform integration
1 3 VM Mgmt platform integration
Infrastructure integration NFVI integration
Cabling …… Power 2 Virtualized platform integration
1 Infrastructure design & implementation
Contents
Changes of 4 Field Achieve NFV Service
Guarantee
Person
NFV
flow
Platform SLA
Change 1:Person--NFV O&M is Not just the job of
the personnel to be re matched front
front service
service monitoring
monitoring service
back presentation Apps Infrastructure
experts expert Experts experts
in the service overall SLA service components reliable platform
field guarantor guarantor guarantor
service
AN IP CN VAS
organization
and
APP APP APP management
infrastructure
management
cloud infrastructure
MANO has become a tool for collaborative NFV in different fields
Change 2:Flow--From Personnel Decisions to
Automation Rule based
Role based Operations managers Operations managers
submit network requirement to network submitted to

planning department the network requirement
Automation services
flow can be customized
Flow control Service templates on-
Flow cure equipment purchase Network planner evolution demand generation
Hardware deployment as a key Automatic allocation of
node hardware resources
opening service flow is slow Automatic Automatic deployment
Purchasing personnel distribute
of service software
hardware deployment
service configuration distribution of resources from the resource pool
Deployment personnel
Resource pool
Change 3:Platform--MANO become the Central
Platform of NFV Automation O&M
Step 1 Step 2 Step 3
Automation life Global resource management O&M and development integration

cycle management Dynamic service orchestration Can create value
• Heterogeneous cloud, • With DevOps to achieve rapid

• VNF auto-deployment, scaling
deployed across DC delivery, rapid innovation
• Layer decoupling
• Flexible service creation, and • Early, fast, easy to test
• Virtualization
dynamic layout
• Single DC deployment
• SDN coordination
customer experience orient
start service-oriented O&M create value
Change 4:Layered SLA—Guarantee Customer
Experience
Customer Experience
SLA Forecast analysis
Service Service management Policy engine
SLA
MANO
Trouble diagnosis and self-healing
Application Disaster recovery plan

App management
SLA Resource optimization algorithm
Virtual machines for high availability

NFVI NFVI management
Trouble Shooting ：Fast Fault Location and
Recovery
MANO:Fault diagnosis and self-healing Self healing KPI decreased VNF
strategy：
Virtual machine
Fault database migration
Virtual machine NFVI
alarm
Diagnosis center
Self healing action
NFVI Event report

Event collector
VNF alarm/
KPI report
EMS VNF
VM VM VM VM VM VM VM VM VM VM VM VM
VIM VIM
Host Host Host Host Host Host
DC DC
High Availability of Virtual Machine：Basis of
Service Continuity Protection
Migrate to other
VNF hardware
When the failure Quickly detect and recover quickly.
happen • Virtual Watchdog, Second-level
fault detection
VM VM VM VM • OpenStack function enhancement,
Support virtual machine rapid
Failure detection migration
Hypervisor
• Virtual machine built-in black box
VIM and analog serial port，ease for
Migration control
debugging
Summary
 This course we have introduced the following topics:
 The Development Trend of IT technology in Telecom Industry Network
 The Basic Concept of the NFV
 The Value and the architecture of the NFV
 The Key of the NFV network design, build, and O&M.
Thank you
www.huawei.com

01 NFV Fundamental Introduction

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

01 NFV Fundamental Introduction

Caricato da

Copyright:

Formati disponibili

NFV Fundamental

Copyright © 2018 Huawei Technologies Co., Ltd. All rights reserved.

 Understand the Basic Concept of the NFV

 Describe the Value and the architecture of the NFV

2. Key Capability and Solutions

3. The Key of NFV Network Design, Build , O&M

2. Key Capability and Solutions

3. The Key of NFV Network Design, Build , O&M

Past Internet of thing

and deployed in various positions on networks,

OSS OSS 1 Based On CT Experience

 The NFV enables operators to reduce costs, improve efficiency on

NFV component devices

• Software and hardware decoupling, Network

Service deployment Simplify Flexible and fast Fast

For third party Promote

2. Key Capability and Solutions

3. The Key of NFV Network Design, Build , O&M

NFV new key competencies：

POC Exploration and Practice 4 High reliability

Open lab Existing

COTS(Huawei supported 200+vendors) TAS VM design:

VNF internal-view (vCSCF)

Binding Hardware and Decoupled LB layer

Master Slaver Master Slaver

Distribute load by Distribute load by LB LB

Multi-vendor Partners Joint

Acknowledgement in the Industry First NFV Commercial Case

3rd MANO Integration

•Enable automatic OAM with MANO

2. Key Capability and Solutions

3. The Key of NFV Network Design, Build , O&M

3.2 The Key of NFV Network Build

3.3 The Key of NFV Network O&M

 Mode of O&M change:from people to tool

 4 key points of NFV

service service service

media media media

Cloud service plane NE Cloud control plane NE Cloud whole network

Open:open interface of OpenStack standard Open:private single manufacturer interface

3.2 The Key of NFV Network Build

3.3 The Key of NFV Network O&M

3.2 The Key of NFV Network Build

3.3 The Key of NFV Network O&M

MANO has become a tool for collaborative NFV in different fields

submit network requirement to network submitted to

Automation life Global resource management O&M and development integration

• Heterogeneous cloud, • With DevOps to achieve rapid

SLA Forecast analysis

Service Service management Policy engine

Application Disaster recovery plan

SLA Resource optimization algorithm

Virtual machines for high availability

NFVI Event report

 The Basic Concept of the NFV

 The Value and the architecture of the NFV

 The Key of the NFV network design, build, and O&M.

Potrebbero piacerti anche