Centralized storage method and device for airborne multi-relational table database
By adopting a centralized storage method for airborne multi-relational table databases, the database performance and efficiency issues were resolved, achieving efficient data management and consistency maintenance, and improving the response speed and throughput of the airborne system.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- XIAN FLIGHT SELF CONTROL INST OF AVIC
- Filing Date
- 2025-12-24
- Publication Date
- 2026-05-05
AI Technical Summary
In the airborne database, data tables are saved to disk when transactions are not completed, leading to frequent refreshes and reduced performance; when memory space is insufficient, only write time is considered, resulting in reduced response speed and throughput; and the lack of support for multi-table relationships in the single-table structure leads to low efficiency in processing related data.
A centralized storage method using an onboard multi-relational table database is adopted. Through multi-relational table storage units, data mirroring table processing units, and transaction management units, data tables are rationally selected for retention or replacement, reducing disk I/O operations and improving data access locality and overall performance.
Improve database response speed, throughput and performance, ensure data consistency, optimize memory usage efficiency, and meet the high-efficiency requirements of airborne systems.
Smart Images

Figure CN121979893A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of database security management technology in the critical area of airborne safety, and particularly relates to a centralized storage method and device for airborne multi-relation table databases. Background Technology
[0002] Compared to traditional database management methods, airborne databases face more complex data operation scenarios, higher real-time requirements, greater data flexibility, and stricter data security requirements. In airborne environments where safety is paramount, ensuring data consistency among distributed nodes, improving the efficiency of concurrent data management, and ensuring data security and trustworthiness remain significant challenges.
[0003] Existing technologies for onboard database storage have the following problems: First, allowing modified data tables to be saved to disk before a transaction is completed leads to frequent disk refreshes, resulting in reduced database performance. Second, when managing data tables in memory, deleting data tables in memory only considers the data table write time when there is no spare memory, which may lead to reduced database response speed and throughput. Third, the use of a single-table structure or a memory-based caching mechanism lacks effective support for multi-table relationships, resulting in low efficiency when processing related data. Summary of the Invention
[0004] To address the problems existing in current technologies: First, allowing modified data tables to be saved to disk before a transaction is completed leads to frequent disk refreshes, resulting in degraded database performance; second, when managing in-memory data tables, deleting in-memory data tables only considers the data table write time when there is no spare memory, which may reduce database response speed and throughput; third, the use of a single-table structure or a memory-based caching mechanism lacks effective support for multi-table relationships, resulting in low efficiency when processing related data; this invention provides a centralized storage method and apparatus for an airborne multi-relational table database, used to manage data tables on disk in an airborne embedded database to improve system performance and resource utilization. Its goal is to rationally select data tables to retain or replace in memory to reduce disk I / O operations and improve the locality and overall performance of data access.
[0005] The technical solution is as follows: In a first aspect, a centralized storage device for an airborne multi-relation table database is provided, the device comprising a multi-relation table storage unit, a data mirroring table processing unit, and a transaction management unit; The multi-relation table storage unit stores lists of data relations and data tables of various relation types; each list of data relations corresponds to at least one data table; The transaction management unit obtains the transaction operation instructions and sends them to the data mirror table processing unit. The transaction operation instructions carry the identification information of the data relationship list. The data mirroring table processing unit searches locally for a corresponding data relationship list based on transaction operation instructions. If a list exists, it retrieves the corresponding data table from the local machine and performs the operations indicated by the transaction operation instructions on the retrieved data table. Otherwise, it retrieves the corresponding data relationship list and data table from the multi-relationship table storage unit and executes the corresponding operations. After executing all transaction operation instructions, the data mirroring table processing unit temporarily stores the updated data relationship list and data table locally. When preset conditions are met, it sends the updated data relationship list and data table to the multi-relationship table storage unit for storage, overwriting the original data relationship list and data table in the multi-relationship table storage unit.
[0006] Furthermore, The data mirroring table processing unit is also used for: When it is necessary to delete the data relationship list and data table stored locally, send the updated data relationship list and data table to the multi-relationship table storage unit; Alternatively, when log checkpoints need to be written, the updated list of data relationships and data tables are sent to the multi-relationship table storage unit.
[0007] Optionally, if the data mirroring table processing unit cannot find the corresponding data relationship list and data table locally based on the transaction operation instruction, the data mirroring table processing unit sends a request message to the transaction management unit. After receiving the request message, the transaction management unit sends an instruction message to the multi-relationship table storage unit. Based on the instruction message, the multi-relationship table storage unit sends the corresponding data relationship list and data table to the data mirroring table processing unit.
[0008] Optionally, when the data mirroring table processing unit needs to delete the locally stored data relationship list and data table, it deletes the data table with the lowest access frequency, the longest access time interval, and the fewest accesses based on the access information of the data table recorded over a period of time.
[0009] Optionally, when recording access information of a data table, the data mirror table processing unit uses a linked list of size K to record information about the K most recently accessed data tables, including the identifier of the accessed data table, the access time, and the number of accesses.
[0010] Optionally, when the data mirroring table processing unit performs the operation indicated by the operation instruction on a certain data table, if other transactions in the transaction management list of the transaction management unit also want to modify the same data table at the same time, the data mirroring table processing unit will send a rejection operation instruction to the transaction management unit. The transaction management unit will update the status of the transaction to delayed modification in the transaction management list. When the data table is modified and the transaction management unit receives the execution completion reply, the rejected transaction operation will be re-executed.
[0011] Optionally, the multi-relationship table storage unit includes: a data table storage module and a data table mirroring management module; The data table storage module manages the data relationship list and data tables. The data relationship list records the relationships between data tables and supports consistent modification of related data tables. The data table mirroring management module analyzes the instruction information from the transaction management unit and sends the data tables required for the transaction to the data mirroring table processing unit.
[0012] Optionally, the transaction management unit includes: a transaction generation module and a transaction list module; The transaction generation module parses transaction operation instructions and saves the corresponding parsed transactions in the transaction list module; The transaction list module stores the transaction status corresponding to each transaction operation instruction and the data tables involved in the transaction operation. It also sends instructions to the multi-relation table data storage unit and the data mirror table processing unit, receives the reply information from the data mirror table processing unit, and sends the database operation result set to the outside world.
[0013] Optionally, the data mirroring table processing unit stores a list of data relationships, the modified data tables, and the execution status of the corresponding transactions; when the transaction execution status is complete, it sends an instruction to the transaction management unit to update the execution status in the transaction list. In a second aspect, a method for providing a centralized storage device for an airborne multi-relation table database as described in any of the first aspects includes: The transaction management unit obtains the transaction operation instructions and sends them to the data mirror table processing unit. The transaction operation instructions carry the identification information of the data relationship list. The data mirror table processing unit searches locally for a corresponding data relationship list based on the transaction operation instruction. If a list exists, it retrieves the corresponding data table from the local database and performs the operation indicated by the transaction operation instruction on the retrieved data table. Otherwise, it retrieves the corresponding data relationship list and data table from the multi-relationship table storage unit and performs the corresponding operation. After executing all transaction operation instructions, the data mirroring table processing unit temporarily stores the updated data relationship list and data table locally. When the preset conditions are met, the updated data relationship list and data table are sent to the multi-relationship table storage unit for storage, overwriting the original data relationship list and data table in the multi-relationship table storage unit.
[0014] The beneficial effects of this invention are at least as follows: 1. After executing all transaction operation instructions, the data mirroring table processing unit temporarily stores the updated data relationship list and data table locally. Other transactions in the transaction list corresponding to the transaction operation instructions can share and access the modified data table, thereby improving the database's response speed, throughput, and performance.
[0015] 2. The transaction management unit schedules data table read and write operations between the data mirroring table processing unit and the multi-relational table storage unit, provides a concurrent transaction control mechanism, ensures data consistency, implements a coordination mechanism for transaction operations and data loading, and manages the lifecycle of transactions.
[0016] 3. Based on the access information of K records of data tables within a certain period, the data tables with the lowest access frequency, the longest access time interval, and the fewest accesses are deleted from the data mirror table processing unit. This implements an intelligent cache eviction strategy, which can effectively avoid the phenomenon of frequently accessed data tables being frequently deleted. It is suitable for resource-constrained airborne systems, optimizes memory usage efficiency, and can better meet the requirements of random data access and high efficiency.
[0017] 4. When modifying a data table, query the data relationship list to support the consistency maintenance of data associated with multiple relationship tables and avoid data conflicts. Attached Figure Description
[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. The drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0019] Figure 1 This is a schematic diagram of the centralized storage device for the airborne multi-relation table database of the present invention. Detailed Implementation
[0020] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0021] The features and illustrative embodiments of various aspects of the present invention will now be described in detail. Numerous specific details are set forth in the following detailed description to provide a thorough understanding of the invention. However, it will be apparent to those skilled in the art that the invention may be practiced without requiring some of these specific details. The following description of embodiments is merely intended to provide a better understanding of the invention by illustrating examples of the invention. The invention is by no means limited to any specific setups and methods set forth below, but covers any improvements, substitutions, and modifications to structures, methods, and devices without departing from the spirit of the invention. Well-known structures and techniques are not shown in the drawings and the following description to avoid unnecessarily obscuring the invention.
[0022] It should be noted that, unless otherwise specified, the embodiments of the present invention and the features thereof can be combined with each other, and the various embodiments can be referenced and cited from each other.
[0023] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments.
[0024] The present invention aims to provide a highly secure, highly reliable, and complete efficient data management solution for complex airborne environments.
[0025] This invention proposes a data table management strategy for airborne database management, enabling efficient data management and rapid retrieval. A suitable data table management strategy can reduce disk I / O overhead, lower energy consumption, extend disk lifespan, and improve the stability and reliability of the database system under high-pressure environments. Furthermore, a suitable data table management strategy can also enhance the response speed and throughput of the database system, improve user experience, and meet the demands of real-time data processing.
[0026] Example 1: When processing a transaction operation using the device of the present invention, the specific steps are as follows: In the airborne database, the multi-relational table storage unit has created the tables "USER_FPLN", "USER_FPLN_LEGS", "AIRPORT", "RUNWAY", "WAYPOINT", "SID", "STAR", and "APPROACH". These tables store information on all company routes, flight segments, airports, runways, waypoints, standard instrument departure routes, standard instrument arrival routes, and approach information, respectively. The maximum storage space for the data mirroring table processing unit is 20.
[0027] Step 1: When a user sends a transaction operation command to set the departure procedure via the 429 bus, the transaction generation module in the transaction management unit analyzes the command and needs to query the "SID" table and the "RUNWAY" table. The transaction is named "Transaction 1" and paired with the corresponding records in the "SID" and "RUNWAY" tables in the transaction list module.
[0028] Step 2: The transaction management unit sends a query command for the "SID" table to the data mirroring table processing unit. Once the table is found, the data mirroring table processing unit sends the table information to the transaction management unit. The transaction management list is updated to "completed" and then sent to the user via the 429 bus by the transaction management unit. Step 3: The transaction management unit sends a query command for the "RUNWAY" table to the data mirroring table processing unit. If the table is not found, the data mirroring table processing unit replies "Does not exist" to the transaction management unit. The transaction management unit then sends a load command for the "RUNWAY" table to the multi-relation table storage unit. The multi-relation table storage unit sends the "RUNWAY" table to the data mirroring table processing unit. After receiving the complete information, the data mirroring table processing unit records the table and the transaction completion status, and sends it to the transaction management unit. The transaction management list updates the status to "Completed," and the transaction management unit sends it to the user via the 429 bus. Step 4: When the user sends a runway identification setting transaction operation command via the 429 bus, the transaction generation module in the transaction management unit analyzes the command and determines whether to query the "USER_FPLN_LEGS" table or insert a flight segment. Recording and status management are then performed in the transaction list module.
[0029] Step 5: The transaction management unit sends a query and modification instruction to the data mirroring table processing unit for the "USER_FPLN_LEGS" table. The data mirroring table processing unit retrieves the table, modifies it accordingly, and marks the table as "modified." The data mirroring table processing unit then sends the modified table information to the transaction management unit, the transaction management list update status is changed to "completed," and the transaction management unit sends it to the user via the 429 bus. Step 6: When a user sends a transaction operation command to set and insert waypoints for a flight segment via the 429 bus, the transaction generation module in the transaction management unit analyzes the command and determines whether to query the "USER_FPLN_LEGS" table and perform the insertion of waypoints for the flight segment. Recording and status management are then performed in the transaction list module.
[0030] Step 7: The transaction management unit sends a query and modification instruction to the data mirror table processing unit for the "USER_FPLN_LEGS" table. The data mirror table processing unit finds the table. If the transaction status of the table is "completed", it continues to modify the table according to the current transaction instruction, sets the table to "modified", and updates the corresponding transaction and status of the table. After completion, the data mirror table processing unit sends the modified table information to the transaction management unit. The transaction management list updates the status to "completed" and the transaction management unit sends it to the user via the 429 bus. Step 8: When the database system writes a checkpoint, the table "USER_FPLN_LEGS" marked as "modified" and its relation list in the data mirroring table processing unit are sent to the multi-relation table storage unit to overwrite the original data.
[0031] Example 2, when performing multi-table relationship consistency maintenance using the device of the present invention, is as follows: Step 1: When a user sends a transaction operation command via the 429 bus, the transaction generation module in the transaction management unit analyzes the transaction operation command and determines that a certain flight point data in the path table needs to be updated.
[0032] Step 2: The transaction management unit sends a modification path table instruction to the data mirror table processing unit, queries the table, queries the relationship list of the path table, and identifies the correlation between the flight point data that needs to be updated and the sensor acquisition table and the mission status table.
[0033] Step 3: If the sensor acquisition table and task status table do not exist in the data mirror table processing unit, the transaction management unit requests the multi-relation table storage unit to load the sensor acquisition table and task status table into the data mirror table processing unit. Step 4: Once the data mirror table processing unit has recorded all the transaction-related data tables, it automatically performs a cascading update to update the relevant data in the sensor acquisition table and the task status table. Step 5: The data mirroring table processing unit completes this consistency operation in the local cache; Step 6: When writing back, submit all changes to the multi-relationship table storage unit to ensure data consistency.
[0034] It should be noted that the above process operations can be combined to varying degrees. For the sake of simplicity, the implementation methods of various combinations will not be elaborated further. Those skilled in the art can flexibly adjust or combine the order of the steps of the above method (or the position of the product components) according to the actual situation.
[0035] It should be noted that the functional components shown in the above embodiments can be implemented in hardware, software, or a combination of both. When implemented in hardware, they can be electronic circuits, application-specific integrated circuits (ASICs), plug-ins, function cards, etc. When implemented in software, they can be programs or code segments used to perform the required tasks. Programs or code segments can be stored in a machine or readable medium, or they can be transmitted over a transmission medium or communication link via data signals carried in a carrier wave.
[0036] The above description merely illustrates embodiments of the present invention and is quite specific and detailed; however, it should not be construed as limiting the scope of the patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these all fall within the scope of protection of the present invention. Furthermore, any parts of the present invention not described in detail are conventional techniques.
Claims
1. A centralized storage device for an airborne multi-relation table database, characterized in that, include: Multi-relational table storage unit, data mirror table processing unit, and transaction management unit; The multi-relation table storage unit stores lists of data relations and data tables of various relation types; each list of data relations corresponds to at least one data table; The transaction management unit is used to obtain transaction operation instructions and send them to the data mirror table processing unit. The transaction operation instructions carry the identification information of the data relationship list. The data mirror table processing unit is used to search locally for a corresponding data relationship list based on transaction operation instructions. If a list exists, the unit retrieves the data table corresponding to the data relationship list from the local machine and performs the operation indicated by the transaction operation instructions on the retrieved data table. Otherwise, the unit retrieves the corresponding data relationship list and data table from the multi-relationship table storage unit and performs the corresponding operation. The data mirroring table processing unit is used to temporarily store the updated data relationship list and data table locally after executing all transaction operation instructions; when preset conditions are met, the updated data relationship list and data table are sent to the multi-relationship table storage unit for storage and overwrite the original data relationship list and data table in the multi-relationship table storage unit.
2. The apparatus according to claim 1, characterized in that, The data mirroring table processing unit is also used for: When it is necessary to delete the data relationship list and data table stored locally, send the updated data relationship list and data table to the multi-relationship table storage unit; Alternatively, when log checkpoints need to be written, the updated list of data relationships and data tables are sent to the multi-relationship table storage unit.
3. The apparatus according to claim 1, characterized in that, If the data mirroring table processing unit cannot find the corresponding data relationship list and data table locally based on the transaction operation instruction, it sends a request message to the transaction management unit. After receiving the request message, the transaction management unit sends an instruction message to the multi-relationship table storage unit. Based on the instruction message, the multi-relationship table storage unit sends the corresponding data relationship list and data table to the data mirroring table processing unit.
4. The apparatus according to claim 2, characterized in that, The data mirroring table processing unit deletes the data relationship list and data tables stored locally when they need to be deleted, based on the access information of the data tables recorded over a period of time. The data tables with the lowest access frequency, the longest access interval, and the fewest accesses are deleted.
5. The apparatus according to claim 4, characterized in that, When recording access information for a data table, the data mirroring table processing unit uses a linked list of size K to record information about the K most recently accessed data tables, including the identifier of the accessed data table, the access time, and the number of accesses.
6. The apparatus according to claim 1, characterized in that, When the data mirroring table processing unit performs the operation indicated by the operation instruction on a certain data table, if other transactions in the transaction management list of the transaction management unit also want to modify the same data table at the same time, the data mirroring table processing unit will send a rejection operation instruction to the transaction management unit. The transaction management unit will update the status of the transaction to delayed modification in the transaction management list. When the data table is modified and the transaction management unit receives the execution completion reply, it will re-execute the rejected transaction operation.
7. The apparatus according to claim 1, characterized in that, The multi-relationship table storage unit includes: a data table storage module and a data table mirroring management module; The data table storage module manages the data relationship list and data tables. The data relationship list records the relationships between data tables and supports consistent modification of related data tables. The data table mirroring management module analyzes the instruction information from the transaction management unit and sends the data tables required for the transaction to the data mirroring table processing unit.
8. The apparatus according to claim 1, characterized in that, The transaction management unit includes: a transaction generation module and a transaction list module; The transaction generation module parses transaction operation instructions and saves the corresponding parsed transactions in the transaction list module; The transaction list module stores the transaction status corresponding to each transaction operation instruction and the data tables involved in the transaction operation. It also sends instructions to the multi-relation table data storage unit and the data mirror table processing unit, receives the reply information from the data mirror table processing unit, and sends the database operation result set to the outside world.
9. The apparatus according to claim 1, characterized in that, The data mirroring table processing unit stores a list of data relationships, the modified data tables, and the execution status of the corresponding transactions. When the transaction execution status is complete, it sends an instruction to the transaction management unit to update the execution status in the transaction list.
10. A method for a centralized storage device for an airborne multi-relation table database as described in any one of claims 1 to 9, characterized in that, include: The transaction management unit obtains the transaction operation instructions and sends them to the data mirror table processing unit. The transaction operation instructions carry the identification information of the data relationship list. The data mirror table processing unit searches locally for a corresponding data relationship list based on the transaction operation instruction. If a list exists, it retrieves the corresponding data table from the local database and performs the operation indicated by the transaction operation instruction on the retrieved data table. Otherwise, it retrieves the corresponding data relationship list and data table from the multi-relationship table storage unit and performs the corresponding operation. After executing all transaction operation instructions, the data mirroring table processing unit temporarily stores the updated data relationship list and data table locally. When the preset conditions are met, the updated data relationship list and data table are sent to the multi-relationship table storage unit for storage, overwriting the original data relationship list and data table in the multi-relationship table storage unit.