File ferrying method and device, storage medium and electronic equipment

Abstract

The invention discloses a file ferrying method and device, a storage medium and electronic equipment, and the method comprises the steps: an initiating end cloud disk determines a ferrying data file corresponding to a ferrying request initiated by a user, obtains a ferrying configuration file of the ferrying data file, and sends the ferrying configuration file to a server; the ferry data file and the ferry configuration file are sent to a ferry folder of the initiating end network, the receiving end cloud disk obtains the ferry data file and the ferry configuration file from the ferry folder of the initiating end network, and the receiving end cloud disk stores the ferry data file based on the ferry configuration file. By adopting the method and the device, the ferry configuration file and the ferry data file are sent to the cloud disk of the receiving end together, so that cloud disk file ferry between different independent networks is realized, the hierarchical relationship in the ferry data file can be ensured by utilizing the ferry configuration file, and the confusion of file contents after file ferry is avoided; and the order of file ferrying is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a file ferrying method, device, storage medium and electronic device. Background Art

[0002] Internet cloud disk is a professional Internet storage tool and a product of Internet cloud technology. It can provide information storage, reading, downloading and other services for enterprises and individuals through the Internet. It has the characteristics of security, stability and massive storage. Users can also directly transfer file data through cloud disk, that is, directly send file data from their own cloud disk to another user's cloud disk. However, if the two cloud disks are not in the same network, but in two isolated and independent networks, the file data in the cloud disk cannot be directly transmitted through the Internet. It is necessary to provide a fast and traversal method for cross-network file transfer. Summary of the invention

[0003] The embodiment of the present application provides a file ferrying method, device, storage medium and electronic device, which can realize the ferrying of cloud disk files between different independent networks by sending the ferrying configuration file and the ferrying data file to the receiving end cloud disk, and can use the ferrying configuration file to ensure the hierarchical relationship in the ferrying data file, avoid the confusion of file content after file ferrying, and improve the orderliness of file ferrying. The technical solution is as follows:

[0004] In a first aspect, an embodiment of the present application provides a file ferrying method, which is applied to an initiating network, and is characterized in that the method includes:

[0005] Determine a ferry data file corresponding to a ferry request initiated by a user, and obtain a ferry configuration file of the ferry data file;

[0006] The ferry data file and the ferry configuration file are sent to the ferry folder of the initiating end network, so that the receiving end cloud disk of the receiving end network saves the ferry data file based on the ferry configuration file.

[0007] In a second aspect, an embodiment of the present application provides a file ferrying method, which is applied to a receiving end network, and is characterized in that the method includes:

[0008] Get the ferry data file and ferry configuration file from the ferry folder of the initiator network;

[0009] The ferry data file is saved based on the ferry configuration file.

[0010] In a third aspect, an embodiment of the present application provides a file ferrying method, characterized in that the method includes:

[0011] The initiator cloud disk of the initiator network determines the ferry data file corresponding to the ferry request initiated by the user, and obtains the ferry configuration file of the ferry data file;

[0012] The initiator cloud disk sends the ferry data file and the ferry configuration file to the ferry folder of the initiator network;

[0013] The receiving-end cloud disk of the receiving-end network obtains the ferry data file and the ferry configuration file from the ferry folder;

[0014] The receiving-end cloud disk saves and processes the ferry data file based on the ferry configuration file.

[0015] In a fourth aspect, an embodiment of the present application provides a file sending device, characterized in that the method includes:

[0016] A file data acquisition module, used to determine the ferry data file corresponding to the ferry request initiated by the user, and acquire the ferry configuration file of the ferry data file;

[0017] The file data ferry module is used to send the ferry data file and the ferry configuration file to the ferry folder of the initiating end network, so that the receiving end cloud disk of the receiving end network saves the ferry data file based on the ferry configuration file.

[0018] In a fifth aspect, an embodiment of the present application provides a file receiving device, characterized in that the device includes:

[0019] The file data receiving module is used to obtain the ferry data file and the ferry configuration file from the ferry folder of the initiator network;

[0020] A saving processing module is used to save the ferry data file based on the ferry configuration file.

[0021] In a sixth aspect, an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0022] In a seventh aspect, an embodiment of the present application provides an electronic device, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0023] In one or more embodiments of the present application, the initiating cloud disk determines the ferry data file corresponding to the ferry request initiated by the user, obtains the ferry configuration file of the ferry data file, sends the ferry data file and the ferry configuration file to the ferry folder of the initiating network, and the receiving cloud disk obtains the ferry data file and the ferry configuration file from the ferry folder of the initiating network, and the receiving cloud disk saves and processes the ferry data file based on the ferry configuration file. By sending the ferry configuration file together with the ferry data file to the receiving cloud disk, while realizing the ferrying of cloud disk files between different independent networks, the ferry configuration file can be used to ensure the hierarchical relationship in the ferry data file, avoiding confusion of file content after file ferrying, and improving the orderliness of file ferrying. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0025] Figure 1 This is an example schematic diagram of a file ferry provided in an embodiment of the present application;

[0026] Figure 2 It is a flowchart of a file ferrying method provided in an embodiment of the present application;

[0027] Figure 3 It is a flowchart of a file ferrying method provided in an embodiment of the present application;

[0028] Figure 4 This is an example schematic diagram of a ferry process form provided in an embodiment of the present application;

[0029] Figure 5 It is a flowchart of a method for sending files under physical isolation provided by an embodiment of the present application;

[0030] Figure 6 It is a flowchart of a method for sending a file under logical isolation provided by an embodiment of the present application;

[0031] Figure 7 It is a flowchart of a file ferrying method provided in an embodiment of the present application;

[0032] Figure 8 It is a flowchart of a file ferrying method provided in an embodiment of the present application;

[0033] Fig. 9It is a flowchart of a file ferrying method provided in an embodiment of the present application;

[0034] Fig.10 It is a flowchart of a file ferrying method provided in an embodiment of the present application;

[0035] Fig.11 It is a structural schematic diagram of a file sending device provided in an embodiment of the present application;

[0036] Fig.12 It is a structural schematic diagram of a file sending device provided in an embodiment of the present application;

[0037] Fig.13 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application;

[0038] Fig.14 It is a structural schematic diagram of a file receiving device provided in an embodiment of the present application;

[0039] Fig.15 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0041] Cloud disk is a professional Internet storage tool and a product of Internet cloud technology. It can provide information storage, reading, downloading and other services for enterprises and individuals through the Internet. If two cloud disks are in the same network, users can send data files in their own network disk to another network disk through the network. However, it is understandable that for information security reasons, some enterprises or units will build independent networks and isolate independent networks from other networks to avoid data exchange and thus data leakage. If the two cloud disks are in two different, isolated and independent networks, the data files in the cloud disk cannot be directly transmitted through the network, and the file ferry method needs to be used to send data files from one network to another.

[0042] Please also see Figure 1, an example schematic diagram of file ferrying is provided for an embodiment of the present application, the initiator network and the receiving network are two isolated and independent networks, the initiator cloud disk is a cloud disk in the initiator network, and the receiving cloud disk is a cloud disk in the receiving network. The file sending device can send data files in the initiator cloud disk to the receiving cloud disk, and the file receiving device can receive the data files sent by the initiator cloud disk and save the data files in the receiving cloud disk. The file sending device can be the initiator cloud disk of the initiator network, or it can be a module in the initiator cloud disk for implementing the file ferrying method, or it can be a device in the initiator network that is connected to the initiator cloud disk and controls the initiator cloud disk to implement the file ferrying method. Similarly, the file receiving device can be the receiving cloud disk in the receiving network, or it can be a module in the receiving cloud disk for implementing the file ferrying method, or it can be a device in the receiving network that is connected to the receiving cloud disk and controls the receiving cloud disk to implement the file ferrying method.

[0043] The mutually isolated networks can be physically isolated or logically isolated. Physical isolation is a technical means of isolating the initiator network from the receiver network by physical methods to avoid the risk of intrusion or information leakage. The initiator network and the receiver are completely isolated in the physical connection of the network, and there is no common storage information. Logical isolation is mainly achieved through a logical isolator, which is an isolation component between different networks. The isolated two ends still have a physical data channel connection, but technical means are used to ensure that there is no data channel between the isolated two ends. If the initiator network and the receiver network are physically isolated, a network gate is required to realize the file ferry between the initiator network and the receiver network. The network gate is an information security device that uses a solid-state switch read-write medium with multiple control functions to connect two independent host systems. Since the two independent host systems are isolated by the network gate, there is no physical connection, logical connection and information transmission protocol for communication between the systems, and there is no information exchange based on the protocol, but only non-protocol ferrying in the form of data files. If the initiator network and the receiver network are logically isolated, the file receiving device needs to obtain the firewall authority of the initiator network to obtain data files from the initiator network.

[0044] The user can initiate a ferry request to the file sending device. The ferry request may include the ferry data file in the initiator cloud disk, the receiving end network and the receiving end cloud disk corresponding to the ferry request. The ferry data file is the data file that the user wants to send to the receiving end cloud disk, such as Figure 1As shown, the ferry data files corresponding to the user's ferry request can be data files in folder 1 and folder 2, namely file A, file B, file C, file D and file E. It can be understood that when transmitting data files, the network gate will only transfer the data files from one end of the network to the other end of the network, and will not pay attention to the target path of the data file storage. For example, if the data files in folder 1 and folder 2 are transferred from the initiating network to the receiving network through the network gate, the receiving network will receive scattered files A, file B, file C, file D and file E after the transmission, and the files will not be saved in the corresponding folders respectively. The files are scattered during the transmission process, which will bring a bad user experience and cause trouble to the user's work and life. The target path can be a hierarchical relationship between files and folders, such as Figure 1 The hierarchical relationship in the ferry data file is "file A, file B and file C are in folder 1, file D and file E are in folder 2", that is, the target path is "file A, file B and file C are saved in folder 1, file D and file E are saved in folder 2", the file sending device can generate a ferry configuration file according to the target path of the ferry data file, and then send the ferry data file and the ferry configuration file together to the file receiving device of the receiving end network. The file receiving device can save the ferry data file in the receiving end cloud disk according to the target path in the ferry configuration file, such as Figure 1 As shown, files A, B, and C in the receiving end cloud disk are in folder 1, and files D and E are in folder 2, which preserves the hierarchical relationship of the ferry data files in the initiator end cloud disk.

[0045] The ferry configuration file may also include file metadata (Metadata) of the ferry data file. File metadata is data that describes data, mainly information that describes data attributes, and is used to support functions such as indicating storage location, historical data, resource search, and file records. For example, in addition to including the hierarchical relationship of the ferry data file, the ferry configuration file may also record the file transfer path of this file ferry, such as the initiator cloud disk of the ferry data file, and the storage path of the ferry data file in the initiator cloud disk, as well as the receiving cloud disk corresponding to the ferry data file, and the storage path of the ferry data file in the receiving cloud disk. File metadata may also include the file size and file name of the ferry data file, which can be used to verify the integrity of the ferry data file.

[0046] The file ferrying method provided by the present application is described in detail below with reference to specific embodiments.

[0047] See also Figure 2 , which is a flowchart of a file ferrying method provided in an embodiment of the present application. Figure 2As shown, the embodiment of the present application describes a file ferrying method in combination with an initiating cloud disk and a receiving cloud disk, and the method may include the following steps S101-S104.

[0048] S101, the initiating end cloud disk determines the ferry data file corresponding to the ferry request initiated by the user, and obtains the ferry configuration file of the ferry data file.

[0049] Specifically, when a user wants to send a ferry data file in the initiator cloud disk of the initiator network to the receiving cloud disk of the receiving network, a ferry request can be initiated to the initiator cloud disk. The ferry request can include the ferry data file for which the file is to be ferryed, as well as the receiving network and the receiving cloud disk that receive the ferry data file. The initiator cloud disk can determine the ferry data file in the initiator cloud disk based on the ferry request initiated by the user, and can obtain the ferry configuration file in the ferry data file. In order to prevent the ferry data file from becoming scattered and disordered after being sent to the receiving cloud disk, the ferry configuration file can include the target path of the ferry data file, and the ferry configuration file can be sent to the receiving cloud disk together with the ferry data file. The receiving cloud disk can save the ferry data file according to the target path in the ferry configuration file.

[0050] S102, the initiating end cloud disk sends the ferry data file and the ferry configuration file to the ferry folder of the initiating end network.

[0051] Specifically, the initiator cloud disk can send the ferry data file and the ferry configuration file to the ferry folder of the initiator network. It can be understood that the ferry data file and the ferry configuration file are one-to-one corresponding, so the initiator cloud disk can package the ferry data file and the ferry configuration file and send them to the ferry folder.

[0052] The ferry folder can be a folder in the initiator cloud disk that is specifically used to store ferry data files and ferry configuration files corresponding to the ferry data files, or a file server that is specifically used to store ferry data files and ferry configuration files corresponding to the ferry data files. It can be used to distinguish ferry data files from other data files to avoid sending erroneous data files without file ferrying permissions to other networks, resulting in data leakage.

[0053] S103, the receiving end cloud disk obtains the ferry data file and the ferry configuration file from the ferry folder of the initiating end network.

[0054] Specifically, the receiving-end cloud disk of the receiving-end network obtains the ferry data file and the ferry configuration file from the ferry folder of the initiating-end network. It can be understood that the files in the ferry folder are all ferry data files to be sent to the receiving-end cloud disk and the ferry configuration files corresponding to the ferry data files. The receiving-end cloud disk can obtain the files in the ferry folder, or the initiating-end cloud disk can send all the files in the ferry folder to the receiving-end cloud disk.

[0055] S104, the receiving end cloud disk saves the ferry data file based on the ferry configuration file.

[0056] Specifically, the receiving-end cloud disk can save and process the ferry data file based on the ferry configuration file. For example, the ferry configuration file can include the target path of the ferry data file. The receiving-end cloud disk saves the ferry data file process based on the target path, thereby restoring the file level of the ferry data file at the time of the initiating-end cloud disk in the receiving-end cloud disk. After the receiving-end cloud disk saves and processes the ferry data file, it can return the ferry result to the initiating-end cloud disk. The ferry result is used to inform the initiating-end cloud disk that the ferry data file has been sent to the receiving-end cloud disk and saved. After receiving the ferry result, the initiating-end cloud disk can delete the ferry data file in the ferry folder and the ferry configuration file corresponding to the ferry data file.

[0057] In an embodiment of the present application, the initiating cloud disk determines the ferry data file corresponding to the ferry request initiated by the user, obtains the ferry configuration file of the ferry data file, sends the ferry data file and the ferry configuration file to the ferry folder of the initiating network, and the receiving cloud disk obtains the ferry data file and the ferry configuration file from the ferry folder of the initiating network, and the receiving cloud disk saves and processes the ferry data file based on the ferry configuration file. By sending the ferry configuration file together with the ferry data file to the receiving cloud disk, while realizing the ferrying of cloud disk files between different independent networks, the ferry configuration file can be used to ensure the hierarchical relationship in the ferry data file, avoiding the confusion of the file content after the file is ferryed, and improving the orderliness of the file ferrying.

[0058] See also Figure 3 , which is a flowchart of a file ferrying method provided in an embodiment of the present application. Figure 3 As shown, the embodiment of the present application describes a file ferrying method in combination with an initiating cloud disk and a receiving cloud disk, and the method may include the following steps S201-S209.

[0059] S201, the initiating cloud disk receives a ferry request initiated by a user.

[0060] Specifically, when a user wants to send a ferrying data file in the initiator cloud disk of the initiator network to the receiving cloud disk of the receiving network, a ferrying request can be initiated to the initiator cloud disk. The ferrying request can include the ferrying data file information to be ferryed, as well as at least one of the receiving network information and the receiving cloud disk information for receiving the ferrying data file.

[0061] Optionally, users can automatically generate a ferry request by filling in the ferry process form in the initiator cloud disk. The ferry process form can include ferry data file information, receiving end network information and receiving end cloud disk information, and can also include user information, etc. Please refer to Figure 4 , an example schematic diagram of a ferry process form is provided for the embodiment of the present application. The initiating end cloud disk can provide the user with a ferry process form. The user can select the ferry data file that he wants to ferry in the ferry process form, and fill in his own user information, application date, and the receiving end network and receiving end cloud disk to which he wants to ferry the file, such as Figure 4 As shown, the ferry process form shows that user A wants to send file A in folder 1 and file D in folder 2 to B cloud disk of network B on July 10, 2020, that is, the ferry data files are file A in folder 1 and file D in folder 2, the receiving network is network B, and the receiving cloud disk is cloud disk B.

[0062] S202, the initiating end cloud disk reviews and processes the ferry request.

[0063] Specifically, there must be private data that cannot be circulated between independent networks, so the initiating cloud disk needs to review the ferry request. Only after the review is passed can the initiating cloud disk ferry the ferry data file. For example, if the review is passed, the initiating cloud disk can obtain a confirmation ferry instruction for the ferry request. The confirmation ferry instruction is used to confirm that the ferry data file corresponding to the ferry request can be ferryed, and instruct the initiating cloud disk to send the ferry data file to the receiving cloud disk. If there is no confirmation ferry instruction, the ferry data file corresponding to the ferry request cannot be ferryed.

[0064] Optionally, the review process may be to review the ferry data file, user information, request date, receiving end network and receiving end cloud disk in the ferry request. If the ferry data file meets the preset ferryable file range, the user information has ferrying authority, the request date meets the preset ferrying date range, the receiving end network is the preset ferryable network, and the receiving end cloud disk is the preset ferryable cloud disk, then the ferry request can be reviewed and processed, wherein the preset ferryable file range, ferrying authority, preset ferrying date range, preset ferryable network, and preset ferryable cloud disk are the initial settings of the initiating end cloud disk, or the settings of relevant staff. If the ferry request meets these conditions at the same time, it can be reviewed and processed.

[0065] Optionally, the initiator cloud disk can send the ferry request to relevant staff for review and processing. Manual review can also carefully review the content of the ferry data file to avoid data leakage. If the ferry request passes the review and processing of the relevant staff, the relevant staff can send a confirmation ferry instruction for the ferry request to the initiator cloud disk. In order to facilitate the manual review and processing of the relevant staff, the initiator cloud disk can send the ferry process form to the relevant staff for review and processing, making the ferry request more intuitive and improving the review and processing efficiency of the relevant staff.

[0066] S203, the initiating end cloud disk determines the ferry data file corresponding to the ferry request initiated by the user.

[0067] Specifically, the initiating-end cloud disk may determine the ferry data file that the user wants to ferry in the initiating-end cloud disk according to the ferry request initiated by the user.

[0068] S204, the initiating end cloud disk obtains file metadata of the ferry data file, obtains the target path of the ferry data file, and generates a ferry configuration file based on the file metadata and the target path.

[0069] Specifically, the initiator cloud disk can obtain the file metadata of the ferry data file. File metadata is data that describes data, mainly information that describes data attributes, and is used to support functions such as indicating storage location, historical data, resource search, and file records. For example, file metadata can include the file size and file name of the ferry data file, which can be used to verify the integrity of the ferry data file. The initiator cloud disk can also obtain the target path of the ferry data file, which is used to instruct the receiving cloud disk to save the ferry data file based on the target path to avoid the ferry data file being scattered and disordered. The initiator cloud disk can generate a ferry configuration file based on the file metadata and the target path.

[0070] Optionally, the file metadata may also include a Secure Hash Algorithm 1 (SHA-1) value calculated based on the ferry data file. The SHA-1 value is an irreversible value used to verify whether the ferry data file has been modified.

[0071] S205, the initiating end cloud disk sends the ferry data file and the ferry configuration file to the ferry folder of the initiating end network.

[0072] Specifically, the initiator cloud disk can send the ferry data file and the ferry configuration file to the ferry folder of the initiator network. It can be understood that the ferry data file and the ferry configuration file are one-to-one corresponding, so the initiator cloud disk can package the ferry data file and the ferry configuration file and send them together to the ferry folder. The ferry folder can be a folder in the initiator cloud disk specifically used to store ferry data files and ferry configuration files corresponding to the ferry data files, or it can be a file server specifically used to store ferry data files and ferry configuration files corresponding to the ferry data files. It can be used to distinguish ferry data files from other data files to avoid sending erroneous data files without file ferrying permissions to other networks, resulting in data leakage.

[0073] It can be understood that a plurality of ferry data files and ferry configuration files corresponding to the ferry data files may be stored in the ferry folder, and the ferry data files and their corresponding ferry configuration files may be packaged and stored in the ferry folder.

[0074] S206, the receiving end cloud disk obtains the ferry data file and the ferry configuration file from the ferry folder of the initiating end network.

[0075] Specifically, the receiving-end cloud disk of the receiving-end network obtains the ferry data file and the ferry configuration file from the ferry folder of the initiating-end network. It can be understood that the files in the ferry folder are all ferry data files to be sent to the receiving-end cloud disk and the ferry configuration files corresponding to the ferry data files. The receiving-end cloud disk can obtain the files in the ferry folder, or the initiating-end cloud disk can send all the files in the ferry folder to the receiving-end cloud disk.

[0076] Optionally, mutually isolated networks may be physically isolated or logically isolated. Physical isolation and logical isolation are different network isolation technical means, so there are different file sending methods corresponding to different network isolation technical means.

[0077] If there is physical isolation between the initiator network and the receiver network, in addition to the ferry folder in the initiator cloud disk, there can also be a target folder in the receiver cloud disk. The initiator cloud disk can send the files in the ferry folder to the target folder through the network gate. Figure 5 , a flowchart of a file sending method under physical isolation is provided for an embodiment of the present application. The file sending method may include the following steps S301-S302.

[0078] S301, the cloud disk at the initiating end uses a network gate to send the files in the ferry folder to the target folder in the receiving end network.

[0079] Specifically, if there is physical isolation between the initiating network and the receiving network, there is a network gate between the initiating network and the receiving network so that there is no information transmission protocol or information exchange between the initiating network and the receiving network. The network gate can also allow non-protocol ferrying between the initiating network and the receiving network in the form of data files. Therefore, the cloud disk at the sending end can use the network gate to send the files in the ferrying folder to the target folder in the receiving network. The target folder can be a folder in the cloud disk at the receiving end that is specifically used to store files sent by the network gate, or it can be a file server that is specifically used to store files sent by the network gate.

[0080] S302, the receiving end cloud disk obtains the ferry data file and the ferry configuration file from the target folder in the receiving end network.

[0081] Specifically, the target folder exists in the receiving end network, and the receiving end cloud disk can directly obtain the ferry data file and the ferry configuration file corresponding to the ferry data file from the target folder of the receiving end network.

[0082] Optionally, since the network gate is constantly transmitting data files between the initiator network and the receiver network, if the network gate sends a prompt message to the receiver cloud disk every time it transmits a ferry data file, prompting the receiver cloud disk to obtain the ferry data file, the network gate will frequently send prompt messages, resulting in excessive power consumption of the network gate. Therefore, the receiver cloud disk can periodically query the target folder whether there are ferry data files and ferry configuration files to be sent to the receiver cloud disk. For example, the receiver cloud disk can query the target folder every one minute whether there are ferry data files and ferry configuration files to be sent to the receiver cloud disk. If so, the ferry data files and ferry configuration files are obtained from the target folder.

[0083] If there is a logical isolation between the initiator network and the receiver network, the receiver cloud disk can obtain the access rights of the initiator network. The access rights are used to allow the receiver cloud disk to obtain files in the shuttle folder. Figure 6 , a flowchart of a file sending method under logical isolation is provided for an embodiment of the present application. The file sending method may include the following steps S401-S402.

[0084] S401, the receiving end cloud disk obtains the access permission of the initiating end network.

[0085] Specifically, the receiving end cloud disk can obtain the access rights of the initiating end network, for example, the firewall access rights of the initiating end network. However, the access rights do not allow the receiving end cloud disk to access all files in the initiating end network, but only the files in the ferry folder of the initiating end network.

[0086] S402, the receiving-end cloud disk sends a file query request to the initiating-end cloud disk of the initiating-end network based on the access permission.

[0087] Specifically, the receiving end cloud disk can send a file query request to the initiating end cloud disk of the initiating end network based on the access rights, so as to query whether there are ferry data files and ferry configuration files to be sent to the receiving end cloud disk in the ferry folder.

[0088] Optionally, the receiving-end cloud disk may periodically send a file query request to the initiating-end cloud disk of the initiating-end network based on access rights. For example, the receiving-end cloud disk may send a file query request to the initiating-end cloud disk once every minute.

[0089] S403, the initiating end cloud disk sends the files in the ferry folder to the receiving end cloud disk.

[0090] Specifically, after the initiating-end cloud disk receives the file query request sent by the receiving-end cloud disk based on the access permission, the file in the ferry folder can be sent to the receiving-end cloud disk.

[0091] Optionally, after receiving the file query request sent by the receiving cloud disk based on the access permission, the initiating cloud disk can query the unsent files in the ferry folder, and then send the unsent files to the receiving cloud disk.

[0092] S207, the receiving end cloud disk obtains the file metadata and target path in the ferry configuration file.

[0093] Specifically, after receiving the ferry data file and the ferry configuration file corresponding to the ferry data file sent by the initiating cloud disk, the receiving-end cloud disk can obtain the file metadata and the target path in the ferry configuration file.

[0094] S208: Perform integrity verification on the ferry data file based on the file metadata.

[0095] Specifically, the file metadata may include the file name, file size, etc. of the ferry data file. The receiving cloud disk may perform integrity verification on the ferry data file based on the file metadata. For example, if the file name and file size of the file metadata are consistent with the file metadata, it means that the ferry data file has passed the integrity verification.

[0096] Optionally, if the file metadata also includes the SHA-1 value of the ferry data file, the receiving cloud disk can also determine whether the ferry data file has been changed based on the SHA-1 value. If the ferry data file has not been changed, the ferry data file has passed the integrity check.

[0097] S209: If the ferry data file passes the integrity check, the receiving end cloud disk saves the ferry data file based on the target path.

[0098] Specifically, if the receiving-end cloud disk determines that the ferry data file has passed the integrity check, the receiving-end disk can save the ferry data file based on the target path. The target path of the ferry data file at the initiating-end cloud disk is restored in the receiving-end cloud disk. After the receiving-end cloud disk saves the ferry data file, it can return the ferry result to the initiating-end cloud disk. At this time, the ferry result is that the file is successfully ferryed, which is used to inform the initiating-end cloud disk that the ferry data file has been sent to the receiving-end cloud disk and saved. After receiving the ferry result, the initiating-end cloud disk can delete the ferry data file in the ferry folder and the ferry configuration file corresponding to the ferry data file.

[0099] Optionally, if the ferry data file fails the integrity check, it means that some files of the ferry data file are lost during the file ferrying process, or the file is damaged. The receiving cloud disk can also return the ferry result to the initiating cloud disk. At this time, the ferry result is a file ferry failure, which is used to inform the initiating cloud disk that the ferry file has not been completely sent to the receiving cloud disk. After receiving the ferry, the initiating cloud disk can send the ferry data file in the ferry folder and the ferry configuration file corresponding to the ferry data file to the receiving cloud disk again.

[0100] In an embodiment of the present application, the initiating cloud disk receives the ferry request initiated by the user, and the initiating cloud disk reviews and processes the ferry request to obtain a confirmation ferry instruction for the ferry request. Only the ferry request that has passed the review process can be confirmed for ferrying. The initiating cloud disk can also provide a ferry process form to facilitate the relevant staff to intuitively review and process, thereby improving the efficiency of the review process. The initiating cloud disk determines the ferry data file corresponding to the ferry request initiated by the user, the initiating cloud disk obtains the file metadata of the ferry data file, obtains the target path of the ferry data file, and generates a ferry configuration file based on the file metadata and the target path. The file metadata can be used to verify the integrity of the ferry data file. The initiating cloud disk sends the ferry data file and the ferry configuration file to the ferry folder of the initiating network. The receiving cloud disk obtains the ferry data file and the ferry configuration file from the ferry folder of the initiating network. The receiving cloud disk obtains the target path in the ferry configuration file, obtains the file metadata in the ferry configuration file, and performs integrity verification on the ferry data file based on the file metadata, thereby ensuring the integrity of the ferry data file and avoiding file damage or loss during the ferrying process. If the ferry data file passes the integrity verification, the receiving cloud disk saves the ferry data file based on the target path. By sending the ferry configuration file and the ferry data file to the receiving cloud disk together, the ferry configuration file can be used to ensure the hierarchical relationship in the ferry data file while realizing the ferrying of cloud disk files between different independent networks, avoiding the confusion of file content after file ferrying, and improving the orderliness of file ferrying. In addition, there are different file transmission methods for logical isolation and physical isolation. In physical isolation, file servers can be set up on both sides of the network to realize the decoupling of cloud disk and network gate, making file ferrying more flexible.

[0101] See also Figure 7 , which is a flowchart of a file ferrying method provided in an embodiment of the present application. Figure 7 As shown, the embodiment of the present application describes a method for ferrying files in conjunction with the initiating cloud disk side, and the method may include the following steps S501-S502.

[0102] S501, determining a ferry data file corresponding to a ferry request initiated by a user, and acquiring a ferry configuration file of the ferry data file.

[0103] Specifically, when a user wants to send a ferry data file in the initiator cloud disk of the initiator network to the receiving cloud disk of the receiving network, a ferry request can be initiated to the initiator cloud disk. The ferry request can include the ferry data file for which the file is to be ferryed, as well as the receiving network and the receiving cloud disk that receive the ferry data file. The initiator cloud disk can determine the ferry data file in the initiator cloud disk based on the ferry request initiated by the user, and can obtain the ferry configuration file in the ferry data file. In order to prevent the ferry data file from becoming scattered and disordered after being sent to the receiving cloud disk, the ferry configuration file can include the target path of the ferry data file, and the ferry configuration file can be sent to the receiving cloud disk together with the ferry data file. The receiving cloud disk can save the ferry data file according to the target path in the ferry configuration file.

[0104] S502, sending the ferry data file and the ferry configuration file to the ferry folder of the initiating end network.

[0105] Specifically, the initiating cloud disk can send the ferry data file and the ferry configuration file to the ferry folder of the initiating network, so that the receiving cloud disk of the receiving network saves the ferry data file based on the ferry configuration file, and the receiving cloud disk of the receiving network obtains the ferry data file and the ferry configuration file from the ferry folder of the initiating network. It can be understood that the files in the ferry folder are all ferry data files to be sent to the receiving cloud disk and the ferry configuration files corresponding to the ferry data files. The receiving cloud disk can obtain the files in the ferry folder, or the initiating cloud disk can send all the files in the ferry folder to the receiving cloud disk. The ferry data file and the ferry configuration file are one-to-one corresponding, so the initiating cloud disk can package the ferry data file and the ferry configuration file and send them to the ferry folder together.

[0106] The ferry folder can be a folder in the initiator cloud disk that is specifically used to store ferry data files and ferry configuration files corresponding to the ferry data files, or a file server that is specifically used to store ferry data files and ferry configuration files corresponding to the ferry data files. It can be used to distinguish ferry data files from other data files to avoid sending erroneous data files without file ferrying permissions to other networks, resulting in data leakage.

[0107] In an embodiment of the present application, the ferry data file corresponding to the ferry request initiated by the user is determined, the ferry configuration file of the ferry data file is obtained, and the ferry data file and the ferry configuration file are sent to the ferry folder of the initiating network, so that the receiving cloud disk of the receiving network saves the ferry data file based on the ferry configuration file. By sending the ferry configuration file and the ferry data file to the receiving cloud disk together, while realizing the ferrying of cloud disk files between different independent networks, the ferry configuration file can be used to ensure the hierarchical relationship in the ferry data file, avoiding confusion of file content after file ferrying, and improving the orderliness of file ferrying.

[0108] See also Figure 8 , which is a flowchart of a file ferrying method provided in an embodiment of the present application. Figure 8 As shown, the embodiment of the present application describes a method for ferrying files in conjunction with the initiating cloud disk side, and the method may include the following steps S601-S605.

[0109] S601, receiving a ferry request initiated by a user.

[0110] Specifically, when a user wants to send a ferry data file in the initiator cloud disk of the initiator network to the receiving cloud disk of the receiving network, he can initiate a ferry request to the initiator cloud disk. The ferry request can include the ferry data file for which he wants to ferry the file, as well as the receiving network and receiving cloud disk that receive the ferry data file.

[0111] Optionally, the user can automatically generate a ferry request by filling in a ferry process form in the initiator cloud disk. The ferry process form may include the ferry data file, the receiving end network and the receiving end cloud disk, and may also include the user's user information.

[0112] S602, review and process the ferry request.

[0113] Specifically, there must be private data between independent networks that cannot be circulated between each other, so the initiating cloud disk needs to review and process the ferry request. If the review process passes, the initiating cloud disk can obtain a confirmation ferry instruction for the ferry request. The confirmation ferry instruction is used to confirm that the ferry data file corresponding to the ferry request can be ferried, and instruct the initiating cloud disk to send the ferry data file to the receiving cloud disk. If there is no confirmation ferry instruction, the ferry data file corresponding to the ferry request cannot be ferried.

[0114] Optionally, the review process may be to review the ferry data file, user information, request date, receiving end network and receiving end cloud disk in the ferry request. If the ferry data file meets the preset ferryable file range, the user information has ferrying authority, the request date meets the preset ferrying date range, the receiving end network is the preset ferryable network, and the receiving end cloud disk is the preset ferryable cloud disk, then the ferry request can be reviewed and processed, wherein the preset ferryable file range, ferrying authority, preset ferrying date range, preset ferryable network, and preset ferryable cloud disk are the initial settings of the initiating end cloud disk, or the settings of relevant staff. If the ferry request meets these conditions at the same time, it can be reviewed and processed.

[0115] Optionally, the initiator cloud disk can send the ferry request to relevant staff for review and processing. Manual review can also carefully review the content of the ferry data file to avoid data leakage. If the ferry request passes the review and processing of the relevant staff, the relevant staff can send a confirmation ferry instruction for the ferry request to the initiator cloud disk. In order to facilitate the manual review and processing of the relevant staff, the initiator cloud disk can send the ferry process form to the relevant staff for review and processing, making the ferry request more intuitive and improving the review and processing efficiency of the relevant staff.

[0116] S603: Determine the ferry data file corresponding to the ferry request initiated by the user.

[0117] Specifically, the initiating-end cloud disk may determine the ferry data file that the user wants to ferry in the initiating-end cloud disk according to the ferry request initiated by the user.

[0118] S604, obtaining file metadata of the ferry data file, obtaining a target path of the ferry data file, and generating a ferry configuration file based on the file metadata and the target path.

[0119] Specifically, the initiator cloud disk can obtain the file metadata of the ferry data file. File metadata is data that describes data, mainly information that describes data attributes, and is used to support functions such as indicating storage location, historical data, resource search, and file records. For example, file metadata can include the file size and file name of the ferry data file, which can be used to verify the integrity of the ferry data file. The initiator cloud disk can also obtain the target path of the ferry data file, which is used to instruct the receiving cloud disk to save the ferry data file based on the target path to avoid the ferry data file being scattered and disordered. The initiator cloud disk can generate a ferry configuration file based on the file metadata and the target path.

[0120] Optionally, the file metadata may also include a SHA-1 value calculated based on the ferry data file. The SHA-1 value is an irreversible value, which is used to verify whether the ferry data file has been modified.

[0121] S605, sending the ferry data file and the ferry configuration file to the ferry folder of the initiating end network.

[0122] Specifically, the initiating cloud disk can send the ferry data file and the ferry configuration file to the ferry folder of the initiating network, so that the receiving cloud disk of the receiving network saves the ferry data file based on the ferry configuration file, and the receiving cloud disk of the receiving network obtains the ferry data file and the ferry configuration file from the ferry folder of the initiating network. It can be understood that the files in the ferry folder are all ferry data files to be sent to the receiving cloud disk and the ferry configuration files corresponding to the ferry data files. The receiving cloud disk can obtain the files in the ferry folder, or the initiating cloud disk can send all the files in the ferry folder to the receiving cloud disk. The ferry data file and the ferry configuration file are one-to-one corresponding, so the initiating cloud disk can package the ferry data file and the ferry configuration file and send them to the ferry folder together.

[0123] The ferry folder can be a folder in the initiator cloud disk that is specifically used to store ferry data files and ferry configuration files corresponding to the ferry data files, or a file server that is specifically used to store ferry data files and ferry configuration files corresponding to the ferry data files. It can be used to distinguish ferry data files from other data files to avoid sending erroneous data files without file ferrying permissions to other networks, resulting in data leakage.

[0124] It can be understood that a plurality of ferry data files and ferry configuration files corresponding to the ferry data files may be stored in the ferry folder, and the ferry data files and their corresponding ferry configuration files may be packaged and stored in the ferry folder.

[0125] Optionally, mutually isolated networks may be physically isolated or logically isolated. Physical isolation and logical isolation are different network isolation technical means, so there are different file sending methods corresponding to different network isolation technical means.

[0126] If there is a physical isolation between the initiating network and the receiving network, there is a network gate between the initiating network and the receiving network so that there is no information transmission protocol or information exchange between the initiating network and the receiving network. The network gate can also allow non-protocol ferrying between the initiating network and the receiving network in the form of data files. Therefore, the cloud disk on the sending end can use the network gate to send the files in the ferrying folder to the target folder in the receiving network, and the cloud disk on the receiving end obtains the ferrying data file and the ferrying configuration folder from the target folder. The target folder can be a folder in the cloud disk on the receiving end that is specifically used to store files sent by the network gate, or it can be a file server that is specifically used to store files sent by the network gate.

[0127] If there is a logical isolation between the initiator network and the receiver network, the receiver cloud disk can obtain the access rights of the initiator network. After the initiator cloud disk receives the file query request sent by the receiver cloud disk based on the access rights, the file in the ferry folder can be sent to the receiver cloud disk.

[0128] In an embodiment of the present application, the initiating cloud disk receives the ferry request initiated by the user, and the initiating cloud disk reviews and processes the ferry request to obtain a confirmation ferry instruction for the ferry request. Only the ferry request that has passed the review process can confirm the ferry. The initiating cloud disk can also provide a ferry process form to facilitate the relevant staff to intuitively review and process, thereby improving the review and processing efficiency. The initiating cloud disk determines the ferry data file corresponding to the ferry request initiated by the user, and the initiating cloud disk obtains the file metadata of the ferry data file, obtains the target path of the ferry data file, and generates a ferry configuration file based on the file metadata and the target path. The file metadata can be used to verify the integrity of the ferry data file. The initiating cloud disk sends the ferry data file and the ferry configuration file to the ferry folder of the initiating network, so that the receiving cloud disk of the receiving network saves the ferry data file based on the ferry configuration file. While realizing the ferrying of cloud disk files between different independent networks, the ferry configuration file can be used to ensure the hierarchical relationship in the ferry data file, avoiding the confusion of file content after file ferrying, and improving the orderliness of file ferrying. There are different file transfer methods for logical isolation and physical isolation. In physical isolation, file servers can be set up on both sides of the network to decouple the cloud disk and the network gate, making file transfer more flexible.

[0129] See also Fig. 9 , which is a flowchart of a file ferrying method provided in an embodiment of the present application. Fig. 9 As shown, the embodiment of the present application describes a file ferrying method in conjunction with the receiving end cloud disk side, and the method may include the following steps S701-S702.

[0130] S701, obtaining a ferry data file and a ferry configuration file from a ferry folder of the initiating end network.

[0131] Specifically, the initiator cloud disk can send the ferry data file and ferry configuration file in the ferry folder to the receiver cloud disk, and the receiver cloud disk can receive the ferry data file in the ferry folder of the initiator network and the ferry configuration file corresponding to the ferry data file.

[0132] S702: Save the ferry data file based on the ferry configuration file.

[0133] Specifically, the receiving-end cloud disk can save and process the ferry data file based on the ferry configuration file. For example, the ferry configuration file can include the target path of the ferry data file. The receiving-end cloud disk saves the ferry data file process based on the target path, thereby restoring the hierarchical relationship of the ferry data file at the time of the initiating-end cloud disk in the receiving-end cloud disk. After the receiving-end cloud disk saves and processes the ferry data file, it can return the ferry result to the initiating-end cloud disk. The ferry result is used to inform the initiating-end cloud disk that the ferry data file has been sent to the receiving-end cloud disk and saved. After receiving the ferry result, the initiating-end cloud disk can delete the ferry data file in the ferry folder and the ferry configuration file corresponding to the ferry data file.

[0134] In the embodiment of the present application, the ferry data file and the ferry configuration file are obtained from the ferry folder of the initiating network, and the ferry data file is saved and processed based on the ferry configuration file. By sending the ferry configuration file and the ferry data file to the receiving cloud disk together, while realizing the ferrying of cloud disk files between different independent networks, the ferry configuration file can be used to ensure the hierarchical relationship in the ferry data file, avoiding the confusion of file content after file ferrying, and improving the orderliness of file ferrying.

[0135] See also Fig.10 , which is a flowchart of a file ferrying method provided in an embodiment of the present application. Fig.10 As shown, the embodiment of the present application describes a file ferrying method in conjunction with the receiving end cloud disk side, and the method may include the following steps S801-S804.

[0136] S801, obtaining a ferry data file and a ferry configuration file from a ferry folder of the initiating end network.

[0137] Specifically, the initiator cloud disk can send the ferry data file and ferry configuration file in the ferry folder to the receiver cloud disk, and the receiver cloud disk can receive the ferry data file in the ferry folder of the initiator network and the ferry configuration file corresponding to the ferry data file.

[0138] Optionally, mutually isolated networks may be physically isolated or logically isolated. Physical isolation and logical isolation are different network isolation technical means, so there are different file sending methods corresponding to different network isolation technical means.

[0139] If there is a physical isolation between the initiator network and the receiver network, the initiator cloud disk uses the network gate to send the files in the ferry folder to the target folder in the receiver network. The target folder can be a folder in the receiver cloud disk specifically used to store files sent by the network gate, or it can be a file server specifically used to store files sent by the network gate. The target folder exists in the receiver network, and the receiver cloud disk can directly obtain the ferry data file and the ferry configuration file corresponding to the ferry data file from the target folder of the receiver network.

[0140] If there is a logical isolation between the initiator network and the receiver network, the receiver cloud disk can obtain the access rights of the initiator network, for example, it can obtain the firewall access rights of the initiator network. It can be immediately noted that the access rights do not allow the receiver cloud disk to access all files in the initiator network, but only the files in the ferry folder of the initiator network. Based on the access rights, the receiver cloud disk can send a file query request to the initiator cloud disk of the initiator network to query whether there are ferry data files and ferry configuration files to be sent to the receiver cloud disk in the ferry folder. After the initiator cloud disk receives the file query request sent by the receiver cloud disk based on the access rights, it can send the files in the ferry folder to the receiver cloud disk.

[0141] S802, obtaining file metadata and target path in the ferry configuration file.

[0142] Specifically, after receiving the ferry data file and the ferry configuration file corresponding to the ferry data file sent by the initiating cloud disk, the receiving-end cloud disk can obtain the file metadata and the target path in the ferry configuration file.

[0143] Optionally, the file metadata may include the file name, file size, SHA-1 value, etc. of the ferry data file.

[0144] S803: Perform integrity verification on the ferry data file based on the file metadata.

[0145] Specifically, the receiving cloud disk can perform integrity verification on the ferry data file based on the file metadata. For example, if the file name and file size of the file metadata are consistent with the file metadata, it means that the ferry data file has passed the integrity verification.

[0146] Optionally, if the file metadata also includes the SHA-1 value of the ferry data file, the receiving cloud disk can also determine whether the ferry data file has been changed based on the SHA-1 value. If the ferry data file has not been changed, the ferry data file has passed the integrity check.

[0147] S804: If the ferry data file passes the integrity check, the ferry data file is saved based on the target path.

[0148] Specifically, if the receiving-end cloud disk determines that the ferry data file has passed the integrity check, the receiving-end disk can save the ferry data file based on the target path. The target path of the ferry data file at the initiating-end cloud disk is restored in the receiving-end cloud disk. After the receiving-end cloud disk saves the ferry data file, it can return the ferry result to the initiating-end cloud disk. At this time, the ferry result is that the file is successfully ferryed, which is used to inform the initiating-end cloud disk that the ferry data file has been sent to the receiving-end cloud disk and saved. After receiving the ferry result, the initiating-end cloud disk can delete the ferry data file in the ferry folder and the ferry configuration file corresponding to the ferry data file.

[0149] Optionally, if the ferry data file fails the integrity check, it means that some files of the ferry data file are lost during the file ferrying process, or the file is damaged. The receiving cloud disk can also return the ferry result to the initiating cloud disk. At this time, the ferry result is a file ferry failure, which is used to inform the initiating cloud disk that the ferry file has not been completely sent to the receiving cloud disk. After receiving the ferry, the initiating cloud disk can send the ferry data file in the ferry folder and the ferry configuration file corresponding to the ferry data file to the receiving cloud disk again.

[0150] In an embodiment of the present application, the initiating cloud disk sends the ferry data file and the ferry configuration file to the ferry folder of the initiating network, and sends the files in the ferry folder to the receiving cloud disk of the receiving network. The receiving cloud disk obtains the file metadata and target path in the ferry configuration file, and performs integrity verification on the ferry data file based on the file metadata, thereby ensuring the integrity of the ferry data file and avoiding file damage or loss during the ferrying process. If the ferry data file passes the integrity verification, the receiving cloud disk saves the ferry data file based on the target path. By sending the ferry configuration file and the ferry data file to the receiving cloud disk together, while realizing the ferrying of cloud disk files between different independent networks, the ferry configuration file can be used to ensure the hierarchical relationship in the ferry data file, avoiding the confusion of file content after file ferrying, and improving the orderliness of file ferrying. In addition, there are different file transfer methods for logical isolation and physical isolation. In physical isolation, file servers can be set up on both sides of the network to realize the decoupling of cloud disk and network gate, making file ferrying more flexible.

[0151] The following will be combined with the attached Fig.11 -Attached Fig.12 , the file sending device provided in the embodiment of the present application is introduced in detail. It should be noted that the attached Fig.11 -Attached Fig.12 The file sending device in the present application is used to execute Figure 7 and Figure 8For the convenience of explanation, only the part related to the embodiment of the present application is shown. For the specific technical details not disclosed, please refer to the present application. Figure 7 and Figure 8 The embodiment shown.

[0152] See also Fig.11 , which shows a schematic diagram of the structure of a file sending device provided by an exemplary embodiment of the present application. The file sending device can be implemented as all or part of the device through software, hardware or a combination of both. The device 1 includes a file data acquisition module 11, a file data sending module 12 and a file data ferry module 13.

[0153] The file data acquisition module 11 is used to determine the ferry data file corresponding to the ferry request initiated by the user, and obtain the ferry configuration file of the ferry data file;

[0154] A file data ferry module 12, configured to send the ferry data file and the ferry configuration file to the ferry folder of the initiating end network, so that the receiving end cloud disk of the receiving end network saves the ferry data file based on the ferry configuration file;

[0155] In this embodiment, the ferry data file corresponding to the ferry request initiated by the user is determined, the ferry configuration file of the ferry data file is obtained, and the ferry data file and the ferry configuration file are sent to the ferry folder of the initiating network, so that the receiving cloud disk of the receiving network saves the ferry data file based on the ferry configuration file. By sending the ferry configuration file and the ferry data file to the receiving cloud disk together, while realizing the ferrying of cloud disk files between different independent networks, the ferry configuration file can be used to ensure the hierarchical relationship in the ferry data file, avoiding the confusion of file content after file ferrying, and improving the orderliness of file ferrying.

[0156] See also Fig.12 , which shows a schematic diagram of the structure of a file sending device provided by an exemplary embodiment of the present application. The file sending device can be implemented as all or part of the device through software, hardware or a combination of both. The device 1 includes an audit processing module 13, a file data acquisition module 11, a file data ferry module 12, a network gate ferry module 14 and a request ferry module 15.

[0157] The review processing module 13 is used to receive a ferry request initiated by a user, wherein the ferry request includes at least one of ferry data file information, receiving end network information and receiving end cloud disk information;

[0158] Reviewing and processing the ferry request;

[0159] The file data acquisition module 11 is used to determine the ferry data file corresponding to the ferry request initiated by the user, and obtain the ferry configuration file of the ferry data file;

[0160] Optionally, the file data acquisition module 11 is specifically used to acquire file metadata of the ferry data file and acquire a target path of the ferry data file;

[0161] A ferry configuration file is generated based on the file metadata and the target path.

[0162] A file data ferry module 12, configured to send the ferry data file and the ferry configuration file to the ferry folder of the initiating end network, so that the receiving end cloud disk of the receiving end network saves the ferry data file based on the ferry configuration file;

[0163] The network gate ferry module 14 is used to use the network gate to send the files in the ferry folder to the target folder in the receiving end network, and the receiving end cloud disk obtains the ferry data file and the ferry configuration folder from the target folder.

[0164] The request ferrying module 15 is used to send the files in the ferrying folder to the receiving end cloud disk if a file query request of the receiving end cloud disk in the receiving end network is received.

[0165] In this embodiment, the initiating cloud disk receives the ferry request initiated by the user, and the initiating cloud disk reviews and processes the ferry request to obtain a confirmation ferry instruction for the ferry request. Only the ferry request that has passed the review process can be confirmed for ferrying. The initiating cloud disk can also provide a ferry process form to facilitate the relevant staff to intuitively review and process, thereby improving the review and processing efficiency. The initiating cloud disk determines the ferry data file corresponding to the ferry request initiated by the user, the initiating cloud disk obtains the file metadata of the ferry data file, obtains the target path of the ferry data file, and generates a ferry configuration file based on the file metadata and the target path. The file metadata can be used to verify the integrity of the ferry data file. The initiating cloud disk sends the ferry data file and the ferry configuration file to the ferry folder of the initiating network, and sends the files in the ferry folder to the receiving cloud disk of the receiving network, so that the receiving cloud disk of the receiving network saves the ferry data file based on the ferry configuration file. While realizing the ferrying of cloud disk files between different independent networks, the ferry configuration file can be used to ensure the hierarchical relationship in the ferry data file, avoiding the confusion of file content after file ferrying, and improving the orderliness of file ferrying. In addition, there are different file transfer methods for logical isolation and physical isolation. In the case of physical isolation, file servers can be set up on both sides of the network to realize the decoupling of the cloud disk and the network gate, making file ferrying more flexible.

[0166] Please refer to Fig.13 , which shows a block diagram of the structure of an electronic device provided by an exemplary embodiment of the present application. The electronic device in the present application may include one or more of the following components: a processor 110, a memory 120, an input device 130, an output device 140, and a bus 150. The processor 110, the memory 120, the input device 130, and the output device 140 may be connected via the bus 150.

[0167] The processor 110 may include one or more processing cores. The processor 110 uses various interfaces and lines to connect various parts of the entire electronic device, and executes various functions and processes data of the terminal 100 by running or executing instructions, programs, code sets or instruction sets stored in the memory 120, and calling data stored in the memory 120. Optionally, the processor 110 can be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 110 can integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Among them, the CPU mainly processes the operating system, user pages, and applications; the GPU is responsible for rendering and drawing display content; and the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 110, but may be implemented separately through a communication chip.

[0168] The memory 120 may include a random access memory (RAM) or a read-only memory (ROM). Optionally, the memory 120 includes a non-transitory computer-readable medium (Non-Transitory Computer-Readable Storage Medium). The memory 120 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 120 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc. The operating system may be an Android system, including a system deeply developed based on the Android system, an IOS system developed by Apple, including a system deeply developed based on the IOS system or other systems.

[0169] The memory 120 can be divided into an operating system space and a user space. The operating system runs in the operating system space, and native and third-party applications run in the user space. In order to ensure that different third-party applications can achieve good operating results, the operating system allocates corresponding system resources to different third-party applications. However, the requirements for system resources in different application scenarios in the same third-party application are also different. For example, in the local resource loading scenario, the third-party application has higher requirements for disk reading speed; in the animation rendering scenario, the third-party application has higher requirements for GPU performance. The operating system and third-party applications are independent of each other, and the operating system often cannot perceive the current application scenario of the third-party application in a timely manner, resulting in the operating system being unable to perform targeted system resource adaptation according to the specific application scenario of the third-party application.

[0170] In order for the operating system to distinguish the specific application scenarios of third-party applications, it is necessary to open up data communication between third-party applications and the operating system so that the operating system can obtain the current scenario information of third-party applications at any time, and then perform targeted system resource adaptation based on the current scenario.

[0171] The input device 130 is used to receive input commands or data, and includes but is not limited to a keyboard, a mouse, a camera, a microphone, or a touch device. The output device 140 is used to output commands or data, and includes but is not limited to a display device and a speaker. In one example, the input device 130 and the output device 140 can be combined, and the input device 130 and the output device 140 are touch screen displays.

[0172] The touch display screen can be designed as a full screen, a curved screen or a special-shaped screen. The touch display screen can also be designed as a combination of a full screen and a curved screen, or a combination of a special-shaped screen and a curved screen, which is not limited in the embodiments of the present application.

[0173] In addition, those skilled in the art will appreciate that the structure of the electronic device shown in the above drawings does not constitute a limitation on the electronic device, and the electronic device may include more or fewer components than shown, or combine certain components, or arrange the components differently. For example, the electronic device also includes a radio frequency circuit, an input unit, a sensor, an audio circuit, a wireless fidelity (WiFi) module, a power supply, a Bluetooth module and other components, which will not be described in detail here.

[0174] exist Fig.13 In the electronic device shown, the processor 110 may be used to call the file ferry application stored in the memory 120, and specifically perform the following operations:

[0175] Determine a ferry data file corresponding to a ferry request initiated by a user, and obtain a ferry configuration file of the ferry data file;

[0176] The ferry data file and the ferry configuration file are sent to the ferry folder of the initiating end network, so that the receiving end cloud disk of the receiving end network saves the ferry data file based on the ferry configuration file.

[0177] In one embodiment, before determining the ferry data file corresponding to the ferry request initiated by the user and obtaining the ferry configuration file of the ferry data file, the processor 110 further performs the following operations:

[0178] Receiving a ferry request initiated by a user, wherein the ferry request includes at least one of ferry data file information, receiving end network information, and receiving end cloud disk information;

[0179] The ferry request is reviewed and processed.

[0180] In one embodiment, when executing to obtain the ferry configuration file of the ferry data file, the processor 110 specifically performs the following operations:

[0181] Obtain file metadata of the ferry data file, and obtain a target path of the ferry data file;

[0182] A ferry configuration file is generated based on the file metadata and the target path.

[0183] In one embodiment, after executing the sending of the ferry data file and the ferry configuration file to the ferry folder of the initiating network, the processor 110 further performs the following operations:

[0184] The network gate is used to send the files in the ferry folder to the target folder in the receiving end network, and the receiving end cloud disk obtains the ferry data file and the ferry configuration folder from the target folder.

[0185] In one embodiment, after executing the sending of the ferry data file and the ferry configuration file to the ferry folder of the initiating network, the processor 110 further performs the following operations:

[0186] If a file query request of a receiving-end cloud disk in the receiving-end network is received, the files in the ferry folder are sent to the receiving-end cloud disk.

[0187] In an embodiment of the present application, the initiating cloud disk receives the ferry request initiated by the user, and the initiating cloud disk reviews and processes the ferry request to obtain a confirmation ferry instruction for the ferry request. Only the ferry request that has passed the review process can confirm the ferry. The initiating cloud disk can also provide a ferry process form to facilitate the relevant staff to intuitively review and process, thereby improving the review and processing efficiency. The initiating cloud disk determines the ferry data file corresponding to the ferry request initiated by the user, and the initiating cloud disk obtains the file metadata of the ferry data file, obtains the target path of the ferry data file, and generates a ferry configuration file based on the file metadata and the target path. The file metadata can be used to verify the integrity of the ferry data file. The initiating cloud disk sends the ferry data file and the ferry configuration file to the ferry folder of the initiating network, so that the receiving cloud disk of the receiving network saves the ferry data file based on the ferry configuration file. While realizing the ferrying of cloud disk files between different independent networks, the ferry configuration file can be used to ensure the hierarchical relationship in the ferry data file, avoiding the confusion of file content after file ferrying, and improving the orderliness of file ferrying. There are different file transfer methods for logical isolation and physical isolation. In physical isolation, file servers can be set up on both sides of the network to decouple the cloud disk and the network gate, making file transfer more flexible.

[0188] The following will be combined with the attached Fig.14 , the file receiving device provided in the embodiment of the present application is introduced in detail. It should be noted that the attached Fig.14 The file receiving device in the present application is used to execute Fig. 9 and Fig.10 For the convenience of explanation, only the part related to the embodiment of the present application is shown. For the specific technical details not disclosed, please refer to the present application. Fig. 9 and Fig.10The embodiment shown.

[0189] See also Fig.14 , which shows a schematic diagram of the structure of a file receiving device provided by an exemplary embodiment of the present application. The file receiving device can be implemented as all or part of the device through software, hardware or a combination of both. The device 2 includes a file data receiving module 21 and a storage processing module 22.

[0190] The file data receiving module 21 is used to obtain the ferry data file and the ferry configuration file from the ferry folder of the initiating end network;

[0191] Optionally, the file data receiving module 21 is specifically configured to obtain a ferry data file and a ferry configuration file from a target folder in the receiving end network.

[0192] Optionally, the file data receiving module 21 is specifically used to obtain access rights of the initiating end network;

[0193] Sending a file query request to the initiator cloud disk of the initiator network based on the access permission;

[0194] The ferry data file and the ferry configuration file sent by the initiator cloud disk based on the file query request are obtained.

[0195] The saving processing module 22 is used to save the ferry data file based on the ferry configuration file.

[0196] Optionally, the saving processing module 22 is specifically used to obtain the file metadata and target path in the ferry configuration file;

[0197] Performing integrity check processing on the ferry data file based on the file metadata;

[0198] If the ferry data file passes the integrity check, the ferry data file is saved based on the target path.

[0199] In this embodiment, the initiating cloud disk sends the ferry data file and the ferry configuration file to the ferry folder of the initiating network, and sends the files in the ferry folder to the receiving cloud disk of the receiving network. The receiving cloud disk obtains the target path and file metadata in the ferry configuration file, and performs integrity verification on the ferry data file based on the file metadata, thereby ensuring the integrity of the ferry data file and avoiding file damage or loss during the ferrying process. If the ferry data file passes the integrity verification, the receiving cloud disk saves the ferry data file based on the target path. By sending the ferry configuration file and the ferry data file to the receiving cloud disk together, while realizing the ferrying of cloud disk files between different independent networks, the ferry configuration file can be used to ensure the hierarchical relationship in the ferry data file, avoiding the confusion of file content after file ferrying, and improving the orderliness of file ferrying. In addition, there are different file transmission methods for logical isolation and physical isolation. In physical isolation, file servers can be set up on both sides of the network to realize the decoupling of cloud disk and network gate, making file ferrying more flexible.

[0200] Please refer to Fig.15 , which shows a block diagram of the structure of an electronic device provided by an exemplary embodiment of the present application. The electronic device in the present application may include one or more of the following components: a processor 210, a memory 220, an input device 230, an output device 240, and a bus 250. The processor 210, the memory 220, the input device 230, and the output device 240 may be connected via a bus 250.

[0201] The processor 210 may include one or more processing cores. The processor 210 uses various interfaces and lines to connect various parts of the entire electronic device, and executes various functions and processes data of the electronic device 200 by running or executing instructions, programs, code sets or instruction sets stored in the memory 220, and calling data stored in the memory 220. Optionally, the processor 210 can be implemented in at least one hardware form of DSP, FPGA, and PLA. The processor 210 can integrate one or a combination of CPU, GPU, modem, etc. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing display content; and the modem is used to handle wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 210, but may be implemented separately through a communication chip.

[0202] The memory 220 may include RAM or ROM. Optionally, the memory 220 includes a non-transient computer-readable medium. The memory 220 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 220 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the following various method embodiments, etc. The operating system may be an Android system, including a system deeply developed based on the Android system, an IOS system developed by Apple, including a system deeply developed based on the IOS system or other systems. The data storage area may also store data created by the electronic device during use, such as a phone book, audio and video data, chat record data, etc.

[0203] The memory 220 can be divided into an operating system space and a user space. The operating system runs in the operating system space, and native and third-party applications run in the user space. In order to ensure that different third-party applications can achieve good operating results, the operating system allocates corresponding system resources to different third-party applications. However, the requirements for system resources in different application scenarios in the same third-party application are also different. For example, in the local resource loading scenario, the third-party application has higher requirements for disk reading speed; in the animation rendering scenario, the third-party application has higher requirements for GPU performance. The operating system and third-party applications are independent of each other, and the operating system often cannot perceive the current application scenario of the third-party application in a timely manner, resulting in the operating system being unable to perform targeted system resource adaptation according to the specific application scenario of the third-party application.

[0204] In order for the operating system to distinguish the specific application scenarios of third-party applications, it is necessary to open up data communication between third-party applications and the operating system so that the operating system can obtain the current scenario information of third-party applications at any time, and then perform targeted system resource adaptation based on the current scenario.

[0205] The input device 230 is used to receive input commands or data, and includes but is not limited to a keyboard, a mouse, a camera, a microphone, or a touch device. The output device 240 is used to output commands or data, and includes but is not limited to a display device and a speaker. In one example, the input device 230 and the output device 240 can be combined, and the input device 230 and the output device 240 are touch screen displays.

[0206] The touch display screen can be designed as a full screen, a curved screen or a special-shaped screen. The touch display screen can also be designed as a combination of a full screen and a curved screen, or a combination of a special-shaped screen and a curved screen, which is not limited in the embodiments of the present application.

[0207] In addition, those skilled in the art can understand that the structure of the electronic device shown in the above drawings does not constitute a limitation on the electronic device, and the electronic device may include more or fewer components than shown, or combine certain components, or arrange the components differently. For example, the electronic device also includes components such as a radio frequency circuit, an input unit, a sensor, an audio circuit, a WiFi module, a power supply, and a Bluetooth module, which will not be described in detail here.

[0208] exist Fig.15 In the electronic device shown, the processor 210 can be used to call the file ferry application stored in the memory 220, and specifically perform the following operations:

[0209] Get the ferry data file and ferry configuration file from the ferry folder of the initiator network;

[0210] The ferry data file is saved based on the ferry configuration file.

[0211] In one embodiment, when the processor 210 acquires the ferry data file and the ferry configuration file from the ferry folder of the initiator network, the processor 210 specifically performs the following operations:

[0212] The ferry data file and the ferry configuration file are obtained from the target folder in the receiving end network.

[0213] In one embodiment, when the processor 210 acquires the ferry data file and the ferry configuration file from the ferry folder of the initiator network, the processor 210 specifically performs the following operations:

[0214] Obtain access rights to the initiator network;

[0215] Sending a file query request to the initiator cloud disk of the initiator network based on the access permission;

[0216] The ferry data file and the ferry configuration file sent by the initiator cloud disk based on the file query request are obtained.

[0217] In one embodiment, when the processor 210 performs the saving process of the ferry data file based on the ferry configuration file, the processor 210 specifically performs the following operations:

[0218] Obtain the file metadata and target path in the ferry configuration file;

[0219] An integrity check process is performed on the ferry data file based on the file metadata.

[0220] If the ferry data file passes the integrity check, the ferry data file is saved based on the target path.

[0221] In an embodiment of the present application, the initiating cloud disk sends the ferry data file and the ferry configuration file to the ferry folder of the initiating network, and sends the files in the ferry folder to the receiving cloud disk of the receiving network. The receiving cloud disk obtains the target path and file metadata in the ferry configuration file, and performs integrity verification on the ferry data file based on the file metadata, thereby ensuring the integrity of the ferry data file and avoiding file damage or loss during the ferrying process. If the ferry data file passes the integrity verification, the receiving cloud disk saves the ferry data file based on the target path. By sending the ferry configuration file and the ferry data file to the receiving cloud disk together, while realizing the ferrying of cloud disk files between different independent networks, the ferry configuration file can be used to ensure the hierarchical relationship in the ferry data file, avoiding the confusion of file content after file ferrying, and improving the orderliness of file ferrying. In addition, there are different file transfer methods for logical isolation and physical isolation. In physical isolation, file servers can be set up on both sides of the network to realize the decoupling of cloud disk and network gate, making file ferrying more flexible.

[0222] The present application also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor as described above. Figure 1-Figure 10 The file ferrying method of the embodiment shown in the figure can be specifically executed by referring to Figure 1-Figure 10 The specific description of the illustrated embodiment will not be repeated here.

[0223] The present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor as described above. Figure 1-Figure 10 The file ferrying method of the embodiment shown in the figure can be specifically executed by referring to Figure 1-Figure 10 The specific description of the illustrated embodiment will not be repeated here.

[0224] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0225] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

[0226] It should be noted that the information (including but not limited to cloud disk device information, cloud disk personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in the embodiments of this specification are all authorized by the cloud disk or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions. For example, the ferry data files, ferry configuration files, etc. involved in this specification are all obtained with full authorization.

Claims

1. A file ferrying method, applied to an initiating end network, characterized in that: The method comprises: Determine a ferry data file corresponding to a ferry request initiated by a user, and obtain a ferry configuration file of the ferry data file; The ferry data file and the ferry configuration file are sent to the ferry folder of the initiating end network, so that the receiving end cloud disk of the receiving end network saves the ferry data file based on the ferry configuration file.

2. The method according to claim 1, characterized in that: Before determining the ferry data file corresponding to the ferry request initiated by the user and obtaining the ferry configuration file of the ferry data file, the method further includes: Receiving a ferry request initiated by a user, wherein the ferry request includes at least one of ferry data file information, receiving end network information, and receiving end cloud disk information; The ferry request is reviewed and processed.

3. The method according to claim 1, characterized in that The step of obtaining the ferry configuration file of the ferry data file comprises: Obtain file metadata of the ferry data file, and obtain a target path of the ferry data file; A ferry configuration file is generated based on the file metadata and the target path.

4. A file ferrying method, applied to a receiving end network, characterized in that: The method comprises: Get the ferry data file and ferry configuration file from the ferry folder of the initiator network; The ferry data file is saved based on the ferry configuration file.

5. The method according to claim 4, characterized in that The step of obtaining the ferry data file and the ferry configuration file from the ferry folder of the initiating end network includes: The ferry data file and the ferry configuration file are obtained from the target folder in the receiving end network.

6. A file ferrying method, characterized in that: The method comprises: The initiator cloud disk of the initiator network determines the ferry data file corresponding to the ferry request initiated by the user, and obtains the ferry configuration file of the ferry data file; The initiator cloud disk sends the ferry data file and the ferry configuration file to the ferry folder of the initiator network; The receiving-end cloud disk of the receiving-end network obtains the ferry data file and the ferry configuration file from the ferry folder; The receiving-end cloud disk saves and processes the ferry data file based on the ferry configuration file.

7. A file sending device, characterized in that: The method comprises: A file data acquisition module, used to determine the ferry data file corresponding to the ferry request initiated by the user, and acquire the ferry configuration file of the ferry data file; The file data ferry module is used to send the ferry data file and the ferry configuration file to the ferry folder of the initiating end network, so that the receiving end cloud disk of the receiving end network saves the ferry data file based on the ferry configuration file.

8. A file receiving device, characterized in that: The device comprises: The file data receiving module is used to obtain the ferry data file and the ferry configuration file from the ferry folder of the initiator network; A saving processing module is used to save the ferry data file based on the ferry configuration file.

9. A computer storage medium, characterized in that The computer storage medium stores a plurality of instructions, which are suitable for being loaded by a processor and executing the method steps of any one of claims 1 to 3, 4 to 5 and 6.

10. An electronic device, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps as claimed in any one of claims 1 to 3, 4 to 5 and 6.

Images