Method, device, medium and electronic equipment for synchronizing information between isolated systems

Abstract

The application discloses a method and device for synchronizing information between isolated systems, a medium and an electronic device. The method comprises: synchronizing user information in an internal system to obtain a personal user identifier with permission; in response to a use request of an external system, obtaining the personal user identifier in the use request of the external system; identifying whether the state of the external system is in an occupied state; if not, modifying the external system to a state of being about to be used, and generating a temporary password of the current personal user identifier; in response to a login operation on the external system, if the personal user identifier of the login operation matches the temporary password, entering the external system; and in response to a processing operation of public data, synchronizing the public data of the external system to an operation record table. The technical scheme can realize automatic synchronization of information between two physically isolated systems, ensure single-person use characteristics of the external system, and facilitate a staff member to synchronize information to the external system.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, medium and electronic device for information synchronization between isolated systems. Background Technology

[0002] In some scenarios, such as entities providing social services, information must not only be disclosed in internal systems but also synchronized to external systems accessible to the public. For example, insurance companies can disclose information about their online insurance products, partner institutions, and other necessary disclosures.

[0003] However, in actual disclosure processes, personnel performing information disclosure operations are located in various locations. Simultaneously, there is a desire to synchronize information disclosure between internal and external systems to avoid consumer ambiguity. Due to special requirements such as confidentiality and security, the internal and external systems are constrained by the following two objective factors: First, the internal and external systems cannot achieve system-level data integration; therefore, information entry can only be completed manually by logging into each system separately. Second, there are differences in account management between the internal and external systems: the internal system is open to staff located in various locations for account login and disclosure operations, while the external system only provides one account for login and disclosure operations. Therefore, how to solve the data synchronization problem under these objective constraints of internal and external systems is a pressing technical challenge that needs to be addressed by those in the field. Summary of the Invention

[0004] This application provides a method, apparatus, medium, and electronic device for information synchronization between isolated systems. By creating an external system access tool between the internal and external systems, this application responds to external system access requests, determines whether the external system is in use, and generates a temporary password for login and data synchronization if the system is not in use. This ensures the single-user accessibility of the external system and facilitates information synchronization by staff.

[0005] This application provides a method for information synchronization between isolated systems, the method comprising:

[0006] Synchronize registered user information from the internal system to obtain authorized personal user identifiers;

[0007] In response to an external system usage request, obtain the personal user identifier from the external system usage request;

[0008] Identify whether the external system is in a occupied state;

[0009] If the external system is not in use, it will be modified to be ready for use, and a temporary password for the current personal user identifier will be generated.

[0010] In response to a login operation to an external system, if the personal user identifier of the login operation matches the temporary password, then the user enters the external system.

[0011] In response to operations that process publicly available data from external systems, the publicly available data from external systems is synchronized to the operation log table.

[0012] Furthermore, after accessing an external system, the method further includes:

[0013] In response to the exit operation of the external system, the status of the external system is changed to unoccupied state;

[0014] or,

[0015] If the duration of access to the external system reaches the preset duration, the current personal user ID will be forcibly logged out, and the status of the external system will be changed to non-occupied.

[0016] Furthermore, after responding to the processing operation of publicly available data from an external system and synchronizing the publicly available data from the external system to the operation log table, the method further includes:

[0017] If the verification trigger conditions are met, the publicly available data from the internal system will be retrieved; the publicly available data from the internal system includes user operation records.

[0018] The publicly available data from external systems is extracted using data acquisition tools; this publicly available data includes user operation records.

[0019] The publicly available data of the internal system and the publicly available data of the external system are verified.

[0020] Furthermore, the publicly available data of the internal system and the publicly available data of the external system are verified, including:

[0021] The public data of the internal system and the public data of the external system are standardized respectively.

[0022] The standardized public data of the internal system and the standardized public data of the external system are fully correlated, and a verification label is generated for each row of data.

[0023] Furthermore, after generating a verification label for each row of data, the method further includes:

[0024] The consistency rate of each individual user's identifier is calculated based on the verification status tags.

[0025] If the consistency rate is lower than the set threshold, a prompt message will be sent to the individual user corresponding to the individual user ID.

[0026] Furthermore, the external system is modified to a state ready for use, and a temporary password for the current personal user identifier is generated, including:

[0027] In response to the external system's usage request, the account and login password of the current external system are obtained from the pre-set account allocation record database.

[0028] Use the Selenium tool to simulate logging into an external system;

[0029] A temporary password is randomly generated. The Selenium tool is used to simulate a human changing the password in an external system, and the temporary password and activation time of the account are recorded in the account allocation record table.

[0030] Furthermore, identifying whether the external system is in an occupied state includes:

[0031] The Redis database synchronous read / write mechanism is used to determine whether other people are using the external system;

[0032] If so, then it is determined that the device is in an occupied state;

[0033] If not, then it is determined to be in an unoccupied state.

[0034] This application embodiment also provides an information synchronization device between isolated systems, the device comprising:

[0035] The identifier acquisition module is used to synchronize registered user information from the internal system and obtain a personal user identifier with the appropriate permissions.

[0036] The request-response module is used to respond to external system usage requests and obtain the personal user identifier in the external system usage request;

[0037] The status recognition module is used to identify whether the external system is in an occupied state;

[0038] The generation module is used to modify the external system to a state of imminent use if it is not in use, and to generate a temporary password for the current personal user identifier;

[0039] The login module is used to respond to login operations to external systems. If the personal user identifier of the login operation matches the temporary password, then the user can enter the external system.

[0040] The synchronization module is used to respond to the processing operations of public data from external systems and to synchronize the public data from external systems to the operation log table.

[0041] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the information synchronization method between isolated systems as described in this application.

[0042] This application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the information synchronization method between isolated systems as described in this application.

[0043] The above-described technical solutions adopted in the embodiments of this application can achieve the following beneficial effects:

[0044] The technical solution provided in this application creates an external system usage tool between the internal and external systems. This tool responds to external system usage requests, determines whether the external system is in use, and generates a temporary password when it is not in use to log in to the external system and synchronize data. This ensures the single-user nature of the external system and facilitates staff in synchronizing information to the external system. Attached Figure Description

[0045] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0046] Figure 1 This is a flowchart illustrating the information synchronization method between isolated systems provided in Embodiment 1 of this application;

[0047] Figure 2 This is a schematic diagram of the account synchronization process of the internal system provided in Embodiment 1 of this application;

[0048] Figure 3 This is a schematic diagram of the entire information synchronization process provided in Embodiment 1 of this application;

[0049] Figure 4 This is a flowchart illustrating the batch processing of external system backend jobs in the polling implementation provided in Embodiment 1 of this application;

[0050] Figure 5 This is a flowchart illustrating the automated verification process provided in Embodiment 1 of this application;

[0051] Figure 6 This is a schematic diagram of the overall information synchronization process provided in Embodiment 1 of this application;

[0052] Figure 7 This is a schematic diagram of the information synchronization device between isolated systems provided in Embodiment 2 of this application. Detailed Implementation

[0053] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0054] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0055] Example 1

[0056] Figure 1 This is a flowchart illustrating the information synchronization method between isolated systems provided in Embodiment 1 of this application. This embodiment is applicable to information synchronization between two physically isolated systems. The method can be executed by the information synchronization device between isolated systems provided in this embodiment. This device can be implemented in software and / or hardware and can be integrated into an electronic device used for information synchronization between isolated systems.

[0057] like Figure 1 As shown, the method includes steps S110 to S160:

[0058] S110. Synchronize registered user information from the internal system to obtain a personal user identifier with the appropriate permissions;

[0059] Specifically, this solution can be implemented from the perspective of external authorization tools. Operators can only use the external closed system through external authorization tools; this ensures that only one person can use the external system at a time, while also recording the actual user.

[0060] To further illustrate step S110, Figure 2 This is a schematic diagram of the account synchronization process of the internal system provided in Embodiment 1 of this application. Figure 2 As shown, the tool requires operators to first register and record their accounts and personal identification information in the internal system, and then synchronize this information to the external authorized tool before they can perform relevant operations in the internal system, ensuring the consistency of accounts between the internal system and the external authorized tool.

[0061] The tool is specifically divided into an interactive application process and a background batch job process. Both processes synchronize state information using Redis (an in-memory database technology).

[0062] To further illustrate step S110, Figure 3 This is a schematic diagram illustrating the entire information synchronization process provided in Embodiment 1 of this application. For example... Figure 3 As shown, the information synchronization design process of the interactive terminal system is mainly divided into: application and allocation stage, usage stage and exit stage.

[0063] The application and allocation phase is mainly used for identity verification, ensuring that the current external system account is used by one person, and generating a temporary password for the current use.

[0064] Operators submit applications to external authorization tools to use account information for external systems.

[0065] S120. In response to an external system usage request, obtain the personal user identifier in the external system usage request;

[0066] In this process, after verifying the identity of an external user using an authorization tool, the system uses a Redis database synchronous read / write mechanism to determine whether other people are using the external system.

[0067] S130. Identify whether the external system is in an occupied state;

[0068] The criterion for determining whether an account is in use can be read from the Redis database to see if any other account is currently being used by an external system.

[0069] In this embodiment, optionally, identifying whether the external system is in an occupied state includes:

[0070] The Redis database synchronous read / write mechanism is used to determine whether other people are using the external system;

[0071] If so, then it is determined that the device is in an occupied state;

[0072] If not, then it is determined to be in an unoccupied state.

[0073] In this case, when someone else changes the state of an external system to a state that is about to be used, it can be understood as a situation where it is being used by someone else.

[0074] This setup allows for quick and accurate identification of the status of external systems by reading data from the Redis database.

[0075] S140. If the external system is not in a occupied state, modify it to a state of imminent use and generate a temporary password for the current personal user identifier.

[0076] If no one else is using it, mark it as intended for use in the Redis database and asynchronously send a password change job to the external system;

[0077] After completing the password modification operation on the external system, the system, based on the operator's usage information, retrieves the actual assignee information for the external system and writes it to the database. A successful assignment message is sent to the operator, indicating that they can log in to the external authorization tool to use the external system.

[0078] Optionally, in this solution, the external system can be modified to a state ready for use, and a temporary password for the current personal user identifier can be generated, including:

[0079] In response to the external system's usage request, the account and login password of the current external system are obtained from a pre-set account allocation record database.

[0080] Use the Selenium tool to simulate logging into an external system;

[0081] A temporary password is randomly generated. The Selenium tool is used to simulate a human changing the password in an external system, and the temporary password and activation time of the account are recorded in the account allocation record table.

[0082] To further illustrate step S140, Figure 4 This is a flowchart of the batch job of the background external system provided in Embodiment 1 of this application. The background batch job process mainly performs relevant polling operations based on the Redis status of the interactive terminal product: the batch job will calculate the execution conditions every 5 seconds: whether there is a command to change the password, and whether the current state is an exit command that needs to be extracted from the log.

[0083] If the execution conditions are met, the account and login password information of the current external system are retrieved from the account allocation record database; the Selenium tool is then used to simulate logging into the external system.

[0084] If the client passes a Redis flag indicating that it is intended to be used, a new password is randomly generated. Selenium is used to simulate a human changing the password in an external system, and the new password and activation time of the account are recorded in the account allocation record table.

[0085] If the password change is successful, the Redis flag will be changed to "ready" and feedback will be sent to the operator via the front-end interaction to indicate that the external system can be used.

[0086] If the client passes a Redis flag indicating that logs have not been retrieved, then Selenium is used to log in to the external system backend to obtain the usage log table, and the logs are written into the user's external system usage record table within the tool.

[0087] The password reset process can be understood as a waiting process that continuously polls to see if there are any status requests initiated by the interactive end, and responds promptly if so.

[0088] S150. In response to a login operation to an external system, if the personal user identifier of the login operation matches the temporary password, then the user enters the external system.

[0089] During the usage phase, operators who have successfully applied to use the external system are provided with a browser environment for using the external system. Operators can only use the external system within this environment.

[0090] After receiving the successful allocation message, the operator logs into the tool again to verify their identity.

[0091] Once the operator formally initiates a request to use an external system, the tool invokes the external system via the chromedriver driver and automatically performs the login operation using the selenium tool. The tool records the login time in the user's external system usage log table.

[0092] S160. Respond to the processing operation of public data from the external system and synchronize the public data from the external system to the operation log table.

[0093] Understandably, operators use chromedriver to start operating external systems and complete their own business operations.

[0094] Based on the above technical solutions, optionally, after entering an external system, the method further includes:

[0095] In response to the exit operation of the external system, the status of the external system is changed to unoccupied state;

[0096] or,

[0097] If the duration of access to the external system reaches the preset duration, the current personal user ID will be forcibly logged out, and the status of the external system will be changed to non-occupied.

[0098] The exit phase mainly involves exiting the external system after its use has been completed.

[0099] After using the external system, operators must log in to the tool again and be authenticated to access the tool.

[0100] Once the operator formally initiates a request to withdraw from the use of the external system, the tool executes the operation to shut down the external system via chromedriver and records the withdrawal time in the user's external system usage record table.

[0101] After successfully shutting down external system operations, the tool initiates an asynchronous batch job to extract logs from the external system. It uses the Selenium tool to extract operation logs from the external system's backend and writes them to the tool's user external new system usage record table.

[0102] Specifically, if the operator does not exit the tool after use, the tool will automatically exit after 3 hours.

[0103] After responding to the processing operation on publicly available data from an external system and synchronizing the publicly available data from the external system to the operation log table, the method further includes:

[0104] If the verification trigger conditions are met, the publicly available data from the internal system will be retrieved; the publicly available data from the internal system includes user operation records.

[0105] The publicly available data from external systems is extracted using data acquisition tools; this publicly available data includes user operation records.

[0106] The publicly available data of the internal system and the publicly available data of the external system are verified.

[0107] Among them, data collection tools can be text or other content recognition tools used to collect publicly available data from external systems, such as extracting text, images, and other useful information.

[0108] The embodiments provided in this application create an external system usage tool between the internal and external systems. This tool responds to external system usage requests, determines whether the external system is occupied, and generates a corresponding temporary password to log in to the external system and synchronize data if it is not occupied. This ensures the single-user nature of the external system and facilitates staff to synchronize information to the external system.

[0109] In one embodiment, optionally, after responding to a processing operation on publicly available data from an external system and synchronizing the publicly available data from the external system to an operation log table, the method further includes:

[0110] If the verification trigger conditions are met, the publicly available data from the internal system will be retrieved; the publicly available data from the internal system includes user operation records.

[0111] The publicly available data from external systems is extracted using data acquisition tools; this publicly available data includes user operation records.

[0112] The publicly available data of the internal system and the publicly available data of the external system are verified.

[0113] This solution mainly involves performing correlation calculations on internal data, tool data, and external data, and then sending the results for verification.

[0114] Figure 5This is a schematic diagram of the automated verification process provided in Embodiment 1 of this application. Figure 5 As shown, the verification trigger conditions are met, such as acquiring relevant publicly available data from the internal system at an agreed time (daily), which also includes user operation records. The data is then cleaned and transformed after verifying the standard fields.

[0115] External system data, crawled within the agreed timeframe, is then correlated with tool data (a user external system usage record table, including user operation records). After data cleaning and verification of standard fields, the data is transformed.

[0116] Optionally, in this solution, the publicly available data of the internal system and the publicly available data of the external system are verified, including:

[0117] The public data of the internal system and the public data of the external system are standardized respectively.

[0118] The standardized public data of the internal system and the standardized public data of the external system are fully correlated, and a verification label is generated for each row of data.

[0119] Understandably, the fields to be checked must be predetermined beforehand, along with details such as the conversion of full-width and half-width formats within those fields. The publicly available data, after internal and external conversion, undergoes a full correlation calculation. For each correlated row, a correlation status label is calculated, along with detailed reasons for any inconsistencies. The consistency rate is calculated based on these labels. Notification tools, such as emails, are automatically set up to send notifications of inconsistencies to relevant personnel.

[0120] Figure 6 This is a schematic diagram of the overall information synchronization process provided in Embodiment 1 of this application. For example... Figure 6 As shown, based on the above solutions, this application adds an external access authorization tool to an account within the external closed system. This ensures that operators can only use the external closed system through the external access authorization tool, guaranteeing that only one person can use the external system at a time, while also recording the actual user. The account for the external access authorization tool is synchronized with the internal system account to ensure consistent login permissions.

[0121] If an operator fails to disclose an operation performed on an internal system in a timely manner on an external system, the external authorized tool will send a text message reminder to the operator.

[0122] During the verification process, publicly available data from internal and external systems is captured using technologies such as data collection and extraction. Inconsistent results are reported through automated verification tools and can be sent to the relevant personnel for confirmation, reference, and modification.

[0123] This systematic and fully automated management approach allows for the accumulation of relevant data, including operational records disclosed by our internal system operators, operational record data from external systems, and performance indicators such as the consistency rate of operators' historical operations.

[0124] Example 2

[0125] Figure 7 This is a schematic diagram of the information synchronization device between isolated systems provided in Embodiment 2 of this application. Figure 7 As shown, the device includes:

[0126] The identifier acquisition module 710 is used to synchronize registered user information from the internal system and obtain a personal user identifier with the appropriate permissions.

[0127] The request response module 720 is used to respond to an external system usage request and obtain the personal user identifier in the external system usage request;

[0128] The status recognition module 730 is used to identify whether the external system is in an occupied state;

[0129] The generation module 740 is used to modify the external system to a state of imminent use if it is not in a state of occupancy, and to generate a temporary password for the current personal user identifier.

[0130] The login module 750 is used to respond to a login operation to an external system. If the personal user identifier of the login operation matches the temporary password, then the user enters the external system.

[0131] The synchronization module 760 is used to respond to the processing operation of public data of the external system and synchronize the public data of the external system to the operation log table.

[0132] This technical solution addresses the issue of shared access within a single account by utilizing external authorization tools, and systematically resolves the problem of tracking actual operations. It automates the entire business process of data acquisition, verification, and reporting between internal and external systems, replacing manual operations and improving productivity. It also provides a novel solution for a synchronized information reminder mechanism for two physically isolated information systems. This solution offers a way to ensure data synchronization between single-account and multi-account systems, specifically addressing two physically isolated systems.

[0133] This device can execute the information synchronization methods between isolated systems provided in the above embodiments, and has corresponding functional modules and beneficial effects. Further details are omitted here.

[0134] Example 3

[0135] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0136] Therefore, this application also proposes a computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the methods described in any embodiment of this application.

[0137] Furthermore, this application also proposes an electronic device including a memory, a processor, an input device, an output device, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method described in any embodiment of this application.

[0138] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0139] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0140] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0141] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0142] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0143] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0144] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for synchronizing information between isolated systems, characterized in that, The method is applicable to scenarios where internal and external systems are physically isolated, and the external system is configured with only a single shared account for multiple internal staff to log in and perform disclosure operations. The method includes: Registered user information is synchronized from the internal system, and the account and personal identification information of the internal system are synchronized to the external authorized tools to obtain personal user identification with permissions, so as to ensure the consistency of accounts between the internal system and the external authorized tools. In response to an external system usage request, obtain the personal user identifier from the external system usage request; Identify whether the external system is in a occupied state; If the external system is not in use, the status of the external system is marked as an intermediate state of imminent use in the Redis database, and a password change job is sent asynchronously to the external system. In response to the completion of the password change job, the status in the Redis database is updated to ready, and a temporary password for the current personal user identifier is generated. The execution of the password change job includes: using the Selenium tool to simulate logging into the external system, randomly generating a temporary password, simulating a human changing the password in the external system, and recording the account's temporary password and activation time in the account allocation record table. In response to a login operation to an external system, if the personal user identifier of the login operation matches the temporary password, then the user enters the external system. In response to operations that process publicly available data from external systems, the publicly available data from external systems is synchronized to the operation log table; If the verification trigger condition is met, the system acquires publicly available data from the internal system, including user operation records. It then extracts publicly available data from the external system, also including user operation records, using a data acquisition tool. The system standardizes both the internal and external publicly available data, fully associating the standardized data with the external publicly available data. A verification status label is generated for each line of data, and the data consistency rate for each individual user identifier is calculated based on the verification status label. If the consistency rate is lower than a set threshold, a notification is sent to the individual user corresponding to that user identifier. After entering the external system, the process also includes: responding to the exit operation of the external system and changing the status of the external system to an unoccupied state; or, if it is detected that the duration of entering the external system reaches a preset duration, forcibly exiting the current personal user ID and asynchronously initiating a batch job to extract operation logs from the external system: using the Selenium tool to log in to the external system backend to extract operation logs, writing the extracted operation logs into the user's external system usage record table, and then changing the status of the external system to an unoccupied state.

2. An information synchronization device between isolated systems, characterized in that, The apparatus is used to perform the method as described in claim 1, the apparatus comprising: The identifier acquisition module is used to synchronize registered user information from the internal system and obtain a personal user identifier with the appropriate permissions. The request-response module is used to respond to external system usage requests and obtain the personal user identifier in the external system usage request; The status recognition module is used to identify whether the external system is in an occupied state; The generation module is used to modify the external system to a state of imminent use if it is not in use, and to generate a temporary password for the current personal user identifier; The login module is used to respond to login operations to external systems. If the personal user identifier of the login operation matches the temporary password, then the user can enter the external system. The synchronization module is used to respond to the processing operations of public data from external systems and to synchronize the public data from external systems to the operation log table.

3. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the information synchronization method between isolated systems as described in claim 1.

4. An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the information synchronization method between isolated systems as described in claim 1.

Images