JP2007280302A - Complex machine, method for controlling operation of complex machine and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To flexibly add or change the function of a front-end PC. <P>SOLUTION: A real time OS11, Corba 12 and filter 13 are mounted on a complex machine 10, and a network I/F 14, a decomposer/imager 15 and an IOT controller 16 operating on them are achieved by an remotely callable API. When the complex machine 10 is directly connected to a direct network 90 as shown by (a), a front end PC30 is not detected by a detection means 17, and the remote calling of the API from an external device is suppressed by the filter 13. Meanwhile, when the complex machine 10 is connected through a front-end PC 30 to a network 90 as shown by (b), the front-end PC 30 is recognized by the detection means 17, and only the remote calling of the API from the front end PC 30 is executed by the filter 13. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a multifunction device that implements a printer function, a scanner function, a facsimile function, and the like in one housing, and more specifically, a multifunction device that can be connected to a device operated for operating instructions of these functions. About.

  2. Description of the Related Art In recent years, so-called multi-function machines that realize a printer function, a scanner function, a facsimile function, and the like in one housing have become widespread. Some of them are connected to a PC (hereinafter referred to as “front-end PC”) operated for operating instructions of these functions. Recently, a method of configuring a system by mounting Windows (registered trademark) on the front-end PC has come to be used. By this method, it is possible to create a Windows-like GUI or to configure a network system having high affinity with Windows (registered trademark). In addition, as the front-end PC, other workstations and servers such as Linux (registered trademark) may be used.

  As described above, the front-end PC can provide many functions to the user, and the functions of the MFP main body are enhanced. However, data communication between the MFP and the front-end PC may be performed using a special protocol (hereinafter referred to as “front-end I / F”) for the interface between the two using a unique protocol. There are many current situations.

  As a conventional technique described in the publication, there is one in which an operation unit of a digital multi-function peripheral is detachable (see, for example, Patent Document 1). This patent document 1 also discloses that the operation unit can be used as a tool for updating the system software of the digital multi-function peripheral.

JP 2003-309681 A

By the way, the front-end PC can provide many functions, and there is often a demand for adding or changing the functions of the front-end PC.
However, as described above, when the multifunction peripheral and the front-end PC communicate with each other using a unique protocol through the front-end I / F, it is not easy to add or change functions. That is, when the front end I / F does not correspond to the function after addition or change, the front end I / F must be replaced to add or change the function.
In some cases, the multifunction peripheral already has a function corresponding to a function to be added or changed to the front-end PC. However, even in such a case, unless the front end I / F corresponds to the function after addition or change, the function of the front end PC cannot be added or changed unless the function is replaced.

That is, in the prior art, even when only the front end I / F does not support the addition or change of functions, the function of the front end PC cannot be added or changed flexibly. There was a problem of hindering smooth operation.
The technique of Patent Document 1 merely changes the system software of the digital multi-function peripheral using a detachable operation unit, and does not solve the above problem.

The present invention has been made to solve the technical problems as described above, and an object of the present invention is to make it possible to flexibly add or change functions of the front-end PC.
Another object of the present invention is to enable secure use of the functions of the multifunction machine by the front end PC.

  For this purpose, in the present invention, the functions of the multifunction peripheral are realized by functions that can be remotely called, that is, API (Application Program Interface). This function can be called remotely only from authorized front-end PCs. In other words, the multifunction device of the present invention receives a storage unit that stores a function in a distributed object environment for operating a specific function and a remote call of the function stored in the storage unit from another device. Control means for determining whether or not the device is a specific device permitted to remotely call the function and controlling the function call based on the result of the determination.

  In the present invention, when the multifunction device does not detect the front-end PC, the remote call of the function from the communication means including the network is suppressed. In that case, the MFP of the present invention further includes detection means for detecting the connection of the specific device, and the control means limits the function call when the detection means does not detect the specific device. .

  Further, according to the present invention, when the multifunction device detects the connection of the front end PC, the function can be called remotely. In that case, the MFP of the present invention further includes detection means for detecting the connection of the specific device, and the control means calls the function when the specific device detected by the detection means is the same as the other device. It will be a thing.

  Furthermore, in the present invention, it is basically possible to remotely call a function via a network. However, the front end PC is recognized from devices connected to the network, and remote calling can be performed only from the recognized device. . In this case, the multifunction peripheral of the present invention further includes detection means for detecting connection of the specific device, and the control means limits the function call when the specific device detected by the detection means is different from the other devices. It becomes that.

  The present invention can also be understood as a method for controlling the operation of the multifunction machine. In this case, the method of the present invention stores the information of a specific device capable of operating the multifunction peripheral in a memory and accepts a remote call of a function in a distributed object environment for operating the multifunction peripheral from another device. A step of determining whether information of the other device is stored in the memory, and a step of controlling a function call based on a result of the determination.

  On the other hand, the present invention can also be understood as a program for controlling the operation of the multifunction machine. In that case, the program of the present invention includes a function for receiving a remote call of a function from another device in a distributed object environment for operating a specific function of the multifunction device, and a specification for permitting the other device to remotely call the function. This is to realize a function for determining whether the device is a device and a function for controlling a function call based on the determination result.

  According to the present invention, it is possible to flexibly add or change functions of the front-end PC.

The best mode for carrying out the present invention (hereinafter referred to as “embodiment”) will be described below in detail with reference to the accompanying drawings.
FIG. 1 shows the configuration of a computer system to which this embodiment is applied.
As shown in the figure, this computer system is configured by connecting a multifunction machine 10 and a terminal device 20 via a network 90.

  Among these, the multifunction device 10 is a device that realizes a printer function, a scanner function, a facsimile function, and the like in one housing. That is, if attention is paid to the printer function, it can be understood as an image forming apparatus, and if attention is paid to the scanner function, it can also be regarded as an image reading apparatus. If attention is paid to the facsimile function, it can be understood as an image transmitting apparatus / image receiving apparatus, and a combination of a printer function and a scanner function can be regarded as a copying machine.

  The multifunction machine 10 is connected to a front-end PC 30 that is operated for operating instructions of these functions. However, the front end PC 30 may be connected via the network 90 instead of the local connection as illustrated.

The terminal device 20 is a device that instructs the multifunction device 10 to print a document, send a facsimile of a document, and the like, and is exemplified by a PC (Personal Computer). In FIG. 1, the front end PC 30 is shown as a device that is operated for operating instructions of functions of the multifunction machine 10, and the terminal device 20 is operated by the multifunction machine 10 as will be described later. Unless it is recognized, the function of the multifunction machine 10 cannot be used.
Furthermore, the network 90 may be a LAN (Local Area Network) or a WAN (Wide Area Network) such as the Internet.

Next, an outline of the present embodiment will be described.
FIG. 2 shows a system configuration in which the front-end PC 30 is not connected to the multifunction device 10 and a system configuration in which the front-end PC 30 is connected to the multifunction device 10.
Among these, FIG. 2A shows a system in which the multifunction machine 10 is directly connected to the network 90 without being connected to the front end PC 30. In the present embodiment, when the front-end PC 30 is not connected to the multifunction device 10 in this way, other devices are prohibited from using the functions of the multifunction device 10 via the network 90.

  On the other hand, FIG. 2B shows a system in which the multifunction machine 10 is connected to the front-end PC 30 via the network 95 and the front-end PC 30 is connected to the network 90. Note that the multifunction machine 10 and the front-end PC 30 may be connected locally instead of via the network 95. In the present embodiment, when the front-end PC 30 is connected to the multifunction device 10 through the network in this way, only the use of the function of the multifunction device 10 from the front-end PC 30 is permitted, and other devices connected to the network. Use from is prohibited.

Here, an example of the internal configuration of the multifunction machine 10 and the front end PC 30 will be described.
First, as shown in FIGS. 2A and 2B, the multi-function device 10 is equipped with a real-time OS 11. Then, Corba (Common Object Request Broker Architecture) (registered trademark) 12 as a distributed object environment is mounted thereon. In addition, a filter 13 which is a program operating on Corba is provided, and this functions as control means for controlling remote calling of the Corba component described below.

In the figure, as a Corba component, a network I / F 14, a decomposer / imager 15, and an IOT (Image Output Terminal) controller 16 are illustrated. Among these, the network I / F 14 is a component that realizes a function as an interface to the network. The decomposer / imager 15 is a component that realizes a function of converting data described in a page description language into image data. Further, the IOT controller 16 is a component that realizes a function of controlling an image forming engine 18 described later. These Corba components can be called locally with respect to each other and can also be called remotely via communication means.
The entity of these Corba components is a program for operating the corresponding function. Accordingly, the Corba component is stored in storage means (not shown), and is called up and executed from there.

In addition, the multifunction machine 10 includes a detection unit 17. This detection means 17 detects the connection of the front end PC 30 and acquires its address and the like.
Further, the multifunction machine 10 has an image forming engine 18. Here, as the image forming engine 18, for example, an electrophotographic system can be used, but any other system may be used.
Here, Corba is exemplified as the distributed object environment, but other distributed object environments such as RMI may be adopted.

  As shown in FIG. 2B, the front-end PC 30 is equipped with a Windows (registered trademark) OS 31. Then, Corba 32 as a distributed object environment is mounted thereon. In the front-end PC 30, an IIS (Internet Information Services) (registered trademark) server 33 and a Web server 34 also operate. The Web server 34 includes a front end I / F 35 that is a Corba component. The front end I / F 35 performs remote calling of the decomposer / imager 15 and the IOT controller 16 which are the above-described Corba components on the multifunction machine 10 side.

Further, FIG. 3 shows a system configuration in which the front-end PC 30 and another terminal device 20 are connected to the multifunction machine 10 via the network 90. In the present embodiment, in such a system configuration, only the functions of the multifunction machine 10 can be used by the front end PC 30 (an apparatus recognized as the front end). Here, FIG. 3 shows one terminal device 20 that cannot use the functions of the multifunction device 10 and one front-end PC 30 that can use the functions of the multifunction device 10. Not limited to. That is, a plurality of terminal devices 20 may be connected to the network 90, and a plurality of front end PCs 30 may be connected to the network 90.
The internal configuration of the terminal device 20 in FIG. 3 is the same as the internal configuration of the front end PC 30 described in FIG.

Next, the detailed operation of the multifunction machine 10 outlined in FIGS. 2 and 3 will be described.
First, the operation of the detection means 17 that detects the connection of the front end PC 30 will be described.
FIG. 4 is a flowchart showing the operation of the detection means 17.
The detection means 17 sends a command for detecting the front end PC 30 to the network 90 (or network 95) (step 101).

Here, as a command for detecting the front-end PC 30, for example, a command for requesting information on a monitoring target device in SNMP (Simple Network Management Protocol) can be used. In this case, the detection means 17 functions as an SNMP manager. In response to this, an SNMP agent operating on a device on the network 90 (or network 95) returns information managed by the MIB (Management Information Base) as a response. This response can include, for example, the device address, manufacturer information, identification information (model / serial number), and the like.
In addition, as a command for detecting the front-end PC 30, a command based on another protocol such as HTTP (HyperText Transfer Protocol) may be used. Also in this case, the address information of the device, manufacturer information, identification information, etc. can be included in the header information of the response by HTTP.

And the detection means 17 determines whether such a response was received (step 102). As a result, when a response is not received within a certain time, it is assumed that the device is not connected, and the process ends. On the other hand, when a response is received, attention is paid to one of the devices that has returned the response, and it is determined whether or not the device can be recognized as the front-end PC 30. That is, the validity of the device is checked (step 103).
As described above, since the information on the manufacturer and the model can be included in the response to the command, the validity can be checked based on the information. For example, it is conceivable that the MFP 10 and the manufacturer of the apparatus are compared and the same manufacturer is recognized as the front end PC 30.

As a result, if it is not determined that the device can be recognized as the front-end PC 30, nothing is performed and it is determined whether there is another device that has returned a response (step 108).
On the other hand, if it is determined that the device can be recognized as the front-end PC 30, the detection means 17 first acquires the address of the device (front-end PC 30) (step 104). Here, the address can be acquired from the received response. Further, the detection means 17 acquires information related to the service provided by the front end PC 30 (step 105). Here, the information related to the service may be acquired by separately sending a command for requesting such information from the MFP 10 or may be included in a response to the command for detecting the front-end PC 30. .

  Then, the detection means 17 identifies the function in the multifunction device 10 corresponding to the service provided by the front end PC 30 (step 106). Specifically, the Corba component that realizes this function is specified. Note that if the information about the service can be acquired in step 105 in a form that can identify the corresponding function in the multifunction machine 10, the process in step 106 may not be performed.

The detecting unit 17 stores correspondence information between the function specified in Step 106 and the address acquired in Step 104 in a memory (not shown) in the multifunction machine 10 (Step 107).
Finally, the detection means 17 determines whether there is another device that has returned a response (step 108).
As a result, if there are other devices, the processes in steps 103 to 107 are repeated. On the other hand, if there is no other device, the process is terminated.

Here, correspondence information (hereinafter referred to as “function / address table”) stored in the memory by the processing of the detection means 17 will be described.
FIG. 5 shows an example of the contents of the function / address table.
As shown in the figure, the function / address table associates the functions of the multifunction machine 10 with the addresses of nodes that can use the functions.

First, information set in the “function” column will be described.
In the “function” column, functions possessed by the multifunction machine 10 are registered in units of software components in which functions in a distributed object environment are packaged or functions in a distributed object. Specifically, descriptions that end with “. *”, Such as “Copy. *”, “Scan. *”, “Mailbox. *”, “Print. *”, Are software components. It is itself. Since a software component is a collection of functions, calling a software component can be considered as calling a function.

First, “Copy. *” Is a software component that sets parameters for copying and executes copying. Among these, the setting of copy parameters is a function that receives parameters set by the user from the front-end PC 30 and applies them to actual copying in the multifunction machine 10. The copy parameters include monochrome / color, resolution, file format (TIFF / PDF), reduction, reading method (both sides / single side), document size, and the like.
“Scan. *” Is a software component that sets scan parameters and executes a scan. In this case as well, the scan parameter setting is a function that receives parameters set by the user from the front-end PC 30 and applies them to the actual scan in the multifunction machine 10.

Further, “Mailbox. *” Is a software component that outputs a list of temporary documents read by scanning and moves the temporary documents to a memory card.
Furthermore, “Print. *” Is a software component that sets printing parameters and executes printing. In this case as well, the print parameter setting is a function that receives parameters set by the user from the front-end PC 30 and applies them to actual printing in the multifunction machine 10.

  The above is an example of software components related to a printer function and a scanner function originally provided in a general multifunction machine 10. However, the functions provided by the multifunction machine 10 are diversified today. In other words, although it is not directly related to image formation, image reading, and image transmission / reception, there may be ancillary functions required when providing services using these functions.

FIG. 5 illustrates a function for charging for the use of the multifunction machine 10 as such an accompanying function.
First, “Charge.current” is a function for acquiring the balance of the coin kit. “Charge.subtract” is a function for subtracting the balance of the coin kit. “Charge.history” is a function for acquiring the history of the coin kit. Among these, “Charge.current” and “Charge.subtract” are positioned as functions for the user, and “Charge.history” is positioned as a function for the administrator.

Next, information set in the “available nodes” column will be described. Basically, the address of a node that can remotely call the corresponding software component or function is registered in this column. Here, an IP address is registered as an address.
First, “127.0.0.1” is a loopback address used for a local call between software components in the multifunction machine 10. For all functions, calling from this loopback address is set to be possible.

  Further, “192.0.0.2” is assumed to be the IP address of the scan service front-end PC 30. The front-end PC 30 provides a function of reading a scanned image to a memory card or the like, for example. Therefore, the front-end PC 30 is allowed to use the scan, the operation of the scanned temporary document, and the function for the user among the functions related to the coin kit. That is, this IP address is set for “Scan. *”, “Mailbox. *”, “Charge.current”, and “Charge.subtract”.

On the other hand, “192.0.0.3” is the IP address of the front-end PC 30 for image printing. The front end PC 30 provides a function of connecting a digital camera or a memory card, for example, with a USB or the like and printing an image therein. Therefore, the front end PC 30 is permitted to perform printing operations and use functions for the user among the functions relating to the coin kit. That is, this IP address is set for “Print. *”, “Charge.current”, and “Charge.subtract”.
Here, only the IP address is registered in the “available node” column, but the port number may be managed in addition to the IP address. Further, other information may be managed as long as the information identifies the node.

Next, the operation of the filter 13 for controlling the remote call with reference to this function / address table will be described.
FIG. 6 is a flowchart showing the operation of the filter 13.
First, the filter 13 receives a remote call of a software component or function from another device (step 111). Then, the address of this device is acquired (step 112).

Thereafter, the filter 13 determines whether or not the correspondence between the software component or function specified in Step 111 and the address acquired in Step 112 is registered in the function / address table (Step 113).
As a result, if registered, the remote call of the software component or function is executed (step 114). On the other hand, if not registered, an error response is returned to the apparatus (step 115).

Next, a modification of the present embodiment will be described.
Here, a case where there are a plurality of versions of the functions of the multifunction machine 10 is considered. Assume that the front-end PC 30 can use only a part of the specific functions of the multifunction device 10.
Therefore, an outline of the operation in such a case will be described.
FIG. 7 is a diagram showing a system configuration for explaining the operation in this case.

In FIG. 7, the multi-function device 10 has substantially the same configuration as that shown in FIGS. However, there are two versions of the decomposer / imager 15, and these are represented by V1 and V2 in the figure.
Further, the front end PC 30 also has substantially the same configuration as that shown in FIGS. However, it is assumed that the front-end I / F 35 supports only V1 of the two versions of the decomposer / imager 15.

In such a case, in the present embodiment, the front end I / F 35 can remotely call only the V1 with respect to the decomposer / imager 15, but cannot call the V2 remotely.
Specifically, this operation can be realized as follows.
That is, in step 105 of FIG. 4, the detection unit 17 of the multifunction machine 10 receives information about the function desired to be used and its version from the front end PC 30. In step 107, in addition to the function and address, the function version is also registered in the function / address table.
In step 111 in FIG. 6, a remote call designating not only the function but also the version is accepted. Then, when executing the remote call in step 114, the interface corresponding to the version of the software component or function realizing the function is called.

As described above, in the present embodiment, the function of the MFP 10 is realized by a function that can be remotely called. This makes it possible to switch between a configuration having the front end PC 30 and a configuration not having the front end PC 30 without replacing the software of the multifunction machine 10. The functions of the front end PC 30 can be added and changed flexibly.
In addition, since the function can be called locally, a framework capable of equivalently handling device / OS / intra-process communication and communication via a network can be realized.
Further, in the present embodiment, only the function remote call from the front-end PC 30 permitted to use the functions of the multifunction machine 10 is executed. As a result, the functions of the multifunction machine can be used securely by the front-end PC 30.

It is the figure which showed the structure of the system with which embodiment of this invention is applied. It is a figure for demonstrating the outline | summary of embodiment of this invention. It is a figure for demonstrating the outline | summary of embodiment of this invention. It is the flowchart which showed the operation | movement of the detection means in embodiment of this invention. It is the figure which showed an example of the function / address table memorize | stored in embodiment of this invention. It is the flowchart which showed the operation | movement of the filter in embodiment of this invention. It is a figure for demonstrating the outline | summary at the time of considering the version of the function in embodiment of this invention.

Explanation of symbols

10: Multifunction machine, 20: Terminal device, 30 ... Front-end PC

Claims (8)

Storage means for storing functions in a distributed object environment for operating a specific function;
When a remote call of the function stored in the storage unit is received from another device, it is determined whether the other device is a specific device permitted to remotely call the function, and based on the result of the determination, A multifunction device comprising control means for controlling function calls. It further comprises detection means for detecting connection of the specific device,
The multifunction device according to claim 1, wherein the control unit limits calling of the function when the detection unit does not detect the specific device. It further comprises detection means for detecting connection of the specific device,
The multifunction device according to claim 1, wherein the control unit calls the function when the specific device detected by the detection unit is the same as the other device. It further comprises detection means for detecting connection of the specific device,
The multifunction device according to claim 1, wherein the control unit restricts calling of the function when the specific device detected by the detection unit is different from the other device. A method for controlling the operation of a multifunction machine,
Storing information of a specific device capable of operating the multifunction peripheral in a memory;
Receiving a remote call of a function in a distributed object environment for operating the multifunction machine from another device;
Determining whether information of the other device is stored in the memory;
Controlling the calling of the function based on the result of the determination. In the storing step, information on the specific device capable of operating a specific function of the multifunction device is stored,
6. The method according to claim 5, wherein in the receiving step, a remote call of the function for operating the specific function is received from the other device. In the storing step, information on the specific device capable of operating a specific version of a specific function of the multifunction device is stored,
In the receiving step, a remote call of the function for operating the specific function is received from the other device,
6. The method of claim 5, wherein the controlling step calls an interface corresponding to the specific version of the function. A program for controlling the operation of a multifunction machine,
A function of accepting a remote call of a function in a distributed object environment for operating a specific function of the multifunction device from another device;
A function of determining whether the other device is a specific device permitted to remotely call the function;
A program for realizing a function of controlling the function call based on the result of the determination.

Images