Target Wake Time Scheduling for Wireless Mesh Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional techniques for scheduling network traffic in wireless communications devices are inefficient in terms of power consumption and fail to address network collisions and stringent latency requirements, particularly in mesh networks used for gaming applications.
Innovation Solution
Implementing a target-wake-time (TWT) scheduling method that configures network traffic schedules with trigger-based transmission and listening periods, allowing devices to optimize power usage while reducing network contention and meeting latency constraints.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If conventional network traffic scheduling is used in wireless communications, then devices can communicate with each other, but power consumption is high and network collisions occur
Solution Approach 1:
The patent implements Target Wake Time (TWT) scheduling that pre-configures wake times and service periods for devices before actual data transmission. This preliminary scheduling allows devices to know in advance when to wake up and transmit/receive data, avoiding random access collisions and reducing the need for retransmissions, thereby improving reliability while managing power consumption
Solution Approach 2:
The patent employs periodic wake intervals and service periods in the TWT mechanism. Devices wake up at predetermined periodic intervals to exchange data during allocated service periods, then return to sleep mode. This periodic structure ensures organized access to the network medium, preventing collisions while allowing devices to conserve power during sleep intervals
2Loss of time
If devices remain active to meet stringent latency requirements, then latency constraints are satisfied, but power consumption increases
Solution Approach 1:
The TWT mechanism pre-configures wake times and service periods in advance, allowing devices to know exactly when to be active for data transmission. This eliminates unnecessary wake-sleep cycles and ensures devices are awake only when needed, meeting latency requirements while minimizing power consumption by keeping devices in low-power state during non-critical periods
Solution Approach 2:
The patent implements dynamic TWT adjustments where wake intervals and service period durations can be modified based on actual network conditions and traffic patterns. This dynamic adaptation allows the system to optimize the balance between latency performance and power consumption by adjusting activity levels according to real-time requirements
3Loss of energy
If TWT scheduling with trigger-based transmission is implemented, then power consumption is reduced and network contention is minimized, but system complexity increases
Solution Approach 1:
The TWT mechanism serves multiple functions simultaneously: it schedules wake times for power saving, allocates service periods for data transmission, coordinates multiple devices to avoid collisions, and provides a framework for both scheduled and on-demand traffic. This multi-functionality reduces the need for separate mechanisms, managing system complexity while achieving power efficiency and collision avoidance
Data Source
AI summary
Systems, methods, and devices schedule network traffic for wireless communications devices. Methods include identifying a plurality of stations included in a first network, and generating, using one or more processors of a first access point, a network traffic schedule configured to assign a plurality of service periods to the plurality of stations, the network traffic schedule identifying a plurality of sleep times and wake times for the plurality of stations. Methods further include transmitting a query frame to at least one station of the plurality of stations during a designated service period, and receiving a data transmission from the at least one station, the data transmission being generated by the station based on transmission parameters included in the query frame.