Packet Handling Policy for Delayed URLLC Traffic Consistency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Mobile wireless networks struggle to consistently handle packets for Ultra-Reliable Low Latency Communications (URLLC) applications due to varying network behaviors across different segments, leading to inconsistent packet handling and potential application malfunctions, as vendors may discard or deliver delayed packets based on local decisions without considering application requirements.

Innovation Solution

A method and system that involves sending a packet handling policy (PHP) from a control plane function to instruct user plane devices on how to handle packets based on defined delay thresholds, including drop or deliver decisions for packets exceeding specific delay thresholds, ensuring consistent packet handling across network segments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If local decisions are made by network nodes to discard or deliver delayed packets, then network flexibility and autonomy are improved, but network behavior consistency and reliability deteriorate

Engineering Contradiction:

Improvenetwork flexibilityVSAvoidnetwork behavior consistency

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the decision-making process by separating policy creation (centralized in control plane function) from policy execution (distributed in user plane devices). This allows each segment to operate autonomously while maintaining overall consistency through the unified policy framework.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a packet handling policy as an intermediary that mediates between the control plane function and user plane devices. This policy acts as a standardized interface that ensures consistent packet handling decisions across all network nodes while allowing local adaptation.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If delayed packets are delivered to meet potential application requirements, then application reliability is improved, but radio resource waste increases

Engineering Contradiction:

Improveapplication reliabilityVSAvoidradio resource waste

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies preliminary action by establishing packet handling policies in advance, before packets are transmitted. The policy pre-defines whether delayed packets should be discarded or delivered based on application requirements, eliminating the need for later decision-making and resource waste.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by having the control plane function receive application requirement information and adjust packet handling policies accordingly. This closed-loop feedback ensures that packet handling decisions are optimized for actual application needs, preventing both resource waste and reliability issues.

Inventive Principle:

Principle #23Feedback

3Adaptability or versatility

If different vendors implement different packet handling designs, then device complexity and customization are improved, but network interoperability and consistency deteriorate

Engineering Contradiction:

Improvedevice customizationVSAvoidnetwork behavior consistency

Core Design Contradiction:

Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent achieves universality by creating a standardized packet handling policy framework that can be universally applied across different vendors and network nodes. The policy structure is designed to be vendor-agnostic while maintaining consistent behavior, allowing each vendor to implement the same standard in their devices.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent uses parameter changes by defining specific packet handling parameters (such as discard thresholds, delivery conditions) that can be configured through policies. These parameters provide a standardized interface that maintains consistency while allowing flexibility in implementation details across different vendors.

Inventive Principle:

Principle #35Parameter changes

4Loss of time

If packets are discarded when exceeding delay budget to meet latency requirements, then latency compliance is improved, but application reliability deteriorates

Engineering Contradiction:

Improvelatency complianceVSAvoidapplication reliability

Core Design Contradiction:

Loss of timeVSReliability

Solution Approach 1:

The patent applies dynamics by making packet handling decisions dynamic rather than static. The packet handling policy can adapt its behavior (discard or deliver) based on real-time conditions such as application requirements, network state, and packet characteristics, allowing optimization of both latency and reliability.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent uses parameter changes by allowing the packet handling policy to modify key parameters such as delay thresholds and discard probabilities based on application requirements. This enables the system to adjust its latency-reliability tradeoff dynamically to meet specific application needs.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentEP3864822B1Method and system for using policy to handle packets

Publication Date: 2025.12.10 HUAWEI TECH CO LTD

Figure 1
Figure 2
Figure 3

AI summary

An aspect of the disclosure provides a method for handling delayed packets in a mobile wireless network performed by a PCF. The method includes receiving information pertaining to packet handling policy (PHP) parameters for a PDU session; and sending the PHP to other network functions for instructing devices in the user plane of the mobile wireless network how to handle delayed packets.