A method and apparatus for processing transaction requests during the switchover between old and new systems.
By modifying the routing strategies of the old and new systems in real time, the problem of low transaction request processing efficiency during the switchover process was solved, enabling uninterrupted processing and continuous operation of transaction requests, thus improving the user experience.
Patent Information
- Application Number
- CN202310007401.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-01-04
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2043-01-04
AI Technical Summary
During the switchover between the old and new systems, the poor stability of the new system caused transaction requests to fail to switch between the old and new systems. The old system had to shut down to process the transaction requests, resulting in low transaction processing efficiency, long user waiting times, and a poor service experience.
By modifying the routing policies of the new and old systems in real time, and based on the whitelist policy of transaction requests, transaction requests are forwarded to the old system or other alternative systems for execution, ensuring uninterrupted and continuous operation of transaction services.
It enables uninterrupted transaction processing during the transition between the old and new systems, ensuring real-time response to transaction requests and continuous operation of online transactions, thereby improving transaction processing efficiency and enhancing user satisfaction.
Smart Images

Figure CN116414628B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of financial technology, and in particular to a method and apparatus for processing transaction requests during the switching between old and new systems. Background Technology
[0002] Online trading refers to the provision of real-time trading services to external entities through a specified communication protocol in a distributed system. During the upgrade of an existing online trading system, it is necessary to switch online trading from the old system to the new system. During this switchover, fixed switching rules are typically pre-configured for the transaction transition between the old and new systems. For example, if transaction 'a' in the old system is switched to transaction 'b' in the new system, the relationship between 'a' and 'b' is solidified, thus switching transaction requests received by the old system from the old system to transaction requests received by the new system from the new system according to the fixed switching rules.
[0003] In the process of realizing this invention, the inventors discovered at least the following problems in the prior art:
[0004] Due to the poor stability of the new system, frequent failures occur, causing transaction requests to fail to switch between the new and old systems. In this case, the old system needs to be shut down and restarted before the transaction requests can be reprocessed. Since the old system cannot receive new transaction requests during the shutdown period, the switching between the new and old systems reduces the efficiency of transaction processing, resulting in longer waiting times for users and a poor service experience. Summary of the Invention
[0005] In view of this, embodiments of the present invention provide a method and apparatus for processing transaction requests during the switching process between old and new systems. This method can modify the routing strategies of the old and new systems in real time, enabling uninterrupted transaction processing during the switching process. It ensures real-time response to transaction requests and continuous and stable operation of online transactions, avoids the impact of system switching on transaction services, and enables transaction request processing without service interruption. This greatly improves transaction processing efficiency and enhances user satisfaction.
[0006] Furthermore, since the routing strategy is not a fixed rule but a routing strategy that can be modified and adjusted in real time, in the event of a failure in the new system, the routing strategy can be modified immediately to forward transaction requests to the old system or other alternative systems for execution, ensuring uninterrupted and continuous operation of the transaction service.
[0007] To achieve the above objectives, according to one aspect of the present invention, a method for processing transaction requests during a switchover between old and new systems is provided. The method is applied to an old system server and includes:
[0008] Receive transaction requests sent by the old system terminal;
[0009] Based on the operating stage of the new system server, the routing strategy corresponding to the transaction request is located in memory; wherein, the routing strategy includes a whitelist strategy;
[0010] If the transaction request conforms to the whitelist policy, the transaction request is forwarded to the new system server, and the request processing result returned by the new system server is received.
[0011] If the exception code of the request processing result is an old system identifier, the routing strategy of the transaction request is modified in real time, and the transaction request is processed according to the real-time modified routing strategy.
[0012] Optionally, the routing strategy further includes an old system strategy, and the real-time modification of the routing strategy for the transaction request, processing the transaction request according to the real-time modified routing strategy, includes:
[0013] The transaction identifier corresponding to the transaction request is removed from the whitelist policy, and the transaction identifier corresponding to the transaction request is added to the old system policy, so that the old system server corresponding to the old system policy can process the transaction request.
[0014] Optionally, the whitelist policy includes an account whitelist, a second-level bank whitelist, or a first-level bank whitelist, and the transaction identifier includes a transaction account, a second-level bank number, and a first-level bank number; the step of deleting the transaction identifier corresponding to the transaction request from the whitelist policy and adding the transaction identifier corresponding to the transaction request to the old system policy includes:
[0015] Remove the transaction account associated with the transaction request from the account whitelist and add the transaction account associated with the transaction request to the old system policy; or,
[0016] Remove the second-level row number corresponding to the transaction account or transaction card number in the transaction request from the second-level row whitelist, and add the second-level row number corresponding to the transaction account or transaction card number in the transaction request to the old system policy; or,
[0017] Remove the first-level row number corresponding to the transaction account or transaction card number of the transaction request from the first-level row whitelist, and add the first-level row number corresponding to the transaction account or transaction card number of the transaction request to the old system policy.
[0018] Optionally, the operation phases of the new system server include a branch account trial phase, a secondary bank trial phase, and a primary bank trial phase; the step of searching for the routing strategy corresponding to the transaction request in memory according to the operation phase of the new system server includes:
[0019] During the trial period of the branch account, the routing strategy corresponding to the transaction request is an account whitelist;
[0020] During the trial phase of the second-level row, the routing strategy corresponding to the transaction request is the second-level row whitelist;
[0021] During the trial phase of the first-level bank, the routing strategy corresponding to the transaction request is the first-level bank whitelist.
[0022] Optionally, the routing strategy also includes a new system strategy, and the operation phase of the new system server also includes a formal launch phase, which further includes:
[0023] During the formal launch phase, the routing strategy corresponding to the transaction request is the new system strategy.
[0024] Optionally, if the routing strategy for the transaction request is a new system strategy, it further includes:
[0025] The transaction request is forwarded to the new system server, and the request processing result returned by the new system server is received.
[0026] If the exception code of the request processing result is an old system identifier, the transaction identifier corresponding to the transaction request is deleted from the new system policy in real time, and the transaction identifier corresponding to the transaction request is added to the old system policy, and the old system server processes the transaction request.
[0027] Optionally, determining the whitelist strategy includes:
[0028] During the trial period of the branch accounts, one or more target transaction accounts covering all business functions of the branch are selected from one or more branches to be tried, and an account whitelist is constructed using the target transaction accounts.
[0029] Optionally, it also includes:
[0030] If the processing results of the transaction requests of each target transaction account in the trial phase of the branch account are all successful, the trial phase of the secondary bank is entered. One or more target secondary banks covering all business functions of the secondary bank are selected from the trial secondary banks, and a secondary bank whitelist is constructed using the secondary bank number of the target secondary banks.
[0031] Optionally, it also includes:
[0032] If the transaction requests of all target secondary banks in the trial phase of the secondary bank are successfully processed, the trial phase of the primary bank is entered. One or more target primary banks that cover all business functions of the primary bank are selected from the primary banks to be tested, and a primary bank whitelist is constructed using the primary bank number of the target primary banks.
[0033] Optionally, determining that the transaction request conforms to the whitelist policy includes:
[0034] Obtain the account identifier field and / or card number identifier field from the request message of the transaction request;
[0035] The transaction request is determined to conform to the whitelist policy by using the values of the account identifier field and / or card number identifier field.
[0036] Optionally, determining whether a transaction request conforms to the whitelist policy based on the value of the account identifier field includes:
[0037] If the request message of the transaction request includes an account identifier field, the transaction account of the transaction request shall be determined according to the value of the account identifier field;
[0038] The transaction account in the transaction request is compared with the account whitelist. If the transaction account in the transaction request belongs to the account whitelist, the transaction request is determined to comply with the whitelist policy; or...
[0039] A second-level row matching request, including the transaction account of the transaction request, is sent to the transaction information server. The server returns the second-level row number corresponding to the transaction account of the transaction request. This second-level row number is compared with the second-level row whitelist. If the second-level row number corresponding to the transaction account of the transaction request belongs to the second-level row whitelist, the transaction request is determined to conform to the whitelist policy; or...
[0040] The transaction information server sends a first-level row matching request, which includes the transaction account of the transaction request, to the transaction information server. The transaction information server returns the first-level row number corresponding to the transaction account of the transaction request. The transaction information server compares the first-level row number corresponding to the transaction account of the transaction request with the first-level row whitelist. If the first-level row number corresponding to the transaction account of the transaction request belongs to the first-level row whitelist, the transaction request is determined to conform to the whitelist policy.
[0041] Optionally, determining whether a transaction request conforms to the whitelist policy based on the value of the card number identifier field includes:
[0042] If the request message of the transaction request includes a card number identifier field, the transaction card number of the transaction request is determined based on the value of the card number identifier field;
[0043] An account matching request, including the transaction card number of the transaction request, is sent to the transaction information server. The transaction information server returns the transaction account corresponding to the transaction card number of the transaction request. The transaction account of the transaction request is compared with the account whitelist. If the transaction account of the transaction request belongs to the account whitelist, the transaction request is determined to comply with the whitelist policy; or...
[0044] A secondary row matching request, including the transaction card number of the transaction request, is sent to the transaction information server. The server returns a secondary row number corresponding to the transaction card number of the transaction request. This secondary row number is compared with the secondary row whitelist. If the secondary row number corresponding to the transaction card number of the transaction request belongs to the secondary row whitelist, the transaction request is determined to conform to the whitelist policy; or...
[0045] A first-level row matching request, including the transaction card number of the transaction request, is sent to the transaction information server. The transaction information server returns the first-level row number corresponding to the transaction card number of the transaction request. The first-level row number corresponding to the transaction card number of the transaction request is compared with the first-level row whitelist. If the first-level row number corresponding to the transaction card number of the transaction request belongs to the first-level row whitelist, the transaction request is determined to conform to the whitelist policy.
[0046] Optionally, the account identifier field can be any of the following fields: standard account field, personalized account field, or anonymous account field, and the card number identifier field can be any of the following fields: standard card number field, personalized card number field, or anonymous card number field.
[0047] Optionally, the personalized account field includes a processing identifier, a transaction account, and a verification code; the personalized card number field includes a processing identifier, a transaction card number, and a verification code; and determining the transaction account or transaction card number of the transaction request based on the value of the account identifier field or the card number identifier field includes:
[0048] The processing identifier and the verification code are deleted from the value of the personalized account field or the personalized card number field to obtain the elimination conversion result; wherein, the elimination conversion is performed using the SPEL parsing expression processor;
[0049] The value of the elimination and conversion result is used as the transaction account or transaction card number of the transaction request.
[0050] Optionally, it also includes:
[0051] Send a restoration request to the transaction information server corresponding to the value of the anonymous account field or the anonymous card number field, and receive the restoration result returned by the transaction information server;
[0052] The value of the restoration result is used as the transaction account or transaction card number of the transaction request.
[0053] Optionally, the transaction request includes the terminal identifier of the old system terminal; and further includes:
[0054] Based on the terminal identifier of the old system terminal, the corresponding financial institution's hiding method is searched from the old system database, and the value of the anonymous account field or the anonymous card number field is restored to determine the restoration result; wherein, the restoration process is executed using the SPEL expression parsing processor.
[0055] The value of the restoration result is used as the transaction account or transaction card number of the transaction request.
[0056] Optionally, the real-time modification of the routing strategy for the transaction request includes:
[0057] The routing policy corresponding to the transaction request, stored in the hard disk or server database, is modified in real time, and the routing policy corresponding to the transaction request, stored in memory, is refreshed.
[0058] Optionally, the step of real-time modification of the routing policy corresponding to the transaction identifier stored in the hard disk or server database and refreshing the routing policy corresponding to the transaction identifier in memory includes:
[0059] Generate a routing policy modification request; wherein, the routing policy modification request includes modifying the mapping relationship;
[0060] The modified correspondence is substituted into the modification script corresponding to the development environment of the old system server and executed to update the routing strategy of the transaction identifier corresponding to the transaction request in the hard disk or the server database;
[0061] The updated routing strategy corresponding to the transaction identifier of the transaction request is obtained from the hard disk or the server database, and the memory is refreshed asynchronously.
[0062] Optionally, the routing strategy for obtaining the updated transaction identifier corresponding to the transaction request from the hard disk or the server database includes:
[0063] Based on the format of the routing policy in memory, determine the acquisition path of the updated routing policy for the transaction identifier corresponding to the transaction request; wherein the routing policy in the hard disk is in XML or JSON format, and the routing policy in the server database is a relational database table or a non-relational database table;
[0064] The updated routing strategy for the transaction identifier corresponding to the transaction request is obtained from the acquisition path.
[0065] Optionally, after forwarding the transaction request to the new system server, the method further includes:
[0066] Determine whether the waiting time for the request processing result exceeds a preset time threshold. If so, resend the transaction request to the new system server.
[0067] Increment the number of timeouts;
[0068] If the number of timeouts exceeds a preset timeout threshold, the routing strategy modifies the server address corresponding to the bank card number in the transaction request to the server URL of the old system server.
[0069] Optionally, it also includes:
[0070] The transaction requests corresponding to the number of timeouts are reversed.
[0071] Optionally, after receiving the request processing result returned by the new system server, the method further includes:
[0072] Determine whether the successfully processed request result matches the expected result.
[0073] If the request processing result does not meet the expected processing result, the transaction request is resent to the new system server;
[0074] The number of deviations in the request processing results that do not meet the expected processing results is counted, and the transaction requests exceeding a preset deviation threshold are processed using the old system server.
[0075] According to another aspect of the present invention, an apparatus for processing transaction requests during a switchover between old and new systems is provided. The apparatus is applied to an old system server and includes:
[0076] The receiving module is used to receive transaction requests sent by the old system terminal;
[0077] The routing module is used to find the routing strategy corresponding to the transaction request in memory according to the running stage of the new system server; wherein, the routing strategy includes a whitelist strategy;
[0078] The judgment module is used to forward the transaction request to the new system server when the transaction request conforms to the whitelist policy, and to receive the request processing result returned by the new system server.
[0079] The modification module is used to modify the routing strategy of the transaction request in real time when the exception code of the request processing result is the old system identifier, and process the transaction request according to the real-time modified routing strategy.
[0080] According to another aspect of the present invention, an electronic device for processing transaction requests during a system switchover is provided, comprising:
[0081] One or more processors;
[0082] Storage device for storing one or more programs.
[0083] When the one or more programs are executed by the one or more processors, the one or more processors implement the transaction request processing method for switching between old and new systems provided by the present invention.
[0084] According to another aspect of the present invention, a computer-readable medium is provided having a computer program stored thereon, which, when executed by a processor, implements the method for processing transaction requests during the switching process between old and new systems provided by the present invention.
[0085] One embodiment of the above invention has the following advantages or beneficial effects: Because it uses an old system server to receive transaction requests sent by old system terminals, and searches the memory for the routing policy corresponding to the transaction request based on the operating stage of the new system server, if the transaction request conforms to the whitelist policy, it forwards the transaction request to the new system server for processing; if the new system server's request processing result is a failure, the routing policy is modified in real time, and the routing policy takes effect immediately, processing the transaction request according to the modified routing policy. Therefore, this overcomes the technical problems of poor stability of the new system, frequent failures leading to failed transaction requests during the switch between the old and new systems, and the inability to receive new transaction requests during old system downtime, which reduces transaction processing efficiency, causes long user waiting times, and results in a poor service experience. Thus, it achieves the technical effect of being able to modify the routing policies of the old and new systems in real time, realizing uninterrupted transaction processing during the switch between the old and new systems, ensuring real-time response to transaction requests and continuous and stable operation of online transactions, avoiding the impact of system switching on transaction services, and realizing transaction request processing without service interruption, greatly improving transaction processing efficiency and enhancing user satisfaction.
[0086] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description
[0087] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:
[0088] Figure 1 This is a schematic diagram of the main flow of the transaction request processing method during the switching process between old and new systems according to an embodiment of the present invention;
[0089] Figure 2 This is a schematic diagram of the main flow of the method for determining the routing strategy according to an embodiment of the present invention;
[0090] Figure 3 This is a schematic diagram of the main process of the method for determining whether a transaction request conforms to the whitelist strategy according to an embodiment of the present invention;
[0091] Figure 4 This is a schematic diagram illustrating the main flow of a method for determining a transaction account based on an account identifier field according to an embodiment of the present invention;
[0092] Figure 5 This is a schematic diagram of the main process of a method for determining a transaction card number based on a card number identifier field according to an embodiment of the present invention;
[0093] Figure 6 This is a schematic diagram of the main flow of the timeout handling method for request processing results according to an embodiment of the present invention;
[0094] Figure 7 This is a schematic diagram illustrating the main flow of different response methods for request processing results according to embodiments of the present invention;
[0095] Figure 8 This is a schematic diagram of the main flow of the method for modifying routing policies according to an embodiment of the present invention;
[0096] Figure 9(a) is a schematic diagram of the main modules of the transaction request processing device during the switching process between old and new systems according to an embodiment of the present invention;
[0097] Figure 9(b) is a schematic diagram illustrating the application of the modified routing policy according to an embodiment of the present invention;
[0098] Figure 10 An exemplary system architecture diagram is shown, illustrating a method or apparatus for processing transaction requests during the switching process between old and new systems, suitable for application in embodiments of the present invention.
[0099] Figure 11 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers of the present invention. Detailed Implementation
[0100] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.
[0101] Transaction account: refers to the account opened by a financial institution for a user to handle fund receipt and payment settlement. It is for internal use by the financial institution and will not change with changes in other user information (such as transaction card number, contact information, address, etc.). Depending on the user type, it includes corporate accounts and personal accounts.
[0102] Transaction card number: refers to the serial number on a credit payment instrument issued by an approved financial institution to a user, which has all or some of the functions of consumer credit, transfer settlement, cash deposit and withdrawal.
[0103] URL: Uniform Resource Locator, refers to the identifier used to specify the location of information on the World Wide Web service of the Internet.
[0104] SpEL: Spring Expression Language, is an expression language that supports runtime querying and manipulation of object graphs, and supports the processing of various regular expressions such as basic expressions, class-related expressions, and collection-related expressions.
[0105] Reversal: This is a remedial measure taken by online transaction systems for failed transactions. When the server is unresponsive for an extended period, and it is impossible to determine whether the transaction has been completed, a cancellation request is resent to ensure data consistency. This causes the server to either roll back the transaction or not process it at all.
[0106] During the existing system switchover process, the new system may run normally in the early testing and verification phases, but various transaction failures occur after the official launch. The existing system failure handling requires the old system to be shut down, the switchover granularity is too large, and it cannot guarantee real-time response to transaction requests, resulting in a waste of various resource costs.
[0107] The transaction request processing method during the system switchover process of this invention modifies the transaction request routing strategy in real time when a new system failure occurs, switching to the old system server for execution. This ensures the uninterrupted and continuous operation of online transaction services and avoids the impact of system switchover on transaction business.
[0108] Figure 1 This is a schematic diagram of the main flow of the transaction request processing method during the switching process between old and new systems according to an embodiment of the present invention, as shown below. Figure 1 As shown, the method for processing transaction requests during the switching process between old and new systems according to the present invention includes the following steps:
[0109] In this embodiment of the invention, the method for processing transaction requests during the switching process between the old and new systems is executed through the old system server.
[0110] Step S101: Receive transaction requests sent by the old system terminal.
[0111] In this embodiment of the invention, the legacy system server receives a transaction request sent by a legacy system terminal. The transaction request includes a request message, which includes an account identifier field and a card number identifier field.
[0112] Furthermore, since different financial institutions have different messaging habits, the account identifier field can be a standard account field, a personalized account field, or a hidden account field; the card number identifier field can be a standard card number field, a personalized card number field, or a hidden card number field.
[0113] Specifically:
[0114] The standard account field or standard card number field is the transaction account or transaction card number. For example, the transaction account is 123456000789654 and the transaction card number is 00000000000006.
[0115] The personalized account field / personalized card number field can be processing identifier + transaction account / transaction card number + verification code; where the processing identifier represents the user's login channel identifier (e.g., MBS for mobile banking, ATM for ATM terminal, EBS for online banking, etc.), and the verification code is a randomly generated multi-digit numeric character, where the numeric character can be any one of 0-9. For example, if the user's login channel is EBS, the verification code is a 4-digit random numeric character 0564. Accordingly, the personalized account field is EBS1234560007896540564, and the personalized card number field is EBS000000000000060564.
[0116] The anonymous account field is the anonymous account after the financial institution has hidden the transaction account / transaction card number. Different financial institutions may adopt different hiding methods. For example, the hiding method is that the financial institution calculates the anonymous account for each bank card number according to the anonymous relationship formula for all users of the institution's services, and stores the correspondence between the bank card number and the anonymous account.
[0117] Furthermore, the anonymous relation can be a series of numerical sequences involving different digits of the transaction account / transaction card number. For example, if the transaction account is 15 digits long, the anonymous relation could include: ① swapping the 2nd and 8th digits to obtain the first value; ② swapping the 5th and 1st digits of the first value to obtain the second value; ③ swapping the 9th and 14th digits of the second value to obtain the anonymous account number. Accordingly, the anonymous account number obtained after processing the transaction account number 123456000789654 using the anonymous relation is 503416025789604.
[0118] Step S102: Based on the operating stage of the new system server, search for the routing policy in memory corresponding to the transaction request; wherein, the routing policy includes a whitelist policy.
[0119] In this embodiment of the invention, the old system server searches for a pre-set routing strategy in memory based on the operating stage of the new system server to determine the processing server for the transaction request; wherein the processing server is either the old system server or the new system server, and the routing strategy can be in the form of a data table.
[0120] Furthermore, when the old system server starts up, it automatically loads the routing policy from the hard drive or the server database into the server memory. In the subsequent processing of transaction requests, the old system server only needs to read the routing policy in the server memory to process and judge the transaction request. This achieves high-speed caching of the routing policy through the server memory, avoiding the performance problems caused by frequent hard drive read and write.
[0121] In this embodiment of the invention, the routing strategy includes a new system strategy, a whitelist strategy, and an old system strategy. Based on the routing strategy, the server address of the transaction request can be determined. The server address can be the server address of the new system server or the server address of the old system server. The server address is in URL form, such as http: / / www.ljjyxjqh.com.
[0122] In this embodiment of the invention, the server address of the new system policy is the server address of the new system server. The server address of the old system policy is the server address of the old system server. The whitelist policy includes an account whitelist, a second-level row whitelist, and a first-level row whitelist, and the server address of the whitelist policy is the server address of the new system server.
[0123] In this embodiment of the invention, the account whitelist includes one or more transaction accounts under one or more business outlets, the secondary bank whitelist includes the secondary bank numbers of one or more secondary banks, and the primary bank whitelist includes the primary bank numbers under one or more primary banks. For example, business outlets are the various business offices or branches of financial institutions, primary banks are the primary branches of various provincial-level administrative regions, and secondary banks are the secondary branches of various prefecture-level administrative regions.
[0124] In this embodiment of the invention, the routing strategy for transaction requests changes with the operational stability of each business function of the new system server. That is, the routing strategy for transaction requests is determined according to the operational stage of the new system server. The business function corresponds to the request type of the transaction request. For example, the business function can be transfer, foreign exchange, loan repayment, pledge, etc., and the transaction request can be transfer request, foreign exchange request, loan repayment request, pledge request, etc.
[0125] In embodiments of the present invention, such as Figure 2 As shown, the method for determining the routing strategy of the present invention includes the following steps:
[0126] Step S201: During the trial period of branch accounts, select one or more target transaction accounts from one or more branches to be tried that cover all business functions of the business branches, and add the target transaction accounts to the account whitelist.
[0127] In this embodiment of the invention, the new system server needs to go through multiple trial phases before it can be stably launched. The new system server is rolled out gradually, going through multiple phases such as the branch account trial phase, the secondary bank trial phase, and the primary bank trial phase before it is officially launched. This prevents the unstable new system server from frequently failing, causing business to stagnate and excessively wasting the switching costs of financial institutions.
[0128] In this embodiment of the invention, transaction requests that conform to the account whitelist are processed by the new system server, while transaction requests that do not conform to the account whitelist are processed by the old system server. Therefore, after the target transaction account is added to the account whitelist, when the old system server processes the transaction request of the target transaction account, it directly forwards the transaction request of the target transaction account to the new system server for processing; if it is a transaction request of a non-target transaction account, it can be processed directly by the old system server.
[0129] Furthermore, during the trial phase of branch accounts, the routing strategy corresponding to transaction requests is the account whitelist.
[0130] Step S202: After the trial period of the branch account ends, determine whether the processing result of the transaction request of each target transaction account is successful. If yes, proceed to step S203; otherwise, proceed to step S208.
[0131] Step S203: Enter the trial phase of the secondary bank, select one or more target secondary bank numbers that cover all business functions of the secondary bank from one or more secondary banks to be tested, and add the target secondary bank numbers to the secondary bank whitelist.
[0132] In this embodiment of the invention, if the processing result of all transaction requests of the target transaction accounts during the trial phase of the branch account is successful, it indicates that the trial result of the branch account trial phase is successful, and the new system server can enter the secondary trial phase.
[0133] In this embodiment of the invention, transaction requests that conform to the secondary bank whitelist are processed by the new system server, while transaction requests that do not conform to the secondary bank whitelist are processed by the old system server. Therefore, after the target secondary bank number is added to the secondary bank whitelist, when the old system server processes a transaction request for the target secondary bank number, it directly forwards the transaction request for the target secondary bank number to the new system server for processing; if it is a transaction request for a non-target secondary bank number, the old system server can process it directly.
[0134] Furthermore, during the trial phase of the secondary bank, the routing strategy corresponding to the transaction request is the secondary bank whitelist.
[0135] Step S204: After the trial period of the secondary bank is completed, determine whether the processing result of the transaction request of each target secondary bank number is successful. If yes, proceed to step S205; otherwise, proceed to step S208.
[0136] Step S205: Enter the trial phase of the primary bank, select one or more target primary bank numbers that cover all business functions of the primary bank from one or more primary banks to be tested, and add the target primary bank numbers to the primary bank whitelist.
[0137] In this embodiment of the invention, if the processing result of all transaction requests for the target secondary bank number in the secondary bank trial phase is successful, it indicates that the trial result of the secondary bank trial phase is successful, and the new system server can enter the primary bank trial phase.
[0138] In this embodiment of the invention, transaction requests that conform to the first-level row whitelist are processed by the new system server, while transaction requests that do not conform to the first-level row whitelist are processed by the old system server. Therefore, after the target first-level row number is added to the first-level row whitelist, when the old system server processes a transaction request for the target first-level row number, it directly forwards the transaction request for the target first-level row number to the new system server for processing; if it is a transaction request for a non-target first-level row number, the old system server can process it directly.
[0139] Furthermore, during the trial phase of the first-level bank, the routing strategy corresponding to the transaction request is the first-level bank whitelist.
[0140] Step S206: After the trial period of the first-level bank is completed, determine whether the processing result of the transaction request of each target first-level bank number is successful. If yes, proceed to step S207; otherwise, proceed to step S208.
[0141] Step S207: Add the accounts at all levels of the financial institution to the new system strategy.
[0142] In this embodiment of the invention, if the processing result of all transaction requests for the target first-level bank number during the trial phase of the first-level bank is successful, it indicates that the trial result of the trial phase of the first-level bank is successful, the new system server can be officially launched, and the transaction requests of any account of the financial institution will be processed by the new system server. That is, the processing strategy for any transaction request of the financial institution is the new system strategy.
[0143] Furthermore, during the official launch phase, the routing strategy corresponding to the transaction request becomes the new system strategy.
[0144] In this embodiment of the invention, the time for each running stage can be selectively set as needed.
[0145] Step S208: Send a fault request to the developers.
[0146] In this embodiment of the invention, if the processing result of a transaction request fails during any trial phase, a fault request is sent to the developers, enabling them to correct the business functions corresponding to the new system server based on the fault feedback, so that the trial can continue and the new system server can be launched stably.
[0147] In this embodiment of the invention, the routing strategy determination method of the present invention, during the account trial phase, select a portion of users from various business outlets, obtain their consent, and construct an account whitelist based on the target transaction accounts of the users who consent to the trial. Transaction requests from the account whitelist are forwarded to the new system server for processing. If the new system server processes all requests normally during the branch trial phase, the system enters the secondary bank trial phase. Select a portion of secondary banks, construct a secondary bank whitelist based on the selected target secondary bank numbers, and forward transaction requests from the secondary bank whitelist to the new system server for processing. If the new system server processes all requests normally during the secondary bank trial phase, the system enters the primary bank trial phase. Select a portion of primary banks, construct a primary bank whitelist based on the selected target primary bank numbers, and forward transaction requests from the primary bank whitelist to the new system server for processing. If the new system server processes all requests normally during the primary bank trial phase, it indicates that the new system server can operate stably. Financial institutions are then added to the new system strategy. This allows for the construction of different routing strategies for different trial phases, which can greatly improve the stability of the new system launch, ensure real-time response to transaction requests during the trial phase, improve transaction processing efficiency during the trial phase, and enhance user satisfaction.
[0148] Step S103: If the transaction request conforms to the whitelist policy, forward the transaction request to the new system server and receive the request processing result returned by the new system server.
[0149] In this embodiment of the invention, all transaction requests that meet the account whitelist during the account trial phase, the secondary bank whitelist during the secondary bank trial phase, the primary bank whitelist during the primary bank trial phase, and the formal launch phase are processed by the new system server. Therefore, after receiving a transaction request, the old system server forwards the transaction request to the new system server and receives the request processing result returned by the new system server.
[0150] In embodiments of the present invention, such as Figure 3 As shown, the method for determining whether a transaction request conforms to the whitelist strategy in this invention includes the following steps:
[0151] Step S301: Obtain the account identifier field and / or card number identifier field of the request message of the transaction request.
[0152] Step S302: Determine that the transaction request conforms to the whitelist policy by using the values of the account identifier field and / or card number identifier field.
[0153] In this embodiment of the invention, when the request message of a transaction request only includes the value of the account identifier field, the value of the account identifier field is used to determine whether the transaction request complies with the whitelist policy; when the request message of a transaction request only includes the value of the card number identifier field, the value of the card number identifier field is used to determine whether the transaction request complies with the whitelist policy; when the request message of a transaction request includes the values of both the account identifier field and the card number identifier field, the value of the account identifier field is used to determine whether the transaction request complies with the whitelist policy.
[0154] Step S3021: Determine that the transaction request conforms to the whitelist policy based on the value of the account identifier field.
[0155] Step S30211: If the request message of the transaction request includes an account identifier field, determine the transaction account of the transaction request based on the value of the account identifier field.
[0156] In embodiments of the present invention, such as Figure 4 As shown, the method for determining a transaction account based on an account identifier field according to the present invention includes the following steps:
[0157] Step S401: Obtain the request message of the transaction request.
[0158] Step S402: Determine whether the request message includes a standard account field. If yes, proceed to step S403; otherwise, proceed to step S404.
[0159] In this embodiment of the invention, the legacy system server determines whether the account identifier field of the request message is a standard account field. Step S403: The value of the standard account field is used as the transaction account of the transaction request.
[0160] Step S404: Determine whether the request message includes a personalized account field. If yes, proceed to step S405; otherwise, proceed to step S406.
[0161] In this embodiment of the invention, when the account identifier field of the request message is not a standard account field, the old system server determines whether the account identifier field of the request message is a personalized account field.
[0162] Step S405: Perform a removal and transformation on the value of the personalized account field, determine the removal and transformation result, and use the value of the removal and transformation result as the transaction account of the transaction request.
[0163] In this embodiment of the invention, the old system server performs a removal and transformation on the value of the personalized account field according to the generation rules of the personalized account field. As described in step S101, the personalized account field consists of a processing identifier, a transaction account, and a verification code. The processing identifier is a 3-digit login channel identifier for the user, and the verification code is a randomly generated 4-digit numeric character. Accordingly, the removal and transformation method is to delete the first 3 digits and the last 4 digits of the personalized account field value. Therefore, when the value of the personalized account field is determined to be EBS1234560007896540564, the old system server deletes the first 5 digits "EBS" and the last 4 digits "0564" to obtain the removal and transformation result, that is, the transaction account 123456000789654 corresponding to the request message.
[0164] Furthermore, the elimination transformation can be performed using the SPEL parsing expression processor on the legacy system server.
[0165] Alternatively, the truncation conversion can also be called the truncation conversion. Accordingly, the old system server truncates the value of the personalized account field according to the generation rules of the personalized account field. As described in step S101, the personalized account field consists of a processing identifier, a bank card number, and a verification code. The processing identifier is a 3-digit login channel identifier for the user, and the verification code is a randomly generated 4-digit numeric character. Accordingly, the truncation conversion method involves truncating 6-20 digits of the personalized account field value. Therefore, when the value of the personalized account field is determined to be EBS1234560007896540564, the old system server truncates 4-18 digits to obtain the truncation conversion result, which is the transaction account 123456000789654 corresponding to the request message.
[0166] Step S406: Based on the anonymous account field of the request message, send a restoration request corresponding to the value of the anonymous account field to the transaction information server, receive the restoration result returned by the transaction information server, and use the value of the restoration result as the transaction account of the transaction request.
[0167] In this embodiment of the invention, since different financial institutions may have different methods for hiding transaction accounts, the old system server needs to send a restoration request corresponding to the value of the anonymous account field to the transaction information server, so that the transaction information server can restore the transaction account corresponding to the anonymous account field according to the hiding method of each financial institution and return the restoration result corresponding to the transaction account to the old system server.
[0168] In this embodiment of the invention, alternatively, the old system server can store the hidden processing methods of various financial institutions. Upon receiving a transaction request, the old system server searches for the corresponding hidden processing method of the financial institution based on the terminal identifier corresponding to the old system terminal, in order to restore the value of the anonymous account field. For example, if the value of the anonymous account field in the received request message is 503416025789604, according to the hidden processing method described in step S101, the old system server performs reverse restoration based on the anonymous relation formula, including: ④ swapping the 9th and 14th bits to obtain the third value; ⑤ swapping the 5th and 1st bits of the third value to obtain the fourth value; ⑥ swapping the 2nd and 8th bits of the fourth value to obtain the transaction account corresponding to the restored result as: 123456000789654.
[0169] Furthermore, the restoration process can be performed using the SPEL parsing expression processor of the legacy system server.
[0170] Step S407: Store the value of the anonymous account field and the restoration result in the routing policy.
[0171] In this embodiment of the invention, the old system server stores the correspondence between the value of the anonymous account field and the corresponding transaction account in the old system database, thereby localizing the correspondence between the value of the anonymous account field and the corresponding transaction account. When the same anonymous account field value is received subsequently, there is no need to send a restoration request to a third-party transaction information server or perform restoration processing on the value of the anonymous account field. The value can be retrieved directly from the local database, which greatly improves the processing speed and system performance of the system server and enhances user satisfaction.
[0172] In this embodiment of the invention, the method for determining the transaction account based on the account identifier field of the present invention performs various processing such as elimination, transformation, and restoration on the values of different fields such as the standard account field, personalized account field, or anonymous account field of the transaction request message. This enables unified switching of transaction requests from financial institutions with different message habits, greatly improving the processing efficiency of transaction requests during the switching process between old and new systems. Compared with the existing request processing that can only verify the standard account field, this greatly expands the processing scenarios of transaction requests, improves the processing efficiency of online transactions, and enhances user satisfaction.
[0173] In step S30212, during the trial phase of the branch account, the whitelist policy is determined to be an account whitelist, and the process proceeds to step S30213; during the trial phase of the secondary bank, the whitelist policy is determined to be a secondary bank whitelist, and the process proceeds to step S30215; during the trial phase of the primary bank, the whitelist policy is determined to be a primary bank whitelist, and the process proceeds to step S30217.
[0174] Step S30213: Compare the transaction account of the transaction request with the account whitelist to determine whether the transaction account of the transaction request belongs to the account whitelist. If yes, proceed to step S30214; otherwise, proceed to step S30219.
[0175] Step S30214: Determine that the transaction account of the transaction request conforms to the whitelist policy.
[0176] In this embodiment of the invention, if the transaction account of the transaction request belongs to the account whitelist, or the second-level row number corresponding to the transaction account of the transaction request belongs to the second-level row whitelist, or the first-level row number corresponding to the transaction account of the transaction request belongs to the first-level row whitelist, the transaction request is determined to comply with the whitelist policy.
[0177] Step S30215: Send a secondary row matching request, including the transaction account of the transaction request, to the transaction information server, and receive the secondary row number corresponding to the transaction account of the transaction request returned by the transaction information server.
[0178] In this embodiment of the invention, a secondary bank matching request is sent to the transaction information server. The secondary bank matching request includes the transaction account of the transaction request and is used to request the secondary bank number corresponding to the transaction account of the transaction request. The transaction information server provides a distributed service, communicates with various financial institutions, and can obtain the secondary bank numbers corresponding to the transaction accounts of each financial institution.
[0179] Step S30216: Compare the secondary row number corresponding to the transaction account of the transaction request with the secondary row whitelist to determine whether the secondary row number corresponding to the transaction account of the transaction request belongs to the secondary row whitelist. If yes, proceed to step S30214; otherwise, proceed to step S30219.
[0180] Step S30217: Send a first-level row matching request, including the transaction account of the transaction request, to the transaction information server, and receive the first-level row number corresponding to the transaction account of the transaction request returned by the transaction information server.
[0181] In this embodiment of the invention, a first-level bank matching request is sent to the transaction information server. The first-level bank matching request includes the transaction account of the transaction request and is used to request the first-level bank number corresponding to the transaction account of the transaction request. The transaction information server communicates with various financial institutions and can obtain the first-level bank numbers corresponding to the transaction accounts of each financial institution.
[0182] Step S30218: Compare the first-level bank number corresponding to the transaction account of the transaction request with the first-level bank whitelist to determine whether the first-level bank number corresponding to the transaction account of the transaction request belongs to the first-level bank whitelist. If yes, proceed to step S30214; if no, proceed to step S30219.
[0183] Step S30219: Determine that the transaction request does not conform to the whitelist policy.
[0184] In this embodiment of the invention, if a transaction request does not conform to the whitelist policy, the old system server directly processes the transaction request.
[0185] Step S3022, determining that the transaction request conforms to the whitelist policy based on the value of the card number identifier field, includes:
[0186] Step S30221: If the request message of the transaction request includes a card number identifier field, determine the transaction card number of the transaction request based on the value of the card number identifier field.
[0187] In embodiments of the present invention, such as Figure 5 As shown, the method for determining the transaction card number based on the card number identifier field of the present invention includes the following steps:
[0188] Step S501: Obtain the request message of the transaction request.
[0189] Step S502: Determine whether the request message includes a standard card number field. If yes, proceed to step S503; otherwise, proceed to step S504.
[0190] In this embodiment of the invention, the old system server determines whether the card number identifier field of the request message is a standard card number field.
[0191] Step S503: Use the value of the standard card number field as the transaction card number of the transaction request.
[0192] Step S504: Determine whether the request message includes a personalized card number field. If yes, proceed to step S505; otherwise, proceed to step S506.
[0193] In this embodiment of the invention, when the card number identifier field of the request message is not a standard card number field, the old system server determines whether the card number identifier field of the request message is a personalized card number field.
[0194] Step S505: Perform a removal and conversion on the value of the personalized card number field, determine the removal and conversion result, and use the value of the removal and conversion result as the transaction card number of the transaction request.
[0195] In this embodiment of the invention, the removal and transformation of the value of the personalized card number field is the same as the removal and transformation of the value of the personalized account field, as detailed in step S405.
[0196] Step S506: Based on the anonymous card number field of the request message, send a restoration request corresponding to the value of the anonymous card number field to the transaction information server, receive the restoration result returned by the transaction information server, and use the value of the restoration result as the transaction card number of the transaction request.
[0197] In this embodiment of the invention, the restoration process of the value of the anonymous card number field is the same as the restoration process of the value of the anonymous account field, as detailed in step S406.
[0198] Step S507: Store the value of the anonymous card number field and the restoration result in the routing policy.
[0199] In this embodiment of the invention, the method for determining the transaction card number based on the card number identifier field of the invention performs various processing such as elimination, conversion, and restoration on the values of different fields such as the standard card number field, personalized card number field, or anonymous card number field in the request message of the transaction request. This enables unified switching of transaction requests from financial institutions with different message habits, greatly improving the processing efficiency of transaction requests during the switching process between old and new systems. Compared with the existing request processing that can only verify the standard card number field, this greatly expands the processing scenarios of transaction requests, improves the processing efficiency of online transactions, and enhances user satisfaction.
[0200] Step S30222: During the trial period of the branch account, the whitelist policy is determined to be an account whitelist, and proceed to step S30223; During the trial period of the secondary bank, the whitelist policy is determined to be a secondary bank whitelist, and proceed to step S30226; During the trial period of the primary bank, the whitelist policy is determined to be a primary bank whitelist, and proceed to step S30228.
[0201] Step S30223: Send an account matching request including the transaction card number of the transaction request to the transaction information server, and receive the transaction account corresponding to the transaction card number of the transaction request returned by the transaction information server.
[0202] Step S30224: Compare the transaction account of the transaction request with the account whitelist to determine whether the transaction account of the transaction request belongs to the account whitelist. If yes, proceed to step S30225; otherwise, proceed to step S302291.
[0203] Step S30225: Determine that the transaction request conforms to the whitelist policy.
[0204] In this embodiment of the invention, if the transaction account of the transaction request belongs to the account whitelist, or the secondary bank number corresponding to the transaction card number of the transaction request belongs to the secondary bank whitelist, or the primary bank number corresponding to the transaction card number of the transaction request belongs to the primary bank whitelist, the transaction request is determined to comply with the whitelist policy.
[0205] Step S30226: Send a secondary row matching request including the transaction card number of the transaction request to the transaction information server, and receive the secondary row number corresponding to the transaction card number of the transaction request returned by the transaction information server.
[0206] Step S30227: Compare the secondary bank number corresponding to the transaction card number of the transaction request with the secondary bank whitelist to determine whether the secondary bank number corresponding to the transaction card number of the transaction request belongs to the secondary bank whitelist. If yes, proceed to step S30225; if no, proceed to step S302291.
[0207] Step S30228: Send a first-level row matching request, including the transaction card number of the transaction request, to the transaction information server, and receive the first-level row number corresponding to the transaction card number of the transaction request returned by the transaction information server.
[0208] Step S30229: Compare the first-level bank number corresponding to the transaction card number of the transaction request with the first-level bank whitelist to determine whether the first-level bank number corresponding to the transaction card number of the transaction request belongs to the first-level bank whitelist. If yes, proceed to step S30225; if no, proceed to step S302291.
[0209] Step S302291: Determine that the transaction request does not conform to the whitelist policy.
[0210] In this embodiment of the invention, if a transaction request does not conform to the whitelist policy, the old system server directly processes the transaction request.
[0211] In this embodiment of the invention, the method for determining whether a transaction request conforms to the whitelist policy is used to search and compare based on the transaction account or transaction card number to determine whether the transaction request conforms to the whitelist policy. This allows for efficient processing of transaction requests at various trial stages, which can greatly improve the processing efficiency of online transactions and enhance user satisfaction.
[0212] In this embodiment of the invention, if the routing strategy for a transaction request is a whitelist strategy and the verification result of verifying the transaction account of the transaction request using the whitelist strategy is a verification failure, the transaction request is processed by the old system server.
[0213] In this embodiment of the invention, when a transaction request conforms to the whitelist policy or the new system policy, the old system server forwards the transaction request to the new system server, which then processes the transaction request. The old system server waits for the new system server to return the request processing result and keeps track of the waiting time to prevent the transaction request from being interrupted due to the new system server not responding for a long time. This ensures that the old system server can respond to the transaction request in a timely manner and guarantee user service.
[0214] In embodiments of the present invention, such as Figure 6 As shown, the timeout handling method for request processing results of the present invention includes the following steps:
[0215] Step S601: Calculate the waiting time for the request processing result.
[0216] In this embodiment of the invention, after the old system server forwards the transaction request to the new system server, it begins to calculate the waiting time for the new system server to return the request processing result.
[0217] Step S602: Determine whether the waiting time for the request processing result exceeds a preset time threshold. If yes, proceed to step S603; otherwise, proceed to step S601.
[0218] In this embodiment of the invention, the old system server determines whether the waiting time for the request processing result exceeds a preset time threshold, for example, the preset time threshold is 1 minute.
[0219] It should be noted that the preset time threshold can be selectively set based on the actual transaction situation in production. Furthermore, since different types of business have different levels of complexity, different types of transaction requests can correspond to different preset time thresholds.
[0220] Furthermore, the old system server searches the old system database based on the business type of the transaction request to determine the preset time threshold corresponding to the business type of the transaction request.
[0221] Step S603: Resend the transaction request to the new system server.
[0222] In this embodiment of the invention, when the old system server determines that the new system server has not returned a request processing result after waiting for a period of time exceeding a preset time threshold, the old system server resends the transaction request to the new system server.
[0223] Step S604: Increment the number of timeouts.
[0224] In this embodiment of the invention, after the old system server resends the transaction request to the new system server, the timeout count of the new system server's response is automatically incremented. For example, every time the new system server times out, the timeout count of the old system server is automatically incremented by 1.
[0225] Step S605: Determine whether the number of timeouts exceeds a preset timeout threshold. If yes, proceed to step S606; otherwise, proceed to step S603.
[0226] In this embodiment of the invention, the old system server determines whether the number of timeouts of the new system server exceeds a preset timeout threshold, for example, the preset timeout threshold is 5 times.
[0227] It should be noted that the preset timeout threshold can be selectively set according to the actual transaction situation in production.
[0228] Step S606: Modify the server address corresponding to the transaction request in the routing policy.
[0229] In this embodiment of the invention, when it is determined that the number of timeouts in the new system server's response to a transaction request exceeds a preset timeout threshold, the old system server modifies the server address corresponding to the bank card number in the transaction request to the server URL of the old system server in the routing strategy, and the old system server processes the transaction request. In this way, the continuous and uninterrupted processing of transaction requests can be achieved, preventing transaction interruptions caused by the failure of the new system server, which could lead to poor user experience such as long waiting times and potential complaints.
[0230] In this embodiment of the invention, after the old system server modifies the routing policy and the new system server receives the modification notification, if the processing of the transaction request involves multiple data interactions between the new system server and the old system server, the new system server needs to synchronize the incremental business data related to the transaction request to the old system server.
[0231] Step S607: Perform a reversal process on the transaction request corresponding to the number of timeouts.
[0232] In this embodiment of the invention, the reversal process refers to the situation where, in the event of a timeout response from the new system server, the old system server is unsure whether the new system server has completed processing the transaction request. Therefore, in order to protect user interests and ensure data consistency between the new and old system servers, the old system server sends a transaction cancellation request to the new system server. Upon receiving the transaction cancellation request, if the new system server has already processed the request, it rolls back the system data to the state before the transaction request was processed; otherwise, it does not process the transaction request and returns the unprocessed result to the old system server.
[0233] In this embodiment of the invention, the order of steps S606 and S607 can be reversed. That is, the old system server first reverses the transaction requests that the new system server responded to in a timeout, and then modifies the routing strategy.
[0234] In this embodiment of the invention, the timeout handling method for request processing results of the present invention is used to determine the response time of the new system server in processing transaction requests. If the waiting time exceeds the preset time threshold multiple times, the routing strategy is modified to change the transaction request to be processed by the old system server, so as to ensure the uninterrupted operation of the online transaction service and improve the satisfaction of transaction processing.
[0235] In this embodiment of the invention, when the old system server receives the request processing result of the transaction request returned by the new system server, since the request processing result may be successful and the result meets expectations, successful but the result does not meet expectations, or the processing fails, the old system server needs to make different responses according to different result situations.
[0236] In embodiments of the present invention, such as Figure 7 As shown, different methods for handling request processing results according to the present invention include the following steps:
[0237] Step S701: Receive the request processing result returned by the new system server.
[0238] Step S702: Determine whether the request processing result is a processing failure. If yes, proceed to step S703; otherwise, proceed to step S704.
[0239] In this embodiment of the invention, when the request processing result is a processing failure, the request processing result includes an exception code, which is an old system identifier. That is, the new system server determines that it cannot process the transaction request and the old system server can process it, so it returns a processing failure request processing result, and the exception code of the request processing result is an old system identifier, so that the transaction request can be modified to be processed by the old system server.
[0240] Step S703: Determine whether the exception code of the request processing result is an old system identifier. If yes, proceed to step S104; otherwise, proceed to step S710.
[0241] Step S704: Determine whether the request processing result meets the expected processing result. If yes, proceed to step S709; if no, proceed to step S705.
[0242] In this embodiment of the invention, the old system server stores the expected processing results of various transaction requests. Therefore, after receiving the processing result of a successfully processed request, the old system server compares the processing result of the request with the expected processing result to determine whether the processing result of the new system server meets the expectations.
[0243] Step S705: Resend the transaction request to the new system server.
[0244] In this embodiment of the invention, if the old system server determines that the request processing result of the new system server does not meet expectations, it indicates that there is a deviation between the request processing result of the new system server and the expected processing result. The old system server needs to resend the transaction request to the new system server in order to obtain a request processing result that meets the requirements.
[0245] Step S706: Increment the number of deviations.
[0246] In this embodiment of the invention, after the old system server resends the transaction request to the new system server, the deviation count of the new system server's request processing result is automatically incremented. For example, every time the new system server's request processing result does not meet the expected processing result, the deviation count of the old system server is automatically incremented by 1.
[0247] Step S707: Determine whether the number of deviations exceeds a preset deviation number threshold. If yes, proceed to step S708; otherwise, proceed to step S705.
[0248] In this embodiment of the invention, the old system server determines whether the number of deviations of the new system server exceeds a preset deviation threshold, for example, the preset deviation threshold is 5 times.
[0249] It should be noted that the preset deviation threshold can be selectively set according to the actual transaction situation in production.
[0250] Step S708: Modify the server address corresponding to the transaction request in the routing policy.
[0251] In this embodiment of the invention, if the number of deviations in the request processing result of the new system server exceeds a preset deviation threshold, the old system server modifies the server address corresponding to the bank card number of the transaction request to the server URL of the old system server in the routing strategy, and the old system server processes the transaction request.
[0252] Step S709: Return the request processing result to the old server terminal.
[0253] Step S710: Reject the transaction request.
[0254] In this embodiment of the invention, if the exception code of the request processing result is not the old system identifier, it indicates that there is an abnormal situation in the transaction request, and the old system server rejects the transaction request and reports it.
[0255] In this embodiment of the invention, different response methods for request processing results are used to deal with different types of request processing results returned by the new system server. In this way, if the request processing result meets expectations, the old system terminal is responded to; if it does not meet expectations or the exception code is identified as an old system identifier, the old system server is modified to execute the request. This achieves uninterrupted service during the switching process between the new and old systems, ensures the stability of online transactions, and improves user satisfaction.
[0256] Step S104: If the exception code of the request processing result is the old system identifier, modify the routing strategy of the transaction request in real time, and process the transaction request according to the real-time modified routing strategy.
[0257] In this embodiment of the invention, the routing policy is pre-registered on the hard disk or server database of the old system server. After the routing policy corresponding to the transaction identifier of the transaction request stored in the hard disk or server database is modified in real time, the distributed characteristics of the online transaction system are utilized to asynchronously refresh the routing policy corresponding to the transaction identifier of the transaction request in memory, so that the old system server executes the real-time modified routing policy, that is, the real-time modified routing policy takes effect in real time.
[0258] In this embodiment of the invention, if the exception code of the request processing result that failed to be processed by the new system server is determined to be the old system identifier, the old system server modifies the server address corresponding to the transaction request in the routing policy to the server URL of the old system server, thereby switching the transaction request to the old system server and ensuring the uninterrupted operation of the online transaction service.
[0259] It should be noted that the old system server is usually a server that has been running for many years and stably supports various transaction services, while the new system server is a server developed for the purpose of upgrading hardware equipment and software. Therefore, the old system server, as a backup server, must be able to support the processing of various transaction requests.
[0260] In embodiments of the present invention, such as Figure 8 As shown, the method for modifying the routing policy of the present invention includes the following steps:
[0261] Step S801: Generate a routing policy modification request; wherein, the routing policy modification request includes modifying the correspondence.
[0262] In this embodiment of the invention, when the number of timeouts in the new system server's response to transaction requests exceeds a preset timeout threshold, the request processing result is a processing failure with an exception code of the old system identifier, or the number of deviations in the new system server's request processing result exceeds a preset deviation threshold, the old system server generates a routing policy modification request to modify the system server processing the transaction requests. The modification of the mapping relationship includes the mapping between the transaction identifier corresponding to the transaction request and the server URL of the system server. The old system server modifies the server address of the transaction identifier corresponding to the transaction request in the routing policy to the server URL of the old system server.
[0263] Step S802: Substitute the modified correspondence into the modification script corresponding to the development environment of the old system server and execute it to update the routing strategy of the transaction identifier corresponding to the transaction request in the hard disk or the server database.
[0264] In this embodiment of the invention, the legacy system server stores modification scripts for modifying routing policies in the hard disk and server database under various development environments. By substituting the modification correspondence into the modification script and executing it, the routing policy can be modified to modify the corresponding server URL, including:
[0265] If a transaction request conforms to the whitelist policy and the exception code of the new system server's processing result for the transaction request is an old system identifier, since the transaction request corresponds to a business function, the abnormal processing result indicates that the business function of the new system server may be abnormal, rather than all business functions being abnormal. Therefore, the processing server for the abnormal transaction account, first-level line number, and second-level line number is changed to the old system server in real time. The old system server processes the transaction request in real time. Then, a fault request is sent to the developers to expedite the maintenance of the new system server. This ensures uninterrupted online transactions and timely correction of the new system server. During real-time modification, the transaction identifier corresponding to the transaction request is removed from the whitelist policy, and the transaction identifier corresponding to the transaction request is added to the old system policy, where the old system server corresponding to the old system policy processes the transaction request. Specifically:
[0266] Remove the trading account requesting the transaction from the account whitelist and add the trading account requesting the transaction to the old system policy in real time; or,
[0267] Remove the second-level line number corresponding to the transaction account or transaction card number in the transaction request from the second-level line whitelist, and add the second-level line number corresponding to the transaction account or transaction card number in the transaction request to the old system policy in real time; or,
[0268] Remove the first-level bank number corresponding to the transaction account or transaction card number of the transaction request from the first-level bank whitelist, and add the first-level bank number corresponding to the transaction account or transaction card number of the transaction request to the old system policy in real time.
[0269] In cases where a transaction request conforms to the whitelist policy and the number of timeouts in the new system server's response to the transaction request exceeds the preset timeout threshold, or where a transaction request conforms to the whitelist policy and the number of deviations in the new system server's request processing results exceeds the preset deviation threshold, the transaction identifier corresponding to the transaction request will be removed from the whitelist policy and added to the old system policy in real time.
[0270] In this embodiment of the invention, the development environment can be languages such as Java, Linux, and Python, and various forms such as Java's timed / asynchronous tasks, Linux's timed scripts, and Python scripts can be used to modify the routing strategies in the hard disk and server database.
[0271] Furthermore, the development environment supports manual script-triggered modifications to routing policies to ensure real-time effectiveness of these modifications.
[0272] Step S803: Obtain the updated routing policy corresponding to the transaction identifier of the transaction request from the hard disk or the server database, and asynchronously refresh the memory.
[0273] Step S8031: Determine the acquisition path of the updated routing policy corresponding to the transaction identifier of the transaction request according to the format of the routing policy in the memory; wherein, the routing policy in the hard disk is in XML or JSON format, and the routing policy in the server database is a relational database table or a non-relational database table.
[0274] In this embodiment of the invention, the old system server determines whether the routing policy acquisition path is the hard disk or the server database based on the format of the routing policy in memory. For example, the routing policy in JSON format includes the routing policy rteTp, and the value of the routing policy rteTp is the new system policy, the old system policy, the account whitelist, the second-level row whitelist, the first-level row whitelist, etc.; the account whitelist routeAccWhiteList includes the account accNo; the first-level row whitelist routeL1BankWhiteList includes the first-level row number lv1BrNo, the first-level row name lv1BrNm, etc. For example, the routing policy in the database table is the route configuration table `route_conf`. The route configuration table `route_conf` includes route types. Different route type values represent different routing policies. A route type value of 04 means all routes are routed to the new system, a route type value of 01 means all routes are routed to the old system, a route type value of 02 means the account whitelist rule is used, and a route type value of 03 means the first-level row whitelist rule is used. The account whitelist `route acc whitelist` includes the account `acc no` and the status `state` (a state of 0 means the account whitelist is disabled, and a state of 1 means the account whitelist is enabled). The first-level row whitelist `route_l1bank_whitelist` includes the first-level row number `lv1_br_no` and the status `state` (a state of 0 means the first-level row whitelist is disabled, and a state of 1 means the first-level row whitelist is enabled), etc.
[0275] Step S8032: Obtain the updated routing strategy for the transaction identifier corresponding to the transaction request from the acquisition path.
[0276] In this embodiment of the invention, the old system server obtains the updated routing policy from the hard disk or server database and refreshes the memory asynchronously.
[0277] In this embodiment of the invention, the routing strategy modification method of the present invention can modify routing strategies in different development environments and formats, ensuring real-time modification of routing strategies and timely and effective processing of transaction requests.
[0278] In this embodiment of the invention, by receiving a transaction request sent by an old system terminal; searching for a routing policy corresponding to the transaction request in memory according to the operating stage of the new system server; wherein the routing policy includes a whitelist policy; if the transaction request conforms to the whitelist policy, forwarding the transaction request to the new system server and receiving the request processing result returned by the new system server; if the exception code of the request processing result is an old system identifier, modifying the routing policy of the transaction request in real time, and processing the transaction request according to the real-time modified routing policy, the routing policies of the new and old systems can be modified in real time, realizing uninterrupted transaction processing during the switching between the new and old systems, ensuring real-time response to transaction requests and continuous and stable operation of online transactions, avoiding the impact of system switching on transaction services, realizing transaction request processing without service interruption, greatly improving transaction processing efficiency and enhancing user satisfaction.
[0279] Figure 9(a) is a schematic diagram of the main modules of the transaction request processing device during the switching process between old and new systems according to an embodiment of the present invention. As shown in Figure 9(a), the transaction request processing device 900 during the switching process between old and new systems of the present invention includes:
[0280] In this embodiment of the invention, the transaction request processing device 900 during the switching process between old and new systems is applied to the old system server.
[0281] The receiving module 901 is used to receive transaction requests sent by the old system terminal.
[0282] The routing module 902 is used to search for the routing policy corresponding to the transaction request in memory according to the operating stage of the new system server; wherein the routing policy includes a whitelist policy.
[0283] The judgment module 903 is used to forward the transaction request to the new system server when the transaction request conforms to the whitelist policy, and to receive the request processing result returned by the new system server.
[0284] Modification module 904 is used to modify the routing strategy of the transaction request in real time when the exception code of the request processing result is the old system identifier, and process the transaction request according to the real-time modified routing strategy.
[0285] In this embodiment of the invention, as shown in Figure 9(b), the modification module 904 can also be called the routing policy refresh layer, the server memory can also be called the routing policy acceleration layer, and the old system server also includes a route penetration processing rule engine selector. The interaction process among the three includes:
[0286] The routing policy refresh layer changes the routing policy in real time and notifies the route penetration processing rule engine selector.
[0287] The route penetration processing rule engine selector selects the route policy retrieval path according to the format of the route policy in the route policy acceleration layer, retrieves the updated route policy from the corresponding retrieval path, and sends it asynchronously to the route policy acceleration layer.
[0288] In this embodiment of the invention, the routing strategies of the new and old systems can be modified in real time through modules such as the receiving module, the routing module, and the modification module, so as to achieve uninterrupted transaction processing during the switching between the new and old systems, ensure the real-time response of transaction requests and the continuous and stable operation of online transactions, avoid the impact of system switching on transaction services, realize transaction request processing without service interruption, greatly improve transaction processing efficiency, and enhance user satisfaction.
[0289] Figure 10 An exemplary system architecture diagram is shown, illustrating a method or apparatus for processing transaction requests during a system transition suitable for application in embodiments of the present invention. Figure 10 As shown, the exemplary system architecture of the method or apparatus for processing transaction requests during the switching process between old and new systems according to embodiments of the present invention includes:
[0290] like Figure 10 As shown, the system architecture 1000 may include terminal devices 1001, 1002, and 1003, a network 1004, a legacy system server 1005, and a new system server 1006. The network 1004 serves as the medium for providing communication links between the terminal devices 1001, 1002, and 1003 and the legacy system server 1005, and between the legacy system server 1005 and the new system server 1006. The network 1004 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.
[0291] Users can use terminal devices 1001, 1002, and 1003 to interact with server 1005 via network 1004 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 1001, 1002, and 1003, such as transaction applications, shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc.
[0292] Terminal devices 1001, 1002, and 1003 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.
[0293] The old system server 1005 can be a server that provides various services, such as a backend management server that supports transaction websites browsed by users using terminal devices 1001, 1002, and 1003. The backend management server can analyze and process received transaction requests and other data, and feed back the processing results (e.g., the transaction request processing server is the new system server) to terminal devices 1001, 1002, and 1003, and forward the transaction requests to the new system server 1006.
[0294] It should be noted that the transaction request processing method provided in this embodiment of the invention during the switching process between the old and new systems is generally executed by the old system server 1005. Correspondingly, the transaction request processing device during the switching process between the old and new systems is generally located in the old system server 1005.
[0295] It should be understood that Figure 10 The number of terminal devices, networks, legacy system servers, and new system servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, legacy system servers, and new system servers can be included.
[0296] Figure 11 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers of the present invention, such as... Figure 11 As shown, the computer system 1100 of the terminal device or server in this embodiment of the invention includes:
[0297] The central processing unit (CPU) 1101 can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 1102 or programs loaded from storage section 1108 into random access memory (RAM) 1103. RAM 1103 also stores various programs and data required for the operation of system 1100. CPU 1101, ROM 1102, and RAM 1103 are interconnected via bus 1104. Input / output (I / O) interface 1105 is also connected to bus 1104.
[0298] The following components are connected to I / O interface 1105: an input section 1106 including a keyboard, mouse, etc.; an output section 1107 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1108 including a hard disk, etc.; and a communication section 1109 including a network interface card such as a LAN card, modem, etc. The communication section 1109 performs communication processing via a network such as the Internet. A drive 1110 is also connected to I / O interface 1105 as needed. Removable media 1111, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1110 as needed so that computer programs read from them can be installed into storage section 1108 as needed.
[0299] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1109, and / or installed from removable medium 1111. When the computer program is executed by central processing unit (CPU) 1101, it performs the functions defined above in the system of this invention.
[0300] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.
[0301] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0302] The modules described in the embodiments of the present invention can be implemented in software or hardware. The described modules can also be housed in a processor; for example, a processor may be described as including a receiving module, a routing module, a judging module, and a modifying module. The names of these modules do not necessarily limit the module itself; for example, a routing module may also be described as "a module that searches for the routing strategy corresponding to the transaction request in memory based on the operating stage of the new system server."
[0303] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs that, when executed by the device, cause the device to include: receiving a transaction request sent by an old system terminal; searching for a routing policy in memory corresponding to the transaction request based on the operating stage of the new system server; wherein the routing policy includes a whitelist policy; if the transaction request conforms to the whitelist policy, forwarding the transaction request to the new system server and receiving a request processing result returned by the new system server; and if the exception code of the request processing result is an old system identifier, modifying the routing policy of the transaction request in real time, and processing the transaction request according to the real-time modified routing policy.
[0304] According to the technical solution of the present invention, the routing rules of the new and old systems can be configured and expanded in real time and flexibly during the process of system upgrade and system switching (that is, the system to which the online transaction of the transaction request belongs changes), so as to realize the system switching processing of online transactions, improve the service availability during the switching and upgrade of the new and old systems, reduce the impact of the system upgrade and switching process on the business, and realize flexible system switching without interrupting the transaction service.
[0305] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.
Claims
1. A method for processing transaction requests during the switchover process between old and new systems, characterized in that, The method is applied to legacy system servers, and the method includes: Receive transaction requests sent by the old system terminal; Based on the operating stage of the new system server, the routing strategy corresponding to the transaction request is located in memory; wherein, the routing strategy includes a whitelist strategy; If the transaction request conforms to the whitelist policy, the transaction request is forwarded to the new system server, and the request processing result returned by the new system server is received. If the exception code of the request processing result is an old system identifier, the routing strategy of the transaction request is modified in real time, and the transaction request is processed according to the real-time modified routing strategy. The operation phases of the new system server include a branch account trial phase, a secondary bank trial phase, and a primary bank trial phase; the step of searching for the routing strategy corresponding to the transaction request in memory based on the operation phase of the new system server includes: During the trial period of the branch account, the routing strategy corresponding to the transaction request is an account whitelist; During the trial phase of the second-level row, the routing strategy corresponding to the transaction request is the second-level row whitelist; During the trial phase of the first-level bank, the routing strategy corresponding to the transaction request is the first-level bank whitelist.
2. The method according to claim 1, characterized in that, The routing strategy also includes the legacy system strategy. The real-time modification of the routing strategy for the transaction request, and processing the transaction request according to the real-time modified routing strategy, includes: The transaction identifier corresponding to the transaction request is removed from the whitelist policy, and the transaction identifier corresponding to the transaction request is added to the old system policy, so that the old system server corresponding to the old system policy can process the transaction request.
3. The method according to claim 2, characterized in that, The whitelist policy includes an account whitelist, a second-level bank whitelist, or a first-level bank whitelist. The transaction identifier includes the transaction account, the second-level bank number, and the first-level bank number. The step of deleting the transaction identifier corresponding to the transaction request from the whitelist policy and adding the transaction identifier corresponding to the transaction request to the old system policy includes: Remove the transaction account associated with the transaction request from the account whitelist and add the transaction account associated with the transaction request to the old system policy; or, Remove the second-level row number corresponding to the transaction account or transaction card number in the transaction request from the second-level row whitelist, and add the second-level row number corresponding to the transaction account or transaction card number in the transaction request to the old system policy; or, Remove the first-level row number corresponding to the transaction account or transaction card number of the transaction request from the first-level row whitelist, and add the first-level row number corresponding to the transaction account or transaction card number of the transaction request to the old system policy.
4. The method according to claim 1, characterized in that, The routing strategy also includes a new system strategy, and the operation phase of the new system server also includes a formal launch phase, which further includes: During the formal launch phase, the routing strategy corresponding to the transaction request is the new system strategy.
5. The method according to claim 4, characterized in that, If the routing strategy for the transaction request is the new system strategy, it also includes: The transaction request is forwarded to the new system server, and the request processing result returned by the new system server is received. If the exception code of the request processing result is an old system identifier, the transaction identifier corresponding to the transaction request is deleted from the new system policy in real time, and the transaction identifier corresponding to the transaction request is added to the old system policy, and the old system server processes the transaction request.
6. The method according to claim 1, characterized in that, The determination of the whitelist strategy includes: During the trial period of the branch accounts, one or more target transaction accounts covering all business functions of the branch are selected from one or more branches to be tried, and an account whitelist is constructed using the target transaction accounts.
7. The method according to claim 6, characterized in that, Also includes: If the processing results of the transaction requests of each target transaction account in the trial phase of the branch account are all successful, the trial phase of the secondary bank is entered. One or more target secondary banks covering all business functions of the secondary bank are selected from the trial secondary banks, and a secondary bank whitelist is constructed using the secondary bank number of the target secondary banks.
8. The method according to claim 7, characterized in that, Also includes: If the transaction requests of all target secondary banks in the trial phase of the secondary bank are successfully processed, the trial phase of the primary bank is entered. One or more target primary banks that cover all business functions of the primary bank are selected from the primary banks to be tested, and a primary bank whitelist is constructed using the primary bank number of the target primary banks.
9. The method according to claim 1, characterized in that, Determining that the transaction request conforms to the whitelist policy includes: Obtain the account identifier field and / or card number identifier field from the request message of the transaction request; The transaction request is determined to conform to the whitelist policy by using the values of the account identifier field and / or card number identifier field.
10. The method according to claim 9, characterized in that, Determining whether a transaction request conforms to the whitelist policy based on the value of the account identifier field includes: If the request message of the transaction request includes an account identifier field, the transaction account of the transaction request shall be determined according to the value of the account identifier field; The transaction account in the transaction request is compared with the account whitelist. If the transaction account in the transaction request belongs to the account whitelist, the transaction request is determined to comply with the whitelist policy; or... A second-level row matching request, including the transaction account of the transaction request, is sent to the transaction information server. The server returns the second-level row number corresponding to the transaction account of the transaction request. This second-level row number is compared with a second-level row whitelist. If the second-level row number corresponding to the transaction account of the transaction request belongs to the second-level row whitelist, the transaction request is determined to conform to the whitelist policy; or... The transaction information server sends a first-level row matching request, which includes the transaction account of the transaction request, to the transaction information server. The transaction information server returns the first-level row number corresponding to the transaction account of the transaction request. The transaction information server compares the first-level row number corresponding to the transaction account of the transaction request with the first-level row whitelist. If the first-level row number corresponding to the transaction account of the transaction request belongs to the first-level row whitelist, the transaction request is determined to conform to the whitelist policy.
11. The method according to claim 9, characterized in that, Determining whether a transaction request conforms to the whitelist policy based on the value of the card number identifier field includes: If the request message of the transaction request includes a card number identifier field, the transaction card number of the transaction request is determined based on the value of the card number identifier field; An account matching request, including the transaction card number of the transaction request, is sent to the transaction information server. The transaction information server returns the transaction account corresponding to the transaction card number of the transaction request. The transaction account of the transaction request is compared with an account whitelist. If the transaction account of the transaction request belongs to the account whitelist, the transaction request is determined to comply with the whitelist policy; or... A secondary row matching request, including the transaction card number of the transaction request, is sent to the transaction information server. The server returns a secondary row number corresponding to the transaction card number of the transaction request. This secondary row number is compared with a secondary row whitelist. If the secondary row number corresponding to the transaction card number of the transaction request belongs to the secondary row whitelist, the transaction request is determined to conform to the whitelist policy. Alternatively, A first-level row matching request, including the transaction card number of the transaction request, is sent to the transaction information server. The transaction information server returns the first-level row number corresponding to the transaction card number of the transaction request. The first-level row number corresponding to the transaction card number of the transaction request is compared with the first-level row whitelist. If the first-level row number corresponding to the transaction card number of the transaction request belongs to the first-level row whitelist, the transaction request is determined to conform to the whitelist policy.
12. The method according to claim 10, characterized in that, The account identifier field is any one of the following fields: standard account field, personalized account field, anonymous account field; the card number identifier field is any one of the following fields: standard card number field, personalized card number field, anonymous card number field.
13. The method according to claim 12, characterized in that, The personalized account field includes a processing identifier, a transaction account, and a verification code; the personalized card number field includes a processing identifier, a transaction card number, and a verification code; determining the transaction account or transaction card number of the transaction request based on the value of the account identifier field or the card number identifier field includes: The processing identifier and the verification code are deleted from the value of the personalized account field or the personalized card number field to obtain the elimination conversion result; wherein, the elimination conversion is performed using the SPEL parsing expression processor; The value of the elimination and conversion result is used as the transaction account or transaction card number of the transaction request.
14. The method according to claim 12, characterized in that, Also includes: Send a restoration request to the transaction information server corresponding to the value of the anonymous account field or the anonymous card number field, and receive the restoration result returned by the transaction information server; The value of the restoration result is used as the transaction account or transaction card number of the transaction request.
15. The method according to claim 12, characterized in that, The transaction request includes the terminal identifier of the old system terminal; and also includes: Based on the terminal identifier of the old system terminal, the corresponding financial institution's hiding method is searched from the old system database, and the value of the anonymous account field or the anonymous card number field is restored to determine the restoration result; wherein, the restoration process is executed using the SPEL expression parsing processor. The value of the restoration result is used as the transaction account or transaction card number of the transaction request.
16. The method according to claim 1, characterized in that, The real-time modification of the routing strategy for the transaction request includes: The routing policy corresponding to the transaction request, stored in the hard disk or server database, is modified in real time, and the routing policy corresponding to the transaction request, stored in memory, is refreshed.
17. The method according to claim 16, characterized in that, The step of real-time modification of the routing policy corresponding to the transaction identifier stored in the hard disk or server database and refreshing the routing policy corresponding to the transaction identifier in memory includes: Generate a routing policy modification request; wherein, the routing policy modification request includes modifying the mapping relationship; The modified correspondence is substituted into the modification script corresponding to the development environment of the old system server and executed to update the routing strategy of the transaction identifier corresponding to the transaction request in the hard disk or the server database; The updated routing strategy corresponding to the transaction identifier of the transaction request is obtained from the hard disk or the server database, and the memory is refreshed asynchronously.
18. The method according to claim 17, characterized in that, The routing strategy for obtaining the updated transaction identifier corresponding to the transaction request from the hard disk or the server database includes: Based on the format of the routing policy in memory, determine the acquisition path of the updated routing policy for the transaction identifier corresponding to the transaction request; wherein the routing policy in the hard disk is in XML or JSON format, and the routing policy in the server database is a relational database table or a non-relational database table; The updated routing strategy for the transaction identifier corresponding to the transaction request is obtained from the acquisition path.
19. The method according to claim 1, characterized in that, After forwarding the transaction request to the new system server, the process further includes: Determine whether the waiting time for the request processing result exceeds a preset time threshold. If so, resend the transaction request to the new system server. Increment the number of timeouts; If the number of timeouts exceeds a preset timeout threshold, the routing strategy modifies the server address corresponding to the bank card number in the transaction request to the server URL of the old system server.
20. The method according to claim 19, characterized in that, Also includes: The transaction requests corresponding to the number of timeouts are reversed.
21. The method according to claim 1, characterized in that, After receiving the request processing result returned by the new system server, the method further includes: Determine whether the successfully processed request result matches the expected result. If the request processing result does not meet the expected processing result, the transaction request is resent to the new system server; The number of deviations in the request processing results that do not meet the expected processing results is counted, and the transaction requests exceeding a preset deviation threshold are processed using the old system server.
22. A device for processing transaction requests during a system switchover, characterized in that, The device is used in legacy system servers, and the device includes: The receiving module is used to receive transaction requests sent by the old system terminal; The routing module is used to find the routing strategy corresponding to the transaction request in memory according to the running stage of the new system server; wherein, the routing strategy includes a whitelist strategy; The judgment module is used to forward the transaction request to the new system server when the transaction request conforms to the whitelist policy, and to receive the request processing result returned by the new system server. The modification module is used to modify the routing strategy of the transaction request in real time when the exception code of the request processing result is the old system identifier, and process the transaction request according to the real-time modified routing strategy; The operation phases of the new system server include the branch account trial phase, the secondary bank trial phase, and the primary bank trial phase; The routing module is also used for: During the trial period of the branch account, the routing strategy corresponding to the transaction request is an account whitelist; During the trial phase of the second-level row, the routing strategy corresponding to the transaction request is the second-level row whitelist; During the trial phase of the first-level bank, the routing strategy corresponding to the transaction request is the first-level bank whitelist.
23. An electronic device for processing transaction requests during a system switchover, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-21.
24. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-21.
25. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-21.
Citation Information
Patent Citations
System switching method and device, equipment, medium and program product
CN114358921A
