Abstract: Systems, apparatus, articles of manufacture (e.g., computer readable media), and methods are disclosed to implement task-oriented communications for networked control systems. Examples disclosed herein are to determine a criticality of a data packet of a data flow, different packets of the data flow having different respective criticalities, the data flow associated with an application. Disclosed examples are also to perform a quality of service (QoS) operation associated with the data packet based on the criticality of the data packet. For example, the QoS operation is to be performed after generation of the data packet and before reception of the data packet by a device that is to implement the application.

Abstract: Techniques are disclosed for the cell/cluster formation of compute nodes and workload and processing resource scheduling. Compute nodes within an environment may be grouped (clustered) together to perform one or more designated workload tasks. The clustered compute nodes may be associated with (or assigned to) a workload cell formed to perform one or more identified task(s).

Abstract: This disclosure describes systems, methods, and devices related to using redundant frames for time-sensitive networking (TSN). A device may identify an Ethernet frame including a redundancy tag and an Internet Protocol (IP) packet; generate, based on the Ethernet frame, a first Wi-Fi frame including the redundancy tag and a sub-network access protocol (SNAP) header after an 802.11 medium access control (MAC) header and prior to the redundancy tag, the first Wi-Fi frame further including a first encapsulation of the IP packet; generate, based on the Ethernet frame, a second Wi-Fi frame including the redundancy tag and the SNAP header after the 802.11 MAC header and prior to the redundancy tag, the second Wi-Fi frame further including a second encapsulation of the IP packet; transmit the first Wi-Fi frame using a first Wi-Fi communication link; and transmit the second Wi-Fi frame using a second Wi-Fi communication link.

Abstract: Systems, apparatuses and methods may provide for technology that detects an initiation of a reset flow in a network edge computing system and determines one or more attributes of one or more long flow instructions during the reset flow, wherein the one or more attributes include a latency of the one or more long flow instructions. Additionally, the one or more attributes may be documented via an interface that is accessible by one or more of an operating system or a hypervisor associated with the network edge computing system.

Abstract: Systems, apparatuses and methods may provide for technology that detects an initiation of a reset flow in a network edge computing system and determines one or more attributes of one or more long flow instructions during the reset flow, wherein the one or more attributes include a latency of the one or more long flow instructions. Additionally, the one or more attributes may be documented via an interface that is accessible by one or more of an operating system or a hypervisor associated with the network edge computing system.

Abstract: Techniques are described for providing processor-based dedicated fixed function hardware to perform runtime integrity measurements for detecting attacks on system supervisory software, such as a hypervisor or native Operating System (OS). The dedicated fixed function hardware is provided with memory addresses of the system supervisory software for monitoring. After obtaining the memory addresses and other information required to facilitate integrity monitoring, the dedicated fixed function hardware activates a lock-out to prevent reception of any additional information, such as information from a corrupted version of the system supervisory software. The dedicated fixed function hardware then automatically performs periodic integrity measurements of the system supervisory software. Upon detection of an integrity failure, the dedicated fixed function hardware uses out-of-band signaling to report that an integrity failure has occurred.

Abstract: Provided are a method, system, and program for interfacing with device hardware supporting a plurality of devices. A device interface driver is initialized to represent the device hardware as a virtual bus to an operating system and to represent to the operating system each device supported in the device hardware as a device attached to the virtual bus. The device hardware is initialized and accessed to determine devices supported by the device hardware. One device object is generated for each determined device supported by the device hardware, wherein each generated device object represents the determined device to the operating system. The determined devices are reported to the operating system, wherein the operating system loads a device driver for each of the reported devices supported by the device hardware.