Cross-platform remote file synchronization method and device and related medium

Abstract

The invention discloses a cross-platform remote file synchronization method and device and a related medium, and the method comprises the steps: obtaining and analyzing a file synchronization instruction, and obtaining synchronization request data; creating a synchronization session object in the cross-platform server based on the synchronization request data, and performing resource allocation processing to obtain session management data; performing fragmentation strategy determination processing on the synchronization request data by using the session management data to generate a synchronization metadata object; constructing a session transmission queue based on the synchronous metadata object, and scheduling and sending the session transmission queue to obtain a cross-platform fragmented transmission data set; performing file recombination processing on the cross-platform client based on the cross-platform fragmented transmission data set to generate a recombination file object, and generating synchronization result notification data according to the recombination file object, according to the method and the device, the received fragmented data is subjected to file recombination at the cross-platform client to generate the recombined file object, and the synchronization result notification data is output, so that the data security during remote file synchronization is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and particularly relates to a cross-platform remote file synchronization method and device and related media. BACKGROUND

[0002] With the wide application of cloud computing and distributed systems, operation and maintenance personnel need to frequently download files on remote servers to the local environment for log analysis, configuration backup, program distribution and other operations in daily work. However, in the prior art, the commonly used remote file transmission tools usually only rely on the basic verification of the underlying transmission protocol or the simple transmission completion mark to determine whether the transmission is completed, and the integrated session management and end-to-end forced integrity verification mechanism for cross-platform clients and remote servers have not been established.

[0003] Especially in the scene of complex network environment, multi-hop link transmission or long-time continuous transmission, once the remote file is tampered with in the transmission process, it will be difficult for the user to discover the data error in time, and the data security is low. SUMMARY

[0004] Embodiments of the present application provide a cross-platform remote file synchronization method, device and related media, aiming to solve the technical problem of low data security in remote file synchronization in the prior art.

[0005] In a first aspect, the embodiments of the present application provide a cross-platform remote file synchronization method, comprising: obtaining a file synchronization instruction triggered in a cross-platform client, and parsing the file synchronization instruction to obtain synchronization request data; creating a synchronization session object in a cross-platform server based on the synchronization request data, performing resource allocation processing on the synchronization session object to obtain session management data; performing slice strategy determination processing on the synchronization request data using the session management data to generate a synchronization metadata object; constructing a session transmission queue based on the synchronization metadata object, and scheduling and sending the slice data in the session transmission queue to obtain a cross-platform slice transmission data set; performing file reorganization processing on the cross-platform client based on the cross-platform slice transmission data set to generate a reorganized file object, and generating synchronization result notification data according to the reorganized file object.

[0006] In a second aspect, the embodiments of the present application provide a cross-platform remote file synchronization device, comprising: a data acquisition unit configured to obtain a file synchronization instruction triggered in a cross-platform client, and parse the file synchronization instruction to obtain synchronization request data; a resource allocation unit configured to create a synchronization session object in a cross-platform server based on the synchronization request data, perform resource allocation processing on the synchronization session object, and obtain session management data; a data synchronization unit configured to perform sharding strategy determination processing on the synchronization request data using the session management data, and generate a synchronization metadata object; a scheduling sending unit configured to construct a session transmission queue based on the synchronization metadata object, perform scheduling sending on the sharding data in the session transmission queue, and obtain a cross-platform sharding transmission data set; a data output unit configured to perform file reorganization processing on the cross-platform sharding transmission data set in the cross-platform client to generate a reorganized file object, and generate synchronization result notification data according to the reorganized file object.

[0007] In a third aspect, an embodiment of the present application provides a computer device, which comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the cross-platform remote file synchronization method of the first aspect when executing the computer program.

[0008] In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program is executable on a processor to implement the cross-platform remote file synchronization method of the first aspect.

[0009] The embodiment of the present application provides a cross-platform remote file synchronization method, which comprises obtaining a file synchronization instruction triggered in a cross-platform client, analyzing the file synchronization instruction to obtain synchronization request data, creating a synchronization session object in a cross-platform server based on the synchronization request data, performing resource allocation processing on the synchronization session object to obtain session management data, performing sharding strategy determination processing on the synchronization request data using the session management data to generate a synchronization metadata object, constructing a session transmission queue based on the synchronization metadata object, performing scheduling sending on the sharding data in the session transmission queue to obtain a cross-platform sharding transmission data set, performing file reorganization processing on the cross-platform sharding transmission data set in the cross-platform client to generate a reorganized file object, and generating synchronization result notification data according to the reorganized file object. The embodiment of the present application generates a reorganized file object by performing file reorganization on the received sharding data in the cross-platform client and outputs synchronization result notification data, thereby improving the data security during remote file synchronization.

[0010] The embodiment of the present application also provides a cross-platform remote file synchronization device, a computer device, and a storage medium, which also have the beneficial effects described above. BRIEF DESCRIPTION OF DRAWINGS

[0011] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments will be briefly introduced. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0012] Figure 1 A flowchart of a cross-platform remote file synchronization method provided by an embodiment of the present application is shown in the figure. Figure 2 A schematic block diagram of a cross-platform remote file synchronization device provided by an embodiment of the present application is shown in the figure. DETAILED DESCRIPTION

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

[0014] It should be understood that when used in the specification and the appended claims, the terms "comprise" and "comprising" indicate the presence of the described features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0015] It should also be understood that the terms used in the present application specification are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in the present application specification and the appended claims, the singular forms "a", "an" and "the" are intended to include the plural forms unless the context clearly indicates otherwise.

[0016] It should be further understood that the term "and / or" used in the present application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes these combinations.

[0017] Please see Figure 1 , Figure 1 A flowchart of a cross-platform remote file synchronization method provided by an embodiment of the present application is shown in the figure, which specifically includes steps S101-S105.

[0018] S101, obtain a file synchronization instruction triggered in a cross-platform client, and parse the file synchronization instruction to obtain synchronization request data; S102. Based on the synchronization request data, create a synchronization session object in the cross-platform server, perform resource allocation processing on the synchronization session object, and obtain session management data. S103. Use the session management data to perform fragmentation strategy determination on the synchronization request data, and generate a synchronization metadata object; S104. Construct a session transmission queue based on the synchronization metadata object, and schedule the transmission of fragmented data in the session transmission queue to obtain a cross-platform fragmented transmission data set. S105. Based on the cross-platform fragmented transmission data set, file reassembly processing is performed on the cross-platform client to generate a reassembled file object, and synchronization result notification data is generated based on the reassembled file object.

[0019] In step S101, the cross-platform client (i.e., the client side, the same below) responds to the file synchronization command triggered by the user locally, parses the file synchronization command, identifies the parameter information related to the target file and the synchronization operation, and organizes it into a unified format of synchronization request data so that it can be transmitted and processed in the network environment later.

[0020] In one embodiment, step S101 includes: Receive file synchronization command line instructions input by the user in the cross-platform client, and extract data from the file synchronization command line instructions to obtain the raw instruction data; The original instruction data is parsed to identify the file path parameters corresponding to the target file, and the device fingerprint information of the cross-platform client is collected. The device fingerprint information is combined with the file path parameters to obtain the instruction parsing result. Based on the instruction parsing result, a dedicated data channel corresponding to the cross-platform client is selected from the multiplexed network long connection pool to encapsulate the instruction parsing result data in a structured manner to obtain transmission request data; The transmission request data is sent to the cross-platform server, and the session authentication middleware of the cross-platform server performs permission verification on the transmission request data to obtain session creation data. Based on the session creation data, a session record is written into the cross-platform server, and then the session record is associated with the transmission request data to obtain the synchronization request data.

[0021] In this embodiment, the cross-platform client runs in the command-line environment of a remote server (i.e., the cross-platform server, hereinafter the same) or a local terminal. When a user needs to download a target file from a remote server, they enter and execute a file synchronization command-line instruction in the command-line interface, such as "r-cp a.tar". The cross-platform client first extracts data from the command-line instruction to obtain raw instruction data containing information such as command name, target file path, and operation type. The client performs command parameter parsing processing on the raw instruction data to identify the file path parameter corresponding to the target file. At the same time, it collects the device fingerprint information of the current cross-platform client locally. The device fingerprint information includes runtime environment parameters such as client identifier, network type, and available storage space. The device fingerprint information is combined with the file path parameter to obtain a structured instruction parsing result.

[0022] Based on this, the cross-platform client selects a dedicated data channel corresponding to the current cross-platform client from a pre-maintained pool of long-lived multiplexed network connections, using the command parsing result. This data channel can be established using a WebSocket long connection. The command parsing result is encapsulated according to a preset structured transmission message format, preferably serialized using Protocol Buffers format, to obtain transmission request data for submission to the cross-platform server (i.e., the server side, hereinafter the same). The cross-platform client sends the transmission request data to the cross-platform server side through the dedicated data channel. The server's session authentication middleware performs permission verification on the transmission request data, including verifying the client's identity, access token, and access permissions of the target file. After successful verification, session creation data is generated to identify the legitimacy of this synchronization operation. The cross-platform server writes the corresponding session record in the session management module according to the session creation data, assigns a globally unique session identifier to this file synchronization operation, and establishes a multi-state session state machine. The session state machine includes seven states: initialization, metadata generation, transmission ready, transmission in progress, transmission paused, transmission completed, and transmission failed. Upon initial creation, the session is in the initialization state. Simultaneously, session records are written to both memory and persistent storage. These records can include core fields such as session ID, file path, file size, client information, creation timestamp, current state, and number of bytes transmitted. This forms a session record corresponding to the current file synchronization operation. This session record is then associated with previous transmission request data, ultimately generating unified synchronization request data on the server side, laying the foundation for resource allocation and data transmission in subsequent synchronization sessions.

[0023] In step S102, after receiving the synchronization request data, the cross-platform server creates a corresponding synchronization session object for the file synchronization operation and allocates system resources for file analysis, data caching and transmission control to the synchronization session object on the server side, thereby forming session management data that can uniformly manage the session lifecycle.

[0024] In one embodiment, step S102 includes: Based on the synchronization request data, the server-side file analysis module is called in the cross-platform server to obtain accurate metadata information, and the accurate metadata information is summarized and processed to obtain a synchronization session object. The verification is initiated in the cross-platform server based on the synchronous session object to obtain the verification configuration data; The verification configuration data is used to call the dynamic sharding engine in the cross-platform server to execute a two-stage sharding strategy and obtain sharding topology data. Using the fragment topology data, a mapping matrix between fragments and region verification blocks is constructed to obtain session fragment mapping management data; Based on the session sharding mapping management data, the cross-platform server calls the metadata compilation module to generate an enhanced metadata file, and associates the enhanced metadata file with the synchronous session object to obtain session management data.

[0025] In this embodiment, after receiving the synchronization request data generated in step S101, the cross-platform server first calls the file analysis module deployed on the server based on the target file path information carried in the synchronization request data. It then accesses the target file through the system call interface provided by the underlying operating system to obtain the precise metadata information corresponding to the target file. This precise metadata information includes at least parameters such as the target file's inode number in the file system, last modification time, file permissions, and the actual disk space occupied by the file. The server summarizes, archives, and structures this precise metadata information, and binds it to the session identifier corresponding to the current synchronization task, thereby obtaining a synchronization session object that describes the basic attributes and session context of this file synchronization.

[0026] After the synchronization session object is established, the cross-platform server initiates a multi-level verification and generation pipeline based on the synchronization session object. This pipeline configures the verification granularity, verification algorithm, and alignment method involved in this file synchronization, resulting in verification configuration data. Specifically, at the global level, the server calculates the MD5 checksum for the entire target file, using this MD5 value as the final benchmark for subsequent end-to-end consistency verification. At the region level, the server divides the target file according to a preset region size, preferably in 10MB units. It calculates the SHA-256 checksum for each region and establishes a region verification table for rapid verification and location of local file regions after transmission. At the fragment level, the server reserves verification configurations that match the dynamic fragmentation results. Once the data boundaries of each fragment are obtained, both CRC32 and MD5 checksums are calculated for each fragment, resulting in a three-level verification configuration covering the global, region, and fragment levels, constituting the verification configuration data.

[0027] After obtaining the verification configuration data, the cross-platform server calls the dynamic fragmentation engine to perform a two-stage fragmentation strategy on the target file specified in the synchronization request data to generate fragmentation topology data describing the file fragmentation structure. In the first stage, the dynamic fragmentation engine applies basic fragmentation rules based on the total size of the target file, dividing the file into several initial fragments at a fixed granularity, such as splitting them into fragments of approximately 1MB each, to maintain a reasonable balance between the number of fragments and the file size, facilitating subsequent queue scheduling and error recovery. In the second stage, the dynamic fragmentation engine combines the client's historical transmission performance characteristics recorded in session management and performs network adaptive adjustments to the initial fragmentation granularity based on operating indicators such as network bandwidth, packet loss rate, and round-trip latency, so that the final size of each fragment changes dynamically within a preset range, such as automatically optimizing within the range of 512KB to 4MB, to appropriately increase the number of fragments to reduce the number of interactions when network conditions are good, and to decrease the number of fragments to reduce the impact of a single transmission failure when network conditions are poor, ultimately obtaining fragmentation topology data containing information such as the size, order, and offset position of each fragment in the file.

[0028] Furthermore, based on the fragmented topology data, the cross-platform server constructs a mapping matrix between fragments and region check blocks, mapping each fragment to its corresponding region check unit and recording the region index, referenced region check value, and its position offset in the global file for each fragment, thus forming a fragment-region mapping matrix. Through this mapping matrix, if a CRC32 or MD5 check failure is detected in a fragment during subsequent transmission or verification, the server can quickly locate the corresponding region check block based on the mapping relationship, thereby achieving rapid location and isolation of erroneous regions and obtaining session fragment mapping management data used to manage the association between fragment and region check data.

[0029] Finally, based on the session fragmentation mapping management data, the cross-platform server calls the metadata compilation module to centrally compile and package the aforementioned synchronization session object, precise metadata information, three-level verification configuration, and fragmentation topology data, generating an enhanced metadata file to guide subsequent data transmission and client file reassembly. This enhanced metadata file contains target file attribute information, global and regional verification data, CRC32 and MD5 verification configurations organized by fragment, fragmentation topology description, and transmission control-related parameter configurations. The metadata file is also signed using a digital signature mechanism to ensure its integrity and tamper-proof nature during transmission. After generation, the cross-platform server associates the enhanced metadata file with the current synchronization session object and writes the relevant indexes into the session management module, thereby forming session management data for unified management of resources and control information for this synchronization session, providing a reliable metadata foundation for subsequent fragmentation scheduling and client-side file reassembly.

[0030] In step S103, the cross-platform server determines the fragmentation strategy for the file to be transmitted based on the session management data, thereby forming corresponding fragmentation rules and control parameters for different file sizes and network conditions, and generating a synchronization metadata object to describe the fragmentation structure, verification information and transmission control information.

[0031] In one embodiment, step S103 includes: In the cross-platform server, the priority transmission queue corresponding to the session management data is invoked, and a weight factor is registered in the priority transmission queue to obtain the transmission queue initialization data; The subscription information of the cross-platform client is associated with the corresponding session identifier using the transmission queue initialization data to obtain session routing management data; Based on the session routing management data, the concurrency control module of the cross-platform server starts an independent sending collaborative execution unit group for each cross-platform client to obtain concurrency configuration data; The concurrent configuration data is used to push a digitally signed metadata file, and the metadata file is bound to the session routing management data to obtain metadata sending control data; Based on the metadata, the control data for sending the data is dynamically adjusted during the data sending phase to obtain the fragmented scheduling control data. The fragmented scheduling control data is used for structured encapsulation to obtain fragmented coded data; Based on the fragmented encoded data, the transmission monitoring module of the cross-platform server performs real-time data statistics on the cross-platform client response to obtain a synchronized metadata object.

[0032] In this embodiment, after the cross-platform server completes the establishment of the synchronization session object and session management data, the server queue manager first calls the priority transmission queue corresponding to the current session identifier, initializes and configures the priority transmission queue, and registers weight factors for each file fragment to be transmitted in the queue. The weight factors comprehensively consider parameters such as fragment sequence number, number of historical transmission failures and target client priority. Preferably, the maximum weight finite priority scheduling algorithm is used to control the dequeue order of the fragments, thereby obtaining the transmission queue initialization data.

[0033] Furthermore, the server-side session router, based on the transmission queue initialization data, establishes a binding relationship between the subscription information of the current cross-platform client and the corresponding session identifier. Through a publish-subscribe mechanism, it continuously tracks all target clients listening to the session, maintaining a one-to-many mapping between clients and sessions, thus obtaining session routing management data to guide subsequent fragmentation path selection. Based on this, the server-side concurrency control module, for each target client in the subscription state, starts an independent sending coordination execution unit group according to the binding relationship recorded in the session routing management data. For example, it configures three parallel-running sending coordination execution units (sending coroutines) for each target client and uniformly manages the concurrency level, thread resources, and buffer size of each sending coordination execution unit, thereby obtaining concurrency configuration data describing the current session's concurrent sending strategy. According to the concurrency configuration data, before data delivery, the server adopts a metadata-first strategy, prioritizing the push of digitally signed enhanced metadata files to each target client through a control channel independent of the data channel. This metadata file is then bound and registered with the corresponding session routing management data, generating metadata sending control data to control the metadata delivery order and target client scope. In subsequent data delivery... During the transmission phase, the transmission coordination execution unit accesses the priority transmission queue based on the metadata transmission control data, acquires the right to send fragments from the transmission queue in a competitive preemptive manner, and dynamically adjusts the transmission window size and transmission rate using a sliding window flow control algorithm based on the current network status, obtaining fragment scheduling control data for each session and each client. The server encapsulates the fragmented data to be sent into a structured form based on the fragment scheduling control data, preferably using the TLV (Type-Length-Value) encoding format to construct fragmented data packets, wherein the fragment header records fields such as fragment sequence number, fragment checksum, and compression flag. The fragment body carries the actual file data, thereby generating fragmented encoded data for network transmission. Simultaneously, the server-side transmission monitoring module, based on the fragmented encoded data, collects and statistically analyzes the fragmented reception confirmation information returned by each target client in real time, continuously updates the session progress and the reception status of each fragment, supports real-time query of the current transmission progress, and integrates the above statistical results with the aforementioned metadata information and session management data to form a synchronous metadata object describing the current session fragmented scheduling status, transmission confirmation status, and verification preparation information, providing a complete control basis for subsequent cross-platform fragmented transmission and client file reassembly.

[0034] In step S104, the cross-platform server constructs a session transmission queue corresponding to the current synchronization session based on the synchronization metadata object, adds the fragmented data to be sent to the session transmission queue in a predetermined order and scheduling strategy, and schedules and sends the fragmented data item by item according to the queue during the file synchronization process, thereby forming a cross-platform fragmented transmission data set between the cross-platform client and the cross-platform server.

[0035] In one embodiment, step S104 includes: The synchronous metadata object is used to build a fragmented receiving queue in the cross-platform client, and a multi-stage receiving pipeline is started to obtain fragmented receiving pipeline data. Based on the fragmented receiving pipeline data, the metadata verification module is invoked to verify the metadata file corresponding to the synchronous metadata object, and temporary file allocation information is obtained. The temporary file allocation information is used to perform micro-verification on each fragment in the fragment receiving queue to obtain fragment verification result data. Based on the fragmentation verification result data, an intelligent retransmission control mechanism is constructed on the cross-platform client to obtain fragmentation retransmission control data. Based on the fragmented retransmission control data, the overall verification value is calculated in the final verification stage to generate the reassembled file verification result; The file replacement process is performed on the cross-platform client using the verification results of the reconstructed file to obtain a cross-platform fragmented transmission data set.

[0036] In this embodiment, after the cross-platform server completes the construction of the session transmission queue and the scheduling and sending of fragmented data based on the synchronous metadata object, the cross-platform client first uses the synchronous metadata object to build a fragmented receiving queue locally for caching inbound fragmented data on the receiving side, and starts a multi-stage receiving pipeline according to the preset pipeline model. Data is transmitted between each receiving stage through a bounded channel, thereby achieving producer-consumer decoupling between fragmented receiving, verification and writing, and obtaining fragmented receiving pipeline data used to describe the running status of each stage.

[0037] Based on the fragmented reception pipeline data, the client calls the metadata verification module to perform integrity and legality verification on the enhanced metadata file corresponding to the synchronized metadata object. Preferably, the digital signature and structural integrity of the metadata file are verified first. After confirming that it has not been tampered with and that all fields are complete, a sparse temporary file is created locally based on the file size and fragment layout information recorded therein. Preferably, disk space is pre-allocated through the fallocate system call, thereby generating temporary file allocation information for subsequent fragment writing and layout mapping. Based on the temporary file allocation information, the client performs micro-verification processing on each fragment that enters the verification stage in the fragmented reception queue. Specifically, this can be done in a three-level progressive manner: first, structural verification is performed to check whether the basic fields such as the format, sequence number, and length of the fragment header meet expectations; after the structural verification passes, integrity verification is performed, calculating the CRC32 check value of the fragmented data and comparing it with the check value carried in the fragment header. The system quickly detects explicit transmission errors. After integrity verification passes, a consistency verification is further performed, calculating the MD5 value of the fragmented data and comparing it with the fragment-level MD5 checksum recorded in the synchronization metadata object to ensure that each fragment is accurate at the byte level. This yields fragment verification result data that marks whether each fragment is qualified and the error type information. Based on the fragment verification result data, the client constructs an intelligent retransmission control mechanism to perform fine-grained management of fragments that need to be retransmitted. This includes: for a single fragment verification failure, immediately sending a negative acknowledgment message to the server to request immediate retransmission; when multiple consecutive fragments fail verification, triggering a batch retransmission strategy to initiate retransmission requests for adjacent erroneous fragments in a segment manner; and simultaneously, combining historical failure distribution and network status characteristics, proactively initiating preventative retransmissions for fragments that may have potential risks, thereby generating fragment retransmission control data that comprehensively considers immediate retransmission, batch retransmission, and preventative retransmission strategies.

[0038] Under the aforementioned micro-verification and retransmission control closed loop, for the verified fragmented data, the client file reassembler employs a double-buffered write strategy according to the fragment order in the synchronization metadata object and the temporary file allocation information. This sequentially writes the fragmented data to the sparse temporary file, ensuring that fragments are written in order and avoiding out-of-order overwriting. Furthermore, it periodically calls `fsync` to flush the written data to disk, enhancing the security of data persistence. After all fragments have been successfully received and written to the temporary file, the client enters the final verification stage. Based on the aforementioned fragment retransmission control data and fragment verification results, it calculates the overall MD5 value of the reassembled file and compares it with the global MD5 checksum recorded in the synchronization metadata object. Simultaneously, it compares the actual MD5 checksum of the reassembled file... The system checks whether file system information such as the file system size and inode are consistent with the metadata records, thereby generating a verification result to identify whether the reconstructed file is completely consistent globally. If the verification result shows that the data content of the reconstructed file is completely consistent with the metadata records, the client performs atomic file replacement processing, replacing the temporary file with the official file under the target file path in one go through the rename system call. This ensures that there are no intermediate states of partial updates during the entire replacement process, thereby completing the safe switching of the original file. All successfully received and verified fragment data are included in the cross-platform fragment transmission data set corresponding to the current session, providing a reliable foundation for the subsequent display of file reconstruction results and notification of synchronization results.

[0039] In step S105, after the cross-platform client receives the cross-platform fragmented transmission data set, it reassembles the fragmented data according to the fragment identifier and order described in the synchronization metadata object, restores each fragment to complete file data to generate a reassembled file object, and generates synchronization result notification data by combining the storage path, session status and other information of the reassembled file object after the reassembly is completed. This data is used to prompt the client side with the completion status of the current file synchronization operation and related result information.

[0040] In one embodiment, step S105 includes: Based on the cross-platform fragmented transmission data set, it is sequentially reassembled in the cross-platform client to generate a reassembled file object; The path information is extracted from the recombined file object to obtain the integrated result data; The integrated result data is used to trigger a progressive user notification process in the cross-platform client to obtain tray notification status data; Based on the tray notification status data, operation events are statistically analyzed within a preset time interval to generate transmission history log data; Based on the transmission history log data, a transmission shortcut menu corresponding to the reconstructed file object is generated and bound to the reconstructed file object to output synchronization result notification data.

[0041] In this embodiment, after completing the aforementioned fragment reception, verification, and writing operations and obtaining the cross-platform fragmented transmission data set, the cross-platform client first reassembles the cross-platform fragmented transmission data set according to the fragment sorting information and file size information recorded in the synchronization metadata object. Each fragment is then mapped back to its corresponding position in the target file in logical order, thereby generating a reassembled file object in the local file system that corresponds one-to-one with the original target file. The client system integration module reads the complete path, directory, and filename of the reassembled file object in the current operating system, formats the path information, constructs integration result data, and automatically writes the path information of the reassembled file object to the multi-platform clipboard to adapt to the clipboard interface specifications of different operating systems such as Windows, macOS, and Linux, enabling users to directly paste the target file path on different platforms.

[0042] After obtaining the integration result data, the client further triggers a progressive user notification process locally. First, a continuously displayed synchronization completion notification icon or bubble is generated in the system tray area to form the initial state of the tray notification, and this state is written to the tray notification status data. If no user click or hover operation event is detected on the tray notification icon within a preset time interval (e.g., 3 seconds), the operating system is driven to display a native pop-up prompt based on the tray notification status data, presenting the path information of the reconstituted file object, the synchronization result, and optional operations to the user in the form of a dialog box. During the above progressive notification process, the client simultaneously performs statistical and persistent recording of user clicks, closes, ignores, and other operation events within the preset time interval based on the tray notification status data and pop-up interaction results, generating corresponding transmission history log data. This transmission history log data is used to describe the completion time, target file path, etc., of each file synchronization task. The client synchronizes the results and user actions, and supports subsequent historical queries and statistical analysis. In a graphical desktop environment, based on the transmission history log data, the client dynamically generates a corresponding transmission shortcut menu for the current reconstructed file object. Shortcut items such as "Open the current folder," "Copy the file path," and "Copy the download link or share link" are encapsulated in a unified menu structure, and the transmission shortcut menu is bound to the reconstructed file object. This allows users to directly call the above shortcuts by right-clicking or clicking in the tray notification, history list, or pop-up interface. Finally, the client encapsulates the comprehensive results, including the reconstructed file object identifier, integration result data, tray notification status data, transmission history log data, and transmission shortcut menu configuration information, into a synchronization result notification output. This maintains a consistent user experience across platforms while completing the presentation of the results and system integration of this cross-platform remote file synchronization task.

[0043] In one embodiment, the cross-platform remote file synchronization method further includes: Based on the synchronization result notification data, the transmission optimization configuration parameters corresponding to the current synchronization session are determined, and network monitoring rules are configured for the transmission optimization configuration parameters to obtain monitoring configuration data. Based on the monitoring configuration data, network bandwidth, round-trip latency, and jitter indicators are collected in the cross-platform client to generate network status monitoring data. The network status monitoring data is then dynamically adjusted to obtain transmission parameter adjustment data. The data adjusted using the transmission parameters is persistently stored on both the cross-platform server and the cross-platform client to generate breakpoint resume status data. The reconstructed file object is associated with the breakpoint resume status data to obtain an incremental synchronization data set; The incremental synchronization data set is compressed to generate a compressed incremental fragmented data set.

[0044] In this embodiment, the cross-platform client and server, based on the aforementioned synchronization result notification data, perform statistical analysis on the file size, number of fragments, number of retransmissions, and network anomalies during the current synchronization session. They then generate transmission optimization configuration parameters corresponding to the synchronization session based on a preset optimization strategy. These parameters include at least control items such as fragment size adjustment range, upper and lower limits for the number of concurrent transmission collaborative execution units, network quality thresholds, and breakpoint resume switch. The cross-platform client configures network monitoring rules for these transmission optimization configuration parameters to obtain monitoring configuration data that guides subsequent network probing actions. During subsequent operation, the cross-platform client periodically or before the session begins probes the current network environment based on the monitoring configuration data, collecting real-time indicators such as network bandwidth, round-trip latency, and jitter to obtain the network status. The system monitors data and dynamically adjusts the fragment size and the number of concurrent transmission collaborative execution units when it detects a decrease in network bandwidth, an increase in round-trip latency, or an increase in jitter. This allows for increased transmission fragments and concurrency to improve throughput when network conditions are good, and reduced fragment granularity and concurrency to alleviate congestion when network conditions are poor. This generates transmission parameter adjustment data to constrain subsequent file transmission behavior. The cross-platform server and cross-platform client use the transmission parameter adjustment data to persistently store status information such as the current session's transmission progress, the offset position of successfully written files, and the fragment number that passed the most recent verification. This results in breakpoint resume transmission status data, enabling both parties to resume file synchronization from the most recent successful transmission position in the event of a subsequent network interruption or abnormal client exit, without having to retransmit completed data blocks.

[0045] Furthermore, when resynchronizing the same target file, the cross-platform server performs fingerprint comparison on the file content based on the breakpoint resume status data and the current reconstructed file object. The file is divided into several data blocks, and the changed data blocks are identified by comparing file fingerprints or block checksums. Only the changed data blocks are used to construct new transmission tasks, thereby extracting an incremental synchronization data set for the current reconstructed file object, significantly reducing the transmission overhead of duplicate, unchanged data. Finally, before formal distribution, the cross-platform server connects the incremental synchronization data set to the transmission compression pipeline, applying a fast compression algorithm to each data block or fragment for online compression. The LZ4 compression algorithm is preferred to compress the fragmented data while ensuring low computational overhead, generating a compressed incremental fragmented data set for efficient transmission over the network. This set is then sent to the cross-platform client according to the aforementioned session transmission queue and fragment scheduling strategy, thereby further reducing network transmission volume and overall synchronization latency while ensuring data reliability.

[0046] In one embodiment, the cross-platform remote file synchronization method can also be used in intelligent folder synchronization scenarios. When the cross-platform client parses the synchronization command input by the user and detects that the current synchronization target is a folder rather than a single file, the client first starts a directory analyzer locally, performs a recursive scan operation on the target folder, traverses all subdirectories and file nodes within it, collects the hierarchical relationship, file name, file type and size and other attribute information of each level of directory, and on this basis, constructs a file tree topology diagram to describe the overall hierarchical structure of the folder, and uniformly models the subordinate relationship, relative path and metadata information of each directory node and file node for subsequent packaging and difference comparison.

[0047] After obtaining the complete file tree topology, the intelligent packaging engine is invoked to determine the appropriate compression strategy for this folder synchronization based on the distribution of file types and sizes in the file tree: For directories with a large number of files and a large overall size, a standard compression algorithm (such as standard ZIP compression) is preferred to generate a single compressed package; for scenarios containing very large files or requiring segmented transmission, a multi-volume compression strategy is selected, dividing the packaged result into multiple contiguous volumes for easy transmission over the network; for folders already in compressed format or sensitive to latency, only packaging is performed without compression to reduce CPU overhead and compression latency. After selecting the packaging strategy, the intelligent packaging engine generates the corresponding packaged file according to the selected strategy and maintains the mapping relationship between the packaged file and the original file tree topology on both the server and client sides.

[0048] Furthermore, a differential transmission algorithm is applied to the generated packaged files. By comparing the structure and content fingerprint of the current packaged files with historical versions or snapshots saved on the cross-platform server, newly added files, modified files, and unchanged files are accurately identified. Incremental data blocks are generated only for the changed parts and added to the transmission queue, thereby achieving incremental synchronization of folder content and avoiding duplicate transmission of unchanged data. After all incremental data blocks are successfully transmitted and merged and updated on the server, the cross-platform client provides users with flexible decompression and recovery options during the synchronization completion phase: one method is automatic decompression, where the client automatically decompresses the compressed package content and restores it to the target directory structure in the background according to the file tree topology; another method is to retain the original packaged structure, saving only the compressed package or split files to a specified location for users to manually decompress later; a selective decompression mode can also be provided, where users select the subdirectories or file nodes to be restored in the graphical interface, and the system only decompresses and writes the selected parts, thus ensuring the integrity of the directory structure while meeting the differentiated needs for decompression granularity and recovery methods in different usage scenarios. Through the above-described intelligent folder synchronization embodiments, the present invention can perform efficient and incremental synchronization processing on large-scale directory structures while maintaining cross-platform consistency, and significantly improve the user's operational convenience and network transmission efficiency in folder synchronization scenarios.

[0049] In summary, at the architectural level, this invention introduces an integrated and collaborative transmission architecture that combines "stateful session management, a three-level verification mechanism, dynamic fragmentation scheduling, and multi-path asynchronous queues." On the server side, file metadata, fragmentation topology, and transmission status are uniformly managed at the session level. During transmission, multi-level queues and concurrency control are combined to achieve fine-grained traffic scheduling and congestion control, significantly improving high-concurrency throughput and long-link transmission stability in complex network environments.

[0050] At the methodological level, by refining the verification mechanism into a three-level system of "regional verification, fragmented dual verification, and global final state verification", regional verification is used to quickly locate local anomalies, fragmented CRC and MD5 dual verification is used to enhance the transmission reliability of single-fragment data, and global MD5 final state verification is used to finally confirm the consistency of the reconstructed file after transmission. Thus, a coarse-to-fine and progressively converging integrity guarantee system is formed on the end-to-end link, which effectively solves the data security risks caused by the lack of mandatory integrity verification in existing technologies.

[0051] At the process level, the client side adopts a phased processing mode of "pipeline decomposition - parallel processing - real-time verification", which decouples the receiving, verification, reassembly and disk flushing links into parallel and collaborative processing links through bounded channels. The server side is equipped with session-level timing advancement and intelligent retransmission mechanism, which enables data to form a closed loop control between the transmission, verification and error correction links, which greatly reduces the retransmission cost and improves the continuity and recoverability of long-term and large-volume transmission tasks.

[0052] At the integration level, this invention deeply couples system-level integration capabilities (such as multi-platform clipboard writing, progressive user notifications, transmission history logs, and quick operation menus) with the underlying transmission core, enabling file synchronization results to be presented in a unified and smooth interactive form across different operating system environments. Furthermore, it connects intelligent folder processing, differentiated incremental synchronization, and transmission optimization compression capabilities into a complete end-to-end solution, thereby improving the user experience while achieving overall optimization of the reliability, maintainability, and ease of use of remote file transmission in complex cloud computing and distributed operation and maintenance scenarios.

[0053] Combination Figure 2 As shown, Figure 2 This is a schematic block diagram of a cross-platform remote file synchronization device provided in an embodiment of the present invention. The cross-platform remote file synchronization device 200 includes: The data acquisition unit 201 is used to acquire the file synchronization instruction triggered in the cross-platform client, and parse the file synchronization instruction to obtain synchronization request data; Resource allocation unit 202 is used to create a synchronization session object in the cross-platform server based on the synchronization request data, perform resource allocation processing on the synchronization session object, and obtain session management data. Data synchronization unit 203 is used to perform fragmentation strategy determination processing on the synchronization request data using the session management data, and generate synchronization metadata object; The scheduling and sending unit 204 is used to construct a session transmission queue based on the synchronization metadata object, and schedule and send the fragmented data in the session transmission queue to obtain a cross-platform fragmented transmission data set. The data output unit 205 is used to perform file reassembly processing on the cross-platform client based on the cross-platform fragmented transmission data set to generate a reassembled file object, and generate synchronization result notification data based on the reassembled file object.

[0054] In this embodiment, the data acquisition unit 201 acquires the file synchronization instruction triggered in the cross-platform client and parses the file synchronization instruction to obtain synchronization request data; the resource allocation unit 202 creates a synchronization session object in the cross-platform server based on the synchronization request data, performs resource allocation processing on the synchronization session object, and obtains session management data; the data synchronization unit 203 uses the session management data to perform fragmentation strategy determination processing on the synchronization request data and generates a synchronization metadata object; the scheduling and sending unit 204 constructs a session transmission queue based on the synchronization metadata object and schedules and sends the fragmented data in the session transmission queue to obtain a cross-platform fragmented transmission data set; the data output unit 205 performs file reassembly processing on the cross-platform client based on the cross-platform fragmented transmission data set to generate a reassembled file object, and generates synchronization result notification data based on the reassembled file object.

[0055] In one embodiment, the data acquisition unit 201 is specifically used for: Receive file synchronization command line instructions input by the user in the cross-platform client, and extract data from the file synchronization command line instructions to obtain the raw instruction data; The original instruction data is parsed to identify the file path parameters corresponding to the target file, and the device fingerprint information of the cross-platform client is collected. The device fingerprint information is combined with the file path parameters to obtain the instruction parsing result. Based on the instruction parsing result, a dedicated data channel corresponding to the cross-platform client is selected from the multiplexed network long connection pool to encapsulate the instruction parsing result data in a structured manner to obtain transmission request data; The transmission request data is sent to the cross-platform server, and the session authentication middleware of the cross-platform server performs permission verification on the transmission request data to obtain session creation data. Based on the session creation data, a session record is written into the cross-platform server, and then the session record is associated with the transmission request data to obtain the synchronization request data.

[0056] In one embodiment, the resource allocation unit 202 is specifically used for: Based on the synchronization request data, the server-side file analysis module is called in the cross-platform server to obtain accurate metadata information, and the accurate metadata information is summarized and processed to obtain a synchronization session object. The verification is initiated in the cross-platform server based on the synchronous session object to obtain the verification configuration data; The verification configuration data is used to call the dynamic sharding engine in the cross-platform server to execute a two-stage sharding strategy and obtain sharding topology data. Using the fragment topology data, a mapping matrix between fragments and region verification blocks is constructed to obtain session fragment mapping management data; Based on the session sharding mapping management data, the cross-platform server calls the metadata compilation module to generate an enhanced metadata file, and associates the enhanced metadata file with the synchronous session object to obtain session management data.

[0057] In one embodiment, the data synchronization unit 203 is specifically used for: In the cross-platform server, the priority transmission queue corresponding to the session management data is invoked, and a weight factor is registered in the priority transmission queue to obtain the transmission queue initialization data; The subscription information of the cross-platform client is associated with the corresponding session identifier using the transmission queue initialization data to obtain session routing management data; Based on the session routing management data, the concurrency control module of the cross-platform server starts an independent sending collaborative execution unit group for each cross-platform client to obtain concurrency configuration data; The concurrent configuration data is used to push a digitally signed metadata file, and the metadata file is bound to the session routing management data to obtain metadata sending control data; Based on the metadata, the control data for sending the data is dynamically adjusted during the data sending phase to obtain the fragmented scheduling control data. The fragmented scheduling control data is used for structured encapsulation to obtain fragmented coded data; Based on the fragmented encoded data, the transmission monitoring module of the cross-platform server performs real-time data statistics on the cross-platform client response to obtain a synchronized metadata object.

[0058] In one embodiment, the scheduling and sending unit 204 is specifically used for: The synchronous metadata object is used to build a fragmented receiving queue in the cross-platform client, and a multi-stage receiving pipeline is started to obtain fragmented receiving pipeline data. Based on the fragmented receiving pipeline data, the metadata verification module is invoked to verify the metadata file corresponding to the synchronous metadata object, and temporary file allocation information is obtained. The temporary file allocation information is used to perform micro-verification on each fragment in the fragment receiving queue to obtain fragment verification result data. Based on the fragmentation verification result data, an intelligent retransmission control mechanism is constructed on the cross-platform client to obtain fragmentation retransmission control data. Based on the fragmented retransmission control data, the overall verification value is calculated in the final verification stage to generate the reassembled file verification result; The file replacement process is performed on the cross-platform client using the verification results of the reconstructed file to obtain a cross-platform fragmented transmission data set.

[0059] In one embodiment, the data output unit 205 is specifically used for: Based on the cross-platform fragmented transmission data set, it is sequentially reassembled in the cross-platform client to generate a reassembled file object; The path information is extracted from the recombined file object to obtain the integrated result data; The integrated result data is used to trigger a progressive user notification process in the cross-platform client to obtain tray notification status data; Based on the tray notification status data, operation events are statistically analyzed within a preset time interval to generate transmission history log data; Based on the transmission history log data, a transmission shortcut menu corresponding to the reconstructed file object is generated and bound to the reconstructed file object to output synchronization result notification data.

[0060] In one embodiment, the cross-platform remote file synchronization device 200 is further configured to: Based on the synchronization result notification data, the transmission optimization configuration parameters corresponding to the current synchronization session are determined, and network monitoring rules are configured for the transmission optimization configuration parameters to obtain monitoring configuration data. Based on the monitoring configuration data, network bandwidth, round-trip latency, and jitter indicators are collected in the cross-platform client to generate network status monitoring data. The network status monitoring data is then dynamically adjusted to obtain transmission parameter adjustment data. The data adjusted using the transmission parameters is persistently stored on both the cross-platform server and the cross-platform client to generate breakpoint resume status data. The reconstructed file object is associated with the breakpoint resume status data to obtain an incremental synchronization data set; The incremental synchronization data set is compressed to generate a compressed incremental fragmented data set.

[0061] Since the embodiments of the apparatus and the embodiments of the method correspond to each other, please refer to the description of the embodiments of the method for the embodiments of the apparatus, which will not be repeated here.

[0062] This invention also provides a computer-readable storage medium storing a computer program thereon, which, when executed, can perform the steps provided in the above embodiments. The storage medium may include various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0063] This invention also provides a computer device, which may include a memory and a processor. The memory stores a computer program, and when the processor calls the computer program in the memory, it can implement the steps provided in the above embodiments. Of course, the computer device may also include various network interfaces, a power supply, a graphics card, etc., to utilize the graphics card's performance to operate the model, such as for inference and training.

[0064] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the systems disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple; relevant parts can be referred to in the method section. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

[0065] It should also be noted that, in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover a 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 limitations, 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.

Claims

1. A cross-platform remote file synchronization method, characterized in that, include: Obtain the file synchronization command triggered in the cross-platform client, and parse the file synchronization command to obtain synchronization request data; Based on the synchronization request data, a synchronization session object is created in the cross-platform server, and resource allocation is performed on the synchronization session object to obtain session management data. The session management data is used to determine the fragmentation strategy for the synchronization request data, and a synchronization metadata object is generated. A session transmission queue is constructed based on the synchronous metadata object, and the fragmented data in the session transmission queue is scheduled to be sent to obtain a cross-platform fragmented transmission data set. Based on the cross-platform fragmented transmission data set, file reassembly processing is performed on the cross-platform client to generate reassembled file objects, and synchronization result notification data is generated based on the reassembled file objects.

2. The cross-platform remote file synchronization method according to claim 1, characterized in that, The process of obtaining the file synchronization command triggered in the cross-platform client and parsing the file synchronization command to obtain synchronization request data includes: Receive file synchronization command line instructions input by the user in the cross-platform client, and extract data from the file synchronization command line instructions to obtain the raw instruction data; The original instruction data is parsed to identify the file path parameters corresponding to the target file, and the device fingerprint information of the cross-platform client is collected. The device fingerprint information is combined with the file path parameters to obtain the instruction parsing result. Based on the instruction parsing result, a dedicated data channel corresponding to the cross-platform client is selected from the multiplexed network long connection pool to encapsulate the instruction parsing result data in a structured manner to obtain transmission request data; The transmission request data is sent to the cross-platform server, so that the session authentication middleware of the cross-platform server performs permission verification on the transmission request data to obtain session creation data. Based on the session creation data, a session record is written into the cross-platform server, and then the session record is associated with the transmission request data to obtain the synchronization request data.

3. The cross-platform remote file synchronization method according to claim 1, characterized in that, The process involves creating a synchronization session object on the cross-platform server based on the synchronization request data, performing resource allocation on the synchronization session object, and obtaining session management data, including: Based on the synchronization request data, the server-side file analysis module is called in the cross-platform server to obtain accurate metadata information, and the accurate metadata information is summarized and processed to obtain a synchronization session object. The verification is initiated in the cross-platform server based on the synchronous session object to obtain the verification configuration data; The verification configuration data is used to call the dynamic sharding engine in the cross-platform server to execute a two-stage sharding strategy and obtain sharding topology data. Using the fragment topology data, a mapping matrix between fragments and region verification blocks is constructed to obtain session fragment mapping management data; Based on the session sharding mapping management data, the cross-platform server calls the metadata compilation module to generate an enhanced metadata file, and associates the enhanced metadata file with the synchronous session object to obtain session management data.

4. The cross-platform remote file synchronization method according to claim 1, characterized in that, The step of using the session management data to determine the sharding strategy for the synchronization request data and generating a synchronization metadata object includes: In the cross-platform server, the priority transmission queue corresponding to the session management data is invoked, and a weight factor is registered in the priority transmission queue to obtain the transmission queue initialization data; The subscription information of the cross-platform client is associated with the corresponding session identifier using the transmission queue initialization data to obtain session routing management data; Based on the session routing management data, the concurrency control module of the cross-platform server starts an independent sending collaborative execution unit group for each cross-platform client to obtain concurrency configuration data; The concurrent configuration data is used to push a digitally signed metadata file, and the metadata file is bound to the session routing management data to obtain metadata sending control data; Based on the metadata, the control data for sending the data is dynamically adjusted during the data sending phase to obtain the fragmented scheduling control data. The fragmented scheduling control data is used for structured encapsulation to obtain fragmented coded data; Based on the fragmented encoded data, the transmission monitoring module of the cross-platform server performs real-time data statistics on the cross-platform client response to obtain a synchronized metadata object.

5. The cross-platform remote file synchronization method according to claim 1, characterized in that, The process involves constructing a session transmission queue based on the synchronized metadata object, and scheduling the transmission of fragmented data within the session transmission queue to obtain a cross-platform fragmented transmission data set, including: The synchronous metadata object is used to build a fragmented receiving queue in the cross-platform client, and a multi-stage receiving pipeline is started to obtain fragmented receiving pipeline data. Based on the fragmented receiving pipeline data, the metadata verification module is invoked to verify the metadata file corresponding to the synchronous metadata object, and temporary file allocation information is obtained. The temporary file allocation information is used to perform micro-verification on each fragment in the fragment receiving queue to obtain fragment verification result data. Based on the fragmentation verification result data, an intelligent retransmission control mechanism is constructed on the cross-platform client to obtain fragmentation retransmission control data. Based on the fragmented retransmission control data, the overall verification value is calculated in the final verification stage to generate the reassembled file verification result; The file replacement process is performed on the cross-platform client using the verification results of the reconstructed file to obtain a cross-platform fragmented transmission data set.

6. The cross-platform remote file synchronization method according to claim 1, characterized in that, The cross-platform fragmented transmission data set is used to perform file reassembly processing on the cross-platform client to generate a reassembled file object, and synchronization result notification data is generated based on the reassembled file object, including: Based on the cross-platform fragmented transmission data set, it is sequentially reassembled in the cross-platform client to generate a reassembled file object; The path information is extracted from the recombined file object to obtain the integrated result data; The integrated result data is used to trigger a progressive user notification process in the cross-platform client to obtain tray notification status data; Based on the tray notification status data, statistical operation events are counted within a preset time interval to generate transmission history log data; Based on the transmission history log data, a transmission shortcut menu corresponding to the reconstructed file object is generated and bound to the reconstructed file object to output synchronization result notification data.

7. The cross-platform remote file synchronization method according to claim 1, characterized in that, Also includes: Based on the synchronization result notification data, the transmission optimization configuration parameters corresponding to the current synchronization session are determined, and network monitoring rules are configured for the transmission optimization configuration parameters to obtain monitoring configuration data. Based on the monitoring configuration data, network bandwidth, round-trip latency, and jitter indicators are collected in the cross-platform client to generate network status monitoring data. The network status monitoring data is then dynamically adjusted to obtain transmission parameter adjustment data. The data adjusted using the transmission parameters is persistently stored on both the cross-platform server and the cross-platform client to generate breakpoint resume status data. The reconstructed file object is associated with the breakpoint resume status data to obtain an incremental synchronization data set; The incremental synchronization data set is compressed to generate a compressed incremental fragmented data set.

8. A cross-platform remote file synchronization device, characterized in that, include: The data acquisition unit is used to acquire file synchronization instructions triggered in the cross-platform client, and parse the file synchronization instructions to obtain synchronization request data; The resource allocation unit is used to create a synchronization session object in the cross-platform server based on the synchronization request data, perform resource allocation processing on the synchronization session object, and obtain session management data. The data synchronization unit is used to perform fragmentation strategy determination on the synchronization request data using the session management data, and generate a synchronization metadata object. The scheduling and sending unit is used to construct a session transmission queue based on the synchronization metadata object, and to schedule and send the fragmented data in the session transmission queue to obtain a cross-platform fragmented transmission data set. The data output unit is used to perform file reassembly processing on the cross-platform client based on the cross-platform fragmented transmission data set to generate a reassembled file object, and generate synchronization result notification data based on the reassembled file object.

9. A computer device, characterized in that, It includes a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor, when executing the computer program, implements the cross-platform remote file synchronization method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the cross-platform remote file synchronization method as described in any one of claims 1 to 7.

Images