JP6231952B2 - Data management apparatus and data management method - Google Patents

Description

  The present invention relates to a data management apparatus and a data management method for managing terminal data.

  Conventionally, it is known to back up client data to a server in preparation for data corruption. For example, Patent Document 1 discloses a technique for efficiently backing up data of a plurality of clients.

JP 2000-215129 A

  By the way, as one of backup technologies, a service is known in which data stored in a communication terminal such as a mobile phone is backed up to a personal computer (PC) and restored to another communication terminal. A service for sharing data among a plurality of communication terminals, that is, synchronizing data between a plurality of communication terminals is also known.

  In recent years, cooperation between a personal computer and a communication terminal has become closer, and it is necessary to provide both backup and restoration between two communication terminals and synchronization of the same data between a plurality of communication terminals via the personal computer. For example, the data of the terminal A is backed up to a personal computer while being stored in the terminal A for the purpose of preventing the data loss of the terminal A and shifting to another terminal B. On the other hand, the photograph S newly taken by the terminal A is set as a synchronization target so that it can be viewed on another terminal B owned by the user. The photos S that are images to be synchronized are stored in the personal computer, and when the terminal B is connected to the personal computer, the photos S need to be automatically stored in the terminal B.

  Usually, backup data and synchronization data are managed at different locations on a personal computer. However, it is considered that there are many same types of two types of data having different uses. This puts pressure on the capacity of the personal computer storage system used for backup and synchronization.

  As described above, Patent Document 1 discloses a technique for efficiently backing up data of a plurality of clients. However, the prior art disclosed in Patent Document 1 focuses only on data backup and restoration, and does not consider data synchronization between a plurality of terminals. Therefore, the technique described in Patent Document 1 cannot efficiently store data when performing both backup and synchronization of data.

  The present invention has been made to solve the above problems, and provides a data management apparatus and a data management method capable of efficiently storing data when both data backup and synchronization are performed. The purpose is to do.

  In order to achieve the above object, a data management apparatus according to the present invention includes, from a terminal, receiving means for receiving data stored in the terminal, and data received by the receiving means for each receiving terminal. Backup data storage means for storing the data as backup data, a synchronization data storage means for creating a link to the data stored by the backup data storage means, and storing the link as data for synchronization between terminals, and a terminal A backup data transmission unit that receives a backup data transmission request including information to be identified, reads out backup data stored in association with the terminal by the backup data storage unit, and transmits the backup data to the request source; and synchronous data storage unit Backup linked by synchronization data stored by It reads the backup data stored by over data storage unit, and a synchronous data transmission unit to be transmitted to the synchronization target terminal.

  The data management apparatus according to the present invention can perform both backup and synchronization of data. In the data management apparatus according to the present invention, synchronization is performed by referring to the link to the backup data. Therefore, it is not necessary to store actual data for synchronization. That is, it is not necessary to store the actual data for backup and the actual data for synchronization in duplicate. As a result, according to the data management device of the present invention, it is possible to efficiently store data when performing both backup and synchronization of data.

  The data management device detects processing for the synchronization data stored by the synchronization data storage means, and performs processing for the backup data linked by the synchronization data and stored by the backup data storage means in response to the detection Or data for detecting the processing for the backup data stored by the backup data storage means, and performing processing for the synchronization data stored by the synchronous data storage means as well as being a link to the backup data in response to the detection An updating unit may be further provided. According to this configuration, the synchronization data and the backup data can be matched. Thereby, synchronization and backup can be performed more appropriately.

  Specifically, the data update means detects that the synchronization data stored by the synchronization data storage means has been deleted, and is linked by the synchronization data and stored by the backup data storage means in response to the detection. The backup data may be deleted. According to this configuration, it is possible to prevent unintended backup of data that the user intends to delete.

  Further, the data update means detects that the backup data stored by the backup data storage means has been edited, and is linked to the backup data and stored by the synchronous data storage means in response to the detection. The synchronization data may indicate that the backup data is to be newly synchronized. According to this configuration, the edited data can be appropriately synchronized.

  The synchronous data storage means may create a link to the data according to the type of data received by the receiving means. According to this configuration, synchronization can be performed only for necessary types of data. Thereby, synchronization can be performed more appropriately.

  By the way, the present invention can be described as the invention of the data management method as described above, as well as the invention of the data management method as follows. This is substantially the same invention only in different categories, and has the same operations and effects.

  That is, the data management method according to the present invention is a data management method that is an operation method of a data management device, and is received in a reception step of receiving data stored in the terminal from the terminal, and in the reception step. A backup data storage step for storing data as backup data for each receiving terminal, and a link to the data stored in the backup data storage step is created, and the link is stored as data for synchronization between terminals Backup data that receives a synchronous data storage step and a backup data transmission request including information for identifying a terminal, reads backup data stored in association with the terminal in the backup data storage step, and transmits the backup data to the request source Transmission step and synchronous data storage step It reads the backup data stored in the link has been backed up data storing step by synchronizing data stored in, including a synchronous data transmission step of transmitting against a synchronized terminal.

  According to the present invention, since it is not necessary to store the actual data for backup and the actual data for synchronization in duplicate, it is possible to efficiently store data when performing both backup and synchronization of data. it can.

It is a figure which shows the structure of the personal computer which is a data management apparatus which concerns on embodiment of this invention. It is a correspondence table memorize | stored in a personal computer. It is a figure which shows the hardware constitutions of the personal computer which is the data management apparatus which concerns on embodiment of this invention. It is a flowchart which shows the process (data management method) at the time of storing the data of the management object performed with the personal computer which is a data management apparatus which concerns on embodiment of this invention. It is a flowchart which shows the process (data management method) at the time of decompression | restoration performed using the data memorize | stored in the personal computer in the communication terminal performed with the personal computer which is a data management apparatus which concerns on embodiment of this invention. It is a flowchart which shows the process (data management method) at the time of using the data memorize | stored in the personal computer in the communication terminal performed by the personal computer which is a data management apparatus which concerns on embodiment of this invention. It is a flowchart which shows the process (data management method) at the time of deletion of the data for a synchronization performed with the personal computer which is a data management apparatus which concerns on embodiment of this invention. It is a flowchart which shows the process (data management method) at the time of editing backup data performed with the personal computer which is a data management apparatus which concerns on embodiment of this invention. It is a flowchart which shows the process (data management method) when the file name of the data for a synchronization is performed performed with the personal computer which is a data management apparatus which concerns on embodiment of this invention.

  Hereinafter, embodiments of a data management device and a data management method according to the present invention will be described in detail with reference to the drawings. In the description of the drawings, the same elements are denoted by the same reference numerals, and redundant description is omitted.

  FIG. 1 shows a personal computer 10 which is a data management apparatus according to this embodiment. The personal computer 10 is a device (data synchronization support device, data sharing device) that manages data of the communication terminal 20. Specifically, the personal computer 10 performs data synchronization among a plurality of communication terminals 20 (supports data synchronization). Data synchronization is to hold the same data among a plurality of communication terminals 20, that is, to share data among a plurality of communication terminals 20. Further, the personal computer 10 backs up the data of the communication terminal 20 in preparation for the damage of the data of the communication terminal 20 or the like. The personal computer 10 transmits the backed up data to the communication terminal 20 as necessary. For example, the personal computer 10 is owned and managed by a user (user) who owns the communication terminal 20 that stores data to be managed.

  Here, the communication terminal 20 that stores data to be managed will be described. The communication terminal 20 is, for example, a device that is owned by a user and can perform communication (for example, mobile communication), and specifically corresponds to a mobile phone including a smartphone. The communication terminal 20 and the personal computer 10 can exchange data with each other. For example, data transmission / reception is performed by at least one of communication by wired connection using a USB (Universal Serial Bus) cable or the like and communication by wireless connection by a wireless local area network (LAN) (for example, Wi-Fi).

  As described above, the communication terminal 20 stores (holds, stores, stores) data to be managed by the personal computer 10. The communication terminal 20 includes a storage system, and stores the above data by the storage system. Specifically, the storage system is a storage built in the communication terminal 20 and an external memory card (for example, an SD card) attached to the communication terminal 20. Data to be managed by the personal computer 10 is, for example, a file such as an image, music, moving image, or document. These data may be user personal information generated by the user of the communication terminal 20.

  Note that data to be managed by the personal computer 10 is set in advance. This setting may be performed for each data, or may be performed for each data type. The data type is the type of image, music, video, document, etc. The setting for data or type includes a setting for performing both synchronization and backup. In addition, the setting may include a setting for performing only backup and a setting for performing only synchronization. The communication terminal 20 may store data that is not managed by the personal computer 10. The above setting is also grasped by the personal computer 10 by transmitting / receiving information regarding the setting between the communication terminal 20 and the personal computer 10.

  The communication terminal 20 has a function of backing up and synchronizing data. The communication terminal 20 acquires data to be managed from the storage system. This acquisition is performed using, for example, an API (Application Programming Interface) of an OS (operating system) operating on the communication terminal 20 (for example, a media store API provided for the Android (registered trademark) OS). The communication terminal 20 transmits the acquired data to the personal computer 10. Details of data transmission will be described later.

  In the communication terminal 20, information for specifying the communication terminal 20 is set in advance. For example, the personal computer 10 distributes a terminal ID as information for specifying the communication terminal 20 to each communication terminal 20. When transmitting data to the personal computer 10, the communication terminal 20 transmits the terminal ID in association with the data. Thereby, in the personal computer 10, the communication terminal 20 of the data transmission source can be specified.

  The backed up data is restored in the same manner as before. That is, the communication terminal 20 requests the personal computer 10 to transmit data including information (for example, the above-described terminal ID) that identifies the communication terminal 20 that backed up the data. Note that the terminal ID included in the data transmission request may not be the terminal ID of itself. That is, data backed up by another communication terminal 20 may be restored to itself. The communication terminal 20 receives data for restoration from the personal computer 10 in response to the transmission request and stores it in its own storage system. The communication terminal 20 performs restoration using the data. Normally, this restoration is performed by writing a file to a directory (folder, path) in the same storage system as at the time of backup.

  Acquisition of data to be synchronized is performed in the same manner as before. That is, when the communication terminal 20 is connected to the personal computer 10, synchronization data is transmitted from the personal computer 10 to the communication terminal 20. The communication terminal 20 receives the synchronization data from the personal computer 10 in response to the transmission request and stores it in its own storage system. For example, the file is written to a path designated in advance in the storage system (for example, the / sync directory under the SD card).

  A plurality of communication terminals 20 (groups of communication terminals 20) that perform synchronization are set in advance and stored in the personal computer 10. The personal computer 10 performs control so that data is synchronized between the set communication terminals 20. The above is the communication terminal 20 that stores data to be managed.

  Subsequently, functions of the personal computer 10 according to the present embodiment will be described. As shown in FIG. 1, the personal computer 10 includes a receiving unit 11, a backup data storage unit 12, a synchronous data storage unit 13, a backup data transmission unit 14, a synchronous data transmission unit 15, and a data update unit 16. It is prepared for. In addition, the personal computer 10 usually has functions other than those described above that are included in a conventional personal computer.

  The receiving unit 11 is a receiving unit that receives management target data stored in the communication terminal 20 from the communication terminal 20. For example, the receiving unit 11 receives data as follows. The receiving unit 11 detects that a communication connection has been established between the personal computer 10 and the communication terminal 20. Here, the communication terminal 20 is a communication terminal 20 that is a target for data backup and synchronization. The receiving unit 11 stores a target communication terminal 20 (for example, the above-described terminal ID) in advance. The receiving unit 11 requests the communication terminal 20 for a list (directory and file) of data to be managed stored in the communication terminal 20 and acquires the list from the communication terminal 20.

  The receiving unit 11 compares the list with the data stored in the backup data storage unit 12, and the difference that is data included in the list but not included in the data stored in the backup data storage unit 12 To extract. When the receiving unit 11 extracts the difference, the receiving unit 11 transmits information indicating the difference to the communication terminal 20. The communication terminal 20 receives the information, acquires data indicated by the difference from its own storage system, and transmits the data including the directory to the receiving unit 11. The receiving unit 11 receives data transmitted from the communication terminal 20. The data transmitted as described above is associated with a terminal ID so that the communication terminal 20 that is the data transmission source can be specified. The receiving unit 11 outputs the received data to the backup data storage unit 12.

  In the above description, data transmission is performed according to a request from the personal computer 10, but it may be performed mainly from the communication terminal 20 side. For example, the communication terminal 20 may detect that a communication connection has been established with the personal computer 10 and transmit data using this detection as a trigger. Or it is good also as transmitting by a user's operation as a trigger. Moreover, although only the difference data is transmitted, all the management target data stored in the communication terminal 20 may be transmitted.

  The backup data storage unit 12 is a backup data storage unit that stores data received by the receiving unit 11 as backup data for each communication terminal 20 that is a reception source. The backup data storage unit 12 stores backup data in a storage system provided in the personal computer 10. The backup data storage unit 12 stores data in different folders in the storage system for each communication terminal 20. Further, the backup data storage unit 12 may store data in different folders in the storage system for each data type. In that case, the backup data storage unit 12 determines the type of each data. The backup data storage unit 12 may determine the type of data using a file extension provided for each data, or may refer to metadata indicating the type added to each data. Good. When the data received by the receiving unit 11 includes a directory, the backup data storage unit 12 stores the directory.

For example, the image, music, moving image, and document data received from the terminal A are stored in the following place (folder).
Image data storage folder:
C: \ Users \ UserA \ AppData \ Local \ APP1 \ deviceA \ picture \
Storage folder for music data:
C: \ Users \ UserA \ AppData \ Local \ APP1 \ deviceA \ music \
Storage folder for video data:
C: \ Users \ UserA \ AppData \ Local \ APP1 \ deviceA \ video \
Document data storage folder:
C: \ Users \ UserA \ AppData \ Local \ APP1 \ deviceA \ document \

  When the backup data storage unit 12 newly stores backup data, the backup data storage unit 12 notifies the synchronous data storage unit 13 of the storage folder and file name of the data.

  The synchronization data storage unit 13 is a synchronization data storage unit that creates a link (link information) to data stored in the backup data storage unit 12 and stores the link as data for synchronization between the communication terminals 20. Specifically, the synchronous data storage unit 13 generates the above-described link by a hard link, for example. The hard link (hard link information) is generated by, for example, the function of the OS (for example, Windows (registered trademark)) of the personal computer 10. Hard link is a technique in which two names, file A and file B, are assigned to one file entity, and both are associated with the file entity.

  The synchronization data storage unit 13 may create the link only for data to be synchronized among the data stored by the backup data storage unit 12. For example, the synchronization data storage unit 13 may create the link only for the type of data to be synchronized. Thus, the synchronous data storage unit 13 may create a link to the data according to the type of data.

  The type of synchronization target can be set on the communication terminal 20 side as described above, but may be set on the personal computer 10 side. For example, settings can be made such that all types of data are synchronized or only image data is synchronized. This setting can be performed, for example, by selecting a type from a setting menu of an application that implements the present embodiment. By default, all data may be synchronized regardless of the type of data.

The synchronization data storage unit 13 stores the synchronization data generated in the storage system included in the personal computer 10. The synchronous data storage unit 13 may store the data in different folders in the storage system for each data type. For example, the received image, music, moving image, and document data stored in the backup data storage unit 12 are stored in the following locations (folders).
Image data storage folder:
C: \ Users \ Users \ Documents \ APP1 \ picture \
Storage folder for music data:
C: \ Users \ Users \ Documents \ APP1 \ music \
Storage folder for video data:
C: \ Users \ Users \ Documents \ APP1 \ video \
Document data storage folder:
C: \ Users \ Users \ Documents \ APP1 \ document \
The difference from the data stored by the backup data storage unit 12 is that it is not stored for each communication terminal 20.

  The synchronous data storage unit 13 manages the correspondence between the link and the actual data using a correspondence table (database) shown in FIG. As shown in FIG. 2, the correspondence table stores information for each data to be managed (backup data). Specifically, the terminal ID, category, actual data folder, file name, attribute, file ID, Synchronous link folder, link file, file hash, synchronous side deletion and actual data deletion information are stored in association with each other.

  The terminal ID is the terminal ID of the communication terminal 20 that is the transmission source of the data. The category is information indicating the type of data. The actual data folder is information indicating a path (folder) in which backup data (actual data) is stored. In addition, the correspondence table of FIG. 2 includes only information after the above “C: \ Users \ UserA \ AppData \ Local \ APP1 \ deviceA \ picture \” (folder specified by the terminal ID and type). Yes. The file name is the name of backup data (actual data). The attribute is information indicating whether the data is a file or a directory.

  The file ID is the only ID of backup data generated by the OS of the personal computer 10. A file ID can be generated by passing backup data to a specified API of the OS. The synchronization link folder is a folder for storing a link to the backup data (synchronization data). The link file is the file name of the link. For example, the synchronous data storage unit 13 generates a file name with a random character string.

  The file hash is hash information (hash value) obtained from backup data. The synchronous data storage unit 13 stores a hash function in advance, and obtains (calculates) hash information by inputting backup data into the hash function. The file hash is data composed of character strings. The synchronization side deletion is information indicating whether or not the link is physically deleted. “Delete” is set in accordance with a process to be described later. The initial value is “not deleted”. The actual data deletion is information indicating whether the backup data has been deleted. “Delete” is set in accordance with a process to be described later. The initial value is “not deleted”.

  The synchronous data storage unit 13 also generates and stores information stored in the correspondence table when the link is generated.

  The backup data transmission unit 14 receives a backup data transmission request including information for specifying the communication terminal 20, and reads out and requests the backup data stored in association with the communication terminal 20 by the backup data storage unit 12. This is backup data transmission means for transmitting to the original. Specifically, the backup data transmission unit 14 receives a data transmission request (restoration request) including the terminal ID of the backed up communication terminal 20 from the communication terminal 20 that requests restoration of backup data. The backup data transmission unit 14 reads the backup data stored in association with the communication terminal 20 indicated by the terminal ID, and transmits it to the requesting communication terminal 20. Note that the communication terminal 20 that requests the restoration of backup data as described above and the communication terminal 20 that has been backed up do not necessarily match. If these communication terminals 20 do not match, the data is transferred from the backed up communication terminal 20 to the communication terminal 20 requesting restoration.

  The synchronization data transmission unit 15 is linked by the synchronization data stored in the synchronization data storage unit 13 and reads the backup data stored in the backup data storage unit 12 to the communication terminal 20 to be synchronized. Synchronous data transmission means for transmitting. The synchronous data transmission unit 15 transmits data as follows, for example. The synchronization data transmission unit 15 stores a communication terminal 20 (for example, the above-described terminal ID) to be synchronized in advance. The synchronization data transmission unit 15 detects that a communication connection has been established between the personal computer 10 and the communication terminal 20 to be synchronized. This detection may be shared with the detection by the receiving unit 11 described above.

  Subsequently, the synchronization data transmission unit 15 specifies data to be transmitted to the communication terminal 20 (data to be synchronized). For example, the synchronization data transmission unit 15 requests the communication terminal 20 for a list (directory and file) of data to be synchronized stored in the communication terminal 20 and acquires the list from the communication terminal 20. To do. If the data to be backed up and the data to be synchronized are the same, the acquisition of this list may be shared with the acquisition by the reception unit 11 described above.

  The synchronization data transmission unit 15 compares the list with the correspondence table shown in FIG. 2 generated by the synchronization data storage unit 13, and calculates a difference that is data included in the correspondence table but not included in the list. Extract. In the correspondence table shown in FIG. 2, data in which the column for deletion on the synchronization side is “deleted” is not subject to synchronization.

Alternatively, the data to be transmitted to the communication terminal 20 (data to be synchronized) may be specified as follows. The synchronous data transmission unit 15 includes a dedicated database and stores a history of data synchronized for each communication terminal 20. For example, as an example of history,
Terminal A: Link information of synchronized data on April 15, 2014: A. jpg, B.M. mp3
Is stored. After that, the synchronization data transmission unit 15 compares the synchronized link stored in the database with the correspondence table shown in FIG. 2 generated by the synchronization data storage unit 13, and is included in the correspondence table but is synchronized. Differences that are data not included in the link are extracted.

  When the synchronous data transmission unit 15 extracts the difference, the synchronous data transmission unit 15 refers to the link of the data related to the difference, reads the backup data referred to by the link, and transmits it to the communication terminal 20.

  When the synchronization data transmission unit 15 detects the connection of the plurality of communication terminals 20 to the personal computer 10, the synchronization data transmission unit 15 sequentially performs the above processing for each communication terminal 20. Specifically, the synchronous data transmission unit 15 acquires a list of connected communication terminals 20 in the form of an array. The synchronization data transmission unit 15 sets a flag for the communication terminal 20 that has been synchronized, and repeatedly transmits the above data until there is no communication terminal 20 that has not been flagged.

  The data update unit 16 is a data update unit that performs data update on at least one of the backup data and the synchronization data. For example, the data updating unit 16 detects (detects) processing for the synchronization data (link) stored by the synchronization data storage unit 13 and is linked by the synchronization data in response to the detection, and is backed up by the backup data storage unit 12. The process for the backup data stored by the is performed. Note that the processing for the synchronization data to be detected may not be performed by the function of the personal computer 10 according to the present invention, and may be performed by the conventional function of the personal computer 10, for example. Moreover, this process is performed according to operation with respect to the personal computer 10 of a user, for example.

  Specifically, the data update unit 16 detects that the synchronization data stored in the synchronization data storage unit 13 has been deleted, and is linked by the synchronization data in response to the detection and is backed up by the backup data storage unit 12. Delete the backup data stored by.

  The data update unit 16 constantly monitors events such as data editing and deletion performed by the OS of the personal computer 10. When the data update unit 16 detects the deletion of the synchronization data by the monitoring, the data update unit 16 acquires an event parameter regarding the deleted data and determines whether the data is a file or a folder. If the data update unit 16 determines that the deleted data is a file, the data update unit 16 uses the file name (link file) of the file to search for a record corresponding to the file in the correspondence table shown in FIG. . The data update unit 16 sets “delete” in the column of deletion on the synchronization side of the record (deletion mark is given).

  The data updating unit 16 periodically searches for a record in the synchronization table in which the synchronization deletion column is set to “deleted”, and deletes the backup data corresponding to the record. When the data update unit 16 deletes the backup data, the data update column of the record in the correspondence table shown in FIG. 2 is set to “delete”. Note that the data updating unit 16 may delete the backup data and the record itself at the timing when the synchronization deletion column of the record is set to “delete”.

  When the data update unit 16 determines that the deleted data is a folder, the data update unit 16 searches for a record corresponding to the folder in the correspondence table illustrated in FIG. 2 using the folder name (synchronized link folder) of the folder. To do. The data update unit 16 sets the column for deletion on the synchronization side of the record as “deleted”. In addition, the data updating unit 16 sets “delete” in the synchronization side deletion column of records corresponding to the folders and files included in the folder. Thereafter, the deletion process is performed in the same manner as when the deleted data is a file.

  Alternatively, the data update unit 16 detects (detects) processing for the backup data stored in the backup data storage unit 12, and is a link to the backup data in response to the detection, and the synchronous data storage unit 13 Process the stored synchronization data. Note that the processing for the backup data to be detected may not be performed by the function of the personal computer 10 according to the present invention, and may be performed by the conventional function of the personal computer 10, for example. Moreover, this process is performed according to operation with respect to the personal computer 10 of a user, for example.

  Specifically, the data update unit 16 detects that the backup data stored by the backup data storage unit 12 has been edited, and in response to the detection, the data update unit 16 is a link to the backup data and stores synchronous data. It is assumed that the synchronization data stored by the unit 13 indicates that the backup data should be newly synchronized.

  When the user opens an image file, which is backup data, with an image editing application provided in the personal computer 10 and performs processing such as entering handwritten characters, the data update unit 16 performs backup data by performing the above monitoring. Detect edits in Since the hash information of the file has changed due to the editing, the data update unit 16 performs the following two processes.

  As a first process, the data update unit 16 acquires hash information of the file. The data update unit 16 searches for a record corresponding to the file in the correspondence table illustrated in FIG. 2 using the file name (link file) of the file. The data update unit 16 updates the file hash sequence of the record with the acquired hash information. The purpose of this process is to not affect the file name change process described below.

  As the second process, even if the file has been synchronized with the communication terminal 20 once, the data update unit 16 sets the synchronization target again because the file has been updated. Specifically, for example, the data update unit 16 adds a flag for synchronizing to the synchronization data even if the file is not included in the difference for synchronization, or for the synchronized data Processing such as deleting the file from the history is performed (in this case, the data history is also included in the synchronization data).

  When the file name of the synchronization data (link) is corrected (changed), the data update unit 16 performs the following processing. The data update unit 16 detects a change in the file name of the synchronization data through the above monitoring. The data update unit 16 acquires the file ID of the file. The data update unit 16 searches for a record corresponding to the file in the correspondence table shown in FIG. 2 using the file ID of the file. If the record is not retrieved, the subsequent processing is not performed. A file related to a record that does not exist in the correspondence table is assumed to be a file in which a user manually copies a file on the personal computer 10 to a folder in which synchronization data is stored. When the record is searched, the data update unit 16 updates the link file column of the record with the updated file name.

  In addition to the correction of the file name of the synchronization data, the data update unit 16 considers the case where the backup data linked by the synchronization data is updated, and updates the file contents of the backup data. Check if it exists. Specifically, the data update unit 16 acquires the hash information of the backup data, and compares the hash information (information on the file hash column) of the record corresponding to the file of the correspondence table illustrated in FIG. . If the hash information matches as a result of the comparison, the process ends. If these pieces of hash information do not match, the data update unit 16 updates the file hash sequence of the record with the acquired hash information. In addition, the data update unit 16 sets the file as a synchronization target again in the same manner as described above. The functional configuration of the personal computer 10 according to the present embodiment has been described above.

  FIG. 3 shows a hardware configuration of the personal computer 10 according to the present embodiment. As shown in FIG. 3, a personal computer 10 includes a central processing unit (CPU) 101, a random access memory (RAM) 102 and a read only memory (ROM) 103 that are main storage devices, a communication module 104 for communication, a hard disk, and the like. The auxiliary storage device 105 is configured as a computer including hardware. The functions of the personal computer 10 described above are exhibited when these components are operated by a program or the like. The above is the configuration of the personal computer 10 according to the present embodiment.

  Subsequently, a data management method, which is an operation method of the personal computer 10 (processing executed by the personal computer 10) according to the present embodiment, will be described for each process using the flowcharts of FIGS. First, a process when data to be managed is stored in the personal computer 10 (a process in which data is backed up from the communication terminal 20) will be described using the flowchart of FIG.

  In this case, as a premise of this process, a connection is established between the personal computer 10 and the communication terminal 20 in order to transmit data to be managed. This connection is performed based on, for example, a user operation or a preset setting of the personal computer 10 and the communication terminal 20. In this process, it is detected by the receiving unit 11 of the personal computer 10 that a communication connection has been established between the personal computer 10 and the communication terminal 20 (S01, receiving step). Subsequently, the receiving unit 11 acquires a list of data to be managed stored in the communication terminal 20 from the communication terminal 20 (S02, reception step).

  Subsequently, the receiving unit 11 compares the list with the data stored in the backup data storage unit 12 and is included in the list but not included in the data stored in the backup data storage unit 12. The difference which is data is extracted (S03, reception step). When the difference is not extracted (NO in S04), the subsequent processing is not performed and the processing ends. When the difference is extracted (YES in S04), the reception unit 11 receives the data indicated by the difference from the communication terminal 20 (S05, reception step). For example, when the image file “/storage/sdcard/DCIM/01.jpg” stored in the communication terminal 20 is not stored (not backed up), the image file is received. The received data is output from the receiving unit 11 to the backup data storage unit 12.

Subsequently, the backup data storage unit 12 stores the data received by the reception unit 11 as backup data for each receiving communication terminal 20 (S06, backup data storage step). For example, in the case of the above difference data, it is stored (backed up) in the following in the personal computer 10 below.
C: \ Users \ Users \ Documents \ APP1 \ picture \ storage \ sdcard \ DCIM \ 01.jpg
Subsequently, the storage folder and file name of the data are notified from the backup data storage unit 12 to the synchronous data storage unit 13.

  Subsequently, a link to data newly stored by the backup data storage unit 12 is created by the synchronization data storage unit 13 and stored as synchronization data (S07, synchronization data storage step). Further, the synchronous data storage unit 13 generates and stores a record relating to the data in the correspondence table shown in FIG. The above is the processing when the management target data is stored in the personal computer 10.

  Subsequently, processing when data is stored in the personal computer 10 in the communication terminal 20 and restoration is performed will be described using the flowchart of FIG. In this case, as a premise of this process, a connection is established between the personal computer 10 and the communication terminal 20 in order to transmit data to be managed. In addition, a transmission request for data including the terminal ID of the backed up communication terminal 20 is transmitted from the communication terminal 20 to the personal computer 10. The above is performed based on a user operation, for example.

  In this process, the above-mentioned transmission request is received by the backup data transmission unit 14 of the personal computer 10 (S11, backup data transmission step). Subsequently, the backup data transmission unit 14 reads the backup data stored in association with the communication terminal 20 indicated by the terminal ID included in the transmission request and transmits it to the requesting communication terminal 20 (S12, backup data). Send step). The communication terminal 20 that has transmitted the transmission request receives the backup data and restores the data. The above is the processing when the data stored in the personal computer 10 is used in the communication terminal 20 to be restored.

  Subsequently, processing when synchronization is performed using data stored in the personal computer 10 in the communication terminal 20 will be described using the flowchart of FIG. 6. In this case, as a premise of this processing, a connection is established between the personal computer 10 and the communication terminal 20 in order to transmit synchronization data. This connection is performed based on, for example, a user operation or a preset setting of the personal computer 10 and the communication terminal 20. In this process, the synchronization data transmission unit 15 of the personal computer 10 detects that a communication connection has been established between the personal computer 10 and the communication terminal 20 (S21, synchronous data transmission step).

  Subsequently, the synchronization data transmission unit 15 determines whether or not synchronization has been completed for all communication terminals 20 with which communication connection has been established (S22, synchronization data transmission step). When it is determined that the synchronization has been completed for all the communication terminals 20 (YES in S22), the subsequent processing is not performed and the processing ends.

  If it is determined that the synchronization has not been completed for all the communication terminals 20 (NO in S22), then, the synchronization data transmission unit 15 performs synchronization target data (existing data) stored in the communication terminal 20 ) List is acquired (S23, synchronous data transmission step).

  Subsequently, the synchronization data transmitting unit 15 compares the list with the correspondence table shown in FIG. 2 generated by the synchronization data storage unit 13, and the data included in the correspondence table but not included in the list. A difference is extracted (S24, synchronous data transmission step). When the difference is not extracted (NO in S24), the synchronization process for the communication terminal 20 ends, and the processes after S22 are repeated.

  When the difference is extracted (YES in S24), the synchronous data transmission unit 15 refers to the link of the data related to the difference, and the backup data referenced by the link is read and transmitted to the communication terminal 20. (S25, synchronous data transmission step). By the transmission, the synchronization process for the communication terminal 20 in the personal computer 10 is finished, and the processes after S22 are repeated. In the communication terminal 20, data transmitted from the personal computer 10 is received and stored as synchronized data.

For example, the following information is acquired as a list of data to be synchronized stored in the communication terminal 20.
/storage/sdcard/sync/a.jpg
/storage/sdcard/sync/b.jpg
/storage/sdcard/sync/01.mp3
Further, the synchronization target data managed in the correspondence table shown in FIG. 2 is as follows.
C: \ Users \ Users \ Documents \ sync \ a.jpg
C: \ Users \ Users \ Documents \ sync \ b.jpg
C: \ Users \ Users \ Documents \ sync \ c.jpg
C: \ Users \ Users \ Documents \ sync \ 01.mp3

The above is compared, the following is determined to be a difference, the backup data related to the difference is read and transmitted to the communication terminal 20.
C: \ Users \ Users \ Documents \ sync \ c.jpg
C: \ Users \ Users \ Documents \ sync \ 02.mp2
The above is the processing when the communication terminal 20 uses the data stored in the personal computer 10 to perform synchronization.

  Subsequently, processing when the synchronization data (link) is deleted in the personal computer 10 will be described with reference to the flowchart of FIG. In this case, the personal computer 10 deletes the synchronization data (link). This deletion is performed based on a user operation, for example. In this process, deletion of the synchronization data is detected by the data update unit 16 (S31, data update step).

  Subsequently, the data update unit 16 determines whether the deleted data is a file or a folder (S32, data update step). If it is determined that the deleted data is a file (NO in S32), the data update unit 16 sets the deletion column of the synchronization side of the record corresponding to the file in the correspondence table illustrated in FIG. (Deletion mark is given) (S33, data update step).

  When it is determined that the deleted data is a folder (YES in S32), the data update unit 16 sets the deletion column of the synchronization side of the record corresponding to the folder in the correspondence table illustrated in FIG. (Deletion mark is given) (S34, data update step). In addition, the synchronization side deletion column of the record corresponding to the file and the folder included in the folder is set to “delete” (deletion mark is given) (S35, data update step).

  After S33 and S35, at a regular timing, the data update unit 16 searches the correspondence table for a record in which the synchronization side deletion column is set to “deleted”, and includes a folder corresponding to the record. Data (actual data) is deleted (S36, data update step). The above is the process when the synchronization data (link) is deleted in the personal computer 10.

  Subsequently, processing when editing of backup data (actual data) in the personal computer 10 will be described with reference to the flowchart of FIG. In this case, the personal computer 10 edits the backup data (actual data). This editing is performed based on a user operation, for example. In this process, the data update unit 16 detects that the backup data has been edited (S41, data update step). Subsequently, the data update unit 16 acquires hash information of the file that is the backup data after editing, and updates the file hash column of the record corresponding to the file in the correspondence table illustrated in FIG. 2 with the acquired hash information. (S42, data update step). Subsequently, the data update unit 16 sets the file as a synchronization target again (S43, data update step). The above is the processing when the backup data (actual data) is edited in the personal computer 10.

  Next, processing when the file name of the synchronization data (link) is changed in the personal computer 10 will be described using the flowchart of FIG. In this case, the personal computer 10 changes the file name of the synchronization data (link). The file name is changed based on, for example, a user operation. In this process, the data update unit 16 detects a change in the file name of the synchronization data (S51, data update step). Subsequently, the data update unit 16 acquires the file ID of the file that is the backup data linked by the synchronization data (S52, data update step).

  Subsequently, the data update unit 16 determines whether or not a record including the file ID of the file exists in the correspondence table shown in FIG. 2 (S53, data update step). When the record including the file ID does not exist in the correspondence table (NO in S53), the subsequent processing is not performed and the processing ends.

  When a record including the file ID exists in the correspondence table (YES in S53), the data update unit 16 updates the link file column of the record with the updated file name (S54, data update step). Subsequently, hash information of the file is acquired by the data update unit 16 (S55, data update step). Subsequently, the data update unit 16 compares the acquired hash information with the hash information of the record corresponding to the file in the correspondence table shown in FIG. 2 (file hash column information) (S56, data update). Step). If they match (YES in S56), the subsequent processing is not performed and the processing ends.

  If they do not match (NO in S56), the data update unit 16 updates the file hash sequence of the record with the acquired hash information (S57, data update step). Subsequently, the data update unit 16 sets the file as a synchronization target again (S58, data update step). The above is the processing when the file name of the synchronization data (link) is changed in the personal computer 10.

  As described above, in the present embodiment, both backup and synchronization of data stored in the communication terminal 20 can be performed. In the present embodiment, synchronization is performed with reference to a link to backup data. Therefore, it is not necessary to store actual data for synchronization. That is, it is not necessary to store the actual data for backup and the actual data for synchronization in duplicate. Thus, according to the present embodiment, efficient data storage can be performed when both data backup and synchronization are performed.

  In addition, as in the present embodiment, processing for the other data may be performed in response to detection of processing for either backup data or synchronization data. According to this configuration, the synchronization data and the backup data can be matched. Thereby, synchronization and backup can be performed more appropriately.

  For example, when the synchronization data is deleted, the corresponding backup data may be deleted. The user usually thinks that he does not want to back up manually deleted data again. Therefore, according to this configuration, it is possible to prevent unintended backup of data intended to be deleted by the user.

  Further, when backup data (actual data) is edited, the corresponding synchronization data may indicate that the backup data should be newly synchronized. Thereby, even when the data before editing has already been synchronized, the data after editing is newly synchronized. That is, according to this configuration, the edited data can be appropriately synchronized.

  Further, the synchronization data may be generated according to the type of data as in the present embodiment. According to this configuration, synchronization can be performed only for necessary types of data. Thereby, synchronization can be performed more appropriately.

  DESCRIPTION OF SYMBOLS 10 ... Personal computer, 11 ... Reception part, 12 ... Backup data storage part, 13 ... Synchronization data storage part, 14 ... Backup data transmission part, 15 ... Synchronization data transmission part, 16 ... Data update part, 101 ... CPU, 102 ... RAM , 103 ... ROM, 104 ... communication module, 105 ... auxiliary storage device, 20 ... communication terminal.

Claims (6)

Receiving means for receiving data stored in the terminal from the terminal;
Backup data storage means for storing data received by the receiving means as backup data for each receiving terminal;
Creating a link to data stored by the backup data storage means, and storing the link as data for synchronization between terminals;
A backup data transmission unit that receives a backup data transmission request including information for specifying a terminal, reads backup data stored in association with the terminal by the backup data storage unit, and transmits the backup data to the request source;
Synchronous data transmission means for reading the backup data linked by the synchronization data stored by the synchronous data storage means and stored by the backup data storage means, and transmitting it to the terminal to be synchronized;
A data management device comprising:   Detecting processing for the synchronization data stored by the synchronization data storage means, and performing processing for the backup data linked by the synchronization data and stored by the backup data storage means in response to the detection, or Data update for detecting processing for backup data stored by the backup data storage means and performing processing for the synchronization data stored by the synchronous data storage means while being a link to the backup data in response to the detection The data management apparatus according to claim 1, further comprising means.   The data update means detects that the synchronization data stored by the synchronization data storage means has been deleted, and the backup data linked by the synchronization data and stored by the backup data storage means in response to the detection The data management device according to claim 2, wherein the data is deleted.   The data update means detects that the backup data stored by the backup data storage means has been edited, and is a link to the backup data and stored by the synchronous data storage means in response to the detection. 4. The data management apparatus according to claim 2, wherein the synchronization data indicates that the backup data should be newly synchronized.   The data management apparatus according to any one of claims 1 to 4, wherein the synchronous data storage unit creates a link to the data according to a type of data received by the receiving unit. A data management method, which is an operation method of a data management device,
A receiving step of receiving data stored in the terminal from the terminal;
A backup data storage step for storing the data received in the reception step as backup data for each terminal of the reception source;
Creating a link to the data stored in the backup data storage step, and storing the link as data for synchronization between terminals; and
A backup data transmission step of receiving a backup data transmission request including information identifying the terminal, reading the backup data stored in association with the terminal in the backup data storage step and transmitting it to the request source;
A synchronization data transmission step of reading the backup data linked by the synchronization data stored in the synchronization data storage step and stored in the backup data storage step, and transmitting it to the terminal to be synchronized;
Data management method.

Images