Unified VNFD Model for Containerized VNF Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of deploying containerized Network Functions Virtualization (NFV) is increased due to the incompatibility of information models between VM-based and containerized VNFs, requiring two independent VNFD models for instantiation, which complicates the evolution from VM-based to containerized VNFs.
Innovation Solution
A unified VNFD model is introduced that supports both VM-based and containerized VNF deployments, using managed container infrastructure objects (MCIOs) and container object packages, allowing for smooth evolution and reducing deployment complexity by managing container objects at an abstract logical resource layer without managing infrastructure resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If two independent VNFD models are used for VM-based and containerized VNFs, then both VNF types can be instantiated, but deployment complexity increases
Solution Approach 1:
The patent applies universality by designing a unified VNFD model that can describe both VM-based VNFs and containerized VNFs using the same information model structure. The VNFD includes common fields for both types, with optional fields to specify VM or container characteristics, eliminating the need for separate information models and reducing deployment complexity while maintaining support for both VNF types
Solution Approach 2:
The patent segments the VNF deployment into distinct components: the unified VNFD information model, the VNF manager for orchestration, and the container management entity for container-specific operations. This segmentation allows the system to handle both VM-based and containerized VNFs through a standardized framework while separating concerns for type-specific management
2Ease of manufacture
If containerized VNFs are deployed using existing VM-based NFV framework, then infrastructure resources are managed, but container object management complexity increases
Solution Approach 1:
The patent introduces a container management entity as an intermediary component between the VNF manager and the container runtime environment. This intermediary handles container-specific operations such as container object creation, modification, and deletion, allowing the VNF manager to focus on high-level orchestration while the container management entity manages the complexity of container object operations
Solution Approach 2:
The patent extracts container object management responsibilities from the VNF manager by introducing a separate container management entity. This extraction allows the VNF manager to maintain a simplified interface for VNF deployment while delegating container-specific complexity to the dedicated container management entity
Data Source
Figure 1-A
Figure 1-B
Figure 2
AI summary
A containerized VNF deployment method and a related device are provided. The containerized VNF deployment method includes: A VNFM receives a first VNF instantiation request from an NFVO, where the first VNF instantiation request carries a first VNF instance identifier and a first virtualised network function descriptor VNFD identifier; the VNFM determines a container object package identifier referenced by a VNFD identified by the first VNFD identifier; the VNFM sends a container object package management request to a container management entity, and receives a container object package management response from the container management entity, where the container object package management response is used to indicate that a container object instance in a container object package is successfully created; and the VNFM creates a VNF instance identified by the first VNF instance identifier, and maintains a mapping relationship between the first VNF instance identifier and the container object package identifier. The method helps reduce complexity of containerized VNF deployment.