JP6611594B2 - Information processing apparatus for synchronizing data, data synchronization method, and program - Google Patents

Description

  The present invention relates to a technique for synchronizing data between information processing apparatuses.

  In recent years, there is a technique for synchronizing a database via a network. Rather than synchronizing all the data in the database when performing synchronization, synchronization by difference is performed. There is a technique of performing synchronization processing at an arbitrary timing instead of performing synchronization processing at a predetermined timing when performing the synchronization processing by difference (see Patent Document 1).

  In addition, when performing synchronization based on database differences, there is a method in which data changed after the last synchronization time is extracted as a difference and data synchronization is performed (see Patent Document 2).

Japanese Patent Laid-Open No. 2002-132531 Japanese Patent Laid-Open No. 11-272533

  If the synchronization process combining the technique described in Patent Document 1 and the technique described in Patent Document 2 is performed, data consistency may not be maintained. In other words, in the case where data changed after the last synchronization time is extracted as a difference and the database is synchronized, if a synchronization request is made to the database at an arbitrary timing, data consistency may not be maintained.

  For example, in a data synchronization system between a plurality of information processing apparatuses each holding a database having a similar configuration, stored data may depend on the function or configuration of the information processing apparatus. Such data is not handled as data to be synchronized to an information processing apparatus whose function or configuration is not valid. This is because there is a possibility that a malfunction may occur if data assuming that the function or configuration is valid is synchronized with an information processing device whose function or configuration is not valid. After that, when the function or configuration becomes valid in the information processing apparatus, the data that has not been the synchronization target until now becomes the synchronization target at a specific timing. In such a case, data consistency cannot be maintained.

  A specific example will be described. Assume that there is an application A that can be introduced into the information processing apparatus, and data related to the application A is synchronized on a plurality of information processing apparatuses as a synchronization target. At this time, it is assumed that the initial value C is stored in the database of the information processing apparatus B in which the application A has not been introduced as data related to the application A. Here, it is assumed that the data related to the application A is changed to the value E in the information processing apparatus D in which the application A is introduced, and the information processing apparatuses are synchronized. Let T be the time when the data associated with this application is changed to the value E. Thereafter, it is assumed that synchronization is performed after time T in each information processing apparatus. Further, consider a case where application A is introduced into information processing apparatus B thereafter. Since the final synchronization completion time of the information processing apparatus B at this time is after the time T, the data related to the application A is in a synchronization completion state in the synchronous operation. Therefore, data related to the application A is not extracted as a difference from the main database, and the application A is operated with the initial value C being changed to the value E. Alternatively, there is a case where the data value (initial value C) at the time when the application A is introduced is updated to the main database, and the synchronization state desired by the user is not achieved.

  The information processing apparatus according to the present invention is connected to a plurality of clients, and is updated after a time when the client performs a previous synchronization process in response to a synchronization request from any of the plurality of clients. An information processing apparatus that transmits a setting value to the client based on a synchronization condition corresponding to the configuration of the client, wherein the first receiving unit receives a notification of an update of the setting value from the client; If the setting value included in the notification received by the receiving means is a setting value indicating that the configuration of the client has been changed, the setting value of the type corresponding to the configuration after the change of the client, And sending the setting information including the setting value that has not been updated since the time of the previous synchronization to the client as synchronization target data When the synchronization request is received by the setting means for setting, the second receiving means for receiving the synchronization request from the client, and the second receiving means, the synchronization request received by the second receiving means is transmitted. Transmission means for transmitting synchronization target data based on the setting of the setting means to the client.

  According to the present invention, when performing differential synchronization of data, data synchronization can be performed while maintaining data consistency.

It is a figure which shows the structure of the whole system which concerns on an Example. It is a figure which shows the hardware constitutions which concern on an Example. It is a figure which shows the software structure which concerns on an Example. It is a figure which shows the flowchart of the data update method at the time of implementing differential synchronization. It is a figure which shows the flowchart of the data synchronization method at the time of implementing differential synchronization. It is a figure which shows the flowchart at the time of the setting value update of Example 1. FIG. It is a figure which shows the flowchart at the time of the setting value synchronous request | requirement of Example 1. FIG. It is a figure which shows the flowchart at the time of the setting value update of Example 2. FIG. It is a figure which shows the flowchart at the time of the setting value synchronous request | requirement of Example 2. FIG. FIG. 10 is a diagram illustrating a flowchart when setting values are updated according to the third embodiment. FIG. 10 is a diagram illustrating a flowchart when a setting value synchronization request is made in the third embodiment. It is a figure which shows the flowchart of the data synchronization method at the time of implementing the difference synchronization of the setting value which is user-managed. FIG. 10 is a diagram illustrating a flowchart when setting values are updated according to the fourth embodiment. FIG. 10 is a diagram illustrating a flowchart when a setting value synchronization request is made in the fourth embodiment.

  Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. First, a configuration according to the embodiment will be described with reference to the drawings. Thereafter, a general differential synchronization process performed using the configuration according to the embodiment will be described, and supplementary explanation will be given for the occurrence of the problem described in the problem. Thereafter, each example using the configuration according to the embodiment will be described.

  FIG. 1 is a diagram illustrating a system configuration example illustrating the entire synchronization system according to the embodiment. A set value management server 110, a multifunction device 120, and a multifunction device 121 are connected to the network 100. Here, an example in which two MFPs are connected is shown, but the present invention is not limited to this. A plurality of multifunction peripherals may be further connected. In the following description of the configuration, the multifunction device 120 will be described as an example, but the configuration of the multifunction device 121 is the same. Here, a multi-function device will be described as an example, but a general information processing apparatus such as a computer or a portable terminal may be used. Each multifunction device synchronizes data stored in each multifunction device with the set value management server. As a result, the data used uniquely for the multifunction device is synchronized between the multifunction device and the setting value management server. In addition, data that is commonly used among the multifunction devices is sequentially synchronized between the multifunction devices via the setting value management server. Details of the synchronization processing will be described later.

  FIG. 2 is a block diagram illustrating the configuration of the setting value management server 110 and the configuration of the multifunction device 120 according to the embodiment.

  FIG. 2A is a diagram illustrating the configuration of the setting value management server 110. The set value management server 110 includes a controller unit 200, an operation unit 201, and a display unit 202. The controller unit 200 includes an operation unit I / F 203, a display unit I / F 204, a CPU 205, a RAM 206, an HDD 207, a ROM 208, a network I / F 209, and a system bus 210.

  A CPU (Central Processing Unit) 205 activates an OS (Operating System) by a boot program stored in a ROM (Read Only Memory) 208. The CPU 205 executes application programs stored in an HDD (Hard Disk Drive) 207 on the activated OS, thereby executing various processes. A RAM (Random Access Memory) 206 is used as a work area of the CPU 205. The HDD 207 stores application programs and setting value data of the multifunction machine 120. Details regarding the management method of the set value data will be described later.

  An operation unit I / F 203, a display unit I / F 204, and a network I / F 209 are connected to the CPU 205, along with a ROM 208 and a RAM 206, via a system bus 210. An operation unit I / F 203 is an interface with the operation unit 201 including a mouse, a keyboard, and the like, and notifies the CPU 205 of information input by the user through the operation unit 201. The display unit I / F 203 outputs image data to be displayed on the display unit 202 including a display to the display unit 202. The network I / F 209 is connected to the network 100 and inputs / outputs information to / from each device on the network 100 via the network 100.

  FIG. 2B is a diagram illustrating the configuration of the multifunction machine 120. The multifunction machine 120 includes a controller unit 220, an operation unit 221, a scanner 231, and a printer 232. The controller unit 220 is connected with an operation unit 221 and a scanner 231 that is an image input device and a printer 232 that is an image output device. The image input / output device to be connected is not limited to the scanner 231 and the printer 232, but a FAX unit or the like for enabling FAX transmission for transmitting an image generated by the MFP 120 to the outside through a telephone line ( (Not shown) can also be connected.

  The controller unit 220 includes a device I / F 222, an operation unit I / F 223, a CPU 224, a RAM 225, an image processing unit 226, an HDD 227, a ROM 228, and a network I / F 229. The CPU 224 starts up the OS by a boot program stored in the ROM 228. The CPU 224 executes application programs stored in the HDD 227 on the OS, thereby executing various processes. A RAM 225 is used as a work area for the CPU 224. The RAM 225 provides a work area and an image memory area for temporarily storing image data. The HDD 227 stores the application program, image data, and various setting values. A setting value management method in the multi function peripheral 120 will be described later.

  An operation unit I / F 223, a device I / F 222, a network I / F 229, and an image processing unit 226 are connected to the CPU 224 through the system bus 230 together with the ROM 228 and the RAM 225. The operation unit I / F 223 is an interface with the operation unit 221 having a touch panel, and outputs image data to be displayed on the operation unit 221 to the operation unit 221. In addition, the operation unit I / F 223 transmits information input by the user through the operation unit 221 to the CPU 224. A scanner 231 and a printer 232 are connected to the device I / F 222, and the device I / F 222 performs synchronous / asynchronous conversion of image data. The network I / F 229 is connected to the network 100 and inputs / outputs information to / from each device on the network 100 via the network 100.

  The image processing unit 226 performs processing such as input image processing from the scanner 231, output image processing to the printer 232, image rotation, image compression, resolution conversion, color space conversion, and gradation conversion.

  FIG. 3 is a software configuration diagram of the setting value synchronization system that operates in each of the setting value management server 110 and the multifunction device 120 of FIG. 2 described above.

  First, a setting value management client application that runs on the multifunction machine 120 will be described. Hereinafter, an application may be simply referred to as an application. The multifunction device 120 functions as a client. FIG. 3B is a diagram illustrating a configuration of a setting value management client application that operates on the multifunction peripheral 120. The setting value management client application 320 shown in FIG. 3B is stored in the ROM 228, the HDD 227, etc. on the multi function peripheral 120, and is executed by the CPU 224.

  The setting value management client application 320 includes a data processing unit 321, a setting value data management unit 322, an application control unit 323, a setting value management database 324, and a communication processing unit 325.

  Examples of setting value data stored in the setting value management database 324 include setting values as shown in Tables 1 and 2.

  The multifunction device 120 stores device setting values as shown in Table 1 in the setting value management database 324. In the setting value management database 324, a UI identifier, a setting value, and an initial value are stored in association with a key identifier that can uniquely specify the setting value.

  For example, the key identifier {settings. devic. network. The setting value specified by “ipadless} is a setting value for managing the IP address of the multi function peripheral 120, and the UI display name is {IP address} for Japan destinations. The currently set value is {192.168.111.222}, and the initial value is {255.255.255.255}.

  The multifunction device 120 also has a function of transmitting image data input from the scanner 231 via the network to the outside by E-Mail, and there is address book data for storing and managing E-Mail destinations. Address book data is also stored as a kind of setting value in the setting value management database 324 of the MFP 120. Table 2 obtained by cutting out the data managed by the address book function in an easy-to-understand manner stores an address book ID uniquely managed by the address book function in association with a destination type, a destination, and a display name.

  For example, information with the address book ID {1} is sent to the destination {aaa @ xxx. co. jp} is stored, and {Taro Tanaka} is displayed on the operation unit 221.

  The set value management database 324 also stores the last synchronization completion time as shown in Table 3.

  Table 3 shows information used when the MFP 120 synchronizes setting value data with the setting value management server 110. Details will be described in the setting value data synchronization method described later.

  Next, the configuration of the setting value management server application 310 of the setting value management server 110 will be described. The setting value management server application 310 in FIG. 3A is a configuration diagram of an application stored in the ROM 208, the HDD 207, and the like on the setting value management server 110 and executed by the CPU 205.

  The setting value management server application 310 includes a data processing unit 311, a setting value data management unit 312, an application control unit 313, a setting value management database 314, a communication processing unit 315, and a response data management unit 316.

  In the set value management database 314, for example, data in Tables 4 to 8 is stored.

  In Table 4, the serial number is set so that the setting value management server application 310 can uniquely identify the client that performs the setting value synchronization processing via the network 100. The device code and version are managed as a unique key that can be searched. The data shown in Table 4 is stored in the setting value management database 314 of the setting value management server application 310. Serial No. Is set so that the product can be uniquely identified, and the product is classified by the device code. The version is serial no. This is the firmware version of each MFP associated with the.

  The setting value management database 324 of the setting value management server manages data of all setting values of the connected multifunction peripherals as shown in Table 5. The setting value management server application 310 sends the setting value data in Table 1 notified from the multifunction device 120 via the network 100 to the serial number of the multifunction device as shown in Table 5. To manage each. When the setting value management server application 310 is notified of updated or newly registered setting value data from the MFP 120, the time stored in the server as shown in Table 5 is associated with each setting value as the server last update time. Are managed.

  Tables 6 to 8 also show setting values stored in the setting value management database 314 of the setting value management server 110. Tables 6 to 8 will be described in detail in the setting value data synchronization method described later.

  Next, normal synchronization processing performed in the configuration as described above will be described with reference to FIGS. 4 and 5 are flowcharts when the setting value management server application 310 and the setting value management client application 320 in FIG. 3 actually synchronize setting value data. Here, the processing between the multifunction device 120 and the setting value management server 110 will be described as an example, but the processing between the arbitrary multifunction device and the setting value management server 110 is the same processing. The actual setting value data synchronization processing method will be described together with Tables 1 to 8.

  Here, specifically, the serial number of the multifunction machine 120 is changed. Is {1234567}, and an example in which the address book data registered in each MFP is handled as a common setting value will be described. The common setting value is a setting value common to apparatuses (including a server and a client) of the synchronization system. In other words, an example will be described in which address book data is handled as common data among the devices. For example, once the address book data of the person who is the multifunction device 120 is updated, as a result, the address book data of the other multifunction devices 121 is also updated synchronously. Specific processing will be described below.

  First, the premise process in a synchronous system is demonstrated. When the setting value management client application 320 connects to the setting value management server application 310 for the first time via the network 100, all the data in the setting value management database 324 is transmitted to the setting value management server application 310. In FIG. 4, it is assumed that the setting value management client application 320 has already been connected to the setting value management server application 310 and all data in the setting value management database 324 has been transmitted to the setting value management server application 310.

  Thereafter, it is assumed that the user changes the setting value of the multifunction machine 120. In step S411, the setting value data management unit 322 of the setting value management client application detects a change in the setting value via the data processing unit 321. When the change of the setting value is detected, in step S412, the application control unit 323 requests the communication processing unit 325 to notify the setting value change, and the communication processing unit 325 notifies the setting value management server application 310 of the setting value change. To do.

  In step S <b> 421, the communication processing unit 315 of the setting value management server application 310 receives a setting value change notification from the setting value management client application 320 via the network 100.

  In step S422, the application control unit 313 updates the setting value corresponding to the notified setting value managed on the server. First, the communication processing unit 315 notifies the application setting unit 313 of the received setting value. The application control unit 313 updates the setting values in the setting value management database 314 via the setting value data management unit 312 and the data processing unit 311. Next, in step S423, the setting value data management unit 312 requests the data processing unit 311 to update the server last update time of the updated setting value and executes it. If the setting value updated at S423 is a common setting value, the update of the common setting value and the server last update time stored in association with all the connected multifunction peripherals are also updated.

  A specific example will be described. For example, assume that setting values are stored as shown in Table 7 in the setting value management database 314 of the setting value management server application. Table 7 shows device serial numbers. Each common setting value is stored in association with each other. Here, when the setting value notified of the update in step S421 is the setting value of the address book ID {3}, and when the update notification is notified to 2015/02/1 13:00, the address book IDs of all the multifunction peripherals. The set value of {3} and the server last update time are updated. Table 7 shows the setting values in this updated state.

  After the update process described above is completed, in step S424, the application control unit 313 requests a response indicating that the update process has been completed to the communication processing unit 315. The communication processing unit 315 transmits the completion of the update process as a response to the setting value management client application 320 via the network 100.

  In step S413, the communication processing unit 325 of the setting value management client application 320 notifies the application control unit 323 that the update processing completion response has been received. Then, the setting value update process is terminated.

  In the present embodiment, as described above, since the setting values of a plurality of multifunction peripherals (client devices) are synchronized, the setting value management client application performs synchronization processing at regular timing. FIG. 5 is a flowchart showing the flow of synchronization processing at regular timing.

  In step S511, the application control unit 323 of the setting value management client application detects the timing of the synchronization request. In step S511, the application control unit 323 detects the timing of the synchronization request when the timing of the periodic synchronization processing is reached. When the timing of the periodic synchronization request is reached, in step S512, the application control unit 323 determines whether the previous synchronization time (final synchronization completion time) stored as shown in Table 3 exists. The previous synchronization time is the time when the previous set value was synchronized.

  If the previous synchronization time exists, the process advances to step S513, and the application control unit 323 requests the communication processing unit 325 to perform a setting value synchronization request with a specified synchronization time. The communication processing unit 325 notifies the setting value management server application 310 of a setting value synchronization request with a synchronization time specification via the network 100.

  On the other hand, if the previous synchronization time does not exist, the process proceeds to step S514, and the application control unit 323 requests the communication processing unit 325 for a setting value synchronization request without specifying the synchronization time. The communication processing unit 325 notifies the setting value management server application 310 of a setting value synchronization request without specifying a synchronization time.

  In step S521, the communication processing unit 315 of the setting value management server application 310 receives the synchronization request and notifies the application control unit 313 of the request. In step S522, the application control unit 313 determines whether a time is specified in the notified synchronization request.

  If the synchronization time is not specified, the process proceeds to step S523. The application control unit 313 requests the setting value data management unit 312 to obtain all the setting values stored in the setting value management database 314 and related to the request source device, and receives the setting value data via the data processing unit 311. get. In this embodiment, the setting value data of all the setting values related to the request source device is a setting value of a type corresponding to the configuration after the change of the client device, and the setting value that has not been updated in the configuration change migration including. In addition, the setting information includes a setting value of a type corresponding to the configuration after the change of the client device, and the setting value updated in the configuration change migration.

  On the other hand, if the synchronization time is designated, the process proceeds to step S524. The application control unit 313 stores the setting value stored in the setting value management database 314 in the setting value data management unit 312 and after the time when the associated server last update time is specified among the setting values related to the request source device. Request to get things. Then, the application control unit 313 acquires setting value data via the data processing unit 311.

  In step S 525, the application control unit 313 requests the setting value data management unit 312 to obtain configuration information of the multifunction peripheral that has performed the synchronization request from the setting value management database 314 via the data processing unit 311. The configuration information of the connected client stored in the setting value management database 314 is stored as shown in Table 6, and the device serial number. The effective state of the function is managed corresponding to For example, the device serial No. {312567} is connected to the FAX unit, but the device serial No. It can be confirmed from Table 6 that a FAX unit is not connected to {1234567}.

  In step S526, the application control unit 313 requests the response data management unit 316 to create response data based on the configuration information of the client from the setting value data acquired in step S522 or step S523. The response data management unit 316 creates data that responds to the multi-function peripheral 120 that has made the synchronization request. At this time, the response data management unit 316 acquires the synchronization condition information in Table 8 stored in the setting value management database 314 via the data processing unit 311 and creates response data.

  For example, it is assumed that the time designated in step S522 is 2015/02/1 12:59. That is, it is assumed that the setting value management server application has received a setting value synchronization request with a specified synchronization time. The time designated in step S522 is the previous synchronization time designated from the multifunction device 120. That is, as shown in step S524, data updated after the previous synchronization time is a candidate for update. In this case, in the setting values of the address book information in Table 7, the data acquired as the update target candidates are the data of the address book IDs {2} and {3}. The response data management unit 316 refers to the set value of the synchronization condition in Table 8. From the information in Table 8, the destination type FAX of the address book information is {setting. option. When the state of “faxunit} is ON, it becomes a synchronization target. Accordingly, the response data management unit 316 determines a setting value to be synchronized from the candidates for update based on the information in Table 8. Referring to the device configuration information managed in Table 6, the device serial No. It can be seen that the FAX unit is not connected to the multifunction device 120 of {1234567}. Therefore, the response data management unit 316 has the device serial number. In the synchronous response data to {1234567}, response data is created so that only the address book ID {2} is returned without including the address book ID {3} that is the destination type FAX. In this way, the response data management unit 316 creates response data by extracting the setting values to be synchronized among the setting values of the update target candidates according to the configuration / state of the multifunction peripheral. In other words, the response data management unit 316 creates response data so as not to include setting values that are not to be synchronized according to the configuration / state of the multifunction peripheral. As described above, when a certain function or configuration of the device is not valid, the data related to the function or configuration is not set as the synchronization target data even if the data is updated after the previous synchronization time. ing. This is because, for example, the multifunction device may determine that the function X of the multifunction device is not valid by referring to the initial value of the setting value related to the function X. If the function X is not valid, the initial value is set. This is because a problem may occur if it is updated.

  Next, the description returns to the flow description. In step S527, the application control unit 313 requests the communication processing unit 315 to transmit the response data created by the response data management unit 316. The communication processing unit 315 transmits response data to the setting value management client application via the network 100.

  In step S515, the communication processing unit 325 of the setting value management client application 320 receives the notification of response data. The communication processing unit 325 notifies the application control unit 323 that the response data has been received, and the application control unit 323 updates the setting values in the setting value management database 324.

  Finally, in step S516, the application control unit 323 updates the final synchronization completion time as shown in Table 3, and refers to the value at the next synchronization request.

  In the description of FIG. 5, the case where the previous synchronization time does not exist mainly refers to the case where the setting value management client application 320 makes a synchronization request to the setting value management server application 310 for the first time.

  The above is description of the form which performs the normal synchronous process of a setting value synchronous system. Here, a description will be given of the fact that the synchronization may not be performed well in the setting value update and synchronization processing flow of FIGS. 4 and 5 described above. That is, a case where a mismatch between a setting value managed by the server and a setting value managed by the client occurs will be described.

  For example, it is assumed that the process of FIG. 5 is performed a plurality of times in the multifunction peripheral 120, and the value {2015/02/01 15:00} is stored as the previous synchronization time in S516. After that, the device serial No. A FAX unit is attached to the multifunction machine 120 of {1234567}, and {setting. option. Assume that the state of “faxunit} becomes {ON}. When the setting value management client application 320 of the MFP 120 makes a synchronization request at the timing of the subsequent synchronization request, the setting value data whose address book ID is {3} is not subject to synchronization in the processing flow of FIG. This is because the server last update time of the address book ID “3” is before the previous synchronization time, and the setting value management server application 310 determines that the address book ID “3” has already been synchronized. . As a result, since it is not acquired as a candidate for update in step S524, it is not included in the response data.

  In Examples 1 to 3 below, various examples for solving such problems will be described.

[Example 1]
The processing of the first embodiment will be described with reference to FIGS. As for the data configuration, the configuration shown in Table 9 in which the configuration change management flag item is added to the data items in Table 4 stored in the set value management server application 310 is held in the set value management database 314.

  Next, the processing of the flowchart of FIG. 6 will be described focusing on the differences from FIG. Steps in the flowchart that are the same as the processing in FIG. 4 are assigned the same numbers as in FIG. 4, and detailed descriptions thereof are omitted here.

  In FIG. 6, similarly to FIG. 4, processing is performed in which the setting value management client application 320 detects a change in the setting value and notifies the setting value management server application 310 of the change. In step S601, the setting value management server application 310 determines whether the setting value updated in step S422 is a setting value related to the synchronization condition of other setting values. When it is determined that the setting value is related to the synchronization condition of the other setting value, the process proceeds to step S602. In step S602, the setting value data management unit 312 of the setting value management server application turns ON the configuration change management flag associated with the client (device serial No.) that has made the update request as managed in Table 9. Then, the process proceeds to step S424.

  For example, the setting value management server application 310 manages setting value data for managing the synchronization conditions as shown in Table 8. When the setting value updated in step S422 changes the synchronization condition setting value as shown in Table 8, it is a setting value related to the synchronization condition of “destination type: FAX”, which is another setting value in the example of Table 8. Can be determined. For example, the device serial No. {Setting.update} is sent to the setting value update notification received from {1234567}. option. In the case of notification of {faxunit} as {ON}, the device serial No. The configuration management flag {1234567} is turned ON.

  Next, the processing of the flowchart of FIG. 7 will be described focusing on the differences from FIG. FIG. 7 shows a process in which the setting value management client application 320 transmits a synchronization request and the setting value management server application 310 transmits response data in response to the synchronization request, as in FIG. Steps in the flowchart that are the same as the processing in FIG. 5 are assigned the same numbers as in FIG. 5, and detailed descriptions thereof are omitted here.

  A periodic synchronization request is executed from the setting value management client application 320. When receiving the synchronization request, the setting value management server application 310 refers to the setting value data stored as shown in Table 9 in step S701, and determines whether the configuration management flag of the device that has performed the synchronization request is ON. . If the configuration management flag of the device that has made the synchronization request is ON, the process advances to step S702, and the setting value data management unit 312 turns OFF the configuration change management flag of the device corresponding to the notification source setting value management client application 320. . In step S523, the application control unit 313 acquires all setting values related to the device that has issued the synchronization request, as described with reference to FIG. Thereafter, similarly to FIG. 5, the response data is generated with reference to the configuration information of the client that is the synchronization request source.

  As described above, in the configuration in which difference synchronization is performed, if there is a change in a setting value that affects the synchronization conditions of other setting values, all setting values are synchronized. Thereby, it is possible to prevent inconsistency between data stored in the setting value management server application 310 and data stored in the setting value management client application 320. In other words, since the setting value management client application 320 performs the same synchronization process as when the setting value management server application 310 makes a synchronization request for the first time, data synchronization with the data managed by the server is possible. The setting value management server application 310 can also create response data without considering the relevance of the data.

[Example 2]
Next, Example 2 will be described. In the first embodiment, when a synchronization request is made after updating the device configuration information of the multifunction device 120, the setting value management server application 310 creates response data for all data related to the device (the multifunction device 120) as synchronization targets. The example to do was explained. In other words, on the setting value management server 110 side, a device whose setting value has been changed that affects the synchronization conditions of other setting values is specified, and when there is a synchronization request from that device, all data is subject to synchronization. An example was explained.

  On the other hand, in the second embodiment, an example will be described in which inconsistency of synchronized data is prevented by changing the processing on the multifunction peripheral 120 side which is a client without changing the processing on the setting value management server 110 side. .

  The process of the flowchart of FIG. 8 will be described focusing on the difference from FIG. The same numbers as those in FIG. 4 are given to the steps of the flowchart that are the same processing.

  The setting value management client application 320 detects the change of the setting value in step S411, and performs the process of step S801 before notifying the setting value management server application 310 of the update in step S412. In step S801, the setting value data management unit 322 determines whether the setting value changed in step S411 is a setting value related to configuration information. If the changed setting value relates to configuration information, the process advances to step S802, and the setting value data management unit 322 separately stores a file indicating the change.

  For example, the setting value data management unit 322 can determine whether the changed setting value is a setting value related to configuration information based on the setting value name of the device setting value in Table 1. For example, the key identifier of the FAX unit is {setting. option. faxunit}. As described above, the set value data management unit 322 uses {setting. option. When there is a change to *}, a key identifier having a retrievability that can be identified so as to be regarded as a change of a setting value related to configuration information may be used.

  Alternatively, the setting value management client application 320 stores setting value data stored in the setting value management server application 310 and corresponding to Table 8 managed by the setting value management server application in the setting value management database 324. It may be stored. Alternatively, a table whose key identifier corresponds to the configuration management data may be stored in the set value management database 324 separately.

  Specifically, {setting. option. When “faxunit} becomes {ON}, the set value data management unit 322 requests the application control unit 323 to perform processing. The application control unit 323 stores the file indicating the change in an external storage unit (HDD 207 or RAM 206) via the system bus 230.

  Next, the processing of the flowchart of FIG. 9 will be described focusing on the differences of FIG. The same numbers as those in FIG. 5 are assigned to the steps of the flowchart that are the same processing.

  If it is detected in step S511 that the periodic synchronization timing has been reached, the process proceeds to step S901, and the application control unit 323 of the setting value management client application determines whether there is a file indicating a configuration change. For example, the application control unit 323 determines whether there is a file indicating a configuration change stored in an external storage unit via the system bus 230.

  If there is a file indicating a configuration change, the process advances to step S514, and the application control unit 323 executes the “synchronization request not specifying the previous synchronization time” that was notified when the periodic synchronization request was made. That is, the same synchronization request (request that all set values are returned as a response) is executed in the case where it is determined in step S512 that the previous synchronization time does not exist. As a result, when the setting value management server application 310 receives the synchronization request, a response of all setting values is returned based on the configuration information of the client (see steps S523 and S525).

  Thereafter, response data is received from the setting value management server application 310, and after the data update (S515) and the previous synchronization time update (S516), the process of step S902 is performed. In step S902, the application control unit 323 determines whether there is a file indicating a change in configuration in the synchronization request flow. If there is a file indicating a configuration change, the application control unit 323 deletes the file indicating the configuration change in step S903.

  In this embodiment, data is transmitted / received via the network 100. Therefore, an error response may be received for some reason (not shown), so the existence of a file indicating a configuration change is confirmed and deleted in the same synchronization request flow.

  As described above, in the second embodiment, the setting value management client application 320 detects the client configuration change without changing the configuration on the setting value management server side, and makes a request for synchronization of all data to perform setting value management. Synchronization with server application is possible.

[Example 3]
Next, Example 3 will be described. In the first embodiment, an example has been described in which it is specified that the configuration has been changed on the setting value management server side, and all data related to the device having the configuration change is synchronized. In the third embodiment, an example will be described in which, when the setting value management server application 310 detects a change in configuration information, not all data related to a device is synchronized but a setting value to be synchronized is determined in advance.

  Hereinafter, the third embodiment will be described focusing on differences from the first embodiment.

  In the third embodiment, the setting value management database 314 of the setting value management server application stores setting values obtained by adding a term “forced synchronization flag” to the setting value data in Table 7, as shown in Table 10.

  The process of the flowchart of FIG. 10 will be described focusing on the difference between FIG. 4 and FIG. The same numbers as those in FIGS. 4 and 6 are assigned to the steps of the flowchart that are the same processing.

  When it is determined in step S601 of the process of the setting value management server application 310 that the updated setting value is a setting value related to the synchronization condition for other setting values, the setting value data management unit 312 proceeds to step S1001. In step S1001, the set value data management unit 312 sets the forced synchronization flag of each related set value to {ON}.

  For example, the setting value management server application 310 manages setting value data for managing synchronization conditions as shown in Table 8. Device serial No. {Setting.update} is sent to the setting value update notification received from {1234567}. option. In the case of the notification that “faxunit} is {ON}, the forced synchronization flag of the setting value data of the destination type {FAX} in Table 10 is set to {ON}.

  Next, the processing of the flowchart of FIG. 11 will be described focusing on the differences of FIG. The same numbers as those in FIG. 5 are assigned to the steps of the flowchart that are the same processing.

  In the process of the set value management server application, after acquiring the set value as a result of the time comparison in step S524, the process proceeds to step S1101. In addition to the setting value acquired in step S524, in step S1101, the setting value data management unit 312 acquires a setting value whose forced synchronization flag is ON. In step S1102, the setting value data management unit 312 sets the forced synchronization flag of the setting value acquired in step S1101 to {OFF} after acquiring the setting value. Thereafter, similarly to FIG. 5, the setting value data is returned based on the configuration information of the synchronization request source client.

  As a result, when there is a change in the setting values related to the device configuration information, it is possible to perform synchronization in consideration of the relationship of the setting values that have an effect, instead of targeting all data.

<Modification>
In the first to third embodiments, the description has been given of the example in which the actual data exists for the client even if it is the common setting value data as shown in Table 7. However, the present invention is applicable even when the data of the common setting value data is managed by one. Moreover, although it demonstrated as a flag in each said Example, it is good also as time information. For example, when managing common setting values in the form of a single data entity, the common setting value is returned to the client in response to a synchronization request as a way to clearly indicate the completion of synchronization to multiple clients. The set time management server application side may manage the set time. That is, in addition to the server last update time that is the time when the setting value is updated from the client, the server response time when the setting value is returned as a response to the synchronization request from the client may be further associated and managed. This server response time is managed in association with a set value for each client as shown in Table 4, for example. That is, the set value management server application manages the response time (server response time) to the synchronization request for each client. When the setting value management server receives a synchronization request from a client for which a time before the server response time is specified, the configuration at that client may have been changed. Therefore, when such a synchronization request is received, the setting value management server also performs a process of responding to all the setting values or responding to the setting values related to the configuration change regardless of the server last update time. Is possible.

[Example 4]
In the first to third embodiments, the example of the process of synchronizing the setting values managed by the setting value management server application for each device has been described. However, as a method for managing the setting value by the setting value management server application, there is a method of managing the setting value for each user. For example, in the case of a multifunction machine in which the client multifunction machine performs login management, the initial value of a certain process may be managed for each user. An example in which such a setting value for each user is synchronously processed between the setting value management server and each client will be described in a fourth embodiment.

  The setting value management database 314 of the setting value management server application manages user information as shown in Table 11, and the setting value management database 324 of the setting value management client application manages user information as shown in Table 12. Has been.

  Example in which each setting value management client application manages the last synchronization time at which each client last performed synchronization processing as the last synchronization time managed by each setting value management client application described in the first to third embodiments. Explained. In this embodiment, in order to adapt to the setting value for each user, each setting value management client application manages the final synchronization time for each user as shown in Table 12. The final synchronization time for each user is the final synchronization time at each client. That is, in other clients, different final synchronization times may be managed for the same user.

  The setting value management database 314 of the setting value management server application has a table for managing setting values for each user as shown in Table 13.

  Table 14 shows an example of device configuration information in the present embodiment. Table 6 described in the first embodiment shows an example of whether the finisher and the FAX unit of each device are valid. Table 14 in the present embodiment shows an example of whether the address book, copy function, scan and transmission function, etc. are valid.

  In the following, a synchronization process when device configuration information is registered as shown in Table 14 will be described. As described above, Table 11 is setting value information for managing users, which is stored in the setting value management database 314 of the setting value management server application. Table 13 manages personal settings set by the user corresponding to Table 11.

  For example, in order to confirm the default setting value at the time of starting the “scan and send” application with the user name “userA”, first the user ID corresponding to the user name “userA” in Table 11 is confirmed. Then, the related data identifier “license.application.ScanToSend” in Table 13 corresponding thereto is confirmed. Specifically, since the user ID corresponding to “userA” is “2”, the related data identifier “license.application.ScanToSend” in Table 13 corresponding to this user ID “2” is confirmed. Table 13 stores default setting values at the time of starting the “scan and send” application of “userA”. According to Table 13, when “userA” activates the “scan and send” application, the file format for sending the scanned image is a setting value in the PDF format. In addition, aaa@xxx.co.jp is set in the CC. The device for which the “scan and send” function is valid is the device “3124567” for which “license.application.ScanToSend” is valid from the valid licenses / options in Table 14.

  When the setting values managed for each user as shown in Table 13 are synchronized between the clients via the server, the user does not need to make a new setting for each client, which improves convenience. However, when the device configuration information as shown in Table 14 changes, for example, when the “scan and send” application is changed from an invalid (not installed) state to an active state in a certain client X There is. In such a case, if the difference synchronization process for synchronizing the differences after the last update time is performed, the appropriate setting value may not be synchronized as in the first embodiment. In the present embodiment, a mode in which appropriate synchronization processing is performed for setting values managed for each user will be described.

  The configuration information in Table 14 is updated by the processing shown in the flowcharts of FIGS. 6 and 8 in the same manner as the description described for Table 6. In other words, when there is a change in the device configuration information in Table 14 (for example, a setting value indicating whether the “scan and send” application is valid), the setting value management client application changes the setting value to the setting value management server. The application is notified (S412). Further, the device to be updated is not only the device configuration information. Also for the setting values for each user as shown in Table 13, when a user who is logged in to a certain client makes a change, the setting value management client application notifies the setting value management server application of the change of the setting value ( S412).

  Also, in the setting value synchronization processing for each user, the setting value management server application has a function of determining a setting value to be synchronized with the login device when logging in to a specific device (client). (S525). For example, if the device to which the user logged in is not enabled for the “Scan and Send” application, even if the settings (initial values at startup) for the “Scan and Send” application are changed on other devices, It is not determined to be synchronized.

  The setting value management client application manages setting values corresponding to items other than the server last update time in Table 14 as shown in Table 15.

  The setting value synchronization request timing managed for each user is performed at the timing when the user logs into the device to be used. For example, when the user logs into the device X, the device X notifies the setting value management server application of a synchronization request as a client.

  Here, a flow of setting value synchronization processing managed for each user will be described with reference to FIG. As in the first embodiment, first, the setting value synchronization process managed for each user will be described with reference to FIG. 12, and the setting value synchronization process according to the present embodiment will be described with reference to FIGS. Also in FIG. 12, the same processes as those described in the first embodiment are denoted by the same reference numerals, and detailed description thereof is omitted. A user logs in to the multifunction machine 120. In step S1201, the setting value management client application detects a user login. In this embodiment, the user login is used as a trigger for the synchronization request.

  Next, in step S1202, the setting value management client application determines whether there is a previous synchronization time as in step S512 of FIG. In step S1202, unlike S512, the setting value client application determines whether there is a previous synchronization time (final synchronization time) of the setting values related to the logged-in user as shown in Table 12. If there is a previous synchronization time of the setting value related to the logged-in user, the process advances to step S1203. In step S1203, the setting value client application notifies the setting value management server application 310 of a setting value synchronization request specifying the previous synchronization time and the user identification information indicating the login user.

  On the other hand, if the previous synchronization time does not exist, in step S1204, the setting value management client application notifies the setting value management server application 310 of a setting value synchronization request in which only the login user is specified without specifying the synchronization time.

  In step S1210, the setting value management server application 310 determines whether or not a user has specified the received synchronization request. If there is no user designation, the process proceeds to step S1213, and the same process as the process after the device setting value synchronization process (S522) described in FIG. 5 is performed.

  If there is a user designation, the process advances to step S522, and the setting value management server application determines whether there is a time designation for the synchronization request in the same manner as S522 described with reference to FIG.

  If the time is specified, the process advances to step S1211, and the set value management server application acquires a set value of the server update time related to the specified user after the specified time.

  Here, for example, a case where the user name “Administrator” logs in and the previous synchronization time is “2015/2/1 13:01” as shown in Table 12 is considered. In this case, the data acquired in step S1211 is the setting value {destination type: FTP, destination: 192.168.222.333, display name: shared server} of the user ID “1” in Table 13.

  If the time is not specified, the process advances to step S1212, and the setting value management server application acquires all the setting values related to the specified user.

  When responding to the setting value acquired in S1211 or S1212, the setting value management server application acquires the configuration information of the synchronization request source client and creates response data in the same manner as in S525 to S527 described in FIG. I do. Here, for example, consider a case where the serial number of the device to which the user has logged in is “1234567”. In this case, referring to Table 14, the set value management server application creates response data only for data related to “license.application.AddressBook” and “license.application.Copy” and responds.

  Finally, the setting value management client application executes the process in the same manner as S515 to S516 in FIG.

  As described with reference to FIG. 12, the synchronization processing is also possible for the data managed for each user by the processing of the setting value management server application 310 and the setting value management client application 320.

In addition, although S1210 of FIG. 12 has shown the example which switches a process according to whether there is a user designation | designated in a synchronous request | requirement, it is not restricted to this. For example, even when there is a user designation in the synchronization request (in the case of YES in S1210), processing similar to S1213 may be performed. In other words, the synchronization process of the common setting value for each device described in the first embodiment or the like may be performed in response to the synchronization request designating the user.

  Table 16 is a table for further managing the time when the device management configuration information is changed to Table 4 described in the first embodiment in order to manage the synchronization data consistency of the present embodiment.

  In this embodiment, when the time attached to the synchronization request from the setting value management client application 320 is before the configuration information change time, resynchronization is performed with all setting values of the setting value management server application 310. A configuration for executing the response to be performed will be described. That is, the setting value management server application 310 acquires the setting value related to the login user as a setting value to be synchronized regardless of the last update time of the setting value, and sets the setting value according to the synchronization condition according to the device configuration to the client. An example of responding to will be described.

  Specific processing contents will be described with reference to the flowcharts of FIGS.

  FIG. 13 is basically the same processing as that described in FIG. In FIG. 13, after the processing from S411 to S601 is performed, the setting value management server application proceeds to step S1301 when the updated setting value is a setting value related to the synchronization condition of other setting values. In step S1301, the setting value management server application updates the configuration change time in Table 16 corresponding to the notification source device to the current time. For example, the setting value management server application, when the setting value notified of the change is a setting value related to a change in device configuration information as shown in Table 14 (for example, when the “scan and send” function is enabled) ), The process proceeds to step S1301. As described in the first embodiment, when the synchronization process is performed before the time of the configuration change, the setting value that is included in the synchronization condition due to the configuration change is synchronized in the subsequent synchronization process. This is because it may not be acquired as a target.

  Therefore, as a result of the data synchronization processing after the device configuration information has been changed using FIG. 14, the synchronization of the setting values managed by the setting value management server application 310 and the setting value management client application 320 becomes inconsistent. A synchronization method for eliminating the state will be described.

  The processing in FIG. 14 will be described focusing on the differences from FIG. When the user is specified in the synchronization request (S1210 YES) and the synchronization request in which the time is specified is received (S522 YES), the process proceeds to step S1311. In step S1311, the setting value management server application compares the configuration change time of the synchronization request source client shown in Table 16 with the previous synchronization time attached to the synchronization request.

  If the previous synchronization time attached to the synchronization request is earlier than the configuration change time of the device, as described above, the setting values that are included in the synchronization conditions due to the device configuration change are appropriately synchronized. It will not be. Therefore, in step S1312, the setting value management server application creates response data notifying that the synchronization state between the setting value management database 314 and the setting value management database 324 is inconsistent. Then, the process proceeds to step S527, and the created response data is transmitted.

  The setting value management client application 320 receives response data from the setting value management server application in step S1301. In step S <b> 1302, the setting value management client application determines whether the content of the received response data is content for notifying synchronization data inconsistency. If the content does not indicate the synchronization data inconsistency, the process advances to step S1305, and the setting value management client application updates the received data in the same manner as in step S515. Then, as in FIG. 12, S516 is performed and the process ends.

  On the other hand, if the content is notification of inconsistency of the synchronization data, the process proceeds to step S1303. In step S1303, the setting value client application deletes the setting data of the login user stored in the setting value management database 324 of the setting value management client application. In step S1304, the process of step S1203 is executed. That is, in step S1304, the setting value management client application performs a synchronization request that designates a user and does not designate a time to the setting value management server application 310. When the synchronization request in step S1304 is received, NO is determined in S522, and the process proceeds to step S1212. Then, the set value management server application acquires the set value related to the designated user regardless of the last update time of the set value. Since the synchronization request in step S1304 is a request for synchronization without specifying time, the determination in step S1311 of the setting value management server application 310 is not passed again. Further, if the response data is other than that notifying the inconsistency of the synchronization data, all the setting values set in advance by the user are updated and the previous synchronization time is updated. That is, as a result of this second synchronization request, the previous synchronization time managed by the set value client application is also updated appropriately. Therefore, the synchronization request specifying the time before the configuration change time is not executed a plurality of times.

  As a result, even when the setting value is managed for each user of the setting value management server application 310 and the setting value management client application 320, it is possible to eliminate the inconsistency of data synchronization due to the configuration information change.

  Information processing apparatuses that are shared and used by a plurality of users, such as personalized computers and multifunction peripherals in recent years, sometimes store settings associated with each user. According to the present embodiment, in synchronization of data managed for each user, it is possible to prevent inconsistency in the synchronization state due to the configuration change of the information processing apparatus.

<Other examples>
As mentioned above, although each Example and the modification were demonstrated, the Example etc. which were mentioned above are examples for implementing this invention, and may implement | achieve combining the process and operation | movement of each Example and a modification. However, the present invention is not limited to the configuration of the embodiment.

  In addition, the description of the first to third embodiments will mainly explain an example in which inconsistency occurs in data synchronized depending on the presence / absence of a FAX unit, and the fourth embodiment synchronizes depending on the presence / absence of an installed application or an activated license. An example in which inconsistency occurs in the data to be processed has been described. However, the device configuration information may be information indicating whether the predetermined configuration of the client is valid. As another example, the setting value is also changed in the case of changing the presence or absence of a license for the tint block function or the presence or absence of a finisher. In other words, the setting value related to the device configuration includes a setting value indicating whether or not the client device has a license, a setting value indicating whether or not the client device functions, a setting value indicating the license status, or a setting value indicating the function status. It can be. The present invention can be applied to the case where setting values and the like are managed with respect to the configuration information of such a device as a client. As described above, the client need not have a configuration limited to the multi-function peripheral, and can be applied to a device that manages a setting value and an information device terminal that has a change in the setting value depending on information that configures the device. For example, the present invention can be applied to an information processing apparatus having a configuration such as a personal computer, a mobile phone terminal, a smartphone terminal, an image forming apparatus, an electronic timepiece, and an electronic notebook.

  The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program This process can be realized. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

Claims (19)

Connected to a plurality of clients, and in response to a synchronization request from an arbitrary client of the plurality of clients, a setting value updated after the time when the client performed a previous synchronization process is stored in the configuration of the client. An information processing apparatus that transmits to the client based on a corresponding synchronization condition,
First receiving means for receiving a notification of an update of a setting value from the client;
When the setting value included in the notification received by the first receiving unit is a setting value indicating that the configuration of the client has been changed, the setting value is of a type corresponding to the configuration after the change of the client. Setting means for setting the setting information including setting values that have not been updated since the time of the previous synchronization with the client to be transmitted to the client as synchronization target data;
Second receiving means for receiving a synchronization request from the client;
A transmission unit configured to transmit synchronization target data based on the setting of the setting unit to a client that has transmitted the synchronization request received by the second reception unit when the second reception unit receives the synchronization request; A characteristic information processing apparatus.   When the setting is performed by the setting unit, the transmission unit is responsive to the client that has transmitted the synchronization request received by the second reception unit, regardless of the time when the client performed the previous synchronization process. The information processing apparatus according to claim 1, wherein a setting value related to the client is transmitted as synchronization target data.   When the setting is not set in the setting unit, the transmission unit is updated to the client that transmitted the synchronization request received by the second reception unit after the time when the client performed the previous synchronization process. The information processing apparatus according to claim 2, wherein the set value is extracted and transmitted as synchronization target data based on the synchronization condition. Connected to a plurality of clients, and in response to a synchronization request from an arbitrary client of the plurality of clients, a setting value updated after the time when the client performed a previous synchronization process is stored in the configuration of the client. An information processing apparatus that transmits to the client based on a corresponding synchronization condition,
First receiving means for receiving a notification of an update of a setting value from the client;
When the setting value included in the notification received by the first receiving unit is a setting value indicating that the configuration of the client has been changed, the setting value related to the change in the configuration of the client is used as synchronization target data. Setting means for setting transmission to the client;
Second receiving means for receiving a synchronization request from the client;
A transmission unit configured to transmit synchronization target data based on the setting of the setting unit to a client that has transmitted the synchronization request received by the second reception unit when the second reception unit receives the synchronization request; A characteristic information processing apparatus.   When the setting is performed by the setting unit, the transmission unit is updated to the client that transmitted the synchronization request received by the second reception unit after the time when the client performed the previous synchronization process. The information processing apparatus according to claim 4, wherein the setting value and the setting value related to the configuration change are transmitted as synchronization target data.   The transmission means is updated to the client that has transmitted the synchronization request received by the second reception means after the time when the client performed the previous synchronization processing when the setting is not set in the setting means. 6. The information processing apparatus according to claim 5, wherein a set value is extracted and transmitted as synchronization target data based on the synchronization condition. A setting value that is transmitted after the time is transmitted from the server to the server as a client including a time at which the previous synchronization processing was performed, and is extracted based on the synchronization condition corresponding to the configuration of the client An information processing device that functions as the client,
First detection means for detecting a change in a setting value managed in the client;
If the detected change in the setting value is a change in the setting value related to the synchronization condition, setting means for setting information indicating that the setting value related to the synchronization condition has been changed;
Second detection means for detecting timing for making a synchronization request to the server;
A transmission means for transmitting a synchronization request to the server based on the information set by the setting means when the second detection means detects the timing of making the synchronization request;
An information processing apparatus comprising: an updating unit configured to update a setting value managed in the client using a setting value transmitted from the server in response to a synchronization request transmitted by the transmitting unit.   The transmission means, when the information is set by the setting means, transmits a synchronization request including a request to return all setting values related to the client as response data to the client. The information processing apparatus according to claim 7.   9. The information processing according to claim 8, wherein, when the information is set by the setting unit, the transmission unit transmits a synchronization request that does not include a time at which a previous synchronization process was performed to the server. apparatus.   10. The information according to claim 8, wherein, when the information is not set by the setting unit, the transmission unit transmits a synchronization request including a time when a previous synchronization process is performed to the server. Processing equipment. An information processing apparatus,
Management means for managing the first time when the configuration of the client device connected to the information processing device is changed in association with the client device;
Acquisition means for acquiring information indicating a second time when the client device and the previous set value were synchronized;
When the second time acquired by the acquisition unit is after the first time, the setting value is of a type corresponding to the changed configuration of the client device and has been updated after the second time. Sending a set value to the client device;
If the second time acquired by the acquisition means is earlier than the first time, it is a set value of a type corresponding to the changed configuration of the client device and has not been updated after the second time An information processing apparatus comprising: transmission means for transmitting setting information including a setting value to the client apparatus. The acquisition means is a synchronization request including identification information of the user of the client device, and acquires the second time when the previous synchronization processing was performed for the setting value associated with the user,
When the second time acquired by the acquiring unit is after the first time, the transmitting unit is a set value of a type corresponding to the changed configuration of the client device and the identification information of the user. A setting value updated after the second time is transmitted to the client device;
When the second time acquired by the acquisition unit is earlier than the first time, the second time is a set value of a type corresponding to the changed configuration of the client device and the user identification information. 12. The information processing apparatus according to claim 11, wherein setting information including setting values that have not been updated thereafter is transmitted to the client apparatus.   11. The synchronization condition according to claim 1, wherein when the predetermined configuration of the client is not valid, a setting value related to the predetermined configuration is excluded from a synchronization target. The information processing apparatus described.   Whether or not the predetermined configuration is valid is a setting value indicating presence or absence of a license for the client device, a setting value indicating presence or absence of a function of the client device, a setting value indicating the state of the license, or the The information processing apparatus according to claim 13, wherein the information processing apparatus is determined based on at least one of setting values indicating a function state. In connection with a plurality of clients, in response to a synchronization request from an arbitrary client of the plurality of clients, a setting value updated after the time when the client performed a previous synchronization process is stored in the configuration of the client. A data synchronization method for transmitting to the client based on a corresponding synchronization condition,
A first receiving step of receiving a notification of a set value update from the client;
When the setting value included in the notification received in the first reception step is a setting value indicating that the configuration of the client has been changed, the setting value is of a type corresponding to the configuration after the change of the client. A setting step for setting transmission of setting information including setting values that have not been updated since the time of the previous synchronization with the client as data to be synchronized to the client;
A second receiving step of receiving a synchronization request from the client;
A transmission step of transmitting synchronization target data based on the setting of the setting step to the client that has transmitted the synchronization request received in the second reception step when the synchronization request is received in the second reception step. A featured data synchronization method. Connected to a plurality of clients, and in response to a synchronization request from an arbitrary client of the plurality of clients, a setting value updated after the time when the client performed a previous synchronization process is stored in the configuration of the client. A data synchronization method for transmitting to the client based on a corresponding synchronization condition,
A first receiving step of receiving a notification of a set value update from the client;
When the setting value included in the notification received in the first reception step is a setting value indicating that the configuration of the client has been changed, the setting value related to the change in the configuration of the client is used as the synchronization target data. A configuration step to configure sending to the client;
A second receiving step of receiving a synchronization request from the client;
A transmission step of transmitting synchronization target data based on the setting in the setting step to the client that has transmitted the synchronization request received in the second reception step when the synchronization request is received in the second reception step. A data synchronization method characterized by the above. A synchronization request including the time when the previous synchronization processing was performed is transmitted to the server as a client, and the setting value updated from the server after the time and extracted based on the synchronization condition corresponding to the configuration of the client A data synchronization method for receiving
A first detection step of detecting a change in a setting value managed in the client;
A setting step for setting information indicating that the setting value related to the synchronization condition has been changed, when the detected change in the setting value is a change of the setting value related to the synchronization condition;
A second detection step of detecting timing for making a synchronization request to the server;
A transmission step of transmitting a synchronization request to the server based on the information set in the setting step when detecting the timing of performing the synchronization request in the second detection step;
A data synchronization method comprising: an update step of updating a setting value managed in the client using a setting value transmitted from the server in response to the synchronization request transmitted in the transmission step. A data synchronization method in the information processing apparatus having a management unit that manages a first time when a configuration of a client apparatus connected to the information processing apparatus is changed in association with the client apparatus,
An acquisition step of acquiring information indicating a second time at which the client device and the previous set value were synchronized;
When the second time acquired in the acquisition step is later than the first time, the setting value is of a type corresponding to the changed configuration of the client device and has been updated after the second time. Sending a set value to the client device;
If the second time acquired in the acquisition step is earlier than the first time, it is a set value of a type corresponding to the changed configuration of the client device and has not been updated after the second time A data synchronization method comprising: transmitting setting information including a setting value to the client device.   The program for functioning a computer as each means of the information processing apparatus as described in any one of Claims 1-14.