Avionics Memory Access Control for ARINC 653 Compliance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current avionics control systems face challenges in dynamically updating memory configurations during initialization without compromising data integrity, leading to increased complexity and non-compliance with safety standards like ARINC 653, as static memory allocation restricts changes to constants and other data types.

Innovation Solution

A method and system for managing memory access in avionics control systems using a partitioning operating system, where each application task is assigned unique memory regions with subregions for data updates, allowing write access during initialization and subsequent protection to prevent overwriting, ensuring compliance with robust partitioning standards.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If static memory allocation is used, then data integrity is maintained, but adaptability and ability to update constants during initialization are reduced

Engineering Contradiction:
Improvedata integrityVSAvoidability to update constants
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic memory access control by transitioning memory regions from a protected state during initialization to a protected state during operation. The memory control device dynamically adjusts access permissions based on the system phase (initialization vs. operation), allowing constants to be updated during initialization while preventing modifications during normal operation to maintain data integrity.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If dynamic memory updates are allowed during initialization, then adaptability is improved, but data integrity and compliance with safety standards may be compromised

Engineering Contradiction:
Improveability to update dataVSAvoiddata integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies preliminary action by establishing memory protection mechanisms before normal operation begins. During the initialization phase, the memory control device permits write access to allow data updates. Once initialization is complete, the system preliminarily configures the memory control device to enforce protection, preventing future modifications and ensuring data integrity for the operational phase.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If memory access protection is enforced, then data integrity is maintained, but complexity of memory configuration increases

Engineering Contradiction:
Improvedata integrityVSAvoidmemory configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The memory control device operates autonomously to manage memory access permissions. It automatically transitions between initialization and operation modes, adjusting protection levels without requiring complex external configuration or intervention. This self-service approach simplifies the overall system configuration while maintaining robust data integrity through automated access control.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP2865164B1Dynamic memory access management
Publication Date: 2019.08.14 SAAB AB
  • EP2865164B1 patent drawingFigure 1~2
  • EP2865164B1 patent drawingFigure 3~4
  • EP2865164B1 patent drawingFigure 5~6

AI summary

The invention pertains to a system, a method and a computer program for managing memory access of an avionics control system having at least one control computer (S1-S4) having at least one memory control device (15).The method comprising assigning a memory access of at least one unique memory region (APPM) of at least one memory unit (4) to each of at least one application task or task set (P1, P2). A further step comprises assigning a memory access of at least one application data update task to at least one subregion of one or more of the at least one unique memory region. Further steps consists of writing at least one data parameter to the at least one subregion and de-activating the assigned memory access of said at least one application data update task.