JP7417044B2 - Information processing device, information processing system, information processing method and program - Google Patents

Description

The present invention relates to a file management system using cloud storage and a NAS server.

A feature of cloud computing in recent years is that users can use the services and computer resources they want, whenever they want, without installing expensive software or servers, as long as they have an Internet environment.

In particular, cloud storage is an online storage service provided using the cloud, and the storage capacity can be changed flexibly, making it possible to increase or decrease the capacity as needed.

Patent Document 1 discloses that without installing a NAS (Network Attached Storage) server within a company, work efficiency equivalent to that of installing a NAS server within the company can be achieved on online storage in the public domain. The technology has been disclosed.

JP2013-37626A

However, in Patent Document 1, files are managed using online storage without installing a NAS (Network Attached Storage) server within the company, but there is an upper limit to the network bandwidth between the online storage and the company. Therefore, there is a limit to the communication speed, and it may be difficult to obtain a file access response similar to that of a NAS server in a company.

An object of the present invention is to provide a mechanism that improves the response of file access to a NAS server when cloud storage and a NAS server are used together.

The present invention provides an information processing device that is connectable to a file storage device and a client terminal and has storage means for storing a part of files stored in the file storage device,
transmitting means for transmitting information on files stored in the file storage device to a first client terminal;
If a file related to information transmitted by the transmitting means and for which an acquisition request has been received from the first client terminal is stored in the storage means, the file is acquired from the storage means, and the file is stored in the storage means. a file transmitting means for acquiring the file from the file storage device and transmitting it to the first client terminal if the file for which the acquisition request has been received from the first client terminal is not stored in the storage means;
When the file in the file storage device is updated from the second client terminal without going through the storage means, an acquisition means for acquiring the updated file;
The storage means stores the file acquired by the acquisition means.
It is characterized by

The present invention uses cloud storage and a NAS server in combination to provide both the good file access response of the NAS server and the flexibility of the storage capacity of the cloud storage, and also allows users to choose whether to access the cloud storage or the NAS server. This has the effect of providing a file system that can be used without distinction.

1 is a block diagram showing a system configuration of an information processing system according to an embodiment of the present invention. 1 is a block diagram showing a hardware configuration of an information processing apparatus applicable to a NAS server 100, a client terminal 101, and a cloud storage 102 according to an embodiment of the present invention. 2 is a first flowchart illustrating an example of a file registration processing procedure according to an embodiment of the present invention. It is a 2nd flow chart explaining an example of a file reference processing procedure concerning an embodiment of the present invention. It is a 3rd flowchart explaining an example of the file synchronization processing procedure based on embodiment of this invention. FIG. 2 is a schematic diagram showing an example of a file structure, a user structure, and a database configuring each of them according to an embodiment of the present invention.

Embodiments of the present invention will be described in detail below with reference to the drawings. First, the system configuration of the present invention will be explained with reference to FIG.

FIG. 1 is a block diagram showing the system configuration of an information processing system according to an embodiment of the present invention.

The cloud storage (file storage device) 102 in FIG. 1 stores files managed by users, and its storage capacity can be changed flexibly.

The NAS server 100 preferentially stores some of the files in the cloud storage 102, particularly files with the latest access date and time. As a result, the client terminals 101a to 101c in the intranet 104 can preferentially acquire and manage recently used files from the NAS server 100, and can transfer files from the cloud storage 102 without going through the Internet 103. Access (file sending and receiving) is possible.

In addition, the NAS server 100 also has a folder/file information table (file attributes) 600 that stores the file configuration of the cloud storage 102, and further includes files stored in the NAS server 100 in the cloud storage 102. A list of files is held as a cache table (file attributes) 610 (file attribute storage unit).

The client terminals 101a to 101c are information processing devices located within the intranet 104 of the same company as the NAS server 100, and accept processes such as file reference, registration, update, and deletion from users (access requests). If the file exists on the NAS server 100, the file is acquired from the SSD of the NAS server 100, and if the file does not exist on the NAS server 100, the file is received from the cloud storage 102 via the NAS server 100 ( File transfer). The client terminal 101d also receives processes such as file reference, registration, update, and deletion from the user by accessing the cloud storage 102 via the Internet 103.

Note that in this embodiment, the storage medium of the NAS server 100 is sometimes described as an SSD (Solid State Drive), but it does not necessarily have to be an SSD, and may be an HDD (Hard Disk Drive). Other storage media may also be used.

The NAS server 100 may be composed of a plurality of cases, or may be the same as the client terminal 101. For example, the storage medium that stores the actual files 105 of the NAS server 100 is configured separately into a housing that includes an SSD (Solid State Drive) and a database housing that includes the folder/file information table 600 and cache table 610. Good too.

Next, with reference to FIG. 2, the hardware configuration of the information processing apparatus used in the present invention will be described.

FIG. 2 is a block diagram showing the hardware configuration of an information processing apparatus applicable to the NAS server 100, client terminal 101, and cloud storage 102 according to the embodiment of the present invention.

In FIG. 2, 201 is a CPU that centrally controls each device and controller connected to the system bus 204. In addition, the ROM 203 or external memory 211 contains BIOS (Basic Input/Output System), which is a control program for the CPU 201, an operating system program (hereinafter referred to as OS), and other programs (described later) that are necessary to realize the function of executing image management. Various programs etc. are stored.

202 is a RAM, which functions as the main memory, work area, etc. of the CPU 201; The CPU 201 loads programs and the like necessary for execution of processing from the ROM 203 or the external memory 211 into the RAM 202, and executes the loaded programs to realize various operations.

Further, an input controller 205 controls input from an input device 209 such as a keyboard or a pointing device. A video controller 206 controls display on a display device such as the display device 210. These are used by the operator as necessary.

207 is a memory controller that is connected via an adapter to a hard disk (HD), flexible disk (FD), or PCMCIA card slot that stores boot programs, various applications, font data, user files, editing files, various data, etc. Controls access to external memory 211 such as CompactFlash (registered trademark) memory.

Furthermore, the hard disk (HD) of the external memory 211 has a large-capacity memory area for storing recorded moving images with audio and audio files in the information processing apparatus.

A communication I/F (interface) controller 208 connects and communicates with external devices via a network (for example, a wireless LAN), and executes communication control processing in the network. For example, communication using TCP/IP is possible.

Note that the CPU 201 enables display on the display device 210 by, for example, executing an outline font development (rasterization) process in a display information area in the RAM 202. Further, the CPU 201 allows the user to give instructions using a mouse cursor (not shown) on the display device 210.

The processing of each step shown in the flowchart described below for realizing the present invention is executed by a program readable and executable by a computer, and the program is recorded in the external memory 211. The program is then loaded into the RAM 202 and executed by the CPU 201 as needed. Further, definition files, various information tables, and the like used when executing the above program are also stored in the external memory 211, and detailed explanations thereof will be given later.

Next, the file management process of the present invention will be explained with reference to the flowcharts of FIGS. 3 to 5.

FIG. 3 is a first flowchart illustrating an example of the file registration processing procedure according to the embodiment of the present invention, and each step of S301 to S308 is each process executed by the CPU 201 on the NAS server 100.

The flowchart in FIG. 3 is, for example, the flow of processing performed by the NAS server 100 when receiving a process for registering a file in the NAS server 100 and the cloud storage 102 from the client terminal 101 used by the user.

In the flowchart of FIG. 3, the process starts when the NAS server 100 receives a file from the client terminal 101 (step S301).

Next, in step S302, the NAS server 100 that has received the file stores the file in the SSD of the NAS server 100.

When registering files in step S302, the NAS server 100 determines whether the total capacity of files stored in the SSD exceeds a predetermined capacity (for example, the total capacity of the SSD) (step S303). If the predetermined capacity is exceeded, the process transitions to step S304, and if the predetermined capacity is not exceeded, the process transitions to step S306.

When the process transitions to step S304, the NAS server 100 cannot store files exceeding a predetermined capacity (for example, the total capacity of the SSD), so in step S302, the NAS server 100 deletes the files in the SSD that would exceed the capacity if stored. The criteria for selecting files to be deleted may be to select the capacity that exceeds the file size starting from the file with the oldest last access date and time (611 in FIG. (above)) You may select a file whose capacity is larger than that of the previous file. The criteria for selecting files to be deleted may be determined using other methods. For example, files older than a predetermined period (for example, three months or more) may be forcibly deleted. Note that although the file selected here is deleted from the NAS server 100, the same file still exists in the cloud storage 102. Next, the process advances to step S305.

In step S305, the NAS server 100 deletes the record in the cache table 610 of the file deleted in step S304, and the process transitions to step S306.

When the process transitions to step S306, the NAS server 100 adds the record of the file stored in step S302 to the cache table 610.

Next, in step S307, the NAS server 100 adds the folder/file information table 600 or updates the last update date.

Next, in step S308, the NAS server 100 uploads the file stored in step S302 to the cloud storage 102 (storage instruction to the file storage device), and the NAS server 100 and the cloud storage 102 synchronize. Note that the processes after step S302 are performed by the NAS server 100, and the client terminal 101 only sends the file to the NAS server 100 in the intranet in step S301. I almost never feel bad about it.

Next, an example of a file reference processing procedure according to an embodiment of the present invention will be described with reference to FIG. 4.

FIG. 4 is a second flowchart illustrating an example of the file reference processing procedure according to the embodiment of the present invention, and each step of S401 to S412 is each process executed by the CPU 201 on the NAS server 100.

The flowchart in FIG. 4 is a flowchart of processing that is started when a file reference request is received from the client terminal 101.

First, in step S401, the NAS server 100 acquires the folder/file information table 600 possessed by the NAS server 100, and in the next step S402, transmits information that causes the client terminal 101 to display the folder/file structure (file structure display control section). The folder/file structure displayed on the client terminal 101 as a result of transmitting information will be specifically explained with reference to FIG. 6.

620 in FIG. 6 is an image of a specific display screen displayed on the display 210 of the client terminal 101. In order to generate a folder structure such as 620, the NAS server 100 obtains information 601 for displaying the folder/file structure of the folder/file information table 600 (file structure storage unit), and generates an image such as 620. is generated and sent to the client terminal 101. Specifically, a tree structure is generated by linking the folder/file ID in the information 601 for displaying the folder/file structure and the parent folder ID of the record. Note that if the client terminal 101 can generate an image such as 620, the information 601 for displaying the folder/file structure may be sent to the client terminal 101. Returning to the explanation of the flowchart in FIG. 4.

After transmitting the folder/file structure display information to the client terminal 101 in step S402 of FIG. 4, the NAS server 100 receives selection of a file to be referenced from the client terminal 101 in the next step S403. Specifically, for example, when a folder/file structure like the 620 screen image in FIG. ) and file 623 (June 1_business daily report.xls) are selected by double-clicking with a mouse (not shown) or the like.

In the next step S404, the NAS server 100 obtains the cache table 610 that the NAS server 100 has in order to determine whether the file selected in step S403 is on the SSD of the NAS server 100. From the acquired cache table 610, it is determined whether there is a record corresponding to the file selected in step S403 (step S405), and the processing is divided. In step S405, if there is a record corresponding to the file selected in step S403 in the cache table 610, the process transitions to step S406, and if there is no record corresponding to the file selected in step S403 in the cache table 610, , the process transitions to step S408.

If the process moves to step S406, this means that the cache table 610 has a record corresponding to the file selected in step S403, so the selected file exists in the NAS server 100. Therefore, in step S406, the NAS server 100 acquires the file selected in step S403 that exists in the SSD. An example of a file in the 620 screen is a case where file 622 (July 2_business daily report.xls) is selected. The file ID of the selected file 622 is 452 according to the folder/file information table 600, and a record with the file ID 452 exists in the cache table 610 (line 612). Since it exists in the cache table 610, the file 622 (July 2_business daily report.xls) stored in the SSD of the NAS server 100 is acquired from the SSD.

Next, in step S407, processing is performed to update the last access date and time of the file obtained in step S406 in the cache table 610. Through this process, the last access date and time of files that are frequently accessed are frequently updated, so the possibility of them being deleted from the SSD is reduced, and the process of retrieving the files to the cloud storage 102 can be omitted. . Next, the process transitions to step S411.

On the other hand, if it is determined in step S405 that there is no record corresponding to the file selected in step S403 in the cache table 610, the process transitions to step S408, and the NAS server 100 transfers the record from the cloud storage 102 to step S403. Get the selected file. An example of a file in the 620 screen is a case where file 623 (June 1_business daily report.xls) is selected. The file ID of the selected file 623 is 401 according to the folder/file information table 600, and no record with the file ID 401 exists in the cache table 610. Since it does not exist in the cache table 610, it is not stored in the SSD of the NAS server 100, and the file 623 (June 1_business daily report.xls) is acquired from the cloud storage 102.

As described above, files that exist on the SSD of the NAS server 100 and files that do not exist on the NAS server 100 but only on the cloud storage 102 can be displayed without distinction as in 622 and 623, and the user can see the location of the file. It has the effect that it can be accessed without worrying about. Note that files that exist on the SSD of the NAS server 100 and files that do not exist may be displayed so that they can be identified, and in that case, files that exist on the SSD of the NAS server 100 (for example, 622) and cloud storage may be displayed in one folder. The file existing in 102 (for example, 623) can be displayed as if it were in the same folder.

Next, in step S409, the NAS server 100 stores the file acquired in step S408 in the SSD of the NAS server 100.

Next, in step S410, the NAS server 100 adds a new record to the cache table 610 to register that the file acquired in step S408 has been stored in the SSD. For files that have been accessed once, the last access date and time are updated, registered in the cache table 610, and stored in the SSD, thereby improving the response the next time the file is accessed. Next, the process transitions to step S411.

When the process transitions to step S411, the NAS server 100 updates the last access date and time in the folder/file information table 600 held by the NAS server 100 and the cloud storage 102.

Next, in step S412, the NAS server 100 transmits to the client terminal 101 the file itself for which selection was accepted from the client terminal 101 in step S403.

With the above processing, when accessing a file stored in the SSD of the NAS server 100, the file can be sent to the client with good response. Furthermore, even if the stored files are deleted from the NAS server 100 when their capacity is too large to be stored on the SSD, the files are still synchronized and saved in the cloud storage 102 as in step S308. . On the file management screen, as shown in 620 in FIG. 6, the user can access the file regardless of whether it is on the NAS server 100 or the cloud storage 102, so the user can access it in the same way regardless of whether it is on the NAS server 100 or the cloud storage 102. It has the effect of being able to retrieve files.

Next, an example of a file synchronization process procedure between the NAS server 100 and the cloud storage 102 according to the embodiment of the present invention will be described with reference to FIG. 5.

FIG. 5 is a third flowchart illustrating an example of the file synchronization process procedure according to the embodiment of the present invention, and each step of S501 to S506 is a process executed by the CPU 201 on the NAS server 100.

The flowchart in FIG. 5 may be a process that is executed periodically on the NAS server 100 (for example, every 3 hours or every other day), or may be executed at the timing when files in the cloud storage 102 are updated. The flowchart of FIG. 5 may be started when the NAS server 100 is notified of the updated file.

First, in step S501, the NAS server 100 acquires the folder/file information table 600 that the cloud storage 102 has.

The processes in the next steps S502 and S503 are for detecting that files have been updated by accessing the cloud storage 102 via the Internet without going through the company intranet. If the file is updated, the latest file will not be reflected on the NAS server 100, so this is a decision branch to execute the processing from step S504 onwards. Note that when accessing a file from the client terminal 101d to the cloud storage 102 via the Internet 103, a screen image such as 620 in FIG. 6 may be displayed on the display 210 of the client terminal 101d to allow access.

In step S502, the NAS server 100 determines the last update date of the cloud storage and the last Compare the update date for each file. If the last update date of the cloud storage is newer, the process moves to step S503, and if the last update date of the cloud storage is older, the process of the flowchart in FIG. 5 is finished.

When the process transitions to step S503, the NAS server 100 determines whether the last updater ID of the folder/file information table 600 acquired from the cloud storage 102 is the NAS user. If the last updater ID is a NAS user (No in step S503), the process of the flowchart in FIG. 5 is finished, and if it is not a NAS user (Yes in step S503), the process transitions to step S504. Whether the last updater ID is a NAS user may be determined as a NAS user if the user is registered in 630 in FIG. 6 (for example, "911", "912", "961", etc.), or For example, if a logged-in user logs in to ``kanon. ichiro@aaa. co. jp'', it can be determined that the user is a user other than the NAS user, for example, via the cloud. “kanon. ichiro@aaa. co. jp'' user is the login ID of ``Kannon Ichiro'' 631 in the user group table 630 via the cloud. Note that the method for identifying whether it is a NAS user or another user may be other than the above, such as setting a flag in the folder/file information table 600 when the access is via the cloud, or setting a flag when the access is via the NAS. You can also identify it by standing up.

The decision branch in step S503 is a branch to prevent a phenomenon in which something updated in the NAS server 100 and synchronized with the cloud storage 102 is resynchronized from the cloud storage 102 to the NAS server 100.

For example, when a new file is uploaded to the NAS server 100, the update date of the NAS server 100 becomes the upload date and time (step S302). Thereafter, synchronization processing is performed by the NAS user from the NAS server 100 to the cloud storage 102 (step S308). Since the data is synchronized to the cloud storage 102 a little later than the upload to the NAS server 100, the last update date of the cloud is greater than the last update date of the NAS, and the last updater ID is the NAS user. However, since this file is the latest file that has been synchronized with both the NAS server 100 and the cloud storage 102, it is determined that there is no need to synchronize it from the cloud, and the processes from step S504 onwards are skipped.

When the process transitions to step S504, the NAS server 100 copies the entity of the corresponding file in the cloud storage 102 to the NAS server 100.

Next, in step S505, the NAS server 100 reflects the contents of the record of the corresponding file in the folder/file information table 600 obtained in step S501 to the corresponding record in the folder/file information table 600 of the NAS server 100.

Next, in step S506, the NAS server 100 adds the record column of the corresponding file to the cache table 610 that the NAS server 100 has.

As described above, by the processing of steps S504 to S506, even if there is a user who directly accesses the cloud storage 102 without going through the NAS server 100 and updates or adds files, the files can be synchronized with the NAS server 100.

By using the above process, cloud storage and NAS server are used together, and the file access response of NAS server is good and the storage capacity of cloud storage is flexible, and the user can access either cloud storage or NAS server. It can be used without any distinction.

In the above embodiment, the case where the application is applied to a plurality of information processing apparatuses has been described, but it may be applied to a single information processing apparatus, or even if a common processing entity such as a plurality of servers on a network is used. good.

Although not particularly shown, information that manages the program group stored on the recording medium, such as version information and creator, is also stored, and information that depends on the OS on the program reading side, such as identifying the program, is also stored. Icons to be displayed may also be stored.

Furthermore, data dependent on various programs is also managed in the directories. Furthermore, if the program or data to be installed is compressed, the program to be decompressed may also be stored.

The functions shown in FIGS. 3 to 5 according to this embodiment may be performed by the host computer by a program installed from the outside. In that case, the present invention is applicable even when the information group including the program is supplied to the output device from a recording medium such as a CD-ROM, flash memory, or FD, or from an external recording medium via a network. It is something.

As described above, a recording medium recording a software program code that implements the functions of the embodiments described above is supplied to a system or device, and the computer (or CPU or MPU) of the system or device records the program code. It goes without saying that the object of the present invention can also be achieved by reading and executing program codes stored on a medium.

In this case, the program code read from the recording medium itself realizes the novel function of the present invention, and the recording medium that stores the program code constitutes the present invention.

Examples of recording media for supplying program codes include flexible disks, hard disks, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, DVD-ROMs, magnetic tapes, and non-volatile memory cards. , ROM, EEPROM, silicon disk, etc. can be used.

Furthermore, by executing the program code read by the computer, not only the functions of the embodiments described above are realized, but also the functions of the program code are executed on the computer based on the instructions of the program code. It goes without saying that this also includes a case where an OS (operating system) or the like performs some or all of the actual processing, and the functions of the embodiments described above are realized by that processing.

Furthermore, after the program code read from the recording medium is written to the memory of the function expansion board inserted into the computer or the function expansion unit connected to the computer, the program code is This also includes the case where the CPU, etc. of the function expansion board or function expansion unit performs part or all of the actual processing based on instructions from the function expansion board, and the functions of the above-described embodiments are realized by the processing. Needless to say.

Furthermore, the present invention may be applied to a system made up of a plurality of devices, or to a device made up of one device. It goes without saying that the present invention can also be applied to cases where the present invention is achieved by supplying a program to a system or device. In this case, by reading into the system or device a recording medium storing a program represented by software for achieving the present invention, the system or device can enjoy the effects of the present invention.

Furthermore, by downloading and reading a program represented by software for achieving the present invention from a server, database, etc. on a network using a communication program, the system or device can enjoy the effects of the present invention. becomes possible.

Note that all configurations that are combinations of the above-described embodiments and their modifications are also included in the present invention.

100 NAS server 101 Client terminal 102 Cloud server 103 Internet 104 Intranet 201 CPU
202 RAM
203 ROM
204 System bus 205 Input controller 206 Video controller 207 Memory controller 208 Communication I/F controller 209 Input device 210 Display device 211 External memory 600 Folder/file information table 610 Cache table

Claims (14)

An information processing device connectable to a file storage device and a client terminal, the information processing device having storage means for storing a part of files stored in the file storage device,
transmitting means for transmitting information on files stored in the file storage device to a first client terminal;
If a file related to information transmitted by the transmitting means and for which an acquisition request has been received from the first client terminal is stored in the storage means, the file is acquired from the storage means, and the file is stored in the storage means. a file transmitting means for acquiring the file from the file storage device and transmitting it to the first client terminal if the file for which the acquisition request has been received from the first client terminal is not stored in the storage means;
When the file in the file storage device is updated from the second client terminal without going through the storage means, an acquisition means for acquiring the updated file;
The storage means stores the file acquired by the acquisition means.
An information processing device characterized by: The acquisition means determines whether the file in the file storage device has been updated from the second client terminal without going through the storage device, when the last update date of the file in the file storage device is stored in the storage device. The file must be newer than the last update date of the file corresponding to the file in the file.
The information processing device according to claim 1, characterized in that: The information on the file includes a first attribute that is an attribute of the file stored in the file storage device, and a second attribute that is an attribute of the file stored in the storage means. The information processing device according to claim 1 or 2 . reflecting means for reflecting information of the file received by the acquiring means for the first attribute on the second attribute;
The information processing device according to claim 3 , characterized in that it has : storage means for storing the file stored in the storage means also in the file storage device;
Deletion means for deleting files that satisfy a predetermined condition from among the files stored in the storage means;
5. The information processing device according to claim 3 , characterized in that the information processing device has: The information processing apparatus according to claim 5, wherein the deletion means deletes a file that satisfies the predetermined condition and also deletes a record of the second attribute regarding the file. The file that satisfies the predetermined condition is identified from the date and time of access to the file stored in the storage means when it is determined that the file for which the registration instruction has been accepted would exceed the upper limit of storage capacity if registered. The information processing device according to claim 5 or 6, wherein the information processing device is a file. The determination as to whether the file for which the acquisition request has been received from the first client terminal is stored in the storage means is determined based on the relationship between the first attribute of the file and the second attribute of the file. The information processing apparatus according to any one of claims 3 to 7. A determination as to whether a file for which an acquisition request has been received from the first client terminal is stored in the storage means is determined based on whether a record corresponding to the first attribute of the file exists in the second attribute. The information processing device according to any one of claims 3 to 8. The information according to any one of claims 3 to 9, further comprising: a registration means for registering file attributes regarding the file registered in the storage means as the first attribute and the second attribute. Processing equipment. Any one of claims 3 to 10 , wherein the first attribute includes information for displaying files stored in the storage means and files not stored in the storage means in a distinguishable manner. The information processing device according to item 1. The information processing apparatus according to any one of claims 1 to 11, wherein the external storage unit constituting the storage means is an SSD. An information processing method for an information processing device, the information processing device having a storage means that is connectable to a file storage device and a client terminal and stores a part of files stored in the file storage device,
a sending step of sending information about files stored in the file storage device to the client terminal;
If a file related to the information transmitted in the sending step and for which an acquisition request has been received from the client terminal is stored in the storage means, the file is acquired from the storage means and the file is sent from the client terminal. If the file for which the acquisition request has been received is not stored in the storage means, a file transmission step of acquiring the file from the file storage device and transmitting it to the client terminal;
If the file in the file storage device is updated from the second client terminal without going through the storage means, an obtaining step of obtaining the updated file;
a registration step of registering the file acquired in the acquisition step in the storage means;
An information processing method characterized by causing an information processing device to execute. A program for causing at least one computer to function as each means of the information processing apparatus according to claim 1.

Images