Avionics IMA Software Decoupling via Configuration Tables

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In integrated modular systems, especially in avionics, changes to application messages require extensive rebuilding and re-testing across multiple software development organizations due to the complexity of coordinating message content and format changes, often leading to project delays and errors.

Innovation Solution

A method is introduced to decouple software by generating configuration tables that allow core software in each module to gather parameter data from producer messages and create target messages tailored to consuming applications, isolating consuming applications from changes in producer applications or message formats.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If application messages use a static arrangement with fixed parameter positions, then message format stability is improved, but system adaptability deteriorates when parameter locations need to change

Engineering Contradiction:
Improvemessage format stabilityVSAvoidsystem adaptability
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system segments the message handling functionality into two independent parts: the static message format definition and the dynamic parameter mapping configuration. This allows the message structure to remain stable while the mapping between producer and consumer parameters can be independently configured and changed without affecting the core message format.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mapping mechanism that sits between the producer application and consumer applications. This mapping layer translates parameter references from consumers to the actual producer message structure, allowing changes in either producer or consumer parameters without direct impact on the other side.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If parameter locations in messages are changed to accommodate new requirements, then system adaptability is improved, but the complexity of coordinating changes across multiple applications increases

Engineering Contradiction:
Improveparameter repositioning flexibilityVSAvoidcoordination complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The mapping configuration acts as an intermediary that absorbs the complexity of parameter repositioning. When parameters need to be moved or reorganized in the producer message, only the mapping configuration needs to be updated, not the consumer applications. This intermediary layer isolates the complexity from the rest of the system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system creates a virtual copy of the parameter mapping relationship that is separate from the actual message structure. This mapping copy allows parameter locations to be redefined without physically restructuring the message flow, reducing coordination complexity.

Inventive Principle:
Principle #26Copying

3Reliability

If all consuming applications are updated whenever a producer application changes, then data consistency is improved, but the time and resources required for rebuilding and re-testing increase

Engineering Contradiction:
Improvedata consistencyVSAvoidrebuilding and re-testing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts the parameter mapping logic from the consumer applications themselves and places it in the core software or configuration layer. This extraction means that when producer applications change, only the mapping configuration needs to be updated, not the consumer applications, dramatically reducing rebuilding and re-testing requirements.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The mapping configuration system automatically handles the translation and adaptation when producer changes occur, without requiring manual updates to consumer applications. This self-service mechanism maintains data consistency automatically while minimizing the time and resources needed for system updates.

Inventive Principle:
Principle #25Self-service

4Adaptability or versatility

If the system uses standardized message formats with fixed structures, then interoperability is improved, but the ease of manufacture deteriorates when custom parameter arrangements are needed

Engineering Contradiction:
ImproveinteroperabilityVSAvoidcustomization ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system maintains standardized message formats at the overall structure level for interoperability, while allowing local customization through the mapping configuration for specific parameter arrangements. This local quality approach enables custom parameter mappings without breaking the standardized message framework.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The mapping configuration provides dynamic adaptability within the standardized message format framework. The system can dynamically adjust parameter mappings to accommodate custom arrangements while maintaining the outer standardized structure, enabling both interoperability and ease of customization.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9063800B2Automated method for decoupling avionics application software in an IMA system
Publication Date: 2015.06.23 HONEYWELL INTERNATIONAL INC
  • US9063800B2 patent drawing
  • US9063800B2 patent drawing
  • US9063800B2 patent drawing

AI summary

A method to decouple software in an integrated modular system that employs message-based data exchange is provided. The method includes generating at least one configuration table for use by core software in at least one module in the integrated modular system. The at least one module hosts at least one of a consuming application. The method also includes gathering parameter data from producer messages at the core software in the at least one module based on the generated configuration table, and creating target messages at the core software based on the gathered parameter data. The target messages have a format specific to the consuming application.