Peer-to-Peer Channel List Negotiation for 5GHz DFS Congestion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current peer-to-peer network systems are limited by the need for a designated group owner, which restricts channel selection and usage, particularly with Dynamic Frequency Selection (DFS) channels, leading to inefficient use of the 5GHz band and congestion in multi-peer networks.
Innovation Solution
A method where peer devices adjust their intent to be a group owner based on their capabilities, allowing them to exchange lists of channels supported as both group owners and clients, enabling dynamic selection of a group owner and channel for connection, including DFS channels, to optimize channel usage and reduce congestion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If devices transmit only channels supported as group owner, then connection reliability is improved, but channel availability and network efficiency deteriorate
Solution Approach 1:
The channel list is segmented into two distinct parts: channels supported as group owner and channels supported as client. This segmentation allows the system to separately manage and evaluate different channel types, enabling devices to connect through channels supported as client even when not supported as group owner, thereby increasing channel availability while maintaining connection reliability through proper role assignment
Solution Approach 2:
The system enables channels to serve multiple functions by allowing a channel to be in the 'supported as client' list of one device and the 'supported as group owner' list of another device. This multi-functionality allows the same channel to facilitate peer-to-peer connections even when individual devices have different capabilities, effectively universalizing channel usage across diverse device configurations
2Adaptability or versatility
If DFS channels are used with stringent monitoring requirements, then channel diversity is improved, but device compatibility and ease of operation deteriorate
Solution Approach 1:
The system embraces asymmetry by allowing different devices to have different channel capability profiles. One device may support DFS channels as group owner while another supports them only as client. This asymmetric approach allows DFS channels to be utilized in peer-to-peer connections without requiring both devices to have identical capabilities or to meet stringent monitoring requirements, thereby improving channel diversity while maintaining ease of operation
Solution Approach 2:
The channel capability exchange mechanism acts as an intermediary that mediates between devices with different DFS channel capabilities. By sharing and comparing capability lists, the system determines appropriate group owner and client roles that accommodate DFS channel usage without requiring both devices to implement stringent monitoring, thus enabling DFS channel diversity while preserving device compatibility
3Adaptability or versatility
If symmetric channel list exchange is implemented, then fairness and adaptability are improved, but negotiation complexity increases
Solution Approach 1:
The system merges the channel capability exchange with the existing peer-to-peer connection negotiation process. By combining these functions, the patent avoids creating a separate complex negotiation protocol while still achieving symmetric information exchange about channel capabilities supported as group owner and as client, thereby improving fairness without proportionally increasing negotiation complexity
Data Source
Figure 1
Figure 2
Figure 3a~3b
AI summary
A method of facilitating peer-to-peer connection involves transmitting (S54), by a first peer device, an identification of the first peer device and information regarding its capabilities, the information regarding its capabilities including a list of transmission channels that the first peer device is capable of supporting. The list including an indication of which transmission channels the first peer device is capable of supporting as a group owner, and/or an indication of which transmission channels the first peer device is capable of supporting as a client. The first peer device receives (S54) from a second peer device, an identification of the second peer device and information regarding its capabilities including a list of transmission channels that the second peer device is capable of supporting, and the first peer device and the second peer device then negotiate (S56) which of the first and second peer devices should be the group owner and which should be the client.