CN115462105A

CN115462105A - Cross-platform equipment network distribution method and device and electronic equipment

Info

Publication number: CN115462105A
Application number: CN202080100270.3A
Authority: CN
Inventors: 张军; 茹昭
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-07-22
Filing date: 2020-07-22
Publication date: 2022-12-09
Also published as: WO2022016426A1

Abstract

The embodiment of the application provides a cross-platform equipment network distribution method, a cross-platform equipment network distribution device and equipment, wherein the method comprises the following steps: the gateway receives a first confirmation value sent by a second platform cloud through a first platform cloud, and sends the first confirmation value to target equipment for verification, wherein the first confirmation value is obtained by the second platform cloud through calculation based on an installation code, and the installation code is dynamically generated or input by a user; and the gateway receives a second confirmation value sent by the target equipment, and sends the second confirmation value to the second platform cloud through the first platform cloud for verification, wherein the second confirmation value is obtained by the target equipment through calculation based on the installation code.

Description

Cross-platform equipment network distribution method and device and electronic equipment

Technical Field

The embodiment of the application relates to the technical field of the Internet of things, in particular to a cross-platform equipment network distribution method and device and electronic equipment.

Background

After being powered on, the Bluetooth Mesh (Mesh) device needs to send a broadcast packet if the Bluetooth Mesh (Mesh) device is in a state of not being distributed with a network, so that the gateway can discover the Bluetooth Mesh device through the broadcast packet. When the bluetooth Mesh device and the gateway do not belong to the same manufacturer, the bluetooth Mesh device needs to be distributed in a cross-platform mode. In the process of distributing the network to the Bluetooth Mesh equipment in a cross-platform mode, because the broadcast packet of the Bluetooth Mesh equipment is public information, any gateway in a certain range can monitor the broadcast packet, and thus, a great safety risk exists.

Disclosure of Invention

The embodiment of the application provides a cross-platform equipment network distribution method and device and electronic equipment.

The method for distributing the network to the cross-platform equipment comprises the following steps:

the gateway receives a first confirmation value sent by a second platform cloud through a first platform cloud, and sends the first confirmation value to target equipment for verification, wherein the first confirmation value is obtained by the second platform cloud through calculation based on an installation code, and the installation code is dynamically generated or input by a user;

and the gateway receives a second confirmation value sent by the target equipment, and sends the second confirmation value to the second platform cloud through the first platform cloud for verification, wherein the second confirmation value is obtained by the target equipment through calculation based on the installation code.

the method comprises the steps that a second platform cloud sends a first confirmation value to a gateway through a first platform cloud, the first confirmation value is forwarded to target equipment by the gateway to be checked, wherein the first confirmation value is obtained by the second platform cloud through calculation based on an installation code, and the installation code is dynamically generated or input by a user;

the second platform cloud receives a second confirmation value sent by the gateway through the first platform cloud, wherein the second confirmation value is calculated by the target device based on the installation code;

and the second platform cloud checks the second confirmation value based on the installation code.

the target equipment sends a second confirmation value to the gateway, the second confirmation value is forwarded to a second platform cloud by the gateway through the first platform cloud for verification, the second confirmation value is obtained by the target equipment through calculation based on an installation code, and the installation code is dynamically generated or input by a user;

the target device receives a first confirmation value sent by the gateway, wherein the first confirmation value is calculated by the second platform cloud based on the installation code;

the target device verifies the first confirmation value based on the installation code.

The utility model provides a cross-platform equipment distribution network device is applied to the gateway, the device includes:

the receiving unit is used for receiving a first confirmation value sent by a second platform cloud through a first platform cloud;

the sending unit is used for sending the first confirmation value to the target device for verification, wherein the first confirmation value is obtained by the second platform cloud through calculation based on an installation code, and the installation code is dynamically generated or input by a user;

the receiving unit is further configured to receive a second acknowledgement value sent by the target device;

the sending unit is further configured to send the second confirmation value to the second platform cloud through the first platform cloud for verification, where the second confirmation value is calculated by the target device based on the installation code.

The cross-platform equipment distribution network device provided by the embodiment of the application is applied to a second platform cloud, and comprises:

a sending unit, configured to send a first confirmation value to a gateway through a first platform cloud, where the first confirmation value is forwarded by the gateway to a target device for verification, where the first confirmation value is calculated by the second platform cloud based on an installation code, and the installation code is dynamically generated or input by a user;

a receiving unit, configured to receive, through the first platform cloud, a second confirmation value sent by the gateway, where the second confirmation value is calculated by the target device based on the installation code;

and the checking unit is used for checking the second confirmation value based on the installation code.

The cross-platform equipment distribution network device provided by the embodiment of the application is applied to target equipment, and comprises:

a sending unit, configured to send a second confirmation value to a gateway, where the second confirmation value is forwarded by the gateway to a second platform cloud through a first platform cloud for verification, where the second confirmation value is calculated by the target device based on an installation code, and the installation code is dynamically generated or input by a user;

a receiving unit, configured to receive a first confirmation value sent by the gateway, where the first confirmation value is calculated by the second platform cloud based on the installation code;

and the checking unit is used for checking the first confirmation value.

The electronic device provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing computer programs, and the processor is used for calling and running the computer programs stored in the memory and executing the cross-platform equipment network distribution method.

The storage medium provided by the embodiment of the application is used for storing a computer program, and the computer program enables a computer to execute the cross-platform device network distribution method.

According to the technical scheme, the second platform cloud calculates the first confirmation value based on the dynamically generated installation code, and the target device verifies the first confirmation value based on the installation code; similarly, the target device calculates a second confirmation value based on the dynamically generated installation code, and the second platform cloud verifies the second confirmation value based on the installation code, so that the verification between the target device and the cloud platform can be correctly realized, and the gateway can accurately distribute the network to the target device. The target device is the Bluetooth Mesh device, so that the user can control the distribution network of the own Bluetooth Mesh device, the Bluetooth Mesh device of the user is prevented from being illegally or wrongly bound by other users, and the safety of the distribution network of the cross-platform Bluetooth Mesh device is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a schematic flowchart of communication between a client device and a server device according to an embodiment of the present application;

fig. 2 is a flowchart of authentication between a bluetooth Mesh network device and a bluetooth Mesh device to be configured (i.e., a new device) according to an embodiment of the present disclosure;

fig. 3 is a flow chart of a network distribution process of a cross-platform bluetooth Mesh device according to an embodiment of the present application;

fig. 4 is a first flowchart of a method for distributing a network to a cross-platform device according to an embodiment of the present disclosure;

fig. 5 is a schematic flowchart illustration two of a method for distributing a network to cross-platform devices according to an embodiment of the present application;

fig. 6 is a third schematic flowchart of a method for distributing a network to a cross-platform device according to an embodiment of the present application;

fig. 7 is a fourth flowchart illustrating a network distribution method for cross-platform devices according to an embodiment of the present disclosure;

fig. 8 is a first schematic structural component diagram of a cross-platform device distribution network apparatus according to an embodiment of the present disclosure;

fig. 9 is a schematic structural composition diagram of a cross-platform device distribution network apparatus according to an embodiment of the present application;

fig. 10 is a schematic structural composition diagram three of a cross-platform device distribution network apparatus provided in the embodiment of the present application;

fig. 11 is a schematic diagram of a hardware component structure of an electronic device according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The Open Connectivity Foundation (OCF) is an emerging technical standard organization of the application layer of the internet of things, and the OCF establishes a Restful service framework for interconnection and intercommunication among devices of the internet of things. In the OCF Restful service framework, information such as Internet of things equipment, functional services of the OCF equipment, the state of the OCF equipment and the like is expressed through resources. The entity providing the resource is an OCF server device (hereinafter referred to as a server device), and the entity accessing the resource is an OCF client (hereinafter referred to as a client device). The service interaction between the client device and the server device is realized through resource operation methods such as creation, reading, updating, deleting or notification of resources.

The flow of communication between the client device and the server device is as shown in fig. 1: the client device sends an update resource request for a resource on the server device to the server device. The server equipment executes corresponding resource operation according to the resource updating request and sends a resource updating response to the client equipment; wherein the update resource response carries an expression of the resource.

Here, the Resource update request carries a Uniform Resource Identifier (URI) of the Resource and a Resource operation method.

The representation of the resource includes: URI of a resource, a resource type, a resource interface, and a functional attribute of a resource, etc., information included in the expression of a resource is described below:

the URI of the resource is denoted by "href" in the expression of the resource, the address of the resource of the OCF server device is provided, the value of "href" is the URI of the specific resource, and the OCF client device accesses the resource of the OCF server device through the URI of the resource.

The resource type, denoted by "rt" in the expression of resource, indicates the type of resource.

The resource interface, denoted by "if" in the representation of the resource, provides a view of the resource and a response to the resource support.

The resource attribute describes attribute information of the resource in the representation of the resource.

The OCF defines a resource discovery resource "/oic/res" which all OCF devices must support, wherein the resource discovery resource is used for discovering the OCF devices and resources; the resource discovery resource provides a function of device resource discovery, and the URI of the resource discovery resource is fixed to "/oic/res".

In order to represent the incidence relation among the resources, the OCF defines resource Links, namely, the Links of the resources; the OCF server-side equipment can provide own resources in a resource link mode, and the OCF client-side equipment can conveniently discover the resources of the OCF server-side equipment. The content of the resource link includes:

anchor, a context URI, represents the URI of the owner resource that contains the resource link.

href target URI, the URI of the target resource referenced in the resource link.

rt, resource type identification of the target resource.

if is the interface supported by the target resource.

eps-an endpoint that can access a target resource.

Because the OCF standard Protocol uses a restricted Application Protocol (CoAP) in the transport layer to carry OCF messages, each OCF server device needs to have an endpoint, and each OCF device must associate with at least one endpoint for sending and receiving messages; the client device may access a target resource of the server device through the endpoint. The end point of the target resource is represented by an 'eps' array in the parameter of the resource link, and the specific end point is represented by 'ep', namely the target resource can be accessed through the address of the value 'ep' in the 'eps' parameter.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description is made of related concepts and technologies related to the embodiments of the present application.

● Related concepts

Bluetooth Mesh network: a mesh device network constructed based on the low-power Bluetooth technology can realize many-to-many Bluetooth device communication.

A gateway: and the Bluetooth Mesh network distribution equipment is responsible for configuring equipment accessed to the Bluetooth Mesh network.

Equipment: the Bluetooth Mesh equipment of the network to be distributed needs to be added into the Bluetooth Mesh network through a Bluetooth Mesh network distribution process.

● Prior Art

After the bluetooth Mesh Device is powered on, if the bluetooth Mesh Device is in a state of not being distributed with a network, a broadcast packet, that is, an unconfigured Device Beacon (upnp Beacon) packet, needs to be sent. The broadcast packet carries a Universal Unique Identifier (UUID) of the bluetooth Mesh Device, which is referred to as a Device UUID for short. The Device UUID is key information for identifying the bluetooth Mesh Device, and the format of the Device UUID is as shown in the following table 1:

TABLE 1

In order to improve the efficiency of the distribution network of the bluetooth Mesh device, the authentication mode of the bluetooth Mesh device adopts a Static Out of Band (Static OOB) verification mode or a No Out of Band (No OOB) verification mode specified in the bluetooth Mesh protocol. The static OOB verification method is as follows: the Confirmation value (i.e., provisiong configuration) is calculated based on the static OOB information. The non OOB authentication mode is as follows: the confirmation value is calculated directly by replacing the OOB information with the value 0. No matter the static OOB verification mode or the non-OOB verification mode is adopted, the network distribution process of the Bluetooth Mesh equipment can be finished without user confirmation operations such as user input authorization value (AuthValue) and the like in the network distribution process.

As shown in fig. 2, the authentication process between the bluetooth Mesh network device and the bluetooth Mesh device to be configured (i.e. the new device) includes the following steps:

step 201: the Bluetooth Mesh network distribution equipment sends a first confirmation value to Bluetooth Mesh equipment to be distributed.

For the case of the static OOB authentication mode, the bluetooth Mesh network distribution device calculates a first confirmation value based on the static OOB information.

For the case of no OOB authenticator, the bluetooth Mesh network device calculates the first acknowledgement value with the value 0 instead of the OOB information.

Step 202: and the Bluetooth Mesh equipment to be distributed sends a second confirmation value to the Bluetooth Mesh distribution network equipment.

For the case of the static OOB authentication mode, the bluetooth Mesh device to be networked calculates a second confirmation value based on the static OOB information.

For the case of no OOB verifier, the bluetooth Mesh device to be networked calculates a second confirmation value with a value of 0 instead of OOB information.

Step 203: the Bluetooth Mesh network distribution equipment sends a first random number to Bluetooth Mesh equipment to be distributed.

Here, when the bluetooth Mesh network equipment calculates the first confirmation value, the first random number is used.

Step 204: and the to-be-distributed network Bluetooth Mesh equipment checks the first confirmation value based on the first random number.

Step 205: and the Bluetooth Mesh equipment to be distributed sends a second random number to the Bluetooth Mesh distribution network equipment.

Here, when the bluetooth Mesh device to be meshed calculates the second confirmation value, the second random number is used.

Step 206: and the Bluetooth Mesh distribution network equipment checks the second confirmation value based on the second random number.

It should be noted that the bluetooth Mesh network distribution device may be implemented by a gateway, and the bluetooth Mesh device to be distributed may also be referred to as a device for short.

The "Confirmation value" in the embodiment of the present application may be referred to as "providing configuration". The "Random number" in the embodiment of the present application may also be referred to as "Provisiong Random".

When the bluetooth Mesh device and the gateway do not belong to the same manufacturer, the bluetooth Mesh device needs to be distributed in a cross-platform (i.e. cross two internet of things cloud platforms) authentication mode, and the process of distributing the network by the cross-platform bluetooth Mesh device is shown in fig. 3, and the method comprises the following steps:

step 301: the user activates the device scanning function of the A platform gateway through voice or APP.

Step 302: the E company device transmits a broadcast packet (containing a UUID and a CID) as a specification.

Here, the E company device refers to a device developed by the E company based on the B platform, and belongs to a bluetooth Mesh device to be networked.

Here, the broadcast packet refers to a bluetooth Mesh non-distribution network broadcast packet, and the broadcast packet carries the UUID of the E company device and the CID of the B platform.

Step 303: the a-platform sends a query device type message (containing UUID and CID) to the a-platform cloud.

Here, after acquiring the broadcast packet sent by the E company device in step 302, the a platform gateway sends the UUID of the E company device and the CID of the B platform to the a platform cloud through the query device type message, and queries the device type of the E company device through the a platform cloud.

Step 303.1: the a platform cloud determines based on CID whether the E company device is a device of the a platform, if not, step 303.2 is performed.

Here, after receiving the device type query message sent by the a platform gateway, the a platform cloud determines, by using the CID in the device type query message, whether the E company device is a device developed based on the a platform (i.e., whether the E company device is a device of the a platform).

Step 303.2: and the platform cloud A queries platform information corresponding to the equipment of the company E from the interconnection and intercommunication server.

Here, if the a platform cloud determines that the E company device is not a device developed based on the a platform, authorization is required by another platform (i.e., a platform for developing the E company device). In order to query and develop the platform of the E company device, the a platform acquires the information (including information such as a B platform authentication Server (Auth Server)) of the B platform corresponding to the CID through the interconnection and interworking Server. Here, when the platform cloud a queries the interconnection and interworking server for platform information corresponding to the E company device, the platform cloud a provides the CID to the interconnection and interworking server, so that the interconnection and interworking server queries the information of the platform B through the CID.

Step 303.3: and the interconnection server sends the information of the platform B to the platform A cloud.

Step 303.4: and the A platform cloud sends a query device type message (containing the information, CID and UUID of the B platform) to the B platform cloud.

Here, the query device type message is used to query the device type of the E company device.

Step 303.5: and the B platform cloud sends the device type information to the A platform cloud.

Here, the device type information is used to determine the device type of the E company device.

Step 304: and the platform A cloud sends the device type information to the platform A gateway.

Step 305: and broadcasting the equipment type information by the A platform gateway.

Step 306: and the user executes input operation on the A platform gateway to operate the A platform gateway to connect the E company equipment.

Step 307: the a-platform gateway sends a Provisioning Invite (Provisioning Invite) message to the E-corporation device.

Step 308: the E company device sends a Provisioning Capabilities message to the a platform gateway.

Step 309: the a-platform gateway transmits a Provisioning Start message to the E-company device.

Step 310: the A platform gateway and the E company equipment complete Public Key (Public Key) exchange through the A platform cloud and the B platform cloud.

Step 311: the B platform cloud calculates a first confirmation value.

Here, the B platform cloud calculates the first confirmation value from the static OOB information or the no OBB information. Wherein the first confirmation value is calculated based on the first random number.

Step 312: the B platform cloud sends authentication information (containing a first confirmation value and a first random number) to the A platform cloud.

Step 313: the a-platform cloud sends authentication information (including a first acknowledgement value and a first random number) to the a-platform gateway.

Step 314: the a-platform gateway sends a first confirmation value to the E-company device.

Step 315: the E company device sends a second confirmation value to the a platform gateway.

Here, the E company device calculates the second confirmation value based on the static OOB information or the no OBB information. Wherein the second confirmation value is calculated based on the second random number.

Step 316: the A platform gateway sends the first random number to the E company device.

Step 317: the E company device verifies the first confirmation value based on the first random number.

Step 318: the E company device sends a second random number to the a platform gateway.

Step 319: the a-platform network sends the device authentication information (including the second confirmation value and the second random number) to the a-platform cloud.

Step 320: and the platform A cloud sends the equipment authentication information (containing a second confirmation value and a second random number) to the platform B cloud.

Step 321: and the platform B cloud checks the second confirmation value based on the second random number.

Step 322: the B platform cloud sends the authentication result (containing the device information of the E company device) to the a platform cloud.

Step 323: the A platform cloud stores device information of the E company device.

Here, the device information includes information such as control functions and control instructions supported by the device.

Step 324: and the platform A cloud sends an authentication result to the platform A gateway.

Step 325: the a-platform gateway sends configuration data to the E-company device.

Step 326: and the A platform gateway broadcasts the authentication result.

Through the process, the E company device formally becomes a node of the Bluetooth Mesh network, and the configuration process is completed.

In the flow shown in fig. 3, the calculation of the first confirmation value or the second confirmation value is based on the static OOB information or the no OOB information, that is, the authentication manner between the B-platform cloud and the E-company device is a static OOB authentication manner or a no OOB authentication manner. Because the broadcast packet of the E company device is public information, any gateway in the scanning distance can monitor the broadcast packet, and if a static OOB verification mode or no OOB verification mode is adopted, it may happen that the E company device of the user a is network-distribution bound by the gateway of the user B, so that the user B can control the E company device of the user a, but the user a cannot control the E company device, and there is a great security risk (for example, devices such as a door lock, a camera, and the like are bound by non-owner devices).

Therefore, the following technical scheme of the embodiment of the application is provided. The technical scheme of the embodiment of the application provides a cross-platform Bluetooth Mesh device distribution network method (referred to as a cross-platform device distribution network method for short), a dynamic OOB verification mode needs to be adopted in the distribution network process, namely, the distribution network of the Bluetooth Mesh device can be realized only by inputting an installation code through user operation. In order to better understand the technical solution of the present application, the following description is made with reference to the embodiments.

Fig. 4 is a first flowchart of a cross-platform device network distribution method provided in the embodiment of the present application, and as shown in fig. 4, the cross-platform device network distribution method includes the following steps:

step 401: the gateway receives a first confirmation value sent by a second platform cloud through a first platform cloud, and sends the first confirmation value to target equipment for verification, wherein the first confirmation value is obtained by the second platform cloud through calculation based on an installation code, and the installation code is dynamically generated or input by a user.

In the embodiment of the present application, the gateway refers to a gateway of the first platform, that is, the gateway may directly communicate with the first platform cloud. Communication between the gateway and the second platform cloud needs to be forwarded through the first platform cloud.

In the embodiment of the application, the gateway may also be referred to as a bluetooth Mesh network distribution device, and the target device may also be referred to as a bluetooth Mesh device to be distributed.

In this embodiment, before the gateway receives the first confirmation value sent by the second platform cloud through the first platform cloud, the gateway sends the installation code to the second Ping Taiyun through the first platform cloud, where the installation code is used for the second platform cloud to calculate the first confirmation value.

In this embodiment, the first confirmation value is calculated by the second platform cloud based on an installation code and a first random number, where the first random number is generated by the second platform cloud. In order to enable the target device to check the first confirmation value, the gateway receives the first random number sent by the second platform cloud through the first platform cloud; and the gateway sends the first random number to the target equipment, wherein the first random number and the installation code are used for verifying the first confirmation value by the target equipment.

In one example, the calculation of the first confirmation value may be in the following manner:

ConfirmationProvisioner＝AES-CMAC _{ConfirmationKey} (RandomProvisioner||SetupCode)；

the ConfirmationProvisioner is a first confirmation value, the RandomProvisioner is a first random number generated by the second platform cloud, the SetupCode is an installation code, the encryption algorithm is AES-CMAC, and the encryption key is ConfirmationKey.

It should be noted that the second platform cloud may use other computing methods to calculate the first confirmation value. In addition, the second platform cloud may also add other parameters to calculate the first confirmation value. The encryption algorithm and the calculation parameter adopted by the target equipment for verifying the first confirmation value are the same as those adopted by the second platform cloud computing first confirmation value, and thus the distribution network can be successfully carried out.

Step 402: and the gateway receives a second confirmation value sent by the target equipment, and sends the second confirmation value to the second platform cloud through the first platform cloud for verification, wherein the second confirmation value is obtained by the target equipment through calculation based on the installation code.

In this embodiment of the present application, the second confirmation value is calculated by the target device based on the installation code and a second random number, and the second random number is generated by the target device. In order to enable a second platform cloud to verify the second confirmation value, the gateway receives the second random number sent by the target device; and the gateway sends the second random number to the second platform cloud through the first platform cloud, wherein the second random number and the installation code are used for verifying the second confirmation value by the second platform cloud.

In one example, the second confirmation value may be calculated in the following manner:

ConfirmationDevice＝AES-CMAC _{ConfirmationKey} (RandomDevice||SetupCode)；

wherein, the ConfirmationDevice is a second confirmation value, the RandomDevice is a second random number generated by the target device, the SetupCode is an installation code, the encryption algorithm is AES-CMAC, and the encryption key is ConfirmationKey.

It should be noted that the target device may calculate the second confirmation value by other calculation methods. In addition, the target device may also add other parameters to calculate the second confirmation value. The encryption algorithm and the calculation parameter used when the second Ping Taiyun verifies the second confirmation value need to be the same as the encryption algorithm and the calculation parameter used when the target device calculates the second confirmation value, so that the distribution network can be successfully performed.

In an embodiment of the present application, the method further includes: the method comprises the steps of inquiring the device type of the target device by the gateway, inviting the gateway and the target device, and exchanging a public key between the gateway and the target device. In particular, the amount of the solvent to be used,

1. the gateway receives the device type information (such as security devices, intelligent door locks and other types) of the target device sent by the second platform cloud through the first platform cloud;

2. the gateway sends an invitation message to the target equipment;

3. the gateway receives a configuration capability message sent by the target equipment;

4. the gateway sends a configuration start message to the target device;

5. the gateway exchanges public keys with the target equipment through the first platform cloud and the second platform cloud;

at least one of the device type information, the invitation message and the configuration capability message carries first indication information, wherein the first indication information is used for indicating that an output out-of-band OOB verification mode and/or an input OOB verification mode is preferentially adopted; the configuration start message carries second indication information, and the second indication information is used for indicating that an OOB authentication mode is determined to be adopted or an OOB authentication mode is input.

In an optional manner, after the gateway receives the configuration capability message sent by the target device, the method further includes: the gateway determines to adopt the OOB authentication mode or input the OOB authentication mode based on at least one of the following conditions: the device type information of the target device, the first indication information carried in the device type information, and the first indication information carried in the configuration capability message.

In the above technical solution, the installation code is dynamically generated or input by a user.

In one example, the installation code is dynamically generated. Such as the gateway dynamically generating and outputting the installation code. The target device then dynamically generates and outputs the installation code, for example.

In another example, the installation code is user-entered. For example, the target device outputs a dynamic or static installation code that the user sees and then enters into the gateway. And for example, the gateway outputs a dynamic or static installation code, and the user inputs the installation code to the target equipment after seeing the installation code. For another example, a static installation code is printed on the instruction sheet, and the user inputs the installation code to the target device or the gateway after seeing the installation code on the instruction sheet.

The technical scheme of the embodiment of the application is based on a dynamic OOB verification mode. Further, there are two dynamic OOB authentication methods, one is an output OOB authentication method, and the other is an input OOB authentication method. These two modes are explained below.

The method I comprises the following steps: in the case of the output OOB authentication mode, the installation code is output by the target device and the installation code is input by a user on the gateway.

In one example, the target device outputs an installation code, which may be a dynamic or static random value, for example, the target device outputs the random value by means of a screen display, a sound, a flash, a vibration, a two-dimensional code, a specification, or the like. The user inputs the installation code on the gateway, wherein the gateway is provided with a screen, a microphone, a camera, a key and other user input devices, and the user can input the installation code through the input devices so as to confirm the installation code output by the target equipment. Namely: the user may obtain the installation code through the output of the target device and enter the installation code onto the gateway.

The second method comprises the following steps: and under the condition of inputting the OOB verification mode, the installation code is output by the gateway, and the installation code is input on the target equipment by a user.

In one example, the gateway outputs an installation code, which may be a dynamic or static random value, for example, the gateway outputs the random value by means of a screen display, sound, flashing, vibration, two-dimensional code, instructions, and the like. The user inputs the installation code on the target device, where the target device has a screen, a microphone, a camera, a key, etc. user input means, and the user can input the installation code through the input means to confirm the installation code output by the gateway. Namely: the user may obtain the installation code through the output of the gateway and enter the installation code onto the target device.

In addition to the first and second modes, the following OBB verification mode may be available: the static installation code is printed on the instruction book, and the user inputs the installation code into the target device or the gateway after seeing the installation code on the instruction book.

After the mutual authentication between the gateway and the target device is completed through the technical scheme of the embodiment of the application, further, the method further comprises the following steps: and the gateway receives the authentication result sent by the second platform cloud through the first platform cloud and sends configuration data to the target equipment.

Fig. 5 is a schematic flowchart of a second method for distributing a network through cross-platform devices according to an embodiment of the present application, where as shown in fig. 5, the method for distributing a network through cross-platform devices includes the following steps:

step 501: the second platform cloud sends a first confirmation value to the gateway through the first platform cloud, the first confirmation value is forwarded to the target device by the gateway for verification, the first confirmation value is obtained by the second platform cloud through calculation based on an installation code, and the installation code is dynamically generated or input by a user.

In this embodiment, the gateway refers to a gateway of the first platform, that is, the gateway may directly communicate with the first platform cloud. Communication between the gateway and the second platform cloud needs to be forwarded through the first platform cloud.

In this embodiment, before the second platform cloud sends the first confirmation value to the gateway through the first platform cloud, the second platform cloud receives the installation code sent by the gateway through the first platform cloud, where the installation code is used for the second platform cloud to calculate the first confirmation value.

In this embodiment, the first confirmation value is calculated by the second platform cloud based on an installation code and a first random number, where the first random number is generated by the second platform cloud. In order to enable the target device to verify the first confirmation value, the second platform cloud sends the first random number to the gateway through the first platform cloud, and the first random number is forwarded to the target device by the gateway, where the first random number and the installation code are used for the target device to verify the first confirmation value.

Step 502: and the second platform cloud receives a second confirmation value sent by the gateway through the first platform cloud, wherein the second confirmation value is calculated by the target equipment based on the installation code.

In this embodiment of the present application, the second confirmation value is calculated by the target device based on the installation code and a second random number, and the second random number is generated by the target device. In order to enable the second platform cloud to verify the second confirmation value, the second platform cloud receives the second random number sent by the gateway through the first platform cloud, wherein the second random number and the installation code are used for the second platform cloud to verify the second confirmation value.

ConfirmationDevice＝AES-CMAC _{ConfirmationKey} (RandomDevice||SetupCode)；

It should be noted that the target device may calculate the second confirmation value by other calculation methods. In addition, the target device may also add other parameters to calculate the second confirmation value.

Step 503: the second platform cloud verifies the second confirmation value based on the installation code.

Specifically, the second platform cloud calculates a first check value based on the second random number and the installation code, and compares the first check value with the second confirmation value; if the first verification value is the same as the second confirmation value, the second platform cloud confirms that the second confirmation value is successfully verified; and if the first verification value is different from the second confirmation value, the second platform cloud confirms that the second confirmation value is failed to be verified.

It should be noted that the encryption algorithm (i.e., calculating the first check value) and the calculation parameter used by the second platform cloud when verifying the second confirmation value need to be the same as the encryption algorithm and the calculation parameter used by the target device to calculate the second confirmation value, so that the distribution network can be successfully performed.

In addition to the first and second modes, the following OBB verification mode may be used: the static installation code is printed on the instruction book, and the user inputs the installation code into the target device or the gateway after seeing the installation code on the instruction book.

Fig. 6 is a third schematic flowchart of a cross-platform device network distribution method provided in the embodiment of the present application, and as shown in fig. 6, the cross-platform device network distribution method includes the following steps:

step 601: the target device sends a second confirmation value to the gateway, the second confirmation value is forwarded to a second platform cloud through the first platform cloud by the gateway for verification, the second confirmation value is obtained by the target device through calculation based on an installation code, and the installation code is dynamically generated or input by a user.

In this embodiment of the present application, the second confirmation value is calculated by the target device based on the installation code and a second random number, and the second random number is generated by the target device. In order to enable the second platform cloud to verify the second confirmation value, the target device sends the second random number to the gateway, and the second random number is forwarded to the second platform cloud by the gateway through the first platform cloud, wherein the second random number and the installation code are used for the second platform cloud to verify the second confirmation value.

Step 602: and the target equipment receives a first confirmation value sent by the gateway, wherein the first confirmation value is calculated by the second platform cloud based on the installation code.

In this embodiment, the first confirmation value is calculated by the second platform cloud based on an installation code and a first random number, where the first random number is generated by the second platform cloud. In order to enable the target device to verify the first confirmation value, the target device receives the first random number sent by the gateway, where the first random number and the installation code are used for the target device to verify the first confirmation value.

wherein, the configrationprovider is a first confirmation value, the randompprovisioner is a first random number generated by the second platform cloud, the SetupCode is an installation code, the encryption algorithm is AES-CMAC, and the encryption key is configrationkey.

It should be noted that the second platform cloud may use other computing methods to calculate the first confirmation value. In addition, the second platform cloud may also add other parameters to calculate the first confirmation value.

Step 603: the target device verifies the first confirmation value based on the installation code.

Specifically, the target device calculates a second check value based on the first random number and the installation code, and compares the second check value with the first confirmation value; if the second check value is the same as the first confirmation value, the target device confirms that the first confirmation value is checked successfully; and if the second check value is different from the first confirmation value, the target device confirms that the first confirmation value is failed to be checked.

It should be noted that, when the target device verifies the first confirmation value (i.e., calculates the second check value), the encryption algorithm and the calculation parameter used by the target device are the same as those used by the second platform cloud to calculate the first confirmation value, so that the distribution network can be successfully performed.

The first method is as follows: in the case of the output OOB authentication mode, the installation code is output by the target device and the installation code is input by a user on the gateway.

In addition to the first and second modes, the following OBB verification mode may be used: the static installation code is printed on the instruction book, and the user inputs the installation code to the target device or the gateway after seeing the installation code on the instruction book.

The technical solutions in the embodiments of the present application are illustrated below with reference to specific flow charts.

Fig. 7 is a fourth flowchart illustrating a network distribution method for cross-platform devices provided in an embodiment of the present application, where a platform gateway corresponds to a gateway in the embodiment of the present application, an E company device corresponds to a target device in the embodiment of the present application, an a platform cloud corresponds to a first platform cloud in the embodiment of the present application, and a B platform cloud corresponds to a second platform cloud in the embodiment of the present application, and as shown in fig. 7, the network distribution method for cross-platform devices includes the following steps:

step 701: the user activates the device scanning function of the A platform gateway through voice or APP.

Step 702: the E company device transmits a broadcast packet (containing a UUID and a CID) as a specification.

Here, the E company device refers to a device developed by the E company based on the B platform, and belongs to the bluetooth Mesh device to be networked.

Step 703: the a platform sends a query device type message (containing UUID and CID) to the a platform cloud.

Here, after acquiring the broadcast packet sent by the E company device in step 702, the a platform gateway sends the UUID of the E company device and the CID of the B platform to the a platform cloud through the query device type message, and queries the device type of the E company device through the a platform cloud.

Step 703.1: the A platform cloud determines whether the E company equipment is the A platform equipment based on CID, if not, step 703.2 is executed.

Step 703.2: and the platform cloud A queries platform information corresponding to the equipment of the company E from the interconnection and intercommunication server.

Step 703.3: and the interconnection server sends the information of the platform B to the platform A cloud.

Step 703.4: and the A platform cloud sends a query device type message (containing the information, CID and UUID of the B platform) to the B platform cloud.

Step 703.5: and the B platform cloud sends the device type information to the A platform cloud.

Optionally, the B platform cloud indicates that the output OOB authentication method and/or the input OOB authentication method is preferentially adopted according to the device type information. That is, when the a-platform gateway and the E-company device support the output OOB authentication method and/or the input OOB authentication method, the output OOB authentication method and/or the input OOB authentication method is preferentially adopted instead of the static OOB authentication method and the no OOB authentication method.

Description of the drawings: and under the output OOB verification mode, the equipment of the company E outputs an installation code, and the user inputs the installation code on the platform A gateway. And under the condition of inputting the OOB verification mode, the A platform gateway outputs an installation code, and the user inputs the installation code on the E company equipment. The OOB authentication procedure of this embodiment takes the output OOB authentication method as an example, but the scheme is also applicable to the input OOB authentication method, and the difference is only that the roles of the devices for outputting and inputting the installation code are different.

Step 704: and the platform A cloud sends the device type information to the platform A gateway.

Optionally, the B platform cloud indicates to preferentially adopt an output OOB authentication manner and/or an input OOB authentication manner according to the device type information. That is, when the a-platform gateway and the E-company device support the output OOB authentication method and/or the input OOB authentication method, the output OOB authentication method and/or the input OOB authentication method is preferentially adopted instead of the static OOB authentication method and the no OOB authentication method.

Step 705: and broadcasting the equipment type information by the A platform gateway.

Step 706: and the user executes input operation on the A platform gateway to operate the A platform gateway to connect the E company equipment.

Step 707: the a-platform gateway sends a Provisioning Invite (Provisioning Invite) message to the E-corporation device.

Optionally, the a-platform gateway instructs, according to the device type information of the device and/or the indication of the a-platform cloud (from step 704), to preferentially adopt the output OOB authentication method and/or the input OOB authentication method.

Step 708: the E company device sends a Provisioning Capabilities message to the a platform gateway.

Optionally, the E company device instructs to preferentially adopt the output OOB authentication mode and/or the input OOB authentication mode.

Step 709 (optional step): the a-platform gateway determines to employ the outgoing OOB authentication scheme or the incoming OOB authentication scheme based on one or more of the device type information, the indication of the a-platform cloud (from step 704), and the indication of the E-company device (from step 708).

Step 710: the a-platform gateway sends a Provisioning Start message to the E-company device.

Optionally, the configuration start message indicates that the output OOB authentication mode or the input OOB authentication mode is determined to be used.

Step 711: the A platform gateway and the E company equipment complete Public Key (Public Key) exchange through the A platform cloud and the B platform cloud.

Step 712: the E company device outputs the installation code.

Here, taking the output OOB authentication manner as an example, the E company device outputs an installation code, which may be a dynamic or static random value, for example, the E company device outputs the random value by means of a screen display, a sound, a flash, a vibration, a two-dimensional code, a specification, and the like.

Step 713: the user enters the installation code on the a-platform gateway.

Here, the a-platform gateway has a user input device such as a screen, a microphone, a camera, and a button, and the user can input the installation code through the input device to confirm the installation code output by the E company device.

Step 714: and the A platform gateway reports the installation code to the A platform cloud.

Step 715: and the platform A cloud reports the installation code to the platform B cloud.

Step 716: the B platform cloud calculates a first validation value using the installation code.

the configuration provider is a first confirmation value, the random provider is a first random number generated by the B platform cloud, the SetupCode is an installation code, the encryption algorithm is AES-CMAC, and the encryption key is the configuration key.

It should be noted that the B platform cloud may use other computing methods to calculate the first confirmation value. In addition, the B platform cloud may also add other parameters to calculate the first confirmation value. The encryption algorithm and the calculation parameters adopted by the company E equipment for verifying the first confirmation value are the same as those adopted by the platform B cloud computing first confirmation value, and thus the distribution network can be successfully carried out.

Step 717: the B platform cloud sends authentication information (containing a first confirmation value and a first random number) to the A platform cloud.

Step 718: the a-platform cloud sends authentication information (including a first acknowledgement value and a first random number) to the a-platform gateway.

Step 719: the A-platform gateway sends a first confirmation value to the E-corporation device.

Step 720: the E company device calculates a second confirmation value using the installation code.

ConfirmationDevice＝AES-CMAC _{ConfirmationKey} (RandomDevice||SetupCode)；

It should be noted that the E company device may calculate the second confirmation value by using other calculation methods. In addition, the E company device may add other parameters to calculate the second confirmation value. The encryption algorithm and the calculation parameter adopted by the B Ping Taiyun for verifying the second confirmation value are the same as those adopted by the E company equipment for calculating the second confirmation value, so that the distribution network can be successfully carried out.

Step 721: the E company device sends a second confirmation value to the a platform gateway.

Step 722: the A platform gateway sends the first random number to the E company device.

Step 723: the E company device verifies the first confirmation value based on the first random number and the installation code.

Here, the E company device calculates the verification value by the same calculation method as in step 716, compares the verification value with the first confirmation value obtained in step 719, and if the verification value is the same, performs step 724.

Step 724: the E company device sends a second random number to the a platform gateway.

Step 725: the a-platform network sends the device authentication information (including the second confirmation value and the second random number) to the a-platform cloud.

Step 726: and the platform A cloud sends the equipment authentication information (containing a second confirmation value and a second random number) to the platform B cloud.

Step 727: and the platform B cloud checks the second confirmation value based on the second random number and the installation code.

Here, the B-platform cloud calculates the verification value by the same calculation method as in step 720, compares the verification value with the second confirmation value obtained in step 726, and if the verification value is the same, executes step 728.

Step 728: the B platform cloud sends the authentication result (containing the device information of the E company device) to the a platform cloud.

Step 729: the A platform cloud stores device information of the E company device.

Step 730: and the platform cloud A sends an authentication result to the platform gateway A.

Step 731: the a-platform gateway sends configuration data to the E-company device.

Step 732: and the A platform gateway broadcasts the authentication result.

In an optional embodiment, the E company device outputs the installation code after entering the distribution network mode, and the user operates and inputs the installation code on the a platform gateway. Referring to fig. 7, step 712 and step 713 may be performed before step 703. Step 714 is deleted and the a platform gateway uploads the installation code to the a platform cloud via step 703. And deleting the step 715, sending the installation code to the platform B cloud by the platform A cloud through the step 703.4, and keeping other processes unchanged.

Fig. 8 is a schematic structural composition diagram of a cross-platform device distribution network apparatus provided in the embodiment of the present application, which is applied to a gateway, and the apparatus includes:

a receiving unit 801, configured to receive, by a first platform cloud, a first acknowledgement value sent by a second platform cloud;

a sending unit 802, configured to send the first confirmation value to a target device for verification, where the first confirmation value is obtained by the second platform cloud through calculation based on an installation code, and the installation code is dynamically generated or input by a user;

the receiving unit 801 is further configured to receive a second acknowledgement value sent by a target device;

the sending unit 802 is further configured to send the second confirmation value to the second platform cloud through the first platform cloud for verification, where the second confirmation value is obtained by the target device through calculation based on the installation code.

In an optional manner, the sending unit 802 is further configured to send the installation code to the second Ping Taiyun through the first platform cloud, where the installation code is used for the second platform cloud to calculate the first confirmation value.

In an alternative, the first confirmation value is calculated by the second platform cloud based on an installation code and a first random number, wherein the first random number is generated by the second platform cloud.

In an optional manner, the receiving unit 801 is further configured to receive, by the first platform cloud, the first random number sent by the second platform cloud;

the sending unit 802 is further configured to send the first random number to the target device, where the first random number and the installation code are used for the target device to check the first confirmation value.

In an alternative, the second confirmation value is calculated by the target device based on the installation code and a second random number, the second random number being generated by the target device.

In an optional manner, the receiving unit 801 is further configured to receive the second random number sent by the target device;

the sending unit 802 is further configured to send the second random number to the second platform cloud through the first platform cloud, where the second random number and the installation code are used for the second platform cloud to check the second confirmation value.

In an optional manner, the receiving unit 801 is further configured to receive, by the first platform cloud, device type information of the target device sent by the second platform cloud;

the sending unit 802 is further configured to send an invitation message to the target device;

the receiving unit 801 is further configured to receive a configuration capability message sent by the target device;

the sending unit 802 is further configured to send a configuration start message to the target device;

at least one of the device type information, the invitation message and the configuration capability message carries first indication information, wherein the first indication information is used for indicating that an output OOB authentication mode and/or an input OOB authentication mode is preferentially adopted; the configuration start message carries second indication information, and the second indication information is used for indicating that an OOB authentication mode is determined to be adopted or an OOB authentication mode is input.

In an optional manner, the apparatus further comprises:

a determining unit (not shown in the figure) for determining whether to adopt the OOB authentication mode or input the OOB authentication mode based on at least one of the following: the device type information of the target device, the first indication information carried in the device type information, and the first indication information carried in the configuration capability message.

In an alternative, in the case of the output OOB authentication mode,

the installation code is output by the target device and the installation code is input by a user on the gateway.

In an alternative, in the case of the input OOB authentication mode,

the installation code is output by the gateway and the installation code is input by a user on the target device.

In an optional manner, the receiving unit 801 is further configured to receive, by the first platform cloud, an authentication result sent by the second platform cloud;

the sending unit 802 is further configured to send configuration data to the target device.

Those skilled in the art should understand that the above-mentioned related description of the cross-platform device distribution network apparatus in the embodiment of the present application may be understood by referring to the related description of the cross-platform device distribution network method in the embodiment of the present application.

Fig. 9 is a schematic structural composition diagram of a cross-platform device distribution network apparatus provided in an embodiment of the present application, where the apparatus is applied to a second platform cloud, and the apparatus includes:

a sending unit 901, configured to send a first confirmation value to a gateway through a first platform cloud, where the first confirmation value is forwarded by the gateway to a target device for verification, where the first confirmation value is obtained by the second platform cloud through calculation based on an installation code, and the installation code is dynamically generated or input by a user;

a receiving unit 902, configured to receive, by the first platform cloud, a second acknowledgement value sent by the gateway, where the second acknowledgement value is calculated by the target device based on the installation code;

a verifying unit 903, configured to verify the second confirmation value based on the installation code.

In an optional manner, the receiving unit 902 is further configured to receive, by the first platform cloud, an installation code sent by the gateway, where the installation code is used for the second platform cloud to calculate the first confirmation value.

In an optional manner, the sending unit 901 is further configured to send the first random number to the gateway through the first platform cloud, where the first random number is forwarded to the target device by the gateway, and the first random number and the installation code are used by the target device to check the first confirmation value.

In an optional manner, the receiving unit 902 is further configured to receive, by the first platform cloud, the second random number sent by the gateway, where the second random number and the installation code are used by the second platform cloud to check the second confirmation value.

In an optional manner, the checking unit 903 is configured to calculate a first check value based on the second random number and the installation code, and compare the first check value with the second confirmation value; if the first verification value is the same as the second confirmation value, the second confirmation value is verified successfully; and if the first verification value is different from the second verification value, confirming that the verification of the second verification value fails.

In an alternative, the installation code is output by the target device and the installation code is input by a user on the gateway.

In an alternative, the installation code is output by the gateway and the installation code is input by a user on the target device.

Fig. 10 is a schematic structural composition diagram of a cross-platform device distribution network apparatus provided in the embodiment of the present application, which is applied to a target device, and the apparatus includes:

a sending unit 1001, configured to send a second confirmation value to a gateway, where the second confirmation value is forwarded to a second platform cloud by the gateway through a first platform cloud and is verified, where the second confirmation value is obtained by the target device through calculation based on an installation code, and the installation code is dynamically generated or input by a user;

a receiving unit 1002, configured to receive a first confirmation value sent by the gateway, where the first confirmation value is calculated by the second platform cloud based on the installation code;

a checking unit 1003, configured to check the first confirmation value.

In an optional manner, the receiving unit 1002 is further configured to receive the first random number sent by the gateway, where the first random number and the installation code are used for the target device to check the first confirmation value.

In an optional manner, the checking unit 1003 is configured to calculate a second check value based on the first random number and the installation code, and compare the second check value with the first confirmation value; if the second check value is the same as the first confirmation value, confirming that the first confirmation value is checked successfully; and if the second check value is different from the first confirmation value, confirming that the first confirmation value fails to be checked.

In an optional manner, the sending unit 1001 is further configured to send the second random number to the gateway, where the second random number is forwarded to the second platform cloud by the gateway through the first platform cloud, and the second random number and the installation code are used by the second platform cloud to check the second confirmation value.

The embodiment of the present invention further provides a gateway, which includes a processor and a memory for storing a computer program capable of running on the processor, wherein when the processor is used for running the computer program, the step of the above cross-platform device network distribution method is executed.

The embodiment of the invention also provides a platform cloud, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the cross-platform equipment network distribution method when the computer program is run.

The embodiment of the present invention further provides a device, which includes a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is configured to execute the steps of the above cross-platform device network distribution method when running the computer program.

Fig. 11 is a schematic diagram of a hardware composition structure of an electronic device (gateway, second platform cloud, device) according to an embodiment of the present invention, where the electronic device 1100 includes: at least one processor 1101, memory 1102, and at least one network interface 1104. The various components in the electronic device 1100 are coupled together by a bus system 1105. It is understood that the bus system 1105 serves to enable connected communication between these components. The bus system 1105 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are labeled in fig. 11 as the bus system 1105.

It will be appreciated that the memory 1102 can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be ROM, programmable Read-Only Memory (PROM), erasable Programmable Read-Only Memory (EPROM), electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic random access Memory (FRAM), flash Memory (Flash Memory), magnetic surface Memory, optical Disc, or Compact Disc Read-Only Memory (CD-ROM); the magnetic surface storage may be disk storage or tape storage. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), synchronous Static Random Access Memory (SSRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), enhanced Synchronous Dynamic Random Access Memory (ESDRAM), enhanced Synchronous Dynamic Random Access Memory (Enhanced DRAM), synchronous Dynamic Random Access Memory (SLDRAM), direct Memory (DRmb Access), and Random Access Memory (DRAM). The memory 1102 described in connection with the embodiments of the invention is intended to comprise, without being limited to, these and any other suitable types of memory.

The memory 1102 in embodiments of the present invention is used to store various types of data in support of the operation of the electronic device 1100. Examples of such data include: any computer program for operating on the electronic device 1100, such as application programs 11022. Programs that implement methods in accordance with embodiments of the invention may be included in application 11022.

The methods disclosed in the embodiments of the present invention described above may be implemented in the processor 1101 or by the processor 1101. The processor 1101 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by instructions in the form of hardware, integrated logic circuits, or software in the processor 1101. The Processor 1101 described above may be a general purpose Processor, a Digital Signal Processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. Processor 1101 may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present invention. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed by the embodiment of the invention can be directly implemented by a hardware decoding processor, or can be implemented by combining hardware and software modules in the decoding processor. The software modules may be located in a storage medium located in the memory 1102, and the processor 1101 reads the information in the memory 1102 to perform the steps of the aforementioned methods in conjunction with its hardware.

In an exemplary embodiment, the electronic Device 1100 may be implemented by one or more Application Specific Integrated Circuits (ASICs), DSPs, programmable Logic Devices (PLDs), complex Programmable Logic Devices (CPLDs), FPGAs, general purpose processors, controllers, MCUs, MPUs, or other electronic components for performing the aforementioned methods.

The embodiment of the application also provides a storage medium for storing the computer program.

Optionally, the storage medium may be applied to the gateway in the embodiment of the present application, and the computer program enables the computer to execute corresponding processes in each method executed by the gateway in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the storage medium may be applied to the second platform cloud in the embodiment of the present application, and the computer program enables the computer to execute corresponding processes in the methods executed by the second platform cloud in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the storage medium may be applied to the target device in the embodiment of the present application, and the computer program enables the computer to execute corresponding processes in each method executed by the target device in the embodiment of the present application, which is not described herein again for brevity.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only exemplary of the present invention and should not be taken as limiting the scope of the present invention, and any modifications, equivalents, improvements, etc. that are within the spirit and principle of the present invention should be included in the present invention.

Claims

A cross-platform device network distribution method, the method comprising:

the gateway receives a first confirmation value sent by a second platform cloud through a first platform cloud, and sends the first confirmation value to target equipment for verification, wherein the first confirmation value is obtained by the second platform cloud through calculation based on an installation code, and the installation code is dynamically generated or input by a user;

and the gateway receives a second confirmation value sent by the target equipment, and sends the second confirmation value to the second platform cloud through the first platform cloud for verification, wherein the second confirmation value is obtained by the target equipment through calculation based on the installation code.
The method of claim 1, wherein prior to the gateway receiving, via the first platform cloud, the first acknowledgement value sent by the second platform cloud, the method further comprises:

the gateway sends the installation code to the second Ping Taiyun through the first platform cloud, wherein the installation code is used for the second platform cloud to calculate the first confirmation value.
The method of claim 1 or 2, wherein the first confirmation value is calculated by the second platform cloud based on an installation code and a first random number, wherein the first random number is generated by the second platform cloud.
The method of claim 3, wherein the method further comprises:

the gateway receives the first random number sent by the second platform cloud through the first platform cloud;

and the gateway sends the first random number to the target equipment, wherein the first random number and the installation code are used for verifying the first confirmation value by the target equipment.
The method of any of claims 1 to 4, wherein the second confirmation value is calculated by the target device based on the installation code and a second random number, the second random number being generated by the target device.
The method of claim 5, wherein the method further comprises:

the gateway receives the second random number sent by the target equipment;

and the gateway sends the second random number to the second platform cloud through the first platform cloud, wherein the second random number and the installation code are used for the second platform cloud to check the second confirmation value.
The method of any of claims 1 to 6, wherein the method further comprises:

the gateway receives the device type information of the target device sent by the second platform cloud through the first platform cloud;

the gateway sends an invitation message to the target equipment;

the gateway receives a configuration capability message sent by the target equipment;

the gateway sends a configuration starting message to the target equipment;

the gateway exchanges public keys with the target equipment through the first platform cloud and the second platform cloud;

at least one of the device type information, the invitation message and the configuration capability message carries first indication information, wherein the first indication information is used for indicating that an output out-of-band OOB authentication mode and/or an input OOB authentication mode is preferentially adopted; the configuration start message carries second indication information, and the second indication information is used for indicating that an OOB authentication mode is determined to be adopted or an OOB authentication mode is input.
The method of claim 7, wherein after the gateway receives the configuration capability message sent by the target device, the method further comprises:

the gateway determines to adopt the OOB authentication mode or input the OOB authentication mode based on at least one of the following modes: the device type information of the target device, the first indication information carried in the device type information, and the first indication information carried in the configuration capability message.
The method according to claim 7 or 8, wherein, in case of outputting the OOB authentication mode,

the installation code is output by the target device and the installation code is input by a user on the gateway.
The method according to claim 7 or 8, wherein, in case of the input OOB authentication mode,

the installation code is output by the gateway and the installation code is input by a user on the target device.
The method of any of claims 1 to 10, wherein the method further comprises:

and the gateway receives the authentication result sent by the second platform cloud through the first platform cloud and sends configuration data to the target equipment.
A cross-platform device network distribution method, the method comprising:

the method comprises the steps that a second platform cloud sends a first confirmation value to a gateway through a first platform cloud, the first confirmation value is forwarded to target equipment by the gateway to be checked, wherein the first confirmation value is obtained by the second platform cloud through calculation based on an installation code, and the installation code is dynamically generated or input by a user;

the second platform cloud receives a second confirmation value sent by the gateway through the first platform cloud, wherein the second confirmation value is obtained by the target device through calculation based on the installation code;

the second platform cloud verifies the second confirmation value based on the installation code.
The method of claim 12, wherein prior to the second platform cloud sending the first confirmation value to the gateway through the first platform cloud, the method further comprises:

and the second platform cloud receives an installation code sent by the gateway through the first platform cloud, wherein the installation code is used for the second platform cloud to calculate the first confirmation value.
The method of claim 12 or 13, wherein the first confirmation value is calculated by the second platform cloud based on an installation code and a first random number, wherein the first random number is generated by the second platform cloud.
The method of claim 14, wherein the method further comprises:

and the second platform cloud sends the first random number to the gateway through the first platform cloud, the first random number is forwarded to the target equipment by the gateway, and the first random number and the installation code are used for verifying the first confirmation value by the target equipment.
The method of any of claims 12 to 15, wherein the second confirmation value is calculated by the target device based on the installation code and a second random number, the second random number being generated by the target device.
The method of claim 16, wherein the method further comprises:

and the second platform cloud receives the second random number sent by the gateway through the first platform cloud, wherein the second random number and the installation code are used for verifying the second confirmation value by the second platform cloud.
The method of claim 17, wherein the second platform cloud verifying the second validation value based on the installation code comprises:

the second platform cloud calculates a first check value based on the second random number and the installation code, and compares the first check value with the second confirmation value;

if the first verification value is the same as the second confirmation value, the second platform cloud confirms that the second confirmation value is successfully verified;

and if the first verification value is different from the second confirmation value, the second platform cloud confirms that the second confirmation value is failed to be verified.
The method of any of claims 12 to 18, wherein the installation code is output by the target device and the installation code is input by a user on the gateway.
The method of any of claims 12 to 18, wherein the installation code is output by the gateway and the installation code is input by a user on the target device.
A cross-platform device network distribution method, the method comprising:

the target equipment sends a second confirmation value to the gateway, the second confirmation value is forwarded to a second platform cloud by the gateway through the first platform cloud for verification, the second confirmation value is obtained by the target equipment through calculation based on an installation code, and the installation code is dynamically generated or input by a user;

the target device receives a first confirmation value sent by the gateway, wherein the first confirmation value is calculated by the second platform cloud based on the installation code;

the target device verifies the first confirmation value based on the installation code.
The method of claim 21, wherein the first confirmation value is calculated by the second platform cloud based on an installation code and a first random number, wherein the first random number is generated by the second platform cloud.
The method of claim 22, wherein the method further comprises:

and the target device receives the first random number sent by the gateway, wherein the first random number and the installation code are used for verifying the first confirmation value by the target device.
The method of claim 23, wherein the target device checking the first confirmation value based on the installation code comprises:

the target device calculates a second check value based on the first random number and the installation code, and compares the second check value with the first confirmation value;

if the second check value is the same as the first confirmation value, the target device confirms that the first confirmation value is checked successfully;

and if the second check value is different from the first confirmation value, the target device confirms that the first confirmation value is failed to be checked.
The method of any of claims 21 to 24, wherein the second confirmation value is calculated by the target device based on the installation code and a second random number, the second random number being generated by the target device.
The method of claim 25, wherein the method further comprises:

and the target device sends the second random number to the gateway, the second random number is forwarded to the second platform cloud by the gateway through the first platform cloud, and the second random number and the installation code are used for verifying the second confirmation value by the second platform cloud.
The method of any of claims 21 to 26, wherein the installation code is output by the target device and the installation code is input by a user on the gateway.
The method of any of claims 21 to 26, wherein the installation code is output by the gateway and the installation code is input by a user on the target device.
A cross-platform equipment distribution network device applied to a gateway comprises:

the receiving unit is used for receiving a first confirmation value sent by a second platform cloud through a first platform cloud;

the sending unit is used for sending the first confirmation value to the target device for verification, wherein the first confirmation value is obtained by the second platform cloud through calculation based on an installation code, and the installation code is dynamically generated or input by a user;

the receiving unit is further configured to receive a second acknowledgement value sent by the target device;

the sending unit is further configured to send the second confirmation value to the second platform cloud through the first platform cloud for verification, where the second confirmation value is calculated by the target device based on the installation code.
The apparatus of claim 29, wherein the means for transmitting is further configured to transmit the installation code to the second Ping Taiyun via the first platform cloud, wherein the installation code is used for the second platform cloud to calculate the first acknowledgement value.
The apparatus of claim 29 or 30, wherein the first confirmation value is calculated by the second platform cloud based on an installation code and a first random number, wherein the first random number is generated by the second platform cloud.
The apparatus of claim 31, wherein,

the receiving unit is further configured to receive, through the first platform cloud, the first random number sent by the second platform cloud;

the sending unit is further configured to send the first random number to the target device, where the first random number and the installation code are used for the target device to check the first confirmation value.
The apparatus of any of claims 29 to 32, wherein the second confirmation value is calculated by the target device based on the installation code and a second random number, the second random number being generated by the target device.
The apparatus of claim 33, wherein,

the receiving unit is further configured to receive the second random number sent by the target device;

the sending unit is further configured to send the second random number to the second platform cloud through the first platform cloud, where the second random number and the installation code are used for the second platform cloud to verify the second confirmation value.
The apparatus of any one of claims 29 to 34,

the receiving unit is further configured to receive, by the first platform cloud, the device type information of the target device sent by the second platform cloud;

the sending unit is further configured to send an invitation message to the target device;

the receiving unit is further configured to receive a configuration capability message sent by the target device;

the sending unit is further configured to send a configuration start message to the target device;

at least one of the device type information, the invitation message and the configuration capability message carries first indication information, wherein the first indication information is used for indicating that an output OOB authentication mode and/or an input OOB authentication mode is preferentially adopted; the configuration start message carries second indication information, and the second indication information is used for indicating that an OOB authentication mode is determined to be adopted or an OOB authentication mode is input.
The apparatus of claim 35, wherein the apparatus further comprises:

a determining unit, configured to determine to adopt the OOB authentication manner or input the OOB authentication manner based on at least one of: the device type information of the target device, the first indication information carried in the device type information, and the first indication information carried in the configuration capability message.
The apparatus according to claim 35 or 36, wherein, in case of outputting the OOB authentication mode,

the installation code is output by the target device and the installation code is input by a user on the gateway.
The apparatus according to claim 35 or 36, wherein, in case of the input OOB authentication mode,

the installation code is output by the gateway and the installation code is input by a user on the target device.
The apparatus of any one of claims 29 to 38,

the receiving unit is further configured to receive, through the first platform cloud, an authentication result sent by the second platform cloud;

the sending unit is further configured to send configuration data to the target device.
A cross-platform equipment distribution network device applied to a second platform cloud, the device comprising:

a sending unit, configured to send a first confirmation value to a gateway through a first platform cloud, where the first confirmation value is forwarded by the gateway to a target device for verification, where the first confirmation value is calculated by the second platform cloud based on an installation code, and the installation code is dynamically generated or input by a user;

a receiving unit, configured to receive, by the first platform cloud, a second confirmation value sent by the gateway, where the second confirmation value is calculated by the target device based on the installation code;

and the checking unit is used for checking the second confirmation value based on the installation code.
The apparatus of claim 40, wherein the receiving unit is further configured to receive, by the first platform cloud, an installation code sent by the gateway, wherein the installation code is used for the second platform cloud to calculate the first acknowledgement value.
The apparatus of claim 40 or 41, wherein the first confirmation value is calculated by the second platform cloud based on an installation code and a first random number, wherein the first random number is generated by the second platform cloud.
The apparatus of claim 42, wherein the sending unit is further configured to send the first nonce to the gateway through the first platform cloud, the first nonce being forwarded by the gateway to the target device, wherein the first nonce and the installation code are used for the target device to check the first acknowledgement value.
The apparatus of any of claims 40 to 43, wherein the second confirmation value is calculated by the target device based on the installation code and a second random number, the second random number being generated by the target device.
The apparatus of claim 44, wherein the receiving unit is further configured to receive, by the first platform cloud, the second random number sent by the gateway, wherein the second random number and the installation code are used for the second platform cloud to check the second confirmation value.
The apparatus of claim 45, wherein the checking unit is configured to calculate a first check value based on the second random number and the installation code, and compare the first check value with the second confirmation value; if the first verification value is the same as the second confirmation value, the second confirmation value is verified successfully; and if the first verification value is different from the second verification value, confirming that the verification of the second verification value fails.
The apparatus of any one of claims 40 to 46, wherein the installation code is output by the target device and the installation code is input by a user on the gateway.
The apparatus of any one of claims 40 to 46, wherein the installation code is output by the gateway and the installation code is input by a user on the target device.
A cross-platform equipment distribution network device applied to a target equipment, the device comprising:

a sending unit, configured to send a second confirmation value to a gateway, where the second confirmation value is forwarded by the gateway to a second platform cloud through a first platform cloud for verification, where the second confirmation value is calculated by the target device based on an installation code, and the installation code is dynamically generated or input by a user;

a receiving unit, configured to receive a first confirmation value sent by the gateway, where the first confirmation value is obtained by the second platform cloud through calculation based on the installation code;

and the checking unit is used for checking the first confirmation value.
The apparatus of claim 49, wherein the first confirmation value is calculated by the second platform cloud based on an installation code and a first random number, wherein the first random number is generated by the second platform cloud.
The apparatus of claim 50, wherein the receiving unit is further configured to receive the first random number sent by the gateway, wherein the first random number and the installation code are used for the target device to check the first confirmation value.
The apparatus of claim 51, wherein the checking unit is configured to calculate a second check value based on the first random number and the installation code, and compare the second check value with the first confirmation value; if the second check value is the same as the first confirmation value, confirming that the first confirmation value is checked successfully; and if the second check value is different from the first confirmation value, confirming that the first confirmation value fails to be checked.
The apparatus of any of claims 49-52, wherein the second confirmation value is calculated by the target device based on the installation code and a second random number, the second random number being generated by the target device.
The apparatus of claim 53, wherein the sending unit is further configured to send the second nonce to the gateway, the second nonce being forwarded by the gateway to the second platform cloud through the first platform cloud, wherein the second nonce and the installation code are used for the second platform cloud to check the second confirmation value.
The apparatus of any one of claims 49-54, wherein the installation code is output by the target device and the installation code is input by a user on the gateway.
The apparatus of any one of claims 49-54, wherein the installation code is output by the gateway and the installation code is input by a user on the target device.
An electronic device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory, to perform the method of any of claims 1 to 11, or the method of any of claims 12 to 20, or the method of any of claims 21 to 28.
A storage medium storing a computer program for causing a computer to perform the method of any of claims 1 to 11, or the method of any of claims 12 to 20, or the method of any of claims 21 to 28.