Analysys Mason VNGN OSS Framework Sep2015 RMA16 RMA07

vNGN-OSS: an architectural framework for virtual network management and orchestration
RESEARCH STRATEGY REPORT
vNGN-OSS: AN ARCHITECTURAL FRAMEWORK FOR VIRTUAL

NETWORK MANAGEMENT AND ORCHESTRATION
SHANTHI RAVINDRAN, DANA COOPERSON and GLEN RAGOONANAN
analysysmason.com
Analysys Mason Limited 2015
About this report

This report analyses the changes that network virtualisation will
demand of communications service providers (CSPs) OSS
architecture so that virtual and hybrid next-generation networks
(vNGN)1 can be properly operated and maintained to meet
customer expectations and CSP business objectives for service
innovation in the digital economy. An expanded, more open control
layer architecture will create new technical requirements and
enable new products and services, which will change the vendor
competitor landscape and lead to changes to Analysys Masons
telecoms software market segmentation.
KEY QUESTIONS ANSWER E D IN THIS R EPOR T

How does a new approach to network design and operational systems
support CSPs digital economy business objectives?
What are the key characteristics and building blocks of an end-to-end
functional architecture that pulls together network function virtualisation
(NFV) management and orchestration (MANO) and OSS?
What are the business and technical requirements of a vNGN-OSS?

How does the vNGN-OSS affect segmentation in the software market?
What opportunities and threats do OSS evolution present to vendors?
How are different vendor types approaching the vNGN-OSS and related
professional service opportunities?
This report provides recommendations for those engaged in

transforming physical networks to hybrid or virtual networks.
The research in this report is based on several sources.
WHO NEEDS TO R EAD THIS R EPOR T
Analysys Masons extensive qualitative and quantitative

telecoms software market research.
OSS and infrastructure strategy, product marketing and management

executives in incumbent and new entrant vendor organisations, who
want a forward-looking analysis of market shifts to help them position
their products and services and develop their businesses.
Interviews with more than 10 software vendors regarding their

capabilities and strategies, and 20 CSPs regarding their needs
and expectations.
CTO and CIO staff in CSPs, who want a forward-looking analysis of vNGNOSS architecture in order to understand the functional blocks and how
they fit together so they can start building their evolution plan.
Secondary research into the enabling technologies and market

forces that are shaping this OSS evolution.
1
Strategy officers in CSPs, who want to understand how virtual networks

can be part of their platform for providing digital economy services.
Analysys Mason defines vNGN as hybrid (physical and virtual) network components because we do
not expect 100% virtualised networks to be possible. Network virtualisation includes network
function virtualisation (NFV), software-defined networking (SDN) and cloud computing.
CONTENTS
EXECUTIVE SUMMARY
CHANGES TO THE OSS ARCHITECTURE
NEW TECHNICAL REQUIREMENTS
CHANGES TO VENDOR COMPETITION AND OUR TAXONOMY
APPENDIX
ABOUT THE AUTHORS AND ANALYSYS MASON

Service
orchestration
Executive summary
Figure 1: Key capabilities of a virtual next-generation network OSS (vNGN-OSS) architecture

to manage multi-vendor hybrid networks
The success of CSPs in the digital economy depends on them

deploying a vNGN-OSS architecture that can dynamically and
holistically manage physical and virtual resources to support
service innovation at scale.1
CSPs will need to protect potential revenue of USD1.71 trillion in

20152 while attacking the wider market for digital economy
services. In order to do this, CSPs need to build new networks.
Dynamic
inventory
Analysys Masons proposed vNGN-OSS will enable CSPs to provide

digital economy services via NFV and SDN, and support traditional
fixed and mobile services. Important elements of a vNGN-OSS
include a dynamic master control inventory, a service
orchestration layer for process automation, and a management
and enforcement layer for resource orchestration and control.
Service
fulfilment
Service
assurance
We provide the following recommendations.

CSPs should understand that vNGN-OSS is critical to deploying
network virtualisation and must plan accordingly.
We expect vNGN-OSS to be less expensive and more agile than existing OSS. For more
information, see Analysys Masons Preparing for an OSS architecture that can support NFV, SDN
and established technologies. Available at www.analysysmason.com/Network-virtualisationApr2014.
USD1.7 trillion
worldwide
New elements
discussed in
this report
Source: Analysys Mason
For more information, see Analysys Masons Global telecoms market: interim forecast update
20142019. Available at www.analysysmason.com/GTF2015.
CSP revenue:
Physical and virtual

network management,
orchestration and control
Vendors should expect significant competition for vNGN-OSS

business, have a solid strategy for providing hybrid network
solutions and expect the competitive landscape to change.
1
Service
orchestration
An automated network that reacts and scales on demand will enable

digital economy services, but a design does not exist
Figure 2: An approach to building and operating networks for enabling digital economy
services
CSPs know they need a new approach to network operations in

order to enable new digital economy services, but the industry
has yet to agree the best way to integrate physicalvirtual
function management, control and orchestration to support
automation.
Present method of operations
Virtualisation should enable a flexible operations framework.

Creating this framework will be disruptive for CSPs, but will pay off
in terms of increased revenue through digital economy service
enablement services while supporting existing revenue streams in
a more cost-efficient manner.
Business and
operational objectives:
Service
assurance
Business and operational objectives specifically those for

improved service agility and enabling new digital economy revenue
should drive functional and technical requirements for the
integration and automation of hybrid physicalvirtual network
resource management, control and orchestration. Existing service
assurance, service fulfilment and network management systems
and virtual network NFV orchestration and SDN control systems
must interwork for networks to scale and change on demand.
?
vNGN-OSS
Service
fulfilment
ETSI has sketched out an architectural framework and functional

blocks for management and orchestration (MANO) of virtual
infrastructure, but has not specified the best flow through these
functional elements and existing OSS functional blocks. Therefore,
CSPs and their suppliers are debating and testing many different
approaches.
Future method of operations
Service agility
and revenue
Development and
maintenance costs
Integration of physical
and virtual resources
EMS/NMS
How to integrate
ETSI MANO and OSS?
API
API
PNFs
PNFs
PNFs
VNFs
CSPs need a vNGN-OSS that supports service agility enabled by

automated orchestration of a hybrid network
Figure 3: vNGN-OSS architecture components to enable agile and automated operations
Analysys Mason is proposing a vNGN-OSS architecture that

supports an agile operational model by allocating network
resources dynamically. The vNGN-OSS is likely to change OSS
product segmentation and the vendor competitive landscape.
Customer care and customer experience management

Closed-loop automation
Network virtualisation will support agile service creation,

provisioning and management that CSPs will need if they
implement a vNGN-OSS framework in order to become digital
service providers (DSPs). The framework must be built around a
unified, dynamic inventory that integrates with service fulfilment
and assurance functions and allows closed-loop planning; a
service orchestration layer within service fulfilment that allows for
conversion of customer-facing services (CFS) to resource-facing
services (RFS); and a separate network management and
enforcement layer that abstracts and controls the virtual and
physical infrastructure.
Inter-layer flows
for automated scaling and security
MASTER CONTROL
This report:
introduces Analysys Masons proposed vNGN-OSS framework,
its benefits compared with the present method of operations
and its fit with the ETSI MANO
Service
fulfilment
Service orchestration
PROCESS AUTOMATION
Network management and orchestration
VIM
SDN controllers
MANAGEMENT AND ENFORCEMENT
assesses vNGN-OSS business and operations drivers, technical

requirements and fulfilment and assurance process changes
vNGN
New or significantly
changed element
highlights changes to competition dynamics and product

segmentation in the OSS market.
Service
assurance
Evolving element
Recommendations
1
2
3
CSPs should understand that vNGN-OSS is critical to deploying commercial network virtualisation (NFV/SDN)
and should include OSS evolution plans as part of their network virtualisation initiative.
Creating a vNGN is hugely disruptive, but justified for CSPs that want to become digital service providers. An OSS
evolution plan that supports hybrid physicalvirtual resource management is essential to benefitting from
virtualisation. The first evolutionary step will be abstraction of existing OSS management through controllers,
orchestrators and infrastructure managers. CSPs should introduce new functions with a final blueprint in mind.
CSPs must move to an operations model that is supported by a dynamic inventory, and automated service and
network orchestration and control layers.
Business and operational goals must drive vNGN-OSS requirements. Evolving service fulfilment and service
assurance systems will use a dynamic, unified inventory to enable closed-loop automation. Multi-vendor network
and service orchestration layers should remain distinct in order to establish a clear demarcation, enhance
operational flexibility and revamp workflows and order-to-cash, plan-to-provision and trouble-to-resolve processes.
Vendors should expect significant competition for vNGN-OSS business, have a solid strategy for management
and control of hybrid networks, and expect product categories to change.
Virtualisation is lowering entry barriers to new software vendors. Incumbent vendors need to differentiate
themselves by providing multi-vendor capabilities, and new entrants must ensure that their NFV/SDN
virtualisation software integrates with existing systems. The OSS product landscape will change as network
management systems evolve.
CONTENTS
EXECUTIVE SUMMARY
APPENDIX
CSPs must open the control layer and move to a dynamic, automated
operations model to meet customers changing service demands
Figure 4: A simplified, layered software-controlled network architecture showing
interconnections
Networks have been managed historically by functions in the

control layer that are tightly coupled to both the service layer
above and the infrastructure layer below. The platform layer has
also been tightly coupled to the infrastructure that it supports.
Tight coupling of layers does not support scalability.
Telecoms
Development
layer
APIs
ICT applications development

APIs and middleware
APIs and middleware
Infrastructure
layer
Professional services
APIs
Platform layer
Connect
Management
Control layer
Co-existence, integration, transformation
APIs
Service layer
Service control
Multi-service IP control, policy control
Multi-service IP controllers
control, policy
Multi-technology
and control
OSS
Multi-technology controllers and OSS
Infrastructure support
Hypervisors, HA, network operating system
Storage, servers, networks
(core, distribution, access, IT, telecoms)
Access
Fixed
User layer
The goal of virtualisation is to make the network easily scalable.

However, efficient use of this scalable resource needs a flexible
and dynamic, automated, closed-loop operations model enabled
by an open control and orchestration layer. A properly designed
and implemented open control layer will be powered by a dynamic
inventory updated using real-time analytics to provide complete
network visibility. Such a control layer will provide CSPs with
several benefits: more-flexible and standardised, yet secure,
access to the platform and infrastructure layers; the ability to
innovate and offer a wider variety of services more quickly, either
directly or through trusted third-party developers; and support for
the evolution to becoming digital service providers (DSPs).
Service delivery
Application servers and delivery
Application servers and applications
The service and control layers, including the OSS, must evolve to
abstract the platform and network layers through controllers and
orchestrators, so that the network may then be tuned in near real
time in response to dynamic service demands. The evolved
networks expanded service and control layers must manage
virtual and physical infrastructure in concert, chaining them
together to create a robust end-user service.
HetNets
End users and end devices

CPE, mobile devices, tablets, laptops
Our recommended vNGN-OSS has an expanded, multi-vendor control layer

and improved automation, management and enforcement
Customer experience
management
Customer care
Closed-loop automation
APIs
Master
control
APIs
Service fulfilment
Process
automation
APIs
Service assurance
APIs
vNGN-OSS
APIs
Service orchestration layer

APIs
Network management
systems (NMS)
Management
and
enforcement
Network orchestration layer (VNFM, NFVO)

APIs
APIs
Established and
unchanged element
Cloud
manager
APIs
VIM
VIM
SDN controllers
PNFs
VNFs
VNFs
PNFs
PNFs
VNI
Evolving element
APIs
APIs
APIs
Network
and IT
Key:
Integrate
or merge
SDN-enabled
Storage
compute
network
Analytics (for closed-loop automation)
BSS
Security (for operations users, VNFs and system automation)
vNGN-OSS
FUNCTION
Policy (for orchestration)
Figure 5: vNGN-OSS functional architecture
New or significantly
changed element
Note: NFVO = NFV orchestrator; PNF = physical network function; VIM = virtual infrastructure manager; VNF = virtual network function; VNFM = VNF manager; VNI = virtual network infrastructure.
10
vNGN-OSS functional blocks explained: Master control and process

automation
Figure 6a: vNGN-OSS functions
vNGN-OSS function
Master control:
service fulfilment
Functional details
Information model and data
OSS improvements
End-to-end service fulfilment across physical and virtual network

resources:
Uses global service and

resource inventory database
(as below)
Closed-loop fulfilment and

assurance
Global service and resource

database comprising
customer service, network
service and network
resource catalogues;
policies; and service models
and their instances
Single inventory view
verification against inventory before activation of the customer order

provision of service models to service assurance function
Dynamic inventory management using network resource data
discovered from the network:
Master control:
inventory
single true inventory should contain all services and network

resources in use
continuous optimisation logic
data is made available to all applications requiring it
Process automation:
service orchestration
layer
Master control:
service assurance
Automated service orchestration across physical and virtual network

resources:
Customer service, network

service and network
resource catalogues and
conversion of CFS to RFS as per TM Forums system information data
policies
(SID) models
Automated capacity
planning and augmentation
Data integrity and

consistency
OSS abstraction: clear

OSS/network demarcation
Dynamic service
orchestration and inventory
discovery updates
process automation for activation, inventory discovery and update,

and localised lifecycle service management
Network service mapping

models
End-to-end service assurance across physical and virtual network

resources, including virtual probes:
Historical fault, event and

performance data
Closed-loop fulfilment and

assurance
provision of data to service fulfilment function for capacity

verification and planning
Real-time network analytics

data
Automated capacity
planning and augmentation
security management of VNFs

Key:
Evolving element
New or significantly changed element
11
vNGN-OSS functional blocks explained: Management and enforcement

Figure 6b: vNGN-OSS functions
Functional details
Management and
enforcement:
network
orchestration
Network service orchestration across physical and virtual network

Network service catalogues,
resources:
policies and instances
conversion of network service into its component VNFs and
Network service to network
networking resources
resource mapping (VNF
lifecycle management of network service composed of a combination
forwarding graph)
of VNFs and networking resources
Network-related
network management for virtual network functions
management information
base (MIB)
South-bound network
abstraction
Dynamic, low-latency,
automated validated and
pre-tested network service
build, to eliminate
deployment cost and time
FCAPS management for physical network functions:

interworks and communicates with network orchestrator to support
orchestration across physical and virtual network resources
MIB for the physical network

elements and network
hierarchical model
Management of hybrid
network in conjunction with
network orchestrator
Management and
enforcement:
cloud manager
Lifecycle management and monitoring of IT data centre cloud resources,

except SDN resources
sets up cloud resources in response to command from network
orchestrator
Cloud management
database (CMDB)
Scaling of cloud resources
Management and
enforcement:
virtual infrastructure
manager (VIM) and
SDN controller
VIM: Lifecycle management and monitoring of NFV infrastructure (NFVI)

scales NFVI in response to command from network orchestrator
SDN controller: Lifecycle management and monitoring of SDN-enabled
infrastructure
sets up SDN networking resources in response to command from
network orchestrator
NFVI, SDN resource

catalogues, policies and
instances
Scaling of NFVI resources

Scaling of SDN resources
Management and
enforcement:
network
management
OSS improvements
vNGN-OSS function
Key:
Evolving element
12
ETSI MANO functionality is deep, but narrow compared with the wider
vNGN-OSS architecture needed for complete NFV/SDN deployments
Figure 7: ETSI MANO in the wider vNGN-OSS architecture
ETSI MANO functional blocks need to be part of an overall vNGNOSS, in order to meet the MANO objectives of dynamic network
scaling based on customer service demands.
SDP
ETSI MANO provides an architectural framework and functional

blocks for network service orchestration, where a network service
is defined as a combination of network functions (VNFs and PNFs)
grouped together and interconnected to function and scale as a
single logical entity. ETSI MANO assumes interconnection with
existing OSS functional blocks of service assurance (SA) systems,
service fulfilment (SF) systems and network management systems
(NMS) to provide functionality that falls outside of its domain, but
it does not specify the best flow through these functional
elements.
SF
SA
Dynamic
inventory
vNGN-OSS
Service orchestration
Analysys Masons recommended vNGN-OSS architecture provides

the capability to link the ETSI MANO functional blocks into the
overall OSS architecture. The vNGN-OSS architecture provides a
way to establish clear abstraction for demarcation of service and
network layers through the service and network orchestration
functional blocks. It also provides for a common information
model and data to be updated and shared across the vNGN-OSS
through a dynamic inventory that is federated for access.
Infrastructure
Customer product
layer
Customer service
layer
NMS
NFVO
Network service level
SDN
controller
VNFM
VNF level
Cloud
manager
VIM
Network
orchestration
The resulting architecture provides the functional components

necessary to create service agility and operational flexibility, and
to obtain the maximum benefits of virtual infrastructure.
BSS
Infrastructure level
MANO
PNF
VNF
Network
NFVI
Compute, storage, networking
Network function
(logical resource)
Infrastructure
(physical resource)
13
CONTENTS
EXECUTIVE SUMMARY
APPENDIX
14
CSPs business and operational objectives create requirements that

drive Analysys Masons vNGN-OSS functional architecture
Figure 8: The relationship between CSPs business and operational objectives and functional and technical requirements supported by the vNGN-OSS architecture
Business objectives
Reduce costs
Increase revenue
Operational objectives
Reduce development and maintenance costs of OSS

while maintaining service quality
Increase service agility to deploy high-value services

quickly with superior customer experience
Functional requirements
Reduce complexity of OSS platforms and deployment

through rationalisation
Reduce time and cost of integration through open
interfaces and hardware and software interoperability
standards
Increase operations automation to enable
convergence of network and IT planning, deployment,
operations and maintenance
Orchestrate and manage physical and virtual

resources to support existing and new services
Encompass delivery and lifecycle management of
services, including management of associated
resources
Provide near-real-time monitoring and control of
operations with secure, policy-controlled automation
and analytics
Technical requirements
vNGNOSS
A single end-to-end view and catalogue-driven service delivery and lifecycle management
Open interfaces and more standardisation for an off-the-shelf, plug-and-play infrastructure
A master policy database that can configure the VNFs based on pre-determined and approved network and
service designs and configurations
Improved security administration, hierarchy and auditing functions for manual and automated tasks
VNFs that provide information to the OSS or orchestrator for seamless auto-discovery and configuration
Near-real-time service assurance and analytics to improve network predictability, with open- and closed-loop
automation workflow options
New simulators and emulators of OSS features to pre-test the results of changes before deployment
15
New eTOM processes, workflows and associated software technologies

form the foundation for vNGN-OSS processes
Figure 9: Four main functions for workflows and three main processes1 that are modified for
vNGN-OSS
Customer
request
Service
translation
Products
Customer-facing
service (CFS)
Network
service
translation
Resource-facing
service (RFS)
Automation and orchestration, a dynamic inventory and real-time

analytics enable the implementation of new automated, closedloop, dynamic workflows for the three key eTOM processes: orderto-cash (O2C), plan-to-provision (P2P) and time-to-resolve (T2R).
Network
activation
Virtualisation allows the dynamic allocation of network resources

to support varying customer service demands. This requires
automation of the O2C, P2P and T2R processes.
Network resource
VNF and PNF
Order-to-cash: dynamic service/network scaling
Resource assignment and prioritisation, provisioning/deactivation of

resources for customer services
NEW: Automated scaling up and down of network resources as per
changing customer service demands
Network orchestration, implemented in the management and

enforcement layer, and service orchestration, implemented in
the master control layer, enable automated network scaling.
It also requires a dynamic, single and true inventory to support the
automated scaling in the O2C process, automated provisioning in
the P2P process and automated assurance in the T2R process.
Plan-to-provision: two control paths
Top-down (classic): Manual or static network performance and

optimisation (NPO), infrastructure defragmentation and optimisation,
procurement initiation
Bottom-up (NEW): Continuous, autonomous network refresh through
network build and discovery, prompting manual action
Service fulfilment manages the update of the inventory through

the usual top-down manual update process and also through
auto-discovery.
Real-time network analytics data is required for the T2R process
for automated trouble management and for automated network
capacity augmentation in the P2P process.
Trouble-to-resolve: split in two paths
NEW: Granular and near real-time network analytics and for automated
trouble resolution/recommended actions, with historical
report/playback to resolve issues
NEW: Update to start automated resource provisioning
Service assurance manages the collection of real-time

analytics.

1
Based on three key macro TM Forums eTOM processes.
16
ETSI MANO describes reference points that did not exist in the physical
domain with NMS, which should encourage multi-vendor interfaces
Figure 10: Four MANO multi-vendor north/south interfaces and one east/west interface
reference points
ETSI MANO describes but does not specify objectives,

functional blocks and interface reference points (single and multivendor). This encourages innovation, but may hamper industry
coalescence as CSPs implement variations of the MANO
architecture with interfaces that suit their scale and domains.
OSS (service
fulfilment)
Multi-vendor south-bound interfaces at the NMS were not possible

in the past due to lack of reference points for integration. MANO
has provided these, encouraging multi-vendor interfaces primarily
between NFVOOSS (1); NFVOVIM (2); VIMVNFs (3); and VNFs
NFVI (4). An east-west multi-vendor interface within the network
orchestration layer (5) is also likely. Reference points within the
orchestration layer enable industry groups and ecosystems to
build implementations that can become de-facto standards. Three
multi-vendor scenarios are possible. The third is most likely.
OSS (service
assurance)
5
Network
orchestration
Network
orchestration
Cloud
managers
Scenario 1: CSPs successfully commoditise VNFs and do their

own management and enforcement. A few of the largest Tier 1
companies may try this, but it is unlikely to drive the entire market.
VIMs
SDN
controllers
VNFs
VNFs
VNFs
PNFs
NFVI
SDNenabled
Scenario 2: New non-NEP orchestrator vendors transform the

industry. A few new entrants may survive as standalone entities,
but most are likely to be acquired or will fail to thrive.
Scenario 3: NEPs successfully extend their physical domain NMS

strategy to multi-vendor operation for virtual domains. This
scenario assumes that CSPs exert pressure on their NEPs or that
IT vendors/SIs enter the NEPs domain.
Service
orchestration
17
CONTENTS
EXECUTIVE SUMMARY
APPENDIX
18
The industry transition lowers barriers to entry, incentivises new entrants

and encourages large CSPs to look beyond incumbent suppliers
Figure 11: Supplierbuyer power dynamics in vNGN-OSS1
Buyers: CSPs need vNGN-OSS for service agility, but supplier

competition enables large CSPs to influence market and
ecosystem development and encourage the creation of de facto
standards. Some Tier 1 CSPs will become their own vNGN-OSS
integrators and suppliers, which will reduce the vendor opportunity.
Start-ups and IT vendors

could disrupt the market
with open, multi-vendor
solutions
Incumbent suppliers: Established NEPs and OSS vendors have

revenue streams to protect. Large incumbent suppliers are costly
to displace within their domains, so they will maintain an
advantage over new entrants. However, telecoms is a highly
competitive industry and open-source software is an unknown
element that might be as much a threat to the status quo as an
opportunity. IT vendors experience of data centre virtualisation is
a plus, but their lack of telecoms experience is a minus.
Tier 1 CSPs will

influence standards
and ecosystem
creation
vNGN-OSS
market
competition
Supplier
power
New entrant suppliers: Market dislocation has lowered entry

barriers. CSPs are interested in fresh approaches and incumbents
vendors installed base, economies of scale and product
differentiation are less relevant in the digital economy. New
entrants can gain access to ecosystems for distribution IT
vendors expanding into telecoms may already have ecosystems to
tap. Managing the embedded base of PNFs is critical so new
entrants must have a hybrid strategy.
Incumbent NEPs
and OSS vendors
will build from their
installed base and
will be hard to
displace
High
Software segmentation will evolve: Changing CSP requirements

and competitive dynamics will lead to new product approaches
that will restructure established software markets.
Threat of
substitutes
Medium
Buyer
power
Some CSPs will

build rather than
buy. Open-source
solutions create
uncertainty for
incumbent vendors
Threat of
new entrants
19
Based on Michael Porters five forces model of competition.
The service fulfilment segment will become more dynamic and research
will focus on automated service orchestration
Figure 12a: Changes to the service fulfilment systems segment
Figure 12b: Changes to the focus of the service fulfilment systems segment, open questions
and the impact on Analysys Masons research
SERVICE
FULFILMENT
SERVICE
FULFILMENT
ORDER MANAGEMENT
ORDER MANAGEMENT
Most likely segment shifts

Orchestration adds to ordering and activation
Inventory is dynamically updated
Engineering systems evolve to closed loop
SERVICE ORCHESTRATION
INVENTORY MANAGEMENT
INVENTORY MANAGEMENT
ACTIVATION
ACTIVATION
ENGINEERING SYSTEMS
ENGINEERING SYSTEMS
PRESENT
FUTURE
Biggest open questions

How deep can service orchestration go into
resource orchestration?
Will inventory become a single truth point?
Research impact
Strategy reports will focus on the evolution of
service orchestration for hybrid networks
Virtualisation coverage added to segments

20
Service assurance is moving towards closed-loop automation

Figure 13a: Changes to the service assurance systems segment
Figure 13b: Changes to the focus of the service assurance systems segment, open questions
and the impact on Analysys Masons research
SERVICE
ASSURANCE
SERVICE
ASSURANCE
SERVICE MANAGEMENT
SERVICE MANAGEMENT
FAULT AND EVENT

MANAGEMENT
UNIFIED vNGN MONITORING

(N-PM, A-PM, FM)1
PERFORMANCE
MONITORING
WORKFORCE AUTOMATION
WORKFORCE AUTOMATION
PROBE SYSTEMS
(PHYSICAL AND VIRTUAL)
PROBE SYSTEMS
SECURITY ANALYTICS AND

ASSURANCE
PRESENT
FUTURE
PM/FM
PM/FMwill
willmerge
merge to
to unified
unified vNGN
vNGN monitoring
monitoring
vProbes
will
enable
better
economies
of scale
Virtual probes will enable better economies
of
scale
Assurance
functions will move to near real time
Assurance functions will move to near real time
Biggest
open
questions
Will security
become
a key
assurance function?
Will will
security
become
a key assurance
How
assurance
interlock
with fulfilment to
function?
provide
closed loop assurance?
How will assurance interlock with fulfilment to
provide closed-loop assurance?
Research impact
Strategy reports will focus on real-time operation

Strategy reports will focus on real-time
and
SA in and
NFV SA
environments
operation
in NFV environments
New
segments
New segments added
added to
to coverage
coverage

1
N-PM = network performance monitoring; A-PM = application performance monitoring for VNFs;
FM = fault and event management. Includes real-time analytics.
21
Network management evolves to orchestration and SDN control as an

essential enabler for virtual/hybrid network automation
Figure 14a: Changes to the network management systems segment
Figure14b: Changes to the focus of the network management systems segment, open
questions and the impact on Analysys Masons research
NETWORK
MANAGEMENT
SYSTEMS
NETWORK
ORCHESTRATION
AND MANAGEMENT
SYSTEMS
MOBILE
(formerly network management

systems segment)

Focuses on NMS evolution for hybrid networks
Controllers, orchestrators, and VIM are
essential parts of network management
EMS/NMS
RESIDENTIAL BROADBAND
NETWORK
ORCHESTRATORS
BUSINESS DATA SYSTEMS
SDN CONTROLLERS
PSTN
VIRTUAL INFRASTRUCTURE
MANAGERS
PRESENT
FUTURE

How will open-source ecosystems affect
network orchestration and management
systems?
Will network orchestration and NMS merge?
Will multi-vendor network orchestration
succeed EMS/NMS?
Research impact
Strategy reports will focus on hybrid networks
and new management and enforcement tools
New segments added to coverage

22
Cloud transformation will be an important component of telecoms

software professional services for an industry in transition
Figure 15a: Changes to the professional services segment
PRESENT
PROFESSIONAL SERVICES
BUSINESS
CONSULTING
DESIGN CONSULTING
PRODUCT-RELATED
SERVICES
SYSTEMS
INTEGRATION
CUSTOM
DEVELOPMENT
OUTSOURCED
OPERATIONS
HOSTED MANAGED
SERVICES
FUTURE
PROFESSIONAL SERVICES
BUSINESS
CONSULTING
DESIGN CONSULTING
CLOUD TRANSFORMATION SERVICES

Cloud transformation services
PRODUCT-RELATED
SYSTEMS
CUSTOM
OUTSOURCED
SERVICES
INTEGRATION
DEVELOPMENT
OPERATIONS
HOSTED MANAGED
SERVICES
Figure 15b: Changes to the focus of the professional services segment, open questions and the impact on Analysys Masons research

Will innovative cloud services help enable/drive
virtualisation?
Will systems integration services be key?

Co-existence, integration and transformation
services for SDN/NFV/cloud become a growth
area across all segments
Research impact
More focused coverage of virtualisation-related
professional services coupled with high-level
tracking of overall TSPS
23
Key questions that the industry will answer during the 10-year transition
to vNGNs
Figure 16: Unanswered questions about the future of virtualised networks
Question
Analysys Mason comments
Will multi-vendor management really

happen this time?
Only if buyers are more serious about multi-vendor management than they have been in the past or if new entrant
vendors force the issue. If so, NMS and network orchestration may merge into a single infrastructure abstraction layer.
Will global resource management be

done at the network orchestrator or
service orchestrator layer?
MANO assumes that it stands alone and, therefore, has global resource management responsibility. However, global
management is probably required at a higher level to work across geographical and other domains and the service
orchestrator may lack needed domain knowledge.
Will there be a hierarchy of orchestrators

and controllers?
Probably, yes a hierarchy and east-west interfaces are likely to be needed for large networks, to properly secure and
guarantee performance in the network, depending on the size and complexity of a specific CSP.
How will inventory update and access be

managed?
The inventory is likely to be a master back-end completely managed by the service fulfilment systems,
with several front-end applications accessing it.
What degree of flow-through service

fulfilment and service assurance
automation/integration will be achieved?
A high level of automation in the P2P and O2C process in service fulfilment and T2R process in service assurance and
closed-loop service model updates between service fulfilment and service assurance depend on dynamic inventory
data model flexibility and service fulfilmentservice assurance open API integration.
Will cloud management and network

orchestrators merge?
The cloud managers that control VNI within enterprise data centres might be extended to orchestrate VNFs across CSP
networks or these two classes of managers/orchestrators could remain separate and interact. OpenStack is being
extended for CSPs requirements, which are more stringent and distinct from enterprise requirements.
Will the multi-vendor VIM supersede

VNFMs?
Some vendors (for example, Amdocs) have coupled the VNFM to the element manager. ETSI MANO shows VNFM as
separate from, and sitting between, the NFVO and VIM, and separate from and connected to both the EMS and the
VNF. The market will have to tease out the best approach.
How will the interface development and

interoperability verification process
unfold?
We expect that a combination of the IETF and open source approaches will be best. De-facto standards could also
develop as vendors and CSPs develop and test applications via the TM Forum and other groups (for example, the Open
Platform for NFV (OPNFV) Project.
24
CONTENTS
EXECUTIVE SUMMARY
APPENDIX
25
vNGN-OSS functional blocks explained: Master control

Figure 17a: vNGN-OSS architecture control layer functions, information model/data and benefit (1):
vNGN-OSS
functions
Master control:
service fulfilment as a
whole
Master control:
inventory
Functional details
End to end service fulfilment across xNFs :

service fulfilment across physical and virtual infrastructure
initiation of service activation across the network through service
orchestrators, after verification with the inventory
mediation across service orchestrators
create, update and maintain a single true inventory
capacity planning logic, with simulators and emulators
dynamic update of service models for service assurance
Dynamic inventory management Discover, activate, audit,

optimise:
single true inventory of services and resources in use
customer service (CFS) to network service (RFS) mapping rules
continuous optimisation logic
geographic inventory data federation and management
authorisation for use, of data discovered from network
make data available to other functional modules
Key:
Evolving element
26
Uses and management of the global

service and resource inventory
database (see below)
Global service and resource

database consisting of customer
service, network service and network
resource catalogues, policies and
service models and their instances
Service and resource models and
their mapping as per TMForums SID
models
Federated data created and
discovered from network
Data from SA for planning
OSS improvements
Closed loop fulfilment

and assurance
Automated capacity
planning and
augmentation
Single inventory view

and data integrity and
consistency
vNGN-OSS functional blocks explained: Master control and process

automation
Figure 17b: vNGN-OSS architecture control layer functions, information model/data and benefit (2):
vNGN-OSS
functions
Process
automation:
service
orchestration
Master control:
service assurance
Key:
Functional details
Information model and

data
Dynamic service orchestration across xNFs: Activate, provision:

Mapping from customer facing service (CFS) to resource facing service (RFS)
as per TM Forum SID models
Network service order generation and validation
Process automation for activation
Dynamic inventory discovery update
Automated execution of validated self-provisioning customer service requests
Hierarchical service orchestration management for large network (in terms of
nodes and geographical reach)
Communicates with the Network orchestrator to provision services, to perform
inventory updates and to manage localised lifecycle service management
End to end service assurance across xNFs Assure:

Service assurance across physical and virtual infrastructure
Unified monitoring of vNGN encompassing fault management, network
performance monitoring and application performance monitoring
End to end service management
Deployment of virtual probes adjunct to VNFs
Workforce automation of test and turn-up and service deployment
Fault and event logger, and player for advanced root cause analysis
Near real-time network analytics collection and analysis
Managing the security of the VNFs and service chains throughout their
lifecycle
Evolving element
27
OSS improvements
Customer service,
network service and
network resource
catalogues and policies
Network service
mapping models from
inventory
Physical network
element data from NMS
Service models from

inventory and their
instances
Historical fault / event /
performance data
Real-time network
analytics data
Periodic data received
from NMS and DPI
probes
Closed loop
fulfilment and
assurance
Automated capacity
planning and
augmentation
North-bound OSS
abstraction clear
OSS / Network
demarcation
Dynamic service
orchestration and
inventory discovery
updates
Resilient and
scalable, new service
orchestrators can be
instantiated as
needed
Elements of an expanded, multivendor control layer: Management and

enforcement (1)
Figure 17c: vNGN-OSS architecture control layer functions, information model/data and benefit (3)
vNGN-OSS
functions
Enforcement and
management:
network
orchestration
Enforcement and
management:
network
management
Key:
Functional details
Information model
and data
Network service orchestration across VNFs and PNFs orchestrate, assure, scale:
mapping of network services to resources - VNFs / PNFs
network service instantiation and monitoring
abstraction of network to SF and SA (north-bound)
mediation across VIMs, SDN controllers and cloud managers (south-bound)
hierarchical management for large networks and mediation across to other
orchestrators (east-west)
scaling and load balancing across VNFs
application-specific VNFs
self-healing at network service level
security enforcement in concert with service assurance
Network function management: VNFM (for VNFs)
VNF discovery - input to master inventory
VNF lifecycle management & monitoring
self-healing at VNF level
low latency and high availability network management
localised assurance, analytics and automation
Network function management for PNFs

communication with Network orchestrators to assist in management of network
services that are constructed across hybrid networks
provisioning and activation of network elements, on direction from SO
traditional FCAPs management for physical network functions
discovery of network elements for population into inventory
low latency and high availability network management
localised assurance, analytics and automation
Evolving element
28
OSS improvements
Network service
catalogues, policies
and instances
Network service to
network resource
mapping (VNF
forwarding graph)
xNF catalogues,
MIB (Management
information base) for
the network elements
and network
hierarchical model
NETCONF, YANG, IETF,
etc.
MIB for the physical

network elements and
physical network
hierarchical model
South-bound network
abstraction
Dynamic, low latency,
automated validated
and pre-tested network
service build, eliminate
deployment cost and
time
Network service selfhealing in a self
contained layer for
network to function
without OSS
intervention
Management of hybrid
network in conjunction
with network
orchestrator
Elements of an expanded, multivendor control layer: Management and

enforcement (2)
Figure 17d: vNGN-OSS architecture control layer functions, information model/data and benefit (4)
vNGN-OSS
functions
Enforcement and
management:
virtual
Infrastructure
manager (VIM)
and SDN
Controller
Enforcement and
management:
cloud manager
Key:
Functional details
VIM
lifecycle management and monitoring of NFVI
scaling of NFVI in response to commands from the network orchestrator
self-healing at the NFVI level
SDN controller
lifecycle management and monitoring of SDN-enabled infrastructure
(OpenFlow, OpenDaylight and other intra- / inter- data centre and WAN
connectivity)
sets up SDN networking resources in response to command from network
orchestrator
self-healing at SDN networking level
.
Lifecycle management and monitoring of IT data centre cloud resources,

except SDN networking resources
Sets up cloud resources in response to command from network
orchestrator
Evolving element
NFVI, SDN resource catalogues,

OSS improvements
Cloud management database

(CMDB)
Scaling of NFVI
resources
Scaling of SDN
resources
Scaling of cloud
resources
Note: Security, policy and analytics are capabilities that exist within the various functions in the expanded, multivendor control layer but are not themselves separate
architectural elements. Requirements details for security, policy and analytics is outside the scope of this report, but will be tackled by Analysys Mason in subsequent
reports.
29
CONTENTS
EXECUTIVE SUMMARY
APPENDIX
30
About the authors

Shanthi Ravindran (Senior Analyst) is a member of Analysys Masons Telecoms Software research team, focusing on OSS, BSS and SDP for
AsiaPacific customers. She leads the Network Orchestration programme. Shanthi has more than 20 years of experience at Tier 1
infrastructure vendors, working on design, deployment and operations of wireless and broadband networks for operators across the Asia
Pacific region, starting with the first GSM and CDMA networks in Malaysia and Singapore, and continuing on through to 3G and 4G networks.
Dana Cooperson (Research Director) is the research director for Analysys Masons network-focused software research programmes. Her
area of expertise is intelligent fixed and mobile network infrastructure. Her goal is to help customers strengthen their link in the
communications value chain while evolving their business operations to benefit from, rather than be threatened by, shifts in the market. The
key network infrastructure trends Dana focuses on include the integration of communications and IT assets and the drive towards softwarecontrolled, virtual networking.
Glen Ragoonanan (Principal Analyst) is the lead analyst for Analysys Masons Infrastructure Solutions, Service Delivery Platforms and
Software-Controlled Networking research programmes. He joined Analysys Mason in 2008 and has worked as a consultant on projects on nextgeneration IT and telecoms networks, systems and technologies for incumbents, new entrants, private companies, regulators and public-sector
clients. His primary areas of specialisation include operations and business support systems (OSS/BSS) solution architecture and integration for
business process re-engineering, business process optimisation, business continuity planning, procurement and outsourcing operations and
strategies.
31
About Analysys Mason

Knowing whats going on is one thing. Understanding how to take advantage of events is quite another. Our ability to understand the
complex workings of telecoms, media and technology (TMT) industries and draw practical conclusions, based on the specialist
knowledge of our people, is what sets Analysys Mason apart. We deliver our key services via two channels: consulting and research.
Consulting
Research
We analyse, track and forecast the different
services accessed by consumers and
enterprises, as well as the software,
infrastructure and technology
delivering those services.
Research clients benefit from
regular and timely intelligence
in addition to direct access to
our team of expert analysts.
Our dedicated Custom Research
team undertakes specialised
and bespoke projects for clients.
For more information, please visit
www.analysysmason.com/research
Our focus is exclusively on TMT.

Consumer
and SME
services
Regulation
and policy
Digital
economy
Regional
markets
Performance
improvement
Network
technologies
Telecoms
software
We support multi-billion dollar investments,

advise clients on regulatory matters,
provide spectrum valuation and auction
support, and advise on operational
performance, business planning
and strategy.
We have developed rigorous

methodologies that deliver tangible
results for clients around the world.
Transaction
support
Strategy
and planning
32
For more information, please visit

www.analysysmason.com/consulting
Research from Analysys Mason

We provide dedicated coverage of developments in the telecoms, media and technology (TMT) sectors, through a
range of research programmes that focus on different services and regions of the world.
PROGRAMMES
PROGRAMMES
Fixed Networks
Wireless Networks
Spectrum
Research
portfolio
PROGRAMMES
Service Assurance
Customer Experience Management
Customer Care
Revenue Management
Analytics
Network Orchestration
Software-Controlled Networking
Service Delivery Platforms
Service Fulfilment
Telecoms Software Market Shares
Telecoms Software Forecasts
Network
technologies
Telecoms
software
Mobile Services
Mobile Devices
Fixed Broadband and Multi-Play
SME Strategies
Consumer
and SME
services
Digital
economy
Regional
markets
To find out more, please visit www.analysysmason.com/research
PROGRAMMES
33
Digital Economy Strategies

Digital Economy Platforms
Future Comms and Media
IoT and M2M Solutions
PROGRAMMES
Global Telecoms Forecasts
AsiaPacific
The Middle East and Africa
European Country Reports
European Core Forecasts
European Telecoms Market Matrix
Consulting from Analysys Mason

For 30 years, our consultants have been bringing the benefits of applied intelligence to enable clients around the
world to make the most of their opportunities.
EXPERTISE
EXPERTISE
Performance analysis
Radio spectrum
auction support
Technology optimisation
Commercial excellence
Consulting
portfolio
Transformation services
Performance
improvement
Spectrum
policy and
auction
support
EXPERTISE
Policy development and response
Margin squeeze tests
Analysing regulatory accounts
Expert legal support
Regulation
Media regulation
Postal sector costing, pricing and regulation
Transaction
support
EXPERTISE
Market research
Market analysis
Regulatory economic costing
EXPERTISE
Net cost of universal service
Commercial due diligence

Regulatory due diligence
Technical due diligence
To find out more, please visit www.analysysmason.com/consulting
Radio spectrum
management
34
Strategy
and
planning
Business strategy and planning

Market sizing and forecasting
Benchmarking and best practice
National and regional broadband
strategy and implementation
PUBLISHED BY ANALYSYS MASON LIMITED IN SEPTEMBER 2015

Bush House North West Wing Aldwych London WC2B 4PJ UK
Tel: +44 (0)20 7395 9000 Fax: +44 (0)20 7395 9001 Email: research@analysysmason.com www.analysysmason.com/research Registered in England No. 5177472
Analysys Mason Limited 2015. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means electronic,
mechanical, photocopying, recording or otherwise without the prior written permission of the publisher.
Figures and projections contained in this report are based on publicly available information only and are produced by the Research Division of Analysys Mason Limited independently of any
client-specific work within Analysys Mason Limited. The opinions expressed are those of the stated authors only.
Analysys Mason Limited recognises that many terms appearing in this report are proprietary; all such trademarks are acknowledged and every effort has been made to indicate them by the
normal UK publishing practice of capitalisation. However, the presence of a term, in whatever form, does not affect its legal status as a trademark.
Analysys Mason Limited maintains that all reasonable care and skill have been used in the compilation of this publication. However, Analysys Mason Limited shall not be under any liability for
loss or damage (including consequential loss) whatsoever or howsoever arising as a result of the use of this publication by the customer, his servants, agents or any third party.

Analysys Mason VNGN OSS Framework Sep2015 RMA16 RMA07

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Analysys Mason VNGN OSS Framework Sep2015 RMA16 RMA07

Încărcat de

Drepturi de autor:

Formate disponibile

vNGN-OSS: an architectural framework for virtual network management and orchestration

RESEARCH STRATEGY REPORT

vNGN-OSS: AN ARCHITECTURAL FRAMEWORK FOR VIRTUAL

Analysys Mason Limited 2015

vNGN-OSS: an architectural framework for virtual network management and orchestration

About this report

KEY QUESTIONS ANSWER E D IN THIS R EPOR T

What are the business and technical requirements of a vNGN-OSS?

This report provides recommendations for those engaged in

WHO NEEDS TO R EAD THIS R EPOR T

Analysys Masons extensive qualitative and quantitative

OSS and infrastructure strategy, product marketing and management

Interviews with more than 10 software vendors regarding their

Secondary research into the enabling technologies and market

Strategy officers in CSPs, who want to understand how virtual networks

Analysys Mason Limited 2015

vNGN-OSS: an architectural framework for virtual network management and orchestration

Analysys Mason Limited 2015

vNGN-OSS: an architectural framework for virtual network management and orchestration

Figure 1: Key capabilities of a virtual next-generation network OSS (vNGN-OSS) architecture

The success of CSPs in the digital economy depends on them

CSPs will need to protect potential revenue of USD1.71 trillion in

Analysys Masons proposed vNGN-OSS will enable CSPs to provide

We provide the following recommendations.

Analysys Mason Limited 2015

Physical and virtual

Vendors should expect significant competition for vNGN-OSS

vNGN-OSS: an architectural framework for virtual network management and orchestration

An automated network that reacts and scales on demand will enable

CSPs know they need a new approach to network operations in

Present method of operations

Virtualisation should enable a flexible operations framework.

Analysys Mason Limited 2015

Business and operational objectives specifically those for

ETSI has sketched out an architectural framework and functional

Future method of operations

vNGN-OSS: an architectural framework for virtual network management and orchestration

CSPs need a vNGN-OSS that supports service agility enabled by

Analysys Mason is proposing a vNGN-OSS architecture that

Customer care and customer experience management

Network virtualisation will support agile service creation,

MANAGEMENT AND ENFORCEMENT

assesses vNGN-OSS business and operations drivers, technical

highlights changes to competition dynamics and product

Analysys Mason Limited 2015

vNGN-OSS: an architectural framework for virtual network management and orchestration

Analysys Mason Limited 2015

vNGN-OSS: an architectural framework for virtual network management and orchestration

Analysys Mason Limited 2015

vNGN-OSS: an architectural framework for virtual network management and orchestration

Networks have been managed historically by functions in the

ICT applications development

Co-existence, integration, transformation

The goal of virtualisation is to make the network easily scalable.

End users and end devices

Analysys Mason Limited 2015

vNGN-OSS: an architectural framework for virtual network management and orchestration

Our recommended vNGN-OSS has an expanded, multi-vendor control layer

Service orchestration layer

Network orchestration layer (VNFM, NFVO)

Analytics (for closed-loop automation)

Security (for operations users, VNFs and system automation)

Policy (for orchestration)