Abstract: Systems and methods for margining diagnostics in a firmware framework are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a controller having firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator of a firmware framework; and a plurality of devices coupled to the controller, where each device of the plurality of devices comprises firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to produce nodes coupled to the orchestrator via the firmware framework, and where the orchestrator is configured to: receive a diagnostics policy; and trigger a device-to-device margining operation with respect to the plurality of devices based, at least in part, upon the diagnostics policy.

Abstract: Systems and methods for reboot management in a firmware framework are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include a controller having firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator of a firmware framework; and a plurality of devices coupled to the controller, where each device of the plurality of devices comprises firmware that, upon execution by a corresponding processing core, cause the corresponding processing core to produce nodes coupled to the orchestrator via the firmware framework, and wherein the orchestrator is configured to: receive a notification; and in response to the notification, queue an operation for execution by a selected one of the plurality of devices upon reboot or reset.

Abstract: Systems and methods for Built-in Self-Test (BIST) management in a firmware framework are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a controller having firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator of a firmware framework; and a plurality of devices coupled to the controller, where each device of the plurality of devices comprises firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to instantiate a respective node in the firmware framework, and where the orchestrator is configured to trigger a BIST operation with respect to a selected one of the plurality of devices based, at least in part, upon a platform manifest that identifies BIST capabilities of the plurality of devices and without any involvement by any host Operating System (OS).

Abstract: Systems and methods for branding management in a firmware framework are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a controller, where the controller includes firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator of a firmware framework; and a plurality of devices coupled to the controller, where each device of the plurality of devices comprises firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to produce nodes coupled to the orchestrator via the firmware framework, and where the orchestrator is configured to: receive a branding policy; and transmit, to a consumer based, at least in part, upon the branding policy, at least one of: (a) an indication of a shared memory location where a branding image is stored, or (b) a copy of the branding image.

Abstract: Systems and methods for failure management in a firmware framework are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a controller, where the controller includes firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator of a firmware framework; and a plurality of devices coupled to the controller, where each device of the plurality of devices comprises firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to instantiate a respective node in the firmware framework, and where the orchestrator is configured to trigger an inference operation based, at least in part, upon an error notification.

Abstract: Systems and methods for runtime diagnostics in a firmware framework are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a controller having firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator of a firmware framework; and a plurality of devices coupled to the controller, where each device of the plurality of devices comprises firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to produce nodes coupled to the orchestrator via the firmware framework, and where the orchestrator is configured to: receive a diagnostics policy; and execute a diagnostics operation with respect to one or more of the plurality of devices at runtime to enforce the diagnostics policy.

Abstract: Systems and methods for Best Known Configuration (BKC) of nodes in a firmware framework. In some embodiments, an Information Handling System (IHS) may include a controller, where the controller comprises firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator, and a plurality of devices coupled to the controller, where each device comprises firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to instantiate a node as part of a firmware framework, and where the orchestrator is configured to apply a BKC to the plurality of nodes.

Abstract: Systems and methods for device reset in a firmware framework are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a controller, where the controller includes firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator of a firmware framework; and a plurality of devices coupled to the controller, where each device includes firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to instantiate a respective node, and where a given node is configured to communicate an indication of a reset or re-enumeration capability to the orchestrator without any involvement by any host Operating System (OS).

Abstract: Disclosed methods and systems leverage a multiservice framework to provision a host system with capabilities indicated in a platform capability manifest (PCM). Responsive to detecting an identification of a particular capability as a restricted capability updates of the restricted capability are blocked. The particular capability and a version of the capability may be identified within a restriction manifest, thereby ensuring that the specified version of the capability will not be altered by conventional OS and OEM update services. The restricted capability may be a hardware component of the host and the restriction may prevent updates to a device driver of the component. The restriction manifest may be created by an IT administrator and delivered to the multiservice framework. Exemplary implementations of software services enabling this managed restriction functionality is also disclosed.

Abstract: Systems and methods for firmware updates with health status checks in a firmware framework are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a controller, where the controller includes firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator of a firmware framework; and a plurality of devices coupled to the controller, where each device includes firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to instantiate a respective node, and where a given node is configured to communicate an indication of a health status to the orchestrator without any involvement by any host Operating System (OS).

Abstract: Systems and methods for device management in a firmware framework are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include a controller, where the controller includes firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator of a firmware framework; and a plurality of devices coupled to the controller, where each device includes firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to instantiate a respective node in the firmware framework, and where the orchestrator is configured to provide a device manager for the plurality of devices without any involvement by any host Operating System (OS) of the IHS.

Abstract: Systems and methods for General-Purpose Input/Output (GPIO) management in a firmware framework are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a controller, where the controller includes firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator of a firmware framework; and a plurality of devices coupled to the controller, where each device includes firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to instantiate a respective node in the firmware framework, and where the orchestrator is configured to provide execute a GPIO command without any involvement by any host Operating System (OS).

Abstract: Systems and methods for health orchestration of modular platforms in a firmware framework are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a controller, where the controller includes firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator of a firmware framework; and a first plurality of devices coupled to the controller, where each device of the first plurality of devices includes firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to instantiate a respective node in the firmware framework, where the orchestrator is coupled to a secondary orchestrator instantiated by another controller of a modular board coupled to the IHS, and where the secondary orchestrator is configured to communicate an indication of a health status to the orchestrator without any involvement by any host Operating System (OS) of the IHS.

Abstract: Systems and methods for power monitoring in a firmware framework are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a controller having firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator of a firmware framework; and a plurality of devices coupled to the controller, where each device includes firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to instantiate a respective node, and where the orchestrator is configured to: in response to an indication of a transition of the IHS into a sleep, hibernation, or modern standby mode, send a command to the plurality of devices to enter a selected low-power state; monitor power consumption of each of the plurality of devices; and based at least in part upon the power consumption, identify one or more power offenders, among the plurality of devices.

Abstract: Systems and methods for deploying instances of Artificial Intelligence (AI) models having different levels of complexity in a heterogenous computing platform are described. In an embodiment, an Information Handling System (IHS), may include a heterogeneous computing platform comprising a plurality of devices and a memory having a plurality of sets of firmware instructions that, upon execution by a respective device, enable the respective device to provide a corresponding service, and where at least one of the devices operates as an orchestrator configured to: select an instance of an AI model among a plurality of instances of the AI model based, at least in part, upon context or telemetry data received from at least a subset of the plurality of devices, where each of the plurality of instances of the AI model has a different level of complexity, and instruct a device to execute the selected instance of the AI model.

Abstract: Dependency compliance features for assessing software dependencies in a host information handling system and remediating dependency non-compliance exceptions are disclosed. Disclosed methods and systems obtain a platform capability manifest (PCM) including capability information for each of one or more supported capabilities and identify at least one enabled capability. The enabled capability may correspond to a software service installed and enabled on the host. A dependency compliance of the host is evaluated based, at least in part, on dependency information included in the PCM. If a dependency non-compliance is detected, the enabled capability may leverage the multiservice framework to remediate the applicable service to achieve dependency compliance. Dependency compliance may include version compliance wherein the dependency information may include version criteria for each software library and/or version criteria for the enabled software service.

Abstract: A system and method to prevent passive voice access to the information handling system using a recorded voice includes a microphone to capture buffered acoustical background sounds in a sliding audio buffer and current passive voice access attempt including current acoustical background sounds. A hardware processor executing computer-readable program code of a context gathering module to capture operating conditions of the information handling system and environmental context where the information handling system is deployed, and provide, as input, the sensed operating conditions of the information handling system and environmental context of a contextual environment identification landscape to a contextual environment ML model to generate a context matching score.

Abstract: Disclosed methods obtain, from a cloud licensing server, licensing information for an end user of a host system. The licensing information indicates valid end user licenses for accessing licensable capabilities. The licensing information may be provided to an intelligent installation service (IIS) running in the host operating system (OS). The IIS leverages a multiservice framework installer to provision the host system with capabilities, including licensable capabilities, in accordance with the licensing information. The licensable capabilities may include licensable capabilities pertaining to audio performance capabilities, including hardware and software coders/decoders (codecs), telemetry capabilities, and overclocking capabilities. The IIS may be configured to scan one or more file depositories to determine available software services and scan the host to determine capabilities available to the end user.

Abstract: A first information handling system executing machine readable code instructions of an ad-hoc secured supercomputer orchestration system may comprise a wireless interface adapter to receive from other information handling systems, capacitive sensor measurements indicating that all of the information handling systems are within a threshold distance of each other, a configuration sensor to sense that the first information handling system is open or on top of the other information handling systems, a hardware processor to execute machine readable code instructions to assign the first information handling system as a cluster controlling anchor information handling system, and the wireless interface adapter to distribute and transmit, via secured sideband communication, deep neural network layers for parallel processing at the other information handling systems to balance power, processing, and thermal capacities across the other information handling systems and to receive and aggregate outputs of such parallel pr

Abstract: Disclosed methods retrieve ad hoc configuration information for an enabled capability of a host system. The enabled capability is associated with a component included in a platform capability manifest (PCM) for the host. Prior to receiving the ad hoc configuration, a multiservice installation may have been performed to provision the host with platform capabilities indicated in the PCM. Upon receiving the ad hoc configuration information, the configuration of the enabled capability is modified in accordance with the ad hoc configuration information. The ad hoc configuration information may correspond to a component configuration indicated by a privileged user such as an IT administrator via a remote console communicatively coupled to the host. The component may be a plug and play (PnP) component and modifying the configuration may include modifying settings in a host OS configuration database, e.g., Windows registry, and invoking a PnP device manager to install the component.