Device binding method, apparatus, device, and storage medium

Abstract

The application discloses a device binding method and device, equipment and a storage medium, and the method comprises the following steps: receiving the device information of a smart device sent by a smart device service platform, wherein the device information is the device information sent by the smart device and received by the smart device service platform when the smart device is connected to a network; encrypting the device information to obtain a device identification code; searching for the device belonging user information corresponding to the device identification code from a block chain; and sending the device identification code to a client corresponding to the device belonging user information, so as to update the state of the smart device corresponding to the device identification code to a controllable state by the client, thereby completing the binding between the smart device and the client.

Description

Technical Field

[0001] This application belongs to the field of Internet of Things (IoT) technology, and in particular relates to a device binding method, apparatus, device, and storage medium. Background Technology

[0002] With the continuous development of IoT technology, people are increasingly using various network-connected smart devices in their lives. Generally, smart devices need to be bound to a corresponding client and associated with a user account before control commands can be issued to the smart devices through the client, and many functions of smart home devices can then be used.

[0003] Currently, the common method is for the user terminal to initiate a binding request to the platform based on the smart device's identity identifier to establish a binding relationship. Alternatively, the user terminal can scan for nearby smart devices, obtain their information, and then send a request to the platform to establish a binding relationship. Users often have to go through a complex binding process after purchasing a smart device, making the pre-use binding process overly cumbersome. Summary of the Invention

[0004] In view of one or more of the above problems, the present invention provides a device binding method, apparatus, device and storage medium that can simplify the device binding operation steps.

[0005] In a first aspect, embodiments of this application provide a device binding method, including:

[0006] Receive device information of smart devices sent by the smart device service platform. The device information is the device information sent by the smart device when the smart device is connected to the network.

[0007] The device information is encrypted to obtain the device identification code;

[0008] Retrieve the device ownership information corresponding to the device identification code from the blockchain;

[0009] Send a device identification code to the client corresponding to the user information to which the device belongs, so that the client can update the status of the smart device corresponding to the device identification code to a controllable state, thereby completing the binding between the smart device and the client.

[0010] In some possible implementations, the device information includes device identifier and device type information; the device information is encrypted to obtain a device identifier code, including:

[0011] The device identification code is obtained by encrypting the device identifier and device type information based on the preset public key.

[0012] In some possible implementations, before receiving the device information of the smart device sent by the smart device service platform, the method also includes:

[0013] receive the user registration information sent by the intelligent device service platform, the user registration information including device information of a user intelligent device;

[0014] establish a corresponding blockchain user account according to the user registration information, the blockchain user account saving the user registration information and being bound with the user registration information;

[0015] in the case that the device information of the intelligent device sent by the client is received, encrypt the device information of the user intelligent device to obtain a corresponding device identification code;

[0016] add the corresponding device identification code in the blockchain user account.

[0017] In some possible implementation manners, after the corresponding device identification code is added in the blockchain user account, the method further includes:

[0018] receive the device ownership change information sent by the client, the device ownership change information including a device identification code of a smart device to be bound;

[0019] change the device identification code in the corresponding blockchain user account according to the ownership change information.

[0020] In some possible implementation manners, the device ownership change information includes a client identification of the client; the changing of the device identification code in the corresponding blockchain user account according to the ownership change information includes:

[0021] obtain ownership record information sent by other multiple blocks in the blockchain;

[0022] verify the client sending the ownership change information based on the ownership record information;

[0023] in the case that the verification is passed, send an initialization instruction to the intelligent device service platform, the initialization instruction being used for clearing device data of a device corresponding to the ownership change information;

[0024] transfer the corresponding device identification code from the original blockchain user account to a new blockchain user account according to the ownership change information.

[0025] In some possible implementation manners, after the corresponding device identification code is added in the blockchain user account based on the user registration information, the method further includes:

[0026] obtain the device identification code corresponding to the blockchain user account;

[0027] send device information corresponding to the device identification code to the client corresponding to the blockchain user account, the device information being used for displaying device display information of a device corresponding to the blockchain user account.

[0028] In some possible implementation manners, the device information corresponding to the device identification code is sent to a client corresponding to the blockchain user account, including:

[0029] The device type information is obtained according to the device identification code of the device corresponding to the blockchain user account;

[0030] The device identification code and the device type information are sent to the client corresponding to the blockchain user account, and the device type information is used to query the device display information of the corresponding device from the intelligent device service platform.

[0031] In some possible implementation manners, before receiving the device information of the intelligent device sent by the intelligent device service platform, the method further includes:

[0032] The device purchase information sent by the client is received, and the device purchase information includes the device information of the intelligent device purchased by the user;

[0033] The device information is encrypted to obtain the device identification code;

[0034] The device identification code is added to the corresponding blockchain user account according to the device purchase information;

[0035] The device identification code is sent to the client.

[0036] In a second aspect, an embodiment of the present application provides a device binding apparatus, and the apparatus includes

[0037] The receiving module is configured to receive the device information of the intelligent device sent by the intelligent device service platform, and the device information is the device information of the intelligent device sent by the intelligent device and received by the intelligent device service platform in a networked condition;

[0038] The encryption module is configured to encrypt the device information to obtain the device identification code;

[0039] The searching module is configured to search for the device belonging user information corresponding to the device identification code from the blockchain;

[0040] The sending module is configured to send the device identification code to the client corresponding to the device belonging user information, so as to update the state of the intelligent device corresponding to the device identification code to the controllable state by the client, and complete the binding of the intelligent device and the client.

[0041] In a third aspect, an embodiment of the present application provides a device binding device, and the device includes a processor and a memory storing computer program instructions; the processor reads and executes the computer program instructions to realize the device binding method as described above.

[0042] In a fourth aspect, the embodiments of the present application provide a computer readable storage medium, and the computer storage medium stores computer program instructions, and the computer program instructions are executed by a processor to implement the device binding method as above.

[0043] The above scheme of the present application saves a unique identifier of each device on the blockchain, and the current ownership of the device is recorded in the blockchain. When the device identifier information is received, the device identifier code of the device in the blockchain is queried, the device ownership information corresponding to the device identifier code is found, the device identifier code is sent to the client corresponding to the device ownership information, and then the client can complete the binding of the device corresponding to the device identifier code according to the device identifier code. In this way, the user only needs to record the obtained digital smart device on the blockchain, and the corresponding device can be bound to the user account. The whole binding process does not need complicated operation. BRIEF DESCRIPTION OF DRAWINGS

[0044] The application can be better understood from the following description of specific embodiments thereof, given by way of example and with reference to the accompanying drawings, in which:

[0045] Other features, objects, and advantages of the application will become more apparent from the following detailed description of non-limiting embodiments thereof, read in conjunction with the accompanying drawings, in which like reference numerals identify like elements.

[0046] Figure 1 is a device binding method flow timing diagram provided by the present application;

[0047] Figure 2 is a device binding method flow timing diagram provided by the present application;

[0048] Figure 3 is a device binding method flow timing diagram provided by another embodiment of the present application;

[0049] Figure 4 is a device binding method flow timing diagram provided by the present application;

[0050] Figure 5 is a device binding method flow timing diagram provided by the present application;

[0051] Figure 6 is a device binding method flow timing diagram provided by the present application; DETAILED DESCRIPTION

[0052] Features and exemplary embodiments of various aspects of the present application will be described in detail below. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present application. However, it will be apparent to one of ordinary skill in the art that the present application can be practiced without some or all of these specific details. The description of the embodiments is merely intended to provide a more detailed understanding of the present application. The present application is in no way limited to any particular configuration and algorithm set forth below, but covers any modifications, equivalents, and alternatives falling within the spirit of the present application. In the drawings and the following description, well-known structures and techniques are not shown in order to avoid unnecessary obscurity of the present application.

[0053] It should be noted that, in this document, the terms such as first and second are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between such entities or operations. Also, the terms "comprises", "comprising", or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements, but can also include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without more limitations, the elements defined by the statement "comprise" do not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the elements.

[0054] Blockchain: a chain composed of one block after another. Each block contains certain information, and they are connected in order according to the time of their generation. This chain is saved in all servers, and as long as one server in the entire system can work, the entire blockchain is safe. These servers are called nodes in the blockchain system, and they provide storage space and computing power support for the entire blockchain system. If you want to modify the information in the blockchain, you must obtain the consent of more than half of the nodes and modify the information in all nodes, and these nodes are usually in the hands of different subjects, so it is extremely difficult to tamper with the information in the blockchain.

[0055] Under the background of the rapid development of Internet of Things technology, a variety of smart home devices that can be connected have entered thousands of households. Among them, there are smart cameras, sockets, sound boxes, and various medical and health class smart devices, etc. These smart devices are spread throughout all aspects of life.

[0056] In the application process of the intelligent device, the binding process of the device and the account is a very important link. After the intelligent device is bound to the corresponding client and user account, the client can issue control instructions to the intelligent device, or retrieve the application data of the intelligent device stored in the device itself or the cloud. The advantages of the intelligent device compared with the traditional device can be realized. For the intelligent device that can be connected to the network, the existing binding methods mainly have the following two kinds:

[0057] One is to obtain the intelligent device id through the mobile phone APP by scanning the two-dimensional code of the device end or using the manual input method, and then send a binding request to the platform end combined with the device type, device manufacturer and other information. The device id and other device details are added to the user account by the platform service end, and the binding relationship is established by this method.

[0058] Secondly, the mobile phone scans the intelligent device in the home through Bluetooth or in the same wireless network to obtain the id and other information broadcast by the device, and sends a request to the platform service end to establish a binding relationship.

[0059] For the current binding method, the device binding is often accompanied by various complex and time-consuming operations, which is not conducive to people's understanding, especially for the elderly users. In addition, when the device is transferred to another person for use, the original device binder needs to request to unbind the device on the platform end, and the new user needs to rebind the device, which causes the use process of the device to be too cumbersome. Moreover, the binding relationship between the user and the device is heavily dependent on the id information of the device. The media access control (MAC) address or international mobile equipment identity (IMEI) of the ordinary device, which can constitute the device id information, is often directly attached to the device machine. There is a risk of id exposure. At the same time, as an important identifier for controlling intelligent devices and retrieving device data, the binding relationship between the user and the id information is directly stored in the platform end, which is too centralized. The security of various private information generated by the user using the intelligent device is facing a huge test. According to the device id, the user's data such as video images generated by the home camera and various body index data collected by the health device can be quickly retrieved in the database. Once the key node or database of the platform end is attacked, the control authority of the user device and the key information stored in the database will face a serious risk of leakage.

[0060] The inventor found that the reason for the above problems is that after the user obtains the smart device, the smart device cannot obtain the information of the corresponding user to complete automatic binding, and can only rely on the user to manually select the smart device for binding. This is because there is no platform to record the direct correspondence between the smart device and the user, and the ownership information of the smart device will not be applied to the smart device binding process after the user purchases the smart device. Therefore, if a blockchain is introduced in the binding process, the ownership information of the smart device is recorded in the blockchain, and then the corresponding user can be automatically bound according to the ownership information. Moreover, the characteristics of the blockchain technology, such as openness, traceability, and tamper resistance, can effectively guarantee the authenticity, accuracy, and security of the binding relationship between the user and the device. At the same time, only the blockchain business platform can obtain the real id information of the device by decrypting the on-chain information of the device, and no one, including the bound user, can obtain the real identity address of the smart device. Specifically, the id of the smart device and other device identity information required for binding can be encrypted and uploaded to the blockchain platform as a digital smart device. The corresponding smart device can be obtained through purchase or transfer by others on the mobile app side, and the platform side adopts an automatic synchronization strategy to establish a binding relationship between the corresponding real smart device and the user, realizing the convenience of smart device binding and the concealment of device id information.

[0061] Specifically, the present scheme is applied to a smart device binding system, which refers to Figure 1 The system includes a user client or simply a client, a blockchain business platform, a smart device business platform, and a smart device end. The user client serves as the capability entrance of the blockchain business platform and the smart device business platform, and faces real users.

[0062] First, when the smart device is manufactured, the mac address or other identification information of the device access id, the type information (deviceType) recognizable by the smart device business platform, and the unique identification code of the device that can be uploaded to the blockchain are assembled together. The asymmetric encryption algorithm and the public key provided by the blockchain business platform are used to generate the unique identification code of the device that can be uploaded to the blockchain. This identification code represents the corresponding smart device in the blockchain.

[0063] And the deviceType that identifies the device type, the corresponding device name, picture identification, and device control instruction set, and other device key information are uploaded to the smart device business platform, so that the smart device business platform can control the smart device. The user client can distinguish different types of smart devices according to the deviceType.

[0064] After that, the digitized smart device is chained through the blockchain business platform, that is, added to the blockchain as the only channel for users to obtain the device and device information. The chained information can include real device appearance picture identification, detailed function description, and device chaining identification code.

[0065] On the user side, the user needs to use a user client, such as a smart device management APP, to control the smart device. First, the user needs to register on the smart device business platform through the user client. The smart device business platform will automatically synchronize the registration relationship to the blockchain business platform, and at the same time, open a blockchain platform account for the user by default and associate it with the corresponding smart device business platform account.

[0066] After the user obtains the smart device through purchase or collection on the blockchain business platform, the blockchain business platform adds the device chaining identification code information to the corresponding user's account for distributed storage. From now on, the user and the digitized smart device establish an association relationship, which is public and searchable on the blockchain platform. The ownership between the smart device and the user is recorded.

[0067] Then, the blockchain platform can push a digitized device association success message to the client, triggering the client user smart device list refresh. The user can also automatically refresh the list information of the digitized device associated with the account on the blockchain platform, including the device identification code and the device type information deviceType decrypted by the private key. After the client obtains the digitized device list, it queries the corresponding real device type, model, name, display icon, and other device list display information from the smart device business platform according to the device type deviceType information, and then completes the device list display in the smart device application client.

[0068] After the user gets the entity smart device, the smart device will try to automatically connect to the network when it is started. After the smart device successfully connects to the network, it will actively send a network binding request to the smart device business platform. The information sent can include the real mac address of the smart device, the device id, and other real device identity information. The smart device business platform will query the registration record of the corresponding id on the platform. If it confirms that it is a new device that has not been registered, it will complete the registration of the real device on the platform and issue a registration success identifier to the real device according to the pre-determined protocol, completing the registration of the real device on the smart device business platform.

[0069] The subsequent smart device directly interacts with the smart device service platform, and needs to push to the user client or issue client control instructions and obtain smart device data information, which are authenticated by the third-party blockchain service platform and transmitted between the client and the smart device service platform, so as to complete the binding of the user and the real smart device.

[0070] Through the above steps, when the user purchases the smart device through online shopping or the like on the blockchain service platform, the blockchain service platform can automatically bind the ownership between the smart device and the corresponding user. Subsequently, the smart device is automatically bound according to the ownership of the smart device. Similarly, when the smart device needs to change the binding relationship, the smart device can be bound to the account of another user by transferring the digital device information of the blockchain platform on the client. The specific process is as follows:

[0071] The original user initiates a digital device transfer request to the blockchain service platform on the client. After identity verification, the blockchain service platform transfers the distributed storage digital device to the corresponding user and forms a transfer record, and issues a device initialization instruction through the smart device service platform to clear the smart device data on the device end and the database storage. The new user obtains the device list through the blockchain service platform to complete the establishment of a new binding relationship.

[0072] Reference can be made to Figure 1 , Figure 1 is the device binding method flow timing diagram provided by the present application, as shown in Figure 1 When the smart device is manufactured, the related information of the smart device is uploaded to the blockchain service platform and the smart device service platform respectively, and the smart device is recorded on the blockchain by the blockchain service platform. After the user registers an account, the client of the user will automatically send the device identification code of the new device to the blockchain service platform every time the user purchases a new smart device, so that the blockchain platform synchronizes the ownership information of the device, thereby pre-recording the ownership information of the smart device in the blockchain and displaying it to the user. When the user obtains the above smart device and turns it on and connects it to the network, the smart device service platform sends the device identification of the connected smart device to the blockchain service platform for synchronization, and the blockchain service platform queries the blockchain according to the device identification to obtain the ownership user of the smart device. Then, the identification information of the online smart device is sent to the client corresponding to the user account of the user, and the client learns that the device has been connected to the network and can be controlled, and then the corresponding device state in the device list is refreshed to controllable, completing the binding. In this way, the smart device can be automatically bound to the user according to the ownership information of the smart device. Figure 1The interaction flow of the dotted line is the flow that the user needs to operate, and the interaction flow of the solid line is automatically performed by the platform according to the preset rules. It can be seen that, in the scheme, the user does not need to perform complicated operations to bind the intelligent device.

[0073] Figure 2 A flowchart of a device binding method provided by an embodiment of the application is shown. The device binding method provided by the embodiment of the application is applied to the blockchain business platform or a similar platform as described above. As shown in Figure 2 The method includes the following steps S201 to S204.

[0074] Step S201: receiving device information of an intelligent device sent by an intelligent device business platform, the device information being device information of the intelligent device sent by the intelligent device and received by the intelligent device business platform in a networked case.

[0075] The intelligent device business platform can be a comprehensive platform for managing various intelligent devices, realizing collection, transmission, storage and analysis of data. The intelligent device business platform can collect data obtained by the intelligent device and issue control instructions to the intelligent device.

[0076] The intelligent device can be a device with computing processing capability, capable of accessing a network and communicating and exchanging data with other devices or systems through the network. Correspondingly, the device information of the intelligent device is hardware information of the intelligent device, such as the MAC address of the intelligent device.

[0077] In a specific implementation, after the blockchain business platform and the intelligent device business platform establish a communication connection, the intelligent device business platform packages the collected intelligent device data into a preset specific format and sends the data to the blockchain business platform as a data packet. After the blockchain business platform receives the data packet, the device information of the intelligent device is obtained.

[0078] Step S202: encrypting the device information to obtain a device identification code.

[0079] The device identification code can be a unique code obtained by encrypting the device information using a key.

[0080] In a specific implementation, after the device information is obtained, a preset encryption algorithm and a key are used to encrypt the device information, and the encryption algorithm includes a symmetric encryption algorithm and an asymmetric encryption algorithm. After encryption, ciphertext is obtained, and the ciphertext can be directly used as the device identification code.

[0081] Step S203: searching for device belonging user information corresponding to the device identification code from the blockchain.

[0082] It should be noted that the correspondence between the device identification code and the user is stored in the blockchain, and the device ownership user information can be the user information of the user corresponding to the device identification code.

[0083] In a specific implementation, after obtaining the device identification code, the blockchain service platform can traverse the transaction records of the blockchain to obtain the user currently corresponding to the device identification code, and then obtain the user information of this user, i.e., the device ownership user information.

[0084] Step S204: Send the device identification code to the client corresponding to the device ownership user information, so as to update the state of the smart device corresponding to the device identification code to a controllable state in the client, thereby completing the binding of the smart device and the client.

[0085] When using the Internet of Things smart device, the user usually needs to issue an instruction to control the smart device. The client can be a smart device user client software used by the user to control the smart device.

[0086] It can be understood that the user and the device identification code of the smart device have a corresponding relationship before this time, but in this case, it is not yet determined whether the actual smart device has reached the user. Therefore, the user cannot control the smart device. The controllable state can mean that the user can control the corresponding smart device on the client.

[0087] In a specific implementation, when the blockchain service platform finds the device ownership user information corresponding to the device identification code, the device identification code is sent to the client corresponding to the user information. This can be achieved by building an interface on the blockchain service platform and passing the device identification code to the client application as data. After receiving the device identification code, the client can verify its validity. This can be achieved by comparing the received device identification code with the device identification code already stored in the client, or by querying the blockchain to verify the authenticity and uniqueness of the device identification code. If the verification is successful, the client can send a control instruction to the smart device for testing. After the test is completed, the state of the smart device is updated to a controllable state, and at this time it can be considered that the smart device and the client have been successfully bound. After binding, the client can control and operate the smart device, and according to the different smart devices, operations such as adjusting the temperature, turning on or off the light, controlling the home appliances, etc. can be performed.

[0088] Embodiments of the present application record a unique identifier of each device on the blockchain, and the current ownership of the device is also recorded on the blockchain. When the device identifier information is received, the device identifier code of the device in the blockchain is queried, the device ownership information corresponding to the device identifier code is found, the device identifier code is sent to the client corresponding to the device ownership information, and then the client can complete the binding of the device corresponding to the device identifier code according to the device identifier code. In this way, the user only needs to record the obtained digital smart device on the blockchain, and the corresponding device can be bound to the user account. The entire binding process does not require complicated operations.

[0089] In some embodiments, the device information includes device identifier and device type information; and the device identifier code is obtained by encrypting the device information, including:

[0090] The device identifier code is obtained by encrypting the device identifier and the device type information based on a preset public key.

[0091] The device type information can be identifier information representing a certain type of device, such as the type and model of the device.

[0092] In a specific implementation, the identifier and type information of the device are first obtained from the smart device business platform. The obtained device identifier and device type information are encrypted using a preset public key and encryption algorithm to obtain the encrypted device identifier code. The encryption process can be performed by the smart device business platform or a dedicated encryption module. To avoid tampering with the device identifier code, the encryption result can be verified after encryption. The verification can be performed by decrypting the result using a preset private key, and comparing the decrypted device identifier and device type information with the original device information to ensure that the encryption process has not been tampered with or has not been tampered with.

[0093] The above embodiments of the present application encrypt the device according to the hardware information of the device and add the device to the blockchain. The security of the device information is improved. Moreover, the device type information is included in the encrypted information, which facilitates the smart device business platform to obtain detailed information of the device according to the device type information.

[0094] In some embodiments, with reference to Figure 3 Before receiving the device information of the smart device sent by the smart device business platform, the method can further include steps S301 to S304.

[0095] Step S301: receiving user registration information sent by the smart device business platform, the user registration information including device information of the user's smart device.

[0096] The user registration information can be information collected and created during the user registration process, which is used to identify and verify the user identity and is associated with the user's activities in the Internet of Things platform or system. It can generally include user identity information for identifying the user identity, user authentication information for verifying the user identity, and user device information indicating the user-owned device, etc.

[0097] In a specific implementation, the user inputs the user registration information through the registration interface provided by the intelligent device business platform and submits it to the intelligent device business platform. At the same time, the intelligent device business platform also establishes a communication connection with the user device for receiving the user registration information. After receiving the user registration information of the intelligent device business platform and completing the user registration, part of the user registration information of the intelligent device business platform and the device information of the user intelligent device are sent to the blockchain business platform in the form of a data packet, and the blockchain business platform obtains the user registration information after receiving the data packet.

[0098] Step S302: Establishing a corresponding blockchain user account according to the user registration information, and the blockchain user account saves the user registration information and is bound with the user registration information.

[0099] In the blockchain, the user account is usually referred to as a public key / private key pair. This is because in the blockchain, the security and trust mechanism mainly relies on the asymmetric encryption algorithm, in which the public key can be public, while the private key is kept secret by the user and cannot be public. Therefore, the blockchain user account can be a public key / private key pair, in which the public key is the address of the account, used for publicizing and verifying transactions; and the private key is the identity of the user, used for signing and ensuring the security of transactions.

[0100] In a specific implementation, after obtaining the registration information, the information needs to be verified. Mainly check the integrity and legality of the information, such as checking whether the information filled in by the user meets the specifications, whether necessary information is omitted, etc. Then a public key / private key pair is formed for the user's account. The public key and the private key are generated by the asymmetric encryption algorithm according to certain rules and stored in the database.

[0101] Step S303: In the case where the device information of the intelligent device sent by the client is received, the device information of the user intelligent device is encrypted to obtain a corresponding device identification code.

[0102] In a specific implementation, after the user registration of the blockchain user account is completed, the user can record the owned intelligent device in the blockchain at this time. For example, the user purchases a new intelligent device on the network platform, and the user's client can send the device information of the purchased device to the blockchain business platform, and the blockchain business platform performs device information encryption to obtain the corresponding device identification code of the purchased device.

[0103] Step S304: Adding the corresponding device identification code in the blockchain user account.

[0104] In a specific implementation, the user account information corresponding to the device identification code can be obtained from the smart device service platform. This can be achieved by querying the database or distributed ledger to associate the user account information with the device identification code. After obtaining the user account information, the device identification code can be added to the user account information. This can be achieved by updating the records in the database or distributed ledger to associate the device identification code with the user account information. After adding the device identification code, the updated user account information needs to be submitted to the blockchain network. This can be achieved by the blockchain service platform packaging the updated records into transactions and broadcasting them to all nodes in the blockchain network for storage.

[0105] The above embodiments of the present application receive user registration information sent by the smart device service platform, the user registration information including device information of the user's smart device; establish a corresponding blockchain user account according to the user registration information, the blockchain user account saving the user registration information and being bound with the user registration information; in the case of receiving device information of the smart device sent by the client, encrypt the device information of the user's smart device to obtain a corresponding device identification code; and add the corresponding device identification code in the blockchain user account. This makes the user register the blockchain user account at the same time of registering in the device service platform, and automatically binds the user and the smart device on the blockchain, facilitating the user's use.

[0106] In some embodiments, after adding the corresponding device identification code in the blockchain user account, the method further comprises:

[0107] Receiving device ownership change information sent by the client, the device ownership change information including the device identification code of the smart device to be bound.

[0108] The device ownership change information can be information recording the change of device ownership. Specifically, when the smart device is transferred from one user to another, or when the ownership of the device changes, the relevant change information will be recorded on the blockchain. These information usually include the identification code of the device, the information of the owner, the timestamp of the change, etc. These information are publicly available on the blockchain, which can effectively prevent disputes and illegal tampering of device ownership.

[0109] In a specific implementation, when the ownership of the smart device changes, such as when the smart device is given to another person for use, the user can broadcast the specific information of this change through the client in the blockchain network, so that the blockchain service platform receives the device ownership change information.

[0110] According to the change of the ownership information, the device identification code in the corresponding blockchain user account is changed.

[0111] In a specific implementation, after receiving the device ownership change information, the blockchain service platform needs to verify and process it. This includes verifying the validity of the information, confirming the change of the ownership of the device, etc. After confirming that the device ownership change information is valid, the original device identification code is usually deleted from the user account, and the new device identification code is added to the user account.

[0112] The above embodiments of the present application receive device ownership change information sent by a client, the device ownership change information including a device identification code of a smart device to be bound; and according to the change of the ownership information, the device identification code in the corresponding blockchain user account is changed. The transfer of the device binding relationship does not require unbinding and rebinding, and only the digital device transfer in the blockchain service platform can change the binding relationship, relying on the traceable and public characteristics of the blockchain technology to ensure the security of the binding relationship.

[0113] In some embodiments, the device ownership change information includes a client identification of the client; and according to the change of the ownership information, the device identification code in the corresponding blockchain user account is changed, including:

[0114] Obtaining ownership record information sent by other nodes in the blockchain.

[0115] The ownership record information can be transaction records and timestamps corresponding to the device identification code.

[0116] In a specific implementation, the device identification code corresponding information is requested from other nodes in the blockchain network, and the ownership record information sent by the other nodes is received.

[0117] Based on the ownership record information, the client sending the ownership change information is verified.

[0118] In a specific implementation, after receiving the ownership record information sent by the other nodes, it needs to be parsed and processed. This includes extracting useful data and information therein, such as the identification code of the device, the information of the owner, etc., for the subsequent verification process. After obtaining the ownership record information, it can be compared and verified with the ownership change information. This can be achieved by comparing the device identification code in the ownership change information with the device identification code in the ownership record information, or by querying the authenticity and uniqueness of the device identification code from the blockchain network through the smart device service platform. If the ownership change information matches the ownership record information, it can be considered that the client is legitimate and authorized. Otherwise, the client can be a malicious node or an unauthorized user. In this case, the blockchain service platform can take appropriate measures, such as rejecting the request of the client or listing it in the blacklist.

[0119] In the case of passing the verification, an initialization instruction is sent to the intelligent device business platform, and the initialization instruction is used to clear the device data of the device corresponding to the change of ownership information.

[0120] The initialization instruction can be a related instruction for clearing the settings and information saved by the intelligent device.

[0121] In specific implementation, after confirming that the verification passes, an initialization instruction can be generated according to the preset rules and logic, and the generated initialization instruction is sent to the intelligent device business platform. After receiving the initialization instruction, the intelligent device business platform parses the instruction and clears the device data corresponding to the change of ownership information according to the indication in the instruction. This can include deleting device data, resetting device state, and the like.

[0122] According to the change of ownership information, the corresponding device identification code is transferred from the original blockchain user account to the new blockchain user account.

[0123] In specific implementation, by querying the database or distributed ledger of the blockchain business platform, the related information of the original blockchain user account and the new blockchain user account can be obtained, including the identity of the user and the device identification code, and the like. The device identification code in the original user account is exchanged or transferred with the device identification code in the new blockchain user account. This can be achieved by deleting the device identification code from one account and adding it to another account through the intelligent device business platform. After completing the transfer of the device identification code, the updated user account information needs to be submitted to the blockchain network. This can be achieved by packaging the updated record into a transaction through the intelligent device business platform and broadcasting it to all nodes in the blockchain network for storage.

[0124] The above embodiments of the present application obtain the ownership record information sent by other multiple blocks in the blockchain; verify the client sending the change of ownership information based on the ownership record information; in the case of passing the verification, an initialization instruction is sent to the intelligent device business platform, and the initialization instruction is used to clear the device data of the device corresponding to the change of ownership information; and according to the change of ownership information, the corresponding device identification code is transferred from the original blockchain user account to the new blockchain user account. When the ownership of the intelligent device changes, identity authentication is performed, the data of the changed device is cleared, and the device change process is more secure.

[0125] In some embodiments, after adding the corresponding device identification code in the blockchain user account based on the user registration information, the method further comprises:

[0126] Obtaining the device identification code corresponding to the blockchain user account.

[0127] In a specific implementation, the device identification code corresponding to the user account can be queried from a database or a distributed ledger of the blockchain service platform.

[0128] The device information corresponding to the device identification code is sent to the client corresponding to the blockchain user account, and the device information is used to display the device display information of the device corresponding to the blockchain user account.

[0129] The device display information can be a picture, a model, and related parameters of the smart device, and other information related to the smart device that the user needs to know.

[0130] The device information can include device type information and device identification code.

[0131] In a specific implementation, the blockchain service platform sends the device information corresponding to the device identification code to the client corresponding to the blockchain user account, so that the client queries the smart device service platform through the device information to obtain the device display information.

[0132] The above embodiments of the present application obtain the device identification code corresponding to the blockchain user account, and send the device information corresponding to the device identification code to the client corresponding to the blockchain user account, and the device information is used to display the device display information of the device corresponding to the blockchain user account. The client of the user displays detailed device information, which is convenient for the user to search and use.

[0133] In some embodiments, sending the device information corresponding to the device identification code to the client corresponding to the blockchain user account comprises:

[0134] The device type information is obtained according to the device identification code of the device corresponding to the blockchain user account.

[0135] In a specific implementation, the device identification code of the device corresponding to the blockchain user account is obtained, the user account information is associated with the device identification code, and then the device identification code is extracted. Once the device identification code is obtained, the device type information corresponding to the device identification code can be queried through the blockchain service platform. This can be achieved by querying a database or a distributed ledger, or by querying the blockchain network.

[0136] The device identification code and the device type information are sent to the client corresponding to the blockchain user account, and the device type information is used to query the smart device service platform to obtain the device display information of the corresponding device.

[0137] The above-mentioned embodiments of the present application obtain the device type information according to the device identification code of the device corresponding to the user account of the blockchain; send the device identification code and the device type information to the client corresponding to the user account of the blockchain, and the device type information is used to query the device display information of the corresponding device from the intelligent device service platform. The device identification code is stored in the blockchain platform, and the device display information is stored in the device service platform. The binding relationship between the device and the user account is no longer strongly associated, so that the information security of the user can be guaranteed.

[0138] Based on the device binding method provided in the above embodiments, the present application also provides a specific implementation of a device binding apparatus. Please refer to the following embodiments.

[0139] As shown in Figure 4 , for example, when a user registers on a client, the user will simultaneously register on an intelligent service platform and a blockchain service platform. Then, the user can send the device information of the intelligent device already owned by the user to the blockchain service platform through the client, so that the blockchain service platform adds these intelligent devices to the blockchain and adds them to the above-mentioned user account.

[0140] Moreover, when the ownership of the device changes, for example, in the case of a second-hand transaction or a gift of the intelligent device, the receiving device receives the ownership change information, verifies the ownership change information in the blockchain, and changes the ownership of the intelligent device if the verification is passed.

[0141] When the user needs to view all the intelligent devices of the user account, the user can obtain the device type information of the intelligent device from the blockchain service platform through the client, and obtain the device display information from the intelligent device service platform through the device type information, so that the user can view the detailed information of all the intelligent devices of the user account.

[0142] After the user purchases a new intelligent device, the ownership relationship between the intelligent device and the user account is recorded on the blockchain when the purchase is made, but at this time, it does not mean that the user can use and control the intelligent device. Therefore, when the user actually starts to use the intelligent device, the intelligent device sends its own device information to the intelligent device service platform, the intelligent device service platform forwards the device information to the blockchain service platform, and the blockchain service platform sends the device identification code corresponding to the above-mentioned device to the corresponding client according to the ownership relationship between the intelligent device and the user account, so that the user can actually control the above-mentioned intelligent device, thereby completing the binding of the device.

[0143] Firstly, referring to Figure 5 , the device binding apparatus 500 provided by the embodiments of the present application comprises the following modules:

[0144] The receiving module 501 is configured to receive device information of the smart device sent by the smart device service platform, the device information being device information of the smart device sent by the smart device service platform and received by the smart device service platform in a networked manner.

[0145] The encryption module 502 is configured to encrypt the device information to obtain a device identification code.

[0146] The searching module 503 is configured to search for device ownership user information corresponding to the device identification code from the blockchain.

[0147] The sending module 504 is configured to send the device identification code to a client corresponding to the device ownership user information, so as to update a state of the smart device corresponding to the device identification code to a controllable state by the client, thereby completing binding of the smart device and the client.

[0148] The above scheme of the present application enables each device to save a unique identification on the blockchain, and the current ownership right of the device is recorded in the blockchain. When receiving the device identification information, the device identification code of the device in the blockchain is queried, the device ownership information corresponding to the device identification code is searched, and the device identification code is sent to the client corresponding to the device ownership information. Then, the client can complete binding of the device corresponding to the device identification code according to the device identification code. In this way, the user only needs to record the obtained digital smart device on the blockchain, and the corresponding device can be bound to the user account, and the entire binding process does not need complicated operations.

[0149] As an implementation manner of the present application, the encryption module 502 is further configured to encrypt the device identification and the device type information based on a preset public key to obtain the device identification code.

[0150] The above implementation manner of the present application encrypts the device according to the hardware information of the device, and adds the device to the blockchain. The security of the device information is improved.

[0151] As an implementation manner of the present application, the receiving module 501 is further configured to receive user registration information sent by the smart device service platform, the user registration information including device information of a user smart device; the encryption module 502 is further configured to encrypt the device information of the user smart device to obtain a corresponding device identification code in a case where the device information of the smart device sent by the client is received; in this implementation manner, the device binding apparatus 500 can further include:

[0152] The establishing module is further configured to establish a corresponding blockchain user account according to the user registration information, the blockchain user account saving the user registration information and being bound to the user registration information.

[0153] The adding module is configured to add the corresponding device identification code in the blockchain user account.

[0154] The above implementation of the application allows a user to register a blockchain user account while registering on a device service platform, and automatically binds the user and a smart device on the blockchain, thereby facilitating the use of the user.

[0155] As an implementation of the application, the receiving module 501 is further configured to receive device home change information sent by the client, the device home change information comprising a device identification code of a smart device to be bound; in this implementation, the device binding apparatus 500 can further comprise:

[0156] a changing module configured to change the device identification code in the corresponding blockchain user account according to the home change information.

[0157] The above implementation of the application allows the device binding relationship to be transferred without the need for unbinding and rebinding, and only the digital device transfer on the blockchain service platform can change the binding relationship, and the security of the binding relationship is ensured by relying on the traceable and public characteristics of the blockchain technology.

[0158] As an implementation of the application, the sending module 504 is further configured to send an initialization instruction to the smart device service platform if the verification is passed, the initialization instruction being used to clear the device data of the device corresponding to the home change information; in this implementation, the device binding apparatus 500 can further comprise:

[0159] an obtaining module configured to obtain home record information sent by other multiple blocks in the blockchain;

[0160] a verification module configured to verify the client sending the home change information based on the home record information;

[0161] a transferring module configured to transfer the corresponding device identification code from the original blockchain user account to a new blockchain user account according to the home change information.

[0162] The above implementation of the application allows the identity to be verified and the data of the changed device to be cleared, thereby making the device changing process more secure.

[0163] As an implementation of the application, the obtaining module is further configured to obtain the device identification code corresponding to the blockchain user account; and the sending module 504 is further configured to send device information corresponding to the device identification code to the client corresponding to the blockchain user account, the device information being used to display device display information of the device corresponding to the blockchain user account.

[0164] The above implementation of the application allows the client of the user to display detailed device information, thereby facilitating the searching and use of the user.

[0165] As an implementation form of the present application, the sending module 504 is further configured to send the device identification code and the device type information to a client corresponding to the blockchain user account, and the device type information is used to query the device display information of the corresponding device from the intelligent device service platform. In this implementation form, the device binding apparatus 500 can further include:

[0166] a processing module configured to obtain the device type information according to the device identification code of the device corresponding to the blockchain user account;

[0167] The above implementation form of the present application stores the device identification code in the blockchain platform and stores the device display information in the device service platform, so that the binding relationship between the device and the user account is no longer strongly associated, and the information security of the user can be ensured.

[0168] Figure 6 A hardware structure diagram of a device binding device provided by an embodiment of the present application is shown.

[0169] The data processing device can include a processor 601 and a memory 602 having computer program instructions stored therein.

[0170] Specifically, the processor 601 can include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or can be configured to implement one or more integrated circuits of the embodiments of the present application.

[0171] The memory 602 can include a mass storage for data or instructions. By way of example and not limitation, the memory 602 can include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. Where appropriate, the memory 602 can include removable or non-removable (or fixed) media. Where appropriate, the memory 602 can be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, the memory 602 is a non-volatile solid-state memory.

[0172] The memory can include read-only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical or other physical / tangible memory storage devices. Thus, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software that, when executed (e.g., by one or more processors), is operable to perform the operations described with reference to the data processing method according to any one of the embodiments of the present disclosure.

[0173] The processor 601 implements any one of the data processing methods in the above-described embodiments by reading and executing computer program instructions stored in the memory 602.

[0174] In one example, the data processing device can further include a communication interface 603 and a bus 610. As shown, the processor 601, the memory 602, and the communication interface 603 are connected through the bus 610 and complete communication therebetween. Figure 6

[0175] The communication interface 603 is mainly used to realize the communication between the modules, devices, units and / or equipment in the embodiments of the present application.

[0176] The bus 610 includes hardware, software or both to couple the components of the online data traffic billing device to each other. By way of example, and not limitation, the bus can include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand (IB) interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, or another suitable bus or combination of two or more of these. Where suitable, the bus 610 can include one or more buses. Although specific buses are described and illustrated in the embodiments of the present application, the present application contemplates any suitable bus or interconnect.

[0177] In addition, in combination with the data processing method in the above-described embodiments, the embodiments of the present application can provide a computer storage medium to implement. The computer storage medium has computer program instructions stored thereon; the computer program instructions are executed by the processor to implement any one of the device binding methods in the above-described embodiments.

[0178] ​However, it is to be understood that the application is not limited to the particular configurations and processes described and illustrated herein. Also, for simplicity and clarity of illustration, detailed descriptions of well-known methods techniques and procedures are omitted. In the above embodiments, several specific steps are described and illustrated as examples. However, the method processes of the present application are not limited to the specific steps described and illustrated, and one skilled in the art can make various changes, modifications and additions thereto, or can perform the steps in a different order, without departing from the spirit of the present application.

[0179] The functional blocks shown in the above described block diagrams can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of the present application are program or code segments that are used to perform the required tasks. The program or code segments can be stored in a machine readable medium or transmitted through a data signal carried in a carrier wave over a transmission medium or communication link. A "machine readable medium" includes any medium that can store or transfer information. Examples of machine readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. The code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0180] The present application can be embodied in other specific forms without departing from the spirit or essential characteristics thereof. For example, the algorithms described in the specific embodiments can be modified without departing from the essential spirit of the system architecture. Therefore, the present embodiments are to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the description presented above, and all changes which come within the meaning and range of equivalency of the claims are intended to be embraced therein.

[0181] It will be appreciated by persons skilled in the art that the present application is not limited to what has been described above and illustrated in the drawings. Different configurations and processes can be made without departing from the spirit and scope of the application. The above embodiments are merely exemplary and not limiting. Different features of different embodiments can be combined to achieve yet further embodiments. Other variations and modifications of the embodiments disclosed can become apparent to those of ordinary skill in the art upon reading the foregoing description. The scope of the application includes all such variations and modifications. The terms "comprise", "comprising", "comprises" and "comprising" when used in this document specify the presence of stated features but do not preclude the presence or addition of one or more other features. The indefinite article "a" or "an" does not exclude the presence of zero or more than one of the mentioned item. The term "first", "second", "third" etc. do not require a specific order but are used for naming purposes only. Any reference signs in the claims should not be construed as limiting the scope of the claims. The functionality of a plurality of means can be implemented by a single hardware or software module. The fact that different features are presented in different dependent claims does not mean that these features cannot be combined in order to receive the advantages of the different features.

Claims

1. A device binding method, characterized in that, The method includes: The system receives device information of a smart device sent by a smart device service platform. The device information is the device information sent by the smart device when the smart device is connected to the network. The device information is encrypted to obtain a device identification code; Retrieve the device ownership information corresponding to the device identifier from the blockchain; The device identification code is sent to the client corresponding to the user information to which the device belongs, so that the client can update the status of the smart device corresponding to the device identification code to a controllable state, thereby completing the binding between the smart device and the client.

2. The device binding method according to claim 1, characterized in that, The device information includes device identifier and device type information; the encryption of the device information to obtain the device identifier code includes: The device identifier code is obtained by encrypting the device identifier and the device type information based on a preset public key.

3. The device binding method according to claim 1, characterized in that, Before receiving the device information of the smart device sent by the smart device service platform, the method further includes: Receive user registration information sent by the smart device service platform, wherein the user registration information includes device information of the user's smart device; A corresponding blockchain user account is established based on the user registration information. The blockchain user account stores the user registration information and is bound to the user registration information. Upon receiving device information of a smart device sent by the client, the device information of the user's smart device is encrypted to obtain the corresponding device identification code; Add the corresponding device identifier code to the blockchain user account.

4. The device binding method according to claim 3, characterized in that, After adding the corresponding device identifier to the blockchain user account, the method further includes: Receive device ownership change information sent by the client, wherein the device ownership change information includes the device identifier code of the smart device to be bound; The device identifier code in the corresponding blockchain user account is changed according to the ownership change information.

5. The device binding method according to claim 4, characterized in that, The device ownership change information includes the client's client identifier; the step of changing the device identifier code in the corresponding blockchain user account according to the ownership change information includes: Obtain attribution record information sent by multiple other nodes in the blockchain; The client that sent the ownership change information is verified based on the ownership record information. If the verification passes, an initialization command is sent to the smart device service platform. The initialization command is used to clear the device data of the device corresponding to the ownership change information. Based on the ownership change information, the corresponding device identification code will be transferred from the original blockchain user account to the new blockchain user account.

6. The device binding method according to claim 3, characterized in that, After adding the corresponding device identifier code to the blockchain user account based on the user registration information, the method further includes: Obtain the device identifier code corresponding to the blockchain user account; The device information corresponding to the device identifier is sent to the client corresponding to the blockchain user account. The device information is used to display the device display information of the device corresponding to the blockchain user account.

7. The device binding method according to claim 6, characterized in that, Sending the device information corresponding to the device identifier code to the client corresponding to the blockchain user account includes: The device type information is obtained based on the device identifier code of the device corresponding to the blockchain user account; The device identifier and device type information are sent to the client corresponding to the blockchain user account. The device type information is used to query the smart device business platform to obtain the device display information of the corresponding device.

8. A device binding device, characterized in that, The device includes: A receiving module is used to receive device information of a smart device sent by a smart device service platform. The device information is the device information sent by the smart device and received by the smart device service platform when the smart device is connected to the network. An encryption module is used to encrypt the device information to obtain a device identification code; The search module is used to search the blockchain for the device owner information corresponding to the device identification code; The sending module is used to send the device identification code to the client corresponding to the user information to which the device belongs, so that the client can update the status of the smart device corresponding to the device identification code to a controllable state, thereby completing the binding between the smart device and the client.

9. A device-to-device pairing system, characterized in that, The device includes: a processor and a memory storing computer program instructions; the processor reads and executes the computer program instructions to implement the device binding method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the device bonding method as described in any one of claims 1-7.

Images