Network disconnection reconstruction method and system meeting network synchronization requirement

Abstract

The application discloses a network disconnection reconstruction method and system meeting network synchronization requirements, and relates to the technical field of network synchronization. The method comprises the following steps: logically dividing production content into multiple independently-operable logical modules in advance; a master synchronization client performs synchronization logic calculation based on the multiple logical modules, and synchronizes progress data of each logical module generated in the calculation process to each ordinary synchronization client in real time as public data, wherein the progress data is determined based on the completion of multiple key nodes in each logical module; when the master synchronization client is disconnected, a new master synchronization client is determined from the multiple ordinary synchronization clients; and the new master synchronization client identifies the completion state of each logical module based on the public data, and performs network disconnection reconstruction based on the completion state of each logical module. The network disconnection reconstruction can be performed by the newly-selected master synchronization client, thereby ensuring the continuity of the network synchronization system.

Description

Technical Field

[0001] This application relates to the field of network synchronization technology, and in particular to a method and system for reconstructing a network disconnection that meets the requirements of network synchronization. Background Technology

[0002] In existing multi-client network synchronization technologies, common implementation methods mainly include two modes: server-authoritative state synchronization and client-frame synchronization. Server-authoritative state synchronization requires the deployment of a dedicated server to run the main business logic, while the client is only responsible for the presentation layer. This mode has high requirements for system architecture and high server deployment and maintenance costs. Client-frame synchronization, on the other hand, requires each client to perform completely consistent logical calculations under the same input. It has extremely high requirements for floating-point precision, execution order, and consistency of underlying libraries, and is prone to data deviations due to hardware or environmental differences.

[0003] In view of this, existing technologies have proposed client-based network synchronization methods with multiple clients participating in network synchronization. By selecting a master synchronization client to centrally execute synchronization logic calculations and distributing the results to other ordinary synchronization clients, server dependency is reduced while ensuring the consistency of calculation results. However, in the application of this method, if the master synchronization client unexpectedly disconnects or crashes, the entire network synchronization system will face the risk of operational interruption. Summary of the Invention

[0004] The purpose of this application is to provide a network disconnection reconstruction method and system that meets the network synchronization requirements, and can solve the problem mentioned above that "when the main synchronization client experiences an unexpected disconnection or crash, the entire network synchronization system will face the risk of operational interruption".

[0005] To achieve the above objectives, this application provides the following solution: Firstly, this application provides a network disconnection reconstruction method that meets network synchronization requirements, applied to multiple clients participating in network synchronization, wherein one of the multiple clients is designated as the primary synchronization client, and the remaining clients are designated as ordinary synchronization clients; the network disconnection reconstruction method that meets network synchronization requirements includes: The content to be produced is pre-divided into multiple independently operable logical modules according to their logical functions; During the network synchronization operation, the main synchronization client performs synchronization logic calculations based on multiple logic modules, and uses the progress data of each logic module generated during the calculation as common data to synchronize to each ordinary synchronization client in real time. The progress data is determined based on the completion status of multiple key nodes within each logic module. When the primary synchronization client disconnects, a new primary synchronization client is determined from among the multiple ordinary synchronization clients and used as the primary synchronization client for reconstruction. The reconstruction master synchronization client identifies the completion status of each logical module based on the public data, and performs network disconnection reconstruction based on the completion status of each logical module.

[0006] In one embodiment, the step of identifying the completion status of each logic module based on the public data, and performing network disconnection reconstruction based on the completion status of each logic module, specifically includes: For each logical module, the reconstruction master synchronization client determines the completion status of the logical module based on the corresponding progress data; When the logic module is in a completed state, it remains in a completed state. When the logic module is in an incomplete state, multiple key nodes that have not yet been completed are identified based on the corresponding progress data, and the execution progress is advanced to the target progress from the starting point of the multiple key nodes that have not yet been completed.

[0007] In one embodiment, the public data further includes key node results, which characterize the business status data generated when the key node in the logic module finishes running.

[0008] In one embodiment, each of the logic modules further includes temporary data and internal data during runtime; The primary synchronization client can also synchronize the temporary data and internal data generated during the calculation process to each of the ordinary synchronization clients.

[0009] In one embodiment, the plurality of said logic modules are configured to execute linearly or concurrently.

[0010] In one embodiment, each of the clients has synchronous logic computing capabilities, and the main synchronous client and each of the ordinary synchronous clients are pre-configured with the operating logic of each of the logic modules.

[0011] Secondly, this application also provides a network disconnection reconstruction system that meets network synchronization requirements, applied to multiple clients participating in network synchronization, wherein one of the multiple clients is designated as the primary synchronization client, and the remaining clients are designated as ordinary synchronization clients; the network disconnection reconstruction system that meets network synchronization requirements includes: Logical partitioning units are used to pre-divide the content to be produced into multiple independently operable logical modules according to their logical functions; The synchronization calculation unit is used to enable the main synchronization client to perform synchronous logical calculations based on multiple logical modules during network synchronization calculations, and to synchronize the progress data of each logical module generated during the calculation process as common data to each ordinary synchronization client in real time. The progress data is determined based on the completion status of multiple key nodes within each logical module. The re-selection unit is used to determine a new primary synchronization client from among the multiple ordinary synchronization clients when the primary synchronization client goes offline, and to serve as the re-reconstructed primary synchronization client. The progress advancement unit is used to enable the reconstruction master synchronization client to identify the completion status of each of the logical modules based on the public data, and to perform network disconnection reconstruction based on the completion status of each of the logical modules.

[0012] In one embodiment, the progress advancement unit includes a state recognition subunit and an execution subunit; For each logical module, the status identification subunit is used to enable the reconstruction master synchronization client to determine the completion status of the logical module based on the corresponding progress data; The execution subunit is used to maintain the completed state when the logic module is in a completed state, and to identify multiple key nodes that have not yet been completed based on the corresponding progress data when the logic module is in an incomplete state, so as to advance the execution progress to the target progress from the starting point of the multiple key nodes that have not yet been completed.

[0013] In one embodiment, the public data further includes key node results, which characterize the business status data generated when the key node in the logic module finishes running.

[0014] In one embodiment, each of the logic modules further includes temporary data and internal data; The primary synchronization client can also synchronize the temporary data and internal data generated during the calculation process to each of the ordinary synchronization clients.

[0015] According to the specific embodiments provided in this application, the following technical effects are disclosed: This application provides a network disconnection reconstruction method that meets network synchronization requirements. By pre-dividing the content into multiple independently runnable logical modules, and during the synchronization process, the main synchronization client synchronizes the progress data of each module as common data to ordinary clients in real time. This allows the newly selected reconstruction main synchronization client to accurately identify the completion status of each logical module based on the synchronized common data when the main synchronization client disconnects. The reconstruction is then performed based on the completion status of each logical module, thus quickly resuming the execution process before the disconnection without recalculating historical data. This effectively solves the technical problem in existing client-based network synchronization methods where the main synchronization client disconnects, causing interruption of operation and inability to accurately restore the execution status, and ensures the continuity of the network synchronization system. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 A flowchart of a network disconnection reconstruction method that meets network synchronization requirements according to an embodiment of this application; Figure 2 This is a block diagram of a network disconnection reconstruction system that meets network synchronization requirements according to an embodiment of this application. Detailed Implementation

[0018] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0019] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0020] This application provides a network disconnection reconstruction method that meets network synchronization requirements and is applied to multiple clients participating in network synchronization. In this method, one of the multiple clients is designated as the primary synchronization client, and the remaining clients are designated as ordinary synchronization clients.

[0021] As can be seen from the above, the application basis and operating environment of the network disconnection reconstruction method of this application are as follows: in a network synchronization system involving multiple clients, a "master-slave architecture" mode is adopted, that is, one client is selected from all clients as the master synchronization client, and the rest are ordinary synchronization clients. The master synchronization client is responsible for centrally executing synchronization logic calculations and distributing data, while the ordinary synchronization clients receive and apply the results calculated by the master synchronization client.

[0022] Specifically, for each synchronization cycle: the primary synchronization client and each ordinary synchronization client collect their local input data, and each ordinary synchronization client sends its local input data to the primary synchronization client; the primary synchronization client receives the local input data sent by each ordinary synchronization client, and performs synchronization logic calculations based on the local input data sent by each ordinary synchronization client and the primary synchronization client's local input data to obtain the data to be synchronized; the primary synchronization client sends the data to be synchronized to each ordinary synchronization client; the primary synchronization client applies the data to be synchronized locally, and each ordinary synchronization client receives the data to be synchronized and applies it locally.

[0023] Taking network synchronization for games as an example, local input data includes, but is not limited to, a series of data such as skill logic, character basic attacks, character attributes, character damage, character movement, collision, etc. The data to be synchronized includes, but is not limited to, a series of data such as which characters released which skills, the direction of skill release, character attribute changes, character movement position and direction, etc. The main synchronization client and each ordinary synchronization client apply the data to be synchronized locally, including but not limited to, playing skill effects, playing hit effects, displaying attribute changes, and performing character movement, etc.

[0024] In this network synchronization scheme, synchronization logic calculations are centralized in the main synchronization client, eliminating the need for a dedicated server and effectively reducing system architecture complexity and operational costs. It also avoids discrepancies in synchronization logic calculations caused by differences in hardware platforms or floating-point operations among clients, thus ensuring consistent synchronization results. The main synchronization client then sends the data to be synchronized to each ordinary synchronization client. Each ordinary synchronization client only needs to upload its local input data and apply the received data locally, simplifying the development and debugging process and improving efficiency.

[0025] See Figure 1Based on the aforementioned network synchronization scheme, this application provides a network disconnection reconstruction method that meets network synchronization requirements. This method allows a newly selected primary synchronization client to quickly resume the execution process of each logical module based on synchronized public data when an abnormal disconnection occurs at the primary synchronization client, thereby ensuring the continuity of the entire network synchronization system. This network disconnection reconstruction method, which meets network synchronization requirements, includes the following steps: S100: The content to be produced is pre-divided into multiple independently operable logical modules according to their logical functions; S200: During the network synchronization operation, the main synchronization client performs synchronization logic calculations based on multiple logic modules, and uses the progress data of each logic module generated during the calculation as common data to synchronize to each ordinary synchronization client in real time. The progress data is determined based on the completion status of multiple key nodes within each logic module. S300: When the primary synchronization client disconnects, a new primary synchronization client is determined from multiple ordinary synchronization clients and used as the primary synchronization client for reconstruction. S400: The primary synchronization client reconstructs the network disconnection based on the completion status of each logical module by identifying the completion status of each logical module.

[0026] In S100, the content to be created is predefined during the development phase; it is the overall business logic that the main synchronization client needs to execute during operation. Typically, the content to be created is treated as a whole and participates in the synchronization logic calculation. The main synchronization client runs this complete logic without internal modularization. However, in this solution, the entire business logic is divided into multiple independent logical modules according to their logical functions. This modular division allows each logical module to independently advance its progress and synchronize its state during runtime. Furthermore, during a disconnection and reconstruction, each module can independently perform recovery operations based on its own progress data, without interfering with each other.

[0027] During the content creation phase, the overall business logic is divided into multiple independent logical modules based on functionality. Each logical module adopts a linear design, meaning that the operation flow within the logical module must proceed sequentially according to preset key nodes to ensure the determinism of the execution order. However, there are no strict constraints on the relationships between modules. Developers can flexibly configure them according to actual needs, designing them as either linear dependencies (one module can only trigger another after it is completed) or concurrent execution (multiple modules run independently at the same time without affecting each other).

[0028] In this embodiment, the granularity of module segmentation of the production content can be flexibly set according to actual needs. Generally speaking, the granularity of module segmentation affects the accuracy and effect of disconnection reconstruction. The finer the production content is segmented, the simpler the business logic carried by each logical module, and the more accurate its progress status, thereby reducing the state deviation after reconstruction.

[0029] Each logical module contains multiple key nodes. In this embodiment, the granularity of these key nodes can be flexibly set according to actual needs. Specifically, the linear operation flow within a logical module is broken down into sufficiently detailed key nodes, each corresponding to a clear completion status and observable result data. When reconnection occurs, the new master synchronization client, based on the progress data recorded in the public data, can accurately identify the specific step in the current progress of each logical module, rather than simply knowing that the module is in the general "incomplete" range. The finer the division of key nodes, the more accurate the progress positioning, and the smaller the deviation from the pre-disconnection state when subsequent execution resumes from an uncompleted node.

[0030] In S200, during network synchronization operations, the primary synchronization client acts as the core computing node, executing synchronized logical calculations based on multiple pre-defined logical modules. Within each synchronization cycle, the primary synchronization client runs the execution logic of each logical module, recording the progress data within each module in real time. This progress data reflects the completion status of multiple key nodes within each logical module. By breaking down the entire execution process of a logical module into multiple sequentially arranged key nodes, the current progress of the logical module is represented by the proportion or position of these key nodes that have been completed, allowing the operational status of the logical module to be quantitatively expressed through the completion status of these key nodes.

[0031] Meanwhile, the progress data is shared and synchronized in real time to all ordinary synchronization clients, enabling each ordinary synchronization client to maintain progress information consistent with the main synchronization client, thereby providing a real-time and usable progress basis for disconnection reconstruction.

[0032] It should be noted that public data does not include all data generated during the operation of the logic module, but only information that must be synchronized to other ordinary clients. Typically, the data publicly disclosed by each logic module is set to a limited representation, that is, only involving necessary information related to the module's current progress.

[0033] In one exemplary embodiment of this application, the common data also includes key node results, which characterize the business status data generated when a key node in the logic module finishes running. Key node results are generated after any key node in the logic module completes its operation. By synchronizing these results as part of the common data to all clients, the primary synchronization client can directly obtain this result information during reconstruction from a lost connection, without needing to recalculate or compensate, ensuring that the module state after reconstruction is consistent with that before the connection failure.

[0034] In one exemplary embodiment of this application, each logical module further includes temporary data and internal data; the master synchronization client can also synchronize the temporary data and internal data generated during the calculation process to each ordinary synchronization client.

[0035] For example, temporary data is data related to rendering or vision, while internal data is business information used internally by the logic module but not publicly disclosed, such as unverified intermediate calculation results. In some application scenarios, the primary synchronization client can synchronize this type of data to ordinary synchronization clients as needed to achieve more refined intermediate state restoration or assist in debugging. However, this is not a necessary operation and depends on the developer's actual configuration requirements.

[0036] While the main synchronization client is running its logic, each logic module records the progress of its internal linear operations. Common data is inevitably synchronized across the network, meaning other ordinary synchronization clients also have access to the progress and key node results of each logic module. This provides a complete progress record for reconnection, allowing any ordinary client selected as the new main client to directly and accurately resume the execution process before the disconnection based on the synchronized common data, thus improving the efficiency and accuracy of reconnection.

[0037] In S300, when the primary synchronization client goes offline, a new client needs to be selected from among the multiple currently online regular synchronization clients to take over the role of the primary synchronization client. This selected client is the primary synchronization client to be rebuilt. This process ensures that even if the core computing node unexpectedly exits during network synchronization, the entire system can still quickly resume operation.

[0038] In this embodiment, if the primary synchronization client crashes or disconnects, one of the remaining ordinary synchronization clients can be selected as the new ordinary synchronization client and rebuilt. The logic that needs to run exists on all ordinary synchronization clients, but it is not running. The new primary synchronization client only needs to start rebuilding to successfully complete the conversion. That is, each client has the ability to perform synchronization logic calculations, and the primary synchronization client and each ordinary synchronization client have pre-configured the running logic of each logic module. When the primary synchronization client crashes or disconnects, rebuilding the primary synchronization client can activate the locally pre-configured running logic.

[0039] Therefore, without any additional restrictions, any ordinary synchronization client can seamlessly take over the role of the main synchronization client, directly restore the execution process of each logical module based on existing data, complete the reconstruction, and maintain the continuous operation of the entire network synchronization system.

[0040] In S400, specifically, the completion status of each logical module is identified based on common data, and the network disconnection reconstruction steps are performed based on the completion status of each logical module. Specifically, for each logical module, the reconstruction master synchronization client determines the completion status of the logical module based on the corresponding progress data; when the logical module is in a completed state, its completed state is maintained; when the logical module is in an incomplete state, multiple key nodes that have not yet been completed are identified based on the corresponding progress data, and the execution progress is advanced to the target progress from the starting point of the multiple key nodes that have not yet been completed.

[0041] The rebuilt master synchronization client independently performs recovery operations on each logical module, and the recovery processes of each logical module do not interfere with or depend on each other. For completed modules, their completed state is maintained directly without restarting; for incomplete modules, based on their current progress, the execution process of the module is advanced to the target progress by simulating user operations, that is, the target position that each incomplete logical module should have reached before the disconnection.

[0042] During the module's internal reconstruction process, it can be further optimized to start execution directly from the critical nodes that are not yet completed, rather than simulating the entire module process from scratch. This optimization requires each critical node to have a clear completion result as an identifier. Therefore, it can avoid repeatedly executing completed critical nodes, and only simulate the remaining unfinished operations, thus improving the efficiency of disconnection reconstruction.

[0043] This application employs a modular design within a master-slave network synchronization framework, significantly improving the efficiency and accuracy of post-disconnection reconstruction. Each logical module independently maintains its progress data, enabling the reconstruction master synchronization client to accurately locate the current progress of each logical module based on synchronized common data after a disconnection, without needing to roll back or recalculate. It can then directly resume execution from the starting point of multiple incomplete key nodes, effectively avoiding redundant calculations and state deviations. Furthermore, the independent recovery mechanism between logical modules and the configurability of key node granularity further optimize the flexibility and accuracy of reconstruction. Therefore, this application not only simplifies the development and debugging process of network synchronization systems but also enhances the robustness and continuity of the system in complex network environments.

[0044] Based on the same inventive concept, this application also provides a network disconnection reconstruction system that meets network synchronization requirements. The solution provided by this system is similar to the solution described in the above method. Therefore, the specific limitations of one or more embodiments of the network disconnection reconstruction system that meet network synchronization requirements provided below can be found in the limitations of the network disconnection reconstruction method that meets network synchronization requirements described above, and will not be repeated here.

[0045] See Figure 2 This application provides a network disconnection reconstruction system that meets network synchronization requirements, comprising: Logical partitioning units are used to pre-divide the content to be produced into multiple independently operable logical modules according to their logical functions; The synchronous computing unit is used to enable the main synchronous client to perform synchronous logical calculations based on multiple logical modules during network synchronous calculations, and to use the progress data of each logical module generated during the calculation process as common data to synchronize to each ordinary synchronous client in real time. The progress data is determined based on the completion status of multiple key nodes within each logical module. The Reconstruct Selected Unit is used to determine a new primary synchronization client from multiple ordinary synchronization clients when the primary synchronization client goes offline, and to serve as the primary synchronization client for reconstruction. The progress advance unit is used to enable the reconstruction master synchronization client to identify the completion status of each logical module based on common data, and to perform network disconnection reconstruction based on the completion status of each logical module.

[0046] In this embodiment, the progress advancement unit includes a state identification subunit and an execution subunit. For each logical module, the state identification subunit is used to enable the reconstruction master synchronization client to determine the completion status of the logical module based on the corresponding progress data. The execution subunit is used to maintain the completion status of the logical module when it is in a completed state, and to identify multiple key nodes that have not yet been completed based on the corresponding progress data when the logical module is in an incomplete state, so as to advance the execution progress to the target progress from the starting point of the multiple key nodes that have not yet been completed.

[0047] In this embodiment of the application, the public data also includes key node results, which are used to characterize the business status data generated when the key nodes in the logic module finish running.

[0048] The results of critical nodes are generated after any critical node of the logic module has been completed. By synchronizing these results to all clients as part of the common data, the main synchronization client can directly obtain these results during the reconstruction of the disconnection without recalculation or compensation, ensuring that the module state after reconstruction is consistent with that before the disconnection.

[0049] In this embodiment of the application, each logical module further includes temporary data and internal data; the master synchronization client can also synchronize the temporary data and internal data generated during the calculation process to each ordinary synchronization client.

[0050] For example, temporary data is data related to rendering or vision, while internal data is business information used internally by the logic module but not publicly disclosed, such as unverified intermediate calculation results. In some application scenarios, the primary synchronization client can synchronize this type of data to ordinary synchronization clients as needed to achieve more refined intermediate state restoration or assist in debugging. However, this is not a necessary operation and depends on the developer's actual configuration requirements.

[0051] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0052] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. Furthermore, those skilled in the art will recognize that, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for reconstructing a network disconnection that meets network synchronization requirements, characterized in that, This method is applied to multiple clients participating in network synchronization, wherein one of the multiple clients is designated as the primary synchronization client, and the remaining clients are designated as ordinary synchronization clients; the network disconnection reconstruction method that meets network synchronization requirements includes: The content to be produced is pre-divided into multiple independently operable logical modules according to their logical functions; During the network synchronization operation, the main synchronization client performs synchronization logic calculations based on multiple logic modules, and uses the progress data of each logic module generated during the calculation as common data to synchronize to each ordinary synchronization client in real time. The progress data is determined based on the completion status of multiple key nodes within each logic module. When the primary synchronization client disconnects, a new primary synchronization client is determined from among the multiple ordinary synchronization clients and used as the primary synchronization client for reconstruction. The reconstruction master synchronization client identifies the completion status of each logical module based on the public data, and performs network disconnection reconstruction based on the completion status of each logical module.

2. The network disconnection reconstruction method that meets network synchronization requirements according to claim 1, characterized in that, The step of identifying the completion status of each logical module based on the public data, and performing network disconnection reconstruction based on the completion status of each logical module, specifically includes: For each logical module, the reconstruction master synchronization client determines the completion status of the logical module based on the corresponding progress data; When the logic module is in a completed state, it remains in a completed state. When the logic module is in an incomplete state, multiple key nodes that have not yet been completed are identified based on the corresponding progress data, and the execution progress is advanced to the target progress from the starting point of the multiple key nodes that have not yet been completed.

3. The network disconnection reconstruction method that meets network synchronization requirements according to claim 1, characterized in that, The public data also includes key node results, which are used to characterize the business status data generated when the key node in the logic module finishes running.

4. The network disconnection reconstruction method that meets network synchronization requirements according to claim 1, characterized in that, Each of the aforementioned logical modules also includes temporary data and internal data during runtime; The primary synchronization client can also synchronize the temporary data and internal data generated during the calculation process to each of the ordinary synchronization clients.

5. The network disconnection reconstruction method that meets network synchronization requirements according to claim 1, characterized in that, The multiple logical modules are configured to execute linearly or concurrently.

6. The network disconnection reconstruction method that meets network synchronization requirements according to claim 1, characterized in that, Each of the aforementioned clients possesses synchronous logic computation capabilities, and the main synchronous client and each of the ordinary synchronous clients have their respective logic modules pre-configured for operation.

7. A network disconnection reconstruction system that meets network synchronization requirements, characterized in that, The network disconnection reconstruction system, which is applied to multiple clients participating in network synchronization, designates one of the multiple clients as the primary synchronization client and the remaining clients as ordinary synchronization clients. The system includes: Logical partitioning units are used to pre-divide the content to be produced into multiple independently operable logical modules according to their logical functions; The synchronization calculation unit is used to enable the main synchronization client to perform synchronous logical calculations based on multiple logical modules during network synchronization calculations, and to synchronize the progress data of each logical module generated during the calculation process as common data to each ordinary synchronization client in real time. The progress data is determined based on the completion status of multiple key nodes within each logical module. The re-selection unit is used to determine a new primary synchronization client from among the multiple ordinary synchronization clients when the primary synchronization client goes offline, and to serve as the re-reconstructed primary synchronization client. The progress advancement unit is used to enable the reconstruction master synchronization client to identify the completion status of each of the logical modules based on the public data, and to perform network disconnection reconstruction based on the completion status of each of the logical modules.

8. The network disconnection reconstruction system that meets network synchronization requirements according to claim 7, characterized in that, The progress advancement unit includes a status identification subunit and an execution subunit; For each logical module, the status identification subunit is used to enable the reconstruction master synchronization client to determine the completion status of the logical module based on the corresponding progress data; The execution subunit is used to maintain the completed state when the logic module is in a completed state, and to identify multiple key nodes that have not yet been completed based on the corresponding progress data when the logic module is in an incomplete state, so as to advance the execution progress to the target progress from the starting point of the multiple key nodes that have not yet been completed.

9. The network disconnection reconstruction system that meets network synchronization requirements according to claim 7, characterized in that, The public data also includes key node results, which are used to characterize the business status data generated when the key node in the logic module finishes running.

10. The network disconnection reconstruction system that meets network synchronization requirements according to claim 7, characterized in that, Each of the aforementioned logical modules also includes temporary data and internal data; The primary synchronization client can also synchronize the temporary data and internal data generated during the calculation process to each of the ordinary synchronization clients.

Images