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

Abstract

The present application relates to an account migration data update method, apparatus, computer equipment, storage medium, and computer program product, and relates to the field of big data technology. The method comprises: obtaining an account migration data table; requesting to obtain the post-migration identity identifier of the target user list, and obtaining a post-migration identity identifier array; for any user in each target user list, if a post-migration identity identifier corresponding to any user exists in the post-migration identity identifier array, updating the current identity identifier of any user in the account migration data table to the post-migration identity identifier, and updating the processing identifier of any user in the account migration data table to migrated. This method can improve the data migration efficiency of account migration.

Description

Technical Field

[0001] The present application relates to the field of big data technology, and in particular to an account migration data update method, apparatus, computer equipment, storage medium, and computer program product. Background Art

[0002] When the business subject's name is changed, the subject of the business subject's business handling official account in the instant messaging software must also be changed. The business handling official account does not support direct modification of the official account platform subject. To retain the users who have been followed by the business handling official account and reduce the impact on business promotion and handling functions, the official account account of the business handling official account needs to be migrated to achieve a smooth subject change. Business subjects include banks and other financial institutions.

[0003] The account migration process involves the review of account migration. During the review period of the account migration request, if the user who originally followed the official account cancels the follow-up, the instant messaging software's conversion interface will not be able to normally return the new identity identifier for the user, such as OpenID, during the migration process. Manual intervention is required to forcibly stop the conversion task, resulting in the interruption of the migration task, which greatly reduces the data migration efficiency of the business handling official account for account migration. Summary of the Invention

[0004] Based on this, it is necessary to provide an account migration data update method, device, computer equipment, computer-readable storage medium and computer program product that can improve the data migration efficiency of account migration in response to the above technical problems.

[0005] In a first aspect, the present application provides a method for updating account migration data. The method comprises:

[0006] Obtain an account migration data table; the account migration data table is used to indicate the migration of the followed users in the business handling official account before the migration to the business handling official account after the migration; the account migration data table includes the pre-migration identity identifier and processing identifier corresponding to each of the followed users; the pre-migration identity identifier is the identity identifier of the followed user in the business handling official account before the migration; the processing identifier is used to represent the migration status of the followed user;

[0007] Requesting to obtain the post-migration identity identifiers of the target user list to obtain a post-migration identity identifier array; the target user list includes a preset batch number of the followed users whose processing identifiers are not migrated; the post-migration identity identifiers are the identity identifiers of the followed users in the business handling public account after the migration;

[0008] For any user in each of the target user lists, if there is a post-migration identity identifier corresponding to the any user in the post-migration identity identifier array, the current identity identifier of the any user in the account migration data table is updated to the post-migration identity identifier, and the processing identifier of the any user in the account migration data table is updated to migrated.

[0009] In one embodiment, the method further comprises:

[0010] Obtaining preliminary verification data of any user in the account migration data table; the preliminary verification data includes the current identity identifier and historical identity identifier of any user in the account migration data table;

[0011] Performing a consistency check on the current identity identifier and the historical identity identifier to obtain a check result;

[0012] When the verification result shows that the new and old user information are inconsistent, the processing flag of any user in the account migration data table is updated to not migrated.

[0013] In one embodiment, the method further comprises:

[0014] In a case where a post-migration identity corresponding to any one of the users exists in the post-migration identity array, the historical identity of any one of the users in the account migration data table is updated to the pre-migration identity.

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

[0016] Obtaining pre-migration data records; the pre-migration data records are used to update the account migration data table;

[0017] When the pre-migration data records are obtained, submit a migration review request for the business handling official account to the management platform of the business handling official account;

[0018] The migration review request is used to request the management platform to review whether the followed users in the business handling public account before the migration can be migrated to the business handling public account after the migration.

[0019] In one embodiment, the method further comprises:

[0020] receiving the migration review pass instruction fed back by the management platform according to the migration review request;

[0021] In response to the migration review passed instruction, the step of requesting to obtain the post-migration identity identifiers of the target user list to obtain a post-migration identity identifier array is executed.

[0022] In one embodiment, the request to obtain the post-migration identity identifiers of the target user list to obtain the post-migration identity identifier array includes:

[0023] According to the preset batch number, the target user list is filtered out from the followed users recorded in the account migration data table;

[0024] According to the pre-migration identity identifier corresponding to each user in the target user list, calling a preset identity conversion interface so that the preset identity conversion interface returns the post-migration identity identifier corresponding to each user in the target user list;

[0025] The post-migration identity array is obtained according to the return result of the preset identity conversion interface.

[0026] In one embodiment, the method further comprises:

[0027] In a case where the post-migration identity identifier corresponding to any one of the users does not exist in the post-migration identity identifier array, the processing identifier of any one of the users in the account migration data table is updated to no migration required.

[0028] In a second aspect, the present application also provides an account migration data update device. The device includes:

[0029] A data table acquisition module is configured to acquire an account migration data table; the account migration data table is configured to indicate the migration of the followed users in the pre-migration business handling official account to the post-migration business handling official account; the account migration data table includes a pre-migration identity identifier and a processing identifier corresponding to each of the followed users; the pre-migration identity identifier is the identity identifier of the followed user in the pre-migration business handling official account; the processing identifier is configured to indicate the migration status of the followed user;

[0030] A post-migration identity request module is configured to request the post-migration identity of a target user list, and obtain a post-migration identity array; the target user list includes a preset number of batches of the followed users whose processing identifiers are not migrated; the post-migration identity is the identity of the followed user in the business handling public account after the migration;

[0031] A data table update module is used to update the current identity identifier of any user in the account migration data table to the post-migration identity identifier, and to update the processing identifier of any user in the account migration data table to migrated, if there is a post-migration identity identifier corresponding to the any user in the post-migration identity identifier array.

[0032] In one embodiment, the apparatus further comprises:

[0033] A verification data acquisition module, configured to acquire preliminary verification data of any user in the account migration data table; the preliminary verification data includes the current identity identifier and historical identity identifier of any user in the account migration data table;

[0034] A verification module, configured to perform a consistency check on the current identity identifier and the historical identity identifier to obtain a verification result;

[0035] The first processing identification updating module is configured to update the processing identification of any user in the account migration data table to not migrated if the verification result shows that the new and old user information are inconsistent.

[0036] In one embodiment, the apparatus further comprises:

[0037] The historical identification updating module updates the historical identity identification of any user in the account migration data table to the pre-migration identity identification when a post-migration identity identification corresponding to any user exists in the post-migration identity identification array.

[0038] In one embodiment, the apparatus further comprises:

[0039] A data record acquisition module, configured to acquire pre-migration data records; the pre-migration data records are used to update the account migration data table;

[0040] A migration review request submission module, configured to submit a migration review request for the business handling official account to the management platform of the business handling official account when the acquisition of the pre-migration data record is completed;

[0041] The migration review request is used to request the management platform to review whether the followed users in the business handling public account before the migration can be migrated to the business handling public account after the migration.

[0042] In one embodiment, the apparatus further comprises:

[0043] A migration review pass instruction receiving module, configured to receive the migration review pass instruction fed back by the management platform according to the migration review request;

[0044] The migration audit passed instruction execution module is used to execute the step of requesting to obtain the post-migration identity identifiers of the target user list and obtaining the post-migration identity identifier array in response to the migration audit passed instruction.

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

[0046] A target user list batch acquisition module is used to filter out the target user list from the followed users recorded in the account migration data table according to the preset batch number;

[0047] an identity conversion interface calling module, configured to call a preset identity conversion interface according to the pre-migration identity corresponding to each user in the target user list, so that the preset identity conversion interface returns the post-migration identity corresponding to each user in the target user list;

[0048] The array acquisition module is used to obtain the post-migration identity identification array according to the return result of the preset identification conversion interface.

[0049] In one embodiment, the apparatus further comprises:

[0050] The second processing identifier updating module updates the processing identifier of any user in the account migration data table to no migration required when the post-migration identity identifier corresponding to any user does not exist in the post-migration identity identifier array.

[0051] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are performed:

[0052] Obtain an account migration data table; the account migration data table is used to indicate the migration of the followed users in the business handling official account before the migration to the business handling official account after the migration; the account migration data table includes the pre-migration identity identifier and processing identifier corresponding to each of the followed users; the pre-migration identity identifier is the identity identifier of the followed user in the business handling official account before the migration; the processing identifier is used to represent the migration status of the followed user;

[0053] Requesting to obtain the post-migration identity identifiers of the target user list to obtain a post-migration identity identifier array; the target user list includes a preset batch number of the followed users whose processing identifiers are not migrated; the post-migration identity identifiers are the identity identifiers of the followed users in the business handling public account after the migration;

[0054] For any user in each of the target user lists, if there is a post-migration identity identifier corresponding to the any user in the post-migration identity identifier array, the current identity identifier of the any user in the account migration data table is updated to the post-migration identity identifier, and the processing identifier of the any user in the account migration data table is updated to migrated.

[0055] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the following steps:

[0056] Obtain an account migration data table; the account migration data table is used to indicate the migration of the followed users in the business handling official account before the migration to the business handling official account after the migration; the account migration data table includes the pre-migration identity identifier and processing identifier corresponding to each of the followed users; the pre-migration identity identifier is the identity identifier of the followed user in the business handling official account before the migration; the processing identifier is used to represent the migration status of the followed user;

[0057] Requesting to obtain the post-migration identity identifiers of the target user list to obtain a post-migration identity identifier array; the target user list includes a preset batch number of the followed users whose processing identifiers are not migrated; the post-migration identity identifiers are the identity identifiers of the followed users in the business handling public account after the migration;

[0058] For any user in each of the target user lists, if there is a post-migration identity identifier corresponding to the any user in the post-migration identity identifier array, the current identity identifier of the any user in the account migration data table is updated to the post-migration identity identifier, and the processing identifier of the any user in the account migration data table is updated to migrated.

[0059] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the following steps:

[0060] Obtain an account migration data table; the account migration data table is used to indicate the migration of the followed users in the business handling official account before the migration to the business handling official account after the migration; the account migration data table includes the pre-migration identity identifier and processing identifier corresponding to each of the followed users; the pre-migration identity identifier is the identity identifier of the followed user in the business handling official account before the migration; the processing identifier is used to represent the migration status of the followed user;

[0061] Requesting to obtain the post-migration identity identifiers of the target user list to obtain a post-migration identity identifier array; the target user list includes a preset batch number of the followed users whose processing identifiers are not migrated; the post-migration identity identifiers are the identity identifiers of the followed users in the business handling public account after the migration;

[0062] For any user in each of the target user lists, if there is a post-migration identity identifier corresponding to the any user in the post-migration identity identifier array, the current identity identifier of the any user in the account migration data table is updated to the post-migration identity identifier, and the processing identifier of the any user in the account migration data table is updated to migrated.

[0063] The above-mentioned account migration data update method, device, computer equipment, storage medium and computer program product first obtain the account migration data table, then request to obtain the post-migration identity identifier of the target user list, obtain the post-migration identity identifier array, and finally, when the post-migration identity identifier exists in the post-migration identity identifier array, update the current identity identifier of any user to the post-migration identity identifier, and update its processing identifier to migrated, complete the post-migration identity identifier according to the status of the processing identifier, and readjust the processing identifier after completing the data update to change the migration status, accurately distinguish between migrated and non-migrated users, ensure that the original account users are migrated smoothly in batches without duplication, avoid the impact of the migration task interruption caused by the user canceling the follow-up during the migration review process on the migration process, and automatically restart when the task is interrupted and accurately filter out the unprocessed data for continued processing to ensure the continuation of the task, thereby achieving the technical effect of improving the data migration efficiency of the business handling public account for account migration. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] Figure 1 This is a diagram of an application environment of an account migration data update method in one embodiment;

[0065] Figure 2 Schematic diagram of a flow chart of a method for updating account migration data in one embodiment;

[0066] Figure 3 A flowchart of an account migration data update method according to another embodiment;

[0067] Figure 4 A flowchart of an account migration data update method according to another embodiment;

[0068] Figure 5 This is a flow chart showing the principle of a method for updating account migration data in one embodiment;

[0069] Figure 6 This is a structural block diagram of an account migration data updating device in one embodiment;

[0070] Figure 7 is a diagram of the internal structure of a computer device in one embodiment;

[0071] Figure 8 FIG. 4 is a diagram showing the internal structure of a computer device in another embodiment. DETAILED DESCRIPTION

[0072] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0073] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions.

[0074] It should be noted that the account migration data update method, apparatus, computer equipment, storage medium and computer program product disclosed in this application can be applied to the field of financial technology, and can also be used in any field other than the field of financial technology.

[0075] The account migration data update method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown, the terminal 102 communicates with the server 104 via a network.

[0076] Terminal 102 may include, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices may include smart speakers, smart TVs, smart air conditioners, and smart car devices. Portable wearable devices may include smart watches, smart bracelets, and head-mounted devices. Server 104 may be implemented as a standalone server or a server cluster consisting of multiple servers.

[0077] In one embodiment, Figure 2 As shown, a method for updating account migration data is provided, which is applied to Figure 1 Taking the terminal 102 in FIG. 1 as an example, the method includes the following steps:

[0078] S201, obtaining an account migration data table.

[0079] Among them, the account migration data table is used to indicate the migration of followed users in the business processing public account before migration to the business processing public account after migration; the account migration data table includes the pre-migration identity identifier and processing identifier corresponding to each followed user; the pre-migration identity identifier is the identity identifier of the followed user in the business processing public account before migration; the processing identifier is used to represent the migration status of the followed user; the business processing public account is used for followed users to conduct business with business objects in instant messaging software, and business objects include banks and other financial institutions.

[0080] For example, the account migration data table is the target object's membership table in the instant messaging software, which can be simply called the member table. It contains the official account appid, official account openid, processing identifier, and original official account openid fields. The processing identifier value includes, but is not limited to, 0, 1, and 2, where 0 represents unprocessed or not migrated, 1 represents migrated, and 2 represents no migration required. The pre-migration identity identifier refers to the data in the official account openid field in the table before the migration.

[0081] S202: Requesting to obtain the post-migration identity identifiers of the target user list, and obtaining a post-migration identity identifier array.

[0082] Among them, the target user list includes a preset batch number of followed users whose processing identification is not migrated; the post-migration identity identification is the identity identification of the followed user in the business processing public account after migration; among them, the post-migration identity identification refers to the openid of the new public account corresponding to the openid of the original public account requested from the data interface of the instant messaging software.

[0083] For example, according to the original account appid, 100 user openid data with processing mark as unprocessed under the original account are obtained from the member table of the instant messaging software in batches, and the openid conversion interface of the instant messaging software is called to obtain the new account openid array corresponding to this batch of users.

[0084] S203, for any user in each target user list, if there is a post-migration identity identifier corresponding to any user in the post-migration identity identifier array, update the current identity identifier of any user in the account migration data table to the post-migration identity identifier, and update the processing identifier of any user in the account migration data table to migrated.

[0085] Among them, for any user in each target user list, the data update process is to update each data in the target user list in turn. The existence of a post-migration identity corresponding to any user in the post-migration identity array means that the user of the original public account openid has successfully obtained the new public account openid from the interface and saved the new public account openid in the target user list; the purpose of updating the current identity of any user in the account migration data table to the post-migration identity is to realize the record of the new public account openid, and the purpose of updating the processing identifier of any user in the account migration data table to migrated is to change the migration status of this data and avoid repeated updates for the same data.

[0086] For example, the new openid array returned by the interface of the instant messaging software is marked as ok, and a new user record is added to the member table. The process of assigning values ​​to each field is: public account appid = new account appid, public account openid = new account openid, processing identifier = 0-unprocessed, original public account openid = old account openid, and at the same time, the processing identifier of the old user record is updated = 1-migrated.

[0087] The ok flag indicates that the post-migration identity array contains a corresponding post-migration identity for any user. In this embodiment, "=" signifies assignment, assigning the data to the right of the equal sign to the field at the coordinate of the equal sign. Accordingly, "Official Account appid = New Account appid" means assigning the data of "New Account appid" to the "Official Account appid" entry in the table.

[0088] In the above account migration data update method, the account migration data table is first obtained, and then the post-migration identity identifier of the target user list is requested to obtain the post-migration identity identifier array. Finally, if the post-migration identity identifier exists in the post-migration identity identifier array, the current identity identifier of any user is updated to the post-migration identity identifier, and its processing identifier is updated to migrated. The post-migration identity identifier is completed according to the status of the processing identifier, and the processing identifier is readjusted after the data update is completed to change the migration status, accurately distinguish between migrated and non-migrated users, and ensure that the original account users are migrated smoothly in batches without duplication, avoiding the impact of the migration task interruption caused by the user canceling the follow-up during the migration review process on the migration process. When the task is interrupted, it can automatically restart and accurately filter out the unprocessed data for continued processing to ensure the continuation of the task, thereby achieving the technical effect of improving the data migration efficiency of the business handling public account for account migration.

[0089] In one embodiment, the method further includes: obtaining verification preliminary data of any user in the account migration data table; performing consistency verification on the current identity identifier and the historical identity identifier to obtain a verification result; if the verification result is that the new and old user information are inconsistent, updating the processing identifier of any user in the account migration data table to not migrated.

[0090] Among them, the verification preparation data includes the current identity and historical identity of any user in the account migration data table; the current identity field stores the identity before migration, and the historical identity field stores the identity after migration. The consistency check refers to verifying whether the new and old user information are consistent.

[0091] For example, after the batch migration is completed, the member table will store two user lists, the new public account and the old public account. The member table will add the original public account openid field. This field will be saved when a new user record is added after calling the openid conversion interface. This can easily identify which original account's openid is converted from the openid of the user it has followed, and check whether the new and old user information are consistent. If the check finds that the new and old user information are inconsistent, the processing flag of the original account's openid can be changed back to 0-unprocessed, and the new user record of the new account's openid can be deleted. Within 15 days after the account migration review is completed, the batch call openid conversion interface will be re-run to migrate the abnormal user again.

[0092] In this embodiment, the verification preliminary data of any user in the account migration data table is first obtained, and then the current identity identifier and the historical identity identifier are consistency checked to obtain the verification result. In the case of inconsistency between the new and old user information, the processing identifier of any user in the account migration data table is updated to not migrated, ensuring the complete retention of the new and old data before and after migration. The normal completion of the migration is guaranteed by the consistency check, and the technical effect of improving the data migration accuracy of the business processing public account for account migration is achieved.

[0093] In one embodiment, the method further includes: if a post-migration identity corresponding to any user exists in the post-migration identity array, updating the historical identity of any user in the account migration data table to a pre-migration identity.

[0094] For example, the original public account field is set in the account migration data table. Specifically, the old account openid data is assigned to the original public account openid field, ensuring that the identity before migration is still traceable after the migration is completed.

[0095] In this embodiment, when there is a post-migration identity identifier corresponding to any user in the post-migration identity identifier array, the historical identity identifier of any user in the account migration data table is updated to the pre-migration identity identifier, thereby ensuring the complete retention of the pre-migration data, providing data preparation for the consistency verification process, and achieving the technical effect of improving the data migration accuracy of the business processing public account for account migration.

[0096] In one embodiment, before the step of obtaining the account migration data table, the method also includes: obtaining pre-migration data records; when the pre-migration data records are obtained, submitting a migration review request for the business handling public account to the management platform of the business handling public account.

[0097] Among them, the pre-migration data records are used to update the account migration data table; the migration review request is used to request the management platform to review whether the followed users in the business processing public account before the migration can be migrated to the business processing public account after the migration. The management platform includes but is not limited to the platform for managing account migration in instant messaging software.

[0098] It should be noted that the pre-migration data record includes the official account identifier and the user's pre-migration identity identifier in the official account, wherein the official account identifier includes but is not limited to the official account appid.

[0099] For example, before submitting the account migration review, the instant messaging software interface is called in batches to obtain the user openid list of the original account, with a maximum of 10,000 data items obtained each time, and saved in the instant messaging software's membership table. The public account appid and public account openid field values ​​are the original account appid and original account openid respectively, and the processing flag = 0-unprocessed.

[0100] In this embodiment, the pre-migration data records are first obtained, and then, when the pre-migration data records are obtained, a migration review request for the business handling public account is submitted to the management platform of the business handling public account, ensuring the complete preparation of data before the migration review request is sent, and introducing the public account appid into the account migration data table, and then using the public account appid after migration to distinguish the number of new and old account users, and then analyze the user loss caused by the subject change, thereby achieving the technical effect of ensuring the completeness of data migration.

[0101] In one embodiment, the method further includes: receiving a migration review pass instruction fed back by the management platform according to the migration review request; in response to the migration review pass instruction, executing a step of requesting to obtain the post-migration identity identifier of the target user list and obtaining a post-migration identity identifier array.

[0102] The management platform includes but is not limited to a platform for managing account migration in instant messaging software, and the migration review pass instruction is an instruction indicating that the management platform has passed the review.

[0103] For example, after the account migration review is completed, according to the original account appID, 100 user openid data with processing identifier = 0-unprocessed under the original account are obtained from the member table in batches, and the openid conversion interface of the instant messaging software is called to obtain the new account openid array corresponding to this batch of users.

[0104] In this embodiment, the management platform first receives the migration review pass instruction fed back based on the migration review request, then requests to obtain the post-migration identity identifiers of the target user list, obtains the post-migration identity identifier array, completes data preparation before the migration review, and uses the processing identifier to execute the call of the data exchange interface after the migration review to perform the identity identifier conversion. For specific scenarios where the migration process may be interrupted, an adaptive all-round protection method is set for it, thereby achieving the technical effect of improving the data migration stability of account migration.

[0105] In one embodiment, a request is made to obtain the post-migration identity identifiers of the target user list to obtain a post-migration identity identifier array, including: filtering out the target user list from the followed users recorded in the account migration data table according to a preset batch number; calling a preset identifier conversion interface based on the pre-migration identity identifier corresponding to each user in the target user list, so that the preset identifier conversion interface returns the post-migration identity identifier corresponding to each user in the target user list; and obtaining a post-migration identity identifier array based on the return result of the preset identifier conversion interface.

[0106] Among them, the preset batch number refers to the batch number of users screened out from the target user list, the identity conversion interface includes the interface for openid conversion in the instant messaging software platform, and the post-migration identity array includes not only the successfully obtained post-migration identity, but also the result of whether the post-migration identity of each user is successfully obtained.

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

[0108] In this embodiment, first, according to the preset batch number, the target user list is filtered out from the followed users recorded in the account migration data table, and then the preset identity conversion interface is called to obtain the post-migration identity identifier corresponding to each user in the target user list to obtain the post-migration identity identifier array. In the face of a large number of data records of followed users, the idea of ​​batch processing is adopted to combine the data batch process with the identity conversion process of the identity conversion interface, thereby realizing the batch acquisition of the post-migration identity identifier, reducing the risk brought to the migration process by the instability of the conversion interface, and achieving the technical effect of improving the data migration stability of account migration.

[0109] In one embodiment, the method further includes: updating a processing flag of any user in the account migration data table to no migration required when there is no post-migration identity corresponding to any user in the post-migration identity array.

[0110] Among them, there is no migrated identity corresponding to any user in the migrated identity array, which means that the user of the original public account openid has not successfully obtained the new public account openid from the interface, and has not saved the new public account openid in the target user list.

[0111] For example, for records marked as not ok, no new user record is added, and only the old user record is updated. Processing flag = 2 - no migration required. The mark of not ok means that the post-migration identity does not exist in the post-migration identity array.

[0112] In this embodiment, when there is no post-migration identity identifier corresponding to any user in the post-migration identity identifier array, the processing identifier of any user in the account migration data table is updated as no need to migrate, and the data of users who do not need to migrate are accurately classified, avoiding the migration interruption problem during the identifier conversion process for such data, and achieving the technical effect of improving the data migration stability and efficiency of account migration.

[0113] In another embodiment, Figure 3 As shown, a method for updating account migration data is provided, including the following steps:

[0114] S301, obtaining data records before migration;

[0115] S302: After the pre-migration data records are obtained, a migration review request for the business handling official account is submitted to the management platform of the business handling official account;

[0116] S303, obtaining the account migration data table;

[0117] S304: Receive a migration review pass instruction from the management platform based on the migration review request;

[0118] S305 , in response to the migration review passing instruction, filtering out a target user list from the followed users recorded in the account migration data table according to a preset batch number;

[0119] S306: Calling a preset identity conversion interface based on the pre-migration identity corresponding to each user in the target user list, so that the preset identity conversion interface returns the post-migration identity corresponding to each user in the target user list;

[0120] S307: Obtain a post-migration identity array according to the return result of the preset identity conversion interface.

[0121] It should be noted that the specific limitations of the above steps can be found in the specific limitations of an account migration data update method mentioned above, which will not be repeated here.

[0122] In another embodiment, Figure 4 As shown, a method for updating account migration data is provided, including the following steps:

[0123] S401, for any user in each target user list, if there is a post-migration identity identifier corresponding to any user in the post-migration identity identifier array, update the current identity identifier of any user in the account migration data table to the post-migration identity identifier, update the processing identifier of any user in the account migration data table to migrated, and update the historical identity identifier of any user in the account migration data table to the pre-migration identity identifier.

[0124] S402: When there is no post-migration identity identifier corresponding to any user in the post-migration identity identifier array, update the processing identifier of any user in the account migration data table to no migration required.

[0125] S403, obtaining preliminary verification data of any user in the account migration data table;

[0126] S404, performing consistency check on the current identity identifier and the historical identity identifier to obtain a check result;

[0127] S405: When the verification result shows that the new and old user information are inconsistent, the processing flag of any user in the account migration data table is updated to not migrated.

[0128] It should be noted that the specific limitations of the above steps can be found in the specific limitations of an account migration data update method mentioned above, which will not be repeated here.

[0129] In one embodiment, the account migration process of the business handling official account includes an online submission review process, confirmation of the changes by administrators of both parties, and automatic initiation of the migration process by the system.

[0130] The online submission review process specifically includes: Account A initiates the migration, the administrator scans for identity authentication, clicks to agree to the relevant agreement, fills in the target account B, waits for confirmation from the target administrator B, and then Administrator A continues to fill in the application materials, including official letters, notarized documents and administrator information, etc., confirms the relevant names, such as using the original account name, using the target account name or customizing a new name, and then fills in the invoice information and pays the migration fee. After waiting for 1 to 3 working days for the review to pass, it is the 15-day confirmation period for Administrators A and B.

[0131] Among them, the confirmation of changes by administrators of both parties refers to the confirmation of changes in account information, specifically including the synchronization of names.

[0132] Among them, the system automatically starts the migration process, specifically including: after confirmation by both parties, account A will be frozen immediately, a notice will be issued before the migration to notify fans in advance, and data migration will begin one day after the notice is issued. The migrated content includes data such as fans and group materials, and then the old account will be recycled. After the migration, a notice will be issued to complete the migration.

[0133] It should be noted that administrators on both sides must confirm the migration notification within 15 days after the successful review. If the time limit is exceeded, it will automatically expire and need to be re-initiated. If you do not receive the migration confirmation notification after the successful review, you can go to the account migration page in the backend of the official account and click Send to receive the confirmation. It can only be issued once a day.

[0134] During the system-automatically initiated migration process, the purpose of the account migration data update method provided in this application is to convert the OpenID of the user followed by the original account to the OpenID of the new account. The specific steps include:

[0135] (1) Create a membership table for the target object in the instant messaging software, including the public account appid and public account openid fields; (2) Before submitting the account migration review, call the instant messaging software interface in batches to obtain the user openid list of the original account, obtaining up to 10,000 data each time, and save them in the membership table. The public account appid and public account openid field values ​​are the original account appid and original account openid respectively; 3) After the account migration review is completed, according to the original account appid, obtain 100 original account user openid data from the membership table in batches, call the instant messaging software's openid conversion interface, and obtain the new account openid array corresponding to this batch of users; (4) Batch update the public account appid and public account openid field values ​​of 100 original user records to the new account appid and new account openid, and then repeat step (3) of this embodiment to obtain the next batch of 100 data for processing until all data conversion is completed. Among them, step (4) of this embodiment directly updates the public account appid and public account openid fields on the original user record, and the data volume does not increase after the processing is completed.

[0136] In this embodiment, it is not considered that during the account migration review period, the original openid cancels the old public account, resulting in the conversion interface of the instant messaging software not returning the new openid. Then, step (3) in this embodiment will not update and save the new openid, and the subsequent acquisition of the user data of the unfollowed user will be repeated, requiring manual intervention to force the conversion task to stop. Moreover, after the migration is completed, it is impossible to evaluate the number of users lost as a result, resulting in a decrease in the migration efficiency of the account data.

[0137] Based on this, this application provides an account migration data update method for public account migration, which converts the openids of users followed by the original account into the openids of new accounts in batches and without duplication. During the public account account migration process, it accurately distinguishes between users who have been migrated and those who do not need to be migrated, ensuring that the original account users are migrated smoothly in batches without duplication. If the task is interrupted and restarted, the unprocessed data can be accurately filtered and continued to be processed. After the migration, it is convenient to trace and check the consistency of the new and old openid user data.

[0138] Reference below Figure 5 , a specific embodiment is used to describe in detail the account migration data update method. It is worth noting that the following description is only an example and not a specific limitation of the application.

[0139] It should be noted that, in this embodiment, the account migration data table is specifically a membership table of the target object in the instant messaging software, and the identity identifier of the followed user is openid.

[0140] In this embodiment, by marking whether each user of the original account has been migrated, and saving a new record of the new OpenID obtained by the instant messaging software interface, and recording the old OpenID of the source, each batch of converted data obtained will not be repeated, and each new OpenID can be traced back to the old OpenID. The specific steps are as follows:

[0141] (1) Optimize the member table, including the official account appid, official account openid, processing identifier, and original official account openid fields; among which, the processing identifier includes but is not limited to 0-unprocessed, 1-migrated, and 2-no migration required.

[0142] It's important to note that according to official instant messaging software recommendations, you must obtain the user list of the original account before submitting for migration review. During the one to three business days of the migration review, customers may unfollow users after receiving the migration notification. The instant messaging software's OpenID conversion API requires the original account's currently followed users to properly return, otherwise an error will occur. Therefore, a processing flag field (0 - unprocessed, 1 - migrated, 2 - no migration required) has been added to the member table. This field is updated after each call to the OpenID conversion API, making it easier to distinguish between unprocessed, migrated, and unfollowed users who don't need migration.

[0143] (2) Before submitting the account migration review, call the instant messaging software interface in batches to obtain the user openid list of the original account, obtaining a maximum of 10,000 data items each time, and save them into the member table. The public account appid and public account openid field values ​​are the original account appid and original account openid respectively, and the processing flag = 0-unprocessed;

[0144] (3) After the account migration review is completed, based on the original account appID, 100 user openid data with the processing identifier = 0 - unprocessed under the original account are obtained from the instant messaging software's membership table in batches, and the instant messaging software's openid conversion interface is called to obtain the new account openid array corresponding to this batch of users;

[0145] (4) The new openid array returned by the instant messaging software interface, the record marked as ok, adds a new user record to the member table, and assigns the following values ​​to each field: public account appid = new account appid, public account openid = new account openid, processing flag = 0-unprocessed, original public account openid = old account openid, and at the same time updates the processing flag of the old user record = 1-migrated; for the record marked as not ok, no new user record is added, only the old user record processing flag is updated = 2-no migration required, and then repeat step (3) in this embodiment, and then obtain the next batch of 100 data for processing until all data conversion is completed.

[0146] Among them, step (4) of this embodiment determines the new openid array elements returned by the interface of the instant messaging software one by one. The record marked as ok indicates that the migration of the followed user is successful, and a new openid record can be added and saved, with the original public account openid = the original account openid, and the processing flag of the old user record is updated to 1-migrated; the record marked as not ok indicates that the user has currently unfollowed and does not need to be migrated. It is not necessary to add a new openid record, and only the processing flag of the old user record is updated to 2-no migration required.

[0147] It should be noted that Figure 5 If the err_msg=ok condition is met, it means that this OpenID is still following the old Official Account and the data conversion is going smoothly. If the err_msg=ok condition is not met, it means that this OpenID is not following the old Official Account and the data conversion failed. Figure 5 The condition old_user_list.size=100 is met, indicating that the user data of this batch has not been processed one by one and needs to be updated.

[0148] In this embodiment, by setting the processing identifier, it is ensured that the data to be processed obtained in batches during the official account migration process will not be repeated, and the old data will be retained after the migration is completed. The number of new and old account users can be distinguished based on the official account appid field, and then the user loss caused by the subject change can be analyzed. The old user data can also be found by associating the original official account openid field recorded in the new openid, and then the consistency of user information before and after the migration can be verified.

[0149] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0150] Based on the same inventive concept, embodiments of the present application also provide an account migration data update device for implementing the aforementioned account migration data update method. The solution provided by this device is similar to the solution described in the aforementioned method. Therefore, the specific limitations of one or more embodiments of the account migration data update device provided below can be found in the limitations of the account migration data update method described above and will not be further elaborated here.

[0151] In one embodiment, Figure 6 As shown, an account migration data update device is provided, comprising: a data table acquisition module 601, a post-migration identity request module 602, and a data table update module 603, wherein:

[0152] The data table acquisition module 601 is used to obtain an account migration data table; the account migration data table is used to indicate the migration of the followed users in the business handling official account before the migration to the business handling official account after the migration; the account migration data table includes the pre-migration identity identifier and the processing identifier corresponding to each followed user; the pre-migration identity identifier is the identity identifier of the followed user in the business handling official account before the migration; the processing identifier is used to indicate the migration status of the followed user;

[0153] The post-migration identity request module 602 is configured to request the post-migration identity of the target user list, thereby obtaining an array of post-migration identity identifiers; the target user list includes a preset number of batches of followed users whose processing identifiers are not migrated; the post-migration identity identifiers are the identities of the followed users in the business handling official account after the migration;

[0154] The data table update module 603 is used to update the current identity identifier of any user in the account migration data table to the post-migration identity identifier for any user in each target user list, and to update the processing identifier of any user in the account migration data table to migrated if there is a post-migration identity identifier corresponding to any user in the post-migration identity identifier array.

[0155] In one embodiment, the device also includes: a verification data acquisition module, which is used to obtain verification preliminary data of any user in the account migration data table; the verification preliminary data includes the current identity identifier and historical identity identifier of any user in the account migration data table; a verification module, which is used to perform consistency verification on the current identity identifier and the historical identity identifier to obtain a verification result; a first processing identifier update module, which is used to update the processing identifier of any user in the account migration data table to not migrated when the verification result is that the new and old user information are inconsistent.

[0156] In one embodiment, the device further includes: a historical identification updating module, which updates the historical identity identification of any user in the account migration data table to the pre-migration identity identification when there is a post-migration identity identification corresponding to any user in the post-migration identity identification array.

[0157] In one embodiment, the device also includes: a data record acquisition module, which is used to obtain pre-migration data records; the pre-migration data records are used to update the account migration data table; a migration review request submission module, which is used to submit a migration review request for the business processing public account to the management platform of the business processing public account when the pre-migration data record acquisition is completed; wherein, the migration review request is used to request the management platform to review whether the followed users in the business processing public account before migration can be migrated to the business processing public account after migration.

[0158] In one embodiment, the device also includes: a migration review pass instruction receiving module, which is used to receive the migration review pass instruction fed back by the management platform based on the migration review request; a migration review pass instruction execution module, which is used to execute the step of requesting to obtain the post-migration identity identifier of the target user list in response to the migration review pass instruction, and obtaining the post-migration identity identifier array.

[0159] In one embodiment, the post-migration identity request module includes: a target user list batch acquisition module, which is used to filter out a target user list from the followed users recorded in the account migration data table according to a preset batch number; an identity conversion interface calling module, which is used to call a preset identity conversion interface based on the pre-migration identity corresponding to each user in the target user list, so that the preset identity conversion interface returns the post-migration identity corresponding to each user in the target user list; an array acquisition module, which is used to obtain a post-migration identity array based on the return result of the preset identity conversion interface.

[0160] In one embodiment, the apparatus further comprises: a second processing identifier updating module, which updates the processing identifier of any user in the account migration data table to no migration required when there is no post-migration identity identifier corresponding to any user in the post-migration identity identifier array.

[0161] Each module in the above-mentioned account migration data update device can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in hardware form, or can be stored in a computer device memory in software form, so that the processor can call and execute the corresponding operations of each module.

[0162] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 7As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O) and a communication interface. The processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used 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, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store data related to account migration. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, it implements an account migration data update method.

[0163] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 8 As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected via a system bus, and the communication interface, the display unit and the input device are connected to the system bus via the input / output interface. The processor of the computer device is used 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 the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, it implements a method for updating account migration data. The display unit of the computer device is used to form a visually visible picture, which 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 device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device casing, or an external keyboard, touchpad or mouse.

[0164] Those skilled in the art will understand that Figure 7 and Figure 8The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0165] In one embodiment, a computer device includes a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0166] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0167] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0168] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processor involved in the various embodiments provided herein may be, but are not limited to, a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, and the like.

[0169] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0170] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A method for updating account migration data, characterized in that: The method comprises: Obtain an account migration data table; the account migration data table is used to indicate the migration of the followed users in the business handling official account before the migration to the business handling official account after the migration; the account migration data table includes the pre-migration identity identifier and processing identifier corresponding to each of the followed users; the pre-migration identity identifier is the identity identifier of the followed user in the business handling official account before the migration; the processing identifier is used to represent the migration status of the followed user; Requesting to obtain the post-migration identity identifiers of the target user list to obtain a post-migration identity identifier array; the target user list includes a preset batch number of the followed users whose processing identifiers are not migrated; the post-migration identity identifiers are the identity identifiers of the followed users in the business handling public account after the migration; For any user in each of the target user lists, if there is a post-migration identity identifier corresponding to the any user in the post-migration identity identifier array, the current identity identifier of the any user in the account migration data table is updated to the post-migration identity identifier, and the processing identifier of the any user in the account migration data table is updated to migrated.

2. The method according to claim 1, characterized in that The method further comprises: Obtaining preliminary verification data of any user in the account migration data table; the preliminary verification data includes the current identity identifier and historical identity identifier of any user in the account migration data table; Performing a consistency check on the current identity identifier and the historical identity identifier to obtain a check result; When the verification result shows that the new and old user information are inconsistent, the processing flag of any one of the users in the account migration data table is updated to not migrated.

3. The method according to claim 2, characterized in that The method further comprises: In a case where a post-migration identity corresponding to any one of the users exists in the post-migration identity array, the historical identity of any one of the users in the account migration data table is updated to the pre-migration identity.

4. The method according to claim 1, wherein Before the step of obtaining the account migration data table, the method further includes: Obtaining pre-migration data records; the pre-migration data records are used to update the account migration data table; When the pre-migration data records are obtained, submit a migration review request for the business handling official account to the management platform of the business handling official account; The migration review request is used to request the management platform to review whether the followed users in the business handling public account before the migration can be migrated to the business handling public account after the migration.

5. The method according to claim 4, characterized in that The method further comprises: receiving the migration review pass instruction fed back by the management platform according to the migration review request; In response to the migration review passed instruction, the step of requesting to obtain the post-migration identity identifiers of the target user list to obtain a post-migration identity identifier array is executed.

6. The method according to claim 1, characterized in that The request obtains the post-migration identity identifiers of the target user list, and obtains a post-migration identity identifier array, including: According to the preset batch number, the target user list is filtered out from the followed users recorded in the account migration data table; According to the pre-migration identity identifier corresponding to each user in the target user list, calling a preset identity conversion interface so that the preset identity conversion interface returns the post-migration identity identifier corresponding to each user in the target user list; The post-migration identity array is obtained according to the return result of the preset identity conversion interface.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: In a case where the post-migration identity identifier corresponding to any one of the users does not exist in the post-migration identity identifier array, the processing identifier of any one of the users in the account migration data table is updated to no migration required.

8. An account migration data updating device, characterized in that: The device comprises: A data table acquisition module is configured to acquire an account migration data table; the account migration data table is configured to indicate the migration of the followed users in the pre-migration business handling official account to the post-migration business handling official account; the account migration data table includes a pre-migration identity identifier and a processing identifier corresponding to each of the followed users; the pre-migration identity identifier is the identity identifier of the followed user in the pre-migration business handling official account; the processing identifier is configured to indicate the migration status of the followed user; A post-migration identity request module is configured to request the post-migration identity of a target user list, and obtain a post-migration identity array; the target user list includes a preset number of batches of the followed users whose processing identifiers are not migrated; the post-migration identity is the identity of the followed user in the business handling public account after the migration; A data table update module is used to update the current identity identifier of any user in the account migration data table to the post-migration identity identifier, and to update the processing identifier of any user in the account migration data table to migrated, if there is a post-migration identity identifier corresponding to the any user in the post-migration identity identifier array.

9. The device according to claim 8, characterized in that The device further comprises: A verification data acquisition module, configured to acquire preliminary verification data of any user in the account migration data table; the preliminary verification data includes the current identity identifier and historical identity identifier of any user in the account migration data table; A verification module, configured to perform a consistency check on the current identity identifier and the historical identity identifier to obtain a verification result; The first processing identification updating module is configured to update the processing identification of any user in the account migration data table to not migrated if the verification result shows that the new and old user information are inconsistent.

10. The device according to claim 9, characterized in that The device further comprises: The historical identification updating module updates the historical identity identification of any user in the account migration data table to the pre-migration identity identification when a post-migration identity identification corresponding to any user exists in the post-migration identity identification array.

11. The device according to claim 8, characterized in that The device further comprises: A data record acquisition module, configured to acquire pre-migration data records; the pre-migration data records are used to update the account migration data table; A migration review request submission module, configured to submit a migration review request for the business handling official account to the management platform of the business handling official account when the acquisition of the pre-migration data record is completed; The migration review request is used to request the management platform to review whether the followed users in the business handling public account before the migration can be migrated to the business handling public account after the migration.

12. The device according to claim 11, characterized in that The device further comprises: A migration review pass instruction receiving module, configured to receive the migration review pass instruction fed back by the management platform according to the migration review request; The migration audit passed instruction execution module is used to execute the step of requesting to obtain the post-migration identity identifiers of the target user list and obtaining the post-migration identity identifier array in response to the migration audit passed instruction.

13. The device according to claim 8, characterized in that The post-migration identity request module includes: A target user list batch acquisition module is used to filter out the target user list from the followed users recorded in the account migration data table according to the preset batch number; an identity conversion interface calling module, configured to call a preset identity conversion interface according to the pre-migration identity corresponding to each user in the target user list, so that the preset identity conversion interface returns the post-migration identity corresponding to each user in the target user list; The array acquisition module is used to obtain the post-migration identity identification array according to the return result of the preset identification conversion interface.

14. The device according to any one of claims 8 to 13, characterized in that The device further comprises: The second processing identifier updating module updates the processing identifier of any user in the account migration data table to no migration required when the post-migration identity identifier corresponding to any user does not exist in the post-migration identity identifier array.

15. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

16. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

17. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images