Discover and match IoT devices and services using a secure global registry
By adopting secure global registry and blockchain technology in IoT devices, the information management problems of IoT devices during ownership transfer and cloud service changes are solved, and the security and flexible identity management of the devices are realized, reducing resource usage and bandwidth requirements .
Patent Information
- Application Number
- CN202080020868.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-03-17
- Filing Date
- 2020-03-05
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2040-03-05
AI Technical Summary
The prior art is difficult to securely store and access device connection information when IoT device ownership transfer and cloud services change, and lacks a simple way to transfer cloud endpoints, limiting the flexibility of the device and the manufacturer's scale capabilities.
Using a secure global registry, especially a distributed blockchain structure based on alliances, allocates global unique device identifiers (DIDs) and public/private key pairs to IoT devices, and stores and manages cloud points of devices through a secure global registry. Message, allowing the device to replace cloud connection information without refreshing.
It realizes the secure, reliable and flexible device identity management of IoT devices, reduces the use of computing resources and bandwidth, supports device ownership transfer and cloud service changes, and improves device flexibility and manufacturer's scale capabilities.
Smart Images

Figure CN113632438B_ABST
Abstract
Description
Background Art
[0001] As computing systems become cheaper and smaller, they have begun to proliferate into almost all areas of life. Internet of Things (IoT) devices are network-connected devices that are placed in many physical spaces to enable people to interact with and collect information about their environment. For example, an office or home may include many IoT devices that can be used to control locks, manage indoor climate and receive climate information, manage lighting and receive lighting information, open and close doors, perform cleaning functions, control audio and / or video devices, provide voice interaction, provide security and monitoring functions, etc. As a result, IoT devices can process and generate a large amount of information. As IoT devices proliferate, it becomes increasingly difficult to manage the devices and their users, and to be able to process the data they generate. Summary of the invention
[0002] Described herein is a device (e.g., an IoT device) comprising: a computer including a processor and a memory having computer-executable instructions stored thereon that, when executed by the processor, cause the computer to: provide a globally unique device identifier of the device to a secure global registry; receive information from the secure global registry; and connect to a cloud-based endpoint using the received information.
[0003] The present invention also describes a method for registering a device, comprising: creating a globally unique identifier for the device; obtaining a public / private key pair for the device; and creating an initial entry in a secure global registry including the globally unique identifier and the device public key, wherein the secure global registry stores current cloud-based endpoint information for the device.
[0004] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. BRIEF DESCRIPTION OF THE DRAWINGS
[0005] Figure 1 is a functional block diagram illustrating an IoT device registration system.
[0006] Figure 2 is a functional block diagram illustrating a distributed shared blockchain database.
[0007] Figure 3 is a flow chart illustrating a method of registering a device.
[0008] Figure 4 is a flow chart illustrating a method of registering a device.
[0009] Figure 5is a flow chart illustrating a method of discovering information from a secure global registry.
[0010] Figure 6 is a flow chart illustrating a method for updating secure global registration information
[0011] Figure 7 is a functional block diagram illustrating an exemplary computing system. DETAILED DESCRIPTION
[0012] Various techniques related to the use of a secure global registry to discover and match Internet of Things (IoT) devices and services are now described with reference to the accompanying drawings, wherein similar reference numerals are used throughout to refer to similar elements. In the following description, for the purpose of explanation, many specific details are set forth in order to provide a thorough understanding of one or more aspects. However, it is apparent that these aspects can be practiced without these specific details. In other cases, well-known structures and devices are shown in block diagram form to facilitate describing one or more aspects. In addition, it should be understood that functions described as being performed by certain system components can be performed by multiple components. Similarly, for example, a component can be configured to perform functions described as being performed by multiple components.
[0013] The subject disclosure supports various products and processes that perform or are configured to perform various actions regarding discovery and matching of Internet of Things (IoT) devices and services using a secure global registry. The following are one or more exemplary systems and methods.
[0014] Aspects of the present disclosure relate to technical problems of discovery and matching of Internet of Things (IoT) devices and services. Technical features associated with solving this problem relate to providing a secure global registry for IoT devices. Using a secure global registry, (multiple) manufacturers, (multiple) device owners, and / or (multiple) IoT devices can securely store, change, and / or access information (e.g., cloud endpoint information) of specific IoT devices and / or about specific IoT devices. IoT devices can be manufactured to be cloud-independent, wherein the IoT devices obtain current connection information from a secure global registry. In some embodiments, the secure global registry includes a private (e.g., consortium-based) blockchain distributed structure (e.g., a database). Therefore, aspects of these technical features exhibit technical effects of more efficiently and effectively discovering and matching IoT devices and services, for example, reducing computer resources (e.g., processing time and / or memory) and / or reducing bandwidth.
[0015] Furthermore, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." That is, unless specified otherwise or clear from the context, the phrase "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, the phrase "X employs A or B" satisfies any of the following: X employs A; X employs B; or X employs A and B. Furthermore, the articles "a" and "an" used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from the context to direct to a singular form.
[0016] As used herein, the terms "component" and "system" and their various forms (e.g., component, system, subsystem, etc.) are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software being executed. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an instance, an executable file, an execution thread, a program, and / or a computer. For example, both an application running on a computer and a computer can be a component. One or more components can reside in a process and / or execution thread, and a component can be located on one computer and / or distributed between two or more computers. In addition, as used herein, the term "exemplary" is intended to mean an illustration or example of something and is not intended to indicate a preference.
[0017] Internet of Things (IoT) devices are network-connected devices placed in many physical spaces to enable people to interact with their environment and collect information about their environment. Many IoT device manufacturers do not want to require their IoT devices to be used with a specific cloud provider, which would limit the manufacturer's ability to manufacture on a large scale. In addition, during the life of a particular device, the device may experience more than one owner. In addition, the device owner may desire to change the cloud provider for one, some, or all IoT devices owned by the owner. Traditionally, there is no easy way to transfer ownership and / or cloud endpoints without re-flashing the device when ownership is transferred.
[0018] The systems and methods described herein include a secure global registry for IoT devices. Using a secure global registry, (multiple) manufacturers, (multiple) device owners, and / or (multiple) IoT devices can securely store, change, and / or access information of and / or about a specific IoT device (e.g., cloud endpoint information). In this way, IoT devices can initially be manufactured to be cloud-independent, where the IoT device obtains current connection information from a secure global registry. Therefore, the connection information of a specific IoT device can be changed without refreshing the device, for example, when the device owner changes ownership or changes cloud-based services. In some embodiments, the secure global registry includes a private (e.g., consortium-based) blockchain distributed structure (e.g., a database).
[0019] refer to Figure 1 , shows an IoT device registration system 100. The system 100 includes a secure global registry 110, an initial registration component 120, an IoT device 130, and a device owner component 140.
[0020] For purposes of explanation and not limitation, the system 100 will be discussed with reference to a single IoT device 130 and a single owner. In some embodiments, the system 100 can be employed with multiple IoT devices 130 (e.g., hundreds, thousands, millions, etc.). In some embodiments, the system 100 can be employed with multiple owners (e.g., initial owner(s) and / or subsequent owner(s) of a particular IoT device 130).
[0021] In some embodiments, to facilitate secure transactions within the secure global registry 110, the initial registration component 120 and / or the device owner component 140 may have security credentials. In some embodiments, the security credentials may include a public / private cryptographic key pair. A variety of encryption algorithms may be used, including but not limited to Advanced Encryption Standard (AES), Data Encryption Standard (DES), Rivest-Shamir-Adleman (RSA), and Elliptic Curve Cryptography (ECC), among others. For the purposes of discussion, the certificates of the (multiple) entities (e.g., initial registration component 120 and / or device owner component 140) that perform transactions within the secure global registry 110 are sometimes referred to herein as "owner certificates," "owner public keys," and / or "owner private keys."
[0022] In some embodiments, the initial registration component 120 is associated with a manufacturer of the IoT device 130. In some embodiments, the initial registration component 120 is associated with a first owner or a subsequent owner of the IoT device 130.
[0023] In some embodiments, each IoT device 130 is assigned a globally unique decentralized identifier (DID). The DID can be assigned by the initial registration component 120. The initial registration component 120 can store the DID on the IoT device 130.
[0024] DIDs allow for self-owned identities, allowing IoT devices 130 to control their digital identities. DIDs can be created, owned, and / or controlled independently of any particular organization (e.g., IoT device manufacturer, cloud provider, IoT device owner), and can include a globally unique identifier linked to a decentralized public key infrastructure (DPKI) metadata, which consists of a JSON document containing public key material, (multiple) authentication descriptors, and / or (multiple) service endpoints. DIDs can have unique properties, such as better guarantees of immutability and tamper resistance.
[0025] In some embodiments, to facilitate secure communication with IoT device 130, initial registration component 120 creates a public / private key pair (sometimes referred to herein as a “device public key” and a “device private key”) for a particular IoT device 130. Initial registration component 120 can store the device private key on IoT device 130 (e.g., securely), and the device public key can be stored in secure global registry 110 for secure communication with IoT device 130.
[0026] The device public key can be used to encrypt data to be retrieved by the IoT device 130. The device private key can be used by the IoT device 130 to decrypt the encrypted data. In some embodiments, the IoT device 130 can use the device private key to sign a message for authentication (e.g., to prove possession of the device private key).
[0027] In some embodiments, a device public / private cryptographic key pair is generated based on an Edwards curve digital signature algorithm (e.g., Ed25519). In some embodiments, a device public / private cryptographic key pair is generated based on a Rivest-Shamir-Adleman encryption algorithm (e.g., an RSA encryption algorithm). In some embodiments, a device public / private cryptographic key pair is generated based on an Advanced Encryption Standard (AES) algorithm. A device public / private key pair is generated based on a Data Encryption Standard (DES) algorithm. In some embodiments, a device public / private cryptographic key pair is generated based on elliptic curve cryptography (ECC). In some embodiments, a device may utilize a symmetric key. In some embodiments, a device key (e.g., a device private key) may be rotated (e.g., changed) by a subsequent owner.
[0028] The initial registration component 120 initiates the creation of an entry 150 associated with a specific IoT device 130 in the secure global registry 110 using the DID. The initial registration component 120 can store information associated with the specific IoT device 130 (e.g., DID, device public key) in the entry 150. In some embodiments, the initial registration component 120 does not store endpoint information (e.g., cloud endpoint information) for and / or about the specific IoT device 130. In some embodiments, the initial registration component 120 stores endpoint information (e.g., cloud endpoint information) for and / or about the specific IoT device 130. In some embodiments, the endpoint information includes an identifier (Uniform Resource Identifier (URI)) of a specific document stored in the secure global registry 110 or elsewhere (e.g., stored off-chain).
[0029] In some embodiments, the secure global registry 110 is a database in which each entry 150 stores information associated with a particular IoT device 130. In some embodiments, the information includes the DID, current configuration information of the particular IoT device 130 (e.g., endpoint information), a reference to the current configuration information of the particular IoT device 130 (e.g., an associated device identifier foundation (DIF) hub), and / or a device public key associated with the particular IoT device 130. In some embodiments, some or all of the information is encrypted using the device public key. In some embodiments, the entry is signed using owner credentials such as the owner's private key.
[0030] In some embodiments, secure global registry 110 is a public blockchain distributed structure. In some embodiments, as discussed more fully below, secure global registry 110 is a private blockchain distributed structure.
[0031] The IoT device 130 includes a boot code 160 that facilitates communication between the IoT device 130 and the secure global registry 110. In some embodiments, the boot code 160 is installed on the IoT device 130 by the manufacturer of the IoT device 130. In some embodiments, the boot code 160 is installed by the owner of the IoT device 130.
[0032] In some embodiments, the boot code 160 is executed when the IoT device 130 is powered on. In some embodiments, the boot code 160 is executed periodically (e.g., hourly, daily, monthly). In some embodiments, the boot code 160 is executed in response to an event, such as receiving an electronic message requesting the IoT device 130 to obtain current information from the secure global registry 110. In some embodiments, the boot code 160 is executed in response to user input (e.g., a reset button) received via the IoT device 130.
[0033] In some embodiments, the boot code 160 provides the DID of a particular IoT device 130 in a request to the secure global registry 110. In response to the request, the secure global registry 110 can provide data (e.g., unencrypted or encrypted) associated with current information (e.g., cloud endpoint information) associated with the DID.
[0034] In some embodiments, the boot code 160 provides the DID of a specific IoT device 130 and a message signed with a device private key to authenticate the IoT device 130. The secure global registry 110 can use the stored device public key to authenticate the specific IoT device 130. Only when authenticated, in response to a request, the secure global registry 110 can provide data (e.g., unencrypted or encrypted) associated with the current information (e.g., cloud endpoint information) associated with the DID. The boot code 160 can use the received information to communicate with a specific cloud-based service 170.
[0035] In some embodiments, the boot code 160 provides the DID of a specific IoT device 130 in a request to the secure global registry 110. In some embodiments, the secure global registry 110 may respond with a challenge requiring the IoT device 130 to authenticate itself. For example, the secure global registry 110 may request the IoT device 130 to sign specific data or a specific message to prove its identity. In response, the boot code 160 may sign the specific data or the specific message with the device's private key and provide the signed message to the secure global registry 110.
[0036] The secure global registry 110 can utilize the stored device public key to authenticate a specific IoT device 130. Only when authenticated, in response to a request, can the secure global registry 110 provide data (e.g., unencrypted or encrypted) associated with the current data (e.g., cloud endpoint information) associated with the DID.
[0037] Next, changes (multiple) may occur that affect the IoT device 130. In some embodiments, the ownership of the IoT device 130 may change from a first owner to a second owner, which may affect the service endpoint. In some embodiments, the owner's cloud endpoint may change from a first service endpoint to a second service endpoint. These changes may be made in the secure global registry 110 using the device owner component 140 (e.g., by the owner and / or subsequent owners).
[0038] In some embodiments, the device owner component 140 and / or an entity (e.g., a cloud provider or other external entity on behalf of the device owner) can update an entry 150 of the secure global registry 110 for a particular IoT device 130 based at least in part on the DID. In some embodiments, the device owner component 140 can update information (e.g., cloud endpoint information) for a particular IoT device 130. In some embodiments, the device owner component 140 can update a reference to current configuration information for a particular IoT device 130 (e.g., an associated device identifier foundation (DIF) hub). In some embodiments, the device owner component 140 signs the updated entry 150 using an owner credential, such as the owner's private key. Once the change(s) are made to the entry 150, the IoT device 130 can receive the updated information, as described above.
[0039] Steering Figure 2 As described above, in some embodiments, the secure global registry 110 includes a distributed shared blockchain database 200. A particular blockchain 210 of the database 200 includes one or more blocks 220 associated with a particular IoT device 130 based at least in part on a DID.
[0040] For purposes of explanation and not limitation, an example initial block is set forth in Table 1:
[0041]
[0042] Table 1
[0043] In the example of Table 1, the device owner or manufacturer does not provide a service endpoint. The boot code 160 of the IoT device 130 associated with this entry will not be able to use the information contained in this initial block to connect to the cloud-based service.
[0044] Block(s) 220 are added to one or more blockchains 210 using a blockchain component 230. In some embodiments, the initial registration component 120, the device owner component 130, and / or the secure global registry 110 may have a blockchain component 230.
[0045] For purposes of explanation and not limitation, the following blocks are set forth in Table 2:
[0046]
[0047] Table 2
[0048] In the example of Table 2, the device owner has updated the distributed shared blockchain database 200 to include a "serviceEndpoint" that the boot code 160 of the IoT device 130 will use to obtain information for connecting to a cloud-based service. In some embodiments, the boot code 160 can download an appropriate software development kit (SDK) associated with a particular cloud based at least in part on the received information. For example, the download location can be embedded in the device's DIF document or published separately in a universal registry for each cloud provider. Once the SDK is downloaded, the boot code 160 can use the SDK to communicate with the cloud-based service.
[0049] In some embodiments, each IoT device 130 of the system 100 is represented as a chain of events within the distributed shared blockchain database 200, e.g., transferring ownership from one party to another on the blockchain, changing a cloud endpoint (e.g., with or without an intermediary), etc. In some embodiments, each event can be cryptographically proven by including a public key of the IoT device 130. Additionally, in some embodiments, each event (e.g., a block added) can be digitally signed with the private key of the current owner, e.g., to allow traceability, to indicate current ownership of the IoT device 130, and / or to indicate past ownership of the IoT device 130.
[0050] In some embodiments, the blockchain may provide a mathematical hierarchy of verifiable events that is immutable and verified at each stage between participants (e.g., each party has a copy of the distributed shared blockchain database 200). Consensus protocols may be used to protect blocks, including cryptographic competitions, proof of work, proof of useful work, proof of stake, rumor mill messaging, etc.
[0051] In response to an event (e.g., a change of ownership, a change of cloud endpoints), the blockchain component 230 can add a block 220 to a specific blockchain 210 associated with a specific IoT device 130 based on the DID. In some embodiments, the blockchain component 230 can be a block 220 of multiple blockchains 210, for example, to facilitate the transfer of ownership and / or the change of cloud endpoints of multiple IoT devices 130.
[0052] In some embodiments, each new block in the blockchain is filled with cryptographically proven events until the block reaches a specified size limit. A hash digest of all event identifiers within the block and the block header of the previous block may be added as the first event in the block.
[0053] In some embodiments, the distributed shared blockchain database 200 is private and shared only among members of the consortium. The (multiple) IoT devices 130 and / or (multiple) initial registrant components 120 (e.g., IoT device manufacturers, owners) and / or device owner components 140 (e.g., IoT device manufacturers, (multiple) owners) are able to access the distributed shared blockchain database 200 if they are members of the consortium. Optionally, the (multiple) IoT devices 130 and / or (multiple) initial registrant components 120 (e.g., IoT device manufacturers, owners) and / or device owner components 140 (e.g., IoT device manufacturers, (multiple) owners) are able to access the distributed shared blockchain database 200 through the consortium members (e.g., when providing the appropriate (multiple) certificates to the member responsible for authentication).
[0054] Figure 3-6 Illustrated are exemplary methods related to (multiple) secure global registries. Although these methods are shown and described as a series of actions performed in sequence, it should be understood and appreciated that the method is not limited by the order of the sequence. For example, some actions may occur in an order different from the order described herein. In addition, an action may occur simultaneously with another action. In addition, in some cases, all actions may not be required to implement the methods described herein. In addition, the actions described herein may be computer executable instructions that can be implemented by one or more processors and / or stored on a computer readable medium or medium. Computer executable instructions may include routines, subroutines, programs, execution threads, etc. Further, the results of the actions of the method may be stored in a computer readable medium, displayed on a display device, etc.
[0055] Reference Figure 3 , a method of registering a device 300 is shown. In some embodiments, the method 300 is performed by the initial registration component 120 to register the IoT device 130.
[0056] At 310, a globally unique device identifier (DID) is created for the IoT device. At 320, an initial entry in a secure global registry is created using the DID and optional endpoint information, wherein the secure global registry stores current cloud-based endpoint information for the device. At 330, the initial entry in the secure global registry entry is signed using an owner private key (e.g., by initial registration component 120). At 340, the globally unique device identifier (DID) is stored on the IoT device. At 350, boot code (e.g., boot code 160) is stored on the IoT device.
[0057] Reference Figure 4 , a method of registering a device 400 is shown. In some embodiments, the method 400 is performed by the initial registration component 120 to register the IoT device 130.
[0058] At 410, a globally unique device identifier (DID) is created for the IoT device. At 420, a public / private key pair is obtained (e.g., created) for the IoT device. At 430, an initial entry in a secure global registry is created using the DID, the device public key, and / or endpoint information, wherein the secure global registry stores current cloud-based endpoint information for the device. At 440, the initial entry in the secure global registry entry is signed using an owner private key (e.g., by initial registration component 120).
[0059] At 450, a device private key is stored on the IoT device. At 460, a globally unique device identifier (DID) is stored on the IoT device. At 470, a boot code (eg, boot code 160) is stored on the IoT device.
[0060] Steering Figure 5 , showing a method of discovering information from a secure global registry 500. In some embodiments, the method 500 is performed by the boot code 160 of the IoT device 130.
[0061] At 510, the DID (e.g., globally unique device identifier) is provided to a secure global registry. In some embodiments, the secure global registry is a single secure database. In some embodiments, the secure global registry is a public blockchain distributed structure. In some embodiments, the secure global registry is a private blockchain distributed structure.
[0062] At 520, a determination is made as to whether authentication is required by the secure global registry. In some embodiments, the determination may be made by the boot code 160 (e.g., hard-coded). In some embodiments, the determination may be made based on receiving a challenge (e.g., a request for authentication) from the secure global registry. If the determination at 520 is yes, then at 530, the IoT device is authenticated to the secure global registry. For example, the boot code 160 may sign a message using a stored device private key and present the signed message to the secure global registry to authenticate the IoT device. At 540, a determination is made as to whether the IoT device has been authenticated. If the determination at 540 is no, no further processing is performed. If the determination at 540 is yes, processing continues at 550. If the determination at 520 is no, processing continues at 550.
[0063] At 550, information (e.g., endpoint connection information) is received from the secure global registry. At 560, the received information is used to connect to the cloud-based endpoint. In some embodiments, the boot code 160 can download an appropriate software development kit (SDK) associated with a particular cloud based at least in part on the received information. For example, the download location can be embedded in the device's DIF document or published separately in a universal registry for each cloud provider. Once the SDK is downloaded, the boot code 160 can use the SDK to communicate with the cloud-based service.
[0064] The IoT device is authenticated to the cloud-based endpoint at 570. For example, a cloud-based service associated with the cloud-based endpoint can verify whether the authentication information provided by the IoT device corresponds to a public certificate in a DIF file associated with the particular IoT device.
[0065] Next reference Figure 6 , a method for updating secure global registration information 600 is shown. In some embodiments, the method 600 is performed by the device owner component 140 and / or the blockchain component 230.
[0066] At 610, a secure global registry entry for a particular IoT device is updated. At 620, the updated entry is signed with the owner private key.
[0067] Described herein is a device comprising: a computer including a processor and a memory having computer executable instructions stored thereon, the computer executable instructions, when executed by the processor, causing the computer to: provide a globally unique device identifier of a device to a secure global registry; receive information from the secure global registry; and connect to a cloud-based endpoint using the received information.
[0068] The device may also include wherein the secure global registry includes a single secure database. The device may also include wherein the secure global registry includes a public blockchain distributed structure. The device may also include wherein the secure global registry includes a private blockchain distributed structure.
[0069] The device may also include a memory having additional computer executable instructions stored thereon, which, when executed by the processor, cause the computer to: authenticate the device to a secure global registry using the device private key. The device may also include a memory having additional computer executable instructions stored thereon, which, when executed by the processor, cause the computer to: authenticate the device to a cloud-based endpoint.
[0070] The device may also include, wherein the computer executable instructions are executed periodically. The device may also include, wherein the computer executable instructions are executed in response to receiving an electronic message requesting the device to obtain current information from a secure global registry. The device may also include, wherein the computer executable instructions are executed in response to receiving user input.
[0071] Described herein is a method for registering a device, comprising: creating a globally unique identifier for the device; obtaining a public / private key pair for the device; and creating an initial entry in a secure global registry including the globally unique identifier and the device public key, wherein the secure global registry stores current cloud-based endpoint information for the device.
[0072] The method may also include signing an initial entry in the secure global registry using an owner private key. The method may also include storing the device private key on the device; and storing a globally unique identifier on the device. The method may also include storing boot code on the device, wherein the boot code facilitates communication between the device and the secure global registry.
[0073] The method may also include wherein the secure global registry comprises a public blockchain distributed structure. The method may also include wherein the secure global registry comprises a private blockchain distributed structure.
[0074] Described herein is a computer storage medium storing computer-readable instructions that, when executed, cause a computing device to: create a globally unique identifier for a device; obtain a public / private key pair for the device; and create an initial entry in a secure global registry including the globally unique identifier and the device public key, wherein the secure global registry stores current cloud-based endpoint information for the device.
[0075] The computer storage medium may store further computer readable instructions that, when executed, cause the computing device to: sign an initial entry in a secure global registry using the owner private key. The computer storage medium may store further computer readable instructions that, when executed, cause the computing device to: store the device private key on the device; and store a globally unique identifier on the device.
[0076] The computer storage medium may store further computer readable instructions that, when executed, cause the computing device to: store boot code on the device, wherein the boot code facilitates communication between the device and the secure global registry. The computer storage medium may also include wherein the secure global registry includes a private blockchain distributed structure.
[0077] refer to Figure 7, an example general purpose computer or computing device 702 is shown (e.g., a mobile phone, desktop, laptop, tablet, watch, server, handheld, programmable consumer or industrial electronic device, set-top box, gaming system, computing node, etc.). For example, computing device 702 can be used in IoT device registration system 100.
[0078] The computer 702 includes one or more processors 720, a memory 730, a system bus 740, (multiple) mass storage devices 750, and one or more interface components 770. The system bus 740 communicatively couples at least the above-mentioned system components. However, it should be understood that in its simplest form, the computer 702 may include one or more processors 720 coupled to the memory 730, which execute various computer-executable actions, instructions, and / or components stored in the memory 730. The instructions may be, for example, instructions for implementing the functions described as being performed by one or more of the above-mentioned components or instructions for implementing one or more of the above-mentioned methods.
[0079] Processor 720 can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but in an alternative, the processor can be any processor, controller, microcontroller, or state machine. (Multiple) processors 720 can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, a multi-core processor, one or more microprocessors combined with a DSP core, or any other such configuration. In one embodiment, processor 720 can be a graphics processor.
[0080] Computer 702 may include or otherwise interact with a variety of computer-readable media to facilitate control of computer 702 to implement one or more aspects of the claimed subject matter. Computer-readable media can be any available media that can be accessed by computer 702 and includes both volatile and nonvolatile media, and removable and non-removable media. Computer-readable media can include two different and mutually exclusive types, computer storage media and communication media.
[0081] Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes storage devices such as memory devices (e.g., random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), etc.), magnetic storage devices (e.g., hard disks, floppy disks, cassettes, tapes, etc.), optical disks (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), and solid-state devices (e.g., solid-state drives (SSDs), flash memory drives (e.g., cards, sticks, key drives), etc.), or any other similar media that stores the desired information accessible by the computer 702, as opposed to transmission or communication. Therefore, computer storage media does not include modulated data signals, such as and what is described with respect to communication media.
[0082] Communication media embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and includes any information delivery media. The term "modulated data signal" refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
[0083] Memory 730 and mass storage device(s) 750 are examples of computer-readable storage media. Depending on the exact configuration and type of computing device, memory 730 may be volatile (e.g., RAM), non-volatile (e.g., ROM, flash memory, etc.), or some combination of the two. For example, a basic input / output system (BIOS), including basic routines for transferring information between elements within the computer 702, such as during startup, may be stored in non-volatile memory, while volatile memory may act as external cache memory to facilitate processing by processor(s) 720, etc.
[0084] The mass storage device(s) 750 include removable / non-removable, volatile / non-volatile computer storage media for storing large amounts of data associated with the memory 730. For example, the mass storage device(s) 750 include, but are not limited to, one or more devices such as a magnetic or optical disk drive, a floppy disk drive, a flash memory, a solid state drive, or a memory stick.
[0085] The memory 730 and the mass storage device(s) 750 may include or have stored therein an operating system 760, one or more applications 762, one or more program modules 764, and data 766. The operating system 760 is used to control and allocate resources of the computer 702. The application 762 includes one or both of system and application software, and can utilize the operating system 760 to manage resources by performing one or more operations through the program modules 764 and data 766 stored in the memory 730 and / or the mass storage device(s) 750. Therefore, the application 762 can turn the general-purpose computer 702 into a special-purpose machine according to the logic provided by it.
[0086] All or part of the claimed subject matter may be implemented using standard programming and / or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed functionality. By way of example and not limitation, the system 100 or a portion thereof may be or form part of an application 762 and include one or more modules 764 and data 766 stored in memory and / or mass storage device 750 that, when executed by one or more processors 720, may implement functionality.
[0087] In some embodiments, (multiple) processors 720 may correspond to a system on chip (SOC) or similar architecture, including or in other words, integrating both hardware and software on a single integrated circuit substrate. Here, (multiple) processors 720 may include one or more processors and at least a memory similar to (multiple) processors 720 and memory 730, etc. Conventional processors include a minimum amount of hardware and software and rely extensively on external hardware and software. In contrast, the SOC implementation of the processor is more powerful because it has embedded hardware and software therein, which can implement specific functions with minimal or no reliance on external hardware and software. For example, system 100 and / or associated functions may be embedded in the hardware of the SOC architecture.
[0088] The computer 702 also includes one or more interface components 770 that are communicatively coupled to the system bus 740 and facilitate interaction with the computer 702. For example, the interface component 770 can be a port (e.g., serial, parallel, PCMCIA, USB, FireWire, etc.) or an interface card (e.g., sound, video, etc.), etc. In one example implementation, the interface component 770 can be embodied as a user input / output interface to enable a user to input commands and information into the computer 702 through one or more input devices (e.g., a pointing device such as a mouse, a trackball, a stylus, a touchpad, a keyboard, a microphone, a joystick, a game controller, a satellite dish, a scanner, a camera, other computers, etc.), such as through one or more gestures or voice input. In another example implementation, the interface component 770 can be embodied as an output peripheral interface to provide output to a display (e.g., LCD, LED, plasma, etc.), a speaker, a printer, and / or other computers, etc. Further, the interface component 770 can be embodied as a network interface to enable communication with other computing devices (not shown), such as through a wired or wireless communication link.
[0089] What has been described above includes examples of aspects of the claimed subject matter. Of course, it is not possible to describe every possible combination of components or methods for the purpose of describing the claimed subject matter, but one of ordinary skill in the art may recognize that many further combinations and permutations of the disclosed subject matter are possible. Therefore, the disclosed subject matter is intended to include all such changes, modifications, and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent the term "comprising" is used in the detailed description or in the claims, the term is intended to be inclusive in a manner similar to the term "comprising" as interpreted when "comprising" is used as a transitional word in a claim.
Claims
1. A device for device connection, comprising: processor; as well as A computer storage medium having computer executable instructions stored thereon, which when executed by the processor, cause the apparatus to: At the first time: providing a globally unique device identifier that uniquely identifies the device to a secure global blockchain database; receiving, from the secure global blockchain database, first cloud-based connection information associated with the globally unique device identifier, the first cloud-based connection information specifying a first cloud-based service to which the device is to connect, wherein the first cloud-based connection information is stored by the secure global blockchain database in one or more first blockchain entries, the one or more first blockchain entries including a device public key of the device; as well as connecting the device to the first cloud-based service specified by the first cloud-based connection information received from the secure global blockchain database: and In the second time: Providing the globally unique device identifier that uniquely identifies the device to the secure global blockchain database: receiving, from the secure global blockchain database, second cloud-based connection information associated with the globally unique device identifier, the second cloud-based connection information specifying a second cloud-based service to which the device is to connect, wherein the second cloud-based connection information is stored by the secure global blockchain database in one or more second blockchain entries, the one or more second blockchain entries including the device public key of the device; as well as Connecting the device to the second cloud-based service specified by the second cloud-based connection information received from the secure global blockchain database.
2. The apparatus of claim 1 , wherein the secure global blockchain database comprises a private blockchain distributed structure.
3. The apparatus of claim 1 , wherein the computer storage medium has stored thereon additional computer executable instructions, which when executed by the processor, cause the apparatus to: The device is authenticated to the secure global blockchain database at the first time and the second time using a device private key corresponding to the device public key.
4. The device of claim 1 , wherein the computer executable instructions are executed at a first time in response to receiving a first electronic message and at a second time in response to receiving a second electronic message, the first electronic message and the second electronic message requesting the device to obtain current connection information from the secure global blockchain database. 5 . The device of claim 1 , wherein the computer-executable instructions are executed at the first time and the second time in response to received user input.
6. The device of claim 1, the computer executable instructions stored on the computer storage medium comprising boot code that executes on the processor in response to powering up the device and causes the device to: At the first power-up of the device: sending the globally unique device identifier to the secure global blockchain database; receiving the first cloud-based connection information from the secure global blockchain database; as well as upon receiving the first cloud-based connection information from the secure global blockchain database, contacting the first cloud-based service; as well as At the second power-up of the device: sending the globally unique device identifier to the secure global blockchain database; receiving the second cloud-based connection information from the secure global blockchain database; and Upon receiving the second cloud-based connection information from the secure global blockchain database, contacting the second cloud-based service.
7. The device of claim 1, the computer executable instructions stored on the computer storage medium comprising boot code that executes on the processor in response to a user input resetting the device and causes the device to: Resetting the device in response to a first user input: sending the globally unique device identifier to the secure global blockchain database; receiving the first cloud-based connection information from the secure global blockchain database; as well as upon receiving the first cloud-based connection information from the secure global blockchain database, contacting the first cloud-based service; as well as Resetting the device in response to a second user input: sending the globally unique device identifier to the secure global blockchain database; receiving the second cloud-based connection information from the secure global blockchain database; and Upon receiving the second cloud-based connection information from the secure global blockchain database, contacting the second cloud-based service.
8. The device of claim 1, the computer executable instructions stored on the computer storage medium comprising boot code that is periodically executed on the processor and causes the device to: For the first regular execution of the boot code: sending the globally unique device identifier to the secure global blockchain database; receiving the first cloud-based connection information from the secure global blockchain database; and upon receiving the first cloud-based connection information from the secure global blockchain database, contacting the first cloud-based service; and For the second regular execution of the boot code: sending the globally unique device identifier to the secure global blockchain database; receiving the second cloud-based connection information from the secure global blockchain database; and Upon receiving the second cloud-based connection information from the secure global blockchain database, contacting the second cloud-based service.
9. The device of claim 1, the computer executable instructions stored on the computer storage medium comprising boot code that executes on the processor and causes the device to: For the first execution of the boot code: receiving a first challenge from the secure global blockchain database; In response to the first challenge, signing a first message using a device private key of the device; submitting the signed first message to the secure global blockchain database; receiving, in response to authentication of the signed first message, the first cloud-based connection information from the secure global blockchain database; as well as upon receiving the first cloud-based connection information from the secure global blockchain database, contacting the first cloud-based service; as well as For the second execution of the boot code: receiving a second challenge from the secure global blockchain database; In response to the second challenge, signing a second message using the device private key; submitting the signed second message to the secure global blockchain database; receiving, in response to authentication of the signed second message, the second cloud-based connection information from the secure global blockchain database; as well as Upon receiving the second cloud-based connection information from the secure global blockchain database, contacting the second cloud-based service.
10. A method for device connection, comprising: Obtaining a globally unique identifier that uniquely identifies the device; Obtaining a public key / private key pair for the device, the public key / private key pair comprising a device private key and a device public key; creating, at a first time, one or more first blockchain entries in a secure global blockchain database, the one or more first blockchain entries comprising the globally unique identifier that uniquely identifies the device, the device public key, and first cloud-based connection information for the device, wherein the first cloud-based connection information identifies a first cloud-based endpoint to which the device is designated to connect when subsequently accessing the secure global blockchain database to obtain the first cloud-based connection information; as well as At a second time after the first time, one or more second blockchain entries are created in the secure global blockchain database, the one or more second blockchain entries including the globally unique identifier that uniquely identifies the device, the device public key, and second cloud-based connection information for the device, wherein the second cloud-based connection information identifies a second cloud-based endpoint different from the first cloud-based endpoint, the device being designated to connect to the second cloud-based endpoint when the secure global blockchain database is subsequently accessed to obtain the second cloud-based connection information.
11. The method according to claim 10, further comprising: The one or more first blockchain entries and the one or more second blockchain entries are signed using an owner private key.
12. The method according to claim 10, further comprising: executing boot code stored on the device, wherein the boot code causes the device to: At the first power-up of the device: sending the globally unique identifier to the secure global blockchain database; receiving the first cloud-based connection information from the secure global blockchain database; as well as upon receiving the first cloud-based connection information from the secure global blockchain database, contacting the first cloud-based endpoint; as well as At the second power-up of the device: sending the globally unique identifier to the secure global blockchain database; receiving the second cloud-based connection information from the secure global blockchain database; and Upon receiving the second cloud-based connection information from the secure global blockchain database, contacting the second cloud-based endpoint.
13. The method according to claim 10, further comprising: executing boot code stored on a device, wherein the boot code causes the device to: In response to a first user input resetting the device: sending the globally unique identifier to the secure global blockchain database; receiving the first cloud-based connection information from the secure global blockchain database; as well as upon receiving the first cloud-based connection information from the secure global blockchain database, contacting the first cloud-based endpoint; as well as In response to a second user input resetting the device: sending the globally unique identifier to the secure global blockchain database; receiving the second cloud-based connection information from the secure global blockchain database; and Upon receiving the second cloud-based connection information from the secure global blockchain database, contacting the second cloud-based endpoint.
14. The method according to claim 10, further comprising: executing boot code stored on the device, wherein the boot code causes the device to periodically check for new connection information, and: For the first regular execution of the boot code: sending the globally unique identifier to the secure global blockchain database; receiving the first cloud-based connection information from the secure global blockchain database; and upon receiving the first cloud-based connection information from the secure global blockchain database, contacting the first cloud-based endpoint; as well as For the second regular execution of the boot code: sending the globally unique identifier to the secure global blockchain database; receiving the second cloud-based connection information from the secure global blockchain database; and Upon receiving the second cloud-based connection information from the secure global blockchain database, contacting the second cloud-based endpoint.
15. The method according to claim 10, further comprising: executing boot code stored on the device, wherein the boot code causes the device to: For the first execution of the boot code: receiving a first challenge from the secure global blockchain database; In response to the first challenge, signing a first message using the device private key; submitting the signed first message to the secure global blockchain database; receiving, in response to authentication of the signed first message, the first cloud-based connection information from the secure global blockchain database; as well as upon receiving the first cloud-based connection information from the secure global blockchain database, contacting the first cloud-based endpoint; as well as For the second execution of the boot code: receiving a second challenge from the secure global blockchain database; In response to the second challenge, signing a second message using the device private key; Submitting the signed second message to a secure global blockchain database; receiving, in response to authentication of the signed second message, the second cloud-based connection information from the secure global blockchain database; as well as Upon receiving the second cloud-based connection information from the secure global blockchain database, contacting the second cloud-based endpoint.
16. One or more computer storage media storing computer readable instructions that, when executed, cause a processor to: Obtaining a globally unique identifier that uniquely identifies the device; Obtaining a public key / private key pair for the device, the public key / private key pair comprising a device private key and a device public key; creating, at a first time, one or more first blockchain entries in a secure global blockchain database, the one or more first blockchain entries comprising the device public key and first cloud-based connection information for the device, wherein the first cloud-based connection information identifies a first cloud-based endpoint to which the device is designated to connect when subsequently accessing the secure global blockchain database to obtain the first cloud-based connection information; as well as At a second time after the first time, one or more second blockchain entries are created in the secure global blockchain database, the one or more second blockchain entries including the globally unique identifier that uniquely identifies the device, the device public key, and second cloud-based connection information for the device, wherein the second cloud-based connection information identifies a second cloud-based endpoint different from the first cloud-based endpoint, the device being designated to connect to the second cloud-based endpoint when the secure global blockchain database is subsequently accessed to obtain the second cloud-based connection information.
17. One or more computer storage media according to claim 16, storing further computer readable instructions that when executed cause the processor to: The one or more first blockchain entries and the one or more second blockchain entries in the secure global blockchain database are signed using an owner private key.
18. The one or more computer storage media of claim 16 storing further computer readable instructions that when executed cause the processor to: storing the device private key on the device; and The globally unique identifier is stored on the device.
19. The one or more computer storage media of claim 16, storing additional computer readable instructions that, when executed, cause the processor to: store boot code on the device, wherein the boot code facilitates communication between the device and the secure global blockchain database.
20. The one or more computer storage media of claim 16, wherein the secure global blockchain database comprises a private blockchain distributed structure.
Citation Information
Patent Citations
Method of establishing a trusted identity for an agent device
CN105684482A
Registry apparatus, agent device, application providing apparatus and corresponding methods
CN105684483A
Method and device for reestablishing user database on block chain, equipment and medium
CN108629027A
Method of providing enrollment service for particular certificate on block chain
CN109064174A
Platform attestation and registration for servers
CN109074466A
