Banking three-party system transaction synchronization method and system

Abstract

The application discloses a bank three-party system transaction synchronization method and system, relates to the field of data synchronization, and can be applied to the financial field and other fields.The system specifically comprises a core system, an intermediate peripheral system and a secondary peripheral system.The core system is used for initiating a transaction request to the intermediate peripheral system, processing a transaction according to a received transaction request feedback result to obtain a transaction success result, and providing the transaction success result to the intermediate peripheral system.The intermediate peripheral system is connected with the core system and is used for providing the received transaction request to the secondary peripheral system, receiving a transaction request feedback result fed back by the secondary peripheral system, and providing the transaction request feedback result to the core system.According to the received transaction success result, the transaction state synchronization of corresponding transactions in the intermediate peripheral system, the core system and the secondary peripheral system is completed.The secondary peripheral system is connected with the intermediate peripheral system and is used for feeding back a transaction request feedback result to the intermediate peripheral system according to the received transaction request.

Description

Technical Field

[0001] This application relates to the field of data synchronization and can be applied to the financial sector and other fields, particularly a method and system for synchronizing transactions in a bank's third-party system. Background Technology

[0002] Currently, the banking system architecture presents the following transaction scenarios: When a transaction occurs, the core system needs to request a transaction verification from an intermediate peripheral system. The peripheral system also needs to request and verify a credit limit from another secondary peripheral system. Only after both the peripheral and secondary peripheral systems have successfully verified the transaction can the core system process it. For example, when some accounts transact within the core system, they need to request a credit limit from the funds pool management system. In addition to verifying the funds pool limit, the funds pool management system also needs to request a credit limit from the credit granting system. In these three systems, the transaction occurs within the core system and has two states (success / failure). The funds pool management system needs to synchronize the transaction status with the core system to update the credit limit information, and the credit granting system needs to update the credit limit information based on the transaction status of the credit granting system. The two peripheral systems need to ensure timely consistency with the core system's transaction status to accurately calculate the credit limit and ensure verification accuracy. With high transaction volumes, anomalies can occur in system transaction processing and inter-system communication, making inter-system transaction synchronization particularly important. Currently, transaction synchronization between the three systems is extremely difficult. Summary of the Invention

[0003] The purpose of this application is to provide a method and system for synchronizing transactions across three banking systems. An intermediate peripheral system handles transaction synchronization with the other two systems, reducing the number of interactions between systems. The core system and the secondary peripheral system do not need to concern themselves with transaction synchronization, minimizing resource consumption for both. The intermediate peripheral system employs different synchronization strategies depending on the system: a transaction result push and proactive query strategy with the core system, and a proactive query and transaction reversal strategy with the secondary peripheral system, ensuring timely synchronization of transactions across the three systems.

[0004] To achieve the above objectives, the bank's third-party system transaction synchronization system provided in this application specifically includes: an intermediate peripheral system, a core system, and a secondary peripheral system; the core system is used to initiate transaction requests to the intermediate peripheral system, process transactions based on the received transaction request feedback results to obtain a successful transaction result, and provide the successful transaction result to the intermediate peripheral system; the intermediate peripheral system is connected to the core system and is used to provide the received transaction requests to the secondary peripheral system, receive transaction request feedback results from the secondary peripheral system, and provide the transaction request feedback results to the core system; and, based on the received successful transaction result, complete the synchronization of the transaction status of corresponding transactions in the intermediate peripheral system, the core system, and the secondary peripheral system; the secondary peripheral system is connected to the intermediate peripheral system and is used to provide transaction request feedback results to the intermediate peripheral system based on the received transaction requests.

[0005] In the aforementioned bank tripartite system transaction synchronization system, optionally, the intermediate peripheral system includes a core transaction result processing module, which is used to synchronize the transaction status of corresponding transactions in the intermediate peripheral system, the core system, and the secondary peripheral system based on the received transaction success and failure results.

[0006] In the aforementioned bank tripartite transaction synchronization system, optionally, the intermediate peripheral system further includes a core transaction query module; the core transaction query module is used to initiate a query request to the core system for the transaction corresponding to the transaction request feedback result when the transaction request feedback result is provided to the core system and no transaction success result is received from the core system after a predetermined period; and to provide the transaction success result and transaction failure result fed back by the core system to the core transaction result processing module.

[0007] In the aforementioned bank tripartite transaction synchronization system, optionally, the intermediate peripheral system further includes a secondary peripheral system exception handling module; the secondary peripheral system exception handling module is connected to the core transaction result processing module and is used to provide the transaction failure result received by the core transaction result processing module to the secondary peripheral system for corresponding transaction reversal processing.

[0008] In the aforementioned bank tripartite transaction synchronization system, optionally, the intermediate peripheral system further includes a secondary peripheral system reversal transaction application module. The secondary peripheral system reversal transaction application module is connected to the secondary peripheral system exception handling module and the secondary peripheral system, respectively. It is used to generate a reversal application for the corresponding transaction based on the transaction failure result, provide the reversal application to the secondary peripheral system, and update the transaction status of the corresponding transaction in the secondary peripheral system based on the reversal processing result fed back by the secondary peripheral system.

[0009] In the aforementioned bank tripartite system transaction synchronization system, optionally, the intermediate peripheral system further includes a secondary peripheral system transaction query module; the secondary peripheral system transaction query module is used to initiate a query request for the transaction corresponding to the transaction request to the secondary peripheral system when the transaction request is provided to the secondary peripheral system and no feedback result of the transaction request is received from the secondary peripheral system after a predetermined period; and to provide the transaction success result and transaction failure result fed back by the secondary peripheral system to the core transaction result processing module.

[0010] In the aforementioned bank tripartite transaction synchronization system, optionally, the intermediate peripheral system further includes a secondary peripheral system reversal transaction application module. The secondary peripheral system reversal transaction application module is connected to the secondary peripheral system exception handling module and the secondary peripheral system, respectively. It is used to generate a reversal application for the corresponding transaction based on the successful transaction result, provide the reversal application to the secondary peripheral system, and update the transaction status of the corresponding transaction in the secondary peripheral system based on the reversal processing result fed back by the secondary peripheral system.

[0011] This application also provides a method for synchronizing bank third-party system transactions applied to the aforementioned bank third-party system transaction synchronization system. The method includes: forwarding transaction requests provided by the core system to secondary peripheral systems, and providing the transaction request feedback results from the secondary peripheral systems to the core system; and synchronizing the transaction status of corresponding transactions in the intermediate peripheral systems, the core system, and the secondary peripheral systems based on the transaction success results fed back by the core system.

[0012] In the aforementioned method for synchronizing transactions across the three banking systems, preferably, the process of synchronizing the transaction status of corresponding transactions in the intermediate peripheral systems, the core system, and the secondary peripheral systems based on the successful transaction result returned by the core system further includes: when the transaction request feedback result is provided to the core system, and no successful transaction result is received from the core system after a predetermined period, initiating a query request to the core system for the transaction corresponding to the transaction request feedback result; and synchronizing the transaction status of corresponding transactions in the intermediate peripheral systems, the core system, and the secondary peripheral systems based on the successful transaction result and the failed transaction result returned by the core system.

[0013] In the aforementioned method for synchronizing transactions across the three-party banking systems, preferably, synchronizing the transaction status of corresponding transactions in the intermediate peripheral system, the core system, and the secondary peripheral system based on the transaction failure result fed back by the core system includes: updating the transaction status of corresponding transactions in the intermediate peripheral system and the core system to "transaction failure" based on the transaction failure result; generating a reversal application for the corresponding transaction based on the transaction failure result and providing the reversal application to the secondary peripheral system; and updating the transaction status of the corresponding transaction in the secondary peripheral system to "transaction failure" based on the reversal processing result fed back by the secondary peripheral system.

[0014] In the aforementioned method for synchronizing transactions across the three-party banking systems, preferably, providing the transaction request feedback result from the secondary peripheral system to the core system further includes: when the transaction request is provided to the secondary peripheral system and no transaction request feedback result is received from the secondary peripheral system after a predetermined period, updating the corresponding transaction status in the intermediate peripheral system and the core system to transaction failure; initiating a query request for the transaction corresponding to the transaction request to the secondary peripheral system, and synchronizing the transaction status of the corresponding transaction in the intermediate peripheral system, the core system, and the secondary peripheral system based on the transaction success result and transaction failure result fed back by the secondary peripheral system.

[0015] In the above-mentioned method for synchronizing transactions in the three-party banking system, preferably, the process of synchronizing the transaction status of the corresponding transaction in the intermediate peripheral system, the core system, and the secondary peripheral system based on the successful transaction result fed back by the secondary peripheral system includes: generating a reversal application for the corresponding transaction based on the successful transaction result, providing the reversal application to the secondary peripheral system, and updating the transaction status of the corresponding transaction in the secondary peripheral system to transaction failure based on the reversal processing result fed back by the secondary peripheral system.

[0016] This application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-described method.

[0017] This application also provides a computer-readable storage medium storing a computer program that performs the above-described methods.

[0018] This application also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described method.

[0019] The beneficial technical effects of this application are as follows: the use of an intermediate peripheral system to be responsible for transaction synchronization with the other two systems reduces the interaction between systems and minimizes the resource consumption of the core system and the secondary peripheral system; the intermediate peripheral system adopts different transaction synchronization strategies according to different systems, thereby achieving the goal of timely and accurate transaction synchronization. Attached Figure Description

[0020] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, do not constitute a limitation thereof. In the drawings:

[0021] Figure 1 This is a schematic diagram of the structure of a bank third-party system transaction synchronization system provided in an embodiment of this application;

[0022] Figure 2 This is a schematic diagram of the principle structure of a bank third-party system transaction synchronization system provided in an embodiment of this application;

[0023] Figure 3 This is a schematic diagram of a normal transaction process and transaction synchronization logic provided in an embodiment of this application;

[0024] Figure 4 This is a schematic diagram illustrating the core abnormal transaction processing flow and successful transaction synchronization logic provided in an embodiment of this application;

[0025] Figure 5 This is a schematic diagram of the core abnormal transaction processing flow and failed transaction synchronization logic provided in an embodiment of this application;

[0026] Figure 6 This is a schematic diagram of the abnormal transaction processing flow and failed transaction synchronization logic of the secondary peripheral system provided in an embodiment of this application;

[0027] Figure 7 This is a schematic diagram illustrating the abnormal transaction processing flow and successful transaction synchronization logic of a secondary peripheral system provided in an embodiment of this application;

[0028] Figure 8 A flowchart illustrating a bank third-party system transaction synchronization method provided in an embodiment of this application;

[0029] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0030] The following will describe in detail the implementation methods of this application with reference to the accompanying drawings and embodiments, so as to fully understand how this application uses technical means to solve technical problems and achieve technical effects, and to implement it accordingly. It should be noted that, as long as there is no conflict, the various embodiments and features in each embodiment of this application can be combined with each other, and the resulting technical solutions are all within the protection scope of this application.

[0031] Furthermore, the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.

[0032] Please refer to Figure 1 As shown, the bank's third-party system transaction synchronization system provided in this application specifically includes: an intermediate peripheral system, a core system, and a secondary peripheral system. The core system initiates a transaction request to the intermediate peripheral system, processes the transaction based on the received transaction request feedback result to obtain a successful transaction result, and provides the successful transaction result to the intermediate peripheral system. The intermediate peripheral system is connected to the core system and is used to provide the received transaction request to the secondary peripheral system, receive the transaction request feedback result from the secondary peripheral system, and provide the transaction request feedback result to the core system. It also synchronizes the transaction status of corresponding transactions in the intermediate peripheral system, core system, and secondary peripheral system based on the received successful transaction result. The secondary peripheral system is connected to the intermediate peripheral system and is used to provide the transaction request feedback result to the intermediate peripheral system based on the received transaction request.

[0033] In practice, the intermediate peripheral systems are responsible for synchronizing transactions with the core system and secondary peripheral systems. When the core system initiates a transaction, it needs to send a transaction request to the intermediate peripheral systems, and the intermediate peripheral systems need to send transaction requests to the secondary peripheral systems. After a successful transaction, the core system sends a message to notify the peripheral systems of the transaction success. For transactions that are unclear in the core system or the secondary peripheral systems, the transaction status needs to be queried. Transaction requests from the core system to the intermediate peripheral systems and from the intermediate peripheral systems to the secondary peripheral systems all use the CICS connection method (requiring a wait for a response). Transaction result notifications from the core system use the MQ connection method (reducing system connections and eliminating the need to wait for a response). Transaction queries between the intermediate peripheral systems and the core system, as well as between the intermediate peripheral systems and the secondary peripheral systems, all use the CICS connection method for information exchange (requiring a wait for a response).

[0034] Please refer to Figure 2As shown, the intermediate peripheral system may include: a core transaction response module, a core transaction result processing module, a core abnormal transaction processing module, a core transaction query module, a secondary peripheral system transaction application module, a secondary peripheral system abnormal handling module, a secondary peripheral system transaction query module, and a secondary peripheral system reversal transaction application module. These modules are interconnected and work together to complete transaction processing and synchronization functions. The specific workflow between modules will be described in detail in subsequent embodiments and will not be elaborated here.

[0035] Please refer to Figure 3 As shown, under normal transaction procedures, the process is mainly completed by three components: the core transaction response module, the secondary peripheral system transaction application module, and the core transaction result processing module. Specifically, the core system initiates a transaction application to the intermediate peripheral system. The core transaction response module of the intermediate peripheral system processes the application successfully. Then, the secondary peripheral system's transaction application module initiates a transaction application to the secondary peripheral system, which also returns successfully. The secondary peripheral system successfully returns its processing result to the core transaction system. Upon receiving the return, the core system completes the transaction and pushes the successful transaction result to the intermediate peripheral system via MQ. The intermediate peripheral system confirms the result, and the entire transaction process ends. After the intermediate peripheral system confirms the result, transaction synchronization is completed, and the transaction status of all three systems is successful. (e.g.) Figure 3 (Processes 1 to 5)

[0036] In one embodiment of this application, the intermediate peripheral system includes a core transaction result processing module. This module is used to synchronize the transaction status of corresponding transactions in the intermediate peripheral system, the core system, and the secondary peripheral system based on received transaction success and failure results. Further, the intermediate peripheral system also includes a core transaction query module. This module is used to initiate a query request to the core system for the transaction corresponding to the transaction request feedback result when the transaction request feedback result is provided to the core system and no transaction success result is received from the core system after a predetermined period. It also provides the transaction success and failure results from the core system to the core transaction result processing module. Subsequently, the intermediate peripheral system may also include a secondary peripheral system exception handling module. This module is connected to the core transaction result processing module and is used to provide the transaction failure result received by the core transaction result processing module to the secondary peripheral system for reversal processing of the corresponding transaction.

[0037] In practice, when abnormal transactions occur in the core system, the handling process is as follows:

[0038] This scenario involves a secondary peripheral system successfully returning a message to the core system. However, due to a core transaction failure or failure to receive the MQ transaction success notification, the intermediate peripheral system is unaware of the core system's transaction result. In this case, the intermediate peripheral system's core transaction exception handling module triggers the core transaction query module to proactively query the core transaction. The query results are categorized as either successful or failed, with different processing flows and synchronization mechanisms for each.

[0039] Transaction success processing procedures and transaction synchronization mechanisms, such as Figure 4 As shown, the core transaction exception handling module informs the core transaction result processing module that the transaction was successful. After confirmation by the core transaction result processing module, the successful transaction synchronization is completed (the transaction status of all three systems is successful). Figure 4 (Processes 1 to 7)

[0040] Transaction failure handling process and transaction synchronization mechanism, such as Figure 5 As shown, when a transaction fails, the intermediate peripheral system first completes its own transaction synchronization processing. After processing, the core and intermediate peripheral systems' transaction status is "failed," while the secondary peripheral system's transaction status is "successful." Then, the intermediate peripheral system's core transaction exception handling module informs the secondary peripheral system's exception handling module of the transaction failure. The secondary peripheral system's processing module triggers the reversal transaction application module to initiate a reversal application for the original transaction. After the secondary peripheral system successfully returns, it completes the transaction synchronization of the secondary peripheral system (all three systems' transaction statuses are "failed"). (For example...) Figure 5 (Processes 1 to 9)

[0041] In one embodiment of this application, the intermediate peripheral system further includes a secondary peripheral system reversal transaction application module. This module is connected to both the secondary peripheral system exception handling module and the secondary peripheral system. It is used to generate a reversal application for the corresponding transaction based on the transaction failure result, and to provide the reversal application to the secondary peripheral system. It also updates the transaction status of the corresponding transaction in the secondary peripheral system based on the reversal processing result fed back by the secondary peripheral system. Further, the intermediate peripheral system also includes a secondary peripheral system transaction query module. This module is used to initiate a query request for the transaction corresponding to the transaction request to the secondary peripheral system when, after providing the transaction request to the secondary peripheral system, no feedback result is received from the secondary peripheral system after a predetermined period. It also provides the transaction success result and transaction failure result fed back by the secondary peripheral system to the core transaction result processing module. Subsequently, the intermediate peripheral system may further include a secondary peripheral system reversal transaction application module. The secondary peripheral system reversal transaction application module is connected to the secondary peripheral system exception handling module and the secondary peripheral system, respectively. It is used to generate a reversal application for the corresponding transaction based on the successful transaction result, provide the reversal application to the secondary peripheral system, and update the transaction status of the corresponding transaction in the secondary peripheral system based on the reversal processing result fed back by the secondary peripheral system.

[0042] In practice, when a secondary peripheral system malfunctions, the handling procedure is as follows:

[0043] This scenario involves an intermediate peripheral system requesting a transaction from a secondary peripheral system, but the request fails and the intermediate peripheral system is unable to ascertain the outcome. In this case, the intermediate peripheral system first reports a transaction failure to the core system, informing it that the transaction failed due to the unclear outcome of the request from the secondary peripheral system, thus completing the transaction synchronization (transaction failure) between the intermediate peripheral system and the core system. Subsequently, the intermediate peripheral system triggers the secondary peripheral system's exception handling module for processing. This exception handling module then triggers the secondary peripheral system's query module, where the query results are categorized as either successful or failed, with different processing flows and synchronization mechanisms for each.

[0044] Transaction failure handling process and transaction synchronization mechanism, such as Figure 6 As shown, when the query result for a transaction is "failed," no further processing is required. At this time, the transaction status between the core system and the intermediate / outer systems is also "failed," and the transaction is synchronized. (e.g.) Figure 6 (Processes 1 to 6)

[0045] Transaction success processing procedures and transaction synchronization mechanisms, such as Figure 7When the transaction result is successful, the transaction status between the core system and the intermediate peripheral system is still considered failed. Therefore, the transaction in the secondary peripheral system needs to be reversed. The exception handling module of the intermediate peripheral system will initiate a reversal transaction to the secondary peripheral system. After the transaction is completed, the transaction synchronization of the three systems is achieved. (e.g.) Figure 7 (Processes 1 to 8)

[0046] Therefore, in this application, the intermediate system is responsible for transaction synchronization with the core system and secondary peripheral systems, reducing the number of interactions between systems. The core system and secondary peripheral systems do not need to concern themselves with transaction synchronization, minimizing resource consumption by both systems. Currently, all transactions in the bank's architecture occur at the core, making core system resources extremely valuable; this design reduces core system resource consumption. The intermediate system adopts different synchronization strategies depending on the system: with the core, it uses transaction result push and proactive query strategies; with secondary peripheral systems, it uses proactive query and transaction reversal strategies, achieving timely synchronization of transactions across the three systems.

[0047] Please refer to Figure 8 As shown, this application also provides a method for synchronizing bank third-party system transactions applied to the aforementioned bank third-party system transaction synchronization system, the method comprising:

[0048] S801 forwards transaction requests provided by the core system to the secondary peripheral system and provides the transaction request feedback results from the secondary peripheral system back to the core system;

[0049] Based on the successful transaction results reported by the core system, S802 synchronizes the transaction status of the corresponding transactions in the intermediate peripheral system, the core system, and the secondary peripheral system.

[0050] In the above embodiments, synchronizing the transaction status of corresponding transactions in the intermediate peripheral systems, the core system, and the secondary peripheral systems based on the successful transaction result fed back by the core system further includes: when the transaction request feedback result is provided to the core system, and no successful transaction result is received from the core system after a predetermined period, initiating a query request to the core system for the transaction corresponding to the transaction request feedback result; synchronizing the transaction status of corresponding transactions in the intermediate peripheral systems, the core system, and the secondary peripheral systems based on the successful transaction result and the failed transaction result fed back by the core system. Specifically, synchronizing the transaction status of corresponding transactions in the intermediate peripheral systems, the core system, and the secondary peripheral systems based on the failed transaction result fed back by the core system includes: updating the transaction status of corresponding transactions in the intermediate peripheral systems and the core system to "failed transaction" based on the failed transaction result; generating a reversal application for the corresponding transaction based on the failed transaction result, and providing the reversal application to the secondary peripheral system; updating the transaction status of the corresponding transaction in the secondary peripheral system to "failed transaction" based on the reversal processing result fed back by the secondary peripheral system. Specific implementation methods have been described in detail in the foregoing embodiments and will not be elaborated further here.

[0051] In another embodiment of this application, providing the transaction request feedback result from the secondary peripheral system to the core system further includes: when the transaction request is provided to the secondary peripheral system and no transaction request feedback result is received from the secondary peripheral system after a predetermined period, updating the corresponding transaction status of the intermediate peripheral system and the core system to transaction failure; initiating a query request for the transaction corresponding to the transaction request to the secondary peripheral system, and synchronizing the transaction status of the corresponding transaction in the intermediate peripheral system, the core system, and the secondary peripheral system based on the transaction success result and transaction failure result fed back by the secondary peripheral system. Specifically, synchronizing the transaction status of the corresponding transaction in the intermediate peripheral system, the core system, and the secondary peripheral system based on the transaction success result fed back by the secondary peripheral system includes: generating a reversal application for the corresponding transaction based on the transaction success result, providing the reversal application to the secondary peripheral system; updating the transaction status of the corresponding transaction in the secondary peripheral system to transaction failure based on the reversal processing result fed back by the secondary peripheral system. Specific implementation methods have been described in detail in the foregoing embodiments and will not be described in detail here.

[0052] The beneficial technical effects of this application are as follows: the use of an intermediate peripheral system to be responsible for transaction synchronization with the other two systems reduces the interaction between systems and minimizes the resource consumption of the core system and the secondary peripheral system; the intermediate peripheral system adopts different transaction synchronization strategies according to different systems, thereby achieving the goal of timely and accurate transaction synchronization.

[0053] This application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-described method.

[0054] This application also provides a computer-readable storage medium storing a computer program that performs the above-described methods.

[0055] This application also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described method.

[0056] like Figure 9 As shown, the electronic device 600 may also include: a communication module 110, an input unit 120, an audio processing unit 130, a display 160, and a power supply 170. It is worth noting that the electronic device 600 does not necessarily need to include these components. Figure 9 All components shown; in addition, the electronic device 600 may also include Figure 9 For components not shown, please refer to existing technologies.

[0057] like Figure 9 As shown, the central processing unit 100, sometimes also referred to as a controller or operating control, may include a microprocessor or other processor device and / or logic device. The central processing unit 100 receives inputs and controls the operation of various components of the electronic device 600.

[0058] The memory 140 may be, for example, one or more of a cache, flash memory, hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices. It may store the aforementioned failure-related information, and also store a program for executing that information. The central processing unit 100 may execute the program stored in the memory 140 to perform information storage or processing, etc.

[0059] Input unit 120 provides input to central processing unit 100. Input unit 120 may be, for example, a keypad or touch input device. Power supply 170 provides power to electronic device 600. Display 160 displays images and text. Display may be, for example, an LCD display, but is not limited thereto.

[0060] The memory 140 can be a solid-state memory, such as a read-only memory (ROM), random access memory (RAM), a SIM card, etc. It can also be a memory that retains information even when power is off, can be selectively erased, and contains more data; examples of this type of memory are sometimes referred to as EPROMs. The memory 140 can also be some other type of device. The memory 140 includes a buffer memory 141 (sometimes referred to as a buffer). The memory 140 may include an application / function storage unit 142 for storing application programs and function programs or processes for executing the operation of the electronic device 600 via the central processing unit 100.

[0061] The memory 140 may also include a data storage unit 143 for storing data, such as contacts, digital data, pictures, sounds, and / or any other data used by the electronic device. The driver storage unit 144 of the memory 140 may include various drivers for the electronic device's communication functions and / or for performing other functions of the electronic device (such as messaging applications, address book applications, etc.).

[0062] The communication module 110 is a transmitter / receiver 110 that transmits and receives signals via antenna 111. The communication module (transmitter / receiver) 110 is coupled to the central processing unit 100 to provide input signals and receive output signals, which can be the same as in a conventional mobile communication terminal.

[0063] Based on different communication technologies, multiple communication modules 110 can be configured in the same electronic device, such as cellular network modules, Bluetooth modules, and / or wireless LAN modules. The communication module (transmitter / receiver) 110 is also coupled to a speaker 131 and a microphone 132 via an audio processor 130 to provide audio output via the speaker 131 and receive audio input from the microphone 132, thereby enabling typical telecommunications functions. The audio processor 130 may include any suitable buffer, decoder, amplifier, etc. Additionally, the audio processor 130 is coupled to a central processing unit 100, enabling on-device recording via the microphone 132 and on-device playback of stored audio via the speaker 131.

[0064] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0065] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0066] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0067] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0068] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above descriptions are merely specific embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A bank's third-party transaction synchronization system, characterized in that, The system comprises: an intermediate peripheral system, a core system, and a secondary peripheral system; The core system is used to initiate transaction requests to the intermediate peripheral system, process the transaction based on the feedback results of the received transaction requests to obtain a successful transaction result, and provide the successful transaction result to the intermediate peripheral system through a message queue. The intermediate peripheral system is connected to the core system and is used to receive the transaction request initiated by the core system via CICS connection, forward the transaction request to the secondary peripheral system via CICS connection, receive the transaction request feedback result from the secondary peripheral system via CICS connection, and provide the transaction request feedback result to the core system via CICS connection. In addition, based on the received successful transaction results, the transaction status of the corresponding transactions in the intermediate peripheral system, core system, and secondary peripheral system is synchronized. The secondary peripheral system is connected to the intermediate peripheral system and is used to receive the transaction request via CICS connection and to send the transaction request feedback result back to the intermediate peripheral system. The intermediate peripheral system includes a core transaction result processing module, a core transaction query module, a secondary peripheral system anomaly handling module, and a secondary peripheral system reversal transaction application module. The core transaction result processing module is used to synchronize the transaction status of corresponding transactions in the intermediate peripheral system, core system and secondary peripheral system based on the received transaction success results and transaction failure results; The core transaction query module is used to initiate a query request to the core system for the transaction corresponding to the transaction request feedback result when the transaction request feedback result is provided to the core system and no transaction success result is received from the core system after a predetermined period. In addition, the transaction success and failure results fed back by the core system are provided to the core transaction result processing module; The secondary peripheral system exception handling module is connected to the core transaction result processing module and is used to provide the transaction failure result received by the core transaction result processing module to the secondary peripheral system for corresponding transaction reversal processing; The secondary peripheral system reversal transaction application module is connected to the secondary peripheral system exception handling module and the secondary peripheral system, respectively, and is used to generate a reversal application for the corresponding transaction based on the transaction failure result, and provide the reversal application to the secondary peripheral system; Furthermore, the transaction status of the corresponding transaction in the secondary peripheral system is updated based on the reversal processing result fed back by the secondary peripheral system.

2. The bank third-party system transaction synchronization system according to claim 1, characterized in that, The intermediate peripheral system also includes a secondary peripheral system transaction query module; The secondary peripheral system transaction query module is used to initiate a query request for the transaction corresponding to the transaction request to the secondary peripheral system when the transaction request is provided to the secondary peripheral system and no feedback result of the transaction request is received from the secondary peripheral system after a predetermined period. In addition, the transaction success and failure results fed back by the secondary peripheral system are provided to the core transaction result processing module.

3. The bank tripartite system transaction synchronization system according to claim 2, characterized in that, The intermediate peripheral system also includes a secondary peripheral system reversal transaction application module. The secondary peripheral system reversal transaction application module is connected to the secondary peripheral system exception handling module and the secondary peripheral system, respectively. It is used to generate a reversal application for the corresponding transaction based on the transaction success result and provide the reversal application to the secondary peripheral system. Furthermore, the transaction status of the corresponding transaction in the secondary peripheral system is updated based on the reversal processing result fed back by the secondary peripheral system.

4. A method for synchronizing bank transactions in a third-party system applied to the bank third-party system transaction synchronization system as described in claim 1, characterized in that, The method includes: The core system forwards transaction requests to the secondary peripheral system and provides the transaction request feedback results from the secondary peripheral system back to the core system. Based on the successful transaction results reported by the core system, the transaction status of the corresponding transactions in the intermediate peripheral system, the core system, and the secondary peripheral system is synchronized.

5. The method for synchronizing transactions in a bank's third-party system according to claim 4, characterized in that, The synchronization of transaction status among the intermediate peripheral systems, core system, and secondary peripheral systems based on the successful transaction results reported by the core system also includes: If the transaction request feedback result is provided to the core system and no transaction success result is received from the core system after a predetermined period, a query request for the transaction corresponding to the transaction request feedback result is initiated to the core system. Based on the successful and failed transaction results fed back by the core system, the transaction status of the corresponding transactions in the intermediate peripheral system, the core system, and the secondary peripheral system is synchronized.

6. The method for synchronizing transactions in a bank's third-party system according to claim 5, characterized in that, The synchronization of transaction status among the intermediate peripheral systems, core system, and secondary peripheral systems based on the transaction failure results fed back by the core system includes: Based on the transaction failure result, update the corresponding transaction status of the intermediate peripheral system and the core system to "transaction failure"; Based on the transaction failure result, a reversal request for the corresponding transaction is generated, and the reversal request is provided to the secondary peripheral system; The transaction status of the corresponding transaction in the secondary peripheral system is updated to "transaction failed" based on the reversal processing result fed back by the secondary peripheral system.

7. The method for synchronizing transactions in a bank's third-party system according to claim 4, characterized in that, Providing the transaction request feedback results from the secondary peripheral system to the core system also includes: If the transaction request is provided to the secondary peripheral system and no feedback result of the transaction request is received from the secondary peripheral system after a predetermined period, the corresponding transaction status of the intermediate peripheral system and the core system is updated to transaction failure. Initiate a query request for the transaction corresponding to the transaction request to the secondary peripheral system, and complete the synchronization of the transaction status of the corresponding transaction in the intermediate peripheral system, the core system and the secondary peripheral system based on the transaction success result and transaction failure result fed back by the secondary peripheral system.

8. The method for synchronizing transactions in a bank's third-party system according to claim 7, characterized in that, The synchronization of transaction status among the intermediate peripheral system, core system, and secondary peripheral system based on the successful transaction result fed back by the secondary peripheral system includes: Based on the successful transaction result, a reversal request for the corresponding transaction is generated, and the reversal request is provided to the secondary peripheral system; The transaction status of the corresponding transaction in the secondary peripheral system is updated to "transaction failed" based on the reversal processing result fed back by the secondary peripheral system.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method of any one of claims 4 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that enables a computer to execute the method of any one of claims 4 to 8.

11. A computer program product, comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method according to any one of claims 4 to 8.

Images