Avionics Configuration Tables for Post-Certification Context Updates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing avionics electronic systems require new software application versions when context changes, necessitating redesign and recertification, which is inefficient and costly.

Innovation Solution

An avionics system with a bootstrap package and additional configuration files that allow dynamic configuration updates, including primary, secondary, and tertiary resource tables, enabling changes in context without full redesign and recertification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If software applications are configurable at design time by integrating configuration values during generation, then manufacturing precision and reliability are improved, but adaptability deteriorates because new configuration values require new software versions

Engineering Contradiction:

Improveconfiguration control precisionVSAvoidconfiguration adaptability

Core Design Contradiction:

Manufacturing precisionVSAdaptability or versatility

Solution Approach 1:

The configuration data is segmented into two distinct parts: (1) certified configuration values that are integrated into the software application at design time, and (2) additional configuration values stored separately in a data file on the storage medium. This segmentation allows the certified part to maintain precision while the separate part provides adaptability for context changes without requiring new software versions.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A data file serving as an intermediary component is introduced between the software application and the configuration values. This intermediary stores additional configuration values that can be loaded at runtime, acting as a buffer that provides configuration flexibility without modifying the certified software code, thus resolving the contradiction between precision and adaptability.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Manufacturing precision

If new configuration values are integrated during software application generation, then manufacturing precision is improved, but device complexity increases due to multiple software version management

Engineering Contradiction:

Improveconfiguration control precisionVSAvoidsoftware version management complexity

Core Design Contradiction:

Manufacturing precisionVSDevice complexity

Solution Approach 1:

The configuration values are extracted from the software application binary and stored separately in an external data file. This extraction eliminates the need to manage multiple software versions when configuration changes are needed, as only the data file needs to be updated while the certified software application remains unchanged, thus reducing device complexity while maintaining manufacturing precision.

Inventive Principle:

Principle #2Taking out (Extraction)

3Adaptability or versatility

If configuration values are stored in software or hardware memory areas, then adaptability is improved, but manufacturing precision deteriorates due to runtime configuration variations

Engineering Contradiction:

Improveruntime configuration capabilityVSAvoidconfiguration characterization precision

Core Design Contradiction:

Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The configuration values are prepared and validated in advance during the software generation process, with certified configuration values integrated into the application and additional configuration values pre-stored in a structured data file. This preliminary action ensures that all configuration values are characterized and validated before runtime, maintaining manufacturing precision while enabling runtime adaptability through controlled loading.

Inventive Principle:

Principle #10Preliminary action

4Adaptability or versatility

If new versions of software applications are generated for context changes, then adaptability is improved, but productivity decreases due to re-certification requirements

Engineering Contradiction:

Improveconfiguration update capabilityVSAvoidsoftware update efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

Instead of generating new software application versions, the system creates copies of configuration values in a separate data file format. This copying approach allows configuration updates to be made by simply creating new data files with updated values, avoiding the time-consuming process of software regeneration and re-certification, thus improving productivity while maintaining adaptability.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS12613707B2Electronic avionics system with additional configuration file

Publication Date: 2026.04.28 THALES SA

AI summary

Avionics system includes a bootstrap package including system partitions, and a primary configuration table, of a first type with hardware resource configuration values, a boot automaton launching the bootstrap package, at least one secondary configuration table of a second type with configuration values usable by a set of partitions, tertiary system configuration tables for the set of partitions, of a third type with configuration values used by a respective partition, application partitions, each including an avionics application and a tertiary configuration table, of the third type and containing configuration values of resources used by the respective application partition. The boot automaton checks whether an additional configuration file is present, and launches the additional configuration file including at least one configuration table of the first, second or third type, same being used instead of a table of the same type among the primary, secondary, tertiary system and tertiary application tables.