Dynamic TDD Subframe Signaling for Variable Traffic Loads
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems, particularly in LTE/LTE-A and next-generation 5G networks, face inefficiencies in handling high and frequently changing traffic loads due to fixed or predetermined subframe structures, which do not adapt dynamically to varying traffic conditions.
Innovation Solution
Implementing techniques for dynamically selecting and indicating a subframe type in a TDD header, allowing for dynamic subframe types such as downlink-centric, uplink-centric, bi-directional, full-duplex, and distributed scheduling types, based on traffic conditions, to create self-contained subframes that include HARQ feedback within the subframe.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If fixed or predetermined subframe structures are used, then system simplicity and ease of operation are maintained, but adaptability to varying traffic conditions deteriorates
Solution Approach 1:
The patent implements dynamic subframe type indication where the subframe type (downlink-centric, uplink-centric, or bi-directional) is selected and indicated dynamically based on current traffic conditions. This allows the TDD system to adapt its subframe structure in real-time rather than using fixed predetermined structures, directly resolving the contradiction between adaptability and complexity by introducing controlled dynamics to the subframe configuration.
Solution Approach 2:
The patent changes the subframe type parameter dynamically by selecting from multiple predefined subframe types (downlink-centric, uplink-centric, bi-directional) based on traffic load characteristics. This parameter change approach allows the system to adapt to varying traffic conditions without fundamentally redesigning the subframe structure, balancing adaptability with manageable complexity.
2Productivity
If dynamic subframe types are implemented, then adaptability to traffic conditions improves, but device complexity and control overhead increase
Solution Approach 1:
The patent defines multiple predefined subframe types (downlink-centric, uplink-centric, bi-directional) in advance, each optimized for specific traffic patterns. Rather than creating complex control mechanisms on-the-fly, the system prepares these configurations beforehand and simply selects the appropriate one based on current traffic conditions, reducing control complexity while maintaining high productivity.
Solution Approach 2:
The system implements productivity improvement through controlled parameter changes by selecting from a limited set of predefined subframe types. This approach enhances communication efficiency by matching subframe characteristics to traffic demands while avoiding the complexity of entirely dynamic configuration, as the parameter space is constrained to specific predefined options.
3Reliability
If self-contained subframes with HARQ feedback are created, then reliability and duration of action improve, but subframe structure complexity increases
Solution Approach 1:
The patent merges the HARQ feedback mechanism within the same subframe structure, creating self-contained subframes where downlink data transmission and uplink HARQ feedback occur within a single subframe boundary. This merging improves reliability by ensuring feedback delivery within the same transmission interval while the complexity is managed through the use of predefined subframe types that already account for these combined functions.
Data Source
AI summary
Techniques are described for wireless communication. One method includes identifying a traffic condition associated with data to be transmitted between a network access device and at least one user equipment (UE); selecting, based at least in part on the traffic condition, a dynamic subframe type of a time-division duplex (TDD) subframe; and indicating the dynamic subframe type in a TDD header of the TDD subframe. Another method includes identifying, in a TDD header of a subframe, an indication of a dynamic subframe type of the TDD subframe; and transmitting data or receiving data in a data region of the TDD subframe based at least in part on the dynamic subframe type.