Method and device for guaranteeing data consistency in new and old system switching process

Abstract

The invention provides a method and a device for guaranteeing data consistency in a new and old system switching process. The method comprises the following steps: constructing an account association table of fund pool products of an old system, and dividing customers of the old system into highest-level customers and subordinate customers to which the highest-level customers belong according to the account association table, so as to construct a customer association table, taking the highest-level customers as vertexes, of the fund pool products, the fund pool product represents a fund pool product in a bank-to-public business scene, data of an old system is loaded according to a client association table to obtain a migration data set, and the migration data set is serially locked one by one by adopting a fund pool contract to obtain a locked migration data set; and migrating the locked migration data set to a new system by taking a client in the client association table as a unit. The problems that an existing new and old system data migration scheme is complex in migration data processing logic and poor in process reusability are solved.

Description

Technical Field

[0001] This application relates to the technical field of ensuring data consistency during the switching process between old and new systems. Specifically, it relates to a method, device, computer-readable storage medium, and electronic device for ensuring data consistency during the switching process between old and new systems. Background Art

[0002] During the process of migrating data from an old system to a new system, it is necessary to ensure the consistency of associated customer data, that is, all or none of the associated customer data is migrated and imported from the source system to the target system to meet the requirements of business scenarios. Most of the existing old-new system data migration solutions are for online data migration at the individual customer dimension or directly use the native migration tools of the database for batch data synchronization at the data table dimension, without involving the consistency processing of associated customer data migration scenarios such as fund pools.

[0003] The existing associated customer data consistency guarantee strategies may increase the complexity of the data migration process and system implementation due to the introduction of a transaction framework (such as heavyweight components like the distributed transaction framework Seata) when migrating data to the new system, and bring system stability risks. Moreover, in different business scenarios or data volume situations, the selection of the associated customer consistency guarantee scheme is not universal, which also brings problems such as complex data processing logic and poor process reusability. Summary of the Invention

[0004] The main purpose of this application is to provide a method, device, computer-readable storage medium, and electronic device for ensuring data consistency during the switching process between old and new systems, so as to at least solve the problems of complex migration data processing logic and poor process reusability in the existing old-new system data migration solutions.

[0005] To achieve the above object, according to one aspect of the present application, a method for ensuring data consistency during the switching process between an old system and a new system is provided, including: constructing an account association table for the fund pool products of the old system, and classifying the customers of the old system into the highest-level customers and the subordinate customers of the highest-level customers according to the account association table, so as to construct a customer association table for each of the fund pool products with the highest-level customer as the vertex, where the fund pool product represents the fund pool product in the corporate banking business scenario of the bank, the account association table includes N-level accounts, the first-level account is the highest-level account, and the N-level account is the subordinate account of the (N-1)-level account, the customer association table includes N-level customers, the first-level customer is the highest-level customer, and the N-level customer is the subordinate customer of the (N-1)-level customer, N≥2; loading and processing the data of the old system according to the customer association table to obtain a migration data set, and serially locking each of the migration data sets one by one using a fund pool contract to obtain a locked migration data set; migrating the locked migration data set to the new system in units of the customers in the customer association table.

[0006] Optionally, during the process of constructing the customer association table for each of the fund pool products with the highest-level customer as the vertex, the method further includes: in the case that the subordinate customers of the highest-level customer are involved in multiple fund pool products, determining multiple highest-level customers of the subordinate customers involved in multiple fund pool products; constructing a virtual highest-level customer as the vertex of the multiple highest-level customers of the subordinate customers, and constructing the cross-fund-pool customer association table with the virtual highest-level customer as the vertex, where the cross-fund-pool refers to the fund pool involving multiple fund pool products.

[0007] Optionally, during the process of serially locking each of the migration data sets one by one using a fund pool contract, the method further includes: in the case that it is detected that the data locking of any customer in the migration data set fails, stopping the current and subsequent locking operations, and unlocking the data in the migration data set that has been successfully locked.

[0008] Optionally, during the process of migrating the locked migration data set to the new system in units of the customers in the customer association table, the method further includes: in the case that it is detected that the data migration of any customer in the locked migration data set shows data migration failure, stopping the data migration of the current customer, and deleting and rolling back the data in the locked migration data set that has been successfully migrated from the new system, where the data migration failure includes data verification exception and system network exception.

[0009] Optionally, after loading the data of the old system according to the customer association table to obtain a migration data set, the method further includes: performing tagging processing on the migration data set by using global routing to set the status of each customer in the migration data set to a pre-migration status, so as to obtain a pre-migration data set; performing transaction detection on the pre-migration data set to determine that no transaction operation has occurred for each of the customers corresponding to the pre-migration data set before the locking operation.

[0010] Optionally, during the process of performing transaction detection on the pre-migration data set, the method further includes: when it is detected that a target customer corresponding to the pre-migration data set has performed a transaction operation, stopping the transaction detection on the pre-migration data set, and restarting the transaction detection process on the pre-migration data set until the target customer completes the transaction operation.

[0011] Optionally, after migrating the locked migration data set to the new system, the method further includes: when it is detected that the locked migration data set has been completely migrated to the new system, performing an unlocking operation on the locked migration data set so that the customers corresponding to the locked migration data set can perform transaction operations.

[0012] According to another aspect of the present application, there is provided a device for ensuring data consistency during the switching process between an old system and a new system, including: a first construction unit, configured to construct an account association table of the fund pool products of the old system, divide the customers of the old system into the highest-level customers and the subordinate customers of the highest-level customers according to the account association table, so as to construct a customer association table of each of the fund pool products with the highest-level customer as the vertex, where the fund pool product represents a fund pool product in the corporate banking business scenario of the bank, the account association table includes N-level accounts, the first-level account is the highest-level account, the N-level account is the subordinate account of the (N - 1)-level account, the customer association table includes N-level customers, the first-level customer is the highest-level customer, the N-level customer is the subordinate customer of the (N - 1)-level customer, and N≥2; a locking unit, configured to load the data of the old system according to the customer association table to obtain a migration data set, and serially lock the migration data set one by one by using a fund pool contract to obtain a locked migration data set; a migration unit, configured to migrate the locked migration data set to the new system in units of the customers in the customer association table.

[0013] According to still another aspect of the present application, there is provided a computer-readable storage medium, where the computer-readable storage medium includes a stored program, and when the program runs, it controls the device where the computer-readable storage medium is located to execute any one of the methods for ensuring data consistency during the switching process between an old system and a new system.

[0014] According to another aspect of the present application, there is provided an electronic device, including: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include a method for ensuring data consistency during the switching process between any of the old and new systems.

[0015] Applying the technical solution of the present application, by constructing an account association table of the fund pool products in the old system, classifying the customers in the old system into the highest-level customers and the subordinate customers of the highest-level customers according to the account association table, so as to construct a customer association table of each fund pool product with the highest-level customer as the vertex, wherein the fund pool product represents the fund pool product in the corporate banking business scenario of the bank, the account association table includes N-level accounts, the first-level account is the highest-level account, the N-level account is the subordinate account of the (N - 1)-level account, the customer association table includes N-level customers, the first-level customer is the highest-level customer, the N-level customer is the subordinate customer of the (N - 1)-level customer, N≥2; performing a loading process on the data in the old system according to the customer association table to obtain a migration data set, and serially locking each of the migration data sets one by one using a fund pool contract to obtain a locked migration data set; migrating the locked migration data set to the new system in units of the customers in the customer association table. By introducing the concept of "vertex customer" and constructing the association relationship between the vertex customer and the customers to be associated, the present application can, without relying on an external transaction framework, achieve the goal of serializing and importing associated customer data into the target system, ensuring the consistency and integrity of the data; the present application not only ensures the efficiency of data migration, meets the performance requirements, but also guarantees the continuity and stability of the business before and after migration, providing solid technical support for the smooth switching of the bank's core system. It solves the problems that the existing data migration solutions between old and new systems have complex data migration processing logic and poor process reusability. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The specification drawings forming a part of the present application are used to provide a further understanding of the present application. The schematic embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation to the present application. In the drawings:

[0017] Figure 1 It shows a hardware structure block diagram of a mobile terminal for implementing a method for ensuring data consistency during the switching process between old and new systems provided in an embodiment of the present application;

[0018] Figure 2 It shows a flowchart of a method for ensuring data consistency during the switching process between old and new systems provided in an embodiment of the present application;

[0019] Figure 3Shows a schematic diagram of identifying associated customers of the fund pool type and constructing a customer association table provided according to an embodiment of the present application;

[0020] Figure 4 Shows a schematic diagram of identifying cross-fund-pool type associated customers and constructing a customer association table provided according to an embodiment of the present application;

[0021] Figure 5 Shows a schematic flowchart of a method for ensuring data consistency during the specific process of switching between old and new systems provided according to an embodiment of the present application;

[0022] Figure 6 Shows a schematic flowchart of the migration process of associated customers provided according to an embodiment of the present application;

[0023] Figure 7 Shows a structural block diagram of a device for ensuring data consistency during the process of switching between old and new systems provided according to an embodiment of the present application.

[0024] Among them, the above-mentioned drawings include the following reference numerals:

[0025] 102, processor; 104, memory; 106, transmission device; 108, input / output device. Detailed implementation manners

[0026] It should be noted that, without conflict, the embodiments in the present application and the features in the embodiments may be combined with each other. The present application will be described in detail below with reference to the drawings and in conjunction with the embodiments.

[0027] In order to enable those skilled in the art to better understand the solution of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0028] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily need to be used to describe a specific order or sequence. It should be understood that such data used may be interchanged under appropriate circumstances for the embodiments of the present application described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device including a series of steps or units does not necessarily need to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these process, method, product or device.

[0029] For ease of description, some nouns or terms related to the embodiments of the present application are described below:

[0030] Old system: The source system for data migration.

[0031] New system: The target system for data migration.

[0032] Fund pool product: Specifically refers to the fund pool product in the corporate business scenario of the bank, which pools the account funds of each member unit and can meet the fund needs of each member unit in a timely manner through fund transfer up and down, ensuring the normal business activities of member units.

[0033] Ordinary customer: Specifically refers to a customer who has not signed up for the three major fund pool products in the corporate cash management business scenario of the bank.

[0034] Fund pool customer: Specifically refers to a customer who has signed up for a fund pool product in the corporate cash management business scenario of the bank, including the highest-level customer who opens the fund pool product and its subordinate customers.

[0035] Cross-fund pool customer: A customer whose different accounts have signed up for two or more fund products at the same time.

[0036] Associated customer: Includes fund pool customers, or cross-fund pool customers who have signed up for two or more fund products at the same time, and other customers belonging to the corresponding fund pool products as a group of associated customers.

[0037] Vertex customer: As a representative of a group of associated customers, the vertex customer constructs the mapping relationship between the vertex customer and the customers to be associated, and realizes the data import of all associated customers into the target system.

[0038] Data loading: The process of parsing and storing the data file that needs to be migrated to the target system, which is converted from the source system, into the intermediate temporary library of the migration system.

[0039] Data migration: Smoothly migrate the business and technical information carried by the data in the source system to the target system, and ensure that the business meaning of all customer service data before and after the migration remains unchanged.

[0040] Online migration: Online migrate the customer-related data of the source system to the new system in a non-stop service manner.

[0041] Business continuity: After the customer data is migrated from the source system to the target system, all business scenarios related to customer service data before and after the migration can remain consistent and continue the business function.

[0042] Locking: To reduce the impact of migration on customers and the impact of the migration process on the old core production, the migration is carried out one by one according to customers or funding pool contracts. The customers being migrated should ensure data quiescence, and the customers being migrated need to be locked to restrict accounting transactions.

[0043] Global Routing: Provides the ability to locate the target deployment unit based on mapping elements. It is used to store and query the customer migration status during the locking and unlocking process.

[0044] As introduced in the background art, the existing data migration solutions between old and new systems have complex migration data processing logic and poor process reusability. To solve the problems of complex migration data processing logic and poor process reusability in the existing data migration solutions between old and new systems, embodiments of the present application provide a method, device, computer-readable storage medium, and electronic device for ensuring data consistency during the switching process between old and new systems.

[0045] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention.

[0046] The method embodiments provided in the embodiments of the present application can be executed on a mobile terminal, a computer terminal, or a similar computing device. Taking running on a mobile terminal as an example, Figure 1 is a hardware structure block diagram of a mobile terminal for a method of ensuring data consistency during the switching process between old and new systems in an embodiment of the present invention. As Figure 1 shown, the mobile terminal may include one or more ( Figure 1 only one is shown in Figure 1 a processor 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data. Among them, the above mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those of ordinary skill in the art can understand that Figure 1 the structure shown is only schematic and does not limit the structure of the above mobile terminal. For example, the mobile terminal may further include more or fewer components than Figure 1 shown, or have a different configuration from

[0047] The memory 104 can be used to store computer programs, such as software programs and modules of application software, such as the computer program corresponding to the method for ensuring data consistency during the switching process between the old and new systems in the embodiments of the present invention. The processor 102 executes various functional applications and data processing by running the computer programs stored in the memory 104, that is, implements the above-mentioned method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memories. In some instances, the memory 104 may further include a memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal through a network. Examples of the above-mentioned network include, but are not limited to, the Internet, enterprise intranet, local area network, mobile communication network, and combinations thereof. The transmission device 106 is used to receive or send data via a network. Specific examples of the above-mentioned network may include the wireless network provided by the communication provider of the mobile terminal. In one instance, the transmission device 106 includes a network adapter (Network Interface Controller, abbreviated as NIC), which can be connected to other network devices through a base station and thus communicate with the Internet. In one instance, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0048] In this embodiment, a method for ensuring data consistency during the switching process between the old and new systems running on a mobile terminal, a computer terminal, or a similar computing device is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here.

[0049] Figure 2 is a flowchart of the method for ensuring data consistency during the switching process between the old and new systems according to the embodiments of the present application. As Figure 2 shown, the method includes the following steps:

[0050] Step S201: Construct an account association table for the fund pool products of the old system. Classify the customers of the old system into top-level customers and their subordinate customers according to the account association table, so as to construct a customer association table with the top-level customers as the vertices for each of the above fund pool products. Among them, the above fund pool products represent the fund pool products in the corporate banking business scenario of the bank. The above account association table includes N-level accounts, the first-level account is the top-level account, and the Nth-level account is the subordinate account of the (N - 1)th-level account. The above customer association table includes N-level customers, the first-level customer is the above top-level customer, and the Nth-level customer is the subordinate customer of the (N - 1)th-level customer, where N≥2;

[0051] Among them, the schematic diagram of identifying the customers associated with the fund pool products and constructing the customer association table is as Figure 3 shown;

[0052] Specifically, after data loading and before actual migration, query the main table of the cash management product contract and account relationship. Obtain the fund pool product contract number, current customer number, and top-level customer number according to the salable product code of the fund pool product, and record the query results into the product contract number, current customer number, and vertex customer number fields of the migration batch customer details table respectively, to complete the recording of the mapping relationship between the vertex customers (top-level customers) and the customers to be associated (subordinate customers). In summary, for the migration of fund pool customers, the concept of vertex customers is designed as a representative of a group of associated customers, and a customer association table between vertex customers and customers to be associated is constructed, providing a basis for the data consistency of the associated customer migration in the subsequent step S203.

[0053] Step S202: Perform loading processing on the data of the old system according to the above customer association table to obtain a migration data set, and serially lock each of the above migration data sets one by one using the fund pool contract to obtain a locked migration data set;

[0054] Specifically, first perform serial locking one by one according to the fund pool contract to ensure that all associated customers being migrated should ensure data stillness. It is necessary to lock all associated customers being migrated to restrict accounting transactions. Since the associated customers represented by the same vertex customer may involve one or more fund pool contracts, use a single-threaded serial call to the old system one by one according to the fund pool contract dimension. After all the customers belonging to the previous contract are successfully locked, then lock the customers belonging to the current contract, so as to ensure the locking process of all associated customers under multiple fund pool contracts. By locking the associated customers according to the fund pool contract and using the vertex customer to represent a group of associated customers for all associations, it makes preparations for the serial import of customer data into the new system in step S203 and ensures the data consistency of associated customers during the switching process between the old and new core systems.

[0055] Step S203: Taking the customers in the above customer association table as units, migrate the above locked migration data set to the new system.

[0056] Specifically, after the associated customers are successfully locked, a single-threaded serialization import of all associated customer data is performed on the target system with the vertex customer representing a group of associated customers. That is, according to a specific vertex customer, query the customer details of the migration batch, obtain the set of associated customers according to the mapping relationship, and serially export the data of the customers in the set from the source system and import it into the target system one by one in a single thread in the form of customer dimension according to the ordinary customer migration method. After the data migration of the previous customers is successful, then perform the data migration of the current customers, so as to ensure that all associated customer data enters the target system completely. To balance the migration efficiency while ensuring data consistency, multi-threaded parallel migration can also be adopted among multiple different vertex customers to ensure that the data migration efficiency meets the performance requirements.

[0057] Through this embodiment, the method for ensuring data consistency in the process of switching between the old and new systems by using the above steps S201, S202, and S203 mainly solves the problem of how to ensure data consistency and business continuity when migrating the data of fund pool customers and cross-fund pool customers to the new system in the scenario of corporate cash management business in banks. By introducing the concept of "vertex customer" and constructing the association relationship between the vertex customer and the customers to be associated, this embodiment can realize the serialization import of associated customer data into the target system without relying on an external transaction framework, ensuring data consistency and integrity. This embodiment not only ensures the efficiency of data migration, meets the performance requirements, but also guarantees the continuity and stability of the business before and after migration, providing strong technical support for the smooth switching of the bank's core system. The embodiment of this application aims to provide a simple, efficient and highly reusable method for ensuring the consistency of associated customer data to meet the requirements of diverse corporate banking business scenarios. It solves the problems of complex data processing logic and poor process reusability in the existing old and new system data migration solutions.

[0058] In the specific implementation process, in the process of constructing the customer association table with the above-mentioned highest-level customer as the vertex for each of the above-mentioned fund pool products in step S201, the above method further includes: in the case where the subordinate customers of the above-mentioned highest-level customer are involved in multiple above-mentioned fund pool products, determining multiple above-mentioned highest-level customers of the above-mentioned subordinate customers involved in multiple above-mentioned fund pool products; constructing a virtual highest-level customer as the vertex of the multiple above-mentioned highest-level customers of the above-mentioned subordinate customers, and constructing the above-mentioned customer association table across the fund pool with the above-mentioned virtual highest-level customer as the vertex, where the above-mentioned cross-fund pool is a fund pool involving multiple above-mentioned fund pool products.

[0059] Among them, the schematic diagram of identifying cross-fund pool types (involving multiple fund pool products) associated customers and constructing a customer association table is as Figure 4 shown.

[0060] When a subordinate customer belongs to multiple fund pool products, it means that its capital flow may be controlled by multiple top-level customers. For example, a subsidiary may belong to the parent company's fund pool and also participate in another fund pool jointly established with other brother companies. To accurately handle such complex relationships during the old and new system switch, the concept of "virtual top-level customer" is introduced. This virtual entity serves as a unified control point to ensure that all related fund pool products can be coordinated during data migration, avoiding data conflicts caused by multiple management. By constructing a cross-fund pool customer association table with the virtual top-level customer as the vertex, cross-fund pool data consistency can be achieved. Whether it is in fund allocation, balance update, or transaction record synchronization, data accuracy and integrity can be ensured. This method is especially suitable for enterprise groups with complex fund management structures. Through the virtual top-level customer, data processing involving multiple fund pool products can be simplified into a single path, greatly improving the efficiency and success rate of data migration. In the corporate banking business scenario, in addition to fund pool products, this method can also be applied to other products and services involving multi-level customer relationships, such as supply chain finance and group account management. As long as there is a similar capital flow control requirement, this strategy can be used to ensure data consistency.

[0061] Specifically, in step S202: during the process of serially locking each of the above migration data sets using a fund pool contract, the above method further includes: when it is detected that the data lock for any customer in the above migration data set fails, stop the current and subsequent locking operations, and perform an unlocking operation on the data in the above migration data set that has been successfully locked.

[0062] Data locking in this method is an important means to ensure data consistency. Especially during the data migration process, in order to prevent data from being concurrently modified, it is necessary to lock the data before the migration starts. As a type of smart contract, the fund pool contract can automatically execute specific rules and conditions to ensure that only verified operations can modify the data when switching between the old and new systems. When applying the fund pool contract to perform serial locking on the migration dataset, if it is detected that the data locking for any customer fails, this may be caused by system failures, network delays, or other technical issues. At this time, immediately stop the current and subsequent locking operations and unlock the data that has been successfully locked, which can prevent the data from being accidentally locked and avoid potential data freezing risks. This method ensures the smooth progress of data migration by promptly responding to locking failure events, and at the same time protects the liquidity of customer funds and avoids unnecessary economic losses. In the scenario of corporate banking business, the situation of data locking failure can be resolved through various methods, including but not limited to retry mechanisms, manual intervention, system health checks, etc., to ensure that the normal state of the data can be quickly restored in case of any technical challenges, and to guarantee the continuity and security of data migration.

[0063] More specifically, in step S203: When migrating the above-mentioned locked migration dataset to the new system with the customers in the above-mentioned customer association table as units, the above-mentioned method further includes: in the case of detecting that the data migration of any customer in the above-mentioned locked migration dataset shows data migration failure, stop the data migration of the current customer, and perform deletion processing and rollback processing on the data that has been successfully migrated in the above-mentioned locked migration dataset from the above-mentioned new system, where the above-mentioned data migration failure includes data verification exceptions and system network exceptions.

[0064] Data migration in this method is the core step of switching between the old and new systems. Regarding data migration failure: When performing data migration with the customers in the customer association table as units, if it is detected that the data migration of any customer fails, whether it is due to data verification exceptions (such as data format mismatch, data integrity damage, etc.) or system network exceptions (such as network connection interruption, server failure, etc.), immediate measures need to be taken. Stop the data migration of the current customer and delete the data that has been successfully migrated from the new system, and then perform rollback processing, which can ensure that the consistency and integrity of the data are not damaged. This method ensures the seamless docking of data between the old and new systems by monitoring the migration process in real time and reacting quickly when problems are found, avoiding the impact of data migration failure on the overall system switch. In the scenario of corporate banking business, the handling mechanism for data migration failure is not limited to the above-mentioned deletion and rollback, and can also include but not limited to data repair, retransmission mechanism, log recording and analysis, etc., all of which are to quickly locate problems and take effective countermeasures in case of data migration obstacles, and to guarantee the quality and efficiency of data migration.

[0065] Further, after performing the loading process on the data of the old system according to the above customer association table in step S202 to obtain the migration data set, the method further includes: performing tagging processing on the migration data set by using global routing to set the status of each customer in the migration data set to the pre-migration status, thereby obtaining a pre-migration data set; performing transaction detection on the pre-migration data set to determine that no transaction operations have occurred for each of the customers corresponding to the pre-migration data set before the locking operation.

[0066] The setting of the pre-migration status in this method is a key step in the data migration preparation stage. It indicates that the data is about to be migrated. However, before that, it is necessary to ensure that no transaction operations will affect the migrated data. Global routing is a mechanism for controlling the data flow. By adding tags of the pre-migration status to the data, it can clearly identify which data is ready for migration and which data is currently active. This method is particularly important in the scenario of corporate banking services. Since the transaction of the fund pool product is frequent and complex, if not controlled, new transaction records may be generated during the data migration process, resulting in data inconsistency. By using global routing to tag the migration data set and performing transaction detection, it can be ensured that no transaction operations have occurred for each customer in the pre-migration data set before the data is locked, thereby avoiding data concurrency problems and ensuring the accuracy of data migration. In the scenario of corporate banking services, transaction detection can not only be applied to the data migration of the fund pool product, but also be extended to other types of corporate banking service data, such as loan records, credit limit adjustments, etc. As long as it involves batch data migration, the reliability and security of data migration can be enhanced by setting the pre-migration status and performing transaction detection.

[0067] Furthermore, during the process of performing transaction detection on the pre-migration data set, the method further includes: in the case where a transaction operation is detected for the target customer corresponding to the pre-migration data set, stopping the transaction detection on the pre-migration data set until the target customer completes the transaction operation, and then restarting the transaction detection processing on the pre-migration data set.

[0068] Among them, transaction detection is a key link to ensure that the data is in a static state before migration. However, in actual operation, it may occur that the target customer is performing a transaction operation, which will hinder the data migration. When it is detected that the target customer corresponding to the pre-migration data set is performing a transaction operation, immediately stop the transaction detection and wait until the transaction is completed before restarting, which can effectively avoid the conflict between the transaction operation and the data migration operation.

[0069] By dynamically adjusting the timing of transaction detection, this method ensures the transaction integrity before data migration, avoiding data locking failures or abnormal data migrations caused by incomplete transactions. In the scenario of corporate banking services, the dynamic adjustment mechanism of transaction detection is not only applicable to fund pool products but also can be applied to other products and services involving real-time transactions, such as foreign exchange transactions and stock trading. As long as there is a need for data migration, this method can be used to ensure data consistency and transaction continuity, significantly improving the success rate and efficiency of bank system upgrades or migrations.

[0070] Specifically, after migrating the above-mentioned locked migration dataset to the new system, the above method further includes: when it is detected that the above-mentioned locked migration dataset has been completely migrated to the above-mentioned new system, performing an unlocking operation on the above-mentioned locked migration dataset so that the customers corresponding to the above-mentioned locked migration dataset can conduct transaction operations.

[0071] The unlocking operation of this method is a necessary step to restore the transaction ability of customers after data migration is completed. Once it is detected that the locked migration dataset has been successfully migrated to the new system in its entirety, the unlocking operation is immediately executed, which can release the locked status of the customer's account and allow the customer to continue with normal transaction operations. By unlocking in a timely manner after data migration is completed, this method ensures the liquidity of customer funds and avoids customer dissatisfaction and potential economic losses caused by long-term locking. In the scenario of corporate banking services, the timeliness and accuracy of the unlocking operation are crucial for maintaining customer relationships and improving service quality. In addition to fund pool products, this method is also applicable to other scenarios that require ensuring data consistency during system switching, such as credit card point systems and insurance claim settlement systems. As long as it involves the batch migration of customer data, this method can be used to balance data security and transaction convenience, achieving efficient and secure system upgrades or migrations.

[0072] The embodiments of the present application also include intelligent pre-migration inspection and dynamic adjustment. In the pre-migration stage, the prior art usually only conducts simple transaction inspections, while this embodiment introduces an intelligent pre-migration inspection mechanism. By analyzing the customer transaction behavior patterns and historical data, the intelligent inspection not only determines whether there are transactions for the customer, but also further evaluates the appropriate timing for customer data migration, predicts the transaction frequency and types that may affect the migration process, and provides a basis for the data migration window period. In addition, to cope with the uncertainties that may occur during the data migration process, such as network fluctuations and system resource limitations, this embodiment also designs a dynamic adjustment mechanism. During the data migration process, the system monitors the resource usage and migration progress in real time, and automatically adjusts the concurrency and execution strategy of the migration. For example, when detecting an increase in network latency, the number of top customer vertices for concurrent migration can be dynamically reduced to avoid data integrity risks; while when there are sufficient idle resources, the concurrency is increased to improve the migration efficiency. The intelligent pre-migration inspection of this embodiment ensures the rationality of the migration window selection, reduces the risk of migration failure caused by high transaction volumes, and improves the success rate of data migration. The dynamic adjustment mechanism enables the system to better adapt to environmental changes, balances the speed and quality of data migration, thereby improving the migration efficiency and stability while ensuring data consistency, and reducing the possibility of migration interruption and data errors caused by environmental factors.

[0073] The embodiments of the present application also include intelligent detection and automatic repair of data differences. After the data migration is completed, this embodiment designs a set of intelligent detection processes for data differences. This process automatically identifies data inconsistencies, such as differences in customer information and omissions in transaction records, by comparing the data of associated customers in the source system and the target system. Once data differences are detected, the system will automatically trigger a data repair process, and according to the preset repair rules, such as data completion and data correction, the data in the target system will be corrected to ensure the integrity and accuracy of the data.

[0074] For example, for data differences of customers across fund pools, the intelligent detection can check whether all related account information and transaction records have been completely migrated. If omissions are found, the system will automatically obtain the missing data from the old system and import it into the new system according to the highest-level customer number mapping configuration table, and at the same time update the relevant mapping relationships to achieve data consistency.

[0075] The intelligent detection and automatic repair function of data differences in this embodiment greatly reduces the need for manual intervention and improves the automation level of quality control after data migration. This not only saves human resources, reduces the risk of data inconsistency caused by manual operation errors, but also ensures the seamless docking of data between the old and new systems after migration, further enhancing business continuity and system reliability. In addition, the automatic repair mechanism can correct data errors in real time, avoiding subsequent abnormal business processing caused by data problems and improving the customer experience and the stability of bank services.

[0076] In order to enable those skilled in the art to more clearly understand the technical solution of this application, the implementation process of the method for ensuring data consistency during the switching process between the old and new systems of this application will be described in detail below in conjunction with specific embodiments.

[0077] This embodiment relates to a specific method for ensuring data consistency during the switching process between the old and new systems, as Figure 5 shown, and specifically includes the following contents:

[0078] First, identify and group related customers of the fund pool type, design and propose the concept of "vertex customers", construct the mapping relationship between vertex customers and related customers to be associated during the data loading phase, and record it in the customer details table of the migration batch. During subsequent migrations, query the set of related customers with mapping relationships based on the vertex customers, and perform data migration for all customers as a group of related customers. The process of screening and identifying the mapping relationship between vertex customers and related customers to be associated is as follows:

[0079] 1. After data loading and before actual migration, query the main table of the relationship between cash management product contracts and accounts, and obtain the fund pool product contract number, current customer number, and highest-level customer number according to the available product code of the fund pool product. Record the query results in the product contract number, current customer number, and vertex customer number fields of the customer details table of the migration batch to complete the recording of the mapping relationship between vertex customers and related customers to be associated, as Figure 3 shown.

[0080] 2. Specifically, for the cross-fund pool scenario where different accounts of the same customer may sign two or more different fund pool products, as Figure 4As shown, for cross-fund pool customers of this type and other customers of the corresponding fund pool products, they also need to be migrated as a group of associated customers to ensure data consistency. Since multiple top-level customers (i.e., multiple vertex customers) will exist due to multiple fund pools, a customer will be distributed into multiple groups, which will lead to the inability to ensure data consistency during subsequent migrations. Therefore, the present invention configures a top-level customer number mapping configuration table in advance, so that during the data loading phase, the top-level customers corresponding to different products in the cash management product contract and the account relationship main table can be mapped to the same virtual top-level customer. Finally, when executing the records of the mapping relationship between the vertex customer and the customers to be associated, different vertex customers can be mapped and normalized to the same vertex customer, providing a basis for the data consistency of subsequent migrations.

[0081] Among them, the core fields of the top-level customer number mapping configuration table are as follows:

[0082] 1) Old vertex customer number old_zone_val: Represents the old vertex customer number.

[0083] 2) New vertex customer number new_zone_val: Represents the new vertex customer number, usually named as a 14-digit virtual customer number starting with 999, i.e., '99900000000XXXX' (xxxx represents the sequence number).

[0084] 3) Valid flag valid_flag: Represents whether this configuration is valid, 0 for no / 1 for yes.

[0085] Example data description: If there are two accounts under a customer A, account m1 and m2 are respectively signed with fund pool products P1 and P2, the vertex customer number of fund pool P1 is A1, and the vertex customer number of fund pool P2 is A2. At this time, it is necessary to map and normalize the vertex customer numbers A1 and A2 to the same virtual vertex customer number, i.e., 99900000000001. Then the configuration of the top-level customer number mapping configuration table is shown in Table 1:

[0086] Table 1

[0087]

[0088] II. Data migration process of associated customers. In this embodiment, the associated customers are mainly locked according to the fund pool contract, and the vertex customer represents a group of associated customers to serially import all the associated customer data into the target system to ensure the consistency of the associated customer data during the switching process between the old and new core systems. The specific data migration process is as Figure 6 shown:

[0089] First, lock the funds pool contracts one by one in series to ensure that all associated customers being migrated should ensure data static, and lock all associated customers being migrated to restrict account transactions. Since the associated customers represented by the same vertex customer may involve one or more fund pool contracts (due to the cross-fund pool contract situation as mentioned above), the present invention uses a single thread to serially call the old system one by one according to the fund pool contract dimension. After all the customers belonging to the previous contract are successfully locked, the customers belonging to the current contract are locked, so as to ensure that all associated customers under multiple fund pool contracts are locked.

[0090] After the associated customers are locked successfully, this embodiment uses the vertex customer to represent a group of associated customers to perform a single-threaded serial import of all associated customer data into the target system. That is, according to a specific vertex customer, the migration batch customer details table is queried to obtain the associated customer set according to the mapping relationship, and the customers in the set are serially exported one by one in a single thread according to the customer dimension in the ordinary customer migration method to perform data migration operations on the target system. After the previous customer data is successfully migrated, the current customer data is migrated, thereby ensuring that all associated customer data is fully entered into the target system. In order to ensure data consistency while taking into account migration efficiency, this embodiment adopts multi-threaded parallel migration between multiple different vertex customers to ensure that the data migration efficiency meets performance requirements.

[0091] 3. Exception scenario processing of associated customer migration. For different exception scenarios, this embodiment designs different exception processing solutions to ensure that all associated customer data is migrated to the target database or retained in the old system. In particular, the data of some associated customers that have entered the target system can be automatically rolled back to the old system to ensure strong data consistency during the migration process. The details are as follows:

[0092] 1. During the pre-migration phase, if the transaction check initiated to the global routing based on the customer dimension fails (i.e., the customer has a transaction), the data migration of this customer and its associated customers will be prohibited on that day and they will not be allowed to enter the target system.

[0093] 2. For customers across fund pools, if it is not configured in the highest-level customer number mapping configuration table, the same customer will belong to different apex customers. For this abnormal customer, a pre-migration legitimacy check will be performed. If it occurs, all the associated customers to which the customer belongs will be prohibited from data migration on the same day and will not enter the target system. Re-initiate the migration after reconfiguring the mapping table.

[0094] 3. If a customer among the associated customers fails in the data loading stage, fails in data verification, or the fund pool contract to which the customer belongs has been migrated, the data migration of this customer and its associated customers will be prohibited on the same day and will not be allowed to enter the target system.

[0095] 4. If, during the above-mentioned locking phase, when invoking the legacy system one by one in a single-threaded serial manner according to the fund pool contract dimension to lock the customers under the contract, if the locking of the customers belonging to the current fund pool contract fails, then stop the locking of the current and subsequent fund pool contracts, and perform an unlocking operation on the customers of all the previously locked successfully fund pool contracts to ensure the consistency of the associated customer locking data status.

[0096] 5. During the data import phase, after obtaining the set of associated customers based on the vertex customer, when serially importing the customers in the set from the source system to the target system one by one in a single thread in the ordinary customer migration manner, if the migration of the current customer data to the target system fails (such as data verification exception, network exception, etc.), then stop the migration of the current customer data, and perform a deletion and rollback process on the associated customer data that has been successfully imported previously from the target system, so as to ensure that all the associated customer data under the current vertex customer is completely intact and has not entered the new system, and can still continue to conduct business processing in the legacy system, ensuring data consistency, integrity, and business continuity.

[0097] In this embodiment, by proposing the concept of "vertex customer", constructing the mapping relationship between the vertex customer and the customers to be associated, and using the vertex customer to represent a group of associated customers to serially import all the associated customer data into the target system, it does not need to rely on components such as an external transaction framework in implementation, simplifying the data consistency processing flow; in addition, a general configuration of the associated customer mapping relationship is designed, and a relatively general solution for identifying and grouping associated customers is proposed for the associated customers generated in different types of fund pool products and business scenarios such as cross-fund pools, with a high degree of reuse of the processing flow; and while ensuring data consistency, the migration efficiency is also taken into account. For multiple different vertex customers, multi-threaded parallel migration is adopted, and the degree of parallelism can be customized and adjusted at runtime to meet the data migration efficiency requirements of different scales.

[0098] The embodiment of the present application also provides a device for ensuring data consistency during the switching process between the legacy system and the new system. It should be noted that the device for ensuring data consistency during the switching process between the legacy system and the new system in the embodiment of the present application can be used to execute the method for ensuring data consistency during the switching process between the legacy system and the new system provided by the embodiment of the present application. The device is used to implement the above-mentioned embodiment and the preferred implementation manner, and those that have been described will not be repeated. As used hereinafter, the term "module" can be a combination of software and / or hardware that can achieve a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware is also possible and contemplated.

[0099] The following introduces the device for ensuring data consistency during the switching process between the legacy system and the new system provided by the embodiment of the present application.

[0100] Figure 7It is a schematic diagram of a device for ensuring data consistency during the switching process between the old and new systems according to an embodiment of the present application. As Figure 7 shown, the device includes:

[0101] A first construction unit 71, configured to construct an account association table of the fund pool products of the old system, divide the customers of the old system into the highest-level customers and the subordinate customers of the highest-level customers according to the account association table, so as to construct a customer association table of each of the above-mentioned fund pool products with the highest-level customer as the vertex, wherein the above-mentioned fund pool product represents a fund pool product in the corporate banking business scenario, the above-mentioned account association table includes N-level accounts, the first-level account is the highest-level account, the N-level account is the subordinate account of the N-1-level account, the above-mentioned customer association table includes N-level customers, the first-level customer is the above-mentioned highest-level customer, the N-level customer is the subordinate customer of the N-1-level customer, and N≥2;

[0102] A locking unit 72, configured to perform a loading process on the data of the old system according to the above-mentioned customer association table to obtain a migration data set, and serially lock each of the above-mentioned migration data sets one by one using a fund pool contract to obtain a locked migration data set;

[0103] A migration unit 73, configured to migrate the above-mentioned locked migration data set to the new system in units of the customers in the above-mentioned customer association table.

[0104] In this embodiment, the first construction unit is configured to construct an account association table of the fund pool products of the old system, divide the customers of the old system into the highest-level customers and the subordinate customers of the highest-level customers according to the account association table, so as to construct a customer association table of each of the above-mentioned fund pool products with the highest-level customer as the vertex, wherein the above-mentioned fund pool product represents a fund pool product in the corporate banking business scenario, the above-mentioned account association table includes N-level accounts, the first-level account is the highest-level account, the N-level account is the subordinate account of the N-1-level account, the above-mentioned customer association table includes N-level customers, the first-level customer is the above-mentioned highest-level customer, the N-level customer is the subordinate customer of the N-1-level customer, and N≥2; the locking unit is configured to perform a loading process on the data of the old system according to the above-mentioned customer association table to obtain a migration data set, and serially lock each of the above-mentioned migration data sets one by one using a fund pool contract to obtain a locked migration data set; the migration unit is configured to migrate the above-mentioned locked migration data set to the new system in units of the customers in the above-mentioned customer association table.

[0105] As an alternative solution, the device further includes a first determination unit and a second construction unit. The first determination unit is configured to determine, during the process of constructing a customer association table with the above-mentioned top-level customer as the vertex for each of the above-mentioned fund pool products, multiple above-mentioned top-level customers of the above-mentioned subordinate customers who are involved in multiple above-mentioned fund pool products when the subordinate customers of the above-mentioned top-level customer are involved in multiple above-mentioned fund pool products. The second construction unit is configured to construct a virtual top-level customer as the vertex of the multiple above-mentioned top-level customers of the above-mentioned subordinate customers, and construct the above-mentioned customer association table across fund pools with the above-mentioned virtual top-level customer as the vertex, where the above-mentioned cross-fund pool is a fund pool involving multiple above-mentioned fund pool products. This solves the problem of how to ensure data consistency and business continuity when migrating data of fund pool customers and cross-fund pool customers to a new system in the corporate cash management business scenario of a bank. By introducing the concept of "vertex customers" and constructing the association relationship between vertex customers and customers to be associated, it is possible to achieve the goal of serializing and importing associated customer data into the target system without relying on an external transaction framework, ensuring data consistency and integrity. This not only ensures the efficiency of data migration, meets performance requirements, but also guarantees the continuity and stability of the business before and after migration, providing solid technical support for the smooth switching of the bank's core system. This solves the problems of complex data migration processing logic and poor process reusability in the existing data migration solutions between old and new systems.

[0106] As an alternative solution, the device further includes a first detection unit, which is configured to stop the current and subsequent locking operations and perform an unlocking operation on the data in the migration data set that has been successfully locked when it detects that the data locking for any customer in the migration data set fails during the process of serially and individually locking the above-mentioned migration data set using a fund pool contract.

[0107] As an alternative solution, the device further includes a second detection unit, which is configured to stop the data migration for the current customer and perform deletion processing and rollback processing on the data in the locked migration data set that has been successfully migrated from the new system when it detects that the data migration for any customer in the locked migration data set shows data migration failure during the process of migrating the above-mentioned locked migration data set to the new system in units of customers in the above-mentioned customer association table, where the above-mentioned data migration failure includes data verification exceptions and system network exceptions.

[0108] An alternative solution is that the device further includes a marking processing unit and a transaction detection unit. The marking processing unit is configured to perform a marking process on the migration data set by using global routing after loading the data of the old system according to the above-mentioned customer association table to obtain a migration data set, so as to set the status of each customer in the migration data set to the pre-migration status, thereby obtaining a pre-migration data set. The transaction detection unit is configured to perform transaction detection on the pre-migration data set to determine that no transaction operation has occurred for each of the customers corresponding to the pre-migration data set before the locking operation.

[0109] An alternative solution is that the device further includes a third detection unit, which is configured to, during the process of performing transaction detection on the pre-migration data set, stop performing transaction detection on the pre-migration data set when it detects that a transaction operation has occurred for the target customer corresponding to the pre-migration data set, and resume performing the above-mentioned transaction detection process on the pre-migration data set until the target customer completes the above-mentioned transaction operation.

[0110] An alternative solution is that the device further includes an unlocking operation unit, which is configured to perform an unlocking operation on the locked migration data set after migrating the locked migration data set to the new system, and when it detects that the locked migration data set has been completely migrated to the new system, so that the customers corresponding to the locked migration data set can perform transaction operations.

[0111] The device for ensuring data consistency during the switching process between the old and new systems includes a processor and a memory. The above-mentioned first construction unit, locking unit, migration unit, etc. are all stored in the memory as program units, and the corresponding functions are implemented by the processor executing the program units stored in the memory. The above-mentioned modules are all located in the same processor; alternatively, the above-mentioned various modules are separately located in different processors in any combination form.

[0112] The processor contains a kernel, and the kernel is used to retrieve the corresponding program units from the memory. One or more kernels can be set, and by adjusting the kernel parameters, the problems of complex migration data processing logic and poor process reusability in the existing data migration solutions between the old and new systems can be solved.

[0113] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of, for example, read-only memory (ROM) or flash memory (flash RAM), and the memory includes at least one storage chip.

[0114] An embodiment of the present invention provides a computer-readable storage medium, which includes a stored program. When the above-mentioned program runs, it controls the device where the computer-readable storage medium is located to execute the method for ensuring data consistency during the switching process between the old and new systems.

[0115] Specifically, the methods for ensuring data consistency during the switching process between the old and new systems include:

[0116] Step S201: Construct an account association table for the fund pool products of the old system. According to the account association table, divide the customers of the old system into the highest-level customers and the subordinate customers of the highest-level customers, so as to construct a customer association table for each of the above fund pool products with the highest-level customers as the vertices. Among them, the above fund pool products represent the fund pool products in the corporate banking business scenario. The above account association table includes N-level accounts, the first-level account is the highest-level account, the N-level account is the subordinate account of the (N - 1)-level account, the above customer association table includes N-level customers, the first-level customer is the above highest-level customer, the N-level customer is the subordinate customer of the (N - 1)-level customer, and N≥2;

[0117] Step S202: Perform a loading process on the data of the old system according to the above customer association table to obtain a migration data set, and use a fund pool contract to serially lock the above migration data set one by one to obtain a locked migration data set;

[0118] Step S203: Take the customers in the above customer association table as units and migrate the above locked migration data set to the new system.

[0119] An embodiment of the present invention provides a processor, and the above processor is used to run a program. Among them, when the above program runs, it executes the method for ensuring data consistency during the switching process between the old and new systems.

[0120] Specifically, the methods for ensuring data consistency during the switching process between the old and new systems include:

[0121] Step S201: Construct an account association table for the fund pool products of the old system. According to the account association table, divide the customers of the old system into the highest-level customers and the subordinate customers of the highest-level customers, so as to construct a customer association table for each of the above fund pool products with the highest-level customers as the vertices. Among them, the above fund pool products represent the fund pool products in the corporate banking business scenario. The above account association table includes N-level accounts, the first-level account is the highest-level account, the N-level account is the subordinate account of the (N - 1)-level account, the above customer association table includes N-level customers, the first-level customer is the above highest-level customer, the N-level customer is the subordinate customer of the (N - 1)-level customer, and N≥2;

[0122] Step S202: Perform a loading process on the data of the old system according to the above customer association table to obtain a migration data set, and use a fund pool contract to serially lock the above migration data set one by one to obtain a locked migration data set;

[0123] Step S203: Taking the customers in the above customer association table as units, migrate the above locked migration dataset to the new system.

[0124] An embodiment of the present invention provides an electronic device, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it implements at least the following steps:

[0125] Step S201: Construct an account association table for the fund pool products of the old system, and divide the customers of the old system into top-level customers and the subordinate customers of the top-level customers according to the account association table, so as to construct a customer association table with the top-level customers as vertices for each of the above fund pool products. Among them, the above fund pool products represent the fund pool products in the corporate banking business scenario. The above account association table includes N-level accounts, the first-level account is the top-level account, the N-level account is the subordinate account of the (N-1)-level account, the above customer association table includes N-level customers, the first-level customer is the above top-level customer, the N-level customer is the subordinate customer of the (N-1)-level customer, and N≥2;

[0126] Step S202: Perform loading processing on the data of the old system according to the above customer association table to obtain a migration dataset, and serially lock each of the above migration datasets using a fund pool contract to obtain a locked migration dataset;

[0127] Step S203: Taking the customers in the above customer association table as units, migrate the above locked migration dataset to the new system.

[0128] The device in this article can be a server, a PC, a PAD, a mobile phone, etc.

[0129] The present application also provides a computer program product, which, when executed on a data processing device, is adapted to execute a program initialized with at least the following method steps:

[0130] Step S201: Construct an account association table for the fund pool products of the old system, and divide the customers of the old system into top-level customers and the subordinate customers of the top-level customers according to the account association table, so as to construct a customer association table with the top-level customers as vertices for each of the above fund pool products. Among them, the above fund pool products represent the fund pool products in the corporate banking business scenario. The above account association table includes N-level accounts, the first-level account is the top-level account, the N-level account is the subordinate account of the (N-1)-level account, the above customer association table includes N-level customers, the first-level customer is the above top-level customer, the N-level customer is the subordinate customer of the (N-1)-level customer, and N≥2;

[0131] Step S202: Load and process the data of the old system according to the above customer association table to obtain a migration data set, and serially lock each data in the migration data set one by one using the fund pool contract to obtain a locked migration data set;

[0132] Step S203: Take the customers in the above customer association table as units and migrate the above locked migration data set to the new system.

[0133] Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device. They can be concentrated on a single computing device or distributed on a network composed of multiple computing devices. They can be implemented by program codes executable by the computing device. Thus, they can be stored in a storage device and executed by the computing device. And in some cases, the steps shown or described herein can be executed in a different order, or they can be separately made into individual integrated circuit modules, or multiple modules or steps among them can be made into a single integrated circuit module for implementation. In this way, the present invention is not limited to any specific combination of hardware and software.

[0134] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0135] The present application is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processors of general-purpose computers, special-purpose computers, embedded processors, or other programmable data processing devices to generate a machine, such that the instructions executed by the processors of the computer or other programmable data processing devices generate means for implementing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0136] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including instruction means that implement the functions specified in the flow Figure 1one or more processes and / or blocks Figure 1 the functions specified in one or more blocks.

[0137] These computer program instructions may also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process. Thus, the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one Figure 1 one or more processes and / or blocks Figure 1 or more processes and / or blocks and / or the functions specified in one or more blocks.

[0138] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0139] The memory may include non-permanent memory in the computer-readable medium, in the form of random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.

[0140] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can store information by any method or technology. The information may be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.

[0141] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, commodity or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, commodity or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the existence of additional identical elements in the process, method, commodity or device comprising the element.

[0142] The above are only the preferred embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and modifications. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the protection scope of the present application.

Claims

1. A method for ensuring data consistency during the switching process between old and new systems, characterized in that, Including: Construct an account association table for the fund pool products of the old system. Classify the customers of the old system into top-level customers and their subordinate customers according to the account association table, so as to construct a customer association table for each of the fund pool products with the top-level customer as the vertex. Among them, the fund pool product represents the fund pool product in the corporate banking business scenario of the bank. The account association table includes N-level accounts, the first-level account is the top-level account, and the N-level account is the subordinate account of the (N - 1)-level account. The customer association table includes N-level customers, the first-level customer is the top-level customer, and the N-level customer is the subordinate customer of the (N - 1)-level customer. N≥2； Perform a loading process on the data of the old system according to the customer association table to obtain a migration data set, and serially lock each of the migration data sets one by one using a fund pool contract to obtain a locked migration data set. Migrate the locked migration data set to the new system in units of the customers in the customer association table.

2. The method according to claim 1, characterized in that, During the process of constructing a customer association table for each of the fund pool products with the top-level customer as the vertex, the method further includes: In the case that the subordinate customers of the top-level customer are involved in multiple of the fund pool products, determine multiple top-level customers of the subordinate customers involved in multiple of the fund pool products. Construct a virtual top-level customer as the vertex of the multiple top-level customers of the subordinate customers, and construct a cross-fund-pool customer association table with the virtual top-level customer as the vertex, where the cross-fund-pool is a fund pool involving multiple of the fund pool products.

3. The method according to claim 1, wherein During the process of serially locking each of the migration data sets one by one using a fund pool contract, the method further includes: In the case that it is detected that the data locking of any customer in the migration data set fails, stop the current and subsequent locking operations, and perform an unlocking operation on the data in the migration data set that has been successfully locked.

4. The method according to claim 1, characterized in that, During the process of migrating the locked migration data set to the new system in units of the customers in the customer association table, the method further includes: In the case that it is detected that the data migration of any customer in the locked migration data set shows a data migration failure, stop the data migration of the current customer, and perform a deletion process and a rollback process on the data in the locked migration data set that has been successfully migrated from the new system, where the data migration failure includes data verification exceptions and system network exceptions.

5. The method according to claim 1, wherein After performing a loading process on the data of the old system according to the customer association table to obtain a migration data set, the method further includes: Perform a tagging process on the migration data set using global routing to set the status of each customer in the migration data set to the pre-migration status to obtain a pre-migration data set. Perform a transaction detection on the pre-migration data set to determine that no transaction operations have occurred for each of the customers corresponding to the pre-migration data set before the locking operation.

6. The method according to claim 5, wherein During the process of performing a transaction detection on the pre-migration data set, the method further includes: When it is detected that a target customer corresponding to the pre-migration data set has a transaction operation, stop transaction detection for the pre-migration data set until the target customer completes the transaction operation, and then re-perform transaction detection processing on the pre-migration data set.

7. The method according to claim 1, wherein After migrating the locked migration data set to the new system, the method further includes: When it is detected that the locked migration data set has been completely migrated to the new system, perform an unlocking operation on the locked migration data set so that the customers corresponding to the locked migration data set can perform transaction operations.

8. An apparatus for ensuring data consistency during the switching process between an old system and a new system, characterized in that, Includes: A first construction unit for constructing an account association table of the fund pool products in the old system, classifying the customers in the old system into the highest-level customers and the subordinate customers of the highest-level customers according to the account association table, so as to construct a customer association table of each of the fund pool products with the highest-level customer as the vertex. The fund pool product represents a fund pool product in the corporate banking business scenario. The account association table includes N-level accounts, the first-level account is the highest-level account, and the N-level account is the subordinate account of the N-1 level account. The customer association table includes N-level customers, the first-level customer is the highest-level customer, and the N-level customer is the subordinate customer of the N-1 level customer, where N≥2; A locking unit for loading the data in the old system according to the customer association table to obtain a migration data set, and sequentially locking the migration data set one by one in series using a fund pool contract to obtain a locked migration data set; A migration unit for migrating the locked migration data set to the new system in units of the customers in the customer association table.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, where, when the program runs, it controls the device where the computer-readable storage medium is located to execute the method for ensuring data consistency during the new and old system switching process according to any one of claims 1 to 7.

10. An electronic device, characterized in that, Includes: One or more processors, a memory, and one or more programs, where the one or more programs are stored in the memory and are configured to be executed by the one or more processors. The one or more programs include a method for executing the new and old system switching process for ensuring data consistency according to any one of claims 1 to 7.

Images