WO2021129541A1

WO2021129541A1 - Synchronization of identity data

Info

Publication number: WO2021129541A1
Application number: PCT/CN2020/137756
Authority: WO
Inventors: 方思维
Original assignee: 浙江口碑网络技术有限公司
Priority date: 2019-12-23
Filing date: 2020-12-18
Publication date: 2021-07-01
Also published as: CN111147568B; CN111147568A

Abstract

Provided are a method and device for synchronization of identity data. The method comprises: acquiring historical identity data of at least one member user, and storing the historical identity data of the at least one member user in a sharable storage system; performing, according to the historical identity data in the sharable storage system, detection on any group of channel user accounts to determine whether there is one or more channel user accounts bound to any one or more member user accounts; and if so, then on the basis of the historical identity data of the one or more member users to which the one or more channel user accounts are bound, perform synchronous updating of historical identity data of a member user of a channel user account.

Description

Sync identity data

Technical field

The present disclosure relates to the field of Internet technology, and 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 in the platform or client can be used as a way for the user to complete consumption activities. Records and vouchers, in turn, facilitate the user's consumption behavior. In the prior art, the membership identities of users on different Internet platforms or clients are completely isolated and are not related to each other. For example, the membership identities on platform A and the membership identities on platform B are independent systems of their respective platforms. For management, the membership identities of the independent systems of the two platforms cannot be connected.

However, the inventor discovered in the process of implementing the embodiments of the present disclosure that the member identity management method in the prior art has at least the following problem: the membership identities between the platforms are isolated from each other, so that the identity data between the platforms cannot be communicated. Facilitate the unified analysis and processing of identity data.

Summary of the invention

According to one aspect of the embodiments of the present disclosure, there is provided a method for synchronizing identity data, including: acquiring historical identity data of at least one member user, and storing the historical identity data of the at least one member user in a shared storage system; member; The user’s historical identity data includes: a member user account, a first channel user account bound to a member user account, and/or at least one second channel user account associated with the first channel user account; according to the shared storage system The historical identity data of any one group of channel user accounts, to detect whether there are one or more channel user accounts bound to any one or more member user accounts in any group of channel user accounts; among them, multiple channel user accounts in a group of channel user accounts There is a direct or indirect relationship between the two; if it is, the member user’s account of the channel user account of the group of channel users is determined based on the historical identity data of one or more member users bound to the one or more channel user accounts in the shared storage system. Synchronous update processing of historical identity data.

According to another aspect of the embodiments of the present disclosure, there is provided an identity data synchronization device, which includes a storage module, a detection module, and a historical member synchronization module.

The storage module 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 a shared storage system; the historical identity data of the member user includes: a member user account, which is tied to a member user account 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 are one or more channel user accounts bound to any one or more member user accounts in any group of channel user accounts based on the historical identity data in the shared storage system; among them, one group The multiple channel user accounts in the channel user accounts have a direct or indirect relationship between each other.

The historical member synchronization module is suitable for if there are one or more channel user accounts bound to any one or more member user accounts, 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 synchronized to update the historical identity data of the member user for the group of channel user accounts.

According to another aspect of the embodiments of the present disclosure, there is provided a computing device, including: a processor, a memory, a communication interface, and a communication bus. The processor, the memory, and the communication interface complete each other through the communication bus. Inter-communication; the memory is used to store executable instructions, and the executable instructions cause the processor to perform operations corresponding to the aforementioned identity data synchronization method.

According to another aspect of the embodiments of the present disclosure, a computer storage medium is provided, and executable instructions are stored in the storage medium, and the executable instructions cause a processor to perform operations corresponding to the aforementioned identity data synchronization method.

Description of the drawings

By reading the detailed description of some embodiments below, various other advantages and benefits will become clear to those of ordinary skill in the art. The drawings are only used for the purpose of illustrating some embodiments, and are not considered as a limitation to the embodiments of the present disclosure. Also, throughout the drawings, the same reference symbols are used to denote the same components.

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

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

FIG. 3 shows a flowchart of a method for synchronizing identity data provided by another embodiment of the present disclosure;

Fig. 4 shows a schematic structural diagram of a device for synchronizing identity data provided by an embodiment of the present disclosure.

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

Detailed ways

Hereinafter, exemplary embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings. Although the drawings show exemplary embodiments of the present disclosure, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure 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 disclosure. 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 a shared storage system; the historical identity data of the member user includes: a member user account, and the first member user account bound to the member user account. 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 that the historical identity data of one or more channels can be aggregated. Among them, the historical identity data obtained here is the identity data historically generated in each channel before synchronization. Among them, the first channel user account is the channel account of the source channel to which the member user account belongs, and the second channel user account is a channel account that is different from the source channel and is associated with the first channel user account. For example, the second channel user account may be directly associated with the first channel user account. For another example, the second channel user account may be directly and indirectly associated with the first channel user 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, and the channel user 11 has registered a member of a certain brand on channel 1 and is a member If the user account is the member user 111, the first channel user account is the channel user 11, and the second channel user account is the channel user 22.

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

The direct association relationship refers to the direct association of channel user accounts established, 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, in channel 1, an association between channel user 11 of this channel 1 and channel user 22 of another channel 2 is established, and at the same time, the relationship between channel user 22 of this channel 2 and channel user 33 of another channel 3 is established in channel 2. Associated, channel user 11 and channel user 22, and channel user 22 and channel user 33 respectively have a direct relationship, while channel user 11 and channel user 33 have an indirect relationship, and channel user 11, channel user 22, and channel user 33 constitutes a set of channel user accounts.

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

Step S130: 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 group of channel user accounts are synchronized to update the historical identity data of the member users.

Specifically, the historical identity data of the member users is synchronized and 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 in sync, and then can be used in each channel user account The member user. For example, channel user 11, channel user 22, and channel user 33 are a set of channel user accounts, where channel user 11 is bound to KFC member users, while channel user 22 and channel user 33 are not bound to KFC members The user can synchronize the historical identity data of the KFC member user bound to 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 there is one member user (obviously belonging to one member object), or if there are multiple member users and the multiple member users belong to the same member object, then synchronous update processing can be performed on the member object; or, if the member There are multiple users, and the multiple member users belong to at least two member objects. The synchronization update process can be performed sequentially for each member object in the same manner as the same member object, or for each member object according to the same member object. The way that the object undergoes synchronous update processing at the same time carries out synchronous update processing. Among them, the member object refers to the entity to which the member user belongs, for example, the brand or shop to which the member user belongs.

This embodiment can be implemented by a synchronization system, which can communicate with various channel systems, obtain the identity data of each channel, and synchronize the identity data to the channel user accounts of each channel; and, the synchronization system can share storage Perform operations on the identity data stored in the system, for example, modify or delete identity data.

According to the method for synchronizing identity data provided in this embodiment, the historical identity data of at least one member user is obtained from various channels and stored in a shared storage system; and, for any group of channel user accounts, based on the shared storage system The historical identity data in the group of channel user accounts detects whether there are one or more member users that need to be synchronized update processing, and accurately detects the synchronization update requirements of historical members; and, when a group of channel user accounts are detected with If one or more channel user accounts are bound to any one or more member user accounts, if it is determined that there is a synchronization update requirement, then based on the one or more member users bound to the one or more channel user accounts in the shared storage system The historical identity data performs synchronous update processing of the historical identity data of the member users on 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. It can be seen that 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 conducive to more historical member data. Channel integration analysis and processing.

Fig. 2 shows a flowchart of a method for synchronizing identity data provided by another embodiment of the present disclosure. In this embodiment, description is made for the case 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 historical identity data of at least one member user, and store the historical identity data of the at least one member user in a shared storage system. The historical identity data of the member user includes: a member user account, a first channel user account bound to the member user account, and/or at least one second channel user account associated with the first channel user account.

In some embodiments, the historical identity data of the member user also includes member resource information and/or object information of the member object. 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. The object information of the member object refers to the identification information of the entity, such as brand name, brand code, etc. Wait. The above-defined data items in the historical identity data are just examples. During specific implementation, those skilled in the art can add other data items to the historical identity data according to actual needs, for example, adding the channel identifier of the source channel of the member user.

Specifically, when the identity data is synchronized, it is usually carried out 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 are one or more channel user accounts bound to any one or more member user accounts in any group of channel user accounts; among them, a group of channel users The multiple channel user accounts in the account have a direct or indirect association relationship; if so, step S230 is executed; if not, the method ends.

Specifically, according to the association relationship between channel user accounts in several target channels, each group of channel user accounts is determined. Among them, the first channel user account and at least one second channel user account in the historical identity data of the member user can be queried. Channel user accounts are used 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, detect 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, then there are one or more channel user accounts bound to any one or more member user accounts in the 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, if the historical identity data in the shared storage system includes a piece of historical identity data of channel user 11 as the first channel user account a, and containing 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 indicates that there is at least one channel in the group of channel user accounts before the synchronization update process The user account has been bound to the member user. At this time, step S230 needs to be performed to perform a synchronous update process, so that the historical identity data of the bound member user is bound to multiple channel user accounts in the group of channel user accounts. The historical identity data of member users is kept in sync. On the contrary, there is no need to perform synchronization update processing.

Step S230: Send a member selection request to the client 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, perform integration processing on the historical identity data of multiple member users; The historical identity data of member users is synchronized to all channel user accounts in the group of channel user accounts.

This embodiment mainly takes a case where it is detected that there are multiple channel user accounts bound to multiple member user accounts in a group of channel user accounts, and the multiple member user accounts belong to the same member object. This situation mainly refers to that at least two channel user accounts in the group of channel user accounts are respectively bound to different member user accounts of the same member object. Table 1 below shows a specific example of this situation.

Table 1

In Table 1, the association between channel user 11 of this channel 1 and channel user 22 of another channel 2 is established in channel 1, and at the same time, channel user 22 of this channel 2 and channel 3 of another channel are established in channel 2. Association of user 33; channel user 11 and channel user 22, and channel user 22 and channel user 33 respectively have a direct relationship, channel user 11 and channel user 33 have an indirect relationship, channel user 11, channel user 22 and channel user 33 It constitutes a set of channel user accounts. In Table 1, the channel user 11 and the channel user 22 are respectively bound to the member user 111 and the member user 222, and the member user 111 and the member user 222 belong to the 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 corresponding to at least one channel user account in the group of channel user accounts, where the at least one channel user account can be any one or more of the group of channel user accounts. A channel user account, optionally, in response to a member user viewing request initiated by a client corresponding to one or more channel user accounts in the group of channel users, sending a member selection request to the client that initiated the member user viewing request; or , Can send a member selection request to the client corresponding to each channel user account in the group of channel user accounts. Among them, open the member center page on the client to initiate a request for member users to view. In addition, the member selection request carries one or more of the historical identity data of multiple member users, so that the client can display the information of multiple member users for selection on the client after receiving the member selection request. Card information, for example, display member user account, membership level, etc. information.

Further, the client terminal receives the user's selection operation, and feeds back the result of the member selection to the execution system of the present disclosure; after receiving the result of the member selection, determines the selected target member user; and then performs the historical identity data of multiple member users Integrated processing, integrating 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, for example, accumulate member points to get updated member points. After completing the above-mentioned integration processing, 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 above synchronization update process.

Suppose that the member selection request of the member user 111 and the member user 222 is sent to the client of the channel user 33, the channel user 33 returns the member selection result of the member user 111, that is, the target member user is the member user 111; the member user 111 and the member user The member resource information of 222 is integrated. For example, if the resource s1 and the resource s2 are accumulated to obtain the updated member resource information of the member user 111, the integrated historical member data can be obtained as shown in Table 2.

Table 2

In Table 2, the integrated historical member data is synchronized to the channel user 11, the channel user 22, and the channel user 33, and the synchronization update process between the group of channel users is completed.

In some embodiments of the present disclosure, the 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-mentioned synchronization in the shared storage system can be synchronized to each channel. When the historical identity data of the member user of the user account is updated, the updated message is sent to each channel user account bound to the member user account in the historical identity data in a timely manner, and the historical identity data of the member user is updated in a timely manner.

In some implementations, after the synchronization update process is completed, for each channel, it is determined whether multiple channel user accounts in any channel have the same historical identity data of member users; if so, the multiple channel user accounts are retained The historical identity data of member users of one channel user account, and the historical identity data of member users of other channel user accounts in multiple channel user accounts are deleted. In an example, 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 members User 111 and member user 111' cannot be bound to member user 111 at the same time; at the same time, among historical member users, there are at least two channel user accounts from different channels to register or bind 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 member data as shown in Table 3 below.

table 3

In Table 3, the channel user 33' is the channel user account of channel 3, and the channel user 33' has no direct or indirect relationship with the channel user 11. After the synchronization update process is completed, there are channel users 33 and channel 3 The channel users 33' are all bound to the member user 111. In this case, it 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 some embodiments, after the synchronization update is completed, for the non-source channel of the selected target user member (the source channel will not violate the above principles), multiple channels of each non-source channel are judged Whether there are two channel user accounts in the user account that are bound to the same member user account, if so, the binding relationship is retained and deleted, so that different channel user accounts of the same channel can only be bound to different members of the same member object Member user. In actual implementation, the process of judging duplicate member users in the same channel can be performed after the synchronization update processing of each group of channel user accounts is completed to ensure that the synchronization update process does not violate the above principles at all times; or, it can also be performed in all groups. The channel user account synchronization update process is executed after the completion of the process, in order to reduce the frequency of data processing.

After the above steps S210 to S230, the synchronization of the historical identity data between the user accounts of each group of channels is completed for the historical member users; the following step S240 is to further add real-time data after the synchronization of the historical identity data is completed. The registered member users of the synchronizing update process.

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

In this embodiment, the composition of the identity data of the newly registered member user is similar to the historical identity data, and so is the identity data of the newly bound member user hereinafter.

Specifically, 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 not been bound to the member user account of the member object (indicating that a member user account containing 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 disclosure through the channel user account. For example, channel user account 11 has not been bound to a member user account of brand n. If a member user of brand n is registered on the client side of channel user account 11, a member registration request will be initiated to the execution system. And, the execution system receives a member registration request initiated by any channel user account, and the member registration request contains the identity data of the newly registered member user; it is determined whether there is a channel user account directly related to the identity data of the newly registered member user. Or at least one channel user account to be synchronized in an indirect relationship, where, if it exists, it indicates that there is a need to synchronize and update 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 channel user account 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 synchronization update processing, only the identity data of the newly registered member user will be saved in the shared storage system Just medium.

In addition, in some embodiments of the present disclosure, after completing the synchronization update processing of the historical identity data of historical member users and/or the identity data of newly registered member users, a member swap request initiated by any channel user account is received, The member rebinding request contains the identity data of the newly bound member user, where a request to add a member user of the target member object is initiated in the client of any channel user account, and the channel user account has been bound with The member user account of the member object indicates that the member user account bound to the channel user account history needs to be replaced with a newly-added member user account, and then a member replacement request is initiated to the execution system of this disclosure through the channel user account ; The execution system receives the request for rebinding of the member, and judges whether there is at least one channel user account to be rebinding that has a direct or indirect relationship with the channel user account in the identity data of the newly bound member user, and if it exists, it indicates There is a channel user account that needs to be re-bonded simultaneously, and the at least one channel user account to be re-bonded is re-bonded according to the identity data of the newly-bound member user. In the process, the identity data of the newly bound member user is synchronized to at least one channel user account to be re-bonded, so that at least one channel user account to be re-bonded replaces the bound member user account of the member object.

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

Specifically, after completing the synchronization of 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 among the user accounts of each group of channels, the new The interface is used to update the synchronized identity data, where the new interface refers to the channel interface corresponding to the synchronized user account of each channel. 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 channel 1, and the historical identity data of the member user 111 is synchronized to the channel user account 11. After account number 22 and channel user account 33, you can update the historical member data through channel 1, channel 2 and channel 3, and synchronize these updated data to other unupdated channels through the shared storage system. Channel user account.

Further, after the synchronization is completed, the member resource information can be updated through any channel user account, for example, the member points are updated, and the resource update data is returned to the execution system of the present disclosure; the execution system of the present disclosure is receiving After the resource is updated, 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, so that 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 the respective 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 any channel user account directly or indirectly associated with a channel user account in a certain group of channel user accounts is newly added or decreased, the second channel user account in the synchronized identity data is updated, and the channel account data is updated Feedback to the execution system of the present disclosure; after receiving the channel account update data, the execution system of the present disclosure 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 The binding relationship between the newly added (or reduced) second channel user account and the member user account of the corresponding member user, so as to send updated historical identity data only to the channel user account that has a direct or indirect connection. Among them, if the update situation is that the second channel user account is increased, the second channel user account in the synchronized member user’s identity data in the shared storage system is added, and the newly added second channel user account and The binding relationship of the member user account of the synchronized member user is synchronized, and the historical identity data of the member user is synchronized to the newly added second channel user account.

In addition, in some embodiments of the present disclosure, when an unbinding request initiated by any channel user account is received, the unbinding request carries the channel user account requested to initiate and the member user account requesting unbinding; Binding request queries a group of channel user accounts where the channel user account initiated by the request is located, unbinds each channel user account in the group of channel user accounts in the shared storage system with the member user account requesting to unbind, and submits the request to the In the group channel user account, other channel user accounts except the channel user account that requested to initiate send an unbinding instruction, and the unbinding instruction carries the member user account that requests unbinding. In this way, after completing the unbinding of the member user account in a channel user account, the unbinding of each channel user account in a group of channel user accounts and the member user account requesting to unbind can be completed to realize the same member user. Quick unbinding of accounts in channel user accounts of multiple channels.

According to the method for synchronizing identity data provided in this embodiment, the historical identity data of at least one member user is obtained from various channels and stored in a shared storage system; and, for any group of channel user accounts, based on the shared storage system The historical identity data in the group of channel user accounts detects whether there are one or more member users that need to be synchronized update processing, and accurately detects the synchronization update needs of historical members. When it is determined that there is a synchronization update need, the synchronization update processing is performed, and the process is completed. Synchronization of historical identity data; and further synchronization update processing of 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 can be synchronized in real time; moreover, after the synchronization update processing is completed, By receiving an update request initiated by a 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 it for use. It can be seen that this embodiment can perform synchronous update processing on historical identity data and 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 conducive to the multi-channel integration of member data. .

Fig. 3 shows a flowchart of a method for synchronizing identity data provided by another embodiment of the present disclosure. In this embodiment, description is made for the case where there are one or more channel user accounts bound to any member user account in any group of channel user accounts. As shown in Figure 3, the method includes the following steps.

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

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

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

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

This embodiment is mainly described based on the case where one or more channel user accounts bound to a member user account are detected in a group of channel user accounts. This situation mainly refers to the group of channel user accounts that are bound to only one member user account. Specifically, it can be that 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 the synchronization update process is performed, the historical identity data of the member user can be synchronized to the channel user account of the group of channel user accounts that is not bound to the member user account. At the same time, in an embodiment, a binding relationship between channel user accounts in the group of channel user accounts other than the one or more channel user accounts and the member user account of the member user is established in the shared storage system, That is, the binding relationship between the channel user account that is not bound to the member user account in the group of channel user accounts and the member user account is established, so that the shared storage system stores each channel user account in the group of channel user accounts and the member The binding relationship of the user accounts further facilitates 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 implementations, after the synchronization update process is completed, for each channel, it is determined whether multiple channel user accounts in any channel have the same historical identity data of member users; if so, the multiple channel user accounts are retained The historical identity data of the member user possessed by one channel user account is deleted, and the historical identity data of the member user possessed by other channel user accounts in multiple channel user accounts is deleted.

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

In some embodiments, a member swap request initiated by a user account of any channel is received, and the member swap request includes the identity data of the newly bound member user; and at least one member is paired according to the identity data of the newly bound member user. The user account of the channel to be re-bonded performs the re-bonding process of the member user's identity data.

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

In the above embodiment of FIG. 3, only the differences from the embodiment of FIG. 2 are described in detail, and the remaining parts that are not described in detail are the same as the implementation principles and processes of the corresponding parts in the embodiment of FIG. 2 , I won’t repeat it here.

According to the identity data synchronization method provided in this embodiment, the historical identity data and the new identity data generated in real time can be synchronized and updated, 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 members. Multi-channel integration of data.

In addition, in some other embodiments of the present disclosure, for any number of member user accounts belonging to multiple member objects, 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 in FIG. 2 is used to perform synchronization update processing. If the member user account of the member object is one, the method of the embodiment in FIG. 3 is used to perform synchronization update processing.

Fig. 4 shows a schematic structural diagram of a device for synchronizing identity data provided by an embodiment of the present disclosure. As shown in FIG. 4, the device includes: a storage module 410, a detection module 420, and a historical member synchronization module 430.

The storage module 410 is adapted to obtain historical identity data of at least one member user, and store the historical identity data of the at least one member user in a shared storage system; the historical identity data of the member user includes: member user account, and 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 are one or more channel user accounts bound to any one or more member user accounts in any group of channel user accounts based on the historical identity data in the shared storage system; among them, one Multiple channel user accounts in a group channel user account have a direct or indirect relationship between each other.

The historical member synchronization module 430 is adapted to, if there are one or more channel user accounts bound to any one or more member user accounts, 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 multiple member users performs a synchronous update process of the historical identity data of the member users on the group of channel user accounts.

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

In an embodiment, the synchronization module is further adapted to: if one or more channel user accounts bound to a member user account are detected in a group of channel user accounts, then the historical identity of the member user The data is synchronized to channel user accounts other than the one or more channel user accounts in the group of channel user accounts.

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

In an embodiment, the synchronization module is further adapted to: if it is detected that there are multiple channel user accounts bound to multiple member user accounts in a group of channel user accounts, and the multiple member user accounts belong to the same member object Send a member selection request to the client corresponding to at least one of the channel user accounts, and receive the member selection result fed back by the client; according to the member selection result, perform integration processing on the historical identity data of multiple member users; The historical identity data of the member users is synchronized to all channel user accounts in the group of channel user accounts.

In an embodiment, 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 one embodiment, the device further includes: a binding correction module, adapted to determine whether multiple channel user accounts in any channel have the same historical identity data of member users for each channel; if so, keep it The historical identity data of member users of one channel user account in multiple channel user accounts, and the historical identity data of member users of other channel user accounts in multiple channel user accounts are deleted.

In one embodiment, the device further includes: a newly-added member synchronization module, adapted to receive a member registration request initiated by a user account of any channel, the member registration request including the identity data of the newly registered member user; to determine whether There is at least one channel user account to be synchronized that has a direct or indirect association relationship with the channel user account in the identity data of the newly registered member user; if so, the identity data of the newly registered member user is synchronized to the At least one user account of the channel to be synchronized.

In an embodiment, the device further includes: a binding swap module, adapted to receive a member swap request initiated by a user account of any channel, and the member swap request includes the identity data of the newly bound member user; Determine whether there is at least one channel user account that is directly or indirectly associated with the channel user account in the identity data of the newly bound member user; if so, according to the identity of the newly bound member user The data performs an exchange process of the identity data of the member user on the at least one channel user account to be exchanged.

In one embodiment, the device further includes: an update module, adapted to receive resource update data of member users returned from user accounts of any channel; and perform membership of corresponding member users in the shared storage system according to the resource update data. Update processing of user resource information.

The embodiment of the present disclosure provides a non-volatile computer storage medium, the computer storage medium stores at least one executable instruction, and the computer executable instruction can execute the identity data synchronization method in any of the foregoing method embodiments.

FIG. 5 shows a schematic structural diagram of a computing device provided by an embodiment of the present disclosure, and the specific embodiment of the present disclosure 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 communication interface (Communications Interface) 504, a memory (memory) 506, and a communication bus 508. Among them, 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 other devices, such as network elements such as clients or other servers. The processor 502 is configured to execute executable instructions 510, and specifically can execute relevant steps in the foregoing embodiment of the method for synchronizing identity data of a computing device.

Specifically, the executable instruction 510 may include a program code, and the program code includes a computer operation instruction.

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 the embodiments of the present disclosure. The one or more processors included in the computing device may be the same type of processor, such as one or more CPUs, or different types of processors, such as one or more CPUs and one or more ASICs.

The memory 506 is used to store executable instructions 510. The memory 506 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), for example, at least one disk memory.

The executable instruction 510 may specifically be used to cause the processor 502 to perform the following operations: obtain historical identity data of at least one member user, and store the historical identity data of the at least one member user in a shared storage system; historical identity data of the member user Including: a member user account, a first channel user account bound to a member 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 are one or more channel user accounts bound to any one or more member user accounts in any group of channel user accounts; among them, multiple channel user accounts in a group of channel user accounts have two Direct or indirect association relationship; if yes, synchronize the historical identity data of member users for the group of channel user accounts based on the historical identity data of one or more member users bound to the one or more channel user accounts in the shared storage system Update processing.

In one embodiment, the executable instruction 510 causes the processor to perform the following operations: if it is detected that there are one or more channel user accounts bound to a member user account in a group of channel user accounts, then The historical identity data of the member user is synchronized to channel user accounts other than the one or more channel user accounts in the group of channel user accounts.

In one embodiment, the executable instruction 510 causes the processor to perform the following operations: establish channel users in the set of channel user accounts other than the one or more channel user accounts in the shared storage system Account, the binding relationship with the member user account of the one member user.

In one embodiment, the executable instruction 510 causes the processor to perform the following operations: if it is detected that there are multiple channel user accounts bound to multiple member user accounts in a group of channel user accounts, and multiple The member user account belongs to the same member object, sends a member selection request to at least one client corresponding to the channel user account, and receives the member selection result fed back by the client; according to the member selection result, the historical identity data of multiple member users Perform integration processing; synchronize the integrated historical identity data of member users to all channel user accounts in the group of channel user accounts.

In one embodiment, the executable instruction 510 causes the processor to perform the following operations: establishing a binding relationship between each channel user account in the set of channel user accounts and the selected member user account in the shared storage system.

In one embodiment, the executable instruction 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 the member user; if so, Then, the historical identity data of the member user of one channel user account in the multiple channel user accounts is retained, and the historical identity data of the member user of the other channel user accounts in the multiple channel user accounts is deleted.

In one embodiment, the executable instruction 510 causes the processor to perform the following operations: receiving a member registration request initiated by a user account of any channel, the member registration request containing the identity data of the newly registered member user; and determining; Whether there is at least one channel user account to be synchronized that has a direct or indirect association 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 all At least one user account of the channel to be synchronized.

In one embodiment, the executable instruction 510 causes the processor to perform the following operations: receiving a member swap request initiated by a user account of any channel, and the member swap request includes the information of the newly bound member user. Identity data; determine whether there is at least one channel user account that is directly or indirectly associated with the channel user account in the identity data of the newly bound member user; if so, based on the newly bound member The user's identity data performs a rebinding process of the member user's identity data on the at least one channel user account to be rebated.

In one embodiment, the executable instruction 510 causes the processor to perform the following operations: receive resource update data of a member user returned by a user account of any channel; The member user updates the member user resource information.

The algorithms or displays provided here are not inherently related to any particular computer, virtual system or other equipment. Various general-purpose systems can also be used with the teaching based on this. Based on the above description, the structure required to construct this type of system is obvious. In addition, the embodiments of the present disclosure are not directed to any specific programming language. It should be understood that various programming languages can be used to implement the content of the embodiments of the present disclosure described herein, and the above description of specific languages is for the purpose of disclosing the best implementation of the embodiments of the present disclosure.

In the instructions provided here, a lot of specific details are explained. However, it can be understood that the embodiments of the present disclosure may be practiced without these specific details. In some instances, well-known methods, structures, and technologies are not shown in detail, so as not to obscure the understanding of this specification.

Similarly, it should be understood that, in order to simplify the embodiments of the present disclosure and help understand one or more of the various inventive aspects, in the above description of the exemplary embodiments of the present disclosure, the various features of the embodiments of the present disclosure are sometimes grouped together into Single embodiment, figure, or description thereof. However, the disclosed method should not be interpreted as reflecting the intention that the claimed embodiments of the present disclosure require more features than those explicitly recorded in each claim. More precisely, as reflected in the following claims, the inventive aspect lies in less than all the features of a single embodiment disclosed previously. Therefore, the claims following the specific embodiment are thus explicitly incorporated into the specific embodiment, wherein each claim itself serves as a separate embodiment of the present disclosure.

Those skilled in the art can understand that it is possible to adaptively change the modules in the device in the embodiment and set them in one or more devices different from the embodiment. The modules or units or components in the embodiments can be combined into one module or unit or component, and in addition, they can be divided into multiple sub-modules or sub-units or sub-components. Except that at least some of such features and/or processes or units are mutually exclusive, any combination can be used to compare all the features disclosed in this specification (including the accompanying claims, abstract and drawings) and any method or methods disclosed in this manner or All the processes or units of the equipment are combined. Unless expressly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstract and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.

In addition, those skilled in the art can understand that although some embodiments herein include certain features included in other embodiments but not other features, the combination of features of different embodiments means that they are within the scope of the present disclosure. And form different embodiments. For example, in the following claims, any one of the claimed embodiments can be used in any combination.

The various component embodiments of the present disclosure may be implemented by hardware, or by software modules running on one or more processors, or by a combination of them. Those skilled in the art should 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 disclosure. The embodiments of the present disclosure may also be implemented as a device or device program (for example, a computer program and a computer program product) for executing part or all of the methods described herein. Such a program for implementing the embodiments of the present disclosure may be stored on a computer-readable medium, or may have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.

It should be noted that the above-mentioned embodiments illustrate the embodiments of the present disclosure rather than limit the present disclosure, and those skilled in the art can design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be constructed as a limitation to the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of multiple such elements. The embodiments of the present disclosure can be implemented by means of hardware including several different elements and by means of a suitably programmed computer. In the unit claims listing several devices, several of these devices may be embodied in the same hardware item. The use of the words first, second, and third, etc. do not indicate any order. These words can be interpreted as names. Unless otherwise specified, the steps in the foregoing embodiment should not be understood as a limitation on the execution order.

Claims

A method for synchronizing identity data, 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 a shared storage system; the historical identity data of the member user includes: a member user account, which is bound to the member user account The first channel 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 are one or more channel user accounts bound to any one or more member user accounts in any group of channel user accounts; among them, a group of channel user accounts There is a direct or indirect relationship between multiple channel user accounts in

If so, 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 users is synchronously updated for the group of channel user accounts.
The method according to claim 1, wherein the historical identity data of the member user further includes member resource information and/or object information of the member object.
The method according to claim 1, wherein the group of channel user accounts is registered on the group of channel user accounts based on 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 update processing of historical identity data further includes:

If it is detected that there are one or more channel user accounts bound to a member user account in the group of channel user accounts, the historical identity data of the member user will be synchronized to the group of channel user accounts except for the one or Channel user accounts other than multiple channel user accounts.
The method according to claim 3, wherein if it is detected that there are one or more channel user accounts bound to a member user account in the group of channel user accounts that have a direct or indirect association relationship, the method further comprises:

A binding relationship between 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.
The method according to claim 1, wherein the historical identity data of one or more member users bound to the one or more channel user accounts in the shared storage system is performed on the group of channel user accounts. The synchronization update processing of historical identity data further includes:

If it is detected that there are multiple channel user accounts that are bound to multiple member user accounts in the group of channel user accounts, and the multiple member user accounts belong to the same member object, report to the client corresponding to at least one of the channel user accounts Sending a member selection request, and receiving the member selection result fed back by the client;

According to the result of member selection, the historical identity data of multiple member users will be integrated and processed;

Synchronize the integrated historical identity data of member users to all channel user accounts in the group of channel user accounts.
The method according to claim 5, wherein, after the integrated processing of the historical identity data of multiple member users, the method further comprises:

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.
The method according to any one of claims 1 to 6, wherein the historical identity data of one or more member users bound to the one or more channel user accounts in the shared storage system is for the group After the channel user account performs the synchronization update processing of the historical identity data of the member user, 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, the historical identity data of the member user of one channel user account in the multiple channel user accounts is retained, and the historical identity data of the member user of the other channel user accounts in the multiple channel user accounts is deleted.
The method according to any one of claims 1-7, wherein the historical identity data of one or more member users bound to the one or more channel user accounts in the shared storage system is for the group After the channel user account performs the synchronization update processing of the historical identity data of the member user, the method further includes:

Receiving a member registration request initiated by a user account of any channel, the member registration request including 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 association 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.
The method according to any one of claims 1-8, wherein the method further comprises:

Receiving a member swap request initiated by a user account of any channel, where the member swap request includes the identity data of the newly bound member user;

Determine whether there is at least one channel user account that is directly or indirectly associated with the channel user account in the identity data of the newly bound member user; if so, according to the identity of the newly bound member user The data performs an exchange process of the identity data of the member user on the at least one channel user account to be exchanged.
The method according to any one of claims 1-9, wherein the method further comprises:

Receive resource update data of member users returned from user accounts of any channel;

According to the resource update data, the corresponding member user in the shared storage system is updated with member user resource information.
A device for synchronizing identity data includes:

The storage module 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 a shared storage system; the historical identity data of the member user includes: a member user account, and A first channel user account bound to a member 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 are one or more channel user accounts bound to any one or more member user accounts in any group of channel user accounts based on the historical identity data in the shared storage system; wherein, Multiple channel user accounts in a group of channel user accounts are directly or indirectly related to each other;

The historical member synchronization module is adapted to, if there are one or more channel user accounts bound to any one or more member user accounts, according to the one or more channel user accounts bound to the one or more channel user accounts in the shared storage system Or the historical identity data of multiple member users performs synchronous update processing of the historical identity data of the member users on the channel user account of the group.
The device according to claim 11, wherein the historical identity data of the member user further includes member resource information and/or object information of the member object.
The device according to claim 11, wherein the synchronization module is further adapted to:

If it is detected that there are one or more channel user accounts bound to a member user account in a group of channel user accounts, the historical identity data of the member user will be synchronized to the group of channel user accounts except for the one or Channel user accounts other than multiple channel user accounts.
The device according to claim 13, wherein the device further comprises: a binding module, adapted to establish in the shared storage system in addition to the one or more channel user accounts of the group of channel user accounts The binding relationship between the channel user account of the member user account and the member user account of the member user.
The device according to claim 11, wherein the synchronization module is further adapted to:

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

According to the result of member selection, the historical identity data of multiple member users will be integrated and processed;

Synchronize the integrated historical identity data of member users to all channel user accounts in the group of channel user accounts.
The device according to claim 15, wherein the device further comprises: a binding module, adapted to establish a binding between each channel user account in the set of channel user accounts and the selected member user account in the shared storage system Definite relationship.
The device according to any one of claims 11-16, wherein the device further comprises:

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 member users; if so, retain the member users of one channel user account among multiple channel user accounts The historical identity data of multiple channel user accounts is deleted, and the historical identity data of member users of other channel user accounts in multiple channel user accounts is deleted.
The device according to any one of claims 11-17, wherein the device further comprises:

A newly-added member synchronization module is suitable for receiving member registration requests initiated by user accounts of any channel. The member registration request contains the identity data of the newly registered member user; it is judged whether there is any identity data with the newly registered member user. The channel user account of has at least one channel user account to be synchronized with a direct or indirect association relationship; if so, the identity data of the newly registered member user is synchronized to the at least one channel user account to be synchronized.
The device according to any one of claims 11-18, wherein the device further comprises:

The rebinding module is adapted to receive a member rebinding request initiated by a user account of any channel, and the member rebinding request includes the identity data of the newly bound member user; and judging whether there is any connection with the newly bound member user The channel user account in the identity data has at least one channel user account to be swapped with a direct or indirect association; if so, the at least one channel user account to be swapped is performed according to the identity data of the newly bound member user Re-binding processing of member user's identity data.
The device according to any one of claims 11-19, wherein the device further comprises:

The update module is adapted to receive the resource update data of the member user returned by any channel user account; according to the resource update data, update the member user resource information on the corresponding member user in the shared storage system.
A computing device includes: a processor, a memory, a communication interface, and a communication bus. The processor, the memory, and the communication interface communicate with each other through the communication bus;

The memory is used to store executable instructions, and the executable instructions cause the processor to perform operations corresponding to the identity data synchronization method according to any one of claims 1-10.
A computer storage medium in which executable instructions are stored, and the executable instructions cause a processor to perform operations corresponding to the method for synchronizing identity data according to any one of claims 1-10.