UWB Clock Synchronization via Firmware Layer Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication technologies face challenges in efficiently managing clock synchronization over ultra-wideband (UWB) and Bluetooth Low Energy (BTLE) links, particularly in reducing power consumption and maintaining accuracy while allowing devices to operate without activating the application processor (AP), which leads to battery drain and synchronization delays.
Innovation Solution
The system configures a mobile device to perform clock synchronization using the firmware layer, specifically the Logical Link Control and Adaptation Protocol (L2CAP) layer, without accessing the application processor, allowing continuous synchronization and maintaining the AP in a hibernation state to conserve power and reduce processing delays.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the application processor is activated to handle synchronization requests, then synchronization accuracy is improved, but power consumption increases and battery life decreases
Solution Approach 1:
The patent divides the synchronization processing into two segments: firmware layer processing for basic synchronization requests and application processor processing for complex requests. This segmentation allows the system to handle routine synchronization tasks without activating the AP, thereby reducing power consumption while maintaining accuracy for essential functions.
Solution Approach 2:
The firmware layer is designed to autonomously handle synchronization requests independently without requiring AP intervention. The firmware performs clock synchronization operations using its own resources, eliminating the need to wake the AP for routine tasks and thus reducing overall power consumption while maintaining synchronization accuracy.
2Productivity
If the application processor is activated to process synchronization requests, then processing capability is improved, but processing time increases and synchronization delay increases
Solution Approach 1:
The patent segments processing capabilities between firmware and application processor. The firmware handles time-critical synchronization requests immediately without waiting for AP activation, while the AP handles complex processing tasks. This segmentation eliminates the delay associated with AP activation and ensures rapid response to synchronization requests.
Solution Approach 2:
The firmware layer performs preliminary synchronization processing and prepares responses in advance, so that when synchronization requests arrive, the system can respond immediately without activating the AP. This preliminary action reduces processing time and eliminates synchronization delays associated with AP wake-up and initialization.
3Measurement precision
If continuous clock synchronization is performed, then synchronization accuracy is maintained, but power consumption increases
Solution Approach 1:
The patent implements periodic clock synchronization at the firmware layer without requiring continuous AP activation. The firmware performs synchronization at appropriate intervals based on system needs, maintaining accuracy while allowing the AP to remain in low-power states between synchronization events, thus reducing overall battery consumption.
Solution Approach 2:
The firmware layer performs continuous or periodic synchronization operations autonomously without requiring AP participation. This self-service capability allows the system to maintain synchronization accuracy through firmware-based clock adjustments while the AP remains in hibernation, significantly reducing battery consumption compared to AP-based continuous synchronization.
Data Source
AI summary
An example system includes an application processor (AP), a transceiver associated with a firmware layer and a controller. The controller is configured to perform operations that include receiving data representing a clock synchronization request from a remote device, such as a UWB clock synchronization request. The request is received by the transceiver over a wireless communication link. The controller generates a response to the synchronization request. The response is configured for synchronizing a remote clock of the remote device and a local clock of the mobile device. The controller sends, to the remote device by the transceiver, the response to the synchronization request.