TXOP Preemption Windows for Low-Latency Traffic Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless networks struggle with managing preemption of low-latency traffic, leading to channel access delays and inefficiencies in handling diverse traffic types and power saving modes, particularly for real-time applications requiring reduced latency.
Innovation Solution
Implementing mechanisms for resource management that include transmitting low-latency indications and reverse direction grants to facilitate efficient preemption within transmission opportunities, ensuring devices remain awake, and managing preemption windows to accommodate various traffic types and directions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If a device holds a TXOP for non-LL data transmission, then channel resources are utilized efficiently, but low-latency traffic experiences channel access delays
Solution Approach 1:
The TXOP is segmented into a first portion for non-LL data transmission and a second portion (LLT window) for low-latency traffic. This segmentation allows both non-LL and LL traffic to coexist within the same TXOP, reducing channel access delays for LL traffic while maintaining efficient channel utilization.
Solution Approach 2:
The TXOP holder transmits a Low Latency Indication (LLI) frame in advance to indicate the upcoming LLT window. This preliminary action allows LL traffic to be prioritized and transmitted without delay during the designated window, while the TXOP holder can continue transmitting non-LL data in the first portion.
2Use of energy by moving object
If a device enters power saving mode, then energy consumption is reduced, but real-time applications experience increased latency
Solution Approach 1:
The system performs preliminary actions by transmitting LLI frames and establishing LLT windows before the device enters power saving mode. This ensures that any pending low-latency traffic is transmitted during the LLT window while the device is awake, preventing latency accumulation during sleep periods.
Solution Approach 2:
The device dynamically adjusts its power saving behavior by remaining awake during designated LLT windows when low-latency traffic is expected. The power saving mode is activated during non-LLT periods, creating a dynamic balance between energy consumption and latency requirements.
3Loss of time
If the TXOP holder transmits an LLI frame, then low-latency traffic can be preempted, but the TXOP structure becomes more complex
Solution Approach 1:
The LLI frame serves multiple functions: it acts as a preemption indicator, defines the LLT window boundaries, and triggers the TXOP holder to pause non-LL transmissions. This multi-functionality reduces the need for separate signaling mechanisms and simplifies overall TXOP management despite the added preemption capability.
Data Source
AI summary
A first electronic device includes a transceiver configured to, during a TXOP held by the first electronic device, receive, from a second electronic device, a low latency indication (LLI) indicating a low latency traffic (LLT) request of the second electronic device corresponding with at least one of an uplink traffic request, a downlink traffic request, and a P2P traffic request, and transmit, in response to receipt of the LLI, an indication for one of an RDG or TXOP sharing for the second electronic device. The first electronic device also includes a processor operably coupled to the transceiver. The processor is configured to cause the first electronic device to refrain from transmitting non-LL data within the TXOP during an LLT window. The LLT window is a duration within the TXOP corresponding with the RDG or TXOP sharing in which the second electronic device may exchange the LLT or P2P traffic.