QoS Flow Discard Timer for 5G Packet Deletion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing data packet deletion mechanisms in 5G networks, which rely on discard timers based on data radio bearers (DRBs), fail to meet the diverse service characteristics of different services, leading to inefficient storage management and packet handling.

Innovation Solution

Implementing a data packet deletion method that uses discard timers with a quality of service (QoS) flow granularity, allowing for customized timer settings based on specific QoS flows, enabling more precise control over packet retention and deletion according to service requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If a discard timer based on DRB granularity is used, then the storage space of the sender can be saved by deleting cached SDUs and PDUs, but the diverse service characteristics of different services cannot be met

Engineering Contradiction:
Improvestorage spaceVSAvoidservice characteristic adaptation
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The patent segments the discard timer control from DRB level to QoS flow level. Each QoS flow within a DRB can have its own discard timer configuration, allowing different services mapped to the same DRB to have different packet deletion behaviors. This segmentation resolves the contradiction by enabling fine-grained control that adapts to diverse service characteristics while still managing storage space effectively.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by allowing different discard timer parameters to be configured for different QoS flows. Each QoS flow can have customized discard timer values based on its specific service requirements, rather than applying a uniform timer to all flows in a DRB. This enables precise control over packet retention for each service type while maintaining overall storage management.

Inventive Principle:
Principle #3Local quality

2Device complexity

If a uniform discard timer is applied to all data packets in a DRB, then the system complexity is reduced, but the data packet deleting demands of various services cannot be satisfied

Engineering Contradiction:
Improvetimer management complexityVSAvoidservice-specific packet deletion
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent introduces segmentation by creating separate discard timer management for each QoS flow within a DRB. The PDCP entity maintains discard timer information per QoS flow, allowing independent control of packet deletion timing for different services. This segmentation increases adaptability while keeping the complexity manageable through structured organization of timer configurations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic discard timer management where the discard timer value can be dynamically configured for each QoS flow based on service requirements. The system can adaptively adjust timer values for different QoS flows, enabling flexible response to varying service demands without requiring a completely different system architecture.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11722425B2Data packet deleting method, device and storage medium
Publication Date: 2023.08.08 GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
  • US11722425B2 patent drawing
  • US11722425B2 patent drawing
  • US11722425B2 patent drawing

AI summary

Embodiments of the present application provide a data packet deleting method, a device and a storage medium, the method includes: when a protocol layer entity of a sender receives an SDU from a higher layer, determining a QoS flow to which the SDU belongs; when the QoS flow to which the SDU belongs is a first QoS flow, the protocol layer entity starts a first discard timer, or the protocol layer entity selects a reference timer from the first discard timer and a second discard timer (a discard timer with DRB granularity), and starts the reference timer; when the first discard timer expires, or, when the reference timer expires, the protocol layer entity deletes the SDU and a PDU corresponding to the SDU.