JP6229689B2 - Server and information processing system - Google Patents

Description

A server and an information processing system that can reduce the amount of communication during data synchronization in the server and the information processing system.

As a data synchronization method between the client and the server, there are a method of synchronizing all data every time synchronization is performed, and a method of acquiring a differential log (data change log such as journal) after the previous synchronization. However, in these methods, there is a problem that the communication amount (data amount) at the time of data synchronization is large and the response on the client side is lowered.

  In order to solve this problem, there can be considered a means for reducing the amount of communication by the client acquiring only the DB difference data (hereinafter referred to as difference data) after the previous synchronization. Specifically, the above-described difference log is generally configured by log output time, difference data, and additional information (log comment or the like). Of these components, the amount of additional information is generally large, so if synchronization can be achieved using only difference data, a reduction in the amount of communication can be expected.

  As a related technique related to a data change notification method from a server to a client, Patent Document 1 discloses the following apparatus and method. In the apparatus and method described in Patent Document 1, a plurality of data values are stored in a server, a subset of the plurality of data values is stored in a cache, and information for identifying an updated data value in the server is stored. The server processor periodically broadcasts the invalidation report it has to the client processor.

JP-A-7-248968

  However, in the synchronous method in which the client acquires only differential data after the previous synchronization, the client does not acquire additional information as compared with the method in which the differential log is acquired. Since the additional information includes data deletion information, in the method of acquiring only difference data, the data synchronization reference source data (hereinafter referred to as master data) is deleted on the server side with respect to data not included in the difference data. Or the client cannot determine if there was no update.

  An object of the present invention is to notify the client side whether or not the master data on the server side has been deleted even in the case of a synchronous method in which only the difference data is acquired by the client.

  The server according to the present invention includes an output unit that synchronizes data with a client and outputs update information that is used for synchronization and has first and second areas. In the case of data deletion, The second area includes data information and deletion notification information. When data is added or changed, the second area includes data information.

  An information processing system according to the present invention includes an output unit that synchronizes data between a server and a client and outputs update information that is used for synchronization and includes first and second areas. In the case of deletion, update information has data information and deletion notification information written in the second area, and in the case of addition or change of data, update information has data information written in the second area. It is characterized by being.

  The data synchronization method of the present invention synchronizes data with a client, outputs update information having first and second areas used for synchronization, and updates data in the case of data deletion. The data information and the deletion notification information are described in the second area, and in the case of addition or change of data, the update information includes the data information in the second area.

By reducing the amount of communication during data synchronization between the client and server, and shortening the synchronization time, the response on the client side can be improved. Even if the amount of communication is reduced, the client side can be notified that the master data has been deleted on the server side, so that data synchronization can be performed appropriately.

It is a figure which shows the process structural example of the information processing system in 1st embodiment of this invention. It is a figure which shows the physical structural example of the information processing system in 1st embodiment of this invention. 4 is a flowchart showing an operation when data on the server side is deleted (FIG. 3a) and an operation when data is added / changed (FIG. 3b) in the information processing system according to the first embodiment of the present invention. . It is a figure which shows the process structural example of the server in 1st embodiment of this invention. It is a figure which shows the process structural example of the information processing system in 2nd embodiment of this invention. It is a figure which shows the structural example of the data on DB of the server in 2nd embodiment of this invention. It is a figure which shows the structural example of the data on local DB of the client in 2nd embodiment of this invention. It is a timing chart which shows operation | movement of the information processing system in 2nd embodiment of this invention. It is a timing chart which shows operation | movement of the information processing system in 2nd embodiment of this invention. It is a flowchart which shows operation | movement of the information processing system in 2nd embodiment of this invention. It is a figure which shows the structural example of the data on DB of the server in other embodiment of this invention.

[First Embodiment] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.
[Description of Configuration] Referring to FIG. 1, an information processing system 100 according to the first embodiment includes a server 10 and a client 20.

  Referring to FIG. 2, the server 10 and the client 20 can be realized with the following configuration, for example. The hardware that constitutes the server 10 and the client 20 includes a CPU (Central Processing Unit) 1, a memory 2, a hard disk drive (HDD) 3, an input / output interface (I / F) 4, and a communication device 5. The functions of the server 10 and the client 20 are realized by, for example, the CPU 1 executing a computer program (software program, hereinafter simply referred to as “program”) read into the memory 2. In execution, the CPU 1 appropriately controls the input / output I / F 4 and the communication device 5.

  Note that the present invention, which will be described using the present embodiment and each embodiment described later as an example, may be configured by a non-volatile storage medium such as a compact disk in which the program is stored. The program stored in the storage medium is read by a drive device (not shown), for example.

  The communication executed by the server 10 and the client 20 is realized by the application program controlling the communication device 5 using a function provided by an OS (Operating System), for example. The server 10 and the client 20 may be configured by connecting two or more physically separated devices in a wired or wireless manner.

  The hardware configuration example shown in FIG. 2 is also applicable to each embodiment described later. The server 10 and the client 20 may be dedicated devices. Note that the hardware configurations of the server 10 and the client 20 and their functional blocks are not limited to those described above.

  Referring to FIG. 1 again, the server 10 is communicably connected to the client 20 and synchronizes data with the client 20. The server 10 includes an output unit 10 a that outputs update information having first and second areas used for synchronization with the client 20.

  In the update information output by the output unit 10a, for example, authentication information added for each synchronization process is described in the first area. The authentication information is, for example, application authentication information used during synchronization or a synchronization session token. When the update content includes data deletion, in the update information output by the output unit 10a, data information and deletion notification information are described in the second area. The data information is information indicating, for example, updates that have occurred since the previous synchronization of the data to be synchronized with the client 20 among the data on the server 10 side. The information indicating update is, for example, information (ID) for specifying data, the field name of the updated field, and the value of the updated field. Examples of field names mainly include product names, number, access authority for each data, and the like as updated by users accessing the client 20 and the server 10. Further, as data that is automatically updated mainly by the server 10 and the client 20, there are data update date and time, data creation date and time, and the like. The deletion notification information includes information indicating that this data is deleted by the server 10 or that corresponding data held by the client 20 is deleted. Further, in the update information, when the update content is only addition or change of data, the data information is described in the second area.

  The client 20 is communicably connected to the server 10. The client 20 receives the update information output from the output unit 10a and performs data synchronization based on the update information.

  [Description of Operation] Referring to FIG. 3a, the information processing system 100, in STEP 31a, when the data to be synchronized with the client 20 is deleted from the data in the server 10 (server-side data deletion), in STEP 32a, The output unit 10a generates and outputs update information in which the data information and the deletion notification information are described in the second area (update information output).

  Referring to FIG. 3b, the information processing system 100 outputs the data in STEP 32b when the data to be synchronized with the client 20 is updated or added (data change / addition on the server side) in STEP 31b. The unit 10a generates and outputs update information in which data information is described in the second area (update information output).

  [Description of Effects] The information processing system 100 according to the present embodiment generates and outputs update information in which deletion notification information is described in the same second area as data information. Based on this update information, the client 20 performs data synchronization. For this reason, compared with data synchronization using a difference log, additional information with large data can be synchronized without communication between the server 10 and the client 20.

[Second Embodiment] An embodiment of the information processing system 110 will be described with reference to FIG.
[Description of Configuration] The information processing system 110 includes a server 11 and a client 21. In the following description, the system is constituted by one server 11 and one client 21. However, the server 11 and a plurality of clients 21 may be connected.

  The server 11 includes a transmission / reception unit 11a, a database (DB) 11b, a data monitoring unit 11c, and a data control unit 11d. The transmission / reception unit 11a is communicably connected to the transmission / reception unit 21a of the client 21. The transmission / reception unit 11a is connected to the data control unit 11d and transmits the difference data received from the data control unit 11d to the transmission / reception unit 21a of the client 21. In addition, the transmission / reception unit 11 a receives a synchronization request from the transmission / reception unit 21 a of the client 21 to the server 11. In the DB 11b, data is changed / deleted by the data control unit 11d.

  The data monitoring unit 11c monitors the scheduled deletion date of data on the DB 11b via the data control unit 11d, and causes the data control unit 11d to delete data that has passed the scheduled deletion date. The data control unit 11d reads the data on the DB 11b, outputs the data update to the transmission / reception unit 11a as difference data including a cache validity period and a deletion flag, which will be described later. Further, the data control unit 11d changes / deletes data on the DB 11b of the server 11.

  Referring to FIG. 6, each data on the DB 11 b is provided with fields of a cache valid period 30, a scheduled deletion date 40, and a deletion flag 50 in addition to normal fields such as ID, data, data creation date / time, and update date / time. It has been. The cache valid period 30 defines a period in which the data is valid on the client 21 side for each data. As will be described later, for example, a cache validity period 32 obtained by adding the cache validity period 30 to the current time at the time of setting is set for the data held on the cache validity period client 21 side, as will be described later. Data is used on the client 21 side within this time limit. The cache valid period 30 may be set separately for each data, or the same period may be set for all data. Further, the value of this field is cleared at the timing when a deletion flag 50 described later is set. The deletion flag 50 indicates whether the data is normal data or temporary deletion data. In the present embodiment, it is assumed that when the value of the deletion flag 50 is false, it is normal data, and when the value is true, it is temporary deletion data. The deletion flag 50 is included in the difference data transmitted to the client 21. The client 21 determines whether or not there is data to be deleted from the deletion flag 50 included in the difference data. The scheduled deletion date 40 is set to a value obtained by adding the current time of the timing when the above-described deletion flag becomes true and the cache expiration date 32.

  The client 21 includes a transmission / reception unit 21a, a local DB 21b, a data control unit 21c, and a data monitoring unit 21d. The transmission / reception unit 21a is communicably connected to the transmission / reception unit 11a of the server 11, and receives the difference data from the transmission / reception unit 11a of the server 11 for the update of data on the DB 11b included in the server 11. In addition, the transmission / reception unit 21 a transmits a synchronization request from the client 21 to the server 11 to the transmission / reception unit 11 a of the server 11.

  In the local DB 21b, data is changed / deleted by the data control unit 21d. The data control unit 21d reflects the difference data received by the transmission / reception unit 21a in the local DB 21b, and deletes the data on the local DB 21b by an instruction from the data monitoring unit 21c. The data monitoring unit 21c monitors the cache expiration date 32 of data on the local DB 21b via the data control unit 21d, and causes the data control unit 21d to delete data whose cache expiration date 32 has expired. Further, the data control unit 21d reads data on the local DB 21b according to an instruction from the data monitoring unit 21c, and confirms whether there is data whose cache expiration date 32 has expired.

  Referring to FIG. 7, each data on the local DB 21b is provided with fields of a cache valid period 31 and a cache valid period 32 in addition to general fields such as ID, data, date and time. When data synchronization is performed between the server 11 and the client 21, the local DB 21 b of the client 21 that has been updated with the difference data according to the set value of the cache validity period 30 set for each data on the DB 11 b of the server 11. In the upper data, a cache validity period 32 (the current time plus the cache validity period 31) is set. A specific example of the relationship between the scheduled deletion date 40 and the cache expiration date 32 is shown below. For example, if the data on the DB 11b of the server 11 is set as temporary deletion data at the same time as the time when the cache expiration date 32 is set on the data on the local DB 21b, the server 11 side and the client 21 side simultaneously The data can be deleted. In another example, when the data on the DB 11b of the server 11 is set as temporary deletion data at the time when the cache expiration date 32 of the data on the client 21 side arrives, the data on the DB 11b of the server 11 can be deleted. The time when the cache becomes valid comes 30 minutes later than the data on the client 21 side.

  [Description of Operation] The operation of the information processing system 110 will be described with reference to FIGS. In the information processing system 110 according to the second embodiment, the temporary deletion data on the server 11 side is obtained by linking the above-described data cache expiration date 32 on the client 21 side with the scheduled data deletion date on the server 11 side. The data is deleted after the corresponding data on the client 21 side is deleted.

  Hereinafter, before the temporary deletion data on the DB 11b of the server 11 is deleted, the data on the DB 11b of the server 11 and the data on the local DB 21b of the client 21 can be synchronized, and on the DB 11b after the scheduled deletion date. The operation of the information processing system 110 will be described with respect to a case where synchronization cannot be performed until data is deleted. In the description of the operation when synchronization is possible, a description will be given including the client 22 that makes a request to delete data on the DB 11 b of the server 11 to the server 11.

  Referring to FIG. 8, when the data on the DB 11 b of the server 11 and the data on the local DB 21 b of the client 21 can be synchronized before the temporarily deleted data is deleted, first, the client 22 first sends the data on the DB 11 b of the server 11. The server 11 receives a synchronization request including a deletion request for data (STEP 1: synchronization request). Here, it is assumed that the data targeted for the deletion request is data whose ID is 3333. Next, the server 11 sets the data with ID 3333 as temporary deletion data (STEP 2: temporary deletion of data (ID: 3333)). Specifically, the server 11 sets a deletion flag for data with ID 3333 to true. When the setting of the provisional deletion data is completed, the server 11 notifies the deletion request source client 22 that the deletion is successful (STEP 3: notification of successful deletion).

Next, consider a case where the client 21 accesses temporary deletion data. When the client 21 requests the server 11 to synchronize the data including the data with ID 3333 (STEP 4: synchronization request), the server 11 sends the difference data to the client 21 for the update that occurred after the previous synchronization with the client 21. Transmit (STEP5: Transmit differential data from previous synchronization). When the difference data acquired from the server 11 includes temporary deletion data (deletion flag is true), the client 21 determines that the data with the deletion flag and the ID 3333 is the deletion target data. The corresponding data is deleted from the local DB 21b of 21 (STEP6: temporary deletion data is deleted).
Further, for each data other than the temporary deletion data (data with ID 3333) of the acquired difference data, the client 21 sets the field of the cache expiration date 32 to a value obtained by adding the current time and the cache expiration date 31. To the local DB 21b. As described above, the client 21 that has synchronized the data within the cache expiration date 32 can immediately delete the data to be deleted from the local DB 21b.

  Next, a case where the temporary expiration data cache expiration date 32 has passed will be described. Referring to FIG. 9, the server 11 periodically checks the field of the scheduled deletion date 40 of the temporary deletion data on the DB 11b, and deletes the temporary deletion data that exceeds the scheduled deletion date 40 (STEP 91: scheduled deletion date). Delete data past. The operation of deleting data on the DB 11b of the server 11 will be described later.

  The client 21 periodically checks the cache expiration date 32 of each data on the local DB 21b, and deletes data that has exceeded the cache expiration date 32 (STEP 92: deletes data that has passed the cache expiration date). As a result of these operations of STEPs 91 and 92, if there is data to be deleted remaining in the client 21 that has not been synchronized, the timing at which the cache expiration date 32 has passed (the provisionally deleted data body is deleted on the server 11 side). At the same timing), it is deleted from the local DB 21b. For this reason, in the information processing system 110 of the present invention, data that has passed the cache validity period 31 does not exist on the client 21 side, and the temporary deletion data is not included in the difference data that the client 21 acquires from the server 11. Inconsistency does not occur between the two data (STEP 93: synchronization request and STEP 94: transmission of difference data from the previous synchronization).

  When deleting data on the DB 11b of the server 11, referring to FIG. 10, first, the server 11 waits for an access request from the client 21 (STEP 101: wait for access request). If the request received from the client 21 includes a request to delete predetermined data (STEP 102: is there a delete request), the server 11 does not delete the requested data and temporarily stores this data. The deletion data is set (STEP 103: temporary deletion data setting). Specifically, referring to FIG. 6, the server 11 sets a data deletion flag as true and newly sets a scheduled deletion date 40 (the current time plus the cache validity period 30). Also, fields other than the deletion flag 50 and the scheduled deletion date 40 are cleared.

  After the data is set as the temporary deletion data, the server 11 waits for the deletion of this data until the scheduled deletion date 40 of the temporary deletion data arrives (STEP 104: waiting for excess of the scheduled deletion date of the corresponding data). When it is detected that the scheduled deletion date 40 of the temporary deletion data has passed (STEP 105: has the scheduled deletion date been exceeded), the server 11 deletes the temporary deletion data from the DB 11b (STEP 106: temporary deletion data deletion).

  [Explanation of Effect] In the information processing system 110 according to the present invention, the data deletion notification on the server 11 side, which is covered by additional information when data synchronization is performed by sending and receiving the difference log, describes the data deletion in the difference data. Therefore, the amount of communication during data synchronization is reduced. Further, since the temporary deletion data of the server 11 is deleted after the scheduled deletion date 40, the resource pressure due to the increase of the temporary deletion data can be reduced, and the temporary deletion data can be deleted even if the temporary deletion data is deleted. Thus, no problem occurs in data synchronization.

  [Other Embodiments] In the information processing system 110 in the second embodiment, the temporary deletion data is not deleted by setting the scheduled deletion date 40, but all clients accessing the DB 11b of the server 11 are updated. You may make it carry out after finishing. For example, referring to FIG. 11, a resource count field is provided in the data on the DB 11b of the server 11, and the initial value is set to the total number of clients that can access the DB 11b. When each client accesses temporary deletion data, check the client ID, MAC address, etc., reduce the resource count so that there is no duplication, and delete the temporary deletion data when the value reaches 0 Can be taken.

  The temporary deletion data may be deleted after receiving a deletion request for all the clients 21 to access. For example, as in the example of providing the resource count field described above, the client 11 that has transmitted the deletion request to the server 11 is counted without duplication, and the server 11 deletes the temporary deletion data at the timing when the deletion request is received from all the clients. be able to.

  In the second embodiment, the two fields of the deletion flag and the scheduled deletion date indicate that the data on the DB 11b of the server 11 is temporary deletion data. May be. In this case, a value is input to the field of scheduled deletion date, and the data control unit 11d recognizes data in which this field is not blank as temporary deletion data.

  The monitoring of data on the DB 11b and the deletion of temporarily deleted data may be appropriately performed according to the load on the server 11. For example, you may search periodically for the existence of data that has exceeded the scheduled deletion date, and when the temporary deletion data is accessed from another client after it has been set as temporary deletion data, the deletion planned date will be exceeded You may check if you are doing. In the second embodiment, as an example of setting temporary deletion data, the fields other than the deletion flag 50 and the scheduled deletion date 40 are cleared. However, the fields may be left without being cleared. In this case, for example, temporary deletion data may be retrieved from the client. Moreover, each embodiment mentioned above can be implemented in combination as appropriate. The block division shown in each block diagram is a configuration shown for convenience of explanation. The present invention described by taking each embodiment as an example is not limited to the configuration shown in each block diagram in the implementation.

  As mentioned above, although the form for implementing this invention was demonstrated, the said embodiment is for making an understanding of this invention easy, and is not for limiting and interpreting this invention. The present invention can be changed and improved without departing from the gist thereof, and the present invention includes equivalents thereof.

1 CPU
2 Memory 3 HDD
4 I / O I / F
5 Communication device 10, 11 Server 10a Output unit 11a Transmission / reception unit 11b DB
11c Data monitoring unit 11d Data control unit 20, 21, 22 Client 21a Transmission / reception unit 21b Local DB
21c Data monitoring unit 21d Data control unit 30, 31 Cache validity period 32 Cache validity period 40 Deletion date 50 Deletion flag 100, 110 Information processing system

Claims (5)

On the server that synchronizes data with the client,
Comprising a first data control means for outputting the difference data as the update information for the synchronization of the data,
The difference data includes a first validity period for setting a first validity period for the data to which the data is reflected on the client side,
The data to be reflected is deleted when the first expiration date passes,
A server in which data of the server that is a reference source of the data is deleted when a second expiration date that comes after the first expiration date passes . The according to claim 1 server further comprising a first data monitoring means for monitoring the second expiration date,
When the first data monitoring unit detects that the second expiration date has passed, the first data monitoring unit causes the data control unit to delete the data of the server. In an information processing system that synchronizes data between a server and a client,
The server includes first data control means for outputting difference data as update information for the synchronization of the data ,
The difference data includes a first validity period for setting a first validity period for the data to which the data is reflected on the client side,
The data to be reflected is deleted when the first expiration date passes,
The information processing system according to claim 1, wherein data of the server that is a reference source of the data is deleted when a second expiration date that comes after the first expiration date has passed . 4. The information processing system according to claim 3 , wherein the client is a second data monitoring unit that monitors the first expiration date of the data of the client , and a second that adds, changes, or deletes the data of the client . Data control means ,
When the second data monitoring unit detects that the first expiration date has passed, the second data monitoring unit causes the second data control unit to delete the data of the client . In a data synchronization method for synchronizing data between a server and a client,
The server outputs difference data as update information for the synchronization of the data ,
The difference data includes a first validity period for setting a first validity period for the data to which the data is reflected on the client side,
The data to be reflected is deleted when the first expiration date passes,
The data synchronization method , wherein data of the server that is a reference source of the data is deleted when a second expiration date that comes after the first expiration date passes .

Images