Data synchronization method, user identity cloud authentication platform, electronic equipment and storage medium

Abstract

The invention provides a data synchronization method, a user identity cloud authentication platform, electronic equipment and a storage medium. When a data synchronization operation initiated by a user based on a terminal is detected, and the data synchronization operation is a real-time data synchronization operation; storing a synchronization information recording entity corresponding to the generated real-time data synchronization operation into a synchronization information data pool; synchronizing the synchronization information to at least one sub-platform indicated by the real-time data synchronization operation, so that the sub-platform completes corresponding data synchronization by using the received synchronization information; in the data synchronization process, when it is detected that the sub-platforms are abnormal, data synchronization on the sub-platforms is interrupted; when it is detected that the sub-platforms return to normal, residual synchronization information is obtained from synchronization information in synchronization information recording entities stored in a synchronization information data pool according to synchronization versions, synchronization record IDs and synchronization processes in data distribution logs corresponding to the sub-platforms, and real-time data synchronization operation is recovered. And synchronizing the residual synchronization information to the sub-platform.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and more specifically, to a data synchronization method, a user identity cloud authentication platform, an electronic device, and a storage medium. Background Art

[0002] In the digital age, enterprises and organizations often rely on multiple platforms to handle different business needs. However, the data isolation between these platforms leads to data silos, which results in information independence for users between platforms.

[0003] In the prior art, a corresponding single sign-on platform is established to synchronize the corresponding data to each sub-platform through the single sign-on platform, so as to achieve data synchronization between the sub-platforms and solve the problem of data islands caused by data isolation between platforms, which leads to information independence of users between platforms due to data islands. However, due to the diversity of sub-platform architectures, the upper-level platform (single sign-on platform) needs to understand the access methods of sub-platforms of different architectures and access the corresponding sub-platform according to the corresponding sub-platform access method, which not only has poor scalability but also is difficult to maintain.

[0004] Moreover, as an independent system service, if an exception occurs in the sub-platform during the data synchronization process, data synchronization will fail. When the sub-platform is detected to be back to normal, the data synchronization process can only be re-executed, that is, all data must be re-synchronized. This will not only increase network usage and system load, but also lead to inconsistency in the data versions synchronized before and after. Summary of the invention

[0005] In view of this, the present application provides a data synchronization method, a user identity cloud authentication platform, an electronic device and a storage medium, with the purpose of improving scalability, reducing maintenance difficulty, reducing network occupancy and reducing system load.

[0006] The first aspect of the present application provides a data synchronization method, which is applied to a user identity cloud authentication platform, and the method comprises:

[0007] When a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, a synchronization information record entity corresponding to the real-time data synchronization operation is generated, and the synchronization information record entity is stored in a synchronization information data pool; wherein the synchronization information record entity includes synchronization information, a synchronization version corresponding to the synchronization information, and a synchronization record ID;

[0008] Synchronize the synchronization information to at least one sub-platform indicated by the real-time data synchronization operation, so that when the sub-platform completely receives the corresponding synchronization information, it uses the received synchronization information to complete the corresponding data synchronization;

[0009] During the data synchronization process, when an abnormality is detected on the sub-platform, a data distribution scheduling is initiated to the sub-platform to interrupt the data synchronization of the sub-platform;

[0010] When it is detected that the sub-platform has returned to normal, the remaining synchronization information is obtained from the synchronization information in each synchronization information recording entity stored in the synchronization information data pool according to the synchronization version, synchronization record ID and synchronization process in the data distribution log corresponding to the sub-platform, and the real-time data synchronization operation is restored to synchronize the remaining synchronization information to the sub-platform; wherein, the data distribution log corresponding to the sub-platform is recorded in real time when the corresponding synchronization information is synchronized to the sub-platform, and the synchronization version and synchronization record ID in the data distribution record are the synchronization version and synchronization record ID of the synchronization information synchronized to the sub-platform before the abnormality of the sub-platform occurs.

[0011] Optionally, when a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, generating a synchronization information record entity corresponding to the data synchronization operation, and storing the synchronization information record entity in a synchronization information data pool, includes:

[0012] When a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, determining that the real-time data synchronization operation indicates synchronized user data, at least one sub-platform ID, and a timestamp;

[0013] Calling a preset data compression program to generate corresponding synchronization information, synchronization version and synchronization record ID according to user data, at least one sub-platform ID and a timestamp, and generating a synchronization information record entity corresponding to the real-time data synchronization operation according to the synchronization information, the synchronization version and the synchronization record ID according to a preset data structure;

[0014] The synchronization information recording entity corresponding to the real-time data synchronization operation is stored in a synchronization information data pool.

[0015] Optionally, synchronizing the synchronization information in the synchronization information recording entity to at least one sub-platform indicated by the real-time data synchronization operation so that the sub-platform completes corresponding data synchronization using the received synchronization information when the synchronization information is completely received, includes:

[0016] For each of the sub-platform IDs, the data distribution scheduling program is called based on the message publishing and subscription mechanism to synchronize the synchronization information in the synchronization information recording entity to the sub-platform corresponding to the sub-platform ID, so that the sub-platform calls the data decompression program to decompress the synchronization information when receiving the synchronization information, obtains the user data, and uses the user data to complete the corresponding data synchronization; wherein, the data decompression program is a decompression program that is associated with the data compression program.

[0017] Optionally, the method further includes:

[0018] When a data synchronization operation initiated by a user based on a terminal is detected, and the data synchronization operation is a rollback data synchronization operation, the synchronization record ID and synchronization information corresponding to the synchronization version indicated by the rollback data synchronization operation are obtained from each synchronization information record entity stored in the synchronization information data pool;

[0019] The synchronization record ID and synchronization information corresponding to the synchronization version indicated by the rollback data synchronization operation are synchronized to at least one sub-platform indicated by the rollback data synchronization operation, so that when the sub-platform completely receives the corresponding synchronization information, it uses the received synchronization information to complete the corresponding data synchronization.

[0020] Optionally, the method further includes:

[0021] After completing the real-time data synchronization operation or the rollback data synchronization operation, detecting in real time whether there is a sub-platform login operation initiated by the user based on the terminal;

[0022] If a sub-platform login operation initiated by the user based on the terminal is detected, determining the architecture type of the sub-platform that the sub-platform login operation indicates to log in;

[0023] According to the login rule corresponding to the architecture type of the sub-platform, the sub-platform login operation indicates the sub-platform to be logged in.

[0024] A second aspect of the present application provides a user identity cloud authentication platform, the user identity cloud authentication platform at least comprising a synchronization information data pool and a multi-platform data distribution and control module;

[0025] A synchronization information data pool, for generating a synchronization information record entity corresponding to the real-time data synchronization operation when a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, and storing the synchronization information record entity in the synchronization information data pool; wherein the synchronization information record entity includes synchronization information, a synchronization version corresponding to the synchronization information, and a synchronization record ID;

[0026] A multi-platform data distribution and control module is used to synchronize the synchronization information to at least one sub-platform indicated by the real-time data synchronization operation, so that when the sub-platform completely receives the corresponding synchronization information, it uses the received synchronization information to complete the corresponding data synchronization; during the data synchronization process, when an abnormality is detected in the sub-platform, a data distribution schedule is initiated to the sub-platform to interrupt the data synchronization of the sub-platform; when it is detected that the sub-platform has returned to normal, the remaining synchronization information is obtained from the synchronization information in each synchronization information record entity stored in the synchronization information data pool according to the synchronization version, synchronization record ID and synchronization process in the data distribution log corresponding to the sub-platform, and the real-time data synchronization operation is restored to synchronize the remaining synchronization information to the sub-platform; wherein, the data distribution log corresponding to the sub-platform is a real-time record when the corresponding synchronization information is synchronized to the sub-platform, and the synchronization version and synchronization record ID in the data distribution record are the synchronization version and synchronization record ID of the synchronization information synchronized to the sub-platform before the abnormality occurs on the sub-platform.

[0027] Optionally, when a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, a synchronization information record entity corresponding to the data synchronization operation is generated, and the synchronization information record entity is stored in a synchronization information data pool of a synchronization information data pool, specifically used for:

[0028] When a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, determine the user data, at least one sub-platform ID and a timestamp that the real-time data synchronization operation indicates to be synchronized; call a pre-set data compression program to generate corresponding synchronization information, synchronization version and synchronization record ID according to the user data, at least one sub-platform ID and a timestamp, and generate a synchronization information record entity corresponding to the real-time data synchronization operation according to the synchronization information, the synchronization version and the synchronization record ID according to a pre-set data structure; and store the synchronization information record entity corresponding to the real-time data synchronization operation in a synchronization information data pool.

[0029] Optionally, the synchronization information in the synchronization information recording entity is synchronized to at least one sub-platform indicated by the real-time data synchronization operation, so that when the sub-platform receives the synchronization information completely, the multi-platform data distribution and control module uses the received synchronization information to complete the corresponding data synchronization, which is specifically used for:

[0030] For each of the sub-platform IDs, the data distribution scheduling program is called based on the message publishing and subscription mechanism to synchronize the synchronization information in the synchronization information recording entity to the sub-platform corresponding to the sub-platform ID, so that the sub-platform calls the data decompression program to decompress the synchronization information when receiving the synchronization information, obtains the user data, and uses the user data to complete the corresponding data synchronization; wherein, the data decompression program is a decompression program that is associated with the data compression program.

[0031] The third aspect of the present application provides an electronic device, comprising: a processor and a memory, wherein the processor and the memory are connected via a communication bus; wherein the processor is used to call and execute a program stored in the memory; and the memory is used to store a program, wherein the program is used to implement the data synchronization method provided in the first aspect of the present application.

[0032] A fourth aspect of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and the computer-executable instructions are used to execute the data synchronization method provided in the first aspect of the present application.

[0033] The present application provides a data synchronization method, a user identity cloud authentication platform, an electronic device and a storage medium, which are applied to the user identity cloud authentication platform. When a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, a synchronization information recording entity corresponding to the real-time data synchronization operation is generated, and the synchronization information recording entity is stored in a synchronization information data pool; wherein the synchronization information recording entity includes synchronization information, a synchronization version corresponding to the synchronization information and a synchronization record ID; the synchronization information is synchronized to at least one sub-platform indicated by the real-time data synchronization operation, so that when the sub-platform receives the corresponding synchronization information completely, it uses the received synchronization information to complete the corresponding data synchronization; during the data synchronization process, when the corresponding synchronization information is detected When an exception occurs in the sub-platform, a data distribution schedule is initiated to the sub-platform to interrupt data synchronization of the sub-platform; when it is detected that the sub-platform has returned to normal, the remaining synchronization information is obtained from the synchronization information in each synchronization information recording entity stored in the synchronization information data pool according to the synchronization version, synchronization record ID and synchronization process in the data distribution log corresponding to the sub-platform, and the real-time data synchronization operation is restored to synchronize the remaining synchronization information to the sub-platform; wherein, the data distribution log corresponding to the sub-platform is recorded in real time when the corresponding synchronization information is synchronized to the sub-platform, and the synchronization version and synchronization record ID in the data distribution record are the synchronization version and synchronization record ID of the synchronization information synchronized to the sub-platform before the exception occurs to the sub-platform. The technical solution provided by the present application can generate a corresponding synchronization information recording entity when it is determined that the data synchronization operation initiated by the user is a real-time data synchronization operation, so that when the data is synchronized, the synchronization information in the synchronization information recording entity can be synchronized to the corresponding sub-platform, which can effectively reduce the amount of data in the data synchronization process, thereby reducing a certain amount of network occupancy and system load; and when the synchronization information is synchronized to the sub-platform, the corresponding synchronization process and the synchronization record ID and synchronization version of the synchronization information synchronized to the sub-platform can also be recorded in real time, and a corresponding data distribution log is generated, so that during the data synchronization process, once an abnormality occurs on the sub-platform, the data synchronization of the sub-platform is interrupted, and when it is detected that the sub-platform has returned to normal, the remaining synchronization information is obtained from the synchronization information in each synchronization information recording entity stored in the synchronization information data pool according to the synchronization version, synchronization record ID and synchronization process in the data distribution log corresponding to the sub-platform, and the real-time data synchronization operation is restored to synchronize the remaining synchronization information to the sub-platform, without re-sending the entire synchronization data to the sub-platform, which can not only ensure the consistency of data synchronization before and after the abnormality occurs on the sub-platform, but also reduce network resource consumption, system load and human data comparison costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0035] Figure 1 An architectural diagram of a user identity cloud authentication platform provided in an embodiment of the present application;

[0036] Figure 2 A flowchart of a data synchronization method provided in an embodiment of the present application;

[0037] Figure 3 An example diagram of a synchronization information recording entity corresponding to a real-time data synchronization operation generated and stored in an embodiment of the present application;

[0038] Figure 4 An example diagram of a data distribution log for recording a real-time data synchronization operation or a rollback data synchronization operation provided in an embodiment of the present application;

[0039] Figure 5 An example diagram of a user identity cloud authentication platform logging into a sub-platform provided in an embodiment of the present application;

[0040] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0041] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0042] In this application, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0043] It should be noted that in the technical solution disclosed in this application, the acquisition, collection, storage, use, processing, transmission, provision, disclosure and application of user data all comply with the provisions of relevant laws and regulations, take necessary confidentiality measures, and do not violate public order and good morals.

[0044] In order to better understand this application, the technical names involved in this application are explained below:

[0045] Data pool: refers to a platform or storage system that centrally stores and manages various structured and unstructured data, and has the function of data version management.

[0046] Data silos: Data silos refer to the situation in which different information systems in an organization or enterprise are isolated from each other and do not share or exchange data, resulting in inefficient data utilization and inconsistent information.

[0047] Single Sign-On (SSO) is an authentication technology that allows users to log in to multiple related but independent software systems or applications with one set of credentials (such as username and password). Users only need to log in once to access all connected systems without having to log in separately in each system, thereby improving user experience and operational efficiency.

[0048] See also Figure 1 , showing an architecture diagram of a user identity cloud authentication platform provided in an embodiment of the present application, the user identity cloud authentication platform includes a unified user data management module, a sub-platform management module, a synchronization information data pool, a multi-platform data distribution and control module and a multi-architecture platform same authentication module.

[0049] In the embodiment of the present application, the unified user data management module is mainly used to store the user data of multiple users, and also has the functions of adding, modifying, deleting, synchronizing with a designated platform, and viewing synchronization records of user data. The unified user data management module includes the basic data for sub-platform authentication implementation, and is responsible for storing the user data corresponding to each user and the designated synchronized sub-platform ID, so that when the user identity authentication cloud platform detects the corresponding data synchronization operation, it can obtain the data corresponding to the data synchronization operation from the unified user data management, and generate the corresponding synchronization information record entity based on the acquired data, and at the same time trigger the synchronization information data pool, so that the synchronization information data pool generates and stores the synchronization information record entity of the corresponding data synchronization operation.

[0050] The synchronization information data pool is used to store the synchronization information record entity, synchronization version, synchronization record ID, etc. of the corresponding data synchronization operation.

[0051] Specifically, the synchronization information data pool is used to generate a synchronization information record entity corresponding to the real-time data synchronization operation when it detects a data synchronization operation initiated by the user based on the terminal and the data synchronization operation is a real-time data synchronization operation, and store the synchronization information record entity in the synchronization information data pool; wherein the synchronization information record entity includes synchronization information, the synchronization version corresponding to the synchronization information, and the synchronization record ID.

[0052] Optionally, when a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, a synchronization information record entity corresponding to the data synchronization operation is generated, and the synchronization information record entity is stored in a synchronization information data pool of a synchronization information data pool, specifically used for:

[0053] When a data synchronization operation initiated by the user based on the terminal is detected and the data synchronization operation is a real-time data synchronization operation, the user data, at least one sub-platform ID and a timestamp indicated for synchronization by the real-time data synchronization operation are determined; a pre-set data compression program is called to generate corresponding synchronization information, synchronization version and synchronization record ID according to the user data, at least one sub-platform ID and a timestamp, and a synchronization information record entity corresponding to the real-time data synchronization operation is generated according to the synchronization information, synchronization version and synchronization record ID according to a pre-set data structure; the synchronization information record entity corresponding to the real-time data synchronization operation is stored in a synchronization information data pool.

[0054] The sub-platform management module is used to store the sub-platform name, sub-platform chart, sub-platform ID and sub-platform architecture type of each sub-platform; wherein the sub-platform architecture type may include a Web-side architecture type, a mobile-side architecture type, a PC client architecture type, etc., which is not limited in the embodiments of the present application.

[0055] The multi-platform data distribution and control module is used to store a pre-set data distribution scheduler, which is used to distribute the synchronization information in the synchronization information recording entity to the corresponding sub-platform to complete the corresponding data synchronization. At the same time, it can also generate and record the data distribution log generated when each data distribution scheduler performs data distribution. Among them, the multi-platform data distribution and control module relies on the synchronization information recording entity generated in the synchronization information data pool to complete data synchronization, and can synchronize data to multiple sub-platforms in an incremental form, reducing the network resource consumption and sub-platform system load caused by the full synchronization of data, and can also reduce the cost of human data comparison.

[0056] Specifically, the multi-platform data distribution and control module is used to synchronize synchronization information to at least one sub-platform indicated by the real-time data synchronization operation, so that when the sub-platform completely receives the corresponding synchronization information, it uses the received synchronization information to complete the corresponding data synchronization; during the data synchronization process, when an abnormality is detected in the sub-platform, a data distribution schedule is initiated to the sub-platform to interrupt the data synchronization of the sub-platform; when it is detected that the sub-platform has returned to normal, the remaining synchronization information is obtained from the synchronization information in each synchronization information record entity stored in the synchronization information data pool according to the synchronization version, synchronization record ID and synchronization process in the data distribution log corresponding to the sub-platform, and the real-time data synchronization operation is restored to synchronize the remaining synchronization information to the sub-platform; wherein, the data distribution log corresponding to the sub-platform is a real-time record when the corresponding synchronization information is synchronized to the sub-platform, and the synchronization version and synchronization record ID in the data distribution record are the synchronization version and synchronization record ID of the synchronization information synchronized to the sub-platform before the abnormality occurs in the sub-platform.

[0057] Optionally, the synchronization information in the synchronization information recording entity is synchronized to at least one sub-platform indicated by the real-time data synchronization operation, so that when the sub-platform receives the synchronization information completely, the multi-platform data distribution and control module completes the corresponding data synchronization using the received synchronization information, which is specifically used for:

[0058] For each sub-platform ID, the data distribution scheduling program is called based on the message publishing and subscription mechanism to synchronize the synchronization information in the synchronization information recording entity to the sub-platform corresponding to the sub-platform ID, so that the sub-platform calls the data decompression program to decompress the synchronization information when receiving the synchronization information, obtains the user data, and uses the user data to complete the corresponding data synchronization; among which, the data decompression program is a decompression program that is associated with the data compression program.

[0059] Optionally, the multi-platform data distribution and control module is also used to:

[0060] When a data synchronization operation initiated by the user based on the terminal is detected, and the data synchronization operation is a rollback data synchronization operation, the synchronization record ID and synchronization information corresponding to the synchronization version indicated by the rollback data synchronization operation are obtained from each synchronization information record entity stored in the synchronization information data pool; the synchronization record ID and synchronization information corresponding to the synchronization version indicated by the rollback data synchronization operation are synchronized to at least one sub-platform indicated by the rollback data synchronization operation, so that when the sub-platform completely receives the corresponding synchronization information, it uses the received synchronization information to complete the corresponding data synchronization.

[0061] The same authentication module for multiple architecture platforms is used to log in to the corresponding sub-platforms according to the login rules corresponding to different architecture types, so as to solve the problem that the traditional single sign-on platform cannot dynamically adapt to the access of multiple architecture platforms. After the user logs in to the user identity cloud authentication platform, he can initiate the corresponding sub-platform login operation through the terminal, log in to the corresponding sub-platform, and then access the corresponding sub-platform without repeatedly entering the corresponding authentication information. This not only simplifies the login operation, but also improves the user experience, enhances the system's ease of use and user satisfaction.

[0062] Optionally, the same authentication module for multiple architecture platforms is specifically used for:

[0063] After completing the real-time data synchronization operation or the rollback data synchronization operation, detect in real time whether there is a sub-platform login operation initiated by the user based on the terminal; if a sub-platform login operation initiated by the user based on the terminal is detected, determine the architecture type of the sub-platform that the sub-platform login operation indicates to be logged in; according to the login rules corresponding to the sub-platform architecture type, log in to the sub-platform that the sub-platform login operation indicates to be logged in.

[0064] The present application provides a user identity cloud authentication platform, which can generate a corresponding synchronization information recording entity when determining that the data synchronization operation initiated by the user is a real-time data synchronization operation, so that when the data is synchronized, the synchronization information in the synchronization information recording entity can be synchronized to the corresponding sub-platform, which can effectively reduce the amount of data in the data synchronization process, thereby reducing a certain amount of network occupancy and system load; and when the synchronization information is synchronized to the sub-platform, the corresponding synchronization process and the synchronization record ID and synchronization version of the synchronization information synchronized to the sub-platform can also be recorded in real time, and a corresponding data distribution log is generated, so that during the data synchronization process, once an abnormality occurs on the sub-platform, the data synchronization of the sub-platform is interrupted, and when it is detected that the sub-platform has returned to normal, the remaining synchronization information is obtained from the synchronization information in each synchronization information recording entity stored in the synchronization information data pool according to the synchronization version, synchronization record ID and synchronization process in the data distribution log corresponding to the sub-platform, and the real-time data synchronization operation is restored to synchronize the remaining synchronization information to the sub-platform, without re-sending the entire synchronization data to the sub-platform, so that not only can the consistency of data synchronization before and after the abnormality of the sub-platform be ensured, but also the network resource consumption, system load and human data comparison cost can be reduced.

[0065] See also Figure 2 , shows a flow chart of a data synchronization method provided in an embodiment of the present application, the data synchronization method is applied to a user identity cloud authentication platform, and the data synchronization method specifically includes the following steps:

[0066] S201: When a data synchronization operation initiated by a user based on a terminal is detected, it is determined whether the data synchronization operation is a real-time data synchronization operation or a rollback data synchronization operation. If the data synchronization operation is a real-time data synchronization operation, step S202 is executed; if the data synchronization operation is a rollback data synchronization operation, step S204 is executed.

[0067] In the specific process of executing step S201, when the user wants to initiate data synchronization, he can first log in to the user identity cloud authentication platform, so that when the user has logged in to the user identity cloud authentication platform, the user identity cloud authentication platform can detect in real time whether there is a data synchronization operation initiated by the user based on the terminal, and when it is detected that the user initiates a corresponding data synchronization operation to the user identity cloud authentication platform based on the corresponding terminal, it is determined whether the data synchronization operation is a real-time data synchronization operation or a rollback data synchronization operation. If the data synchronization operation is a real-time data synchronization operation, execute step S202; if the data synchronization operation is a rollback data synchronization operation, execute step S204.

[0068] S202: Generate a synchronization information record entity corresponding to the real-time data synchronization operation, and store the synchronization information record entity in a synchronization information data pool; wherein the synchronization information record entity includes synchronization information, a synchronization version corresponding to the synchronization information, and a synchronization record ID.

[0069] In the process of specifically executing step S202, when it is determined that the data synchronization operation initiated by the user based on the terminal is a real-time data synchronization operation, it means that the synchronization information data pool has not currently stored the synchronization information record entity corresponding to the real-time data synchronization operation, and then the synchronization information data pool can first determine the user data, at least one sub-platform ID and timestamp that need to be synchronized indicated by the real-time data synchronization operation, so as to generate the synchronization information record entity corresponding to the real-time data synchronization operation according to the user data, at least one sub-platform ID and timestamp indicated by the real-time data synchronization operation, and store the synchronization information record entity in the synchronization information data pool.

[0070] Optionally, when a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, the process of generating a synchronization information recording entity corresponding to the real-time data synchronization operation can be specifically as follows: when a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, determining the user data, at least one sub-platform ID and a timestamp that the real-time data synchronization operation indicates to be synchronized; calling a pre-set data compression program to generate corresponding synchronization information, synchronization version and synchronization record ID according to the user data, at least one sub-platform ID and a timestamp, and generating a synchronization information recording entity corresponding to the real-time data synchronization operation according to the synchronization information, synchronization version and synchronization record ID according to a pre-set data structure, and storing the synchronization information recording entity corresponding to the real-time data synchronization operation in a synchronization information data pool.

[0071] In some embodiments, the pre-set data structure may be synchronization information+synchronization version+synchronization record ID, and there is a corresponding association relationship among the synchronization information, the synchronization version and the synchronization record ID.

[0072] It should be noted that the corresponding real-time data synchronization operation initiated by the user based on the terminal may carry the user name / user ID corresponding to the user data to be synchronized, at least one sub-platform name, etc., which is not limited in this embodiment of the present application.

[0073] In the actual application process, after determining that the data synchronization operation initiated by the user is a real-time data synchronization operation, the timestamp when the real-time data synchronization operation is detected can be first obtained through the synchronization information data pool, and the corresponding user data can be obtained from the unified user data management module according to the user name / user ID carried in the real-time data synchronization operation, and the sub-platform ID corresponding to each sub-platform can be obtained from the sub-platform module according to the names of each sub-platform carried by the real-time data synchronization operation; call a preset data compression algorithm to generate synchronization information according to user data, at least one sub-platform ID and a timestamp, and can also generate a synchronization version and a synchronization record ID corresponding to the synchronization information, and generate a synchronization information record entity corresponding to the real-time data synchronization operation according to the synchronization information, the synchronization version and the synchronization record ID according to the preset data structure, and finally store the synchronization information record entity corresponding to the real-time data synchronization operation in the synchronization information pool, such as Figure 3 The synchronization information record entity includes synchronization information, synchronization record ID and synchronization version, and there is a corresponding association relationship between the synchronization information, synchronization version and synchronization record ID.

[0074] It should be noted that the data compression algorithm is a technology for reducing the size of data. The algorithm reduces the size of data by eliminating redundant information in the data or using the pattern of the data. That is, the data compression algorithm can be used to compress user data, at least one sub-platform ID and timestamp into corresponding synchronization information, so that a certain amount of network occupancy and system load can be reduced during the data synchronization process. Among them, data compression algorithms can be divided into two categories: lossless compression and lossy compression. Lossless compression algorithms can completely restore the original data after compression and decompression, and are suitable for applications that need to retain all original information, such as documents, spreadsheets, and source code. Lossy compression algorithms lose some information in the original data during the compression process to achieve a higher compression rate, and are suitable for applications such as images, videos, and audio that do not need to retain all original information.

[0075] It should also be noted that when the synchronization information of the real-time data synchronization operation is generated, the synchronization version and synchronization record ID corresponding to the synchronization information are generated at the same time. In the subsequent data synchronization process, once the sub-platform has an exception and recovers, the corresponding synchronization version and synchronization record ID can be used to accurately locate the synchronization information of the same version, thereby avoiding the problem of inconsistent data versions synchronized before and after the sub-platform has an exception and recovers.

[0076] In an embodiment of the present application, after the synchronization information data pool generates the synchronization information record entity corresponding to the real-time data synchronization operation, it can further store the synchronization record entity corresponding to the real-time data synchronization operation to achieve decoupling between the user identity cloud authentication platform and the sub-platform. Specifically, the synchronization record entity corresponding to the real-time data synchronization operation is first stored as an intermediate cache layer to avoid poor traceability caused by frequent updates of the user identity cloud authentication platform, and also lay the basis for fine-grained control of sub-platform data; since the synchronization information data pool records the corresponding synchronization information and its synchronization version and synchronization record ID in detail, the subsequent comparison of the sub-platform synchronization record can achieve data synchronization or precise rollback of the sub-platform in the form of incremental data.

[0077] S203: Synchronize the synchronization information to at least one sub-platform indicated by the real-time data synchronization operation, so that when the sub-platform completely receives the corresponding synchronization information, it uses the received synchronization information to complete the corresponding data synchronization.

[0078] In the process of specifically executing step S203, a data decompression program associated with the data compression program can be pre-set; after the user identity cloud authentication platform generates a synchronization information recording entity corresponding to the real-time data synchronization operation through the synchronization information data pool, the corresponding synchronization information can be synchronized to the sub-platform corresponding to each sub-platform ID indicated by the real-time data synchronization operation through the multi-platform data distribution and control module, so that when each sub-platform receives the complete synchronization information, it can call the data decompression program associated with the data compression program to decompress the received synchronization information recording entity, obtain the corresponding synchronization information, and use the obtained synchronization information to complete the corresponding data synchronization.

[0079] In an embodiment of the present application, a plurality of data distribution scheduling programs are pre-set, and the corresponding synchronization information recording entities can be synchronized to the corresponding sub-platforms at the same time through the pre-set data distribution scheduling programs, thereby improving data synchronization efficiency.

[0080] Optionally, the synchronization information is synchronized to at least one sub-platform indicated by the real-time data synchronization operation, so that when the sub-platform receives the complete synchronization information, it uses the synchronization information to complete the corresponding data synchronization. The specific process can be: for each sub-platform ID, based on the message publishing and subscription mechanism, the data distribution scheduling program is called to synchronize the synchronization information in the synchronization information recording entity to the sub-platform corresponding to each sub-platform ID, so that when each sub-platform receives the complete synchronization information, it calls the data decompression program to decompress the received synchronization information to obtain user data, and use the user data to complete the corresponding data synchronization; wherein, the data decompression program is a decompression program that is associated with the data compression program.

[0081] It should be noted that, during the data compression process, redundant parts of the data are removed through characteristic algorithms to reduce the required storage space and transmission bandwidth. Therefore, by pre-setting a data decompression algorithm that is associated with the degree of data compression, the sub-platform can call the data decompression algorithm that is associated with the degree of data compression after receiving the synchronization information. The data can be reconstructed according to the rules used by the data compression program and the compressed data generated to obtain the original user data.

[0082] S204: Acquire the synchronization record ID and synchronization information corresponding to the synchronization version of the rollback data synchronization operation indication from each synchronization information record entity stored in the synchronization information data pool.

[0083] During the specific execution of step S204, since the synchronization information and its synchronization version and synchronization record ID are recorded in detail in the synchronization information data pool, when the user identity cloud authentication platform determines that the detected data synchronization operation is a rollback data synchronization operation, it can directly obtain the synchronization information corresponding to the synchronization version and synchronization ID indicated by the rollback data synchronization operation from each synchronization information record entity stored in itself through the synchronization information data pool. There is no need to regenerate the corresponding synchronization information record entity, which can further improve the data synchronization efficiency and realize the accurate rollback of the sub-platform in the form of incremental data.

[0084] It should be noted that the corresponding rollback data synchronization operation initiated by the user based on the terminal may carry the synchronization version and synchronization record ID corresponding to the synchronization information to be synchronized, at least one sub-platform name, etc., which is not limited in this embodiment of the present application.

[0085] S205: Synchronize the synchronization record ID and synchronization information corresponding to the synchronization version indicated by the rollback data synchronization operation to at least one sub-platform indicated by the rollback data synchronization operation, so that when the sub-platform completely receives the corresponding synchronization information, it uses the received synchronization information to complete the corresponding data synchronization.

[0086] In the process of specifically executing step S205, a data decompression program associated with the data compression program can be pre-set; after the user identity cloud authentication platform obtains the synchronization record ID and synchronization information corresponding to the synchronization version of the rollback data synchronization operation indication from each synchronization information recording entity stored in the synchronization information data pool, the corresponding synchronization information can be synchronized to the sub-platform corresponding to each sub-platform ID of the rollback data synchronization operation indication through the multi-platform data distribution and control module, so that when each sub-platform receives the complete synchronization information, it can call the data decompression program associated with the data compression program to decompress the received synchronization information record entity to obtain the corresponding synchronization information, and use the obtained synchronization information to complete the corresponding data synchronization.

[0087] Optionally, based on the message publish-subscribe mechanism, the data distribution scheduling program is called to synchronize the synchronization record ID and synchronization version indicated by the rollback data synchronization operation to the sub-platform corresponding to each sub-platform ID indicated by the rollback data synchronization operation, so that each sub-platform calls the data decompression program to decompress the received synchronization information when receiving the corresponding synchronization information, obtains the corresponding user data, and uses the obtained user data to complete the corresponding data synchronization; wherein, the data decompression program is a decompression program that is associated with the data compression program.

[0088] It should be noted that, during the data compression process, redundant parts of the data are removed through characteristic algorithms to reduce the required storage space and transmission bandwidth. Therefore, by pre-setting a data decompression algorithm that is associated with the degree of data compression, the sub-platform can call the data decompression algorithm that is associated with the degree of data compression after receiving the synchronization information. The data can be reconstructed according to the rules used by the data compression program and the compressed data generated to obtain the original user data.

[0089] In the embodiment of the present application, the multi-platform data distribution and control module can also perform corresponding distribution status identification on the data distribution scheduler in real time to generate and record the data distribution log corresponding to the sub-platform in the process of synchronizing the corresponding synchronization information (synchronization information in the synchronization information recording entity corresponding to the real-time data synchronization operation, or the synchronization record ID and synchronization information corresponding to the synchronization version indicated by the rollback data synchronization operation) of the corresponding data distribution scheduler through the message publishing and subscription mechanism to the corresponding sub-platform. Figure 4 As shown, the data distribution log includes the synchronization version, synchronization record ID and synchronization process of the corresponding synchronization information synchronized to the sub-platform; in the process of synchronizing the corresponding synchronization information to the corresponding sub-platform, when the sub-platform encounters an exception and cannot continue to receive the synchronization information, the data distribution scheduling can be scheduled to the sub-platform, that is, the data distribution scheduling program is suspended to interrupt the corresponding real-time data synchronization operation or roll back the data synchronization operation, so as to realize the fine-grained data control of the sub-platform, so that when it is detected that the sub-platform has returned to normal, according to the synchronization process, synchronization version, synchronization record ID recorded in the recorded data distribution log and the synchronization information pre-stored in the synchronization information data pool, the remaining information can continue to be synchronized to the sub-platform, so that not only can data be synchronized to multiple sub-platforms in an incremental form, but also the network resource consumption and sub-platform system load in the data synchronization process can be reduced, and the human data comparison cost can also be reduced to ensure the consistency of the data versions synchronized before and after.

[0090] S206: During the data synchronization process, when an abnormality is detected on a sub-platform, a data distribution schedule is initiated to the sub-platform to interrupt the data synchronization on the sub-platform.

[0091] During the specific execution of step S206, for each sub-platform, when the user identity cloud authentication platform synchronizes the synchronization information corresponding to the data synchronization operation (real-time data synchronization operation or rollback data synchronization operation) to the sub-platform through the multi-platform data distribution and control module, when an abnormality is detected in the sub-platform, the data distribution scheduling program that synchronizes the same synchronization information to the sub-platform can be controlled to be paused to interrupt the data synchronization of the sub-platform, that is, to initiate data distribution scheduling for the sub-platform and stop synchronizing the corresponding data to the sub-platform.

[0092] S207: When it is detected that the sub-platform has returned to normal, the remaining synchronization information is obtained from the synchronization information in each synchronization information record entity stored in the synchronization information data pool according to the synchronization version, synchronization record ID and synchronization process in the data distribution log corresponding to the sub-platform, and the real-time data synchronization operation is restored to synchronize the remaining synchronization information to the sub-platform; wherein, the data distribution log corresponding to the sub-platform is recorded in real time when the corresponding synchronization information is synchronized to the sub-platform, and the synchronization version and synchronization record ID in the data distribution record are the synchronization version and synchronization record ID of the synchronization information synchronized to the sub-platform before the sub-platform exception occurs.

[0093] In the specific execution process of step S207, when the user identity cloud authentication platform detects that the sub-platform that had an abnormality during data synchronization has returned to normal, it can obtain the data distribution log corresponding to the sub-platform through multi-platform data distribution and control, obtain the corresponding synchronization information from the synchronization information data pool according to the synchronization version and synchronization record ID in the data distribution log, and obtain the remaining synchronization information from the obtained synchronization information according to the synchronization process recorded in the data distribution log, and finally restore the corresponding data synchronization operation (real-time data synchronization operation or rollback data synchronization operation), that is, re-call the data distribution program based on the message publishing and subscription mechanism to synchronize the remaining synchronization information to the sub-platform, so that each sub-platform calls the data decompression program to decompress the received synchronization information when receiving the complete synchronization information, obtains the user data, and uses the user data to complete the corresponding data synchronization.

[0094] It can be seen from this that after the user identity cloud authentication platform perceives that an exception has occurred on the sub-platform, it can promptly understand through the sub-platform's corresponding data distribution log which data needs to be synchronized on the sub-platform during and before the exception, so that when it is detected that the sub-platform has returned to normal, the remaining data of the corresponding version of the corresponding data distribution log can continue to be synchronized to the sub-platform. This not only ensures the consistency of data synchronization before and after the sub-platform exception occurs, but also reduces network resource consumption, system load and human data comparison costs.

[0095] The present application provides a data synchronization method, which is applied to a user identity cloud identity authentication platform. When it is determined that the data synchronization operation initiated by the user is a real-time data synchronization operation, a corresponding synchronization information recording entity can be generated, so that when the data is synchronized, the synchronization information in the synchronization information recording entity can be synchronized to the corresponding sub-platform, which can effectively reduce the amount of data in the data synchronization process, thereby reducing a certain amount of network occupancy and system load; and when the synchronization information is synchronized to the sub-platform, the corresponding synchronization process and the synchronization record ID and synchronization version of the synchronization information synchronized to the sub-platform can also be recorded in real time, and a corresponding data distribution log is generated, so that during the data synchronization process, once an abnormality occurs on the sub-platform, the data synchronization of the sub-platform is interrupted, and when it is detected that the sub-platform has returned to normal, the remaining synchronization information is obtained from the synchronization information in each synchronization information recording entity stored in the synchronization information data pool according to the synchronization version, synchronization record ID and synchronization process in the data distribution log corresponding to the sub-platform, and the real-time data synchronization operation is restored to synchronize the remaining synchronization information to the sub-platform, without re-sending the entire synchronization data to the sub-platform, so that not only can the consistency of data synchronization before and after the abnormality of the sub-platform be ensured, but also the network resource consumption, system load and human data comparison cost can be reduced.

[0096] Further, based on the data synchronization method provided in the embodiment of the present application, the data synchronization method provided in the embodiment of the present application may also include the following contents:

[0097] After completing the real-time data synchronization operation or the rollback data synchronization operation, detect in real time whether there is a sub-platform login operation initiated by the user based on the terminal; if a sub-platform login operation initiated by the user based on the terminal is detected, determine the architecture type of the sub-platform that the sub-platform login operation indicates to be logged in; according to the login rules corresponding to the sub-platform architecture type, log in to the sub-platform that the sub-platform login operation indicates to be logged in.

[0098] In an embodiment of the present application, login rules corresponding to each architecture type can be pre-set for the architecture types of each sub-platform maintained in the sub-platform management module, so that when the user has logged in to the identity cloud authentication platform and completed the real-time data synchronization operation or the rollback data synchronization operation, the same authentication module of the multiple architecture platforms can be used to detect in real time whether there is a sub-platform login operation initiated by the user based on the terminal; if a sub-platform login operation initiated by the user based on the terminal is detected, the login rule corresponding to the architecture type of the sub-platform indicated by the sub-platform login operation can be obtained from the pre-set login rules, so that the login rule corresponding to the architecture type of the sub-platform indicated by the sub-platform login operation can be used to log in to the corresponding sub-platform.

[0099] It can be seen that after the user logs in to the user identity cloud authentication platform, he can initiate the corresponding sub-platform login operation through the terminal, log in to the corresponding sub-platform, and then access the corresponding sub-platform without repeatedly entering the corresponding authentication information. This not only simplifies the login operation, but also improves the user experience, enhances the system's ease of use and user satisfaction.

[0100] It should be noted that the architecture type of the sub-platform may include a web-side architecture type, a mobile-side architecture type, a PC client architecture type, etc., which is not limited in the embodiments of the present application.

[0101] In some embodiments, when the user identity cloud authentication platform determines that the architecture type of the sub-platform that the user logs in to based on the sub-platform login operation initiated by the terminal is a Web-end architecture type, it can jump to the sub-platform page address by carrying a JWT token, so that the Web terminal platform can parse the token according to the SDK and API method provided by the user identity cloud authentication platform to achieve password-free login; when the user identity cloud authentication platform determines that the architecture type of the sub-platform that the user logs in to based on the sub-platform login operation initiated by the terminal is a mobile-end architecture type, it scans the corresponding QR code to identify the corresponding user information, so that the mobile terminal platform can parse the token according to the SDK and API method in the identified user information to achieve password-free login; when the user identity cloud authentication platform determines that the architecture type of the sub-platform that the user logs in to based on the sub-platform login operation initiated by the terminal is a telecommunications architecture type, it can use a web page quick login method, based on the same domain principle / quick login page to obtain the corresponding user information from the Cookie, and then feed it back to the corresponding sub-platform, so that the telecommunications terminal platform can parse the token according to the SDK and API method in the fed-back user information to achieve password-free login, such as Figure 5 shown.

[0102] It can be seen from this that the present application can pre-set login rules corresponding to each architecture type of each sub-platform maintained in the sub-platform management module, so that in the process of logging into the sub-platform, the sub-platform can be logged in by utilizing the login rules corresponding to the architecture type of the sub-platform to achieve single sign-on with unified authentication. Users only need to log in once on the user identity cloud authentication platform, and then they can log in to the corresponding sub-platform through the user identity cloud authentication platform without repeatedly entering the corresponding authentication information. This can not only solve the problem that traditional single sign-on platforms cannot dynamically adapt to the access of multiple architecture platforms, but also simplify the corresponding login operations, improve user experience, and enhance the system's usability and user satisfaction.

[0103] The present application embodiment provides an electronic device, such as Figure 6As shown, the electronic device includes a processor 601 and a memory 602, the memory 602 is used to store program codes and data for data synchronization, and the processor 601 is used to call program instructions in the memory to execute the steps shown in the data synchronization method in the above embodiment.

[0104] An embodiment of the present application provides a storage medium, which includes a storage program, wherein when the program is running, the device where the storage medium is located is controlled to execute the data synchronization method shown in the above embodiment.

[0105] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, in which the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0106] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0107] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

[0108] The above are only preferred implementations of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A data synchronization method, characterized in that: Applied to a user identity cloud authentication platform, the method includes: When a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, a synchronization information record entity corresponding to the real-time data synchronization operation is generated, and the synchronization information record entity is stored in a synchronization information data pool; wherein the synchronization information record entity includes synchronization information, a synchronization version corresponding to the synchronization information, and a synchronization record ID; Synchronize the synchronization information to at least one sub-platform indicated by the real-time data synchronization operation, so that when the sub-platform completely receives the corresponding synchronization information, it uses the received synchronization information to complete the corresponding data synchronization; During the data synchronization process, when an abnormality is detected on the sub-platform, a data distribution scheduling is initiated to the sub-platform to interrupt the data synchronization of the sub-platform; When it is detected that the sub-platform has returned to normal, the remaining synchronization information is obtained from the synchronization information in each synchronization information recording entity stored in the synchronization information data pool according to the synchronization version, synchronization record ID and synchronization process in the data distribution log corresponding to the sub-platform, and the real-time data synchronization operation is restored to synchronize the remaining synchronization information to the sub-platform; wherein, the data distribution log corresponding to the sub-platform is recorded in real time when the corresponding synchronization information is synchronized to the sub-platform, and the synchronization version and synchronization record ID in the data distribution record are the synchronization version and synchronization record ID of the synchronization information synchronized to the sub-platform before the abnormality of the sub-platform occurs.

2. The method according to claim 1, characterized in that When a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, a synchronization information record entity corresponding to the data synchronization operation is generated, and the synchronization information record entity is stored in a synchronization information data pool, including: When a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, determining that the real-time data synchronization operation indicates synchronized user data, at least one sub-platform ID, and a timestamp; Calling a preset data compression program to generate corresponding synchronization information, synchronization version and synchronization record ID according to user data, at least one sub-platform ID and a timestamp, and generating a synchronization information record entity corresponding to the real-time data synchronization operation according to the synchronization information, the synchronization version and the synchronization record ID according to a preset data structure; The synchronization information recording entity corresponding to the real-time data synchronization operation is stored in a synchronization information data pool.

3. The method according to claim 2, characterized in that The step of synchronizing the synchronization information in the synchronization information recording entity to at least one sub-platform indicated by the real-time data synchronization operation, so that the sub-platform completes corresponding data synchronization using the received synchronization information when the synchronization information is completely received, includes: For each of the sub-platform IDs, the data distribution scheduling program is called based on the message publishing and subscription mechanism to synchronize the synchronization information in the synchronization information recording entity to the sub-platform corresponding to the sub-platform ID, so that the sub-platform calls the data decompression program to decompress the synchronization information when receiving the synchronization information, obtains the user data, and uses the user data to complete the corresponding data synchronization; wherein, the data decompression program is a decompression program that is associated with the data compression program.

4. The method according to claim 1, characterized in that: The method further comprises: When a data synchronization operation initiated by a user based on a terminal is detected, and the data synchronization operation is a rollback data synchronization operation, the synchronization record ID and synchronization information corresponding to the synchronization version indicated by the rollback data synchronization operation are obtained from each synchronization information record entity stored in the synchronization information data pool; The synchronization record ID and synchronization information corresponding to the synchronization version indicated by the rollback data synchronization operation are synchronized to at least one sub-platform indicated by the rollback data synchronization operation, so that when the sub-platform completely receives the corresponding synchronization information, it uses the received synchronization information to complete the corresponding data synchronization.

5. The method according to claim 1 or 4, characterized in that: The method further comprises: After completing the real-time data synchronization operation or the rollback data synchronization operation, detecting in real time whether there is a sub-platform login operation initiated by the user based on the terminal; If a sub-platform login operation initiated by the user based on the terminal is detected, determining the architecture type of the sub-platform that the sub-platform login operation indicates to log in; According to the login rule corresponding to the architecture type of the sub-platform, the sub-platform login operation indicates the sub-platform to be logged in.

6. A user identity cloud authentication platform, characterized in that: The user identity cloud authentication platform at least includes a synchronization information data pool and a multi-platform data distribution and control module; A synchronization information data pool, for generating a synchronization information record entity corresponding to the real-time data synchronization operation when a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, and storing the synchronization information record entity in the synchronization information data pool; wherein the synchronization information record entity includes synchronization information, a synchronization version corresponding to the synchronization information, and a synchronization record ID; A multi-platform data distribution and control module is used to synchronize the synchronization information to at least one sub-platform indicated by the real-time data synchronization operation, so that when the sub-platform completely receives the corresponding synchronization information, it uses the received synchronization information to complete the corresponding data synchronization; during the data synchronization process, when an abnormality is detected in the sub-platform, a data distribution schedule is initiated to the sub-platform to interrupt the data synchronization of the sub-platform; when it is detected that the sub-platform has returned to normal, the remaining synchronization information is obtained from the synchronization information in each synchronization information record entity stored in the synchronization information data pool according to the synchronization version, synchronization record ID and synchronization process in the data distribution log corresponding to the sub-platform, and the real-time data synchronization operation is restored to synchronize the remaining synchronization information to the sub-platform; wherein, the data distribution log corresponding to the sub-platform is a real-time record when the corresponding synchronization information is synchronized to the sub-platform, and the synchronization version and synchronization record ID in the data distribution record are the synchronization version and synchronization record ID of the synchronization information synchronized to the sub-platform before the abnormality occurs on the sub-platform.

7. The user identity cloud authentication platform according to claim 6, characterized in that: When a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, a synchronization information record entity corresponding to the data synchronization operation is generated, and the synchronization information record entity is stored in a synchronization information data pool of a synchronization information data pool, specifically used for: When a data synchronization operation initiated by a user based on a terminal is detected and the data synchronization operation is a real-time data synchronization operation, determining that the real-time data synchronization operation indicates synchronized user data, at least one sub-platform ID, and a timestamp; Call a preset data compression program to generate corresponding synchronization information, synchronization version and synchronization record ID according to user data, at least one sub-platform ID and a timestamp, and generate a synchronization information record entity corresponding to the real-time data synchronization operation according to the synchronization information, the synchronization version and the synchronization record ID according to a preset data structure; store the synchronization information record entity corresponding to the real-time data synchronization operation in a synchronization information data pool.

8. The user identity cloud authentication platform according to claim 6, characterized in that: The multi-platform data distribution and control module is specifically used to synchronize the synchronization information in the synchronization information recording entity to at least one sub-platform indicated by the real-time data synchronization operation, so that when the sub-platform receives the synchronization information completely, it uses the received synchronization information to complete the corresponding data synchronization. For each of the sub-platform IDs, the data distribution scheduling program is called based on the message publishing and subscription mechanism to synchronize the synchronization information in the synchronization information recording entity to the sub-platform corresponding to the sub-platform ID, so that the sub-platform calls the data decompression program to decompress the synchronization information when receiving the synchronization information, obtains the user data, and uses the user data to complete the corresponding data synchronization; wherein, the data decompression program is a decompression program that is associated with the data compression program.

9. An electronic device, characterized in that: include: A processor and a memory, wherein the processor and the memory are connected via a communication bus; wherein the processor is used to call and execute a program stored in the memory; The memory is used to store a program, and the program is used to implement the data synchronization method as described in any one of claims 1-5.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to execute the data synchronization method according to any one of claims 1 to 5.

Images