Bluetooth binding method and system for electro-tricycle

Abstract

The invention discloses an electro-tricycle Bluetooth binding method and system, belongs to the technical field of electro-tricycle intelligent control, effectively improves the accuracy of data association of a production end, establishes'Bluetooth MAC address-equipment SN code-frame number 'three-dimensional mapping data through double verification of the production end, and improves the accuracy of data association of the production end. By combining station-level secondary verification and a production line sound-light alarm mechanism, data mismatching caused by manual wrong scanning and cross-station operation, AES-256 encrypted storage and cloud multi-access control are completely eradicated, data transmission and storage safety is guaranteed, the problems of single-dimension association and data leakage and tampering are solved, the safety of the whole process of a binding link is enhanced, and the safety of the whole process of the binding link is improved. The cloud triple verification resists illegal requests, the dynamic secret key is embedded into a frame number fragment and a timestamp, and the alarm triple verification and a failure dormancy mechanism are matched, so that hidden dangers such as secret key counterfeiting and multiplexing, communication defense line building through BLE connection and SN code secondary verification, open type pairing cracking and weak secret key security are avoided.

Description

Technical Field

[0001] This invention relates to the field of intelligent control technology for electric tricycles, specifically to a Bluetooth binding method and system for electric tricycles. Background Technology

[0002] With the continuous improvement of the intelligence level of electric tricycles, Bluetooth technology has been widely used in core scenarios such as vehicle status monitoring, remote control, and anti-theft alarms. As a key step in establishing a secure communication link between devices, Bluetooth pairing directly affects the implementation effect of vehicle intelligent functions and user experience.

[0003] However, existing Bluetooth pairing technology for electric tricycles still has many shortcomings that need to be addressed, making it difficult to meet the safety and accuracy requirements in practical applications:

[0004] 1. Insufficient accuracy of data association at the production end: In existing technologies, alarm Bluetooth hardware information (such as Bluetooth MAC address) is only associated with the vehicle identification number (VIN) in a single dimension, lacking a dual verification mechanism at the production workstation level, and failing to establish a three-dimensional mapping data system of "Bluetooth MAC address - device serial number - VIN". During the production process, data binding errors are easily caused by manual misscanning, cross-workstation operations, etc. At the same time, the collected data is mostly transmitted and stored in an unencrypted manner, posing a risk of data leakage or tampering, and creating security vulnerabilities for subsequent binding processes.

[0005] 2. Weak security of the binding link: The open Bluetooth search and pairing mode lacks effective access control policies, making it vulnerable to scanning and hijacking by unauthorized devices; the dynamic key relies on a single encryption algorithm and is not deeply integrated with key information such as the vehicle's unique identifier (such as a fragment of the VIN) and timestamp, posing a security risk of key forgery and reuse; the cloud verification process lacks a multi-dimensional verification mechanism and does not comprehensively verify the legitimacy of the APP, the source of the request, and the validity of the user account, making it difficult to resist attacks from unauthorized requests.

[0006] 3. Lack of security constraints in user operation scenarios: The QR code binding process does not have spatial and temporal restrictions, and does not use Bluetooth signal strength detection or other means to determine the actual distance between the user and the vehicle, resulting in the security risk of remotely stealing the vehicle identification number (VIN) QR code to obtain the Bluetooth address; at the same time, the Bluetooth information fed back from the cloud often has no expiration date, which further increases the probability of the information being used illegally, and there is a lack of effective protection mechanisms in abnormal verification scenarios, making it vulnerable to malicious cracking attempts.

[0007] In summary, existing Bluetooth binding methods have shortcomings in data accuracy, link security, and operational standardization, which not only affect the user binding experience but may also lead to security issues such as leakage of device control permissions and vehicle theft. Therefore, a Bluetooth binding method and system for electric tricycles is proposed. Summary of the Invention

[0008] The purpose of this invention is to provide a Bluetooth binding method and system for electric tricycles to solve the problems mentioned in the background art.

[0009] To achieve the above objectives, the present invention provides the following technical solution: a Bluetooth binding method for an electric tricycle, comprising the following steps:

[0010] S1. Dual verification and information association on the production side;

[0011] S2, User-side scenario-based QR code scanning and Bluetooth address acquisition;

[0012] S3, multi-factor Bluetooth connectivity and key pairing;

[0013] S4. Vehicle binding confirmation and status synchronization.

[0014] As a further preferred embodiment of this technical solution: In S1, the specific operating steps are as follows:

[0015] A1. Collect hardware information: During the production process of electric tricycles, the Bluetooth hardware information of the electric tricycle alarm is collected through the production execution system or barcode scanning equipment.

[0016] A2. Secondary Scan and Correlation Verification: Workers scan the vehicle chassis number nameplate barcode a second time. The production execution system compares the collected Bluetooth hardware information with the chassis number to see if they come from the same production station, thus forming mapping data.

[0017] A3. Verification result processing: If the workstation association is consistent, the mapping data is retained; if the workstation association is inconsistent, the production execution system triggers an audible and visual alarm and suspends the production line until it is re-scanned and confirmed.

[0018] A4. Encrypted Storage and Access Control: Verified mapping data is stored in a cloud database using an encryption algorithm. The cloud is equipped with multiple access verifications and only authorized servers of the company's official APP are allowed to access it.

[0019] In A1, Bluetooth hardware information includes the Bluetooth MAC address and device serial number, and the collected data is transmitted to the production execution system via the production line intranet;

[0020] In A2, the mapping data is the established three-dimensional mapping data of "Bluetooth MAC address-device SN code-vehicle frame number";

[0021] In A4, the encryption algorithm used is AES-256.

[0022] As a further preferred embodiment of this technical solution: In S2, the specific operating steps are as follows:

[0023] B1. Account Registration and Access: Users complete registration through the electric tricycle's accompanying APP. After successful registration, they will be taken to the "Device Binding" page.

[0024] B2. QR code scanning function activation restrictions: When the APP enables the Bluetooth scanning function, it will detect the Bluetooth signal strength of the surrounding electric tricycle alarms in real time. When the Bluetooth signal strength of the electric tricycle alarm is detected to be ≥-60dBm, the QR code scanning function will be activated.

[0025] B3. Binding Request Initiation: The user scans the QR code on the vehicle's VIN plate. After the APP parses the VIN, it automatically attaches the user's account and sends a Bluetooth information request to the cloud database.

[0026] B4. Cloud Verification and Information Feedback: The cloud database verifies the following in sequence: the validity of the APP's API key, whether the requesting IP is in the whitelist, the validity of the user account registration, and the binding status of the mobile phone number. After passing the triple verification, the Bluetooth MAC address is fed back to the APP using an encryption algorithm.

[0027] In B1, you need to bind your mobile phone number and complete SMS verification during registration to ensure the uniqueness of your account. The mobile phone number binding is generated in real time through the enterprise server.

[0028] In B2, if the APP detects a Bluetooth signal strength of <-60dBm, it will prompt the user to approach the vehicle and try again.

[0029] In B4, the encryption algorithm uses the RSA asymmetric encryption algorithm, and the validity period of the feedback information is 10 minutes.

[0030] As a further preferred embodiment of this technical solution: In S3, the specific operating steps are as follows:

[0031] C1. BLE Connection Initiation and Device SN Code Secondary Verification: Within the validity period of the information fed back by the APP in the cloud, the APP automatically initiates a BLE connection request based on the obtained Bluetooth MAC address, and the connection process adopts "Bluetooth device SN code secondary verification".

[0032] C2. Dynamic Key Generation: After the Bluetooth connection is established, the background uses an encryption algorithm to generate a dynamic key, and the key embeds the last 6 digits of the vehicle identification number and the generation timestamp accurate to the second.

[0033] C3. Alarm Triple Authentication and Anomaly Handling: After receiving the key, the alarm performs triple authentication:

[0034] Verify that the key length is 16 bits;

[0035] Verify whether it contains the last 6 digits of the vehicle identification number (VIN).

[0036] Verify that the difference between the key generation time and the current time of the alarm is ≤1 minute;

[0037] If the triple verification is successful, pairing is complete; otherwise, pairing is rejected and the specific error type is reported to the APP. After three consecutive verification failures, the alarm's Bluetooth module will go into sleep mode for 5 minutes.

[0038] In C1, the APP reads the device SN code in the alarm broadcast packet and compares it with the unique device identification code fed back by the cloud. If they match, the connection continues.

[0039] In C2, the encryption algorithm used is AES-128.

[0040] In C3, the time difference is the difference between the current time of the alarm and the key generation timestamp, accurate to the second.

[0041] As a further preferred embodiment of this technical solution: In S4, the specific operating steps are as follows:

[0042] D1. Binding Confirmation Request Initiation: After successful Bluetooth pairing, the APP sends a binding confirmation request containing "Vehicle Identification Number - User Account - Bluetooth MAC Address" to the cloud database, along with a timestamp of the successful pairing.

[0043] D2. Cloud Recording and Status Marking: The cloud database stores the binding relationships recorded in D1, generates a full-process log containing "binding time - verification node", and marks the vehicle as "bound" in the same state.

[0044] D3. Result Feedback and Local Caching: The cloud returns a binding success command to the APP. The APP uses encrypted caching of binding information locally and displays a "Binding Successful" interface, thus completing the Bluetooth binding of the entire vehicle.

[0045] As a further preferred embodiment of this technical solution, it also includes an unbinding step: the user initiates an unbinding request through the APP, the cloud deletes the binding record, marks the vehicle as unbound, sends an unbinding command to the alarm, and the APP clears its local cache.

[0046] An electric tricycle Bluetooth binding system includes a production-side dual verification module, a user-side scenario-based interaction module, a triple verification module, a full-process recording module, and an exception handling module. The production-side dual verification module is used to collect, verify, and encrypt the mapping data. The production-side dual verification module includes a production execution system, a barcode scanning device, and an encrypted storage unit.

[0047] The production execution system is used for information verification and process control at the production end, thereby laying a precise data foundation for end-to-end security binding.

[0048] The barcode scanning device is used for production-end information collection and verification, and the information collection includes hardware information collection and vehicle identification number (VIN) collection.

[0049] The encrypted storage unit is an AES-256 encrypted storage unit, used to ensure the storage security and uniqueness of key binding data on the production side, laying a secure and reliable data foundation for end-to-end Bluetooth binding.

[0050] As a further preferred embodiment of this technical solution: the user-side scenario-based interaction module is used to obtain the Bluetooth address and initiate a connection in a scenario-based manner. The user-side scenario-based interaction module includes a Bluetooth signal strength detection unit, a QR code parsing unit, a BLE communication unit, and a multi-factor key generation unit.

[0051] The Bluetooth signal strength detection unit achieves security verification of user terminal binding through spatial scene restrictions;

[0052] The QR code parsing unit is used to connect the user's scanning operation with the cloud information request, providing accurate vehicle identification data for Bluetooth binding, and strengthening security with scenario-based verification.

[0053] The BLE communication unit enables secure, efficient, and low-power Bluetooth connection and key data transmission between the APP and the electric tricycle alarm, laying the communication foundation for multi-factor key pairing.

[0054] The multi-factor key generation unit generates a dynamic key that is secure, unique, and timely, providing a verification basis for Bluetooth pairing.

[0055] As a further preferred embodiment of this technical solution: the triple verification module is deployed in the cloud and the alarm device for end-to-end security verification;

[0056] The full-process recording module is used to store binding records and mark vehicle binding status. The full-process recording module includes a binding log storage unit, a vehicle status marking unit, and a local encrypted cache unit.

[0057] The binding log storage unit is used to store the complete binding relationship of "Vehicle Identification Number - User Account - Bluetooth MAC Address", generate and retain a full-process log containing "Binding Time - Verification Node", and provide data basis for the traceability and verification of the entire Bluetooth binding link;

[0058] The vehicle status marking unit is used to accurately mark the vehicle's "bound" or "unbound" status, forming a clear identifier of the vehicle's binding status, and providing basic support for the permission control and process connection of the entire Bluetooth binding process.

[0059] The local encrypted cache unit securely stores Bluetooth binding information locally within the APP, forming a dual data protection of "cloud + local" to support efficient and secure operation after binding.

[0060] As a further preferred embodiment of this technical solution: the exception handling module is used to handle abnormal scenarios such as production mismatch, verification failure and binding timeout. The exception handling module includes an MES alarm unit, an alarm sleep unit and an APP retry guidance unit.

[0061] The MES alarm unit is used to respond promptly to data mismatch issues during the production process, ensuring the accuracy of "one vehicle, one alarm, one mapping" and building a solid data security defense line for the entire Bluetooth binding process.

[0062] The alarm sleep unit is used to deal with malicious verification or frequent failures during the Bluetooth pairing process. By forcing the device into sleep mode, it blocks illegal operations and ensures the security of the Bluetooth binding of the electric tricycle and the stable operation of the alarm.

[0063] The APP retry guidance unit is used to provide accurate prompts and clear retry instructions for various abnormal scenarios in the entire Bluetooth binding process, reduce user operation costs, ensure the smooth progress of the binding process, and improve user experience and binding success rate.

[0064] Compared with the prior art, the beneficial effects of the present invention are:

[0065] 1. This invention effectively improves the accuracy of data association at the production end. It establishes a three-dimensional mapping data of "Bluetooth MAC address-device SN code-vehicle frame number" through dual verification at the production end. Combined with secondary verification at the workstation level and the sound and light alarm mechanism of the production line, it eliminates data mismatch caused by manual scanning errors and cross-workstation operations. AES-256 encrypted storage and cloud-based multi-access control ensure the security of data transmission and storage, and solve the problems of single-dimensional association and data leakage and tampering.

[0066] 2. This invention strengthens the security of the entire binding link process. The cloud triple verification (API key + IP whitelist + user account) resists illegal requests. The dynamic key is embedded with the vehicle identification number fragment and timestamp. Combined with the triple verification of the alarm and the failure sleep mechanism, it avoids key forgery and reuse. BLE connection and SN code secondary verification build a solid communication defense line and overcome the hidden dangers of open pairing and weak key security.

[0067] 3. This invention standardizes security constraints for user operation scenarios: the scanning function is activated by Bluetooth signal strength ≥-60dBm, limiting the user's operation to within 1 meter to prevent remote theft; cloud feedback information is valid for 10 minutes to reduce the risk of illegal use of information; the APP's precise abnormal guidance and abnormal handling module work together to improve the binding success rate and user experience, solving the problems of unrestrained scenarios and lack of protection.

[0068] 4. This invention enables controllable binding throughout the entire lifecycle, with a complete binding and unbinding process. Combined with dual data storage of "cloud + local" and full-process log traceability, it ensures that the binding relationship is uniquely verifiable. After unbinding, the device status is updated synchronously, balancing security and flexibility, and avoiding security issues such as permission leakage and vehicle theft. Attached Figure Description

[0069] Figure 1 This is a flowchart illustrating the operation of a Bluetooth binding method for an electric tricycle according to the present invention.

[0070] Figure 2 This is a schematic diagram of the architecture of an electric tricycle Bluetooth binding system according to the present invention. Detailed Implementation

[0071] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0072] Example 1

[0073] Please see Figures 1-2 This invention provides a technical solution: a Bluetooth binding method for an electric tricycle, comprising the following steps:

[0074] S1. Dual verification and information association on the production side;

[0075] S2, User-side scenario-based QR code scanning and Bluetooth address acquisition;

[0076] S3, multi-factor Bluetooth connectivity and key pairing;

[0077] S4. Vehicle binding confirmation and status synchronization.

[0078] In this embodiment, specifically: in S1, the specific operating steps are as follows:

[0079] A1. Collect hardware information: During the production process of electric tricycles, the Bluetooth hardware information of the electric tricycle alarm is collected through the Production Execution System (MES) or barcode scanning equipment (scanner).

[0080] A2. Secondary Scanning and Correlation Verification: Workers (using barcode scanning equipment) scan the vehicle chassis number nameplate barcode a second time. The Production Execution System (MES) compares the collected Bluetooth hardware information with the chassis number to see if they come from the same production station, thus forming mapping data.

[0081] A3. Verification result processing: If the workstation association is consistent, the mapping data is retained. If the workstation association is inconsistent (e.g., cross-workstation misscanning), the Production Execution System (MES) triggers an audible and visual alarm and suspends the production line until it is rescanned and confirmed, ensuring "one vehicle, one alarm, one mapping".

[0082] A4. Encrypted Storage and Access Control: Verified mapping data is stored in the cloud database using encryption algorithms. The cloud sets up triple access verification of "API key + IP whitelist + user account" and only allows authorized servers of the enterprise's official APP to access it.

[0083] In A1, Bluetooth hardware information includes the Bluetooth MAC address and device SN code (unique identification code), and the collected data is transmitted to the production execution system through the production line intranet;

[0084] In A2, the mapping data is the established three-dimensional mapping data of "Bluetooth MAC address-device SN code-vehicle frame number";

[0085] In A4, the encryption algorithm used is AES-256.

[0086] In this embodiment, specifically in S2, the specific operating steps are as follows:

[0087] B1. Account Registration and Access: Users complete registration through the electric tricycle's accompanying APP. After successful registration, they will be taken to the "Device Binding" page.

[0088] B2. QR code scanning function activation restrictions: When the APP enables the Bluetooth scanning function, it will detect the Bluetooth signal strength of the surrounding electric tricycle alarms in real time. The QR code scanning function will only be activated when the Bluetooth signal strength of the electric tricycle alarm is detected to be ≥-60dBm (determining that the user is within 1 meter of the vehicle).

[0089] B3. Binding Request Initiation: The user scans the QR code on the vehicle's VIN plate. After the APP parses the VIN, it automatically attaches the user's account and sends a Bluetooth information request to the cloud database.

[0090] B4. Cloud Verification and Information Feedback: The cloud database verifies the following in sequence: the validity of the APP's API key, whether the requesting IP is in the whitelist, the validity of the user account registration, and the binding status of the mobile phone number. After passing the triple verification, the Bluetooth MAC address is fed back to the APP using an encryption algorithm.

[0091] In B1, you need to bind your mobile phone number and complete SMS verification during registration to ensure the uniqueness of your account. The mobile phone number binding is generated in real time through the enterprise server.

[0092] In B2, if the APP detects a Bluetooth signal strength of <-60dBm, it will prompt the user to approach the vehicle and try again.

[0093] In B4, the encryption algorithm uses the RSA asymmetric encryption algorithm, and the validity period of the feedback information is 10 minutes.

[0094] In this embodiment, specifically in S3, the specific operating steps are as follows:

[0095] C1. BLE (Bluetooth Low Energy) Connection Initiation and Device SN Code Secondary Verification: Within the validity period of the information fed back by the APP in the cloud, the APP automatically initiates a BLE (Bluetooth Low Energy) connection request based on the obtained Bluetooth MAC address. During the connection process, "Bluetooth device SN code secondary verification" is used.

[0096] C2. Dynamic Key Generation: After the Bluetooth connection is established, the background uses an encryption algorithm to generate a dynamic key, and the key embeds the last 6 digits of the vehicle identification number and the generation timestamp accurate to the second.

[0097] C3. Alarm Triple Authentication and Anomaly Handling: After receiving the key, the alarm performs triple authentication:

[0098] Verify that the key length is 16 bits (AES-128 encryption algorithm standard).

[0099] Verify whether it contains the last 6 digits of the vehicle identification number (VIN).

[0100] Verify that the difference between the key generation time and the current time of the alarm is ≤1 minute (to prevent key reuse).

[0101] If all three verifications pass, pairing is complete; otherwise, pairing is rejected and the app is notified of the specific error type (such as key timeout, missing VIN fragment, etc.). After three consecutive verification failures, the alarm's Bluetooth module will go into sleep mode for 5 minutes.

[0102] In C1, the APP reads the device SN code in the alarm broadcast packet and compares it with the unique device identification code fed back by the cloud. If they match, the connection continues.

[0103] In C2, the encryption algorithm used is AES-128.

[0104] In C3, the time difference is the difference between the current time of the alarm and the key generation timestamp, accurate to the second.

[0105] In this embodiment, specifically in S4, the specific operating steps are as follows:

[0106] D1. Binding Confirmation Request Initiation: After successful Bluetooth pairing, the APP sends a binding confirmation request containing "Vehicle Identification Number - User Account - Bluetooth MAC Address" to the cloud database, along with a timestamp of the successful pairing.

[0107] D2. Cloud Recording and Status Marking: The cloud database stores the binding relationship in D1, generates a full-process log containing "binding time - verification node", and marks the vehicle as "bound" (and only allows the bound APP to initiate subsequent control commands).

[0108] D3. Result Feedback and Local Caching: The cloud returns a binding success command to the APP. The APP uses encrypted caching (key stored in the phone's security chip) to store the binding information locally and displays the "Binding Successful" interface, thus completing the Bluetooth binding of the entire vehicle.

[0109] In this embodiment, specifically, it also includes an unbinding step: the user initiates an unbinding request through the APP, the cloud deletes the binding record, marks the vehicle as unbound, sends an unbinding command (clears the local key) to the alarm, and the APP clears the local cache.

[0110] An electric tricycle Bluetooth binding system includes a production-side dual verification module, a user-side scenario-based interaction module, a triple verification module, a full-process recording module, and an exception handling module. The production-side dual verification module is used to collect, verify, and encrypt the mapping data. The production-side dual verification module includes a production execution system (MES), a barcode scanning device (scanner), and an encrypted storage unit.

[0111] Among them, the Production Execution System (MES) is used for information verification and process control at the production end, thereby laying a precise data foundation for end-to-end security binding;

[0112] Among them, the barcode scanning equipment is used for the connection of information collection and verification at the production end. Information collection includes hardware information collection and vehicle identification number collection.

[0113] The encrypted storage unit is an AES-256 encrypted storage unit, used to ensure the storage security and uniqueness of critical binding data on the production side, laying a secure and reliable data foundation for end-to-end Bluetooth binding.

[0114] In this embodiment, specifically: the user-side scenario-based interaction module is used to obtain the Bluetooth address and initiate a connection in a scenario-based manner. The user-side scenario-based interaction module includes a Bluetooth signal strength detection unit, a QR code parsing unit, a BLE communication unit, and a multi-factor key generation unit.

[0115] Among them, the Bluetooth signal strength detection unit can realize the security verification of user terminal binding through spatial scene restrictions, thus avoiding the risk of remote theft.

[0116] The QR code parsing unit connects the user's scanning operation with the cloud information request, providing accurate vehicle identification data for Bluetooth binding, and enhancing security with scenario-based verification.

[0117] Among them, the BLE communication unit enables secure, efficient, and low-power Bluetooth connection and key data transmission between the APP and the electric tricycle alarm, laying the communication foundation for multi-factor key pairing;

[0118] Among them, the multi-factor key generation unit generates dynamic keys with high security, uniqueness and timeliness, providing key verification basis for Bluetooth pairing and avoiding the risk of key forgery and reuse.

[0119] In this embodiment, specifically: a triple verification module (API key + IP whitelist + user account verification) is deployed in the cloud and an alarm (key length + VIN fragment + time difference verification) is used for end-to-end security verification;

[0120] The full-process recording module is used to store binding records and mark vehicle binding status. The full-process recording module includes a binding log storage unit, a vehicle status marking unit, and a local encrypted cache unit.

[0121] Among them, the binding log storage unit is used to store the complete binding relationship of "Vehicle Identification Number - User Account - Bluetooth MAC Address", generate and retain the full-process log containing "Binding Time - Verification Node", and provide accurate data basis for the traceability and verification of the entire Bluetooth binding link;

[0122] Simultaneously, in conjunction with the full-process recording module and the vehicle status marking unit, the system can record the associated status of the vehicle as "bound" or "unbound," ensuring the integrity and traceability of the bound data and providing data support for subsequent unbinding operations and troubleshooting of abnormal scenarios (such as tracing the source of binding failures).

[0123] Among them, the vehicle status marking unit is used to accurately mark the core status of the vehicle as "bound" or "unbound", forming a clear identifier of the vehicle binding status and providing basic support for the permission control and process connection of the entire Bluetooth binding process.

[0124] It should be further explained that after successful binding, the vehicle will be marked as "bound" as the basis for determining the permission to only allow the bound APP to initiate control commands, thus preventing unauthorized operation by unauthorized devices.

[0125] When unbinding, the cloud binding record will be deleted and updated to "unbound" status to ensure that the vehicle can be legally bound again. At the same time, the status flag of this unit is linked with the binding log storage unit, so that the vehicle binding status can be queried and traced in real time, ensuring the uniqueness of the binding relationship and the compliance of the operation.

[0126] Among them, the local encrypted cache unit securely stores key Bluetooth binding information locally in the APP, forming a dual data protection of "cloud + local", supporting the efficiency and security of operations after binding;

[0127] It needs to be further explained that it will encrypt and cache core data such as the binding relationship between "Vehicle Identification Number - User Account - Bluetooth MAC Address" and the dynamic key generated during pairing into the phone's security chip, thereby eliminating the risk of local data being stolen or tampered with.

[0128] Meanwhile, it provides local verification for subsequent control commands from the APP to the vehicle, eliminating the need to rely on cloud queries every time, greatly improving command response speed and optimizing user experience;

[0129] Furthermore, even in scenarios involving network outages or poor performance, users can quickly check the vehicle binding status, ensuring uninterrupted use. This complements cloud storage and further enhances the security and accessibility of bound data.

[0130] In this embodiment, specifically: the exception handling module is used to handle abnormal scenarios such as production mismatch, verification failure, and binding timeout. The exception handling module includes an MES alarm unit, an alarm sleep unit, and an APP retry guidance unit.

[0131] Among them, the MES alarm unit is used to respond promptly to the binding data mismatch problem in the production process, ensuring the accuracy of "one vehicle, one alarm, one mapping", and building a solid data security defense line for the production end for the whole-link Bluetooth binding.

[0132] It needs to be further explained that in the dual verification process at the production end (A2-A3 in step S1), when the Manufacturing Execution System (MES) finds that the Bluetooth hardware information and the vehicle identification number do not come from the same production station (such as cross-station misscanning or other inconsistent association scenarios), the MES alarm unit will immediately trigger an audible and visual alarm and simultaneously suspend the production line operation to prevent the retention of mismatched mapping data through forced intervention.

[0133] The production line only resumes operation after the workers rescan and confirm to eliminate the anomaly, thus preventing data errors such as "one vehicle with multiple mappings" and "multiple vehicles with one mapping" from the source. This ensures that the three-dimensional mapping data of "Bluetooth MAC address-device SN code-vehicle frame number" collected at the production end is unique and accurate, providing a reliable data foundation for subsequent user-end binding and end-to-end security verification.

[0134] Among them, the alarm sleep unit is used to deal with malicious verification or frequent failures during the Bluetooth pairing process. By forcing the sleep mode to block illegal operations, it ensures the security of Bluetooth binding of electric tricycles and the stable operation of the alarm.

[0135] It needs to be further explained that in the multi-factor Bluetooth pairing process on the user side (C3 in step S3), when the alarm fails to perform triple verification of the dynamic key (length, VIN fragment, time difference) three times in a row, the alarm sleep unit will immediately trigger the alarm Bluetooth module to enter a 5-minute sleep state. This design can effectively resist attacks launched by malicious hackers through repeated attempts to obtain fake keys and make illegal requests, and prevent the alarm Bluetooth module from malfunctioning due to frequent receipt of invalid requests. At the same time, it temporarily shuts down the Bluetooth communication channel at the physical level, eliminates repeated illegal pairing attempts in a short period of time, builds the last line of defense for the security verification of Bluetooth binding, and protects the binding rights of legitimate users and the safety of vehicle use.

[0136] The APP retry guidance unit is used to provide accurate prompts and clear retry instructions for various abnormal scenarios in the entire Bluetooth binding process, reducing user operation costs, ensuring the smooth progress of the binding process, and improving user experience and binding success rate.

[0137] Example 2

[0138] Production end information entry and verification process

[0139] The manufacturing company adopts the following operations:

[0140] 1. When the alarm is assembled into the vehicle, the worker uses a barcode scanner to scan the barcode on the surface of the alarm (including MAC address: AA:BB:CC:DD:EE:FF, SN code:SN202506001), and the data is transmitted to the MES or barcode system;

[0141] 2. Workers scan the vehicle chassis number nameplate barcode (chassis number: LZWADAGA0NB123456) at the same workstation (A05). The MES system confirms that the "alarm information - chassis number" all come from workstation A05 and establishes a three-dimensional mapping data of "chassis number: LZWADAGA0NB123456 - Bluetooth MAC: AA: BB: CC: DD: EE: FF - SN code: SN202506001".

[0142] 3. The 3D mapping data is uploaded to the Alibaba Cloud RDS database using the AES-256 encryption algorithm. The database is configured to allow access only from the enterprise APP server IP via the API key (APPKey2025TRI).

[0143] Example 3

[0144] User-side scenario-based binding operation

[0145] After purchasing an electric tricycle, users can complete the binding process by following these steps:

[0146] 1. Download the company's official APP, complete the mobile phone number registration (138XXXX1234), and enter the "Device Binding" page;

[0147] 2. The APP enables Bluetooth scanning and detects that the Bluetooth signal strength of the alarm is -52dBm (≥-60dBm), thus activating the scanning function; the user scans the QR code on the vehicle identification number plate, and the APP parses it to obtain the vehicle identification number "LZWADAGA0NB123456";

[0148] 3. After the APP sends a request to the cloud and the cloud verifies the request, it returns the MAC address "AA:BB:CC:DD:EE:FF" using RSA encryption.

[0149] 4. The APP reads the SN code "SN202506001" from the alarm broadcast packet, which is consistent with the cloud feedback, and initiates a BLE connection; after the connection is successful, it generates the key "8a7f6b5c4d3e2f1a" (including the last 6 digits of the vehicle identification number "123456", generated at 10:12) and sends it to the alarm.

[0150] 5. Alarm verification: ① Key length 16 bits; ② Contains the "123456" segment. Verification passes, and feedback "Pairing successful" is provided.

[0151] 6. The APP sends a binding confirmation request to the cloud. The cloud records "User 138XXXX1234-Vehicle VIN LZWADAGA0NB123456-MACAA:BB:CC:DD:EE:FF-Binding Time 10:13" and marks the vehicle as "Bound". The APP displays a binding success interface and caches the information to the phone's security chip.

[0152] Example 4

[0153] Exception handling and unbinding process

[0154] 1. If the Bluetooth signal strength is -75dBm (< -60dBm) when the user scans the code, the APP will prompt "Please move within 1 meter of the vehicle to try again" and the scanning function will not be activated;

[0155] 2. If the key verification fails 3 times, the alarm's Bluetooth will go into sleep mode for 5 minutes, and the APP will display the message "Too many verification failures, please try again in 5 minutes";

[0156] 3. Unbinding Operation: On the "My Devices" page of the APP, the user clicks "Unbind". After completing the secondary verification of the account verification code, the APP sends an unbinding request to the cloud. The cloud deletes the binding record, marks the vehicle as "unbound", and sends an unbinding command (clears the local key) to the alarm. The APP clears the local cache and prompts "Unbound, you can rebind".

[0157] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A Bluetooth binding method for an electric tricycle, characterized in that, Includes the following steps: S1. Dual verification and information association on the production side; S2, User-side scenario-based QR code scanning and Bluetooth address acquisition; S3, multi-factor Bluetooth connectivity and key pairing; S4. Vehicle binding confirmation and status synchronization.

2. The Bluetooth binding method for an electric tricycle according to claim 1, characterized in that: In S1, the specific steps are as follows: A1. Collect hardware information: During the production process of electric tricycles, the Bluetooth hardware information of the electric tricycle alarm is collected through the production execution system or barcode scanning equipment. A2. Secondary Scan and Correlation Verification: Workers scan the vehicle chassis number nameplate barcode a second time. The production execution system compares the collected Bluetooth hardware information with the chassis number to see if they come from the same production station, thus forming mapping data. A3. Verification result processing: If the workstation association is consistent, the mapping data is retained; if the workstation association is inconsistent, the production execution system triggers an audible and visual alarm and suspends the production line until it is re-scanned and confirmed. A4. Encrypted Storage and Access Control: Verified mapping data is stored in a cloud database using an encryption algorithm. The cloud is equipped with multiple access verifications and only authorized servers of the company's official APP are allowed to access it. In A1, Bluetooth hardware information includes the Bluetooth MAC address and device serial number, and the collected data is transmitted to the production execution system via the production line intranet; In A2, the mapping data is the established three-dimensional mapping data of "Bluetooth MAC address-device SN code-vehicle chassis number"; In A4, the encryption algorithm used is AES-256.

3. The Bluetooth binding method for an electric tricycle according to claim 2, characterized in that: In S2, the specific steps are as follows: B1. Account Registration and Access: Users complete registration through the electric tricycle's accompanying APP. After successful registration, they will be taken to the "Device Binding" page. B2. QR code scanning function activation restrictions: When the APP enables the Bluetooth scanning function, it will detect the Bluetooth signal strength of the surrounding electric tricycle alarms in real time. When the Bluetooth signal strength of the electric tricycle alarm is detected to be ≥-60dBm, the QR code scanning function will be activated. B3. Binding Request Initiation: The user scans the QR code on the vehicle's VIN plate. After the APP parses the VIN, it automatically attaches the user's account and sends a Bluetooth information request to the cloud database. B4. Cloud Verification and Information Feedback: The cloud database verifies the following in sequence: the validity of the APP's API key, whether the requesting IP is in the whitelist, the validity of the user account registration, and the binding status of the mobile phone number. After passing the triple verification, the Bluetooth MAC address is fed back to the APP using an encryption algorithm. In B1, you need to bind your mobile phone number and complete SMS verification during registration to ensure the uniqueness of your account. The mobile phone number binding is generated in real time through the enterprise server. In B2, if the APP detects a Bluetooth signal strength of <-60dBm, it will prompt the user to approach the vehicle and try again. In B4, the encryption algorithm uses the RSA asymmetric encryption algorithm, and the validity period of the feedback information is 10 minutes.

4. The Bluetooth binding method for an electric tricycle according to claim 3, characterized in that: In S3, the specific steps are as follows: C1. BLE Connection Initiation and Device SN Code Secondary Verification: Within the validity period of the information fed back by the APP in the cloud, the APP automatically initiates a BLE connection request based on the obtained Bluetooth MAC address, and uses "Bluetooth device SN code secondary verification" during the connection process. C2. Dynamic Key Generation: After the Bluetooth connection is established, the background uses an encryption algorithm to generate a dynamic key, and the key embeds the last 6 digits of the vehicle identification number and the generation timestamp accurate to the second. C3. Alarm Triple Authentication and Anomaly Handling: After receiving the key, the alarm performs triple authentication: Verify that the key length is 16 bits; Verify whether it contains the last 6 digits of the vehicle identification number (VIN). Verify that the difference between the key generation time and the current time of the alarm is ≤1 minute; If the triple verification is successful, pairing is complete; otherwise, pairing is rejected and the specific error type is reported to the APP. After three consecutive verification failures, the alarm's Bluetooth module will go into sleep mode for 5 minutes. In C1, the APP reads the device SN code in the alarm broadcast packet and compares it with the unique device identification code fed back by the cloud. If they match, the connection continues. In C2, the encryption algorithm used is AES-128. In C3, the time difference is the difference between the current time of the alarm and the key generation timestamp, accurate to the second.

5. The Bluetooth binding method for an electric tricycle according to claim 1, characterized in that: In S4, the specific steps are as follows: D1. Binding Confirmation Request Initiation: After successful Bluetooth pairing, the APP sends a binding confirmation request containing "Vehicle Identification Number - User Account - Bluetooth MAC Address" to the cloud database, along with a timestamp of the successful pairing. D2. Cloud Recording and Status Marking: The cloud database stores the binding relationships recorded in D1, generates a full-process log containing "binding time - verification node", and marks the vehicle as "bound" in the status. D3. Result Feedback and Local Caching: The cloud returns a binding success command to the APP. The APP uses encrypted caching of binding information locally and displays a "Binding Successful" interface, thus completing the Bluetooth binding of the entire vehicle.

6. The Bluetooth binding method for an electric tricycle according to claim 1, characterized in that: It also includes an unbinding step: the user initiates an unbinding request through the APP, the cloud deletes the binding record, marks the vehicle as unbound, sends an unbinding command to the alarm, and the APP clears its local cache.

7. An electric tricycle Bluetooth binding system, comprising a production-side dual verification module, a user-side scenario-based interaction module, a triple verification module, a full-process recording module, and an exception handling module, characterized in that: The production-side dual verification module is used to collect, verify and encrypt the mapping data. The production-side dual verification module includes a production execution system, a barcode scanning device and an encrypted storage unit. The production execution system is used for information verification and process control at the production end, thereby laying a precise data foundation for end-to-end security binding. The barcode scanning device is used for production-end information collection and verification, and the information collection includes hardware information collection and vehicle identification number (VIN) collection. The encrypted storage unit is an AES-256 encrypted storage unit, used to ensure the storage security and uniqueness of key binding data on the production side, laying a secure and reliable data foundation for end-to-end Bluetooth binding.

8. The Bluetooth binding system for an electric tricycle according to claim 7, characterized in that: The user-side scenario-based interaction module is used to obtain the Bluetooth address and initiate a connection in a scenario-based manner. The user-side scenario-based interaction module includes a Bluetooth signal strength detection unit, a QR code parsing unit, a BLE communication unit, and a multi-factor key generation unit. The Bluetooth signal strength detection unit achieves security verification of user terminal binding through spatial scene restrictions; The QR code parsing unit is used to connect the user's scanning operation with the cloud information request, providing accurate vehicle identification data for Bluetooth binding, and strengthening security with scenario-based verification. The BLE communication unit enables secure, efficient, and low-power Bluetooth connection and key data transmission between the APP and the electric tricycle alarm, laying the communication foundation for multi-factor key pairing. The multi-factor key generation unit generates a dynamic key that is secure, unique, and timely, providing a verification basis for Bluetooth pairing.

9. The Bluetooth binding system for an electric tricycle according to claim 8, characterized in that: The triple verification module is deployed in the cloud and on the alarm device for end-to-end security verification; The full-process recording module is used to store binding records and mark vehicle binding status. The full-process recording module includes a binding log storage unit, a vehicle status marking unit, and a local encrypted cache unit. The binding log storage unit is used to store the complete binding relationship of "Vehicle Identification Number - User Account - Bluetooth MAC Address", generate and retain a full-process log containing "Binding Time - Verification Node", and provide data basis for the traceability and verification of the entire Bluetooth binding link; The vehicle status marking unit is used to accurately mark the vehicle's "bound" or "unbound" status, forming a clear identifier of the vehicle's binding status, and providing basic support for the permission control and process connection of the entire Bluetooth binding process. The local encrypted cache unit securely stores Bluetooth binding information locally within the APP, forming a dual data protection of "cloud + local" to support efficient and secure operation after binding.

10. The Bluetooth binding system for an electric tricycle according to claim 9, characterized in that: The exception handling module is used to handle abnormal scenarios such as production mismatch, verification failure and binding timeout. The exception handling module includes an MES alarm unit, an alarm sleep unit and an APP retry guidance unit. The MES alarm unit is used to respond promptly to data mismatch issues during the production process, ensuring the accuracy of "one vehicle, one alarm, one mapping" and building a solid data security defense line for the entire Bluetooth binding process. The alarm sleep unit is used to deal with malicious verification or frequent failures during the Bluetooth pairing process. By forcing the device into sleep mode, it blocks illegal operations and ensures the security of the Bluetooth binding of the electric tricycle and the stable operation of the alarm. The APP retry guidance unit is used to provide accurate prompts and clear retry instructions for various abnormal scenarios in the entire Bluetooth binding process, reduce user operation costs, ensure the smooth progress of the binding process, and improve user experience and binding success rate.

Images