Wireless Mesh Beacon Timing Synchronization Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In wireless mesh networks, achieving timing synchronization and beacon generation is challenging due to the diversity of devices, particularly for mesh points (MPs) that need to operate in both infrastructure and independent basic service set (IBSS) modes, with issues like beacon collisions and power save modes complicating synchronization.
Innovation Solution
The proposed solution involves a beacon generation algorithm for mesh points that allows non-AP mesh points to transmit a synchronization capability field in their beacons, enabling them to indicate support for synchronization, request synchronization from peers, and manage their timing synchronization function independently, while MAPs operate in infrastructure mode and never enter power save mode, ensuring timely delivery of traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If non-AP mesh points operate in IBSS mode with distributed timing synchronization, then flexibility and adaptability are improved, but beacon collisions and synchronization complexity increase
Solution Approach 1:
The patent segments mesh points into two distinct operational modes: MAPs that operate in infrastructure mode with centralized timing control, and non-AP mesh points that can operate in IBSS mode with distributed synchronization. This segmentation allows each type to use the synchronization mechanism best suited to its role, reducing overall system complexity while maintaining flexibility.
Solution Approach 2:
The patent implements dynamic behavior where non-AP mesh points can transition between synchronized and unsynchronized states based on network conditions. The synchronization capability field in beacons allows devices to dynamically adjust their timing behavior, enabling the system to adapt to changing topologies and reduce beacon collisions when needed.
2Reliability
If MAPs synchronize with other mesh points, then network coordination is improved, but beacon collisions and timing conflicts increase
Solution Approach 1:
The patent extracts the timing synchronization function from MAPs, allowing them to operate independently without synchronizing with other mesh points. This extraction eliminates the source of beacon collisions while non-AP mesh points that need coordination can do so through the IBSS mode mechanism without affecting MAP operations.
Solution Approach 2:
The patent applies different synchronization qualities to different devices: MAPs operate with independent timing (infrastructure mode quality), while non-AP mesh points can optionally synchronize with peers (IBSS mode quality). This local differentiation ensures that synchronization only occurs where needed, avoiding beacon collisions in MAP operations.
3Use of energy by moving object
If mesh points enter power save mode, then energy efficiency is improved, but timing synchronization and beacon delivery reliability decrease
Solution Approach 1:
The patent introduces the synchronization capability field as an intermediary mechanism that allows power save status to be communicated between devices. This enables non-AP mesh points to indicate when they are in power save mode, allowing other devices to adjust beacon timing accordingly while maintaining reliability for critical traffic.
Solution Approach 2:
The patent implements preliminary action by having non-AP mesh points advertise their power save status in advance through beacon frames. This allows the network to pre-adjust timing and beacon delivery parameters before power save mode fully engages, ensuring reliable beacon delivery during critical periods while maintaining energy efficiency.
Data Source
AI summary
A method is used by a mesh point that includes one or more step of receiving one of a beacon and probe response from an other mesh point; setting a state of whether the mesh point is already synchronized with one or more peers to true and performing a beacon timing synchronization function when the mesh point is in the unsynchronized state and the other mesh point requests synchronization from a peer mesh point; adding an identity of the other mesh point to a database of beacon senders maintained by the mesh point and performing a beacon timing synchronization function when the mesh point and the other mesh point are both synchronized; and providing indications of whether the mesh point supports synchronization, requests synchronization from a peer mesh point, and is already synchronized with one or more peer.