Peripheral Custom Event Registration and Relay Through Unified APIs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing information handling systems face limitations in receiving custom events from peripheral devices due to restrictions imposed by bus protocols, preventing the transmission of non-standardized events such as temperature data from webcams or error codes from keyboards, which hinders effective management and monitoring of peripheral device workspaces.
Innovation Solution
Implementing a unified device application programming interface (API) that allows the information handling system to discover and register for custom event notifications from peripheral devices, enabling the transmission of events beyond standard protocols through callback messages and event triggers, and communicating these events to a cloud orchestrator server for management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If standardized bus protocols are used for peripheral device communication, then device compatibility and stability are improved, but the ability to transmit custom events (such as temperature data or error codes) deteriorates
Solution Approach 1:
The patent introduces an intermediary layer (custom event notification mechanism) between the standardized bus protocol and the information handling system. This intermediary enables custom events to be transmitted by wrapping them in standardized protocol frames, allowing both standardized communication and custom event transmission to coexist without conflict
Solution Approach 2:
The bus protocol is extended to serve multiple functions: it maintains its original standardized communication capability while simultaneously supporting custom event transmission. The protocol structure is designed to accommodate both traditional data transfers and custom event notifications within the same communication framework
2Adaptability or versatility
If custom event transmission is enabled beyond standard protocols, then monitoring and management capabilities are improved, but system complexity increases
Solution Approach 1:
The system is segmented into distinct functional components: event generation modules in peripheral devices, event notification mechanisms, and event processing modules in the information handling system. This segmentation allows custom event transmission to be added as a separate layer without fundamentally redesigning the entire system architecture
Solution Approach 2:
The patent establishes preliminary event registration and callback mechanisms before custom events are transmitted. By pre-configuring event handlers and registration protocols, the system prepares the necessary infrastructure in advance, reducing the complexity burden during actual event transmission operations
Data Source
AI summary
An information handling system node includes a hardware processor, a memory device, a power management unit with a peripheral device node operatively coupled to the information handling system node. The hardware processor may execute computer-readable program code of a custom event and device manageability service sub-agent to discover the peripheral device node operatively coupled to the information handling system node including a unique peripheral device identification (ID), request and receive, via a unified device application programming interface module, peripheral device capabilities and event IDs, where the event IDs describe custom events that are transmittable via any bus protocol from the peripheral device node, and register for custom event notifications with the peripheral device node by sending callback messages to the peripheral device node describing which custom events to receive custom event notifications about and setting custom event triggers that trigger the custom event notifications.