Patent Application
20240314247
This application is based on and claims priority under 35 USC 119 from Japanese Patent Application No. 2023-043089 filed Mar. 17, 2023.
The present disclosure relates to an information processing system, a non-transitory computer readable medium, and an information processing method.
Japanese Unexamined Patent Application Publication No. 2017-038356 proposes an information processing apparatus including: a management unit configured to manage setting information about settings of an image forming apparatus; a receiving unit configured to receive, from the image forming apparatus, setting information held by the image forming apparatus in a case where the image forming apparatus is connected to the information processing apparatus, and receives, from the image forming apparatus, information indicating update content of setting information held by the image forming apparatus in a case where the setting information is updated after the image forming apparatus is connected to the information processing apparatus; and a transmitting unit configured to transmit, as a response to reception of setting information in a case where the image forming apparatus is connected to the information processing apparatus, a response to the image forming apparatus indicating whether to transmit information indicating update content from the image forming apparatus to the information processing apparatus in units of setting items.
Prior to the initial installation of a machine such as an image forming apparatus, it is conceivable to configure settings in an environment different from the machine to be actually installed, such as a reproducing environment that reproduces the actual machine, e.g., a cloud environment, and to reflect the settings onto the machine to be actually installed at the time of the initial installation of the machine. Here, for example, the machine may be shipped from the factory with settings that are adjusted from the initial settings. As above, in the case where the machine has settings different from the initial settings prior to the initial installation, if settings configured on the basis of the initial settings in an environment different from the machine to be actually installed are reflected onto the actual to-be-installed machine which is to be initialized, this reflection becomes, for example, one that disregards the settings changed upon shipment from the factory, and an inconvenience may arise.
Aspects of non-limiting embodiments of the present disclosure relate to an information processing system, a non-transitory computer readable medium, and an information processing method capable of reflecting settings configured in an environment different from a machine to be actually installed onto a machine to be installed without causing any inconvenience.
Aspects of certain non-limiting embodiments of the present disclosure address the above advantages and/or other advantages not described above. However, aspects of the non-limiting embodiments are not required to address the advantages described above, and aspects of the non-limiting embodiments of the present disclosure may not address advantages described above.
According to an aspect of the present disclosure, there is provided an information processing system including a processor configured to perform a process, the process including: holding, in a predetermined region, specific setting information that is setting information to be reflected onto a machine to be installed and that has been specified in an environment different from a machine to be actually set up; and, in reflecting the specific setting information onto the machine, in a case where it is determined that a conflict occurs between the specific setting information held in the predetermined region and setting information preconfigured on the machine, notifying a predetermined notification destination, receiving a command to resolve the conflict, and reflecting the conflict-resolved setting information onto the machine.
An exemplary embodiment of the present disclosure will be described in detail based on the following figures, wherein:
Hereinafter, an exemplary embodiment of the present disclosure will be described in detail with reference to the drawings.
The image forming system 10 according to the present exemplary embodiment includes, as illustrated in
The local server 11 and the image forming devices 12 are each connected to an internal communication line 17, such as a local area network (LAN) or an intranet. The internal communication line 17 and the cloud server 14 are each connected to an external communication line 18, such as a wide area network (WAN) or the Internet. The local server 11, the image forming devices 12, and the cloud server 14 are each configured to be able to transmit and receive various types of data to and from each other via the internal communication line 17 and the external communication line 18.
The image forming device 12 according to the present exemplary embodiment includes, as illustrated in
The image forming device 12 according to the present exemplary embodiment also includes a hard disk drive (HDD) 26, which stores various types of data, application programs, and the like. The image forming device 12 further includes a display controller 28, which is connected to a user interface 22 and which controls the displaying of various operation screens and the like on a display of the user interface 22. Moreover, the image forming device 12 includes an operation input detector 30, which is connected to the user interface 22 and which detects operation commands input via the user interface 22. In the image forming device 12, the HDD 26, the display controller 28, and the operation input detector 30 are electrically connected to the system bus 42. Although an example in which the image forming device 12 according to the present embodiment includes the HDD 26 is described, this is not the only possible case, and the image forming device 12 may include a non-volatile memory such as a flash memory.
The image forming device 12 according to the present exemplary embodiment includes a reading controller 32, which controls an optical image reading operation performed by a document reader 46 and a document feed operation performed by a document feeder, and an image formation controller 34, which controls image formation processing performed by an image forming unit 24, and the conveyance of paper to the image forming unit 24 by a conveying unit 25. The image forming device 12 also includes a communication line interface (communication line I/F) unit 36, which is connected to the internal communication line 17 and which transmits and receives communication data to and from another device connected to the internal communication line 17, and an image processor 44, which performs various types of image processing. The image forming device 12 further includes a facsimile interface (facsimile I/F) unit 38, which is connected to an unillustrated phone line and which transmits and receives facsimile data to and from a facsimile machine connected to the phone line. The image forming device 12 also includes a transmission/reception controller 40, which controls the transmission and reception of facsimile data via the facsimile interface unit 38. In the image forming device 12, the transmission/reception controller 40, the reading controller 32, the image formation controller 34, the communication line interface unit 36, the facsimile interface unit 38, and the image processor 44 are electrically connected to the system bus 42. With the above configuration, the image forming device 12 according to the present exemplary embodiment executes, using the CPU 20A, access to each of the RAM 20C, the ROM 20B, and the HDD 26. The image forming device 12 executes, using the CPU 20A, control of displaying of information such as operation screens and various messages on the display of the user interface 22 via the display controller 28. The image forming device 12 also executes, using the CPU 20A, control of the operation of the document reader 46 and the document feeder via the reading controller 32. In addition, the image forming device 12 executes, using the CPU 20A, each of control of the operation of the image forming unit 24 and the conveying unit 25 via the image formation controller 34, and control of the transmission and reception of communication data via the communication line interface unit 36. Moreover, the image forming device 12 executes, using the CPU 20A, control of the transmission and reception of facsimile data via the facsimile interface unit 38 by the transmission/reception controller 40. Furthermore, the image forming device 12 executes, using the CPU 20A, the grasping of the operation contents of the user interface 22 based on operation information detected by the operation input detector 30, and executes various types of control based on the operation contents.
Next, the configuration of the principal parts of the electrical system of the local server 11 and the cloud server 14 in the image forming system 10 according to the present exemplary embodiment will be described.
The cloud server 14 according to the present exemplary embodiment includes, as illustrated in
With the above configuration, the cloud server 14 according to the present exemplary embodiment executes, using the CPU 14A, access to the ROM 14B, the RAM 14C, and the storage 14D, obtaining of various types of data via the operation unit 14E, and displaying of various types of information on the display 14F. In addition, the cloud server 14 executes, using the CPU 14A, control of the transmission and reception of communication data via the communication line interface unit 14G.
The local server 11 configured as described above has the function of a managed print service (MPS) which manages multiple image forming devices 12. Note that the local server 11 may be referred to as the MPS 11 with the same reference numerals. Moreover, the image forming device 12 may be referred to as the real device 12 with the same reference numerals.
As illustrated in
In the image forming system 10 according to the present exemplary embodiment, for example, as illustrated in
Then, the verified setting information S of the image forming devices 12 is downloaded from the setting management server 54 or is directly imported by the vendor and reflected onto the real devices 12, which allows the image forming devices 12 to be immediately operational.
However, a setting conflict may occur between the simulator environment 50 and the actual image forming devices 12, and a malfunction may occur if the settings of only one side are adopted. For example, a machine may be shipped from the factory with settings that are adjusted from the initial settings. As above, in the case where a machine has settings different from the initial settings before the initial installation, if the settings configured on the basis of the initial settings in the simulator environment 50, which is different from the image forming device 12 to be actually installed, are reflected onto the actual to-be-installed machine which is to be initialized, this reflection becomes, for example, one that disregards the settings changed upon shipment from the factory, and an inconvenience may arise.
Specifically, the actual image forming devices 12 are adjusted at the assembly factory, and setting values that reflect the adjustment result are configured, while the characteristic values of sensors are configured. In the meantime, for settings configured by a vendor of the image forming devices 12 in the simulator environment 50, default values are applied, instead of changing the configuration of setting values adjusted at the assembly factory or the sensor characteristics. Then, if the setting information configured in the simulator environment 50 is reflected onto the actual image forming devices 12, the setting values configured at the factory are overwritten with the default values, and an inconvenience arises. For example, as illustrated in
Accordingly, in the image forming system 10 according to the present exemplary embodiment, a process is performed including: holding, in a predetermined region, specific setting information, which is setting information to be reflected onto the image forming device 12 to be installed and which has been specified in an environment different from the image forming device 12 to be actually set up; and, in reflecting the specific setting information onto the image forming device 12, in the case where it is determined that a conflict occurs between the specific setting information held in the predetermined region and setting information preconfigured on the image forming device 12, notifying a predetermined notification destination, receiving a command to resolve the conflict, and reflecting the conflict-resolved setting information onto the image forming device 12. Note that an example of the different environment corresponds to the simulator environment 50 (see
Next, a functional configuration for performing the above-described processing in the image forming system 10 according to the present exemplary embodiment will be described.
The image forming system 10 according to the present exemplary embodiment includes the functions of the simulator environment 50 as a reproducing environment, the setting management server 54, a setting changing system 52, a default management server 56, and the real device 12. Note that the simulator environment 50, the setting management server 54, the setting changing system 52, and the default management server 56 may be functions provided by the single cloud server 14; alternatively, at least one of the functions may be provided by another server, or each of the functions may be provided by a different server. In the present exemplary embodiment, it is described that the simulator environment 50, the setting management server 54, and the default management server 56 are functions provided by the cloud server 14, and the setting changing system 52 is a function provided by the local server (MPS) 11.
The simulator environment 50 has the functions of an environment controller 58 and the virtual device 60, and the environment controller 58 creates the virtual device 60 virtually reproducing the image forming device 12 as a virtual environment different from the image forming device 12. The virtual device 60 created by the environment controller 58 performs processing to verify the customer-specific settings at the delivery destination of the image forming device 12 and to register the verified setting information into the setting management server 54.
The environment controller 58 has the functions of a communication I/F unit 61, a setting obtaining unit 62, and a virtual device creating unit 63.
The communication I/F unit 61 communicates with the default management server 56 to transmit and receive various types of data such as default setting data.
The setting obtaining unit 62 obtains the default setting data of the image forming device 12, which is to be simulated, from the default management server 56 via the communication I/F unit 61.
The virtual device creating unit 63 creates the virtual device 60, which is the virtual image forming device 12 to which the default setting data obtained by the setting obtaining unit 62 is applied.
The virtual device 60 has the functions of a user interface (UI) 64, a communication I/F unit 65, a conflict resolving unit 66, a setting controller 67, a setting data section 68, and an update data section 69.
The UI 64 displays setting information when verifying the settings of the virtual device 60, receives setting values, and so on.
The communication I/F unit 65 communicates with the setting changing system 52 to transmit and receive various types of data such as setting information.
On receipt of a notification of update success from the setting management server 54, the conflict resolving unit 66 empties the update data section 69, changes the setting data based on the obtained data, and stores the changed setting content in the setting data section 68.
The setting controller 67 controls the operation of the virtual device 60 in accordance with the setting values received by the UI 64. For example, in the case where the settings are changed, the setting controller 67 stores the changed setting content in the setting data section 68, and also adds to the update data section 69 the change content to be transmitted to the setting management server 54.
The setting data section 68 is a region for storing the setting values received by the UI 64, and the update data section 69 is a region for storing the updated setting values and so on.
The setting management server 54 has the functions of a communication I/F unit 70, a setting data update controller 71, an update pending data section 72 as an example of a predetermined region, a setting data section 73, a conflict determining unit 74, a conflict management unit 75, a conflict key section 76, and a conflict data section 77.
The communication I/F unit 70 communicates with the virtual device 60, the setting changing system 52, and the virtual device 12 to transmit and receive various types of data.
On receipt of setting information, the setting data update controller 71 controls the storage to the update pending data section 72 and the storage to the setting data section 73 in accordance with the transmission source of the setting information. For example, on receipt of setting information from the real device 12, the setting information is stored in the setting data section 73. In contrast, on receipt of setting information from the simulator environment 50 or the setting changing system 52, the setting information is stored in the update pending data section 72 instead of being stored in the setting data section 73, and, after the end of a conflict determination, the setting information is stored in the setting data section 73.
The update pending data section 72 is a region for storing change content of setting information, transmitted from the simulator environment 50 or the setting changing system 52, and the setting data section 73 is a region for storing setting information.
The conflict determining unit 74 determines whether a conflict occurs between setting information received from the real device 12 and setting information received from the simulator environment 50 or the setting changing system 52 by determining whether these items of setting information are inconsistent.
In the case where it is determined by the conflict determining unit 74 that a conflict is occurring, the conflict management unit 75 creates a conflict key for identifying the conflict, stores the conflict key in the conflict key section 76, and stores the conflict data in the conflict data section 77.
The conflict key section 76 is a storage region for storing a conflict key created by the conflict management unit 75, and the conflict data section 77 is a storage region for storing conflict data.
The setting changing system 52 has the function of a communication I/F unit 78 and a conflict resolving unit 79.
The communication I/F unit 78 communicates with the simulator environment 50, the setting management server 54, and the real device 12 to transmit and receive various types of data.
In the case of configuring the settings of multiple devices, if a similar conflict occurs, the conflict resolving unit 79 stores the result of selecting setting information configured first as specific setting information, and, if a similar conflict occurs in another device, set up this other device in accordance with rules set first.
The default management server 56 has the functions of a communication I/F unit 80, a setting data management unit 81, and a default setting data section 82.
The communication I/F unit 80 communicates with the simulator environment 50 to transmit and receive various types of data such as default setting data.
In response to a request from the simulator environment 50, the setting data management unit 81 reads the default setting data of a corresponding model from the default setting data section 82, and transmits the default setting data to the simulator environment 50.
The default setting data section 82 is a storage region for storing default setting data which is determined in advance for each model.
The real device 12 has the functionality that is the same as or similar to the virtual device 60 in the simulator environment 50. That is, the real device 12 has the functions of the UI 64, the communication I/F unit 65, the conflict resolving unit 66, the setting controller 67, the setting data section 68, and the update data section 69. Each function is the same as or similar to that of the virtual device 60 in the simulator environment 50, and a description thereof is omitted.
That is, with each function described above, in the image forming system 10 according to the present exemplary embodiment, a process is performed including: holding setting information specified in the simulator environment 50 in the update pending data section 72; and, in reflecting the setting information onto the real device 12, in the case where it is determined that a conflict occurs between the setting information held in the update pending data section 72 and setting information preconfigured on the image forming device 12, notifying a predetermined notification destination, receiving a command to resolve the conflict, and reflecting the conflict-resolved setting information onto the real device 12.
Specifically, in the image forming system 10 according to the present exemplary embodiment, each part performs processing in processes 1 to 6 below. The details of processes 1 to 6 will be described later.
The virtual device 60 and the real device 12 perform a process of receiving a setting change (process 1) and a process of synchronizing with the setting management server 54 (process 2).
The setting management server 54 performs a process of receiving a data update notification (process 3), a process of receiving a data obtaining request (process 4), and a process of determining a data conflict (process 5).
In addition, the setting data update source (virtual device 60, real device 12, and setting changing system 52) performs a process of receiving a conflict notification (process 6). The chronological flow in the major cases is as follows.
In the case where there is no update data, the flow is as follows: process 2 (request the setting management server 54 to obtain update pending data)→process 4 (respond to the device with the update pending data)→process 2 (end). Hereinafter, this is abbreviated as “obtain the update pending data”.
In the case where there is no update data and there is a conflict, the flow is as follows: process 2→process 4 (respond to the device that the obtaining of data failed due to a conflict)→process 2 (the device enters a sync request waiting state)→process 6 (transmit a conflict-resolved data update notification to the setting management server 54)→process 3 (the server receives the data update notification)→“obtain the update pending data”. Note that “obtain the update pending data” is unnecessary when process 6 is performed by the real device 12.
In the case where there is update data and there is no conflict, the flow is as follows: process 1→process 2 (transmit a data update notification to the setting management server 54)→process 3 (receive the data update notification)→process 5 (no conflict)→process 3 (respond that the update is successful)→“obtain the update pending data”.
In the case where there is update data and there is a conflict, the flow is as follows: the flow process 1→process 2→process 3 is the same as the flow when there is no conflict; process 1→process 2→process 3→process 5 (there is a conflict)→process 3 (respond that the update failed due to a conflict)→process 2 (empty the update data, and enter a sync request waiting state)→process 6→“obtain the update pending data”. Note that “obtain the update pending data” is unnecessary when process 6 is performed by the real device 12.
Next, the flow of the specific processing in processes 1 to 6 described above, performed by each part of the image forming system 10 according to the present exemplary embodiment, will be described.
First, F the process of receiving a setting change, which is process 1 described above, will be described.
In step 100, the virtual device 60 receives a setting change request, and moves to step 102. That is, the UI 64 receives a setting change request.
In step 102, the virtual device 60 determines whether the sync setting is valid and whether the change is independent of sync processing. In the case where the determination is affirmative, the virtual device 60 moves to step 104, and, in the case where the determination is negative, the virtual device 60 moves to step 106. Note that a change that depends on sync processing is a process of reflecting data of the setting management server 54, and a process of reflecting a conflict resolution onto values selected by the device.
In step 104, the virtual device 60 writes the requested setting to the update data section 69 and moves to step 106.
In step 106, the virtual device 60 writes the requested setting to the setting data section 68 and ends the series of processes.
Next, the process of synchronizing with the setting management server 54, which is process 2 descried above, will be described.
In step 200, the virtual device 60 receives a request to synchronize with the setting management server 54, and moves to step 202.
In step 202, the virtual device 60 determines whether there is update data. That is, the virtual device 60 determines whether update data is stored in the update data section 69. In the case where the determination is negative, the virtual device 60 moves to step 204, and, in the case where the determination is affirmative, the virtual device 60 moves to step 210.
In step 204, the virtual device 60 obtains update pending data of the setting management server 54, and moves to step 206.
In step 206, the virtual device 60 determines whether the obtaining of update pending data has been successful. In the case where the determination is affirmative, the virtual device 60 moves to step 208, and, in the case where the determination is negative, the virtual device 60 returns to step 200, and repeats the process described above.
In step 208, the virtual device 60 changes the setting data based on the obtained data, and ends the series of processes.
In contrast, in step 210, the virtual device 60 transmits a data update request to the setting management server 54, and moves to step 212.
In step 212, the virtual device 60 determines whether the update result has been received from the setting management server 54. The virtual device 60 waits until the determination is affirmative, and then moves to step 214.
In step 214, the virtual device 60 determines whether the update has been successful. In the case where the determination is affirmative, the virtual device 60 moves to step 216, and, in the case where the determination is negative, the virtual device 60 moves to step 218.
In step 216, the virtual device 60 empties the update data section 69, and moves to step 204 described above.
In contrast, in step 218, the virtual device 60 determines whether the result is a failure due to a conflict. In the case where the determination is negative, the virtual device 60 returns to step 200 and repeats the process described above, and, in the case where the determination is affirmative, the virtual device 60 moves to step 220.
In step 220, the virtual device 60 empties the update data section 69, returns to step 200, and repeats the process described above.
Next, the process of receiving a data update notification, which is process 3, will be described.
In step 300, the setting management server 54 receives an update data notification, and moves to step 302. Specifically, the setting data update controller 71 receives an update data notification from the virtual device 60, the real device 12, or the setting changing system 52. As an update data notification, for example, {“A”: 1} is received as a notification indicating that setting A has been updated to “1”. Note that, in the case of Hypertext Transfer Protocol (HTTP), for example, information on the requester of an update data notification is obtained from meta data such as the user agent, IP address, or the like written in the header.
In step 302, the setting management server 54 determines whether there is a conflict with update pending data. As the determination, the setting data update controller 71 determines whether update pending data stored in the update pending data section 72 is inconsistent with setting data stored in the setting data section 73. In the case where the determination is affirmative, the setting management server 54 moves to step 304, and, in the case where the determination is negative, the setting management server 54 moves to step 312.
In step 304, the setting management server 54 determines whether there is an update notification that matches a conflict key managed by the setting management server 54. In the case where there is no match with the conflict key and the determination is negative, the setting management server 54 moves to step 306, and, in the case where the determination is affirmative, the setting management server 54 moves to step 322.
In step 306, the setting management server 54 writes the information of the update pending data and the current information in the conflict data section 77, and moves to step 308.
In step 308, the setting management server 54 transmits a conflict notification to other requesters of conflict data and to a registered notification destination, and moves to step 310.
In step 310, the setting management server 54 responds with “update failed due to the occurrence of a conflict” and the conflict data, and ends the series of processes.
In contrast, when the determination in step 302 is negative and the setting management server 54 moves to step 312, in step 312, the setting management server 54 determines whether the notification is a notification from the real device 12. In the case where the determination is negative, the setting management server 54 moves to step 314, and, in the case where the determination is affirmative, the setting management server 54 moves to step 316.
In step 314, the setting management server 54 writes the setting data and the update requester information to the update pending data section 72, and moves to step 320.
In step 316, the setting management server 54 writes the received update data to the setting data section 73, and moves to step 318.
In step 318, the setting management server 54 deletes the read-only data in the update pending data section 72, and moves to step 320. Note that read-only data is not a setting that can be changed later as a setting item, but rather a setting that dynamically changes depending on the state of the real device 12, such as whether a hard disk drive is connected.
In step 320, the setting management server 54 responds with “update is successful”, and ends the series of processes.
In contrast, when the determination in step 304 is affirmative and the setting management server 54 moves to step 322, in step 322, the setting management server 54 deletes the conflict key of the device, which is held by the conflict management unit 75, and moves to step 312 described above. Along with the deletion of the conflict key, the conflict data corresponding to the conflict key is also deleted.
Next, the process of receiving a data obtaining request, which is process 4, will be described.
In step 400, the setting management server 54 receives a data obtaining notification, and moves to step 402.
In step 402, the setting management server 54 determines whether there is a conflict key for the device. In the case where the determination is affirmative, the setting management server 54 moves to step 404, and, in the case where there is no conflict key and the determination is negative, the setting management server 54 moves to step 406.
In step 404, the setting management server 54 responds with a data obtaining failure due to a conflict and content similar to a conflict notification, and ends the series of processes.
In contrast, in step 406, the setting management server 54 responds with a data obtaining success and update pending data, and moves to step 408.
In step 408, the setting management server 54 determines whether the notification is a notification from the real device 12. In the case where the determination is negative, the setting management server 54 ends the series of processes, and, in the case where the determination is affirmative, the setting management server 54 moves to step 410.
In step 410, the setting management server 54 reflects the update pending data onto the setting data, and ends the series of processes.
Next, the process of determining a data conflict, which is process 5, will be described.
In step 500, the setting management server 54 determines whether the value of update data and the value of update pending data are different. In the case where update data and update pending data are the same and the determination is negative, the setting management server 54 moves to step 502, and, in the case where the determination is affirmative, the setting management server 54 moves to step 510.
In step 502, the setting management server 54 determines whether the notification source is the real device 12, the update pending data includes a read-only setting, and the update data does not include the same read-only setting. In the case where the determination is affirmative, the setting management server 54 moves to step 504, and, in the case where the determination is negative, the setting management server 54 moves to step 506.
In step 504, the setting management server 54 determines that there is no conflict, and ends the series of processes.
In contrast, in step 506, the setting management server 54 determines whether the real device priority of the read-only setting is turned off. In the case where the determination is negative, the setting management server 54 moves to step 504 described above, and, in the case where the determination is affirmative, the setting management server 54 moves to step 508.
In step 508, the setting management server 54 determines that there is a conflict, and ends the series of processes. In step S510, the setting management server 54 determines whether the notification sources are different. In the case where the determination is affirmative, the setting management unit 54 moves to step 508, and, in the case where the determination is negative, the setting management unit 54 moves to step 502.
Next, the process of receiving a conflict notification, which is process 6, will be described.
In step 600, the virtual device 60 receives a conflict occurrence notification, and moves to step 602. For example, the virtual device 60 receives a conflict notification illustrated in
In step 602, the virtual device 60 displays information of each setting change requester and the change content, and moves to step 604. For example, as illustrated in
In step 604, the virtual device 60 determines whether the virtual device 60 has received the result of selecting a to-be-reflected setting. The virtual device 60 waits until the determination is affirmative, and then moves to step 606. For example, the virtual device 60 waits until a selection is made and “confirm” is selected on the selection screen 84 in
In step 606, the virtual device 60 outputs a data update notification including a conflict key included in the conflict occurrence notification, and ends the series of processes. For example, the virtual device 60 outputs an update notification including the conflict key illustrated in
Here, the above-described processing performed by the image forming system 10 according to the present exemplary embodiment will be described using specific examples.
First, the case in which there is no setting conflict will be described with reference to
In the case where there is no setting conflict, the flow from the assembly at the factory to the installation of the real device 12 is performed as below.
Next, the case in which there is a setting conflict will be described with reference to
In the case where there is a setting conflict, the flow from the assembly at the factory to the installation of the real device 12 is performed as below.
The real device 12 performs the batch setting again, receives setting A: 2, setting B: valid, and setting Z: MPS, and reflects them onto the setting data ([10-1]); and the setting management server 54 reflects A: 2, B: valid, and Z: MPS onto the setting data, and empties the update pending data section 72 ([10-2]).
Next, the case in which there is a setting conflict and the settings of multiple devices are to be configured will be described with reference to
In the case where there is a setting conflict and the settings of multiple devices are to be configured, the flow from the assembly at the factory to the installation of the real device 12 is performed as below.
The MPS 11 records, into the conflict resolving unit 79 that, for settings A, B, and Z, the setting data from the virtual device 60 has been selected.
The vendor performs the batch setting on the real device a again, and reflects setting A: 2, setting B: valid, and setting Z: MPS onto the setting data ([11-1]); and the setting management server 54 reflects A: 2, B: valid, and Z: MPS onto the setting data section 73, and empties the update pending data section 72 ([11-2]).
The vendor applies the selection content recorded in on receipt of a conflict notification by the MPS 11 to other machines as well.
The vendor installs the real device B.
When the vendor performs the batch setting on the real device B, the vendor tries to register setting A into the setting management server 54, and a conflict occurs.
The setting management server 54 notifies the real devices 12, the simulator environment 50, and the MPS 11 of a conflict.
On receipt of a conflict notification, the MPS 11 uses the selection data recorded in to create update data including a conflict key, and notifies the setting management server 54 thereof.
The same operation as is performed on the real device B, and the batch setting is completed.
Next, the case in which there is a read-only setting conflict will be described with reference to
In the case where there is a read-only setting conflict, the flow from the assembly at the factory to the installation of the real device 12 is performed as below.
In the above exemplary embodiment, the simulator environment 50 is described using an example in which a virtual environment on the cloud is applied, but this is not the only possible example. For example, a real device may be prepared at a sales company and the real device may be applied as the simulator environment 50.
In the above exemplary embodiment, the image forming device 12 is described as an example of a machine to be installed, but the image forming device 12 is not the only possible example of the machine. For example, other various machines such as image processing devices and image reading devices may be applied.
In the embodiments above, the term “processor” refers to hardware in a broad sense. Examples of the processor include general processors (e.g., CPU: Central Processing Unit) and dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, and programmable logic device).
In the embodiments above, the term “processor” is broad enough to encompass one processor or plural processors in collaboration which are located physically apart from each other but may work cooperatively. The order of operations of the processor is not limited to one described in the embodiments above, and may be changed.
In addition, processing performed by each part of the image forming system 10 according to the above exemplary embodiment may be processing performed by software, processing performed by hardware, or processing performed by a combination of both. Moreover, processing performed by each part of the image forming system 10 may be stored in a storage medium as a program and distributed.
Furthermore, the present disclosure is not limited to the above, and, in addition to the above, various modifications can be implemented within a range that does not deviate from the spirit thereof.
The foregoing description of the exemplary embodiments of the present disclosure has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. Obviously, many modifications and variations will be apparent to practitioners skilled in the art. The embodiments were chosen and described in order to best explain the principles of the disclosure and its practical applications, thereby enabling others skilled in the art to understand the disclosure for various embodiments and with the various modifications as are suited to the particular use contemplated. It is intended that the scope of the disclosure be defined by the following claims and their equivalents.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2023-043089 | Mar 2023 | JP | national |
