Abstract: The concepts and technologies disclosed herein are directed to policy-based programmable Internet of Things (“IoT”) devices. An apparatus, for example, can include a device that includes an interface through which the device is to be connected to an asset. The asset can include one or more asset sensors. The device can include one or more device sensors, a network module, and a controller that executes instructions that cause the device to perform operations. In particular, the controller can execute instructions to cause the device to receive a device policy that instructs the device to collect device data from the device sensor(s) in accordance with a device ruleset. The device also can receive an asset policy that instructs the device to collect asset data from the asset sensor(s) in accordance with an asset ruleset. The device can collect the device data and the asset data in accordance with the device/asset policies.

Abstract: The concepts and technologies disclosed herein are directed to proximity routing policy enforcement for trans-border Internet of Things (“IoT”) data governance compliance. A network gateway can receive, from a data source device, a device registration message comprising a device registration header. The network gateway can determine, based upon the device registration header and a data governance policy, whether the data source device is permitted to access a data governance zone. In response to determining that the data source device is permitted to access the data governance zone, the network gateway can determine, based upon a further data governance policy, at least one gateway of a plurality of gateways operating in the data governance zone to which the device registration message is to be forwarded. The network gateway can forward the registration message to the at least one gateway so that the at least one gateway is enabled for device operation.

Abstract: The concepts and technologies disclosed herein are directed to time-aware blockchain staged regulatory control of Internet of Things (“IoT”) data. A federation platform can receive a registration request from an enterprise edge platform to register a blockchain identifier for publication of public data on a public blockchain. The federation platform can determine if the registration request contains any restricted data parameters. In response to determining that the registration request does not contain any restricted data parameters, the federation platform can query a security module to obtain an encryption key. The federation platform can receive the encryption key from the security module. The federation platform can store the encryption key in association with the blockchain identifier and an enterprise edge platform ID that uniquely identifies the enterprise edge platform.

Abstract: The concepts and technologies disclosed herein are directed to policy-based programmable Internet of Things (“IoT”) devices. An apparatus, for example, can include a device that includes an interface through which the device is to be connected to an asset. The asset can include one or more asset sensors. The device can include one or more device sensors, a network module, and a controller that executes instructions that cause the device to perform operations. In particular, the controller can execute instructions to cause the device to receive a device policy that instructs the device to collect device data from the device sensor(s) in accordance with a device ruleset. The device also can receive an asset policy that instructs the device to collect asset data from the asset sensor(s) in accordance with an asset ruleset. The device can collect the device data and the asset data in accordance with the device/asset policies.

Abstract: The concepts and technologies disclosed herein are directed to proximity routing policy enforcement for trans-border Internet of Things (“IoT”) data governance compliance. A network gateway can receive, from a data source device, a device registration message comprising a device registration header. The network gateway can determine, based upon the device registration header and a data governance policy, whether the data source device is permitted to access a data governance zone. In response to determining that the data source device is permitted to access the data governance zone, the network gateway can determine, based upon a further data governance policy, at least one gateway of a plurality of gateways operating in the data governance zone to which the device registration message is to be forwarded. The network gateway can forward the registration message to the at least one gateway so that the at least one gateway is enabled for device operation.

Abstract: A data source device (“device”) can generate a plurality of data segments, each of which can include data that is owned by a specific entity. The device can calculate and store a hash for each data segment of the plurality of data segments as part of a message footer of a data message. The device can calculate and store a further hash that includes a combination of the plurality of data segments and the hashes for the plurality of data segments as part of the message footer. The device can encrypt each data segment to create a plurality of encrypted data segments. The device can assemble the data message to include the plurality of encrypted data segments and the message footer. The device can send the data message to a gateway for further processing.

Abstract: The concepts and technologies disclosed herein are directed to time-aware blockchain staged regulatory control of Internet of Things (“IoT”) data. A federation platform can receive a registration request from an enterprise edge platform to register a blockchain identifier for publication of public data on a public blockchain. The federation platform can determine if the registration request contains any restricted data parameters. In response to determining that the registration request does not contain any restricted data parameters, the federation platform can query a security module to obtain an encryption key. The federation platform can receive the encryption key from the security module. The federation platform can store the encryption key in association with the blockchain identifier and an enterprise edge platform ID that uniquely identifies the enterprise edge platform.

Abstract: The concepts and technologies disclosed herein are directed to policy-based programmable Internet of Things (“IoT”) devices. An apparatus, for example, can include a device that includes an interface through which the device is to be connected to an asset. The asset can include one or more asset sensors. The device can include one or more device sensors, a network module, and a controller that executes instructions that cause the device to perform operations. In particular, the controller can execute instructions to cause the device to receive a device policy that instructs the device to collect device data from the device sensor(s) in accordance with a device ruleset. The device also can receive an asset policy that instructs the device to collect asset data from the asset sensor(s) in accordance with an asset ruleset. The device can collect the device data and the asset data in accordance with the device/asset policies.

Abstract: The concepts and technologies disclosed herein are directed to time-aware blockchain staged regulatory control of Internet of Things (“IoT”) data. A federation platform can receive a registration request from an enterprise edge platform to register a blockchain identifier for publication of public data on a public blockchain. The federation platform can determine if the registration request contains any restricted data parameters. In response to determining that the registration request does not contain any restricted data parameters, the federation platform can query a security module to obtain an encryption key. The federation platform can receive the encryption key from the security module. The federation platform can store the encryption key in association with the blockchain identifier and an enterprise edge platform ID that uniquely identifies the enterprise edge platform.

Abstract: A gateway can provision a device serial number. The gateway can generate a private blockchain identifier and a public blockchain identifier for a device. The gateway can create a private mapping between the device serial number and the private blockchain identifier. The gateway can create a public mapping between the device serial number and the public blockchain identifier. The gateway can allocate a private digital currency amount to the private blockchain identifier and a public digital currency amount to the public blockchain identifier. The gateway can provision a private service transaction cost to the public blockchain identifier, a public service transaction cost to the public blockchain identifier, a private service transaction fee to the private blockchain identifier, a public service transaction fee to the public blockchain identifier, and a ruleset for the device. The gateway can register the public blockchain identifier and the private blockchain identifier with a network gateway.

Abstract: The concepts and technologies disclosed herein are directed to proximity routing policy enforcement for trans-border Internet of Things (“IoT”) data governance compliance. A network gateway can receive, from a data source device, a device registration message comprising a device registration header. The network gateway can determine, based upon the device registration header and a data governance policy, whether the data source device is permitted to access a data governance zone. In response to determining that the data source device is permitted to access the data governance zone, the network gateway can determine, based upon a further data governance policy, at least one gateway of a plurality of gateways operating in the data governance zone to which the device registration message is to be forwarded. The network gateway can forward the registration message to the at least one gateway so that the at least one gateway is enabled for device operation.

Abstract: A data source device (“device”) can generate a plurality of data segments, each of which can include data that is owned by a specific entity. The device can calculate and store a hash for each data segment of the plurality of data segments as part of a message footer of a data message. The device can calculate and store a further hash that includes a combination of the plurality of data segments and the hashes for the plurality of data segments as part of the message footer. The device can encrypt each data segment to create a plurality of encrypted data segments. The device can assemble the data message to include the plurality of encrypted data segments and the message footer. The device can send the data message to a gateway for further processing.

Abstract: The concepts and technologies disclosed herein are directed to policy-based programmable Internet of Things (“IoT”) devices. An apparatus, for example, can include a device that includes an interface through which the device is to be connected to an asset. The asset can include one or more asset sensors. The device can include one or more device sensors, a network module, and a controller that executes instructions that cause the device to perform operations. In particular, the controller can execute instructions to cause the device to receive a device policy that instructs the device to collect device data from the device sensor(s) in accordance with a device ruleset. The device also can receive an asset policy that instructs the device to collect asset data from the asset sensor(s) in accordance with an asset ruleset. The device can collect the device data and the asset data in accordance with the device/asset policies.