JP2012079043A - Icon display program, method and system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To allow a user using a terminal device to recognize a state of file synchronization so as to improve operability for files.SOLUTION: An icon display part 123 of a terminal device 1 displays a mark showing a file uploading, a failure in uploading and a state of downloading, a mark showing a state in which "create a new file" or "copy the file" is performed in other terminal device 1 and a new file is not downloaded from a storage server 3, and a mark showing that "update the file," "change the file name" or "move the file" is performed in other terminal device 1 and the old file is held in the own terminal device 1, by adding it onto an icon of the file and/or an icon of the folder in response to each state. The icon display part 123 propagates this mark to a superior folder for the integral display.

Description

  The present invention relates to a technique for displaying a folder icon, and more particularly to a technique for reflecting the state of a file belonging to a folder on the icon display.

  Conventionally, there is known an icon display technique for displaying a mark indicating that an error has occurred in addition to an icon of a folder to which the file belongs when the result of processing on the file is an error (see Patent Document 1). ). According to this icon display technology, the user can easily grasp that an error has occurred in a file in the folder only by looking at the icon of the folder displayed on the screen.

  On the other hand, in a system in which a terminal device and a server are connected via a network, a technique for establishing synchronization between a file stored in the terminal device and a file stored in the server is known ( (See Patent Documents 2 and 3). Processing for making these two files have the same data is called file synchronization. In general, file synchronization refers to processing performed on each device in order to make files existing in two or more devices into data of the same content. For example, when a file held by the terminal device is changed, the terminal device transmits the change information to the server, and the server changes the file held by the terminal device based on the change information. By such file synchronization, synchronization can be established between the file stored in the terminal device and the file stored in the server.

  Assuming that the above icon display technology is applied to such a file synchronization system, for example, when a terminal device fails to download or upload a file, it adds an error mark to the icon of the folder to which the file belongs. To display. Thereby, the user can recognize from the display of the icon that an error has occurred in the file.

JP 2010-160741 A JP 2009-64115 A JP 2006-99730 A

  The file synchronization system described above typically has a process for establishing file synchronization. However, the user using the terminal device cannot accurately recognize the progress status of file synchronization, errors caused by file synchronization, and the like only by displaying the file icon and the folder icon. For example, after a user downloads a file from the server to the terminal device, when the file stored in the server is updated by another user using another terminal device, the user operates the downloaded file. It is desirable to be able to recognize that a file is already stale before doing so.

  Accordingly, the present invention has been made to solve the above-described problems, and an object of the present invention is to make a user using a terminal device recognize the state of file synchronization and improve operability for files. It is an object to provide a possible icon display program, method and system.

  In order to solve the above-mentioned problem, the invention of claim 1 provides information indicating a synchronization state between a file stored in a storage unit and a file stored in another device connected via a network. And a step of determining a display of a predetermined mark to be added to the icon of the upper folder to which the file belongs, and a step of adding and displaying the determined predetermined mark to the icon of the upper folder. It is in a program characterized by being executed.

  According to a second aspect of the present invention, in the program according to the first aspect, the step of downloading a file with the other device based on the information indicating the synchronization state; And the step of deleting the display of the predetermined mark when the download is completed between the two.

  The invention according to claim 3 is the program according to claim 1 or 2, wherein when the upload of a file is started with the other device, the file icon and / or the host to which the file belongs A folder icon is displayed with a predetermined mark added, and when the upload fails, the icon is displayed with another predetermined mark added, and when the upload is completed, the predetermined mark is displayed. And a step of deleting the display of the other predetermined mark.

  According to a fourth aspect of the present invention, in the program according to any one of the first to third aspects, the step of propagating the predetermined mark from the icon to an icon of a higher folder is displayed. It is made to perform.

  The invention according to claim 5 is the program according to any one of claims 1 to 4, wherein a mark corresponding to a type of operation of the file by the user is added to the icon and displayed. Are executed by a computer.

  The invention according to claim 6 is the icon display method of the terminal device in a system in which a plurality of terminal devices and a storage server having a folder accessible by the terminal device are connected via a network. The server includes a storage unit in which files belonging to the folder are stored, the terminal device includes a storage unit in which files are stored, and the storage server indicates a file attribute that is stored in the storage unit Transmitting an index to the terminal device; and, based on the attribute data of the file stored in the storage unit by the terminal device and the file index received from the storage server, an upper folder to which the file belongs. Determining the display of a predetermined mark to be added to the icon , The terminal device is characterized by having the steps of: displaying by adding the predetermined mark icon level folder.

  Further, the invention of claim 7 is a system in which a plurality of terminal devices and a storage server having a folder accessible by the terminal device are connected via a network, and the storage server includes a file belonging to the folder. A storage unit that is stored, and a file index transmission unit that transmits a file index indicating an attribute of the file stored in the storage unit to the terminal device, wherein the terminal device includes a storage unit that stores a file; Determining the display of a predetermined mark to be added to the icon of the upper folder to which the file belongs based on the attribute data of the file stored in the storage unit and the file index received from the storage server, Icon table that is displayed with a mark added to the icon of the upper folder Characterized by comprising a part, the.

  As described above, according to the present invention, the file synchronization status is displayed by being added to the icon of the upper folder to which the file belongs. Thus, the user using the terminal device can accurately recognize the state of the file before performing the file operation, and can improve the operability.

1 is a diagram showing an overall configuration of a file synchronization system according to an embodiment of the present invention. It is a figure which shows the flow of the information at the time of file operation in the file synchronization system by embodiment of this invention. It is a figure explaining an event notification sequence. It is a figure which shows the structure of a file index (henceforth FI). It is a figure explaining transition of FI at the time of new file creation. It is a figure explaining transition of FI at the time of file update. It is a figure explaining transition of FI at the time of file deletion. It is a figure explaining transition of FI at the time of file name change. It is a figure explaining transition of FI at the time of file movement. It is a figure explaining transition of FI at the time of file copy. It is a figure explaining the sequence at the time of a file collision. It is a figure explaining the sequence (continuation 1) at the time of a file collision. It is a figure explaining the sequence (continuation 2) at the time of a file collision. It is a figure explaining the sequence at the time of file update (update process for every area | region). It is a block diagram which shows the structure of a terminal device. It is a flowchart which shows the process of a terminal device. It is a flowchart which shows the process (file operation notification production | generation process) of the attribute process part in a terminal device. It is a figure which shows the list of the attributes provided by file operation. It is a flowchart which shows the process (status display) of the icon display part in a terminal device. It is a figure which shows the example of a display of an icon. It is a figure which shows the structure of the area | region data file stored in the memory | storage part of the terminal device. It is a flowchart which shows the file update process (update process for every area | region) of the file processing part in a terminal device. It is a block diagram which shows the structure of an API server. It is a figure which shows the structure of the update notification stored in the memory | storage part of an API server. It is a flowchart which shows the process of an API server. It is a block diagram which shows the structure of a storage server. It is a figure which shows the structure of the shared folder information stored in the memory | storage part of a storage server. It is a flowchart which shows the process of a storage server. It is a flowchart which shows the process of the operation classification specific | specification part in a storage server. It is a flowchart which shows the process of the file and FI process part in a storage server. It is a flowchart which shows the process of the FI transmission part in a storage server. It is a flowchart which shows the process of the collision process part in a storage server. It is a figure which shows the structure of the area | region data file stored in the memory | storage part of a storage server. It is a flowchart which shows the file update process (update process for every area | region) of the file and FI process part in a storage server. It is a block diagram which shows the structure of an event server. It is a figure which shows the structure of the connection information stored in the memory | storage part of an event server. It is a flowchart which shows the process of an event server. It is a block diagram which shows the structure of a connection server. It is a flowchart which shows the process of a connection server. It is a figure which shows the example of the hierarchical structure of the folder with which the storage server was equipped. It is a figure which shows the structure of a folder index. 6 is a diagram showing a folder index of a folder E. FIG. It is a flowchart which shows the other process of the operation classification specific | specification part in a storage server.

  Hereinafter, embodiments for carrying out the present invention will be described in detail with reference to the drawings. The present invention is characterized in that the file synchronization status is displayed by being added to the icon of the upper folder to which the file belongs. Thus, the user using the terminal device can accurately recognize the state of the file before performing the file operation, and can improve the operability. The present invention is applied to the following file synchronization system, but this file synchronization system is an example, and can be applied to other systems.

  An example of a file synchronization system to which the present invention is applied is a file synchronization system in which a storage server having a plurality of terminal devices and folders accessible by the terminal devices is connected via a network. When establishing synchronization between the file to be operated and the file stored in the folder of the storage server, the attributes of the file are transmitted and received.

  Specifically, when a file operation is performed by a user who uses the terminal device, the terminal device generates an attribute group (attribute data) of the file and transmits it to the storage server. Here, the file attribute group is data in which the file attribute is defined, and is generated by the terminal device. An FI described later is data in which file attributes are defined, and is generated by the storage server. Then, the storage server identifies the type of file operation, performs file processing according to the type of file operation (store new file, update file, delete file, etc.), generates a new FI, and creates this new file. The FI is transmitted to the terminal device on which the file operation has been performed, and the FIs of all the files belonging to the folder are transmitted to the other terminal devices. Thereby, all the terminal devices and storage servers connected to the storage server can hold the same FI corresponding to the same file in the folder, and file synchronization can be established. Therefore, it is not necessary to send and receive files each time a file is operated by the user, and it is sufficient to send and receive files only when necessary. Therefore, file synchronization processing can be realized with low load and high efficiency. It becomes.

  Here, file operations include new file creation, file update, file deletion, file name change, file movement, and file copy. New file creation is an operation of creating a new file in a folder. By this operation, a new file is stored in the folder, and a new FI is generated. The file update is an operation for updating data of a file existing in the folder. By this operation, the file to be updated existing in the file is deleted, and a new update file is stored in the folder. The FI is also updated. The file deletion is an operation for deleting a file existing in the folder. This operation also deletes the FI. The file name change is an operation for changing the name of a file existing in a folder. By this operation, the file name included in the FI is renewed while the file is stored as it is. The file move is an operation for moving a file existing in a folder to another folder. By this operation, the file path included in the FI is renewed while the file is stored as it is. File copy is an operation of creating a new file by copying a file existing in a folder. By this operation, a new file at the copy destination is created with the copy source file as it is, and a new FI for the copy destination file is generated separately from the FI for the copy source file. . Details of the FI will be described later.

[Configuration of file synchronization system]
First, the configuration of the file synchronization system according to the embodiment of the present invention will be described. FIG. 1 is a diagram showing the overall configuration of the file synchronization system. The file synchronization system 10 includes a plurality of terminal devices 1-1, 1-2,..., An API (Application Program Interface) server 2, a storage server 3, an event server 4, and a connection server 5. The plurality of terminal devices 1-1, 1-2,..., The API server 2, the storage server 3, the event server 4, and the connection server 5 are connected via a network 6, respectively. In FIG. 1, only one API server 2, storage server 3, event server 4, and connection server 5 are shown for convenience of explanation, but there may be a plurality of units depending on the scale of the file synchronization system 10. . Further, the API server 2 and the storage server 3 may be configured as a single storage server, and the event server 4 and the connection server 5 may be configured as a single event notification server. The network 6 is a communication network such as the Internet or a LAN (Local Area Network).

  The terminal devices 1-1, 1-2,... (Hereinafter collectively referred to as the terminal device 1) are, for example, personal computers, portable telephones that can be carried by users, PDAs (Personal Digital Assistants), music players. It may be a portable terminal such as a digital camera. When the terminal device 1 is a mobile terminal, the terminal device 1 is connected to the network 6 via a wireless communication network and a relay server. The terminal device 1 is a device used by a user who can access a folder provided in the storage server 3, and logs in to the network 6 constituting the file synchronization system 10 in accordance with a user operation. In addition, the terminal device 1 performs a file operation by the user, and downloads a file in a folder from the storage server 3 or uploads a new file or an updated file to the storage server 3.

  The API server 2 bridges data transmission / reception between the terminal device 1 and the storage server 3 and between the storage server 3 and the event server 4. For example, when the terminal device 1 performs HTTP (HyperText Transfer Protocol) communication using a Web browser, the terminal device 1 performs HTTP communication processing and transfers data to and from the storage server 3.

  The storage server 3 includes a folder that can be accessed by the terminal device 1, and manages the files in the folder and the users who can access the folder. Also, the FI used for file synchronization is managed in association with the files in the folder.

  The event server 4 receives from the connection server 5 and stores information related to the terminal device 1 and the user logged in to the network 6 (information related to the terminal device 1 and the user is referred to as user-specific information). In addition, when the FI stored in the storage server 3 is updated, the event server 4 identifies the notification destination terminal device 1 that notifies the updated event, and displays information indicating that the event has been updated. Information is notified to the terminal device 1 via the connection server 5.

  When the terminal device 1 logs in to the network 6 constituting the file synchronization system 10 by the user, the connection server 5 manages the logged-in user and user-specific information of the connected terminal device 1 as connection information. That is, the connection server 5 manages, as connection information, the user accessing the folder provided in the storage server 3 and the user specific information related to the terminal device 1 used by the user.

[Information flow during file operations]
Next, the flow of information when a file operation is performed by a user using the terminal device 1 in the file synchronization system 10 shown in FIG. 1 will be described. FIG. 2 is a diagram showing a flow of information at the time of file operation. In FIG. 2, the user (user ID: A) uses the terminal device 1-1 (terminal ID: PC-A), and the user (user ID: B) uses the terminal device 1-2 (terminal ID: PC-B). , And the terminal devices 1-1 and 1-2 are connected to the storage server 3 via the API server 2.

(1) Login Information First, when a user using the terminal device 1-1 executes an application program for operating a file in a folder by the file synchronization system 10, the terminal device 1-1 is connected to the network of the file synchronization system 10. Log in to 6. Thereby, login information (user ID: A, terminal ID: PC-A) is transmitted from the terminal device 1-1 to the connection server 5. When a user using the terminal device 1-2 executes a similar application program, the terminal device 1-2 logs in to the network 6 of the file synchronization system 10. Thereby, login information (user ID: B, terminal ID: PC-B) is transmitted from the terminal device 1-2 to the connection server 5. Although not shown, the connection server 5 uses the login information received from the terminal devices 1-1 and 1-2 as connection information from the terminal devices 1-1 and 1-2 to the storage server 3. Send to.

  Also, the terminal devices 1-1 and 1-2 access the storage server 3 via the API server 2, receive the FIs of files belonging to the shared folder via the API server 2, and store them in the shared folder and shared folder. Displays the icon of the file to which it belongs.

(2) (3) File operation notification When a user who uses the terminal device 1-2 designates a file in the shared folder and performs a file operation, the terminal device 1-2 determines from a plurality of attributes about the file. And a file operation notification including the attribute group is transmitted to the API server 2. The attribute group includes a plurality of attributes that differ depending on the type of file operation. When the API server 2 receives the file operation notification from the terminal device 1-2, the API server 2 transmits the received file operation notification to the storage server 3.

  When the storage server 3 receives the file operation notification from the API server 2, the storage server 3 identifies the type of file operation, performs processing according to the type of file operation (store new file, update file, delete file, etc.) A new FI is generated for the file on which the file operation was performed. Then, the storage server 3 updates the notification (event type (updated), shared) to notify the other terminal device 1-1 other than the terminal device 1-2 on which the file operation is performed that the FI has been updated. Information (user ID: A, B), upper folder path (folder to which file operation has been performed), transmission source terminal ID (PC-B)) are generated. Here, the shared information is a user ID of a user who is permitted to access the shared folder, and the upper folder path is a path indicating the location of the folder to which the file on which the file operation is performed belongs. Details of the update notification will be described later.

(4 ') (5') FI
The storage server 3 transmits the generated new FI to the API server 2. Then, the API server 2 transmits the FI received from the storage server 3 to the terminal device 1-2. In this case, the API server 2 receives the terminal ID: PC-B of the terminal device 1-2 on which the file operation is performed together with the FI, thereby determining the FI transmission destination. The terminal device 1-2 receives a new FI from the API server 2.

  FIG. 3 is a diagram for explaining an event notification sequence. This event notification sequence corresponds to the sequence (4) to (13) in FIG. 2 and indicates that the FI has been updated in accordance with the file operation in the terminal device 1-2 (a new FI has been generated). This shows a procedure for notifying the terminal device 1-1 of an event. Hereinafter, a description will be given with reference to FIGS.

(4) (5) Update notification The storage server 3 transmits an update notification to the API server 2. When the API server 2 receives the update notification from the storage server 3, the API server 2 stores the update notification and transmits the update notification to the event server 4.

(6) Update command When the event server 4 receives the update notification, the event server 4 refers to the stored connection information, and shares information (user ID: A, B) and transmission source terminal ID (PC-B) included in the update notification. ) To identify the notification destination terminal device 1-1 (terminal ID: PC-A) that notifies the update event. Then, the event server 4 transmits an update command including a notification destination terminal ID (PC-A), which is a notification destination of the update event, to the connection server 5.

(7) When there is an update When the connection server 5 receives the update command from the event server 4, the connection server 5 transmits information with the update to the terminal device 1-1 that is the notification destination terminal ID (PC-A) included in the update command. Accordingly, the terminal device 1-1 can determine that the file in the shared folder of the storage server 3 has been updated, and performs a process for acquiring a new FI from the storage server 3.

(8) Update information acquisition request Upon receiving updated information from the connection server 5, the terminal apparatus 1-1 acquires the path of the upper folder to which the new FI file belongs prior to acquiring the new FI. In order to do this, an update information acquisition request including its own terminal ID (PC-A) is transmitted to the API server 2.

(9) Host Folder Path When the API server 2 receives the update information acquisition request from the terminal device 1-1, the API server 2 refers to the stored update notification and includes the terminal ID (PC-A) included in the update information acquisition request. Based on the above, the path of the upper folder is specified. Then, the API server 2 transmits the path of the upper folder to the terminal device 1-1. As a result, the terminal device 1-1 can determine the path of the upper folder to which the updated file belongs, and performs processing for obtaining the FIs of all the files belonging to the upper folder. The reason why the FIs of all the files belonging to the upper folder are acquired is that all the FIs include a new FI generated by the file operation in the terminal device 1-2.

(10) (11) FI acquisition request Upon receiving the upper folder path from the API server 2, the terminal device 1-1 acquires the upper folder path in order to acquire the FIs of all the files belonging to the upper folder. The FI acquisition request including this is transmitted to the API server 2. When the API server 2 receives the FI acquisition request from the terminal device 1-1, the API server 2 transmits the received FI acquisition request to the storage server 3. The FIs of all files belonging to the upper folder are FIs of all shared files belonging to the shared folder, and do not include FIs of files other than shared files belonging to the shared folder. This is because the files belonging to the shared folder include not only shared files that can be accessed by a plurality of users but also files that are not shared by a plurality of users and can be accessed only by a specific user. The same applies to the following description.

(12) (13) FI group When the storage server 3 receives the FI acquisition request from the API server 2, the storage server 3 includes all the FIs stored in the storage server 3 based on the path of the upper folder included in the FI acquisition request. From this, the FI of the file belonging to the upper folder is specified, and the FI group is transmitted to the API server 2. When the API server 2 receives the FI group from the storage server 3, the API server 2 transmits the FI group to the terminal device 1-1.

  Thus, the FI newly generated by the storage server 3 in accordance with the file operation in the terminal device 1-2 is transmitted from the storage server 3 to the terminal device 1-2 via the API server 2. Further, information indicating that the FI has been updated (update event) is transmitted to the other terminal device 1-1 via the API server 2, the event server 4, and the connection server 5 by the event notification sequence described above, The FIs (including newly generated FIs) of all files belonging to the shared folder are transmitted to the terminal device 1-1 via the API server 2. Thereby, the terminal devices 1-1 and 1-2 and the storage server 3 can hold the new identical FI, and can establish file synchronization.

  Note that the login information (1) and (7) is performed in non-SSL without using the SSL (Secure Socket Layer) protocol. Among these, the login information (1) is encrypted by Cookie (Ecokie), and the updated information (7) is transmitted / received between the terminal device 1 and the connection server 5 as real data that is not encrypted. Thereby, the processing load in the terminal device 1 and the connection server 5 can be reduced. Various information (5 ') (8) (9) (10) (13) is transmitted and received as encrypted data according to the SSL protocol between the terminal device 1 and the API server 2. This is because it is highly necessary to conceal the data such as the path and FI of the upper folder. Thereby, the information regarding the shared folder, the FI, etc. is concealed, and the security of the information can be ensured.

[Transition of FI during file operations]
Next, the transition of FI in the information flow during file operation shown in FIG. 2 will be described. First, FI will be described in detail. FIG. 4 is a diagram illustrating the configuration of the FI. This FI is composed of a plurality of pieces of information indicating file attributes. Specifically, unique ID: a, file size: b, hash value: c, E tag (Entity tag): d, file name: e, It consists of each attribute of file path: f and update date: g. There is one FI corresponding to one file. The unique ID is a value for uniquely identifying a file, and a different value is assigned to each file. The file size is a value indicating the size of the file, and the hash value is a function value of file data obtained by a hash function. The E tag is a value newly given when a file is operated, and is used to determine a file collision described later. The file name is the name of the file, the file path is an address indicating the location of the file in the folder, and the update date is the date when the FI was newly created or updated. When a new FI is generated, a new unique ID is assigned, and when the FI is updated, the same value as before is used as the unique ID of the FI. For example, when a new file is created or a file is copied, the storage server 3 generates an FI including a new unique ID for the new file or the copy destination file. For example, when a file is updated, an FI including the same unique ID as that before the update is generated for the updated file. Hereinafter, the FI transition will be specifically described in each file operation of new file creation, file update, file deletion, file name change, file movement, and file copy.

(FI when creating a new file)
First, the transition of FI when creating a new file will be described. FIG. 5 is a diagram for explaining the transition of FI when a new file is created. In FIG. 5, the API server 2, the event server 4, the connection server 5, and information transmitted and received by these devices are omitted. The information of (2), (3), (4 ′), (5 ′), (4) to (11), (12), and (13) in FIG. 5 is the same as that shown in FIGS. The same applies to FIGS.

  Further, the terminal device 1-1 (terminal ID: PC-A) used by the user (user ID: A) and the terminal device 1-2 (terminal ID: PC-B) used by the user (user ID: B). Log in to the network 6 of the file synchronization system 10, access the shared folder provided in the storage server 3, and store the FI (β1),..., FI (βn) of all files belonging to the shared folder on the storage server 3. It is acquired from and held. That is, the terminal devices 1-1 and 1-2 hold the same FI (β1),..., FI (βn), respectively. β1 to βn are identifiers for distinguishing individual files for convenience. For example, FI (β1) indicates the FI of the file β1. In FIG. 5, it is assumed that the terminal devices 1-1 and 1-2 display the shared folder icon.

  Here, the user who uses the terminal device 1-2 performs an operation of creating a new file in the shared folder, and completes the operation of creating a new file. Then, the terminal device 1-2 assigns a null unique ID, a file size b1, a hash value c1, a null E tag, a file name e1, a file path f1, and a null update date and time, and an attribute group including these attributes Is generated. Then, the terminal device 1-2 has an attribute group (-, b1, c1,-, e1, f1,-), file data, its own terminal ID (PC-B), and file operation type data (indicating new file creation). A file operation notification including (data) is generated, and file operation notifications (2) and (3) are transmitted to the storage server 3 via the API server 2.

  When the storage server 3 receives the file operation notification from the terminal device 1-2 via the API server 2, the storage server 3 specifies the type of file operation as “create new file”, and creates a new file uploaded from the terminal device 1-2. Store. Then, the storage server 3 assigns the unique IDa2, the E tag d2, and the update date / time g2, and generates and stores a new FI (a2, b1, c1, d2, e1, f1, g2) including these attributes. . Thereby, FI (βz) corresponding to the new file is generated.

  The storage server 3 transmits a new FI (βz) (4 ′) (5 ′) to the terminal device 1-2 via the API server 2. Thereby, the terminal device 1-2 adds FI (βz) to the FI of the file belonging to the shared folder, and holds FI (β1),..., FI (βn), FI (βz).

  In addition, the storage server 3 uses the event notification sequences (4) to (11), (12), and (13) shown in FIGS. 2 and 3 to perform FI (β1), which is the FI group of all files belonging to the shared folder. ..., FI (βn), FI (βz) are transmitted to the terminal device 1-1. Thereby, the terminal device 1-1 holds FI (β1),..., FI (βn), FI (βz) as FIs of the files belonging to the shared folder.

  As described above, a new file is uploaded from the terminal device 1-2 to the storage server 3 via the API server 2 and newly generated by the storage server 3 in accordance with the operation of creating a new file in the terminal device 1-2. The FI (βz) corresponding to the new file is transmitted from the storage server 3 to the terminal device 1-2 via the API server 2. Also, the FI group (including the newly created FI (βz)) of all the files belonging to the shared folder is transmitted to the terminal device 1-1 by the event notification sequence. Thereby, the terminal devices 1-1 and 1-2 and the storage server 3 can hold the new identical FI (βz), and can establish file synchronization.

(FI at the time of file update)
Next, FI transition at the time of file update will be described. FIG. 6 is a diagram for explaining the transition of FI during file update. Similarly to FIG. 5, the terminal apparatuses 1-1 and 1-2 log in to the network 6 of the file synchronization system 10, acquire the FIs of all the files belonging to the shared folder from the storage server 3, and use the same FI (β1 ),..., FI (βn) are held. Here, FI (βn) is composed of a unique IDa, a file size b, a hash value c, an E tag d, a file name e, a file path f, and an update date and time g, and FI (a, b, c, d, e). , F, g).

  Here, the user using the terminal device 1-2 downloads the file of FI (βn) in the shared folder from the storage server 3, performs an operation to update the file, and completes the file update operation. Then, the terminal device 1-2 assigns the file size b1 and the hash value c1, and generates an attribute group (a, b1, c1, d, e, f, g) including these attributes. Then, the terminal device 1-2 includes an attribute group (a, b1, c1, d, e, f, g), file data, its own terminal ID (PC-B), and file operation type data (data indicating file update). ) Including the file operation notification, and the file operation notifications (2) and (3) are transmitted to the storage server 3 via the API server 2.

  When the storage server 3 receives the file operation notification from the terminal device 1-2 via the API server 2, the storage server 3 specifies the file operation type as “file update” and stores the update file uploaded from the terminal device 1-2. . Then, the storage server 3 assigns the E tag d2 and the update date and time g2, and assigns these attributes, the unique IDa of the attribute group included in the received file operation notification, the file size b1, the hash value c1, the file name e, and the file FI (a, b1, c1, d2, e, f, g2) is generated (updated) and overwritten by the path f. Thereby, FI (βn) corresponding to the update file is generated.

  The storage server 3 transmits FI (βn) (4 ′) (5 ′) to the terminal device 1-2 via the API server 2. Thereby, the terminal device 1-2 updates the FI (βn) of the file belonging to the shared folder, and holds FI (β1),... And the updated FI (βn).

  Further, the storage server 3 uses the event notification sequences (4) to (11), (12), and (13) shown in FIGS. 2 and 3 to perform FI (β1), ..., FI (βn) is transmitted to the terminal device 1-1. Thereby, the terminal device 1-1 holds FI (β1),... And the updated FI (βn) as FIs of the files belonging to the shared folder.

  As described above, the update file is uploaded from the terminal device 1-2 to the storage server 3 via the API server 2 and generated (updated) by the storage server 3 in accordance with the file update operation in the terminal device 1-2. The FI (βn) corresponding to the update file is transmitted from the storage server 3 to the terminal device 1-2 via the API server 2. Further, the FI group (including the updated FI (βn)) of all the files belonging to the shared folder is transmitted to the terminal device 1-1 by the event notification sequence. Thereby, the terminal devices 1-1 and 1-2 and the storage server 3 can hold the same updated FI (βn), and can establish file synchronization.

(FI when deleting files)
Next, the transition of FI at the time of file deletion will be described. FIG. 7 is a diagram for explaining the transition of FI when a file is deleted. The terminal devices 1-1 and 1-2 log in to the network 6 of the file synchronization system 10, acquire the FIs of all files belonging to the shared folder from the storage server 3, and use the same FI (β1),. It is assumed that FI (βm) and FI (βn) are held. Here, FI (βn) is composed of a unique IDa, a file size b, a hash value c, an E tag d, a file name e, a file path f, and an update date and time g, and FI (a, b, c, d, e). , F, g).

  Here, the user using the terminal device 1-2 performs an operation of deleting the file of FI (βn) in the shared folder, and completes the file deletion operation. Then, the terminal device 1-2 generates an attribute group (a, b, c, d, e, f, g) using the held attribute of FI (βn), and the attribute group (a, b, c, d, e, f, g), a file operation notification including its own terminal ID (PC-B) and file operation type data (data indicating file deletion), and a file operation notification (2) (3) Is transmitted to the storage server 3 via the API server 2. Also, the terminal device 1-2 deletes FI (βn). Thereby, the terminal device 1-2 holds FI (β1),..., FI (βm) as FIs of the files belonging to the shared folder. The terminal device 1-2 may transmit a file operation notification including the unique IDa, information indicating that a file deletion operation has been performed, and its terminal ID (PC-B).

  When the storage server 3 receives the file operation notification from the terminal device 1-2 via the API server 2, the storage server 3 specifies the type of file operation as “file delete”, deletes the file of FI (βn), and stores the FI βn) is deleted.

  The storage server 3 uses the event notification sequences (4) to (11), (12), and (13) shown in FIGS. 2 and 3 to perform FI (β1), which is the FI group of all files belonging to the shared folder. .., FI (βm) is transmitted to the terminal device 1-1. As a result, the terminal device 1-1 holds FI (β1),..., FI (βm) as FIs of the files belonging to the shared folder.

  Thus, the FI (βn) for the file to be deleted is deleted in the terminal device 1-2 and the storage server 3 in accordance with the file deletion operation in the terminal device 1-2. Also, the FI group (not including the deleted FI (βn)) of all the files belonging to the shared folder is transmitted to the terminal device 1-1 by the event notification sequence. Thereby, the terminal apparatuses 1-1 and 1-2 and the storage server 3 can hold the same FI group that does not include the deleted FI (βn), and can establish file synchronization.

(FI when changing file name)
Next, the transition of the FI when the file name is changed will be described. FIG. 8 is a diagram for explaining the transition of the FI when the file name is changed. Similarly to FIGS. 5 and 6, the terminal devices 1-1 and 1-2 log in to the network 6 of the file synchronization system 10, acquire the FIs of all files belonging to the shared folder from the storage server 3, and the same Assume that FI (β1),..., FI (βn) are held. Here, FI (βn) is composed of a unique IDa, a file size b, a hash value c, an E tag d, a file name e, a file path f, and an update date and time g, and FI (a, b, c, d, e). , F, g).

  Here, the user using the terminal device 1-2 performs an operation of changing the file name of the FI (βn) in the shared folder, and the operation of changing the file name is completed. Then, the terminal device 1-2 assigns the file name e1, generates an attribute group (a, b, c, d, e1, f, g), and generates an attribute group (a, b, c, d, e1, f, g), a file operation notification including its own terminal ID (PC-B) and file operation type data (data indicating a file name change) is generated, and the file operation notifications (2) and (3) are sent to the API server 2 To the storage server 3.

  When the storage server 3 receives the file operation notification from the terminal device 1-2 via the API server 2, the storage server 3 specifies the file operation type as “file name change”. Then, the storage server 3 assigns the E tag d2 and the update date and time g2, and assigns these attributes, the unique IDa of the attribute group included in the received file operation notification, the file size b, the hash value c, the file name e1, and the file FI (a, b, c, d2, e1, f, g2) is generated (updated) and overwritten by the path f.

  The storage server 3 transmits FI (βn) (4 ′) (5 ′) to the terminal device 1-2 via the API server 2. Thereby, the terminal device 1-2 updates the FI (βn) of the file belonging to the shared folder, and holds FI (β1),... And the updated FI (βn).

  Further, the storage server 3 uses the event notification sequences (4) to (11), (12), and (13) shown in FIGS. 2 and 3 to perform FI (β1), ..., FI (βn) is transmitted to the terminal device 1-1. Thereby, the terminal device 1-1 holds FI (β1),... And the updated FI (βn) as FIs of the files belonging to the shared folder.

  As described above, the FI (βn) generated (updated) by the storage server 3 in accordance with the operation of changing the file name in the terminal device 1-2 is transmitted from the storage server 3 via the API server 2 to the terminal device 1-2. Sent to. Further, the FI group (including the updated FI (βn)) of all the files belonging to the shared folder is transmitted to the terminal device 1-1 by the event notification sequence. Thereby, the terminal devices 1-1 and 1-2 and the storage server 3 can hold the same updated FI (βn), and can establish file synchronization.

(FI when moving files)
Next, the transition of FI during file movement will be described. FIG. 9 is a diagram for explaining the transition of FI during file movement. The terminal apparatuses 1-1 and 1-2 log in to the network 6 of the file synchronization system 10, acquire the FIs of all files belonging to the shared folder from the storage server 3, and have the same FI (β1) in the first folder , FI (β2), and the same FI (γ1) in the second folder. Here, FI (β2) is composed of a unique IDa, a file size b, a hash value c, an E tag d, a file name e, a file path f, and an update date and time g, and FI (a, b, c, d, e). , F, g).

  Here, the user who uses the terminal device 1-2 performs an operation of moving the file of FI (β2) belonging to the first folder to the second folder, and the operation of moving the file is completed. Then, the terminal device 1-2 assigns the destination file path f1, generates an attribute group (a, b, c, d, e, f1, g), and generates an attribute group (a, b, c, d, e, f1, g), a file operation notification including its own terminal ID (PC-B) and file operation type data (data indicating file movement) is generated, and the file operation notifications (2) and (3) are sent to the API server. 2 to the storage server 3.

  When the storage server 3 receives the file operation notification from the terminal device 1-2 via the API server 2, the storage server 3 specifies the type of file operation as “file move”. The storage server 3 then assigns the E tag d2 and the update date and time g2, and uses these attributes and the unique IDa, file size b, hash value c, and file name e of the attribute group included in the received file operation notification. , FI (a, b, c, d2, e, f1, g2) is generated (updated) and overwritten.

  The storage server 3 transmits FI (β2) (4 ′) (5 ′) to the terminal device 1-2 via the API server 2. Thereby, the terminal device 1-2 deletes FI (β2) from the first folder, adds FI (β2) to the second folder, holds FI (β1) in the first folder, FI (γ1) and FI (β2) are held in the second folder.

  Further, the storage server 3 uses the event notification sequences (4) to (11), (12), and (13) shown in FIGS. 2 and 3 to determine the FI group of all the files belonging to the first folder in the shared folder. A certain FI (β1) and FI (γ1) and FI (β2) which are FI groups of all files belonging to the second folder are transmitted to the terminal device 1-1. Accordingly, the terminal device 1-1 holds FI (β1) in the first folder and FI (γ1) and FI (β2) in the second folder as FIs of the files belonging to the shared folder.

  In this way, the FI (β2) generated (updated) by the storage server 3 in accordance with the file movement operation in the terminal device 1-2 is transferred from the storage server 3 to the terminal device 1-2 via the API server 2. Sent. Also, the FI group (including the updated FI (β2)) of all files belonging to the first folder that is the file move source and the second folder that is the file move destination is the terminal by the event notification sequence. It is transmitted to the device 1-1. Thereby, the terminal apparatuses 1-1 and 1-2 and the storage server 3 can hold the same FI (β1) in the first folder, and the FI (γ1) and the added same in the second folder. FI (β2) can be held, and file synchronization can be established without moving the actual data file.

(FI during file copy)
Next, the transition of FI during file copying will be described. FIG. 10 is a diagram for explaining the transition of FI during file copying. Similarly to FIG. 9, the terminal devices 1-1 and 1-2 log in to the network 6 of the file synchronization system 10, acquire the FIs of all the files belonging to the shared folder from the storage server 3, and in the first folder Assume that the same FI (β1) and FI (β2) are held, and the same FI (γ1) is held in the second folder. Here, FI (β2) is composed of a unique IDa, a file size b, a hash value c, an E tag d, a file name e, a file path f, and an update date and time g, and FI (a, b, c, d, e). , F, g).

  Here, the user who uses the terminal device 1-2 performs an operation of copying the file of FI (β2) belonging to the first folder to the second folder, thereby completing the file copy operation. Then, the terminal device 1-2 assigns a null unique ID and a copy destination file path f1, generates an attribute group (-, b, c,-, e, f1,-), and generates an attribute group (-, b, c,-, e, f1,-), its own terminal ID (PC-B) and file operation type data (data indicating file copy) are generated, and file operation notification (2) ( 3) is transmitted to the storage server 3 via the API server 2.

  When the storage server 3 receives the file operation notification from the terminal device 1-2 via the API server 2, the storage server 3 specifies the type of file operation as “file copy”. Then, the storage server 3 stores the new file as the copy destination file by copying the copy source file. The copy source file is specified based on a unique ID (not shown) of the copy source file included in the file operation notification. Then, the storage server 3 assigns the unique IDa2, the E tag d2, and the update date / time g2, and uses these attributes and the file size b, hash value c, and file name e of the attribute group included in the received file operation notification. A new FI (a2, b, c, d2, e, f1, g2) is generated and stored as FI (γ2). As a result, the storage server 3 holds the FI (β2) of the copy source file and the FI (γ2) of the copy destination file.

  The storage server 3 transmits FI (γ2) (4 ′) (5 ′) to the terminal device 1-2 via the API server 2. Thereby, the terminal device 1-2 adds FI (γ2) to the second folder, holds FI (β1) and FI (β2) in the first folder, and FI (γ1) in the second folder. , FI (γ2).

  In addition, the storage server 3 uses the event notification sequences (4) to (11), (12), and (13) shown in FIGS. 2 and 3 to determine the FI group of all files belonging to the second folder in the shared folder. A certain FI (γ1) and FI (γ2) are transmitted to the terminal device 1-1. As a result, the terminal apparatus 1-1 holds FI (β1) and FI (β2) in the first folder as FIs of the files belonging to the shared folder, and FI (γ1) and FI (γ2 in the second folder. ).

  In this way, the FI (γ2) newly generated by the storage server 3 in accordance with the file copy operation in the terminal device 1-2 is transmitted from the storage server 3 to the terminal device 1-2 via the API server 2. Is done. Also, the FI group (including the newly generated FI (γ2)) belonging to the second folder that is the file copy destination is transmitted to the terminal device 1-1 by the event notification sequence. As a result, the terminal apparatuses 1-1 and 1-2 and the storage server 3 can hold the same FI (γ2) added in the second folder, and can copy the file without copying the actual data file. Synchronization can be established.

[Terminal device]
Next, the terminal device 1 shown in FIGS. 1 and 2 will be described in detail. FIG. 15 is a block diagram illustrating a configuration of the terminal device 1. The terminal device 1 includes a communication unit 11, a file processing unit 12, and a storage unit 13.

  The communication unit 11 transmits and receives data between the API server 2 and the connection server 5 using a predetermined protocol. As the file synchronization system 10 logs in to the network 6, login information (user ID, terminal ID) is transmitted to the connection server 5. In addition, the communication unit 11 receives information with update from the connection server 5 and outputs the information to the file processing unit 12. In addition, the communication unit 11 receives a file operation notification, an update information acquisition request, and an FI acquisition request from the file processing unit 12 and transmits them to the API server 2, and receives the path and FI of the upper folder from the API server 2 Output to the processing unit 12. Further, the communication unit 11 receives a user selection command from the API server 2 and outputs it to the file processing unit 12, inputs a user selection type from the file processing unit 12, and transmits it to the API server 2.

  The file processing unit 12 includes a file operation unit 121, an attribute processing unit 122, and an icon display unit 123. The file operation unit 121 performs processing related to file operations such as creating a new file, downloading and updating a file from the storage server 3, and deleting the file in accordance with the file operation by the user.

  The attribute processing unit 122 accesses the shared folder provided in the storage server 3 via the communication unit 11 and logs in to the network 6 of the file synchronization system 10 and acquires the FIs of all files belonging to the shared folder. The icon display unit 123 displays the shared folder icon and the file icon. In addition, the attribute processing unit 122 generates an attribute group according to the file operation processing by the file operation unit 121, and stores the attribute group, its own terminal ID, file operation type data (data for specifying the type of file operation), and the like. A file operation notification is generated and output to the communication unit 11.

  The icon display unit 123 receives information about a folder, FI of a file belonging to the folder, and the like from the file operation unit 121 and the attribute processing unit 122, and displays a folder icon and a file icon.

  The storage unit 13 includes an FI, a file, and a region data file. The FI, file, and area data file are stored and read by the file processing unit 12. Since the attributes constituting the FI have already been described with reference to FIG. 4, the description thereof is omitted here. The area data file will be described later. The storage unit 13 stores a new file when creating a new file, and stores a file downloaded from the storage server 3 when updating the file. Also, the file stored in the storage unit 13 is read by the file processing unit 12 and uploaded to the storage server 3 via the communication unit 11.

  Next, the process of the terminal device 1 shown in FIG. 15 will be described. FIG. 16 is a flowchart showing the processing of the terminal device 1. The communication unit 11 of the terminal device 1 determines whether or not the FI has been received from the storage server 3 via the API server 2 (step S1601), and if it is determined that the FI has been received (step S1601: Y), the reception is performed. The FI is output to the file processing unit 12. Then, the attribute processing unit 122 of the file processing unit 12 receives the FI from the communication unit 11, stores it in the storage unit 13, and outputs it to the icon display unit 123. The icon display unit 123 receives the FI from the attribute processing unit 122, and displays a preset shared folder icon and file icon based on the file path included in the FI (step S1602). In addition, when a file download operation is performed by the user, the file operation unit 121 outputs an instruction for downloading the file specified by the user to the communication unit 11. This instruction is transmitted to the storage server 3 via the API server 2, and the file operation unit 121 inputs a file downloaded from the storage server 3 via the API server 2 from the communication unit 11 and stores it in the storage unit 13. (Step S1603). On the other hand, when it determines with the communication part 11 not receiving FI in step S1601 (step S1601: N), it transfers to step S1604.

  The attribute processing unit 122 of the file processing unit 12 determines whether or not the file operation processing has been performed by the file operation unit 121 (step S1604), and determines that the file operation processing has been performed (step S1604: Y). ), An attribute group associated with the file operation is generated (step S1605), a file operation notification including the attribute group, its own terminal ID, file operation type data, and the like is generated and output to the communication unit 11. This file operation notification is transmitted to the storage server 3 via the API server 2 (step S1606). Also, the attribute processing unit 122 is newly created from the storage unit 13 when the file operation performed by the file operation unit 121 is “create new file” or “update file” in accordance with the output of the file operation notification. The file or the updated file is read and output to the communication unit 11. This file is uploaded to the storage server 3 via the API server 2 (step S1607). Further, the attribute processing unit 122 performs processing according to the file operation. For example, when the file operation is file deletion, the FI of the file to be deleted is deleted from the storage unit 13 and the icon display unit 123 is made to delete the icon display of the file. On the other hand, if the attribute processing unit 122 determines in step S1604 that the file operation process is not performed (step S1604: N), the attribute processing unit 122 proceeds to step S1608.

  The communication unit 11 determines whether or not updated information is received from the connection server 5 (step S1608). If it is determined that updated information is received (step S1608: Y), the updated information is displayed. Output to the file processing unit 12. When the attribute processing unit 122 of the file processing unit 12 inputs information with update from the communication unit 11, the attribute processing unit 122 outputs an update information acquisition request to the communication unit 11. This update information acquisition request is transmitted to the API server 2 (step S1609). When the API server 2 receives the update information acquisition request from the terminal device 1, the API server 2 specifies the path of the upper folder to which the file operated by the other terminal device 1 belongs, and transmits the path of the upper folder to the terminal device 1. The processing of the API server 2 will be described later. When the attribute processing unit 122 inputs the path of the upper folder received from the API server 2 from the communication unit 11 (step S1610), the attribute processing unit 122 outputs an FI acquisition request including the path of the upper folder to the communication unit 11. This FI acquisition request is transmitted to the storage server 3 via the API server 2 (step S1611). The FI that is a response to the FI acquisition request is processed in steps S1601 and S1602. On the other hand, if the communication unit 11 determines in step S1608 that the updated information has not been received (step S1608: N), the communication unit 11 proceeds to step S1612.

  Steps S1612 to S1614 show processing at the time of file collision. For example, the terminal device 1 transmits a file operation notification to the storage server 3 via the API server 2 in accordance with the file update operation by the user, and the storage server 3 receives the file operation notification and there is a file collision. Assuming that In this case, the storage server 3 transmits a user selection command to the terminal device 1 (the terminal device 1 that has transmitted the file operation notification) via the API server 2. A file collision occurs when a file operation is performed in the terminal device 1 without the FI generated in the storage server 3 being reflected in the terminal device 1. For example, after the first terminal device 1 and the second terminal device 1 download the same file, the first terminal device 1 is changed from online to offline, and the second terminal device 1 performs file update. When the storage server 3 updates the FI and the file along with the file update, and the first terminal device 1 is changed from offline to online and performs the file update process, the storage server 3 File conflicts occur. That is, when a file update process is performed by the second terminal apparatus 1 and then a file update process is performed by the first terminal apparatus 1, a file collision may occur. Details of the file collision will be described later.

  The communication unit 11 of the terminal device 1 determines whether or not a user selection command has been received from the storage server 3 via the API server 2 (step S1612). If it is determined in step S1612 that the user selection command has been received (step S1612: Y), the communication unit 11 outputs the user selection command to the file operation unit 121 of the file processing unit 12. When the user selection command is input from the communication unit 11, the file operation unit 121 selects a user selection type from among “Save new file”, “Forced overwrite”, “Discard and update latest”, and “Cancel”. Let Then, the file operation unit 121 outputs the user selection type selected by the user to the communication unit 11. This user selection type is transmitted to the storage server 3 via the API server 2 (step S1613). Then, the file operation unit 121 performs processing according to the user selection type (step S1614).

  Here, when “save new file” is selected by the user, the update file is stored in the storage server 3 as a new file. In addition, when “forced overwrite” is selected by the user, the update file is overwritten in the storage server 3. Therefore, in the above example, the file updated by the second terminal device 1 and stored in the storage server 3 is deleted, and the file updated by the first terminal device 1 is stored in the storage server 3. When the user selects “Discard and latest acquisition”, the file operation unit 121 deletes the file stored in the storage unit 13 and the attribute group generated by the attribute processing unit 122. Then, instead of the deleted FI, the file operation unit 121 inputs a new FI transmitted from the storage server 3 (in the above example, the FI generated when the second terminal device 1 updates the file). And stored in the storage unit 13. When “Cancel” is selected by the user, the FI and the update file stored in the storage unit 13 and the attribute group generated by the attribute processing unit 122 are held as they are.

  When the terminal device 1 proceeds from step S1603, step S1607, step S1611, and step S1614, or determines in step S1612 that a user selection command has not been received (step S1612: N), the terminal device 1 ends the process and proceeds to step S1601. Repeat the process.

(FI processing unit / terminal device)
Next, processing (file operation notification generation processing) of the attribute processing unit 122 in the terminal device 1 illustrated in FIG. 15 will be described in detail. FIG. 17 is a flowchart showing the file operation notification generation processing of the attribute processing unit 122, and corresponds to the processing in steps S1604 to S1607 shown in FIG. FIG. 18 is a diagram showing a list of attributes given by file operations. In FIG. 18, attributes given by file operations are underlined, and attributes for which null is set are represented by-. The storage unit 13 of the terminal device 1 stores the FI (unique IDa, file size b, hash value c, E tag d, file name e, file path f, update date / time g) of the file to be operated. (Refer to the attribute of the original FI in FIG. 18).

  The attribute processing unit 122 determines the type of file operation processing performed by the file operation unit 121 (step S1701). If the attribute processing unit 122 determines that the file operation is “create new file”, the attribute processing unit 122 assigns the file size b1, the hash value c1, the file name e1, and the file path f1 (step S1702), and the unique ID, E tag, Null is set in the update date and time, and an attribute group (-, b1, c1,-, e1, f1,-) is generated (see the attribute of "Create new file" in step S1703, FIG. 18). Then, the attribute processing unit 122 generates a file operation notification (attribute group, file data, terminal ID, etc.) including this attribute group, and outputs it to the communication unit 11. This file operation notification is transmitted to the storage server 3 via the API server 2 (step S1704).

  If the attribute processing unit 122 determines that the file operation is “file update”, the attribute processing unit 122 assigns the file size b1 and the hash value c1 (step S1705), and based on the assigned attribute and the held FI attribute, An attribute group (a, b1, c1, d, e, f, g) is generated (see the attribute of “file update” in step S1706 and FIG. 18). Then, the attribute processing unit 122 generates a file operation notification (attribute group, file data, terminal ID, etc.) including this attribute group, and outputs it to the communication unit 11. This file operation notification is transmitted to the storage server 3 via the API server 2 (step S1707).

  If the attribute processing unit 122 determines that the file operation is “file deletion”, the attribute processing unit 122 generates an attribute group using the same attribute as the FI stored in the storage unit 13 (step S1708, “ (See “File Delete” attribute). Then, the attribute processing unit 122 generates a file operation notification (attribute group, terminal ID, etc.) including this attribute group, and outputs it to the communication unit 11. This file operation notification is transmitted to the storage server 3 via the API server 2 (step S1709).

  When the attribute processing unit 122 determines that the file operation is “change file name”, the attribute processing unit 122 assigns the file name e1 (step S1710), and based on the assigned attribute and the held FI attribute, the attribute group ( a, b, c, d, e1, f, g) are generated (refer to the attribute of “file name change” in step S1711, FIG. 18). Then, the attribute processing unit 122 generates a file operation notification (attribute group, terminal ID, etc.) including this attribute group, and outputs it to the communication unit 11. This file operation notification is transmitted to the storage server 3 via the API server 2 (step S1712).

  When the attribute processing unit 122 determines that the file operation is “file move”, the attribute processing unit 122 assigns the destination file path f1 (step S1713), and based on the assigned attribute and the held FI attribute, A group (a, b, c, d, e, f1, g) is generated (see the attribute of “file move” in step S1714, FIG. 18). Then, the attribute processing unit 122 generates a file operation notification (attribute group, terminal ID, etc.) including this attribute group, and outputs it to the communication unit 11. This file operation notification is transmitted to the storage server 3 via the API server 2 (step S1715).

  If the attribute processing unit 122 determines that the file operation is “file copy”, the attribute processing unit 122 assigns the copy destination file path f1 (step S1716), sets the unique ID to null, and assigns the attribute to which the null unique ID is assigned. Based on the held FI attributes, an attribute group (-, b, c,-, e, f1,-) is generated (see the attribute "file copy" in step S1717, FIG. 18). Then, the attribute processing unit 122 generates a file operation notification (attribute group, terminal ID, etc.) including this attribute group, and outputs it to the communication unit 11. This file operation notification is transmitted to the storage server 3 via the API server 2 (step S1718).

[Synchronization status display] (Icon display / terminal unit)
Next, processing in the case where the icon display unit 123 in the terminal device 1 shown in FIG. 15 performs file synchronization status display will be described in detail. FIG. 19 is a flowchart showing processing (status display processing) by the icon display unit 123, and corresponds to the icon display processing in steps S1602, S1603, and S1607 shown in FIG. FIG. 20 is a diagram illustrating a display example of icons. In FIG. 20, (1) to (5) are marks indicating the state of individual files in file synchronization, and the marks are not overlapped with each other within the display range of the folder icon or the file icon. It is arranged at a predetermined position. For example, the mark is composed of pixel values and arrangement coordinates for each pixel. As shown in the upper part of FIG. 20 (6), the icon display unit 123 combines the image of the folder icon with the image in which the marks (1) to (5) are arranged at predetermined positions. The icon is displayed on the screen. The image in which the mark is arranged at the predetermined position is transmitted through the portion other than the mark, and is combined with the folder icon image. Further, as shown in the interruption of FIG. 20 (6), the icon display unit 123 adds and displays all the marks indicating the status of the files belonging to the folder on the folder icon. As shown in the lower part of FIG. 20 (6), the icon display unit 123 adds and displays a mark indicating the state of the file belonging to the folder for each icon of the lower layer folder belonging to the folder. The icon display unit 123 propagates this mark to the upper folder and displays it. That is, when the icon display unit 123 displays the folder to which the file belongs and the icon of the upper folder to which the folder belongs (in the case of using the file as a reference, each icon for the folder in the upper hierarchy). A mark indicating the state of is added to these icons and displayed.

  The icon display unit 123 determines whether or not file uploading has started (step S1901), and when it is determined that uploading has started (step S1901: Y), an up arrow mark (FIG. 20 (1)) is added to the shared folder icon or the like and displayed (step S1902). Thereby, when the mark of the up arrow is added to the shared folder or the like, the user can recognize that any file in the shared folder is being uploaded. On the other hand, if the icon display unit 123 determines in step S1901 that the upload has not started (step S1901: N), the icon display unit 123 proceeds to step S1907. The communication unit 11 monitors the state of uploading files to the storage server 3 via the API server 2, and the icon display unit 123 receives the file upload status (start, failure) from the communication unit 11. And complete) information.

  The icon display unit 123 determines whether the file upload has failed (step S1903). If the icon display unit 123 determines that the upload has failed (step S1903: Y), the icon display unit 123 displays an up arrow and a rain A mark (see FIG. 20B) is added to a shared folder icon or the like and displayed (step S1904). Thereby, when the up arrow and the rain mark are added to the shared folder or the like, the user can recognize that any file in the shared folder has failed to upload. On the other hand, if the icon display unit 123 determines in step S1903 that the upload has not failed (step S1903: N), the icon display unit 123 proceeds to step S1905.

  The icon display unit 123 determines whether or not the file upload has been completed (step S1905). If it is determined that the upload has been completed (step S1905: Y), the icon display unit 123 displays an up arrow mark, an up arrow mark, and a rain mark. The shared folder icon is deleted from the display (step S1906). Thereby, the user can recognize that the upload of any file in the shared folder is completed. On the other hand, if the icon display unit 123 determines in step S1905 that the upload has not been completed (step S1905: N), the icon display unit 123 proceeds to step S1903.

  The icon display unit 123 shifts from step S1901 to determine whether or not the file download has started (step S1907). When it is determined that the download has started (step S1907: Y), the icon display unit 123 displays the downloading state. A downward arrow mark (see FIG. 20 (3)) is added to the icon of the shared folder and displayed (step S1908). As a result, the user can recognize that a file is being downloaded to the shared folder when a down arrow mark is added to the shared folder or the like. On the other hand, if the icon display unit 123 determines in step S1907 that the download has not started (step S1907: N), the icon display unit 123 proceeds to step S1911. The communication unit 11 monitors the state of downloading a file from the storage server 3 via the API server 2, and the icon display unit 123 receives a file download state (start and completion) from the communication unit 11. ) Information.

  The icon display unit 123 determines whether or not the download of the file is completed (step S1909). When it is determined that the download is completed (step S1909: Y), the icon of the shared folder is displayed as a down arrow mark or the like. Is deleted from the display (step S1910). Thereby, the user can recognize that the download of any file in the shared folder is completed. On the other hand, if it is determined in step S1909 that the download has not been completed (step S1909: N), the icon display unit 123 waits until the completion.

  The icon display unit 123 proceeds from step S1907 to determine whether the communication unit 11 has received the FI (step S1911). When the icon display unit 123 determines that the FI has been received (step S1911: Y), the received FI And the attribute group being held (attribute group generated by file operation) are compared to determine the type of file operation (step S1912). Specifically, when the received FI is a FI including a new unique ID, the icon display unit 123 indicates that a file operation such as “create new file” or “file copy” has been performed in another terminal device 1. The file operation type is determined as “new file creation” or “file copy”. Further, the icon display unit 123 identifies a holding attribute group having the same attribute as the unique ID included in the received FI, and determines that the file operation type is “file update” when the file size and the hash value are different. If the file names are different, the file operation type is determined to be “change file name”, and if the file paths are different, the file operation type is determined to be “file move”.

  If the icon display unit 123 determines that the type of file operation is “create new file” or “file copy” in step S 1912, the file operation of “create new file” or “file copy” is performed in the other terminal device 1. A cloud mark (see FIG. 20 (4)) indicating that a new file has not been downloaded is added to the shared folder icon or the like and displayed (step S1913). As a result, when a cloud mark is added to the shared folder or the like, the user creates a new file in the shared folder of the storage server 3 by another terminal device 1 and downloads the file to his / her terminal device 1. You can recognize that it is not.

  If the icon display unit 123 determines in step S 1912 that the type of file operation is “file update”, “file name change”, or “file move”, “file update”, “file name change”, or “file move”. The file mark operation is performed in the other terminal device 1, and the rain mark (see FIG. 20 (5)) indicating that the updated file, the renamed file, or the moved file has not been downloaded is displayed in the shared folder. Is added to the icon or the like and displayed (step S1914). As a result, when a rain mark is added to the shared folder or the like, the user updates or moves the file in the shared folder of the storage server 3 by another terminal device 1 or changes the file name. Can be recognized that the old file is not downloaded to its own terminal device 1 and the old file is stored in its own terminal device 1. Further, the icon display unit 123 deletes the mark displayed in step S1913 and step S1914 when the download of the file related to the mark is completed in step S1910.

  As described above, the icon display unit 123 of the file processing unit 12 in the terminal device 1 displays the mark indicating the file upload, upload failure, and download status (up arrow mark, up arrow mark, rain mark, and down arrow mark). Mark), “new file creation” or “file copy” is performed in the other terminal device 1 and a new file is not downloaded (cloud mark), “file update”, “file” "Name change" or "file move" is performed in another terminal device 1, and a mark (rain mark) indicating that its own terminal device 1 holds an old file is a folder corresponding to each state. Added to the icon and displayed. Thereby, the user recognizes from the mark displayed in addition to the folder icon that his / her terminal device 1 does not hold a new file, or that the held file is old. Can do. Therefore, the user can accurately recognize the state of the file synchronization process. In addition, the icon display unit 123 displays the mark indicating the state of the file on the icon of the folder above the folder. As a result, the user can recognize the status of the folder and file under the displayed folder icon.

  It should be noted that the icon display unit 123 displays, as the file synchronization status, a mark indicating the uploading status (FIG. 20 (1)), a mark indicating the upload failure status (FIG. 20 (2)), and the downloading status. Mark (FIG. 20 (3)), mark (FIG. 20 (4)) indicating that an operation such as “create new file” has been performed, and mark (FIG. 20) indicating that an operation such as “file update” is performed. (5)) is added to the icon and displayed. On the other hand, the icon display unit 123 may collectively display the state of these files. Specifically, the icon display unit 123 displays a mark indicating the uploading state (FIG. 20 (1)) or the mark indicating the downloading state (FIG. 20 (3)). Instead, a mark indicating a state in which file synchronization processing is being performed (synchronized state) is added to the icon and displayed. Further, the icon display unit 123 displays a mark indicating an upload failure state (FIG. 20 (2)), a mark indicating that an operation such as “create new file” (FIG. 20 (4)), or “file update”. When a mark indicating that there has been an operation such as "" (FIG. 20 (5)) is displayed, instead of these marks, a mark indicating that file synchronization processing is not being performed is displayed as an icon. To be displayed. In addition, the icon display unit 123 is displayed by adding a mark indicating the state of the file to the folder icon, but may be displayed by adding it to the file.

[Access via Web browser] (communication unit / terminal device)
Next, processing when the communication unit 11 and the file processing unit 12 in the terminal device 1 illustrated in FIG. 15 access the storage server 3 via the API server 2 according to HTTP by a Web browser will be described in detail.

  FIG. 40 is a diagram illustrating an example of a hierarchical structure of folders provided in the storage server 3. As shown in FIG. 40, the storage server 3 includes folders A to G, and the structure is that the folders B and C belong to the folder A, the folders D and E belong to the folder B, and the folders F and G belong to the folder. The relationship belongs to C. The folders A to G are assigned unique IDs 1 to 7 for uniquely specifying the folder. Assume that the folder E is a shared folder, the file “ddd.txt” belongs to the folder E, and can be accessed by a plurality of users. In this case, the path (folder path) of the folder E is “/ A / B / E”, and the path (file path) of the file “ddd.txt” is “/A/B/E/ddd.txt”. It is.

  FIG. 41 is a diagram showing the structure of a folder index. This folder index is composed of a plurality of pieces of information indicating the attributes of the folder. Specifically, the folder index is composed of attributes of unique ID, folder size, hash value, E tag, folder name, and folder path. There is one folder index corresponding to one folder. The unique ID is a value for uniquely specifying a folder, and different values are assigned to all folders and all files. That is, different values including the unique ID of the FI shown in FIG. The folder size is a value obtained by adding the sizes of all the files belonging to the folder, and the hash value is a function value obtained by a hash function. The E tag is a value newly given when the folder is updated. The folder name is the name of the folder, and the folder path is an address indicating the location of the folder. These attributes correspond to the FI attributes (unique ID, file size, hash value, E tag, file name, file path) shown in FIG. When a new folder is created, a new unique ID and E tag are assigned. When a folder size, a folder name, and the like are changed, a new E tag is assigned.

  FIG. 42 is a diagram showing a folder index of the folder E shown in FIG. As shown in FIG. 42, the folder index of the folder E is as follows: unique ID: 5, folder size: b, hash value: c, E tag: d, folder name: E, and folder path: / A / B / E. Consists of each attribute. Note that the folder index is stored in the storage server 3.

  Here, processing when the terminal device 1 accesses the shared folder E provided in the storage server 3 by a Web browser by an operation of a user who uses the terminal device 1 will be described.

  The terminal device 1 is assumed to have acquired the folder index of the folder E shown in FIG. A user who uses the terminal device 1 designates “http: //....jp/5” as the URL of the folder E. This URL “http: //....jp/5” includes the protocol type “http”, the name (host name) of the storage server 3 “... Jp”, and the unique ID “5” of the folder E. Consists of. Then, the communication unit 11 of the terminal device 1 generates a request including the unique ID “5” in the URL specified by the user by the Web browser, and transmits the request to the API server 2 according to HTTP.

  When the API server 2 receives a request from the terminal device 1 according to HTTP, the API server 2 acquires the unique ID “5” from the request and transmits it to the storage server 3. Upon receiving the unique ID “5” from the API server 2, the storage server 3 searches all folder indexes and FIs using the unique ID “5” as a key, and specifies a folder index having the unique ID “5”. Then, the path “/ A / B / E” (see FIG. 42) included in the specified folder index is read. Then, the storage server 3 accesses the folder E using the read path, acquires information about the folder E (for example, the FIs of all files belonging to the folder E), and sends the information to the terminal device 1 via the API server 2. Send.

  The communication unit 11 receives a response including information related to the folder E from the API server 2 via the Web browser according to HTTP, analyzes the response, acquires information related to the folder E, and outputs the information to the file processing unit 12. Then, the file processing unit 12 inputs information about the folder E and performs processing such as screen display.

  Here, when the unique ID of the folder E is specified as a part of the URL by the user and the request is transmitted, the URL “http: //....jp/5” is displayed on the screen by the Web browser. The That is, the unique ID “5” of the folder E is displayed on the screen, but the file path “/ A / B / E” is not displayed.

  The process described above is the same when accessing a file. It is assumed that the terminal device 1 has acquired the FI of the file “ddd.txt” from the storage server 3. A user who uses the terminal device 1 designates “http: //....jp/a” as the URL of the file “ddd.txt”. “A” is a unique ID of the file “ddd.txt”. Then, the communication unit 11 of the terminal device 1 generates a request including the unique ID “a” in the URL specified by the user by the Web browser, and transmits the request to the API server 2 according to HTTP. Here, the URL “http: //....jp/a” is displayed on the screen according to the designation of the user. That is, the unique ID “a” of the file “ddd.txt” is displayed on the screen, but the file path “/A/B/E/ddd.txt” is not displayed.

  As described above, the communication unit 11 and the file processing unit 12 of the terminal device 1 specify the URL including the file “ddd.txt” or the unique ID (“5” or “a”) of the folder E by the user. Then, a request including a unique ID in the URL is generated and transmitted to the API server 2 according to HTTP. This eliminates the need for the user to specify a URL including the file or folder path (“/A/B/E/ddd.txt” or “/ A / B / E”). It is not displayed on the screen. Therefore, the path information can be reliably concealed and the path information is not known to other users, so that security can be ensured.

[API server]
Next, the API server 2 shown in FIGS. 1 and 2 will be described in detail. FIG. 23 is a block diagram showing the configuration of the API server 2. The API server 2 includes a communication unit 21 and a storage unit 22.

  The communication unit 21 transmits / receives data to / from the terminal device 1, the storage server 3, and the event server 4 using a predetermined protocol. The communication unit 21 receives the file operation notification and the FI acquisition request from the terminal device 1 and transmits them to the storage server 3. The communication unit 21 receives the FI and the update notification from the storage server 3, transmits the FI to the terminal device 1, stores the update notification in the storage unit 22, and transmits it to the event server 4.

  Further, the communication unit 21 receives an update information acquisition request (including the transmission source terminal ID) from the terminal device 1, and the transmission source terminal ID included in the update information acquisition request and the update stored in the storage unit 22. Based on the shared information and the transmission source terminal ID included in the notification, the path of the upper folder included in the update notification is specified, and the path of the upper folder is the terminal having the terminal ID of the transmission source that has transmitted the update information acquisition request Transmit to device 1.

  The storage unit 22 stores an update notification. The update notification is stored and read out by the communication unit 21. The storage unit 22 stores an update notification generated by the storage server 3 at the time of file operation, and responds to update information acquisition requests transmitted from all the terminal devices 1 that have received information with update by the update notification. When the upper folder path is read, the update notification including the upper folder path is deleted by the communication unit 21.

  FIG. 24 is a diagram illustrating the configuration of the update notification stored in the storage unit 22. As described above, the update notification includes the event type (updated), shared information (user ID permitted to access the shared folder to which the file operation has been performed), and the file to which the file operation has been performed. The upper folder path and the source terminal ID (the terminal ID of the terminal device 1 that has transmitted the file operation notification, that is, the terminal ID of the terminal device 1 that has performed the file operation) are configured. Each time the API server 2 receives an update notification from the storage server 3, each update notification is stored in the storage unit 22.

  Next, processing of the API server 2 shown in FIG. 23 will be described. FIG. 25 is a flowchart showing processing of the API server 2. The communication unit 21 of the API server 2 determines whether or not a file operation notification has been received from the terminal device 1 on which the file operation has been performed (step S2501), and determines that the file operation notification has been received (step S2501: Y) A file operation notification is transmitted to the storage server 3 (step S2502). On the other hand, if the communication unit 21 determines in step S2501 that a file operation notification has not been received (step S2501: N), the communication unit 21 proceeds to step S2503.

  The communication unit 21 proceeds from step S2501 to determine whether or not an FI has been received from the storage server 3 (step S2503). When it is determined that the FI has been received (step S2503: Y), the received FI is The terminal device 1 that has transmitted the FI acquisition request or the terminal device 1 on which the file operation has been performed is transmitted (step S2504). On the other hand, when it determines with the communication part 21 not receiving FI in step S2503 (step S2503: N), it transfers to step S2505.

  The communication unit 21 proceeds from step S2503 to determine whether or not an update notification has been received from the storage server 3 (step S2505). When it is determined that an update notification has been received (step S2505: Y), the update notification Is stored in the storage unit 22 (step S2506). In addition, the communication unit 21 transmits the received update notification to the event server 4 (step S2507). On the other hand, when it determines with the communication part 21 not having received the update notification in step S2505 (step S2505: N), it transfers to step S2508.

  The communication unit 21 proceeds from step S2505, determines whether or not an update information acquisition request has been received from the terminal device 1 (step S2508), and determines that an update information acquisition request has been received (step S2508: Y). ), The transmission source terminal ID included in the update information acquisition request, the shared information (user ID) included in the update notification stored in the storage unit 22, and the transmission source terminal ID (of the terminal device 1 on which the file operation was performed). Based on the terminal ID), the path of the upper folder included in the update notification is specified (step S2509). Specifically, the communication unit 21 illustrates the terminal ID of the terminal device 1 used by the user of the user ID from the shared information (user ID) included in the update notification stored in the storage unit 22. Shared folder information (same as shared folder information described later provided in the storage server 3 and acquired from the storage server 3. This shared file information is the user ID of the user accessing the shared folder of the storage server 3. And the terminal ID of the terminal device 1 is a pair of information). Then, for each update notification, the communication unit 21 excludes the transmission source terminal ID (the terminal ID of the terminal device 1 on which the file operation has been performed) included in the update notification from the plurality of terminal IDs corresponding to the shared information, The remaining terminal ID is compared with the terminal ID of the transmission source included in the update information acquisition request. The communication unit 21 then adds the terminal ID of the transmission source (the terminal ID of the terminal device 1 that has transmitted the update information acquisition request) to the remaining terminal ID (the terminal ID of the terminal device 1 that has not performed the file operation). If included, the update notification is assumed to correspond to the update information acquisition request, and the path of the upper folder included in the update notification is specified.

  The communication unit 21 transmits the path of the identified upper folder to the terminal device 1 having the transmission source terminal ID included in the update information acquisition request (step S2510).

  When the communication unit 21 proceeds from step S2508 to determine whether an FI acquisition request has been received from the terminal device 1 (step S2511), and determines that the FI acquisition request has been received (step S2511: Y), An FI acquisition request is transmitted to the storage server 3 (step S2512).

  When the API server 2 shifts from Step S2502, Step S2504, Step S2507, Step S2510, Step S2512 or determines that the FI acquisition request has not been received in Step S2511 (Step S2511: N), the process ends. Then, the process of step S2501 is performed again.

[Storage Server]
Next, the storage server 3 shown in FIGS. 1 and 2 will be described in detail. FIG. 26 is a block diagram showing the configuration of the storage server 3. The storage server 3 includes a communication unit 31, a synchronization control unit 32, and a storage unit 33.

  The communication unit 31 transmits / receives data to / from the API server 2 using a predetermined protocol. The communication unit 31 receives the file operation notification, the FI acquisition request, and the user selection type transmitted by the terminal device 1 from the API server 2 and outputs them to the synchronization control unit 32. Further, the communication unit 31 receives an update notification, FI, and user selection command from the synchronization control unit 32 and transmits them to the API server 2.

  The synchronization control unit 32 includes an operation type identification unit 321, a file / FI processing unit 322, an FI transmission unit 323, and a collision processing unit 324. The operation type identification unit 321 inputs a file operation notification from the communication unit 31 and identifies the type of file operation (operation type) based on the file operation type data included in the file operation notification.

  The file / FI processing unit 322 performs file processing for each operation type specified by the operation type specifying unit 321, stores the file in the storage unit 33 according to the operation type, and sets a new file for the file that has been processed. A new FI is generated and stored in the storage unit 33.

  The FI transmission unit 323 outputs the new FI generated by the file / FI processing unit 322 to the communication unit 31. Also, the FI transmission unit 323 transmits the event type (updated), the path of the upper folder to which the file processed by the file / FI processing unit 322 belongs, the shared information (user ID) of the upper folder, and the file operation notification. An update notification including the terminal ID (source terminal ID) of the terminal device 1 has been generated and output to the communication unit 31. In addition, the FI transmission unit 323 receives the FI acquisition request from the communication unit 31, reads out the FIs of all the files belonging to the upper folder from the storage unit 33 based on the path of the upper folder included in the FI acquisition request, Output to the communication unit 31.

  The collision processing unit 324 is based on the E tag of the attribute group included in the file operation notification from the terminal device 1 input from the communication unit 31 by the operation type specifying unit 321 and the E tag of the FI read from the storage unit 33. When it is determined whether or not there is a file collision, and when it is determined that there is a file collision, a user selection command is output to the communication unit 31. In addition, the collision processing unit 324 receives a user selection type from the communication unit 31 and performs processing according to the user selection type.

  The storage unit 33 stores files, FIs about files, shared folder information, and area data files. These pieces of information are stored and read out by the synchronization control unit 32.

  FIG. 27 is a diagram illustrating a configuration of shared folder information stored in the storage unit 33. In the shared folder information, information about users who can access the shared folder is defined. As shown in FIG. 27, the shared folder information includes a path of the shared folder and a user ID of a user who can access the shared folder. The area data file stored in the storage unit 33 will be described later.

  Next, processing of the storage server 3 shown in FIG. 26 will be described. FIG. 28 is a flowchart showing the processing of the storage server 3. When the communication unit 31 of the storage server 3 receives the file operation notification transmitted by the terminal device 1, the communication unit 31 outputs the file operation notification to the operation type specifying unit 321 of the synchronization control unit 32, and the operation type specifying unit 321 Based on the file operation type data included in the notification, an operation type indicating the type of file operation is specified (step S2801). As described above, the operation types include new file creation, file update, file deletion, file name change, file movement, and file copy.

  The collision processing unit 324 compares the E tag of the attribute group included in the file operation notification with the E tag of the FI having the same unique ID as the attribute group included in the file operation notification read from the storage unit 33. It is determined whether or not there is a file collision (step S2802). When the E tags are different, the collision processing unit 324 determines that there is a file collision (step S2803: present), and performs a collision process (step S2807). On the other hand, when the E tag is the same, the collision processing unit 324 determines that there is no file collision (step S2803: NO), and proceeds to step S2804.

  The file / FI processing unit 322 shifts from step S2803 to file processing corresponding to the operation type specified in step S2801 (for example, processing for storing a new file in the storage unit 33, deleting a file from the storage unit 33) (Step S2804). Then, the file / FI processing unit 322 adds an E tag, an update date / time, and the like for the file subjected to the file processing in step S2804, generates a new FI, and stores it in the storage unit 33 (step S2805). Then, the FI transmission unit 323 performs processing for transmitting the new FI generated in step S2805 to the terminal device 1 (step S2806).

(Operation type identification unit / storage server)
Next, processing of the operation type identification unit 321 in the storage server 3 illustrated in FIG. 26 will be described in detail. FIG. 29 is a flowchart showing the process of the operation type identification unit 321 and corresponds to the process of step S2801 shown in FIG.

  The operation type identification unit 321 inputs the file operation notification transmitted from the terminal device 1 from the communication unit 31 (step S2901), and acquires file operation type data from the file operation notification (step S2902). Then, the operation type specifying unit 321 specifies the operation type based on the file operation type data (steps S2903 to S2909).

  The operation type specifying unit 321 may specify the operation type based on an attribute group included in the file operation notification.

  FIG. 43 is a flowchart showing another process of the operation type identification unit 321 (a process of identifying an operation type based on an attribute group included in the file operation notification). The operation type identification unit 321 inputs the file operation notification transmitted from the terminal device 1 from the communication unit 31 (step S4301), and acquires an attribute group from the file operation notification (step S4302). Then, the operation type identification unit 321 determines whether or not data exists in the unique ID, E tag, and update date / time included in the attribute group (null is set) (step S4303), and no data exists. (Step S4303: Y), the operation type is specified as “create new file” (step S4304). On the other hand, if the operation type identification unit 321 determines in step S4303 that data exists in any of the unique ID, the E tag, and the update date (step S4303: N), the operation type identification unit 321 proceeds to step S4305.

  The operation type identification unit 321 moves from step S4303 to determine whether or not data exists in the unique ID included in the attribute group (null is set) (step S4305). If it is determined (step S4305: Y), the operation type is specified as “file copy” (step S4306). On the other hand, if the operation type identification unit 321 determines in step S4305 that data exists in the unique ID (step S4305: N), the operation type identification unit 321 proceeds to step S4307.

  The operation type identification unit 321 moves from step S4305, acquires a unique IDa (assuming that the attribute group includes a unique IDa) from the attribute group, and reads the FI having the unique IDa from the storage unit 33 ( Step S4307). The FI attributes read from the storage unit 33 are (unique IDa, file size b, hash value c, E tag d, file name e, file path f, update date and time g). That is, the terminal device 1 has generated an attribute group by performing a file operation on the FI file stored in the storage unit 33 of the storage server 3 by the user.

  The operation type identification unit 321 compares the attribute group from the terminal device 1 with the FI read from the storage unit 33 (step S4308), and identifies the operation type. The operation type identification unit 321 compares the file size b1 included in the attribute group with the file size b included in the FI, and compares the hash value c1 included in the attribute group with the hash value c included in the FI ( (Step S4309) When it is determined that the two attributes are different (step S4309: Y), the operation type is specified as “file update” (step S4310). On the other hand, if the operation type identification unit 321 determines in step S4309 that the two attributes are not different (any attribute or the two attributes are the same) (step S4309: N), the operation type identification unit 321 proceeds to step S4311. .

  The operation type identification unit 321 compares each attribute ag included in the attribute group with each attribute ag included in the FI (step S4311), and determines that all attributes are the same (step S4311). S4311: Y), the operation type is specified as “file deletion” (step S4312). On the other hand, if the operation type identification unit 321 determines in step S4311 that all attributes are not the same (any attribute is different) (step S4311: N), the operation type identification unit 321 proceeds to step S4313.

  The operation type identification unit 321 compares the file name e1 included in the attribute group with the file name e included in the FI (step S4313), and determines that the attributes of the file names are different (step S4313: Y). The type is specified as “file name change” (step S4314). On the other hand, if the operation type identification unit 321 determines in step S4313 that the attributes of the file names are not different (same) (step S4313: N), the operation type identification unit 321 proceeds to step S4315.

  The operation type identification unit 321 compares the file path f1 included in the attribute group with the file path f included in the FI (step S4315), and determines that the file path attribute is different (step S4315: Y). The type is specified as “file move” (step S4316).

  The operation type identification unit 321 transitions from step S4304, step S4306, step S4310, step S4312, step S4314, step S4316, or when it is determined in step S4315 that the file path attributes are not different (same) ( Step S4315: N), the process is terminated, and the process of step S4301 is performed again.

(File / FI processing unit / Storage server)
Next, the processing of the file / FI processing unit 322 in the storage server 3 shown in FIG. 26 will be described in detail. FIG. 30 is a flowchart showing the processing of the file / FI processing unit 322, and corresponds to the processing of step S2804 and step S2805 shown in FIG.

  The file / FI processing unit 322 determines the operation type specified by the operation type specifying unit 321 (step S3001). As described above, the FI read from the storage unit 33 is defined as FI (a, b, c, d, e, f, g).

  When the operation type is “create new file”, the attribute group from the terminal device 1 is FI (−, b1, c1, −, e1, f1, −). In this case, the file / FI processing unit 322 uploads a newly created file from the terminal device 1 on which the file operation has been performed, and stores the new file in the storage unit 33 (step S3002). The file / FI processing unit 322 adds the E tag d2 and the update date / time g2 (step S3003), and also assigns a unique IDa2 for uniquely specifying the file stored in the storage unit 33 (step S3004). Then, the file / FI processing unit 322 calculates a new FI (a2, b1, c1, d2, e1, f1, g2) for the file stored in the storage unit 33 based on the assigned attribute and the attribute included in the attribute group. Generated and stored in the storage unit 33 (step S3005).

  When the operation type is “file update”, the attribute group from the terminal device 1 is FI (a, b1, c1, d, e, f, g). In this case, the file / FI processing unit 322 uploads the updated file from the terminal device 1 on which the file operation is performed, and deletes the original file (the file having the same unique IDa as the attribute group) from the storage unit 33. The uploaded update file is stored in the storage unit 33 (step S3006). Then, the file / FI processing unit 322 assigns the E tag d2 and the update date / time g2 (step S3007), and uses the FI (a) for the update file stored in the storage unit 33 from the assigned attribute and the attribute included in the attribute group. , B1, c1, d2, e, f, g2) are generated and overwritten on the storage unit 33 (step S3008). That is, the generated FI (a, b1, c1, d2, e, f, g2) is overwritten on the original FI (a, b, c, d, e, f, g).

  When the operation type is “delete file”, the attribute group from the terminal device 1 is FI (a, b, c, d, e, f, g). In this case, the file / FI processing unit 322 deletes the file (the file having the same unique IDa as the attribute group) from the storage unit 33 (step S3009). Then, the file / FI processing unit 322 deletes the FI having the same attribute as the attribute group from the storage unit 33 (step S3010).

  When the operation type is “change file name”, the attribute group from the terminal device 1 is FI (a, b, c, d, e1, f, g). In this case, the file / FI processing unit 322 assigns the E tag d2 and the update date / time g2 (step S3011), and calculates FI (a, b, c, d2, e1, f, g2) is generated and overwritten on the storage unit 33 (step S3012). That is, the generated FI (a, b, c, d2, e1, f, g2) is overwritten on the original FI (a, b, c, d, e, f, g).

  When the operation type is “file move”, the attribute group from the terminal device 1 is FI (a, b, c, d, e, f1, g). In this case, the file / FI processing unit 322 assigns the E tag d2 and the update date / time g2 (step S3013), and the FI (a, b, c, d2, e, f1, g2) are generated and overwritten in the storage unit 33 (step S3014). That is, the generated FI (a, b, c, d2, e, f1, g2) is overwritten on the original FI (a, b, c, d, e, f, g).

  When the operation type is “file copy”, the attribute group from the terminal device 1 is FI (−, b, c, −, e, f1, −). In this case, the file / FI processing unit 322 copies the copy source file and stores it in the storage unit 33 as a new file (step S3015). The copy source file is specified based on a unique ID (not shown) of the copy source file included in the file operation notification. Then, the file / FI processing unit 322 adds the E tag d2 and the update date / time g2 (step S3016), and also assigns a unique IDa2 for uniquely specifying a new file stored in the storage unit 33 (step S3017). ). Then, the file / FI processing unit 322 determines a new FI (a2, b, c, d2, e, f1, g2) for the new file stored in the storage unit 33 from the attribute included in the assigned attribute and the attribute group. ) And is stored in the storage unit 33 (step S3018).

(FI transmitter / storage server)
Next, processing of the FI transmission unit 323 in the storage server 3 illustrated in FIG. 26 will be described in detail. FIG. 31 is a flowchart showing the processing of the FI transmission unit 323, and corresponds to the processing of step S2806 shown in FIG.

  The FI transmission unit 323 outputs the FI generated by the file / FI processing unit 322 to the communication unit 31. This FI is transmitted via the API server 2 to the terminal device 1 that has transmitted the file operation notification (step S3101). Thereby, the terminal device 1 can hold the same FI as the FI generated by the file / FI processing unit 322 of the storage server 3 and stored in the storage unit 33.

  The FI transmission unit 323 displays the path of the upper folder to which the file operated file belongs to the file path included in the FI generated by the file / FI processing unit 322 (file indicating the location of the file operated file). Based on (path), it identifies (step S3102). When the operation type is “file move”, the FI transmission unit 323 also specifies the path of the upper folder to which the file before the move belongs. Specifically, the file / FI processing unit 322 reads the FI having the same unique IDa as the attribute group included in the file operation notification from the storage unit 33 before overwriting the FI in step S3014 shown in FIG. The transmission unit 323 acquires the file path f (file path indicating the location of the file before the movement) included in the FI read by the file / FI processing unit 322, and based on the file path f, the file path f before the movement is acquired. Specify the path of the upper folder to which the file belongs.

  The FI transmission unit 323 reads the shared folder information from the storage unit 33, and identifies the user ID corresponding to the upper folder path identified in step S3102 (step S3103). The specified user ID is used as shared information.

  The FI transmission unit 323 includes the event type (updated), the shared information (user ID) identified in step S3103, the path of the upper folder identified in step S3102, and the terminal ID of the terminal device 1 that has transmitted the file operation notification. An update notification including (source terminal ID) is generated (step S3104). Thereby, the event notification sequence shown in FIG. 3 is performed.

  The FI transmission unit 323 transmits an update notification to the API server 2 (step S3105). The FI transmission unit 323 is included in the terminal device 1 (the terminal device 1 that has not transmitted the file operation notification among the terminal devices 1 connected to the storage server 3 via the API server 2), that is, included in the update notification. From the communication unit 31, an FI acquisition request received from the terminal device 1 used by the user of the shared information (user ID) to be received via the API server 2 from the terminal device 1 that has not transmitted the file operation notification is received. Input (step S3106).

  The FI transmission unit 323 refers to the file path of the FI stored in the storage unit 33 based on the path of the upper folder included in the FI acquisition request, and stores the FIs of all the files belonging to the upper folder. (Step S3107). Then, as a response to the FI acquisition request, the FI transmission unit 323 sends the FIs of all the files belonging to the upper folder to the terminal device 1 via the API server 2 (the terminal device 1 that has transmitted the FI acquisition request in step S3106). ) (Step S3108). Accordingly, the terminal device 1 that has transmitted the FI acquisition request can hold the same FI as the FI stored in the storage unit 33 of the storage server 3.

[Collision Processing] (Collision Processing Unit / Storage Server)
Next, the process of the collision processing unit 324 in the storage server 3 illustrated in FIG. 26 will be described in detail. FIG. 32 is a flowchart showing the processing of the collision processing unit 324, which corresponds to the processing of step S2802, step S2803, and step S2807 shown in FIG. Corresponding to the processing of the collision processing unit 324, processing by the communication unit 11 in the terminal device 1 and the file operation unit 121 of the file processing unit 12 is performed as shown in steps S1612 to S1614 in FIG.

  A file collision occurs when a file operation is performed in the terminal device 1 without the FI generated in the storage server 3 being reflected in the terminal device 1. For example, after the first terminal device 1 and the second terminal device 1 download the same file, the first terminal device 1 is changed from online to offline, and the second terminal device 1 performs file update. When the storage server 3 updates the FI and the file along with this file update, and the first terminal device 1 is changed from offline to online and performs the file update process, the storage server 3 File conflict occurs.

  11, 12 and 13 are diagrams for explaining the sequence at the time of file collision. The terminal devices 1-1 and 1-2 acquire the FI of the same file by acquiring the FI of the same file from the storage server 3 and downloading the file. Here, it is assumed that FI (a, b, c, d, e, f, g). Hereinafter, the process of the collision processing unit 324 illustrated in FIG. 32 will be described using the sequences of FIGS. 11, 12, and 13.

  It is assumed that the terminal device 1-1 is changed from online to offline, and the user has performed a file update operation in the terminal device 1-2. Then, the terminal device 1-2 generates an attribute group (a, b1, c1, d, e, f, g) (not shown), and sends a file operation notification including this attribute group to the storage server 3. To do. The operation type specifying unit 321 of the synchronization control unit 32 in the storage server 3 inputs the file operation notification received from the terminal device 1-2 from the communication unit 31, and the operation type is “file update” by the process shown in FIG. To be specific.

  The collision processing unit 324 compares the E tag d included in the attribute group with the E tag d included in the FI (step S3201), determines that the E tag d is the same (step S3201: Y), and file collision The absence is determined (step S3202). Then, the update file is uploaded from the terminal device 1-2, and the update file is stored in the storage unit 33 as the file x. Also, FI (a, b1, c1, d2, e, f, g2) for the file x is generated, stored in the storage unit 33, and transmitted to the terminal device 1-2. Note that since the terminal device 1-1 is offline, an event with update due to the update notification is not notified to the terminal device 1-1. At this time, the terminal device 1-2 and the storage server 3 hold the same FI (a, b1, c1, d2, e, f, g2) and the file x of this FI, and the terminal device 1-1 , The FI (a, b, c, d, e, f, g) before update and the file before update are held.

  It is assumed that a file update operation is performed by the user in the terminal device 1-1 and the terminal device 1-1 is changed from offline to online. It is assumed that the file y is generated by updating and the attribute group (a, b3, c3, d, e, f, g) is generated. Then, the terminal device 1-1 transmits a file operation notification including this attribute group (a, b3, c3, d, e, f, g) to the storage server 3. The operation type specifying unit 321 of the synchronization control unit 32 in the storage server 3 inputs the file operation notification received from the terminal device 1-1 from the communication unit 31, and sets the operation type to “file update” by the process shown in FIG. To be specific.

  The collision processing unit 324 compares the E tag d included in the attribute group with the E tag d2 included in the FI (step S3201), determines that the E tags are different (step S3201: N), and determines that there is a file collision. (Step S3203). Then, the collision processing unit 324 determines whether or not both the operation type in the terminal device 1-2 and the operation type in the terminal device 1-1 are “file update” (step S3204). In the case of this example, it is determined that the operation type in the terminal devices 1-1 and 1-2 is “file update” (step S3204: Y), that is, after the file update by the terminal device 1-2 is performed, The file update by the terminal device 1-1 is performed, and it is determined that there is a file collision state, and a collision avoidance process at the time of file update is performed. The collision processing unit 324 outputs a user selection command to the communication unit 31. This user selection command is transmitted via the API server 2 to the terminal device 1-1 that has transmitted the file operation notification (step S3205). As a result, the terminal device 1-1 receives the user selection command, and selects “Save New File”, “Forced Overwrite”, “Discard Latest Update”, and “Cancel” as shown in Step S1613 of FIG. Thus, the user selection type is transmitted to the storage server 3 via the API server 2.

  The collision processing unit 324 inputs the user selection type received from the terminal device 1-1 from the communication unit 31, and determines the user selection type (steps S3206 and S3207). As illustrated in FIG. 12A, when the collision processing unit 324 determines the user selection type “new file storage”, the file y is uploaded from the terminal device 1-1 and stored in the storage unit 33 as a new file. (Step S3208). Then, the collision processing unit 324 assigns the E tag d4 and the update date / time g4 (step S3209), assigns the unique IDa4 for specifying the file y, and also assigns the file name e4 (step S3210). Then, the collision processing unit 324 generates a new FI (1) FI (a4, b3, c3, d4, e4, f, g4), and stores it in the storage unit 33 (step S3211). Then, the collision processing unit 324 transmits the new FI (1) and the FI of the file x updated by the terminal device 1-2 to the terminal device 1-1 that has transmitted the file operation notification (step S3212). Further, the collision processing unit 324 transmits FI (1) and FI to the terminal device 1-2 by the event notification sequence shown in FIG.

  As described above, when the collision processing unit 324 of the storage server 3 determines that there is a file collision by updating the files of the terminal devices 1-1 and 1-2, the file y updated later in addition to the file x updated earlier. Is also stored in the storage unit 33, and FI and FI (1) are transmitted to the terminal devices 1-1 and 1-2. As a result, the terminal apparatuses 1-1 and 1-2 and the storage server 3 can respectively hold the FI of the file x updated earlier and the FI (1) of the file y updated later, and establish file synchronization. be able to. That is, the file synchronization system 10 can manage different files x and y generated by updating the same file, and the user can update the file y updated in the terminal device 1-1 and the terminal device 1-2. The file x updated in step 1 is not lost.

  As illustrated in FIG. 12B, when the collision processing unit 324 determines the user selection type “forced overwrite”, the file y is uploaded from the terminal device 1-1 and the original file is deleted from the storage unit 33. The uploaded file y is stored in the storage unit 33 as a new file (step S3213). Then, the collision processing unit 324 adds the E tag d4 and the update date and time g4 (step S3214), generates FI (a, b3, c3, d4, e, f, g4), and overwrites the storage unit 33 ( Step S3215). Then, the collision processing unit 324 transmits the generated FI to the terminal device 1-1 that has transmitted the file operation notification (step S3212). Further, the collision processing unit 324 transmits the generated FI to the terminal device 1-2 by the event notification sequence illustrated in FIG.

  As described above, when the collision processing unit 324 of the storage server 3 determines that there is a file collision by updating the files of the terminal devices 1-1 and 1-2, the previously updated file x is deleted from the storage unit 33, The file y updated later is stored in the storage unit 33, and the FI of the file y is transmitted to the terminal devices 1-1 and 1-2. Thereby, the terminal devices 1-1 and 1-2 and the storage server 3 can each hold the FI of the file y updated later, and can establish file synchronization. That is, the file synchronization system 10 can manage the file y updated later.

  As shown in FIG. 13 (3), when the collision processing unit 324 determines the user selection type “discard and latest acquisition”, the FI (a, b1, c1, d2, e, f, g2) of the file x Is transmitted to the terminal device 1-1 that has transmitted the file operation notification (step S3212).

  As described above, when the collision processing unit 324 of the storage server 3 determines that there is a file collision by updating the files of the terminal devices 1-1 and 1-2, the FI of the file x that has been updated first is used as the terminal device 1-1. Was sent to. As a result, the terminal apparatuses 1-1 and 1-2 and the storage server 3 can each hold the FI of the file x updated previously, and can establish file synchronization. That is, the file synchronization system 10 can manage the previously updated file x.

  As illustrated in FIG. 13 (4), when the collision processing unit 324 determines the user selection type “cancel”, the collision processing unit 324 ends the process illustrated in FIG. 32 without performing the process.

  As described above, the collision processing unit 324 of the storage server 3 is configured not to perform processing when it is determined that there is a file collision by updating the files of the terminal devices 1-1 and 1-2. Thereby, the terminal device 1-2 and the storage server 3 can each hold FI of the file x updated previously, and can establish file synchronization. Also, the terminal device 1-1 holds the file y and FI (a, b3, c3, d, e, f, g) when the file operation notification is transmitted as they are.

  As described above, the collision processing unit 324 of the synchronization control unit 32 in the storage server 3 holds the E tag included in the received file operation notification attribute group and the storage unit 33 of the storage server 3. The E tag included in the FI is compared, and if the E tag is different, it is determined that there is a file collision. In addition to the file x updated earlier, the file y updated later is stored in the storage unit 33, and the file x FI (1) for file FI and file y is transmitted to the terminal device 1. As a result, the file collision is reliably adjusted, and the terminal device 1 and the storage server 3 can hold the same FI, so that file synchronization can be established. Never lose track of your files. In other words, in the terminal device 1-2 that has performed the file operation first and the terminal device 1-1 that has performed the file operation later, the file updated in the terminal device 1 is stored in the storage server 3 and other terminal devices. Since the file updated in 1 is also stored in the storage server 3, the file conflict is resolved, and the user who operates each terminal device 1-1, 1-2 does not lose sight of the file. As described above, when the terminal device 1-2 is connected to the storage server 3 and the terminal device 1-1 is not connected to the storage server 3, the storage device 3 is updated with the file update in the terminal device 1-2. And the attribute group transmitted to the storage server 3 along with the file update in the terminal device 1-1 when the terminal device 1-1 is connected to the storage server 3 later. It is determined that there is a collision. Then, the storage server 3 stores two FI and FI (1) and two files x and y. Thereby, file collision is eliminated and the user who operates each terminal device 1-1, 1-2 does not lose sight of the file.

  If the collision processing unit 324 determines in step S3204 that the operation type in the terminal devices 1-1 and 1-2 is not “file update” (step S3204: N), the collision avoidance process associated with another operation is performed. Is performed (step S3216). For example, in the terminal devices 1-1 and 1-2 shown in FIG. 11, when the operation in the terminal devices 1-1 and 1-2 is both “file move”, the previous operation by the terminal device 1-2 is “ When the file operation is “file move” and the subsequent operation by the terminal device 1-1 is “file update”, or the previous operation by the terminal device 1-2 is “file name change” and the subsequent operation by the terminal device 1-1 is In the case of “file name change” or when the previous operation by the terminal device 1-2 is “file deletion” and the subsequent operation by the terminal device 1-1 is “file update”, the file operation is performed first. In the terminal device 1-2 and the terminal device 1-1 that has operated the file later, the file updated in its own terminal device 1 is stored in the storage server 3, and the file updated in the other terminal device 1 is also It is stored in the tray di server 3. At this time, as in the case where the operation type in the terminal devices 1-1 and 1-2 is “file update”, the collision processing unit 324 transmits a user selection command to the terminal device 1-1, and selection by the user. May be accepted.

[File update for each divided area]
Next, a file update process performed for each area obtained by dividing a file into predetermined sizes when uploading the file will be described. FIG. 14 is a diagram for explaining a sequence in the case of updating a file for each area.

(File update for each area / file operation unit / terminal device)
First, the processing of the file processing unit 12 in the terminal device 1 will be described with reference to FIG. FIG. 22 is a flowchart illustrating a process when the file processing unit 12 of the terminal device 1 performs file update for each region. The storage unit 33 of the storage server 3 stores a predetermined file and FI (a, b, c (1),..., C (5), d, e, f, g) of the file. And The hash values c (1),..., C (5) are values corresponding to area data in an area obtained by dividing a predetermined file into a predetermined size.

  The file operation unit 121 of the file processing unit 12 in the terminal device 1-2 receives FI (a, b, c (1),..., C (5), d, e, f, g), the file is downloaded (step S2201), and hash values c (1),..., for each area number (area numbers 1,..., 5) obtained by dividing the file into predetermined sizes. c (5) and the area data are stored in the area data file of the storage unit 13 (step S2202).

  FIG. 21 is a diagram illustrating a configuration of the area data file stored in the storage unit 13 of the terminal device 1. As shown in FIG. 21, the area data file is composed of a hash value and area data for each area number.

  Here, it is assumed that the file update operation is performed by the user, and only the area data of area number 3 in the file is updated (step S2203: Y). Then, the file operation unit 121 assigns the hash value c1 (3) to the updated region data of the region number 3, and stores the hash value c1 (3) and the updated region data corresponding to the region number 3 in the storage unit. 13 area data files are stored (step S2204).

  The attribute processing unit 122 assigns the file size b1 (step S2205), and the hash values c (1), c (2), c1 (3), c (4), c (5) from the area data file in the storage unit 13. ) Is read (step S2206), and attribute groups (a, b1, c (1), c (2), c1 (3), c (4), c (5), d, e, f, g) are generated. (Step S2207).

  The attribute processing unit 122 outputs a file operation notification including the attribute group generated in step S2207 and the terminal ID (PC-B) of the terminal device 1-2 to the communication unit 11. This file operation notification is transmitted to the storage server 3 via the API server 2 (step S2208). Thereby, the storage server 3 receives the file operation notification, specifies the operation type as “file update”, specifies the area number 3 in which the area data has been updated, and issues an area data transmission command including the area number 3, It transmits to the terminal device 1-2 via the API server 2.

  The file operation unit 121 inputs the region data transmission command received from the storage server 3 via the API server 2 from the communication unit 11 (step S2209), and is included in the region data transmission command from the region data file in the storage unit 13. The hash value c1 (3) and area data of area number 3 are read (step S2210), and an area data response including the area number 3, hash value c1 (3) and area data is generated and output to the communication unit 11. This area data response is transmitted to the storage server 3 via the API server 2 (step S2211). As a result, the storage server 3 receives the area data response, integrates the area data, stores it in the storage unit 33, and performs normal file update processing. Details will be described later.

(File update per area / file / FI processing unit / storage server)
Next, processing of the file / FI processing unit 322 in the storage server 3 will be described with reference to FIG. FIG. 34 is a flowchart showing processing when file update is performed for each area by the file / FI processing unit 322 of the storage server 3.

  FIG. 33 is a diagram showing the configuration of the area data file stored in the storage unit 33 of the storage server 3. As shown in FIG. 33, the area data file is configured for each unique ID for specifying a file, and includes a hash value and area data for each area number. Assume that the storage unit 33 stores hash values c (1),..., C (5) and area data for each area number for the file with the unique IDa.

  When the operation type specifying unit 321 of the synchronization control unit 32 in the storage server 3 specifies “file update” based on the file operation notification received from the terminal device 1-2 (step S3401: Y), the file The FI processing unit 322 compares the hash value of the attribute group included in the file operation notification with the hash value of the FI having the same unique ID stored in the storage unit 33 of the storage server 3, and the different hash value c1 (3 ) Is selected and area number 3 is specified (step S3402).

  The file / FI processing unit 322 generates a region data transmission command including the region number 3 and outputs the region data transmission command to the communication unit 31. This area data transmission command is transmitted via the API server 2 to the terminal device 1-2 that has transmitted the file operation notification (step S3403). Thereby, the terminal device 1-2 reads the hash value c1 (3) and the region data of the region number 3 included in the region data transmission command from the region data file in the storage unit 13 as described above, and the region number 3, An area data response including the hash value c1 (3) and area data is transmitted to the storage server 3.

  The file / FI processing unit 322 inputs the region data response received from the terminal device 1-2 from the communication unit 31 (step S3404), and sets the region number 3 included in the region data response in the region data file of the storage unit 33. Correspondingly, the hash value c1 (3) and the area data included in the area data file are stored (step S3405).

  The file / FI processing unit 322 uses the same hash value c (1), c included in the same FI with the unique ID stored in the storage unit 33 of the storage server 3 among the hash values of the attribute group included in the file operation notification. For (2), c (4), and c (5), area numbers 1, 2, 4, and 5 are specified, and the area data of area numbers 1, 2, 4, and 5 are extracted from the area data file in the storage unit 33. Read (step S3406).

  The file / FI processing unit 322 integrates the area data of area number 3 included in the received area data response and the area data of area numbers 1, 2, 4, and 5 read in step S3406 (step S3407). The original file is deleted from the storage unit 33, and the integrated file is stored in the storage unit 33 (step S3408). The processing in step S3408 corresponds to the processing in step S3006 shown in FIG. Then, the file / FI processing unit 322 performs processing such as generating an FI by adding an E tag d2 or the like (step S3409). The processing in step S3409 corresponds to the processing in steps S3007 and S3008 shown in FIG.

  As described above, according to the file operation unit 121 and the attribute processing unit 122 of the file processing unit 12 in the terminal device 1 and the file / FI processing unit 322 of the synchronization control unit 32 in the storage server 3, the file is divided into a predetermined size. The area data file including the hash value and area data for each area is stored, and the hash value included in the attribute group and FI is handled as the hash value for each area. Then, the file operation unit 121 of the file processing unit 12 in the terminal device 1 transmits only the updated area data to the storage server 3 in accordance with the area number included in the area data transmission command received from the storage server 3. . Thereby, since it is not necessary to transmit all the data constituting the file, the amount of transmission data can be reduced, and the transmission processing speed can be improved. Further, when the communication is resumed after being interrupted, it is not necessary to transmit all the data constituting the file, and only the area data of the updated area needs to be transmitted, so that the processing efficiency can be improved.

  Further, when an error occurs when uploading a new file from the terminal device 1 to the storage server 3 and the upload is not completed, the terminal device 1 has been uploaded after the error is cleared. Only area data that is not required may be continuously uploaded to the storage server 3. As a result, the amount of transmission data can be reduced and the transmission processing speed can be improved, and the efficiency of upload processing can be improved.

  The file update process for each area described above is a process for uploading a file, but it can also be applied for downloading a file. That is, the terminal device 1 compares the hash value included in the FI received from the storage server 3 with the hash value included in the FI stored in the terminal device 1, identifies the updated region number, and determines the region number. An area data transmission command including “” is transmitted to the storage server 3. Then, the storage server 3 reads the updated region data from the storage unit 33 according to the region number included in the region data transmission command received from the terminal device 1, and transmits a region data response including the region data to the terminal device 1. To do.

[Event server]
Next, the event server 4 shown in FIGS. 1 and 2 will be described in detail. FIG. 35 is a block diagram showing a configuration of the event server 4. The event server 4 includes a communication unit 41 and a storage unit 42.

  The communication unit 41 transmits and receives data between the API server 2 and the connection server 5 using a predetermined protocol. The communication unit 41 receives connection information (user ID and terminal ID) logged into the network 6 of the file synchronization system 10 managed by the connection server 5 and stores the connection information in the storage unit 42. Further, the communication unit 41 receives the update notification from the API server 2, reads the connection information from the storage unit 42, and shares information (user ID) and the transmission source terminal ID (the terminal on which the file operation has been performed) included in the update notification The terminal ID of the device 1) and the connection information (user ID and terminal ID) are specified, and the terminal ID of the terminal device 1 that notifies the updated event is specified, and an update command including the notification destination terminal ID is sent to the connection server. To 5.

  The storage unit 42 stores connection information. The connection information is stored and read by the communication unit 41. As described above, the connection information is information managed by the connection server 5, and when the terminal device 1 logs in to the network 6 constituting the file synchronization system 10 by the user, the logged-in user and the connected terminal device. 1 is information including a user ID and a terminal ID. That is, it is user specific information in which a user ID and a terminal ID related to the terminal device 1 used by the user are paired.

  FIG. 36 is a diagram illustrating a configuration of connection information stored in the storage unit 42. As described above, the connection information is user-specific information in which a user ID and a terminal ID are paired. For example, user ID: A and terminal ID: PC-A pair information, user ID: B and terminal ID: PC -B pair information. In the example of the connection information shown in FIG. 36, the terminal device 1 having the terminal ID: PC-A is logged in and connected to the network 6 of the file synchronization system 10 with the user ID: A, and the terminal ID: PC- The terminal device 1 having B is logged in and connected by the user ID: B.

  Next, processing of the event server 4 shown in FIG. 35 will be described. FIG. 37 is a flowchart showing the processing of the event server 4. The communication unit 41 of the event server 4 determines whether or not connection information has been received from the connection server 5 (step S3701). If it is determined that the connection information has been received (step S3701: Y), the connection information is stored in the storage unit. 42 (step S3702). On the other hand, if the communication unit 41 determines in step S3701 that connection information has not been received (step S3701: N), the communication unit 41 proceeds to step S3703.

  The communication unit 41 proceeds from step S3701 to determine whether or not an update notification has been received from the API server 2 (step S3703). When it is determined that an update notification has been received (step S3703: Y), the storage unit 42, the connection information is read out, and an event with an update is determined based on the shared information (user ID) and the transmission source terminal ID (terminal ID of the terminal device 1 on which the file operation has been performed) included in the update notification and the connection information. The terminal ID of the terminal device 1 to be notified is specified (step S3704). Specifically, the communication unit 41 identifies the terminal ID corresponding to the user ID of the shared information based on the connection information (user ID and terminal ID), and the transmission source terminal ID (file) of the identified terminal IDs The terminal device 1 that notifies an event with an update of a terminal ID (other terminal device 1 connected to the storage server 3 via the API server 2) other than the terminal ID of the terminal device 1 on which the operation is performed. The terminal ID, that is, the notification destination terminal ID is specified.

  The communication unit 41 outputs an update command including the notification destination terminal ID to the connection server 5 (step S3705).

  When the event server 4 proceeds from step S3702 or step S3705 or determines that the update notification is not received in step S3703 (step S3703: N), the event server 4 ends the process and performs the process of step S3701 again.

[Connection Server]
Next, the event server 5 shown in FIGS. 1 and 2 will be described in detail. FIG. 38 is a block diagram showing the configuration of the connection server 5. The connection server 5 includes a communication unit 51 and a connection management unit 52.

  The communication unit 51 transmits and receives data between the terminal device 1 and the event server 4 using a predetermined protocol. The communication unit 51 receives login information (user ID and terminal ID) from the terminal device 1 and outputs the login information (user ID and terminal ID) to the connection management unit 52, and inputs connection information (user ID and terminal ID) from the connection management unit 52. 4 to send. In addition, the communication unit 51 receives an update command from the event server 4 and transmits information indicating that there is an update to the terminal device 1 of the notification destination terminal ID included in the update command.

  The connection management unit 52 receives login information from the communication unit 51, manages it as connection information, and outputs the connection information to the communication unit 51.

  Next, processing of the connection server 5 shown in FIG. 38 will be described. FIG. 39 is a flowchart showing processing of the connection server 5. The communication unit 51 of the connection server 5 determines whether or not login information has been received from the terminal device 1 (step S3901). If it is determined that the login information has been received (step S3901: Y), the login information is connection-managed. To the unit 52. Then, the connection management unit 52 receives the login information from the communication unit 51, manages it as connection information (step S3902), and outputs the connection information to the communication unit 51. The communication unit 51 inputs connection information from the connection management unit 52 and transmits it to the event server 4 (step S3903). On the other hand, if the communication unit 51 determines in step S3901 that login information has not been received (step S3901: N), the communication unit 51 proceeds to step S3904.

  The communication unit 51 proceeds from step S3901 to determine whether or not an update command has been received from the event server 4 (step S3904). When it is determined that an update command has been received (step S3904: Y), the update command Is transmitted to the terminal device 1 of the notification destination terminal ID included in (step S3905).

  When the connection server 5 shifts from Step S3903 and Step S3905, or determines that an update command has not been received in Step S3904 (Step S3904: N), the connection server 5 ends the process and performs the process of Step S3901 again.

  As described above, according to the file synchronization system 10 according to the embodiment of the present invention, the icon display unit 123 of the file processing unit 12 in the terminal device 1 has the mark indicating the file upload, upload failure, and download status, “ “New file creation” or “file copy” is performed in another terminal device 1 and a mark indicating that a new file has not been downloaded from the storage server 3, and “file update”, “file name change” or “ “Move file” is performed in the other terminal device 1, and a mark indicating that the old file is held in its own terminal device 1 is added to the icon of the folder according to each state and displayed. did. In addition, the mark is propagated and displayed to the upper folder, and further, these marks are collectively displayed. Thus, the user can accurately recognize the file synchronization state from the mark displayed by being added to the folder icon before performing the file operation. Therefore, the operability for the file can be improved.

  The present invention has been described with reference to the embodiment. However, the present invention is not limited to the above-described embodiment, and various modifications can be made without departing from the technical idea thereof. For example, in the example illustrated in FIG. 2, the terminal device 1-1 receives the upper folder path from the API server 2 and transmits an FI acquisition request including the upper folder path. On the other hand, the terminal device 1-1 may receive the unique ID of the shared file in the upper folder instead of the path of the upper folder, and transmit the FI acquisition request including the unique ID. Further, in the file synchronization system 10 shown in FIGS. 1 and 2, the storage server 3 may have the functions of the event server 4 and the connection server 5. In this case, the file synchronization system 10 includes the terminal device 1, the receiving device 2, and the storage server 3.

  In addition, as a hardware configuration of the terminal device 1, the API server 2, the storage server 3, the event server 4, and the connection server 5 of the file synchronization system 10 according to the embodiment of the present invention, a normal computer can be used. These devices are configured by a computer having a volatile storage medium such as a CPU and a RAM, a non-volatile storage medium such as a ROM, an interface, and the like. A communication unit 11 and a file processing unit 12 provided in the terminal device 1, a communication unit 21 provided in the API server 2, a communication unit 31 and a synchronization control unit 32 provided in the storage server 3, a communication unit 41 provided in the event server 4, Each function of the communication unit 51 included in the connection server 5 is realized by causing the CPU to execute a program describing these functions. These programs can also be stored and distributed in a storage medium such as a magnetic disk (floppy (registered trademark) disk, hard disk, etc.), optical disk (CD-ROM, DVD, etc.), semiconductor memory, or the like.

DESCRIPTION OF SYMBOLS 1 Terminal device 2 API server 3 Storage server 4 Event server 5 Connection server 6 Network 10 File synchronous system 11, 21, 31, 41, 51 Communication part 12 File processing part 13, 22, 33, 42 Storage part 32 Synchronization control part 52 Connection management unit 121 File operation unit 122 Attribute processing unit 123 Icon display unit 321 Operation type identification unit 322 File / FI processing unit 323 FI transmission unit 324 Collision processing unit

Claims (7)

Added to the icon of the upper folder to which the file belongs based on the information indicating the synchronization status between the file stored in the storage unit and the file stored in another device connected via the network Determining the display of a predetermined mark to be performed;
A program causing a computer to execute the step of adding the determined predetermined mark to an icon of a higher-order folder and displaying it. The program according to claim 1,
Downloading a file with the other device based on the information indicating the synchronization state;
A program for causing a computer to execute the step of deleting the display of the predetermined mark when downloading with the other device is completed. In the program according to claim 1 or 2,
When uploading a file with the other device, the file icon and / or the icon of the upper folder to which the file belongs are displayed with a predetermined mark, and the upload has failed. And displaying the icon with another predetermined mark, and causing the computer to execute a step of deleting the display of the predetermined mark and the other predetermined mark when the upload is completed. A program characterized by In the program according to any one of claims 1 to 3,
A program causing a computer to execute the step of propagating and displaying the predetermined mark from the icon to an icon of a higher folder. In the program according to any one of claims 1 to 4,
A program causing a computer to execute a step of adding and displaying a mark corresponding to a type of operation on the file by a user to the icon. In the terminal device icon display method in a system in which a storage server having a plurality of terminal devices and a folder accessible by the terminal device is connected via a network,
The storage server includes a storage unit storing files belonging to the folder,
The terminal device includes a storage unit in which a file is stored,
The storage server transmitting a file index indicating an attribute of the file stored in the storage unit to the terminal device;
Based on the attribute data of the file stored in the storage unit and the file index received from the storage server, the terminal device determines display of a predetermined mark to be added to the icon of the upper folder to which the file belongs. And steps to
The terminal device displaying the predetermined mark added to an icon of a higher folder; and
An icon display method characterized by comprising: In a system in which a storage server having a plurality of terminal devices and a folder accessible by the terminal device is connected via a network,
The storage server
A storage unit storing files belonging to the folder;
A file index transmission unit that transmits a file index indicating the attribute of the file stored in the storage unit to the terminal device,
The terminal device
A storage unit storing files;
Based on the attribute data of the file stored in the storage unit and the file index received from the storage server, the display of a predetermined mark to be added to the icon of the upper folder to which the file belongs is determined, And an icon display unit for displaying the mark added to the icon of the upper folder.

Images