Automated Bluetooth Pairing via Backend Key Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Bluetooth pairing methods using MAC addresses or UUIDs are not secure and do not provide user-specific connections, and existing key generation techniques are resource-intensive, making them unsuitable for small devices with limited battery power.
Innovation Solution
Implementing a user-specific, automated Bluetooth pairing system using a pre-stored private key in a first device and downloading a public key in a second device, which enables secure connections without relying on MAC addresses or UUIDs, utilizing public/private key encryption and a backend system for key management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If MAC address or UUID is used for Bluetooth pairing, then device identification is simple, but connection security is insufficient
Solution Approach 1:
The patent applies preliminary action by pre-provisioning the first device with a private key during manufacturing. This allows the device to immediately participate in secure pairing without requiring complex key generation at runtime, thus improving security while managing complexity through advance preparation.
Solution Approach 2:
The patent introduces a backend system as an intermediary that facilitates secure key exchange. The backend system receives authentication credentials, generates public keys, and transmits them to the second device, enabling secure pairing without direct complex interactions between the Bluetooth devices themselves.
2Reliability
If public key cryptography is implemented for secure pairing, then connection security is improved, but processing requirements increase
Solution Approach 1:
The patent applies preliminary action by pre-generating and storing the private key in the first device during manufacturing. This eliminates the need for computationally intensive key generation during Bluetooth pairing, reducing real-time processing requirements and power consumption while maintaining security.
Solution Approach 2:
The first device uses its pre-stored private key to autonomously authenticate itself to the backend system without requiring external assistance. This self-service capability reduces processing burden on both the first device and the backend system during the pairing process.
3Productivity
If automated pairing with pre-stored keys is implemented, then pairing speed is improved, but device provisioning complexity increases
Solution Approach 1:
The patent applies preliminary action by pre-provisioning the first device with a private key during manufacturing. This advance preparation enables rapid automated pairing without requiring complex runtime key management, thus improving pairing speed while concentrating complexity in the manufacturing process.
Solution Approach 2:
The backend system acts as an intermediary that manages the complexity of public key distribution. It receives authentication credentials from the second device, generates corresponding public keys, and transmits them appropriately, thereby simplifying the overall system architecture while enabling fast automated pairing.
Data Source
AI summary
This disclosure relates to creating a Bluetooth and/or BLE connection between two devices without using a UUID and/or MAC address. For example, a first device storing a private key may enter advertising mode to create a Bluetooth/BLE connection. An advertising packet (e.g., advertising channel packet data unit (PDU)) may be transmitted (e.g., in encrypted format). A second device may enter scanning or initiator mode and may receive the advertising packet. A second device may request that a user log into an account associated with the first device (e.g., a customer account, a financial account, an employee account, and/or the like) in order to initiate a Bluetooth/BLE connection. A second device user may enter login credentials via the second device, which may then be transmitted to a backend system. A backend system may receive and validate the login credentials and, in response, transmit a public key to the second device. The public key may be transmitted in an encrypted format. A second device may receive the public key and may use the public key to perform a public/private key handshake in order to validate the first device. The handshake may then be validated by the first device and a Bluetooth and/or BLE connection may be created.