CN112668937A - Flight data monitoring method and related device - Google Patents

Flight data monitoring method and related device Download PDF

Info

Publication number
CN112668937A
CN112668937A CN202110062630.1A CN202110062630A CN112668937A CN 112668937 A CN112668937 A CN 112668937A CN 202110062630 A CN202110062630 A CN 202110062630A CN 112668937 A CN112668937 A CN 112668937A
Authority
CN
China
Prior art keywords
data
flight
event
passenger
preset special
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110062630.1A
Other languages
Chinese (zh)
Inventor
涂卫平
王艺超
刘梓辉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Travelsky Technology Co Ltd
China Travelsky Holding Co
Original Assignee
China Travelsky Holding Co
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Travelsky Holding Co filed Critical China Travelsky Holding Co
Priority to CN202110062630.1A priority Critical patent/CN112668937A/en
Publication of CN112668937A publication Critical patent/CN112668937A/en
Pending legal-status Critical Current

Links

Images

Abstract

The application discloses a flight data monitoring method and a related device, wherein the flight data monitoring method is realized based on a flight management system comprising a bridging module, firstly abnormal data is obtained through monitoring and the like, then based on a bridging module, acquiring passenger data and flight data, integrating the passenger data and the flight data, judging whether the abnormal data is a preset special event, and finally judging whether the preset special event affects flight operation when the abnormal data is the preset special event, if so, determining the preset special event as a target event, generating memo information for storage or generating notification information according to the type of the target event, and sending the notification information to the passenger or the passenger management module, so as to realize memo or notification aiming at the target event, and improve the data freshness of the flight information or the passenger information cached in the passenger management module.

Description

Flight data monitoring method and related device
Technical Field
The present application relates to the field of computer application technologies, and in particular, to a flight data monitoring method and a related device.
Background
With the continuous development of computer technology, computer technology is increasingly used in the travel industry for managing and supporting travel reservations and data associated therewith.
During the process of booking flights, events of flight availability may occur, which may cause the data freshness of the booking data of a certain flight to be lost, and thus, the experience of booking flights for passengers is adversely affected.
Disclosure of Invention
In order to solve the technical problem, the application provides a flight data monitoring method and a related device, so as to solve the problem that the data freshness of flight data is lost due to the occurrence of a special event.
In order to achieve the technical purpose, the embodiment of the application provides the following technical scheme:
a flight data monitoring method is realized based on a flight management system comprising a bridge module, wherein a flight module in the flight management system and a passenger management module are connected with a bridge through the bridge module, and the flight data monitoring method comprises the following steps:
acquiring abnormal data;
acquiring passenger data and flight data based on the bridging module, integrating the passenger data and the flight data, and judging whether the abnormal data is a preset special event;
when the abnormal data is a preset special event, judging whether the preset special event affects the flight operation, if so, determining the preset special event as a target event, generating memo information according to the type of the target event, storing the memo information or generating notification information, and sending the notification information to a passenger or a passenger management module.
A flight data monitoring system is realized based on a flight management system comprising a bridge module, wherein a flight module and a passenger management module in the flight management system are connected with a bridge through the bridge module, and the flight data monitoring system comprises:
the data acquisition module is used for acquiring abnormal data;
the event determining module is used for acquiring passenger data and flight data based on the bridging module, integrating the passenger data and the flight data and judging whether the abnormal data is a preset special event or not;
and the event processing module is used for judging whether the preset special event influences the flight operation when the abnormal data is the preset special event, if so, determining the preset special event as a target event, generating memo information according to the type of the target event, storing the memo information or generating notification information and sending the notification information to a passenger or a passenger management module.
A flight data monitoring system, comprising: a memory and a processor;
the memory is used for storing program codes, and the processor is used for calling the program codes, wherein the program codes are used for the flight data monitoring method in any one of the above items.
A storage medium having stored thereon program code which, when executed, implements a flight data monitoring method as in any one of the above.
From the above technical solutions, embodiments of the present application provide a flight data monitoring method and a related device, wherein, the flight data monitoring method is realized based on a flight management system comprising a bridging module, firstly obtains abnormal data by monitoring and the like, then based on a bridging module, acquiring passenger data and flight data, integrating the passenger data and the flight data, judging whether the abnormal data is a preset special event, and finally judging whether the preset special event affects flight operation when the abnormal data is the preset special event, if so, determining the preset special event as a target event, generating memo information for storage or generating notification information according to the type of the target event, and sending the notification information to the passenger or the passenger management module, so as to realize memo or notification aiming at the target event, and improve the data freshness of the flight information or the passenger information cached in the passenger management module.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a schematic flow chart of a flight data monitoring method according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a flight management system according to an embodiment of the present application;
fig. 3 is a schematic flow chart of a flight data monitoring method according to another embodiment of the present application;
fig. 4 is a schematic structural diagram of a flight data monitoring system according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a flight data monitoring system according to another embodiment of the present application.
Detailed Description
As described in the background, computer technology is increasingly being used in the travel industry to manage and support travel reservations and data associated therewith. In particular, third party booking agents (e.g., travel agencies) and/or customers (e.g., travelers) often utilize computer-based devices or Web portals to interact with booking systems (e.g., Global Distribution Systems (GDSs)) to book travel for customer scheduling and/or travel related services. When booking travel-related services using such a reservation terminal in communication with such a travel reservation system, the travel agency and/or the customer may initiate a reservation session between the reservation terminal and the travel reservation system to reserve one or more travel inventory items corresponding to the travel for the relevant services (e.g., flights, hotels, rail transportation, dining reservations, etc.) provided to the customer during the reservation session.
Availability-based data used in flight searches associated with the reservation process may be derived from a cache, thereby avoiding the need for real-time shopping queries and determinations. The quality of cached availability-based data is based on a balance between data freshness and the likelihood of value changes. The quality of cache-based availability-based data may degrade over time due to lost data freshness. Furthermore, the occurrence of events that affect flight availability may cause altitude fluctuations that affect the accuracy of the cached availability-based data.
In order to solve the problem, the embodiment of the present application provides a flight data monitoring method, which is implemented based on a flight management system including a bridge module, and firstly obtains abnormal data by monitoring and the like, then based on a bridging module, acquiring passenger data and flight data, integrating the passenger data and the flight data, judging whether the abnormal data is a preset special event, and finally judging whether the preset special event affects flight operation when the abnormal data is the preset special event, if so, determining the preset special event as a target event, generating memo information for storage or generating notification information according to the type of the target event, and sending the notification information to the passenger or the passenger management module, so as to realize memo or notification aiming at the target event, and improve the data freshness of the flight information or the passenger information cached in the passenger management module.
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The embodiment of the application provides a flight data monitoring method, as shown in fig. 1, which is implemented based on a flight management system including a bridge module, wherein a flight module in the flight management system is connected with a passenger management module through the bridge module, and the flight data monitoring method includes:
s101: acquiring abnormal data;
s102: acquiring passenger data and flight data based on the bridging module, integrating the passenger data and the flight data, and judging whether the abnormal data is a preset special event;
s103: when the abnormal data is a preset special event, judging whether the preset special event affects the flight operation, if so, determining the preset special event as a target event, generating memo information according to the type of the target event, storing the memo information or generating notification information, and sending the notification information to a passenger or a passenger management module.
Referring to fig. 2, fig. 2 shows a specific structural diagram of the flight management system, and the flight management system includes: an operating system, at least one processor, memory (e.g., a distributed storage module), and a flight monitoring module and a passenger monitoring module. The flight management system may include a user interface that incorporates one or more user input/output devices, such as a keyboard, pointing device, display, printer, etc., and a network interface. Alternatively, the input may be information received through another computer or terminal (e.g., a client system, a provider system, and/or a travel reservation system) through a network interface coupled to a network. The flight management system typically operates under the control of an operating system for controlling a flight monitoring module comprising an event management unit, an observation unit and a bridge unit. The event manager unit may be configured to receive and aggregate specific events and related events that may affect the availability change. Events are considered to be specific events because each event is selected from a plan, inventory, and distribution event. An event is considered relevant if it has a significant impact on flight availability. The event manager unit may receive availability data and sales data from the travel reservation system, receive inventory traffic, and interface with the observation unit. The passenger monitoring module stores information such as passenger flight records and the like.
The observation unit is used to monitor a given travel domain, such as the flight domain in the exemplary embodiment, and determine the monitored flight domain affected by an event arriving from the event management unit. The flight domain includes a set of customer-supplied flights, possibly including travel solutions, flight dates and/or slots. The flight domain may be limited to a particular market (e.g., flights departing from beijing or arriving in the sea), a particular departure or arrival location (e.g., beijing T2 airport), further limiting the category of a particular market or location, in which case the event details received by the observation unit are communicated to the bridge unit. The observation unit implements additional offline services to initialize and set each monitored flight domain and to prospectively modify each monitored flight domain.
The bridge module is used to provide a link to the customer based on information about the flight domain affected by the event and triggering a notification. Based on the details provided by the observation unit on the bay/flight status change, the bridge unit retrieves one or more flight domains that are specifically affected (e.g., aircraft stopped, delayed, etc.) and sends a notification to the cache system to notify the client system. Upon receiving such a notification, the client system may delete the travel solution, may assign the travel solution for recalculation, may assign a recalculation priority, and so forth. The bridge unit may also trigger a new viewing task to the observation unit when the new flight domain comes from one of the client systems.
The distributed data storage module includes a database that includes data and supporting data structures that store and organize the data. Specifically, the distributed data storage module contains all passenger flight records for each customer and updates the status of the passenger flight records. The distributed data storage module may be arranged with a relational database, a hierarchical database, a network database and/or combinations thereof. The distributed data storage module includes a database that uses an open source relational database management system and operates as a server providing multi-user access to multiple databases, critically a travel segment date in the form of a representative of flight dates, each schedule being a combination of a schedule and a date, meaning a single instance of a schedule that operates on a given date in the year. The contents of the distributed data storage module are a set of availability values or availability publications (e.g., direct online intermodal, origin and destination, airline flight transfer listings, originator of requests) stored according to market and/or context. For availability releases associated with low cost operators, the price of the travel solution may also be available in the corresponding release stored by the distributed data storage module.
The flight data monitoring method provided by the embodiment of the application can be implemented based on the flight management system shown in fig. 2.
The following describes a feasible implementation process of each step of the flight data monitoring method provided by the embodiment of the present application.
Optionally, referring to fig. 3, the acquiring the abnormal data includes:
s1011: receiving a request for a triggering event;
s1012: and generating the abnormal data according to the request of the triggering event, wherein the abnormal data at least comprises one of abnormal weather data and abnormal holiday flight operation data.
The request for the trigger event may be, for example, receiving an abnormal factor affecting flight operation, and generating abnormal data based on the request, such as weather parameter influence caused by extreme weather, holiday abnormal flight operation data, and the like.
Optionally, still referring to fig. 3, the integrating the passenger data and the flight data, and determining whether the abnormal data is a preset special event includes:
s1021: judging whether the abnormal data is a preset special event or not by combining the flight data, the data relation between the passenger seat rate and the time in the passenger data, the passenger full period setting data, the passenger seat rate data of a special date, the flight change rate caused by extreme weather and the special operation data of the passenger;
in this step, the bridge module may bridge-link the flight information and the passenger information, integrate the flight data and the passenger data to perform a data bridge analysis database, and determine the special event according to the bridge analysis database.
The special operation data includes at least one of cancelling flights, transferring flights, and changing flights.
The step of judging whether the preset special event affects the flight operation comprises the following steps:
s1031: determining the type of the preset special event, and acquiring an event influence value corresponding to the preset special event of the type;
s1032: and judging whether the event influence value corresponding to the preset special event exceeds the acquired event influence value, if so, judging that the flight operation is influenced by the preset special event, and if not, judging that the flight operation is not influenced by the preset special event.
In the embodiment, for different types of preset special events, a corresponding flight operation affecting data threshold is set, and an event with an event affecting value greater than the threshold is determined as the preset special event affecting flight operation. For example, rainfall in extreme weather is greater than a certain rainfall amount or a thunderstorm alarm value, flight operation is affected, the holiday passenger flow rate is increased greatly and is increased to a certain threshold value, and an airline company increases flights to relieve the situation.
Still referring to fig. 3, the generating memo information for storage or generating notification information to send to the passenger or the passenger management module according to the target event category includes:
s1033: when the target event is a first type of target event, generating notification information and sending the notification information to a passenger or a passenger management module;
s1034: when the target event is a second type of target event, generating memo information for storage;
the first type of target event at least comprises flight cancellation, flight delay and temporary increase of flights, wherein the takeoff time of the increased flights is coincident with the travel time of passengers;
the second type of target event comprises a temporary increase flight, and the takeoff time of the increased flight is not overlapped with the travel time of the passenger.
In this embodiment, according to flights affected by special events, the bridge unit classifies the passenger trip data according to the flight information of the special events and the passenger information, some special events affect the passenger trip, for example, extreme weather causes the flight cancellation or delay, special dates (holidays) may temporarily increase the flights, some passengers who have scheduled the flights may have many more time choices, and passengers may also cancel inappropriate time trips to make a reptation trip, thereby affecting the passenger trip. Such special events affect flights and cause hard situations for travel of passengers, and notifications are sent to passengers.
If the travel of the passenger is not influenced by the condition that the flight operation changes, for example, the time of the special date increased flight and the flight time of the passenger travel are within a certain threshold range, the travel of the passenger is not influenced, at the moment, any message is not sent to the passenger, and the memo information is generated and stored.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
Although the operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flight data monitoring system provided in the embodiment of the present application is described below, and the flight data monitoring system described below may be referred to in correspondence with the flight data monitoring method described above.
Correspondingly, an embodiment of the present application further provides a flight data monitoring system, as shown in fig. 4, which is implemented based on a flight management system including a bridge module, where a flight module and a passenger management module in the flight management system are connected to a bridge through the bridge module, and the flight data monitoring system includes:
a data acquisition module 100, configured to acquire abnormal data;
an event determining module 200, configured to obtain passenger data and flight data based on the bridge module, synthesize the passenger data and the flight data, and determine whether the abnormal data is a preset special event;
the event processing module 300 is configured to, when the abnormal data is a preset special event, determine whether the preset special event affects flight operation, if so, determine the preset special event as a target event, generate memo information according to the type of the target event, store the memo information, or generate notification information, and send the notification information to a traveler or a traveler management module.
Optionally, the data obtaining module includes:
a request receiving unit, configured to receive a request for a trigger event;
and the data generation unit is used for generating the abnormal data according to the request of the trigger event, wherein the abnormal data at least comprises one of abnormal weather data and abnormal holiday flight operation data.
Optionally, the event determining module integrates the passenger data and the flight data, and determines whether the abnormal data is a preset special event, specifically, in combination with the flight data, a data relationship between a passenger seat rate and time in the passenger data, passenger full period setting data, passenger seat rate data on a special date, a flight change rate caused by extreme weather, and special operation data of the passenger, determines whether the abnormal data is the preset special event;
the special operation data includes at least one of cancelling flights, transferring flights, and changing flights.
Optionally, the event processing module determines whether the preset special event affects flight operation, specifically, determines a type of the preset special event, and obtains an event impact value corresponding to the preset special event of the type;
and judging whether the event influence value corresponding to the preset special event exceeds the acquired event influence value, if so, judging that the flight operation is influenced by the preset special event, and if not, judging that the flight operation is not influenced by the preset special event.
Optionally, the event processing module generates memo information for storage or generates notification information for sending to the passenger or the passenger management module according to the type of the target event, and the notification information is specifically used for generating the notification information and sending to the passenger or the passenger management module when the target event is a first type of target event;
when the target event is a second type of target event, generating memo information for storage;
the first type of target event at least comprises flight cancellation, flight delay and temporary increase of flights, wherein the takeoff time of the increased flights is coincident with the travel time of passengers;
the second type of target event comprises a temporary increase flight, and the takeoff time of the increased flight is not overlapped with the travel time of the passenger.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a unit does not in some cases constitute a limitation of the unit itself, for example, the first retrieving unit may also be described as a "unit for retrieving at least two internet protocol addresses".
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
Correspondingly, an embodiment of the present application further provides a flight data monitoring system, as shown in fig. 5, including: memory 100A and processor 200A;
the memory is configured to store program code, the processor is configured to invoke the program code, and the program code is configured to:
acquiring abnormal data;
acquiring passenger data and flight data based on the bridging module, integrating the passenger data and the flight data, and judging whether the abnormal data is a preset special event;
when the abnormal data is a preset special event, judging whether the preset special event affects the flight operation, if so, determining the preset special event as a target event, generating memo information according to the type of the target event, storing the memo information or generating notification information, and sending the notification information to a passenger or a passenger management module.
Correspondingly, an embodiment of the present application further provides a storage medium, where the storage medium stores program codes, and the program codes, when executed, implement the flight data monitoring system according to any one of the above embodiments.
In the context of this disclosure, a storage medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The storage medium may be a machine-readable signal medium or a machine-readable storage medium. A storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
It should be noted that the storage media described above in this disclosure can be computer readable signal media or computer readable storage media or any combination of the two. A storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of storage media may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a storage medium may include a propagated data signal with computer-readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A storage medium may also be any computer-readable medium that is not a computer-readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
The storage medium may be included in the electronic device; or may exist separately without being assembled into the electronic device.
Example 1 provides a flight data monitoring method, which is implemented based on a flight management system including a bridge module, where a flight module and a passenger management module in the flight management system connect a bridge through the bridge module, and the flight data monitoring method includes:
acquiring abnormal data;
acquiring passenger data and flight data based on the bridging module, integrating the passenger data and the flight data, and judging whether the abnormal data is a preset special event;
when the abnormal data is a preset special event, judging whether the preset special event affects the flight operation, if so, determining the preset special event as a target event, generating memo information according to the type of the target event, storing the memo information or generating notification information, and sending the notification information to a passenger or a passenger management module.
In one or more embodiments disclosed herein, example 2 provides the flight data monitoring method of example 1, wherein the obtaining of the abnormal data includes:
receiving a request for a triggering event;
and generating the abnormal data according to the request of the triggering event, wherein the abnormal data at least comprises one of abnormal weather data and abnormal holiday flight operation data.
In one or more embodiments disclosed herein, example 3 provides the flight data monitoring method of example 1, wherein the integrating the passenger data and the flight data to determine whether the abnormal data is a preset special event includes:
judging whether the abnormal data is a preset special event or not by combining the flight data, the data relation between the passenger seat rate and the time in the passenger data, the passenger full period setting data, the passenger seat rate data of a special date, the flight change rate caused by extreme weather and the special operation data of the passenger;
the special operation data includes at least one of cancelling flights, transferring flights, and changing flights.
In one or more embodiments disclosed herein, example 4 provides the flight data monitoring method of example 1, wherein the determining whether the preset special event affects flight operation includes:
determining the type of the preset special event, and acquiring an event influence value corresponding to the preset special event of the type;
and judging whether the event influence value corresponding to the preset special event exceeds the acquired event influence value, if so, judging that the flight operation is influenced by the preset special event, and if not, judging that the flight operation is not influenced by the preset special event.
In one or more embodiments disclosed herein, example 5 provides the flight data monitoring method of example 1, wherein generating memo information for storage or generating notification information for sending to the traveler or a traveler management module according to the target event category includes:
when the target event is a first type of target event, generating notification information and sending the notification information to a passenger or a passenger management module;
when the target event is a second type of target event, generating memo information for storage;
the first type of target event at least comprises flight cancellation, flight delay and temporary increase of flights, wherein the takeoff time of the increased flights is coincident with the travel time of passengers;
the second type of target event comprises a temporary increase flight, and the takeoff time of the increased flight is not overlapped with the travel time of the passenger.
In one or more embodiments disclosed herein, example 6 provides a flight data monitoring system implemented based on a flight management system including a bridge module, where a flight module and a passenger management module in the flight management system connect a bridge through the bridge module, and the flight data monitoring system includes:
the data acquisition module is used for acquiring abnormal data;
the event determining module is used for acquiring passenger data and flight data based on the bridging module, integrating the passenger data and the flight data and judging whether the abnormal data is a preset special event or not;
and the event processing module is used for judging whether the preset special event influences the flight operation when the abnormal data is the preset special event, if so, determining the preset special event as a target event, generating memo information according to the type of the target event, storing the memo information or generating notification information and sending the notification information to a passenger or a passenger management module.
Example 7 provides the flight data monitoring system of example 6, in one or more embodiments disclosed herein, the data acquisition module comprising:
a request receiving unit, configured to receive a request for a trigger event;
and the data generation unit is used for generating the abnormal data according to the request of the trigger event, wherein the abnormal data at least comprises one of abnormal weather data and abnormal holiday flight operation data.
In one or more embodiments disclosed herein, example 8 provides the flight data monitoring system of example 6, wherein the event determining module integrates the passenger data and the flight data, and determines whether the abnormal data is a preset special event, and in combination with the flight data and a data relationship between a passenger seat rate and time in the passenger data, a passenger full period setting data, a passenger seat rate data on a special date, a flight change rate due to extreme weather, and a special operation data of a passenger, determines whether the abnormal data is a preset special event;
the special operation data includes at least one of cancelling flights, transferring flights, and changing flights.
According to one or more embodiments disclosed in the present application, example 9 provides the flight data monitoring system of example 6, where the event processing module determines whether the preset special event affects flight operation, specifically determines a type of the preset special event, and obtains an event impact value corresponding to the preset special event of the type;
and judging whether the event influence value corresponding to the preset special event exceeds the acquired event influence value, if so, judging that the flight operation is influenced by the preset special event, and if not, judging that the flight operation is not influenced by the preset special event.
In one or more embodiments disclosed herein, example 10 provides the flight data monitoring system of example 6, where the event processing module generates memo information according to the types of the target events to store the memo information or generates notification information to send to the traveler or the traveler management module, and is specifically configured to generate the notification information to send to the traveler or the traveler management module when the target event is a first type of target event;
when the target event is a second type of target event, generating memo information for storage;
the first type of target event at least comprises flight cancellation, flight delay and temporary increase of flights, wherein the takeoff time of the increased flights is coincident with the travel time of passengers;
the second type of target event comprises a temporary increase flight, and the takeoff time of the increased flight is not overlapped with the travel time of the passenger.
Example 11 provides, in accordance with one or more embodiments disclosed herein, a flight data monitoring system, comprising: a memory and a processor;
the memory is used for storing program codes, and the processor is used for calling the program codes, and the program codes are used for executing the flight data monitoring method of any one of the above embodiments.
Example 12 provides, in one or more embodiments disclosed herein, a storage medium having program code stored thereon, the program code, when executed, implementing the steps of the flight data monitoring method according to any one of the embodiments.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
While several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.

Claims (12)

1. A flight data monitoring method is realized based on a flight management system comprising a bridge module, wherein a flight module in the flight management system and a passenger management module are connected with a bridge through the bridge module, and the flight data monitoring method comprises the following steps:
acquiring abnormal data;
acquiring passenger data and flight data based on the bridging module, integrating the passenger data and the flight data, and judging whether the abnormal data is a preset special event;
when the abnormal data is a preset special event, judging whether the preset special event affects the flight operation, if so, determining the preset special event as a target event, generating memo information according to the type of the target event, storing the memo information or generating notification information, and sending the notification information to a passenger or a passenger management module.
2. The method of claim 1, wherein the obtaining anomaly data comprises:
receiving a request for a triggering event;
and generating the abnormal data according to the request of the triggering event, wherein the abnormal data at least comprises one of abnormal weather data and abnormal holiday flight operation data.
3. The method of claim 1, wherein integrating the passenger data and the flight data to determine whether the anomaly data is a predetermined special event comprises:
judging whether the abnormal data is a preset special event or not by combining the flight data, the data relation between the passenger seat rate and the time in the passenger data, the passenger full period setting data, the passenger seat rate data of a special date, the flight change rate caused by extreme weather and the special operation data of the passenger;
the special operation data includes at least one of cancelling flights, transferring flights, and changing flights.
4. The method of claim 1, wherein the determining whether the predetermined special event affects flight operations comprises:
determining the type of the preset special event, and acquiring an event influence value corresponding to the preset special event of the type;
and judging whether the event influence value corresponding to the preset special event exceeds the acquired event influence value, if so, judging that the flight operation is influenced by the preset special event, and if not, judging that the flight operation is not influenced by the preset special event.
5. The method of claim 1, wherein generating memo information for storage or generating notification information for sending to a traveler or a traveler management module according to the target event category comprises:
when the target event is a first type of target event, generating notification information and sending the notification information to a passenger or a passenger management module;
when the target event is a second type of target event, generating memo information for storage;
the first type of target event at least comprises flight cancellation, flight delay and temporary increase of flights, wherein the takeoff time of the increased flights is coincident with the travel time of passengers;
the second type of target event comprises a temporary increase flight, and the takeoff time of the increased flight is not overlapped with the travel time of the passenger.
6. A flight data monitoring system implemented based on a flight management system including a bridge module, wherein a flight module and a passenger management module in the flight management system connect a bridge via the bridge module, the flight data monitoring system comprising:
the data acquisition module is used for acquiring abnormal data;
the event determining module is used for acquiring passenger data and flight data based on the bridging module, integrating the passenger data and the flight data and judging whether the abnormal data is a preset special event or not;
and the event processing module is used for judging whether the preset special event influences the flight operation when the abnormal data is the preset special event, if so, determining the preset special event as a target event, generating memo information according to the type of the target event, storing the memo information or generating notification information and sending the notification information to a passenger or a passenger management module.
7. The system of claim 6, wherein the data acquisition module comprises:
a request receiving unit, configured to receive a request for a trigger event;
and the data generation unit is used for generating the abnormal data according to the request of the trigger event, wherein the abnormal data at least comprises one of abnormal weather data and abnormal holiday flight operation data.
8. The system according to claim 6, wherein the event determination module integrates the passenger data and the flight data, and determines whether the abnormal data is a preset special event, and in particular, determines whether the abnormal data is a preset special event by combining the flight data and a data relationship between a passenger seat rate and time in the passenger data, passenger full period setting data, passenger seat rate data of a special date, a flight change rate caused by extreme weather, and special operation data of a passenger;
the special operation data includes at least one of cancelling flights, transferring flights, and changing flights.
9. The system according to claim 6, wherein the event processing module determines whether the preset special event affects flight operation, specifically, determines a type of the preset special event, and obtains an event impact value corresponding to the preset special event of the type;
and judging whether the event influence value corresponding to the preset special event exceeds the acquired event influence value, if so, judging that the flight operation is influenced by the preset special event, and if not, judging that the flight operation is not influenced by the preset special event.
10. The system of claim 6, wherein the event processing module generates memo information for storage or generates notification information for sending to the passenger or the passenger management module according to the type of the target event, and is specifically configured to generate the notification information for sending to the passenger or the passenger management module when the target event is a first type of target event;
when the target event is a second type of target event, generating memo information for storage;
the first type of target event at least comprises flight cancellation, flight delay and temporary increase of flights, wherein the takeoff time of the increased flights is coincident with the travel time of passengers;
the second type of target event comprises a temporary increase flight, and the takeoff time of the increased flight is not overlapped with the travel time of the passenger.
11. A flight data monitoring system, comprising: a memory and a processor;
the memory is configured to store program code, and the processor is configured to invoke the program code, and the program code is configured to perform the flight data monitoring method of any one of claims 1-5.
12. A storage medium having stored thereon program code which, when executed, implements a flight data monitoring method according to any one of claims 1 to 5.
CN202110062630.1A 2021-01-18 2021-01-18 Flight data monitoring method and related device Pending CN112668937A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110062630.1A CN112668937A (en) 2021-01-18 2021-01-18 Flight data monitoring method and related device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110062630.1A CN112668937A (en) 2021-01-18 2021-01-18 Flight data monitoring method and related device

Publications (1)

Publication Number Publication Date
CN112668937A true CN112668937A (en) 2021-04-16

Family

ID=75415561

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110062630.1A Pending CN112668937A (en) 2021-01-18 2021-01-18 Flight data monitoring method and related device

Country Status (1)

Country Link
CN (1) CN112668937A (en)

Similar Documents

Publication Publication Date Title
US10984349B2 (en) Travel advisory notifications
US20040039614A1 (en) System and method to support end-to-end travel service including disruption notification and alternative flight solutions
US20090276250A1 (en) Process and system to determine commercial airline arrivals
US20040039617A1 (en) Travel interface and communication of travel related information via a computer system
US8296281B2 (en) System and method for notifications relating to flight tracking or planning
US20070143153A1 (en) Demand tracking system and method for a transportation carrier
EP2587221A2 (en) Systems, methods and devices for generating alternate itineraries
US20040039613A1 (en) Passenger status based on flight status information
US20060155591A1 (en) Systems, methods, and media for managing a travel itinerary
US7792634B2 (en) Flight information reminder system and method
US20130110833A1 (en) Method and system for identifying candidate users
US20120072249A1 (en) System and method for sending travel information to a wireless mobile device
EP1565858A2 (en) Advanced travel management system
US20150127408A1 (en) Static schedule reaccommodation
US20180032926A1 (en) Redistribution based on real time presence data
US20080004920A1 (en) Airline management system generating routings in real-time
US7603281B1 (en) Method, computer program, and system for pushing flight information to passengers
US20130218613A1 (en) Method and system for sending messages
US20160132977A1 (en) Systems and methods for sending messages to probable locations of persons
CN112668937A (en) Flight data monitoring method and related device
US11055636B2 (en) Composite travel disruption monitoring and mitigation
US20040039616A1 (en) System and method for use in connection with human travel
CN114297183A (en) Data processing method and device for additional service
US20180365599A1 (en) Updating an entire itinerary based on modifying a single travel reservation
US11232374B2 (en) Travel disruption management using fragmented source data

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination