JP2013077079A - Storage system, storage server, user data sharing method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To combine a plurality of storage techniques and seamlessly integrate them, on the basis of a concept to cache user data in a server, in a storage system.SOLUTION: A storage system comprises a user terminal (10) and a storage server (20). The user terminal (10) caches user data in the storage server (20), collects meta data about the user data and transmits the data to the storage server (20). The storage server (20) stores cache of the user data and the meta data, presents information which is based on the meta data to an authenticated terminal, and transmits the cache to the authenticated terminal when an acquisition request of the cache is performed by the authenticated terminal. By this way, an external terminal (30) can use the user data on the user terminal (10) through the storage server (20).

Description

  The present invention relates to a storage system, a storage server, a user data sharing method, and a program, and more particularly to a storage system, a storage server, a user data sharing method, and a program that use network storage in cloud computing.

  In cloud computing, any one or a combination of an unspecified number of servers in a “cloud”, which is a network whose configuration node is unknown to the user, provides a service to the user. Yes.

  Conventionally, in an online storage type service, a dedicated storage area is provided in advance in a server constituting the cloud, and the user is charged according to the size (capacity) of the reserved storage area. A user selects a file (various data) and a folder (directory) to be stored in a server constituting the cloud in advance, and sets them in application software (hereinafter, application). The application automatically uploads the selected file to the reserved storage area according to the settings. Online storage type services are often used for purposes such as mirroring.

  In the cloud storage synchronization type service, files are synchronized between a terminal and a server constituting the cloud via a dedicated application compatible with a terminal such as a PC (personal computer) or a smartphone. Thereby, each terminal will be in the state which shares the file via the server which comprises a cloud. When a certain terminal updates a synchronized file, the updated contents are also reflected in the synchronized file on the other terminal side via a server constituting the cloud. That is, the file on the cloud is used as a master file, and the content updated on a certain terminal is reflected on the master file on the cloud, thereby reflecting the updated content on the file on the other terminal side.

  In the home storage type service, a storage device having a network function is sold to an end user. As an example of a storage device having a network function, NAS (Network Attached Storage) can be considered. The NAS's own network file sharing function allows each end user to share the large-capacity storage of NAS installed at home via the Internet.

  However, the online storage type service is too simple and can only be used for file backup, and is inferior in function to other storage services.

  Further, in the online storage type service and the cloud storage synchronization type service, basically, it is necessary to secure all received files on the cloud side, so that the provider providing the service has a storage cost. For this reason, charging according to the capacity used by the user is required, and the burden on the user increases. Furthermore, it is not possible to provide a very large capacity network storage to the user.

  Also, in the home storage type service, the storage in the user home cannot be used when it is offline. When a large number of people access from multiple points, the line speed of the target user's house becomes a bottleneck, and scalability (scalability) is low. Since security measures depend on the response status of individual users, they may be vulnerable to DoS attacks from the network.

  As a related technique, Patent Document 1 (Japanese Patent Laid-Open No. 2010-198540) discloses a virtual folder creation apparatus. In this related technology, a management device is placed between the client and the file server. On the GUI screen, the client accepts input of a virtual folder placement location, virtual folder name, and metadata, and searches the file server for a file to which metadata corresponding to the input metadata is assigned. A file list of the search results is created, and virtual folder identification information is added to the location, virtual folder name, and metadata, and stored in the virtual folder setting database in the management apparatus. The file list is stored in the virtual folder cache database in the management apparatus as a file list corresponding to the virtual folder identification information.

  However, in the above technology, when a file is exchanged between a home user terminal and a user terminal outside the home, the file cannot be transmitted / received due to a failure (speed reduction, disconnection, etc.) of any network connection environment. is there.

JP 2010-198540 A

  An object of the present invention is to provide a storage system in which a plurality of storage technologies are combined and seamlessly integrated based on the concept of caching user data in a storage server.

  A user terminal according to the present invention and a storage server connectable to the user terminal via a network are included. The user terminal transmits metadata regarding user data to be a master file to the storage server. The storage server stores metadata and a cache of user data. In addition, information based on the metadata is presented to the authenticated terminal. When there is a user data acquisition request from an authenticated terminal, it is checked whether a cache of user data is stored. If the user data cache is stored, the user data cache is transmitted to the authenticated terminal. If the user data cache is not stored, the user data is acquired from the user terminal. Also, the user data is transmitted to the authenticated terminal.

  The storage server according to the present invention stores means for connecting to a user terminal via a network, means for receiving metadata relating to user data serving as a master file from the user terminal, and metadata and a cache of user data. Means for presenting information based on metadata to an authenticated terminal, and means for confirming whether or not a cache of user data is stored when there is a user data acquisition request from the authenticated terminal; Means for transmitting user data cache to an authenticated terminal if user data cache is stored; means for obtaining user data from user terminal if user data cache is not stored; and user data Is transmitted to the authenticated terminal.

  A user data sharing method according to the present invention is a user data sharing method implemented by a computer, which connects to a user terminal via a network and receives metadata relating to user data as a master file from the user terminal. Storing metadata and user data cache, presenting information based on metadata to an authenticated terminal, and requesting acquisition of user data from an authenticated terminal Check if user data cache is stored; if user data cache is stored, send user data cache to authenticated terminal; do not store user data cache The user data is obtained from the user terminal and the user data is authenticated. And transmitting to.

  The program according to the present invention includes a step of connecting to a user terminal via a network, a step of receiving metadata relating to user data serving as a master file from the user terminal, and a step of storing metadata and a cache of user data. A step of presenting information based on the metadata to the authenticated terminal, a step of checking whether or not a cache of user data is stored when there is a user data acquisition request from the authenticated terminal, and a user If the data cache is stored, the user data cache is transmitted to the authenticated terminal; if the user data cache is not stored, the user data is acquired from the user terminal; The step of sending to the authenticated terminal is executed on the computer. Is a program of the order to. The program according to the present invention can be stored in a storage device or a storage medium.

  Compared to conventional services, it can provide low cost, large capacity, high reliability, and high added value network storage to end users.

It is a figure which shows the structural example of the storage system which concerns on this invention. It is a figure for demonstrating the flow of the metadata (index information) registration process concerning this invention. It is a figure for demonstrating the flow of the metadata (index information) acquisition process which concerns on this invention. It is a figure for demonstrating the flow of the server access process which concerns on this invention. It is a figure for demonstrating the flow of the user data acquisition process which concerns on this invention. It is a figure for demonstrating the flow of the user data external edit process which concerns on this invention. It is a figure for demonstrating the flow of the user data external registration process which concerns on this invention. It is a figure for demonstrating the flow of the user data deletion process 1 which concerns on this invention. It is a figure for demonstrating the flow of the user data deletion process 2 which concerns on this invention. It is a figure for demonstrating the example of the file selection screen for WebUI which concerns on this invention. It is a figure for demonstrating the example of the user data registration screen (user data writing screen) for Web UI which concerns on this invention.

<Embodiment>
Embodiments of the present invention will be described below with reference to the accompanying drawings.

[System configuration]
As shown in FIG. 1, the storage system according to the present invention includes a user terminal 10, a storage server 20, and an external terminal 30. The number of each device is arbitrary.

  The user terminal 10 is located in the user's home (in a predetermined building or room), and metadata (index information) regarding user data such as files and folders held by the terminal and a server / storage device connected to the terminal. : Data used for user data identification, data for managing, searching, and acquiring user data) is transmitted to the storage server 20 and cached when user data is transmitted based on metadata (index information). To do. “Caching” is to store “cache”, which is duplicated data of the user data, in a relatively high-speed storage device in order to speed up reading of the original user data. That is, the user terminal 10 stores a cache of user data managed by the terminal in the storage server 20. The user terminal 10 can also use a cache of user data stored in the storage server 20 by another terminal. The user terminal 10 is preferably connected to the storage server 20 constantly / periodically. The user's house is only an example of the location of the user data body. Actually, it is not limited to the user's house.

  The storage server 20 stores a cache of user data acquired from each user terminal 10. The storage server 20 may be a server constituting a cloud (a combination of at least one server and a plurality of servers is also possible). Further, when there is a request for user data from the user terminal 10 or the external terminal 30 based on the stored metadata (index information), the storage server 20 authenticates the request source terminal and the user, and performs authentication. As a result, for the terminal (authenticated terminal) to which the use authority of the user data is given or the user, the user is stored from the stored cache or from the user terminal 10 storing the user data serving as the master file. Acquire data and provide the user data.

  The external terminal 30 is located outside the user's home (a place other than the user's home), and user data managed by the user terminal 10 indirectly by using a cache stored in the storage server 20 by the user terminal 10. Is used. Here, a terminal such as a general PC (personal computer) or a smartphone is assumed as an example of the external terminal 30. Note that the external terminal 30 may be one of the user terminals 10. That is, the external terminal 30 may have the same function as the user terminal 10. For example, when the user of the user terminal 10 uses a cache of other person's user data, the user terminal 10 becomes the external terminal 30. Further, even if the terminals are used by the same user, the “terminal used in the user's house” may be the user terminal 10 and the “terminal used outside the user's house” may be the external terminal 30. Further, even the same terminal can be the user terminal 10 when “used inside the user's house” and the external terminal 30 when “used outside the user's house”. Whether the user is in the user's home or not can be determined from the IP address of the terminal or relay device, GPS information (position information), or the like, but the user himself / herself may set the storage server 20 or the client application.

[User terminal configuration]
The user terminal 10 includes a client application execution unit 11 and a data storage unit 12.

  The client application execution unit 11 executes a client application (client application software) in accordance with an execution operation from the user or when the user terminal 10 is activated. The client application execution unit 11 collects metadata (index information) related to user data according to the client application and transmits it to the storage server 20. Further, the client application execution unit 11 transmits the user data requested by the external terminal 30 based on the metadata (index information) to the storage server 20 and caches it via the storage server 20 according to the client application. Further, the client application execution unit 11 may transmit user-specified user data to the storage server 20 and cache it in accordance with the client application. At this time, the client application execution unit 11 may synchronize user data between the user terminal 10 and the storage server 20 in accordance with the client application. The synchronization method may be either “push type” / “pull type”.

  If the size of the cache stored in the storage server 20 is larger than the specified value, the client application execution unit 11 divides the cache into blocks, and transmits all or differences to the storage server 20 for each block. On the other hand, when the size of the cache acquired from the storage server 20 is larger than the specified value, all or the difference of the cache divided into blocks is received from the storage server 20 for each block.

  In addition, when there is a change (update, addition, deletion, etc.) in the content of user data designated in advance, the client application execution unit 11 transmits metadata (index information) regarding the changed user data to the storage server 20. The metadata (index information) related to the changed user data is stored in the storage server 20. For example, metadata (index information) related to user data after change is overwritten with metadata (index information) related to user data before change. When user data before change is stored in the storage server 20 as a cache, the user data after change may be transmitted to the storage server 20 to update the cache stored in the storage server 20. For example, the cache of user data after change is overwritten with the cache of user data before change.

  The data storage unit 12 stores a user data body serving as a master file. The data storage unit 12 is not limited to a storage device inside the user terminal 10 but may be an external file server or the like. The data storage unit 12 may be a predetermined storage area in the storage device. That is, the data storage unit 12 may be managed by the user of the user terminal 10. The data storage unit 12 is preferably connected to the network constantly / periodically.

[Storage server configuration]
The storage server 20 includes a client manager execution unit 21, a core manager execution unit 22, a cache storage unit 23, a metadata storage unit 24, an ACL (Access Control List) management unit 25, and a Web UI (Web User Interface) execution. Part 26 is provided.

  The client manager execution unit 21 executes a client manager (server application) corresponding to the client application. The client manager execution unit 21 communicates with the client application execution unit 11 of each user terminal 10 and stores user data stored in the data storage unit 12 of each user terminal 10 and metadata (index information) about the user data. To get.

  The core manager execution unit 22 executes a core manager (server application) corresponding to the client manager. The core manager execution unit 22 manages the client manager execution unit 21 and collects individual user data and metadata (index information). The core manager execution unit 22 performs internal control of the storage server 20.

  The cache storage unit 23 stores a cache of user data. Here, the cache storage unit 23 secures an area for storing the cache for each user terminal (or for each user). The business operator who operates the storage server 20 can charge the capacity (size) of the cache itself and the capacity of the area for storing the cache. For example, it is free up to a certain capacity, and the user is charged for the excess.

  The cache includes a temporary cache and a permanent cache (permanent). The temporary cache is a cache that is automatically deleted from the area when there is no room in the reserved area. A permanent cache is a cache that is not automatically deleted even if there is no room in the reserved area. However, it is possible to delete the permanent cache according to the operation of the user of the user terminal 10. Whether the cache is temporary or permanent can be set for each cache by the user of the user terminal 10.

  The metadata storage unit 24 stores metadata (index information) related to individual user data. The contents of the metadata (index information) will be described later. Further, the metadata storage unit 24 may store information such as presence / absence of cache of user data, a user identifier, and a terminal identifier in association with the metadata.

  The ACL management unit 25 stores a list (ACL) enumerating resources such as access authority of individual users / terminals and files accessible by the individual users / terminals. Here, the management object of ACL is expanded so as to be compatible with a plurality of users / terminals other than the user, and metadata (index information) is disclosed to a plurality of users / terminals outside the user. Enable cache browsing and editing from the terminal. The user terminal 10 sets the access authority of each user / terminal, the file accessible by each user / terminal, etc. according to the input operation from the user. The storage server 20 creates an ACL based on the setting from the user terminal 10. In practice, the user terminal 10 may directly edit the ACL in accordance with an input operation from the user. Further, the user terminal 10 can be set to charge a cache or the like having a high access frequency as pay information and to grant an access authority corresponding to the payment fee. The business operator operating the storage server 20 can collect a part of the payment fee as a management fee / fee.

  The web UI execution unit 26 provides the user terminal 10 and the external terminal 30 with a web UI for displaying data and inputting data via the network. As examples of the Web UI, a Web page displayed on a browser or the like, an operation screen of a network-compatible application, and the like can be considered.

[Contents of metadata (index information)]
As an example of the content of the metadata (index information), any one or combination of the following (1) to (3) is conceivable.

(1) General file information Identification information (full path file name, etc.), creation / update date, file size, etc.

(2) Main properties Document data: Title name, application name, attribute information, etc. Music data: Song name, album name, artist information, song length, other tag information, etc. Image data: Vertical / horizontal size, resolution, camera information, Thumbnail image etc.

(3) System information Hash function (one-way summary function): MD5 (Message Digest 5) etc. Block information, terminal identifier (device ID) etc.

  However, actually, it is not limited to these examples.

[Hardware example]
Hereinafter, a specific example of hardware for realizing the storage system according to the present invention will be described.

  Here, as examples of the user terminal 10, the storage server 20, and the external terminal 30, a computer such as a PC (personal computer), a mobile phone, a smartphone, a smart book, an appliance, a workstation, a mainframe, and a supercomputer is assumed. doing. In addition, not only a terminal and a server but a relay device and a peripheral device may be used. Moreover, an expansion board mounted on a computer or the like, or a virtual machine (VM: Virtual Machine) constructed on a physical machine may be used.

  Although not shown, each of the user terminal 10, the storage server 20, and the external terminal 30 communicates with a processor that drives based on a program and executes predetermined processing, a memory that stores the program and various data, and a network It is realized by the interface used for

  Examples of the processor include a CPU (Central Processing Unit), a network processor (NP), a microprocessor, a microcontroller, or a semiconductor integrated circuit (IC: Integrated Circuit) having a dedicated function. Conceivable.

  Examples of the memory include semiconductor storage devices such as a RAM (Random Access Memory), a ROM (Read Only Memory), an EEPROM (Electrically Erasable and Programmable Read Only Memory), a flash memory, and an HDD (Hold SMD). An auxiliary storage device such as State Drive), a removable disk such as a DVD (Digital Versatile Disk), a storage medium such as an SD memory card (Secure Digital memory card), or the like is conceivable. Further, a buffer or a register may be used. Alternatively, DAS (Direct Attached Storage), FC-SAN (Fibre Channel-Storage Area Network), NAS (Network Attached Storage), IP-SAN (IP-Storage Area), etc. may be used.

  Note that the processor and the memory may be integrated. For example, in recent years, a single chip such as a microcomputer has been developed. Therefore, a case where a one-chip microcomputer mounted on an electronic device or the like includes the processor and the memory can be considered.

  Examples of the interfaces include semiconductor integrated circuits such as substrates (motherboards and I / O boards) and chips that support network communication, network adapters such as NIC (Network Interface Card), and similar expansion cards and communication devices such as antennas. A communication port such as a connection port (connector) is conceivable.

  Examples of the network include the Internet, a LAN (Local Area Network), a wireless LAN (Wireless LAN), a WAN (Wide Area Network), a backbone (Backbone), a cable television (CATV) line, a fixed telephone network, a mobile phone network, WiMAX (IEEE 802.16a), 3G (3rd Generation), dedicated line (lease line), IrDA (Infrared Data Association), Bluetooth (registered trademark), serial communication line, data bus, and the like can be considered.

  The internal components of each of the user terminal 10, the storage server 20, and the external terminal 30 may be a module, a component, a dedicated device, or an activation (calling) program thereof.

  However, actually, it is not limited to these examples.

[Processing procedure]
The flow of processing in the storage system according to the present invention will be described below.

[Metadata (index information) registration process]
With reference to FIG. 2, the flow of processing when storing metadata (index information) from the user terminal 10 to the storage server 20 will be described.

(1) Step S101
The client application execution unit 11 of the user terminal 10 executes the client application in accordance with an execution operation from the user or when the user terminal 10 is activated.

(2) Step S102
The client application execution unit 11 of the user terminal 10 designates and sets the data storage unit 12 that stores user data for the storage server 20 in accordance with the input operation / pre-setting information from the user. If necessary, user data itself may be designated and set. Note that the data storage unit 12 that stores user data that may be transmitted to the external terminal 30 and the data storage unit 12 that stores user data received from the external terminal 30 may be the same storage device / storage area or different. It may be a storage device / storage area. Further, the client application execution unit 11 stores user data that may be transmitted to the external terminal 30 and user data received from the external terminal 30 in the data storage unit 12. The client application execution unit 11 sets the access authority and the like related to the specified user data to the storage server 20 in accordance with an input operation from the user. Further, the client application execution unit 11 places a restriction that only the storage server 20 can access the user data itself / the data storage unit 12 itself stored in the data storage unit 12. For example, the client application execution unit 11 grants access permission of the user data stored in the data storage unit 12 to the client application, and the server authentication or IP address of the storage server 20 by SSL (Secure Socket Layer) or the like The access request from the storage server 20 is accepted and the process is executed. Also, access requests from other than the storage server 20 are not accepted and processing is not executed.

(3) Step S103
The client application execution unit 11 of the user terminal 10 is stored in the data storage unit 12 when receiving an instruction from the user / periodically / when starting up the user terminal or the client application / when creating / changing user data. Metadata (index information) related to user data that is present (or specified in advance). The client application execution unit 11 may collectively collect the collected metadata (index information) into a list information format such as a database or a table.

(4) Step S104
The client application execution unit 11 of the user terminal 10 transmits the collected metadata (index information) together with the identification information (user identifier, terminal identifier, IP address, etc.) of the user terminal 10 to the storage server 20. The client application execution unit 11 may individually transmit the changed metadata (index information) to the storage server 20 when creating or changing the user data, or list the collected metadata (index information). The information may be stored in the form of information and periodically transmitted to the storage server 20. Thereby, the client application execution part 11 can synchronize the metadata (index information) regarding user data between the user terminal 10 and the storage server 20. The client application execution unit 11 of the user terminal 10 transmits a request based on the metadata (index information) from the storage server 20 or the external terminal 30 when transmitting the collected metadata (index information) to the storage server 20. When receiving / instructing a user / periodically / when starting a user terminal or client application / when creating / changing user data, the user data is acquired and the user data is stored in the storage server 20 You may make it cache.

[Metadata (index information) acquisition processing]
With reference to FIG. 3, the flow of processing when acquiring metadata (index information) from the user terminal 10 on the storage server 20 will be described.

(1) Step S201
The client manager execution unit 21 of the storage server 20 establishes a connection with the client application execution unit 11 of each user terminal 10, and the identification information of the user terminal 10 (from the client application execution unit 11 of each user terminal 10 ( Metadata (index information) is received together with a user identifier, a terminal identifier, an IP address, and the like. The metadata (index information) may be in the form of list information.

(2) Step S202
The core manager execution unit 22 of the storage server 20 associates the received metadata (index information) with the identification information (user identifier, terminal identifier, IP address, etc.) of the user terminal 10 and stores it in the metadata storage unit 24. Store. The metadata (index information) may be in the form of list information. At this time, if there is already metadata (index information) corresponding to the identification information of the same user terminal 10, the core manager execution unit 22 deletes or overwrites the old metadata (index information), and the metadata (index information) ).

(3) Step S203
The core manager execution unit 22 of the storage server 20 stores the cache of user data that does not correspond to the metadata (index information) stored in the metadata storage unit 24 when the cache storage unit 23 stores the cache. It deletes from the part 23. On the contrary, the core manager executing unit 22 determines that the capacity of the cache storage unit 23 is not stored in the cache storage unit 23 when the cache of the user data corresponding to the metadata (index information) stored in the metadata storage unit 24 is not stored. If there is a margin (vacant), the user data may be acquired via the client application execution unit 11, and the user data may be stored in the cache storage unit 23 as a cache.

(4) Step S204
The core manager execution unit 22 of the storage server 20 creates a list (ACL) that lists the access authority of each user / terminal and resources such as accessible files, and stores the ACL in the ACL management unit 25.

  At this time, the client manager execution unit 21 of the storage server 20 acquires pre-designated user data stored in the data storage unit 12 of the user terminal 10 from the client application execution unit 11 of each user terminal 10. You may do it. Actually, the client manager execution unit 21 may transmit the user data acquisition request to the client application execution unit 11 and receive the user data as a response.

  The core manager execution unit 22 of the storage server 20 may acquire user data from the client manager execution unit 21 and store the user data in the cache storage unit 23 as a cache.

[Server access processing]
With reference to FIG. 4, the flow of processing when accessing the storage server 20 from the external terminal 30 (including other user terminals 10) will be described.

(1) Step S301
The Web UI execution unit 26 of the storage server 20 transmits Web UI initial screen data to the external terminal 30 in response to an access request from the external terminal 30. Note that the Web UI execution unit 26 of the storage server 20 may publish Web UI initial screen data on the network as a Web page. Here, it is assumed that the initial screen data of the Web UI is provided with an input field for authentication information (such as a user identifier and a password).

(2) Step S302
The external terminal 30 inputs authentication information (such as a user identifier and a password) to the initial screen data of the Web UI according to an input operation from the user of the terminal, and transmits the authentication information to the storage server 20.

(3) Step S303
When the Web UI execution unit 26 of the storage server 20 receives the authentication information (user identifier and password, etc.) input to the initial screen data of the Web UI from the external terminal 30, the authentication information (user identifier and password, etc.) is executed by the core manager. Pass to part 22.

(4) Step S304
The core manager execution unit 22 of the storage server 20 performs authentication for authentication information (such as a user identifier and a password) based on the ACL stored in the ACL management unit 25.

(5) Step S305
The core manager execution unit 22 of the storage server 20 refers to the metadata (index information) regarding the user data when the access authority regarding the predetermined user data is given to the external terminal 30 as a result of the authentication. It is confirmed whether the cache of the user data is stored in the cache storage unit 23 (whether or not there is a cache).

(6) Step S306
The core manager execution unit 22 of the storage server 20 confirms the connection status between the client manager execution unit 21 of the storage server 20 and the client application execution unit 11 of the user terminal 10 to confirm whether the user terminal 10 is online. Actually, the operation status of the client application, the communication line speed, and the like may be confirmed.

(7) Step S307
The core manager execution unit 22 of the storage server 20 creates file selection screen data for Web UI based on the confirmation result. Here, in the file selection screen data for Web UI, information indicating the presence / absence of a cache, information indicating online / offline of the user terminal 10, and selected user data are acquired together with metadata (index information) related to user data. It is assumed that an acquisition button or the like is included. For user data for which no access authority is given to the external terminal 30, metadata (index information) regarding the user data and information indicating the presence / absence of a cache are not included in the file selection screen data for Web UI. Also good.

(8) Step S308
The Web UI execution unit 26 of the storage server 20 transmits Web UI file selection screen data to the external terminal 30.

  Here, the external terminal 30 accesses the storage server 20 via the Web UI. However, in practice, the external terminal 30 may access the storage server 20 using a client application.

[User data acquisition processing]
With reference to FIG. 5, a processing flow when the external terminal 30 (including other user terminals 10) uses a cache or the like via the storage server 20 will be described.

(1) Step S401
The external terminal 30 displays a file selection screen for Web UI based on the file selection screen data for Web UI. The external terminal 30 designates metadata (index information) related to predetermined user data displayed on the Web UI file selection screen in accordance with an input operation from the user, and when the acquisition button is pressed, The identification information is transmitted to the storage server 20.

(2) Step S402
When the Web UI execution unit 26 of the storage server 20 receives identification information of predetermined user data from the external terminal 30, it passes this identification information to the core manager execution unit 22.

(3) Step S403
The core manager execution unit 22 of the storage server 20 checks whether the cache of user data corresponding to this identification information is stored in the cache storage unit 23 (whether or not there is a cache). The core manager execution unit 22 confirms the access authority of the external terminal 30 or the user based on the ACL before confirming whether or not the cache exists, and transmits user data corresponding to the identification information to the external terminal 30. You may make it judge whether it is okay.

(4) Step S404
When the cache of the user data corresponding to the identification information is stored in the cache storage unit 23, the core manager execution unit 22 of the storage server 20 reads the cache from the cache storage unit 23 and uses the cache as the user data. It transmits to the external terminal 30.

(5) Step S405
When the cache of the user data corresponding to the identification information is not stored in the cache storage unit 23, the core manager execution unit 22 of the storage server 20 moves the user terminal 10 that manages the user data corresponding to the identification information to the user terminal 10 The user corresponding to the identification information is identified based on the terminal identifier associated with the user data, and accessed through the client application execution unit 11 of the identified user terminal 10 to the data storage unit 12 of the user terminal 10. Data is extracted and acquired, and the user data is stored in the cache storage unit 23 as a cache. In practice, the client manager execution unit 21 transmits a cache acquisition request to the client application execution unit 11, receives user data as a response, and stores the cache of the user data in the cache storage unit 23. Also good.

(6) Step S406
When the core manager execution unit 22 of the storage server 20 stores the cache of the user data in the cache storage unit 23, the core manager execution unit 22 updates the information indicating the presence / absence of the cache of the user data and reflects it in the file selection screen data for Web UI. The cache is read from the cache storage unit 23 and transmitted to the external terminal 30. The storage server 20 may transmit the user data acquired from the user terminal 10 to the external terminal 30 instead of the cache stored in the cache storage unit 23. That is, the storage of the user data cache in the cache storage unit 23 and the transmission of the user data to the external terminal 30 may be processed in parallel.

(7) Step S407
The core manager execution unit 22 of the storage server 20 cannot acquire the user data from the user terminal 10 that manages the user data within a specified time after starting the acquisition process of the user data corresponding to the identification information. In this case, it is determined that a failure has occurred in the network connection environment of the user terminal 10 or the user terminal 10 itself (power supply or the like), and information indicating a cache acquisition error or offline of the user terminal 10 is displayed for the Web UI. The file selection screen data is reflected and notified to the external terminal 30.

[Transmission and reception processing between terminal and server]
It is also conceivable to change user data transmission / reception processing according to the communication quality of the network connection environment among the user terminal 10, the storage server 20, and the external terminal 30.

  For example, when the communication quality of the network connection environment between the user terminal 10 and the storage server 20 is high, and the communication quality of the network connection environment between the storage server 20 and the external terminal 30 is low, the storage server 20 collectively receives user data from the user terminal 10 in units of files / folders. At this time, if the external terminal 30 is executing the client application, the received user data or the cache of the user data is divided into blocks and transmitted to the external terminal 30 for each block. A client application is required for transmission and reception in blocks. If the Web client is compatible with byte range operations, data can be transmitted and received from the middle.

  Conversely, when the communication quality of the network connection environment between the user terminal 10 and the storage server 20 is low, and the communication quality of the network connection environment between the storage server 20 and the external terminal 30 is high, the storage The server 20 divides the user data of the user terminal 10 in units of blocks, receives the user data for each block, and transmits the user data or the cache of the user data to the external terminal 30 in units of files / folders. To do.

  As a result, the playback position is moved, the transcode data is temporarily stored, the next content is prefetched, and the first content (the first episode, the first song, etc.) is the next at the latest. It is possible to cache the contents (2nd episode, 2nd song, etc.) and later in the storage server by prefetching so that they can be read quickly.

  Here, the transmission of user data in the flow “user terminal 10 → storage server 20 → external terminal 30” has been described. However, the transmission of user data in the flow “external terminal 30 → storage server 20 → user terminal 10”. It is possible to carry out similarly.

[When to delete cache]
For example, the core manager execution unit 22 of the storage server 20 deletes the cache at the following timing.

(1) Default time The core manager execution unit 22 of the storage server 20 deletes the cache of user data of the user terminal 10 from the cache storage unit 23 after a predetermined time after the user terminal 10 goes offline (inactive). .

(2) Default Capacity The core manager execution unit 22 of the storage server 20 caches the user data cache of the user terminal 10 when the cache accumulated in the area reserved for the user terminal 10 reaches the predetermined capacity. It deletes from the part 23.

[Order of cache to delete]
When deleting the cache from the cache storage unit 23, the cache is deleted in the following order.

(1) Usage frequency The core manager execution unit 22 of the storage server 20 deletes caches in order from the oldest registered date and the lowerest access frequency.

(2) Request from User The core manager execution unit 22 of the storage server 20 deletes the cache of user data requested to be deleted from the user terminal 10. On the other hand, the user data other than the user data cache requested by the user terminal 10 may be deleted.

(3) Cooperation When the core manager execution unit 22 of the storage server 20 detects that the user data managed by the user terminal 10 on the data storage unit 12 has been deleted (or when notified), Delete the user data cache.

  The core manager execution unit 22 of the storage server 20 deletes the user data cache from the cache storage unit 23 and then updates information indicating whether or not the deleted user data cache exists.

[User data external editing processing]
With reference to FIG. 6, the flow of processing when editing user data cached on the storage server 20 from the external terminal 30 (including other user terminals 10) will be described.

  For example, not only when a user other than the user of the user terminal 10 edits the cached user data using the external terminal 30 outside the user's home, the user of the user terminal 10 uses the external terminal 30 outside the user's home. It is also possible to edit cached user data.

(1) Step S501
The external terminal 30 receives the cached user data from the storage server 20. At this time, the core manager execution unit 22 of the storage server 20 creates user data editing screen data for Web UI including the contents of the cached user data, and edits user data for Web UI via the Web UI execution unit 26. The screen data may be transmitted to the external terminal 30.

(2) Step S502
The external terminal 30 refers to the contents of the cached user data. At this time, the external terminal 30 may display the Web UI user data editing screen based on the Web UI user data editing screen data received from the storage server 20. The user data editing screen for Web UI may directly display identification information (file name, etc.) and contents of cached user data, or display an icon of cached user data. In addition, when the icon or the like is clicked, the contents of the cached user data may be displayed.

(3) Step S503
The external terminal 30 edits the cached user data in accordance with an input operation from the user of the terminal. At this time, the external terminal 30 may display a screen for editing the contents of the cached user data when the edit button displayed on the user data editing screen for Web UI is pressed. good. Actually, a general file editing application may be activated to edit the contents of the cached user data. The external terminal 30 edits the cached user data on the user data editing screen for Web UI or the file editing application.

(4) Step S504
When the editing of the cached user data is completed, the external terminal 30 transmits the edited user data to the storage server 20. At this time, the external terminal 30 transmits the edited user data to the storage server 20 when the completion button displayed on the user data editing screen for Web UI is pressed according to the input operation from the user of the terminal. You may make it do.

(5) Step S505
When receiving the edited user data from the external terminal 30, the Web UI execution unit 26 of the storage server 20 passes the edited user data to the core manager execution unit 22.

(6) Step S506
When the core manager executing unit 22 of the storage server 20 receives the edited user data, the core manager executing unit 22 authenticates the authentication information (user identifier, password, etc.) of the external terminal 30 based on the ACL stored in the ACL managing unit 25. Do. Note that the authentication is not limited to the time when the edited user data is received, and may be performed in advance. For example, the authentication performed when the storage server 20 is first accessed from the external terminal 30 may be the authentication.

(7) Step S507
As a result of authentication, the core manager execution unit 22 of the storage server 20 is given the authority to update the user data to the external terminal 30, based on the metadata stored in the metadata storage unit 24. The edited user data is reflected in the cache stored in the cache storage unit 23. For example, the core manager execution unit 22 overwrites the contents of the edited user data in the cache stored in the cache storage unit 23 with the contents of the cache having the same identification information (file name, etc.) as the edited user data. To do. Alternatively, the core manager execution unit 22 replaces the cache stored in the cache storage unit 23 with the edited user data. At this time, the core manager execution unit 22 of the storage server 20 may update the metadata (index information) stored in the metadata storage unit 24. For example, the core manager execution unit 22 of the storage server 20 reflects the metadata (index information) related to the edited user data in the metadata (index information) stored in the metadata storage unit 24.

(8) Step S508
The core manager execution unit 22 of the storage server 20 identifies the user terminal 10 based on the terminal identifier associated with the user data, and the client manager execution unit 21 of the storage server 20 and the client application execution unit 11 of the user terminal 10 The connection status is confirmed, whether the user terminal 10 is online, and if the user terminal 10 is online, the edited user data is transmitted to the user terminal 10. For example, the core manager execution unit 22 stores the edited user data cache in an area reserved for each user in the cache storage unit 23, so that the user terminal 10 of the user who uses the area stores the user data cache. The edited user data is transmitted. Alternatively, the edited user data may be transmitted to the user terminal 10 designated by the external terminal 30. At this time, the core manager execution unit 22 confirms whether the edited user data is user data edited by the external terminal 30 to which the predetermined authority is given based on the ACL, and the permitted external terminal 30 If the user data is edited, the edited user data may be transmitted to the user terminal 10. Alternatively, the core manager execution unit 22 may confirm whether the edited user data may be transmitted to the user terminal 10 before transmission. When the client application execution unit 11 of the user terminal 10 receives the edited user data, the client application execution unit 11 stores the edited user data in the data storage unit 12. For example, the client application execution unit 11 overwrites the content of the original user data (master file) with the content of the edited user data. Alternatively, the client application execution unit 11 replaces the original user data (master file) with the edited user data. Thereafter, the client application execution unit 11 transmits a write completion notification to the client manager execution unit 21 of the storage server 20. The core manager execution unit 22 may notify the external terminal 30 of this write completion notification via the Web UI execution unit 26. Further, when the user terminal 10 is not online (offline) or when the user terminal 10 is refused to receive / store the edited user data, the core manager execution unit 22 passes the Web UI execution unit 26. Thus, a storage error may be notified to the external terminal 30. Also, in this case, referring to the ACL, before the storage error is transmitted according to the user's membership grade (paid member / free member, etc.), the edited user data is stored in the cache storage unit 23 as a cache, The connection status may be checked again after a certain time, and the edited user data may be transmitted to the user terminal 10 as soon as the user terminal 10 is online.

(9) Step S509
When the client application execution unit 11 of the user terminal 10 stores the edited user data in the data storage unit 12, the client application execution unit 11 updates metadata (index information) related to the user data. For example, the client application execution unit 11 of the user terminal 10 collects metadata (index information) related to user data based on the edited user data and reflects the metadata on the storage server 20. In addition, when the metadata (index information) regarding the said user data is already updated on the storage server 20, this process does not need to be performed.

[User data external registration processing]
With reference to FIG. 7, the flow of processing when registering new user data in the user terminal 10 from the external terminal 30 (including other user terminals 10) via the storage server 20 will be described.

  For example, the user of the user terminal 10 is not limited to a case where a user other than the user of the user terminal 10 registers new user data in the user terminal 10 from the external terminal 30 outside the user's home via the storage server 20. A case where new user data is registered in the user terminal 10 from the external terminal 30 via the storage server 20 is also conceivable.

(1) Step S601
The external terminal 30 once transmits new user data to the storage server 20 in accordance with an input operation from the user of the terminal. At this time, the core manager execution unit 22 of the storage server 20 creates user data registration screen data for Web UI, and transmits the user data registration screen data for Web UI to the external terminal 30 via the Web UI execution unit 26. Also good. The external terminal 30 displays a user data registration screen for Web UI based on the user data registration screen data for Web UI, and when a transmission button displayed on the user data registration screen for Web UI is pressed, a new user is displayed. Data is transmitted to the storage server 20.

(2) Step S602
When the Web UI execution unit 26 of the storage server 20 receives new user data from the external terminal 30, it passes the new user data to the core manager execution unit 22.

(3) Step S603
When the core manager execution unit 22 of the storage server 20 receives new user data, the core manager execution unit 22 authenticates the authentication information (such as a user identifier and password) of the external terminal 30 based on the ACL stored in the ACL management unit 25. . The authentication is not limited to the time when new user data is received, and may be performed in advance. For example, the authentication performed when the storage server 20 is first accessed from the external terminal 30 may be the authentication.

(4) Step S604
The core manager execution unit 22 of the storage server 20 stores the cache of the new user data in the cache storage unit 23 when the authority to register the new user data is given to the external terminal 30 as a result of the authentication. . At this time, the core manager execution unit 22 of the storage server 20 may update the metadata (index information) stored in the metadata storage unit 24. For example, the core manager execution unit 22 of the storage server 20 reflects the metadata (index information) related to the new user data in the metadata (index information) stored in the metadata storage unit 24.

(5) Step S605
The core manager execution unit 22 of the storage server 20 identifies the user terminal 10 based on the terminal identifier associated with the user data, and the client manager execution unit 21 of the storage server 20 and the client application execution unit 11 of the user terminal 10 The connection status is confirmed, it is confirmed whether the user terminal 10 is online, and when the user terminal 10 is online, new user data is transmitted to the user terminal 10. For example, the core manager execution unit 22 stores a cache of new user data in an area reserved for each user in the cache storage unit 23, so that the user terminal 10 of the user who uses the area can Send new user data. Alternatively, the new user data may be transmitted to the user terminal 10 designated by the external terminal 30. At this time, the core manager execution unit 22 confirms whether the new user data is user data edited by the external terminal 30 to which the predetermined authority is given based on the ACL, and edits by the permitted external terminal 30. If it is user data, new user data may be transmitted to the user terminal 10. Alternatively, the core manager execution unit 22 may confirm whether new user data may be transmitted to the user terminal 10 before transmission. When the client application execution unit 11 of the user terminal 10 receives new user data, the client application execution unit 11 stores the new user data in the data storage unit 12. Thereafter, the client application execution unit 11 transmits a write completion notification to the client manager execution unit 21 of the storage server 20. The core manager execution unit 22 may notify the external terminal 30 of this write completion notification via the Web UI execution unit 26. Further, when the user terminal 10 is not online (offline) or when the user terminal 10 is refused to receive / store the edited user data, the core manager execution unit 22 passes the Web UI execution unit 26. Thus, a storage error may be notified to the external terminal 30. Also, in this case, referring to the ACL, before the storage error is transmitted according to the user's membership grade (paid member / free member, etc.), the edited user data is stored in the cache storage unit 23 as a cache, The connection status may be checked again after a certain time, and the edited user data may be transmitted to the user terminal 10 as soon as the user terminal 10 is online.

(6) Step S606
The client application execution unit 11 of the user terminal 10 updates metadata (index information) related to user data. For example, the client application execution unit 11 of the user terminal 10 collects metadata (index information) related to new user data and reflects it on the storage server 20. In addition, when the metadata (index information) regarding the said user data is already updated on the storage server 20, this process does not need to be performed.

[Connection attempt when user terminal is offline]
Although not essential, in the “user data external editing process” shown in FIG. 6 and the “user data external registration process” shown in FIG. 7, the core manager execution unit 22 of the storage server 20 is not online (offline). In this case, the client manager execution unit 21 of the storage server 20 may be instructed to connect to the client application execution unit 11 of the user terminal 10. The client manager execution unit 21 of the storage server 20 tries to connect to the client application execution unit 11 of the user terminal 10. When the connection with the client application execution unit 11 of the user terminal 10 is established, the client manager execution unit 21 notifies the core manager execution unit 22 of the storage server 20 that the user terminal 10 is online. In addition, the client manager execution unit 21 of the storage server 20 determines that the connection with the client application execution unit 11 of the user terminal 10 cannot be established even if connection is attempted for a predetermined number of times / predetermined periods. You may make it notify to 22 that the user terminal 10 cannot be accessed.

  Further, in the “user data external editing process” shown in FIG. 6 and the “user data external registration process” shown in FIG. 7, the storage server 20 uses the user acquired from the external terminal 30 instead of the cache stored in the cache storage unit 23. Data may be transmitted to the user terminal 10. That is, the storage of the user data cache in the cache storage unit 23 and the transmission of the user data to the user terminal 10 may be processed in parallel.

[User data external edit processing using user data external registration processing]
In the “user data external registration process” shown in FIG. 7, when “new user data” is read as “cache after editing”, this “user data external registration process” is changed to “user data external edit process”. It can be. That is, when user data is not edited on the Web UI, it can be handled only by the “user data external registration process” shown in FIG. 7, and the “user data external edit process” shown in FIG. 6 is not necessary.

  When performing “user data external editing processing” by “user data external registration processing”, the core manager execution unit 22 of the storage server 20 determines whether the received user data is “user data after editing” or “new user data”. Is determined by comparing the received user data identification information (file name, etc.) and other attribute information with the metadata (index information) stored in the metadata storage unit 24. You may do it.

[User data deletion process 1]
With reference to FIG. 8, the flow of the 1st process at the time of deleting the user data (master file) on the user terminal 10 is demonstrated.

(1) Step S701
The client application execution unit 11 of the user terminal 10 deletes the specified user data from the user data stored in the data storage unit 12 in accordance with an input operation from the user. Actually, the client application execution unit 11 of the user terminal 10 may delete the user data designated by the user by using the OS file management program without using the client application.

(2) Step S702
The client application execution unit 11 updates the metadata related to the user data when receiving an instruction from the user / periodically / when starting the user terminal or the client application / when deleting the user data, and deleting the user data. The deleted user data is identified by comparison with the history and the metadata before update, and a request to delete the cache of the user data is transmitted to the storage server 20.

(3) Step S703
The client manager execution unit 21 of the storage server 20 establishes a connection with the client application execution unit 11 of each user terminal 10, and requests to delete the cache of the user data from the client application execution unit 11 of each user terminal 10. Receive.

(4) Step S704
The core manager execution unit 22 of the storage server 20 deletes the cache of the user data requested to be deleted from the cache storage unit 23.

(5) Step S705
The core manager execution unit 22 updates the metadata (index information) stored in the metadata storage unit 24. For example, the core manager execution unit 22 discards metadata (index information) related to user data for which a cache deletion request has been made.

[User data deletion process 2]
With reference to FIG. 9, the flow of the 2nd process at the time of deleting the user data (master file) on the user terminal 10 is demonstrated.

(1) Step S801
The client application execution unit 11 of the user terminal 10 deletes the specified user data from the user data stored in the data storage unit 12 in accordance with an input operation from the user. Actually, the client application execution unit 11 of the user terminal 10 may delete the user data designated by the user by using the OS file management program without using the client application.

(2) Step S802
The client application execution unit 11 of the user terminal 10 receives metadata (index information) related to user data when receiving an instruction from the user / periodically / when starting the user terminal or the client application / when deleting user data. collect. Here, metadata (index information) relating to all user data (master files) to be targeted on the data storage unit 12 of the user terminal 10 is collected. At this time, metadata (index information) regarding the deleted user data is not collected.

(3) Step S803
The client application execution unit 11 of the user terminal 10 transmits the collected metadata (index information) together with the identification information (user identifier, terminal identifier, IP address, etc.) of the user terminal 10 to the storage server 20.

(4) Step S804
The client manager execution unit 21 of the storage server 20 receives metadata (index information) from the client application execution unit 11 of each user terminal 10 together with identification information (user identifier, terminal identifier, IP address, etc.) of the user terminal 10. Receive.

(5) Step S805
The core manager execution unit 22 of the storage server 20 associates the received metadata (index information) with the identification information (user identifier, terminal identifier, IP address, etc.) of the user terminal 10 and stores it in the metadata storage unit 24. Store. At this time, the core manager execution unit 22 of the storage server 20 updates the metadata (index information) stored in the metadata storage unit 24 and does not match the received metadata (index information). Is stored in the metadata storage unit 24, the metadata (index information) is determined as metadata relating to the deleted user data, and is deleted (deleted). Here, metadata (index information) related to all user data (master files) as targets on the user terminal 10 is collected, but metadata (index information) related to deleted user data is not collected. The metadata (index information) that does not match the received metadata (index information) is naturally metadata related to the deleted user data.

(6) Step S806
The core manager execution unit 22 of the storage server 20 stores the cache of user data that does not correspond to the metadata (index information) stored in the metadata storage unit 24 when the cache storage unit 23 stores the cache. It deletes from the part 23.

  Note that the user data deletion process described above may not be performed when it is desired to leave a cache on the storage server 20 even after deleting user data (master file) on the user terminal 10. In this case, when the client application execution unit 11 of the user terminal 10 deletes the specified user data from the user data stored in the data storage unit 12 in accordance with an input operation from the user, the processing is performed. Complete. Further, it is necessary to prevent the metadata (index information) related to the deleted user data from being deleted from the metadata (index information) stored in the metadata storage unit 24. For example, the discarding / deletion of metadata (index information) stored in the metadata storage unit 24 is performed only when an instruction from the user of the user terminal 10 is received.

[Example of file selection screen]
With reference to FIG. 10, a file selection screen example will be described as an example of a Web UI file selection screen. However, actually, it is not limited to this example.

  On the file selection screen, a user identifier (user ID) indicating a user, a terminal identifier (device ID) indicating a user terminal, and information indicating online / offline of the user terminal are displayed.

  In addition, for each terminal identifier (device ID), a selection check box for selecting user data, identification information (file name, etc.) of the user data, update date and time of the user data, and cache of the user data A record in which the information indicating the presence / absence and the radio button for selecting whether the user data cache is a temporary cache or a permanent cache is displayed in a table format.

  When the selection check box for selecting user data is selected, if the user data is a folder, information on files in the folder may be displayed in a list.

  Further, an acquisition button and a write button are displayed on the file selection screen.

  If the acquisition button is pressed after the selection check box for selecting user data is selected, the user data cache exists on the storage server, or the user data can be acquired from the user terminal. For example, the user data / cache of the user data is displayed / downloaded.

  When a write button for writing user data (registering in the user terminal 10) is pressed, a user data write screen is displayed.

[User data writing screen example]
With reference to FIG. 11, a user data writing screen example will be described as an example of a user data registration screen for Web UI. However, actually, it is not limited to this example.

  The user data writing screen includes an area for inputting / selecting a terminal identifier (device ID) indicating a user terminal where the user data to be written is stored and information (location information, identification information, etc.) indicating the user data to be written. Is displayed.

  Further, a transmission button and a return button are displayed on the user data writing screen.

  When a terminal identifier (device ID) indicating a user terminal where the user data to be written is stored and information indicating the user data to be written are input / selected and the transmission button is pressed, the user data to be written is transmitted to the storage server 20. And cached.

  When the return button is pressed, the user data writing screen returns to the file selection screen.

<Features of the present invention>
As described above, in the present invention, the external terminal can use the user data on the user terminal via the storage server.

  In the present invention, the storage server collects metadata (index information) related to user data on the user terminal, and presents a list of metadata (index information) related to the user data to the external terminal. The external terminal requests user data on the user terminal based on a list of metadata (index information).

  At this time, in the user terminal, the storage server acquires the user data on the user terminal and indirectly provides it to the external terminal so that the external terminal does not directly operate the user data body on the user terminal. At this time, the storage server temporarily stores user data as a cache. If there is a large amount of user data, only a part of the user data is stored as a cache. When a cache of user data requested from an external terminal is on the storage server, the storage server provides the cache to the external terminal as the user data. If the storage server does not have the requested user data cache on the storage server, the storage server requests the user terminal for the corresponding user data, and if the user data can be obtained, stores the user data as a cache. User data or its cache is provided to an external terminal.

<Remarks>
As mentioned above, although embodiment of this invention was explained in full detail, actually, it is not restricted to said embodiment, Even if there is a change of the range which does not deviate from the summary of this invention, it is included in this invention.

DESCRIPTION OF SYMBOLS 10 ... User terminal 11 ... Client application execution part 12 ... Data storage part 20 ... Storage server 21 ... Client manager execution part 22 ... Core manager execution part 23 ... Cache storage part 24 ... Metadata storage part 25 ... ACL (Access Control List) Management unit 26 ... Web UI (Web User Interface) execution unit 30 ... External terminal

Claims (10)

A user terminal,
A storage server that can be connected to the user terminal via a network;
The user terminal transmits metadata about user data to be a master file to the storage server,
The storage server stores the metadata and a cache of the user data, presents information based on the metadata to an authenticated terminal, and receives an acquisition request for the user data from the authenticated terminal. If the user data cache is stored, the user data cache is stored. If the user data cache is stored, the user data cache is transmitted to the authenticated terminal, and the user data cache is stored. If not, the storage system acquires the user data from the user terminal and transmits the user data to the authenticated terminal. The storage system according to claim 1,
The storage server acquires the user data from the user terminal when there is a request to acquire the user data from the authenticated terminal, and transmits the user data to the authenticated terminal. A storage system that stores data as a cache. The storage system according to claim 1 or 2,
When there is a user data write request from the authenticated terminal, the storage server acquires the user data from the authenticated terminal, and transmits the user data to the user terminal. A storage system that stores as a cache. The storage system according to claim 3,
The storage server confirms the connection status with the user terminal when there is a user data write request from the authenticated terminal, and acquires from the authenticated terminal when the user terminal is offline. A storage system that stores user data as a cache and transmits the user data stored as the cache to the user terminal when the user terminal is online. The storage system according to any one of claims 1 to 4, wherein
The storage server confirms whether or not the user data is cached and the connection status with the user terminal. For the authenticated terminal, the user data is cached together with information based on the metadata. And a storage system that presents information indicating a connection status with the user terminal. The storage system according to any one of claims 1 to 5,
When there is a change in the user data serving as a master file on the user terminal, the user terminal collects metadata about the user data again and sends it to the storage server,
The storage server updates the stored metadata based on the received metadata. The storage system according to any one of claims 1 to 5,
The storage server
When the user terminal is offline after a predetermined time, or when a predetermined storage capacity is reached, or when the registered date / time is an old cache or a cache with low access frequency, or from the user terminal A storage system that deletes a cache of user data acquired from the user terminal when a deletion request is made or when user data on the user terminal is deleted. Means for connecting to a user terminal via a network;
Means for receiving metadata relating to user data to be a master file from the user terminal;
Means for storing the metadata and a cache of the user data;
Means for presenting information based on the metadata to an authenticated terminal;
Means for checking whether the user data cache is stored when there is a request for acquisition of the user data from the authenticated terminal;
Means for transmitting the user data cache to the authenticated terminal, if storing the user data cache;
Means for acquiring the user data from the user terminal if the user data cache is not stored;
Means for transmitting the user data to the authenticated terminal. A user data sharing method implemented by a computer,
Connecting to a user terminal via a network;
Receiving from the user terminal metadata about user data to be a master file;
Storing the metadata and a cache of the user data;
Presenting information based on the metadata to an authenticated terminal;
If there is an acquisition request for the user data from the authenticated terminal, checking whether the user data cache is stored;
When storing the cache of user data, transmitting the cache of user data to the authenticated terminal;
If the user data cache is not stored, obtaining the user data from the user terminal;
Transmitting the user data to the authenticated terminal. A user data sharing method. Connecting to a user terminal via a network;
Receiving from the user terminal metadata about user data to be a master file;
Storing the metadata and a cache of the user data;
Presenting information based on the metadata to an authenticated terminal;
If there is a request for acquisition of the user data from the authenticated terminal, checking whether the cache of the user data is stored;
When storing the cache of user data, transmitting the cache of user data to the authenticated terminal;
If the user data cache is not stored, obtaining the user data from the user terminal;
A program for causing a computer to execute the step of transmitting the user data to the authenticated terminal.

Images