JP7476541B2 - Information processing system, control device, peripheral device control method, and peripheral device control program - Google Patents

Description

This invention relates to an information processing system, a control device, a peripheral device control method, and a peripheral device control program, and in particular to an information processing system including a plurality of control devices, a control device included in the information processing system, a peripheral device control method executed in the information processing system, and a peripheral device control program that causes a computer to execute the peripheral device control method.

A multifunction peripheral is known that includes a server and an image forming device connected to the server via an internal network that is separate from the external network to which the server is connected. In a system in which multiple multifunction peripherals are connected to one another via an external network, a technique is known for identifying one image forming device from one server in a system in which multiple multifunction peripherals are connected.

For example, Japanese Patent Application Publication No. 2011-138277 discloses a technique in which, in order to distribute requests for print data from user devices in multiple local areas with restricted access to printing devices in the multiple local areas, a request management server accepts requests for print data from client devices located at bases with restricted external access, identifies a print server located at the base to which the user device belongs as a device that will print the print data, and instructs the identified print server to obtain the print data via the client device that made the request for print data. In the technique described in Japanese Patent Application Publication No. 2011-138277, the relationship between the user device and the print server is specified in advance in the request management server.

However, there are cases where the network addresses assigned to multiple image forming devices by the internal network are fixed to the same value, in which case the image forming device cannot be identified by the network address assigned by the internal network.

For this reason, for example, when a user operates a multifunction device to instruct printing, printing may occur on a different multifunction device. As such, in an information processing system that includes multiple multifunction devices, there is a problem in that it is not possible to identify the appropriate device from among the multiple image forming devices.

JP 2011-138277 A

This invention has been made to solve the above-mentioned problems, and one of the objects of this invention is to provide an information processing system that is capable of identifying peripheral devices in an information processing system that includes multiple control devices.

Another object of the present invention is to provide a control device capable of identifying peripheral devices in an information processing system composed of multiple control devices.

Another object of the present invention is to provide a peripheral device control method capable of identifying peripheral devices in an information processing system composed of multiple control devices.

Yet another object of the present invention is to provide a peripheral device control program capable of identifying peripheral devices in an information processing system composed of multiple control devices.

The present invention has been made to solve the above-mentioned problems, and according to one aspect of the present invention, an information processing system is an information processing system including a plurality of control devices, at least one of which is equipped with a processing control unit that executes processing to control one or more processing devices to which the same fixed IP address is assigned , and each of the plurality of control devices is equipped with a reception unit that accepts instructions input from the outside, and each of the one or more control devices connected to one or more processing devices among the plurality of control devices is equipped with an equipment communication unit that communicates with a single processing device connected to the control device, and the processing control unit transmits a processing result obtained by executing processing in accordance with an instruction accepted by one of the plurality of reception units respectively equipped in the plurality of control devices to the equipment communication unit among the one or more equipment communication units that is associated with the reception unit that accepted the instruction.

According to this aspect, when a command is received by any of the multiple control devices, the processing result processed according to the command is transmitted to the device communication unit associated with the reception unit that received the command. Therefore, if a single processing device is connected to the control device that received the command, the processing result processed based on the command can be transmitted to the processing device connected to the control device that received the command. As a result, it is possible to provide an information processing system that can identify peripheral devices in an information processing system including multiple control devices.

Preferably, the processing control unit transmits the processing result to the device communication unit associated with the reception unit that received the command, and then outputs a response received from the processing device with which the device communication unit to which the processing result was transmitted communicates to the reception unit that received the command.

According to this aspect, the control device that receives the command outputs the response of the processing device, so the response received from the processing device can be notified to the user who issued the command.

According to another aspect of the present invention, an information processing system including a plurality of control devices, at least one of which is provided with a processing control unit that executes processing to control one or more processing devices, and each of the plurality of control devices is provided with a reception unit that receives commands input from outside, and each of the one or more control devices connected to any of the one or more processing devices among the plurality of control devices is provided with an equipment communication unit that communicates with the processing device connected to the control device, and a registration unit that registers registration information that associates the equipment communication unit provided in each of the one or more control devices connected to any of the one or more processing devices among the plurality of control devices with the control device, and the processing control unit further includes, wherein the reception unit adds identification information to the command input from outside for identifying the control device provided with the reception unit, and when a command is input from any of a plurality of reception units provided respectively in the plurality of control devices, the processing control unit transmits a processing result obtained by executing processing in accordance with the command to the equipment communication unit provided in the control device identified by the identification information added to the command.

According to this aspect, identification information for identifying the control device is added to the command input from the outside, and the processing result is transmitted to the device communication unit included in the control device identified by the identification information added to the command. Therefore, the processing result processed based on the command can be transmitted to the device communication unit associated with the reception unit that received the command.

Preferably, any one of the multiple control devices further includes an alternative device registration unit that registers alternative registration information that associates a control device that is not connected to any of the one or more processing devices among the multiple control devices with any one of the one or more control devices connected to any of the one or more processing devices, and if a control device identified by the identification information added to a command input from any one of the multiple reception units is not registered, the processing control unit transmits a processing result to an equipment communication unit included in the control device associated by the alternative registration information with the control device identified by the identification information added to the command input from any one of the multiple reception units.

In accordance with this aspect, a command received from the outside by a control device to which no processing device is connected is transmitted to a processing device connected to another control device associated with that control device. Therefore, by inputting a command to one of the multiple control devices, a user can control a processing device that is predetermined for the control device to which the command was input.

Preferably, each of the multiple control devices further includes a component management unit that inputs and outputs data via the virtual network and generates a part of the multiple components that make up the virtual system, and the multiple components include a processing control unit, a reception unit, a registration unit, and a device communication unit.

In accordance with this aspect, it is possible to provide an information processing system capable of identifying peripheral devices when a virtual system is configured with multiple control devices.

Preferably, a reception unit provided in each of one or more control devices connected to one or more processing devices receives a response received by the control device from the processing device.

In accordance with this aspect, the results of controlling the processing device can be notified to the user.

Preferably, the reception unit receives commands that the control device receives from the outside.

In accordance with this aspect, if a processing device is connected to the control device that has received the command, the processing results obtained by the control device in accordance with the command received from the outside can be transmitted to the processing device connected to the control device that has received the command.

Preferably, the reception unit receives commands via an external network to which multiple control devices are connected.

In accordance with this aspect, if a processing device is connected to the control device that has received the command, the processing results obtained by the control device in accordance with the command received via the external network can be transmitted to the processing device connected to the control device that has received the command.

Preferably, the reception unit receives commands input by a user to a user interface.

In accordance with this aspect, if a processing device is connected to the control device that receives the command, the processing results obtained according to the command input by the user to the control device can be transmitted to the processing device connected to the control device operated by the user.

Preferably, the processing device includes an image forming device that forms an image.

In accordance with this aspect, when a command is input to one of the multiple control devices that make up the information processing system, if an image forming device is connected to the control device that received the command, the image forming device can be made to form an image in accordance with the command.

According to another aspect of the present invention, the control device is any one of a plurality of control devices included in an information processing system, and when the control device is set as a predetermined responsible device among the plurality of control devices, the control device comprises a processing control unit that executes processing to control one or more processing devices assigned the same fixed IP address , a reception unit that accepts instructions input from the outside, and when the control device is connected to any one of the one or more processing devices, an equipment communication unit that communicates with a single processing device connected to the control device, and the processing control unit transmits a processing result obtained by executing processing in accordance with an instruction accepted by any one of a plurality of reception units respectively equipped in the plurality of control devices to an equipment communication unit associated with the reception unit that accepted the instruction, among one or more equipment communication units respectively equipped in the one or more control devices connected to any one of the one or more processing devices among the plurality of control devices.

In accordance with this aspect, it is possible to provide a control device capable of identifying peripheral devices in an information processing system made up of multiple control devices.

Preferably, the processing control unit transmits the processing result to the device communication unit associated with the reception unit that received the command, and then outputs a response received from the processing device with which the device communication unit to which the processing result was transmitted communicates to the reception unit that received the command.

According to another aspect of the present invention, a device is any one of a plurality of control devices included in an information processing system, and when the device itself is set as a predetermined responsible device among the plurality of control devices, the device comprises a processing control unit that executes processing to control one or more processing devices, a reception unit that receives commands input from the outside, and when the device itself is connected to any one of the one or more processing devices, an equipment communication unit that communicates with the processing device connected to the device, and a registration unit that registers registration information that associates the equipment communication unit provided in each of the one or more control devices connected to any of the one or more processing devices among the plurality of control devices with the control device, wherein the reception unit adds identification information for identifying the control device provided with the reception unit to the command input from the outside, and when a command is input from any one of a plurality of reception units provided respectively in the plurality of control devices, the processing control unit transmits the processing result of the processing performed in accordance with the command to the equipment communication unit provided in the control device identified by the identification information added to the command.

Preferably, when the self-device is a predetermined registered device among the multiple control devices, the device further includes an alternative device registration unit that registers alternative registration information that associates a control device that is not connected to any of the one or more processing devices among the multiple control devices with any of the one or more control devices connected to any of the one or more processing devices, and when a control device identified by identification information added to a command input from any of the multiple reception units that each of the multiple control devices has is not registered, the processing control unit transmits a processing result to an equipment communication unit included in the control device associated by the alternative registration information with the control device identified by the identification information added to a command input from any of the multiple reception units.

Preferably, each of the multiple control devices further includes a component management unit that inputs and outputs data via the virtual network and generates a part of the multiple components that make up the virtual system, and the multiple components include a processing control unit, a reception unit, a registration unit, and a device communication unit.

According to yet another aspect of the present invention, a peripheral device control method is a peripheral device control method executed in an information processing system including a plurality of control devices, comprising: causing at least one of the plurality of control devices to execute a processing control step for controlling one or more processing devices to which the same fixed IP address is assigned ; causing each of the plurality of control devices to execute a reception step for receiving an instruction input from the outside; and causing each of the one or more control devices connected to any of the one or more processing devices among the plurality of control devices to execute an equipment communication step for communicating with a single processing device connected to the control device, and the processing control step includes a step of transmitting a processing result obtained by executing a processing in accordance with the instruction received by any of the plurality of control devices to a control device associated with the control device among the one or more control devices connected to any of the processing devices from which the instruction was received.

According to this aspect, it is possible to provide a peripheral device control method capable of identifying peripheral devices in an information processing system composed of multiple control devices.

Preferably, the processing control step includes a step of outputting a response received from a processing device connected to the control device to which the processing result was transmitted, after the processing result is transmitted to a control device associated with the control device to which the command was received, among one or more control devices connected to any of the processing devices, to the control device that received the command.

According to yet another aspect of the present invention, there is provided a peripheral device control method executed in an information processing system including a plurality of control devices, comprising: causing at least one of the plurality of control devices to execute a processing control step for executing a process for controlling one or more processing devices; causing each of the plurality of control devices to execute a reception step for receiving a command input from outside; causing each of the one or more control devices connected to any of the one or more processing devices among the plurality of control devices to execute an equipment communication step for communicating with the processing device connected to the control device; and causing one of the plurality of control devices to execute a registration step for registering each of the one or more control devices connected to any of the one or more processing devices among the plurality of control devices, the reception step including a step of adding identification information for identifying the control device that has received the command to the command input from outside; and the processing control step including a step of, when a command is input from any of the plurality of control devices, transmitting a processing result of processing performed in accordance with the command to the control device identified by the identification information added to the command if the control device identified by the identification information added to the command is registered.

Preferably, an alternative device registration step is executed by one of the multiple control devices to register alternative registration information that associates a control device that is not connected to any of the one or more processing devices among the multiple control devices with any of the one or more control devices connected to any of the one or more processing devices, and the processing control step includes a step of transmitting a processing result to a control device associated by the alternative registration information with the control device identified by the identification information added to the command input from any of the multiple control devices if the control device identified by the identification information added to the command is not registered.

Preferably, each of the multiple control devices further executes a component management step of inputting and outputting data via a virtual network and generating a part of the multiple components that make up the virtual system, and the multiple components execute one of a processing control step, a reception step, a registration step, and a device communication step.

According to yet another aspect of the present invention, a peripheral device control program is a peripheral device control program that causes multiple computers to execute a peripheral device control method, and causes at least one of the multiple computers to execute a processing control step of executing processing for controlling one or more processing devices assigned the same fixed IP address , causes each of the multiple computers to execute a reception step of accepting instructions input from the outside, and causes each of the one or more computers connected to any of the one or more processing devices among the multiple computers to execute an equipment communication step of communicating with a single processing device connected to the computer, and the processing control step includes a step of transmitting a processing result of the processing executed in accordance with the instruction accepted by any of the multiple computers to a computer associated with the computer from which the instruction was accepted among the one or more computers connected to any of the processing devices.

In accordance with this aspect, it is possible to provide a peripheral device control program capable of identifying peripheral devices in an information processing system made up of multiple control devices.

Preferably, the processing control step includes a step of causing the computer that received the command to output a response received from a processing device connected to the computer to which the processing result was sent after the processing result is sent to a computer associated with the computer to which the command was received among one or more computers connected to any one of the processing devices.

According to yet another aspect of the present invention, a peripheral device control program for causing a plurality of computers to execute a peripheral device control method includes causing at least one of the plurality of computers to execute a processing control step for executing processing for controlling one or more processing devices, causing each of the plurality of computers to execute a reception step for receiving a command input from outside, causing each of the one or more computers connected to any of the one or more processing devices among the plurality of computers to execute an equipment communication step for communicating with the processing device connected to the computer, and causing one of the plurality of computers to execute a registration step for registering each of the one or more computers connected to any of the one or more processing devices among the plurality of computers, the reception step including a step of adding identification information to the command input from outside for identifying the computer that received the command, and the processing control step including a step of, when a command is input from any of the plurality of computers, if the computer identified by the identification information added to the command is registered, transmitting a processing result of processing performed in accordance with the command to the computer identified by the identification information added to the command.

Preferably, an alternative device registration step is executed on one of the multiple computers to register alternative registration information that associates a computer that is not connected to any of the one or more processing devices among the multiple computers with any of the one or more computers connected to any of the one or more processing devices, and the processing control step includes a step of transmitting a processing result to a computer associated by the alternative registration information with the computer identified by the identification information added to the command input from any of the multiple computers if the computer identified by the identification information added to the command is not registered.

Preferably, each of the multiple computers further executes a component management step of inputting and outputting data via a virtual network and generating a part of the multiple components that make up the virtual system, and the multiple components execute any one of a processing control step, a reception step, a registration step, and a device communication step.

1 is a diagram showing an overall overview of an information processing system according to one embodiment of the present invention; FIG. 2 is a perspective view showing the appearance of a first composite device in the present embodiment. FIG. 2 is a block diagram showing an example of a hardware configuration of a first multifunction peripheral. FIG. 1 is a diagram for explaining an overview of a virtual system. FIG. 4 is a block diagram showing an example of detailed functions of a CPU included in a server of the first multifunction peripheral; FIG. 4 is a block diagram showing an example of detailed functions of a CPU included in a server of the second multifunction peripheral; FIG. 11 is a diagram illustrating an example of a data flow when a virtual system is started. 5 is a diagram showing an example of a data flow when a PC requests the first multifunction peripheral to execute printing; FIG. FIG. 2 is a diagram showing the flow of data in a virtual system. 6 is a diagram showing an example of a data flow when a print execution request is made from the operation panel to the first multifunction peripheral; FIG. FIG. 11 is a diagram illustrating an example of the flow of a reverse proxy process. FIG. 11 is a diagram illustrating an example of the flow of a device proxy process. FIG. 11 is a diagram illustrating an example of the flow of a UI proxy process. FIG. 11 is a diagram illustrating an example of the flow of a device control process. FIG. 13 is a diagram for explaining an overview of a virtual system in a modified example. FIG. 11 is a block diagram showing an example of functions of a CPU included in a server of a first multifunction peripheral according to a modified example. FIG. 13 is a diagram showing an example of a data flow when a virtual system is started up in the modified example. 5 is a diagram showing an example of a data flow when a PC requests the first multifunction peripheral to execute printing; FIG.

The following describes an embodiment of the present invention with reference to the drawings. In the following description, identical parts are given the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated.

Fig. 1 is a diagram showing an overall overview of an information processing system in one embodiment of the present invention. Referring to Fig. 1, the information processing system is composed of a first multifunction device 1, a second multifunction device 2, and a personal computer (hereinafter referred to as "PC") 400. The first multifunction device 1, the second multifunction device 2, and the PC 400 are connected by an external LAN 3, which is a local area network (hereinafter referred to as "LAN"), and can communicate with each other. Note that the first multifunction device 1, the second multifunction device 2, and the PC 400 may be connected by other networks such as the Internet, not limited to the external LAN 3. The first multifunction device 1 and the second multifunction device 2 have the same hardware configuration and functions, so the first multifunction device 1 will be used as an example for the explanation here unless otherwise specified.

Fig. 2 is a perspective view showing the external appearance of the first multifunction device in this embodiment. Referring to Fig. 1, the first multifunction device 1 includes an MFP (Multi Function Peripheral) 100, a server 200 arranged below the MFP 100, and an operation panel 300 arranged on the side of the MFP 100. The server 200 functions as a control device, and the MFP 100 functions as a processing device controlled by the server 200.

MFP 100 is an example of an image forming device, and includes an automatic document feeder 120, a document reading unit 130, an image forming unit 140, and a paper feed unit 150. Automatic document feeder 120 automatically transports multiple documents set on a document tray one by one to a document reading position of document reading unit 130, and ejects the documents from which the images formed on the documents have been read by document reading unit 130 onto a document ejection tray.

The document reading unit 130 includes a light source that irradiates light and a photoelectric conversion element that receives the light, and scans an image formed on a document placed on the reading surface. When a document is placed in the reading area, the light irradiated from the light source is reflected by the document, and the reflected light forms an image on the photoelectric conversion element. When the photoelectric conversion element receives the light reflected by the document, it generates image data by converting the received light into an electrical signal.

The paper feed unit 150 includes two paper feed trays for storing paper. The paper feed unit 150 transports paper stored in either of the two paper feed trays to the image forming unit 140. The image forming unit 140 forms images using a well-known electrophotographic method, and forms an image on paper transported by the paper feed unit 150 based on image data, and discharges the paper with the image formed onto the paper output tray 155.

Figure 3 is a block diagram showing an example of the hardware configuration of the first multifunction device. Referring to Figure 3, the MFP 100 and the server 200 are connected via an internal LAN 4.

The server 200 includes a main CPU 201, which is a central processing unit that controls the entire server 200, a ROM (Read Only Memory) 202 that stores programs to be executed by the main CPU 201, a RAM (Random Access Memory) 203 used as a working area for the main CPU 201, a hard disk drive (HDD) 204 that stores data in a non-volatile manner, an external LAN communication unit 205 that connects the main CPU 201 to an external LAN 3, an internal LAN communication unit 206 that connects the main CPU 201 to the MFP 100, an external storage device 209, a VRAM (Video RAM) 207, and a panel communication unit 208 that is connected to the operation panel 300. The main CPU 201, ROM 202, RAM 203, HDD 204, external LAN communication unit 205, internal LAN communication unit 206, VRAM 207, panel communication unit 208 and external storage device 209 are connected to a bus 221.

The ROM 202 stores the programs executed by the main CPU 201, or data necessary to execute the programs. The RAM 203 is used as a working area when the main CPU 201 executes the programs.

The external LAN communication unit 205 is an interface for connecting the main CPU 201 to the external LAN 3. Therefore, the main CPU 201 can communicate with the PC 400 and the second multifunction device 2 via the external LAN 3. Furthermore, when the external LAN 3 is connected to the Internet, the main CPU 201 can communicate with a computer connected to the Internet. The internal LAN communication unit 206 is an interface for connecting the main CPU 201 to the internal LAN 4. Therefore, the main CPU 201 can communicate with the MFP 100 via the internal LAN 4. The external LAN communication unit 205 and the internal LAN communication unit 206 each communicate using a communication protocol such as TCP (Transmission Control Protocol) or UDP (User Datagram Protocol).

The VRAM 207 stores screen images generated by the main CPU 201. The main CPU 201 generates screen images to be displayed on the operation panel 300 and stores them in the VRAM 207. The panel communication unit 208 is an interface for connecting the main CPU 201 to the operation panel 300. The panel communication unit 208 may be connected to the operation panel 300 by a USB (Universal Serial Bus) cable.

HDD204 is a large-capacity storage device and is controlled by main CPU201. Main CPU201 can read data stored in HDD204 and can also write data to HDD204.

The external storage device 209 is controlled by the main CPU 201, and is equipped with a CD (Compact Disk)-ROM 210 or a semiconductor memory. The main CPU 201 controls the external storage device 209 to read data stored in the CD-ROM 210 or the semiconductor memory, or to write data to the CD-ROM 210 or the semiconductor memory.

The MFP 100 includes a device CPU 111, which is a central processing unit that controls the entire MFP 100, a device LAN communication unit 112, a ROM 113, a RAM 114, a facsimile unit 115, a VRAM 116, an automatic document feeder 120, a document reading unit 130, an image forming unit 140, and a paper feed unit 150. The device CPU 111 is connected to the device LAN communication unit 112, the ROM 113, the RAM 114, the facsimile unit 115, the VRAM 116, the automatic document feeder 120, the document reading unit 130, the image forming unit 140, and the paper feed unit 150, and controls the entire MFP 100.

The ROM 113 stores the program executed by the device CPU 111, or data required to execute the program. The RAM 114 is used as a working area when the device CPU 111 executes the program. The RAM 114 also temporarily stores image data that is continuously sent from the document reading unit 130.

Facsimile unit 115 is connected to the public switched telephone network (PSTN) and transmits facsimile data to the PSTN or receives facsimile data from the PSTN. Facsimile unit 115 converts the received facsimile data into print data that can be printed by image forming unit 140 and outputs it to image forming unit 140. In this way, image forming unit 140 forms an image of the facsimile data received by facsimile unit 115 on paper. Facsimile unit 115 also converts image data output by document reading unit 130 after reading a document into facsimile data and transmits it to a facsimile device connected to the PSTN.

The device LAN communication unit 112 is an interface for connecting the device CPU 111 to the internal LAN 4. Therefore, the device CPU 111 can communicate with the server 200 via the internal LAN 4. The device LAN communication unit 112 communicates with the server 200 connected to the internal LAN 4 using a communication protocol such as TCP or FTP. The connection form of the internal LAN 4 can be either wired or wireless.

The VRAM 116 stores screen images generated by the device CPU 111. The device CPU 111 generates screen images to be displayed on the operation panel 300 and stores them in the VRAM 116.

The HDD 204 and external storage device 209 are set by the main CPU 201 to be shared with the MFP 100, and are set by the main CPU 201 to be accessible from the MFP 100. Therefore, the device CPU 111 can read data stored in the HDD 204 or the CD-ROM 210 attached to the external storage device 209, and can also write data to them.

In this embodiment, an example is described in which the device CPU 111 executes a program stored in ROM 113, but the device CPU 111 may read a program to be executed by the device CPU 111 from the HDD 204 or a CD-ROM 210 or the like mounted on the external storage device 209, and load the read program into RAM 114 for execution. Similarly, the main CPU 201 may read a program to be executed by the main CPU 201 from the HDD 204 or a CD-ROM 210 or the like mounted on the external storage device 209, and load the read program into RAM 203 for execution.

The recording medium for storing the programs executed by the device CPU 111 or the main CPU 201 is not limited to the CD-ROM 210, but may be a flexible disk, a cassette tape, an optical disk (MO (Magnetic Optical Disc)/MD (Mini Disc)/DVD (Digital Versatile Disc)), an IC card, an optical card, a mask ROM, an EPROM (Erasable Programmable ROM), or other semiconductor memory medium.

Furthermore, the device CPU 111 or the main CPU 201 may download a program from a computer connected to the external LAN 3 or the Internet and store it in the HDD 204, or the computer connected to the external LAN 3 or the Internet may write the program to the HDD 204. In this case, the device CPU 111 loads the program stored in the HDD 204 into the RAM 114 and executes it, and the main CPU 201 loads the program stored in the HDD 204 into the RAM 203 and executes it. The program here includes not only programs that can be directly executed by the device CPU 111 or the main CPU 201, but also source programs, compressed programs, encrypted programs, etc.

The operation panel 300 includes a switching unit 301, a display unit 303, and an operation unit 305. The switching unit 301 is connected to the display unit 303, VRAM 116, and VRAM 207. The switching unit 301 switches between VRAM 116 and VRAM 207 in accordance with a switching command input from the panel communication unit 208.

Display unit 303 displays an image stored in either VRAM 116 or VRAM 207, whichever is selected by switching unit 301. Display unit 303 is, for example, a liquid crystal display (LCD), and displays an instruction menu for the user, information about acquired image data, and the like. Note that instead of an LCD, for example, an organic electroluminescence (EL) display can be used as long as it is a device that displays images.

The operation unit 305 includes a touch panel 307 and a hard key unit 309. The touch panel 307 is of a capacitance type. Note that the touch panel 307 is not limited to a capacitance type, and other types such as a resistive film type, a surface acoustic wave type, an infrared type, and an electromagnetic induction type can be used. The hard key unit 309 includes a plurality of hard keys. The hard keys are, for example, contact switches.

The touch panel 307 is provided superimposed on the upper or lower surface of the display unit 303. Here, the size of the detection surface of the touch panel 307 is the same as the size of the display surface of the display unit 303. Therefore, the coordinate system of the display surface and the coordinate system of the detection surface are the same. The touch panel 307 detects, on the detection surface, the position at which the user points on the display surface of the display unit 303, and outputs position information indicating the coordinates of the detected position to the panel communication unit 208. Since the coordinate system of the display surface and the coordinate system of the detection surface are the same, the coordinates specified by the position information output by the touch panel 307 can be replaced with the coordinates of the display surface of the display unit 303. The hard key unit 309 includes a plurality of hard keys. The hard keys are, for example, contact switches.

Hereinafter, the components and functions of the second combination device 2 will be assigned the same reference numerals as those of the first combination device 1, with the letter "A" added after the reference numerals.

Figure 4 is a diagram for explaining an overview of the virtual system. The virtual system is composed of a first multifunction device 1 and a second multifunction device 2. The first multifunction device 1 includes a server 200, an MFP 100, and an operation panel 300, and the second multifunction device 2 includes a server 200A, an MFP 100A, and an operation panel 300A.

In the first multifunction device 1, the server 200 has an external LAN communication unit 205 connected to the external LAN 3 and an internal LAN communication unit 206 connected to the internal LAN 4. The MFP 100 is connected to the internal LAN 4. Therefore, the server 200 can communicate with the MFP 100 via the internal LAN 4. In the internal LAN 4, the network addresses assigned to the server 200 and the MFP 100 are predetermined fixed IP addresses. Also, in the second multifunction device 2, the server 200A has an external LAN communication unit 205A connected to the external LAN 3 and an internal LAN communication unit 206A connected to the internal LAN 4A. The MFP 100A is connected to the internal LAN 4A. Therefore, the server 200A can communicate with the MFP 100A via the internal LAN 4A. In the internal LAN 4A, the network addresses assigned to the server 200A and the MFP 100A are predetermined fixed IP addresses. In addition, the server 200 of the first multifunction device 1, the server 200A of the second multifunction device 2, and the PC 400 can communicate with each other via the external LAN 3.

Figure 5 is a block diagram showing an example of detailed functions of a CPU provided in the server of the first multifunction device. The functions shown in Figure 5 are functions that are realized by the main CPU 201 provided in the server 200 of the first multifunction device 1 as the main CPU 201 executes a peripheral device control program.

Figure 6 is a block diagram showing an example of detailed functions of a CPU provided in the server of the second multifunction device. The functions shown in Figure 6 are functions that are realized by the main CPU 201A provided in the server 200A of the second multifunction device 2 when the main CPU 201A executes a peripheral device control program.

With reference to Figures 4 to 6, the main CPU 201 of the server 200 includes a first cluster management unit 251 that functions as a component management unit, and the main CPU 201A of the server 200A includes a second cluster management unit 251A that functions as a component management unit. The first cluster management unit 251 functions as a component management unit that generates some of the components that make up a virtual system. Specifically, the first cluster management unit 251 generates a plurality of containers as some of the components that make up a virtual system in the main CPU 201 that becomes a node, in order to build a virtual system. The second cluster management unit 251A functions as a component management unit that generates some of the components that make up a virtual system. Specifically, the second cluster management unit 251A generates a plurality of containers as other parts of the components that make up a virtual system in the main CPU 201A that becomes a node, in order to build a virtual system. The first cluster management unit 251 is preliminarily designated as the master, and the second cluster management unit 251A is preliminarily designated as the slave, and the first cluster management unit 251 and the second cluster management unit 2511A communicate with each other, and multiple containers that make up a virtual system are generated in the main CPU 201 and the main CPU 201A. The virtual system is made up of multiple containers, and the multiple containers are connected by a virtual network. Therefore, each of the multiple containers is assigned a virtual address as a network address assigned in the virtual network.

The first cluster management unit 251 generates in the main CPU 201 a first reverse proxy container 253 that functions as a reception unit, a first device proxy container 255 that functions as a device communication unit that communicates with the MFP 100, which is a processing device, and a first UI proxy container 257 that functions as a reception unit.

The first reverse proxy container 253 controls the external LAN communication unit 205 and the internal LAN communication unit 206. The first reverse proxy container 253 acts as a proxy for the external LAN communication unit 205 and the internal LAN communication unit 206, and functions as a network interface for other containers.

The first reverse proxy container 253 includes a first identification information addition unit 261. The first identification information addition unit 261 adds a node ID for identifying the server 200 to data received from the outside by the external LAN communication unit 205 or the internal LAN communication unit 206. The data received from the outside by the external LAN communication unit 205 includes an instruction to execute a print job received from a computer connected to the external LAN 3. The data received from the outside by the internal LAN communication unit 206 includes status information indicating the execution result of the job received from the MFP 100. The first identification information addition unit 261 acquires a node ID from the first cluster management unit 251. Specifically, the first identification information addition unit 261 adds a node ID to data received by the external LAN communication unit 205 from the PC 400 or the second multifunction device 2 via the external LAN 3. In addition, the first identification information adding unit 261 adds a node ID to data that the internal LAN communication unit 206 receives from the MFP 100 via the internal LAN 4.

The first reverse proxy container 253 outputs the data with the node ID added to another container. Specifically, the first reverse proxy container 253 determines the container to which the data is to be output based on the data received from outside.

The first device proxy container 255 acts as a proxy for the MFP 100 and functions as the MFP 100 with respect to other containers. The first device proxy container 255 includes a first device identification information acquisition unit 271, a first device registration unit 273, and a first device communication unit 275.

The first device communication unit 275 controls the internal LAN communication unit 206 and communicates with the MFP 100 connected via the internal LAN 4. The first device communication unit 275 transfers data input from other containers to the MFP 100. The first device communication unit 275 communicates with the MFP 100 using a network address assigned to the MFP 100 in the internal LAN 4. Here, the MFP 100 is assigned a predetermined fixed IP address as its network address in the internal LAN 4.

In response to the first device proxy container 255 starting up, the first device identification information acquisition unit 271 acquires the node ID of the server 200 from the first cluster management unit 251 and outputs the node ID to the first device registration unit 273.

When the first device proxy container 255 is started, the first device registration unit 273 registers registration information in the virtual system that associates the first device proxy container 255 with the server 200. Specifically, the first device registration unit 273 generates registration information including the node ID of the server 200 input from the first device identification information acquisition unit 271 and the virtual address assigned to the first device proxy container 255. The first device registration unit 273 stores the registration information in a registration DB. The registration DB may be stored in the HDD 204 of either the server 200 or the server 200A. Here, an example is described in which the registration DB is stored in the HDD 204 of the server 200 having the main CPU 201 in which the first cluster management unit 251 serving as the master is formed. The registration information may be only the node ID of the server 200. In this case, the server 200 can be identified from the registration information, and therefore the virtual address of the first device proxy container 255 generated in the server 200 can be identified.

The first UI proxy container 257 acts as a user interface for the other containers, acting as a proxy for the operation panel 300. The first UI proxy container 257 includes a first UI identification information acquisition unit 281, a first UI registration unit 283, and a first panel communication unit 285.

The first panel communication unit 285 communicates with the operation panel 300 via the panel communication unit 208. Specifically, the first panel communication unit 285 displays an image on the display unit 303 based on an instruction input from another container. The other container is, for example, a task that executes a Web application that defines a process for displaying an operation screen for operating the MFP 100 and a process for accepting an operation that the user inputs to the operation unit 305 according to the operation screen. The first panel communication unit 285 receives from the operation unit 305 an operation input by a user that is accepted by the operation panel 300. The first panel communication unit 285 outputs an instruction determined by the operation received from the operation panel 300 to another container. The first panel communication unit 285 determines a container to which the instruction is to be output based on an instruction determined by the operation. The instruction determined by the operation includes, for example, an instruction to execute a copy job. For example, the first panel communication unit 285 outputs an instruction determined by the operation received from the operation panel 300 to the device control container 259.

In response to the first UI proxy container 257 starting up, the first UI identification information acquisition unit 281 acquires the node ID of the server 200 from the first cluster management unit 251 and outputs the node ID to the first UI registration unit 283.

When the first UI proxy container 257 is started, the first UI registration unit 283 registers registration information that associates the first UI proxy container 257 with the server 200 in the virtual system. Specifically, the first UI registration unit 283 generates registration information including the node ID of the server 200 input from the first UI identification information acquisition unit 281 and the virtual address assigned to the first UI proxy container 257. The first UI registration unit 283 stores the registration information in a registration DB stored in the HDD 204.

The second cluster management unit 251A generates in the main CPU 201A a second reverse proxy container 253A that functions as a reception unit, a second device proxy container 255A that functions as a device communication unit that communicates with the processing device MFP 100A, a second UI proxy container 257A that functions as a reception unit, and a device control container 259.

The device control container 259 functions as a process control unit that executes processes for controlling the processing devices MFP 100, 100A. Specifically, the device control container 259 executes a predetermined process. Here, the device control container 259 executes a process for generating a print job to be executed by MFP 100 or MFP 100A. The device control container 259 is an example of an application container. At least one application container is generated in a virtual system. Here, an example is shown in which one device control container 259 is generated as an application container in the main CPU 201A of the server 200A provided in the second multifunction device 2 in the virtual system. The device control container 259 executes an application program for the main CPU 201 to control the MFP 100 or MFP 100A.

The second reverse proxy container 253A controls the external LAN communication unit 205A and the internal LAN communication unit 206A. The second reverse proxy container 253A acts as a proxy for the external LAN communication unit 205A and the internal LAN communication unit 206A, and functions as a network interface for other containers.

The second reverse proxy container 253A includes a second identification information addition unit 261A. The second identification information addition unit 261A adds a node ID for identifying the server 200A to data that the external LAN communication unit 205A or the internal LAN communication unit 206A receives from the outside. The second identification information addition unit 261A acquires the node ID from the second cluster management unit 251A. Specifically, the second identification information addition unit 261A adds a node ID to data that the external LAN communication unit 205A receives from the PC 400 or the first multifunction device 1 via the external LAN 3. The second identification information addition unit 261A also adds a node ID to data that the internal LAN communication unit 206A receives from the MFP 100A via the internal LAN 4A.

The second reverse proxy container 253A outputs the data with the node ID added to another container. Specifically, the second reverse proxy container 253A determines the container to which the data is to be output based on the data received from outside.

The second device proxy container 255A acts as a proxy for the MFP 100A and functions as the MFP 100A with respect to other containers. The second device proxy container 255A includes a second device identification information acquisition unit 271A, a second device registration unit 273A, and a second device communication unit 275A.

The second device communication unit 275A controls the internal LAN communication unit 206A and communicates with the MFP 100A connected via the internal LAN 4A. The second device communication unit 275A transfers data input from other containers to the MFP 100A. The second device communication unit 275A communicates with the MFP 100A using a network address assigned to the MFP 100A in the internal LAN 4A. Here, a predetermined fixed IP address is assigned to the MFP 100A as a network address in the internal LAN 4A. The internal LAN 4 and the internal LAN 4A use physically different LAN cables as a medium. Therefore, the fixed IP address assigned to the MFP 100 and the fixed IP address assigned to the MFP 100A may be the same.

In response to the second device proxy container 255A starting up, the second device identification information acquisition unit 271A acquires the node ID of the server 200A from the second cluster management unit 251A and outputs the node ID to the second device registration unit 273A.

When the second device proxy container 255A is started, the second device registration unit 273A registers registration information that associates the second device proxy container 255A with the server 200A in the virtual system. Specifically, the second device registration unit 273A generates registration information including the node ID of the server 200A input from the second device identification information acquisition unit 271A and the virtual address assigned to the second device proxy container 255A. The second device registration unit 273A stores the registration information in a registration DB stored in the HDD 294.

The second UI proxy container 257A acts as a user interface for the other containers, acting on behalf of the operation panel 300A. The second UI proxy container 257A includes a second UI identification information acquisition unit 281A, a second UI registration unit 283A, and a second panel communication unit 285A.

The second panel communication unit 285A communicates with the operation panel 300A via the panel communication unit 208A. Specifically, the second panel communication unit 285A displays an image on the display unit 303 based on an instruction input from another container. The other container is, for example, a task that executes a Web application that defines a process for displaying an operation screen for operating the MFP 100A and a process for accepting an operation that the user inputs to the operation unit 305A according to the operation screen. The second panel communication unit 285A receives from the operation unit 305A an operation input by a user that is accepted by the operation panel 300A. The second panel communication unit 285A outputs an instruction determined by the operation received from the operation panel 300A to the other container. The second panel communication unit 285A determines a container to which the instruction is to be output based on an instruction determined by the operation. The instruction determined by the operation includes, for example, an instruction to execute a copy job or a scan job. For example, the second panel communication unit 285A outputs a command determined by an operation received from the operation panel 300A to the device control container 259A.

In response to the second UI proxy container 257A starting up, the second UI identification information acquisition unit 281A acquires the node ID of the server 200A from the second cluster management unit 251A and outputs the node ID to the second UI registration unit 283A.

When the second UI proxy container 257A is started, the second UI registration unit 283A registers registration information that associates the second UI proxy container 257A with the server 200A in the virtual system. Specifically, the second UI registration unit 283A generates registration information including the node ID of the server 200A input from the second UI identification information acquisition unit 281A and the virtual address assigned to the second UI proxy container 257A. The second UI registration unit 283A stores the registration information in a registration DB stored in the HDD 204.

The device control container 259 determines the container to which data is to be output based on the node ID added to the data input from another container. Specifically, it searches the registration DB stored in the HDD 204 of the server 200 using the node ID, and determines the virtual address associated with the node ID from the registration information including the node ID. The device control container 259 outputs the data to the container to which the determined virtual address is assigned.

Figure 7 is a diagram showing an example of data flow when a virtual system is started. In Figure 7, the vertical direction indicates the passage of time, and the arrows indicate the flow of data. Note that Figure 7 shows a first cluster management unit 251 formed in the server 200 of the first composite device 1, a first device proxy container 255, and a device control container 259 formed in the first UI proxy container 257.

Referring to FIG. 7, when the virtual system is started, the first device proxy container 255 requests a node ID from the first cluster management unit 251. In response to the request, the first cluster management unit 251 returns the node ID of the server 200, and the first device proxy container 255 receives the node ID of the server 200. The first device proxy container 255 then generates registration information that associates the node ID of the server 200 with the virtual address assigned to the first device proxy container 255, and stores the registration information in a registration DB stored in the HDD 204.

When the virtual system is started, the first UI proxy container 257 requests a node ID from the first cluster management unit 251. In response to the request, the first cluster management unit 251 replies with the node ID of the server 200, and the first UI proxy container 257 receives the node ID of the server 200. The first UI proxy container 257 then generates registration information that associates the node ID of the server 200 with the virtual address assigned to the first UI proxy container 257, and stores the registration information in a registration DB stored in the HDD 204.

Figure 8 is a diagram showing an example of data flow when a PC requests the first multifunction device to execute printing. The vertical direction indicates the passage of time, and the arrows indicate the flow of data. Here, an example is explained in which a print execution request is sent from the PC 200 to the first multifunction device. Note that Figure 8 shows a first reverse proxy container 253 and a first device proxy container 255 formed on the server 200 of the first multifunction device 1, and a device control container 259 formed on the server 200A of the second multifunction device 2.

First, the data flow when the PC 400 causes the first multifunction device 1 to execute a print job will be described. This data flow is indicated by a bold line in FIG. 4. Referring to FIG. 8, when a print execution request is sent from the PC 400 to the first multifunction device 1, the first reverse proxy container 253 receives the print execution request. The first reverse proxy container 253 adds a node ID to the print execution request and outputs it to the device control container 259. The node ID that the first reverse proxy container 253 adds to the print execution request is the node ID of the server 200. The first reverse proxy container 253 may obtain the node ID from the first cluster management unit 251 at startup.

When a print execution request is input, the device control container 259 executes processing according to the print execution request. Specifically, the device control container 259 generates a print job for forming an image of the data determined by the print execution request. The device control container 259 also extracts the node ID added to the print execution request in order to determine the container that will be the output destination of the print job. In the virtual system, the first device proxy container 255 and the second device proxy container 255A are candidates for the container that will be the output destination of the print job. Therefore, the device control container 259 determines either the first device proxy container 255 or the second device proxy container 255A as the output destination of the print job.

The device control container 259 searches for a container using the node ID. Specifically, the device control container 259 searches the registration DB stored in the HDD 204, extracts registration information including the node ID, and determines the virtual address associated with the node ID based on the registration information. The registration DB contains registration information in which the first device proxy container 255 associates the node ID of the server 200 with the virtual address of the first device proxy container 255, and registration information in which the second device proxy container 255A associates the node ID of the server 200A with the virtual address of the second device proxy container 255A. Since the node ID added to the print execution request input from the first reverse proxy container 253 is the node ID of the server 200, the device control container 259 determines the virtual address of the first device proxy container 255.

Then, the device control container 259 outputs the print job to the first device proxy container 255 identified by the virtual address. The first device proxy container 255 transfers the print job to the MFP 100, and causes the MFP 100 to execute the print job.

The device control container 259 also notifies the PC 400 that sent the print execution request that the transmission of the print job is complete. When the print execution request is input, the device control container 259 obtains the virtual address of the first reverse proxy container 253 that output the print execution request, and after transmitting the print job, generates status information including a print status indicating the print state of the print job and stores it in the HDD 204. In this example, the status information includes the virtual address of the first reverse proxy container 253 that output the print execution request and the node ID of the server 200 on which the first device proxy container 255 that output the print job is generated. The device control container 259 obtains the node ID of the server 200 from the first device proxy container 255 that output the print job. Then, the device control container 259 transmits a print status indicating that the transmission of the print job is complete to the PC 400. Specifically, the device control container 259 outputs the print status to the first reverse proxy container 253, and the first reverse proxy container 253 transmits the print status to the PC 400. The status information may be stored in the HDD 204A of the server 200A on which the device control container 259 is generated.

Next, the flow of the print status indicating the result of the MFP 100 executing a print job will be described. This data flow is indicated by a thick dotted line in FIG. 4. The MFP 100 receives the print job, executes the print job, and starts printing. Then, if necessary, it returns a print status indicating the printing status to the server 200. The print status is received by the first reverse proxy container 253. The first reverse proxy container 253 adds the node ID of the server 200 to the print status, and outputs the print status to the device control container 259.

When the print status is input, the device control container 259 extracts the node ID added to the print status and extracts the status information including the node ID from the status information stored in the HDD 204. The device control container 259 determines the virtual address associated with the extracted node ID from the status information including the node ID. Since the status information including the node ID of the server 200 and the virtual address of the first reverse proxy container 253 is stored in the HDD 204 at the stage of generating the print job, the device control container 259 determines the virtual address of the first reverse proxy container 253. Then, the device control container 259 updates the print status of the status information and outputs the print status to the first reverse proxy container 253 specified by the virtual address of the first reverse proxy container 253. The first reverse proxy container 253 transmits the print status to the PC 400 that has sent the print execution request.

Next, we will explain an example in which a user operates the operation panel 300 of the first multifunction device 1 to cause the MFP 100 to execute a print job.

Figure 9 is a diagram showing the flow of data in the virtual system. The flow of data when the operation panel 300 causes the MFP 100 to execute a print job is shown by a thick solid line, and the flow of print status indicating the result of the MFP 100 executing the print job is shown by a thick dotted line.

Figure 10 is a diagram showing an example of data flow when a print execution request is made to the first multifunction device from the operation panel. The vertical direction indicates the passage of time, and the arrows indicate the data flow. Note that Figure 10 shows the first UI proxy container 257, first reverse proxy container 253, and first device proxy container 255 formed on the server 200 of the first multifunction device 1, and the device control container 259 realized on the server 200A of the second multifunction device 2.

First, when a user inputs an operation to generate a print job on the operation panel 300, the operation is accepted by the first UI proxy container 257. The first UI proxy container 257 adds the node ID of the server 200 to the accepted operation and outputs it to the device control container 259. The node ID that the first UI proxy container 257 adds to the operation is the node ID of the server 200 that the first UI proxy container 257 obtained from the first cluster management unit 251 at startup. The node ID that the first UI proxy container 257 adds to the operation is the node ID of the server 200.

When an operation is input, the device control container 259 executes processing according to the operation. Specifically, the device control container 259 generates a print job for forming an image of the data determined by the operation.

The device control container 259 extracts the node ID attached to the operation to determine the container that will be the output destination of the print job. In the virtual system, the first device proxy container 255 and the second device proxy container 255A are candidates for the container that will be the output destination of the print job. Therefore, the device control container 259 determines either the first device proxy container 255 or the second device proxy container 255A as the output destination of the print job.

The device control container 259 uses the node ID to search the registration DB stored in the HDD 204, extracts registration information including the node ID, and determines the virtual address associated with the node ID from the registration information. The registration DB contains registration information in which the first device proxy container 255 associates the node ID of the server 200 with the virtual address of the first device proxy container 255, and registration information in which the second device proxy container 255A associates the node ID of the server 200A with the virtual address of the second device proxy container 255A. Since the node ID added to the operation input from the first UI proxy container 257 is the node ID of the server 200, the device control container 259 determines the virtual address of the first device proxy container 255.

Then, the device control container 259 outputs the print job to the first device proxy container 255 identified by the virtual address, and displays on the operation panel 300, where operations are input, that the transmission of the print job has been completed. The first device proxy container 255 transfers the print job to the MFP 100.

When the operation is input, the device control container 259 obtains the virtual address of the first UI proxy container 257 that output the operation, and after sending the print job, generates status information including a print status indicating the print state of the print job and stores it in the HDD 204. In this example, the status information includes the virtual address of the first UI proxy container 257 that output the operation and the node ID of the server 200 on which the first device proxy container 255 that output the print job is generated. The device control container 259 obtains the node ID of the server 200 from the first device proxy container 255 that output the print job. Then, the device control container 259 outputs a print status indicating that the transmission of the print job has been completed to the first UI proxy container 257. The first UI proxy container 257 displays the print status on the operation panel 300. Specifically, the first UI proxy container 257 outputs a switching command to the switching unit 301 to switch to VRAN 116. Alternatively, an image of a screen showing the print status may be stored in VRAM 207, and a switching command to switch to VRAN 207 may be output to switching unit 301.

Next, the flow of the print status indicating the result of the MFP 100 executing a print job will be explained. The MFP 100 receives the print job, executes the print job, and starts printing. Then, if necessary, it returns a print status indicating the printing status to the server 200. The print status is received by the first reverse proxy container 253. The first reverse proxy container 253 adds the node ID of the server 200 to the print status, and outputs the print status to the device control container 259.

When the print status is input, the device control container 259 extracts the node ID added to the print status and extracts the status information including the node ID from the status information stored in the HDD 204. The device control container 259 determines a virtual address associated with the node ID from the status information including the node ID. Since the status information including the node ID of the server 200 and the virtual address of the first UI proxy container 257 is stored in the HDD 204 at the stage of generating the print job, the device control container 259 determines the virtual address of the first UI proxy container 257. Then, the device control container 259 updates the print status of the status information and outputs the print status to the first UI proxy container 257 specified by the virtual address of the first UI proxy container 257. The first UI proxy container 257 displays the print status on the operation panel 300. Specifically, the first UI proxy container 257 outputs a switching command to the switching unit 301 to switch to VRAN 116. Alternatively, an image of a screen showing the print status may be stored in VRAM 207, and a switching command to switch to VRAN 207 may be output to switching unit 301.

Figure 11 is a diagram showing an example of the flow of reverse proxy processing. The reverse proxy processing is a process executed by the main CPU 201 of the server 200 provided in the first multifunction device 1, as the main CPU 201 executes a peripheral device control program stored in the ROM 202, HDD 204, or CD-ROM 210. Specifically, the reverse proxy processing is a process executed by the first reverse proxy container 253 realized by the main CPU 201.

Referring to FIG. 11, the first reverse proxy container 253 implemented by the main CPU 201 determines whether data has been received (step S01). The external LAN communication unit 205 or the internal LAN communication unit 206 enters a standby state until data is received (NO in step S01), and if data has been received, the process proceeds to step S02.

In step S02, the transfer destination is determined based on the data. If the external LAN communication unit 205 receives a print execution instruction from the PC 400, or if the internal LAN communication unit 206 receives a print status from the MFP 100, the device control container 259 is determined as the transfer destination, and the process proceeds to step S03.

In step S03, a node ID is added to the data, and the process proceeds to step S04. The node ID is identification information for identifying the server 200, and in this case is the network address assigned to the server 200 in the external LAN 3. In step S04, the data is output to the transfer destination, and the process returns to step S01.

Figure 12 is a diagram showing an example of the flow of device proxy processing. The device proxy processing is executed by the main CPU 201 of the server 200 provided in the first multifunction device 1 as the main CPU 201 executes a peripheral device control program stored in the ROM 202, HDD 204, or CD-ROM 210. Specifically, the device proxy processing is executed by the first device proxy container 255 realized by the main CPU 201.

Referring to FIG. 12, the first device proxy container 255 realized by the main CPU 201 acquires the node ID of its own device (step S11). The node ID is identification information for identifying the server 200. The node ID is a network address assigned to the server 200 in the external LAN 3. The first device proxy container 255 requests the node ID of the server 200 from the first cluster management unit 251 realized by the main CPU 201. Then, it is determined whether or not a device to be controlled exists (step S12). When configuring a virtual system, the MFP 100 is set in advance in the server 200 as a device to be controlled, and the MFP 100A is set in advance in the server 200A as a device to be controlled. Information on the device to be controlled is stored in advance in the HDD 204. The first cluster management unit 251 may output information on the device to be controlled. If a device to be controlled exists, the process proceeds to step S13, but if not, the process proceeds to step S15. Steps S15 and S16 will be described later.

In step S13, a virtual address assigned to the first device proxy container 255 in the virtual network is obtained, and the process proceeds to step S14. In step S14, registration information is stored, and the process proceeds to step S17. The registration information includes the node ID obtained in step S11 and the virtual address obtained in step S13. The registration information is stored in a registration DB stored in the HDD 204.

In step S17, it is determined whether data has been input from another container. The process waits until data is input (NO in step S17), and if data has been input (YES in step S17), the process proceeds to step S18. In step S18, the data is sent to the device to be controlled, and the process returns to step S17.

Figure 13 is a diagram showing an example of the flow of UI proxy processing. The UI proxy processing is a process executed by the main CPU 201 of the server 200 provided in the first multifunction device 1, as the main CPU 201 executes a peripheral device control program stored in the ROM 202, HDD 204, or CD-ROM 210. Specifically, the UI proxy processing is a process executed by the first UI proxy container 257 realized by the main CPU 201.

Referring to FIG. 13, the first UI proxy container 257 realized by the main CPU 201 acquires the node ID of its own device (step S21). The node ID is identification information for identifying the server 200. The node ID is a network address assigned to the server 200 in the external LAN 3. The first UI proxy container 257 requests the node ID of the server 200 from the first cluster management unit 251 realized by the main CPU 201.

Then, the virtual address assigned to the first UI proxy container 257 in the virtual network is obtained (step S22), and the process proceeds to step S23. In step S23, registration information is stored. The registration information includes the node ID obtained in step S21 and the virtual address obtained in step S22. The registration information is stored in a registration DB stored in the HDD 204.

In step S24, it is determined whether an operation has been accepted from the operation panel 300. If the operation has been accepted, the process proceeds to step S25; if not, the process proceeds to step S27. In step S25, the node ID acquired in step S21 is added to the operation, and the process proceeds to step S26. In step S26, the operation is output to the device control container 259, and the process proceeds to step S27.

In step S27, it is determined whether data has been input from another container. If data has been input, the process proceeds to step S28; if not, the process returns to step S24. In step S28, an image of the data is displayed on the operation panel 300, and the process returns to step S24.

Figure 14 is a diagram showing an example of the flow of device control processing. The device control processing will be described taking as an example a process executed by the main CPU 201A of the server 200A of the second multifunction device 2 as the main CPU 201A executes a peripheral device control program stored in the ROM 202, HDD 204 or CD-ROM 210. Specifically, the device control processing is a process executed by the device control container 259 realized by the main CPU 201A.

Referring to FIG. 14, the device control container 259 implemented by the main CPU 201A determines whether data has been input from another container (step S31). If data has been input from another container, the process proceeds to step S32, otherwise the process proceeds to step S33. For example, a print execution instruction is input from the first reverse proxy container 253. Also, an operation input by the user is input from the first UI proxy container 257. In step S32, a job is set according to the data input in step S31, and the process proceeds to step S33. The job settings include, for example, conditions for forming an image.

In step S33, it is determined whether the data input in step S31 indicates a job execution instruction. If the data is an operation, it is determined whether the operation indicates a job execution instruction, and if the data is a print execution instruction, it is determined that the data indicates a job execution instruction. If the data indicates a job execution instruction, processing proceeds to step S34, but if not, processing returns to step S31. In step S34, a print job is generated, and processing proceeds to step S35.

In step S35, the node ID is extracted, and the process proceeds to step S36. The node ID added to the data input in step S31 is extracted. In step S36, it is determined whether registration information including the node ID extracted in step S35 is registered in the registration DB. The registration information here is registration information including the virtual address of the device proxy container. When the above-mentioned device proxy process is executed, registration information is registered if a device to be controlled exists, and if a device to be controlled does not exist, registration information is not registered and an alternative device is registered. If registration information including the node ID extracted in step S35 is registered in the registration DB, the process proceeds to step S37, but if not, the process proceeds to step S38.

In step S37, the virtual address included in the registration information is determined, and the process proceeds to step S40. Steps S38 and S39 will be described later. In this example, the registration information including the node ID extracted in step S35 includes the virtual address of the first device proxy container 255. In this case, in step S40, the print job is sent to the first device proxy container 255 to which the virtual address determined in step S37 is assigned, and the process proceeds to step S41. In this case, the first device proxy container 255 sends the print job to the MFP 100, so the print job is executed in the MFP 100. Then, in step S41, status information is generated and stored in the HDD 204. The status information includes the virtual address of the container that has output the data input in step S41, and the node ID extracted in step S35.

In the next step S42, it is determined whether or not a print status has been input from another container. If a print status has been input, the process proceeds to step S42; if not, the process returns to step S31. In step S43, the node ID added to the print status is extracted, and the process proceeds to step S44. In step S44, the status information is updated, and the process proceeds to step S45. Specifically, the print status of the status information stored in HDD 204 in step S41 that includes the node ID extracted in step S42 is updated with the print status input in step S42.

In step S45, the virtual address of the setting source of the print job is acquired, and the process proceeds to step S46. The virtual address included in the status information including the node ID extracted in step S42 is acquired as the setting source virtual address. In step S46, the print status is output to the setting source, and the process returns to step S31. Specifically, the print status is output to the container identified by the virtual address acquired in step S45. For example, when the first reverse proxy container 253 receives a print execution instruction from the PC 200, the print status is output to the first reverse proxy container 253 and transmitted from the first reverse proxy container 253 to the PC 400. Also, when the first UI proxy container 257 accepts an operation from the operation panel 300, the print status is transmitted to the first UI proxy container 257, and is displayed on the operation panel 300 by the first UI proxy container 257.

<Modification>
In the information processing system of the modified example, the first multifunction device 1 does not include the MFP 100. In this case, a print job input to the first multifunction device 1 is executed by the MFP 100A included in the second multifunction device 2.

Figure 15 is a diagram for explaining an overview of a virtual system in a modified example. The virtual system in the modified example is composed of a first multifunction device 1 and a second multifunction device 2. The first multifunction device 1 includes a server 200 and an operation panel 300, and the second multifunction device 2 includes a server 200A, an MFP 100A, and an operation panel 300A.

In the first multifunction device, the external LAN communication unit 205 of the server 200 is connected to the external LAN 3. In the second multifunction device 2, the external LAN communication unit 205A of the server 200A is connected to the external LAN 3, and the internal LAN communication unit 206A is connected to the internal LAN 4. The MFP 100A is connected to the internal LAN 4A. Therefore, the server 200A can communicate with the MFP 100A via the internal LAN 4A. In the internal LAN 4A, the network addresses assigned to the server 200A and the MFP 100A are predetermined fixed IP addresses. In addition, the server 200 of the first multifunction device, the server 200A of the second multifunction device 2, and the PC 400 can communicate with each other via the external LAN 3.

Figure 16 is a block diagram showing an example of the functions of a CPU provided in a server of a first multifunction device in a modified example. The functions shown in Figure 16 are functions that are realized by the main CPU 201 provided in the server 200 of the first multifunction device 1 as the main CPU 201 executes a peripheral device control program in the modified example.

Referring to FIG. 16, the difference from the functions shown in FIG. 5 is that the first cluster management unit 251 has been changed to a first cluster management unit 251B, and the first device proxy container 255 has been changed to a first device proxy container 255B. The other functions are the same as those shown in FIG. 5, so the description will not be repeated here.

The first cluster management unit 251B generates a first reverse proxy container 253, a first device proxy container 255B, and a first UI proxy container 257 in the main CPU 201. The first cluster management unit 251B includes an alternative device registration unit 291. The alternative device registration unit 291 stores the node ID of the alternative device in the HDD 204. For example, when the node ID of the alternative device is input by an administrator who manages the virtual system, the alternative device registration unit 291 stores the node ID of the alternative device in the HDD 204. Here, an example will be described in which the node ID of the server 200A of the second composite device 2 is stored in the HDD 204 as the node ID of the alternative device.

The first device proxy container 255B includes a first device identification information acquisition unit 271 and an alternative device registration unit 273B. In response to the first device proxy container 255 starting up, the first device identification information acquisition unit 271 acquires the node ID of the server 200 from the first cluster management unit 251B and outputs the node ID to the alternative device registration unit 273B.

The alternative device registration unit 273B acquires the node ID of the alternative device stored in the HDD 204. The alternative device registration unit 273B generates alternative registration information including the node ID of the server 200 and the node ID of the alternative device, and stores the alternative registration information in a registration DB stored in the HDD 204.

Figure 17 is a diagram showing an example of data flow when a virtual system in a modified example is started. In Figure 17, the vertical direction indicates the passage of time, and the arrows indicate the flow of data. Note that Figure 17 shows the first device proxy container 255B, first UI proxy container 257, and first cluster management unit 251B formed in the server 200 of the first composite device 1.

Referring to FIG. 17, when the virtual system is started, the first device proxy container 255B reads the node ID of the alternative device from the HDD 204. The first device proxy container 255B then requests the node ID from the first cluster management unit 251. In response to the request, the first cluster management unit 251 replies with the node ID of the server 200, and the first device proxy container 255 receives the node ID of the server 200. The first device proxy container 255 then generates alternative registration information including the node ID of the server 200 and the node ID of the alternative device, and stores the alternative registration information in a registration DB stored in the HDD 204.

When the virtual system is started, the first UI proxy container 257 requests a node ID from the first cluster management unit 251. In response to the request, the first cluster management unit 251 replies with the node ID of the server 200, and the first UI proxy container 257 receives the node ID of the server 200. The first UI proxy container 257 then generates registration information that associates the node ID of the server 200 with the virtual address assigned to the first UI proxy container 257, and stores the registration information in a registration DB stored in the HDD 204.

Figure 18 is a diagram showing an example of data flow when a PC requests the first multifunction device to execute printing. The vertical direction indicates the passage of time, and the arrows indicate the flow of data. Here, an example is explained in which a print execution request is sent from the PC 200 to the first multifunction device 1. Note that Figure 18 shows a first reverse proxy container 253 formed on the server 200 of the first multifunction device 1, and a second reverse proxy container 253A, device control container 259, and second device proxy container 255A formed on the server 200A of the second multifunction device 2.

First, the data flow when the PC 400 causes the first multifunction device 1 to execute a print job will be described. This data flow is indicated by a bold line in FIG. 15. With reference to FIG. 18, when a print execution request is sent from the PC 400 to the first multifunction device 1, the first reverse proxy container 253 receives the print execution request. The first reverse proxy container 253 adds the node ID of the server 200 to the print execution request and outputs it to the device control container 259.

When a print execution request is input, the device control container 259 generates a print job for forming an image of the data determined by the print execution request. In addition, the device control container 259 extracts the node ID of the server 200 added to the print execution request in order to determine the container to which the print job is to be output. The device control container 259 searches the registration DB stored in the HDD 204 using the node ID of the server 200. However, in the modified example, registration information including the node ID of the server 200 is not registered in the registration DB. Therefore, the device control container 259 searches for an alternative device registered in the registration DB using the node ID of the server 200, and extracts the node ID alternative registration information of the server 200. Then, the device control container 259 obtains the node ID of the server 200A, which is determined as the alternative device, from the alternative registration information including the node ID of the server 200. Furthermore, the device control container 259 searches the registration DB using the node ID of the server 200A. In the registration DB, the second device proxy container 255A registers registration information that associates the node ID of the server 200A with the virtual address of the second device proxy container 255A. The device control container 259 determines the virtual address of the second device proxy container 255A based on the registration information that includes the node ID of the server 200A.

Then, the device control container 259 outputs the print job to the second device proxy container 255A identified by the virtual address, and notifies the PC 400 that sent the print execution request that the transmission of the print job is complete. The second device proxy container 255A transfers the print job to the MFP 100A, and causes the MFP 100A to execute the print job.

When a print execution request is input, the device control container 259 acquires the virtual address of the first reverse proxy container 253 that has output the print execution request, and after sending the print job, generates status information including a print status indicating the print state of the print job, and stores it in the HDD 204. In this example, the status information includes the virtual address of the first reverse proxy container 253 that has output the print execution request, and the node ID of the server 200A on which the second device proxy container 255A that has output the print job is generated. The device control container 259 acquires the node ID of the server 200A from the second device proxy container 255A that has output the print job. The server 200A is an alternative device for the server 200. The device control container 259 then transmits a print status indicating that the transmission of the print job has been completed to the PC 400. Specifically, the device control container 259 outputs the print status to the first reverse proxy container 253, and the first reverse proxy container 253 transmits the print status to the PC 400.

Next, the flow of the print status indicating the result of MFP 100A executing a print job will be described. This data flow is indicated by a thick dotted line in FIG. 15. MFP 100A receives the print job, executes the print job, and starts printing. Then, if necessary, it returns a print status indicating the printing status to server 200A. The print status is received by the second reverse proxy container 253A. The second reverse proxy container 253A adds the node ID of server 200A to the print status, and outputs the print status to the device control container 259.

When the print status is input, the device control container 259 extracts the node ID added to the print status and extracts the status information including the node ID from the status information stored in the HDD 204. The device control container 259 determines the virtual address associated with the extracted node ID from the status information including the node ID. Since the status information including the node ID of the server 200A and the virtual address of the first reverse proxy container 253 is stored in the HDD 204 at the stage of generating the print job, the device control container 259 determines the virtual address of the first reverse proxy container 253. Then, the device control container 259 updates the print status of the status information and outputs the print status to the first reverse proxy container 253 specified by the virtual address of the first reverse proxy container 253. The first reverse proxy container 253 transmits the print status to the PC 400 that has sent the print execution request.

In the virtual system of the modified example, the device proxy process shown in FIG. 12 is executed by the main CPU 201. In this case, steps S15 and S16 are executed. In step S15, the node ID of the alternative device is obtained, and the process proceeds to step S16. In the virtual system, if no device to be controlled is connected to the server 200, an alternative device is preregistered in the server 200, and the node ID of the alternative device stored in the HDD 204 is read out. In this case, server 200A is preregistered as the alternative device for server 200, and therefore the node ID of server 200A is stored in the HDD 204 as the node ID of the alternative device for server 200.

In step S16, the alternative device is registered, and the process proceeds to step S17. Alternative registration information including the node ID of server 200 and the node ID of the alternative device read in step S15 is registered in the registration DB of HDD 204.

In the virtual system of the modified example, the device proxy process shown in FIG. 14 is executed by the main CPU 201A of the server 200A. In this case, steps S38 and S39 are executed. In step S38, an alternative device is determined, and the process proceeds to step S39. Alternative registration information including the node ID extracted in step S35 is read from the alternative registration information stored in the HDD 204, and the node ID of the alternative device included in the read alternative registration information is determined. In the modified example, since the server 200A is set as the alternative device for the server 200, the node ID of the server 200A is determined.

In step S39, the virtual address included in the registration information is determined, and the process proceeds to step S40. Here, registration information including the node ID of the server 200A, which is the alternative device determined in step S38, is registered in the registration DB, and the registration information includes the virtual address of the second device proxy container 255A. In this case, in step S39, the virtual address of the second device proxy container 255A is determined. In the next step S40, the print job is sent to the second device proxy container 255A to which the virtual address determined in step S37 is assigned, and the process proceeds to step S41. In this case, the second device proxy container 255A sends the print job to the MFP 100A, and the print job is executed in the MFP 100A.

Then, in step S41, status information is generated and stored in HDD 204. The status information includes the virtual address of the container that has output the instruction to execute the job, the node ID of server 200A, which is the alternative device extracted in step S38, and the print status. The container that has output the instruction to execute the job is any one of the first reverse proxy container 253, the first UI proxy container 257, the second reverse proxy container 253A, and the second UI proxy container 257A.

In step S45, the virtual address of the setting source of the print job is acquired, and the process proceeds to step S46. The virtual address included in the status information including the node ID extracted in step S43 is acquired as the setting source virtual address. In step S46, the print status is output to the setting source, and the process returns to step S31. Specifically, the print status is output to the container identified by the virtual address acquired in step S45. For example, when the first reverse proxy container 253 receives a print execution instruction from the PC 200, the print status is output to the first reverse proxy container 253 and transmitted from the first reverse proxy container 253 to the PC 400. Also, when the first UI proxy container 257 accepts an operation from the operation panel 300, the print status is transmitted to the first UI proxy container 257, and is displayed on the operation panel 300 by the first UI proxy container 257.

As described above, the information processing system in this embodiment is an information processing system that configures a virtual system with multiple servers 200, 200A, and each of the multiple servers 200, 200A inputs and outputs data via a virtual network and generates a part of the multiple containers that configure the virtual system. In the server 200, the first cluster management unit 251 generates a first reverse proxy container 253, which is an input receiving container that adds the node ID of the server 200 to data input from outside the server 200, and a first device proxy container 255 that transmits data input from other containers to the MFP 100 because the server 200 is a connection device connected to the MFP 100. In the server 200, the second cluster management unit 251A generates a second reverse proxy container 253A which is an input receiving container that adds the node ID of the server 200A to data input from outside the server 200A, a second device proxy container 255A which transmits data input from other containers to the MFP 100A because the server 200A is a connection device connected to the MFP 100A, and a device control container 259 which is an application container that executes a predetermined process because the server 200A is a responsible device determined in the virtual system. Since the server 200 is a connection device, registration information associating the node ID of the server 200 with the virtual address of the first device proxy container 255 is registered in the registration DB in response to the generation of the first device proxy container 255, and since the server 200A is a connection device, registration information associating the node ID of the server 200A with the virtual address of the second device proxy container 255A is registered in the registration DB in response to the generation of the second device proxy container 255A. The device control container 259 outputs the processed data to another container, for example, the first device proxy container 255 associated with the server 200 identified by the node ID added to the data input from the first reverse proxy container 253, based on the registration information registered in the virtual system. Therefore, for example, when data is input to the server 200, the data is output to the MFP 100 connected to the server 200, and when data is input to the server 200A, the data is output to the MFP 100A connected to the server 200A. Therefore, in the multiple servers 200, 200A constituting the virtual system, it is possible to identify the peripheral device to be controlled from among the multiple MFPs 100, 100A. This is particularly effective when the fixed IP address assigned to the MFP 100 in the internal LAN 4 and the fixed IP address assigned to the MFP 100A in the internal LAN 4A are the same.

In addition, the first reverse proxy container 253 adds the node ID of the server 200 to the data received via the external LAN 3, and the second reverse proxy container 253A adds the node ID of the server 200A to the data received via the external LAN 3. This allows the MFP 100 to execute a print job according to a print execution instruction sent from the PC 400 to the server 200, and allows the MFP 100A to execute a print job according to a print execution instruction sent from the PC 400 to the server 200A.

The first UI proxy container 257 also accepts operations input by the user to the operation panel 300 and adds the node ID of the server 200 to the operations, and the second UI proxy container 257A accepts operations input by the user to the operation panel 300A and adds the node ID of the server 200A to the operations. This allows the MFP 100 to execute a print job according to the operations input by the user to the operation panel 300, and allows the MFP 100A to execute a print job according to the operations input by the user to the operation panel 300A.

After outputting a print job, which is control data for controlling the MFP 100 according to the instruction data output from the first reverse proxy container 253 or the first UI proxy container 257, to the first device proxy container 255, the device control container 259 outputs the print status received from the MFP 100 to either the first reverse proxy container 253 or the first UI proxy container 257, whichever output the instruction data. After outputting a print job, which is control data for controlling the MFP 100A according to the instruction data output from the second reverse proxy container 253A or the second UI proxy container 257A, to the second device proxy container 255A, the device control container 259 outputs the print status received from the MFP 100A to either the second reverse proxy container 253A or the second UI proxy container 257A, whichever output the instruction data. This allows the user to be notified of the control result.

The server 200 is connected to the MFP 100 via the internal LAN 4, and the first reverse proxy container 253 outputs data received from the MFP 100 via the internal LAN 4 to the device control container 259. The server 200A is connected to the MFP 100A via the internal LAN 4A, and the second reverse proxy container 253A outputs data received from the MFP 100A via the internal LAN 4A to the device control container 259A. Therefore, in the virtual system, data output by the MFP 100 can be processed, and data output by the MFP 100A can be processed.

In the information processing system of the modified example, the server 200 registers in the registration DB alternative registration information that associates the node ID of the server 200A, which is predefined as an alternative device for the server 200, with the node ID of the server 200. When the server 200 is identified by the identification information added to the data input from another container, the device control container 259 outputs processed data to the server 200A, which is an alternative device associated with the server 200 by the alternative registration information, and the second device proxy container 255A, which is associated with the server 200 by the registration information, since the server 200 is not associated by the registration information. Therefore, a print job after processing data input from the outside to the server 200 is sent to the MFP 100A connected to the server 200A, which is an alternative device associated with the server 200. Therefore, when a print execution request is input to the server 200, the MFP 100A can execute the print job according to the print execution request. Also, when a print execution request is input to the server 200A, the MFP 100A can execute the print job according to the print execution request.

In this embodiment, MFP 100 is connected to internal LAN 4, and MFP 100A is connected to internal LAN 4A, but MFP 100 and MFP 100A may be connected to external LAN 3.

The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present invention is indicated by the claims, not by the above description, and is intended to include all modifications within the meaning and scope of the claims.

1 First multifunction device, 2 Second multifunction device, 3 External LAN, 4, 4A Internal LAN, 200, 200A Server, PC 400, 111 Device CPU, 112 Device LAN communication unit, 113 ROM, 114 RAM, 115 Facsimile unit, 116 VRAM, 120 Automatic document feeder, 130 Document reading unit, 140 Image forming unit, 150 Paper feed unit, 201, 201A Main CPU, 202 ROM, 203 RAM, 204 HDD, 205, 205A External LAN communication unit, 206, 206A Internal LAN communication unit, 207 VRAM, 208 Panel communication unit, 209 External storage device, 300, 300A Operation panel, 301 Switching unit, 303 Display unit, 305 Operation unit, 307 touch panel, 309 hard key unit, 310 switching unit, 251 first cluster management unit, 253 first reverse proxy container, 255 first device proxy container, 257 first UI proxy container, 251A second cluster management unit, 253A second reverse proxy container, 255A second device proxy container, 257A second UI proxy container, 259 device control container, 273B alternative device registration unit, 291 alternative device registration unit.

Claims (25)

An information processing system including a plurality of control devices,
At least one of the plurality of control devices includes a processing control unit that executes a process for controlling one or more processing devices to which the same fixed IP address is assigned;
Each of the plurality of control devices includes a reception unit that receives a command input from an external device,
Each of the one or more control devices connected to one or more of the processing devices among the plurality of control devices includes an equipment communication unit that communicates with a single processing device connected to the control device;
An information processing system in which the processing control unit transmits the processing result obtained by executing processing in accordance with the command received by one of the multiple receiving units provided in each of the multiple control devices to the device communication unit associated with the receiving unit that received the command, among the one or more device communication units. The information processing system according to claim 1, wherein the processing control unit transmits the processing result to the device communication unit associated with the reception unit that received the command, and then outputs a response received from the processing device with which the device communication unit to which the processing result was transmitted communicates to the reception unit that received the command. An information processing system including a plurality of control devices,
At least one of the plurality of control devices includes a processing control unit that executes processing for controlling one or more processing devices;
Each of the plurality of control devices includes a reception unit that receives a command input from an external device,
Each of the one or more control devices connected to one or more of the processing devices among the plurality of control devices includes a device communication unit that communicates with the processing device connected to the control device;
a registration unit that registers registration information that associates the device communication unit provided in each of the one or more control devices connected to any one or more of the processing devices among the plurality of control devices with the control device;
the reception unit adds identification information for identifying the control device including the reception unit to the command input from an outside,
An information processing system in which, when the command is input from one of a plurality of receiving units provided in each of a plurality of control devices, the processing control unit transmits the processing result obtained by executing the processing in accordance with the command to the device communication unit provided in the control device identified by the identification information attached to the command. Any of the plurality of control devices further includes an alternative device registration unit that registers alternative registration information that associates the control device that is not connected to any of the one or more processing devices among the plurality of control devices with any of the one or more control devices that are connected to any of the one or more processing devices;
The information processing system of claim 3, wherein when the control device identified by the identification information attached to the command input from one of the multiple receiving units is not registered, the processing control unit transmits the processing result to the device communication unit provided in the control device associated with the control device identified by the identification information attached to the command input from one of the multiple receiving units by the alternative registration information. Each of the plurality of control devices further includes a configuration element management unit that inputs and outputs data via a virtual network and generates a part of a plurality of configuration elements that configure a virtual system;
The information processing system according to claim 3 , wherein the plurality of components include the process control unit, the reception unit, the registration unit, and the device communication unit. The information processing system according to any one of claims 1 to 5, wherein the reception unit provided in each of the one or more control devices connected to the one or more processing devices receives a response received by the control device from the processing device. The information processing system according to any one of claims 1 to 6, wherein the reception unit receives a command that the control device receives from an external device. The information processing system according to claim 7, wherein the reception unit receives commands received via an external network to which the multiple control devices are connected. The information processing system according to any one of claims 1 to 8, wherein the reception unit receives commands input by a user to a user interface. The information processing system according to any one of claims 1 to 9, wherein the processing device includes an image forming device that forms an image. Any one of a plurality of control devices included in an information processing system,
a processing control unit that executes a process for controlling one or more processing devices to which the same fixed IP address is assigned when the device itself is set as a predetermined responsible device among the plurality of control devices;
A reception unit that receives a command input from an external device;
a device communication unit that communicates with a single processing device connected to the device when the device itself is connected to one or more of the processing devices;
A control device, wherein the processing control unit transmits a processing result obtained by executing processing in accordance with the command received by one of the multiple receiving units provided in each of the multiple control devices to one or more device communication units provided in each of the one or more control devices connected to one or more of the processing devices among the multiple control devices, the device communication unit corresponding to the receiving unit that received the command. The control device according to claim 11, wherein the processing control unit transmits the processing result to the device communication unit associated with the reception unit that received the command, and then outputs a response received from the processing device with which the device communication unit to which the processing result was transmitted communicates to the reception unit that received the command. Any one of a plurality of control devices included in an information processing system,
a processing control unit that executes a process for controlling one or more processing devices when the device itself is set as a predetermined responsible device among the plurality of control devices;
A reception unit that receives a command input from an external device;
When the device itself is connected to one or more of the processing devices, a device communication unit that communicates with the processing device connected to the device itself;
a registration unit that registers registration information that associates the device communication unit provided in each of the one or more control devices connected to any one or more of the processing devices among the plurality of control devices with the control device;
the reception unit adds identification information for identifying the control device including the reception unit to the command input from an outside,
A control device, wherein when the command is input from one of a plurality of receiving units each provided in a plurality of control devices, the processing control unit transmits the processing result obtained by executing the processing in accordance with the command to the device communication unit provided in the control device identified by the identification information attached to the command. When the control device is a predetermined registered device among the plurality of control devices, the control device further includes an alternative device registration unit that registers alternative registration information that associates the control device that is not connected to any of the one or more processing devices among the plurality of control devices with any of the one or more control devices that are connected to any of the one or more processing devices;
The control device according to claim 13, wherein, when the control device identified by the identification information attached to the command input from one of the multiple receiving units that each of the multiple control devices has is not registered, the processing control unit transmits the processing result to the device communication unit provided in the control device that is associated with the control device identified by the identification information attached to the command input from one of the multiple receiving units by the alternative registration information. Each of the plurality of control devices further includes a configuration element management unit that inputs and outputs data via a virtual network and generates a part of a plurality of configuration elements that configure a virtual system;
The control device according to claim 13 or 14, wherein the plurality of components include the process control unit, the reception unit, the registration unit, and the device communication unit. A peripheral device control method executed in an information processing system including a plurality of control devices, comprising:
causing at least one of the plurality of control devices to execute a process control step for executing a process for controlling one or more processing devices to which the same fixed IP address is assigned;
causing each of the plurality of control devices to execute a receiving step of receiving a command input from an external device;
Executing an equipment communication step in which each of the one or more control devices connected to any one or more of the processing devices among the plurality of control devices communicates with a single processing device connected to the control device;
The processing control step of the peripheral device control method includes a step of transmitting a processing result obtained by executing processing in accordance with the command received by any one of the plurality of control devices to a control device associated with the control device from which the command was received, among one or more control devices connected to any one of the processing devices. The peripheral device control method according to claim 16, wherein the processing control step includes a step of outputting, to the control device that accepted the command, a response received from the processing device connected to the control device that received the command after the processing result is transmitted to the control device associated with the control device that received the command among one or more control devices connected to any one of the processing devices. A peripheral device control method executed in an information processing system including a plurality of control devices, comprising:
causing at least one of the plurality of control devices to execute a process control step for executing a process for controlling one or more processing devices;
causing each of the plurality of control devices to execute a receiving step of receiving a command input from an external device;
A device communication step is performed in each of the one or more control devices connected to any one or more of the processing devices among the plurality of control devices to communicate with the processing device connected to the control device;
A registration step of registering each of the one or more control devices connected to one or more of the processing devices among the plurality of control devices is executed by any one of the plurality of control devices;
the receiving step includes a step of adding identification information for identifying the control device that has received the command to the command input from outside,
The processing control step of the peripheral device control method includes a step of, when the command is input from one of a plurality of control devices, and when the control device identified by the identification information attached to the command is registered , transmitting a processing result of processing performed in accordance with the command to the control device identified by the identification information attached to the command. having one of the plurality of control devices execute an alternative device registration step of registering alternative registration information that associates the control device that is not connected to any of the one or more processing devices among the plurality of control devices with any of the one or more control devices that are connected to any of the one or more processing devices;
The peripheral device control method of claim 18, wherein the processing control step includes a step of transmitting the processing result to the control device identified by the identification information attached to the command input from any one of the plurality of control devices when the control device identified by the identification information attached to the command is not registered, and the control device associated with the control device identified by the identification information attached to the command by the alternative registration information. a configuration element management step of inputting and outputting data via a virtual network to each of the plurality of control devices and generating a part of a plurality of configuration units constituting a virtual system;
20. The peripheral device control method according to claim 18, wherein the plurality of components execute any one of the process control step, the reception step, the registration step, and the device communication step. A peripheral device control program for causing a plurality of computers to execute a peripheral device control method,
causing at least one of the plurality of computers to execute a process control step for executing a process for controlling one or more processing devices to which the same fixed IP address is assigned;
causing each of the plurality of computers to execute a receiving step of receiving a command input from an external source;
executing a device communication step for each of the one or more computers connected to any one or more of the processing devices among the plurality of computers to communicate with a single processing device connected to the computer;
A peripheral device control program, wherein the processing control step includes a step of transmitting the processing result obtained by executing processing in accordance with the command received by any one of the plurality of computers to a computer associated with the computer from which the command was received, among one or more computers connected to any one of the processing devices. The peripheral device control program according to claim 21, wherein the processing control step includes a step of outputting, to the computer that accepted the command, a response received from the processing device connected to the computer to which the processing result was sent after the processing result was sent to the computer associated with the computer to which the command was received, among one or more of the computers connected to any one of the processing devices. A peripheral device control program for causing a plurality of computers to execute a peripheral device control method,
causing at least one of the plurality of computers to execute a process control step for executing a process for controlling one or more processing devices;
causing each of the plurality of computers to execute a receiving step of receiving a command input from an external source;
causing each of the one or more computers connected to any of the one or more processing devices among the plurality of computers to execute a device communication step of communicating with the processing device connected to the computer;
A registration step of registering each of the one or more computers connected to any one or more of the processing devices among the plurality of computers is executed by any one of the plurality of computers;
the receiving step includes a step of adding identification information for identifying the computer that has received the command to the command input from outside,
A peripheral device control program, wherein the processing control step includes a step of, when the command is input from one of a plurality of computers, and when the computer identified by the identification information attached to the command is registered , sending a processing result of executing the processing in accordance with the command to the computer identified by the identification information attached to the command. having one of the plurality of computers execute an alternative device registration step of registering alternative registration information that associates the computer that is not connected to any of the one or more processing devices among the plurality of computers with any of the one or more computers that are connected to any of the one or more processing devices;
The peripheral device control program of claim 23, wherein the processing control step includes a step of transmitting the processing result to the computer associated with the computer identified by the identification information added to the command input from any one of the multiple computers by the alternative registration information when the computer identified by the identification information added to the command is not registered. and causing each of the plurality of computers to further execute a configuration element management step of inputting and outputting data via a virtual network and generating a part of a plurality of configuration parts that constitute a virtual system;
25. The peripheral device control program according to claim 23, wherein the plurality of components execute any one of the process control step, the reception step, the registration step, and the device communication step.

Images