Asynchronous Task Updates Between In-Band and Out-of-Band Clients

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing information handling systems face inefficiencies in asynchronous communication between processing unit clients and out-of-band clients, particularly due to proprietary methods and the need for continuous polling, which can lead to resource wastage and inefficiencies in managing tasks like firmware updates.

Innovation Solution

Implementing a system that generates a task object and a task updater object for asynchronous communication between in-band and out-of-band clients, using a management controller to manage task states and update information handling systems, allowing for efficient task management and status updates without continuous polling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If continuous polling is used for status updates, then the out-of-band client can monitor task execution, but system resources are wasted and efficiency decreases

Engineering Contradiction:

Improvetask status informationVSAvoidsystem resources

Core Design Contradiction:

Loss of informationVSLoss of energy

Solution Approach 1:

The system implements event-driven feedback where the in-band client automatically notifies the out-of-band client of task status changes. The management controller generates events when task state changes occur, and these events are transmitted to the out-of-band client, eliminating the need for continuous polling while ensuring real-time status information delivery.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The in-band client autonomously monitors task execution and proactively pushes status updates to the out-of-band client without requiring external requests. This self-service mechanism allows the system to maintain accurate status information while minimizing resource consumption by avoiding continuous active polling.

Inventive Principle:

Principle #25Self-service

2Adaptability or versatility

If proprietary communication methods are used between clients, then each client can implement its own protocol, but incompatibility arises between different client systems

Engineering Contradiction:

Improveclient protocol flexibilityVSAvoidcommunication compatibility

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The management controller serves as an intermediary between the in-band client and out-of-band client, translating and standardizing communication protocols. It receives task execution requests from the out-of-band client, communicates with the in-band client using appropriate protocols, and returns standardized status information, thereby ensuring compatibility between different client systems while maintaining protocol flexibility.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The management controller implements a universal communication interface that can handle multiple client types and protocols. By providing a standardized event notification mechanism that works with different client implementations, the system achieves broad compatibility while allowing each client to maintain its own communication preferences through the unified interface.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Speed

If synchronous communication is used for task management, then real-time status updates are achieved, but the system cannot handle tasks that require processing unit reboot or extended execution

Engineering Contradiction:

Improvestatus update speedVSAvoidtask execution flexibility

Core Design Contradiction:

SpeedVSAdaptability or versatility

Solution Approach 1:

The system dynamically adapts its communication approach based on task requirements. For tasks requiring extended execution or processing unit reboot, the asynchronous event-driven model maintains real-time status notification capability while accommodating varying task durations and execution contexts. The event notification mechanism remains active and responsive regardless of task state changes.

Inventive Principle:

Principle #15Dynamics

4Loss of information

If the out-of-band client polls for task status, then status information can be obtained, but the communication efficiency decreases and resource utilization increases

Engineering Contradiction:

Improvetask status informationVSAvoidcommunication efficiency

Core Design Contradiction:

Loss of informationVSProductivity

Solution Approach 1:

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The event notification mechanism provides continuous status information delivery without interruption or idle polling cycles. The system maintains constant readiness to notify status changes while avoiding wasted communication cycles, ensuring that the out-of-band client receives timely updates only when necessary, thereby maximizing communication efficiency.

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS12632293B2Asynchronous client to client task management

Publication Date: 2026.05.19 DELL PROD LP

AI summary

A system generates a task object and a task updater object upon receipt of a request from an out-of-band client to execute a task on a processing unit via an in-band client, receives a status update from the in-band client upon execution of the task on the processing unit, and maps the task updater object to the task object associated with the task. The system may also update a state of the task object based on the status update of the task updater object, and transmit the state of the task object to the out-of-band client.