Generalized Data Messaging for Heterogeneous Endpoint Interfaces

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing electronic systems with heterogeneous components face inflexibility and technological complexity due to the need for custom interfaces between each pair of components, leading to code proliferation and costly recertification for minor changes.

Innovation Solution

Implementing a common interface component for each endpoint that translates between endpoint-specific and generalized messages, allowing communication through a unified interface without requiring changes to compiled code.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If custom interfaces are developed for each pair of heterogeneous components, then communication compatibility between components is achieved, but device complexity and code proliferation increase

Engineering Contradiction:

Improvecommunication compatibilityVSAvoidinterface complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a message bus as an intermediary component that mediates communication between heterogeneous components. Instead of creating custom point-to-point interfaces between each pair of components, all components communicate through the centralized message bus using standardized message formats, thereby reducing interface complexity while maintaining communication compatibility

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The message bus serves as a universal communication infrastructure that handles messaging between any pair of components in the system. This single universal interface replaces multiple specialized custom interfaces, allowing the same message bus to facilitate communication between diverse heterogeneous components without requiring component-specific interface implementations

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If custom interfaces are developed for each pair of components, then communication between heterogeneous components is enabled, but the amount of code and hardware that must be designed and supported proliferates

Engineering Contradiction:

Improvecommunication capabilityVSAvoidcode quantity

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple分散 custom interface implementations into a single centralized message bus component. All communication functionality is consolidated into this one interface, eliminating the need for separate custom interface code for each component pair and significantly reducing the total quantity of code that must be designed, maintained, and supported

Inventive Principle:

Principle #5Merging (Combining)

3Adaptability or versatility

If interface components are changed, then system flexibility and adaptability improve, but recompilation and recertification requirements increase

Engineering Contradiction:

Improveinterface flexibilityVSAvoidrecertification time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The message bus is designed with dynamic configurability, allowing communication protocols, message formats, and component registrations to be modified at runtime without requiring system recompilation. This dynamic architecture enables interface changes to be implemented through configuration updates alone, avoiding time-consuming recertification processes while maintaining system flexibility

Inventive Principle:

Principle #15Dynamics

4Device complexity

If a common interface component is used for all endpoints, then code maintenance and certification are simplified, but the ability to handle endpoint-specific communication nuances may be reduced

Engineering Contradiction:

Improveinterface management complexityVSAvoidendpoint-specific communication capability

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The message bus implements local quality by allowing each endpoint to have customized message serialization and deserialization logic specific to its communication needs, while still using the same centralized message bus infrastructure. This enables endpoint-specific communication nuances to be handled through localized adaptation layers at each endpoint without requiring custom point-to-point interfaces, thus maintaining both simplicity and adaptability

Inventive Principle:

Principle #3Local quality

Data Source

PatentUS12505056B2Communicating between heterogenous endpoints of an electronic system via generalized data messaging

Publication Date: 2025.12.23 TEXTRON SYSTEMS CORP

AI summary

A technique for communicating between multiple endpoints of an electronic system includes providing a common interface component for each endpoint. Each common interface component is configured to translate between endpoint-specific messages of a respective endpoint and generalized messages that are not specific to any endpoint. Using this arrangement, any two endpoints can communicate via generalized messages, by translating endpoint-specific messages of a sender into generalized messages and by translating generalized messages into endpoint-specific messages of a receiver.