Method and apparatus for sending web disk ferry file

Abstract

The embodiment of the present application discloses a kind of receiving, sending method, device and system of web disk ferry file, by reading ferry description file, using special ferry account to execute corresponding ferry receiving task, and in the namespace of this ferry account, the task is executed, to avoid the conflict between multiple ferry tasks.And using the task, the document block of document is stored, and by parsing ferry description file, receiver information, authority information and storage path information are obtained, the receiver is authorized by ferry account, and the document is transferred to the corresponding directory.Under the condition of setting ferry account to execute ferry task, other users do not need to participate in the ferry process, and according to the authorization of ferry description file, the security of document in the ferry process is effectively guaranteed, and leakage is prevented.Meanwhile, the document can also be transferred according to the storage path in the ferry description file, avoiding manual transfer of the user, and improving work efficiency.

Description

[0001] The present application is a divisional application of the patent application with the application date of August 2, 2022 and the invention name of "Receiving and sending method, device and system for file transfer in network disk". TECHNICAL FIELD

[0002] Embodiments of the present application relate to the technical field of network disk, in particular to a receiving and sending method, device and system for file transfer in network disk. BACKGROUND

[0003] With the rapid development of Internet cloud computing technology, network disk service has become a core content of contemporary information service. Users can edit documents online through network disk, and can also perform remote collaborative work on the same document, thereby greatly improving the convenience and flexibility of document processing.

[0004] Network disk should have strong security to protect the privacy and security of user data. In particular, company network disk is often set up in multiple different network segments to ensure data security. Network disks are completely physically isolated using a network gateway.

[0005] Currently, documents can be transferred between network disks in different network segments using an FTP server through a transfer method. In the process of implementing the present application, the inventors found the following technical problems: in the process of transferring files, the receiving network disk can only set the transferred file in the same temporary folder and notify the receiving person to take the file from the temporary folder and move it to the personal directory, which is not only cumbersome, but also loses the control of the document during the transfer process, resulting in the leakage of important documents during the transfer process. SUMMARY

[0006] Embodiments of the present application provide a receiving and sending method, device and system for file transfer in network disk to achieve the purpose of fast and secure document transfer between network disks across network segments.

[0007] In a first aspect, embodiments of the present application provide a transmission method for collaborative processing of documents across network segments, comprising:

[0008] obtaining a transfer description file from a transfer directory in an FTP server and reading the transfer description file;

[0009] creating a transfer receiving task according to the transfer description file using a transfer account, creating a transfer account namespace for the transfer receiving task, and executing the transfer receiving task in the transfer account namespace;

[0010] determining a transfer file directory according to the transfer receiving task, downloading file blocks of the transfer file from the transfer file directory, and storing the file blocks;

[0011] The ferry description file is parsed to obtain recipient information, and permissions are set for the recipients of the ferry file.

[0012] Obtain the storage path from the ferry description file and move the ferry file to the directory corresponding to the storage path.

[0013] Secondly, embodiments of the present invention also provide a method for sending files transferred via cloud storage, comprising:

[0014] Obtain the target file and destination file for the file transfer based on the file transfer operation on the cloud drive;

[0015] The ferry instance identifier is determined based on the ferry target file and the ferry destination;

[0016] Based on the ferry instance identifier, check if there is a duplicate ferry instance;

[0017] When the same ferry instance identifier exists, the corresponding relay FTP server is determined based on the ferry instance;

[0018] Create a ferry file directory on the transit FTP server and name the ferry file directory according to the ferry instance identifier and the ferry task identifier;

[0019] Traverse the database files, obtain the file blocks of the target file to be transferred, and upload them to the transfer directory;

[0020] The ferry description file is encapsulated based on the ferry instance information and ferry task information, and then uploaded to the ferry directory.

[0021] Thirdly, embodiments of the present invention also provide a receiving device for transferring files via cloud storage, comprising:

[0022] The reading module is used to obtain the ferry description file from the ferry directory of the FTP server and read the ferry description file;

[0023] A creation module is used to create a ferry receiving task based on the ferry description file using a ferry account, and to create a ferry account namespace for the ferry receiving task, and to transfer the ferry receiving task to the ferry account namespace for execution.

[0024] The storage module is used to determine the ferry file directory according to the ferry receiving task, download file blocks of the ferry file from the ferry file directory, and store them.

[0025] The parsing module is used to parse the ferry description file, obtain recipient information from the ferry description file, and set permissions for the recipients of the ferry file.

[0026] The transfer module is used to obtain the storage path from the ferry description file and transfer the ferry file to the directory corresponding to the storage path.

[0027] Fourthly, embodiments of the present invention also provide a file transfer device for cloud storage, comprising: an acquisition module, configured to acquire a target file and a destination file for transfer according to a cloud storage file transfer operation; and a determination module, configured to determine a transfer instance identifier based on the target file, the destination file, and the transfer channel.

[0028] The search module is used to search for whether there is a duplicate ferry instance based on the ferry instance identifier;

[0029] The server determination module is used to determine the corresponding relay FTP server based on the ferry instance when there are identical ferry instance identifiers.

[0030] A creation module is used to create a ferry file directory on the transit FTP server and name the ferry file directory according to the ferry instance identifier and the ferry task identifier;

[0031] The upload module is used to traverse the database files, obtain the file blocks of the target file to be transferred, and upload them to the file directory to be transferred.

[0032] The encapsulation module is used to encapsulate the ferry description file based on the ferry instance information and ferry task information, and then upload it to the ferry directory.

[0033] Fifthly, embodiments of the present invention also provide a cloud storage file system, including: a first cloud storage and a second cloud storage.

[0034] The first cloud storage includes the file transfer device provided in the above embodiments;

[0035] The second cloud storage includes the file transfer receiving device provided in the above embodiments.

[0036] The present invention provides a method, apparatus, and system for sending and receiving files transferred via cloud storage. The receiving end's cloud storage is configured to retrieve a transfer description file from a transfer directory on an FTP server. The transfer description file is read. A transfer receiving task is created using a transfer account based on the transfer description file, and a transfer account namespace is created for the transfer receiving task. The transfer receiving task is then executed within the transfer account namespace. A transfer directory is determined based on the transfer receiving task, and file blocks of the transferred file are downloaded from the transfer directory and stored. The transfer description file is parsed to obtain recipient information and set permissions for the recipient. A storage path is obtained from the transfer description file, and the transferred file is moved to the directory corresponding to the storage path. By reading the transfer description file and using a dedicated transfer account to execute the corresponding transfer receiving task within the namespace of that transfer account, conflicts between multiple transfer tasks can be avoided. This task stores document blocks and, by parsing the transfer description file, obtains recipient information, permission information, and storage path information. The transfer account then grants permissions to the recipient and moves the document to the corresponding directory. By setting up a transfer account to execute the transfer task, no other user intervention is required during the transfer process, and permissions are granted according to the transfer description file. This effectively ensures document security during the transfer process and prevents leaks. Furthermore, it allows for document transfer based on the storage path specified in the transfer description file, avoiding manual document transfer by users and improving work efficiency. Attached Figure Description

[0037] Other features, objects, and advantages of the invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0038] Figure 1 This is a flowchart illustrating the method for receiving files transferred via cloud storage according to Embodiment 1 of the present invention.

[0039] Figure 2 This is a flowchart illustrating the method for receiving files transferred via cloud storage according to Embodiment 2 of the present invention.

[0040] Figure 3 This is a flowchart illustrating the method for sending files via cloud storage provided in Embodiment 3 of the present invention;

[0041] Figure 4 This is a schematic diagram of the structure of the file receiving device for cloud storage provided in Embodiment 4 of the present invention;

[0042] Figure 5 This is a schematic diagram of the structure of the file transfer device provided in Embodiment 5 of the present invention;

[0043] Figure 6This is a schematic diagram of the structure of the cloud storage ferry file system provided in Embodiment Six of the present invention. Detailed Implementation

[0044] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.

[0045] Example 1

[0046] Figure 1 This is a flowchart illustrating the method for receiving files transferred between cloud storage and other cloud storage networks according to Embodiment 1 of the present invention. This embodiment is applicable to situations where documents are received from other cloud storage networks in a cross-network segment cloud storage environment. The method can be executed by a file transfer receiving device, which can be located in the receiving cloud storage network. Specifically, it includes the following steps:

[0047] Step 110: Obtain the ferry description file from the ferry directory on the FTP server and read the ferry description file.

[0048] Document transfer between cloud storage services on different network segments requires the use of an FTP server. When transferring documents, the sending cloud storage can send the document to the FTP server, and the receiving end can download the document by accessing the FTP server, thus completing the document transfer.

[0049] Correspondingly, descriptions of all files that need to be transferred can usually be stored in a specified file directory on the FTP server, so that the receiving end cloud drive can retrieve the corresponding transfer file information from it.

[0050] In this embodiment, to facilitate the processing of the ferry files, a ferry description file is included in the ferry directory, which describes the detailed information of this ferry. The ferry description file can be generated by the sending cloud storage based on the ferry information of the ferry file.

[0051] Therefore, in this embodiment, the ferry description file can be obtained from the ferry directory in the FTP server, and the information therein can be read.

[0052] Step 120: Use the ferry account to create a ferry receiving task based on the ferry description file, and create a ferry account namespace for the ferry receiving task, and transfer the ferry receiving task to the ferry account namespace for execution.

[0053] Because multiple ferry receiving tasks may occur simultaneously, errors will arise if they are not isolated in the program. Furthermore, ferry receiving tasks should be executed by a corresponding user. However, there may be multiple receiving users with different permissions. If the receiving user executes the task, it could lead to permission exceeding limits and resulting in data leaks. For example, with only preview permissions, the file might be modified or downloaded during the document receiving process, compromising document security.

[0054] Therefore, in this embodiment, the system can set up a ferry account, which is used to ferry files and does not actually exist. Furthermore, it can be set as a temporary account, disappearing when the ferry receiving task ends. Correspondingly, after reading the ferry description file, a ferry receiving task can be created using the ferry account based on the information provided in the ferry description file. Correspondingly, a ferry account namespace is created for the ferry receiving task, and the ferry receiving task is executed within the ferry account namespace. Namespaces are a form of code organization used in many programming languages. They are used to classify and distinguish different code functions, avoiding conflicts caused by identical variable names when different code snippets (usually used by different people collaborating or calling existing code snippets) are used simultaneously. As mentioned above, there may be multiple ferry accounts, and multiple ferry file receiving tasks may be processed simultaneously. To avoid conflicts, the aforementioned namespace can be used to prevent conflicts.

[0055] Step 130: Determine the ferry file directory according to the ferry receiving task, download the file blocks of the ferry file from the ferry file directory, and store them.

[0056] In the task of ferrying files, the specific path of the document in the current task on the FTP server, i.e., the ferry file directory, can be selected. The corresponding file blocks are then downloaded from the ferry file directory and stored in the current recipient's cloud drive.

[0057] Step 140: Parse the ferry description file, obtain the recipient information from the ferry description file, and set permissions for the recipient of the ferry file.

[0058] The download description file records the recipient and permission information. For example, the recipient information can be a user ID in the recipient's cloud storage. By parsing the standardized format of the download description file, the recipient and permission information can be obtained. Based on the permission information, the current download file is then assigned corresponding permissions to the recipient.

[0059] Accordingly, by determining whether there is a recipient in the cloud storage organizational structure, the ferry receiving task is terminated if there is no recipient.

[0060] Step 150: Obtain the storage path from the ferry description file and transfer the ferry file to the directory corresponding to the storage path.

[0061] The file transfer description file also records the file storage path information. The corresponding storage path can still be obtained by parsing the standard format of the transfer description file, and the transferred file can be moved to the directory corresponding to that storage path. This allows the recipient to view the received file through their personal cloud storage.

[0062] The method for receiving files transferred from a cloud storage service provided in this invention involves: setting the receiving end's cloud storage to retrieve a transfer description file from a transfer directory on an FTP server; reading the transfer description file; creating a transfer receiving task using a transfer account based on the transfer description file, and creating a transfer account namespace for the transfer receiving task; transferring the transfer receiving task to the transfer account namespace for execution; determining the transfer file directory based on the transfer receiving task, downloading file blocks of the transfer file from the transfer file directory, and storing them; parsing the transfer description file, obtaining recipient information from the transfer description file, and setting permissions for the recipient of the transfer file; obtaining the storage path from the transfer description file, and transferring the transfer file to the directory corresponding to the storage path. By reading the transfer description file, using a dedicated transfer account to execute the corresponding transfer receiving task, and executing the task within the namespace of that transfer account, conflicts between multiple transfer tasks can be avoided. This task stores document blocks and, by parsing the transfer description file, obtains recipient information, permission information, and storage path information. The transfer account then grants permissions to the recipient and moves the document to the corresponding directory. By setting up a transfer account to execute the transfer task, no other user intervention is required during the transfer process, and permissions are granted according to the transfer description file. This effectively ensures document security during the transfer process and prevents leaks. Furthermore, it allows for document transfer based on the storage path specified in the transfer description file, avoiding manual document transfer by users and improving work efficiency.

[0063] In a preferred embodiment of this example, after setting permissions for the recipient of the transferred file and before obtaining the storage path from the transferred file description file, the method may further include the following step: transferring the transferred file receiving task to the recipient's namespace for execution. Since document transfer involves the user's personal cloud storage space, although the transferred account can access this space, this method is prone to data leakage. Therefore, in this embodiment, after setting permissions for the recipient, the recipient's namespace can continue to execute the transferred file receiving task, and the transferred file can be transferred to the personal cloud storage directory. This method not only improves the turnover efficiency of the transferred account, allowing the transferred account to centrally handle the preliminary processing of transferred files, but also ensures the data security of the recipient's personal cloud storage space.

[0064] Example 2

[0065] Figure 2 This is a flowchart illustrating the method for receiving files transferred via cloud storage according to Embodiment 2 of the present invention. This embodiment can be optimized based on the above embodiment. Specifically, the storage path is obtained from the transfer description file. The optimization is as follows: the storage path information is extracted from the transfer description file according to the set format and feature.

[0066] Accordingly, the method for receiving files transferred via cloud storage provided in this embodiment specifically includes the following steps:

[0067] Step 210: Obtain the ferry description file from the ferry directory in the FTP server and read the ferry description file.

[0068] Step 220: Use the ferry account to create a ferry receiving task based on the ferry description file, and create a ferry account namespace for the ferry receiving task, and transfer the ferry receiving task to the ferry account namespace for execution.

[0069] Step 230: Determine the ferry file directory according to the ferry receiving task, download the file blocks of the ferry file from the ferry file directory, and store them.

[0070] Step 240: Parse the ferry description file, obtain the recipient information from the ferry description file, and set permissions for the recipient of the ferry file.

[0071] Step 250: Extract storage path information from the ferry description file according to the set format and characteristics, and transfer the ferry file to the directory corresponding to the storage path.

[0072] The ferry description file contains information about various ferry tasks. To facilitate reading and identification and prevent parsing errors, corresponding format rules can be pre-defined to allow the sender to encapsulate the ferry description file and the receiver to parse it. For example, the storage path can be identified using `copypath`, with the specific storage path appended after the identifier, and an end marker set at the end. The corresponding storage path can be read based on the identifier and end marker. The ferry file can then be moved to the directory corresponding to the specified storage path.

[0073] Furthermore, the sender and receiver might be the same user, each with accounts on both cloud storage services. In this case, the sender typically doesn't specify a corresponding storage path. Therefore, the storage path information cannot be extracted from the ferry description file. In this situation, the source path of the ferry file can be extracted based on the set format and characteristics, and this source path can be used as the storage path. Since the source path is automatically filled in and encapsulated data when the ferry task is generated, it must be written into the ferry description file. Further, if a corresponding storage path does not exist upon receipt, a file directory needs to be created based on the source path. This ensures the ferry file is stored in the specified path for easy retrieval by the receiver.

[0074] This embodiment obtains the storage path from the ferry description file by specifying the format and characteristics. Specifically, it extracts the storage path information from the ferry description file according to a set format and characteristics. This allows for accurate extraction of the corresponding storage path from the ferry description file, facilitating the accurate transfer of the ferry file to the designated path and enabling the recipient to quickly locate the ferry file.

[0075] Example 3

[0076] Figure 3 This is a flowchart illustrating the method for sending files via cloud storage according to Embodiment 3 of the present invention. This embodiment is applicable to sending documents to other cloud storage segments in a cross-segment cloud storage environment. The method can be executed by a file-sending device, which can be located in the cloud storage of the file-sending party. Specifically, it includes the following steps:

[0077] Step 310: Obtain the target file and destination for the file transfer based on the file transfer operation on the cloud drive.

[0078] In this embodiment, users can initiate a file transfer request within the cloud storage service. This is done by selecting the transfer destination (the receiving cloud storage service) and the target file.

[0079] Step 320: Determine the ferry instance identifier based on the ferry target file and the ferry destination.

[0080] In this embodiment, a "ferry" class can be provided, which is an abstract template for ferrying. Ferry instances are specific "objects" created based on the ferry class. Each object has the same methods, but their data may differ. A specific ferry instance is required to execute a ferry task. Correspondingly, each ferry instance can have an identifier, which can be a specific parameter. Therefore, it can include at least: a ferry target file and a ferry destination. Thus, the ferry instance identifier can be determined based on the ferry target file and the ferry destination. For example, determining the ferry instance identifier based on the ferry target file and the ferry destination can include: generating the ferry instance identifier based on the ferry destination number and a brief description of the ferry target file.

[0081] Step 330: Based on the ferry instance identifier, check if there is a matching ferry instance. If there is a matching ferry instance identifier, determine the corresponding relay FTP server based on the ferry instance.

[0082] Since file transfers between cloud storage services are frequent, duplicate transfer instances may exist. Therefore, the existence of identical transfer instances can be determined based on the transfer instance identifier. If an instance exists, it can be directly invoked to transfer the file. This method avoids duplicate transfers, thus saving network transmission resources. Furthermore, the corresponding relay FTP server can be determined based on the instance.

[0083] Furthermore, if no identical ferry instance exists, a corresponding ferry instance can be created based on the received operation. This ferry instance can then be used to determine the appropriate relay FTP server.

[0084] Step 340: Create a ferry file directory on the transit FTP server and name the ferry file directory according to the ferry instance identifier and the ferry task identifier.

[0085] A transfer directory is created on the relay FTP server so that the receiving cloud drive can quickly locate the transferred files. Accordingly, since there are multiple transfer tasks, the transfer directory can be given a distinctive name so that the receiving cloud drive can identify the files to be transferred based on the directory folder name. Optionally, naming the transfer file directory based on the transfer instance identifier and the transfer task identifier can include naming the transfer file directory based on the transfer instance identifier and the transfer task sequence number.

[0086] For example, it can be named in the format of dczName+taskId, where dczName is the name of the ferry and taskId is the task ID.

[0087] Step 350: Traverse the database files, obtain the file blocks of the target file to be transferred, and upload them to the file directory to be transferred.

[0088] Since the files are stored in a database, it is necessary to locate the specific file block corresponding to the file ID of the target file being transferred. The file blocks are then retrieved by traversing the database and uploaded to the transfer file directory on the intermediary FTP server.

[0089] Step 360: Encapsulate the ferry description file based on the ferry instance information and ferry task information, and upload it to the ferry directory.

[0090] A ferry description file is used to describe the detailed information of this ferry. The receiving cloud storage can parse the content and perform corresponding receiving processing on the file. This achieves the purpose of setting permissions and storing the file in a specified storage path. Therefore, in this embodiment, the ferry description file can be automatically encapsulated based on the exemplary ferry information and ferry task information. For example, encapsulating the ferry description file based on the ferry instance information includes: writing the recipient information into the ferry recipient identifier; writing the storage path of the ferry file into the storage path identifier; writing the receiving path into the receiving path identifier; and writing the permission code into the permission identifier. In this way, the receiving cloud storage can accurately parse the corresponding content and execute it accordingly.

[0091] This embodiment obtains the target file and destination for file transfer based on cloud storage file transfer operations; determines a transfer instance identifier based on the target file and destination; searches for identical transfer instances based on the transfer instance identifier; if identical transfer instance identifiers exist, determines the corresponding relay FTP server based on the transfer instance; creates a transfer file directory on the relay FTP server and names the transfer file directory based on the transfer instance identifier and transfer task identifier; traverses database files to obtain file blocks of the target file and uploads them to the transfer file directory; encapsulates a transfer description file based on the transfer instance information and transfer task information and uploads it to the transfer directory. It can determine the corresponding transfer instance based on cloud storage transfer operation information and automatically encapsulate and generate a transfer description file based on the transfer instance and transfer task information, enabling the receiving cloud storage to automatically create a transfer file receiving task based on the transfer description file, and set permissions for the recipient and transfer the transferred file. This improves the security and convenience of cloud storage file transfer.

[0092] Example 4

[0093] Figure 4 This is a schematic diagram of the structure of the file receiving device for cloud storage provided in Embodiment 4 of the present invention, as shown below. Figure 4 As shown, the device includes:

[0094] The reading module 410 is used to obtain a ferry description file from the ferry directory of the FTP server and read the ferry description file;

[0095] The creation module 420 is used to create a ferry receiving task based on the ferry description file using the ferry account, and to create a ferry account namespace for the ferry receiving task, and to transfer the ferry receiving task to the ferry account namespace for execution.

[0096] Storage module 430 is used to determine the ferry file directory according to the ferry receiving task, download file blocks of the ferry file from the ferry file directory, and store them.

[0097] The parsing module 440 is used to parse the ferry description file, obtain recipient information from the ferry description file, and set permissions for the recipients of the ferry file.

[0098] The transfer module 450 is used to obtain the storage path from the ferry description file and transfer the ferry file to the directory corresponding to the storage path.

[0099] The file-receiving device for cloud storage provided in this embodiment of the invention retrieves a file-receiving description file from a file-receiving directory on an FTP server by setting the receiving end's cloud storage to do so; reads the file-receiving description file; creates a file-receiving task using a file-receiving account based on the file-receiving description file, and creates a file-receiving account namespace for the task, executing the task within the file-receiving account namespace; determines the file-receiving directory based on the task, downloads file blocks of the file to the file-receiving directory, and stores them; parses the file-receiving description file, retrieves recipient information from it, and sets permissions for the recipient; retrieves the storage path from the file-receiving description file, and moves the file to the directory corresponding to the storage path. By reading the file-receiving description file and executing the corresponding file-receiving task using a dedicated file-receiving account within the namespace of that account, conflicts between multiple file-receiving tasks can be avoided. This task stores document blocks and, by parsing the transfer description file, obtains recipient information, permission information, and storage path information. The transfer account then grants permissions to the recipient and moves the document to the corresponding directory. By setting up a transfer account to execute the transfer task, no other user intervention is required during the transfer process, and permissions are granted according to the transfer description file. This effectively ensures document security during the transfer process and prevents leaks. Furthermore, it allows for document transfer based on the storage path specified in the transfer description file, avoiding manual document transfer by users and improving work efficiency.

[0100] Based on the above embodiments, the device further includes:

[0101] The transfer module is used to transfer the ferry receiving task to the recipient's namespace for execution.

[0102] Based on the above embodiments, the device further includes:

[0103] The judgment module is used to determine whether there is a recipient in the cloud storage organizational structure. If there is no recipient, the ferry receiving task is terminated.

[0104] Based on the above embodiments, the transfer module includes:

[0105] The extraction unit is used to extract storage path information from the ferry description file according to the set format and characteristics.

[0106] Based on the above embodiments, the transfer module further includes:

[0107] The source path extraction unit is used to extract the source path of the ferry file according to the set format and characteristics when the storage path information is not extracted, and to use the source path as the storage path.

[0108] Based on the above embodiments, the transfer module further includes:

[0109] A creation unit is used to create a file directory corresponding to the source path.

[0110] Example 5

[0111] Figure 5 This is a schematic diagram of the structure of the file transfer device provided in Embodiment 5 of the present invention, as shown below. Figure 5 As shown, the device includes:

[0112] The acquisition module 510 is used to obtain the target file, destination, and transfer channel for file transfer based on the file transfer operation on the cloud drive.

[0113] The determination module 520 is used to determine the ferry instance identifier based on the ferry target file and the ferry destination;

[0114] The search module 530 is used to search for whether there is a duplicate ferry instance based on the ferry instance identifier;

[0115] Server determination module 540 is used to determine the corresponding relay FTP server based on the ferry instance when there are identical ferry instance identifiers.

[0116] The creation module 550 is used to create a ferry file directory on the transit FTP server and name the ferry file directory according to the ferry instance identifier and the ferry task identifier.

[0117] The upload module 560 is used to traverse the database files, obtain the file blocks of the target file to be transferred, and upload them to the file directory to be transferred.

[0118] The encapsulation module 570 is used to encapsulate the ferry description file based on the ferry instance information and ferry task information, and upload it to the ferry directory.

[0119] The file transfer device provided in this embodiment obtains the target file and destination for file transfer based on the file transfer operation; determines a transfer instance identifier based on the target file and destination; searches for the existence of a duplicate transfer instance based on the transfer instance identifier; if a duplicate transfer instance identifier exists, determines the corresponding relay FTP server based on the transfer instance; creates a transfer file directory on the relay FTP server and names the transfer file directory based on the transfer instance identifier and transfer task identifier; traverses the database files, obtains the file blocks of the target file for transfer, and uploads them to the transfer file directory; encapsulates a transfer description file based on the transfer instance information and transfer task information, and uploads it to the transfer directory. It can determine the corresponding transfer instance based on the file transfer operation information and automatically encapsulate and generate a transfer description file based on the transfer instance and transfer task information, so that the receiving end of the file transfer can automatically create a file transfer receiving task based on the transfer description file, and set permissions for the recipient and transfer the transferred file. This can improve the security and convenience of file transfer on the file transfer server.

[0120] Based on the above embodiments, the device includes:

[0121] The generation module is used to generate a ferry instance based on the ferry target file, ferry destination and ferry channel when no identical ferry instance exists, and to determine the corresponding relay FTP server using the ferry instance.

[0122] Based on the above embodiments, the determining module includes:

[0123] The identifier generation unit is used to generate a ferry instance identifier based on the ferry destination number and the brief description of the ferry target file.

[0124] Based on the above embodiments, the creation module includes:

[0125] The naming unit is used to name the ferry file directory according to the ferry instance identifier and the ferry task sequence number.

[0126] Based on the above embodiments, the packaging module includes:

[0127] The first writing unit is used to write the recipient information into the ferry recipient identifier;

[0128] The second writing unit is used to write the storage path of the ferry file into the storage path identifier;

[0129] The third writing unit is used to write the receiving path into the receiving path identifier;

[0130] The fourth writing unit is used to write the permission code into the permission identifier.

[0131] The file transfer device for cloud storage provided in this embodiment of the invention can execute the file transfer method for cloud storage provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method.

[0132] Example 6

[0133] Figure 6 This is a schematic diagram of the cloud storage file system provided in Embodiment Six of the present invention. See also: Figure 6 The document processing system that enables cross-network segment collaborative processing includes: a first network drive and a second network drive.

[0134] Accordingly, the first cloud storage includes the cloud storage file receiving device provided in the above embodiments;

[0135] The second cloud drive includes the file transfer device provided in the above embodiments.

[0136] The cloud storage transfer file system provided in this invention utilizes a transfer description file to execute a corresponding transfer receiving task using a dedicated transfer account. This task is executed within the namespace of the transfer account to avoid conflicts between multiple transfer tasks. The task stores document blocks and, by parsing the transfer description file, obtains recipient information, permission information, and storage path information. The transfer account then grants permissions to the recipient and moves the document to the corresponding directory. By setting a transfer account to execute the transfer task, no other user intervention is required during the transfer process, and permissions are granted according to the transfer description file. This effectively ensures document security during the transfer process and prevents leakage. Furthermore, the document can be transferred based on the storage path in the transfer description file, avoiding manual document transfer by users and improving work efficiency.

[0137] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. A method for sending a webdisk ferry file, characterized in that, The method is performed by a sender web disk of a web disk ferry file, and comprises: According to the web disk ferry file operation, a ferry target file and a ferry destination are obtained; According to the ferry target file and the ferry destination, a ferry instance identifier is determined; According to the ferry instance identifier, it is determined whether there is a same ferry instance; When there is a same ferry instance identifier, a corresponding transfer FTP server is determined according to the ferry instance; A ferry file directory is created in the transfer FTP server, and the ferry file directory is named according to the ferry instance identifier and a ferry task identifier; Database files are traversed, file blocks of the ferry target file are obtained, and are uploaded into the ferry file directory; According to the information of the ferry instance and the ferry task information, a ferry description file is encapsulated, and is uploaded into the ferry directory.

2. The method of claim 1, wherein, Comprise: When there is no same ferry instance, a ferry instance is generated according to the ferry target file, the ferry destination and a ferry channel, and a corresponding transfer FTP server is determined by using the ferry instance.

3. The method of claim 1, wherein, According to the ferry target file and the ferry destination, a ferry instance identifier is determined, comprising: According to the ferry destination number and the ferry target file brief description, a ferry instance identifier is generated.

4. The method of claim 3, wherein, According to the ferry instance identifier and the ferry task identifier, the ferry file directory is named, comprising: According to the ferry instance identifier and the ferry task serial number, the ferry file directory is named.

5. The method of claim 1, wherein, According to the information of the ferry instance and the ferry task information, a ferry description file is encapsulated, comprising: Recipient information is written into a ferry recipient identifier; A storage path of the ferry file is written into a storage path identifier; A receiving path is written into a receiving path identifier; A permission code is written into a permission identifier.

6. A sending apparatus of a web folder ferry file, characterized in that, Comprise: The obtaining module is used for obtaining a ferry target file, a ferry destination and a ferry channel according to a web disk ferry file operation; The determining module is used for determining a ferry instance identifier according to the ferry target file, the ferry destination and the ferry channel; The finding module is used for finding whether there is a same ferry instance according to the ferry instance identifier; The server determining module is used for determining a corresponding transfer FTP server according to the ferry instance when there is a same ferry instance identifier; The creating module is used for creating a ferry file directory in the transfer FTP server, and naming the ferry file directory according to the ferry instance identifier and a ferry task identifier; The uploading module is used for traversing database files, obtaining file blocks of the ferry target file, and uploading into the ferry file directory; The encapsulating module is used for encapsulating a ferry description file according to the information of the ferry instance and the ferry task information, and uploading into the ferry directory.

Images