Description:Related Application
[0001] This patent application is related to India Patent Application No. 201947022378, filed on 06 June 2019, entitled “THE INTERNET OF THINGS”.

Cross Reference to Related Application
[0002] The present application claims the benefit of the filing date of United States Patent Provisional Application Serial No. 62/441,070, by Ned M. Smith et al., entitled “THE INTERNET OF THINGS,” filed December 30, 2016, and which is incorporated herein by reference.

Technical Field
[0003] The present techniques relate generally to Internet of Things (IoT) devices. More specifically the present techniques relate to devices that can perform remote sensing and actuation functions.

Background
[0004] A current view of the Internet is the connection of clients, such as personal computers, tablets, smart phones, servers, digital photo-frames, and many other types of devices, to publicly-accessible data-centers hosted in server farms. However, this view represents a small portion of the overall usage of the globally-connected network. A very large number of connected resources currently exist, but are not publicly accessible. Examples include corporate networks, private organizational control networks, and monitoring networks spanning the globe, often using peer-to-peer relays for anonymity.
[0005] It has been estimated that the internet of things (IoT) may bring Internet connectivity to more than 15 billion devices by 2020. For organizations, IoT devices may provide opportunities for monitoring, tracking, or controlling other devices and items, including further IoT devices, other home and industrial devices, items in manufacturing and food production chains, and the like. The emergence of IoT networks has served as a catalyst for profound change in the evolution of the Internet. In the future, the Internet is likely to evolve from a primarily human-oriented utility to an infrastructure where humans may eventually be minority actors in an interconnected world of devices.
[0006] In this view, the Internet will become a communications system for devices, and networks of devices, to not only communicate with data centers, but with each other. The devices may form functional networks, or virtual devices, to perform functions, which may dissolve once the function is performed. Challenges exist in enabling reliable, secure, and identifiable devices that can form networks as needed to accomplish tasks.

Brief Description of the Drawings
[0007] Fig. 1 is a drawing of interconnections that may be present in the Internet in accordance with some embodiments.
[0008] Fig. 2 is a drawing of a network topology for a number of internet-of-things (IoT) networks coupled through backbone links to gateways in accordance with some embodiments.
[0009] Fig. 3 is a drawing of a cloud computing network, or cloud, in communication with a number of IoT devices in accordance with some embodiments.
[0010] Fig. 4 is a drawing of a cloud computing network, or cloud, in communication with a mesh network of IoT devices, which may be termed a fog device, operating at the edge of the cloud in accordance with some embodiments.
[0011] Fig. 5 is a schematic drawing showing the formation of a composite object from a number of atomic objects in accordance with some embodiments.
[0012] Fig. 6 is a schematic drawing of the formation of a group object from a collection of atomic objects and composite objects in accordance with some embodiments.
[0013] Fig. 7 is a process flow diagram of an example method for group creation using a collection of objects in accordance with some embodiments.
[0014] Fig. 8 is a block diagram of an example of components that may be present in an IoT device for offloading data in accordance with some embodiments.
[0015] Fig. 9 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to form group objects in accordance with some embodiments.
[0016] Fig. 10 is a schematic drawing showing the use of Enhanced Privacy Identification (EPID) for object type identity in accordance with some embodiments.
[0017] Fig. 11 is a ladder diagram of an example method for dynamic creation of an object type in accordance with some embodiments.
[0018] Fig. 12 is a ladder diagram of an example method for type introspection using recursion in accordance with some embodiments.
[0019] Fig. 13 is a ladder diagram of an example method for recursive type attestation in accordance with some embodiments.
[0020] Fig. 14 is a block diagram of an example of components that may be present in an IoT device for assigning types to composite objects as they are formed in accordance with some embodiments.
[0021] Fig. 15 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to form group objects in accordance with some embodiments.
[0022] Fig. 16 is a schematic drawing of the formation of a coalition group in accordance with some embodiments.
[0023] Fig. 17 is a process flow diagram of an example method for enrolling members in a coalition group in accordance with some embodiments.
[0024] Fig. 18 is a block diagram of an example of components that may be present in an IoT device for creating coalition groups in accordance with some embodiments.
[0025] Fig. 19 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to create coalition groups in accordance with some embodiments.
[0026] Fig. 20 is a schematic diagram of a semi-permissioned distributed ledger transaction in accordance with some embodiments.
[0027] Fig. 21 is a process flow diagram of an example method for performing semi-permissioned transactions in accordance with some embodiments.
[0028] Fig. 22 is a block diagram of an example of components that may be present in an IoT device for creating coalition groups in accordance with some embodiments.
[0029] Fig. 23 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to securely communicate in groups in accordance with some embodiments.
[0030] Fig. 24 is a schematic diagram of the use of a trusted execution environment (TEE) to securely boot a device in an IoT environment in accordance with some embodiments.
[0031] Fig. 25 is a block diagram of a blockchain block holding boot integrity transactions in accordance with some embodiments.
[0032] Fig. 26 is a schematic diagram of the use of a whitelist image collection with a blockchain in accordance with some embodiments.
[0033] Fig. 27 is a drawing of a blockchain block with integrity transactions for whitelist images in accordance with some embodiments.
[0034] Fig. 28 is a process flow diagram of an example method for a secure boot process flow using blockchain roots-of-trust in accordance with some embodiments.
[0035] Fig. 29 is a block diagram of an example of components that may be present in an IoT device for creating coalition groups in accordance with some embodiments.
[0036] Fig. 30 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to securely communicate in groups in accordance with some embodiments.
[0037] Fig. 31 is a schematic drawing illustrating interoperability across public domains, private domains, and public-private domains in accordance with some embodiments.
[0038] Fig. 32 is a schematic drawing of interoperability across a heterogeneous network of wired networks and wireless networks in accordance with some embodiments.
[0039] Fig. 33 is a schematic drawing of an inline routing system connecting two different fog or cloud entities, such as cloud A with cloud B in accordance with some embodiments.
[0040] Fig. 34 is a schematic drawing of in-line routing showing implicit pass-through routing by an IoT device in accordance with some embodiments.
[0041] Fig. 35 is a schematic drawing of an explicit permissioned routing by an IoT device in accordance with some embodiments.
[0042] Fig. 36 is a schematic drawing of an easement layer for in-line routing used for pass through policy control in accordance with some embodiments.
[0043] Fig. 37 is a ladder diagram of an example method for explicit pass-through routing based on permissions in accordance with some embodiments.
[0044] Fig. 38 is a ladder diagram of an example method of for a time limited lease approach for explicit pass-through in accordance with some embodiments.
[0045] Fig. 39 is a block diagram of an example of components that may be present in an IoT device for creating coalition groups in accordance with some embodiments.
[0046] Fig. 40 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to transfer communications between devices through easements in accordance with some embodiments.
[0047] Fig. 41 is a schematic drawing of using a frame structure to carry proof-of-provenance (PoP) information through devices in a network in accordance with some embodiments.
[0048] Fig. 42 is a schematic diagram of a procedure that may be used to create a PoP transit code or key in accordance with some embodiments.
[0049] Fig. 43 is a process flow diagram of an example method for generating a PoP key in accordance with some embodiments.
[0050] Fig. 44 is a process flow diagram of an example method for verifying the PoP keys in a packet in accordance with some embodiments.
[0051] Fig. 45 is a block diagram of an example of components that may be present in an IoT device for tracking proof-of-provenance in packets in accordance with some embodiments.
[0052] Fig. 46 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to transfer communications between devices through easements in accordance with some embodiments.
[0053] Fig. 47 is a schematic drawing of an example of a packet that includes micropayment information in a token bucket in accordance with some embodiments.
[0054] Fig. 48 is a process flow diagram of an example method for using a token bucket to pass micropayments to transmitting systems in accordance with some embodiments.
[0055] Fig. 49 is a block diagram of an example of components that may be present in an IoT device for using token buckets to facilitate payments in accordance with some embodiments.
[0056] Fig. 50 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to transfer communications between devices based on payments from a token bucket in accordance with some embodiments.
[0057] Fig. 51 is a drawing of a heterogeneous network (hetnet) infrastructure, connecting IP domains to non-IP domains at multiple stages in accordance with some embodiments.
[0058] Fig. 52 is a schematic drawing of protocol packing used to package frames from one protocol into another protocol in accordance with some embodiments.
[0059] Fig. 53 is a schematic drawing of protocol packing used to package a Low Power Wide Area Network (LPWAN) protocol frame, such as a LoRaWAN frame inside an IEEE 802.11 (or Wi-Fi®) media access control (MAC) layer frame in accordance with some embodiments.
[0060] Fig. 54 is a process flow diagram of an example method for protocol packing for the transmission of a frame in accordance with some embodiments.
[0061] Fig. 55 is a block diagram of an example of components that may be present in an IoT device to package frames in a first protocol in frames of a different protocol in accordance with some embodiments.
[0062] Fig. 56 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to package frames in a first protocol in frames of a different protocol in accordance with some embodiments.
[0063] Fig. 57 is a drawing of a frame structure that may be used as a payload in a low power wide area (LPWA) frame, such as a LoRaWAN frame in accordance with some embodiments.
[0064] Fig. 58 is a schematic drawing of transmission data payload being fragmented into a number of sub-blocks for sending in accordance with some embodiments.
[0065] Fig. 59 is a schematic drawing of Network Division Multiplexing (NDM)-serial-to-parallel transmission in accordance with some embodiments.
[0066] Fig. 60 is a schematic drawing of the reception of the sub-blocks in accordance with some embodiments.
[0067] Fig. 61 is a schematic drawing of the recombination of the sub-blocks to form the received data payload in accordance with some embodiments.
[0068] Fig. 62 is a process flow diagram of an example method for fragmenting and dispatching a payload over multiple parallel communication channels in accordance with some embodiments.
[0069] Fig. 63 is a process flow diagram of an example method for receiving and recombining packets sent using an NDM technique in accordance with some embodiments.
[0070] Fig. 64 is a block diagram of an example of components that may be present in an IoT device for fragmenting payloads for transmission along multiple parallel paths in accordance with some embodiments.
[0071] Fig. 65 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to fragment and transmit payloads along multiple parallel paths in accordance with some embodiments.
[0072] Fig. 66 is a schematic drawing of an overlay beaconing system in which a beaconing node provides a location message to a nearby IoT device in accordance with some embodiments.
[0073] Fig. 67 is a process flow diagram of an example method for generating a location payload in accordance with some embodiments.
[0074] Fig. 68 is a process flow diagram of an example method for parsing a frame that includes a location payload in accordance with some embodiments.
[0075] Fig. 69 is a block diagram of an example of components that may be present in a beacon node for establishing a beacon node system for sharing location data in accordance with some embodiments.
[0076] Fig. 70 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to send and receive location payloads in accordance with some embodiments.
[0077] Fig. 71 is a schematic drawing of a distributed content-distribution system for heterogeneous networks in accordance with some embodiments.
[0078] Fig. 72 is a process flow diagram of an example method for dispersed content distribution in accordance with some embodiments.
[0079] Fig. 73 is a block diagram of an example of components that may be present in an IoT device for implementing a distributed content-distribution system in accordance with some embodiments.
[0080] Fig. 74 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to implement a distributed content-distribution system in accordance with some embodiments.
[0081] Fig. 75 is a schematic drawing of a wireless memory system in accordance with some embodiments.
[0082] Fig. 76 is another schematic drawing of the wireless memory system in accordance with some embodiments.
[0083] Fig. 77 is a process flow diagram of an example method for fragmenting and storing data in a transmission loop between devices in accordance with some embodiments.
[0084] Fig. 78 is a process flow diagram of an example method for data storage and access using a communications channel for storage in accordance with some embodiments.
[0085] Fig. 79 is a block diagram of an example of components that may be present in an IoT device for storing data in transmission channels in accordance with some embodiments.
[0086] Fig. 80 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to fragment and transmit payloads along multiple parallel paths in accordance with some embodiments.
[0087] Fig. 81 is a drawing of a structure that may be used for dynamic signaling in accordance with some embodiments.
[0088] Fig. 82 is a process flow diagram of an example method for transmission of data using a Zadoff-Chu (ZC) preamble structure in accordance with some embodiments.
[0089] Fig. 83 is a process flow diagram of an example method for receiving data on multiple channels using the ZC shifted sequence in accordance with some embodiments.
[0090] Fig. 84 is a series of plots illustrating the correlation process detailed in in the above equation for each of the sequences given by K in accordance with some embodiments.
[0091] Fig. 85 is a block diagram of an example of components that may be present in an IoT device for using ZC sequences to send data in multiple simultaneous channels in accordance with some embodiments.
[0092] Fig. 86 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to communicate over channels modulate using ZC sequences in accordance with some embodiments.
[0093] Fig. 87 is a schematic drawing of a multi-radio coexistence system in an IoT device in accordance with some embodiments.
[0094] Fig. 88 is a ladder diagram of an example method of control and management of the operation and coexistence of multiple radios in accordance with some embodiments.
[0095] Fig. 89 is a block diagram of an example of components that may be present in an IoT device for using multiple coexisting radios to communicate with other nodes in accordance with some embodiments.
[0096] Fig. 90 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to communicate over channels modulate using ZC sequences in accordance with some embodiments.
[0097] Fig. 91 is a schematic diagram of a service network overlay function across a heterogeneous network in accordance with some embodiments.
[0098] Fig. 92 is a process flow diagram of an example method for handling new requests for a service in accordance with some embodiments.
[0099] Fig. 93 is a process flow diagram of an example method for registering an endpoint, or service component, with an network domain controller (NDC), or other service coordinator in accordance with some embodiments.
[0100] Fig. 94 is a block diagram of an example of components that may be present in an IoT device for coordinating or fulfilling service requests in accordance with some embodiments.
[0101] Fig. 95 is a block diagram of a non-transitory, machine readable medium including code to direct a processor, or processors, to coordinate or fulfill service requests in accordance with some embodiments.
[0102] Fig. 96 is a schematic diagram of the ad-hoc formation of a reverse distributed hash table (DHT) network for IoT services in accordance with some embodiments.
[0103] Fig. 97 is a schematic diagram of a process for tracking which nodes may be used for storing or transmitting file data in accordance with some embodiments.
[0104] Fig. 98 is a process flow diagram of an example method for targeting storage or sending nodes in accordance with some embodiments.
[0105] Fig. 99 is a process flow diagram of an example method for storing or transmitting data using a distributed hash table (DHT) in accordance with some embodiments.
[0106] Fig. 100 is a block diagram of an example of components that may be present in an IoT device for coordinating or fulfilling service requests in accordance with some embodiments.
[0107] Fig. 101 is a block diagram of a non-transitory, machine readable medium including code to direct a processor, or processors, to coordinate or fulfill service requests in accordance with some embodiments.
[0108] Fig. 102 is a schematic diagram of a multi-route communications system depicting three example routes between two endpoints and that may available for potential usage in accordance with some embodiments.
[0109] Fig. 103 is a process flow diagram of an example method for selecting a communication path in accordance with some embodiments.
[0110] Fig. 104 is a block diagram of an example of components that may be present in an IoT device for sending data over multiple communication channels in accordance with some embodiments.
[0111] Fig. 105 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to send data over multiple communication channels in accordance with some embodiments.
[0112] Fig. 106 is a schematic drawing of an IoT gateway for secure communications and translations between domains in accordance with some embodiments.
[0113] Fig. 107 is a process flow diagram of an example method for translating workloads in a secure IoT gateway in accordance with some embodiments.
[0114] Fig. 108 is a block diagram of an example of components that may be present in an IoT gateway for translating workloads between domains in accordance with some embodiments.
[0115] Fig. 109 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to translate a workload between an ingress network and an egress network in accordance with some embodiments.
[0116] Fig. 110 is a schematic diagram of devices that are onboarded by different domains being incorporated by a shared domain created to allow the devices to participate as components of a new domain in accordance with some embodiments.
[0117] Fig. 111 is a schematic diagram of the creation of a shared resource to allow a device to participate across domains in accordance with some embodiments.
[0118] Fig. 112 is a process flow diagram of an example method for establishing a combined IoT domain including shared resources in accordance with some embodiments.
[0119] Fig. 113 is a block diagram of an example of components that may be present in an IoT device for creating shared resources in accordance with some embodiments.
[0120] Fig. 114 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to establish shared resources across domains in accordance with some embodiments.
[0121] Fig. 115 is a ladder diagram showing a stages in a product lifecycle for the implementation of a product tracing system in accordance with some embodiments.
[0122] Fig. 116 is a schematic drawing of using private data stores, wherein a record key may be used to access the traceability records for each stage to in accordance with some embodiments.
[0123] Fig. 117 is a schematic drawing of using a public or common data store in accordance with some embodiments.
[0124] Fig. 118 is a schematic diagram of a process for implementing a traceability system in accordance with some embodiments.
[0125] Fig. 119 is a block diagram of an example of components that may be present in an IoT device for providing traceability records for a product in accordance with some embodiments.
[0126] Fig. 120 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to share resources across domains in accordance with some embodiments.
[0127] Fig. 121(A) is a schematic drawing of the hierarchical policy management system used in many current computer networks in accordance with some embodiments.
[0128] Fig. 121(B) is a schematic drawing of policy management in a peer-to-peer (P2P) network, such as an IoT mesh network in accordance with some embodiments.
[0129] Fig. 122 is a schematic diagram of systems in nodes to implement a distributed policy management system in accordance with some embodiments.
[0130] Fig. 123(A) is a ladder diagram of an example method of a new non-configured node attempting to discover policies on a network, for example, from a peer node in accordance with some embodiments.
[0131] Fig. 123(B) is a ladder diagram of an example method of a new non-configured node discovering policies from a configured node in accordance with some embodiments.
[0132] Fig. 124 is a ladder diagram of an example method of a configured node communicating with a node having an updated policy to update the policies of the configured node in accordance with some embodiments.
[0133] Fig. 125 is a ladder diagram of an example method showing the concatenation of policies obtained from different nodes by the configured node in accordance with some embodiments.
[0134] Fig. 126 is a block diagram of an example of components that may be present in an IoT device for the distributed management of policies in accordance with some embodiments.
[0135] Fig. 127 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to manage policies in an IoT network in cooperation with other IoT devices in accordance with some embodiments.
[0136] Fig. 128 is a drawing of a power plug device that may be used to improve the availability of an IoT device in accordance with some embodiments.
[0137] Fig. 129 is a plot of a global state transition based on self-adaptation for the power plug device in accordance with some embodiments.
[0138] Fig. 130 is a process flow diagram of an example method for using a power plug device to increase the reliability of an IoT device in accordance with some embodiments.
[0139] Fig. 131 is a block diagram of an example of components that may be present in a power plug device for increasing the availability of an IoT device in accordance with some embodiments.
[0140] Fig. 132 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to increase the availability of an IoT device in accordance with some embodiments.
[0141] Fig. 133 is a schematic diagram of a failover mechanism for a failed device in accordance with some embodiments.
[0142] Fig. 134 is a process flow diagram of an example method for implementing a failover mechanism using a trusted reliability engine (TRE) in accordance with some embodiments.
[0143] Fig. 135 is a block diagram of an example of components that may be present in an IoT device for implementing a failover mechanism using a trusted reliability engine in accordance with some embodiments.
[0144] Fig. 136 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to implement a failover mechanism using a trusted reliability engine in accordance with some embodiments.
[0145] Fig. 137 is a schematic diagram of the construction of a key using fractional keys and exchanged between nodes in an IoT network in accordance with some embodiments.
[0146] Fig. 138 is a process flow diagram of an example method for assembling a full key from fractional keys stored in individual nodes in an IoT network in accordance with some embodiments.
[0147] Fig. 139 is a schematic diagram of the assembly of a complete key from fractional keys provided by five nodes A - E in accordance with some embodiments.
[0148] Fig. 140 is a block diagram of an example of components that may be present in an IoT device for assembling multiple fractional keys from different nodes in an IP mesh network into a single complete key in accordance with some embodiments.
[0149] Fig. 141 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to receive fractional keys, assemble the fractional keys into a final key, and use the final key in accordance with some embodiments.
[0150] Fig. 142 is a schematic diagram of a procedure for generating keys on demand for devices on lossy networks in accordance with some embodiments.
[0151] Fig. 143 is a schematic diagram of a key generation method that may be used in the on-demand process for key generation described above, as well as for generating keys in other contexts in accordance with some embodiments.
[0152] Fig. 144 is a process flow diagram of an example method for generating keys in accordance with some embodiments.
[0153] Fig. 145 is a block diagram of an example of components that may be present in an IoT device for generating keys on demand in accordance with some embodiments.
[0154] Fig. 146 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to generate keys on demand in accordance with some embodiments.
[0155] Fig. 147 is a schematic diagram of an entropy multiplexing process for generating a number of seeds that may be used to generate new keys in accordance with some embodiments.
[0156] Fig. 148 is a schematic diagram illustrating a process for generating a location seed tree in accordance with some embodiments.
[0157] Fig. 149 is a process flow diagram of an example method for generating seeds using entropy multiplexing, and using those seeds to generate keys for encrypted communications in accordance with some embodiments.
[0158] Fig. 150 is a block diagram of an example of components that may be present in an IoT device for assembling multiple fractional keys from different nodes in an IP mesh network into a single complete key in accordance with some embodiments.
[0159] Fig. 151 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to use entropy multiplexing to generate a common secret between devices in accordance with some embodiments.
[0160] Fig. 152 is a ladder diagram of an example method for unified key management in an IoT network environment in accordance with some embodiments.
[0161] Fig. 153 is a block diagram of an example of components that may be present in an IoT device for managing keys in a network of IoT mesh devices in accordance with some embodiments.
[0162] Fig. 154 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to manage keys for secure communications in accordance with some embodiments.
[0163] Fig. 155 is a schematic diagram of a process for bootstrap and discovery of a device in accordance with some embodiments.
[0164] Fig.156 is a process flow diagram of an example method for bootstrapping and discovery of devices in accordance with some embodiments.
[0165] Fig. 157 is a schematic diagram of a process for bootstrap, discovery, and lifecycle of devices using smart contract functions in accordance with some embodiments.
[0166] Fig. 158 is a process flow diagram of an example method for bootstrapping, discovery, and lifecycle of devices using a smart contract in accordance with some embodiments.
[0167] Fig. 159 is a block diagram of an example of components that may be present in an IoT device for bootstrap, discovery, and lifecycle management in accordance with some embodiments.
[0168] Fig. 160 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to manage keys for secure communications in accordance with some embodiments.
[0169] Fig. 161 is a schematic diagram of a process using bloom filter hops to discover resources in accordance with some embodiments.
[0170] Fig.162 is a process flow diagram of an example method resource discovery using DHT in accordance with some embodiments.
[0171] Fig. 163 is a block diagram of an example of components that may be present in an IoT device for assembling multiple fractional keys from different nodes in an IP mesh network into a single complete key in accordance with some embodiments.
[0172] Fig. 164 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to use a bloom filter hops method for resource discovery in accordance with some embodiments.
[0173] Fig. 165 is a schematic diagram of an example method for a task definition and commissioning in accordance with some embodiments.
[0174] Fig. 166 is a process flow diagram of an example method for protocol conversion brokering by a protocol conversion broker in accordance with some embodiments.
[0175] Fig. 167 is a block diagram of an example of components that may be present in an IoT device to define tasks and commission nodes in accordance with some embodiments.
[0176] Fig. 168 is a block diagram of a non-transitory, machine readable medium including code to define tasks and commission nodes in accordance with some embodiments.
[0177] Fig. 169 is a process flow diagram of an example method to manage a floating service and value in a digital wallet in accordance with some embodiments.
[0178] Fig. 170 is a schematic diagram of an example floating service data structure to manage a floating service and the options, conditions and terms in accordance with some embodiments.
[0179] Fig. 171 is a process flow diagram of an example method for floating service management in accordance with some embodiments.
[0180] Fig. 172 is a block diagram of an example of components that may be present in an IoT device to manage floating services in accordance with some embodiments.
[0181] Fig. 173 is a block diagram of a non-transitory, machine readable medium including code to manage floating services in accordance with some embodiments.
[0182] Fig. 174 is a schematic diagram showing an example permissions guide negotiation process in accordance with some embodiments.
[0183] Fig. 175 is a process flow diagram of an example method for permissions guide negotiation in accordance with some embodiments.
[0184] Fig. 176 is a schematic diagram of an example data structure to assess and assign a value to a unit of data in accordance with some embodiments.
[0185] Fig. 177 is a block diagram of an example of components that may be present in an IoT device for negotiation with valued data units in accordance with some embodiments.
[0186] Fig. 178 is a block diagram of a non-transitory, machine readable medium including code to define tasks and commission nodes in accordance with some embodiments.
[0187] Fig. 179 is a schematic diagram of an example organization for the decentralized network access proxy to use functions in accordance with some embodiments.
[0188] Fig. 180 is a process flow diagram of an example method for a decentralized network access proxy to use functions in accordance with some embodiments.
[0189] Fig. 181 is a block diagram of an example of components that may be present in an IoT device for negotiation with valued data units in accordance with some embodiments.
[0190] Fig. 182 is a block diagram of a non-transitory, machine readable medium including code to define tasks and commission nodes in accordance with some embodiments.
[0191] Fig. 183 is a schematic diagram of an example organization for a decentralized version of providing authentication, authorization, and accounting with a permissions guide in accordance with some embodiments.
[0192] Fig. 184 is a process flow diagram of an example method for a decentralized version of providing authentication, authorization, and accounting with a permissions guide in accordance with some embodiments.
[0193] Fig. 185 is a block diagram of an example of components that may be present in an IoT device for decentralized authorization, authentication, and accounting with an IoT device in accordance with some embodiments.
[0194] Fig. 186 is a block diagram of a non-transitory, machine readable medium including code for decentralized authorization, authentication, and accounting with an IoT device in accordance with some embodiments.
[0195] Fig. 187 is a schematic diagram of a technique for decentralized authorization, authentication, and accounting on an IoT device using Remote Authentication Dial-In User Service (RADIUS) or a DIAMETER protocol in accordance with some embodiments.
[0196] Fig. 188 is a schematic diagram of an action diagram for the components of Fig. 187 to act through a decentralized RADIUS proxy for authorization, authentication, and accounting on an IoT device in accordance with some embodiments.
[0197] Fig. 189 is a ladder diagram of an example method for the components of Fig. 187 to act through a decentralized API 18706 for authorization, authentication, and accounting on an IoT device in accordance with some embodiments.
[0198] Fig. 190 is a schematic diagram of an action diagram for decentralized authorization, authentication, and accounting on an IoT device in accordance with some embodiments.
[0199] Fig. 191 is a block diagram of an example of components that may be present in an IoT device for decentralized authorization, authentication, and accounting with an IoT device in accordance with some embodiments.
[0200] Fig. 192 is a block diagram of a non-transitory, machine readable medium including code to direct a processor for decentralized authorization, authentication, and accounting with an IoT device in accordance with some embodiments.
[0201] Fig. 193 is a schematic diagram of a process for configuring and operating a consensus network using a native decentralized database in accordance with some embodiments.
[0202] Fig. 194 is a process flow diagram of an example method for joining and operating within a consensus network using a native decentralized database in accordance with some embodiments.
[0203] Fig. 195 is a block diagram of an example of components that may be present in an IoT device for joining and operating a decentralized database in accordance with some embodiments.
[0204] Fig. 196 is a block diagram of a non-transitory, machine readable medium including code to direct a processor for joining and operating a decentralized database in accordance with some embodiments.
[0205] Fig. 197 is a schematic diagram of logical division for access control in an IoT object in accordance with some embodiments.
[0206] Fig. 198 is a schematic diagram of logical divisions between a caller credential and a request for access control in an IoT object in accordance with some embodiments.
[0207] Fig. 199 is a schematic diagram of logical divisions between of an object capability for access control using layers in an IoT object in accordance with some embodiments.
[0208] Fig. 200 is a process flow diagram of an example method for access control in an IoT object in accordance with some embodiments.
[0209] Fig. 201 is a block diagram of an example of components that may be present in an IoT device for access control in an IoT object in accordance with some embodiments.
[0210] Fig. 202 is a block diagram of a non-transitory, machine readable medium 19600 including code to direct a processor for access control in an IoT object in accordance with some embodiments.
[0211] Fig. 203 is a process flow diagram of an example method for use by an IoT device to map resources and requirements of self-describing hardware.
[0212] Fig. 204 is a block diagram of an example of components that may be present in an IoT device to map resources and requirements of self-describing hardware in accordance with some embodiments.
[0213] Fig. 205 is a block diagram of a non-transitory, machine readable medium including instructions that, when executed, direct a processor to map resources and requirements of self-describing hardware in accordance with some embodiments.
[0214] Fig. 206 is a process flow diagram of an example method for use by an IoT device to map resources and requirements of self-describing hardware in accordance with some embodiments.
[0215] Fig. 207 is a block diagram of an example of components that may be present in an IoT device for a calculation tool for self-describing hardware in accordance with some embodiments.
[0216] Fig. 208 is a block diagram of a non-transitory, machine readable medium including instructions that, when executed, direct a processor to map resources and requirements of self-describing hardware in accordance with some embodiments.
[0217] FIG 209 is a process flow diagram of an example method for use by an IoT device to configure signal conditioning circuitry in accordance with some embodiments.
[0218] Fig. 210 is a block diagram of an example of components that may be present in an IoT device to configure signal conditioning circuitry in accordance with some embodiments.
[0219] Fig. 211 is a block diagram of a non-transitory, machine readable medium including instructions that, when executed, direct a processor to configure signal conditioning circuitry in accordance with some embodiments.
[0220] Fig. 212 is a schematic diagram of hierarchical device and network health reporting in accordance with some embodiments.
[0221] Fig. 213 is a schematic diagram of device level bloom filter and shadow filter health reporting in accordance with some embodiments.
[0222] Fig. 214 is a schematic diagram of network level bloom filter reporting of historical intermittent loss of watchdog reporting in accordance with some embodiments.
[0223] Fig. 215 shows a process flow diagram of an example method for use by an IoT device to report health using shadow and bloom filters in accordance with some embodiments.
[0224] Fig. 216 is a block diagram of an example of components that may be present in an IoT device for reporting health of a network and network devices in accordance with some embodiments.
[0225] Fig. 217 is a block diagram of a non-transitory, machine readable medium including code to report health of a network and network devices in accordance with some embodiments.
[0226] Fig. 218 is a schematic diagram of a wireless wide area network (WWAN) where a control channel may be used across each connection in accordance with some embodiments.
[0227] Fig. 219 is a schematic diagram of a map of a physical area broken into zones in accordance with some embodiments.
[0228] Fig. 220 shows a process flow diagram of an example method for use by an IoT device to report geolocation using time difference of arrival in accordance with some embodiments.
[0229] Fig. 221 is a schematic diagram of a network for determining a time difference based on time of arrival information in a heterogeneous network using, in part, zone ID in accordance with some embodiments.
[0230] Fig. 222 is a schematic diagram of an example control channel frame structure packed in an example low power wide area network frame (LPWAN) in accordance with some embodiments.
[0231] Fig. 223 is a block diagram of an example of components that may be present in an IoT device for discovery of resources and geolocation sector identification in accordance with some embodiments.
[0232] Fig. 224 is a block diagram of a non-transitory, machine readable medium including code to report health of a network and network devices in accordance with some embodiments.
[0233] Fig. 225 is a schematic diagram of a conceptual model of data analytics in accordance with some embodiments.
[0234] Fig. 226 shows a process flow diagram of an example method for use by an IoT device to provide data analytics of IoT systems in accordance with some embodiments.
[0235] Fig. 227 is a block diagram of an example of components that may be present in an IoT device to provide data analytics of IoT systems in accordance with some embodiments.
[0236] Fig. 228 is a block diagram of a non-transitory, machine readable medium including code to report health of a network and network devices.
[0237] Fig. 229 shows a process flow diagram of an example method for use by an IoT device in distributed neural network mapping and resource management in accordance with some embodiments.
[0238] Fig. 230 is a schematic diagram for a distributed neural network mapping for resource management in accordance with some embodiments.
[0239] Fig. 231 is a block diagram of an example of components that may be present in an IoT device for distributed neural network mapping and resource management in accordance with some embodiments.
[0240] Fig. 232 is a block diagram of a non-transitory, machine readable medium including code to report health of a network and network devices in accordance with some embodiments.
[0241] Fig. 233 is a schematic diagram of a hierarchy of blockchains associated with levels in a network hierarchy in accordance with some embodiments.
[0242] Fig. 234 is a process flow diagram of an example method for constructing a blockchain hierarchy in accordance with some embodiments.
[0243] Fig. 235 is expanded view of the Merkle trees described with respect to Fig. 233 in accordance with some embodiments.
[0244] Fig. 236 is a process flow diagram of an example method for searching a blockchain hierarchy using Merkle tree indexes in accordance with some embodiments.
[0245] Fig. 237 is a schematic diagram of a cached Merkle tree stored in a cloud server in accordance with some embodiments.
[0246] Fig. 238 shows a schematic diagram of a distributed Merkle tree cache at the IoT network level H1, as described with respect to Fig. 233, in accordance with some embodiments.
[0247] Fig. 239 is a schematic diagram of a technique for maintaining a distributed cache with coherency in accordance with some embodiments.
[0248] Fig. 240 is a process flow diagram of an example method to construct a coherent cache for a hierarchy of blockchains in accordance with some embodiments.
[0249] Fig. 241 is a process flow diagram of an example method to maintain a coherent cache for a hierarchy of blockchains in accordance with some embodiments.
[0250] Fig. 242 is a block diagram of an example of components that may be present in an IoT device for implementing hierarchical blockchains with associated indexes in accordance with some embodiments.
[0251] Fig. 243 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to manage keys for secure communications in accordance with some embodiments.
[0252] Fig. 244 is a schematic diagram of using Pub-Sub routing based on bloom filters in accordance with some embodiments.
[0253] Fig. 245 is a schematic diagram of using a whitelist bloom filter for allowing the distribution of content in accordance with some embodiments.
[0254] Fig. 246 is a schematic diagram of using a blacklist bloom filter for preventing the distribution of content in accordance with some embodiments.
[0255] Fig. 247 is a process flow diagram of an example method for implementing Pub-Sub with blacklist or white list bloom filters for content control in accordance with some embodiments.
[0256] Fig. 248 is a block diagram of an example of components that may be present in an IoT device for implementing a Pub-Sub content distribution system using bloom filters in accordance with some embodiments.
[0257] Fig. 249 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to manage a Pub-Sub system using bloom filters for content distribution in accordance with some embodiments.
[0258] Fig. 250 is a schematic diagram of topic notification with encrypted content in accordance with some embodiments.
[0259] Fig. 251(A) is a schematic diagram of a group of routers receiving notifications of a topic that includes encrypted content in accordance with some embodiments.
[0260] Fig. 251(B) is a schematic diagram of a group of routers warming their caches in anticipation of a subscriber requesting an encrypted topic in accordance with some embodiments.
[0261] Fig. 252 is a process flow diagram of an example method for using key management notification and warm Key caching in accordance with some embodiments.
[0262] Fig. 253 is a block diagram of an example of components that may be present in an IoT device for managing topic notification with encrypted content in accordance with some embodiments.
[0263] Fig. 254 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to manage topic notification with encrypted content in accordance with some embodiments.
[0264] Fig. 255 is a schematic diagram of a subscriber obtaining a topic group key in accordance with some embodiments.
[0265] Fig. 256 is a schematic diagram of a publisher generating a subscription bloom filter for notification of subscribers of available topics in accordance with some embodiments.
[0266] Fig. 257 is a ladder diagram of an example method for topic encryption in accordance with some embodiments.
[0267] Fig. 258 is a schematic diagram of the use of multilevel security labels in a publication-subscribe environment in accordance with some embodiments.
[0268] Fig. 259 is a process flow diagram of an example method for implementing bloom filters to apply multi-level security policies to notification messages in accordance with some embodiments.
[0269] Fig. 260 is a block diagram of an example of components that may be present in an IoT device for managing topic notification with encrypted content in accordance with some embodiments.
[0270] Fig. 261 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to manage topic notification with encrypted content in accordance with some embodiments.
[0271] Fig. 262 is a drawing of an example of a shy robot in accordance with some embodiments.
[0272] Fig. 263 is a block diagram of an example of components that may be present in a shy robot in accordance with some embodiments.
[0273] Fig. 264 is a schematic diagram of the operation of the context engine in accordance with some embodiments.
[0274] Fig. 265 is a schematic diagram of the operation to of a swarm of shy robots in accordance with some embodiments.
[0275] Fig. 266 is a process flow diagram of an example method for the operation of a shy robot in a swarm in accordance with some embodiments.
[0276] Fig. 267 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to manage operations of shy robots in accordance with some embodiments.
[0277] Fig. 268 is a schematic diagram of a use case showing drones as pre-first responder devices to a scene within a jurisdiction in accordance with some embodiments.
[0278] Fig. 269 is a process flow diagram of an example method for performing a joining and registration process associated with the single and multiple jurisdictional control zones in Fig. 268 in accordance with some embodiments.
[0279] Fig. 270 is a schematic diagram of trip planning for an emergency responder (ER), or other entity, to determine a route to a destination in accordance with some embodiments.
[0280] Fig. 271 is a schematic diagram of using emergency management (EM) sub-trees at each waypoint in accordance with some embodiments.
[0281] Fig. 272 is a process flow diagram of an example method for dynamic configuration of a pre-first responder dispatch (PFRD) network at a scene in accordance with some embodiments.
[0282] Fig. 273 is a ladder diagram of an example method for beaconing scene information by a PFRD in accordance with some embodiments.
[0283] Fig. 274 is a block diagram of an example of components that may be present in a PFRD in accordance with some embodiments.
[0284] Fig. 275 is a block diagram of a non-transitory, machine readable medium including code to direct a processor to manage operations of pre-first responder devices in accordance with some embodiments.
[0285] The same numbers are used throughout the disclosure and the figures to reference like components and features. Numbers in the 100 series refer to features originally found in Fig. 1; numbers in the 200 series refer to features originally found in Fig. 2; and so on.

Description of the Embodiments
[0286] The Internet-of-Things (IoT) is a system in which a large number of computing devices are interconnected to each other and to a communications network (e.g., the Internet) to provide a functionality, such as data acquisition and actuation, at very low levels in networks. Low levels indicate devices that may be located at or near the edges of networks, such as the last devices before the networks end. As used herein, an IoT device may include a device performing a function, such as sensing or control, among others, in communication with other IoT devices and a communications network. The IoT device may include an autonomous device or a semiautonomous device configured to perform one or more functions. Often, IoT devices can be limited in memory, size, or functionality, allowing larger numbers to be deployed for a similar cost to a smaller number of larger devices. However, an IoT device may be a smart phone, laptop, tablet, PC, and/or other larger device. Further, an IoT device may be a virtual device, such as an application on a smart phone or other computing device. IoT devices may include IoT gateways, used to couple IoT devices to other IoT devices and to cloud applications, for data storage, process control, and the like.
[0287] Networks of IoT devices may include commercial and home devices, such as water distribution systems, electric power distribution systems, pipeline control systems, plant control systems, light switches, thermostats, locks, cameras, alarms, motion sensors, and the like. The IoT devices may be accessible through a controller, such as computers, servers, and other systems, for example, to control systems or access data. The controller and the IoT devices can be remotely located from one another.
, Claims:1. An apparatus comprising:
at least one memory;
machine-readable instructions; and
processor circuitry to execute the machine-readable instructions to at least:
determine a measurement based on a code object before execution of the code object, the code object to be executed in a boot sequence;
compare the measurement to a trusted measurement on a blockchain; and
execute the code object in a trusted execution environment after a determination that the measurement matches the trusted measurement.