NFV MANO Virtual Link Management via Os-Ma-nfvo
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 5G network architecture lacks efficient mechanisms for managing and orchestrating virtual links and virtual network function forwarding graphs, particularly in adding or removing external connectivity and network forwarding paths, which hinders dynamic network service updates and optimizations.
Innovation Solution
The implementation of enhanced Network Function Virtualization (NFV) Management and Orchestration (MANO) capabilities, including the Os-Ma-nfvo reference point, allows for the addition and removal of virtual links and the management of virtual network function forwarding graphs within the 5G network service instances, enabling operators to dynamically update network configurations and connectivity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If enhanced NFV MANO capabilities are implemented to enable dynamic management of virtual links and forwarding graphs, then network agility and responsiveness are improved, but system complexity increases
Solution Approach 1:
The patent introduces an NFV Orchestrator (NFVO) as an intermediary component that manages virtual links and forwarding graphs between the network elements. The NFVO provides standardized interfaces (Os-Ma-nfvo reference point) that simplify the management complexity while enabling dynamic network service updates. This mediator handles the complexity of virtual link management, allowing operators to update network configurations without directly managing the underlying complexity of each network function instance.
2Adaptability or versatility
If virtual links and network forwarding paths are dynamically added or removed, then network service flexibility is improved, but management overhead increases
Solution Approach 1:
The patent implements preliminary action by pre-defining Network Service Descriptors (NSDs) and Virtual Network Function Forwarding Graph (VNFFG) templates that contain the configuration information for virtual links and forwarding paths. When network services need to be deployed or updated, these pre-configured templates are instantiated and modified, rather than creating configurations from scratch. This approach reduces management overhead by reusing standardized templates and automating the instantiation process through the NFV orchestrator.
Solution Approach 2:
The patent uses copying by creating instances of virtual links and forwarding graphs from standardized templates. The NSD and VNFFG templates serve as reusable blueprints that can be copied and instantiated multiple times across different network service instances. This copying mechanism allows rapid deployment and updating of network services without manually configuring each virtual link, significantly reducing management overhead while maintaining flexibility.
3Ease of operation
If external connectivity management is enhanced through Os-Ma-nfvo reference point, then connectivity control capability is improved, but interface complexity increases
Solution Approach 1:
The patent implements universality by designing the Os-Ma-nfvo reference point as a multi-functional interface that handles multiple connectivity management operations through standardized methods. The same interface supports adding virtual links, removing virtual links, updating forwarding graphs, and managing external connectivity across different network service types. This universal interface approach consolidates multiple specialized interfaces into one, improving ease of operation while managing interface complexity through standardization and reuse of communication protocols.
Data Source
AI summary
An apparatus of a Network Manager (NM) comprises one or more processors to send a Network Service (NS) update request to a Network Function Virtualization Orchestrator (NFVO) to add external connectivity to a Physical Network Function (PNF) instance or a Virtual Network Function (VNF) instance in an NS instance, to receive an operation result containing a lifecycle operation occurrence identifier from the NFVO, to receive a lifecycle change notification from the NFVO indicating a start of an NS update, and to receive an NS Lifecycle Change notification from the NFVO indicating a result of the NS update. A memory is to store the result of the NS update.