Abstract: A delta file may be assembled for use in updating software on a networked device. The delta file may include at least one manifest, and each manifest may be associated with a subset of files (e.g., replacement and/or upgrade files for the networked device). The subset(s) of files may be selected based on a wide range of criteria. In an example, subsets may be selected based on rules that regulate when files are allowed to change. Subsets may also be defined based on the device associated with the files (e.g., a metrology device or a communications device). Any desired criteria/criterion may be used to define a subset of files. The delta file may be transmitted to the networked device. On the networked device, the subset(s) of files may be verified against data corruption, actions of bad actors, and/or unexpected changes at runtime.

Abstract: A delta file may be assembled for use in updating software on a networked device. The delta file may include at least one manifest, and each manifest may be associated with a subset of files (e.g., replacement and/or upgrade files for the networked device). The subset(s) of files may be selected based on a wide range of criteria. In an example, subsets may be selected based on rules that regulate when files are allowed to change. Subsets may also be defined based on the device associated with the files (e.g., a metrology device or a communications device). Any desired criteria/criterion may be used to define a subset of files. The delta file may be transmitted to the networked device. On the networked device, the subset(s) of files may be verified against data corruption, actions of bad actors, and/or unexpected changes at runtime.

Abstract: A system set of a utility node device, such as a kernel and/or root file system, may be updated by utilizing a multi-system set configuration. For example, the multi-system set configuration may include a first system set that is generally configured to act as an “active” set, a second system set (e.g., “idle” set) that is configured to operate when the first system set is non-operational or in an “idle” state, and a third system set that is configured to operate when the first and second system sets are non-operational. During an update of a system set, an update package may be applied to the second “idle” system set, while the first “active” system set remains operational. The utility node device may comprise a smart utility meter, sensor, control device, transformer, switch, relay, or the like.

Abstract: The techniques described herein implement an operating system that can reliably process time sensitive information in non real-time manner. Thus, the operating system described herein is capable of processing an instance of time sensitive input during a time period after the instance of time sensitive input is received (e.g., at a future point in time). To accomplish this, the techniques timestamp each instance of time sensitive input when it is received at a device. The techniques then store the timestamped instance of time sensitive input in a temporary queue, and make the timestamped instance available to the operating system at a time period after the time period when it is received, as indicated by the timestamp. Additional techniques described herein prioritize the activation of a driver configured to receive the time sensitive information during a boot sequence or a reboot sequence.

Abstract: A system set of a utility node device, such as a kernel and/or root file system, may be updated by utilizing a multi-system set configuration. For example, the multi-system set configuration may include a first system set that is generally configured to act as an “active” set, a second system set (e.g., “idle” set) that is configured to operate when the first system set is non-operational or in an “idle” state, and a third system set that is configured to operate when the first and second system sets are non-operational. During an update of a system set, an update package may be applied to the second “idle” system set, while the first “active” system set remains operational. The utility node device may comprise a smart utility meter, sensor, control device, transformer, switch, relay, or the like.

Abstract: A system set of a utility node device, such as a kernel and/or root file system, may be updated by utilizing a multi-system set configuration. For example, the multi-system set configuration may include a first system set that is generally configured to act as an “active” set, a second system set (e.g., “idle” set) that is configured to operate when the first system set is non-operational or in an “idle” state, and a third system set that is configured to operate when the first and second system sets are non-operational. During an update of a system set, an update package may be applied to the second “idle” system set, while the first “active” system set remains operational. The utility node device may comprise a smart utility meter, sensor, control device, transformer, switch, relay, or the like.

Abstract: Software and/or firmware of a utility node device may be updated by utilizing an update package that includes multiple update items related to different types of the software and/or firmware. The utility node device may selectively install one or more of the multiple update items based on a type of the software and/or firmware that is currently installed on the device. The different types of software and/or firmware may relate to different versions of the software and/or firmware and/or different types of hardware. In some instances, an update item of the update package comprises a delta file that contains differences between different versions of the software and/or firmware. The utility node device may comprise a smart utility meter, sensor, control device, transformer, switch, relay, or the like.

Abstract: A system set of a utility node device, such as a kernel and/or root file system, may be updated by utilizing a multi-system set configuration. For example, the multi-system set configuration may include a first system set that is generally configured to act as an “active” set, a second system set (e.g., “idle” set) that is configured to operate when the first system set is non-operational or in an “idle” state, and a third system set that is configured to operate when the first and second system sets are non-operational. During an update of a system set, an update package may be applied to the second “idle” system set, while the first “active” system set remains operational. The utility node device may comprise a smart utility meter, sensor, control device, transformer, switch, relay, or the like.

Abstract: The techniques described herein implement an operating system that can reliably process time sensitive information in non real-time manner. Thus, the operating system described herein is capable of processing an instance of time sensitive input during a time period after the instance of time sensitive input is received (e.g., at a future point in time). To accomplish this, the techniques timestamp each instance of time sensitive input when it is received at a device. The techniques then store the timestamped instance of time sensitive input in a temporary queue, and make the timestamped instance available to the operating system at a time period after the time period when it is received, as indicated by the timestamp. Additional techniques described herein prioritize the activation of a driver configured to receive the time sensitive information during a boot sequence or a reboot sequence.

Abstract: Software and/or firmware of a utility node device may be updated by utilizing an update package that includes multiple update items related to different types of the software and/or firmware. The utility node device may selectively install one or more of the multiple update items based on a type of the software and/or firmware that is currently installed on the device. The different types of software and/or firmware may relate to different versions of the software and/or firmware and/or different types of hardware. In some instances, an update item of the update package comprises a delta file that contains differences between different versions of the software and/or firmware. The utility node device may comprise a smart utility meter, sensor, control device, transformer, switch, relay, or the like.