Contention-Based Time Period Allocation for Latency-Sensitive Traffic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems face challenges in efficiently managing latency-sensitive traffic due to variability and jitter, leading to suboptimal scheduling and resource allocation, particularly in scenarios requiring deterministic and non-deterministic traffic handling.
Innovation Solution
Implementing a contention-based time period allocation mechanism using a predefined Association Identifier (AID) value in trigger frames to allow non-AP stations to transmit latency-sensitive traffic according to a channel contention mechanism, with parameters such as PPDU duration limits and EDCA settings, ensuring efficient allocation of resources during contention-based time periods.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional scheduling mechanisms are used for wireless communication, then resource allocation is simplified, but latency-sensitive traffic cannot be efficiently handled due to variability and jitter
Solution Approach 1:
The wireless medium access is segmented into different types of access opportunities: scheduled access for deterministic traffic and contention-based access for non-deterministic latency-sensitive traffic. This segmentation allows each type of traffic to use the most appropriate access mechanism, improving latency handling while maintaining scheduling simplicity for non-latency-sensitive traffic.
Solution Approach 2:
The system dynamically switches between scheduled access and contention-based access mechanisms depending on traffic characteristics. Latency-sensitive traffic that arrives outside scheduled opportunities can contend for channel access, providing adaptive response to varying traffic conditions while keeping the overall scheduling framework relatively simple.
2Productivity
If contention-based access is allowed for all traffic, then channel utilization improves, but deterministic scheduling for latency-sensitive traffic deteriorates due to access variability
Solution Approach 1:
Different quality characteristics are applied to different access mechanisms: scheduled access provides deterministic timing for critical traffic, while contention-based access provides high channel utilization for non-critical traffic. Each access opportunity has locally optimized properties suitable for its intended traffic type, resolving the contradiction between determinism and utilization.
Solution Approach 2:
The scheduled access opportunities act as an intermediary mechanism that provides deterministic service for latency-sensitive traffic, while allowing contention-based access to fill gaps and improve overall channel utilization. The scheduled opportunities mediate between the need for determinism and the benefit of higher utilization by providing a structured framework within which contention can occur.
3Reliability
If scheduled access opportunities are provided for latency-sensitive traffic, then access variability is reduced, but channel utilization deteriorates due to fixed time allocations
Solution Approach 1:
The system ensures continuous useful action by combining scheduled access (providing regular, reliable opportunities) with contention-based access (filling unused opportunities). This continuity maximizes channel utilization while maintaining the reliability benefits of scheduled access for latency-sensitive traffic, as contention can occur both within scheduled opportunities and in between them.
4Speed
If channel contention mechanism is implemented for non-AP stations, then prioritized access for latency-sensitive traffic is achieved, but system complexity increases due to additional parameters and settings
Solution Approach 1:
The patent applies partial action by implementing contention-based access only for specific non-AP stations with latency-sensitive traffic, rather than for all stations. This selective application provides prioritized access where needed while limiting the increase in system complexity to only the necessary extent, avoiding excessive configuration overhead.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
For example, an Access Point (AP) may be configured to set an Association Identifier (AID) field to a predefined AID value. For example, the predefined AID value may be configured to indicate that a non-AP station (STA) having latency-sensitive traffic is to be allowed to transmit a non-Trigger-Based (non-TB) Physical layer (PHY) Protocol Data Unit (PPDU) including the latency-sensitive traffic according to a channel contention mechanism during a contention-based time period. For example, the AP may be configured to transmit a trigger frame to allocate the contention-based time period. For example, the trigger frame may include the AID field.