BLE Control Procedure Responses Within One Connection Event
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Bluetooth Low Energy (BLE) protocols close connection events prematurely when devices indicate they have no more data to send, preventing timely responses to control procedure requests, leading to delays in completing control procedures.
Innovation Solution
Devices set the MD bit to indicate they have more data to send, even if they don't, maintaining the connection event open to allow substantive responses during the same event, thereby accelerating control procedures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If devices set the MD bit to indicate they have more data to send even when they don't, then the connection event remains open allowing substantive responses during the same event, but this deviates from the standard BLE protocol behavior where the MD bit should accurately reflect the actual data transmission state
Solution Approach 1:
The patent inverts the conventional meaning of the MD bit. Instead of setting MD=1 only when actual data is present in the transmission queue, the device sets MD=1 during control procedure packets to prevent connection event closure, regardless of whether data is actually queued. This inversion allows the connection to remain open for substantive responses while the data field remains empty or contains only control information.
Solution Approach 2:
The patent changes the interpretation and usage of the MD bit parameter from its standard definition. The MD bit is repurposed as a connection maintenance signal rather than a data availability indicator during control procedures. This parameter change enables the connection event to extend beyond the control procedure exchange, allowing time for substantive data transmission responses.
2Productivity
If devices wait for the next connection event to respond to control procedure requests, then protocol compliance is maintained, but control procedure completion is delayed
Solution Approach 1:
The patent performs preliminary action by maintaining the connection event open during the control procedure exchange itself, rather than waiting for the next scheduled connection event. By setting the MD bit to prevent closure, the device prepares the connection state in advance to accommodate substantive responses within the same event window, eliminating the waiting period between control procedure completion and data transmission.
Solution Approach 2:
The patent ensures continuity of useful action by keeping the BLE connection event active throughout the control procedure exchange. Instead of allowing the connection to close and requiring a new connection event for substantive responses, the connection remains continuous and open, enabling immediate follow-up data transmission without interruption or delay to the next connection interval.
3Reliability
If the MD bit accurately reflects data availability, then protocol correctness is maintained, but connection events close prematurely preventing timely responses
Solution Approach 1:
The patent applies local quality by differentiating the MD bit behavior based on packet type. During control procedure packets, the MD bit is set to 1 to maintain connection openness regardless of data availability. For regular data packets, the MD bit continues to accurately reflect transmission queue status. This localized modification preserves protocol correctness for data transmission while enabling connection maintenance during control procedures.
Solution Approach 2:
The patent introduces dynamics to the MD bit usage, making its value dependent on the operational context. The MD bit dynamically adjusts between accurately reflecting data availability during normal operation and serving as a connection maintenance signal during control procedures. This dynamic behavior allows the system to adapt the protocol parameter usage to different operational phases, optimizing both reliability and productivity.
Data Source
AI summary
A first BLUETOOTH device includes a transceiver configured to receive a control procedure packet from a second BLUETOOTH device during a BLUETOOTH connection event of a BLUETOOTH connection between the first BLUETOOTH device and the second BLUETOOTH device. The first BLUETOOTH device also includes a controller coupled to the transceiver and configured to set a more data (MD) bit of a response packet to the control procedure packet to a first value independent of whether the first BLUETOOTH device has more data to send to the second BLUETOOTH device. The first value corresponds to maintaining the BLUETOOTH connection event open. The transceiver is further configured to send the response packet to the second BLUETOOTH device during the BLUETOOTH connection event.