A data synchronization method and device, computer equipment and storage medium

Abstract

The present disclosure provides a data synchronization method and device, computer device and storage medium, wherein the method comprises: receiving a target instruction sent by a user terminal in a first application program, and a first user identifier of the user terminal in the first application program; determining a center user identifier bound with the first user identifier, wherein the center user identifier is used to constitute a binding relationship between user identifiers of each application program; determining whether the center user identifier is bound with a second user identifier, wherein the second user identifier is a user identifier of the user terminal in a second application program; if yes, after determining a response result of the target instruction corresponding to the center user identifier, synchronizing the response result and the first user identifier to a first server corresponding to the first application program, and synchronizing the response result and the second user identifier to a second server corresponding to the second application program.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more specifically, to a data synchronization method, device, computer equipment, and storage medium. Background Technology

[0002] With the widespread use of mobile phones and computers, more and more applications are being used by users. Because different applications use different accounts, typically, one application executes one command, and so on.

[0003] The result cannot be synchronized to another application. For example, if a user books a live broadcast of a match in one application, the other application will still show that the live broadcast of the match has not been booked, which will reduce the user experience. Summary of the Invention

[0004] This disclosure provides at least one data synchronization method, apparatus, computer device, and storage medium.

[0005] 5. In a first aspect, embodiments of this disclosure provide a data synchronization method applied to an account middleware server, comprising:

[0006] Receive the target instruction sent by the user terminal in the first application, and the first user identifier of the user terminal in the first application;

[0007] Determine the central user identifier bound to the first user identifier, wherein the central user identifier is used to form the binding relationship between user identifiers of each application;

[0008] Determine whether the central user identifier is bound to a second user identifier, wherein the second user identifier is the user identifier of the user terminal in the second application;

[0009] If so, after determining the response result of the target instruction corresponding to the central user identifier, the response result and the first user identifier are synchronized to the first server corresponding to the first application, and the response result and the second user identifier are synchronized to the second server corresponding to the second application.

[0010] In one possible implementation, the central user identifier is a user identifier registered by the user terminal within the central application; if the user terminal is not registered in the central application, the central user identifier is a generated virtual identifier.

[0011] The method described in 0 further includes:

[0012] The response result and the central user identifier are synchronized to the third server corresponding to the central application.

[0013] In one possible implementation, the account middleware server stores the binding relationships between multiple user identifiers registered by other applications and the central user identifier;

[0014] The determination of the central user identifier bound to the first user identifier includes:

[0015] In the binding relationship, check whether the first user identifier has a bound user identifier;

[0016] If so, the found user identifier will be used as the central user identifier bound to the first user identifier;

[0017] If not, obtain the user's registration information and determine the central user identifier bound to the first user identifier based on the registration information.

[0018] In one possible implementation, after determining the central user identifier bound to the first user identifier based on the registration information, the method further includes:

[0019] The binding relationship is updated based on the first user identifier and the central user identifier.

[0020] In one possible implementation, the account middleware server stores user identifiers registered by each user client within each application;

[0021] The step of determining the central user identifier bound to the first user identifier based on the registration information includes:

[0022] Create a virtual identifier and receive registration information sent by the user terminal;

[0023] Based on the registration information, check whether the account middleware server stores a central user identifier corresponding to the registration information;

[0024] If so, the found central user identifier will be used as the central user identifier bound to the first user identifier;

[0025] If not, the virtual identifier is determined to be the central user identifier bound to the first user identifier.

[0026] In one possible implementation, determining the response result of the target instruction corresponding to the central user identifier includes:

[0027] The central user identifier is encrypted, and the encrypted central user identifier and the target instruction are sent to the business server.

[0028] Receive the encrypted central user identifier and response result sent by the business server;

[0029] Before synchronizing the response result and the first user identifier to the first server corresponding to the first application, and before synchronizing the response result and the second user identifier to the second server corresponding to the second application, the method further includes:

[0030] The encrypted central user identifier is decrypted to determine the first user identifier and the second user identifier bound to the decrypted central user identifier.

[0031] In one possible implementation, the method further includes:

[0032] The system receives a modification instruction for the response result sent by the user terminal within any application, as well as a third user identifier of the user terminal within that application; wherein the third user identifier is either the first user identifier or the second user identifier.

[0033] Determine the central user identifier bound to the third user identifier, and determine the change result of the change instruction corresponding to the central user identifier;

[0034] The change result and the third user identifier are synchronized to the server corresponding to the third user identifier, and the change result and other user identifiers other than the third user identifier are synchronized to the servers corresponding to the other user identifiers.

[0035] In one possible implementation, when the central user identifier is the virtual identifier, the method further includes:

[0036] Receive the fourth user identifier registered by the user terminal in the central application, sent by the user terminal;

[0037] The virtual identifier in the binding relationship is updated based on the fourth user identifier.

[0038] Secondly, embodiments of this disclosure also provide a data synchronization device, comprising:

[0039] The receiving module is used to receive the target instruction sent by the user terminal in the first application, and the first user identifier of the user terminal in the first application.

[0040] The first determining module is used to determine the central user identifier bound to the first user identifier, wherein the central user identifier is used to form the binding relationship between user identifiers of each application.

[0041] The second determining module is used to determine whether the central user identifier is bound to a second user identifier, wherein the second user identifier is the user identifier of the user terminal in the second application;

[0042] The synchronization module is configured to, if so, after determining the response result of the target instruction corresponding to the central user identifier, synchronize the response result and the first user identifier to the first server corresponding to the first application, and synchronize the response result and the second user identifier to the second server corresponding to the second application.

[0043] In one possible implementation, the central user identifier is a user identifier registered by the user terminal within the central application; if the user terminal is not registered in the central application, the central user identifier is a generated virtual identifier.

[0044] The synchronization module is also used for:

[0045] The response result and the central user identifier are synchronized to the third server corresponding to the central application.

[0046] In one possible implementation, the account middleware server stores the binding relationships between multiple user identifiers registered by other applications and the central user identifier;

[0047] The first determining module, when determining the central user identifier bound to the first user identifier, is used to:

[0048] In the binding relationship, check whether the first user identifier has a bound user identifier;

[0049] If so, the found user identifier will be used as the central user identifier bound to the first user identifier;

[0050] If not, obtain the user's registration information and determine the central user identifier bound to the first user identifier based on the registration information.

[0051] In one possible implementation, after determining the central user identifier bound to the first user identifier based on the registration information, the first determining module is further configured to:

[0052] The binding relationship is updated based on the first user identifier and the central user identifier.

[0053] In one possible implementation, the account middleware server stores user identifiers registered by each user client within each application;

[0054] The first determining module, when determining the central user identifier bound to the first user identifier based on the registration information, is used to:

[0055] Create a virtual identifier and receive registration information sent by the user terminal;

[0056] Based on the registration information, check whether the account middleware server stores a central user identifier corresponding to the registration information;

[0057] If so, the found central user identifier will be used as the central user identifier bound to the first user identifier;

[0058] If not, the virtual identifier is determined to be the central user identifier bound to the first user identifier.

[0059] In one possible implementation, the synchronization module, when determining the response result of the target instruction corresponding to the central user identifier, is used to:

[0060] The central user identifier is encrypted, and the encrypted central user identifier and the target instruction are sent to the business server.

[0061] Receive the encrypted central user identifier and response result sent by the business server;

[0062] Before synchronizing the response result and the first user identifier to the first server corresponding to the first application, and before synchronizing the response result and the second user identifier to the second server corresponding to the second application, the synchronization module is further configured to:

[0063] The encrypted central user identifier is decrypted to determine the first user identifier and the second user identifier bound to the decrypted central user identifier.

[0064] In one possible implementation, the device is also used for:

[0065] The system receives a modification instruction for the response result sent by the user terminal within any application, as well as a third user identifier of the user terminal within that application; wherein the third user identifier is either the first user identifier or the second user identifier.

[0066] Determine the central user identifier bound to the third user identifier, and determine the change result of the change instruction corresponding to the central user identifier;

[0067] The change result and the third user identifier are synchronized to the server corresponding to the third user identifier, and the change result and other user identifiers other than the third user identifier are synchronized to the servers corresponding to the other user identifiers.

[0068] In one possible implementation, when the central user identifier is the virtual identifier, the device is further configured to:

[0069] Receive the fourth user identifier registered by the user terminal in the central application, sent by the user terminal;

[0070] The virtual identifier in the binding relationship is updated based on the fourth user identifier.

[0071] Thirdly, embodiments of this disclosure also provide a computer device, including: a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the computer device is running, the processor communicates with the memory via the bus, and when the machine-readable instructions are executed by the processor, the steps of the first aspect above, or any possible implementation of the first aspect, are performed.

[0072] Fourthly, embodiments of this disclosure also provide a computer-readable storage medium storing a computer program that, when executed by a processor, performs the steps of the first aspect or any possible implementation of the first aspect.

[0073] The data synchronization method, apparatus, computer device, and storage medium provided in this disclosure can, after receiving a target instruction sent by a user terminal from a first application and a first user identifier of the user terminal within the first application, determine a central user identifier bound to the first user identifier, and then determine whether the central user identifier is bound to a second user identifier. If so, after determining the response result corresponding to the target instruction, the response result and the first user identifier are synchronized to a first server corresponding to the first application, and the response result and the second user identifier are synchronized to a second server corresponding to the second application. Using this method, the response result of the target instruction sent by the first application can be synchronized to the servers corresponding to other applications, thereby enabling other applications to obtain the same response result by accessing the corresponding servers, improving the user experience.

[0074] Furthermore, in this embodiment, all application user identifiers are bound to a central user identifier. When any application sends a target instruction, data synchronization can be performed through the response result of the target instruction corresponding to the central user identifier, avoiding conflicts caused by different response results of different applications and improving the data synchronization effect.

[0075] To make the above-mentioned objects, features and advantages of this disclosure more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0076] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings used in the embodiments will be briefly described below. These drawings are incorporated in and constitute a part of this specification. They illustrate embodiments conforming to this disclosure and, together with the specification, serve to explain the technical solutions of this disclosure. It should be understood that the following drawings only show some embodiments of this disclosure and should not be considered as limiting the scope. Those skilled in the art can obtain other related drawings based on these drawings without creative effort.

[0077] Figure 1 A flowchart of a data synchronization method provided by an embodiment of this disclosure is shown;

[0078] Figure 2 A flowchart illustrating a method for determining a central user identifier and establishing a binding relationship between a first user identifier and a central user identifier, as provided in an embodiment of this disclosure, is shown.

[0079] Figure 3 This diagram shows an overall flowchart of a data synchronization method provided by an embodiment of the present disclosure;

[0080] Figure 4 A schematic diagram of the architecture of a data synchronization device provided in an embodiment of this disclosure is shown;

[0081] Figure 5 A schematic diagram of the structure of a computer device provided in an embodiment of this disclosure is shown. Detailed Implementation

[0082] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this disclosure, and not all of them. The components of the embodiments of this disclosure described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this disclosure provided in the accompanying drawings is not intended to limit the scope of the claimed disclosure, but merely represents selected embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0083] With the widespread use of mobile phones and computers, more and more applications are being used by users. Because different applications use different accounts, the results of executing a command in one application are often not synchronized with other applications. For example, if a user books a live match in one application, another application may still show that the match was not booked, thus degrading the user experience.

[0084] Based on the above research, this disclosure provides a data synchronization method, apparatus, computer device, and storage medium. After receiving a target instruction sent by a user terminal from a first application, and a first user identifier of the user terminal within the first application, the method determines a central user identifier bound to the first user identifier. Then, it determines whether the central user identifier is bound to a second user identifier. If so, after determining the response result corresponding to the target instruction, the method synchronizes the response result and the first user identifier to a first server corresponding to the first application, and synchronizes the response result and the second user identifier to a second server corresponding to the second application. Using this method, the response result of the target instruction sent by the first application can be synchronized to the servers corresponding to other applications, thereby enabling other applications to obtain the same response result by accessing the corresponding servers, improving the user experience.

[0085] Furthermore, in this embodiment, all application user identifiers are bound to a central user identifier. When any application sends a target instruction, data synchronization can be performed through the response result of the target instruction corresponding to the central user identifier, avoiding conflicts caused by different response results of different applications and improving the data synchronization effect.

[0086] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0087] In this document, the term "and / or" merely describes a relationship, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" in this document means any combination of at least two of any one or more elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0088] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0089] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0090] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0091] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0092] To facilitate understanding of this embodiment, a data synchronization method disclosed in this disclosure will first be described in detail. The execution subject of the data synchronization method provided in this disclosure is generally an account middleware server. The account middleware server is used to store the user identifiers registered by the user terminal on the servers corresponding to various applications. This data synchronization method can be implemented by the processor calling computer-readable instructions stored in the memory.

[0093] See Figure 1 The diagram shows a flowchart of a data synchronization method provided in an embodiment of this disclosure. The method includes steps 101 to 104, wherein:

[0094] Step 101: Receive the target instruction sent by the user terminal in the first application, and the first user identifier of the user terminal in the first application;

[0095] Step 102: Determine the central user identifier bound to the first user identifier, wherein the central user identifier is used to form the binding relationship between user identifiers of each application.

[0096] Step 103: Determine whether the central user identifier is bound to a second user identifier, wherein the second user identifier is the user identifier of the user terminal in the second application;

[0097] Step 104: If yes, after determining the response result of the target instruction corresponding to the central user identifier, the response result and the first user identifier are synchronized to the first server corresponding to the first application, and the response result and the second user identifier are synchronized to the second server corresponding to the second application.

[0098] The following is a detailed explanation of the steps described above:

[0099] Regarding step 101,

[0100] The target instruction can be, for example, a reservation instruction (such as a reservation for a live stream or a reservation for a download) or a login instruction (such as logging into other applications using a first user identifier). For example, when the target instruction is a reservation instruction, the target instruction is used to instruct the account middleware server to make a reservation based on the first user identifier, which can be the user's account or identity document.

[0101] Specifically, when the account middleware server receives a target instruction sent by the user terminal from the first application, the user terminal may first generate and send the target instruction to the first server corresponding to the first application in response to a first trigger operation. Then, the first server receives the target instruction and finally sends the target instruction to the account middleware server. Here, the target instruction sent by the first server may be generated in response to the target instruction received by the first server.

[0102] For example, after a user triggers the reservation button, the user terminal can send a reservation instruction to the first server, and then the first server can send the reservation instruction to the account middleware server.

[0103] Correspondingly, the first user identifier of the user terminal within the first application received by the account middleware server may be the first user identifier sent by the first server.

[0104] Before sending the first user identifier to the account middleware server, the first server needs to determine the first user identifier of the user terminal within the first application. Therefore, in one possible implementation, the first user identifier can be determined through the following steps A1 to A4:

[0105] A1. The user terminal responds to the first triggering operation and determines the user terminal's login status in the first application.

[0106] Specifically, when the first application is logged in, it stores the key sent by the first server. Therefore, if the key is detected as stored on the user's device, it can be determined that the user is logged in; if the key is not detected as stored on the user's device, it can be determined that the user is not logged in.

[0107] Here, if the login status is logged in, step A2 is executed; if the login status is not logged in, step A3 is executed.

[0108] A2. When the login status is "logged in", the first server can determine the first user identifier of the user terminal based on the key carried when the user terminal sends the target instruction.

[0109] Specifically, when the user logs in, the first server establishes a target session for communication with the user. The target session corresponds to the user's first user identifier, mobile phone number, key, and other related information (here, the method of obtaining personal information such as mobile phone number can be found in paragraphs 7 to 10 of the Specific Implementation Section of this disclosure). When the user sends information to the first server, it carries the key. The first server can determine the target session and the first user identifier corresponding to the user based on the key.

[0110] Here, after step A2 is completed, steps A3 to A4 will not be executed.

[0111] A3. When the login status is not logged in, the user terminal displays a login page and then, in response to the user's login operation, sends the login information of the first application to the first server.

[0112] The login operation may include inputting login information and triggering a login identifier. The login information may include a mobile phone number, password, ID card number, first user identifier, nickname, etc. (For details on how to obtain personal information such as mobile phone number, ID card number, and name, please refer to paragraphs 7 to 10 of the Specific Embodiments section of this disclosure). Specifically, the user-side front-end may use a bridge (JSBridge) to call the login function of the first application and display the login page for the user to log in.

[0113] A4. The first server determines the first user identifier corresponding to the login information, establishes a target session for communication with the user terminal, generates a key corresponding to the target session, and sends the key to the user terminal.

[0114] Specifically, the first server stores a correspondence between login information and user identifiers for each user terminal. The first server can query the login information from this correspondence and determine the first user identifier corresponding to the login information. Here, if the login information includes the first user identifier, the first server can directly determine the first user identifier based on the login information sent by the user terminal.

[0115] Here, due to poor network conditions or user cancellation, user login may fail. In one possible implementation, if the user fails to log in (i.e., if the key is not detected on the user's end), the user's end may display a first prompt message to indicate that the login failed or the target instruction failed to execute, such as "login error" or "appointment failed".

[0116] Regarding step 102,

[0117] In one possible implementation, the central user identifier can be a user identifier registered by the user terminal within a central application. The central application can be at least one application, and the at least one application corresponds to the same user group for storing user identifiers. That is, for any user terminal, there is the same user identifier within the at least one application. For example, user terminal A's account can be used to log in to application A, application B, and application C. If the user terminal is not registered in the central application, the central user identifier can be a generated virtual identifier.

[0118] Here, if the first user identifier is the central user identifier, it is not necessary to determine the central user identifier bound to the first user identifier. Therefore, in one possible implementation, before determining the central user identifier, it can be determined whether the first user identifier is the central user identifier. Specifically, before determining the central user identifier bound to the first user identifier, the first server can receive the application identifier sent by the first application and compare the application identifier with the pre-stored central application identifier of the central application. If they are the same, then the first user identifier is the central user identifier; if they are different, then the first application identifier is not the central user identifier. Here, the central application identifier may include at least one application identifier.

[0119] If the first user identifier is the central user identifier, the process can directly jump to step 103.

[0120] In another possible implementation, the central user identifier may simply be a generated virtual identifier. In this case, it is not necessary to determine whether the first user identifier is the central user identifier.

[0121] In one possible implementation, the account middleware server stores the binding relationships between multiple user identifiers registered by other applications and a central user identifier. When determining the central user identifier bound to the first user identifier, it can search the binding relationships to see if the first user identifier has a bound user identifier. If so, the found user identifier is used as the central user identifier bound to the first user identifier. If not, the registration information of the user terminal is obtained, and the central user identifier bound to the first user identifier is determined based on the registration information.

[0122] The registration information may include the user's mobile phone number, password, ID card number, name, etc. (For the method of obtaining personal information such as mobile phone number, ID card number, name, etc., please refer to paragraphs 7 to 10 of the Specific Implementation Section of this Disclosure). In the binding relationship, any central user identifier can be bound to at least one user identifier registered by another application. For example, central user identifier 1 is bound to user identifier 1 registered by the user terminal in application A and user identifier 2 registered in application B.

[0123] For example, the binding relationship includes: user identifier 1 is bound to central user identifier 1, user identifier 2 and user identifier 3 are bound to central user identifier 2, user identifier 4 is bound to central user identifier 3. If the first user identifier is user identifier 2, then the central user identifier bound to the first user identifier is central user identifier 2. If the first user identifier is user identifier 5, then it is necessary to obtain the registration information of the user terminal and determine the central user identifier bound to the first user identifier based on the registration information.

[0124] Using this method, when a central user identifier is already bound, the central user identifier can be found for data synchronization; when a central user identifier is not bound, a central user identifier that can be used for binding can be determined for data synchronization.

[0125] Here, after the account middleware server searches for the central user identifier in the binding relationship, it can generate a query result and send the query result to the first server.

[0126] In one possible implementation, the account middleware server stores user identifiers registered by each user client within each application; when determining the central user identifier bound to the first user identifier based on the registration information, such as Figure 2 As shown, the following steps B1 to B4 can be used:

[0127] B1. Create a virtual identifier and receive the registration information sent by the user terminal.

[0128] Specifically, the account middleware server can pre-generate virtual identifiers randomly. These generated virtual identifiers are user identifiers other than those stored in the account middleware server's database (including the already generated virtual identifiers). When receiving registration information from the user client, the user client can first send the registration information to the first server, and then the first server can send the registration information to the account middleware server.

[0129] In one possible implementation, to establish a binding relationship between the first user identifier and the central user identifier, in order to protect the user's rights, authorization from the user terminal can be obtained first, i.e., the user's consent can be acquired. When receiving registration information sent by the user terminal, the following steps C1 to C4 can be adopted:

[0130] C1. After receiving the query result, the first server sends an authorization request to the user terminal.

[0131] C2. In response to the authorization request, the user terminal displays an authorization page; wherein the authorization page is used for the user to confirm authorization and input the registration information.

[0132] C3. In response to the second trigger operation on the authorization page, the user terminal sends an authorization instruction carrying the registration information to the first server.

[0133] The second triggering operation can be, for example, a triggering operation on the authorization identifier displayed on the authorization page. Here, if the registration information has been entered on the authorization page, the user terminal can respond to the second triggering operation and send the authorization instruction.

[0134] In steps C1 to C3 above, authorization may fail due to poor network conditions, errors in the first application, or the user closing the authorization page. In one possible implementation, the user terminal may display a second prompt message in the event of authorization failure. The second prompt message may be used to inform the user that the target instruction execution failed and / or authorization failed, such as "appointment failed" or "authorization error".

[0135] C4. The first server sends the registration information to the account middleware server.

[0136] This method allows registration information to be obtained with user authorization, enabling users to decide whether to bind the first user identifier with the central user identifier, thus improving the user experience.

[0137] B2. Based on the registration information, check whether the account middleware server stores a central user identifier corresponding to the registration information.

[0138] Specifically, the user identifiers registered by each user terminal in each application are stored in the account middleware server in correspondence with the registration information of each user terminal. If the user terminal has registered a central user identifier in the central application, the central user identifier registered by the user terminal in the central application can be found in the user group corresponding to the central application based on the registration information.

[0139] If so, proceed to step B3;

[0140] If not, proceed to step B4.

[0141] B3. Use the found central user identifier as the central user identifier bound to the first user identifier.

[0142] The central user identifier found includes a virtual identifier and the user identifier registered by the user terminal in the central application.

[0143] Here, after finding the central user identifier, the virtual identifier created in step B1 can be deleted.

[0144] Once step B3 is completed, step B4 will not be executed.

[0145] B4. The virtual identifier is determined as the central user identifier bound to the first user identifier.

[0146] In one possible implementation, after determining the central user identifier bound to the first user identifier based on the registration information, the binding relationship can be updated based on the first user identifier and the central user identifier.

[0147] Specifically, a correspondence between the first user identifier and the central user identifier can be added to the binding relationship. This way, when performing data synchronization later, the central user identifier can be directly determined from the binding relationship, which speeds up the processing efficiency of the account middleware server.

[0148] Here, when the account middleware server needs to simultaneously establish binding relationships between multiple central user identifiers and multiple user terminal first user identifiers, it cannot determine which user terminal's first user identifier corresponds to each of the multiple central user identifiers. Therefore, for any given first user identifier, such as Figure 2 As shown, the binding relationship between the first user identifier and the central user identifier can be established using the following steps D1 to D3:

[0149] D1. The account middleware server encrypts the central user identifier and sends the encrypted central user identifier to the first server.

[0150] D2. The first server pairs the encrypted central user identifier with the first user identifier, and sends the paired first user identifier and the encrypted central user identifier to the account middleware server.

[0151] D3. The account middleware server decrypts the received encrypted central user identifier to obtain the paired central user identifier and the first user identifier, and adds the paired central user identifier and the first user identifier to the binding relationship.

[0152] Using this method, since the first server has established a session with each user terminal after login, and each session records the processing data corresponding to each user terminal (including the requested virtual identifier and / or the received encrypted central user identifier), it can be determined which encrypted central user identifier should be paired with the first user identifier of each user terminal. This allows multiple user terminals' first user identifiers to be paired with the corresponding central user identifiers simultaneously. In addition, encrypting the central user identifier before sending it to the first server can prevent the central user identifier from being obtained by servers other than the third server corresponding to the central application, thus ensuring the data security of the central user identifier to a certain extent.

[0153] Regarding step 103,

[0154] Specifically, the central user identifier can be found from the binding relationship, and then the user identifier bound to the central user identifier can be used as the second user identifier. Here, if the central user identifier is only bound to the first user identifier, then the second user identifier is empty. In this case, when executing step 104, only the response result and the first user identifier can be synchronized to the first server corresponding to the first application.

[0155] Regarding step 104,

[0156] Specifically, when determining the response result corresponding to the target instruction, the service server for executing the target instruction can be determined first. Then, the target instruction and the central user identifier are sent to the service server to generate a response result corresponding to the central user identifier. Finally, the service server receives the central user identifier and the response result sent by the service server. For example, if the target instruction is a reservation instruction, after sending the target instruction to the service server, the service server can generate a response result (i.e., a reservation result) corresponding to the central user identifier based on the target instruction.

[0157] Then, the account middleware server can store the correspondence between the central user identifier and the response result. Afterwards, based on the binding relationship, a first user identifier and a second user identifier bound to the central user identifier are determined. The response result and the first user identifier are then sent to the first server corresponding to the first application to establish a correspondence between the first user identifier and the response result on the first server. The response result and the second user identifier are then sent to the second server corresponding to the second application to establish a correspondence between the second user identifier and the response result on the second server. In this way, the response results are stored on the servers corresponding to each application. When the user client queries the response result, it can directly send a query request to the server corresponding to the currently used application, and that server will then send the response result to the user client.

[0158] In the process of sending the target instruction to the business server, if the central user identifier is sent directly to the business server, it is easy to cause the information of the central user identifier to be leaked. Therefore, in one possible implementation, when determining the response result corresponding to the target instruction, the central user identifier can be encrypted first, and the encrypted central user identifier and the target instruction can be sent to the business server; then the encrypted central user identifier and the response result sent by the business server can be received.

[0159] Subsequently, before synchronizing the response result and the first user identifier to the first server corresponding to the first application, and before synchronizing the response result and the second user identifier to the second server corresponding to the second application, the encrypted central user identifier is decrypted to determine the first user identifier and the second user identifier bound to the decrypted central user identifier.

[0160] Using this method, the corresponding response result can be obtained from the business server based on the encrypted central user identifier, thereby avoiding the business server directly obtaining the central user identifier and preventing the central user identifier from being intercepted during communication, thus improving information security.

[0161] In one possible implementation, the account middleware server can also synchronize the response result and the central user identifier to the third server corresponding to the central application. Specifically, if the central user identifier is the user identifier registered by the user client in the central application, synchronizing the response result to the third server allows the user client to send a query request to the third server through the central application to obtain the response result sent by the third server.

[0162] Here, if the central user identifier is not bound to the second user identifier, the response result and the central user identifier can also be synchronized to the third server corresponding to the central application.

[0163] In one possible implementation, if the central user identifier is the virtual identifier, the account middleware server can also receive a fourth user identifier sent by the user client that the user client registered in the central application, and then update the virtual identifier in the binding relationship based on the fourth user identifier.

[0164] Specifically, when the user registers the fourth user identifier with the third server, it sends registration information to the third server. The third server then generates the fourth user identifier and sends the registration information and the fourth user identifier to the account middleware server for storage. The account middleware server can then search for the corresponding fourth user identifier based on the registration information. In the binding relationship, it checks whether there is a central user identifier (i.e., a virtual identifier) ​​bound to the fourth user identifier. If it exists, the virtual identifier is replaced with the fourth user identifier.

[0165] In one possible implementation, the response result can also be modified using the following steps E1-E3 and synchronized to all servers:

[0166] E1. Receive a modification instruction for the response result sent by the user terminal in any application, and a third user identifier of the user terminal in the application; wherein the third user identifier is the first user identifier or the second user identifier.

[0167] Specifically, the server corresponding to the third user identifier (i.e., the first server or the second server) may first receive the change instruction sent by the user terminal, and then the server may send the change instruction and the third user identifier of the user terminal to the account middleware server. The change instruction may be, for example, a cancellation instruction.

[0168] E2. Determine the central user identifier bound to the third user identifier, and determine the change result of the change instruction corresponding to the central user identifier.

[0169] Specifically, the account middleware server can modify the response result based on the change instruction to obtain the modified result. For example, if the change instruction is a cancellation instruction and the response result is a reservation result "Live Stream A Reserved", then the account middleware server can change the reservation result to "Live Stream A Not Reserved".

[0170] E3. Synchronize the change result and the third user identifier to the server corresponding to the third user identifier, and synchronize the change result and other user identifiers other than the third user identifier to the servers corresponding to the other user identifiers.

[0171] Here, after receiving the change result and the third user identifier, the server corresponding to the third user identifier can update the response result corresponding to the third user identifier stored in the server to the change result. Similarly, after receiving the change result and the other user identifier, the server corresponding to the third user identifier can update the response result corresponding to the third user identifier stored in the server to the change result, so that the data stored in each server can be updated in a timely manner.

[0172] It should be noted that the third user identifier can also be the central user identifier. If the third user identifier is the central user identifier, only steps E1 and E3 are executed.

[0173] Using this method, the response result can be modified by a change command sent by any application, and the modified result can be synchronized to the server corresponding to each application.

[0174] Finally, a specific implementation process of the data synchronization method is described, such as... Figure 3 As shown, the steps F1 to F12 are included:

[0175] F1. In response to a first trigger operation for the first application, the user terminal generates a target instruction and determines whether the user terminal is logged in to the first application.

[0176] If not, proceed to step F2;

[0177] If so, proceed to step F3.

[0178] F2. The user terminal displays a login page, and then, in response to the user's login operation, sends the login information of the first application to the first server. The first server determines the first user identifier corresponding to the login information, establishes a target session for communication with the user terminal, generates a key corresponding to the target session, and sends the key to the user terminal.

[0179] Here, when the login status is logged in, the user terminal will carry the key sent by the first server every time it communicates with the first server, so that the first server can determine the first user identifier of the user terminal based on the key.

[0180] F3. The first user terminal sends the key, the target instruction, and the application identifier of the first application to the first server.

[0181] F4. The first server determines whether the application identifier is the central application identifier of the central application.

[0182] If so, proceed to step F10;

[0183] If not, proceed to step F5.

[0184] F5. The first server sends the first user identifier to the account middleware server, and the account middleware server checks whether the first user identifier has a bound user identifier in the binding relationship.

[0185] If so, proceed to step F6;

[0186] If not, proceed to step F7.

[0187] F6. The account middleware server uses the found user identifier as the central user identifier bound to the first user identifier.

[0188] Here, after executing step F6, the process jumps to execute step F10.

[0189] F7. The account middleware server creates a virtual identifier and receives the registration information sent by the user terminal; based on the registration information, it checks whether the account middleware server stores a central user identifier corresponding to the registration information.

[0190] If so, proceed to step F8;

[0191] If not, proceed to step F9.

[0192] F8. The account middleware server will use the found central user identifier as the central user identifier bound to the first user identifier.

[0193] Here, after executing step F8, the process jumps to execute step F10.

[0194] F9. The account middleware server determines the virtual identifier as the central user identifier bound to the first user identifier.

[0195] F10. The account middleware server encrypts the central user identifier and sends the encrypted central user identifier and the target instruction to the business server.

[0196] F11. The account middleware server receives the encrypted central user identifier and response result sent by the business server.

[0197] F12, synchronize the response result and the first user identifier to the first server corresponding to the first application, and synchronize the response result and the second user identifier to the second server corresponding to the second application.

[0198] The data synchronization method provided in this disclosure can, after receiving a target instruction sent by a user terminal from a first application and a first user identifier of the user terminal within the first application, determine a central user identifier bound to the first user identifier, and then determine whether the central user identifier is bound to a second user identifier. If so, after determining the response result corresponding to the target instruction, the response result and the first user identifier are synchronized to a first server corresponding to the first application, and the response result and the second user identifier are synchronized to a second server corresponding to the second application. Using this method, the response result of the target instruction sent by the first application can be synchronized to the servers corresponding to other applications, thereby enabling other applications to obtain the same response result by accessing the corresponding servers, improving the user experience.

[0199] Furthermore, in this embodiment, all application user identifiers are bound to a central user identifier. When any application sends a target instruction, data synchronization can be performed through the response result of the target instruction corresponding to the central user identifier, avoiding conflicts caused by different response results of different applications and improving the data synchronization effect.

[0200] Those skilled in the art will understand that, in the above-described method of the specific implementation, the order in which each step is written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0201] Based on the same inventive concept, this disclosure also provides a data synchronization device corresponding to the data synchronization method. Since the principle of the device in this disclosure for solving the problem is similar to the data synchronization method described above in this disclosure, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0202] Reference Figure 4 The diagram shown is an architectural schematic of a data synchronization device provided in an embodiment of this disclosure. The device includes: a receiving module 401, a first determining module 402, a second determining module 403, and a synchronization module 404; wherein,

[0203] The receiving module 401 is used to receive the target instruction sent by the user terminal in the first application, and the first user identifier of the user terminal in the first application.

[0204] The first determining module 402 is used to determine the central user identifier bound to the first user identifier, wherein the central user identifier is used to form the binding relationship between the user identifiers of each application.

[0205] The second determining module 403 is used to determine whether the central user identifier is bound to a second user identifier, wherein the second user identifier is the user identifier of the user terminal in the second application.

[0206] The synchronization module 404 is configured to, if so, after determining the response result of the target instruction corresponding to the central user identifier, synchronize the response result and the first user identifier to the first server corresponding to the first application, and synchronize the response result and the second user identifier to the second server corresponding to the second application.

[0207] In one possible implementation, the central user identifier is a user identifier registered by the user terminal within the central application; if the user terminal is not registered in the central application, the central user identifier is a generated virtual identifier.

[0208] The synchronization module 404 is also used for:

[0209] The response result and the central user identifier are synchronized to the third server corresponding to the central application.

[0210] In one possible implementation, the account middleware server stores the binding relationships between multiple user identifiers registered by other applications and the central user identifier;

[0211] The first determining module 402, when determining the central user identifier bound to the first user identifier, is used to:

[0212] In the binding relationship, check whether the first user identifier has a bound user identifier;

[0213] If so, the found user identifier will be used as the central user identifier bound to the first user identifier;

[0214] If not, obtain the user's registration information and determine the central user identifier bound to the first user identifier based on the registration information.

[0215] In one possible implementation, after determining the central user identifier bound to the first user identifier based on the registration information, the first determining module 402 is further configured to:

[0216] The binding relationship is updated based on the first user identifier and the central user identifier.

[0217] In one possible implementation, the account middleware server stores user identifiers registered by each user client within each application;

[0218] The first determining module 402, when determining the central user identifier bound to the first user identifier based on the registration information, is used to:

[0219] Create a virtual identifier and receive registration information sent by the user terminal;

[0220] Based on the registration information, check whether the account middleware server stores a central user identifier corresponding to the registration information;

[0221] If so, the found central user identifier will be used as the central user identifier bound to the first user identifier;

[0222] If not, the virtual identifier is determined to be the central user identifier bound to the first user identifier.

[0223] In one possible implementation, the synchronization module 404, when determining the response result of the target instruction corresponding to the central user identifier, is used to:

[0224] The central user identifier is encrypted, and the encrypted central user identifier and the target instruction are sent to the business server.

[0225] Receive the encrypted central user identifier and response result sent by the business server;

[0226] Before synchronizing the response result and the first user identifier to the first server corresponding to the first application, and before synchronizing the response result and the second user identifier to the second server corresponding to the second application, the synchronization module 404 is further configured to:

[0227] The encrypted central user identifier is decrypted to determine the first user identifier and the second user identifier bound to the decrypted central user identifier.

[0228] In one possible implementation, the device is also used for:

[0229] The system receives a modification instruction for the response result sent by the user terminal within any application, as well as a third user identifier of the user terminal within that application; wherein the third user identifier is either the first user identifier or the second user identifier.

[0230] Determine the central user identifier bound to the third user identifier, and determine the change result of the change instruction corresponding to the central user identifier;

[0231] The change result and the third user identifier are synchronized to the server corresponding to the third user identifier, and the change result and other user identifiers other than the third user identifier are synchronized to the servers corresponding to the other user identifiers.

[0232] In one possible implementation, when the central user identifier is the virtual identifier, the device is further configured to:

[0233] Receive the fourth user identifier registered by the user terminal in the central application, sent by the user terminal;

[0234] The virtual identifier in the binding relationship is updated based on the fourth user identifier.

[0235] The processing flow of each module in the device and the interaction flow between each module can be referred to the relevant descriptions in the above method embodiments, and will not be detailed here.

[0236] Based on the same technical concept, this disclosure also provides a computer device. (See also...) Figure 5 The diagram shows the structure of a computer device 500 provided in this embodiment of the present disclosure, including a processor 501, a memory 502, and a bus 503. The memory 502 stores execution instructions and includes main memory 5021 and external memory 5022. The main memory 5021, also called internal memory, is used to temporarily store computational data in the processor 501 and data exchanged with external memory 5022 such as a hard disk. The processor 501 exchanges data with the external memory 5022 through the main memory 5021. When the computer device 500 is running, the processor 501 and the memory 502 communicate through the bus 503, causing the processor 501 to execute the following instructions:

[0237] Receive the target instruction sent by the user terminal in the first application, and the first user identifier of the user terminal in the first application;

[0238] Determine a central user identifier bound to the first user identifier, wherein the central user identifier is used to form the binding relationship between user identifiers of each application;

[0239] Determine whether the central user identifier is bound to a second user identifier, wherein the second user identifier is the user identifier of the user terminal in the second application;

[0240] If so, after determining the response result of the target instruction corresponding to the central user identifier, the response result and the first user identifier are synchronized to the first server corresponding to the first application, and the response result and the second user identifier are synchronized to the second server corresponding to the second application.

[0241] In one possible implementation, in the instructions executed by the processor 501, the central user identifier is a user identifier registered by the user terminal in the central application; if the user terminal is not registered in the central application, the central user identifier is a generated virtual identifier.

[0242] The method further includes:

[0243] The response result and the central user identifier are synchronized to the third server corresponding to the central application.

[0244] In one possible implementation, the instructions executed by the processor 501 include an account middleware server storing binding relationships between multiple user identifiers registered by other applications and a central user identifier.

[0245] The determination of the central user identifier bound to the first user identifier includes:

[0246] In the binding relationship, check whether the first user identifier has a bound user identifier;

[0247] If so, the found user identifier will be used as the central user identifier bound to the first user identifier;

[0248] If not, obtain the user's registration information and determine the central user identifier bound to the first user identifier based on the registration information.

[0249] In one possible implementation, after determining the central user identifier bound to the first user identifier based on the registration information, the method further includes the following instructions executed by processor 501:

[0250] The binding relationship is updated based on the first user identifier and the central user identifier.

[0251] In one possible implementation, the instructions executed by the processor 501 include the account middleware server storing user identifiers registered by each user terminal within each application.

[0252] The step of determining the central user identifier bound to the first user identifier based on the registration information includes:

[0253] Create a virtual identifier and receive registration information sent by the user terminal;

[0254] Based on the registration information, check whether the account middleware server stores a central user identifier corresponding to the registration information;

[0255] If so, the found central user identifier will be used as the central user identifier bound to the first user identifier;

[0256] If not, the virtual identifier is determined to be the central user identifier bound to the first user identifier.

[0257] In one possible implementation, the instruction executed by processor 501, the response result for determining the target instruction corresponding to the central user identifier, includes:

[0258] The central user identifier is encrypted, and the encrypted central user identifier and the target instruction are sent to the business server.

[0259] Receive the encrypted central user identifier and response result sent by the business server;

[0260] Before synchronizing the response result and the first user identifier to the first server corresponding to the first application, and before synchronizing the response result and the second user identifier to the second server corresponding to the second application, the method further includes:

[0261] The encrypted central user identifier is decrypted to determine the first user identifier and the second user identifier bound to the decrypted central user identifier.

[0262] In one possible implementation, the method further includes the following instructions executed by processor 501:

[0263] The system receives a modification instruction for the response result sent by the user terminal within any application, as well as a third user identifier of the user terminal within that application; wherein the third user identifier is either the first user identifier or the second user identifier.

[0264] Determine the central user identifier bound to the third user identifier, and determine the change result of the change instruction corresponding to the central user identifier;

[0265] The change result and the third user identifier are synchronized to the server corresponding to the third user identifier, and the change result and other user identifiers other than the third user identifier are synchronized to the servers corresponding to the other user identifiers.

[0266] In one possible implementation, the method further includes, in the case that the central user identifier is the virtual identifier, the instructions executed by the processor 501:

[0267] Receive the fourth user identifier registered by the user terminal in the central application, sent by the user terminal;

[0268] The virtual identifier in the binding relationship is updated based on the fourth user identifier.

[0269] This disclosure also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the data synchronization method described in the above-described method embodiments. The storage medium may be a volatile or non-volatile computer-readable storage medium.

[0270] This disclosure also provides a computer program product carrying program code. The program code includes instructions that can be used to execute the steps of the data synchronization method described in the above method embodiments. For details, please refer to the above method embodiments, which will not be repeated here.

[0271] The aforementioned computer program product can be implemented through hardware, software, or a combination thereof. In one optional embodiment, the computer program product is specifically embodied in a computer storage medium; in another optional embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0272] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. In the several embodiments provided in this disclosure, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection may be through some communication interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms.

[0273] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0274] In addition, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0275] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0276] Finally, it should be noted that the above-described embodiments are merely specific implementations of this disclosure, used to illustrate the technical solutions of this disclosure, and not to limit it. The protection scope of this disclosure is not limited thereto. Although this disclosure has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this disclosure. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this disclosure, and should all be covered within the protection scope of this disclosure. Therefore, the protection scope of this disclosure should be determined by the protection scope of the claims.

Claims

1. A data synchronization method, characterized in that, Applications to account middleware servers include: Receive the target instruction sent by the user terminal in the first application, and the first user identifier of the user terminal in the first application; Determine a central user identifier bound to the first user identifier, wherein the central user identifier is used to form the binding relationship between user identifiers of each application; Determine whether the central user identifier is bound to a second user identifier, wherein the second user identifier is the user identifier of the user terminal in the second application; If so, after determining the response result of the target instruction corresponding to the central user identifier, the response result and the first user identifier are synchronized to the first server corresponding to the first application, and the response result and the second user identifier are synchronized to the second server corresponding to the second application; The data synchronization method further includes: If the first user identifier is not bound to a central user identifier, a virtual identifier is created as the central user identifier, and based on the received user registration information, it is determined whether the virtual identifier should be identified as the actual central user identifier corresponding to the registration information.

2. The method according to claim 1, characterized in that, The central user identifier is the user identifier registered by the user terminal within the central application. If the user terminal has not registered in the central application, the central user identifier is a generated virtual identifier. The method further includes: The response result and the central user identifier are synchronized to the third server corresponding to the central application.

3. The method according to claim 1, characterized in that, The account middleware server stores the binding relationships between multiple user identifiers registered by other applications and the central user identifier; The determination of the central user identifier bound to the first user identifier includes: In the binding relationship, check whether the first user identifier has a bound user identifier; If so, the found user identifier will be used as the central user identifier bound to the first user identifier; If not, then obtain the user's registration information and determine the central user identifier bound to the first user identifier based on the registration information.

4. The method according to claim 3, characterized in that, After determining the central user identifier bound to the first user identifier based on the registration information, the method further includes: The binding relationship is updated based on the first user identifier and the central user identifier.

5. The method according to claim 3, characterized in that, The account middleware server stores the user identifiers registered by each user client within each application; The step of determining the central user identifier bound to the first user identifier based on the registration information includes: Create a virtual identifier and receive registration information sent by the user terminal; Based on the registration information, check whether the account middleware server stores a central user identifier corresponding to the registration information; If so, the found central user identifier will be used as the central user identifier bound to the first user identifier; If not, the virtual identifier is determined to be the central user identifier bound to the first user identifier.

6. The method according to claim 1, characterized in that, The response result for determining the target instruction corresponding to the central user identifier includes: The central user identifier is encrypted, and the encrypted central user identifier and the target instruction are sent to the business server. Receive the encrypted central user identifier and response result sent by the business server; Before synchronizing the response result and the first user identifier to the first server corresponding to the first application, and before synchronizing the response result and the second user identifier to the second server corresponding to the second application, the method further includes: The encrypted central user identifier is decrypted to determine the first user identifier and the second user identifier bound to the decrypted central user identifier.

7. The method according to claim 1, characterized in that, The method further includes: The system receives a modification instruction for the response result sent by the user terminal within any application, as well as a third user identifier of the user terminal within that application; wherein the third user identifier is either the first user identifier or the second user identifier. Determine the central user identifier bound to the third user identifier, and determine the change result of the change instruction corresponding to the central user identifier; The change result and the third user identifier are synchronized to the server corresponding to the third user identifier, and the change result and other user identifiers other than the third user identifier are synchronized to the servers corresponding to the other user identifiers.

8. The method according to claim 2, characterized in that, When the central user identifier is the virtual identifier, the method further includes: Receive the fourth user identifier registered by the user terminal in the central application, sent by the user terminal; The virtual identifier in the binding relationship is updated based on the fourth user identifier.

9. A data synchronization device, characterized in that, include: The receiving module is configured to receive a target instruction sent by a user terminal in a first application, and a first user identifier of the user terminal within the first application. The first determining module is configured to determine a central user identifier bound to the first user identifier, wherein the central user identifier is used to form a binding relationship between user identifiers of various applications; The second determining module is configured to determine whether the central user identifier is bound to a second user identifier, wherein the second user identifier is the user identifier of the user terminal within the second application; and The synchronization module is configured to, if the central user identifier is bound to a second user identifier, after determining the response result of the target instruction corresponding to the central user identifier, synchronize the response result and the first user identifier to the first server corresponding to the first application, and synchronize the response result and the second user identifier to the second server corresponding to the second application. The first determining module is further configured to, if the first user identifier is not bound to a central user identifier, create a virtual identifier as the central user identifier, and determine, based on the received user registration information, whether to determine the virtual identifier as the actual central user identifier corresponding to the registration information.

10. A computer device, characterized in that, include: The computer device includes a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor, and the processor communicates with the memory via the bus when the computer device is running, and the machine-readable instructions, when executed by the processor, perform the steps of the data synchronization method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the data synchronization method as described in any one of claims 1 to 8.

Images