Bluetooth Handover Address Mapping for Seamless Connection Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network handover procedures in Bluetooth devices require pre-configuration of the same network address across all devices, leading to scalability issues and potential connection loss during handover due to key refreshment and data packet decoding challenges.
Innovation Solution
A method for seamless handover between network devices without requiring pre-configured same network addresses, involving the transfer of network addresses and connection parameters between source and destination devices, maintaining separate data bases for each connection, and ensuring transparent communication continuity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the same network address is pre-configured across all Bluetooth devices for handover, then handover can be performed, but scalability is limited and connection loss occurs during handover due to key refreshment and data packet decoding challenges
Solution Approach 1:
The patent creates a virtual copy of the source device's network address (first network address) on the destination device. Instead of requiring physical reconfiguration or using the destination's own address, the destination device adopts the source's address as a virtual identifier, allowing seamless handover while maintaining scalability since each destination device can independently implement this virtual address mapping without affecting other devices in the network.
2Adaptability or versatility
If network address changes during handover from source device to destination device, then device mobility is enabled, but connection loss occurs due to key refreshment and data packet decoding issues
Solution Approach 1:
The destination device pre-configures itself with the source device's network address before the handover actually occurs. When the handover is initiated, the destination device is already prepared to communicate using the first network address, eliminating the need for address changes during the transition and preventing connection loss due to key refreshment and decoding issues.
3Ease of operation
If separate data bases are maintained for each network address, then connection management is improved, but device complexity increases
Solution Approach 1:
The patent segments the network connection management by maintaining separate data base structures for different network addresses within the destination device. Each data base stores connection parameters, bonding tables, and piconet clock timings specific to its associated network address, allowing independent management of connections without interfering with other addresses, thus improving connection management clarity despite increased data base structure complexity.
Data Source
Figure 1A~1B
Figure 2
Figure 3A
AI summary
One example discloses a network destination device: wherein the network destination device is configured to receive a handover message from a network source device; wherein the network source device is identified by a first network address; wherein the network destination device is identified by a second network address; wherein the handover message is configured to initiate a transfer of a user device from the network source device to the network destination device; wherein the network destination device is configured to communicate with the user device using both the first network address and the second network address.