Abstract: Apparatus and associated methods relate to dynamically configuring an Internet of Things (IoT) device and a processor interfacing the IoT device. The processor captures a specific one or more of a plurality of deployment configuration templates for the IoT. The IoT device is then configured by the processor based, at least in part, on the one or more of the plurality of deployment configuration templates captured. The processor then deploys software for use by the processor to interface with the IoT device configured. The software deployed is determined based on the one or more of the plurality of deployment configuration templates captured.

Abstract: Apparatus and associated methods relate to delivering firmware to be installed in a plurality of remotely located engine-control computers in an efficient manner. Local-area-network connection is provided to an engine-control computer configuration device (ECC configuration device) via a mobile firmware delivery system. Cellular internet connection is also provided to the ECC configuration device via a mobile firmware delivery system. The ECC configuration device makes a request of the mobile firmware delivery system to download a firmware file. The mobile firmware delivery system downloads the firmware file requested if the firmware file requested is not stored in a cache memory. Instead of downloading the firmware file, the mobile firmware delivery system provides the firmware file stored in the cache memo if it is found to be stored there.

Abstract: An Internet of Things system comprises an IoT hub and a local subsystem with a plurality of subsystem devices. These subsystem devices include an edge hub communicatively coupled to the IoT hub and to each other subsystem device; a requestor module configured to perform a task according to a requestor module schedule; and a scheduler module with a persistent time loop. The scheduler module receives a scheduler request from the requestor module via the edge hub, and based on this scheduler request generates a subsystem schedule that includes the requestor module schedule. The scheduler module transmits at least a part of this subsystem schedule to a persistence layer outside of the local IoT subsystem, via the IoT hub. The scheduler module flags scheduled event occurrences via the time loop and the subsystem schedule, and transmits task-specific triggered messages to the requestor module in response to these event occurrences.

Abstract: An Internet of Things system comprises an IoT hub and a local subsystem with a plurality of subsystem devices. These subsystem devices include an edge hub communicatively coupled to the IoT hub and to each other subsystem device; a requestor module configured to perform a task according to a requestor module schedule; and a scheduler module with a persistent time loop. The scheduler module receives a scheduler request from the requestor module via the edge hub, and based on this scheduler request generates a subsystem schedule that includes the requestor module schedule. The scheduler module transmits at least a part of this subsystem schedule to a persistence layer outside of the local IoT subsystem, via the IoT hub. The scheduler module flags scheduled event occurrences via the time loop and the subsystem schedule, and transmits task-specific triggered messages to the requestor module in response to these event occurrences.

Abstract: Apparatus and associated methods relate to dynamically configuring an Internet of Things (IoT) device and a processor interfacing the IoT device. The processor captures a specific one or more of a plurality of deployment configuration templates for the IoT. The IoT device is then configured by the processor based, at least in part, on the one or more of the plurality of deployment configuration templates captured. The processor then deploys software for use by the processor to interface with the IoT device configured. The software deployed is determined based on the one or more of the plurality of deployment configuration templates captured.