Local backup service handling method and system for multi-leg flights

Abstract

The application discloses a kind of local backup service handling method and system of multi-segment flight, it is related to aviation technical field.The method includes: receiving the backup request sent by target station end in multiple station ends;Multiple station ends are checked by resource control mechanism, and the inspection result is obtained;In response to determining that multi-segment flight can be converted into local backup service handling mode according to the inspection result, backup response is returned to target station end;Synchronization message sent by target station end is distributed to other station ends except target station end in multiple station ends, wherein, synchronization message is used to update the local database of other station ends, and the local database is used to support other station ends to carry out local backup service handling for multi-segment flight.The application solves the technical problem that the efficiency of flight conversion local backup handling scheme for multi-segment flight is low, cost is high, security risk is high and user experience is poor.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of aviation technology, in particular to a local backup service handling method and system for multi-leg flights. BACKGROUND

[0002] Flight transfer local backup handling refers to a series of operation processes for continuing to handle boarding procedures for passengers by enabling a backup system when the departure system at the airport fails. In modern air transportation, the application of information technology has greatly improved the efficiency of airport operation and the travel experience of passengers. However, the widespread application of information technology has also made the stability of airport information systems one of the key factors affecting the normal operation of civil aviation. In particular, when the departure system fails, how to quickly and effectively handle flight transfer local backup to ensure normal flight operation and passenger satisfaction has become one of the popular research directions.

[0003] In related technologies, the flight transfer local backup handling scheme only supports single-leg flight handling, and is not applicable to other important scenarios such as multi-leg flights. Specifically, the flight transfer local backup handling scheme in related technologies requires users to perform tedious operations in the multi-leg flight handling scenario, and these operations will affect other stations. The process of transferring local backup handling cannot synchronize information to intermediate stations in real time through the above operations. For example, a multi-leg flight corresponding to a certain flight is “A-B-C”, and the check-in clerk gives the passenger a seat number 32A at the A station. At this time, due to network interruption, the 32A seat number at the B station is still determined as a check-in seat, which may cause passenger seat conflicts (another passenger is given a seat number 32A at the B station). In this case, a large amount of offline manual processing is required to complete the backup handling of the multi-leg flight, that is, the existing flight transfer local backup handling scheme has low handling efficiency, high labor cost, and may result in poor passenger experience in the multi-leg flight scenario.

[0004] In addition, in the existing flight transfer local backup handling scheme, users are almost not involved in multi-leg flights during pre-rehearsal, and multi-leg flights (such as stopover flights, transfer flights, etc.) are not uncommon in actual scenarios. Based on this, when the open departure in the actual scenario fails, insufficient pre-rehearsal may cause flight delays, which not only affects passenger travel but also brings great departure safety hazards.

[0005] As can be seen from the above, how to handle flight transfer local backup for multi-leg flights in information system failure scenarios to improve handling efficiency, reduce handling cost, and thus optimize passenger experience and enhance flight safety has become one of the important technical problems in the related technical field. In view of the above problems, no effective solution has been proposed so far. SUMMARY

[0006] The embodiments of the present invention provide a method and system for handling local backup services for multi-segment flights, so as to at least solve the technical problems of low efficiency, high cost, high security risk and poor user experience in the solution of flight transfer to local backup for multi-segment flights.

[0007] According to one aspect of an embodiment of the present invention, a local backup business processing method for a multi-segment flight is provided, which is applied to a central end of a local backup business processing system, wherein the local backup business processing system also includes multiple terminal ends corresponding to the multi-segment flight, and the local backup business processing method includes: receiving a backup request issued by a target terminal end among the multiple terminal ends, wherein the backup request is triggered when the target terminal end detects a departure server failure; performing a resource control mechanism inspection on the multiple terminal ends to obtain an inspection result; in response to determining that the multi-segment flight can be converted to a local backup business processing mode according to the inspection result, returning a backup response to the target terminal end, wherein the backup response is used to assist the target terminal end in performing the backup action; distributing a synchronization message issued by the target terminal end to other terminal ends among the multiple terminal ends except the target terminal end, wherein the synchronization message is used to update the local database of the other terminal ends, and the local database is used to support the other terminal ends in performing local backup business processing for the multi-segment flight.

[0008] Optionally, the data carried in the backup request includes: flight information and passenger information of a multi-segment flight, terminal information, resource demand information and authority verification information of the target terminal, a backup mode identifier, and failure information of the departure server.

[0009] Optionally, a resource control mechanism check is performed on multiple site terminals, and the inspection results obtained include: determining multiple items to be checked corresponding to the local backup business processing mode according to the preset resource control mechanism; and inspecting multiple site terminals based on the multiple items to be checked to determine the inspection results.

[0010] Optionally, based on the plurality of to-be-inspected items, the plurality of station ends are inspected to determine the inspection result, including: performing online state inspection on the plurality of station ends to obtain a first inspection result, wherein the first inspection result is used to represent whether the plurality of station ends are in real-time response state; performing flight resource usage situation inspection on the plurality of station ends to obtain a second inspection result, wherein the flight resource usage situation corresponds to flight resources including seat resources and baggage resources, and the second inspection result is used to represent whether there is backup handling resource conflict between the plurality of station ends; performing backup operation permission inspection on the target station end to obtain a third inspection result, wherein the third inspection result is used to represent whether the target station end has permission to perform backup operation on the multi-leg flight; performing business conflict inspection on the target station end and other station ends to obtain a fourth inspection result, wherein the fourth inspection result is used to represent whether there is business conflict between the target station end and other station ends; performing software and hardware system state inspection on the plurality of station ends to obtain a fifth inspection result, wherein the fifth inspection result is used to represent whether there is software compatibility exception or hardware stability exception in the plurality of station ends in the local backup business handling mode; and in response to the first inspection result, the second inspection result, the third inspection result, the fourth inspection result and the fifth inspection result satisfying a target condition, determining that the inspection result is that the multi-leg flight can be converted into the local backup business handling mode.

[0011] Optionally, the target condition that the first inspection result, the second inspection result, the third inspection result, the fourth inspection result and the fifth inspection result satisfy includes: determining that the plurality of station ends are in real-time response state according to the first inspection result; determining that there is no backup handling resource conflict between the plurality of station ends according to the second inspection result; determining that the target station end has permission to perform backup operation on the multi-leg flight according to the third inspection result; determining that there is no business conflict between the target station end and other station ends according to the fourth inspection result; and determining that there is no software compatibility exception and hardware stability exception in the plurality of station ends in the local backup business handling mode according to the fifth inspection result.

[0012] Optionally, the synchronization message is triggered to be generated by a backup action performed by the target station end, and data carried by the synchronization message is determined by an execution result of the backup action.

[0013] Optionally, the local backup business handling method further includes: responding to a message data pulling request of the plurality of station ends according to a preset period, and distributing a plurality of message data packets in the synchronization message corresponding to the plurality of station ends to the plurality of station ends, wherein the plurality of station ends have started a timing task, and the plurality of message data packets are used to update a local database of the plurality of station ends.

[0014] Optionally, the local backup business handling method further includes: in response to detecting a center end failure, sending a suspension handling message to the plurality of station ends, wherein the suspension handling message is used to represent that the center end suspends responding to the backup request.

[0015] Optionally, the local backup service handling method further comprises: performing statistical analysis on data carried by the backup request corresponding to the multi-leg flight and data carried by the synchronization message to obtain a statistical result; and displaying the statistical result in a graphical user interface.

[0016] According to another aspect of the embodiments of the present application, a local backup service handling system for a multi-leg flight is also provided, comprising: a center end and a plurality of station ends, wherein the plurality of station ends correspond to a plurality of stations corresponding to the multi-leg flight; when a target station end of the plurality of station ends detects a departure server failure, the target station end initiates a backup request for the multi-leg flight to the center end; the center end is configured to perform a resource control mechanism check on the plurality of station ends to obtain a check result, and return a backup response to the target station end when it is determined according to the check result that the multi-leg flight can be converted into a local backup service handling mode, wherein the backup response is used to assist the target station end to perform a backup action; the plurality of station ends are configured to perform the backup action according to the backup response, and send a synchronization message to the center end; the center end is configured to distribute the synchronization message to other station ends of the plurality of station ends except the target station end; and the other station ends are configured to update a local database according to the synchronization message, and perform local backup service handling for the multi-leg flight based on the updated local database.

[0017] In the embodiments of the present application, a backup request issued by a target station end of the plurality of station ends is received, wherein the backup request is triggered to be generated when the target station end detects a departure server failure; a resource control mechanism check is performed on the plurality of station ends to obtain a check result; and a backup response is returned to the target station end in response to a determination according to the check result that the multi-leg flight can be converted into a local backup service handling mode, wherein the backup response is used to assist the target station end to perform a backup action; and a synchronization message issued by the target station end is distributed to other station ends of the plurality of station ends except the target station end, wherein the synchronization message is used to update a local database of the other station ends, and the local database is used to support the other station ends to perform local backup service handling for the multi-leg flight. Thus, the present application achieves the purpose of automatically and efficiently completing flight conversion to local backup handling for the multi-leg flight through the interaction between the plurality of station ends in the center end of the local backup service handling system, thereby realizing the technical effects of improving the service handling efficiency, reducing the handling cost, improving the flight safety and user experience when performing flight conversion to local backup handling for the multi-leg flight, and further solving the technical problems of low efficiency, high cost, high safety risk and poor user experience of the scheme for performing flight conversion to local backup handling for the multi-leg flight. BRIEF DESCRIPTION OF DRAWINGS

[0018] The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application. In the drawings:

[0019] Figure 1 is a hardware structure block diagram of an optional terminal device for a local backup service handling method of a multi-leg flight according to an embodiment of the application;

[0020] Figure 2 is a flow chart of a local backup service handling method of a multi-leg flight according to an embodiment of the application;

[0021] Figure 3 is an optional flow chart of a multi-leg flight backup handling according to an embodiment of the application;

[0022] Figure 4 is an optional message synchronization process diagram according to an embodiment of the application;

[0023] Figure 5 is an optional station-side active pull scheme implementation diagram according to an embodiment of the application;

[0024] Figure 6 is a structure block diagram of a local backup service handling device of a multi-leg flight according to an embodiment of the application. DETAILED DESCRIPTION

[0025] In order to make the technical personnel in the art better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor should be within the scope of protection of the present application.

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

[0027] According to an embodiment of the present application, an embodiment of a local backup service handling method for multi-leg flights 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.

[0028] Figure 1 is a hardware structure block diagram of an optional terminal device for a local backup service handling method for multi-leg flights according to an embodiment of the present application, as shown in Figure 1 The terminal device can include one or more processors 102 (the processor 102 can include but not limited to a processing device such as a microcontroller unit (MCU) or a field programmable gate array (FPGA)), a memory 104 for storing data, and a transmission device 106 for communication function. In addition, it can also include a display device 110, an input / output device 108 (i.e. I / O device), a universal serial bus (USB) port (which can be included as one of the ports of the computer bus, not shown in the figure), a network interface (not shown in the figure), a power supply (not shown in the figure) and / or a camera (not shown in the figure). Those skilled in the art can understand that Figure 1 The structure shown is only schematic, which does not limit the structure of the terminal device 10 described above. For example, the terminal device can also include more or less components than those shown in Figure 1 or have a different configuration from that shown in Figure 1 .

[0029] It should be noted that the one or more processors 102 and / or other data processing circuits described above can be embodied in whole or in part as software, hardware, firmware or any other combination. In addition, the data processing circuit can be a single independent processing module, or all or part of it can be combined into any one of the other elements in the terminal device (or mobile device).

[0030] The memory 104 can be used to store software programs of application software and modules, such as program instructions / data storage devices corresponding to the local backup service handling method for multi-leg flights in the embodiments of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implements the local backup service handling method for multi-leg flights as described above. The memory 104 can include a high-speed random access memory, and can also include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some examples, the memory 104 can further include memories remotely arranged with respect to the processor 102, which can be connected to the terminal device through a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0031] The transmission device 106 is used to receive or send data via a network. Specific examples of the above-mentioned network can include a wireless network provided by a communication provider of the terminal device. In one example, the transmission device 106 includes a network adapter (NIC), which can be connected to other network devices through a base station so as to be able to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet in a wireless manner.

[0032] Under the above-mentioned operating environment, the embodiments of the present application provide a local backup service handling method for multi-leg flights as shown in Figure 2 which is applied to a center end of a local backup service handling system. The local backup service handling system further includes a plurality of station ends corresponding to multi-leg flights. Figure 2 is a flowchart of a local backup service handling method for multi-leg flights according to the embodiments of the present application, as shown in Figure 2 which includes the following implementation steps:

[0033] Step S201, receiving a backup request sent by a target station end in the plurality of station ends, wherein the backup request is triggered and generated when the target station end detects a departure server failure;

[0034] Step S202, performing resource control mechanism checking on the plurality of station ends to obtain a checking result;

[0035] Step S203, in response to determining that the multi-leg flight can be converted into a local backup service handling mode according to the checking result, returning a backup response to the target station end, wherein the backup response is used to assist the target station end to perform a backup action;

[0036] Step S204, distribute the synchronization message sent by the target station end to other station ends except the target station end, wherein the synchronization message is used to update the local database of other station ends, and the local database is used to support other station ends to perform local backup business handling for multi-leg flights.

[0037] The plurality of station ends includes the origin airport, the intermediate stop airport, and the destination airport corresponding to the multi-leg flight.

[0038] The target station end needs to convert the flight mode into the specific airport information system of the local backup handling mode when detecting the departure server failure or network anomaly.

[0039] The backup request can be a request sent to the center end system when the target station end detects the departure server failure. The backup request is used to transfer the flight information and business operation permission to the local to ensure that the service can still be provided for passengers in the case of failure.

[0040] In the application scenario, when the departure server of the target station end encounters a failure, the system automatically triggers the instruction to generate the backup request to cope with possible business interruption. The center end can timely receive the backup request from the target station end, which ensures that the backup mode can be quickly started when the departure system fails, reducing the impact on flight operation and passenger service.

[0041] The specific implementation of the resource control mechanism check can be that the center end checks the resource usage, online state, permission allocation, and other information of all station ends according to the backup request to ensure resource coordination and data consistency after the flight is converted to the local backup business handling mode.

[0042] The check result can be an evaluation report generated by the center end after checking the resource control mechanism of the plurality of station ends. The check result can be used to determine whether the multi-leg flight can be converted to backup.

[0043] Through the resource control mechanism check, the system can effectively avoid resource conflicts such as seat duplication allocation, and ensure that the business handling of the multi-leg flight in the local backup mode is efficient and safe.

[0044] The backup response can be the confirmation information sent by the center end to the target station end to allow backup. That is, after the resource control mechanism check, if it is confirmed that the flight can be converted to the local backup mode, the backup response is returned.

[0045] It should be noted that the backup response not only contains the indication of allowing backup, but also can contain specific backup operation guidelines, such as backup mode of flight data, resource locking strategy, etc., to assist the target station end to correctly perform the backup action.

[0046] By returning a backup response to the target station end when it is determined that the multi-leg flight can be converted to the local backup business handling mode, the authority handover between the center end and the target station end is realized, ensuring that the target station end can continue business operation safely and effectively in the backup mode, reducing service interruption caused by main system failure.

[0047] The above-mentioned synchronization message can be update information sent by the target station end to the center end after business operation in the local backup mode. The data carried by the synchronization message can include flight status, seat allocation, baggage information, etc.

[0048] In the application scenario, after receiving the synchronization message of the target station end, the center end broadcasts it to all related airport information systems, ensuring real-time synchronization of information. Through the distribution of the synchronization message, information sharing of multi-leg flights in the local backup mode is ensured, and all station ends can adjust the local database according to the latest information, avoiding problems caused by information delay or conflict, ensuring the continuity and accuracy of flight operation and passenger service.

[0049] It is easy to note that the technical scheme provided by the embodiment of the application can avoid data conflict between multiple stations when a multi-leg flight is converted to local backup handling. In addition, after automatic processing of the node with data conflict, the node can be displayed in the page, the flight report can be output based on the processing result of the node, and the station end can be notified.

[0050] In the application scenario, the local backup systems of multiple stations have an island nature and cannot achieve real-time communication after leaving the host, and simultaneous handling of passenger business by the same flight can easily cause data conflict. Through the embodiment of the application, the data synchronization degree between stations can be broken, real-time data communication can be established, communication cost between stations can be saved, and efficient backup handling of multi-leg flights can be realized.

[0051] Through the above steps S201 to S204, the embodiment of the application realizes that the multi-leg flight is quickly and safely converted to the local backup business handling mode when the departure system fails, and through the resource control and information synchronization of the center end, the consistency of flight data and the coordination of business operation are ensured, the risk of service interruption caused by system failure is reduced, and the overall stability of the civil aviation system and the convenience of passenger travel are improved.

[0052] In an embodiment of the present invention, a backup request is received from a target terminal among multiple terminal terminals, wherein the backup request is triggered when the target terminal detects a departure server failure; a resource control mechanism check is performed on the multiple terminal terminals to obtain an inspection result; in response to determining that a multi-segment flight can be converted into a local backup business processing mode according to the inspection result, a backup response is returned to the target terminal terminal, wherein the backup response is used to assist the target terminal terminal in performing the backup action; a synchronization message sent by the target terminal is distributed to other terminal terminals among the multiple terminal terminals except the target terminal terminal, wherein the synchronization message is used to update the local database of the other terminal terminals, and the local database is used to support the other terminal terminals in performing local backup business processing for the multi-segment flight. Therefore, the present invention achieves the purpose of automatically and efficiently completing the flight transfer to local backup for multi-segment flights through the interaction between multiple station terminals in the central terminal of the local backup business processing system, thereby realizing the technical effect of improving the business processing efficiency, reducing the processing cost, and improving the flight safety and user experience when transferring flights to local backup for multi-segment flights, and thus solving the technical problems of low efficiency, high cost, high security risk and poor user experience in the solution of transferring flights to local backup for multi-segment flights.

[0053] The above method of the embodiment of the present invention is further introduced below.

[0054] Optionally, in the above-mentioned local backup service processing method for multi-segment flights, the data carried in the backup request includes: flight information and passenger information of the multi-segment flight, terminal information, resource demand information and authority verification information of the target terminal, backup mode identifier, and failure information of the departure server.

[0055] In this application scenario, when the target terminal sends a backup request for a multi-segment flight to the central terminal, the request must include a series of key data to ensure that the central terminal can accurately understand and process the request. Specifically, the backup request typically includes the following data.

[0056] (1) Flight information, including flight number, departure date, origin, destination, and all flight segment information (including stops). Flight information is used to uniquely identify the multi-segment flight requested for backup.

[0057] (2) Requested airport information, i.e., the airport code of the target terminal and the specific time of the request. Requested airport information helps the center identify which airport initiated the request and determine the context of the request.

[0058] (3) Fault description information, which is used to describe the specific fault or problem encountered at the target terminal, such as “departure system network interruption”, “host server downtime”, etc., and to describe the current system status, such as whether departure protection has been implemented for the flight.

[0059] (4) Backup request, used to explicitly indicate the reason for requesting to switch to local backup mode, such as the need to handle check-in, luggage handling, etc., and to explicitly indicate the number of passengers and business types that may be involved.

[0060] (5) Resource requirements, used to list the resources that the target station end may need in backup mode, such as seat resources, luggage resources, etc., and to list the scope or quantity of specific resources.

[0061] (6) Permission declaration, used to confirm the target station end's permission to operate backup operations on multi-leg flights, and whether the center end needs to temporarily grant or adjust the permission.

[0062] (7) Security authentication information, including the target station end's authentication identifier, operator serial number, etc., to ensure the legality and security of the request.

[0063] (8) Message type identification, used to mark the message type of this request, to facilitate the message control center of the center end to identify and process.

[0064] In addition, the backup request message structure and data format design should take into account the need for efficient transmission and parsing, and usually uses standardized data formats to facilitate communication and data exchange between systems. In addition, in order to ensure the security and consistency of data, the backup message may also contain encryption information or check codes to prevent data tampering or loss during transmission.

[0065] Optionally, in step S202, the resource control mechanism check on the plurality of station ends to obtain the check result can further include the following execution steps:

[0066] Step S221, determining a plurality of to-be-checked items corresponding to the local backup business handling mode according to the preset resource control mechanism;

[0067] Step S222, checking the plurality of station ends based on the plurality of to-be-checked items to determine the check result.

[0068] In application scenarios, when the center end receives the backup request of the target station end, it will automatically identify and determine the key items that need to be checked when switching to the local backup business handling mode according to the preset resource control mechanism. These items cover all aspects of flight operations, ensuring that the conversion process can fully assess possible risks and problems.

[0069] Further, the center end checks the status and resources of each station end in real time or at regular intervals according to the preset resource control mechanism, including checking online status, resource usage, permission settings, and business conflict status, to ensure that all station ends can smoothly enter and maintain the local backup business handling state.

[0070] The steps S221 and S222 determine and implement comprehensive inspection on the local backup service handling mode through the preset resource control mechanism, ensure that the flight service mode can be quickly and safely converted to the local of the station end in the case of departure system failure or network anomaly, avoid the risk of flight operation interruption, and improve the emergency handling capability of the civil aviation system and the passenger service experience. This series of inspection and evaluation not only strengthens the stability of the system in the emergency state, but also promotes the efficient management and utilization of multi-leg flight resources, and is an important part of the civil aviation informatization construction.

[0071] Optionally, in the step S222, based on the plurality of to-be-inspected items, the plurality of station ends are inspected to determine the inspection result, and the step S222 can further include the following execution steps:

[0072] In the step S2221, online state inspection is performed on the plurality of station ends to obtain a first inspection result, wherein the first inspection result is used to represent whether the plurality of station ends are in a real-time response state.

[0073] In the step S2222, flight resource usage situation inspection is performed on the plurality of station ends to obtain a second inspection result, wherein the flight resource usage situation corresponds to flight resources including seat resources and baggage resources, and the second inspection result is used to represent whether there is a backup handling resource conflict between the plurality of station ends.

[0074] In the step S2223, backup operation permission inspection is performed on the target station end to obtain a third inspection result, wherein the third inspection result is used to represent whether the target station end has the permission to perform backup operation on the multi-leg flight.

[0075] In the step S2224, business conflict inspection is performed on the target station end and other station ends to obtain a fourth inspection result, wherein the fourth inspection result is used to represent whether there is a business conflict between the target station end and the other station ends.

[0076] In the step S2225, software and hardware system state inspection is performed on the plurality of station ends to obtain a fifth inspection result, wherein the fifth inspection result is used to represent whether there is a software compatibility exception or a hardware stability exception in the plurality of station ends under the local backup service handling mode.

[0077] In the step S2226, in response to the first inspection result, the second inspection result, the third inspection result, the fourth inspection result and the fifth inspection result satisfying a target condition, it is determined that the inspection result is that the multi-leg flight can be converted to the local backup service handling mode.

[0078] In the application scenario, the center end checks the resource control mechanism of multiple station ends, so as to ensure that the multi-leg flight can be safely and efficiently converted into a local backup business handling mode when the departure server or network fails. Specifically, the center end system checks the real-time online status of each station end (including the origin airport, intermediate stopover airport and destination airport) by sending periodic monitoring, that is, the online status check, to ensure that all related airports can respond to the instructions and messages of the center end in a timely manner, and obtain a first check result. The first check result is used to represent whether all station ends can meet the real-time response requirement.

[0079] Through the real-time online status check, it can be ensured that all station ends are in working state when converted to local backup mode, and can timely receive and process the instructions of the center end, avoiding flight information asynchronization and business operation delay caused by part of the airport offline, and enhancing the overall stability and response speed of the system.

[0080] Further, the center end analyzes the seat resource and baggage resource usage of each station end under multi-leg flight, to ensure that there is no resource conflict (such as seat duplication allocation) between airports when converted to local backup mode, which affects the normal travel of passengers (i.e. resource usage check), and obtains a second check result. The above-mentioned second check result is used to represent whether the flight resources of each station end have been reasonably allocated, and whether there is a risk of resource conflict.

[0081] The check of resource usage ensures that flight resources (such as seats and baggage) can be reasonably allocated and used in local backup mode, avoiding service interruption and passenger complaints caused by resource conflict, improving flight service quality and efficiency, and ensuring that multi-leg flights can still maintain normal operation when the departure system fails.

[0082] Further, the center end verifies whether the target station end is authorized to perform backup operation, that is, whether it has the right to convert the flight from the center mode to the local backup mode, completes the backup operation permission check, and obtains a third check result. The above-mentioned third check result is used to represent whether the target airport has the legal right to perform backup operation.

[0083] The above-mentioned permission check ensures that only authorized airports can perform backup operation, avoiding data confusion and security problems caused by unauthorized airports operating arbitrarily, and maintaining the security of the system and the standardization of business operation.

[0084] Further, the center end evaluates whether there is a business operation conflict (i.e. business conflict check) between the target station end and other station ends when performing backup, such as inconsistency of seat locking state, and obtains a fourth check result. The above-mentioned fourth check result is used to represent whether there is a business conflict that the multi-leg flight may encounter during the conversion process, such as seat duplication allocation or baggage handling conflict.

[0085] Through the business conflict check, the system can identify and avoid the business operation conflicts that may occur when the multi-leg flight is converted to the local backup mode, ensuring the business connection and data consistency between airports, and improving the accuracy of flight services and passenger satisfaction.

[0086] Further, the center end evaluates the system stability of each station end, including the compatibility of software and the availability of hardware, completes the software and hardware system state check, and obtains a fifth check result, ensuring that all airport systems can run smoothly in the local backup mode. The above-mentioned fifth check result is used to represent whether the software and hardware system of the multi-station end meets the running demand in the backup mode.

[0087] The system state check ensures that when the multi-leg flight is converted to the local backup mode, the software and hardware system of all station ends is in a healthy and compatible state, which can support the business operation in the backup mode, avoid service interruption caused by software incompatibility or hardware failure, and enhance the overall stability and reliability of the system.

[0088] By comprehensively evaluating all check results, the center end can make accurate judgments to decide whether to allow the multi-leg flight to be converted to the local backup business handling mode, ensuring that the flight can quickly and safely enter the backup mode when the system fails, continue to provide services for passengers, while avoiding potential business risks and safety problems, and maintaining the continuity of flight operation and the convenience of passenger travel.

[0089] Based on the above steps S2221 to S2226, the embodiments of the present application ensure that the multi-leg flight can be quickly, accurately and safely converted to the local backup business handling mode when the departure system fails through a series of detailed check steps. These checks cover online status, resource usage, permission allocation, business conflict and system health, not only improving the response speed in emergency situations, but also maintaining the stability and security of the system, ensuring the normal operation of the flight and the smooth travel of passengers. It is an important innovation in civil aviation informatization construction, which can significantly improve the service quality and emergency handling capacity.

[0090] Optionally, in the above local backup business handling method for multi-leg flights, the target conditions met by the first check result, the second check result, the third check result, the fourth check result and the fifth check result include:

[0091] According to the first check result, it is determined that the plurality of station ends are in a real-time response state;

[0092] According to the second check result, it is determined that there is no backup handling resource conflict between the plurality of station ends;

[0093] According to the third check result, it is determined that the target field station end has the permission to perform the backup operation on the multi-leg flight;

[0094] According to the fourth check result, it is determined that there is no business conflict between the target field station end and other field station ends;

[0095] According to the fifth check result, it is determined that there is no software compatibility exception and hardware stability exception in the local backup business handling mode of the plurality of field station ends.

[0096] In the application scenario, when the above five check results meet the target conditions, the center end determines that the check result is that the multi-leg flight can be converted to the local backup business handling mode. This process ensures that when the departure system or network fails, the flight service mode can be quickly and accurately converted to the local field station end, avoiding the risk of flight operation interruption and improving the emergency handling capability of the civil aviation system and the passenger service experience. The comprehensive check and evaluation of the center end not only strengthens the stability of the system in emergency state, but also promotes the efficient management and utilization of multi-leg flight resources, which is an indispensable important part of civil aviation informatization construction, and significantly improves the service quality and operation efficiency.

[0097] Optionally, in the local backup business handling method of the multi-leg flight, the synchronization message is triggered by the backup action performed by the target field station end, and the data carried by the synchronization message is determined by the execution result of the backup action.

[0098] In the application scenario, the target field station end interacts with the center end once for each business handled, that is, the target field station end triggers the generation of the synchronization message corresponding to the backup action after performing each backup action. The data carried by the synchronization message is determined by the execution result of the currently executed backup action.

[0099] Optionally, the local backup business handling method of the multi-leg flight can further include the following method steps:

[0100] Step S205, according to the preset period, respond to the message data pulling request of the plurality of field station ends, and distribute the plurality of message data packets corresponding to the plurality of field station ends in the synchronization message to the plurality of field station ends, wherein the plurality of field station ends have started the timing task, and the plurality of message data packets are used to update the local database of the plurality of field station ends.

[0101] In the application scenario, the center end responds to the message data pulling request from the plurality of field station ends according to the time interval set by the system (for example, every 10 seconds). This periodic time point ensures the periodic update of the message data, and guarantees the real-time and effectiveness of the information.

[0102] Further, the center end receives the backup action execution result of the target field station end, generates and stores the synchronization message. In response to the message data pulling request of other field station ends, the center end distributes the corresponding message data packet according to the message content and the receiving request airport. The information contained in the data packet is customized according to the needs of each airport, and only contains information related to the airport, which not only ensures the pertinence of the information, but also optimizes the data transmission efficiency.

[0103] Each of the above-mentioned multiple message data packets can contain flight status, passenger service, resource allocation and other information related to the requesting airport. In this way, the center end can accurately provide customized updates to each field station end, avoiding unnecessary information transmission, reducing data processing burden, while ensuring the accuracy and applicability of the information.

[0104] Further, after the field station end receives the message data packet related to itself, it will update the local database according to the information in the message data packet. This process ensures that the flight information and service status in the database of each airport are consistent with the synchronization message of the center end. Through the update of the database, the airport can accurately grasp the detailed situation of the flight, including the seat locking state, the luggage allocation situation and the passenger service record, so as to provide accurate service for passengers and avoid business conflicts caused by inconsistent information.

[0105] Based on step S205, the present application can construct an efficient information synchronization mechanism in a multi-leg flight local backup business handling scheme. By responding to the message data pulling request of multiple field station ends in a preset period, the center end can orderly distribute customized message data packets to all related airports, ensuring that each airport can update the local database in time to meet the operation needs of the flight in the backup mode. This mechanism not only optimizes the efficiency and pertinence of information transmission, but also effectively avoids data conflicts and resource competition, ensuring the continuity of flight operation and the high quality of passenger service in the local backup mode.

[0106] Alternatively, the local backup business handling method of the multi-leg flight can further include the following method steps:

[0107] Step S206, in response to detecting the center end failure, a suspension handling message is sent to the multiple field station ends, wherein the suspension handling message is used to represent that the center end suspends responding to the backup request.

[0108] The center end, as the information hub of the whole system, may not be able to provide normal service due to hardware failure, software error, network interruption or high traffic load. The fault detection mechanism is responsible for monitoring the running state of the center end, including its response time, message processing capacity, system load and other key indicators. Once it is found that the center end cannot meet the service demand, it is determined that the center end has failed, that is, the fault response process is triggered.

[0109] When the central end failure is detected, the system will automatically generate and send a suspension message to all relevant airports. The suspension message explicitly instructs all station ends to stop sending new backup requests to the central end, including multi-leg flight backup requests, resource locking requests, or business conflict checking requests, etc. This message is a key instruction to ensure system stability and avoid information confusion in emergency situations.

[0110] The suspension message conveys that the central end will suspend receiving and processing backup requests from the station end during the failure period. This not only includes requests for local backup mode, but also various resource and service requests made in backup mode, such as seat locking, boarding pass issuance, baggage handling, etc. By suspending the processing of requests, the central end can concentrate resources to solve its own failure, avoiding the burden of information processing during the failure period and reducing the risk of data inconsistency caused by failure.

[0111] Based on step S206, the embodiments of the present application not only ensure the stability of the entire system in emergency situations, but also provide convenience for failure recovery, effectively maintaining business continuity and passenger travel experience. This mechanism is an important part of the multi-leg flight local backup business handling scheme, ensuring that the system can quickly respond when the central end fails, take measures to prevent information confusion, and provide a stable and safe service environment for passengers.

[0112] Optionally, the above-mentioned multi-leg flight local backup business handling method can further include the following method steps:

[0113] Step S2071, statistical analysis is performed on the data carried by the backup request corresponding to the multi-leg flight and the data carried by the synchronization message, and a statistical result is obtained;

[0114] Step S2072, the statistical result is displayed in a graphical user interface.

[0115] In application scenarios, the central end comprehensively analyzes the backup request data and synchronization message data collected to understand the frequency of flight backup requests, the efficiency of backup mode conversion, resource usage, and the operation of multi-leg flights in backup mode, etc. Statistical analysis can evaluate the running effect of the backup mode, identify potential problems, and provide data support for optimizing system design and improving flight operation efficiency.

[0116] The graphical user interface is a visualization platform used by the central end to display statistical analysis results. The graphical user interface usually includes various charts, data lists, and index monitoring, helping system operators or managers to intuitively understand the processing of flight backup requests, the transmission efficiency of synchronization messages, the rationality of resource allocation, and the operation status of flights in backup mode, etc.

[0117] After completing the statistical analysis, the center end presents the statistical results to the operators or managers in a graphical manner. The presented statistical results include the response time of the backup request, the proportion of successful and failed requests, the receiving and processing status of the synchronization message, the number of resource conflicts, and the overall operation of the flight in the backup mode, etc. The result display helps to monitor the system performance in real time, discover problems in time, and make adjustments and optimization.

[0118] Based on steps S2071 to S2072, the embodiments of the present application enhance the transparency of the system and the decision-making ability of the operators through statistical analysis and result display of the backup request and synchronization message data, support real-time monitoring and optimization of the system performance, and improve the operation efficiency of the flight in the local backup mode and the passenger service experience.

[0119] The above technical solutions provided by the embodiments of the present application will be exemplarily described in combination with specific implementation scenarios.

[0120] Figure 3 is a flowchart of an optional multi-leg flight backup handling according to an embodiment of the present application. As shown in Figure 3 The center end can be a center end cluster, and the multiple station ends corresponding to the multi-leg flight can include an airport end A and an airport end B.

[0121] The center end can include a message module, a statistical module, and an authorization module. The message module of the center end is responsible for receiving the backup request and the synchronization message from the airport end, and broadcasting the notification and the instruction to each airport end, to ensure the real-time synchronization of information between all related station ends. The statistical module provides a web-based statistical interface for displaying and querying the statistical information of the multi-leg flight, including the flight status, the resource usage, etc., to facilitate monitoring and management. The authorization module is responsible for the permission control of the multi-leg flight, to ensure that only the authorized airport end can perform the flight local backup operation, and to maintain the security and consistency of the system.

[0122] The airport end (such as the airport end A and the airport end B) can include a message module and a background page operation module. The message module of the airport end is used to send the backup request and the synchronization message to the center end, and to parse the message distributed by the center end, to ensure the update and synchronization of the local database. The background page operation module provides an operation interface, allowing the check-in staff to perform the check-in, boarding, etc. of the flight and the passenger in the local backup mode, to ensure the continuity of the service and the passenger experience.

[0123] As shown in Figure 3 When the network fails or the departure server is unavailable, the flight enters the departure protection state, preventing further departure operations, to protect the integrity of the flight data. At this time, the fault airport (and Figure 3The airport terminal A sends a backup request to the center terminal. The check-in staff corresponding to the airport terminal A sends a backup request to the control center of the center terminal cluster, requesting whether the backup can be performed (full route commissioning is required).

[0124] Further, after receiving the backup request from the airport A, the control center of the center terminal cluster immediately checks the online status and resource availability of all airport terminals involved in the multi-leg flight. If all airport terminals are online and resources meet the requirements of local backup business handling, the center terminal generates and returns a true check result, allowing the airport terminal A to switch to the local backup mode. Otherwise, a false response is returned, indicating that the airport terminal A's backup request is rejected.

[0125] Further, when the airport terminal A receives the true response from the center terminal, it successfully switches to the local backup mode and starts sending synchronization messages to the center terminal. The message type is system event type, reporting the dynamic of local business handling.

[0126] Further, after receiving the synchronization message from the airport terminal A, the center terminal stores the synchronization message and initializes the status of the synchronization message to be distributed (e.g., NT), and then distributes the synchronization message to all related airport terminals according to the message content, to achieve information sharing and data synchronization.

[0127] Further, each airport terminal can start a timed pull task to actively obtain synchronization messages related to its airport from the center terminal and save them to the local database, ensuring the real-time and consistency of resource information.

[0128] Further, the airport terminal parsing thread processes the synchronization messages in the queue in order, updates the local database according to the message type (e.g., flight, passenger, seat, etc.), and writes the processing result back to the center terminal to update the message status, achieving bidirectional synchronization of data.

[0129] Further, the airport terminal continues to perform check-in, boarding and other business operations for passengers based on the synchronization message information stored in the local database, ensuring efficient and accurate service even in backup mode.

[0130] Through the implementation of the above architecture and process, the above technical solution provided by the embodiment of the application can effectively cope with the challenges of multi-leg flights in the case of departure system failure or network anomalies, ensuring that the flight can still smoothly perform business handling in backup mode, improving the stability of civil aviation services and passenger satisfaction. The close cooperation between the center terminal and the airport terminal not only solves the problem of resource conflict and information inconsistency, but also optimizes the efficiency and safety of business operations.

[0131] In the above specific implementation scenarios, the load balancing of the center end and the airport end also needs to be solved. The core of the load balancing mechanism is to achieve the purposes of optimizing resource utilization, enhancing throughput, shortening response time and preventing any single resource from being overloaded by reasonably allocating traffic and improving system reliability and high availability, thereby guaranteeing the smooth operation of the backup flight.

[0132] To this end, the above technical solution provided by the embodiments of the present application includes the following two strategies: first, the center end can deploy a message queue, and the airport end pulls messages from the message queue in real time. The characteristics of this strategy are excellent real-time performance, low delay, simplified consumption process of the airport end, and implementation based on a mature message consumption mode. Second, the airport end actively initiates data pulling by periodically polling the state of the center end. This strategy is easy to implement, has stronger controllability, can simplify the software architecture and reduce the risk of single-point failure, thereby achieving a better balance between cost and stability.

[0133] In the above specific implementation scenarios, the problem of reasonably managing shared resources to prevent business conflicts also needs to be solved. For example, after the airport end A allocates 12C seats to a passenger, if the airport end B does not obtain this update and still checks in other passengers for the seats, a conflict will be caused. After the flight is converted into a local backup mode, all operations related to shared resources, such as seat numbers and baggage numbers, must be coordinated through the center end to ensure the uniqueness and availability of the resources.

[0134] To this end, in the above technical solution provided by the embodiments of the present application, when the airport end processes seat-related business, if it needs to lock the 14A seat of the airport a to airport b segment, it should request the resource availability from the center end. The center end will return a Boolean value, true indicating that the resource is available, and the business process can continue; and false indicating that the seat has been occupied, which will prevent further operation of the airport end. When processing the request of the airport end, the center end uses a single-thread mode to query the database to ensure consistency in seat operations of the same flight. If there is no related locking record in the database, the locking operation is performed to lock the 14A seat of the airport a to airport b segment; after completing the resource allocation, the locking operation is released, and true is returned to the airport end at this time.

[0135] Through the above process, the center end effectively controls the shared resource operations of all airport ends, avoids business conflicts caused by resource conflicts in the backup mode of multi-segment flights, and ensures real-time synchronization of information and smooth operation of passenger services.

[0136] In the above specific implementation scenarios, the problem of message synchronization between airport ends also needs to be solved. For example, Figure 4As shown, the above technical solution provided by the embodiments of the present application involves three main message types between the airport terminals: flight messages, seat messages, and passenger messages. The flight messages are used to transmit flight status, the seat messages are used to transmit seat occupancy, and the passenger messages are used to transmit updates of passenger information.

[0137] First, after completing the service, the airport terminal B needs to send updates to the center terminal cluster:

[0138] The flight message contains specific flight information and actions (for example, "HEK-HRB / GSY+1"), and is used to notify changes in flight status.

[0139] The seat message records the use state of the seat in detail (for example, "HEK-HRB / 32AW / +OCC"), and ensures unified management of seat resources.

[0140] The passenger message uses an open format and carries updates of the full node of the passenger, so as to facilitate the center terminal cluster to comprehensively understand changes in passenger information.

[0141] Subsequently, the airport terminal A receives and parses the messages from the center terminal cluster:

[0142] Flight message parsing: the consumption module directly performs incremental parsing, updates local flight data, and realizes real-time synchronization of flight status.

[0143] Seat message parsing: the consumption module performs incremental parsing, updates the occupancy information of specific seats, and maintains the consistency of seat resources.

[0144] Passenger message parsing: the non-empty fields in the message will overwrite the local data (Database, referred to as DB) of the airport terminal A, and the parts that are not updated remain unchanged, ensuring the accuracy and integrity of passenger information.

[0145] Through the above mechanism, efficient and accurate message synchronization is realized between the airport terminal and the center terminal cluster, ensuring smooth business process of multi-leg flights in the local backup mode, and avoiding resource conflicts and passenger service interruptions caused by inconsistent information.

[0146] It should be noted that in the above specific implementation scenario, the active pull scheme is adopted by the embodiments of the present application for load balancing, and the heart beat interface can also be registered and maintained by the airport terminal to the center terminal, as shown. Figure 5 Through the registration and maintenance of the heart beat interface by the airport terminal to the center terminal, it is ensured that the center terminal can continuously monitor the server state of the airport terminal, and the airport terminal can independently manage the completeness, order and timeliness of the message, while ensuring the high availability and load balancing of itself.

[0147] Specifically, when the airport terminal (such as Figure 5When the open airport terminal A, the open airport terminal B, the open airport terminal C, and the open airport terminal D decide to switch to the backup mode according to the field conditions, if the central terminal solution has been deployed in the airport terminal, the flight backup request is sent to the central terminal; the central terminal checks the backup situation of all airport terminals of the route; if an airport terminal is offline, the backup request is rejected, and the process is terminated; if all airport terminals are online, the central terminal sends a backup notification to all, and confirms the backup request.

[0148] It should be noted that after the central terminal receives the backup request of the airport terminal, only the empty message carrying the flight information is broadcast to each related airport, and the central terminal updates the message state according to the analysis state of the message, and needs to consider the analysis progress of each airport. The processing flow of the broadcast message is: within a set period, the airport terminal uses a distributed lock to ensure that only one server can pull the message at a time, acquires the broadcast message belonging to the airport as needed, performs analysis and storage.

[0149] For example, the open airport terminal A initiates a backup request, the central terminal verifies that the open airport terminal B and the open airport terminal C are online in the multi-leg flight (marked as A-B-C-D), approves the request of the open airport terminal A, and notifies the open airport terminal B and the open airport terminal C. The open airport terminal B and the open airport terminal C actively pull the latest message from the center every 10 seconds, analyze and save it to the local database, and prepare for subsequent passenger business processing.

[0150] The airport terminal (such as Figure 5 The message pulling and analyzing mechanism of the open airport terminal A, the open airport terminal B, the open airport terminal C, and the open airport terminal D is as follows.

[0151] First, the pulling thread starts with the project, is controlled by the multi-leg mode deployment (the configuration item deployed-mode is set to 1), actively pulls the message every 10 seconds, ensures that only one server executes pulling at the same time, and continues immediately if 100 messages are not completed in each round, and waits for the next round if the pulling is completed.

[0152] Secondly, the analysis thread also starts with the project, runs in the multi-leg mode, actively queries the local database every 3 seconds, ensures that only one server queries at the same time, processes the first stored message in time sequence, processes 20 messages in each round, continues to query immediately if the processing is not completed, waits if the processing is completed, and updates the central terminal state according to the result after single-thread processing and independent operation.

[0153] From the above, the embodiment of the application adopts the active pulling scheme to ensure the accuracy and efficiency of information synchronization, effectively controls the load of the airport terminal and the central terminal, avoids the conflict in data processing, and provides a strong guarantee for the smooth operation of the multi-leg flight in the local backup mode.

[0154] Further, in the specific implementation scenario described above, after all the departure airports successfully switch to the backup mode, the multi-leg flight can smoothly carry out business in this mode. The tasks of the center include not only handling the flight transfer backup event, but also managing the transaction data of the airport in the backup mode, focusing on the update of flight information, passenger data and seat status.

[0155] In the technical solution described above, the message classification is designed as follows:

[0156] (1) Passenger message: the compressed message contains passenger full node information, which is used to synchronize passenger data;

[0157] (2) Seat message: message compression transmission, records the change of leg, seat and attribute, and ensures the unified control of seat resources;

[0158] (3) Flight message: after compression, the message reflects the change of flight field, and maintains the consistency of flight information.

[0159] In addition, for different resource types, the application embodiments design corresponding control implementations. For example, when the check-in clerk checks in the passenger 12A in the backup mode, it involves the occupation locking, fat locking and check locking of the seat. The occupation locking of the seat is automatically obtained or specified by the current airport, and the center is requested to lock, the data is inserted in TA_MUTEX_RESOURCE_CHECK, and the lock is returned successfully, otherwise the business is blocked. The seat locking release is requested by the current airport to the center to release the specified seat TA_MUTEX_RESOURCE_CHECK, and the specified data is deleted. The seat locking check is requested by the current airport to the center to check the locking status of the specified seat, and the specified data is searched in TA_MUTEX_RESOURCE_CHECK. true represents that the seat is locked, and false represents that the seat is not used.

[0160] The seat-related request is initiated by the airport end, but the related resources need to be limited, such as boarding number, baggage number, host number, etc. The central end uniformly controls and issues to each airport end. Taking the boarding number as an example. The airport end carries the maximum boarding number resource of the current station, such as 20, each time the request is made. The logic of the first request is to record the maximum value of the current flight to the database TA_MUTEX_RESOURCE_CHECK, and the update value 20+1 is returned to the requester (the database stores the maximum value 21 of the current flight). The subsequent request logic is to query the maximum value of the HOST type of the TA_MUTEX_RESOURCE_CHECKI of the current flight, and the update value 21+1 is returned to the requester (the database stores the maximum value 22 of the current flight). For example, A airport values the seat of passenger 12A, A airport needs to inform the center end that 12A is occupied, and the center end records that 12A is occupied. B airport will know that 12A is occupied when polling the center end message at regular intervals. When B airport also wants to value the seat of passenger 12A, an error prompt will be reported. Assuming that B airport does not parse the message of 12A being occupied at this time, B airport will be rejected by the center end when requesting to occupy 12A, prompting that the seat is not available, and B airport can only give the passenger a new seat for reception.

[0161] The above passenger backup transaction process can include: receiving a central passenger transaction message; parsing the transaction content; executing the content field of the transaction message to replace the content of the database. If the transaction fails, it needs to write back to the center end, write the message state and modify the error failure reason.

[0162] Through the above process, the technical scheme provided by the embodiment of the application realizes efficient resource management and passenger data synchronization of multi-leg flights after backup, ensures the smooth progress of the business in the backup mode, avoids the operation interruption caused by data conflict, and provides continuous and error-free service experience for passengers.

[0163] In the embodiment, a local backup business handling device for multi-leg flights is also provided. The device is used to realize the above-described embodiments and preferred embodiments, and will not be described again. As used below, a "module" can be a combination of software and / or hardware that realizes a predetermined function. Although the device described in the following embodiments is preferably realized in software, hardware or a combination of software and hardware is also possible and is conceived.

[0164] Figure 6 The structure block diagram of a local backup business handling device for multi-leg flights according to an embodiment of the application is shown in FIG. 1, which includes: Figure 6

[0165] ​The receiving module 601 is configured to receive a backup request sent by a target station terminal of the plurality of station terminals, wherein the backup request is triggered to be generated when the target station terminal detects a departure server failure;

[0166] The checking module 602 is configured to perform resource control mechanism checking on the plurality of station terminals to obtain a checking result.

[0167] The returning module 603 is configured to return a backup response to the target station terminal in response to determining that the multi-leg flight can be converted into the local backup business handling mode according to the checking result, wherein the backup response is used to assist the target station terminal to perform a backup action.

[0168] The distributing module 604 is configured to distribute a synchronization message sent by the target station terminal to other station terminals of the plurality of station terminals except the target station terminal, wherein the synchronization message is used to update a local database of the other station terminals, and the local database is used to support the other station terminals to perform local backup business handling for the multi-leg flight.

[0169] It should be noted that the above modules can be implemented by software or hardware, and for the latter, the following implementation manners can be used, but are not limited thereto: the above modules are located in the same processor; or the above modules are located in different processors in any combination.

[0170] According to another aspect of the embodiment of the present application, a computer readable storage medium is also provided, which comprises a stored program, wherein the program controls a device where the storage medium is located to perform the above-mentioned any one of the multi-leg flight local backup business handling method when the program is running.

[0171] Optionally, in the embodiment, the above storage medium can be configured to store a computer program for performing the following steps: receiving a backup request sent by a target station terminal of the plurality of station terminals, wherein the backup request is triggered to be generated when the target station terminal detects a departure server failure; performing resource control mechanism checking on the plurality of station terminals to obtain a checking result; returning a backup response to the target station terminal in response to determining that the multi-leg flight can be converted into the local backup business handling mode according to the checking result, wherein the backup response is used to assist the target station terminal to perform a backup action; and distributing a synchronization message sent by the target station terminal to other station terminals of the plurality of station terminals except the target station terminal, wherein the synchronization message is used to update a local database of the other station terminals, and the local database is used to support the other station terminals to perform local backup business handling for the multi-leg flight.

[0172] Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store computer programs.

[0173] According to another aspect of an embodiment of the present invention, a local backup business processing system for multi-segment flights is also provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute any one of the aforementioned local backup business processing methods for multi-segment flights.

[0174] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program: receiving a backup request from a target terminal among multiple terminal terminals, wherein the backup request is triggered when the target terminal terminal detects a departure server failure; performing a resource control mechanism check on the multiple terminal terminals to obtain an inspection result; in response to determining, based on the inspection result, that a multi-segment flight can be converted to a local backup business processing mode, returning a backup response to the target terminal terminal, wherein the backup response is used to assist the target terminal terminal in performing a backup action; distributing a synchronization message from the target terminal terminal to other terminal terminals among the multiple terminal terminals except the target terminal terminal, wherein the synchronization message is used to update the local database of the other terminal terminals, and the local database is used to support the other terminal terminals in performing local backup business processing for the multi-segment flight.

[0175] According to another aspect of an embodiment of the present invention, a local backup business processing system for multi-segment flights is also provided, including: a central end and multiple station ends, wherein the multiple station ends correspond to multiple stations corresponding to the multi-segment flight; when a target station end among the multiple station ends detects a departure server failure, the target station end initiates a backup request for the multi-segment flight to the central end; the central end is used to perform a resource control mechanism inspection on the multiple station ends, obtain the inspection results, and return a backup response to the target station end when it is determined according to the inspection results that the multi-segment flight can be converted to a local backup business processing mode, wherein the backup response is used to assist the target station end in performing the backup action; the multiple station ends are used to perform the backup action according to the backup response and send a synchronization message to the central end; the central end is used to distribute the synchronization message to other station ends among the multiple station ends except the target station end; the other station ends are used to update the local database according to the synchronization message, and perform local backup business processing for the multi-segment flight based on the updated local database.

[0176] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiment and its optional implementation manners, which will not be repeated here.

[0177] The serial numbers of the above embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments.

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

[0179] In the several embodiments provided by the present invention, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, 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.

[0180] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0181] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0182] 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, 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. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program code, such as a USB flash drive, ROM, RAM, mobile hard disk, magnetic disk or optical disk.

[0183] The above merely describes the preferred embodiments of the present application, and it should be pointed out that, for those skilled in the art, several improvements and refinements can be made without departing from the principles of the present application, and these improvements and refinements should also be considered as falling within the protection scope of the present application.

Claims

1. A local backup service handling method for a multi-leg flight, characterized by, The application relates to a local backup service processing system center end, the local backup service processing system further comprises a plurality of station ends corresponding to a plurality of multi-leg flights, and the local backup service processing method comprises the following steps: receiving a backup request sent by a target station end in the plurality of station ends, wherein the backup request is triggered and generated when a departure server fault is detected in the target station end; performing resource control mechanism checking on the plurality of station ends to obtain checking results, including: determining a plurality of checking items corresponding to the local backup service processing mode according to a preset resource control mechanism; based on the plurality of checking items, checking the plurality of station ends to determine the checking results; wherein, based on the plurality of checking items, checking the plurality of station ends to determine the checking results includes: performing online state checking on the plurality of station ends to obtain a first checking result, wherein the first checking result is used to represent whether the plurality of station ends are in a real-time response state; performing flight resource usage checking on the plurality of station ends to obtain a second checking result, wherein the flight resource usage corresponds to seat resources and baggage resources, and the second checking result is used to represent whether there is a backup processing resource conflict between the plurality of station ends; performing backup operation permission checking on the target station end to obtain a third checking result, wherein the third checking result is used to represent whether the target station end has the permission to perform backup operation on the multi-leg flight; performing business conflict checking on the target station end and other station ends to obtain a fourth checking result, wherein the fourth checking result is used to represent whether there is a business conflict between the target station end and the other station ends; performing software and hardware system state checking on the plurality of station ends to obtain a fifth checking result, wherein the fifth checking result is used to represent whether there is a software compatibility exception or a hardware stability exception in the plurality of station ends under the local backup service processing mode; and in response to the first checking result, the second checking result, the third checking result, the fourth checking result and the fifth checking result satisfying a target condition, determining that the checking result is that the multi-leg flight can be converted into the local backup service processing mode; in response to determining that the multi-leg flight can be converted into the local backup service processing mode according to the checking result, returning a backup response to the target station end, wherein the backup response is used to assist the target station end in performing backup actions; distributing a synchronization message sent by the target station end to other station ends except the target station end in the plurality of station ends, wherein the synchronization message is used to update a local database of the other station ends, and the local database is used to support the other station ends to perform local backup service processing on the multi-leg flight.

2. The local backup service handling method according to claim 1, characterized in that, The backup request carries data including flight information and passenger information of the multi-leg flight, station information, resource demand information and permission verification information of the target station end, a backup mode identifier and fault information of the departure server.

3. The local backup service handling method according to claim 1, characterized in that, The first check result, the second check result, the third check result, the fourth check result and the fifth check result satisfy the target condition, which includes: According to the first check result, it is determined that the multiple station ends are in the real-time response state; According to the second check result, it is determined that there is no backup handling resource conflict between the multiple station ends; According to the third check result, it is determined that the target station end has the permission to perform the backup operation on the multi-leg flight; According to the fourth check result, it is determined that there is no business conflict between the target station end and the other station ends; According to the fifth check result, it is determined that there is no software compatibility exception and hardware stability exception in the local backup business handling mode of the multiple station ends.

4. The local backup service handling method of claim 1, wherein, The synchronization message is triggered by the backup action performed by the target station end, and the data carried by the synchronization message is determined by the execution result of the backup action.

5. The local backup service handling method of claim 1, wherein, The local backup business handling method further includes: According to a preset period, respond to the message data pulling request of the multiple station ends, and distribute the multiple message data packets in the synchronization message corresponding to the multiple station ends to the multiple station ends, wherein the multiple station ends have started a timing task, and the multiple message data packets are used to update the local database of the multiple station ends.

6. The local backup service handling method of claim 1, wherein, The local backup business handling method further includes: In response to detecting a center end failure, a suspension handling message is sent to the multiple station ends, wherein the suspension handling message is used to represent that the center end suspends responding to the backup request.

7. The local backup service handling method of claim 1, wherein, The local backup business handling method further includes: Statistical analysis is performed on the data carried by the backup request corresponding to the multi-leg flight and the data carried by the synchronization message, and a statistical result is obtained; The statistical result is displayed in a graphical user interface.

8. A local backup service handling system for a multi-leg flight, characterized by It includes: A center end and multiple station ends, wherein the multiple station ends correspond to multiple stations corresponding to the multi-leg flight; When a target station end in the multiple station ends detects a departure server failure, the target station end initiates a backup request for the multi-leg flight to the center end; The center end is used to check the resource control mechanism of the multiple station ends to obtain a check result, and returns a backup response to the target station end when it is determined that the multi-leg flight can be converted to a local backup business handling mode according to the check result, wherein the backup response is used to assist the target station end to perform a backup action; Wherein, checking the resource control mechanism of the multiple station ends to obtain the check result, including: according to a preset resource control mechanism, determining multiple to-be-checked items corresponding to the local backup business handling mode; based on the multiple to-be-checked items, checking the multiple station ends to determine the check result; The multiple station ends are checked based on the multiple to-be-checked items, and the checking result is determined, including: performing online state checking on the multiple station ends to obtain a first checking result, wherein the first checking result is used to represent whether the multiple station ends are in a real-time response state; performing flight resource usage checking on the multiple station ends to obtain a second checking result, wherein the flight resource usage corresponds to flight resources including seat resources and baggage resources, and the second checking result is used to represent whether there is a backup handling resource conflict between the multiple station ends; performing backup operation permission checking on the target station end to obtain a third checking result, wherein the third checking result is used to represent whether the target station end has the permission to perform the backup operation on the multi-leg flight; performing business conflict checking on the target station end and other station ends to obtain a fourth checking result, wherein the fourth checking result is used to represent whether there is a business conflict between the target station end and the other station ends; performing software and hardware system state checking on the multiple station ends to obtain a fifth checking result, wherein the fifth checking result is used to represent whether there is a software compatibility exception or a hardware stability exception in the multiple station ends in the local backup business handling mode; and in response to the first checking result, the second checking result, the third checking result, the fourth checking result and the fifth checking result satisfying a target condition, determining that the checking result is that the multi-leg flight can be converted into the local backup business handling mode. The multiple station ends are used to perform backup actions according to the backup response, and send a synchronization message to the center end; The center end is used to distribute the synchronization message to other station ends in the multiple station ends except the target station end; The other station ends are used to update a local database according to the synchronization message, and perform local backup business handling for the multi-leg flight based on the updated local database.

Images