Orchestration Node Trunk Port Management via Function Manager
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current specifications, such as SOL001 and SOL003, do not adequately address the creation and management of trunk ports in NFV-MANO architectures, particularly in dynamically adding or removing network sub-interfaces without updating the VNFD.
Innovation Solution
The proposed solution involves an orchestration node, such as a NFVO, sending trunk-port specific information to a function manager, like a VNFM, enabling unambiguous orchestration of trunk ports. This includes using a single CPD for each port, with a trunk_mode attribute, and providing trunk-port specific information like segmentation IDs to support dynamic management of network sub-interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If current specifications (SOL001 and SOL003) are used for managing network interfaces, then the VNFD model is maintained, but trunk port management and dynamic addition/removal of network sub-interfaces are not adequately supported
Solution Approach 1:
The patent segments the network interface management by introducing a trunk_mode attribute that distinguishes between access ports and trunk ports. This segmentation allows the system to handle different port types with appropriate management mechanisms, enabling trunk ports to dynamically add/remove network sub-interfaces while access ports follow the traditional model.
Solution Approach 2:
The patent introduces dynamic capabilities for trunk ports by allowing the addition and removal of network sub-interfaces at runtime without requiring VNFD updates. The trunk port can dynamically adjust its configuration based on operational needs, making the system more adaptable while maintaining specification stability.
2Device complexity
If a single CPD is used for each port with trunk_mode attribute, then the model simplicity is maintained, but unambiguous orchestration of trunk ports requires additional trunk-port specific information
Solution Approach 1:
The patent adds a new dimension to the CPD model by introducing the trunk_mode attribute and associated trunk-port specific information (such as segmentation IDs). This dimensional extension allows the same CPD structure to represent both access and trunk ports unambiguously, with the additional attribute providing the necessary differentiation without creating separate model structures.
3Ease of operation
If dynamic addition or removal of network sub-interfaces is enabled for trunk ports, then operational flexibility is improved, but VNFD updates would be required in traditional specifications
Solution Approach 1:
The patent prepares the CPD model in advance with the trunk_mode attribute and trunk-port specific information structure, enabling dynamic operations without requiring VNFD updates. By pre-configuring the model to support trunk port operations, the system eliminates the time-consuming VNFD update process while maintaining operational flexibility.
Solution Approach 2:
The patent introduces trunk-port specific information as an intermediary layer between the CPD model and the actual network interface configuration. This intermediary structure allows dynamic addition and removal of network sub-interfaces without triggering VNFD updates, as the changes are handled through the intermediate trunk-port configuration mechanism.
Data Source
AI summary
Embodiments relate to e.g. a method performed by an orchestration node for managing network interfaces. The orchestration node sends to a function manager, trunk-port specific information of a trunk port to enable the function manager to unambiguously orchestrate trunk ports.