Avionics Computing Platform for Runtime Context Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing avionics software applications configured at design time require regeneration of new versions for changes in execution context, leading to inefficiencies and increased certification needs.
Innovation Solution
A computer platform with an additional configuration file that allows the addition of new configuration values after design, including resource configuration tables, to facilitate changes in execution context while retaining certification benefits.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software applications are configured at design time by integrating configuration values during generation, then control over configuration is improved and certification is facilitated, but changes in execution context require regeneration of new software versions
Solution Approach 1:
The configuration data is segmented into two distinct parts: (1) the software application binary with embedded configuration values for design-time stability and certification, and (2) a separate external configuration file stored in file system memory that contains execution-context-specific parameters. This segmentation allows the software to maintain its certified structure while adapting to different execution contexts by loading appropriate external configuration files at runtime.
Solution Approach 2:
An external configuration file serves as an intermediary between the certified software application and the variable execution context. This intermediary layer allows configuration values to be changed without modifying the core software binary, thus maintaining certification integrity while enabling adaptability to different operational scenarios.
2Adaptability or versatility
If new versions of software applications are regenerated to incorporate new configuration values, then the configuration is updated, but additional certification and technical checks are required
Solution Approach 1:
By separating configuration data from the software binary into external configuration files, the invention allows configuration updates without generating new software versions. This avoids the complex certification and technical check processes that would otherwise be required for each configuration change.
Solution Approach 2:
The invention enables parameter changes (configuration values) to be made externally through configuration files rather than through software compilation and regeneration. This allows parameter modification without triggering the complex certification processes associated with software version changes.
3Adaptability or versatility
If configuration values are retrieved from memory areas during execution, then changes in execution context can be accommodated, but robustness must be added to configuration values and certification becomes more difficult
Solution Approach 1:
External configuration files serve as a controlled intermediary that provides runtime configuration access while maintaining robustness. The files are structured and validated before being used by the software, ensuring configuration reliability without requiring the software itself to be robust against configuration variations.
Solution Approach 2:
Configuration files are prepared and validated in advance before execution, with the boot automaton checking for their presence and integrity. This preliminary action ensures that configuration values are robust and reliable before the software application uses them, avoiding the need to add robustness handling within the application code.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
This computer platform is embedded on board an aircraft, runs a set of application partition(s), hosts an operating system and includes: + resources; + a boot package including a kernel, at least one resource driver, a set of system partition(s) and at least one resource configuration table, each system partition including at least one operating system service, the table or tables being chosen from the group consisting of: a table of a first type containing configuration values for hardware resources, a table of a second type containing configuration values for resources usable by a respective set of partition(s), a table of a third type containing configuration values for resources used by a respective partition, the first, second and third types being distinct from each other, one of the at least one table being of the first type;and + a boot process capable of being executed first following a power-up of the platform and configured to launch the boot package; The boot process checks if an additional configuration file is present in the storage memory, and launches, before the boot package, the additional configuration file including at least one resource configuration table of the first, second or third type, then used in place of a respective table of the same type from among the at least one table of the boot package.;