Wi-Fi Beacon Synchronization for Concurrent Network Throughput
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Wi-Fi Direct networks face inefficiencies due to unsynchronized beacon intervals between client devices and group owners, leading to reduced throughput, increased latency, and higher packet loss rates, especially in concurrent mode where devices switch between legacy Wi-Fi and peer-to-peer networks.
Innovation Solution
The client device informs the group owner of its beacon schedule, allowing the group owner to adjust its beacon interval to synchronize with the client's needs, ensuring optimal timing for data transfer and reducing the likelihood of beacon-miss-induced disconnections by specifying the desired ratio of time spent on each network based on anticipated network traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the group owner uses a fixed beacon interval without synchronization, then the device complexity is reduced, but the throughput decreases and latency increases
Solution Approach 1:
The client device sends a synchronization request to the group owner containing the client's desired beacon interval or offset. The group owner adjusts its beacon schedule based on this feedback from the client, enabling coordinated beacon timing without requiring complex autonomous synchronization algorithms on either device.
Solution Approach 2:
The group owner dynamically changes its beacon interval parameter based on the synchronization request received from the client. By adjusting the beacon timing parameter to match the client's needs, the system optimizes throughput and reduces latency while maintaining relatively simple device architecture.
2Productivity
If the group owner adjusts beacon interval to synchronize with client needs, then throughput improves and latency reduces, but the device complexity increases
Solution Approach 1:
Rather than the group owner autonomously determining optimal beacon timing, the system uses feedback from the client device to guide the adjustment. The client provides its desired beacon interval or offset information, and the group owner simply adjusts its schedule accordingly, keeping the complexity manageable through distributed decision-making.
Solution Approach 2:
The beacon interval is made dynamic and adjustable based on real-time synchronization requests from clients. The group owner transitions from using a fixed beacon schedule to a flexible, demand-driven schedule that can adapt to different client needs, improving performance without requiring complex autonomous control mechanisms.
3Ease of operation
If beacon intervals are unsynchronized between client and group owner, then the ease of operation is maintained, but packet loss rate increases
Solution Approach 1:
The client device provides feedback about its operational needs and desired beacon timing to the group owner. This feedback mechanism enables the group owner to adjust its beacon schedule in a way that supports the client's ease of operation between networks while simultaneously reducing packet loss through synchronized timing.
Solution Approach 2:
The synchronization mechanism performs preliminary coordination before data transmission occurs. By establishing aligned beacon intervals in advance through client-initiated synchronization requests, the system prevents packet loss before it occurs, maintaining both ease of operation and reliability.
Data Source
AI summary
Various approaches enable a computing device (e.g., mobile phone, tablet computer, etc.), serving as a client to inform a group owner (GO) of a peer-to-peer (P2P) group in a Wi-Fi Direct network or other such network regarding the timing of the group owner's beacon schedule. Advantageously, this synchronization of the beacon schedule between the client and the GO can enable improved throughput and latency of the client device when the client device is in concurrent mode (i.e., when the P2P client is connected to two networks such as a legacy Wi-Fi network with an AP and a P2P network with a GO).