EVTOL airborne navigation database design method

Abstract

The invention discloses an eVTOL airborne navigation database design method, and belongs to the field of airborne navigation databases. The method comprises the following steps: classifying navigation content data; respectively designing the terminal program data, the route section data, the route data, the route point data and the stop point data, and determining the basic field content of the terminal program data, the route section data, the route data, the route point data and the stop point data; associating the terminal program data file into the route data file; associating the route data file into the route section data file; associating the route segment data file to each underlying data file; performing data sorting and indexing on all the data files; performing standard check on each item of data; and optimizing a storage result. According to the method, the unique requirements of the eVTOL aircraft in the urban environment are met, the eVTOL aircraft can be helped to plan a safe path and avoid obstacles, and flight safety is guaranteed.

Description

Technical Field

[0001] The present invention belongs to the field of airborne navigation databases, and in particular, the present invention relates to a method for designing an eVTOL airborne navigation database. Background Art

[0002] The trend of the number of smart cities and the demand for sustainable transportation has grown dramatically across the globe in the past few years to optimize urban functions and drive economic growth. In addition, multiple governments around the world have signed the Paris Agreement to reduce the carbon footprint of their respective countries, thereby promoting sustainable air transportation. However, due to increasing traffic congestion, it has become very difficult for daily commuters in large cities to travel by road, so daily commuters are looking for efficient, sustainable and safer modes of transportation to reach their workplaces and other desired destinations. In addition, due to limited urban land space, some megacities have reached the limit of expanding road infrastructure.

[0003] eVTOL (Electric Vertical Takeoff and Landing) aircraft represent a major innovation in the future of aviation. They are electric, vertical takeoff and landing aircraft that can achieve fast, low-noise, and efficient air transportation in urban environments. This emerging technology is attracting widespread attention and has become a hot topic in the fields of "air taxis" and "urban air mobility". eVTOL aircraft are expected to begin commercial operations in the next few years, bringing a complete change to urban transportation.

[0004] The successful operation and safe navigation of eVTOL aircraft are critical to achieving this vision. In urban environments, eVTOLs face a variety of challenges, including terrain, buildings, weather conditions, traffic control, and other aircraft. To ensure their safe and efficient operation, eVTOL aircraft require highly accurate navigation database support.

[0005] The eVTOL onboard navigation database is significantly different from the traditional navigation database in many aspects, which are mainly reflected in the following aspects:

[0006] 1. Aerial navigation path planning: eVTOL aircraft usually need to fly at low altitudes, through urban areas or busy urban airspace. Therefore, compared with traditional high-altitude flights, they require more detailed navigation path planning and obstacle avoidance strategies to ensure safe flight in urban environments.

[0007] 2. Vertical take-off and landing area: eVTOL aircraft have vertical take-off and landing capabilities, so their navigation database needs to include data on vertical take-off and landing areas to guide the aircraft's operations in confined spaces. This is completely different from the take-off and landing process of traditional aircraft.

[0008] 3. Urban geographic information: The navigation database of eVTOL aircraft needs to include detailed geographic information of urban areas, including landmarks such as buildings, roads, utility poles, and viaducts, to help the aircraft avoid obstacles. Traditional navigation databases usually do not contain this information.

[0009] 4. Real-time data update: Due to real-time changes in the urban environment, the eVTOL onboard navigation database needs to be able to update data in real time to reflect information such as new buildings, traffic control, weather conditions and flight restrictions. Traditional navigation databases are usually updated periodically.

[0010] 5. Flight performance and energy management: eVTOL aircraft usually use electric power systems, so the navigation database also needs to include information about battery status, charging station location and energy management to ensure the energy management and flight planning of the aircraft.

[0011] In order to realize an onboard navigation database dedicated to eVTOL, the present invention provides an eVTOL onboard navigation database design method. Summary of the invention

[0012] The present invention aims to overcome the shortcomings of the prior art and proposes an eVTOL airborne navigation database design method to achieve the following objectives: Through the eVTOL airborne navigation database design method provided by the present invention, an airborne navigation database dedicated to eVTOL is obtained to meet the unique needs of eVTOL aircraft in urban environments, help eVTOL aircraft plan safe paths, avoid obstacles, and ensure flight safety.

[0013] In order to achieve the above object, the technical solution adopted by the present invention is: a method for designing an eVTOL airborne navigation database, the method comprising the following steps:

[0014] S1. Classify the navigation content data, including terminal program data, route segment data, route data, waypoint data, stop point data, restriction data, and landmark data;

[0015] S2. Design the terminal program data and determine the basic field content thereof;

[0016] S3, designing the route segment data and determining the basic field content thereof;

[0017] S4. Design the route data and determine the basic field contents thereof;

[0018] S5. Design the waypoint data and determine the basic field contents thereof;

[0019] S6. Design the stop point data and determine the basic field content thereof;

[0020] S7, associating the terminal program data file with the route data file;

[0021] S8, associating the route data file with the route segment data file;

[0022] S9, associating the route segment data file to the waypoint data file, the stop point data file, the restriction data file, and the landmark data file respectively;

[0023] S10, sorting all data files;

[0024] S11, indexing the data in all data files;

[0025] S12. Conduct standard checks on each data item;

[0026] S13. Optimize storage results.

[0027] Preferably, the terminal program data includes vertical take-off and landing process data, vertical and short take-off and landing process data, standard instrument departure and approach data.

[0028] Preferably, in step S3, the design of the route segment data includes:

[0029] S31. assigning a unique identifier to each route segment;

[0030] S32. Each route segment includes the following information:

[0031] Minimum flight altitude: the lowest permitted flight altitude of the aircraft in this route segment;

[0032] Maximum flight altitude: the maximum permitted flight altitude of the aircraft in this route segment;

[0033] Minimum flight speed: the minimum allowed flight speed of the aircraft in this route segment;

[0034] Maximum flight speed: the maximum allowed flight speed of the aircraft in this route segment;

[0035] S33, classifying each route segment, the categories including vertical ascent, vertical descent, straight flight, and curved flight;

[0036] S34. Each route segment includes a starting point and an end point;

[0037] S35. Each route segment includes the duration of the corresponding route segment.

[0038] Preferably, in step S4, the design of the route data includes:

[0039] S41. assign a unique identifier to each route;

[0040] S42, each route includes a starting point and an end point of the corresponding route;

[0041] S43, classifying each route into categories including high-altitude routes and low-altitude routes;

[0042] S44, dividing each route segment into a plurality of route segments;

[0043] S45. Each route includes a plurality of waypoints, and the waypoints are used to describe the route path.

[0044] Preferably, in step S5, the design of the waypoint data includes:

[0045] S51, assigning a unique identifier to each waypoint;

[0046] S52, each waypoint includes the longitude and latitude of the corresponding waypoint;

[0047] S53, each waypoint includes a height limit and a speed limit corresponding to the waypoint;

[0048] S54. Classify each route into the following categories:

[0049] Turning point: marks the turning point in the route, usually used to change the flight direction;

[0050] Intersection: marks the intersection of different routes;

[0051] Approach Point: Used to indicate key points during the approach process;

[0052] Parking position: used to identify the parking positions within the airport;

[0053] S55. Use the WGS 84 coordinate system to store the longitude and latitude of the waypoint coordinates.

[0054] Preferably, in step S6, the design of the stop point data includes:

[0055] S61, assigning a unique identifier to each stop;

[0056] S62, each stop point includes its geographical coordinates, and the geographical coordinates include longitude and latitude;

[0057] S63, each stop point includes its height information relative to the ground;

[0058] S64, classifying each stop point, the categories including passenger boarding and alighting points, cargo delivery points, and charging stations;

[0059] S65. Each stop includes availability and status information of the corresponding stop;

[0060] S66. Each stop includes information about charging facilities, navigation performance parameters, obstacles, and safety area information.

[0061] Preferably, the restriction data comprises a sequential list of vertical and lateral restrictions for restricted areas, and a sequential list of vertical and lateral restrictions for controlled airspace.

[0062] Preferably, in step S10, all data files are sorted according to their corresponding identifiers.

[0063] Preferably, in step S11, the data files are indexed by an index file, wherein, for waypoint and stop point data files, each file is matched with another file for index sorting.

[0064] Preferably, in step S13, the optimization method for storing the results includes:

[0065] S131, for a file with a fixed database record size, using record numbers to randomly access records in the file;

[0066] S132: Use shared memory to construct a database table, where the database table contains multiple database records.

[0067] The technical effects of the present invention are as follows: (1) The eVTOL airborne navigation database designed by the present invention includes key data such as urban geographic information, vertical take-off and landing areas, traffic control areas and battery charging stations, meeting the unique needs of eVTOL aircraft in urban environments; (2) The airborne navigation database dedicated to eVTOL obtained by the method of the present invention is more detailed than the traditional navigation database and includes data and functions specific to eVTOL operations, ensuring their safe and efficient operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] Figure 1 This is a flow chart of a method for designing an eVTOL airborne navigation database according to an embodiment of the present invention;

[0069] Figure 2 A schematic diagram of the Airportfile file structure provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0070] The following is a further detailed description of the specific implementation of the present invention through the description of the embodiments with reference to the accompanying drawings, the purpose of which is to help those skilled in the art have a more complete, accurate and in-depth understanding of the inventive concept and technical solution of the present invention, and to facilitate its implementation. It should be noted that the words "first", "second" and the like described in this application are only for the convenience of describing the technical solution to distinguish different components, and are not used to limit this application. In order to make the technical solution of the present invention clearer, the present invention is explained through the following embodiments.

[0071] A method for designing an eVTOL airborne navigation database, such as Figure 1 As shown, the method comprises the following steps:

[0072] S1. Classify the navigation content data, the categories include terminal program data, route segment data, route data, waypoint data, stop point data, restriction data, landmark data, etc.

[0073] S2. Design the terminal program data and determine its basic field content.

[0074] S3. Design the route segment data and determine its basic field contents.

[0075] S4. Design the route data and determine its basic field contents.

[0076] S5. Design the waypoint data and determine its basic field contents.

[0077] S6. Design the stop point data and determine its basic field content.

[0078] S7. Associate the terminal program data file with the route data file.

[0079] S8. Associating the route data file with the route segment data file.

[0080] S9. Associate the route segment data file with the waypoint data file, the stop point data file, the restriction data file, and the landmark data file respectively.

[0081] S10. Sort all data files.

[0082] S11. Index the data in all data files.

[0083] S12. Conduct a standard check on each data item.

[0084] S13. Optimize storage results.

[0085] Specifically, in step S1 of this embodiment, in order to meet the navigation needs of the eVTOL aircraft, the navigation content data is classified, and the classification categories include terminal program data, route segment data, route data, and waypoint data, which are also available in traditional databases, but in this embodiment, they are all optimized for eVTOL. At the same time, the navigation content data of this embodiment also includes stop point data, restriction data, landmark data, etc., which are categories designed specifically for eVTOL. Among them, the stop point data includes airport data, apron data, charging station data, etc., to meet the docking and charging needs of the eVTOL aircraft. The restriction data includes a sequential list of vertical and lateral restrictions in the restricted area, a sequential list of vertical and lateral restrictions in the controlled airspace, etc., to ensure that the eVTOL aircraft flies within a safe range. Landmark data is landmark-type geological feature data. Because eVTOL aircraft usually fly at low altitudes, landmark data is entered to avoid collisions with high-rise buildings or mountain features, and to be able to identify the area under IFR rules.

[0086] At the same time, the data is further subdivided in each navigation content data category to ensure that the organization and management of the data meet the navigation requirements of the eVTOL aircraft. For example, the data can be divided according to the navigation mission phase, navigation mode and navigation method to better support different types of navigation tasks. For example, the runway or apron data of the airport will be used in the vertical take-off and landing phase, while only the location data of the airport needs to be known in the cruise phase. Therefore, in the design phase, the extended field of the data table designed for the vertical take-off and landing program data (a terminal program data) must not only be designed with an interface with the airport data table, but also with the first apron design of the airport. The extended field of the data table designed for the cruise program (a terminal program data) only needs to define the airport data table.

[0087] To ensure data consistency and accuracy, each navigation content data item needs to have its data specifications clearly defined. These specifications include data types (such as strings, integers, floating point numbers, etc.), unit (such as feet, meters, knots, meters / second, etc.), value range, allowed character set, update frequency, sequence description, etc. The formulation of these specifications should comply with the ARINC 424 standard, and also include data accuracy, resolution, data processing assurance level, etc. that meet the development assurance level C to ensure data standardization and compliance.

[0088] In step S2 of this embodiment, for each terminal program data item, its data specification is defined, and the specific specification definition can refer to step 1. At the same time, the terminal program data, which is an important part of the navigation database, is further subdivided into eVTOL aircraft to ensure that the organization and management of the data meet the eVTOL navigation requirements. The categories include:

[0089] VTOL Process Data: This category includes information related to VTOL flight processes, such as VTOL procedures, vertical paths, etc. VSTOL Process Data: This category includes navigation data applicable to VSTOLs, such as VSTOL procedures, vertical and short takeoff and landing paths, etc. SIDAR Data: This category covers information related to departure and arrival processes, including standard instrument departure and arrival procedures.

[0090] In step S3 of this embodiment, the design of the route segment data needs to take into account the special properties of vertical take-off and landing and short-distance take-off and landing. At the same time, for each route data item, its data specification is defined. For details, please refer to the specification definition in step 1. Specifically, the route segment data is designed with the following fields:

[0091] S31. Assign a unique identifier to each route segment for reference and retrieval in the database.

[0092] S32. For vertical take-off and landing and short take-off and landing flights, altitude restrictions and speed restrictions are very important, so each route segment includes the following information:

[0093] Minimum flight altitude: The lowest permitted flight altitude of the aircraft on this route.

[0094] Maximum flight altitude: The maximum permitted flight altitude of the aircraft on this route segment.

[0095] Minimum flight speed: The minimum allowed flight speed of the aircraft in this route segment.

[0096] Maximum flight speed: The maximum allowed flight speed of the aircraft in this route segment.

[0097] S33. Classify each route segment. Considering the vertical operations of vertical take-off and landing and short take-off and landing, the route segments can be classified according to their characteristics. The categories include:

[0098] Climb: describes the route segment of climbing upward, including altitude and speed restrictions. Descent: describes the route segment of descending, including altitude and speed restrictions. Straight Flight: describes the route segment of horizontal straight flight, including altitude and speed restrictions. Turn Flight: describes the route segment of curved or turning flight, including altitude and speed restrictions.

[0099] S34. Each route segment includes a starting point and an ending point. These points may be specific coordinate locations or landmarks, and are used to provide information such as latitude and longitude coordinates, identifiers, and location descriptions.

[0100] S35. Each route segment includes a duration of the corresponding route segment. For vertical take-off and landing and short take-off and landing operations of eVTOL aircraft, understanding the duration of each route segment is helpful for planning and scheduling flight missions.

[0101] In step S4 of this embodiment, for each route data item, its data specification is defined, and the specific specification definition can refer to step 1. At the same time, the route data is designed with the following fields:

[0102] S41. Assign a unique identifier to each route.

[0103] S42. Each route includes a starting point and an end point of the corresponding route.

[0104] S43. Classify each route into categories such as high-altitude routes, low-altitude routes, etc.

[0105] S44. Divide each route segment into multiple segments, each segment including a waypoint sequence, an altitude limit, a speed limit, etc.

[0106] S45. Each route includes a plurality of waypoints, and the waypoints are used to describe the route path, including latitude and longitude coordinates, waypoint identifiers, etc.

[0107] In step S5 of this embodiment, for each waypoint data item, its data specification is defined, and the specific specification definition can refer to step 1. At the same time, the waypoint data is designed with the following fields:

[0108] S51. Assign a unique identifier to each waypoint.

[0109] S52. Each waypoint includes the longitude and latitude of the corresponding waypoint.

[0110] S53. Each waypoint includes a corresponding altitude restriction (describing the altitude restriction of the waypoint, including the minimum and maximum altitudes) and a speed restriction (describing the speed restriction of the waypoint, including the minimum and maximum speeds).

[0111] S54. Classify each route into the following categories:

[0112] Turning Point: Identifies the turning point in the route, usually used to change the flight direction.

[0113] Intersection: marks the intersection of different routes.

[0114] Approach Points: Used to indicate critical points during an approach.

[0115] Parking position: used to identify the parking positions within the airport.

[0116] S55. Use the WGS 84 coordinate system to store the longitude and latitude of the waypoint coordinates to ensure that the longitude and latitude of the waypoint coordinates are stored in the correct coordinate system.

[0117] In step S6 of this embodiment, for each docking point data item, its data specification is defined, and the specific specification definition can refer to step 1. At the same time, the docking point data design of eVTOL aircraft needs to take into account the needs of these aircraft to perform electric vertical take-off and landing and short-distance take-off and landing operations in cities and surrounding areas. The following is the field design of the docking point data.

[0118] S61. Assign a unique identifier to each stop.

[0119] S62, each stop includes the geographical coordinates where it is located, and the geographical coordinates include longitude and latitude. These coordinates will be used for navigation and determining the position of the stop on the city map.

[0120] S63. Due to the vertical take-off and landing capability of the eVTOL aircraft, each docking point also includes its height information relative to the ground. This helps determine the vertical position of the docking point.

[0121] S64. Classify each stop, including passenger boarding and alighting points, cargo delivery points, charging stations, etc. Each type of stop should have relevant attribute information.

[0122] S65. Each stop includes availability and status information of the corresponding stop. For example, some stops may be unavailable due to maintenance or other reasons, while other stops may be operating normally. This helps the aircraft plan flight missions.

[0123] S66. Each stop includes information about charging facilities (used for planning battery charging tasks), navigation performance parameters (such as maximum wind speed, maximum vertical climb rate, maximum descent rate, etc., used to determine whether the eVTOL aircraft can safely enter and exit the stop), obstacle and safety area information, etc.

[0124] This embodiment provides a stop point database, as shown in Table 1.

[0125]

[0126] Table 1

[0127] In summary, the eVTOL airborne navigation database designed by the present invention includes key data such as urban geographic information, vertical take-off and landing areas, traffic control areas, and battery charging stations, meeting the unique needs of eVTOL aircraft in urban environments. The airborne navigation database dedicated to eVTOL of the present invention is more detailed and includes data and functions specific to eVTOL operations compared to traditional navigation databases, ensuring their safe and efficient operation.

[0128] Furthermore, this embodiment takes the vertical take-off and landing and short take-off and landing program (V / STOL, a terminal program) data file as an example to describe the subsequent design method of the present invention. The method is similar to the traditional aviation terminal program, but is adjusted to meet the needs of eVTOL. For example, eVTOL may require special take-off and landing procedures, which need to be defined in the vertical take-off and landing and short take-off and landing program data file. For example, the vertical take-off and landing and short take-off and landing procedures require detailed altitude and flight segment information to ensure that the eVTOL aircraft can perform these operations safely. In addition, considering the particularity of the eVTOL aircraft, the vertical take-off and landing and short take-off and landing program data file may also include performance parameters related to vertical take-off and landing, such as maximum climb rate, descent rate, etc. These parameters are crucial for planning eVTOL flight missions.

[0129] For step S7: associate the terminal program data file with the route data file. The vertical take-off and short-distance take-off and landing program data file records the number of routes included in each vertical take-off and short-distance take-off and landing program. Therefore, this embodiment associates the vertical take-off and short-distance take-off and landing program data file with the next-level data file, i.e., the route data file, through the index data item / index file. This design ensures the integrity of the routes in each vertical take-off and short-distance take-off and landing program.

[0130] The routes in each route data file are composed of a combination of multiple route segments, so based on step S8 of this example, the route data file is associated with the route segment data file. At the same time, the route segment data usually also involves waypoint data, so based on step S9 of this example, the route segment data files are respectively associated with the waypoint data files. In this way, the navigation database can be used to know which waypoints the route segment data passes through and on which route it is. At the same time, for the navigation data items designed for eVTOL, such as stop point data, restriction data, and landmark data, based on step S9 of this example, the route segment data file is also associated with the stop point data file, restriction data file, and landmark data file, so as to meet the navigation requirements of the eVTOL aircraft and ensure the efficient and safe flight of the eVTOL aircraft.

[0131] In order to facilitate the calling and searching of data items in each data file, in step S10 of the present embodiment, data of all data files are sorted. Since the present embodiment designs a unique identifier for the data item of each data file, the present embodiment sorts the data according to the identifier, which greatly improves the efficiency of subsequent data search.

[0132] In order to achieve accurate search of data in each data file, in step S11 of this embodiment, the data in all data files are indexed by setting index data items or index files. Among them, for the underlying data files of the database, such as the waypoint and stop point data files of this embodiment, each file is equipped with another file for index sorting, so as to achieve mutual indexing between the underlying data files.

[0133] like Figure 2 The file shown is an Airportfile designed in this embodiment. Each record in this file contains information about a specific airport, and the file is sorted by the airport identifier (ICAO Ident). In order to fully describe the airport facilities and environment, there are many reference files in the file. For example, the runway record number in the Airportfile file references the Runwayfile file. Each record in the Runwayfile file describes a Runway. The file is not sorted in any specific order. The route segments that make up the Runway are specified by referring to the route segment file associated with the Runwayfile file. For another example, the number of records in the Airportfile file references the Airportfrequencyfile file. Each record in this file contains frequency information associated with the airport.

[0134] In step S12 of this embodiment, after the database design is completed, a standard check is performed on each data to ensure the accuracy and consistency of the data to meet the safety and reliability requirements of eVTOL flight operations.

[0135] In step S13 of this embodiment, the storage of the database is also optimized, and the optimization method includes:

[0136] S131. The size of the database records in the file is fixed. By ensuring that the size of the records is fixed, the record numbers can be used to randomly access the records in the file. This structured approach is very convenient for finding records in string files. In actual use, a table often contains records from multiple databases, so the table and the records are considered separately, and the actual structure depends on the structure of the table. Considering the characteristics of records running in different address spaces (possibly even on different ACRs), pointers will not work for this situation because the memory space between the two ACRs may not be allocated in exactly the same way. In addition, a single instance of the navigation database is shared by multiple processes, each with a different memory mapping. Because each process loads the shared memory space differently, the pointer becomes unavailable. Therefore, the database reference-based method of this embodiment solves this problem by using a specific location in the logical structure rather than a memory address.

[0137] S132, using shared memory to build a database table, the database table contains multiple database records, so that they can be shared between processes. Through shared memory, only one process is responsible for loading them, and all other processes have read access to them. In this embodiment, the search method provides a common interface for searching records in the database by identifier. Therefore, this search operation only applies to tables that contain records with identifiers. These tables include airports, obstacle-free, VHF navigation equipment, waypoints, and custom waypoints. The loading process starts with reading the main header file. The header file of each database file is then compared with the main file to ensure consistency. If the database is consistent, each file is loaded.

[0138] The present invention is described above by way of example in conjunction with the accompanying drawings. Obviously, the specific implementation of the present invention is not limited to the above-mentioned manner. As long as various non-substantial improvements are made using the method concept and technical solution of the present invention. Or the above concept and technical solution of the present invention is directly applied to other occasions without improvement, it is within the protection scope of the present invention.

Claims

1. A method for designing an eVTOL airborne navigation database, characterized in that: The method comprises the following steps: S1. Classify the navigation content data, including terminal program data, route segment data, route data, waypoint data, stop point data, restriction data, and landmark data; S2. Design the terminal program data and determine the basic field content thereof; S3, designing the route segment data and determining the basic field content thereof; S4. Design the route data and determine the basic field contents thereof; S5. Design the waypoint data and determine the basic field contents thereof; S6. Design the stop point data and determine the basic field content thereof; S7, associating the terminal program data file with the route data file; S8, associating the route data file with the route segment data file; S9, associating the route segment data file to the waypoint data file, the stop point data file, the restriction data file, and the landmark data file respectively; S10, sorting all data files; S11, indexing the data in all data files; S12. Conduct standard checks on each data item; S13. Optimize storage results.

2. The method for designing an eVTOL airborne navigation database according to claim 1, characterized in that: The terminal procedure data includes vertical take-off and landing process data, vertical and short take-off and landing process data, standard instrument departure and approach data.

3. The method for designing an eVTOL airborne navigation database according to claim 1, characterized in that: In step S3, the design of the route segment data includes: S31. assigning a unique identifier to each route segment; S32. Each route segment includes the following information: Minimum flight altitude: the lowest permitted flight altitude of the aircraft in this route segment; Maximum flight altitude: the maximum permitted flight altitude of the aircraft in this route segment; Minimum flight speed: the minimum allowed flight speed of the aircraft in this route segment; Maximum flight speed: the maximum allowed flight speed of the aircraft in this route segment; S33, classifying each route segment, the categories including vertical ascent, vertical descent, straight flight, and curved flight; S34. Each route segment includes a starting point and an end point; S35. Each route segment includes the duration of the corresponding route segment.

4. The method for designing an eVTOL airborne navigation database according to claim 1, characterized in that: In step S4, the design of the route data includes: S41. assign a unique identifier to each route; S42, each route includes a starting point and an end point of the corresponding route; S43, classifying each route into categories including high-altitude routes and low-altitude routes; S44, dividing each route segment into a plurality of route segments; S45. Each route includes a plurality of waypoints, and the waypoints are used to describe the route path.

5. The method for designing an eVTOL airborne navigation database according to claim 1, characterized in that: In step S5, the design of the waypoint data includes: S51, assigning a unique identifier to each waypoint; S52, each waypoint includes the longitude and latitude of the corresponding waypoint; S53, each waypoint includes a height limit and a speed limit corresponding to the waypoint; S54. Classify each route into the following categories: Turning point: marks the turning point in the route, usually used to change the flight direction; Intersection: marks the intersection of different routes; Approach Point: Used to indicate key points during the approach process; Parking position: used to identify the parking positions within the airport; S55. Use the WGS 84 coordinate system to store the longitude and latitude of the waypoint coordinates.

6. The method for designing an eVTOL airborne navigation database according to claim 1, characterized in that: In step S6, the design of the stop point data includes: S61, assigning a unique identifier to each stop; S62, each stop point includes its geographical coordinates, and the geographical coordinates include longitude and latitude; S63, each stop point includes its height information relative to the ground; S64, classifying each stop point, the categories including passenger boarding and alighting points, cargo delivery points, and charging stations; S65. Each stop includes availability and status information of the corresponding stop; S66. Each stop includes information about charging facilities, navigation performance parameters, obstacles, and safety area information.

7. The method for designing an eVTOL airborne navigation database according to claim 1, characterized in that: The restriction data includes a sequential list of vertical and lateral restrictions for restricted areas and a sequential list of vertical and lateral restrictions for controlled airspace.

8. The method for designing an eVTOL airborne navigation database according to claim 1, characterized in that: In step S10, all data files are sorted according to their corresponding identifiers.

9. The method for designing an eVTOL airborne navigation database according to claim 1, characterized in that: In step S11, the data files are indexed by an index file, wherein for waypoint and stop point data files, each file is matched with another file for index sorting.

10. The method for designing an eVTOL airborne navigation database according to claim 1, characterized in that: In step S13, the optimization method for storing the results includes: S131, for a file with a fixed database record size, using record numbers to randomly access records in the file; S132: Use shared memory to construct a database table, where the database table contains multiple database records.

Images