Flight channel adjustment method and device

Abstract

The invention discloses a flight channel adjustment method and device, relates to the technical field of flight channel adjustment, and aims to obtain flight channel data only by automatically counting flight scheduling data without depending on manual channel reservation and statistics. According to the flight channel data, whether available maintenance channels of aircrafts in overnight bases without maintenance capacity meet future regular check requirements or not can be automatically and quickly counted, and the maintenance channels are determined according to the aircraft type base maintenance information and the flight channel data. Maintenance channel marks are marked on flight lines related to connection change after evaluation in a maintenance channel, channel evaluation is closer to the real operation condition by comprehensively considering actual constraints such as aircraft types, station-crossing time and aircraft exchangeability, misjudgment is reduced, and therefore in flight plan arrangement, the reliability of flight planning is improved. And enough flight maintenance channels can be quickly and accurately reserved for aircrafts of the same type in an overnight base without maintenance capability.

Description

Technical Field

[0001] This application relates to the field of flight channel adjustment technology, and more specifically, to a flight channel adjustment method and apparatus. Background Technology

[0002] In airline operations, regular aircraft maintenance is a mandatory and planned core task. Due to the concentration of maintenance capabilities, a large number of aircraft are stationed daily at overnight bases scattered across the country and even the world that lack large-scale scheduled maintenance capabilities.

[0003] To ensure that aircraft can return to the maintenance base on time, specific ferry flights, or aircraft maintenance channels, need to be planned in advance in the long-term flight schedule. Typically, one channel is reserved for every three aircraft of the same type for ferry maintenance.

[0004] Current methods for reserving flight maintenance access routes primarily rely on manual methods for reservation and statistics. Since airline flight plans involve hundreds of aircraft and tens of thousands of flight segments, spanning planning periods of several months or even longer, manual reservation and statistics are inefficient and struggle to guarantee data consistency and overall visibility. When maintenance plans change, flight schedules are adjusted, or aircraft are reassigned, extensive manual calculations and verifications are required, leading to slow response times and reduced decision-making efficiency and plan iteration. Furthermore, relying on manual reservation and statistics fails to adequately consider actual operational constraints such as aircraft type differences, flight turnaround times, the possibility of aircraft reassignment, and specific flight segment time occupancy, resulting in discrepancies between the results and actual conditions.

[0005] Therefore, how to quickly and accurately reserve sufficient flight maintenance channels for aircraft of the same type at overnight bases without maintenance capabilities in flight scheduling is an urgent problem that this application needs to solve. Summary of the Invention

[0006] In view of this, this application discloses a flight channel adjustment method and apparatus, which aims to quickly and accurately reserve sufficient flight maintenance channels for aircraft of the same type at overnight bases without maintenance capabilities during flight scheduling.

[0007] To achieve the above objectives, the disclosed technical solution is as follows:

[0008] The first aspect of this application discloses a method for adjusting flight channels, the method comprising:

[0009] Obtain aircraft type base maintenance information and flight scheduling data; wherein, the aircraft type base maintenance information includes information on whether the flight's landing airport is in the maintenance access base list and information on whether the base supports aircraft type maintenance;

[0010] The flight scheduling data is statistically analyzed to obtain flight channel data;

[0011] By using the aircraft type base maintenance information and the flight channel data, maintenance channels are determined, and routes involving connection changes after evaluation are marked with maintenance channel identifiers.

[0012] A second aspect of this application discloses a flight channel adjustment device, the device comprising:

[0013] The acquisition unit is used to acquire aircraft type base maintenance information and flight scheduling data; wherein, the aircraft type base maintenance information is used to determine whether the flight's landing airport is in the maintenance channel base list, and to determine whether the base supports aircraft type maintenance;

[0014] The statistics unit is used to perform statistics on the flight scheduling data to obtain flight channel data;

[0015] The determination unit is used to determine the maintenance channel through the aircraft base maintenance information and the flight channel data, and to mark the routes involving connection changes in the maintenance channel with maintenance channel identifiers after evaluation.

[0016] As can be seen from the above technical solution, this application discloses a method and apparatus for adjusting flight channels, which obtains aircraft type base maintenance information and flight scheduling data; wherein, the aircraft type base maintenance information is used to determine whether the airport where the flight lands is in the maintenance channel base list and to determine the information on the base supporting aircraft type maintenance, the flight scheduling data is statistically analyzed to obtain flight channel data, and the maintenance channel is determined by using the aircraft type base maintenance information and the flight channel data, and the routes involving connection changes in the maintenance channel after evaluation are marked with maintenance channel identification. This solution eliminates the need for manual channel reservation and statistics. Instead, it automatically analyzes flight scheduling data to obtain channel information. Based on this data, it can automatically and quickly assess whether available maintenance channels meet future scheduled maintenance needs for aircraft at overnight bases without maintenance capabilities. By combining aircraft type and base maintenance information with flight channel data, maintenance channels are determined. Routes involving connection changes within the assessed maintenance channels are marked with maintenance channel identifiers. By comprehensively considering practical constraints such as aircraft type, turnaround time, and aircraft interchangeability, channel assessments more closely reflect real-world operational conditions, reducing misjudgments. This allows for the rapid and accurate reservation of sufficient maintenance channels for aircraft of the same type at overnight bases without maintenance capabilities during flight scheduling. Ultimately, this ensures aircraft can fly to maintenance bases on time for scheduled maintenance, avoiding maintenance delays or flight schedule conflicts due to insufficient channels. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0018] Figure 1 This is a flowchart illustrating a flight channel adjustment method disclosed in an embodiment of this application;

[0019] Figure 2 This is an example diagram of the flight rescheduling channel disclosed in the embodiments of this application;

[0020] Figure 3 This is the overall call timing diagram disclosed in the embodiments of this application;

[0021] Figure 4 This is a timing diagram illustrating the concurrent execution of the calculation of the number of overnight aircraft by a thread pool, as disclosed in an embodiment of this application.

[0022] Figure 5 This is a schematic diagram illustrating the detailed channel type determination and statistical process disclosed in the embodiments of this application;

[0023] Figure 6 This is a flowchart illustrating another flight channel adjustment method disclosed in an embodiment of this application;

[0024] Figure 7 This is a schematic diagram of the structure of a flight channel adjustment device disclosed in an embodiment of this application. Detailed Implementation

[0025] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0026] In this application, the terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0027] As the background technology shows, existing methods for reserving passageways mainly rely on manual reservation and statistics, which leads to low efficiency. Furthermore, relying on manual reservation and statistics fails to fully consider actual operational constraints such as differences in aircraft type, flight turnaround times, the possibility of aircraft changes, and the time occupied by specific flight segments, resulting in discrepancies between the results and the actual situation.

[0028] To address the aforementioned issues, this application discloses a method and apparatus for adjusting flight channels. This method eliminates the need for manual channel reservation and statistics; it automatically analyzes flight scheduling data to obtain flight channel data. Based on this data, it can automatically and quickly assess whether available maintenance channels for aircraft at overnight bases without maintenance capabilities meet future scheduled maintenance requirements. Maintenance channels are determined using aircraft type and base maintenance information, along with flight channel data. Routes involving connection changes within the assessed maintenance channels are marked with maintenance channel identifiers. By comprehensively considering practical constraints such as aircraft type, turnaround time, and aircraft interchangeability, the channel assessment more closely reflects actual operational conditions, reducing misjudgments. This allows for the rapid and accurate reservation of sufficient flight maintenance channels for the same aircraft type at overnight bases without maintenance capabilities during flight scheduling. The specific implementation is illustrated in the following embodiments.

[0029] refer to Figure 1 The diagram shown is a flowchart illustrating a flight channel adjustment method disclosed in an embodiment of this application. The flight channel adjustment method mainly includes the following steps:

[0030] S101: Obtain aircraft type base maintenance information and flight scheduling data; among which, aircraft type base maintenance information is used to determine whether the airport where the flight lands is in the maintenance channel base list, and to determine the base supports aircraft type maintenance.

[0031] By using aircraft type base maintenance information, maintenance is carried out on each aircraft type, and the bases where each aircraft type can be repaired are maintained, which serves as the basis for flight channel statistics and maintenance channel determination.

[0032] S102: Statistically analyze flight scheduling data to obtain flight channel data.

[0033] S102 compiles and displays flight channel data, including channel demand for each base and aircraft type, the number of existing channels, and the number of channels to be adjusted (i.e., the number of channels to be adjusted).

[0034] Aisle requirements: One aisle is required for every 3 wide-body, narrow-body, and regional aircraft. If there are fewer than 3 aircraft, an additional aisle is required.

[0035] Existing channel quantity: For example, if the aircraft departs from a certain base and stays overnight at a maintenance base within a preset time (such as within 2 days, either staying overnight at the maintenance base on the same day or going to a certain base first and then staying overnight at the maintenance base the next day), it will stay overnight at a maintenance base that can maintain the aircraft type of the flight, including natural channels, transfer channels, overnight channels, etc.

[0036] Adjustable number of channels: Only flight schedules with transit times that do not conform to the existing channel logic, but differ from the transit time by a preset interval (e.g., 5 to 60 minutes). For example, originating from a certain base, among the flight schedules of the same period, excluding the maiden flight, there are flight schedules with transit times 5 to 60 minutes different from the standard transit time of this flight's first terminal, and which ultimately spend the night at the corresponding large aircraft maintenance base. (This does not consider the case of skipping a second terminal on a route, nor does it consider cases of spending the night at other bases and then going to the maintenance base).

[0037] The specific process of statistically analyzing flight scheduling data to obtain flight channel data is shown in A1-A7.

[0038] A1: Query the monthly release status of all airlines through flight scheduling data.

[0039] To query the monthly release status of all airlines, the specific query code is as follows:

[0040] List <ekfltplanmonthdto>allAirlnDeliverMonth=fltPlnaPushMonMapper.getAllAirlnDeliverMonth().

[0041] A2: Determine the corresponding data source based on the monthly release status; the data source must include at least a seasonal data source or a monthly data source.

[0042] For each airline combination in a flight season, determine whether it has been published to the monthly level:

[0043] If a monthly report has already been published, the monthly data source calculation method will be used.

[0044] If no monthly data is published, the seasonal data source calculation method will be used.

[0045] A3: Determine the corresponding data calculation method based on the data source.

[0046] A4: When the query parameters are received, the number of overnight aircraft is obtained by performing concurrent calculations based on the data calculation method and the query parameters.

[0047] The specific process of obtaining the number of overnight aircraft through concurrent calculation using data calculation methods and query parameters is as follows:

[0048] For each flight season, call the `calculateCurrentChannelNums` method:

[0049] Step 1: Construct query parameters:

[0050] FltPlanQueryRequestDTO requestDTO=new FltPlanQueryRequestDTO();

[0051] requestDTO.setAirlnCd(tsSeasonDO.getAirln()); / / Airline code

[0052] requestDTO.setAirlnCdList(Arrays.asList(tsSeasonDO.getAirln(), "CN")); / / Merge HU and CN;

[0053] requestDTO.setSeason(tsSeasonDO.getYear()+tsSeasonDO.getSeasonNo()); / / Season;

[0054] requestDTO.setYear(tsSeasonDO.getYear()); / / Year;

[0055] requestDTO.setDataType(type); / / Data type (S / M);

[0056] Step 2: Submit the asynchronous task:

[0057] Future <repairchannelstatisticdto>submit = executorService.submit(

[0058] new RepairChannelStatisticTask(requestDTO, fltPlanSeasonMapper) );

[0060] Step 3: Obtain task results (blocking and waiting):

[0061] RepairChannelStatisticDTO dto = submit.get();

[0062] Step 4: Invoke the channel calculation service:

[0063] RepairChannelStatisticDTO currentDTO=

[0064] repairCurrentChannelStatisticService.calulateChannleCurrent(

[0065] requestDTO,

[0066] SpringContextUtil.getBean(EkIFltPlanMonQueryService.class),

[0067] dto,

[0068] airlnCds );

[0070] Step 5: Combine the calculation results:

[0071] transferCurrentNum(dto, currentDTO);

[0072] Calculation of overnight aircraft (RepairChannelStatisticTask)

[0073] Core logic:

[0074] 1. Query flight data:

[0075] List <fltplandto>fltPlanDTOS=fltPlanSeasonMapper.queryListByParam(planQueryRequestDTO);

[0076] 2. Data deduplication:

[0077] Deduplicating flight data by capacity name follows these rules:

[0078] The "CN" airline will be merged into the "HU" airline;

[0079] Remove the "standby" identifier from the capacity name;

[0080] Deduplication is performed by capacity name + aircraft type + region name;

[0081] 3. Statistics are grouped by region and aircraft type:

[0082] / / Group by region

[0083] Map <String, List <fltplandto>> map1 = fltPlanDTOSet.stream()

[0084] .collect(Collectors.groupingBy(FltPlanDTO::getRegionName));

[0085] / / Quantity counted by model

[0086] Map<String, Long> collect = seasonDtoList.stream()

[0087] .collect(Collectors.groupingBy(FltPlanDTO::getKzType, Collectors.counting()));

[0088] Output data structure:

[0089] RepairChannelStatisticDTO;

[0090] ├── airln: Airline code;

[0091] ├── regionList: List of regions;

[0092] │ ├── RegionKzCountDTO

[0093] │ │ ├── region: Region name (e.g., "Beijing", "Shanghai");

[0094] │ │ ├── list: A list of aircraft models;

[0095] │ │ │ ├── KzCountDto;

[0096] │ │ │ │ ├── kzType: Aircraft type (K-wide-body aircraft, Z-narrow-body aircraft);

[0097] │ │ │ │ ├── overNightNum: Number of overnight aircraft.

[0098] A5: The number of overnight aircraft is calculated using the channel demand calculation formula to obtain the channel demand for each base and aircraft type.

[0099] The formula for calculating channel demand is as follows:

[0100] Demand channel count = [Number of overnight flights / 3]

[0101] It should be noted that one maintenance lane can serve an average of 3 overnight aircraft, rounded up.

[0102] A6: Obtain the number of existing channels that conform to the existing channel logic from the flight scheduling data; where the existing channel logic consists of the originating base and the maintenance channel base; the number of existing channels is the number of channels of each complete daily flight route; the existing channel types include at least natural channels, overnight channels, rescheduled channels and time-switched channels.

[0103] The existing channel logic is as follows: originating from a certain base, and within a preset time (e.g., within 2 days, overnight at a maintenance base on the same day or first arriving at a certain base and then overnight at a maintenance base the following day), overnight at a maintenance base capable of maintaining that aircraft type. The existing channel logic is used to determine the current number of channels.

[0104] Statistical Method 1: Natural Channel: Starting from a certain base, the flight does not return to this base for the night on the same day according to the schedule, but instead goes to a maintenance base that can maintain the "large aircraft" of this flight for the night.

[0105] Statistical Method 2: Transfer Channel: Starting from a certain base, in the same flight schedule, except for the first flight route, there are bases at the first terminal of the other routes that meet the transit time standard of this flight (not considering the second terminal of the bypass route), and ultimately spend the night at the corresponding large aircraft maintenance base. That is, if all four conditions are met simultaneously: (1) the large aircraft type is the same; (2) there are bases in the flight schedule that ultimately spend the night at the corresponding large aircraft maintenance base; (3) the flight schedule must meet the transit time; and (4) the flight schedule is the same, then it is considered as one channel.

[0106] Statistical Method 3: Overnight Passage: Starting from a certain base A, in the same flight schedule, except for the first flight route, there are bases at the first terminal of the other routes that meet the transit time standard for this flight (not considering the situation of the terminal in the bypass route), and the flight does not return to this base for overnight stay or go to the corresponding maintenance base for overnight stay. The next day, the flight departs from base B and finally goes to the maintenance base that can maintain the "large aircraft type" of this flight for overnight stay. That is, meeting (1) the same large aircraft type; (2) the transit flight schedule meets the transit time; (3) the transit flight schedule is the same; (4) there is a flight schedule that can go to the maintenance base for overnight stay within 2 days. The above 4 conditions are considered as one passage.

[0107] The process for determining the existing channel type is shown in B1-B4:

[0108] B1: Determine the query method for flight schedule data based on the data source.

[0109] The data source is the data type, which includes seasonal data and monthly data. Seasonal data is represented by "S", and monthly data is represented by "M".

[0110] B2: Retrieve flight schedule data based on the query method.

[0111] The flight schedule data includes seasonal and monthly data.

[0112] If the query method is a seasonal data query method, then call iFltPlanQueryService.queryFltPlanListAllAuthority().

[0113] If the query method is for monthly data: call ekIFltPlanMonQueryService.queryFltPlanListByAllAuth().

[0114] B3: Based on flight schedule data, route construction is performed using route construction rules to obtain complete daily flight routes. The route construction rules are used to stitch together single-segment routes into complete daily flight routes by matching take-off and landing airports and times.

[0115] The specific route construction rules are as follows:

[0116] 1. Group flight data by capacity name and flight schedule;

[0117] 2. Perform route stitching on each set of data:

[0118] Starting from each flight;

[0119] Find the next flight that matches the arrival airport and time of this flight;

[0120] The complete flight path is recursively constructed until the takeoff base is returned or the process can no longer continue.

[0121] 3. Deduplication and filtration:

[0122] Remove duplicate routes;

[0123] Remove the contained sub-lines (e.g., remove AD from ABCD).

[0124] Prioritize retaining complete routes (routes where the number of flights equals the number of flight segments).

[0125] B4: Determine the channel type of each complete daily flight route by using the channel type determination method.

[0126] The specific method for determining the channel type is as follows:

[0127] For each constructed route, determine its channel type:

[0128] (1) Existing channel (natural channel) - CURRENT

[0129] Judgment conditions:

[0130] The departure airport and the landing airport are the same (returning to base).

[0131] Turnover times for all segments meet minimum standards.

[0132] The last flight is not an international route.

[0133] Standard transit time:

[0134] Turnover time = Next flight departure time - Current flight arrival time;

[0135] Minimum transit time standard (minutes):

[0136] Domestic to domestic: 45 minutes;

[0137] Domestic to international: 90 minutes;

[0138] International to domestic: 90 minutes;

[0139] International to international: 90 minutes;

[0140] Note: If the transit time does not meet the standard, it will not be included in the existing channel.

[0141] (2) Overnight access:

[0142] Judgment conditions:

[0143] The plane will spend the night at the airport after the last flight of the day lands.

[0144] Airports that are open overnight have maintenance access channels (search repairChannelMapper).

[0145] This base has the capability to operate this aircraft type overnight.

[0146] Recognition rules:

[0147] After grouping by flight schedule, find the last flight for each capacity name in each flight schedule;

[0148] Check if the airport where the flight lands is on the maintenance access base list;

[0149] Check if the facility supports repairs for this model;

[0150] (3) Channel can be directly switched - EXCHANGE:

[0151] Judgment conditions:

[0152] The flight route departs from and arrives at the same airport (returning to base);

[0153] The transit time did not meet the standard, but it met the standard after adjustment.

[0154] The same capacity on different schedules can be adjusted to meet transit time requirements;

[0155] Standard floating rules:

[0156] Fluctuation range:

[0157] Domestic routes: ±15 minutes;

[0158] International routes: ±30 minutes;

[0159] Calculation method:

[0160] Minimum transit time = Standard transit time - Floating time;

[0161] Maximum transit time = Standard transit time + Floating time;

[0162] If the actual transit time is within the range of [minimum transit time, maximum transit time], it is determined that the channel can be directly changed;

[0163] (4) Time Adjustment Channel - ADJUST:

[0164] Judgment conditions:

[0165] The transit time does not meet the standard;

[0166] After standard floating, the transit time requirement can be met;

[0167] Flight schedules need to be adjusted.

[0168] A7: Obtain the number of adjustable channels that conform to the preset scheduling plan from the flight scheduling data; wherein, the preset scheduling plan is the scheduling plan of the transit station whose transit time does not conform to the existing channel logic and differs from the transit time by a preset time.

[0169] A schedule that conforms to the preset schedule refers to a schedule where only the transit time of the transit terminals does not conform to the existing channel logic, but the difference between the transit time and the preset interval (e.g., 5 to 60 minutes) is different. For example, starting from a certain base, among the schedules of the same period, excluding the maiden flight, there are flight schedules whose first terminal differs from the standard transit time of this flight by 5 to 60 minutes, and which ultimately spend the night at the corresponding large aircraft maintenance base. (This does not consider the second terminal in the bypass route, nor does it consider the situation of spending the night at other bases and then going to the maintenance base).

[0170] S103: Based on aircraft type base maintenance information and flight channel data, determine the maintenance channel and mark the routes involving connection changes in the maintenance channel with maintenance channel identification after evaluation.

[0171] Specifically, the maintenance channel is determined by using the aircraft base maintenance information and the flight channel data, and the routes involving connection changes in the maintenance channel are marked with the maintenance channel identifier after evaluation, as shown in C1-C4.

[0172] C1: Determine the target aircraft type for maintenance at the airport where the target flight lands in the maintenance access base list based on the aircraft type and base maintenance information (e.g., the Haikou base can maintain 73B aircraft).

[0173] C2: Obtain the target flight schedule data corresponding to the target maintenance aircraft type from the flight schedule data.

[0174] C3: The scheduling data of each target flight that meets the transit standards of the target flight's landing airport will be exchanged and connected.

[0175] C4: Based on the rescheduled flight arrangement data of each target flight, a maintenance channel is formed, and the routes involving connection changes in the maintenance channel are marked with the maintenance channel identifier.

[0176] To facilitate understanding of the process of determining maintenance channels using aircraft base maintenance information and flight channel data, and then marking routes within those channels that have undergone connection changes after evaluation with maintenance channel identification, this section combines... Figure 2 For example:

[0177] Step 1: The target maintenance aircraft type under the Haikou base has been set, which means that the 73B aircraft can be maintained;

[0178] Step 2: Obtain the data via timed / manual means. Figure 2 Flight scheduling data for Beijing 8 and Haikou 10 were used to calculate flight corridor data. After Beijing 8 HU7482 lands in Haikou at 14:00, it connects with Haikou 10 HU7041 departing at 15:20, with a turnaround time of 80 minutes. Haikou 10 HU7072 lands in Haikou at 14:20, connecting with Beijing 8 HU7651 departing at 15:30, with a turnaround time of 70 minutes. Both meet Haikou Airport's turnaround standards. After the switch, Beijing 8 operates HU7482, HU7041, and HU7042, while Haikou 10 operates HU7071, HU7072, HU7651, HU7222, and HU7214, allowing Beijing 8 to land at its aircraft's maintenance base in Haikou. Therefore, after the switch, a maintenance corridor can be formed between Beijing 8 and Haikou 10.

[0179] Step 3: Display the channel calculation results on the scheduling page. For routes involving connection changes, the flight channels will be marked on the scheduling page, i.e., HU7482, HU7041, HU7651, and HU7072 will be marked with channel labels.

[0180] Flight routes marked with the maintenance lane icon will be displayed on the scheduling page. When a message to modify a flight's lane is received, a notification will be displayed on the scheduling page when the user modifies the flight's lane. This notification may be displayed via pop-up windows or other means.

[0181] The implementation principle of this solution is as follows:

[0182] 1.3.1 Overall Architecture:

[0183] System components:

[0184] Control layer (Resource): RepairChannelStatisticResource - Receives HTTP requests;

[0185] Service Layer: IRepairChannelStatisticServiceImpl - Business Process Orchestration;

[0186] Asynchronous Task Layer: RepairChannelStatisticTask - Concurrently calculates the number of overnight aircraft;

[0187] Channel Calculation Service: RepairCurrentChannelStatisticService - Detailed channel calculation logic;

[0188] Data Access Layer (Mapper): Database access;

[0189] The complete call flow from the controller to each service layer is as follows: Figure 3 As shown.

[0190] The specific thread pool concurrently executes the calculation of the number of overnight aircraft, as follows: Figure 4 As shown.

[0191] Technology selection:

[0192] Thread pool: ExecutorService (fixed to 5 threads);

[0193] Concurrent tasks: Future / Callable pattern;

[0194] Data processing: Java Stream API;

[0195] Data storage: MySQL database;

[0196] 1.3.2 Core Calculation Process:

[0197] Phase 1: Parameter parsing and permission verification;

[0198] Input parameter: RepairChannelStatisticDTO;

[0199] • season: flight season (e.g., "20241", "20242");

[0200] •dataType: Data type ("S" - flight season, "M" - month);

[0201] •airln: Airline code;

[0202] Processing logic:

[0203] 1. If flight season parameters are provided, retrieve user permission information via Feign call;

[0204] 2. Parse the flight season string and extract the year and season number;

[0205] 3. Construct a TsSeasonDO object and set the season attributes (XQ - Summer / Autumn, DC - Winter / Spring);

[0206] 4. If no flight season is provided, query all maintained flight seasons and automatically add the corresponding previous flight season.

[0207] Previous flight season calculation rules:

[0208] Current season → Previous season:

[0209] Summer / Autumn 2024 (20241) → Winter / Spring 2023 (20232);

[0210] 2024 Winter / Spring (20242) → 2024 Summer / Autumn (20241);

[0211] Calculation formula:

[0212] if (current season number == 1) { / / Summer / Autumn

[0213] Previous flight season year = current year - 1

[0214] Previous flight season = 2 (winter / spring)

[0215] } else { / / Winter and Spring

[0216] Previous flight season year = current year

[0217] Previous flight season = 1 (summer / autumn)

[0218] }

[0219] Phase Two: Data Source Selection and Concurrent Computation

[0220] 1. Data source determination:

[0221] Check the monthly release status of all airlines:

[0222] List <ekfltplanmonthdto>allAirlnDeliverMonth=fltPlnaPushMonMapper.getAllAirlnDeliverMonth();

[0223] For each airline combination in a flight season, determine whether it has been published to the monthly level:

[0224] Monthly data already published: Calculated using monthly data;

[0225] Unpublished monthly data: Calculated using flight season data;

[0226] 2. Thread pool initialization:

[0227] Create a thread pool with a fixed size of 5:

[0228] ExecutorService executorService = Executors.newFixedThreadPool(5,

[0229] new TaskThreadFactory(REPAIR_STATISTIC_POOL, false, Thread.MIN_PRIORITY));

[0230] 3. Concurrently calculate the number of overnight aircraft:

[0231] For each flight season, call the `calculateCurrentChannelNums` method:

[0232] Step 1: Construct query parameters:

[0233] FltPlanQueryRequestDTO requestDTO = new FltPlanQueryRequestDTO();

[0234] requestDTO.setAirlnCd(tsSeasonDO.getAirln()); / / Airline code

[0235] requestDTO.setAirlnCdList(Arrays.asList(tsSeasonDO.getAirln(), "CN")); / / Merge HU and CN

[0236] requestDTO.setSeason(tsSeasonDO.getYear()+tsSeasonDO.getSeasonNo()); / / Season

[0237] requestDTO.setYear(tsSeasonDO.getYear()); / / Year

[0238] requestDTO.setDataType(type); / / Data type (S / M)

[0239] Step 2: Submit the asynchronous task:

[0240] Future <repairchannelstatisticdto>submit = executorService.submit(

[0241] new RepairChannelStatisticTask(requestDTO, fltPlanSeasonMapper) );

[0243] Step 3: Obtain task results (blocking and waiting):

[0244] RepairChannelStatisticDTO dto = submit.get();

[0245] Step 4: Invoke the channel calculation service:

[0246] RepairChannelStatisticDTO currentDTO =

[0247] repairCurrentChannelStatisticService.calulateChannleCurrent(

[0248] requestDTO,

[0249] SpringContextUtil.getBean(EkIFltPlanMonQueryService.class),

[0250] dto,

[0251] airlnCds );

[0253] Step 5: Combine the calculation results:

[0254] transferCurrentNum(dto, currentDTO);

[0255] Phase 3: Calculation of the number of overnight aircraft (RepairChannelStatisticTask)

[0256] Core logic:

[0257] 1. Query flight data

[0258] List <fltplandto>fltPlanDTOS=fltPlanSeasonMapper.queryListByParam(planQueryRequestDTO);

[0259] 2. Data deduplication: Flight data is deduplicated by capacity name. The processing rules are as follows:

[0260] The "CN" airline will be merged into the "HU" airline.

[0261] Remove the "standby" label from the capacity name.

[0262] Deduplication by capacity name + aircraft type + region name

[0263] Statistics grouped by region and aircraft type

[0264] / / Group by region

[0265] Map <String, List <fltplandto>> map1 = fltPlanDTOSet.stream()

[0266] .collect(Collectors.groupingBy(FltPlanDTO::getRegionName));

[0267] / / Quantity counted by model

[0268] Map<String, Long> collect = seasonDtoList.stream()

[0269] .collect(Collectors.groupingBy(FltPlanDTO::getKzType, Collectors.counting()));

[0270] Output data structure:

[0271] RepairChannelStatisticDTO

[0272] ├── airln: airline code

[0273] ├── regionList: List of regions

[0274] │ ├── RegionKzCountDTO

[0275] │ │ ├── region: Region name (e.g., "Beijing", "Shanghai")

[0276] │ │ ├── list: Model statistics list

[0277] │ │ │ ├── KzCountDto

[0278] │ │ │ │ ├── kzType: Aircraft type (K-Wide-body aircraft, Z-Narrow-body aircraft)

[0279] │ │ │ │ ├── overNightNum: Number of overnight aircraft

[0280] Phase Four: Detailed Channel Calculation (RepairCurrentChannelStatisticService)

[0281] Detailed channel calculations include several sub-steps:

[0282] Step 1: Query flight schedule data:

[0283] Select the query method based on the data type:

[0284] Flight season data: Call iFltPlanQueryService.queryFltPlanListAllAuthority();

[0285] Monthly data: Call ekIFltPlanMonQueryService.queryFltPlanListByAllAuth();

[0286] Flight season data needs to be converted to a monthly format for unified processing;

[0287] Step 2: Route Construction

[0288] This is the core step in channel calculation, with the goal of combining single flight segments into complete daily flight routes.

[0289] Route construction rules:

[0290] 1. Group flight data by capacity name and flight schedule

[0291] 2. Perform route stitching on each set of data:

[0292] Starting from each flight;

[0293] Find the next flight that matches the arrival airport and time of this flight;

[0294] The complete flight path is recursively constructed until the takeoff base is returned or the process can no longer continue.

[0295] 3. Deduplication and filtering:

[0296] Remove duplicate routes;

[0297] Remove the contained sub-lines (e.g., remove AD from ABCD);

[0298] Prioritize retaining complete routes (routes where the number of flights equals the number of flight segments);

[0299] Step 3: Channel type determination (specifically as follows) Figure 5 (as shown)

[0300] For each constructed route, determine its channel type:

[0301] (1) Existing channels (natural channels) - CURRENT

[0302] Judgment conditions:

[0303] The departure airport and the landing airport are the same (returning to base);

[0304] Turnover times for all segments meet the minimum standards;

[0305] The last flight was not an international route;

[0306] Standard transit time:

[0307] Turnover time = Next flight departure time - Current flight arrival time;

[0308] Minimum transit time standard (minutes):

[0309] Domestic to domestic: 45 minutes;

[0310] Domestic to international: 90 minutes;

[0311] International to domestic: 90 minutes;

[0312] International to international: 90 minutes;

[0313] Note: If the transit time does not meet the standard, it will not be included in the existing channel.

[0314] (2) Overnight access

[0315] Judgment conditions:

[0316] After the last flight of the day landed, the passengers spent the night at the airport.

[0317] Airports with overnight stays have maintenance access channels (search repairChannelMapper).

[0318] The base has overnight storage capacity for this aircraft type.

[0319] Recognition rules:

[0320] After grouping by flight schedule, find the last flight for each capacity name in each flight schedule.

[0321] Check if the airport where the flight lands is on the maintenance access base list.

[0322] Check if the base supports repairs for this model.

[0323] (3) Channel can be directly switched - EXCHANGE

[0324] Judgment conditions:

[0325] The flight route departs from and arrives at the same airport (returning to base).

[0326] The transit time did not meet the standard, but it did after standard adjustment.

[0327] The same capacity on different schedules can be adjusted to meet transit time requirements.

[0328] Standard floating rules:

[0329] Fluctuation range:

[0330] Domestic routes: ±15 minutes;

[0331] International routes: ±30 minutes;

[0332] Calculation method:

[0333] Minimum transit time = Standard transit time - Floating time;

[0334] Maximum transit time = Standard transit time + Floating time;

[0335] If the actual transit time falls within the range of [minimum transit time, maximum transit time], it is determined to be a transferable route.

[0336] (4) Time Adjustment Channel - ADJUST:

[0337] Judgment conditions:

[0338] The transit time does not meet the standard;

[0339] After standard floating, the transit time requirement can be met;

[0340] Flight schedules need to be adjusted;

[0341] Step 4: Statistical Summary:

[0342] Statistics by region, device model, and channel type:

[0343] Map<String,KzCountDto> regionNumMap = new HashMap<>();

[0344] / / Region_Model->Statistics

[0345] KzCountDto contains:

[0346] - currentNum: Number of existing channels

[0347] - overnightNum: Number of overnight channels

[0348] - exchangeNum: Number of swappable channels

[0349] - adjustNum: Number of time adjustment channels

[0350] - currentChannelDetail: Existing channel details (flight number list)

[0351] - adjustChannelDetail: Adjust / Time Adjustment Channel Details

[0352] Channel demand calculation formula:

[0353] Demand channel count = [Number of overnight flights / 3]

[0354] It should be noted that one maintenance lane can serve an average of 3 overnight aircraft, rounded up.

[0355] Phase 5: Data Persistence

[0356] Step 1: Clear historical data:

[0357] repairChannelStatisticMapper.deleteAllData(dto); / / Delete statistics table data

[0358] repairChannelStatisticMapper.deleteAllDataDetail(dto); / / Delete the detail table data.

[0359] fltPlanMapper.clearHistoryData(dto); / / Clear flight plan identifier data

[0360] Step 2: Save statistical data

[0361] Iterate through all regions and model combinations and save them to the repair_channel_statistic table:

[0362] RepairChannelStatisticDO aDo = new RepairChannelStatisticDO();

[0363] aDo.setAirline(dto.getAirln()); / / Airlines

[0364] aDo.setBase(regionKzCountDTO.getRegion()); / / Base

[0365] aDo.setAircraftType(kzCountDto.getKzType()); / / Aircraft type

[0366] aDo.setOverNightNum(kzCountDto.getOverNightNum()); / / Number of overnight nights

[0367] aDo.setDemandNum((int) Math.ceil(kzCountDto.getOverNightNum() / 3)); / / Number of channels required

[0368] aDo.setCurrentChannelNum(current); / / Current number of channels

[0369] aDo.setAdjustChannelNum(adjust); / / Adjust time / switch channel number

[0370] aDo.setYear(dto.getYear()); / / Year

[0371] aDo.setSeason(dto.getSeason()); / / Season

[0372] aDo.setSeasonNo(dto.getSeasonNo()); / / Season number

[0373] aDo.setDataType(dto.getDataType()); / / Data type

[0374] repairChannelStatisticMapper.insertSingle(aDo);

[0375] Step 3: Save channel details:

[0376] Parse the channel detail string and save it to the repair_channel_detail table:

[0377] / / Channel details format: "HU7123&HU7456(+30)&HU7789#"

[0378] / / & Separate different flights

[0379] / / The text in parentheses contains the adjusted time (in minutes).

[0380] / / # Identify overnight access

[0381] Channel type identification:

[0382] - Contains parentheses: Time Adjustment Channel (ADJUST)

[0383] - Contains the # symbol: Overnight channel

[0384] - Existing Channel Details: Natural Channel (CURRENT)

[0385] - Channel swapping details: Swappable channels (EXCHANGE)

[0386] Step 4: Identify flight routes:

[0387] Flights identified as corridors will be marked in the schedule:

[0388] saveChannelFlag(ekFltPlanIdSet, dto);

[0389] / / Save the flight ID to the flt_plan_channel_flag table

[0390] Phase Six: Returning Results

[0391] Close the thread pool and return a success result:

[0392] executorService.shutdown();

[0393] loggerDecorator.info("Statistical channel quantity cost: " + (System.currentTimeMillis() - beginDate.getTime()));

[0394] return ResultDto.successResult().

[0395] To facilitate understanding of the flight channel adjustment process, combined with Figure 6 Explanation:

[0396] Figure 6 In the process, step 1: aircraft maintenance: maintain the bases where each aircraft type can be repaired, thereby serving as the basis for judging flight channel statistics.

[0397] Step 2: Flight Channel Statistics: Based on the statistical tasks, flight scheduling data is compiled and displayed. The flight scheduling data includes the channel demand, existing channel quantity, and adjustable channel quantity for each base and aircraft type. Statistical tasks include scheduled tasks and manual tasks.

[0398] Step 3: Display the channel calculation results back to the scheduling page: Write the calculated channel identifier back to the scheduling page, and provide a pop-up reminder when the user modifies the channel flight.

[0399] In this embodiment, there is no need for manual channel reservation and statistics. The system automatically compiles flight scheduling data to obtain flight channel data. Based on this data, it can automatically and quickly assess whether available maintenance channels meet future scheduled maintenance needs for aircraft at overnight bases without maintenance capabilities. Maintenance channels are determined by combining aircraft type and base maintenance information with flight channel data. Routes involving connection changes after evaluation are marked with maintenance channel identifiers. By comprehensively considering practical constraints such as aircraft type, turnaround time, and aircraft interchangeability, channel evaluation more closely reflects actual operational conditions, reducing misjudgments. This allows for the rapid and accurate reservation of sufficient flight maintenance channels for aircraft of the same type at overnight bases without maintenance capabilities during flight scheduling. This ensures that aircraft can fly to maintenance bases on time for scheduled maintenance, avoiding maintenance delays or flight schedule conflicts due to insufficient channels.

[0400] Based on the above embodiments Figure 1 The present application also discloses a flight channel adjustment device, such as a method for adjusting flight channels. Figure 7 As shown, the flight aisle adjustment device includes:

[0401] The acquisition unit 701 is used to acquire aircraft type base maintenance information and flight scheduling data; wherein, the aircraft type base maintenance information is used to determine whether the flight's landing airport is in the maintenance channel base list, and to determine the base's support for aircraft type maintenance.

[0402] The statistical unit 702 is used to statistically analyze flight scheduling data to obtain flight channel data;

[0403] The determination unit 703 is used to determine the maintenance channel through the aircraft base maintenance information and the flight channel data, and to mark the routes involving connection changes in the maintenance channel after actual constraint assessment with maintenance channel identification.

[0404] Furthermore, statistical unit 702 includes:

[0405] The query module is used to query the monthly release status of all airlines based on flight scheduling data;

[0406] The first determining module is used to determine the corresponding data source based on the monthly release status; wherein, the data source includes at least a seasonal data source or a monthly data source;

[0407] The second determining module is used to determine the corresponding data calculation method based on the data source.

[0408] The concurrent calculation module is used to perform concurrent calculations based on the data calculation method and the query parameters when the query parameters are received, so as to obtain the number of overnight aircraft.

[0409] The calculation module is used to calculate the number of overnight aircraft using the channel demand calculation formula, and to obtain the channel demand of each aircraft type at each base.

[0410] The first acquisition module is used to obtain the number of existing channels that conform to the existing channel logic from the flight scheduling data; wherein, the existing channel logic consists of the origin base and the maintenance channel base; the number of existing channels is the number of channels of each complete daily flight route; the existing channel types include at least natural channels, overnight channels, rescheduled channels and time-switched channels;

[0411] The second acquisition module is used to acquire the number of channel adjustments that conform to the preset scheduling plan from flight scheduling data; wherein, the preset scheduling plan is a scheduling plan in which the transit time of the transit station does not conform to the existing channel logic and differs from the transit time by a preset time.

[0412] Furthermore, the first acquisition module for determining the existing channel type includes:

[0413] The determination submodule is used to determine the query method for flight plan data based on the data source.

[0414] The query submodule is used to retrieve flight schedule data based on the query method.

[0415] The construction submodule is used to construct routes from flight plan data using route construction rules to obtain complete daily flight routes. The route construction rules are used to stitch together single-segment routes into complete daily flight routes by matching take-off and landing airports and times.

[0416] The determination submodule is used to determine the channel type of each complete daily flight route by means of channel type determination.

[0417] Furthermore, the defined unit 703 includes:

[0418] The third determination module is used to determine the target maintenance aircraft type in the maintenance channel base list based on the aircraft type base maintenance information;

[0419] The third acquisition module is used to acquire the target flight arrangement data corresponding to the target maintenance aircraft type from the flight arrangement data;

[0420] The switching and connection module is used to switch and connect the staging data of various target flights that meet the transit standards of the target flight's landing airport.

[0421] The identification generation module is used to form maintenance channels based on the flight scheduling data of each target flight after the connection is changed, and to mark the routes involving connection changes in the maintenance channels with maintenance channel identification after actual constraint assessment.

[0422] Furthermore, the flight aisle adjustment device also includes:

[0423] The echo unit displays the routes marked with the maintenance channel identifier back to the arrangement page;

[0424] The reminder unit is used to provide a reminder on the scheduling page when a message indicating a change in flight channel is received.

[0425] In this embodiment, there is no need to rely on manual channel reservation and statistics. Instead, the system automatically compiles flight scheduling data to obtain flight channel data. Based on this data, it can automatically and quickly determine whether the available maintenance channels for aircraft at overnight bases without maintenance capabilities meet future scheduled maintenance requirements. By combining aircraft type and base maintenance information with flight channel data, maintenance channels are determined. Routes involving connection changes after evaluation are marked with maintenance channel identifiers. By comprehensively considering actual constraints such as aircraft type, turnaround time, and aircraft interchangeability, the channel evaluation is closer to the actual operating conditions, reducing misjudgments. Thus, in flight scheduling, sufficient flight maintenance channels can be quickly and accurately reserved for aircraft of the same type at overnight bases without maintenance capabilities.

[0426] For the foregoing method embodiments, in order to simplify the description, they are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, because according to this application, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0427] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For apparatus embodiments, since they are basically similar to method embodiments, the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0428] The steps in the methods of the various embodiments of this application can be adjusted, combined, or deleted according to actual needs.

[0429] Finally, it should be noted that in this paper, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0430] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0431] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.< / fltplandto> < / fltplandto> < / repairchannelstatisticdto> < / ekfltplanmonthdto> < / fltplandto> < / fltplandto> < / repairchannelstatisticdto> < / ekfltplanmonthdto>

Claims

1. A method for adjusting flight channels, characterized in that, The method includes: Obtain aircraft type base maintenance information and flight scheduling data; wherein, the aircraft type base maintenance information includes information on whether the flight's landing airport is in the maintenance access base list and information on whether the base supports aircraft type maintenance; The flight scheduling data is statistically analyzed to obtain flight channel data; By using the aircraft base maintenance information and the flight channel data, maintenance channels are determined, and routes involving connection changes after actual constraint assessment are marked with maintenance channel identifiers.

2. The method according to claim 1, characterized in that, The flight channel data includes at least the channel demand for each base and aircraft type, the existing number of channels, and the number of channel adjustments. The statistical analysis of the flight scheduling data to obtain the flight channel data includes: The monthly release status of all airlines can be queried using the aforementioned flight scheduling data; The corresponding data source is determined based on the monthly release status; wherein, the data source includes at least a seasonal data source or a monthly data source; The corresponding data calculation method is determined based on the data source. When the query parameters are received, the number of overnight aircraft is obtained by performing concurrent calculations using the data calculation method and the query parameters. The number of overnight aircraft is calculated using the channel demand calculation formula to obtain the channel demand of each aircraft type at each base. The number of existing channels that conform to the existing channel logic is obtained from the flight scheduling data; wherein, the existing channel logic consists of the originating base and the maintenance channel base; the number of existing channels is the number of channels of each complete daily flight route; the existing channel types include at least natural channels, overnight channels, rescheduled channels and time-switched channels; The number of channel adjustments that conform to the preset scheduling plan is obtained from the flight scheduling data; wherein, the preset scheduling plan is a scheduling plan in which the transit time of the transit station does not conform to the existing channel logic and differs from the transit time by a preset time.

3. The method according to claim 2, characterized in that, The process of determining the existing channel type includes: The query method for flight schedule data is determined based on the data source. Retrieve flight schedule data using the described query method; Based on the flight schedule data, routes are constructed using route construction rules to obtain complete daily flight routes; wherein, the route construction rules are used to stitch together single-segment routes into complete daily flight routes by matching take-off and landing airports and times. The channel type of each complete daily flight route is determined by the channel type determination method.

4. The method according to claim 1, characterized in that, The process of determining maintenance channels using the aircraft type base maintenance information and flight channel data, and marking routes involving connection changes within the maintenance channels after actual constraint assessment with maintenance channel identifiers, includes: Based on the aircraft type base maintenance information, determine the target aircraft type for maintenance in the maintenance channel base list at the airport where the target flight will land. Obtain the target flight schedule data corresponding to the target maintenance aircraft type from the flight schedule data; The scheduling data of each target flight that meets the transit standards of the target flight's landing airport will be exchanged and connected. Maintenance channels are formed based on the flight schedule data of each target flight after the connection is changed, and the routes involving connection changes in the maintenance channels after actual constraint assessment are marked with maintenance channel labels.

5. The method according to claim 1, characterized in that, Also includes: The routes marked with the maintenance access sign will be displayed on the scheduling page; When a message to modify the flight channel is received, a notification will be displayed on the scheduling page.

6. A flight aisle adjustment device, characterized in that, The device includes: The acquisition unit is used to acquire aircraft type base maintenance information and flight scheduling data; wherein, the aircraft type base maintenance information is used to determine whether the flight's landing airport is in the maintenance channel base list, and to determine whether the base supports aircraft type maintenance; The statistics unit is used to perform statistics on the flight scheduling data to obtain flight channel data; The determination unit is used to determine the maintenance channel through the aircraft base maintenance information and the flight channel data, and to mark the routes involving connection changes in the maintenance channel after actual constraint assessment with maintenance channel identification.

7. The apparatus according to claim 6, characterized in that, The flight channel data includes at least the channel demand for each base and aircraft type, the existing number of channels, and the number of channels to be adjusted. The statistical unit includes: The query module is used to query the monthly release status of all airlines using the flight scheduling data; The first determining module is used to determine the corresponding data source based on the monthly release status; wherein, the data source includes at least a seasonal data source or a monthly data source; The second determining module is used to determine the corresponding data calculation method based on the data source; The concurrent calculation module is used to perform concurrent calculations using the data calculation method and the query parameters when the query parameters are received, to obtain the number of overnight aircraft. The calculation module is used to calculate the number of overnight aircraft using the channel demand calculation formula to obtain the channel demand of each aircraft type at each base. The first acquisition module is used to acquire the number of existing channels that conform to the existing channel logic from the flight scheduling data; wherein, the existing channel logic consists of the origin base and the maintenance channel base; the number of existing channels is the number of channels of each complete daily flight route; the existing channel types include at least natural channels, overnight channels, rescheduled channels and time-switched channels; The second acquisition module is used to acquire the number of channel adjustments that conform to the preset scheduling plan from the flight scheduling data; wherein, the preset scheduling plan is a scheduling plan in which the transit time of the transit station does not conform to the existing channel logic and differs from the transit time by a preset time.

8. The apparatus according to claim 7, characterized in that, The first acquisition module for determining the existing channel type includes: The determination submodule is used to determine the query method for flight plan data based on the data source. The query submodule is used to retrieve flight plan data according to the query method described above; A construction submodule is used to construct routes from the flight plan data using route construction rules to obtain complete daily flight routes; wherein, the route construction rules are to splice single-segment routes into complete daily flight routes by matching take-off and landing airports and times. The determination submodule is used to determine the channel type of each complete daily flight route by means of channel type determination.

9. The apparatus according to claim 7, characterized in that, The determining unit includes: The third determining module is used to determine the target maintenance aircraft type in the maintenance channel base list of the target flight's landing airport based on the aircraft type base maintenance information. The third acquisition module is used to acquire the target flight arrangement data corresponding to the target maintenance aircraft type from the flight arrangement data; The switching and connection module is used to switch and connect the staging data of various target flights that meet the transit standards of the target flight's landing airport. The identification generation module is used to form maintenance channels based on the rescheduled flight arrangement data of each target flight, and to mark the routes involving connection changes in the maintenance channels with maintenance channel identification.

10. The apparatus according to claim 7, characterized in that, Also includes: The echo unit displays the routes marked with the maintenance channel identifier back to the arrangement page; The reminder unit is used to provide a reminder on the scheduling page when a message indicating a change in flight channel is received.

Images