Low-altitude airspace no-fly zone dividing method and device

Abstract

The invention relates to the technical field of no-fly zone division, and provides a low-altitude airspace no-fly zone division method and device. The method comprises the following steps: identifying a thunderstorm area in a target low-altitude airspace; extracting an intersection area between the thunderstorm area and an air traffic control system management area; generating a convex polygon region containing the intersection region; and determining a no-fly zone in the target low-altitude airspace based on the convex polygon area. According to the invention, the machine automatically responds in real time in the whole process, and thunderstorm region identification on all flight paths within the management range of the target low-altitude airspace hollow pipe system can be completely covered, so that the sudden thunderstorm weather and high-frequency multi-path flight of the aircraft can be effectively dealt with; therefore, thunderstorm no-fly zone division is carried out on the flight route of the aircraft in each path in time, the flight safety of the aircraft is ensured, a large number of professionals are not needed to carry out continuous monitoring and decision making, and the manpower and operation cost is effectively reduced.

Description

Technical Field

[0001] This application relates to the technical field of no-fly zone delineation, specifically to a method and apparatus for delineating low-altitude airspace no-fly zones. Background Art

[0002] With the development of the low-altitude economy, low-altitude aircraft such as drones have also developed rapidly in fields such as agricultural plant protection, power line inspection, emergency rescue, and logistics transportation. As a result, their operating environment has become increasingly complex, and the possibility of encountering extreme weather such as thunderstorms has increased significantly.

[0003] Thunderstorms are often accompanied by severe convective weather, such as sudden gusts, strong vertical airflow, heavy precipitation, hail, and strong electromagnetic interference. These factors can easily cause aircraft to lose attitude, interrupt navigation signals, damage communication links, or even crash.

[0004] Therefore, the impact of thunderstorms needs to be fully considered in the flight route planning of aircraft to avoid them entering thunderstorm areas. However, the current response process of low-altitude air traffic control systems to thunderstorms is mainly manual. On the one hand, thunderstorms often occur suddenly, and aircraft have the characteristics of high-frequency, multi-path flight. Manual response is limited by human reaction speed and workload. When faced with sudden thunderstorm events, it is difficult to promptly delineate no-fly zones for aircraft on various paths, thus affecting the safe flight of aircraft. On the other hand, in order to cover a wide range of low-altitude airspace and frequent flight activities, a large number of professionals are needed for continuous monitoring and decision-making, which consumes a lot of manpower and operating costs.

[0005] In summary, existing manual response methods for thunderstorms are insufficient for timely designation of no-fly zones for aircraft along their flight paths, thus affecting safe flight. Furthermore, they require a large number of professionals for continuous monitoring and decision-making, resulting in significant manpower and operational costs. Summary of the Invention

[0006] This application provides a method and apparatus for delineating no-fly zones in low-altitude airspace, which solves the technical problem that existing manual response methods for thunderstorms are difficult to delineate no-fly zones for aircraft on various flight paths in a timely manner, thus affecting the safe flight of aircraft, and require a large number of professionals for continuous monitoring and decision-making, which consumes a lot of manpower and operating costs.

[0007] In a first aspect, embodiments of this application provide a method for delineating a low-altitude airspace no-fly zone, including: Identify thunderstorm areas within the target's low-altitude airspace; Extract the intersection area between the thunderstorm area and the air traffic control system management area; Generate a convex polygonal region that includes the intersection region; Based on the convex polygon region, a no-fly zone is determined within the target low-altitude airspace.

[0008] In one embodiment, generating the convex polygonal region containing the intersection region includes: Outside the intersection region, multiple first sampling points are obtained around the intersection region; The plurality of first sampling points are connected sequentially as vertices of a convex polygon to obtain the convex polygon region.

[0009] In one embodiment, determining the no-fly zone within the target low-altitude airspace based on the convex polygon region includes: Uniform sampling is performed on the boundary of the convex polygonal region to obtain multiple second sampling points; By sequentially connecting the multiple second sampling points, a static no-fly zone within the target low-altitude airspace is obtained.

[0010] In one embodiment, the step of uniformly sampling along the boundary of the convex polygonal region to obtain multiple second sampling points includes: Determine the target number of samples for the second sampling point; The sampling step size of the second sampling point is determined based on the ratio between the number of the plurality of first sampling points and the target sampling number; For the first sampling point on the boundary of the convex polygon region, the last first sampling point within the sampling step is obtained as the second sampling point at each sampling step, thus obtaining the second sampling point.

[0011] In one embodiment, obtaining the static no-fly zone within the target low-altitude airspace includes: Obtain the update frequency of thunderstorm meteorological data within the static no-fly zone; The static no-fly zone is linearly extended according to the update frequency to obtain the dynamic no-fly zone within the target low-altitude airspace.

[0012] In one embodiment, the step of linearly extending the static no-fly zone according to the update frequency to obtain the dynamic no-fly zone within the target low-altitude airspace includes: Obtain the moving speed and direction of the thunderstorm area within the static no-fly zone; Based on the moving speed and the update frequency, the expected moving distance of the static no-fly zone is obtained; After extending the static no-fly zone to the expected moving distance in the moving direction according to the update frequency, return to the step of obtaining the moving speed and moving direction of the thunderstorm area within the static no-fly zone, until the static no-fly zone is located outside the air traffic control system management area or outside the target low-altitude airspace; The static no-fly zone that moves along the promotion path will be designated as the dynamic no-fly zone.

[0013] Secondly, embodiments of this application provide a device for demarcating low-altitude no-fly zones, comprising: Thunderstorm area identification module, used to: identify thunderstorm areas within the target's low-altitude airspace; The intersection region extraction module is used to: extract the intersection region between the thunderstorm region and the air traffic control system management region; A convex polygon region generation module is used to: generate a convex polygon region containing the intersection region; The no-fly zone determination module is used to: determine the no-fly zone within the target low-altitude airspace based on the convex polygon region.

[0014] Thirdly, embodiments of this application provide an electronic device, including a processor and a memory storing a computer program, wherein the processor executes the program to implement the steps of the low-altitude airspace no-fly zone delineation method described in the first aspect.

[0015] Fourthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the steps of the low-altitude airspace no-fly zone delineation method described in the first aspect.

[0016] Fifthly, embodiments of this application provide a non-transitory computer-readable storage medium, including a computer program, which, when executed by a processor, implements the steps of the low-altitude airspace no-fly zone demarcation method described in the first aspect.

[0017] The method and apparatus for delineating no-fly zones in low-altitude airspace provided in this application identify thunderstorm areas within a target low-altitude airspace, extract the intersection area between the thunderstorm area and the air traffic control system's management area, generate a convex polygon area containing the intersection area, and determine the no-fly zone within the target low-altitude airspace based on the convex polygon area. This application avoids regional bias during intersection area extraction by extracting the intersection area between the thunderstorm area and the air traffic control system's management area, and then uses a convex polygon to enclose this intersection area, thus obtaining as complete a thunderstorm area as possible within the air traffic control system's management range. Therefore, the no-fly zone within the target low-altitude airspace can be accurately determined based on this convex polygon area. This application features fully automated, real-time machine response and can completely cover the identification of thunderstorm areas on all flight paths within the air traffic control system's management range in the target low-altitude airspace. Therefore, it can effectively cope with the suddenness of thunderstorm weather and the high-frequency, multi-path flight of aircraft, thereby promptly delineating no-fly zones for each flight path, ensuring flight safety, and eliminating the need for continuous monitoring and decision-making by a large number of professionals, effectively reducing manpower and operating costs. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is one of the flowcharts illustrating the method for delineating low-altitude no-fly zones provided in this application embodiment; Figure 2 This is the second flowchart illustrating the method for delineating low-altitude no-fly zones provided in this application embodiment; Figure 3 This is the third flowchart illustrating the method for delineating low-altitude no-fly zones provided in this application embodiment; Figure 4 This is the fourth flowchart illustrating the method for delineating low-altitude no-fly zones provided in this application embodiment; Figure 5 This is the fifth flowchart illustrating the method for delineating low-altitude no-fly zones provided in this application embodiment; Figure 6 This is a schematic diagram of the structure of the low-altitude airspace no-fly zone demarcation device provided in the embodiments of this application; Figure 7 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0021] It should be noted that in the description of the embodiments of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element. The terms "upper," "lower," etc., indicating orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this application. Unless otherwise expressly specified and limited, the terms "installed," "connected," and "linked" should be interpreted broadly, for example, they can be fixed connections, detachable connections, or integral connections; they can be mechanical connections or electrical connections; they can be direct connections or indirect connections through an intermediate medium; and they can be internal connections between two elements. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0022] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class, without limiting the number of objects; for example, a first object can be one or more. Furthermore, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects have an "or" relationship.

[0023] Figure 1 This is one of the flowcharts illustrating the method for delineating low-altitude airspace no-fly zones provided in this application embodiment; see reference. Figure 1 This application provides a method for delineating a low-altitude airspace no-fly zone, which may include: 101. Identify thunderstorm areas within the target's low-altitude airspace; 102. Extract the intersection area between the thunderstorm area and the air traffic control system management area; 103. Generate a convex polygon region containing intersecting areas; 104. Based on the convex polygon region, determine the no-fly zone within the target's low-altitude airspace.

[0024] In step 101, while identifying the thunderstorm area, meteorological data such as the movement speed and direction of the thunderstorm area, the latitude and longitude coordinates of the area boundary points, and the altitude of the area center can also be obtained.

[0025] In step 102, since the target low-altitude airspace may not be entirely within the management range of the air traffic control system, if the thunderstorm area is outside the management range of the air traffic control system, the air traffic control system will not be able to respond to it. Therefore, the intersection area between the thunderstorm area and the management area of ​​the air traffic control system can be extracted based on the latitude and longitude coordinates of the boundary point of the thunderstorm area and the center height of the thunderstorm area to determine the thunderstorm area within the management range of the air traffic control system.

[0026] In step 103, in order to prevent deviations during the extraction of the intersection region or the sudden overflow of the thunderstorm region, a convex polygon region that can completely cover the intersection region is generated. That is, the range of the intersection region is appropriately expanded and a certain safety margin is provided to avoid missing thunderstorm regions outside the intersection region due to extraction deviations within the air traffic control system management area, or incorrectly identifying thunderstorm overflow areas as safe areas.

[0027] In step 104, the convex polygonal region can cover the thunderstorm area within the air traffic control system's management range relatively completely and accurately, and simultaneously considers the area expansion due to the suddenness of thunderstorms. Therefore, it can accurately determine the thunderstorm no-fly zone within the target low-altitude airspace and ensure flight safety.

[0028] The low-altitude no-fly zone delineation method provided in this embodiment identifies thunderstorm areas within the target low-altitude airspace, extracts the intersection area between the thunderstorm area and the air traffic control system's management area, generates a convex polygon region containing the intersection area, and determines the no-fly zone within the target low-altitude airspace based on the convex polygon region. This embodiment extracts the intersection area between the thunderstorm area and the air traffic control system's management area, and then uses a convex polygon to enclose this intersection area to avoid regional deviations during the extraction of the intersection area, obtaining as complete a thunderstorm area as possible within the air traffic control system's management range. Therefore, the no-fly zone within the target low-altitude airspace can be accurately determined based on this convex polygon region. This embodiment features fully automated, real-time machine response and can completely cover the identification of thunderstorm areas on all flight paths within the air traffic control system's management range in the target low-altitude airspace. Therefore, it can effectively cope with the suddenness of thunderstorm weather and the high-frequency, multi-path flight of aircraft, thereby promptly delineating thunderstorm no-fly zones for the flight routes of aircraft on each path, ensuring flight safety, and effectively reducing manpower and operating costs by eliminating the need for continuous monitoring and decision-making by a large number of professionals.

[0029] Furthermore, the timely and accurate establishment of no-fly zones during thunderstorms can help air traffic control systems adjust aircraft routes in real time and improve their emergency response capabilities.

[0030] Figure 2 This is the second flowchart illustrating the method for delineating low-altitude no-fly zones provided in this application; see also... Figure 2 In one embodiment, generating a convex polygonal region containing intersecting regions may include: 201. Outside the intersection region, obtain multiple first sampling points around the intersection region; 202. Connect multiple first sampling points as vertices of a convex polygon in sequence to obtain a convex polygon region.

[0031] In step 201, the distance between the first sampling point and the intersection area can be preset to a moderate value to avoid covering the safe area due to the distance being too far, or failing to achieve the effect of area expansion due to the distance being too close.

[0032] In addition, the number of first sampling points can be as large as possible, so that the clear boundary outline formed by the first sampling points helps to determine the expanded region.

[0033] In step 202, a convex polygon means that all its interior angles are less than 180 degrees. When connecting multiple first sampling points in sequence, if a first sampling point that does not meet this condition is found, it is discarded and then reconnected.

[0034] In this embodiment, by obtaining multiple first sampling points around the intersection region and connecting them sequentially, a convex polygonal region that completely covers the intersection region can be obtained conveniently and quickly.

[0035] Figure 3 This is the third flowchart illustrating the method for delineating low-altitude no-fly zones provided in this application; see also... Figure 3 In one embodiment, determining a no-fly zone within the target low-altitude airspace based on a convex polygon region may include: 301. Perform uniform sampling on the boundary of the convex polygon region to obtain multiple second sampling points; 302. Connect multiple second sampling points in sequence to obtain the static no-fly zone within the target low-altitude airspace.

[0036] Since the boundary of the convex polygon region is obtained by connecting multiple first sampling points in sequence, and there may be multiple sampling points clustered in the same place among the first sampling points, these clustered sampling points have similar features and do not need to be retained. Therefore, uniform sampling can be carried out in multiple first sampling points. On the one hand, the vertex features of the first sampling points can be retained to the maximum extent to maintain the shape of the convex polygon region formed by the first sampling points. On the other hand, the number of sampling points at the boundary can be simplified, and the recognition efficiency of static no-fly zones can be improved.

[0037] This embodiment simplifies the number of sampling points on the boundary of the convex polygon region, thereby improving the identification efficiency of static no-fly zones while maintaining the original shape of the convex polygon region. This greatly reduces the calculation difficulty for subsequent adjustments to aircraft flight paths in static no-fly zones and improves the efficiency of flight path adjustments.

[0038] Figure 4 This is the fourth flowchart illustrating the method for delineating low-altitude no-fly zones provided in this application; see also... Figure 4 In one embodiment, uniform sampling is performed on the boundary of the convex polygon region to obtain multiple second sampling points, which may include: 401. Determine the target number of samples for the second sampling point; 402. Determine the sampling step size of the second sampling point based on the ratio between the number of multiple first sampling points and the target sampling number; 403. For the first sampling point on the boundary of the convex polygon region, the last first sampling point within each sampling step is taken as the second sampling point to obtain the second sampling point.

[0039] In step 401, the number of the first sampling points and the number of the second sampling points are generally one order of magnitude different. For example, the number of the first sampling points is several hundred and the number of the second sampling points is several tens. In this embodiment, the number of the second sampling points can be set to less than 10, that is, the target sampling number does not exceed 10.

[0040] In step 402, assuming the number of first sampling points is 500 and the target sampling number is 10, the ratio of the two is 50, that is, the sampling step size of the second sampling point is 50.

[0041] In step 403, every 50 first sampling points out of the 500 first sampling points, the last first sampling point among these 50 first sampling points is taken as the second sampling point. For example, the 50th, 100th, 150th, 200th, 250th, 300th, 350th, 400th, 450th and 500th first sampling points, these 10 first sampling points are the second sampling points.

[0042] It should be noted that sometimes the ratio between the number of first sampling points and the target number of sampling points is not an integer. In this case, the ratio can be rounded up before obtaining the second sampling point. For example, if the number of first sampling points is 300 and the target number of sampling points is 8, the ratio, after rounding up, is 38. Therefore, the sampling step size of the second sampling point is 38. The 38th, 76th, 114th, 152nd, 190th, 228th, and 266th first sampling points out of the 500 first sampling points are obtained as second sampling points. It can be seen that, due to rounding up, the final number of second sampling points is 7, instead of the target number of 8. However, this is sufficient to maintain the shape of the original convex polygon region and can further improve the recognition efficiency of static no-fly zones.

[0043] This embodiment calculates the ratio between the number of first sampling points and the target number of second sampling points, and determines this ratio as the sampling step size. Sampling is performed at the first sampling points, which can collect evenly distributed second sampling points from the first sampling points. This helps to maintain the shape of the original convex polygon area to the maximum extent with as few sampling points as possible, and improves the recognition efficiency of static no-fly zones.

[0044] Figure 5 This is the fifth flowchart illustrating the method for delineating low-altitude no-fly zones provided in this application; see also... Figure 5 In one embodiment, after obtaining the static no-fly zone within the target low-altitude airspace, the following may be included: 501. Obtain the update frequency of thunderstorm meteorological data within the static no-fly zone; 502. By linearly extending the static no-fly zone according to the update frequency, a dynamic no-fly zone within the target low-altitude airspace is obtained.

[0045] In step 501, the thunderstorm meteorological data can be meteorological data such as the movement speed and direction of the thunderstorm area, the latitude and longitude coordinates of the boundary points of the area, and the altitude of the center of the area. Its update frequency can be set to once every n minutes.

[0046] Step 502 is as follows: 502a. Obtain the movement speed and direction of the thunderstorm area within the static no-fly zone; 502b. Based on the movement speed and update frequency, the expected movement distance of the static no-fly zone is obtained; 502c. After extending the static no-fly zone by the expected distance in the direction of movement according to the update frequency, return to step 502a until the static no-fly zone is located outside the air traffic control system's management area or outside the target low-altitude airspace. 502d. Static no-fly zones that move along the promotion path will be designated as dynamic no-fly zones.

[0047] Step 502b: Convert the movement speed of the thunderstorm area to m kilometers per minute, then the expected movement distance of the thunderstorm area in the next update will be m. n kilometers.

[0048] In steps 502c to 502d, the current static no-fly zone can be moved m in the direction of the thunderstorm area. The area swept by the static no-fly zone over a distance of n kilometers is the promotion path of the static no-fly zone before the next update. By repeating the above steps, the continuously extending promotion path of the static no-fly zone can be obtained. The static no-fly zone that moves continuously in the promotion path is the dynamic no-fly zone.

[0049] This embodiment, based on the static no-fly zone, uses thunderstorm meteorological data and its update frequency to perform route simulations for the static no-fly zone. This allows for timely response to real-time changes in the thunderstorm area, obtaining dynamic changes in the static no-fly zone to determine the dynamic no-fly zone, and further providing a real-time response basis for the air traffic control system to adjust aircraft routes.

[0050] The following describes the low-altitude no-fly zone demarcation device provided in the embodiments of this application. The low-altitude no-fly zone demarcation device described below and the low-altitude no-fly zone demarcation method described above can be referred to in correspondence with each other.

[0051] Figure 6 This is a schematic diagram of the low-altitude airspace no-fly zone demarcation device provided in an embodiment of this application. (Refer to...) Figure 6 This application provides a device for delineating low-altitude no-fly zones, which may include: Thunderstorm area identification module 601 is used to: identify thunderstorm areas within the target's low-altitude airspace; The intersection region extraction module 602 is used to: extract the intersection region between the thunderstorm region and the air traffic control system management region; The convex polygon region generation module 603 is used to: generate a convex polygon region containing the intersection region; The no-fly zone determination module 604 is used to: determine the no-fly zone within the target low-altitude airspace based on the convex polygon region.

[0052] The low-altitude no-fly zone delineation device provided in this embodiment identifies thunderstorm areas within the target low-altitude airspace, extracts the intersection area between the thunderstorm area and the air traffic control system's managed area, generates a convex polygon region containing the intersection area, and determines the no-fly zone within the target low-altitude airspace based on the convex polygon region. This embodiment extracts the intersection area between the thunderstorm area and the air traffic control system's managed area, and then uses a convex polygon to enclose this intersection area to avoid regional deviations during the extraction of the intersection area, obtaining as complete a thunderstorm area as possible within the air traffic control system's managed area. Therefore, the no-fly zone within the target low-altitude airspace can be accurately determined based on this convex polygon region. This embodiment features fully automated, real-time machine response and can completely cover the identification of thunderstorm areas on all flight paths within the air traffic control system's managed area in the target low-altitude airspace. Therefore, it can effectively cope with the suddenness of thunderstorm weather and the high-frequency, multi-path flight of aircraft, thereby promptly delineating thunderstorm no-fly zones for the flight routes of aircraft on each path, ensuring flight safety, and eliminating the need for continuous monitoring and decision-making by a large number of professionals, effectively reducing manpower and operating costs.

[0053] In one embodiment, the convex polygon region generation module 603 is specifically used for: Outside the intersection region, multiple first sampling points are obtained around the intersection region; The plurality of first sampling points are connected sequentially as vertices of a convex polygon to obtain the convex polygon region.

[0054] In one embodiment, the no-fly zone determination module 604 is specifically used for: Uniform sampling is performed on the boundary of the convex polygonal region to obtain multiple second sampling points; By sequentially connecting the multiple second sampling points, a static no-fly zone within the target low-altitude airspace is obtained.

[0055] In one embodiment, the no-fly zone determination module 604 is specifically used for: Determine the target number of samples for the second sampling point; The sampling step size of the second sampling point is determined based on the ratio between the number of the plurality of first sampling points and the target sampling number; For the first sampling point on the boundary of the convex polygon region, the last first sampling point within the sampling step is obtained as the second sampling point at each sampling step, thus obtaining the second sampling point.

[0056] In one embodiment, a dynamic no-fly zone delineation module (not shown in the figure) is also included, for: Obtain the update frequency of thunderstorm meteorological data within the static no-fly zone; The static no-fly zone is linearly extended according to the update frequency to obtain the dynamic no-fly zone within the target low-altitude airspace.

[0057] In one embodiment, the dynamic no-fly zone delineation module is specifically used for: Obtain the moving speed and direction of the thunderstorm area within the static no-fly zone; Based on the moving speed and the update frequency, the expected moving distance of the static no-fly zone is obtained; After extending the static no-fly zone to the expected moving distance in the moving direction according to the update frequency, return to the step of obtaining the moving speed and moving direction of the thunderstorm area within the static no-fly zone, until the static no-fly zone is located outside the air traffic control system management area or outside the target low-altitude airspace; The static no-fly zone that moves along the promotion path will be designated as the dynamic no-fly zone.

[0058] Figure 7 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application, such as... Figure 7 As shown, the electronic device may include: a processor 710, a communication interface 720, a memory 730, and a communication bus 740, wherein the processor 710, the communication interface 720, and the memory 730 communicate with each other via the communication bus 740. The processor 710 can call the computer program in the memory 730 to execute the steps of the method for delineating low-altitude airspace no-fly zones, such as: Identify thunderstorm areas within the target's low-altitude airspace; Extract the intersection area between the thunderstorm area and the air traffic control system management area; Generate a convex polygonal region that includes the intersection region; Based on the convex polygon region, a no-fly zone is determined within the target low-altitude airspace.

[0059] Furthermore, the logical instructions in the aforementioned memory 730 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0060] On the other hand, this application also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can perform the steps of the low-altitude airspace no-fly zone demarcation method provided in the above embodiments, such as including: Identify thunderstorm areas within the target's low-altitude airspace; Extract the intersection area between the thunderstorm area and the air traffic control system management area; Generate a convex polygonal region that includes the intersection region; Based on the convex polygon region, a no-fly zone is determined within the target low-altitude airspace.

[0061] On the other hand, embodiments of this application also provide a non-transitory computer-readable storage medium storing a computer program thereon. The computer program is used to cause a processor to execute the steps of the low-altitude airspace no-fly zone demarcation method provided in the above embodiments, including, for example: Identify thunderstorm areas within the target's low-altitude airspace; Extract the intersection area between the thunderstorm area and the air traffic control system management area; Generate a convex polygonal region that includes the intersection region; Based on the convex polygon region, a no-fly zone is determined within the target low-altitude airspace.

[0062] The non-transitory computer-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0063] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0064] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0065] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application 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 of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for delineating no-fly zones in low-altitude airspace, characterized in that, include: Identify thunderstorm areas within the target's low-altitude airspace; Extract the intersection area between the thunderstorm area and the air traffic control system management area; Generate a convex polygonal region that includes the intersection region; Based on the convex polygon region, a no-fly zone is determined within the target low-altitude airspace.

2. The method for delineating low-altitude airspace no-fly zones according to claim 1, characterized in that, The generation of the convex polygon region containing the intersection region includes: Outside the intersection region, multiple first sampling points are obtained around the intersection region; The plurality of first sampling points are connected sequentially as vertices of a convex polygon to obtain the convex polygon region.

3. The method for delineating low-altitude airspace no-fly zones according to claim 2, characterized in that, The step of determining the no-fly zone within the target low-altitude airspace based on the convex polygon region includes: Uniform sampling is performed on the boundary of the convex polygonal region to obtain multiple second sampling points; By sequentially connecting the multiple second sampling points, a static no-fly zone within the target low-altitude airspace is obtained.

4. The method for delineating low-altitude airspace no-fly zones according to claim 3, characterized in that, The process involves uniformly sampling along the boundary of the convex polygon region to obtain multiple second sampling points, including: Determine the target number of samples for the second sampling point; The sampling step size of the second sampling point is determined based on the ratio between the number of the plurality of first sampling points and the target sampling number; For the first sampling point on the boundary of the convex polygon region, the last first sampling point within the sampling step is obtained as the second sampling point at each sampling step, thus obtaining the second sampling point.

5. The method for delineating low-altitude airspace no-fly zones according to claim 3, characterized in that, After obtaining the static no-fly zone within the target low-altitude airspace, the process includes: Obtain the update frequency of thunderstorm meteorological data within the static no-fly zone; The static no-fly zone is linearly extended according to the update frequency to obtain the dynamic no-fly zone within the target low-altitude airspace.

6. The method for delineating low-altitude airspace no-fly zones according to claim 5, characterized in that, The step of linearly extending the static no-fly zone according to the update frequency to obtain the dynamic no-fly zone within the target low-altitude airspace includes: Obtain the moving speed and direction of the thunderstorm area within the static no-fly zone; Based on the moving speed and the update frequency, the expected moving distance of the static no-fly zone is obtained; After extending the static no-fly zone to the expected moving distance in the moving direction according to the update frequency, return to the step of obtaining the moving speed and moving direction of the thunderstorm area within the static no-fly zone, until the static no-fly zone is located outside the air traffic control system management area or outside the target low-altitude airspace; The static no-fly zone that moves along the promotion path will be designated as the dynamic no-fly zone.

7. A device for delineating no-fly zones in low-altitude airspace, characterized in that, include: Thunderstorm area identification module, used to: identify thunderstorm areas within the target's low-altitude airspace; The intersection region extraction module is used to: extract the intersection region between the thunderstorm region and the air traffic control system management region; A convex polygon region generation module is used to: generate a convex polygon region containing the intersection region; The no-fly zone determination module is used to: determine the no-fly zone within the target low-altitude airspace based on the convex polygon region.

8. An electronic device comprising a processor and a memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method for delineating low-altitude no-fly zones according to any one of claims 1 to 6.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the method for delineating low-altitude airspace no-fly zones as described in any one of claims 1 to 6.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the method for delineating low-altitude airspace no-fly zones as described in any one of claims 1 to 6.

Images