Bluetooth Low Energy Connection Management via Selective Data Loading
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Bluetooth Low Energy (BLE) devices face inefficiencies in managing multiple connections due to the persistent storage of pairing information and context data in volatile memory, leading to increased power consumption and memory usage, especially during power-on reset when not all bonded devices are actively connected.
Innovation Solution
Implement a method where only device identification information is copied from non-volatile memory to volatile memory at power-on reset, and persistent data is transferred only when a bonded peer device forms an active connection, optimizing memory usage and power conservation by selectively loading information based on active connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all bonding information is copied from non-volatile memory to volatile memory at power-on reset, then connection reliability is improved, but startup time and power consumption increase
Solution Approach 1:
The patent extracts only the essential device identification information (device address and identity resolving key) from the bonding information, separating it from the complete bonding data. This selective extraction allows the system to load minimal necessary data into volatile memory at power-on reset, reducing startup time while maintaining connection reliability through the preserved essential identifiers.
Solution Approach 2:
The bonding information is segmented into two parts: device identification information (loaded at power-on reset) and complete bonding information (loaded on-demand during active connection). This segmentation allows the system to handle different data portions at different times, optimizing both startup performance and connection reliability.
2Reliability
If all bonding information is copied from non-volatile memory to volatile memory at power-on reset, then connection reliability is improved, but memory usage increases
Solution Approach 1:
The patent extracts only the essential device identification information (device address and identity resolving key) from the bonding information, separating it from the complete bonding data. This selective extraction allows the system to load minimal necessary data into volatile memory at power-on reset, reducing startup time while maintaining connection reliability through the preserved essential identifiers.
Solution Approach 2:
The bonding information is segmented into two parts: device identification information (loaded at power-on reset) and complete bonding information (loaded on-demand during active connection). This segmentation allows the system to handle different data portions at different times, optimizing both startup performance and connection reliability.
3Reliability
If data restore operations are performed for each bonded peer device, then connection reliability is improved, but power consumption and processing overhead increase
Solution Approach 1:
The patent implements periodic action by performing data restore operations only when needed (during active connection events) rather than continuously or at every power-on reset. This event-driven approach maintains connection reliability by restoring data on-demand while significantly reducing unnecessary power consumption and processing overhead during idle periods.
Solution Approach 2:
The system implements self-service by automatically restoring complete bonding information only when an active connection event occurs, without requiring continuous processing or manual intervention. This on-demand restoration mechanism maintains reliability while minimizing power consumption by performing operations only when the system naturally needs them.
4Reliability
If context information is kept in volatile memory for disconnected peer devices, then reconnection reliability is improved, but memory usage and power consumption increase
Solution Approach 1:
The patent extracts only the essential device identification information (device address and identity resolving key) from the bonding information, separating it from the complete bonding data. This selective extraction allows the system to load minimal necessary data into volatile memory at power-on reset, reducing startup time while maintaining connection reliability through the preserved essential identifiers.
Solution Approach 2:
The bonding information is segmented into two parts: device identification information (loaded at power-on reset) and complete bonding information (loaded on-demand during active connection). This segmentation allows the system to handle different data portions at different times, optimizing both startup performance and connection reliability.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods and systems are disclosed for multiple connection management for Bluetooth (BT) devices, and more particularly for BT Low Energy (BLE) devices, to multiple different bonded BT peer devices. A BT device database within a non-volatile memory (NVM) stores identification and persistent information for each bonded BT peer device. At power-on reset (PoR), only device identification information (DII) data, such as an address (ADDR) and an IRK (identity resolving key), for each bonded BT peer device is copied from the NVM to a volatile memory that is used for run-time operation. When a bonded BT peer device forms an active connection, it is identified using the DII data, and its persistent data is copied from NVM to volatile memory as run-time data. The BT device then communicates with the actively connected BT peer device at least in part using the run-time data for the actively connected BT peer device.