Event Queue Mediator for Embedded Controller Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems with embedded controllers (EC) and super input output (SIO) face complexity and security challenges when handling events, particularly in managing security features and operations, as the source code for these features is often not accessible, leading to potential conflicts and increased complexity when integrated with third-party core firmware (FW).
Innovation Solution
Implementing a generic interface library within the binary library that maintains control over security features and operations, allowing the core FW to extract events from a queue without exposing the source code, thereby simplifying development and enhancing security by limiting access to the source code.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the core FW directly interacts with the binary library to handle security features, then the functionality and control over security operations are improved, but the complexity and potential conflicts increase due to source code accessibility issues
Solution Approach 1:
The patent introduces an event queue as an intermediary mechanism between the core FW and the binary library. The queue stores events generated by the binary library's security operations, allowing the core FW to process these events without directly accessing or understanding the binary library's source code. This mediator approach maintains security control while reducing system complexity and potential conflicts.
Solution Approach 2:
The system is segmented into distinct functional components: the binary library generates security events, the event queue stores and manages these events, and the core FW processes the events. This segmentation allows each component to operate independently with well-defined interfaces, reducing complexity while maintaining reliable security operations.
2Ease of manufacture
If the source code of security features is made accessible to the core FW, then the ease of integration and customization is improved, but the security and control over security operations deteriorate
Solution Approach 1:
The event queue serves as an intermediary that enables easy integration of the binary library with the core FW without exposing the binary library's source code. The queue provides a standardized interface for event exchange, making integration straightforward while maintaining security control by keeping the source code inaccessible.
3Productivity
If the core FW processes events directly from the binary library, then the response time and efficiency are improved, but the complexity of managing security features increases
Solution Approach 1:
The binary library preliminarily processes security operations and generates standardized events before passing them to the core FW. This preliminary action allows the core FW to efficiently process events without dealing with the complexity of security feature management, as the events are already prepared and structured.
Solution Approach 2:
The event queue acts as a mediator that buffers and structures events from the binary library, allowing the core FW to process events at its own pace without direct interaction with the binary library's complex security operations. This maintains efficiency while reducing management complexity.
Data Source
AI summary
The examples include methods and apparatuses to store events in a queue for an EC, Storing events in a queue for an EC can include receiving a message from a core FW of an EC and identifying an event corresponding to the message. Storing events in a queue for an EC can also include accessing a priority associated with the event and adding the event and the priority to a queue to be processed by the EC.