Universal Software Bus for Multi-Protocol Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software buses are single transport protocol oriented, requiring additional code and manual coding for each new transport protocol, making them inefficient for bridging various software modules across different systems and networks.
Innovation Solution
A universal software bus, referred to as the Distributed Component Interconnect Framework (DCIF), enables communication across multiple transport protocols without requiring new code, using standardized service contracts and model-driven development to abstract system deployment and manage communication between different software modules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single transport protocol oriented software bus is used, then the system is simple to implement, but it cannot communicate with multiple transport protocols without additional code
Solution Approach 1:
The patent introduces a protocol translation layer as an intermediary component that sits between the single-protocol software bus and multiple external transport protocols. This translator mediates communication by converting messages from various protocols into the native protocol of the software bus, enabling multi-protocol support without modifying the core bus logic or adding complexity to the original simple architecture.
Solution Approach 2:
The software bus is enhanced with universal communication capabilities through the protocol translation layer, which provides multi-functionality by supporting multiple transport protocols (CAN, LIN, Ethernet, wireless) while maintaining the original single-protocol interface. This allows the same bus to serve multiple communication standards without requiring separate bus implementations for each protocol.
2Productivity
If manual coding is used for each bridge software component, then communication between software modules is achieved, but the time and effort to maintain operation increases
Solution Approach 1:
The protocol translation layer implements self-service functionality by automatically discovering available transport protocols and generating the necessary bridge software components without requiring manual coding. The system autonomously configures communication paths and generates implementation code, eliminating the need for developers to manually write and maintain bridge components for each protocol integration.
Solution Approach 2:
The system performs preliminary actions by pre-configuring the protocol translation layer with knowledge of multiple transport protocols before actual communication is needed. This advance preparation includes defining protocol specifications, pre-compiling translation routines, and establishing communication templates, so that when new protocols need to be integrated, the system can quickly adapt without time-consuming manual coding and maintenance.
3Adaptability or versatility
If additional code is written for each new client, then new clients can be incorporated, but the codebase becomes larger and more difficult to maintain
Solution Approach 1:
The protocol translation layer provides universal client integration capability by implementing a standardized interface that works with multiple transport protocols and client types. Instead of writing specific code for each new client or protocol, the translation layer handles protocol-specific details universally, allowing new clients to be integrated by simply configuring the translation layer rather than writing new code, thus maintaining ease of manufacture while improving adaptability.
Data Source
AI summary
Methods and systems are provided for a device for a communications control system. In one example, the device includes a distributed component interconnect framework (DCIF) configured to enable communication between different software modules of a communications network based on already existing code. The DCIF allows simultaneous communication between multiple transport protocols.