A cloud-based method for real-time synchronization of file operations and a cloud server

Abstract

The application discloses a cloud-based file operation real-time synchronization method and a cloud server, real-time acquisition of first operation instructions for target cloud storage files is performed by each client; for each client, the first operation instructions of the same type are continuously merged to obtain second operation instructions; priority calculation is performed on the second operation instructions obtained by merging; and the second operation instructions are cloud-persisted and synchronized to the client according to the priority of each second operation instruction; the first operations of the same type of the client are merged, the operation synchronization efficiency is improved, the priority calculation is performed on the second operation after merging, the cloud persistence and synchronization to the client of the second operation are performed according to the priority, the cloud persistence of the operation instruction can effectively record the operation history of the user, and a more fine-grained operation tracking and rollback mechanism can be realized, and more perfect version update management can be provided.

Description

Technical Field

[0001] This invention relates to the field of cloud computing technology, and more specifically to a method for real-time synchronization of file operations based on the cloud and a cloud server. Background Technology

[0002] Currently, most common cloud storage synchronization solutions on the market use timed polling or file change-triggered synchronization methods. For example, Dropbox uses file system monitoring to detect local file changes, and OneDrive uses timed scanning to check for file updates. These solutions primarily focus on synchronizing file addition, deletion, and modification operations.

[0003] In current technology, file editing operations (such as scaling, cropping, 3D rotation, etc.) are often handled with overwrite updates, resulting in the loss of operation history. This easily leads to version conflicts during multi-user collaborative editing, and the resolution mechanism is not perfect, lacking fine-grained operation tracking and rollback mechanisms.

[0004] Therefore, a real-time file operation synchronization solution that can provide more comprehensive version update management is needed. Summary of the Invention

[0005] The technical problem to be solved by this invention is to provide a method and cloud server for real-time synchronization of file operations based on the cloud, which can provide more comprehensive version update management.

[0006] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is as follows: A method for real-time file operation synchronization based on the cloud, including the following steps: S1. Real-time acquisition of the first operation instructions for the target cloud storage file from each client listening and capturing; S2. For each client, merge consecutive first operation instructions of the same type to obtain a second operation instruction; S3. Calculate the priority of the merged second operation instruction; S4. Based on the priority of each of the second operation instructions, persist the second operation instructions to the cloud and synchronize them to the client.

[0007] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is as follows: A cloud server includes a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of the cloud-based real-time file operation synchronization method described above.

[0008] The beneficial effects of this invention are as follows: The method for real-time synchronization of file operations based on the cloud and the cloud server of this invention merges the first operations of the same type and consecutively on the client, thereby improving the efficiency of operation synchronization. Furthermore, the method performs priority calculation on the merged second operations and performs cloud persistence and synchronization to the client based on the priority. The cloud persistence based on operation instructions can effectively record the user's operation history and can realize a more granular operation tracking and rollback mechanism, thereby providing more complete version update management. Attached Figure Description

[0009] Figure 1 This is a simplified flowchart illustrating a method for real-time synchronization of file operations based on the cloud, according to an embodiment of the present invention. Figure 2 This is a structural example diagram of a cloud server according to an embodiment of the present invention; Figure 3 This is an interactive example diagram of a cloud-based real-time file operation synchronization method according to an embodiment of the present invention; Label Explanation: 1. A cloud server; 2. A processor; 3. A memory. Detailed Implementation

[0010] To explain in detail the technical content, objectives, and effects of the present invention, the following description is provided in conjunction with the embodiments and accompanying drawings.

[0011] Please refer to Figure 1 as well as Figure 3 A method for real-time synchronization of file operations based on the cloud, comprising the following steps: S1. Real-time acquisition of the first operation instructions for the target cloud storage file from each client listening and capturing; S2. For each client, merge consecutive first operation instructions of the same type to obtain a second operation instruction; S3. Calculate the priority of the merged second operation instruction; S4. Based on the priority of each of the second operation instructions, persist the second operation instructions to the cloud and synchronize them to the client.

[0012] As can be seen from the above description, the beneficial effects of the present invention are as follows: The present invention provides a cloud-based method for real-time synchronization of file operations, which merges similar consecutive first operations on the client to improve the efficiency of operation synchronization. Furthermore, it performs priority calculation on the merged second operations, and performs cloud persistence and synchronization to the client based on the priority. Cloud persistence based on operation instructions can effectively record the user's operation history and can realize a more granular operation tracking and rollback mechanism, and can provide more complete version update management.

[0013] Furthermore, merging consecutive first operation instructions of the same type includes: For consecutive scaling operations, obtain the final scaling ratio; For consecutive rotation operations, obtain the accumulated rotation angle; For continuous movement operations, calculate the net displacement; Obtain the final filter parameters from a series of filter operations.

[0014] As described above, merging consecutive operations of the same type, including but not limited to scaling, rotation, movement, and filter adjustment, can preserve the purpose of the operation while avoiding unnecessary operation synchronization, thus improving the efficiency of operation synchronization and saving network resources.

[0015] Furthermore, the steps between step S2 and step S3 include: S21. Perform dependency analysis and invalid operation filtering on the second operation instruction.

[0016] As described above, dependency analysis and invalid operation filtering are performed on the second operation instruction to further improve the synchronization efficiency of the operation instructions.

[0017] Furthermore, the dependency analysis described in step S21 includes the following steps: Construct an operation dependency graph, wherein the operation dependency graph uses the second operation instruction as a node, and establishes connection lines between nodes according to the dependency relationship between the second operation instructions; Based on the operation dependency graph, the second operation instructions that modify the same region differently at the same time are identified as mutually exclusive operations, and circular dependency detection is performed.

[0018] As described above, an operation dependency graph is constructed, and mutual exclusion operations and operations with circular dependencies are detected based on the operation dependency graph.

[0019] Furthermore, the invalid operation in step S21 includes the second operation instruction that is overridden by subsequent operations, the second operation instructions whose final effects cancel each other out, and the second operation instruction that exceeds its scope of application.

[0020] As can be seen from the above description, operations that are covered, mutually canceled, or cannot take effect beyond their scope are considered invalid operations.

[0021] Furthermore, step S3 specifically includes: Factors involved in prioritizing the second operation instruction include operation type, scope of operation impact, timeliness of operation, and user permissions.

[0022] As described above, the factors to be considered in priority calculation include operation type, scope of operation impact, timeliness of operation, and user permissions, to ensure the effectiveness of priority calculation.

[0023] Furthermore, the priority is calculated as follows: priority=baseWeight×scopeFactor×timeFactor×userWeight; Among them, priority represents priority; baseWeight represents the basic weight of the operation, which is determined according to the operation type; scopeFactor represents the scope of influence coefficient, which is determined according to the scope of the operation's influence; timeFactor represents the time decay coefficient, which decreases from the initial value over time and is not less than 0; and userWeight represents the user weight coefficient, which is determined according to the user's permissions.

[0024] As described above, the final priority of an operation instruction is determined based on the basic weight of the operation type, combined with the influence range coefficient, time decay coefficient, and user weight coefficient.

[0025] Further, step S4 includes the following steps: The second operation instructions are sorted according to priority; Based on the priority sorting results, an operation batch is constructed for the third operation instruction whose priority exceeds a preset threshold in the second operation instruction. The operation batch includes the third operation instruction, the second operation instruction corresponding to the subordinate operation associated with the third operation instruction, and the second operation instruction corresponding to the context operation necessary to execute the third operation instruction. Based on the priority order and in conjunction with the preset synchronization strategy, the operation batches and the second operation instructions are synchronized to the client, wherein a synchronization interval is set for the synchronization of every two operation batches.

[0026] As described above, the operation batch and the second operation instruction are synchronized according to the priority order and the preset synchronization strategy. At the same time, the synchronization of the operation batch is spaced out to avoid network congestion and improve the synchronization efficiency.

[0027] Furthermore, the preset synchronization strategy is an incremental synchronization strategy; The incremental synchronization strategy includes selective synchronization based on the scope of operational impact.

[0028] As can be seen from the above description, adopting an incremental synchronization strategy, while selectively synchronizing based on the scope of operational impact, effectively improves the efficiency of operational synchronization.

[0029] Please refer to Figure 2A cloud server includes a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of the above-described method for real-time synchronization of file operations based on a cloud.

[0030] As can be seen from the above description, the beneficial effects of the present invention are as follows: The cloud server of the present invention merges the first operations of the same type and consecutively performed by the client, thereby improving the efficiency of operation synchronization. Furthermore, it performs priority calculation on the merged second operations, and performs cloud persistence and synchronization to the client based on the priority. The cloud persistence based on operation instructions can effectively record the user's operation history and can realize a more granular operation tracking and rollback mechanism, thereby providing more complete version update management.

[0031] The present invention provides a method and cloud server for real-time synchronization of file operations based on the cloud, which is suitable for multi-terminal collaborative processing of cloud files.

[0032] Please refer to Figure 1 and Figure 3 Embodiment 1 of the present invention is as follows: A method for real-time file operation synchronization based on the cloud, including the following steps: S1. Real-time acquisition of the first operation commands for the target cloud storage file from each client's listening and capture.

[0033] In this embodiment, it can be referred to Figure 3 An Operation Capture module is built in the client to capture the user's first operation command on the target cloud storage file and synchronize the operation command to the WebSocket service of the cloud server through the SyncEngine synchronization engine.

[0034] The cloud server receives and obtains the first operation instructions from each client through the WebSocket service.

[0035] S2. For each client, merge consecutive first operation instructions of the same type to obtain a second operation instruction; Merging consecutive first operation instructions of the same type includes: For consecutive scaling operations, obtain the final scaling ratio; For consecutive rotation operations, obtain the accumulated rotation angle; For continuous movement operations, calculate the net displacement; Obtain the final filter parameters from a series of filter operations.

[0036] In this embodiment, the first operation instruction includes, but is not limited to, scaling, cropping, and 3D rotation. An intelligent operation compressor mechanism is established to merge consecutive similar operations (such as multiple scaling operations) into a single optimized operation (i.e., the second operation instruction). The steps for merging operation instructions are as follows: Establish an operation buffer queue and set a time window (e.g., 500ms); Identify and group consecutive first operation instructions of the same type: { type: "scale", operations: [ {value: 0.8, timestamp: 1000}, {value: 0.9, timestamp: 1200}, {value: 1.2, timestamp: 1400} ] } Different merging strategies are used depending on the type of operation: Scaling operation: Get the final scaling ratio; Rotation operation: Accumulate rotation angle; Movement operation: Calculate net displacement; Filter operation: Preserve final parameters.

[0037] Preferably, in this embodiment, a further step is included between step S2 and step S3: S21. Perform dependency analysis and invalid operation filtering on the second operation instruction; The dependency analysis described in step S21 includes the following steps: Construct an operation dependency graph, wherein the operation dependency graph uses the second operation instruction as a node, and establishes connection lines between nodes according to the dependency relationship between the second operation instructions; Based on the operation dependency graph, the second operation instructions that modify the same region at the same time but with different modifications are identified as mutually exclusive operations, and circular dependency detection is performed. The invalid operations mentioned in step S21 include second operation instructions that are overridden by subsequent operations, second operation instructions whose final effects cancel each other out, and second operation instructions that are outside their scope of application.

[0038] In this embodiment, dependency analysis and invalid operation filtering are performed: Construct an operation dependency graph: nodes represent operations, and edges represent the dependencies between operations.

[0039] Perform dependency analysis: identify mutually exclusive operations (such as different modifications to the same region); detect circular dependencies (such as A depends on B, B depends on C, and C depends on A).

[0040] Invalid operation criteria: Operations that are completely overridden by subsequent operations, operation sequences whose final effects are negated, and operations that are outside the scope of their effect.

[0041] S3. Calculate the priority of the merged second operation instruction; Step S3 is as follows: Factors involved in prioritizing the second operation instruction include operation type, scope of operation impact, timeliness of operation, and user permissions; The priority is calculated as follows: priority=baseWeight×scopeFactor×timeFactor×userWeight; Among them, priority represents priority; baseWeight represents the basic weight of the operation, which is determined according to the operation type; scopeFactor represents the scope of influence coefficient, which is determined according to the scope of the operation's influence; timeFactor represents the time decay coefficient, which decreases from the initial value over time and is not less than 0; and userWeight represents the user weight coefficient, which is determined according to the user's permissions.

[0042] In this embodiment, the priority mechanism is implemented as follows: Priority calculation factors include: operation type weight (structural modification > visual effect modification); operation impact scope (global operation > local operation); operation timeliness (latest operation > historical operation); and user role weight. As an example, in the specific calculation of priority, these are reflected in the following order: baseWeight: basic operation weight (e.g., delete = 10, rotate = 5); scopeFactor: impact scope coefficient (global = 1.5, local = 1.0); timeFactor: time decay coefficient (decreases over time); and userWeight: user weight coefficient (administrator = 1.2, regular user = 1.0).

[0043] S4. Based on the priority of each of the second operation instructions, persist the second operation instructions to the cloud and synchronize them to the client; Step S4 includes the following steps: The second operation instructions are sorted according to priority; Based on the priority sorting results, an operation batch is constructed for the third operation instruction whose priority exceeds a preset threshold in the second operation instruction. The operation batch includes the third operation instruction, the second operation instruction corresponding to the subordinate operation associated with the third operation instruction, and the second operation instruction corresponding to the context operation necessary to execute the third operation instruction. Based on the priority order and combined with the preset synchronization strategy, the operation batches and the second operation instructions are synchronized to the client, wherein a synchronization interval is set for the synchronization of every two operation batches. The default synchronization strategy is incremental synchronization. The incremental synchronization strategy includes selective synchronization based on the scope of operational impact.

[0044] In this embodiment, the synchronization strategy is exemplified as follows: Sort by priority from highest to lowest; Build operation batches, each batch contains: Critical operations (priority > 8); Related subordinate operations; Necessary context operations.

[0045] Set appropriate synchronization intervals between batches to avoid network congestion.

[0046] This effectively reduces data transmission volume, improves synchronization efficiency, and ensures the accuracy and real-time performance of operations.

[0047] Incremental synchronization strategy: Introduce a hierarchical operation caching mechanism to maintain local cache, temporary cache and persistent cloud storage respectively; design a selective synchronization algorithm based on the scope of operation impact; implement an intelligent preloading mechanism to predict possible operations based on user behavior.

[0048] In this embodiment, the specific implementation steps of the selective synchronization algorithm based on the scope of operational influence are as follows: Operational impact scope analysis: Global operations: affect the entire file (such as scaling, filters); Region operations: affect a specific region (such as cropping or local modification); Attribute operations: only affect metadata (such as renaming, tagging).

[0049] Calculation of the scope of impact: { "operation": { "type": "crop", "affectedArea": ​​{ "x": 100, "y": 100, "width":500, "height":300 }, "impactLevel": "regional", "affectedLayers": ["layer1", "layer2"] } } Selective synchronization implementation steps: (1) Operation analysis stage: Calculate the scope of the operation's impact; determine the affected layers or components; Evaluate operation priorities; mark dependencies.

[0050] (2) Synchronization strategy formulation: Real-time synchronization: global critical operations, multi-user collaborative area operations, and high-priority operations.

[0051] Delayed synchronization: Local non-critical operations, operations in a single user's independent area, and low-priority operations.

[0052] (3) Perform synchronization: { "syncStrategy": { "type": "selective", "priority": "high", "syncTiming": "immediate", "dependencies": ["op_123", "op_124"], "cacheLevel": "temporary } } Layered caching collaboration: Local cache: stores operations in the current working area; Temporary cache: stores the queue of operations to be synchronized; Cloud storage: persists confirmed operations.

[0053] This embodiment provides an optimization mechanism, including: Batch processing: merging consecutive operations within the same region; batch submission of non-urgent operations. Intelligent scheduling: adjusting synchronization strategies based on network conditions; dynamically adjusting synchronization frequency. Conflict handling: detecting overlapping operation regions; resolving concurrent operation conflicts.

[0054] For implementation examples, please refer to: { "selectiveSyncConfig": { "immediateSync": { "conditions": [ "globalOperation", "collaborativeArea", "highPriority" ], "batchSize": 1, "retryStrategy": "immediate" }, "deferredSync": { "conditions": [ "localOperation", "singleUserArea", "lowPriority" ], "batchSize": 10, "syncInterval": 5000 } } } In this embodiment, the selective synchronization algorithm based on the scope of operational influence can effectively improve synchronization efficiency and reduce unnecessary data transmission.

[0055] Embodiment 2 of the present invention is as follows: A cloud-based method for real-time synchronization of file operations differs from Embodiment 1 in that it introduces a distributed version tree structure and an operation weight calculation model to automatically determine the importance of operations.

[0056] In this embodiment, the operation weight setting scheme is as follows: Weight calculation model design: operationWeight=baseWeight×impactFactor×timeFactor×userFactor×dependencyFactor; The base weight varies depending on the operation type, including structural operations: deletion: 10.0; cropping: 8.0; layer merging: 7.0. Visual effects operations: 3D rotation: 6.0; filters: 5.0; scaling: 4.0. Attribute operations: rename: 3.0; label modification: 2.0.

[0057] Impact Factor: Determined based on the impact of the operation on the target cloud file. Examples: Global impact: 1.5; Multi-layer impact: 1.3; Single-layer impact: 1.0; Local impact: 0.8.

[0058] Time Factor: timeFactor=1.0×Math.exp(-0.1×timeDiff); Wherein, timeDiff is the difference (in hours) between the operation and the current time.

[0059] User Factor: Determined based on the user's account type, for example: Administrator: 1.2; Project Manager: 1.1; Regular User: 1.0; Visitor: 0.8.

[0060] The dependency factor is determined based on the dependencies of an operation. For example, if there are n dependent operations: 1 + 0.1 × n; if there are no dependencies: 1.0.

[0061] Dynamic weight adjustment mechanism: { "weightAdjustment": { "conditions": { "frequentAccess": { "threshold": 10, "multiplier": 1.2 }, "conflictRate": { "threshold": 0.3, "multiplier": 1.3 }, "collaborativeEditing": { "threshold": 2, "multiplier": 1.1 } } } } Weight application example: { "operation": { "type": "crop", "timestamp": "2024-01-01T10:00:00Z", "user": "projectLead", "scope": "global", "dependencies": 2, "weightCalculation": { "baseWeight": 8.0, "impactFactor": 1.5, "timeFactor": 1.0, "userFactor": 1.1, "dependencyFactor": 1.2, "finalWeight": 15.84 } } } In this embodiment, the weighting strategy includes: synchronization priority judgment, conflict resolution priority, version merging decision, and operation rollback impact assessment.

[0062] Through this multi-dimensional weight calculation model, the system can accurately assess the importance of operations, providing a reliable basis for subsequent synchronization strategies, conflict handling, and version management. It enables intelligent version merging strategies, automatically integrates relevant versions, and supports conditional triggering and automatic management of version branches.

[0063] The second operation instruction is converted into a standardized operation description object, generating a unique identifier and timestamp.

[0064] Operation log synchronization: Establish a WebSocket long connection for real-time data transmission; use an incremental synchronization strategy to transmit only operation instructions rather than complete files; and employ a queue mechanism to handle concurrent operations.

[0065] Version control mechanism: Maintains the operation history tree structure; enables forward replay and backward rollback of operations; supports the restoration of any historical version.

[0066] Conflict handling: Concurrent operations are handled using operation transformation algorithms. Through semantic analysis and transformation of operations, the operation sequences from different terminals are ultimately made consistent. For example: { "Primary operation sequence": [ {"type": "scale", "value": 0.8}, {"type": "scale", "value": 0.9}, {"type": "scale", "value": 1.0} ], "After conversion": { "type": "scale_sequence", "start_value": 0.8, "final_value": 1.0, "optimization": "direct_transform" } } It enables automatic conflict detection and resolution, and provides a manual conflict handling interface.

[0067] In a typical collaborative work scenario, designer A uses computer software to edit product images, while designer B views and modifies the same file via a mobile device. The specific process is as follows: Designer A first scales the image by 50%, and the system immediately captures this operation and generates an operation description object: { "operationType": "scale", "params": {"ratio": 0.5}, "timestamp": "2023-12-20 10:30:15", "userId": "userA } The operation was pushed to the cloud in real time via WebSocket and broadcast to all online collaborators. Designer B's mobile device immediately received and executed the operation, maintaining consistency between the views on both ends.

[0068] Designer B then rotated the image 90 degrees in 3D, generating corresponding operation instructions and synchronizing them. The system automatically records all operation history, allowing users to revert to any previous version at any time.

[0069] For reference Figure 2 Embodiment 3 of the present invention is as follows: A cloud server 1 includes a processor 2, a memory 3, and a computer program stored in the memory 3 and executable on the processor 2. When the processor 2 executes the computer program, it implements the steps of the cloud-based file operation real-time synchronization method described in Embodiment 1 or 2 above.

[0070] In summary, the present invention provides a cloud-based method for real-time file operation synchronization. It merges consecutive first operations of the same type on the client side, improving the efficiency of operation synchronization. Furthermore, it calculates the priority of the merged second operations, and persists the second operations to the cloud and synchronizes them to the client based on the priority. Cloud persistence based on operation instructions effectively records the user's operation history and enables more granular operation tracking and rollback mechanisms, providing more comprehensive version update management.

[0071] This invention provides a cloud-based method and cloud server for real-time file operation synchronization, which significantly improves the real-time performance of file operations, allowing users to instantly see the modifications made by collaborators; it greatly reduces the amount of data transmission, synchronizing only operation instructions rather than the entire file; it provides complete operation history tracking and version rollback capabilities; an intelligent conflict handling mechanism ensures the stability of multi-user collaboration; and fine-grained operation control enhances the user experience.

[0072] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent modifications made based on the content of the present invention specification and drawings, or direct or indirect applications in related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A method for real-time synchronization of file operations based on the cloud, characterized in that, Including the following steps: S1. Real-time acquisition of the first operation instructions for the target cloud storage file from each client listening and capturing; S2. For each client, merge consecutive first operation instructions of the same type to obtain a second operation instruction; S3. Calculate the priority of the merged second operation instruction; S4. Based on the priority of each of the second operation instructions, persist the second operation instructions to the cloud and synchronize them to the client.

2. The method for real-time synchronization of file operations based on the cloud according to claim 1, characterized in that, Merging consecutive first operation instructions of the same type includes: For consecutive scaling operations, obtain the final scaling ratio; For consecutive rotation operations, obtain the accumulated rotation angle; For continuous movement operations, calculate the net displacement; Obtain the final filter parameters from a series of filter operations.

3. The method for real-time synchronization of file operations based on the cloud according to claim 1, characterized in that, The steps between step S2 and step S3 include: S21. Perform dependency analysis and invalid operation filtering on the second operation instruction.

4. The method for real-time synchronization of file operations based on the cloud according to claim 3, characterized in that, The dependency analysis described in step S21 includes the following steps: Construct an operation dependency graph, wherein the operation dependency graph uses the second operation instruction as a node, and establishes connection lines between nodes according to the dependency relationship between the second operation instructions; Based on the operation dependency graph, the second operation instructions that modify the same region differently at the same time are identified as mutually exclusive operations, and circular dependency detection is performed.

5. The method for real-time synchronization of file operations based on the cloud according to claim 3, characterized in that, The invalid operations mentioned in step S21 include second operation instructions that are overridden by subsequent operations, second operation instructions whose final effects cancel each other out, and second operation instructions that are outside their scope of application.

6. The method for real-time synchronization of file operations based on the cloud according to claim 1, characterized in that, Step S3 is as follows: Factors involved in prioritizing the second operation instruction include operation type, scope of operation impact, timeliness of operation, and user permissions.

7. The method for real-time synchronization of file operations based on the cloud according to claim 6, characterized in that, The priority is calculated as follows: priority=baseWeight×scopeFactor×timeFactor×userWeight; Among them, priority represents priority; baseWeight represents the basic weight of the operation, which is determined according to the operation type; scopeFactor represents the scope of influence coefficient, which is determined according to the scope of the operation's influence; timeFactor represents the time decay coefficient, which decreases from the initial value over time and is not less than 0; and userWeight represents the user weight coefficient, which is determined according to the user's permissions.

8. The method for real-time synchronization of file operations based on the cloud according to claim 1, characterized in that, Step S4 includes the following steps: The second operation instructions are sorted according to priority; Based on the priority sorting results, an operation batch is constructed for the third operation instruction whose priority exceeds a preset threshold in the second operation instruction. The operation batch includes the third operation instruction, the second operation instruction corresponding to the subordinate operation associated with the third operation instruction, and the second operation instruction corresponding to the context operation necessary to execute the third operation instruction. Based on the priority order and in conjunction with the preset synchronization strategy, the operation batches and the second operation instructions are synchronized to the client, wherein a synchronization interval is set for the synchronization of every two operation batches.

9. The method for real-time synchronization of file operations based on the cloud according to claim 8, characterized in that, The default synchronization strategy is incremental synchronization. The incremental synchronization strategy includes selective synchronization based on the scope of operational impact.

10. A cloud server, comprising a processor, a memory, 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 steps of the cloud-based real-time file operation synchronization method as described in any one of claims 1-9.

Images