HK1092916A1 - Data processing method and system - Google Patents
Data processing method and systemInfo
- Publication number
- HK1092916A1 HK1092916A1 HK06113622.3A HK06113622A HK1092916A1 HK 1092916 A1 HK1092916 A1 HK 1092916A1 HK 06113622 A HK06113622 A HK 06113622A HK 1092916 A1 HK1092916 A1 HK 1092916A1
- Authority
- HK
- Hong Kong
- Prior art keywords
- processing
- day
- data
- memory
- host
- Prior art date
Links
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a data disposal system and method, which comprises the following parts: system host, data disposer, host storage and mirror-image storage, wherein the system host proceeds daily business disposal and night disposal, which modifies the accounting date into the following day date and switches the mirror-image storage into the data disposer; the data disposer proceeds total bill disposal; the system host receives the disposal result of data disposer, which takes over the mirror-image storage to proceed next daily business disposal. The invention can continue the disposal day and night, which improves the working efficiency.
Description
Technical Field
The present invention relates to a data processing method and a data processing system, and more particularly, to a data processing method and a data processing system for use in financial institutions such as banks.
Background
Currently, the computer systems of financial institutions, especially the core business systems of banks, have a certain time for batch processing after completing the normal work of day business. During batch processing, the core business system performs data backup, general ledger formation, rolling product counts, periodic transfers, loan expiration processing, and forming part of accounting statements based on its master database. During this period, in order to ensure the "breakpoint" of the data, i.e. to ensure that the account data is kept static for a certain time before switching to the next accounting period, so as to ensure the accuracy of the statistics, the core business system may lock the master database, thereby causing the core business system of the bank not to receive and process the transaction request from the self-service device.
The self-service device includes an Automatic Teller Machine (ATM), a point of sale (POS), a kiosk, a call center, an internet bank, or any terminal used by a bank to automatically receive a customer's request for funds.
The core business system refers to a business support system of the financial institution, and is used for processing all core businesses of the financial institution including the foreign currency.
The reasons for the core business system of the financial institution to stop or interrupt the service are mainly as follows:
(1) in the process of concurrent processing of online transactions, a database lock recording phenomenon occurs;
(2) when the batch processing is carried out at the end of the day, the core business system carries out the lock bank processing so as to carry out fund clearing, general ledger formation, general core division and the like;
(3) accounting data of the time points of the accounting dates are required to be switched and are used for the daily accounting processing and the peripheral system;
(4) the accounting date can not be switched normally due to the annual final settlement.
Fig. 1 is an external service flow diagram of a conventional financial institution core business system.
As shown in fig. 1: the financial institution core business system stops external service after the daytime transaction processing is finished, performs the daily final batch processing (step S101), and finishes the daily batch processing business, wherein the business comprises: batch processing rolling number, general ledger generation, large transaction processing business, current day accounting processing and the like. At this time, the business of the bank on the day is completely finished.
After that, the financial institution core business system starts to backup the database, extract and process the data, and package and send the processed data to the front-end processor of each peripheral system and each subsystem (step S102). The data in the core database of the financial institution at this time is static data, that is, the data is not changed at this time. After the data processing is completed, the host accounting date of the financial institution core business system is switched to enter the next day business.
The first batch treatment was performed. At the beginning of the day of the next day business of the financial institution, the core business system of the financial institution performs the initialization of the beginning of the day, prepares a business access environment and performs the financial processing of the beginning of the day, wherein a large business processing mode is used to ensure the integrity of the processing mode of the core business system. After the initial daily account is finished, yesterday report forms are generated, and since external business does not occur at the moment, data for generating the report forms are yesterday complete data, and the generated yesterday report forms can accurately represent yesterday business. After the processing is completed, the financial institution core business system opens the connections of all the peripheral service systems, and starts transaction processing (step S103).
At this point the financial institution enters the next day transaction.
The core business system of the financial institution stops transaction processing in a short time, which brings inconvenience to customers. With the development of new business varieties, such as continuous derivation of all-weather business such as personal exchange trading, a core business system capable of realizing all-weather external service is more and more urgently needed to improve the market competitiveness of financial institutions.
Disclosure of Invention
In order to solve the problem that the core business system of a bank cannot provide a service to a customer during the above-mentioned batch processing, according to an aspect of the present invention, there is provided a data processing method of a data processing system including a system host for performing transaction processing and batch processing, a data processor for backing up data processing and general ledger generation, a host memory which is a storage device of the system host, a host memory which is a synchronous storage device of the host memory, and a mirror memory which is a temporary storage device of the data processor when the mirror memory is switched from the host memory to the data processor, wherein the data processing method includes the steps of:
a) the system host computer carries out daytime transaction processing;
b) the system host machine carries out daily final batch processing;
c) the system host switches the mirror image memory to the data processor and modifies the counting date into the next day date;
d) the system host computer carries out day and first batch processing, and the data processor carries out general ledger processing:
e) the system host receives the processing result of the data processor and takes over the mirror image memory;
f) and the system host machine carries out the next inter-day transaction processing.
According to another aspect of the present invention, there is also provided a data processing system, including a system host for performing transaction processing, end-of-day batch processing, and beginning-of-day batch processing; and a host memory for storage of data of the system host;
the data processing system also comprises a data processor, a data processing unit and a data processing unit, wherein the data processor is used for backup data processing and general ledger processing; the mirror image memory is a synchronous storage device of the host memory, when the system host finishes day transaction processing and carries out day ending batch processing, the mirror image memory is switched from the host memory to the data processor, the counting date is changed into the next day date, and the data processor carries out general ledger processing according to the data in the mirror image memory; and after the data processor general ledger processing is finished, the system host takes over the mirror image memory to perform the next inter-day transaction processing.
The invention utilizes the data processor and the mirror image memory to complete the accounting processing such as general ledger generation and historical report generation and the processing and extraction of data required by peripheral systems such as database backup and report system, thereby ensuring that the general ledger generation and database backup of large-area lock base are required to be carried out at the time point of switching accounting date under the condition that the transaction processing of the system host is not influenced, and improving the efficiency of transaction acceptance and the safety of data storage.
In addition, according to the invention, a small affair processing mode is adopted when the system host computer carries out the batch processing at the end of day and the batch processing at the beginning of day, and the host computer memory and the mirror image memory adopt a double-balance double-date data structure, so that the user is subjected to the rolling number, the daily account processing and the daily statement processing on the basis.
The scheme of the invention can realize all channels, all products and all services of the financial institution to be continuously externally served all the day, greatly enhance the external service capability of the financial institution, relieve the operation service pressure of the financial institution and be beneficial to the financial institution to carry out internal daily final batch processing service and annual final settlement service.
Drawings
FIG. 1 is an external service flow diagram of a conventional financial institution core business system;
fig. 2 is a schematic block diagram of a core service system according to a first embodiment of the present invention;
fig. 3 is a flowchart of a data processing method of a financial institution core business system according to a first embodiment of the present invention;
fig. 4 is a flowchart of a data processing method of a system host of a financial institution core business system according to a first embodiment of the present invention;
FIG. 5 is a flowchart of a data processing method of a data processor of a financial institution core business system according to a first embodiment of the present invention;
FIG. 6 is a flowchart for extracting breakpoints of switching dates according to the first embodiment of the present invention;
FIG. 7 is an example of a dual date dual balance data structure according to the present invention.
Detailed Description
Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
Fig. 2 is a schematic block diagram of a core service system according to a first embodiment of the present invention. As shown in fig. 2, the core service system includes a system host 10, a data processor 20, a host memory 30 and a mirror memory 40.
The system host 10 is used for transaction and batch processing, the data handler 20 is used for backup data processing and general ledger generation, the host memory 30 is a storage device of the system host 10, the mirror memory 40 is a synchronous storage device of the host memory 30, and serves as a temporary storage device of the data handler 20 when the mirror memory 40 is switched from the host memory 30 to the data handler 20.
Fig. 3 is a flowchart of a data processing method of a financial institution core business system according to a first embodiment of the present invention. In fig. 3, reference numeral 201 denotes a data processing procedure of the system host 10, and reference numeral 202 denotes a data processing procedure of the data processor 20, and in this case, the used data is mirror data at the time of date switching, and corresponds to time-point static data of the flow.
The data processing method of the system host 10 will be described with reference to fig. 3.
After the daytime transaction processing, the system host 10 performs end-of-day batch processing (step S203).
After the end-of-day batch processing is completed, the system host 10 quickly switches the mirror memory 40 to the data processor 20 and modifies the counting date to the next day date (step S204).
Then, the initial batch processing is performed (step S205).
After the data handler 20 completes the general ledger processing, the system host 10 receives the processing result of the data handler 20 and takes over the mirror memory 40.
After that, the next day operation is performed.
The data processing method of the data processor 20 mainly includes taking over the mirror memory 40 (step S207), performing general ledger processing (step S208), transmitting the processing result to the system host 10, and switching the mirror memory 40 to the system host 10 (step S209).
Fig. 4 is a flowchart illustrating a data processing method of the system host 10 of the financial institution core business system in more detail according to the first embodiment of the present invention.
As shown in fig. 4, the end-of-day batch processing (step S203) performed by the system host 10 of the core business system is a reconciliation processing including a reservation processing occurring on the day when the day counter business is finished. During this process, the end-of-day batch process does not affect the outbound transaction processing of the system host 10.
Since transactions by the system host 10 occur frequently, it is necessary to find a time point at which to switch the accounting date. At this point in time, a condition that the daily end batch ledger is completed, no transaction occurs, and the amount of data transfer between the system host memory 30 and the mirror memory 40 is small must be satisfied, so that the system host memory 30 and the mirror memory 40 can be instantaneously separated. This point in time is referred to as the accounting date switch "breakpoint" time.
After the first processing of the end-of-day batch processing is finished, the accounting date switching "breakpoint" time is extracted in a loop processing manner (see fig. 6 for details).
Once the system host 10 extracts the accounting date switching "breakpoint" time, the system host 10 separates the mirror memory 40 and takes over by the data processor 20 while switching the accounting date to the next date (step S204), wherein the separation of the mirror memory 40 and the switching of the accounting date of the system host can be regarded as being performed simultaneously when the data stored in the mirror memory 40 is identical to the data in the system host memory 30 at the time when the accounting date is switched to the "breakpoint". And then, all transactions generated by the core service system are regarded as next day services.
After the accounting date is switched, the system host performs an initial initialization process (step S205), which mainly includes updating the parameter table in the parameter database.
Then, daily account processing and daily statement processing are performed (step S205), in which the non-pending accounts on the previous day are processed using an alternate-day account processing method, such as alternate-day penalty processing.
Every other day accounting processing refers to processing the last day of accounting after the accounting date is switched. In order to realize the processing of the last day account, the extracted account information is data at the time of switching to the next accounting date.
The system host 10 performs real-time monitoring on the data processor 20 after separating the mirror image memory, monitors whether the data processor 20 successfully takes over the mirror image memory 40, whether the database engine is successfully started, whether the database data is correct, and monitors general ledger generation in the data processor 20 and separation of the data processor 20 from the mirror image memory 40.
After the completion of the daily accounting processing and the daily statement generation, the system host 10 starts waiting for a signal of completion of accounting such as general ledger of the data processor 20, and upon receiving the accounting completion signal, the system host determines that the received text data of the general ledger is complete. Since the ledger text data does not affect the current transaction, receipt of the ledger text data can be performed in parallel with transaction processing.
After the receipt of the general ledger text data is completed, the system host 10 performs the day-to-day ledger completion processing (step S210). The initial daily account supplementary processing is mainly aimed at the initial daily processing related to the general ledger, such as balance check of the general ledger and the branch ledger, and generates related reports, such as a daily accounting table, a general ledger page and the like.
After the completion of the initial day accounting completion, the accounting part of the batch processing of the system host 10 is completed. Then, the system host 10 determines whether the data handler 20 has successfully detached the mirror memory 40. If the splitting is determined to have been successful, the host memory 30 takes over the mirror memory 40 (step 211), and the host memory 30 and the mirror memory 40 start synchronizing to ensure the consistency of their data.
During the time that host memory 30 takes over mirroring memory 40, host memory 30 may remain active at all times, i.e., system host 10 may still conduct transaction processing in real time. After the host memory 30 takes over the mirror memory 40, the system host 10 receives the historical report form returned by the data processor 20, moves to a corresponding report form catalog, cuts and packs the report form generated by the system host together, and sends the report form to the front-end processor of each subsystem, so that each subsystem can print the daily account report form for checking, recording and the like.
By this point, the processing by the system host of the core service system is completely finished.
Next, the data processing process of the data processor 20 is described in detail with reference to fig. 5.
The data handler 20 starts waiting at the same time as the batch processing of the system host 10 starts. After receiving the signal of successful separation of the host memory 30 from the mirror memory 40 from the system host 10, the data processor 20 takes over the mirror memory 40 (step S207).
Since the data handler 20 is identical to the device environment of the system host 10, the data handler 20 after taking over the mirror memory 40 is equivalent to a second host having static data at the time of switching the "breakpoint" of the accounting date, and can satisfy the needs of performing accounting processing and data processing on the static data.
After taking over the mirror memory 40, the static data can be kept unchanged since the data handler 20 is not serviced externally. Therefore, the data processor 20 can perform accounting processing and generation of general ledgers that require a large-area lock base (step S212). The large-area database locking is to operate a large number of data tables in the processing process, and the integrity of the tables needs to be ensured at the same time, so that the database system automatically locks the tables at the moment, and the data change caused by the operation of a second party is prevented.
For example, generation of the general ledger involves almost all the accounting tables, and requires a long processing time. The system host cannot perform transactions when generating the general ledger. And the data handler 20 can perform parallel processing while the system host 10 performs batch processing and transaction processing, thereby implementing a "dual host batch" scheme.
After the general ledger generation is completed, the data processor 20 sends the general ledger back to the system host 10. The system host 10 completes the receipt of the general ledger.
After the data processor 20 finishes the accounting processing, the business of the day is terminated. At this time, the core service system needs to use a database backup tool for backup.
Then, the backed-up data is extracted according to the list file on the data processor 20, or the data in the database is processed and unloaded to obtain the data required by the peripheral system, and then the data is packed in a differentiated manner, i.e. the fragmented file is compressed into a data storage file, and the packed data is sent to each peripheral system to generate a partial history report (step S213). The processing time of the historical report is long, a large amount of operation databases are needed, and the occupied system resources are large, so that the pressure of a system host can be reduced by generating the historical report by the data processor, and the batch processing time is greatly reduced.
After the data processor 20 has completed operating the mirror memory 40, it needs to be separated. The mirror database engine is shut down and the data handler 20 is disconnected from the mirror store 40. After the mirror memory 40 is separated, the data handler 20 sends the generated history report to the system host 10. The host memory 30 takes over the mirror memory 40 (step S214).
At this time, the data processor 20 processes the backup data, extracts the subsystem data, cuts the subsystem data into the backup directories of each subsystem according to the subsystem, packs the backup directories according to the subsystem, and compresses and packs the database backup data. The database backup data is sent to the dedicated backup memory, and the subsystem data packets are sent to the subsystem front-end computers (step S215).
By this point, the processing of the data processor is completely finished.
Fig. 6 is a flowchart for extracting an accounting date switching breakpoint according to the first embodiment of the present invention. As shown in fig. 6, the daily final batch accounting process is performed first (step S220). Then, it is determined whether the daily final batch accounting is completed (step S221). It is then determined whether the mirror memory 30 can be quickly detached (step S222), and it is then determined whether no transaction has occurred (step S223). If the judgment result of any one of the steps S221-S223 is NO, the step S221 is returned to continue to circularly process the accounting until the accounting date switching breakpoint is extracted. Thereafter, the flow advances to step S204 to switch the accounting date and separate the mirror memory.
In order to enable the system host to continuously perform transaction processing so that the financial institution can continuously provide services for customers, the invention also provides a batch processing business online scheme. In the scheme, the function of conventional batch processing is realized in an online transaction processing mode, so that under the condition that a system host does not stop transaction, the parallel processing of transaction and batch processing can be realized.
According to the first embodiment of the invention, the batch business online scheme mainly comprises four aspects of content, namely small transaction processing, rolling number of mobile clients, daily account processing and daily statement processing.
The transaction processing is a database programming method, which refers to locking and logging updated contents when a database is updated, ensuring that data in the database cannot be changed by a second party user in the processing process, recovering the locked data under the condition of processing failure, and releasing the locked data for next processing only after a transaction is completed and submitted.
Large transactions are locks on all pending data, commit after all processing has been completed, and then release all locks. The processing mode can ensure the integrity of the data of the same service, but the data of the service is in a locked state in the processing process, and the service cannot occur. Particularly, when batch processing is performed, all data of the whole system needs to be locked, so that the main business of the whole system cannot occur.
In order to reduce the transaction stop time of the system host, the invention provides a small transaction processing scheme: the method is characterized in that the method comprises the steps of refining the service to be processed, locking by taking a subsystem belonging to a core service system of a financial institution as a set or taking an account as a set, and processing the account simultaneously with other accounts of the service or accounts of other subsystems in the account service processing process. In this way, the occurrence of traffic that does not affect other subsystems or accounts that are not locked is not affected. Furthermore, since the time required to batch each collection is very short, the occurrence of the locked subsystem or account traffic is also hardly affected during the batch process.
The number of live users rolling the number of products refers to the number of rolling products processed while the transaction is taking place. The method adopts a mode of rolling the accumulated number by the mobile account, and rolls the accumulated number while realizing online business for loan accounts, public deposit accounts, private deposit accounts and internal accounts, thereby relieving the system pressure caused by batch rolling of the accumulated number. The implementation of the number of live user rolls is based on a database structure called double balance double date.
Fig. 7 is an example of a dual balance dual date data structure according to the present invention.
As shown in fig. 7, the internal account master file in the accounting base in the host memory 30 of the core business system has current transaction information such as account balance, transaction date, and balance direction, and previous transaction information such as transaction date and transaction balance direction. Therefore, the balance of the accounting date switching breakpoint moment can be accurately obtained according to the transaction date field, so that the account of yesterday and the end of the day is processed, and the normal occurrence of the account of the day cannot be influenced.
Wherein the account balance refers to the actual balance of the current account; the transaction date refers to the accounting date when the balance amount is changed into the account balance since the account is subjected to accounting last time; the last day balance refers to the account balance before the balance change occurs on the date of the account transaction; the transaction date refers to the transaction date of the record before the balance change occurred on the account transaction date.
When the mobile account rolls the accumulated number, and the transaction and account balance change occur for the first time in the accounting date of the account, the accumulated number of the mobile account is calculated according to the current transaction date and the previous balance, so that the current accumulated number is obtained and is updated to the database.
The action of moving the user refers to the action that business exchange occurs in a certain account, so that the actual balance of the current account is changed. If the mobile user is the first transaction on the same day, the transaction date is changed to the transaction date, the transaction date is changed to the same day, and the balance on the same day is changed to the account balance.
In the case of batch processing business integrated processing, when the previous day accounting processing is performed, the previous day account-not-yet accounting is processed by using an alternate day accounting processing method, such as alternate day penalty processing. Every other day accounting processing refers to processing the last day of accounting after the accounting date is switched. In order to realize the processing of the last day account, the extracted account information is data when the last day is switched. The implementation mode is also based on a database mode with double balances and double dates, after date switching, the direction of the balance of the last day and the direction of the balance of the last day are extracted when the transaction date is the same day, and the direction of the balance of the current account and the direction of the balance of the account are extracted when the transaction date is not the same day.
When the daily statement is processed based on the database mode with double balances and double dates, the data of the accounting date when the breakpoint is switched is extracted, the daily accounting statement is generated, and the accuracy of the presentation of the daily accounting statement of banking business is guaranteed. The method for extracting the data when the accounting date switches the breakpoint is the same as the method used when the last day accounting processing is performed.
Claims (20)
1. A data processing method of a data processing system including a system host (10), a data handler (20), a host memory (30), and a mirror memory (40), the system host (10) being used for transaction processing and batch processing, the data handler (20) being used for backup data processing and general ledger generation, the host memory (30) being a storage device of the system host (10), the mirror memory (40) being a synchronous storage device of the host memory (30), and being a temporary storage device of the data handler (20) when the mirror memory (40) is switched from the host memory (30) to the data handler (20), wherein the data processing method comprises the steps of:
a) the system host (10) performs daytime transaction processing;
b) the system host (10) carries out batch processing at the end of a day;
c) the system host (10) switches the mirror memory (40) to the data processor (20) and changes the counting date to the next day date;
d) the system host (10) performs primary batch processing, and the data processor (20) performs general ledger processing;
e) the system host (10) receives the processing result of the data processor (20) and takes over the mirror image memory (40);
f) the system host (10) performs the next inter-day transaction processing.
2. The data processing method of claim 1, wherein between the step b) and the step c), further comprising the steps of:
g) performing daily final batch accounting processing;
h) judging whether the daily final batch processing account is finished or not;
i) judging whether the mirror memory (30) can be quickly separated;
j) judging whether no transaction occurs;
if the judgment result of any one of the steps h), i) and j) is 'no', returning to the step g) to continue to circularly process the accounting, otherwise, extracting an accounting date switching breakpoint.
3. The data processing method of claim 1, wherein the beginning-of-day batch processing comprises:
initializing at the beginning of the day;
processing the last day account;
and (5) processing the report on the day.
4. A data processing method according to claim 1, wherein in said step e), a day-to-day accounting post-processing is performed after receiving processing data of said data processor (20).
5. The data processing method of claim 1, wherein the end-of-day batch processing employs a small transaction approach.
6. The data processing method of claim 1, wherein the beginning-of-day batch processing employs a small transaction approach.
7. The data processing method of claim 1, wherein the databases in the host memory (30) and the mirror memory (40) employ a dual date dual balance structure.
8. The data processing method of claim 7, wherein a floating owner roll number process is employed during the end-of-day batch process and the initial-of-day batch process.
9. A data processing method as claimed in claim 3, wherein the databases in the host memory (30) and the mirror memory (40) employ a dual date dual balance structure.
10. The data processing method of claim 9, wherein in performing the receivables processing, receivables outstanding accounts are processed using an every other day accounting processing method.
11. The data processing method according to claim 9, wherein in the previous-day statement processing, data at a break point of switching of an accounting date is extracted, and an account statement of the previous day is generated.
12. The data processing method according to claim 10, wherein the final-day batch processing and the initial-day batch processing employ a small transaction processing manner and a rolling number of mobile users, and when the previous-day report processing is performed, data at a break point of switching of an accounting date is extracted, and an account report of the previous day is generated.
13. A data processing system comprises a system host (10) used for carrying out transaction processing, end-of-day batch processing and initial-of-day batch processing; and a host memory (30) for storage of data of the system host (10);
wherein the data processing system further comprises:
a data processor (20) for backup data processing and general ledger processing;
a mirror memory (40) being a synchronous storage device of the host memory (30),
when the system host (10) finishes day transaction processing and end-of-day batch processing, switching the mirror image memory (40) from the host memory (30) to the data processor (20), modifying the counting date to the next day date, and performing general ledger processing by the data processor (20) according to the data in the mirror image memory (40);
after the data processor (20) general ledger processing is finished, the system host (10) takes over the mirror memory (40) and performs the next inter-day transaction processing.
14. The data processing system of claim 13, wherein the end-of-day batching is in a small transaction.
15. The data processing system of claim 13, wherein the beginning-of-day batch processing employs a small transaction approach.
16. The data processing system of claim 13, wherein the databases in the host memory (30) and the mirrored memory (40) employ a dual date dual balance architecture.
17. The data processing system of claim 13, wherein a player roll number process is employed during the end-of-day batch process and the initial-of-day batch process.
18. The data processing system of claim 13, wherein the beginning-of-day batch process comprises:
initializing at the beginning of the day;
processing the last day account;
and (5) processing the report on the day.
19. The data processing system of claim 18, wherein in performing the receivables processing, receivables outstanding accounts are processed using an every other day accounting processing method.
20. The data processing system of claim 18, wherein in the daily statement processing, data at a break point of accounting date switching is extracted to generate a daily accounting statement.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200410101351.8A CN1790416B (en) | 2004-12-17 | 2004-12-17 | Data processing method and data processing system |
Publications (2)
Publication Number | Publication Date |
---|---|
HK1092916A1 true HK1092916A1 (en) | 2007-02-16 |
HK1092916B HK1092916B (en) | 2016-02-19 |
Family
ID=
Also Published As
Publication number | Publication date |
---|---|
CN1790416B (en) | 2015-07-15 |
CN1790416A (en) | 2006-06-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN1790416B (en) | Data processing method and data processing system | |
Lacker | Payment system disruptions and the federal reserve following September 11, 2001 | |
Ureche-Rangau et al. | One crisis, two crises… the subprime crisis and the European sovereign debt problems | |
US20140114821A1 (en) | Apparatus for consolidating financial transaction information | |
WO1998004992A2 (en) | Process facility management matrix and system and method for performing batch processing in an on-line environment | |
CN109377355A (en) | Transaction data processing method and device | |
CN106991606B (en) | Transaction data processing method and device | |
CN108762895B (en) | Method and device for processing distributed transaction | |
CN101329795B (en) | System and method for implementing bank card agent authorization | |
CN111680080A (en) | Data processing method and data processing system | |
CN101950452B (en) | Bank card core system and bank card stand-in authorization system data synchronous processing method | |
Hofmann et al. | The impact of unconventional monetary policies on retail lending and deposit rates in the euro area | |
HK1092916B (en) | Data processing method and system | |
CN111275423A (en) | Third-party base account balance monitoring reconciliation method | |
CN100424687C (en) | Network-based online processing system and method | |
US20030191741A1 (en) | Trading data management system, method and program therefor | |
JP3471728B2 (en) | Future date completion processing system and method | |
JP3903471B2 (en) | Complete processing system with date and time | |
CN111563816A (en) | System and method for separating accounts and messages under bank-crossing payment business | |
CN107730381B (en) | Method and device for backing up cross section data | |
Lublóy et al. | Operational disruption and the Hungarian real time gross settlement system (VIBER) | |
CN113240515A (en) | Debit card information processing method and system | |
CN116521452B (en) | Disaster recovery system and business processing method based on disaster recovery system | |
JP2003256646A (en) | Business information processing method and business information processing program for credit recovery | |
JP2852302B2 (en) | Re-transfer processing method of account transfer processing |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PC | Patent ceased (i.e. patent has lapsed due to the failure to pay the renewal fee) |
Effective date: 20211217 |