Upload
others
View
3
Download
0
Embed Size (px)
Citation preview
© 2019 TM Forum | 1#TMFDigital
Senior Engineer, Sri Lanka Telecom
Anuradha Udunuwara
Achieving real-time, dynamic orchestration across a hybrid infrastructure
21st January 2020, Dubai
© 2019 TM Forum | 2#TMFDigital
Source: Global 4G-LTE Forecasts: 2010–2020, GSMA Intelligence Source: 5G Market Snapshot, January 2020, GSA
© 2019 TM Forum | 3#TMFDigital
The World of “Mobile”
© 2019 TM Forum | 4#TMFDigital
• Ability to have different applications running across a network with respective QoSparameters is actually achieved through network slicing.
• Required capabilities like virtualization, automation, agility and flexibility are achieved through network softwarization (SDN, NFV and Cloud).
• 5G is not the only use case for network transformation and softwarization.
• As operators transform themselves from CSPs to future DSPs, they realize that they need both agility and flexibility which is only possible in software.
• Hence the softwarization of telco networks and systems.
Beyond 5G for Network Transformation
© 2019 TM Forum | 5#TMFDigital
Network Transformation with Lifecycle Automation
• This has to also be coupled with end-to-end dynamic service orchestration.
• Two notable initiatives in terms of standardizing and supporting this industry requirement are the works of MEF and TM Forum.
• MEF has developed LSO (Lifecycle Services Orchestration) specifications with open APIs to automate the entire lifecycle for services orchestrated across multiple provider networks and multiple technology domains within a provider network and across provider networks.
• TM Forum has developed the TM Forum Open API program.
• We see the industry is adopting these common language frameworks.
© 2019 TM Forum | 6#TMFDigital
Orchestration
Source: Photo by Manuel Nägeli on Unsplash
1. Arrangement of a piece of music in parts so that it can be played by an orchestra2. Act of organizing a complicated plan or event very carefully or secretly
Source: Oxford Advanced Learner's Dictionary
© 2019 TM Forum | 7#TMFDigital
Orchestration Definition
• MEF LSO
– Open and interoperable automation of management operations over the entire lifecycle of Layer 2 and Layer 3 Connectivity Services. This includes fulfillment, control, performance, assurance, usage, security, analytics and policy capabilities, over all the network domains that require coordinated management and control in order to deliver the service.
(Source: MEF 55 - Lifecycle Service Orchestration(LSO): Reference Architecture and Framework)
• TM Forum
– Orchestration is the coordination and management of systems in an automated fashion.
(Source: TMF IG1139 - Business Rationale and Technical Overview for Orchestration and Autonomic Control Loops)
• ONAP
– The arrangement, sequencing and automated implementation of tasks, rules and policies to coordinate logical and physical resources in order to meet a customer or on-demand request to create, modify or remove network or service resources. (Source: ONAP)
• ETSI NFV-MANO
– NFV Orchestrator has two main responsibilities:
• orchestration of NFVI resources across multiple VIMs, fulfilling the Resource Orchestration functions described in “Management and Orchestration aspects of Network Functions Virtualisation Infrastructure “
• lifecycle management of Network Services, fulfilling the Network Service Orchestration functions, as described in clause “Management and Orchestration aspects of Network Services “
(Source: ETSI GS NFV-MAN 001 V1.1.1 (2014-12) – NFV MANO)
© 2019 TM Forum | 8#TMFDigital Source: MEF
© 2019 TM Forum | 9#TMFDigital
Types of Orchestration in MEF LSO
• Product Ordering and Service Activation Orchestration
• Order Fulfillment Orchestration: deals with decomposing a customer order into one or multiple service provisioning activities and orchestrating of all customer order-related fulfillment activities
• Service Configuration and Activation Orchestration: responsible for the design, assignment, and activation activities for the end-to-end service and/or some or all Service Components
• Service Control Orchestration: permits the service to be dynamically changed within specific bounds described in policies that are established at the time of provisioning
• Service Delivery Orchestration: responsible for the service delivery via network implementation delegation of each Service Component to their respective delivery system or mechanism
• Service Activation Testing Orchestration: coordinates all service activation testing activities, for parts and/or the complete end-to-end service
Source: MEF 55: LSO Reference Architecture and Framework
© 2019 TM Forum | 10#TMFDigital
“Service Types” in TM Forum Information Framework (SID)
Service
Customer
Resource(networks, subnetworks, network components, and other related aspects of a network) – Physical and Logical
Customer-Facing Services
Resource-FacingServices
Create Products and Product Offers
VNFs, PNFs
NFV-MANO Orchestration
NFV OrchestrationService
Orchestration
Source: https://inform.tmforum.org/features-and-analysis/2016/03/what-does-orchestration-really-mean/
© 2019 TM Forum | 11#TMFDigital
NFV-MANO Architectural Framework with Reference Points
Source: ETSI NFV Architecture Framework
© 2019 TM Forum | 12#TMFDigital
Management and Orchestration aspects in NFV MANO
• Management and Orchestration aspects of NFVI– The management and orchestration of virtualised resources should be able to handle NFVI resources (e.g. in NFVI
Nodes), in NFVI Points of Presence (NFVI-PoPs). Management of non-virtualised resources is restricted to provisioning connectivity to PNFs, necessary when a NS instance includes a PNF that needs to connect to a VNF, or when the NS instance is distributed across multiple NFVI-PoPs or N-PoPs.
• Management and Orchestration aspects of VNFs– Management and orchestration aspects of a VNF include traditional Fault Management, Configuration
Management, Accounting Management, Performance Management, and Security Management (FCAPS), but the focus in the present document is on the newer aspect introduced by NFV
• Management and Orchestration aspects of Network Services – The Network Service Orchestration is responsible for the Network Service lifecycle management including
operations such as: • On-board Network Service, i.e. register a Network Service in the catalogue and ensure that all the templates describing the NS are
on-boarded. • Instantiate Network Service, i.e. create a Network Service using the NS on-boarding artefacts. • Scale Network Service, i.e. grow or reduce the capacity of the Network Service. • Update Network Service by supporting Network Service configuration changes of various complexity such as changing inter-VNF
connectivity or the constituent VNF instances. • Create, delete, query, and update of VNFFGs associated to a Network Service.• Terminate Network Services, i.e. request the termination of constituent VNF instances, request the release of NFVI resources
associated to NSs, and return them to NFVI resource pool if applicable.
Source: ETSI GS NFV-MAN 001 V1.1.1 (2014-12)
© 2019 TM Forum | 13#TMFDigital
Automated Onboarding
• If you are really particular about TTM, leveraging onboarding automation of NFs is key.
• One of the essential requirement to have is a NF onboarding automation tool that supports both VNFs and CNFs (or 2 separate systems).
• But you need to check whether they are really open, meaning that they can onboard any open VNF/CNF and optimize the process/operation.
• Further, it should be able to perform automated service [chain] design as well.
• Ultimately the entire lifecycle of a NF from procurement/sourcing, onboarding, testing, acceptance/validation, deployment, configuration and assurance/maintenance should be automated, leading the industry to a same-day NF onboarding status.
• OPNFV Verification Program (OVP) is a helpful program in this regard.
© 2019 TM Forum | 14#TMFDigital
Closed-loop Service Assurance
• Optimum delivery of services in reality is also linked with closed-loop service assurance. AI can be used to achieve this easily.
• As operators bring real automation to their service engines, service assurance data will play a key role.
• Ideally, service assurance data will have to be in a “closed loop” that uses constant assessment of network health (traffic and performance) to optimize service parameters like quality, detect possible threats and do many other tasks automatically.
• This plays an important role in service providers’ ability to offer new services which change with customer needs, without requiring network reconfiguration or a lot of human touch.
• Example:- Sri Lanka Telecom was a champion in the Proactive Service Assurance via Closed Loop Predictive AI/ML TM Forum Catalyst project. The project demonstrates advancement toward fully automated service assurance for network transformation, working with actual network data and utilizing AI, predictive analysis, and knowledge-based self-learning.
© 2019 TM Forum | 15#TMFDigital
Service / Network Function Evaporation
Source: Photo by Wolfgang Hasselmann on Unsplash
Service
ServiceService
Service
Service
VNF
VNF
VNF
PNFPNF
PNF
VNF VNF
CNF
CNFCNF
CNF
© 2019 TM Forum | 16#TMFDigital
VNFPNFPNF
HDN
Network Transformation Cannot Happen Overnight
HDN
PNF
SDN
VNF
SDN
CNF
Complex, but we mastered
the complexity
End (Hybrid)
Migration period(Hybrid)
SDN
VNF
looks complex, mainly because of the lack of knowledge, skills and education
Start
Complex ?
PNF
© 2019 TM Forum | 17#TMFDigital
Guest OS
Hypervisor
Guest OS
Host HW
Host OS
Host Virtualized
APs
VMs
PMHost HW
Host OS
Bare-Metal Native
APs
PM
Guest OS
Hypervisor
Guest OS
Host HW
Bare-Metal Virtualized
APs
VMs
PM
Bins/Libs Bins/Libs
Host HW
Host OS
Containerized
APs
Containers
PM
Container Engine (ex:- Docker engine)
Bins/
Libs
Hypervisor
Guest OS
Host HW
Host OS
Containers in VMs
APs
Containers
PM
Bins/
Libs
Bins/
Libs
Guest OS
Bins/
Libs
VMs
Container Engine Container Engine
Bins/Libs
Hypervisor
Guest OS
Host HW
Host OS
Containers and VMs
APs
Containers & VMs
PM
Container Engine
Host HW
Host OS
VMs in Containers
APs
VMs
PM
Guest OS
Hypervisor
Containers
Guest OS
Hypervisor
Container Engine
© 2019 TM Forum | 18#TMFDigital
Hybrid Network Environment (Network Controller)
Source: ETSI GS NFV-MAN 001 V1.1.1 (2014-12)
© 2019 TM Forum | 19#TMFDigital
EMS/NMS for the NFVI Network
Source: ETSI GS NFV-MAN 001 V1.1.1 (2014-12)
© 2019 TM Forum | 20#TMFDigital
IETF SDNRGIETF NFVRG
+ O-ECOMP =>
+ = =>
SDN Standard definitions
NFV Standard definitions
SDN
Co
ntr
olle
r im
ple
men
tati
on
s NFV implementations
Cloud/Container Orchestration / Management tools
Orchestration Definitions
Orchestrator implementations
Japanese Softwarization Projects
Other Open Source Projects
Softwarization standards and Open Source Projects
Tracker NFV Orchestration
( )
Single InstanceMulti Instance
(LFN) harmonization
© 2019 TM Forum | 21#TMFDigital
ONAP vs. OSM
© 2019 TM Forum | 22#TMFDigital
Vendor Perspective
• Margins of selling hardware boxes and software are getting thinner, mainly due to open hardware and software initiatives.
• Vendors are slowly moving to the service business (training, system integration, operation and maintenance of telecom networks and systems).
• Fast TMT requires capabilities like automation, DevOps and agility. Achieving those in a multi-vendor environment is challenging as vendors’ true willingness to be open is still a question.
© 2019 TM Forum | 23#TMFDigital
Problem Becomes Multi- Dimensional
Source: Photo by Andrej Lišakov on Unsplash
multi-vendor
© 2019 TM Forum | 24#TMFDigital
Summary
CSP
DSP
Source: Photo by Simon English on Unsplash
• As we move from yesterday to tomorrow, the hybrid infrastructure in a telco environment will pose new challenges in automation, especially • the onboarding of network functions• achieving real-time dynamic orchestration of end-to-end service • closed-loop service assurance
• Open collaboration among all stakeholders of the industry makes us navigate the transitioning period for network transformation slowly and steadily