CN117235046A

CN117235046A - Account migration data updating method and device, computer equipment and storage medium

Info

Publication number: CN117235046A
Application number: CN202311214075.5A
Authority: CN
Inventors: 庞以新; 廖远忠; 马林; 廖国翔; 胡蝶颖
Original assignee: CCB Finetech Co Ltd
Current assignee: CCB Finetech Co Ltd
Priority date: 2023-09-19
Filing date: 2023-09-19
Publication date: 2023-12-15

Abstract

The application relates to an account migration data updating method, an account migration data updating device, computer equipment, a storage medium and a computer program product, and relates to the technical field of big data. The method comprises the following steps: acquiring an account migration data table; requesting to acquire the migrated identity of the target user list, and acquiring a migrated identity array; and updating the current identity of any user in the account migration data table to be the migrated identity and updating the processing identity of any user in the account migration data table to be migrated under the condition that the migrated identity corresponding to any user exists in the migrated identity array aiming at any user in each target user list. By adopting the method, the data migration efficiency of account migration can be improved.

Description

Account migration data updating method and device, computer equipment and storage medium

Technical Field

The present application relates to the field of big data technologies, and in particular, to a method, an apparatus, a computer device, a storage medium, and a computer program product for updating account migration data.

Background

When the subject name of the service object is changed, the subject of the service handling public number in the instant messaging software also needs to be changed, the service handling public number does not support direct modification of the public number platform subject, and the influence on service propaganda and handling functions is reduced for keeping the concerned users in the service handling public number, so that the public number account number of the service handling public number needs to be migrated, and the stable change of the subject is realized. Wherein the business object comprises a financial institution such as a bank.

During the verification of the account migration request, if the user who has paid attention to the public number cancels the attention, the conversion interface of the instant messaging software cannot normally return a new identity identifier, such as openid, for the user in the migration process, and further the conversion task is forcibly stopped by manual intervention, so that the interruption of the migration task is caused, and the data migration efficiency of the account migration by the business handling public number is greatly reduced.

Disclosure of Invention

In view of the foregoing, it is desirable to provide an account migration data updating method, apparatus, computer device, computer readable storage medium and computer program product that can improve the data migration efficiency of account migration.

In a first aspect, the application provides an account migration data updating method. The method comprises the following steps:

acquiring an account migration data table; the account migration data table is used for indicating that the concerned users in the business handling public numbers before migration are migrated to the business handling public numbers after migration; the account migration data table comprises pre-migration identity identifiers and processing identifiers corresponding to the concerned users; the identity before migration is the identity in the business handling public number of the concerned user before migration; the process identifies a migration state for characterizing the user of interest;

Requesting to acquire the migrated identity of the target user list, and acquiring a migrated identity array; the target user list comprises a preset batch number of the concerned users with the processing identification not migrated; the migrated identity is the identity of the concerned user in the migrated business handling public number;

and updating the current identity of any user in the account migration data table to be the migrated identity and updating the processing identity of any user in the account migration data table to be migrated under the condition that the migrated identity corresponding to the any user exists in the migrated identity array aiming at any user in each target user list.

In one embodiment, the method further comprises:

acquiring verification preparation data of any user in the account migration data table; the verification preparation data comprise the current identity and the historical identity of the any user in the account migration data table;

consistency verification is carried out on the current identity and the historical identity, and a verification result is obtained;

And updating the processing identification of any user in the account migration data table to be not migrated under the condition that the verification result is that the information of the new user and the old user is inconsistent.

In one embodiment, the method further comprises:

and under the condition that the post-migration identity corresponding to any user exists in the post-migration identity array, updating the historical identity of the any user in the account migration data table to be the pre-migration identity.

In one embodiment, before the step of obtaining the account migration data table, the method further includes:

acquiring a data record before migration; the pre-migration data record is used for updating the account migration data table;

under the condition that the data record acquisition before migration is completed, submitting a migration audit request aiming at the service handling public number to a management platform of the service handling public number;

the migration checking request is used for requesting the management platform to check whether the concerned user in the pre-migration business handling public numbers can be migrated to the post-migration business handling public numbers.

In one embodiment, the method further comprises:

Receiving the migration audit passing instruction fed back by the management platform according to the migration audit request;

and responding to the migration audit passing instruction, executing the step of requesting to acquire the migrated identity of the target user list and obtaining a migrated identity array.

In one embodiment, the obtaining the migrated identity of the target user list to obtain the migrated identity array includes:

screening the target user list from the concerned users recorded in the account migration data table according to the preset batch number;

calling a preset identification conversion interface according to the pre-migration identification corresponding to each user in the target user list so as to enable the preset identification conversion interface to return to the post-migration identification corresponding to each user in the target user list;

and obtaining the migrated identity identification array according to the returned result of the preset identity conversion interface.

In one embodiment, the method further comprises:

and under the condition that the migrated identity corresponding to any user does not exist in the migrated identity array, updating the processing identification of any user in the account migration data table to be unnecessary to migrate.

In a second aspect, the application further provides an account migration data updating device. The device comprises:

the data table acquisition module is used for acquiring an account migration data table; the account migration data table is used for indicating that the concerned users in the business handling public numbers before migration are migrated to the business handling public numbers after migration; the account migration data table comprises pre-migration identity identifiers and processing identifiers corresponding to the concerned users; the identity before migration is the identity in the business handling public number of the concerned user before migration; the process identifies a migration state for characterizing the user of interest;

the post-migration identity request module is used for requesting to acquire the post-migration identity of the target user list and obtaining a post-migration identity array; the target user list comprises a preset batch number of the concerned users with the processing identification not migrated; the migrated identity is the identity of the concerned user in the migrated business handling public number;

the data table updating module is used for updating the current identity of any user in the account number migration data table to be the migrated identity and updating the processing identity of the any user in the account number migration data table to be migrated when the migrated identity corresponding to the any user exists in the migrated identity array for any user in each target user list.

In one embodiment, the apparatus further comprises:

the verification data acquisition module is used for acquiring verification preparation data of any user in the account migration data table; the verification preparation data comprise the current identity and the historical identity of the any user in the account migration data table;

the verification module is used for carrying out consistency verification on the current identity mark and the historical identity mark to obtain a verification result;

and the first processing identifier updating module is used for updating the processing identifier of any user in the account migration data table to be not migrated under the condition that the verification result is that the information of the new user is inconsistent with the information of the old user.

In one embodiment, the apparatus further comprises:

and the history identification updating module is used for updating the history identification of the any user in the account number migration data table to be the identification before migration under the condition that the identification after migration corresponding to the any user exists in the identification after migration array.

In one embodiment, the apparatus further comprises:

the data record acquisition module is used for acquiring the data record before migration; the pre-migration data record is used for updating the account migration data table;

The migration audit request submitting module is used for submitting a migration audit request aiming at the service handling public number to the management platform of the service handling public number under the condition that the data record acquisition before migration is completed;

In one embodiment, the apparatus further comprises:

the migration audit passing instruction receiving module is used for receiving the migration audit passing instruction fed back by the management platform according to the migration audit request;

and the migration audit passing instruction execution module is used for responding to the migration audit passing instruction, executing the step of requesting to acquire the migrated identity of the target user list and obtaining a migrated identity array.

In one embodiment, the post-migration identity request module includes:

the target user list batch acquisition module is used for screening the target user list from the concerned users recorded in the account migration data table according to the preset batch number;

The identification conversion interface calling module is used for calling a preset identification conversion interface according to the pre-migration identification corresponding to each user in the target user list so as to enable the preset identification conversion interface to return the post-migration identification corresponding to each user in the target user list;

and the array acquisition module is used for acquiring the migrated identity identification array according to the returned result of the preset identity conversion interface.

In one embodiment, the apparatus further comprises:

and the second processing identifier updating module is used for updating the processing identifier of any user in the account number migration data table to be unnecessary to migrate under the condition that the migrated identity corresponding to any user does not exist in the migrated identity array.

In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor which when executing the computer program performs the steps of:

In a fourth aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:

In a fifth aspect, the present application also provides a computer program product. The computer program product comprises a computer program which, when executed by a processor, implements the steps of:

According to the account migration data updating method, the device, the computer equipment, the storage medium and the computer program product, the account migration data table is firstly obtained, then the migrated identity of the target user list is requested to be obtained, the migrated identity array is obtained, finally under the condition that the migrated identity exists in the migrated identity array, the current identity of any user is updated to be the migrated identity, the processing identity of any user is updated to be migrated, the migrated identity is completed according to the state of the processing identity, the processing identity is readjusted after the data updating is completed to change the migration state, the migrated user is accurately distinguished from the user without the migration, the influence of the interrupt of the migration task caused by the cancellation of attention of the user in the migration checking process on batches is avoided, the unprocessed data can be automatically restarted and accurately screened out to continue processing when the task is interrupted, the continuous processing of the task is ensured, and the technical effect of improving the data migration efficiency of the account migration by handling public number is obtained.

Drawings

FIG. 1 is an application environment diagram of an account migration data update method in one embodiment;

FIG. 2 is a flowchart of a method for updating account migration data in one embodiment;

fig. 3 is a flowchart of a method for updating account migration data in another embodiment;

fig. 4 is a flowchart of a method for updating account migration data in another embodiment;

FIG. 5 is a schematic flow chart of an account migration data updating method in one embodiment;

FIG. 6 is a block diagram of an account migration data update apparatus in one embodiment;

FIG. 7 is an internal block diagram of a computer device in one embodiment;

fig. 8 is an internal structural view of a computer device in another embodiment.

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards of the related country and region.

It should be noted that the account migration data updating method, the device, the computer equipment, the storage medium and the computer program product disclosed by the application can be applied to the field of financial science and technology, and can also be applied to any field except the field of financial science and technology.

The account migration data updating method provided by the embodiment of the application can be applied to an application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network.

The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices, and portable wearable devices, where the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart vehicle devices, and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The server 104 may be implemented as a stand-alone server or as a server cluster of multiple servers.

In one embodiment, as shown in fig. 2, an account migration data updating method is provided, and the method is applied to the terminal 102 in fig. 1 for illustration, and includes the following steps:

s201, acquiring an account migration data table.

The account migration data table is used for indicating that the concerned user in the business handling public numbers before migration is migrated to the business handling public numbers after migration; the account migration data table comprises pre-migration identity identifiers and processing identifiers corresponding to the concerned users; the identity before migration is the identity in the public number of the business transaction before migration of the concerned user; the process identifies a migration state used to characterize the user of interest; the business handling public number is used for the concerned users to handle business to business objects in the instant messaging software, and the business objects comprise financial institutions such as banks.

The account migration data table is a member table in instant messaging software, which may be simply referred to as a member table, and includes public number app id, public number openid, processing identifier, and original public number openid fields; wherein the values of the process identifier include, but are not limited to, 0, 1, 2, where 0 represents untreated or not migrated, 1 represents migrated, and 2 represents no migration required. The identification before migration refers to data of public number openid fields in a table before migration.

S202, requesting to acquire the migrated identity of the target user list, and obtaining a migrated identity array.

The target user list comprises a preset batch number of concerned users with processing marks not migrated; the migrated identity is the identity in the public number of the service transaction after the migration of the concerned user; the migrated identity refers to an openid of a new public number corresponding to the openid of the original public number, which is acquired from a data interface of the instant messaging software.

In an exemplary embodiment, according to the original account app id, 100 pieces of user openid data which are processed under the original account and identified as unprocessed are obtained from a member table of the instant messaging software in batches, and an openid conversion interface of the instant messaging software is called to obtain a new account openid array corresponding to the batch of users.

S203, updating the current identity of any user in the account migration data table to be the migrated identity and updating the processing identity of any user in the account migration data table to be migrated under the condition that the migrated identity corresponding to any user exists in the migrated identity array aiming at any user in each target user list.

The updating process of the representation data is to update each piece of data in the target user list in sequence for any user in each target user list. The migrated identity mark corresponding to any user exists in the migrated identity mark array, which means that a new public number openid is successfully obtained from an interface for the user of the original public number openid, and the new public number openid is stored in a target user list; the purpose of updating the current identity of any user in the account migration data table as the migrated identity is to realize the record of the new public number openid, and the purpose of updating the processing identity of any user in the account migration data table as migrated is to change the migration state of the data and avoid repeated updating for the same data.

The new openid array returned by the interface of the instant messaging software is identified as an ok record, a user record is newly added in the membership table, and the assignment process of each field is as follows: public number app id = new account app id, public number openid = new account openid, process identity = 0-unprocessed, original public number openid = old account openid, process identity of update old user record = 1-migrated.

The identification ok indicates that the migrated identity corresponding to any user exists in the migrated identity array. In addition, in the present embodiment, "=" means assignment, meaning that data on the right of an equal sign is assigned to a field of an equal sign coordinate, and correspondingly, "public number app id = new account app id" means that data of "new account app id" is assigned to "public number app id" of this piece of data in a table.

In the account migration data updating method, firstly, the account migration data table is obtained, then, the migrated identity of the target user list is requested to be obtained, a migrated identity array is obtained, finally, under the condition that the migrated identity exists in the migrated identity array, the current identity of any user is updated to be the migrated identity, the processing identity of any user is updated to be migrated, the migrated identity is completed according to the state condition of the processing identity, the processing identity is readjusted after the data updating is completed to change the migration state, the migrated user is accurately distinguished from the user without being migrated, the original account user is ensured to be not repeatedly migrated in batches, the influence on the migration process caused by the interruption of a migration task due to the cancellation of attention of the user in the migration checking process is avoided, the unprocessed data can be automatically restarted and accurately screened out to continue processing when the task is interrupted, the continuation of the task is ensured, and the technical effect of improving the data migration efficiency of account migration by the service handling public number is obtained.

In one embodiment, the method further comprises: acquiring check preparation data of any user in an account migration data table; consistency verification is carried out on the current identity mark and the historical identity mark, and a verification result is obtained; and updating the processing identification of any user in the account migration data table to be not migrated under the condition that the verification result is that the information of the new user and the old user is inconsistent.

The verification preparation data comprises a current identity and a historical identity of any user in an account migration data table; the current identity identification field stores the identity identification before migration, the history identity identification field stores the identity identification after migration, and consistency check refers to verifying whether the information of the new user and the old user is consistent.

After batch migration is completed, the member list stores two user lists of new public numbers and old public numbers at the same time, and the member list is added with an original public number openid field which is stored when a user record is newly added after an openid conversion interface is called, so that the fact that the openid of a new account is converted by the openid of a user concerned by which original account can be conveniently identified, and whether the information of the new user is consistent with the information of the old user can be checked; if the check finds that the information of the new user is inconsistent with the information of the old user, the processing identification of the original account openid can be changed back to 0-unprocessed, the newly added user record of the new account openid is deleted, the operation of running batch again to call the openid conversion interface is carried out within 15 days after the account migration audit is completed, and the abnormal user is migrated again.

In this embodiment, first, check preliminary data of any user in an account migration data table is obtained, then consistency check is performed on a current identity identifier and a historical identity identifier to obtain a check result, and in the case that information of new and old users is inconsistent, a processing identifier of any user in the account migration data table is updated to be not migrated, so that complete retention of new and old data before and after migration is ensured, normal completion of migration is ensured through consistency check, and a technical effect of improving data migration accuracy of account migration by service handling public numbers is obtained.

In one embodiment, the method further comprises: and updating the historical identity of any user in the account number migration data table to be the pre-migration identity under the condition that the post-migration identity corresponding to any user exists in the post-migration identity array.

The original public number field is set in the account migration data table, specifically, the data of the old account openid is assigned to the original public number openid field, so that the identity before migration is ensured to be still well-found after the migration is completed.

In this embodiment, under the condition that the post-migration identity corresponding to any user exists in the post-migration identity array, the historical identity of any user in the account migration data table is updated to be the pre-migration identity, so that complete retention of pre-migration data is ensured, data preparation is provided for a consistency verification process, and the technical effect of improving the accuracy of data migration of account migration by service handling public numbers is obtained.

In one embodiment, before the step of obtaining the account migration data table, the method further comprises: acquiring a data record before migration; and under the condition that the data record acquisition before migration is completed, submitting a migration audit request aiming at the service handling public number to a management platform of the service handling public number.

The pre-migration data record is used for updating an account migration data table; the migration audit request is used for requesting a management platform to audit whether the concerned user in the business handling public number before migration can be migrated to the business handling public number after migration, and the management platform comprises, but is not limited to, a platform for managing account migration in instant messaging software.

It should be noted that the pre-migration data record includes an identifier of a public number and a pre-migration identifier of a user in the public number, where the identifier of the public number includes, but is not limited to, a public number app id.

Before submitting an account migration audit, an interface of the instant messaging software is called for obtaining a user openid list of the original account in a divided mode, 10000 pieces of data are obtained at most each time, the user openid list is stored in a member list of the instant messaging software, public number app id and public number openid field values are the original account app id and the original account openid respectively, and a processing identifier=0-unprocessed.

In this embodiment, the pre-migration data record is first obtained, then, under the condition that the pre-migration data record is obtained, a migration audit request for the service handling public number is submitted to a management platform of the service handling public number, so that complete preparation of data before the migration audit request is sent is ensured, and public number app id is introduced into an account migration data table, so that the number of new and old account users can be distinguished by using the public number app id after migration, and further, the user loss condition caused by main body change is analyzed, and the technical effect of ensuring the completeness of data migration is obtained.

In one embodiment, the method further comprises: receiving a migration audit passing instruction fed back by the management platform according to the migration audit request; and responding to the migration audit passing instruction, and executing the step of requesting to acquire the migrated identity of the target user list to obtain the migrated identity array.

The management platform comprises, but is not limited to, a platform for managing account migration in instant messaging software, and migration audit passing instructions are instructions for the management platform to characterize audit passing instructions.

After the account migration audit is completed, 100 pieces of user openid data with the processing identifier=0-unprocessed under the original account are obtained from the member table in batches according to the original account app id, and an openid conversion interface of the instant messaging software is called to obtain a new account openid array corresponding to the batch of users.

In this embodiment, firstly, a migration audit passing instruction fed back by a management platform according to a migration audit request is received, then a post-migration identity identifier of a target user list is requested to be obtained, a post-migration identity identifier array is obtained, data preparation is completed before migration audit, a data exchange interface is executed by using a processing identifier after migration audit to convert the identity identifier, and an adaptive omnibearing guarantee mode is set for a specific scene in which a migration process is likely to be interrupted, so that a technical effect of improving data migration stability of account migration is obtained.

In one embodiment, the step of requesting to obtain the migrated identity of the target user list to obtain the migrated identity array includes: screening a target user list from the concerned users recorded in the account migration data table according to the preset batch number; calling a preset identification conversion interface according to the pre-migration identity corresponding to each user in the target user list so as to enable the preset identification conversion interface to return to the post-migration identity corresponding to each user in the target user list; and obtaining the migrated identity identification array according to a preset returned result of the identity conversion interface.

The preset batch number refers to the batch number of the users in the target user list, the identifier conversion interface comprises an interface for performing openid conversion in a platform of the instant messaging software, and the migrated identity identification array comprises not only successfully acquired migrated identity identifications, but also results of whether the migrated identity identifications of the users are successfully acquired.

For example, according to the original account app id, 100 pieces of user openid data with the processing identifier=0-unprocessed under the original account are obtained from the member table in batches, and an openid conversion interface of the instant messaging software is called to obtain a new account openid array corresponding to the batch of users.

In this embodiment, a target user list is first screened out from focused users recorded in an account migration data table according to a preset batch number, and then a preset identifier conversion interface is called to obtain migrated identifiers corresponding to each user in the target user list, so as to obtain a migrated identifier array, and the data batch process and the identifier conversion process of the identifier conversion interface are combined by adopting the thinking of batch processing, so that batch acquisition of migrated identifiers is realized, risks brought by instability of the conversion interface to the migration process are reduced, and the technical effect of improving the data migration stability of account migration is obtained.

In one embodiment, the method further comprises: and updating the processing identification of any user in the account number migration data table to be unnecessary to migrate under the condition that the migrated identification corresponding to any user does not exist in the migrated identification array.

The migrated identity identification array does not have a migrated identity identification corresponding to any user, and indicates that the user aiming at the original public number openid does not successfully acquire a new public number openid from an interface, and the new public number openid is not stored in a target user list.

Illustratively, for records identified as not ok, no user records are added, only the old user records are updated processing identification = 2-no migration is required. The meaning of the mark as not ok is that the post-migration identity mark does not exist in the post-migration identity mark array.

In this embodiment, under the condition that no post-migration identity corresponding to any user exists in the post-migration identity array, updating the processing identity of any user in the account migration data table to be migration-free, accurately classifying the data of the user which is not required to be migrated, avoiding the problem of migration interruption in the process of performing identity conversion on such data, and obtaining the technical effect of improving the data migration stability and efficiency of account migration.

In another embodiment, as shown in fig. 3, there is provided an account migration data updating method, including the following steps:

s301, acquiring a data record before migration;

s302, under the condition that data record acquisition before migration is completed, submitting a migration audit request aiming at the service handling public number to a management platform of the service handling public number;

s303, acquiring an account migration data table;

s304, receiving a migration audit passing instruction fed back by the management platform according to the migration audit request;

s305, responding to a migration audit passing instruction, and screening a target user list from the concerned users recorded in the account migration data table according to the preset batch number;

s306, calling a preset identification conversion interface according to the pre-migration identity identifications corresponding to the users in the target user list so as to enable the preset identification conversion interface to return to the post-migration identity identifications corresponding to the users in the target user list;

s307, obtaining the migrated identity identification array according to the returned result of the preset identity conversion interface.

It should be noted that, the specific limitation of the above steps may be referred to the specific limitation of an account migration data updating method, which is not described herein.

In another embodiment, as shown in fig. 4, there is provided an account migration data updating method, including the following steps:

s401, updating the current identity of any user in the account migration data table to be the migrated identity, updating the processing identity of any user in the account migration data table to be migrated and updating the historical identity of any user in the account migration data table to be the pre-migration identity under the condition that the migrated identity corresponding to any user exists in the migrated identity array aiming at any user in each target user list.

S402, updating the processing identification of any user in the account number migration data table to be unnecessary to migrate under the condition that the migrated identity corresponding to any user does not exist in the migrated identity array.

S403, obtaining check preparation data of any user in an account migration data table;

s404, carrying out consistency verification on the current identity and the historical identity to obtain a verification result;

and S405, updating the processing identification of any user in the account migration data table as non-migration under the condition that the verification result is that the information of the new user is inconsistent with the information of the old user.

In one embodiment, the account migration process of the business handling public numbers comprises an online submitting and checking process, a two-party manager confirming change and a system automatic starting migration process.

The online submitting and auditing process specifically comprises the following steps: the account A initiates migration, the administrator scans to perform identity verification, clicks and agrees with a related protocol, fills in a target account B, waits for confirmation of the target administrator B, then continues to fill in application data including public letters, public certificates, administrator information and the like, confirms related names such as original account names, target account names or custom new names, fills in invoice information and pays migration cost, and waits for 1 to 3 working days to pass after auditing, namely 15-day confirmation period of the AB administrator.

Wherein, the confirmation of the change of the two administrators refers to the confirmation of the change of account information, and specifically includes the synchronization of names.

The system automatically starts the migration flow, specifically, after confirmation of both sides, the account A is frozen immediately, a notification is issued before migration, a vermicelli is notified in advance, after the notification is issued for one day, migration data is started, migrated contents comprise data such as vermicelli, mass-sending materials and the like, then old account is recovered, and after migration, a notification is issued to complete migration.

It should be noted that, the two side administrators must confirm the migration notification within 15 days after the success of the audit, and the automatic failure needs to be restarted after the timeout; if the migration confirmation notification is not received after the verification is successful, the migration confirmation notification can be sent by clicking the account migration page in the background of the public number, and the migration confirmation notification can be only issued once a day.

In the automatic system starting migration flow, the method for updating account migration data provided by the application aims to convert the openid of the user concerned by the original account into a new account openid, and comprises the following specific steps:

(1) Creating a member table of a target object in instant messaging software, wherein the member table comprises public number app id and public number openid fields; (2) Before submitting account migration audit, calling an interface of instant communication software to acquire a user openid list of the original account in a divided manner, acquiring 10000 pieces of data at most each time, and storing an entry table, wherein public number app id and public number openid field values are respectively the original account app id and the original account openid; 3) After account migration audit is completed, according to the original account app id, obtaining user openid data of 100 original accounts from a member table in batches, calling an openid conversion interface of instant messaging software, and obtaining a new account openid array corresponding to the batch of users; (4) And (3) updating 100 pieces of public number app id and public number openid field values recorded by the original user in batches into a new account app id and a new account openid, and then repeating the step (3) in the embodiment to acquire the next 100 pieces of data for processing until all the data are converted. In the step (4) in this embodiment, two fields of public number app id and public number openid are directly updated on the original user record, and the data size is not increased after the processing is completed.

In this embodiment, it is not considered that during the account migration audit period, the old public number is paid attention to by the original openid, so that the conversion interface of the instant messaging software does not return the new openid, then the new openid is not updated and stored in step (3) in this embodiment, the processing of acquiring the user data of which attention is cancelled is repeated later, the conversion task is forcibly stopped by manual intervention, and the number of attention users lost due to the failure to evaluate after the migration is completed, so that the migration efficiency of the account data is reduced.

Based on the method, the account migration data updating method for converting the openid of the user concerned by the original account into the new account openid in batches and without repetition is provided for the public account migration, in the public account migration process, the migrated users are accurately distinguished and are not required to be migrated, the original account user is ensured to be stably migrated in batches without repetition, unprocessed data can be accurately screened for continuous processing if the task is restarted by interruption, and the consistency of the new and old openid user data can be conveniently traced and checked after migration.

The account migration data update method is described in detail below in a specific embodiment with reference to fig. 5. It is to be understood that the following description is exemplary only and is not intended to limit the application to the details of construction and the arrangements of the components set forth herein.

It should be noted that, in this embodiment, the account migration data table is specifically a member table in the instant messaging software of the target object, and the identity of the user who has paid attention to is openid.

In this embodiment, by marking whether each user of the original account has migrated, and storing a new record of the new openid acquired by the interface of the instant messaging software, and recording the old openid of the source, the conversion data acquired in each batch will not be repeated, and each new openid can trace back the old openid. The method comprises the following specific steps:

(1) The optimized member table comprises public number app id, public number openid, processing identification and original public number openid fields; wherein the process identification includes, but is not limited to, 0-untreated, 1-migrated, 2-no-migration.

It should be noted that, according to the official advice of the instant messaging software, the user list of the original account number needs to be obtained before the migration audit is ready to be submitted. During the migration audit period of 1 to 3 working days, the client may cancel the attention when receiving the migration notification, but the openid conversion interface of the instant messaging software must be normally returned by the user of the old account currently in attention, otherwise, the error occurs, so that the adding of the processing identifier in the member table includes 0-unprocessed, 1-migrated and 2-unnecessary migration fields, and the fields are updated after each call of the openid conversion interface, so that the unprocessed, migrated and cancelled user data can be conveniently distinguished without the migration.

(2) Before submitting account migration audit, calling an interface of instant communication software to acquire a user openid list of the original account in a divided manner, acquiring 10000 pieces of data at most each time, and storing the acquired personnel list, wherein public number app id and public number openid field values are respectively the original account app id and the original account openid, and processing identifier = 0-unprocessed;

(3) After account migration audit is completed, according to the original account app id, acquiring 100 pieces of user openid data which are processed by the original account and have the identification=0-unprocessed from a member table of the instant messaging software in batches, and calling an openid conversion interface of the instant messaging software to acquire a new account openid array corresponding to the batch of users;

(4) A new openid array returned by the interface of the instant messaging software is marked as an ok record, a user record is newly added in a member list, and each field is assigned as follows: public number app id = new account app id, public number openid = new account openid, process identity = 0-unprocessed, original public number openid = old account openid, process identity of update old user record = 1-migrated; the record marked as not ok is not added, the user record is not added, only the old user record processing mark=2 is updated-no migration is needed, then step (3) in the embodiment is repeated, and next 100 pieces of data processing are acquired until all data are converted.

Step (4) in this embodiment judges new openid array elements returned by the interface of the instant messaging software one by one, and marks as ok records, which indicate that the concerned user has migrated successfully, new openid records can be newly added and stored, original public number openid=original account openid, and process identifiers of updated and old user records=1-migrated; the record marked as not ok indicates that the user has cancelled attention currently without migration, and does not need to newly add a new openid record, but only updates the processing identifier=2 of the old user record-without migration.

It should be noted that, the err_msg=ok condition in fig. 5 is satisfied, which indicates that this openid still focuses on the old public number at present, and the conversion is normal in the data conversion process; whereas err_msg=ok condition is not satisfied, indicating that this openid is not currently concerned with the old public number, i.e. the conversion fails in the data conversion process; the condition old_user_list.size=100 in fig. 5 is satisfied, which indicates that the user data of the batch has not been processed one by one, and the update needs to be completed continuously.

In this embodiment, by setting the processing identifier, it is ensured that the to-be-processed data obtained in batches in the public number migration process is not repeated, and the old data is still reserved after the migration is completed, so that the number of users of the new account and the old account can be distinguished according to the public number app id field, further, the user loss caused by the change of the main body is analyzed, and the old user data can be found according to the original public number openid field association of the new openid record, further, the consistency of the user information before and after the migration is verified.

It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides an account migration data updating device for realizing the account migration data updating method. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, so the specific limitation in the embodiment of one or more account migration data updating devices provided below can be referred to the limitation of the account migration data updating method hereinabove, and will not be repeated here.

In one embodiment, as shown in fig. 6, there is provided an account migration data updating apparatus, including: a data table acquisition module 601, a post-migration identity identification request module 602, and a data table update module 603, wherein:

the data table obtaining module 601 is configured to obtain an account migration data table; the account migration data table is used for indicating that the concerned user in the business handling public numbers before migration is migrated to the business handling public numbers after migration; the account migration data table comprises pre-migration identity identifiers and processing identifiers corresponding to the concerned users; the identity before migration is the identity in the public number of the business transaction before migration of the concerned user; the process identifies a migration state used to characterize the user of interest;

the post-migration identity request module 602 is configured to request to obtain a post-migration identity of the target user list, so as to obtain a post-migration identity array; the target user list comprises a preset batch number of concerned users with processing marks not migrated; the migrated identity is the identity in the public number of the service transaction after the migration of the concerned user;

the data table updating module 603 is configured to update, for any user in each target user list, if a post-migration identity corresponding to any user exists in the post-migration identity array, a current identity of any user in the account migration data table as a post-migration identity, and update a processing identity of any user in the account migration data table as migrated.

In one embodiment, the apparatus further comprises: the verification data acquisition module is used for acquiring verification preparation data of any user in the account migration data table; checking the preparation data to include the current identity and the historical identity of any user in an account migration data table; the verification module is used for carrying out consistency verification on the current identity mark and the historical identity mark to obtain a verification result; and the first processing identifier updating module is used for updating the processing identifier of any user in the account migration data table to be not migrated under the condition that the verification result is that the information of the new user is inconsistent with the information of the old user.

In one embodiment, the apparatus further comprises: and the historical identity updating module is used for updating the historical identity of any user in the account number migration data table to be the pre-migration identity under the condition that the post-migration identity corresponding to any user exists in the post-migration identity array.

In one embodiment, the apparatus further comprises: the data record acquisition module is used for acquiring the data record before migration; the pre-migration data record is used for updating an account migration data table; the migration audit request submitting module is used for submitting a migration audit request aiming at the business handling public number to the management platform of the business handling public number under the condition that the data record acquisition before migration is completed; the migration checking request is used for requesting the management platform to check whether the concerned user in the business handling public numbers before migration can be migrated to the business handling public numbers after migration.

In one embodiment, the apparatus further comprises: the migration audit passing instruction receiving module is used for receiving a migration audit passing instruction fed back by the management platform according to the migration audit request; and the migration audit passing instruction execution module is used for responding to the migration audit passing instruction and executing the step of requesting to acquire the migrated identity of the target user list to obtain the migrated identity array.

In one embodiment, the post-migration identity request module comprises: the target user list batch acquisition module is used for screening a target user list from the concerned users recorded in the account migration data table according to the preset batch number; the identification conversion interface calling module is used for calling a preset identification conversion interface according to the pre-migration identification corresponding to each user in the target user list so as to enable the preset identification conversion interface to return to the post-migration identification corresponding to each user in the target user list; the array acquisition module is used for acquiring the migrated identity identification array according to the return result of the preset identity conversion interface.

In one embodiment, the apparatus further comprises: and the second processing identifier updating module is used for updating the processing identifier of any user in the account number migration data table to be unnecessary to migrate under the condition that the migrated identity identifier corresponding to any user does not exist in the migrated identity identifier array.

All or part of the modules in the account migration data updating device can be realized by software, hardware and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 7. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for storing the related data of account migration. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements a method for updating account migration data.

In one embodiment, a computer device is provided, which may be a terminal, and the internal structure thereof may be as shown in fig. 8. The computer device includes a processor, a memory, an input/output interface, a communication interface, a display unit, and an input means. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program, when executed by a processor, implements a method for updating account migration data. The display unit of the computer device is used for forming a visual picture, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be a key, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.

It will be appreciated by persons skilled in the art that the structures shown in fig. 7 and 8 are block diagrams of only portions of structures associated with the present inventive arrangements and are not limiting of the computer device to which the present inventive arrangements are applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device includes a memory having a computer program stored therein and a processor that when executing the computer program performs the steps of the method embodiments described above.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, carries out the steps of the method embodiments described above.

In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, or the like, but is not limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The foregoing examples illustrate only a few embodiments of the application and are described in detail herein without thereby limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.

Claims

1. An account migration data updating method, which is characterized by comprising the following steps:

2. The method according to claim 1, wherein the method further comprises:

3. The method according to claim 2, wherein the method further comprises:

4. The method of claim 1, wherein prior to the step of obtaining an account migration data table, the method further comprises:

5. The method according to claim 4, wherein the method further comprises:

6. The method of claim 1, wherein the requesting to obtain the migrated identity of the target user list, obtaining the migrated identity array, comprises:

7. The method according to any one of claims 1 to 6, further comprising:

8. An account migration data updating apparatus, the apparatus comprising:

9. The apparatus of claim 8, wherein the apparatus further comprises:

10. The apparatus of claim 9, wherein the apparatus further comprises:

11. The apparatus of claim 8, wherein the apparatus further comprises:

12. The apparatus of claim 11, wherein the apparatus further comprises:

13. The apparatus of claim 8, wherein the post-migration identity request module comprises:

14. The apparatus according to any one of claims 8 to 13, further comprising:

15. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 7 when the computer program is executed.

16. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 7.

17. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 7.