VNF Instantiation via Ingress Containers for Microservice Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing NFV architectures face challenges in meeting the access requirements of microservices due to the introduction of container management platforms, necessitating improved methods for creating ingress container objects to facilitate microservice access.
Innovation Solution
An instantiation method and apparatus for VNFs that involve determining configuration information for ingress container objects based on microservice configuration, using VNFD mapping information to extend virtual connection points and introduce parameters like container object type, service type, domain name type, and priority into the VNFD, enabling better reconstruction and life cycle management of network element microservices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If container management platforms are introduced to NFV architecture, then microservice deployment capability is improved, but the complexity of managing ingress container objects increases
Solution Approach 1:
The patent introduces an ingress container object as an intermediary component that manages access to multiple microservices. This intermediary handles layer 7 access requirements (domain names, paths) and routes traffic to appropriate microservices, thereby improving deployment capability while managing complexity through a dedicated access management layer
Solution Approach 2:
The ingress container object serves multiple functions simultaneously: it provides layer 7 routing based on domain names and paths, manages access to multiple different microservices, and acts as a unified entry point for various network functions. This multi-functionality improves versatility while consolidating management complexity into a single object type
2Reliability
If traditional NFV virtual connection points are used, then network function virtualisation is achieved, but access requirements of microservices at layer 7 cannot be met
Solution Approach 1:
The patent extends the traditional virtual connection point concept by adding new parameters specifically for layer 7 access: domain name parameters and path parameters. These additional parameters enable the virtual connection point to handle microservice access requirements at the application layer while maintaining the core NFV virtualisation functionality
Solution Approach 2:
The patent segments the access management functionality by introducing distinct ingress container objects for different virtual connection points, each with its own set of microservices and access parameters. This segmentation allows independent configuration and management of access requirements for different network functions while maintaining overall system reliability
Data Source
AI summary
A method includes: A VNFM receives a first instantiation request from an NFVO, where the first instantiation request includes configuration information of a first virtual connection point of a VNF, and the configuration information of the first virtual connection point includes configuration information of K microservices of an NF corresponding to the VNF; further determines configuration information of a first ingress container object corresponding to the first virtual connection point, where the first ingress container object configured to provide an access ingress of the K microservices; and sends the configuration information of the first ingress container object to a CISM, where the configuration information of the first ingress container object is for creating the first ingress container object.