Flight checking method, device and equipment and storage medium

Abstract

The invention discloses a flight checking method, device and equipment and a storage medium, and the method comprises the steps: combining incoming and outgoing flights which are carried by the same aircraft and have a mapping relation in a departure flight plan through a preset mapping rule, and generating a flight information group; the uniquely corresponding inbound flight can be determined for the departure flight to serve as a checking basis, and information checking errors caused by information matching disorder are avoided. And further, taking the to-be-checked information of the inbound flights in the flight information group as a checking basis, and judging whether the to-be-checked information of the outbound flights has errors or not, so as to obtain a checking result of the outbound flight plan. On the basis, the accuracy of the question checking result and the flight checking efficiency are improved.

Description

Technical Field

[0001] The present application relates to the technical field of flight management systems, and more specifically, to a flight verification method, device, equipment and storage medium. Background Art

[0002] A departure flight plan refers to the flight plan of multiple flights at an airport within a certain period of time. Each airport will formulate a departure flight plan based on its operational needs, route arrangements, flight schedules and other factors. It usually includes information such as the flight route, aircraft model, flight frequency and time.

[0003] Departure flight plan verification is the most critical step before a flight takes off. Through careful verification of the departure flight plan, we can ensure that all safety procedures have been properly implemented, and then obtain the passenger list from the reservation system. Passengers can check in online and select seats, etc., to reduce the possibility of unexpected flight situations. Since the departure time is short before departure, once the flight information is changed or the verification is wrong, it will have a great impact on airport planning and passenger travel. For example: aircraft model changes affect the flight crew, the scheduling of the executing aircraft, etc. Once a mistake occurs, it will have a great impact on the flight scheduling work on site.

[0004] At present, the method for checking the inbound and outbound flights in the departure flight plan relies on manual query and comparison of the inbound and outbound flights in the departure flight plan one by one. This checking method not only has low checking efficiency, but also has the possibility of human checking errors. Therefore, how to improve the efficiency and accuracy of checking the inbound and outbound flights in the departure flight plan needs to be solved urgently. Summary of the invention

[0005] In view of this, the present application provides a flight checking method, device, equipment and storage medium to achieve the purpose of improving the efficiency and accuracy of checking inbound and outbound flights in a departure flight plan.

[0006] The first aspect of the present application provides a flight verification method, comprising:

[0007] Obtaining a departure flight plan and a pre-set mapping rule, wherein the departure flight plan includes: flight information of an incoming flight and flight information of an outgoing flight, wherein the flight information includes at least: a flight identifier and information to be verified, and the mapping rule sets a mapping relationship between the inbound flight identifier and the outbound flight identifier carried by the same aircraft in the departure flight plan;

[0008] Based on the mapping rule and the departure flight plan, determining at least one flight information group, the flight information group including to-be-checked information of the inbound flight corresponding to the inbound flight identifier and to-be-checked information of the outbound flight corresponding to the outbound flight identifier, for which the mapping relationship exists;

[0009] For each of the flight information groups, using the to-be-checked information of the inbound flight as a basis for checking, checking whether the to-be-checked information of the outbound flight is consistent with the to-be-checked information of the inbound flight;

[0010] If the to-be-checked information of the outbound flight in each of the flight information groups is consistent with the to-be-checked information of the inbound flight, it is determined that the check result of the outbound flight plan is correct.

[0011] A second aspect of the present application provides a flight verification device, comprising:

[0012] an information acquisition unit, configured to acquire a departure flight plan and a pre-set mapping rule, wherein the departure flight plan includes: flight information of an incoming flight and flight information of an outgoing flight, wherein the flight information includes at least: a flight identifier and information to be verified, and the mapping rule sets a mapping relationship between an incoming flight identifier and an outgoing flight identifier carried by the same aircraft in the departure flight plan;

[0013] a flight mapping unit, configured to determine at least one flight information group based on the mapping rule and the departure flight plan, the flight information group including to-be-checked information of the inbound flight corresponding to the inbound flight identifier and to-be-checked information of the outbound flight corresponding to the outbound flight identifier, for which the mapping relationship exists;

[0014] An information checking unit, for each of the flight information groups, using the to-be-checked information of the inbound flight as a checking basis to check whether the to-be-checked information of the outbound flight is consistent with the to-be-checked information of the inbound flight;

[0015] The result confirmation unit is used to determine that the verification result of the departure flight plan is correct if the verification result of each flight information group obtained by the information verification unit is yes.

[0016] A third aspect of the present application provides a flight verification device, including a memory and a processor;

[0017] The memory is used to store programs;

[0018] The processor is used to execute the program to implement each step of any one of the flight verification methods.

[0019] A fourth aspect of the present application provides a storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, each step of any one of the flight verification methods is implemented.

[0020] With the help of the above technical scheme, the flight verification method provided by the present application can combine the inbound and outbound flights in the departure flight plan that are carried by the same aircraft and have a mapping relationship through pre-set mapping rules to generate a flight information group, which can determine the only corresponding inbound flight for the departure flight as the basis for verification, avoiding information matching confusion and causing information verification errors.

[0021] Furthermore, the information to be checked of the incoming flights in the flight information group is used as the basis for checking, and it is judged whether there is any error in the information to be checked of the outgoing flights, so as to obtain the checking result of the outgoing flight plan. Since the information to be checked of the incoming flights is used as the basis for checking, and the information to be checked of the incoming flights is the outgoing flight information that has been checked correctly in another outgoing flight plan, the accuracy of the checking result can be improved, and compared with the manual checking in the prior art, the efficiency of flight checking is also improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0023] Figure 1 A schematic diagram of a flow chart of a flight verification method provided in an embodiment of the present application;

[0024] Figure 2 An example diagram of a flight verification method provided in an embodiment of the present application;

[0025] Figure 3 A schematic diagram of the structure of a flight verification device provided in an embodiment of the present application;

[0026] Figure 4 A schematic diagram of the structure of a flight verification device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0028] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "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". The relevant definitions of other terms will be given in the following description.

[0029] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0030] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0031] The embodiment of the present application can use a server or a pre-set system to replace manual work to perform the verification of departure flight plans, thereby solving the problems of low verification efficiency and verification errors caused by manual verification.

[0032] Further, in order to improve the accuracy of the server or the preset system in checking the departure flight plan, the embodiment of the present application provides a flight checking method, which is applied to a device or platform such as a server or a preset system, see Figure 1 , a flowchart of a flight verification method provided by an embodiment of the present application, the specific process may include:

[0033] Step S110, obtaining the departure flight plan and pre-set mapping rules.

[0034] The departure flight plan includes: the flight information of the incoming flight and the flight information of the outgoing flight, wherein the flight information at least includes: the flight identification and the information to be verified. The information to be verified may include: the aircraft number, the flight segment, the date, the flight schedule, the office number, whether it is an international flight, the terminal, the time, the boarding gate, the layout, the aircraft type, etc. The flight identification is the identification information that can be used to identify each incoming and outgoing flight, such as the flight number, the aircraft number, etc.

[0035] It is understandable that the premise for the aircraft of the flight to leave the airport is that the aircraft of the flight entered and stayed at the airport at some time before. For example, flight A flies from airport A to airport B and stays at airport B. At this time, aircraft A corresponding to flight A can appear in the departure flight plan of airport B and depart from airport B as flight B. Therefore, when checking the departure flight plan, what is checked is whether there is a corresponding arrival flight for each outbound flight, whether the arrival flight and the outbound flight are operated by the same aircraft, and whether the flight information of the outbound flight corresponds to the flight information of the arrival flight, etc.

[0036] The mapping rules set the mapping relationship between the inbound flight ID and the outbound flight ID operated by the same aircraft in the outbound flight plan. The purpose of the mapping rules is to bind the outbound flights and inbound flights operated by the same aircraft in the outbound flight plan, so as to facilitate the subsequent verification of the flight information of the inbound and outbound flights with a binding relationship. It is understandable that the flight information of the outbound flights to be verified does not have accurate information, such as the aircraft number corresponding to each aircraft, the flight number of each flight, etc., which may be recorded incorrectly.

[0037] Therefore, the flight identifier used to represent the inbound and outbound flights in the mapping rules can be the information with the lowest error probability among each inbound and outbound flight that has a binding relationship. For example, in the departure flight plan, the flight number of each inbound and outbound flight is recorded correctly, so the flight identifier used to represent the inbound and outbound flights in the mapping rules can be the flight number, and the mapping rules set the mapping relationship between the flight number of the inbound flight and the flight number of the outbound flight carried by the same aircraft in the departure flight plan.

[0038] A feasible way to obtain mapping rules, the server can obtain the mapping rules set by the operation and maintenance personnel through a communication connection with the user end or an input window.

[0039] Step S120: determining at least one flight information group based on the mapping rule and the departure flight plan.

[0040] The flight information group includes pending verification information of inbound flights corresponding to the inbound flight identifiers and pending verification information of outbound flights corresponding to the outbound flight identifiers, which have a mapping relationship.

[0041] In one possible implementation, according to the mapping rules, the flight identification of each pair of inbound and outbound flights with a mapping relationship is matched with the flight identification of each inbound and outbound flight in the departure flight plan to obtain the to-be-checked information corresponding to each pair of inbound and outbound flights with a mapping relationship, and the to-be-checked information corresponding to each pair of inbound and outbound flights with a mapping relationship is combined to obtain multiple flight information groups.

[0042] Taking the verification of the departure flight plan below as an example, the process of obtaining the flight information group is described. The flight information of the inbound flights included in the departure flight plan is shown in Table 1, and the flight information of the outbound flights is shown in Table 2.

[0043] Table 1 Flight information of incoming flights

[0044]

[0045] Table 2 Flight information of outbound flights

[0046]

[0047] Among them, Table 1 and Table 2 respectively show the flight numbers of the incoming flights and the outgoing flights, as well as other information to be checked and other information. In the embodiment of the present application, the information to be checked may include: aircraft model / version, aircraft number, layout table number, etc.

[0048] The mapping rules set by the operation and maintenance personnel are obtained, wherein the mapping rules are set as follows: Rule 1: There is a mapping relationship between inbound flight CA1225 and outbound flight CA1224; Rule 2: There is a mapping relationship between inbound flight CA1229 and outbound flight CA1230.

[0049] According to the flight number CA1225 of the inbound flight in Rule 1, the flight numbers in the inbound flight information in the outbound flight plan are matched one by one, and the flight number CA1224 of the outbound flight in Rule 1 is matched one by one with the flight numbers in the outbound flight information in the outbound flight plan, to obtain the flight information of the inbound and outbound flights with the mapping relationship set in Rule 1, and determine the information to be checked corresponding to the inbound and outbound flights, to obtain flight information group 1 as shown in Table 3, based on which the flight information group 2 corresponding to Rule 2 is determined, which will not be repeated here.

[0050] Table 3 Flight information group

[0051]

[0052] Step S130, for each flight information group, using the pending verification information of the inbound flight as a verification basis, to check whether the pending verification information of the outbound flight is consistent with the pending verification information of the inbound flight.

[0053] In the case where the departure flight plan of each airport is checked according to the flight information verification method provided in the embodiment of the present application, flight CA1225 is a departure flight relative to airport PEK in the flight segment PEK-SHA, and flight CA1225 can fly normally from airport PEK to airport SHA, which proves that the verification result of the flight information of flight CA1225 in the departure flight plan of airport PEK is correct. Therefore, when checking flight information group 1 in the departure flight plan of airport SHA, the information to be verified of flight CA1225 can be used as the correct information, and the information to be verified of flight CA1224 can be checked to determine whether there is incorrect information. Based on this, when checking flight information group 2, the information to be verified of inbound flight CA1229 is used as the basis for verification to determine whether the information to be verified of outbound flight CA1230 is wrong.

[0054] Therefore, when checking the information of each flight information group corresponding to the departure flight plan, the pending information of the arrival flight is used as the basis for checking to see whether the pending information of the departure flight is consistent with the pending information of the arrival flight, so as to determine the information verification result of each flight information group.

[0055] Step S140: If the to-be-checked information of the outbound flight in each flight information group is consistent with the to-be-checked information of the inbound flight, it is determined that the check result of the outbound flight plan is correct.

[0056] As in the flight information group 1 in the above example, the layout table number, aircraft model / version, and aircraft number of the outbound flight CA1224 are respectively the same as the layout table number, aircraft model / version, and aircraft number of the inbound flight CA1225, so the verification result of the flight information group 1 is that the information is consistent.

[0057] In flight information group 2, the layout table number, aircraft model / version, and aircraft number of outbound flight CA1230 are different from those of inbound flight CA1229. The verification result of flight information group 2 is that the information is incorrect.

[0058] If the information verification results of each flight information group are consistent, it can be determined that the flight information of each outbound flight with a mapping relationship is correct and can depart normally, and the verification result of the current departure flight plan is confirmed to be correct, and the departure flight plan can be implemented normally.

[0059] If the verification result of any flight information group among many flight information groups is that the information is incorrect, it proves that the current departure flight plan cannot be implemented normally, and the erroneous information in the departure flight plan needs to be corrected to avoid affecting the normal flight of the flight.

[0060] In a possible implementation, if the pending verification information of the outbound flight and the pending verification information of the inbound flight in any flight information group are inconsistent, the pending verification information of the outbound flight is corrected according to the pending verification information of the inbound flight so that the pending verification information of the outbound flight is consistent with the pending verification information of the inbound flight.

[0061] As can be seen from the above description, in the flight information group, the pending verification information of the incoming flight is consistent with the pending verification information of the outgoing flight, so as to ensure that the aircraft corresponding to the incoming flight is the same aircraft as the aircraft corresponding to the outgoing flight, and to ensure that the navigation information of each aircraft is correct and the navigation of each aircraft can be traced. Therefore, for the flight information group with inconsistent information, the information in the pending verification information of the outgoing flight that is inconsistent with the pending verification information of the incoming flight is corrected to make it consistent with the pending verification information of the incoming flight.

[0062] For example, in the example above, the layout table number, model / version, and aircraft number of flight information group 2 of outbound flight CA1230 are inconsistent with those of inbound flight CA1229. When revising the outbound flight plan, the layout table number of outbound flight CA1230 is revised from 112 to 110 to make it consistent with the layout table number of inbound flight CA1229. Similarly, the model / version and aircraft number of outbound flight CA1230 are revised to 737 / 123G and B1231 respectively.

[0063] It is understandable that the information in the flight information group is corrected, that is, the information in the departure flight plan is corrected. After verification, it is confirmed that there is inconsistent information in the departure flight plan. According to the above example, the erroneous information is corrected to obtain the correct departure flight plan.

[0064] To summarize, the embodiments of the present application can combine the inbound and outbound flights in the departure flight plan that are operated by the same aircraft and have a mapping relationship through pre-set mapping rules to generate a flight information group, which can determine the only corresponding inbound flight for the departure flight as a basis for verification, thereby avoiding information matching confusion and causing information verification errors.

[0065] Furthermore, the information to be checked of the incoming flights in the flight information group is used as the basis for checking, and it is judged whether there is any error in the information to be checked of the outgoing flights, so as to obtain the checking result of the outgoing flight plan. Since the information to be checked of the incoming flights is used as the basis for checking, and the information to be checked of the incoming flights is the outgoing flight information that has been checked correctly in another outgoing flight plan, the accuracy of the checking result can be improved, and compared with the manual checking in the prior art, the efficiency of flight checking is also improved.

[0066] Furthermore, other possible implementations in the embodiments of the present application are described.

[0067] In a possible implementation, in a departure flight plan, if there are inbound flights for which no flight information group is generated and outbound flights for which no flight information group is generated, the flight information corresponding to the inbound flights for which no flight information group is generated and the outbound flights for which no flight information group is generated are sent to the front end; in response to the front end's modification of the mapping rule, a modified flight information group is generated based on the modified mapping rule and the flight information corresponding to the inbound flights for which no flight information group is generated and the outbound flights for which no flight information group is generated, the modified mapping rule sets a mapping relationship between the inbound flight identifier for which no flight information group is generated and the outbound flight identifier for which no flight information group is generated; and for the modified flight information group, step S130 and subsequent steps are executed.

[0068] As shown in the above example, the inbound flight 3U1500 and the outbound flight 3U1510 in the departure flight plan do not generate corresponding flight information groups. For the outbound flight 3U1510, there may be no corresponding aircraft in the airport SHA to perform this flight, and the outbound flight 3U1510 needs to be removed from the departure flight plan; or the operation and maintenance personnel omitted the outbound flight 3U1510 when setting or entering the mapping rules.

[0069] No matter which of the above situations is the case, it will affect the airport's arrangement of subsequent flight plans. Therefore, the above situations, as well as the outbound flights and inbound flights that failed to generate flight information groups, can be fed back to the front end to remind the front-end operation and maintenance personnel so that they can provide corresponding solutions.

[0070] If the operation and maintenance personnel miss out the outbound flight 3U1510 and the inbound flight 3U1500 when setting or inputting the mapping rules, the operation and maintenance personnel can reset the mapping rules corresponding to the outbound flight 3U1510 and the inbound flight 3U1500 through the front end to obtain the revised mapping rules. The revised mapping rules set that in the departure flight plan, there is a mapping relationship between the outbound flight 3U1510 and the inbound flight 3U1500, and they are carried by the same aircraft, or other verification conditions can be added to the mapping conditions, such as allowing the layout table numbers of the two flights to be inconsistent, the boarding gate of the outbound flight to be D2, whether the date offset of the two flights is empty, etc. In the subsequent verification, not only the verification mode of the inbound flight and the outbound flight to be verified in the flight information group mentioned above can be maintained consistent, and the mapping rules described in the above steps S110-S140 can also be used when setting, and the additional conditions can be adjusted, which will not be repeated here.

[0071] After receiving the revised mapping rule, the server for checking the departure flight plan combines the to-be-checked information corresponding to the departure flight 3U1510 and the arrival flight 3U1500 according to the revised mapping rule to generate the corresponding flight information group 3, as shown in Table 4. Based on Table 4, the layout table number and aircraft model / version to-be-checked information of the departure flight 3U1510 are revised.

[0072] Table 4 Flight information group 3

[0073] In one possible implementation, if the front-end operation and maintenance personnel confirm that outbound flight 3U1510 is a redundant flight and there is no departure plan for this flight, the operation and maintenance personnel can send an operation to remove outbound flight 3U1510 to the server through the front-end, and the server can respond to the removal operation and remove outbound flight 3U1510 from the departure flight plan to obtain the latest departure flight plan.

[0074] It is understandable that there may be aircraft stranded at the airport and not leaving. Therefore, in the departure flight plan, if there are only inbound flights for which corresponding flight information groups cannot be generated, the mapping rules do not need to be reset.

[0075] In a possible implementation, for each flight information group, the flight information of the incoming flight and the flight information of the outgoing flight are compared; based on the comparison result, the information comparison result corresponding to each flight information group is generated; and the information comparison result corresponding to each flight information group is sent to the front end.

[0076] Referring to Tables 2, 3, and 4 listed above, the information comparison results of the inbound and outbound flights in the flight information group are more intuitive than the verification results of "information is consistent" and "information is incorrect". Therefore, in an embodiment of the present application, the flight information comparison results in the form of tables, reports, messages, charts, etc. can also be sent to the front end, and the comparison results are sent to the front end to improve the intuitiveness of the departure flight plan verification results.

[0077] See also Figure 2 , an example diagram of implementing the flight verification method provided in the embodiment of the present application, illustrates the practical application of the above-mentioned flight verification method. This example applies the flight verification method to a verification and validation system, wherein the verification and validation system includes: a rule mapping module, a comparison execution module, an execution result display module, a fast calibration module and a rule correction feedback module. The departure flight plan is verified based on the verification and validation system, and the obtained verification result is sent to the departure open system, so that the departure open system can arrange the flight of the flight according to the verified departure flight plan.

[0078] The following is an explanation of how each module in the verification system implements the above steps to realize the process of verifying the departure flight plan.

[0079] The rule mapping relationship module is used to respond to user operations and set flight arrival and departure mapping rules, such as: the carrier aircraft used by the outbound flight needs to correspond one-to-one with the carrier aircraft used by the inbound flight.

[0080] The comparison execution module is used to respond to the user clicking the comparison execution button and start the comparison of inbound and outbound flight models. The comparison content may include flight number, flight segment, date, flight schedule, office number, whether it is an international flight, terminal, time, boarding gate, layout, aircraft model, and aircraft number.

[0081] The execution result display module is used to display the results of the comparison of the inbound and outbound flight models of the comparison execution module, among which the flights with inconsistent inbound and outbound aircraft models are highlighted.

[0082] Quick calibration module: used to send the flight information with inconsistent inbound and outbound aircraft models in the comparison results to the user end for review. It also provides a quick query entry for users to quickly query the inbound and outbound flight plan information, and determine whether the inconsistent information needs to be corrected based on the query results. For those that need to be corrected, in response to the user clicking the correction button, the outbound flight model is changed to be consistent with the inbound model.

[0083] The rule correction feedback module is used to display flights that do not match the mapping relationship. According to user needs, the mapping relationship can be directly generated for subsequent comparison.

[0084] This example can automatically compare the aircraft numbers and models for all inbound and outbound flights at the terminal. It also supports users to set inbound and outbound mapping rules. It is not limited to a single inbound and outbound verification mode that is completely consistent. It can flexibly match and adapt to various corresponding relationships. For inconsistent comparison results, it provides a quick processing method, which improves work efficiency and ensures the accuracy of flight plans.

[0085] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0086] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0087] Although operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in a sequential order.Multitasking and parallel processing may be advantageous under certain circumstances.

[0088] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0089] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving 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 may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0090] The flight verification device provided in an embodiment of the present application is described below. The flight verification device described below and the flight verification method described above can be referenced to each other.

[0091] First, combine Figure 3 , introduces the flight checking device applied to the server or application system, such as Figure 3 As shown, the flight checking device may include:

[0092] The information acquisition unit 100 is used to acquire a departure flight plan and a pre-set mapping rule, wherein the departure flight plan includes: flight information of an incoming flight and flight information of an outgoing flight, wherein the flight information includes at least: a flight identifier and information to be verified, and the mapping rule sets a mapping relationship between an incoming flight identifier and an outgoing flight identifier carried by the same aircraft in the departure flight plan;

[0093] A flight mapping unit 200, configured to determine at least one flight information group based on the mapping rule and the departure flight plan, wherein the flight information group includes to-be-checked information of the inbound flight corresponding to the inbound flight identifier and to-be-checked information of the outbound flight corresponding to the outbound flight identifier, for which the mapping relationship exists;

[0094] The information checking unit 300 is used to check, for each of the flight information groups, whether the information to be checked of the outbound flight is consistent with the information to be checked of the inbound flight, based on the information to be checked of the inbound flight;

[0095] The result confirmation unit 400 is used to determine that the verification result of the departure flight plan is verified to be correct if the verification result of each flight information group obtained by the information verification unit is yes.

[0096] To summarize, the embodiments of the present application can combine the inbound and outbound flights in the departure flight plan that are operated by the same aircraft and have a mapping relationship through pre-set mapping rules to generate a flight information group, which can determine the only corresponding inbound flight for the departure flight as a basis for verification, thereby avoiding information matching confusion and causing information verification errors.

[0097] Furthermore, the information to be checked of the incoming flights in the flight information group is used as the basis for checking, and it is judged whether there is any error in the information to be checked of the outgoing flights, so as to obtain the checking result of the outgoing flight plan. Since the information to be checked of the incoming flights is used as the basis for checking, and the information to be checked of the incoming flights is the outgoing flight information that has been checked correctly in another outgoing flight plan, the accuracy of the checking result can be improved, and compared with the manual checking in the prior art, the efficiency of flight checking is also improved.

[0098] In a possible implementation, the flight verification device may further include:

[0099] The information correction unit is used to correct the information to be checked of the outbound flight according to the information to be checked of the inbound flight when the checking result of the information checking unit is negative, so that the information to be checked of the outbound flight is consistent with the information to be checked of the inbound flight.

[0100] In a possible implementation, the flight verification device may further include:

[0101] a flight sending unit, configured to send flight information corresponding to the inbound flight for which the flight information group is not generated and the outbound flight for which the flight information group is not generated to the front end, respectively, if there are the inbound flights for which the flight information group is not generated and the outbound flights for which the flight information group is not generated in the outbound flight plan;

[0102] a demand response unit, configured to generate a revised flight information group in response to the front end modifying the mapping rule, based on the modified mapping rule and the flight information corresponding to the inbound flight for which the flight information group is not generated and the outbound flight for which the flight information group is not generated, wherein the modified mapping rule sets a mapping relationship between the inbound flight identifier for which the flight information group is not generated and the outbound flight identifier for which the flight information group is not generated;

[0103] The checking unit is used to jump to the information checking unit for the revised flight information group, and execute the step of checking, for each flight information group, whether the information to be checked of the outbound flight is consistent with the information to be checked of the inbound flight using the information to be checked of the inbound flight as a checking basis.

[0104] In a possible implementation, the flight verification device may further include:

[0105] a flight information checking unit, for comparing the flight information of the incoming flight with the flight information of the outgoing flight for each of the flight information groups;

[0106] A result generating unit, configured to generate, based on the comparison result, an information comparison result corresponding to each of the flight information groups;

[0107] The result sending unit is used to send the information comparison result corresponding to each flight information group to the front end.

[0108] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware. The name of a unit does not limit the unit itself in some cases. For example, the first acquisition unit may also be described as a "unit for acquiring at least two Internet Protocol addresses".

[0109] The functions described above herein 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 chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0110] The flight verification device provided in the embodiment of the present application can be applied to flight verification equipment.

[0111] Figure 4 The schematic diagram of the flight verification equipment is shown. Figure 4 , the structure of the flight verification device may include: at least one processor 10, at least one memory 20, at least one communication bus 30 and at least one communication interface 40;

[0112] In the embodiment of the present application, the number of the processor 10, the memory 20, the communication bus 30, and the communication interface 40 is at least one, and the processor 10, the memory 20, and the communication interface 40 communicate with each other through the communication bus 30;

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

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

[0115] The memory stores a program, and the processor can call the program stored in the memory, and the program is used to implement each processing flow in the aforementioned flight verification plan.

[0116] An embodiment of the present application further provides a storage medium, which can store a program suitable for execution by a processor, wherein the program is used to implement each processing flow in the aforementioned flight verification solution.

[0117] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0118] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. Computer readable signal media may also be any computer readable medium other than computer readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0119] The computer-readable medium may be included in the electronic device, or may exist independently without being installed in the electronic device.

[0120] According to one or more embodiments of the present disclosure, Example 1 provides a flight verification method, including:

[0121] Obtaining a departure flight plan and a pre-set mapping rule, wherein the departure flight plan includes: flight information of an incoming flight and flight information of an outgoing flight, wherein the flight information includes at least: a flight identifier and information to be verified, and the mapping rule sets a mapping relationship between the inbound flight identifier and the outbound flight identifier carried by the same aircraft in the departure flight plan;

[0122] Based on the mapping rule and the departure flight plan, determining at least one flight information group, the flight information group including to-be-checked information of the inbound flight corresponding to the inbound flight identifier and to-be-checked information of the outbound flight corresponding to the outbound flight identifier, for which the mapping relationship exists;

[0123] For each of the flight information groups, using the to-be-checked information of the inbound flight as a basis for checking, checking whether the to-be-checked information of the outbound flight is consistent with the to-be-checked information of the inbound flight;

[0124] If the to-be-checked information of the outbound flight in each of the flight information groups is consistent with the to-be-checked information of the inbound flight, it is determined that the check result of the outbound flight plan is correct.

[0125] According to one or more embodiments of the present disclosure, Example 2 provides the flight verification method of Example 1, further including: if in any of the flight information groups, the to-be-verified information of the outbound flight is inconsistent with the to-be-verified information of the inbound flight, the to-be-verified information of the outbound flight is corrected based on the to-be-verified information of the inbound flight so that the to-be-verified information of the outbound flight is consistent with the to-be-verified information of the inbound flight.

[0126] According to one or more embodiments of the present disclosure, Example 3 provides the flight checking method of Example 1, further comprising:

[0127] In the departure flight plan, if there are the inbound flights for which the flight information group has not been generated and the outbound flights for which the flight information group has not been generated, sending the flight information corresponding to the inbound flights for which the flight information group has not been generated and the outbound flights for which the flight information group has not been generated to the front end;

[0128] In response to the front end modifying the mapping rule, a modified flight information group is generated based on the modified mapping rule and the flight information corresponding to the inbound flight for which the flight information group is not generated and the outbound flight for which the flight information group is not generated, wherein the modified mapping rule sets a mapping relationship between the inbound flight identifier for which the flight information group is not generated and the outbound flight identifier for which the flight information group is not generated;

[0129] For the revised flight information group, the step of performing, for each flight information group, using the to-be-checked information of the inbound flight as a checking basis, checking whether the to-be-checked information of the outbound flight is consistent with the to-be-checked information of the inbound flight.

[0130] According to one or more embodiments of the present disclosure, Example 4 provides the flight checking method of Example 1, further comprising:

[0131] For each of the flight information groups, comparing the flight information of the incoming flight with the flight information of the outgoing flight;

[0132] Based on the comparison result, generating information comparison results corresponding to each flight information group;

[0133] The information comparison result corresponding to each flight information group is sent to the front end.

[0134] According to one or more embodiments of the present disclosure, Example 5 provides a flight verification device, including:

[0135] an information acquisition unit, configured to acquire a departure flight plan and a pre-set mapping rule, wherein the departure flight plan includes: flight information of an incoming flight and flight information of an outgoing flight, wherein the flight information includes at least: a flight identifier and information to be verified, and the mapping rule sets a mapping relationship between an incoming flight identifier and an outgoing flight identifier carried by the same aircraft in the departure flight plan;

[0136] a flight mapping unit, configured to determine at least one flight information group based on the mapping rule and the departure flight plan, the flight information group including to-be-checked information of the inbound flight corresponding to the inbound flight identifier and to-be-checked information of the outbound flight corresponding to the outbound flight identifier, for which the mapping relationship exists;

[0137] An information checking unit, for each of the flight information groups, using the to-be-checked information of the inbound flight as a checking basis to check whether the to-be-checked information of the outbound flight is consistent with the to-be-checked information of the inbound flight;

[0138] The result confirmation unit is used to determine that the verification result of the departure flight plan is correct if the verification result of each flight information group obtained by the information verification unit is yes.

[0139] According to one or more embodiments of the present disclosure, Example 6 provides the flight verification device of Example 5, further comprising:

[0140] The information correction unit is used to correct the information to be checked of the outbound flight according to the information to be checked of the inbound flight when the checking result of the information checking unit is negative, so that the information to be checked of the outbound flight is consistent with the information to be checked of the inbound flight.

[0141] According to one or more embodiments of the present disclosure, Example 7 provides the flight verification device of Example 5, further comprising:

[0142] a flight sending unit, configured to send flight information corresponding to the inbound flight for which the flight information group is not generated and the outbound flight for which the flight information group is not generated to the front end, respectively, if there are the inbound flights for which the flight information group is not generated and the outbound flights for which the flight information group is not generated in the outbound flight plan;

[0143] a demand response unit, configured to generate a revised flight information group in response to the front end modifying the mapping rule, based on the modified mapping rule and the flight information corresponding to the inbound flight for which the flight information group is not generated and the outbound flight for which the flight information group is not generated, wherein the modified mapping rule sets a mapping relationship between the inbound flight identifier for which the flight information group is not generated and the outbound flight identifier for which the flight information group is not generated;

[0144] The checking unit is used to jump to the information checking unit for the revised flight information group, and execute the step of checking, for each flight information group, whether the information to be checked of the outbound flight is consistent with the information to be checked of the inbound flight using the information to be checked of the inbound flight as a checking basis.

[0145] According to one or more embodiments of the present disclosure, Example 8 provides the flight verification device of Example 5, further comprising:

[0146] a flight information checking unit, for comparing the flight information of the incoming flight with the flight information of the outgoing flight for each of the flight information groups;

[0147] A result generating unit, configured to generate, based on the comparison result, an information comparison result corresponding to each of the flight information groups;

[0148] The result sending unit is used to send the information comparison result corresponding to each flight information group to the front end.

[0149] According to one or more embodiments of the present disclosure, Example 9 provides a flight checking device, including:

[0150] The memory is used to store programs;

[0151] The processor is used to execute the program to implement each step of the flight verification method described in any one of Examples 1 to 4.

[0152] According to one or more embodiments of the present disclosure, Example 10 provides a storage medium, including: a computer program stored thereon, and when the computer program is executed by a processor, the various steps of the flight verification method described in any one of Examples 1 to 4 are implemented.

[0153] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.

[0154] Although several specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Certain features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0155] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.

Claims

1. A flight verification method, characterized in that: include: Obtaining a departure flight plan and a pre-set mapping rule, wherein the departure flight plan includes: flight information of an incoming flight and flight information of an outgoing flight, wherein the flight information includes at least: a flight identifier and information to be verified, and the mapping rule sets a mapping relationship between the inbound flight identifier and the outbound flight identifier carried by the same aircraft in the departure flight plan; Based on the mapping rule and the departure flight plan, determining at least one flight information group, the flight information group including to-be-checked information of the inbound flight corresponding to the inbound flight identifier and to-be-checked information of the outbound flight corresponding to the outbound flight identifier, for which the mapping relationship exists; For each of the flight information groups, using the to-be-checked information of the inbound flight as a basis for checking, checking whether the to-be-checked information of the outbound flight is consistent with the to-be-checked information of the inbound flight; If the to-be-checked information of the outbound flight in each of the flight information groups is consistent with the to-be-checked information of the inbound flight, it is determined that the check result of the outbound flight plan is correct.

2. The flight verification method according to claim 1, characterized in that: Also includes: If the to-be-checked information of the outbound flight in any of the flight information groups is inconsistent with the to-be-checked information of the inbound flight, the to-be-checked information of the outbound flight is corrected according to the to-be-checked information of the inbound flight so that the to-be-checked information of the outbound flight is consistent with the to-be-checked information of the inbound flight.

3. The flight verification method according to claim 1, characterized in that: Also includes: In the departure flight plan, if there are the inbound flights for which the flight information group has not been generated and the outbound flights for which the flight information group has not been generated, sending the flight information corresponding to the inbound flights for which the flight information group has not been generated and the outbound flights for which the flight information group has not been generated to the front end; In response to the front end modifying the mapping rule, a modified flight information group is generated based on the modified mapping rule and the flight information corresponding to the inbound flight for which the flight information group is not generated and the outbound flight for which the flight information group is not generated, wherein the modified mapping rule sets a mapping relationship between the inbound flight identifier for which the flight information group is not generated and the outbound flight identifier for which the flight information group is not generated; For the revised flight information group, the step of performing, for each flight information group, using the to-be-checked information of the inbound flight as a checking basis, checking whether the to-be-checked information of the outbound flight is consistent with the to-be-checked information of the inbound flight.

4. The flight verification method according to claim 1, characterized in that: Also includes: For each of the flight information groups, comparing the flight information of the incoming flight with the flight information of the outgoing flight; Based on the comparison result, generating information comparison results corresponding to each flight information group; The information comparison result corresponding to each flight information group is sent to the front end.

5. A flight verification device, characterized in that: include: an information acquisition unit, configured to acquire a departure flight plan and a pre-set mapping rule, wherein the departure flight plan includes: flight information of an incoming flight and flight information of an outgoing flight, wherein the flight information includes at least: a flight identifier and information to be verified, and the mapping rule sets a mapping relationship between an incoming flight identifier and an outgoing flight identifier carried by the same aircraft in the departure flight plan; a flight mapping unit, configured to determine at least one flight information group based on the mapping rule and the departure flight plan, the flight information group including to-be-checked information of the inbound flight corresponding to the inbound flight identifier and to-be-checked information of the outbound flight corresponding to the outbound flight identifier, for which the mapping relationship exists; An information checking unit, for each of the flight information groups, using the to-be-checked information of the inbound flight as a checking basis to check whether the to-be-checked information of the outbound flight is consistent with the to-be-checked information of the inbound flight; The result confirmation unit is used to determine that the verification result of the departure flight plan is correct if the verification result of each flight information group obtained by the information verification unit is yes.

6. The flight verification device according to claim 5, characterized in that: Also includes: The information correction unit is used to correct the information to be checked of the outbound flight according to the information to be checked of the inbound flight when the checking result of the information checking unit is negative, so that the information to be checked of the outbound flight is consistent with the information to be checked of the inbound flight.

7. The flight verification device according to claim 5, characterized in that: Also includes: a flight sending unit, configured to send flight information corresponding to the inbound flight for which the flight information group is not generated and the outbound flight for which the flight information group is not generated to the front end, respectively, if there are the inbound flights for which the flight information group is not generated and the outbound flights for which the flight information group is not generated in the outbound flight plan; a demand response unit, configured to generate a revised flight information group in response to the front end modifying the mapping rule, based on the modified mapping rule and the flight information corresponding to the inbound flight for which the flight information group is not generated and the outbound flight for which the flight information group is not generated, wherein the modified mapping rule sets a mapping relationship between the inbound flight identifier for which the flight information group is not generated and the outbound flight identifier for which the flight information group is not generated; The checking unit is used to jump to the information checking unit for the revised flight information group, and execute the step of checking, for each flight information group, whether the information to be checked of the outbound flight is consistent with the information to be checked of the inbound flight using the information to be checked of the inbound flight as a checking basis.

8. The flight verification device according to claim 5, characterized in that: Also includes: a flight information checking unit, for comparing the flight information of the incoming flight with the flight information of the outgoing flight for each of the flight information groups; A result generating unit, configured to generate, based on the comparison result, an information comparison result corresponding to each of the flight information groups; The result sending unit is used to send the information comparison result corresponding to each flight information group to the front end.

9. A flight checking device, characterized in that: including memory and processor; The memory is used to store programs; The processor is used to execute the program to implement each step of the flight verification method according to any one of claims 1 to 4.

10. A storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a processor, each step of the flight verification method described in any one of claims 1 to 4 is implemented.

Images