A method and apparatus for automatically changing flight schedules and terminal locations

Abstract

This application relates to a method and apparatus for automatically changing the terminal information of a flight plan. The method includes: parsing the terminal information item in an ASM message; generating corresponding change rules based on the terminal change information; a rule processing module modifying existing rules according to a change rule request to generate new specified rules and returning the change result, and tagging the terminal information; changing the terminal information of the flight plan specified in the message according to the specified rules; if the change fails, changing the terminal information of the flight plan specified in the message according to the modified specified rules of the rule processing module, so that the terminal information on the specified flight plan is updated to the terminal information specified in the message. This method automates the modification of terminal rules and flight plan information, reduces the user's rule change process, and can solve the problem of temporary adjustments to the terminal information of specified flight plans for airlines operating under a two-zone airport model.

Description

Technical Field

[0001] This application belongs to the field of flight plan management technology, and specifically relates to a method, apparatus, electronic device, and computer-readable storage medium for automatically changing flight plan terminal. Background Technology

[0002] The "one airport, two zones" operation model refers to establishing two independent operating zones within the same airport to accommodate the operational needs of different airlines. This model typically involves setting up two or more terminals within the airport, each serving a specific airline or route, thereby achieving more refined operational management and service improvements. When flights operated by the same airline involve multiple terminals, passengers may not be able to disembark and board via jet bridges. To solve this problem and improve the airline's jet bridge utilization rate, it is usually necessary to schedule the arrival terminal of preceding flights based on the departure terminal of subsequent flights, thus requiring temporary terminal adjustments. Traditional change procedures require users to first modify terminal rules and then adjust flight schedules. Because terminal rules may exist multiple times and have complex combinations, changes cannot be made if there are conflicts in the rules.

[0003] Patent application "Method and Apparatus for Generating Flight Schedules" (application number: 201910620433.X, China TravelSky Holding Company Limited) disclosed a method for generating and matching flight terminal rules. However, this application belongs to the traditional terminal rule modification method and cannot solve the problem of temporary adjustments to the terminal for a specific flight schedule. Summary of the Invention

[0004] To address the aforementioned issues and better meet the needs of flight schedule terminal information changes, this application proposes a new method and apparatus for automatically changing flight schedule terminal information. More specifically, this application is for the civil aviation passenger transport sector and aims to provide airlines with a method for making corresponding terminal rule changes and flight schedule changes based on terminal change information in ASM messages.

[0005] ASM message: AD HOC SCHEDULE MESSAGE, an IATA standard message for temporary changes to flight schedules. This message is applicable to changes to flight schedules on a single day, but not to changes to flight schedules over a period of time.

[0006] To achieve the above objectives, this application provides the following technical solution:

[0007] The first aspect of this application provides a method for automatically changing the terminal of a flight schedule, comprising:

[0008] Message processing: The message processing module parses the terminal information items in the ASM message, generates corresponding change rules based on the terminal change information in the ASM message, and sends the change rule request to the rule processing module. Then, based on the change result returned by the rule processing module, it marks the terminal information on the corresponding message storage item. After the terminal information is marked, the message status is set to pending processing.

[0009] Rule processing: The rule processing module modifies the existing rules in the system according to the rule change request sent by the message processing module, generates new specified rules, and then returns the change results to the message processing module.

[0010] Flight schedule matching: The terminal information of the flight schedule specified in the message is changed according to the rules after the rule processing module is modified, so that the terminal information and other changed information on the specified flight schedule are updated to the content specified by the corresponding rules;

[0011] Flight refresh: When the flight plan matching module fails, the terminal information of the flight plan specified in the message will be updated according to the rules changed by the rule processing module, so that the terminal information on the specified flight plan is updated to the terminal content specified in the message.

[0012] Optionally, in the method of this application, the message processing includes:

[0013] Message parsing: The message processing module parses the ASM message line by line according to the ASM standard message format requirements to obtain the corresponding terminal change information;

[0014] Generate terminal change rules: Generate system interaction change messages based on the terminal change information obtained from message parsing and store them in the database. Then, generate corresponding change rules based on the terminal change information and send the generated change rule requests to the rule processing module for change processing.

[0015] Terminal Information Tagging: After the rule processing module changes the rule, it returns the processing result. If the rule change is successful, the terminal information flag in the system interaction message is marked as Terminal, indicating that the message contains arrival terminal information and the rule has been successfully changed. Subsequent flight changes will be updated according to the arrival terminal information specified in the message. If the rule change fails, the terminal information flag in the system interaction message is marked as RodoTerminal. The rule processing module will automatically resynchronize and change the rule during subsequent flight planning processes. If the message does not contain terminal information, the terminal information flag in the system interaction message will be marked as empty.

[0016] Optionally, in the method of this application, the arrival terminal information in the terminal change information obtained by parsing the message is stored in DEI98, and the storage format is aaaaaa 98 / x(x), where aaaaaa represents the changed flight segment.

[0017] Optionally, in the method of this application, the terminal change rules include the following information:

[0018] Airline: The airline to which the message belongs, and also the airline to which the rule change applies;

[0019] Rule Name: The rule name is Terminal;

[0020] Rule value: Arrival terminal information obtained from message parsing;

[0021] Rule hierarchy: The rule hierarchy is flight number + arrival station. The rule hierarchy indicates which flight information items are matched for this rule.

[0022] Flight number: Flight number information in the message;

[0023] Arrival at the terminal: The message contains information about changing the last three letters of the flight segment identifier in item DEI98;

[0024] Start Date: The date of the change in the message;

[0025] End Date: The date specified in the message as the end date;

[0026] Schedule: Calculate the corresponding schedule based on the change date in the message.

[0027] Optionally, in the method of this application, the rule processing includes:

[0028] The rule processing module receives a rule change request sent by the message processing module, and then queries the database to see if there is any overlapping rule data based on the airline, rule name, rule level, start date, end date, and flight schedule information in the rule change request.

[0029] If the intersection rule data does not exist in the database, the database storage data is generated based on the requested rule data and the data is added to the database. After successful database entry, the message processing module is returned that the rule generation is successful. If the rule generation fails or the database entry fails, the message processing module is returned that the rule generation failed.

[0030] If there is overlapping rule data in the database, first determine whether the data in the database is completely consistent with the requested rule data; if they are completely consistent, delete the overlapping rule data, generate database storage data based on the requested rule data and add data to the database. If the data is successfully added to the database, return a message processing module indicating that the rule generation was successful. If the rule generation or data addition fails, return a message processing module indicating that the rule generation failed.

[0031] If there is overlapping rule data in the database, and it is not completely consistent with the data in the change rule request, then the overlapping rule data is split according to the start date, end date, and shift of the change rule request. The request rule date is excluded from the overlapping rule dates. If there is an inclusion relationship between rule factors, then the request rule factor is excluded from the overlapping rule factors. For the split overlapping rule data, first delete the part that is completely consistent with the request rule data. Then, generate database storage data and add data to the database according to the inconsistent overlapping rule data. At the same time, generate database storage data and add data to the database according to the request rule data. If the database entry is successful, return a message to the message processing module that the rule generation is successful. If the rule generation fails or the database entry fails, return a message to the message processing module that the rule generation failed.

[0032] If a message contains multiple rules, the message processing module will only return a message indicating that the rule generation was successful if all rules have been successfully modified; otherwise, it will return a message indicating that the rule generation failed.

[0033] Optionally, in the method of this application, the intersection rule data refers to rule data in the database where the requested date has the same airline, the rule name is terminal rule, the rule level is flight number + arrival terminal, the rule factor flight number includes the requested flight number, and the rule factor arrival terminal includes the requested terminal.

[0034] Optionally, in the method of this application, the flight schedule matching includes the following three processing methods:

[0035] (1) Terminal information exists and the rule is successfully generated.

[0036] The message processing module sends system interaction change messages with a pending status to the flight plan matching module. The flight plan matching module queries the terminal rules and other rules required for flight changes stored in the database based on the requested flight plan information, and changes the flight plan information according to the rule values. After the change is completed, it returns a success message to the message processing module, which then marks the message as processed successfully. If the rule matching fails, it returns a failure message to the message processing module, which then marks the message as processed failed.

[0037] (2) Terminal information exists but rule generation failed.

[0038] The message processing module regenerates the change rules and sends them to the rule processing module. If the rule generation is successful, the message processing module re-tags the terminal information on the message and executes the steps in (1). If the rule generation continues to fail, the terminal information is tagged and the message is marked as processing failed.

[0039] (3) No terminal information exists.

[0040] The message processing module sends system interaction change messages with a pending status to the flight plan matching module. The flight plan matching module matches flight information with relevant rules, and then changes the flight plan information according to the rule values. After the change is completed, it returns a success message to the message processing module, which then marks the message as processed successfully. If the rule matching fails, it returns a failure message to the message processing module, which then marks the message as processed failed.

[0041] Optionally, in the method of this application, the flight refresh includes:

[0042] For messages that have terminal information and have been successfully generated, but whose message status is "processing failed", if it is necessary to change the terminal information of the specified flight plan for the message, a separate refresh operation should be performed.

[0043] The message processing module requests the flight refresh module to refresh the terminal rules based on the airline, flight number, and flight date information specified in the message.

[0044] The flight refresh module queries the system for existing flight schedules based on the request, and then queries the corresponding terminal rules based on the flight schedules to change the terminal information.

[0045] A second aspect of this application provides an apparatus for automatically changing the terminal of a flight schedule, the apparatus comprising:

[0046] Message processing module: used to parse the items with terminal information in the ASM message, generate corresponding change rules based on the terminal change information in the ASM message, send the change rule request to the rule processing module, and then mark the terminal information on the corresponding message storage item according to the change result returned by the rule processing module; after the terminal information is marked, the message status is set to pending processing.

[0047] Rule processing module: Used to modify existing rules in the system according to the rule change request sent by message processing module, generate new specified rules, and then return the change result to message processing module;

[0048] Flight plan matching module: Used to modify the terminal information of the flight plan specified in the message according to the rules modified by the rule processing module, so that the terminal information and other modified information on the specified flight plan are updated to the content specified by the corresponding rules;

[0049] Flight refresh module: When the flight plan matching module fails, the module updates the terminal information of the flight plan specified in the message according to the rules changed by the rule processing module, so that the terminal information on the specified flight plan is updated to the terminal content specified in the message.

[0050] The device implements the steps of the aforementioned method for automatically changing flight schedules and terminals when it is in operation.

[0051] A third aspect of this application provides an electronic device, including: a memory and a processor;

[0052] Memory: Used to store computer programs;

[0053] Processor: Used to execute the computer program to implement the steps of the aforementioned method for automatically changing flight schedules and terminals.

[0054] A fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the aforementioned method for automatically changing flight schedule terminals.

[0055] In summary, this application presents a method for modifying terminal rules and flight schedules based on terminal change information in ASM messages. This method automates the modification of terminal rules and flight schedules, reducing the user's rule modification process. For airlines operating under a two-zone airport model, it can address temporary adjustments to the terminal for specific flight schedules, and the method is highly convenient to use. Furthermore, this application provides a function for users to refresh flight schedules based on messages, enabling the operation of refreshing flight schedules by specifying messages.

[0056] Other features and advantages of this application will be set forth in the following description and will be apparent in part from the description or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the techniques pointed out in the description, claims and drawings. Attached Figure Description

[0057] 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 some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0058] Figure 1 This is a flowchart illustrating the overall processing framework of a method according to an embodiment of this application.

[0059] Figure 2 This is a schematic diagram illustrating the implementation process of a method according to one embodiment of this application.

[0060] Figure 3 This is a schematic diagram of the structural composition of an apparatus according to an embodiment of this application. Detailed Implementation

[0061] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, 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.

[0062] The term “comprising” and its variations as used herein are open-ended inclusions, meaning “including but not limited to”; the term “based on” means “at least partially based on”; and the term “one embodiment” means “at least one embodiment”.

[0063] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that they should be understood as "one or more" unless the context clearly indicates otherwise.

[0064] In current business scenarios, if a user needs to adjust the terminal rules for a specific flight schedule, they must first change the terminal rules and then refresh or modify the flight schedule. This application provides a method for changing flight schedules based on messages, which allows for simultaneous changes to terminal rules and flight schedules using messages. This meets users' needs for temporary adjustments to terminal rules and enables quick and accurate adjustments to specified terminals.

[0065] Figure 1 The diagram illustrates a method for automatically changing the terminal of a flight schedule according to this application. This method is implemented through a system comprising: a message processing module, a rule processing module, a flight schedule matching module, and a flight refresh module; wherein:

[0066] The message processing module is primarily responsible for message processing, including parsing terminal information items from standard ASM messages sent by airlines and storing them in the database. It also generates corresponding terminal rules based on the terminal change information in the message and sends them to the rule processing module for modification. Then, based on the modification results from the rule processing module, it tags the corresponding message storage item with terminal information, indicating that the modified message contains terminal information that needs to be changed, so that subsequent terminal information modification operations can be performed on the corresponding message.

[0067] The rule processing module is primarily responsible for processing rules, including modifying existing rules in the system according to terminal rule change requests sent by the message processing module. After modifying a rule, the rule processing module returns the change status to the message processing module.

[0068] The flight plan matching module is mainly responsible for rule matching, including changing the terminal information of the flight plan specified in the message according to the rules changed by the rule processing module, so that the terminal information and other changed information on the specified flight plan are updated to the content specified by the corresponding rules.

[0069] The flight refresh module is mainly responsible for refreshing flights. When the flight plan matching module fails, it updates the terminal information of the flight plan specified in the message according to the modified terminal rules of the rule processing module, so that the terminal information on the specified flight plan is updated to the terminal content specified in the message.

[0070] To better understand the technical solution of this application, its implementation process will be further described in detail with the following examples of business scenarios.

[0071] 1. Message Processing

[0072] The message processing module is responsible for message processing, including message parsing, generating terminal change rules, and tagging terminal information.

[0073] 1) Message parsing

[0074] The message is parsed line by line according to the ASM standard message format requirements to obtain the corresponding flight schedule change information. The arrival terminal information is stored in DEI98 (DEI is the identifier for storing flight attribute information in the standard message; DEI98 stores the arrival terminal information). The storage format is aaaaaa98 / x(x), where aaaaaa indicates a changed flight segment, 98 indicates that this is DEI98, and x(x) is represented by 1-2 characters, meaning the arrival terminal value. The specific format is shown in Table 1 below:

[0075] Table 1. Format of Terminal Building Information Items

[0076]

[0077]

[0078] 2) Generate terminal change rules

[0079] After parsing the message, the corresponding flight change information is obtained. Based on the change information, a change message for system interaction is generated and stored in the database for subsequent change operations. For messages that parse out arrival terminal information, corresponding arrival terminal rules are generated based on the flight information and terminal information, and sent to the rule processing module for processing. The generated terminal rule information is shown in Table 2 below:

[0080] Table 2 Terminal Rules Information

[0081]

[0082] Specifically, if the destination terminal of message DEI98 is not QQQ, the destination terminal is taken from the one in DEI; if the destination terminal of message DEI98 is QQQ, the destination terminal matching the flight segment in the message is taken. For example, for a message with the route PEK-SHA-CTU, if DEI98 is SHAQQQ, then the destination terminal is CTU; if DEI98 is PEKQQQ, then the destination terminal is SHA; if DEI98 is QQQQQQ, then the destination terminals are SHA and CTU. For cases with multiple destination terminals, multiple rules are generated for modification.

[0083] Since the ASM message is a single-day flight schedule change message, the start date and end date of the generated rule are the same, taking the date of the changed flight schedule in the message.

[0084] One or more terminal rules generated from a single message can be sent in batches to the rule processing module for processing.

[0085] 3) Terminal information tagging

[0086] After the rule processing module modifies a rule, it returns the processing result. If the rule change is successful, the terminal information flag in the system interaction message is marked as "Terminal," indicating that the message contains arrival terminal information and the rule has been successfully changed. Subsequent flight changes will be updated based on the arrival terminal information specified in the message. If the rule change fails, the terminal information flag in the system interaction message is marked as "RodoTerminal," indicating that the terminal rule generation failed. Subsequent flight scheduling will automatically retry, i.e., resynchronize the rule processing module to perform the rule change. If the message does not contain terminal information, the terminal information flag in the system interaction message is marked as empty.

[0087] After the terminal information is tagged, the message processing module sets the message status to pending processing.

[0088] 2. Terminal rule processing

[0089] The rule processing module is responsible for processing rules. When it receives a request to modify a rule, it checks whether there are overlapping rule data based on the airline, rule name, rule level, start date, end date, and flight schedule in the request. Overlapping rule data refers to rules in the database that have the same airline on the request date, are named "Terminal Rule," have a rule level of "Flight Number + Arrival Terminal," have a rule factor "Flight Number" that includes the requested flight number, and have a rule factor "Arrival Terminal" that includes the requested terminal.

[0090] If the intersection rule data does not exist in the database, the database storage data is generated according to the requested rule, and the data is added to the database. After successful database insertion, a message processing module is returned indicating that the rule generation was successful. If rule generation or database insertion fails, a message processing module is returned indicating that the rule generation failed.

[0091] If overlapping rules exist in the database, it's necessary to determine if the data in the database is completely identical to the requested data. If the overlapping rules and the requested rules are completely identical, the overlapping rules are deleted, the requested rules are used to generate the database storage data, and the new data is added to the database. Upon successful database insertion, a message processing module is returned indicating successful rule generation. If rule generation or database insertion fails, a message processing module is returned indicating rule generation failure.

[0092] If there are intersection rule data in the database, and they are not completely consistent with the request rule, then the intersection rule needs to be split. The principle of splitting is to split the intersection rule according to the start date, end date, and shift of the request rule, excluding the request rule date from the intersection rule date. If there is an inclusion relationship between rule factors, the request rule factors also need to be excluded from the intersection rule. For example, the intersection rule is CA,Terminal,T3,930-940,[PEK,SHA],2024 / 09 / 01,2024 / 09 / 30,1234567, and the request rule is CA,Terminal,T2,935,[PEK],2024 / 09 / 10,2024 / 09 / 10,2. After splitting, it becomes rule 1: CA,Terminal,T3,930-934,[PEK,SHA],2024 / 09 / 01,2024 / 0 9 / 09, 1234567, Rule 2: CA,Terminal,T3,936-940,[PEK,SHA],2024 / 09 / 11,2024 / 09 / 30,1234567, Rule 3: CA,Terminal,T3,935,[SHA],2024 / 09 / 10,2024 / 09 / 10,2,Rule 4: CA,Terminal,T3,935,[PEK],2024 / 09 / 10,2024 / 09 / 10,2. For the split rules, first delete the intersection rules, then generate database storage data for rules 1, 2, and 3 respectively, and add new data to the database. Simultaneously, use request rules to generate database storage data and add new data to the database. After successful database insertion, return a message processing module indicating successful rule generation. If rule generation or database insertion fails, return a message processing module indicating rule generation failure.

[0093] If a message contains multiple rules, the message processing module will only return a message indicating that the rule generation was successful if all rules are changed successfully; otherwise, it will return a message indicating that the rule generation failed.

[0094] 3. Flight schedule matching

[0095] The flight schedule matching module is responsible for rule matching. After the message processing module completes the terminal information tagging, it can continue to modify the flight schedule information. The specific processing situations can be divided into the following categories:

[0096] 1) Terminal information exists and rules are successfully generated.

[0097] The message processing module sends system interaction change messages with a pending status to the flight plan matching module. The flight plan matching module queries the terminal rules and other rules required for flight changes stored in the database based on the requested flight plan information, and changes the flight plan information according to the rule values ​​to complete the change of the flight to be effective. It then returns a success message to the message processing module, which marks the message as processed successfully. If the matching rule fails, it returns a failure message to the message processing module, which marks the message as processed failed.

[0098] 2) Terminal information exists, but rule generation failed.

[0099] The message processing module regenerates the terminal rules and sends them to the rule processing module. If the rule generation is successful, the message processing module will re-tag the terminal information on the message and execute the steps in 1). If the rule generation continues to fail, the terminal information will be tagged and the message will be marked as a processing failure.

[0100] 3) No terminal information is available.

[0101] The message processing module sends system interaction change messages with a pending status to the flight plan matching module. The flight plan matching module matches flight information with relevant rules, then changes the flight plan information according to the rule values ​​to complete the change of the flight to be effective, and returns a success message to the message processing module, which then marks the message as processed successfully. If the rule matching fails, a failure message is returned to the message processing module, which then marks the message as processed failed.

[0102] 4. Flight updates

[0103] The flight refresh module is responsible for refreshing flights. For messages with terminal information and successful rule generation, but whose message status is "processing failed", if the user wants to change the terminal information of the specified flight plan in the message, a separate refresh operation can be performed.

[0104] The message processing module requests the flight refresh module to update the terminal rules based on the airline, flight number, and flight date information specified in the message. The flight refresh module queries the system for existing flight schedules based on the request, then queries the corresponding terminal rules to modify the terminal information and generates a list of flights to be updated. This refresh process only changes the terminal information and does not alter other information on the flight schedule.

[0105] Figure 2 The diagram illustrates a method for automatically changing the terminal of a flight schedule according to this application, comprising the following steps:

[0106] Message processing: The message processing module parses the terminal information items in the ASM message, generates corresponding change rules based on the terminal change information in the ASM message, and sends the change rule request to the rule processing module. Then, based on the change result returned by the rule processing module, it marks the terminal information on the corresponding message storage item. After the terminal information is marked, the message status is set to pending processing.

[0107] Rule processing: The rule processing module modifies the existing rules in the system according to the rule change request sent by the message processing module, generates new specified rules, and then returns the change results to the message processing module.

[0108] Flight schedule matching: The terminal information of the flight schedule specified in the message is changed according to the rules after the rule processing module is modified, so that the terminal information and other changed information on the specified flight schedule are updated to the content specified by the corresponding rules;

[0109] Flight refresh: When the flight plan matching module fails, the terminal information of the flight plan specified in the message will be updated according to the rules changed by the rule processing module, so that the terminal information on the specified flight plan is updated to the terminal content specified in the message.

[0110] Figure 3 The diagram shows an apparatus for automatically changing the terminal of a flight schedule according to this application, comprising: a message processing module, a rule processing module, a flight schedule matching module, and a flight refresh module; wherein:

[0111] The message processing module is mainly responsible for message processing: parsing the terminal information items in the ASM message, generating corresponding change rules based on the terminal change information in the ASM message, sending the change rule request to the rule processing module, and then tagging the terminal information on the corresponding message storage item according to the change result returned by the rule processing module, indicating that the change message has terminal information that needs to be changed, so that the corresponding flight information of the change message can be changed accordingly in the future; after the terminal information is tagged, the message status is set to pending processing.

[0112] The rule processing module is mainly responsible for processing rules: it is used to modify the existing rules in the system according to the rule change request sent by the message processing module, generate new specified rules, and then return the change results to the message processing module.

[0113] The flight plan matching module is mainly responsible for rule matching: it is used to change the terminal information of the flight plan specified in the message according to the specified rules after the rule processing module, so that the terminal information and other changed information on the specified flight plan are updated to the content specified by the corresponding rule;

[0114] The flight refresh module is mainly responsible for flight refresh: when the flight plan matching module fails, it updates the terminal information of the flight plan specified in the message according to the rules changed by the rule processing module, so that the terminal information on the specified flight plan is updated to the terminal content specified in the message.

[0115] The apparatus composed of the above modules implements the steps of the method for automatically changing flight schedules and terminals disclosed in this application when it is in operation.

[0116] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0117] The names of messages or data exchanged between multiple modules in this disclosure are for illustrative purposes only and are not intended to limit the scope of these messages or data.

[0118] Furthermore, embodiments of this application also disclose an electronic device, including: a memory and a processor;

[0119] The memory is used to store a computer program, and the processor is used to run the computer program to implement the steps of the above-described method for automatically changing flight schedules and terminals.

[0120] It is understandable that, in addition to memory and a processor, this electronic device may also include input devices such as a keyboard, output devices such as a display, and a communication module. The input devices, output devices, and communication module communicate with the processor through I / O interfaces (i.e., input / output interfaces).

[0121] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0122] Furthermore, this application also discloses a computer-readable storage medium, wherein when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is able to perform the steps of the method for automatically changing flight schedule terminals disclosed in this application.

[0123] In the context of this disclosure, a computer-readable storage medium can be a tangible medium, and more specific examples include portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0124] In particular, according to embodiments of this disclosure, the processes described in the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device, or installed from a ROM. When the computer program is executed by a processing device, it performs the functions defined in the methods of embodiments of this disclosure.

[0125] While several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure. The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept.

[0126] Those skilled in the art should also understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions 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 this application.

Claims

1. A method for automatically changing the terminal of a flight schedule, characterized in that, The method includes: Message processing: The message processing module parses the terminal information items in the ASM message, generates corresponding change rules based on the terminal change information in the ASM message, and sends the change rule request to the rule processing module. Then, based on the change result returned by the rule processing module, it marks the terminal information on the corresponding message storage item. After the terminal information is marked, the message status is set to pending processing. Rule processing: The rule processing module modifies the existing rules in the system according to the rule change request sent by the message processing module, generates new specified rules, and then returns the change results to the message processing module. Flight schedule matching: The terminal information of the flight schedule specified in the message is changed according to the rules after the change by the rule processing module, so that the terminal information and other changed information on the specified flight schedule are updated to the content specified by the corresponding rules; Flight refresh: When the flight plan matching module fails, the terminal information of the flight plan specified in the message will be updated according to the specified rules after the rule processing module is changed, so that the terminal information on the specified flight plan is updated to the terminal content specified in the message. The rule processing includes: The rule processing module receives a rule change request sent by the message processing module, and then queries the database to see if there is any overlapping rule data based on the airline, rule name, rule level, start date, end date, and flight schedule information in the rule change request. If the intersection rule data does not exist in the database, generate database storage data based on the requested rule data and add new data to the database; If there is intersection rule data in the database, first determine whether the data in the database is completely consistent with the requested rule data; if the two are completely consistent, delete the intersection rule data, generate database storage data based on the requested rule data, and add new data to the database. If there is intersection rule data in the database, and it is not completely consistent with the data in the change rule request, then the intersection rule data is split according to the start date, end date, and shift of the change rule request. The request rule date is excluded from the intersection rule dates. If there is an inclusion relationship between rule factors, then the request rule factors are excluded from the intersection rule factors. For the split intersection rule data, first delete the parts that are completely consistent with the request rule data. Then, generate database storage data and add new data to the database based on the inconsistent intersection rule data. At the same time, generate database storage data and add new data to the database based on the request rule data. The flight schedule matching includes the following three processing methods: (1) Terminal information exists and rules are successfully generated: The message processing module sends the system interaction change message with the status of pending to the flight plan matching module. The flight plan matching module queries the terminal rules and other rules required for flight changes stored in the database according to the requested flight plan information, and changes the flight plan information according to the rule values. (2) Terminal information exists but rule generation fails: The message processing module regenerates the change rule and sends it to the rule processing module. If the rule generation is successful, the message processing module re-labels the terminal information in the message and executes the steps in (1). (3) No terminal information: The message processing module sends the system interaction change message with the status of pending to the flight plan matching module. The flight plan matching module matches the flight information with the relevant rules, and then changes the flight plan information according to the rule value.

2. The method according to claim 1, characterized in that, The message processing includes: Message parsing: The message processing module parses the ASM message line by line according to the ASM standard message format requirements to obtain the corresponding terminal change information; Generate terminal change rules: Generate system interaction change messages based on the terminal change information obtained from message parsing and store them in the database. Then, generate corresponding change rules based on the terminal change information and send the generated change rule requests to the rule processing module for change processing. Terminal Information Tagging: After the rule processing module changes the rule, it returns the processing result. If the rule change is successful, the terminal information flag in the system interaction message is marked as Terminal, indicating that the message contains arrival terminal information and the rule has been successfully changed. Subsequent flight changes will be updated according to the arrival terminal information specified in the message. If the rule change fails, the terminal information flag in the system interaction message is marked as RodoTerminal. The rule processing module will automatically resynchronize and change the rule during subsequent flight planning processes. If the message does not contain terminal information, the terminal information flag in the system interaction message will be marked as empty.

3. The method according to claim 2, characterized in that, In the terminal change information obtained from the message parsing, the arrival terminal information is stored in DEI98, and the storage format is aaaaaa 98 / x(x), where aaaaaa represents the changed flight segment.

4. The method according to claim 2, characterized in that, The terminal change rules include the following information: Airline: The airline to which the message belongs, and also the airline to which the rule change applies; Rule Name: The rule name is Terminal; Rule value: Arrival terminal information obtained from message parsing; Rule hierarchy: The rule hierarchy is flight number + arrival station. The rule hierarchy indicates which flight information items are matched for this rule. Flight number: Flight number information in the message; Arrival at the terminal: The message contains information about changing the last three letters of the flight segment identifier in item DEI98; Start Date: The date of the change in the message; End Date: The date specified in the message as the end date; Schedule: Calculate the corresponding schedule based on the change date in the message.

5. The method according to claim 1, characterized in that, The intersection rule data refers to rule data in the database where the requested date has the same airline, the rule name is terminal rule, the rule level is flight number + arrival terminal, the rule factor flight number includes the requested flight number, and the rule factor arrival terminal includes the requested terminal.

6. The method according to claim 1, characterized in that, The flight updates include: For messages that have terminal information and have been successfully generated, but whose message status is "processing failed", if it is necessary to change the terminal information of the specified flight plan for the message, a separate refresh operation should be performed. The message processing module requests the flight refresh module to refresh the terminal rules based on the airline, flight number, and flight date information specified in the message. The flight refresh module queries the system for existing flight schedules based on the request, and then queries the corresponding terminal rules based on the flight schedules to change the terminal information.

7. An apparatus for automatically changing the terminal of a flight schedule, used to perform the method as described in any one of claims 1 to 6, characterized in that, The device includes: Message processing module: used to parse the items with terminal information in the ASM message, generate corresponding change rules based on the terminal change information in the ASM message, send the change rule request to the rule processing module, and then mark the terminal information on the corresponding message storage item according to the change result returned by the rule processing module; after the terminal information is marked, the message status is set to pending processing. Rule processing module: Used to modify existing rules in the system according to the rule change request sent by message processing module, generate new specified rules, and then return the change result to message processing module; Flight plan matching module: Used to modify the terminal information of the flight plan specified in the message according to the rules modified by the rule processing module, so that the terminal information and other modified information on the specified flight plan are updated to the content specified by the corresponding rules; Flight refresh module: When the flight plan matching module fails, the module updates the terminal information of the flight plan specified in the message according to the rules changed by the rule processing module, so that the terminal information on the specified flight plan is updated to the terminal content specified in the message.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the method for automatically changing the flight schedule terminal as described in any one of claims 1 to 6.

Images