JP2007280045A - Server device, print controller, their control methods, computer program and storage medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a server device capable of notifying the end result of a job by an event even when a user logs out from a network and logs in again. <P>SOLUTION: The server device connected through a network with the print controller and a plurality of client devices comprises: a holding means for holding the list of the users who have logged in the plurality of client devices respectively; an updating means for respectively acquiring the login conditions of the plurality of client devices and updating the list; a reception means for receiving the inquiry of the login conditions of the user who requests printing to the print controller from the print controller; a specifying means for specifying the client device that the user logs in the list corresponding to the inquiry; and a transmission means for transmitting the information of the specified client device to the print controller. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a server device, a print control device, a control method thereof, a computer program, and a storage medium.

  In recent network environments, networks using DHCP (Dynamic Host Configuration Protocol) have become common. In a network using DHCP, when a PC (personal computer) joins the network, an IP address that is an identification number of the PC participating in the network is determined.

  In addition, systems for printing from a PC or the like to a printer via a network are widely used. In such an environment, there is an application that immediately notifies a print instruction obtained from a printer to a PC that has instructed printing.

  As a method for notifying a user who has instructed printing via a network, the following invention has been proposed in Patent Document 1. That is, in the client / server system, when an event subscription user is logged in, the event is transmitted to the client PC, and when the user logs out, the event transmission is stopped / invalidated (see Patent Document 1).

  In addition to this, there are the following methods more specifically.

<CJL job completion notification>
First, there is a job end notification according to CJL. The PC adds the assigned IP address to the print job and sends it to the printer. The printer that has received the print job sends a job end notification to the PC in accordance with the IP address added to the print job after printing is completed. The application on the PC that has received the notification notifies the user of the end of the job. In this way, in the CJL job end notification, a print completion notification to the user is made based on the IP address of the PC used by the user at the time of the print instruction given to the print job.

  However, the user is not always logged in to the same PC until receiving a job end notification. In other words, a network usage method in which the user logs out after a printing instruction from a PC on the network and logs in again after a predetermined time can be considered. In this case, the PC logs in to the network twice, and the same IP address is not necessarily assigned.

  Therefore, the job end notification from the printer is sent to the IP address assigned to the PC used by the user when creating the job, and the user who issued the print instruction does not receive the job end notification. There is a fear. In this case, when the IP address is assigned to a PC that is being used by another person, there is a problem that a job end notification is sent to the other person.

<CPCA job completion notification>
As another method, there is a job end notification according to CPCA (Common Peripheral Controlling Architecture) which is a control command group for office equipment.
In this method, the PC registers an event transmission to the printer before sending the print job, and the print job has a unique job ID (job identifier) consisting of an arbitrary character string or number corresponding to its own host name. Is sent to the printer. The printer that has received the print job with the job ID sends the event with the job ID to all PCs that can be connected to the printer via the network after printing is completed. The application on each PC that has received an event with a job ID looks at the job ID and finds a character string or number corresponding to its host name, and notifies the user that the job has ended. On the other hand, if the job ID does not correspond to its own host name, the job is discarded.

  Even in this method, if the user logs out of the PC after sending a print job and logs in to another PC, the host name of the job ID embedded in the event does not match the host name of the PC after re-login It becomes. Therefore, even if the application of the PC after re-login receives the event with the job ID, there is a problem that it cannot be determined that it is addressed to the own PC and is discarded.

  Further, the following method is also conceivable. First, all client PCs on the network register for job state change event notification to the device. On the device side, the job owner name is added to the job status change event and returned to the PC. The application of the client PC that has received the event notifies the user of the job result only when the job owner name added to the event matches the name of the currently logged-in user.

  According to this method, even when a user who has performed printing re-login to another PC, an event is transmitted to the re-login destination PC, and an application running on another PC can be used as long as the user name matches the owner name. Can report job results.

However, this is limited to the case where the user uses a common user name. For example, when the common user name “Guest” is used as the user name on the re-login destination PC, the notification cannot be received. . In addition, when a print instruction is issued with the user name “Guest”, the job result is notified regardless of who prints. Furthermore, when the owner name notified from the device is fixed to a specific name (eg “anonymous”) due to network or device restrictions, the login user name and the owner name may not match, and the result may be notified to the user. Can not.
JP 2004-199382 A

  As described above, conventionally, when the user logs out of the network and logs in again, it is difficult to reliably notify the job end result by an event.

  The present invention for solving the above-mentioned problems is, in one aspect of the embodiments, a server device connected to a print control device and a plurality of client devices via a network, and logs in each of the plurality of client devices. A print request from the print control apparatus to the print control apparatus. A receiving unit that receives an inquiry about a login status of a user; a specifying unit that specifies a client device to which the user is logged in in the list in response to the inquiry; and information about the specified client device in the print control device And transmitting means for transmitting to.

  In another aspect of the embodiments, the present invention for solving the above-described problem is a print control apparatus connected to a plurality of client apparatuses and a server apparatus via a network, from any one of the plurality of client apparatuses. A print request that includes at least information related to a user who has made the print request, a print control unit that causes a printing apparatus to execute a print process according to the print request, and a login of the user Inquiry means for inquiring the status to the server device, and a notification for notifying the client device of completion of the printing process when the client device to which the user is logged in is notified from the server device in response to the inquiry Means.

  The present invention for solving the above-described problems is a print control apparatus connected to a plurality of client apparatuses and a server apparatus via a network according to still another aspect of the embodiment. A print request from one client device, the print request including at least information relating to a user who has made the print request and identification information of the print request including the first host name of the first client device. A receiving unit that accepts, a printing control unit that causes a printing apparatus to execute a printing process according to the printing request, an inquiry unit that inquires the server apparatus about a login status of the user, and the server apparatus that responds to the inquiry from the user. Is notified of the second host name of the second client device to which the user is logged in. The completion notification of the print processing including the identification information obtained by replacing the hostname by said second host name, and a notification means for transmitting to the plurality of client devices.

  According to the present invention, even when the user logs out from the network and logs in again, the job completion result can be notified by an event.

  Hereinafter, a printing system according to an embodiment of the present invention will be described with reference to the drawings.

  FIG. 1 is a block diagram showing a configuration of a printing system according to an embodiment of the present invention. In FIG. 1, a server (hereinafter referred to as a print server) 101 is an information processing apparatus connected to a network 106 by a network cable. The print server 101 accumulates files used in the network 106 and monitors the use state of the network 106. In addition, a communication device capable of bidirectional communication with other devices connected to the network 106 is provided, and a plurality of printers are managed.

  The print server 101 further has a function of storing and printing a print job including print data for which a print request is issued from the clients 102 to 104. Also, only the job information that does not include print data is received from the clients 102 to 104 to manage the print order of the clients 102 to 104, and the transmission permission of the print job including the print data is notified to the client that has reached the print order. You can also Furthermore, a function is provided for acquiring statuses of the network printer 105 and various types of print job information and notifying the clients 102 to 104.

  The clients 102 to 104 are information processing apparatuses connected to the network 106 by a network cable such as Ethernet (registered trademark), and can execute various programs such as application programs. A printer driver having a function of converting print data into a printer language corresponding to the printer is installed. Here, the printer driver supports a plurality of printers. Furthermore, a communication device capable of bidirectional communication with other devices connected to the network 106 is provided.

  In the above, the print server 101 and the clients 102 to 104 are information processing apparatuses and can be realized by a general-purpose personal computer. The print server 101 can also have functions as clients 102 to 104. The print server 101 and the clients 102 to 104 store print control programs that perform different controls.

  In the following, for simplicity of explanation, the client 102 among the clients 102 to 104 will be described in particular. However, the explanation for the client 102 can be applied to the clients 103 and 104 in the same manner.

  Next, the network printer 105 is a printing apparatus and is connected to the network 106 via a predetermined network interface. The network printer 105 analyzes a print job including print data transmitted from the client 102, converts the print job into an image page by page, and prints each page. The network printer 105 may be any of various types such as a laser beam printer that employs an electrophotographic system, an inkjet printer that employs an inkjet system, and a printer that utilizes a thermal transfer system. Here, the network printer 105 may be realized as a single printing apparatus. Alternatively, it may be realized by a combination of a printing apparatus equipped with a printer engine and a printing control apparatus that analyzes a print job, converts an image page by page, supplies the image to the printing apparatus, and controls printing processing in the printing apparatus. .

  A print server 101, a client 102, a network printer 105, and the like are connected to the network 106. Network 106 is preferably implemented as a local area network (LAN).

  Next, an example of the hardware configuration of the print server 101 or the client 102 as the information processing apparatus and the network printer 105 will be described with reference to FIG.

  In FIG. 2, a print server 101 or client 102 as an information processing apparatus and a network printer 105 are connected by a network 106.

  Reference numeral 200 denotes a CPU as control means for controlling the overall operation of the print server 101 and client 102. The CPU 200 executes an application program, a printer driver program, an OS, a network printer control program of the present invention, and the like stored in the hard disk (HD) 205. Also, the RAM 202 is controlled to temporarily store information, files, etc. necessary for program execution.

  Reference numeral 201 denotes a ROM which is a storage unit, and stores therein various data such as a program such as a basic I / O program, font data used for document processing, and template data. Reference numeral 202 denotes a RAM as temporary storage means, which functions as a main memory, work area, and the like of the CPU 200.

  A floppy (registered trademark) disk (FD) drive 203 serves as a storage medium reading unit. Via this FD drive 203, a program or the like stored in a floppy (registered trademark) disk (FD) 204 as a storage medium can be loaded into the computer system as a client. Note that the storage medium is not limited to the FD, and may be any CD-ROM, CD-R, CD-RW, PC card, DVD, IC memory card, MO, memory stick, and the like. The FD 204 stores a computer-readable program.

  Reference numeral 205 denotes an external storage device, which is a hard disk (HD) that functions as a large-capacity memory, and stores an application program, a printer driver program, an OS, a network printer control program, related programs, and the like. Furthermore, a spooler is secured here. This spooler is a client spooler in the client 102, and is a server spooler in the print server 101. In the print server 101, job information received from the client 102 is stored, and a table for performing order control is also generated and stored in the external storage device.

  A keyboard (instruction input unit) 206 is used by the user to input device control command instructions to the client 102 and to the print server 101 by an operator or administrator. A display (display unit) 207 displays a command input from the keyboard 206, a printer status, and the like. A system bus 208 controls the data flow between the blocks.

  In this embodiment, the network printer control program and related data can be loaded from the FD 204 directly into the RAM 202 and executed. In addition to this, every time the network printer control program is operated from the FD 204, the network printer control program already installed in the HD 205 may be loaded into the RAM 202.

  The medium for storing the network printer control program may be a CD-ROM, CD-R, PC card, DVD, or IC memory card in addition to the FD. Further, it is possible to store the network printer control program in the ROM 201, configure it as a part of the memory map, and execute it directly by the CPU 200.

  Next, an example of the hardware configuration of the network printer 105 as a print control apparatus will be described. The network printer 105 includes a connection unit 226, a data control unit (printer engine) 225, an operation unit 224, an external memory 223, a PCPU 220, a PRAM 222, and a PROM 221, which will be described in detail later. These components are connected to each other via a system bus 227.

  A printer CPU (PCPU) 220 is responsible for overall control of the network printer 105. The PCPU 220 transmits an image signal to the data control unit 225 from a printer control command (transmission data) received by the connection unit 226 based on a control program stored in the PROM 221 or the external memory 223 described later.

  A printer RAM (PRAM) 222 is provided as a main memory of the PCPU 220 with a temporary storage area for various data used as a work data area when the PCPU 220 executes control. The external memory 223 is also connected as an option, and stores font data, an emulation program, form data, and the like. A printer ROM (PROM) 221 is a printer internal memory, and stores various data, a printer control program for controlling the network printer 105, and the like, similar to the external memory.

  The data control unit 225 is a printer engine, is controlled by the PCPU 220, receives an image signal output via the system bus 227 from a control program stored in the PROM 221 or the external memory 223, and performs an actual printing process. The data control unit 225 may be stored in the print control apparatus, or may be realized in a printing apparatus as a printer installed outside the print control apparatus, and may be connected to the print control apparatus by a cable or the like.

  The operation unit 224 includes an input unit such as an operation panel and an operation switch, and a display unit such as an LED and a liquid crystal panel, and receives an operation of the operator and displays a result. The operator can instruct and confirm the setting of the network printer 105 corresponding to the present embodiment via the operation unit 224.

  A connection unit 226 is connected to the connection unit 210 such as the information processing apparatus 101 via the network 106, and can receive a print control command (transmission data) or notify the internal status of the network printer 105. It is.

  In addition, software that realizes the same function as each of the above devices can be used as an alternative to a hardware device.

[First Embodiment]
The first embodiment of the present invention will be described below as an embodiment related to CJL job completion notification. First, FIG. 3 is a diagram illustrating an example of a job script created by the print server 101 or the client 102.

  Before and after the print data 304, job attributes are set using a PJL (Printer Job Language) command. The format for setting job attributes is “@PJL command =“ parameter ””. For commands that do not require parameters, “=” and the following can be omitted. For example, the “JOB NAME” command 302 has ““ + UDP172.024... ”” As a parameter, and the parameter is handled as job identification information. Further, they are treated as the same job until an “EOJ NAME” command 305 having the same parameters is received.

  In FIG. 3, the parameter of the “JOB NAME” command 302 is composed of a 26-byte protocol address and a 40-byte job ID. The format of the protocol address specifies the notification protocol (UDP in the example of FIG. 3) with the first 4 bytes. Then, the protocol-defined address (port number 11D7 in the IP address 192.024.159.166 in the example of FIG. 3) is designated by the following 26 bytes, and the rest is filled with spaces. The job ID is made up of an arbitrary number or character string designated by the client that submitted the job, and is different for each job and identifies the job. In the case of FIG. 3, the job ID is “10000005PC-ABC 00000002”.

  The device that has received such a job script notifies the end of job processing using the parameters specified by the “JOB NAME” command 302 after the end of job processing. That is, the parameter portion of the “JOB NAME” command 302 is transmitted as data to the protocol address described in the parameter by a predetermined method of the UDP protocol.

  Next, an example of a data structure of a packet used when information is transmitted from the information processing apparatus will be described with reference to FIG. In FIG. 4, 401 is a header portion for identifying a packet. Reference numeral 402 denotes an operation code portion in which a code for specifying the operation of the packet is set. Reference numeral 403 denotes a size portion in which the parameter size is set. Reference numeral 404 denotes a parameter section, in which parameters corresponding to the operation command 402 are set.

  Next, an example of the operation of the network printer 105 corresponding to this embodiment will be described with reference to FIG. In the following, for the sake of simplicity of explanation, a case where job completion is notified as an example of an event will be described. The processing shown in the flowchart of FIG. 7 is realized by reading a corresponding program stored in the PROM 221 or the external memory 223 into the PRAM 222 and executing it by the PCPU 220.

  In step S <b> 701, it is determined whether data is received from the client 102 as the information processing apparatus via the network 106 and the connection unit 226. If it is determined that data has been received (“YES” in step S701), the process proceeds to step S702. On the other hand, when data is not received (“NO” in step S701), monitoring of data reception is continued.

  Next, in step 702, the PCPU 220 analyzes the data received in step S701, and determines whether or not the analysis target in the data is data relating to job settings. Here, if the “JOB NAME” command 302 or the “OUTPUT PRINTER” command 303 is included in the PJL command, it is determined that the data is related to job setting.

  If it is determined that the data is related to job setting (“YES” in step S702), the process proceeds to step S703, where the parameters of the “JOB NAME” command 302 and “OUTPUT PRINTER” command 303 are determined from the received data. Specifically, for example, a job ID (“10000005PC-ABC 00000002” in the example of FIG. 3) or the like can be acquired from the parameters of the “JOB NAME” command 303. Also, the “OUTPUT PRINTER” command 303 For example, the user name (“U1234” in the example of FIG. 3), etc. can be acquired from these parameters, etc. Information such as the acquired job ID and user name is stored in a storage area prepared in advance in the PRAM 222. Set and retained as job settings.

  If it is determined in step S702 that the data is not related to job setting (“NO” in step S702), the process proceeds to step S704. In step S704, the PCPU 220 analyzes the data received in step S701, and determines whether the analysis target in the data is print data. In the case of a job script as shown in FIG. 3, the data sandwiched between the “OUTPUT PRINTER” command 303 and the “EOJ NAME” command 305 is determined as print data. If the print data is determined, the process proceeds to step S705, and the data control unit 225 executes print processing using the print data. If it is determined that the data is not print data (“NO” in step S704), the process returns to step S701 and the above processing is repeated.

  After the printing process in step S705 is completed, the process proceeds to step S706. In step S706, the print server 101 is inquired about the information of the client 102 currently used by the user by sending a request packet 1200 as shown in FIG. The request packet 1200 is generated by the PCPU 220, and first, a code “Get_Machine_info” is set in the operation code section 402 according to the format of FIG. 4 (1202 of FIG. 12). This code “Get_Machine_info” is a code indicating an information request of the information processing apparatus currently used by the user specified by the parameter unit 404. Further, the user name (“U1234” in the example of FIG. 3) saved in the storage area in the PRAM 222 is set in the parameter unit 404 (1204 in FIG. 12). The header part 401 and the size part 403 are set as appropriate (1201 and 1204 in FIG. 12). The created request packet is transmitted to the print server 101 through the network 106 via the connection unit 226.

  The print server 101 creates a response packet 1300 as shown in FIG. 13 from the stored user name and client list, and transmits information on the client currently used by the user to the network printer 105. This response procedure will be described later with reference to FIG. The network printer 105 receives the response packet 1300 transmitted from the print server 101 via the connection unit 226 through the network 106.

  Next, in step S707, the response packet 1300 received by the CPU 220 is analyzed, and the IP address is extracted from the information of the information processing apparatus currently used by the user described in the parameter unit 1304.

  Next, in step S708, an event packet 1400 as shown in FIG. 14 is sent to the IP address acquired in step S707 to perform event distribution. The event packet 1400 is generated by the PCPU 220, and first, the code “EV_JOB_STATE_CHANGE” is set in the operation code section 402 according to the format of FIG. 4 (1402 of FIG. 14). The code “EV_JOB_STATE_CHANGE” is a code indicating a predetermined job state change event. Further, the header portion 401 and the size portion 403 are set as appropriate (1401 and 1403 in FIG. 14). In the parameter section 404, complete indicating the completion is set in the attribute state indicating the job state (1404 in FIG. 14), and success is set in the reason attribute indicating the reason for the state change (1405 in FIG. 14). Further, the job ID stored in step S703 is set in the job ID (1406 in FIG. 14). Note that the job settings stored in step S703 are initialized in conjunction with the sending of the event packet.

  As described above, the network printer 105 can notify the client 102 that the printing process has been completed.

  Next, an example of the operation of the print server 101 corresponding to the present embodiment will be described with reference to FIG. The processing shown in the flowchart of FIG. 8 is realized by reading the corresponding program stored in the ROM 201 or the hard disk device 205 into the RAM 202 and executing it by the CPU 200.

  First, in step S801, the number of users logged in to the network 106 is acquired by the print server 101, and it is determined whether or not the number of users has increased or decreased. For example, when the network uses a Windows (registered trademark) domain controller, the name of the currently logged-in user can be listed using the function NetSessonEnum () prepared in advance.

  If the number of users is increasing in step S801 (“increase” in step S801), the process proceeds to step S802. In this case, since a user who has newly logged into the network 106 has been confirmed, the user list held in a previously secured area of the RAM 202 is updated in step S802. This user list is a list for managing the login status of each client connected on the network 106, and holds the user name of the login user, the host name of the client, the IP address assigned to the client, and the like. . Therefore, for a user who is newly confirmed to log in, the user name, client host name, IP address, etc. are added to the list, and the list is updated. Thereafter, the process proceeds to step S804.

  On the other hand, when the number of users is decreasing in step S801 (“decrease” in step S801), the process proceeds to step S803. In step S803, the acquired user name and the user list stored in the RAM 202 are compared to identify the user who has logged out, and the user is deleted from the user list. Thereafter, the process proceeds to step S804.

  In this way, the print server 101 can acquire the login status of each client on the network 106 and update the user list based on the acquired login status.

  If there is no increase or decrease in the number of users in step S801 (“no increase / decrease” in step S801), the process proceeds to step S804.

  In step S804, it is determined whether a user inquiry has been received from the network printer 105 or the client 102. More specifically, it is determined whether or not a request packet 1200 as shown in FIG. 12 is received through the connection unit 210 via the network 106. The CPU 200 analyzes the received request packet 1200 and confirms whether the operation code part 402 is set to “Get_Machine_info” according to the format of FIG. If “Get_Machine_info” is set, it can be determined that the request is a user inquiry request.

  If it is determined in step S805 that a user inquiry has been received (“YES” in step S804), the process proceeds to step S805. On the other hand, if a user inquiry has not been received (“NO” in step S804), the process returns to step S801.

  In a succeeding step S806, the print server 101 answers the user inquiry. First, the CPU 200 of the print server 101 extracts the user name ("U1234" in the case of FIG. 12) from the parameter part 404 of the received request packet 1200. Based on the extracted user name, a list is searched for the user list stored in the RAM 202, and information on the client to which the user is currently logged in is extracted. Next, a response packet 1300 as shown in FIG. 13 is created in accordance with the format shown in FIG. Specifically, “Rep_Get_Machine_info” indicating a response to the “Get_Machine_info” command is set in the operation code section 402 (1302 in FIG. 13). Also, the header 401 and the size 403 are set as appropriate (1301, 1303 in FIG. 13). Further, an IP address and a host name which are addresses on the network 106 of the client used by the user are set in the parameter unit 404 (1304 in FIG. 13). The response packet created in this way is returned to the destination of the request command through the connection unit 210 and the network 106.

  As described above, according to the present embodiment, even when the user who issued the print instruction changes the login destination client, the event packet can be transmitted to the re-logged-in client. As a result, the client at the re-login destination can notify the user of a change in the job status in real time using the event packet that has been delivered to the user who is currently logged in to the own apparatus.

[Second Embodiment]
Next, a second embodiment of the present invention will be described as an embodiment related to CPCA job completion notification. The configuration of the printing system in this embodiment is the same as that shown in FIGS. 1 and 2, and the basic operation is also the same as that in the first embodiment. Hereinafter, configurations and functions unique to the present embodiment will be described.

  FIG. 5 is a diagram illustrating an example of a job script corresponding to the present embodiment. The job script 500 is composed of a combination of packets as shown in FIG. In the first packets 501 to 503 of the job script 500, “Set_job” for setting job attributes is specified in the operation code portion 402, respectively. In the parameter section 404, a job owner name, a document name, and a job ID are set as setting attributes, and each setting value is given. That is, “U1234” is set as the job owner name in the packet 501, and “Test Print” is set as the document name in the packet 502. In the packet 503, “00000001PC-ABC ____ 0000001” is set as the job ID.

  In the packet 504 of FIG. 5, “Job_Start” is specified in the operation code portion 402. In this case, a drawing command is specified in the parameter portion 404. After the packet 504, when the operation code part 402 is “Job_End” (506), the drawing command is completed.

  Upon receiving the job script 500 as shown in FIG. 5, the network printer 105 creates job information according to the job settings and performs printing according to the drawing command.

  In addition, with reference to FIG. 15, a configuration example of an event distribution registration packet transmitted from the client 102 to the network printer 105 corresponding to the present embodiment will be described. The operation code part 402 is designated with “Append_To_List” meaning event delivery registration, and the parameter part 404 is set with an event occurrence target (OBJ), an event type (EV), a delivery destination (IP), and the like. The client 102 can register such an event that is desired to be transmitted by transmitting such an event distribution registration packet to the network printer 105 that is a monitoring device.

  Next, a configuration example of the job ID will be described with reference to FIG. The job ID 600 includes a job number 601 (8 bytes) uniquely determined in the client PC from the top, a host name 602 (16 bytes), and a job ID 603 (8 bytes) issued by the client.

  Next, an example of processing in the network printer 105 corresponding to the present embodiment will be described with reference to FIG. The processing shown in the flowchart of FIG. 9 is realized by reading the corresponding program stored in the PROM 221 or the external memory 223 into the PRAM 222 and executing it by the PCPU 220.

  In step S <b> 901, the network printer 105 determines whether data has been received from the client 102 via the connection unit 226 through the network 106. If it is determined that data has been received (“YES” in step S901), the process proceeds to step S902. On the other hand, when data is not received (“NO” in step S901), data reception monitoring is continued.

  Next, in step S902, the PCPU 220 analyzes the data received in step S901, and determines whether or not the analysis target in the data is data related to job settings. If the operation code portion 402 of the received data is “Set_job”, it is determined that the job is set.

  If it is determined that the job is set (“YES” in step S902), the process proceeds to step S903. On the other hand, if it is not determined that the job is set (“NO” in step S902), the process proceeds to step S904.

  In step S 903, the job setting value is extracted from the received data and stored in a storage area prepared in advance in the PRAM 222. In the example of FIG. 5, packets 501 to 503 in the received job script correspond to data relating to job settings. Accordingly, in step S 903, the setting value set in the parameter unit 404 in each packet is extracted and stored in the storage area in the PRAM 222. Thereafter, the process returns to step S902.

  In step S904, the PCPU 220 analyzes the data received in step S901, and determines whether the analysis target in the data is print data. In the case of a job script as shown in FIG. 5, when the operation code portion 402 is “job_start”, it is determined as print data. If it is determined as print data (“YES” in step S904), the process proceeds to step S905. In step S905, the data control unit 225 executes print processing according to the drawing command 505. On the other hand, if it is determined that it is not print data (“NO” in step S904), the process proceeds to step S909.

  After the printing process in step S905 is completed, the process proceeds to step S906. In step S906, the print server 101 is inquired by sending a request packet shown in FIG.

  The print server 101 creates a response packet as shown in FIG. 13 from the stored user name and client list based on the response procedure described later with reference to FIG. The client information is transmitted to the network printer 105. The network printer 105 receives the response packet transmitted from the print server 101 via the connection unit 226 through the network 106.

  In step S907, the response packet received by the CPU 220 is analyzed, and the host name is extracted from the information on the information processing apparatus currently used by the user described in the parameter unit 1304. In step S903, the job setting value saved in the storage area in the RAM 222 is rewritten with the host name from which the job ID is extracted, and is overwritten and saved. That is, the job ID indicated by the packet 503 in FIG. 5 is rewritten with the host name acquired in step S906.

  Next, in step 908, the PCPU 220 generates an event packet 1400 as shown in FIG. 14 according to the format of FIG. 4, and transmits it to the IP address of the event distribution registration destination. In this event packet 1400, a code “EV_JOB_STATE_CHANGE” is set in the operation code portion 402. This “EV_JOB_STATE_CHANGE” is a code indicating a predetermined job state change end event. Also, the header part 401 and the size part 403 are set as appropriate. Furthermore, complete indicating the completion is set in the attribute state indicating the job state in the parameter unit 404, and success is set in the reason attribute indicating the reason for the state change. Further, the job ID rewritten in step S907 is set as the job ID. In addition to the transmission of the event packet, the job setting stored in step S903 is initialized.

  Next, the case where it is determined in step S904 that the data is not print data and the process proceeds to step S909 will be described. In step S909, the data received in step S901 is analyzed by the PCUP 220, and it is determined whether the processing target in the data is data related to event distribution registration. This determination can be made based on whether or not the operation code part 402 is “Append_To_List”.

  If it is determined in step S909 that the event distribution is registered (“YES” in step S909), the process proceeds to step S910. In step S910, the PCPU 220 extracts the event delivery destination IP address, event type, and the like from the packet data received in step S901. In the example of FIG. 15, an IP address 1506 and an event type 1505 are extracted. The extracted information is set and stored in an event distribution destination storage area prepared in advance in the PRAM 222. If it is determined in step S909 that the event distribution is not registered (“NO” in step S909), the process returns to step S901 and the above processing is repeated.

  As described above, according to the present embodiment, even when the user who has issued the print instruction changes the login destination client, the event packet information addressed to the client is changed in accordance with the change destination client. be able to. As a result, the client at the re-login destination can notify the user of a change in the job status in real time using the event packet that has been delivered to the user who is currently logged in to the own apparatus.

[Third Embodiment]
In the first and second embodiments described above, a case has been described in which a user is logged in to any client on the network 106 at the end of a job in the device. However, in the first and second embodiments, a client that returns an event may not be found if the user is not logged in to any client when the job ends.

  Therefore, in the present embodiment, a case where the user is not logged in at the end of the job will be described. Since the system configuration and basic operation in the present embodiment are the same as those in the first embodiment, only different points will be described for the sake of simplicity.

  FIG. 10 is a flowchart showing an example of the operation of the network printer 105 corresponding to this embodiment. The processing shown in the flowchart of FIG. 10 is realized by reading the corresponding program stored in the PROM 221 or the external memory 223 into the PRAM 222 and executing it by the PCPU 220.

  In step S <b> 1001, it is determined whether data is received from the client 102 as the information processing apparatus via the network 106 and via the connection unit 226. If it is determined that data has been received (“YES” in step S701), the process proceeds to step S1002. On the other hand, when data is not received ("NO" in step S1001), the process proceeds to step S1009.

  The processing from step S1003 to step S1006 is the same as that from step S703 to step S706 of FIG. 7 in the first embodiment. In step S1007 following step S1006, the PCPU 220 analyzes the response packet 1300 received in step S1006 and determines whether the user is currently logged in. This determination can be made based on whether or not data exists in the parameter portion 1304 of the response packet 1300. If the user is not logged in, the print server 101 does not have a value to return, so no data exists in the parameter portion 1304 of the response packet 1300. Therefore, whether or not the user is logged in can be determined based on the presence or absence of the data.

  If it is determined in step S1007 that the user is not logged in (“NO” in step S1007), the process proceeds to step S1008. In step S1008, the IP address area held in the job setting storage area of the PRAM 222 in step S1003 is initialized and stored again. Then, it returns to step S1001 and repeats a process.

  If it is determined in step S1007 that the user is logged in (“YES” in step S1007), the process proceeds to step S1012. Step S1012 and step S1013 correspond to step S707 and step S708 in FIG.

  Next, processing after step S1009 will be described. In step S1009, it is determined whether there is an unsent event. Specifically, the PCPU 220 analyzes the contents of the job settings stored in the job setting storage area in the PRAM 222 and checks whether there is an entry in which the IP address area is initialized. If an entry in which the IP address area is initialized is found, it is determined that there is an unsent event. On the other hand, when an entry in which the IP address area is initialized is not found, it is determined that there is no unsent event.

  If it is determined in step S1009 that there is no unsent event (“NO” in step S1009), the process returns to step 1001 and is repeated. On the other hand, when it is determined in step S1009 that there is an unsent event (“YES” in step 1009), the process proceeds to step S1010. In step S1010, the print server 101 is inquired as to whether or not the user has logged in again. Specifically, the inquiry can be made in the same manner as the processing in step S1006, that is, the processing in step S706 of FIG.

  In subsequent step S1011, it is determined based on the received response packet 1300 whether or not the target user has re-logged in to any client. This determination is the same as that in step S1007. If it is determined that the user has not re-logged in ("NO" in step 1011), the process returns to step S1001 and continues. On the other hand, if it is determined that the user has logged in again ("YES" in step 1011), the process proceeds to step S1012.

  Next, processing in the print server 101 corresponding to the present embodiment will be described. The operation of the print server 101 corresponding to this embodiment is basically the same as the operation described with reference to FIG. 8 in the first embodiment. However, the process in step S806 is different.

  In this embodiment, in step S806, the CPU 200 of the print server 101 extracts the user name (“U1234” in the case of FIG. 12) from the parameter portion 404 of the received packet. Based on the extracted user name, a list is searched for the user list stored in the RAM 202, and information on the client to which the user is currently logged in is extracted. Next, a response command packet as shown in FIG. 13 is created according to the format shown in FIG. Specifically, “Rep_Get_Machine_info” indicating a response to the “Get_Machine_info” command is set in the operation code section 402 (1302 in FIG. 13). Also, the header 401 and the size 403 are set as appropriate (1301, 1303 in FIG. 13). Further, when the user is found in the user list, the parameter unit 404 is set with the IP address and host name of the client to be used (1304 in FIG. 13). On the other hand, if it is not found in the user list, nothing is set in the parameter part, and 0 is set in the size. Thereby, it can be notified that the user is not currently logged in to any client. The response packet created in this way is returned to the destination of the request command through the connection unit 210 and the network 106.

  As described above, according to the present exemplary embodiment, even when an event to be notified by the device occurs when the user who has issued the print instruction is not logged in to the network, the event can be notified at the time of re-login without being discarded. Therefore, necessary information can be notified to the user without omission.

[Fourth Embodiment]
In the above description, a job end event has been described as an example of an event for ease of explanation. This job end event basically occurs only once per job. However, in actual operation, as a job status change event, it is common to notify a plurality of users of a status before the end of the job, such as “printing”, “suspending”, or “pausing”. Therefore, when a multi-state event notification is applied to the third embodiment, when the user logs in again, a plurality of events that have not been transmitted to the user arrive at the same time.

  In addition, as a characteristic of the network, a part of the time series may be reversed and reach the destination even if the packets are transmitted almost simultaneously. If a large number of events arrive in reverse time series, the user may be confused if the notification is made as it is.

  Therefore, this embodiment is characterized in that only the latest state is notified when the user logs in again. Hereinafter, processing corresponding to this embodiment will be described. FIG. 11 is a flowchart showing an example of the operation of the network printer 105 corresponding to the present embodiment. The process shown in the flowchart of FIG. 11 is realized by reading a corresponding program stored in the PROM 221 or the external memory 223 into the PRAM 222 and executing it by the PCPU 220.

  In FIG. 11, steps S1101 to S1105 are the same as steps S1001 to S1005 of FIG. 10 in the third embodiment, and thus description thereof is omitted here.

  In step S1105, print processing is performed. In step S1106, it is determined whether a job state change event has occurred. For example, in a case where printing is stopped due to no paper or printing is temporarily stopped due to an external request, the state of the job held inside the device is changed. The network printer 105 includes means for monitoring the execution status of the printing process such as various sensors as a job status. When a change in the execution status of the printing process is detected, it is determined that an event has occurred. The sensor includes, for example, a sensor for detecting the presence or absence of recording paper in the tray, a sensor for detecting paper jam in the recording paper conveyance process, and a sensor for detecting the remaining amount of toner or ink. included. The PCPU 220 controls and manages the execution status of the printing process and receives information from various sensors.

  If it is determined in step S1106 that an event has occurred (“YES” in step S1106), the job status is updated in step S1107. The job status is saved in the job setting storage area in the PRAM 222, and the saved content is updated with the current job status detected in step S1106. In this embodiment, the job status includes, for example, “printing”, “paused”, “resume”, “interrupting”, “preparing”, “deleting”, “completed”, and the like. The reason for reaching the job state is included. The reason for reaching the current job state includes, for example, “normal”, “user instruction”, “error”, “upper limit error”, and the like. If it is determined in step S1106 that no event has occurred (“NO” in step S1106), the process returns to step S1105 and printing processing is continued.

  The subsequent processing from step S1108 to step S1115 is the same as the processing from step S1006 to step S1013 in FIG. 10, and thus the description thereof is omitted here.

  After the job setting storage process is performed in step S1110, or after the event distribution is performed in step S1115, the process proceeds to step S1116. In step S1116, it is determined whether the printing process in step S1105 has ended. This print processing end determination can be made based on whether or not the job status held in the job setting storage area in the PRAM 222 indicates the end of printing. In other words, when the printing process in step S1105 is not continued, for example, when the job status is “complete” or “error”, it can be determined that printing is finished.

  If it is determined in step S1116 that printing has ended (“YES” in step S1116), the process returns to step S1101 and continues. If it is determined that the printing is not finished (“NO” in step S1116), the process returns to step S1105 to continue the printing process. As a result, the job status is updated each time an event occurs when the printing process continues, and if the user is logged in, the event is distributed at any time. If the user is not logged in, the job status at the time of login is distributed. Will be.

  In the above embodiment, even if an event to be notified by the device occurs when the user who has instructed printing is not logged in to the network, the event is notified when the user logs in again without being discarded. Further, by only being notified of the latest state in the job, the user can know only new and useful information.

[Other Embodiments]
Note that the present invention can be applied to a system including a plurality of devices (for example, a host computer, an interface device, a reader, and a printer), and a device (for example, a copying machine and a facsimile device) including a single device. You may apply to.

  The object of the present invention can also be achieved by supplying a storage medium storing software program codes for realizing the above-described functions to the system, and the system reading and executing the program codes. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the storage medium storing the program code constitutes the present invention. In addition, an operating system (OS) running on a computer performs part or all of actual processing based on an instruction of the program code, and the above-described functions are realized by the processing.

  Furthermore, you may implement | achieve with the following forms. That is, the program code read from the storage medium is written into a memory provided in a function expansion card inserted into the computer or a function expansion unit connected to the computer. Then, based on the instruction of the program code, the case where the above-described functions are realized by the CPU included in the function expansion card or the function expansion unit performing part or all of the actual processing is also included.

  When the present invention is applied to the storage medium, the storage medium stores program codes corresponding to the flowcharts described above.

1 is a diagram illustrating a configuration example of a printing system corresponding to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a hardware configuration of a printing system corresponding to an embodiment of the present invention. It is a figure which shows an example of the data structure of the job script corresponding to the 1st Embodiment of this invention. It is a figure which shows an example of a structure of the packet data corresponding to embodiment of this invention. It is a figure which shows an example of a structure of the job script corresponding to the 2nd Embodiment of this invention. It is a figure which shows an example of a structure of job ID corresponding to the 2nd Embodiment of this invention. 6 is a flowchart illustrating an example of an operation of the network printer 105 corresponding to the first embodiment of the present invention. 6 is a flowchart illustrating an example of an operation of the print server 101 corresponding to the first embodiment of the present invention. It is a flowchart which shows an example of operation | movement of the network printer 105 corresponding to the 2nd Embodiment of this invention. 10 is a flowchart illustrating an example of an operation of the network printer 105 corresponding to the third exemplary embodiment of the present invention. It is a flowchart which shows an example of operation | movement of the network printer 105 corresponding to the 4th Embodiment of this invention. FIG. 6 is a diagram illustrating an example of a data configuration of a request packet transmitted from the client to the print server 101, corresponding to the first embodiment of the present invention. FIG. 3 is a diagram illustrating an example of a data configuration of a response packet transmitted from the print server 101 to the client 102, corresponding to the first embodiment of the present invention. It is a figure which shows an example of a structure of the packet data transmitted at the time of event delivery from the network printer 105 corresponding to the 1st Embodiment of this invention. It is a figure which shows the structural example of the packet for event delivery registration transmitted to the network printer 105 from the client 102 corresponding to the 2nd Embodiment of this invention.

Claims (16)

A server device connected to a print control device and a plurality of client devices via a network,
Holding means for holding a list of users logged into each of the plurality of client devices;
Update means for acquiring login statuses of the plurality of client devices, respectively, and updating the list;
Receiving means for receiving an inquiry about the login status of a user who has made a print request to the print control apparatus from the print control apparatus;
In response to the inquiry, a specifying unit that specifies a client device to which the user is logged in in the list;
A server apparatus comprising: a transmission unit configured to transmit the specified information of the client apparatus to the print control apparatus.   The server apparatus according to claim 1, wherein the information on the client apparatus includes at least an address on the network.   The transmission means transmits information indicating that the user is not currently logged in to the print control apparatus when the identification means cannot identify the client apparatus to which the user is logged in. The server apparatus according to claim 1 or 2. A print control device connected to a plurality of client devices and server devices via a network,
A receiving unit that receives a print request from any of the plurality of client devices and includes at least information about a user who has made the print request;
Print control means for causing a printing apparatus to execute print processing in response to the print request;
Inquiry means for inquiring the server device about the login status of the user;
Print control comprising: notifying means for notifying the completion of the print processing to the client device when the client device to which the user is logged in is notified from the server device in response to the inquiry apparatus. When the server device notifies that the user has not logged in to any of the plurality of client devices, the inquiry unit performs the inquiry again,
5. The notification unit according to claim 4, wherein the notification unit suppresses notification of completion of the printing process until the server device is notified of the client device to which the user is logged in in response to the inquiry again. The printing control apparatus described. The print control means includes an acquisition means for acquiring a print processing execution status in the printing apparatus,
The inquiry means makes the inquiry when the execution status changes,
In the case where the client device to which the user is logged in is notified from the server device in response to the inquiry, the notification unit notifies the client device only of the latest execution status at the time of the notification. The printing control apparatus according to claim 4 or 5. A print control device connected to a plurality of client devices and server devices via a network,
The print request from the first client device among the plurality of client devices, the print request including at least information related to a user who has made the print request and the first host name of the first client device. Receiving means for receiving a print request including identification information;
Print control means for causing a printing apparatus to execute print processing in response to the print request;
Inquiry means for inquiring the server device about the login status of the user;
In response to the inquiry, when the second host name of the second client device to which the user is logged in is notified from the server device, the first host name is replaced with the second host name. A printing control apparatus comprising: a notification unit configured to transmit a notification of completion of the printing process including the identification information to the plurality of client apparatuses. A control method of a server device connected to a print control device and a plurality of client devices via a network,
Obtaining login status of each of the plurality of client devices;
An update step of updating a list of users logged in each of the plurality of client devices, which is held in a holding unit;
Receiving from the print control device an inquiry about the login status of the user who made a print request to the print control device;
In response to the inquiry, a specifying step of specifying a client device to which the user is logged in in the list;
And a transmitting step of transmitting the specified information of the client device to the print control device.   9. The server device control method according to claim 8, wherein the information on the client device includes at least an address on the network.   In the transmitting step, information indicating that the user is not currently logged in is transmitted to the print control device when the client device to which the user is logged in cannot be identified in the identifying step. The server device control method according to claim 8 or 9. A control method of a print control apparatus connected to a plurality of client apparatuses and server apparatuses via a network,
Receiving a print request from any of the plurality of client devices, the print request including at least information about a user who has made the print request;
A printing control step for causing a printing apparatus to execute a printing process according to the printing request;
An inquiry step of inquiring the server device about the login status of the user;
And a notification step of notifying the client device of the completion of the print processing when the server device is notified of the client device to which the user is logged in in response to the inquiry. Control method of the device. When the server device is notified that the user has not logged into any of the plurality of client devices, the inquiry is performed again in the inquiry step,
The printing control apparatus according to claim 11, wherein notification in the notification step is suppressed until the client apparatus to which the user is logged in is notified from the server apparatus in response to the inquiry again. Control method. The printing control step includes an acquisition step of acquiring an execution status of a printing process in the printing apparatus,
In the inquiry step, the inquiry is performed when the execution status changes,
In the notification step, when the client device to which the user is logged in is notified from the server device in response to the inquiry, only the latest execution status at the time of the notification is notified to the client device. The method for controlling a printing control apparatus according to claim 11 or 12, characterized in that: A control method of a print control apparatus connected to a plurality of client apparatuses and server apparatuses via a network,
The print request from the first client device among the plurality of client devices, the print request including at least information related to a user who has made the print request and the first host name of the first client device. A receiving step for receiving a print request including identification information;
A printing control step for causing a printing apparatus to execute a printing process according to the printing request;
An inquiry step of inquiring the server device about the login status of the user;
In response to the inquiry, when the second host name of the second client device to which the user is logged in is notified from the server device, the first host name is replaced with the second host name. A printing control apparatus control method, comprising: a notification step of transmitting a completion notification of the printing process including the identification information to the plurality of client apparatuses.   The computer program for making a computer perform the method in any one of Claims 8 thru | or 14.   A computer-readable storage medium storing the computer program according to claim 15.

Images