CN114979126A - Method, device and system for receiving and sending network disk ferry file - Google Patents

Method, device and system for receiving and sending network disk ferry file Download PDF

Info

Publication number
CN114979126A
CN114979126A CN202210918831.1A CN202210918831A CN114979126A CN 114979126 A CN114979126 A CN 114979126A CN 202210918831 A CN202210918831 A CN 202210918831A CN 114979126 A CN114979126 A CN 114979126A
Authority
CN
China
Prior art keywords
ferry
file
directory
instance
task
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202210918831.1A
Other languages
Chinese (zh)
Other versions
CN114979126B (en
Inventor
张绍军
王建
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tianjin Lenovo Collaboration Technology Inc
Original Assignee
Tianjin Lenovo Collaboration Technology Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tianjin Lenovo Collaboration Technology Inc filed Critical Tianjin Lenovo Collaboration Technology Inc
Priority to CN202210918831.1A priority Critical patent/CN114979126B/en
Priority to CN202211570454.3A priority patent/CN116192830A/en
Publication of CN114979126A publication Critical patent/CN114979126A/en
Application granted granted Critical
Publication of CN114979126B publication Critical patent/CN114979126B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Storage Device Security (AREA)

Abstract

The embodiment of the invention discloses a method, a device and a system for receiving and sending a network disk ferry file. And storing the document blocks of the document by using the task, acquiring the information of the receiver, the authority information and the storage path information by analyzing the ferry description file, endowing the right to the receiver by using the ferry account, and transferring the document to a corresponding directory. The ferry account is set to execute the ferry task, so that other users do not need to participate in the ferry process, and the right is correspondingly given according to the ferry description file. Effectively ensures the safety of the document in the ferrying process and prevents the disclosure. Meanwhile, the document can be transferred according to the storage path in the ferry description file, so that the document is prevented from being manually transferred by a user, and the working efficiency is improved.

Description

Method, device and system for receiving and sending network disk ferry file
Technical Field
The embodiment of the invention relates to the technical field of network disks, in particular to a method, a device and a system for receiving and sending a network disk ferry file.
Background
With the rapid development of internet cloud computing technology, the network disk service has become a core content of the current-generation information service. The user can edit the document on line through the network disk, and can perform remote cooperative operation aiming at the same document, so that the convenience and flexibility of document processing can be greatly improved.
The network disk has stronger security, and the privacy and the security of user data are guaranteed. Especially company network disk, for ensuring data security. Network disks located in a plurality of different network segments are often set, and the network disks are completely physically separated by using a network gate.
At present, a file can be transmitted between network disks of different network segments by using an FTP server in a ferrying mode. In the process of implementing the invention, the inventor finds the following technical problems: in the process of ferrying files, the network disk of the receiver can only arrange the ferry files in the same temporary folder and inform the receiver of the other party to take out the files from the temporary folder and transfer the files to the personal directory, so that the operation is complicated, and the authority control of the files is lost in the ferry process, so that the leakage of the important files is caused in the ferry process.
Disclosure of Invention
The embodiment of the invention provides a method, a device and a system for receiving and sending a network disk ferry file, and aims to achieve the purpose of quickly and safely carrying out document ferry among network disks in cross-network sections.
In a first aspect, an embodiment of the present invention provides a method for implementing transmission of a cross-network-segment cooperative processing document, including:
acquiring a ferry description file from a ferry directory in an FTP server, and reading the ferry description file;
establishing a ferry receiving task according to the ferry description file by using a ferry account, establishing a ferry account name space for the ferry receiving task, and transferring the ferry receiving task to the ferry account name space for execution;
determining a ferry file directory according to the ferry receiving task, downloading file blocks of the ferry file from the ferry file directory, and storing the file blocks;
analyzing the ferry description file, acquiring receiver information from the ferry description file, and setting authority for the receiver of the ferry file;
and acquiring a storage path from the ferry description file, and transferring the ferry file to a directory corresponding to the storage path.
In a second aspect, an embodiment of the present invention further provides a method for sending a network disk ferry file, where the method includes:
acquiring a ferry target file and a ferry destination according to the operation of the network disk ferry file;
determining a ferry instance identifier according to the ferry target file and the ferry destination;
searching whether the same ferry instances exist according to the ferry instance identifications;
when the same ferry instance identification exists, determining a corresponding transfer FTP server according to the ferry instance;
creating a ferry file directory in the transfer FTP server, and naming the ferry file directory according to a ferry instance identifier and a ferry task identifier;
traversing database files, acquiring file blocks of the ferry target file, and uploading the file blocks to the ferry directory;
and packaging the ferry description file according to the information of the ferry instance and the ferry task information, and uploading the ferry description file to a ferry directory.
In a third aspect, an embodiment of the present invention further provides a device for receiving a network disk ferry file, including:
the reading module is used for acquiring a ferry description file from a ferry directory in the FTP server and reading the ferry description file;
the system comprises a creating module, a data processing module and a data processing module, wherein the creating module is used for creating a ferry receiving task according to the ferry description file by using a ferry account, creating a ferry account name space for the ferry receiving task, and transferring the ferry receiving task into the ferry account name space for execution;
the storage module is used for determining a ferry file directory according to the ferry receiving task, downloading file blocks of the ferry file from the ferry file directory and storing the file blocks;
the analysis module is used for analyzing the ferry description file, acquiring receiver information from the ferry description file and setting authority for a receiver of the ferry file;
and the transfer module is used for acquiring a storage path from the ferry description file and transferring the ferry file to a directory corresponding to the storage path.
In a fourth aspect, an embodiment of the present invention further provides a device for sending a network disk ferry file, where the device includes:
the acquisition module is used for acquiring a ferry target file and a ferry destination according to the operation of the network disk ferry file;
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 searching module is used for searching whether the identical ferrying examples exist or not according to the ferrying example identification;
the server determining module is used for determining a corresponding transfer FTP server according to the ferry instance when the same ferry instance identifier exists;
the creating module is used for creating a ferry file directory in the transfer FTP server and naming the ferry file directory according to a ferry instance identifier and a ferry task identifier;
the uploading module is used for traversing database files, acquiring file blocks of the ferry target file and uploading the file blocks to the ferry file directory;
and the packaging module is used for packaging the ferry description file according to the information of the ferry instance and the ferry task information and uploading the ferry description file to a ferry directory.
In a fifth aspect, an embodiment of the present invention further provides a network disk ferry file system, including: a first mesh plate and a second mesh plate,
the first network disk comprises the sending device of the network disk ferry file provided by the embodiment;
the second network disk comprises the receiving device for the network disk ferry file provided by the embodiment.
The embodiment of the invention provides a method, a device and a system for sending and receiving a network disk ferry file.A network disk at a receiving end is set to acquire a ferry description file from a ferry directory in an FTP server and read the ferry description file; establishing a ferry receiving task according to the ferry description file by using a ferry account, establishing a ferry account name space for the ferry receiving task, and transferring the ferry receiving task to the ferry account name space for execution; determining a ferry directory according to the ferry receiving task, downloading a file block of a ferry file from the ferry directory, and storing the file block; analyzing the ferry description file, acquiring receiver information from the ferry description file, and setting permission for a receiver of the ferry file; and acquiring a storage path from the ferry description file, and transferring the ferry file to a directory corresponding to the storage path. And executing the corresponding ferry receiving task by using the read ferry description file and the special ferry account, and executing the task in the namespace of the ferry account so as to avoid conflict among a plurality of ferry tasks. And storing the document block of the document by using the task, acquiring the information of the receiver, the authority information and the storage path information by analyzing the ferry description file, authorizing the receiver by using the ferry account, and transferring the document to a corresponding directory. By setting the ferry account number to execute the ferry task, other users do not need to participate in the ferry process, and the right is correspondingly given according to the ferry description file. Effectively ensures the safety of the document in the ferrying process and prevents the disclosure. Meanwhile, the document can be transferred according to the storage path in the ferry description file, so that the document is prevented from being manually transferred by a user, and the working efficiency is improved.
Drawings
Other features, objects and advantages of the invention will become more apparent upon reading of the detailed description of non-limiting embodiments made with reference to the following drawings:
fig. 1 is a schematic flow chart of a method for receiving a network disk ferry file according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of a method for receiving a network disk ferry file according to a second embodiment of the present invention;
fig. 3 is a schematic flow chart of a method for sending a network disk ferry file according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of a receiving apparatus for a network disk ferry file according to a fourth embodiment of the present invention;
fig. 5 is a schematic structural diagram of a device for sending a network disk ferry file according to a fifth embodiment of the present invention;
fig. 6 is a schematic structural diagram of a network disk ferry file system according to a sixth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a schematic flow chart of a method for receiving a network disk ferry file according to an embodiment of the present invention, where the embodiment is applicable to a situation where documents in network disks of other network segments are received in a network disk crossing environment, and the method may be executed by a receiving device for a network disk ferry file, where the receiving device for a network disk ferry file may be disposed in a network disk of a receiving party of the network disk ferry file, and specifically includes the following steps:
and step 110, acquiring a ferry description file from a ferry directory in the FTP server, and reading the ferry description file.
The file transmission between the cross-network-segment network disks needs to be carried out by means of an FTP server, when the file ferry is carried out, the network disk of the sending end can send the file to the FTP server, and the receiving end downloads the file by accessing the FTP server to complete the ferry of the file.
Accordingly, all file descriptions to be ferred can be stored in a certain designated file directory in the FTP server, so that the network disk at the receiving end can conveniently obtain corresponding ferry file information from the file directories.
In the present embodiment, the ferry file is processed for convenience. A ferry description file is set in the ferry directory and is used for describing the detailed information of the ferry. The ferry description file can be generated by the network disk of the sender according to the ferry information of the ferry file.
Therefore, in the present embodiment, the ferry description file can be acquired from the ferry directory in the FTP server, and the information therein can be read.
And 120, creating a ferry receiving task according to the ferry description file by using a ferry account, creating a ferry account name space for the ferry receiving task, and transferring the ferry receiving task to the ferry account name space for execution.
Since there may be multiple ferry reception tasks at the same time, errors may occur if isolation is not done programmatically. And the ferry receiving task needs to be executed by the corresponding user. However, there may be a plurality of receiving users with different authorities, but if the receiving users perform the authority override, the disclosure may be compromised. For example, when only the preview authority is provided, the file may be modified or downloaded during the document receiving process, which may affect the security of the document.
Thus, in this embodiment, the system may set a ferry account number, which is used for a ferry file, which does not actually exist. Furthermore, the temporary account number can be set as a temporary account number and disappears when the ferry receiving task is finished. Correspondingly, after the ferry description file is read, a ferry receiving task can be created by using the ferry account according to information provided by the ferry description file. Correspondingly, a ferry account name space is created for the ferry receiving task, and the ferry receiving task is transferred to the ferry account name space for execution. The namespace is a code organization form used by many programming languages, and is classified by the namespace to distinguish different code functions, and avoid conflicts caused by the same variable names among different codes when different code fragments (usually, different people work together or call the existing code fragments) are used at the same time. As described above, there may be a plurality of ferry accounts, and a plurality of ferry file receiving tasks are processed simultaneously, so as to avoid a conflict, the above namespace may be used to avoid the conflict problem.
Step 130, determining a ferry file directory according to the ferry receiving task, downloading file blocks of the ferry file from the ferry file directory, and storing the file blocks.
The ferry receiving task can specifically aim at the specific path of the document in the current task in the FTP server, namely a ferry file directory. And downloading the corresponding file blocks from the ferry file directory. And storing the data into the current receiver network disk.
Step 140, analyzing the ferry description file, acquiring the information of the receiver from the ferry description file, and setting the authority for the receiver of the ferry file.
The ferry description file records the recipient and the authority information. Illustratively, the recipient information may be a user ID in a recipient web disk. Through analysis of the ferry description file standard format, the information of the receiver and the authority can be obtained. And endowing the current ferry file with corresponding authority to the receiver according to the authority information.
Correspondingly, whether a receiver exists in the network disk organization framework or not is judged, and the ferry receiving task is terminated when the receiver does not exist.
And 150, acquiring a storage path from the ferry description file, and transferring the ferry file to a directory corresponding to the storage path.
The file storage path information is also described in the ferry description file. Still can correspondingly obtain corresponding storage path through the analysis to ferry description file specification format. And transferring the ferry file to a directory corresponding to the storage path. So that the recipient can view the received ferry file through the personal network disk space.
The method for receiving the network disk ferry file provided by the embodiment of the invention comprises the steps that the network disk at a receiving end is set to obtain a ferry description file from a ferry directory in an FTP server, and the ferry description file is read; establishing a ferry receiving task according to the ferry description file by using a ferry account, establishing a ferry account name space for the ferry receiving task, and transferring the ferry receiving task to the ferry account name space for execution; determining a ferry file directory according to the ferry receiving task, downloading file blocks of the ferry file from the ferry file directory, and storing the file blocks; analyzing the ferry description file, acquiring receiver information from the ferry description file, and setting authority for the receiver of the ferry file; and acquiring a storage path from the ferry description file, and transferring the ferry file to a directory corresponding to the storage path. And executing the corresponding ferry receiving task by using the read ferry description file and the special ferry account, and executing the task in the namespace of the ferry account so as to avoid conflict among a plurality of ferry tasks. And storing the document blocks of the document by using the task, acquiring the information of the receiver, the authority information and the storage path information by analyzing the ferry description file, endowing the right to the receiver by using the ferry account, and transferring the document to a corresponding directory. The ferry account is set to execute the ferry task, so that other users do not need to participate in the ferry process, and the right is correspondingly given according to the ferry description file. Effectively ensures the safety of the document in the ferrying process and prevents the disclosure. Meanwhile, the document can be transferred according to the storage path in the ferry description file, so that the document is prevented from being manually transferred by a user, and the working efficiency is improved.
In a preferred implementation manner of this embodiment, after setting the authority for the recipient of the ferry file, before acquiring the storage path from the ferry description file, the method may further add the following steps: and transferring the ferry receiving task to a receiver name space for execution. Since transferring documents involves the user's personal web space. While ferry accounts may have access to personal webdisk space, this approach easily creates a personal webdisk space compromise. Therefore, in the embodiment, after the authority is set for the receiver, the namespace of the receiver continues to execute the ferry file receiving task, and the ferry file can be transferred to the personal webdisk directory.
Example two
Fig. 2 is a schematic flow chart of a method for receiving a network disk ferry file according to a second embodiment of the present invention, where this embodiment may be optimized on the basis of the foregoing embodiment, specifically, a storage path is obtained from the ferry description file, and is specifically optimized as follows: and extracting storage path information from the ferry description file according to the set format and the set characteristic symbol.
Correspondingly, the method for receiving the network disk ferry file provided by the embodiment specifically includes the following steps:
step 210, obtaining a ferry description file from a ferry directory in the FTP server, and reading the ferry description file.
Step 220, a ferry receiving task is created according to the ferry description file by using a ferry account, a ferry account name space is created for the ferry receiving task, and the ferry receiving task is transferred to the ferry account name space for execution.
Step 230, determining a ferry file directory according to the ferry receiving task, downloading file blocks of the ferry file from the ferry file directory, and storing the file blocks.
And 240, analyzing the ferry description file, acquiring the information of the receiver from the ferry description file, and setting the authority for the receiver of the ferry file.
And step 250, extracting storage path information from the ferry description file according to the set format and the set characteristic symbol, and transferring the ferry file to a directory corresponding to the storage path.
The ferry description file records related information of a plurality of ferry file tasks. In order to facilitate reading and identification and avoid analysis errors, a corresponding format rule can be preset so that a sender packages a ferry description file and a receiver analyzes the ferry description file. For example, a copypath may be used as an identifier for a memory path, and after the identifier, a specific memory path is written, and finally, a corresponding end flag is set. The read to the corresponding memory path may be based on the identifier and the end identification bit. And then moving the ferry file to the directory corresponding to the storage path.
In addition, the sender and the receiver may be the same user, and there may be an account on both end network disks, respectively. Therefore, the storage path information cannot be extracted from the ferry description file, and in this case, the source path of the ferry file can be extracted according to the set format and the set characteristic symbol, and the source path can be used as the storage path. Since the source path is the data that is automatically filled in when the ferry task is generated. Therefore, it must be written into the ferry description file. Further, if no corresponding storage path exists after receiving, a file directory needs to be correspondingly created according to the source path. The ferry file is stored in the designated path, so that the ferry file can be conveniently searched by a receiver.
In this embodiment, a storage path is obtained from the ferry description file, and is specifically optimized as follows: and extracting storage path information from the ferry description file according to the set format and the set characteristic symbol. The corresponding storage path can be accurately extracted from the ferry description file, so that the ferry file can be conveniently and accurately transferred to a designated path, and a receiver can conveniently and quickly find the ferry file.
EXAMPLE III
Fig. 3 is a schematic flow chart of a method for sending a network disk ferry file according to a third embodiment of the present invention, where this embodiment is applicable to a case where a document is sent to a network disk in another network segment in a cross-network segment network disk environment, and the method may be executed by a sending device for a network disk ferry file, where the sending device for a network disk ferry file may be disposed in a network disk of a receiver of the network disk ferry file, and specifically includes the following steps:
and 310, acquiring a ferry target file and a ferry destination according to the operation of the network disk ferry file.
In this embodiment, the user may initiate a ferry file request in the network disk. And initiating a ferry file request by selecting a ferry destination, namely a receiver network disk, a ferry target file and the like.
And step 320, determining a ferry instance identifier according to the ferry target file and the ferry destination.
In this embodiment, a ferry class may be provided, which is an abstract template for ferry, and the ferry instance is a concrete "object" created from the ferry class, each object having the same method, but the respective data may be different. When the ferry task is executed, a specific ferry instance is required to operate. Correspondingly, each ferry instance can be provided with an identifier, and the identifier can be a corresponding specific parameter. Correspondingly, therefore, at least: a ferry target file and a ferry destination. Therefore, the ferry instance identification can be determined according to the ferry target file and the ferry destination. For example, the determining of the ferry instance identifier according to the ferry target file and the ferry destination may include: and generating a ferry instance identifier according to the ferry destination number and the ferry target file brief description.
And step 330, searching whether the same ferry instance exists according to the ferry instance identifier, and determining a corresponding transfer FTP server according to the ferry instance when the same ferry instance identifier exists.
Since the ferry files between the network disks are frequent, the same ferry instances may exist, and therefore, whether the same ferry instances exist can be determined according to the ferry instance identifications. When the file ferry exists, the ferry instance can be directly called, and file ferry is realized. By using the mode, repeated ferrying can be avoided, and network transmission resources are further saved. Meanwhile, the corresponding transfer FTP server can be determined according to the example.
In addition, when the same ferry instance does not exist, a corresponding ferry instance may be created according to the received operation. And determining a corresponding transfer FTP server by using the ferry instance.
And 340, creating a ferry file directory in the transfer FTP server, and naming the ferry file directory according to the ferry instance identifier and the ferry task identifier.
And correspondingly, due to the existence of a plurality of ferry tasks, the ferry directory can be named characteristically, so that the network disk of the receiver can determine the files needing ferry according to the names of the directory folders. Optionally, the naming the ferry file directory according to the ferry instance identifier and the ferry task identifier may include: and naming the ferry file directory according to the ferry instance identifier and the ferry task sequence number.
Illustratively, the names may be dczName + taskId, dczName being the ferry name and taskId being the task ID.
And 350, traversing database files, acquiring file blocks of the ferry target file, and uploading the file blocks to the ferry file directory.
Since the file is stored in the database, a specific file block corresponding to the file needs to be correspondingly searched according to the file ID of the ferry target file. And acquiring the file blocks in a traversing mode, and correspondingly uploading the file blocks to a ferry file directory in the transfer FTP server.
And step 360, packaging the ferry description file according to the information of the ferry instance and the ferry task information, and uploading the ferry description file to a ferry directory.
And the ferry description file is used for describing the detailed information of the ferry. The receiving network disk can perform corresponding receiving processing on the file by analyzing the content in the receiving network disk. The purposes of setting authority and storing the appointed storage path are achieved. Therefore, in the embodiment, automatic packaging of the ferry description file can be realized according to the ferry exemplary information and the ferry task information. Illustratively, the packaging the ferry description file according to the information of the ferry instance includes: writing the information of the receiver into the identification of the ferry receiver; 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 authority code into the authority identifier. By the method, the receiving-side network disk can accurately analyze the corresponding content and correspondingly execute the corresponding content.
In the embodiment, a ferry target file and a ferry destination are obtained through operation according to a network disk ferry file; determining a ferry instance identifier according to the ferry target file and the ferry destination; searching whether the same ferry instance exists according to the ferry instance identifier; when the same ferry instance identification exists, determining a corresponding transfer FTP server according to the ferry instance; creating a ferry file directory in the transfer FTP server, and naming the ferry file directory according to a ferry instance identifier and a ferry task identifier; traversing database files, acquiring file blocks of the ferry target file, and uploading the file blocks to the ferry file directory; and packaging the ferry description file according to the information of the ferry instance and the ferry task information, and uploading the ferry description file to a ferry directory. The corresponding ferry instance can be determined according to the network disk ferry operation information, and the ferry description file is generated by automatic packaging according to the ferry instance and the ferry task information, so that a ferry file receiving task can be automatically created by the ferry receiving terminal network disk according to the ferry description file, and the permission is set for a receiver and the ferry file is transferred. The safety and the convenience of the network disk file ferrying can be improved.
Example four
Fig. 4 is a schematic structural diagram of a receiving apparatus for a network disk ferry file according to a fourth embodiment of the present invention, and as shown in fig. 4, the apparatus includes:
the reading module 410 is configured to obtain a ferry description file from a ferry directory in an FTP server, and read the ferry description file;
a creating module 420, configured to create a ferry receiving task according to the ferry description file by using a ferry account, create a ferry account namespace for the ferry receiving task, and transfer the ferry receiving task to a ferry account namespace for execution;
the storage module 430 is configured to determine a ferry file directory according to the ferry receiving task, download a file block of a ferry file from the ferry file directory, and store the file block;
the analysis module 440 is configured to analyze the ferry description file, obtain recipient information from the ferry description file, and set an authority for a recipient of the ferry file;
the transferring module 450 is configured to obtain a storage path from the ferry description file, and transfer the ferry file to a directory corresponding to the storage path.
According to the receiving device for the network disk ferry file provided by the embodiment of the invention, the network disk at the receiving end is set to acquire the ferry description file from the ferry directory in the FTP server, and the ferry description file is read; establishing a ferry receiving task according to the ferry description file by using a ferry account, establishing a ferry account name space for the ferry receiving task, and transferring the ferry receiving task to the ferry account name space for execution; determining a ferry directory according to the ferry receiving task, downloading a file block of a ferry file from the ferry directory, and storing the file block; analyzing the ferry description file, acquiring receiver information from the ferry description file, and setting authority for the receiver of the ferry file; and acquiring a storage path from the ferry description file, and transferring the ferry file to a directory corresponding to the storage path. And executing the corresponding ferry receiving task by using the read ferry description file and the special ferry account, and executing the task in the namespace of the ferry account so as to avoid the conflict among a plurality of ferry tasks. And storing the document block of the document by using the task, acquiring the information of the receiver, the authority information and the storage path information by analyzing the ferry description file, authorizing the receiver by using the ferry account, and transferring the document to a corresponding directory. The ferry account is set to execute the ferry task, so that other users do not need to participate in the ferry process, and the right is correspondingly given according to the ferry description file. Effectively ensures the safety of the document in the ferrying process and prevents the disclosure. Meanwhile, the document can be transferred according to the storage path in the ferry description file, so that the document is prevented from being manually transferred by a user, and the working efficiency is improved.
On the basis of the above embodiments, the apparatus further includes:
and the transfer-in module is used for transferring the ferry receiving task to a receiver namespace for execution.
On the basis of the above embodiments, the apparatus further includes:
and the judging module is used for judging whether a receiver exists in the network disk organization framework or not, and terminating the ferry receiving task when the receiver does not exist.
On the basis of the above embodiments, the transfer module includes:
and the extracting unit is used for extracting the storage path information from the ferry description file according to the set format and the set characteristic symbol.
On the basis of the above embodiments, the transfer module further includes:
and the source path extracting unit is used for extracting a source path of the ferry file according to a set format and a set characteristic symbol when the storage path information is not extracted, and taking the source path as a storage path.
On the basis of the above embodiments, the transfer module further includes:
and the creating unit is used for correspondingly creating a file directory according to the source path.
EXAMPLE five
Fig. 5 is a schematic structural diagram of a device for sending a network disk ferry file according to a fifth embodiment of the present invention, and as shown in fig. 5, the device includes:
an obtaining module 510, configured to obtain a ferry target file, a ferry destination, and a ferry channel according to a network disk ferry file operation;
a determining module 520, configured to determine a ferry instance identifier according to the ferry target file and the ferry destination;
a searching module 530, configured to search whether the same ferry instance exists according to the ferry instance identifier;
the server determining module 540 is configured to determine, when the same ferry instance identifier exists, a corresponding transfer FTP server according to the ferry instance;
a creating module 550, configured to create a ferry file directory in the transit FTP server, and name the ferry file directory according to a ferry instance identifier and a ferry task identifier;
the uploading module 560 is configured to traverse a database file, obtain a file block of the ferry target file, and upload the file block to the ferry file directory;
and the packaging module 570 is used for packaging the ferry description file according to the information of the ferry instance and the ferry task information, and uploading the ferry description file to a ferry directory.
The device for sending the network disk ferry file provided by the embodiment obtains a ferry target file and a ferry destination through operation according to the network disk ferry file; determining a ferry instance identifier according to the ferry target file and a ferry destination; searching whether the same ferry instance exists according to the ferry instance identifier; when the same ferry instance identification exists, determining a corresponding transfer FTP server according to the ferry instance; creating a ferry file directory in the transfer FTP server, and naming the ferry file directory according to a ferry instance identifier and a ferry task identifier; traversing database files, acquiring file blocks of the ferry target file, and uploading the file blocks to the ferry file directory; and packaging the ferry description file according to the information of the ferry instance and the ferry task information, and uploading the ferry description file to a ferry directory. The corresponding ferry instance can be determined according to the network disk ferry operation information, and the ferry description file is generated by automatic packaging according to the ferry instance and the ferry task information, so that a ferry file receiving task can be automatically created by the ferry receiving terminal network disk according to the ferry description file, and the permission is set for a receiver and the ferry file is transferred. The safety and the convenience of the network disk file ferrying can be improved.
On the basis of the above embodiments, the apparatus includes:
and the generating module is used for generating a ferry instance according to the ferry target file, the ferry destination and the ferry channel when the same ferry instance does not exist, and determining a corresponding transfer FTP server by using the ferry instance.
On the basis of the foregoing embodiments, the determining module includes:
and the identification generation unit is used for generating a ferry instance identification according to the ferry destination number and the ferry target file brief description.
On the basis of the foregoing embodiments, the creating module includes:
and the naming unit is used for naming the ferry file directory according to the ferry instance identifier and the ferry task sequence number.
On the basis of the above embodiments, the encapsulation module includes:
the first writing unit is used for writing the information of the receiver into the identification of the ferry receiver;
the second writing unit is used for writing the storage path of the ferry file into the storage path identifier;
a third writing unit, configured to write the receiving path into the receiving path identifier;
and the fourth writing unit is used for writing the authority code into the authority identifier.
The device for sending the network disk ferry file provided by the embodiment of the invention can execute the method for sending the network disk ferry file provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
EXAMPLE six
Fig. 6 is a schematic structural diagram of a network disk ferry file system provided in a sixth embodiment of the present invention, and referring to fig. 6, the system for implementing cross-network-segment cooperative processing of a document includes: a first mesh plate and a second mesh plate.
Correspondingly, the first network disk comprises the receiving device for the network disk ferry file provided by the embodiment;
the second network disk comprises the sending device of the network disk ferry file provided by the embodiment.
The network disk ferry file system provided by the embodiment of the invention utilizes the read ferry description file, utilizes the special ferry account to execute the corresponding ferry receiving task, and executes the task in the namespace of the ferry account so as to avoid the conflict among a plurality of ferry tasks. And storing the document block of the document by using the task, acquiring the information of the receiver, the authority information and the storage path information by analyzing the ferry description file, authorizing the receiver by using the ferry account, and transferring the document to a corresponding directory. The ferry account is set to execute the ferry task, so that other users do not need to participate in the ferry process, and the right is correspondingly given according to the ferry description file. Effectively ensures the safety of the document in the ferrying process and prevents the leakage of secret. Meanwhile, the document can be transferred according to the storage path in the ferry description file, so that the document is prevented from being manually transferred by a user, and the working efficiency is improved.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (14)

1. A method for receiving a network disk ferry file is characterized by comprising the following steps:
acquiring a ferry description file from a ferry directory in an FTP server, and reading the ferry description file;
establishing a ferry receiving task according to the ferry description file by using a ferry account, establishing a ferry account name space for the ferry receiving task, and transferring the ferry receiving task to the ferry account name space for execution;
determining a ferry file directory according to the ferry receiving task, downloading file blocks of the ferry file from the ferry file directory, and storing the file blocks;
analyzing the ferry description file, acquiring receiver information from the ferry description file, and setting authority for the receiver of the ferry file;
and acquiring a storage path from the ferry description file, and transferring the ferry file to a directory corresponding to the storage path.
2. The method of claim 1, wherein after setting the authority for the ferry file recipient, prior to obtaining a storage path from the ferry description file, the method further comprises:
and transferring the ferry receiving task to a receiver name space for execution.
3. The method of claim 1, further comprising:
and judging whether a receiver exists in the network disk organization framework or not, and terminating the ferry receiving task when the receiver does not exist.
4. The method of claim 1, wherein said retrieving a storage path from said ferry description file comprises:
and extracting storage path information from the ferry description file according to the set format and the set characteristic symbol.
5. The method of claim 4, further comprising:
and when the storage path information is not extracted, extracting a source path of the ferry file according to a set format and a set characteristic symbol, and taking the source path as a storage path.
6. The method of claim 5, further comprising:
and correspondingly creating a file directory according to the source path.
7. A method for sending a network disk ferry file is characterized by comprising the following steps:
acquiring a ferry target file and a ferry destination according to the operation of the network disk ferry file;
determining a ferry instance identifier according to the ferry target file and the ferry destination;
searching whether the same ferry instance exists according to the ferry instance identifier;
when the same ferry instance identification exists, determining a corresponding transfer FTP server according to the ferry instance;
creating a ferry file directory in the transfer FTP server, and naming the ferry file directory according to a ferry instance identifier and a ferry task identifier;
traversing database files, acquiring file blocks of the ferry target file, and uploading the file blocks to the ferry file directory;
and packaging the ferry description file according to the information of the ferry instance and the ferry task information, and uploading the ferry description file to a ferry directory.
8. The method of claim 7, comprising:
and when the same ferry instance does not exist, generating a ferry instance according to the ferry target file, the ferry destination and the ferry channel, and determining a corresponding transfer FTP server by using the ferry instance.
9. The method of claim 7, wherein said determining a ferry instance identification from said ferry target file and ferry destination comprises:
and generating a ferry instance identifier according to the ferry destination number and the ferry target file brief description.
10. The method of claim 9, wherein the naming the ferry file directory according to a ferry instance identifier and a ferry task identifier comprises:
and naming the ferry file directory according to the ferry instance identifier and the ferry task sequence number.
11. The method of claim 7, wherein encapsulating the ferry description file according to the information of the ferry instance comprises:
writing the information of the receiver into the identification of the ferry receiver;
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 authority code into the authority identifier.
12. A receiving device for a network disk ferry file is characterized by comprising:
the reading module is used for acquiring a ferry description file from a ferry directory in the FTP server and reading the ferry description file;
the system comprises a creating module, a data processing module and a data processing module, wherein the creating module is used for creating a ferry receiving task according to the ferry description file by using a ferry account, creating a ferry account name space for the ferry receiving task, and transferring the ferry receiving task into the ferry account name space for execution;
the storage module is used for determining a ferry file directory according to the ferry receiving task, downloading file blocks of the ferry file from the ferry file directory and storing the file blocks;
the analysis module is used for analyzing the ferry description file, acquiring receiver information from the ferry description file and setting authority for a receiver of the ferry file;
and the transfer module is used for acquiring a storage path from the ferry description file and transferring the ferry file to a directory corresponding to the storage path.
13. A transmission device for a network disk ferry file is characterized by comprising:
the acquisition module is used for acquiring a ferry target file, a ferry destination and a ferry channel according to the operation of the network disk ferry file;
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 searching module is used for searching whether the same ferrying examples exist according to the ferrying example identifications;
the server determining module is used for determining a corresponding transfer FTP server according to the ferry instance when the same ferry instance identifier exists;
the creating module is used for creating a ferry file directory in the transfer FTP server and naming the ferry file directory according to a ferry instance identifier and a ferry task identifier;
the uploading module is used for traversing database files, acquiring file blocks of the ferry target file and uploading the file blocks to the ferry file directory;
and the packaging module is used for packaging the ferry description file according to the information of the ferry instance and the ferry task information and uploading the ferry description file to a ferry directory.
14. A network disk ferry file system, comprising: a first mesh plate and a second mesh plate,
the first network disk comprises the network disk ferry file sending device of claim 13;
the second net disk comprises a receiving device of the net disk ferry file of claim 12.
CN202210918831.1A 2022-08-02 2022-08-02 Method, device and system for receiving and sending network disk ferry file Active CN114979126B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202210918831.1A CN114979126B (en) 2022-08-02 2022-08-02 Method, device and system for receiving and sending network disk ferry file
CN202211570454.3A CN116192830A (en) 2022-08-02 2022-08-02 Method and device for sending network disk ferry file

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210918831.1A CN114979126B (en) 2022-08-02 2022-08-02 Method, device and system for receiving and sending network disk ferry file

Related Child Applications (1)

Application Number Title Priority Date Filing Date
CN202211570454.3A Division CN116192830A (en) 2022-08-02 2022-08-02 Method and device for sending network disk ferry file

Publications (2)

Publication Number Publication Date
CN114979126A true CN114979126A (en) 2022-08-30
CN114979126B CN114979126B (en) 2022-12-23

Family

ID=82969943

Family Applications (2)

Application Number Title Priority Date Filing Date
CN202211570454.3A Pending CN116192830A (en) 2022-08-02 2022-08-02 Method and device for sending network disk ferry file
CN202210918831.1A Active CN114979126B (en) 2022-08-02 2022-08-02 Method, device and system for receiving and sending network disk ferry file

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN202211570454.3A Pending CN116192830A (en) 2022-08-02 2022-08-02 Method and device for sending network disk ferry file

Country Status (1)

Country Link
CN (2) CN116192830A (en)

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102196004A (en) * 2010-03-12 2011-09-21 新奥特(北京)视频技术有限公司 Management method and system of remote material file
WO2015172616A1 (en) * 2014-05-16 2015-11-19 北京奇虎科技有限公司 Method, device and system for uploading file to cloud disk, and cloud disk server
CN106713283A (en) * 2016-12-03 2017-05-24 浙江广播电视集团 Internetwork secure interaction system and method based on PaaS media technology
CN107800713A (en) * 2017-11-10 2018-03-13 北京明朝万达科技股份有限公司 The secure exchange method and system of data between a kind of net
CN108833387A (en) * 2018-06-01 2018-11-16 江苏中安联科信息技术有限公司 A kind of internet high security enterprise cloud platform
CN111464561A (en) * 2020-04-21 2020-07-28 南京珥仁科技有限公司 Data ferry management system
CN113946547A (en) * 2021-12-21 2022-01-18 天津联想协同科技有限公司 Method and device for ferrying network disk file, network disk and storage medium
CN113988025A (en) * 2021-12-28 2022-01-28 天津联想协同科技有限公司 Method, device and system for sending, transmitting and receiving cooperative processing document
CN114706651A (en) * 2022-06-06 2022-07-05 天津联想协同科技有限公司 Method and device for prompting ferry state of network disk file, network disk and storage medium

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102196004A (en) * 2010-03-12 2011-09-21 新奥特(北京)视频技术有限公司 Management method and system of remote material file
WO2015172616A1 (en) * 2014-05-16 2015-11-19 北京奇虎科技有限公司 Method, device and system for uploading file to cloud disk, and cloud disk server
CN106713283A (en) * 2016-12-03 2017-05-24 浙江广播电视集团 Internetwork secure interaction system and method based on PaaS media technology
CN107800713A (en) * 2017-11-10 2018-03-13 北京明朝万达科技股份有限公司 The secure exchange method and system of data between a kind of net
CN108833387A (en) * 2018-06-01 2018-11-16 江苏中安联科信息技术有限公司 A kind of internet high security enterprise cloud platform
CN111464561A (en) * 2020-04-21 2020-07-28 南京珥仁科技有限公司 Data ferry management system
CN113946547A (en) * 2021-12-21 2022-01-18 天津联想协同科技有限公司 Method and device for ferrying network disk file, network disk and storage medium
CN113988025A (en) * 2021-12-28 2022-01-28 天津联想协同科技有限公司 Method, device and system for sending, transmitting and receiving cooperative processing document
CN114706651A (en) * 2022-06-06 2022-07-05 天津联想协同科技有限公司 Method and device for prompting ferry state of network disk file, network disk and storage medium

Also Published As

Publication number Publication date
CN114979126B (en) 2022-12-23
CN116192830A (en) 2023-05-30

Similar Documents

Publication Publication Date Title
US8914856B1 (en) Synchronization of networked storage systems and third party systems
CN108933805A (en) A kind of document transmission method and system
CN111338893B (en) Process log processing method, device, computer equipment and storage medium
CN103780700A (en) Application system and method for achieving compatibility and sharing among multi-source heterogeneous systems
CN103475682A (en) File transfer method and file transfer equipment
US20080244514A1 (en) Scriptable object model for network based services
CN103927252A (en) Cross-component log recording method, device and system
CN104079623A (en) Method and system for controlling multilevel cloud storage synchrony
CN114979126B (en) Method, device and system for receiving and sending network disk ferry file
CN103973772B (en) File read/write method and device
CN111414339B (en) File processing method, system, device, equipment and medium
WO2024198818A1 (en) Device configuration method and system, and device and storage medium
CN106803836B (en) Multi-center file forwarding processing method and device
CN113382012A (en) Internal and external network data exchange method, device, equipment and storage medium
CN112650710A (en) Data migration sending method and device, storage medium and electronic device
CN115826828B (en) Network disk file operation method, device, terminal and storage medium
CN103220327B (en) user information storage method and device
US9002788B2 (en) System for configurable reporting of network data and related method
US9626371B2 (en) Attribute selectable file operation
CN103312533A (en) Information processing system, information processing apparatus, apparatus, and non-transitory computer readable medium storing information processing program
CN113726838A (en) File transmission method, device, equipment and storage medium
CN117896182B (en) Linux network communication security management and control method, device and storage medium
CN102724547A (en) Remote data acquisition system and remote data acquisition method
CN114629954B (en) Content distribution method, system, device and storage medium
JP4274530B2 (en) Operation method of configuration management target file in software configuration management system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant