Access authentication method, device, equipment and storage medium

ECDH calculation is performed through the first platform cloud and Bluetooth Mesh devices, and a shared root key is generated, which solves the problem of leakage of Static OOB authentication information in cross-platform access authentication of Bluetooth Mesh devices, and improves the security of the access process.

CN115669209BActive Publication Date: 2024-11-01GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080101163.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-07-22
Publication Date
2024-11-01
Estimated Expiration
2040-07-22

AI Technical Summary

Technical Problem

During the cross-platform access authentication process of Bluetooth Mesh devices, there is a risk of leakage of Static OOB authentication information AuthValue, affecting security.

Method used

ECDH calculation is performed through the first platform cloud and Bluetooth Mesh device, and a shared root key is generated, which is used to generate network distribution authentication information, avoid the second platform gateway to exchange confirmation values ​​and reduce the risk of leakage.

Benefits of technology

Enhanced security during Bluetooth Mesh device access, prevents the leakage of Static OOB certification information, and ensures the security certification process of the device.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115669209B_ABST
    Figure CN115669209B_ABST
Patent Text Reader

Abstract

The present application discloses an access authentication method, device, equipment and storage medium, and relates to the field of network technology. The method is applied to a first platform cloud, which is a cloud server that stores authentication information of a Bluetooth Mesh device. The method includes: performing an elliptic curve algorithm ECDH calculation with the Bluetooth Mesh device to generate a shared root key ECDHSecret, and the Bluetooth Mesh device is configured to access the network by a second platform gateway; based on the shared root key, generating network adapter authentication information, and the network adapter authentication information is used for access authentication with the Bluetooth Mesh device.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of network technology, and in particular to an access authentication method, device, equipment and storage medium. Background Art

[0002] Bluetooth wireless mesh (Mesh) technology is a many-to-many key technology based on Bluetooth. Bluetooth Mesh devices based on Bluetooth Mesh technology can perform access authentication across different platforms across domains.

[0003] For example, the authentication information (AuthValue) of the Bluetooth Mesh device belonging to Company E is stored in the B platform cloud, and the Bluetooth Mesh device is configured to access the network by the A platform gateway. In order to perform cross-platform access authentication, the A platform gateway and the A platform cloud corresponding to the A platform gateway need to help transmit the configuration end confirmation value (provisioning confirmation) corresponding to the B platform cloud to realize the access authentication of the Bluetooth Mesh device through the B platform cloud.

[0004] In the related technology, the A platform gateway and the Bluetooth Mesh device perform elliptic curve algorithm (Elliptic Curves Diffie-Hellman, ECDH) calculation to obtain a shared root key (ECDHSecret). In this case, there is a possibility that the A platform gateway can reverse the AuthValue, affecting the security of the authentication information of the Bluetooth Mesh device. Summary of the invention

[0005] The embodiments of the present application provide an access authentication method, apparatus, device and storage medium to avoid the risk of leakage of Static OOB authentication information AuthValue of Bluetooth Mesh devices and ensure the security of Bluetooth Mesh devices during access. The technical solution is as follows.

[0006] According to one aspect of the present application, an access authentication method is provided, which is applied to a first platform cloud, where the first platform cloud is a cloud server storing authentication information of a Bluetooth Mesh device, and the method includes:

[0007] Perform ECDH calculation with the Bluetooth Mesh device to generate a shared root key ECDHSecret, and the Bluetooth Mesh device is configured to join the network by the second platform gateway;

[0008] Based on the shared root key, network adapter authentication information is generated, and the network adapter authentication information is used to perform access authentication with the Bluetooth Mesh device.

[0009] According to one aspect of the present application, an access authentication method is provided, which is applied to a Bluetooth wireless mesh network Mesh device, and the method includes:

[0010] Perform ECDH calculation with the First Platform Cloud to generate a shared root key ECDHSecret;

[0011] Among them, the first platform cloud is a cloud server that stores the authentication information of the Bluetooth Mesh device, the Bluetooth Mesh device is configured to enter the network by the second platform gateway, and the shared root key is used to generate a device confirmation value deviceconfirmation, and the device confirmation value is used for access authentication with the first platform cloud.

[0012] According to one aspect of the present application, an access authentication method is provided, which is applied to a second platform gateway.

[0013] The second platform gateway is used to configure the Bluetooth wireless mesh network Mesh device to join the network, the Bluetooth Mesh device stores the authentication information of the Bluetooth Mesh device by the first platform cloud, the cloud server corresponding to the second platform gateway is the second platform cloud, and the method includes:

[0014] Receiving, through the second platform cloud, network adapter authentication information whose source address is the first platform cloud, wherein the network adapter authentication information is used for access authentication with the Bluetooth Mesh device;

[0015] Forwarding the network adapter authentication information to the Bluetooth Mesh device;

[0016] Among them, the network adapter authentication information is generated by the first platform cloud according to the shared root key ECDHSecret, and the shared root key is obtained by performing elliptic curve algorithm ECDH calculation on the first platform cloud and the Bluetooth Mesh device.

[0017] According to one aspect of the present application, an access authentication method is provided, which is applied to a first platform cloud, where the first platform cloud is a cloud server storing authentication information of a Bluetooth Mesh device, and the method includes:

[0018] In response to the Bluetooth Mesh device starting a network configuration process, generating authentication information AuthValue corresponding to this network configuration process, where the authentication information is the same as the authentication information at the Bluetooth Mesh device;

[0019] Sending the authentication information, where the destination address of the authentication information is a second platform gateway, and the second platform gateway is used to configure the Bluetooth Mesh device into the network;

[0020] The authentication information is used by the second platform gateway to authenticate the Bluetooth Mesh device.

[0021] According to one aspect of the present application, an access authentication method is provided, which is applied to a second platform gateway, wherein the second platform gateway is used to configure a Bluetooth wireless mesh network Mesh device to access the network, wherein the Bluetooth Mesh device stores the authentication information of the Bluetooth Mesh device by a first platform cloud, and the cloud server corresponding to the second platform gateway is a second platform cloud, wherein the method includes:

[0022] Receiving, through the second platform cloud, authentication information AuthValue sent by the first platform cloud;

[0023] Generate network adapter authentication information based on the authentication information, and use the network adapter authentication information to perform access authentication with the Bluetooth Mesh device.

[0024] According to one aspect of the present application, an access authentication method is provided, which is applied to a Bluetooth Mesh device, wherein the Bluetooth Mesh device is configured to access the network by a second platform gateway, and the Bluetooth Mesh device stores authentication information of the Bluetooth Mesh device by a first platform cloud, and the method includes:

[0025] In response to the Bluetooth Mesh device starting a network configuration process, authentication information AuthValue corresponding to this network configuration process is generated, and the authentication information is the same as the authentication information at the first platform cloud.

[0026] According to one aspect of the present application, there is provided an access authentication device, which is applied to a first platform cloud, wherein the first platform cloud is a cloud server storing authentication information of a Bluetooth Mesh device, and the device comprises: a generation module;

[0027] The generation module is used to perform ECDH calculation with the Bluetooth Mesh device to generate a shared root key ECDHSecret, and the Bluetooth Mesh device is configured to access the network by the second platform gateway;

[0028] The generation module is used to generate network provisioner authentication information according to the shared root key, and the network provisioner authentication information is used to perform access authentication with the Bluetooth Mesh device.

[0029] According to one aspect of the present application, there is provided an access authentication device, which is applied to a Bluetooth Mesh device, and the device includes: a generating module;

[0030] The generation module is used to perform ECDH calculation with the first platform cloud to generate a shared root key ECDHSecret;

[0031] Among them, the first platform cloud is a cloud server that stores the authentication information of the Bluetooth Mesh device, the Bluetooth Mesh device is configured to enter the network by the second platform gateway, and the shared root key is used to generate a device confirmation value deviceconfirmation, and the device confirmation value is used for access authentication with the first platform cloud.

[0032] According to one aspect of the present application, an access authentication device is provided, which is applied to a second platform gateway, wherein the second platform gateway is used to configure a Bluetooth wireless mesh network Mesh device to access the network, wherein the Bluetooth Mesh device stores the authentication information of the Bluetooth Mesh device by a first platform cloud, and the cloud server corresponding to the second platform gateway is a second platform cloud, wherein the device includes: a receiving module and a sending module;

[0033] The receiving module is used to receive, through the second platform cloud, network adapter authentication information whose source address is the first platform cloud, where the network adapter authentication information is used to perform access authentication with the Bluetooth Mesh device;

[0034] The sending module is used to forward the network adapter authentication information to the Bluetooth Mesh device;

[0035] Among them, the network adapter authentication information is generated by the first platform cloud according to the shared root key ECDHSecret, and the shared root key is obtained by performing elliptic curve algorithm ECDH calculation on the first platform cloud and the Bluetooth Mesh device.

[0036] According to one aspect of the present application, an access authentication device is provided, which is applied to a first platform cloud, wherein the first platform cloud is a cloud server storing authentication information of a Bluetooth Mesh device, and the device includes: a generating module and a sending module;

[0037] The generating module is used to generate authentication information AuthValue corresponding to the current network configuration process in response to the Bluetooth Mesh device starting the network configuration process, wherein the authentication information is the same as the authentication information at the Bluetooth Mesh device;

[0038] The sending module is used to send the authentication information, the destination address of the authentication information is the second platform gateway, and the second platform gateway is used to configure the Bluetooth Mesh device to join the network;

[0039] The authentication information is used by the second platform gateway to authenticate the Bluetooth Mesh device.

[0040] According to one aspect of the present application, an access authentication device is provided, which is applied to a second platform gateway, wherein the second platform gateway is used to configure a Bluetooth wireless mesh network Mesh device to access the network, wherein the Bluetooth Mesh device stores the authentication information of the Bluetooth Mesh device by a first platform cloud, and the cloud server corresponding to the second platform gateway is a second platform cloud, wherein the device includes: a receiving module and a generating module;

[0041] The receiving module is used to receive the authentication information AuthValue sent by the first platform cloud through the second platform cloud;

[0042] The generating module is used to generate network adapter authentication information according to the authentication information, and the network adapter authentication information is used to perform access authentication with the Bluetooth Mesh device.

[0043] According to one aspect of the present application, an access authentication device is provided, which is applied to a Bluetooth Mesh device, wherein the Bluetooth Mesh device is configured to access the network by a second platform gateway, and the Bluetooth Mesh device stores authentication information of the Bluetooth Mesh device by a first platform cloud, and the device includes: a generation module;

[0044] The generation module is used to generate authentication information AuthValue corresponding to the current network configuration process in response to the Bluetooth Mesh device starting the network configuration process, and the authentication information is the same as the authentication information at the first platform cloud.

[0045] According to one aspect of the present application, a first platform cloud is provided, comprising: a processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the access authentication method as described in the above aspects.

[0046] According to one aspect of the present application, a second platform gateway is provided, which includes: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the access authentication method as described in the above aspects.

[0047] According to one aspect of the present application, a Bluetooth Mesh device is provided, comprising: a processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the access authentication method as described in the above aspects.

[0048] According to one aspect of the present application, a computer-readable storage medium is provided, in which executable instructions are stored. The executable instructions are loaded and executed by a processor to implement the access authentication method as described in the above aspect.

[0049] According to one aspect of the present application, a computer program product or a computer program is provided, which includes computer instructions, which are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the access authentication method described in the above aspect.

[0050] The technical solution provided by the embodiments of the present application includes at least the following beneficial effects:

[0051] By performing ECDH calculation between the first platform cloud and the Bluetooth Mesh device to generate a shared root key, the risk of leakage of the StaticOOB authentication information AuthValue of the Bluetooth Mesh device is avoided when the ECDH calculation is performed between the second platform gateway and the Bluetooth Mesh device, because confirmation values ​​(such as configuration end confirmation values) are exchanged through the second platform gateway and the second platform gateway stores the shared root key generated by the ECDH calculation, thereby ensuring the security of the Bluetooth Mesh device during access. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0053] Figure 1 It is a block diagram of a Bluetooth Mesh device cross-platform access authentication system provided by an exemplary embodiment of the present application;

[0054] Figure 2 is a flow chart of a method for accessing and authenticating a device across different platforms provided by an exemplary embodiment of the related art;

[0055] Figure 3 is a flow chart of an access authentication method provided by an exemplary embodiment of the present application;

[0056] Figure 4 is a flow chart of an access authentication method provided by an exemplary embodiment of the present application;

[0057] Figure 5is a flow chart of an access authentication method provided by an exemplary embodiment of the present application;

[0058] Figure 6 is a flow chart of an access authentication method provided by an exemplary embodiment of the present application;

[0059] Figure 7 is a flow chart of an access authentication method provided by an exemplary embodiment of the present application;

[0060] Figure 8 is a flow chart of an access authentication method provided by an exemplary embodiment of the present application;

[0061] Fig. 9 is a flow chart of an access authentication method provided by an exemplary embodiment of the present application;

[0062] Fig.10 is a structural block diagram of an access authentication device provided by an exemplary embodiment of the present application;

[0063] Fig.11 is a structural block diagram of an access authentication device provided by an exemplary embodiment of the present application;

[0064] Fig.12 is a structural block diagram of an access authentication device provided by an exemplary embodiment of the present application;

[0065] Fig.13 is a structural block diagram of an access authentication device provided by an exemplary embodiment of the present application;

[0066] Fig.14 is a structural block diagram of an access authentication device provided by an exemplary embodiment of the present application;

[0067] Fig.15 is a structural block diagram of an access authentication device provided by an exemplary embodiment of the present application;

[0068] Fig.16 It is a schematic diagram of the structure of a server provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0069] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0070] First, the nouns involved in the embodiments of the present application are briefly introduced:

[0071] Bluetooth Mesh Network:

[0072] It is a low-power Bluetooth network topology used to establish many-to-many device communications. It allows the creation of large networks based on multiple devices. The network can contain dozens, hundreds or even thousands of Bluetooth Mesh devices, which can communicate with each other.

[0073] For a device to become a member of a Bluetooth Mesh network, it needs to go through a security process called "provisioning" to add the device to the Bluetooth Mesh network. Devices that are members of a Bluetooth Mesh network are called "nodes", and devices that do not constitute nodes are called "devices". The provisioning process will turn an ordinary "device" into a "node", making it a formal member of the Bluetooth Mesh network.

[0074] The process of starting configuration mainly includes five stages: 1 sending Beacon signal, 2 invitation, 3 exchanging public keys, 4 authentication, and 5 starting configuration data distribution.

[0075] For the authentication phase, there are three available verification methods: Output Out-Of-Band (Output OOB), Input OOB, and Static OOB or No OOB.

[0076] In actual product forms, due to considerations of equipment cost and network configuration convenience, few devices use the Output / Input OOB method (which requires the device to have input or output capabilities and requires human participation in the process), while the NoOOB method is not secure, and most devices use the StaticOOB verification method. In the embodiment of the present application, the verification method used by the device is StaticOOB.

[0077] Figure 1 A block diagram of a Bluetooth Mesh device cross-platform access authentication system provided by an exemplary embodiment of the present application is shown. The system may include: a Bluetooth Mesh device 12, a second platform gateway 141, a second platform cloud 142 and a first platform cloud 16.

[0078] The Bluetooth Mesh device 12 is a device that supports Bluetooth technology and can access a Bluetooth Mesh network. The Bluetooth Mesh device includes various types of IoT devices, such as light bulbs, speakers, mobile phones, etc., which are not limited in the present application embodiment.

[0079] The Bluetooth Mesh device 12 is configured to access the network by the second platform gateway 141, and the cloud server corresponding to the second platform gateway 141 is the second platform cloud 142. The second platform gateway 141 is connected to the second platform cloud 142 via a wired or wireless network. Optionally, the second platform cloud gateway 141 receives data from the Bluetooth Mesh device 12, calculates and processes the data, and sends the data to the second platform cloud 142, which is stored or further processed by the second platform cloud 142.

[0080] The Bluetooth Mesh device 12 is developed based on the first platform cloud 16 , and the authentication information of the Bluetooth Mesh device 12 is stored in the first platform cloud 16 .

[0081] There is a communication link between the second platform cloud 142 and the first platform cloud 16. Optionally, the second platform cloud 142 sends the information required by the Bluetooth Mesh device 12 in the authentication process with the first platform cloud 16 to the first platform cloud 16; or, forwards the information required by the Bluetooth Mesh device 12 in the authentication process with the first platform cloud 16 to the second platform gateway 141.

[0082] Among them, the above-mentioned second platform cloud 142 and the first platform cloud 16 are cloud computing resource pools in the field of cloud technology, and various types of virtual resources are deployed in the resource pool for external customers to choose to use. The cloud computing resource pool mainly includes: computing devices (virtualized machines, including operating systems), storage devices, and network devices. It can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), and big data and artificial intelligence platforms.

[0083] Figure 2 A flow chart of a method for accessing and authenticating a device across different platforms in a related art is shown, the method comprising:

[0084] Step 21: The user uses voice or APP to activate and scan the A platform gateway.

[0085] Step 22, the E company's device (developed based on the B platform) broadcasts the Bluetooth Mesh unprovisioned broadcast packet according to the specification.

[0086] The broadcast packet includes the company identifier (CID) of the B platform.

[0087] Step 23, the A platform gateway queries the device type.

[0088] After obtaining the unconfigured network broadcast information broadcast by the E company's equipment, the A platform gateway uploads the information to the A platform cloud to query the type of the device.

[0089] Step 23.1, the A platform cloud determines whether it is a device of this platform.

[0090] Step 23.2, platform A queries the cloud for the device's corresponding platform information.

[0091] After receiving the device information reported by the A platform gateway, the A platform cloud determines through the CID that the E company's equipment is not a device developed based on the A platform and requires authorization from other platforms.

[0092] Step 23.3, the A platform cloud obtains the platform information corresponding to the CID through the interconnection server.

[0093] Optionally, the platform information includes information such as the B platform authority management server (AuthServer).

[0094] Step 23.4, the A platform cloud queries the B platform cloud for the device type.

[0095] Step 23.5, the A platform cloud obtains the device type from the B platform cloud.

[0096] Step 24, the A platform cloud forwards the device type to the A platform gateway.

[0097] Step 25, the A platform gateway announces the device and device type to the user.

[0098] Step 26, user input: connect device.

[0099] Step 27, the A platform gateway and the E company device perform the connection and invitation process (Link&Invitation).

[0100] Step 27.1, the A platform gateway sends a Provisioning Start message to the E company device.

[0101] Step 27.2, the A platform gateway sends the provisioning public key (Provisoning Public Key) to the E company device.

[0102] In step 27.3, the E company device sends the device public key to the A platform gateway.

[0103] In step 27.4, the E company device and the A platform gateway perform ECDH calculation to generate a confirmation key (ConfirmationKey).

[0104] Step 27.5, the A platform gateway reports the confirmation key generated during the device authentication process to the A platform cloud.

[0105] Step 27.6, Platform A cloud reports the confirmation key to Platform B cloud.

[0106] Step 27.7, the A platform cloud obtains the provisioner confirmation value (provisionerconfirmation) and the provisioner random number (provisioner random) required for authentication through the B platform cloud.

[0107] Step 27.8, the A platform cloud forwards the configuration end confirmation value and the configuration end random number to the A platform gateway.

[0108] Step 27.9: The A platform gateway sends the configuration end confirmation value to the E company device.

[0109] Step 27.10, the E company's device returns a device confirmation value (deviceconfirmation) from the device side.

[0110] Step 27.11, the A platform gateway sends the configuration end random number to the E company device.

[0111] Step 27.12: Company E's equipment verifies the value confirmed by the configuration end.

[0112] Step 27.13, the verification is passed, and the E company's device returns the device random number (devicerandom) on the device side.

[0113] Step 27.14, the A platform gateway reports the device confirmation value and device random number of the device to the A platform cloud.

[0114] Step 27.15, the A platform cloud sends the device confirmation value and the device random number to the B platform cloud.

[0115] Step 27.16, Platform B performs authentication verification on the cloud.

[0116] Step 27.17, Platform B Cloud returns the authentication result and device information.

[0117] The device information includes the control functions and control instructions supported by the device.

[0118] Step 27.18, A platform cloud storage device information.

[0119] Step 27.19, the A platform cloud forwards the authentication result to the A platform gateway.

[0120] Step 28: The A platform gateway broadcasts the authentication result to the user.

[0121] Optionally, in the above steps, the confirmation key (ConfirmationKey), the configuration end confirmation value (provisionerconfirmation), and the device confirmation value (deviceconfirmation) are calculated as follows, which is derived from Bluetooth MeshProfilev1.0.1.

[0122] ConfirmationProvisioner=AES-CMAC ConfirmationKey (RandomProvisioner||AuthValue);

[0123] ConfirmationDevice = AES-CMAC ConfirmationKey (RandomDevice||AuthValue);

[0124] ConfirmationKey=k1(ECDHSecret, ConfirmationSalt, "prck");

[0125] ConfirmationSalt=s1(ConfirmationInputs);

[0126] ConfirmationInputs=ProvisioningInvitePDUValue||ProvisioningCapabilitiesPDUValue||ProvisioningStartPDUValue||PublicKeyProvisioner||PublicKeyDevice;

[0127] ECDHSecret=P-256 (private key, peer public key).

[0128] From the above calculation method, it can be seen that since the configuration-end confirmation value generated by the B platform cloud is related to the confirmation key and AuthValue, the confirmation key is saved at the A platform gateway. When the configuration-end confirmation value is received, the configuration-end confirmation value can be decrypted to derive the device's authentication information AuthValue, resulting in the leakage of the device's authentication information.

[0129] To solve the above problems, the present invention provides two different technical solutions:

[0130] 1) ECDH calculation is performed by B platform cloud and Bluetooth Mesh device.

[0131] 2) Each time the network is configured, Static OOB information (ie, AuthValue) is dynamically generated.

[0132] It is understandable that in technical solution 1), the StaticOOB information (ie, AuthValue) is constant, such as being pre-generated and directly burned into the Bluetooth Mesh device at the factory. In technical solution 2), the StaticOOB information (ie, AuthValue) is regenerated each time the network is configured.

[0133] The following is an exemplary description of the above two technical solutions.

[0134] Technical solution 1)

[0135] Figure 3 A flowchart of an access authentication method provided by an exemplary embodiment of the present application is shown. The method can be applied to Figure 1 In the Bluetooth Mesh device cross-platform access authentication system shown, the method includes:

[0136] In step 310, the first platform cloud and the Bluetooth Mesh device perform ECDH calculation to generate a shared root key (ECDHSecret).

[0137] Bluetooth Mesh devices are devices that support access to Bluetooth Mesh networks. Bluetooth Mesh devices include various types of home devices (such as lights), industrial assets (such as examination equipment in hospitals), etc.

[0138] The platform corresponding to the first platform cloud is a platform for developing Bluetooth Mesh devices. The first platform cloud stores authentication information (AuthValue) of Bluetooth Mesh devices.

[0139] The second platform gateway is a node that supports adding Bluetooth Mesh devices to the Bluetooth Mesh network. The Bluetooth Mesh device is configured to access the network by the second platform gateway. The cloud server corresponding to the second platform gateway is the second platform cloud and the first platform cloud. The first platform cloud and the second platform cloud are two different platform clouds and belong to different platforms. Optionally, the Bluetooth Mesh device performs a connection and invitation process (Link&Invitation) with the second platform gateway, and the second platform obtains the information required by the Bluetooth Mesh device in the authentication process from the first platform cloud.

[0140] ECDH is a DH (Diffie-Hellman) key exchange algorithm based on the Elliptic Curve Cryptosystem (ECC). The two parties can negotiate a key without sharing any secrets. This algorithm inherits the outstanding advantages of ECC, such as short key length, fast calculation speed and good security performance.

[0141] Unlike the related art, where the ECDH calculation is performed by the second platform gateway and the Bluetooth Mesh device, Figure 3 In the illustrated embodiment, the ECDH calculation process is transferred to the first platform cloud, and the ECDH calculation is performed by the first platform cloud and the Bluetooth Mesh device, and a shared root key is generated at both the first platform cloud and the Bluetooth Mesh device.

[0142] Optionally, both the first platform cloud and the Bluetooth Mesh device support the FIPS P-256 elliptic curve algorithm, and can perform ECDH calculations to generate a shared root key. A secure channel is created through asymmetric encryption based on the algorithm to complete the remaining startup configuration process. Exemplarily, the calculation formula for the shared root key is: ECDHSecret = P-256 (private key, peer public key). Among them, private key is the private key of each party, and peer public key is the public key of each party.

[0143] Optionally, the shared root key is used to derive other keys, such as the device key (DevKey), session key (SessionKey), and session random number (SessionNonce).

[0144] Step 320: The first platform cloud generates network adapter authentication information based on the shared root key.

[0145] The network adapter authentication information is used for access authentication with Bluetooth Mesh devices.

[0146] During the Bluetooth Mesh device access authentication process, the Bluetooth Mesh device and the first platform cloud need to verify the authentication information generated by the other party based on the shared device authentication information AuthValue. If the verification passes, continue with the next process. The network adapter authentication information is the configuration end authentication information corresponding to the first platform cloud. The destination address of the network adapter authentication information is the Bluetooth Mesh device, and the Bluetooth Mesh device can check and verify the network adapter authentication information.

[0147] Optionally, the Bluetooth Mesh device generates a device confirmation value based on the shared root key. The device confirmation value is device-side authentication information corresponding to the Bluetooth Mesh device.

[0148] Optionally, the network adapter authentication information includes a configuration end confirmation value. Step 310 includes: the first platform cloud generates a confirmation key based on the shared root key; generates a configuration end random number, and the configuration end random number and the authentication information of the Bluetooth Mesh device form a first plaintext; and uses the confirmation key to encrypt the first plaintext to generate a configuration end confirmation value.

[0149] Exemplarily, the calculation formula of the configuration end confirmation value is: ConfirmationProvisioner=AES-CMACConfirmationKey(RandomProvisioner||AuthValue), wherein AES-CMAC is an encryption algorithm.

[0150] Optionally, the first platform cloud generates a confirmation key based on the shared root key, including: the first platform cloud obtains a confirmation input value (ConfirmationInputs); generates a confirmation salt value (ConfirmationSalt) based on the confirmation input value; generates a confirmation key based on the confirmation salt value, the shared root key and the character string "prck".

[0151] Exemplarily, the calculation formula of the confirmation key is: ConfirmationKey=k1(ECDHSecret, ConfirmationSalt, "prck").

[0152] Optionally, the first platform cloud obtains the confirmation input value, including: the first platform cloud receives configuration information whose source address is the gateway of the second platform; receives the device public key of the Bluetooth Mesh device as the source address; generates the configuration end public key; generates the confirmation input value according to the configuration information, the device public key and the configuration end public key; wherein the configuration information includes: at least one of the configuration invitation protocol data unit value (ProvisioningInvitePDUValue), the configuration capability protocol data unit value (ProvisioningCapabilitiesPDUValue), and the configuration start protocol data unit value (ProvisioningStartPDUValue).

[0153] Exemplarily, the calculation formula for confirming the input value is: ConfimationInputs=ProvisioningInvitePDUValue||ProvisioningCapabilitiesPDUValue||ProvisioningStartPDUValue||PublicKeyProvisioner||PublicKeyDevice.

[0154] Optionally, the second platform includes a second platform gateway and a second platform cloud. The process of the second platform sending configuration information includes: the second platform gateway sends the configuration information, the destination address of the configuration information is the first platform cloud; the second platform cloud forwards the configuration information to the first platform cloud.

[0155] Similarly, the device public key of the Bluetooth Mesh device will also be forwarded through the second platform, including: receiving the device public key with the source address as the Bluetooth Mesh device through the second platform gateway; the second platform gateway forwarding the device public key to the second platform cloud; the second platform cloud forwarding the device public key to the first platform cloud.

[0156] The network provisioner and the Bluetooth Mesh device to be provisioned need to exchange public keys. When the first platform cloud and the Bluetooth Mesh device perform ECDH calculation, the first platform cloud sends the configuration end public key generated by itself to the Bluetooth Mesh device. Optionally, before step 310, the first platform cloud sends the above configuration end public key, and the destination address of the configuration end public key is the Bluetooth Mesh device.

[0157] Optionally, the second platform includes a second platform gateway and a second platform cloud, and the configuration end public key will reach the Bluetooth Mesh device via forwarding by the second platform, including: receiving the configuration end public key whose source address is the first platform cloud through the second platform cloud; the second platform cloud forwards the configuration end public key to the second platform gateway; the second platform gateway forwards the configuration end public key to the Bluetooth Mesh device.

[0158] Step 330: The first platform cloud sends the network adapter authentication information to the second platform cloud.

[0159] The first platform cloud sends the network distributor authentication information to the second platform cloud, and the second platform cloud receives the network distributor authentication information from the first platform cloud accordingly.

[0160] Step 340: The second platform cloud forwards the network adapter authentication information to the second platform gateway.

[0161] Step 350: The second platform gateway forwards the network adapter authentication information to the Bluetooth Mesh device.

[0162] Through the forwarding of the second platform cloud and the second platform gateway, the network adapter authentication information is transmitted from the source address first platform cloud to the destination address Bluetooth Mesh device.

[0163] Optionally, the Bluetooth Mesh device verifies the network provisioning device authentication information. If the verification is successful, the network provisioning process continues; otherwise, the network provisioning process is terminated.

[0164] Optionally, the first platform cloud will also verify the authentication information (such as device confirmation value) from the device side of the Bluetooth Mesh device accordingly. After the verification is completed, the authentication result needs to be fed back. When feeding back the authentication result, the first platform cloud sends the device key, session key and session random number to the second platform. In the case of ECDH calculation between the first platform cloud and the Bluetooth Mesh device, the first platform cloud generates the above three types of data and sends them to the second platform for the second platform to use the above three types of data later.

[0165] Optionally, the second platform includes a second platform gateway and a second platform cloud, and the process of the second platform receiving the above three data includes: receiving the device key, session key and session random number whose source address is the first platform cloud through the second platform cloud; the second platform cloud forwards the device key, session key and session random number to the second platform gateway.

[0166] In summary, the method provided in this embodiment generates a shared root key by performing ECDH calculation by the first platform cloud and the Bluetooth Mesh device, thereby avoiding the risk of leakage of the StaticOOB authentication information AuthValue of the Bluetooth Mesh device due to the exchange of confirmation values ​​(such as configuration end confirmation values) through the second platform gateway and the Bluetooth Mesh device when the ECDH calculation is performed by the second platform gateway and the Bluetooth Mesh device, and the second platform gateway stores the shared root key generated by the ECDH calculation, thereby ensuring the security of the Bluetooth Mesh device during the access process.

[0167] Based on Figure 3 In an optional embodiment, Figure 4 A flowchart of an access authentication method provided by an exemplary embodiment of the present application is shown. The method can be applied to Figure 1 In the Bluetooth Mesh device cross-platform access authentication system shown, the method includes:

[0168] Step 41, the user uses voice or APP to activate and scan the second platform gateway.

[0169] Step 42: The Bluetooth Mesh device (developed based on the first platform) broadcasts a Bluetooth Mesh unprovisioned broadcast packet according to the specification.

[0170] The broadcast packet includes the CID of the first platform.

[0171] Step 43: The second platform gateway queries the device type.

[0172] After the second platform gateway obtains the unconfigured network broadcast information broadcast by the Bluetooth Mesh device, it uploads the information to the second platform cloud to query the type of the device.

[0173] Step 43.1, the second platform cloud determines whether it is a device on this platform.

[0174] Step 43.2, the second platform cloud queries the CID corresponding to the device.

[0175] After receiving the device information reported by the second platform gateway, the second platform cloud determines through CID that the Bluetooth Mesh device is not a device developed based on the second platform and requires authorization from other platforms.

[0176] Step 43.3, the second platform cloud obtains the platform information corresponding to the CID through the interconnection server.

[0177] Optionally, the platform information includes information such as the first platform rights management server.

[0178] Step 43.4, the second platform cloud queries the first platform cloud for the device type.

[0179] Step 43.5, the second platform cloud obtains the device type from the first platform cloud.

[0180] Step 44: The second platform cloud forwards the device type to the second platform gateway.

[0181] Step 45: The second platform gateway announces the device and device type to the user.

[0182] Step 46, user input: connect device.

[0183] Step 47: The second platform gateway and the Bluetooth Mesh device are connected and invited.

[0184] Step 47.1, the second platform gateway reports the configuration invitation protocol data unit value, the configuration capability protocol data unit value and the configuration start protocol data unit value to the second platform cloud.

[0185] Step 47.2, the second platform cloud reports the configuration invitation protocol data unit value, the configuration capability protocol data unit value and the configuration start protocol data unit value to the first platform cloud.

[0186] Step 47.3, the first platform cloud generates a configuration end public key and reports it to the second platform cloud.

[0187] Step 47.4, the second platform cloud sends the configuration end public key to the second platform gateway.

[0188] Step 47.5, the second platform gateway starts sending configuration to the Bluetooth Mesh device.

[0189] Step 47.6: The second platform gateway sends the configuration end public key to the Bluetooth Mesh device.

[0190] Step 47.7, the Bluetooth Mesh device sends the device public key to the second platform gateway.

[0191] Step 47.8: The second platform gateway sends the device public key to the second platform cloud.

[0192] Step 47.9, the second platform cloud sends the device public key to the first platform cloud.

[0193] Step 47.10, the Bluetooth Mesh device and the first platform cloud perform ECDH calculation to generate a confirmation key.

[0194] Step 47.11, the second platform cloud obtains the configuration end confirmation value and configuration end random number required for authentication through the first platform cloud.

[0195] Step 47.12, the second platform cloud forwards the configuration end confirmation value and the configuration end random number to the second platform gateway.

[0196] Step 47.13, the second platform gateway sends the configuration end confirmation value to the Bluetooth Mesh device.

[0197] Step 47.14, the Bluetooth Mesh device returns a device confirmation value on the device side.

[0198] Step 47.15, the second platform gateway sends the configuration end random number to the Bluetooth Mesh device.

[0199] Step 47.16, the Bluetooth Mesh device verifies the configuration end confirmation value.

[0200] Step 47.17, the verification is successful, and the Bluetooth Mesh device returns the device random number on the device side.

[0201] Step 47.18, the second platform gateway reports the device confirmation value and the device random number of the device to the second platform cloud.

[0202] Step 47.19, the second platform cloud sends the device confirmation value and the device random number to the first platform cloud.

[0203] Step 47.20, the first platform cloud performs authentication verification.

[0204] Step 47.21, the first platform cloud returns the authentication result, device information, device key, session key and session random number.

[0205] The device information includes the control functions and control instructions supported by the device.

[0206] Step 47.22, second platform cloud storage device information.

[0207] Step 47.23, the second platform cloud forwards the authentication result, device information, device key, session key and session random number to the second platform gateway.

[0208] Among them, the second platform gateway stores the device key for subsequent configuration of the Bluetooth Mesh device. The second platform gateway uses the session key and session random number to encrypt the authentication configuration data, and then sends the configuration data to the Bluetooth Mesh device.

[0209] Step 48: The second platform gateway broadcasts the authentication result to the user.

[0210] In summary, the method provided in this embodiment not only ensures the security of Bluetooth Mesh devices during access, but also supports cross-platform authentication access of Bluetooth Mesh devices with existing constant StaticOOB information.

[0211] It is possible that when performing ECDH calculations, the Bluetooth Mesh device's key pair (public-private keypair) is fixed and not regenerated every time the network is configured, resulting in the shared root key remaining unchanged. The second platform gateway can use the configuration end public key, configuration end confirmation value, configuration end random number, session key, and session random number generated during the last configuration process with the same device to replay the device, so that even if the Bluetooth Mesh device has not been authenticated by the first platform cloud, it can still be successfully configured, affecting the security of the Bluetooth Mesh device configuration process.

[0212] In order to solve the above problems, based on Figure 3 In the optional embodiments, the following possible solutions are proposed.

[0213] 1) The Bluetooth Mesh device receives the configuration end public key whose source address is the first platform cloud through forwarding by the second platform; checks the configuration end public key; terminates the network configuration process if the configuration end public key is saved in the local record; and feeds back the device public key if the configuration end public key is not in the local record.

[0214] The Bluetooth Mesh device has a local record corresponding to it, and the local record records the historical configuration end public keys received by the Bluetooth Mesh device during the historical network configuration process. Optionally, the embodiment of the present application does not limit the number of historical configuration end public keys recorded in the local record.

[0215] During this network configuration process, if the configuration end public key received by the Bluetooth Mesh device is saved in the local record and belongs to the historical configuration end public key, it means that the configuration end public key received by the Bluetooth Mesh device may be used by the second platform gateway for replay attack, and the Bluetooth Mesh device terminates the network configuration process; if the configuration end public key received by the Bluetooth Mesh device is not in the local record and does not belong to the historical configuration end public key, it means that the configuration end public key received by the Bluetooth Mesh device may be regenerated by the first platform cloud, then the Bluetooth Mesh device continues the network configuration process and starts to feedback the device public key.

[0216] Exemplary, with reference to Figure 5 , Figure 5 exist Figure 4 Based on the previous step, step 57.7: Bluetooth Mesh device checks the configuration end public key is added.

[0217] Optionally, the Bluetooth Mesh device may also check one or more of the configuration end public key, the configuration end confirmation value, the configuration end random number, the session key, and the session random number to ensure the accuracy of the check result.

[0218] Exemplarily, the local record records the historical configuration end confirmation value received by the Bluetooth Mesh device during the historical network configuration process. The Bluetooth Mesh device determines whether to terminate the network configuration process based on whether the received configuration end confirmation value is saved in the local record.

[0219] Exemplarily, the local record records the historical configuration end public key and historical configuration end random number received by the Bluetooth Mesh device during the historical network configuration process. After the Bluetooth Mesh device receives the configuration end public key, it determines that the configuration end public key belongs to the historical configuration end public key, then the Bluetooth Mesh device continues the network configuration process first, and if the configuration end random number received subsequently also belongs to the historical configuration end random number, the network configuration process is terminated.

[0220] 2) The first platform cloud receives a first random number whose source address is a Bluetooth Mesh device; generates a confirmation input value according to the first random number, configuration information, device public key and configuration end public key.

[0221] Correspondingly, the Bluetooth Mesh device sends a first random number, and the destination address of the first random number is the first platform cloud; wherein the first random number is used for the first platform cloud to generate a confirmation input value.

[0222] Correspondingly, the second platform includes: a second platform gateway and a second platform cloud. The process of the second platform sending the first random number includes: receiving the first random number whose source address is the Bluetooth Mesh device through the second platform gateway; the second platform gateway forwarding the first random number to the second platform cloud; the second platform cloud forwarding the first random number to the first platform cloud, and the first random number is used for the first platform cloud to generate a confirmation input value.

[0223] That is to say, at the beginning of each network configuration process, the Bluetooth Mesh device generates a first random number, and the confirmation input value generated by the first platform cloud is related to the first random number. Since the configuration end confirmation value generated by the first platform cloud is related to the confirmation input value, it can be ensured that the configuration end confirmation value is different each time, and then the second platform gateway cannot use the historical configuration end confirmation value recorded in the history to complete the authentication process with the Bluetooth Mesh device.

[0224] Exemplarily, the calculation method of the confirmation input value is modified as follows: ConfirmationInputs=ProvisioningInvitePDUValue||ProvisioningCapabilitiesPDUValue||ProvisioningStartPDUValue||PublicKeyProvisioner||PublicKeyDevice||Random.

[0225] Optionally, the first random number is included in a universally unique identifier (UUID). The Bluetooth Mesh device generates a first random number and fills it into the UUID each time it enters the network configuration state.

[0226] Exemplary, with reference to Figure 6 , Figure 6 exist Figure 4 Based on this, the following steps were modified:

[0227] Step 62: The Bluetooth Mesh device broadcasts a Bluetooth Mesh unprovisioned broadcast packet according to the specification, and the broadcast packet carries a first random number.

[0228] Step 63: The second platform gateway queries the device type, carrying the first random number.

[0229] Step 63.4, the second platform cloud queries the first platform cloud for the device type, carrying the first random number.

[0230] At the same time, step 63.5 is added: the first platform cloud saves the first random number for calculating and confirming the input value.

[0231] 3) The Bluetooth Mesh device sends a second random number, the destination address of which is the first platform cloud; wherein the second random number is used for the first platform cloud to generate the first verification information (VerifyValue). The second verification information is calculated based on the second random number; the first verification information with the source address of the first platform cloud is forwarded through the second platform; if the first verification information and the second verification information are different, the network configuration process is terminated.

[0232] Correspondingly, the first platform cloud receives a second random number whose source address is the Bluetooth Mesh device; uses the authentication information of the Bluetooth Mesh device to encrypt the second random number to generate first proofreading information; sends the first proofreading information, and the destination address of the first proofreading information is the Bluetooth Mesh device; wherein the first proofreading information is used for the Bluetooth Mesh device to determine whether to terminate the network configuration process.

[0233] Correspondingly, the second platform includes: a second platform gateway and a second platform cloud. The process of the second platform forwarding the second random number and the first proofreading information includes: receiving the second random number whose source address is the Bluetooth Mesh device through the second platform gateway; the second platform gateway forwards the second random number to the second platform cloud; the second platform cloud forwards the second random number to the first platform cloud, and the second random number is used for the first platform cloud to generate the first proofreading information; receiving the first proofreading information whose source address is the first platform cloud through the second platform cloud; the second platform cloud forwards the first proofreading information to the second platform gateway; the second platform gateway sends the first proofreading information to the Bluetooth Mesh device.

[0234] That is to say, at the beginning of each network configuration process, the Bluetooth Mesh device generates a second random number and informs the first platform cloud of the second random number. The first platform cloud and the Bluetooth Mesh device use the same Bluetooth Mesh device authentication information and second random number to calculate the proofreading information according to the same formula. If the second proofreading information calculated by the Bluetooth Mesh device is the same as the first proofreading information received, the subsequent process continues to ensure that the first platform cloud participates in this access authentication.

[0235] Exemplarily, the calculation formula of the verification information is: VerifyValue=AES-CMACstaticoob(Random).

[0236] Optionally, the second random number is included in the UUID. The Bluetooth Mesh device generates a second random number and fills it into the UUID each time it enters the network configuration state.

[0237] Exemplary, with reference to Figure 7 , Figure 7 exist Figure 4 Based on this, the following steps were modified:

[0238] Step 72: The Bluetooth Mesh device broadcasts a Bluetooth Mesh unprovisioned broadcast packet according to the specification, and the broadcast packet carries a second random number.

[0239] Step 73: The second platform gateway queries the device type, carrying a second random number.

[0240] Step 73.4, the second platform cloud queries the first platform cloud for the device type, carrying the second random number.

[0241] Step 73.6, the second platform cloud obtains the device type and the first proofreading information from the first platform cloud.

[0242] Step 74, the second platform cloud forwards the device type and the first proofreading information to the second platform gateway.

[0243] At the same time, step 73.5 is added: the first platform cloud uses the second random number to calculate the first proofreading information.

[0244] Added step 77.1, the Bluetooth Mesh device checks the first calibration information.

[0245] like Figure 7 As shown, the second platform cloud forwards the second random number generated by the Bluetooth Mesh device to the first platform cloud. The first platform cloud uses the above calculation formula to calculate the first proofreading information and the device type and sends them to the second platform cloud. The second platform cloud sends the first proofreading information and the device type to the second platform gateway. The second platform gateway sends the first proofreading information to the Bluetooth Mesh device in the Link&Invatition process with the Bluetooth Mesh device. The Bluetooth Mesh device uses the same calculation formula to calculate the second proofreading information and compares the first proofreading information sent by the second platform gateway. If they are the same, the subsequent process will continue. Otherwise, the connection will be disconnected to terminate the network configuration process.

[0246] In summary, the method provided in this embodiment provides three different solutions to prevent the second platform gateway from using the information saved in the historical network configuration process to perform a replay attack to successfully configure the network, thereby enhancing the security and reliability of the Bluetooth Mesh device configuration process.

[0247] Technical solution 2)

[0248] Figure 8 A flowchart of an access authentication method provided by an exemplary embodiment of the present application is shown. The method can be applied to Figure 1 In the Bluetooth Mesh device cross-platform access authentication system shown, the method includes:

[0249] Step 810, in response to the Bluetooth Mesh device starting the network configuration process, the first platform cloud generates authentication information corresponding to this network configuration process, and the authentication information is the same as the authentication information at the Bluetooth Mesh device.

[0250] Bluetooth Mesh devices are devices that support access to Bluetooth Mesh networks. Bluetooth Mesh devices include various types of home devices (such as lights), industrial assets (such as examination equipment in hospitals), etc.

[0251] The platform corresponding to the first platform cloud is a platform for developing Bluetooth Mesh devices. The first platform cloud stores authentication information (AuthValue) of Bluetooth Mesh devices.

[0252] Each time the Bluetooth Mesh device is networked, the Bluetooth Mesh device regenerates authentication information for this network configuration process with the first platform cloud. In other words, the authentication information is only valid in a single network configuration process.

[0253] Optionally, in response to the Bluetooth Mesh device starting the network configuration process, the Bluetooth Mesh device also generates authentication information corresponding to this network configuration process. Since the authentication information is generated using the same parameters and the same formula, the authentication information at the Bluetooth Mesh device is the same as the authentication information at the first platform cloud.

[0254] It can be understood that the embodiment of the present application does not limit the specific implementation method of the first platform cloud and the Bluetooth Mesh device generating authentication information corresponding to this network configuration process.

[0255] Step 820: The first platform cloud sends authentication information to the second platform.

[0256] The second platform gateway is a node that supports adding Bluetooth Mesh devices to the Bluetooth Mesh network. The Bluetooth Mesh device is configured to join the network by the second platform gateway. The cloud server corresponding to the second platform gateway is the second platform cloud and the first platform cloud. The first platform cloud and the second platform cloud are two different platform clouds and belong to different platforms.

[0257] In each network configuration process, the first platform cloud sends the dynamically generated authentication information to the second platform for the second platform gateway to use the authentication information to complete the authentication of the Bluetooth Mesh device.

[0258] Optionally, in order to generate authentication information corresponding to this network configuration process, the first platform cloud receives a third random number whose source address is a Bluetooth Mesh device; when the third random number is not in the local record, it sends authentication information, and the destination address of the authentication information is the second platform gateway.

[0259] Correspondingly, the Bluetooth Mesh device sends a third random number, and the destination address of the third random number is the first platform cloud.

[0260] Correspondingly, the second platform includes: a second platform gateway and a second platform cloud. The process of the second platform forwarding the third random number includes: receiving the third random number whose source address is the Bluetooth Mesh device through the second platform gateway; the second platform gateway forwards the third random number to the second platform cloud; the second platform cloud forwards the third random number to the first platform cloud; wherein the third random number is used for the first platform cloud to determine whether to send authentication information to the second platform.

[0261] That is to say, the first platform cloud corresponds to a local record, and the local record records the historical third random number received by the first platform cloud during the historical network configuration process. Optionally, the embodiment of the present application does not limit the number of historical third random numbers recorded in the local record. During this network configuration process, if the third random number received by the first platform cloud is not in the local record and does not belong to the historical third random number, it means that the Bluetooth Mesh device has restarted a new round of network configuration process, and the first platform cloud uses the third random number to generate authentication information corresponding to this network configuration process.

[0262] Optionally, the third random number is included in the UUID. The Bluetooth Mesh device generates a third random number and fills it into the UUID each time it enters the network configuration state.

[0263] Step 830: Receive authentication information sent by the first platform cloud through the second platform cloud.

[0264] Step 840: The second platform cloud forwards the authentication information to the second platform gateway.

[0265] Step 850: The second platform gateway generates network distributor authentication information based on the authentication information.

[0266] The network adapter authentication information is used for access authentication with Bluetooth Mesh devices.

[0267] Optionally, the destination address of the network provisioner authentication information is a Bluetooth Mesh device, and the Bluetooth Mesh device can check and verify the network provisioner authentication information. The network provisioner authentication information includes a configuration end confirmation value.

[0268] Optionally, the second platform includes: a second platform gateway and a second platform cloud. After step 850: the second platform gateway generates an authentication result; the second platform gateway sends the authentication result to the second platform cloud. Since the second platform gateway stores the authentication information corresponding to the current network configuration process, the second platform gateway generates an authentication result after checking the device confirmation value, and sends the confirmation result to the second platform cloud for storage.

[0269] To sum up, in the method provided in this embodiment, the authentication information AuthValue of the Bluetooth Mesh device is dynamically generated each time the network is configured and is only valid within a single network configuration cycle, thereby avoiding the risk of leakage of the StaticOOB authentication information AuthValue of the Bluetooth Mesh device and ensuring the security of the Bluetooth Mesh device during access.

[0270] Based on Figure 8 In an optional embodiment, Fig. 9 A flowchart of an access authentication method provided by an exemplary embodiment of the present application is shown. The method can be applied to Figure 1In the Bluetooth Mesh device cross-platform access authentication system shown, the method includes:

[0271] Step 91, the user uses voice or APP to activate scanning of the second platform gateway.

[0272] Step 92: The Bluetooth Mesh device (developed based on the first platform) broadcasts a Bluetooth Mesh unprovisioned broadcast packet according to the specification, and the broadcast packet carries a third random number.

[0273] The broadcast packet includes the CID corresponding to the first platform.

[0274] In each network configuration process, the Bluetooth Mesh device generates a third random number corresponding to this network configuration process and sends it in the broadcast packet.

[0275] Step 93: The second platform gateway queries the device type, carrying a third random number.

[0276] After the second platform gateway obtains the unconfigured network broadcast information broadcast by the Bluetooth Mesh device, it uploads the information to the second platform cloud, queries the type of the device, and at the same time, uploads the third random number to the second platform cloud.

[0277] Step 93.1, the second platform cloud determines whether it is a device on this platform.

[0278] Step 93.2, the second platform cloud queries the CID corresponding to the device.

[0279] After receiving the device information reported by the second platform gateway, the second platform cloud determines through CID that the Bluetooth Mesh device is not a device developed based on the second platform and requires authorization from other platforms.

[0280] Step 93.3, the second platform cloud obtains the first platform information corresponding to the CID through the interconnection server.

[0281] Optionally, the first platform information includes information such as the first platform rights management server.

[0282] Step 93.4, the second platform cloud queries the first platform cloud for the device type, carrying the third random number.

[0283] Step 93.5, the first platform cloud checks whether the third random number has been used and generates authentication information.

[0284] The first platform cloud verifies the legitimacy of the third random number and calculates the authentication information of this network configuration.

[0285] Step 93.6, the A platform cloud obtains the device type and authentication information from the first platform cloud.

[0286] Step 94: The second platform cloud forwards the device type and authentication information to the second platform gateway.

[0287] Step 95: The second platform gateway announces the device and device type to the user.

[0288] Step 96, user input: connect device.

[0289] Step 97: The second platform gateway and the Bluetooth Mesh device perform a connection and invitation process.

[0290] Step 97.1, the second platform gateway starts sending configuration to the Bluetooth Mesh device.

[0291] Step 97.2: The second platform gateway sends the configuration end public key to the Bluetooth Mesh device.

[0292] Step 97.3, the Bluetooth Mesh device sends the device public key to the second platform gateway.

[0293] In step 97.4, the Bluetooth Mesh device and the second platform gateway perform ECDH calculation.

[0294] Step 97.5, the second platform gateway sends the configuration end confirmation value to the Bluetooth Mesh device.

[0295] Since the second platform gateway obtains the authentication information, the second platform can calculate and generate the configuration end confirmation value.

[0296] Step 97.6, the Bluetooth Mesh device sends a device confirmation value to the second platform gateway.

[0297] Step 97.7: The second platform gateway sends a configuration end random number to the Bluetooth Mesh device.

[0298] The configuration end confirmation value is generated by the second platform gateway.

[0299] Step 97.8, the Bluetooth Mesh device verifies the configuration end confirmation value.

[0300] Step 97.9: After verification, the Bluetooth Mesh device returns the device random number on the device side.

[0301] Step 97.10: The second platform gateway performs authentication verification.

[0302] Step 97.11, the second platform gateway returns the authentication result.

[0303] Step 97.12, second platform cloud storage device information.

[0304] Step 98: The second platform gateway broadcasts the authentication result to the user.

[0305] To sum up, the method provided in this embodiment ensures the security of the Bluetooth Mesh device during the access process. At the same time, the second platform gateway generates the configuration end confirmation value and the configuration end random number without obtaining them from the first platform cloud, which simplifies the process and improves the efficiency of access authentication.

[0306] It should be noted that the above method embodiments can be implemented separately or in combination, and this application does not limit this.

[0307] In the above embodiments, the steps executed by the first platform cloud can be independently implemented as an access authentication method on the first platform cloud side, the steps executed by the Bluetooth Mesh device can be independently implemented as an access authentication method on the Bluetooth Mesh device side, and the steps executed by the second platform gateway can be independently implemented as an access authentication method on the second platform gateway side.

[0308] Fig.10 The structural block diagram of an access authentication device provided by an exemplary embodiment of the present application is shown. The device can be implemented as a first platform cloud, or implemented as a part of the first platform cloud. The first platform cloud is a cloud server storing authentication information of Bluetooth Mesh devices. The device includes: a generating module 1001;

[0309] A generation module 1001 is used to perform ECDH calculation with a Bluetooth Mesh device to generate a shared root key. The Bluetooth Mesh device is configured to join the network by the second platform gateway;

[0310] The generation module 1001 is used to generate network adapter authentication information according to the shared root key, and the network adapter authentication information is used to perform access authentication with the Bluetooth Mesh device.

[0311] Optionally, the device further includes: a receiving module 1002 and a sending module 1003 .

[0312] In an optional embodiment, the network provisioner authentication information includes a configuration end confirmation value; a generation module 1001 is used to generate a confirmation key based on a shared root key; a generation module 1001 is used to generate a configuration end random number, and the configuration end random number and the authentication information AuthValue of the Bluetooth Mesh device form a first plain text; the generation module 1001 is used to encrypt the first plain text using the confirmation key to generate a configuration end confirmation value.

[0313] In an optional embodiment, generation module 1001 is used to obtain a confirmation input value; generation module 1001 is used to generate a confirmation salt value based on the confirmation input value; generation module 1001 is used to generate a confirmation key based on the confirmation salt value, the shared root key and the string "prck".

[0314] In an optional embodiment, the receiving module 1002 is used to receive configuration information whose source address is the gateway of the second platform; the receiving module 1002 is used to receive the device public key of the Bluetooth Mesh device whose source address is the device; the generating module 1001 is used to generate the configuration end public key; according to the configuration information, the device public key and the configuration end public key, a confirmation input value is generated; wherein the configuration information includes: at least one of a configuration invitation protocol data unit value, a configuration capability protocol data unit value and a configuration start protocol data unit value.

[0315] In an optional embodiment, the receiving module 1002 is used to receive a first random number whose source address is a Bluetooth Mesh device; the generating module 1001 is used to generate a confirmation input value according to the first random number, configuration information, device public key and configuration end public key.

[0316] In an optional embodiment, the first random number is included in the UUID.

[0317] In an optional embodiment, the sending module 1003 is used to send the configuration end public key, and the destination address of the configuration end public key is the Bluetooth Mesh device.

[0318] In an optional embodiment, the sending module 1003 is used to send a device key, a session key and a session random number, and the destination address of the device key, the session key and the session random number is the second platform gateway.

[0319] In an optional embodiment, the receiving module 1002 is used to receive a second random number whose source address is a Bluetooth Mesh device; the generating module 1001 is used to encrypt the second random number using the authentication information of the Bluetooth Mesh device to generate first proofreading information; the sending module 1003 is used to send the first proofreading information, and the destination address of the first proofreading information is the Bluetooth Mesh device; wherein the first proofreading information is used for the Bluetooth Mesh device to determine whether to terminate the network configuration process.

[0320] In an optional embodiment, the second random number is included in the UUID.

[0321] Fig.11 The structure block diagram of an access authentication device provided by an exemplary embodiment of the present application is shown. The device can be implemented as a Bluetooth Mesh device, or implemented as a part of a Bluetooth Mesh device. The device includes: a generating module 1101;

[0322] A generation module 1101 is used to perform ECDH calculation with the first platform cloud to generate a shared root key;

[0323] Among them, the first platform cloud is a cloud server that stores the authentication information of the Bluetooth Mesh device. The Bluetooth Mesh device is configured to enter the network by the second platform gateway. The shared root key is used to generate the device confirmation value, and the device confirmation value is used for access authentication with the first platform cloud.

[0324] Optionally, the device further includes: a receiving module 1102 , a process termination module 1103 , a sending module 1104 and a calculating module 1105 .

[0325] In an optional embodiment, the receiving module 1102 is used to receive the configuration end public key whose source address is the first platform cloud through the second platform gateway; the process termination module 1103 is used to terminate the network configuration process when the configuration end public key is saved in the local record; the sending module 1104 is used to feedback the device public key when the configuration end public key is not in the local record.

[0326] In an optional embodiment, the sending module 1104 is used to send a first random number, and the destination address of the first random number is the first platform cloud; wherein the first random number is used for the first platform cloud to generate a confirmation input value.

[0327] In an optional embodiment, the first random number is included in a universally unique identifier UUID.

[0328] In an optional embodiment, the sending module 1104 is used to send a second random number, and the destination address of the second random number is the first platform cloud; wherein the second random number is used for the first platform cloud to generate the first proofreading information.

[0329] In an optional embodiment, the calculation module 1105 is used to calculate the second proofreading information based on the second random number; the receiving module 1102 is used to receive the first proofreading information whose source address is the first platform cloud through the second platform gateway; the process termination module 1103 is used to terminate the network configuration process when the first proofreading information and the second proofreading information are different.

[0330] In an optional embodiment, the second random number is included in the UUID.

[0331] Fig.12 The structure block diagram of an access authentication device provided by an exemplary embodiment of the present application is shown. The device can be implemented as a second platform gateway, or implemented as a part of the second platform gateway. The second platform is a platform for configuring Bluetooth Mesh devices to access the network. The Bluetooth Mesh device stores the authentication information of the Bluetooth Mesh device by the first platform cloud. The cloud server corresponding to the second platform gateway is the second platform cloud. The device includes: a receiving module 1201 and a sending module 1202;

[0332] The receiving module 1201 is used to receive, through the second platform cloud, the network adapter authentication information whose source address is the first platform cloud, where the network adapter authentication information is used to perform access authentication with the Bluetooth Mesh device;

[0333] The sending module 1202 is used to forward the network adapter authentication information to the Bluetooth Mesh device;

[0334] Among them, the network adapter authentication information is generated by the first platform cloud based on the shared root key, and the shared root key is obtained by ECDH calculation between the first platform cloud and the Bluetooth Mesh device.

[0335] Receiving module 1201 sending module 1202 In an optional embodiment, the sending module 1202 is used to send configuration information to the first platform through the second platform cloud; the receiving module 1201 is used to receive the device public key Device Public Key of the Bluetooth Mesh device whose source address is the device; the sending module 1202 is used to send the device public key to the first platform cloud through the second platform cloud; wherein the configuration information and the device public key are used for the first platform cloud to generate a confirmation input value, and the configuration information includes: at least one of a configuration invitation protocol data unit value, a configuration capability protocol data unit value, and a configuration start protocol data unit value.

[0336] In an optional embodiment, the receiving module 1201 is used to receive a first random number whose source address is a Bluetooth Mesh device; the sending module 1202 is used to send the first random number to the first platform cloud through the second platform cloud, and the first random number is used for the first platform cloud to generate a confirmation input value.

[0337] In an optional embodiment, the first random number is included in the UUID.

[0338] In an optional embodiment, the receiving module 1201 is used to receive the configuration end public key Provisoning Public Key whose source address is the first platform cloud through the second platform cloud; the sending module 1202 is used to forward the configuration end public key to the Bluetooth Mesh device.

[0339] In an optional embodiment, the receiving module 1201 is used to receive a device key DevKey, a session key SessionKey and a session random number SessionNonce whose source address is the first platform cloud through the second platform cloud.

[0340] In an optional embodiment, the receiving module 1201 is used to receive a second random number whose source address is a Bluetooth Mesh device; the sending module 1202 is used to send the second random number to the first platform cloud through forwarding by the second platform cloud, and the second random number is used for the first platform cloud to generate the first proofreading information VerifyValue; the receiving module 1201 is used to receive the first proofreading information whose source address is the first platform cloud through the second platform cloud; the sending module 1202 is used to send the first proofreading information to the Bluetooth Mesh device.

[0341] In an optional embodiment, the second random number is included in the UUID.

[0342] Fig.13 A structural block diagram of an access authentication device provided by an exemplary embodiment of the present application is shown. The device can be implemented as a first platform cloud, or as a part of the first platform cloud. The first platform cloud is a cloud server storing authentication information of a Bluetooth Mesh device. The device includes: a generating module 1301 and a sending module 1302;

[0343] A generating module 1301 is used for generating authentication information corresponding to the current network configuration process in response to the Bluetooth Mesh device starting the network configuration process, where the authentication information is the same as the authentication information at the Bluetooth Mesh device;

[0344] The sending module 1302 is used to send authentication information, the destination address of the authentication information is the second platform gateway, and the second platform gateway is used to configure the Bluetooth Mesh device to join the network;

[0345] The authentication information is used by the second platform gateway to authenticate the Bluetooth Mesh device.

[0346] Optionally, the device further includes: a receiving module 1303.

[0347] In an optional embodiment, the receiving module 1303 is used to receive a third random number whose source address is a Bluetooth Mesh device; the sending module 1302 is used to send authentication information when the third random number is not in the local record.

[0348] In an optional embodiment, the third random number is included in the UUID.

[0349] Fig.14The structure block diagram of an access authentication device provided by an exemplary embodiment of the present application is shown. The device can be implemented as a second platform gateway, or implemented as a part of the second platform gateway. The second platform gateway is used to configure the Bluetooth wireless mesh network Mesh device to access the network. The Bluetooth Mesh device is stored by the first platform cloud. The cloud server corresponding to the second platform gateway is the second platform cloud. The device includes: a receiving module 1401 and a generating module 1402;

[0350] The receiving module 1401 is used to receive the authentication information AuthValue sent by the first platform cloud through the second platform cloud;

[0351] The generating module 1402 is used to generate network adapter authentication information according to the authentication information, and the network adapter authentication information is used to perform access authentication with the Bluetooth Mesh device.

[0352] In an optional embodiment, the device also includes: a sending module 1403; a receiving module 1401, used to receive a third random number whose source address is a Bluetooth Mesh device; a sending module 1403, used to send the third random number to the first platform cloud through the second platform cloud; wherein the third random number is used for the first platform cloud to determine whether to send authentication information to the second platform gateway.

[0353] In an optional embodiment, the third random number is included in the UUID.

[0354] In an optional embodiment, the device further includes: a sending module 1403; a generating module 1402, used to generate an authentication result; and a sending module 1403, used to send the authentication result to the second platform cloud.

[0355] Fig.15 The structural block diagram of an access authentication device provided by an exemplary embodiment of the present application is shown. The device can be implemented as a Bluetooth Mesh device, or implemented as a part of a Bluetooth Mesh device. The Bluetooth Mesh device is configured to access the network by the second platform gateway, and the Bluetooth Mesh device stores the authentication information of the Bluetooth Mesh device by the first platform cloud. The device includes: a generation module 1501;

[0356] The generating module 1501 is used to respond to the Bluetooth Mesh device starting the network configuration process, corresponding to the authentication information of this network configuration process, and the authentication information is the same as the authentication information at the first platform cloud.

[0357] Please refer to Fig.16 , which shows a structural block diagram of a server provided by an exemplary embodiment of the present application. The server can be used to implement the access authentication method provided in the above embodiment. Specifically:

[0358] The server 1600 includes a central processing unit (CPU) 1601, a system memory 1604 including a random access memory (RAM) 1602 and a read-only memory (ROM) 1603, and a system bus 1605 connecting the system memory 1604 and the central processing unit 1601. The server 1600 also includes a basic input / output system (I / O system) 1606 for facilitating information transmission between various components in the server, and a large-capacity storage device 1607 for storing an operating system 1613, application programs 1614, and other program modules 1615.

[0359] The basic input / output system 1606 includes a display 1608 for displaying information and an input device 1609 such as a mouse and a keyboard for user inputting information. The display 1608 and the input device 1609 are connected to the central processing unit 1601 through an input / output controller 1610 connected to the system bus 1605. The basic input / output system 1606 may also include an input / output controller 1610 for receiving and processing inputs from a plurality of other devices such as a keyboard, a mouse, or an electronic stylus. Similarly, the input / output controller 1610 also provides output to a display screen, a printer, or other types of output devices.

[0360] The mass storage device 1607 is connected to the central processing unit 1601 via a mass storage controller (not shown) connected to the system bus 1605. The mass storage device 1607 and its associated computer-readable storage medium provide non-volatile storage for the server 1600. That is, the mass storage device 1607 may include a computer-readable storage medium (not shown) such as a hard disk or a compact disc read-only memory (CD-ROM) drive.

[0361] Without loss of generality, the computer-readable storage medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information such as computer-readable storage instructions, data structures, program modules or other data. Computer storage media include RAM, ROM, Erasable Programmable Read Only Memory (EPROM), Electronically Erasable Programmable Read-Only Memory (EEPROM), flash memory or other solid-state storage technology, CD-ROM, Digital Versatile Disc (DVD) or other optical storage, cassette, tape, disk storage or other magnetic storage devices. Of course, those skilled in the art will know that the computer storage medium is not limited to the above. The above-mentioned system memory 1604 and mass storage device 1607 can be collectively referred to as memory.

[0362] The memory stores one or more programs, and the one or more programs are configured to be executed by one or more central processing units 1601. The one or more programs contain instructions for implementing the above-mentioned method embodiments. The central processing unit 1601 executes the one or more programs to implement the methods provided by the above-mentioned method embodiments.

[0363] According to various embodiments of the present application, the server 1600 can also be connected to a remote server on the network through a network such as the Internet. That is, the server 1600 can be connected to the network 1612 through the network interface unit 1611 connected to the system bus 1605, or the network interface unit 1611 can be used to connect to other types of networks or remote server systems (not shown).

[0364] The memory also includes one or more programs, which are stored in the memory, and the one or more programs include steps for performing the method provided in the embodiment of the present application and executed by the first platform cloud or the second platform cloud.

[0365] In an exemplary embodiment, a computer-readable storage medium is also provided, in which at least one instruction, at least one program, a code set or an instruction set is stored. The at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by a processor to implement the access authentication method performed by the device provided by the above-mentioned various method embodiments.

[0366] In an exemplary embodiment, a computer program product or a computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the access authentication method described in the above aspects.

[0367] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0368] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. An access authentication method, characterized in that: Applied in a first platform cloud, the first platform cloud is a cloud server storing authentication information of a Bluetooth wireless mesh network Mesh device, the method includes: Perform elliptic curve algorithm ECDH calculation with the Bluetooth Mesh device to generate a shared root key ECDHSecret, and the Bluetooth Mesh device is configured to join the network by the second platform gateway; Generate network adapter authentication information according to the shared root key, where the network adapter authentication information is used to perform access authentication with the Bluetooth Mesh device. The provisioner authentication information includes a provisioner confirmation value, and the generating of the provisioner authentication information according to the shared root key includes: Generate a confirmation key ConfirmationKey according to the shared root key; Generate a provisioner random number, wherein the provisioner random number and the authentication information AuthValue of the Bluetooth Mesh device form a first plain text; The first plaintext is encrypted using the confirmation key to generate the configuration end confirmation value.

2. The method according to claim 1, characterized in that The generating a confirmation key ConfirmationKey according to the shared root key includes: Get the confirmation input value ConfirmationInputs; Generate a confirmation salt value ConfirmationSalt according to the confirmation input value; The confirmation key is generated according to the confirmation salt value, the shared root key and the string "prck".

3. The method according to claim 2, characterized in that The obtaining of the confirmation input value ConfirmationInputs includes: Receiving configuration information whose source address is the gateway of the second platform; The receiving source address is the device public key Device Public Key of the Bluetooth Mesh device; Generate the Provisoning Public Key; Generate the confirmation input value according to the configuration information, the device public key and the configuration end public key; The configuration information includes: at least one of a configuration invitation protocol data unit value ProvisioningInvitePDUValue, a configuration capability protocol data unit value ProvisioningCapabilitiesPDUValue, and a configuration start protocol data unit value ProvisioningStartPDUValue.

4. The method according to claim 3, characterized in that Generating the confirmation input value according to the configuration information, the device public key and the configuration end public key includes: Receive a first random number whose source address is the Bluetooth Mesh device; The confirmation input value is generated according to the first random number, the configuration information, the device public key and the configuration end public key.

5. The method according to claim 4, characterized in that The first random number is included in a universal unique identifier UUID.

6. The method according to claim 3, characterized in that The method further comprises: The configuration end public key is sent, and the destination address of the configuration end public key is the Bluetooth Mesh device.

7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: The device key DevKey, the session key SessionKey and the session random number SessionNonce are sent, and the destination address of the device key, the session key and the session random number is the second platform gateway.

8. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: Receive a second random number whose source address is the Bluetooth Mesh device; Encrypt the second random number using the authentication information of the Bluetooth Mesh device to generate first verification information VerifyValue; Sending the first proofreading information, where the destination address of the first proofreading information is the Bluetooth Mesh device; The first calibration information is used by the Bluetooth Mesh device to determine whether to terminate the network configuration process.

9. The method according to claim 8, characterized in that The second random number is included in the UUID.

10. An access authentication method, characterized in that: Applied to a Bluetooth wireless mesh network Mesh device, the method includes: Perform elliptic curve algorithm ECDH calculation with First Platform Cloud to generate a shared root key ECDHSecret; The first platform cloud is a cloud server storing the authentication information of the Bluetooth Mesh device, the Bluetooth Mesh device is configured to access the network by the second platform gateway, the shared root key is used to generate a device confirmation value deviceconfirmation, and the device confirmation value is used to perform access authentication with the first platform cloud. The shared root key is used by the first platform to generate provisioner authentication information, the provisioner authentication information is used to perform access authentication with the Bluetooth Mesh device, the provisioner authentication information includes a provisioner confirmation value, and the first platform generates the provisioner confirmation value by: Generate a confirmation key ConfirmationKey according to the shared root key; Generate a provisioner random number, wherein the provisioner random number and the authentication information AuthValue of the Bluetooth Mesh device form a first plain text; The first plaintext is encrypted using the confirmation key to generate the configuration end confirmation value.

11. The method according to claim 10, characterized in that The method further comprises: Receive, through the second platform gateway, a configuration end public key ProvisoningPublic Key whose source address is the first platform cloud; When the configuration end public key is stored in the local record, the network configuration process is terminated; When the configuration end public key is not in the local record, the device public key DevicePublic Key is fed back.

12. The method according to claim 10, characterized in that The method further comprises: Sending a first random number, where the destination address of the first random number is the first platform cloud; Among them, the first random number is used for the first platform cloud to generate a confirmation input value ConfirmationInputs.

13. The method according to claim 12, characterized in that The first random number is included in a universal unique identifier UUID.

14. The method according to claim 10, characterized in that The method further comprises: Sending a second random number, where the destination address of the second random number is the first platform cloud; Among them, the second random number is used for the first platform cloud to generate the first proofreading information VerifyValue.

15. The method according to claim 14, characterized in that The method further comprises: Calculating second proofreading information according to the second random number; Receiving, through the second platform gateway, the first proofreading information whose source address is the first platform cloud; When the first proofreading information and the second proofreading information are different, the network configuration process is terminated.

16. The method according to claim 14, characterized in that The second random number is included in the UUID.

17. An access authentication method, characterized in that: Applied in a second platform gateway, the second platform gateway is used to configure a Bluetooth wireless mesh network Mesh device to join the network, the Bluetooth Mesh device is stored by the first platform cloud with authentication information of the Bluetooth Mesh device, and the cloud server corresponding to the second platform gateway is the second platform cloud, the method includes: Receiving, through the second platform cloud, network adapter authentication information whose source address is the first platform cloud, wherein the network adapter authentication information is used for access authentication with the Bluetooth Mesh device; Forwarding the network adapter authentication information to the Bluetooth Mesh device; The network adapter authentication information is generated by the first platform cloud according to the shared root key ECDHSecret, and the shared root key is obtained by performing elliptic curve algorithm ECDH calculation on the first platform cloud and the Bluetooth Mesh device. The network provisioner authentication information includes a provisioner confirmation value, and the first platform generates the provisioner confirmation value by: Generate a confirmation key ConfirmationKey according to the shared root key; Generate a provisioner random number, wherein the provisioner random number and the authentication information AuthValue of the Bluetooth Mesh device form a first plain text; The first plaintext is encrypted using the confirmation key to generate the configuration end confirmation value.

18. The method according to claim 17, characterized in that The method further comprises: Sending configuration information to the first platform cloud via the second platform cloud; The receiving source address is the device public key Device Public Key of the Bluetooth Mesh device; Sending the device public key to the first platform cloud via the second platform cloud; Among them, the configuration information and the device public key are used for the first platform cloud to generate a confirmation input value ConfirmationInputs, and the configuration information includes: at least one of a configuration invitation protocol data unit value ProvisioningInvitePDUValue, a configuration capability protocol data unit value ProvisioningCapabilitiesPDUValue, and a configuration start protocol data unit value ProvisioningStartPDUValue.

19. The method according to claim 18, characterized in that The method further comprises: Receive a first random number whose source address is the Bluetooth Mesh device; The first random number is sent to the first platform cloud through the second platform cloud, and the first random number is used by the first platform cloud to generate the confirmation input value.

20. The method according to claim 19, characterized in that The first random number is included in a universal unique identifier UUID.

21. The method according to claim 17, characterized in that The method further comprises: Receive, through the second platform cloud, a configuration end public key ProvisoningPublic Key whose source address is the first platform cloud; Forward the configuration end public key to the Bluetooth Mesh device.

22. The method according to any one of claims 17 to 21, characterized in that: The method further comprises: Through the second platform cloud, a device key DevKey, a session key SessionKey and a session random number SessionNonce whose source address is the first platform cloud are received.

23. The method according to any one of claims 17 to 21, characterized in that: The method further comprises: Receive a second random number whose source address is the Bluetooth Mesh device; Sending the second random number to the first platform cloud through the second platform cloud, where the second random number is used by the first platform cloud to generate first proofreading information VerifyValue; Receiving, through the second platform cloud, the first proofreading information whose source address is the first platform cloud; Send the first calibration information to the Bluetooth Mesh device.

24. The method according to claim 23, characterized in that The second random number is included in the UUID.

25. An access authentication device, characterized in that: Applied in a first platform cloud, the first platform cloud is a cloud server storing authentication information of a Bluetooth wireless mesh network Mesh device, the device comprises: a generation module; The generation module is used to perform elliptic curve algorithm ECDH calculation with the Bluetooth Mesh device to generate a shared root key ECDHSecret, and the Bluetooth Mesh device is configured to access the network by the second platform gateway; The generating module is used to generate network adapter authentication information according to the shared root key, and the network adapter authentication information is used to perform access authentication with the Bluetooth Mesh device. Wherein, the network provisioner authentication information includes the configuration end confirmation value provisionerconfirmation; The generating module is used to generate a confirmation key ConfirmationKey according to the shared root key; The generating module is used to generate a provisioner random number, wherein the provisioner random number and the authentication information AuthValue of the Bluetooth Mesh device form a first plain text; The generating module is used to encrypt the first plaintext using the confirmation key to generate the configuration end confirmation value.

26. The device according to claim 25, characterized in that The generating module is used to obtain the confirmation input value ConfirmationInputs; The generating module is used to generate a confirmation salt value ConfirmationSalt according to the confirmation input value; The generation module is used to generate the confirmation key according to the confirmation salt value, the shared root key and the character string "prck".

27. The device according to claim 26, characterized in that The device further comprises: a receiving module; The receiving module is used to receive the configuration information whose source address is the gateway of the second platform; The receiving module is used to receive a device public key Device Public Key whose source address is the Bluetooth Mesh device; The generating module is used to generate a Provisoning Public Key; Generate the confirmation input value according to the configuration information, the device public key and the configuration end public key; The configuration information includes: at least one of a configuration invitation protocol data unit value ProvisioningInvitePDUValue, a configuration capability protocol data unit value ProvisioningCapabilitiesPDUValue, and a configuration start protocol data unit value ProvisioningStartPDUValue.

28. The device according to claim 27, characterized in that The receiving module is used to receive a first random number whose source address is the Bluetooth Mesh device; The generating module is used to generate the confirmation input value according to the first random number, the configuration information, the device public key and the configuration end public key.

29. The device according to claim 28, characterized in that The first random number is included in a universal unique identifier UUID.

30. The device according to claim 29, characterized in that The device also includes: a sending module; The sending module is used to send the configuration end public key, and the destination address of the configuration end public key is the Bluetooth Mesh device.

31. The device according to any one of claims 25 to 30, characterized in that The device also includes: a sending module; The sending module is used to send a device key DevKey, a session key SessionKey and a session random number SessionNonce, and the destination address of the device key, the session key and the session random number is the second platform gateway.

32. The device according to any one of claims 25 to 30, characterized in that The device also includes: a receiving module and a sending module; The receiving module is used to receive a second random number whose source address is the Bluetooth Mesh device; The generating module is used to encrypt the second random number using the authentication information of the Bluetooth Mesh device to generate the first verification information VerifyValue; The sending module is used to send the first proofreading information, where the destination address of the first proofreading information is the Bluetooth Mesh device; The first calibration information is used by the Bluetooth Mesh device to determine whether to terminate the network configuration process.

33. The device according to claim 32, characterized in that The second random number is included in the UUID.

34. An access authentication device, characterized in that: Applied in a Bluetooth wireless mesh network Mesh device, the device comprises: a generating module; The generation module is used to perform elliptic curve algorithm ECDH calculation with the first platform cloud to generate a shared root key ECDHSecret; The first platform cloud is a cloud server storing the authentication information of the Bluetooth Mesh device, the Bluetooth Mesh device is configured to access the network by the second platform gateway, the shared root key is used to generate a device confirmation value deviceconfirmation, and the device confirmation value is used to perform access authentication with the first platform cloud. The shared root key is used by the first platform to generate provisioner authentication information, the provisioner authentication information is used to perform access authentication with the Bluetooth Mesh device, the provisioner authentication information includes a provisioner confirmation value, and the first platform generates the provisioner confirmation value by: Generate a confirmation key ConfirmationKey according to the shared root key; Generate a provisioner random number, wherein the provisioner random number and the authentication information AuthValue of the Bluetooth Mesh device form a first plain text; The first plaintext is encrypted using the confirmation key to generate the configuration end confirmation value.

35. The device according to claim 34, characterized in that The device also includes: a receiving module, a process termination module and a sending module; The receiving module is used to receive, through the second platform gateway, a provisoning public key whose source address is the first platform cloud; The process termination module is used to terminate the network configuration process when the configuration end public key is stored in the local record; The sending module is used to feedback the device public key Device Public Key when the configuration end public key is not in the local record.

36. The device according to claim 34, characterized in that The device also includes: a sending module; The sending module is used to send a first random number, where the destination address of the first random number is the first platform cloud; Among them, the first random number is used for the first platform cloud to generate a confirmation input value ConfirmationInputs.

37. The device according to claim 36, characterized in that The first random number is included in a universal unique identifier UUID.

38. The device according to claim 34, characterized in that The device also includes: a sending module; The sending module is used to send a second random number, where the destination address of the second random number is the first platform cloud; Among them, the second random number is used for the first platform cloud to generate the first proofreading information VerifyValue.

39. The device according to claim 38, characterized in that The device also includes: a calculation module, a receiving module and a process termination module; The calculation module is used to calculate the second proofreading information according to the second random number; The receiving module is used to receive the first proofreading information whose source address is the first platform cloud through the second platform gateway; The process termination module is used to terminate the network configuration process when the first proofreading information and the second proofreading information are different.

40. The device according to claim 38, characterized in that The second random number is included in the UUID.

41. An access authentication device, characterized in that: Applied in a second platform gateway, the second platform gateway is used to configure a Bluetooth wireless mesh network Mesh device to join the network, the Bluetooth Mesh device is stored by the first platform cloud with authentication information of the Bluetooth Mesh device, the cloud server corresponding to the second platform gateway is the second platform cloud, and the device includes: a receiving module and a sending module; The receiving module is used to receive, through the second platform cloud, network adapter authentication information whose source address is the first platform cloud, where the network adapter authentication information is used to perform access authentication with the Bluetooth Mesh device; The sending module is used to forward the network adapter authentication information to the Bluetooth Mesh device; The network adapter authentication information is generated by the first platform cloud according to the shared root key ECDHSecret, and the shared root key is obtained by performing elliptic curve algorithm ECDH calculation on the first platform cloud and the Bluetooth Mesh device. The network provisioner authentication information includes a provisioner confirmation value, and the first platform generates the provisioner confirmation value by: Generate a confirmation key ConfirmationKey according to the shared root key; Generate a provisioner random number, wherein the provisioner random number and the authentication information AuthValue of the Bluetooth Mesh device form a first plain text; The first plaintext is encrypted using the confirmation key to generate the configuration end confirmation value.

42. The device according to claim 41, characterized in that The sending module is used to send configuration information to the first platform cloud through the second platform cloud; The receiving module is used to receive a device public key Device Public Key whose source address is the Bluetooth Mesh device; The sending module is used to send the device public key to the first platform cloud through the second platform cloud; Among them, the configuration information and the device public key are used for the first platform cloud to generate a confirmation input value ConfirmationInputs, and the configuration information includes: at least one of a configuration invitation protocol data unit value ProvisioningInvitePDUValue, a configuration capability protocol data unit value ProvisioningCapabilitiesPDUValue, and a configuration start protocol data unit value ProvisioningStartPDUValue.

43. The device according to claim 42, characterized in that The receiving module is used to receive a first random number whose source address is the Bluetooth Mesh device; The sending module is used to send the first random number to the first platform cloud through the second platform cloud, and the first random number is used by the first platform cloud to generate the confirmation input value.

44. The device according to claim 43, characterized in that The first random number is included in a universal unique identifier UUID.

45. The device according to claim 41, characterized in that The receiving module is used to receive the configuration end public key Provisoning Public Key whose source address is the first platform cloud through forwarding by the second platform cloud; The sending module is used to forward the configuration end public key to the Bluetooth Mesh device.

46. ​​The device according to any one of claims 41 to 45, characterized in that The receiving module is used to receive, through the second platform cloud, a device key DevKey, a session key SessionKey and a session random number SessionNonce whose source address is the first platform cloud.

47. The device according to any one of claims 41 to 45, characterized in that The receiving module is used to receive a second random number whose source address is the Bluetooth Mesh device; The sending module is used to send the second random number to the first platform cloud through the second platform cloud, where the second random number is used by the first platform cloud to generate first proofreading information VerifyValue; The receiving module is used to receive the first proofreading information whose source address is the first platform cloud through the second platform cloud; The sending module is used to send the first calibration information to the Bluetooth Mesh device.

48. The device according to claim 47, characterized in that The second random number is included in the UUID.

49. A first platform cloud, characterized in that: The first platform cloud includes: processor; a transceiver connected to the processor; a memory for storing executable instructions for the processor; The processor is configured to load and execute the executable instructions to implement the access authentication method as described in any one of claims 1 to 9.

50. A second platform gateway, characterized in that: The second platform gateway includes: processor; a transceiver connected to the processor; a memory for storing executable instructions for the processor; The processor is configured to load and execute the executable instructions to implement the access authentication method as described in any one of claims 17 to 24.

51. A Bluetooth wireless mesh network Mesh device, characterized in that: The Bluetooth Mesh device includes: processor; a transceiver connected to the processor; a memory for storing executable instructions for the processor; The processor is configured to load and execute the executable instructions to implement the access authentication method as described in any one of claims 10 to 16.

52. A computer-readable storage medium, characterized in that: The readable storage medium stores executable instructions, and the executable instructions are loaded and executed by a processor to implement the access authentication method according to any one of claims 1 to 24.