Data diversion method and device
By using dynamic shunt rule tables in the flight data processing system, flight information is divided into target or historical data processing systems, the business interruption problem when switching data processing systems is solved, and the stability and real-time nature of data processing are achieved.
Patent Information
- Application Number
- CN202411879689.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-19
- Publication Date
- 2025-05-02
- Estimated Expiration
- 2044-12-19
AI Technical Summary
The problem of service interruption caused by switching data processing systems in the prior art has not been effectively solved.
By receiving flight initialization messages, extracting the pending flight information, and dividing it into the target data processing system or historical data processing system for processing according to the dynamic diversion rule table, the gradual switching of the data processing system is realized.
It avoids business interruptions caused by switching systems, and realizes smooth diversion of flight information to different data processing systems, ensuring the stability and real-timeness of data processing.
Smart Images

Figure CN119324893B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of civil aviation message processing, and more specifically, to a data diversion method and device. Background Art
[0002] With the development of civil aviation business, civil aviation information technology is also constantly improving and upgrading. Information systems play a supporting and guaranteeing role in improving the efficiency and quality of civil aviation business. Among various business systems in the civil aviation field, the departure system is one of the most core information systems. Airlines need to rely on the departure system to complete business operations such as check-in, boarding, baggage handling, and security checks in the passenger travel process.
[0003] Among the related technologies, most airports mainly use DCS (Distributed Control System Host Standby System), and the users of the system are mainly airports and airlines. Airlines have independently developed an open departure system, which will gradually replace DCS. The open departure system is an integrated system composed of multiple subsystems and centered on transactions. It has the characteristics of high complexity, wide range of data connections, high business relevance, and high requirements for real-time data interaction and system stability. However, the transfer and switching of the departure system may cause interruptions in business use and delays in data processing, thus affecting user use and experience.
[0004] Currently, no effective solution has been proposed to solve the problem of business interruption caused by switching data processing systems to process flight data in related technologies. Summary of the invention
[0005] The main purpose of the present application is to provide a data diversion method and device to solve the problem of business interruption caused by switching data processing systems to process flight data in the related art.
[0006] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a data diversion method is provided. The method comprises: receiving a flight initialization message, extracting flight information to be processed from the flight initialization message, and when the flight information to be processed matches the dynamic diversion rule table, dividing the flight information to be processed into a target data processing system for processing, wherein the dynamic diversion rule table contains multiple dynamic diversion rules, and each dynamic diversion rule is used to determine whether the flight information is divided into the target data processing system for processing; when the flight information to be processed does not match the dynamic diversion rule table, dividing the flight information to be processed into a historical data processing system for processing.
[0007] Optionally, before receiving the flight initialization message, the method also includes: receiving a flight plan message, extracting multiple flight information from the flight plan message, and determining whether each flight information matches a preset static diversion rule table, wherein the static diversion rule table contains multiple static diversion rules, and each static diversion rule indicates that at least one flight information needs to be divided into a target data processing system for processing; when the flight information does not match the static diversion rule table, the flight information is divided into a historical data processing system for processing; when the flight information matches the static diversion rule table, the flight information is determined as target flight information, dynamic diversion rules are generated based on the target flight information, and the dynamic diversion rules are added to the dynamic diversion rule table.
[0008] Optionally, before determining whether each piece of flight information matches a preset static diversion rule table, the method further includes: for each piece of flight information extracted from the flight plan message, determining whether the flight information matches the dynamic diversion rule table; if the flight information does not match the dynamic diversion rule table, executing the step of determining whether each piece of flight information matches the preset static diversion rule table; if the flight information matches the dynamic diversion rule table, determining whether the flight information is initialized, wherein initialization is a data processing system to which the flight information has been determined to be divided, and the divided data processing system is a target data processing system or a historical data processing system; if the flight information has been initialized, skipping the flight information, and executing the step of determining whether the next piece of flight information matches the dynamic diversion rule table; if the flight information has not been initialized, updating the dynamic diversion rule corresponding to the flight information in the dynamic diversion rule table.
[0009] Optionally, the method further includes: receiving an update rule message, parsing the update rule message, and determining whether an abnormality occurs in the parsing process of the update rule message; in the case of an abnormality in the parsing process, issuing a first prompt message, and in the case of no abnormality in the parsing process, verifying the update rule message, and in the case of a verification result indicating that an illegal field exists in the update rule message, issuing a first prompt message, wherein the first prompt message is used to prompt that the rule update fails; in the case of a verification result indicating that the verification passes, extracting a target diversion rule in the update rule message, and determining whether the target diversion rule conflicts with other rules in the diversion rule table, wherein the diversion rule table It is a static diversion rule table or a dynamic diversion rule table, and other rules are the rules in the diversion rule table except the diversion rules corresponding to the flight information; when there is a conflict between the target diversion rule and other rules, a first prompt message is issued, and when there is no conflict between the target diversion rule and other rules, the diversion rule corresponding to the flight information in the diversion rule table is updated to the target diversion rule, and it is determined whether there is an abnormality in the updating process of the diversion rule; when there is an abnormality in the updating process of the diversion rule, a first prompt message is issued, and when there is no abnormality in the updating process of the diversion rule, a second prompt message is issued, wherein the second prompt message is used to prompt that the rule update is successful.
[0010] Optionally, the method further includes: receiving a rule generation message, parsing the rule generation message, and determining whether an abnormality occurs in the parsing process of the rule generation message; in the case of an abnormality in the parsing process, issuing a third prompt message; in the case of no abnormality in the parsing process, verifying the rule generation message, and in the case of the verification result indicating that an illegal field exists in the rule generation message, issuing a third prompt message, wherein the third prompt message is used to prompt that the rule addition fails; in the case of the verification result indicating that the verification passes, extracting a target diversion rule in the rule generation message, and determining whether the target diversion rule conflicts with other rules in the diversion rule table, wherein the other rules are rules in the diversion rule table other than the diversion rules corresponding to the flight information; in the case of a conflict between the target diversion rule and other rules, issuing a third prompt message, in the case of no conflict between the target diversion rule and other rules, inserting the target diversion rule into the diversion rule table, and determining whether an abnormality occurs in the insertion process of the target diversion rule; in the case of an abnormality in the insertion process of the target diversion rule, issuing a third prompt message, and in the case of no abnormality in the insertion process of the target diversion rule, issuing a fourth prompt message, wherein the fourth prompt message is used to prompt that the rule addition is successful.
[0011] Optionally, after receiving a flight initialization message and extracting the flight information to be processed from the flight initialization message, the method further includes: determining whether the flight information to be processed matches the dynamic diversion rule table; if the flight information to be processed does not match the dynamic diversion rule table, skipping the flight initialization message and executing the step of dividing the flight information to be processed into a historical data processing system for processing; if the flight information to be processed matches the dynamic diversion rule table, determining whether the flight information to be processed is initialized, and if the flight information to be processed has been initialized, skipping the flight initialization message; if the flight information to be processed is not initialized, determining whether the data processing system for the flight information to be processed divided in the flight initialization message is a target data processing system; if the data processing system for the flight information to be processed divided in the flight initialization message is the target data processing system, executing the step of dividing the flight information to be processed into the target data processing system for processing; if the data processing system for the flight information to be processed divided in the flight initialization message is not the target data processing system, executing the step of dividing the flight information to be processed into the historical data processing system for processing.
[0012] Optionally, the method also includes: receiving a flight initialization deletion message, extracting the flight information to be deleted from the flight initialization information to be deleted, and judging whether the flight information to be deleted matches the dynamic diversion rule table; if the flight information to be deleted does not match the dynamic diversion rule table, skipping the flight initialization deletion message, and if the flight information to be deleted matches the dynamic diversion rule table, judging whether the flight information to be deleted has been initialized; if the flight information to be deleted is not initialized, skipping the flight initialization deletion message, and if the flight information to be deleted has been initialized, judging whether the flight information to be deleted matches the static diversion rule table; if the flight information to be deleted does not match the static diversion rule table, deleting the dynamic diversion rule corresponding to the flight information to be deleted in the dynamic diversion rule table, and if the flight information to be deleted matches the static diversion rule table, updating the dynamic diversion rule corresponding to the flight information to be deleted in the dynamic diversion rule table.
[0013] Optionally, deleting the dynamic diversion rule corresponding to the flight information to be deleted in the dynamic diversion rule table includes: parsing the rule deletion message, and determining whether there is an abnormality in the parsing process of the rule deletion message; if there is an abnormality in the parsing process, issuing a fifth prompt message, and if there is no abnormality in the parsing process, verifying the rule deletion message, and if the verification result indicates that there are illegal fields in the rule deletion message, issuing a fifth prompt message, wherein the fifth prompt message is used to prompt that the rule deletion has failed; if the verification result indicates that the verification has passed, determining the dynamic diversion rule to be deleted from the dynamic diversion rule table based on the primary key of the rule deletion message, deleting the dynamic diversion rule from the dynamic diversion rule table, and determining whether there is an abnormality in the deletion process of the dynamic diversion rule; if there is an abnormality in the deletion process of the dynamic diversion rule, issuing a fifth prompt message, and if there is no abnormality in the deletion process of the dynamic diversion rule, issuing a sixth prompt message, wherein the sixth prompt message is used to prompt that the rule has been successfully deleted.
[0014] Optionally, the method also includes: receiving a query rule message, parsing the query rule message, and determining whether an abnormality occurs in the parsing process of the query rule message; in the case of an abnormality in the parsing process, issuing a seventh prompt message, and in the case of no abnormality in the parsing process, verifying the query rule message, and in the case that the verification result indicates that there are illegal fields in the query rule message, issuing a seventh prompt message, wherein the seventh prompt message is used to prompt that the rule query fails; in the case that the verification result indicates that the verification is passed, querying the target diversion rule from the dynamic diversion rule table and the static diversion rule table based on the flight information of the query rule message, and determining whether an abnormality occurs in the query process of the target diversion rule; in the case of an abnormality in the query process of the target diversion rule, issuing the seventh prompt message, and in the case of no abnormality in the query process of the target diversion rule, issuing the target diversion rule.
[0015] Optionally, the method also includes: receiving a dynamic rule modification instruction, determining the rule to be modified and the modification cycle from the dynamic rule modification instruction; updating the first identifier of the rule to be modified in the dynamic diversion rule table to a second identifier within the modification cycle, wherein the first identifier is used to indicate that the rule to be modified is valid, and the second identifier is used to indicate that the rule to be modified is invalid; within the modification cycle, classifying the flight information to be processed that matches the rule to be modified to the historical data processing system for processing; after the modification cycle, updating the second identifier of the rule to be modified to the first identifier.
[0016] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a data diversion device is provided. The device includes: a receiving unit, which is used to receive a flight initialization message, extract the flight information to be processed from the flight initialization message, and divide the flight information to be processed into a target data processing system for processing when the flight information to be processed matches the dynamic diversion rule table, wherein the dynamic diversion rule table contains multiple dynamic diversion rules, and each dynamic diversion rule is used to determine whether the flight information is divided into the target data processing system for processing; a first dividing unit, which is used to divide the flight information to be processed into a historical data processing system for processing when the flight information to be processed does not match the dynamic diversion rule table.
[0017] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps of the data diversion method described in each embodiment of the present application are implemented.
[0018] Through the present application, the following steps are adopted: receiving a flight initialization message, extracting the flight information to be processed from the flight initialization message, and when the flight information to be processed matches the dynamic diversion rule table, dividing the flight information to be processed to the target data processing system for processing, the dynamic diversion rule table contains multiple dynamic diversion rules, each dynamic diversion rule is used to determine whether the flight information is divided to the target data processing system for processing; when the flight information to be processed does not match the dynamic diversion rule table, the flight information to be processed is divided to the historical data processing system for processing, which solves the problem of business interruption caused by switching the data processing system to process flight data in the related technology. By setting the dynamic diversion rule table, the matching flight information is divided to the target data processing system for processing based on the dynamic diversion rule, and the unmatched flight information is divided to the historical data processing system for processing, which realizes the gradual switching of the data processing system, thereby achieving the effect of diverting the flight information to different data processing systems for processing, avoiding the business interruption caused by switching the system. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] 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:
[0020] Figure 1 is a flow chart of a data diversion method provided according to an embodiment of the present application;
[0021] Figure 2 It is a schematic diagram of a flight plan message receiving process provided according to an embodiment of the present application;
[0022] Figure 3 is a schematic diagram of a rule update process provided according to an embodiment of the present application;
[0023] Figure 4 is a schematic diagram of a rule adding process provided according to an embodiment of the present application;
[0024] Figure 5 It is a schematic diagram of a flight initialization message receiving process provided according to an embodiment of the present application;
[0025] Figure 6 It is a schematic diagram of a flight initialization deletion message receiving process provided according to an embodiment of the present application;
[0026] Figure 7 is a schematic diagram of a rule deletion process provided according to an embodiment of the present application;
[0027] Figure 8 is a schematic diagram of a rule query process provided according to an embodiment of the present application;
[0028] Fig. 9 is a schematic diagram of a data distribution system provided according to an embodiment of the present application;
[0029] Fig.10 is a schematic diagram of an optional data offloading method provided according to an embodiment of the present application;
[0030] Fig.11 is a schematic diagram of a data splitting device provided according to an embodiment of the present application;
[0031] Fig.12 is a schematic diagram of an electronic device provided according to an embodiment of the present application. DETAILED DESCRIPTION
[0032] 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.
[0033] 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.
[0034] 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.
[0035] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.
[0036] It should be noted that the information collected is 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 comply with the relevant laws, regulations and standards of the relevant regions, take necessary confidentiality measures, do not violate public order and good customs, and provide corresponding operation entrances for users to choose to authorize or refuse.
[0037] The present invention is described below in conjunction with preferred implementation steps. Figure 1 is a flow chart of a data splitting method provided according to an embodiment of the present application, such as Figure 1 As shown, the method comprises the following steps:
[0038] Step S101, receiving a flight initialization message, extracting flight information to be processed from the flight initialization message, and when the flight information to be processed matches the dynamic diversion rule table, dividing the flight information to be processed into a target data processing system for processing, wherein the dynamic diversion rule table contains multiple dynamic diversion rules, and each dynamic diversion rule is used to determine whether the flight information is divided into a target data processing system for processing.
[0039] Specifically, the flight initialization message may be a message for updating the processing status of flight information, wherein the flight information to be processed has been initialized, indicating that the flight information to be processed has been diverted and processed, indicating that the flight information to be processed has been divided into a target data processing system or a historical data processing system, the target data processing system may be an open departure system independently developed by the civil aviation, and the historical data processing system may be a DCS system. The flight information to be processed may include flight number and flight date information, etc. The dynamic diversion rule table may be a diversion rule table for real-time processing of flight information, that is, a diversion rule table for instantly judging whether the flight information needs to be diverted to the target data processing system according to the dynamic real-time changes of the flight information.
[0040] The dynamic diversion rule is the basis for determining whether to divert data (i.e., flight information to be processed) to the target data processing system or the historical data processing system. When the flight initialization message is received, the flight information to be processed indicated by the flight initialization message needs to be initialized. After extracting the flight information to be processed from the flight initialization message, the flight information to be processed is first matched with the dynamic diversion rule table. If the flight information to be processed matches the dynamic diversion rule table, it means that the flight information to be processed needs to be diverted to the target data processing system for processing. For example, the flight number, flight date, terminal, and terminal date information in the flight information to be processed are matched with the existing data in the dynamic diversion rule. If there is a matching dynamic diversion rule, the data is diverted to the target data processing system. If there is no matching rule, the data is diverted to the historical data processing system.
[0041] Among them, the dynamic diversion rules can be set according to the field content and format of Table 1. Table 1 shows the field content and format of the dynamic diversion rules.
[0042] Table 1
[0043]
[0044] For example, Table 2 is a dynamic diversion rule table.
[0045] Table 2
[0046]
[0047] Dynamic diversion rules can be diverted according to flight day information. If the flight day information in the flight information to be processed is: CA1234, and the flight date is 2023-11-11, it is matched with the data in the dynamic diversion rule table. The matching result indicates that the flight information to be processed can be successfully matched with dynamic diversion rule 1, and it is determined that the flight information to be processed will be diverted to the target data processing system. If the flight information to be processed is: CA5678, and the flight date is 2023-11-11, it is matched with the data in the dynamic diversion rule table. The matching result indicates that no matching data is found, and it is determined that the flight information to be processed will be diverted to the historical data processing system.
[0048] Dynamic diversion rules can also be diverted according to flight station information. If the flight station information in the pending flight information is: CA1234, flight date 2023-11-11, terminal PEK, terminal date 2023-11-11, then it is matched with the data in the dynamic diversion rule table, and the matching result indicates that the pending flight information can be successfully matched with dynamic diversion rule 2, and it is determined that the pending flight information will be diverted to the target data processing system. If the flight station information in the pending flight information is: CA5678, flight date 2023-11-11, terminal SHA, terminal date 2023-11-11, then it is matched with the data in the dynamic diversion rule table, and the matching result indicates that no matching data is found, and it is determined that the pending flight information will be diverted to the historical data processing system.
[0049] Step S102: When the flight information to be processed does not match the dynamic diversion rule table, the flight information to be processed is divided into a historical data processing system for processing.
[0050] Specifically, if the flight information to be processed does not match the dynamic diversion rule table, it means that the flight information to be processed does not need to be diverted to the target data processing system for processing, and can be directly divided into the historical data processing system for processing, which will not affect the operation of aviation business.
[0051] It should be noted that, because the number of real-time data requests from the departure system is huge, the data diversion method of this embodiment uses the calculation results in advance, and directly uses the results for diversion when in use, rather than performing real-time calculations for each request, which reduces the amount of calculations in the data diversion system and ensures the real-time nature of data processing. The data diversion processing is all completed automatically by the background, and the front-end requests are processed in real time and automatically diverted to the corresponding data processing system, ensuring real-time response to the requests, transparency to the front-end users, and ensuring the stability of the data processing system during the switching and transfer process.
[0052] The data diversion method provided in the embodiment of the present application receives a flight initialization message, extracts the flight information to be processed from the flight initialization message, and divides the flight information to be processed into a target data processing system for processing when the flight information to be processed matches a dynamic diversion rule table, wherein the dynamic diversion rule table contains a plurality of dynamic diversion rules, each of which is used to determine whether the flight information is divided into a target data processing system for processing; when the flight information to be processed does not match the dynamic diversion rule table, the flight information to be processed is divided into a historical data processing system for processing, thereby solving the problem of business interruption caused by switching the data processing system to process flight data in the related art. By setting a dynamic diversion rule table, matching flight information is divided into a target data processing system for processing based on the dynamic diversion rule, and unmatched flight information is divided into a historical data processing system for processing, thereby realizing the step-by-step switching of the data processing system, thereby achieving the effect of diverting flight information to different data processing systems for processing, thereby avoiding the business interruption caused by switching systems.
[0053] The flight information that needs to be diverted can be first configured through static diversion rules. Optionally, in the data diversion method provided in an embodiment of the present application, before receiving the flight initialization message, the method also includes: receiving a flight plan message, extracting multiple flight information from the flight plan message, and determining whether each flight information matches a preset static diversion rule table, wherein the static diversion rule table contains multiple static diversion rules, and each static diversion rule indicates that at least one flight information needs to be divided into a target data processing system for processing; when the flight information does not match the static diversion rule table, the flight information is divided into a historical data processing system for processing; when the flight information matches the static diversion rule table, the flight information is determined as target flight information, dynamic diversion rules are generated based on the target flight information, and the dynamic diversion rules are added to the dynamic diversion rule table.
[0054] Specifically, a flight plan message refers to a message containing multiple flight information and used for the same planning of different flight signals. The static diversion rule table can be a rule table set manually for static planning of different types of flight information to determine whether diversion is required. For example, according to expert experience, the data of certain flights is diverted to the target data processing system for processing. After receiving the flight plan message, the flight information of each flight is extracted, and each flight information is first matched with the static diversion rule table. If the flight information matches the static diversion rule table, it means that the flight information is planned to be diverted to the target data processing system for processing. The flight information is determined as the target flight information, and a dynamic diversion rule is generated based on the target flight information and added to the dynamic diversion rule table. If the flight information does not match the static diversion rule table, it is assumed that no diversion is required, and the flight information is directly divided into the historical data processing system for processing.
[0055] In some embodiments, in the absence of a flight plan message, the diversion result data of the test flight can be manually inserted directly into the dynamic diversion rule table, thereby diverting the test flight request data to the target data processing system.
[0056] This embodiment processes flight plan messages, matches flight information according to a preset static diversion rule table, generates dynamic diversion rules for the flight information, and controls the diverted data according to multiple dimensions such as flight dimensions, airline dimensions, and airport dimensions through configuration management of static diversion rules, so that the data processing system has greater flexibility in processing data diversion.
[0057] Among them, the static diversion rules can be set according to the field content and format of Table 3, which shows the field content and format of the static diversion rules.
[0058] Table 3
[0059]
[0060] Static diversion rules can be set according to a flight of an airline. For example, it is planned to divert the data of a flight of a certain airline to the target data processing system. For example, the flight information is: CA1234, the flight segment is PEK-CAN, the flight start date is 2023-01-01, and the flight end date is 2023-12-31. Table 4 shows the diversion rule data of the above example.
[0061] Table 4
[0062]
[0063] In some examples, it is planned to divert all flights of a certain airline to the target data processing system, and the flight information is: all flights of CA with the flight segment of PEK-CAN, the flight start date is 2023-01-01, and the flight end date is 2023-12-31. Table 5 shows the diversion rule data of the above example.
[0064] Table 5
[0065]
[0066] In some examples, it is planned to divert all flights of a certain airline departing from a certain terminal to the target data processing system, and the flight information is: all flights of CA departing from PEK, the flight start date is 2023-01-01, and the flight end date is 2023-12-31. Table 6 shows the diversion rule data of the above example.
[0067] Table 6
[0068]
[0069] In some examples, it is planned to divert all flights of all airlines departing from a certain terminal to the target data processing system, and the flight information is: all flights of all airlines departing from PEK, the flight start date is 2023-01-01, and the flight end date is 2023-12-31. Table 7 shows the diversion rule data of the above example.
[0070] Table 7
[0071]
[0072] After receiving the flight plan message, it is also necessary to first determine whether the flight information in the flight plan message already exists in the dynamic diversion rule table. Optionally, in the data diversion method provided in the embodiment of the present application, before determining whether each flight information matches the preset static diversion rule table, the method also includes: for each flight information extracted from the flight plan message, determining whether the flight information matches the dynamic diversion rule table; if the flight information does not match the dynamic diversion rule table, executing the step of determining whether each flight information matches the preset static diversion rule table; if the flight information matches the dynamic diversion rule table, determining whether the flight information is initialized, wherein initialization is that the flight information has been determined to be divided into a data processing system, and the divided data processing system is a target data processing system or a historical data processing system; if the flight information has been initialized, skip the flight information, and execute the step of determining whether the next flight information matches the dynamic diversion rule table; if the flight information is not initialized, update the dynamic diversion rule corresponding to the flight information in the dynamic diversion rule table.
[0073] Specifically, some flight information in the flight plan message may already exist in the existing dynamic diversion rule table. Therefore, before matching the flight information in the flight plan message with the static diversion rule table, first determine whether the flight information matches the dynamic diversion rule table. If not, it means that the dynamic diversion rule for the flight information has not been generated yet, and continue to execute the steps of matching with the static diversion rule table. If the flight information matches the dynamic diversion rule table, it means that the dynamic diversion rule corresponding to the flight information has been added to the dynamic diversion rule table. At this time, it is necessary to determine whether the data processing system to which the flight information has been divided has been determined. If the data processing system to which the flight information has been divided has been determined, no diversion processing is performed on the flight information. If the data processing system to which the flight information has been divided has not been determined, the latest data processing system for the diversion planned for the flight in the current flight plan message is determined based on the flight information, and the data processing system for the diversion of the flight information in the existing dynamic diversion rule is updated by the latest data processing system of the diversion.
[0074] For example, Figure 2 is a schematic diagram of a flight plan message receiving process provided in an embodiment of the present application, such as Figure 2 As shown, the flight plan message is received, and it is determined whether the flight information is already in the dynamic diversion rule. If yes, it is determined whether the flight is initialized. If yes, it ends; if no, the dynamic diversion rule is updated. If no, it continues to determine whether the flight information matches the static rule. If yes, a dynamic diversion rule is added. If the flight information is not in the dynamic diversion rule, it ends.
[0075] This embodiment avoids repeated generation of dynamic diversion rules for the same flight information, which may cause data conflicts in the dynamic diversion rule table, by matching the dynamic diversion rule table before matching the flight information with the static diversion rule table.
[0076] The rules in the static diversion rule table and the dynamic diversion rule table can be updated at any time. Optionally, in the data diversion method provided in the embodiment of the present application, the method also includes: receiving an update rule message, parsing the update rule message, and determining whether an abnormality occurs in the parsing process of the update rule message; in the case of an abnormality in the parsing process, issuing a first prompt message, and in the case of no abnormality in the parsing process, verifying the update rule message, and in the case where the verification result indicates that there are illegal fields in the update rule message, issuing a first prompt message, wherein the first prompt message is used to prompt that the rule update has failed; in the case where the verification result indicates that the verification has passed, extracting the target diversion rule in the update rule message, and determining whether the target diversion rule is different from the diversion rule. Whether there are conflicts with other rules in the table, wherein the diversion rule table is a static diversion rule table or a dynamic diversion rule table, and other rules are rules in the diversion rule table other than the diversion rules corresponding to the flight information; when there is a conflict between the target diversion rule and other rules, a first prompt message is issued; when there is no conflict between the target diversion rule and other rules, the diversion rule corresponding to the flight information in the diversion rule table is updated to the target diversion rule, and it is determined whether there is an abnormality in the updating process of the diversion rule; when there is an abnormality in the updating process of the diversion rule, a first prompt message is issued; when there is no abnormality in the updating process of the diversion rule, a second prompt message is issued, wherein the second prompt message is used to prompt that the rule update is successful.
[0077] Specifically, the target diversion rule may be a target static diversion rule or a target dynamic diversion rule. The rules in the static diversion rule table and the dynamic diversion rule table may be updated at any time according to expert experience. Figure 3 is a schematic diagram of a rule update process provided according to an embodiment of the present application, such as Figure 3 As shown, a message for updating rules is received. The received message is parsed. If a parsing exception occurs, the first prompt message indicating that the rule update failed is returned. If no exception occurs, the legality of each parameter in the message is checked. If an illegal field occurs, the first prompt message is returned. If no exception occurs, the rule for the message content is compared with other rules in the diversion rule table. There should be no overlap with other rules. If there is, it is considered that the updated rule conflicts with the existing rule, and the first prompt message is returned. If no exception occurs, the target diversion rule is updated to the diversion rule table. If an update exception occurs, the first prompt message is returned. If no exception occurs, the second prompt message indicating that the rule update is successful is returned.
[0078] It should be noted that if the flight plan changes, a new flight plan message will be generated, and the data processing system will continue to process the new flight plan message and update the data of the dynamic diversion rule. For example, the flight plan message: CA1234, flight date 2023-11-11, flight segment PEK-CAN, terminal date 2023-11-11, after successfully matching the static diversion rule, the generated dynamic diversion rule data is shown in Table 8.
[0079] Table 8
[0080]
[0081] If the flight plan changes, the destination station of the flight segment is changed from CAN to HAK. The new flight plan message is: CA1234, flight date 2023-11-11, flight segment PEK-HAK, terminal date 2023-11-11. After successfully matching the static rules, the updated dynamic diversion rule data is shown in Table 9.
[0082] Table 9
[0083]
[0084] This embodiment can control and adjust the diversion rules in real time according to the update of the rules and in accordance with multiple dimensions such as flight dimensions, airline dimensions, and airport dimensions, and has strong flexibility.
[0085] The rules in the static diversion rule table and the dynamic diversion rule table can also be added at any time. Optionally, in the data diversion method provided in the embodiment of the present application, the method also includes: receiving a rule generation message, parsing the rule generation message, and determining whether an abnormality occurs in the parsing process of the rule generation message; in the case of an abnormality in the parsing process, issuing a third prompt message, and in the case of no abnormality in the parsing process, verifying the rule generation message, and in the case where the verification result indicates that there are illegal fields in the rule generation message, issuing a third prompt message, wherein the third prompt message is used to prompt that the rule addition failed; in the case where the verification result indicates that the verification has passed, extracting the target diversion rule in the rule generation message. Then, determine whether there is a conflict between the target diversion rule and other rules in the diversion rule table, wherein other rules are rules in the diversion rule table other than the diversion rules corresponding to the flight information; if there is a conflict between the target diversion rule and other rules, issue a third prompt message; if there is no conflict between the target diversion rule and other rules, insert the target diversion rule into the diversion rule table, and determine whether there is an abnormality in the insertion process of the target diversion rule; if there is an abnormality in the insertion process of the target diversion rule, issue a third prompt message; if there is no abnormality in the insertion process of the target diversion rule, issue a fourth prompt message, wherein the fourth prompt message is used to prompt that the rule has been added successfully.
[0086] Specifically, the target diversion rule may be a target static diversion rule or a target dynamic diversion rule. Diversion rules may be added to the static diversion rule table and the dynamic diversion rule table at any time according to expert experience. Figure 4 is a schematic diagram of a rule adding process provided in an embodiment of the present application, such as Figure 4 As shown, a rule generation message is received. The received message is parsed. If a parsing exception occurs, the third prompt message indicating that the rule addition failed is returned. If no exception occurs, the legality of each parameter in the message is checked. If an illegal field occurs, the third prompt message is returned. If no exception occurs, the newly added target diversion rule in the message content is compared with other rules in the diversion rule table. There should be no overlap with other rules. If there is, it is considered that the inserted target diversion rule conflicts with other rules, and the third prompt message is returned. If no exception occurs, the target diversion rule is inserted into the diversion rule table. If an insertion exception occurs, the third prompt message is returned. If no exception occurs, the fourth prompt message indicating that the rule addition is successful is returned.
[0087] This embodiment receives various flight-related messages and adds diversion rules in real time. The diversion data can be updated in time according to the changes in flights, thereby ensuring the accuracy of the diversion data.
[0088] Optionally, in the data diversion method provided in the embodiment of the present application, after receiving the flight initialization message and extracting the flight information to be processed from the flight initialization message, the method further includes: judging whether the flight information to be processed matches the dynamic diversion rule table; if the flight information to be processed does not match the dynamic diversion rule table, skipping the flight initialization message, and executing the step of dividing the flight information to be processed into a historical data processing system for processing; if the flight information to be processed matches the dynamic diversion rule table, judging whether the flight information to be processed is initialized, and if the flight information to be processed has been initialized, skipping the flight initialization message; if the flight information to be processed is not initialized, judging whether the data processing system for the flight information to be processed divided in the flight initialization message is the target data processing system; if the data processing system for the flight information to be processed divided in the flight initialization message is the target data processing system, executing the step of dividing the flight information to be processed into the target data processing system for processing; if the data processing system for the flight information to be processed divided in the flight initialization message is not the target data processing system, executing the step of dividing the flight information to be processed into the historical data processing system for processing.
[0089] Specifically, after receiving the flight initialization message, it is necessary to initialize the pending flight information indicated by the flight initialization message. The flight initialization message contains the flight number and flight date information. The flight initialization message is sent after the flight plan message. The purpose of processing the flight initialization message is to update the "Is the flight initialized" field content in the dynamic diversion rule, and update N to Y, indicating that the flight has been initialized. If the value of this field is already Y, the received flight initialization message will not be processed. If the value of the "Is the flight initialized" field in the dynamic diversion rule table is modified to "Y", the result data of the dynamic diversion rule table will be locked at this time. Even if a new flight plan message comes in, the dynamic diversion result data will not be updated, and the request data of the upstream system will be fixedly transferred to the required target data processing system.
[0090] For example, Figure 5 is a schematic diagram of a flight initialization message receiving process provided in an embodiment of the present application, such as Figure 5 As shown, the flight initialization message is received. Determine whether the flight information to be processed is already in the dynamic diversion rule. If not, it means that the flight information does not need to be diverted and ends directly; if yes, determine whether the flight information to be processed has been initialized. If yes, it means that the flight information to be processed has been divided into the data processing system, and ends directly without processing the initialization message of the flight information to be processed. If the flight information to be processed has not been initialized, determine whether the flight information to be processed is a flight initialized by DC (Departure Control, open departure system), where DC is also the target data processing system. If yes, prepare flight diversion data, determine that the flight information to be processed has been initialized and valid, and update the initialization status in the dynamic diversion rule corresponding to the flight information to be processed from N to Y; if the flight information to be processed is not a flight initialized by DC, prepare flight diversion data, determine that the flight information to be processed has been initialized and invalid, and update the initialization status in the dynamic diversion rule corresponding to the flight information to be processed from N to Y.
[0091] This embodiment ensures the accuracy of data diversion through the processing flow of the flight initialization message and avoids the conflict between the flight initialization message and the dynamic diversion rule.
[0092] The initialized flight information can be deleted through a flight initialization deletion message. Optionally, in the data diversion method provided in the embodiment of the present application, the method also includes: receiving a flight initialization deletion message, extracting the flight information to be deleted from the flight initialization deletion message, and judging whether the flight information to be deleted matches the dynamic diversion rule table; if the flight information to be deleted does not match the dynamic diversion rule table, skipping the flight initialization deletion message, and if the flight information to be deleted matches the dynamic diversion rule table, judging whether the flight information to be deleted has been initialized; if the flight information to be deleted is not initialized, skipping the flight initialization deletion message, and if the flight information to be deleted has been initialized, judging whether the flight information to be deleted matches the static diversion rule table; if the flight information to be deleted does not match the static diversion rule table, deleting the dynamic diversion rule corresponding to the flight information to be deleted in the dynamic diversion rule table, and if the flight information to be deleted matches the static diversion rule table, updating the dynamic diversion rule corresponding to the flight information to be deleted in the dynamic diversion rule table.
[0093] Specifically, for initialized flight information, as static diversion rules are updated, it may be necessary to delete the dynamic diversion rules corresponding to the initialized flight information. Therefore, the rules in the dynamic diversion rule table are updated by processing the flight initialization deletion message. The flight information to be deleted contained in the flight initialization deletion message is consistent with the flight initialization message. The purpose of processing the flight initialization deletion message is also to update the "Is the flight initialized" field content in the dynamic diversion rule, and update Y to N, indicating that the flight corresponding to the flight information to be deleted has been deleted and initialized. If the value of this field is already N, the received flight initialization deletion message will not be processed.
[0094] For example, Figure 6 is a schematic diagram of a flight initialization deletion message receiving process provided in an embodiment of the present application, such as Figure 6As shown, the flight initialization deletion message is received. It is determined whether the flight information to be deleted in the flight initialization deletion message is already in the dynamic diversion rule table. If the flight information to be deleted is not in the dynamic diversion rule table, that is, the flight information to be deleted does not match the dynamic diversion rule table, then it means that the flight initialization deletion message does not need to be processed, and the flight initialization deletion message is directly skipped. If the flight information to be deleted is in the dynamic diversion rule table, that is, the flight information to be deleted matches the dynamic diversion rule table, it is necessary to determine whether the flight information to be deleted has been initialized. If the flight information to be deleted is not initialized, then it means that the flight initialization deletion message does not need to be processed, and the flight initialization deletion message is directly skipped. If the flight information to be deleted has been initialized, it is determined whether the flight information to be deleted matches the static diversion rule table. If it does not match, it means that the dynamic diversion rule corresponding to the flight information to be deleted needs to be deleted, and then the process ends. If the flight information to be deleted matches the static diversion rule table, the corresponding dynamic diversion rule is updated according to the new static diversion rule that matches the flight information to be deleted in the static diversion rule table.
[0095] This embodiment timely updates the status of whether a flight is initialized in the dynamic diversion rule table through the processing flow of the flight initialization deletion message, thereby ensuring other subsequent processing flows of the same flight information.
[0096] The dynamic diversion rule can be deleted through a rule deletion message. Optionally, in the data diversion method provided in the embodiment of the present application, deleting the dynamic diversion rule corresponding to the flight information to be deleted in the dynamic diversion rule table includes: parsing the rule deletion message, and judging whether there is an abnormality in the parsing process of the rule deletion message; in the case of an abnormality in the parsing process, issuing a fifth prompt message, and in the case of no abnormality in the parsing process, verifying the rule deletion message, and in the case where the verification result indicates that there are illegal fields in the rule deletion message, issuing a fifth prompt message, wherein the fifth prompt message is used to prompt that the rule deletion fails; in the case where the verification result indicates that the verification is passed, determining the dynamic diversion rule to be deleted from the dynamic diversion rule table based on the primary key of the rule deletion message, and deleting the dynamic diversion rule from the dynamic diversion rule table, and judging whether there is an abnormality in the deletion process of the dynamic diversion rule; in the case of an abnormality in the deletion process of the dynamic diversion rule, issuing a fifth prompt message, and in the case of no abnormality in the deletion process of the dynamic diversion rule, issuing a sixth prompt message, wherein the sixth prompt message is used to prompt that the rule deletion is successful.
[0097] For example, Figure 7 is a schematic diagram of a rule deletion process provided according to an embodiment of the present application, such as Figure 7As shown, a rule deletion message is received. The received message is parsed. If a parsing exception occurs, the fifth prompt message indicating that the rule deletion failed is returned. If no exception occurs, the legality of each parameter in the message is checked. If an illegal field occurs, the fifth prompt message is returned. If no exception occurs, the dynamic diversion rule to be deleted is determined according to the unique primary key in the message, and the rule is deleted from the dynamic diversion rule table. If a deletion exception occurs, the fifth prompt message is returned. If no exception occurs, the sixth prompt message indicating that the rule deletion is successful is returned.
[0098] It should be noted that, in addition to being used to delete dynamic diversion rules, the rule deletion message in this embodiment can also be used to delete static diversion rules in the static diversion rule table based on the same process through the rule deletion message. This embodiment can delete the rules in the static diversion rule table or the dynamic diversion rule table at any time through the rule deletion message, thereby improving the flexibility of diversion rule configuration.
[0099] Static diversion rules or dynamic diversion rules can be viewed at any time through query rule messages. Optionally, in the data diversion method provided in the embodiment of the present application, the method also includes: receiving a query rule message, parsing the query rule message, and determining whether there is an abnormality in the parsing process of the query rule message; in the case of an abnormality in the parsing process, issuing a seventh prompt message; in the case of no abnormality in the parsing process, verifying the query rule message, and in the case where the verification result indicates that there are illegal fields in the query rule message, issuing a seventh prompt message, wherein the seventh prompt message is used to prompt that the rule query fails; in the case where the verification result indicates that the verification is passed, querying the target diversion rule from the dynamic diversion rule table and the static diversion rule table based on the flight information in the query rule message, and determining whether there is an abnormality in the query process of the target diversion rule; in the case of an abnormality in the query process of the target diversion rule, issuing a seventh prompt message; in the case of no abnormality in the query process of the target diversion rule, issuing the target diversion rule.
[0100] For example, Figure 8 is a schematic diagram of a rule query process provided according to an embodiment of the present application, such as Figure 8 As shown, a query rule message is received. The received message is parsed. If a parsing exception occurs, the seventh prompt message indicating that the rule query failed is returned. If no exception occurs, the legality of each parameter in the message is checked. If an illegal field occurs, the seventh prompt message is returned. If no exception occurs, the dynamic diversion rule table and the static diversion rule table are queried according to the message conditions (that is, the flight information of the query rule message). If a query exception occurs, the seventh prompt message is returned. If no exception occurs, the queried target diversion rule list is returned.
[0101] This embodiment queries static diversion rules and dynamic diversion rules at any time through rule query messages, ensures the accuracy of diversion rules, and can handle abnormalities in diversion rules in a timely manner.
[0102] Optionally, in the data diversion method provided in the embodiment of the present application, the method also includes: receiving a dynamic rule modification instruction, determining the rule to be modified and the modification cycle from the dynamic rule modification instruction; updating the first identifier of the rule to be modified in the dynamic diversion rule table to the second identifier within the modification cycle, wherein the first identifier is used to represent that the rule to be modified is valid, and the second identifier is used to represent that the rule to be modified is invalid; within the modification cycle, dividing the flight information to be processed that matches the rule to be modified into the historical data processing system for processing; after the modification cycle, updating the second identifier of the rule to be modified to the first identifier.
[0103] Specifically, if a flight has a temporary failure in the target data processing system, in order to ensure the normal operation of the flight in the upstream system, the upstream data of the flight needs to be temporarily diverted to the historical data processing system. At this time, the value of the "Is the rule valid" field in the dynamic diversion rule table needs to be modified to "N", which is the second mark. At this time, the upstream request data of the flight (that is, the flight information to be processed that matches the rule to be modified) will be diverted to the historical data processing system. Then, after the target data processing system returns to normal, the value of the "Is the rule valid" field in the dynamic diversion rule table is modified to "Y", which is the first mark. At this time, the request data of the upstream system of the flight will be diverted to the target data processing system again. According to the needs of the business scenario, the diversion time of the flight information to be processed to the target data processing system or the historical data processing system can be adjusted according to the setting of the modification cycle.
[0104] It should be noted that the rules to be modified can be controlled by configuring the "Flight Suffix" field in the dynamic diversion rule table to determine only the dynamic diversion rules corresponding to the flights with the target suffix as the rules to be modified. When a temporary problem occurs to all flights of an airline in the target data processing system, in order to ensure that all flights of this airline run normally in the upstream system, it is necessary to temporarily switch all the request data of all flights of this airline (an airline generally has multiple flights) to the historical data processing system at one time, and all dynamic diversion rules with the suffix of this airline can be determined as rules to be modified.
[0105] In this embodiment, by adjusting the first identifier and the second identifier of the dynamic diversion rule, data can be freely controlled to be diverted to different data processing systems at different times.
[0106] According to another embodiment of the present application, a data distribution system is also provided. Fig. 9Schematic diagram of a data distribution system provided according to an embodiment of the present application. Fig. 9 As shown, the system includes: a static diversion rule management component, a dynamic diversion rule management component, and a message processing component.
[0107] Specifically, the static diversion rule management component includes the management of static diversion rules, such as adding rules, deleting rules, modifying rules, and querying rules. Static rules are used to control the granularity of data diversion. Through the configuration of static rules, data diversion can be controlled according to the airport dimension, airline dimension, and flight dimension.
[0108] The dynamic rule management component includes the management of dynamic diversion rules, such as adding rules, deleting rules, modifying rules, and querying rules. Dynamic diversion rules are the basis for judging data diversion, judging whether the request data is diverted to the target data processing system for processing or to the historical data processing system for processing.
[0109] The message processing component includes flight plan message processing, flight initialization message processing, and flight initialization deletion message processing. It is used to receive and process flight plan messages, flight initialization messages, and flight initialization deletion messages, match them with static diversion rules, and generate or update dynamic diversion rules.
[0110] This embodiment completes the change and launch of the data processing system without shutting down the system through cloud deployment of the data diversion system. By configuring the diversion rules, data can be diverted from the historical data processing system to the target data processing system according to the dimensions of airports, airlines, flights, etc., to achieve gradual switching of the data processing system. The diversion results can be updated in real time through advance calculation to ensure real-time data processing. All data diversion processing is completed automatically in the background to achieve transparent and seamless switching of the system.
[0111] According to another embodiment of the present application, an optional data distribution method applied to a data distribution system is also provided. Fig.10 Schematic diagram of an optional data diversion method provided according to an embodiment of the present application. Fig.10 As shown, the method includes: the front end initiates a data processing request to the data diversion system, the data diversion system receives the flight message, matches the flight message with the static diversion rule, and generates a dynamic diversion rule when the match is successful, and the dynamic diversion rule diverts the data in the flight message to DCS or DC.
[0112] This embodiment uses an optional data diversion method to match flight messages with static diversion rules and generate dynamic diversion rules. Based on the dynamic diversion rules, the data in the matched flight messages are divided into DC for processing, and the unmatched data are divided into DCS for processing, thereby realizing the gradual switching of the data processing system, thereby achieving the effect of diverting flight data to different data processing systems for processing, and avoiding business interruptions caused by switching systems.
[0113] 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.
[0114] The embodiment of the present application also provides a data splitting device, and it should be noted that the data splitting device of the embodiment of the present application can be used to execute the data splitting method provided by the embodiment of the present application. The data splitting device provided by the embodiment of the present application is introduced below.
[0115] Fig.11 Schematic diagram of a data splitting device provided according to an embodiment of the present application. Fig.11 As shown, the device comprises:
[0116] The receiving unit 1101 is used to receive a flight initialization message, extract the flight information to be processed from the flight initialization message, and divide the flight information to be processed into a target data processing system for processing when the flight information to be processed matches the dynamic diversion rule table, wherein the dynamic diversion rule table contains multiple dynamic diversion rules, and each dynamic diversion rule is used to determine whether the flight information is divided into a target data processing system for processing;
[0117] The first division unit 1102 is used to divide the flight information to be processed into the historical data processing system for processing when the flight information to be processed does not match the dynamic diversion rule table.
[0118] The data diversion device provided in the embodiment of the present application receives a flight initialization message through a receiving unit 1101, extracts flight information to be processed from the flight initialization message, and divides the flight information to be processed into a target data processing system for processing when the flight information to be processed matches a dynamic diversion rule table, wherein the dynamic diversion rule table contains multiple dynamic diversion rules, and each dynamic diversion rule is used to determine whether the flight information is divided into a target data processing system for processing; the first dividing unit 1102 divides the flight information to be processed into a historical data processing system for processing when the flight information to be processed does not match the dynamic diversion rule table, thereby solving the problem of business interruption caused by switching the data processing system to process flight data in the related art, and by setting a dynamic diversion rule table, the matching flight information is divided into the target data processing system for processing based on the dynamic diversion rule, and the unmatched flight information is divided into the historical data processing system for processing, thereby realizing the gradual switching of the data processing system, thereby achieving the effect of diverting the flight information to different data processing systems for processing, and avoiding the business interruption caused by switching the system.
[0119] Optionally, in the data diversion device provided in the embodiment of the present application, the device also includes: a first extraction unit, used to receive a flight plan message, extract multiple flight information from the flight plan message, and determine whether each flight information matches a preset static diversion rule table, wherein the static diversion rule table contains multiple static diversion rules, and each static diversion rule indicates that at least one flight information needs to be divided into a target data processing system for processing; a second division unit, used to divide the flight information into a historical data processing system for processing when the flight information does not match the static diversion rule table; a first determination unit, used to determine the flight information as target flight information when the flight information matches the static diversion rule table, generate dynamic diversion rules based on the target flight information, and add the dynamic diversion rules to the dynamic diversion rule table.
[0120] Optionally, in the data diversion device provided in the embodiment of the present application, the device also includes: a first judgment unit, used to judge whether the flight information extracted from the flight plan message matches the dynamic diversion rule table; a first execution unit, used to execute the step of judging whether each flight information matches the preset static diversion rule table when the flight information does not match the dynamic diversion rule table; a second judgment unit, used to judge whether the flight information is initialized when the flight information matches the dynamic diversion rule table, wherein the initialization is that the flight information has been determined to be divided into a data processing system, and the divided data processing system is a target data processing system or a historical data processing system; a first skipping unit, used to skip the flight information when the flight information has been initialized, and execute the step of judging whether the next flight information matches the dynamic diversion rule table; an updating unit, used to update the dynamic diversion rule corresponding to the flight information in the dynamic diversion rule table when the flight information is not initialized.
[0121] Optionally, in the data diversion device provided in the embodiment of the present application, the device also includes: a first parsing unit, used to receive an update rule message, parse the update rule message, and determine whether an abnormality occurs in the parsing process of the update rule message; a first prompt unit, used to issue a first prompt message when an abnormality occurs in the parsing process, and to verify the update rule message when no abnormality occurs in the parsing process, and to issue a first prompt message when the verification result indicates that there are illegal fields in the update rule message, wherein the first prompt message is used to prompt that the rule update has failed; a conflict judgment unit, used to extract a target diversion rule in the update rule message when the verification result indicates that the verification has passed, and to determine whether the target diversion rule is consistent with other rules in the diversion rule table. There is a conflict, wherein the diversion rule table is a static diversion rule table or a dynamic diversion rule table, and the other rules are the rules in the diversion rule table except the diversion rules corresponding to the flight information; a second prompt unit is used to issue a first prompt message when there is a conflict between the target diversion rule and other rules, and update the diversion rule corresponding to the flight information in the diversion rule table to the target diversion rule when there is no conflict between the target diversion rule and other rules, and judge whether there is an abnormality in the updating process of the diversion rule; a third prompt unit is used to issue a first prompt message when there is an abnormality in the updating process of the diversion rule, and issue a second prompt message when there is no abnormality in the updating process of the diversion rule, wherein the second prompt message is used to prompt that the rule update is successful.
[0122] Optionally, in the data diversion device provided in the embodiment of the present application, the device also includes: a second parsing unit, which is used to receive a generated rule message, parse the generated rule message, and determine whether an abnormality occurs in the parsing process of the generated rule message; a fourth prompt unit, which is used to issue a third prompt message when an abnormality occurs in the parsing process, and to verify the generated rule message when no abnormality occurs in the parsing process, and to issue a third prompt message when the verification result indicates that there is an illegal field in the generated rule message, wherein the third prompt message is used to prompt that the rule addition fails; a rule extraction unit, which is used to extract the target diversion rule in the generated rule message when the verification result indicates that the verification is passed, and to determine whether the target diversion rule then whether there is a conflict with other rules in the diversion rule table, wherein other rules are the rules in the diversion rule table other than the diversion rules corresponding to the flight information; a fifth prompt unit, used to issue a third prompt message when there is a conflict between the target diversion rule and other rules, and to insert the target diversion rule into the diversion rule table when there is no conflict between the target diversion rule and other rules, and to determine whether there is an abnormality in the insertion process of the target diversion rule; a sixth prompt unit, used to issue a third prompt message when there is an abnormality in the insertion process of the target diversion rule, and to issue a fourth prompt message when there is no abnormality in the insertion process of the target diversion rule, wherein the fourth prompt message is used to prompt that the rule has been added successfully.
[0123] Optionally, in the data diversion device provided in the embodiment of the present application, the device also includes: a third judgment unit, used to judge whether the flight information to be processed matches the dynamic diversion rule table; a second skipping unit, used to skip the flight initialization message when the flight information to be processed does not match the dynamic diversion rule table, and execute the step of dividing the flight information to be processed into the historical data processing system for processing; a fourth judgment unit, used to judge whether the flight information to be processed is initialized when the flight information to be processed matches the dynamic diversion rule table, and skip the flight initialization message when the flight information to be processed has been initialized; a fifth judgment unit, used to judge whether the data processing system divided into the flight information to be processed in the flight initialization message is the target data processing system when the flight information to be processed is not initialized; a second execution unit, used to execute the step of dividing the flight information to be processed into the target data processing system for processing when the data processing system divided into the flight information to be processed in the flight initialization message is the target data processing system; a third execution unit, used to execute the step of dividing the flight information to be processed into the historical data processing system for processing when the data processing system divided into the flight information to be processed in the flight initialization message is not the target data processing system.
[0124] Optionally, in the data diversion device provided in the embodiment of the present application, the device also includes: a second extraction unit, used to receive a flight initialization deletion message, extract the flight information to be deleted from the flight initialization information to be deleted from the flight initialization deletion message, and determine whether the flight information to be deleted matches the dynamic diversion rule table; a third skip unit, used to skip the flight initialization deletion message when the flight information to be deleted does not match the dynamic diversion rule table, and when the flight information to be deleted matches the dynamic diversion rule table, determine whether the flight information to be deleted has been initialized; a fourth skip unit, used to skip the flight initialization deletion message when the flight information to be deleted is not initialized, and when the flight information to be deleted has been initialized, determine whether the flight information to be deleted matches the static diversion rule table; a deletion unit, used to delete the dynamic diversion rule corresponding to the flight information to be deleted in the dynamic diversion rule table when the flight information to be deleted does not match the static diversion rule table, and update the dynamic diversion rule corresponding to the flight information to be deleted in the dynamic diversion rule table when the flight information to be deleted matches the static diversion rule table.
[0125] Optionally, in the data diversion device provided in the embodiment of the present application, the deletion unit includes: a parsing module, which is used to parse the rule deletion message and determine whether there is an abnormality in the parsing process of the rule deletion message; a verification module, which is used to issue a fifth prompt message when an abnormality occurs in the parsing process, and verify the rule deletion message when no abnormality occurs in the parsing process, and issue a fifth prompt message when the verification result indicates that there are illegal fields in the rule deletion message, wherein the fifth prompt message is used to prompt that the rule deletion fails; a deletion module, which is used to determine the dynamic diversion rule to be deleted from the dynamic diversion rule table based on the primary key of the rule deletion message when the verification result indicates that the verification is passed, and delete the dynamic diversion rule from the dynamic diversion rule table to determine whether there is an abnormality in the deletion process of the dynamic diversion rule; a first prompt module, which is used to issue a fifth prompt message when an abnormality occurs in the deletion process of the dynamic diversion rule, and issue a sixth prompt message when no abnormality occurs in the deletion process of the dynamic diversion rule, wherein the sixth prompt message is used to prompt that the rule is successfully deleted.
[0126] Optionally, in the data diversion device provided in the embodiment of the present application, the device also includes: a third parsing unit, used to receive a query rule message, parse the query rule message, and determine whether there is an abnormality in the parsing process of the query rule message; a verification unit, used to issue a seventh prompt message when an abnormality occurs in the parsing process, and verify the query rule message when no abnormality occurs in the parsing process, and issue a seventh prompt message when the verification result indicates that there are illegal fields in the query rule message, wherein the seventh prompt message is used to prompt that the rule query fails; a query unit, used to query the target diversion rule from the dynamic diversion rule table and the static diversion rule table based on the flight information of the query rule message when the verification result indicates that the verification is passed, and determine whether there is an abnormality in the query process of the target diversion rule; an issuing unit, used to issue the seventh prompt message when an abnormality occurs in the query process of the target diversion rule, and issue the target diversion rule when no abnormality occurs in the query process of the target diversion rule.
[0127] Optionally, in the data diversion device provided in the embodiment of the present application, the device also includes: a second determination unit, used to receive a dynamic rule modification instruction, and determine the rule to be modified and the modification period from the dynamic rule modification instruction; a first update unit, used to update the first identifier of the rule to be modified in the dynamic diversion rule table to a second identifier within the modification period, wherein the first identifier is used to indicate that the rule to be modified is valid, and the second identifier is used to indicate that the rule to be modified is invalid; a third division unit, used to divide the flight information to be processed that matches the rule to be modified to the historical data processing system for processing within the modification period; and a second update unit, used to update the second identifier of the rule to be modified to the first identifier after the modification period.
[0128] The data splitting device includes a processor and a memory. The above-mentioned receiving unit 1101 and the first dividing unit 1102 are stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.
[0129] The processor contains a kernel, which calls the corresponding program unit from the memory. One or more kernels can be set, and the flight information can be diverted to different data processing systems for processing by adjusting the kernel parameters, avoiding business interruption caused by switching systems.
[0130] 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.
[0131] 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, a data diversion method is implemented.
[0132] An embodiment of the present invention provides a processor, which is used to run a program, wherein a data diversion method is executed when the program is running.
[0133] Fig.12 is a schematic diagram of an electronic device provided according to an embodiment of the present application. Fig.12 As shown, the electronic device 1201 includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, the following steps are implemented: receiving a flight initialization message, extracting flight information to be processed from the flight initialization message, and when the flight information to be processed matches the dynamic diversion rule table, dividing the flight information to be processed into a target data processing system for processing, wherein the dynamic diversion rule table contains a plurality of dynamic diversion rules, each of which is used to determine whether the flight information is divided into a target data processing system for processing; when the flight information to be processed does not match the dynamic diversion rule table, dividing the flight information to be processed into a historical data processing system for processing. The device in this article may be a server, a PC, a PAD, a mobile phone, etc.
[0134] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program having the following method steps: receiving a flight initialization message, extracting flight information to be processed from the flight initialization message, and when the flight information to be processed matches a dynamic diversion rule table, dividing the flight information to be processed to a target data processing system for processing, wherein the dynamic diversion rule table contains multiple dynamic diversion rules, and each dynamic diversion rule is used to determine whether the flight information is divided to a target data processing system for processing; when the flight information to be processed does not match the dynamic diversion rule table, dividing the flight information to be processed to a historical data processing system for processing.
[0135] 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.
[0136] 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.
[0137] 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.
[0138] 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 A step that specifies a function in one or more boxes.
[0139] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0140] 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.
[0141] 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.
[0142] 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.
[0143] 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 take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the present application may take 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.
[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 diversion method, characterized in that: include: receiving a flight initialization message, extracting to-be-processed flight information from the flight initialization message, and, if the to-be-processed flight information matches a dynamic diversion rule table, dividing the to-be-processed flight information into a target data processing system for processing, wherein the dynamic diversion rule table includes a plurality of dynamic diversion rules, and each dynamic diversion rule is used to determine whether the flight information is divided into a target data processing system for processing; In the case where the flight information to be processed does not match the dynamic diversion rule table, the flight information to be processed is divided into a historical data processing system for processing; Wherein, before receiving the flight initialization message, the method further includes: receiving a flight plan message, extracting multiple flight information from the flight plan message, and determining whether each flight information matches a preset static diversion rule table, wherein the static diversion rule table contains multiple static diversion rules, and each static diversion rule indicates that at least one flight information needs to be divided into a target data processing system for processing; if the flight information does not match the static diversion rule table, the flight information is divided into a historical data processing system for processing; if the flight information matches the static diversion rule table, the flight information is determined as target flight information, a dynamic diversion rule is generated based on the target flight information, and the dynamic diversion rule is added to the dynamic diversion rule table; Before determining whether each piece of flight information matches a preset static diversion rule table, the method further includes: for each piece of flight information extracted from the flight plan message, determining whether the flight information matches the dynamic diversion rule table; when the flight information does not match the dynamic diversion rule table, executing the step of determining whether each piece of flight information matches the preset static diversion rule table; when the flight information matches the dynamic diversion rule table, determining whether the flight information is initialized, wherein the initialization is that the flight information has been determined to be divided into a data processing system, and the divided data processing system is the target data processing system or the historical data processing system; when the flight information has been initialized, skipping the flight information, and executing the step of determining whether the next piece of flight information matches the dynamic diversion rule table; when the flight information is not initialized, updating the dynamic diversion rule corresponding to the flight information in the dynamic diversion rule table.
2. The method according to claim 1, characterized in that The method further comprises: Receiving an update rule message, parsing the update rule message, and determining whether an abnormality occurs during the parsing process of the update rule message; In the case where an abnormality occurs in the parsing process, a first prompt message is issued; in the case where no abnormality occurs in the parsing process, the update rule message is verified, and in the case where the verification result indicates that an illegal field exists in the update rule message, the first prompt message is issued, wherein the first prompt message is used to prompt that the rule update fails; If the verification result indicates that the verification has passed, extract the target diversion rule in the update rule message, and determine whether the target diversion rule conflicts with other rules in the diversion rule table, wherein the diversion rule table is a static diversion rule table or the dynamic diversion rule table, and the other rules are rules in the diversion rule table other than the diversion rule corresponding to the flight information; In the case where the target diversion rule conflicts with the other rules, the first prompt information is issued; in the case where the target diversion rule does not conflict with the other rules, the diversion rule corresponding to the flight information in the diversion rule table is updated to the target diversion rule, and whether an abnormality occurs in the diversion rule update process; When an abnormality occurs in the updating process of the diversion rule, the first prompt information is issued, and when no abnormality occurs in the updating process of the diversion rule, the second prompt information is issued, wherein the second prompt information is used to prompt that the rule update is successful.
3. The method according to claim 1, characterized in that The method further comprises: Receiving a rule generation message, parsing the rule generation message, and determining whether an abnormality occurs during the parsing process of the rule generation message; In the case where an abnormality occurs in the parsing process, a third prompt message is issued; in the case where no abnormality occurs in the parsing process, the rule generation message is verified, and in the case where the verification result indicates that an illegal field exists in the rule generation message, the third prompt message is issued, wherein the third prompt message is used to prompt that the rule addition fails; If the verification result indicates that the verification has passed, extract the target diversion rule in the generated rule message, and determine whether the target diversion rule conflicts with other rules in the diversion rule table, wherein the other rules are rules in the diversion rule table other than the diversion rule corresponding to the flight information; In the case where the target diversion rule conflicts with the other rules, the third prompt information is issued; in the case where the target diversion rule does not conflict with the other rules, the target diversion rule is inserted into the diversion rule table, and it is determined whether an abnormality occurs during the insertion of the target diversion rule; When an abnormality occurs during the insertion of the target diversion rule, the third prompt message is issued, and when no abnormality occurs during the insertion of the target diversion rule, the fourth prompt message is issued, wherein the fourth prompt message is used to prompt that the rule is added successfully.
4. The method according to claim 1, characterized in that: After receiving the flight initialization message and extracting the flight information to be processed from the flight initialization message, the method further includes: Determine whether the flight information to be processed matches the dynamic diversion rule table; In the case where the flight information to be processed does not match the dynamic diversion rule table, skipping the flight initialization message, and executing the step of dividing the flight information to be processed into the historical data processing system for processing; When the flight information to be processed matches the dynamic diversion rule table, determining whether the flight information to be processed is initialized, and when the flight information to be processed is initialized, skipping the flight initialization message; In the case where the flight information to be processed is not initialized, determining whether the data processing system for dividing the flight information to be processed in the flight initialization message is a target data processing system; In a case where the data processing system to which the flight information to be processed is allocated by the flight initialization message is the target data processing system, executing the step of allocating the flight information to be processed to the target data processing system for processing; In a case where the data processing system to which the flight information to be processed is allocated by the flight initialization message is not the target data processing system, a step of allocating the flight information to be processed to the historical data processing system for processing is performed.
5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: receiving a flight initialization deletion message, extracting flight information to be deleted from the flight initialization information to be deleted from the flight initialization deletion message, and determining whether the flight information to be deleted matches the dynamic diversion rule table; If the flight information to be deleted does not match the dynamic diversion rule table, skip the flight initialization deletion message, and if the flight information to be deleted matches the dynamic diversion rule table, determine whether the flight information to be deleted has been initialized; If the flight information to be deleted is not initialized, skip the flight initialization deletion message; if the flight information to be deleted is initialized, determine whether the flight information to be deleted matches the static diversion rule table; When the flight information to be deleted does not match the static diversion rule table, the dynamic diversion rule corresponding to the flight information to be deleted in the dynamic diversion rule table is deleted; when the flight information to be deleted matches the static diversion rule table, the dynamic diversion rule corresponding to the flight information to be deleted in the dynamic diversion rule table is updated.
6. The method according to claim 5, characterized in that Deleting the dynamic diversion rule corresponding to the flight information to be deleted in the dynamic diversion rule table includes: Parsing the rule deletion message, and determining whether an abnormality occurs during the parsing process of the rule deletion message; In the case where an abnormality occurs in the parsing process, a fifth prompt message is issued; in the case where no abnormality occurs in the parsing process, the rule deletion message is verified, and in the case where the verification result indicates that an illegal field exists in the rule deletion message, the fifth prompt message is issued, wherein the fifth prompt message is used to prompt that the rule deletion fails; If the verification result indicates that the verification has passed, determining the dynamic diversion rule to be deleted from the dynamic diversion rule table based on the primary key of the rule deletion message, deleting the dynamic diversion rule from the dynamic diversion rule table, and determining whether an abnormality occurs in the deletion process of the dynamic diversion rule; When an abnormality occurs in the deletion process of the dynamic diversion rule, the fifth prompt message is issued, and when no abnormality occurs in the deletion process of the dynamic diversion rule, the sixth prompt message is issued, wherein the sixth prompt message is used to prompt that the rule is successfully deleted.
7. The method according to claim 1, characterized in that The method further comprises: Receiving a query rule message, parsing the query rule message, and determining whether an abnormality occurs during the parsing process of the query rule message; In the case where an abnormality occurs in the parsing process, seventh prompt information is issued; in the case where no abnormality occurs in the parsing process, the query rule message is verified, and in the case where the verification result indicates that an illegal field exists in the query rule message, the seventh prompt information is issued, wherein the seventh prompt information is used to prompt that the rule query fails; If the verification result indicates that the verification has passed, querying the target diversion rule from the dynamic diversion rule table and the static diversion rule table based on the flight information of the query rule message, and determining whether an abnormality occurs in the query process of the target diversion rule; When an abnormality occurs in the query process of the target diversion rule, the seventh prompt information is issued; when no abnormality occurs in the query process of the target diversion rule, the target diversion rule is issued.
8. The method according to claim 1, characterized in that The method further comprises: receiving a dynamic rule modification instruction, and determining a rule to be modified and a modification period from the dynamic rule modification instruction; updating the first identifier of the rule to be modified in the dynamic diversion rule table to a second identifier within the modification period, wherein the first identifier is used to indicate that the rule to be modified is valid, and the second identifier is used to indicate that the rule to be modified is invalid; During the modification period, the flight information to be processed that matches the rule to be modified is divided into the historical data processing system for processing; After the modification period, the second identifier of the rule to be modified is updated to the first identifier.
9. A data splitting device, characterized in that: include: a receiving unit, configured to receive a flight initialization message, extract flight information to be processed from the flight initialization message, and, if the flight information to be processed matches a dynamic diversion rule table, divide the flight information to be processed into a target data processing system for processing, wherein the dynamic diversion rule table includes a plurality of dynamic diversion rules, and each dynamic diversion rule is used to determine whether the flight information is divided into a target data processing system for processing; A first division unit is used to divide the flight information to be processed into a historical data processing system for processing when the flight information to be processed does not match the dynamic diversion rule table; The device further includes: a first extraction unit, configured to receive a flight plan message, extract multiple flight information from the flight plan message, and determine whether each flight information matches a preset static diversion rule table, wherein the static diversion rule table contains multiple static diversion rules, and each static diversion rule indicates that at least one flight information needs to be divided into a target data processing system for processing; a second division unit, configured to divide the flight information into a historical data processing system for processing when the flight information does not match the static diversion rule table; a first determination unit, configured to determine the flight information as target flight information when the flight information matches the static diversion rule table, generate dynamic diversion rules based on the target flight information, and add the dynamic diversion rules to the dynamic diversion rule table; a first judgment unit, for judging, for each piece of flight information extracted from the flight plan message, whether the flight information matches the dynamic diversion rule table; a first execution unit, for, if the flight information does not match the dynamic diversion rule table, executing the step of judging whether each piece of flight information matches the preset static diversion rule table; a second judgment unit, for, if the flight information matches the dynamic diversion rule table, judging whether the flight information is initialized, wherein the initialization is that the flight information has been determined to be divided into a data processing system, and the divided data processing system is the target data processing system or the historical data processing system; a first skipping unit, for, if the flight information has been initialized, skipping the flight information, and executing the step of judging whether the next piece of flight information matches the dynamic diversion rule table; an updating unit, for, if the flight information is not initialized, updating the dynamic diversion rule corresponding to the flight information in the dynamic diversion rule table.
Citation Information
Patent Citations
Flight operation data message analysis system and method
CN111030989A
Flight guarantee information monitoring method, terminal and readable storage medium
CN113420105A