NFV IP Address Allocation via VNFD Requirement Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In Network Function Virtualization (NFV) systems, there is a need for an efficient mechanism to coordinate and implement special IP address allocation requests for specific virtual network function components (VNFC) instances across different vendor nodes, as existing systems lack a standardized approach to support vendor-specific IP address allocation schemes.

Innovation Solution

A method and system where a first node in the NFV system obtains IP address allocation requirements from a virtualised network function descriptor (VNFD), determines additional requirements, and sends them to a second node for IP address allocation, ensuring that the allocated IP address meets the specified criteria, such as type, access point name, IP address pool, range, or list, to support dynamic and static allocation processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a standardized IP address allocation mechanism is implemented across NFV systems, then compatibility and resource management efficiency are improved, but flexibility to support vendor-specific allocation schemes is reduced

Engineering Contradiction:
ImprovecompatibilityVSAvoidallocation mechanism complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The IP address allocation process is segmented into multiple stages: (1) extracting basic allocation requirements from VNFD, (2) determining additional requirements based on allocation type (static/dynamic), and (3) sending refined requirements to the second node for actual allocation. This segmentation allows the system to handle both standardized and vendor-specific requirements through a modular approach.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The first node acts as an intermediary between the VNFD and the second node. It receives the basic allocation requirements, processes them through determination logic, and sends refined requirements to the second node. This intermediary layer enables the system to translate between different allocation schemes while maintaining overall system compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If dynamic IP address allocation is used for VNFC instances, then resource management efficiency is improved, but the complexity of coordinating allocation across multiple nodes increases

Engineering Contradiction:
Improveresource management efficiencyVSAvoidcoordination complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The dynamic allocation process is divided into distinct functional segments: the first node extracts requirements from VNFD, determines additional dynamic allocation parameters, and sends them to the second node which performs the actual allocation. This segmentation reduces coordination complexity by dividing the allocation task into manageable steps.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses feedback mechanisms where the first node receives the VNFD, processes it through determination logic, and sends refined requirements to the second node. This feedback loop ensures that allocation requirements are properly translated and coordinated across nodes while maintaining efficiency.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If vendor-specific IP address allocation schemes are supported, then flexibility and adaptability are improved, but system complexity and standardization are reduced

Engineering Contradiction:
Improvevendor-specific scheme supportVSAvoidsystem standardization
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system applies local quality by allowing different allocation determination logic at the first node based on the specific VNFD and allocation type. While the overall architecture remains standardized, the local processing of allocation requirements can adapt to vendor-specific schemes through the determination step.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The allocation mechanism is made dynamic through the determination step that adapts to different allocation types (static/dynamic) and vendor-specific requirements. The system can switch between standardized and vendor-specific allocation logic based on the input VNFD, providing flexibility without sacrificing overall standardization.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10375015B2Methods and system for allocating an IP address for an instance in a network function virtualization (NFV) system
Publication Date: 2019.08.06 FUTUREWEI TECHNOLOGIES INC
  • US10375015B2 patent drawing
  • US10375015B2 patent drawing
  • US10375015B2 patent drawing

AI summary

A non-transitory computer-readable medium storing computer instructions for allocating an IP address for an instance in a network function virtualization (NFV) system, that when executed by one or more processors, cause the one or more processors to perform the steps of obtaining a first requirement of IP address allocation from VNFD by a first node in the NFV system, determining a second requirement of IP address allocation for the instance according to the first requirement; and sending to a second node in the NFV system the second requirement, wherein the IP address is allocated for the instance based upon the second requirement.