Batch adjustment method and system for airline code sharing and electronic equipment

Abstract

The invention relates to the technical field of flight management, and particularly discloses an airline code sharing batch adjustment method and system and electronic equipment, and the method comprises the steps: initiating a request; verifying the request; recording the information of the request to a result table; replying successful termination of cooperation to the requester; when the request is termination, deleting a corresponding airline protocol, and deleting a corresponding free sales layout rule; deleting the free sales rule, and generating a free sales rule to take effect; when the airline is a market side, deleting the flight plan, and generating a flight plan to take effect; a free sales rule which automatically takes effect and waits to take effect; when the airline is the market side, all the to-be-effective flights in the previous step are automatically effective at the same time; and updating the state of the one-key termination and pause result table according to the effective result. According to the method, one-time batch processing of related operations can be realized, the flight code sharing information adjusting and publishing efficiency is greatly improved, and airlines are assisted to quickly respond to market demand changes.

Description

Technical Field

[0001] The present application belongs to the technical field of flight management, and in particular relates to a method, system and electronic equipment for batch adjustment of airline code sharing. Background Art

[0002] Currently, airline flight managers generally make flight plan changes (create, modify, delete), take effect, and publish in the Passenger Service System (PSS). Flight managers manually adjust flight plans through the front-end page of the PSS system, or make flight plan changes through IATA standard ASM / SSM messages, custom messages, etc., and publish flight plans after the changes take effect.

[0003] According to business needs, airlines need to cancel a large number of flights in cooperation with foreign airlines within a certain period of time, that is, cancel the host's free sales flights or market flights. Or completely terminate the cooperation relationship with a certain airline within a certain period of time, and no further cooperation is required.

[0004] For example, CA Airlines will terminate its free sales partnership with UA from 2023-02-01 to 2023-02-31, and terminate all cooperation between CA as the market and UA as the carrier. Based on the current system, the following steps need to be initiated on the front end:

[0005] 1. Manually delete all flight plans with CA as the market and UA as the operator from 2023-02-01 to 2023-02-31, and generate multiple flights to be effective.

[0006] 2. Manually validate all pending flights generated in the previous step and publish them.

[0007] 3. Manually delete the free sales rules with CA as the market and UA as the carrier from 2023-02-01 to 2023-02-31, and generate rules to be effective.

[0008] 4. Manually validate all pending rules generated in the previous step.

[0009] 5. Manually delete the free sales layout rules from 2023-02-01 to 2023-02-31 where CA is the market and UA is the carrier.

[0010] 6. Manually delete the airline agreements with CA as the marketer and UA as the carrier from 2023-02-01 to 2023-02-31.

[0011] For step 1: the user needs to initiate a query request according to the conditions on the front end to query all free sale flights with CA as the market and UA as the carrier from 2023-01-01 to 2023-01-31. If many are found, the user needs to manually delete the flights one by one. Assume that there are date segments: 2023-01-01 to 2023-01-07, 2023-01-08 to 2023-01-14, 2023-01-15 to 2023-01-21, 2023-01-22 to 2023-02-31. Among them, the flight plan from 2023-01-22 to 2023-02-31 spans the termination time range, so you cannot directly select to delete all flights. The flight plan from 2023-01-22 to 2023-01-31 needs to be retained. Therefore, when deleting, you need to clearly specify the correct start date, end date, and flight schedule to prevent accidental deletion of flight plans that should not be deleted.

[0012] For step 3 and step 5: Similarly, there are cases where the start date, end date, and shift period are split, which increases the difficulty of manual operation.

[0013] In summary, the current PSS system requires multiple operations on the front end to terminate cooperation, and the operation is difficult. Users need to enter the correct operation value in different operation steps to ensure the correctness of the operation; and some operation steps are sequential, such as users must complete operation 1 before operation 2, and complete operation 3 before operation 4; in addition, users need to take the initiative to check whether the previous step is completed from time to time. Therefore, the existing methods for terminating free sales cooperation have the problems of extremely cumbersome operations, prone to errors, higher time costs, high rollback costs after errors, and no unified interface to query all the market party flights that have been canceled, which need to be checked one by one. In addition, the existing methods for suspending free sales cooperation also have the same problems. Summary of the invention

[0014] In response to the above problems, the present application provides a method, system and electronic device for batch adjustment of airline code sharing.

[0015] According to a first aspect of the present application, a method for batch adjustment of airline code sharing is provided, the method comprising the following steps:

[0016] Initiate a request to terminate / suspend free sales cooperation;

[0017] Verify the request;

[0018] Record the request termination / pause information in the result table;

[0019] Reply to the requesting party that the cooperation termination is successful;

[0020] When the request is for termination, delete the corresponding airline agreement;

[0021] When the request is terminated, the corresponding free sale layout rule is deleted;

[0022] Delete the free sale rules and generate the free sale rules to be implemented. When the airline is the market party, delete the flight plan and generate the flight plan to be implemented.

[0023] The pending free sale rules of the previous step will automatically take effect; when the airline is the marketer, all pending flights of the previous step will also automatically take effect;

[0024] Update the status of the one-key termination and suspension result table according to the effectiveness results.

[0025] Optionally, the verification request includes:

[0026] Verify request fields;

[0027] Verify whether the user has the authority to terminate the cooperation;

[0028] Verify airline agreements;

[0029] Verify office;

[0030] Verify that free sale file processing is complete.

[0031] Optionally, the deleting of the corresponding airline agreement includes:

[0032] Query airline agreements based on request conditions;

[0033] If the termination date is less than or equal to the start date of a certain airline agreement, then delete the airline agreement;

[0034] If the termination date is greater than the start date of a certain airline agreement and less than or equal to the end date, the end date of the airline agreement will be modified to the request date - 1.

[0035] Optionally, deleting the corresponding free sale layout rule includes:

[0036] If the rule start date is less than the end date and the rule end date is greater than or equal to the end date, the rule is split according to the end date. The end date of the first rule is the end date - 1, and the start date of the second rule is the end date.

[0037] Optionally, the flight plan and free sale rules are deleted, and the flight plan and free sale rules to be effective are generated, including:

[0038] Query all airline flight numbers according to the request conditions;

[0039] Update the total number of the initialized result table = the total number of flight numbers queried in the previous step;

[0040] Query all flight plans to be terminated based on the host flight number and the requested termination or suspension time range;

[0041] Split the flight plan and generate records of flights that are actually to be cancelled;

[0042] Initialize the canceled flight record to the details table;

[0043] Simulate the free sale message table update, delete the flight plan and free sale rules; generate the flight plan and free sale rules to be effective.

[0044] Optionally, after terminating the free sale cooperation, you can resume the cooperation by adding airline agreements, layout rules, processing free sale SSIM files, or manually adding flights and free sale rules;

[0045] After suspending free sale cooperation, you can resume cooperation by processing the free sale SSIM file or manually adding flights and free sale rules.

[0046] Optionally, the method further includes querying the code sharing suspension and termination results; the querying the code sharing suspension and termination results includes:

[0047] Initiate a query request;

[0048] The list of pause and termination results is displayed according to the query conditions; among them, users are supported to query the details of a specified pause or termination result with a status of "processing completed"; users are supported to re-operate on a specified pause or termination result with a status of "processing failed".

[0049] Optionally, when the airline is the market party, for a pause or termination operation that has been processed, it supports querying the deleted flight plan.

[0050] According to a second aspect of the present application, a system for batch adjustment of airline code-sharing is provided, the system comprising:

[0051] A request initiating unit, used to submit a request for terminating / suspending free sale cooperation;

[0052] A verification unit, used for verifying a request;

[0053] The flight plan management component is used to record the requested termination / suspension information to the result table; to reply to the requester that the cooperation has been successfully terminated, to cancel the flight plan and free sale rules, to generate the flight plan to be effective and the free sale rules to be effective, to validate the flight plan to be effective and the code-sharing rules to be effective; and to update the status of the one-key termination and suspension result table according to the effectiveness results;

[0054] The agreement management component is used to delete the corresponding airline agreement according to the termination request;

[0055] A rule management component is used to delete the corresponding free sale layout rule according to the termination request.

[0056] According to a third aspect of the present application, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the program.

[0057] Beneficial effects of this application: Compared with the existing method of terminating / suspending free sales cooperation by manually adjusting operations one by one, this application can realize one-time batch processing of related operations. After the user initiates a request at the front end, the system will suspend or terminate all free sales cooperation relationships within a certain time period and record the situation of the operation; the user can view the suspension or termination information by himself, and can re-initiate the suspension or termination operation if the processing fails. This application greatly improves the efficiency of adjusting and publishing flight code-sharing information, helping airlines to quickly respond to changes in market demand.

[0058] Other features and advantages of the present application will be described in the following description, and partly become apparent from the description, or be understood by practicing the present application. The purpose and other advantages of the present application can be realized and obtained by the structures indicated in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0060] Figure 1 A flowchart of the steps of a method for batch adjustment of airline code sharing according to an embodiment of the present application is shown.

[0061] Figure 2 The figure shows a timing diagram of one-key termination / pause of free sale flights when the Host acts as the marketer.

[0062] Figure 3 The diagram shows the one-key termination / pause timing of a free sale flight when the Host is the operator.

[0063] Figure 4 The figure shows the one-click termination flowchart when the host airline acts as the marketer.

[0064] Figure 5 A free sale flight plan and rule deletion and effectiveness flow chart is shown.

[0065] Figure 6 The figure shows the one-click termination flowchart when the host airline is the carrier.

[0066] Figure 7 The one-click pause flowchart when the host airline acts as the marketer is shown.

[0067] Figure 8 The one-click pause flowchart when the host airline is the carrier is shown.

[0068] Fig. 9 A flow chart of querying code sharing one-key termination and suspension results is shown.

[0069] Fig.10 A flowchart of querying code sharing one-key termination and suspension details is shown.

[0070] Fig.11 An airline code-sharing batch adjustment system according to an embodiment of the present application is shown.

[0071] Fig.12 An exemplary diagram of the architecture of an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0072] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0073] To facilitate understanding of the present application, the following first describes the relevant concepts of the present application:

[0074] Flight number: It consists of airline, flight number and flight suffix, and uniquely identifies a flight. For example, CA110, CA110A, etc.

[0075] Date range: consists of a start date and an end date, where the end date is greater than or equal to the start date.

[0076] Schedule: The day of the week that a flight is operated, represented by a combination of numbers 1 to 7, 1 for Monday, 2 for Tuesday, and so on, 7 for Sunday. For example, Schedule 24 means that the flight is operated every Tuesday and Thursday.

[0077] Flight plan: It consists of the flight number, flight date range, flight schedule and other flight information (route, take-off and arrival times, aircraft type, etc.), flight section information, flight segment information, and code-sharing information. It is a data record of the flight company's scheduling and management of flights.

[0078] Host airline: An airline whose flight management and inventory management system uses the TravelSky Passenger Service System (PSS).

[0079] Flight section information: For example, flight plan: CA110, route PEK-SHA-CTU, date and flight schedule from 2024-01-01 to 2024-01-31, flight schedule 1234567. Then PEK-SHA is the first flight section of the flight, and SHA-CTU is the second flight section of the flight. The flight section contains other flight information such as departure, arrival, aircraft type, etc.

[0080] Flight segment information: For example, flight plan: CA110, route PEK-SHA-CTU, date and flight schedule from 2024-01-01 to 2024-01-31, flight schedule 1234567. PEK-SHA, PEK-CTU, and SHA-CTU are all flight segments of CA110, and the flight segments contain other flight attributes.

[0081] Code-sharing information: Code-sharing information is recorded on the flight schedule and consists of the partner's flight number, partner type (carrier or market), sharing type, etc. Sharing types include free sales, etc.

[0082] Code-sharing rules: consist of information such as the carrier flight number, the market flight number, the host airline, the start date, the end date, the flight schedule, the code-sharing type (including free sale, reserved seat, SMAP, physical inner bag), and city pairs.

[0083] Free sale rules: Free sale rules are a type of code-sharing rules, and the code-sharing type is free sale.

[0084] Flight rules [non-code-share rules]: Flight rules are the specifications that need to be followed when adding additional information to the flight plan. Flight rules consist of rule name, rule level, rule factor value corresponding to the rule level, rule value, and rule effective date range (start date + end date + flight schedule).

[0085] Free sales layout rule: Free sales layout rule is a type of flight rule, and its composition is the same as that of flight rules. Among them, the carrier airlines and market airlines in the rule factors are discrete factors. There will be multiple carrier airlines or market airlines recorded in the rule. For example, the carrier airlines of a free sales layout rule are MU and FM, and the market airlines are CA and MF, so this rule generates 4 code-sharing partnerships. If the business initiates the termination of one of the cooperations, it involves the segmentation of this rule.

[0086] Airline Agreement: It consists of information such as carrier airline, market airline, host airline, start date, end date, agreement type (free sale, reserved seat, SMAP, physical inner bag), and city pair. If you want to create code-sharing rules or flight plans, an airline agreement is required to allow users to create corresponding code-sharing rules and flights.

[0087] Figure 1 A flowchart of the steps of a method for batch adjustment of airline code sharing according to an embodiment of the present application is shown; Figure 2 It shows the timing diagram of one-key termination / pause of free sale flights when the host is the market party; Figure 3 The following is a timing diagram of one-key termination / pause of free sale flights when the Host is the carrier. Figure 1-3 As shown, this method can realize one-click termination / suspension of free sales cooperation when the host airline acts as the market party or the carrier, including the following steps:

[0088] S1: Initiate a request to terminate / suspend free sales cooperation;

[0089] S2: Verification request;

[0090] S3: Record the request termination / pause information to the result table;

[0091] S4: Reply to the requesting party that the cooperation has been successfully terminated;

[0092] S5: When the request is for termination, delete the corresponding airline agreement;

[0093] S6: when the request is termination, deleting the corresponding free sale layout rule;

[0094] S7: Delete the free sale rules and generate the free sale rules to be implemented; when the airline is the market party, delete the flight plan at the same time and generate the flight plan to be implemented;

[0095] S8: The pending free sale rules of the previous step will automatically take effect; when the airline is the market party, all pending flights of the previous step will automatically take effect at the same time;

[0096] S9: According to the effectiveness result, the status of the one-key termination and suspension result table is updated.

[0097] The airline code-sharing batch adjustment method of the present application is specifically described below through examples.

[0098] Embodiment 1

[0099] This embodiment can realize the one-click termination operation of free sale flights when the host airline is the market party. The host airline and foreign airlines are in code-sharing cooperation. The system has the corresponding market party flight plan, carrier code-sharing information and free sale rules. It supports one-click termination of code-sharing cooperation within the specified date range, and automatically deletes the market party flight plan, carrier code-sharing information, airline agreement and free sale layout rules. Subsequent users must restore cooperation by adding airline agreements, layout rules, processing free sale SSIM files or manually adding flights and free sale rules.

[0100] Figure 4 The figure shows the one-click termination flow chart when the host airline acts as the marketer. Figure 4 As shown, the airline code-sharing batch adjustment method of this embodiment includes the following steps S1-S9.

[0101] S1: Initiate a request to terminate free sales cooperation.

[0102] The requested fields include the carrier airline, the market airline, and the termination date.

[0103] S2: Verify request.

[0104] In this step, if the verification passes, the normal flow continues, otherwise the requesting party is replied to terminate the cooperation failure.

[0105] In some embodiments, the verification request includes:

[0106] 1) Verify the request fields: carrier airline, market airline, and termination date.

[0107] 2) Verify whether the user has the authority to terminate the cooperation: determine whether the requesting airline is a carrier airline or a market airline in the agreement; if so, continue the normal flow, otherwise reply to the requesting party that the termination failed.

[0108] 3) Verify airline agreements: Query airline agreements according to the requested carrier airline, market airline, and termination date. If an airline agreement that overlaps with the termination date can be found, continue the normal process. Otherwise, reply to the requesting party that the termination of cooperation has failed.

[0109] 4) Verify the office: Verify whether the user's current office is a code sharing office. If so, continue the normal flow; otherwise, reply to the requesting party that the cooperation has failed.

[0110] 5) Verify whether the free sale file has been processed: verify that there are no free sale SSIM files of the same carrier and the same market party that are being imported or processed but not yet effective; verify that there are no flights of the same carrier and the same market party that are waiting to take effect; verify that there are no flight effectiveness batches or corresponding effectiveness batches of the same carrier and the same market party that are in the queue or in effect; verify that there are no ineffective free sale rules of the same carrier and the same market party.

[0111] S3: Record the request termination / pause information to the result table.

[0112] S4: Reply to the requesting party that the cooperation termination is successful.

[0113] S5: Delete the corresponding airline agreement.

[0114] In some embodiments, when querying airline agreements according to the requested carrier airline and market airline, multiple airline agreements may be found: if the termination date is less than or equal to the start date of an airline agreement, delete the airline agreement; if the termination date is greater than the start date of an airline agreement and the termination date is less than or equal to the end date of the agreement, modify the end date of the airline agreement to the request date - 1, and record the operator and operation time.

[0115] S6: Delete the corresponding free sales layout rule.

[0116] In some embodiments, if the host airline does not belong to the group airline, the free sales layout rules are queried according to the following conditions:

[0117] 1) If the requested carrier airline is the host airline and the market airline is a non-host airline, the query level contains the market airline factor and the value of the rule factor contains the free sales layout rule of the non-host airline;

[0118] 2) If the requested market airline is the host airline and the carrier airline is a non-host airline, the query level contains the carrier airline factor and the value of the rule factor contains the free sales layout rule of the non-host airline.

[0119] If no rule is found, the exception flow will not be entered and the deletion is considered successful. If the rule is found, perform the following operations:

[0120] 1) For a rule whose start date is greater than or equal to the end date, if the factor value (if the non-host airline is the market party, the market party airline factor is determined; if the non-host airline is the carrier party, the carrier airline factor is determined, the same below) is only for the non-host airline, delete it directly; if the factor value still exists for other airlines, modify the rule, remove the factor value for the airline, and record the operator and operation time.

[0121] 2) When the rule start date is less than the end date and the rule end date is greater than or equal to the end date, the rule is split according to the end date, the end date of the previous rule is the end date-1, and the start date of the next rule is the end date, and the operator and operation time are recorded; if the factor value is only the non-host airline, the next rule is deleted; if the factor value still exists for other airlines, modify the next rule and remove the non-host airline from the factor value.

[0122] For example, if the MF carrier and DL market have a termination date of August 1, and the layout rule level market party DL and date range are June 1-December 30, then the post-termination rule dates are June 1-July 31.

[0123] For example, for MF carrier and DL market, the termination date is August 1, and the layout rule-level market parties are DL, WS, and the date range is June 1-December 30. Then after termination, the layout rule-level market parties are DL, WS, and the rule dates are June 1-July 31, and the layout rule-level market parties are WS, and the rule dates are August 1-December 30.

[0124] In some embodiments, if the host airline belongs to a group airline, the free sales layout rules are queried according to the following conditions:

[0125] 1) If the requested carrier airline is the host airline and the market airline is a non-host airline, the query level includes the carrier airline factor and the value of the rule factor includes the host airline, and includes the market airline factor and the value of the rule factor includes the free sales layout rule of the non-host airline.

[0126] 2) If the requested market airline is the host airline and the carrier airline is a non-host airline, the query level includes the market airline factor and the value of the rule factor includes the host airline, and includes the carrier airline factor and the value of the rule factor includes the free sales layout rule of the non-host airline.

[0127] If no rule is found, the exception flow will not be entered and the deletion is considered successful. If the rule is found, perform the following operations:

[0128] 1) For a rule whose start date is greater than or equal to the end date, if the two factor values ​​meet any of the following conditions, referred to as "factor value meets the condition", the same below:

[0129] a. The carrier airline factor value is only the host airline and the market airline factor value is only the non-host airline.

[0130] b. The market airline factor value is only the host airline and the carrier airline factor value is only the non-host airline.

[0131] If the factor value does not meet the conditions, modify the rules:

[0132] Logic A: If the carrier airline factor value is only the host airline and the market airline factor value is multiple including the non-host airline (one to many, such as OC: MU, MC: KL, UA, KE), or the market airline factor value is multiple including the host airline and the carrier airline factor value is only the non-host airline (many to one, such as OC: KL, UA, KE, MC: MU), then the factor value that does not meet the conditions will remove the requested airline and record the operator and operation time.

[0133] Logic B: If the carrier airline factor value is multiple including the host airline and the market airline factor value is multiple including the non-host airline (many-to-many, for example, OC: MU, FM, MC: KL, UA, KE), or the market airline factor value is multiple including the host airline and the carrier airline factor value is multiple including the non-host airline (many-to-many, for example, OC: KL, UA, KE, MC: MU, FM), then the data is split into multiple lines according to the field where the host airline is located, and then logic A is executed.

[0134] 2) For rules whose start date is less than the end date and whose end date is greater than or equal to the end date, the rules are split according to the end date, with the end date of the previous rule being the end date - 1 and the start date of the next rule being the end date. The operator and operation time are recorded. If the factor value meets the conditions, the next rule is deleted; if the factor value does not meet the conditions, the next rule is modified, with the same modification as the above logic A and logic B.

[0135] For example, if the carrier is DL and the market is FM, the termination date is August 1, and the layout rule level is carrier field party DL, market party FM, and the date range is June 1-December 30, then after termination, the layout rule level is market party carrier field party DL, market party FM, and the date range is June 1-July 31.

[0136] For example, MU carrier, DL market, the termination date is August 1, the layout rule level carrier MU, FM, market DL, date range 6.1-12.30, then after termination, the layout rule level carrier MU, FM, market DL, date range 6.1-7.31 and carrier FM, market DL, date range 8.1-12.30.

[0137] For example, DL carrier, FM market, the termination date is August 1, the layout rule level carrier field party DL, WS, market party FM, date range 6.1-12.30, then after termination, the layout rule level market party carrier field party DL, WS, market party FM, date range 6.1-7.31 and carrier field party WS, market party FM, date range 8.1-12.30.

[0138] For example, DL carrier, FM market, the termination date is August 1, the layout rule level carrier yard DL, KE, market FM, MU, date range 6.1-12.30, then after termination, the layout rule level carrier yard DL, KE, market FM, MU, date range 6.1-7.31; carrier yard DL, KE, market MU, date range 8.1-12.30; carrier yard KE, market FM, date range 8.1-12.30.

[0139] S7: Delete the flight plan and free sale rules, and generate a flight plan to be implemented and a free sale rule to be implemented.

[0140] In this step, the flight plan and free sale rules are queried according to the requested carrier airline, market airline, and date range; the flight plan and free sale rule date range can be found if they intersect with the termination date or are greater than the termination date; if no flight or free sale rule is found, it is deemed to have been terminated or terminated, and the abnormal flow is not entered; if the flight or free sale rule is found, the market flight plan and free sale rules on and after the termination date are deleted, and the flight and free sale rules to be effective are generated.

[0141] Figure 5 The free sale flight plan and rule deletion and effectiveness flow chart are shown. Figure 5 As shown, the deleting of the flight plan and the free sale rules, and generating the flight plan to be effective and the free sale rules to be effective, include the following steps S71-S76.

[0142] S71: Query all host flight numbers according to the request conditions; wherein the request conditions include the carrier airline, the market airline, and the date range.

[0143] S72: Update the total number of the initialized result table = the total number of flight numbers queried in the previous step.

[0144] S73: Query all flight plans to be terminated according to the host flight number and the requested termination or suspension time range.

[0145] S74: Split the flight plan and generate records of flights that are actually to be cancelled.

[0146] S75: Cancel the flight record and initialize it to the details table.

[0147] S76: Simulate the free sale message table update, delete the flight plan and free sale rules; generate the flight plan and free sale rules to be effective.

[0148] S8: All pending flights and pending free sales rules in the previous step will automatically take effect.

[0149] In this step, if all cancellations are successful, all pending flights and pending free sale rules in step S7 will be automatically effective; if there is a failure, the status of the one-key termination and suspension result table will be updated to processing failure, and the process ends; or the reprocessing function can be used to reprocess, and it will automatically take effect after successful reprocessing.

[0150] S9: According to the effectiveness result, the status of the one-key termination and suspension result table is updated.

[0151] Embodiment 2

[0152] This implementation can realize the one-click termination of free sale flights when the host airline is the carrier. The host airline and foreign airlines are in code-sharing cooperation. The system has the corresponding market flight plan, carrier code-sharing information and free sale rules. It supports one-click termination of code-sharing cooperation within the specified date range, and automatically deletes the market flight plan, carrier code-sharing information, airline agreement and free sale layout rules. Subsequent users must restore cooperation by adding airline agreements, layout rules, processing free sale SSIM files or manually adding flights and free sale rules.

[0153] Figure 6 The figure shows the one-click termination flow chart when the host airline is the carrier. Figure 6 As shown, the difference between the airline code-sharing batch adjustment method of this embodiment and the airline code-sharing batch adjustment method of the first embodiment lies in step 17 and step 18.

[0154] In this embodiment, step 17: deleting the free sale rule and generating a free sale rule to be effective.

[0155] Specifically, according to the requested carrier airline, market airline, and date range, the flight plan and free sale rules are queried; if the flight plan and free sale rule date range intersect with the termination date or is greater than the termination date, they can be queried; if no flight or free sale rule is found, it is deemed to have been terminated or terminated, and does not enter the abnormal flow; if the free sale rule is found, the free sale rules after the termination date are deleted, and the free sale rules to be effective are generated. If some rules for the date and flight are left after the deletion, the rule modification operator and operation time are determined.

[0156] If the date range of a flight or free sale rule overlaps with the termination date, the flight and free sale rule need to be split. For example, if the market's flight date range is 2.1-3.1 and the requested termination date is 2.2, then the system has an effective flight on 2.1 and a pending effective flight on 2.2-3.1.

[0157] In this embodiment, step 8: the system automatically takes effect on the pending free sale rules of the previous step.

[0158] Specifically, query all the free sale rules of the airline as the host carrier that are ineffective and to be changed. For each rule, query the system flights according to the host flight number, flight node, start date, end date and flight schedule; if there is a system flight with the same host flight number and flight node as the rule, and the date and flight schedule intersect, change the code-sharing information of the corresponding flight node of the host flight in the intersection: the ineffective rule is deleted: according to this rule, delete the corresponding partner information on the flight node on the flight plan; update the code-sharing information of the flight plan without generating flights to be effective, and directly update the corresponding flight agreement after the modification is successful.

[0159] Set the status of all free sales rules to Effective.

[0160] Embodiment 3

[0161] This implementation can realize the one-click suspension of free sale flights when the host airline is acting as the marketer. The host airline and foreign airlines are in code-sharing cooperation. The system has the corresponding marketer flight plan, carrier code-sharing information and free sale rules. It supports one-click suspension of code-sharing cooperation within the specified date range, and automatically deletes the marketer flight plan, carrier code-sharing information and free sale rules. Subsequent users can resume cooperation by processing the free sale SSIM file or manually adding flights and free sale rules.

[0162] Figure 7 The figure shows the one-key pause flow chart when the host airline acts as the market party. Figure 7 As shown, the difference between the airline code-sharing batch adjustment method of this embodiment and the airline code-sharing batch adjustment method of embodiment 1 lies in step 15 and step 16. This embodiment does not include deleting the airline agreement and deleting the free sales layout rule.

[0163] Embodiment 4

[0164] This implementation can realize the one-click suspension of free sale flights when the host airline is the carrier. The host airline and foreign airlines are in code-sharing cooperation. The system has the corresponding market flight plan, carrier code-sharing information and free sale rules. It supports one-click suspension of code-sharing cooperation within the specified date range, automatically deletes the market flight plan, carrier code-sharing information and free sale rules, and subsequent users can resume cooperation by processing the free sale SSIM file or manually adding flights and free sale rules.

[0165] Figure 8 The figure shows the one-key pause flow chart when the host airline is the carrier. Figure 8 As shown, the difference between the airline code-sharing batch adjustment method of this embodiment and the airline code-sharing batch adjustment method of embodiment 2 lies in step 15 and step 16. This embodiment does not include deleting the airline agreement and deleting the free sales layout rules.

[0166] Embodiment 5

[0167] This implementation can query the results of code sharing suspension and termination. Users can view the results of this operation after suspending or terminating code sharing.

[0168] Fig. 9 The flowchart of querying code sharing one-key termination and suspension results is shown. Fig. 9 As shown, the query code sharing suspension and termination results include the following steps: initiating a query request; and displaying a suspension and termination result list according to the query conditions.

[0169] After the query request is initiated, the request field is checked, see step S2 of embodiment 1. If the request field does not meet the check requirement, the abnormal flow is entered, otherwise the normal flow is continued.

[0170] It should be noted that users can only query the suspension and termination operation results of the airline group to which the user belongs.

[0171] In some embodiments, the list information includes: operator, operation time, operation (pause / termination), carrier airline, market airline, suspension start date or end date, suspension end date (if no end date is entered during suspension, the end date is empty), and status. If there are flights or agreements that have not been deleted during the suspension or termination operation, the status of the suspension termination result is "processing"; if there are flights or agreements that failed to be deleted, the status of the suspension termination result is "processing failed"; if all flights or agreements are successfully deleted, the status of the suspension termination result is "processing completed". By default, it is sorted in descending order by operation time, and paging is supported.

[0172] This application supports users to query details of a specified pause or termination result with a status of "processing completed"; and supports users to re-operate on a specified pause or termination result with a status of "processing failed".

[0173] Embodiment 6

[0174] This implementation can query the details of code-sharing suspension and termination results. When the host airline is the market party, it can query the deleted flight plan after the suspension or termination operation is completed.

[0175] Fig.10 The flowchart of querying the one-key termination and suspension details of code sharing is shown. Fig.10 As shown, the difference between the airline code-sharing batch adjustment method of this embodiment and the airline code-sharing batch adjustment method of Example 5 is that the present application can display a detailed table of termination or suspension results of the processing completed when the host airline acts as the market party.

[0176] Fig.11 A code-sharing batch adjustment system for airlines according to an embodiment of the present application is shown, and the system is used to implement the method of the above embodiment. Fig.11 As shown, the system includes:

[0177] A request initiating unit 1, used for submitting a request for terminating / suspending free sale cooperation;

[0178] Verification unit 2, used for verifying the request;

[0179] Flight plan management component 3, used to record the requested termination / suspension information to the result table; used to reply to the requester that the cooperation termination is successful, used to cancel the flight plan and free sale rules, generate the flight plan to be effective and the free sale rules to be effective, and to validate the flight plan to be effective and the code sharing rules to be effective; and used to update the status of the one-key termination and suspension result table according to the effectiveness result;

[0180] The agreement management component 4 is used to delete the corresponding airline agreement according to the termination request;

[0181] The rule management component 5 is used to delete the corresponding free sale layout rule according to the termination request.

[0182] The present application provides a method and system for batch adjustment of airline code-sharing, which solves the problems existing in the existing methods for realizing termination / suspension of free sales cooperation, such as extremely cumbersome operation, prone to errors, higher time cost, high rollback cost after errors, and no unified interface to query all the market party flights that have been canceled, which need to be checked one by one. It can realize one-time batch processing of related operations. After the user initiates a request on the front end, the system will suspend or terminate all free sales cooperation relationships within a certain time period and record the situation of the operation; the user can view the suspension or termination information by himself, and can re-initiate the suspension or termination operation if the processing fails. The present application greatly improves the efficiency of adjusting and publishing flight code-sharing information, helping airlines to quickly respond to changes in market demand. In addition, the present application reduces the reliance on code-sharing SSIM files and improves the operational efficiency of airlines in adjusting flight code-sharing information.

[0183] Fig.12 FIG. 1 shows an example diagram of the architecture of an electronic device according to an embodiment of the present application. Fig.12 As shown, the electronic device includes a processor 110, a communication interface 120, a memory 130 for storing processor executable instructions, and a communication bus 140. The processor 110, the communication interface 120, and the memory 130 communicate with each other through the communication bus 140. The processor 50 implements the above-mentioned feature screening method by running an executable computer program.

[0184] Among them, the computer program in the memory 130 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0185] The system embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, i.e., they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected based on actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art may understand and implement it without creative effort.

[0186] Although the present application has been described in detail with reference to the aforementioned embodiments, a person of ordinary skill in the art should understand that it is still possible to modify the technical solutions described in the aforementioned embodiments, or to make equivalent replacements for some of the technical features therein; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for batch adjustment of airline code sharing, characterized in that: The following steps are involved: Initiate a request to terminate / suspend free sales cooperation; Verify the request; Record the request termination / pause information in the result table; Reply to the requesting party that the cooperation termination is successful; When the request is for termination, delete the corresponding airline agreement; When the request is terminated, the corresponding free sale layout rule is deleted; Delete the free sale rules and generate the free sale rules to be implemented. When the airline is the market party, delete the flight plan and generate the flight plan to be implemented. The pending free sale rules of the previous step will automatically take effect; when the airline is the marketer, all pending flights of the previous step will also automatically take effect; Update the status of the one-key termination and suspension result table according to the effectiveness results.

2. The method for batch adjustment of airline code sharing according to claim 1, characterized in that: The verification request includes: Verify request fields; Verify whether the user has the authority to terminate the cooperation; Verify airline agreements; Verify office; Verify that free sale file processing is complete.

3. The method for batch adjustment of airline code sharing according to claim 1, characterized in that: The deletion of the corresponding airline agreement includes: Query airline agreements based on the requested conditions; If the termination date is less than or equal to the start date of a certain airline agreement, then delete the airline agreement; If the termination date is greater than the start date of a certain airline agreement and less than or equal to the end date, the end date of the airline agreement will be modified to the request date - 1.

4. The method for batch adjustment of airline code sharing according to claim 1, characterized in that: The deleting of the corresponding free sale layout rule includes: If the rule start date is less than the end date and the rule end date is greater than or equal to the end date, the rule is split according to the end date. The end date of the first rule is the end date - 1, and the start date of the second rule is the end date.

5. The method for batch adjustment of airline code sharing according to claim 1, characterized in that: Delete the flight plan and free sale rules, and generate the flight plan and free sale rules to be effective, including: Query all airline flight numbers according to the request conditions; Update the total number of the initialized result table = the total number of flight numbers queried in the previous step; Query all flight plans to be terminated based on the host flight number and the requested termination or suspension time range; Split the flight plan and generate records of flights that are actually to be cancelled; Cancel flight records and initialize them to the details table; Simulate the free sale message table update, delete the flight plan and free sale rules; generate the flight plan and free sale rules to be effective.

6. The method for batch adjustment of airline code sharing according to claim 1, characterized in that: After terminating the free sale cooperation, the cooperation can be resumed by adding airline agreements, layout rules, processing free sale SSIM files, or manually adding flights and free sale rules; After suspending free sale cooperation, you can resume cooperation by processing the free sale SSIM file or manually adding flights and free sale rules.

7. The method for batch adjustment of airline code sharing according to claim 1, characterized in that: The method further includes querying code sharing suspension and termination results; The query code sharing suspension and termination results include: Initiate a query request; Display the list of pause and termination results according to the query conditions; among them, support users to query the details of a specified pause or termination result with the status of "processing completed"; support users to re-operate on a specified pause or termination result with the status of "processing failed".

8. The method for batch adjustment of airline code sharing according to claim 7, characterized in that: When the airline is the marketer, it supports querying the deleted flight plans for a completed suspension or termination operation.

9. An airline code-sharing batch adjustment system, characterized in that: include: A request initiating unit, used to submit a request for terminating / suspending free sale cooperation; A verification unit, used for verifying a request; Flight schedule management component, used to record the requested termination / suspension information into the result table; Used to reply to the requesting party that the cooperation has been successfully terminated, to cancel flight plans and free sales rules, to generate flight plans and free sales rules to be implemented, and to implement flight plans and code-sharing rules to be implemented; and for updating the status of the one-key termination and suspension result table according to the effective results; The agreement management component is used to delete the corresponding airline agreement according to the termination request; A rule management component is used to delete the corresponding free sale layout rule according to the termination request.

10. An electronic device, characterized in that: The electronic device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the method according to any one of claims 1 to 8 when executing the program.

Images