NFV Traffic Resource Allocation for Ultra-Low Latency Services

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing network function virtualization (NFV) technologies fail to dynamically adjust network resources based on traffic characteristics, particularly for ultra-low latency traffic, leading to unsatisfied performance requirements and user experience.

Innovation Solution

Implement a traffic resource management method that prioritizes resource allocation and deployment for ultra-low latency traffic near the user, employs resource preemption and over-configuration, and dynamically adjusts resources based on performance feedback to maintain latency requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If NFV technology is used for network orchestration and management, then resource sharing and flexibility are improved, but differentiated management for different traffic requirements cannot be performed

Engineering Contradiction:

Improveresource sharing flexibilityVSAvoiddifferentiated traffic management capability

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent segments traffic into different types (e.g., ultra-low latency traffic, high priority traffic, best effort traffic) and creates separate management mechanisms for each type. This is achieved through traffic classification modules that identify different traffic types and apply specific resource allocation strategies to each, enabling differentiated management while maintaining overall NFV flexibility.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by implementing traffic-specific resource allocation policies where different parts of the network resource pool are allocated with different priorities and characteristics based on traffic type. Ultra-low latency traffic receives guaranteed resources with highest priority, while other traffic types receive resources according to their specific requirements, creating localized optimization within the overall system.

Inventive Principle:

Principle #3Local quality

2Ease of manufacture

If static resource allocation is used in NFV deployment, then deployment simplicity is improved, but dynamic adjustment according to traffic performance changes cannot be performed

Engineering Contradiction:

Improvedeployment simplicityVSAvoiddynamic resource adjustment capability

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic resource allocation mechanisms that continuously monitor traffic performance metrics and automatically adjust resource allocation accordingly. The system transitions from static pre-configured resources to dynamic resources that can be reallocated in real-time based on actual traffic conditions, performance requirements, and network state, while maintaining manageable complexity through automated control loops.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent incorporates feedback mechanisms where traffic performance is continuously monitored and measured, and this information is fed back to the resource allocation module. The system uses this feedback to automatically adjust resource allocation decisions, creating a closed-loop control system that adapts to changing traffic conditions without requiring manual intervention, thus achieving dynamic adjustment with manageable operational complexity.

Inventive Principle:

Principle #23Feedback

3Device complexity

If general resource allocation is applied to all traffic types, then resource management simplicity is improved, but ultra-low latency traffic performance requirements cannot be satisfied

Engineering Contradiction:

Improveresource management complexityVSAvoidultra-low latency traffic performance guarantee

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The patent implements preliminary action by pre-allocating and reserving specific network resources for ultra-low latency traffic before actual traffic arrival. Resource reservation mechanisms ensure that dedicated bandwidth, computing resources, and network paths are prepared in advance for time-sensitive traffic, guaranteeing performance requirements without requiring complex real-time resource management during traffic flow.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent applies partial action by allocating resources selectively to specific traffic types rather than applying uniform allocation to all traffic. Ultra-low latency traffic receives preferential and excessive resource allocation compared to its actual needs, ensuring performance guarantees, while other traffic types receive resources based on their requirements, simplifying the overall management by treating different traffic types differently rather than using complex unified management.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentEP3855703B1Traffic resource management method, network device, and readable storage medium

Publication Date: 2025.11.05 ZTE CORP

Figure 1
Figure 2
Figure 3~4

AI summary

Provided are a traffic resource management method and apparatus, a network device, and a readable storage medium. The method includes: determining a type of traffic to which a network service (NS) or a virtualized network function (VNF) to be managed is applied; and in response to the type of traffic to which the NS or the VNF is applied being low latency traffic, providing a corresponding management service for the NS or the VNF according to a low latency traffic resource management strategy.