Equipment binding method and device, equipment and storage medium

Abstract

The invention discloses a device binding method and apparatus, a device and a storage medium, the method comprising: receiving device information of an intelligent device sent by an intelligent device service platform, the device information being the device information sent by the intelligent device and received by the intelligent device service platform when the intelligent device is networked; encrypting the equipment information to obtain an equipment identification code; searching equipment affiliation user information corresponding to the equipment identification code from a block chain; and sending the equipment identification code to a client corresponding to the equipment affiliation user information, so that the client updates the state of the intelligent equipment corresponding to the equipment identification code to be a controllable state to complete binding of the intelligent equipment and the client.

Description

Technical Field

[0001] The present application belongs to the technical field of Internet of Things, and in particular, relates to a device binding method, apparatus, device and storage medium. Background Art

[0002] With the continuous development of Internet of Things technology, people are increasingly using various smart devices that can be connected to the Internet in their lives. Generally speaking, it is necessary to bind the smart device to the corresponding client and associate it with the user account before the client can issue control instructions to the smart device, and many functions of smart home devices can be used.

[0003] At present, the user terminal generally initiates a binding request to the platform side according to the identity of the smart device to establish a binding relationship. Or the user terminal scans nearby smart devices, obtains the device information, and then sends a request to the platform side to establish a binding relationship. Users often need to go through a complicated binding process after purchasing a smart device, and the binding process before the device is used is too 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, which can simplify the operation steps of device binding.

[0005] In a first aspect, an embodiment of the present application provides 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 and received by the smart device service platform when the smart device is connected to the Internet;

[0007] Encrypting the device information to obtain a device identification code;

[0008] Search the blockchain for device ownership information corresponding to the device identification code;

[0009] The device identification code is sent to the client corresponding to the device-attributed user information, so that the client updates the state of the smart device corresponding to the device identification code to a controllable state, thereby completing the binding of the smart device and the client.

[0010] In some possible implementations, the device information includes a device identification and device type information; encrypting the device information to obtain a device identification code includes:

[0011] The device identification and device type information are encrypted based on a preset public key to obtain a device identification code.

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

[0013] Receive user registration information sent by the smart device service platform, where the user registration information includes device information of the user's smart device;

[0014] A corresponding blockchain user account is established according to the user registration information. The blockchain user account stores the user registration information and is bound to the user registration information.

[0015] When receiving the 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;

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

[0017] In some possible implementations, after adding the corresponding device identification code to the blockchain user account, the method further includes:

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

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

[0020] In some possible implementations, the device ownership change information includes a client identifier of the client; and changing the device identifier in the corresponding blockchain user account according to the ownership change information includes:

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

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

[0023] If the verification is passed, an initialization instruction is sent to the smart device service platform. The initialization instruction is used to clear the device data of the device corresponding to the ownership change information;

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

[0025] In some possible implementations, after adding the corresponding device identification code to the blockchain user account based on the user registration information, the method further includes:

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

[0027] The device information corresponding to the device identification code 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.

[0028] In some possible implementations, sending device information corresponding to the device identification code to the client corresponding to the blockchain user account includes:

[0029] Obtain device type information based on the device identification code of the device corresponding to the blockchain user account;

[0030] The device identification code 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.

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

[0032] Receive device purchase information sent by the client, where the device purchase information includes device information of the smart device purchased by the user;

[0033] Encrypting the device information to obtain a device identification code;

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

[0035] Send the device identification code to the client.

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

[0037] A receiving module, used to receive device information of smart devices sent by the smart device service platform, where the device information is device information sent by the smart device and received by the smart device service platform when the smart device is connected to the Internet;

[0038] An encryption module, used to encrypt device information to obtain a device identification code;

[0039] A search module, used to search the device ownership user information corresponding to the device identification code from the blockchain;

[0040] The sending module is used to send the device identification code to the client corresponding to the device belonging user information, so that the client can update the state of the smart device corresponding to the device identification code to a controllable state to complete the binding of the smart device and the client.

[0041] In a third aspect, an embodiment of the present application provides a device binding device, the device comprising: 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 above.

[0042] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the device binding method as described above is implemented.

[0043] The above scheme of the present application allows each device to save a unique identifier on the blockchain, and the current ownership of the device will be recorded in the blockchain. In this way, when the device identification information is received, the device identification code of the device in the blockchain is queried, and the device ownership information corresponding to the device identification code is found, and the device identification code is sent to the client corresponding to the device ownership information. Then the client can complete the 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 acquired digital smart device on the blockchain, and the corresponding device can be bound to the user account, and the entire binding process does not require cumbersome operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The present invention can be better understood from the following description of specific embodiments of the present invention in conjunction with the accompanying drawings, in which:

[0045] Other features, objects and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings, in which the same or similar reference numerals represent the same or similar features.

[0046] Figure 1 It is a timing diagram of the device binding method process provided by this application;

[0047] Figure 2 This is a schematic diagram of a device binding method flow chart provided by an embodiment of the present application;

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

[0049] Figure 4 It is a schematic diagram of the overall device binding method flow provided by an embodiment of the present application;

[0050] Figure 5 It is a structural diagram of a device binding apparatus provided by an embodiment of the present application;

[0051] Figure 6 It is a schematic diagram of the hardware structure of the device binding device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0052] The features and exemplary embodiments of various aspects of the present invention will be described in detail below. In the detailed description below, many specific details are proposed to provide a comprehensive understanding of the present invention. However, it is obvious to those skilled in the art that the present invention can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present invention by illustrating examples of the present invention. The present invention is by no means limited to any specific configuration and algorithm proposed below, but covers any modification, replacement and improvement of elements, parts and algorithms without departing from the spirit of the present invention. In the accompanying drawings and the following description, known structures and technologies are not shown to avoid unnecessary ambiguity to the present invention.

[0053] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "include..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0054] Blockchain: It is a chain of blocks. Each block stores certain information, and they are connected into a chain in the order of their generation. This chain is stored in all servers. As long as there is one server in the entire system that 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. These nodes are usually in the hands of different entities, so it is extremely difficult to tamper with the information in the blockchain.

[0055] With the rapid development of the Internet of Things technology, a wide variety of smart homes that can be connected to the Internet have entered thousands of households, including smart cameras, sockets, speakers, and various medical and health smart devices, which are used in all aspects of life.

[0056] In the application process of smart devices, the binding process of devices and accounts is a very important link. Only after the smart device is bound to the corresponding client and user account, can the client issue control instructions to the smart device, or retrieve the smart device application data stored on the device itself or in the cloud. Only then can the advantages of smart devices over traditional devices be reflected. For smart devices that can be connected to the Internet, there are mainly two existing binding methods:

[0057] One is to obtain the smart device ID through the mobile APP by scanning the QR code on the device or manually entering it, and then initiate a binding request to the platform based on the device type, device manufacturer and other information. The platform server adds the device ID and other device details to the user account to establish a binding relationship.

[0058] Secondly, the mobile phone scans the smart devices in the home through Bluetooth or on the same wireless network, obtains the ID and other information broadcast by the device, and also sends a request to the platform server to establish a binding relationship.

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

[0060] The inventor has studied the above problems and found that the reason for the above problems is that after the user obtains the smart device, the smart device cannot know the information of the corresponding user to complete the 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. After the user purchases the smart device, the ownership information of the smart device will not be applied to the smart device binding process. Therefore, if the 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 blockchain technology, which is open, transparent, traceable, and tamper-proof, can effectively ensure the authenticity, accuracy and security of the binding relationship between the user and the device. At the same time, the real id information of the device can only be obtained by the blockchain business platform through the decryption of the device's chain information, including the binding user. The real identity address of the smart device cannot be obtained. 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 by purchasing or giving away on the mobile app side. The platform 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, this solution is applied to the smart device binding system, refer to Figure 1 The system includes the user client or simply referred to as the client, the blockchain business platform, the smart device business platform, and the smart device end. The user client serves as the capability entrance of the blockchain business platform and the smart device business platform and is oriented to real users.

[0062] First, when smart devices leave the factory, they assemble the device access ID generated by the MAC address or other identification information and the type information (deviceType) identifiable by the smart device business platform together, and use the asymmetric encryption algorithm and public key provided by the blockchain business platform to generate a unique identification code that can be uploaded to the chain. This identification code represents the corresponding smart device in the blockchain.

[0063] The deviceType that identifies the device type and the corresponding device name, image identification, device control instruction set and other key device information will be 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 based on deviceType.

[0064] Afterwards, the digital smart device will be put on the chain through the blockchain business platform, that is, added to the blockchain. As the only channel for users to obtain devices and device information, the information on the chain can include the appearance picture logo of the real device, detailed function description, and the identification code of the device on the chain.

[0065] On the user side, in order to control smart devices, users need to use user clients, such as smart device management apps, etc. First, users need to complete the registration 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 a user obtains a smart device through purchase or collection on the blockchain business platform, the blockchain business platform will add the device's on-chain identification code information to the corresponding user's account for distributed storage. From then on, the user and the digital smart device establish an association relationship, which is open and traceable on the blockchain platform, and the ownership between the smart device and the user is recorded.

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

[0068] After the user obtains the physical smart device, the smart device will try to automatically connect to the Internet when it is turned on. After the smart device successfully connects to the Internet, it will actively send a network binding request to the smart device service platform. The information sent may include the real MAC address, device ID and other real device identity information of the smart device. The smart device service platform will query the registration record of the corresponding ID on the platform. If it is confirmed that it is an unregistered new device, it will complete the registration of the real device on the platform, and send a registration success mark to the real device according to the predetermined protocol to complete the registration of the real device on the smart device service platform.

[0069] Subsequently, the smart device will directly interact with the smart device business platform for information. The push to the user client or the issuance of client control instructions and the acquisition of smart device data information will all be authenticated by the third-party blockchain business platform, and information will be transparently transmitted between the client and the smart device business platform to complete the binding between the user and the real smart device.

[0070] Through the above steps, when users purchase smart devices through online shopping on the blockchain business platform, the blockchain business platform can automatically bind the ownership rights between the smart device and the corresponding user. Subsequently, the smart device will be automatically bound according to the ownership rights of the smart device. Similarly, when the smart device needs to change the binding relationship, it only needs to transfer the digital device information of the blockchain platform on the client, and the smart device can be bound to the account of other users. The specific process is as follows:

[0071] The original user initiates a digital device transfer request to the blockchain business platform on the client. After identity verification, the blockchain business platform transfers the distributed digital device to the corresponding user and forms a transfer record. At the same time, the smart device business platform issues a device initialization instruction to clear the smart device data stored on the device side and in the database. The new user obtains the device list through the blockchain business platform and completes the establishment of a new binding relationship.

[0072] You can refer to Figure 1 , Figure 1 This is a timing diagram of the device binding method provided by this application, such as Figure 1 As shown, when the smart device leaves the factory, the relevant information of the smart device is uploaded to the blockchain business platform and the smart device business platform respectively, and the blockchain business platform records the smart device on the blockchain. After the user registers an account, every time a new smart device is purchased, the user's client will automatically send the device identification code of the new device to the blockchain business platform, so that the blockchain platform can synchronize the ownership information of the device, thereby pre-recording the ownership information of the above-mentioned smart device in the blockchain and displaying it to the user. When the user obtains the above-mentioned smart device and turns on and connects the device to the network, the smart device business platform will send the device identification of the connected smart device to the blockchain business platform for synchronization, and the blockchain business platform will query the blockchain according to the device identification to obtain the owner of the smart device. Then send the identification information of the online smart device to the customer corresponding to the user account of this user, and the client will know that the device has been connected to the network and can be controlled, and then refresh the corresponding device status in the device list to controllable, and complete 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 interactive process in the middle dashed line is the process that the user needs to operate, and the interactive processes in the other solid lines are all automatically performed by the platform according to the preset rules. It can be seen that in this solution, the user does not need to perform cumbersome operations to bind the smart device.

[0073] Figure 2 The schematic diagram of the process of the device binding method provided by an embodiment of the present application is shown. The device binding method provided by the embodiment of the present application is applied to the above blockchain business platform or similar platforms. Figure 2 As shown, the method includes the following steps S201 to S204.

[0074] Step S201: receiving device information of a smart device sent by a smart device service platform, where the device information is device information sent by a smart device and received by the smart device service platform when the smart device is connected to the Internet.

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

[0076] A smart device can be a device that has computing and processing capabilities, can access a network, and communicate and exchange data with other devices or systems through the network. Accordingly, the device information of a smart device is the hardware information of the smart device, such as the MAC address of the smart device.

[0077] In the specific implementation, after the blockchain business platform establishes a communication connection with the smart device business platform, the smart device business platform packages the collected smart device data into a preset specific format and sends it to the blockchain business platform as a data packet. After the blockchain business platform receives the data packet, it obtains the device information of the smart device.

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

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

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

[0081] Step S203: Search the blockchain for device ownership information corresponding to the device identification code.

[0082] It should be noted that the correspondence between the device identification code and the user is stored in the blockchain, and the device-attributed user information may be the user information of the user corresponding to the above-mentioned device identification code.

[0083] In a specific implementation, after obtaining the above-mentioned device identification code, the blockchain business platform can traverse the transaction records of the blockchain, obtain the user currently corresponding to the device identification code, and then obtain the user information of this user, that is, the device-attributed user information.

[0084] Step S204: sending a device identification code to the client corresponding to the device-attributing user information, so that the client updates the state of the smart device corresponding to the device identification code to a controllable state, thereby completing the binding of the smart device and the client.

[0085] When using IoT smart devices, users usually need to send instructions to the smart devices to control them. The above-mentioned client can be the smart device user client software used by the user to control the smart devices.

[0086] It is understandable that before this, the user and the device identification code of the smart device have already had a corresponding relationship, but in this case it has not yet been determined whether the actual smart device has been in the hands of the user, so the user cannot control the above smart device. The controllable state can refer to the situation where the user can already control the corresponding smart device on the client.

[0087] In the specific implementation, after the blockchain business platform finds the device-attributed 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 done by building an interface on the blockchain business platform to pass the device identification code as data to the client application. After the client receives the device identification code, it can verify its validity. This can be done by comparing the received device identification code with the device identification code already stored by the client, or by verifying the authenticity and uniqueness of the device identification code through blockchain query. 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, at which point 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. Depending on the smart device, operations such as adjusting the temperature, turning on and off lights, and controlling home appliances can be performed.

[0088] The embodiment of the present application allows each device to save a unique identifier on the blockchain, and the current ownership of the device will be recorded in the blockchain. In this way, when the device identification information is received, the device identification code of the device in the blockchain is queried, and the device ownership information corresponding to the device identification code is found, and the device identification code is sent to the client corresponding to the device ownership information. Then the client can complete the 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 acquired digital smart device on the blockchain, and the corresponding device can be bound to the user account, and the entire binding process does not require cumbersome operations.

[0089] In some implementations, the device information includes a device identification and device type information; encrypting the device information to obtain a device identification code includes:

[0090] The device identification and device type information are encrypted based on a preset public key to obtain a device identification code.

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

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

[0093] The above implementation of the present application encrypts the device hardware information and adds the device to the blockchain. This improves the security of the device information. In addition, the encrypted information contains the device type information, which facilitates the smart device business platform to directly obtain the detailed information of the device based on the device type information.

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

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

[0096] User registration information can be information collected and created during the user registration process, which is used to identify and verify the user's identity and is associated with his or her activities in the IoT platform or system. It can usually include user identity information used to identify the user, user authentication information used to verify the user's identity, and user device information indicating the device owned by the user.

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

[0098] Step S302: A corresponding blockchain user account is established according to the user registration information. The blockchain user account stores the user registration information and is bound to the user registration information.

[0099] In blockchain, user accounts are often referred to as a public / private key pair. This is because in blockchain, security and trust mechanisms rely mainly on asymmetric encryption algorithms, where public keys can be made public, while private keys are held in secret by users and cannot be made public. Therefore, a blockchain user account can be a public / private key pair, where the public key is the address of the account, used to disclose and verify transactions; the private key is the user's identity, used to sign and ensure the security of transactions.

[0100] In the specific implementation, after obtaining the registration information, it is necessary to verify the information. It is mainly to verify the integrity and legality of the information, such as checking whether the information filled in by the user complies with the specifications and whether necessary information is omitted. Then it becomes a public key / private key pair for the user's account. The public key and private key are generated by an asymmetric encryption algorithm according to certain rules and stored in the database.

[0101] Step S303: upon receiving the 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.

[0102] In the specific implementation, after the blockchain user account user registration is completed, the user can record the smart devices he owns in the blockchain. For example, if a user purchases a new smart device on the network platform, the user's client can send the device information of the purchased device to the blockchain business platform, and the blockchain business platform will encrypt the device information and obtain the device identification code corresponding to the purchased device.

[0103] Step S304: Add 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 business platform. This can be done by querying a database or a 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 done 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 done by packaging the updated records into transactions through the blockchain business platform and broadcasting them to all nodes in the blockchain network for storage.

[0105] The above implementation of the present application receives user registration information sent by the smart device service platform, the user registration information includes the device information of the user's smart device; establishes a corresponding blockchain user account according to the user registration information, the blockchain user account stores the user registration information and is bound to the user registration information; when receiving the device information of the smart device sent by the client, encrypts the device information of the user's smart device to obtain the corresponding device identification code; and adds the corresponding device identification code to the blockchain user account. This allows the user to register a blockchain user account while registering on the device service platform, and automatically binds the user to the smart device on the blockchain, making it convenient for the user to use.

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

[0107] The device ownership change information sent by the client is received, where the device ownership change information includes a device identification code of the smart device to be bound.

[0108] Device ownership change information can be information that records changes in device ownership. Specifically, when a 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. This information usually includes the device's identification code, the owner's information, the timestamp of the change, etc. This information is publicly available on the blockchain, which can effectively prevent disputes over device ownership and illegal tampering.

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

[0110] The device identification code in the corresponding blockchain user account is changed according to the ownership change information.

[0111] In the specific implementation, after receiving the device ownership change information, the blockchain business platform needs to verify and process it. This includes verifying the validity of the information, confirming the ownership change 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 implementation of the present application receives the device ownership change information sent by the client, and the device ownership change information includes the device identification code of the smart device to be bound; the device identification code in the corresponding blockchain user account is changed according to the ownership change information. The transfer of device binding relationship does not require unbinding and rebinding. The binding relationship can be changed by transferring the digital device on the blockchain business platform. The traceability and public nature of the modification based on blockchain technology ensures the security of the binding relationship.

[0113] In some embodiments, the device ownership change information includes a client identifier of the client; and changing the device identifier in the corresponding blockchain user account according to the ownership change information includes:

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

[0115] The attribution record information may be a transaction record and a timestamp corresponding to the device identification code.

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

[0117] The client sending the ownership change information is verified based on the ownership record information.

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

[0119] If the verification is passed, an initialization instruction is sent to the smart device service platform, and the initialization instruction is used to clear the device data of the device corresponding to the ownership change information.

[0120] The initialization instruction may be an instruction related to clearing the settings and information saved in the smart device.

[0121] In the specific implementation, after the verification is confirmed, an initialization instruction can be generated according to the preset rules and logic, and the generated initialization instruction can be sent to the smart device service platform. After receiving the initialization instruction, the smart device service platform will parse the instruction and clear the device data corresponding to the ownership change information according to the instructions in the instruction. This can include operations such as deleting device data and resetting device status.

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

[0123] In the specific implementation, by querying the database or distributed ledger of the blockchain business platform, relevant information of the original blockchain user account and the new blockchain user account can be obtained, including the user's identity and device identification code. 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 smart 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 done by packaging the updated records into transactions through the smart device business platform and broadcasting them to all nodes in the blockchain network for storage.

[0124] The above implementation of the present application obtains the ownership record information sent by other multiple blocks in the blockchain; verifies the client that sends the ownership change information based on the ownership record information; if the verification passes, sends an initialization instruction to the smart device service platform, and the initialization instruction is used to clear the device data of the device corresponding to the ownership change information; according to the ownership change 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 smart device changes, identity authentication is performed, and the data of the changed device is cleared, making the device change process safer.

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

[0126] Get 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 the database or distributed ledger of the blockchain business platform.

[0128] The device information corresponding to the device identification code 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.

[0129] The device display information may be pictures, models, related parameters, and other information related to the smart device that the user needs to know.

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

[0131] In the specific implementation, the blockchain business platform sends the device information corresponding to the device identification code to the client corresponding to the blockchain user account, allowing the client to query the smart device business platform through the device information to obtain the device display information.

[0132] The above implementation of the present application obtains the device identification code corresponding to the blockchain user account; sends 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 user's client is allowed to display detailed device information, which is convenient for the user to find and use.

[0133] In some implementations, sending device information corresponding to a device identification code to a client corresponding to a blockchain user account includes:

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

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

[0136] The device identification code 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.

[0137] The above implementation of the present application obtains device type information according to the device identification code of the device corresponding to the blockchain user account; sends the device identification code and device type information 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. 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 user's information security can be guaranteed.

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

[0139] like Figure 4 As shown, for example, when a user registers on the client, he / she will register on the smart business platform and the blockchain business platform at the same time. After that, the user can send the device information of the smart devices he / she already owns to the blockchain business platform through the client, so that the blockchain business platform can add these smart devices to the blockchain and add them to the above-mentioned user accounts.

[0140] Moreover, when the ownership of the device changes, such as when the smart device is traded second-hand or donated, the ownership change information of the device is received and verified in the blockchain. If the verification is passed, the ownership of the smart device is changed.

[0141] When a user needs to view all the smart devices in his / her user account, he / she can obtain the device type information of the smart device from the blockchain business platform through the client, and obtain the device display information from the smart device business platform through this device type information for display, so that the user can view the detailed information of all the smart devices in his / her user account.

[0142] When a user purchases a new smart device, the ownership relationship between the smart device and the user account has been recorded on the blockchain at the time of purchase, but this does not mean that the user can use and control the smart device. Therefore, when the user actually starts to use the smart device, the smart device will send its own device information to the smart device business platform, and the smart device business platform will forward the device information to the blockchain business platform. The blockchain business platform will send the device identification code corresponding to the above device to the corresponding client based on the ownership relationship between the smart device and the user account, so that the user can actually control the above smart device, thereby completing the device binding.

[0143] See first Figure 5 The device binding apparatus 500 provided in the embodiment of the present application includes the following modules:

[0144] The receiving module 501 is used to receive device information of the smart device sent by the smart device service platform, where 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 Internet;

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

[0146] A search module 503 is used to search the device ownership user information corresponding to the device identification code from the blockchain;

[0147] The sending module 504 is used to send the device identification code to the client corresponding to the device belonging user information, so that the client updates the state of the smart device corresponding to the device identification code to a controllable state, thereby completing the binding of the smart device and the client.

[0148] The above scheme of the present application allows each device to save a unique identifier on the blockchain, and the current ownership of the device will be recorded in the blockchain. In this way, when the device identification information is received, the device identification code of the device in the blockchain is queried, and the device ownership information corresponding to the device identification code is found, and the device identification code is sent to the client corresponding to the device ownership information. Then the client can complete the 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 acquired digital smart device on the blockchain, and the corresponding device can be bound to the user account, and the entire binding process does not require cumbersome operations.

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

[0150] The above implementation of the present application encrypts the hardware information of the device and adds the device to the blockchain, thereby improving the security of the device information.

[0151] As an implementation of the present application, the receiving module 501 is further used to receive user registration information sent by the smart device service platform, where the user registration information includes device information of the user's smart device; the encryption module 502 is further used to encrypt the device information of the user's smart device to obtain a corresponding device identification code when receiving the device information of the smart device sent by the client; in this implementation, the device binding device 500 may also include:

[0152] The establishment module is also used to establish a corresponding blockchain user account according to the user registration information. The blockchain user account stores the user registration information and is bound to the user registration information;

[0153] Add module, used to add corresponding device identification code in blockchain user account.

[0154] The above implementation method of the present application allows users to register a blockchain user account while registering on the device business platform, and automatically binds the user to the smart device on the blockchain, making it convenient for users to use.

[0155] As an implementation of the present application, the receiving module 501 is further used to receive device ownership change information sent by the client, where the device ownership change information includes a device identification code of the smart device to be bound; in this implementation, the device binding apparatus 500 may also include:

[0156] The change module is used to change the device identification code in the corresponding blockchain user account according to the ownership change information.

[0157] The above-mentioned implementation method of the present application makes it possible to transfer device binding relationships without unbinding and rebinding. The binding relationship can be changed by simply transferring the digital device on the blockchain business platform. The traceability and public nature of the modification based on blockchain technology ensures the security of the binding relationship.

[0158] As an implementation of the present application, the sending module 504 is further used to send an initialization instruction to the smart device service platform when the verification is passed, and the initialization instruction is used to clear the device data of the device corresponding to the ownership change information; in this implementation, the device binding device 500 may also include:

[0159] The acquisition module is used to obtain the ownership record information sent by multiple other blocks in the blockchain;

[0160] A verification module, used for verifying the client sending the ownership change information based on the ownership record information;

[0161] The transfer module is used to transfer the corresponding device identification code from the original blockchain user account to the new blockchain user account according to the ownership change information.

[0162] The above implementation method of the present application performs identity authentication and clears the data of the changed device, making the device change process safer.

[0163] As an implementation method of the present application, the acquisition module is also used to obtain the device identification code corresponding to the blockchain user account; the sending module 504 is also used to send 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.

[0164] The above implementation method of the present application allows the user's client to display detailed device information, making it easier for the user to search and use.

[0165] As an implementation of the present application, the sending module 504 is also used to send the device identification code and device type information 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. In this implementation, the device binding device 500 may also include:

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

[0167] The above implementation method of the present application stores the device identification code on the blockchain platform and stores the device display information on the device business platform. The binding relationship between the device and the user account is no longer strongly associated, and the user's information security can be guaranteed.

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

[0169] The data processing device may include a processor 601 and a memory 602 storing computer program instructions.

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

[0171] The memory 602 may include a large capacity memory for data or instructions. By way of example and not limitation, the memory 602 may 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. In appropriate cases, the memory 602 may include a removable or non-removable (or fixed) medium. In appropriate cases, the memory 602 may be inside or outside the integrated gateway disaster recovery device. In a specific embodiment, the memory 602 is a non-volatile solid-state memory.

[0172] The memory may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Therefore, typically, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the data processing method according to any one embodiment of the present disclosure.

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

[0174] In one example, the data processing device may further include a communication interface 603 and a bus 610. Figure 6 As shown, the processor 601, the memory 602, and the communication interface 603 are connected via a bus 610 and communicate with each other.

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

[0176] Bus 610 includes hardware, software or both, and the parts of online data flow billing equipment are coupled to each other. For example, but not limitation, bus may include accelerated graphics port (AGP) or other graphics bus, enhanced industrial standard architecture (EISA) bus, front-end bus (FSB), hypertransport (HT) interconnection, industrial standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In appropriate cases, bus 610 may include one or more buses. Although the present application embodiment describes and shows a specific bus, the present application considers any suitable bus or interconnection.

[0177] In addition, in combination with the data processing method in the above embodiment, the embodiment of the present application can provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when the computer program instructions are executed by a processor, any device binding method in the above embodiment is implemented.

[0178] However, it should be clear that the present invention is not limited to the specific configurations and processes described above and shown in the figures. Moreover, for the sake of simplicity, a detailed description of known methods and techniques is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present invention is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present invention.

[0179] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present invention are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting 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, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0180] The present invention can be implemented in other specific forms without departing from its spirit and essential features. For example, the algorithms described in the specific embodiments can be modified, and the system architecture does not depart from the basic spirit of the present invention. Therefore, the current embodiments are regarded as exemplary and non-restrictive in all aspects, and the scope of the present invention is defined by the appended claims rather than the above description, and all changes falling within the meaning and equivalent scope of the claims are thus included in the scope of the present invention.

[0181] Those skilled in the art should understand that the above embodiments are exemplary rather than restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Based on the study of the drawings, the specification and the claims, those skilled in the art should be able to understand and implement other variations of the disclosed embodiments. In the claims, the term "comprising" does not exclude other devices or steps; the indefinite article "a" does not exclude a plurality; the terms "first" and "second" are used to indicate names rather than to indicate any specific order. Any figure marks in the claims should not be understood as limiting the scope of protection. The functions of multiple parts appearing in the claims can be implemented by a single hardware or software module. The appearance of certain technical features in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A device binding method, characterized in that: The method comprises: Receiving device information of a smart device sent by a smart device service platform, wherein the device information is device information sent by the smart device and received by the smart device service platform when the smart device is connected to the Internet; Encrypting the device information to obtain a device identification code; Searching the blockchain for device ownership information corresponding to the device identification code; The device identification code is sent to the client corresponding to the device belonging user information, so that the client updates the state of the smart device corresponding to the device identification code to a controllable state, thereby completing the binding of the smart device and the client.

2. The device binding method according to claim 1, characterized in that: The device information includes device identification and device type information; the device information is encrypted to obtain a device identification code, including: The device identification and the device type information are encrypted based on a preset public key to obtain a device identification code.

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: Receiving user registration information sent by the smart device service platform, wherein the user registration information includes device information of the user's smart device; Establish a corresponding blockchain user account according to the user registration information, wherein the blockchain user account stores the user registration information and is bound to the user registration information; Upon receiving the 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; Add the corresponding device identification code in the blockchain user account.

4. The device binding method according to claim 3, characterized in that: After adding the corresponding device identification code to the blockchain user account, the method further includes: Receiving device ownership change information sent by the client, wherein the device ownership change information includes a device identification code of the smart device to be bound; The device identification 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 a client identifier of the client; and the changing of the device identification code in the corresponding blockchain user account according to the ownership change information includes: Obtain ownership record information sent by multiple other nodes in the blockchain; verifying the client sending the attribution change information based on the attribution record information; If the verification is passed, an initialization instruction is sent to the smart device service platform, wherein the initialization instruction is used to clear device data of the device corresponding to the ownership change information; According to the ownership change information, the corresponding device identification code is 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 identification code to the blockchain user account based on the user registration information, the method further includes: Get the device identification code corresponding to the blockchain user account; The device information corresponding to the device identification code is sent to the client corresponding to the blockchain user account, where 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: The sending the device information corresponding to the device identification code to the client corresponding to the blockchain user account includes: Obtain device type information according to the device identification code of the device corresponding to the blockchain user account; 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.

8. A device binding apparatus, characterized in that: The device comprises: A receiving module, used to receive device information of a smart device sent by a smart device service platform, wherein the device information is device information sent by the smart device and received by the smart device service platform when the smart device is connected to the Internet; An encryption module, used for encrypting the device information to obtain a device identification code; A search module, used to search for device ownership information corresponding to the device identification code from the blockchain; The sending module is used to send the device identification code to the client corresponding to the device belonging user information, so that the client updates the state of the smart device corresponding to the device identification code to a controllable state, thereby completing the binding of the smart device and the client.

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

10. A computer-readable storage medium, characterized in that: The computer storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the device binding method according to any one of claims 1 to 7 is implemented.

Images