JP5104968B2 - Control in a control device connected to the network - Google Patents

Description

  The present invention relates to control in a control device connected to a network, and more particularly to a technique for providing and registering information.

  In a printing system using a network, for example, a printer is connected to a print server via a USB cable, and the print server and a client computer are connected via a network such as a LAN.

  The print server is usually provided with a database for storing various information called MIB (Management Information Base). In response to an information acquisition request from the client computer, the print server reads data indicating the content of the information from the MIB and provides the data to the client computer. Further, the print server registers data indicating the contents of the information given from the client computer in the MIB in response to the information setting request from the client computer.

  The MIB can store not only information about the print server but also information about the printer. Information about the printer is stored in the MIB when the print server obtains data indicating the contents of the information from the printer every predetermined time.

JP 2005-165524 A

  However, in the conventional technology, the print server may not be able to appropriately provide or register the information in response to an acquisition request or a setting request from a client computer. Specifically, when the print server executes processing in response to an acquisition request or a setting request from a client computer, nothing is exchanged between the print server and the printer. For this reason, in some cases, the data read from the MIB and provided to the client computer in response to a request for acquiring information about the printer is not the latest data. In addition, there is a case where data given from a client computer and registered in the MIB in response to a request for setting information related to the printer is data that is not allowed by the printer.

  Note that the above problem is common to not only a printing system including a print server but also a network system including a control device connected to a network.

  The present invention has been made to solve the above-described problems, and an object thereof is to appropriately provide and register information in a control device connected to a network.

In order to solve at least a part of the problems described above, a first device of the present invention is a control device connected to a network,
A first communication unit that communicates with a computer connected via the network;
A second communication unit for communicating with a local device connected without going through the network;
A first memory for storing data;
A data providing unit that provides data indicating the content of the target information to the computer via the first communication unit when acquisition of the target information is requested from the computer via the first communication unit; ,
With
The data providing unit includes:
If the target information is information belonging to a first group, the data indicating the content of the target information is read from the first memory, and the read data is provided to the computer,
When the target information is information belonging to a second group, data indicating the content of the target information is acquired from the local device via the second communication unit, and the acquired data is It is provided to a computer.

  In this apparatus, when the target information of the acquisition request belongs to the first group, the data read from the first memory is provided to the computer, and when the target information of the acquisition request belongs to the second group Provides data acquired from the local device to the computer, and thus can appropriately provide the target information. Specifically, when the target information belongs to the first group, it is not necessary to acquire data from the local device. When the target information belongs to the second group, the latest data is acquired from the local device. can do.

  For example, the fixed information that is not changed is information that belongs to the first group, and the information that can be changed by the local device may be information that belongs to the second group.

In the above device,
The data providing unit includes:
If the target information is information belonging to a first subgroup of the second group, the first data indicating the content of the target information is read from the first memory and the first information After supplying data to the local device, the second data indicating the content of the target information is obtained from the local device;
If the target information is information belonging to a second subgroup of the second group, the content of the target information is read from the local device without executing a read process on the first memory. The data shown may be acquired.

  In this way, before acquiring data from the local device, whether or not to supply the data read from the control device to the local device can be changed according to the target information.

  For example, if the information represented by data having a relatively small size is information belonging to the first subgroup, and the information represented by data having a relatively large size is information belonging to the second subgroup, Good.

In the above device,
The data providing unit includes:
When the second data indicating the content of the target information is acquired from the local device, the first data indicating the content of the target information in the first memory is obtained according to an instruction from the local device. It is preferable to change to the second data.

  By doing so, it is possible to update the data indicating the content of the target information stored in the first memory of the control device.

A second device of the present invention is a network device,
A control device which is the first device;
The local device;
With
The local device is
A data supply unit that supplies data indicating the content of the target information to the control device is provided.

  In this way, the local device can supply the latest data to the control device.

In the above device,
The data supply unit
A second memory for storing third data indicating the content of the target information;
The data supply unit
When the third data is newer than the first data supplied from the control device, the third data may be supplied to the data providing unit as the second data.

In the above device,
The data supply unit further instructs to store the third data as the second data in the first memory when the third data is newer than the first data. It is preferable to do.

  By doing so, it is possible to update the data indicating the content of the target information stored in the first memory of the control device.

In the above device,
The data supply unit requests the data providing unit to notify the local device when the control device receives a request to acquire the target information belonging to the second group from the computer. May be.

A third device of the present invention is a control device connected to a network,
A first communication unit that communicates with a computer connected via the network;
A second communication unit for communicating with a local device connected without going through the network;
Memory to store data,
A data registration unit for registering data indicating the content of the target information in the memory when setting of the target information is requested from the computer via the first communication unit;
With
The data registration unit
If the target information is information belonging to the first group, register data indicating the content of the target information supplied from the computer in the memory,
If the target information is information belonging to a second group, whether to register data indicating the content of the target information supplied from the computer to the local device via the second communication unit is determined. Inquiry, if the registration of the data is allowed by the local device, the data is registered in the memory.

  In this apparatus, when the target information of the setting request belongs to the first group, the data supplied from the computer is registered in the memory, and when the target information of the setting request belongs to the second group, the local device If the registration is permitted, the data supplied from the computer is registered in the memory, so that the target information can be registered appropriately. Specifically, when the target information belongs to the first group, it is not necessary to inquire of the local device whether registration is possible, and when the target information belongs to the second group, registration is permitted. Data can be registered in the memory.

  For example, the fixed information that is not changed may be information belonging to the first group, and the information related to the local device that can be set by the user may be information belonging to the second group.

In the above device,
The data registration unit
If registration of alternative data different from the data is permitted by the local device, the alternative data may be registered in the memory.

  In this way, when the registration of data indicating the contents of the target information is not allowed, the computer does not need to supply other data to the control device again.

The fourth device of the present invention is
A network device,
A control device which is the third device;
The local device;
With
The local device is
A determining unit that determines whether or not to register the data is provided in response to the inquiry from the control device.

  In this way, the control device can register appropriate data in the memory.

In the above device,
In the case where registration of the data is not permitted, the determination unit may select the alternative data and allow registration of the alternative data.

  In this way, when the registration of data indicating the contents of the target information is not allowed, the computer does not need to supply other data to the control device again.

In the above device,
The determination unit requests the data registration unit to notify the local device when the control device receives a request for setting the target information belonging to the second group from the computer. Also good.

  The present invention can be realized in various forms, and includes a control apparatus, a control method in the control apparatus, a local device, a control method in the local device, a network apparatus including the control apparatus and the local device, and the network apparatus And a computer program for realizing the functions of these methods or apparatuses, a recording medium storing the computer program, a data signal including the computer program and embodied in a carrier wave, etc. Can do.

It is explanatory drawing which shows the structure of a network system. It is explanatory drawing which shows typically the principal part of each apparatus 100,200,300 which comprises the network system of FIG. 4 is an explanatory diagram showing a group of information stored in a database data area. FIG. 5 is a flowchart illustrating a procedure of preprocessing performed between the device server 100 and the multifunction device 200. 4 is a flowchart showing a procedure of a first process executed when the device server 100 receives a scanner status information acquisition request from a client computer 300. It is explanatory drawing which shows the content of the communication data exchanged between each apparatus 100,200,300 when the process of FIG. 5 is performed. 10 is a flowchart illustrating a procedure of a second process executed when the device server 100 receives a scanner status information acquisition request from a client computer 300. FIG. It is explanatory drawing which shows the content of the communication data exchanged between each apparatus 100,200,300 when the process of FIG. 7 is performed. 6 is a flowchart illustrating a procedure of processing executed when the device server 100 receives a display panel language information setting request from a client computer 300; It is explanatory drawing which shows the content of the communication data exchanged between each apparatus 100,200,300 when the process of FIG. 9 is performed.

Next, embodiments of the present invention will be described in the following order based on examples.
A. Network system configuration:
A-1. Device server configuration:
A-2. Multi-function machine configuration:
B. Main parts of the network system:
B-1. Main parts of the device server:
B-2. Main parts of the MFP:
B-3. The main parts of the client computer:
C. Preprocessing:
D. Handling requests from clients:
D-1. First process for an acquisition request:
D-2. Second process for the acquisition request:
D-3. Processing for setting request:
D-3-1. Variation of processing for setting request:

A. Network system configuration:
FIG. 1 is an explanatory diagram showing a configuration of a network system. The network system includes a device server 100, a multifunction device 200, and a client computer (hereinafter simply referred to as “client”) 300. The device server 100 and the client 300 are connected to each other via a network NW such as a LAN. The device server 100 and the multifunction device 200 are connected to each other via a USB cable.

  In this embodiment, the device server 100 and the multifunction device 200 are stored in different housings, but may be stored in a common housing.

  Note that the device server 100 in this embodiment corresponds to the control device in the present invention, and the multifunction device 200 corresponds to a local device. The device server 100 and the multifunction device 200 correspond to a network device.

A-1. Device server configuration:
The device server 100 (FIG. 1) includes a control circuit 110, a network interface (IF) unit 192, and a USB host interface (IF) unit 198.

  The network IF unit 192 is an interface for communicating with the client 300 via the network NW.

  The USB host IF unit 198 is an interface for communicating with a local device such as the MFP 200 via a USB cable.

  The control circuit 110 includes a CPU and a memory (not shown). The control circuit 110 includes a process execution unit 112, a first communication control unit 114, and a second communication control unit 116. The functions of the process execution unit 112, the first communication control unit 114, and the second communication control unit 116 are realized by the CPU executing a computer program. The computer program is provided in a form recorded on a computer-readable recording medium such as a CD-ROM.

  The first communication control unit 114 transmits / receives communication data to / from the client 300 connected to the network via the network IF unit 192. Note that the first communication control unit 114 executes TCP and / or UDP layer processing and IP layer processing.

  The second communication control unit 116 transmits / receives communication data to / from the multi-function device 200 connected by the USB cable via the USB host IF unit 198.

  The process execution unit 112 executes various processes based on the communication data received from the first communication control unit 114. The process execution unit 112 will be further described later.

  Note that the network IF unit 192, the first communication control unit 114, and a part of the processing execution unit 112 (described later) in this embodiment correspond to the first communication unit in the present invention. The USB host IF unit 198 and the second communication control unit 116 correspond to the second communication unit.

A-2. Multi-function machine configuration:
The multifunction device 200 (FIG. 1) includes a control circuit 210, a display panel 270, a printer unit 281, a scanner unit 282, and a USB device interface (IF) unit 298.

  The USB device IF unit 298 is an interface for communicating with the device server 100 via a USB cable.

  The control circuit 210 includes a CPU and a memory (not shown). The control circuit 210 includes a process execution unit 212 and a communication control unit 216. The functions of the process execution unit 212 and the communication control unit 216 are realized by the CPU executing a computer program.

  The communication control unit 216 transmits / receives communication data to / from the device server 100 connected via the USB cable via the USB device IF unit 298. Note that the function of the communication control unit 216 is realized by a USB class driver.

  The process execution unit 212 executes various processes based on the communication data received by the communication control unit 216. For example, the process execution unit 212 controls the printer unit 281 to execute printing, or controls the scanner unit 282 to execute reading of image data. In addition, the process execution unit 212 displays characters and pictures on the display panel 270.

B. The main parts of the network system:
FIG. 2 is an explanatory diagram schematically showing the main part of each device 100, 200, 300 that constitutes the network system of FIG.

B-1. Main parts of the device server:
As shown in FIG. 2, the device server 100 includes a server module 120 and a database 130. The server module 120 and the database 130 are included in the processing execution unit 112 in the device server 100 of FIG. The server module 120 in the process execution unit 112 is included in the first communication unit in the present invention described above.

  The server module 120 receives a request given from the client computer 300 and provides a service corresponding to the request. The server module 120 is a server program that provides a service according to a specific protocol. As the specific protocol, various protocols such as the XML protocol (XMLP) and the SOAP (Simple Object Access Protocol) protocol can be used.

  The database 130 includes a database management unit 132 and a database data area 134.

  A database data area (hereinafter also referred to as “DB data area”) 134 stores various types of information. FIG. 3 is an explanatory diagram showing a group of information stored in the database data area 134. However, in FIG. 3, the item name of each information is shown. As illustrated, the DB data area 134 includes information “NWInfo” related to the device server 100 and information “DeviceInfo” related to the multifunction device 200. The information “NWInfo” regarding the device server includes information “IPAddress” indicating the IP address. Information related to the MFP “DeviceInfo” includes information “MFDName” indicating the device name of the MFP, information “MFDStatus” regarding the status (operation state) of the MFP, and information “MFDPanel” related to the display panel provided in the MFP. Is included. The information “MFDStatus” regarding the status of the multifunction device includes status information of each functional unit of the multifunction device, specifically, status information “PrinterStatus” of the printer unit 281 and status information “ScannerStatus” of the scanner unit 282. Yes. The information “MFDPanel” related to the display panel provided in the multi-function peripheral includes language information “PanelLnguage” indicating the language used for display on the display panel.

  Note that each piece of information shown in FIG. 3 is actually described in XML (eXtensible Markup Language).

  When the database management unit (hereinafter also referred to as “DB management unit”) 132 receives an acquisition request for information (for example, “ScannerStatus”) from the client 300, the database management unit 132 reads data indicating the content of the information from the DB data area 134. When a request for setting information (for example, “PanelLnguage”) is received from the client 300, data indicating the content of the information is written in the DB data area 134.

  In particular, in this embodiment, the DB management unit 132 has a function of notifying the multi-function device 200 when an information acquisition request or setting request previously set as a notification target is received from the client 300. . Specifically, the DB management unit 132 includes a notification management table 133. In the notification management table 133, notification target information and a notification method are registered in association with each other. The notification target information is information selected from the information group including each piece of information and other information shown in FIG. In this embodiment, a plurality of notification methods are prepared.

  When receiving an information acquisition request for which the first notification method is set, the DB management unit 132 reads data indicating the content of the information from the DB data area 134 and then notifies the MFP 200. . This notification includes the read data.

  When receiving an information acquisition request for which the second notification method is set, the DB management unit 132 notifies the MFP 200 without executing a read process for the DB data area 134.

  When receiving a setting request for information in which the third notification method is set, the DB management unit 132 notifies the multi-function device 200 without executing the writing process to the DB data area 134.

  Information for which the first or second notification method is set includes information related to the multifunction device and can be changed by the multifunction device. Examples of such information include printer status information “PrinterStatus” and scanner status information “ScannerStatus”.

  The information for which the third notification method is set includes information related to the multifunction peripheral and can be set (changed) by the user. Examples of such information include language information “PanelLnguage” used for the display panel 270.

  When receiving an acquisition request for information not registered in the notification management table 133, that is, information for which a notification method is not set, the DB management unit 132 reads data indicating the content of the information from the DB data area 134. . However, the DB management unit 132 does not notify the multifunction device 200. When receiving a setting request for information for which no notification method is set, the DB management unit 132 writes data indicating the content of the information in the DB data area 134. However, the DB management unit 132 does not notify the multifunction device 200. The information for which the notification method is not set includes information that is not related to the multifunction peripheral, and includes, for example, each information included in the information “NWInfo” regarding the device server 100. The information for which the notification method is not set includes fixed information that is related to the multifunction peripheral and is not changed. For example, information “MFDName” indicating the device name of the multifunction peripheral is included.

  Of the information group that is the target of the acquisition request, information for which the notification method is not set corresponds to information belonging to the first group in the present invention, and information for which the first or second notification method is set. Corresponds to information belonging to the second group. The information for which the first notification method is set corresponds to the information belonging to the first subgroup of the second group in the present invention, and the information for which the second notification method is set is the second information This corresponds to information belonging to the second subgroup of the group.

  Further, in the information group that is the target of the setting request, information for which the notification method is not set corresponds to information belonging to the first group in the present invention, and information for which the third notification method is set is This corresponds to information belonging to Group 2.

  In the present embodiment, the fourth communication method can also be set. When receiving a setting request for information in which the fourth communication method is set, the DB management unit 132 performs a writing process on the DB data area 134 and then notifies the MFP 200. This notification includes the written data. The information for which the fourth notification method is set includes, for example, information that does not affect the operation of the multifunction peripheral and can be set (changed) by the user. However, in the present embodiment, the fourth communication method is not used.

  The DB management unit 132 in this embodiment corresponds to the data providing unit and the data registration unit in the present invention.

B-2. Main parts of the MFP:
As illustrated in FIG. 2, the multi-function device 200 includes a device management unit 232 and a device data area 234. The device management unit 232 and the device data area 234 are included in the processing execution unit 212 in the multi-function device 200 of FIG.

  In the device data area 234, various types of information related to the multifunction device 200 are stored. For example, the device data area 234 stores various information included in “DeviceInfo” in FIG. 3, more specifically, status information of the functional units 281 and 282, use language information of the display panel 270, and the like. ing.

  The device management unit 232 has a function of managing the multifunction device 200. For example, the device management unit 232 acquires status information from the function units 281 and 282 every predetermined time and stores the status information in the device data area 234. In addition, the device management unit 232 reads setting values used for the operation of each unit of the multifunction device 200 from the device data area 234 and provides them to each unit.

  In particular, in this embodiment, the device management unit 232 requests the DB management unit 132 to register a notification. Specifically, the device management unit 232 includes a notification request table 233, in which notification target information and a notification method are registered in association with each other. The device management unit 232 supplies the contents of the notification request table 233 to the DB management unit 132 of the device server 100. Thereby, the DB management unit 132 can create the notification management table 133 described above.

  Further, the device management unit 232 receives the notification from the DB management unit 132 of the device server 100 and responds to the notification. At this time, the device management unit 232 reads data indicating the content of the target information of the acquisition request from the device data area 234 and returns the data to the DB management unit 132. In addition, the device management unit 232 determines whether data indicating the content of the target information of the setting request can be registered, and writes the data in the device data area 234 when registration is possible.

  Note that the device management unit 232 in this embodiment corresponds to the data supply unit and the determination unit in the present invention.

B-3. The main parts of the client computer:
As shown in FIG. 2, the client 300 includes a client module 320. The client module 320 is provided corresponding to the server module 120 of the device server 100. Specifically, the client module 320 is a client program that uses the same protocol as the server module 120.

C. Preprocessing:
FIG. 4 is a flowchart illustrating a pre-processing procedure performed between the device server 100 and the multifunction device 200. This process is executed, for example, when the multifunction device 200 is turned on or when the multifunction device 200 is reset.

  In step S102, the device management unit 232 of the multifunction device 200 requests registration of notification regarding specific information. Specifically, the device management unit 232 requests the device server 100 to notify the multifunction device when the device server 100 receives an acquisition request for specific information from the client 300. Further, the device management unit 232 requests the device server 100 to notify the multifunction device when the device server 100 receives a specific information setting request from the client 300. In practice, in step S102, the device management unit 232 supplies the contents of the notification request table 233 to the device server 100.

  In step S104, the DB management unit 132 of the device server 100 registers a notification regarding specific information. Specifically, the DB management unit 132 registers the contents of the notification request table 233 received in step S102 in the notification management table 133.

  Accordingly, when receiving an information acquisition request or setting request from the client 300, the device server 100 can determine whether the information is notification target information with reference to the notification management table 133. At the same time, the MFP 200 can be notified according to the notification method associated with the notification target information.

D. Handling requests from clients:
D-1. First process for an acquisition request:
FIG. 5 is a flowchart illustrating a procedure of a first process executed when the device server 100 receives a scanner status information acquisition request from the client computer 300. FIG. 6 is an explanatory diagram showing the contents of communication data exchanged between the devices 100, 200, and 300 when the processing of FIG. 5 is executed.

  5 and 6 will be described assuming that the first notification method is registered for the scanner status information by the preprocessing of FIG.

  In step S112 (FIG. 5), the client 300 requests acquisition of scanner status information. Specifically, when the user of the client 300 instructs to acquire the scanner status information via the application program execution screen, the client module 320 issues a scanner status information acquisition request. At this time, the client 300 transmits the first communication data CD1 to the device server 100.

  FIG. 6A shows the contents of the first communication data CD1. As shown in the figure, the communication data CD1 includes a description of <ScannerStatus />, and the acquisition of scanner status information is requested.

  In step S <b> 114, the device server 100 reads data indicating the contents of the scanner status information stored in the DB data area 134 and notifies the multifunction device 200. Specifically, when receiving the first communication data CD1 from the client 300, the server module 120 of the device server 100 instructs the DB management unit 132 to prepare data indicating the contents of the scanner status information.

  The DB management unit 132 refers to the notification management table 133 to determine whether the scanner status information is notification target information. Whether or not the scanner status information is notification target information is determined by whether or not the scanner status information is registered in the notification management table 133. Here, it is assumed that scanner status information is registered in the notification management table 133 and the first notification method is set corresponding to the scanner status information. For this reason, the DB management unit 132 determines that the scanner status information is notification target information, and performs notification according to the first notification method. Specifically, the DB management unit 132 first reads data indicating the content of the scanner status information stored in the DB data area 134 (hereinafter also referred to as “first data”). Then, the DB management unit 132 supplies the first data to the multifunction device 200 and notifies the multifunction device 200. At this time, the DB management unit 132 transmits the second communication data CD2 to the multifunction device 200.

  FIG. 6B shows the contents of the second communication data CD2. As illustrated, the communication data CD2 includes a description of <ScannerStatus> AAA </ ScannerStatus>. “AAA” is first data indicating the contents of the scanner status information read from the DB data area 134.

  Note that, as shown in FIG. 6B, the second communication data CD2 is described in XML (eXtensible Markup Language). Two tags <ScannerStatus> and </ ScannerStatus> representing scanner status information are sandwiched between two tags <MPDStatus> and </ MPDStatus> representing the status information of the multifunction peripheral, and the two tags <MPDStatus>, </ MPDStatus> is sandwiched between two tags <DeviceInfo> and </ DeviceInfo> representing information about the multifunction peripheral.

  In step S116, the multifunction device 200 includes first data indicating the content of the scanner status information supplied from the device server 100 and data indicating the content of the scanner status information stored in the multifunction device 200 (hereinafter referred to as “second”). Or “data”) is selected. Then, the multifunction device 200 supplies the selected one data (hereinafter also referred to as “selected data”) to the device server 100, and responds to the notification in step S114.

  Specifically, when receiving the second communication data CD2 from the device server 100, the device management unit 232 of the multi-function device 200 receives the first data indicating the content of the scanner status information included in the second communication data CD2. The time stamp is compared with the time stamp of the second data indicating the content of the scanner status information stored in the device data area 234 of the multifunction device 200. The time stamp indicates the data update date. If the time stamp of the second data indicates the same time as the time stamp of the first data (or a time before the time stamp of the first data), the device management unit 232 selects the first data To do. On the other hand, when the time stamp of the second data indicates a time more recent than the time stamp of the first data, the device management unit 232 selects the second data. When comparing the time stamps, actual data representing the second data is not read from the device data area 234. The time stamp of the second data is obtained by referring to the directory information of the file system that stores the second data. When the second data is selected, the device management unit 232 reads the second data (actual data) from the device data area 234. When the device management unit 232 selects one of the two data, the device management unit 232 transmits the third communication data CD3 including the selection data to the device server 100.

  FIGS. 6C-1 and 6C-2 respectively show the contents of the third communication data CD3. The communication data CD3 in FIG. 6C-1 is issued when the time stamp of the second data indicates the same time as the time stamp of the first data (or a time earlier than the time stamp of the first data). <ScannerStatus> AAA </ ScannerStatus> is included. “AAA” is the first data. The communication data CD3 in FIG. 6C-2 is issued when the time stamp of the second data indicates a time more recent than the time stamp of the first data, and the description of <ScannerStatus> BBB </ ScannerStatus> include. “BBB” is the second data.

  Note that the communication data CD3 shown in FIGS. 6C-1 and C-2 is created using the communication data CD2 shown in FIG. 6B. The communication data CD3 in FIG. 6C-1 includes the same content as the communication data CD2 in FIG. The communication data CD3 in FIG. 6C-2 includes almost the same content as the communication data CD2 in FIG. 6B, but is described between two tags <ScannerStatus> and </ ScannerStatus>. Has been changed.

  In addition, the communication data CD3 in FIG. 6C-2 includes a description of <DeviceInfo set = "1">. “Set =“ 1 ”” should store the data (“BBB”) described in the communication data CD3 as data indicating the contents of the scanner status information stored in the DB data area 134 of the device server 100. It means that. As can be seen from this description, in this embodiment, when returning the second data to the device server 100, the device management unit 232 instructs the device server 100 to store the second data. .

  In step S118, the device server 100 responds to the acquisition request received from the client 300 in step S112. Specifically, the DB management unit 132 of the device server 100 provides selection data (that is, first data or second data) included in the received third communication data CD3 to the server module 120. Then, the server module 120 transmits the fourth communication data CD4 including the selection data to the client 300.

  When the DB management unit 132 receives the third communication data CD3 including the save instruction “set =“ 1 ”” illustrated in FIG. 6C-2, the DB management unit 132 stores the third communication data CD3 in the DB data area 134. The first data (“AAA”) indicating the content of the scanner status information is changed to the second data (“BBB”) included in the third communication data CD3. Thereby, the scanner status information in the DB data area 134 is updated.

  FIG. 6D shows the contents of the fourth communication data CD4. As illustrated, the fourth communication data CD4 includes a description of <ScannerStatus> CCC </ ScannerStatus>. “CCC” is selection data selected in step S116 and included in the third communication data CD3, and indicates first data (“AAA”) or second data (“BBB”).

  In step S120, the client module 320 of the client 300 receives the fourth communication data CD4 from the device server 100. The fourth communication data CD4 includes data indicating the contents of the scanner status information. As a result, the client 300 can acquire the scanner status information from the device server 100.

D-2. Second process for the acquisition request:
FIG. 7 is a flowchart showing the procedure of the second process executed when the device server 100 receives a scanner status information acquisition request from the client computer 300. FIG. 8 is an explanatory diagram showing the contents of communication data exchanged between the devices 100, 200, and 300 when the processing of FIG. 7 is executed.

  7 and 8 will be described assuming that the second notification method is registered for the scanner status information by the preprocessing of FIG.

  FIG. 7 is substantially the same as FIG. 5, but steps S114a, S116a, and S118a are changed. FIG. 8 is substantially the same as FIG. 6, but FIGS. 8B to 8D are changed.

  In step S <b> 114 a, the device server 100 notifies the multifunction device 200 without executing read processing for the DB data area 134. Specifically, when the server module 120 of the device server 100 receives the first communication data CD1 (FIG. 8A) from the client 300, the server module 120 instructs the DB management unit 132 to prepare scanner status information. .

  The DB management unit 132 refers to the notification management table 133, determines that the scanner status information is notification target information, and performs notification according to the second notification method. Specifically, the DB management unit 132 performs notification to the multi-function device 200 without executing a read process for the DB data area 134. At this time, the DB management unit 132 transmits the second communication data CD2a to the multifunction device 200.

  FIG. 8B shows the contents of the second communication data CD2a. FIG. 8B is almost the same as FIG. 6B, but no data is described between the two tags <ScannerStatus> and </ ScannerStatus>. This is because the reading process for the DB data area 134 is not executed.

  In step S116a, the MFP 200 reads the second data, supplies the second data to the device server 100, and responds to the notification in step S114a. Specifically, when the device management unit 232 of the multifunction device 200 receives the second communication data CD2a from the device server 100, the device management unit 232 reads the second data indicating the content of the scanner status information stored in the device data area 234. . Then, the device management unit 232 transmits the third communication data CD3a including the second data to the device server 100.

  FIG. 8C shows the contents of the third communication data CD3a. FIG. 8C is substantially the same as FIG. 6C-2, and the third communication data CD3a includes a description of <ScannerStatus> BBB </ ScannerStatus>. “BBB” is the second data.

  In step S118a, the device server 100 responds to the acquisition request received from the client 300 in step S112. Specifically, the DB management unit 132 of the device server 100 provides the server module 120 with the second data included in the received third communication data CD3a. Then, the server module 120 transmits the fourth communication data CD4 including the second data to the client 300.

  Further, as shown in FIG. 8C, since the third communication data CD3a includes the save instruction “set =“ 1 ””, the DB management unit 132 is stored in the DB data area 134. The first data indicating the contents of the scanner status information is changed to the second data (“BBB”) included in the third communication data CD3a. Thereby, the scanner status information in the DB data area 134 is updated.

  Note that the communication data CD3a in FIG. 8C includes a description of <DeviceInfo set = "1">, similar to the communication data CD3 in FIG. 6C-2. , <DeviceInfo set = "0"> or <DeviceInfo> may be included. In this case, in step S118a, the updating process of the scanner status information in the DB data area 134 is not executed.

  FIG. 8D shows the contents of the fourth communication data CD4a. As illustrated, the fourth communication data CD4 includes a description of <ScannerStatus> BBB </ ScannerStatus>. “BBB” is the second data read from the multifunction device 200 in step S116a.

  In step S120, as described above, the client 300 acquires the scanner status information from the device server 100.

  In FIGS. 7 and 8, the case where the second notification method is set for the scanner status information has been described. When the second notification method is set for the target information of the acquisition request, the read processing is not executed for the DB data area 134 of the device server 100, so the target information is stored in the DB data area 134. The data indicating the contents may not be stored. In this way, the memory capacity required for the DB data area 134 of the device server 100 can be reduced. As can be seen from this description, it is preferable that the second notification method is set particularly for information having a relatively large data size. Examples of such information include image information (scanner image information) acquired by the scanner unit 282.

  5 and 7 describe the processing when an information acquisition request for which the first notification method or the second notification method is set is generated. When receiving an acquisition request for information for which no notification method is set, the device server 100 reads data indicating the content of the information from the DB data area 134 and transmits communication data including the data to the client 300. That is, in this case, communication data is not exchanged between the device server 100 and the multifunction device 200.

  As described above, in this embodiment, when the device server 100 receives from the client 300 an acquisition request for the first type of information for which the notification method is not set, the device server 100 reads the request from the DB data area 134. When the second data acquisition request for which the first or second notification method is set is received, the data acquired from the MFP 200 is provided to the client 300. For this reason, the device server 100 can appropriately execute the provision of the target information to the client 300. Specifically, when the device server 100 receives the first type information acquisition request, the device server 100 does not need to acquire data from the multifunction device 200, and when the second type information acquisition request is received. Can acquire the latest data from the multifunction device 200.

  In the prior art, in order to provide the client with information related to the printer, the print server needs to acquire data indicating the content of the information from the printer at predetermined time intervals. That is, the print server needs to acquire data from the printer even when it has not received an acquisition request from the client. On the other hand, in the present embodiment, the device server 100 acquires data indicating the content of the notification target information from the multifunction device 200 only when receiving a notification target information acquisition request from the client 300. Therefore, in this embodiment, the device server 100 can efficiently provide information in response to an information acquisition request from the client 300.

  In this embodiment, when the device server 100 receives from the client 300 an acquisition request for the second type of information in which the first notification method is set, the data read from the DB data area 134 When the second type information acquisition request for which the second notification method is set is received, the read processing for the DB data area 134 is not executed, so the data size and other targets The contents of the notification process can be changed according to the characteristics of the information.

D-3. Processing for setting request:
FIG. 9 is a flowchart showing a procedure of processing executed when the device server 100 receives a setting request for language information used on the display panel from the client computer 300. FIG. 10 is an explanatory diagram showing the contents of communication data exchanged between the devices 100, 200, and 300 when the processing of FIG. 9 is executed.

  9 and 10 will be described assuming that the third notification method is registered for the language information used on the display panel by the preprocessing of FIG.

  In step S152 (FIG. 9), the client 300 requests setting of language information used on the display panel. Specifically, when the user of the client 300 instructs to set the language used for the display panel to a specific language via the application program execution screen, the client module 320 issues a request for setting the language used for the display panel. Issue. At this time, the client 300 transmits the first communication data CD6 to the device server 100.

  FIG. 10A shows the contents of the first communication data CD6. As shown in the figure, the communication data CD6 includes a description of <PanelLnguage> en </ PanelLnguage>, and the setting of the language information used for the display panel is requested. In FIG. 10A, English (“en”) is designated as the language to be set.

  In step S <b> 154, the device server 100 performs notification to the multi-function device 200 without executing write processing for the DB data area 134. Specifically, when the server module 120 of the device server 100 receives the first communication data CD6 from the client 300, the language used by the client 300 as the language used by the DB management unit 132 (hereinafter also referred to as “designated language”). To be set).

  The DB management unit 132 refers to the notification management table 133, determines that the language information used on the display panel is notification target information, and performs notification according to the third notification method. Specifically, the DB management unit 132 notifies the multi-function device 200 without executing the writing process in the DB data area 134. At this time, the DB management unit 132 transmits the second communication data CD7 to the multifunction device 200.

  FIG. 10B shows the contents of the second communication data CD7. As illustrated, the second communication data CD2 includes a description of <PanelLnguage> en </ PanelLnguage>. “En” is data indicating a designated language designated by the client 300.

  In step S156, the multi-function device 200 determines whether or not the language used can be changed to the designated language, returns the determination result to the device server 100, and responds to the notification in step S154.

  Specifically, when the device management unit 232 of the multifunction device 200 receives the second communication data CD7 from the device server 100, the designated language (“en”) included in the second communication data CD7 is registered (used). Determine if it is a possible language. This determination is made with reference to a language list (not shown) stored in the device data area 234. One or more languages that can be used on the display panel 270 are registered in the language list. The device management unit 232 refers to the language list and determines whether or not the specified language is a language that can be registered (used) depending on whether or not the specified language (“en”) is registered in the language list. Judging. When it is determined that the designated language can be registered, the device management unit 232 transmits the third communication data CD8 including the designated language to the device server 100. On the other hand, when it is determined that the designated language cannot be registered, the device management unit 232 transmits the third communication data CD8 not including the designated language to the device server 100.

  FIGS. 10C-1 and 10C-2 respectively show the contents of the third communication data CD8. The communication data CD8 in FIG. 10C-1 is issued when it is determined that the specified language can be registered, and includes a description of <PanelLnguage> en </ PanelLnguage>. Between the two tags <PanelLnguage> and </ PanelLnguage>, data “en” indicating the specified language is described. Communication data CD8 in FIG. 10C-2 is issued when it is determined that the designated language cannot be set, and includes a description of <PanelLnguage> </ PanelLnguage>. Between the two tags <PanelLnguage>, </ PanelLnguage>, data indicating a language is not described.

  Further, the communication data CD8 in FIG. 10C-1 includes a description of <DeviceInfo set = "1">. “Set =“ 1 ”” should store the data (“en”) described in the communication data CD8 as data indicating the contents of the language information used stored in the DB data area 134 of the device server 100. It means that. As can be understood from this description, in this embodiment, the device management unit 232 instructs the device server 100 to save the specified language when the language used on the display panel can be changed to the specified language. To do.

  In step S158, the device server 100 responds to the setting request received from the client 300 in step S152. Specifically, the DB management unit 132 of the device server 100 gives the result (success or failure) to the setting request to the server module 120 based on the third communication data CD8. Note that, as shown in FIG. 10C-1, the DB management unit 132 determines success when the specified language is sandwiched between the two tags <PanelLnguage> and </ PanelLnguage>. As shown in (C-2), if the specified language is not sandwiched between the two tags <PanelLnguage> and </ PanelLnguage>, it is determined as a failure. Then, the server module 120 transmits the fourth communication data CD9 including the result to the client 300.

  Further, when receiving the third communication data CD8 including the save instruction “set =“ 1 ”” illustrated in FIG. 10C-1, the DB management unit 132 is stored in the DB data area 134. Data indicating the content of the language information used on the display panel (for example, “jp” indicating Japanese) is changed to data (“en”) included in the third communication data CD8. Thereby, the language information used for the display panel in the DB data area 134 is updated.

  In step S160, the client module 320 of the client 300 receives the fourth communication data CD9 from the device server 100 and receives a result for the setting request.

  In FIG. 9 and FIG. 10, the processing when the information setting request for which the third notification method is set has been described has been described. When the device server 100 receives a request for setting information for which the notification method is not set, the device server 100 writes data indicating the content of the information in the DB data area 134 and transmits communication data including a result (success or failure) to the client 300. Send to. That is, in this case, communication data is not exchanged between the device server 100 and the multifunction device 200.

  As described above, in this embodiment, the device server 100 registers data in the DB data area 134 when receiving a setting request from the client 300 for the first type of information for which the notification method is not set. When a request for setting the second type of information for which the third notification method is set is received, after inquiring whether the registration can be made to the multifunction device 200, the DB is registered in the DB data area 134. Registration of target information in the data area 134 can be appropriately executed. Specifically, when the device server 100 receives the first type information setting request, the device server 100 does not need to inquire whether the registration is possible or not, and receives the second type information setting request. Can be registered in the DB data area 134.

D-3-1. Variation of processing for setting request:
As described in step S156, in the present embodiment, when the designated language is not a language that can be registered (used), registration of the designated language is rejected. However, instead of this, when the designated language is not a language that can be registered (used), registration of an alternative language may be allowed. For example, it is assumed that the client 300 requests that the language used for the display panel be set to French, and that French is not a language that can be registered (used). In this case, the device management unit 232 may allow registration of an alternative language (for example, English) instead of the designated language (French) as the language used. As an alternative language, a language that is highly likely to be understood by the user may be prepared in advance.

  Further, in this embodiment, the case where the target information of the setting request is the language information used for the display panel has been described. However, the registration of the alternative data is parameter information in which the target information of the setting request is represented by a numerical value. It is suitable for the case. Specifically, when setting of specific parameter information is requested by the client 300 and a value that cannot be registered (used) is specified as a parameter value, registration of an alternative value within a range that can be registered (used) Is acceptable. For example, when the specified value is a value (for example, 511) that exceeds a registerable range (for example, 0 to 255), the maximum value (for example, 255) of the range may be registered as an alternative value.

  As described above, the device management unit 232 may permit registration of alternative data when registration of data indicating the content of the target information of the setting request given from the client 300 is not permitted. In this case, the device management unit 232 transmits communication data including alternative data to the device server 100. Then, the DB management unit 132 registers the substitute data in the DB data area 134, and the server module 120 transmits communication data indicating that the substitute data is registered to the client 300. In this way, when the substitute data is registered, there is an advantage that the client 300 does not need to supply other specified data to the device server 100 again when registration of the specified data supplied from the client is not permitted. is there.

  The present invention is not limited to the above-described examples and embodiments, and can be implemented in various modes without departing from the gist thereof. For example, the following modifications are possible.

(1) In the above embodiment, the notification target information and the notification method are set in the device server 100 by executing the preprocessing shown in FIG. May be set in the device server 100 by the administrator of the network system.

  In the above embodiment, the notification method is determined by the DB management unit 132 referring to the notification management table 133. Alternatively, the notification method may be designated for each piece of information from the client. .

  Generally, the presence / absence of notification to the local device may be changed depending on whether the target information of the acquisition request or setting request is the notification target information.

(2) In the above embodiment, the multifunction device 200 is used as a local device, and the multifunction device 200 includes the printer unit 281 and the scanner unit 282. However, instead of or together with this, a storage device is provided. Other functional units such as a copying unit and a facsimile unit may be provided.

  In the above-described embodiment, a multifunction peripheral is used as a local device. Alternatively, other local devices such as a printer, a scanner, a storage device, and a facsimile may be used.

(3) In the above-described embodiment, one local device is connected to the device server 100, but a plurality of local devices may be connected instead. In this case, the contents of the plurality of notification request tables 233 supplied from each local device may be registered in the notification management table 133 of the device server 100 for each local device.

  When a plurality of local devices are connected to the device server 100, a plurality of local devices may be connected to the device server 100 in parallel, or a plurality of local devices may be connected to the device server 100 in series. It may be connected. When connected in series, communication data may be exchanged between the device server and the second local device far from the device server via the first local device close to the device server.

(4) In the above embodiment, a part of the configuration realized by hardware may be replaced with software, and conversely, a part of the configuration realized by software may be replaced with hardware. Also good.

DESCRIPTION OF SYMBOLS 100 ... Device server 110 ... Control circuit 112 ... Processing execution part 114 ... 1st communication control part 116 ... 2nd communication control part 120 ... Server module 130 ... Database 132 ... Database management part 133 ... Notification management table 134 ... Database data Area 192 ... Network IF section 198 ... USB host IF section 200 ... MFP 210 ... Control circuit 212 ... Processing execution section 216 ... Communication control section 232 ... Device management section 233 ... Notification request table 234 ... Device data area 270 ... Display panel 281 ... Printer unit 282 ... Scanner unit 298 ... USB device IF unit 300 ... Client computer 320 ... Client module NW ... Network

Claims (6)

A control device connected to a network,
A first communication unit that communicates with a computer connected via the network;
A second communication unit for communicating with a local device connected without going through the network;
Memory to store data,
A data registration unit for registering data indicating the content of the target information in the memory when setting of the target information is requested from the computer via the first communication unit;
With
The data registration unit
If the target information is information belonging to the first group, register data indicating the content of the target information supplied from the computer in the memory,
If the target information is information belonging to a second group, whether to register data indicating the content of the target information supplied from the computer to the local device via the second communication unit is determined. Query, if the registration of the data is allowed by the local device, register the data in the memory ,
When the local device permits registration of alternative data different from the data, the control device registers the alternative data in the memory . A network device,
A control device according to claim 1 Symbol placement,
The local device;
With
The local device is
A network device comprising: a determination unit that determines whether or not to register the data in response to the inquiry from the control device. A network device,
A control device according to claim 1 ;
The local device;
With
The local device is
In response to the inquiry from the control device, comprising a determination unit for determining whether to register the data,
When the determination unit does not permit registration of the data, the determination unit selects the alternative data and permits registration of the alternative data. The network device according to claim 2 or 3 , wherein
The determination unit is configured to request the data registration unit to notify the local device when the control device receives a request for setting the target information belonging to the second group from the computer. . A control apparatus comprising: a first communication unit that communicates with a computer connected via a network; a second communication unit that communicates with a local device connected without via the network; and a memory that stores data. A control method executed by
A step of registering data indicating the content of the target information in the memory when setting of the target information is requested from the computer via the first communication unit;
The registration process includes:
When the target information is information belonging to a first group, registering data indicating the content of the target information supplied from the computer in the memory;
When the target information is information belonging to a second group, the local device is inquired of whether registration of data indicating the content of the target information supplied from the computer is possible via the second communication unit. Registering the data in the memory when registration of the data is allowed by the local device;
And registering the alternative data in the memory when registration of alternative data different from the data is allowed by the local device . A control apparatus comprising: a first communication unit that communicates with a computer connected via a network; a second communication unit that communicates with a local device connected without via the network; and a memory that stores data. A computer program for causing a computer to execute control,
When setting of target information is requested from the computer via the first communication unit, the control device realizes a function of registering data indicating the content of the target information in the memory,
The registration function
A function of registering data indicating the content of the target information supplied from the computer in the memory when the target information is information belonging to a first group;
When the target information is information belonging to a second group, the local device is inquired of whether registration of data indicating the content of the target information supplied from the computer is possible via the second communication unit. A function of registering the data in the memory when registration of the data is permitted by the local device;
And a function of registering the substitute data in the memory when registration of substitute data different from the data is permitted by the local device .

Images