KR20220071493A - Method and apparatus for managing network drive using local cache - Google Patents

Abstract

The present invention relates to a method and an apparatus for managing a network driver using a local cache. The method includes: receiving meta-information on a folder from the network driver; generating a file list provided to a folder of a virtual driver by using the meta-information on the folder, requesting whole data for a file having whole read events to be downloaded by the network driver server; storing, in a local cache folder, the file downloaded from the network driver server and mapping the file with a program requesting the file, storing a file for changed information in the local cache folder, when a work for the file is finished, and uploading the file having the changed information into the network driver.

Description

Method and device for network drive management using local cache {METHOD AND APPARATUS FOR MANAGING NETWORK DRIVE USING LOCAL CACHE}

The present invention relates to a method and apparatus for managing a network drive using a local cache. In more detail, when performing operations in a virtual drive environment, as files stored in the local cache folder are used, the local cache is used to provide an environment in which the speed is not delayed even when performing operations on the entire file. It is to provide a method and apparatus for managing a network drive.

Access to the file is mainly performed in two ways. The first is when only a part of the file is read (Nasca, vaccine, thumbnail, preview, etc.), and the second is when the entire file is read and used (editing using a general application). do.

There are a namespace method and a virtual drive method for accessing these files, but the namespace method has a problem in that files must always be uploaded and downloaded to the server in order to manage the actual files. In particular, in terms of usability, the operation in Windows Explorer and Application (Excel, etc.) is different, and thumbnails and previews are not possible if it is not a downloaded file. That is, there is a disadvantage in that a situation occurs in which a download cannot be made or a response cannot be made for all files.

In the case of Virtual Drive, when editing a file, the actual file is on the server, and the part of the file required for editing is requested from the server to work. will occur

There is a need for a network drive management method that can compensate for the shortcomings of each file access method as described above and can guarantee reliability for speed.

Registered Patent Publication No. 10-1795087 (registered on Nov. 1, 2017)

The technical problem to be solved by the present invention is to provide an environment in which the speed is not delayed even when performing an operation on the entire file by using a file stored in a local cache folder when performing an operation in a virtual drive environment. This is to provide a method and apparatus for managing a network drive using a local cache.

Another technical problem to be solved by the present invention is to provide an environment in which the reliability of speed is guaranteed by preventing unnecessary speed degradation by using a method of loading only a part of a file when the work on the entire file is not performed. This is to provide a method and apparatus for managing a network drive using a local cache that can be provided.

Another technical problem to be solved by the present invention is to provide a method and apparatus for managing a network drive using a local cache that can perform an operation in real time using a local database even when the connection with the network drive server is disconnected to be.

The technical problems of the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the following description.

The method for managing a network drive using a local cache according to an embodiment of the present invention for solving the above problems is a method performed by a computing device. requesting meta information indicating information stored in a folder corresponding to the folder selection event; receiving meta information on the folder from the network drive server; generating a list of files provided to the virtual drive, generating a full read event for the files included in the file list on the virtual drive, and downloading all data on the file for which the full read event has occurred to the network drive server requesting, storing the file downloaded from the network drive server in a local cache folder, mapping the file to the program that requested the file, and storing the changed file after the operation on the file is completed It may include storing the file in a cache folder and uploading the changed file to the network drive.

A network drive management apparatus using a local cache according to another embodiment of the present invention for solving the above problems includes a processor, a network interface, a memory executed by the processor to load a computer program, and the computer program storage to store, wherein the computer program requests meta information indicating information stored in a folder corresponding to the folder selection event to a network drive server according to a folder selection event of a virtual drive (instruction) , an instruction for receiving meta information on the folder from the network drive server, an instruction for generating a file list provided to the folder of the virtual drive using meta information on the folder, included in the file list on the virtual drive An instruction for generating a full read event for a file, an instruction for requesting download of all data for a file for which the full read event has occurred to the network drive server, and storing the file downloaded from the network drive server in a local cache folder an instruction for mapping the file to a program requesting the file, and an instruction for storing a file with changed contents in the local cache folder after work on the file is completed, and uploading the changed file to the network drive may include

1 is a diagram for explaining a method for managing a network drive using a local cache according to an embodiment of the present invention.
2 is a flowchart schematically illustrating a method for managing a network drive using a local cache according to an embodiment of the present invention.
3 is a diagram for explaining an embodiment of generating a file list of a network drive management system using a local cache according to an embodiment of the present invention.
4 is a system flowchart for explaining an information processing process according to the embodiment of FIG. 3 .
5 is a diagram for explaining an embodiment of executing and storing a file for the operation of a network drive management system using a local cache according to an embodiment of the present invention.
6 is a system flowchart for explaining an information processing process according to the embodiment of FIG. 5 .
FIG. 7 is a diagram for specifically explaining step S231 of FIG. 6 .
8 is a diagram illustrating a capacity that can be stored in a local cache folder.
9 is a diagram for explaining an embodiment in which a partial read event for a file is generated.
FIG. 10 is a system flowchart for explaining an information processing process according to the embodiment of FIG. 9 .
11 is a diagram for explaining an embodiment of executing and storing a file in a state in which a network connection with a network drive server is released.
12 is a system flowchart for explaining an information processing process according to the embodiment of FIG. 11 .
13 is a system flowchart illustrating a process of synchronizing with a network drive server after a network connection is reconnected in FIG. 12 .
14 is a diagram for describing a data type included in meta information.
15 is a hardware configuration diagram of an apparatus for managing a network drive using a local cache according to another embodiment of the present invention.

Hereinafter, various embodiments will be described in detail with reference to the accompanying drawings. Advantages and features of according to an embodiment of the present invention, and a method of achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments published below, but may be implemented in various different forms, and only these embodiments make the publication of the present invention complete, and to which one embodiment of the present invention belongs. It is provided to fully inform those of ordinary skill in the art the scope of the invention, and the present invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the meaning commonly understood by those of ordinary skill in the art to which an embodiment of the present invention pertains. can In addition, terms defined in a commonly used dictionary are not to be interpreted ideally or excessively unless clearly defined in particular. The terminology used herein is for the purpose of describing the embodiments and is not intended to limit the present invention. In this specification, the singular also includes the plural unless specifically stated otherwise in the phrase.

Hereinafter, some embodiments will be described with reference to the drawings.

1 is a diagram for explaining a method for managing a network drive using a local cache according to an embodiment of the present invention, and FIG. 2 is a flowchart schematically illustrating a method for managing a network drive using a local cache according to an embodiment of the present invention. to be.

The method of managing a network drive using a local cache according to the present embodiment is a method of providing and managing data to a client through a virtual disk drive in a network environment for centralizing data. According to the present embodiment, information desired by a client can be provided at high speed by mixing a virtual drive and a namespace method.

Referring to FIG. 1 , in step S100, a list of files that can be displayed in a virtual drive environment may be generated. This file list includes information about the file and the path of the file through the client's explorer, and may point to the list of files stored in each folder of the network drive server.

Specifically, each folder of the network drive server can be selected and searched by the client, and as each folder is selected, meta information indicating information stored in each folder is received from the network drive server, and this meta information is retrieved from the network drive server. A file list containing information about subfolders and files stored in each folder of the network drive server can be created and provided to the client by using it.

In step S200, the file included in the folder of the network drive server may be executed through the explorer provided in the virtual drive environment. Such a file may be a file of various types for work, and is not limited to any one type. Thereafter, a file download is requested to a network drive server according to an execution event of the file, and the downloaded file may be stored in a local cache folder and then mapped to a corresponding program. These files can be modified by the operation of the corresponding program, and the files whose contents are changed afterwards can be stored in a local cache folder and uploaded to a network drive server again.

In order to examine this embodiment in more detail, reference is made to FIG. 2 .

In FIG. 2 , when step S100 is performed, steps S110 to S140 may be performed, and when step S200 is performed, steps S210 to S250 may be performed.

Specifically, meta information may be requested from the network drive server according to the folder selection event of the virtual drive in step S110. The meta information may refer to information stored in a folder corresponding to a folder selection event.

Thereafter, meta information about the folder may be received from the network drive server in step S120. That is, meta information can be obtained by requesting the network drive server at the same time as the folder opening operation like a folder selection event.

In step S130, a list of files provided in a folder of a virtual drive may be created using meta information about the folder. The created file list may be responded to by the explorer, and the explorer may provide a list of data stored in the corresponding folder of the network drive server through the virtual drive and simple information about the file using the file list. A detailed description of the meta information and the file list will be provided later.

In step S140, meta information may be stored in a local database. This step is not essential for generating the file list, but is shown in FIG. 2 for reference as a step necessary for the embodiment to acquire meta information by itself in case the connection with the network drive server to be described later is released. it has become

After that, in step S200, the file for the job may be executed and the modified file may be stored. In step S210, a full read event for the file included in the file list may be generated on the virtual drive. A read-all event for a file is an event that requests access to data about the file in its entirety by opening the file.

In this case, it may be checked whether a file corresponding to the entire read event exists in the local cache folder in step S220. If the file corresponding to the full read event exists in the local cache folder, the program may be mapped to the file stored in the local cache folder and the operation may be performed without downloading the file.

In step S230, a download of all data for the file in which the full read event has occurred may be requested to the network drive server.

In step S240, the entire data of the file may be downloaded from the network drive server. Downloaded files may be stored in a local cache folder. The local cache folder is a storage space that operates the cache managed in units of files. In this step, the file is stored in the local cache folder, and the file stored in the local cache folder can be mapped to the requested program. The full read event can be generated through the explorer of the virtual drive, but it can also be generated through a program. can access

Thereafter, after the operation on the file stored in the cache folder is completed in step S250, the changed file may be stored in the local cache folder, and the changed file may be uploaded to the network drive.

In the method for managing a network drive using a local cache according to an embodiment of the present invention, when performing an operation in a virtual drive environment, since files stored in the local cache folder are used, the speed is not delayed even when performing an operation on all files. It can provide an environment that is not.

In addition, according to the present embodiment, when the operation of the entire file is not performed, it is possible to provide an environment in which the reliability of the speed is guaranteed by preventing the speed from being unnecessarily lowered by using the method of loading only a part of the file. . Hereinafter, step S100 described in FIGS. 1 and 2 will be described in detail with reference to FIGS. 3 and 4 .

3 is a diagram for explaining an embodiment of generating a file list of a network drive management system using a local cache according to an embodiment of the present invention.

Referring to FIG. 3 , the network drive management system using the local cache may include the explorer 2 , the agent 100 , the network drive server 200 , the local cache folder 300 , and the local database 400 .

The explorer 2 is a program 3 that can search a folder stored in the network drive server 200 in a virtual drive environment. When a folder is selected by the explorer 2 , a folder selection event is transmitted to the agent 100 , and the agent 100 may request meta information from the network drive server 200 . The agent 100 may receive meta information from the network drive server 200 . The agent 100 checks the version of the file stored in the local cache folder 300 using meta information, creates a file list using the meta information, and then calls back the file list to the explorer 2 . have. The agent 100 may store meta information in the local database 400 . In order to examine this embodiment in more detail, reference is made to FIG. 4 .

4 is a system flowchart for explaining an information processing process according to the embodiment of FIG. 3 .

In FIG. 4 , the user of the client may be logged in through the agent 100 in step S101. In step S102, it may be checked whether the file in the local cache folder 300 corresponds to the deletion policy at the time of login. As will be described later, a file in the local cache folder 300 may be deleted if it corresponds to a deletion policy. In this step, if the storage period of the file stored in the local cache folder 300 is exceeded and falls under the deletion policy, it may be deleted.

In step S110 , a folder selection event of a virtual drive may be generated by the agent 100 , and meta information may be requested from the network drive server 200 . Thereafter, meta information may be transmitted from the network drive server 200 by the network drive server 200 in step S120 . In step S121, the version of the file stored in the local cache folder 300 may be checked.

Thereafter, when the file version of the local cache folder 300 is lower than the version included in the meta information in step S122 , it corresponds to the deletion policy, and the file corresponding to the deletion policy may be deleted from the local cache folder 300 .

In step S130 , a file list using meta information may be generated by the agent 100 , and the file list generated in step S131 may be called back to the explorer 2 . Meta information may be stored in the local database 400 . Hereinafter, step S200 described in FIGS. 1 and 2 will be described in detail with reference to FIGS. 5 and 6 .

5 is a diagram for explaining an embodiment of executing and storing a file for the operation of a network drive management system using a local cache according to an embodiment of the present invention.

Referring to FIG. 5 , in the network drive management system using the local cache, an operation on a file stored in the network drive server 200 may be performed through the agent 100 .

A full read event for a file in the folder of the explorer 2 can be generated through the program 3 . Since the agent 100 has previously received meta information about the file, it can check whether the file exists in the local cache folder 300 using the meta information.

If the file does not exist in the local cache folder 300 , the agent 100 requests the download of data for the file to the network drive server 200 , and downloads the file from the network drive server 200 . can do.

A file existing in the local cache folder 300 is mapped to the corresponding program 3, and after the operation is finished, a file of the changed contents may be stored in the local cache folder 300. Thereafter, the agent 100 may The file may be uploaded to the network drive server 200 . In order to examine this embodiment in more detail, reference is made to FIG. 6 .

6 is a system flowchart for explaining the information processing process of the embodiment of FIG. 5 , FIG. 7 is a diagram for specifically explaining step S231 of FIG. 6 , and FIG. 8 is a local cache folder 300 that may be stored It is a diagram showing capacity.

In step S210 of FIG. 6 , a full read event for a file included in the file list is generated on the virtual drive, and in step S220 , it may be checked whether a file corresponding to the event exists in the local cache folder 300 . If it is confirmed that the file exists in the local cache folder 300 , the file may be mapped to the program 3 in step S241 .

If the file does not exist in the local cache folder 300, the download of all data for the file in which the full read event has occurred is requested to the network drive server 200 in step S220, and the network drive server 200 in step S230 ) to send the entire file read event. At this time, in step S231, the file may be deleted if the file in the local cache folder 300 corresponds to the deletion policy by comparing the free capacity of the local cache folder 300 with the capacity of the file. In order to examine this in detail, reference is made to FIG. 6 .

When it is determined that the file in the local cache folder 300 corresponds to the deletion policy by comparing the capacity of the local cache folder 300 with the capacity of the downloaded file in step S231, the file corresponding to the deletion policy for the capacity is deleted can be

In step S2311, it may be checked whether the size of the downloaded file is less than or equal to the free space capacity of the local cache folder 300 . As shown in Figure 8, the size of the used space and the empty space of the local cache folder is calculated, and the size of the empty space and the size of the downloaded file can be compared. When the downloaded file in step S2313 is larger than the free space capacity of the local cache folder 300 , the deleted file may be selected in consideration of the final access time of the local cache folder 300 and the file capacity. Thereafter, the file selected in step S2315 may be deleted. By performing this step, the local cache folder 300 has the advantage of always securing a storage space.

Thereafter, when the storage space of the local cache folder 300 is secured, the file is transmitted from the network drive server 200 , the file downloaded in step S240 may be stored in the local cache folder 300 , and the file stored in step S241 . can be mapped to the program (3).

After the end of the program 3 in step S250, the changed file may be stored in the local cache folder 300, may be uploaded to the network drive server 200, and the file uploaded in step S260 may be versioned and stored. have.

So far, a method for managing a network drive using a local cache that provides a file list in a virtual drive environment and selects a file to perform an operation has been described in detail with reference to FIGS. 1 to 8 .

Hereinafter, various embodiments that can be implemented in a method for managing a network drive using a local cache will be described with reference to FIGS. 9 to 14 .

9 is a diagram for explaining an embodiment in which a partial read event for a file is generated, and FIG. 10 is a system flowchart for explaining an information processing process according to the embodiment of FIG. 9 .

Some read events for a file are generated in the explorer 2 of FIG. 9 , and the agent 100 may request some read events to the network drive server 200 . The agent 100 may receive the requested information from the network drive server 200 . The agent 100 may call back the requested information to the explorer 2 . The present embodiment has the advantage of providing information at a high speed because only requested information is provided in real time without using the local cache folder 300 .

In step S300 of FIG. 10 , a partial read event for a file included in the file list may be generated on the virtual drive. For example, a partial read event for a file in this step may mean a case in which only partial request for file information of thumbnails and previews is received from the explorer 2 . In another embodiment, some read events for a file may mean a case in which a user opens a file requiring security with the program 3 . Depending on the permission to access the file included in the file list, it may be possible to read only the part corresponding to the permission of the file.

For example, an event that reads only the contents from position 1 to position 3000 in the file may be generated.

In step S310, a download of some data for a file in which a partial read event has occurred may be requested to the network drive server 200 . Afterwards, some data about the file may be received from the network drive server 200 in step S320 . In step S330 , some data may be answered by the searcher 2 .

As described above, in this embodiment, it may be possible to set whether to cache each file without having to work after downloading it to the local cache folder 300 for all files.

11 is a diagram for explaining an embodiment of executing and storing a file in a state in which the network connection with the network drive server 200 is released, and FIG. 12 is a system flowchart for explaining the information processing process of the embodiment of FIG. .

Referring to FIG. 11 , the agent 100 may release a network connection with the network drive server 200 . Because the network connection with the network drive server 200 is released, the agent 100 cannot request the file read event of the explorer 2 through the program 3 to the network drive server 200 . The agent 100 may receive meta information stored in the local database 400 , and when it is confirmed that the file exists in the local cache folder 300 according to the meta information, the agent 100 maps the file to the corresponding program 3 . can do it Thereafter, when the operation of the file in the program 3 is completed, the changed file may be stored in the local cache folder 300 . The embodiment will be described in more detail with reference to FIG. 12 .

In step S400 of FIG. 12 , meta information may be transmitted from the local database 400 to the agent 100 , and in step S410 , a file list may be generated using the meta information of the local database 400 . This file list is not synchronized with the network drive server 200 in real time, but since it is a list generated using meta information transmitted and received while connecting to the most recent network drive server 200, minimum reliability can be guaranteed. .

In step S420, a full read event for a file included in the file list may be generated on the virtual drive.

In step S430 , it may be checked whether a file corresponding to the event exists in the local cache folder 300 . In this case, if the file exists in the local cache folder 300 , the file may be mapped to the program 3 in step S440 . After the operation of the file is completed through the program 3 , the file may be stored in the local cache folder 300 .

Thereafter, when the network drive server 200 is connected again, the files stored in the network drive server 200 and the local cache folder 300 may be synchronized in step S460 .

If the file corresponding to the event does not exist in the local cache folder 300 in step S430, the file read event may be processed as failure.

The network drive management method using the local cache according to the present embodiment has the advantage of being able to access a file and perform an operation even when the connection with the network drive server 200 is disconnected.

13 is a system flowchart illustrating a process of synchronizing with the network drive server 200 after the network connection is reconnected in FIG. 12 .

In FIG. 13, the synchronization of step S460 of FIG. 12 may be performed, before that, in a state in which the first agent 100-1 is disconnected from the network drive server 200, in step S500, the first agent 100-1 ), after the file is changed, the file may be stored in the local cache folder 300 . In addition, as in step S510 in a state in which the first agent 100-1 is disconnected from the network drive server 200, the file may be modified by the second agent 100-2 and then stored in the server.

In this case, since the same file is modified by a different subject, a file conflict problem may occur.

In step S520, the history of file changes by the first agent 100 in the offline state may be transmitted to the network drive server 200, and in step S530, while the first agent 100 is offline, the network drive server ( The event list generated in 200 may be transmitted to the first agent 100 .

If it is determined in step S540 that the change history and the event list collide, the user may be requested to select a file for which changes to be applied, and the file may be determined by the user in step S550. Thereafter, the file determined by the user in step S560 may be stored in the network drive server 200 . In addition, the file determined by the user may be equally stored in the local cache folder 300 in step S570.

According to this embodiment, even if a change operation is made in a state in which the connection with the network drive server 200 is disconnected, and a file conflict problem occurs after reconnection occurs, the conflict problem is determined by comparison between the change history and the event list. can be resolved.

14 is a diagram for describing a data type included in meta information.

Meta information may store a file name, folder path, creation time, modification time, file size, type, author, caching status for each file, and the like. File #1(6) may have a file name aaa and a folder path \a\b. It can also include information about creation time, modification time, file size and type, and creator. In addition, each file may include a caching or not field, and this field may include information about which part of the file can be accessed. According to the meta information, file #1 can read data from 1 to 3000.

File #2(7) may have a file name bbb and a folder path \root. It can also include information about creation time, modification time, file size and type, and creator. According to the meta information, file #2 can read the entire data.

File #3(8) may have a file name ccc and a folder path \c\d\e. It can also include information about creation time, modification time, file size and type, and creator. According to the meta information, file #3 can read data from 500 to 600 times.

So far, a network drive management method using the local cache described in this specification has been described with reference to FIGS. 1 to 14 .

15 is an exemplary hardware configuration diagram illustrating the computing device 500 .

15 , the computing device 500 loads one or more processors 510 , a bus 550 , a communication interface 570 , and a computer program 591 executed by the processor 510 . It may include a memory 530 and a storage 590 for storing the computer program (591). However, only the components related to according to an embodiment of the present invention are shown in FIG. 15 . Accordingly, a person skilled in the art according to an embodiment of the present invention can know that other general-purpose components other than the components shown in FIG. 15 may be further included.

The processor 510 controls the overall operation of each component of the computing device 500 . The processor 510 is a CPU (Central Processing Unit), MPU (Micro Processor Unit), MCU (Micro Controller Unit), GPU (Graphic Processing Unit), or any form well known in the art according to an embodiment of the present invention. It may be configured to include at least one of the processors. In addition, the processor 510 may perform an operation on at least one application or program for executing the method/operation according to various embodiments described herein. Computing device 500 may include one or more processors.

The memory 530 stores various data, commands, and/or information. Memory 530 may load one or more programs 591 from storage 590 to execute methods/operations according to various embodiments described herein. An example of the memory 530 may be a RAM, but is not limited thereto.

The bus 550 provides a communication function between components of the computing device 500 . The bus 550 may be implemented as various types of buses, such as an address bus, a data bus, and a control bus.

The communication interface 570 supports wired/wireless Internet communication of the computing device 500 . The communication interface 570 may support various communication methods other than Internet communication. To this end, the communication interface 570 may be configured to include a communication module well-known in the art according to an embodiment of the present invention.

The storage 590 may non-temporarily store one or more computer programs 591 . The storage 590 is a non-volatile memory such as a read only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a hard disk, a removable disk, or according to an embodiment of the present invention. It may be configured to include any type of computer-readable recording medium well known in the art.

The computer program 591 may include one or more instructions in which methods/acts according to various embodiments described herein are implemented. When the computer program 591 is loaded into the memory 530 , the processor 510 may execute the one or more instructions to perform methods/operations according to various embodiments described herein.

In one embodiment, the computer program 591 requests meta information indicating information stored in a folder corresponding to the folder selection event to a network drive server according to a folder selection event of a virtual drive (instruction) , an instruction for receiving meta information on the folder from the network drive server, an instruction for generating a file list provided to the folder of the virtual drive using meta information on the folder, included in the file list on the virtual drive An instruction for generating a full read event for a file, an instruction for requesting download of all data for a file for which the full read event has occurred to the network drive server, and a file downloaded from the network drive server to the local cache folder After the instructions for storing the file and mapping the file to the program requesting the file, and the operation on the file are completed, the file of the changed contents is stored in the local cache folder, and the file of the changed contents is uploaded to the network drive It may contain instructions.

The methods according to the embodiments described so far may be performed by executing a computer program implemented as computer readable code. The computer program may be transmitted from the first computing device to the second computing device through a network such as the Internet and installed in the second computing device, thereby being used in the second computing device. The first computing device and the second computing device include all of a server device, a physical server belonging to a server pool for cloud services, and a stationary computing device such as a desktop PC.

The computer program may be stored in a recording medium such as a DVD-ROM or a flash memory device.

Although the embodiments have been described above with reference to the accompanying drawings, those of ordinary skill in the art to which an embodiment of the present invention pertains do not change the technical spirit or essential features of an embodiment of the present invention. It can be understood that it may be implemented in other specific forms without Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive.

Claims (18)

A method performed by a computing device, comprising:
requesting meta information indicating information stored in a folder corresponding to the folder selection event to a network drive server according to a folder selection event of a virtual drive;
receiving meta information about the folder from the network drive server;
generating a file list provided to the folder of the virtual drive by using meta information about the folder;
generating a full read event for a file included in the file list on the virtual drive;
requesting the download of all data for the file in which the full read event has occurred to the network drive server;
storing the file downloaded from the network drive server in a local cache folder, and mapping the file to a program requesting the file; and
After the work on the file is completed, storing a file of the changed content in the local cache folder, and uploading the file of the changed content to the network drive,
How to manage network drives using local cache. According to claim 1,
The step of generating a list of files provided in the folder of the virtual drive by using meta information about the folder includes:
Storing the meta information in a local database for managing the meta information received from the network drive server separately from the network drive server,
How to manage network drives using local cache. According to claim 1,
The step of requesting the download of the entire file in which the entire read event has occurred to the network drive server,
checking whether a file corresponding to the entire read event exists in the local cache folder; and
Comprising the step of requesting to download the entire file to the network drive server when the file corresponding to the all read event does not exist in the local cache folder,
How to manage network drives using local cache. According to claim 1,
When the file included in the local cache folder corresponds to the deletion policy, the method further comprising the step of deleting the file corresponding to the deletion policy from the cache folder,
How to manage network drives using local cache. 5. The method of claim 4,
The step of deleting the file corresponding to the deletion policy from the cache folder,
When the folder selection event of the virtual drive occurs, if it is determined that the file storage period of the local cache folder violates the deletion policy using meta information, deleting a file corresponding to the deletion policy for the storage period; containing,
How to manage network drives using local cache. 5. The method of claim 4,
The step of deleting the file corresponding to the deletion policy from the cache folder,
After receiving the meta information from the network drive server, if it is determined that the file version of the local cache folder violates the deletion policy using the meta information, deleting the file corresponding to the deletion policy for the version; containing,
How to manage network drives using local cache. 5. The method of claim 4,
The step of deleting the file corresponding to the deletion policy from the cache folder,
After the step of requesting the download of all files in which the read all event has occurred, the capacity of the local cache folder is compared with the capacity of the downloaded file, and when it is determined that the file in the local cache folder corresponds to the deletion policy, the capacity Deleting files that fall under the deletion policy for
How to manage network drives using local cache. 8. The method of claim 7,
The step of deleting the file corresponding to the deletion policy for the capacity,
checking whether the size of the downloaded file is less than or equal to the free space capacity of the local cache folder;
selecting a file to be deleted in consideration of the final access time of the local cache folder and the capacity of the file when the downloaded file is larger than the free space capacity of the local cache folder; and
Including the step of deleting the selected file,
How to manage network drives using local cache. According to claim 1,
generating a partial read event for a file included in the file list on the virtual drive;
requesting the network drive server to download some data for the file in which the partial read event has occurred;
receiving some data for the file from the network drive server;
Further comprising the step of responding to the explorer some data about the file,
How to manage network drives using local cache. 10. The method of claim 9,
The step of generating some read events for files included in the file list on the virtual drive,
Including the step of generating a thumbnail or preview event for the file list on the virtual drive,
How to manage network drives using local cache. 10. The method of claim 9,
The step of generating some read events for files included in the file list on the virtual drive,
Including the step of generating an event of reading a part corresponding to the permission of the file according to the permission to access the file included in the file list,
How to manage network drives using local cache. According to claim 1,
releasing the network connection with the network drive server;
receiving meta information from a local database;
generating a file list using meta information received from the local database;
generating a full read event for a file included in the file list on the virtual drive;
checking whether a file corresponding to the event exists in a local cache folder;
when the file corresponding to the event exists in a local cache folder, mapping the file to a program requesting the file;
Comprising the step of storing a file of the changed contents in the local cache folder after the work on the file is completed,
How to manage network drives using local cache. 13. The method of claim 12,
connecting a network connection to the network drive server; and
Further comprising the step of synchronizing the file of the changed contents after the operation stored in the local cache folder is completed with the file stored in the network drive server,
How to manage network drives using local cache. 14. The method of claim 13,
The step of synchronizing with the file stored in the network drive server is,
Transmitting a history of changes to a file stored in the local cache folder that is changed in a state in which the network connection with the network drive server is released to the network drive server,
How to manage network drives using local cache. 15. The method of claim 14,
The step of synchronizing with the file stored in the network drive server is,
Transmitting an event list for files stored in the network drive server changed in a state in which the network connection with the network drive server is released to the network drive server,
How to manage network drives using local cache. 16. The method of claim 15,
In a state in which the network connection with the network drive server is disconnected, a file changed by another user is uploaded to the network drive server, and the change of the file through comparison of the change history and the event list from the network drive server being notified if there has been a collision;
determining a selection for the conflicting file according to the notification; and
receiving the file synchronized according to the result of the determination, and storing the synchronized file in the local cache folder;
How to manage network drives using local cache. According to claim 1,
The meta information is
including at least one of a name of the file, a creation time of the file, a modification time of the file, a path where the file is located, or a range for accessing data of the file,
How to manage network drives using local cache. processor;
network interface;
a memory executed by the processor to load a computer program; and
A storage for storing the computer program,
The computer program is
an instruction for requesting meta information indicating information stored in a folder corresponding to the folder selection event to a network drive server according to a folder selection event of a virtual drive;
instructions for receiving meta information about the folder from the network drive server;
an instruction for generating a file list provided to the folder of the virtual drive by using meta information about the folder;
an instruction for generating an entire read event for a file included in the file list on the virtual drive;
an instruction for requesting download of all data for the file in which the full read event has occurred to the network drive server;
an instruction for storing a file downloaded from the network drive server in a local cache folder and mapping the file to a program requesting the file; and
After the work on the file is completed, a file of the changed content is stored in the local cache folder, and the file of the changed content is uploaded to the network drive.
A data management device that mixes virtual drive and namespace approaches.

Images