CN111147568B - Method and device for synchronizing identity data - Google Patents

Abstract

The invention discloses a method and a device for synchronizing identity data, wherein the method comprises the following steps: acquiring historical identity data of at least one member user, and storing the historical identity data of the at least one member user into a shared storage system; detecting whether one or more channel user accounts bound with any one or more member user accounts exist in any group of channel user accounts according to historical identity data in the shared storage system; and if so, synchronously updating the historical identity data of the member users for any group of channel user accounts according to the historical identity data of one or more member users bound by the one or more channel user accounts. Therefore, the method and the device can synchronize the member user accounts bound by the group of channel user accounts with direct or indirect incidence relation, so that the member user accounts of the same user in a plurality of channels are kept consistent.

Description

Method and device for synchronizing identity data

technical field

The present invention relates to the field of Internet technologies, in particular to a method and device for synchronizing identity data.

Background technique

With the continuous development of Internet technology, it has become more and more common to meet daily needs through Internet platforms or clients. At the same time, on an Internet platform or client, especially an Internet platform or client that contains multiple brand objects, the user's membership for a certain brand on the platform or client can be used as the basis for the user to complete consumption activities. Records and credentials, which are conducive to the user's consumption behavior. In the prior art, the membership identities of users in different Internet platforms or clients are completely isolated and not related to each other. For example, the membership identities in platform A and the membership identities in platform B are determined by the independent systems of the respective platforms. For management, the membership of the independent systems of the two platforms cannot be connected.

However, in the process of implementing the embodiments of the present invention, the inventor found that there are at least the following problems in the membership management method in the prior art: the membership identities between the platforms are isolated from each other, so that the identity data between the platforms cannot be communicated with each other. It is convenient for unified analysis and processing of identity data.

SUMMARY OF THE INVENTION

In view of the above problems, embodiments of the present invention are proposed to provide a method and apparatus for synchronizing identity data that overcome the above problems or at least partially solve the above problems.

According to an aspect of the embodiments of the present invention, a method for synchronizing identity data is provided, including:

Obtain the historical identity data of at least one member user, and store the historical identity data of the at least one member user in the shared storage system; the historical identity data of the member user includes: the member user account, the first channel bound with the member user account User account, and/or at least one second channel user account associated with the first channel user account;

According to the historical identity data in the shared storage system, detect whether there is one or more channel user accounts bound to any one or more member user accounts in any group of channel user accounts; There is a direct or indirect relationship between each channel user account;

If it is, then according to the historical identity data of one or more member users bound to the one or more channel user accounts in the shared storage system, synchronously update the historical identity data of the member users for the group of channel user accounts.

Optionally, the historical identity data of the member user also includes member resource information and/or object information of member objects.

Optionally, according to the historical identity data of one or more member users bound to the one or more channel user accounts in the shared storage system, the synchronization of the historical identity data of the member user is performed on the any group of channel user accounts. The update process further includes:

If it is detected that there are one or more channel user accounts bound to any member user account in any group of channel user accounts, the historical identity data of the one member user will be synchronized to the group of channel user accounts except for the one or a channel user account other than multiple channel user accounts.

Optionally, if it is detected that there is one or more channel user accounts bound to any member user account in any group of channel user accounts with direct or indirect association, the method further includes:

A binding relationship between the channel user accounts other than the one or more channel user accounts in the group of channel user accounts and the member user account of the one member user is established in the shared storage system.

Optionally, according to the historical identity data of one or more member users bound to the one or more channel user accounts in the shared storage system, the synchronization of the historical identity data of the member user is performed on the any group of channel user accounts. The update process further includes:

If it is detected that there are multiple channel user accounts bound to any number of member user accounts in any group of channel user accounts, and the multiple member user accounts belong to the same member object, send the member selection to the client corresponding to at least one channel user account request, and receive the member selection result fed back by the client;

According to the result of member selection, integrate the historical identity data of multiple member users;

Synchronize the integrated historical identity data of member users to all channel user accounts in the group of channel user accounts.

Optionally, after the integrated processing of the historical identity data of the multiple member users, the method further includes:

A binding relationship between each channel user account in the group of channel user accounts and the selected member user account is established in the shared storage system.

Optionally, according to the historical identity data of one or more member users bound to the one or more channel user accounts in the shared storage system, the historical identity data of the member user is performed on the any group of channel user accounts. After the synchronization update process, the method further includes:

For each channel, determine whether multiple channel user accounts in any channel have the same historical identity data of member users;

If so, keep the historical identity data of the member users of one channel user account among the multiple channel user accounts, and delete the historical identity data of the member users of other channel user accounts among the multiple channel user accounts.

Optionally, according to the historical identity data of one or more member users bound to the one or more channel user accounts in the shared storage system, the historical identity data of the member user is performed on the any group of channel user accounts. After the synchronization update process, the method further includes:

Receive a member registration request initiated by any channel account, where the member registration request includes the identity data of the newly registered member user;

Determine whether there is at least one channel user account to be synchronized that has a direct or indirect relationship with the channel user account in the identity data of the newly registered member user; if so, synchronize the identity data of the newly registered member user to The at least one channel user account to be synchronized.

Optionally, the method further includes:

Receive a membership rebinding request initiated by a user account of any channel, where the membership rebinding request includes the identity data of the newly bound member user;

Determine whether there is at least one channel user account to be bound that has a direct or indirect relationship with the channel user account in the identity data of the newly bound member user; if so, then according to the identity of the newly bound member user The data performs the exchange and binding process of the identity data of the member user for the at least one channel user account to be exchanged and bound.

Optionally, the method further includes:

Receive the resource update data of member users returned by the user account of any channel;

The member user resource information update process is performed on the corresponding member user in the shared storage system according to the resource update data.

According to another aspect of the embodiments of the present invention, an apparatus for synchronizing identity data is provided, including:

The storage module is suitable for acquiring the historical identity data of at least one member user, and storing the historical identity data of the at least one member user in the shared storage system; the historical identity data of the member user includes: a predetermined first channel user account and/or at least one second channel user account associated with the first channel user account;

The detection module is adapted to detect whether there is one or more channel user accounts bound to any one or any plurality of member user accounts in any group of channel user accounts according to the historical identity data in the shared storage system; There is a direct or indirect relationship between multiple channel user accounts in the channel account;

The historical member synchronization module is adapted to, if there is one or more channel user accounts bound to any one or more member user accounts, then according to the one or more channel user accounts bound to the one or more channel user accounts in the shared storage system. The historical identity data of each member user is subjected to synchronous update processing of the historical identity data of the member user for the group of channel user accounts.

Optionally, the historical identity data of the member user also includes member resource information and/or object information of member objects.

Optionally, the synchronization module is further adapted to:

If it is detected that there are one or more channel user accounts bound to any member user account in any group of channel user accounts, the historical identity data of the one member user will be synchronized to the group of channel user accounts except for the one or a channel user account other than multiple channel user accounts.

Optionally, the device further includes: a binding module, adapted to establish in the shared storage system channel user accounts other than the one or more channel user accounts in the group of channel user accounts, and the one or more channel user accounts. The binding relationship of the member user account of the member user.

Optionally, the synchronization module is further adapted to:

If it is detected that there are multiple channel user accounts bound to any number of member user accounts in any group of channel user accounts, and the multiple member user accounts belong to the same member object, send the member selection to the client corresponding to at least one channel user account request, and receive the member selection result fed back by the client;

According to the result of member selection, integrate the historical identity data of multiple member users;

Synchronize the integrated historical identity data of member users to all channel user accounts in the group of channel user accounts.

Optionally, the device further includes: a binding module adapted to establish a binding relationship between each channel user account in the group of channel user accounts and the selected member user account in the shared storage system.

Optionally, the device further includes:

The binding correction module is suitable for each channel to determine whether multiple channel user accounts in any channel have the same historical identity data of the member user; if so, retain the member user of one channel user account among the multiple channel user accounts and delete the historical identity data of member users of other channel user accounts in multiple channel user accounts.

Optionally, the device further includes:

The newly added member synchronization module is suitable for receiving a member registration request initiated by any channel account, and the member registration request includes the identity data of the newly registered member user; it is judged whether there is an identity data related to the newly registered member user. The channel user account has at least one to-be-synchronized channel user account with a direct or indirect association; if so, synchronize the identity data of the newly registered member user to the at least one to-be-synchronized channel user account.

Optionally, the device further includes:

The binding exchange module is suitable for receiving a member exchange binding request initiated by a user account of any channel, and the member exchange binding request contains the identity data of the newly bound member user; judges whether there is a relationship with the newly bound member user. The channel user account in the identity data has at least one channel user account to be exchanged and bound with a direct or indirect relationship; if so, the at least one channel user account to be exchanged and bound is performed according to the identity data of the newly bound member user. Binding processing of identity data of member users.

Optionally, the device further includes:

The update module is adapted to receive the resource update data of the member user returned by the user account of any channel; according to the resource update data, the update process of the member user resource information is performed on the corresponding member user in the shared storage system.

According to yet another aspect of the embodiments of the present invention, a computing device is provided, including: a processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface complete each other through the communication bus communication between;

The memory is used for storing at least one executable instruction, and the executable instruction enables the processor to execute the operation corresponding to the above-mentioned method for synchronizing the identity data.

According to yet another aspect of the embodiments of the present invention, a computer storage medium is provided, where at least one executable instruction is stored in the storage medium, and the executable instruction causes a processor to perform operations corresponding to the above-mentioned method for synchronizing identity data .

According to the method and device for synchronizing identity data according to the embodiments of the present invention, the historical identity data of at least one member user is firstly obtained from each channel, and stored in a shared storage system in a aggregated manner; and, for any group of channel user accounts, based on shared The historical identity data in the storage system detects whether there are one or more member users that need to be synchronously updated in the group of channel user accounts, and accurately detects the synchronous update requirements of historical members; If there is one or more channel user accounts bound to any one or more member user accounts, and it is determined that there is a need for synchronous update, then according to the one or more members bound to the one or more channel user accounts in the shared storage system The historical identity data of the user is subjected to synchronous update processing of the historical identity data of the member users for the group of channel user accounts, so as to keep the member users bound to each channel user account in the group of channel user accounts synchronized. It can be seen that the solution of this embodiment can complete the synchronization of the historical identity data of historical member users in any group of channel user accounts, so that the member users bound to the channel user accounts of the same user in each channel are consistent, which is beneficial to the historical member data. Multi-channel fusion analysis and processing.

The above description is only an overview of the technical solutions of the embodiments of the present invention. In order to understand the technical means of the embodiments of the present invention more clearly, it can be implemented according to the contents of the description, and in order to make the above and other purposes, features and The advantages can be more obvious and easy to understand, and the following specific implementations of the embodiments of the present invention are given.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for the purpose of illustrating the preferred embodiments, and are not considered to be limitations of the embodiments of the present invention. Also, the same components are denoted by the same reference numerals throughout the drawings. In the attached image:

1 shows a flowchart of a method for synchronizing identity data provided by an embodiment of the present invention;

2 shows a flowchart of a method for synchronizing identity data provided by another embodiment of the present invention;

3 shows a flowchart of a method for synchronizing identity data provided by yet another embodiment of the present invention;

4 shows a schematic structural diagram of an apparatus for synchronizing identity data provided by an embodiment of the present invention;

FIG. 5 shows a schematic structural diagram of a computing device provided by an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present invention will be more thoroughly understood, and will fully convey the scope of the present invention to those skilled in the art.

FIG. 1 shows a flowchart of a method for synchronizing identity data provided by an embodiment of the present invention. As shown in Figure 1, the method includes the following steps:

Step S110: Obtain the historical identity data of at least one member user, and store the historical identity data of the at least one member user in the shared storage system; A channel user account, and/or at least one second channel user account associated with the first channel user account.

Specifically, the historical identity data of at least one member user in the channel is obtained from each channel, and stored in the shared storage system, so as to realize the aggregation of the historical identity data of one or more channels, wherein the historical identity data obtained here is Identity data is the identity data historically generated in each channel before synchronization. Wherein, the first channel account is the channel account of the source channel to which the member user account belongs, and the second channel account is the channel account that is different from the source channel and is associated with the first channel account, and the second channel account may only be related to the first channel. The channel account directly associated with the account, or the channel account directly or indirectly associated with the first channel account. For example, the channel user account of the user in channel 1 is channel user 11, the channel user account of channel 2 associated with the channel user 11 is channel user 22, the channel user 11 has registered a member of a certain brand on channel 1 and the member If the user account is member user 111 , the first channel user account is channel user 11 , and the second channel user account is channel user 22 .

Step S120: According to the historical identity data in the shared storage system, detect whether there is one or more channel user accounts bound to any one or more member user accounts in any group of channel user accounts; wherein, a group of channel accounts There is a direct or indirect association relationship between the multiple channel user accounts in ; if yes, step S130 is executed; if not, the method ends.

The direct association relationship refers to the established direct association of channel user accounts, and the indirect association relationship refers to the association between at least two accounts that are not directly associated but can be connected through direct association. For example, establish an association between channel user 11 of this channel 1 and channel user 22 of another channel 2 in channel 1, and at the same time establish an association between channel user 22 of this platform and channel user 33 of another channel 3 in channel 2 , then the channel user 11 and the channel user 22, and the channel user 22 and the channel user 33 have a direct relationship respectively, while the channel user 11 and the channel user 33 have an indirect relationship, and the channel user 11, the channel user 22 and the channel user 33 have an indirect relationship. Forms a set of channel user accounts.

The shared storage system stores the historical identity data of each member user. Based on this, it is detected whether there is a channel user account bound to a member user account in any group of channel user accounts. Since the historical identity data is maintained by each channel, and If not connected, if the detection result is existence, it indicates that there is a need for historical identity data synchronization in this group of channel user accounts. At this time, step S130 is performed to perform synchronous update processing; if the detection result is nonexistent, it indicates that this group of channel user accounts There is no requirement for historical data synchronization, and the method ends.

Step S130: Synchronize and update the historical identity data of the member users for the group of channel user accounts according to the historical identity data of the one or more member users bound to the one or more channel user accounts in the shared storage system.

Specifically, the historical identity data of member users is synchronously updated for the group of channel user accounts, so that the member users bound to each channel user account in the group of channel user accounts are kept synchronized, and can be used in all channel user accounts. the member user. For example, channel account 11, channel user 22 and channel user 33 are a group of channel user accounts, wherein channel user 11 is bound to a member of KFC, while channel user 22 and channel user 33 are not bound to a member of KFC user, by synchronizing the historical identity data of the KFC member user bound by the channel user 11 to the channel user 22 and the channel user 33, so that the channel user 22 and the channel user 33 can also use the member user.

Further, if one or more member users are one (obviously a member object), or, if one or more member users are multiple and the multiple member users belong to the same member object, then synchronously update the member object. Or, if there are multiple one or more member users, and the multiple member users belong to at least two member objects, synchronous update can be performed for each member object in turn according to the method of synchronous update processing for the same member object. The synchronous update processing can also be performed simultaneously for each member object in the manner of performing synchronous update processing on the same member object. The member object is the entity to which the member user belongs, for example, the brand or store to which the member user belongs.

The solution of this embodiment can be implemented by a synchronization system, which can communicate with each channel system, obtain the identity data of each channel, and synchronize the identity data with the channel user accounts of each channel; The identity data stored in the shared storage system is operated, for example, the modification and deletion of the identity data are performed.

According to the method for synchronizing identity data provided by this embodiment, the historical identity data of at least one member user is firstly obtained from each channel, and stored in a shared storage system in aggregate; and, for any group of channel user accounts, based on the shared storage system The historical identity data in Detect whether there are one or more member users that need to be synchronously updated in this group of channel user accounts, and accurately detect the synchronous update requirements of historical members; One or more channel user accounts bound to any one or more member user accounts, and it is determined that there is a need for synchronous update, then according to the one or more member users bound to the one or more channel user accounts in the shared storage system. The historical identity data is used to synchronize and update the historical identity data of the member users for the group of channel user accounts, so as to keep the member users bound to each channel user account in the group of channel user accounts synchronized. It can be seen that the solution of this embodiment can complete the synchronization of the historical identity data of historical member users in any group of channel user accounts, so that the member users bound to the channel user accounts of the same user in each channel are consistent, which is beneficial to the historical member data. Multi-channel fusion analysis and processing.

FIG. 2 shows a flowchart of a method for synchronizing identity data provided by another embodiment of the present invention. In this embodiment, description will be given for a situation where there are multiple channel user accounts bound to any multiple member user accounts in any group of channel user accounts, and the multiple member user accounts belong to the same member object. As shown in Figure 2, the method includes the following steps:

Step S210: Obtain the historical identity data of at least one member user, and store the historical identity data of the at least one member user in the shared storage system; A channel user account, and/or at least one second channel user account associated with the first channel user account.

In some optional embodiments, the member user's historical identity data further includes member resource information and/or member object object information. Among them, the member resource information refers to the information reflecting the membership level, points and/or rights and interests, and the member object is the entity to which the member user belongs, and the object information of the member object refers to the identification information of the entity, such as brand name, brand code, etc. Wait. It should be noted here that the present invention does not take the data items in the above-defined historical identity data as an example. During specific implementation, those skilled in the art can add other data items to the historical identity data according to actual needs, such as , and add the channel ID of the source channel of the member user.

Specifically, when synchronizing the identity data, it is usually performed between several target channels. Correspondingly, the historical identity data of at least one member user is obtained from the several target channels and stored in the shared storage system. .

Step S220: According to the historical identity data in the shared storage system, detect whether there is one or more channel user accounts bound to any one or more member user accounts in any group of channel user accounts; wherein, a group of channel accounts There is a direct or indirect association relationship between the multiple channel user accounts in ; if yes, step S230 is executed; if not, the method ends.

Specifically, each group of channel user accounts is determined according to the association relationship between channel user accounts in several target channels, wherein the first channel user account and at least one second channel user account in the historical identity data of the member users can be queried. channel user accounts to determine each group of channel user accounts; alternatively, each group of channel user accounts can be determined by querying the channel user account association table.

Further, after determining each group of channel user accounts, for any group of channel user accounts, it is detected from the historical identity data in the shared storage system whether the first channel user account is any channel in the group of channel user accounts. If the historical identity data of the user account exists, there is one or more channel user accounts bound to any one or more member user accounts in this group of channel user accounts.

Still taking a group of channel user accounts composed of channel user 11, channel user 22 and channel user 33 as an example for illustration, if the historical identity data in the shared storage system includes a first channel user account as channel user 11 The historical identity data a, and include a piece of historical identity data b that the first channel user account is the channel user 22, then there are two channel user accounts bound to the two member user accounts in the group of channel user accounts.

If it is detected that there are one or more channel user accounts bound to any one or more member user accounts in the group of channel user accounts, it means that there is at least one channel in the group of channel user accounts before the synchronization update process is performed. If the user account has been bound to a member user, then step S230 needs to be executed to perform synchronous update processing, so that the historical identity data of the bound member user is bound to the members of the multiple channel user accounts in the group of channel user accounts. The user's historical identity data is kept in sync. On the contrary, there is no need to perform synchronous update processing.

Step S230: Send a member selection request to the client terminal corresponding to at least one channel user account, and receive the member selection result fed back by the client; according to the member selection result, integrate the historical identity data of multiple member users; The historical identity data of member users is synchronized to all channel user accounts in this group of channel user accounts.

This embodiment is mainly described by detecting that there are multiple channel user accounts bound to any number of member user accounts in any group of channel user accounts, and the multiple member user accounts belong to the same member object. This situation mainly means that there are at least two channel user accounts in the group of channel user accounts respectively bound to different member user accounts of the same member object. A specific example of this situation is shown in Table 1 below:

In Table 1 above, channel user 11 and channel user 22 are bound to member user 111 and member user 222 respectively, and both member user 111 and member user 222 belong to brand m, which conforms to the situation targeted by this embodiment.

Specifically, in response to the above situation, a member selection request is sent to the client terminal corresponding to at least one channel user account in the group of channel user accounts, wherein the at least one channel user account may be any one or any number of channel user accounts in the group a channel user account, optionally, according to a member user viewing request initiated by a client corresponding to one or more channel user accounts in the group of channel users, a member selection request is sent to the client that initiated the member user viewing request, wherein, Open the member center page on the client to initiate a member user viewing request; or, send a member selection request to the client corresponding to each channel user account in the group of channel user accounts. In addition, the member selection request carries one or more pieces of data in the historical identity data of multiple member users, so that the client can display the data of the multiple member users for selection on the client after receiving the member selection request. Card information, for example, displays information such as member user account, membership level and so on.

Further, the client terminal receives the user's selection operation, and feeds back the member selection result to the execution system of the scheme; after receiving the member selection result, determines the selected target member user; Integrate processing, integrate the historical identity data of multiple member users into the historical identity data of the target user member, and specifically integrate the member resource information in the historical identity data of multiple member users as the historical identity data of the target member user. Member resource information in the , for example, accumulating member points to obtain updated member points. After the above integration processing is completed, the updated historical identity data of the target member user is synchronized to all channel user accounts in the group of channel user accounts. The following takes Table 1 as an example to specifically describe the process of the above-mentioned synchronous update processing:

Suppose that a member selection request of member user 111 and member user 222 is sent to the client of channel user 33, and channel user 33 returns the member selection result of selecting member user 111, that is, the target member user is member user 111; The member resource information of 222 is integrated and processed. For example, by accumulating the resource s1 and the resource s2 to obtain the member resource information updated by the member user 111, the integrated historical member data can be obtained as follows:

Synchronizing the integrated historical membership data to the channel user 11 , the channel user 22 and the channel user 33 completes the synchronization update process among the group of channel users.

In some optional embodiments of the present invention, a binding relationship between each channel user account in the group of channel user accounts and the selected member user account is established in the shared storage system, and then the above synchronization in the shared storage system can be performed. When the historical identity data of the member users of each channel user account is updated, timely send an update message to each channel user account bound to the member user account in the historical identity data, and update the historical identity data of the member user in time .

In some optional implementations, after completing the above synchronization update process, for each channel, it is determined whether multiple channel user accounts in any channel have the same historical identity data of the member user; if so, keep multiple channels The historical identity data of member users of one channel user account in the user account, delete the historical identity data of member users of other channel user accounts in multiple channel user accounts. In practice, different channel user accounts of the same channel can only be bound to different member users of the same member object. For example, for brand m, channel user 11 and channel user 11' in channel 1 can only be bound to different member users 111 and member user 111', but cannot be bound to member user 111 at the same time; at the same time, among the historical member users, there are at least two channel user accounts of at least two channels registered or bound to the same member user, and the at least two The channel user account does not have a direct or indirect relationship. For example, on the basis of Table 1 above, if there is also a piece of historical membership data as follows:

Among them, channel user 33' is the channel user account of channel 3, and channel user 33' has no direct or indirect relationship with channel user 11. After the above synchronization update process is completed, there are channel user 33 and channel user in channel 3. 33' is bound to member user 111, which violates the principle that different channel user accounts of the same channel can only be bound to different member users of the same member object.

Based on the above situation, in these optional embodiments, after the synchronization update is completed, for the non-source channels of the selected target user members (there is no situation that violates the above principles in the source channels), determine the Whether there are two channel user accounts in multiple channel user accounts bound to the same member user account, if so, retain and delete the binding relationship, so that different channel user accounts of the same channel can only be bound to the same member Different member users of the object. It should be noted here that, in actual implementation, the process of judging duplicate member users in the same channel can be performed after the synchronization update process of each group of channel user accounts is completed, so as to ensure that the above principles are not violated during the synchronization update process at all times; Alternatively, it can also be executed after all group channel user accounts are updated synchronously to reduce the frequency of data processing.

After the above steps S210 to S230, the historical identity data is synchronized between the accounts of each group of channel users for the historical member users; in the following step S240, after the synchronization of the historical identity data is completed, the real-time new identity data is further synchronized. The registered member users will be updated synchronously.

Step S240: According to the member registration request initiated by any channel user account, perform synchronization update processing of the real-time identity data of the member user on the channel user account that has a direct or indirect relationship with the channel account.

First of all, it should be noted here that, in this embodiment, the composition of the identity data of the newly registered member user is similar to the historical identity data, and the same is true of the identity data of the newly bound member user in the following.

Specifically, a request to add a member user of a target member object is initiated in the client of any channel user account, and the channel user account has not been bound to the member user account of the member object (indicating that a member user account including the channel user account is included) If the group channel user account is not bound to the member user account of the member object), a member registration request will be initiated to the execution system of this scheme through the channel user account. For example, the channel user account 11 has not been bound to the member user account of brand n. If a member user of the brand n is registered on the client terminal of the channel user account 11, a member registration request will be initiated to the execution system. And, receive a member registration request initiated by any channel account, the member registration request contains the identity data of the newly registered member user; determine whether there is a direct or indirect association with the channel user account in the identity data of the newly registered member user At least one channel user account of the relationship to be synchronized, wherein, if there is, it indicates that there is a need for synchronous update processing of the identity data of the newly registered member user, and the identity data of the newly registered member user is synchronized to the at least one The user account of the channel to be synchronized; if it does not exist, it means that although there is a newly registered member user, but there is no need for synchronous update processing, only the identity data of the newly registered member user can be stored in the shared storage system. .

In addition, in some optional embodiments of the present invention, after completing the synchronous update processing of the historical identity data of the historical member users and/or the identity data of the newly registered member users, the member exchange initiated by the user account of any channel is received. Binding request, the member exchange binding request contains the identity data of the newly bound member user, wherein a request for adding a member user of a target member object is initiated in the client of any channel user account, and the channel user account has been The member user account bound to the member object means that the member user account historically bound to the channel user account needs to be replaced with a new member user account, and then the channel user account is used to initiate membership to the execution system of this plan. Change binding request; determine whether there is at least one channel user account to be exchanged that has a direct or indirect relationship with the channel user account in the newly bound member user's identity data, if so, it indicates that there is a need for synchronous exchange binding The channel user account of the newly bound member user is subjected to the exchange and binding process of the identity data of the member user for the at least one channel user account to be exchanged according to the identity data of the newly bound member user. The identity data of the predetermined member user is synchronized to the at least one channel user account to be exchanged and bound, so that the at least one channel user account to be exchanged and bound will replace the bound member user account of the member object.

Step S250: Receive the resource update data of the member user returned by the user account of any channel; perform the update process of the member user resource information on the corresponding member user in the shared storage system according to the resource update data.

Specifically, after the historical identity data of historical member users, the identity data of newly registered member users, and/or the identity data of newly bound member users are synchronized between each group of channel user accounts, the interface to update the synchronized identity data, wherein the new interface refers to the channel interface corresponding to each channel user account to be synchronized. Still taking Table 1 as an example, before the synchronization update process, the historical identity data corresponding to the member user 111 can only be updated through the channel 1, and the historical identity data of the member user 111 is synchronized to the channel account 11 and the channel account 22. After and channel account number 33, the historical member data can be updated through channel 1, channel 2 and channel 3 respectively, and these updated data can be synchronized to the channel user accounts in other channels that have not been updated through the shared storage system. .

Further, after the synchronization is completed, the member resource information can be updated through the user account of any channel, for example, the member points can be updated, and the resource update data shall be returned to the execution system of this scheme; After the resource update data is reached, the member resource information in the historical identity data of the corresponding member user in the shared storage system is updated, so that the member resource information in the shared storage system is kept as the latest data in real time, and then can make Each channel monitors the latest member resource information from the shared storage system and updates the member resource information of the member user account bound to the channel user account of the same group in each channel.

And, after the synchronization is completed, the user account of the second channel in the synchronized identity data can also be updated through the user account of any channel. When a channel user account directly or indirectly associated with any channel user account in a group of channel user accounts is added or decreased, the second channel user account in the synchronized identity data will be updated, and the channel account update data will be updated. Feedback to the execution system of this scheme; after receiving the update data of the channel account, the execution system of this scheme updates the second channel user account in the identity data of the corresponding member user in the shared storage system, and adds (or deletes) the new account. The binding relationship between the increased (or decreased) second channel user account and the member user account of the corresponding member user, so that the updated historical identity data is only mistakenly sent to the channel user account with direct or indirect association. Wherein, if the update situation is that the second channel user account is increased, the second channel user account in the identity data of the synchronized member user in the shared storage system is newly added, and the newly added second channel user account and The binding relationship of the member user account of the synchronized member user, and the historical identity data of the member user is synchronized to the newly added second channel user account.

In addition, in some optional embodiments of the present invention, when an unbinding request initiated by any channel user account is received, the unbinding request carries the channel user account initiated by the request and the member user account requested for unbinding; According to the unbinding request, query a group of channel user accounts where the channel user account initiated by the request is located, and release the binding relationship between each channel user account in the group of channel user accounts in the shared storage system and the member user account requested to be unbound, Send an unbinding instruction to other channel user accounts in the group of channel user accounts except the channel user account that initiates the request, where the unbinding instruction carries the member user account that is requested to be unbound. In this way, after completing the binding of member user accounts in one channel user account, the binding of each channel user account in a group of channel user accounts with the member user account requested to be unbound can be completed, so that the same member user account can be Quick unbinding in channel user accounts for multiple channels.

According to the method for synchronizing identity data provided by this embodiment, the historical identity data of at least one member user is firstly obtained from each channel, and stored in a shared storage system in aggregate; and, for any group of channel user accounts, based on the shared storage system The historical identity data in Detect whether there are one or more member users that need to be synchronously updated in this group of channel user accounts, and accurately detect the synchronous update requirements of historical members. When it is determined that there is a synchronous update demand, perform synchronous update processing and complete. Synchronization of historical identity data; and further synchronously update the identity data of newly registered member users in real time, so that the member user accounts bound to the same group of channel user accounts are synchronized in real time; By receiving the update request initiated by the user account of any channel, the identity data in the shared storage system is updated, so that each channel can monitor the updated identity data and obtain and use it. It can be seen that the solution of this embodiment can synchronously update the historical identity data and the new identity data generated in real time, so that the member users bound to the channel user accounts of the same user in each channel are consistent, which is beneficial to the multiplication of member data. Channel integration.

FIG. 3 shows a flowchart of a method for synchronizing identity data provided by yet another embodiment of the present invention. In this embodiment, description will be given for the case where one or more channel user accounts bound to any member user account exist in any group of channel user accounts. As shown in Figure 3, the method includes the following steps:

Step S310: Obtain the historical identity data of at least one member user, and store the historical identity data of the at least one member user in the shared storage system; A channel user account, and/or at least one second channel user account associated with the first channel user account.

Wherein, the historical identity data of the member user also includes member resource information and/or object information of member objects.

Step S320: According to the historical identity data in the shared storage system, detect whether there is one or more channel user accounts bound to any one or more member user accounts in any group of channel user accounts; wherein, a group of channel accounts There is a direct or indirect association relationship between the multiple channel user accounts in ; if yes, step S230 is executed; if not, the method ends.

Step S330: Synchronize the historical identity data of the one member user to the channel user accounts other than the one or more channel user accounts in the group of channel user accounts.

This embodiment is mainly described in the case of detecting that one or more channel user accounts bound to any member user account exist in any group of channel user accounts. This situation mainly means that the group of channel user accounts is bound to only one member user account, specifically, only one channel user account in the group of channel user accounts is bound to the one member user account, or it can be the group of channel users Multiple channel user accounts in the account are bound to the one member user account.

Specifically, in view of the above situation, when performing the synchronization update process, the historical identity data of the one member user can be synchronized to the channel user account that is not bound to the member user account in the group of channel user accounts. Meanwhile, in an optional implementation manner, the channel user accounts other than the one or more channel user accounts in the group of channel user accounts are established in the shared storage system, and are bound to the member user account of the one member user. That is, to establish a binding relationship between the channel account that is not bound to the member user account in the channel account of the group and the member user account, so that each channel user account in the channel user account of the group is stored in the shared storage system. The binding relationship with the member user account is further conducive to the subsequent sending of update messages of the member user's identity data to each channel user account in the group of channel user accounts.

In some optional implementations, after completing the above synchronization update process, for each channel, it is determined whether multiple channel user accounts in any channel have the same historical identity data of the member user; if so, keep multiple channels The historical identity data of member users of one channel user account in the user account, delete the historical identity data of member users of other channel user accounts in multiple channel user accounts.

Step S340: According to the member registration request initiated by any channel user account, perform synchronization update processing of the real-time identity data of the member user for the channel user account that has a direct or indirect relationship with the channel account.

In some optional implementations, a member exchange request initiated by a user account of any channel is received, and the member exchange request includes the identity data of the newly bound member user; according to the identity data of the newly bound member user Swap and bind the identity data of the member user for the at least one channel user account to be swapped.

Step S350: Receive the resource update data of the member user returned by the user account of any channel; perform the update process of the member user resource information on the corresponding member user in the shared storage system according to the resource update data.

In the embodiment of FIG. 3 above, only the differences from the embodiment of FIG. 2 are described in detail, and the other parts that are not described in detail have the same implementation principles and processes as the corresponding parts in the embodiment of FIG. 2 . , and will not be repeated here.

According to the method for synchronizing identity data provided in this embodiment, historical identity data and new identity data generated in real time can be synchronously updated, so that the member users bound to the channel user accounts of the same user in various channels are consistent, which is beneficial to members Multi-channel fusion of data.

In addition, in some other embodiments of the present invention, for the situation that any number of member user accounts belong to multiple member objects, the synchronous update processing is performed according to the member object. Specifically, for each member object, if the member object's If there are multiple member user accounts, the method of the embodiment of FIG. 2 is used to perform synchronous update processing. If the member object has one member user account, the method of the embodiment of FIG. 3 is used to perform synchronous update processing.

FIG. 4 shows a schematic structural diagram of an apparatus for synchronizing identity data provided by an embodiment of the present invention. As shown in Figure 4, the device includes:

The storage module 410 is adapted to obtain the historical identity data of at least one member user, and store the historical identity data of the at least one member user in the shared storage system; the historical identity data of the member user includes: a member user account, and a member user account The bound first channel user account, and/or at least one second channel user account associated with the first channel user account;

The detection module 420 is adapted to detect whether there is one or more channel user accounts bound to any one or any plurality of member user accounts in any group of channel user accounts according to the historical identity data in the shared storage system; There is a direct or indirect relationship between multiple channel user accounts in a group channel account;

The historical member synchronization module 430 is adapted to, if there is one or more channel user accounts bound with any one or more member user accounts, then according to the one or more channel user accounts bound to the one or more channel user accounts in the shared storage system. The historical identity data of a plurality of member users is subjected to synchronous update processing of the historical identity data of the member users for the group of channel user accounts.

In an optional manner, the historical identity data of the member user also includes member resource information and/or object information of member objects.

In an optional manner, the synchronization module is further adapted to:

If it is detected that there are one or more channel user accounts bound to any member user account in any group of channel user accounts, the historical identity data of the one member user will be synchronized to the group of channel user accounts except for the one or a channel user account other than multiple channel user accounts.

In an optional manner, the apparatus further includes: a binding module adapted to establish in the shared storage system channel user accounts other than the one or more channel user accounts in the group of channel user accounts , the binding relationship with the member user account of the one member user.

In an optional manner, the synchronization module is further adapted to:

If it is detected that there are multiple channel user accounts bound to any number of member user accounts in any group of channel user accounts, and the multiple member user accounts belong to the same member object, send the member selection to the client corresponding to at least one channel user account request, and receive the member selection result fed back by the client;

According to the result of member selection, integrate the historical identity data of multiple member users;

Synchronize the integrated historical identity data of member users to all channel user accounts in the group of channel user accounts.

In an optional manner, the device further includes: a binding module adapted to establish a binding relationship between each channel user account in the group of channel user accounts and the selected member user account in the shared storage system.

In an optional manner, the device further includes:

The binding correction module is suitable for each channel to determine whether multiple channel user accounts in any channel have the same historical identity data of the member user; if so, retain the member user of one channel user account among the multiple channel user accounts and delete the historical identity data of member users of other channel user accounts in multiple channel user accounts.

In an optional manner, the device further includes:

The newly added member synchronization module is suitable for receiving a member registration request initiated by any channel account, and the member registration request includes the identity data of the newly registered member user; it is judged whether there is an identity data related to the newly registered member user. The channel user account has at least one to-be-synchronized channel user account with a direct or indirect association; if so, synchronize the identity data of the newly registered member user to the at least one to-be-synchronized channel user account.

In an optional manner, the device further includes:

The binding exchange module is suitable for receiving a member exchange binding request initiated by a user account of any channel, and the member exchange binding request contains the identity data of the newly bound member user; judges whether there is a relationship with the newly bound member user. The channel user account in the identity data has at least one channel user account to be exchanged and bound with a direct or indirect relationship; if so, the at least one channel user account to be exchanged and bound is performed according to the identity data of the newly bound member user. Binding processing of identity data of member users.

In an optional manner, the device further includes:

The update module is adapted to receive the resource update data of the member user returned by the user account of any channel; according to the resource update data, the update process of the member user resource information is performed on the corresponding member user in the shared storage system.

An embodiment of the present invention provides a non-volatile computer storage medium, where the computer storage medium stores at least one executable instruction, and the computer executable instruction can execute the method for synchronizing identity data in any of the above method embodiments.

FIG. 5 shows a schematic structural diagram of a computing device provided by an embodiment of the present invention. The specific embodiment of the present invention does not limit the specific implementation of the computing device.

As shown in FIG. 5 , the computing device may include: a processor (processor) 502 , a communications interface (Communications Interface) 504 , a memory (memory) 506 , and a communication bus 508 .

The processor 502 , the communication interface 504 , and the memory 506 communicate with each other through the communication bus 508 . The communication interface 504 is used to communicate with network elements of other devices such as clients or other servers. The processor 502 is configured to execute the program 510, and specifically may execute the relevant steps in the foregoing embodiments of the method for synchronizing identity data of a computing device.

Specifically, the program 510 may include program code including computer operation instructions.

The processor 502 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention. The one or more processors included in the computing device may be the same type of processors, such as one or more CPUs; or may be different types of processors, such as one or more CPUs and one or more ASICs.

The memory 506 is used to store the program 510 . Memory 506 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk memory.

The program 510 can specifically be used to cause the processor 502 to perform the following operations:

Obtain the historical identity data of at least one member user, and store the historical identity data of the at least one member user in the shared storage system; the historical identity data of the member user includes: the member user account, the first channel bound with the member user account User account, and/or at least one second channel user account associated with the first channel user account;

According to the historical identity data in the shared storage system, detect whether there is one or more channel user accounts bound to any one or more member user accounts in any group of channel user accounts; There is a direct or indirect relationship between each channel user account;

If it is, then according to the historical identity data of one or more member users bound to the one or more channel user accounts in the shared storage system, synchronously update the historical identity data of the member users for the group of channel user accounts.

In an optional manner, the historical identity data of the member user also includes member resource information and/or object information of member objects.

In an optional manner, the program 510 causes the processor to perform the following operations:

If it is detected that there are one or more channel user accounts bound to any member user account in any group of channel user accounts, the historical identity data of the one member user will be synchronized to the group of channel user accounts except for the one or a channel user account other than multiple channel user accounts.

In an optional manner, the program 510 causes the processor to perform the following operations:

A binding relationship between the channel user accounts other than the one or more channel user accounts in the group of channel user accounts and the member user account of the one member user is established in the shared storage system.

In an optional manner, the program 510 causes the processor to perform the following operations:

If it is detected that there are multiple channel user accounts bound to any number of member user accounts in any group of channel user accounts, and the multiple member user accounts belong to the same member object, send the member selection to the client corresponding to at least one channel user account request, and receive the member selection result fed back by the client;

According to the result of member selection, integrate the historical identity data of multiple member users;

Synchronize the integrated historical identity data of member users to all channel user accounts in the group of channel user accounts.

In an optional manner, the program 510 causes the processor to perform the following operations:

A binding relationship between each channel user account in the group of channel user accounts and the selected member user account is established in the shared storage system.

In an optional manner, the program 510 causes the processor to perform the following operations:

For each channel, determine whether multiple channel user accounts in any channel have the same historical identity data of member users;

If so, keep the historical identity data of the member users of one channel user account among the multiple channel user accounts, and delete the historical identity data of the member users of other channel user accounts among the multiple channel user accounts.

In an optional manner, the program 510 causes the processor to perform the following operations:

Receive a member registration request initiated by any channel account, where the member registration request includes the identity data of the newly registered member user;

Determine whether there is at least one channel user account to be synchronized that has a direct or indirect relationship with the channel user account in the identity data of the newly registered member user; if so, synchronize the identity data of the newly registered member user to The at least one channel user account to be synchronized.

In an optional manner, the program 510 causes the processor to perform the following operations:

Receive a membership rebinding request initiated by a user account of any channel, where the membership rebinding request includes the identity data of the newly bound member user;

Determine whether there is at least one channel user account to be bound that has a direct or indirect relationship with the channel user account in the identity data of the newly bound member user; if so, then according to the identity of the newly bound member user The data performs the exchange and binding process of the identity data of the member user for the at least one channel user account to be exchanged and bound.

In an optional manner, the program 510 causes the processor to perform the following operations:

Receive the resource update data of member users returned by the user account of any channel;

The member user resource information update process is performed on the corresponding member user in the shared storage system according to the resource update data.

The algorithms or displays provided herein are not inherently related to any particular computer, virtual system, or other device. Various general-purpose systems can also be used with teaching based on this. The structure required to construct such a system is apparent from the above description. Furthermore, embodiments of the present invention are not directed to any particular programming language. It is to be understood that various programming languages can be used to implement the contents of the embodiments of the invention described herein and that the above descriptions of specific languages are intended to disclose the best mode of carrying out the embodiments of the invention.

In the description provided herein, numerous specific details are set forth. It will be understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it is to be understood that in the above description of exemplary embodiments of the invention, various features of the embodiments of the invention are sometimes grouped together in order to simplify the embodiments of the invention and to aid in the understanding of one or more of the various aspects of the invention. in a single embodiment, figure, or description thereof. However, this disclosed approach should not be construed to reflect an intention that the claimed embodiments of the invention require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art will understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. The modules or units or components in the embodiments may be combined into one module or unit or component, and further they may be divided into multiple sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method so disclosed may be employed in any combination, unless at least some of such features and/or procedures or elements are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, it will be understood by those skilled in the art that although some of the embodiments herein include certain features, but not others, included in other embodiments, that combinations of features of the different embodiments are intended to be within the scope of the present invention And form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

Various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will understand that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components according to the embodiments of the present invention. Embodiments of the present invention can also be implemented as apparatus or apparatus programs (eg, computer programs and computer program products) for performing part or all of the methods described herein. Such a program implementing embodiments of the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such signals may be downloaded from Internet sites, or provided on carrier signals, or in any other form.

It should be noted that the above-described embodiments illustrate rather than limit embodiments of the invention, and that alternative embodiments may be devised by those skilled in the art without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. Embodiments of the invention may be implemented by means of hardware comprising several different elements and by means of suitably programmed computers. In a unit claim enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. do not denote any order. These words can be interpreted as names. The steps in the above embodiments should not be construed as limitations on the execution order unless otherwise specified.

Claims (22)

1. A method of synchronizing identity data, comprising:

acquiring historical identity data of at least one member user, and storing the historical identity data of the at least one member user into a shared storage system; the historical identity data of the member user comprises: the system comprises a member user account, a first channel user account bound with the member user account and/or at least one second channel user account associated with the first channel user account;

detecting whether one or more channel user accounts bound with any one or more member user accounts exist in any group of channel user accounts according to historical identity data in the shared storage system; the method comprises the following steps that a plurality of channel user accounts in a group of channel accounts have direct or indirect incidence relation;

if yes, performing synchronous updating processing on the historical identity data of the member users on the group of channel user accounts according to the historical identity data of the one or more member users bound by the one or more channel user accounts in the shared storage system.

2. The method of claim 1, wherein the member user's historical identity data further comprises member resource information, and/or object information of the member object.

3. The method of claim 1, wherein the synchronously updating the historical identity data of the member users for any group of channel user accounts according to the historical identity data of the one or more member users bound to the one or more channel user accounts in the shared storage system further comprises:

if one or more channel user accounts bound with any member user account are detected in any group of channel user accounts, synchronizing the historical identity data of the member user to channel user accounts in the group of channel user accounts except the one or more channel user accounts.

4. The method of claim 3, wherein if it is detected that there are one or more channel user accounts bound to any one member user account in any one group of channel user accounts having a direct or indirect relationship, the method further comprises:

and establishing a binding relationship between channel user accounts in the group of channel user accounts except the one or more channel user accounts and the member user account of the member user in a shared storage system.

5. The method of claim 1, wherein the synchronously updating the historical identity data of the member users for any group of channel user accounts according to the historical identity data of the one or more member users bound to the one or more channel user accounts in the shared storage system further comprises:

if the fact that a plurality of channel user accounts bound with any plurality of member user accounts exist in any group of channel user accounts and the plurality of member user accounts belong to the same member object is detected, a member selection request is sent to a client corresponding to at least one channel user account, and a member selection result fed back by the client is received;

according to the member selection result, performing integration processing on historical identity data of a plurality of member users;

and synchronizing the integrated historical identity data of the member user to all channel user accounts in the group of channel user accounts.

6. The method of claim 5, wherein after the integrating the historical identity data of the plurality of member users, the method further comprises:

and establishing a binding relationship between each channel user account in the group of channel user accounts and the selected member user account in the shared storage system.

7. The method according to any one of claims 1 to 6, wherein after the processing of synchronously updating the historical identity data of the member users of any one group of channel user accounts according to the historical identity data of the one or more member users bound to the one or more channel user accounts in the shared storage system, the method further comprises:

judging whether a plurality of channel user accounts in any channel have the same historical identity data of member users or not aiming at each channel;

if yes, historical identity data of the member users of one channel user account in the channel user accounts are reserved, and historical identity data of the member users of other channel user accounts in the channel user accounts are deleted.

8. The method according to any one of claims 1 to 6, wherein after the processing of synchronously updating the historical identity data of the member users of any one group of channel user accounts according to the historical identity data of the one or more member users bound to the one or more channel user accounts in the shared storage system, the method further comprises:

receiving a member registration request initiated by any channel account, wherein the member registration request comprises the identity data of a newly registered member user;

judging whether at least one channel user account to be synchronized having a direct or indirect association relation with a channel user account in the identity data of the newly registered member user exists; and if so, synchronizing the identity data of the newly registered member user to the at least one channel user account to be synchronized.

9. The method of any of claims 1-6, wherein the method further comprises:

receiving a member binding change request initiated by a user account of any channel, wherein the member binding change request comprises the identity data of a newly bound member user;

judging whether at least one channel user account to be bound having direct or indirect incidence relation with the channel user account in the identity data of the newly bound member user exists; and if so, performing binding change processing on the identity data of the member user on the at least one channel user account to be bound according to the newly bound identity data of the member user.

10. The method of any of claims 1-6, wherein the method further comprises:

receiving resource updating data of the member user returned by any channel user account;

and updating the member user resource information of the corresponding member users in the shared storage system according to the resource updating data.

11. A synchronization apparatus of identity data, comprising:

the storage module is suitable for acquiring historical identity data of at least one member user and storing the historical identity data of the at least one member user into the shared storage system; the historical identity data of the member user comprises: the system comprises a member user account, a first channel user account bound with the member user account and/or at least one second channel user account associated with the first channel user account;

the detection module is suitable for detecting whether one or more channel user accounts bound with any one or more member user accounts exist in any group of channel user accounts according to historical identity data in the shared storage system; the method comprises the following steps that a plurality of channel user accounts in a group of channel accounts have direct or indirect incidence relation;

and the historical member synchronization module is suitable for performing synchronous updating processing on historical identity data of the member users on the group of channel user accounts according to the historical identity data of the one or more member users bound with the one or more channel user accounts in the shared storage system if one or more channel user accounts bound with any one or more member user accounts exist.

12. The apparatus of claim 11, wherein the member user's historical identity data further comprises member resource information, and/or object information of the member object.

13. The apparatus of claim 11, wherein the synchronization module is further adapted to:

if one or more channel user accounts bound with any member user account are detected in any group of channel user accounts, synchronizing the historical identity data of the member user to channel user accounts in the group of channel user accounts except the one or more channel user accounts.

14. The apparatus of claim 13, wherein the apparatus further comprises: and the binding module is suitable for establishing a binding relationship between the channel user accounts in the group of channel user accounts except the one or more channel user accounts and the member user account of the member user in a shared storage system.

15. The apparatus of claim 11, wherein the synchronization module is further adapted to:

if the fact that a plurality of channel user accounts bound with any plurality of member user accounts exist in any group of channel user accounts and the plurality of member user accounts belong to the same member object is detected, a member selection request is sent to a client corresponding to at least one channel user account, and a member selection result fed back by the client is received;

according to the member selection result, performing integration processing on historical identity data of a plurality of member users;

and synchronizing the integrated historical identity data of the member user to all channel user accounts in the group of channel user accounts.

16. The apparatus of claim 15, wherein the apparatus further comprises: and the binding module is suitable for establishing the binding relationship between each channel user account in the group of channel user accounts and the selected member user account in the shared storage system.

17. The apparatus of any one of claims 11-16, wherein the apparatus further comprises:

the binding correction module is suitable for judging whether a plurality of channel user accounts in any channel have the same historical identity data of the member user or not aiming at each channel; if yes, historical identity data of the member users of one channel user account in the channel user accounts are reserved, and historical identity data of the member users of other channel user accounts in the channel user accounts are deleted.

18. The apparatus of any one of claims 11-16, wherein the apparatus further comprises:

the system comprises a newly-added member synchronization module, a member registration module and a member registration module, wherein the newly-added member synchronization module is suitable for receiving a member registration request initiated by an account number of any channel, and the member registration request comprises the identity data of a newly-registered member user; judging whether at least one channel user account to be synchronized having a direct or indirect association relation with a channel user account in the identity data of the newly registered member user exists; and if so, synchronizing the identity data of the newly registered member user to the at least one channel user account to be synchronized.

19. The apparatus of any one of claims 11-16, wherein the apparatus further comprises:

the system comprises a binding changing module, a binding changing module and a binding changing module, wherein the binding changing module is suitable for receiving a member binding changing request initiated by a user account in any channel, and the member binding changing request comprises identity data of a newly bound member user; judging whether at least one channel user account to be bound having direct or indirect incidence relation with the channel user account in the identity data of the newly bound member user exists; and if so, performing binding change processing on the identity data of the member user on the at least one channel user account to be bound according to the newly bound identity data of the member user.

20. The apparatus of any one of claims 11-16, wherein the apparatus further comprises:

the updating module is suitable for receiving resource updating data of the member user returned by the user account of any channel; and updating the member user resource information of the corresponding member users in the shared storage system according to the resource updating data.

21. A computing device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;

the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the operation corresponding to the identity data synchronization method according to any one of claims 1-10.

22. A computer storage medium having stored therein at least one executable instruction for causing a processor to perform operations corresponding to the method of synchronizing identity data according to any one of claims 1-10.

Images