A Method and System for Runtime Migration of Customer Data

Abstract

The present invention relates to the technical field of data migration, and particularly to a method and system for migrating customer data during runtime, including determining whitelist customer data and migrating the whitelist customer data from a centralized architecture system to a distributed system according to rules; when customer data merging occurs, judging the application scenario; when it belongs to the application scenario where customer data is merged from an old centralized architecture system to an old distributed system or customer data is merged from a new centralized architecture system to a new distributed system, performing normal customer data merging processing; when it belongs to the application scenario where customer data is merged from an old centralized architecture system to a new distributed system or customer data is merged from a new centralized architecture system to an old distributed system, updating the whitelist customer data and performing normal customer data merging processing. This method can achieve parallel operation of the old and new systems, ensure the stability of system functions, and at the same time verify some data.

Description

Technical Field

[0001] The present invention relates to the field of electronic finance technology, and in particular, to a method and system for migrating customer data during runtime. Background Art

[0002] In the prior art, most systems are undergoing the process of switching and transformation from a centralized architecture system to a distributed architecture system, and it is necessary to migrate the existing data in the old system to the new system. In order to ensure the stability during the system switching process, generally, a small amount of data is migrated in the form of a whitelist first, and then the scope of the whitelist is gradually expanded until the complete data migration is gradually completed. The customer data of the centralized architecture system generally exists in a single file or database table. The process of switching to the distributed architecture includes the process of splitting the customer data in the single file or database table into horizontally distributed database tables according to certain rules. During this process, the integrity and accuracy of the customer data need to be ensured.

[0003] The conventional method for migrating customer data during runtime across systems and databases is to import the existing data in the old system into the new system database in batches. At this time, there are four scenarios when customer merging occurs: customer data is merged from the old system to the old system, customer data is merged from the new system to the new system, customer data is merged from the old system to the new system, and customer data is merged from the new system to the old system. For the latter two types of cross-system and cross-database data, the prior art cannot achieve the merging of customer data. To solve the problems such as data migration consistency in this scenario, the present invention proposes a stable and reliable method for migrating customer data, which can ensure that during the migration process, when customer merging occurs under the parallel operation of the old and new systems, the customer data that undergoes merging can be migrated normally and completely. Summary of the Invention

[0004] To solve the deficiencies of the prior art, the present invention proposes a method and system for migrating customer data during runtime.

[0005] To achieve the above objectives, the technical solutions adopted by the present invention include:

[0006] A method for migrating customer data during runtime, characterized by comprising the following steps:

[0007] Step S1, determining the whitelist customer data, and migrating the whitelist customer data from the centralized architecture system to the distributed system according to the rules;

[0008] Step S2, when customer data merging occurs, determining whether it belongs to the application scenarios of customer data being merged from the old centralized architecture system to the old distributed system, customer data being merged from the new centralized architecture system to the new distributed system, customer data being merged from the old centralized architecture system to the new distributed system, or customer data being merged from the new centralized architecture system to the old distributed system;

[0009] Step S3: When it belongs to the application scenario where customer data is merged from the old centralized architecture system to the old distributed system or customer data is merged from the new centralized architecture system to the new distributed system, perform normal customer data merging processing; when it belongs to the application scenario where customer data is merged from the old centralized architecture system to the new distributed system or customer data is merged from the new centralized architecture system to the old distributed system, update the whitelist customer data and perform normal customer data merging processing;

[0010] Step S4: Gradually expand the whitelist customer data until the full-system data information migration is achieved.

[0011] Furthermore, Step S1 preferably further includes gradually migrating the whitelist customer data according to regional divisions.

[0012] Furthermore, in Step S3, when it belongs to the application scenario where customer data is merged from the old centralized architecture system to the new distributed system or customer data is merged from the new centralized architecture system to the old distributed system, it preferably further includes merging the whitelist customer data A into the corresponding non-whitelist customer data B or merging the non-whitelist customer data B into the corresponding whitelist customer data A, where the whitelist customer data A is any data in the whitelist customer data and the non-whitelist customer data B is any data in the non-whitelist data.

[0013] Furthermore, in Step S3, when it belongs to the application scenario where customer data is merged from the old centralized architecture system to the new distributed system or customer data is merged from the new centralized architecture system to the old distributed system, it preferably further includes:

[0014] Delete the whitelist customer data A;

[0015] Delete the whitelist customer data A corresponding to the migration in the distributed system;

[0016] Perform normal customer data merging processing in the centralized architecture system.

[0017] Furthermore, Step S3 preferably further includes, when the customer data needs to be chain-maintained, processing it using the customer data merging chain processing method.

[0018] Furthermore, Step S3 preferably further includes storing the customer data merging operation records in the same array, traversing the array, updating the records already stored in the array, and continuing to scan the array until the array to be stored is empty, and then saving the records.

[0019] Furthermore, Step S4 further includes, after the distributed system is verified to be correct, gradually expanding the whitelist customer data until the full-system data information migration is achieved.

[0020] The present invention also relates to a customer data runtime migration system, which is characterized by including:

[0021] A data migration module, configured to determine whitelist customer data and migrate the whitelist customer data from a centralized architecture system to a distributed system according to rules;

[0022] A judgment module, when customer data merging occurs, configured to judge whether it belongs to application scenarios where customer data is merged from an old centralized architecture system to an old distributed system, customer data is merged from a new centralized architecture system to a new distributed system, customer data is merged from an old centralized architecture system to a new distributed system, or customer data is merged from a new centralized architecture system to an old distributed system;

[0023] A data merging processing module, when it belongs to application scenarios where customer data is merged from an old centralized architecture system to an old distributed system or customer data is merged from a new centralized architecture system to a new distributed system, configured to perform normal customer data merging processing; when it belongs to application scenarios where customer data is merged from an old centralized architecture system to a new distributed system or customer data is merged from a new centralized architecture system to an old distributed system, update the whitelist customer data and perform normal customer data merging processing;

[0024] An operation module, configured to gradually expand the whitelist customer data until the full amount of system data information migration is achieved.

[0025] The present invention also relates to a computer-readable storage medium, which is characterized in that a computer program is stored on the storage medium, and when the computer program is executed by a processor, the above method is implemented.

[0026] The present invention also relates to an electronic device, which is characterized by including a processor and a memory;

[0027] The memory is used to store operation instructions;

[0028] The processor is configured to execute the above method by calling the said operation instructions.

[0029] A computer program product, including a computer program and / or instructions, which is characterized in that when the computer program and / or instructions are executed by a processor, the steps of the above method are implemented.

[0030] The beneficial effects of the present invention are:

[0031] The customer data runtime migration method and system of the present invention are mainly used to solve the problem of difficult customer data migration during the parallel operation of the old and new systems when switching from a centralized architecture system to a distributed architecture system. This method can achieve the parallel operation of the old and new systems, ensure the stability of the system functions, and at the same time verify some data; and maintain the data in a chained merging manner, which can avoid problems such as customer data errors caused by updating records; at the same time, a white list switching mechanism is adopted to gradually migrate the data to ensure the stability of the system and the integrity of the data. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 It is a schematic flow chart of the customer data runtime migration method of the present invention.

[0033] Figure 2 It is a schematic structural diagram of the customer data runtime migration system of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0034] In the present invention, customer merging means that the same customer may have multiple different numbers in the customer system, but only the customer information with one number is completely correct or complete. Delete the incorrect or incomplete customer numbers and merge them into the same customer number.

[0035] To better understand the content of the present invention, it will be described in detail in combination with the drawings and embodiments.

[0036] The first aspect of the present invention relates to a customer data runtime migration method with a step flow as Figure 1 shown, including:

[0037] Step S1: Determine the white list customer data and migrate the white list customer data from the centralized architecture system to the distributed system according to the rules;

[0038] Step S2: When customer data merging occurs, determine whether it belongs to the application scenarios of customer data merging from the old centralized architecture system to the old distributed system, customer data merging from the new centralized architecture system to the new distributed system, customer data merging from the old centralized architecture system to the new distributed system, or customer data merging from the new centralized architecture system to the old distributed system;

[0039] Step S3: When it belongs to the application scenarios of customer data merging from the old centralized architecture system to the old distributed system or customer data merging from the new centralized architecture system to the new distributed system, perform normal customer data merging processing; when it belongs to the application scenarios of customer data merging from the old centralized architecture system to the new distributed system or customer data merging from the new centralized architecture system to the old distributed system, update the white list customer data and perform normal customer data merging processing;

[0040] Step S4: Gradually expand the whitelist customer data until the migration of all system data information is achieved.

[0041] Exemplarily, step S1 is preferably to gradually migrate the whitelist customer data according to regional divisions.

[0042] Exemplarily, in step S3, when it belongs to the application scenario where customer data is merged from an old centralized architecture system to an old distributed system or customer data is merged from a new centralized architecture system to a new distributed system, and customer data A needs to be merged into customer data B in the customer merging scenario, first determine whether customer data A is within the scope of the whitelist customer data, and then determine whether customer data B is within the scope of the whitelist customer data; if both customer data A and customer data B are within the scope of the whitelist customer data, then perform a normal customer merging operation to merge customer data A into customer data B; if both customer data A and customer data B are not within the scope of the whitelist customer data, then a normal customer merging operation can also be performed to merge customer data A into customer data B. Among them, whitelist customer data A is any data in the whitelist customer data, and non-whitelist data B is any data in the non-whitelist data.

[0043] Further, in step S3, when it belongs to the application scenario where customer data is merged from an old centralized architecture system to a new distributed system or customer data is merged from a new centralized architecture system to an old distributed system, it also includes merging whitelist customer data A into its corresponding non-whitelist customer data B or merging non-whitelist data B into its corresponding whitelist customer data A, where whitelist customer data A is any data in the whitelist customer data, and non-whitelist customer data B is any data in the non-whitelist data.

[0044] Exemplarily, in step S3, when it belongs to the application scenario where customer data is merged from an old centralized architecture system to a new distributed system or customer data is merged from a new centralized architecture system to an old distributed system, it also includes:

[0045] Delete whitelist customer data A;

[0046] Delete the corresponding migrated whitelist customer data A in the distributed system;

[0047] Perform normal customer data merging processing in the centralized architecture system.

[0048] Optionally, when the customer data needs to be maintained in a chain, a customer data merging chain processing method is adopted for processing.

[0049] Exemplarily, the customer merging chain processing method described in the present invention includes storing the customer data merging operation records into the same array. For example, the records already stored in the array are A→B, and the record to be stored in the array is B→C. When the above chain maintenance is required, traverse the array, update the records already stored in the array, update from A→B to A→B→C, and continue to scan the array until the data to be stored is empty, then store the record in the array, save the record, and finally the customer merging chain processing ends. Then, sequentially execute the customer data merging process. Herein, A, B, and C respectively represent customer data information. Exemplarily, A→B means that customer data A is merged into its corresponding customer data B.

[0050] Through the above merging chain processing method, the following problems can be better avoided during customer data merging: merging customer data A into customer data B, and at the same time merging customer data B into customer data C. In the actual operation process, if the operation of merging customer data B into customer data C is executed first, then when executing the operation of merging customer data A into customer data B, it will fail because customer data B cannot be found.

[0051] Optionally, step S4 further includes gradually expanding the whitelist customer data until the full amount of system data information migration is achieved after the distributed system runs stably for a period of time or is verified without errors.

[0052] Exemplarily, through the above method, the migration of customer data in one province can be expanded to two provinces until it covers all customer data in the country.

[0053] The customer data runtime migration method and system described in the present invention are mainly used to solve the problem of difficult customer data migration during the parallel operation of the old and new systems when switching from a centralized architecture system to a distributed architecture system. This method can realize the parallel operation of the old and new systems, ensure the stability of the system functions, and at the same time verify some data; and maintain the data in a chained merging manner, which can avoid problems such as customer data errors caused by updating records; at the same time, adopt the whitelist switching mechanism to gradually perform data migration to ensure the stability of the system and the integrity of the data.

[0054] On the other hand, the present invention also relates to a customer data runtime migration system, the structure of which is as Figure 2 shown, including:

[0055] A data migration module, used to determine the whitelist customer data and migrate the whitelist customer data from the centralized architecture system to the distributed system according to the rules;

[0056] A judgment module, which is used to judge whether it belongs to the application scenarios of merging customer data from an old centralized architecture system to an old distributed system, merging customer data from a new centralized architecture system to a new distributed system, merging customer data from an old centralized architecture system to a new distributed system, or merging customer data from a new centralized architecture system to an old distributed system when customer data merging occurs;

[0057] A data merging processing module, which is used to perform normal customer data merging processing when it belongs to the application scenarios of merging customer data from an old centralized architecture system to an old distributed system or merging customer data from a new centralized architecture system to a new distributed system; when it belongs to the application scenarios of merging customer data from an old centralized architecture system to a new distributed system or merging customer data from a new centralized architecture system to an old distributed system, update the whitelist customer data and perform normal customer data merging processing;

[0058] An operation module, which is used to gradually expand the whitelist customer data until the full amount of system data information migration is achieved.

[0059] By using this system, the above-mentioned arithmetic processing method can be executed and the corresponding technical effects can be achieved.

[0060] An embodiment of the present invention also provides a computer-readable storage medium capable of implementing all steps in the method in the above embodiment. A computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, all steps of the method in the above embodiment are implemented.

[0061] An embodiment of the present invention also provides an electronic device for executing the above method. As an implementation device of this method, the electronic device at least has a processor and a memory. In particular, the memory stores the data and related computer programs required for executing the method, such as etc., and all steps of the method are implemented by the processor calling the data and programs in the memory, and the corresponding technical effects are obtained.

[0062] Preferably, the electronic device may include a bus architecture. The bus may include any number of interconnected buses and bridges, and the bus links various circuits including one or more processors and memories together. The bus can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art, so they will not be further described herein. The bus interface provides an interface between the bus and the receiver and transmitter. The receiver and transmitter can be the same element, that is, a transceiver, which provides a unit for communicating with various other systems on the transmission medium. The processor is responsible for managing the bus and general processing, and the memory can be used to store the data used by the processor when executing operations.

[0063] Additionally, the electronic device may further include components such as a communication module, an input unit, an audio processor, a display, a power supply, etc. The processor (or controller, operation control) used may include a microprocessor or other processor devices and / or logic devices. The processor receives inputs and controls the operations of the various components of the electronic device; the memory may be one or more of a buffer, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory, or other suitable devices, which can store the above relevant data information. In addition, it can also store programs for executing relevant information, and the processor can execute the programs stored in the memory to achieve information storage or processing, etc.; the input unit is used to provide inputs to the processor, for example, it can be a button or a touch input device; the power supply is used to provide power to the electronic device; the display is used to display display objects such as images and texts, for example, it can be an LCD display. The communication module is a transmitter / receiver that sends and receives signals via an antenna. The communication module (transmitter / receiver) is coupled to the processor to provide input signals and receive output signals, which can be the same as in the case of a conventional mobile communication terminal. Based on different communication technologies, multiple communication modules can be provided in the same electronic device, such as a cellular network module, a Bluetooth module, and / or a wireless local area network module, etc. The communication module (transmitter / receiver) is also coupled to the speaker and the microphone via the audio processor to provide audio output via the speaker and receive audio input from the microphone, so as to achieve normal telecommunication functions. The audio processor may include any suitable buffer, decoder, amplifier, etc. Additionally, the audio processor is also coupled to the central processor, so that it is possible to record on the device through the microphone and play the sounds stored on the device through the speaker.

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

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

[0066] 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 produce a manufactured article including an instruction system that implements the functions specified in one or more flows Figure 1 one or more flows and / or blocks Figure 1 or one or more blocks.

[0067] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more flows Figure 1 one or more flows and / or blocks Figure 1 or one or more blocks. Although the preferred embodiments of the present invention have been described, those skilled in the art can make additional changes and modifications to these embodiments once they learn the basic creative concepts. Therefore, the appended claims are intended to be construed to include the preferred embodiments and all changes and modifications falling within the scope of the present invention.

[0068] The above is only the preferred specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed by the present invention should be covered by the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

1. A method for runtime migration of customer data, characterized in that, it includes the following steps: Step S1: Determine the whitelist customer data, and migrate the whitelist customer data from the centralized architecture system to the distributed system according to the rules; Step S2: When customer data merging occurs, determine whether it belongs to the application scenarios of customer data merging from the old centralized architecture system to the old distributed system, customer data merging from the new centralized architecture system to the new distributed system, customer data merging from the old centralized architecture system to the new distributed system, or customer data merging from the new centralized architecture system to the old distributed system; Step S3: When it belongs to the application scenarios of customer data merging from the old centralized architecture system to the old distributed system or customer data merging from the new centralized architecture system to the new distributed system, perform normal customer data merging processing; when it belongs to the application scenarios of customer data merging from the old centralized architecture system to the new distributed system or customer data merging from the new centralized architecture system to the old distributed system, update the whitelist customer data and perform normal customer data merging processing; Step S4: Gradually expand the whitelist customer data until the full-system data information migration is achieved; The update of the whitelist customer data includes: Delete the whitelist customer data A; Delete the corresponding migrated whitelist customer data A in the distributed system; Perform normal customer data merging processing in the centralized architecture system; Wherein, merging means that when the same customer has multiple different numbers in the customer system, only the customer information with one number is completely correct or complete, delete the incorrect or incomplete customer numbers, and merge them into the same customer number.

2. The method according to claim 1, characterized in that, Step S1 further includes gradually migrating the whitelist customer data according to the regional division.

3. The method according to claim 1, characterized in that, In step S3, when it belongs to the application scenarios of customer data merging from the old centralized architecture system to the new distributed system or customer data merging from the new centralized architecture system to the old distributed system, it further includes merging the whitelist customer data A into its corresponding non-whitelist customer data B or merging the non-whitelist customer data B into its corresponding whitelist customer data A, wherein, the whitelist customer data A is any data in the whitelist customer data, and the non-whitelist customer data B is any data in the non-whitelist data.

4. The method according to claim 1, characterized in that, Step S3 further includes when the customer data needs to be chain-maintained, adopting the customer data merging chain processing method for processing.

5. The method according to claim 1, characterized in that, Step S3 further includes storing the customer data merging operation records into the same array, traversing the array, updating the records stored in the array, and continuing to scan the array until the array to be stored is empty, and then saving the records.

6. The method according to any one of claims 1 to 5, characterized in that, Step S4 further includes when the distributed system is verified to be correct, gradually expanding the whitelist customer data until the full-system data information migration is achieved.

7. A customer data runtime migration system, characterized in that, it includes: A data migration module, which is used to determine the whitelist customer data and migrate the whitelist customer data from the centralized architecture system to the distributed system according to the rules; A judgment module, which is used to judge whether it belongs to the application scenarios of customer data merging from the old centralized architecture system to the old distributed system, customer data merging from the new centralized architecture system to the new distributed system, customer data merging from the old centralized architecture system to the new distributed system, or customer data merging from the new centralized architecture system to the old distributed system when customer data merging occurs; A data merging processing module, which is used to perform normal customer data merging processing when it belongs to the application scenarios of customer data merging from the old centralized architecture system to the old distributed system or customer data merging from the new centralized architecture system to the new distributed system; when it belongs to the application scenarios of customer data merging from the old centralized architecture system to the new distributed system or customer data merging from the new centralized architecture system to the old distributed system, update the whitelist customer data and perform normal customer data merging processing; An operation module, which is used to gradually expand the whitelist customer data until the full volume of system data information migration is achieved; The updating of the whitelist customer data includes: Deleting the whitelist customer data A; Deleting the corresponding migrated whitelist customer data A in the distributed system; Performing normal customer data merging processing in the centralized architecture system; Wherein, merging means that when there are multiple different numbers of the same customer in the customer system, only the customer information of one number is completely correct or complete, deleting the incorrect or incomplete customer numbers and merging them into the same customer number.

8. A computer-readable storage medium, characterized in that, a computer program is stored on the storage medium, and when the computer program is executed by a processor, the method described in any one of claims 1 to 6 is implemented.

9. An electronic device, characterized in that, it includes a processor and a memory; The memory is used to store operation instructions; The processor is used to execute the method described in any one of claims 1 to 6 by calling the operation instructions.

10. A computer program product, including a computer program and / or instructions, characterized in that, when the computer program and / or instructions are executed by a processor, the steps of the method described in any one of claims 1 to 6 are implemented.

Images