Tiered Virtual Network Function Chaining Design

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing and deploying large numbers of Virtual Network Function (VNF) chains in cloud computing environments is resource-intensive due to the need for extensive storage and processing of network service records, which increases storage, processing, and memory requirements.

Innovation Solution

Assigning a Number of Services attribute and a Tier attribute to each network service record allows for inter-referencing, condensing a large quantity of VNF chains into a smaller quantity of records, enabling efficient storage and streamlined management, configuration, and deployment of network services by representing multiple VNF chains with a single record.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a separate network service record is created for each VNF chain, then complete service information is stored, but storage space and processing requirements increase significantly

Engineering Contradiction:
Improveservice information completenessVSAvoidstorage space requirements
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

Multiple VNF chain records that share common service information are merged into a single network service record. The record contains shared service-level attributes that apply to multiple VNF chains, eliminating redundant storage and reducing processing overhead while maintaining complete service information.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The network service record is designed to serve multiple purposes simultaneously - it stores service information that can be applied to multiple different VNF chains. A single record structure supports various service types and configurations through parameterized fields, making it a universal template that reduces the total number of records needed.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Manufacturing precision

If extensive network service records are stored for each VNF chain, then service management accuracy is improved, but processing and memory requirements increase

Engineering Contradiction:
Improveservice management accuracyVSAvoidprocessing and memory capacity
Core Design Contradiction:
Manufacturing precisionVSPower

Solution Approach 1:

The service record structure is segmented into hierarchical levels - service-level attributes that apply to multiple chains and chain-specific attributes. This segmentation allows the system to process only the necessary level of detail for each operation, reducing memory requirements while maintaining management accuracy through structured data organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of storing complete duplicate records for each VNF chain, the system creates lightweight references or copies of shared service information. When a VNF chain needs service information, it references the master network service record rather than storing a full copy, significantly reducing processing and memory requirements.

Inventive Principle:
Principle #26Copying

3Manufacturing precision

If manual management of large numbers of VNF chains is performed, then service configuration accuracy is maintained, but operational complexity and time requirements increase

Engineering Contradiction:
Improveservice configuration accuracyVSAvoidoperational complexity
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The system enables automated self-service operations for VNF chain management. The network service records contain sufficient information to automatically configure and deploy VNF chains without manual intervention. The structured record format allows systems to automatically interpret and apply service definitions, reducing operational complexity while maintaining configuration accuracy through consistent data structures.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Service configurations are prepared in advance and stored in standardized network service records. These pre-configured records contain all necessary information for automatic deployment, allowing the system to perform service instantiation rapidly without manual configuration steps, thereby reducing operational complexity while preserving accuracy through pre-validated service definitions.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10791029B2Tier based virtual network function chaining design
Publication Date: 2020.09.29 VERIZON PATENT & LICENSING INC
  • US10791029B2 patent drawing
  • US10791029B2 patent drawing
  • US10791029B2 patent drawing

AI summary

Techniques described herein may be used to condense a large quantity of Virtual Network Function (VNF) chains (that each correspond to a network service) into a much smaller quantity of VNF records; and extract any of the large quantity of VNF chains from the smaller quantity of network service records. This may be accomplished by assigning a Number (No.) of Services attribute and a Tier attribute into each VNF record. The No. of Services attribute and Tier attribute may enable the VNF records to reference one another such that the larger quantity of VNF chains may, in effect, be entirely represented by the much smaller quantity of VNF records, thereby conserving storage space, streamlining VNF chain management, and reducing the processing and memory capacity required to search, configure, and deploy virtual network services.