Data backup method, system and device

When the connection between the airport and the flight service platform is abnormal, the data backup method of the message platform and the backup platform is used to generate and send data backup messages, which solves the problem of passenger check-in abnormalities caused by the inability to obtain the flight service platform data, and realizes the normal progress of passenger check-in operation.

CN119336549BActive Publication Date: 2025-05-06TRAVELSKY TECHNOLOGY LIMITED
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202411870228.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-12-18
Publication Date
2025-05-06
Estimated Expiration
2044-12-18

AI Technical Summary

Technical Problem

When there is an abnormal connection between the airport and the flight service platform, the data in the flight service platform cannot be obtained, resulting in abnormal passenger check-in operation.

Method used

When listening to the message platform receiving the event notification, it obtains event notification from the message platform, obtains event data related to the event notification, generates data backup messages, and sends data backup messages to the backup platform to realize local backup of the data.

Benefits of technology

When the flight business platform is not available, passenger check-in is carried out through the data in the local backup platform to ensure the normal operation of passenger check-in operations and avoid passenger dissatisfaction and chaos in airport operation order due to abnormal connections.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119336549B_ABST
    Figure CN119336549B_ABST
Patent Text Reader

Abstract

The present application discloses a data backup method, system and device. It relates to the field of big data. The method comprises: obtaining the event notification from the message platform when monitoring that the message platform receives the event notification, wherein the event notification is sent from the flight service platform to the message platform; obtaining event data related to the event notification from the flight service platform; generating a data backup message according to the event notification and the event data; sending the data backup message to the message platform, wherein the message platform sends the data backup message to the backup platform. Through the present application, the problem in the related technology that when there is an abnormality in the connection between the airport and the flight service platform, the data in the flight service platform cannot be obtained, resulting in abnormalities in the passenger check-in operation is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of big data, and more specifically, to a data backup method, system, and device. Background Art

[0002] In the modern civil aviation industry, passenger check-in is an indispensable key link before boarding. Its efficiency and accuracy directly affect the passenger's travel experience and the airport's operating efficiency. The passenger check-in process involves the interaction and processing of multiple core data, including but not limited to flight data, passenger basic information data, passenger seat selection data, and passenger baggage check-in data. The real-time transmission and accurate processing of these data rely on the support of a stable and efficient information system.

[0003] Traditional passenger check-in systems usually seamlessly connect with flight business platforms through airport front-end service interfaces to achieve real-time data exchange and processing. Specifically, when passengers arrive at the airport and prepare to check in, the airport front-end service interface will send a request to the flight business platform to obtain flight data including flight status, seat layout, baggage allowance, etc., and verify the identity of the passenger and obtain basic passenger information based on the identity information provided by the passenger. Subsequently, the system assigns seats based on the passenger's choice or preset rules, handles baggage check-in, and finally generates an electronic boarding pass or prints a paper boarding pass to complete the check-in process.

[0004] However, in actual operation, such systems face risks and challenges that cannot be ignored, especially emergencies such as network failures or flight business platform failures. Once the airport front-end service interface cannot establish a stable connection with the flight business platform, it will lead to a series of chain reactions: first, the system cannot obtain the latest flight data in real time, including whether the flight is delayed, canceled or the seat is changed, which will directly affect the passengers' itinerary arrangements; second, the core links such as passenger basic information verification, seat allocation and baggage check-in will not be able to proceed, resulting in passengers unable to complete check-in normally; finally, long-term failures may also cause passenger dissatisfaction, aggravate airport congestion and chaos, and have a negative impact on the airport's operating order and brand image.

[0005] With regard to the problem in the related technology that when there is an abnormality in the connection between the airport and the flight business platform, the data in the flight business platform cannot be obtained, resulting in abnormal passenger check-in operations, no effective solution has been proposed yet. Summary of the invention

[0006] The present application provides a data backup method, system and device to solve the problem in the related art that when there is an abnormality in the connection between the airport and the flight service platform, the data in the flight service platform cannot be obtained, resulting in abnormal passenger check-in operations.

[0007] According to one aspect of the present application, a data backup method is provided. The method includes: obtaining the event notification from the message platform when monitoring that the message platform receives the event notification, wherein the event notification is sent from the flight service platform to the message platform; obtaining event data related to the event notification from the flight service platform; generating a data backup message according to the event notification and the event data; and sending the data backup message to the message platform, wherein the message platform sends the data backup message to the backup platform.

[0008] Optionally, before obtaining event data related to the event notification from the flight business platform, the method also includes: obtaining an event identifier in the event notification, and determining the event type of the event to be backed up indicated by the event notification based on the event identifier; judging whether the event type is a preset event type, wherein the preset event type is used to characterize the object of the event to be backed up; if the event type is the preset event type, executing the operation of obtaining event data related to the event notification from the flight business platform; if the event type is not the preset event type, deleting the obtained event notification.

[0009] Optionally, obtaining event data related to the event notification from the flight business platform includes: obtaining event attribute information carried in the event notification, wherein the event attribute information is used to determine the event to be backed up indicated by the event notification; sending the event attribute information to the flight business platform, and receiving the event data of the event notification sent by the flight business platform.

[0010] Optionally, generating a data backup message based on the event notification and event data includes: obtaining an event identifier carried in the event notification, and obtaining attribute information of the event to be backed up indicated in the event notification from the event notification, wherein the attribute information includes at least one of the following: time information, airport name, flight number; combining the event identifier, attribute information and event data to obtain a data backup message.

[0011] Optionally, after sending the data backup message to the message platform, the method also includes: receiving the message sending result sent by the message platform; storing the event notification and the message sending result in a message sending record table in association with each other; and sending the message sending record table to the message platform when a record table query request is received from the message platform.

[0012] According to another aspect of the present application, a data backup method is provided. The method includes: receiving an event notification sent by a flight service platform, and obtaining an event identifier and attribute information in the event notification; determining an event storage queue for storing the event notification according to the event identifier and attribute information, and storing the event notification in the event storage queue, wherein the event storage queue is monitored by a message generation platform; upon receiving a data backup message associated with the event notification sent by the message generation platform, storing the data backup message in the message storage queue according to the event identifier and attribute information, and sending the data backup message to the backup platform, wherein the message storage queue is associated with the event identifier and attribute information.

[0013] Optionally, the method also includes: when a message sending record table sent by a message generation platform is received, comparing the event notification recorded in the message sending record table with the event notification stored in the event storage queue to obtain a comparison result, wherein the message sending record table stores event notifications corresponding to each message sent by the message generation platform and the message sending result; when the comparison result indicates that the event notification recorded in the message sending record table is consistent with the event notification stored in the event storage queue, determining that the message generation platform is running normally; when the comparison result indicates that the event notification recorded in the message sending record table is inconsistent with the event notification stored in the event storage queue, determining that there is an abnormality in the operation of the message generation platform, and generating a prompt message, wherein the prompt message is used to indicate that there is an abnormality in the operation of the message generation platform.

[0014] According to another aspect of the present application, a data backup system is provided. The system includes: a flight service platform, which is used to send an event notification to a message platform; the message platform, which is used to determine an event storage queue according to the event identifier and attribute information of the event notification when receiving the event notification, and store the event notification in the event storage queue, and when receiving a data backup message associated with the event notification sent by the message generation platform, store the data backup message in the message storage queue according to the event identifier and attribute information, and send the data backup message to the backup platform, wherein the message storage queue is associated with the event identifier and attribute information; the message generation platform, which is used to obtain the event notification from the message platform when monitoring that the message platform receives the event notification, and obtain event data related to the event notification from the flight service platform, generate a data backup message according to the event notification and the event data, and send the data backup message to the message platform; the backup platform, which is used to store the data backup message according to the event identifier and attribute information of the data backup message when receiving the data backup message.

[0015] According to another aspect of the present application, a data backup device is provided. The device includes: a first acquisition unit, which is used to acquire an event notification from a message platform when monitoring that the message platform receives an event notification, wherein the event notification is sent from the flight service platform to the message platform; a second acquisition unit, which is used to acquire event data related to the event notification from the flight service platform; a generation unit, which is used to generate a data backup message according to the event notification and the event data; and a first sending unit, which is used to send the data backup message to the message platform, wherein the message platform sends the data backup message to the backup platform.

[0016] According to another aspect of the present application, another data backup device is provided. The device includes: a first receiving unit, used to receive an event notification sent by a flight service platform, and obtain an event identifier and attribute information in the event notification; a determining unit, used to determine an event storage queue for storing the event notification according to the event identifier and attribute information, and store the event notification in the event storage queue, wherein the event storage queue is monitored by a message generation platform; a storage unit, used to store the data backup message in the message storage queue according to the event identifier and attribute information when receiving a data backup message associated with the event notification sent by the message generation platform, and send the data backup message to the backup platform, wherein the message storage queue is associated with the event identifier and attribute information.

[0017] According to another aspect of the present invention, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, a data backup method provided in the aforementioned embodiment of the present application is implemented.

[0018] According to another aspect of the present invention, an electronic device is provided, comprising one or more processors and a memory; the memory stores computer-readable instructions, and the processor is used to execute the computer-readable instructions, wherein when the computer-readable instructions are executed, a data backup method provided in the aforementioned embodiment is executed.

[0019] Through this application, the following steps are adopted: when monitoring the message platform receiving the event notification, obtain the event notification from the message platform, wherein the event notification is sent by the flight service platform to the message platform; obtain the event data related to the event notification from the flight service platform; generate a data backup message according to the event notification and the event data; send the data backup message to the message platform, wherein the message platform sends the data backup message to the backup platform. The problem that the data in the flight service platform cannot be obtained when there is an abnormality in the connection between the airport and the flight service platform in the related technology, resulting in abnormal passenger check-in operation, is solved. The event notification sent by the flight service platform is received by the receiving message platform, and the corresponding data is obtained from the flight service platform according to the event notification, and further combined into a message according to the event data and the event notification, and the events stored in the flight service platform are backed up to the local backup platform in the form of a message, so that the user can directly obtain the flight-related data through the local backup platform, and then when the flight service platform cannot be used, the passenger check-in is performed according to the data in the local backup platform, achieving the technical effect of ensuring the normal check-in operation of the passenger. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0021] Figure 1 is a flow chart of a data backup method provided according to an embodiment of the present application;

[0022] Figure 2 is a flow chart of another data backup method provided according to an embodiment of the present application;

[0023] Figure 3 is a schematic diagram of a data backup system provided according to an embodiment of the present application;

[0024] Figure 4 is a schematic diagram of a data backup device provided according to an embodiment of the present application;

[0025] Figure 5 is a schematic diagram of another data backup device provided according to an embodiment of the present application;

[0026] Figure 6 It is a schematic diagram of an electronic device provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0027] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

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

[0029] 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 are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0030] It should be noted that the data backup method, system and device determined in the present disclosure can be used in the field of big data, and can also be used in any field other than the field of big data. The application field of the data backup method, system and device determined in the present disclosure is not limited.

[0031] It should be noted that the collected information, user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) used in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data are in compliance with the relevant laws, regulations and standards of the relevant regions, necessary confidentiality measures are taken, and public order and good customs are not violated. Corresponding operation portals are provided for users to choose to authorize or refuse to use. For example, an interface is set up between this system and relevant users or organizations. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or organization.

[0032] The embodiments or examples of the present disclosure are not exhaustive, but are only illustrative of some embodiments or examples, and are not intended to be specific limitations on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment or example can be implemented as an independent example, and the steps can be combined arbitrarily. For example, the scheme after removing some steps in a certain embodiment or example can also be implemented as an independent example, and the order of the steps in a certain embodiment or example can be arbitrarily exchanged. In addition, the optional methods or optional examples in a certain embodiment or example can be combined arbitrarily; in addition, the various embodiments or examples can be combined arbitrarily, for example, some or all steps of different embodiments or examples can be combined arbitrarily, and a certain embodiment or example can be combined arbitrarily with the optional methods or optional examples of other embodiments or examples.

[0033] According to an embodiment of the present application, a data backup method is provided.

[0034] Figure 1 1 is a flow chart of a data backup method provided according to an embodiment of the present application. Figure 1 As shown, the method comprises the following steps:

[0035] Step S101, when monitoring that the message platform receives an event notification, obtain the event notification from the message platform, wherein the event notification is sent from the flight service platform to the message platform.

[0036] It should be noted that the execution subject of this embodiment is the message generation platform, and the event notification can be an event notification generated by the flight business platform according to the event data sent by the passenger after receiving the passenger event (such as adding or modifying flight or passenger or seat data) sent by the passenger through the airport front-end service interface or client, so as to represent the event data through the event notification. The message platform can be used to transfer messages and notifications between multiple platforms, so as to decouple multiple platforms and asynchronously send messages between platforms.

[0037] It should be noted that the flight business platform can process flight-related information, passenger-related information, baggage-related information, etc., that is, all business information related to boarding can be processed by the flight business platform.

[0038] Specifically, after the flight service platform receives the newly added passenger information sent by the passenger, it can store the newly added passenger information according to its specific content and send the information to the message platform through an event notification. The event notification can include the flight name, user information, event type, etc., thereby representing the event data corresponding to the event notification.

[0039] Furthermore, the executor of this embodiment is a message generation platform, which continuously monitors whether the message platform receives event notifications, and when receiving event notifications, obtains the event notifications from the message platform, thereby generating corresponding storage messages according to the content in the event notifications.

[0040] It should be noted that the message generation platform can, based on information such as the airlines and airports to which the platform belongs, only monitor event notifications in the message platform that are associated with the airlines and airports to which the platform belongs, thereby reducing the number of event notifications obtained and stored in the message platform while ensuring the completeness and accuracy of the received event notifications.

[0041] Step S102, acquiring event data related to the event notification from the flight service platform;

[0042] Specifically, when an event notification is received, since the event notification only contains partial information but not all the information of the event, it is necessary to obtain event data related to the event notification from the flight business platform, so that when storing the event, the event data and the event notification are associated and stored to ensure the integrity of the event data of the passenger event.

[0043] For example, an event notification could look like this:

[0044] {"eventType":"PSL","opStatusType":"PSL","airline":"ZH","flightNumber":9755,"flightDate":"2023-10-10","departureDate":"2023-10-10","opAirport":"YTY"," hostNumber":186,"departureAirport":"YTY","arrivalAirport":"XMN","passengerSurname":"ZHANGSAN","bagInfoList":[],"timestamp":"2023-11-2415:56:51.894"};

[0045] It contains information such as time, passenger name, flight number, etc., but does not include the specific event data of the event sent by the user, such as flight changes, passenger information changes, etc., which are not displayed in the event notification. Therefore, it is necessary to obtain the event data based on the event notification, so as to store the event notification and event data together in the backup platform to ensure the integrity of the data.

[0046] It should be noted that after receiving the event notification, when storing the event notification, it is necessary to store each event notification in order according to the time when it was generated, so as to ensure the time accuracy of each event notification.

[0047] Step S103: Generate a data backup message according to the event notification and event data.

[0048] Specifically, after obtaining the event notification and the event data, the event notification and the event data may be combined to obtain a data backup message regarding the event.

[0049] For example, when receiving event notifications and event data, first determine the specific requirements that need to be included in the data backup message, including backup scope, strategy, target location, etc. Then, generate structured data backup operation instructions based on this information, and then generate data backup messages based on the data backup operation instructions according to the message format requirements and message content requirements, so that the data to be backed up is stored in the data backup message, and then the data to be backed up is transmitted to the backup platform by transmitting the message.

[0050] Step S104, sending the data backup message to the message platform, wherein the message platform sends the data backup message to the backup platform.

[0051] Specifically, after obtaining the data backup message, the data backup message can be sent to the message platform, and then the data backup message can be transferred to the backup platform through the message platform, and then the data transmission operation can be completed through the message platform, and the message storage operation can be completed at the same time, so that the data is stored in the backup platform. When it is necessary to obtain the parameters of an event from the backup platform, the corresponding message can be directly queried in the backup platform, and the message can be parsed to obtain the event data, thereby ensuring that when passenger information is needed, it can be obtained from the locally configured backup platform, avoiding the inability to obtain passenger data when the flight business platform fails or cannot connect to the flight business platform.

[0052] The data backup method provided in the embodiment of the present application obtains the event notification from the message platform when monitoring the message platform receiving the event notification, wherein the event notification is sent by the flight service platform to the message platform; obtains the event data related to the event notification from the flight service platform; generates a data backup message according to the event notification and the event data; and sends the data backup message to the message platform, wherein the message platform sends the data backup message to the backup platform. The method solves the problem that in the case of an abnormal connection between the airport and the flight service platform in the related technology, the data in the flight service platform cannot be obtained, resulting in an abnormal check-in operation of the passenger. The event notification sent by the flight service platform is received by the receiving message platform, and the corresponding data is obtained from the flight service platform according to the event notification, and further combined into a message according to the event data and the event notification, and the events stored in the flight service platform are backed up to the local backup platform in the form of a message, and then when the flight service platform cannot be used, the passenger check-in is performed according to the data in the local backup platform, thereby achieving the technical effect of ensuring the normal check-in operation of the passenger.

[0053] Optionally, in the data backup method provided in the embodiment of the present application, before obtaining event data related to the event notification from the flight business platform, the method also includes: obtaining an event identifier in the event notification, and determining the event type of the event to be backed up indicated by the event notification based on the event identifier; judging whether the event type is a preset event type, wherein the preset event type is used to characterize the object of the event to be backed up; if the event type is the preset event type, executing the operation of obtaining event data related to the event notification from the flight business platform; if the event type is not the preset event type, deleting the obtained event notification.

[0054] It should be noted that after the message generation platform receives the event notification sent by the message platform, since not all event notifications are passenger notifications that need to be stored, there may be other time-sensitive or unimportant event notifications. Therefore, there is no need to back up and store the above event notifications.

[0055] Therefore, after receiving the event notification, it is necessary to determine whether the event notification is a notification that needs to be stored, and after obtaining the determination result, further storage is performed.

[0056] Specifically, after receiving the event notification, the event identifier in the event notification can be obtained, and the event type of the event to be backed up indicated by the event notification can be determined according to the event identifier, so as to determine whether the event data corresponding to the event notification needs to be backed up and stored according to the event type. After obtaining the event identifier, the event identifier can be compared with the identifier in the identifier comparison table to determine the event type of the event.

[0057] For example, Table 1 is an optional identification comparison table. As shown in Table 1, when the event identification is "eventType: "PSL", opStatusType: "PSL"", it indicates that the event type corresponding to the identification is a passenger increment event.

[0058] Table 1

[0059]

[0060] Furthermore, after obtaining the event type, it is necessary to determine whether the event type is a preset event type, and if the event type is a preset event type, it indicates that the event notification needs to be stored, and therefore a corresponding data backup message needs to be generated according to the event notification.

[0061] When the event type is not a preset event type, it indicates that the event data of the event notification does not need to be stored. In this case, the event notification can be directly deleted, thereby completing the screening operation of the event notification.

[0062] For example, when it is determined that the notification type of an event notification is a "passenger increment event", and the preset event types include: "new event", "flight increment event", "passenger increment event", and "baggage increment event", the event type representing the event notification is the preset event type, then a data backup message of this event type is generated.

[0063] Furthermore, when it is determined that the event type of an event notification is a preset event type, it is also necessary to determine whether the event type is an incremental event type. When the event type is an incremental event type, it is necessary to determine whether there is a full event notification with the same flight information as the incremental event notification in the database. When there is a full event notification with the same flight information as the incremental event, the subsequent process of processing the incremental event notification can be executed. When there is no full event notification with the same flight information as the incremental event, the incremental event is deleted, thereby ensuring the accuracy of the received and stored incremental events.

[0064] This embodiment screens event notifications by determining the event types of the event notifications, thereby reducing the workload of the message generation platform and improving the message generation efficiency.

[0065] Optionally, in the data backup method provided in an embodiment of the present application, obtaining event data related to the event notification from the flight business platform includes: obtaining event attribute information carried in the event notification, wherein the event attribute information is used to determine the event to be backed up indicated by the event notification; sending the event attribute information to the flight business platform, and receiving the event data of the event notification sent by the flight business platform.

[0066] Specifically, when obtaining event data, since the message platform only contains event notifications but not event data, it is necessary to obtain event data from the flight business platform. When obtaining event data, the event attribute information of the passenger event can be first obtained from the event notification, and the event attribute information is sent to the flight business platform. The flight business platform obtains the event data of the corresponding passenger event in the database through the event attribute information, and sends the event data to the message generation platform, thereby completing the event data acquisition operation.

[0067] It should be noted that when obtaining event data, further screening and acquisition of event data can be performed according to the event type. If the event type is a new event, all event data under the event can be obtained. If the event type is an incremental event, only the relevant event data that needs to be added or modified can be obtained without obtaining all event data.

[0068] That is, after determining the event data corresponding to the passenger event based on the attribute information, the event data can also be filtered according to the event type, retaining only the event data that needs to be added or modified, thereby reducing the amount of data in the content of the subsequently generated data backup message and improving data storage efficiency.

[0069] Optionally, in the data backup method provided in an embodiment of the present application, generating a data backup message based on event notification and event data includes: obtaining an event identifier carried in the event notification, and obtaining attribute information of the event to be backed up indicated in the event notification from the event notification, wherein the attribute information includes at least one of the following: time information, airport name, flight number; combining the event identifier, attribute information and event data to obtain a data backup message.

[0070] Specifically, after obtaining the event notification and event data, the notification needs to be parsed to extract the event identifier, and at the same time, the attribute information of the event to be backed up needs to be captured from the event notification, including but not limited to time information, airport name and flight number. After the message is generated, the above content will be used to locate the event data, and then when querying the message, the message can be queried according to the above content to obtain the message content in the message.

[0071] Furthermore, when generating a message, it is necessary to integrate the event identifier, attribute information and event data. When integrating the event identifier, attribute information and event data into a message, it is necessary to determine the specific instructions, data types, storage requirements and other detailed information required to perform the backup, so as to determine the specifications and requirements of the message based on the above information, thereby ensuring the accuracy of the generated message, so that the generated backup message can successfully execute subsequent backup operations.

[0072] Furthermore, after determining the information and requirements in the process of generating a message, the event identifier, attribute information and event data can be integrated into a message according to the above information and requirements, thereby obtaining a data backup message for the passenger event. The event identifier and attribute information in the message can be used to store the message and to query the data backup message in the backup platform.

[0073] This embodiment integrates the event identifier, attribute information and event data into a passenger event message, thereby ensuring the accuracy of the message content and the accuracy of subsequent storage and query of the message.

[0074] Optionally, in the data backup method provided in the embodiment of the present application, after sending the data backup message to the message platform, the method also includes: receiving the message sending result sent by the message platform; associating the event notification and the message sending result and storing them in a message sending record table; and sending the message sending record table to the message platform when a record table query request sent by the message platform is received.

[0075] Specifically, after sending the data backup message to the message platform, the message platform will send the data backup message to the backup platform, and send a message sending result to the message generation platform, wherein the message sending result includes a successful sending or a sending failure.

[0076] Furthermore, regardless of whether the message is sent successfully or unsuccessfully, the message generation platform needs to associate the event notification of the message and the message sending result and store them in the message sending record table, thereby recording the message sending situation in the record table, and providing guidance for subsequent maintenance of the message generation platform. At the same time, it is also possible to determine whether the message generation platform has accurately monitored each event notification of the message platform based on the message sending record table, thereby ensuring the accuracy of the generated message and avoiding the phenomenon that some passenger events are not backed up due to failure to monitor the event notification.

[0077] This embodiment ensures the accuracy and completeness of the passenger sending event by generating a message sending record table.

[0078] According to an embodiment of the present application, another data backup method is provided.

[0079] Figure 2 FIG. 1 is a flow chart of another data backup method provided according to an embodiment of the present application. Figure 2 As shown, the method comprises the following steps:

[0080] Step S201: receiving an event notification sent by a flight service platform, and obtaining an event identifier and attribute information in the event notification.

[0081] Specifically, after the flight business platform receives and stores the passenger event, the message platform needs to receive the event notification sent by the flight business platform based on the passenger event, and obtain the event identifier and attribute information in the event notification, so as to determine the storage queue where the event notification is stored based on the event identifier and attribute information, and then store the event notification in the storage queue, so that the message generation platform that monitors the storage queue can obtain the event notification in time.

[0082] For example, the event type is determined based on the event identifier, and the event, flight, airport and other information of the passenger event are determined based on the attribute information, so that the type of event notification in each storage queue is consistent and they are event notifications for the same flight at the same airport on the same date.

[0083] Step S202: determine an event storage queue for storing event notifications according to the event identifier and attribute information, and store the event notifications in the event storage queue, wherein the event storage queue is monitored by the message generation platform.

[0084] Specifically, after obtaining the event identifier and attribute information, the event notification can be stored in the storage queue corresponding to the event identifier and attribute information according to the event identifier and attribute information, thereby ensuring that the report generation platform monitoring the storage queue can obtain the event notification in time.

[0085] Step S203, when receiving the data backup message associated with the event notification sent by the message generation platform, the data backup message is stored in the message storage queue according to the event identifier and attribute information, and the data backup message is sent to the backup platform, wherein the message storage queue is associated with the event identifier and attribute information.

[0086] Specifically, after receiving the data backup message sent by the message generation queue, the data backup message needs to be stored in the message storage queue according to the event identifier and attribute information, so as to partition the data backup message for easy management of the backup message.

[0087] Furthermore, the messages in the same message storage queue can be synchronously stored in the backup platform in the order of storage time, thereby ensuring that the messages with the same attributes and the same type in the backup platform are stored in the same area, thereby ensuring the accuracy of data storage.

[0088] The data backup method provided by the embodiment of the present application receives an event notification sent by a flight service platform, and obtains the event identifier and attribute information in the event notification; determines the event storage queue for storing the event notification according to the event identifier and attribute information, and stores the event notification in the event storage queue, wherein the event storage queue is monitored by the message generation platform; upon receiving a data backup message associated with the event notification sent by the message generation platform, stores the data backup message in the message storage queue according to the event identifier and attribute information, and sends the data backup message to the backup platform, wherein the message storage queue is associated with the event identifier and attribute information. This solves the problem in the related art that when there is an abnormality in the connection between the airport and the flight service platform, the data in the flight service platform cannot be obtained, resulting in abnormal passenger check-in operations. The message receiving platform receives event notifications sent by the flight business platform, obtains corresponding data from the flight business platform based on the event notification, further combines the event data and event notification into a message, and backs up the events stored in the flight business platform to the local backup platform in the form of a message. In the event that the flight business platform cannot be used, passenger check-in is performed based on the data in the local backup platform, thereby achieving the technical effect of ensuring normal check-in operations for passengers.

[0089] Optionally, in the data backup method provided in the embodiment of the present application, the method also includes: when a message sending record table sent by a message generation platform is received, comparing the event notification recorded in the message sending record table with the event notification stored in the event storage queue to obtain a comparison result, wherein the message sending record table stores event notifications corresponding to each message sent by the message generation platform and the message sending result; when the comparison result indicates that the event notification recorded in the message sending record table is consistent with the event notification stored in the event storage queue, determining that the message generation platform is running normally; when the comparison result indicates that the event notification recorded in the message sending record table is inconsistent with the event notification stored in the event storage queue, determining that there is an abnormality in the operation of the message generation platform, and generating a prompt message, wherein the prompt message is used to indicate that there is an abnormality in the operation of the message generation platform.

[0090] Specifically, after receiving the message sending record table sent by the message generation platform, it is necessary to compare the event notification recorded in the message sending record table with the event notification stored in the event storage queue, so as to determine whether there is a difference between the event notification recorded in the message sending record table and the event notification stored in the event storage queue, and in the case that there is no difference, it indicates that the message generation platform can accurately monitor each event notification, and generate and send the corresponding message according to the event notification. At this time, it can be determined that the message generation platform is operating normally. When the comparison result indicates that the event notification recorded in the message sending record table is inconsistent with the event notification stored in the event storage queue, it indicates that the message generation platform has missed some event notifications. Therefore, it can be determined that the message generation platform cannot monitor the message platform normally, or cannot generate and transmit messages normally. At this time, it is determined that the message generation platform is abnormal and needs to be repaired.

[0091] This embodiment compares the event notification recorded in the message sending record table with the event notification stored in the event storage queue, thereby determining the running state of the message generation platform, thereby ensuring that the message generation platform can run normally.

[0092] Figure 3 is a schematic diagram of a data backup system provided according to an embodiment of the present application, such as Figure 3 As shown, the data backup system includes:

[0093] The flight service platform 301 is used to send event notifications to the message platform 302 .

[0094] The message platform 302 is used to determine the event storage queue according to the event identifier and attribute information of the event notification when an event notification is received, and store the event notification in the event storage queue; and when a data backup message associated with the event notification sent by the message generation platform 303 is received, the data backup message is stored in the message storage queue according to the event identifier and attribute information, and the data backup message is sent to the backup platform 304, wherein the message storage queue is associated with the event identifier and attribute information.

[0095] The message generation platform 303 is used to obtain the event notification from the message platform 302 and the event data related to the event notification from the flight business platform 301 when monitoring that the message platform 302 receives the event notification, generate a data backup message according to the event notification and the event data, and send the data backup message to the message platform 302.

[0096] The backup platform 304 is used to store the data backup message according to the event identifier and attribute information of the data backup message when receiving the data backup message.

[0097] Specifically, when the flight service platform 301 receives a passenger event, it stores the passenger event and generates an event notification. For example, when the flight service platform 301 completes the data modification of the flight, passenger or seat, the corresponding event notification is triggered, wherein the event notification needs to carry necessary information, such as the operation type, object identifier, etc.

[0098] Furthermore, the flight service platform 301 sends the event notification to the message platform 302, and uses the message platform 302 as a message queue middleware to asynchronously send the event notification to the storage queue specified in the message platform 302. By sending messages in sequence, all event notification messages of the same flight on the same date are arranged in order in the same partition. The configuration of the queue of the message platform 302 can ensure the reliability and persistence of event notifications.

[0099] Further, after the message platform 302 stores the event notification in the corresponding storage queue, the message generation platform 303 monitoring the storage queue will monitor the event notification and determine whether to send the data backup message to the backup platform 304 according to the predefined conditions. If the conditions are met, the message generation and sending logic is triggered.

[0100] The following is an explanation of the logical process of data backup operations performed by each unit in this system:

[0101] First, pre-define conditions to filter events (only some events are used as examples here) notifications, as shown in Table 2:

[0102] Table 2

[0103]

[0104] When the message generation platform 303 obtains the event notification, it parses the EVENT TYPE and OP STATUSTYPE in the event notification, compares it with the above-defined condition filtering event, and determines whether it is necessary to generate a data backup message. Table 3 is a comparison table of the judgment results of the event notification according to the above-defined conditions:

[0105] Table 3

[0106]

[0107] Furthermore, when it is determined that a data backup message needs to be generated for the event notification, the message generation platform 303 will query the event data in the database of the flight business platform 301 based on the event attribute information and event identifier in the event notification, and generate a data backup message based on the event notification and event data, and send the data backup message to the message platform 302.

[0108] It should be noted that when generating a message, the corresponding type of synchronous data message can be constructed according to the operation type (new creation, flight modification, passenger modification, seat modification). For example, for a new flight operation, a message containing full data is constructed; for other operations, an incremental message of the corresponding type is constructed. The difference between a full message and an incremental message is that a full message contains all the information about flights, passengers, and seats. Incremental messages only contain partial information and are mainly divided into three types: flight incremental messages, passenger backup messages, and seat backup messages. Flight incremental messages only contain flight information, passenger backup messages only contain information about specified passengers, and seat backup messages only contain seat information.

[0109] Furthermore, after obtaining the data backup message, the message generation platform 303 needs to asynchronously send the constructed data backup message to the message platform 302. The message platform 302 stores the data backup message according to the attribute information and event identifier, ensuring that all data backup messages of the same flight on the same date are arranged in order in the same partition, which helps to maintain the order consistency of events. Ensure that the order in which the message generation platform 303 consumes the event notification is consistent with the order in which the operations are performed on the flight business platform 301, thereby ensuring that the message generation platform 303 generates and sends the data backup message in the order in which the operations are performed by the flight business platform 301, thereby ensuring that the data backup messages received by the backup platform 304 are updated in sequence, avoiding data confusion caused by the message being sent later and placed earlier.

[0110] Through the above steps, it is ensured that the data synchronization process between the flight business platform 301 and the message generation platform 303 is efficient, reliable and scalable. By using the message queue of the message platform 302, the transaction of modifying data on the flight business platform 301 and sending synchronization data messages on the message generation platform 303 can be decoupled, allowing independent expansion or modification of the processing processes of both parties, as long as the same interface constraints are ensured between the platforms; in the case of a sharp increase in access volume, the use of message queues can enable key components to bear sudden access pressures without completely crashing due to sudden overload requests. This process architecture is designed to reduce coupling between systems while ensuring the orderliness and consistency of data, and improving the maintainability and scalability of the overall system.

[0111] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0112] The embodiment of the present application also provides a data backup device. It should be noted that the data backup device of the embodiment of the present application can be used to execute the data backup method provided by the embodiment of the present application. The data backup device provided by the embodiment of the present application is introduced below.

[0113] Figure 4 Schematic diagram of a data backup device provided according to an embodiment of the present application. Figure 4 As shown, the device includes: a first acquiring unit 41, a second acquiring unit 42, a generating unit 43, and a first sending unit 44.

[0114] The first acquisition unit 41 is used to acquire the event notification from the message platform when monitoring that the message platform receives the event notification, wherein the event notification is sent from the flight service platform to the message platform.

[0115] The second acquisition unit 42 is used to acquire event data related to the event notification from the flight service platform.

[0116] The generating unit 43 is used to generate a data backup message according to the event notification and the event data.

[0117] The first sending unit 44 is used to send the data backup message to the message platform, wherein the message platform sends the data backup message to the backup platform.

[0118] The data backup device provided in the embodiment of the present application obtains the event notification from the message platform through the first acquisition unit 41 when monitoring the message platform receiving the event notification, wherein the event notification is sent by the flight service platform to the message platform; the second acquisition unit 42 obtains the event data related to the event notification from the flight service platform; the generation unit 43 generates the data backup message according to the event notification and the event data; the first sending unit 44 sends the data backup message to the message platform, wherein the message platform sends the data backup message to the backup platform. The problem that the data in the flight service platform cannot be obtained when there is an abnormality in the connection between the airport and the flight service platform in the related technology, resulting in abnormal passenger check-in operation, is solved, the event notification sent by the flight service platform is received by the receiving message platform, and the corresponding data is obtained from the flight service platform according to the event notification, and further combined into a message according to the event data and the event notification, and the events stored in the flight service platform are backed up to the local backup platform in the form of a message, and then when the flight service platform cannot be used, the passenger check-in is performed according to the data in the local backup platform, thereby achieving the technical effect of ensuring the normal check-in operation of the passenger.

[0119] Optionally, in the data backup device provided in the embodiment of the present application, before obtaining event data related to the event notification from the flight business platform, the device also includes: a third acquisition unit, used to obtain the event identifier in the event notification, and determine the event type of the event to be backed up indicated by the event notification based on the event identifier; a judgment unit, used to judge whether the event type is a preset event type, wherein the preset event type is used to characterize the object of the event to be backed up; an execution unit, used to execute the operation of obtaining event data related to the event notification from the flight business platform when the event type is the preset event type; and a deletion unit, used to delete the obtained event notification when the event type is not the preset event type.

[0120] Optionally, in the data backup device provided in the embodiment of the present application, the second acquisition unit 42 includes: a first acquisition module, used to acquire event attribute information carried in the event notification, wherein the event attribute information is used to determine the event to be backed up indicated by the event notification; a sending module, used to send the event attribute information to the flight business platform, and receive the event data of the event notification sent by the flight business platform.

[0121] Optionally, in the data backup device provided in the embodiment of the present application, the generation unit 43 includes: a second acquisition module, used to obtain the event identifier carried in the event notification, and obtain attribute information of the event to be backed up indicated by the event notification from the event notification, wherein the attribute information includes at least one of the following: time information, airport name, flight number; a combination module, used to combine the event identifier, attribute information and event data to obtain a data backup message.

[0122] Optionally, in the data backup device provided in the embodiment of the present application, after sending the data backup message to the message platform, the device also includes: a second receiving unit, used to receive the message sending result sent by the message platform; a second sending unit, used to store the event notification and the message sending result in a message sending record table in association with each other; and a third sending unit, used to send the message sending record table to the message platform upon receiving a record table query request sent by the message platform.

[0123] Figure 5 Schematic diagram of another data backup device provided according to an embodiment of the present application. Figure 5 As shown, the device includes: a first receiving unit 51, a determining unit 52, and a storage unit 53.

[0124] The first receiving unit 51 is used to receive the event notification sent by the flight service platform, and obtain the event identifier and attribute information in the event notification.

[0125] The determining unit 52 is used to determine an event storage queue for storing event notifications according to the event identifier and attribute information, and store the event notifications in the event storage queue, wherein the event storage queue is monitored by the message generation platform.

[0126] The storage unit 53 is used to store the data backup message in a message storage queue according to the event identifier and attribute information when receiving a data backup message associated with an event notification sent by a message generation platform, and send the data backup message to the backup platform, wherein the message storage queue is associated with the event identifier and attribute information.

[0127] The data backup device provided in the embodiment of the present application receives the event notification sent by the flight business platform through the first receiving unit 51, and obtains the event identifier and attribute information in the event notification; the determination unit 52 determines the event storage queue for storing the event notification according to the event identifier and attribute information, and stores the event notification in the event storage queue, wherein the event storage queue is monitored by the message generation platform; the storage unit 53, when receiving the data backup message associated with the event notification sent by the message generation platform, stores the data backup message in the message storage queue according to the event identifier and attribute information, and sends the data backup message to the backup platform, wherein the message storage queue is associated with the event identifier and attribute information. The invention solves the problem in the related technology that when there is an abnormality in the connection between the airport and the flight business platform, the data in the flight business platform cannot be obtained, resulting in abnormal passenger check-in operations. The event notification sent by the flight business platform is received by the message receiving platform, and the corresponding data is obtained from the flight business platform according to the event notification. The event data and the event notification are further combined into a message, and the events stored in the flight business platform are backed up to the local backup platform in the form of a message. Then, when the flight business platform cannot be used, passenger check-in is performed according to the data in the local backup platform, thereby achieving the technical effect of ensuring normal passenger check-in operations.

[0128] Optionally, in the data backup device provided in the embodiment of the present application, the device also includes: a comparison module, which is used to compare the event notification recorded in the message sending record table with the event notification stored in the event storage queue when a message sending record table sent by the message generation platform is received, to obtain a comparison result, wherein the message sending record table stores the event notifications corresponding to each message sent by the message generation platform and the message sending result; a first determination module, which is used to determine that the message generation platform is running normally when the comparison result indicates that the event notification recorded in the message sending record table is consistent with the event notification stored in the event storage queue; a second determination module, which is used to determine that there is an abnormality in the operation of the message generation platform when the comparison result indicates that the event notification recorded in the message sending record table is inconsistent with the event notification stored in the event storage queue, and generate a prompt message, wherein the prompt message is used to indicate that there is an abnormality in the operation of the message generation platform.

[0129] The above-mentioned data backup device includes a processor and a memory. The above-mentioned first acquisition unit 41, second acquisition unit 42, generation unit 43, first sending unit 44, first receiving unit 51, determination unit 52, storage unit 53, etc. are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.

[0130] The processor includes a kernel, which retrieves the corresponding program unit from the memory. One or more kernels can be set, and the kernel parameters are adjusted to solve the problem in the related technology that when there is an abnormality in the connection between the airport and the flight business platform, the data in the flight business platform cannot be obtained, resulting in abnormal passenger check-in operations.

[0131] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0132] An embodiment of the present invention provides a computer-readable storage medium on which a program is stored. When the program is executed by a processor, the data backup method is implemented.

[0133] An embodiment of the present invention provides a processor, which is used to run a program, wherein the data backup method is executed when the program is running.

[0134] Figure 6 is a schematic diagram of an electronic device provided according to an embodiment of the present application, such as Figure 6As shown, an embodiment of the present invention provides an electronic device, the electronic device 60 includes a processor, a memory, and a program stored in the memory and executable on the processor, and the processor implements the steps of the above data backup method when executing the program. The device in this article can be a server, a PC, a PAD, a mobile phone, etc.

[0135] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program that initializes the steps of the above-mentioned data backup method.

[0136] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0137] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0138] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0139] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0140] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0141] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0142] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0143] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0144] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A data backup method, characterized in that: include: In the case of monitoring that the message platform receives an event notification, obtaining the event notification from the message platform, wherein the event notification is sent to the message platform by the flight service platform, and the event notification includes event attribute information but does not include specific event data; In the case where the event type of the event notification is a preset event type, event data related to the event notification is obtained from the flight service platform, wherein after receiving the event notification, the event data is stored in order according to the generation time of each event notification, and in the case where the event type is a new event, all event data under the event are obtained, and in the case where the event type is an incremental event, only newly added or modified related event data are obtained, and the preset event type is used to characterize the object to be backed up for event processing; Generate a data backup message according to the event notification and the event data; The data backup message is sent to the message platform, wherein the message platform sends the data backup message to the backup platform.

2. The method according to claim 1, characterized in that Before acquiring event data related to the event notification from the flight service platform, the method further includes: Obtaining an event identifier in the event notification, and determining an event type of the event to be backed up indicated by the event notification according to the event identifier; Determining whether the event type is a preset event type, wherein the preset event type is used to characterize the object of the event to be backed up; In the case where the event type is the preset event type, performing the operation of acquiring event data related to the event notification from the flight service platform; When the event type is not the preset event type, the acquired event notification is deleted.

3. The method according to claim 1, characterized in that Acquiring event data related to the event notification from the flight service platform includes: Acquire event attribute information carried in the event notification, wherein the event attribute information is used to determine the event to be backed up indicated by the event notification; The event attribute information is sent to the flight service platform, and the event data of the event notification sent by the flight service platform is received.

4. The method according to claim 1, characterized in that: Generating a data backup message according to the event notification and the event data includes: Acquire the event identifier carried in the event notification, and acquire attribute information of the event to be backed up indicated by the event notification from the event notification, wherein the attribute information includes at least one of the following: time information, airport name, and flight number; The event identifier, the attribute information and the event data are combined to obtain the data backup message.

5. The method according to claim 1, characterized in that After sending the data backup message to the message platform, the method further includes: Receiving the message sending result sent by the message platform; The event notification and the message sending result are associated and stored in a message sending record table; When receiving the record table query request sent by the message platform, the message sending record table is sent to the message platform.

6. A data backup method, characterized in that: include: Receive an event notification sent by the flight service platform, and obtain the event identifier and attribute information in the event notification, wherein the event notification includes event attribute information but does not include specific event data; In the case where the event type of the event notification is a preset event type, an event storage queue for storing the event notification is determined according to the event identifier and the attribute information, and the event notification is stored in the event storage queue, wherein the event storage queue is monitored by the message generation platform, wherein after receiving the event notification, each event notification is stored in order according to the generation time, and, in the case where the event type is a newly added event, all event data under the event are obtained, and in the case where the event type is an incremental event, only newly added or modified related event data are obtained, and the preset event type is used to characterize the object to be backed up for event processing; When a data backup message associated with the event notification is received from the message generation platform, the data backup message is stored in a message storage queue according to the event identifier and the attribute information, and the data backup message is sent to a backup platform, wherein the message storage queue is associated with the event identifier and the attribute information.

7. The method according to claim 6, characterized in that The method further comprises: When receiving the message sending record table sent by the message generation platform, compare the event notification recorded in the message sending record table with the event notification stored in the event storage queue to obtain a comparison result, wherein the message sending record table stores the event notification corresponding to each message sent by the message generation platform and the message sending result; When the comparison result indicates that the event notification recorded in the message sending record table is consistent with the event notification stored in the event storage queue, determining that the message generation platform operates normally; When the comparison result indicates that the event notification recorded in the message sending record table is inconsistent with the event notification stored in the event storage queue, it is determined that there is an abnormality in the operation of the message generation platform, and a prompt information is generated, wherein the prompt information is used to indicate that there is an abnormality in the operation of the message generation platform.

8. A data backup system, characterized in that: include: The flight business platform is used to send event notifications to the messaging platform; The message platform is used to determine an event storage queue according to the event identifier and attribute information of the event notification when receiving the event notification, and store the event notification in the event storage queue, and when receiving a data backup message associated with the event notification sent by a message generation platform, store the data backup message in the message storage queue according to the event identifier and the attribute information, and send the data backup message to a backup platform, wherein the message storage queue is associated with the event identifier and the attribute information, and the event notification contains event attribute information but does not contain specific event data; The message generation platform is used to obtain the event notification from the message platform when monitoring that the message platform receives the event notification, and when the event type of the event notification is a preset event type, obtain the event data related to the event notification from the flight service platform, generate a data backup message according to the event notification and the event data, and send the data backup message to the message platform, wherein after receiving the event notification, the event notifications are stored in order according to the generation time of each event notification, and when the event type is a new event, all event data under the event are obtained, and when the event type is an incremental event, only the newly added or modified related event data are obtained, and the preset event type is used to characterize the object of the event to be backed up; The backup platform is used to store the data backup message according to the event identifier and the attribute information of the data backup message when the data backup message is received.

9. A data backup device, characterized in that: include: A first acquisition unit is configured to acquire the event notification from the message platform when monitoring that the message platform receives the event notification, wherein the event notification is sent to the message platform by the flight service platform, and the event notification includes event attribute information but does not include specific event data; a second acquisition unit, configured to acquire event data related to the event notification from the flight service platform when the event type of the event notification is a preset event type, wherein after receiving the event notification, the event data are sequentially stored according to the generation time of each event notification, and when the event type is a newly added event, all event data under the event are acquired, and when the event type is an incremental event, only newly added or modified related event data are acquired, and the preset event type is used to characterize the object to be backed up for event processing; A generating unit, configured to generate a data backup message according to the event notification and the event data; The first sending unit is used to send the data backup message to the message platform, wherein the message platform sends the data backup message to the backup platform.

10. A data backup device, characterized in that: include: A first receiving unit is used to receive an event notification sent by the flight service platform, and obtain an event identifier and attribute information in the event notification, wherein the event notification includes event attribute information but does not include specific event data; a determination unit, configured to determine, when the event type of the event notification is a preset event type, an event storage queue for storing the event notification according to the event identifier and the attribute information, and store the event notification in the event storage queue, wherein the event storage queue is monitored by a message generation platform, wherein after receiving the event notification, each event notification is stored in order according to the generation time, and, when the event type is a newly added event, all event data under the event are obtained, and when the event type is an incremental event, only newly added or modified related event data are obtained, and the preset event type is used to characterize the object to be backed up for event processing; A storage unit is used to store the data backup message in a message storage queue according to the event identifier and the attribute information when receiving the data backup message associated with the event notification sent by the message generation platform, and send the data backup message to the backup platform, wherein the message storage queue is associated with the event identifier and the attribute information.

Citation Information

Patent Citations

  • Data circulation method and device

    CN110874379A