System switching method, device, computer equipment and storage medium

Abstract

The present application relates to a system switching method, apparatus, computer equipment, storage medium and computer program product, and relates to the field of computer technology, and can be used in the field of financial technology or other related fields. The method includes: verifying transaction information according to tag information; when the transaction information meets the tag information, inputting the transaction information into the history system, obtaining a first output result corresponding to the transaction information output by the history system, and synchronizing the first output result to the target system; when the transaction information does not meet the tag information, inputting the transaction information into the history system and the target system respectively, obtaining a second output result corresponding to the transaction information output by the history system, and a third output result corresponding to the transaction information output by the target system; updating the tag information, and when the tag information meets the preset end condition after the update, determining that the history system has successfully switched to the target system. The use of this method can improve the switching accuracy of the system.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a system switching method, apparatus, computer equipment, storage medium, and computer program product. Background Art

[0002] With the development of financial technology, system switching has become crucial to promote the upgrading of financial services and meet the growing needs of new business.

[0003] In traditional technology, when switching systems, transaction information is mainly processed simultaneously by the new system and the old system, and the processing results of the new system and the old system are synchronized; however, this method has the problem of time difference, which can easily cause delays or errors in the synchronization of processing results, resulting in low system switching accuracy. Summary of the Invention

[0004] Based on this, it is necessary to provide a system switching method, apparatus, computer equipment, computer-readable storage medium and computer program product that can improve the switching accuracy of the system in response to the above technical problems.

[0005] In a first aspect, the present application provides a system switching method, comprising:

[0006] Verify the acquired transaction information associated with the financial business based on tag information associated with the historical system and the target system; the tag information is used to represent problem information during the system switching process, and the historical system is used to represent the system corresponding to the historical version of the target system;

[0007] If the transaction information satisfies the tag information, input the transaction information into the history system, obtain a first output result corresponding to the transaction information output by the history system, and synchronize the first output result to the target system;

[0008] If the transaction information does not satisfy the tag information, input the transaction information into the history system and the target system respectively, obtaining a second output result corresponding to the transaction information output by the history system and a third output result corresponding to the transaction information output by the target system;

[0009] updating the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system to obtain updated label information;

[0010] The updated tag information is used as the new tag information, and the process jumps to the step of verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system, until the updated tag information obtained meets the preset end condition, and then it is determined that the historical system has successfully switched to the target system.

[0011] In one embodiment, updating the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system to obtain updated label information includes:

[0012] identifying first target tag information corresponding to the transaction information from the tag information according to the first output result corresponding to the transaction information in the historical system and the first output result corresponding to the transaction information in the target system;

[0013] The first target label information is deleted from the label information to obtain updated label information.

[0014] In one embodiment, updating the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system to obtain updated label information includes:

[0015] performing a comparison process on the second output result corresponding to the transaction information in the historical system and the third output result corresponding to the transaction information in the target system;

[0016] When the second output result and the third output result are different, the label information is updated according to the transaction information to obtain updated label information.

[0017] In one embodiment, when the second output result and the third output result are different, updating the label information according to the transaction information to obtain updated label information includes:

[0018] If the second output result and the third output result are different, generating second target tag information corresponding to the transaction information;

[0019] The second target label information is added to the label information to obtain updated label information.

[0020] In one embodiment, when the second output result and the third output result are different, generating second target tag information corresponding to the transaction information includes:

[0021] If the second output result and the third output result are different, generating error information corresponding to the transaction information;

[0022] generating an error reporting keyword corresponding to the transaction information according to the error reporting information corresponding to the transaction information;

[0023] According to the error reporting keyword corresponding to the transaction information, second target tag information corresponding to the transaction information is generated.

[0024] In one embodiment, before verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system, the process further includes:

[0025] Obtaining problem information during the system switching process;

[0026] filtering out problem information associated with the historical system and the target system from the problem information during the system switching process as target problem information;

[0027] According to the target problem information, tag information associated with the historical system and the target system is determined.

[0028] In one embodiment, before verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system, the process further includes:

[0029] Obtaining transaction information associated with the financial business;

[0030] Preprocessing the transaction information to obtain preprocessed transaction information associated with the financial service;

[0031] The verification of the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system includes:

[0032] The obtained pre-processed transaction information associated with the financial business is verified according to tag information associated with the historical system and the target system.

[0033] In a second aspect, the present application further provides a system switching device, comprising:

[0034] An information verification module is used to verify the acquired transaction information associated with the financial business based on tag information associated with the historical system and the target system; the tag information is used to represent problem information during the system switching process, and the historical system is used to represent the system corresponding to the historical version of the target system;

[0035] a first judgment module configured to, if the transaction information satisfies the tag information, input the transaction information into the history system, obtain a first output result corresponding to the transaction information output by the history system, and synchronize the first output result to the target system;

[0036] a second judgment module configured to, if the transaction information does not satisfy the tag information, input the transaction information into the history system and the target system, respectively, to obtain a second output result corresponding to the transaction information output by the history system and a third output result corresponding to the transaction information output by the target system;

[0037] a label update module, configured to update the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system, thereby obtaining updated label information;

[0038] The target switching module is used to use the updated label information as the new label information and jump to the step of verifying the acquired transaction information associated with the financial business based on the label information associated with the historical system and the target system, until the updated label information obtained meets the preset end condition, then it is determined that the historical system has successfully switched to the target system.

[0039] In a third aspect, the present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0040] Verify the acquired transaction information associated with the financial business based on tag information associated with the historical system and the target system; the tag information is used to represent problem information during the system switching process, and the historical system is used to represent the system corresponding to the historical version of the target system;

[0041] If the transaction information satisfies the tag information, input the transaction information into the history system, obtain a first output result corresponding to the transaction information output by the history system, and synchronize the first output result to the target system;

[0042] If the transaction information does not satisfy the tag information, input the transaction information into the history system and the target system respectively, obtaining a second output result corresponding to the transaction information output by the history system and a third output result corresponding to the transaction information output by the target system;

[0043] updating the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system to obtain updated label information;

[0044] The updated tag information is used as the new tag information, and the process jumps to the step of verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system, until the updated tag information obtained meets the preset end condition, and then it is determined that the historical system has successfully switched to the target system.

[0045] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0046] Verify the acquired transaction information associated with the financial business based on tag information associated with the historical system and the target system; the tag information is used to represent problem information during the system switching process, and the historical system is used to represent the system corresponding to the historical version of the target system;

[0047] If the transaction information satisfies the tag information, input the transaction information into the history system, obtain a first output result corresponding to the transaction information output by the history system, and synchronize the first output result to the target system;

[0048] If the transaction information does not satisfy the tag information, input the transaction information into the history system and the target system respectively, obtaining a second output result corresponding to the transaction information output by the history system and a third output result corresponding to the transaction information output by the target system;

[0049] updating the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system to obtain updated label information;

[0050] The updated tag information is used as the new tag information, and the process jumps to the step of verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system, until the updated tag information obtained meets the preset end condition, and then it is determined that the historical system has successfully switched to the target system.

[0051] In a fifth aspect, the present application further provides a computer program product, comprising a computer program, which, when executed by a processor, implements the following steps:

[0052] Verify the acquired transaction information associated with the financial business based on tag information associated with the historical system and the target system; the tag information is used to represent problem information during the system switching process, and the historical system is used to represent the system corresponding to the historical version of the target system;

[0053] If the transaction information satisfies the tag information, input the transaction information into the history system, obtain a first output result corresponding to the transaction information output by the history system, and synchronize the first output result to the target system;

[0054] If the transaction information does not satisfy the tag information, input the transaction information into the history system and the target system respectively, obtaining a second output result corresponding to the transaction information output by the history system and a third output result corresponding to the transaction information output by the target system;

[0055] updating the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system to obtain updated label information;

[0056] The updated tag information is used as the new tag information, and the process jumps to the step of verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system, until the updated tag information obtained meets the preset end condition, and then it is determined that the historical system has successfully switched to the target system.

[0057] The system switching method, apparatus, computer device, storage medium, and computer program product first verify acquired transaction information associated with financial services based on tag information associated with the historical system and the target system. If the transaction information satisfies the tag information, the transaction information is input into the historical system to obtain a first output result corresponding to the transaction information output by the historical system, and the first output result is synchronized with the target system. If the transaction information does not satisfy the tag information, the transaction information is input into both the historical system and the target system to obtain a second output result corresponding to the transaction information output by the historical system and a third output result corresponding to the transaction information output by the target system. Next, based on the first or second output result corresponding to the transaction information in the historical system and the first or third output result corresponding to the transaction information in the target system, the tag information is updated to obtain updated tag information. The updated tag information is then used as the new tag information, and the process proceeds to the step of verifying acquired transaction information associated with financial services based on the tag information associated with the historical system and the target system. The process continues until the acquired updated tag information meets a preset termination condition, thereby determining that the historical system has successfully switched to the target system. In this way, when switching the system, by verifying the transaction information according to the tag information and performing corresponding processing according to the verification result of the transaction information, the processing method of the transaction information can be judged more accurately, avoiding the simultaneous processing of transaction information, which easily causes synchronization delays or errors in the processing results, resulting in the defect of low system switching accuracy; moreover, by repeatedly verifying and updating the tag information through the output results until the updated tag information meets the preset end conditions, it is conducive to the continuous optimization and improvement of the historical system to the target system, thereby improving the switching accuracy of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following briefly introduces the drawings required for use in the embodiments or related technical descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0059] Figure 1 1 is a flow chart of a system switching method according to an embodiment;

[0060] Figure 2 A schematic diagram of a process for obtaining updated tag information in one embodiment;

[0061] Figure 3 Schematic diagram of a process for updating tag information in one embodiment;

[0062] Figure 4is a flow chart of a system switching method according to another embodiment;

[0063] Figure 5 Schematic diagram of a flow chart of a method for ensuring data consistency in a high-concurrency scenario according to one embodiment;

[0064] Figure 6 is a structural block diagram of a system switching device in one embodiment;

[0065] Figure 7 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0066] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0067] 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 relevant countries and 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.

[0068] In an exemplary embodiment, Figure 1 As shown, a system switching method is provided. This embodiment uses the method applied to a server as an example for illustration; it is understandable that the method can also be applied to a terminal, and can also be applied to a system including a terminal and a server, and is implemented through interaction between the terminal and the server. The terminal can be, but is not limited to, various personal computers, laptops, smartphones, and tablet computers; the server can be implemented as an independent server or a server cluster consisting of multiple servers. In this embodiment, the method includes the following steps:

[0069] Step S101 , verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system; the tag information is used to represent the problem information during the system switching process, and the historical system is used to represent the system corresponding to the historical version of the target system.

[0070] The historical system refers to a system corresponding to a previous version of the target system, and may be a system corresponding to the previous version of the target system, or may refer to a system before the switch.

[0071] The target system refers to the system after the version update, or the system after the switch.

[0072] The tag information refers to the tag information corresponding to the problem information during the system switching process and is used to judge the transaction information. If the transaction information meets the tag information, it means that the transaction information hits the tag information, that is, the transaction information and the tag information match each other. If the transaction information does not meet the tag information, it means that the transaction information does not hit the tag information, that is, the transaction information and the tag information do not match.

[0073] Transaction information may refer to a data flow associated with financial business.

[0074] The problem information during the system switching process refers to common problems that occur during the system switching process.

[0075] Among them, historical versions refer to previous versions, such as the previous version.

[0076] Exemplarily, in response to a system switching instruction, the server obtains problem information during the system switching process from a database, and determines the tag information associated with the historical system and the target system based on the problem information during the system switching process and the correspondence between the problem information and the tag information; then, the server obtains transaction information associated with the financial business from the database, and verifies the obtained transaction information associated with the financial business based on the tag information associated with the historical system and the target system.

[0077] Step S102: When the transaction information satisfies the tag information, the transaction information is input into the history system, a first output result corresponding to the transaction information output by the history system is obtained, and the first output result is synchronized to the target system.

[0078] The first output result refers to the output result corresponding to the transaction information output by the history system when the transaction information meets the tag information.

[0079] Exemplarily, when the transaction information satisfies the tag information, the server inputs the transaction information into the history system, runs the transaction information through the history system, obtains a first output result corresponding to the transaction information output by the history system, and synchronizes the first output result to the target system.

[0080] Step S103: If the transaction information does not meet the tag information, the transaction information is input into the history system and the target system respectively to obtain a second output result corresponding to the transaction information output by the history system and a third output result corresponding to the transaction information output by the target system.

[0081] The second output result refers to the output result corresponding to the transaction information output by the history system when the transaction information does not meet the label information.

[0082] The third output result refers to the output result corresponding to the transaction information output by the target system when the transaction information does not meet the label information.

[0083] Exemplarily, when the transaction information does not meet the tag information, the server inputs the transaction information into the history system, runs the transaction information through the history system, and obtains the second output result corresponding to the transaction information output by the history system; then, the server inputs the transaction information into the target system, runs the transaction information through the target system, and obtains the third output result corresponding to the transaction information output by the target system.

[0084] Step S104 : updating the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system to obtain updated label information.

[0085] Here, updating the tag information refers to the process of adding or deleting the tag information.

[0086] The updated label information refers to the updated label information.

[0087] Exemplarily, the server updates the label information according to the first output result corresponding to the transaction information in the historical system and the first output result corresponding to the transaction information in the target system to obtain updated label information.

[0088] Furthermore, the server updates the label information according to the second output result corresponding to the transaction information in the historical system and the third output result corresponding to the transaction information in the target system to obtain updated label information.

[0089] In step S105, the updated tag information is used as the new tag information, and the process jumps to the step of verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system, until the updated tag information obtained meets the preset end condition, and it is determined that the historical system has successfully switched to the target system.

[0090] The preset end condition refers to a pre-set end condition, such as a preset quantity, used to determine the updated tag information. If the updated tag information obtained satisfies the preset end condition, that is, the updated tag information obtained satisfies the preset quantity, such as if the quantity corresponding to the updated tag information obtained is 0, then it is determined that the historical system has successfully switched to the target system. If the updated tag information obtained does not meet the preset end condition, that is, the updated tag information obtained does not meet the preset quantity, such as if the quantity corresponding to the updated tag information obtained is not 0, then the updated tag information is used as the new tag information, and the process jumps to the step of verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system.

[0091] Exemplarily, the server judges the updated tag information based on the preset end condition; if the updated tag information does not meet the preset end condition, the updated tag information is used as the new tag information, and the process jumps to the step of verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system, until the updated tag information obtained meets the preset end condition, and it is determined that the historical system has successfully switched to the target system.

[0092] Furthermore, after determining that the historical system has successfully switched to the target system, the server obtains the system identification information corresponding to the historical system and the target system, such as the version numbers corresponding to the historical system and the target system, and obtains the switching time information corresponding to the successful switching of the historical system to the target system; then, the server generates version update information corresponding to the historical system and the target system based on the system identification information and the switching time information.

[0093] In the above-mentioned system switching method, the acquired transaction information associated with the financial business is first verified based on the tag information associated with the historical system and the target system. If the transaction information satisfies the tag information, the transaction information is input into the historical system to obtain a first output result corresponding to the transaction information output by the historical system, and the first output result is synchronized to the target system. If the transaction information does not satisfy the tag information, the transaction information is input into the historical system and the target system respectively to obtain a second output result corresponding to the transaction information output by the historical system and a third output result corresponding to the transaction information output by the target system. Then, based on the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system, the tag information is updated to obtain updated tag information. Then, the updated tag information is used as the new tag information, and the process jumps to the step of verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system. When the obtained updated tag information meets the preset end condition, it is determined that the historical system has successfully switched to the target system. In this way, when switching the system, by verifying the transaction information according to the tag information and performing corresponding processing according to the verification result of the transaction information, the processing method of the transaction information can be judged more accurately, avoiding the simultaneous processing of transaction information, which easily causes synchronization delays or errors in the processing results, resulting in the defect of low system switching accuracy; moreover, by repeatedly verifying and updating the tag information through the output results until the updated tag information meets the preset end conditions, it is conducive to the continuous optimization and improvement of the historical system to the target system, thereby improving the switching accuracy of the system.

[0094] In an exemplary embodiment, Figure 2 As shown, the above step S104 updates the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system to obtain the updated label information, which specifically includes the following steps:

[0095] Step S201 : identifying first target tag information corresponding to the transaction information from the tag information according to the first output result corresponding to the transaction information in the historical system and the first output result corresponding to the transaction information in the target system.

[0096] Step S202: Delete the first target tag information from the tag information to obtain updated tag information.

[0097] Among them, in the case of the output results corresponding to the transaction information in the historical system and the target system, the label information corresponding to the transaction information.

[0098] Exemplarily, the server identifies the first target tag information corresponding to the transaction information from the tag information based on the first output result corresponding to the transaction information in the historical system and the first output result corresponding to the transaction information in the target system; then, the server deletes the first target tag information from the tag information and obtains tag information other than the first target tag information as the updated tag information.

[0099] For example, refer to Figure 3 The server identifies the first target tag information corresponding to the transaction information from the special tag list, such as tag 1, based on the first output result corresponding to the transaction information in the historical system and the first output result corresponding to the transaction information in the target system. Then, the server deletes tag 1 from the special tag list and obtains tag information other than tag 1, such as tag 2, etc., and uses these tags as updated tag information.

[0100] In this embodiment, when it is determined that the output results corresponding to the transaction information in the historical system and the target system are the same, the label information corresponding to the transaction information is deleted from the label information, so that the updated label information is more targeted and practical, which is conducive to maintaining the timeliness and accuracy of the label information.

[0101] In an exemplary embodiment, the above-mentioned step S104 updates the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system to obtain updated label information, and specifically includes the following steps: comparing the second output result corresponding to the transaction information in the historical system and the third output result corresponding to the transaction information in the target system; when the second output result and the third output result are different, updating the label information according to the transaction information to obtain updated label information.

[0102] Comparison refers to the process of comparing the output results of transaction information in the historical system and the target system. It should be noted that information such as date and time stamp does not need to be compared.

[0103] Exemplarily, the server preprocesses the second output result corresponding to the transaction information in the historical system and the third output result corresponding to the transaction information in the target system to obtain the preprocessed second output result and the preprocessed third output result; for example, the server deletes the date, timestamp and other information in the second output result and the third output result to obtain the preprocessed second output result and the preprocessed third output result; then, the server compares the preprocessed second output result and the preprocessed third output result; if the second output result and the third output result are different, the server updates the label information according to the transaction information to obtain the updated label information.

[0104] In this embodiment, by comparing the output results corresponding to the transaction information in the historical system and the target system, the differences between the transaction information processed by the historical system and the target system can be discovered in a timely manner; moreover, when the results are different, the label information is updated according to the transaction information, which can ensure the accuracy and timeliness of the label information and better reflect the actual situation.

[0105] In an exemplary embodiment, when the second output result and the third output result are different, the label information is updated according to the transaction information to obtain updated label information, which specifically includes the following steps: when the second output result and the third output result are different, generating second target label information corresponding to the transaction information; and adding the second target label information to the label information to obtain updated label information.

[0106] The second target label information refers to the label information corresponding to the transaction information when the second output result and the third output result are different.

[0107] Exemplarily, when the second output result and the third output result are different, the server generates second target tag information corresponding to the transaction information based on the transaction information; then, the server adds the second target tag information to the tag information to obtain the added tag information as the updated tag information.

[0108] For example, refer to Figure 3 When the second output result and the third output result are different, the server generates the second target tag information corresponding to the transaction information, such as tag 3; then, the server adds tag 3 to the special tag list and obtains the added special tag list as the updated tag information.

[0109] In this embodiment, when it is clear that the second output result and the third output result are different, the newly generated second target label information is added to the label information, so that the label information is updated, which can better reflect the actual situation of the system switching and is beneficial to subsequent analysis and decision-making.

[0110] In an exemplary embodiment, when the second output result and the third output result are different, second target label information corresponding to the transaction information is generated, which specifically includes the following steps: when the second output result and the third output result are different, error information corresponding to the transaction information is generated; based on the error information corresponding to the transaction information, an error keyword corresponding to the transaction information is generated; based on the error keyword corresponding to the transaction information, second target label information corresponding to the transaction information is generated.

[0111] The error message refers to the error reason corresponding to the transaction information, such as the customer name does not match.

[0112] The error keyword refers to the error code corresponding to the error cause, such as 00008368.

[0113] Exemplarily, when the second output result and the third output result are different, the server generates error information corresponding to the transaction information based on the transaction information; then, the server generates an error keyword corresponding to the error information as the error keyword corresponding to the transaction information based on the error information corresponding to the transaction information and the correspondence between the error information and the error keyword; then, the server generates tag information corresponding to the error keyword as the second target tag information corresponding to the transaction information based on the error keyword corresponding to the transaction information and the correspondence between the error keyword and the tag information.

[0114] For example, refer to Figure 3 When the second output result and the third output result are different, the server performs quasi-real-time calculations, dynamically counts the relevant records of system failures and successes in the past 24 hours, obtains the error reasons corresponding to the transaction information based on the failure records, generates error keywords corresponding to the error reasons based on the error reasons, and generates tag information corresponding to the error keywords based on the error keywords; then, the server adds to the special tag list based on the tag information corresponding to these error keywords to obtain updated tag information.

[0115] Furthermore, based on the failed record, the server obtains the error information corresponding to the transaction information: "Customer name does not match", and generates the error keyword corresponding to the error information (i.e., error code 00008368) based on the error information. Based on the error keyword, the server obtains the tag information TAG00008368 corresponding to the error keyword as the tag information corresponding to the transaction information.

[0116] In this embodiment, when the second output result and the third output result are different, error information corresponding to the transaction information is generated, which is conducive to discovering possible problems. Moreover, based on the error information corresponding to the transaction information, label information corresponding to the transaction information is generated, making the label information more targeted and facilitating better processing of the transaction information.

[0117] In an exemplary embodiment, the above-mentioned step S101, before verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system, specifically includes the following steps: obtaining problem information during the system switching process; filtering out the problem information associated with the historical system and the target system from the problem information during the system switching process as target problem information; and determining the tag information associated with the historical system and the target system based on the target problem information.

[0118] The target problem information refers to the problem information associated with the historical system and the target system in the problem information during the system switching process, such as common problems during the switching process of a high-concurrency system.

[0119] Exemplarily, in response to a system switching instruction, the server obtains problem information during the system switching process from a database; then, the server filters out problem information associated with the historical system and the target system from the problem information during the system switching process as target problem information; then, the server determines the label information corresponding to the target problem information based on the target problem information and the correspondence between the problem information and the label information, as the label information associated with the historical system and the target system.

[0120] In this embodiment, by obtaining problem information during the system switching process, it is helpful to promptly discover problems that may affect the normal operation of the system during the system switching; moreover, filtering out problem information related to the historical system and the target system from the problem information is conducive to improving the accuracy of determining the problem information, thereby improving the accuracy of determining the label information.

[0121] In an exemplary embodiment, the above-mentioned step S101, before verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system, specifically includes the following steps: acquiring the transaction information associated with the financial business; preprocessing the transaction information to obtain preprocessed transaction information associated with the financial business.

[0122] Then, based on the tag information associated with the historical system and the target system, the acquired transaction information associated with the financial business is verified, specifically including the following steps: based on the tag information associated with the historical system and the target system, the acquired pre-processed transaction information associated with the financial business is verified.

[0123] The pre-processed transaction information refers to the transaction information that has been processed in advance.

[0124] Exemplarily, the server obtains transaction information associated with the financial business from the database; then, the server preprocesses the transaction information to obtain preprocessed transaction information associated with the financial business; for example, the server deletes abnormal information in the transaction information to obtain processed transaction information as the preprocessed transaction information associated with the financial business; then, the server verifies the obtained preprocessed transaction information associated with the financial business based on the tag information associated with the historical system and the target system.

[0125] In this embodiment, by obtaining transaction information associated with financial services and preprocessing it, more targeted and accurate transaction information can be obtained. The preprocessed transaction information can provide a more reliable basis for decision-making and facilitate subsequent judgment and processing.

[0126] In an exemplary embodiment, Figure 4 As shown, another system switching method is provided, which is described by taking the application of this method to a server as an example, and includes the following steps:

[0127] Step S401, acquiring transaction information associated with the financial business; preprocessing the transaction information to obtain preprocessed transaction information associated with the financial business.

[0128] Step S402, obtaining problem information during the system switching process; filtering out problem information associated with the historical system and the target system from the problem information during the system switching process as target problem information; determining tag information associated with the historical system and the target system based on the target problem information; the historical system is used to represent the system corresponding to the historical version of the target system.

[0129] Step S403 : verifying the acquired pre-processed transaction information associated with the financial business according to the tag information associated with the historical system and the target system.

[0130] Step S404: If the pre-processed transaction information satisfies the tag information, the pre-processed transaction information is input into the history system, a first output result corresponding to the pre-processed transaction information output by the history system is obtained, and the first output result is synchronized to the target system.

[0131] Step S405: Identify first target tag information corresponding to the preprocessed transaction information from the tag information based on the first output result corresponding to the preprocessed transaction information in the historical system and the first output result corresponding to the preprocessed transaction information in the target system; delete the first target tag information from the tag information to obtain updated tag information.

[0132] Step S406: If the pre-processed transaction information does not satisfy the label information, the pre-processed transaction information is input into the history system and the target system respectively, and a second output result corresponding to the pre-processed transaction information output by the history system and a third output result corresponding to the pre-processed transaction information output by the target system are obtained.

[0133] Step S407 compares the second output result corresponding to the preprocessed transaction information in the historical system with the third output result corresponding to the preprocessed transaction information in the target system. If the second output result and the third output result are different, an error message corresponding to the preprocessed transaction information is generated. Based on the error message corresponding to the preprocessed transaction information, an error keyword corresponding to the preprocessed transaction information is generated. Based on the error keyword corresponding to the preprocessed transaction information, second target tag information corresponding to the preprocessed transaction information is generated. The second target tag information is added to the tag information to obtain updated tag information.

[0134] In step S408, the updated tag information is used as the new tag information, and the process jumps to the step of verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system, until the updated tag information obtained meets the preset end condition, and it is determined that the historical system has successfully switched to the target system.

[0135] In the above-mentioned system switching method, when performing system switching, by verifying the transaction information according to the label information and performing corresponding processing according to the verification result of the transaction information, the processing method of the transaction information can be judged more accurately, avoiding the simultaneous processing of transaction information, which easily causes synchronization delays or errors in the processing results, resulting in the defect of low system switching accuracy; moreover, by repeatedly verifying and updating the label information through the output results until the updated label information meets the preset end conditions, it is conducive to the continuous optimization and improvement from the historical system to the target system, thereby improving the switching accuracy of the system.

[0136] In an exemplary embodiment, in order to more clearly illustrate the system switching method provided by the embodiment of the present application, the system switching method is specifically described below with a specific embodiment. In one embodiment, Figure 5As shown, the present application also provides a method for ensuring data consistency in a high-concurrency scenario. When switching systems, the acquired transaction information associated with the financial business is first verified according to the tag information associated with the historical system and the target system. If the transaction information meets the tag information, the transaction information is input into the historical system to obtain the first output result corresponding to the transaction information output by the historical system, and the first output result is synchronized to the target system. If the transaction information does not meet the tag information, the transaction information is input into the historical system and the target system respectively to obtain the second output result corresponding to the transaction information output by the historical system and the third output result corresponding to the transaction information output by the target system. Then, according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system, the tag information is updated to obtain the updated tag information. Then, the updated tag information is used as the new tag information, and the process jumps to the step of verifying the acquired transaction information associated with the financial business according to the tag information associated with the historical system and the target system, until the updated tag information meets the preset end condition, then it is determined that the historical system has successfully switched to the target system. Specifically including the following contents:

[0137] The present invention proposes the concept of a core "baffle", which uses big data analysis algorithms as the background, summarizes the common problems in the switching process between the old and new systems, and extracts special tags, which can be continuously iterated and updated during the operation of high-concurrency systems, thereby gradually diverting transactions from the old system to the new system, without any customer awareness and without the need for manual operation and maintenance. Compared with traditional switching modes, it avoids performance problems that may be caused by excessive transaction volume in the "parallel" and "dual-write" modes, reduces system consumption, and avoids systemic risks. Since this solution ensures intelligent emergency handling when errors occur during operation on the new system, it fundamentally guarantees the data consistency of the old and new systems, thereby ensuring the quality of the switch between the old and new systems.

[0138] Since there are one-to-many and many-to-one relationships between the table structures of the old and new systems, using database synchronization will make the merge processing logic very complicated, and the database processing method in high-concurrency scenarios also has timeliness issues, making the database synchronization method not applicable in this scenario. The "baffle" plays an important role. It not only ensures the accuracy of this transaction and the consistency of the data of the old and new systems, but also saves the comparison results of the consistency of the data of the old and new systems. The key and difficult problem that the present invention needs to overcome is the data consistency problem of the old and new systems in high-concurrency scenarios, and can update labels in real time, thereby greatly reducing the operation and maintenance costs while ensuring the public opinion that may be caused by the switch, and ensuring that customer business is not affected.

[0139] The present invention provides a method for ensuring data consistency in high-concurrency scenarios, namely, setting special tags through big data algorithms, and further provides a data comparison method between new and old systems to gradually repair inconsistent data, thereby achieving seamless switching between new and old systems to produce the smallest granular impact on downstream.

[0140] Step 1: All entrances need to be changed to the new system as the entrance. After entering the new system, you will enter the core "baffle" module of the new system.

[0141] Step 2: Run the new system according to the relevant input parameters.

[0142] In step 3, the "baffle" matches the special tag to determine whether it hits the special tag: if the special tag is not hit, the transaction will be based on the result of the new system operation and the response will be based on the new system result; if the special tag is hit, it means that there is a problem with the data running in the new system. According to the baffle principle, the relevant transactions must be diverted to the original old system, the input parameters must be run in the old system again, and the response will be based on the old system's operation results. At the same time, the new system data is updated, and the relevant logs are synchronously registered for subsequent analysis and use.

[0143] In step 4, the "Match" module can compare multiple input and output parameters of the old and new systems one by one, and automatically match them. If any field does not match, the match will fail. Special fields such as dates and timestamps can be set to be ignored.

[0144] In step 5, the backend big data analysis algorithm asynchronously synchronizes data and performs near-real-time calculations, dynamically tallying system failure and success records from the past 24 hours. For failed records, after preliminary analysis based on error causes, the system identifies those errors based on error keywords that require re-transactions in the legacy system and registers them with special tags. The special tags are then updated in near-real time based on the calculation results, and the updated special tags can be applied to subsequent transactions.

[0145] Step 6: Analyze the application processing of the new system based on the registration records, and arrange version updates in a timely manner.

[0146] Step 7. After the version is updated, the big data analysis algorithm will continue to run in the background, constantly adding and deleting special tags. After the version is updated, the big data analysis algorithm will automatically compare and determine the direction of subsequent transactions, without the need for manual switching or emergency processing.

[0147] In step 8, when a problem occurs in the new system, the "baffle" will use the operating results of the old system as a response and write to the new system simultaneously. This is invisible to the business and transparent to the operation and maintenance personnel, greatly reducing the operation and maintenance costs.

[0148] Step 9: Through continuous version updates and iterations, the final number of special tags is 0, which means that all traffic has been directed to the new system and the switch between the old and new systems is complete.

[0149] In the above embodiment, when switching systems, by verifying transaction information based on tag information and performing corresponding processing based on the verification results of the transaction information, the processing method of the transaction information can be more accurately determined, avoiding the situation where simultaneous processing of transaction information easily causes synchronization delays or errors in the processing results, resulting in the defect of low system switching accuracy; moreover, by outputting the results and repeatedly verifying and updating the tag information until the updated tag information meets the preset end conditions, it is conducive to the continuous optimization and improvement of the historical system to the target system, thereby improving the switching accuracy of the system. At the same time, the present application can solve the problem of data consistency not being guaranteed in high-concurrency scenarios during the switching process between the old and new financial systems, ensure the data consistency of the new and old systems, greatly reduce the switching cost and switching risk, and the application does not need to pay attention to data quality issues after the switching, as the invention ensures data quality issues; the present application can automatically shield the impact of the switching back between the old and new systems on the data, ensure the synchronization of the new system data after the system is switched back, and the switching does not require the old and new systems to cooperate in emergency switching, and no manual intervention is required; the present application can automatically divert traffic to the new system for switching after the new system is repaired, greatly reducing the switching workload and ensuring customer service quality.

[0150] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0151] Based on the same inventive concept, embodiments of the present application also provide a system switching device for implementing the aforementioned system switching method. The solution provided by this device is similar to the solution described in the aforementioned method. Therefore, the specific limitations in one or more system switching device embodiments provided below can be found in the above-described limitations on the system switching method and will not be further elaborated here.

[0152] In an exemplary embodiment, Figure 6As shown, a system switching device is provided, including: an information verification module 601, a first judgment module 602, a second judgment module 603, a label update module 604 and a target switching module 605, wherein:

[0153] The information verification module 601 is used to verify the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system; the tag information is used to represent the problem information during the system switching process, and the historical system is used to represent the system corresponding to the historical version of the target system.

[0154] The first judgment module 602 is used to input the transaction information into the history system when the transaction information meets the tag information, obtain a first output result corresponding to the transaction information output by the history system, and synchronize the first output result to the target system.

[0155] The second judgment module 603 is used to input the transaction information into the history system and the target system respectively when the transaction information does not meet the label information, and obtain a second output result corresponding to the transaction information output by the history system and a third output result corresponding to the transaction information output by the target system.

[0156] The label update module 604 is used to update the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system to obtain updated label information.

[0157] The target switching module 605 is used to use the updated tag information as the new tag information, and jump to the step of verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system, until the updated tag information obtained meets the preset end condition, then it is determined that the historical system has successfully switched to the target system.

[0158] In an exemplary embodiment, the label update module 604 is also used to identify the first target label information corresponding to the transaction information from the label information based on the first output result corresponding to the transaction information in the historical system and the first output result corresponding to the transaction information in the target system; delete the first target label information from the label information to obtain updated label information.

[0159] In an exemplary embodiment, the label update module 604 is also used to compare the second output result corresponding to the transaction information in the historical system and the third output result corresponding to the transaction information in the target system; when the second output result and the third output result are different, the label information is updated according to the transaction information to obtain updated label information.

[0160] In an exemplary embodiment, the label update module 604 is further configured to generate second target label information corresponding to the transaction information when the second output result and the third output result are different; and add the second target label information to the label information to obtain updated label information.

[0161] In an exemplary embodiment, the label update module 604 is also used to generate error information corresponding to the transaction information when the second output result and the third output result are different; generate error keywords corresponding to the transaction information based on the error information corresponding to the transaction information; and generate second target label information corresponding to the transaction information based on the error keywords corresponding to the transaction information.

[0162] In an exemplary embodiment, the system switching device also includes a label determination module for obtaining problem information during the system switching process; filtering out problem information associated with the historical system and the target system from the problem information during the system switching process as target problem information; and determining label information associated with the historical system and the target system based on the target problem information.

[0163] In an exemplary embodiment, the system switching device further includes an information processing module configured to obtain transaction information associated with the financial service; and pre-process the transaction information to obtain pre-processed transaction information associated with the financial service.

[0164] Each module in the above-mentioned system switching device can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0165] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 7As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O) and a communication interface. The processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store data such as tag information and transaction information. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a system switching method is implemented.

[0166] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0167] In an exemplary embodiment, a computer device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0168] In an exemplary embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0169] In an exemplary embodiment, a computer program product is provided, including a computer program. When the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0170] 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 analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0171] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the above-mentioned embodiments. In particular, any reference to memory, database, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processors involved in the various embodiments provided herein may be, but are not limited to, general-purpose processors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), data processing logic devices based on quantum computing, and the like.

[0172] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0173] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A system switching method, characterized in that: The method comprises: Verify the acquired transaction information associated with the financial business based on tag information associated with the historical system and the target system; the tag information is used to represent problem information during the system switching process, and the historical system is used to represent the system corresponding to the historical version of the target system; If the transaction information satisfies the tag information, input the transaction information into the history system, obtain a first output result corresponding to the transaction information output by the history system, and synchronize the first output result to the target system; If the transaction information does not satisfy the tag information, input the transaction information into the history system and the target system respectively, obtaining a second output result corresponding to the transaction information output by the history system and a third output result corresponding to the transaction information output by the target system; updating the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system to obtain updated label information; The updated tag information is used as the new tag information, and the process jumps to the step of verifying the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system, until the updated tag information obtained meets the preset end condition, and then it is determined that the historical system has successfully switched to the target system.

2. The method according to claim 1, characterized in that The updating of the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system to obtain updated label information includes: identifying first target tag information corresponding to the transaction information from the tag information according to the first output result corresponding to the transaction information in the historical system and the first output result corresponding to the transaction information in the target system; The first target label information is deleted from the label information to obtain updated label information.

3. The method according to claim 1, characterized in that The updating of the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system to obtain updated label information includes: performing a comparison process on the second output result corresponding to the transaction information in the historical system and the third output result corresponding to the transaction information in the target system; When the second output result and the third output result are different, the label information is updated according to the transaction information to obtain updated label information.

4. The method according to claim 3, characterized in that When the second output result and the third output result are different, updating the label information according to the transaction information to obtain updated label information includes: If the second output result and the third output result are different, generating second target tag information corresponding to the transaction information; The second target label information is added to the label information to obtain updated label information.

5. The method according to claim 4, characterized in that When the second output result and the third output result are different, generating second target tag information corresponding to the transaction information includes: If the second output result and the third output result are different, generating error information corresponding to the transaction information; generating an error reporting keyword corresponding to the transaction information according to the error reporting information corresponding to the transaction information; According to the error reporting keyword corresponding to the transaction information, second target tag information corresponding to the transaction information is generated.

6. The method according to claim 1, wherein Before verifying the acquired transaction information related to financial services based on the tag information associated with the historical system and the target system, the following steps are also included: Obtaining problem information during the system switching process; filtering out problem information associated with the historical system and the target system from the problem information during the system switching process as target problem information; According to the target problem information, tag information associated with the historical system and the target system is determined.

7. The method according to any one of claims 1 to 6, characterized in that Before verifying the acquired transaction information related to financial services based on the tag information associated with the historical system and the target system, the following steps are also included: Obtaining transaction information associated with the financial business; Preprocessing the transaction information to obtain preprocessed transaction information associated with the financial service; The verification of the acquired transaction information associated with the financial business based on the tag information associated with the historical system and the target system includes: The obtained pre-processed transaction information associated with the financial business is verified according to tag information associated with the historical system and the target system.

8. A system switching device, characterized in that: The device comprises: An information verification module is used to verify the acquired transaction information associated with the financial business based on tag information associated with the historical system and the target system; the tag information is used to represent problem information during the system switching process, and the historical system is used to represent the system corresponding to the historical version of the target system; a first judgment module configured to, if the transaction information satisfies the tag information, input the transaction information into the history system, obtain a first output result corresponding to the transaction information output by the history system, and synchronize the first output result to the target system; a second judgment module configured to, if the transaction information does not satisfy the tag information, input the transaction information into the history system and the target system, respectively, to obtain a second output result corresponding to the transaction information output by the history system and a third output result corresponding to the transaction information output by the target system; a label update module, configured to update the label information according to the first output result or the second output result corresponding to the transaction information in the historical system and the first output result or the third output result corresponding to the transaction information in the target system, thereby obtaining updated label information; The target switching module is used to use the updated label information as the new label information and jump to the step of verifying the acquired transaction information associated with the financial business based on the label information associated with the historical system and the target system, until the updated label information obtained meets the preset end condition, then it is determined that the historical system has successfully switched to the target system.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

11. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images