Low-altitude air route naming management method and device, air route management equipment and system

Abstract

This invention provides a method and apparatus for low-altitude airway naming and management, as well as airway management equipment and systems, relating to the field of low-altitude traffic management technology. The method includes: acquiring basic information about the target airway, including geographical location information, management entity information, technical specifications information, and safety requirements information; and generating a target airway code with a preset coding structure based on the basic information of the target airway. The preset coding structure includes a region code, a district / county code, a task type, a sequence number, and a check code. This invention, by employing a preset coding structure including a region code, district / county code, task type, sequence number, and check code when naming airways, achieves a refined airway management model of "one-code identification, precise positioning, and efficient management." Functionally, it realizes the standardization, intelligence, and efficiency of airway management, effectively solving core problems such as confusing airway identification, ambiguous permission division, and low scheduling efficiency.

Description

Technical Field

[0001] This invention relates to the field of low-altitude traffic management technology, and in particular to a method and apparatus for low-altitude route naming management, as well as route management equipment and systems. Background Technology

[0002] With the rapid development of low-altitude transportation and the increasing prevalence of drones, flying cars, and electric vertical takeoff and landing (eVTOL) aircraft, the demand for low-altitude airway networks has grown significantly, creating an urgent need for a specialized airway naming and management system. In the construction of urban air traffic systems, the extensive deployment of low-altitude airways adapted to different flight missions is crucial for optimizing urban airspace resource allocation and improving the efficiency of low-altitude transportation operations.

[0003] Currently, there is no unified standard for low-altitude airway naming rules, and the continued use of traditional high-altitude aviation naming standards has significant applicability issues. While traditional naming provides basic identification functions, it suffers from low information carrying efficiency and insufficient standardization, making it difficult to meet the technical requirements of refined low-altitude traffic management. Specifically: existing airway naming relies on simple alphanumeric combinations, limiting its information carrying capacity and failing to effectively distinguish key attributes such as geographical regions, mission types, and management levels; different regions and management departments use their own naming rules, lacking a unified standard, leading to poor system compatibility and difficulties in data exchange; airway coding lacks logic and scalability, making it difficult to adapt to rapid increases in the number of airways and easily causing coding conflicts; the existing coding system cannot effectively support hierarchical management and regional coordination of airways, affecting management efficiency; and the lack of standardized procedures for updating airway information easily leads to inconsistencies, impacting flight safety. These problems make it difficult for low-altitude traffic management departments to establish a unified and efficient airway management system, hindering accurate airway identification, rapid retrieval, and intelligent scheduling, severely restricting the standardized development of low-altitude traffic management systems.

[0004] Therefore, there is an urgent need for a unified, standardized, and scalable low-altitude airway naming rule and coding system to support the standardization and informatization of airway management for the future high-density urban air traffic network. Summary of the Invention

[0005] The purpose of this invention is to provide a low-altitude airway naming management method and apparatus, airway management equipment and system, so as to at least solve one of the problems existing in the current low-altitude airway naming system.

[0006] In a first aspect, the present invention provides a method for low-altitude airway naming management, comprising: Obtain basic information about the target route, including geographical location information, management entity information, technical specifications information, and safety requirements information; Based on the basic information of the target route, a target route code with a preset coding structure is generated; the preset coding structure includes a region code, a district / county code, a mission type, a sequence number, and a check code.

[0007] In an optional implementation, a target route code with a preset coding structure is generated based on the basic information of the target route, including: Based on the geographical location information and management entity information of the target route, generate the target area code and the target district / county code; Based on the management entity information, technical specifications information, and safety requirements information of the target route, generate the target mission type; Generate the target sequence number according to the preset generation algorithm; Generate a target verification code based on the target region code, target district / county code, target task type, and target sequence number; The target area code, target district / county code, target mission type, target sequence number, and target check code are combined according to the preset coding structure to obtain the current route code; Determine the target route code based on the current route code.

[0008] In an optional implementation, the target sequence number is generated according to a preset generation algorithm, including: Target serial numbers are generated sequentially, using a random algorithm, or based on timestamps.

[0009] In an optional implementation, a target verification code is generated based on the target region code, target county code, target task type, and target sequence number, including: After assigning values ​​to the target region code, target district / county code, and target task type respectively, the values ​​corresponding to the target sequence number are summed to obtain the total. Perform a modulo operation on the sum to obtain the target check code.

[0010] In an optional implementation, determining the target route code based on the current route code includes: Perform a validity check on the current route code and obtain the check result; If the verification result is unsuccessful, the step of generating the target sequence number according to the preset generation algorithm will be executed again. If the verification result is successful, the current route code will be determined as the target route code.

[0011] In an optional implementation, the validity of the current route code is verified to obtain the verification result, including: Perform a consistency check on the current route code based on the target check code; When the consistency check passes, the current route code is checked for duplication based on the real-time status information of the preset code library. If the repeatability check passes, the check result is determined to be passed. If the consistency check or the repeatability check fails, the check result is determined to be failed.

[0012] In an optional implementation, the region code and county code are both encoded with 2 letters, the task type and check code are both encoded with 1 letter, and the serial number is encoded with 4 digits.

[0013] Secondly, the present invention provides a low-altitude airway naming management device, comprising: The acquisition module is used to acquire basic information about the target route, including geographical location information, management entity information, technical specifications information, and safety requirements information. The generation module is used to generate a target route code with a preset coding structure based on the basic information of the target route; the preset coding structure includes a region code, district / county code, mission type, sequence number, and check code.

[0014] Thirdly, the present invention provides an airway management device, including a memory and a processor. The memory stores a computer program that can run on the processor. When the processor executes the computer program, it implements the low-altitude airway naming management method of any of the foregoing embodiments.

[0015] Fourthly, the present invention provides an airway management system, including multi-level airway management nodes based on administrative divisions, wherein the airway management nodes at each level are connected to form a multi-level information synchronization network; wherein the airway management nodes are used to provide airway naming services corresponding to the low-altitude airway naming management method of any of the foregoing embodiments and permission verification services using a hierarchical authorization mechanism.

[0016] The low-altitude airway naming management method, device, airway management equipment, and system provided by this invention include: acquiring basic information of the target airway, including geographical location information, management entity information, technical specifications information, and safety requirements information; generating a target airway code with a preset coding structure based on the basic information of the target airway; wherein the preset coding structure includes a region code, a district / county code, a task type, a sequence number, and a check code. In this way, when naming airways, a preset coding structure including a region code, a district / county code, a task type, a sequence number, and a check code is adopted, integrating functions such as geographical identification, management level, task type, airway sequence number, and verification mechanism into a unified airway code identifier. This achieves a unified expression of geographical location, management level, task type, and unique identity. Furthermore, through layered coding design and a built-in verification mechanism, it ensures that the airway code has structure, uniqueness, and verifiability, thereby realizing a refined airway management model of "one code identification, accurate positioning, and efficient management." Functionally, it achieves standardization, intelligence, and efficiency in airway management, effectively solving core problems such as confusing airway identity recognition, ambiguous permission division, and low scheduling efficiency. Attached Figure Description

[0017] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0018] Figure 1 A flowchart illustrating a low-altitude airway naming management method provided in an embodiment of the present invention; Figure 2 A flowchart illustrating another low-altitude airway naming management method provided in an embodiment of the present invention; Figure 3 A schematic diagram of a low-altitude airway naming management device provided in an embodiment of the present invention; Figure 4 This is a schematic diagram of the structure of an airway management device provided in an embodiment of the present invention. Detailed Implementation

[0019] The technical solution of the present invention will be clearly and completely described below with reference to the embodiments. Obviously, the described embodiments are only some embodiments of the present invention, and 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.

[0020] The embodiments of this invention aim to solve several key problems existing in the current low-altitude airway naming system, such as weak information carrying capacity, lack of unified coding standards, poor compatibility, and difficulty in supporting the refined operation of low-altitude traffic. Traditional airway naming methods mostly use simple character combinations, which cannot simultaneously express the geographical affiliation, mission attributes, management level, and unique identification information of an airway, and there are serious information silos and naming conflicts in cross-regional and cross-platform scheduling.

[0021] To overcome the aforementioned problems, this invention proposes a standardized naming rule and hierarchical coding system for the complex operating environment of low-altitude airspace. It constructs a five-layer fusion coding architecture (National Airway Identity Code, NAIC) centered on "regional code - district / county code - task type - sequence number - check code," and includes corresponding field structure definitions, coding generation rules, and verification mechanisms to ensure that each airway has a unique, clear, and verifiable identity. The regional code expresses geographical affiliation, the regional code and district / county code together express management level, the task type expresses task attributes, and the sequence number expresses unique identification information. Furthermore, this invention simultaneously establishes a hierarchical airway management mechanism based on administrative divisions, supporting dynamic generation, parsing, and decentralized authorization of airway codes, enabling seamless access and collaborative scheduling of airway data across different management levels. The overall system not only possesses excellent structured expression capabilities, scalability, and data consistency guarantees, but also effectively integrates with flight planning systems, scheduling platforms, and airspace layer systems, providing crucial technical support for the large-scale deployment and standardized operation of low-altitude transportation infrastructure. Decentralized authorization refers to the different permissions that route management nodes have for different mission types.

[0022] This invention provides a method and apparatus for low-altitude airway naming management, as well as airway management equipment and systems. It proposes a new naming rule and coding system for low-altitude airways, establishing a hierarchical low-altitude airway coding structure. Specifically, through the format of "regional code-county code-task type-serial number-check code," a unified naming standard and information coding system are provided for low-altitude airways, enabling accurate identification, classification management, and efficient scheduling of airways. This design significantly improves the standardization level and operational efficiency of low-altitude traffic management, and is particularly suitable for urban drone logistics delivery airway networks, dedicated emergency rescue airways, agricultural plant protection operation airways, and future low-altitude eVTOL (Electric Vertical Takeoff and Landing) and flying car airway planning and management scenarios.

[0023] To facilitate understanding of this embodiment, a low-altitude airway naming management method disclosed in this embodiment of the invention will first be described in detail.

[0024] This invention provides a method for low-altitude airway naming management, which can be executed by an electronic device with data processing capabilities (hereinafter referred to as an airway management device). See also Figure 1 The diagram shows a flowchart of a low-altitude airway naming management method, which mainly includes the following steps S110 to S120: Step S110: Obtain basic information about the target route, including geographical location information, management entity information, technical specifications information, and safety requirements information.

[0025] The aforementioned target airway is a requested name route. This can be an initial request for naming, or a route that needs renaming due to changes in mission type or administrative affiliation. Before generating the airway code, several key basic information needs to be obtained, including geographic location information, management entity information, technical specifications, and safety requirements. Geographic location information can include the geographic coordinates of different locations along the route, such as the longitude and latitude of key locations like the origin, destination, and waypoints. Management entity information can be the department or organization overseeing the airway. Technical specifications can include one or more of the following: altitude layer allocation, minimum offset distance, and speed limits. Safety requirements can include one or more of the following: meteorological conditions, communication requirements, and emergency procedures.

[0026] Step S120: Generate a target route code with a preset coding structure based on the basic information of the target route; wherein the preset coding structure includes a region code, a district / county code, a mission type, a sequence number, and a check code.

[0027] This embodiment proposes a low-altitude airway naming rule and coding system based on a hierarchical coding structure. The airway coding system is divided into four main functional layers, with the structure adapted to management needs and system compatibility. Geographic identifiers (corresponding to region codes and county codes), management levels (corresponding to region codes and county codes), task types, airway sequence numbers (corresponding to sequence numbers), and verification mechanisms (corresponding to check codes) are integrated into a unified airway coding identifier, constructing a five-layer fusion coding model of "region code - county code - task type - sequence number - check code". Specifically, region codes and county codes can be generated based on geographic location information and management entity information; task types can be generated based on management entity information, technical specifications, and safety requirements; sequence numbers can be generated based on a preset generation algorithm, which can be a sequential generation algorithm, a random algorithm, or a timestamp-based generation algorithm; and check codes can be generated based on region codes, county codes, task types, and sequence numbers to facilitate consistency verification of region codes, county codes, task types, and sequence numbers.

[0028] Optionally, the area code and county code both use 2-letter encoding, the task type and check digit both use 1-letter encoding, and the sequence number uses 4-digit numeric encoding. Regarding the encoding length, the total length of the route code can be set to 10 characters, following the format "XX-XX-X-XXXX-X", where the area code is 2 characters, the county code is 2 characters, the task type is 1 character, the sequence number is 4 characters, and the check digit is 1 character. The following factors were considered in determining this length: a) Information capacity optimization: Since the serial number part uses a 4-digit code, under the three-element combination of "regional code-county code-task type", each task type can support up to 9,999 unique route identifiers, which can support the route of each district / county task type and meet the needs of future continuous development. b) System compatibility: Standardized length facilitates database storage and data exchange between systems; c) Personnel identification: The appropriate code length makes it easy for managers to remember and use; d) Extended reservation: Reserve coding space for future new task types and special requirements.

[0029] In addition, for renamed routes, an old-new mapping relationship can be established based on the current target route code to ensure data consistency.

[0030] The low-altitude airway naming management method provided in this invention adopts a preset coding structure including regional code, district / county code, task type, sequence number, and check code when naming airways. It integrates functions such as geographic identification, management level, task type, airway sequence number, and verification mechanism into a unified airway code identifier, realizing a unified expression of geographic location, management level, task type, and unique identity. Furthermore, through hierarchical coding design and built-in verification mechanism, it ensures that the airway code has structure, uniqueness, and verifiability, thereby realizing a refined airway management mode of "one code identification, accurate positioning, and efficient management." Functionally, it achieves standardization, intelligence, and efficiency in airway management, effectively solving core problems such as confusion in airway identity recognition, ambiguous permission division, and low scheduling efficiency.

[0031] For ease of understanding, please refer to the following: Figure 2 The above-mentioned low-altitude airway naming management methods are described in detail. For example... Figure 2 As shown, the low-altitude airway naming management method may include the following steps: Step S210: Obtain the geographical location information, management entity information, technical specifications information, and safety requirements information of the target route.

[0032] Step S220: Generate the target region code and the target district / county code based on the geographical location information and management entity information of the target route.

[0033] The region code identifies the prefecture-level city or municipality to which the air route belongs, while the district / county code identifies the district / county administrative unit where the air route is located. Target region codes and target district / county codes can be generated based on geographic location information and management entity information, according to national or regional administrative division standards.

[0034] Step S230: Generate the target mission type based on the management entity information, technical specifications information, and safety requirements information of the target route.

[0035] The task type identifies the operational task category corresponding to the airway. The task type field supports expansion and currently includes, but is not limited to: "S" for Standard airway and "T" for Task-specific airway. Task types enable rapid classification and permission adaptation at the airway function level. Comprehensive analysis of management entity information, technical specifications, and security requirements yields the target task type, ensuring the safety, efficiency, and compliance of task execution.

[0036] Step S240: Generate the target sequence number according to the preset generation algorithm.

[0037] In one possible implementation, the target sequence number can be generated sequentially, using a random algorithm, or based on a timestamp. Specifically, sequential generation can be achieved through an auto-incrementing field in a database or by maintaining a counter; random generation can use random number generation functions in a programming language or directly use a UUID (Universally Unique Identifier) ​​library; and timestamp generation can be achieved in Java by using System.currentTimeMillis() to obtain the current timestamp and converting it to a 4-digit decimal number.

[0038] Step S250: Generate a target verification code based on the target region code, target district / county code, target task type, and target sequence number.

[0039] The check code is used to quickly verify the legality of the entire route code. The check code improves the error tolerance and information integrity of the code, and is suitable for scenarios involving automatic system identification and manual verification. The check code can be generated by numerical conversion and modulo operation on the characters of the basic code. Based on this, step S250 may include: assigning values ​​to the target area code, target district / county code, and target task type respectively, summing these values ​​with the values ​​corresponding to the target sequence number to obtain a total; and performing a modulo operation on the total to obtain the target check code. The modulo operation, also known as the modulo operation or remainder operation, refers to calculating the remainder after dividing one number by another.

[0040] In one possible implementation, the sum can be divided by 26 and the remainder can be taken: if the remainder is not equal to 0, the check code is the letter corresponding to the remainder (e.g., remainder = 3 → C); if the remainder is 0, the check code is directly set to "Z" (corresponding to the value 26).

[0041] Step S260: Combine the target area code, target district / county code, target mission type, target sequence number, and target check code according to the preset coding structure to obtain the current route code.

[0042] In one possible implementation, the current route code can be obtained by combining the target region code, target district / county code, target task type, target sequence number, and target checksum in that order. It should be noted that this embodiment does not impose a limitation on the order in which these parts are arranged.

[0043] Step S270: Determine the target route code based on the current route code.

[0044] In one possible implementation, the current route code can be directly used as the target route code.

[0045] In another possible implementation, in order to ensure the validity of the route code, the current route code can be validated to obtain the validation result; if the validation result is unsuccessful, the step of generating the target sequence number according to the preset generation algorithm is re-executed; if the validation result is successful, the current route code is determined as the target route code.

[0046] To ensure the consistency and uniqueness of route codes, during validity verification, the consistency of the current route code can be verified based on the target check code. When the consistency verification passes, the current route code is checked for duplication based on the real-time status information of the preset code library. When the duplication verification passes, the verification result is determined to be passed. When the consistency verification or the duplication verification fails, the verification result is determined to be failed.

[0047] The above-mentioned consistency verification process can be as follows: Based on the target area code, target district code, target mission type and target sequence number in the current route code, generate a check code according to the check code generation method and compare it with the target check code. If the two are consistent, the consistency verification passes; otherwise, the consistency verification fails.

[0048] The above-mentioned duplication verification process can be as follows: obtain the real-time status information of the preset coding library, and search in the preset coding library for a route code that is the same as the current route code. If it exists, the duplication verification fails; otherwise, if it does not exist, the duplication verification passes.

[0049] Furthermore, embodiments of the present invention also support dynamic code management, providing rapid response capabilities for handling emergencies or special tasks. In special circumstances, it supports temporary code allocation and emergency adjustments, providing rapid response and traceability management for emergency response and other special situations. In such cases, temporary route codes can be quickly generated according to actual needs and revoked after the event ends.

[0050] The embodiments of the present invention have the following beneficial effects: (1) High-efficiency route identification: Through the nationally unified standardized coding system (NAIC), the efficiency of route identification and retrieval can be significantly improved, avoiding scheduling bottlenecks caused by manual confirmation or system query delays. This coding system can be adapted to the operational needs of various low-altitude aircraft and supports unified management and rapid retrieval of routes of different scales and purposes.

[0051] (2) Multi-level management system: A five-layer integrated coding structure with "regional code - district / county code - task type - sequence number - check code" as the core is proposed, forming a top-down multi-level route management system. In this system, the regional code provides macro-regional identification, the district / county code realizes fine-grained geographic positioning, the task type clarifies the route's purpose category, the sequence number arrangement ensures the unique identification of similar routes, and the check code provides rapid verification and error prevention capabilities. This achieves synergistic optimization of rapid identification, accurate positioning, and hierarchical management.

[0052] (3) Three-level information management system: A three-level route information management system is constructed, consisting of basic coding information, extended attribute information (such as task types which can be further extended), and dynamic status information (dynamic status in management, such as support for temporary code allocation). Route attributes, technical parameters, and management requirements are uniformly incorporated into the coding identifier to achieve a "one code covering the entire route" management model. This system replaces the traditional mechanism that relies on multiple queries and manual confirmation, can meet the needs of rapid deployment and layout of high-density route networks, reduce management complexity and manual intervention costs, and further support standardized operation and intelligent scheduling.

[0053] (4) Unified Standards and Scalability: By relying on a nationally unified coding standard and hierarchical management synchronization mechanism, consistent management of airway information can be achieved across regions and departments (i.e., management departments corresponding to different task types), effectively eliminating airway identity confusion and management conflicts. The system adopts a scalable technical architecture, which can efficiently connect with core systems such as airspace management, flight planning, and traffic dispatching, providing standardized interfaces and information services for smart city air traffic management, and has good forward-looking and industrial application potential.

[0054] Corresponding to the aforementioned low-altitude airway naming management method, this embodiment of the invention also provides a low-altitude airway naming management device. See also... Figure 3 The diagram shows a structural schematic of a low-altitude airway naming management device, which includes: The acquisition module 301 is used to acquire basic information about the target route, including geographical location information, management entity information, technical specifications information, and safety requirements information. The generation module 302 is used to generate a target route code with a preset coding structure based on the basic information of the target route; wherein the preset coding structure includes a region code, a district / county code, a mission type, a sequence number, and a check code.

[0055] The low-altitude route naming management device provided in this invention adopts a preset coding structure including regional code, district / county code, task type, sequence number, and check code when naming routes. It integrates functions such as geographic identification, management level, task type, route sequence number, and verification mechanism into a unified route code identifier, realizing a unified expression of geographic location, management level, task type, and unique identity. Furthermore, through hierarchical coding design and built-in verification mechanism, it ensures that the route code has structure, uniqueness, and verifiability, thereby realizing a refined route management mode of "one code identification, accurate positioning, and efficient management." Functionally, it achieves standardization, intelligence, and efficiency in route management, effectively solving core problems such as route identity confusion, ambiguous permission division, and low scheduling efficiency.

[0056] Furthermore, the aforementioned generation module 302 is specifically used for: generating a target region code and a target county code based on the geographical location information and management entity information of the target route; generating a target task type based on the management entity information, technical specifications information, and safety requirements information of the target route; generating a target sequence number according to a preset generation algorithm; generating a target check code based on the target region code, target county code, target task type, and target sequence number; combining the target region code, target county code, target task type, target sequence number, and target check code according to a preset coding structure to obtain the current route code; and determining the target route code based on the current route code.

[0057] Furthermore, the aforementioned generation module 302 is also used to: generate target serial numbers in sequence, using a random algorithm, or based on timestamps.

[0058] Furthermore, the aforementioned generation module 302 is also used to: assign values ​​to the target region code, target district / county code, and target task type respectively, and then sum the values ​​corresponding to the target sequence number to obtain a total; and perform a modulo operation on the total to obtain the target verification code.

[0059] Furthermore, the aforementioned generation module 302 is also used to: perform validity verification on the current route code and obtain the verification result; when the verification result is unsuccessful, re-execute the step of generating the target sequence number according to the preset generation algorithm; when the verification result is successful, determine the current route code as the target route code.

[0060] Furthermore, the aforementioned generation module 302 is also used to: perform a consistency check on the current route code based on the target check code; when the consistency check passes, perform a repeatability check on the current route code based on the real-time status information of the preset code library; when the repeatability check passes, determine the check result as passed; when the consistency check fails or the repeatability check fails, determine the check result as failed.

[0061] Furthermore, the aforementioned region codes and district / county codes all use 2-letter encoding, the task type and check code both use 1-letter encoding, and the serial number uses 4-digit numeric encoding.

[0062] The low-altitude route naming management device provided in this embodiment has the same implementation principle and technical effects as the aforementioned low-altitude route naming management method embodiment. For the sake of brevity, any parts not mentioned in the low-altitude route naming management device embodiment can be referred to the corresponding content in the aforementioned low-altitude route naming management method embodiment.

[0063] like Figure 4 As shown, an embodiment of the present invention provides an airway management device 400, including: a processor 401, a memory 402 and a bus. The memory 402 stores a computer program that can run on the processor 401. When the airway management device 400 is running, the processor 401 and the memory 402 communicate through the bus. The processor 401 executes the computer program to implement the above-mentioned low-altitude airway naming management method.

[0064] Specifically, the memory 402 and processor 401 mentioned above can be general-purpose memory and processor, without any specific limitations here.

[0065] This invention also provides an airway management system, including multi-level airway management nodes based on administrative divisions, with each level of airway management nodes connected to form a multi-level information synchronization network; wherein, the airway management nodes are used to provide airway naming services corresponding to the aforementioned low-altitude airway naming management method and permission verification services using a hierarchical authorization mechanism.

[0066] For example, route management nodes can be divided into national-level management nodes, municipal-level management nodes, county-level management nodes, etc. National-level management nodes have the highest authority, and the management nodes at the next higher level have the management authority of the management nodes at the next lower level.

[0067] To meet the large-scale operational demands of future urban air traffic, this invention effectively addresses core issues such as route identification confusion, ambiguous permission division, and low scheduling efficiency. By constructing a nationally unified route coding and identification system (NAIC), along with a task type field mapping mechanism and automatic checksum calculation rules, and combined with hierarchical management and verification authorization mechanisms, it ensures standardized generation, uniqueness confirmation, and efficient sharing of route codes in complex airspace environments. This system supports rapid generation, parsing, querying, and dynamic updating of route codes, and can be widely applied to various scenarios such as urban low-altitude logistics route management, eVTOL operation scheduling, agricultural aerial plant protection operations, and emergency response route configuration. It possesses excellent scalability and engineering feasibility, providing a unified technical foundation for the informatization and intelligent upgrading of low-altitude transportation systems.

[0068] To address the core issues of insufficient information carrying capacity, inconsistent coding standards, and difficulty in supporting large-scale operation and management in the current low-altitude airway naming system, this invention proposes a standardized naming and coding method based on the National Unified Airway Code Identifier (NAIC). This system adopts a five-segment structure: "Regional Code - District / County Code - Mission Type - Sequence Number - Check Code," achieving a unified expression of geographical location (corresponding to the regional code and district / county code), airway purpose (corresponding to the mission type), mission type, and unique identity (corresponding to the sequence number). Through hierarchical coding design and a built-in verification mechanism, the airway code is ensured to possess structure, uniqueness, and verifiability. The specific coding generation process may include key steps such as parameter definition, structure allocation, mission type identification, sequence number generation, and check code calculation, which will be described in detail below.

[0069] (1) Parameters and definitions: 1) National Unified Airway Identification Code (NAIC): The hierarchical coding and identification system constructed at the core of this invention is used to uniquely identify each low-altitude airway. The coding structure adopts a five-segment combination of "regional code - district / county code - mission type - sequence number - check code" as the core carrier of airway information; 2) Regional Code: This is a two-letter identifier used to identify the prefecture-level city or municipality to which the route belongs. It can be an abbreviation of the first letter of its pinyin, such as "HZ" for Hangzhou. This field provides macro-geographical information about the route and supports cross-regional identification and management. 3) District Code: Consists of two uppercase English letters and is used to identify the district or county administrative unit where the route is located, such as "FY" representing Fuyang District; This field is used in conjunction with the area code to achieve fine-grained geographic positioning of the route and support the hierarchical control strategy of the route based on administrative divisions. 4) Task Type: Represented by a single uppercase letter, this field identifies the operational task category corresponding to the route. This field supports expansion and currently includes, but is not limited to: "S" for Standard route and "T" for Task-specific route, used to achieve rapid classification and permission adaptation at the route function level. 5) Serial Number: A 4-digit decimal number (0001–9999) used to distinguish specific routes under the same "region-county-mission type" combination, possessing uniqueness and scalability; 6) Check Code: Consists of a single uppercase letter, calculated from the first 9 digits of the code, and is used to quickly verify the legality of the entire route code; the check code improves the error tolerance and information integrity of the code, and is suitable for scenarios involving automatic system identification and manual verification. 7) Hierarchical Management Network: A multi-level information synchronization network formed by connecting airway management nodes at all levels. It builds a virtual management space based on the airway coding system and provides real-time status updates and access verification services.

[0070] (2) Standardized coding structure design: To achieve standardized, unique, and automated generation of route codes, this invention provides the following coding structure design process: 1) Obtain basic information about the target route; Before generating the code, key basic information about the target route needs to be collected, including but not limited to the route's geographical coordinates, management entity, technical specifications, and safety requirements. This information will be used for matching coding fields and subsequent task classification to ensure that route attributes are fully expressed in the coding system.

[0071] 2) Calculate the NAIC value; Public routes: NAIC = Area code (2 digits) + District / county code (2 digits) + Mission type (1 digit) + Sequence number (4 digits) + Check digit (1 digit); Dedicated mission route: NAIC = Region code (2 digits) + District code (2 digits) + Mission type (1 digit) + Sequence number (4 digits) + Check digit (1 digit); Task type identifier: "S": indicates a standard route, "T": indicates a task-specific route.

[0072] 3) Verification code generation method: To ensure the uniqueness and integrity of each route code and prevent misalignment or errors in route code information during exchange and transmission, this invention introduces a 1-bit letter-type "check code." This check code is generated by numerical conversion and modulo operation of the characters in the basic code portion, enabling rapid verification of the code's accuracy. The specific steps are as follows: Step 1: Assigning values ​​to letters. Assign values ​​to the 26 uppercase English letters in alphabetical order: A=1, B=2, C=3...Z=26. This converts the letters into calculable numerical values. Example: The code "HZ-FY-S" corresponds to the values ​​"H=8, Z=26, F=6, Y=25, S=19".

[0073] Step 2: Summation. Sum the first 5 letters and the last 4 serial numbers of the basic code to calculate the total.

[0074] Example: HZ-FY-S-0004=8+26+6+25+19+4=88.

[0075] Step 3: Calculate the check code. Divide the sum obtained above by 26 (the total number of letters), and take the remainder: if the remainder ≠ 0, the check letter is the letter corresponding to the remainder (e.g., remainder = 3 → C); if the remainder = 0, the check letter is directly set to "Z" (corresponding to the value 26). Example: The above sum 88 ÷ 26 = 3 remainder 10, the remainder 10 corresponds to the letter "J", so the complete code is "HZ-FY-S-0004-J".

[0076] 4) Encoding verification logic (verifying the validity of the encoding); After obtaining the 10-digit code, during decoding, take the first 9 basic letters, repeat "Step 1-Step 2" to calculate the sum, and then follow "Step 3" to obtain the check letter. Compare it with the last digit of the code: if they match, the code is valid; if they do not match, the code is invalid (there may be errors such as misspelled letters or reversed order, and you can be prompted to re-enter or review).

[0077] (3) Coding system design: The embodiments of the present invention divide the route coding system into four main functional layers, and the structure is adapted according to management requirements and system compatibility.

[0078] 1) Encoding length design; The total length of the route code is set to 10 characters, following the format "XX-XX-X-XXXX-X", including 2 digits for the area code, 2 digits for the district / county code, 1 digit for the mission type, 4 digits for the sequence number, and 1 digit for the check code.

[0079] 2) Categorized management adaptation mechanism; A tiered adaptation mechanism (based on regional and district / county codes) is established according to the route management hierarchy and actual application characteristics. Public routes (inter-city, inter-district, or important trunk routes) adopt a unified coding rule to facilitate unified management by relevant departments, and a local coding rule to support independent management. Dedicated mission routes (emergency, inspection, and other maneuver, special purposes, etc.) use dedicated identifiers to ensure access control and rapid identification. Each level of route uses the same coding format and management protocol, achieving precise adaptation to different management needs through differences in mission type identifiers.

[0080] 3) Dynamic coding management mechanism; Establish a coding allocation and uniqueness verification system. Uniqueness verification is automatically performed during code generation to avoid duplicate allocation. When the route mission type or management affiliation changes, new codes are automatically generated and an old-new mapping relationship is established to ensure data consistency. Access verification employs a hierarchical authorization mechanism (setting the scope of permissions based on the level of the route management node) to prevent code abuse and illegal route creation, ensuring the standardization and authority of the route coding system. Temporary code allocation and emergency adjustments are supported in special circumstances, providing rapid response and traceable management for handling emergencies and other special situations.

[0081] In summary, the low-altitude airway naming rules and coding system proposed in this invention establish a standardized naming and coding system centered on a nationally unified airway coding identifier, addressing the needs of large-scale low-altitude traffic operation and management. It adopts a hierarchical coding scheme integrating five layers: "regional code - district / county code - task type - sequence number - check code," achieving standardization, intelligence, and efficiency in airway management. This system fully adapts to the refined management characteristics of low-altitude traffic, significantly improving airway identification and scheduling efficiency, reducing management costs, and providing crucial technical support for the large-scale deployment of urban air traffic infrastructure. With the rapid development of low-altitude traffic, this coding system will play a vital role in future low-altitude airway planning and operation management.

[0082] This invention also provides a computer-readable storage medium storing a computer program. When a processor runs the computer program, it executes the low-altitude airway naming management method described in the preceding method embodiments. The computer-readable storage medium includes various media capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory (ROM), RAM, magnetic disk, or optical disk.

[0083] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" in this document means any combination of at least two of any one or more elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0084] In all examples shown and described herein, any specific values ​​should be interpreted as merely exemplary and not as limitations; therefore, other examples of exemplary embodiments may have different values.

[0085] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0086] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and there may be other division methods in actual implementation. Furthermore, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the coupling or direct coupling or communication connection shown or discussed may be through some communication interface; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0087] The modules described as separate components may or may not be physically separate. Similarly, the components shown as modules may or may not be physical modules; they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0088] In addition, the functional modules in the various embodiments of the present invention can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module.

[0089] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for naming and managing low-altitude airways, characterized in that, include: Obtain basic information about the target route, including geographical location information, management entity information, technical specifications information, and safety requirements information; Based on the basic information of the target route, a target route code with a preset coding structure is generated; wherein, the preset coding structure includes a region code, a district / county code, a mission type, a sequence number, and a check code.

2. The low-altitude airway naming management method according to claim 1, characterized in that, The step of generating a target route code with a preset coding structure based on the basic information of the target route includes: Based on the geographical location information and management entity information of the target route, generate the target area code and the target district / county code; Based on the management entity information, technical specifications information, and safety requirements information of the target route, generate the target mission type; Generate the target sequence number according to the preset generation algorithm; Generate a target verification code based on the target region code, the target district / county code, the target task type, and the target sequence number; The target region code, the target district / county code, the target mission type, the target sequence number, and the target check code are combined according to the preset coding structure to obtain the current route code; The target route code is determined based on the current route code.

3. The low-altitude airway naming management method according to claim 2, characterized in that, The step of generating the target sequence number according to the preset generation algorithm includes: The target serial number is generated sequentially, using a random algorithm, or based on a timestamp.

4. The low-altitude airway naming management method according to claim 2, characterized in that, The step of generating a target verification code based on the target region code, the target district / county code, the target task type, and the target sequence number includes: After assigning values ​​to the target region code, the target district / county code, and the target task type respectively, the sum is obtained by summing the values ​​corresponding to the target sequence number; The target check code is obtained by performing a modulo operation on the sum.

5. The low-altitude airway naming management method according to claim 2, characterized in that, Determining the target route code based on the current route code includes: The validity of the current route code is verified, and the verification result is obtained; If the verification result is unsuccessful, the step of generating the target serial number according to the preset generation algorithm is re-executed; When the verification result is successful, the current route code is determined as the target route code.

6. The low-altitude airway naming management method according to claim 5, characterized in that, The validity verification of the current route code, to obtain the verification result, includes: Perform a consistency check on the current route code based on the target check code; When the consistency check passes, the current route code is checked for duplication based on the real-time status information of the preset coding library. When the repeatability check passes, the check result is determined to be passed; If the consistency check or the repeatability check fails, the check result is determined to be unsuccessful.

7. The low-altitude airway naming management method according to any one of claims 1-6, characterized in that, The region code and the district / county code both use 2-letter encoding, the task type and the check code both use 1-letter encoding, and the serial number uses 4-digit numeric encoding.

8. A low-altitude airway naming and management device, characterized in that, include: The acquisition module is used to acquire basic information about the target route, including geographical location information, management entity information, technical specifications information, and safety requirements information. The generation module is used to generate a target route code with a preset coding structure based on the basic information of the target route; wherein the preset coding structure includes a region code, a district / county code, a mission type, a sequence number, and a check code.

9. A route management device, comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, characterized in that, When the processor executes the computer program, it implements the low-altitude airway naming management method according to any one of claims 1-7.

10. A route management system, characterized in that, It includes multi-level airway management nodes based on administrative divisions, and the airway management nodes at each level are connected to form a multi-level information synchronization network; wherein, the airway management nodes are used to provide airway naming services and permission verification services using a hierarchical authorization mechanism corresponding to the low-altitude airway naming management method of any one of claims 1-7.

Images