Bluetooth device access authentication method, electronic device and storage medium

Abstract

This application discloses a method for Bluetooth device access authentication, comprising: a Bluetooth device determining first information, the first information comprising a random device address or a random number of the Bluetooth device; and the Bluetooth device determining authentication information based on the first information, the authentication information being used for access authentication of the Bluetooth device for network configuration. This application also discloses another Bluetooth device access authentication method, electronic device, and storage medium.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a Bluetooth device access authentication method, electronic device, and storage medium. Background Art

[0002] With the continuous improvement of Bluetooth Mesh functions and the increasing popularity of its applications, the demand for network configuration of Bluetooth devices is increasing. In the Bluetooth device network configuration process, access authentication of Bluetooth devices is required. How to improve the security of Bluetooth device access authentication has always been the goal pursued by Bluetooth network technology. Summary of the Invention

[0003] The embodiments of the present application provide a Bluetooth device access authentication method, an electronic device, and a storage medium, which can improve the security of Bluetooth device access authentication.

[0004] In a first aspect, an embodiment of the present application provides a Bluetooth device access authentication method, comprising: a Bluetooth device determining first information, the first information comprising: a random device address or a random number of the Bluetooth device;

[0005] The Bluetooth device determines authentication information based on the first information, where the authentication information is used for access authentication of the Bluetooth device during network configuration.

[0006] In a second aspect, an embodiment of the present application provides a method for access authentication of a Bluetooth device, comprising: a network provisioner obtaining second information, the second information comprising: a random device address of the Bluetooth device, or a first field carrying a random number;

[0007] The second information is used to determine authentication information, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0008] In a third aspect, an embodiment of the present application provides a Bluetooth device access authentication method, comprising: a cloud server obtaining third information, the third information comprising: a random device address of the Bluetooth device, or a first field carrying a random number;

[0009] The cloud server performs network configuration access authentication on the Bluetooth device based on the third information.

[0010] In a fourth aspect, an embodiment of the present application provides a Bluetooth device access authentication method, comprising: a first cloud platform gateway obtaining fourth information, the fourth information comprising: a random device address of the Bluetooth device, or a first field carrying a random number;

[0011] The fourth information is used to determine authentication information, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0012] In a fifth aspect, an embodiment of the present application provides a Bluetooth device access authentication method, comprising: a first cloud platform obtaining fifth information, the fifth information comprising: a random device address of the Bluetooth device, or a first field carrying a random number;

[0013] The fifth information is used to determine authentication information, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0014] In a sixth aspect, an embodiment of the present application provides a Bluetooth device access authentication method, including:

[0015] The second cloud platform obtains sixth information, where the sixth information includes: a random device address of the Bluetooth device, or a first field carrying a random number;

[0016] The second cloud platform performs network configuration access authentication on the Bluetooth device based on the sixth information.

[0017] In a seventh aspect, an embodiment of the present application provides a Bluetooth device, comprising:

[0018] This embodiment of the present application provides a cloud platform, which includes:

[0019] A first processing unit is configured to determine first information, wherein the first information includes: a random device address or a random number of the Bluetooth device;

[0020] The first processing unit is configured to determine authentication information based on the first information, where the authentication information is used for access authentication of the Bluetooth device during network configuration.

[0021] In an eighth aspect, an embodiment of the present application provides a network distributor, the network distributor comprising:

[0022] A first receiving unit is configured to obtain second information, wherein the second information includes: a random device address of a Bluetooth device, or a first field carrying a random number;

[0023] The second information is used to determine authentication information, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0024] In a ninth aspect, an embodiment of the present application provides a cloud server, the cloud server comprising:

[0025] A second receiving unit is configured to obtain third information, wherein the third information includes: a random device address of the Bluetooth device, or a first field carrying a random number;

[0026] The fourth processing unit is configured to perform access authentication of the Bluetooth device to the network configuration based on the third information.

[0027] In a tenth aspect, an embodiment of the present application provides a first cloud platform gateway, the first cloud platform gateway comprising:

[0028] A third receiving unit is configured to obtain fourth information, where the fourth information includes: a random device address of the Bluetooth device, or a first field carrying a random number;

[0029] The fourth information is used to determine authentication information, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0030] In an eleventh aspect, an embodiment of the present application provides a first cloud platform, the first cloud platform comprising:

[0031] a fourth receiving unit configured to obtain fifth information, wherein the fifth information includes: a random device address of the Bluetooth device, or a first field carrying a random number;

[0032] The fifth information is used to determine authentication information, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0033] In a twelfth aspect, an embodiment of the present application provides a second cloud platform, the second cloud platform comprising:

[0034] a fifth receiving unit configured to obtain sixth information, the sixth information comprising: a random device address of the Bluetooth device, or a first field carrying a random number;

[0035] The fifth processing unit is configured to perform access authentication of the Bluetooth device to the network configuration based on the sixth information.

[0036] In the thirteenth aspect, an embodiment of the present application provides a Bluetooth device, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is used to execute the steps of the Bluetooth device access authentication method executed by the above-mentioned Bluetooth device when running the computer program.

[0037] In the fourteenth aspect, an embodiment of the present application provides a network adapter, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is used to execute the steps of the Bluetooth device access authentication method executed by the above-mentioned network adapter when running the computer program.

[0038] In the fifteenth aspect, an embodiment of the present application provides a cloud server, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is used to execute the steps of the Bluetooth device access authentication method executed by the above-mentioned cloud server when running the computer program.

[0039] In the sixteenth aspect, an embodiment of the present application provides a first cloud platform gateway, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein when the processor is used to run the computer program, it executes the steps of the Bluetooth device access authentication method executed by the above-mentioned first cloud platform gateway.

[0040] In aspect 17, an embodiment of the present application provides a first cloud platform, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein when the processor is used to run the computer program, it executes the steps of the Bluetooth device access authentication method executed by the above-mentioned first cloud platform.

[0041] In aspect 18, an embodiment of the present application provides a second cloud platform, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein when the processor is used to run the computer program, it executes the steps of the Bluetooth device access authentication method executed by the above-mentioned second cloud platform.

[0042] In the nineteenth aspect, an embodiment of the present application provides a chip, including: a processor, used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned Bluetooth device access authentication method.

[0043] In the twentieth aspect, an embodiment of the present application provides a storage medium storing an executable program, which, when executed by a processor, implements the above-mentioned Bluetooth device access authentication method.

[0044] In aspect 21, an embodiment of the present application provides a computer program product, comprising computer program instructions, which enable a computer to execute the above-mentioned Bluetooth device access authentication method.

[0045] In aspect 22, an embodiment of the present application provides a computer program, which enables a computer to execute the above-mentioned Bluetooth device access authentication method.

[0046] The Bluetooth device access authentication method, electronic device, and storage medium provided in the embodiments of the present application include: the Bluetooth device determines first information, the first information including: a random device address or a random number of the Bluetooth device; the Bluetooth device determines authentication information based on the first information, and the authentication information is used for access authentication of the Bluetooth device network configuration. In this way, since the random device address or random number is dynamically generated by the Bluetooth device in each network configuration cycle, the authentication information determined based on the random device address or random number dynamically generated in each network configuration cycle improves the security of Bluetooth device access authentication compared to authentication information determined based on constant parameters, and avoids the Bluetooth device being configured and controlled by other network configuration devices due to leakage of constant parameters; at the same time, the Bluetooth device access authentication method provided in the embodiments of the present application can also ensure the convenience of Bluetooth device access authentication. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 Output OOB authentication process diagram for this application embodiment;

[0048] Figure 2 A schematic diagram of the process of inputting OOB authentication for an embodiment of the present application;

[0049] Figure 3 This is a flowchart of static OOB or non-OOB authentication in an embodiment of the present application;

[0050] Figure 4 A schematic diagram of an optional processing flow of a Bluetooth device access authentication method applied to a Bluetooth device provided in an embodiment of the present application;

[0051] Figure 5 This is a schematic diagram of the format of an unconfigured network broadcast message in an embodiment of the present application;

[0052] Figure 6 A schematic diagram of an optional processing flow of a Bluetooth device access authentication method applied to a network adapter provided in an embodiment of the present application;

[0053] Figure 7 A schematic diagram of an optional processing flow of a Bluetooth device access authentication method applied to a cloud server provided in an embodiment of the present application;

[0054] Figure 8 A schematic diagram of an optional processing flow of a Bluetooth device access authentication method applied to a first cloud platform gateway provided in an embodiment of the present application;

[0055] Figure 9 A schematic diagram of an optional processing flow of a Bluetooth device access authentication method applied to a first cloud platform provided in an embodiment of the present application;

[0056] Figure 10A schematic diagram of an optional processing flow of a Bluetooth device access authentication method applied to a second cloud platform provided in an embodiment of the present application;

[0057] Figure 11 A schematic diagram of a first optional detailed processing flow of the Bluetooth device access authentication method provided in an embodiment of the present application;

[0058] Figure 12 A schematic diagram of a second optional detailed processing flow of the Bluetooth device access authentication method provided in an embodiment of the present application;

[0059] Figure 13 A schematic diagram of a third optional detailed processing flow of the Bluetooth device access authentication method provided in an embodiment of the present application;

[0060] Figure 14 A schematic diagram of a fourth optional detailed processing flow of the Bluetooth device access authentication method provided in an embodiment of the present application;

[0061] Figure 15 A fifth optional detailed processing flow diagram of the Bluetooth device access authentication method provided in an embodiment of the present application;

[0062] Figure 16 A sixth optional detailed processing flow diagram of the Bluetooth device access authentication method provided in an embodiment of the present application;

[0063] Figure 17 A schematic diagram of an optional structure of a Bluetooth device provided in an embodiment of the present application;

[0064] Figure 18 A schematic diagram of an optional structure of the network distribution device provided in an embodiment of the present application;

[0065] Figure 19 A schematic diagram of an optional structure of a cloud server provided in an embodiment of the present application;

[0066] Figure 20 A schematic diagram of an optional composition structure of the first cloud platform gateway provided in an embodiment of the present application;

[0067] Figure 21 A schematic diagram of an optional composition structure of the first cloud platform provided in an embodiment of the present application;

[0068] Figure 22 A schematic diagram of an optional composition structure of the second cloud platform provided in an embodiment of the present application;

[0069] Figure 23 A schematic diagram of the hardware structure of the electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0070] In order to enable a more detailed understanding of the features and technical contents of the embodiments of the present application, the implementation of the embodiments of the present application is described in detail below with reference to the accompanying drawings. The attached drawings are for reference only and are not used to limit the embodiments of the present application.

[0071] Before describing the embodiments of the present application, a brief description of the relevant contents is given.

[0072] Bluetooth Mesh (wireless mesh network): A mesh device network built on low-power Bluetooth technology that enables many-to-many Bluetooth device communication.

[0073] Gateway: A Bluetooth Mesh network configuration device responsible for configuring devices connected to the Bluetooth Mesh network.

[0074] Bluetooth device: A Bluetooth Mesh device to be configured needs to join the Bluetooth Mesh network through the Bluetooth Mesh configuration process and become a Bluetooth Mesh device in the Bluetooth Mesh network.

[0075] Session key: used to encrypt and decrypt configuration data during the Bluetooth Mesh configuration process.

[0076] Device key: used for subsequent configuration of Bluetooth Mesh devices after successful network configuration. Only the gateway and Bluetooth Mesh devices know it and are used for secure communication between the two.

[0077] During the network configuration process of Bluetooth devices, access authentication needs to be performed on the Bluetooth devices. There are four out-of-band (OOB) authentication methods for Bluetooth devices: No OOB, Static OOB, Input OOB, and Output OOB.

[0078] Output OOB authentication process diagram, such as Figure 1 As shown, an unprovisioned Bluetooth device selects a random number and outputs it in a manner compatible with its functionality. For example, if the unprovisioned device is a light bulb, it can flash a specified number of times. If the device has an LCD screen, it can display the random number as a multi-digit value. The provisioner needs to input the observed number to authenticate the Bluetooth device.

[0079] Enter the OOB authentication process diagram, such as Figure 2 As shown in the figure, the provisioner generates and displays a random number, then prompts the user to take appropriate action to enter the random number into the unprovisioned Bluetooth device. For example, in the case of a light switch, the user can enter the random number by pressing the button several times within a certain time.

[0080] Flowchart of static OOB or no OOB authentication, such as Figure 3 As shown, if neither input or output out-of-band is available, the provisioner and the unprovisioned Bluetooth device can use Static OOB verification or No OOB verification: using static OOB information; or, if static OOB information is unavailable, directly replacing it with a value of 0. In this case, the provisioner and the unprovisioned Bluetooth device each generate a random number and then check the value to confirm it.

[0081] The authentication formula for Bluetooth devices is:

[0082] ConfirmationDevice=AES-CMACconfirmationkey(RandomDevice||AuthValue)

[0083] The authentication formula for the network adapter is:

[0084] ConfirmationProvisioner=AES-CMACconfirmationkey(RandomProvisioner||AuthValue)

[0085] Among them, AES-CMAC is the encryption algorithm, confirmationkey is the confidential key, (RandomProvisioner||AuthValue) is the plaintext, ConfirmationProvisioner is the generated ciphertext, AuthValue is the OOB authentication information, the network provisioner and the Bluetooth device have the same OOB authentication information, and the network provisioner and the Bluetooth device complete the network provisioning authentication of the Bluetooth device by exchanging their own calculated confirmation and ProvisioningRandom.

[0086] In actual product forms, Output OOB / Input OOB authentication requires the Bluetooth device to have input or output capabilities, and human participation is required during the authentication process. Therefore, due to factors such as Bluetooth device cost and network configuration convenience, few devices use Output OOB / Input OOB authentication, and No OOB authentication is completely insecure. Therefore, most devices use Static OOB authentication.

[0087] In the related art, the OOB authentication information required for the Static OOB authentication method of Bluetooth devices is mostly pre-generated and directly burned into the device at the factory. The Static OOB authentication information is the same every time the network is configured, and the security of the network configuration process cannot be optimized. When the Static OOB authentication information is leaked, other network configuration devices can configure the Bluetooth device through external devices and achieve the purpose of control.

[0088] If the OOB authentication information is leaked, an attacker can impersonate a legitimate device to try to join the Bluetooth network. Since the attacker has the leaked OOB authentication information and the Beacon information broadcast by the legitimate device is also easy to copy, the attacker can completely join the network through the authentication process, resulting in the leakage of the network key (NetKey) and application key (AppKey), causing a huge security vulnerability.

[0089] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, advanced long term evolution (LTE-A) system, new radio (NR) system, NR system evolution system, LTE on unlicensed band (LTE-based access to unlicensed spectrum, LTE-U) system, NR on unlicensed band (NR-based access to unlicensed spectrum, NR-U) system, universal mobile telecommunication system (UMTS), world wide interoperability for microwave access (WMI), etc. access, WiMAX) communication system, wireless local area networks (WLAN), wireless fidelity (WiFi), next generation communication system or other communication systems, etc.

[0090] The system architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0091] The network devices involved in the embodiments of the present application may be ordinary base stations (such as NodeB or eNB or gNB), new radio controllers (new radio controller, NR controller), centralized network elements (centralized unit), new wireless base stations, radio frequency remote modules, micro base stations, relays, distributed network elements (distributed unit), transmission reception points (TRP), transmission points (TP) or any other devices. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network devices. For the convenience of description, in all embodiments of the present application, the above-mentioned devices that provide wireless communication functions for terminal devices are collectively referred to as network devices.

[0092] In the embodiments of the present application, the terminal device may be any terminal, for example, the terminal device may be a user equipment for machine type communication. That is, the terminal device may also be referred to as a user equipment UE, a mobile station (MS), a mobile terminal, a terminal, etc. The terminal device may communicate with one or more core networks via a radio access network (RAN). For example, the terminal device may be a mobile phone (or a "cellular" phone), a computer with a mobile terminal, etc. For example, the terminal device may also be a portable, pocket-sized, handheld, computer-built-in, or vehicle-mounted mobile device that exchanges language and / or data with a radio access network. This is not specifically limited in the embodiments of the present application.

[0093] Optionally, the network device and terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface; can also be deployed in the air on aircraft, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of the network device and terminal device.

[0094] Optionally, the network device and the terminal device, and the terminal device and the terminal device may communicate through a licensed spectrum (licensed spectrum), or may communicate through an unlicensed spectrum (unlicensed spectrum), or may communicate through both a licensed spectrum and an unlicensed spectrum. The network device and the terminal device, and the terminal device and the terminal device may communicate through a spectrum below 7 gigahertz (GHz), or may communicate through a spectrum above 7 GHz, or may communicate using a spectrum below 7 GHz and a spectrum above 7 GHz at the same time. The embodiments of the present application do not limit the spectrum resources used between the network device and the terminal device.

[0095] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and vehicle-to-vehicle (V2V) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0096] An optional processing flow of a Bluetooth device access authentication method applied to a Bluetooth device provided in an embodiment of the present application is as follows: Figure 4 As shown, the following steps may be included:

[0097] Step S201: The Bluetooth device determines first information, where the first information includes: a random device address or a random number of the Bluetooth device.

[0098] In some embodiments, the random device address or random number of the Bluetooth device may be regenerated by the Bluetooth device in the waiting network configuration state based on the current network configuration.

[0099] In some embodiments, the random device address may be a random dedicated device address.

[0100] Step S202: The Bluetooth device determines authentication information based on the first information, where the authentication information is used for access authentication of the Bluetooth device to a network.

[0101] In some embodiments, the first information includes a random device address, and the Bluetooth device determines the authentication information based on the random device address. The manner in which the Bluetooth device determines the authentication information based on the random device address may include at least one of the following:

[0102] OOB authentication information = SHA256 (Device address, Device ID, Secret);

[0103] OOB authentication information = SHA256 (Device address, UUID, Secret);

[0104] OOB authentication information = SHA256 (Device address, Secret);

[0105] Device address represents the random device address, Device ID represents the Bluetooth device identifier, Secret represents the secret key, and UUID represents the Bluetooth device's Universally Unique Identifier. SHA256 is a standard secure hash algorithm, but the algorithm used to determine the authentication information is not limited to SHA256. A method for calculating OOB authentication information is shown in Table 1 below:

[0106] Table 1

[0107]

[0108] The UUID of a Bluetooth device is defined by the manufacturer of the Bluetooth device. The format of the UUID of a Bluetooth device is shown in Table 2 below:

[0109] Table 2

[0110] Field Size (Octets) Notes Company ID 2 Company logo Did 6 Device ID, unique device identifier RFU 8 reserve

[0111] In some embodiments, the method may further include:

[0112] Step S203: The Bluetooth device sends a broadcast message.

[0113] In some embodiments, the broadcast message carries a random device address; for example, the random device address is carried in an "AdvA" field of the broadcast message.

[0114] In some other embodiments, the random number is carried in the first field of the broadcast message. In a specific implementation, if the broadcast message is an unprovisioned Beacon message, the random number can be carried in the Uniform Resource Identifier (URI) Hash field of the unprovision Beacon message.

[0115] Among them, the format of the unprovision Beacon message is as follows: Figure 5As shown, the URI Hash field includes four bytes, and the random number is filled in the URI Hash field including one or more bytes.

[0116] In some optional implementations, the Bluetooth device sends a broadcast message to the network provisioner, so that the network provisioner uses the broadcast message to perform access authentication on the Bluetooth device based on static OOB authentication.

[0117] In other optional implementations, the Bluetooth device can send a broadcast message to the platform gateway of the network to be accessed, and the platform gateway sends the content included in the broadcast message to the cloud platform for developing the Bluetooth device, so that the cloud platform for developing the Bluetooth device can perform access authentication on the Bluetooth device based on static OOB authentication.

[0118] It should be noted that in the embodiments of the present application, the random device address remains unchanged during a single network configuration process; the random number remains unchanged during a single network configuration process. This can be understood as meaning that the random device address remains unchanged until the current network configuration ends, or before the network configuration times out, or before the network configuration fails; and the random number remains unchanged until the current network configuration ends, or before the network configuration times out, or before the network configuration fails. That is, the random number or random device address determined by the Bluetooth device is valid within the Bluetooth device's single network configuration process.

[0119] An optional processing flow of a Bluetooth device access authentication method applied to a network adapter is provided in an embodiment of the present application, such as Figure 6 As shown, the following steps may be included:

[0120] Step S301: The network adapter obtains second information, where the second information includes: a random device address of the Bluetooth device, or a first field carrying a random number; the second information is used to determine authentication information.

[0121] In some embodiments, the network adapter receives second information sent by the Bluetooth device.

[0122] In some embodiments, the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0123] In some embodiments, the first field may be a URI Hash field filled with a random number generated by the Bluetooth device.

[0124] In some optional implementations, the network provisioner obtains the second information, including: the network provisioner receives a broadcast message sent by a Bluetooth device, where the broadcast message carries the random device address.

[0125] In some other optional implementations, the network provisioner obtains the second information, including: the network provisioner receives a broadcast message sent by a Bluetooth device, where the first field of the broadcast message carries the random number.

[0126] In some embodiments, the method may further include:

[0127] Step S302: The network provisioner performs network provisioning access authentication on the Bluetooth device based on the second information.

[0128] In some optional implementations, for a scenario where the second information includes a random device address, the network provisioner performs network provisioning access authentication on the Bluetooth device based on the number of times the random device address is used.

[0129] In specific implementation, if the random device address has been used more than or equal to once, the network provisioner confirms that the Bluetooth device authentication has failed; that is, if the random device address has been used before this network provisioning, the network provisioner confirms that the Bluetooth device authentication has failed; it can also be understood that if the random device address has been used before this network provisioning and the random device address is included in the used random device addresses stored by the network provisioner itself, the network provisioner confirms that the Bluetooth device authentication has failed. Alternatively, if the random device address has been used zero times and the UUID of the Bluetooth device is valid, the network provisioner determines the authentication information based on the random device address; that is, if the random device address has not been used before this network provisioning (the random device address is not included in the used random device addresses stored by the network provisioner itself before this network provisioning), if the network provisioner checks that the UUID of the Bluetooth device is valid, the network provisioner obtains the device's secret through Did, and uses the random device address, UUID, and secret to determine the authentication information of the Bluetooth device in this network provisioning, and starts this network provisioning process.

[0130] In some embodiments, the network adapter may determine authentication information based on the random device address in at least one of the following ways:

[0131] OOB authentication information = SHA256 (Device address, Device ID, Secret);

[0132] OOB authentication information = SHA256 (Device address, UUID, Secret);

[0133] OOB authentication information = SHA256 (Device address, Secret);

[0134] Among them, Device address represents the random device address, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0135] In some other optional implementations, for the scenario where the second information includes the first field, the network provisioner performs network provisioning access authentication on the Bluetooth device based on the number of times the value of the first field is used.

[0136] In specific implementation, if the value of the first field has been used more than or equal to once, the network provisioner confirms that the Bluetooth device authentication has failed; that is, the value of the first field has been used before this network provisioning; it can also be understood that before this network provisioning, the value of the first field used and saved by the network provisioner itself includes the value of the first field carried in the second message, then the network provisioner confirms that the Bluetooth device authentication has failed. Alternatively, if the value of the first field has been used the number of times is zero (before this network provisioning, the value of the first field has not been used, and the value of the first field used and saved by the network provisioner itself does not include the value of the first field carried in the second message), and the UUID of the Bluetooth device is legal, the network provisioner obtains the device's secret through Did, and determines the authentication information of the Bluetooth device in this network provisioning using the value of the first field, UUID, and secret, and starts this network provisioning process.

[0137] Taking the first field as a URI Hash field as an example, the value of the first field is the URI Hash value. The network adapter can determine the authentication information based on the value of the first field in at least one of the following ways:

[0138] OOB authentication information = SHA256 (URI Hash value, Device ID, Secret);

[0139] OOB authentication information = SHA256 (URI Hash value, UUID, Secret);

[0140] OOB authentication information = SHA256 (URI Hash value, Secret);

[0141] Among them, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0142] In the above step S302, after the network provisioner obtains the second information, the network provisioner performs network access authentication on the Bluetooth device based on the second information. However, in some specific embodiments, after the network provisioner obtains the second information, the network provisioner does not perform network access authentication on the Bluetooth device, but instead sends the content included in the second information to the cloud server, which then performs network access authentication on the Bluetooth device. In this scenario, after executing step S301, the embodiment of the present application further includes:

[0143] Step S303: The network distributor sends the third information to the cloud server, where the third information includes: the random device address or the first field.

[0144] In some embodiments, the third information is used by the cloud server to perform access authentication for the Bluetooth device to perform network configuration.

[0145] In some embodiments, the third information may further include a UUID of the Bluetooth device.

[0146] It should be noted that in the embodiments of the present application, the random device address remains unchanged during a single network configuration process; the random number remains unchanged during a single network configuration process. This can be understood as meaning that the random device address remains unchanged until the current network configuration ends, or before the network configuration times out, or before the network configuration fails; and the random number remains unchanged until the current network configuration ends, or before the network configuration times out, or before the network configuration fails. That is, the random number or random device address determined by the Bluetooth device is valid within the Bluetooth device's single network configuration process.

[0147] An optional processing flow of a Bluetooth device access authentication method applied to a cloud server provided in an embodiment of the present application is as follows: Figure 7 As shown, the following steps may be included:

[0148] In step S401, the cloud server obtains third information, where the third information includes: a random device address of the Bluetooth device, or a first field carrying a random number.

[0149] In some embodiments, the cloud server receives third information sent by the network distributor.

[0150] In some embodiments, the third information may further include a UUID of the Bluetooth device.

[0151] In some embodiments, the first field may be a URI Hash field filled with a random number generated by the Bluetooth device.

[0152] Step S402: The cloud server performs network access authentication on the Bluetooth device based on the third information.

[0153] In some optional implementations, for a scenario where the second information includes a random device address, the cloud server performs network configuration access authentication on the Bluetooth device based on the number of times the random device address is used.

[0154] In specific implementation, if the random device address has been used more than or equal to once, the cloud server confirms that the Bluetooth device authentication has failed; that is, before this network configuration, the random device address has been used, and the cloud server confirms that the Bluetooth device authentication has failed; it can also be understood that before this network configuration, the random device address is included in the used random device addresses saved by the cloud server itself, and the cloud server confirms that the Bluetooth device authentication has failed. Alternatively, if the random device address has been used a number of times and the Bluetooth device's UUID is legal, the cloud server determines the authentication information based on the random device address; that is, before this network configuration, the random device address has not been used (before this network configuration, the random device address is not included in the used random device addresses saved by the cloud server itself). If the cloud server checks that the UUID of the Bluetooth device is legal, the cloud server obtains the device's secret through Did, and uses the random device address, UUID, and secret to determine the authentication information of the Bluetooth device in this network configuration, and starts this network configuration process.

[0155] In some embodiments, the cloud server may determine authentication information based on the random device address in at least one of the following ways:

[0156] OOB authentication information = SHA256 (Device address, Device ID, Secret);

[0157] OOB authentication information = SHA256 (Device address, UUID, Secret);

[0158] OOB authentication information = SHA256 (Device address, Secret);

[0159] Among them, Device address represents the random device address, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0160] In other optional implementations, for the scenario where the second information includes the first field, the cloud server performs network configuration access authentication on the Bluetooth device based on the number of times the value of the first field is used.

[0161] In specific implementation, if the value of the first field is used more than or equal to once, the cloud server confirms that the Bluetooth device authentication has failed; that is, the value of the first field has been used before this network configuration; it can also be understood that the value of the first field has been used before this network configuration, and the value of the first field used and saved by the cloud server itself includes the value of the first field carried in the second message, then the cloud server confirms that the Bluetooth device authentication has failed. Alternatively, if the value of the first field is used zero times (before this network configuration, the value of the first field used and saved by the cloud server itself does not include the value of the first field carried in the second message), and the UUID of the Bluetooth device is legal, the cloud server obtains the device's secret through Did, and determines the authentication information of the Bluetooth device in this network configuration using the value of the first field, UUID, and secret, and starts this network configuration process.

[0162] Taking the first field as a URI Hash field as an example, the value of the first field is the URI Hash value. The cloud server can determine the authentication information based on the value of the first field in at least one of the following ways:

[0163] OOB authentication information = SHA256 (URI Hash value, Device ID, Secret);

[0164] OOB authentication information = SHA256 (URI Hash value, UUID, Secret);

[0165] OOB authentication information = SHA256 (URI Hash value, Secret);

[0166] Among them, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0167] It should be noted that in the embodiments of the present application, the random device address remains unchanged during a single network configuration process; the random number remains unchanged during a single network configuration process. This can be understood as meaning that the random device address remains unchanged until the current network configuration ends, or before the network configuration times out, or before the network configuration fails; and the random number remains unchanged until the current network configuration ends, or before the network configuration times out, or before the network configuration fails. That is, the random number or random device address determined by the Bluetooth device is valid within the Bluetooth device's single network configuration process.

[0168] In some scenarios, the Bluetooth device is a device in a smart home system, and the Bluetooth device can be accessed and authenticated across different smart home platforms. Based on this, an optional processing flow of the Bluetooth device access authentication method applied to the first cloud platform gateway provided in the embodiment of the present application is as follows: Figure 8As shown, the following steps may be included:

[0169] In step S501, the first cloud platform gateway obtains fourth information, where the fourth information includes: a random device address of a Bluetooth device, or a first field carrying a random number; and the fourth information is used to determine authentication information.

[0170] In some embodiments, the first cloud platform gateway receives fourth information sent by the Bluetooth device.

[0171] In some embodiments, the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0172] In some embodiments, the first field may be a URI Hash field filled with a random number generated by the Bluetooth device.

[0173] In some embodiments, the fourth information further includes: a company identifier (CID) of the second cloud platform corresponding to the Bluetooth device. The second cloud platform corresponding to the Bluetooth device may be a cloud platform for developing the Bluetooth device.

[0174] In some optional implementations, the first cloud platform gateway obtains the fourth information, including: the first cloud platform gateway receives a broadcast message sent by a Bluetooth device, where the broadcast message carries the random device address.

[0175] In some other optional implementations, the first cloud platform gateway receives the fourth information, including: the first cloud platform gateway receives a broadcast message sent by a Bluetooth device, and the first field of the broadcast message carries the random number.

[0176] For a scenario where the fourth message includes a random device address, in some optional embodiments, the method may further include:

[0177] Step S502: The first cloud platform gateway sends a random device address to the first cloud platform, and the first cloud platform gateway corresponds to the first cloud platform.

[0178] Among them, the first cloud platform gateway corresponds to the first cloud platform, and the first cloud platform Wangguang and the first cloud platform may belong to the same network.

[0179] For the scenario where the fourth message includes the first field, in some optional embodiments, after executing step S501, the method may further include:

[0180] Step S503: The first cloud platform gateway sends the first field to the first cloud platform, where the first cloud platform gateway corresponds to the first cloud platform.

[0181] Among them, the first cloud platform gateway corresponds to the first cloud platform, and the first cloud platform Wangguang and the first cloud platform may belong to the same network.

[0182] In the optional steps S502 and S503 of the embodiment of the present application, the first cloud platform gateway sends a random device address or a first field carrying a random number to the first cloud platform, and the first cloud platform can send the random device address or the first field carrying a random number to the second cloud platform for developing the Bluetooth device, so that the second cloud platform performs access authentication for the Bluetooth device network configuration.

[0183] It should be noted that in the embodiments of the present application, the random device address remains unchanged during a single network configuration process; the random number remains unchanged during a single network configuration process. This can be understood as meaning that the random device address remains unchanged until the current network configuration ends, or before the network configuration times out, or before the network configuration fails; and the random number remains unchanged until the current network configuration ends, or before the network configuration times out, or before the network configuration fails. That is, the random number or random device address determined by the Bluetooth device is valid within the Bluetooth device's single network configuration process.

[0184] In some scenarios, the Bluetooth device is a device in a smart home system, and the Bluetooth device can be accessed and authenticated across different smart home platforms. Based on this, an optional processing flow of the Bluetooth device access authentication method applied to the first cloud platform is provided in an embodiment of the present application, such as Figure 9 As shown, the following steps may be included:

[0185] In step S601, the first cloud platform obtains fifth information, where the fifth information includes: a random device address of the Bluetooth device, or a first field carrying a random number; the fifth information is used to determine authentication information.

[0186] In some embodiments, the first cloud platform receives fifth information sent by the first cloud platform gateway.

[0187] In some embodiments, the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0188] In some embodiments, the fifth information may further include: a UUID of the Bluetooth device and a CID of the second cloud platform corresponding to the Bluetooth device.

[0189] In some embodiments, if the Bluetooth device is not a device corresponding to the first cloud platform, that is, the Bluetooth device is not a device developed by the first cloud platform, the method may further include:

[0190] Step S602: The first cloud platform sends sixth information to the second cloud platform, where the sixth information includes: the random device address, or the first field.

[0191] In some embodiments, the first cloud platform determines the second cloud platform for developing the Bluetooth device based on the CID of the second cloud platform corresponding to the Bluetooth device, and sends sixth information to the second cloud platform; the sixth information is used by the second cloud platform to determine authentication information, and the second cloud platform corresponds to the Bluetooth device.

[0192] In some embodiments, the first field may be a URI Hash field filled with a random number generated by the Bluetooth device.

[0193] It should be noted that in the embodiments of the present application, the random device address remains unchanged during a single network configuration process; the random number remains unchanged during a single network configuration process. This can be understood as meaning that the random device address remains unchanged until the current network configuration ends, or before the network configuration times out, or before the network configuration fails; and the random number remains unchanged until the current network configuration ends, or before the network configuration times out, or before the network configuration fails. That is, the random number or random device address determined by the Bluetooth device is valid within the Bluetooth device's single network configuration process.

[0194] In some scenarios, the Bluetooth device is a device in a smart home system, and the Bluetooth device can be accessed and authenticated across different smart home platforms. Based on this, an optional processing flow of the Bluetooth device access authentication method applied to the second cloud platform provided in the embodiment of the present application is as follows: Figure 10 As shown, the following steps may be included:

[0195] Step S801: The second cloud platform receives sixth information, where the sixth information includes: a random device address of a Bluetooth device, or a first field carrying a random number.

[0196] In some embodiments, the second cloud platform receives the sixth information sent by the first cloud platform; the first cloud platform belongs to the network to which the Bluetooth device is to be paired; the second cloud platform corresponds to the Bluetooth device and is a cloud platform for developing Bluetooth devices.

[0197] In some embodiments, the first field may be a URI Hash field filled with a random number generated by the Bluetooth device.

[0198] Step S802: The second cloud platform performs network configuration access authentication on the Bluetooth device based on the sixth information.

[0199] In some optional implementations, for a scenario where the sixth information includes a random device address, the second cloud platform performs network configuration access authentication on the Bluetooth device based on the number of times the random device address is used.

[0200] In specific implementation, if the random device address has been used more than or equal to once, the second cloud platform confirms that the Bluetooth device authentication has failed; that is, before this network configuration, the random device address has been used, the second cloud platform confirms that the Bluetooth device authentication has failed; it can also be understood that before this network configuration, the random device address has been used, and the second cloud platform itself saves the used random device addresses including the random device address, the second cloud platform confirms that the Bluetooth device authentication has failed. Alternatively, if the random device address has been used zero times and the UUID of the Bluetooth device is legal, the second cloud platform determines the authentication information based on the random device address; that is, before this network configuration, the random device address has not been used (before this network configuration, the second cloud platform itself saves the used random device addresses including the random device address), if the second cloud platform checks that the UUID of the Bluetooth device is legal, the second cloud platform obtains the device's secret through Did, and uses the random device address, UUID and secret to determine the authentication information of the Bluetooth device in this network configuration, and starts this network configuration process.

[0201] In some embodiments, the second cloud platform may determine the authentication information based on the random device address in at least one of the following ways:

[0202] OOB authentication information = SHA256 (Device address, Device ID, Secret);

[0203] OOB authentication information = SHA256 (Device address, UUID, Secret);

[0204] OOB authentication information = SHA256 (Device address, Secret);

[0205] Among them, Device address represents the random device address, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0206] In other optional implementations, for the scenario where the sixth information includes the first field, the second cloud platform performs network configuration access authentication on the Bluetooth device based on the number of times the value of the first field is used.

[0207] In specific implementation, if the number of times the value of the first field is used is greater than or equal to once, the second cloud platform confirms that the Bluetooth device authentication has failed; that is, before this network configuration, the value of the first field has been used; it can also be understood that before this network configuration, the value of the first field has been used, and the value of the first field used and saved by the second cloud platform itself includes the value of the first field carried in the second message, then the second cloud platform confirms that the Bluetooth device authentication has failed. Alternatively, if the number of times the value of the first field is used is zero (before this network configuration, the value of the first field has not been used, and the value of the first field used and saved by the second cloud platform itself does not include the value of the first field carried in the second message), and the UUID of the Bluetooth device is legal, the second cloud platform obtains the device's secret through Did, and determines the authentication information of the Bluetooth device in this network configuration using the value of the first field, UUID, and secret, and starts this network configuration process.

[0208] Taking the first field as a URI Hash field as an example, the value of the first field is the URI Hash value. The second cloud platform determines the authentication information based on the value of the first field in at least one of the following ways:

[0209] OOB authentication information = SHA256 (URI Hash value, Device ID, Secret);

[0210] OOB authentication information = SHA256 (URI Hash value, UUID, Secret);

[0211] OOB authentication information = SHA256 (URI Hash value, Secret);

[0212] Among them, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0213] In the embodiment of the present application, after the second cloud platform determines the authentication information of the Bluetooth device in the current network configuration, the method may further include:

[0214] Step S803: The second cloud platform sends authentication information of the Bluetooth device to the first cloud platform.

[0215] It should be noted that in the embodiments of the present application, the random device address remains unchanged during a single network configuration process; the random number remains unchanged during a single network configuration process. This can be understood as meaning that the random device address remains unchanged until the current network configuration ends, or before the network configuration times out, or before the network configuration fails; and the random number remains unchanged until the current network configuration ends, or before the network configuration times out, or before the network configuration fails. That is, the random number or random device address determined by the Bluetooth device is valid within the Bluetooth device's single network configuration process.

[0216] Based on the above description of the embodiment of the present application, for the static OOB authentication method, the first optional detailed processing flow of the Bluetooth device access authentication method provided in the embodiment of the present application is as follows: Figure 11 As shown, the network adapter determines the authentication information of the Bluetooth device based on the random device address, which may include the following steps:

[0217] Step S901: The Bluetooth device enters a state ready for network configuration. The Bluetooth device regenerates a random device address and determines OOB authentication information for this network configuration based on the random device address.

[0218] In some embodiments, the random device address remains unchanged until the current network configuration ends, or the current network configuration times out or fails.

[0219] In some embodiments, the manner in which the Bluetooth device determines the OOB authentication information for the current network configuration based on the random device address may include one of the following:

[0220] OOB authentication information = SHA256 (Device address, Device ID, Secret);

[0221] OOB authentication information = SHA256 (Device address, UUID, Secret);

[0222] OOB authentication information = SHA256 (Device address, Secret);

[0223] Among them, Device address represents the random device address, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0224] Step S902: The Bluetooth device broadcasts unprovision Beacon information.

[0225] In some embodiments, the unprovision Beacon information includes a random device address.

[0226] Step S903: The network adapter discovers the Bluetooth device and determines OOB authentication information based on the random device address.

[0227] In some embodiments, the network provisioner discovers the Bluetooth device through scanning, and sends the UUID and random device address of the Bluetooth device to the cloud server; the network provisioner checks whether the UUID of the Bluetooth device is legal and whether the random device address has been used before this network provisioning; if the UUID of the Bluetooth device is legal and the random device address has not been used before this network provisioning, the network provisioner obtains the secret of the Bluetooth device through Did; the network provisioner determines the OOB authentication information based on the random device address, the UUID of the Bluetooth device and the secret of the Bluetooth device.

[0228] In some embodiments, the network adapter may determine authentication information based on the random device address in at least one of the following ways:

[0229] OOB authentication information = SHA256 (Device address, Device ID, Secret);

[0230] OOB authentication information = SHA256 (Device address, UUID, Secret);

[0231] OOB authentication information = SHA256 (Device address, Secret);

[0232] Among them, Device address represents the random device address, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0233] In steps S904 to S9020, the Bluetooth device interacts with the network adapter to implement network configuration of the Bluetooth device.

[0234] In some embodiments, after the Bluetooth device and the network adapter respectively determine the OOB authentication information, the Bluetooth device interacts with the network adapter to implement the processing flow of network adapter configuration of the Bluetooth device, which is the same as the existing technology and will not be repeated here.

[0235] Based on the above description of the embodiment of the present application, for the static OOB authentication method, the embodiment of the present application provides a second optional detailed processing flow of the Bluetooth device access authentication method, such as Figure 12 As shown, the cloud server determines the authentication information of the Bluetooth device based on the random device address, including the following steps:

[0236] Step S1001: The Bluetooth device enters a state ready for network configuration. The Bluetooth device regenerates a random device address and determines OOB authentication information for this network configuration based on the random device address.

[0237] In some embodiments, the random device address remains unchanged until the current network configuration ends, or the current network configuration times out or fails.

[0238] In some embodiments, the manner in which the Bluetooth device determines the OOB authentication information for the current network configuration based on the random device address may include one of the following:

[0239] OOB authentication information = SHA256 (Device address, Device ID, Secret);

[0240] OOB authentication information = SHA256 (Device address, UUID, Secret);

[0241] OOB authentication information = SHA256 (Device address, Secret);

[0242] Among them, Device address represents the random device address, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0243] Step S1002: The Bluetooth device broadcasts unprovision Beacon information.

[0244] In some embodiments, the unprovision Beacon information includes a random device address.

[0245] Step S1003: The network adapter discovers the Bluetooth device and determines OOB authentication information based on the random device address.

[0246] In some embodiments, the network adapter discovers the Bluetooth device by scanning, and sends the UUID and random device address of the Bluetooth device to the cloud server.

[0247] Step S1004: The cloud server determines OOB authentication information.

[0248] In some embodiments, the cloud server checks whether the UUID of the Bluetooth device is legal and whether the random device address has been used before this network configuration; if the UUID of the Bluetooth device is legal and the random device address has not been used before this network configuration, the cloud server obtains the secret of the Bluetooth device through Did; the cloud server determines the OOB authentication information based on the random device address, the UUID of the Bluetooth device and the secret of the Bluetooth device.

[0249] In some embodiments, the cloud server may determine authentication information based on the random device address in at least one of the following ways:

[0250] OOB authentication information = SHA256 (Device address, Device ID, Secret);

[0251] OOB authentication information = SHA256 (Device address, UUID, Secret);

[0252] OOB authentication information = SHA256 (Device address, Secret);

[0253] Among them, Device address represents the random device address, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0254] Step S1005: The cloud server sends OOB authentication information to the network adapter.

[0255] In steps S1006 to S1022, the Bluetooth device interacts with the network adapter to implement network configuration of the Bluetooth device.

[0256] In some embodiments, after the Bluetooth device and the network adapter respectively determine the OOB authentication information, the Bluetooth device interacts with the network adapter to implement the processing flow of network adapter configuration of the Bluetooth device, which is the same as the existing technology and will not be repeated here.

[0257] Based on the above description of the embodiment of the present application, for the static OOB authentication method, the embodiment of the present application provides a third optional detailed processing flow of the Bluetooth device access authentication method, such as Figure 13 As shown, the access authentication of Bluetooth devices between smart home systems may include the following steps:

[0258] Step S1101: The Bluetooth device enters a state ready for network configuration. The Bluetooth device regenerates a random device address and determines OOB authentication information for this network configuration based on the random device address.

[0259] In some embodiments, the random device address remains unchanged until the current network configuration ends, or the current network configuration times out or fails.

[0260] In some embodiments, the manner in which the Bluetooth device determines the OOB authentication information for the current network configuration based on the random device address may include one of the following:

[0261] OOB authentication information = SHA256 (Device address, Device ID, Secret);

[0262] OOB authentication information = SHA256 (Device address, UUID, Secret);

[0263] OOB authentication information = SHA256 (Device address, Secret);

[0264] Among them, Device address represents the random device address, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0265] In some embodiments, the Bluetooth device is a device developed based on the B cloud platform

[0266] Step S1102: The Bluetooth device sends a broadcast packet to the A cloud platform gateway.

[0267] In some embodiments, the broadcast packet may include: a random device address, a UUID of a Bluetooth device.

[0268] Among them, the A cloud platform gateway is the gateway corresponding to the network to which the Bluetooth device is to be configured.

[0269] In step S1103, the A cloud platform gateway queries the type of the Bluetooth device and sends the type of the Bluetooth device to the A cloud platform.

[0270] In some embodiments, the type of the Bluetooth device may include a UUID and a random device address of the Bluetooth device.

[0271] In some embodiments, cloud platform A obtains OOB authentication information through cloud platform B. The specific implementation may include at least the following steps:

[0272] In step S11031, the A cloud platform determines that the Bluetooth device is not a device developed by the A cloud platform.

[0273] In step S11032, the A cloud platform sends a request to the intercommunication server to query the CID corresponding to the Bluetooth device.

[0274] Step S11033: The interconnection server sends the platform information for developing the Bluetooth device to the A cloud platform.

[0275] Step S11034: Cloud platform A sends a request message to cloud platform B, requesting to query the device type.

[0276] In some embodiments, the request message includes the CID of the Bluetooth device, the UUID of the Bluetooth device, and the random device address.

[0277] In step S11035, the B cloud platform checks whether the UUID of the Bluetooth device is legal and whether the random device address has been used before this network configuration; if the UUID of the Bluetooth device is legal and the random device address has not been used before this network configuration, the B cloud platform obtains the secret of the Bluetooth device through Did; the B cloud platform determines the OOB authentication information based on the random device address, the UUID of the Bluetooth device and the secret of the Bluetooth device.

[0278] Step S11036: Cloud platform B sends the device type and OBB authentication information to cloud platform A.

[0279] In some embodiments, the B cloud platform also sends device information to the A cloud platform, where the device information includes control functions and control commands supported by the Bluetooth device.

[0280] In step S1104, the A cloud platform sends the device type and OOB authentication information to the A cloud platform gateway.

[0281] In steps S1105-S1106, the A platform gateway completes connection and access with the Bluetooth device.

[0282] Execute steps S11071 to S110710, the Bluetooth device interacts with the A cloud platform gateway to implement network configuration of the Bluetooth device.

[0283] Step S110711, the A cloud platform gateway reports the authentication result to the A cloud platform.

[0284] Step S110712, cloud platform A stores device information.

[0285] In step S1108, the A cloud platform gateway broadcasts the authentication result.

[0286] Based on the above description of the embodiment of the present application, for the static OOB authentication method, the embodiment of the present application provides a fourth optional detailed processing flow of the Bluetooth device access authentication method, such as Figure 14 As shown, the network provisioner determines the authentication information of the Bluetooth device based on the URI Hash field, which may include the following steps:

[0287] Step S1201: The Bluetooth device enters a state ready for network configuration. The Bluetooth device regenerates a random number and determines OOB authentication information for this network configuration based on the random number.

[0288] In some embodiments, the random number remains unchanged until the current network configuration ends, or the current network configuration times out or fails.

[0289] In some embodiments, the Bluetooth device determines the OOB authentication information for the current network configuration based on a random number, which may be the Bluetooth device determining the OOB authentication information for the current network configuration based on a URI Hash field populated with a random number. The manner in which the Bluetooth device determines the OOB authentication information for the current network configuration based on the URI Hash field populated with a random number may include one of the following:

[0290] OOB authentication information = SHA256 (URI Hash, Device ID, Secret);

[0291] OOB authentication information = SHA256 (URI Hash, UUID, Secret);

[0292] OOB authentication information = SHA256 (URI Hash, Secret);

[0293] Among them, URI Hash represents the value of the URI Hash field filled with a random number, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0294] Step S1202: The Bluetooth device broadcasts information.

[0295] In some embodiments, the information includes a URI Hash field.

[0296] Step S1203: The network adapter discovers the Bluetooth device and determines the OOB authentication information based on the URI Hash.

[0297] In some embodiments, the network provisioner discovers the Bluetooth device through scanning, and sends the UUID and URIHash field of the Bluetooth device to the cloud server; the network provisioner checks whether the UUID of the Bluetooth device is legal and whether the value of the URI Hash field has been used before this network provisioning; if the UUID of the Bluetooth device is legal and the value of the URI Hash field has not been used before this network provisioning, the network provisioner obtains the secret of the Bluetooth device through Did; the network provisioner determines the OOB authentication information based on the value of the URI Hash field, the UUID of the Bluetooth device and the secret of the Bluetooth device.

[0298] In some embodiments, the network provisioner may determine the authentication information based on the value of the URI Hash field in at least one of the following ways:

[0299] OOB authentication information = SHA256 (URI Hash, Device ID, Secret);

[0300] OOB authentication information = SHA256 (URI Hash, UUID, Secret);

[0301] OOB authentication information = SHA256 (URI Hash, Secret);

[0302] Among them, URI Hash represents the value of the URI Hash field, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0303] In steps S1204 to S1220, the Bluetooth device interacts with the network adapter to implement network configuration of the Bluetooth device.

[0304] In some embodiments, after the Bluetooth device and the network adapter respectively determine the OOB authentication information, the Bluetooth device interacts with the network adapter to implement the processing flow of network adapter configuration of the Bluetooth device, which is the same as the existing technology and will not be repeated here.

[0305] Based on the above description of the embodiment of the present application, for the static OOB authentication method, the fifth optional detailed processing flow of the Bluetooth device access authentication method provided in the embodiment of the present application is as follows: Figure 15 As shown, the cloud server determines the authentication information of the Bluetooth device based on the URI Hash field, including the following steps:

[0306] Step S1301: The Bluetooth device enters a state ready for network configuration. The Bluetooth device regenerates a random number and determines OOB authentication information for this network configuration based on the random number.

[0307] In some embodiments, the random number remains unchanged until the current network configuration ends, or the current network configuration times out or fails.

[0308] In some embodiments, the manner in which the Bluetooth device determines the OOB authentication information for the current network configuration based on the random number may include one of the following:

[0309] OOB authentication information = SHA256 (URI Hash, Device ID, Secret);

[0310] OOB authentication information = SHA256 (URI Hash, UUID, Secret);

[0311] OOB authentication information = SHA256 (URI Hash, Secret);

[0312] Among them, URI Hash represents the value of the URI Hash field filled with a random number, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0313] Step S1302: The Bluetooth device broadcasts information.

[0314] In some embodiments, the information includes a URI Hash field.

[0315] Step S1303: The network adapter discovers the Bluetooth device.

[0316] In some embodiments, the network provisioner discovers the Bluetooth device through scanning, and sends the UUID and URIHash fields of the Bluetooth device to the cloud server.

[0317] In step S1304, the cloud server determines OOB authentication information based on the URI Hash.

[0318] In some embodiments, the cloud server checks whether the UUID of the Bluetooth device is legal and whether the value of the URI Hash field has been used before this network configuration; if the UUID of the Bluetooth device is legal and the value of the URI Hash field has not been used before this network configuration, the cloud server obtains the secret of the Bluetooth device through Did; the cloud server determines the OOB authentication information based on the value of the URI Hash field, the UUID of the Bluetooth device and the secret of the Bluetooth device.

[0319] In some embodiments, the cloud server may determine the authentication information based on the value of the URI Hash field in at least one of the following ways:

[0320] OOB authentication information = SHA256 (URI Hash, Device ID, Secret);

[0321] OOB authentication information = SHA256 (URI Hash, UUID, Secret);

[0322] OOB authentication information = SHA256 (URI Hash, Secret);

[0323] Among them, URI Hash represents the value of the URI Hash field, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0324] Step S1305: The cloud server sends OOB authentication information to the network adapter.

[0325] In steps S1306 to S1322, the Bluetooth device interacts with the network adapter to implement network configuration of the Bluetooth device.

[0326] In some embodiments, after the Bluetooth device and the network adapter respectively determine the OOB authentication information, the Bluetooth device interacts with the network adapter to implement the processing flow of network adapter configuration of the Bluetooth device, which is the same as the existing technology and will not be repeated here.

[0327] Based on the above description of the embodiment of the present application, for the static OOB authentication method, the embodiment of the present application provides a sixth optional detailed processing flow of the Bluetooth device access authentication method, such as Figure 16 As shown, the access authentication of Bluetooth devices between smart home systems may include the following steps:

[0328] Step S1401: The Bluetooth device enters a state ready for network configuration. The Bluetooth device regenerates a random number and determines OOB authentication information for this network configuration based on the random number.

[0329] In some embodiments, the random number remains unchanged until the current network configuration ends, or the current network configuration times out or fails.

[0330] In some embodiments, the Bluetooth device determines the OOB authentication information for the current network configuration based on a random number, which may be the Bluetooth device determining the OOB authentication information for the current network configuration based on a URI Hash field populated with a random number. The manner in which the Bluetooth device determines the OOB authentication information for the current network configuration based on the URI Hash field populated with a random number may include one of the following:

[0331] OOB authentication information = SHA256 (URI Hash, Device ID, Secret);

[0332] OOB authentication information = SHA256 (URI Hash, UUID, Secret);

[0333] OOB authentication information = SHA256 (URI Hash, Secret);

[0334] Among them, URI Hash represents the value of the URI Hash field filled with a random number, Device ID represents the Bluetooth device identifier, Secret represents the secret key, UUID is the universal unique identifier of the Bluetooth device; SHA256 is the standard secure hash algorithm.

[0335] In some embodiments, the Bluetooth device is a device developed based on the B cloud platform.

[0336] Step S1402: The Bluetooth device sends a broadcast packet to the A cloud platform gateway.

[0337] In some embodiments, the broadcast packet may include: a URI Hash field and a UUID of the Bluetooth device.

[0338] Among them, the A cloud platform gateway is the gateway corresponding to the network to which the Bluetooth device is to be configured.

[0339] In step S1403, the A cloud platform gateway queries the type of the Bluetooth device and sends the type of the Bluetooth device to the A cloud platform.

[0340] In some embodiments, the type of the Bluetooth device may include a UUID and a URI Hash field of the Bluetooth device.

[0341] In some embodiments, cloud platform A obtains OOB authentication information through cloud platform B. The specific implementation may include at least the following steps:

[0342] In step S14031, the A cloud platform determines that the Bluetooth device is not a device developed by the A cloud platform.

[0343] In step S14032, the A cloud platform sends a request to the intercommunication server to query the CID corresponding to the Bluetooth device.

[0344] Step S14033: The interconnection server sends the platform information for developing the Bluetooth device to the A cloud platform.

[0345] Step S14034: Cloud platform A sends a request message to cloud platform B, requesting to query the device type.

[0346] In some embodiments, the request message includes the CID of the Bluetooth device, the UUID of the Bluetooth device, and a URIHash field.

[0347] In step S14035, the B cloud platform checks whether the UUID of the Bluetooth device is legal and whether the value of the URI Hash field has been used before this network configuration; if the UUID of the Bluetooth device is legal and the value of the URI Hash field has not been used before this network configuration, the B cloud platform obtains the secret of the Bluetooth device through Did; the B cloud platform determines the OOB authentication information based on the random device address, the UUID of the Bluetooth device and the secret of the Bluetooth device.

[0348] Step S14036: Cloud platform B sends the device type and OBB authentication information to cloud platform A.

[0349] In some embodiments, the B cloud platform also sends device information to the A cloud platform, where the device information includes control functions and control commands supported by the Bluetooth device.

[0350] In step S1404, the A cloud platform sends the device type and OOB authentication information to the A cloud platform gateway.

[0351] In steps S1405-S1406, the A platform gateway completes connection and access with the Bluetooth device.

[0352] Execute steps S14071 to S140710, the Bluetooth device interacts with the A cloud platform gateway to implement network configuration of the Bluetooth device.

[0353] Step S140711: Cloud platform A gateway reports the authentication result to cloud platform A.

[0354] Step S140712, cloud platform A stores device information.

[0355] In step S1408, the A cloud platform gateway broadcasts the authentication result.

[0356] It should be noted that the "Bluetooth device" described in the embodiment of the present application can also be a Bluetooth Mesh device used in a Bluetooth Mesh network, and the "cloud platform" described in the embodiment of the present application is a cloud platform accessed by the gateway.

[0357] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0358] In the prior art, the OOB authentication information determined by constant parameters is also constant. Once the constant parameters or constant OOB authentication information are leaked, the attacker can impersonate a legitimate Bluetooth device to try to join the Bluetooth network. Since the attacker has the leaked Static OOB and the Beacon information broadcast by the legitimate Bluetooth device is also easy to copy, the attacker can completely join the Bluetooth network through authentication, resulting in the leakage of the NetKey or AppKey of the Bluetooth network, leading to a huge security vulnerability. The Bluetooth device access authentication method provided in the embodiment of the present application, the Bluetooth device generates a random device address or a random number in each network configuration cycle, and generates OOB authentication information based on the random device address or random number. The network adapter, or the cloud server, or the cloud platform corresponding to the Bluetooth device collaborates to generate OOB authentication information based on the random device address or random number, so that the network adapter or the gateway of the Bluetooth device to be configured performs access authentication on the Bluetooth device based on the OOB authentication information, completing the network configuration process of the Bluetooth device. Since the random device address or random number used to generate OOB authentication information in the embodiment of the present application is only valid in the current network configuration cycle, even if an attacker obtains the random device address or random number, the OOB information generated by the attacker using the obtained random device address or random number in other network configuration cycles cannot be used to authenticate the Bluetooth device, thereby improving the security of Bluetooth device configuration.

[0359] In order to implement the Bluetooth device access authentication method provided in the embodiment of the present application, the embodiment of the present application also provides a Bluetooth device, the optional component structure of the Bluetooth device 1500 is as follows: Figure 17 Shown, including:

[0360] The first processing unit 1501 is configured to determine first information, where the first information includes: a random device address or a random number of a Bluetooth device;

[0361] The first processing unit 1501 is configured to determine authentication information based on the first information, where the authentication information is used for access authentication of the Bluetooth device during network configuration.

[0362] In some embodiments, the Bluetooth device 1500 further includes:

[0363] The first sending unit 1502 is configured to send a broadcast message, where the broadcast message carries the random device address.

[0364] In some embodiments, the Bluetooth device 1500 further includes:

[0365] The second sending unit 1503 is configured to send a broadcast message, where the first field of the broadcast message carries the random number.

[0366] In some embodiments, the first field includes: a URI Hash field.

[0367] In some embodiments, the random device address remains unchanged in a single network configuration process; the random number remains unchanged in a single network configuration process.

[0368] In order to implement the Bluetooth device access authentication method provided in the embodiment of the present application, the embodiment of the present application also provides a network adapter, the optional component structure of the network adapter 1600 is as follows: Figure 18 Shown, including:

[0369] The first receiving unit 1601 is configured to obtain second information, where the second information includes: a random device address of a Bluetooth device, or a first field carrying a random number;

[0370] The second information is used to determine authentication information, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0371] In some embodiments, the first receiving unit 1601 is configured to receive a broadcast message, where the broadcast message carries the random device address.

[0372] In some embodiments, the network distributor 1600 further includes:

[0373] The second processing unit 1602 is configured to perform access authentication of the Bluetooth device to the network configuration based on the random device address.

[0374] In some embodiments, the second processing unit 1602 is configured to perform network configuration access authentication on the Bluetooth device based on the number of times the random device address is used.

[0375] In some embodiments, the second processing unit 1602 is configured to determine that the Bluetooth device authentication has failed if the number of times the random device address has been used is greater than or equal to once;

[0376] Alternatively, if the number of times the random device address has been used is zero and the UUID of the Bluetooth device is legal, the authentication information is determined based on the random device address.

[0377] In some embodiments, the first receiving unit 1601 is configured to receive a broadcast message, and the first field of the broadcast message carries the random number.

[0378] In some embodiments, the network distributor 1600 further includes:

[0379] The third processing unit 1603 is configured to perform access authentication of the Bluetooth device to the network configuration based on the first field.

[0380] In some embodiments, the third processing unit 1603 is configured to perform network configuration access authentication on the Bluetooth device based on the number of times the value of the first field is used.

[0381] In some embodiments, the third processing unit 1603 is configured to determine that the Bluetooth device authentication has failed if the number of times the value of the first field is used is greater than or equal to once;

[0382] Alternatively, if the number of times the value of the first field is used is zero and the UUID of the Bluetooth device is legal, the authentication information is determined based on the first field.

[0383] In some embodiments, the first field includes: a URI Hash field.

[0384] In some embodiments, the network distributor 1600 further includes:

[0385] A third sending unit 1604 is configured to send the third information to the cloud server, where the third information includes: the random device address or the first field;

[0386] The third information is used by the cloud server to perform access authentication for the Bluetooth device during network configuration.

[0387] In some embodiments, the random device address remains unchanged in a single network configuration process; the random number remains unchanged in a single network configuration process.

[0388] In order to implement the Bluetooth device access authentication method provided in the embodiment of the present application, the embodiment of the present application also provides a cloud server, and the optional component structure of the cloud server 1700 is as follows: Figure 19 Shown, including:

[0389] The second receiving unit 1701 is configured to obtain third information, where the third information includes: a random device address of a Bluetooth device, or a first field carrying a random number;

[0390] The fourth processing unit 1702 is configured to perform network configuration access authentication on the Bluetooth device based on the third information.

[0391] In some embodiments, if the third information includes a random device address of the Bluetooth device, the fourth processing unit 1702 is configured to perform network configuration access authentication on the Bluetooth device based on the number of times the random device address is used.

[0392] In some embodiments, if the random device address is used more than or equal to once, the fourth processing unit 1702 is configured to confirm that the Bluetooth device authentication has failed;

[0393] If the number of times the random device address has been used is zero and the UUID of the Bluetooth device is legal, the fourth processing unit 1702 is configured to determine authentication information based on the random device address, where the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0394] In some embodiments, if the third information includes the first field, the fourth processing unit 1702 is configured to perform network configuration access authentication on the Bluetooth device based on the number of times the value of the first field is used.

[0395] In some embodiments, if the number of times the value of the first field is used is greater than or equal to once, the fourth processing unit 1702 is configured to confirm that the Bluetooth device authentication has failed;

[0396] Alternatively, if the number of times the value of the first field is used is zero and the UUID of the Bluetooth device is legal, the fourth processing unit 1702 is configured to determine authentication information based on the first field, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0397] In some embodiments, the first field includes: a URI Hash field.

[0398] In some embodiments, the random device address remains unchanged in a single network configuration process; the random number remains unchanged in a single network configuration process.

[0399] In order to implement the Bluetooth device access authentication method provided in the embodiment of the present application, the embodiment of the present application also provides a first cloud platform gateway, the optional component structure of the first cloud platform gateway 1800 is as follows: Figure 20 Shown, including:

[0400] The third receiving unit 1801 is configured to obtain fourth information, where the fourth information includes: a random device address of a Bluetooth device, or a first field carrying a random number;

[0401] The fourth information is used to determine authentication information, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0402] In some embodiments, the third receiving unit 1801 is configured to receive a broadcast message, where the broadcast message carries the random device address.

[0403] In some embodiments, the first cloud platform gateway 1800 further includes:

[0404] The fourth sending unit 1802 is configured to send the random device address to the first cloud platform, and the first cloud platform gateway corresponds to the first cloud platform.

[0405] In some embodiments, the third receiving unit 1801 is configured to receive a broadcast message, and the first field of the broadcast message carries the random number.

[0406] In some embodiments, the first cloud platform gateway 1800 further includes:

[0407] The fifth sending unit 1803 is configured to send the first field to the first cloud platform, and the first cloud platform gateway corresponds to the first cloud platform.

[0408] In some embodiments, the first field includes: a URI Hash field.

[0409] In some embodiments, the fourth information further includes: a CID of the Bluetooth device corresponding to the second cloud platform.

[0410] In some embodiments, the random device address remains unchanged in a single network configuration process; the random number remains unchanged in a single network configuration process.

[0411] In order to implement the Bluetooth device access authentication method provided in the embodiment of the present application, the embodiment of the present application further provides a first cloud platform, the optional component structure of the first cloud platform 1900 is as follows: Figure 21 Shown, including:

[0412] The fourth receiving unit 1901 is configured to obtain fifth information, where the fifth information includes: a random device address of a Bluetooth device, or a first field carrying a random number;

[0413] The fifth information is used to determine authentication information, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0414] In some embodiments, the first cloud platform 1900 further includes:

[0415] The sixth sending unit 1902 is configured to send sixth information to the second cloud platform if the Bluetooth device is not a device corresponding to the first cloud platform, the sixth information including: the random device address or the first field;

[0416] The sixth information is used by the second cloud platform to determine authentication information, and the second cloud platform corresponds to the Bluetooth device.

[0417] In some embodiments, the first field includes: a URI Hash field.

[0418] In some embodiments, the fifth information further includes: a CID of the Bluetooth device corresponding to the second cloud platform.

[0419] In some embodiments, the random device address remains unchanged in a single network configuration process; the random number remains unchanged in a single network configuration process.

[0420] In order to implement the Bluetooth device access authentication method provided in the embodiment of the present application, the embodiment of the present application also provides a second cloud platform, the optional component structure of the second cloud platform 2000 is as follows: Figure 22 Shown, including:

[0421] The fifth receiving unit 2001 is configured to obtain sixth information, where the sixth information includes: a random device address of the Bluetooth device, or a first field carrying a random number;

[0422] The fifth processing unit 2002 is configured to perform network configuration access authentication on the Bluetooth device based on the sixth information.

[0423] In some embodiments, the fifth processing unit 2002 is configured to perform network configuration access authentication on the Bluetooth device based on a number of times the random device address is used if the sixth information includes the random device address of the Bluetooth device.

[0424] In some embodiments, the fifth processing unit 2002 is configured to determine that the Bluetooth device authentication has failed if the number of times the random device address has been used is greater than or equal to once;

[0425] Alternatively, if the number of times the random device address is used is zero and the UUID of the Bluetooth device is legal, authentication information is determined based on the random device address, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0426] In some embodiments, the fifth processing unit 2002 is configured to perform network configuration access authentication on the Bluetooth device based on the number of times the value of the first field is used if the fifth information includes the first field.

[0427] In some embodiments, if the value of the first field is used a number of times greater than or equal to once, then it is determined that the Bluetooth device authentication has failed;

[0428] Alternatively, if the number of times the value of the first field is used is zero and the UUID of the Bluetooth device is legal, authentication information is determined based on the first field, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

[0429] In some embodiments, the first field includes: a URI Hash field.

[0430] In some embodiments, the random device address remains unchanged in a single network configuration process; the random number remains unchanged in a single network configuration process.

[0431] An embodiment of the present application provides a Bluetooth device, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is configured to execute the steps of the Bluetooth device access authentication method executed by the above-mentioned Bluetooth device when running the computer program.

[0432] An embodiment of the present application provides a network adapter, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is configured to execute the steps of the Bluetooth device access authentication method executed by the above-mentioned network adapter when running the computer program.

[0433] An embodiment of the present application provides a cloud server, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is configured to execute the steps of the Bluetooth device access authentication method executed by the above-mentioned cloud server when running the computer program.

[0434] An embodiment of the present application provides a first cloud platform gateway, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is used to execute the steps of the Bluetooth device access authentication method executed by the above-mentioned first cloud platform gateway when running the computer program.

[0435] An embodiment of the present application provides a first cloud platform, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is used to execute the steps of the Bluetooth device access authentication method executed by the above-mentioned first cloud platform when running the computer program.

[0436] An embodiment of the present application provides a second cloud platform, including a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is used to execute the steps of the Bluetooth device access authentication method executed by the above-mentioned second cloud platform when running the computer program.

[0437] An embodiment of the present application also provides a chip, including: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned Bluetooth device access authentication method.

[0438] An embodiment of the present application further provides a storage medium storing an executable program, which, when executed by a processor, implements the above-mentioned Bluetooth device access authentication method.

[0439] An embodiment of the present application also provides a computer program product, including computer program instructions, which enable a computer to execute the above-mentioned Bluetooth device access authentication method.

[0440] An embodiment of the present application also provides a computer program, which enables a computer to execute the above-mentioned Bluetooth device access authentication method.

[0441] Figure 23 This is a schematic diagram of the hardware composition structure of the electronic device (Bluetooth device, network adapter, or cloud server, or first cloud platform gateway, or first cloud platform, or second cloud platform) of the embodiment of the present application. The electronic device 700 includes: at least one processor 701, a memory 702 and at least one network interface 704. The various components in the electronic device 700 are coupled together through a bus system 705. It can be understood that the bus system 705 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 705 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, Figure 23 Various buses are labeled as bus system 705.

[0442] It is understood that the memory 702 can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disk, or compact disc read-only memory (CD-ROM); the magnetic surface memory can be a magnetic disk or a magnetic tape. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM). The memory 702 described in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

[0443] The memory 702 in the embodiment of the present application is used to store various types of data to support the operation of the electronic device 700. Examples of such data include any computer program for operating on the electronic device 700, such as the application 7022. The program for implementing the method of the embodiment of the present application may be included in the application 7022.

[0444] The methods disclosed in the above embodiments of the present application can be applied to the processor 701 or implemented by the processor 701. The processor 701 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the hardware integrated logic circuit in the processor 701 or by instructions in the form of software. The above processor 701 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 701 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 702. The processor 701 reads the information in the memory 702 and completes the steps of the above method in combination with its hardware.

[0445] In an exemplary embodiment, the electronic device 700 can be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), FPGAs, general-purpose processors, controllers, MCUs, MPUs, or other electronic components to perform the aforementioned method.

[0446] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0447] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0448] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0449] It should be understood that the terms "system" and "network" are often used interchangeably in this application. The term "and / or" in this application simply describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this application generally indicates that the associated objects are in an "or" relationship.

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

Claims

1. A method for authenticating access to a Bluetooth device, the method comprising: The Bluetooth device determines first information, where the first information includes: a random device address or a random number of the Bluetooth device; the random device address or the random number is regenerated by the Bluetooth device in each network configuration cycle; The Bluetooth device determines authentication information based on the first information, where the authentication information is used for access authentication of the Bluetooth device for network configuration; The method further comprises: The Bluetooth device sends a broadcast message, the broadcast message carries the random device address, or the first field of the broadcast message carries the random number; the first field is a uniform resource identifier hash URI Hash field filled with the random number; the number of times the random device address is used is used to perform access authentication for network configuration of the Bluetooth device; or, the number of times the value of the first field is used is used to perform access authentication for network configuration of the Bluetooth device.

2. The method according to claim 1, wherein The random device address remains unchanged during a single network configuration process; The random number remains unchanged during a single network configuration process.

3. A method for Bluetooth device access authentication, the method comprising: The network provisioner obtains second information, where the second information includes: a random device address of the Bluetooth device, or a first field carrying a random number; the random device address or the random number is regenerated by the Bluetooth device in each network provisioning cycle; The second information is used to determine authentication information, and the authentication information is used for access authentication of the Bluetooth device for network configuration; The method further comprises: The network provisioner receives a broadcast message, the broadcast message carries the random device address, or the first field of the broadcast message carries the random number; the first field is a uniform resource identifier hash URI Hash field filled with the random number; the number of times the random device address is used is used to perform access authentication for network provisioning of the Bluetooth device; or, the number of times the value of the first field is used is used to perform access authentication for network provisioning of the Bluetooth device.

4. The method according to claim 3, wherein: The method further comprises: The network provisioner performs network provisioning access authentication on the Bluetooth device based on the random device address.

5. The method according to claim 4, wherein The network provisioner performs access authentication for the Bluetooth device based on the random device address, including: The network provisioner performs network provisioning access authentication on the Bluetooth device based on the number of times the random device address is used.

6. The method according to claim 5, wherein: The network provisioner performs network provisioning access authentication on the Bluetooth device based on the number of times the random device address is used, including: If the random device address is used more than or equal to once, the network adapter determines that the Bluetooth device authentication has failed; Alternatively, if the number of times the random device address has been used is zero and the universal unique identifier (UUID) of the Bluetooth device is legal, the network provisioner determines the authentication information based on the random device address.

7. The method according to claim 3, wherein: The method further comprises: The network provisioner performs network provisioning access authentication on the Bluetooth device based on the first field.

8. The method according to claim 7, wherein: The network provisioner performing network provisioning access authentication on the Bluetooth device based on the first field includes: The network provisioner performs network provisioning access authentication on the Bluetooth device based on the number of times the value of the first field is used.

9. The method according to claim 8, wherein The network provisioner performing network provisioning access authentication on the Bluetooth device based on the number of times the value of the first field is used includes: If the number of times the value of the first field is used is greater than or equal to once, the network provisioner determines that the Bluetooth device authentication has failed; Alternatively, if the number of times the value of the first field is used is zero and the universal unique identifier UUID of the Bluetooth device is legal, the network provisioner determines the authentication information based on the first field.

10. The method according to claim 3, wherein: The method further comprises: The network distributor sends third information to the cloud server, where the third information includes: the random device address or the first field; The third information is used by the cloud server to perform access authentication for the Bluetooth device during network configuration.

11. The method according to any one of claims 3 to 10, wherein: The random device address remains unchanged during a single network configuration process; The random number remains unchanged during a single network configuration process.

12. A method for Bluetooth device access authentication, the method comprising: The cloud server obtains third information, where the third information includes: a random device address of the Bluetooth device, or a first field carrying a random number; the random device address or the random number is regenerated by the Bluetooth device in each network configuration cycle; The cloud server performs access authentication for the Bluetooth device to the network configuration based on the third information; the first field is a uniform resource identifier hash URI Hash field filled with the random number; the number of times the random device address is used is used to perform access authentication for the Bluetooth device to the network configuration; or, the number of times the value of the first field is used is used to perform access authentication for the Bluetooth device to the network configuration.

13. The method according to claim 12, wherein: The cloud server performing network access authentication on the Bluetooth device based on the third information includes: If the third information includes the random device address of the Bluetooth device, the cloud server performs network configuration access authentication on the Bluetooth device based on the number of times the random device address is used.

14. The method according to claim 13, wherein: The cloud server performing network access authentication on the Bluetooth device based on the number of times the random device address is used includes: If the random device address is used more than or equal to once, the cloud server confirms that the Bluetooth device authentication has failed; Alternatively, if the number of times the random device address is used is zero and the UUID of the Bluetooth device is legal, the cloud server determines authentication information based on the random device address, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

15. The method according to claim 12, wherein: The cloud server performing network access authentication on the Bluetooth device based on the third information includes: If the third information includes the first field, the cloud server performs network configuration access authentication on the Bluetooth device based on the number of times the value of the first field is used.

16. The method according to claim 15, wherein The cloud server performing network configuration access authentication on the Bluetooth device based on the number of times the value of the first field is used includes: If the number of times the value of the first field is used is greater than or equal to once, the cloud server confirms that the Bluetooth device authentication has failed; Alternatively, if the number of times the value of the first field is used is zero and the UUID of the Bluetooth device is legal, the cloud server determines authentication information based on the first field, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

17. The method according to any one of claims 12 to 16, wherein: The random device address remains unchanged during a single network configuration process; The random number remains unchanged during a single network configuration process.

18. A method for access authentication of a Bluetooth device, the method comprising: The first cloud platform gateway obtains fourth information, where the fourth information includes: a random device address of the Bluetooth device, or a first field carrying a random number; the random device address or the random number is regenerated by the Bluetooth device in each network configuration cycle; The fourth information is used to determine authentication information, and the authentication information is used for access authentication of the Bluetooth device for network configuration; The method further comprises: The first cloud platform gateway receives a broadcast message, the broadcast message carries the random device address, or the first field in the broadcast message carries the random number; the first field is a uniform resource identifier hash URI Hash field filled with the random number; the number of times the random device address is used is used to perform access authentication for the Bluetooth device network configuration; or, the number of times the value of the first field is used is used to perform access authentication for the Bluetooth device network configuration.

19. The method according to claim 18, wherein The method further comprises: The first cloud platform gateway sends the random device address to the first cloud platform, and the first cloud platform gateway corresponds to the first cloud platform.

20. The method according to claim 18, wherein The method further comprises: The first cloud platform gateway sends the first field to the first cloud platform, and the first cloud platform gateway corresponds to the first cloud platform.

21. The method according to any one of claims 18 to 20, wherein: The fourth information also includes: The Bluetooth device corresponds to the company identifier CID of the second cloud platform.

22. The method according to claim 21, wherein The random device address remains unchanged during a single network configuration process; The random number remains unchanged during a single network configuration process.

23. A method for Bluetooth device access authentication, the method comprising: The first cloud platform obtains fifth information, the fifth information including: a random device address of the Bluetooth device, or a first field carrying a random number; the random device address or the random number is regenerated by the Bluetooth device in each network configuration cycle; The fifth information is used to determine the authentication information, and the authentication information is used for the access authentication of the Bluetooth device network configuration; the first field is the uniform resource identifier hash URIHash field filled with the random number; the number of times the random device address is used is used for the access authentication of the Bluetooth device network configuration; or, the number of times the value of the first field is used is used for the access authentication of the Bluetooth device network configuration.

24. The method according to claim 23, wherein If the Bluetooth device is not a device corresponding to the first cloud platform, the method further includes: The first cloud platform sends sixth information to the second cloud platform, where the sixth information includes: the random device address, or the first field; The sixth information is used by the second cloud platform to determine authentication information, and the second cloud platform corresponds to the Bluetooth device.

25. The method according to claim 23 or 24, wherein The fifth information also includes: The Bluetooth device corresponds to the company identifier CID of the second cloud platform.

26. The method according to claim 25, wherein The random device address remains unchanged during a single network configuration process; The random number remains unchanged during a single network configuration process.

27. A method for Bluetooth device access authentication, the method comprising: The second cloud platform obtains sixth information, the sixth information including: a random device address of the Bluetooth device, or a first field carrying a random number; the random device address or the random number is regenerated by the Bluetooth device in each network configuration cycle; The second cloud platform performs access authentication for the network configuration of the Bluetooth device based on the sixth information; the first field is a uniform resource identifier hash URIHash field filled with the random number; the number of times the random device address is used is used to perform access authentication for the network configuration of the Bluetooth device; or, the number of times the value of the first field is used is used to perform access authentication for the network configuration of the Bluetooth device.

28. The method according to claim 27, wherein The second cloud platform performing network configuration access authentication on the Bluetooth device based on the sixth information includes: If the sixth information includes a random device address of the Bluetooth device, the second cloud platform performs network configuration access authentication on the Bluetooth device based on the number of times the random device address is used.

29. The method according to claim 28, wherein The second cloud platform performing network configuration access authentication on the Bluetooth device based on the number of times the random device address is used includes: If the random device address is used more than or equal to once, the second cloud platform determines that the Bluetooth device authentication has failed; Alternatively, if the random device address is used a number of times and the UUID of the Bluetooth device is legal, the second cloud platform determines authentication information based on the random device address, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

30. The method of claim 27, wherein: The second cloud platform performing network configuration access authentication on the Bluetooth device based on the sixth information includes: If the sixth information includes the first field, the second cloud platform performs network configuration access authentication on the Bluetooth device based on the number of times the value of the first field is used.

31. The method according to claim 30, wherein The second cloud platform performing network configuration access authentication on the Bluetooth device based on the number of times the value of the first field is used includes: If the number of times the value of the first field is used is greater than or equal to once, the second cloud platform determines that the Bluetooth device authentication has failed; Alternatively, if the number of times the value of the first field is used is zero and the UUID of the Bluetooth device is legal, the second cloud platform determines authentication information based on the first field, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

32. The method according to any one of claims 27 to 31, wherein The random device address remains unchanged during a single network configuration process; The random number remains unchanged during a single network configuration process.

33. A Bluetooth device, comprising: A first processing unit is configured to determine first information, where the first information includes: a random device address or a random number of a Bluetooth device; the random device address or the random number is regenerated by the Bluetooth device in each network configuration cycle; The first processing unit is configured to determine authentication information based on the first information, where the authentication information is used for access authentication of the Bluetooth device for network configuration; A first sending unit is configured to send a broadcast message, wherein the broadcast message carries the random device address, or the first field of the broadcast message carries the random number; the first field is a uniform resource identifier hash URI Hash field filled with the random number; the number of times the random device address is used is used to perform access authentication for network configuration of the Bluetooth device; or the number of times the value of the first field is used is used to perform access authentication for network configuration of the Bluetooth device.

34. The Bluetooth device according to claim 33, wherein The random device address remains unchanged during a single network configuration process; The random number remains unchanged during a single network configuration process.

35. A network distributor, comprising: A first receiving unit is configured to obtain second information, where the second information includes: a random device address of a Bluetooth device, or a first field carrying a random number; the random device address or the random number is regenerated by the Bluetooth device in each network configuration cycle; The second information is used to determine authentication information, and the authentication information is used for access authentication of the Bluetooth device for network configuration; The first receiving unit is configured to receive a broadcast message, the broadcast message carries the random device address, or the first field of the broadcast message carries the random number; the first field is a uniform resource identifier hash URI Hash field filled with the random number; the number of times the random device address is used is used to perform access authentication for the Bluetooth device network configuration; or, the number of times the value of the first field is used is used to perform access authentication for the Bluetooth device network configuration.

36. The network distributor according to claim 35, wherein: The network distributor also includes: The second processing unit is configured to perform access authentication of the Bluetooth device to the network configuration based on the random device address.

37. The network distributor according to claim 36, wherein: The second processing unit is configured to perform access authentication of the Bluetooth device to the network configuration based on the number of times the random device address is used.

38. The network distributor according to claim 37, wherein: The second processing unit is configured to determine that the Bluetooth device authentication has failed if the random device address has been used more than or equal to once; Alternatively, if the number of times the random device address has been used is zero and the universal unique identifier (UUID) of the Bluetooth device is legal, the authentication information is determined based on the random device address.

39. The network distributor according to claim 35, wherein: The network distributor also includes: The third processing unit is configured to perform access authentication of the Bluetooth device to the network configuration based on the first field.

40. The network distributor according to claim 39, wherein: The third processing unit is configured to perform access authentication of the Bluetooth device to the network configuration based on the number of times the value of the first field is used.

41. The network distributor according to claim 40, wherein: The third processing unit is configured to determine that the Bluetooth device authentication fails if the number of times the value of the first field is used is greater than or equal to once; Alternatively, if the number of times the value of the first field is used is zero and the universal unique identifier UUID of the Bluetooth device is legal, the authentication information is determined based on the first field.

42. The network distributor according to claim 35, wherein: The network distributor also includes: a third sending unit, configured to send third information to the cloud server, the third information including: the random device address, or the first field; The third information is used by the cloud server to perform access authentication for the Bluetooth device during network configuration.

43. The network distributor according to any one of claims 35 to 42, wherein: The random device address remains unchanged during a single network configuration process; The random number remains unchanged during a single network configuration process.

44. A cloud server, comprising: The second receiving unit is configured to obtain third information, where the third information includes: a random device address of the Bluetooth device, or a first field carrying a random number; the random device address or the random number is regenerated by the Bluetooth device in each network configuration cycle; A fourth processing unit is configured to perform access authentication for the Bluetooth device to the network configuration based on the third information; the first field is a uniform resource identifier hash URI Hash field filled with the random number; the number of times the random device address is used is used to perform access authentication for the Bluetooth device to the network configuration; or, the number of times the value of the first field is used is used to perform access authentication for the Bluetooth device to the network configuration.

45. The cloud server according to claim 44, wherein: If the third information includes the random device address of the Bluetooth device, the fourth processing unit is configured to perform network configuration access authentication on the Bluetooth device based on the number of times the random device address is used.

46. ​​The cloud server according to claim 45, wherein: If the random device address has been used more than or equal to once, the fourth processing unit is configured to confirm that the Bluetooth device authentication has failed; If the number of times the random device address is used is zero and the UUID of the Bluetooth device is legal, the fourth processing unit is configured to determine authentication information based on the random device address, where the authentication information is used for access authentication of the Bluetooth device for network configuration.

47. The cloud server according to claim 44, wherein: If the third information includes the first field, the fourth processing unit is configured to perform network configuration access authentication on the Bluetooth device based on the number of times the value of the first field is used.

48. The cloud server according to claim 47, wherein: If the number of times the value of the first field is used is greater than or equal to once, the fourth processing unit is configured to confirm that the Bluetooth device authentication fails; Alternatively, if the number of times the value of the first field is used is zero and the UUID of the Bluetooth device is legal, the fourth processing unit is configured to determine authentication information based on the first field, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

49. The cloud server according to any one of claims 44 to 48, wherein: The random device address remains unchanged during a single network configuration process; The random number remains unchanged during a single network configuration process.

50. A first cloud platform gateway, comprising: A third receiving unit is configured to obtain fourth information, where the fourth information includes: a random device address of the Bluetooth device, or a first field carrying a random number; the random device address or the random number is regenerated by the Bluetooth device in each network configuration cycle; The fourth information is used to determine authentication information, and the authentication information is used for access authentication of the Bluetooth device for network configuration; The third receiving unit is configured to receive a broadcast message, the broadcast message carries the random device address, or the first field of the broadcast message carries the random number; the first field is a uniform resource identifier hash URI Hash field filled with the random number; the number of times the random device address is used is used to perform access authentication for the Bluetooth device network configuration; or, the number of times the value of the first field is used is used to perform access authentication for the Bluetooth device network configuration.

51. The first cloud platform gateway according to claim 50, wherein: The first cloud platform gateway further includes: The fourth sending unit is configured to send the random device address to the first cloud platform, and the first cloud platform gateway corresponds to the first cloud platform.

52. The first cloud platform gateway according to claim 50, wherein: The first cloud platform gateway further includes: The fifth sending unit is configured to send the first field to the first cloud platform, and the first cloud platform gateway corresponds to the first cloud platform.

53. The first cloud platform gateway according to any one of claims 50 to 52, wherein: The fourth information also includes: The Bluetooth device corresponds to the company identifier CID of the second cloud platform.

54. The first cloud platform gateway according to claim 53, wherein: The random device address remains unchanged during a single network configuration process; The random number remains unchanged during a single network configuration process.

55. A first cloud platform, comprising: a fourth receiving unit configured to obtain fifth information, the fifth information comprising: a random device address of the Bluetooth device, or a first field carrying a random number; the random device address or the random number is regenerated by the Bluetooth device in each network configuration cycle; The fifth information is used to determine the authentication information, and the authentication information is used for the access authentication of the Bluetooth device network configuration; the first field is the uniform resource identifier hash URIHash field filled with the random number; the number of times the random device address is used is used for the access authentication of the Bluetooth device network configuration; or, the number of times the value of the first field is used is used for the access authentication of the Bluetooth device network configuration.

56. The first cloud platform according to claim 55, wherein: The first cloud platform also includes: a sixth sending unit, configured to send sixth information to the second cloud platform if the Bluetooth device is not a device corresponding to the first cloud platform, the sixth information including: the random device address or the first field; The sixth information is used by the second cloud platform to determine authentication information, and the second cloud platform corresponds to the Bluetooth device.

57. The first cloud platform according to claim 55 or 56, wherein: The fifth information also includes: The Bluetooth device corresponds to the company identifier CID of the second cloud platform.

58. The first cloud platform according to claim 57, wherein: The random device address remains unchanged during a single network configuration process; The random number remains unchanged during a single network configuration process.

59. A second cloud platform, comprising: a fifth receiving unit configured to obtain sixth information, the sixth information comprising: a random device address of the Bluetooth device, or a first field carrying a random number; the random device address or the random number is regenerated by the Bluetooth device in each network configuration cycle; A fifth processing unit is configured to perform access authentication for the Bluetooth device to the network configuration based on the sixth information; the first field is a uniform resource identifier hash URI Hash field filled with the random number; the number of times the random device address is used is used to perform access authentication for the Bluetooth device to the network configuration; or, the number of times the value of the first field is used is used to perform access authentication for the Bluetooth device to the network configuration.

60. The second cloud platform according to claim 59, wherein: The fifth processing unit is configured to, if the sixth information includes a random device address of the Bluetooth device, perform access authentication for the Bluetooth device to the network configuration based on a number of times the random device address is used.

61. The second cloud platform according to claim 60, wherein: The fifth processing unit is configured to determine that the Bluetooth device authentication fails if the random device address is used more than or equal to once; Alternatively, if the number of times the random device address is used is zero and the UUID of the Bluetooth device is legal, authentication information is determined based on the random device address, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

62. The second cloud platform according to claim 59, wherein: The fifth processing unit is configured to perform access authentication of the Bluetooth device to the network configuration based on the number of times the value of the first field is used if the fifth information includes the first field.

63. The second cloud platform according to claim 62, wherein: If the number of times the value of the first field is used is greater than or equal to once, it is determined that the Bluetooth device authentication has failed; Alternatively, if the number of times the value of the first field is used is zero and the UUID of the Bluetooth device is legal, authentication information is determined based on the first field, and the authentication information is used for access authentication of the Bluetooth device for network configuration.

64. The second cloud platform according to any one of claims 59 to 63, wherein: The random device address remains unchanged during a single network configuration process; The random number remains unchanged during a single network configuration process.

65. A Bluetooth device comprising a processor and a memory for storing a computer program capable of running on the processor, wherein: When the processor is used to run the computer program, it executes the steps of the Bluetooth device access authentication method according to claim 1 or 2.

66. A network distributor comprising a processor and a memory for storing a computer program capable of running on the processor, wherein: When the processor is used to run the computer program, it executes the steps of the Bluetooth device access authentication method according to any one of claims 3 to 11.

67. A cloud server comprising a processor and a memory for storing a computer program capable of running on the processor, wherein: When the processor is used to run the computer program, it executes the steps of the Bluetooth device access authentication method according to any one of claims 12 to 17.

68. A first cloud platform gateway, comprising a processor and a memory for storing a computer program capable of running on the processor, wherein: When the processor is used to run the computer program, it executes the steps of the Bluetooth device access authentication method according to any one of claims 18 to 22.

69. A first cloud platform comprises a processor and a memory for storing a computer program capable of running on the processor, wherein: When the processor is used to run the computer program, it executes the steps of the Bluetooth device access authentication method according to any one of claims 23 to 26.

70. A second cloud platform comprising a processor and a memory for storing a computer program capable of running on the processor, wherein: When the processor is used to run the computer program, it executes the steps of the Bluetooth device access authentication method according to any one of claims 27 to 32.

71. A storage medium storing an executable program, wherein when the executable program is executed by a processor, the Bluetooth device access authentication method according to claim 1 or 2 is implemented.

72. A storage medium storing an executable program, wherein when the executable program is executed by a processor, the Bluetooth device access authentication method according to any one of claims 3 to 11 is implemented.

73. A storage medium storing an executable program, wherein when the executable program is executed by a processor, the Bluetooth device access authentication method described in any one of claims 12 to 17 is implemented.

74. A storage medium storing an executable program, wherein when the executable program is executed by a processor, the Bluetooth device access authentication method described in any one of claims 18 to 22 is implemented.

75. A storage medium storing an executable program, wherein when the executable program is executed by a processor, the Bluetooth device access authentication method described in any one of claims 23 to 26 is implemented.

76. A storage medium storing an executable program, wherein when the executable program is executed by a processor, the Bluetooth device access authentication method described in any one of claims 27 to 32 is implemented.

77. A computer program product, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the Bluetooth device access authentication method according to claim 1 or 2.

78. A computer program product, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the Bluetooth device access authentication method according to any one of claims 3 to 11.

79. A computer program product, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the Bluetooth device access authentication method according to any one of claims 12 to 17.

80. A computer program product, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the Bluetooth device access authentication method according to any one of claims 18 to 22.

81. A computer program product, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the Bluetooth device access authentication method according to any one of claims 23 to 26.

82. A computer program product, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the Bluetooth device access authentication method according to any one of claims 27 to 32.

83. A chip comprising: The processor is configured to call and run a computer program from a memory, so that a device equipped with the chip executes the Bluetooth device access authentication method according to claim 1 or 2.

84. A chip comprising: The processor is configured to call and run a computer program from a memory, so that a device equipped with the chip executes the Bluetooth device access authentication method according to any one of claims 3 to 11.

85. A chip, comprising: The processor is configured to call and run a computer program from a memory, so that a device equipped with the chip executes the Bluetooth device access authentication method according to any one of claims 12 to 17.

86. A chip comprising: The processor is configured to call and run a computer program from a memory, so that a device equipped with the chip executes the Bluetooth device access authentication method according to any one of claims 18 to 22.

87. A chip comprising: The processor is used to call and run a computer program from a memory so that the device equipped with the chip executes the Bluetooth device access authentication method as described in any one of claims 23 to 26.

88. A chip comprising: The processor is used to call and run a computer program from a memory so that the device equipped with the chip executes the Bluetooth device access authentication method as described in any one of claims 27 to 32.

Images