Avionics Database Replica Synchronization via Version Source Metadata
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for managing shared databases in avionics systems face challenges in detecting inconsistencies between replicas, especially during connection losses and data link interruptions, and are not optimized for low latency and robustness in embedded systems with limited bandwidth.
Innovation Solution
A method that increments the version number and changes the source name of database elements upon modification, allowing for reliable detection of changes even during data link interruptions, using a message transmission system that includes version numbers and source names to identify parallel modifications and ensure data integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a large quantity of information is transmitted between replicas to ensure consistency detection, then detection reliability improves, but bandwidth consumption increases and latency increases
Solution Approach 1:
The patent extracts only the essential information needed for inconsistency detection from the complete database state. Instead of transmitting all database contents, it transmits only modified elements identified by their identifiers and version numbers, significantly reducing bandwidth consumption while maintaining detection reliability.
Solution Approach 2:
The patent applies partial action by transmitting only the necessary subset of data (modified elements with their metadata) rather than the complete database state. This partial transmission is sufficient for inconsistency detection purposes, avoiding the excessive bandwidth consumption of full data synchronization.
2Measurement precision
If complete data transmission is used to ensure consistency, then detection accuracy improves, but latency increases which is unacceptable for embedded systems
Solution Approach 1:
The patent extracts only the critical metadata (identifier, version number, source name) needed for inconsistency detection, excluding the actual data values from the transmission. This extraction approach maintains detection accuracy while minimizing transmission time and latency.
Solution Approach 2:
The system performs preliminary identification of modified elements before transmission. By pre-processing and identifying only the changed elements with their metadata, the system prepares the minimal necessary data for transmission, reducing latency while maintaining detection accuracy.
3Ease of manufacture
If simple version numbers are used for change detection, then implementation simplicity improves, but reliability deteriorates when parallel modifications occur
Solution Approach 1:
The patent merges the version number with the source name identifier to create a composite metadata structure. This combination allows the system to detect parallel modifications from different sources by comparing both the version number and source name, maintaining implementation simplicity while improving reliability.
Solution Approach 2:
The patent adds another dimension (source name) to the version number metadata. This dimensional extension allows differentiation of parallel modifications from different sources, transforming a single-dimension version check into a two-dimension verification system that detects concurrent changes more reliably.
4Reliability
If frequent synchronization is performed to maintain data integrity, then consistency improves, but computational resource consumption increases
Solution Approach 1:
The patent implements periodic synchronization triggered by modification events rather than continuous synchronization. Each synchronization cycle is initiated only when changes occur, allowing the system to maintain data integrity while minimizing computational resource consumption during idle periods.
Solution Approach 2:
The patent extracts and transmits only the modified elements identified by their identifiers, avoiding transmission of unchanged data. This extraction approach reduces the computational load of processing and comparing data during synchronization while maintaining integrity detection for all relevant changes.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Method of managing a database shared by a plurality of embedded systems (4), each embedded system (4) being implemented in a respective platform (2), each embedded system (4) comprising a replica (6) of the database, and being connected to each other embedded system (4) of the plurality of embedded systems (4) by a data link, each replica (6) comprising a set of elements, each element comprising a value, a version number associated with that value, and a source name associated with that version number, the source name indicating the name of the platform (2) comprising the embedded system (4) generating the value of the element according to said version number, the management method comprising steps of: - modifying the value of at least one element; - incrementing the version number; - changing the source name.