A bluetooth module device id management method and device

Abstract

This invention discloses a method and apparatus for managing device IDs in a Bluetooth module. The method includes: developing activation software to obtain a device ID from a cloud platform and transmitting the device ID to the Bluetooth module; verifying the validity of the device ID through the Bluetooth module and writing the device ID into the eFuse area, and sending a confirmation message of successful device ID writing back to the activation software; and the activation software replying to the cloud platform to notify that the device ID writing was successful. The advantages of this invention are: the device ID is controlled by the brand owner, making it difficult to copy, and the number of device IDs can be flexibly allocated.

Description

Technical Field

[0001] This invention relates to the field of Bluetooth device manufacturing technology, and more specifically, to a method and apparatus for managing the device ID of a Bluetooth module. Background Technology

[0002] When a brand designer commissions a hardware supplier to produce Bluetooth devices, the brand designer typically provides the device ID (DID) to the supplier, who then burns the DID into the Bluetooth module. This is usually done by sending a file containing a list of device IDs online. Once the supplier receives the file, they read the device IDs from the file and burn them into the module.

[0003] This technology has the following drawbacks:

[0004] 1. Device IDs are easily leaked: By transmitting device IDs via files, suppliers have the right to open and view the file contents. This makes it easy for relevant personnel of the supplier to obtain the device IDs and thus counterfeit the devices.

[0005] 2. The number of device IDs cannot be flexibly expanded or recycled: When brand designers entrust hardware suppliers to produce Bluetooth devices, the device IDs are given to the suppliers in the form of files. If the brand needs to temporarily increase production, it needs to resend the device ID files. If it needs to reduce production, the device IDs cannot be recycled immediately, which is very inflexible. Summary of the Invention

[0006] This invention provides a method and apparatus for managing device IDs of Bluetooth modules, solving the problems of easy leakage of device IDs and the inability to flexibly expand or recycle the number of device IDs in the prior art.

[0007] To address the aforementioned problems, this invention provides a method for managing the device ID of a Bluetooth module, comprising:

[0008] Develop activation software to obtain the device ID from the cloud platform and transmit the device ID to the Bluetooth module;

[0009] The Bluetooth module verifies the validity of the device ID and writes the device ID into the efuse area, and sends a confirmation message of successful device ID writing to the activation software.

[0010] The activation software replies to the cloud platform to notify that the device ID was successfully written.

[0011] Also includes:

[0012] Build a cloud platform to generate device IDs.

[0013] The process of building a cloud platform to generate device IDs includes:

[0014] The cloud platform sets up a user table to record the user's username, password, maximum number of modules, and the number of modules currently produced. This allows users to log in to the cloud platform using their username and password. The cloud platform then verifies the username and password to determine if the user is authorized to perform subsequent operations.

[0015] The device information table is set up through the cloud platform to record the device ID and MAC address. After the user logs in successfully, the MAC address is read from the Bluetooth module that needs to be activated and uploaded to the cloud platform. The device ID is obtained by looking up the MAC address.

[0016] Verify whether the number of modules currently produced is greater than or equal to the maximum number of modules. If so, do not allow the application for a device ID.

[0017] The step of writing activation software to obtain the device ID from the cloud platform and transmitting the device ID to the Bluetooth module includes:

[0018] The software's login window receives the username and password entered by the user.

[0019] Send the username and password to the cloud platform via HTTPS to enable the user to log in to the cloud platform;

[0020] Check if the serial port of the activation software is connected to the Bluetooth module to read the MAC address from the Bluetooth module to be activated, and upload the MAC address to the cloud platform. The device ID is obtained by looking up the MAC address.

[0021] After receiving the device ID from the cloud platform, the activation software sends the device ID to the Bluetooth module via a serial port and sends activation and write commands to the Bluetooth module.

[0022] The Bluetooth module verifies the validity of the device ID and writes the device ID into the efuse area. It then sends a confirmation message of successful device ID writing to the activation software, including:

[0023] The Bluetooth module checks if a device ID exists in the efuse area to determine whether activation is required.

[0024] After receiving the device ID, the Bluetooth module performs CRC data verification on the device ID;

[0025] Write the device ID to the efuse area and read it again from the efuse area to determine whether the storage was successful;

[0026] If the device ID is successfully written, a confirmation message indicating successful activation is sent to the activation software; otherwise, a message indicating activation failure is sent to the activation software.

[0027] The step of replying to the cloud platform via the activation software to notify that the device ID was successfully written also includes:

[0028] If the cloud platform receives a message from the activation software indicating a successful write of the device ID, it increments the number of modules already produced by 1.

[0029] On the one hand, a device ID management device for a Bluetooth module is provided, comprising:

[0030] The software development module is used to develop activation software to obtain the device ID from the cloud platform and transmit the device ID to the Bluetooth module.

[0031] The module writing module is used to verify the validity of the device ID through the Bluetooth module and write the device ID into the efuse area, and to send back a confirmation message of successful device ID writing to the activation software;

[0032] The notification module is used to reply to the cloud platform through the activation software to notify that the device ID was successfully written.

[0033] It also includes a setup module for building a cloud platform to generate device IDs, the setup module comprising:

[0034] The user table settings submodule is used to set up the user table through the cloud platform to record the user's username, password, maximum number of modules, and number of modules currently produced. This allows users to log in to the cloud platform using their username and password, and the cloud platform verifies the username and password to determine if the user can perform subsequent operations.

[0035] The device information setting submodule is used to set the device information table through the cloud platform to record the device ID and MAC address. After the user logs in successfully, the MAC address is read from the Bluetooth module that needs to be activated and uploaded to the cloud platform. The device ID is obtained by looking up the MAC address.

[0036] The verification submodule is used to verify whether the number of modules currently produced is greater than or equal to the maximum number of modules. If so, the application for a device ID is not allowed.

[0037] The software programming module includes a receiving submodule, a login submodule, a serial port checking submodule, and an instruction sending submodule;

[0038] The receiving submodule is used to receive the username and password entered by the user through the login window of the activated software;

[0039] The login submodule is used to send a request for the username and password to the cloud platform via the HTTPS protocol so that the user can log in to the cloud platform;

[0040] The serial port inspection submodule is used to check whether the serial port of the activation software is connected to the Bluetooth module in order to read the MAC address from the Bluetooth module to be activated, and upload the MAC address to the cloud platform, and obtain the device ID by looking up the MAC address;

[0041] The instruction sending submodule is used to send the device ID to the Bluetooth module via serial port after the activation software receives the device ID from the cloud platform, and to send activation and write instructions to the Bluetooth module.

[0042] The module writing module includes an efuse check submodule, a CRC check submodule, an ID writing submodule, and a reply submodule;

[0043] The efuse check submodule is used to enable the Bluetooth module to check whether a device ID exists in the efuse area to determine whether activation is required.

[0044] The CRC verification submodule is used to perform CRC data verification on the device ID after the Bluetooth module receives the device ID;

[0045] The ID writing submodule is used to write the device ID into the efuse area and reread it from the efuse area to determine whether the storage was successful.

[0046] The reply submodule is used to reply to the activation software with a confirmation message of successful activation if the device ID is successfully written, and to reply to the activation software with a message of activation failure otherwise.

[0047] The notification module is also used to increment the number of modules currently produced by 1 if the cloud platform receives a successful write device ID message returned by the activation software.

[0048] On the one hand, a computer-readable storage medium is provided, wherein a plurality of instructions are stored in the storage medium, the instructions being adapted to be loaded by a processor to execute a device ID management method for a Bluetooth module as described above.

[0049] The beneficial effects of this invention are as follows: the device ID is obtained from a cloud platform provided by the brand owner, and then written to the Bluetooth module EFSUE via activation software. The entire communication process is secure. Due to the characteristics of the EFSUE area, the device ID is unreadable after being written to the module, thus ensuring secure management of the entire device ID and making it difficult to copy. Each activation by the supplier retrieves the device ID from the cloud platform, and each retrieval can be controlled via a calculator. This allows the supplier to flexibly allocate the number of devices produced by the brand. Attached Figure Description

[0050] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0051] Figure 1 This is a flowchart of a device ID management method for a Bluetooth module provided in an embodiment of the present invention. Detailed Implementation

[0052] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0053] In the description of this invention, it should be understood that the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer," etc., indicating orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more features. In the description of this invention, "a plurality of" means two or more, unless otherwise explicitly specified.

[0054] In this invention, the term "exemplary" is used to mean "serving as an example, illustration, or description." Any embodiment described as "exemplary" in this invention is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to make and use the invention. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that the invention can be made without using these specific details. In other instances, well-known structures and processes will not be described in detail to avoid obscuring the description of the invention with unnecessary detail. Therefore, the invention is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed herein.

[0055] See Figure 1 , Figure 1 This is a flowchart of a device ID management method for a Bluetooth module according to an embodiment of the present invention. The device ID management method for the Bluetooth module includes steps S1-S4:

[0056] S1. Develop activation software to obtain the device ID from the cloud platform and transmit the device ID to the Bluetooth module; Step S1 includes steps S11-S14:

[0057] S11. Receive the username and password entered by the user through the login window of the activation software.

[0058] In this embodiment, activation software is developed that can access a cloud platform. Through the login window, users enter their username and password, click the login button, and send the username and password to the platform via HTTPS. The platform verifies the credentials and returns the login result. If successful, the user proceeds to the next step; otherwise, they log in again.

[0059] S12. Send the username and password to the cloud platform via HTTPS protocol to enable the user to log in to the cloud platform.

[0060] In this embodiment, the device ID is obtained from the cloud platform via HTTPS and then sent to the Bluetooth module. Because the platform access uses the secure HTTPS protocol, the entire process, from obtaining the device ID to writing it to the module, is completed through activation software, ensuring strong communication security. The device ID is not easily cracked or obtained throughout the entire process.

[0061] S13. Check whether the serial port of the activation software is connected to the Bluetooth module to read the MAC address from the Bluetooth module to be activated, and upload the MAC address to the cloud platform. The device ID is obtained by searching the MAC address.

[0062] In this embodiment, after successful login, it checks whether the serial port of the currently connected module is open, obtains the MAC address from the module to be activated, and uploads the MAC address to the platform to obtain the device ID.

[0063] S14. After receiving the device ID from the cloud platform, the activation software sends the device ID to the Bluetooth module via the serial port and sends activation and write commands to the Bluetooth module.

[0064] In this embodiment, upon receiving the device ID from the platform, the module sends the device ID to the module via serial port and sends an activation write command to the module. The module then performs the device ID write operation and awaits the module's processing result. Once the module completes processing, it returns a result: if successful, it sends an activation success message to the platform; otherwise, it returns an activation failure message.

[0065] S2. Verify the validity of the device ID through the Bluetooth module and write the device ID into the efuse area, and send a confirmation message of successful device ID writing to the activation software; Step S2 includes steps S21-S24:

[0066] S21. The Bluetooth module checks if a device ID exists in the efuse area to determine whether activation is required.

[0067] In this embodiment, the Bluetooth module and the activation software are connected via a serial port. After receiving a request to obtain the MAC address, the Bluetooth module checks whether the device ID exists in the eFuse area. If it exists, it informs that activation is not required. If it does not exist, it reads the MAC address and returns it to the activation software.

[0068] S22. After receiving the device ID, the Bluetooth module performs CRC data verification on the device ID.

[0069] In this embodiment, after receiving the MAC address, the activation software exchanges it for a device ID from the platform and sends it to the Bluetooth module via a serial port. Upon receiving the device ID, the Bluetooth module first performs a CRC data verification.

[0070] S23. Write the device ID into the efuse area and reread it from the efuse area to determine whether the storage was successful.

[0071] In this embodiment, after receiving the device ID from the activation software, the module first verifies the ID's validity using a CRC check, and then writes it to the efuse area. Since the efuse area is a one-time storage area and cannot be read, all device IDs cannot be copied after being written. The module then writes the device ID back to the efuse area and rereads it to check if the storage was successful.

[0072] S24. If the device ID is successfully written, send a confirmation message of successful activation to the activation software; otherwise, send a message of activation failure to the activation software.

[0073] In this embodiment, if the device ID is successfully written, the activation is successful; otherwise, the activation fails. After all operations are completed, the module is reset.

[0074] S3. The activation software replies to the cloud platform to notify that the device ID has been successfully written. If the cloud platform receives the successful device ID writing message from the activation software, it increments the number of modules currently produced by 1.

[0075] In this embodiment, after the module successfully writes the device ID, it needs to send a confirmation to the activation software. The activation software then replies to the platform that the device ID was successfully written. At this time, the platform will decrement the remaining module inventory of that manufacturer by 1.

[0076] S4. Set up a cloud platform to generate device IDs. Step S4 includes steps S41-S43:

[0077] S41. Set up a user table through the cloud platform to record the user's username, password, maximum number of modules, and the number of modules currently produced, so that the user can log in to the cloud platform with the username and password, and the cloud platform verifies the username and password to determine whether the user can perform subsequent operations.

[0078] In this embodiment, a cloud platform is built. The cloud platform assigns a login account to each manufacturer and specifies the number of device IDs each account can obtain. It also provides interfaces for manufacturer login and device ID retrieval. Specifically, the cloud platform designs a UserTable to record the manufacturer's username (userName), password (password), maximum number of modules (maxCount), and the number of modules currently in production (curCount). Manufacturers log in to the cloud platform using their username (userName) and password (password). The platform verifies the user and password. If the verification passes, the next step is performed; otherwise, an "illegal user" message is displayed.

[0079] S42. Set up a device information table through the cloud platform to record the device ID and MAC address. After the user logs in successfully, read the MAC address from the Bluetooth module that needs to be activated, upload the MAC address to the cloud platform, and obtain the device ID by looking up the MAC address.

[0080] In this embodiment, the cloud platform designs a device information table (deviceTable) to record device IDs, MAC addresses, etc. After a user successfully logs in, the MAC address is read from the module that needs to be activated and uploaded to the platform in exchange for a device ID. Upon receiving the request, the cloud platform checks if the MAC address exists in the deviceTable. If it does not exist, the corresponding device ID is generated according to the rules, and the MAC address and device ID are stored in the deviceTable. If the MAC address already exists, it means that a device ID has already been requested for that MAC address, and a "duplicate request" message is displayed.

[0081] S43. Verify whether the number of modules currently produced is greater than or equal to the maximum number of modules. If so, do not allow the application for a device ID.

[0082] In this embodiment, manufacturers can call the device ID retrieval interface after logging in. Each successful call decrements the manufacturer's remaining module count by 1. To prevent manufacturers from producing more devices than allowed, each time a device ID is requested, the number of modules already produced (curCount) is checked against the module count (maxCount). If curCount is greater than or equal to maxCount, the request is denied, and the message "Production quantity exceeded" is displayed. After each successful request, the system waits for the activation software's processing result. If the activation software returns success, curCount is incremented by 1 and persisted to the UserTable. To temporarily adjust the manufacturer's module production quantity, simply adjust the maxCount value on the platform, thus achieving flexible configuration of the manufacturer's module production quantity.

[0083] In summary, the device ID management method for Bluetooth modules provided by this invention solves the following problems:

[0084] I. Solving the problems of device IDs being difficult to leak and devices being difficult to imitate:

[0085] Brands provide activation software to suppliers. The activation software requires an account and password to log in and can read the device ID online and write the device ID into the efuse area of ​​the Bluetooth module. For the supplier's activation software, it is a black box. It cannot see the device ID, nor can it read it from the efuse area of ​​the Bluetooth module.

[0086] II. Solving the problem of the inflexible expansion or recycling of Bluetooth module devices:

[0087] The activation software is connected to the cloud platform. Suppliers need to log in each time they use it. Brands can set the number of device IDs that the supplier account can read on the cloud platform. Each time a device ID is read, the number of devices is reduced by 1. If the maximum production quantity is exceeded, it will not be allowed to continue to be called. This makes it easy to expand or reclaim the number of supplier production devices.

[0088] The present invention also provides a device ID management device for a Bluetooth module, comprising:

[0089] The software development module is used to develop activation software to obtain the device ID from the cloud platform and transmit the device ID to the Bluetooth module.

[0090] The module writing module is used to verify the validity of the device ID through the Bluetooth module and write the device ID into the efuse area, and to send back a confirmation message of successful device ID writing to the activation software;

[0091] The notification module is used to reply to the cloud platform through the activation software to notify that the device ID was successfully written.

[0092] It also includes a setup module for building a cloud platform to generate device IDs, the setup module comprising:

[0093] The user table settings submodule is used to set up the user table through the cloud platform to record the user's username, password, maximum number of modules, and number of modules currently produced. This allows users to log in to the cloud platform using their username and password, and the cloud platform verifies the username and password to determine if the user can perform subsequent operations.

[0094] The device information setting submodule is used to set the device information table through the cloud platform to record the device ID and MAC address. After the user logs in successfully, the MAC address is read from the Bluetooth module that needs to be activated and uploaded to the cloud platform. The device ID is obtained by looking up the MAC address.

[0095] The verification submodule is used to verify whether the number of modules currently produced is greater than or equal to the maximum number of modules. If so, the application for a device ID is not allowed.

[0096] The software programming module includes a receiving submodule, a login submodule, a serial port checking submodule, and an instruction sending submodule;

[0097] The receiving submodule is used to receive the username and password entered by the user through the login window of the activated software;

[0098] The login submodule is used to send a request for the username and password to the cloud platform via the HTTPS protocol so that the user can log in to the cloud platform;

[0099] The serial port inspection submodule is used to check whether the serial port of the activation software is connected to the Bluetooth module in order to read the MAC address from the Bluetooth module to be activated, and upload the MAC address to the cloud platform, and obtain the device ID by looking up the MAC address;

[0100] The instruction sending submodule is used to send the device ID to the Bluetooth module via serial port after the activation software receives the device ID from the cloud platform, and to send activation and write instructions to the Bluetooth module.

[0101] The module writing module includes an efuse check submodule, a CRC check submodule, an ID writing submodule, and a reply submodule;

[0102] The efuse check submodule is used to enable the Bluetooth module to check whether a device ID exists in the efuse area to determine whether activation is required.

[0103] The CRC verification submodule is used to perform CRC data verification on the device ID after the Bluetooth module receives the device ID;

[0104] The ID writing submodule is used to write the device ID into the efuse area and reread it from the efuse area to determine whether the storage was successful.

[0105] The reply submodule is used to reply to the activation software with a confirmation message of successful activation if the device ID is successfully written, and to reply to the activation software with a message of activation failure otherwise.

[0106] The notification module is also used to increment the number of modules currently produced by 1 if the cloud platform receives a successful write device ID message returned by the activation software.

[0107] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor. Therefore, embodiments of the present invention provide a storage medium storing multiple instructions that can be loaded by a processor to execute the steps in any of the Bluetooth module device ID management methods provided in the embodiments of the present invention.

[0108] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0109] Since the instructions stored in the storage medium can execute the steps in any of the Bluetooth module device ID management methods provided in the embodiments of the present invention, the beneficial effects that any of the Bluetooth module device ID management methods provided in the embodiments of the present invention can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0110] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for managing the device ID of a Bluetooth module, characterized in that, include: Develop activation software to obtain the device ID from the cloud platform and transmit the device ID to the Bluetooth module; The Bluetooth module verifies the validity of the device ID and writes the device ID into the efuse area, and sends a confirmation message of successful device ID writing to the activation software. The activation software replies to the cloud platform to notify that the device ID was successfully written. The method for managing the device ID of the Bluetooth module also includes: building a cloud platform to generate device IDs; The process of building a cloud platform to generate device IDs includes: The cloud platform sets up a user table to record the user's username, password, maximum number of modules, and the number of modules currently produced. This allows users to log in to the cloud platform using their username and password. The cloud platform then verifies the username and password to determine if the user is authorized to perform subsequent operations. The device information table is set up through the cloud platform to record the device ID and MAC address. After the user logs in successfully, the MAC address is read from the Bluetooth module that needs to be activated and uploaded to the cloud platform. The device ID is obtained by looking up the MAC address. Verify whether the number of modules currently produced is greater than or equal to the maximum number of modules. If so, do not allow the application for a device ID.

2. The device ID management method according to claim 1, characterized in that, The step of writing activation software to obtain the device ID from the cloud platform and transmitting the device ID to the Bluetooth module includes: The software's login window receives the username and password entered by the user. Send the username and password to the cloud platform via HTTPS to enable the user to log in to the cloud platform; Check if the serial port of the activation software is connected to the Bluetooth module to read the MAC address from the Bluetooth module to be activated, and upload the MAC address to the cloud platform. The device ID is obtained by looking up the MAC address. After receiving the device ID from the cloud platform, the activation software sends the device ID to the Bluetooth module via a serial port and sends activation and write commands to the Bluetooth module.

3. The device ID management method according to claim 2, characterized in that, The Bluetooth module verifies the validity of the device ID and writes the device ID into the efuse area. It then sends a confirmation message of successful device ID writing to the activation software, including: The Bluetooth module checks if a device ID exists in the efuse area to determine whether activation is required. After receiving the device ID, the Bluetooth module performs CRC data verification on the device ID; Write the device ID to the efuse area and read it again from the efuse area to determine whether the storage was successful; If the device ID is successfully written, a confirmation message indicating successful activation is sent to the activation software; otherwise, a message indicating activation failure is sent to the activation software.

4. The device ID management method according to claim 3, characterized in that, The step of replying to the cloud platform via the activation software to notify that the device ID was successfully written also includes: If the cloud platform receives a message from the activation software indicating a successful write of the device ID, it increments the number of modules already produced by 1.

5. A device ID management device for a Bluetooth module, characterized in that, include: The software development module is used to develop activation software to obtain the device ID from the cloud platform and transmit the device ID to the Bluetooth module. The module writing module is used to verify the validity of the device ID through the Bluetooth module and write the device ID into the efuse area, and to send back a confirmation message of successful device ID writing to the activation software; The notification module is used to reply to the cloud platform through the activation software to notify that the device ID has been successfully written; The module is used to build a cloud platform to generate device IDs; The construction module specifically includes: The user table settings submodule is used to set up the user table through the cloud platform to record the user's username, password, maximum number of modules, and number of modules currently produced. This allows users to log in to the cloud platform using their username and password, and the cloud platform verifies the username and password to determine if the user can perform subsequent operations. The device information setting submodule is used to set the device information table through the cloud platform to record the device ID and MAC address. After the user logs in successfully, the MAC address is read from the Bluetooth module that needs to be activated and uploaded to the cloud platform. The device ID is obtained by looking up the MAC address. The verification submodule is used to verify whether the number of modules currently produced is greater than or equal to the maximum number of modules. If so, the application for a device ID is not allowed.

6. The device ID management device according to claim 5, characterized in that, The software programming module includes a receiving submodule, a login submodule, a serial port checking submodule, and an instruction sending submodule; The receiving submodule is used to receive the username and password entered by the user through the login window of the activated software; The login submodule is used to send a request for the username and password to the cloud platform via the HTTPS protocol so that the user can log in to the cloud platform; The serial port inspection submodule is used to check whether the serial port of the activation software is connected to the Bluetooth module in order to read the MAC address from the Bluetooth module to be activated, and upload the MAC address to the cloud platform, and obtain the device ID by looking up the MAC address; The instruction sending submodule is used to send the device ID to the Bluetooth module via serial port after the activation software receives the device ID from the cloud platform, and to send activation and write instructions to the Bluetooth module. The module writing module includes an efuse check submodule, a CRC check submodule, an ID writing submodule, and a reply submodule; The efuse check submodule is used to enable the Bluetooth module to check whether a device ID exists in the efuse area to determine whether activation is required. The CRC verification submodule is used to perform CRC data verification on the device ID after the Bluetooth module receives the device ID; The ID writing submodule is used to write the device ID into the efuse area and reread it from the efuse area to determine whether the storage was successful. The reply submodule is used to reply to the activation software with a confirmation message of successful activation if the device ID is successfully written, and to reply to the activation software with a message of activation failure otherwise. The notification module is also used to increment the number of modules currently produced by 1 if the cloud platform receives a successful write device ID message returned by the activation software.

7. A computer-readable storage medium, characterized in that, The storage medium stores multiple instructions, which are adapted to be loaded by a processor to execute a device ID management method for a Bluetooth module according to any one of claims 1 to 4.

Images