JP4261742B2 - Device, network system, job processing method, job monitoring method, and computer-readable storage medium - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a device, a network system, a job processing method, a job monitoring method, and a computer-readable storage medium, and in particular, searches for a device on a network and makes it easy for a user to find the search device and its position information. Therefore, it is suitable for use in displaying and outputting easily.
[0002]
[Prior art]
Conventionally, for example, a method called a directory service has been provided as a method for efficiently discovering and using various resources (devices such as printers, server devices, and scanners) connected to a network. Yes.
This directory service has a function of a telephone directory related to the network, and stores various information.
[0003]
As a specific example of the directory system using the directory service, there is, for example, LDAP (Lightweight Directory Access Protocol). The regulation of LDAP is described in “RFC (Request For Commets) 1777” which is a standard specification issued by IETF (Internet Engineering Task Face).
[0004]
By searching for devices connected on the network by the directory service as described above, for example, a list of addresses on the network (address list) of devices available on the network can be obtained.
[0005]
[Problems to be solved by the invention]
However, in the address list obtained by the conventional directory service as described above, the position of an available device cannot be obtained in an easily recognizable form.
[0006]
For example, when searching for a printer on the network, “Where is the closest printer to my location on my floor?” Or “Which printer in the building can output a color image?” Although it has been desired to notify the user of the device's hierarchical location information such as “no?” In an easy-to-understand manner, this has not been realized in the past.
In addition, when the information processing device on the network requests the printer to execute a job such as printing, “Which printer did you request to print” or “Your requested printing has been completed successfully. It has been desired to notify the user of information such as “whether or not an error such as a jam or out of paper has occurred”, but this has not been realized in the past.
[0007]
Therefore, the present invention is made to eliminate the above-described drawbacks. When a job is requested to the device together with a desired device position, information such as the status of the job is sent to the user. The purpose is to be able to provide it in an easily recognizable form.
[0008]
[Means for Solving the Problems]
The device of the present invention is a device for processing a job requested via a network, and a receiving means for receiving a job transmitted from an information processing apparatus on the network, and an event for the job occurs. And transmitting means for transmitting to the information processing apparatus, the hierarchical position information representing its own position and event information indicating the event.
[0009]
A network system according to the present invention is a network system including at least a device that processes a job requested via a network and an information processing apparatus that monitors the requested job. Receiving means for receiving a job transmitted from the server, hierarchical position information hierarchically representing its own position and event information indicating the event in response to the occurrence of an event for the job, the information processing apparatus Transmitting information to the device, the information processing apparatus is information transmitted from the device in response to occurrence of an event for the job, and transmission means for transmitting a job to the device, Reception of receiving hierarchical location information hierarchically representing the location of the device and event information indicating the event. And means, based on the received hierarchical location information by said receiving means, characterized in that it comprises a display means for displaying the event that the event information indicates.
[0010]
The job processing method of the present invention is a job processing method for processing a job requested via a network, the receiving step for receiving a job transmitted from an information processing apparatus on the network, and an event for the job And a transmission step of transmitting the event information indicating the event to the information processing apparatus in a hierarchical manner and the event information indicating the event.
[0011]
The job monitoring method of the present invention is a job monitoring method for monitoring a job requested via a network, and includes a first transmission step of transmitting a job to a device on the network, and the first transmission step. A first reception step for receiving a transmitted job, and hierarchical position information hierarchically representing its own position in response to occurrence of an event for the job received by the first reception step; The event information indicating the event is On the network A second transmission step for transmitting to the information processing apparatus, and before the transmission by the second transmission step. Record A second receiving step for receiving the hierarchical position information and the event information; and a display step for displaying an event indicated by the event information based on the hierarchical position information received by the second receiving step. It is characterized by including.
[0012]
The computer-readable storage medium of the present invention is a computer-readable storage medium that stores a computer program for causing a computer to execute a job requested via a network, and the computer program includes: A receiving step for receiving a job transmitted from an information processing apparatus on the network, and hierarchical position information representing the position of the job hierarchically in response to the occurrence of an event for the job, and the event A transmission step of transmitting event information to the information processing apparatus is caused to be executed by a computer.
[0032]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0033]
The present invention is applied to, for example, a device search system as shown in FIG.
The device search system of the present embodiment has a configuration in which the client device 20, the device 30, and the server device 10 are arranged on the network 40 as shown in FIG.
[0034]
The client device 20 includes, for example, a general-purpose computer, and includes a search request module 21 and a display module 22.
The search request module 21 transmits a desired device search condition to the server device 10 and receives the result. The search result received by the search request module 21 is displayed visually.
[0035]
The server apparatus 10 has a function as a directory server having a database 11 that manages attribute information of the devices 30 on the network 40.
In the database 11, identification information of the device 30 on the network 40 and information on various attributes of the device 30 are registered.
[0036]
The server device 10 includes a search module 12 and an attribute registration module 13.
Based on the device search condition received from the client apparatus 20, the search module 12 searches the database 11 for a device that matches the condition, and transmits the search result to the client apparatus 20.
The attribute registration module 13 receives device attributes from the device 30 and registers them in the database 111.
[0037]
The device 30 has a function for providing various services to the client device 20 and the like, and is, for example, a scanner, a printer, or a facsimile.
The device 30 includes a device attribute transmission module 31. The device attribute transmission module 31 transmits the attribute information of the device 30 itself to the server apparatus 10 and makes a registration request to the database 11.
[0038]
In FIG. 1, for the sake of simplicity, the minimum unit configuration of the device search system is shown. In other words, FIG. 1 illustrates a configuration in which one client device 20 and each device 30 are connected to the network 40, but the number of connections is not limited, and each of the plurality of client devices 20 is connected. The device 30 may be connected to the network 40.
Similarly, the server device 10 may be configured to connect a plurality of server devices 10 to the network 40.
[0039]
FIG. 2 shows an example of the configuration of a network system in which the device search system of this embodiment can operate.
[0040]
In FIG. 2, “101” indicates a color printer, “102” indicates an MFP, “103” and “104” indicate monochrome printers, and “105” indicates a scanner.
These devices 101 to 105 (corresponding to the device 30 in FIG. 1 above, hereinafter also referred to as “network device”) are connected to a network 100 (corresponding to the network 40 in FIG. 1 above) such as a LAN.
[0041]
The MFP (Multi Function Peripheral) is a copier, but can also be used as a network printer. Hereinafter, it is also referred to as a “multifunctional copier”.
[0042]
“111” and “113” are a desktop personal computer (hereinafter also referred to as “desktop PC”) and a notebook personal computer (hereinafter also referred to as “notebook PC”), respectively.
These PCs 111 and 113 are PCs that can execute the network client program of the present embodiment, and are connected to the network 100 as client devices (corresponding to the client device 20 in FIG. 1 described above). In addition to a function of issuing inquiry information (device search inquiry information) regarding a device that satisfies a desired condition to a server device connected on the network 100, the server apparatus also has a display function of displaying the search result of the device.
[0043]
“112” is a PC that can execute the network server program of the present embodiment, and is connected to the network 100 as a server device (corresponding to the server device 10 in FIG. 1).
For this reason, the server device 112 receives various functions related to the network devices 101 to 105 and device search inquiries from the client devices 111 or 113 connected to the network 100, which will be described in detail later. It has a function to return a result.
[0044]
In the network system according to the present embodiment as described above, the color printer 101, the multi-function copier 102, the monochrome printer 103, the client device 111, and the server device 112 among the network devices 101 to 105 are described later. A firewall 120 is installed on the second floor.
Of the network devices 101 to 105, the monochrome printer 104 and the scanner 105 are installed on the first floor.
The notebook PC 113 is currently installed on the first floor, but may be removed from the network 100 on the first floor and moved to the second floor.
[0045]
A network 100 that interconnects devices installed on the first floor and the second floor is connected to the Internet 130 via a firewall 120, and is further connected to another network 140 via the Internet 130. Are also connected.
[0046]
FIG. 3 shows an internal configuration of an arbitrary personal computer 200 (hereinafter simply referred to as “PC 200”).
The desktop PC 111, notebook PC 113, server terminal device 112, etc. shown in FIG. 2 have the functions of the PC 200 shown in FIG.
[0047]
Specifically, the PC 200 is configured to run a network client program (client device software) or a network server program (server device software).
In the following description, client device software and server device software are collectively referred to as “network device terminal device search software”.
[0048]
In the PC 200, the CPU 202 is connected to the system bus 201 by executing network device search software stored in the ROM 203 or the hard disk (HD) 211 or network device search software supplied from the floppy disk drive (FD) 212. The components 203 to 213 are collectively controlled.
[0049]
The RAM 204 functions as a main memory or work area for the CPU 202. A keyboard controller (KBC) 205 controls an instruction input from a keyboard (KB) 209 or a pointing device (not shown).
A controller (CRTC) 206 controls display on a CRT display (CRT) 210.
[0050]
A disk controller (DKC) 207 controls access to a hard disk (HD) 211 and a floppy disk controller (FD) 212 that store a boot program, various applications, edit files, user files, a network management program, and the like.
[0051]
A network interface card (NIC) 208 is used to exchange data with a network printer, another network device, or another PC via the LAN 220 in both directions.
[0052]
The mouse controller (MC) 213 controls the mouse (MS) 214.
[0053]
In FIG. 3, the LAN 220 corresponds to the LAN 100 shown in FIG.
[0054]
FIG. 4 is a diagram for explaining hierarchical position information for expressing the position of a device on the LAN 100 in the network system of FIG.
In this embodiment, the data structure of the hierarchical position information is a hierarchical structure, and more detailed position information is specified from the upper layer to the lower layer.
Therefore, the user may specify a desired hierarchy according to the use date.
[0055]
For example, in FIG. 4 above, the hierarchical location information of “LBP1110” indicated by “309” in the drawing is (C: JP (301), O: ABC Trading (302), BR: Tokyo Branch (303), OP = extended (304), Bu = M building (305), FL = 2F (306), BL = 2-1 (307), DV = prenter (308)). In this case, the map (map) is indicated as “10X + 10Y”.
[0056]
Further, each entry will be described. “C” indicates country information (“JP” indicates “Japan”, “US” indicates “USA”, etc.), and “O” indicates organization information (“ABC Trading”, “BR” indicates information such as a branch or branch (“Tokyo branch”, “Osaka branch”, etc., hereinafter referred to as “branch information”).
“BU” indicates building information indicating a building (“AA building”, “BB building”, etc.), “FL” indicates floor information indicating the number of floors (“1F”, “2F”, etc.), “BL” "" Indicates block information indicating a block on the floor ("1-1", "2-1", etc.), "DV" indicates a device ("printer", "MFP", etc.), and "NM" indicates a device name. ("LBP1110", "LBP3310", etc.).
[0057]
Also, a layout bitmap, which is image data that visually displays an arrangement layout, is prepared corresponding to the block information “BL”, and “MAP” in FIG. 4 indicates coordinate information on the map. .
[0058]
Furthermore, “OP” indicates that option information, that is, information on the “BU” hierarchy, the “FL” hierarchy, and the “BL” hierarchy is included (extend-extension).
It should be noted that the option information may be set in another hierarchy, or may have a data structure in which the option information hierarchy is not set.
[0059]
Therefore, the main purpose of the present embodiment is to manage the search request by managing the position information of each device connected on the network (here, the LAN 100) by the hierarchical structure as shown in FIG. An object is to specify the position of a device and to display the specified device position in an easy-to-understand manner for the user.
[0060]
5 to 8 are examples of layout bitmaps corresponding to the block hierarchy BL of the hierarchical position information shown in FIG. These layout bitmaps of FIGS. 5 to 8 are displayed on the client device 111 side. Thereby, the user can confirm the position of a device easily.
[0061]
The layout bit map of FIG. 5 is a position map in the 2-1 block of 2F.
In this layout bitmap, the color printer 101 and the MFP 102 are arranged on a layout (layout of actual desks and partitions in the 2F floor) stored in advance as a bitmap, and a firewall. 120 and the server device 112 are installed in the layout.
[0062]
The layout bitmap shown in FIG. 6 is a position map in the 2-2 block of 2F.
As shown in FIG. 6, the PC 111 and the printer 103 are installed in the layout shown in FIG.
[0063]
The layout bit map of FIG. 7 is a position map in 1-1 block of 1F.
As shown in FIG. 7, the PC 113 and the monochrome printer 104 are installed in the 1-1 block of 1F in the layout as shown in FIG.
[0064]
The layout bit map of FIG. 8 is a position map in the 1-2 block of 1F.
As shown in FIG. 8, the scanner 105 is installed in the 1-2 block of 1F in the layout as shown in FIG.
[0065]
The layout bitmap as described above is displayed on the screen of the client device 111.
[0066]
Hereinafter, the first to fifth embodiments will be described with respect to the operation of the network system shown in FIG. 2 that searches for devices based on the hierarchical location information shown in FIG.
[0067]
First, in the first embodiment, event information about a job issued to a device by the client apparatus 111 is notified in an easy-to-understand manner together with the position information of the device.
In the first embodiment, the client apparatus 111 holds a layout bitmap for expressing the position of the searched device. In the second embodiment, the layout bitmap is used. Is held by the server device 112.
Furthermore, in the first and second embodiments, only the layout bitmap corresponding to the block (BL) hierarchy is retained. In the third embodiment, each hierarchy of the hierarchical position information is stored in each hierarchy. The corresponding layout bitmap is held and reflected in the search result display of the client device 111.
[0068]
In the fourth and fifth embodiments, the position of the device on the network 100 is notified to the user in an easy-to-understand manner, and the state of the device is notified to the user.
Here, in the fourth embodiment, the device state is obtained by polling from the device, and in the fifth embodiment, the device state is obtained by event notification from the device.
[0069]
<First Embodiment>
In the present embodiment, event information about a job issued to the device by the client apparatus 111 is notified together with the position information of the device in an easy-to-understand manner.
In the system according to the present embodiment, the layout bitmap for expressing the position of the device is held in the client apparatus 111.
[0070]
First, a configuration for the server apparatus 112 to manage attribute information of each device on the network 100 will be described.
[0071]
FIG. 9 is an example of a data structure of a database for the server apparatus 112 to manage attribute information of each device on the network 100.
In FIG. 9, each column corresponds to one piece of data relating to each registered device, that is, a tuple, and each row corresponds to an attribute for each tuple.
In the database 800, hierarchical position information “802” to “810” and other attribute information “811” and “812” are stored in association with each device.
The other attribute information includes, for example, an attribute (811) indicating the presence / absence of a color input / output function and an IP address (812), but is not limited thereto, and indicates the presence / absence of a stapling function. You may make it use the information of the attribute with which a device is generally provided, such as an attribute and the attribute which shows the presence or absence of a double-sided printing function.
[0072]
FIG. 10 is a diagram illustrating an example of a data structure of device registration data when the device registers itself in the database 800 managed by the server device 112.
The device registration data 900 includes location information TAG 901 (902 to 911) in which hierarchical device position information is set, and device attribute information TA 912 (913 to 914) in which device attribute information is set.
Each device transmits its device registration data 900 to the server device 112 after power-on.
[0073]
The operation in which the device transmits its device registration data 900 may be executed in response to a change in an item in the device registration data 900, or in response to the device being plugged into the network. The transmission operation may be executed periodically, or the transmission operation may be executed periodically. Further, the device may transmit the device registration data 900 in response to an inquiry from the server device 112.
[0074]
In response to the reception of the device registration data 900 from the device, the server device 112 registers the information related to the received device in the database 800.
[0075]
Note that the device registration data 900 of FIG. 10 is device registration data for the device “LBP1110”. If the hierarchical location information is not yet registered on the LBP 1110 side, “903” and “904” to “911” is transmitted to the server device 112 in a state where no data is set or meaningless data is set.
[0076]
FIG. 11 shows an example of a search condition input screen when a device search is performed from the client device 111.
In FIG. 11, search entries are input to “1001a”, “1001b”, and “1001c”. The input at this time can be input by selecting a desired one from a pull-down menu, for example.
In “1002a”, “1002b”, and “1002c”, attribute information corresponding to each entry is input.
[0077]
For example, when an entry is selected as a device, the attribute information is displayed as a pull-down menu for a printer, MFP (MFP), or scanner, and the user wants to search from the attribute information. Will be selected.
[0078]
When the above various inputs are completed, the search conditions are input using the input buttons 1003 and 1004.
A button 1003 indicates that the search is performed using the AND of the conditions, and a button 1004 indicates that the search is performed using the OR of the conditions.
After the user inputs the search condition, the user executes a search using a search start button 1005.
[0079]
FIG. 12 is a diagram showing a specific example of the search input screen.
In FIG. 12, the device is a printer as the attribute information, and a device capable of color output is searched.
For example, when searching for a printer whose installation floor is the second floor as the hierarchical position information, “floor” may be input to “1001c” and “2F” may be input to “1002c”. Furthermore, if you want to search by specifying a more detailed location on the second floor, for example, enter “Block” in “1001c” and enter “2-1” in “1002c”. Then, it is possible to search for a printer whose installation block is 2-1.
[0080]
FIG. 13 is a diagram illustrating an expression representing the search condition in the above search example.
FIG. 13 shows a condition that the device terminal device (DV) is a printer and color output (color) is possible (TRUE).
[0081]
Here, it is necessary to explain how the server apparatus 112 that has received the search condition formula shown in FIG. 13 evaluates the formula “FL = 2F”. This is because the location condition of the 2F floor is not only satisfied by the device installed on the 2nd floor of the “Tokyo branch AA building” which is the search target desired by the user, but also the “YY building at the Osaka branch”. The device installed in 2F also satisfies the condition. For this reason, even a device of “Osaka branch w building”, which is not of interest to the user, is a search hit, and a search result that is extremely difficult for the user to output is output.
[0082]
Therefore, in order to avoid the above situation, the server device 112 needs to have a mechanism for automatically specifying a higher hierarchy than the floor hierarchy (FL).
As an example of this mechanism, there is a method in which the hierarchical position information of the server apparatus 112 is applied to the search condition of the hierarchy above the floor hierarchy (FL) by holding the hierarchical position information of the server apparatus 112 itself.
[0083]
According to the above method, if a search request is issued under the condition “FL = 2F” to the server apparatus 112 installed in the “AA building of the Tokyo branch”, only the devices on the 2F floor of the AA building are searched. It becomes possible to target.
In addition, when it is desired to search for a device installed in the 2nd floor of the “YY building in Osaka branch”, “FL = 2F” is set to the server device 112 installed in the “YY building in Osaka branch”. A search request may be issued under conditions.
[0084]
In the screen shown in FIG. 12, if only one layer is specified, it is only from the specified layer, but it may be so-called full path specification that specifies from the highest layer (C) to a predetermined layer.
In this case, the search condition formula shown in FIG. 13 is a full path designation from the highest hierarchy (for example, C: JP, O = ABC, BR = Tokyo branch,...).
If such a full path designation is used, the server device 112 installed in the “Tokyo branch AA building” can search for devices installed in the 2nd floor of the “YY building in Osaka branch”.
[0085]
FIG. 14 is an example of a search result in which the server apparatus 112 returns a device that matches the search condition formula illustrated in FIG. 13 to the client apparatus 111.
The server device 112 searches the database 800 (see FIG. 9) based on the search condition expression of FIG. 13 received from the client device 111, and returns the matched device information to the client device 111 as a search result 1300. To do.
The search result 1300 includes hierarchical position information 1301 to 1310 and device attribute information 1311 to 1312.
When there are a plurality of devices that match the search condition, the search result 1300 includes hierarchical position information 1301 to 1310 and device attribute information 1311 to 1312 of the plurality of devices.
[0086]
Here, as an example, since only the LBP 1110 matches the search condition expression shown in FIG. 13, only the information of the search result 1300 shown in FIG. 14 is returned to the client device 111. .
[0087]
FIG. 15 is a correspondence list of the block hierarchy (BL) and the layout bitmap (bitmap) of the hierarchical position information that the client device 111 has.
By using such a correspondence list, the layout bitmap can be specified from the hierarchical position information on the client device 111 side.
[0088]
In the present embodiment, layout bitmaps as shown in FIGS. 16, 17, 18, and 19 are held corresponding to the blocks 1-1, 1-2, 2-1, and 2-2, respectively. is doing.
For the other blocks, the layout bitmap of FIG. 20 is displayed.
[0089]
That is, FIGS. 16 to 19 show layout bitmaps corresponding to the respective block hierarchies.
In the present embodiment, information indicating the searched device is superimposed on these layout bitmaps to visually indicate which block on which floor and which position the requested device is located. To be able to.
[0090]
FIG. 20 is a layout bitmap (hereinafter referred to as “unknownMAP”) displayed when the device does not hold hierarchical location information or when the layout bitmap of the client apparatus 111 does not match.
In FIG. 20, the “1901” area indicates that there is no layout bitmap, and the “1902” area displays a device that does not have hierarchical position information or does not match the hierarchical position information.
[0091]
FIG. 21 is a device icon for displaying each device held by the client apparatus 111.
The device icon here is associated with each device name (NM) on a one-to-one basis, and a device icon indicating “unknown” is displayed for a device whose name is unknown.
[0092]
FIG. 22 is a diagram illustrating a mechanism in which the client device 111 displays a device icon on the layout bitmap.
The client device 111 extracts hierarchical position information and device attribute information from the search result acquired from the server device 112, and selects a layout bitmap and a device icon corresponding to each. Since the client apparatus 111 can obtain the coordinate information of the selected layout bitmap from the extracted hierarchical position information, for example, the color printer 101 (to the coordinates “10X + 10Y” of the selected layout bitmap is selected. A device icon 2002 representing LBP 1110) is displayed in an overlapping manner.
Thus, by displaying the device icon so as to overlap the corresponding coordinates of the layout bitmap, it is possible to easily show the position of the device for which the search request has been made to the user.
[0093]
FIG. 23 shows an example of a bitmap displayed on the client device 111 as a result of device search. From this display, it can be seen that the printer 101 capable of color output is in the vicinity of the table near the entrance of the 2nd 2-1 block.
[0094]
FIG. 24 is a block diagram showing an internal configuration of the color LBP 1110 (the printer 101 in FIG. 2) in the present embodiment.
As shown in FIG. 24, the printer 101 is connected to a system bus 2301 with a CPU 2302 that processes a program, a ROM 2303 that stores the program, a RAM 2304 that is a work area and a buffer area of the program, and the like. It is configured.
[0095]
In FIG. 24, “2305” is an LBP engine engine controller, and the engine 2309 is connected via this controller 2305.
“2306” is a panel controller. The panel controller 2306 controls input / output to / from the panel 2310 and manages the panel 2310.
[0096]
Further, the color LBP 1110 in this embodiment holds a hard disk (HD) 2211 and can temporarily spool print data in the HD 2211.
“2307” is a disk controller that manages the HD 2211.
[0097]
“2308” is a network interface controller, and the printer 101 is connected to the network 100 via the controller 2308.
[0098]
“2312” is a non-volatile RAM (NVRAM) that retains data even when the printer 101 is powered off.
In the present embodiment, hierarchical position information, attribute information, and the like are held in the NVRAM 2312.
[0099]
25 to 29 are flowcharts for explaining the processing procedure in the network system in this embodiment.
Hereinafter, the operation of the network system in the present embodiment will be specifically described with reference to a flowchart.
[0100]
First, device hierarchical location information registration processing will be described with reference to the flowchart shown in FIG.
Here, as an example, the operation will be described focusing on the operation of the printer 101 (LBP 1110).
[0101]
The LBP 1110 keeps the hierarchical position information and attribute information in the nonvolatile RAM (2312) in the device. When power is turned on, the CPU 2302 of the LBP 1110 connects to the server device 112 (step S2801).
After this connection, the hierarchical position information and attribute information are read from the non-volatile RAM (2312) of the LBP 1110 and registered in the server device 112 in the format as shown in FIG. 10 (step SS2802).
[0102]
After the above registration, the CPU 2302 of the LBP 1110 releases the connection with the server device 112 (step S2803).
[0103]
By following the procedure as described above, each device registers hierarchical position information and attribute information in the server device 112 after power-on.
[0104]
Next, the processing of the server device 112 will be described using the flowchart of FIG.
Here, the server device 112 is constituted by, for example, an event-driven program, and when an event occurs, the server device 112 analyzes the event and performs corresponding processing.
[0105]
When the power is turned on, the server device 112 first opens a reception port (step S2401).
Next, the server device 112 acquires an event (step S2402), and determines whether the acquired event is an end command (step S2403). As a result of the determination, if the acquired event is an end command, the reception port is closed (step S2404), and this process ends.
[0106]
On the other hand, if it is determined in step S2403 that the command is not an end command, the server apparatus 112 determines whether it is a search request (step S2405). If the request is a search request, database search processing is performed in step S2406.
[0107]
On the other hand, if it is determined in step S2405 that the request is not a search request, the server apparatus 112 determines in step S2407 whether it is a registration request to the database. If the result of this determination is a registration request, the server device 112 registers the received data on the table 800 shown in FIG. 9 (step S2408). The registered data is held in the HD 211.
If the result of determination in step S2407 is another request, other processing is performed (step S2409).
[0108]
Next, the data search process executed by the server device 112 will be described in more detail with reference to FIG.
[0109]
First, the server device 112 determines whether or not all search conditions have been processed (step S2501).
As a result of this determination, this processing is repeated until all search conditions are completed.
[0110]
As a result of the determination in step S2501, when all the search conditions in the received packet have been searched, the server device 112 transmits the result to the client device 111 (step S2502), and this processing ends.
[0111]
As a result of the determination in step S2501, if not all the search conditions in the received packet have been searched, the server apparatus 112 extracts the search conditions from the received packet (step S2503).
Then, the server device 112 determines whether all registered device information in the table shown in FIG. 9 has been searched for the search condition (step S2504).
[0112]
If all the registered device information is searched as a result of the determination in step S2504, the server apparatus 112 returns to step S2501 in order to retrieve the next search condition.
[0113]
If it is determined in step S2504 that not all registered device information has been searched, the server apparatus 112 extracts the n-th device information from the HD 211 (step S2505).
Then, the server device 112 determines whether or not the extracted device information matches the condition (step S2506).
[0114]
If they match as a result of the determination in step S2506, the server apparatus 112 acquires the device information (step S2507) and appends it to the result (step S2508). Thereafter, the process returns to step S2504.
[0115]
If the result of determination in step S2506 is that they do not match, the server apparatus 112 returns to step S2504 in order to perform processing for the next device.
[0116]
Through the processing as described above, the server device 112 searches all the devices in the table 800 shown in FIG. 9 for each search condition, and transmits the result to the client device 111.
[0117]
Next, the overall operation of the client apparatus 111 will be described with reference to FIG.
Here, the client device 111 is configured by, for example, an event-driven program, and when an event occurs, the client device 111 analyzes the event and performs corresponding processing.
[0118]
First, the client device 111 acquires an event (step S2601). If an end command event is received, the process ends as it is (step S2602).
[0119]
In the client device 111, the search condition is input from the user from the search condition input screen as shown in FIG. When the user clicks the search start button 1005, the event is generated.
[0120]
If the request is a search command issuance request in step S2603, the client terminal apparatus 111 transmits the search request to the server apparatus 112 (step S2604).
[0121]
At this time, the server terminal apparatus 112 is inquired with the search condition formulas as shown in FIG. 12 and FIG. Also, by storing this search condition formula in the HD 211, the condition formula can be used in the next device search. In this case, it is possible to omit re-input of search conditions from the user.
[0122]
Next, the client apparatus 111 waits for a search result from the server apparatus 112, and when receiving the event, the client apparatus 111 determines in step S2605.
If it is determined in step S2605 that a search result as shown in FIG. 14 is received, search result display processing is performed (step S2606).
If another event is received, other processing is performed (step S2607).
[0123]
Next, the search result display process in step S2606 in FIG. 28 will be described in more detail using the flowchart in FIG.
[0124]
First, in the first step S2701, it is determined whether or not all search results have been processed. As a result of this determination, if it is determined that all processing has been completed, this processing ends.
[0125]
On the other hand, if all the processes are not completed as a result of the determination in step S2701, the process proceeds to step S2702, and hierarchical position information is acquired from the received search result. Then, based on the acquired hierarchical position information, the client device 111 determines whether a map can be displayed (step S2703).
[0126]
In the present embodiment, the hierarchical position information capable of displaying a device is hierarchical position information including information indicated by reference numeral “1401” in FIG. If the hierarchical location information does not include this, it is confirmed whether or not the unknownMAP has been displayed (step S2709), and the unknown device shown in FIG. 20 is displayed (step S2710).
[0127]
Furthermore, NM information is acquired from the hierarchical position information (step S2711), and a device icon corresponding to NM is displayed in the area of reference numeral “1902” in FIG. In this case, the device is not displayed normally, that is, a device whose hierarchical location information is not yet registered is displayed here.
[0128]
On the other hand, if it is determined in step S2703 that the device terminal can be displayed, the BL information in the hierarchical position information is acquired (step S2704). The client device 111 tries to display the necessary layout bitmap by comparing the BL information with the BL information table shown in FIG.
[0129]
Here, it is determined whether or not the corresponding layout bitmap has already been displayed (step S2705). If the result of this determination is that it has not been displayed yet, the corresponding bitmap is displayed (step S2706). Then, NM information and map information are acquired from the hierarchical position information (step S2707).
[0130]
If the result of determination in step S2705 is that it has been displayed, processing proceeds to step S2707. The corresponding device icon is read from the table of FIG. 21 from the NM information. In addition, it determines where to display the device icon from the map information.
[0131]
In the present embodiment, the server apparatus 112 returns a result as shown in FIG. 14 as a search result, so that NM is LBP 1110 and the device is “10X + 10Y”. A device icon is displayed at a position as shown in FIG. 22 (step S2708). By displaying the device icon on the previous layout map 1, the search result as shown in FIG. 23 is displayed on the display of the client device 111.
[0132]
Through the processing as described above, the layout bitmap as shown in FIG. 5 to FIG. 8 is displayed on the display of the client apparatus 111, and the user can obtain detailed position information of the searched device. .
Thereafter, the user of the client apparatus 111 selects a desired device from the plurality of searched devices, and transmits a job to the selected device. For example, a print job is transmitted if the device is a printer, and a transmission job is transmitted if the device is a FAX.
[0133]
FIG. 30 is a diagram illustrating an example of print job information issued by the client apparatus 111.
In FIG. 30, “3101” is a job characteristic TAG indicating that the following information is job attribute information. “3102” to “3105” are followed by print job information.
“3102” is a job ID for the job input device or the client apparatus 111 to specify the job. In FIG. 30, the job ID is “1234”.
[0134]
FIG. 31 shows a job management table 3200 for managing jobs received by the device.
In the job management table 3200, an event condition to be notified to the client apparatus 111 for each job and a network address of the notification destination are stored in association with each other.
[0135]
When the device receives the print job shown in FIG. 30, the device stores the job in the job management table 3200 based on the information described in the job. When the device executes a job and detects the occurrence of an event to be notified to the client device 111, the device notifies the client device 111 of the event.
[0136]
FIG. 32 shows an example of an event notification format notified from the device to the client apparatus 111.
This event notification format 3301 is used to notify an event to a client apparatus indicated by “TCP / IP: 192.168.2.16:1025” when a print job is completed. The hierarchical type shown in FIG. Position information 3302 is added.
[0137]
FIG. 33 shows an example of a screen displayed on the display device 27 of the client device 111 when the job of “JOB ID = 1234” is completed.
In FIG. 33 above, the fact that printing has been completed is displayed as character information ("printing has been finished ...").
[0138]
FIG. 34 is a flowchart showing a processing procedure up to the screen display in the client device 111.
[0139]
First, when the event notification reception process is started, it is determined in the first step S3501 whether or not the input information is an event notification. As a result of this determination, if the input information is not an event notification, this process is terminated.
[0140]
If the input information is an event notification, the process advances to step S3502 to acquire location information (hierarchical position information) from the received event information 3301. Then, based on the acquired hierarchical position information, the client apparatus 111 determines whether a layout bitmap can be displayed (step S3503).
[0141]
In the present embodiment, the hierarchical position information capable of displaying a device is hierarchical position information including information indicated by reference numeral “1401” in FIG. If the hierarchical location information does not include this, the unknownMAP shown in FIG. 20 is displayed (step S3510).
[0142]
Further, NM information is acquired from the hierarchical position information (step S3511), and a device icon corresponding to NM is displayed in the area of reference numeral “1902” shown in FIG. 20 (step S3512). In this case, a device that is not normally displayed, that is, a device for which hierarchical position information is not yet registered is displayed here.
[0143]
On the other hand, if it is determined in step S3503 that the device terminal can be displayed, the BL information in the hierarchical position information is acquired (step S3504). Then, the client terminal device 111 displays the necessary layout bitmap by comparing the acquired BL information with the BL information table shown in FIG. 15 (step S3505).
[0144]
By performing the process as described above, it is possible to display the generated event information such as “printing has ended. JOB ID = 1234” as shown in FIG. Become.
[0145]
Next, NM information and map information are acquired from the hierarchical position information (step S3506). In the present embodiment, NM is LBP 1110 and the device coordinates indicated by the device icon are “1OX + 10Y”, so the device icon is displayed at the position shown in FIG. 22 (step S3509). By superimposing the device icon on the previous layout map, the device that issued the event notification can be displayed as shown in FIG.
[0146]
FIG. 35 is a flowchart showing the overall operation of the device.
First, an event is acquired in the first step S3601. Then, it is determined whether or not the acquired event is an end command event (step S3602). As a result of this determination, if the received event is an end command, this processing is ended as it is.
[0147]
On the other hand, if it is determined in step S3602 that the received event is not an end command, the process advances to step S3603 to determine whether it is an event registration request. As a result of this determination, if so, the process proceeds to step S3604 to perform event registration processing.
[0148]
On the other hand, if it is determined in step S3603 that the request is not an event registration request, the process advances from step S3603 to step S3605 to determine whether a job processing request has been received. If the result of this determination is a job (print job) processing request, the process advances to step S3606 to execute print processing. If it is determined in step S3605 that the received event is not a job processing request, the process advances to step S3607 to perform other processing.
[0149]
FIG. 36 is a flowchart showing a processing procedure when an event occurs in the device.
First, when an event occurs, it is determined whether or not it is a job-related event (step S3700).
[0150]
Next, the process proceeds to step S3701, and the notification condition of the corresponding “JOB ID” is determined. Based on the result of this determination, it is determined whether or not the conditions are matched in step S3701, and if they match, the process advances to step S3703 to acquire hierarchical position information.
[0151]
In step S3704, a notification packet is created, and the created notification packet is notified to a designated address (step S3705).
Next, in step S3706, it is determined whether or not the job has ended. If the job has ended, the process proceeds to step S3707 to perform processing for deleting the corresponding “JOB ID” entry from the job management table (see FIG. 31). .
[0152]
As described above, according to the present embodiment, event information about a job issued by the user can be notified in an easy-to-understand manner together with the location of the device where the event has occurred.
In particular, when the client apparatus 111 automatically selects a job request destination device without using a user, a device whose location is unknown to the user may be selected. In such a case, it is possible to notify the user of an easily understood device position.
[0153]
The job requested from the device is not limited to the job directly requested from the client apparatus 111 that is the event notification destination for the job. That is, the job from the client device may be transferred from the third device.
[0154]
<Second Embodiment>
In the first embodiment, the client apparatus 111 is configured to hold the layout bitmap for expressing the position of the searched device. However, in the present embodiment, the layout bitmap is stored in the server apparatus 112. Hold.
[0155]
Since the present embodiment is based on the first embodiment, a configuration different from the first embodiment will be specifically described here.
[0156]
In the present embodiment, the layout bitmap shown in FIG. 16 to FIG. 20, the correspondence table between the hierarchical position information and layout bitmap shown in FIG. 15, and the device icon information shown in FIG. Stored in the hard disk of the server device 112.
Therefore, first, the operation of the client device 111 will be described with respect to parts different from the first embodiment.
[0157]
FIG. 37 is a flowchart showing search result display processing of the client device 111.
In first step S5001, it is determined whether all search results have been processed. As a result of this determination, if it is determined that all processing has been completed, the processing ends.
[0158]
On the other hand, if all the processes are not completed as a result of the determination in step S5001, the process proceeds to step S5002, and hierarchical position information is acquired from the received search result.
Next, the server apparatus 112 is connected (step S5003), and map information corresponding to the acquired hierarchical position information is acquired (step S5004).
[0159]
Next, it is determined whether or not the map corresponding to the hierarchical position information has been displayed (step S5005). If the result of this determination is that it has not yet been displayed, a corresponding layout map is acquired (step S5006).
Further, NM information and map information are acquired from the hierarchical position information (step S5007), and a device bit mat corresponding to the acquired NM information and map information is acquired (step S5008).
[0160]
Next, the acquired device bit mat is displayed at a predetermined position on the map (step S5009), and then the connection with the server device 112 is disconnected (step S5010).
[0161]
FIG. 38 is a flowchart of processing in which the client apparatus 111 performs display based on the event notification received from the device.
First, when the event notification reception process is started, it is determined in step S5100 whether or not the input information is an event notification. As a result of the determination, if the input information is not an event notification, the process is terminated.
[0162]
On the other hand, if the input information is an event notification, the process advances to step S 5101 to connect to the server device 112.
Next, it is determined whether or not the corresponding map has been displayed. If the map has not been displayed yet, the corresponding layout bitmap is acquired from the server device 112 (step S5103).
Further, NM information is acquired from the hierarchical position information (step S5104), and a corresponding device icon is acquired (step S5105).
[0163]
Next, based on the acquired information, the device icon is displayed on the layout map based on the received coordinate information (step S5106).
[0164]
Next, the connection with the server device 112 is disconnected (step S5107), and the event information and “JOB ID” are acquired. Then, the acquired event information and “JOB ID” are displayed. Thereby, the display as shown in FIG. 33 can be realized.
[0165]
Next, the operation of the server device 112 will be described with respect to parts different from the first embodiment.
[0166]
FIG. 40 is a flowchart showing layout bitmap search processing in the server apparatus 112.
First, in first step S5201, it is determined whether or not the search request is a layout map search request.
[0167]
If the result of the determination is a layout map search request, the process advances to step S5202 to determine whether or not the hierarchical position information received from the client device 111 can be displayed as a map. If it is determined that display is possible, in step S5203, the corresponding layout bitmap is loaded from the correspondence table shown in FIG. 15, the acquired map is returned to the client device 111, and the process is terminated. .
[0168]
On the other hand, if the result of determination in step S5202 is that map display is not possible, processing proceeds to step S5205, and the unknownMAP shown in FIG. 21 is displayed.
[0169]
If it is determined in step S5201 that the search request is not a layout map search request, the process advances to step S5206 to determine whether the request is a device icon search request.
[0170]
If the result of the determination is a device bitmap search request, the process advances to step S5207 to load the corresponding device icon from the table shown in FIG. 21 and return it to the client apparatus 111 (step S5204). ).
[0171]
In the first embodiment, since the layout bitmap is stored in the client device 111, the layout bitmap is transferred from the server device 112 to the client device 111 when the search result is displayed on the client device 111. Is not required to be transferred, and it is possible to reduce processing and time for displaying, and to reduce traffic on the network system.
On the other hand, in this embodiment, since the server apparatus 112 is configured to maintain the layout bitmap, the map information can be managed in the server apparatus 112 in a unified manner, and the map information needs to be held for each client apparatus 111. This makes it possible to facilitate maintenance such as updating and reduce the load of memory resources of the client device 111.
Therefore, the first embodiment or the present embodiment may be adopted as appropriate in consideration of the load on the network 100, the capability of the client device 111, and the like.
[0172]
<Third Embodiment>
In the first and second embodiments, only the layout bit map corresponding to the block (BL) hierarchy is held. However, in this embodiment, the layout bits corresponding to each hierarchy of the hierarchical position information. The map is held and reflected in the search result display of the client device 111.
According to the present embodiment, the searched device is displayed in the layout bitmap of the hierarchy according to the user's preference from rough position information at the building level to detailed position information such as one section of the floor. Is possible.
[0173]
In this embodiment, the client apparatus 111 holds the layout bitmap as in the first embodiment. However, the server apparatus 112 holds the layout bitmap as in the second embodiment. It may be time.
[0174]
FIG. 40 shows a MAP list corresponding to each hierarchy to be searched.
The list in the lower half of FIG. 40 is a list corresponding to FIG.
In this embodiment, when a device bitmap is displayed, the device is displayed based on attribute information immediately below the attribute of the hierarchy to be searched. The hierarchical relationship is the same as the hierarchical relationship shown in FIG.
[0175]
For example, when searching for all devices with BU = AA building, the attribute FL (see FIG. 4 above) is displayed on the layout map as position information for displaying the device.
[0176]
For example, when searching for all devices in ABC Shoji, the company name (O) is selected as “1001a” from the pull-down menu on the input screen shown in FIG. 11, and the attribute value is set as “1002a”. The user enters ABC trading and starts the search by a search start button 1005.
[0177]
The client device 111 acquires the search result from the server device 112 by the procedure as described above, and displays the device bitmap on the layout bitmap based on the search result.
[0178]
The display process in the client device 111 at this time is shown in the flowchart of FIG.
First, when this process is started, it is determined in the first step S6001 whether or not the display of all search results has been completed, and this process is repeated until the process is completed.
[0179]
If it is determined in step S6001 that all the searches have not been completed, the attribute NM is acquired from the search results in step S6002. This is processing performed to display a device icon in step S6008, step S6010, or step S6013.
[0180]
Next, it is determined whether or not the layout bitmap corresponding to the attribute of the condition searched in step S6003 has been displayed. In this example, since the search is executed by the attribute O = attribute value ABC trading, the search result device is displayed on the layout bitmap as shown in FIG. 42 obtained from the MAP correspondence list (see FIG. 41). It will be.
It is determined whether the layout bitmap of FIG. 42 has been displayed. If the result of this determination is that it has not yet been displayed, it is displayed in step S6004, and the process proceeds to step S6005.
[0181]
If the layout bit map of FIG. 42 has already been displayed as a result of the determination in step S6003, the lower layer attribute and attribute value of the searched attribute are acquired from the search result in step S6005. In step S6006, it is determined whether or not the acquired attribute value can be displayed. Since it is not possible to display a device that is out of the attribute value range or that has not been input with the attribute value, the process advances to step S6011.
[0182]
In step S6011, it is determined whether unknownMAP has been displayed. If not, it is displayed in step S6012, and the device icon corresponding to the NM value acquired in step S6002 is displayed in the device field of unknownMAP. (Step S6013).
[0183]
On the other hand, if the result of determination in step S6006 is that display is possible, it is determined whether the lower layer attribute is the MAP attribute (step S6007). If the result of this determination is that the attribute is not a MAP attribute, the process advances to step S6008, and the device icon corresponding to the NM value acquired in step S6002 is displayed superimposed on the attribute position on the displayed layout bitmap. In this case, since the attribute value of the hierarchy BR below the hierarchy (O) in the hierarchical location information is the Tokyo branch (see FIG. 4 above), each device is displayed on the position of the Tokyo branch 5001. It will be. As a result, the display as shown in FIG. 42 is obtained.
[0184]
Further, when searching for the device position in more detail, on the input screen shown in FIG. 11, the block name (BL) is selected from the pull-down menu as “1001a”, and the attribute value is set to “1002a”. 1 is selected, and the search start button 1005 causes the user to start the search.
[0185]
The client device 111 acquires the search result from the server device 112 by the procedure as described above. Based on the search result acquired from the server device 112, the client device 111 displays the device bitmap on the layout bitmap. At this time, similarly, the processing flow shown in FIG. 41 is executed. In this case, since the lower layer attribute information is MAP information in the snubber S6007, the process proceeds to step S6009.
[0186]
In step S6009, it is determined whether the coordinate range is within the layout bitmap range. If it is within the range, in step S6010, the device icon corresponding to the NM value acquired in step S6002 is superimposed and displayed at the coordinate position of the displayed layout bitmap.
[0187]
In this case, since the search is executed with the attribute BL and the attribute value 2-1, the search result device is displayed on the layout bitmap of FIG. 18 obtained from the MAP correspondence list (see FIG. 40). .
[0188]
Since it is a hierarchy MAP below the BL of the hierarchy location information (see FIG. 4 above), each device of the search result is displayed on the coordinates on the layout. As a result, the display as shown in FIG. 5 is obtained.
[0189]
Here, layout bit map diagrams of other layers will be described.
As described above, FIG. 43 shows a layout bitmap in the case of searching with attribute O = attribute value ABC Trading. A device whose lower attribute BR of the attribute O is a Tokyo branch is displayed in 5001, and a device that is an Osaka branch is displayed in 5002.
[0190]
FIG. 43 is a result display when all devices are searched by attribute O = attribute value ABC Trading.
[0191]
FIG. 44 is a layout bitmap when searching for attribute BR = attribute value Tokyo branch. The lower attribute of the attribute value BR is OP, which indicates that there is OPTION, and further indicates that there is detailed information further below. A device whose attribute Bu is AA building is displayed in 5201.
[0192]
FIG. 45 is a search result display when all devices are searched in the attribute BR = attribute value Tokyo branch, and a building 5302 is displayed.
[0193]
FIG. 46 is a layout bitmap when searching with attribute BU = attribute value AA building. A device whose lower layer attribute FL of the attribute BU is 2F is displayed in the bitmap 5402, and a device whose 1F is 1F is displayed in the bitmap 5401.
[0194]
FIG. 47 is a display of results when all devices are searched with the attribute BU = attribute value AA building. All devices existing in the 2F bitmap 5502 and all devices present in the 1F bitmap 5501 are displayed. Is displayed.
[0195]
FIG. 48 is a layout bitmap when searching with attribute FL = attribute value 2F. A device whose lower level attribute BL of the attribute FL is 2-1 is displayed in the bitmap 5601, and a device whose name is 2-2 is displayed in the bitmap 5602.
[0196]
FIG. 49 is a result display when all devices are searched with the attribute FL = attribute value 2F. All devices existing in the 2F-1 bitmap 5701 and the 2F-2 bitmap 5702 are displayed.
[0197]
FIG. 50 is a layout bitmap when searching with attribute FL = attribute value 1F. FIG. 51 is a display of results when all devices are searched with attribute FL = attribute value 1F. A device having a lower layer attribute BL of the attribute FL of 1-2 is displayed in the bitmap 59901, and a device of 1-1 is displayed in the bitmap 5902.
[0198]
As described above, according to the present embodiment, it is possible to search and display according to each level of location information from detailed display to rough display according to the search request level of the user. become.
[0199]
<Fourth embodiment>
In the present embodiment, the position of the device on the network 100 is notified to the user in an easy-to-understand manner, and the state of the device is notified to the user.
In the present embodiment, the device status is acquired by polling from the device.
[0200]
Since the present embodiment is based on the first embodiment, a configuration different from the first embodiment will be specifically described here.
[0201]
FIG. 52 shows a management table for managing device icon information of each device in the client apparatus 111.
The device icon information here is composed of several types of icon information representing the state of each device.
Therefore, the client apparatus 111 selects a device icon corresponding to the state acquired from the device from the management table of FIG. 52 and displays it on the layout bitmap.
In FIG. 52, icons other than devices, such as a PC, are also shown.
[0202]
In FIG. 52, device icon information corresponding to each state of operating (Ready), running out of paper (No Paper), and paper jammed (Paper Jammed) is shown for each device.
Each device icon information is associated with each device name (NM), and a device icon indicating “unknown” is displayed for a device whose name is unknown.
[0203]
FIG. 53 shows the position of the device icon to be displayed superimposed on the layout bitmap.
For example, the printer 101 (LBP 1110) having the location information of the coordinate information “10X + 10Y” is displayed at the position shown in FIG. 53 in the form of a bitmap icon corresponding to the current state.
In FIG. 53, a device icon indicating that the state of the printer 101 is out of paper (No Paper) is displayed.
[0204]
As described above, by displaying the bitmap icon and the layout bitmap together, the position of the searched device and the current state of the device can be displayed to the user in an easily understandable manner.
[0205]
FIG. 54 shows a layout bitmap displayed on the client device 111 after obtaining the status of the searched device.
As shown in FIG. 54, in this layout bit map, it can be visually seen that the printer (LBP 1110) capable of color input / output is near the table near the entrance of the block 2-1 on 2F. Further, the color printer 101 can simultaneously know that it is out of paper.
[0206]
FIG. 55 is a flowchart showing search request transmission processing in the client apparatus 111.
In the search request transmission process shown in FIG. 55, first, the search condition input on the search condition input screen as shown in FIG. 12 is acquired, and the search condition expression format as shown in FIG. 13 is obtained. (Step S5601).
Next, a search request packet including the converted search condition formula is generated and transmitted to the server device 112 to make an inquiry (step S5602).
[0207]
By storing the search condition formula in the hard disk 211, the saved search condition formula can be used when a device search is performed under the same conditions at the next search. Thereby, it is possible to save the user from re-inputting the search condition.
[0208]
FIG. 56 is a flowchart showing device search result processing of the client apparatus 111.
In FIG. 56, it is determined whether one or more devices matching the search condition have been found as a result of the device search (step S5701). If no device that matches the search condition is found, a message (not shown) indicating that the corresponding device has not been found is displayed (step S5704), and the process is terminated.
[0209]
On the other hand, if it is determined in step S5701 that one or more devices have been found, the search results (location information and attribute information of the corresponding device) are stored in the hard disk 211. For example, when a search result as shown in FIG. 14 is obtained, it is stored in the hard disk 211. Thereafter, a state acquisition process to be described later is activated (step S5703), and this process is terminated.
[0210]
FIG. 57 shows the operation of the state acquisition process activated in step S5703 in the flowchart of FIG.
This status acquisition process is a program for acquiring the device status at a certain interval and displaying the device icon corresponding to the current status on the layout bitmap.
[0211]
When the status acquisition process is started, first, the search results stored in the hard disk 211 in step S5702 in FIG. 56 are referred to to determine whether all search results have been processed, that is, stored search results. In step S5801, it is determined whether status acquisition processing has been completed for all IP address devices included in the device.
[0212]
Here, when all the search results have been processed, a polling timer is started in order to acquire the state of the device found by the search processing at a certain interval (step S5813), and then polling is performed in step S5814. The timer waits for a timeout event. If a polling timer timeout event is received, the process again proceeds to step S5801, and the same processing is performed.
[0213]
If it is determined in step S5801 that there is an unprocessed search result, device information (location information and attribute information) for one device is acquired from the unprocessed search result (step S5802). Further, a status acquisition request packet (not shown) is transmitted to the IP address included in the acquired attribute information (step S5803), and a status acquisition response packet reception waiting state as shown in FIG. 58 is entered.
For example, when the search result as shown in FIG. 14 is processed, the IP address is “192.1.2.1”, and a status acquisition request packet is transmitted to this IP address.
[0214]
In step S5804, when the status acquisition response packet is received from the target device, the above-described figure is based on the device name (NM) information included in the location information of the search result and the device status information of the received status acquisition response packet. An appropriate device icon corresponding to the device state is selected from the various device icons as shown in 52 (step S5805).
For example, when the search result as shown in FIG. 14 is processed, the device name information is “LBP 1110”. If the device status information in the status acquisition response packet indicates a paper out, the bitmap icon indicated by “2001” in FIG. 52 is selected.
[0215]
Next, it is determined whether or not the client apparatus 111 can display a layout bitmap corresponding to block (BL) information as location information, that is, whether or not the layout bitmap information corresponding to block (BL) information is held. Is determined using the information table shown in FIG. 15 (step S2906).
In the present embodiment, the location information that can display the layout bitmap is location information including information indicated by “1401” in FIG. If the location information does not include this, it is determined whether or not the unknownMAP shown in FIG. 20 has already been displayed (step S5810).
[0216]
Here, if the unknownMAP is not displayed yet, the unknownMAP is displayed in the area 1901 shown in FIG. 20 (step S5811). Then, the device bitmap icon selected in step S5805 is displayed in area 1902 shown in FIG. 20 (step S5812). In this case, an icon of a device whose layout map has not been normally displayed, that is, whose location information has not yet been registered, is displayed here.
[0217]
On the other hand, if it is determined in step S5806 that the layout bitmap can be displayed, it is determined whether a layout bitmap corresponding to the block (BL) information in the location information has already been displayed (step S5807). If it is determined that it is not displayed yet, a layout bitmap corresponding to the block (BL) information is displayed on the screen (step S5808).
For example, when the search result as shown in FIG. 14 is processed, the block (BL) information of the color printer 101 (LBP 1100) found by the search is “2-1”. 18 layout bitmaps are displayed.
[0218]
Based on the coordinate information (MAP) in the location information, the device bitmap icon selected in step S5805 is displayed in an overlapping manner at the corresponding display position on the layout bitmap (step S5809).
For example, when the search result as shown in FIG. 14 is processed, the coordinate information (MAP) of the color printer 101 (LBP 1100) is “10X + 10Y”. If the result of inquiring the status to the color printer 101 (LBP 1100) is “out of paper”, a device icon indicating that the paper is out is displayed at the position shown in FIG. By displaying this device icon so as to overlap the previous layout bitmap, the search result as shown in FIG. 55 can be displayed.
[0219]
FIG. 59 shows a device status acquisition response operation.
After the power is turned on, the device opens a reception port for receiving a status acquisition request packet and enters a receivable state (step S5901).
When a status acquisition request packet is received from the client device 111 (step S5902), the status of the device itself is checked and status information to be notified is determined (step S5903). For example, when “out of paper” has occurred, status information indicating “out of paper” is determined as information to be notified.
[0220]
Next, a response packet as shown in FIG. 58 including the state information to be notified is generated (step S5904). Then, the generated response packet is transmitted to the client device 111 (step S5905), and the state acquisition request packet can be received again.
[0221]
As described above, according to the present embodiment, it is possible to notify the user of the position of the device on the network 100 in an easy-to-understand manner and to notify the user of the device information.
Further, since the device status is acquired from the device by polling, even if a packet is temporarily lost on the network 100, the device status can be reliably acquired.
[0222]
<Fifth embodiment>
In the present embodiment, the position of the device on the network 100 is notified to the user in an easy-to-understand manner, and the state of the device is notified to the user.
In the present embodiment, the state of the device is acquired by event notification from the device.
[0223]
Since the present embodiment is based on the first embodiment, a configuration different from the first embodiment will be specifically described here.
[0224]
60 to 63 are flowcharts showing the operation of the client apparatus 111 in the fifth embodiment.
FIGS. 64 to 65 are flowcharts showing the operation of the device in the fifth embodiment.
Hereinafter, the operation of the network system according to this embodiment will be described with reference to these flowcharts.
[0225]
First, the overall operation of the client apparatus 111 in this embodiment will be described with reference to FIG.
In the present embodiment, in particular, the processing in step S6107 and step S6108 is added to the operation in the first embodiment (see FIG. 28).
[0226]
In step S6107, it is determined whether or not the acquired event is an event notification reception from the device (response from the device to the event notification destination registration request performed in the search result processing in step S2606).
If it is determined that an event notification has been received from the device, an event notification reception process described later is performed (snubbing S6108).
Thereafter, the process returns to step S6101, and the client apparatus 111 again waits for an event to occur.
[0227]
FIG. 61 is a flowchart showing the search request transmission process in step S2604 of FIG.
This process is the same as the process in the fourth embodiment.
[0228]
Next, the search result processing in step S6106 of FIG. 60 will be described in more detail using the flowchart of FIG.
[0229]
In FIG. 62, it is determined whether one or more devices matching the search condition have been found as a result of the device search (step S6301). If no device that matches the search condition is found, a message (not shown) indicating that the corresponding device has not been found is displayed (step S6315), and the process is terminated.
[0230]
On the other hand, if it is determined in step S6301 that one or more devices have been found, the search results (location information and attribute information of the corresponding device) are stored in the hard disk 211.
For example, when a search result as shown in FIG. 14 is obtained, it is stored in the hard disk 211.
Thereafter, a state acquisition process is executed for each search result stored in the hard disk 211 by the processing from the subsequent processing step S6303.
[0231]
In the status acquisition process in the present embodiment, the client apparatus 111 issues an event notification destination registration request to the device indicated by the search result, acquires an event notification returned from the device as a response thereto, and This is a program for superimposing and displaying a device icon corresponding to the current state on the layout bitmap according to the device state information included in the event notification.
[0232]
When the status acquisition process is started, first, the search results stored in the hard disk 211 in step S6302 are referred to, and whether or not all search results have been processed, that is, in the stored search results. It is determined whether or not the event notification destination registration process has been completed for all the IP address devices included (step S6303). Here, when all the search results have been processed, this processing is terminated.
[0233]
On the other hand, if it is determined that there is a search result that has not yet been processed, device information (location information and attribute information) for one device is acquired from the unprocessed search result (step S6304).
Further, an event notification destination registration packet as shown in FIG. 66 is transmitted to the IP address included in the acquired attribute information (step S6305).
For example, when the search result shown in FIG. 14 is processed, the IP address is “19.2.1.2.1”, and an event notification destination registration packet is transmitted to this IP address.
[0234]
Here, the event notification destination registration packet shown in FIG. 66 includes notification condition information for indicating event notification when an event occurs, and event notification destination information for indicating the notification destination. Including.
That is, the first field 6701 indicates that the content of this packet is event notification destination registration. A second field 6702 is a tag indicating that the subsequent information is information indicating a notification condition. The third field 6703 stores information representing actual notification conditions. The fourth field 6704 is a tag indicating that the subsequent information is information indicating an event notification destination. The last field 6705 stores information indicating the network address of the actual notification destination.
[0235]
In FIG. 66, the event notification destination registration packet issuance destination device is the color printer 101 indicated by the IP address “192.2.1.2.1”, and the notification condition information includes “out of paper” of the color printer 101. ”And“ paper jam ”, and the IP address“ 192.1, 2.16: 1025 ”representing the client is set in the event notification destination information.
[0236]
After sending the event notification destination registration packet, the system waits to receive an event notification destination registration response packet. In step S6306, when an event notification destination registration response packet as shown in FIG. 67 is received from the target device, the device name (NM) information included in the location information of the search result and the received response packet include Based on the device status information, an appropriate bitmap icon corresponding to the device status is selected from the various device icons shown in FIG. 52 (step S6307).
[0237]
Here, FIG. 67 is a diagram illustrating an example of a response packet transmitted from the device to the client apparatus 111.
This response packet is transmitted to the event notification destination registration packet (see FIG. 66 above) transmitted from the client apparatus 111 to the device in order to return device state information indicating the state of the device at that time.
[0238]
In FIG. 67, the first field 6801 indicates that the content of this packet is a response to event notification destination registration. A second field 6802 is a tag indicating that the subsequent information is information indicating the state of the device. The last field 6803 stores information indicating an actual device state (for example, an error code).
[0239]
For example, when the client apparatus 111 receives the response packet as shown in FIG. 67, the device status information in the response packet indicates “out of paper”. Therefore, in step S6307, as shown in FIG. A device icon corresponding to the LBP 1110 is selected.
[0240]
Next, it is determined whether or not the client apparatus 111 can display a layout bitmap corresponding to block (BL) information as location information, that is, whether or not the layout bitmap information corresponding to block (BL) information is held. Is determined using the information table of FIG. 15 (step S6308).
In the present embodiment, the location information that can display the layout bitmap is location information including information indicated by “1401” in FIG. If the location information does not include this, it is determined whether or not the unknownMAP shown in FIG. 20 has already been displayed (step S6312).
[0241]
If the unknownMAP is not yet displayed in the above determination, the unknownMAP is displayed in the area “1901” in FIG. 20 (step S6313). The device icon selected in step S6307 is displayed in the area “1902” in FIG. 20 (step S6314). In this case, an icon of a device whose layout map has not been normally displayed, that is, whose location information has not yet been registered, is displayed here.
[0242]
On the other hand, if it is determined in step S6308 that the layout bitmap can be displayed, it is determined whether a layout bitmap corresponding to the block (BL) information in the location information has already been displayed (step S6309). If it is determined that it has not been displayed yet, a layout bitmap corresponding to the block (BL) information is displayed on the screen (step S6310).
For example, when the search result of FIG. 14 is processed, the block (BL) information of the color printer 101 (LBP 1100) found by the search is “2-1”, so the layout bit of FIG. Display the map.
[0243]
Based on the coordinate information (MAP) in the location information, the device icon selected in step S6307 is displayed in an overlapping manner at the corresponding display position on the layout bitmap (step S6311).
For example, when the search result of FIG. 14 is processed, the coordinate information (MAP) of the color printer 101 (LBP 1100) is “10X + 10Y”. If the result of inquiring the status to the color printer 101 (LBP 1100) is “out of paper”, a device bitmap icon indicating the out of paper is displayed at the position shown in FIG. By displaying this device bitmap icon so as to overlap the previous layout bitmap, the search result can be displayed as shown in FIG.
[0244]
Next, the operation of the event notification receiving process shown in step S6108 of FIG. 60 will be described in detail with reference to the flowchart of FIG.
[0245]
63, when the client apparatus 111 first receives an event notification packet as shown in FIG. 68 from the device to which the event notification destination has been registered by the process of step S6305 in FIG. Event information representing the content of the event that occurred in the device is acquired from the notification packet (step S6401), and location information representing the position of the device is acquired (step S6402).
[0246]
Here, as shown in FIG. 68, each device monitors its own state change, and when an event that matches the notification condition registered from the client device 111 occurs, the device is also registered from the client device 111. The event information is sent to the notification destination. At this time, the location information held in the device as the position of the device is also packetized and transmitted.
FIG. 68 shows a packet sent when a paper out event occurs in the color printer 101 (LBP 1100).
[0247]
Next, the client apparatus 111 determines whether or not device information having information matching the location information acquired from the event notification packet exists in the search result stored in the hard disk 211 by the device search process. Judgment is made (step S6403). This is because the event notification destination registration process may be performed from another client apparatus 113, and is sent from the device location information indicated by the search result of itself and the event generation destination device. This is because the location information does not always match.
[0248]
If it is determined in step S6403 that there is no device information that matches the location information in the event notification packet, this process is terminated.
[0249]
On the other hand, if there is matching device information, the event information (status information) acquired from the event notification packet and the device name (NM) information included in the location information are shown in FIG. An appropriate device icon corresponding to the device state is selected from the various device icons (step S6404).
[0250]
Then, the layout bitmap corresponding to the acquired location information is displayed on the screen, and at the corresponding display position on the layout bitmap based on the coordinate information (MAP) in the location information, in step S6404. The selected device icon is displayed in a superimposed manner (step S6405).
Thereby, the display of the device icon is changed according to the change in the state of the device.
[0251]
For example, when the event notification destination registration process is performed, the device status information sent from the color printer 101 as a response is “active”, and a device icon representing the active status is displayed on the screen. If the color printer 101 runs out of paper while the printer is running, the device icon indicating that the printer is in operation is changed to the icon indicating that the paper is cut as shown in FIG. 54 and displayed.
[0252]
Next, the operation of event notification destination registration processing on the device side will be described in detail with reference to the flowchart of FIG.
Here, for simplicity of explanation, the color printer 101 will be described among various devices.
[0253]
After the power is turned on, the color printer 101 opens a reception port for receiving the event notification destination registration packet as shown in FIG. 66 from the client device 111, and enters a receivable state (step S6501). When an event notification destination registration packet is received from a certain search client PC (step S6502), the notification conditions and notification destination information included in the event notification destination registration packet are stored in an event notification destination table as shown in FIG. (Step S6503).
[0254]
Here, the event notification destination table shown in FIG. 69 is held on the device side, and communication protocol information is stored in addition to the notification condition registered from the client device 111 and the network address of the notification destination. ing.
[0255]
Next, the color printer 101 investigates the state of the device at the time when the event notification destination registration packet is received, and determines the state information to be notified (step S6504).
For example, when the “out of paper” state has occurred, the state information indicating “out of paper” is determined as information to be notified.
[0256]
Next, a response packet as shown in FIG. 67 including the current state information to be notified is generated (step S6505). Then, the generated response packet is transmitted to the client device 111 that issued the event notification destination registration packet (step S6506), and the event notification destination registration packet is receivable again.
[0257]
Next, the event notification process performed on the device side will be described in detail with reference to the flowchart of FIG.
Here, for the sake of simplicity, the description will be given focusing on the color printer 101 among various devices.
[0258]
The color printer 101 monitors its own state change and determines whether or not a state change event has occurred (step S6601). Here, when a state change event occurs, the event notification destination table as shown in FIG. 69 is referred to search for a client apparatus to be notified of the generated event (step S6602).
[0259]
Then, it is determined whether or not there is one or more client devices to be notified of the event (step S6603). Here, it is determined whether an event that has occurred in the color printer 101 is a client device registered as a notification condition in the event notification destination table. If such a client device exists, an event notification packet as shown in FIG. 68 including the event information is generated (step S6604) and transmitted to all the client devices to be notified (step S6604). Step S6605). Thereafter, the process returns to step S6601, and again enters a state of waiting for occurrence of a state change event.
[0260]
As described above, according to the present embodiment, it is possible to notify the user of the position of the device on the network 100 in an easy-to-understand manner and to notify the user of the device information.
Further, since the device state is acquired by event notification from the device, it is possible to reduce traffic on the network 100 as compared to the case of acquiring by polling.
[0261]
In the fourth and fifth embodiments, the client apparatus 111 holds the layout bitmap. However, the server apparatus holds the layout bitmap as in the second embodiment. Also good.
In the fourth and fifth embodiments, only the layout bitmap corresponding to the block (BL) hierarchy is stored. However, as in the third embodiment, each layer of the hierarchical position information is stored in each hierarchy. A corresponding layout bitmap may be held and reflected in the search result display of the client device 111.
[0262]
<Other embodiment 1 of this invention>
The device search system in the first to fifth embodiments can be realized by using a technique such as that used in the WWW technique. In this case, the server device 112 is configured to include a WWW server, a database function (DBMS), and a gateway function that mediates the WWW server and the DBMS.
[0263]
The WWW server provides a search screen composed of HTML or XML to the client device.
The client device displays a search screen provided from the WWW server by the browser software, and the user of the client device executes a device search using the displayed search screen.
[0264]
Various data (MAP, icon, etc.) exchanged between the server apparatus, client apparatus, and device is composed of HTML, XML, etc., and HTTP is used as a protocol for exchanging data.
[0265]
In order to realize a function that the general-purpose browser software does not have on the client device side, for example, there is a form of using an applet (Applet) which is one of JAVA technologies.
[0266]
<Other embodiment 2 of this invention>
In the first to fifth embodiments, the computer apparatus having the configuration shown in FIG. 3 is used as an example of the client apparatus 111 and the server apparatus 112. For example, a scanner, a facsimile, a printer, or the like is used. These devices may have the function of the client device 111 or the function of the server device 112.
[0267]
Specifically, for example, when the scanner is configured to have the function of the client device 111, the state of the printer that prints the document data read by the scanner, or the facsimile that transmits the document data read by the scanner It becomes possible to know the state.
[0268]
<Other embodiment 3 of this invention>
A storage medium storing software program codes for realizing the functions of the host and terminal of the first to fifth embodiments is supplied to the system or apparatus, and the computer (or CPU or MPU) of the system or apparatus stores the storage medium. Needless to say, the present invention can also be achieved by reading and executing the program code stored in the medium.
In this case, the program code of the software itself realizes the functions of the first to fifth embodiments, and the program code itself and means for supplying the program code to a computer, for example, A storage medium storing the program code constitutes the present invention.
[0269]
As a storage medium for storing the program code, for example, a floppy disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used.
[0270]
Further, the device control program on the network 100 in the first to fifth embodiments may be executed by the PC 200 (see FIG. 3 above) by a program installed from the outside.
In this case, the information group including the above program is loaded into the PC 200 from a storage medium such as a CD-ROM, flash memory, floppy disk, or an external storage medium via a network such as e-mail or personal computer communication. Even in such a case, the present invention is applied.
[0271]
FIG. 70 is a diagram showing a memory map of a CD-ROM as an example of the storage medium.
In FIG. 30, “9999” is an area in which directory information is stored, and indicates the positions of the subsequent areas 9998 and 9997.
An area 9998 is an area where an installation program is stored, and an area 9997 is an area where a network device control program is stored.
[0272]
When the network control program to which the present invention is applied is installed in the PC 200, first, the installation program stored in the area 9998 where the installation program is stored is loaded into the PC 200 and executed by the CPU 202. The
Then, the installation program executed by the CPU 202 reads the network device control program from the area 9997 where the network device control program is stored, and stores it in the hard disk 211.
[0273]
Further, by executing the program code read by the computer, not only the functions of the first to fifth embodiments are realized, but also an OS running on the computer based on the instruction of the program code. It goes without saying that the case where (operating system) or the like performs part or all of the actual processing and the functions of the first to fifth embodiments are realized by the processing.
Further, after the program code read from the storage medium is written to the memory provided in the extension function board inserted in the computer or the function extension unit connected to the computer, the function extension is performed based on the instruction of the program code. It goes without saying that the CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing, and the functions of the first to fifth embodiments are realized by the processing.
[0274]
【The invention's effect】
As described above, according to the present invention, in response to the occurrence of an event for a job, hierarchical position information that hierarchically represents the position of the device and an event indicating the event from the device to the information processing apparatus. By transmitting the information, the information processing apparatus can display the event indicated by the event information according to the occurrence of the event based on the hierarchical position information. It is possible to easily recognize a specific location, and it is possible to easily and accurately recognize an event regarding a job requested by the device.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of a device search system to which the present invention is applied in a first embodiment.
FIG. 2 is a diagram for explaining a configuration of an example of a network system in which the device search system can operate.
FIG. 3 is a block diagram showing an internal configuration of a general personal computer.
FIG. 4 is a diagram for explaining an example of hierarchical position information;
FIG. 5 is a diagram for explaining the position of each device in the 2-1 block on the second floor.
FIG. 6 is a diagram for explaining the position of each device in the 2-2 block on the second floor.
FIG. 7 is a diagram for explaining the position of each device in the 1-1 block on the first floor.
FIG. 8 is a diagram for explaining the position of each device in the 1-2 block on the first floor;
FIG. 9 is a diagram for explaining hierarchical position information and attribute information managed by the server apparatus.
FIG. 10 is a diagram for describing hierarchical position information and attribute information registered by a device.
FIG. 11 is a diagram for explaining a device search input screen.
FIG. 12 is a diagram for explaining a specific example of a device search input screen.
FIG. 13 is a diagram for explaining an example of a device search condition.
FIG. 14 is a diagram for explaining an example of a device search result.
FIG. 15 is a diagram for describing a bitmap and hierarchical position information managed by a client device.
FIG. 16 is a diagram for explaining a layout bitmap (first floor-1 floor) managed by a client device;
FIG. 17 is a diagram for explaining a layout bitmap (first floor-2 floor) managed by a client device;
FIG. 18 is a diagram for explaining a layout bit map (second floor-2 floor) managed by a client device;
FIG. 19 is a diagram for explaining a layout bitmap (second floor-2 floor) managed by a client device;
FIG. 20 is a diagram for explaining a layout bitmap (unknownMAP) managed by a client device;
FIG. 21 is a diagram for explaining device icons managed by a client apparatus;
FIG. 22 is a diagram for explaining a position of a device icon.
FIG. 23 is a diagram for explaining a device search result;
FIG. 24 is a block diagram showing an internal configuration of a device.
FIG. 25 is a flowchart for explaining registration processing;
FIG. 26 is a flowchart for explaining the overall operation of the server device;
FIG. 27 is a flowchart for explaining database search processing;
FIG. 28 is a flowchart for explaining the overall operation of the client device;
FIG. 29 is a flowchart for explaining search result display processing;
FIG. 30 is a diagram illustrating an example of print job information issued by a client.
FIG. 31 is a diagram for explaining an event notification table managed by a device;
FIG. 32 is a diagram for explaining event notification notified from the device to the client apparatus;
FIG. 33 is a diagram for explaining an example of a display when a print end event is received.
FIG. 34 is a flowchart for explaining processing when an event is received by a client device;
FIG. 35 is a flowchart for explaining the overall operation of the device.
FIG. 36 is a flowchart for explaining processing when a device event occurs;
FIG. 37 is a flowchart for explaining the operation (search result display operation) of the client device in the second embodiment;
FIG. 38 is a flowchart for explaining the operation (display operation) of the client device;
FIG. 39 is a flowchart for explaining the operation of the server apparatus;
FIG. 40 is a diagram for explaining an example of a list of layout bitmaps corresponding to each hierarchy in the third embodiment.
FIG. 41 is a flowchart for explaining the operation of the client device;
FIG. 42 is a diagram for explaining an example (Example 1) of a layout bitmap prepared for each layer;
FIG. 43 is a diagram for explaining an example (example 2) of a layout bitmap prepared for each layer;
FIG. 44 is a diagram for describing an example (Example 3) of a layout bitmap prepared for each layer;
FIG. 45 is a diagram for explaining an example (Example 4) of a layout bitmap prepared for each layer;
FIG. 46 is a diagram for explaining an example (Example 5) of a layout bitmap prepared for each layer;
FIG. 47 is a diagram for explaining an example (Example 6) of a layout bitmap prepared for each layer;
FIG. 48 is a diagram for explaining an example (Example 7) of a layout bitmap prepared for each layer;
FIG. 49 is a diagram for describing an example (Example 8) of a layout bitmap prepared for each layer;
FIG. 50 is a diagram for explaining an example (Example 9) of a layout bitmap prepared for each layer;
FIG. 51 is a diagram for explaining an example (Example 10) of a layout bitmap prepared for each layer;
FIG. 52 is a diagram for explaining a device icon management table in the client device in the fourth embodiment;
FIG. 53 is a diagram for explaining an example (Example 1) of a layout bitmap display;
FIG. 54 is a diagram for describing an example (Example 2) of a layout bitmap display;
FIG. 55 is a flowchart for explaining the operation of the client device (search request transmission processing).
FIG. 56 is a flowchart for explaining the operation (search result processing) of the client device;
FIG. 57 is a flowchart for explaining the operation (state acquisition process) of the client device;
FIG. 58 is a diagram for explaining a response packet of a device.
FIG. 59 is a flowchart for explaining device operation;
FIG. 60 is a flowchart for explaining the operation (overall operation) of the client device in the fifth embodiment;
FIG. 61 is a flowchart for explaining an operation (search request transmission process) of the client device;
FIG. 62 is a flowchart for explaining the operation (search result processing) of the client device;
FIG. 63 is a flowchart for explaining an operation (event notification reception process) of the client device;
FIG. 64 is a flowchart showing device operation (event notification destination registration processing).
FIG. 65 is a flowchart showing device operation (event notification processing).
FIG. 66 is a diagram for explaining an event notification destination registration packet of the client device;
FIG. 67 is a diagram for explaining a response packet of a device;
FIG. 68 is a diagram for explaining an event notification packet of a device.
FIG. 69 is a diagram for explaining an event notification destination table managed by a device;
FIG. 70 is a diagram for explaining an example of a memory map in another embodiment;
[Explanation of symbols]
10 Server device
11 Database
12 Search module
13 Attribute registration module
20 Client device
21 Search request module
22 display modules
30 devices
31 Attribute transmission module
40 network

Claims (8)

A device that processes a job requested via a network,
Receiving means for receiving a job transmitted from the information processing apparatus on the network;
Transmission means for transmitting hierarchical position information representing the position of the job hierarchically and event information indicating the event to the information processing apparatus in response to the occurrence of an event for the job;
A device characterized by comprising: Among the events that occurred in the job, the information processing device further includes designation information receiving means for receiving information designating an event to be notified,
The device according to claim 1, wherein the transmission unit transmits event information to the information processing apparatus in response to occurrence of an event designated by information received by the designation information reception unit. A network system having at least a device for processing a job requested via a network and an information processing apparatus for monitoring the requested job;
The device is
Receiving means for receiving a job transmitted from the information processing apparatus;
Transmission means for transmitting hierarchical position information representing the position of the job hierarchically and event information indicating the event to the information processing apparatus in response to the occurrence of an event for the job;
Including
The information processing apparatus includes:
Transmitting means for transmitting a job to the device;
Receiving means for receiving hierarchical position information hierarchically representing the position of the device and event information indicating the event, which is information transmitted from the device in response to the occurrence of an event for the job; ,
Display means for displaying the event indicated by the event information based on the hierarchical position information received by the receiving means;
A network system comprising: A job processing method for processing a job requested via a network,
A receiving step of receiving a job transmitted from the information processing apparatus on the network;
A transmission step of transmitting, to the information processing apparatus, hierarchical position information that hierarchically represents its own position and event information indicating the event in response to the occurrence of an event for the job;
A job processing method. A specified information receiving step of receiving information specifying an event to be notified to the information processing apparatus among events generated in the job;
5. The job processing method according to claim 4, wherein in the transmission step, event information is transmitted to the information processing apparatus in response to occurrence of an event designated by the information received in the designation information reception step. A job monitoring method for monitoring a job requested via a network,
A first transmission step of transmitting a job to a device on the network;
A first reception step of receiving the job transmitted by the first transmission step;
In response to the occurrence of an event for the job received in the first receiving step, hierarchical position information that hierarchically represents its own position and event information indicating the event are displayed on the information processing apparatus on the network. A second transmission step of transmitting to
A second receiving step of receiving the second transmission before Symbol hierarchical location information and the event information transmitted by the step,
A display step of displaying an event indicated by the event information based on the hierarchical position information received by the second receiving step;
A job monitoring method comprising: A computer-readable storage medium storing a computer program for causing a computer to execute a job requested via a network,
The computer program is
A receiving step of receiving a job transmitted from the information processing apparatus on the network;
A transmission step of transmitting, to the information processing apparatus, hierarchical position information that hierarchically represents its own position and event information indicating the event in response to the occurrence of an event for the job;
A computer-readable storage medium characterized by causing a computer to execute. The computer program is
Among the events that occurred in the job, let the computer further execute a specified information receiving step for receiving information specifying an event to be notified to the information processing device,
8. The computer-readable storage according to claim 7, wherein the transmitting step transmits event information to the information processing apparatus in response to an event specified by the information received in the specified information receiving step. Medium.

Images