Bluetooth Pairing via Account Login and Pre-Stored Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Bluetooth pairing methods using MAC addresses and UUIDs are insecure and not user-specific, and key generation techniques like TLS require significant processing power, which is not feasible for small devices with limited battery resources.
Innovation Solution
A user-specific, automated Bluetooth pairing method using a pre-stored private key in a first device and downloading a public key in a second device, eliminating the need for MAC addresses or UUIDs, and utilizing public/private key encryption for secure connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If MAC address and UUID are used for Bluetooth pairing, then device identification is simple, but connection security is insufficient and not user-specific
Solution Approach 1:
The patent applies preliminary action by pre-provisioning the first device with a private key during manufacturing. This pre-established cryptographic credential enables secure automated pairing without requiring complex runtime security negotiations, thus improving connection security while maintaining pairing simplicity.
Solution Approach 2:
The patent introduces public/private key cryptography as an intermediary mechanism between devices. The private key in the first device and corresponding public key in the second device act as cryptographic mediators that enable secure user-specific pairing, resolving the security deficiency of MAC address/UUID-based pairing without significantly increasing device complexity.
2Reliability
If TLS key generation is used for secure connection, then connection security is improved, but processing power and battery consumption increase significantly
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 runtime, allowing small devices with limited battery power to achieve secure pairing without excessive energy consumption.
Solution Approach 2:
The patent extracts the computationally heavy key generation process from the runtime pairing operation and moves it to the manufacturing stage. By separating key generation from pairing execution, the patent enables secure connections for resource-constrained devices that cannot perform intensive cryptographic operations during normal operation.
3Ease of operation
If MAC address is used for pairing, then device identification is straightforward, but vulnerability to spoofing attacks increases
Solution Approach 1:
The patent introduces cryptographic key verification as an intermediary layer between device identification and connection establishment. The public/private key mechanism serves as a mediator that verifies device authenticity without exposing vulnerable identifiers like MAC addresses, thus maintaining pairing simplicity while eliminating spoofing vulnerabilities.
Solution Approach 2:
The patent replaces the use of physical device identifiers (MAC addresses) with cryptographic copies (public keys) for device identification. The public key acts as a secure copy that represents the device's identity without revealing vulnerable underlying identifiers, preventing spoofing while maintaining operational simplicity.
Data Source
AI summary
This disclosure relates to creating a connection between two devices without using a UUID and/or MAC address. For example, a first device can store a private key for creating a secure connection. 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 the wireless connection. The second device user can enter login credentials via the second device, which may then be transmitted to a backend system. The backend system can receive and validate the login credentials and, in response, transmit a public key to the second device. The second device can use the public key to perform a public/private key handshake in order to validate the first device.