Unmanned airfield operation control method and program product

Abstract

The present disclosure provides a kind of unmanned plane airport operation control method and program product, it is related to unmanned plane technical field.The method comprises the following steps: in response to connection trigger operation, communication connection is established with target unmanned plane, and jump to loading and unloading page;Obtain the cargo information reported through loading and unloading page, and jump to safety control page, safety control page includes safety protection control;In response to the closing operation of safety protection control, the state of safety protection control is switched from opening to closing, and jump to flight execution page;In flight execution page, control target unmanned plane take off.According to the embodiment of the present disclosure, the overall operation efficiency of unmanned plane distribution can be improved.

Description

Technical Field

[0001] This disclosure relates to the field of unmanned aerial vehicle (UAV) technology, and in particular to a UAV airport operation control method and program product. Background Technology

[0002] With the rapid development of the low-altitude economy and drone technology, drones are increasingly being used in logistics and delivery (such as food delivery, express delivery, and instant retail). To achieve automated drone operation, drone airports (or take-off and landing sites) have been built in various regions. Drones can automatically take off and land, swap batteries, and load and unload goods within these airports, thus completing logistics and delivery tasks. However, in the actual operation of existing drone airports, the overall operational efficiency of drone delivery remains low, making it difficult to meet the demands of high-frequency, large-scale commercial operations.

[0003] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0004] This disclosure provides a method and program for controlling unmanned aerial vehicle (UAV) airport operations, which can optimize ground operation processes to at least a certain extent, thereby improving the overall operational efficiency of UAV delivery.

[0005] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0006] According to one aspect of this disclosure, a method for controlling unmanned aerial vehicle (UAV) airport operations is provided, applied to a client. The method includes: on a device connection page, in response to a connection trigger operation, establishing a communication connection with a target UAV, and, if the connection is successful and the target UAV passes a self-test, redirecting to a loading / unloading page; acquiring cargo information reported through the loading / unloading page, the cargo information including cargo photos and / or cargo weight, and, if the cargo photos and / or cargo weight meet preset cargo verification conditions, redirecting to a safety control page, the safety control page including a safety protection control; in response to a closing operation of the safety protection control, switching the state of the safety protection control from on to off, and redirecting to a flight execution page, the safety protection control being used to enable or disable the safety protection mode; and on the flight execution page, controlling the target UAV to take off.

[0007] In one embodiment of this disclosure, prior to responding to the connection triggering operation, the method further includes: displaying a work order list page, the work order list page including multiple task cards, each task card including corresponding drone delivery task information; responding to a selection operation on a target task card, redirecting to a device connection page; correspondingly, controlling the target drone to take off, including: controlling the target drone to take off so that the target drone executes the drone delivery task corresponding to the target task card; wherein, the drone delivery task information includes at least one of timeliness information, destination airport, operating route, drone call sign, work order number, and waybill number, and the timeliness information includes at least one of allocated duration and task allocation time; wherein, the multiple task cards in the work order list page are displayed in sorted order based on the timeliness information.

[0008] In one embodiment of this disclosure, on the device connection page, in response to a connection trigger operation, establishing a communication connection with the target drone includes: in response to a scan trigger operation, invoking a scan interface, obtaining the serial number by recognizing the drone identification code, and establishing a communication connection with the target drone based on the serial number; or, in response to a manual connection trigger operation, displaying a list of nearby drones, wherein the list only displays drone identifiers within a preset connection distance range, and in response to a selection operation of the target drone identifier among the drone identifiers, establishing a communication connection with the target drone; or, in response to a one-click connection trigger operation, directly establishing a communication connection with the target drone.

[0009] In one embodiment of this disclosure, the method further includes: displaying a connection failure message on a QR code scanning interface or device connection page when a communication connection with the target drone fails to be established; wherein the connection failure message includes at least one of the following: the target drone is offline, the target drone is not in a connectable state, the target drone has been connected to another device, or the target drone has exceeded a preset connection distance.

[0010] In one embodiment of this disclosure, on the device connection page, in response to a connection trigger operation, a communication connection is established with the target drone, and if the connection is successful and the target drone passes its self-test, the user is redirected to the loading / unloading page. This includes: in response to a connection trigger operation, obtaining the task configuration information corresponding to the target task card; if the task configuration information indicates that a battery swap is required, the user is redirected to the battery swapping page and displays a battery replacement prompt on the battery swapping page; in response to a reconnection trigger operation detected on the battery swapping page, a communication connection is established with the target drone; and if the connection is successful and the target drone passes its self-test, the user is redirected to the loading / unloading page.

[0011] In one embodiment of this disclosure, if the connection is successful and the target drone passes its self-test, the user is redirected to the loading / unloading page. This includes: if the connection is successful, the target drone passes its self-test, and the target drone is in a safety protection mode, the user is redirected to the loading / unloading page; if the target drone is not in a safety protection mode, the user is redirected to the safety control page; in response to an activation trigger operation of the safety protection control on the safety control page, a sliding confirmation pop-up is displayed; in response to a sliding confirmation operation detected in the sliding confirmation pop-up, the state of the safety protection control is switched to "on," and a heartbeat verification timer is started; if the heartbeat verification timer reaches a preset heartbeat verification duration and a heartbeat verification pass signal is received from the target drone, the user determines that the target drone is in a safety protection mode and is redirected to the loading / unloading page.

[0012] In one embodiment of this disclosure, in response to a closing operation of the safety protection control, switching the state of the safety protection control from on to off includes: in response to a closing trigger operation of the safety protection control, displaying a sliding confirmation pop-up window, the sliding confirmation pop-up window displaying a first prompt message, the first prompt message being used to prompt the user to move away from the target drone at a preset safe distance before performing the closing operation; in response to a sliding confirmation operation detected in the sliding confirmation pop-up window, switching the state of the safety protection control to off, and controlling the target drone to output a safety prompt signal, the safety prompt signal including at least one of an acoustic prompt signal and an optical prompt signal.

[0013] In one embodiment of this disclosure, controlling the takeoff of a target drone on a flight execution page includes: displaying a takeoff confirmation pop-up in response to a triggering operation on the takeoff control in the flight execution page; and sending a takeoff control command to the target drone in response to a confirmation operation detected in the takeoff confirmation pop-up, so that the target drone takes off to perform a drone delivery task.

[0014] In one embodiment of this disclosure, obtaining cargo information reported through the loading and unloading page includes: displaying a photo prompt interface and / or a cargo weight input box on the loading and unloading page, wherein the photo prompt interface is used to prompt the user to take a photo of the target cargo with the cargo box door closed; obtaining the target cargo photo, and / or obtaining the cargo weight entered through the cargo weight input box; associating and storing the target cargo photo and / or cargo weight with the task identifier of the drone delivery task as an operation certificate for archiving; wherein the preset cargo verification conditions include: the cargo weight is less than or equal to the preset maximum load threshold of the target drone, and / or the cargo photo contains image features of the cargo box door being closed.

[0015] According to another aspect of this disclosure, an electronic device is provided, comprising: a memory for storing program instructions; and a processor for calling the program instructions stored in the memory to implement the above-described unmanned aerial vehicle (UAV) airport operation control method.

[0016] According to another aspect of this disclosure, a computer program product is provided, the computer program product including program instructions for implementing the above-described unmanned aerial vehicle (UAV) airport operation control method.

[0017] The technical solutions provided in this disclosure can include the following beneficial effects: This embodiment of the disclosure achieves full-process digital and standardized management and control of UAV ground operations by constructing a standardized page flow mechanism from task selection, equipment connection, cargo loading and unloading, safety confirmation to flight execution. The method sets strict precondition verification at each key page jump node, including equipment connection and self-inspection status verification, dual compliance verification of cargo photos and weight, and status switching confirmation of safety protection mode. This effectively avoids arbitrary operation and process omissions by ground personnel. While ensuring the compliance of cargo loading and the safety of personnel working near the UAV, it significantly reduces the cost of manual verification and communication, thereby significantly improving the ground turnover efficiency and overall delivery operation efficiency of UAV airports.

[0018] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0020] Obviously, the accompanying drawings described below are merely some embodiments of this disclosure. Those skilled in the art can obtain other drawings based on these drawings without any creative effort.

[0021] Figure 1 This diagram illustrates a drone delivery route scenario according to an embodiment of the present disclosure. Figure 2 This diagram illustrates a flowchart of an unmanned aerial vehicle (UAV) airport operation control method according to an embodiment of the present disclosure. Figure 3 This diagram illustrates a client interface according to an embodiment of the present disclosure. Figure 4 This diagram illustrates a work order list page in an embodiment of the present disclosure. Figure 5 This diagram illustrates the battery swapping process in an embodiment of the present disclosure. Figure 6This diagram illustrates the flowchart of the process of jumping to the loading and unloading page in an embodiment of this disclosure; Figure 7 This invention discloses a flowchart of another unmanned aerial vehicle (UAV) airport operation control method in an embodiment of the present invention. Figures 8 to 17 This diagram illustrates the client interaction interface in an embodiment of the present disclosure. Figure 18 This diagram illustrates an exception handling flowchart in an embodiment of the present disclosure. Figure 19 This diagram illustrates the client-side personal center interface in an embodiment of this disclosure. Figure 20 This diagram illustrates a flowchart of the visual inspection process in an embodiment of this disclosure. Figure 21 A schematic diagram of the blade management interface in an embodiment of this disclosure is shown; Figure 22 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0022] To facilitate understanding of the technical solutions of this disclosure, the disclosure will be further described below with reference to the accompanying drawings.

[0023] The terms "first" and "second," etc., used in this disclosure are only used to distinguish different objects and not to describe a specific order. The terms "comprising" and "having," and any variations thereof, in the embodiments of this disclosure are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may also include steps or units not listed.

[0024] Throughout this disclosure, the references to "embodiments" do not necessarily refer to the same embodiments, nor are they independent or alternative embodiments mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that the embodiments described in this disclosure can be combined with other embodiments.

[0025] In the embodiments of this disclosure, "at least one" refers to one or more, "more" refers to two or more, "at least two" refers to two or three or more, and "and / or" is used to describe the relationship between associated objects. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0026] In practical applications of drone delivery, there are two main control methods: one is independent operation of a single drone by a single person; the other is centralized control of multiple drones by a server, which typically has professional supervisors monitoring the drones' flight status in real time. In the server-centralized control mode, ground personnel are usually required to handle ground operations such as loading / unloading and battery swapping. Furthermore, drone delivery flight modes can be dynamically planned based on order requirements or can follow pre-set fixed routes for patrol flights. In the embodiments of this disclosure, the drones can be used for patrol missions.

[0027] To facilitate understanding, let's first combine... Figure 1 This disclosure describes the roving missions outlined in this publication. For example... Figure 1 As shown, the patrol mission in this disclosure refers to a closed-loop flight mission in which a UAV takes off from a designated starting point and landing point according to a pre-configured operating route, performs delivery operations at at least one target starting point and landing point, and finally returns and lands at the starting point and landing point.

[0028] Figure 1 The diagram shows multiple airports (e.g., airports 1 through 5). Airports 1, 2, and 3 have multiple take-off and landing points, while airports 4 and 5 have only one (such airports with only one take-off and landing point can also be called single-take-off and landing airports). Taking "Route 1" in the diagram as an example, the drone takes off from a specific take-off and landing point in airport 1, flies sequentially to the target take-off and landing points in airports 2 and 3 to perform delivery tasks, and finally returns and lands at the original take-off and landing point in airport 1. Taking "Route 2" as an example, the drone departs from another take-off and landing point in airport 1, passes sequentially through the target take-off and landing points in airports 4 and 5 (i.e., single-take-off and landing airports), and finally returns to the original take-off and landing point in airport 1.

[0029] It should be noted that the number of target take-off and landing points included in the operational route of the patrol mission can be flexibly configured according to actual business needs. For example, it can pass through only one target take-off and landing point, or it can pass through multiple target take-off and landing points sequentially. Furthermore, the target take-off and landing points along the route can be located at airports with multiple take-off and landing points, or at airports with only one take-off and landing point. In addition, when the drone performs delivery operations at the target take-off and landing points along the route, it can either land directly at the take-off and landing point for loading and unloading, or it can use a hovering descent method. Therefore, the drone may or may not land at the target take-off and landing points along the route. Through this patrol mission design, the drone can perform delivery flights cyclically on a fixed operational route, with the take-off and landing positions being the same take-off and landing point, thus facilitating centralized operation and maintenance management of the drones by the drone airport, including battery swapping, loading and unloading.

[0030] Figure 2This diagram illustrates a flowchart of a UAV airport operation control method according to an embodiment of the present disclosure. This UAV airport operation control method can be executed by a client (such as a ground control terminal, smartphone, etc.). Figure 2 As shown, the unmanned aerial vehicle (UAV) airport operation control method provided in this embodiment includes S201 to S204.

[0031] In S201, on the device connection page, in response to the connection trigger operation, a communication connection is established with the target drone, and if the connection is successful and the target drone passes the self-test, the user is redirected to the loading and unloading page.

[0032] On the device connection page, operators establish a communication connection with the target drone through connection triggering operations. These connection triggering operations can take several forms, such as: responding to a QR code triggering operation, invoking a QR code scanning interface, obtaining the serial number by recognizing the drone's identification code, and establishing a communication connection with the target drone based on the serial number; or responding to a manual connection triggering operation, displaying a list of nearby drones, showing only drones within a preset connection distance, and establishing a communication connection with the target drone by selecting its identifier; or responding to a one-click connection triggering operation, directly establishing a communication connection with the target drone.

[0033] In some embodiments, if a communication connection with the target drone fails to be established, a connection failure message is displayed on the QR code scanning interface or the device connection page; wherein the connection failure message includes at least one of the following: the target drone is offline, the target drone is not in a connectable state, the target drone has been connected to another device, or the target drone has exceeded the preset connection distance.

[0034] The client will only redirect to the loading / unloading page after a successful connection and the target drone's self-check. If the self-check fails, the user can be guided to handle the anomaly. By making device connection and self-check mandatory prerequisites for entering the loading / unloading process, the client ensures that the drone is in a healthy and controllable state before allowing subsequent ground operations, thus reducing safety risks.

[0035] In S202, the cargo information reported through the loading and unloading page is obtained. The cargo information includes cargo photos and / or cargo weight. If the cargo photos and / or cargo weight meet the preset cargo verification conditions, the user is redirected to the safety control page, which includes safety protection controls.

[0036] On the loading and unloading page, the client obtains cargo information reported by the operator. Regarding the acquisition of cargo weight, in some embodiments, it may include at least one of the following methods: one method is that the operator manually enters the cargo weight through the input box on the client; another method is that the client communicates with the intelligent weighing device and automatically obtains the cargo weight measured by the weighing device.

[0037] Regarding cargo photos, the client can prompt the user to take photos of the target cargo showing its cargo box door closed for digital documentation. The client verifies the cargo photos and weight, for example, checking if the weight is less than or equal to the target drone's preset maximum payload threshold, and whether the cargo photos contain image features indicating the cargo box door is closed. If the cargo photos and weight meet the preset cargo verification conditions, the user is redirected to the safety control page. These settings automate cargo status verification, ensuring compliant cargo loading and improving ground handling efficiency and flight safety.

[0038] It should be understood that in some feasible implementations, cargo information includes cargo photographs and cargo weight; in other feasible implementations, cargo information includes cargo photographs but not cargo weight; and in still other feasible implementations, cargo information includes cargo weight but not cargo photographs.

[0039] In S203, in response to the closing operation of the safety protection control, the state of the safety protection control is switched from on to off, and the user is redirected to the flight execution page. The safety protection control is used to turn the safety protection mode on or off.

[0040] On the safety control page, the operator can switch the status of the safety protection control from on to off by turning it off, thereby deactivating the drone's safety protection mode and redirecting the user to the flight execution page.

[0041] In some embodiments, to prevent accidental activation, in response to a closing trigger operation of the safety protection control, the client can display a sliding confirmation pop-up, prompting the user to move away from the drone at a preset safe distance before performing the closing operation; in response to a sliding confirmation operation detected in the sliding confirmation pop-up, the state of the safety protection control is switched to off, and the target drone can be controlled to output a safety warning signal (such as an acoustic warning signal and / or an optical warning signal) to alert surrounding personnel. Through the above settings, it is ensured that ground personnel only deactivate the safety protection after confirming that loading and unloading are complete and that personnel have evacuated the safe area, maximizing the personal safety of the operating personnel.

[0042] In S204, on the flight execution page, control the target drone to take off.

[0043] On the flight execution page, operators control the target drone to take off by triggering actions. For example, in response to a trigger action on the takeoff control on the flight execution page, the client can display a takeoff confirmation pop-up; in response to a confirmation action detected in the takeoff confirmation pop-up, a takeoff control command is sent to the target drone to enable it to take off and perform the drone delivery mission. Through this setup, a complete closed-loop control is achieved from task issuance, device connection, cargo verification, and security confirmation to final takeoff execution, realizing a high degree of standardization and automation of drone ground operation processes and significantly improving the overall operational efficiency of the drone airport.

[0044] In some embodiments, prior to S201 above, a work order list page may be displayed. The work order list page includes multiple task cards, each task card including corresponding drone delivery task information. In response to a selection of a target task card, the user is redirected to a device connection page.

[0045] The client displays a work order list page, visually showing the drone delivery tasks currently pending in the form of task cards. Each task card corresponds to a drone delivery task, and the task card contains the corresponding drone delivery task information.

[0046] In some embodiments, drone delivery task information includes at least one of timeliness information, destination airport, operating route, drone call sign, work order number, and waybill number, and timeliness information includes at least one of allocated duration and task allocation time; wherein, multiple task cards in the work order list page are displayed in sorted order based on timeliness information.

[0047] In some embodiments, multiple task cards in the work order list page can be sorted and displayed based on timeliness information (such as allocated duration and task allocation time). For example, new or urgent work orders can be automatically pinned to the top, making it easier for ground operators to quickly understand the task overview and make selections, thereby achieving centralized management and efficient scheduling of delivery tasks.

[0048] As an example, the interface after entering the client can be as follows: Figure 3 As shown, in Figure 3 In the middle, the user clicks on the work order and enters... Figure 4 The work order list page shown is as follows. Figure 4 The work order list page shown only includes one task card. In practice, the work order list page can include one or more task cards.

[0049] When an operator confirms that a specific task needs to be performed, the client responds by selecting the target task card (such as clicking or touching it), and jumps from the work order list page to the device connection page.

[0050] In some embodiments, on the device connection page, in response to a connection triggering operation, a communication connection is established with the target drone, and if the connection is successful and the target drone passes its self-test, the user is redirected to the loading / unloading page, which may include... Figure 5 S501 to S504 are shown.

[0051] In S501, in response to the connection trigger operation, the task configuration information corresponding to the target task card is obtained.

[0052] Upon responding to the connection trigger, the client first retrieves the task configuration information corresponding to the target task card. This task configuration information can be retrieved from the server in real time or pre-stored locally. The task configuration information includes all the prerequisites required to execute the current drone delivery task, including but not limited to the target drone's current battery status, estimated task power consumption, and whether battery replacement is needed. By retrieving the task configuration information, the client can assess in advance whether the target drone has the hardware and power requirements to directly execute the task.

[0053] In S502, if the task configuration information indicates that a battery swap is needed, the user will be redirected to the battery swap page, where a battery replacement prompt will be displayed.

[0054] The client parses the task configuration information. If the task configuration information indicates that a battery swap is needed (for example, the target drone's current remaining battery power is lower than a preset safe battery power threshold, or the task configuration information directly indicates that a full charge is required for takeoff), the client automatically redirects to the battery swap page. On the battery swap page, the client displays battery replacement prompts. For example, these prompts may include text prompts (such as "Current battery power is low, please replace the battery"), voice prompts, or animated guidance (such as displaying a dynamic diagram of the battery compartment opening and battery replacement) to intuitively guide ground operators to complete the battery replacement operation in a standardized and quick manner.

[0055] In S503, a communication connection is established with the target drone in response to a reconnection trigger detected on the battery swapping page.

[0056] After the operator completes the physical battery replacement, the existing communication connection will typically be lost because the battery swapping process may cause the target drone to power off and restart. Therefore, the client needs to detect the reconnection trigger on the battery swapping page. This reconnection trigger can be initiated manually by the operator clicking the "Reconnect" control on the page, or it can be automatically triggered by the client after detecting that the target drone has come back online. In response to this action, the client re-establishes a communication connection with the target drone to resume data interaction between the two parties.

[0057] In S504, if the connection is successful and the target drone passes the self-test, the user will be redirected to the loading and unloading page.

[0058] After re-establishing the communication connection, the client controls or waits for the target drone to perform a self-check. The self-check process may include checking the installation status of the new battery, whether battery communication is normal, and the health status of the drone's core components. Only if the connection is successful and the target drone passes the self-check will the client redirect to the loading / unloading page. If the self-check fails, a fault message (such as "Battery not installed correctly") will continue to be displayed on the battery swapping page or the troubleshooting page to guide the user in troubleshooting.

[0059] This embodiment intelligently identifies the drone's battery status during the device connection phase and automatically initiates a battery swapping process, ensuring that the target drone has sufficient power before performing delivery tasks. This not only avoids flight mission interruptions or safety risks due to insufficient power, but also ensures the rapid recovery of the drone's status after battery swapping through a standardized battery swapping guidance and reconnection mechanism, achieving seamless integration of ground operation processes and significantly improving the overall operational efficiency of drone airports.

[0060] In some embodiments, upon successful connection and passing the target drone's self-test, redirection to the loading / unloading page may include... Figure 6 S601 to S606 are shown.

[0061] In S601, it is determined whether the connection is successful, the target drone passes the self-test, and the target drone is in the security protection mode.

[0062] If the connection is successful, the target drone passes the self-test, and the target drone is in the security protection mode, then execute the jump to the loading and unloading page in S602.

[0063] After confirming a successful connection with the target drone and passing the self-test, the client will further obtain the target drone's current operating mode status. If the target drone is currently in a safety protection mode (for example, if the drone did not exit this mode after the previous task ended, or if this mode is enabled by default at system startup), it indicates that the drone has met the safety prerequisites for ground personnel to approach and perform loading and unloading operations. At this point, the client will directly jump to the loading and unloading page, reducing unnecessary interaction steps and improving the efficiency of ground operations.

[0064] If the target drone is not in security protection mode, execute S603 to jump to the security control page.

[0065] If the client detects that the target drone is not in safety protection mode (e.g., safety protection mode has been deactivated or has not yet been activated), it indicates that the drone has not yet entered a safety lock state and does not meet the safety conditions for direct loading and unloading. In this case, the client automatically redirects to the safety control page to guide the operator to manually activate the safety protection mode, thereby ensuring the safety of personnel in subsequent ground operations.

[0066] In S604, in response to the activation trigger operation of the security protection control in the security control page, a sliding confirmation pop-up is displayed.

[0067] On the safety control page, operators can trigger the activation operation by clicking or touching the safety protection control. To prevent accidental activation when people are lingering around the drone, the client displays a sliding confirmation pop-up in response to the activation trigger. For example, this sliding confirmation pop-up may contain prompt text (such as "Please confirm that all personnel have evacuated to a safe distance") and a slider, requiring the operator to complete the confirmation by sliding the slider. This physical interaction method increases the operational cost and effectively prevents the risk of accidental activation.

[0068] In S605, in response to a sliding confirmation operation detected in the sliding confirmation pop-up, the state of the security protection control is switched to enabled, and the heartbeat verification timer is started.

[0069] In response to the swipe confirmation action detected in the swipe confirmation pop-up, the client switches the security protection control from off to on. Simultaneously, the client starts a heartbeat verification timer. It's important to note that this state switch involves not only updating the client's UI, but also simultaneously sending a low-level control command to the target drone to activate the security protection mode. The purpose of starting the heartbeat verification timer is to allow the drone's underlying system sufficient response time to receive commands, execute security protection actions (such as locking motors or closing doors), and provide status feedback.

[0070] In S606, when the heartbeat verification timer reaches the preset heartbeat verification duration and a heartbeat verification pass signal is received from the target drone, the target drone is determined to be in safe protection mode, and the system redirects to the loading and unloading page.

[0071] During the heartbeat verification timeout period (e.g., 3 or 5 seconds), the client continuously monitors the target drone's feedback. If a heartbeat verification pass signal is received from the target drone within the preset heartbeat verification timeout period (this signal is generated and sent by the drone's underlying control system after successfully executing the safety protection action), the client determines that the target drone is truly and reliably in safety protection mode and then redirects to the loading / unloading page. If the signal is not received within the preset timeout period, or a verification failure signal is received, the client can display a timeout or failure message, guiding the user to retry or troubleshoot the issue.

[0072] In some embodiments, switching the state of the security protection control from on to off in response to a closing operation of the security protection control may include the following steps: In response to the closing trigger operation of the safety protection control, a sliding confirmation pop-up window is displayed. The sliding confirmation pop-up window displays the first prompt message, which is used to remind the user to move away from the target drone at a preset safe distance before performing the closing operation.

[0073] In practical applications, when a user prepares to deactivate the safety protection mode, the client displays a sliding confirmation pop-up. The first prompt in the pop-up (such as a warning text or voice message) serves to forcefully remind the user to confirm that surrounding personnel have been evacuated to a preset safe distance. This design adds an operation confirmation step from the human-computer interaction perspective, effectively preventing users from accidentally deactivating the safety protection in dangerous areas and ensuring personnel safety.

[0074] In response to a detected slide confirmation operation in the slide confirmation pop-up window, the state of the safety protection control is switched to off, and the target drone is controlled to output a safety warning signal, which includes at least one of an acoustic warning signal and an optical warning signal.

[0075] Specifically, after the user confirms via a swipe, the client switches the security protection control to off and sends a release command to the drone. Simultaneously, the target drone outputs a safety warning signal to alert nearby personnel that the drone is about to unlock and prepare for maneuver. The acoustic warning signal can be emitted via a buzzer or speaker on the drone, while the optical warning signal can be achieved through the flashing or color-changing of LED indicators on the drone's body, thus providing a clear safety alert at the physical environment level.

[0076] With the above settings, when the safety protection mode is deactivated, the combination of the front-end sliding confirmation anti-accidental touch mechanism and the back-end sound, light and physical warnings effectively avoids safety risks caused by personnel not evacuating or misoperation, thus improving the overall safety of drone ground operations.

[0077] In some embodiments, obtaining cargo information reported via the loading / unloading page may include the following steps: On the loading and unloading page, display a photo prompt interface and / or a cargo weight input box. The photo prompt interface is used to prompt you to take a photo of the target cargo with the cargo box door closed; obtain the photo of the target cargo, and / or obtain the cargo weight entered through the cargo weight input box.

[0078] In practical applications, the client guides users to take photos correctly through a photo-taking prompt interface (such as a viewfinder with auxiliary alignment lines), ensuring that the photo fully includes the cargo door and its closed state; it also provides a cargo weight input box to obtain accurate weight data. This standardizes the reporting process for ground personnel, ensuring the completeness and accuracy of the collected data.

[0079] The target cargo photo and / or cargo weight are associated with the mission identifier of the drone delivery mission and stored as an operational credential for archiving.

[0080] Specifically, the collected image and weight data can be bound to the current task identifier (such as order number or task batch number) and stored persistently. This not only enables the digital retention of cargo loading information, but also provides reliable operational credentials for subsequent logistics traceability, responsibility determination, and anomaly investigation.

[0081] The cargo information is verified based on preset cargo verification conditions, which include: the cargo weight is less than or equal to the preset maximum load threshold of the target drone, and / or the cargo photo contains an image feature that the cargo box door is in a closed state.

[0082] On the one hand, the weight of the cargo is checked to ensure it does not exceed the preset maximum load threshold, preventing overloading that could lead to flight accidents. On the other hand, image recognition algorithms are used to analyze photos of the target cargo to detect whether they contain image features indicating that the cargo container door is closed (such as identifying closed door edges and locked latches), ensuring the cargo container is properly sealed and preventing cargo from being lost during flight. Only when the above verification conditions are met can the subsequent takeoff or delivery process be allowed.

[0083] The above settings achieve standardized and automated verification of cargo information reporting. This ensures the traceability of logistics data through associated storage, and effectively eliminates flight safety hazards caused by overloading and loose cargo boxes through dual verification of weight and door closure status, thus improving the safety and reliability of drone delivery operations.

[0084] It should be understood that in some feasible implementations, cargo information includes cargo weight and cargo photos. Correspondingly, a photo-taking prompt interface and a cargo weight input box are displayed on the loading / unloading page. The photo-taking prompt interface prompts the user to take a photo of the target cargo with the cargo box door closed; the target cargo photo is obtained, and the cargo weight entered through the cargo weight input box is also obtained; the target cargo photo and cargo weight are associated with the task identifier of the drone delivery task and stored as an operational credential for archiving. In another feasible implementation, cargo information includes cargo weight. Correspondingly, a cargo weight input box is displayed on the loading / unloading page; the cargo weight entered through the cargo weight input box is obtained; the cargo weight is associated with the task identifier of the drone delivery task and stored as an operational credential for archiving. In yet another feasible implementation, cargo information includes cargo photos. Correspondingly, a photo-taking prompt interface is displayed on the loading / unloading page. The photo-taking prompt interface prompts the user to take a photo of the target cargo with the cargo box door closed; the target cargo photo is obtained; the target cargo photo is associated with the task identifier of the drone delivery task and stored as an operational credential for archiving.

[0085] Figure 7 This diagram illustrates a flowchart of a UAV airport operation control method according to an embodiment of the present disclosure. The following is a summary of the process. Figure 7 and Figures 8 to 17 This disclosure provides a detailed description of the unmanned aerial vehicle (UAV) airport operation control method in the embodiments of this disclosure.

[0086] Figure 4 This page displays a work order list. Work orders are the core carrier of delivery execution, covering the entire process from connecting the drone to completing its launch, including loading and unloading information entry, battery swapping, and launch execution. Figure 4 The work order list page shown has a first-level tab that includes "In Progress" and "Completed". In some embodiments, new work orders are automatically pinned to the top of the work order list.

[0087] In some embodiments, the information displayed on the task card (also known as the work order card) may include timeliness information (such as allocated 1 minute or 14:25), destination airport, operating route, drone call sign, work order number, waybill number, etc.

[0088] In some embodiments, the task card may also include navigation buttons (such as...). Figure 4 Click the button after the location XXX to view a map and route guide to the destination airport.

[0089] In some embodiments, the task card may also include an issue control, which serves as a general entry point for encountering issues.

[0090] In some embodiments, the task card includes a start execution control, which can be a slider to reduce the probability of accidental touches. After the task is first entered and started, then exited and re-entered, the control can be changed to execute immediately.

[0091] exist Figure 4 Clicking the "Start Execution" control on the target task card in the interface will navigate to... Figure 8 Interface. Upon first entering... Figure 8 When the interface is accessed, it may display a message indicating that the drone is not connected. Figure 8 The interface includes three ways to connect to a drone: scanning the drone's QR code, manually entering the call sign, and one-click connection. Selecting to scan the drone's QR code will bring up the scanning interface, which will obtain the serial number by recognizing the drone's identification code and establish a communication connection with the target drone based on the serial number. Selecting to manually enter the call sign will take you to the call sign input interface, or you can view a floating window displaying a list of nearby drones. This list only shows drones within a preset connection distance, allowing the user to select a target drone and establish a communication connection. One-click connection will directly connect to the target drone corresponding to the current task.

[0092] You can enter after a successful connection. Figure 9 Interface, in Figure 9 The interface prompts the user to load or unload goods. After clicking "Report Goods Information," the user is redirected to... Figure 10 Interface, in Figure 10 The interface allows you to use the camera to take photos of the goods, or select photos from your album. You also need to enter the weight of the goods, and then click "Complete Loading and Unloading".

[0093] In some embodiments, Figure 10 The interface can also display the maximum payload of this model, and loading and unloading operations should not exceed this payload. If the entered cargo weight exceeds the maximum payload, it will indicate that the drone's payload range has been exceeded.

[0094] It should be noted that this embodiment of the disclosure also checks whether the drone is in a safety protection mode; the above-mentioned steps will only be performed if the drone is in a safety protection mode. Figure 9 and Figure 10 During the loading and unloading process, once the safety protection mode is successfully activated, the drone can issue an audible and visual alert to inform the user that the drone is currently in safety protection mode and can be approached for operation.

[0095] In some embodiments, a detection can be performed before the loading and unloading process described above to determine if a battery swap is required. If a battery swap is required, the process can proceed before entering the loading / unloading area. Figure 9 You can enter the interface first. Figure 11The battery swapping interface. It's understandable that battery swapping is an optional step, and conditions that may trigger it include the requirement for a battery swapping in the patrol mission configuration. Figure 11 The system prompts you to replace the drone battery first. After replacing the battery, click "Reconnect Drone." Once connected successfully, you will see the connected drone card, which displays the drone's self-test results. If the security protection is off, you can turn it on. If there are any outstanding historical tasks, you can click "Clear Historical Tasks."

[0096] After loading and unloading are completed, proceed to Figure 12 The interface displays a "Disable Security Protection" message. Clicking "Disable Security Protection" will bring up a pop-up window. Figure 13 The prompt indicates that the protection will be turned off after moving 3 meters away from the drone. After sliding to confirm the shutdown, you will hear an audio-visual prompt from the drone (such as three beeping sounds).

[0097] After the security protection is turned off, enter. Figure 14 The interface, titled "Launch Drones," leads to the following: Click "Initiate Drone Delivery." Figure 15 In the pop-up window shown, view the launch confirmation information, click "Initiate Drone Delivery," slide to initiate flight, and then proceed to... Figure 16 interface.

[0098] After successful launch, enter Figure 17 The interface displays successful work order information, including destination and estimated arrival time. Clicking "back" will take you back to the work order list and allow you to continue with the next task.

[0099] The following is combined with Figure 18 introduce Figure 3 Drone ground management within the interface. (Through...) Figure 3 The ground management of drones can enter the drone anomaly handling process.

[0100] The drone anomaly handling module is used to connect to the drone and execute remote commands, including activating safety protections and canceling flight missions. It is suitable for situations where the drone malfunctions, allowing the operator to connect to the drone and issue commands for handling.

[0101] The anomaly handling process includes connecting to the drone and executing commands. It is important to note that safety protection must be activated before approaching the drone. Ground delivery personnel must activate safety protection before operating the drone and must maintain a safe distance before takeoff. In case of an anomaly, the mission can be canceled and safety protection activated. Approaching the drone is only permitted after hearing the drone's audible and visual cues and activating safety protection.

[0102] The first step is to connect the drone. For details on how to connect, please refer to the previous text.

[0103] After successfully connecting to the drone, the following information will be displayed: drone call sign, such as WSK0001; drone model; safety protection status; drone battery level (integrated battery value).

[0104] After successfully connecting to the drone, you can enable security protection, cancel the flight mission and enable protection, or disconnect and return to the homepage. Enabling security protection requires a double swipe confirmation: first click, then a confirmation pop-up appears, then swipe to confirm, and finally wait 5 seconds for heartbeat verification. Canceling the flight mission and enabling protection also requires a double swipe confirmation: first click, then a confirmation pop-up appears, then swipe to confirm, and finally wait for the result. Disconnecting and returning to the homepage also requires a double swipe confirmation.

[0105] In some embodiments, if a barcode scanning drone cannot connect, the error message may include the following four types: the drone is offline and cannot connect; the drone is not in a connectable state; the drone has been connected to another device; or it must be within a preset distance.

[0106] In some embodiments, if the drone connection fails, a pop-up window will indicate the reason for the failure, and the user can adjust the settings and try again.

[0107] In some embodiments, if the drone fails the self-test (without needing to replace the drone), the abnormality can be handled according to the client instructions. After handling, the connection is disconnected and reconnected until the self-test passes.

[0108] In some embodiments, if takeoff fails (without needing to switch aircraft), the flight mission can be canceled and safety protection enabled. Follow the client's error message to resolve the issue, then disable safety protection and retry takeoff.

[0109] In some embodiments, if multiple retries to launch still fail (without needing to change aircraft), you can click to report the exception and close the work order. The work order will disappear from the client list, and the management side will see the exception prompt and alarm and then handle the exception.

[0110] In some embodiments, if a self-check or launch fails and a replacement drone is required, the current drone's patrol mission can be canceled on the mobile device, and a new patrol mission can be created for the new drone. The mission can then continue after a new work order is issued at the current airport.

[0111] In some embodiments, if a user needs to terminate or reassign a work order for personal reasons, they can click [here]. Figure 4 If a problem is encountered and an exception is reported, the server can reassign loading / unloading and release work orders as needed.

[0112] In some embodiments, if you need to exit the work order details page during the execution of a work order, the behavior upon re-entering depends on the current stage: Before launch: A pop-up window prompts you to confirm and exit the work order process. After confirming, you exit; upon re-entering, you return to the previous screen. Figure 8 Connecting the drone requires going through the entire process again; Once the launch begins: You cannot exit manually; there is no exit button in the upper left corner. You must wait for the launch process to finish. If you close the client background: the work order will still be there after you exit and re-enter. If the aircraft has successfully taken off, you need to contact the management to end the work order; if the aircraft has not taken off, you can re-release it.

[0113] It should be noted that if a launch action has been initiated and the drone is in the process of being launched, the work order cannot be cancelled.

[0114] In some embodiments, Figure 3 The page also displays key information about the current delivery person's project, including project status, online / offline status, current task overview, and quick access points.

[0115] Project Selection: A project selection button can be displayed at the top of the homepage. Clicking it will bring up a floating panel (the title can be "Please select a project"). A scrolling selector will be used to display the project list. The project name can only show the projects that the current user has deployed. There are confirmation and close buttons at the bottom.

[0116] Cached historical projects: If there are cached historical projects to select, the project name will be displayed; if there are no cached projects but projects have been deployed, please select a project; if there are no projects to deploy, there are no projects to select, please complete the employee deployment first.

[0117] Online / Offline Operation: Click the online / offline button in the top bar, select online or offline, and trigger a toast notification.

[0118] Function entry points: Work orders, patrol tasks, drone appearance inspection, drone ground management, and creating round-trip delivery.

[0119] Red dot notification for work order messages: When a new work order is received, a red dot notification will be displayed at the top right corner of the function module entry.

[0120] In some embodiments, by Figure 3 The interface can also be accessed Figure 19 The personal center interface, as shown, displays the delivery driver's personal information, work order statistics, and system settings, allowing drivers to easily view work results and manage personal preferences. Clicking to enter the completed work order list displays the work orders for the day, arranged in ascending order of completion time. Information includes the route, waybill number, completion time, and work order type tag. Clicking to enter the cancelled work order list displays the work orders for the day, arranged in ascending order of cancellation time. Information includes the route, waybill number, completion time, and work order type tag. Work order statistics cover all items, and data is updated daily (T+1).

[0121] In some embodiments, by Figure 3The interface also allows access to a settings page, which may include the following functional controls: upload logs, check for updates, application settings, clear data, notification management, system time, etc.

[0122] In some embodiments, by Figure 3 The drone appearance inspection option in the interface leads to the appearance inspection process, as shown below. Figure 20 A detailed explanation of the appearance inspection process.

[0123] like Figure 20 As shown, when conducting an external inspection, you can first scan the drone's QR code (or manually enter the call sign), then check the fuselage structure, sensors, battery, and waterproof performance separately, and finally summarize and submit the inspection results.

[0124] It's understandable that the drone scanning during visual inspection involves scanning for the drone's call sign, not actually connecting to the drone. The drone scanning during visual inspection allows for the registration of drone information.

[0125] The drone identification feature in the visual inspection section supports both scanning the call sign and allowing users to input the call sign. If a drone is identified, the user will proceed to the visual inspection completion stage. Error messages will be displayed if the call sign is incorrect or the drone is not the user's own; these messages will be consistent across all scenarios.

[0126] In some embodiments, during a drone appearance inspection, the terminal device acquires drone identification information, which is obtained by scanning the drone's QR code or by manually entering the drone's call sign. Upon successful identification, the terminal device displays an inspection overview page to show aircraft information and the total number of inspection items.

[0127] The terminal device then guides the user through a module-by-module inspection, which includes four modules: structure, sensing, power supply, and waterproofing. For each module inspection, the terminal device supports multiple interaction methods. In response to triggering the illustrated control, a reference diagram for that module's inspection is displayed; in response to confirming that all inspection items for that module are problem-free, a quick option to mark all items as error-free is provided; in response to expanding a single inspection item, inspection instructions are displayed, and error-free or error-marked items are received.

[0128] When an anomaly flag is received, the terminal device displays an anomaly reporting pop-up to obtain anomaly information. This anomaly information includes an anomaly type label, the cause of the fault, and attachment information. The anomaly type label is a required multiple-choice field, the cause of the fault is optional, and the attachment information can include up to five photos or a video clip of up to fifteen seconds. In response to the confirmation submission, the terminal device submits the anomaly information and guides the user to the next inspection module.

[0129] Once all the aforementioned modules have completed their checks, the terminal device displays an inspection overview page. The top of this page shows a global status indicating either all items passed or the number of items with anomalies, and displays aircraft information including call sign, model, inspector, completion time, and total number of items checked. For modules with anomalies, users can expand to view the anomaly tags, notes, and attachments. In response to the submission of inspection results, the terminal device completes the report and automatically returns to the QR code scanning page to prepare for the next inspection.

[0130] In addition, if the drone's appearance inspection results are abnormal, the use of the drone for flight missions will be restricted, and the user will be prompted to handle the matter according to the operation and maintenance and after-sales procedures.

[0131] In some embodiments, the drone ground management interface can also be used to access the propeller management process, which is mainly used for binding and verifying propellers for specific drones.

[0132] Specifically, the propeller binding process first includes obtaining the drone's identification information. In practical applications, this can be achieved through two methods: scanning a QR code or manual input. In the QR code scanning method, in response to triggering the QR code scanning control, the terminal device activates its camera to scan the code and automatically obtain the drone's serial number. In the manual input method, in response to triggering the manual call sign input control, the terminal device displays the call sign input interface, obtains the drone's call sign entered by the user, and proceeds to the next step control in response to triggering the next step control. Figure 21 interface.

[0133] After obtaining the drone identification information, in Figure 21 The interface performs the propeller binding operation. Since the propeller code is typically located at the base of the back of the propeller, in response to the scan button, the terminal device activates its camera to scan the propeller code to automatically obtain the propeller's serial number. In response to the submit control, the terminal device performs the propeller binding. If binding is successful, a success message is output; if binding fails, the specific reason for the failure is displayed.

[0134] It should be noted that the drone's propeller configuration requires four positive and four negative blades to be bound together; incorrect binding poses a safety risk. In this embodiment, the system does not forcibly verify whether the propeller binding has been completed before takeoff. Instead, it guides the user through the aforementioned binding process and relies on manual verification to ensure that the binding operation has been completed. This ensures operational flexibility while reminding the user to pay attention to the correctness of the propeller configuration.

[0135] Based on the same inventive concept, this disclosure also provides an electronic device. For example... Figure 22As shown, the electronic device provided in this embodiment includes a processor 2201 and a memory 2202; the memory 2202 is used to store program instructions; the processor 2201 is used to call the program instructions stored in the memory 2202 to implement the UAV airport operation control method described in the above method embodiment.

[0136] In some embodiments, the processor 2201 is a device with data processing capabilities, including but not limited to a central processing unit (CPU), a field-programmable gate array (FPGA), and other programmable logic devices. The processor 2201 may include one or more processing cores.

[0137] In some embodiments, the memory 2202 is a device with data storage capability, including but not limited to random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory.

[0138] In some embodiments, the processor 2201 and memory 2202 can be configured separately or integrated together. As an example, the processor 2201 and memory 2202 can be integrated on a single board or a system on a chip (SOC).

[0139] like Figure 22 As shown, the electronic device provided in this embodiment may further include an interface 2203. The interface 2203 is connected between the processor 2201 and the memory 2202, enabling information exchange between the processor 2201 and the memory 2202. In some embodiments, the processor 2201, the memory 2202, and the interface 2203 are interconnected via a bus 2204.

[0140] In some embodiments, there may be one or more processors 2201.

[0141] In some embodiments, there may be one or more memories 2202.

[0142] In some embodiments, there may be one or more interfaces 2203.

[0143] In some embodiments, the memory 2202 stores one or more program instructions. When the one or more program instructions are executed by the one or more processors 2201, the one or more processors 2201 implement the UAV airport operation control method described in the above method embodiments and achieve the corresponding technical effects.

[0144] In some embodiments, the electronic device may also communicate with one or more external devices, such as a keyboard, pointing device, Bluetooth device, etc. In some embodiments, the electronic device may also communicate with one or more devices that enable a user to interact with the electronic device. In some embodiments, the electronic device may also communicate with devices that enable the electronic device to communicate with one or more other computing devices. In some embodiments, the above communication may be performed through interface 2203.

[0145] Understandable, Figure 22 The illustrated structure does not constitute a specific limitation on the electronic device. In some embodiments, the electronic device may include... Figure 22 The number of components shown may be more or fewer. In some embodiments, the electronic device has... Figure 22 Based on the diagram, some components can be combined, some components can be separated, or different component arrangements can be made.

[0146] In some embodiments, Figure 22 The components shown can be implemented in hardware, software, or a combination of both.

[0147] Based on the same inventive concept, this disclosure also provides a computer-readable storage medium storing program instructions. When the program instructions are executed by a computer, they implement the UAV airport operation control method described in the above method embodiments, achieving the corresponding technical effects.

[0148] In some embodiments, the computer-readable storage medium can be any available medium capable of storing program instructions or a data storage device such as a data center containing one or more available media. In some embodiments, the available medium can be a magnetic medium, an optical medium, or a semiconductor medium, etc. As an example, a magnetic medium can be a floppy disk, a hard disk, a magnetic tape, etc. As an example, an optical medium can be a high-density digital video optical disc. As an example, a semiconductor medium can be a solid-state drive.

[0149] Based on the same inventive concept, this disclosure also provides a computer program product, which includes program instructions for implementing the UAV airport operation control method described in the above method embodiments. When executed by a computer, the program instructions cause the computer to implement the UAV airport operation control method described in the above method embodiments, achieving the corresponding technical effects. In specific implementations, the program instructions can be written using any combination of one or more programming languages. The program instructions can be executed entirely on the user device, partially on the user device, as a standalone software package, partially on the user device and partially on a remote device, or entirely on a remote device or server.

[0150] Those skilled in the art will understand that all or part of the steps of the above embodiments can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation, or an implementation combining hardware and software aspects.

[0151] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A method for controlling unmanned aerial vehicle (UAV) airport operations, characterized in that, include: On the device connection page, in response to the connection trigger operation, a communication connection is established with the target drone, and if the connection is successful and the target drone passes the self-test, the user is redirected to the loading and unloading page. The system retrieves cargo information reported through the loading and unloading page, including cargo photos and / or cargo weight. If the cargo photos and / or cargo weight meet preset cargo verification conditions, the system redirects to a safety control page, which includes safety protection controls. In response to the closing operation of the safety protection control, the state of the safety protection control is switched from on to off, and the user is redirected to the flight execution page. The safety protection control is used to turn the safety protection mode on or off. On the flight execution page, control the target drone to take off.

2. The method according to claim 1, characterized in that, Prior to the connection trigger operation, the method further includes: The work order list page is displayed, which includes multiple task cards, and each task card includes corresponding drone delivery task information. In response to the selection of a target task card, the user is redirected to the device connection page. Correspondingly, controlling the takeoff of the target drone includes: Control the target drone to take off, so that the target drone can perform the drone delivery task corresponding to the target task card; The drone delivery task information includes at least one of the following: timeliness information, destination airport, operating route, drone call sign, work order number, and waybill number; the timeliness information includes at least one of the following: allocated duration and task allocation time. In the work order list page, multiple task cards are displayed in sorted order based on the timeliness information.

3. The method according to claim 1, characterized in that, On the device connection page, in response to a connection trigger operation, establishing a communication connection with the target drone includes: In response to the scanning trigger operation, the scanning interface is invoked, the serial number is obtained by recognizing the drone identification code, and a communication connection is established with the target drone based on the serial number; Alternatively, in response to a manual connection trigger operation, a list of nearby drones is displayed, which only shows drones within a preset connection distance range. In response to a selection operation of a target drone from the drones, a communication connection is established with the target drone. Alternatively, in response to a one-click connection trigger operation, a communication connection can be directly established with the target drone.

4. The method according to claim 3, characterized in that, The method further includes: If a communication connection with the target drone fails to be established, a connection failure message will be displayed on the QR code scanning interface or the device connection page. The connection failure message includes at least one of the following: the target drone is offline, the target drone is not connectable, the target drone has been connected to another device, or the target drone has exceeded the preset connection distance.

5. The method according to claim 2, characterized in that, On the device connection page, in response to a connection trigger operation, a communication connection is established with the target drone, and if the connection is successful and the target drone passes its self-test, the user is redirected to the loading / unloading page, including: In response to the connection triggering operation, obtain the task configuration information corresponding to the target task card; If the task configuration information indicates that a battery swap is required, the user will be redirected to the battery swap page, where a battery replacement prompt will be displayed. In response to a reconnection trigger operation detected on the battery swapping page, a communication connection is established with the target drone; Once the connection is successful and the target drone passes its self-test, the user will be redirected to the loading / unloading page.

6. The method according to claim 1, characterized in that, Upon successful connection and successful self-test of the target drone, the user is redirected to the loading / unloading page, which includes: If the connection is successful, the target drone passes the self-test, and the target drone is in the security protection mode, the user will be redirected to the loading and unloading page. If the target drone is not in security protection mode, then redirect to the security control page; In response to the activation trigger operation of the security protection control in the security control page, a sliding confirmation pop-up window is displayed; In response to the sliding confirmation operation detected in the sliding confirmation pop-up, the state of the security protection control is switched to "on", and the heartbeat verification timer is started; When the heartbeat verification timer reaches the preset heartbeat verification duration and a heartbeat verification pass signal is received from the target drone, the target drone is determined to be in a safety protection mode, and the user is redirected to the loading and unloading page.

7. The method according to claim 1, characterized in that, The step of switching the state of the security protection control from on to off in response to the closing operation of the security protection control includes: In response to the closing trigger operation of the security protection control, a sliding confirmation pop-up window is displayed. The sliding confirmation pop-up window displays a first prompt message, which is used to prompt the user to move away from the target drone at a preset safe distance before performing the closing operation. In response to a sliding confirmation operation detected in the sliding confirmation pop-up, the state of the security protection control is switched to off, and the target drone is controlled to output a security warning signal, which includes at least one of an acoustic warning signal and an optical warning signal.

8. The method according to claim 1, characterized in that, The step of controlling the takeoff of the target drone on the flight execution page includes: In response to a triggering operation on the takeoff control in the flight execution page, a takeoff confirmation pop-up window is displayed; In response to a confirmation action detected in the takeoff confirmation pop-up window, a takeoff control command is sent to the target drone to cause the target drone to take off and perform the drone delivery mission.

9. The method according to claim 1, characterized in that, The process of obtaining cargo information reported through the loading and unloading page includes: The loading and unloading page displays a photo prompt interface and / or a cargo weight input box. The photo prompt interface is used to prompt the user to take a photo of the target cargo with the cargo box door closed. Obtain a photo of the target cargo, and / or obtain the cargo weight entered through the cargo weight input box; The target cargo photo and / or cargo weight are associated with the task identifier of the drone delivery mission and stored as an operational credential for archiving. The preset cargo verification conditions include: the weight of the cargo is less than or equal to the preset maximum load threshold of the target drone, and / or the cargo photo contains an image feature that the cargo box door is closed.

10. A computer program product, characterized in that, The computer program product includes program instructions for implementing the unmanned aerial vehicle airport operation control method as described in any one of claims 1 to 9.

Images