Multi-Link DRX Scheduling for 3GPP and Non-3GPP Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Inconsistent DRX-related parameters between 3GPP and non-3GPP access networks in network aggregation scenarios lead to synchronization issues and increased power consumption in user equipment during downlink data aggregation.
Innovation Solution
A method and apparatus for determining and reconfiguring configuration parameters for multiple network links based on initial parameters to enable synchronized data reception across both 3GPP and non-3GPP networks, using a unified DRX mechanism to manage power consumption and latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If different initial configuration parameters are used for 3GPP and non-3GPP access networks, then each network can operate with its native DRX mechanism, but synchronization issues arise between the receiving modules during downlink data aggregation
Solution Approach 1:
The patent transforms DRX parameters between different network types by establishing conversion relationships between 3GPP DRX parameters (drx-OnDurationTimer, drx-SlotOffset, drx-InactivityTimer, etc.) and non-3GPP DRX parameters (aDrx-OnDuration, aDrx-SlotOffset, aDrx-InactivityTimer, etc.). This parameter transformation enables unified scheduling across different access networks while maintaining their native DRX characteristics, thereby resolving the synchronization issue without sacrificing adaptability
Solution Approach 2:
The patent introduces a unified scheduling function in the network side that acts as an intermediary between 3GPP and non-3GPP access networks. This unified scheduler receives data from both networks, performs parameter conversion, and coordinates the delivery timing to ensure synchronized reception at the terminal, eliminating the need for terminal-side complex synchronization logic
2Loss of time
If real-time data reception is used in non-3GPP access networks, then data can be received immediately when available, but power consumption increases compared to DRX-based reception
Solution Approach 1:
The patent applies DRX parameter transformation to non-3GPP access networks, converting real-time reception parameters into DRX-based parameters (aDrx-OnDuration, aDrx-SlotOffset, aDrx-InactivityTimer, etc.). This allows non-3GPP networks to adopt discontinuous reception patterns similar to 3GPP, enabling terminals to enter sleep modes during inactive periods and thereby reducing power consumption while maintaining acceptable data reception timing
Solution Approach 2:
The patent implements periodic DRX cycles in non-3GPP access networks, where terminals activate receivers at regular intervals (drx-SlotOffset, aDrx-SlotOffset) rather than continuously monitoring. This periodic activation pattern reduces power consumption by keeping the receiver off during inactive periods while still capturing data transmissions that occur during active windows
3Reliability
If unified DRX parameter configuration is applied across multiple network links, then synchronization is improved, but the complexity of parameter management and conversion increases
Solution Approach 1:
The patent segments the parameter management function into two parts: network-side unified scheduling that handles parameter conversion and coordination, and terminal-side simplified execution that follows unified scheduling instructions. This segmentation places the complex parameter transformation logic in the network side where it can be centralized, while keeping the terminal side simple, thereby reducing overall system complexity while maintaining synchronization
Solution Approach 2:
The patent creates a universal DRX parameter framework that can handle both 3GPP and non-3GPP access networks through a single unified scheduling entity. The unified scheduler performs multiple functions including parameter conversion, coordination timing calculation, and data distribution across different access networks, eliminating the need for separate management mechanisms and reducing overall system complexity
Data Source
AI summary
A data transmission method includes obtaining a first initial configuration parameter for a first network link for communicating with a user terminal, and determining a target configuration parameter for at least one target network link based at least on the first initial configuration parameter. The at least one target network link includes at least a second network link for communicating with the user terminal, and the second network link has a second initial configuration parameter different from the first initial configuration parameter. The method further includes performing configuration parameter reconfiguration for at least the second network link based on the target configuration parameter, to enable the user terminal to receive data sent by the network terminal based on aggregation of the first network link and the second network link.


