CN116158100A - Bluetooth equipment access authentication method, electronic equipment and storage medium - Google Patents

Bluetooth equipment access authentication method, electronic equipment and storage medium Download PDF

Info

Publication number
CN116158100A
CN116158100A CN202080102514.1A CN202080102514A CN116158100A CN 116158100 A CN116158100 A CN 116158100A CN 202080102514 A CN202080102514 A CN 202080102514A CN 116158100 A CN116158100 A CN 116158100A
Authority
CN
China
Prior art keywords
bluetooth device
random
information
bluetooth
cloud platform
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202080102514.1A
Other languages
Chinese (zh)
Inventor
董建利
罗朝明
张军
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of CN116158100A publication Critical patent/CN116158100A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The application discloses a Bluetooth equipment access authentication method, which comprises the following steps: the Bluetooth device determines first information, the first information comprising: a random device address or random number of the bluetooth device; and the Bluetooth equipment determines authentication information based on the first information, wherein the authentication information is used for access authentication of the Bluetooth equipment distribution network. The application also discloses another Bluetooth equipment access authentication method, electronic equipment and storage medium.

Description

Bluetooth equipment access authentication method, electronic equipment and storage medium Technical Field
The present disclosure relates to the field of wireless communications technologies, and in particular, to a bluetooth device access authentication method, an electronic device, and a storage medium.
Background
With the increasing perfection of bluetooth Mesh functions and the increasing wide application, the network distribution requirements of bluetooth devices are increasing, and in the network distribution process of bluetooth devices, it is always a goal pursued by bluetooth network technology how to perform access authentication on bluetooth devices and improve the security of the access authentication of bluetooth devices.
Disclosure of Invention
The embodiment of the application provides a Bluetooth device access authentication method, electronic equipment and a storage medium, which can improve the security of Bluetooth device access authentication.
In a first aspect, an embodiment of the present application provides a bluetooth device access authentication method, including: the Bluetooth device determines first information, the first information comprising: a random device address or random number of the bluetooth device;
and the Bluetooth equipment determines authentication information based on the first information, wherein the authentication information is used for access authentication of the Bluetooth equipment distribution network.
In a second aspect, an embodiment of the present application provides a bluetooth device access authentication method, including: the network distributor acquires second information, wherein the second information comprises: a random device address of the bluetooth device, or a first field carrying a random number;
the second information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
In a third aspect, an embodiment of the present application provides a bluetooth device access authentication method, including: the cloud server acquires third information, wherein the third information comprises: a random device address of the bluetooth device, or a first field carrying a random number;
and the cloud server executes access authentication of the distribution network to the Bluetooth equipment based on the third information.
In a fourth aspect, an embodiment of the present application provides a bluetooth device access authentication method, including: the first cloud platform gateway obtains fourth information, wherein the fourth information comprises: a random device address of the bluetooth device, or a first field carrying a random number;
The fourth information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
In a fifth aspect, an embodiment of the present application provides a bluetooth device access authentication method, including: the first cloud platform obtains fifth information, wherein the fifth information comprises: a random device address of the bluetooth device, or a first field carrying a random number;
the fifth information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
In a sixth aspect, an embodiment of the present application provides a bluetooth device access authentication method, including:
the second cloud platform obtains sixth information, wherein the sixth information comprises: a random device address of the bluetooth device, or a first field carrying a random number;
and the second cloud platform executes access authentication of the distribution network for the Bluetooth equipment based on the sixth information.
In a seventh aspect, embodiments of the present application provide a bluetooth device, including: .
The embodiment of the application provides a cloud platform, the cloud platform includes:
a first processing unit configured to determine first information, the first information including: a random device address or random number of the bluetooth device;
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 distribution network.
In an eighth aspect, an embodiment of the present application provides a network device, where the network device includes:
a first receiving unit configured to acquire second information including: a random device address of the bluetooth device, or a first field carrying a random number;
the second information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
In a ninth aspect, embodiments of the present application provide a cloud server, where the cloud server includes:
a second receiving unit configured to acquire third information including: a random device address of the bluetooth device, or a first field carrying a random number;
and a fourth processing unit configured to perform access authentication of a distribution network for the bluetooth device based on the third information.
In a tenth aspect, embodiments of the present application provide a first cloud platform gateway, where the first cloud platform gateway includes:
a third receiving unit configured to acquire fourth information including: a random device address of the bluetooth device, or a first field carrying a random number;
The fourth information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
In an eleventh aspect, embodiments of the present application provide a first cloud platform, where the first cloud platform includes:
a fourth receiving unit configured to acquire fifth information including: a random device address of the bluetooth device, or a first field carrying a random number;
the fifth information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
In a twelfth aspect, embodiments of the present application provide a second cloud platform, where the second cloud platform includes:
a fifth receiving unit configured to acquire sixth information including: a random device address of the bluetooth device, or a first field carrying a random number;
and a fifth processing unit configured to perform access authentication of a distribution network for the bluetooth device based on the sixth information.
In a thirteenth aspect, an embodiment of the present application provides a bluetooth device, including a processor and a memory configured to store a computer program capable of running on the processor, where the processor is configured to execute, when running the computer program, the steps of the bluetooth device access authentication method executed by the bluetooth device.
In a fourteenth aspect, an embodiment of the present application provides a network distributor, including a processor and a memory for storing a computer program capable of running on the processor, where the processor is configured to execute the steps of the bluetooth device access authentication method executed by the network distributor when running the computer program.
In a fifteenth aspect, an embodiment of the present application provides a cloud server, including a processor and a memory for storing a computer program capable of running on the processor, where the processor is configured to execute, when running the computer program, the steps of the bluetooth device access authentication method executed by the cloud server.
In a sixteenth aspect, an embodiment of the present application provides a first cloud platform gateway, including a processor and a memory configured to store a computer program capable of running on the processor, where the processor is configured to execute, when running the computer program, a step of a bluetooth device access authentication method executed by the first cloud platform gateway.
In a seventeenth aspect, an embodiment of the present application provides a first cloud platform, including a processor and a memory configured to store a computer program capable of running on the processor, where the processor is configured to execute, when running the computer program, a step of a bluetooth device access authentication method executed by the first cloud platform.
In an eighteenth aspect, an embodiment of the present application provides a second cloud platform, including a processor and a memory configured to store a computer program capable of running on the processor, where the processor is configured to execute, when running the computer program, a step of a bluetooth device access authentication method executed by the second cloud platform.
In a nineteenth aspect, an embodiment of the present application provides a chip, including: and the processor is used for calling and running the computer program from the memory, so that the device provided with the chip executes the Bluetooth device access authentication method.
In a twentieth aspect, an embodiment of the present application provides a storage medium storing an executable program, where the executable program when executed by a processor implements the above-mentioned bluetooth device access authentication method.
In a twenty-first aspect, embodiments of the present application provide a computer program product comprising computer program instructions for causing a computer to perform the above-described bluetooth device access authentication method.
In a twenty-second aspect, an embodiment of the present application provides a computer program, where the computer program causes a computer to execute the above bluetooth device access authentication method.
The Bluetooth equipment access authentication method, the electronic equipment and the storage medium provided by the embodiment of the application comprise the following steps: the Bluetooth device determines first information, the first information comprising: a random device address or random number of the bluetooth device; and the Bluetooth equipment determines authentication information based on the first information, wherein the authentication information is used for access authentication of the Bluetooth equipment distribution network. Therefore, because the random device address or the random number is dynamically generated by the Bluetooth device in each distribution network period, compared with the authentication information determined based on the constant parameter, the authentication information determined based on the random device address or the random number dynamically generated in each distribution network period improves the security of the Bluetooth device access authentication, and the Bluetooth device is prevented from being distributed and controlled by other distribution network devices due to the constant parameter leakage; meanwhile, the Bluetooth equipment access authentication method provided by the embodiment of the application can also ensure the convenience of Bluetooth equipment access authentication.
Drawings
FIG. 1 is a schematic flow chart of an embodiment of the present application for outputting OOB authentication;
FIG. 2 is a flow chart of the input OOB authentication according to an embodiment of the present application;
FIG. 3 is a flow chart of static OOB or OOB-free authentication according to an embodiment of the present application;
Fig. 4 is a schematic diagram of an alternative processing flow of a bluetooth device access authentication method applied to a bluetooth device according to an embodiment of the present application;
fig. 5 is a schematic diagram of a format of a broadcast message without network allocation according to an embodiment of the present application;
fig. 6 is a schematic diagram of an alternative processing flow of a bluetooth device access authentication method applied to a network distributor according to an embodiment of the present application;
fig. 7 is a schematic diagram of an alternative processing flow of a bluetooth device access authentication method applied to a cloud server according to an embodiment of the present application;
fig. 8 is a schematic diagram of an alternative processing flow of a bluetooth device access authentication method applied to a first cloud platform gateway according to an embodiment of the present application;
fig. 9 is a schematic diagram of an optional processing flow of a bluetooth device access authentication method applied to a first cloud platform according to an embodiment of the present application;
fig. 10 is a schematic diagram of an alternative process flow of a bluetooth device access authentication method applied to a second cloud platform according to an embodiment of the present application;
fig. 11 is a schematic diagram of a first optional detailed processing flow of a bluetooth device access authentication method according to an embodiment of the present application;
fig. 12 is a schematic diagram of a second alternative detailed processing flow of the bluetooth device access authentication method according to the embodiment of the present application;
Fig. 13 is a schematic diagram of a third alternative detailed processing flow of a bluetooth device access authentication method according to an embodiment of the present application;
fig. 14 is a schematic diagram of a fourth optional detailed processing flow of a bluetooth device access authentication method according to an embodiment of the present application;
fig. 15 is a schematic diagram of a fifth optional detailed processing flow of a bluetooth device access authentication method according to an embodiment of the present application;
fig. 16 is a schematic diagram of a sixth alternative detailed processing flow of a bluetooth device access authentication method according to an embodiment of the present application;
fig. 17 is a schematic diagram of an alternative composition structure of a bluetooth device according to an embodiment of the present application;
fig. 18 is a schematic diagram of an alternative composition structure of a network distributor according to an embodiment of the present application;
fig. 19 is a schematic diagram of an alternative composition structure of a cloud server according to an embodiment of the present application;
fig. 20 is a schematic diagram of an optional composition structure of a first cloud platform gateway according to an embodiment of the present application;
fig. 21 is a schematic diagram of an alternative composition structure of a first cloud platform according to an embodiment of the present application;
fig. 22 is a schematic diagram of an alternative composition structure of a second cloud platform according to an embodiment of the present application;
fig. 23 is a schematic diagram of a hardware composition structure of an electronic device according to an embodiment of the present application.
Detailed Description
For a more complete understanding of the nature and the technical content of the embodiments of the present application, reference should be made to the following detailed description of embodiments of the present application in connection with the accompanying drawings, which are provided for purposes of illustration only and are not intended to limit the embodiments of the present application.
Before explaining the embodiments of the present application, the related contents will be briefly explained.
Bluetooth Mesh (wireless Mesh network): a mesh device network constructed based on a low-power Bluetooth technology can realize many-to-many Bluetooth device communication.
Gateway: the Bluetooth Mesh distribution network equipment is responsible for configuring equipment accessed to the Bluetooth Mesh network.
Bluetooth device: the blue tooth Mesh device to be matched with the network needs to be added into a blue tooth Mesh network through a blue tooth Mesh distribution flow to form the blue tooth Mesh device in the blue tooth Mesh network.
Session key: the method is used for encrypting and decrypting the distribution network data in the Bluetooth Mesh distribution network flow.
Device key: after the network allocation of the Bluetooth Mesh device is successful, the subsequent configuration of the Bluetooth Mesh device is only known by the gateway and the Bluetooth Mesh device, and the gateway and the Bluetooth Mesh device are used for secure communication between the gateway and the Bluetooth Mesh device.
In the network configuration flow of the bluetooth device, access authentication needs to be performed on the bluetooth device, and the modes for performing access authentication on the bluetooth device include four Out of Band (OOB) authentication (authentication) modes: OOB free (No OOB), static out-of-band (Static OOB), input out-of-band (Input OOB), and Output out-of-band (Output OOB).
As shown in fig. 1, a bluetooth device that is not configured with a network selects a random number and outputs the random number in a manner compatible with the function of the random number. For example, if the unactivated configuration device is a light bulb, it can flash a specified number of times. If the device has an LCD screen, the random number may be displayed as a multi-bit value. The network distributor needs to input the observed numbers to authenticate the bluetooth device.
The flow chart of the OOB authentication is entered, as shown in fig. 2, the network distributor generates and displays a random number, and then prompts the user to take appropriate action to enter the random number into the bluetooth device that is not connected. Taking the example of a light switch, the user can press a button several times within a certain time, and input a random number in this form.
The Static OOB or OOB-free authentication flow chart is shown in fig. 3, and in the case that neither the input out-of-band nor the output out-of-band is available, the network distributor and the bluetooth device without the network can adopt Static OOB authentication or No OOB authentication: static OOB information is adopted; or static OOB information is not available, it is directly replaced by a value of 0. In this case, each of the network distributor and the bluetooth device not connected to the network generates a random number, and then performs a check confirmation value operation.
The authentication formula of the Bluetooth device is as follows:
ConfirmationDevice=AES-CMACconfirmationkey(RandomDevice||AuthValue)
the authentication formula of the network distributor is as follows:
ConfirmationProvisioner=AES-CMACconfirmationkey(RandomProvisioner||AuthValue)
the AES-CMAC is an encryption algorithm, confirmatory is a secret key, (random provider I AuthValue) is a plaintext, confirmatory provider is a generated ciphertext, authValue is OOB authentication information, the network distributor and the Bluetooth device have the same OOB authentication information, and the network distributor and the Bluetooth device complete network distribution authentication of the Bluetooth device by exchanging the calculated confirmations and provisioningRandom respectively.
In the actual product form, the authentication mode of Output OOB/Input OOB requires that the Bluetooth equipment has the capability of Input or Output, and manual participation is required in the authentication process; therefore, due to the factors of Bluetooth equipment cost, network distribution convenience and the like, the fresh equipment adopts an Output OOB/Input OOB authentication mode, and the No OOB authentication mode has No security; most devices are authenticated by way of Static OOB authentication.
In the related art, most of OOB authentication information required by the Static OOB authentication mode of the Bluetooth device is pre-generated and directly burnt into the device when leaving the factory, static OOB authentication information is the same when the network is allocated each time, the security of the network allocation process cannot reach the optimum, and when the Static OOB authentication information is revealed, other network allocation devices can allocate the network to the Bluetooth device to achieve the purpose of control.
If the OOB authentication information is revealed, an attacker can impersonate the legal device to try to join the Bluetooth network, and as the attacker has the revealed OOB authentication information and the Beacon information broadcasted by the legal device is easy to copy, the attacker can completely join the network through the authentication process, so that the network key (NetKey) and the application key (AppKey) of the network are revealed, and a great security hole is caused.
The technical solution of the embodiment of the application can be applied to various communication systems, for example: global system for mobile communications (global system of mobile communication, GSM), code division multiple access (code division multiple access, CDMA) system, wideband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (general packet radio service, GPRS), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, long term evolution advanced (advanced long term evolution, LTE-a) system, new Radio (NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed band, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed band, universal mobile communication system (universal mobile telecommunication system, UMTS), universal internet microwave access (worldwide interoperability for microwave access, wiMAX) communication system, wireless local area network (wireless local area networks, WLAN), wireless fidelity (wireless fidelity, wiFi), next generation communication system or other communication system, etc.
The system architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided in the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of the new service scenario, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.
The network device involved in the embodiments of the present application may be a common base station (such as a NodeB or eNB or gNB), a new radio controller (new radio controller, NR controller), a centralized network element (centralized unit), a new radio base station, a remote radio module, a micro base station, a relay, a distributed network element (distributed unit), a receiving point (transmission reception point, TRP), a transmission point (transmission point, TP), or any other device. The embodiment of the application does not limit the specific technology and the specific device form adopted by the network device. For convenience of description, in all embodiments of the present application, the above-mentioned apparatus for providing a wireless communication function for a terminal device is collectively referred to as a network device.
In the embodiment of the present application, the terminal device may be any terminal, for example, the terminal device may be a user device 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 (mobile terminal), a terminal (terminal), etc., which may communicate with one or more core networks via a radio access network (radio access network, RAN), e.g., the terminal device may be a mobile phone (or "cellular" phone), a computer with a mobile terminal, etc., e.g., the terminal device may also be a portable, pocket, hand-held, computer-built-in or car-mounted mobile device, which exchanges voice and/or data with the radio access network. The embodiments of the present application are not specifically limited.
Alternatively, the network devices and terminal devices may be deployed on land, including indoors or outdoors, hand-held or vehicle-mounted; the device can be deployed on the water surface; but also on aerial planes, balloons and satellites. The embodiment of the application does not limit the application scene of the network equipment and the terminal equipment.
Optionally, communication between the network device and the terminal device and between the terminal device and the terminal device may be performed through a licensed spectrum (licensed spectrum), communication may be performed through an unlicensed spectrum (unlicensed spectrum), or communication may be performed through both the licensed spectrum and the unlicensed spectrum. Communication between the network device and the terminal device and between the terminal device and the terminal device may be performed through a frequency spectrum of 7 gigahertz (GHz) or less, may be performed through a frequency spectrum of 7GHz or more, and may be performed using a frequency spectrum of 7GHz or less and a frequency spectrum of 7GHz or more simultaneously. The embodiments of the present application do not limit the spectrum resources used between the network device and the terminal device.
Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, with the development of communication technology, the mobile communication system will support not only conventional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (machine to machine, M2M) communication, machine type communication (machine type communication, MTC), inter-vehicle (vehicle to vehicle, V2V) communication, and the like, to which the embodiments of the present application can also be applied.
An optional processing flow of the bluetooth device access authentication method applied to a bluetooth device provided in the embodiment of the present application, as shown in fig. 4, may include the following steps:
in step S201, the bluetooth device determines first information, where the first information includes: a random device address or a random number for the bluetooth device.
In some embodiments, the random device address or the random number of the bluetooth device may be regenerated by the bluetooth device in the state of waiting for the network to be configured based on the network configuration.
In some embodiments, the random device address may be a random dedicated device address.
Step S202, the Bluetooth device determines authentication information based on the first information, wherein the authentication information is used for access authentication of the Bluetooth device distribution network.
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:
OOB authentication information=sha256 (Device address, device ID, secret);
OOB authentication information=sha256 (Device address, UUID, secret);
OOB authentication information=sha256 (Device address, secret);
wherein the Device address represents a random Device address, the Device ID represents a Bluetooth Device identifier, the Secret represents a Secret key, and the UUID is a universal unique identifier (Universally Unique Identifier) of the Bluetooth Device; SHA256 is a standard secure hash algorithm, and the algorithm that determines the actual use of authentication information is not limited to SHA256. One way of calculating the OOB authentication information is as follows in table 1:
TABLE 1
Figure PCTCN2020117522-APPB-000001
The UUID of the bluetooth device is defined by the manufacturer of the bluetooth device, and one format of the UUID of the bluetooth device is shown in table 2 below:
TABLE 2
Field (Field) Size (Octets) Notes
Company ID 2 Company logo
Did 6 Device ID, device unique identifier
RFU 8 Reservation of
In some embodiments, the method may further comprise:
in step S203, the bluetooth device transmits a broadcast message.
In some embodiments, the broadcast message carries a random device address; such as carrying a random device address in the AdvA field of the broadcast message.
In other embodiments, the random number is carried in a first field of the broadcast message. In implementation, if the broadcast message is an unassigned broadcast message (unprovision Beacon message), the random number may be carried in the Hash field of the uniform resource identifier (Uniform Resource Identifier, URI) of the unprovision Beacon message.
Wherein the format of the unprovision Beacon message, as shown in fig. 5, the URI Hash field comprises four bytes, and the random number is padded in one or more bytes included in the URI Hash field.
In some alternative embodiments, the bluetooth device sends a broadcast message to the network distributor, so that the network distributor performs access authentication on the bluetooth device based on the static OOB authentication by using the broadcast message.
In other alternative embodiments, the bluetooth device may send a broadcast message to a platform gateway of the network to be accessed, where the platform gateway sends content included in the broadcast message to a cloud platform for developing the bluetooth device, so that the cloud platform for developing the bluetooth device performs access authentication on the bluetooth device based on the static OOB authentication mode.
It should be noted that, in the embodiment of the present application, the random device address remains unchanged in the single network configuration flow; the random number remains unchanged in the single distribution flow. It can be understood that the random device address remains unchanged before the end of the network, before the timeout of the network, or before the failure of the network; the random number remains unchanged before the end of the distribution network, before the overtime of the distribution network, or before the failure of the distribution network. I.e. the random number or the random device address determined by the bluetooth device is valid in one network allocation procedure of the bluetooth device.
An optional processing flow of the bluetooth device access authentication method applied to the network distributor provided in the embodiment of the present application, as shown in fig. 6, may include the following steps:
step S301, the network distributor acquires 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.
In some embodiments, the network distributor receives the second information sent by the bluetooth device.
In some embodiments, the authentication information is used for access authentication of the bluetooth device distribution network.
In some embodiments, the first field may be a URI Hash field populated with a random number, the random number generated by the bluetooth device.
In some optional embodiments, the network distributor obtains the second information, including: and the network distributor receives a broadcast message sent by the Bluetooth equipment, wherein the broadcast message carries the random equipment address.
In other alternative embodiments, the network distributor obtains the second information, including: the network distributor receives a broadcast message sent by Bluetooth equipment, wherein the first field of the broadcast message carries the random number.
In some embodiments, the method may further comprise:
In step S302, the network distributor performs access authentication of the network distribution on the bluetooth device based on the second information.
In some alternative embodiments, for the scenario in which the second information includes a random device address, the network distributor performs access authentication of the network distribution on the bluetooth device based on the number of times the random device address is used.
In the specific implementation, if the number of times of using the random equipment address is greater than or equal to one time, the network distributor confirms that the Bluetooth equipment authentication fails; that is, before the network is allocated this time, if the random device address is used, the network allocation device confirms that the Bluetooth device authentication fails; it can also be understood that, before the network allocation, the random device address is used, and the used random device address stored by the network allocation device itself includes the random device address, so that the network allocation device confirms that the bluetooth device authentication fails. Or if the number of times of using the random equipment address is zero and the UUID of the Bluetooth equipment is legal, the network distributor determines authentication information based on the random equipment address; that is, before the network allocation is performed, the random device address is not used (before the network allocation is performed, the random device address is not included in the used random device address stored by the network allocation device, if the network allocation device checks that the UUID of the bluetooth device is legal, the network allocation device obtains the secret of the device through Did, and determines the authentication information of the bluetooth device in the network allocation by using the random device address, the UUID and the secret, and starts the network allocation flow.
In some embodiments, the manner in which the network distributor determines the authentication information based on the random device address may include at least one of:
OOB authentication information=sha256 (Device address, device ID, secret);
OOB authentication information=sha256 (Device address, UUID, secret);
OOB authentication information=sha256 (Device address, secret);
the Device address represents a random Device address, the Device ID represents a Bluetooth Device identifier, the Secret represents a Secret key, and the UUID is a universal unique identifier of the Bluetooth Device; SHA256 is a standard secure hash algorithm.
In other alternative embodiments, the network distributor performs access authentication of the network distribution on the bluetooth device based on the number of uses of the value of the first field for the scenario in which the second information includes the first field.
In the implementation, if the number of times of using the value of the first field is greater than or equal to one time, the network distributor confirms that the Bluetooth equipment authentication fails; i.e. before the present distribution network, the value of the first field is used; it may also be understood that, before the network allocation, the network allocation device confirms that the bluetooth device authentication fails if the value of the used first field stored in the network allocation device itself includes the value of the first field carried in the second message. Or if the number of times of use of the value of the first field is zero (before the network allocation is performed this time, the value of the first field is not used, the value of the first field, which is stored in the network allocation device and is used, 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 allocation device obtains the secret of the device through Did, and the value of the first field, the UUID and the secret determine authentication information of the bluetooth device in the network allocation this time, and starts the network allocation process this time.
Taking the first field as a URI Hash field as an example, the value of the first field is a URI Hash value. The manner in which the network distributor determines the authentication information based on the value of the first field may include at least one of:
OOB authentication information=sha256 (URI Hash value, device ID, secret);
OOB authentication information=sha256 (URI Hash value, UUID, secret);
OOB authentication information=sha256 (URI Hash value, secret);
the Device ID represents a Bluetooth Device identifier, the Secret represents a Secret key, and the UUID is a universal unique identifier of the Bluetooth Device; SHA256 is a standard secure hash algorithm.
In the step S302, after the network distributor acquires the second information, the network distributor performs access authentication of the network distributor on the bluetooth device based on the second information. However, in some embodiments, after the network distributor acquires the second information, the network distributor does not perform access authentication of the network distributor on the bluetooth device, but sends the content included in the second information to the cloud server, and the cloud server performs access authentication of the network distributor on the bluetooth device; in this scenario, after executing step S301, the embodiment of the present application further includes:
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.
In some embodiments, the third information is used for the cloud server to perform access authentication of the distribution network for the bluetooth device.
In some embodiments, the third information may also include a UUID of the bluetooth device.
It should be noted that, in the embodiment of the present application, the random device address remains unchanged in the single network configuration flow; the random number remains unchanged in the single distribution flow. It can be understood that the random device address remains unchanged before the end of the network, before the timeout of the network, or before the failure of the network; the random number remains unchanged before the end of the distribution network, before the overtime of the distribution network, or before the failure of the distribution network. I.e. the random number or the random device address determined by the bluetooth device is valid in one network allocation procedure of the bluetooth device.
An optional processing flow of the bluetooth device access authentication method applied to the cloud server provided in the embodiment of the present application, as shown in fig. 7, may include the following steps:
in step S401, the cloud server acquires third information, where the third information includes: a random device address of the bluetooth device, or a first field carrying a random number.
In some embodiments, the cloud server receives third information sent by the network distributor.
In some embodiments, the third information may also include a UUID of the bluetooth device.
In some embodiments, the first field may be a URI Hash field populated with a random number, the random number generated by the bluetooth device.
In step S402, the cloud server performs access authentication of the distribution network to the bluetooth device based on the third information.
In some optional embodiments, for the scenario in which the second information includes a random device address, the cloud server performs access authentication of the distribution network on the bluetooth device based on the number of times the random device address is used.
In the implementation, if the number of times of using the random device address is greater than or equal to one, the cloud server confirms that the Bluetooth device authentication fails; before the network is allocated this time, the cloud server confirms that the Bluetooth equipment fails to authenticate; it can also be understood that, before the network allocation, the cloud server confirms that the bluetooth device authentication fails if the used random device address stored by the cloud server itself includes the random device address. Or if the using times of the random equipment address is zero and the UUID of the Bluetooth equipment is legal, the cloud server determines authentication information based on the random equipment address; that is, before the current network allocation, the random device address is not used (before the current network allocation, the used random device address stored by the cloud server does not include the random device address), if the cloud server checks that the UUID of the bluetooth device is legal, the cloud server obtains the secret of the device through Did, and determines the authentication information of the bluetooth device in the current network allocation by using the random device address, the UUID and the secret, and starts the current network allocation flow.
In some embodiments, the manner in which the cloud server determines the authentication information based on the random device address may include at least one of:
OOB authentication information=sha256 (Device address, device ID, secret);
OOB authentication information=sha256 (Device address, UUID, secret);
OOB authentication information=sha256 (Device address, secret);
the Device address represents a random Device address, the Device ID represents a Bluetooth Device identifier, the Secret represents a Secret key, and the UUID is a universal unique identifier of the Bluetooth Device; SHA256 is a standard secure hash algorithm.
In other alternative embodiments, the cloud server performs access authentication of the distribution network to the bluetooth device based on the number of uses of the value of the first field for the scenario in which the second information includes the first field.
In the implementation, if the number of times of using the value of the first field is greater than or equal to one time, the cloud server confirms that the Bluetooth equipment authentication fails; i.e. before the present distribution network, the value of the first field is used; it may also be understood that, before the network configuration, the value of the first field is used, and the value of the first field stored in the cloud server itself after the use includes the value of the first field carried in the second message, so that the cloud server confirms that the bluetooth device fails to authenticate. Or if the number of times of use of the value of the first field is zero (before the current network allocation, the value of the first field which is stored by the cloud server and used 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 secret of the device through Did, and the value of the first field, the UUID and the secret determine authentication information of the bluetooth device in the current network allocation, and the current network allocation flow is started.
Taking the first field as a URI Hash field as an example, the value of the first field is a URI Hash value. The manner in which the cloud server determines the authentication information based on the value of the first field may include at least one of:
OOB authentication information=sha256 (URI Hash value, device ID, secret);
OOB authentication information=sha256 (URI Hash value, UUID, secret);
OOB authentication information=sha256 (URI Hash value, secret);
the Device ID represents a Bluetooth Device identifier, the Secret represents a Secret key, and the UUID is a universal unique identifier of the Bluetooth Device; SHA256 is a standard secure hash algorithm.
It should be noted that, in the embodiment of the present application, the random device address remains unchanged in the single network configuration flow; the random number remains unchanged in the single distribution flow. It can be understood that the random device address remains unchanged before the end of the network, before the timeout of the network, or before the failure of the network; the random number remains unchanged before the end of the distribution network, before the overtime of the distribution network, or before the failure of the distribution network. I.e. the random number or the random device address determined by the bluetooth device is valid in one network allocation procedure of the bluetooth device.
In some scenarios, the bluetooth device is a device in the smart home system, and the bluetooth device can span different smart home platforms to perform access authentication; 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, as shown in fig. 8, may include the following steps:
Step S501, 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 fourth information is used to determine authentication information.
In some embodiments, the first cloud platform gateway receives fourth information sent by the bluetooth device.
In some embodiments, the authentication information is used for access authentication of the bluetooth device distribution network.
In some embodiments, the first field may be a URI Hash field populated with a random number, the random number generated by the bluetooth device.
In some embodiments, the fourth information further comprises: the bluetooth device corresponds to a Company IDentifier (CID) for the second cloud platform. The second cloud platform corresponding to the bluetooth device may be a cloud platform for developing the bluetooth device.
In some optional embodiments, the first cloud platform gateway obtains fourth information, including: and the first cloud platform gateway receives a broadcast message sent by the Bluetooth device, wherein the broadcast message carries the random device address.
In other alternative embodiments, the first cloud platform gateway receives fourth information, including: and the first cloud platform gateway receives a broadcast message sent by the Bluetooth device, wherein the random number is carried in the first field of the broadcast message.
For the scenario where the fourth message includes a random device address, in some alternative embodiments, the method may further comprise:
step S502, a first cloud platform gateway sends a random device address to a first cloud platform, and the first cloud platform gateway corresponds to the first cloud platform.
The first cloud platform gateway corresponds to the first cloud platform, and may be that the first cloud platform forgets light and the first cloud platform belong to the same network.
For the scenario in which the fourth message includes the first field, in some alternative embodiments, after performing step S501, the method may further include:
in 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.
The first cloud platform gateway corresponds to the first cloud platform, and may be that the first cloud platform forgets light and the first cloud platform belong to the same network.
In optional steps S502 and S503, the first cloud platform gateway sends the random device address or the first field carrying the random number to the first cloud platform, and the first cloud platform can send the random device address or the first field carrying the random number to the second cloud platform developing the bluetooth device, so that the second cloud platform performs access authentication on the bluetooth device network.
It should be noted that, in the embodiment of the present application, the random device address remains unchanged in the single network configuration flow; the random number remains unchanged in the single distribution flow. It can be understood that the random device address remains unchanged before the end of the network, before the timeout of the network, or before the failure of the network; the random number remains unchanged before the end of the distribution network, before the overtime of the distribution network, or before the failure of the distribution network. I.e. the random number or the random device address determined by the bluetooth device is valid in one network allocation procedure of the bluetooth device.
In some scenarios, the bluetooth device is a device in the smart home system, and the bluetooth device can span different smart home platforms to perform access authentication; based on this, an optional process flow of the bluetooth device access authentication method applied to the first cloud platform provided in the embodiment of the present application, as shown in fig. 9, may include the following steps:
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.
In some embodiments, the first cloud platform receives fifth information sent by the first cloud platform gateway.
In some embodiments, the authentication information is used for access authentication of the bluetooth device distribution network.
In some embodiments, the fifth information may further include: the UUID of the Bluetooth device and the CID of the second cloud platform corresponding to the Bluetooth device.
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:
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.
In some embodiments, the first cloud platform determines to develop a second cloud platform of the bluetooth device according to a CID of the second cloud platform corresponding to the bluetooth device, and sends sixth information to the second cloud platform; and the sixth information is used for determining authentication information by the second cloud platform, and the second cloud platform corresponds to the Bluetooth device.
In some embodiments, the first field may be a URI Hash field populated with a random number, the random number generated by the bluetooth device.
It should be noted that, in the embodiment of the present application, the random device address remains unchanged in the single network configuration flow; the random number remains unchanged in the single distribution flow. It can be understood that the random device address remains unchanged before the end of the network, before the timeout of the network, or before the failure of the network; the random number remains unchanged before the end of the distribution network, before the overtime of the distribution network, or before the failure of the distribution network. I.e. the random number or the random device address determined by the bluetooth device is valid in one network allocation procedure of the bluetooth device.
In some scenarios, the bluetooth device is a device in the smart home system, and the bluetooth device can span different smart home platforms to perform access authentication; 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, as shown in fig. 10, may include the following steps:
in step S801, the second cloud platform receives sixth information, where the sixth information includes: a random device address of the bluetooth device, or a first field carrying a random number.
In some embodiments, the second cloud platform receives the sixth information sent by the first cloud platform; the first cloud platform belongs to a network of a Bluetooth device to be distributed; the second cloud platform corresponds to the Bluetooth device and is a cloud platform for developing the Bluetooth device.
In some embodiments, the first field may be a URI Hash field populated with a random number, the random number generated by the bluetooth device.
Step S802, the second cloud platform performs access authentication of the distribution network for the bluetooth device based on the sixth information.
In some optional embodiments, for a scenario in which the sixth information includes a random device address, the second cloud platform performs access authentication of the distribution network for the bluetooth device based on the number of times the random device address is used.
In the implementation, if the number of times of using the random device address is greater than or equal to one, the second cloud platform confirms that the Bluetooth device authentication fails; before the network allocation is performed, the second cloud platform confirms that the Bluetooth equipment fails to authenticate; it may also be understood that, before the network allocation is performed this time, the random device address is used, and the used random device address stored in the second cloud platform itself includes the random device address, so that the second cloud platform confirms that the bluetooth device authentication fails. Or if the number of times of using the random device address is zero and the UUID of the Bluetooth device is legal, the second cloud platform determines authentication information based on the random device address; that is, before the network is configured this time, the random device address is not used (before the network is configured this time, the random device address is not included in the used random device address stored in the second cloud platform itself), if the second cloud platform checks that the UUID of the bluetooth device is legal, the second cloud platform obtains the secret of the device through Did, and determines the authentication information of the bluetooth device in the network is configured this time by using the random device address, the UUID and the secret, and starts the network configuration process this time.
In some embodiments, the manner in which the second cloud platform determines the authentication information based on the random device address may include at least one of:
OOB authentication information=sha256 (Device address, device ID, secret);
OOB authentication information=sha256 (Device address, UUID, secret);
OOB authentication information=sha256 (Device address, secret);
the Device address represents a random Device address, the Device ID represents a Bluetooth Device identifier, the Secret represents a Secret key, and the UUID is a universal unique identifier of the Bluetooth Device; SHA256 is a standard secure hash algorithm.
In other alternative embodiments, the second cloud platform performs access authentication of the distribution network to the bluetooth device based on the number of uses of the value of the first field for a scenario in which the sixth information includes the first field.
In the implementation, if the number of times of using the value of the first field is greater than or equal to one time, the second cloud platform confirms that the Bluetooth equipment authentication fails; i.e. before the present distribution network, the value of the first field is used; it may also be understood that, before the network configuration, the value of the first field is used, and the value of the first field, which is stored in the second cloud platform and used, includes the value of the first field carried in the second message, so that the second cloud platform confirms that the bluetooth device authentication fails. Or if the number of times of use of the value of the first field is zero (before the network configuration is performed this time, the value of the first field is not used, the value of the first field carried in the second message is not included in the value of the used first field stored by the second cloud platform, and the UUID of the bluetooth device is legal, the second cloud platform obtains the secret of the device through Did, and the value of the first field, the UUID and the secret determine authentication information of the bluetooth device in the network configuration this time, and starts the network configuration flow this time.
Taking the first field as a URI Hash field as an example, the value of the first field is a URI Hash value. The manner in which the second cloud platform determines the authentication information based on the value of the first field may include at least one of:
OOB authentication information=sha256 (URI Hash value, device ID, secret);
OOB authentication information=sha256 (URI Hash value, UUID, secret);
OOB authentication information=sha256 (URI Hash value, secret);
the Device ID represents a Bluetooth Device identifier, the Secret represents a Secret key, and the UUID is a universal unique identifier of the Bluetooth Device; SHA256 is a standard secure hash algorithm.
In this embodiment of the present application, after the second cloud platform determines authentication information of the bluetooth device in the present distribution network, the method may further include:
in step S803, the second cloud platform sends authentication information of the bluetooth device to the first cloud platform.
It should be noted that, in the embodiment of the present application, the random device address remains unchanged in the single network configuration flow; the random number remains unchanged in the single distribution flow. It can be understood that the random device address remains unchanged before the end of the network, before the timeout of the network, or before the failure of the network; the random number remains unchanged before the end of the distribution network, before the overtime of the distribution network, or before the failure of the distribution network. I.e. the random number or the random device address determined by the bluetooth device is valid in one network allocation procedure of the bluetooth device.
Based on the above description of the embodiments of the present application, for the static OOB authentication manner, the first optional detailed processing flow of the bluetooth device access authentication method provided in the embodiments of the present application, as shown in fig. 11, may include the following steps, where the network distributor determines authentication information of the bluetooth device based on a random device address:
in step S901, the bluetooth device enters a network to be configured, regenerates a random device address, and determines OOB authentication information of the network to be configured based on the random device address.
In some embodiments, the random device address remains unchanged until the current network allocation ends, or the current network allocation times out, or the current network allocation fails.
In some embodiments, the manner in which the bluetooth device determines the OOB authentication information of the present distribution network based on the random device address may include one of the following:
OOB authentication information=sha256 (Device address, device ID, secret);
OOB authentication information=sha256 (Device address, UUID, secret);
OOB authentication information=sha256 (Device address, secret);
the Device address represents a random Device address, the Device ID represents a Bluetooth Device identifier, the Secret represents a Secret key, and the UUID is a universal unique identifier of the Bluetooth Device; SHA256 is a standard secure hash algorithm.
In step S902, the bluetooth device broadcasts unprovision Beacon information.
In some embodiments, the unprovision Beacon information includes a random device address.
In step S903, the network distributor discovers the bluetooth device and determines OOB authentication information based on the random device address.
In some embodiments, the network distributor discovers the bluetooth device by scanning, and the network distributor transmits the UUID and the random device address of the bluetooth device to the cloud server; the network distributor checks whether the UUID of the Bluetooth equipment is legal or not and whether the random equipment address is used before the network distribution is carried out; if the UUID of the Bluetooth device is legal and the random device address is not used before the network allocation is performed, the network allocation device acquires the secret of the Bluetooth device through Did; the network distributor determines the OOB authentication information according to the random device address, the UUID of the Bluetooth device and the secret of the Bluetooth device.
In some embodiments, the manner in which the network distributor determines the authentication information based on the random device address may include at least one of:
OOB authentication information=sha256 (Device address, device ID, secret);
OOB authentication information=sha256 (Device address, UUID, secret);
OOB authentication information=sha256 (Device address, secret);
The Device address represents a random Device address, the Device ID represents a Bluetooth Device identifier, the Secret represents a Secret key, and the UUID is a universal unique identifier of the Bluetooth Device; SHA256 is a standard secure hash algorithm.
Step 904-step 9020, the Bluetooth device interacts with the network distributor to realize the network distribution of the Bluetooth device.
In some embodiments, after the bluetooth device and the network distributor respectively determine the OOB authentication information, the bluetooth device interacts with the network distributor, and a processing flow for implementing network distribution of the bluetooth device is the same as that in the prior art, which is not described herein.
Based on the above description of the embodiments of the present application, for the static OOB authentication manner, the second optional detailed processing flow of the bluetooth device access authentication method provided in the embodiments of the present application, as shown in fig. 12, determines, by a cloud server, authentication information of a bluetooth device based on a random device address, and includes the following steps:
in step S1001, the bluetooth device enters a network to be configured, and regenerates a random device address, and determines OOB authentication information of the network to be configured based on the random device address.
In some embodiments, the random device address remains unchanged until the current network allocation ends, or the current network allocation times out, or the current network allocation fails.
In some embodiments, the manner in which the bluetooth device determines the OOB authentication information of the present distribution network based on the random device address may include one of the following:
OOB authentication information=sha256 (Device address, device ID, secret);
OOB authentication information=sha256 (Device address, UUID, secret);
OOB authentication information=sha256 (Device address, secret);
the Device address represents a random Device address, the Device ID represents a Bluetooth Device identifier, the Secret represents a Secret key, and the UUID is a universal unique identifier of the Bluetooth Device; SHA256 is a standard secure hash algorithm.
In step S1002, the bluetooth device broadcasts unprovision Beacon information.
In some embodiments, the unprovision Beacon information includes a random device address.
In step S1003, the network distributor discovers the bluetooth device and determines OOB authentication information based on the random device address.
In some embodiments, the network distributor discovers the bluetooth device by scanning, and the network distributor transmits the UUID of the bluetooth device and the random device address to the cloud server.
In step S1004, the cloud server determines OOB authentication information.
In some embodiments, the cloud server checks whether the UUID of the bluetooth device is legal and whether the random device address was used before the current network allocation; if the UUID of the Bluetooth device is legal and the random device address is not used before the network allocation is performed, the cloud server acquires the secret of the Bluetooth device through Did; and the cloud server determines the OOB authentication information according to the random device address, the UUID of the Bluetooth device and the secret of the Bluetooth device.
In some embodiments, the manner in which the cloud server determines the authentication information based on the random device address may include at least one of:
OOB authentication information=sha256 (Device address, device ID, secret);
OOB authentication information=sha256 (Device address, UUID, secret);
OOB authentication information=sha256 (Device address, secret);
the Device address represents a random Device address, the Device ID represents a Bluetooth Device identifier, the Secret represents a Secret key, and the UUID is a universal unique identifier of the Bluetooth Device; SHA256 is a standard secure hash algorithm.
In step S1005, the cloud server sends OOB authentication information to the network distributor.
Step S1006-step S1022, the Bluetooth device interacts with the network distributor to realize the network distribution of the Bluetooth device.
In some embodiments, after the bluetooth device and the network distributor respectively determine the OOB authentication information, the bluetooth device interacts with the network distributor, and a processing flow for implementing network distribution of the bluetooth device is the same as that in the prior art, which is not described herein.
Based on the above description of the embodiments of the present application, for the static OOB authentication manner, the third optional detailed processing flow of the bluetooth device access authentication method provided in the embodiments of the present application, as shown in fig. 13, may include the following steps for access authentication of bluetooth devices between smart home systems:
Step 1101, the bluetooth device enters a network to be configured state, and regenerates a random device address, and determines OOB authentication information of the network to be configured based on the random device address.
In some embodiments, the random device address remains unchanged until the current network allocation ends, or the current network allocation times out, or the current network allocation fails.
In some embodiments, the manner in which the bluetooth device determines the OOB authentication information of the present distribution network based on the random device address may include one of the following:
OOB authentication information=sha256 (Device address, device ID, secret);
OOB authentication information=sha256 (Device address, UUID, secret);
OOB authentication information=sha256 (Device address, secret);
the Device address represents a random Device address, the Device ID represents a Bluetooth Device identifier, the Secret represents a Secret key, and the UUID is a universal unique identifier of the Bluetooth Device; SHA256 is a standard secure hash algorithm.
In some embodiments, the Bluetooth device is a device developed based on a B-cloud platform
In step S1102, the bluetooth device sends a broadcast packet to the a-cloud platform gateway.
In some embodiments, the broadcast packet may include: random device address, UUID of bluetooth device.
The A cloud platform gateway is a gateway corresponding to a network of a Bluetooth device to be matched with the network.
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.
In some embodiments, the type of bluetooth device may include the UUID of the bluetooth device and a random device address.
In some embodiments, the a-cloud platform obtains the OOB authentication information through the B-cloud platform. In specific implementation, at least the following steps can be included:
in step S11031, the a-cloud platform determines that the bluetooth device is not a-cloud platform developed device.
In step S11032, the a-cloud platform sends a request to the interconnection server, requesting to query the CID corresponding to the bluetooth device.
In step S11033, the interconnection server sends platform information for developing the bluetooth device to the a-cloud platform.
In step S11034, the a-cloud platform sends a request message to the B-cloud platform requesting to query the device type.
In some embodiments, the request message includes a CID of the bluetooth device, a UUID of the bluetooth device, and a random device address.
Step S11035, the B cloud platform checks whether UUIDs of Bluetooth devices are legal or not and whether random device addresses are used before the network allocation is performed; if the UUID of the Bluetooth device is legal and the random device address is not used before the network allocation is performed, the B cloud platform acquires the secret of the Bluetooth device through Did; and the cloud B platform determines the OOB authentication information according to the random device address, the UUID of the Bluetooth device and the secret of the Bluetooth device.
In step S11036, the B-cloud platform sends the device type and the OBB authentication information to the a-cloud platform.
In some embodiments, the B-cloud platform also sends device information to the a-cloud platform, wherein the device information includes control functions and control commands supported by the bluetooth device.
And step S1104, the A cloud platform sends the equipment type and the OOB authentication information to an A cloud platform gateway.
And step S1105-S1106, the A-platform gateway completes connection and access with the Bluetooth device.
And step S11071-step S110710 are executed, and the Bluetooth equipment interacts with the A cloud platform gateway to realize the distribution network of the Bluetooth equipment.
And step S110711, the A cloud platform gateway reports the authentication result to the A cloud platform.
Step S110712, the a-cloud platform stores the device information.
In step S1108, the a-cloud platform gateway broadcasts the authentication result.
Based on the above description of the embodiments of the present application, for the static OOB authentication manner, the fourth optional detailed processing flow of the bluetooth device access authentication method provided in the embodiments of the present application, as shown in fig. 14, may include the following steps, where the network distributor determines authentication information of the bluetooth device based on the URI Hash field:
step S1201, the bluetooth device enters a network to be configured, regenerates a random number, and determines OOB authentication information of the network to be configured based on the random number.
In some embodiments, the random number remains unchanged until the current network allocation ends, or the current network allocation times out, or the current network allocation fails.
In some embodiments, the bluetooth device determines the OOB authentication information of the current network based on the random number, which may be that the bluetooth device determines the OOB authentication information of the current network based on the URI Hash field filled with the random number; the method for determining the OOB authentication information of the present distribution network by the bluetooth device based on the URI Hash field filled with the random number may include one of the following:
OOB authentication information=sha256 (URI Hash, device ID, secret);
OOB authentication information=sha256 (URI Hash, UUID, secret);
OOB authentication information=sha256 (URI Hash, secret);
the Device ID represents Bluetooth equipment identification, secret represents a Secret key, and UUID is a universal unique identifier of the Bluetooth equipment; SHA256 is a standard secure hash algorithm.
In step S1202, the bluetooth device broadcasts information.
In some embodiments, the information includes a URI Hash field.
In step S1203, the network distributor discovers the bluetooth device and determines OOB authentication information based on the URI Hash.
In some embodiments, the network distributor discovers the bluetooth device through scanning, and the network distributor sends the UUID and URI Hash fields of the bluetooth device to the cloud server; the network distributor checks whether UUID of the Bluetooth equipment is legal or not, and whether the value of the URI Hash field is used before the network distribution is carried out; if the UUID of the Bluetooth device is legal and the value of the URI Hash field is not used before the network allocation is performed, the network allocation device acquires the secret of the Bluetooth device through Did; the network distributor determines the OOB authentication information according to the value of the URI Hash field, the UUID of the Bluetooth device and the secret of the Bluetooth device.
In some embodiments, the manner in which the network distributor determines the authentication information based on the value of the URI Hash field may include at least one of:
OOB authentication information=sha256 (URI Hash, device ID, secret);
OOB authentication information=sha256 (URI Hash, UUID, secret);
OOB authentication information=sha256 (URI Hash, secret);
the Device ID represents a Bluetooth Device identifier, the Secret represents a Secret key, and the UUID is a universal unique identifier of the Bluetooth Device; SHA256 is a standard secure hash algorithm.
Step 1204-step 1220, the bluetooth device interacts with the network distributor to realize the network distribution of the bluetooth device.
In some embodiments, after the bluetooth device and the network distributor respectively determine the OOB authentication information, the bluetooth device interacts with the network distributor, and a processing flow for implementing network distribution of the bluetooth device is the same as that in the prior art, which is not described herein.
Based on the above description of the embodiments of the present application, for the static OOB authentication manner, a fifth optional detailed processing flow of the bluetooth device access authentication method provided in the embodiments of the present application, as shown in fig. 15, determines, by a cloud server, authentication information of a bluetooth device based on a URI Hash field, including the following steps:
In step S1301, the bluetooth device enters a network to be configured, regenerates a random number, and determines OOB authentication information of the network to be configured based on the random number.
In some embodiments, the random number remains unchanged until the current network allocation ends, or the current network allocation times out, or the current network allocation fails.
In some embodiments, the manner in which the bluetooth device determines the OOB authentication information of the present configuration network based on the random number may include one of the following:
OOB authentication information=sha256 (URI Hash, device ID, secret);
OOB authentication information=sha256 (URI Hash, UUID, secret);
OOB authentication information=sha256 (URI Hash, secret);
the Device ID represents Bluetooth equipment identification, secret represents a Secret key, and UUID is a universal unique identifier of the Bluetooth equipment; SHA256 is a standard secure hash algorithm.
In step S1302, the bluetooth device broadcasts information.
In some embodiments, the information includes a URI Hash field.
In step S1303, the network distributor discovers the bluetooth device.
In some embodiments, the network distributor discovers the bluetooth device by scanning, and the network distributor transmits the UUID and URI Hash fields of the bluetooth device to the cloud server.
In step S1304, the cloud server determines OOB authentication information based on the URI Hash.
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 was used before the current network allocation; if the UUID of the Bluetooth device is legal and the value of the URI Hash field is not used before the network allocation is performed, the cloud server acquires the secret of the Bluetooth device through Did; and the cloud server determines the OOB authentication information according to the value of the URI Hash field, the UUID of the Bluetooth device and the secret of the Bluetooth device.
In some embodiments, the manner in which the cloud server determines the authentication information based on the value of the URI Hash field may include at least one of:
OOB authentication information=sha256 (URI Hash, device ID, secret);
OOB authentication information=sha256 (URI Hash, UUID, secret);
OOB authentication information=sha256 (URI Hash, secret);
the Device ID represents a Bluetooth Device identifier, the Secret represents a Secret key, and the UUID is a universal unique identifier of the Bluetooth Device; SHA256 is a standard secure hash algorithm.
In step S1305, the cloud server sends OOB authentication information to the network distributor.
Step S1306-step S1322, the Bluetooth device interacts with the network distributor to realize the network distribution of the Bluetooth device.
In some embodiments, after the bluetooth device and the network distributor respectively determine the OOB authentication information, the bluetooth device interacts with the network distributor, and a processing flow for implementing network distribution of the bluetooth device is the same as that in the prior art, which is not described herein.
Based on the above description of the embodiments of the present application, for the static OOB authentication manner, a sixth optional detailed processing flow of the bluetooth device access authentication method provided in the embodiments of the present application, as shown in fig. 16, may include the following steps for access authentication of bluetooth devices between smart home systems:
in step S1401, the bluetooth device enters a network to be configured, regenerates a random number, and determines OOB authentication information of the network to be configured based on the random number.
In some embodiments, the random number remains unchanged until the current network allocation ends, or the current network allocation times out, or the current network allocation fails.
In some embodiments, the bluetooth device determines the OOB authentication information of the current network based on the random number, which may be that the bluetooth device determines the OOB authentication information of the current network based on the URI Hash field filled with the random number; the method for determining the OOB authentication information of the present distribution network by the bluetooth device based on the URI Hash field filled with the random number may include one of the following:
OOB authentication information=sha256 (URI Hash, device ID, secret);
OOB authentication information=sha256 (URI Hash, UUID, secret);
OOB authentication information=sha256 (URI Hash, secret);
the Device ID represents Bluetooth equipment identification, secret represents a Secret key, and UUID is a universal unique identifier of the Bluetooth equipment; SHA256 is a standard secure hash algorithm.
In some embodiments, the bluetooth device is a device developed based on a B-cloud platform.
Step S1402, the bluetooth device sends a broadcast packet to the a-cloud platform gateway.
In some embodiments, the broadcast packet may include: URI Hash field, UUID of Bluetooth device.
The A cloud platform gateway is a gateway corresponding to a network of a Bluetooth device to be matched with the network.
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.
In some embodiments, the type of bluetooth device may include the UUID and URI Hash fields of the bluetooth device.
In some embodiments, the a-cloud platform obtains the OOB authentication information through the B-cloud platform. In specific implementation, at least the following steps can be included:
in step S14031, the a-cloud platform determines that the bluetooth device is not a device developed by the a-cloud platform.
In step S14032, the cloud platform a sends a request to the interconnection server to query the CID corresponding to the bluetooth device.
In step S14033, the interconnection server sends platform information for developing the bluetooth device to the a cloud platform.
In step S14034, the cloud platform a sends a request message to the cloud platform B requesting to query the device type.
In some embodiments, the request message includes a CID of the bluetooth device, a UUID of the bluetooth device, and a URI Hash field.
Step S14035, the B cloud platform checks whether UUID of the Bluetooth device is legal or not and whether the value of the URI Hash field is used before the network configuration; if the UUID of the Bluetooth device is legal and the value of the URI Hash field is not used before the network configuration is performed, the B cloud platform acquires the secret of the Bluetooth device through Did; and the cloud B platform determines the OOB authentication information according to the random device address, the UUID of the Bluetooth device and the secret of the Bluetooth device.
In step S14036, the B-cloud platform sends the device type and the OBB authentication information to the a-cloud platform.
In some embodiments, the B-cloud platform also sends device information to the a-cloud platform, wherein the device information includes control functions and control commands supported by the bluetooth device.
In step S1404, the a-cloud platform sends the device type and the OOB authentication information to the a-cloud platform gateway.
In steps S1405-S1406, the a-platform gateway completes the connection and access with the bluetooth device.
And step S14071-step S140710 are executed, and the Bluetooth equipment interacts with the A cloud platform gateway to realize the distribution network of the Bluetooth equipment.
And step S140711, the A cloud platform gateway reports the authentication result to the A cloud platform.
Step S140712, the a-cloud platform stores the device information.
In step S1408, the a-cloud platform gateway broadcasts the authentication result.
It should be noted that, the "bluetooth device" in the embodiment of the present application may also be a bluetooth Mesh device applied to a bluetooth Mesh network, and the "cloud platform" in the embodiment of the present application is a cloud platform accessed by a gateway.
It should be understood that, in various embodiments of the present application, the sequence number of each process described above does not mean that the execution sequence of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
In the prior art, OOB authentication information determined by constant parameters is also constant, once the constant parameters or the constant OOB authentication information are revealed, an attacker can impersonate legal Bluetooth equipment to try to join the Bluetooth network, and as the attacker has revealed Static OOB and Beacon information broadcasted by the legal Bluetooth equipment is also easy to copy, the attacker can completely join the Bluetooth network through authentication, so that the NetKey or AppKey of the Bluetooth network is revealed, and a great security hole is caused. According to the Bluetooth equipment access authentication method, the Bluetooth equipment generates a random equipment address or a random number in each distribution network period, and OOB authentication information is generated based on the random equipment address or the random number. The network distributor or the cloud server or the cloud platform corresponding to the Bluetooth device cooperatively generates OOB authentication information according to the random device address or the random number, so that the gateway of the network distributor or the Bluetooth device to be distributed performs access authentication on the Bluetooth device based on the OOB authentication information, and the network distribution flow of the Bluetooth device is completed. Because the random device address or the random number used for generating the OOB authentication information in the embodiment of the application is only valid in the current network distribution period, even if an attacker obtains the random device address or the random number, the OOB information generated by the attacker by using the obtained random device address or the random number in other network distribution periods cannot be used for authenticating the Bluetooth device, and the security of the network distribution of the Bluetooth device is improved.
In order to implement the bluetooth device access authentication method provided in the embodiments of the present application, the embodiments of the present application further provide a bluetooth device, where an optional composition structure of the bluetooth device 1500, as shown in fig. 17, includes:
a first processing unit 1501 for determining first information, the first information comprising: a random device address or random number of the bluetooth device;
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 distribution network.
In some embodiments, the bluetooth device 1500 further comprises:
the first sending unit 1502 is configured to send a broadcast message, where the broadcast message carries the random device address.
In some embodiments, the bluetooth device 1500 further comprises:
the second sending unit 1503 is configured to send a broadcast message, where the first field of the broadcast message carries the random number.
In some embodiments, the first field comprises: URI Hash field.
In some embodiments, the random device address remains unchanged during a single distribution flow; the random number remains unchanged in a single distribution flow.
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 network distributor, where an optional composition structure of the network distributor 1600, as shown in fig. 18, includes:
a first receiving unit 1601 configured to acquire second information, the second information including: a random device address of the bluetooth device, or a first field carrying a random number;
the second information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
In some embodiments, the first receiving unit 1601 is configured to receive a broadcast message, where the broadcast message carries the random device address.
In some embodiments, the network distributor 1600 further comprises:
a second processing unit 1602 is configured to perform access authentication of the distribution network for the bluetooth device based on the random device address.
In some embodiments, the second processing unit 1602 is configured to perform access authentication of the distribution network for the bluetooth device based on the number of uses of the random device address.
In some embodiments, the second processing unit 1602 is configured to confirm that the bluetooth device authentication fails if the number of uses of the random device address is greater than or equal to one;
Or if the number of times of using the random device address is zero and the UUID of the Bluetooth device is legal, determining authentication information based on the random device address.
In some embodiments, the first receiving unit 1601 is configured to receive a broadcast message, where the random number is carried in the first field of the broadcast message.
In some embodiments, the network distributor 1600 further comprises:
a third processing unit 1603 is configured to perform access authentication of the distribution network to the bluetooth device based on the first field.
In some embodiments, the third processing unit 1603 is configured to perform access authentication of the distribution network to the bluetooth device based on the number of uses of the value of the first field.
In some embodiments, the third processing unit 1603 is configured to confirm that the bluetooth device authentication fails if the number of uses of the value of the first field is greater than or equal to one;
or if the number of times of use of the value of the first field is zero and the UUID of the bluetooth device is legal, determining authentication information based on the first field.
In some embodiments, the first field comprises: URI Hash field.
In some embodiments, the network distributor 1600 further comprises:
a third sending unit 1604 configured to send the third information to a cloud server, where the third information includes: the random device address, or the first field;
and the third information is used for the cloud server to execute access authentication of the distribution network for the Bluetooth equipment.
In some embodiments, the random device address remains unchanged during a single distribution flow; the random number remains unchanged in a single distribution flow.
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 cloud server, where an optional composition structure of the cloud server 1700, as shown in fig. 19, includes:
a second receiving unit 1701 configured to acquire third information comprising: a random device address of the bluetooth device, or a first field carrying a random number;
a fourth processing unit 1702 is configured to perform access authentication of a distribution network for the bluetooth device based on the third information.
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 access authentication of a distribution network for the bluetooth device based on a number of times the random device address is used.
In some embodiments, if the number of uses of the random device address is greater than or equal to one, the fourth processing unit 1702 is configured to confirm that the bluetooth device authentication fails;
if the number of times of use of the random device address 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 distribution network.
In some embodiments, if the third information includes the first field, the fourth processing unit 1702 is configured to perform access authentication of a distribution network for the bluetooth device based on a number of uses of a value of the first field.
In some embodiments, if the number of uses of the value of the first field is greater than or equal to one, the fourth processing unit 1702 is configured to confirm that the bluetooth device authentication fails;
or if the number of times of use of the value of the first field 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, where the authentication information is used for access authentication of the bluetooth device distribution network.
In some embodiments, the first field comprises: URI Hash field.
In some embodiments, the random device address remains unchanged during a single distribution flow; the random number remains unchanged in a single distribution flow.
In order to implement the bluetooth device access authentication method provided in the embodiments of the present application, the embodiments of the present application further provide a first cloud platform gateway, where an optional composition structure of the first cloud platform gateway 1800, as shown in fig. 20, includes:
a third receiving unit 1801 configured to acquire fourth information, the fourth information including: a random device address of the bluetooth device, or a first field carrying a random number;
the fourth information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
In some embodiments, the third receiving unit 1801 is configured to receive a broadcast message, where the broadcast message carries the random device address.
In some embodiments, the first cloud platform gateway 1800 further comprises:
and a fourth sending unit 1802 configured to send the random device address to a first cloud platform, where the first cloud platform gateway corresponds to the first cloud platform.
In some embodiments, the third receiving unit 1801 is configured to receive a broadcast message, where the random number is carried in the first field of the broadcast message.
In some embodiments, the first cloud platform gateway 1800 further comprises:
and a fifth sending unit 1803, configured to send the first field to a first cloud platform, where the first cloud platform gateway corresponds to the first cloud platform.
In some embodiments, the first field comprises: URI Hash field.
In some embodiments, the fourth information further comprises: the bluetooth device corresponds to a CID for the second cloud platform.
In some embodiments, the random device address remains unchanged during a single distribution flow; the random number remains unchanged in a single distribution flow.
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, where an optional composition structure of the first cloud platform 1900 is shown in fig. 21, and includes:
a fourth receiving unit 1901 configured to acquire fifth information, the fifth information including: a random device address of the bluetooth device, or a first field carrying a random number;
The fifth information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
In some embodiments, the first cloud platform 1900 further comprises:
a sixth sending unit 1902, configured to send sixth information to a second cloud platform if the bluetooth device is not a device corresponding to the first cloud platform, where the sixth information includes: the random device address, or the first field;
and the sixth information is used for determining authentication information by the second cloud platform, and the second cloud platform corresponds to the Bluetooth device.
In some embodiments, the first field comprises: URI Hash field.
In some embodiments, the fifth information further comprises: the bluetooth device corresponds to a CID for the second cloud platform.
In some embodiments, the random device address remains unchanged during a single distribution flow; the random number remains unchanged in a single distribution flow.
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 second cloud platform, where an optional composition structure of the second cloud platform 2000, as shown in fig. 22, includes:
A fifth receiving unit 2001 configured to acquire sixth information including: a random device address of the bluetooth device, or a first field carrying a random number;
a fifth processing unit 2002 is configured to perform access authentication of a distribution network for the bluetooth device based on the sixth information.
In some embodiments, the fifth processing unit 2002 is configured to perform access authentication of the distribution network on the bluetooth device based on the number of times the random device address is used if the sixth information includes the random device address of the bluetooth device.
In some embodiments, the fifth processing unit 2002 is configured to confirm that the bluetooth device authentication fails if the number of uses of the random device address is greater than or equal to one;
or if the number of times of using the random equipment address is zero and the UUID of the Bluetooth equipment is legal, determining authentication information based on the random equipment address, wherein the authentication information is used for access authentication of the Bluetooth equipment distribution network.
In some embodiments, the fifth processing unit 2002 is configured to perform access authentication of the distribution network on the bluetooth device based on the number of uses of the value of the first field if the fifth information includes the first field.
In some embodiments, if the number of uses of the value of the first field is greater than or equal to one, confirming that the bluetooth device authentication fails;
or if the number of times of use of the value of the first field is zero and the UUID of the bluetooth device is legal, determining authentication information based on the first field, where the authentication information is used for access authentication of the bluetooth device distribution network.
In some embodiments, the first field comprises: URI Hash field.
In some embodiments, the random device address remains unchanged during a single distribution flow; the random number remains unchanged in a single distribution flow.
The embodiment of the application provides a Bluetooth device, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the Bluetooth device access authentication method executed by the Bluetooth device when the computer program runs.
The embodiment of the application provides a network distributor, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the Bluetooth equipment access authentication method executed by the network distributor when running the computer program.
The embodiment of the application provides a cloud server, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the Bluetooth equipment access authentication method executed by the cloud server when the computer program runs.
The embodiment of the application provides a first cloud platform gateway, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the Bluetooth equipment access authentication method executed by the first cloud platform gateway when running the computer program.
The embodiment of the application provides a first cloud platform, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the Bluetooth equipment access authentication method executed by the first cloud platform when running the computer program.
The embodiment of the application provides a second cloud platform, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the Bluetooth equipment access authentication method executed by the second cloud platform when running the computer program.
The embodiment of the application also provides a chip, which comprises: and the processor is used for calling and running the computer program from the memory, so that the device provided with the chip executes the Bluetooth device access authentication method.
The embodiment of the application also provides a storage medium which stores an executable program, and when the executable program is executed by a processor, the Bluetooth equipment access authentication method is realized.
The embodiment of the application also provides a computer program product, which comprises computer program instructions, wherein the computer program instructions enable a computer to execute the Bluetooth device access authentication method.
The embodiment of the application also provides a computer program, which enables a computer to execute the Bluetooth equipment access authentication method.
Fig. 23 is a schematic diagram of a hardware composition structure of an electronic device (a bluetooth device, a network distributor, or a cloud server, or a first cloud platform gateway, or a first cloud platform, or a second cloud platform) according to an embodiment of the present application, where the electronic device 700 includes: at least one processor 701, memory 702, and at least one network interface 704. The various components in the electronic device 700 are coupled together by a bus system 705. It is appreciated that the bus system 705 is used to enable connected communications between these components. The bus system 705 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration, the various buses are labeled as bus system 705 in fig. 23.
It is to be appreciated that the memory 702 can be either volatile memory or nonvolatile memory, and can include both volatile and nonvolatile memory. Wherein the nonvolatile Memory may be ROM, programmable read-Only Memory (PROM, programmable Read-Only Memory), erasable programmable read-Only Memory (EPROM, erasable Programmable Read-Only Memory), electrically erasable programmable read-Only Memory (EEPROM, electrically Erasable Programmable Read-Only Memory), magnetic random access Memory (FRAM, ferromagnetic random access Memory), flash Memory (Flash Memory), magnetic surface Memory, optical disk, or compact disk read-Only Memory (CD-ROM, compact Disc Read-Only Memory); the magnetic surface memory may be a disk memory or a tape memory. The volatile memory may be random access memory (RAM, random Access Memory), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (SRAM, static Random Access Memory), synchronous static random access memory (SSRAM, synchronous Static Random Access Memory), dynamic random access memory (DRAM, dynamic Random Access Memory), synchronous dynamic random access memory (SDRAM, synchronous Dynamic Random Access Memory), double data rate synchronous dynamic random access memory (ddr SDRAM, double Data Rate Synchronous Dynamic Random Access Memory), enhanced synchronous dynamic random access memory (ESDRAM, enhanced Synchronous Dynamic Random Access Memory), synchronous link dynamic random access memory (SLDRAM, syncLink Dynamic Random Access Memory), direct memory bus random access memory (DRRAM, direct Rambus Random Access Memory). The memory 702 described in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
The memory 702 in the embodiments 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 application 7022. A program implementing the method of the embodiment of the present application may be contained in the application program 7022.
The method disclosed in the embodiments of the present application may be applied to the processor 701 or implemented by the processor 701. The processor 701 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in the processor 701 or by instructions in the form of software. The processor 701 may be a general purpose processor, a digital signal processor (DSP, digital Signal Processor), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The processor 701 may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly embodied in a hardware decoding processor or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium in a memory 702. The processor 701 reads information in the memory 702 and, in combination with its hardware, performs the steps of the method as described above.
In an exemplary embodiment, the electronic device 700 can be implemented by one or more application specific integrated circuits (ASIC, application Specific Integrated Circuit), DSP, programmable logic device (PLD, programmable Logic Device), complex programmable logic device (CPLD, complex Programmable Logic Device), FPGA, general purpose processor, controller, MCU, MPU, or other electronic components for performing the aforementioned methods.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this application is merely an association relation describing an associated object, and indicates that three relations may exist, for example, a and/or B may indicate: a exists alone, A and B exist together, and B exists alone. In this application, the character "/" generally indicates that the associated object is an or relationship.
The foregoing description of the preferred embodiments of the present application is not intended to limit the scope of the present application, but is intended to cover any modifications, equivalents, and alternatives falling within the spirit and principles of the present application.

Claims (118)

  1. A bluetooth device access authentication method, the method comprising:
    the Bluetooth device determines first information, the first information comprising: a random device address or random number of the bluetooth device;
    and the Bluetooth equipment determines authentication information based on the first information, wherein the authentication information is used for access authentication of the Bluetooth equipment distribution network.
  2. The method of claim 1, wherein the method further comprises:
    and the Bluetooth equipment sends a broadcast message, wherein the broadcast message carries the random equipment address.
  3. The method of claim 1, wherein the method further comprises:
    the Bluetooth device sends a broadcast message, wherein the first field of the broadcast message carries the random number.
  4. The method of claim 3, wherein the first field comprises:
    uniform resource identifier Fu Haxi URI Hash field.
  5. The method of any of claims 1-4, wherein the random device address remains unchanged in a single distribution flow;
    The random number remains unchanged in a single distribution flow.
  6. A bluetooth device access authentication method, the method comprising:
    the network distributor acquires second information, wherein the second information comprises: a random device address of the bluetooth device, or a first field carrying a random number;
    the second information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
  7. The method of claim 6, wherein the network distributor obtaining second information comprises:
    and the network distributor receives a broadcast message, wherein the broadcast message carries the random equipment address.
  8. The method according to claim 6 or 7, wherein the method further comprises:
    and the network distributor executes access authentication of the network distribution for the Bluetooth equipment based on the random equipment address.
  9. The method of claim 8, wherein the network distributor performing access authentication of a network distribution to the bluetooth device based on the random device address comprises:
    and the network distributor executes access authentication of the network distribution for the Bluetooth equipment based on the using times of the random equipment address.
  10. The method of claim 9, wherein the network distributor performing access authentication of the bluetooth device based on the number of uses of the random device address comprises:
    If the number of times of using the random equipment address is greater than or equal to one, the network distributor confirms that the Bluetooth equipment authentication fails;
    or if the number of times of using the random device address is zero and the UUID of the universal unique identifier of the Bluetooth device is legal, the network distributor determines authentication information based on the random device address.
  11. The method of claim 6, wherein the network distributor obtaining second information comprises:
    the network distributor receives a broadcast message, wherein the first field of the broadcast message carries the random number.
  12. The method according to claim 6 or 11, wherein the method further comprises:
    and the network distributor executes access authentication of the network distribution on the Bluetooth equipment based on the first field.
  13. The method of claim 12, wherein the network distributor performing access authentication of a network distribution to the bluetooth device based on the first field comprises:
    the network distributor executes access authentication of the distribution network for the Bluetooth equipment based on the using times of the value of the first field.
  14. The method of claim 13, wherein the network distributor performing access authentication of a network distribution to the bluetooth device based on the number of uses of the value of the first field comprises:
    If the number of times of using the value of the first field is greater than or equal to one, the network distributor confirms that the Bluetooth equipment authentication fails;
    or if the number of times of use of the value of the first field is zero and the universal unique identifier UUID of the bluetooth device is legal, the network distributor determines authentication information based on the first field.
  15. The method of any of claims 6 to 14, wherein the first field comprises:
    uniform resource identifier Fu Haxi URI Hash field.
  16. The method of claim 6, or 7, or 11, wherein the method further comprises:
    the network distributor sends the third information to a cloud server, wherein the third information comprises: the random device address, or the first field;
    and the third information is used for the cloud server to execute access authentication of the distribution network for the Bluetooth equipment.
  17. The method of any of claims 6 to 16, wherein the random device address remains unchanged in a single distribution flow;
    the random number remains unchanged in a single distribution flow.
  18. A bluetooth device access authentication method, the method comprising:
    the cloud server acquires third information, wherein the third information comprises: a random device address of the bluetooth device, or a first field carrying a random number;
    And the cloud server executes access authentication of the distribution network to the Bluetooth equipment based on the third information.
  19. The method of claim 18, wherein the cloud server performing access authentication of a distribution network to the bluetooth device based on the third information comprises:
    and if the third information comprises the random equipment address of the Bluetooth equipment, the cloud server executes access authentication of the distribution network for the Bluetooth equipment based on the using times of the random equipment address.
  20. The method of claim 19, wherein the cloud server performing access authentication of the distribution network to the bluetooth device based on the number of uses of the random device address comprises:
    if the number of times of using the random equipment address is greater than or equal to one, the cloud server confirms that the Bluetooth equipment authentication fails;
    or if the number of times of using the random equipment address is zero and the UUID of the Bluetooth equipment is legal, the cloud server determines authentication information based on the random equipment address, wherein the authentication information is used for access authentication of the Bluetooth equipment distribution network.
  21. The method of claim 18, wherein the cloud server performing access authentication of a distribution network to the bluetooth device based on the third information comprises:
    And if the third information comprises the first field, the cloud server executes access authentication of the distribution network for the Bluetooth equipment based on the using times of the value of the first field.
  22. The method of claim 21, wherein the cloud server performing access authentication of a distribution network for the bluetooth device based on the number of uses of the value of the first field comprises:
    if the number of times of using the value of the first field is greater than or equal to one, the cloud server confirms that the Bluetooth equipment authentication fails;
    or if the number of times of use of the value of the first field is zero and the UUID of the bluetooth device is legal, the cloud server determines authentication information based on the first field, where the authentication information is used for access authentication of the bluetooth device distribution network.
  23. The method of any of claims 18 to 22, wherein the first field comprises:
    uniform resource identifier Fu Haxi URI Hash field.
  24. The method of any of claims 18 to 23, wherein the random device address remains unchanged in a single distribution flow;
    the random number remains unchanged in a single distribution flow.
  25. A bluetooth device access authentication method, the method comprising:
    The first cloud platform gateway obtains fourth information, wherein the fourth information comprises: a random device address of the bluetooth device, or a first field carrying a random number;
    the fourth information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
  26. The method of claim 25, wherein the first cloud platform gateway obtaining fourth information comprises:
    and the first cloud platform gateway receives a broadcast message, wherein the broadcast message carries the random equipment address.
  27. The method of claim 25 or 26, wherein the method further comprises:
    the first cloud platform gateway sends the random equipment address to a first cloud platform, and the first cloud platform gateway corresponds to the first cloud platform.
  28. The method of claim 25, wherein the first cloud platform gateway obtaining fourth information comprises:
    the first cloud platform gateway receives a broadcast message, wherein the first field of the broadcast message carries the random number.
  29. The method of claim 25 or 28, wherein the method further comprises:
    the first cloud platform gateway sends the first field to a first cloud platform, and the first cloud platform gateway corresponds to the first cloud platform.
  30. The method of any of claims 25 to 29, wherein the first field comprises:
    uniform resource identifier Fu Haxi URI Hash field.
  31. The method of any of claims 25 to 30, wherein the fourth information further comprises:
    the bluetooth device corresponds to a company identification CID for the second cloud platform.
  32. The method of any of claims 25 to 31, wherein the random device address remains unchanged in a single distribution flow;
    the random number remains unchanged in a single distribution flow.
  33. A bluetooth device access authentication method, the method comprising:
    the first cloud platform obtains fifth information, wherein the fifth information comprises: a random device address of the bluetooth device, or a first field carrying a random number;
    the fifth information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
  34. The method of claim 33, wherein if the bluetooth device is not the device corresponding to the first cloud platform, the method further comprises:
    the first cloud platform sends sixth information to the second cloud platform, wherein the sixth information comprises: the random device address, or the first field;
    And the sixth information is used for determining authentication information by the second cloud platform, and the second cloud platform corresponds to the Bluetooth device.
  35. The method of claim 33 or 34, wherein the first field comprises:
    uniform resource identifier Fu Haxi URI Hash field.
  36. The method of any of claims 33 to 35, wherein the fifth information further comprises:
    the bluetooth device corresponds to a company identification CID for the second cloud platform.
  37. The method of any of claims 33 to 36, wherein the random device address remains unchanged in a single distribution flow;
    the random number remains unchanged in a single distribution flow.
  38. A bluetooth device access authentication method, the method comprising:
    the second cloud platform obtains sixth information, wherein the sixth information comprises: a random device address of the bluetooth device, or a first field carrying a random number;
    and the second cloud platform executes access authentication of the distribution network for the Bluetooth equipment based on the sixth information.
  39. The method of claim 38, wherein the second cloud platform performing access authentication of a distribution network for the bluetooth device based on the sixth information comprises:
    and if the sixth information comprises the random equipment address of the Bluetooth equipment, the second cloud platform executes access authentication of the distribution network for the Bluetooth equipment based on the using times of the random equipment address.
  40. The method of claim 39, wherein the second cloud platform performing access authentication of the distribution network to the bluetooth device based on the number of uses of the random device address comprises:
    if the number of times of using the random device address is greater than or equal to one, the second cloud platform confirms that the Bluetooth device authentication fails;
    or if the number of times of using the random device address is zero and the UUID of the Bluetooth device is legal, the second cloud platform determines authentication information based on the random device address, wherein the authentication information is used for access authentication of the Bluetooth device distribution network.
  41. The method of claim 38, wherein the second cloud platform performing access authentication of a distribution network for the bluetooth device based on the fifth information comprises:
    and if the fifth information comprises the first field, the second cloud platform executes access authentication of the distribution network on the Bluetooth equipment based on the using times of the value of the first field.
  42. The method of claim 41, wherein the second cloud platform performing access authentication of the distribution network to the bluetooth device based on the number of uses of the value of the first field comprises:
    If the number of times of using the value of the first field is greater than or equal to one, the second cloud platform confirms that the Bluetooth equipment authentication fails;
    or if the number of times of use of the value of the first field is zero and the UUID of the bluetooth device is legal, the second cloud platform determines authentication information based on the first field, where the authentication information is used for access authentication of the bluetooth device distribution network.
  43. The method of any one of claims 38 to 42, wherein the first field comprises:
    uniform resource identifier Fu Haxi URI Hash field.
  44. The method of any one of claims 38 to 43, wherein the random device address remains unchanged in a single distribution flow;
    the random number remains unchanged in a single distribution flow.
  45. A bluetooth device, the bluetooth device comprising:
    a first processing unit configured to determine first information, the first information including: a random device address or random number of the bluetooth device;
    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 distribution network.
  46. The bluetooth device of claim 45, wherein the bluetooth device further comprises:
    And the first sending unit is configured to send a broadcast message, wherein the broadcast message carries the random equipment address.
  47. The bluetooth device of claim 45, wherein the bluetooth device further comprises:
    and the second sending unit is configured to send a broadcast message, and the first field of the broadcast message carries the random number.
  48. The bluetooth device of claim 47, wherein the first field comprises:
    uniform resource identifier Fu Haxi URI Hash field.
  49. A bluetooth device according to any of claims 45 to 48, wherein the random device address remains unchanged in a single distribution flow;
    the random number remains unchanged in a single distribution flow.
  50. A network distributor, the network distributor comprising:
    a first receiving unit configured to acquire second information including: a random device address of the bluetooth device, or a first field carrying a random number;
    the second information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
  51. The network distributor of claim 50, wherein,
    the first receiving unit is configured to receive a broadcast message, where the broadcast message carries the random device address.
  52. A network distributor as claimed in claim 50 or 51, wherein the network distributor further comprises:
    and the second processing unit is configured to perform access authentication of a distribution network on the Bluetooth equipment based on the random equipment address.
  53. The network distributor according to claim 52, wherein the second processing unit is configured to perform access authentication of the distribution network to the bluetooth device based on the number of uses of the random device address.
  54. The network distributor of claim 53, wherein the second processing unit is configured to confirm that the bluetooth device authentication fails if the number of uses of the random device address is greater than or equal to one;
    or if the number of times of using the random device address is zero and the UUID of the universal unique identifier of the Bluetooth device is legal, determining authentication information based on the random device address.
  55. The network distributor of claim 50, wherein,
    the first receiving unit is configured to receive a broadcast message, where the first field of the broadcast message carries the random number.
  56. A network distributor as claimed in claim 50 or 55, wherein the network distributor further comprises:
    and the third processing unit is configured to perform access authentication of a distribution network on the Bluetooth equipment based on the first field.
  57. The network distributor according to claim 56, wherein the third processing unit is configured to perform access authentication of the distribution network to the bluetooth device based on the number of uses of the value of the first field.
  58. The network distributor of claim 57, wherein the third processing unit is configured to confirm that the bluetooth device authentication failed if the number of uses of the value of the first field is greater than or equal to one;
    or if the number of times of use of the value of the first field is zero and the universal unique identifier UUID of the bluetooth device is legal, determining authentication information based on the first field.
  59. A network distributor as claimed in any one of claims 50 to 58 wherein the first field comprises:
    uniform resource identifier Fu Haxi URI Hash field.
  60. The network distributor of claim 50, or 51, or 55, wherein the network distributor further comprises:
    a third sending unit configured to send the third information to a cloud server, where the third information includes: the random device address, or the first field;
    and the third information is used for the cloud server to execute access authentication of the distribution network for the Bluetooth equipment.
  61. A network distributor as claimed in any one of claims 50 to 60 wherein the random device address remains unchanged in a single network distribution flow;
    the random number remains unchanged in a single distribution flow.
  62. A cloud server, the cloud server comprising:
    a second receiving unit configured to acquire third information including: a random device address of the bluetooth device, or a first field carrying a random number;
    and a fourth processing unit configured to perform access authentication of a distribution network for the bluetooth device based on the third information.
  63. The cloud server of claim 62, wherein if the third information includes a random device address of the bluetooth device, the fourth processing unit is configured to perform access authentication of a distribution network for the bluetooth device based on a number of uses of the random device address.
  64. The cloud server of claim 63, wherein if the number of uses of the random device address is greater than or equal to one, the fourth processing unit is configured to confirm that the bluetooth device authentication fails;
    and if the using times of the random equipment address is zero and the UUID of the Bluetooth equipment is legal, the fourth processing unit is configured to determine authentication information based on the random equipment address, wherein the authentication information is used for access authentication of the Bluetooth equipment distribution network.
  65. The cloud server of claim 62, wherein if the third information includes the first field, the fourth processing unit is configured to perform access authentication of a distribution network for the bluetooth device based on a number of uses of a value of the first field.
  66. The cloud server of claim 65, wherein if the number of uses of the value of the first field is greater than or equal to one, the fourth processing unit is configured to confirm that the bluetooth device authentication failed;
    or if the number of times of use of the value of the first field 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, where the authentication information is used for access authentication of the bluetooth device distribution network.
  67. The cloud server of any of claims 62 to 66, wherein the first field comprises:
    uniform resource identifier Fu Haxi URI Hash field.
  68. The cloud server of any of claims 62 to 67, wherein,
    the random equipment address is kept unchanged in a single network distribution process;
    the random number remains unchanged in a single distribution flow.
  69. A first cloud platform gateway, the first cloud platform gateway comprising:
    A third receiving unit configured to acquire fourth information including: a random device address of the bluetooth device, or a first field carrying a random number;
    the fourth information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
  70. The first cloud platform gateway of claim 69, wherein,
    the third receiving unit is configured to receive a broadcast message, where the broadcast message carries the random device address.
  71. The first cloud platform gateway of claim 69 or 70, wherein the first cloud platform gateway further comprises:
    and the fourth sending unit is configured to send the random equipment address to a first cloud platform, and the first cloud platform gateway corresponds to the first cloud platform.
  72. The first cloud platform gateway of claim 69, wherein,
    the third receiving unit is configured to receive a broadcast message, where the first field of the broadcast message carries the random number.
  73. The first cloud platform gateway of claim 69 or 72, wherein the first cloud platform gateway further comprises:
    and the fifth sending unit is configured to send the first field to a first cloud platform, and the first cloud platform gateway corresponds to the first cloud platform.
  74. The first cloud platform gateway of any of claims 69-73, wherein the first field comprises:
    uniform resource identifier Fu Haxi URI Hash field.
  75. The first cloud platform gateway of any of claims 69-74, wherein the fourth information further comprises:
    the bluetooth device corresponds to a company identification CID for the second cloud platform.
  76. The first cloud platform gateway of any of claims 69-75, wherein said random device address remains unchanged in a single distribution flow;
    the random number remains unchanged in a single distribution flow.
  77. A first cloud platform, the first cloud platform comprising:
    a fourth receiving unit configured to acquire fifth information including: a random device address of the bluetooth device, or a first field carrying a random number;
    the fifth information is used for determining authentication information, and the authentication information is used for access authentication of the Bluetooth equipment distribution network.
  78. The first cloud platform of claim 77, wherein said first cloud platform further comprises:
    a sixth sending unit, configured to send sixth information to a second cloud platform if the bluetooth device is not a device corresponding to the first cloud platform, where the sixth information includes: the random device address, or the first field;
    And the sixth information is used for determining authentication information by the second cloud platform, and the second cloud platform corresponds to the Bluetooth device.
  79. The first cloud platform of claim 77 or 78, wherein the first field comprises:
    uniform resource identifier Fu Haxi URI Hash field.
  80. The first cloud platform of any of claims 77-79, wherein the fifth information further comprises:
    the bluetooth device corresponds to a company identification CID for the second cloud platform.
  81. The first cloud platform of any of claims 77-80, wherein the random device address remains unchanged in a single distribution flow;
    the random number remains unchanged in a single distribution flow.
  82. A second cloud platform, the second cloud platform comprising:
    a fifth receiving unit configured to acquire sixth information including: a random device address of the bluetooth device, or a first field carrying a random number;
    and a fifth processing unit configured to perform access authentication of a distribution network for the bluetooth device based on the sixth information.
  83. The second cloud platform of claim 82, wherein,
    and the fifth processing unit is configured to execute access authentication of the distribution network for the Bluetooth device based on the use times of the random device address if the sixth information comprises the random device address of the Bluetooth device.
  84. The second cloud platform of claim 83, wherein,
    the fifth processing unit is configured to confirm that the bluetooth device authentication fails if the number of times of using the random device address is greater than or equal to one time;
    or if the number of times of using the random equipment address is zero and the UUID of the Bluetooth equipment is legal, determining authentication information based on the random equipment address, wherein the authentication information is used for access authentication of the Bluetooth equipment distribution network.
  85. The second cloud platform of claim 82, wherein,
    and the fifth processing unit is configured to execute access authentication of a distribution network on the Bluetooth device based on the use times of the value of the first field if the fifth information comprises the first field.
  86. The second cloud platform of claim 85, wherein,
    if the number of times of using the value of the first field is greater than or equal to one, confirming that the Bluetooth equipment fails to authenticate;
    or if the number of times of use of the value of the first field is zero and the UUID of the bluetooth device is legal, determining authentication information based on the first field, where the authentication information is used for access authentication of the bluetooth device distribution network.
  87. The second cloud platform of any of claims 82-86, wherein the first field comprises:
    uniform resource identifier Fu Haxi URI Hash field.
  88. The second cloud platform of any of claims 82 to 87, wherein the random device address remains unchanged in a single distribution flow;
    the random number remains unchanged in a single distribution flow.
  89. A bluetooth device comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,
    the processor is configured to execute the steps of the bluetooth device access authentication method according to any one of claims 1 to 5 when the computer program is run.
  90. A network distributor comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,
    the processor being configured to perform the steps of the bluetooth device access authentication method of any one of claims 6 to 17 when the computer program is run.
  91. A cloud server comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,
    the processor being configured to perform the steps of the bluetooth device access authentication method of any one of claims 18 to 24 when the computer program is run.
  92. A first cloud platform gateway comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,
    the processor being configured to perform the steps of the bluetooth device access authentication method of any one of claims 25 to 32 when the computer program is run.
  93. A first cloud platform comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,
    the processor being configured to perform the steps of the bluetooth device access authentication method of any one of claims 33 to 37 when the computer program is run.
  94. A second cloud platform comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,
    the processor being configured to perform the steps of the bluetooth device access authentication method of any one of claims 38 to 44 when the computer program is run.
  95. A storage medium storing an executable program which, when executed by a processor, implements the bluetooth device access authentication method according to any one of claims 1 to 5.
  96. A storage medium storing an executable program which, when executed by a processor, implements the bluetooth device access authentication method according to any one of claims 6 to 17.
  97. A storage medium storing an executable program which, when executed by a processor, implements the bluetooth device access authentication method according to any one of claims 18 to 24.
  98. A storage medium storing an executable program which, when executed by a processor, implements the bluetooth device access authentication method according to any one of claims 25 to 32.
  99. A storage medium storing an executable program which, when executed by a processor, implements the bluetooth device access authentication method according to any one of claims 33 to 37.
  100. A storage medium storing an executable program which, when executed by a processor, implements the bluetooth device access authentication method of any one of claims 38 to 44.
  101. A computer program product comprising computer program instructions for causing a computer to perform the bluetooth device access authentication method according to any of claims 1 to 5.
  102. A computer program product comprising computer program instructions which cause a computer to perform the bluetooth device access authentication method according to any of claims 6 to 17.
  103. A computer program product comprising computer program instructions which cause a computer to perform the bluetooth device access authentication method according to any of claims 18 to 24.
  104. A computer program product comprising computer program instructions which cause a computer to perform the bluetooth device access authentication method according to any of claims 25 to 32.
  105. A computer program product comprising computer program instructions which cause a computer to perform the bluetooth device access authentication method according to any of claims 33 to 37.
  106. A computer program product comprising computer program instructions for causing a computer to perform the bluetooth device access authentication method according to any of claims 38 to 44.
  107. A computer program for causing a computer to execute the bluetooth device access authentication method according to any one of claims 1 to 5.
  108. A computer program for causing a computer to perform the bluetooth device access authentication method according to any one of claims 6 to 17.
  109. A computer program for causing a computer to perform the bluetooth device access authentication method according to any one of claims 18 to 24.
  110. A computer program for causing a computer to perform the bluetooth device access authentication method according to any one of claims 25 to 32.
  111. A computer program for causing a computer to perform the bluetooth device access authentication method according to any one of claims 33 to 37.
  112. A computer program for causing a computer to perform the bluetooth device access authentication method according to any one of claims 38 to 44.
  113. A chip, comprising: a processor for calling and running a computer program from a memory, so that a device mounted with the chip performs the bluetooth device access authentication method according to any one of claims 1 to 5.
  114. A chip, comprising: a processor for calling and running a computer program from a memory, so that a device on which the chip is mounted performs the bluetooth device access authentication method according to any one of claims 6 to 17.
  115. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the bluetooth device access authentication method according to any of claims 18 to 24.
  116. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the bluetooth device access authentication method according to any one of claims 25 to 32.
  117. A chip, comprising: a processor for calling and running a computer program from a memory, so that a device on which the chip is mounted performs the bluetooth device access authentication method according to any one of claims 33 to 37.
  118. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the bluetooth device access authentication method according to any one of claims 38 to 44.
CN202080102514.1A 2020-09-24 2020-09-24 Bluetooth equipment access authentication method, electronic equipment and storage medium Pending CN116158100A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/117522 WO2022061668A1 (en) 2020-09-24 2020-09-24 Bluetooth device access authentication method, and electronic device and storage medium

Publications (1)

Publication Number Publication Date
CN116158100A true CN116158100A (en) 2023-05-23

Family

ID=80846037

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202080102514.1A Pending CN116158100A (en) 2020-09-24 2020-09-24 Bluetooth equipment access authentication method, electronic equipment and storage medium

Country Status (2)

Country Link
CN (1) CN116158100A (en)
WO (1) WO2022061668A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114666154B (en) * 2022-04-08 2023-11-24 深圳市欧瑞博科技股份有限公司 Device communication method, device, gateway, device, system, medium and product

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3466193A4 (en) * 2016-05-30 2019-11-06 Left of The Dot Media Inc. Method for establishing network clusters between networked devices
CN110139274A (en) * 2019-02-28 2019-08-16 上海愚境科技有限公司 A kind of method for authenticating of bluetooth equipment, electronic equipment and can storage medium
CN110300396A (en) * 2019-05-27 2019-10-01 苏宁智能终端有限公司 The WIFI distribution method, apparatus and terminal of smart machine
CN110418322A (en) * 2019-08-09 2019-11-05 四川虹美智能科技有限公司 Distribution method and system, a kind of node based on bluetooth Mesh network
CN110489958B (en) * 2019-08-27 2021-03-05 上海银基信息安全技术股份有限公司 Identity authentication method, positioning device and terminal to be unlocked

Also Published As

Publication number Publication date
WO2022061668A1 (en) 2022-03-31

Similar Documents

Publication Publication Date Title
US11743812B2 (en) Methods and apparatuses for reconfiguring a data connection
US10798647B2 (en) Network slice selection
US10075840B2 (en) Device and operation method thereof
CN111107520B (en) Mechanism to activate and manage standalone devices for cellular services
CN112637785B (en) Method and apparatus for multicast transmission
WO2021031030A1 (en) Communication method and communication apparatus
WO2012174722A1 (en) Method and apparatus for providing a virtual sim for mobile communications
KR20200019743A (en) Systems and Methods for Delivering Radio Applications to Reconfigurable Radio Equipment
US10904763B2 (en) Network access method and device
EP4061024A1 (en) D2d communication method, apparatus and system
WO2021022460A1 (en) Session verification method, electronic device, and storage medium
JP2023552243A (en) Method and device for transmitting user identifiers
CN116158100A (en) Bluetooth equipment access authentication method, electronic equipment and storage medium
WO2021056131A1 (en) Radio communication method, terminal device, and network device
WO2021088007A1 (en) Wireless communication method, terminal device, and network device
EP3962209A1 (en) Data processing method, apparatus and system
CN115037705A (en) Communication method and apparatus
EP4398610A1 (en) Communication method and apparatus
US11881961B2 (en) Communication method and related apparatus
US20240244711A1 (en) Communication method and apparatus
WO2022021433A1 (en) Method for device access authentication, terminal device, and cloud platform
US20230276231A1 (en) Authentication Between Wireless Devices and Edge Servers
WO2023202337A1 (en) Communication method and apparatus
CN115706933A (en) Communication method and device
CN116156476A (en) Request method, request device, request apparatus and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination