IOT based on block chain

Abstract

A method for user control of one or more devices located within a physical space. The method includes creating a network block in response to a user input, the network block including network identification metadata. The network identification metadata includes a list of one or more devices. The method further includes writing the network block to an account book under the first user profile, linking the network block to a host server, receiving a first request to modify the network block, and modifying the network block. The step of modifying the network block comprises the substeps of adding the network identification metadata, deleting the network identification metadata and changing the network identification metadata. The method also includes receiving a second request to transfer ownership of the network block and linking the network block to a second user profile. Linking the network block to the second user profile transfers ownership of the list of one or more devices.

Description

Related applications

[0001] This application claims priority to provisional patent application number 63 / 457,560, filed April 6, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0002] The embodiments disclosed herein relate to a method for user control of one or more devices located in a physical space. Summary of the Invention

[0003] Modern living and working spaces may include one or more smart devices (e.g., fans, light outlets, televisions, thermostats, etc.) and be controlled via a network. Smart devices can be remotely controlled by external devices (e.g., smartphones, tablets, etc.) that communicate electronically with the network. Smart devices can also be configured to operate based on established user control settings for a specific living or working space. Users can be owners, occupants, and / or tenants of the specific living or working space. Typically, user control of a living or working space changes, and established user control settings remain valid even after such changes. New users may wish to modify or transfer smart devices in their living or working space without reconfiguring each smart device on the network. In some cases, reconfiguring the specifications or settings of each smart device can be difficult and time-consuming for new users. The methods disclosed herein allow for a faster transfer of control of smart devices from established users to new users. For example, control of one or more smart devices within a specific living or working space is transferred to a new user. The new user can access the smart devices without needing to reconfigure each smart device to the network using new user control settings.

[0004] In one aspect, this disclosure provides a method for user control of one or more devices located in a physical space. The method includes creating a network block in response to user input, the network block including network identification metadata, and the network identification metadata including a list of one or more devices located in the physical space. The method also includes writing the network block to a ledger under a first user profile, linking the network block to a host server, receiving a first request to modify the network block, and modifying the network block in response to receiving the first request. Modifying the network block includes at least one of the following: adding network identification metadata to the network block, deleting network identification metadata from the network block, and changing the network identification metadata within the network block. The method also includes receiving a second request to transfer ownership of the network block, and linking the network block to a second user profile in response to receiving the second request. Linking the network block to the second user profile transfers ownership of the list of one or more devices located in the physical space to the second user profile.

[0005] In some respects, the list of one or more devices includes at least one selected from a group consisting of a first group of devices, a second group of devices, and a third group of devices, wherein the first group of devices is different from the second group of devices and the third group of devices, and the second group of devices is different from the third group of devices.

[0006] In some respects, the first set of devices includes first identity metadata, the second set of devices includes second identity metadata, and the third set of devices includes third identity metadata.

[0007] In some respects, linking network blocks to a second user profile transfers ownership of the first group of devices, the second group of devices, and the third group of devices to the second user profile.

[0008] In some respects, writing network blocks into the ledger involves storing network blocks in a blockchain.

[0009] In some respects, the list of one or more devices includes smart home devices.

[0010] In some aspects, the method includes receiving a third request to create a first user profile, creating the first user profile based on the third request, receiving a fourth request to create a second user profile, and creating the second user profile based on the fourth request. The third request is made by a different user than the user making the fourth request.

[0011] In another aspect, this disclosure provides a method for modifying user controls for one or more devices located in a physical space. The method includes creating a network block in response to user input, the network block including network identification metadata, and the network identification metadata including a list of one or more devices located in the physical space. The method also includes writing the network block to a ledger under a first user profile, linking the network block to a host server, receiving a request to modify the network block, and modifying the network block in response to receiving the request to modify the network block.

[0012] In some respects, the list of one or more devices includes at least one selected from a group consisting of a first group of devices, a second group of devices, and a third group of devices, wherein the first group of devices is different from the second group of devices and the third group of devices, and the second group of devices is different from the third group of devices.

[0013] In some respects, the first set of devices includes first identity metadata, the second set of devices includes second identity metadata, and the third set of devices includes third identity metadata.

[0014] In some respects, modifying a network block involves adding network identification metadata to the network block based on a received request to modify the network block.

[0015] In some respects, modifying a network block includes deleting network identifier metadata from the network block based on a received request to modify the network block.

[0016] In some respects, modifying a network block involves changing the network identifier metadata within the network block based on a received request to modify the network block.

[0017] In another aspect, this disclosure provides a method for tracking user control of one or more devices located in a physical space. The method includes creating a network block in response to user input, the network block including network identification metadata, and the network identification metadata including a list of one or more devices located in the physical space. The method also includes writing the network block to a ledger under a first user profile, linking the network block to a host server, receiving a first request for transferring ownership of the network block, and linking the network block to a second user profile in response to receiving the first request for transferring ownership.

[0018] In some respects, the list of one or more devices includes at least one selected from a group consisting of a first group of devices, a second group of devices, and a third group of devices, wherein the first group of devices is different from the second group of devices and the third group of devices, and the second group of devices is different from the third group of devices.

[0019] In some respects, the first set of devices includes first identity metadata, the second set of devices includes second identity metadata, and the third set of devices includes third identity metadata.

[0020] In some respects, linking network blocks to a second user profile transfers ownership of the first group of devices, the second group of devices, and the third group of devices to the second user profile.

[0021] In some respects, the method involves storing network blocks in a blockchain.

[0022] In some respects, the list of one or more devices includes devices in physical space.

[0023] In some aspects, the method includes receiving a second request to create a first user profile, creating the first user profile based on the second request, receiving a third request to create a second user profile, and creating the second user profile based on the third request. The second request is made by a different user than the one making the third request.

[0024] Other aspects of this technology will become apparent upon consideration of the detailed description and accompanying drawings. Attached Figure Description

[0025] Figure 1 The physical space including one or more devices according to an embodiment of the present disclosure is shown.

[0026] Figure 2 An embodiment of the present disclosure is shown for use with Figure 1 A user-controlled system for one or more devices.

[0027] Figure 3 An embodiment of the present disclosure is shown for tracking. Figure 1 A user-controlled system for one or more devices.

[0028] Figure 4 An embodiment of the present disclosure is shown for use with Figure 1 A user-controlled system for one or more devices.

[0029] Figure 5 An embodiment of the present disclosure is shown for tracking. Figure 1 A user-controlled system for one or more devices.

[0030] Figure 6 This is a flowchart of a method for user control of one or more devices located in a physical space, according to embodiments of the present disclosure.

[0031] Figure 7 This is a flowchart of a method for modifying user controls of one or more devices located in a physical space, according to embodiments of the present disclosure.

[0032] Figure 8This is a flowchart of a method for tracking user controls of one or more devices located in a physical space, according to embodiments of the present disclosure. Detailed Implementation

[0033] Before explaining any embodiment of this application in detail, it should be understood that the application of this application is not limited to the construction details and component arrangements set forth in the following description or shown in the following figures. For ease of description, some or all example systems presented herein are illustrated with a single example of each of their components. Some examples may not describe or illustrate all components of the system. Other exemplary embodiments may include more or fewer of each of the components shown, may combine some components, or may include additional or alternative components. The application is capable of having other embodiments and can be practiced or performed in various ways. Furthermore, it should be understood that the wording and terminology used herein are for descriptive purposes only and should not be considered limiting. The use of "comprising," "including," or "having," and variations thereof, means to include items listed below and their equivalents, as well as additional items.

[0034] Furthermore, it should be understood that embodiments may include hardware, software, and electronic components or modules, which may be shown and described for the purposes of discussion, with most components implemented solely in hardware. However, those skilled in the art will recognize, based on this detailed description, that in at least one embodiment, the electronic aspects may be implemented in software (e.g., stored on a non-transitory computer-readable medium) executable by one or more electronic processors, such as microprocessors and / or application-specific integrated circuits (“ASICs”). Therefore, it should be noted that embodiments may be implemented using multiple hardware and software-based devices and multiple different structural components. For example, “server,” “computing device,” “controller,” “processor,” etc., described in the specification may include one or more electronic processors, one or more computer-readable medium modules, one or more input / output interfaces, and various connectors (e.g., system buses) connecting these components.

[0035] The methods described herein can be executed by a processor or a collection of processors located locally on a single device, or distributed across various local and remote locations (e.g., in a single device, in the cloud, etc.). Furthermore, all or some of the steps presented in each method can be used. In some embodiments, these steps are performed in a different order.

[0036] Figure 1A physical space 100 including one or more devices is illustrated according to some embodiments. For example, physical space 100 can be any enclosed living or working area capable of accommodating human residents. In the illustrated embodiment, physical space 100 is a smart home, where one or more devices are home appliances. One or more devices can be electrically connected to and / or communicate electronically with a wireless network of physical space 100. In some embodiments, one or more devices can be remotely controlled via a wireless network in response to one or more inputs from external devices.

[0037] like Figure 1 As shown, one or more devices within physical space 100 may include a first group of devices 105 (e.g., one or more smart TVs), a second group of devices 110 (e.g., one or more smart thermostats), a third group of devices 115 (e.g., a smart washing machine and / or dryer), a fourth group of devices 120 (e.g., a smart ceiling fan), a fifth group of devices 125 (e.g., a smart doorbell with video and audio transmission capabilities, such as, but not limited to, a doorbell), and a sixth group of devices (e.g., a smart refrigerator). It should be understood that physical space 100 may include more or fewer groups of devices than shown. For example, one or more devices may also include smart devices such as, but not limited to, water heaters, lamp holders, lighting fixtures, light bulbs, alarm / security systems, garage doors, audio equipment, dishwashers, automatic vacuum cleaners, etc. Although described above as a smart home, in some embodiments, physical space 100 may be other living areas with different human residents or owners over a period of time, such as apartments, condominiums, timeshares, etc. Although described below as having one or more owners, transfers may occur between tenants, residents, users, etc.

[0038] In other embodiments, physical space 100 is a larger enclosed work area, such as a hospital, office building, construction site, grocery store, warehouse, etc. In such embodiments, one or more devices may include smart devices, such as computers, industrial lighting equipment, air conditioning systems, medical devices, manufacturing equipment, etc. Furthermore, when one or more devices within physical space 100 are configured to communicate with a wireless network, the one or more devices may be configured with certain specifications or settings based on the current user (e.g., owner or tenant) of physical space 100. When ownership / occupancy of physical space 100 is transferred to a new user (e.g., a new owner or new tenant), reconfiguring the specifications or settings for each of the one or more devices can be difficult and time-consuming.

[0039] Figure 2 A user-controlled network system 200 for one or more devices within a physical space 100 is shown according to some embodiments. Figure 2The illustrated embodiments can also be viewed as a blockchain ecosystem. In the illustrated embodiments, network system 200 includes a first owner 205 (e.g., the current owner / user / tenant / resident of physical space 100), host organization 210, client 215, multiple distributed nodes 220, ledger 225 (e.g., a blockchain ledger), and host server 230, which itself includes storage for network identification metadata 235. In some embodiments, the first owner 205 accesses host organization 210 and client 215 via web applications and / or mobile applications. In some embodiments, web applications and mobile applications are combined into a single application that performs the functions of both, such as... Figure 2 As shown, a combination of host organization 210 and client 215 is included. Personal devices can be used to access web applications and mobile applications, such as, but not limited to, mobile devices, personal tablets, personal computers, corporate or organizational computers, etc. For example, a personal device may include an electronic processor (e.g., a microprocessor, electronic controller, microcontroller, or other suitable programmable device), memory, a first communication interface, and input / output devices.

[0040] The memory can be a non-transitory computer-readable medium. The memory can include combinations of different types of memory, such as ROM, RAM (e.g., DRAM, SDRAM, etc.), EEPROM, flash memory, hard disk, SD card, or other suitable magnetic, optical, physical, or electronic storage devices. An electronic processor is connected to the memory and executes software instructions that can be stored in the memory's RAM (e.g., during execution), the memory's ROM (e.g., typically permanent), or another non-transitory computer-readable medium (e.g., another type of memory or optical disc). The electronic processor is configured, among other things, to execute instructions related to the operations and methods described herein.

[0041] Host organization 210 may be a third-party institution, company, and / or organization that provides an implementation of client 215 via a web application or mobile application. In some embodiments, client 215 is a blockchain client. Client 215 may be software stored in a web application and / or mobile application for accessing and processing transactions (or, for example, stored in the memory of a personal device or the memory of a remote server). In some embodiments, host organization 210 and client 215 receive user input (e.g., a request) from first owner 205 instructing the creation of a network block. A network block may be a virtualization of one or more devices within physical space 100, having a persistent link to network identifier metadata 235. In response to receiving user input to create a network block, client 215 may create a network block including network identifier metadata 235 by communicating with multiple distributed nodes 220. Multiple distributed nodes 220 may be a collection of electronic processors implementing client 215 within network system 200. For example, multiple distributed nodes 220 may be a public blockchain, where each electronic processor in the collection is independently owned. In some examples, multiple distributed nodes 220 verify the network block at each of the multiple nodes 220. When verifying a network block, each of the multiple nodes 220 stores a copy of the network block for future verification. For example, multiple distributed nodes 220 store network blocks (including network identifier metadata 235) in a shared distributed digital ledger.

[0042] In some embodiments, multiple distributed nodes 220 electronically communicate with a centralized digital storage of multiple network blocks. In the illustrated embodiment, the multiple distributed nodes 220 electronically communicate with a ledger 225. For example, the multiple distributed nodes 220 send their stored transactions (e.g., the creation of network blocks) to the ledger 225 for storage. In some embodiments, once a network block is stored in the ledger 225, the ledger 225 encrypts the network block so that only a first owner 205 can view the network identifier metadata 235. The ledger 225 can grant the first owner 225 authorization to modify the network block, as described below. Furthermore, the ledger 225 securely verifies the creation of network blocks within the network system 200.

[0043] In some embodiments, ledger 225 communicates electronically with host server 230. In some embodiments, host server 230 facilitates interaction between first owner 205 and network block (including network identification metadata 235) via client 215. For example, host server 230 stores an encrypted copy of the network block. First owner 205 can modify the network block by accessing client 215 via a web application or mobile application. In some embodiments, each of one or more devices includes network identification metadata 235. For example, network identification metadata 235 includes information associated with a list of one or more devices within the network block, electrical connections of one or more devices, settings or configurations of one or more devices, and network system 200.

[0044] Figure 3 A user-controlled network system 300 for tracking one or more devices within a physical space 100 is illustrated according to some embodiments. In the illustrated embodiments, the network system 300 may include components similar to those of the network system 200, as referenced above. Figure 2As described above. In some embodiments, network system 300 includes a second owner (user / tenant / resident) 305. For example, the second owner 305 is a subsequent owner / user / tenant / resident of physical space 100 after the first owner 205. The first owner 205 may transfer user control of one or more devices of physical space 100 to the second owner 305. For example, the first owner 205 provides user input (e.g., a transfer request) to client 215, indicating that user control of one or more devices is expected to be transferred 310 to the second owner 305. In some embodiments, the transfer request is provided via a web application and / or a mobile application. In other embodiments, the transfer request may be an electronic transfer of assets, or may be the result of an electronic transfer of assets, such as, but not limited to, bank transfers, bank transactions, loan transfers, etc., of physical space 100. In some embodiments, for example, when user control of physical space 100 is frequently transferred (such as apartments, condominiums, hospital wards, etc.), the transfer request may be provided to the second owner 305 via email from a web application or mobile application. Upon receiving a transfer request, client 215 can process the transfer request as a user control transaction for a network block from first owner 205 to second owner 210. Client 215 can provide the user control transaction to multiple distributed nodes 220. The multiple distributed nodes 220 can verify the network block transaction and store a copy of the network block, wherein second owner 305 has user control over one or more devices. In some embodiments, the multiple distributed nodes 220 send their stored transactions (e.g., the anticipated transfer 310 of the network block) to ledger 225 for storage. In some embodiments, once the network block is stored in ledger 225, ledger 225 encrypts the network block so that only second owner 305 can view the network identity metadata 235. Ledger 225 can grant second owner 225 authorization to modify the network block, as described below. In some embodiments, ledger 225 creates a link between first owner 205 and second owner 305, indicating a transfer of user control over one or more devices to second owner 305.

[0045] Figure 4 A network system 400 for user control of one or more devices within a physical space 100 is illustrated according to some embodiments. In the illustrated embodiments, the network system 400 may include, as referenced above... Figure 2The network system 200 comprises similar components. In some embodiments, the network system 400 includes an authorization server 420. The authorization server 420 may be a private blockchain. For example, the authorization server 420 is a server operated by a third-party institution, company, or organization to verify the creation of network blocks, as described above. When verifying a network block, the authorization server 420 stores a copy of the network block for future verification. For example, the authorization server 420 stores the network block (including network identifier metadata 235) in a private distributed digital ledger. The authorization server 420 can provide greater security for the network block by setting permission levels or identifier authorization, such that only the first owner 205 can modify the network block.

[0046] In some embodiments, the authorization server 420 communicates electronically with a centralized digital storage of multiple network blocks. In the illustrated embodiment, the authorization server 420 communicates electronically with ledger 225. For example, the authorization server 420 sends its stored transactions (e.g., the creation of network blocks) to ledger 225 for storage. In some embodiments, once a network block is stored in ledger 225, ledger 225 encrypts the network block so that only the first owner 205 can view the network identifier metadata 235. Ledger 225 can grant the first owner 225 authorization to modify the network block, as described below. Furthermore, ledger 225 securely verifies the creation of network blocks within network system 200.

[0047] Figure 5 A network system 500 for tracking one or more devices within a physical space 100, according to some embodiments, is illustrated. In the illustrated embodiments, the network system 500 may include components as referenced above. Figure 4The network system 400 comprises components similar to those described above. In some embodiments, the network system 400 includes a second owner 305. In some embodiments, the first owner 205 provides a transfer request to the client 215, indicating that user control of one or more devices is expected to be transferred 310 to the second owner 305. In some embodiments, the transfer request is provided via a web application or a mobile application. In other embodiments, the transfer request may be an electronic transfer of assets, or may be the result of an electronic transfer of assets, such as, but not limited to, bank transfers, bank transactions, loan transfers, etc., of physical space 100. In some embodiments, for example, when user control of physical space 100 is frequently transferred (such as apartments, condominiums, hospital wards, etc.), the transfer request may be provided to the second owner 305 via email from a web application or a mobile application. Upon receiving the transfer request, the client 215 may process the transfer request as a transaction for user control of a network block from the first owner 205 to the second owner 210. The client 215 may provide the transaction for user control to an authorization server 420. The authorization server 420 may verify the transaction for the network block and store a copy of the network block, wherein the second owner 305 has user control over one or more devices. In some embodiments, the authorization server 420 sends its stored transactions (e.g., the anticipated transfer 310 of a network block) to ledger 225 for storage. In some embodiments, once a network block is stored in ledger 225, ledger 225 encrypts the network block so that only the second owner 305 can view the network identifier metadata 235. Ledger 225 may grant the second owner 225 authorization to modify the network block, as described below. In some embodiments, the authorization server 420 grants authorization to the second owner 225. In some embodiments, ledger 225 creates a link between the first owner 205 and the second owner 305, indicating the transfer of user control of one or more devices to the second owner 305.

[0048] Figure 6This is a flowchart illustrating a method 600 for user control of one or more devices located within physical space 100, according to some embodiments. It should be understood that the order of steps disclosed in method 600 can vary. For example, additional steps may be added to the process, and not all steps may be necessary, or steps shown in one order may appear in a second order. Method 600 begins at step 605 when client 215 creates a network block in response to user input instructing a first owner 205 to create a network block. In some embodiments, the network block includes network identification metadata 235. Network identification metadata 235 may include a list of one or more devices located within physical space 100. For example, the list of one or more devices includes a first group of devices 105, a second group of devices 110, and a third group of devices 115. In some embodiments, the first group of devices 105 includes first identification metadata, the second group of devices 110 includes second identification metadata, and the third group of devices 115 includes third identification metadata. The first identification metadata is different from the second and third identification metadata, and the second identification metadata is different from the third identification metadata. It should be understood that the list of one or more devices may include more or fewer devices than the number described above. Then, method 600 proceeds to step 610.

[0049] At step 610, client 215 writes the network block to ledger 225 under a first user profile. For example, client 215 provides the network block to ledger 225 via multiple distributed nodes 220 or an authorization server 420. Ledger 225 may store the network block under a first user profile associated with the first owner 205. In some embodiments, the network block is stored in the blockchain of ledger 225. Then, method 600 proceeds to step 615. At step 615, ledger 225 links the network block to host server 230. For example, ledger 225 provides the network block to host server 230, and host server 230 stores an encrypted copy of the network block for the first owner 205 to access via client 215. Then, method 600 proceeds to step 620.

[0050] At step 620, host server 230 determines whether it has received a first request to modify the network block. For example, first owner 205 provides the first request to modify the network block to host server 230 via client 215. When host server 230 determines that it has not received the first request, method 600 may repeat step 620 until host server 230 receives the first request. When host server 230 determines that it has received the first request, method 600 then proceeds to step 625. At step 625, host server 230 modifies the network block in response to receiving the first request. For example, host server 230 adds a fourth group of devices 120, including fourth identity metadata, to the network block in response to receiving the first request. In other embodiments, host server 230 removes one or more devices from the physical space 100 of the network block. For example, host server 230 removes a third group of devices 115, including third identity metadata, from the network block in response to receiving the first request. In other embodiments, host server 230 changes network identity metadata 235 within the network block in response to receiving the first request. Once a network block is modified by host server 230, the modified network block is provided to ledger 225. Ledger 225 can store a copy of the modified network block. Then, method 600 proceeds to step 630.

[0051] At step 630, host server 230 determines whether it has received a second request for ownership transfer of the network block. For example, first owner 205 provides a second request for ownership transfer of the network block to second owner 305 via client 215. When host server 230 determines that it has not received the second request, method 600 may repeat step 630 until host server 230 receives the second request. When host server 230 determines that it has received the second request, method 600 then proceeds to step 635. At step 635, ledger 225, in response to receiving the second request, links the network block to a second user profile. The second user profile may be associated with second owner 305. For example, ledger 225 receives the second request and links the network block to second owner 305, the second request indicating that user control of a network block including a list of one or more devices is expected to be transferred 310 to second owner 305. In some examples, linking the network block to the second user profile transfers ownership of a list of one or more devices located within physical space 100 to the second user profile (e.g., to second owner 305). For example, ownership of a first group of devices 105 including first identity metadata, a second group of devices 110 including second identity metadata, and a third group of devices 115 including third identity metadata is transferred to a second user profile. In some embodiments, after ledger 225 links a network block to the second user profile, method 600 may return to step 620 to continue determining whether a request to modify the network block has been received.

[0052] In some embodiments, host organization 210 and client 215 receive a third request from first owner 205 via a web application and / or mobile application to create a first user profile. For example, the first user profile is a unique exchange profile such that any action performed by the web application and / or mobile application is associated with the first owner 205 performing the action. Based on the receipt of the third request, the web application and / or mobile application creates the first user profile. The first user profile may include a public and private key pair used by host organization 210 to encrypt all transactions conducted via client 215 and to view network blocks on host server 230. Therefore, only those possessing the required keys can view the contents of transactions and network blocks. Similarly, host organization 210 and client 215 may receive a fourth request from second owner 305 via a web application and / or mobile application to create a second user profile. For example, the second user profile is a unique exchange profile such that any action performed by the web application and / or mobile application is associated with the second owner 305 performing the action. Based on the receipt of the fourth request, the web application and / or mobile application creates the second user profile. The second user profile may include a public and private key pair, used by host organization 210 to encrypt all transactions conducted via client 215, and to view network blocks on host server 230.

[0053] Figure 7 This is a flowchart of a method 700 for modifying user controls of one or more devices located within physical space 100, according to some embodiments. It should be understood that the order of steps disclosed in method 700 can vary. For example, additional steps may be added to the process, and not all steps may be necessary, or steps shown in one order may appear in a second order. Method 700 begins at step 705 when client 215 creates a network block in response to user input instructing a first owner 205 to create a network block. In some embodiments, the network block includes network identification metadata 235. Network identification metadata 235 may include a list of one or more devices located within physical space 100. For example, the list of one or more devices includes a first group of devices 105, a second group of devices 110, and a third group of devices 115. In some embodiments, the first group of devices 105 includes first identification metadata, the second group of devices 110 includes second identification metadata, and the third group of devices 115 includes third identification metadata. The first identification metadata is different from the second and third identification metadata, and the second identification metadata is different from the third identification metadata. It should be understood that the list of one or more devices may include more or fewer devices than the number described above. Then, method 700 proceeds to step 710.

[0054] At step 710, client 215 writes the network block to ledger 225 under a first user profile. For example, client 215 provides the network block to ledger 225 via multiple distributed nodes 220 or an authorization server 420. Ledger 225 may store the network block under a first user profile associated with the first owner 205. In some embodiments, the network block is stored in the blockchain of ledger 225. Then, method 700 proceeds to step 715. At step 715, ledger 225 links the network block to host server 230. For example, ledger 225 provides the network block to host server 230, and host server 230 stores an encrypted copy of the network block for the first owner 205 to access via client 215. Then, method 700 proceeds to step 720.

[0055] At step 720, host server 230 determines whether it has received a first request to modify the network block. For example, first owner 205 provides the first request to modify the network block to host server 230 via client 215. When host server 230 determines that it has not received the first request, method 700 may repeat step 720 until host server 230 receives the first request. When host server 230 determines that it has received the first request, method 700 then proceeds to step 725. At step 725, host server 230 modifies the network block in response to receiving the first request. For example, host server 230 adds a fourth group of devices 120, including fourth identifier metadata, to the network block in response to receiving the first request. In some cases, host server 230 adds network identifier metadata 235 to a list of one or more devices based on receiving the first request. In other embodiments, host server 230 removes one or more devices from the network block within physical space 100. For example, host server 230 removes a third group of devices 115, including third identifier metadata, from the network block in response to receiving the first request. In some embodiments, host server 230 removes network identifier metadata 235 from a list of one or more devices based on a received first request. In other embodiments, host server 230 modifies the network identifier metadata 235 within a network block in response to receiving the first request. Once a network block is modified by host server 230, the modified network block is provided to ledger 225. Ledger 225 may store a copy of the modified network block. In some embodiments, after host server 230 modifies a network block, method 700 may return to step 720 to continue determining whether a request to modify the network block has been received.

[0056] Figure 8This is a flowchart of a method 800 for tracking user control of one or more devices located within physical space 100, according to some embodiments. It should be understood that the order of steps disclosed in method 800 can vary. For example, additional steps may be added to the process, and not all steps may be necessary, or steps shown in one order may appear in a second order. Method 800 begins at step 805 when client 215 creates a network block in response to user input instructing a first owner 205 to create a network block. In some embodiments, the network block includes network identification metadata 235. Network identification metadata 235 may include a list of one or more devices located within physical space 100. For example, the list of one or more devices includes a first group of devices 105, a second group of devices 110, and a third group of devices 115. In some embodiments, the first group of devices 105 includes first identification metadata, the second group of devices 110 includes second identification metadata, and the third group of devices 115 includes third identification metadata. The first identification metadata is different from the second and third identification metadata, and the second identification metadata is different from the third identification metadata. It should be understood that the list of one or more devices may include more or fewer devices than the number described above. Then, method 800 proceeds to step 810.

[0057] At step 810, client 215 writes the network block to ledger 225 under a first user profile. For example, client 215 provides the network block to ledger 225 via multiple distributed nodes 220 or an authorization server 420. Ledger 225 may store the network block under a first user profile associated with the first owner 205. In some embodiments, the network block is stored in the blockchain of ledger 225. Then, method 800 proceeds to step 815. At step 815, ledger 225 links the network block to host server 230. For example, ledger 225 provides the network block to host server 230, and host server 230 stores an encrypted copy of the network block for the first owner 205 to access via client 215. Then, method 800 proceeds to step 820.

[0058] At step 820, host server 230 determines whether it has received a first request for ownership transfer of the network block. For example, first owner 205 provides a first request for ownership transfer of the network block to second owner 305 via client 215. When host server 230 determines that it has not received a second request, method 800 may repeat step 820 until host server 230 receives the second request. When host server 230 determines that it has received the second request, method 800 then proceeds to step 825. At step 825, ledger 225, in response to receiving the first request, links the network block to a second user profile. The second user profile may be associated with second owner 305. For example, ledger 225 receives the first request and links the network block to second owner 305, the first request indicating that user control of a network block including a list of one or more devices is expected to be transferred 310 to second owner 305. In some examples, linking the network block to the second user profile transfers ownership of a list of one or more devices located within physical space 100 to the second user profile (e.g., to second owner 305). For example, ownership of a first group of devices 105 including first identity metadata, a second group of devices 110 including second identity metadata, and a third group of devices 115 including third identity metadata are transferred to a second user profile. In some embodiments, after ledger 225 links the network block to the second user profile, method 800 may return to step 820 to continue determining whether a request for the transfer of ownership of the network block has been received.

[0059] In some embodiments, as described above, host organization 210 and client 215 receive a second request for creating a first user profile from first owner 205 via a web application and / or mobile application. Based on receiving the second request, the web application and / or mobile application creates the first user profile. Similarly, as described above, host organization 210 and client 215 may receive a third request for creating a second user profile from second owner 305 via a web application and / or mobile application. Based on receiving the third request, the web application and / or mobile application creates the second user profile.

[0060] Therefore, this application provides, among other things, a method for user control of one or more devices located in a physical space. Various features and advantages of this application are set forth in the following claims.

Claims

1. A method for user control of one or more devices located in a physical space, the method comprising: A network block is created in response to user input, the network block including network identification metadata, wherein the network identification metadata includes a list of the one or more devices located within the physical space; Write the network block into the ledger under the first user configuration file; Link the network block to the host server; Receive a first request to modify the network block; Modify the network block in response to receiving the first request. Modifying the network block includes selecting at least one from the group consisting of: adding network identifier metadata to the network block, deleting network identifier metadata from the network block, and changing the network identifier metadata within the network block; Receive a second request to transfer ownership of the network block; and In response to receiving the second request, the network block is linked to the second user profile. Linking the network block to the second user profile transfers ownership of the list of one or more devices located in the physical space to the second user profile.

2. The method according to claim 1, wherein, The list of one or more devices includes at least one selected from a group consisting of a first group of devices, a second group of devices, and a third group of devices, wherein the first group of devices is different from the second group of devices and the third group of devices, and the second group of devices is different from the third group of devices.

3. The method according to claim 2, wherein, The first group of devices includes first identification metadata, the second group of devices includes second identification metadata, and the third group of devices includes third identification metadata.

4. The method according to claim 3, wherein, Linking the network block to the second user profile transfers ownership of the first group of devices, the second group of devices, and the third group of devices to the second user profile.

5. The method according to claim 1, wherein, Writing the network block into the ledger includes storing the network block in the blockchain.

6. The method according to claim 1, wherein, The list of one or more devices includes smart home devices.

7. The method according to claim 1, further comprising: Receive a third request to create the first user profile; The first user profile is created based on the third request; Receive a fourth request to create the second user profile; as well as The second user profile is created based on the fourth request. The third request is created by a different user than the fourth request.

8. A method for modifying user controls of one or more devices located in a physical space, the method comprising: A network block is created in response to user input, the network block including network identification metadata, wherein the network identification metadata includes a list of the one or more devices located within the physical space; Write the network block into the ledger under the first user configuration file; Link the network block to the host server; Receive a request to modify the network block; and The network block is modified in response to the received request to modify the network block.

9. The method according to claim 8, wherein, The list of one or more devices includes at least one selected from a group consisting of a first group of devices, a second group of devices, and a third group of devices, wherein the first group of devices is different from the second group of devices and the third group of devices, and the second group of devices is different from the third group of devices.

10. The method according to claim 9, wherein, The first group of devices includes first identification metadata, the second group of devices includes second identification metadata, and the third group of devices includes third identification metadata.

11. The method according to claim 10, wherein, Modifying the network block also includes: Based on the received request to modify the network block, network identifier metadata is added to the network block.

12. The method according to claim 10, wherein, Modifying the network block also includes: Based on the received request to modify the network block, the network identifier metadata is deleted from the network block.

13. The method according to claim 10, wherein, Modifying the network block also includes: Based on the received request to modify the network block, the network identifier metadata within the network block is changed.

14. A method for tracking user controls of one or more devices located in a physical space, the method comprising: A network block is created in response to user input, the network block including network identification metadata, wherein the network identification metadata includes a list of the one or more devices located within the physical space; Write the network block into the ledger under the first user configuration file; Link the network block to the host server; Receive a first request for the transfer of ownership of the network block; and In response to receiving the first request for transfer of ownership, the network block is linked to a second user profile.

15. The method according to claim 14, wherein, The list of one or more devices includes at least one selected from a group consisting of a first group of devices, a second group of devices, and a third group of devices, wherein the first group of devices is different from the second group of devices and the third group of devices, and the second group of devices is different from the third group of devices.

16. The method according to claim 15, wherein, The first group of devices includes first identification metadata, the second group of devices includes second identification metadata, and the third group of devices includes third identification metadata.

17. The method according to claim 16, wherein, Linking the network block to the second user profile transfers ownership of the first group of devices, the second group of devices, and the third group of devices to the second user profile.

18. The method of claim 14, further comprising: The network blocks are stored in the blockchain.

19. The method of claim 14, wherein, The list of one or more devices includes devices in the physical space.

20. The method of claim 14, further comprising: Receive a second request to create the first user profile; The first user configuration file is created based on the second request; Receive a third request to create the second user profile; as well as The second user profile is created based on the third request. The second request was created by a different user than the third request.

Images