Information Processing Systems

Abstract

To provide a new technology capable of remotely managing setting of an apparatus.SOLUTION: A system 1 includes a first communication device 2 and a second communication device 3, which can communicate with a cloud storage 6. The first communication device is configured so as to store setting data describing an operation condition to be set in an apparatus 5 managed by the second communication device. The first communication device is configured so as to execute first communication processing. The first communication processing includes writing the setting data in the cloud storage. The second communication device is configured so as to execute second communication processing. The second communication processing includes accessing the cloud storage to acquire the setting data written in the cloud storage, and updating the operation condition set in the apparatus to an operation condition described by the setting data acquired from the cloud storage.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to an information processing system. [Background technology]

[0002] A system is already known in which a server device acquires setting information for an image forming device from a management device and provides the acquired setting information to the image forming device in response to an inquiry from the image forming device. According to this system, a setting unit of the image forming device acquires the setting information sent from the server device and configures the image forming device using the acquired information (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-148957 Summary of the Invention [Problem to be solved by the invention]

[0004] In conventional systems, the setting operation of the image forming apparatus is realized by the active operation of the server device, but this technology requires the construction of a dedicated server device.

[0005] Therefore, according to one aspect of the present disclosure, it is desirable to provide a new technology that enables remote management of device settings without using a dedicated server device. [Means for solving the problem]

[0006] According to one aspect of the present disclosure, there is provided an information processing system including a first communication device and a second communication device capable of communicating with a cloud storage.

[0007] The first communication device includes a communication processing unit and a storage unit. The storage unit is configured to store setting data describing operating conditions to be set in a device managed by the second communication device. The communication processing unit is configured to execute a first communication process. The first communication process includes writing the setting data stored in the storage unit to cloud storage.

[0008] The second communication device is configured to execute a second communication process, which includes repeatedly accessing the cloud storage to acquire setting data written in the cloud storage, and updating operating conditions set in the device to the operating conditions described in the setting data acquired from the cloud storage.

[0009] This information processing system allows device settings to be remotely managed via the first communication device, the second communication device, and cloud storage. By using cloud storage, there is no need to build a dedicated server device and place it on a wide area network to remotely manage device settings.

[0010] Therefore, according to one aspect of the present disclosure, a novel technique can be provided that enables remote management of device settings without using a dedicated server device. Furthermore, device settings can be proactively managed by an administrator using a first communication device. Therefore, even in an environment where device settings may be changed by device users, the administrator can appropriately manage the device settings. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 2 is a block diagram illustrating the configuration of a management system and a cloud server. [Figure 2] FIG. 2 is a block diagram showing the configuration of a master. [Figure 3] FIG. 2 is a block diagram showing the configuration of a client and a device. [Figure 4] 10 is a flowchart showing a remote setting process repeatedly executed by a master processor. [Figure 5] FIG. 2 is a diagram illustrating a device management database and a setting file stored in a master storage. [Figure 6] FIG. 10 is an explanatory diagram regarding registration of request data and setting files to a cloud server. [Figure 7] 10 is a flowchart showing a monitoring process repeatedly executed by a master processor. [Figure 8] 10 is a flowchart showing a setting-related process repeatedly executed by a processor of a client. [Figure 9] 10 is a flowchart illustrating a setting process executed by a processor of a client. DETAILED DESCRIPTION OF THE INVENTION

[0012] Exemplary embodiments of the present disclosure will now be described with reference to the drawings. [Overall configuration] The management system 1 of this embodiment shown in Fig. 1 is an information processing system configured to remotely manage one or more devices 5 through cooperation between a master 2 and a client 3. In Fig. 1, a plurality of devices 5 are shown as examples of the one or more devices 5.

[0013] The master 2 is connected to a local area network N1 established at a first base. The master 2 is configured to be able to communicate with a cloud server 6 connected to a wide area network N2 via the local area network N1 and a router (not shown).

[0014] The client 3 is connected to a local area network N3 established at a second location. The client 3 is configured to be able to communicate with a device 5 connected to the local area network N3.

[0015] The client 3 is further configured to be able to communicate with a cloud server 6 connected to a wide area network N2 via a local area network N3 and a router (not shown). The local area networks N1 and N3 may include at least one of a wireless LAN and a wired LAN. The wide area network N2 may include the Internet.

[0016] The device 5 is connected to the same local area network N3 as the client 3 and is configured to be able to communicate with the client 3. Unlike the client 3, the device 5 does not have the ability to use cloud services provided by the cloud server 6.

[0017] Therefore, the devices 5 are managed directly by the clients 3 and indirectly by the master 2 via the clients 3 and the cloud server 6. One or more of the devices 5 may not be connected to the local area network N3, and may be connected by wire or wirelessly to the clients 3 so as to be able to communicate directly with them, as shown by the dashed arrows in FIG. 1.

[0018] The managed device 5 may be, for example, a device used by an organization such as a company. In this case, each location may be an activity base of the organization. For example, the first location where the master 2 is located may be an office that houses the management department of the organization. The second location may be a branch office of the organization that is located away from the first location. There may be multiple second locations. A local area network N3 to which the client 3 and the device 5 are connected may be constructed at each of the multiple second locations.

[0019] Examples of the device 5 include a printer, a scanner, and a digital multifunction peripheral that integrates the functions of these. The master 2 and the client 3 are configured, for example, by installing a dedicated computer program on a personal computer.

[0020] [Device configuration] 2 includes a processor 21, a memory 23, a storage 25, a user interface 27, and a communication interface 29. The processor 21 executes processing in accordance with a computer program stored in the storage 25, which serves as a storage unit.

[0021] The memory 23 includes a RAM and is used as a working memory when processing is executed. The storage 25 stores computer programs for executing processing required for managing the devices 5 through the cloud server 6 and the client 3. Examples of the storage 25 include a hard disk drive and a solid state drive.

[0022] The storage 25 further stores a setting file D0 (see FIG. 5) that describes operating conditions to be set in the device 5. The setting file D0 describes, as operating conditions for the device 5, values ​​to be set for each of a plurality of operating parameters that define the operation of the device 5. Setting operating conditions in the device 5 corresponds to providing the device 5 with information that defines the operation of the device 5 and / or specifies the operation content of the device 5.

[0023] The user interface 27 is configured to receive operations from an administrator who operates the master 2, and further to display various information to the administrator. The user interface 27 includes a display unit 27A and an operation unit 27B.

[0024] The display unit 27A includes, for example, a liquid crystal display to display various information to the administrator. The operation unit 27B includes one or more input devices for inputting operation signals from the administrator who operates the master 2. Examples of the input devices include a keyboard and a pointing device.

[0025] The communication interface 29 is connected to the local area network N1 and is configured to be able to communicate with nodes connected to the local area network N1, and further to be able to communicate with nodes connected to the wide area network N2 via a router not shown.

[0026] 3 includes a processor 31, a memory 33, a storage 35, a user interface 37, and a communication interface 39. The processor 31 executes processing in accordance with a computer program stored in the storage 35.

[0027] The memory 33 includes a RAM and is used as a working memory when processing is performed. The storage 35 stores computer programs for executing processing required to manage the devices 5 based on requests from the master 2 via the cloud server 6.

[0028] The user interface 37 is configured to receive operations from a user who operates the client 3 and display various information to the user. The communication interface 39 is connected to the local area network N3 and is configured to be able to communicate with nodes connected to the local area network N3 and further to be able to communicate with nodes connected to the wide area network N2 via a router (not shown).

[0029] As shown in FIG. 1, the cloud server 6 includes a processor 61, a memory 63, a first storage 67, and a second storage 69, and is configured to be able to communicate with the master 2 and the client 3 via the wide area network N2.

[0030] The processor 61 executes processing in accordance with a computer program stored in the memory 63. Execution of the above processing by the processor 61 causes the cloud server 6 to function as cloud storage. The cloud storage includes table storage and object storage. The first storage 67 functions as table storage, and the second storage 69 functions as object storage.

[0031] The exemplary first storage 67 functions as a NoSQL data store and is configured to be able to store tables each having a group of schema-less entities as components. The exemplary second storage 69 functions as an object storage that can externally read and write any text file or binary file as an object using the HTTP / HTTPS protocol.

[0032] Microsoft's Azure (registered trademark) is a known cloud service that provides the above-mentioned table storage and object storage. The cloud server 6 can operate in the same manner as such a cloud service.

[0033] [Processing details] Next, the process executed by the processor 21 of the master 2 to manage the operating conditions of the device 5 will be described in detail.

[0034] The master 2 manages the operating conditions of the device 5 by executing a process to return at least some of the operating conditions, which have been changed by a user of the device 5 via the operation panel 51 of the device 5, to the standard operating conditions. This process is performed, for example, to return operating conditions that have deviated from the administrator's management tolerance range to the standard operating conditions.

[0035] The processor 21 of the master 2 periodically and repeatedly executes the remote setting process shown in Fig. 4 to manage the operating conditions of the devices 5. When the processor 21 starts the remote setting process, it refers to the management database 251 shown in Fig. 5 and determines whether or not there is any device 5 for which the setting timing has arrived (S110). The setting timing is the timing to set the operating conditions of the device 5 back to the standard operating conditions.

[0036] As shown in FIG. 5, the management database 251 has, for each managed device 5, device management data 253 including a device ID that is an identifier of the corresponding device 5, definition information that defines the setting timing of the corresponding device 5, and designated file information that specifies the setting file D0 to be used for setting the device 5.

[0037] The definition information defines the setting timing, for example, on a daily or weekly basis. Alternatively, the definition information defines the setting timing as a date and time, such as noon every Monday. The specified file information indicates the storage location in storage 25 of the setting file D0 to be used for setting device 5.

[0038] If the processor 21 determines that there is no device 5 whose setting timing has arrived, it ends the remote setting process. If the processor 21 determines that there is a device 5 whose setting timing has arrived (Yes in S110), it generates request data D1 requesting the client 3 managing the device 5 whose setting timing has arrived to execute a setting task (S120).

[0039] 6, the request data D1 includes request detail information, request destination information, and status information. The request detail information indicates that the request data D1 is data requesting the execution of a configuration task, along with the storage location in the second storage 69 of the configuration file D0 to be used for executing the configuration task.

[0040] The request destination information indicates the device ID of the device 5 for which the setting timing has arrived, and is the setting destination. The status information is information that indicates the execution status of the setting task. The status indicated when the request data D1 is generated is "request", which indicates that execution of the setting task is being requested.

[0041] Thereafter, the processor 21 communicates with the cloud server 6 via the communication interface 29, and registers the request data D1 generated in S120 as one entity in a table 67A for request data registration prepared in the first storage 67 (S130).

[0042] Furthermore, processor 21 stores configuration file D0 to be used for executing the configuration task in the storage location of second storage 69 described in request data D1 (S130). The corresponding configuration file D0 is read from storage 25 by referring to device management data 253, and stored in second storage 69 of cloud server 6. Thereafter, processor 21 ends the remote configuration process. When there are multiple devices 5 for which the configuration timing has arrived, processor 21 can execute the processes of S120 to S130 for each of the devices 5.

[0043] In addition, the processor 21 periodically and repeatedly executes the monitoring process shown in Fig. 7. This monitoring process is executed, for example, following the remote setting process shown in Fig. 3. That is, in this embodiment, the remote setting process shown in Fig. 3 and the subsequent monitoring process shown in Fig. 7 are periodically executed by the processor 21. As a result, the processor 21 is configured to monitor the execution of a setting task at the client 3 based on the request data D1 registered in table 67A in S130, and execute processing in response to the completion of the setting task.

[0044] 7, the processor 21 selects one of the request data D1 registered in the table 67A of the cloud server 6 as the processing target (S210). In the following S220, the processor 21 refers to the status information of the request data D1 to be processed and determines whether or not the request data D1 to be processed has a status of "completed."

[0045] The "completed" status of the request data D1 relating to the setting task indicates that the corresponding setting task has been executed by the client 3 and that the updating of the operating conditions of the device 5 based on the setting file D0 has been completed.

[0046] When the processor 21 determines that the request data D1 to be processed is request data D1 indicating a "completed" status (Yes in S220), it deletes the request data D1 to be processed and the setting file D0 associated with the request data D1 from the cloud server 6 (S230).

[0047] The setting file D0 to be erased is a setting file D0 whose storage location is described in the request data D1 to be erased, and is thereby associated with the request data D1, and is a setting file D0 that has been registered on the cloud server 6 together with the request data D1.

[0048] Specifically, the processor 21 deletes the request data D1 from the table 67A and deletes the setting file D0 associated with the request data D1 from the second storage 69 (S230). After that, the processor 21 executes the process of S260.

[0049] When the processor 21 determines that the request data D1 to be processed is not request data D1 indicating the "completed" status (No in S220), the processor 21 executes the process of S240. In S240, the processor 21 determines whether the request data D1 to be processed is old request data D1 for which a predetermined time has elapsed since it was registered in the table 67A.

[0050] The predetermined time may be, for example, 500 seconds or 10 minutes. To determine the time elapsed since registration, the processor 21 can store, in the storage 25, log data describing the registration content and the registration time for each registration of the request data D1 in the table 67A.

[0051] When the processor 21 determines that the request data D1 to be processed is old request data D1 for which a predetermined time has passed since its registration (Yes in S240), it deletes the request data D1 to be processed and the setting file D0 associated with the request data D1 from the cloud server 6 (S250). Thereafter, the processor 21 executes the process of S260. When the request data D1 to be processed is request data D1 for which a predetermined time has not passed since its registration (No in S240), the processor 21 executes the process of S260 without executing the process of S250.

[0052] In S260, the processor 21 determines whether or not all of the request data D1 registered in the table 67A have been selected in the processing of S210. If it is determined that no request data D1 has been selected (No in S260), the processor 21 selects one of the unselected request data D1 registered in the table 67A as the processing target (S210), and executes the processing from S220 onwards for the new request data D1 to be processed.

[0053] After individually selecting all of the request data D1 registered in the table 67A and executing the processes from S220 onwards, the processor 21 makes an affirmative determination in S260 and ends the monitoring process.

[0054] In this way, during the monitoring process, the processor 21 deletes from the cloud server 6 the configuration file D0 for which the configuration of the device 5 based on the request data D1 has been completed, and the configuration file D0 associated with the request data D1 that has not been processed for a long time, thereby reducing the possibility that the configuration file D0 on the cloud server 6 will be tampered with.

[0055] 8, the processor 31 of the client 3 periodically and repeatedly accesses the cloud server 6 and executes a setting task based on the request data D1 registered in the cloud server 6 by the master 2. The processor 31 can execute the setting-related process, for example, at one-minute intervals.

[0056] When the setting-related process starts, the processor 31 refers to the first storage 67 of the cloud server 6 and searches for unprocessed request data D1 related to the setting task registered in the table 67A (S310). The processor 31 can determine that the request data D1 in the "Request" status is unprocessed request data D1.

[0057] If no unprocessed request data D1 is found (S320 No), the processor 31 ends the setting-related process. If one or more unprocessed request data D1 are found (S320 Yes), the processor 31 determines whether the unprocessed request data D1 is addressed to itself (S330).

[0058] The processor 31 can determine that the request data D1, in which the device ID of the device 5 managed by the processor 31 is described in the request destination information included in the request data D1, is the request data D1 addressed to the processor 31 itself.

[0059] The storage 35 of the client 3 stores a device list that lists the devices 5 in the local area network N3 managed by the client 3. The device list associates the device IDs of the managed devices 5 with node information for communicating with the corresponding devices 5 through the local area network N3.

[0060] The node information may include information on the MAC address and / or IP address of the device 5. Based on the device list stored in the storage 35, the processor 31 can determine whether the unprocessed request data D1 includes request data D1 addressed to itself.

[0061] If processor 31 determines that request data D1 addressed to itself does not exist (No in S330), it ends the setting-related processing. If processor 31 determines that request data D1 addressed to itself exists (Yes in S330), it starts executing the setting processing shown in Fig. 9 based on the request data D1 addressed to itself as the requested setting task (S340).

[0062] When there are multiple pieces of request data D1 addressed to the processor 31, the processor 31 can execute the setting process for each piece of request data D1, with the corresponding piece of request data D1 being the processing target. After executing the process of S340, the processor 31 ends the setting-related process.

[0063] When the setting process shown in FIG. 9 starts, the processor 31 updates the status information of the request data D1 to be processed stored in the table 67A so as to update the status of the request data D1 to be processed to "in progress" (S410).

[0064] Furthermore, the processor 31 acquires the setting file D0 associated with the request data D1 to be processed from the second storage 69 of the cloud server 6 (S420). Specifically, the processor 31 acquires the setting file D0 associated with the request data D1 by downloading the setting file D0 stored in the storage location described in the request data D1 to be processed (S420).

[0065] Thereafter, the processor 31 communicates with the device 5 indicated as request destination information in the request data D1 to be processed via the communication interface 39, and sets the operating conditions of the device 5 to the operating conditions described in the setting file D0 (S430).

[0066] That is, the processor 31 updates the setting values ​​of the operation parameters that define the operating conditions of the device 5 stored in the memory 53 of the device 5 to the setting values ​​of the operation parameters described in the setting file D0 (S430).

[0067] The memory 53 includes NVRAM, which is a nonvolatile memory that allows data to be electrically rewritten. Examples of NVRAM include flash memory and EEPROM. In the device 5, the setting values ​​of each operating parameter are stored in the NVRAM as data that will not volatilize even when the device 5 is shut down.

[0068] When the setting of the operating conditions is completed, the processor 31 accesses the cloud server 6 and updates the status information of the request data D1 to be processed stored in the table 67A of the first storage 67 so as to update the status of the request data D1 to be processed to "completed" (S440). Thereafter, the processor 31 ends the setting process.

[0069] Updating the status of the request data D1 to "completed" corresponds to writing, as status information, a message indicating that the corresponding setting task has been completed in the table 67A of the first storage 67.

[0070] According to the management system 1 of this embodiment described above, the setting values ​​of a plurality of devices 5 that belong to a local area network N3 that is different from the local area network N1 to which the master 2 belongs are remotely and centrally managed from the master 2. Moreover, the remote management of the devices 5 is realized by data exchange between the master 2 and the clients 3 via the cloud server 6 that functions as cloud storage.

[0071] By using cloud storage as a relay device for node communication between different local area networks N1 and N3, there is no need to build a dedicated server device in the wide area network N2 for remote management of device 5. By using general-purpose cloud storage as a relay device, the system operation costs for remote management of device 5 can be reduced.

[0072] However, when a dedicated server device is used as a relay device, special processing for remote management of device 5 can be realized by the dedicated server device, but when a general-purpose cloud storage is used, special processing for remote management of device 5 cannot be realized by the cloud storage.

[0073] Therefore, in this embodiment, the master 2 operates independently and periodically writes the request data D1 and the setting file D0 to the cloud server 6, thereby realizing periodic updates of the settings of the device 5 via the client 3.

[0074] 8 in a cycle that is sufficiently shorter than the cycle in which the master 2 writes the request data D1 and the setting file D0 to the cloud server 6. This allows the setting task to be executed quickly (in other words, substantially immediately) in response to a request from the master 2, and realizes periodic updates of the settings of the device 5 in response to periodic requests from the master 2.

[0075] With periodic updates, even if the settings of the device 5 are changed by a user operating the operation panel 51 of the device 5, the changed settings can be restored to the standard settings, thereby preventing the device 5 from operating for a long period of time based on the changed settings.

[0076] Therefore, if the setting value of the device 5 is changed to a setting value that is undesirable from a security standpoint, for example, the state of the device 5 that is undesirable from a management standpoint can be restored to the original appropriate state by regular operation. In this way, according to this embodiment, the settings of the device 5 can be remotely and appropriately managed while using cloud storage.

[0077] Furthermore, in this embodiment, the setting file D0 registered in the cloud server 6 is deleted from the cloud server 6 upon completion of the corresponding setting task. Furthermore, in this embodiment, the setting file D0 registered in the cloud server 6 is deleted from the cloud server 6 when a predetermined time has elapsed since registration. Therefore, it is possible to appropriately manage the settings of the device 5 based on the setting file D0.

[0078] For example, consider an example in which the setting file D0 is stored for a long period of time in the cloud server 6. In this example, the client 3 can periodically read the setting file D0 registered in the cloud server 6 and periodically update the settings of the device 5. In this example, the master 2 does not need to perform periodic operations.

[0079] However, if the setting file D0 remains registered in the cloud server 6 for a long period of time, there is an increased possibility that the setting file D0 will be tampered with. If the setting of the device 5 is based on the tampered setting file D0, the device 5 cannot be managed appropriately.

[0080] In this embodiment, the management system 1 does not store the setting file D0 on the cloud server 6 for a long period of time, and furthermore, updates to the settings of the device 5 are realized in response to an operation from the master 2, specifically, the write operation of the request data D1 and the setting file D0 from the master 2. This reduces the possibility of tampering with the setting file D0, and allows the settings of the device 5 to be managed appropriately.

[0081] The present disclosure is not limited to the above embodiment, and various modifications are possible. For example, the master 2 may be configured to overwrite and update the setting file D0 on the cloud server 6.

[0082] For example, in a configuration in which the client 3 configures the device 5 upon writing the request data D1 to the cloud server 6, an unaltered, legitimate configuration file D0 is written to the cloud server 6 in addition to writing the request data D1, thereby reducing the possibility that the device 5 will be configured based on a tampered configuration file.

[0083] The master 2 may be configured to write only the setting file D0 without writing the request data D1 to the cloud server 6. The client 3 may be configured to configure the device 5 in response to the writing of the setting file D0 by the master 2.

[0084] The setting file D0 and the request data D1 may be integrated. That is, the request data D1 may include setting values ​​for each operating parameter as the operating conditions to be set in the device 5.

[0085] The master 2 may be configured to write the request data D1 and the setting file D0 to the cloud server 6 on an irregular basis or based on instructions from an administrator. The client 3 may also be configured to access the cloud server 6 on an irregular basis and refer to the request data D1.

[0086] The function of one component in the above embodiments may be distributed among multiple components. The functions of multiple components may be integrated into one component. Part of the configuration of the above embodiments may be omitted. At least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments. All aspects included in the technical idea identified from the wording of the claims are embodiments of the present disclosure.

[0087] [Correspondence between terms] The first storage 67 and the second storage 69 included in the cloud server 6 correspond to an example of cloud storage. The master 2 corresponds to an example of a first communication device, and the client 3 corresponds to an example of a second communication device.

[0088] The processor 21 of the master 2 corresponds to an example of a communication processing unit. The remote setting process and monitoring process executed by the processor 21 of the master 2 correspond to an example of a first communication process, and the setting-related process and setting process executed by the processor 31 of the client 3 correspond to an example of a second communication process. [Explanation of symbols]

[0089] 1...management system, 2...master, 3...client, 5...device, 6...cloud server, 21,31,61...processor, 23,33,63...memory, 25,35...storage, 27,37...user interface, 29,39...communication interface, 51...operation panel, 53...memory, 67...first storage, 67A...table, 69...second storage, 251...management database, 253...device management data, D0...setting file, D1...request data, N1,N3...local area network, N2...wide area network.

Claims

1. A first communication device and a second communication device capable of communicating with cloud storage Equipped with the first communication device, a communication processing unit configured to perform a first communication process; a storage unit configured to store configuration data describing operating conditions to be set in devices managed by the second communication device; Equipped with the first communication process includes writing the setting data stored in the storage unit to the cloud storage; the second communication device is configured to perform a second communication process; The second communication process includes: repeatedly accessing the cloud storage to obtain the setting data written to the cloud storage; updating the operating conditions set in the device to the operating conditions described in the setting data acquired from the cloud storage; On condition that the update of the operating conditions based on the setting data has been completed, writing a message indicating that the update has been completed to the cloud storage; Including, The first communication process includes repeatedly accessing the cloud storage and erasing the setting data from the cloud storage on condition that the message has been written to the cloud storage. Information processing system.

2. A first communication device and a second communication device capable of communicating with cloud storage Equipped with the first communication device, a communication processing unit configured to perform a first communication process; a storage unit configured to store configuration data describing operating conditions to be set in devices managed by the second communication device; Equipped with The first communication process includes: writing the setting data stored in the storage unit to the cloud storage; writing request data requesting an update of the operating conditions set in the device to the cloud storage in association with the setting data; Including, the second communication device is configured to perform a second communication process; The second communication process includes: repeatedly accessing the cloud storage, and, on condition that the requested data has been written to the cloud storage, acquiring the setting data associated with the requested data and written to the cloud storage; updating the operating conditions set in the device to the operating conditions described in the setting data acquired from the cloud storage; An information processing system including:

3. the second communication process includes, on condition that the update of the operating conditions based on the setting data has been completed, writing a message indicating that the update has been completed to the cloud storage; The first communication process includes repeatedly accessing the cloud storage and erasing the setting data from the cloud storage on condition that the message has been written to the cloud storage.

3. The information processing system according to claim 2.

4. The information processing system according to claim 2 , wherein the first communication process includes deleting the setting data from the cloud storage when a predetermined time has elapsed since the setting data was written to the cloud storage.

5. The first communication process includes erasing the setting data from the cloud storage when a predetermined time has elapsed after the setting data has been written to the cloud storage, regardless of whether the message has been written to the cloud storage.

4. The information processing system according to claim 1.

6. 5. The information processing system according to claim 2, wherein in the first communication process, the request data and the setting data are periodically and repeatedly written to the cloud storage.

7. The information processing system according to claim 1 or 5, wherein in the first communication process, the setting data is periodically and repeatedly written to the cloud storage.

Images