A flight schedule full life cycle dynamic management method based on execution rate prediction

Abstract

The application discloses a kind of based on execution rate prediction's flight time whole life cycle dynamic management method, including constructing core table system and date interval week enumeration formula, according to rule split and calculate and process airline application information, process flight time cancellation, process flight time return and approved quota, process flight time return and approved quota, daily update flight actual operation execution state, season operation in real time and estimate and predict time execution rate, after season end, the actual execution rate of whole time is counted;The application solves the problems that the existing system lacks flight time whole life cycle closed-loop management and control capability, time execution rate monitoring lags behind, lacks pre-warning capability, breaks the limitation that traditional mode can only rely on manual checking to carry out post-execution rate analysis after season ends, builds whole-process execution rate prediction and early warning capability relying on real-time operation data, helps airlines to adjust operation strategy in time, reduces the idle and waste of flight time resources.

Description

Technical Field

[0001] This invention belongs to the field of aviation operation management technology, specifically relating to a dynamic management method for the entire lifecycle of flight slots based on execution rate prediction. Background Technology

[0002] With the rapid development of the civil aviation industry, flight slot resources are becoming increasingly scarce. In addition, with the gradual opening of low-altitude airspace and the increasing number of various unmanned aerial vehicles such as electric vertical take-off and landing aircraft (EVTOL), the supply and demand contradiction of airport resources available for aircraft take-off and landing is becoming more and more prominent. This places unprecedented demands on the standardization, efficiency and precision of slot management.

[0003] The current flight schedule management system has the following main shortcomings:

[0004] 1. Lack of dynamic management mechanism for the entire lifecycle: Existing systems focus more on the slot allocation at the beginning of the flight season. For dynamic adjustment business such as slot cancellation, return, and restitution during the flight season, there is a lack of unified data models and process support, making it difficult to achieve closed-loop management of slot resources from application, allocation, adjustment to completion.

[0005] 2. Rigid quota management and lack of intelligent splitting capabilities: In the process of time slot return or cancellation, there is a lack of a real-time dynamic verification mechanism for the remaining quota. When an airline applies to return more time slots than its available limit, the system cannot automatically perform intelligent splitting processing of "partial return and partial cancellation," often requiring manual intervention for judgment, which is inefficient and prone to errors.

[0006] 3. Lagging execution rate monitoring and lack of early warning mechanisms: Traditional slot execution rate analysis is mostly conducted after the flight season ends, which is essentially "hindsight." The system cannot predict execution trends and issue early warnings based on real-time data during the flight season, causing airlines to be unable to adjust their operating strategies in a timely manner, resulting in the idleness and waste of slot resources.

[0007] 4. The execution rate assessment system is not perfect: The slot execution rate is a core quantitative indicator for civil aviation management departments to assess the operational quality of airlines, evaluate the efficiency of slot resource utilization, and determine the priority of slot allocation for the next flight season. However, the existing technology lacks a technical solution that can automatically and accurately calculate the execution rate and link it with dynamic adjustment operations (such as return and re-return) in real time. A large amount of work is done manually, which affects the accuracy and authority of the assessment data and fails to effectively incentivize airlines to improve slot utilization.

[0008] Therefore, there is an urgent need to build an intelligent management method that can achieve real-time dynamic adjustment automation, precise performance evaluation, and forward-looking operation monitoring. Summary of the Invention

[0009] To address the shortcomings of the existing technologies, the present invention aims to provide a dynamic management method for the entire lifecycle of flight slots based on execution rate prediction. This method solves the problems of existing systems lacking closed-loop management of the entire lifecycle of flight slots, lagging slot execution rate monitoring, and lacking early warning capabilities. The present invention breaks through the drawbacks of the traditional model, which can only conduct post-event execution rate analysis through manual verification after the flight season ends. It relies on real-time operational data to build a full-process prediction and execution rate early warning capability, helping airlines to adjust their operational strategies in a timely manner and reduce slot resource idleness and waste.

[0010] To achieve the above objectives, the technical solution adopted by the present invention is as follows:

[0011] The present invention provides a dynamic management method for the entire lifecycle of flight slots based on execution rate prediction, comprising the following steps:

[0012] 1) Construct the core table system and the formula for enumerating the day of the week for each date range;

[0013] 2) Receive the application information from the airline, and sequentially complete the splitting of flight time / flight time attribute and flight period / week dimension; for the split records, fill in the execution rate group code, flight time quantity, and business type fields respectively to generate a complete flight time plan execution table;

[0014] 3) Execute the flight schedule cancellation service, select the original cancellation operation record, and enter the cancellation start and end times; split the original cancellation operation record and the original cancellation operation related records that match the association conditions in the flight schedule plan execution table into three segments, and configure the execution start and end times and business type for each record respectively; populate the flight schedule quantity field of the three split records;

[0015] 4) Execute the flight slot return business, select the original record of the return operation, and enter the start and end times; split the original record of the return operation and the related records of the original return operation obtained by matching and filtering into three segments, and complete the calculation of the flight slot quantity and field filling; change the business type or split the return segment record a second time according to the relationship between the remaining quantity and the flight slot quantity returned this time; update the flight slot plan execution table and the airline slot application table.

[0016] 5) Execute the flight slot return service, select the original return operation record, and enter the start and end times; split the original return operation record and the related original return operation records obtained by matching and filtering into three segments, and complete the calculation and field filling of the flight slot quantity; change the business type or split the return segment record a second time according to the relationship between the remaining amount and the flight slot quantity returned this time; update the flight slot plan execution table and the airline slot application table.

[0017] 6) Periodically migrate the flight schedule execution records from the previous day in the flight schedule execution table to the actual flight schedule execution table; then perform correlation matching based on the actual flight execution data and update the flight execution status; for unexecuted flight records, adjust the flight execution status after review and approval;

[0018] 7) Calculate the execution rate during the flight season and the predicted execution rate for the current flight season according to the group code of the flight schedule execution rate. Then compare the predicted execution rate with the preset warning line and alarm line for the current flight season in turn, and push the prompt information to the corresponding airline based on the comparison results.

[0019] 8) Calculate the actual flight schedule execution rate at the end of the flight season and compare the execution rate with the preset alarm threshold for the flight season. When the actual execution rate is lower than the alarm threshold, push the data to the corresponding airline.

[0020] Further, step 1) specifically includes:

[0021] 11) Establish a flight schedule execution table, whose specific data items include: flight schedule execution rate calculation group code, flight season, flight number, day of the week, departure airport, arrival airport, flight time, flight time attribute, start execution time, end execution time, business type and flight time volume;

[0022] 12) Establish an airline slot application form, the specific data information of which includes: flight season, flight number, flight schedule, departure airport, departure time, arrival airport, arrival time, start time, end time, and business type;

[0023] 13) Establish a formula for enumerating the weekdays for a date range to simultaneously calculate the total number of dates corresponding to the target weekday and the specific date list;

[0024] 14) Establish a flight slot return / refund quota table, whose specific data items include: flight season, return quota and refund quota; and follow the uniqueness rule: only one quota record can exist in the table for a single flight season;

[0025] 15) Establish a flight schedule execution table, whose specific data items include: schedule execution rate calculation group code, flight season, flight number, day of the week, departure airport, arrival airport, flight schedule, flight schedule attribute, actual execution time, business category, execution category and appeal reason;

[0026] 16) Establish a flight schedule execution rate early warning / alarm table, whose specific data items include: flight season, early warning line, and alarm line; and follow the uniqueness rule: only one record can exist in the table for a single flight season.

[0027] Further, step 13) specifically includes:

[0028] 131) Define S as the start date, E as the end date, and T as the target weekday;

[0029] 132) Calculate the weekday W of the starting date using the Zeller formula. S The week of the end date E ;

[0030] 133) Calculate the total number of days D from the start date to the end date. C The details are as follows:

[0031] ;

[0032] 134) Calculate the first target date between the start date and the end date. The details are as follows:

[0033] ;

[0034] Where mod represents the remainder operation;

[0035] 135) Calculate the total number N of dates corresponding to the target week, as follows:

[0036] ;

[0037] in, Indicates rounding down; when N=0, it is a list of specific dates corresponding to the target weekday. If empty; otherwise, the specific date list F corresponding to the target weekday is:

[0038] ;

[0039] Among them, F N This represents the Nth target date between the start date and the end date.

[0040] Further, step 2) specifically includes:

[0041] 21) Receive the slot application data submitted by the airline and enter the application data into the airline slot application form. The application information includes: flight season, flight number, flight schedule, departure airport, departure time, arrival airport, arrival time, start time, end time and business type.

[0042] 22) Based on the airline slot application information obtained in step 21), the flight slot / slot attribute and flight period / week dimension are split in sequence according to the flight slot execution rate calculation grouping rules; for each record after splitting, the execution rate calculation group code, flight slot quantity and business type fields are filled in respectively, and the processed valid records are stored in the flight slot plan execution table.

[0043] 23) Delete invalid records in step 22) where the flight time slot quantity is 0 in the flight time slot plan execution table. If the time slot quantity of all records in step 22) in the flight time slot plan execution table is 0, delete the records in step 21) in the airline time slot application form.

[0044] Furthermore, step 3) specifically includes:

[0045] 31) When performing flight slot cancellation, select the record with the business type "New" in the airline slot application form and define the record as the original record for the cancellation operation; enter the start time and end time corresponding to this cancellation operation, and the entered cancellation start time and cancellation end time must be within the time interval formed by the start execution time and end execution time of the original record for the cancellation operation;

[0046] 32) Based on the data entered in step 31), the original record of the cancellation operation is split into a pre-cancellation retention segment record, a cancellation segment record, and a post-cancellation retention segment record according to the start and end times of the cancellation;

[0047] 33) Based on the original record of the cancellation operation selected in step 31), retrieve the flight schedule execution table to obtain the corresponding associated record, and define the associated record as the original associated record of the cancellation operation; then, according to the start time and end time of the cancellation, divide each original associated record of the cancellation operation into the original associated record before cancellation, the original associated record after cancellation, and the original associated record after cancellation.

[0048] 34) Remove the original record of the cancellation operation selected in step 31) of the airline slot application form; at the same time, enter and save the three records generated in step 32) as the application information submitted by the airline into the airline slot application form.

[0049] 35) Remove the original associated record of the cancellation operation obtained in step 33) from the flight schedule execution table; at the same time, split each original associated record of the cancellation operation in step 33) into three records and save them as new data to the flight schedule execution table;

[0050] 36) Delete the invalid records in step 35) where the number of flight slots in the flight schedule execution table is 0.

[0051] Further, step 4) specifically includes:

[0052] 41) When performing flight slot return operations, select the record with the business type "New" in the airline slot application form and define this record as the original record for the return operation; enter the start time and end time corresponding to this return operation, wherein the start time and end time of the return are respectively within the start execution time and end execution time interval of the selected record; and the entered return start time and return end time must both be within the time interval formed by the start execution time and end execution time of the original record for the return operation.

[0053] 42) Based on the data entered in step 41), the original record of the handover operation is divided into the pre-handover retention segment record, the handover segment record, and the post-handover retention segment record according to the start and end times of the handover.

[0054] 43) Based on the original record of the handover operation selected in step 41), retrieve the flight schedule execution table to obtain the corresponding associated record, and define the record as the original associated record of the handover operation; then, according to the start time and end time of the handover, divide each original associated record of the handover operation into the original associated pre-handover retention segment record, the original associated handover segment record, and the original associated post-handover retention segment record.

[0055] 44) For each original associated return segment record in step 43), extract the flight slot execution rate of the record, calculate the group code, flight season, and flight slot quantity; fill the flight slot quantity field value into the planned return flight slot quantity. Where I represents the flight slot execution rate calculation group code; using this flight slot execution rate calculation group code and flight season as matching conditions, all records in the flight slot plan execution table with the business type "returned" are retrieved, and the flight slot quantity field values ​​of all retrieved records are summed, which is the returned flight slot quantity corresponding to the flight slot execution rate calculation group code. Search the flight slot return / return limit table for records based on flight season as the matching condition. If no record is found, proceed to step 48); otherwise, populate the return limit field value of the record. (Execute step 45).

[0056] 45) Calculate the remaining returnable flight slots based on the flight slot execution rate extracted in step 44) using the block code. , ;when At that time, for each original associated return segment record in step 43), update its business type field to cancel, and proceed to step 48). When, proceed to step 48); when and At that time, the number of flight slots that cannot be returned this time is calculated. , (Execute step 46).

[0057] 46) For each original associated return segment record in step 43), further decompose it into two records: a record for retaining the return segment and a record for turning the return segment into a cancellation segment.

[0058] 47) Remove the original associated records of the handover operation obtained in step 43) from the flight schedule execution table; split each original associated record of the handover operation in step 43) to generate the original associated pre-handover retained segment record and the original associated post-handover retained segment record, and save the retained handover segment record and handover-to-cancellation segment record generated in step 46) as new data to the flight schedule execution table; delete the invalid records in the flight schedule execution table where the new data flight slot quantity is 0; after completion, proceed to step 49).

[0059] 48) Remove the original associated records of the handover operation obtained in step 43) from the flight schedule execution table; split each original associated record of the handover operation in step 43) into three records and save them as new data to the flight schedule execution table; delete the invalid records in the flight schedule execution table where the new data flight slot quantity is 0;

[0060] 49) Remove the original record of the return operation selected in step 41) of the airline slot application form; at the same time, enter and save the three records generated in step 42) as the application information submitted by the airline to the airline slot application form.

[0061] Furthermore, step 5) specifically includes:

[0062] 51) When performing flight slot return service, select the record with the business type "new" in the airline slot application form and define the record as the original record of the return operation; enter the start time and end time corresponding to this return operation, and the entered return start time and return end time must be within the time interval formed by the start execution time and end execution time of the original record of the return operation.

[0063] 52) Based on the data entered in step 51), the original record of the return operation is divided into a pre-return retention record, a return record, and a post-return retention record according to the start and end times of the return.

[0064] 53) Based on the original record of the return operation selected in step 51), retrieve the flight schedule execution table to obtain the corresponding associated record, and define the record as the original associated record of the return operation; then, according to the start time and end time of the return, divide each original associated record of the return operation into the original associated record before return, the original associated record after return, and the original associated record after return.

[0065] 54) For each original associated return segment record in step 53), extract the flight slot execution rate of the record, calculate the group code, flight season, and flight slot quantity; fill the flight slot quantity field value into the planned return flight slot quantity. Where I represents the flight slot execution rate calculation group code; simultaneously, using this flight slot execution rate calculation group code and flight season as matching conditions, all records in the flight slot plan execution table with the business type of "return" are retrieved, and the sum of the flight slot quantity field values ​​of all retrieved records is the returned flight slot quantity corresponding to this flight slot execution rate calculation group code. Using flight season as the matching criterion, retrieve records from the flight slot return / refund limit table. If no record is found, proceed to step 58); otherwise, populate the return limit field value of the record. (Execute step 55).

[0066] 55) Calculate the remaining returnable flight slots based on the flight slot execution rate extracted in step 54) using the block code. , ;when At that time, for each original associated return segment record in step 53), update its business type field to cancel, and execute step 58); when and When, execute step 58); when and At that time, the number of flight slots that cannot be returned this time is calculated. , (Execute step 56).

[0067] 56) For each original associated return segment record in step 53), further decompose it into two records: a record to retain the return segment and a record to convert the return segment to a cancellation segment.

[0068] 57) Remove the original associated records of the return operation obtained in step 53 from the flight schedule execution table; save the original associated return pre-return retained segment and original associated return post-return retained segment records generated by splitting each original associated record of the return operation in step 53), as well as the retained return segment record and return-to-cancellation segment record generated in step 56), as new data to the flight schedule execution table; delete the invalid records in the flight schedule execution table where the new data flight slot quantity is 0; after completion, proceed to step 59).

[0069] 58) Remove the original associated records of the return operation obtained in step 53) from the flight schedule execution table; split each original associated record of the return operation in step 53) into three records and save them as new data to the flight schedule execution table; delete the invalid records in the table where the new data flight slot quantity is 0;

[0070] 59) Remove the original record of the return operation selected in step 51) from the airline slot application form; at the same time, enter and save the three records generated in step 52) as the application information submitted by the airline to the airline slot application form.

[0071] Furthermore, step 6) specifically includes:

[0072] 61) Configure a scheduled data synchronization task to perform data migration operations at a fixed time H every day: Filter out all records in the flight schedule execution table whose scheduled execution date is the previous day, and migrate the data completely to the actual flight schedule execution table;

[0073] 62) Extract key information from the previous day's actual flight execution data, specifically including: flight number, planned departure airport, actual departure airport, planned arrival airport, actual arrival airport, planned execution date, and actual execution date; for supplementary flights, the flight number format conversion needs to be completed in advance;

[0074] 63) Perform a line-by-line matching operation between the actual flight execution data in step 62) and the records in the actual execution table of transfer flight times in step 61), and perform the matching and field update in two steps;

[0075] 64) For flight records marked as not executed in the actual execution table of flight schedules, enter the corresponding appeal supporting information and the reason for the appeal; after the review is completed and the review result is determined to be passed, change the flight execution category corresponding to the flight record from not executed to executed.

[0076] Furthermore, step 7) specifically includes:

[0077] 71) During the current flight season, track the flight schedule execution status in real time and calculate the real-time flight schedule execution data; calculate group codes based on the flight schedule execution rate from the actual flight schedule execution table, and classify and statistically analyze the flight schedule execution details corresponding to each group code;

[0078] 72) During the current flight season, track the flight schedule execution status in real time and predict the expected flight schedule execution data for the current flight season;

[0079] 73) The current season's slot availability forecast. The system calculates warnings and alarms based on the warning and alarm lines defined in the flight schedule execution rate warning / alarm table. If the judgment conditions are met, the system sends relevant prompts on the flight schedule execution status to the corresponding airline.

[0080] Furthermore, step 8) specifically includes:

[0081] 81) Calculate the actual execution rate of flight schedules for the current flight season using group code I. The calculation formula is:

[0082] ;

[0083] 82) The actual execution rate of flight times corresponding to each group code for this flight season. The alarm threshold for this flight season is compared with the pre-set alarm threshold in the flight schedule execution rate warning table; if If the data falls below the alarm threshold, the abnormal flight data will be sent to the corresponding airline.

[0084] The beneficial effects of this invention are:

[0085] 1. This invention introduces a "date interval weekday enumeration formula" and automatic segmentation logic, transforming the time adjustment business, which originally relied on manual judgment and processing, into automatic segmentation and calculation by the system. This significantly improves the processing efficiency of time adjustment, reduces errors caused by manual intervention, and enhances the standardization and reliability of time management.

[0086] 2. This invention introduces a "dynamic quota verification" and "automatic cancellation" mechanism in the time-based return and repayment business, realizing intelligent splitting and compliant processing in over-limit scenarios. It effectively solves the problems of difficulty in handling over-limit, cumbersome process, and easy error in the traditional model, and improves the intelligence level and processing flexibility of the time-based adjustment business.

[0087] 3. This invention adds an execution rate prediction step during the flight season, which can identify execution risks in advance and send alerts to airlines, helping airlines to optimize flight plans in a timely manner and improve the overall utilization rate of slot resources.

[0088] This invention replaces the traditional manual processing method with automation, automatically reviewing the execution status of flight slots throughout the flight season and calculating the execution rate, which significantly improves efficiency and provides detailed data for civil aviation management departments, helping to formulate more scientific slot allocation policies. Attached Figure Description

[0089] Figure 1 This is a flowchart illustrating the method of the present invention. Detailed Implementation

[0090] To facilitate understanding by those skilled in the art, the present invention will be further described below with reference to embodiments and accompanying drawings. The content mentioned in the embodiments is not intended to limit the present invention.

[0091] Flight slots refer to an aircraft's right to use relevant infrastructure and services for arrival at or departure from an airport on a specified date and time. Flight slot times are based on wheel chock timing and wheel chock removal time. According to the Civil Aviation Administration of China (CAAC) regulations, air carriers must apply for flight slots at 5-minute intervals. For example, flight slots applied for between 9 and 10:00 AM can only include 12 time points: 9:00, 9:05, 9:10, 9:15, 9:20, 9:25, 9:30, 9:35, 9:40, 9:45, 9:50, and 9:55.

[0092] Flight schedule execution rate refers to the ratio of the number of flight schedules actually executed as planned to the total number of flight schedules that should be counted in daily operations management; the calculation should follow the following rules:

[0093] Cycle rule: Execution rate is calculated on a weekly basis, using a specific operating day within each week as the calculation benchmark;

[0094] Multiple series rule: If the same flight retains two or more flight time series at the same time, the execution rate of each series should be calculated independently;

[0095] Joint operation rule: For jointly operated flights involving two or more flight time series, the execution rate should be calculated separately for each different time series;

[0096] To facilitate the calculation of flight schedule execution rate, flight schedules should be grouped according to the above rules, with each group corresponding to one execution rate calculation result.

[0097] A make-up flight (also called a supplementary flight) refers to an additional flight arranged by an airline to transport stranded passengers after a originally scheduled flight has been canceled due to weather, mechanical failure, air traffic control, or other reasons.

[0098] The assessment cycle for flight slot execution rate is consistent with the Civil Aviation Administration's flight season, which is divided into the summer / autumn flight season (the last Sunday of March to the last Saturday of October) and the winter / spring flight season (the last Sunday of October to the last Saturday of March of the following year). At the end of each flight season, the execution status of all approved flight slots within that season is statistically analyzed to calculate the flight slot execution rate. The assessment results will serve as an important basis for airlines' eligibility to apply for flight slots in the next flight season, the allocation of new slot quotas, and the adjustment of existing slots.

[0099] Reference Figure 1 As shown, the present invention provides a dynamic management method for the entire lifecycle of flight slots based on execution rate prediction, comprising the following steps:

[0100] 1) Construct the core business table and build the day-of-week enumeration formula for the date range to perform the calculations that provide the required time dimension rules;

[0101] The core business tables include a flight schedule execution table, a flight schedule return / refund limit table, a flight schedule actual execution table, and a flight schedule execution rate warning / alarm table.

[0102] Specifically, step 1) includes:

[0103] 11) Establish a flight schedule execution table, whose specific data items include: flight schedule execution rate calculation group code (abbreviated as: group code), flight season (3 characters, the first 2 characters are the last two digits of the year, the third character is the flight season code: S=summer and autumn flight season, W=winter and spring flight season), flight number, day of the week (1 character, "1" represents every Monday, ..., "7" represents every Sunday), departure airport, arrival airport, flight time, flight time attribute ("D" represents departure, "A" represents arrival), start execution time, end execution time, business type (1 character, "0" represents new, "1" represents cancellation, "2" represents return, "3" represents return), and number of flight slots;

[0104] The departure and arrival airports use the four-letter airport codes of the International Civil Aviation Organization (ICAO); the flight times use the 24-hour time format (HHMM), accurate to the minute; and the start and end times use the year-month-day time format (YYYYMMDD).

[0105] 12) Establish an airline slot application form, whose specific data information includes: flight season, flight number, flight schedule (1-7 characters, consisting of 1, 2, 3, 4, 5, 6, 7, representing Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday respectively), departure airport, departure time, arrival airport, arrival time, start time, end time, and service type (1 character, "0" represents new, "1" represents cancellation, "2" represents return, and "3" represents return).

[0106] 13) Establish a formula for enumerating the weekdays within a date range to simultaneously calculate the total number of dates corresponding to the target weekday and the specific date list, as follows:

[0107] 131) Define S as the start date, E as the end date, and T as the target weekday (Monday = 1, ..., Sunday = 7);

[0108] 132) Calculate the weekday W of the starting date using the Zeller formula. S The week of the end date E ;

[0109] 133) Calculate the total number of days D from the start date to the end date (inclusive). C The details are as follows:

[0110] ;

[0111] 134) Calculate the first target date between the start date and the end date (inclusive). The details are as follows:

[0112] ;

[0113] Where mod represents the remainder operation;

[0114] 135) Calculate the total number N of dates corresponding to the target week, as follows:

[0115] ;

[0116] in, Indicates rounding down; when N=0, it is a list of specific dates corresponding to the target weekday. If empty; otherwise, the specific date list F corresponding to the target weekday is:

[0117] ;

[0118] Among them, F N This represents the Nth target date between the start date and the end date.

[0119] 14) Establish a flight slot return / refund quota table, whose specific data items include: flight season, return quota and refund quota; and follow the uniqueness rule: only one quota record can exist in the table for a single flight season;

[0120] 15) Establish a flight schedule actual execution table, whose specific data items include: schedule execution rate calculation group code (abbreviated as: group code), flight season, flight number, day of the week, departure airport, arrival airport, flight schedule, flight schedule attribute, actual execution time, business category, execution category (1 character, "0" represents not executed, "1" represents executed) and appeal reason;

[0121] 16) Establish a flight schedule execution rate early warning / alarm table, whose specific data items include: flight season, early warning line, and alarm line; and follow the uniqueness rule: only one record can exist in the table for a single flight season.

[0122] 1) Construct the core table system and the formula for enumerating the day of the week for each date range;

[0123] 2) Receive application information from airlines and sequentially complete the splitting of flight schedule / flight schedule attribute and flight period / weekday dimension; for the split records, populate the execution rate grouping code, flight slot quantity, and business type fields respectively to generate a complete flight schedule plan execution table; details are as follows:

[0124] 21) Receive the slot application data submitted by the airline and enter the application data into the airline slot application form. The application information includes: flight season, flight number, flight schedule (1-7 characters, consisting of 1, 2, 3, 4, 5, 6, 7, representing Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday respectively), departure airport, departure time, arrival airport, arrival time, start time, end time, and business type (default is "0", representing new).

[0125] The rules for the shift period field are as follows:

[0126] The schedule string consists of the numbers 1–7;

[0127] Each number represents the day of the week in which the event takes place.

[0128] The order of numbers does not affect the meaning (but they are generally arranged from smallest to largest).

[0129] Duplicate numbers are not allowed (e.g., "113" is invalid).

[0130] Minimum length 1 (e.g., "1"), maximum length 7 (e.g., "1234567");

[0131] For example:

[0132] "135" → Operates on Mondays, Wednesdays, and Fridays;

[0133] "67" → Operates on Saturdays and Sundays;

[0134] "246" → Operates on Tuesdays, Thursdays, and Saturdays.

[0135] 22) Based on the airline slot application information obtained in step 21), perform flight slot / slot attribute splitting and flight period / week dimension splitting according to the flight slot execution rate calculation grouping rules; for each record after splitting, fill in the execution rate calculation grouping code, flight slot quantity, and business type fields respectively, and then store the processed valid records into the flight slot plan execution table; as follows:

[0136] 221) Flight Schedule / Schedule Attribute Splitting: The flight schedule execution table sets flight schedules and flight schedule attributes. The flight schedule application information submitted by the airline includes departure and arrival times. These two are split and then included in the flight schedule execution table, as follows:

[0137] For a single airline slot application, two independent records are generated, corresponding to the departure time and the arrival time respectively. The departure time from the original application information is filled into the flight time field of the first record, and the flight time attribute field of that record is also filled with departure. The arrival time from the original application information is filled into the flight time field of the second record, and the flight time attribute field of that record is also filled with arrival. Except for the flight time field and the flight time attribute field, all other fields of the two split records, including flight season, flight number, flight schedule, departure airport, arrival airport, start execution time, end execution time, and business type, are consistent with the original application information.

[0138] 222) Flight Schedule / Weekday Dimension Splitting: The flight schedule execution table includes a weekday field, which is a 1-character data type with values ​​from 1 to 7, uniquely corresponding to Monday through Sunday. The airline's schedule application information includes a flight schedule field, which is a 1-7 character data type consisting of unique combinations of the numbers 1-7. A splitting determination is made for the flight schedule field: if the flight schedule field length is 1, no splitting is required; if the flight schedule field length is greater than 1, the two records obtained in step 221) need to be split into flight schedules and weeks respectively. Specific rules are as follows:

[0139] If the length of the shift field is N (1≤N≤7, where N is a positive integer), then the record information will be split into N independent records;

[0140] Each split record corresponds to a single numeric character in the schedule field, which is then used to fill the weekday field in the flight schedule execution table. Except for the weekday field, all other fields, including flight season, flight number, departure airport, arrival airport, start time, end time, and business type, are filled in according to the original application information and kept consistent. Throughout the schedule splitting process, it must be ensured that all numeric characters in the schedule field are unique and complete, and that the weekday field value of each split record is unique and matches the corresponding numeric character in the schedule field.

[0141] 223) Filling the Flight Schedule Execution Rate Calculation Group Code: For each record stored in the flight schedule plan execution table in step 222), fill in the flight schedule execution rate calculation group code field. The group code is obtained by concatenating the flight season in the flight schedule application information with the independently generated universally unique identifier (UUID), with the flight season first and the UUID second. The UUID uses the fourth version of universally unique identifiers, and each record corresponds to a unique UUID. The flight schedule execution rate calculation group code must be filled before the record is stored in the flight schedule plan execution table to ensure that the group code is globally unique. At the same time, this field must fully cover all records generated by flight schedule / schedule attribute splitting and flight period / weekday dimension splitting, without any omissions.

[0142] 224) Assigning values ​​to the time slot quantity field: Fill the flight time slot quantity field in the records stored in the flight time schedule execution table in step 222). Using the day of the week enumeration formula for the date interval in step 13), take the flight execution start date corresponding to the record as the calculation start date and the flight execution end date as the calculation end date (the end date is included). Use the value of the day of the week field of the record as the target week to calculate the total number of dates corresponding to the target week in the date interval, and fill the number of dates into the flight time slot quantity field.

[0143] 23) Delete invalid records in step 22) where the flight slot quantity in the flight slot schedule execution table is 0. If all records in step 22) of the flight slot schedule execution table have a slot quantity of 0, also delete the records in step 21) of the airline slot request form. A specific example of records in the flight slot schedule execution table is shown in Table 1.

[0144] Table 1

[0145]

[0146] Example 1: Flight schedule execution rate calculation group code S24UUID1, during the 25W flight season from December 1, 2025 to February 23, 2026, flight number CA1000 will operate normally every Monday as scheduled, departing from ZBAA airport at 8:00 and landing at ZGGG airport.

[0147] Example 2: Flight schedule execution rate calculation group code S24UUID2, during the 26S flight season from April 1, 2026 to July 1, 2026, flight number CA2000 will operate normally every Wednesday as scheduled, taking off from ZWWW airport and landing at ZSSS airport at 10:00.

[0148] 3) Execute the flight schedule cancellation service. Select the original cancellation record and enter the cancellation start and end times. Split the original cancellation record and the related records in the flight schedule execution table that match the associated conditions into three segments, and configure the execution start and end times and service type for each record. Populate the flight schedule quantity field for the three split records. Details are as follows:

[0149] 31) When performing flight slot cancellation, select the record with the business type "New" in the airline slot application form and define the record as the original record for the cancellation operation; enter the start time and end time corresponding to this cancellation operation, and the entered cancellation start time and cancellation end time must be within the time interval formed by the start execution time and end execution time of the original record for the cancellation operation;

[0150] 32) Based on the data entered in step 31), split the original cancellation operation record into a pre-cancellation retention segment (first record), a cancellation segment (second record), and a post-cancellation retention segment (third record) according to the start and end times of cancellation; as follows:

[0151] The start execution time of the previously retained record is equal to the start execution time of the original record being cancelled; the end execution time of the previously retained record is equal to the start time of the cancellation - 1; and the business type of the previously retained record is "new".

[0152] The start execution time of the cancellation segment record = the start time of cancellation, the end execution time of the cancellation segment record = the deadline of cancellation, and the business type of the cancellation segment record = cancellation;

[0153] The start execution time of the retained record after cancellation = the cancellation deadline + 1; the end execution time of the retained record after cancellation = the end execution time of the original record of the cancellation operation; the business type of the retained record after cancellation = new.

[0154] The remaining fields of the three records, including flight season, flight number, flight schedule, departure airport, arrival airport, departure airport, departure time, arrival airport, and arrival time, are consistent with the original record information of the cancellation operation;

[0155] If the start time of a record in the retained segment before cancellation is later than the end time, the record is considered an abnormal record and is discarded; if the start time of a record in the retained segment after cancellation is later than the end time, the record is considered an abnormal record and is discarded.

[0156] 33) Based on the original cancellation operation record selected in step 31), retrieve the flight schedule execution table to obtain the corresponding associated record, and define the associated record as the original associated record of the cancellation operation; then, according to the start time and end time of the cancellation, divide each original associated record of the cancellation operation into the original associated record before cancellation (the first record), the original associated record after cancellation (the second record), and the original associated record after cancellation (the third record);

[0157] The association rules between the flight schedule execution table and the original cancellation record must simultaneously meet the following matching conditions:

[0158] (1) The flight season in the flight schedule execution table is equal to the flight season in the original record of the cancellation operation;

[0159] (2) The flight number in the flight schedule execution table is equal to the flight number in the original cancellation record;

[0160] (3) The weekday field value of the flight schedule execution table is included within the range of the flight date value of the original record of the cancellation operation;

[0161] (4) The start time of the flight schedule execution table is equal to the start time of the original cancellation record;

[0162] (5) The end execution time of the flight schedule execution table is equal to the end execution time of the original cancellation record;

[0163] (6) Satisfying either of the following relationships: the time attribute of the flight schedule execution table is departure, and the value of the flight time field is equal to the departure time of the original record of the cancellation operation; or the time attribute of the flight schedule execution table is landing, and the value of the flight time field is equal to the landing time of the original record of the cancellation operation;

[0164] Each cancellation operation's original associated record is split into three records, as follows:

[0165] The start execution time of the retained records before the original association was cancelled = the start execution time of the original association records before the cancellation operation; the end execution time of the retained records before the original association was cancelled = the start time of cancellation - 1; the business type of the retained records before the original association was cancelled = new;

[0166] The start execution time of the original associated cancellation segment record = the start time of cancellation, the end execution time of the original associated cancellation segment record = the end time of cancellation, and the business type of the original associated cancellation segment record = cancellation;

[0167] The start execution time of the retained record after the original association is cancelled = the cancellation deadline + 1; the end execution time of the retained record after the original association is cancelled = the end execution time of the original association record after the cancellation operation; the business type of the retained record after the original association is cancelled = new.

[0168] The remaining fields of the three records, including flight time execution rate calculation group code, flight season, flight number, weekday, departure airport, arrival airport, flight time, and flight time attribute, are consistent with the original associated record information of the cancellation operation;

[0169] If the start time of a retained segment record before the original association is cancelled is later than the end time, the record is considered an abnormal record and is discarded; if the start time of a retained segment record after the original association is cancelled is later than the end time, the record is considered an abnormal record and is discarded.

[0170] Assigning values ​​to the time quantity field of the three records: Using the date interval weekday enumeration formula in step 13), the start date of the flight execution corresponding to the record is the calculation start date, the end date of the flight execution is the calculation end date (the end date is included), and the weekday field corresponding to the record is the target weekday. The total number of dates corresponding to the target weekday in the date interval is calculated and filled into the time quantity field.

[0171] 34) Remove the original record of the cancellation operation selected in step 31) of the airline slot application form; at the same time, enter and save the three records generated in step 32) as the application information submitted by the airline into the airline slot application form.

[0172] 35) Remove the original associated record of the cancellation operation obtained in step 33) from the flight schedule execution table; at the same time, split each original associated record of the cancellation operation in step 33) into three records and save them as new data to the flight schedule execution table;

[0173] 36) Delete the invalid records in step 35) where the number of flight slots in the flight schedule execution table is 0.

[0174] 4) Execute the flight slot return operation, select the original record for the return operation, and enter the start and end times; split the original record for the return operation and the related records obtained through matching and filtering into three segments, and complete the calculation and field filling of the flight slot quantity; based on the relationship between the remaining quantity and the flight slot quantity returned this time, change the business type or perform a second split on the return segment records; update the flight slot plan execution table and the airline slot application table; details are as follows:

[0175] 41) When performing flight slot return operations, select the record with the business type "New" in the airline slot application form and define this record as the original record for the return operation; enter the start time and end time corresponding to this return operation, wherein the start time and end time of the return are respectively within the start execution time and end execution time interval of the selected record; and the entered return start time and return end time must both be within the time interval formed by the start execution time and end execution time of the original record for the return operation.

[0176] 42) Based on the data entered in step 41), the original record of the handover operation is divided into three segments according to the start and end times of the handover: the pre-handover retention segment (first record), the handover segment (second record), and the post-handover retention segment (third record); as follows:

[0177] The start execution time of the record to be retained before being handed over is equal to the start execution time of the original record to be handed over. The end execution time of the record to be retained before being handed over is equal to the start time of the handover - 1. The business type of the record to be retained before being handed over is added.

[0178] The start execution time of the return segment record = the start time of the return; the end execution time of the return segment record = the end time of the return; the business type of the return segment record = return.

[0179] The start execution time of the retained record after the handover = the deadline for handover + 1; the end execution time of the retained record after the handover = the end execution time of the original record in the handover operation; the business type of the retained record after the handover = new.

[0180] The remaining fields of the three records, including flight season, flight number, flight schedule, departure airport, arrival airport, departure airport, departure time, arrival airport, and arrival time, are consistent with the information in the original records of the return operation.

[0181] If the start execution time of a record in the retained section before being handed over is later than the end execution time, the record is considered an abnormal record and is discarded; if the start execution time of a record in the retained section after being handed over is later than the end execution time, the record is considered an abnormal record and is discarded.

[0182] 43) Based on the original record of the handover operation selected in step 41), retrieve the flight schedule execution table to obtain the corresponding associated record, and define the record as the original associated record of the handover operation; then, according to the start time and end time of the handover, divide each original associated record of the handover operation into the original associated pre-handover retention segment (first record), the original associated handover segment (second record), and the original associated post-handover retention segment (third record);

[0183] The association rule between the flight schedule execution table and the original record of the handover operation must simultaneously meet the following matching conditions:

[0184] (1) The flight season in the flight schedule execution table is equal to the flight season in the original handover operation record;

[0185] (2) The flight number in the flight schedule execution table is equal to the flight number in the original return operation record;

[0186] (3) The weekday field value of the flight schedule execution table is included within the range of the flight date value of the original record of the return operation;

[0187] (4) The start time of the flight schedule execution table is equal to the start time of the original record of the return operation;

[0188] (5) The end execution time of the flight schedule execution table is equal to the end execution time of the original record of the return operation;

[0189] (6) Satisfying either of the following relationships: the time attribute of the flight schedule execution table is departure, and the value of the flight time field is equal to the departure time of the original record of the return operation; or the time attribute of the flight schedule execution table is landing, and the value of the flight time field is equal to the landing time of the original record of the return operation.

[0190] Each return operation splits the original associated record into three records, as follows:

[0191] The start execution time of the original associated record before the return is equal to the start execution time of the original associated record during the return operation. The end execution time of the original associated record before the return is equal to the start time of the return - 1. The business type of the original associated record before the return is equal to "new".

[0192] The start execution time of the original associated return segment record = the start time of the return; the end execution time of the original associated return segment record = the end time of the return; the business type of the original associated return segment record = return.

[0193] The start execution time of the retained record after the original association is returned = the deadline for return + 1; the end execution time of the retained record after the original association is returned = the end execution time of the original association record in the return operation; the business type of the retained record after the original association is returned = new.

[0194] The remaining fields of the three records, including the time execution rate calculation group code, flight season, flight number, day of the week, departure airport, arrival airport, flight time, and flight time attribute, are consistent with the original associated record information of the return operation.

[0195] If the start execution time of a record in the retained segment before the original association is returned is later than the end execution time, the record is considered an abnormal record and is discarded; if the start execution time of a record in the retained segment after the original association is returned is later than the end execution time, the record is considered an abnormal record and is discarded.

[0196] Assigning values ​​to the flight timetable field of the three records: Using the day-of-week enumeration formula for the date interval in step 13), the start date of the flight execution corresponding to the record is the calculation start date, the end date of the flight execution is the calculation end date (the end date is included), and the day-of-week field corresponding to the record is the target day of the week. The total number of dates corresponding to the target day of the date interval is calculated and filled into the flight timetable field.

[0197] 44) For each original associated return segment record in step 43), extract the flight slot execution rate of the record, calculate the group code, flight season, and flight slot quantity; fill the flight slot quantity field value into the planned return flight slot quantity. Where I represents the flight slot execution rate calculation group code; using this flight slot execution rate calculation group code and flight season as matching conditions, all records in the flight slot plan execution table with the business type "returned" are retrieved, and the flight slot quantity field values ​​of all retrieved records are summed, which is the returned flight slot quantity corresponding to the flight slot execution rate calculation group code. Search the flight slot return / return limit table for records based on flight season as the matching condition. If no record is found, proceed to step 48); otherwise, populate the return limit field value of the record. (Execute step 45).

[0198] 45) Calculate the remaining returnable flight slots based on the flight slot execution rate extracted in step 44) using the block code. , ;when At that time, for each original associated return segment record in step 43), update its business type field to cancel, and proceed to step 48). When, proceed to step 48); when and At that time, calculate the number of flight slots that cannot be returned (returned but cancelled). , (Execute step 46).

[0199] 46) For each original associated return segment record in step 43), further decompose it into two records: a record for retaining the return segment (the fourth record) and a record for turning the return segment into a cancellation segment (the fifth record), as follows:

[0200] The start execution time of the retained re-entry segment record = the start execution time of the original associated re-entry segment record; the end execution time of the retained re-entry segment record = the start execution time of the original associated re-entry segment record + ... The business type for retaining the return segment record is return, and the time period for retaining the return segment record is... ;

[0201] The start execution time of the surrender / cancel segment record = the start execution time of the original associated surrender segment record + The end execution time of the surrender / cancellation segment record = the end execution time of the original associated surrender segment record; the business type of the surrender / cancellation segment record = cancellation; the time limit of the surrender / cancellation segment record = ;

[0202] 47) Remove the original associated records of the handover operation obtained in step 43) from the flight schedule execution table; split each original associated record of the handover operation in step 43) to generate the original associated pre-handover retained segment record and the original associated post-handover retained segment record, and save the retained handover segment record and handover-to-cancellation segment record generated in step 46) as new data to the flight schedule execution table; delete the invalid records in the flight schedule execution table where the new data flight slot quantity is 0; after completion, proceed to step 49).

[0203] 48) Remove the original associated records of the handover operation obtained in step 43) from the flight schedule execution table; split each original associated record of the handover operation in step 43) into three records and save them as new data to the flight schedule execution table; delete the invalid records in the flight schedule execution table where the new data flight slot quantity is 0;

[0204] 49) Remove the original record of the return operation selected in step 41) of the airline slot application form; at the same time, enter and save the three records generated in step 42) as the application information submitted by the airline to the airline slot application form.

[0205] 5) Execute the flight slot return service, select the original return operation record, and enter the start and end times; split the original return operation record and the related records obtained through matching and filtering into three segments, and complete the calculation and field filling of the flight slot quantity; based on the relationship between the remaining amount and the flight slot quantity returned this time, change the business type or perform a second split on the return segment record; update the flight slot schedule execution table and the airline slot application table; details are as follows:

[0206] 51) When performing flight slot return service, select the record with the business type "new" in the airline slot application form and define the record as the original record of the return operation; enter the start time and end time corresponding to this return operation, and the entered return start time and return end time must be within the time interval formed by the start execution time and end execution time of the original record of the return operation.

[0207] 52) Based on the data entered in step 51), the original record of the return operation is divided into three segments according to the start and end times of the return: the pre-return retention segment (first record), the return segment (second record), and the post-return retention segment (third record); as follows:

[0208] The start execution time of the record to be retained before return is equal to the start execution time of the original record to be returned; the end execution time of the record to be retained before return is equal to the start time of return - 1; the business type of the record to be retained before return is added.

[0209] The start execution time of the return segment record = the start time of return; the end execution time of the return segment record = the end time of return; the business type of the return segment record = return.

[0210] The start execution time of the record to be retained after return = the deadline for return + 1; the end execution time of the record to be retained after return = the end execution time of the original record for return; the business type of the record to be retained after return = new.

[0211] The remaining fields of the three records, including flight season, flight number, flight schedule, departure airport, arrival airport, departure airport, departure time, arrival airport, and arrival time, are consistent with the information in the original return operation record.

[0212] If the start execution time of a record in the pre-returned retained segment is later than the end execution time, the record is considered an abnormal record and is discarded; if the start execution time of a record in the post-returned retained segment is later than the end execution time, the record is considered an abnormal record and is discarded.

[0213] 53) Based on the original record of the return operation selected in step 51), retrieve the flight schedule execution table to obtain the corresponding associated record, and define the record as the original associated record of the return operation; then, according to the start time and end time of the return, divide each original associated record of the return operation into the original associated record before return (the first record), the original associated record after return (the second record), and the original associated record after return (the third record);

[0214] The association rule between the flight schedule execution table and the original return operation record must simultaneously meet the following matching conditions:

[0215] (1) The flight season in the flight schedule execution table is equal to the flight season in the original record of the return operation;

[0216] (2) The flight number in the flight schedule execution table is equal to the flight number in the original record of the return operation;

[0217] (3) The weekday field value of the flight schedule execution table is included within the range of the flight date value of the original record of the return operation;

[0218] (4) The start time of the flight schedule execution table is equal to the start time of the original record of the return operation;

[0219] (5) The end execution time of the flight schedule execution table is equal to the end execution time of the original record of the return operation;

[0220] (6) Satisfying either of the following relationships: the time attribute of the flight schedule execution table is departure, and the time field value is equal to the departure time of the original record of the return operation; or the time attribute of the flight schedule execution table is landing, and the time field value is equal to the landing time of the original record of the return operation.

[0221] Each return operation's original associated record is split into three records, as follows:

[0222] The start execution time of the original associated record before return = the start execution time of the original associated record of the return operation; the end execution time of the original associated record before return = the start time of return - 1; the business type of the original associated record before return = -new.

[0223] The start execution time of the original associated return segment record = the start time of return; the end execution time of the original associated return segment record = the end time of return; the business type of the original associated return segment record = return.

[0224] The start execution time of the original associated record after return = the end time of return + 1; the end execution time of the original associated record after return = the end execution time of the original associated record of the return operation; the business type of the original associated record after return = new.

[0225] The remaining fields of the three records, including the execution rate calculation group code, flight season, flight number, day of the week, departure airport, arrival airport, flight time, and flight time attribute, are consistent with the original associated record information of the return operation.

[0226] If the start execution time of a record in the retained segment before the original association is returned is later than the end execution time, the record is considered an abnormal record and is discarded; if the start execution time of a record in the retained segment after the original association is returned is later than the end execution time, the record is considered an abnormal record and is discarded.

[0227] Assigning values ​​to the flight timetable field of the three records: Using the day-of-week enumeration formula for the date interval in step 13), the start date of the flight execution corresponding to the record is the calculation start date, the end date of the flight execution is the calculation end date (the end date is included), and the day-of-week field corresponding to the record is the target day of the week. The total number of dates corresponding to the target day of the date interval is calculated and filled into the flight timetable field.

[0228] 54) For each original associated return segment record in step 53), extract the flight slot execution rate of the record, calculate the group code, flight season, and flight slot quantity; fill the flight slot quantity field value into the planned return flight slot quantity. Where I represents the flight slot execution rate calculation group code; simultaneously, using this flight slot execution rate calculation group code and flight season as matching conditions, all records in the flight slot plan execution table with the business type of "return" are retrieved, and the sum of the flight slot quantity field values ​​of all retrieved records is the returned flight slot quantity corresponding to this flight slot execution rate calculation group code. Using flight season as the matching criterion, retrieve records from the flight slot return / refund limit table. If no record is found, proceed to step 58); otherwise, populate the return limit field value of the record. (Execute step 55).

[0229] 55) Calculate the remaining returnable flight slots based on the flight slot execution rate extracted in step 54) using the block code. , ;when At that time, for each original associated return segment record in step 53), update its business type field to cancel, and execute step 58); when and When, execute step 58); when and At that time, the number of flight slots that cannot be returned (returned but cancelled) is calculated. , (Execute step 56).

[0230] 56) For each original associated return segment record in step 53), further decompose it into two records: a record for retaining the return segment (the fourth record) and a record for converting the return to a cancellation segment (the fifth record), as follows:

[0231] The start execution time of the retained return segment record = the start execution time of the original associated return segment record; the end execution time of the retained return segment record = the start execution time of the original associated return segment record + ... The business type for retaining return segment records is = return, and the time period for retaining return segment records is = ;

[0232] The start execution time of the return-to-cancellation segment record = the start execution time of the original associated return segment record + The end execution time of the return-to-cancellation segment record = the end execution time of the original associated return segment record; the business type of the return-to-cancellation segment record = cancellation; the time interval of the return-to-cancellation segment record = .

[0233] 57) Remove the original associated records of the return operation obtained in step 53 from the flight schedule execution table; save the original associated return pre-return retained segment and original associated return post-return retained segment records generated by splitting each original associated record of the return operation in step 53), as well as the retained return segment record and return-to-cancellation segment record generated in step 56), as new data to the flight schedule execution table; delete the invalid records in the flight schedule execution table where the new data flight slot quantity is 0; after completion, proceed to step 59).

[0234] 58) Remove the original associated records of the return operation obtained in step 53) from the flight schedule execution table; split each original associated record of the return operation in step 53) into three records and save them as new data to the flight schedule execution table; delete the invalid records in the table where the new data flight slot quantity is 0;

[0235] 59) Remove the original record of the return operation selected in step 51) from the airline slot application form; at the same time, enter and save the three records generated in step 52) as the application information submitted by the airline to the airline slot application form.

[0236] 6) Periodically migrate the flight schedule execution records from the previous day (Date) in the flight schedule execution table to the actual flight schedule execution table; then perform correlation matching based on the actual flight execution data and update the flight execution status; for unexecuted flight records, adjust the flight execution status after review and approval; details are as follows:

[0237] 61) Configure a scheduled data synchronization task to perform data migration at a fixed time each day (e.g., 2 AM): Filter out all records in the flight schedule execution table whose scheduled execution date is the previous day, and migrate this data completely to the actual flight schedule execution table. The specific steps are as follows:

[0238] 611) Define the parameter Date as the previous day's date, with a value one day less than the current system date; query the flight schedule execution table to find all flight data records where the parameter Date falls within the interval of the record's start and end execution times; iterate through each query result, using the start execution time of a single record as the date calculation start time and the end execution time as the date calculation end time (the calculation interval includes the end time), match the corresponding weekday field parameter of the record, and use the date interval weekday enumeration formula from step 13) to generate all specific dates within the time interval that meet the target weekday requirements, and integrate them to form a date list F;

[0239] 612) Determine if Date exists in the specific date list F corresponding to each record obtained in step 611). If Date exists in date list F, then transfer the record from the flight schedule execution table to the actual flight schedule execution table. The field mapping rules are as follows:

[0240] The group code for calculating the flight schedule execution rate in the actual flight schedule execution table is equal to the group code for calculating the flight schedule execution rate in the planned flight schedule execution table.

[0241] The actual flight schedule season equals the scheduled flight schedule season.

[0242] The flight number in the actual flight schedule execution table equals the flight number in the planned flight schedule execution table;

[0243] The week of the actual flight schedule is equal to the week of the scheduled flight schedule.

[0244] The departure airport in the actual flight schedule is equal to the departure airport in the planned flight schedule.

[0245] The actual airport of arrival in the flight schedule = the airport of arrival in the flight schedule plan.

[0246] The actual execution time in the flight schedule equals the time in the planned execution time in the flight schedule.

[0247] The time attribute of the actual flight schedule execution table is equal to the time attribute of the planned flight schedule execution table.

[0248] The actual execution time of the flight schedule execution table = Date;

[0249] The business category in the actual flight schedule execution table equals the business category in the planned flight schedule execution table.

[0250] If the business category field value of the flight schedule execution table is "return" or "refund", the execution category of the actual flight schedule execution table will be "executed"; otherwise, the execution category of the actual flight schedule execution table will be "not executed".

[0251] 62) Extract key information from the previous day's (Date) flight execution data, specifically including: flight number, planned departure airport, actual departure airport, planned arrival airport, actual arrival airport, planned execution date, and actual execution date; for supplementary flights, the flight number format conversion needs to be completed in advance, and the specific conversion rules are as follows:

[0252] Character-number mapping rules: The letters Z, Y, X, W, V, U, T, S, R, and Q in the flight number are replaced with the numbers 0, 1, 2, 3, 4, 5, 6, 7, 8, and 9 respectively.

[0253] Rules for tracing the dates of make-up flights: If the last character of the flight number is a letter, the make-up flight corresponds to the original flight of the previous day; if the second to last character of the flight number is a letter, the make-up flight corresponds to the original flight of the previous two days.

[0254] 63) Perform a line-by-line matching operation between the actual flight execution data in step 62) and the records in the actual execution table of transfer flight times in step 61). The matching and field update are performed in two steps, as follows:

[0255] 631) Takeoff end matching;

[0256] A match is considered successful if and only if all of the following conditions are met:

[0257] The actual flight number in the flight execution data matches the flight number recorded in the actual flight schedule execution table.

[0258] The planned departure airport in the actual flight execution data is consistent with the departure airport recorded in the actual flight schedule.

[0259] The actual flight schedule execution table records flight schedules with the attribute set to "departure";

[0260] The actual execution date of the flight execution data is consistent with the actual execution time recorded in the flight schedule execution table.

[0261] Once a match is successful, update the execution category field value of the corresponding record in the actual execution table of flight times to "executed".

[0262] 632) Landing end matching;

[0263] A match is considered successful if and only if all of the following conditions are met:

[0264] The actual flight number in the flight execution data matches the flight number recorded in the actual flight schedule execution table.

[0265] The planned landing airport in the actual flight execution data is consistent with the landing airport recorded in the actual flight schedule.

[0266] The actual flight schedule execution table records a flight schedule with the attribute of "landing";

[0267] The actual execution date of the flight execution data is consistent with the actual execution time recorded in the flight schedule execution table.

[0268] Once a match is successful, update the execution category field value of the corresponding record in the actual execution table of flight times to "executed".

[0269] 64) For flight records marked as not executed in the actual execution schedule, the airline shall enter the corresponding supporting information and reasons for the appeal; after the review is completed and the review result is approved, the flight execution category corresponding to the flight record shall be changed from not executed to executed;

[0270] 641) By querying the actual execution table, the airline can fill in the following information in the appeal reason field of the record: the reason for the appeal (such as force majeure, air traffic control reasons, airport reasons, etc.) and a brief description of the event.

[0271] 642) Review the appeal and related evidence submitted by the airline: if the reasons are valid (e.g., force majeure), the review will be approved and the execution category of the record will be updated to executed; otherwise, if the reasons are invalid or the evidence is insufficient, the review will not be approved.

[0272] 7) Monitor flight schedule execution in real time during the flight season, calculate group codes based on flight schedule execution rate, and separately statistically analyze the actual and predicted flight schedule execution data to calculate the execution rate for group code I during the flight season. and the current season's slot availability forecast. Then, the predicted execution rate is compared with the current flight season's preset warning line YJX and alarm line GJX in sequence. Based on the comparison results, alarm prompts, warning prompts, or no prompt information are sent to the corresponding airlines, as detailed below:

[0273] 71) During the current flight season, track flight schedule execution in real time and calculate real-time flight schedule execution data; from the actual flight schedule execution table, calculate group codes based on flight schedule execution rate, and categorize and statistically analyze the flight schedule execution details corresponding to each group code; among which,

[0274] Flight slots to be executed The calculation is as follows: Filter the actual flight schedule execution table, select all valid flight data records with flight schedule execution rate calculation group code I and belonging to the current flight season, count the total number of records that meet the above filtering conditions, and the statistical result is the number of flight schedules to be executed for the corresponding group code I;

[0275] Flight slots already executed The calculation is as follows: Filter the actual execution table of flight schedules, select all data records with flight schedule execution rate calculation group code I, flight season is the current flight season and execution category is executed, count the total number of records that meet all the above conditions, and the count value is the number of executed flight schedules corresponding to group code I;

[0276] Return of already executed flight slots The calculation is as follows: Filter the actual execution table of flight slots, and select all data records with flight slot execution rate calculation group code I, flight season as the current flight season, execution category as executed and business category as returned. Count the total number of records that meet all the above filtering conditions. The statistical result is the amount of returned executed flight slots corresponding to group code I.

[0277] Execution rate during the corresponding flight season for block code I The specific formula is:

[0278] ;

[0279] 72) During the current flight season, the execution of flight schedules will be tracked in real time, and the expected execution data for flight schedules in the current flight season will be predicted; the details are as follows:

[0280] Flight slots to be implemented in the current flight season The calculation is as follows: Filter the flight schedule execution table, select all data records with flight schedule execution rate calculation group code I and the current flight season, and calculate the total number of flight slots corresponding to all records that meet the filtering conditions. The calculated value is the number of flight slots that should be executed in the current flight season for the corresponding group code I.

[0281] Currently unused flight slots The calculation is as follows: Filter the actual execution table of flight schedules, select all data records with flight schedule execution rate calculation group code I, flight season is the current flight season and execution category is non-executed, count the total number of records that meet all the above filtering conditions, and the count value is the current non-executed flight schedule for the corresponding group code I;

[0282] Predicted current season slot fulfillment rate corresponding to block code I The specific formula is:

[0283] ;

[0284] 73) The current season's slot availability forecast. The system calculates and issues warnings based on the warning line (YJX) and alarm line (GJX) defined in the flight schedule execution rate warning / alarm table. If the criteria are met, a notification regarding the flight schedule execution status is sent to the corresponding airline. The specific criteria and notification rules are as follows:

[0285] 731) Extract the warning and alarm line parameters that have been set for the current flight season, and use them as the core benchmark for judging abnormal flight schedule execution rates. The extraction process must ensure that the parameters correspond to the current flight season.

[0286] 732) Determine the predicted value of the current flight season's slot execution rate. If the threshold is less than the warning threshold, the warning / alarm calculation process is terminated, and the airline is notified of the relevant alarm information: the flight schedule execution rate corresponding to group code I cannot meet the prescribed standard by the end of the flight season; if the threshold is not met, proceed to step 733).

[0287] 733) Determine the predicted value of the current flight season's slot execution rate. If the threshold is lower than the warning line, and the condition is met, a warning message will be sent to the airline: if subsequent flight schedules are not executed, the flight schedule execution rate corresponding to group code I may not meet the prescribed standard by the end of the flight season; if the condition is not met, no message needs to be sent to the airline.

[0288] 8) Calculate the actual flight schedule execution rate at the end of the flight season and compare it with the preset alarm threshold for the current flight season. When the actual execution rate is lower than the alarm threshold, push the data to the corresponding airline; the details are as follows:

[0289] 81) Calculate the actual execution rate of flight schedules for the current flight season using group code I. The calculation formula is:

[0290] ;

[0291] 82) The actual execution rate of flight times corresponding to each group code for this flight season. The alarm threshold for this flight season is compared with the pre-set alarm threshold in the flight schedule execution rate warning table; if If the data falls below the alarm threshold, the abnormal flight data will be sent to the corresponding airline.

[0292] This invention has many specific applications. The above description is only a preferred embodiment of this invention. It should be noted that for those skilled in the art, several improvements can be made without departing from the principle of this invention, and these improvements should also be considered within the scope of protection of this invention.

Claims

1. A dynamic management method for the entire lifecycle of flight slots based on execution rate prediction, characterized in that, The steps include the following: 1) Construct the core table system and the formula for enumerating the day of the week for each date range; 2) Receive the application information from the airline, and sequentially complete the splitting of flight time / flight time attribute and flight period / week dimension; for the split records, fill in the execution rate group code, flight time quantity, and business type fields respectively to generate a complete flight time plan execution table; 3) To perform a flight cancellation, select the original cancellation record and enter the start and end times of the cancellation. The original cancellation operation record and the original cancellation operation related record in the flight schedule execution table that match the association conditions are split into three segments, and the execution start and end time and business type of each record are configured respectively; the flight schedule quantity field of the three split records is populated. 4) Perform flight time slot return service, select the original record for return operation, and enter the start and end times; The original records of the handover operation and the original related records of the handover operation obtained by matching and filtering are split into three segments to complete the calculation of flight slot quantity and field filling; based on the relationship between the remaining quantity and the flight slot quantity of this handover, the business type of the handover segment records is changed or split again; the flight slot plan execution table and the airline slot application table are updated. 5) To perform flight time slot return service, select the original record for the return operation and enter the start and end times; The original record of the return operation and the original related record of the return operation obtained by matching and filtering are split into three segments to complete the calculation of flight time slots and field filling; based on the relationship between the remaining amount and the flight time slots returned this time, the business type of the return segment record is changed or split again; the flight time slot plan execution table and the airline time slot application table are updated. 6) Periodically migrate the flight schedule execution records from the previous day in the flight schedule execution table to the actual flight schedule execution table; then perform correlation matching based on the actual flight execution data and update the flight execution status; for unexecuted flight records, adjust the flight execution status after review and approval; 7) Calculate the execution rate during the flight season and the predicted execution rate for the current flight season according to the group code of the flight schedule execution rate. Then compare the predicted execution rate with the preset warning line and alarm line for the current flight season in turn, and push the prompt information to the corresponding airline based on the comparison results. 8) Calculate the actual flight schedule execution rate at the end of the flight season and compare the execution rate with the preset alarm threshold for the flight season. When the actual execution rate is lower than the alarm threshold, push the data to the corresponding airline.

2. The method for dynamic management of flight slots throughout their entire lifecycle based on execution rate prediction as described in claim 1, characterized in that, Step 1) specifically includes: 11) Establish a flight schedule execution table, whose specific data items include: flight schedule execution rate calculation group code, flight season, flight number, day of the week, departure airport, arrival airport, flight time, flight time attribute, start execution time, end execution time, business type and flight time volume; 12) Establish an airline slot application form, the specific data information of which includes: flight season, flight number, flight schedule, departure airport, departure time, arrival airport, arrival time, start time, end time, and business type; 13) Establish a formula for enumerating the weekdays for a date range to simultaneously calculate the total number of dates corresponding to the target weekday and the specific date list; 14) Establish a flight slot return / refund quota table, whose specific data items include: flight season, return quota and refund quota; and follow the uniqueness rule: only one quota record can exist in the table for a single flight season; 15) Establish a flight schedule execution table, whose specific data items include: schedule execution rate calculation group code, flight season, flight number, day of the week, departure airport, arrival airport, flight schedule, flight schedule attribute, actual execution time, business category, execution category and appeal reason; 16) Establish a flight schedule execution rate early warning / alarm table, whose specific data items include: flight season, early warning line, and alarm line; and follow the uniqueness rule: only one record can exist in the table for a single flight season.

3. The method for dynamic management of flight slots throughout their entire lifecycle based on execution rate prediction according to claim 2, characterized in that, Step 13) specifically includes: 131) Define S as the start date, E as the end date, and T as the target weekday; 132) Calculate the weekday W of the starting date using the Zeller formula. S The week of the end date E ; 133) Calculate the total number of days D from the start date to the end date. C The details are as follows: ； 134) Calculate the first target date between the start date and the end date. The details are as follows: ； Where mod represents the remainder operation; 135) Calculate the total number N of dates corresponding to the target week, as follows: ； in, Indicates rounding down; when N=0, it is a list of specific dates corresponding to the target weekday. If empty; otherwise, the specific date list F corresponding to the target weekday is: ； Among them, F N This represents the Nth target date between the start date and the end date.

4. The method for dynamic management of flight slots throughout their entire lifecycle based on execution rate prediction according to claim 1, characterized in that, Step 2) specifically includes: 21) Receive the slot application data submitted by the airline and enter the application data into the airline slot application form. The application information includes: flight season, flight number, flight schedule, departure airport, departure time, arrival airport, arrival time, start time, end time and business type. 22) Based on the airline slot application information obtained in step 21), the flight slot / slot attribute and flight period / week dimension are split in sequence according to the flight slot execution rate calculation grouping rules; for each record after splitting, the execution rate calculation group code, flight slot quantity and business type fields are filled in respectively, and the processed valid records are stored in the flight slot plan execution table. 23) Delete invalid records in step 22) where the flight time slot quantity is 0 in the flight time slot plan execution table. If the time slot quantity of all records in step 22) in the flight time slot plan execution table is 0, delete the records in step 21) in the airline time slot application form.

5. The method for dynamic management of flight slots throughout their entire lifecycle based on execution rate prediction according to claim 1, characterized in that, Step 3) specifically includes: 31) When performing flight slot cancellation, select the record with the business type "New" in the airline slot application form and define the record as the original record for the cancellation operation; enter the start time and end time corresponding to this cancellation operation, and the entered cancellation start time and cancellation end time must be within the time interval formed by the start execution time and end execution time of the original record for the cancellation operation; 32) Based on the data entered in step 31), the original record of the cancellation operation is split into a pre-cancellation retention segment record, a cancellation segment record, and a post-cancellation retention segment record according to the start and end times of the cancellation; 33) Based on the original record of the cancellation operation selected in step 31), retrieve the flight schedule execution table to obtain the corresponding associated record, and define the associated record as the original associated record of the cancellation operation; then, according to the start time and end time of the cancellation, divide each original associated record of the cancellation operation into the original associated record before cancellation, the original associated record after cancellation, and the original associated record after cancellation. 34) Remove the original record of the cancellation operation selected in step 31) of the airline slot application form; at the same time, enter and save the three records generated in step 32) as the application information submitted by the airline into the airline slot application form. 35) Remove the original associated record of the cancellation operation obtained in step 33) from the flight schedule execution table; at the same time, split each original associated record of the cancellation operation in step 33) into three records and save them as new data to the flight schedule execution table; 36) Delete the invalid records in step 35) where the number of flight slots in the flight schedule execution table is 0.

6. The method for dynamic management of flight slots throughout their entire lifecycle based on execution rate prediction according to claim 1, characterized in that, Step 4) specifically includes: 41) When performing flight slot return operations, select the record with the business type "New" in the airline slot application form and define this record as the original record for the return operation; enter the start time and end time corresponding to this return operation, wherein the start time and end time of the return are respectively within the start execution time and end execution time interval of the selected record; and the entered return start time and return end time must both be within the time interval formed by the start execution time and end execution time of the original record for the return operation. 42) Based on the data entered in step 41), the original record of the handover operation is divided into the pre-handover retention segment record, the handover segment record, and the post-handover retention segment record according to the start and end times of the handover. 43) Based on the original record of the handover operation selected in step 41), retrieve the flight schedule execution table to obtain the corresponding associated record, and define the record as the original associated record of the handover operation; then, according to the start time and end time of the handover, divide each original associated record of the handover operation into the original associated pre-handover retention segment record, the original associated handover segment record, and the original associated post-handover retention segment record. 44) For each original associated return segment record in step 43), extract the flight slot execution rate of the record, calculate the group code, flight season, and flight slot quantity; fill the flight slot quantity field value into the planned return flight slot quantity. Where I represents the flight slot execution rate calculation group code; using this flight slot execution rate calculation group code and flight season as matching conditions, all records in the flight slot plan execution table with the business type "returned" are retrieved, and the flight slot quantity field values ​​of all retrieved records are summed, which is the returned flight slot quantity corresponding to the flight slot execution rate calculation group code. Search the flight slot return / return limit table for records based on flight season as the matching condition. If no record is found, proceed to step 48); otherwise, populate the return limit field value of the record. (Execute step 45). 45) Calculate the remaining returnable flight slots based on the flight slot execution rate extracted in step 44) using the block code. , ;when At that time, for each original associated return segment record in step 43), update its business type field to cancel, and proceed to step 48). When, proceed to step 48); when and At that time, the number of flight slots that cannot be returned this time is calculated. , (Execute step 46). 46) For each original associated return segment record in step 43), further decompose it into two records: a record for retaining the return segment and a record for turning the return segment into a cancellation segment. 47) Remove the original associated records of the handover operation obtained in step 43) from the flight schedule execution table; split each original associated record of the handover operation in step 43) to generate the original associated pre-handover retained segment record and the original associated post-handover retained segment record, and save the retained handover segment record and handover-to-cancellation segment record generated in step 46) as new data to the flight schedule execution table; delete the invalid records in the flight schedule execution table where the new data flight slot quantity is 0; after completion, proceed to step 49). 48) Remove the original associated records of the handover operation obtained in step 43) from the flight schedule execution table; split each original associated record of the handover operation in step 43) into three records and save them as new data to the flight schedule execution table; delete the invalid records in the flight schedule execution table where the new data flight slot quantity is 0; 49) Remove the original record of the return operation selected in step 41) of the airline slot application form; at the same time, enter and save the three records generated in step 42) as the application information submitted by the airline to the airline slot application form.

7. The method for dynamic management of flight slots throughout their entire lifecycle based on execution rate prediction according to claim 1, characterized in that, Step 5) specifically includes: 51) When performing flight slot return service, select the record with the business type "new" in the airline slot application form and define the record as the original record of the return operation; enter the start time and end time corresponding to this return operation, and the entered return start time and return end time must be within the time interval formed by the start execution time and end execution time of the original record of the return operation. 52) Based on the data entered in step 51), the original record of the return operation is divided into a pre-return retention record, a return record, and a post-return retention record according to the start and end times of the return. 53) Based on the original record of the return operation selected in step 51), retrieve the flight schedule execution table to obtain the corresponding associated record, and define the record as the original associated record of the return operation; then, according to the start time and end time of the return, divide each original associated record of the return operation into the original associated record before return, the original associated record after return, and the original associated record after return. 54) For each original associated return segment record in step 53), extract the flight slot execution rate of the record, calculate the group code, flight season, and flight slot quantity; fill the flight slot quantity field value into the planned return flight slot quantity. Where I represents the flight slot execution rate calculation group code; simultaneously, using this flight slot execution rate calculation group code and flight season as matching conditions, all records in the flight slot plan execution table with the business type of "return" are retrieved, and the sum of the flight slot quantity field values ​​of all retrieved records is the returned flight slot quantity corresponding to this flight slot execution rate calculation group code. Using flight season as the matching criterion, retrieve records from the flight slot return / refund limit table. If no record is found, proceed to step 58); otherwise, populate the return limit field value of the record. (Execute step 55). 55) Calculate the remaining returnable flight slots based on the flight slot execution rate extracted in step 54) using the block code. , ;when At that time, for each original associated return segment record in step 53), update its business type field to cancel, and execute step 58); when and When, execute step 58); when and At that time, the number of flight slots that cannot be returned this time is calculated. , (Execute step 56). 56) For each original associated return segment record in step 53), further decompose it into two records: a record to retain the return segment and a record to convert the return segment to a cancellation segment. 57) Remove the original associated records of the return operation obtained in step 53 from the flight schedule execution table; save the original associated return pre-return retained segment and original associated return post-return retained segment records generated by splitting each original associated record of the return operation in step 53), as well as the retained return segment record and return-to-cancellation segment record generated in step 56), as new data to the flight schedule execution table; delete the invalid records in the flight schedule execution table where the new data flight slot quantity is 0; after completion, proceed to step 59). 58) Remove the original associated records of the return operation obtained in step 53) from the flight schedule execution table; split each original associated record of the return operation in step 53) into three records and save them as new data to the flight schedule execution table; delete the invalid records in the table where the new data flight slot quantity is 0; 59) Remove the original record of the return operation selected in step 51) from the airline slot application form; at the same time, enter and save the three records generated in step 52) as the application information submitted by the airline to the airline slot application form.

8. The method for dynamic management of flight slots throughout their entire lifecycle based on execution rate prediction according to claim 1, characterized in that, Step 6) specifically includes: 61) Configure a scheduled data synchronization task to perform data migration operations at a fixed time H every day: Filter out all records in the flight schedule execution table whose scheduled execution date is the previous day, and migrate the data completely to the actual flight schedule execution table; 62) Extract key information from the previous day's actual flight execution data, specifically including: flight number, planned departure airport, actual departure airport, planned arrival airport, actual arrival airport, planned execution date, and actual execution date; for supplementary flights, the flight number format conversion needs to be completed in advance; 63) Perform a line-by-line matching operation between the actual flight execution data in step 62) and the records in the actual execution table of transfer flight times in step 61), and perform the matching and field update in two steps; 64) For flight records marked as not executed in the actual execution table of flight schedules, enter the corresponding appeal supporting information and the reason for the appeal; after the review is completed and the review result is determined to be passed, change the flight execution category corresponding to the flight record from not executed to executed.

9. The method for dynamic management of flight slots throughout their entire lifecycle based on execution rate prediction according to claim 1, characterized in that, Step 7) specifically includes: 71) During the current flight season, track the flight schedule execution status in real time and calculate the real-time flight schedule execution data; calculate group codes based on the flight schedule execution rate from the actual flight schedule execution table, and classify and statistically analyze the flight schedule execution details corresponding to each group code; 72) During the current flight season, track the flight schedule execution status in real time and predict the expected flight schedule execution data for the current flight season; 73) The current season's slot availability forecast. The system calculates warnings and alarms based on the warning and alarm lines defined in the flight schedule execution rate warning / alarm table. If the judgment conditions are met, the system sends relevant prompts on the flight schedule execution status to the corresponding airline.

10. The method for dynamic management of flight slots throughout their entire lifecycle based on execution rate prediction according to claim 1, characterized in that, Step 8) specifically includes: 81) Calculate the actual execution rate of flight schedules for the current flight season using group code I. The calculation formula is: ； 82) The actual execution rate of flight times corresponding to each group code for this flight season. The alarm threshold for this flight season is compared with the pre-set alarm threshold in the flight schedule execution rate warning table; if If the data falls below the alarm threshold, the abnormal flight data will be sent to the corresponding airline.

Images