Bluetooth Isochronous Data Transmission Protocol for Low Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Bluetooth Low Energy (BLE) communication protocols experience inefficiencies in data transfer, particularly in sensor applications, due to constant overhead from 'request-response' mechanisms, leading to increased latency and reduced report rates, which is detrimental for applications like gaming and sensor data transmission.
Innovation Solution
A communication protocol that defines a unique starting time point for data transmission from peripheral devices, eliminating the need for continuous requests from central devices, allowing isochronous data to be transmitted without waiting for prompts, and using an integrity signal for batch data packet verification to reduce overhead and latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If conventional BLE request-response communication is used, then devices can exchange data reliably, but latency increases and report rates decrease due to constant overhead from requests and feedback signals
Solution Approach 1:
The central device pre-configures report event parameters including time offsets, interval settings, and data formats before the peripheral device begins transmission. This preliminary configuration eliminates the need for continuous request-response exchanges during data transfer, reducing latency while maintaining reliability through pre-established communication rules
Solution Approach 2:
The patent implements periodic report events where peripheral devices transmit sensor data at predetermined intervals based on configured time offsets. This periodic transmission pattern eliminates unnecessary continuous requests and feedback signals, reducing communication overhead and latency while maintaining reliable data exchange through structured periodic updates
2Reliability
If continuous request-response mechanisms are used, then data can be verified for integrity, but communication overhead increases and power consumption rises
Solution Approach 1:
The patent establishes continuous periodic data transmission from peripheral to central devices without requiring continuous acknowledgment cycles. The central device receives data streams continuously at configured intervals, eliminating the need for repeated request-response pairs while maintaining data integrity through continuous monitoring and error detection mechanisms built into the periodic transmission protocol
Solution Approach 2:
Peripheral devices autonomously transmit data according to pre-configured report events without requiring continuous commands from the central device. The system self-regulates transmission timing and intervals based on configured parameters, reducing the need for active management and feedback signals that would increase power consumption
3Productivity
If request-response protocols are used, then communication can be controlled and managed, but report rates are reduced and data transfer efficiency decreases
Solution Approach 1:
All communication control parameters including report intervals, time offsets, and transmission formats are pre-configured before data transfer begins. This preliminary setup enables high-speed autonomous data exchange without requiring continuous control signals, thereby increasing data transfer efficiency while maintaining communication control through pre-established parameters
Solution Approach 2:
Data transmission follows a periodic pattern with fixed intervals and time offsets, enabling efficient bulk data transfer without the overhead of continuous control messages. This periodic structure maintains ease of operation through predictable timing while maximizing report rates by eliminating unnecessary interstitial requests and acknowledgments
Data Source
AI summary
The present disclosure relates to a method of managing a data transmission from a second device to a first device, the method including: determining a reference time point for the data transmission from the second device to the first device; determining a time offset associated with the second device, wherein the reference time point and the time offset define a starting time point for the second device to start the data transmission; and carrying out the data transmission from the second device to the first device in accordance with the starting time point, wherein the data transmission includes transmitting isochronous data from the second device to the first device.


