Triggered TXOP Sharing With Access Class Traffic Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing IEEE 802.11be Draft specification lacks control over which non-AP STA should be selected for TXOP sharing, leading to inefficiencies in managing Quality of Service (QoS) for different Access Classes (ACs) of data queued in Enhanced Distributed Channel Access (EDCA).
Innovation Solution
The proposed solution involves incorporating Access Class (AC) limitations into the MU RTS TXS trigger frame to ensure that non-AP STAs only use the allocated TXOP time for data transmission if they have buffered units meeting the specified AC requirements, allowing the AP to schedule other STAs with suitable data for transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If triggered TXOP sharing is implemented without AC limitation rules, then non-AP STAs can transmit RTA traffic more easily, but there is no control over which STAs get priority transmission
Solution Approach 1:
The patent introduces AC limitation parameters into the TXS Trigger frame to control which non-AP STAs can access the shared TXOP. By specifying AC limitations (e.g., AC_BK, AC_BE, AC_VI, AC_VO) in the trigger frame, the AP can selectively enable or disable access for different traffic categories, thereby implementing prioritized transmission control while maintaining the TXOP sharing mechanism.
2Productivity
If TXOP time is allocated without AC requirements, then more STAs can access the channel, but QoS for different Access Classes cannot be managed
Solution Approach 1:
The patent applies local quality by differentiating access permissions for different ACs within the TXOP sharing mechanism. Instead of uniform access control, the AP can specify different AC limitations for different non-AP STAs or different traffic types, allowing high-priority traffic (e.g., AC_VO for voice, AC_VI for video) to receive preferential treatment while lower-priority traffic (e.g., AC_BK for background) receives standard access.
3Loss of time
If AP allocates TXOP time to non-AP STAs without AC verification, then transmission latency is reduced, but network performance for prioritized traffic deteriorates
Solution Approach 1:
The patent implements a feedback mechanism where the AP receives AC capability information from non-AP STAs and uses this information to make intelligent allocation decisions. The AP can verify whether a non-AP STA has the required AC capabilities before allocating TXOP time, ensuring that high-priority traffic is assigned to STAs that can handle it, thereby maintaining both low latency and high overall network performance.
Data Source
AI summary
A wireless protocol allowing an AP to allocate time within a transmit opportunity (TXOP) to non-AP stations. The allocations are made under condition that the non-AP STA(s) will satisfy Access Class (AC) requirements communicated in a frame sent by the AP STA, such as within an MU RTS TXS Trigger frame. Upon receiving the frame, the non-AP responds on whether it can meet the conditions, such as within a Clear-To-Send (CTS) message. If the non-AP can meet the conditions, then it proceeds to transmit data (to the AP, or a peer non-AP). Otherwise, if it cannot meet the conditions, then the AP can communicate the allocation to another non-AP STA. There are also conditions for how the non-AP can aggregate data units into A-MSDUs.