Aircraft execution rate determination method and device, medium and electronic equipment
The method corrects actual flight data to match planned data using specific rules, addressing inaccuracies in aircraft execution rate calculations and ensuring accurate statistics for air traffic control.
Patent Information
- Application Number
- CN202411091427.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-09
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2044-08-09
AI Technical Summary
The inaccuracy in calculating aircraft execution rates due to deviations between actual and planned flight data, especially for international flights and flights affected by weather or other force majeure, leads to inaccurate statistics for air traffic control bureaus.
A method and device for determining aircraft execution rates by correcting actual flight data to match planned flight data using specific correction rules, including date and type adjustments, to ensure accurate counting of flight data within a target time window.
Ensures accurate calculation of aircraft execution rates by aligning actual flight data with planned data, providing reliable statistics for air traffic control bureaus and aiding in operational efficiency assessments.
Smart Images

Figure CN119091693A_ABST
Abstract
Description
Background Art
[0002] With the rapid development of the global aviation industry and the continuous growth of air transport demand, airlines are facing increasingly complex operational challenges. The execution rate of each airline in each season or month is directly related to the airline's operational efficiency, economic benefits and customer satisfaction. When the aircraft is actually performing its flight mission, due to weather reasons or other force majeure, it may cause aircraft delays, make-up flights, adjustments, etc., so that there may be differences between the actual flight data corresponding to each planned flight data and the planned flight data. This makes the Air Traffic Control Bureau inaccurate when calculating the execution rate of each airline in each season or month due to the deviation between the actual flight data and the planned flight data. Summary of the invention
[0003] In response to the above technical problems, the present application provides a method, device, medium and electronic equipment for determining an aircraft execution rate, which at least partially solve the problems existing in the prior art.
[0004] In a first aspect of the present application, a method for determining an aircraft execution rate is provided, the method comprising the following steps:
[0005] S100, obtaining the actual flight data corresponding to the target subject within the target time window to obtain an actual flight data list SF = (SF 1 , S.F. 2 ,…,SF i ,…,SF n ), i = 1, 2, ..., n, where n is the number of actual flight data corresponding to the target subject within the target time window; SF i is the ith actual flight data of the target subject within the target time window; SF i =(SFQ i , S.F.L. i , SFH i , SFZ i );SFQ i is the actual take-off airport corresponding to the ith actual flight data; SFL i is the actual landing airport corresponding to the ith actual flight data; SFH i is the actual flight number corresponding to the ith actual flight data; SFZ i is the actual execution date corresponding to the ith actual flight data; each actual flight data has a corresponding actual flight type;
[0006] S200, if SF i If the flight data to be revised on the date and / or the flight data to be revised on the type, SFZ i Correct to the planned execution date in the corresponding planned flight data and / or change the SFi The corresponding actual flight type is corrected to the planned flight type in the corresponding planned flight data, otherwise it is not corrected to obtain the updated SF; among which, the flight data to be corrected on the date is SFQ i For non-domestic airports, SFL i It is a domestic airport and SFZ i Actual flight data with a different planned execution date from the corresponding planned flight data; flight data to be corrected includes both domestic and non-domestic segments, and actual flight data with a different actual flight type from the corresponding planned flight data;
[0007] S300, matching each flight data in the updated SF with the corresponding planned flight data to obtain a target correction list MX=(MX 1 , MX 2 , …, MX j , …, MX m ); j = 1, 2, ..., m; m is the number of flight data in the updated SF that are not identical to the corresponding planned flight data; MX j is the jth flight data in the updated SF that is not completely identical to the corresponding planned flight data;
[0008] S400, correcting MX according to the planned flight data and a preset correction rule to obtain a number of target flight data; wherein the target flight data includes the corrected actual flight data and the uncorrected actual flight data; the target flight data is the flight data corresponding to the corresponding departure airport, landing airport, flight number and execution date and the planned departure airport, planned landing airport, planned flight number and planned execution date in the corresponding planned flight data;
[0009] S500, based on the target flight data and the planned flight data corresponding to the target subject within the target time window, obtain the execution rate ZX corresponding to the target subject within the target time window, and ZX meets the following conditions: ZX = MF / JF; wherein MF is the number of target flight data; JF is the number of planned flight data corresponding to the target subject within the target time window.
[0010] In a second aspect of the present application, a device for determining an aircraft execution rate is provided, the device comprising:
[0011] The actual data acquisition unit is used to acquire the actual flight data corresponding to the target subject within the target time window to obtain the actual flight data list SF = (SF 1 , S.F. 2 ,…,SF i ,…,SF n), i = 1, 2, ..., n, where n is the number of actual flight data corresponding to the target subject within the target time window; SF i is the ith actual flight data of the target subject within the target time window; SF i =(SFQ i , S.F.L. i , SFH i , SFZ i );SFQ i is the actual take-off airport corresponding to the ith actual flight data; SFL i is the actual landing airport corresponding to the ith actual flight data; SFH i is the actual flight number corresponding to the ith actual flight data; SFZ i is the actual execution date corresponding to the ith actual flight data; each actual flight data has a corresponding actual flight type;
[0012] The first correction unit is used if SF i If the flight data to be revised on the date and / or the flight data to be revised on the type, SFZ i Correct to the planned execution date in the corresponding planned flight data and / or change the SF i The corresponding actual flight type is corrected to the planned flight type in the corresponding planned flight data, otherwise it is not corrected to obtain the updated SF; among which, the flight data to be corrected on the date is SFQ i For non-domestic airports, SFL i It is a domestic airport and SFZ i Actual flight data with a different planned execution date from the corresponding planned flight data; flight data to be corrected includes both domestic and non-domestic segments, and actual flight data with a different actual flight type from the corresponding planned flight data;
[0013] A matching unit is used to match each flight data in the updated SF with the corresponding planned flight data to obtain a target correction list MX = (MX 1 , MX 2 , …, MX j , …, MX m ); j = 1, 2, ..., m; m is the number of flight data in the updated SF that are not identical to the corresponding planned flight data; MX j is the jth flight data in the updated SF that is not completely identical to the corresponding planned flight data;
[0014] A second correction unit is used to correct the MX according to the planned flight data and a preset correction rule to obtain a number of target flight data; wherein the target flight data includes the corrected actual flight data and the uncorrected actual flight data; the target flight data is the flight data corresponding to the corresponding take-off airport, landing airport, flight number and execution date and the planned take-off airport, planned landing airport, planned flight number and planned execution date in the corresponding planned flight data;
[0015] The determination unit is used to obtain the execution rate ZX corresponding to the target subject in the target time window according to the target flight data and the planned flight data corresponding to the target subject in the target time window, and ZX meets the following conditions: ZX=MF / JF; wherein MF is the number of target flight data; JF is the number of planned flight data corresponding to the target subject in the target time window.
[0016] In a third aspect of the present application, a non-transitory computer-readable storage medium is provided, in which at least one instruction or at least one program is stored, and the at least one instruction or at least one program is loaded and executed by a processor to implement the aforementioned aircraft execution rate determination method.
[0017] In a fourth aspect of the present application, an electronic device is provided, comprising a processor and the above-mentioned non-transitory computer-readable storage medium.
[0018] This application has at least the following beneficial effects:
[0019] The method for determining the aircraft execution rate provided in the present application traverses each actual flight data. For international inbound flights that take off from a non-domestic airport and land at a domestic airport, since they do not have the jurisdiction of an international airport, when flying in a non-domestic area, or if there is a delay due to weather conditions during takeoff, etc., accurate information cannot be obtained. Therefore, the execution date in the flight data corresponding to such flights is the landing date (the date of landing at the domestic airport), and here, the corresponding planned flight data is determined based on its departure airport, landing airport and flight number. According to the corresponding planned flight data, if its corresponding actual execution date (the date of landing at the domestic airport) is inconsistent with the planned flight data, it is corrected to the execution date corresponding to the planned flight data. In this way, the international inbound flights for which accurate information cannot be obtained are corrected to be consistent with the data in the corresponding planned flight data, so that the air traffic control bureau can obtain the data when counting the execution rate of a certain time window. On the other hand, in some off-seasons or other special circumstances, a flight without a ticket may be changed to a cargo flight. When the actual flight number, actual departure airport, actual landing airport and actual execution date are the same as the corresponding planned flight data, and when the air traffic control bureau approves it, it is a passenger flight, but when it is actually running, it is a cargo flight. In this case, its flight type will be changed to passenger so that the air traffic control bureau can obtain the data when counting the execution rate of a certain time window. After the above two steps, each flight data in the updated SF is matched with the corresponding planned flight data. If the flight is operated completely according to the planned flight data, the actual flight data obtained is the same as the corresponding planned flight data. However, due to weather or other force majeure, the actual flight data may not be completely the same as the corresponding planned flight data.
[0020] Then, according to the corresponding planned flight data, the preset correction rules are used to correct MX, so that the actual flight data that may not be completely the same as the corresponding planned flight data due to weather or other force majeure reasons will be the same as the corresponding planned flight data after correction. So that the aforementioned target flight data can be accurately obtained when calculating the execution rate. The target flight data includes the corrected actual flight data and the uncorrected actual flight data. Because there are some uncorrected actual flight data (which may be corrected by date and type) that are the same as the corresponding planned flight data, they are directly determined as target flight data, and there are also some flight data that are corrected by the preset correction rules that are the same as the corresponding planned flight data, which are determined as target flight data. In this way, the corresponding execution rate of the target subject within the target time window is obtained. The execution rate data is modified in a targeted manner according to the different corresponding situations of each actual flight data, so that the flight data that is not completely consistent with the corresponding planned flight data due to weather reasons or other force majeure factors can be consistent with the corresponding planned flight data after targeted correction, so that the executed flight data can be accurately counted, so as to obtain the accurate execution rate data of the target subject within the target time window. The execution rate data can assist the Air Traffic Control Bureau in making execution rate statistics for each airline or airport and provide a data basis for the corresponding assessment. The overall flight situation of the corresponding target subject within the target time window can be obtained. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0022] Figure 1 A flow chart of a method for determining an aircraft execution rate provided in an embodiment of the present application;
[0023] Figure 2 A structural block diagram of an aircraft execution rate determination device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0024] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.
[0025] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or server that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0026] It should be noted that various aspects of the embodiments within the scope of the appended claims are described below. It should be apparent that the aspects described herein may be embodied in a wide variety of forms, and any specific structure and / or function described herein is merely illustrative. Based on the present application, it should be understood by those skilled in the art that an aspect described herein may be implemented independently of any other aspect, and two or more of these aspects may be combined in various ways. For example, any number of aspects described herein may be used to implement the device and / or practice the method. In addition, other structures and / or functionalities other than one or more of the aspects described herein may be used to implement this device and / or practice this method.
[0027] Please refer to Figure 1 As shown, an embodiment of the present application provides a method for determining an aircraft execution rate, the method comprising:
[0028] S100, obtaining the actual flight data corresponding to the target subject within the target time window to obtain an actual flight data list SF = (SF 1 , S.F. 2 ,…,SF i ,…,SF n ), i = 1, 2, ..., n, where n is the number of actual flight data corresponding to the target subject within the target time window; SF i is the ith actual flight data of the target subject within the target time window; SF i =(SFQ i , S.F.L. i , SFH i , SFZ i );SFQ i is the actual take-off airport corresponding to the ith actual flight data; SFL i is the actual landing airport corresponding to the ith actual flight data; SFH iis the actual flight number corresponding to the ith actual flight data; SFZ i is the actual execution date corresponding to the i-th actual flight data; each actual flight data has a corresponding actual flight type.
[0029] Specifically, in this embodiment, the target entity can be a certain airline or a certain airport, the target time window can be a certain flight season, a certain month, etc., and the actual flight data is the flight data corresponding to a certain flight on a certain execution date, including the corresponding actual take-off airport, actual landing airport, flight number and execution date.
[0030] Here, the actual execution date is determined by the following steps: If SFQ i For domestic airports, SFL i For domestic or non-domestic airports, SFZ i is the departure date; if SFQ i For non-domestic airports, SFL i For domestic airports, SFZ i The date of landing. For domestic flights, the domestic segment of international flights, and international departing flights, the corresponding execution date is the departure date; and for international arriving flights, the corresponding execution date is the landing date. Flight types include passenger and cargo.
[0031] S200, if SF i If the flight data to be revised on the date and / or the flight data to be revised on the type, SFZ i Correct to the planned execution date in the corresponding planned flight data and / or change the SF i The corresponding actual flight type is corrected to the planned flight type in the corresponding planned flight data, otherwise it is not corrected to obtain the updated SF; among which, the flight data to be corrected on the date is SFQ i For non-domestic airports, SFL i It is a domestic airport and SFZ i Actual flight data that is different from the planned execution date in the corresponding planned flight data; flight data whose type is to be revised is actual flight data that includes both domestic segments and non-domestic segments, and actual flight data whose actual flight type is different from the flight type of the corresponding planned flight data.
[0032] Specifically, each actual flight data is traversed. For international inbound flights that take off from non-domestic airports and land at domestic airports, since they do not have the jurisdiction of international airports, when flying in non-domestic areas, or if there are delays due to weather conditions during takeoff, accurate information cannot be obtained. Therefore, the execution date in the flight data corresponding to such flights is the landing date (the date of landing at the domestic airport), and here, the corresponding planned flight data is determined according to its departure airport, landing airport and flight number. According to the corresponding planned flight data, if its corresponding actual execution date (date of landing at the domestic airport) is inconsistent with the planned flight data, it will be corrected to the execution date corresponding to the planned flight data. In this way, the international inbound flights for which accurate information cannot be obtained will be corrected to be consistent with the data in the corresponding planned flight data, so that the air traffic control bureau can obtain the data when counting the execution rate of a certain time window.
[0033] It should be noted that, as an example, the actual flight data that includes both domestic and non-domestic segments can be: the actual flight data of Beijing-Chongqing-Rome, where the domestic segment is Beijing-Chongqing and the international segment is Chongqing-Rome. For the planned flight data corresponding to this actual flight data, the Air Traffic Control Bureau directly sets it as an international flight, and in the actual flight data, the Beijing-Chongqing segment is recorded as the domestic segment, and the Chongqing-Rome segment is recorded as the international segment. Therefore, the actual flight data that includes both domestic and non-domestic segments needs to be corrected and directly corrected to an international flight.
[0034] On the other hand, during certain off-seasons or other special circumstances, an unsold flight may be changed to a cargo flight. When the actual flight number, actual departure airport, actual landing airport and actual execution date are the same as the corresponding planned flight data, and when the air traffic control bureau approves it, it is a passenger flight, but when it is actually operating, it is a cargo flight. In this case, its flight type will be changed to passenger flight so that the air traffic control bureau can obtain the data when calculating the execution rate of a certain time window.
[0035] S300, matching each flight data in the updated SF with the corresponding planned flight data to obtain a target correction list MX=(MX 1 , MX 2 , …, MX j , …, MX m ); j = 1, 2, ..., m; m is the number of flight data in the updated SF that are not identical to the corresponding planned flight data; MX j is the jth flight data in the updated SF that is not exactly the same as the corresponding planned flight data.
[0036] Specifically, after the above two steps, each flight data in the updated SF is matched with the corresponding planned flight data. If the flight is operated completely according to the planned flight data, the actual flight data obtained is the same as the corresponding planned flight data. However, due to weather or other force majeure reasons, the actual flight data may not be completely the same as the corresponding planned flight data.
[0037] S400, correcting MX according to the planned flight data and preset correction rules to obtain a number of target flight data; wherein the target flight data includes the corrected actual flight data and the uncorrected actual flight data; the target flight data is the corresponding take-off airport, landing airport, flight number and execution date and the planned take-off airport, planned landing airport, planned flight number and planned execution date in the corresponding planned flight data all correspond to the same flight data.
[0038] S500, based on the target flight data and the planned flight data corresponding to the target subject within the target time window, obtain the execution rate ZX corresponding to the target subject within the target time window, and ZX meets the following conditions: ZX = MF / JF; wherein MF is the number of target flight data; JF is the number of planned flight data corresponding to the target subject within the target time window.
[0039] Specifically, according to the corresponding planned flight data, the preset correction rules are used to correct MX, so that the actual flight data that may be different from the corresponding planned flight data due to weather or other force majeure is the same as the corresponding planned flight data after correction, so that the aforementioned data can be accurately obtained when calculating the execution rate.
[0040] The target flight data is the flight data corresponding to the corresponding departure airport, landing airport, flight number and execution date and the planned departure airport, planned landing airport, planned flight number and planned execution date in the corresponding planned flight data. The target flight data also includes the corrected actual flight data and the uncorrected actual flight data. Because there are some uncorrected actual flight data (which may be corrected by date and type) that are the same as the corresponding planned flight data, they are directly determined as the target flight data, and there are also some flight data corrected by the preset correction rules that are the same as the corresponding planned flight data, which are determined as target flight data. In this way, the corresponding execution rate of the target subject in the target time window is obtained. The execution rate data is targeted according to the corresponding different situations of each actual flight data, so that the flight data that is not completely consistent with the corresponding planned flight data due to weather reasons or other force majeure factors can be consistent with the corresponding planned flight data after targeted correction, so that the executed flight data can be accurately counted, so that the accurate execution rate data of the target subject in the target time window can be obtained. The execution rate data can assist the Air Traffic Control Bureau in making execution rate statistics for each airline or airport and provide a data basis for the corresponding assessment. It can obtain the overall flight performance of the corresponding target entity within the target time window.
[0041] In an exemplary embodiment of the present application,
[0042] The preset correction rules include: correcting MX in the order of cross-day delay correction, cancellation and make-up correction, mid-season adjustment correction and active return correction.
[0043] The cross-day delay correction is performed by the following steps:
[0044] If (SFZX i -SFZJ i )≤-2, and SFZX i Belong to SFZX i If the execution date is between midnight and 5:00 a.m., SFZ i Corrected to the day before the current actual execution date; among them, SFZX i For SF i The corresponding actual execution hour period; SFZJ i For SF i The corresponding planned flight data in the planned execution hour segment; SF i The corresponding planned flight number, planned departure airport and SF in the planned flight data i The actual flight number and actual departure airport in the corresponding actual flight data are the same.
[0045] Specifically, as an example: if flight A is scheduled to be executed at 23:15 on June 15, 2024; and it is delayed due to weather reasons, the actual execution time is 00:15 on June 16, 2024; then the scheduled execution date of flight A is June 15, 2024, and the planned execution hour period is 23:00; the actual execution date of flight A is June 16, 2024, and the actual execution hour period is 00:00; then its corresponding execution date will be corrected to June 15, 2024.
[0046] According to the above correction method, flights delayed across days can be returned to the corresponding execution date, avoiding missing data when calculating the execution rate, thereby ensuring the accuracy of the execution rate calculation.
[0047] The cancellation and make-up class correction is performed through the following steps:
[0048] If SFQ i and SFL i All are domestic airports, and SFH i If the last digit of is a letter, SFH i The last letter of the flight number is changed to the corresponding number according to the preset cancellation flight number modification rules, and SFZ i Corrected to the day before the current actual execution date;
[0049] If SFQ i and SFL i All are domestic airports, and SFH i If the last two digits of the i The last two letters of the flight number are changed to the corresponding numbers according to the preset cancellation flight number modification rules, and SFZ i Corrected to two days before the current actual execution date.
[0050] Specifically, the preset rules for modifying the canceled flight number are: Z is changed to 0; Y is changed to 1; X is changed to 2; W is changed to 3; V is changed to 4; U is changed to 5; T is changed to 6; S is changed to 7; R is changed to 8; Q is changed to 9.
[0051] If the last digit of the flight number is one of the above letters, the last letter will be changed to the corresponding number according to the preset cancellation flight number modification rules, and the execution date will be corrected to the day before the current actual execution date.
[0052] If the last two digits of the flight number are the above-mentioned letters, the last two letters will be modified to the corresponding numbers according to the preset cancellation flight number modification rules, and the execution date will be corrected to two days before the current actual execution date.
[0053] This is because there will be no letters at the end of the two digits of a normal flight number. The presence of letters means that it is a make-up flight for a cancelled flight.
[0054] According to the above correction method, the make-up flights can be restored to the corresponding planned data, avoiding missing data when calculating the execution rate, and ensuring the accuracy of the execution rate calculation.
[0055] The mid-season adjustment correction is performed by the following steps:
[0056] If SF i If the corresponding planned flight data is the changed planned flight data, then SFZ i Corrected to the execution date corresponding to the planned flight data before the change.
[0057] Specifically, as an example: Airline A's Route 1 is scheduled to fly on Mondays, Wednesdays, and Fridays in the flight data; for some reason, Airline A applies to adjust Route 1 to fly on Tuesdays, Thursdays, and Saturdays, then the actual flight data records the execution dates of Tuesdays, Thursdays, and Saturdays, which need to be adjusted to Mondays, Wednesdays, and Fridays to match the corresponding scheduled flight data.
[0058] In addition, the mid-season adjustment correction is also performed through the following steps:
[0059] If SF i If the corresponding planned flight data is new data, then SF i The corresponding planned flight data is added to the planned flight data list corresponding to the target subject within the target time window.
[0060] According to the above correction method, the adjusted actual flight data can be corrected back to the corresponding planned flight data.
[0061] Specifically, for the newly added actual flight data, corresponding planned flight data is generated and added to the corresponding planned flight data list of the target subject within the target time window, so as to perform an assessment based on the newly added planned flight data.
[0062] Alternatively, the cancelled planned flight data may be directly deleted from the planned flight data list when the execution rate is finally calculated.
[0063] The active handback correction is performed by the following steps:
[0064] If there is a planned flight time corresponding to the planned flight data actively returned by the target subject, the planned flight data corresponding to the actively returned planned flight time will be added to MX.
[0065] Specifically, the airline may proactively return part of the planned flight times due to some special reasons, in which case the planned flight data corresponding to these planned flight times will be deemed to have been flown and added to MX.
[0066] According to the above correction method, part of the planned flight schedules voluntarily returned by the airline company will not affect the calculation result of the execution rate.
[0067] In summary, the above-mentioned correction methods can make targeted corrections according to different actual flight situations, avoid missing data when calculating the execution rate, and ensure the accuracy of the execution rate calculation.
[0068] Please refer to Figure 2 As shown, an embodiment of the present application provides an aircraft execution rate determination device 100, the device comprising:
[0069] The actual data acquisition unit 110 is used to acquire the actual flight data corresponding to the target subject within the target time window to obtain the actual flight data list SF = (SF 1 , S.F. 2 ,…,SF i ,…,SF n ), i = 1, 2, ..., n, where n is the number of actual flight data corresponding to the target subject within the target time window; SF i is the ith actual flight data of the target subject within the target time window; SF i =(SFQ i , S.F.L. i , SFH i , SFZ i );SFQ i is the actual take-off airport corresponding to the ith actual flight data; SFL i is the actual landing airport corresponding to the ith actual flight data; SFH i is the actual flight number corresponding to the ith actual flight data; SFZ i is the actual execution date corresponding to the i-th actual flight data; each actual flight data has a corresponding actual flight type.
[0070] The first correction unit 120 is used to i If the flight data to be revised on the date and / or the flight data to be revised on the type, SFZ i Correct to the planned execution date in the corresponding planned flight data and / or change the SF i The corresponding actual flight type is corrected to the planned flight type in the corresponding planned flight data, otherwise it is not corrected to obtain the updated SF; among which, the flight data to be corrected on the date is SFQ i For non-domestic airports, SFLi It is a domestic airport and SFZ i Actual flight data that is different from the planned execution date in the corresponding planned flight data; flight data whose type is to be revised is actual flight data that includes both domestic segments and non-domestic segments, and actual flight data whose actual flight type is different from the flight type of the corresponding planned flight data.
[0071] The matching unit 130 is used to match each flight data in the updated SF with the corresponding planned flight data to obtain a target correction list MX=(MX 1 , MX 2 , …, MX j , …, MX m ); j = 1, 2, ..., m; m is the number of flight data in the updated SF that are not identical to the corresponding planned flight data; MX j is the jth flight data in the updated SF that is not exactly the same as the corresponding planned flight data.
[0072] The second correction unit 140 is used to correct MX according to the planned flight data and preset correction rules to obtain a number of target flight data; wherein the target flight data includes the corrected actual flight data and the uncorrected actual flight data; the target flight data is the corresponding take-off airport, landing airport, flight number and execution date and the planned take-off airport, planned landing airport, planned flight number and planned execution date in the corresponding planned flight data all correspond to the same flight data.
[0073] The determination unit 150 is used to obtain the execution rate ZX corresponding to the target subject in the target time window according to the target flight data and the planned flight data corresponding to the target subject in the target time window, and ZX meets the following conditions: ZX=MF / JF; wherein MF is the number of target flight data; JF is the number of planned flight data corresponding to the target subject in the target time window.
[0074] An embodiment of the present application further provides a computer program product, which includes program code. When the program product is run on an electronic device, the program code is used to enable the electronic device to execute the steps of the method according to various exemplary embodiments of the present application described above in this specification.
[0075] In addition, although the steps of the method in the present application are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.
[0076] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the implementation methods of the present application.
[0077] In an exemplary embodiment of the present application, an electronic device capable of implementing the above method is also provided.
[0078] Those skilled in the art will appreciate that various aspects of the present application may be implemented as a system, method or program product. Therefore, various aspects of the present application may be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to as "circuit", "module" or "system" herein.
[0079] The electronic device according to this embodiment of the present application is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0080] The electronic device is presented in the form of a general-purpose computing device. The components of the electronic device may include, but are not limited to: the at least one processor mentioned above, the at least one storage device mentioned above, and a bus connecting different system components (including storage devices and processors).
[0081] The storage stores program codes, which can be executed by the processor, so that the processor executes the steps described in the above “Exemplary Method” section of this specification according to various exemplary embodiments of the present application.
[0082] The memory may include readable media in the form of volatile memory, such as random access memory (RAM) and / or cache memory, and may further include read only memory (ROM).
[0083] The storage may also include a program / utility having a set (at least one) of program modules, such program modules including but not limited to: an operating system, one or more application programs, other program modules and program data, each of which or some combination may include the implementation of a network environment.
[0084] The bus may represent one or more of several types of bus structures including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures.
[0085] The electronic device can also communicate with one or more external devices (such as keyboards, pointing devices, Bluetooth devices, etc.), and can also communicate with one or more devices that enable users to interact with the electronic device, and / or communicate with any device (such as routers, modems, etc.) that enables the electronic device to communicate with one or more other computing devices. This communication can be carried out through an input / output (I / O) interface. In addition, the electronic device can also communicate with one or more networks (such as local area networks (LANs), wide area networks (WANs) and / or public networks, such as the Internet) through a network adapter. As shown in the figure, the network adapter communicates with other modules of the electronic device through a bus. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.
[0086] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation methods of the present application.
[0087] In an exemplary embodiment of the present application, a computer-readable storage medium is also provided, on which a program product capable of implementing the above method of the present specification is stored. In some possible implementations, various aspects of the present application can also be implemented in the form of a program product, which includes a program code. When the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps according to various exemplary implementations of the present application described in the above "Exemplary Method" section of the present specification.
[0088] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The 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 readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable 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.
[0089] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.
[0090] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.
[0091] Program code for performing the operations of the present application may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., via the Internet using an Internet service provider).
[0092] In addition, the above-mentioned figures are only schematic illustrations of the processes included in the method according to the exemplary embodiments of the present application, and are not intended to be limiting. It is easy to understand that the processes shown in the above-mentioned figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.
[0093] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.
[0094] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.
Claims
1. A method for determining an aircraft execution rate, characterized in that: The method comprises: S100, obtaining the actual flight data corresponding to the target subject within the target time window to obtain an actual flight data list SF = (SF1, SF2, ..., SF i ,…,SF n ), i = 1, 2, ..., n, where n is the number of actual flight data corresponding to the target subject within the target time window; SF i is the ith actual flight data of the target subject within the target time window; SF i =(SFQ i , S.F.L. i , SFH i , SFZ i );SFQ i is the actual take-off airport corresponding to the ith actual flight data; SFL i is the actual landing airport corresponding to the ith actual flight data; SFH i is the actual flight number corresponding to the ith actual flight data; SFZ i is the actual execution date corresponding to the ith actual flight data; each actual flight data has a corresponding actual flight type; S200, if SF i If the flight data to be revised on the date and / or the flight data to be revised on the type, SFZ i Correct to the planned execution date in the corresponding planned flight data and / or change the SF i The corresponding actual flight type is corrected to the planned flight type in the corresponding planned flight data, otherwise it is not corrected to obtain the updated SF; among which, the flight data to be corrected on the date is SFQ i For non-domestic airports, SFL i It is a domestic airport and SFZ i Actual flight data with a different planned execution date from the corresponding planned flight data; flight data to be corrected includes both domestic and non-domestic segments, and actual flight data with a different actual flight type from the corresponding planned flight data; S300, matching each flight data in the updated SF with the corresponding planned flight data to obtain a target correction list MX = (MX1, MX2, ..., MX j , …, MX m ); j = 1, 2, ..., m; m is the number of flight data in the updated SF that are not identical to the corresponding planned flight data; MX j is the jth flight data in the updated SF that is not completely identical to the corresponding planned flight data; S400, correcting MX according to the planned flight data and a preset correction rule to obtain a number of target flight data; wherein the target flight data includes the corrected actual flight data and the uncorrected actual flight data; the target flight data is the flight data corresponding to the corresponding departure airport, landing airport, flight number and execution date and the planned departure airport, planned landing airport, planned flight number and planned execution date in the corresponding planned flight data; S500, based on the target flight data and the planned flight data corresponding to the target subject within the target time window, obtain the execution rate ZX corresponding to the target subject within the target time window, and ZX meets the following conditions: ZX = MF / JF; wherein MF is the number of target flight data; JF is the number of planned flight data corresponding to the target subject within the target time window.
2. The method for determining the aircraft execution rate according to claim 1, characterized in that: The actual execution date is determined by the following steps: If SFQ i For domestic airports, SFL i For domestic or non-domestic airports, SFZ i is the actual departure date; If SFQ i For non-domestic airports, SFL i For domestic airports, SFZ i The actual landing date.
3. The method for determining the aircraft execution rate according to claim 1, characterized in that: Flight types include passenger and cargo.
4. The method for determining the aircraft execution rate according to claim 1, characterized in that: The preset correction rules include: correcting MX in the order of cross-day delay correction, cancellation and make-up correction, mid-season adjustment correction and active return correction; The cross-day delay correction is performed by the following steps: If (SFZX i -SFZJ i )≤-2, and SFZX i Belong to SFZX i If the execution date is between midnight and 5:00 a.m., SFZ i Corrected to the day before the current actual execution date; among them, SFZX i For SF i The corresponding actual execution hour period; SFZJ i For SF i The corresponding planned flight data in the planned execution hour segment; SF i The corresponding planned flight number, planned departure airport and SF in the planned flight data i The actual flight number and actual departure airport in the corresponding actual flight data are the same; The cancellation and make-up class correction is performed through the following steps: If SFQ i and SFL i All are domestic airports, and SFH i If the last digit of is a letter, then SFH i The last letter of the flight number is changed to the corresponding number according to the preset cancellation flight number modification rules, and SFZ i Corrected to the day before the current actual execution date; If SFQ i and SFL i All are domestic airports, and SFH i If the last two digits of the i The last two letters of the flight number are changed to the corresponding numbers according to the preset cancellation flight number modification rules, and SFZ i Corrected to two days before the current actual execution date; The mid-season adjustment correction is performed by the following steps: If SF i If the corresponding planned flight data is the changed planned flight data, then SFZ i Corrected to the execution date corresponding to the planned flight data before the change; The active handback correction is performed by the following steps: If there is a planned flight time corresponding to the planned flight data actively returned by the target subject, the planned flight data corresponding to the actively returned planned flight time will be added to MX.
5. The method for determining the aircraft execution rate according to claim 4, characterized in that: The mid-season adjustment correction is also performed by the following steps: If SF i If the corresponding planned flight data is new data, then SF i The corresponding planned flight data is added to the planned flight data list corresponding to the target subject within the target time window.
6. An aircraft execution rate determination device, characterized in that: The device comprises: The actual data acquisition unit is used to acquire the actual flight data corresponding to the target subject within the target time window to obtain the actual flight data list SF = (SF1, SF2, ..., SF i ,…,SF n ), i = 1, 2, ..., n, where n is the number of actual flight data corresponding to the target subject within the target time window; SF i is the ith actual flight data of the target subject within the target time window; SF i =(SFQ i , S.F.L. i , SFH i , SFZ i );SFQ i is the actual take-off airport corresponding to the ith actual flight data; SFL i is the actual landing airport corresponding to the ith actual flight data; SFH i is the actual flight number corresponding to the ith actual flight data; SFZ i is the actual execution date corresponding to the ith actual flight data; each actual flight data has a corresponding actual flight type; The first correction unit is used if SF i If the flight data to be revised on the date and / or the flight data to be revised on the type, SFZ i Correct to the planned execution date in the corresponding planned flight data and / or change the SF i The corresponding actual flight type is corrected to the planned flight type in the corresponding planned flight data, otherwise it is not corrected to obtain the updated SF; among which, the flight data to be corrected on the date is SFQ i For non-domestic airports, SFL i It is a domestic airport and SFZ i Actual flight data with a different planned execution date from the corresponding planned flight data; flight data to be corrected includes both domestic and non-domestic segments, and actual flight data with a different actual flight type from the corresponding planned flight data; A matching unit is used to match each flight data in the updated SF with the corresponding planned flight data to obtain a target correction list MX = (MX1, MX2, ..., MX j , …, MX m ); j = 1, 2, ..., m; m is the number of flight data in the updated SF that are not identical to the corresponding planned flight data; MX j is the jth flight data in the updated SF that is not completely identical to the corresponding planned flight data; A second correction unit is used to correct the MX according to the planned flight data and a preset correction rule to obtain a number of target flight data; wherein the target flight data includes the corrected actual flight data and the uncorrected actual flight data; the target flight data is the flight data corresponding to the corresponding take-off airport, landing airport, flight number and execution date and the planned take-off airport, planned landing airport, planned flight number and planned execution date in the corresponding planned flight data; The determination unit is used to obtain the execution rate ZX corresponding to the target subject in the target time window according to the target flight data and the planned flight data corresponding to the target subject in the target time window, and ZX meets the following conditions: ZX=MF / JF; wherein MF is the number of target flight data; JF is the number of planned flight data corresponding to the target subject in the target time window.
7. A non-transitory computer-readable storage medium, characterized in that: The storage medium stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the method as claimed in any one of claims 1 to 5.
8. An electronic device, characterized in that: The invention comprises a processor and the non-transitory computer-readable storage medium as claimed in claim 7.
Citation Information
Patent Citations
Method for semi-automatically correcting flight next-day plan data of flight
CN114283623A
Flight business primary key processing method and device, electronic equipment and storage medium
CN116701408A
Flight time correction method and system based on data analysis
CN118230608A
Method for revising a target take off time in the environment of an airport, associated system and aircraft comprising such a system
US20200126433A1
Departure flight data updating method and related device
WO2023273518A1
