vNF Chaining Manager for Service Infrastructure Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional Domain Name Service (DNS) and Internet Protocol (IP) load balancers are inadequate for managing the integration of new virtualized network functions (vNFs) into an end-to-end service infrastructure, as they cannot efficiently support chaining needs such as application access control, traffic throttling, priority differentiation, and overload control, making the process slow and time-consuming.
Innovation Solution
A vNF chaining manager server that receives information from vNF chaining clients to update a service chaining catalog and transmit necessary information to peering vNFs, using message types like ADD_NEW, SUBSCRIBE, UPDATE, REMOVE, and NOTIFY to manage the instantiation, configuration changes, and removal of vNFs, enabling efficient integration and communication among vNFs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional DNS or IP load balancers are used for vNF integration, then basic network routing is supported, but advanced chaining needs such as application access control, traffic throttling, priority differentiation, and overload control cannot be supported
Solution Approach 1:
The patent introduces a service chaining manager as an intermediary component that sits between traditional network infrastructure (DNS, IP load balancers) and virtualized network functions. This mediator handles advanced chaining needs including application access control lists, traffic throttling, priority differentiation, and overload control, while traditional DNS and load balancers continue to handle basic routing functions. This resolves the contradiction by adding specialized functionality without requiring complete system replacement.
2Reliability
If carefully planned configuration processes are used across the network for vNF integration, then integration accuracy can be maintained, but the process becomes slow and time consuming
Solution Approach 1:
The service chaining manager implements automated self-service mechanisms where vNFs can autonomously register themselves with the manager, which then automatically updates service chaining catalogs and propagates configuration information to peering vNFs. This eliminates the need for slow, manual configuration processes while maintaining integration accuracy through systematic automated updates. The system performs configuration propagation automatically based on vNF instantiation events, resolving the contradiction between reliability and productivity.
3Manufacturing precision
If manual configuration processes are used for vNF chaining, then configuration accuracy can be controlled, but the time required for vNF instantiation and integration increases significantly
Solution Approach 1:
The service chaining manager pre-establishes service chaining catalogs that define relationships between peering vNFs before they are instantiated. When a new vNF is instantiated, the manager automatically matches it with appropriate peering vNFs based on pre-defined chaining rules and immediately propagates configuration information. This preliminary preparation of chaining templates and relationships enables rapid vNF integration while maintaining configuration accuracy through pre-validated chaining definitions, resolving the contradiction between precision and time loss.
Data Source
AI summary
A method for vNF chaining management includes receiving virtualized network function (vNF) information from a chaining client associated with a particular vNF. A service chaining catalog is updated based on the vNF information and chaining information is transmitted to peering vNFs of the particular vNF. The vNF information can indicate instantiation of a vNF and identify peering vNFs. Updates received from vNFs can be used to update the chaining catalog. Updated vNF information can then be sent to peering vNFs of the vNF which sent the update.