Customer information merging method, merging device and business system

Abstract

The present application provides a customer information merging method, merging device and business system, the method comprising: obtaining a first customer number and a second customer number, the first customer number and the second customer number being different customer numbers of the same customer; migrating the first customer information to a data shard where the second customer information is located, the first customer information being customer information of the first customer number, and the second customer information being customer information of the second customer number; pre-merging the first customer information and the second customer information to obtain merged customer information; detecting whether the merged customer information meets regulatory requirements and business requirements; and if the merged customer information meets regulatory requirements and business requirements, determining that the second customer number is the merged customer number, and the merged customer information is the customer information of the merged customer number, thereby solving the problem in the prior art that the merging of customer information does not meet regulatory requirements and business requirements.

Description

Technical Field

[0001] The present application relates to the technical field of data migration, and in particular to a method for merging customer information, a merging device, a computer-readable storage medium, a processor, and a business system. Background Art

[0002] Currently, there are situations where the same customer uses different certificates to establish multiple customer numbers in the same bank. Due to regulatory requirements and the customer's own business needs, there is an objective need to merge the customer business data under one customer number into another customer number. This requirement involves migrating customers from the source database data shard to the new database data shard.

[0003] In the core systems of the industry that adopt a centralized architecture, the merging of customer business data and other operations occur in the same database, and there is no cross-database or even cross-physical machine situation. In the core systems of the distributed architecture, there is no description of this part of the function or technical solution in the publicly available information.

[0004] Commercial banks are migrating from centralized core systems to distributed core systems. Most distributed core systems are divided into databases and tables based on customer numbers. When a customer's identity or factors change, involving a change in the customer number, all customer data needs to be migrated from the old customer number to the database corresponding to the new customer number, and the corresponding business data needs to be merged.

[0005] The main disadvantages of the existing technical solutions are as follows:

[0006] (1) The centralized architecture is an account-level migration solution, not a customer-level solution. This design naturally leads to data inconsistencies after customer mergers, which affects customer experience and the difficulty of internal enterprise data governance.

[0007] (2) Lack of real-time customer merging solutions under distributed databases.

[0008] This invention patent aims to solve the overall migration of customer data between different databases and database shards in a distributed environment.

[0009] Currently, the centralized core system mainly adopts the following solutions when processing customer mergers:

[0010] Only the customer number of the account in the core system is changed, and the customer to whom the account belongs is logically changed. No changes are made to the media, contract and other information.

[0011] The above information disclosed in the background technology section is only used to enhance the understanding of the background technology of the technology described in this article. Therefore, the background technology may contain certain information that does not form the prior art known in this country for those skilled in the art. Summary of the invention

[0012] The main purpose of this application is to provide a customer information merging method, merging device, computer-readable storage medium, processor and business system to solve the problem in the prior art that customer information merging does not meet regulatory requirements and business requirements.

[0013] According to one aspect of an embodiment of the present invention, a method for merging customer information is provided, wherein a distributed database includes multiple data shards, and the data shards are used to store customer information corresponding to a customer number. The method includes: obtaining a first customer number and a second customer number, wherein the first customer number and the second customer number are different customer numbers of the same customer; migrating the first customer information to the data shard where the second customer information is located, wherein the first customer information is the customer information of the first customer number, and the second customer information is the customer information of the second customer number; pre-merging the first customer information and the second customer information to obtain merged customer information; detecting whether the merged customer information meets regulatory requirements and business requirements, wherein the regulatory requirements include requirements for prescribed limits and prescribed quantity restrictions, and the business requirements include requirements for not affecting business continuity; and determining, when the merged customer information meets regulatory requirements and business requirements, that the second customer number is the merged customer number, and the merged customer information is the customer information of the merged customer number.

[0014] Optionally, the method also includes: sending a notification when the merged customer information does not meet regulatory requirements and business requirements, wherein the notification is used to prompt the customers corresponding to the first customer number and the second customer number to handle target business, and the target business is the business corresponding to the change of customer information that does not meet regulatory requirements and business requirements.

[0015] Optionally, migrating the first customer information to the data shard where the second customer information is located includes: querying the data shard where the first customer information is located according to the first customer number to obtain the first data shard; reading the first customer information of the first data shard and generating a customer information file according to a naming convention; uploading the customer information file to a file system and obtaining file-related information, wherein the file-related information includes a file name and a file path; querying the data shard where the second customer information is located according to the second customer number to obtain the second data shard; downloading the customer information file according to the file-related information and storing it in the second data shard.

[0016] Optionally, detecting whether the merged customer information meets regulatory requirements and business requirements includes: if there is no violation information in the merged customer information and it does not affect business continuity, determining that the merged customer information meets regulatory requirements and business requirements, and the violation information is an information item that does not comply with the regulatory requirements; if there is violation information in the merged customer information and / or it affects business continuity, determining that the merged customer information does not meet regulatory requirements and business requirements.

[0017] Optionally, detecting whether the merged customer information meets regulatory requirements and business requirements includes: detecting whether the pricing of the same type of the first customer number and the second customer number is consistent, and obtaining a first detection result, the pricing including fee pricing and revenue pricing; detecting whether the number of media of the first customer number and the second customer number exceeds a first specified quantity limit, and obtaining a second detection result; detecting whether the sum of the number of accounts of the first customer number and the second customer number exceeds a second specified quantity limit, and obtaining a third detection result; determining whether the merged customer information meets regulatory requirements and business requirements based on the first detection result, the second detection result and the third detection result.

[0018] Optionally, before migrating the first customer information to the data shard where the second customer information is located, the method further includes: locking the first customer number and the second customer number so that the services of the first customer number and the second customer number are stopped.

[0019] Optionally, when the merged customer information meets regulatory requirements and business requirements, after determining that the merged customer number is the second customer number, the method further includes: unlocking the merged customer number so that the business of the merged customer number can be resumed.

[0020] According to another aspect of an embodiment of the present invention, a device for merging customer information is also provided, wherein the distributed database includes multiple data shards, and the data shards are used to store customer information corresponding to a customer number, and the device includes: an acquisition unit, used to acquire a first customer number and a second customer number, wherein the first customer number and the second customer number are different customer numbers of the same customer; a migration unit, used to migrate the first customer information to the data shard where the second customer information is located, wherein the first customer information is the customer information of the first customer number, and the second customer information is the customer information of the second customer number; a pre-merge unit, used to pre-merge the first customer information and the second customer information to obtain merged customer information; a detection unit, used to detect whether the merged customer information meets regulatory requirements and business requirements, wherein the regulatory requirements include requirements for prescribed limits and prescribed quantity restrictions, and the business requirements include requirements for not affecting business continuity; a merging unit, used to determine that the second customer number is a merged customer number and the merged customer information is the customer information of the merged customer number if the merged customer information meets regulatory requirements and business requirements.

[0021] According to yet another aspect of the embodiments of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes a stored program, wherein the program executes any one of the methods described.

[0022] According to yet another aspect of an embodiment of the present invention, a processor is provided, wherein the processor is used to run a program, wherein any one of the methods is executed when the program is run.

[0023] According to one aspect of an embodiment of the present invention, a business system is also provided, including a distributed database, one or more processors, a memory, a display device and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include methods for executing any one of the methods described.

[0024] In an embodiment of the present invention, in the method for merging the above-mentioned customer information, first, a first customer number and a second customer number are obtained, and the above-mentioned first customer number and the above-mentioned second customer number are different above-mentioned customer numbers of the same customer; then, the first customer information is migrated to the above-mentioned data shard where the second customer information is located, and the above-mentioned first customer information is the customer information of the above-mentioned first customer number, and the above-mentioned second customer information is the customer information of the above-mentioned second customer number; then, the above-mentioned first customer information and the above-mentioned second customer information are pre-merged to obtain merged customer information; then, it is detected whether the above-mentioned merged customer information meets regulatory requirements and business requirements, the above-mentioned regulatory requirements include requirements for prescribed limits and prescribed quantity restrictions, and the above-mentioned business requirements include requirements for not affecting business continuity; finally, when the above-mentioned merged customer information meets regulatory requirements and business requirements, it is determined that the above-mentioned second customer number is the merged customer number, and the above-mentioned merged customer information is the customer information of the above-mentioned merged customer number. The method performs a pre-merge before merging customer information to detect whether the merged customer information meets regulatory requirements and business requirements, and after ensuring that the merged customer information meets regulatory requirements and business requirements, determines the merged customer information as the customer information of the merged customer number, thereby avoiding the situation where the customer information of the merged customer number does not meet regulatory requirements and business requirements, and solves the problem in the prior art that the merger of customer information does not meet regulatory requirements and business requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The drawings constituting part of the present application are used to provide a further understanding of the present application. The exemplary embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0026] Figure 1 A flowchart showing a method for merging customer information according to an embodiment of the present application is shown;

[0027] Figure 2 A flowchart showing a method for merging customer information according to another specific embodiment of the present application is shown;

[0028] Figure 3 A flowchart of a method for merging customer information according to another specific embodiment of the present application is shown;

[0029] Figure 4 A schematic diagram of a device for merging customer information according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0030] It should be noted that the following detailed descriptions are illustrative and are intended to provide further explanation of the present application. Unless otherwise specified, all technical and scientific terms used herein have the same meanings as those commonly understood by those skilled in the art to which the present application belongs.

[0031] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments according to the present application. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should be understood that when the terms "comprise" and / or "include" are used in this specification, it indicates the presence of features, steps, operations, devices, components and / or combinations thereof.

[0032] It should be understood that when an element (such as a layer, film, region, or substrate) is described as being "on" another element, the element may be directly on the other element, or there may be intermediate elements. Moreover, in the specification and claims, when an element is described as being "connected" to another element, the element may be "directly connected" to the other element, or "connected" to the other element through a third element.

[0033] For the convenience of description, some nouns or terms involved in the embodiments of the present application are explained below:

[0034] Distributed database: A complete database is divided into multiple deployment nodes according to specific rules. Each node has a complete copy or a partial copy. Different nodes are connected to each other through a computer network to form a logically centralized and physically distributed large database.

[0035] Centralized architecture: computing, storage and other resources are all in a physically centralized hardware system, eliminating the need to deal with network partitioning issues;

[0036] Three elements of the customer: certificate type, certificate number, and customer name;

[0037] Core system: The account processing system in the commercial bank information system architecture is responsible for providing 7x24 hours basic account services for various businesses, such as interest calculation, payment, settlement, accounting, etc. It is the most basic and core part of banking business;

[0038] Global routing: Provides customer location functions for each application component of the core system, so that the application component can locate the corresponding database according to the customer number when processing transactions;

[0039] Combined trading platform: Through cross-system service orchestration and connection, it realizes the integration of short-process business and other functions, and realizes the decoupling of service consumers and service providers;

[0040] HDFS: The full name is Hadoop Distributed File System, a distributed file system designed to run on general-purpose hardware. It has the characteristics of high fault tolerance, high throughput, and support for large files.

[0041] Context: In programming, a memory area where data can be freely stored and accessed by the program.

[0042] As mentioned in the background technology, the customer information merging in the prior art does not meet regulatory requirements and business requirements. In order to solve the above problems, in a typical implementation of the present application, a customer information merging method, a merging device, a computer-readable storage medium, a processor and a business system are provided.

[0043] According to an embodiment of the present application, a method for merging customer information is provided.

[0044] Figure 1 is a flow chart of a method for merging customer information according to an embodiment of the present application. Figure 1 As shown, the method comprises the following steps:

[0045] Step S101, obtaining a first customer number and a second customer number, wherein the first customer number and the second customer number are different customer numbers of the same customer;

[0046] Step S102, migrating first customer information to the data shard where second customer information is located, the first customer information being customer information of the first customer number, and the second customer information being customer information of the second customer number;

[0047] Step S103, pre-merging the first customer information and the second customer information to obtain merged customer information;

[0048] Step S104, detecting whether the combined customer information meets regulatory requirements and business requirements, wherein the regulatory requirements include requirements for prescribed limits and prescribed quantity restrictions, and the business requirements include requirements for not affecting business continuity;

[0049] Step S105, when the combined customer information meets regulatory requirements and business requirements, determine that the second customer number is the combined customer number, and the combined customer information is the customer information of the combined customer number.

[0050] In the above-mentioned method for merging customer information, first, the first customer number and the second customer number are obtained, and the above-mentioned first customer number and the above-mentioned second customer number are different customer numbers of the same customer; then, the first customer information is migrated to the above-mentioned data shard where the second customer information is located, and the above-mentioned first customer information is the customer information of the above-mentioned first customer number, and the above-mentioned second customer information is the customer information of the above-mentioned second customer number; then, the above-mentioned first customer information and the above-mentioned second customer information are pre-merged to obtain merged customer information; then, it is detected whether the above-mentioned merged customer information meets regulatory requirements and business requirements, the above-mentioned regulatory requirements include requirements for prescribed limits and prescribed quantity restrictions, and the above-mentioned business requirements include requirements for not affecting business continuity; finally, when the above-mentioned merged customer information meets regulatory requirements and business requirements, it is determined that the above-mentioned second customer number is the merged customer number, and the above-mentioned merged customer information is the customer information of the above-mentioned merged customer number. The method performs a pre-merge before merging customer information to detect whether the merged customer information meets regulatory requirements and business requirements, and after ensuring that the merged customer information meets regulatory requirements and business requirements, determines the merged customer information as the customer information of the merged customer number, thereby avoiding the situation where the customer information of the merged customer number does not meet regulatory requirements and business requirements, and solves the problem in the prior art that the merger of customer information does not meet regulatory requirements and business requirements.

[0051] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0052] It should also be noted that the above-mentioned customer information includes routine business information and regulatory compliance information. The above-mentioned routine business information includes non-final information that must be transferred, such as account information, media information, contract information, contract information, and additional information that are in normal status; it also involves final information such as contract information, media information, account information, contract information, additional information, etc. that have been terminated, cancelled, and closed under the customer, as well as information such as registration books, transaction details, and transaction flows before the customer merger; the above-mentioned regulatory compliance information is mainly divided into two types. One is the relevant limit and quantity restriction information of customers stipulated by external supervision, such as the quantity restriction of Class I, II, and III accounts; the other is the customer's own limit control information, such as the annual cumulative limit for overseas cash withdrawals through self-service channels, the cumulative value of bilateral collection and payment amounts of Class III accounts, and the agent account opening information and the number of agent accounts opened under the migrated customer when he acts as an agent.

[0053] In one embodiment of the present application, the method further includes: in the case where the merged customer information does not meet regulatory requirements and business requirements, sending a notification, the notification being used to prompt the customers corresponding to the first customer number and the second customer number to handle the target business, the target business being the business corresponding to the change in customer information that does not meet regulatory requirements and business requirements. In this embodiment, after the pre-merger, when it is detected that the merged customer information, i.e., the merged regular business information and regulatory compliance information, does not meet regulatory requirements and business requirements, a notification needs to be sent to the customer to guide the customer to perform relevant compliance operations or business processing first, so as to ensure that the merged customer information meets regulatory requirements and business requirements.

[0054] In one embodiment of the present application, migrating the first customer information to the data slice where the second customer information is located includes: querying the data slice where the first customer information is located according to the first customer number to obtain the first data slice; reading the first customer information of the first data slice and generating a customer information file according to the naming specification; uploading the customer information file to the file system and obtaining file-related information, the file-related information including the file name and the file path; querying the data slice where the second customer information is located according to the second customer number to obtain the second data slice; downloading the customer information file according to the file-related information and storing it in the second data slice. In this embodiment, the customer merging process is divided into two parts: customer migration out and customer migration in. The customer migration task specifically includes: 1) Following the migration customer route: According to the migration customer route, go to the data shard where the migration customer is located; 2) Generate a migration file, that is, generate a customer information file: Generate a customer information file according to the naming specification for the data to be migrated according to the business, and the framework supports the data export function at the SQL configuration level; 3) Upload files: Provide tools, and the tools use HDFS tools or batch tools to upload customer information files to the HDFS file system; 4) Upload file-related information and customer information to the context: Add the generated file list to the batch context, and subsequent jobs can obtain file name, file path, account, contract and other information from the context to provide necessary information for subsequent jobs. The customer migration task specifically includes: 1) Migrating customer routing: Determine the data shard where the migrating customer is located based on the migrating customer information and perform the corresponding merge operation processing; 2) Downloading files: Obtain information such as the file name and file path from the context and download the file from HDFS; 3) Determine whether the migrating customer is in the same data shard as the migrating customer; (4) Business data merging: Determine whether to write the file data to a specific data shard based on the result of the previous step, and then read the file data to merge the business data based on the business logic. The above method is a data migration solution in a distributed environment, which realizes the migration of customer information data between different databases. Moreover, under the premise that the core system is an online transaction system with extremely high performance requirements, it realizes quasi-real-time overall customer information data migration, thereby improving the performance of the core system and customer experience.

[0055] It should be noted that the flexibly configured merge scheduling scheme can adjust and configure the various sub-jobs of customer merging in the scheduling platform according to changes in demand, making the entire customer merging function highly configurable. To add a new customer merging function, you only need to implement the framework layer data migration and data migration interfaces, and perform simple configuration to call up the customer merging of this business module. The entire customer merging function is also plug-and-play, and it also supports the removal of tasks on demand.

[0056] In one embodiment of the present application, detecting whether the above-mentioned merged customer information meets regulatory requirements and business requirements includes: if the above-mentioned merged customer information does not contain any illegal information and does not affect business continuity, determining that the above-mentioned merged customer information meets regulatory requirements and business requirements, and the above-mentioned illegal information is an information item that does not meet the above-mentioned regulatory requirements; if the above-mentioned merged customer information contains illegal information and / or affects business continuity, determining that the above-mentioned merged customer information does not meet regulatory requirements and business requirements. In this embodiment, Figure 2 As shown, the core process of customer merging in the system is customer pre-inspection and customer merging. Before customer merging, in order to ensure that the merged customer information after the customer merging step meets regulatory requirements and business requirements, a pre-merger is required to check the information items under the customer's name that will not meet regulatory requirements after the merger, as well as the business status of the migrating customer's in-transit business and other business items that affect business continuity after the merger, so as to avoid the customer information of the merged customer not meeting regulatory requirements or affecting business continuity.

[0057] In one embodiment of the present application, detecting whether the above-mentioned merged customer information meets regulatory requirements and business requirements includes: detecting whether the pricing of the same type of the above-mentioned first customer number and the above-mentioned second customer number is consistent, and obtaining a first detection result, and the above-mentioned pricing includes charging pricing and revenue pricing; detecting whether the number of media of the above-mentioned first customer number and the above-mentioned second customer number exceeds the first prescribed quantity limit, and obtaining a second detection result; detecting whether the sum of the number of accounts of the above-mentioned first customer number and the above-mentioned second customer number exceeds the second prescribed quantity limit, and obtaining a third detection result; determining whether the above-mentioned merged customer information meets regulatory requirements and business requirements based on the above-mentioned first detection result, the above-mentioned second detection result and the above-mentioned third detection result. In this embodiment, the customer merging operation can be initiated in parallel according to each business module, and the core process of the customer merging operation in the system is customer pre-inspection and customer merging. Figure 2 As shown, the two processes of customer pre-inspection and customer merging can be classified into various business modules such as pricing, media, and accounts according to the business type. Each module implements its own customer pre-inspection and customer merging processes according to its own business needs, which can be called on demand for batch scheduling. Among them, the business modules such as pricing, media, and accounts are called to perform customer pre-inspection to obtain the above-mentioned first test result, the above-mentioned second test result, and the above-mentioned third test result, so as to determine whether the above-mentioned merged customer information meets the regulatory requirements and business requirements.

[0058] In one embodiment of the present application, before migrating the first customer information to the data shard where the second customer information is located, the method further includes: locking the first customer number and the second customer number so that the services of the first customer number and the second customer number are stopped. Figure 3As shown, before the customer merging step is performed, the customer number needs to be locked to ensure that the subsequent steps are not interfered with. After the core system receives the customer locking request, the global routing marks the migrated and migrated customers. At this time, if there are related transactions involving two customers from other systems, the global routing will directly reject the transaction and return a prompt message "The customer has been locked".

[0059] In one embodiment of the present application, when the merged customer information meets regulatory requirements and business requirements, after determining that the merged customer number is the second customer number, the method further includes: unlocking the merged customer number so that the business of the merged customer number can be resumed. Figure 3 As shown, after completing the steps of merging the merged customers, unlock the migrated-in and migrated-out customers in the global routing, restore customer services, and the business of merging customer numbers can be handled normally.

[0060] The embodiment of the present application also provides a customer information merging device. It should be noted that the customer information merging device of the embodiment of the present application can be used to execute the customer information merging method provided in the embodiment of the present application. The customer information merging device provided in the embodiment of the present application is introduced below.

[0061] Figure 4 Schematic diagram of a device for merging customer information according to an embodiment of the present application. Figure 4 As shown, the device comprises:

[0062] An acquisition unit 10 is used to acquire a first customer number and a second customer number, wherein the first customer number and the second customer number are different customer numbers of the same customer;

[0063] A migration unit 20, configured to migrate the first customer information to the data slice where the second customer information is located, wherein the first customer information is the customer information of the first customer number, and the second customer information is the customer information of the second customer number;

[0064] A pre-merging unit 30, configured to pre-merge the first customer information and the second customer information to obtain merged customer information;

[0065] A detection unit 40 is used to detect whether the combined customer information meets regulatory requirements and business requirements, the regulatory requirements include requirements for prescribed limits and prescribed quantity limits, and the business requirements include requirements for not affecting business continuity;

[0066] The merging unit 50 is used to determine that the second customer number is the merged customer number and the merged customer information is the customer information of the merged customer number when the merged customer information meets regulatory requirements and business requirements.

[0067] In the above-mentioned customer information merging device, there is an acquisition unit: the above-mentioned acquisition unit acquires the first customer number and the second customer number, the above-mentioned first customer number and the above-mentioned second customer number are different customer numbers of the same customer; the migration unit: the above-mentioned migration unit migrates the first customer information to the above-mentioned data shard where the second customer information is located, the above-mentioned first customer information is the customer information of the above-mentioned first customer number, and the above-mentioned second customer information is the customer information of the above-mentioned second customer number; the pre-merger unit: the above-mentioned pre-merger unit pre-merges the above-mentioned first customer information and the above-mentioned second customer information to obtain merged customer information; the detection unit: the above-mentioned detection unit detects whether the above-mentioned merged customer information meets the regulatory requirements and business requirements, the above-mentioned regulatory requirements include requirements for prescribed limits and prescribed quantity restrictions, and the above-mentioned business requirements include requirements for not affecting business continuity; the merging unit: when the above-mentioned merged customer information meets the regulatory requirements and business requirements, the above-mentioned merging unit determines that the above-mentioned second customer number is the merged customer number, and the above-mentioned merged customer information is the customer information of the above-mentioned merged customer number. The device performs pre-merger before merging customer information to detect whether the merged customer information meets regulatory requirements and business requirements, and after ensuring that the merged customer information meets regulatory requirements and business requirements, determines the merged customer information as the customer information of the merged customer number, thereby avoiding the situation where the customer information of the merged customer number does not meet regulatory requirements and business requirements, and solves the problem in the prior art that the customer information merger does not meet regulatory requirements and business requirements.

[0068] It should be noted that the above-mentioned customer information includes routine business information and regulatory compliance information. The above-mentioned routine business information includes non-final information that must be transferred, such as account information, media information, contract information, contract information, and additional information in normal status; it also involves final information such as contract information, media information, account information, contract information, additional information, etc. that have been terminated, cancelled, and closed under the customer, as well as information such as registration books, transaction details, and transaction flows before the customer merger; the above-mentioned regulatory compliance information is mainly divided into two types. One is the relevant limit and quantity restriction information of customers stipulated by external supervision, such as the quantity restriction of Class I, II, and III accounts; the other is the customer's own limit control information, such as the annual cumulative limit for overseas cash withdrawals through self-service channels, the cumulative value of bilateral collection and payment amounts of Class III accounts, and the agent account opening information and the number of agent accounts opened when the migrating customer acts as an agent.

[0069] In one embodiment of the present application, the device further includes a sending unit, and the sending unit is used to send a notification when the merged customer information does not meet regulatory requirements and business requirements, and the notification is used to prompt the customers corresponding to the first customer number and the second customer number to handle the target business, and the target business is the business corresponding to the change of customer information that does not meet regulatory requirements and business requirements. In this embodiment, after the pre-merger, when it is detected that the merged customer information, that is, the merged regular business information and regulatory compliance information, does not meet regulatory requirements and business requirements, it is necessary to send a notification to the customer to guide the customer to perform relevant compliance operations or business processing first to ensure that the merged customer information meets regulatory requirements and business requirements.

[0070] In one embodiment of the present application, the migration unit includes a first query module, a first transmission module, a second query module, and a second transmission module, wherein the first query module is used to query the data slice where the first customer information is located according to the first customer number to obtain the first data slice; read the first customer information of the first data slice and generate a customer information file according to the naming specification; the first transmission module is used to upload the customer information file to the file system and obtain file-related information, and the file-related information includes the file name and the file path; the second query module is used to query the data slice where the second customer information is located according to the second customer number to obtain the second data slice; the second transmission module is used to download the customer information file according to the file-related information and store it in the second data slice. In this embodiment, the customer merging process is divided into two parts: customer migration out and customer migration in. The customer migration task specifically includes: 1) Following the migration customer route: According to the migration customer route, go to the data shard where the migration customer is located; 2) Generate the migration file, that is, generate the customer information file: Generate the customer information file according to the naming specification for the data to be migrated according to the business, and the framework supports the data export function at the SQL configuration level; 3) Upload the file: Provide a tool, the tool uses the HDFS tool or batch tool to upload the customer information file to the HDFS file system; 4) Upload the file-related information and customer information to the context: Add the generated file list to the batch context, and the subsequent jobs can obtain the file name, file path, account, contract and other information from the context to provide the necessary information for the subsequent jobs. The customer migration task specifically includes: 1) Migrating customer routing: Determine the data shard where the migrating customer is located based on the migrating customer information and perform the corresponding merge operation processing; 2) Downloading files: Obtain information such as the file name and file path from the context and download the file from HDFS; 3) Determine whether the migrating customer is in the same data shard as the migrating customer; (4) Business data merging: Determine whether to write the file data to a specific data shard based on the result of the previous step, and then read the file data to merge the business data based on the business logic. The above method is a data migration solution in a distributed environment, which realizes the migration of customer information data between different databases. Moreover, under the premise that the core system is an online transaction system with extremely high performance requirements, it realizes quasi-real-time overall customer information data migration, thereby improving the performance of the core system and customer experience.

[0071] It should be noted that the flexibly configured merge scheduling scheme can adjust and configure the various sub-jobs of customer merging in the scheduling platform according to changes in demand, making the entire customer merging function highly configurable. To add a new customer merging function, you only need to implement the framework layer data migration and data migration interfaces, and perform simple configuration to call up the customer merging of this business module. The entire customer merging function is also plug-and-play, and it also supports the removal of tasks on demand.

[0072] In one embodiment of the present application, the detection unit includes a first determination module and a second determination module, wherein the first determination module is used to determine that the merged customer information meets regulatory requirements and business requirements when there is no violation information in the merged customer information and does not affect business continuity, and the violation information is an information item that does not meet the regulatory requirements; the second determination module is used to determine that the merged customer information does not meet regulatory requirements and business requirements when there is violation information in the merged customer information and / or affects business continuity. In this embodiment, Figure 2 As shown, the core process of customer merging in the system is customer pre-check and customer merging. Before customer merging, in order to ensure that the merged customer information after the customer merging step meets the regulatory requirements and business requirements, it is necessary to pre-merge and check the information items under the customer's name that will not meet the regulatory requirements after the merger, as well as the business status of the migrating customer's in-transit business and other business items that affect business continuity after the merger, so as to avoid the customer information of the merged customer not meeting the regulatory requirements or affecting business continuity.

[0073] In one embodiment of the present application, the detection unit further includes a first detection module, a second detection module, a third detection module and a third determination module, wherein the first detection module is used to detect whether the pricing of the same type of the first customer number and the second customer number is consistent, and obtain a first detection result, and the pricing includes charging pricing and revenue pricing; the second detection module is used to detect whether the number of media of the first customer number and the second customer number exceeds the first prescribed quantity limit, and obtain a second detection result; the third detection module is used to detect whether the sum of the number of accounts of the first customer number and the second customer number exceeds the second prescribed quantity limit, and obtain a third detection result; the third determination module is used to determine whether the merged customer information meets regulatory requirements and business requirements based on the first detection result, the second detection result and the third detection result. In this embodiment, the customer merging operation can be initiated in parallel according to each business module, and the core process of the customer merging operation in the system is customer pre-inspection and customer merging. Figure 2 As shown, the two processes of customer pre-inspection and customer merging can be classified into various business modules such as pricing, media, and accounts according to the business type. Each module implements its own customer pre-inspection and customer merging processes according to its own business needs, which can be called on demand for batch scheduling. Among them, the business modules such as pricing, media, and accounts are called to perform customer pre-inspection to obtain the above-mentioned first test result, the above-mentioned second test result, and the above-mentioned third test result, so as to determine whether the above-mentioned merged customer information meets the regulatory requirements and business requirements.

[0074] In one embodiment of the present application, the device further includes a locking unit, which is used to lock the first customer number and the second customer number before migrating the first customer information to the data shard where the second customer information is located, so that the services of the first customer number and the second customer number are stopped. Figure 3 As shown, before the customer merging step is performed, the customer number needs to be locked to ensure that the subsequent steps are not interfered with. After the core system receives the customer locking request, the global routing marks the migrated and migrated customers. At this time, if there are related transactions involving two customers from other systems, the global routing will directly reject the transaction and return a prompt message "The customer has been locked".

[0075] In one embodiment of the present application, the device further includes an unlocking unit, which is used to unlock the merged customer number after determining that the merged customer number is the second customer number when the merged customer information meets regulatory requirements and business requirements, so that the business of the merged customer number can be resumed. Figure 3 As shown, after completing the steps of merging the merged customers, unlock the migrated-in and migrated-out customers in the global routing, restore customer services, and the business of merging customer numbers can be handled normally.

[0076] The above-mentioned customer information merging device includes a processor and a memory. The above-mentioned acquisition unit, migration unit, pre-merging unit, detection unit, merging unit, etc. are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.

[0077] The processor includes a kernel, which calls the corresponding program unit from the memory. One or more kernels can be set, and the problem of customer information merging not meeting regulatory requirements and business requirements in the prior art can be solved by adjusting kernel parameters.

[0078] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0079] An embodiment of the present invention provides a processor, and the processor is used to run a program, wherein the method for merging customer information is executed when the program is run.

[0080] An embodiment of the present invention provides a business system, including a distributed database, one or more processors, a memory, a display device, 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 when the processor executes the program, at least the following steps are implemented:

[0081] Step S101, obtaining a first customer number and a second customer number, wherein the first customer number and the second customer number are different customer numbers of the same customer;

[0082] Step S102, migrating first customer information to the data shard where second customer information is located, the first customer information being customer information of the first customer number, and the second customer information being customer information of the second customer number;

[0083] Step S103, pre-merging the first customer information and the second customer information to obtain merged customer information;

[0084] Step S104, detecting whether the combined customer information meets regulatory requirements and business requirements, wherein the regulatory requirements include requirements for prescribed limits and prescribed quantity restrictions, and the business requirements include requirements for not affecting business continuity;

[0085] Step S105, when the combined customer information meets regulatory requirements and business requirements, determine that the second customer number is the combined customer number, and the combined customer information is the customer information of the combined customer number.

[0086] The devices in this article can be servers, PCs, PADs, mobile phones, etc.

[0087] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program for initializing at least the following method steps:

[0088] Step S101, obtaining a first customer number and a second customer number, wherein the first customer number and the second customer number are different customer numbers of the same customer;

[0089] Step S102, migrating first customer information to the data shard where second customer information is located, the first customer information being customer information of the first customer number, and the second customer information being customer information of the second customer number;

[0090] Step S103, pre-merging the first customer information and the second customer information to obtain merged customer information;

[0091] Step S104, detecting whether the combined customer information meets regulatory requirements and business requirements, wherein the regulatory requirements include requirements for prescribed limits and prescribed quantity restrictions, and the business requirements include requirements for not affecting business continuity;

[0092] Step S105, when the combined customer information meets regulatory requirements and business requirements, determine that the second customer number is the combined customer number, and the combined customer information is the customer information of the combined customer number.

[0093] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0094] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the above-mentioned units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0095] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0096] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0097] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable computer-readable storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a computer-readable storage medium, including a number of instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the above-mentioned methods of each embodiment of the present invention. The aforementioned computer-readable storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0098] From the above description, it can be seen that the above embodiments of the present application achieve the following technical effects:

[0099] 1) In the method for merging customer information of the present application, first, a first customer number and a second customer number are obtained, and the first customer number and the second customer number are different customer numbers of the same customer; then, the first customer information is migrated to the data shard where the second customer information is located, and the first customer information is the customer information of the first customer number, and the second customer information is the customer information of the second customer number; then, the first customer information and the second customer information are pre-merged to obtain merged customer information; then, it is detected whether the merged customer information meets regulatory requirements and business requirements, the regulatory requirements include requirements for prescribed limits and prescribed quantity restrictions, and the business requirements include requirements for not affecting business continuity; finally, if the merged customer information meets regulatory requirements and business requirements, it is determined that the second customer number is the merged customer number, and the merged customer information is the customer information of the merged customer number. The method performs a pre-merge before merging customer information to detect whether the merged customer information meets regulatory requirements and business requirements, and after ensuring that the merged customer information meets regulatory requirements and business requirements, determines the merged customer information as the customer information of the merged customer number, thereby avoiding the situation where the customer information of the merged customer number does not meet regulatory requirements and business requirements, and solves the problem in the prior art that the merger of customer information does not meet regulatory requirements and business requirements.

[0100] 2) In the customer information merging device of the present application, the acquisition unit acquires the first customer number and the second customer number, and the first customer number and the second customer number are different customer numbers of the same customer; the migration unit migrates the first customer information to the data shard where the second customer information is located, and the first customer information is the customer information of the first customer number, and the second customer information is the customer information of the second customer number; the pre-merger unit pre-merges the first customer information and the second customer information to obtain merged customer information; the detection unit detects whether the merged customer information meets regulatory requirements and business requirements, and the regulatory requirements include requirements for prescribed limits and prescribed quantity restrictions, and the business requirements include requirements for not affecting business continuity; the merging unit determines that the second customer number is the merged customer number, and the merged customer information is the customer information of the merged customer number when the merged customer information meets regulatory requirements and business requirements. The device performs pre-merger before merging customer information to detect whether the merged customer information meets regulatory requirements and business requirements, and after ensuring that the merged customer information meets regulatory requirements and business requirements, determines the merged customer information as the customer information of the merged customer number, thereby avoiding the situation where the customer information of the merged customer number does not meet regulatory requirements and business requirements, and solves the problem in the prior art that the customer information merger does not meet regulatory requirements and business requirements.

[0101] 3) The business system of the present application includes a distributed database, one or more processors, a memory, a display device, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include a method for executing the above-mentioned customer information merging method. The method performs a pre-merge before merging customer information, detects whether the merged customer information meets regulatory requirements and business requirements, and determines the merged customer information as the customer information of the merged customer number while ensuring that the merged customer information meets regulatory requirements and business requirements, so as to avoid the situation where the customer information of the merged customer number does not meet regulatory requirements and business requirements, and solves the problem that the customer information merger in the prior art does not meet regulatory requirements and business requirements.

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

Claims

1. A method for merging customer information, characterized in that: The distributed database includes a plurality of data shards, and the data shards are used to store customer information corresponding to a customer number. The method includes: Obtaining a first customer number and a second customer number, wherein the first customer number and the second customer number are different customer numbers of the same customer; Migrate first customer information to the data shard where second customer information is located, the first customer information being customer information of the first customer number, and the second customer information being customer information of the second customer number; Pre-merging the first customer information and the second customer information to obtain merged customer information; Check whether the combined customer information meets regulatory requirements and business requirements, the regulatory requirements include requirements for prescribed limits and prescribed quantity restrictions, and the business requirements include requirements for not affecting business continuity; In the case where the combined customer information meets regulatory requirements and business requirements, determining that the second customer number is the combined customer number, and the combined customer information is the customer information of the combined customer number; The customer merging operation is divided into customer migration out and customer migration in. The customer migration out includes: determining the data shard where the first customer number is located according to the migration out customer route; generating a customer information file according to the naming specification for the data to be migrated, and the framework supports the data export function at the SQL configuration level; uploading the customer information file to the HDFS file system using HDFS tools or batch tools; adding the file list of the generated customer information file to the context, and subsequent operations obtain the file name, file path, account and contract information from the context; the customer migration in includes: determining the data shard where the second customer information is located to perform corresponding merging operation processing; obtaining the file name and file path from the context, and using the HDFS tool to download the customer information file; writing the customer information file to the data shard where the second customer information is located, and reading the customer information file to perform business data merging according to business logic; The customer merging operation is initiated in parallel according to each business module. The core process of the customer merging operation in the system is customer pre-inspection and customer merging. The customer pre-inspection and customer merging are classified into the business modules including pricing, media, and accounts according to business types. Each business module implements the corresponding customer pre-inspection and customer merging processes according to corresponding business requirements.

2. The method according to claim 1, characterized in that The method further comprises: In the case where the merged customer information does not meet regulatory requirements and business requirements, a notification is sent, wherein the notification is used to prompt the customers corresponding to the first customer number and the second customer number to handle target business, wherein the target business is the business corresponding to the change of customer information that does not meet regulatory requirements and business requirements.

3. The method according to claim 1, characterized in that: Migrating the first customer information to the data shard where the second customer information is located includes: Query the data slice where the first customer information is located according to the first customer number to obtain a first data slice; Reading the first customer information of the first data slice and generating a customer information file according to a naming convention; Upload the customer information file to the file system and obtain file related information, the file related information including the file name and file path; Query the data slice where the second customer information is located according to the second customer number to obtain a second data slice; The customer information file is downloaded according to the file-related information and stored in the second data slice.

4. The method according to claim 1, characterized in that Check whether the merged customer information meets regulatory and business requirements, including: If there is no illegal information in the merged customer information and business continuity is not affected, it is determined that the merged customer information meets regulatory requirements and business requirements, and the illegal information is an information item that does not meet the regulatory requirements; If the merged customer information contains illegal information and / or affects business continuity, it is determined that the merged customer information does not meet regulatory requirements and business requirements.

5. The method according to claim 1, characterized in that Check whether the merged customer information meets regulatory and business requirements, including: Detecting whether the same type of pricing of the first customer number and the second customer number is consistent, and obtaining a first detection result, wherein the pricing includes charge pricing and revenue pricing; Detecting whether the quantity of media of the first customer number and the second customer number exceeds a first prescribed quantity limit, and obtaining a second detection result; Detecting whether the sum of the number of accounts of the first customer number and the second customer number exceeds a second prescribed number limit, and obtaining a third detection result; Determine whether the combined customer information meets regulatory requirements and business requirements based on the first test result, the second test result, and the third test result.

6. The method according to any one of claims 1 to 5, characterized in that: Before migrating the first customer information to the data shard where the second customer information is located, the method further includes: The first customer number and the second customer number are locked so that the business of the first customer number and the second customer number is stopped.

7. The method according to any one of claims 1 to 5, characterized in that: In the case where the combined customer information meets regulatory requirements and business requirements, after determining that the combined customer number is the second customer number, the method further includes: The merged customer number is unlocked so that the business of the merged customer number can be resumed.

8. A device for merging customer information, characterized in that: The distributed database includes a plurality of data slices, wherein the data slices are used to store customer information corresponding to a customer number, and the device includes: An acquiring unit, configured to acquire a first customer number and a second customer number, wherein the first customer number and the second customer number are different customer numbers of the same customer; A migration unit, configured to migrate first customer information to the data shard where second customer information is located, wherein the first customer information is customer information of the first customer number, and the second customer information is customer information of the second customer number; a pre-merging unit, configured to pre-merge the first customer information and the second customer information to obtain merged customer information; a detection unit, configured to detect whether the combined customer information meets regulatory requirements and business requirements, wherein the regulatory requirements include requirements for prescribed limits and prescribed quantity restrictions, and the business requirements include requirements for not affecting business continuity; A merging unit, configured to determine that the second customer number is a merged customer number and the merged customer information is customer information of the merged customer number if the merged customer information meets regulatory requirements and business requirements; The pre-merge unit is used to perform customer merging operations, and the customer merging operations are divided into customer migration out and customer migration in. The customer migration out unit corresponding to the customer migration out is used to determine the data shard where the first customer number is located according to the migration out customer route; the data to be migrated is used to generate a customer information file according to the naming specification, and the framework supports the data export function at the SQL configuration level; the customer information file is uploaded to the HDFS file system using the HDFS tool or batch tool; the file list of the generated customer information file is added to the context, and subsequent operations obtain the file name, file path, account and contract information from the context; the customer migration in unit corresponding to the customer migration in is used to determine the data shard where the second customer information is located to perform corresponding merging operation processing; the file name and the file path are obtained from the context, and the customer information file is downloaded using the HDFS tool; the customer information file is written into the data shard where the second customer information is located, and the customer information file is read to perform business data merging according to the business logic; The customer merging operation is initiated in parallel according to each business module. The core process of the customer merging operation in the system is customer pre-inspection and customer merging. The customer pre-inspection and customer merging are classified into the business modules including pricing, media, and accounts according to business types. Each business module implements the corresponding customer pre-inspection and customer merging processes according to corresponding business requirements.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein the program executes the method of any one of claims 1 to 7.

10. A processor, characterized in that: The processor is used to run a program, wherein the program executes the method according to any one of claims 1 to 7 when running.

11. A business system, characterized in that: It includes a distributed database, one or more processors, a memory, a display device and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include methods for executing any one of claims 1 to 7.

Images