OS-Independent IPC Message Bus for Application Device Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies face challenges in enabling seamless communication between applications and device hardware across different operating systems and business verticals, leading to time lags, code reuse issues, and limited portability due to tightly coupled third-party APIs and OS-specific requirements.
Innovation Solution
A Self-Service Terminal (SST) implementation using a post office API that allows client applications and device drivers to communicate independently of specific operating systems through message passing, facilitated by post office clients and services that manage IPC transport across different OS processing contexts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If third-party APIs are used for device integration, then application-device communication is enabled, but the applications become tightly coupled to specific OS environments and device configurations
Solution Approach 1:
The patent introduces an OS-independent message bus as an intermediary layer between applications and device drivers. This message bus implements standardized message formats and routing mechanisms that enable communication without direct coupling to specific OS APIs or device configurations, allowing applications to interact with devices through a universal interface.
Solution Approach 2:
The system segments the communication architecture into distinct components: message producers (applications), message consumers (device drivers), and the message bus (intermediary). This segmentation allows each component to operate independently with well-defined interfaces, improving adaptability while maintaining communication functionality.
2Reliability
If OS-specific third-party APIs are implemented, then device support is achieved for that OS, but substantial modifications are required to access devices across different OS platforms
Solution Approach 1:
The message bus implements universal message formats and communication protocols that work across multiple OS platforms. Device drivers and applications communicate through standardized message types (request, response, event, error) that are OS-agnostic, enabling the same code base to port across different operating systems without substantial modifications.
3Ease of operation
If custom proprietary interfaces are created for device driver integration, then application-device sharing is enabled, but code reuse and portability are reduced
Solution Approach 1:
The system uses parameter-based message formats where communication details are conveyed through standardized message parameters rather than custom interface structures. Messages contain fields for message type, payload, routing information, and status, allowing flexible device sharing through parameter configuration rather than interface customization.
Data Source
AI summary
An Inter-Process Communication (IPC) message transport mechanism is provided with an Application Programming Interface (API). Applications use the API to create and register clients, and device drivers for devices use the API to create and register services. The applications and device drivers use their own independent API to pass commands and responses to one another using the clients and services. An IPC message transport manager manages and routes the commands as messages without any restrictions on the format or content of the messages. The messages routed in an OS independent fashion.