Message sending method and device based on flight takeoff and landing, medium and product
By using radar to obtain the track and conducting condition checks, the problem of flights being unable to timely send messages in complex flight situations is solved, and the accuracy of flight status judgment and the stability and safety of aviation management are improved.
Patent Information
- Application Number
- CN202411968495.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-30
- Publication Date
- 2025-02-25
Smart Images

Figure CN119516843A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology. Specifically, the present application relates to a method, device, medium and product for sending messages based on flight takeoffs and landings. Background Art
[0002] During flight operation, it is usually necessary to monitor the flight operation status in real time to obtain flight operation information in real time. Flight operation information is a set of dynamically changing data. In order to facilitate flight-related managers to quickly obtain flight operation information, the airport needs to send Aeronautical Fixed Telecommunication Network (AFTN) messages based on the acquired flight operation information so that other managers can continuously update the flight operation information based on the received messages. AFTN message data is an important data source for real-time processing and updating of flight operation information on the day. It is also the basis for further analysis and processing of flight operation information data on the day, which plays a significant role in flight management and safety.
[0003] ANT messages include Departure Message (DEP) and Arrival Message (ARR). These two messages need to be sent only when a flight takes off or lands. However, in complex flight scenarios, due to weather or flight volume, a small number of flights cannot correctly judge the flight status, resulting in some flights being unable to send the corresponding takeoff or landing messages in time, affecting aviation control operations and affecting flight management and safety. Summary of the invention
[0004] The embodiments of the present application provide a method, device, medium and product for sending messages based on flight take-off and landing, which can solve the problem that the corresponding take-off message or landing message cannot be sent in time in the existing complex flight situation, affecting the operation of aviation control and affecting the management and safety of flights. In order to achieve this purpose, the embodiments of the present application provide the following solutions.
[0005] According to one aspect of an embodiment of the present application, a method for sending a message based on flight take-off and landing is provided, the method comprising:
[0006] Use radar to obtain flight tracks within the airspace;
[0007] If a preset event is determined to be triggered according to the flight track or surface status information, a condition check is performed, wherein the preset event includes any one of a flight take-off status and a flight landing status, and the condition check includes at least one of a data source check, a timeliness check, a relevance check, and a surface status verification, and the surface status information is obtained through an electronic progress sheet of the tower;
[0008] Execute the message sending operation based on the condition check result.
[0009] In a possible implementation, the obtaining of the track of the aircraft in the airspace by using radar includes:
[0010] Acquire the track data of the aircraft, and acquire the target track corresponding to the flight plan of the flight according to the track data, wherein the track data at least includes the flight number, transponder, and take-off point.
[0011] In a possible implementation, acquiring a target track corresponding to a flight plan according to the track data includes:
[0012] The matching information between each track in the track data and the flight plan of the flight is obtained, and the target track is determined according to the matching information, wherein the target track includes any one of a related track and an unrelated track.
[0013] In a possible implementation, determining the triggering preset event includes:
[0014] Acquire motion data of the target track within a predetermined range, where the predetermined range is determined based on the airport center point and the control altitude;
[0015] Determine the movement trend of the target track relative to the airport center point and the control altitude according to the movement data;
[0016] If the movement trend meets the preset trend, determining a preset event corresponding to the preset trend that is triggered;
[0017] Or, the scene status information is obtained through the tower electronic process sheet system, and whether a preset event is triggered is detected according to the scene status change information in the scene status information.
[0018] In a possible implementation, the condition check includes a data source check, and the data source check includes:
[0019] Determine a data source corresponding to the preset event that is triggered, wherein the data source includes at least one of a track and a scene status information;
[0020] If it is determined that the current sending mode is consistent with the data source, it is determined that the check is passed.
[0021] In a possible implementation, the condition check includes a relevance check, and the relevance check includes:
[0022] Acquire the associated information corresponding to the triggered preset event, and determine the inspection result according to the associated information, wherein the associated information includes at least one of task information, take-off and landing information, and whether the telegram address exists.
[0023] In a possible implementation, the condition check includes scene status verification, and the scene status verification includes:
[0024] Obtain the flight number corresponding to the preset event that is triggered;
[0025] Utilize the flight number to query the status information and the time when the track event occurs in the surface status information;
[0026] The inspection result is determined based on the query result.
[0027] According to one aspect of an embodiment of the present application, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the method described above.
[0028] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method described above are implemented.
[0029] According to one aspect of an embodiment of the present application, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps of the method described above are implemented.
[0030] The beneficial effects of the technical solution provided by the embodiment of the present application are:
[0031] The message sending method based on flight takeoff and landing provided in the present application utilizes radar to obtain the track in the airspace; if a preset event is determined to be triggered based on the track or the acquired surface status information, a condition check is performed, and the preset event includes any one of the flight takeoff status and the flight landing status, and the condition check includes at least one of the data source check, the timeliness check, the relevance check, and the surface status verification; the message sending operation is performed according to the condition check result. The embodiment of the present application can utilize radar or the tower electronic progress sheet to identify the takeoff status or landing status of the flight, improve the accuracy of flight status judgment, reduce the possibility that some flights cannot send messages in time, improve the stability of aviation management operations, and improve the safety of flights and the reliability of flight management. BRIEF DESCRIPTION OF THE DRAWINGS
[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following is a brief introduction to the drawings required for use in describing the embodiments of the present application.
[0033] Figure 1 A flowchart of a method for sending messages based on flight takeoffs and landings provided in an embodiment of the present application;
[0034] Figure 2 A schematic diagram of take-off state determination provided by an embodiment of the present application;
[0035] Figure 3 A schematic diagram of the landing status judgment provided in an embodiment of the present application;
[0036] Figure 4 A flowchart of the method for sending messages based on flight takeoffs and landings provided in an embodiment of the present application;
[0037] Figure 5 A structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0038] The embodiments of the present application are described below in conjunction with the drawings in the present application. It should be understood that the implementation methods described below in conjunction with the drawings are exemplary descriptions for explaining the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions of the embodiments of the present application.
[0039] It will be understood by those skilled in the art that, unless specifically stated, the singular forms "one", "said", and "the" used herein may also include plural forms. It should be further understood that the terms "including" and "comprising" used in the embodiments of the present application refer to that the corresponding features can be implemented as the presented features, information, data, steps, operations, elements and / or components, but do not exclude the implementation of other features, information, data, steps, operations, elements, components and / or combinations thereof supported by the present technical field. It should be understood that when we say that an element is "connected" or "coupled" to another element, the one element may be directly connected or coupled to the other element, or it may refer to that the one element and the other element establish a connection relationship through an intermediate element. In addition, the "connection" or "coupling" used herein may include wireless connection or wireless coupling. The term "and / or" used herein indicates at least one of the items defined by the term, for example, "A and / or B" indicates that it is implemented as "A", or is implemented as "A", or is implemented as "A and B".
[0040] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.
[0041] The following describes several exemplary embodiments to illustrate the technical solutions of the embodiments of the present application and the technical effects produced by the technical solutions of the present application. It should be noted that the following embodiments can refer to, draw on or combine with each other, and the same terms, similar features and similar implementation steps in different embodiments will not be described repeatedly.
[0042] The flight takeoff and landing-based message sending method, device, medium and product provided in the present application are intended to solve at least one technical problem existing in the prior art.
[0043] In an embodiment of the present application, a method for sending messages based on flight takeoffs and landings is provided. The method can be used for mobile phones, computers, towers, flight information processing subsystem (FIPS) of the integrated information control system, and other objects that can make status judgments and execute message sending operations based on track and scene status information.
[0044] Alternatively, if Figure 1-Figure 4 As shown, the message sending method based on flight take-off and landing of the present application includes:
[0045] S101: Use radar to obtain flight tracks within the airspace.
[0046] Optionally, radar is used to obtain the track of an aircraft in the airspace, including: obtaining the track data of the aircraft, and obtaining a target track corresponding to the flight plan of the flight based on the track data, the track data including at least the flight number, transponder, and take-off point.
[0047] Optionally, the track data can be an aircraft operation status dictionary. The track is received, analyzed and processed by the FIPS system, the airspace situation within the control range is modeled, and the aircraft operation status dictionary within the airspace is maintained and updated. Each element of the dictionary is the relevant information of a single flight. The operation status dictionary contains track data of multiple flights. These track data are stored in the memory as "key-value" pairs and retrieved by "key". The index key between rows is set by the track number and the transponder. The track data of the flight is added if there is none, updated if there is, and deleted if expired. The airspace situation is periodically output and updated according to the aircraft monitoring data, and the relevant events such as flight take-off and landing are judged.
[0048] Optionally, after acquiring the track data, the track data can be matched with the flight plan to obtain the association result between the track related to the track data and the flight plan. The track is determined as a related track or an unrelated track based on the association result. Specifically, acquiring the target track corresponding to the flight plan based on the track data includes: acquiring the matching information between each track in the track data and the flight plan, and determining the target track based on the matching information, wherein the target track includes any one of a related track and an unrelated track. Among them, the operation of acquiring the track data can be acquiring new track data or updating the track data, such as detecting a new aircraft entering the airspace, updating the track data of an aircraft in the airspace, and changes in other track data.
[0049] In one embodiment, after obtaining the track data, the track is first matched with the flight plan to identify related tracks and unrelated tracks. Among them, the related track is: the track whose flight number, transponder and take-off place are consistent with the track data and the flight plan, and the deviation of the take-off time (actual take-off time or expected take-off time) corresponding to the track in the track data and the expected take-off time of the flight plan is less than a first threshold value (such as 6 hours). Unrelated tracks are: the transponder is consistent, the flight plan is to take off from this airport, and the deviation of the take-off time of the track from the expected take-off time of the flight plan is less than a second threshold value (such as 3 hours). If the take-off time is not included in the track data, the track update time (a data content in the track data, recording the time when the track signal corresponding to the track is output) is used instead.
[0050] Optionally, after identifying the target track according to the matching result of the track data and the flight plan, motion data of the target track within a predetermined range is collected, and whether a take-off event or a landing event occurs is detected according to the motion data.
[0051] S102: If it is determined that a preset event is triggered according to the track or scene status information, a condition check is performed.
[0052] Optionally, the preset event includes any one of the flight take-off status and the flight landing status, the condition check includes at least one of the data source check, timeliness check, relevance check and surface status verification, and the surface status information is obtained through the tower electronic process sheet.
[0053] Optionally, the determination of triggering a preset event includes: obtaining motion data of the target track within a predetermined range, the predetermined range being determined based on the airport center point and the control altitude; determining the motion trend of the target track relative to the airport center point and the control altitude based on the motion data; if the motion trend satisfies a preset trend, determining to trigger a preset event corresponding to the preset trend that is satisfied; or obtaining scene status information through the tower electronic process sheet system, and detecting whether a preset event is triggered based on scene status change information in the scene status information.
[0054] Optionally, the predetermined range includes a horizontal range and a height range, wherein the horizontal range is a circle center area with the center point of the airport as the center and a predetermined length as the radius, and the height range is a cylindrical area with the circle center area as the bottom, and the height of the cylindrical area is the control height. The horizontal range can also be a rectangular area with the airport center coordinate point as the origin, extending along the runway direction, and with a length and width of a specified length and width, and the height range can be a rectangular area with the bottom as the height of the rectangle and the height as the control height. The location information related to the predetermined range can be determined using geodetic longitude and latitude coordinates and Cartesian plane coordinates, and the height can be determined using pressure altitude.
[0055] Optionally, the preset trend may include a trend of gradually moving farther and higher, and a trend of gradually approaching and gradually decreasing. Among them, if within a predetermined range, it is determined based on the aircraft's track that it has a trend of gradually moving farther and higher, then the flight is determined to take off, and a takeoff event is triggered (that is, the flight status is in the takeoff state). If the altitude corresponding to the aircraft's track of certain data is less than the control altitude, and the position of most of the track and the position of the airport center point are approaching in the horizontal direction and decreasing in the vertical direction. Then it is determined that the flight has landed, and a landing event is triggered.
[0056] In one embodiment, Figure 2 As shown, the control altitude can be 1000m, the center point of the airport is the origin, the track of the aircraft is collected by radar, and the track is displayed in the form of points. Figure 2 According to the figure, it can be seen that a certain number of tracks are less than the control altitude, and the positions of most tracks tend to be farther away from the center of the airport in the horizontal direction and higher in the vertical direction. It is determined that the tracks have a tendency to be farther away and higher, triggering a takeoff event.
[0057] Optionally, when detecting whether a landing event is triggered, the control altitude may be the flight's missed approach altitude. If the flight track shows an asymptotically decreasing trend, and the altitude of part of the flight track is lower than the missed approach altitude, the flight is determined to have landed, triggering a landing event. The missed approach altitude may be determined based on the airport elevation and the ground pressure altitude.
[0058] Optionally, the track data of the landing flights at the current airport can be collected, the pressure altitude corresponding to the last track data of each landing flight can be counted, the average value of the pressure altitude can be calculated, and the average value can be determined as the touchdown pressure altitude of the flight. Whether the touchdown pressure altitude is reasonable (such as matching the airport elevation) is detected according to the airport elevation. If it is reasonable, the touchdown pressure altitude is used as the go-around altitude. If it is unreasonable, the go-around altitude is determined according to the airport elevation or the data of the pressure altimeter.
[0059] In one embodiment, for the determination of the gradually decreasing trend, such as Figure 3 As shown, the track of the aircraft is collected and displayed in the form of points. Figure 3 In, according to Figure 3 It can be seen that a certain number of tracks are less than the control altitude, and the positions corresponding to most of the tracks are asymptotically approaching the position of the airport center point in the horizontal direction and gradually decreasing in the vertical direction. When the altitude corresponding to the track is lower than the missed approach altitude (such as 30m), the landing event is determined to be triggered.
[0060] Optionally, the scene status information can be obtained through the data exchange interface of the TOMS (Tower Electronic Process Sheet) system, and the scene status change information can be obtained using the scene status information, and whether the preset event is triggered or not can be determined based on the scene status change information.
[0061] In one embodiment, after receiving an operation instruction to transmit scene status information, the TOMS system may transmit the scene status information to the FIPS system executing the method of the present application through a data exchange interface.
[0062] Optionally, after acquiring the surface status information, the surface status information is used to acquire the surface status of flights that have not taken off (such as the flight plan has not been cancelled, deleted, or there is no actual take-off time) and flights that have not landed (such as the flight plan has not been cancelled, deleted, or there is no actual landing time). If it is determined that the surface status of the flight that has not taken off has changed from "issued take-off order (TAK)" to "take-off (FIN)", it is determined that the take-off event is triggered. If the surface status of the flight that has not landed has changed from "landed (TCH)" to "VAC (vacated runway), TAX (taxiing), or FIN", it is determined that the landing event is triggered.
[0063] Optionally, after determining that a takeoff event or a landing event is triggered, information of the triggered takeoff event or the landing event is stored, the information including the triggering event, event-related track or surface status information, and flight information.
[0064] Optionally, after determining that the flight has triggered a take-off event or a landing event, a condition check is required. Wherein, when the condition check is a data source check, the data source check includes: determining the data source corresponding to the triggered preset event, the data source includes at least one of the track and the scene status information; if it is determined that the current sending mode is consistent with the data source, then it is determined that the check has passed.
[0065] In one embodiment, different sending modes can be set according to different data sources. When the sending mode is consistent with the data source corresponding to the triggered takeoff event or landing event (for example, the takeoff event is triggered by scene status information, the data source is scene status information, and the data source corresponding to the current sending mode is also scene status information, and the two data sources are consistent), a message is generated and sent, otherwise the event is ignored.
[0066] Optionally, the timeliness check may be to compare the trigger time with the current time. If the deviation between the trigger time and the current time is greater than a third time threshold (eg, 30 minutes), the takeoff event or landing event corresponding to the trigger time is ignored.
[0067] Optionally, when the condition check includes a correlation check, the correlation check includes: obtaining correlation information corresponding to the triggered preset event, determining the inspection result according to the correlation information, the correlation information including at least one of task information, take-off and landing information, and whether the telegram address exists.
[0068] Optionally, different operations are performed according to different inspection results, wherein if it is determined according to the task information that the flight corresponding to the triggered preset event is a training flight of this airport, no processing is performed. If it is determined according to the take-off and landing information that the corresponding flight is not a flight taking off and landing at this airport, no processing is performed and an alarm is issued; if it is determined that the flight corresponding to the triggered preset event has no relevant telegram address, no processing is performed and an alarm is issued.
[0069] Optionally, to improve data processing efficiency, after the data source check, timeliness check and relevance check are all passed, the scene status verification can be performed. The scene status verification includes: obtaining the flight number corresponding to the triggered preset event; using the flight number to query the state information and the time when the track event occurred in the scene status information; and determining the inspection result according to the query result.
[0070] Optionally, the surface state verification method corresponding to the take-off event is the same as the surface state verification method related to the landing event.
[0071] In one embodiment, when performing surface status verification for a takeoff event, the flight number (FPID) of the flight that triggers the takeoff event can be obtained, and the flight number is used to search whether the flight corresponding to the flight number in the surface status information has a specified state (ES) at the same time. If it exists, a message is generated and sent, and an event processing flag is set for the takeoff event; otherwise, the track event generation time (TE) is obtained, and the time is compared with the current time (TN). If it is determined that the difference between the two exceeds the set fourth threshold time, an alarm is issued, and if it does not exceed, no alarm is issued.
[0072] Optionally, when an alarm is issued, an alarm message may be sent to a designated object to remind the object to perform manual intervention, thereby reducing the possibility of errors in monitoring of take-off events and landing events.
[0073] S103: Execute a message sending operation according to the condition check result.
[0074] Optionally, if it is determined that the message can be sent according to the condition check result, a message corresponding to the triggered preset event is generated, and the message is sent according to the sending address corresponding to the message.
[0075] The message sending method based on flight takeoff and landing of the present application utilizes the scanning data of the radar and the field status information to detect whether a takeoff event or a landing event is triggered, and can more accurately determine the takeoff and landing time of the flight, thereby avoiding mis-sending or missing sending due to the shutdown of the local radar and inaccurate comprehensive track data, avoiding the original airport from making a false report due to the flight approaching the airport for a go-around and standby landing, and avoiding the radar track matching the wrong flight due to the transponder being occupied, resulting in a false report, and there is no need for large-scale upgrade and transformation of the system, thereby reducing the cost of aviation management.
[0076] In an optional embodiment, an electronic device is provided, such as Figure 5 As shown, Figure 5 The electronic device 4000 shown includes: a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, such as through a bus 4002. Optionally, the electronic device 4000 may also include a transceiver 4004, which may be used for data interaction between the electronic device and other electronic devices, such as data transmission and / or data reception. It should be noted that in actual applications, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of the present application.
[0077] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.
[0078] The bus 4002 may include a path to transmit information between the above components. The bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 4002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.
[0079] Memory 4003 can be ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or it can be EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disc, optical disk, digital versatile disc, Blu-ray disc, etc.), magnetic disk storage medium, other magnetic storage devices or any other medium that can be used to carry or store computer programs and can be read by a computer, without limitation here.
[0080] The memory 4003 is used to store the computer program for executing the embodiment of the present application, and the execution is controlled by the processor 4001. The processor 4001 is used to execute the computer program stored in the memory 4003 to implement the steps shown in the above method embodiment.
[0081] Among them, the electronic device can be any electronic product that can interact with an object, such as a personal computer, a tablet computer, a smart phone, a personal digital assistant (PDA), a game console, an interactive network television (IPTV), a smart wearable device, etc.
[0082] The electronic device may also include a network device and / or an object device, wherein the network device includes, but is not limited to, a single network server, a server group consisting of multiple network servers, or a cloud consisting of a large number of hosts or network servers based on cloud computing.
[0083] The network where the electronic device is located includes but is not limited to the Internet, a wide area network, a metropolitan area network, a local area network, a virtual private network (Virtual Private Network, VPN), etc.
[0084] An embodiment of the present application provides a computer-readable storage medium, which includes a computer program. When the computer program is executed by a processor, the steps and corresponding contents of the aforementioned method embodiment can be implemented.
[0085] An embodiment of the present application provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps and corresponding contents of the aforementioned method embodiment can be implemented.
[0086] The terms "first", "second", "third", "fourth", "1", "2", etc. (if any) in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than that shown or described in the drawings.
[0087] It should be understood that, although each operation step is indicated by arrows in the flowchart of the embodiment of the present application, the implementation order of these steps is not limited to the order indicated by the arrows. Unless clearly stated herein, in some implementation scenarios of the embodiment of the present application, the implementation steps in each flowchart can be performed in other orders according to demand. In addition, some or all of the steps in each flowchart may include multiple sub-steps or multiple stages based on actual implementation scenarios. Some or all of these sub-steps or stages may be executed at the same time, and each sub-step or stage in these sub-steps or stages may also be executed at different times respectively. In different scenarios of execution time, the execution order of these sub-steps or stages may be flexibly configured according to demand, and the embodiment of the present application does not limit this.
[0088] The above is only an optional implementation method for some implementation scenarios of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the technical concept of the solution of the present application, other similar implementation methods based on the technical ideas of the present application are also within the protection scope of the embodiments of the present application.
Claims
1. A method for sending messages based on flight take-off and landing, characterized in that: The method comprises: Use radar to obtain flight tracks within the airspace; If a preset event is determined to be triggered according to the flight track or surface status information, a condition check is performed, wherein the preset event includes any one of a flight take-off status and a flight landing status, and the condition check includes at least one of a data source check, a timeliness check, a relevance check, and a surface status verification, and the surface status information is obtained through an electronic progress sheet of the tower; Execute the message sending operation based on the condition check result.
2. The method for sending messages based on flight take-offs and landings according to claim 1, characterized in that: The method of obtaining the flight path of an aircraft in an airspace by using radar includes: Acquire the track data of the aircraft, and acquire the target track corresponding to the flight plan of the flight according to the track data, wherein the track data at least includes the flight number, transponder, and take-off point.
3. The method for sending messages based on flight take-offs and landings according to claim 2, characterized in that: The step of acquiring a target track corresponding to the flight plan according to the track data includes: The matching information between each track in the track data and the flight plan of the flight is obtained, and the target track is determined according to the matching information, wherein the target track includes any one of a related track and an unrelated track.
4. The method for sending messages based on flight take-offs and landings according to claim 2, characterized in that: Determination of triggering preset events, including: Acquire motion data of the target track within a predetermined range, where the predetermined range is determined based on the airport center point and the control altitude; Determine the movement trend of the target track relative to the airport center point and the control altitude according to the movement data; If the movement trend meets the preset trend, determining a preset event corresponding to the preset trend that is triggered; Or, the scene status information is obtained through the tower electronic process sheet system, and whether a preset event is triggered is detected according to the scene status change information in the scene status information.
5. The method for sending messages based on flight take-offs and landings according to claim 4, characterized in that: The condition check includes a data source check, and the data source check includes: Determine a data source corresponding to the preset event that is triggered, wherein the data source includes at least one of a track and a scene status information; If it is determined that the current sending mode is consistent with the data source, then it is determined that the check is passed.
6. The method for sending messages based on flight take-offs and landings according to claim 1, characterized in that: The condition check includes a relevance check, and the relevance check includes: Acquire the associated information corresponding to the triggered preset event, and determine the inspection result according to the associated information, wherein the associated information includes at least one of task information, take-off and landing information, and whether the telegram address exists.
7. The method for sending messages based on flight take-offs and landings according to claim 1, characterized in that: The condition check includes scene status verification, and the scene status verification includes: Obtain the flight number corresponding to the preset event that is triggered; Utilize the flight number to query the status information and the time when the track event occurs in the surface status information; The inspection result is determined based on the query result.
8. An electronic device comprising a memory, a processor and a computer program stored in the memory, characterized in that: The processor executes the computer program to implement the steps of the method according to any one of claims 1 to 7.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.
Citation Information
Cited By
Flight event processing method and device, electronic equipment and computer program product
CN121686848A