Aircraft Software Corruption Detection and Dynamic Reloading

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software corruption in aircraft on-board computers can lead to data loss, malfunction, and high maintenance costs, especially during long flights where exposure to corruption sources increases, and can result in system failures without clear failure signaling.

Innovation Solution

A method for automatically detecting software corruption and reloading non-corrupt versions during authorized operational phases of the aircraft, using a verification code comparison and delaying the reloading process based on aircraft position, speed, engine state, and refueling status to prevent untimely software loading.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software reloading is performed immediately after corruption detection, then system reliability is improved, but aircraft safety may be compromised during critical operational phases

Engineering Contradiction:
Improvesoftware reliabilityVSAvoidsafety risk during critical phases
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent implements dynamic control of software reloading by adjusting the reloading behavior based on the aircraft's operational phase. The system transitions between different reloading strategies: immediate reloading during safe phases (ground, parking, refueling) and delayed reloading during critical phases (takeoff, landing, flight). This dynamic adaptation resolves the contradiction by making the reloading process flexible rather than static, allowing the system to prioritize safety during critical operations while maintaining reliability through timely reloading during safe operations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of reloading timing based on aircraft operational conditions. By monitoring parameters such as aircraft position (ground/air), speed (below/above 80 kts), and operational phase (takeoff, landing, flight, refueling), the system adjusts the reloading decision. This parameter-based control allows the system to automatically select appropriate reloading moments, resolving the contradiction between immediate reliability restoration and safety preservation during critical phases.

Inventive Principle:
Principle #35Parameter changes

2Object-affected harmful factors

If software reloading is delayed until authorized operational phases, then aircraft safety is maintained, but maintenance time increases

Engineering Contradiction:
Improvesafety during critical phasesVSAvoidmaintenance time
Core Design Contradiction:
Object-affected harmful factorsVSLoss of time

Solution Approach 1:

The patent prepares for software reloading in advance by detecting corruption and queuing reloading requests during critical operational phases. The system proactively identifies when reloading will be needed and schedules it for the next appropriate operational phase, rather than waiting passively for maintenance windows. This preliminary preparation reduces actual maintenance downtime by having everything ready to go as soon as safe conditions arise.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent accelerates the reloading process by executing it immediately during safe operational phases (ground, parking, refueling) rather than deferring to scheduled maintenance windows. When conditions permit, the system rushes through the reloading operation without delay, thereby minimizing the total time the aircraft is out of service while still maintaining safety during critical phases.

Inventive Principle:
Principle #21Skipping (Rushing through)

3Reliability

If manual investigation and maintenance procedures are used for software corruption, then thorough problem solving is achieved, but maintenance costs and aircraft downtime increase

Engineering Contradiction:
Improveproblem resolution thoroughnessVSAvoidmaintenance efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements self-service by enabling the on-board computer to automatically detect software corruption, verify the corruption, request reloading, and execute the reloading process without human intervention. The system monitors its own software integrity, identifies issues, and performs corrective actions autonomously during appropriate operational phases. This self-service capability eliminates the need for manual investigation and maintenance procedures, thereby resolving the contradiction between thorough problem solving and maintenance efficiency.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent establishes a feedback loop where the on-board computer continuously monitors software integrity, detects corruption, and triggers automatic reloading. The system provides feedback about the corruption status and reloading progress, enabling closed-loop control. This automated feedback mechanism ensures thorough problem detection and resolution while eliminating manual intervention, thereby improving maintenance efficiency without sacrificing reliability.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8984346B2Method for automatically reloading software and a device for automatically reloading software
Publication Date: 2015.03.17 AIRBUS OPERATIONS (SAS)
  • US8984346B2 patent drawing
  • US8984346B2 patent drawing
  • US8984346B2 patent drawing

AI summary

Method for automatically reloading software characterized in that it comprises: a step of detecting corruption (E101) of at least one part of a software package of an on-board programmable device (10-1, 10-2, 10-n); and, in response to signaling, a step of reloading (E103) a non-corrupt version of the said at least one corrupt part of the software in order to replace the said at least one corrupt part of the software.