Boarding gate message processing method, electronic equipment with boarding gate message processing method and storage medium

Abstract

The invention discloses a boarding gate message processing method, electronic equipment with the boarding gate message processing method and a storage medium. The method comprises the steps that boarding gate information is received, the boarding gate information comprises a boarding gate message and a boarding gate message processing rule, the boarding gate message processing rule is obtained through configuration of an aviation operation user, and the boarding gate message processing rule is used for determining whether target operation is executed on the boarding gate message or not according to preset processing logic; the target operation comprises at least one of the following operations: closing message automatic processing, performing message delay processing, stopping message updating and closing boarding gate coverage; processing the boarding gate message based on the boarding gate message processing rule to obtain a message result; and sending the message result to a corresponding downstream system. According to the method and the device, the technical problem that the personalized requirements of different users on boarding gate information change and the scene adaptability problem cannot be met because the boarding gate message processing mode of the existing flight data control system (FDC) is too unified and rigid is solved.

Description

Technical Field

[0001] The present invention relates to the field of aviation operation technology, and in particular to a method for processing a boarding gate message and an electronic device and a storage medium having the same. Background Art

[0002] Gate information broadcast is an integral part of aviation operations. It mainly broadcasts flight information, gate location, gate closing time, etc. Traditionally, gate information broadcast is mainly done manually by staff, which is inefficient and inaccurate, and the staff has high work intensity and work pressure. With the development of technology, an automated broadcast system has emerged. The automated broadcast system can automatically broadcast gate information, reduce the work pressure of staff, and improve work efficiency.

[0003] In the prior art, airlines and airports will send gate messages to the flight data control system (FDC) after completing the allocation and adjustment of the gate. After receiving the gate message, the FDC processes it and publishes the flight schedule dynamics to the downstream related systems. Although the current FDC system adopts a relatively unified gate message processing method, it still has certain problems: if a user sends too many gate messages for a certain flight, the FDC system completes the message processing and updates the gate multiple times, resulting in the possibility that passengers may wait at different gates; when the received gate message meets the filtering and processing rules, as long as the gate message sent by the airline is received, it will automatically change the processing, which will overwrite the gate manually modified by the user; the existing logic does not support the function of delaying the processing of the gate message. When the received gate message meets the filtering and processing rules, as long as the gate message sent by the airline is received, it will automatically change the processing.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiment of the present invention provides a method for processing boarding gate messages and an electronic device and a storage medium having the same, so as to at least solve the technical problem that the existing flight data control system (FDC) is too uniform and rigid in processing boarding gate messages, resulting in the inability to meet the personalized needs of different users for boarding gate information changes and the problem of scene adaptability.

[0006] According to one aspect of an embodiment of the present invention, a method for processing a gate message is provided, comprising: receiving gate information, wherein the gate information comprises: a gate message, a gate message processing rule, wherein the gate message processing rule is configured by an aviation operation user, and the gate message processing rule is used to determine whether to perform a target operation on the gate message according to a preset processing logic, wherein the target operation comprises at least one of the following: closing automatic message processing, postponing message processing, stopping message updating, closing gate coverage; processing the gate message based on the gate message processing rule to obtain a message result; and sending the message result to a corresponding downstream system.

[0007] Further, the gate message is processed based on the gate message processing rules, including: when the gate message processing rules include an automatic processing rule and a first rule value corresponding to the automatic processing rule, determining whether the first rule value is yes, wherein the automatic processing rule is used to determine whether the gate message is automatically processed, and the first rule value includes yes and no; in response to the first rule value being yes, automatically processing the gate message; in response to the first rule value being no, closing automatic message processing on the gate message.

[0008] Furthermore, processing the gate message based on the gate message processing rule also includes: in a case where the gate message processing rule includes a message overdue processing rule and a second rule value corresponding to the message overdue processing rule, determining whether the second rule value is yes, wherein the message overdue processing rule is used to determine whether to process the gate message when the time interval between the terminal date and the current date exceeds a preset time interval, and the second rule value includes yes and no; in response to the second rule value being no, performing message deferral processing on the gate message whose time interval between the terminal date and the current date exceeds a preset time period; in response to the second rule value being yes or in response to the time interval between the terminal date and the current date of the gate message not exceeding the preset time period, automatically processing the gate message.

[0009] Furthermore, processing the gate message based on the gate message processing rule also includes: in a case where the gate message processing rule includes an update number rule and a third rule value corresponding to the update number rule, determining whether the number of message updates in the gate message is greater than the third rule value, wherein the update number rule is used to limit the number of automatic changes to the gate on the flight plan updated in the gate message, and the third rule value includes a preset number of gate changes; in response to the number of message updates in the gate message being less than or equal to the third rule value, automatically processing the gate message to update the gate information on the flight plan; in response to the number of message updates in the gate message being greater than the third rule value, executing stop message processing on the gate message.

[0010] Furthermore, processing the gate message based on the gate message processing rules also includes: in a case where the gate message processing rules include an automatic override rule and a fourth rule value corresponding to the automatic override rule, determining whether the fourth rule value is yes, wherein the automatic override rule is used to determine whether the gate message can update the gate information of the flight plan, and the fourth rule value includes yes and no; in response to the fourth rule value being yes, performing gate data override processing on the gate message; in response to the fourth rule value being no and the gate corresponding to the gate message being a non-default boarding area, closing the gate override on the gate message.

[0011] Furthermore, before receiving the gate message processing rule, the method includes: in response to the existence of a previous message processing rule, performing a rule conflict check on the gate message processing rule and the previous message processing rule, and determining whether to receive the gate message processing rule according to the check result.

[0012] Further, receiving the gate message processing rule includes: obtaining the gate message processing rule based on remote communication, wherein the gate message processing rule is configured by an aviation operation user through a pre-configured user graphical interface.

[0013] According to another aspect of an embodiment of the present invention, there is further provided an electronic device, comprising: a memory storing an executable program; and a processor for running the program, wherein the method in each embodiment of the present invention is executed when the program is running.

[0014] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided. The computer-readable storage medium includes a stored executable program, wherein when the executable program is running, the device where the computer-readable storage medium is located is controlled to execute the methods in various embodiments of the present invention.

[0015] According to another aspect of an embodiment of the present invention, a computer program product is provided, including a computer program. When the computer program is executed by a processor, the method in each embodiment of the present invention is implemented.

[0016] In the embodiment of the present invention, a personalized gate message processing rule is configured, and the aviation operation user sets the gate message processing rule according to his own needs, so as to achieve the purpose of accurately controlling the change of gate information, thereby achieving the technical effects of improving boarding efficiency, reducing passenger confusion, and enhancing system adaptability and user satisfaction, and further solving the technical problem that the existing flight data control system (FDC) cannot meet the personalized needs of different users for gate information changes and the problem of scenario adaptability due to the overly unified and rigid gate message processing method. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0018] Figure 1 is a flow chart of an optional method for processing a boarding gate message according to an embodiment of the present invention;

[0019] Figure 2 The present invention is a flowchart of an optional method for processing a boarding gate message according to an embodiment of the present invention. DETAILED DESCRIPTION

[0020] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0021] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0022] According to an embodiment of the present invention, an embodiment of a method for processing a boarding gate message is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0023] Figure 1 is a method according to an embodiment of the present invention, such as Figure 1 As shown, the method comprises the following steps:

[0024] Step S101, receiving gate information; wherein the gate information includes: a gate message and a gate message processing rule, wherein the gate message processing rule is configured by an aviation operation user, and the gate message processing rule is used to determine whether to perform a target operation on the gate message according to a preset processing logic, wherein the target operation includes at least one of the following: closing automatic message processing, postponing message processing, stopping message updating, and closing gate coverage;

[0025] Optionally, the gate message usually includes key information such as the flight number, the new gate location, and the change time, and is used to notify the system of changes to the flight gate.

[0026] The gate message processing rules are a series of criteria that determine whether the gate message needs to be executed immediately, whether the gate information needs to be updated, whether the original information can be overwritten, etc. based on the specific needs of aviation operation users. Aviation operation users can configure different gate message processing rules based on flight number, terminal, date range and other conditions through the system interface.

[0027] Turn off automatic message processing: After the user sets this rule, the system will not automatically process boarding gate messages for certain specific flights, which avoids changing boarding gate information at inappropriate times or under inappropriate circumstances.

[0028] Deferred message processing: Users can specify that when a gate message with a terminal date that is N days later than the current date is received, it will be marked as deferred processing, and the change operation will not be performed until the set processing date range is reached. For example, if N days is set to 3 days, then gate changes with a date more than 3 days in the future will not be processed temporarily until the date is closer.

[0029] Stop message updates: Users can limit the frequency of gate information updates for a certain flight. Once the set number of updates is reached, subsequent gate messages received for the same flight will no longer cause gate information updates, thus avoiding passenger confusion caused by frequent changes.

[0030] Disable gate override: Users can set the gate information they have set manually to not be overwritten when a new gate message is received, unless the user initiates the change. This ensures the user's control over the gate information and avoids automatically overwriting the user's special arrangements.

[0031] Step S102, processing the gate message based on the gate message processing rule to obtain a message result;

[0032] Through this series of rule matching and analysis, the system can intelligently process boarding gate messages, ensuring that only boarding gate information changes that meet the specific needs of airlines and airports will be executed, thereby avoiding unnecessary boarding gate changes and ensuring smooth and comfortable boarding for passengers. It also reduces the burden on operators and improves the accuracy and efficiency of system operations.

[0033] Step S103: Send the message result to the corresponding downstream system.

[0034] Sending the message results to the corresponding downstream system can ensure that the gate change information can be conveyed to passengers in a timely and accurate manner, avoiding confusion and delays during boarding, while also reducing the work pressure of airport staff and improving the overall operational efficiency of the airport. The broadcasting method includes at least one of the following: boarding gate information display system, broadcasting system. The downstream system is managed by aviation operation users, and the information synchronized by the downstream system is mainly for flight control users such as airlines / airports. Aviation operation users will broadcast the message results.

[0035] Through the above steps, in an embodiment of the present invention, a personalized gate message processing rule is configured, and the aviation operation user sets the gate message processing rule according to his own needs, so as to achieve the purpose of accurately controlling the change of gate information, thereby achieving the technical effect of improving boarding efficiency, reducing passenger confusion, and enhancing system adaptability and user satisfaction, and further solving the technical problem that the existing flight data control system cannot meet the personalized needs of different users for gate information changes and the problem of scenario adaptability due to the overly unified and rigid gate message processing method.

[0036] As an optional implementation, processing the boarding gate message based on the boarding gate message processing rules includes: when the boarding gate message processing rules include an automatic processing rule and a first rule value corresponding to the automatic processing rule, determining whether the first rule value is yes, wherein the automatic processing rule is used to determine whether the boarding gate message is automatically processed, and the first rule value includes yes and no; in response to the first rule value being yes, automatically processing the boarding gate message; in response to the first rule value being no, closing automatic message processing on the boarding gate message.

[0037] Optionally, automatic processing rules are used to control whether received gate messages are automatically processed. If this rule is not configured, the message is automatically processed by default. After receiving the gate message, the system will first look for the automatic processing rule related to the message. If the automatic processing rule exists, the system will check the first rule value of the rule. The first rule value is a Boolean parameter that indicates whether the system is allowed to automatically process the gate message. If the first rule value is "yes", the system will automatically process the message according to the preset processing flow; if the first rule value is "no", the system will execute the operation of closing the automatic processing of the message, that is, no automatic gate information changes will be made.

[0038] Optionally, the system will automatically parse the information in the gate message, update the gate information in the flight schedule database, and record the update log. The system will also synchronize the updated gate information to the downstream system through interface calls to notify passengers of gate changes in a timely manner.

[0039] If automatic processing is turned off, the system will not automatically change the gate information, but mark the message status as "unprocessed". Aviation operation users can view these unprocessed gate messages through the system interface and decide whether manual intervention is required or adjust the message processing rules based on the actual situation.

[0040] Optionally, in a specific embodiment, an airport is processing a gate change message for flight number CZ350, which carries new gate information G03. Before processing, the system first checks the automatic processing rules and finds an automatic processing rule configured as "For flight number CZ350 between May 1, 2024 and May 31, 2024, the first rule value is yes." This indicates that the system can automatically process changes to the gate information for CZ350. The gate information for flight CZ350 is then automatically updated to G03, and the change is recorded in the system log. Next, the system sends the change information to the downstream system, and the user can query the changed gate information at the front end of the departure system.

[0041] Optionally, in a specific embodiment, an airline is operating a flight with a flight number of CZ808, and the original boarding gate of the flight is G10. Because the terminal is undergoing temporary maintenance and renovation, the airline's operations team configures an automatic processing rule in the flight data control system (FDC), which is for flight CZ808 and sets the date range from June 1, 2024 to June 30, 2024. When configuring the automatic processing rule, the aviation operation user selects "No" as the first rule value, which means that within the above date range, the system will not automatically process any gate change instructions for flight CZ808. During the maintenance period, the system receives a gate change message for flight CZ808, which suggests changing the gate from G10 to G15. Based on the automatic processing rule, in response to the first rule value of "No", the system will not automatically update the gate information in the flight plan, nor will it send the change information to the gate, and the status of the message is marked as "unprocessed".

[0042] Through this embodiment, by using automatic processing rules and their first rule values, the system can automatically and flexibly respond to changes in boarding gate information, which not only reduces the workload of operators, but also ensures the timeliness and accuracy of passenger information, thereby improving the airport's operating efficiency and passenger service experience.

[0043] As an optional implementation, processing the boarding gate message based on the boarding gate message processing rules also includes: in a case where the boarding gate message processing rules include a message overdue processing rule and a second rule value corresponding to the message overdue processing rule, determining whether the second rule value is yes, wherein the message overdue processing rule is used to determine whether the boarding gate message is processed when the time interval between the terminal date and the current date exceeds a preset time interval, and the second rule value includes yes and no; in response to the second rule value being no, performing message deferral processing on the boarding gate message whose time interval between the terminal date and the current date exceeds a preset time period; in response to the second rule value being yes or in response to the time interval between the terminal date and the current date of the boarding gate message not exceeding the preset time period, automatically processing the boarding gate message.

[0044] Optionally, the message overdue processing rule is a set of rules set in the flight data control system (FDC) to meet the special time requirements of airlines and airports for boarding gate changes. It allows aviation operation users to specify whether the boarding gate change message should be delayed when the time interval between the terminal date and the current date exceeds the preset time period. The introduction of this rule provides the system with flexibility in the time dimension, allowing the operator to more accurately control the update time of the boarding gate information based on the current operation status and passenger service needs.

[0045] Optionally, in a specific embodiment, a flight CZ1234 operated by an airline has a terminal date of August 10, 2024. Due to the complexity of flight plans, the airline hopes to postpone the processing of gate change messages that exceed the current date by 5 days to reduce interference with recent flight operations. The airline's operations team configures a message overdue processing rule in the FDC system. The rule sets that when the time interval between the terminal date and the current date exceeds 5 days, the second rule value is set to "No". On August 4, 2024, the system receives a gate change message for flight CZ1234, suggesting that the gate be changed from G20 to G25. According to the configured rules, the system determines that the time interval between the terminal date (August 10, 2024) and the current date (August 4, 2024) is 6 days, which exceeds the preset 5-day time interval. Therefore, the system identifies that the second rule value is "No", and the system will not process this gate change message immediately, but mark its status as "delayed processing" and record it in the system. At the same time, the system may trigger an alert to inform airline operations staff about the existence of the message and the decision to delay processing. As the terminal date approaches, that is, within a preset time (such as 2 days) from August 10, 2024, the system will automatically re-evaluate all gate change messages marked as "delayed processing". For the message of flight CZ1234, the system will perform automatic processing, update the gate information to G25, and send the information to the boarding gate.

[0046] If on August 8, 2024, the system receives another gate change message for flight CZ1234, suggesting changing the gate from G20 to G30. The system will determine that the time interval between the terminal date and the current date is 2 days, which does not exceed the preset 5-day time interval, so the system recognizes the second rule value as "yes". The system will automatically process this message directly and update the gate information to G30.

[0047] In this embodiment, the introduction of the message overdue processing rule enables the aviation operator to set a reasonable time window according to the specific circumstances of the flight to determine the timing of processing the gate change message. This not only helps to avoid unnecessary gate changes during the critical period of flight operation, thereby reducing the impact on passengers, but also ensures that the gate information is accurately updated within the appropriate time to ensure smooth flight operations. The flexible setting of the second rule value enables the system to intelligently perform the delay or automatic processing of the gate change message according to the needs of the aviation operator.

[0048] As an optional implementation, processing the gate message based on the gate message processing rule further includes: in the case where the gate message processing rule includes an update number rule and a third rule value corresponding to the update number rule, determining whether the number of message updates in the gate message is greater than the third rule value, wherein the update number rule is used to limit the number of automatic changes of the gate on the updated flight plan in the gate message, and the third rule value includes the preset number of gate changes; in response to the number of message updates in the gate message being less than or equal to the third rule value, automatically processing the gate message; in response to the number of message updates in the gate message being greater than the third rule value, executing a stop message on the gate message. Stopping message updates is also gate updates.

[0049] Optionally, the update count rule is used to control the number of times the gate message updates the gate change on the flight plan. If this rule is not configured, the default message has no update count limit.

[0050] Optionally, in a specific embodiment, flight CZ2002 operated by an airline receives multiple gate change messages in a certain day, and the aviation operator hopes to limit the number of automatic gate changes to avoid passengers receiving change information multiple times in a short period of time, causing confusion. To this end, the airline configures the update number rule and sets the third rule value to 3 times, which means that the gate change message of the same flight allows automatic update of the gate information up to 3 times. In the morning of the same day, flight CZ2002 receives the gate change instruction for the first time, changing the gate from G30 to G35. In the afternoon, the system receives the gate change message for CZ2002 again, and this time it recommends changing the gate from G35 to G40. The system determines that the number of gate changes is 2 times, which is less than the third rule value of 3 times, so it performs automatic update. In the evening, the system receives the gate change message for CZ2002 for the third time, and recommends changing the gate from G40 to G45. The system recognizes that the number of changes is 3 times, which is equal to the third rule value, so it performs automatic update. On the second day, the fourth gate change message for flight CZ2002 was received, suggesting that the gate be changed again. However, after checking the update count rule and the third rule value, the system found that the number of gate changes for this flight had exceeded the limit (3 times), so the system stopped updating the gate and kept the gate information on the flight plan as G45 without further updates. The system marked the message status as "alarm" and recorded the alarm information that the number of updates had reached the upper limit. The message status and alarm information can be queried at the front end of the departure system, informing the aviation operation user that the number of gate changes has exceeded the limit and manual review or rule adjustment is required.

[0051] In this embodiment, by using the update number rule and the third rule value, the frequency of gate changes can be effectively controlled to avoid unnecessary information updates. At the same time, when the number of gate changes reaches the upper limit, the alarm mechanism is triggered to ensure that aviation operation users can notice and take corresponding measures in time to maintain the efficiency of operations and the continuity of passenger services. The setting of this rule reflects the flexibility and user orientation of system design, which helps airlines and airports to manage flight information more finely and improve passenger experience in a complex and changing operating environment.

[0052] As an optional implementation, processing the gate message based on the gate message processing rules further includes: when the gate message processing rules include an automatic override rule and a fourth rule value corresponding to the automatic override rule, determining whether the fourth rule value is yes, wherein the automatic override rule is used to determine whether the gate message can update the gate information of the flight plan, and the fourth rule value includes yes and no; in response to the fourth rule value being yes, performing gate data override processing on the gate message; in response to the fourth rule value being no and the gate corresponding to the gate message is a non-default boarding area, closing the gate override on the gate message.

[0053] The boarding gate message is used to modify the boarding gate information on the flight plan. The determination of whether the boarding gate is the default check-in area refers to the boarding gate information stored in the flight plan.

[0054] Optionally, the automatic overwrite rule is used to control whether the received gate message can automatically overwrite the existing gate information in the flight plan. If this rule is not configured, the default message updates the gate information of the flight plan. When the FDC system receives a gate change message, it first identifies the flight information in the message, the changed gate number, and the gate information that already exists in the current flight plan. The system searches for the automatic overwrite rule associated with the message. If the automatic overwrite rule is matched, the system will check the fourth rule value of the rule. If the fourth rule value is "yes", the system will perform data overwrite processing and update the flight plan with the latest gate information. If the fourth rule value is "no", the message status will be marked as "alarm", and the alarm will be recorded as not allowing overwriting of existing data.

[0055] Optionally, in a specific embodiment, a certain flight CZ9001 receives multiple gate change instructions on the day of the terminal due to the adjustment of the internal operation of the terminal. In order to ensure the stability of the gate information under specific circumstances, the aviation operation user decides to set an automatic overwrite rule for the gate change instructions of the non-default boarding area, and sets the fourth rule value to "no" to restrict its automatic update behavior. On the day of the terminal, the boarding gate of flight CZ9001 was initially set to G50, which is not the default boarding area of ​​the system. Subsequently, the system receives a gate change instruction, suggesting that the gate be changed to G55. The system first matches the automatic overwrite rule, identifies that the fourth rule value is "no", and the current boarding gate G50 is not the default boarding area, so it executes to close the gate overwrite, does not update the gate information, and the message status is marked as "alarm". At the same time, the system may generate an alarm notification to inform the operation user that the change instruction is blocked. The message status will be marked as "alarm", and the alarm will be recorded as not allowing overwriting of existing data.

[0056] In this embodiment, the flexibility and stability of gate information changes are effectively balanced through the application of automatic override rules and the fourth rule value. While allowing airlines and airports to flexibly respond to operational needs, unnecessary information changes are avoided by limiting automatic overrides in specific situations (such as non-default boarding areas), making gate information changes more cautious, reducing potential impacts on passengers, and improving the reliability of flight plans and passenger service satisfaction.

[0057] As an optional implementation, before receiving the boarding gate message processing rule, the method includes: in response to the existence of a prior message processing rule, performing a rule conflict check on the boarding gate message processing rule and the prior message processing rule, and determining whether to receive the boarding gate message processing rule based on the check result.

[0058] Optionally, the system compares the new rule configuration request with the content of the previous message processing rules, paying special attention to the rule conditions that may conflict, such as automatic processing rules, automatic update times rules, automatic overwrite rules and deferred processing rules. The system determines whether the new rule configuration request conflicts with the previous message processing rules based on the preset conflict verification principles. The conflict verification principles usually include exact matching of conditions and overlapping checks on date ranges to ensure that the rule settings under specific conditions are unique and valid. If the rule conflict verification finds that the new rule configuration request conflicts with the previous message processing rules, the system will refuse to accept the new rule and generate a conflict alarm to inform the aviation operation user that the rule conditions or rule values ​​need to be adjusted to avoid conflicts. If the conflict verification result shows that the new rule does not conflict with the previous rule, or the new rule covers a special case of the previous rule, the system will accept the new rule configuration request and apply it to subsequent boarding gate reports.

[0059] Optionally, in a specific embodiment, an airline operations team submits a new rule configuration request to configure an automatic override rule to limit the automatic override behavior of gate change messages received by flight CZ3000 between July 1, 2024 and July 31, 2024. Before receiving the new rule configuration request, the system retrieves a prior automatic update number rule for flight CZ3000, the date range of which is from July 5, 2024 to July 25, 2024, which partially overlaps with the date range of the new rule. Based on the result of the conflict check, the system determines that the new rule configuration request conflicts with the prior rule, and therefore refuses to accept the new rule. At the same time, the system generates an alarm message to prompt the aviation operation user that the date range of the new rule configuration overlaps with the existing automatic update number rule, and the date range or rule type needs to be adjusted to avoid the conflict. The subsequent operation user adjusts the date to August 1, 2024 to August 31, 2024. After submitting the new rule configuration request again, since the date range no longer conflicts with the previous rule, the system receives this new rule configuration request and applies it to the subsequent gate change message processing of flight CZ3000.

[0060] In this embodiment, the rule conflict verification process plays an important role in ensuring the accuracy and consistency of system rule configuration. It not only helps aviation operation users avoid information processing errors caused by rule conflicts, but also ensures the transparency and controllability of system operations, and improves the stability and operational efficiency of the flight data control system.

[0061] As an optional implementation, receiving the boarding gate message processing rule includes: obtaining the boarding gate message processing rule based on remote communication, wherein the boarding gate message processing rule is configured by an aviation operation user through a pre-configured user graphical interface.

[0062] Optionally, the aviation operation user configures the gate information through the graphical user interface provided by the FDC system. The interface usually includes the flight number, terminal information, date, time, gate number and a series of options for gate change rules, such as automatic processing, update limit, overwrite rules and deferred processing. The user enters or selects the required gate information and change rules in the graphical interface, and the system automatically saves these configurations to form gate change instructions or rules. After saving the configuration, the system sends the gate change information to the server of the FDC system through remote communication protocols such as TCP / IP, HTTP, etc., requesting to update the gate information of the flight plan or modify the rule settings.

[0063] In an alternative embodiment, if Figure 2As shown, when an aviation operation user submits a boarding gate message, the system will process the boarding gate message according to the automatic processing rules, message overdue processing rules, update number rules, and automatic overwrite rules, obtain the message result, and send the message result to the corresponding downstream system.

[0064] Optionally, in a specific embodiment, a flight number operated by an airline is CA888, which is scheduled to take off from Tianhe Terminal and go to Shanghai Hongqiao Airport, and the operation date is September 1, 2024. In order to improve the efficiency of flight operations and passenger experience, the airline's operations team decided to use the FDC system's four gate change processing rules for personalized configuration to deal with possible gate changes on the day of the flight. The operations team configures the automatic processing rules for CA888 flight, and the first rule value is set to "yes"; it also sets that the gate change message with a terminal date 3 days later than the current date should be automatically processed, and the second rule value is set to 3 days; the operations team limits the number of automatic changes of the gate change messages received on the day of the flight to 2 times. The third rule value is set to 2; the automatic coverage rule is set, and the fourth rule value is set to "no". On a certain day before the flight operation date (such as August 28, 2024), the FDC system receives the first gate change message for CA888 flight and changes the gate information from G01 to G02. The system first matches the automatic processing rule. Since the value of the first rule is "yes", the system continues to process. The system checks the deferred processing rule and finds that the terminal date of the message is outside the 3-day range of the current date. The second rule value supports the processing of the change message, so the message is automatically processed and the system continues to process. The system checks the update count rule. This is the first gate change of the flight day. The update count does not exceed the limit of 2 times, so the system continues to process. Since the gate information of the flight plan does not exist or has never been manually modified to a non-default boarding area, the system automatically updates the gate information to G02.

[0065] Through the above embodiments, the combined use of automatic processing rules, update number rules, automatic coverage rules and deferred processing rules not only ensures the timeliness and accuracy of flight boarding gate information, but also provides the airline operation team with flexible control means to cope with various possible operational needs and challenges, thereby improving the efficiency of flight operations and passenger satisfaction.

[0066] The embodiment of the present application further provides an electronic device, comprising: a memory storing an executable program; a processor for running the program, wherein when the program is running, the method for processing the boarding gate message in each embodiment of the present invention is executed. The steps are as follows:

[0067] Step S101, receiving gate information, wherein the gate information includes: a gate message and a gate message processing rule, wherein the gate message processing rule is configured by an aviation operation user, and the gate message processing rule is used to determine whether to perform a target operation on the gate message according to a preset processing logic, wherein the target operation includes at least one of the following: closing automatic message processing, postponing message processing, stopping message updating, and closing gate coverage;

[0068] Step S102, processing the gate message based on the gate message processing rule to obtain a message result;

[0069] Step S103: Send the message result to the corresponding downstream system.

[0070] The embodiment of the present application further provides a computer-readable storage medium, the computer-readable storage medium includes a stored executable program, wherein when the executable program is running, the device where the computer-readable storage medium is located is controlled to execute the method for processing the boarding gate message in each embodiment of the present invention. The steps are as follows:

[0071] Step S101, receiving gate information, wherein the gate information includes: a gate message and a gate message processing rule, wherein the gate message processing rule is configured by an aviation operation user, and the gate message processing rule is used to determine whether to perform a target operation on the gate message according to a preset processing logic, wherein the target operation includes at least one of the following: closing automatic message processing, postponing message processing, stopping message updating, and closing gate coverage;

[0072] Step S102, processing the gate message based on the gate message processing rule to obtain a message result;

[0073] Step S103: Send the message result to the corresponding downstream system.

[0074] The embodiments of the present application also provide a computer program product, including a computer program, which implements the method for processing boarding gate messages in various embodiments of the present invention when executed by a processor. The steps are as follows:

[0075] Step S101, receiving gate information, wherein the gate information includes: a gate message and a gate message processing rule, wherein the gate message processing rule is configured by an aviation operation user, and the gate message processing rule is used to determine whether to perform a target operation on the gate message according to a preset processing logic, wherein the target operation includes at least one of the following: closing automatic message processing, postponing message processing, stopping message updating, and closing gate coverage;

[0076] Step S102, processing the gate message based on the gate message processing rule to obtain a message result;

[0077] Step S103: Send the message result to the corresponding downstream system.

[0078] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0079] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0080] 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, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0081] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0082] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of 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 method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0083] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for processing boarding gate messages, characterized in that: include: Receive gate information, wherein the gate information includes: a gate message and a gate message processing rule, wherein the gate message processing rule is configured by an aviation operation user, and the gate message processing rule is used to determine whether to perform a target operation on the gate message according to a preset processing logic, wherein the target operation includes at least one of the following: closing automatic message processing, postponing message processing, stopping message update, and closing gate coverage; Processing the boarding gate message based on the boarding gate message processing rule to obtain a message result; Send the message result to the corresponding downstream system.

2. The processing method according to claim 1, characterized in that: Processing the boarding gate message based on the boarding gate message processing rule includes: In a case where the gate message processing rule includes an automatic processing rule and a first rule value corresponding to the automatic processing rule, determining whether the first rule value is yes, wherein the automatic processing rule is used to determine whether the gate message is automatically processed, and the first rule value includes yes or no; In response to the first rule value being yes, automatically processing the boarding gate message; In response to the first rule value being no, performing the closing message automatic processing on the boarding gate message.

3. The processing method according to claim 1, characterized in that: Processing the boarding gate message based on the boarding gate message processing rule also includes: In the case where the gate message processing rule includes a message overdue processing rule and a second rule value corresponding to the message overdue processing rule, determining whether the second rule value is yes, wherein the message overdue processing rule is used to determine whether to process the gate message when the terminal date and the current date exceed a preset time interval, and the second rule value includes yes or no; In response to the second rule value being no, performing the message extension process on the gate message whose time interval between the terminal date and the current date exceeds a preset time period; In response to the second rule value being yes or in response to the time interval between the terminal date of the gate message and the current date not exceeding the preset time period, the gate message is automatically processed.

4. The processing method according to claim 1, characterized in that: Processing the boarding gate message based on the boarding gate message processing rule also includes: In a case where the gate message processing rule includes an update number rule and a third rule value corresponding to the update number rule, determining whether the message update number in the gate message is greater than the third rule value, wherein the update number rule is used to limit the number of automatic changes of the gate on the updated flight plan in the gate message, and the third rule value includes the preset number of gate changes; In response to the number of message updates in the gate message being less than or equal to the third rule value, automatically processing the gate message; In response to the number of message updates in the boarding gate message being greater than the third rule value, stop message processing is performed on the boarding gate message.

5. The processing method according to claim 1, characterized in that: Processing the boarding gate message based on the boarding gate message processing rule also includes: In a case where the gate message processing rule includes an automatic override rule and a fourth rule value corresponding to the automatic override rule, determining whether the fourth rule value is yes, wherein the automatic override rule is used to determine whether the gate message can update the gate information of the flight plan, and the fourth rule value includes yes or no; In response to the fourth rule value being yes, performing gate data overwriting processing on the gate message; In response to the fourth rule value being no and the boarding gate corresponding to the boarding gate message being a non-default boarding area, the closing boarding gate coverage is performed on the boarding gate message.

6. The processing method according to any one of claims 1 to 5, characterized in that: Before receiving the boarding gate message processing rule, the method includes: In response to the existence of a previous message processing rule, a rule conflict check is performed on the boarding gate message processing rule and the previous message processing rule, and it is determined whether to accept the boarding gate message processing rule according to the check result.

7. The processing method according to claim 1, characterized in that: Receiving the boarding gate information includes: The gate message processing rule is obtained based on remote communication, wherein the gate message processing rule is configured by an aviation operation user through a pre-configured user graphical interface.

8. An electronic device, characterized in that: include: A memory storing an executable program; A processor, configured to run the program, wherein the program executes the method according to any one of claims 1 to 7 when running.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored executable program, wherein when the executable program is executed, the device where the storage medium is located is controlled to execute the method according to any one of claims 1 to 7.

10. A computer program product, characterized in that The invention comprises a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 7.

Images