A route planning method and device based on military-civilian-ground collaborative management platform

Abstract

The present application discloses a route planning method and device based on a military-civilian-ground collaborative management platform. The method obtains a takeoff request from a drone, determines the operator corresponding to the takeoff request, and determines whether the operator corresponding to the takeoff request supports cross-regional flight. If so, the takeoff request is sent to the military-civilian-ground collaborative management platform for the military-civilian-ground collaborative management platform to determine and plan a route based on the takeoff request. The present application determines the corresponding operator through the drone's takeoff request, further determines whether the operator supports cross-regional flight, and achieves dual protection for cross-regional flight through dual right confirmation, further preventing cross-regional drone flight from disrupting normal flight routes. At the same time, the safety of cross-regional drone flight is improved by determining the planned route through the military-civilian-ground collaborative management platform.

Description

Technical Field

[0001] The present application relates to the field of UAV route planning, and in particular to a route planning method and device based on a military-civilian-ground collaborative management platform. Background Art

[0002] In the fields of military aviation, civil aviation, and drone aviation, space management issues are particularly important. In particular, the number of aircraft in the low-altitude area is increasing, and the flight routes are complex, making route planning calculations increasingly difficult. Among them, cross-regional flights achieved through a military-civilian-ground collaborative management platform can greatly improve flight efficiency.

[0003] The existing military-civilian-local collaborative management platform organically combines the resources and capabilities of the military, civil aviation, local governments and other departments through various information technology means to achieve information sharing, command coordination and resource optimization. While ensuring efficient flight transportation, how to improve the safety of cross-regional flights of various operators is a concern for people. Summary of the Invention

[0004] In view of this, this application provides a route planning method based on a military-civilian-ground collaborative management platform to improve the safety of UAV cross-regional flights.

[0005] In order to achieve the above objectives, the following solutions are proposed:

[0006] A route planning method based on a military-civilian-ground collaborative management platform includes:

[0007] Get the drone's takeoff request;

[0008] determining an operator corresponding to the takeoff request;

[0009] Determining whether the operator corresponding to the takeoff request supports cross-region flights;

[0010] If so, a takeoff request is sent to the military-civilian-ground collaborative management platform, so that the military-civilian-ground collaborative management platform can determine the planned route according to the takeoff request.

[0011] Optionally, the takeoff request includes a drone identifier and an operator identification code, and determining the operator corresponding to the takeoff request includes:

[0012] Sending the drone identification to the pending operator according to the operator identification code, so that the pending operator can determine that the drone is a registered user and send a response message;

[0013] The undetermined operator is determined to be the operator corresponding to the drone based on the response information.

[0014] Optionally, the takeoff request includes a takeoff location and a destination, and the civil-military collaborative management platform determines a planned route based on the takeoff request, including:

[0015] determining at least one route based on the departure location and the destination;

[0016] Determine the types of military and civil areas included in each route;

[0017] A route corresponding to the takeoff request is planned based on the types of military and civil areas included in each route and preset route rules.

[0018] Optionally, the takeoff request includes a request sequence number, and determining whether the operator corresponding to the takeoff request supports cross-region flights includes:

[0019] Determining whether the request sequence number exists in a preset cross-region flight permission table, where the cross-region flight permission table is used to record all request sequence numbers for cross-region flight permission;

[0020] If so, determining whether the response information is received;

[0021] If so, it is determined that the operator corresponding to the takeoff request supports cross-regional flights.

[0022] Optionally, after determining whether the operator corresponding to the takeoff request supports cross-region flights, the method further includes:

[0023] If the response information is not received, and / or the request sequence number does not exist in the preset table of permitted cross-region flights, a first prompt information is sent.

[0024] Optionally, after determining whether the operator corresponding to the takeoff request supports cross-region flights, the method further includes:

[0025] If the operator corresponding to the takeoff request does not support cross-region flights, a second prompt message is sent.

[0026] A route planning device based on a military-civilian-ground collaborative management platform, comprising:

[0027] Request acquisition module, used to obtain the drone's takeoff request;

[0028] An operator determination module, configured to determine the operator corresponding to the takeoff request;

[0029] A request determination module, configured to determine whether the operator corresponding to the takeoff request supports cross-region flights;

[0030] The route planning module is used to send a takeoff request to the military-civilian-ground collaborative management platform if the operator corresponding to the takeoff request supports cross-regional flights, so that the military-civilian-ground collaborative management platform can determine the planned route according to the takeoff request.

[0031] Optionally, the takeoff request includes a drone identifier and an operator identification code, and the operator determination module includes:

[0032] a first operator determination submodule, configured to send the drone identification to a pending operator based on the operator identification code, so that the pending operator can determine that the drone is a registered user and send a response message;

[0033] The second operator determination submodule is configured to determine, based on the response information, that the undetermined operator is the operator corresponding to the drone.

[0034] Optionally, the takeoff request includes a takeoff location and a destination, and the route planning module includes:

[0035] A first route planning submodule is configured to determine at least one route according to the departure location and the destination;

[0036] The second route planning submodule is used to determine the types of military and civilian areas included in each route;

[0037] The third route planning submodule is used to plan a route corresponding to the take-off request according to the types of military and civil areas included in each route and preset route rules.

[0038] Optionally, the takeoff request includes a request sequence number, and the request determination module includes:

[0039] A first request determination submodule is configured to determine whether the request sequence number exists in a preset permitted cross-region flight table, wherein the permitted cross-region flight table is configured to record all request sequence numbers for permitted cross-region flights;

[0040] a second request determination submodule, configured to, after executing the first request determination submodule, determine whether the response information is received;

[0041] The third request judgment submodule is configured to, after executing the second request judgment submodule, determine if yes, that the operator corresponding to the takeoff request supports cross-regional flights.

[0042] As can be seen from the above technical solutions, the embodiments of the present application provide a route planning method and apparatus based on a military-civilian-ground collaborative management platform. This method obtains a drone takeoff request and identifies the corresponding operator. It then determines whether the operator supporting the takeoff request supports cross-regional flights. If approved, the takeoff request is sent to the military-civilian-ground collaborative management platform, which then determines the planned route based on the takeoff request. This application screens drone takeoff requests to ensure that all requests are from certified operators. This helps reduce collision risks during takeoff and improves drone flight safety. By determining whether the operator supporting cross-regional flights supports takeoff requests, takeoff requests can be effectively classified and processed, preventing collisions between drones and other aircraft during flight. This helps optimize route planning and improve air traffic management efficiency. Furthermore, the drone takeoff request is sent to the military-civilian-ground collaborative management platform, enabling military-civilian collaborative management. Through this platform, coordination between drones and other aircraft can be achieved, ensuring their safe operation in the air. This method can further standardize and streamline drone takeoff management, improving management efficiency. In this way, drone takeoff requests can be promptly reviewed and processed, reducing management costs and alleviating workload for managers. The route planning method based on the military-civilian-ground collaborative management platform will improve the safety and management efficiency of drone takeoffs, making the operation of drones more standardized and coordinated. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 A flow chart of a route planning method based on a military-civilian-ground collaborative management platform provided in an embodiment of the present application;

[0044] Figure 2 A flow chart of a route planning method provided in an embodiment of the present application;

[0045] Figure 3 Another route planning flow chart based on the military-civilian-ground collaborative management platform provided in an embodiment of the present application;

[0046] Figure 4 A schematic diagram of the structure of a route planning device based on a military-civilian-ground collaborative management platform provided in an embodiment of the present application;

[0047] Figure 5 This is a hardware structure block diagram of a route planning device based on a military-civilian-ground collaborative management platform disclosed in an embodiment of the present application. DETAILED DESCRIPTION

[0048] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0049] Figure 1 An embodiment of the present application provides a route planning method based on a military-civilian-ground collaborative management platform, which may include the following steps:

[0050] Step S100: Obtain a takeoff request from a UAV.

[0051] Specifically, the take-off request of the drone can be obtained through a server or a computer. The take-off request of the drone can be sent directly by the drone control platform or the control terminal, or forwarded by the drone.

[0052] Step S110: Determine the operator corresponding to the takeoff request.

[0053] Specifically, the operator may be an enterprise that has obtained national airspace operation qualifications. The corresponding operator can be determined based on the takeoff request. The operator corresponding to the takeoff request may be different, and the operator corresponding to the takeoff request can be determined.

[0054] Step S120: Determine whether the operator corresponding to the takeoff request supports cross-region flights.

[0055] Specifically, based on flight safety considerations, the entry permissions for different airspaces may be different, and the airspace flight permissions for different operators may be different. Examples of operators may be military operators, civilian operators, or local operators, etc. Support for cross-regional flights may be the relevant permissions between operators for allowing cross-airspace flights, which can be determined by determining whether the operator corresponding to the takeoff request supports cross-regional flights.

[0056] Step S130: If yes, a take-off request is sent to the military-civilian-ground collaborative management platform, so that the military-civilian-ground collaborative management platform can determine the planned route according to the take-off request.

[0057] Specifically, the planned route can be a route that is re-planned based on the current route and take-off request. When it is determined that the operator supports cross-regional flights, a take-off request can be sent to the military-civilian-ground collaborative management platform so that the military-civilian-ground collaborative management platform can determine the planned route based on the take-off request.

[0058] In the above-mentioned embodiment, this application screens drone takeoff requests to ensure that all takeoff requests are from certified operators. This helps reduce collision risks during takeoff and improves drone flight safety. By determining whether the operator corresponding to the takeoff request supports cross-regional flights, takeoff requests can be effectively classified and processed, preventing conflicts between drones and other aircraft during flight. This helps optimize route planning and improves air traffic management efficiency. Furthermore, drone takeoff requests are sent to a military-civilian-ground collaborative management platform, enabling military-civilian collaborative management. This platform enables coordination between drones and other aircraft, ensuring their safe operation in the air. This method can further standardize and streamline drone takeoff management, improving management efficiency. In this way, drone takeoff requests can be promptly reviewed and processed, reducing management costs and alleviating workload for management personnel. This route planning method based on the military-civilian-ground collaborative management platform will improve drone takeoff safety and management efficiency, making drone operations more standardized and coordinated.

[0059] In some embodiments of the present application, the takeoff request may include a drone identifier and an operator identification code. The following describes the process of determining the operator corresponding to the takeoff request in step S110. The process may include:

[0060] Step S111: Send the drone identification to the pending operator according to the operator identification code, so that the pending operator can determine that the drone is a registered user and send a response message.

[0061] Specifically, the operator identification code can be a combination of numbers with special meanings. Different operator identification codes correspond to different operators. The corresponding operator is determined according to the operator identification code. The pending operator can be the name of an uncertain operator. The drone identification can be unique, indicating the identity information or authority of the drone. The drone identification can be sent to the pending operator according to the operator identification code, so that the pending operator can determine that the drone is a registered user according to the drone identification, and can send corresponding response information to the drone terminal.

[0062] Step S112: Determine, based on the response information, that the undetermined operator is the operator corresponding to the drone.

[0063] Specifically, the response information may include information that the drone and the operator are correctly matched. Based on the response information, it can be determined that the undetermined operator is the operator corresponding to the drone.

[0064] In some embodiments of the present application, the take-off request may include information such as the take-off location and the destination. The following describes the process of step S130, if yes, sending the take-off request to the military-civilian-ground collaborative management platform so that the military-civilian-ground collaborative management platform can determine the planned route according to the take-off request. Figure 2 As shown, the process may include:

[0065] Step S131: Determine at least one route based on the departure location and destination;

[0066] Specifically, after determining that the operator corresponding to the takeoff request supports cross-regional flights, there may be multiple different routes through the departure point and destination, and it can be determined that at least one route is feasible and can normally reach the destination from the departure point, that is, at least one route is determined based on the departure point and destination.

[0067] Step S132: determining the types of military and civil areas included in each route;

[0068] Specifically, the military and civil land type can be any of the military type, civilian type and local type. The area passed by each route may be different, and the corresponding military and civil land types may be different. Each route contains at least one military and civil land type, and it is necessary to determine the military and civil land type contained in each route.

[0069] Step S133: planning a route corresponding to the takeoff request based on the types of military and civil areas included in each route and preset route rules.

[0070] Specifically, the preset route rules may include settings that allow crossing the area only at specific times. The preset route rules can be set according to needs. For example, military dependents are only allowed to cross the area at specific times. When the time of the take-off request conflicts with the specific time, the route corresponding to the take-off request can be re-planned, that is, the route corresponding to the take-off request is planned according to the military and civilian types contained in each route and the preset route rules.

[0071] Furthermore, in some embodiments of the present application, the takeoff request may include a request sequence number, which may be identity information indicating permission for cross-regional flight. The following describes the process of step S120, determining whether the operator corresponding to the takeoff request supports cross-regional flight. Figure 3 As shown, the process may include:

[0072] Step S121: Determine whether the request sequence number exists in a preset table of permitted cross-region flights.

[0073] Specifically, the permitted cross-region flight table may be used to record all request serial numbers for permitted cross-region flight, and the permitted cross-region flight table may be retrieved to determine whether the request serial number exists in the preset permitted cross-region flight table.

[0074] Step S122: If yes, determine whether the response information is received.

[0075] Specifically, if the request sequence number exists in the table of permitted cross-region flights, it can be further determined whether a response message is received.

[0076] Step S123: If yes, determine whether the operator corresponding to the takeoff request supports cross-region flights.

[0077] Specifically, if it is determined that the response information is received, it can be determined that the operator corresponding to the takeoff request supports cross-regional flights.

[0078] Furthermore, in some embodiments of the present application, step S120, the process of determining whether the operator corresponding to the takeoff request supports cross-region flights, may further include the following steps:

[0079] Step S123: If the response message is not received, or the request sequence number does not exist in the preset table of permitted cross-region flights, a first prompt message is sent.

[0080] Specifically, the first prompt message may be information indicating that the takeoff request is not approved. When no response message is received, the first prompt message may be sent; when no response message is received and the request sequence number does not exist in the preset table of permitted cross-regional flights, the first prompt message may be sent; when the request sequence number does not exist in the preset table of permitted cross-regional flights, the first prompt message may be sent. An example of the first prompt message may be that no response message is received.

[0081] In some embodiments of the present application, after step S120, determining whether the operator corresponding to the takeoff request supports cross-region flights, the following steps may also be included:

[0082] Step S140: If the operator corresponding to the takeoff request does not support cross-region flights, a second prompt message is sent.

[0083] Specifically, the second prompt information may be different from the first prompt information. The second prompt information may include the above-mentioned first prompt information. For example, the second prompt information may be that the operator does not support cross-regional flights. The specific reasons are as follows: receiving a response message.

[0084] The following describes the route planning device based on the military-civilian-land collaborative management platform provided in an embodiment of the present application. The route planning device based on the military-civilian-land collaborative management platform described below and the route planning method based on the military-civilian-land collaborative management platform described above can be referenced to each other.

[0085] like Figure 4 As shown, it discloses a structural schematic diagram of a route planning device based on a military-civilian-ground collaborative management platform. The route planning device based on the military-civilian-ground collaborative management platform may include:

[0086] The request acquisition module 11 is used to obtain the takeoff request of the UAV;

[0087] An operator determination module 12, configured to determine the operator corresponding to the takeoff request;

[0088] A request determination module 13 is configured to determine whether the operator corresponding to the takeoff request supports cross-region flights;

[0089] The route planning module 14 is configured to send a takeoff request to the civil-military-ground collaborative management platform if the operator corresponding to the takeoff request supports cross-regional flights, so that the civil-military-ground collaborative management platform can determine a planned route based on the takeoff request.

[0090] Optionally, the takeoff request includes a drone identifier and an operator identification code, and the operator determination module 12 may include:

[0091] a first operator determination submodule, configured to send the drone identification to a pending operator based on the operator identification code, so that the pending operator can determine that the drone is a registered user and send a response message;

[0092] The second operator determination submodule is configured to determine, based on the response information, that the undetermined operator is the operator corresponding to the drone.

[0093] Optionally, the takeoff request may include a takeoff location and a destination, and the route planning module 14 may include:

[0094] A first route planning submodule is configured to determine at least one route according to the departure location and the destination;

[0095] The second route planning submodule is used to determine the types of military and civilian areas included in each route;

[0096] The third route planning submodule is used to plan a route corresponding to the take-off request according to the types of military and civil areas included in each route and preset route rules.

[0097] Optionally, the takeoff request may include a request sequence number, and the request determination module 13 may include:

[0098] A first request determination submodule is configured to determine whether the request sequence number exists in a preset permitted cross-region flight table, wherein the permitted cross-region flight table is configured to record all request sequence numbers for permitted cross-region flights;

[0099] a second request determination submodule, configured to, after executing the first request determination submodule, determine whether the response information is received;

[0100] The third request judgment submodule is configured to, after executing the second request judgment submodule, determine if yes, that the operator corresponding to the takeoff request supports cross-regional flights.

[0101] Optionally, the device further includes:

[0102] The first prompt module is configured to send a first prompt message if the response message is not received and / or the request sequence number does not exist in the preset permitted cross-region flight table after the request judgment module 13 is executed.

[0103] The second prompting module is configured to send a second prompting message after executing the request judging module 13 if the operator corresponding to the takeoff request does not support cross-regional flight.

[0104] The route planning device based on the military-civilian-ground collaborative management platform provided in the embodiment of the present application can be applied to a route planning device based on the military-civilian-ground collaborative management platform. The route planning device based on the military-civilian-ground collaborative management platform can be a terminal. Figure 5 The hardware structure diagram of the route planning equipment based on the military-civilian-ground collaborative management platform is shown. Figure 5 ,The hardware structure of the route planning device based on the military-civilian-ground collaborative management platform may include: at least one processor 1, at least one communication interface 2, at least one memory 3 and at least one communication bus 4;

[0105] In the embodiment of the present application, the number of the processor 1, the communication interface 2, the memory 3, and the communication bus 4 is at least one, and the processor 1, the communication interface 2, and the memory 3 communicate with each other through the communication bus 4;

[0106] The processor 1 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention;

[0107] The memory 3 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory;

[0108] The memory stores a program, and the processor can call the program stored in the memory, wherein the program is used to:

[0109] Get the drone's takeoff request;

[0110] determining an operator corresponding to the takeoff request;

[0111] Determining whether the operator corresponding to the takeoff request supports cross-region flights;

[0112] If so, a takeoff request is sent to the military-civilian-ground collaborative management platform, so that the military-civilian-ground collaborative management platform can determine the planned route according to the takeoff request.

[0113] Optionally, the detailed functions and extended functions of the program may refer to the above description.

[0114] An embodiment of the present application further provides a storage medium, which may store a program suitable for execution by a processor, wherein the program is used to:

[0115] Get the drone's takeoff request;

[0116] determining an operator corresponding to the takeoff request;

[0117] Determining whether the operator corresponding to the takeoff request supports cross-region flights;

[0118] If so, a takeoff request is sent to the military-civilian-ground collaborative management platform, so that the military-civilian-ground collaborative management platform can determine the planned route according to the takeoff request.

[0119] Optionally, the detailed functions and extended functions of the program may refer to the above description.

[0120] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0121] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The various embodiments can be combined with each other, and the same or similar parts can be referenced to each other.

[0122] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present application. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application is not limited to the embodiments shown herein, but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A route planning method based on a military-civilian-ground collaborative management platform, characterized in that: include: Get the drone's takeoff request; determining an operator corresponding to the takeoff request; Determining whether the operator corresponding to the takeoff request supports cross-region flights; If yes, a takeoff request is sent to the military-civilian-ground collaborative management platform, so that the military-civilian-ground collaborative management platform determines a planned route according to the takeoff request; The takeoff request includes a drone identifier and an operator identification code, and determining the operator corresponding to the takeoff request includes: Sending the drone identification to the pending operator according to the operator identification code, so that the pending operator can determine that the drone is a registered user and send a response message; Determining, based on the response information, that the undetermined operator is the operator corresponding to the drone; The takeoff request includes a takeoff location and a destination, and the military-civilian-ground collaborative management platform determines a planned route based on the takeoff request, including: determining at least one route based on the departure location and the destination; Determine the types of military and civil areas included in each route; Planning a route corresponding to the takeoff request based on the types of military and civil areas included in each route and preset route rules; The takeoff request includes a request sequence number, and determining whether the operator corresponding to the takeoff request supports cross-region flights includes: Determining whether the request sequence number exists in a preset cross-region flight permission table, where the cross-region flight permission table is used to record all request sequence numbers for cross-region flight permission; If so, determining whether the response information is received; If so, it is determined that the operator corresponding to the takeoff request supports cross-regional flights.

2. The method according to claim 1, characterized in that After determining whether the operator corresponding to the takeoff request supports cross-region flights, the method further includes: If the response information is not received, and / or the request sequence number does not exist in the preset table of permitted cross-region flights, a first prompt information is sent.

3. The method according to claim 1, characterized in that After determining whether the operator corresponding to the takeoff request supports cross-region flights, the method further includes: If the operator corresponding to the takeoff request does not support cross-region flights, a second prompt message is sent.

4. A route planning device based on a military-civilian-ground collaborative management platform, characterized in that: include: Request acquisition module, used to obtain the drone's takeoff request; An operator determination module, configured to determine the operator corresponding to the takeoff request; A request determination module, configured to determine whether the operator corresponding to the takeoff request supports cross-region flights; A route planning module is configured to send a takeoff request to a civil-military-ground collaborative management platform if the operator corresponding to the takeoff request supports cross-regional flights, so that the civil-military-ground collaborative management platform can determine a planned route based on the takeoff request; The takeoff request includes a drone identifier and an operator identification code, and the operator determination module includes: a first operator determination submodule, configured to send the drone identification to a pending operator based on the operator identification code, so that the pending operator can determine that the drone is a registered user and send a response message; A second operator determination submodule, configured to determine, based on the response information, that the undetermined operator is the operator corresponding to the drone; The take-off request includes a take-off location and a destination, and the route planning module includes: A first route planning submodule is configured to determine at least one route according to the departure location and the destination; The second route planning submodule is used to determine the types of military and civilian areas included in each route; A third route planning submodule is configured to plan a route corresponding to the takeoff request based on the types of military and civil areas included in each route and preset route rules; The takeoff request includes a request sequence number, and the request determination module includes: A first request determination submodule is configured to determine whether the request sequence number exists in a preset permitted cross-region flight table, wherein the permitted cross-region flight table is configured to record all request sequence numbers for permitted cross-region flights; a second request determination submodule, configured to, after executing the first request determination submodule, determine whether the response information is received; The third request judgment submodule is configured to, after executing the second request judgment submodule, determine if yes, that the operator corresponding to the takeoff request supports cross-regional flights.

Images