JP5656722B2 - Data synchronization apparatus, data synchronization system, data synchronization method and program - Google Patents

Description

  The present invention relates to a data synchronization apparatus, a data synchronization system, a data synchronization method, and a program.

  Data synchronization is performed among a plurality of computers. For example, data such as photos and phone books recorded on a mobile phone is synchronized with a server to back up the data or to share data among a plurality of devices. The data depends on other data. However, the data may refer to other data. In such a case, synchronization is performed so as not to break the relationship of the data. For example, when transmitting the second data referring to the first data, the first data can also be transmitted (see Patent Document 1). Such synchronization processing is normally processed atomically, and if the transmission of the first data fails, the synchronization processing as a whole fails regardless of whether the transmission of the second data is successful or not. Is done.

JP 2005-25362 A

  However, if the entire synchronization process is unsuccessful due to the failure of the transmission of the first data, the second data cannot be used even if the transmission of the second data is successful.

  The present invention has been made in view of such a background, and provides a data synchronization apparatus, a data synchronization system, a data synchronization method, and a program capable of increasing the availability of data in synchronization of data having a reference relationship. For the purpose.

  A main invention of the present invention for solving the above-described problem is an apparatus for synchronizing data with a server that stores data, wherein the first data and the first data are referred to. A data storage unit that stores second data in which reference information indicating the data is set, the first and second data stored in the server, and the acquired first and second data When the acquisition of the first data fails, the synchronization processing unit for registering the data in the data storage unit and the setting of the reference information from the second data are canceled, and the first data A data changing unit that sets inconsistency information indicating that acquisition has failed in the second data.

  In the data synchronization apparatus of the present invention, the synchronization processing unit registers the second data in which the inconsistency information is set in the data storage unit when the acquisition of the first data is successful. If it is, the second data may be acquired from the server.

  Further, the data synchronization apparatus of the present invention includes a failure data storage unit that stores data specifying information for specifying data that has failed to be acquired, and the synchronization processing unit, when the acquisition of the first data fails, The data specifying information for specifying the first data is registered in the failure data storage unit, and the data changing unit stores the data specifying information for each of the data specifying information registered in the failure data storage unit. The second data for which the corresponding reference information is set is searched from the data storage unit, the setting of the reference information is canceled from the searched second data, and the inconsistency information is set. It may be.

  According to another aspect of the present invention, there is provided a system for synchronizing data between a server and a client communicably connected to the server, wherein the client includes first data, first data A client data storage unit that stores data and second data in which reference information indicating the first data is set, and the first and second data stored in the client data storage unit A client synchronization processing unit for uploading to the server, the server storing a server data storage unit for storing the first and second data, and the first and second data uploaded from the client The server synchronization processing unit registered in the received server data storage unit and the second data when the reception of the first data fails. A server data changing unit that cancels the setting of the reference information from the data, and the client synchronization processing unit uploads the first data again when the uploading of the first data fails, When re-uploading of the first data is successful, the second data in which the reference information for specifying the first data is set is read from the client data storage unit, and the read second data is read Upload to the server again.

  Further, in the data synchronization system of the present invention, the data includes a header part, the reference information is included in the header part, and the client synchronization processing unit has succeeded in uploading the first data again, Only the header part of the second data may be uploaded to the server again.

  In the data synchronization system of the present invention, the server includes a failure data storage unit that stores data specifying information that specifies data that failed to be uploaded, and the server synchronization processing unit is set to the second data. When the data specifying information for specifying the first data indicated by the reference information is registered in the failure data storage unit, the setting of the reference information may be canceled.

  In the data synchronization system of the present invention, an update time is set for the first and second data, and the client stores an anchor time that is the last time the data is uploaded to the server. When the second upload of the first time data and the anchor time storage unit succeeds, the client data storage unit is searched for the second data in which the reference information indicating the first data is set, An update time update unit that updates the update time of the searched second data to a time that is newer than the anchor time, wherein the client synchronization processing unit is set with the update time after the anchor time. The first and second data may be uploaded to the server.

  In the data synchronization system of the present invention, the client further includes a failure data storage unit that stores data specifying information for specifying the first data that has failed to be uploaded, and the client synchronization processing unit further includes the failure data The first data specified by the data specifying information stored in the storage unit may be uploaded to the server.

  According to another aspect of the present invention, there is provided a method for synchronizing data with a server storing data, wherein the first data refers to the first data and indicates the first data. A computer including a data storage unit that stores second data in which reference information is set acquires the first and second data stored in the server, and the acquired first and second data When registering data in the data storage unit and failing to acquire the first data, the setting of the reference information is canceled from the second data, and acquisition of the first data has failed Is set in the second data.

  Another aspect of the present invention is a method of synchronizing data between a server and a client that is communicably connected to the server, and refers to the first data and the first data. The client includes a client data storage unit that stores second data in which reference information indicating the first data is set. The first and second data stored in the client data storage unit. The server having a server data storage unit for storing the first and second data is received by the server, and the server receives the first and second data uploaded from the client. When registration with the data storage unit fails to receive the first data, the setting of the reference information is canceled from the second data, and the first data If the uploading of the first data fails, the first data is uploaded again. If the uploading of the first data succeeds again, the reference information for specifying the first data is set in the second data. Are read from the client data storage unit, and the read second data is uploaded to the server again.

  According to another aspect of the present invention, there is provided a program for synchronizing data with a server storing data, wherein the first data refers to the first data. The first and second data stored in the server are acquired by a computer including a data storage unit that stores second data in which reference information indicating the second information is set, and the acquired first and second data Registering the second data in the data storage unit, and when the acquisition of the first data fails, the setting of the reference information is canceled from the second data, and the acquisition of the first data And the step of setting inconsistency information indicating the failure of the second data to the second data.

  Other problems and solutions to be disclosed by the present application will be made clear by the embodiments of the invention and the drawings.

  ADVANTAGE OF THE INVENTION According to this invention, the availability of data can be improved in the synchronization of the data which have a reference relationship.

It is a figure which shows the whole structure of the data synchronization system of this embodiment. FIG. 3 is a diagram for explaining a configuration example of synchronization data 40; 2 is a diagram illustrating a hardware configuration example of a general computer 11 used for a client 10 and a server 20. FIG. 2 is a diagram illustrating an example of a software configuration of a client 10. FIG. 3 is a diagram illustrating a configuration example of a synchronization data storage unit 131 and synchronization data 40. FIG. 2 is a diagram illustrating an example of a software configuration of a server 20. FIG. It is a figure explaining the flow of the synchronous process in a data synchronous system. It is a figure which shows the flow of a download process. It is a figure which shows the flow of the resolution process of a collision. It is a figure which shows the flow of a registration process of the synchronous data 40 by the client 10. FIG. It is a figure which shows the flow of an upload process. It is a figure which shows the flow of a registration process of the synchronous data 40 by the server 20. FIG. It is a figure which shows the flow of an inconsistency cancellation process.

== System configuration ==
Hereinafter, a data synchronization system according to an embodiment of the present invention will be described. FIG. 1 is a diagram showing the overall configuration of the data synchronization system of the present embodiment. The data synchronization system of the present embodiment includes a client 10 and a server 20. The client 10 is, for example, a mobile phone, a personal computer, a workstation, a PDA (Personal Digital Assistant) that manages various data such as text data and image data. The server 20 synchronizes data with the client 10 in order to back up data stored in the client 10 or share data among the plurality of clients 10, for example, a personal computer or a workstation Etc. The client 10 and the server 20 are connected to be communicable with each other via the communication path 30. The communication path 30 is, for example, the Internet or a LAN (Local Area Network), and is configured by Ethernet (registered trademark), a public telephone line, a mobile phone line, a wireless communication path, and the like.

  Data is synchronized between the client 10 and the server 20. Data synchronized between the client 10 and the server 20 may be set to a reference to other data related to the data. For example, if a file is managed for each folder, a reference to the folder is set for the file, and if the folder has a hierarchical structure, a reference to the upper folder is set for the lower folder. The When a tag is set for an image, a reference to the tag is set for the image, and a record of a table in which a relation is defined in a relational database management system (RDBMS) has a reference to a record of another table. Is set. It is assumed that the data synchronization system of this embodiment synchronizes data having such a reference relationship.

  FIG. 2 is a diagram for explaining a configuration example of the synchronization data 40. The synchronization data 40 includes a header part 41 and a body part 42. In the header part 41, information for specifying the synchronization data 40 (hereinafter referred to as “GUID411 (Global Unique IDentification)”) is set. Information (hereinafter referred to as “reference ID 412”) indicating other synchronization data 40 referred to by the synchronization data 40 can be set. In the present embodiment, in order to simplify the description, data synchronized between the client 10 and the server 20 (hereinafter referred to as “synchronized data 40”) includes image data for displaying an image, and an image. It is assumed that the tag data indicates a tag to be set in. In the example of FIG. 2, a reference ID 412 indicating tag data 1 is set in the header portion 41 of the image data 2. The relationship between the tag data 1 and the image data 2 is a one-to-many relationship, and the reference ID 412 is set only for the image data 2 and not set for the tag data 1.

Even if the synchronization of the tag data 1 fails, the data synchronization system of this embodiment temporarily cancels the reference from the image data 2 to the tag data 1 when the synchronization of the image data 2 succeeds. Thus, the image data 2 itself can be used by the user.
Details will be described below.

== Hardware configuration ==
FIG. 3 is a diagram illustrating a hardware configuration example of a general computer 11 (information processing apparatus) used for the client 10 and the server 20. The computer 11 includes a CPU 101, a memory 102, a storage device 103, a communication interface 104, an input device 105, and an output device 106. The storage device 103 is, for example, a hard disk drive or a flash memory that stores various data and programs. The CPU 101 implements various functions by reading a program stored in the storage device 103 into the memory 102 and executing it. The communication interface 104 is an interface to the communication path 30, for example, an adapter for connecting to Ethernet (registered trademark), a modem for connecting to a telephone line network, a wireless communication apparatus for connecting to a wireless communication path, etc. It is. The input device 105 is, for example, a keyboard, a mouse, a touch panel, a button, a dial, or a microphone that receives data input from a user. The output device 106 is, for example, a display, a speaker, or a printer that outputs data to the user.

== Client 10 ==
FIG. 4 is a diagram illustrating a software configuration example of the client 10. The client 10 includes a synchronization processing unit 111, a header changing unit 112, a tag data storage 131, an anchor storage unit 132, a download failure ID storage unit 133, and an upload failure ID storage unit 134. The synchronization processing unit 111 and the header changing unit 112 are realized by the CPU 101 included in the client 10 reading out the program stored in the storage device 103 to the memory 102 and executing it. The synchronous data storage unit 131, the anchor storage unit 132, the download failure ID storage unit 133, and the upload failure ID storage unit 134 are realized as a part of the storage area provided by the memory 102 and the storage device 103 provided in the client 10.

  The synchronization data storage unit 131 stores the synchronization data 40. FIG. 5 is a diagram illustrating a configuration example of the synchronization data storage unit 131 and the synchronization data 40. As described above, the tag data 1 and the image data 2 are stored as the synchronization data 40 in the synchronization data storage unit 131, and the synchronization data 40 includes the header part 41 and the body part 42. The header part 41 includes a GUID 411 of the synchronization data 40, a creation time 413 and an update time 414 of the synchronization data 40. The creation time point 413 and the update time point 414 can be, for example, date and time, or can be serial values that increase each time data is created or updated. One of the two synchronization data 40 having a relationship includes a GUID for specifying the other synchronization data 40 as a reference ID 412 in the header portion 41. As described above, in the present embodiment, the image data 2 includes the GUID of the tag data 1 to be referenced as the reference ID 412 in the header portion 41, but the tag data 1 includes the reference ID 412 to the image data 2. It is assumed that the reference ID 412 for the image data 2 may be included in the tag data 1. Although a plurality of reference IDs 412 can be set, in the present embodiment, it is assumed that only one reference ID 412 can be set in the header portion 41 in order to simplify the description. Further, inconsistency ID 415 can be set in header section 41. The inconsistency ID 415 is a GUID indicating the tag data 1 that is set in place of the reference ID 412 when downloading of the tag data 1 indicated by the reference ID 412 fails, as will be described later.

  The anchor storage unit 132 stores a time point when the last synchronization process was performed (hereinafter referred to as “anchor time point”). The anchor time may be a date and time, or may be a serial value that increases every time the synchronization data 40 is created or updated or synchronization processing is performed.

  The download failure ID storage unit 133 stores the GUID of the synchronization data 40 that has failed to be downloaded from the server 20. The upload failure ID storage unit 134 stores the GUID of the synchronization data 40 that failed to be uploaded to the server 20.

  The synchronization processing unit 111 synchronizes the synchronization data 40 with the server 20. In the present embodiment, the synchronization processing unit 111 downloads the synchronization data 40 created or updated in the server 20 after the anchor time from the server 20 and also created or updated in the client 10 after the anchor time. The synchronization process is performed by uploading 40 to the server 20. To download the synchronization data 40, the synchronization processing unit 111 transmits a command (hereinafter referred to as “download request”) requesting to download the synchronization data 40 to the server 20 and transmits it from the server 20 in response to the download request. Synchronization data 40 to be received is received. The anchor point is set in the download request. Further, a GUID indicating the synchronization data 40 to be downloaded can be set in the download request. The server 20 responds with synchronization data 40 created or updated after the anchor point set in the download request, and if a GUID is set in the download request, the synchronization data 40 corresponding to the GUID also responds. Is done. In the present embodiment, description of processing related to general synchronization processing is omitted, but of course, the synchronization processing unit 111 can perform various processing related to general synchronization processing.

  Downloading and uploading the synchronization data 40 may fail. For example, when an error occurs in the communication path 30 or when an error occurs when recording the synchronization data 40, restrictions on the communication amount and storage capacity are set, and the downloaded or uploaded synchronization data 40 is Downloads and uploads may fail if restrictions are violated. In this embodiment, for the sake of simplicity, the synchronization data 40 to be downloaded or uploaded is synchronized with an error in the communication path 30 after exchange between the client 10 and the server 20. It is assumed that downloading or uploading fails when all of the data 40 cannot be received.

  The synchronization processing unit 111 registers the GUID of the failed synchronization data 40 in the download failure ID storage unit 133 when the download of the synchronization data 40 fails, and fails when the upload of the synchronization data 40 fails. The GUID of the synchronization data 40 is registered in the upload failure ID storage unit 134. As will be described later, the synchronization processing unit 111 uploads the synchronization data 40 whose GUID is registered in the upload failure ID storage unit 133 again even if the update time is before the anchor time. Further, the synchronization processing unit 111 explicitly downloads the synchronization data 40 in which the inconsistency ID 415 is set in the header unit 41 regardless of the update time. Details of the synchronization process of the synchronization data 40 will be described later.

  The header changing unit 112 deletes the reference ID 411 from the header part 41 of the other synchronization data 40 referring to the synchronization data 40 when the download of the synchronization data 40 fails, and is set to the reference ID 411 The GUID is set in the header part 41 as the inconsistency ID 415. When the synchronization data 40 is successfully downloaded, the header changing unit 112 deletes the inconsistency ID 415 and sets the inconsistency ID 415 for the synchronization data 40 in which the GUID of the synchronization data 40 is set as the inconsistency ID 415. The set GUID is set as the reference ID 411.

  The header changing unit 112 sets the GUID as the reference ID 411 when the upload of a certain synchronization data 40 is successful and the GUID of the synchronization data 40 is registered in the upload failure ID storage unit 134. The update time 414 is set after the anchor time so that the synchronized data 40 being uploaded is also uploaded.

== Server 20 ==
FIG. 6 is a diagram illustrating a software configuration example of the server 20. The server 20 includes a synchronization processing unit 211, a header change unit 212, a synchronization data storage unit 231, and a failure ID storage unit 232. The synchronization processing unit 211 and the header changing unit 212 are realized by the CPU 101 included in the server 20 reading out the program stored in the storage device 103 to the memory 102 and executing it. The synchronous data storage unit 231 and the failure ID storage unit 232 are realized as part of a storage area provided by the memory 102 or the storage device 103 provided in the server 20.

  The synchronization data storage unit 231 stores the synchronization data 40. The synchronous data storage unit 231 has the same configuration as the synchronous data storage unit 131 of the client 10 shown in FIG.

  The failure ID storage unit 232 stores the GUID of the synchronization data 40 for which uploading from the client 10 has failed.

  The synchronization processing unit 211 synchronizes the synchronization data 40 with the client 10. When the synchronization processing unit 211 receives a download request from the client 10, the synchronization processing unit 211 searches the synchronization data storage unit 231 for the synchronization data 40 that has a newer creation time or update time than the anchor time included in the download request. Data 40 is transmitted to the client 10. Further, when a GUID is set in the download request, the synchronization processing unit 211 reads the synchronization data 40 corresponding to the GUID from the synchronization data storage unit 231 and transmits it to the client 10.

  Further, when the synchronization data 40 is uploaded from the client 10, the synchronization processing unit 211 receives the uploaded synchronization data 40 and registers it in the synchronization data storage unit 231, and the GUI ID of the synchronization data 40 is the failure ID. If it is registered in the storage unit 232, the GUID is deleted from the failure ID storage unit 232. When the upload of the synchronization data 40 fails, the synchronization processing unit 211 registers the GUID of the synchronization data 40 in the failure ID storage unit 232. Note that the synchronization processing unit 211 can also perform general synchronization processing.

  When the synchronization data 40 including the GUID stored in the failure ID storage unit 232 as the reference ID 412 in the header unit 41 is registered in the synchronization data storage unit 232, the header changing unit 212 stores the header data 41 of the synchronization data 40. The reference ID 412 is deleted.

== Synchronous processing ==
Hereinafter, a synchronization process of the synchronization data 40 in the data synchronization system of the present embodiment will be described. FIG. 7 is a diagram for explaining the flow of synchronization processing in the data synchronization system. In the synchronization process in the data synchronization system, a download process for downloading the synchronization data 40 from the server 20 to the client 10 is performed (S501), a collision resolution process is performed in the client 10 (S502), and the synchronization data downloaded in the client 10 is downloaded. 40 registration processes are performed (S503). Next, upload processing of the synchronization data 40 from the client 10 to the server 20 is performed (S504), registration processing of the synchronization data 40 uploaded in the server 20 is performed (S505), and the inconsistency ID 415 is set. Update processing (inconsistency elimination processing) of the synchronization data 40 is performed (S506). Finally, the anchor point in the client 10 is updated to a new point (for example, the present point of time or the latest point in time of creation or update of the downloaded or uploaded synchronization data 40) (S507). .

FIG. 8 is a diagram showing the flow of download processing in step S501 of FIG.
The synchronization processing unit 111 of the client 10 reads the anchor point from the anchor storage unit 132 (S521), and creates a download request in which the read anchor point is set (S522). The synchronization processing unit 111 reads the GUID stored in the download failure ID storage unit 133 and sets it as a download request (S523). The synchronization processing unit 111 searches the synchronization data storage unit 131 for the synchronization data 40 in which the inconsistency ID 415 is set and the GUID set in the inconsistency ID 415 is not registered in the download failure ID storage unit 133. (S524) If the synchronous data 40 is searched, the GUID of the synchronous data 40 is set in the download request (S525). The synchronization processing unit 111 transmits a download request to the server 20 (S526).
The synchronization processing unit 211 of the server 20 reads, from the synchronization data storage unit 231, the synchronization data 40 in which the creation time 413 or the update time 414 after the anchor time set in the download request received from the client 10 is set. (S527) The read synchronous data 40 is transmitted to the client 10 (S528).
The synchronization processing unit 111 of the client 10 receives the synchronization data 40 from the server 20 (S529), and if there is synchronization data 40 that has failed to be received, the GUI of the failed synchronization data 40 is stored in the download failure ID storage unit 133. Register (S530). The synchronization processing unit 111 creates a list of the synchronization data 40 that has been successfully downloaded (S531), and deletes the GUID of the synchronization data 40 that has been successfully downloaded from the download failure ID storage unit 133 (S532).
As described above, the server 20 includes the synchronization data 40 created or updated after the anchor time, the synchronization data 40 that failed to be downloaded last time, and the synchronization data 40 whose reference destination failed to download. Downloaded from.

  FIG. 9 is a diagram showing the flow of the collision elimination process in step S502 of FIG. The synchronization processing unit 111 of the client 10 performs the following processing for each of the synchronization data 40 that has been successfully downloaded. The synchronization processing unit 111 determines whether or not a collision has occurred in the synchronization data 40 (S541). Data collision means that data has been updated in each of two devices that are synchronizing data. In the present embodiment, when the synchronization data 40 update time 414 downloaded from the server 20 and the update time 414 of the synchronization data 40 stored in the synchronization data storage unit 131 are both later than the anchor time, the collision occurs. Detected. When detecting a collision (S541: YES), the synchronization processing unit 111 determines which of the synchronization data 40 downloaded from the server 20 and the synchronization data 40 stored in the client 10 is prioritized (S542). . For example, the synchronization processing unit 111 may always prioritize either the synchronization data 40 of the server 20 or the client 10, or may determine which one is prioritized according to the update time point 414, You may make it receive designation | designated from a user. When the synchronization processing unit 111 determines to prioritize the synchronization data 40 stored in the client 10 (S543: YES), the synchronization processing unit 111 deletes the synchronization data 40 from the list (S544). In this way, the collision of the synchronization data 40 is resolved in the client 10.

  FIG. 10 is a diagram showing the flow of registration processing of the synchronization data 40 by the client 10 in step S503 of FIG. The synchronization processing unit 111 of the client 10 registers the synchronization data 40 included in the list in the synchronization data storage unit 131 (S561). The synchronization processing unit 111 reads the GUID from the download failure ID storage unit 133 (S562). For each of the read GUIDs, the header changing unit 112 sets the GUID as the inconsistent ID 415 in the synchronization data 40 in which the GUID is set in the reference ID 412 (S563), and refers to the synchronization data 40. The synchronous data storage unit 131 is updated so as to delete the ID 412 (S564). In this way, when the synchronization data 40 is downloaded, the downloaded synchronization data 40 is registered in the synchronization data storage unit 131, and the synchronization data 40 that refers to the synchronization data 40 that has failed to download is referred to. The ID 412 may be deleted and an inconsistent ID 415 may be set instead.

FIG. 11 is a diagram showing a flow of upload processing of the synchronization data 40 in step S504 of FIG.
The synchronization processing unit 111 of the client 10 reads the anchor time from the anchor storage unit 132 (S581), reads the synchronization data 40 that is newer in creation time 413 or update time 414 than the anchor time from the synchronization data storage unit 131 (S582), The synchronous data 40 corresponding to the GUID stored in the upload failure ID storage unit 134 is read from the synchronous data storage unit 131 (S583), and the read synchronous data 40 is transmitted to the server 20 (S584). The synchronization processing unit 111 deletes the GUID stored in the upload failure ID storage unit 134 (S585), and if there is synchronization data 40 that has failed to be transmitted, the GUI ID of the failed synchronization data 40 is uploaded to the upload failure ID storage unit 134. (S586).
On the other hand, the synchronization processing unit 211 of the server 20 receives the synchronization data 40 transmitted from the client 10 (S587), and if there is synchronization data 40 that has failed to be received, the GUI of the failed synchronization data 40 is indicated as a failure ID storage unit. It registers in H.232 (S588) and creates a list of synchronization data 40 that have been successfully received (S589).
As described above, the synchronization data 40 created or updated after the anchor point in the client 10 and the synchronization data 40 that failed to be uploaded last time are uploaded to the server 20.

  FIG. 12 is a diagram showing a flow of registration processing of the synchronization data 40 by the server 20 in step S505 of FIG. The synchronization processing unit 211 of the server 20 registers the synchronization data 40 included in the list in the synchronization data storage unit 231 (S601). The header changing unit 212 reads the GUID from the failure ID storage unit 232 (S602), and for each of the read GUIDs, the GUID is set as the reference ID 412 among the synchronization data 40 stored in the synchronization data storage unit 231. The reference ID 412 is deleted from the existing one (S603).

  FIG. 13 is a diagram showing the flow of inconsistency resolution processing by the client 10 in step S506 of FIG. The header changing unit 112 of the client 10 searches the synchronization data storage unit 131 for the synchronization data 40 for which the inconsistency ID 415 is set (S621), and each of the searched synchronization data 40 is set to the inconsistency ID 415. It is determined whether or not the GUID is registered in the upload failure ID storage unit 134 (S622). If not registered (S622: NO), the GUID set in the inconsistent ID 415 is set as the reference ID 412 in the header unit 41. It is set (S623), the inconsistency ID 415 is deleted (S624), and the update time 414 is updated to a time later than the anchor time (for example, the current time) (S625). As a result, the synchronous data 40 is uploaded to the server 20 in the next upload process. Since the server 20 has deleted the reference ID 412 from the header portion 41 of the synchronous data 40 that failed to be uploaded, the reference ID deleted by this upload is restored.

  As described above, according to the data synchronization system of the present embodiment, when synchronizing the synchronization data 40 having the reference relationship, even if the synchronization of the reference destination synchronization data 40 fails, the reference source temporarily The reference ID 412 from the synchronization data 40 can be deleted to release the reference relationship. In general, when synchronizing related data, an atomic synchronization process is performed. When synchronization of reference data fails, reference data synchronization also fails. According to the data synchronization system of the embodiment, even when the synchronization of the reference destination synchronization data 40 fails, the reference source synchronization data 40 can be continuously used. Therefore, the availability of the synchronization data 40 can be increased.

  Further, according to the data synchronization system of the present embodiment, the server 20 does not need to manage the download failure, and if the upload fails, the synchronization data referring to the failed synchronization data 40 It is only necessary to delete the reference ID 412 from 40. That is, the server 20 does not need to consider restoration of the reference relationship. Therefore, even when the server 20 synchronizes with many clients 10, the load of the server 20 for managing the reference relationship can be reduced.

  In the present embodiment, the number of clients 10 is one. However, a plurality of clients 10 and the server 20 may be synchronized. Moreover, you may comprise the server 20 by multiple units | sets.

  In the present embodiment, only the image data and the tag data are synchronized between the client 10 and the server 20, but, of course, reference to other data such as a folder and a record managed by a relational database management system. It is also possible to synchronize various data for which the ID 412 can be set.

  In the present embodiment, the tag data 1 and the image data 2 are assumed to have a one-to-many relationship, but may be a one-to-one relationship or a many-to-many relationship. . In the case of a many-to-many relationship, the reference ID 412 may not be set in the header portion 41 of the synchronization data 40 but may be set in data for managing the relationship (hereinafter referred to as “relationship data”). .

  In this embodiment, the reference ID 412 is set only for the image data 2, but the reference ID 412 for the image data 2 may be set for the tag data 1.

  In this embodiment, for the sake of simplicity, the synchronization data 40 to be downloaded or uploaded is synchronized with an error in the communication path 30 after exchange between the client 10 and the server 20. The download or upload failed when the data 40 could not be received. However, not only the error in the communication path 30 but, for example, when an error occurs when recording the synchronous data 40, the communication amount or the storage If a restriction on the capacity is set and the downloaded or uploaded synchronization data 40 violates this restriction, a download or upload failure may be detected.

  In the present embodiment, for the synchronous data 40 for which the inconsistent ID 415 has been set, when the upload of the synchronous data 40 corresponding to the GUID set in the inconsistent ID 415 is successful, the entire synchronous data 40 is restored again. Although uploading is assumed, only the header 41 may be uploaded. Further, when downloading and downloading the synchronization data 40, it is determined whether or not there is a difference in the body part 42. If there is a difference, the entire synchronization data 40 is downloaded or uploaded. If there is no difference, the header part 41 is downloaded. You may make it download or upload only. Furthermore, only the difference of the synchronization data 40 can be uploaded or downloaded.

  Further, in this embodiment, when the synchronization data 40 corresponding to the GUID set in the inconsistent ID 415 is successfully uploaded, the upload is performed again by updating the update time point 414. Step S625 may be omitted and uploading may not be performed.

  Further, in the present embodiment, when the download of the tag data 1 fails, the reference ID 411 is deleted from the header 41 of the image data 2 in which the GUID of the tag data 1 is set to the reference ID 412, and inconsistency is used instead. Although the ID 415 is set, the present invention is not limited to this, and the reference ID 412 may not be deleted and the inconsistent ID 415 may not be set. In this case, for example, when the upload of the synchronization data 40 corresponding to the GUID registered in the upload failure ID storage unit 134 is successful, an upload success ID storage unit for storing the GUID is provided, and the reference ID 412 is set. For those GUIDs registered in the upload success ID storage unit, uploading may be performed again.

  Although the present embodiment has been described above, the above embodiment is intended to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention can be changed and improved without departing from the gist thereof, and the present invention includes equivalents thereof.

DESCRIPTION OF SYMBOLS 1 Tag data 2 Image data 10 Client 20 Server 30 Communication path 40 Synchronization data 41 Header part 42 Body part 111 Synchronization processing part 112 Header change part 131 Synchronization data storage part 132 Anchor storage part 133 Download failure ID storage part 134 Upload failure ID storage Unit 211 synchronization processing unit 212 header changing unit 231 synchronization data storage unit 232 failure ID storage unit 411 GUID
412 Reference ID
413 Creation time 414 Update time 415 Inconsistency ID

Claims (11)

A device for synchronizing data with a server for storing data,
A data storage unit that stores first data and second data that refers to the first data and in which reference information indicating the first data is set;
A synchronization processing unit that acquires the first and second data stored in the server and registers the acquired first and second data in the data storage unit;
When the acquisition of the first data fails, the setting of the reference information is canceled from the second data, and inconsistency information indicating that the acquisition of the first data has failed is set to the second data. A data change part to be set in the data;
A data synchronizer comprising: The data synchronizer according to claim 1,
When the second data in which the inconsistency information is set is registered in the data storage unit when the synchronization processing unit has succeeded in obtaining the first data, the second processing unit Obtaining data from the server,
A data synchronizer characterized by the above. The data synchronization device according to claim 1 or 2,
A failure data storage unit for storing data specifying information for specifying data that has failed to be acquired;
If the acquisition of the first data fails, the synchronization processing unit registers the data specifying information for specifying the first data in the failure data storage unit,
For each of the data specifying information registered in the failure data storing unit, the data changing unit sends the second data in which the reference information corresponding to the data specifying information is set from the data storing unit. Searching, releasing the setting of the reference information from the searched second data, and setting the inconsistency information;
A data synchronizer characterized by the above. A system for synchronizing data between a server and a client communicably connected to the server,
The client
A client data storage unit that stores first data and second data that refers to the first data and in which reference information indicating the first data is set;
A client synchronization processing unit for uploading the first and second data stored in the client data storage unit to the server;
With
The server
A server data storage unit for storing the first and second data;
A server synchronization processing unit that receives the first and second data uploaded from the client and registers in the received server data storage unit;
A server data changing unit for releasing the setting of the reference information from the second data when reception of the first data fails;
With
The client synchronization processing unit uploads the first data again when the upload of the first data fails, and identifies the first data when the upload of the first data succeeds. Reading the second data set with the reference information from the client data storage unit and uploading the read second data to the server again;
A data synchronization system characterized by The data synchronization system according to claim 4,
The data includes a header part, and the reference information is included in the header part,
The client synchronization processing unit uploads only the header part of the second data to the server again when the first data upload succeeds;
A data synchronization system characterized by A data synchronization system according to any one of claims 4 and 5,
The server includes a failure data storage unit that stores data specifying information for specifying data that failed to be uploaded,
The server synchronization processing unit refers to the reference when the data specifying information for specifying the first data indicated by the reference information set in the second data is registered in the failure data storage unit. Canceling the information settings,
A data synchronization system characterized by The data synchronization system according to any one of claims 4 to 6,
An update time point is set in the first and second data,
The client
An anchor point storage unit that stores an anchor point that is a point of time when the data was last uploaded to the server;
When re-uploading of the first data is successful, the second data in which the reference information indicating the first data is set is retrieved from the client data storage unit, and the retrieved second data An update point update unit for updating the update point of data to a point newer than the anchor point;
The client synchronization processing unit uploads the first and second data set with the update time after the anchor time to the server;
A data synchronization system characterized by The data synchronization system according to claim 7, wherein
The client includes a failure data storage unit that stores data specifying information for specifying the first data that has failed to be uploaded,
The client synchronization processing unit further uploads the first data specified by the data specifying information stored in the failure data storage unit to the server;
A data synchronization system characterized by A method of synchronizing data with a server storing data,
A computer including a data storage unit that stores first data and second data in which reference information indicating the first data is set, which refers to the first data.
Acquiring the first and second data stored in the server, registering the acquired first and second data in the data storage unit;
When the acquisition of the first data fails, the setting of the reference information is canceled from the second data, and inconsistency information indicating that the acquisition of the first data has failed is set to the second data. To set the data,
A data synchronization method characterized by the above. A method of synchronizing data between a server and a client communicatively connected to the server,
The client comprising a client data storage unit that stores first data and second data that is set with reference information indicating the first data and that refers to the first data. Uploading the first and second data stored in the server to the server;
The server including a server data storage unit that stores the first and second data,
Receive the first and second data uploaded from the client, register in the received server data storage unit,
When the reception of the first data fails, the setting of the reference information is canceled from the second data,
When the upload of the first data fails, the first data is uploaded again. When the upload of the first data succeeds again, the reference information for specifying the first data is set. Reading the second data from the client data storage unit and uploading the read second data to the server again.
A data synchronization method characterized by the above. A program for synchronizing data with a server storing data,
A computer including a data storage unit that stores first data and second data that is set with reference information indicating the first data and that refers to the first data.
Acquiring the first and second data stored in the server, and registering the acquired first and second data in the data storage unit;
When the acquisition of the first data fails, the setting of the reference information is canceled from the second data, and inconsistency information indicating that the acquisition of the first data has failed is set to the second data. Steps to set the data,
A program for running.

Images