Avionics Module Configuration via Integration Zones and Partitions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Integrated Modular Avionics (IMA) systems lack the ability to independently integrate applications due to global constraints and shared resources, preventing coexistence of applications with different temporal, industrial, or confidential requirements.

Innovation Solution

A method for configuring electronic modules that involves obtaining specific configuration parameters to define integration zones and partitions, allowing resource allocation and usage management at multiple levels, enabling independent integration of resource-consuming elements while ensuring compliance with partitioning rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a single integrator manages all resources globally, then resource allocation compliance is ensured, but independent integration of applications with different requirements is prevented

Engineering Contradiction:
ImproveIndependent integration capabilityVSAvoidIntegration management structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent divides the module resources into multiple integration zones at the first level of segmentation, allowing different integrators to independently manage resources within each zone. This segmentation enables applications with different temporal, industrial, or confidential requirements to be integrated independently while maintaining overall resource compliance through the hierarchical structure.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If global resource management is used, then module-wide constraints are satisfied, but applications requiring separation for temporal, industrial or confidential issues cannot coexist

Engineering Contradiction:
ImproveApplication coexistenceVSAvoidResource allocation control
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent implements a nested hierarchical structure where integration zones contain multiple partitions, and each partition contains resource-consuming elements. This nesting allows global resource management to be maintained at the zone level while enabling independent control and separation at the partition level, allowing applications with different requirements to coexist without losing resource allocation control.

Inventive Principle:
Principle #7Nested doll (Nesting)

3Productivity

If resources are shared across all applications, then resource utilization is maximized, but partitioning and qualification of the module cannot be ensured

Engineering Contradiction:
ImproveResource utilizationVSAvoidModule qualification
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies local quality by allowing different integration zones to have different resource allocation strategies and partitioning configurations tailored to their specific requirements. Each zone can optimize resource utilization for its applications while maintaining the necessary partitioning and qualification controls, achieving both high productivity and reliability through localized resource management.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP3839737A1Method for configuring an electronic module of an avionics system
Publication Date: 2021.06.23 THALES SA
  • EP3839737A1 patent drawingFigure 1
  • EP3839737A1 patent drawingFigure 2
  • EP3839737A1 patent drawingFigure 3

AI summary

The present invention relates to a method for configuring an electronic module (16) of an avionics system (10), the method comprising the steps of: a. obtaining a set of configuration parameters specific to the module (16), the set of configuration parameters comprising: i. a first group of configuration parameters defining a first level of segmentation for all the resources (14) of the module (16), the segmentations of the first level being called integration zones, ii. a second group of configuration parameters for each integration zone defining a second level of segmentation for the resources (14) allocated to the integration zone, the segmentations of the second level being called partitions, b. determining a partitioning configuration of the resources (14) of the module (16) according to the groups of configuration parameters obtained, and c.operation of module (16) according to the determined partitioning configuration.