CN115170277A

CN115170277A - Customer information merging method, merging device and service system

Info

Publication number: CN115170277A
Application number: CN202210769971.7A
Authority: CN
Inventors: 朱峰; 曹兴旺; 王永福; 王战兵; 李逢安
Original assignee: Postal Savings Bank of China Ltd
Current assignee: Postal Savings Bank of China Ltd
Priority date: 2022-07-01
Filing date: 2022-07-01
Publication date: 2022-10-11

Abstract

The application provides a merging method, a merging device and a service system of customer information, wherein the method comprises the following steps: acquiring a first client number and a second client number, wherein the first client number and the second client number are different client numbers of the same client; migrating first customer information to a data fragment where second customer information is located, wherein the first customer information is customer information of a first customer number, and the second customer information is customer information of a second customer number; pre-combining the first customer information and the second customer information to obtain combined customer information; detecting whether the merged customer information meets the supervision requirement and the service requirement; and under the condition that the merged client information meets the supervision requirement and the service requirement, determining that the second client number is the merged client number, and the merged client information is the client information of the merged client number, so that the problem that the client information merging does not meet the supervision requirement and the service requirement in the prior art is solved.

Description

Customer information merging method, merging device and service system

Technical Field

The present application relates to the field of data migration technologies, and in particular, to a method and an apparatus for merging client information, a computer-readable storage medium, a processor, and a service system.

Background

At present, the vast majority of client data in China breaks through billions or approaches to billions, and in a distributed environment, the billions of client data are evenly distributed to nearly one hundred databases and thousands of data fragments. However, due to various historical and actual factors (for example, 15-bit ID card is replaced by 18-bit ID card, military officer ID card is replaced by ID card, etc.), the condition that the same customer uses different certificates to establish a plurality of customer numbers in the same bank exists at present. Because of the supervision requirement and the business requirement of the client, the requirement of combining the client business data under one client number into another client number objectively exists. The need is related to migrating clients from a source database data shard to a new database data shard.

In a core system adopting a centralized architecture in the same industry, services such as merging of customer service data and the like occur in the same database, and the condition of crossing databases and even physical machines does not exist. In the core system of the distributed architecture, the published information has no relevant description about the part of functions or technical schemes.

A commercial bank migrates a centralized core system to a distributed core system, and the distributed core system mostly performs database division and table division according to the client number of a client; when the identity of the client changes or the elements change and the change of the client number is involved, all data of the client need to be uniformly migrated from the data of the old client number to the database corresponding to the new client number, and corresponding service data are merged.

The main disadvantages of the prior art are as follows:

(1) The migration at the account level is aimed at under a centralized architecture, and the migration is not a customer-level solution, and the design naturally has the difficulties that the data inconsistency occurs after customers are merged, and the customer experience and the internal data management of enterprises are influenced.

(2) There is a lack of a real-time client consolidation solution under a distributed database.

The invention aims to solve the problem of overall migration of client data among different databases and database shards in a distributed environment.

Currently, the centralized core system mainly adopts the following scheme when handling customer merging:

only the number of the client to which the account belongs in the core system is changed, the client to which the account belongs is logically changed, and information such as media, contracts and the like is not changed.

The above information disclosed in this background section is only for enhancement of understanding of the background of the technology described herein and, therefore, certain information may be included in the background that does not form the prior art that is already known in this country to a person of ordinary skill in the art.

Disclosure of Invention

The present application mainly aims to provide a method, an apparatus, a computer-readable storage medium, a processor and a business system for merging client information, so as to solve the problem that in the prior art, client information merging does not meet the supervision requirement and the business requirement.

According to an aspect of the embodiments of the present invention, there is provided a method for merging client information, where a distributed database includes a plurality of data fragments, and the data fragments are used to store client information corresponding to a client number, the method includes: acquiring a first client number and a second client number, wherein the first client number and the second client number are different client numbers of the same client; migrating first customer information to the data fragment 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; pre-combining the first customer information and the second customer information to obtain combined customer information; detecting whether the merged customer information meets the requirements of supervision and service, wherein the requirements of supervision comprise the requirements of specified quota and specified quantity limitation, and the service requirement comprises the requirement of not influencing service continuity; and under the condition that the merged customer information meets the supervision requirement and the service requirement, determining that the second customer number is the merged customer number, wherein the merged customer information is the customer information of the merged customer number.

Optionally, the method further comprises: and under the condition that the merged client information does not meet the supervision requirement and the service requirement, sending a notice, wherein the notice is used for prompting the client corresponding to the first client number and the second client number to handle a target service, and the target service is a service corresponding to the client information which does not meet the supervision requirement and the service requirement and is changed.

Optionally, migrating the first customer information to the data segment where the second customer information is located includes: inquiring the data fragment where the first client information is located according to the first client number to obtain a first data fragment; reading the first client information of the first data fragment and generating a client information file according to a naming specification; uploading the client information file to a file system and acquiring file related information, wherein the file related information comprises a file name and a file path; inquiring the data fragment where the second client information is located according to the second client number to obtain a second data fragment; and downloading the client information file according to the file related information and storing the client information file to the second data fragment.

Optionally, detecting whether the merged customer information meets the regulatory requirement and the business requirement includes: determining that the merged customer information meets the supervision requirement and the service requirement when the merged customer information does not have violation information and does not influence service continuity, wherein the violation information is an information item which does not meet the supervision requirement; and if violation information exists in the merged customer information and/or the business continuity is influenced, determining that the merged customer information does not meet the supervision requirement and the business requirement.

Optionally, detecting whether the merged customer information meets the regulatory requirement and the business requirement includes: detecting whether the pricing of the same type of the first customer number and the second customer number is consistent or not to obtain a first detection result, wherein the pricing comprises charging pricing and income pricing; detecting whether the media quantity of the first customer number and the second customer number exceeds a first specified quantity limit or not to obtain a second detection result; detecting whether the sum of the account numbers of the first customer number and the second customer number exceeds a second specified number limit or not to obtain a third detection result; and determining whether the merged customer information meets the supervision requirement and the service requirement according to the first detection result, the second detection result and the third detection result.

Optionally, before migrating the first client information to the data slice in which the second client information is located, the method further includes: and locking the first client number and the second client number, so that the transaction of the first client number and the second client number is stopped.

Optionally, in a case that the merged customer information satisfies regulatory requirements and business requirements, after determining that the merged customer number is the second customer number, the method further includes: and unlocking the merged client number to ensure that the business of the merged client number is returned and transacted.

According to another aspect of the embodiments of the present invention, there is further provided a merging apparatus for client information, where a distributed database includes a plurality of data fragments, and the data fragments are used to store client information corresponding to a client number, the apparatus includes: an acquisition unit configured to acquire a first customer number and a second customer number, the first customer number and the second customer number being different customer numbers of a same customer; a migration unit, configured to migrate first customer information to the data segment where second customer information is located, where 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; the pre-merging unit is used for pre-merging the first customer information and the second customer information to obtain merged customer information; a detecting unit, configured to detect whether the merged customer information meets a regulatory requirement and a service requirement, where the regulatory requirement includes a requirement that a specified quota and a specified quantity are limited, and the service requirement includes a requirement that service continuity is not affected; and the merging unit is used for determining that the second client number is the merging client number under the condition that the merging client information meets the supervision requirement and the service requirement, and the merging client information is the client information of the merging client number.

According to still another aspect of embodiments of the present invention, there is also provided a computer-readable storage medium including a stored program, wherein the program executes any one of the methods.

According to another aspect of the embodiments of the present invention, there is also provided a processor, configured to execute a program, where the program executes any one of the methods.

There is also provided, in accordance with an aspect of an embodiment of the present invention, a business system, including a distributed database, one or more processors, 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, the one or more programs including instructions for performing any of the methods described herein.

In the embodiment of the present invention, in the method for merging client information, first, a first client number and a second client number are obtained, where the first client number and the second client number are different client numbers of the same client; then, migrating first customer information to the data fragment 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; then, pre-combining the first customer information and the second customer information to obtain combined customer information; then, detecting whether the merged customer information meets the supervision requirement and the service requirement, wherein the supervision requirement comprises the requirements of specified quota and specified quantity limitation, and the service requirement comprises the requirement of not influencing service continuity; and finally, under the condition that the merged client information meets the supervision requirement and the service requirement, determining the second client number as the merged client number, wherein the merged client information is the client information of the merged client number. The method carries out precombination before the customer information is combined, detects whether the combined customer information meets the supervision requirement and the service requirement, determines the combined customer information as the customer information of the combined customer number under the condition of ensuring that the combined customer information meets the supervision requirement and the service requirement, avoids the condition that the customer information of the combined customer number does not meet the supervision requirement and the service requirement, and solves the problem that the customer information combination does not meet the supervision requirement and the service requirement in the prior art.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this application, illustrate embodiments of the application and, together with the description, serve to explain the application and are not intended to limit the application. In the drawings:

FIG. 1 shows a flow diagram of a method of merging customer information according to an embodiment of the present application;

FIG. 2 illustrates a flow diagram of a method for merging customer information according to another particular embodiment of the present application;

FIG. 3 illustrates a flow diagram of a method for merging customer information according to yet another particular embodiment of the present application;

fig. 4 shows a schematic diagram of a merging device of customer information according to an embodiment of the application.

Detailed Description

It should be noted that the following detailed description is exemplary and is intended to provide further explanation of the disclosure. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs.

It is noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of exemplary embodiments according to the present application. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, and it should be understood that when the terms "comprises" and/or "comprising" are used in this specification, they specify the presence of stated features, steps, operations, devices, components, and/or combinations thereof, unless the context clearly indicates otherwise.

It will be understood that when an element such as a layer, film, region, or substrate is referred to as being "on" another element, it can be directly on the other element or intervening elements may also be present. Also, 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.

For convenience of description, some terms or expressions referred to in the embodiments of the present application are explained below:

distributed database: dividing a complete database into a plurality of deployment nodes according to a specific rule, wherein each node has a complete copy or a partial copy, and different nodes are connected with each other through a computer network to form a logically centralized and physically distributed large database;

centralized architecture: resources such as calculation, storage and the like are all in a set of physically centralized hardware system, and the problem of network partition does not need to be solved;

the client has three elements: certificate type, certificate number, customer name;

a core system: the accounting processing system in the commercial bank information system architecture is responsible for providing basic account services of 7x24 hours for various businesses, such as interest counting, payment, settlement, accounting and the like, and is the most basic and most core part in the banking business;

global routing: providing a client positioning function for each application component of the core system, so that the application component can be positioned to a corresponding database according to a client number during transaction processing;

a combined transaction platform: the functions of integrating short-flow business and the like are realized through cross-system service arrangement and series connection, and the decoupling of a service consumer and a service provider is realized;

HDFS (Hadoop distributed File System): the Distributed File System is named as Hadoop Distributed File System, is a Distributed File System designed to run on general hardware, and has the characteristics of high fault tolerance, high throughput, large File support and the like.

Context: a memory data area in the program design can be freely stored and accessed by the program.

As mentioned in the background, in order to solve the above problems, in the prior art, the merging of customer information does not meet the regulatory requirements and the business requirements, in an exemplary embodiment of the present application, a merging method, a merging device, a computer-readable storage medium, a processor, and a business system for customer information are provided.

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

Fig. 1 is a flowchart of a method for merging customer information according to an embodiment of the present application. As shown in fig. 1, the method comprises the steps of:

step S101, a first client number and a second client number are obtained, wherein the first client number and the second client number are different client numbers of the same client;

step S102, migrating first customer information to the data fragment 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;

step S103, pre-combining the first customer information and the second customer information to obtain combined customer information;

step S104, detecting whether the merged customer information meets the supervision requirement and the service requirement, wherein the supervision requirement comprises the requirements of specified quota and specified quantity limitation, and the service requirement comprises the requirement of not influencing service continuity;

step S105, under the condition that the merged customer information meets the supervision requirement and the service requirement, determining that the second customer number is the merged customer number, wherein the merged customer information is the customer information of the merged customer number.

In the method for merging the customer information, first, a first customer number and a second customer number are obtained, wherein the first customer number and the second customer number are different customer numbers of the same customer; then, migrating first customer information to the data fragment 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; then, pre-merging the first customer information and the second customer information to obtain merged customer information; then, detecting whether the merged customer information meets the supervision requirement and the service requirement, wherein the supervision requirement comprises the requirements of specified quota and specified quantity limitation, and the service requirement comprises the requirement of not influencing service continuity; and finally, under the condition that the merged client information meets the supervision requirement and the service requirement, determining the second client number as the merged client number, wherein the merged client information is the client information of the merged client number. The method carries out precombination before the customer information is combined, detects whether the combined customer information meets the supervision requirement and the service requirement, determines the combined customer information as the customer information of the combined customer number under the condition of ensuring that the combined customer information meets the supervision requirement and the service requirement, avoids the condition that the customer information of the combined customer number does not meet the supervision requirement and the service requirement, and solves the problem that the customer information combination does not meet the supervision requirement and the service requirement in the prior art.

It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowcharts, in some cases, the steps illustrated or described may be performed in an order different than here.

It should be further noted that the customer information includes conventional service information and regulatory compliance information, where the conventional service information includes non-final state information that must be transferred, such as account information, media information, contract information, and sponsoring information in a normal state; the terminal state information comprises contract information, medium information, account information, contract information, addition information and the like of released, cancelled and sold clients, and information such as a register, transaction details, transaction flow and the like before the clients are merged; the supervision compliance information is mainly divided into two types, one type is the related quota of the client specified by external supervision and the quantity limit information such as the quantity limit of I, II and III types of users; the other is limit control information of the client itself, such as annual cumulative limit for outdoor withdrawal in a self-service channel, cumulative value of amount paid in class III account fund, agent account opening information and agent account opening amount when the client is moved out as an agent, and the like.

In an embodiment of the present application, the method further includes: and sending a notice under the condition that the merged client information does not meet the supervision requirement and the service requirement, wherein the notice is used for prompting the clients corresponding to the first client number and the second client number to handle the target service, and the target service is the service corresponding to the client information change which does not meet the supervision requirement and the service requirement. In this embodiment, after the pre-merging, when it is detected that the merged customer information, that is, the merged general service information and the merged supervision compliance information, do not meet the supervision requirement and the service requirement, a notification needs to be sent to the customer to guide the customer to perform relevant compliance operation or service processing first, so as to ensure that the merged customer information meets the supervision requirement and the service requirement.

In an embodiment of the application, migrating the first client information to the data fragment where the second client information is located includes: inquiring the data fragment where the first client information is according to the first client number to obtain a first data fragment; reading the first client information of the first data fragment and generating a client information file according to a naming specification; uploading the client information file to a file system and acquiring file related information, wherein the file related information comprises a file name and a file path; inquiring the data fragment where the second client information is located according to the second client number to obtain a second data fragment; and downloading the client information file according to the file related information and storing the client information file in the second data fragment. In this embodiment, the client merging process is divided into two parts, client migration-out and client migration-in. The client migration task specifically comprises the following steps: 1) According to the migrating client route: according to the route of the migrating client, the data fragment of the migrating client is located; 2) Generating an emigration file, namely generating a customer information file: generating a client information file according to the data to be migrated from the service according to a naming specification, wherein the framework supports the data export function of the SQL configuration level; 3) Uploading a file: providing a tool, wherein the tool uploads a client information file to an HDFS file system by using an HDFS tool or a batch tool; 4) Uploading file related information and client information to the following: and adding the generated file list into the batch context, and acquiring information such as file names, file paths, accounts, contracts and the like from the context by the subsequent operation so as to provide necessary information for the subsequent operation. The client immigration task specifically comprises the following steps: 1) Migrating the client route: determining the data fragment where the migration client is located according to the migration client information to perform corresponding merging operation processing; 2) Downloading a file: obtaining information such as file names, file paths and the like from the context, and downloading files from the HDFS; 3) Acquiring whether the migrated client and the migrated client share the same data fragment; and (4) service data merging: the method is a data migration scheme under a distributed environment, migration of client information data among different databases is achieved, on the premise that a core system is used as an online transaction system with extremely high performance requirements, quasi-real-time client information overall data migration is achieved, and performance and client experience of the core system are improved.

It should be noted that, according to the change of the demand, the flexibly configured merge scheduling scheme may adjust and configure each sub-job merged by the client in the scheduling platform, so that the function of the entire client merge is highly configurable. The newly added client merging function only needs to realize the frame layer data migration-out and data migration-in interfaces, and can call the client merging of the service module through simple configuration, so that the whole client merging function also has the property of plug and play, and simultaneously supports the removal of tasks as required.

In an embodiment of the present application, detecting whether the merged customer information meets the supervision requirement and the service requirement includes: determining that the merged customer information meets the supervision requirement and the service requirement when the merged customer information does not have violation information and does not influence service continuity, wherein the violation information is an information item which does not meet the supervision requirement; and determining that the merged customer information does not meet the supervision requirement and the service requirement when the merged customer information has violation information and/or influences service continuity. In this embodiment, as shown in fig. 2, a core flow of the customer merging operation in the system is customer pre-inspection and customer merging, before customer merging, in order to ensure that merged customer information after the customer merging step is completed meets the supervision requirement and the service requirement, pre-merging is required to check information items that will not meet the supervision requirement after merging under the name of the customer, and service states and the like that affect service continuity after merging such as in-transit services and the like of the customer are migrated, so as to avoid that the customer information of the merged customer does not meet the supervision requirement or affect service continuity.

In an embodiment of the present application, detecting whether the merged customer information meets the supervision requirement and the service requirement includes: detecting whether the pricing of the same type of the first customer number and the second customer number is consistent or not to obtain a first detection result, wherein the pricing comprises charging pricing and income pricing; detecting whether the media quantity of the first customer number and the second customer number exceeds a first specified quantity limit to obtain a second detection result; detecting whether the sum of the account numbers of the first customer number and the second customer number exceeds a second specified number limit or not to obtain a third detection result; and determining whether the merged customer information meets the supervision requirement and the service requirement according to the first detection result, the second detection result and the third detection result. In this embodiment, the client merge job may be initiated in parallel according to each service module, and the core flow of the client merge job in the system is client pre-check and client merge. As shown in fig. 2, the two flows of customer pre-inspection and customer merging may be further classified into business modules such as pricing, medium, account, etc. according to the business types, and each module respectively implements the respective customer pre-inspection and customer merging flows according to its own business requirements for batch scheduling to be called as required, wherein each business module such as pricing, medium, account, etc. is called to perform customer pre-inspection, so as to obtain the first detection result, the second detection result, and the third detection result, thereby determining whether the merged customer information meets the supervision requirement and the business requirement.

In an embodiment of the present application, before migrating the first client information to the data slice where the second client information is located, the method further includes: and locking the first client number and the second client number so as to stop transacting the services of the first client number and the second client number. In this embodiment, as shown in fig. 3, before the step of merging clients is performed, the client number needs to be locked to ensure that the subsequent steps are not interfered, after the core system receives the client locking request, the migrating-out and migrating-in clients are marked by the global routing, and at this time, if there is a relevant transaction related to two clients from other systems, the global routing directly rejects the transaction and returns a prompt that "the client is locked".

In an embodiment of the application, after determining that the merge client number is the second client number when the merge client information meets the supervision requirement and the service requirement, the method further includes: and unlocking the merged client number to ensure that the business of the merged client number is returned and transacted. In this embodiment, as shown in fig. 3, after the merging step is completed for the merged customer, the migrated customer and migrated customer are unlocked in the global route, the customer service is restored, and the service of the merged customer number can be handled normally.

The embodiment of the present application further provides a device for merging client information, and it should be noted that the device for merging client information according to the embodiment of the present application may be used to execute the method for merging client information provided in the embodiment of the present application. The following describes a device for merging customer information provided in the embodiments of the present application.

Fig. 4 is a schematic diagram of a customer information merging device according to an embodiment of the present application. As shown in fig. 4, the apparatus includes:

an acquiring unit 10 configured to acquire 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;

a migration unit 20, configured to migrate first client information to the data segment where second client information is located, where the first client information is client information of the first client number, and the second client information is client information of the second client number;

a pre-merging unit 30, configured to pre-merge the first customer information and the second customer information to obtain merged customer information;

a detecting unit 40, configured to detect whether the merged customer information meets a regulatory requirement and a service requirement, where the regulatory requirement includes a requirement of a specified quota and a specified quantity limit, and the service requirement includes a requirement that service continuity is not affected;

a merging unit 50, configured to determine that the second client number is a merged client number when the merged client information meets the supervision requirement and the service requirement, where the merged client information is client information of the merged client number.

The above-mentioned acquisition unit obtains the first customer number and second customer number, the above-mentioned first customer number and above-mentioned second customer number are different above-mentioned customer numbers of the same customer; the migration unit migrates first customer information to the data fragment 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, wherein the pre-merging unit pre-merges the first customer information and the second customer information to obtain merged customer information; the detecting element detects whether the above-mentioned amalgamated customer information meets the supervision requirement and business requirement, the above-mentioned supervision requirement includes stipulating the limited requirement of quota and stipulating quantity, the above-mentioned business requirement includes the requirement not influencing the continuity of the business; and the merging unit determines that the second client number is the merging client number under the condition that the merging client information meets the supervision requirement and the service requirement, and the merging client information is the client information of the merging client number. The device carries out precombination before the customer information is combined, detects whether the combined customer information meets the supervision requirement and the service requirement, determines the combined customer information as the customer information of the combined customer number under the condition of ensuring that the combined customer information meets the supervision requirement and the service requirement, avoids the condition that the customer information of the combined customer number does not meet the supervision requirement and the service requirement, and solves the problem that the customer information combination does not meet the supervision requirement and the service requirement in the prior art.

It should be noted that the customer information includes conventional service information and regulatory compliance type information, and the conventional service information includes non-final state information that must be transferred, such as account information, media information, contract information, and sponsoring information in a normal state; the system also relates to final state information such as contract information, medium information, account information, contract agreement information, addition information and the like of released, cancelled and sold clients, and information such as a register, transaction details, transaction flow and the like before merging clients; the supervision compliance information is mainly divided into two types, one type is the related quota of the client specified by external supervision and the quantity limit information such as the quantity limit of I, II and III types of users; the other is limit control information of the client itself, such as annual cumulative limit for outdoor withdrawal in a self-service channel, cumulative value of amount paid in class III account fund, agent account opening information and agent account opening amount when the client is moved out as an agent, and the like.

In an embodiment of the application, the apparatus further includes a sending unit, where the sending unit is configured to send a notification when the merged customer information does not meet the regulatory requirement and the service requirement, where the notification is used to prompt a customer corresponding to the first customer number and the second customer number to handle a target service, and the target service is a service corresponding to a change of the customer information that does not meet the regulatory requirement and the service requirement. In this embodiment, after the pre-merging, when it is detected that the merged customer information, that is, the merged general service information and the merged supervision compliance information, do not meet the supervision requirement and the service requirement, a notification needs to be sent to the customer to guide the customer to perform relevant compliance operation or service processing first, so as to ensure that the merged customer information meets the supervision requirement and the service requirement.

In an 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, where the first query module is configured to query the data fragment where the first client information is located according to the first client number to obtain a first data fragment; reading the first client information of the first data fragment and generating a client information file according to a naming specification; the first transmission module is used for uploading the client information file to a file system and acquiring file related information, wherein the file related information comprises a file name and a file path; the second query module is used for querying the data fragment where the second client information is located according to the second client number to obtain a second data fragment; the second transmission module is used for downloading the client information file according to the file related information and storing the client information file to the second data fragment. In this embodiment, the client merging process is divided into two parts, client migration-out and client migration-in. The client migration task specifically comprises: 1) According to the migrating client route: according to the route of the migrating client, the data fragment of the migrating client is located; 2) Generating a migration file, namely generating a client information file, namely generating the client information file according to the data to be migrated according to the service and the naming specification, wherein the framework supports the data export function of the SQL configuration level; 3) Uploading a file: providing a tool, wherein the tool uploads a client information file to an HDFS file system by using an HDFS tool or a batch tool; 4) Uploading file related information and client information to the context: and adding the generated file list into the batch context, and acquiring information such as file names, file paths, accounts, contracts and the like from the context by the subsequent operation so as to provide necessary information for the subsequent operation. The client immigration task specifically comprises the following steps: 1) Migrating the client route: determining the data fragments where the migrating clients are located according to the migrating client information to perform corresponding merging operation processing; 2) Downloading a file: obtaining information such as file names, file paths and the like from the context, and downloading files from the HDFS; 3) Acquiring whether the migrated client and the migrated client share the same data fragment; and (4) service data merging: the method is a data migration scheme under a distributed environment, migration of client information data among different databases is achieved, and on the premise that a core system is used as an online transaction system with extremely high performance requirements, quasi-real-time client information overall data migration is achieved, and performance and client experience of the core system are improved.

It should be noted that, according to the change of the demand, the flexibly configured merge scheduling scheme can adjust and configure each sub-job merged by the client in the scheduling platform, so that the function of merging the whole client is highly configurable. The newly added client merging function only needs to realize the frame layer data migration-out and data migration-in interfaces, and can call the client merging of the service module through simple configuration, so that the whole client merging function also has the property of plug and play, and simultaneously supports the removal of tasks as required.

In an embodiment of the present application, the detection unit includes a first determination module and a second determination module, where the first determination module is configured to determine that the merged customer information meets a supervision requirement and a service requirement when the merged customer information does not have violation information and does not affect service continuity, and the violation information is an information item that does not meet the supervision requirement; the second determining module is configured to determine that the merge customer information does not meet the regulatory requirement and the business requirement when the merge customer information has violation information and/or influences business continuity. In this embodiment, as shown in fig. 2, a core flow of the customer merging operation in the system is customer pre-inspection and customer merging, before customer merging, in order to ensure that merged customer information after the customer merging step is completed meets the supervision requirement and the service requirement, information items that will not meet the supervision requirement after merging under the name of the customer need to be pre-merged and checked, and service states that affect service continuity after merging, such as on-the-road services of the removal customer, and the like, are required to avoid that the customer information of the merged customer does not meet the supervision requirement or affect service continuity.

In an embodiment of the application, the detecting unit further includes a first detecting module, a second detecting module, a third detecting module, and a third determining module, where the first detecting module is configured to detect whether pricing of the same type of the first customer number and pricing of the same type of the second customer number are consistent, and obtain a first detecting result, where the pricing includes pricing for charging and pricing for revenue; the second detection module is used for detecting whether the media quantity of the first customer number and the second customer number exceeds a first specified quantity limit or not to obtain a second detection result; the third detection module is used for detecting whether the sum of the account numbers of the first customer number and the second customer number exceeds a second specified number limit to obtain a third detection result; the third determining module is configured to determine whether the merged customer information meets the supervision requirement and the service requirement according to the first detection result, the second detection result, and the third detection result. In this embodiment, the client merge job may be initiated in parallel according to each service module, and the core flow of the client merge job in the system is client pre-check and client merge. As shown in fig. 2, the two flows of customer pre-inspection and customer merging may be further classified into business modules such as pricing, medium, account, etc. according to the business types, and each module respectively implements the respective customer pre-inspection and customer merging flows according to its own business requirements for batch scheduling to be called as required, wherein each business module such as pricing, medium, account, etc. is called to perform customer pre-inspection, so as to obtain the first detection result, the second detection result, and the third detection result, thereby determining whether the merged customer information meets the supervision requirement and the business requirement.

In an embodiment of the application, the apparatus further includes a locking unit, where the locking unit is configured to lock the first client number and the second client number before migrating the first client information to the data fragment where the second client information is located, so that the transaction of the first client number and the second client number is stopped. In this embodiment, as shown in fig. 3, before the step of merging clients is performed, the client number needs to be locked to ensure that the subsequent steps are not interfered, after the core system receives the client locking request, the migrating-out and migrating-in clients are marked by the global routing, and at this time, if there is a relevant transaction related to two clients from other systems, the global routing directly rejects the transaction and returns a prompt that "the client is locked".

In an embodiment of the application, the apparatus further includes an unlocking unit, where the unlocking unit is configured to unlock the merge client number after determining that the merge client number is the second client number when the merge client information meets the supervision requirement and the service requirement, so that the service of the merge client number is resumed. In this embodiment, as shown in fig. 3, after the merging step is completed for the merged customer, the migrated customer and migrated customer are unlocked in the global route, the customer service is restored, and the service of the merged customer number can be handled normally.

The client information merging device comprises a processor and a memory, wherein the acquisition unit, the migration unit, the pre-merging unit, the detection unit, the merging unit and the like are stored in the memory as program units, and the processor executes the program units stored in the memory to realize corresponding functions.

The processor comprises a kernel, and the kernel calls the corresponding program unit from the memory. One or more than one kernel can be set, and the problem that the client information combination does not meet the supervision requirement and the service requirement in the prior art is solved by adjusting the kernel parameters.

The memory may include volatile memory in a computer readable medium, random Access Memory (RAM) and/or nonvolatile memory such as Read Only Memory (ROM) or flash memory (flash RAM), and the memory includes at least one memory chip.

The embodiment of the invention provides a processor, which is used for running a program, wherein the program executes the merging method of the client information during running.

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, where the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the processors implement at least the following steps when executing the programs:

step S101, a first customer number and a second customer number are obtained, wherein the first customer number and the second customer number are different customer numbers of the same customer;

The device herein may be a server, a PC, a PAD, a mobile phone, etc.

The present application further provides a computer program product adapted to perform a program of initializing at least the following method steps when executed on a data processing device:

In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the embodiments provided in the present application, it should be understood that the disclosed technical content can be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the above-described division of the units may be a logical division, and in actual implementation, there may be another division, for example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit may be stored in a computer-readable storage medium if it is implemented in the form of a software functional unit and sold or used as a separate product. Based on such understanding, the technical solution of the present invention, which is substantially or partly contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a computer readable storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned computer-readable storage medium comprises: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

From the above description, it can be seen that the above-described embodiments of the present application achieve the following technical effects:

1) In the method for merging client information, first, a first client number and a second client number are obtained, wherein the first client number and the second client number are different client numbers of the same client; then, migrating first customer information to the data fragment 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; then, pre-merging the first customer information and the second customer information to obtain merged customer information; then, detecting whether the merged customer information meets the supervision requirement and the service requirement, wherein the supervision requirement comprises the requirements of specified quota and specified quantity limitation, and the service requirement comprises the requirement of not influencing service continuity; and finally, under the condition that the merged customer information meets the supervision requirement and the service requirement, determining that the second customer number is the merged customer number, wherein the merged customer information is the customer information of the merged customer number. The method carries out pre-combination before the customer information combination, detects whether the combined customer information meets the supervision requirement and the service requirement, determines the combined customer information as the customer information of the combined customer number under the condition of ensuring that the combined customer information meets the supervision requirement and the service requirement, avoids that the customer information of the combined customer number does not meet the supervision requirement and the service requirement, and solves the problem that the customer information combination does not meet the supervision requirement and the service requirement in the prior art.

2) In the client information combining device of the present application, the acquiring unit acquires a first client number and a second client number, which are different client numbers of the same client; a migration unit, wherein the migration unit migrates first client information to the data segment where second client information is located, the first client information being client information of the first client number, and the second client information being client information of the second client number; a pre-merging unit, where the pre-merging unit performs pre-merging on the first customer information and the second customer information to obtain merged customer information; the detection unit detects whether the merged customer information meets the supervision requirement and the service requirement, wherein the supervision requirement comprises the requirements of specified quota and specified quantity limitation, and the service requirement comprises the requirement of not influencing service continuity; the merging unit determines that the second customer number is a merged customer number under the condition that the merged customer information meets the supervision requirement and the service requirement, and the merged customer information is the customer information of the merged customer number. The device carries out precombination before the customer information is combined, detects whether the combined customer information meets the supervision requirement and the service requirement, determines the combined customer information as the customer information of the combined customer number under the condition of ensuring that the combined customer information meets the supervision requirement and the service requirement, avoids the condition that the customer information of the combined customer number does not meet the supervision requirement and the service requirement, and solves the problem that the customer information combination does not meet the supervision requirement and the service requirement in the prior art.

3) The business system comprises 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 the one or more programs comprise a combination method for executing the client information. The method carries out pre-combination before the customer information combination, detects whether the combined customer information meets the supervision requirement and the service requirement, determines the combined customer information as the customer information of the combined customer number under the condition of ensuring that the combined customer information meets the supervision requirement and the service requirement, avoids that the customer information of the combined customer number does not meet the supervision requirement and the service requirement, and solves the problem that the customer information combination does not meet the supervision requirement and the service requirement in the prior art.

The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like 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 client information, wherein a distributed database comprises a plurality of data fragments, and the data fragments are used for storing client information corresponding to a client number, and the method comprises:

acquiring 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 first customer information to the data fragment 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;

pre-merging the first customer information and the second customer information to obtain merged customer information;

detecting whether the merged customer information meets the supervision requirement and the service requirement, wherein the supervision requirement comprises the requirements of specified quota and specified quantity limitation, and the service requirement comprises the requirement of not influencing service continuity;

and under the condition that the merged customer information meets the supervision requirement and the service requirement, determining that the second customer number is the merged customer number, wherein the merged customer information is the customer information of the merged customer number.

2. The method of claim 1, further comprising:

and sending a notice under the condition that the merged client information does not meet the supervision requirement and the service requirement, wherein the notice is used for prompting the client corresponding to the first client number and the second client number to handle the target service, and the target service is the service corresponding to the client information change which does not meet the supervision requirement and the service requirement.

3. The method of claim 1, wherein migrating first customer information to the data segment in which second customer information is located comprises:

inquiring the data fragment where the first client information is according to the first client number to obtain a first data fragment;

reading the first client information of the first data fragment and generating a client information file according to a naming specification;

uploading the client information file to a file system and acquiring file related information, wherein the file related information comprises a file name and a file path;

inquiring the data fragment where the second client information is according to the second client number to obtain a second data fragment; and downloading the client information file according to the file related information and storing the client information file to the second data fragment.

4. The method of claim 1, wherein detecting whether the consolidated customer information meets regulatory and business requirements comprises:

determining that the merged customer information meets the supervision requirement and the service requirement when the merged customer information does not have violation information and does not influence service continuity, wherein the violation information is an information item which does not meet the supervision requirement;

and if violation information exists in the merged customer information and/or the business continuity is influenced, determining that the merged customer information does not meet the supervision requirement and the business requirement.

5. The method of claim 1, wherein detecting whether the consolidated customer information meets regulatory and business requirements comprises:

detecting whether the same type pricing of the first customer number and the second customer number is consistent or not to obtain a first detection result, wherein the pricing comprises charging pricing and income pricing;

detecting whether the media quantity of the first customer number and the second customer number exceeds a first specified quantity limit or not to obtain a second detection result;

detecting whether the sum of the account numbers of the first customer number and the second customer number exceeds a second specified number limit or not to obtain a third detection result;

and determining whether the merged customer information meets the supervision requirement and the service requirement according to the first detection result, the second detection result and the third detection result.

6. The method of any of claims 1 to 5, wherein prior to migrating the first customer information to the data slice in which the second customer information is located, the method further comprises:

and locking the first client number and the second client number, so that the transaction of the first client number and the second client number is stopped.

7. The method according to any one of claims 1 to 5, wherein after determining that the merged client number is the second client number in a case where the merged client information satisfies regulatory requirements and business requirements, the method further comprises:

and unlocking the merged client number to ensure that the business of the merged client number is returned and transacted.

8. An apparatus for merging client information, wherein a distributed database comprises a plurality of data fragments, and the data fragments are used for storing client information corresponding to a client number, the apparatus comprising:

an acquisition unit configured to acquire a first customer number and a second customer number, the first customer number and the second customer number being different customer numbers of a same customer;

a migration unit, configured to migrate first customer information to the data segment where second customer information is located, where 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;

the pre-merging unit is used for pre-merging the first customer information and the second customer information to obtain merged customer information;

the detection unit is used for detecting whether the merged customer information meets the supervision requirement and the service requirement, wherein the supervision requirement comprises the requirements of specified quota and specified quantity limitation, and the service requirement comprises the requirement of not influencing service continuity;

and the merging unit is used for determining that the second client number is the merging client number under the condition that the merging client information meets the supervision requirement and the service requirement, and the merging client information is the client information of the merging client number.

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

10. A processor, characterized in that the processor is configured to run a program, wherein the program when running performs the method of any of claims 1 to 7.

11. A business system comprising a distributed database, one or more processors, 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, the one or more programs comprising instructions for performing the method of any of claims 1-7.