WO2019047976A1 - Procédé de gestion de fichiers réseau, terminal et support de stockage lisible par ordinateur - Google Patents

Procédé de gestion de fichiers réseau, terminal et support de stockage lisible par ordinateur Download PDF

Info

Publication number
WO2019047976A1
WO2019047976A1 PCT/CN2018/105059 CN2018105059W WO2019047976A1 WO 2019047976 A1 WO2019047976 A1 WO 2019047976A1 CN 2018105059 W CN2018105059 W CN 2018105059W WO 2019047976 A1 WO2019047976 A1 WO 2019047976A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
network
local terminal
remote server
management method
Prior art date
Application number
PCT/CN2018/105059
Other languages
English (en)
Chinese (zh)
Inventor
孙怡
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2019047976A1 publication Critical patent/WO2019047976A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/188—Virtual file systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/188—Virtual file systems
    • G06F16/192—Implementing virtual folder structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display

Definitions

  • the present disclosure relates to, but is not limited to, the field of cloud storage.
  • the user After logging in to the cloud disk through the web page or the client, the user needs to operate the network file in the cloud disk according to the cloud disk operation mode provided by the cloud disk operator.
  • the cloud disk operators provided by different cloud disk operators operate in different ways. Therefore, different cloud disk operation modes often cause inconvenience to users. For example, users need to read the cloud disk usage instructions, and then learn how to operate, etc., which is reduced. User experience.
  • a network file management method including: obtaining, by a communication link between a local terminal and a remote server, a file storage attribute of a network file on a remote server; and constructing and displaying a virtual file system corresponding to the file storage attribute.
  • the operation mode of the virtual file system is matched with the file operation mode of the local terminal; the management operation of the user in the virtual file system is monitored; and the network file is managed according to the management operation through the communication link.
  • a network file management terminal including a processor, a memory, and a communication bus, wherein the communication bus is used to implement connection communication between the processor and the memory, and the processor executes one or more stored in the memory At the time of the program, the processor executes the network file management method according to the present disclosure.
  • Embodiments of the present disclosure also provide a computer readable storage medium having stored thereon one or more programs, the one or more programs being executed by one or more processors, the one or more processors executing A network file management method according to the present disclosure.
  • FIG. 1 shows a common interface diagram of a cloud disk in the related art
  • FIG. 2 is a flowchart of a network file management method according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of a virtual file system in accordance with an embodiment of the present disclosure.
  • FIG. 4 is another schematic diagram of a virtual file system in accordance with an embodiment of the present disclosure.
  • FIG. 5 is a schematic structural diagram of a network file management terminal according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of a network architecture of a network file management terminal according to an embodiment of the present disclosure
  • FIG. 7 is a flowchart of a network file management method according to an embodiment of the present disclosure.
  • FIG. 8 is a flowchart of a cloud disk login according to an embodiment of the present disclosure.
  • FIG. 9 is a flowchart of an open file operation in accordance with an embodiment of the present disclosure.
  • FIG. 10 is a flowchart of an update file operation according to an embodiment of the present disclosure.
  • FIG. 11 is a flow chart of a delete file operation in accordance with an embodiment of the present disclosure.
  • FIG. 1 shows a common interface diagram of a cloud disk in the related art.
  • the file management interface only the file/folder list of the corresponding layer is displayed. For example, only the folder 1, the folder 2, and the file 3 are displayed when the user enters the initial interface of the cloud disk. For the subfiles/folders in folder 1 and folder 2, even if the user moves the mouse over the icon of folder 1, it will not be displayed. Users need to open folder 1 or folder 2 to see it. Subfiles/folders within. For storage space information, the initial interface is not displayed at all, and the user needs to open a specific query option for query.
  • FIG. 2 is a flow chart of a network file management method in accordance with an embodiment of the present disclosure.
  • a network file management method may include steps S101 to S104.
  • step S101 the file storage attribute of the network file on the remote server is obtained through a communication link between the local terminal and the remote server.
  • the file storage attributes include a file directory structure, a file list, file attributes, and storage space information of the network file on the remote server.
  • the file directory structure specifically refers to the inclusion relationship between the file and the folder, the reference relationship between the files, and the like, and is usually embodied by a file tree.
  • the file list is a list of all files and folders.
  • File attributes include information such as the size, creation time, update time, and file type of each file or folder.
  • the storage space information is the storage space allocated by the remote server such as the cloud disk operator, the size of the used storage space, and the remaining space size.
  • step S102 a virtual file system corresponding to the file storage attribute is constructed and displayed, and the operation mode of the virtual file system matches the file operation mode of the local terminal.
  • the constructing the virtual file system may include: acquiring a storage space display manner and a file information display manner in a file operation mode of the local terminal; displaying the storage space information by using the storage space display manner; and using the file information.
  • the display mode displays the file directory structure, file list, and file attributes.
  • the file operation mode of the local terminal is related to the operating system of the local terminal.
  • the following is an example of the operating system of the local terminal as the Windows system. It is foreseeable that the implementation of other operating systems is similar, so it will not be described again.
  • the storage space display mode is to display the total space size, the occupied space size, and the remaining space size on the disk display interface
  • the file information display manner is to display the file or folder in a list manner, and when the user moves the mouse to When a folder is displayed, the properties and lists of its internal folders/files are displayed.
  • FIG. 3 is a schematic diagram of a virtual file system in accordance with an embodiment of the present disclosure.
  • the cloud disk is virtualized as a disk E and displayed separately.
  • information such as the total space size, the used space size, and the remaining space size are displayed.
  • the cloud disk can also be virtualized as a folder, which is substantially the same as the mode of virtual disk, and will not be described again.
  • FIG. 4 is another schematic diagram of a virtual file system in accordance with an embodiment of the present disclosure.
  • the folder 1, the folder 2, and the file 3 are displayed in a list manner.
  • the attributes and lists of the folders/files inside thereof are displayed, for example, the names, sizes, modification dates, and the like of the files 4 and 5 are displayed.
  • step S103 the user's management operation in the virtual file system is monitored.
  • the management operation includes a normal user operation, and may be an operation in which a user double-clicks a file to open a corresponding file, an operation of deleting a file by a delete key, an operation of uploading a new file, and an operation of replacing a file. , as well as the operation of updating a file, and so on. The following will explain the different operations separately.
  • step S104 the network file is managed according to the management operation through the communication link.
  • the management operation may include an opening operation
  • step S104 may include: determining a first file corresponding to the opening operation; searching for the first file in the local terminal cache; opening the first file if the first file is found And if the first file is not found, the first file is downloaded from the remote server via the communication link, and the downloaded first file is opened.
  • the step S104 may further include: determining whether the remaining space of the local terminal cache is greater than the size of the first file; if the remaining space of the local terminal cache is greater than the size of the first file, the first file is cached. In the local terminal cache; if the remaining space of the local terminal cache is not larger than the size of the first file, delete the file with the oldest timestamp in the local terminal cache until the remaining space of the local terminal cache is larger than the size of the first file, and then A file is cached in the local terminal cache.
  • a caching mechanism is introduced to download and cache a network file from a server, so that the user can directly open and edit the cached file.
  • the terminal transmits the user's operation to the server in real time, and the server completes the editing of the file in response to the user operation, and the user can respond to the user operation in real time according to the embodiment of the present disclosure without requiring the server response, so that the user edits the speed. It is faster and can be edited in a way that users are accustomed to, which is convenient for users to manage.
  • the management operation may include an update operation
  • step S104 may include: determining a second file corresponding to the update operation; and synchronizing the update content of the second file to the remote server in an incremental update manner.
  • the second file may be subjected to blocking processing according to a preset rule.
  • the preset rule may be, for example, the size of the data block (for example, 10 KB), so that the second file is divided into a plurality of data blocks having a size of 10 KB.
  • the check value of each data block of the second file in the local terminal and the check value of each data block of the second file in the remote server may be calculated, and the check values of each data block are sequentially compared to determine the check value. Different data blocks.
  • the data block with different check values in the second file in the local terminal may be used as the update content, and the data block corresponding to the second file in the remote server may be updated.
  • the management operation may include a delete operation
  • step S104 may include: determining a third file corresponding to the delete operation; deleting the third file in the remote server by the communication link; and deleting the file storage attribute and the third Information about the file.
  • the management operation may include a replacement operation
  • step S104 may include: determining a fourth file corresponding to the replacement operation; downloading the fourth file from the remote server through the communication link; deleting the second server in the remote server through the communication link Four files; operating the fourth file in the local terminal to generate a fifth file; and transmitting the fifth file to the remote server through the communication link.
  • the step of building a virtual file system includes building a virtual file system based on the file storage attributes cached in the local terminal cache.
  • the file storage attribute may be subjected to block processing according to a preset rule, and the check value of each data block of the file storage attribute in the local terminal cache and the network file may be calculated on the remote server.
  • the check value of each data block may be sequentially compared to determine a data block with different check values, and the data block with different check value in the file storage attribute of the network file on the remote server is used as the synchronization content, and is cached in the local terminal.
  • the data block corresponding to the file storage attribute is updated.
  • the local terminal involved in the present disclosure includes various devices having network communication functions, such as a computer, a tablet, a mobile phone, a set top box, and the like.
  • a file storage attribute such as a directory of a network file on a remote server is obtained through a communication link between the local terminal and the remote server, and then a virtual operation mode is matched with a file operation mode of the local terminal.
  • the user can manage the network file on the virtual file system by using the file operation mode of the local terminal, and then manage the network file stored on the remote server based on the communication link between the local terminal and the remote server.
  • the user only needs to operate according to the normal operation mode, and does not need to learn the operation modes of various cloud disks, thereby solving the problem that the user operation is inconvenient due to the need to learn the operation mode of the cloud disk, and the problem is improved.
  • User experience In the meantime, according to the embodiment of the present disclosure, only the virtual file system needs to be constructed and displayed on the client, and the remote server is not required to be modified by the cloud disk operator or the like, so that it can be compatible with various cloud disk services.
  • FIG. 5 is a schematic structural diagram of a network file management terminal according to an embodiment of the present disclosure.
  • a network file management terminal may include a processor 21, a memory 22, and a communication bus 23.
  • the communication bus 23 is used to implement connection communication between the processor 21 and the memory 22.
  • the processor 21 executes one or more programs stored in the memory 22, the processor 21 can execute a network file management method according to various embodiments of the present disclosure.
  • the present disclosure also provides a computer readable storage medium having stored thereon one or more programs that, when executed by one or more processors, can execute a network in accordance with embodiments of the present disclosure File management method.
  • FIG. 6 is a schematic diagram of a network architecture of a network file management terminal according to an embodiment of the present disclosure.
  • the bottom layer is the physical layer hardware, including the connection mode provided by the communication module such as wired network and wireless network; the TCP/IP protocol layer is above the physical layer hardware; and the application layer is above TCP/IP.
  • Protocols such as HTTP (Hypertext Transfer Protocol) and REST (Representational State Transfer) interfaces belong to the HTTP protocol.
  • HTTP Hypertext Transfer Protocol
  • REST Real-Time Transfer
  • the common interface hides the differences between different protocol layers, different devices, and different operating systems, providing a unified file access interface for applications, and applications use common interfaces to implement different applications.
  • FIG. 7 is a flowchart of a network file management method according to an embodiment of the present disclosure.
  • the network file management method may include steps S401 to S404.
  • step S401 the file storage attribute of the network file is acquired, and a local virtual file system is constructed.
  • FIG. 8 is a flow chart of a cloud disk login according to an embodiment of the present disclosure.
  • the cloud disk login may include steps S501 to S504.
  • step S501 the user logs in to the cloud disk using an account password or the like.
  • the cloud disk login interface is opened, and then the login is initiated according to the account and password input by the user. After the verification is passed, the cloud disk login is successful.
  • TOKEN token
  • step S502 the storage information of the cloud disk and the file information of the network file are acquired.
  • step S503 a virtual file system of the local terminal is constructed.
  • a new file system can be created on the Windows system as a virtual file system corresponding to the cloud disk, and the interface thereof is a display interface of the virtual file system, as shown in FIG. 3 or FIG. 4, the virtual file system and the local terminal.
  • the way the operating system displays information can be identical.
  • the Dokan library is a library that helps programmers build user-level file systems on Windows systems. The following is an example of establishing a virtual file system through the Dokan library.
  • the Dokan library contains a user-mode dynamic link library (DLL) file (dokan.dll) and a kernel mode file system driver (dokan.sys). Once the Dokan file system driver is installed, you can create the same file system on the Windows system as the normal file system.
  • An application that uses a file system created by the Dokan library is called a file system application. File operation requests from the user program (eg, create files, read files, write files, etc.) will be sent to the Windows input/output subsystem (which runs in kernel mode), and then file operation requests will be sent to the Dokan file.
  • DLL user-mode dynamic link library
  • daokan.sys kernel mode file system driver
  • the file system application can register a callback function with the file system driver. After receiving the operation request in the file, the file system driver can call the registered callback function routine to respond to the file operation request, and the processing result of the callback function routine is returned to the user program.
  • the file operation request "OpenDirectory” will be sent to the Dokan file system driver (dokan.sys), and then the driver will call the file system application to provide the "OpenDirectory" request.
  • Corresponding callback function routines The result of the function routine is returned to the Windows Explorer as a response to the "OpenDirectory" request.
  • the Dokan file system driver (dokan.sys) can be thought of as an agent between the user program and the file system program.
  • the virtual file system is configured and displayed.
  • the Dokan file system can be used to map information such as the directory structure, file list, and file attributes on the cloud disk server to a drive letter under the local Windows system, so that the user can browse various files.
  • the Dokan file system can monitor the addition, deletion, and modification of files in the local Windows operating system. These operations can be formed as interfaces.
  • the application can implement the service connection with the background server in these interfaces.
  • the REST interface of the HTTP protocol can be used. Docking these businesses.
  • the disk E can be initialized, then the storage information of the cloud disk is configured as the storage attribute of the disk E, and the file information of the network file is Write to disk E, as shown in Figure 4.
  • step S402 the local terminal cache is configured and enabled.
  • the local application can open up a memory space for caching the contents of the file, and also needs to set a threshold. When the threshold is exceeded, the memory space of the first file content needs to be released.
  • small files such as files smaller than 20MB
  • the Dokan file system can be used to directly read the file contents to effectively reduce the network load.
  • step S403 the incremental synchronization algorithm is configured and enabled.
  • the mechanism of incremental synchronization that is, the differential synchronization algorithm, can be used, and the content transmitted in the network is only a difference part, not all. content.
  • a synchronization thread can be set in the background, and the content in the buffer and the server are synchronized every predetermined time period.
  • the file can be divided into multiple data blocks on the client, and an MD5 (Message Digest Algorithm 5) value is calculated as a strong check value and a checksum as a weak check value for each data block. And send it to the server.
  • MD5 Message Digest Algorithm 5
  • the server divides the corresponding file into blocks of the same block size, and calculates the MD5 value and checksum of each data block, and checks whether each data block is consistent with a certain checksum sent by the client, if it is in the server file.
  • the checksum of the data block is consistent with a checksum sent by the client, indicating that the content of the data block in the server file is likely to be consistent with the data block content of the file in the corresponding client, but due to the school
  • the checksum strength is not enough, so the MD5 value is matched again. If the MD5 values of the two data blocks are also matched, it is confirmed that the contents of the two data blocks are consistent, and the server can send the matching segment number to the client. For those data blocks that cannot be matched, the server sends the original content of the data block to the client.
  • the client obtains the matching information sent by the server, and can construct a replica that is consistent with the server file.
  • the replication server sends the The content of the data block.
  • step S404 the management operation of the user is monitored and executed.
  • FIG. 9 is a flow diagram of an open file operation in accordance with an embodiment of the present disclosure.
  • the opening file operation may include: determining a first file corresponding to the opening operation; searching for the first file in the local terminal cache; and opening the first file if the first file is found The first file; and if the first file is not found, downloading the first file from the remote server through the communication link, and opening the downloaded first file.
  • the user can double-click a certain network file (ie, the first file) in the resource manager to perform an opening operation (step S601).
  • a certain network file ie, the first file
  • the resource manager can perform an opening operation (step S601).
  • step S602 it is determined whether the network file has been cached in the local cache (step S602). If the network file has been cached, the content of the network file is directly read from the cache (step S603); otherwise, the REST interface can be used to download from the server.
  • the network file step S604.
  • step S605 After downloading the network file from the remote server, it may be judged whether the remaining space of the local terminal cache is larger than the size of the network file (step S605). If the remaining space of the local terminal cache is larger than the size of the network file, the network file is cached in the local terminal cache (step S607); if the remaining space of the local terminal cache is not greater than the size of the network file, the local is deleted. The file with the oldest timestamp in the terminal cache (step S606) until the remaining space of the local terminal cache is larger than the size of the network file, and then the network file is cached in the local terminal cache (step S607).
  • FIG. 10 is a flowchart of an update file operation in accordance with an embodiment of the present disclosure.
  • the update file operation may include: determining a second file corresponding to the update operation; and synchronizing the updated content of the second file to the remote server in an incremental update manner.
  • the edited file ie, the second file
  • the remote server step S701
  • the edited The updated content of the file is synced to the cloud disk.
  • the second file may be subjected to blocking processing according to a preset rule, and a check value of each data block of the second file in the local terminal and a check value of each data block of the second file in the remote server may be calculated.
  • the check values of the data blocks may be sequentially compared to determine data blocks with different check values, and the data blocks with different check values in the second file in the local terminal may be used as the update content, and the second in the remote server.
  • the data block corresponding to the file is updated.
  • the file to be updated is divided into several data blocks, and the strong check value and the weak check value of each data block are calculated.
  • the information i.e., the strong check value and the weak check value of each data block
  • the server divides the corresponding file into blocks according to the same data block size, and calculates a strong check value and a weak check value of each data block (step S703).
  • the server cyclically detects the information of each data block and compares it with the information of each of the transmitted data blocks (step S704). First, it is compared whether the weak check values are the same (step S705).
  • step S706 If the weak check values are not the same, it is determined that the data block is a data block to be updated (step S706); if the weak check values are the same, the strong check is continued. Whether the values are the same (step S707), if the strong check values are not the same, it is determined that the data block is a data block to be updated (step S706); if the strong check value is also the same, it indicates that the data block does not need to be updated (step S708) ). It is judged whether or not all the data blocks are compared (step S709), and when all the data blocks are compared, all the data blocks to be updated are updated (step S710).
  • FIG. 11 is a flow chart of a delete file operation in accordance with an embodiment of the present disclosure.
  • the deleting a file operation may include: determining a third file corresponding to the deletion operation; deleting the third file in the remote server by using the communication link; and deleting the file storage attribute and the third file Related information.
  • step S801 the file to be deleted is obtained (step S801), and then the REST interface is called to delete the file (step S802). Determining the return value of the REST interface (step S803), if the REST interface returns the deletion succeeds, updating the local cache, and deleting the information of the file in the local cache (step S804); if the REST interface returns the deletion failure, the information may not be performed Any operation. Finally, the deletion result is reported to the user (step S805).
  • the remote file can be downloaded to the local, the remote file is deleted, the local file is modified, and the modified local file is re-uploaded to the server.
  • the user can operate according to a conventional operation mode (ie, a file operation mode of the local terminal) without learning the operations of various cloud disks.
  • a conventional operation mode ie, a file operation mode of the local terminal
  • the method is convenient for the user to operate and improves the user experience.
  • only the virtual file system needs to be constructed and displayed on the client, and the cloud server operator or the like is not required to modify the remote server, so that the cloud disk service can be compatible.
  • modules or steps of the above-described embodiments of the present disclosure may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices. Alternatively, they may be implemented by program code executable by a computing device such that they may be stored in a computer storage medium (ROM/RAM, diskette, optical disk) by a computing device, and in some cases
  • ROM/RAM, diskette, optical disk a computer storage medium
  • the steps shown or described may be performed in a different order than that herein, or they may be separately fabricated into individual integrated circuit modules, or a plurality of the modules or steps may be implemented as a single integrated circuit module. Therefore, the present disclosure is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un procédé de gestion de fichiers réseau, un terminal et un support de stockage lisible par ordinateur. Ledit procédé consiste à : acquérir, au moyen d'une liaison de communication entre un terminal local et un serveur distant, un attribut de stockage de fichier, tel que le répertoire, d'un fichier réseau sur le serveur distant; construire et afficher un système de fichier virtuel correspondant à l'attribut de stockage de fichier, le mode de fonctionnement du système de fichier virtuel correspondant à la manière d'opération de fichier d'un terminal local; surveiller l'opération de gestion de l'utilisateur sur le système de fichier virtuel; et réaliser, au moyen de la liaison de communication, la gestion sur le fichier réseau selon l'opération de gestion.
PCT/CN2018/105059 2017-09-11 2018-09-11 Procédé de gestion de fichiers réseau, terminal et support de stockage lisible par ordinateur WO2019047976A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710813217.8A CN110069454A (zh) 2017-09-11 2017-09-11 一种网络文件管理方法、终端及计算机可读存储介质
CN201710813217.8 2017-09-11

Publications (1)

Publication Number Publication Date
WO2019047976A1 true WO2019047976A1 (fr) 2019-03-14

Family

ID=65633547

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/105059 WO2019047976A1 (fr) 2017-09-11 2018-09-11 Procédé de gestion de fichiers réseau, terminal et support de stockage lisible par ordinateur

Country Status (2)

Country Link
CN (1) CN110069454A (fr)
WO (1) WO2019047976A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110727487B (zh) * 2019-09-02 2022-06-10 厦门鑫朗软件有限公司 一种将网盘窗口嵌入到windows资源管理器的方法
CN111444139A (zh) * 2020-03-24 2020-07-24 腾讯科技（深圳）有限公司 一种文件管理方法、装置、设备及存储介质
CN111736777A (zh) * 2020-06-28 2020-10-02 天津联想协同科技有限公司 一种虚拟磁盘的实现方法及装置
CN112667565B (zh) * 2020-12-30 2021-12-03 湖南博匠信息科技有限公司 一种基于fuse的存储单元文件管理方法及系统
CN113238997A (zh) * 2021-07-13 2021-08-10 云宏信息科技股份有限公司 终端设备用的云端数据操作方法、存储介质和终端设备
CN117234410A (zh) * 2022-06-08 2023-12-15 中兴通讯股份有限公司 一种数据文件缓存处理方法、装置、存储介质及电子装置
CN116010364B (zh) * 2023-03-27 2023-08-04 天津联想协同科技有限公司 网盘文件状态的更新方法、装置、网盘及存储介质
CN116566965B (zh) * 2023-07-11 2023-09-26 山东英围特智能科技有限公司 一种ofd大文件的处理方法
CN117312264B (zh) * 2023-12-01 2024-02-20 中孚信息股份有限公司 虚拟磁盘系统中的文件同步方法、系统、设备及介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006116203A1 (fr) * 2005-04-25 2006-11-02 Network Appliance, Inc. Systeme et procede servant a mettre en antememoire des systemes de fichier de reseau
CN102355502A (zh) * 2011-10-13 2012-02-15 罗立群 存储系统远程接入桌面操作系统的远程接入方法
CN102662741A (zh) * 2012-04-05 2012-09-12 华为技术有限公司 虚拟桌面的实现方法、装置和系统
CN103116618A (zh) * 2013-01-28 2013-05-22 南开大学 基于客户端持久缓存的远程文件系统镜像方法及系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102065104A (zh) * 2011-01-10 2011-05-18 深信服网络科技（深圳）有限公司 一种异地文件访问方法、装置及系统
CN103731483B (zh) * 2013-12-25 2017-05-03 侯金涛 一种基于云计算的虚拟文件系统
CN103841113B (zh) * 2014-03-20 2017-01-04 武汉理工大学 一种基于用户模式文件系统的安全网络文件系统
CN104462224A (zh) * 2014-11-12 2015-03-25 成都卫士通信息产业股份有限公司 一种云盘文件在线编辑方法
CN106559392A (zh) * 2015-09-28 2017-04-05 北京神州泰岳软件股份有限公司 一种文件共享方法、装置和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006116203A1 (fr) * 2005-04-25 2006-11-02 Network Appliance, Inc. Systeme et procede servant a mettre en antememoire des systemes de fichier de reseau
CN102355502A (zh) * 2011-10-13 2012-02-15 罗立群 存储系统远程接入桌面操作系统的远程接入方法
CN102662741A (zh) * 2012-04-05 2012-09-12 华为技术有限公司 虚拟桌面的实现方法、装置和系统
CN103116618A (zh) * 2013-01-28 2013-05-22 南开大学 基于客户端持久缓存的远程文件系统镜像方法及系统

Also Published As

Publication number Publication date
CN110069454A (zh) 2019-07-30

Similar Documents

Publication Publication Date Title
US11985192B2 (en) Synchronized content library
US10848557B2 (en) Server-side selective synchronization
WO2019047976A1 (fr) Procédé de gestion de fichiers réseau, terminal et support de stockage lisible par ordinateur
US20220100494A1 (en) Providing access to a hybrid application offline
US10277673B2 (en) Local server for synced online content management system
US11372990B2 (en) Restricting access to content
US20150012861A1 (en) Syncing content clipboard
US10261996B2 (en) Content localization using fallback translations
US10348821B2 (en) Prioritizing structural operations and distributing changes in a synced online content management system
US11442752B2 (en) Central storage management interface supporting native user interface versions
US20230122861A1 (en) Unified metadata search
US9075722B2 (en) Clustered and highly-available wide-area write-through file system cache
US10198449B2 (en) Creating unique content item identifiers
JP2023547439A (ja) 非同期動作のための意図トラッキング

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18853875

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 18853875

Country of ref document: EP

Kind code of ref document: A1