An account management method, device, equipment and medium

Abstract

The application relates to the field of data processing, in particular to an account management method and device, equipment and medium, which are used to solve the problem of transaction abnormality in a transaction system during account change. The method is applied to a transaction system and comprises the following steps: after receiving an account change message of a client system, searching for first transaction records associated with first account information in a first cluster database; the account change message represents that a same user changes from the first account information to second account information; before changing the first account information in the first transaction records into the second account information, transactions using the first account information and the second account information are prohibited; after generating second transaction records, the second transaction records are stored into a second cluster database; and transactions using the second account information in a second distributed cluster application are allowed, so that the situation that the first account information and the second account information are used in parallel for transactions in the transaction system is avoided.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of data processing, in particular to an account management method and device, equipment and medium. BACKGROUND

[0002] At present, in order to provide better user experience for users in the transaction process, the transaction system usually uses distributed cluster application, and the user determines a distributed cluster application for transaction by the account of the client system, that is, the transaction process of different users is carried by different distributed cluster applications, and each distributed cluster application is connected with a cluster database, which is used to store the transaction record of the user in the transaction process, and at the same time, each distributed cluster application is also connected with the same public database, which is used to store the transaction data shared by each distributed cluster application.

[0003] However, when the user changes the account in the client system, the transaction system cannot change the corresponding transaction account in real time, so that the old account information will be used to carry out transaction in one distributed cluster application of the transaction system and generate transaction record, and at the same time, the new account information will be used to carry out transaction in another distributed cluster application of the transaction system and generate transaction record, which leads to transaction exception. SUMMARY

[0004] The embodiments of the present application provide an account management method, device, equipment and medium, which are used to solve the problem of transaction exception in the account changing process.

[0005] In the first aspect, an account management method is provided, which is applied to a transaction system, the transaction system includes a plurality of distributed cluster applications, and the distributed cluster applications are one-to-one corresponding to cluster databases, and the method comprises the following steps:

[0006] After receiving the account changing message sent by the client system, the first transaction record associated with the first account information is searched in the first cluster database, wherein the account changing message represents that the account of the same user in the client system is changed from the first account information to the second account information, and the first cluster database is the cluster database corresponding to the first distributed cluster application determined according to the first account information;

[0007] If the first transaction record exists, before the second transaction record is generated, the transaction using the first account information and the second account information in each distributed cluster application is prohibited, and after the second transaction record is generated, the second transaction record is stored in the second cluster database, and the transaction using the second account information in the second distributed cluster application is allowed, wherein the second transaction record is generated according to the first transaction record and the second account information, and the second cluster database is the cluster database corresponding to the second distributed cluster application determined according to the second account information.

[0008] In the embodiments of the present application, before the transaction system changes the first account information to the second account information, the scheme of prohibiting using the first account information and the second account information to perform transactions in each distributed cluster application effectively avoids the situation that the first account information and the second account information are used in the transaction system at the same time, and the generated second transaction record is stored in the second cluster database, so that the second account information can be used to perform transactions in the second cluster database after the account is changed, thereby ensuring the integrity of the transaction record after the account is changed and avoiding the occurrence of transaction abnormities.

[0009] In a possible embodiment, the first distributed cluster application is determined in the following manner:

[0010] A preset cluster algorithm is used to determine the first cluster number corresponding to the first account information, and based on the correspondence between the preset cluster number and the cluster application, the first distributed cluster application corresponding to the first cluster number is determined from the plurality of distributed cluster applications.

[0011] The second distributed cluster application is determined in the following manner:

[0012] A preset cluster algorithm is used to determine the second cluster number corresponding to the second account information, and based on the correspondence between the preset cluster number and the cluster application, the second distributed cluster application corresponding to the second cluster number is determined from the plurality of distributed cluster applications.

[0013] The distributed cluster application and the cluster number are in one-to-one correspondence.

[0014] In the embodiments of the present application, through the cluster number and the setting of the correspondence between the cluster number and the cluster application, the distributed cluster application corresponding to the account information can be quickly and efficiently determined, so that in the account change process, the distributed cluster application to which the second account information is to be switched can be quickly and efficiently determined according to the cluster number.

[0015] In a possible embodiment, after receiving the account change message sent by the client system, the first transaction record associated with the first account information is searched in the first cluster database, including:

[0016] After receiving the account change message sent by the client system, the first account information is parsed from the account change message;

[0017] The transaction account associated with the first account information is searched in the preset mapping relationship between the first account information and the transaction account;

[0018] The first transaction record containing the first account information and the transaction account is searched in the first cluster database.

[0019] In the embodiments of the present application, in the process of searching the first transaction record, the transaction account is determined through the mapping relationship between the first account information and the transaction account, that is, the first transaction record associated with the first account information is searched in combination with the unique label in the transaction system, so that the first transaction record can be accurately and quickly determined.

[0020] In a possible embodiment, the second transaction record is generated in the following manner:

[0021] The first account information included in the first transaction record is changed to the second account information, and the changed first transaction record is taken as the second transaction record.

[0022] In the embodiments of the present application, after the first account information included in the first transaction record is changed to the second account information, the second transaction record is generated, the purpose of keeping the historical transaction record for the customer is achieved, and then the second transaction record is stored in the second cluster database, so that the integrity of the transaction record is ensured.

[0023] In a possible embodiment, each distributed cluster application corresponds to the same public database, and the use of the first account information and the second account information in the transaction in each distributed cluster application is prohibited, including:

[0024] Before the transaction using the first account information and the second account information in each distributed cluster application, the transaction authority of the first account information and the second account information is queried from the public database;

[0025] If the first account information and the second account information are prohibited from transaction authority, the transaction content of the first account information and the second account information in the transaction in each distributed cluster application is set to empty.

[0026] In the embodiments of the present application, by setting the transaction authority of the first account information and the second account information in the public database, the transaction content corresponding to the transaction account is empty, so that the transaction of the first account information and the second account information in each distributed cluster application can be quickly and effectively prohibited.

[0027] In a possible embodiment, the use of the second account information in the transaction in the second distributed cluster application is allowed, including:

[0028] The transaction authority of the second account information in the public database is set to the allowed transaction authority, so as to allow the use of the second account information in the transaction in the second distributed cluster application.

[0029] In the embodiments of the present application, by modifying the transaction authority of the second account information to the allowed transaction authority in the public database, the restriction on the transaction of the second account information can be conveniently removed.

[0030] In one possible implementation, the second account information is used to conduct transactions in the second distributed cluster application in the following manner:

[0031] The first account information included in the preset mapping relationship between the first account information and the trading account is changed to the second account information to obtain the mapping relationship between the second account information and the trading account.

[0032] Based on the mapping relationship between the second account information and the transaction account, determine the transaction account corresponding to the second account information;

[0033] Use the transaction account to conduct transactions in the second distributed cluster application.

[0034] In this embodiment of the application, in order to enable customers to use the second account information to conduct new transactions and generate new transaction records, the first account information in the mapping relationship between the first account information and the transaction account is updated to the second account information, thereby assigning the transaction account corresponding to the first account information to the second account information, so as to facilitate the use of the second account information to conduct transactions in the second distributed cluster application.

[0035] Secondly, this application provides an account management device, the device comprising:

[0036] The lookup module is used to search for the first transaction record associated with the first account information in the first cluster database after receiving an account change message from the customer system. The account change message indicates that the account of the same user in the customer system has changed from the first account information to the second account information. The first cluster database is the cluster database corresponding to the first distributed cluster application determined based on the first account information.

[0037] The management module is used to prohibit the use of the first account information and the second account information to conduct transactions in each distributed cluster application before the second transaction record is generated, if a first transaction record exists, and to store the second transaction record in the second cluster database after the second transaction record is generated, allowing the use of the second account information to conduct transactions in the second distributed cluster application. The second transaction record is generated based on the first transaction record and the second account information, and the second cluster database is the cluster database corresponding to the second distributed cluster application determined based on the second account information.

[0038] In one possible implementation, the first distributed cluster application is determined in the following way:

[0039] Using a preset cluster algorithm, the first cluster number corresponding to the first account information is determined, and based on the preset correspondence between the cluster number and the cluster application, the first distributed cluster application corresponding to the first cluster number is determined from multiple distributed cluster applications.

[0040] The second distributed cluster application is determined in the following manner:

[0041] A preset cluster algorithm is used to determine a second cluster number corresponding to the second account information, and based on a preset correspondence between the cluster number and the cluster application, a second distributed cluster application corresponding to the second cluster number is determined from the plurality of distributed cluster applications.

[0042] The distributed cluster application and the cluster number are in one-to-one correspondence.

[0043] In a possible embodiment, the searching module is configured to:

[0044] After receiving the account change message sent by the client system, the first account information is parsed from the account change message;

[0045] The transaction account associated with the first account information is searched in the preset mapping relationship between the first account information and the transaction account.

[0046] The first transaction record containing the first account information and the transaction account is searched in the first cluster database.

[0047] In a possible embodiment, the device further comprises: the second transaction record is generated in the following manner:

[0048] Each first account information included in the first transaction record is changed to the second account information, and the changed first transaction record is taken as the second transaction record.

[0049] In a possible embodiment, the management module is configured to:

[0050] Before the first account information and the second account information are used to perform transactions in each distributed cluster application, the transaction authority of the first account information and the second account information is queried from the public database.

[0051] If it is found that the first account information and the second account information have a prohibited transaction authority, the transaction content of the first account information and the second account information in each distributed cluster application is set to be empty.

[0052] In a third aspect, the application provides an electronic device, comprising:

[0053] A memory configured to store program instructions;

[0054] A processor configured to invoke the program instructions stored in the memory, and perform the steps included in the method of any one of the first aspect according to the obtained program instructions.

[0055] In a fourth aspect, the present application provides a computer readable storage medium, which stores a computer program, the computer program comprising program instructions, when executed by a computer, causing the computer to perform the method of any one of the first aspect.

[0056] In a fifth aspect, the present application provides a computer program product, which comprises computer program code, when the computer program code is run on a computer, causing the computer to perform the method of any one of the first aspect. BRIEF DESCRIPTION OF DRAWINGS

[0057] Figure 1 A schematic diagram of connection of a client system and a transaction system in the prior art;

[0058] Figure 2 A flowchart of an account management method provided by an embodiment of the present application;

[0059] Figure 3 A flowchart of determining a first transaction record based on an account change message provided by an embodiment of the present application;

[0060] Figure 4 A flowchart of prohibiting transaction using first account information and second account information provided by an embodiment of the present application;

[0061] Figure 5 A flowchart of allowing transaction using second account information in a second distributed cluster application provided by an embodiment of the present application;

[0062] Figure 6 A structural diagram of an account management device provided by an embodiment of the present application;

[0063] Figure 7 A structural diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0064] In order to make the objectives, technical solutions and advantages of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work fall within the scope of protection of the present application. In the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other at will. Moreover, although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that here.

[0065] The terms "first" and "second" in the specification and claims of the present application and the above drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the term "comprising" and any variations thereof are intended to cover non-exclusive protection. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but can optionally include steps or units not listed, or can optionally include other steps or units inherent to the process, method, product or device. "Multiple" in the present application can mean at least two, for example, can be two, three or more, and the embodiments of the present application are not limited.

[0066] The exemplary embodiments of the present application are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present application to assist in understanding, and should be considered as merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope of the present disclosure. Also, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description. It should be noted that in the embodiments of the present application, some software, components, models and the like may be mentioned, which should be considered as exemplary, and the purpose is only to illustrate the feasibility of the implementation of the technical solutions of the present application, but does not mean that the applicant has or must have used the scheme.

[0067] In the technical solutions of the present application, the acquisition, transmission, storage and use of data comply with the requirements of relevant national laws and regulations.

[0068] Before introducing the account management method provided by the embodiments of the present application, in order to facilitate understanding, the technical background of the embodiments of the present application is first introduced in detail.

[0069] In order to provide better user experience for users in the transaction process, the transaction system usually uses distributed cluster application, please refer to Figure 1 The transaction system is connected with the customer system, and the transaction system receives account information from the customer system. The transaction system determines the transaction account according to the above-mentioned account information, so that the user can transact in the transaction system. The above-mentioned transaction system includes a plurality of distributed cluster applications, a plurality of cluster databases and a public database, the distributed cluster application and the cluster database are one-to-one corresponding, for example, Figure 1 The first distributed cluster application in the above-mentioned transaction system is connected with the first cluster database, the second distributed cluster application is connected with the second cluster database, and the Nth distributed cluster application is connected with the Nth cluster database.

[0070] The cluster database is a private database of a distributed cluster application connected thereto, and is used to store transaction records of account information for transactions in the distributed cluster application. In the implementation process, a distributed cluster application is determined by the account of the user in the client system to perform transactions, that is, the transaction processes of different users are carried out by different distributed cluster applications, and each distributed cluster application is connected to a cluster database. Meanwhile, each distributed cluster application is also connected to the same public database, and the public database is used to store transaction data shared by each distributed cluster application.

[0071] However, when the user changes the account in the client system, the transaction system cannot change the corresponding transaction account in real time. For example, when the account of the user in the client system is changed from account A to account B, the transaction system is in a transaction peak period (assuming 10:00-15:00). In this case, the transaction system will not modify the related records of the transaction system according to the message that the account A is changed to the account B immediately, but will modify the account A in the transaction record of the account A to the account B until the transaction off-peak period (assuming 16:00-24:00). Before the above-mentioned receiving of the change message to the arrival of the transaction off-peak period, the transaction system will directly determine another distributed cluster application according to the account B and perform transactions in another distributed cluster application. Thus, the same user's account A will perform transactions in one distributed cluster application of the transaction system and generate transaction records, and at the same time, the user's account B will perform transactions in another distributed cluster application of the transaction system and generate transaction records, resulting in transaction abnormalities.

[0072] In order to solve the problem of transaction abnormalities in the transaction system in the above-mentioned account changing process, an account management method is proposed in the embodiments of the present application. The preferred embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0073] An account management method is proposed in the embodiments of the present application. The above-mentioned account management method is applied to a transaction system. It should be noted that the transaction system in the present application is the same as the transaction system in the prior art, and its connection mode with the client system is described in the above-mentioned Figure 1 , which will not be described here. The implementation steps of the account management method will be described in detail below with reference to Figure 2 , which will not be described here. The implementation steps of the account management method will be described in detail below with reference to

[0074] Step 201: After receiving the account change message sent by the client system, the first transaction record associated with the first account information is searched in the first cluster database, wherein the account change message represents that the account of the same user in the client system is changed from the first account information to the second account information, and the first cluster database is the cluster database corresponding to the first distributed cluster application determined according to the first account information.

[0075] First of all, the account information of the client system is usually determined according to the user's identity card number and the user's name, and the above-mentioned account information has uniqueness in the client system, only when the user has the account information, the user is allowed to trade in the transaction system, when the user's account information in the client system is changed, the client system will send the account change message to the transaction system immediately, for example, the transaction system obtains the account change message from the client system through subscription.

[0076] In the implementation process, after the transaction system receives the user's account information, it will first determine the distributed cluster application used for transaction according to the account information. Considering that the above-mentioned account change message represents that the account of the same user in the client system is changed from the first account information to the second account information, that is, the old account of the user is the first account information, and the new account of the user is the second account information. The following will introduce the determination process of the distributed cluster application combined with the first account information and the second account information.

[0077] (1) After receiving the first account information of the client system, the transaction system determines the first distributed cluster application by the following way:

[0078] A preset cluster algorithm is used to determine the first cluster number corresponding to the first account information, and based on the preset correspondence between the cluster number and the cluster application, the first distributed cluster application corresponding to the first cluster number is determined from the multiple distributed cluster applications. It should be noted that the distributed cluster application is one-to-one corresponding to the cluster number.

[0079] In the implementation process, considering that the transaction process to be processed by the transaction system is large, and the transaction system includes multiple distributed cluster applications. After the transaction system receives the first account information of the client system, the first cluster number corresponding to the first account information is calculated by using the preset cluster algorithm, and each preset cluster number will be pre-established one-to-one correspondence with each distributed cluster application. After the first cluster number is calculated, one distributed cluster application is determined from the multiple distributed cluster applications according to the above-mentioned correspondence, that is, the first distributed cluster application is found in the multiple distributed cluster applications according to the first cluster number. In this way, the user corresponding to the first account information can trade in the first distributed cluster application.

[0080] (2) After receiving the second account information of the client system, the transaction system determines the second distributed cluster application by the following way:

[0081] The preset cluster algorithm is used to determine the second cluster number corresponding to the second account information, and based on the preset cluster number and the corresponding relationship of the cluster application, the second distributed cluster application corresponding to the second cluster number is determined from the plurality of distributed cluster applications. It should be noted that the distributed cluster application corresponds to the cluster number one by one.

[0082] Similarly, after the transaction system receives the second account information of the client system, the preset cluster algorithm is used to calculate the second cluster number corresponding to the second account information, and each preset cluster number is pre-established in one-to-one correspondence with each distributed cluster application. After calculating the second cluster number, a distributed cluster application is determined from the plurality of distributed cluster applications according to the above-mentioned corresponding relationship, that is, the second distributed cluster application is found in the plurality of distributed cluster applications according to the second cluster number. In this way, the user corresponding to the second account information can perform transactions in the second distributed cluster application.

[0083] In order to maintain the integrity and uniqueness of the transaction record, after the client system sends the account change message, the first transaction record associated with the first account information needs to be changed to the second transaction record and then stored in the second distributed cluster application. Therefore, in the implementation process, after the first distributed cluster application is determined according to the first account information in the account change message, the first transaction record needs to be further determined.

[0084] For example, after receiving the account change message sent by the client system, the first transaction record associated with the first account information is searched in the first cluster database. Referring to Figure 3 As shown in the figure, it includes:

[0085] Step 2011: After receiving the account change message sent by the client system, the first account information is parsed from the account change message.

[0086] Considering that the above-mentioned account change message includes the first account information before the change and the second account information after the change, in the implementation process, the transaction system will parse the first account information before the change from the account change message after receiving the account change message sent by the client system.

[0087] For example, the format of the account change message is preset as account change message 1 = first account information + second account information, so in the parsing process, the first account information before the plus sign "+" in the account change message 1 can be directly parsed.

[0088] For another example, the format of the account change message is preset as account change message 2 = second account information replaced by first account information, so in the parsing process, the first account information after the Chinese character "be" in the account change message 2 can be directly parsed.

[0089] Step 2012: find the transaction account associated with the first account information in the mapping relationship between the preset first account information and the transaction account.

[0090] The transaction system is essentially generated according to the transaction record, that is, the same user in the transaction system corresponds to a transaction account, the first account information of the client system and the transaction account of the transaction system one-to-one, and the mapping relationship between the first account information and the transaction account is established according to the first account information of the client system and the transaction account of the transaction system. In the implementation process, after the first account information is parsed from the account change message, the first account information is found in the above mapping relationship between the first account information and the transaction account, and the transaction account associated with the found first account information is further determined.

[0091] Step 2013: find the first transaction record containing the first account information and the transaction account in the first cluster database.

[0092] In the implementation process, after the first account information and the transaction account are determined, the first account information and the transaction account are searched in the plurality of transaction records in the first cluster database of the first distributed cluster application, and the transaction record containing the first account information and the transaction account is determined as the first transaction record.

[0093] Step 202: if the first transaction record exists, before the second transaction record is generated, the first account information and the second account information are prohibited from being used to transact in each distributed cluster application, and after the second transaction record is generated, the second transaction record is stored in the second cluster database, and the second account information is allowed to be used to transact in the second distributed cluster application, wherein the second transaction record is generated according to the first transaction record and the second account information, and the second cluster database is the cluster database corresponding to the second distributed cluster application determined according to the second account information.

[0094] In the implementation process, after it is determined that the first transaction record exists in the first cluster database, it means that the user corresponding to the first account information is not a new user. After the transaction system receives the account change message, the first transaction record needs to be changed to the second transaction record accordingly, and the second transaction record needs to be stored in the second cluster database corresponding to the second distributed cluster application accordingly, so as to ensure the integrity and uniqueness of the transaction record.

[0095] It needs to be supplemented that the second transaction record is generated in the following way:

[0096] Change each first account information included in the first transaction record to the second account information, and change the changed first transaction record to the second transaction record.

[0097] Since the transaction record represents the account information of the user in the transaction process of the transaction system, in order to avoid transaction abnormalities, the transaction system only allows to store one transaction record for the same user, so that when the account information of the user is changed, the original transaction record of the user will be rewritten as a record associated with the new account, and the rewritten transaction record will also be stored in the distributed cluster application running in real time of the new account.

[0098] In the implementation process, after the first transaction record is found, each first account information is determined from the above first transaction record, and each first account information is changed to second account information accordingly, so that the first transaction record includes second account information, transaction account and other transaction related information. The transaction record including the second account information and the transaction account after the above change is taken as the second transaction record.

[0099] Considering the lag of the transaction system in processing the account change message, that is, before all the first account information included in the first transaction record is changed to the second account information, in order to avoid transaction abnormalities, the use of the first account information and the second account information in the transaction of each distributed cluster application is prohibited in the embodiment of the application.

[0100] Exemplarily, each distributed cluster application corresponds to the same public database, and the use of the first account information and the second account information in the transaction of each distributed cluster application is prohibited, as shown in Figure 4 , including:

[0101] Step 2021: Before using the first account information and the second account information to perform transactions in each distributed cluster application, querying the transaction authority of the first account information and the second account information from the public database.

[0102] Before all the first account information included in the first transaction record is changed to the second account information, in the implementation process, if the user wants to use the first account information or the second account information to perform transactions in each distributed cluster application, the transaction authority of the first account information and the transaction authority of the second account information need to be queried from the above public database before the transaction.

[0103] Generally, the above transaction authority is divided into allowed transaction authority and prohibited transaction authority, for example, when the first account information is allowed transaction authority, that is, the user can use the first account information to perform transactions in the corresponding distributed cluster application; for another example, when the first account information is prohibited transaction authority, that is, the user cannot use the first account information to perform transactions in the corresponding distributed cluster application, that is, the transaction content of the user using the first account information for transaction is set to be empty.

[0104] It should be noted that, since different account information of a user corresponds to different distributed cluster applications, the above transaction permission is usually stored in the public database for easy query.

[0105] Step 2022: If it is found that the first account information and the second account information are prohibited transaction permissions, set the transaction content of the first account information and the second account information in each distributed cluster application to be empty.

[0106] In the implementation process, if it is found from the public database that the first account information and the second account information are prohibited transaction permissions, the above transaction permission is the transaction permission set by the transaction system for the first account information and the second account information before the first transaction record is changed to the second account information, then the transaction content of the first account information and the second account information in each distributed cluster application is set to be empty, i.e. the first account information and the second account information are not allowed to be used for transaction.

[0107] It should be noted that, if it is found from the public database that the transaction permission of the first account information and the second account information is not prohibited transaction permission before the first transaction record is changed to the second account information, the transaction permission of the first account information and the second account information will be set to prohibited transaction permission again, so that the first account information and the second account information are not allowed to be used for transaction.

[0108] After receiving the account change message, but before the transaction system changes the first transaction record to the second account information (for example, the transaction low peak period of the transaction system has not been reached), the transaction system prohibits the use of the first account information and the second account information in the distributed cluster application by controlling the transaction permission. But in order to ensure the synchronization with the customer system and the normal operation of the transaction system, the transaction system will also change the first transaction record to the second account information after reaching the preset condition (for example, the transaction low peak period), so as to obtain the second transaction record, at the same time, in order to ensure the integrity of the transaction record, the above obtained second transaction record will also be stored in the second cluster database, and the use of the second account information in the second distributed cluster application is allowed.

[0109] Referring to Figure 5 The above allowing the use of the second account information in the second distributed cluster application includes:

[0110] Step 2023: Set the transaction permission of the second account information to the public database to be allowed transaction permission, so as to allow the use of the second account information in the second distributed cluster application.

[0111] In the implementation process, after the second transaction record is stored in the second cluster database, it indicates that the transaction system has completely changed the first account information to the second account information, and the first account information is invalid for the transaction system. Then, the transaction permission of the second account information is set to the permission of transaction in the public database, thereby releasing the restriction on the transaction of the second account information. Since the distributed cluster application determined according to the second account information is the second distributed cluster application, the transaction of the second account information in the second distributed cluster application is allowed.

[0112] Exemplarily, the transaction of the second account information in the second distributed cluster application is performed in the following manner:

[0113] 1) The first account information in the preset mapping relationship between the first account information and the transaction account is changed to the second account information, to obtain a mapping relationship between the second account information and the transaction account.

[0114] Considering that the user will also use the second account information to perform a new transaction in the second distributed cluster application and generate a new transaction record, in the embodiment of the application, the first account information in the preset mapping relationship between the first account information and the transaction account is changed to the second account information, that is, the mapping relationship is updated, to obtain a mapping relationship between the second account information and the transaction account.

[0115] 2) Based on the mapping relationship between the second account information and the transaction account, the transaction account corresponding to the second account information is determined.

[0116] After obtaining the mapping relationship between the second account information and the transaction account, the transaction account corresponding to the second account information is searched in the mapping relationship. In this way, the user also has a transaction account in the second distributed cluster application. It should be noted that the transaction account corresponding to the first account information is the same, thereby ensuring that a same customer has only one transaction account in the transaction system.

[0117] 3) The transaction account is used to perform a transaction in the second distributed cluster application.

[0118] In the implementation process, after the customer has a transaction account in the second distributed cluster application, the user can use the transaction account to perform a transaction in the second distributed cluster application and generate a new transaction record. The new transaction record is stored in the second cluster database of the second distributed cluster application together with the second transaction record, thereby constituting all transaction records of the user.

[0119] The account management method provided in the embodiments of the present application specifically comprises: after receiving an account change message that an account of a same user in a client system is changed from first account information to second account information sent by the client system, searching for first transaction records associated with the first account information in a first cluster database; if the first transaction records exist, before second transaction records are generated, prohibiting transactions in each distributed cluster application using the first account information and the second account information; and after the second transaction records are generated, storing the second transaction records into a second cluster database and allowing transactions in a second distributed cluster application using the second account information. The scheme of prohibiting transactions in each distributed cluster application using the first account information and the second account information before the first account information is changed to the second account information in the transaction system effectively avoids the situation that the first account information and the second account information simultaneously perform transactions in the transaction system, and the generated second transaction records are stored into the second cluster database to allow transactions in the second distributed cluster application using the second account information, so that after the account change is completed, transactions using the second account information are allowed, and on the basis of ensuring the completeness of transaction records after the account change, the normal operation of transactions is ensured.

[0120] Based on the same inventive concept, the embodiments of the present application provide an account management device, please refer to Figure 6 The device comprises:

[0121] The searching module 601 is configured to search for first transaction records associated with the first account information in a first cluster database after receiving an account change message sent by the client system, wherein the account change message indicates that an account of a same user in a client system is changed from first account information to second account information, and the first cluster database is a cluster database corresponding to a first distributed cluster application determined according to the first account information.

[0122] The management module 602 is configured to, if the first transaction records exist, prohibit transactions in each distributed cluster application using the first account information and the second account information before the second transaction records are generated, and after the second transaction records are generated, store the second transaction records into a second cluster database and allow transactions in a second distributed cluster application using the second account information, wherein the second transaction records are generated according to the first transaction records and the second account information, and the second cluster database is a cluster database corresponding to a second distributed cluster application determined according to the second account information.

[0123] In a possible embodiment, the device further comprises: determining the first distributed cluster application by:

[0124] The preset cluster algorithm is used to determine a first cluster number corresponding to the first account information, and based on a preset correspondence between the cluster number and the cluster application, a first distributed cluster application corresponding to the first cluster number is determined from the plurality of distributed cluster applications.

[0125] The second distributed cluster application is determined in the following manner:

[0126] The preset cluster algorithm is used to determine a second cluster number corresponding to the second account information, and based on a preset correspondence between the cluster number and the cluster application, a second distributed cluster application corresponding to the second cluster number is determined from the plurality of distributed cluster applications.

[0127] The distributed cluster application and the cluster number are in one-to-one correspondence.

[0128] In a possible embodiment, the apparatus further includes a searching module 601 configured to:

[0129] After receiving the account change message sent by the client system, the first account information is parsed from the account change message;

[0130] The transaction account associated with the first account information is searched in the preset mapping relationship between the first account information and the transaction account;

[0131] The first transaction record containing the first account information and the transaction account is searched in the first cluster database.

[0132] In a possible embodiment, the apparatus further includes that the second transaction record is generated in the following manner:

[0133] Each first account information included in the first transaction record is changed to the second account information, and the changed first transaction record is taken as the second transaction record.

[0134] In a possible embodiment, the apparatus further includes that the management module 602 is configured to:

[0135] Before the first account information and the second account information are used to perform transactions in each distributed cluster application, the transaction authority of the first account information and the second account information is queried from the public database;

[0136] If it is found that the first account information and the second account information are prohibited from transaction, the transaction content of the first account information and the second account information in each distributed cluster application is set to be empty.

[0137] Based on the same inventive concept, the embodiments of the present application provide an electronic device which can realize the functions of the account management apparatus discussed above, please refer to Figure 7 The device includes a processor 701 and a memory 702.

[0138] The memory 702 is configured to store computer programs executed by the processor 701. The memory 702 can mainly include a program storage area and a data storage area. The program storage area can store an operating system and programs required for running the instant messaging function, etc. The data storage area can store various instant messaging information and operation instruction sets, etc.

[0139] The memory 702 can be a volatile memory, for example, a random-access memory (RAM). The memory 702 can also be a non-volatile memory, for example, a read-only memory, a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD), or the memory 702 can be any other medium capable of carrying or storing desired program codes in the form of instructions or data structures and capable of being accessed by a computer, but is not limited to this. The memory 702 can be a combination of the above memories.

[0140] The processor 701 can include one or more central processing units (CPUs) or digital processing units, etc. The processor 701 is configured to invoke the computer programs stored in the memory 702 to implement the above account management method.

[0141] Based on the same inventive concept, the embodiments of the present application provide a computer readable storage medium, and a computer program product. The computer program product includes computer program codes, which, when executed on a computer, cause the computer to perform any of the account management methods discussed in the foregoing. Since the principle of the computer readable storage medium for solving the problem is similar to the account management method, the implementation of the computer readable storage medium can be referred to the implementation of the method, and the repeated parts will not be described herein.

[0142] Based on the same inventive concept, the embodiments of the present application further provide a computer program product. The computer program product includes computer program codes, which, when executed on a computer, cause the computer to perform any of the account management methods discussed in the foregoing. Since the principle of the computer program product for solving the problem is similar to the account management method, the implementation of the computer program product can be referred to the implementation of the method, and the repeated parts will not be described herein.

[0143] Those skilled in the art will appreciate that embodiments of the application can be devised for a method, a system, or a computer program product. Accordingly, the present application can be embodied in the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage devices, and the like) embodying computer readable program code.

[0144] The present application is described in reference to the flowchart illustrations and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams.

[0145] These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams.

[0146] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams.

[0147] Obviously, numerous modifications and variations of the present application are possible in light of the above teachings. It is therefore to be understood that within the scope of the apparent to those skilled in the art that various modifications and changes can be made thereto without departing from the scope and spirit of the present application. It is intended that the scope of the present application be limited only by the appended claims, and their equivalents.

Claims

1. An account management method, characterized by, The method is applied to a transaction system, the transaction system comprising a plurality of distributed cluster applications, the distributed cluster applications corresponding to cluster databases one by one, and the method comprising: after receiving an account change message issued by a client system, searching for a first transaction record associated with first account information in a first cluster database, wherein the account change message represents that an account of a same user in the client system is changed from the first account information to second account information, and the first cluster database is a cluster database corresponding to a first distributed cluster application determined according to the first account information; if the first transaction record exists, before a second transaction record is generated and before transactions are performed in each of the distributed cluster applications using the first account information and the second account information, querying transaction permissions of the first account information and the second account information from a common database, if it is queried that the first account information and the second account information are prohibited from transaction permissions, setting transaction contents of the first account information and the second account information in transactions performed in each of the distributed cluster applications as null, and after the second transaction record is generated, storing the second transaction record into a second cluster database, and allowing transactions to be performed in a second distributed cluster application using the second account information, wherein the second transaction record is generated according to the first transaction record and the second account information, the second cluster database is a cluster database corresponding to the second distributed cluster application determined according to the second account information, and each of the distributed cluster applications corresponds to a same common database.

2. The method of claim 1, wherein, The first distributed cluster application is determined in the following manner: a first cluster number corresponding to the first account information is determined by using a preset cluster algorithm, and the first distributed cluster application corresponding to the first cluster number is determined from the plurality of distributed cluster applications based on a preset correspondence between cluster numbers and cluster applications. The second distributed cluster application is determined in the following manner: a second cluster number corresponding to the second account information is determined by using a preset cluster algorithm, and the second distributed cluster application corresponding to the second cluster number is determined from the plurality of distributed cluster applications based on a preset correspondence between cluster numbers and cluster applications. The distributed cluster applications correspond to the cluster numbers one by one.

3. The method of claim 1, wherein, After receiving the account change message issued by the client system, the first transaction record associated with the first account information is searched for in the first cluster database, comprising: after receiving the account change message issued by the client system, the first account information is parsed from the account change message; a transaction account associated with the first account information is searched for in a preset mapping relationship between first account information and transaction accounts; the first transaction record containing the first account information and the transaction account is searched for in the first cluster database.

4. The method of claim 1, wherein, The second transaction record is generated in the following manner: Change the first account information included in the first transaction record into second account information, and store the first transaction record after the change as the second transaction record.

5. The method of claim 3, wherein, The allowing of the use of the second account information to conduct transactions in the second distributed cluster application comprises: Setting the transaction authority of the second account information in the public database to an allowed transaction authority to allow the use of the second account information to conduct transactions in the second distributed cluster application.

6. The method of claim 5, wherein, The use of the second account information to conduct transactions in the second distributed cluster application is performed by: Changing the first account information included in the preset mapping relationship between the first account information and transaction account into second account information to obtain a mapping relationship between second account information and transaction account; Based on the mapping relationship between the second account information and the transaction account, determining the transaction account corresponding to the second account information; Using the transaction account to conduct transactions in the second distributed cluster application.

7. An account management apparatus characterized by comprising: The device comprises: The finding module is configured to find, after receiving an account change message issued by a client system, a first transaction record associated with first account information in a first cluster database, wherein the account change message indicates that the account of a same user in the client system is changed from the first account information to second account information, and the first cluster database is a cluster database corresponding to a first distributed cluster application determined according to the first account information. The management module is configured to, if the first transaction record exists, before a second transaction record is generated and before transactions are conducted in each of the distributed cluster applications using the first account information and the second account information, query the transaction authority of the first account information and the second account information from a public database, set the transaction content of the transactions conducted in each of the distributed cluster applications using the first account information and the second account information to be empty if the first account information and the second account information are found to be prohibited transaction authorities, and after the second transaction record is generated, store the second transaction record in a second cluster database to allow the use of the second account information to conduct transactions in a second distributed cluster application, wherein the second transaction record is generated according to the first transaction record and the second account information, the second cluster database is a cluster database corresponding to a second distributed cluster application determined according to the second account information, and each of the distributed cluster applications corresponds to a same public database.

8. The apparatus of claim 7, wherein, The first distributed cluster application is determined by: Using a preset cluster algorithm to determine a first cluster number corresponding to the first account information, and based on a preset correspondence between cluster numbers and cluster applications, determining the first distributed cluster application corresponding to the first cluster number from a plurality of distributed cluster applications. The second distributed cluster application is determined by: The preset cluster algorithm is used to determine a second cluster number corresponding to the second account information, and based on a preset correspondence between the cluster number and the cluster application, the second distributed cluster application corresponding to the second cluster number is determined from the plurality of distributed cluster applications. The distributed cluster application corresponds to the cluster number one by one.

9. The apparatus of claim 7, wherein, The search module is configured to: After receiving the account change message sent by the customer system, parse the first account information from the account change message; Find the transaction account associated with the first account information in the preset mapping relationship between the first account information and the transaction account; Find the first transaction record containing the first account information and the transaction account in the first cluster database.

10. The apparatus of claim 7, wherein, The second transaction record is generated by: Changing each first account information included in the first transaction record to second account information, and taking the changed first transaction record as the second transaction record.

11. An electronic device, comprising: It includes: A memory for storing program instructions; The processor is configured to call the program instructions stored in the memory, and execute the steps included in the method according to the obtained program instructions.

12. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, and the computer program includes program instructions, which, when executed by a computer, cause the computer to execute the method as claimed in any one of claims 1-6.

13. A computer program product, characterised in that, The computer program product includes: computer program code, when the computer program code runs on the computer, makes the computer execute the method as claimed in any one of claims 1-6.

Images