JP2010198622A - Output device and method of controlling the same, and storage medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To store output data and recipient identification information showing a plurality of recipients who receive the output data by being associated with each other, and to invalidate the output data by reception of the stored output data by the plurality of recipients. <P>SOLUTION: The output device includes: an input step to input the output data; an acceptance step of accepting recipient identification information showing the plurality of recipients who receive the output data inputted in the input step; a storage step of storing the output data inputted in the input step and the recipient identification information accepted in the acceptance step into a memory by being associated with each other; and an invalidation step of invalidating the output data stored in the memory according to output of the output data stored in the memory by the plurality of recipients shown by the recipient identification information stored by being associated with the output data. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

The present invention relates to an output device, a control method therefor, and a storage medium .

  In recent years, a local area network (LAN) in which computers are connected to each other has become widespread, and such a local area network is constructed over a building floor or an entire building, a group of buildings (premises), a region, or a larger area. be able to. Such networks are further interconnected to form a global network, the so-called “Internet”.

  In addition to computers, computer peripheral devices such as printers and facsimile machines are often connected to the LAN or the Internet, and can be used from a computer via a network.

  The computer peripheral devices connected to the network as described above are generally smaller than the number of computers or the number of users using the computers, and are shared by a plurality of computers or users.

By the way, when a document created on a computer in a network is handed over to another person, it is generally performed in one of the following two ways.
・ Print it yourself and hand it over or mail it.
・ Transfer the electronic file (document file) of the created document to the recipient or store it on the medium for output.

  However, there is a problem that the former is lacking in immediacy and the cost is generally increased when sending the output result.

  On the other hand, the latter has a problem that the application used to create the document file must be installed in the counterpart device.

  In order to solve the above problem, there may be a means of sending and outputting data to a printer or FAX near the recipient, and informing the recipient by telephone or the like. The problem remains.

  -Since the data is output from the computer peripheral device regardless of the recipient's convenience, the output result may be seen by a person other than the recipient, resulting in lack of confidentiality.

  Similarly, because the data is output from the computer peripheral device regardless of the recipient's convenience, a lot of output sheets accumulate in the output tray of the computer peripheral device.

The present invention has been made in view of the above problems, and stores output data and recipient identification information indicating a plurality of recipients receiving the output data in association with each other. It is an object of the present invention to provide an output device for invalidating output data, a control method therefor, and a storage medium according to being received by a plurality of recipients .

In order to solve this problem, for example, the output device of the present invention has the following configuration. That is,
An input means for inputting output data;
Receiving means for receiving recipient identification information indicating a plurality of recipients that receive the output data input by the input means;
Storage means for storing the output data input by the input means and the recipient identification information received by the receiving means in association with each other;
The output data stored in the storage means is invalidated in response to the output data stored in the storage means being output by a plurality of recipients indicated by the recipient identification information stored in association with the output data. And invalidating means .

According to the present invention, output data and recipient identification information indicating a plurality of recipients receiving the output data are stored in association with each other, and the stored output data is received by a plurality of recipients. Accordingly, the output data can be invalidated .

It is a conceptual diagram of the job generation software and its peripheral operation environment in the first embodiment. It is a figure which shows the example of a network structure which embodiment applies. It is a block block diagram of the personal computer in embodiment. It is a schematic diagram which shows the operation | movement relationship of the job generation software in 1st Embodiment. It is a flowchart figure which shows the flow of a process of the job issuing means in this embodiment. 6 is a flowchart showing a flow of processing of a “job issue notification” transmission unit in the first embodiment. 6 is a flowchart showing a flow of processing of a “job issue notification” receiving unit in the first embodiment. It is a flowchart which shows the flow of a process of the job execution instruction | indication means in 1st this embodiment. 12 is a flowchart showing a flow of processing of a “job issue notification” transmission unit in the second embodiment. 10 is a flowchart showing a flow of processing of a “job issue notification” receiving unit in the second embodiment. It is a flowchart which shows the flow of a process of the job execution instruction | indication means in 2nd this embodiment. It is a figure which shows the operation used by the job data and job execution instruction command data of 1st, 2nd this embodiment. It is a detailed data structure diagram of each operation. It is a detailed data structure diagram of each operation. It is a detailed data structure diagram of each operation. It is a detailed data structure diagram of each operation. It is a detailed data structure diagram of each operation. It is a figure which shows the job attribute used with job data and job execution instruction command data. It is a transmission sequence diagram of job data when a job is issued. It is a transmission sequence diagram of command data at the time of job execution instruction. 1 is a block configuration diagram of a printer according to a first embodiment. FIG. It is a figure which shows an example of the content of the job management table in FIG. It is a conceptual diagram of the job generation software and its peripheral operation environment in the third embodiment. It is a schematic diagram which shows the operation | movement relationship of the job generation software in 3rd Embodiment. It is a flowchart which shows the flow of a process of the job issuing means in 3rd this embodiment. 14 is a flowchart showing a flow of processing of a “job issue notification” receiving unit in the third embodiment. 14 is a flowchart illustrating a flow of processing of a job execution instruction unit according to the third embodiment. 14 is a flowchart illustrating a flow of processing of a job transfer unit in the third embodiment. It is a figure which shows the operation used by the job data of 3rd this embodiment, and job execution instruction command data. It is a structure figure of the job correction command data added in 3rd Embodiment. It is a figure which shows the job attribute used by the job data and job execution instruction command data in 3rd Embodiment. It is a figure which shows the transmission sequence of the command data at the time of the job attribute correction in 3rd Embodiment. 10 is a flowchart illustrating an operation processing procedure of a printer according to a third embodiment.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments according to the present invention will be described in detail with reference to the accompanying drawings.

<First Embodiment>
First, a network used by an embodiment of the present invention will be described. In the following, a personal computer (or a workstation) may be referred to as a PC.

  FIG. 2 shows an example of a network system to which the embodiment is applied.

  In the figure, reference numeral 102 denotes a printer having an open type architecture, which is equipped with a network board (NB) 101 for connection to a network. The NB 101 is connected to a local area network (LAN) 100 via a LAN interface such as an Ethernet (registered trademark) interface 10Base-2 having a coaxial connector or a 10Base-T having RJ-45.

  A plurality of personal computers (PCs) such as the PC 103 and the PC 104 are also connected to the network 100, and these PCs can communicate with the NB 101 under the control of the network operating system. Some printers are directly connected to a network, such as the printer 101, and some are connected to a PC, such as the printer 105.

  Typically, a LAN, such as LAN 100, provides services to a somewhat local user group, such as a user group on one floor in a building or multiple consecutive floors. For example, a wide area network (WAN) may be created as a user moves away from another user, such as when the user is in another building or prefecture. A WAN is basically an aggregate formed by connecting several LANs with a high-speed digital line such as a high-speed integrated services digital network (ISDN) telephone line.

  Therefore, as shown in FIG. 2, the LAN 100, the LAN 110, and the LAN 120 are connected via a modulation / demodulation (MODEM) / transponder 130 and a backbone 140 to form a WAN. These connections are simple electrical connections with several buses. Each LAN includes a dedicated PC, and although not necessarily required, usually includes a file server and a print server.

  Therefore, as shown in FIG. 2, the LAN 110 includes a PC 111, a PC 112, a file server 113, a network disk 114, a print server 115, a printer 116 and a printer 117. In contrast, LAN 120 includes only PC 121 and PC 122. Devices connected to the LAN 100, the LAN 110, and the LAN 120 can access the functions of other LAN devices via the WAN connection.

  An example in which a PC on the network generates a job for another device on the network in the network environment will be described. More specifically, this is a case in which printing is output from the PC 111 on the network 110 to a certain user on the network 100 by the printer 101 on the network 100.

  FIG. 3 is a block diagram showing the configuration of a PC on which the job generation software can be operated. All the PCs have the same configuration, but will be described as the PC 111 here for convenience.

  The PC 111 includes a CPU 501 that executes job generation software stored in a ROM 502 or a hard disk (HD) 511 or supplied from a floppy (registered trademark) disk drive (FD) 512, and is connected to a system bus 504. Control overall. Reference numeral 503 denotes a RAM which functions as a main memory, work area, and the like for the CPU 501.

  A keyboard controller (KBC) 505 controls an instruction input from a keyboard (KB) 509 or a pointing device (not shown). Reference numeral 506 denotes a CRT controller (CRTC) which controls display on a CRT display (CRT) 510. A disk controller (DKC) 507 is used to access a hard disk (HD) 511 and a floppy (registered trademark) disk controller (FD) 512 that store a boot program, various applications, editing files, user files, a network management program, and the like. Control. Reference numeral 508 denotes a network interface card (NIC) that exchanges data bidirectionally with an agent or a network device via the LAN 100.

  As described above, the above configuration is not limited to the PC 111, and other PCs have the same configuration.

<< Configuration of job generation software >>
Next, the configuration of the job generation software in this embodiment will be described.

  The job generation apparatus of the present invention is realized on a PC capable of executing job generation software as shown in FIG. The hard disk (HD) 511 stores a job generation software program according to the present application, which is an operation subject in all the descriptions below. In all the descriptions below, unless otherwise specified, the execution subject is the CPU 501 in hardware. On the other hand, the subject of software control is job generation software stored in the hard disk (HD) 511.

  The job generation software program according to the present application may be supplied in a form stored in a storage medium such as a floppy (registered trademark) disk or a CD-ROM. In this case, the floppy (registered trademark) disk shown in FIG. A program is read from a storage medium by a controller (FD) 512 or a CD-ROM drive (not shown) and installed in a hard disk (HD) 511.

  FIG. 1 is a conceptual configuration diagram when the PC 111 having the above configuration is viewed as job generation software and its peripheral function units. Note that other PCs have the same configuration.

  In the figure, reference numeral 2 denotes job generation software for issuing job data and issuing job data output execution instructions, which are stored in the hard disk 511 in FIG. 3 and executed by the CPU 501. Further, the RAM 503 is used for the job recognition memory 14 and the job execution information memory 15 inside the job generation software 2, and the RAM 503 is also used as a work area for the CPU 501 to execute the job generation software.

  Reference numeral 3 denotes an input unit that transmits user input to the job generation software 2 and is realized by the keyboard controller 505 in FIG. A network control unit 4 controls the network protocol and the network board when the job generation software 2 communicates with the network, and is realized by the CPU 501 and the NIC 508.

  In the configuration as described above, in the present embodiment, the job-related software is activated on the PC 111 and the PC 103, and the job is printed (output) on the printer 102 on the network to which the PC 103 is connected. Details of the operation procedure in this case will be described below.

  As a precondition before performing the following processing, it is assumed that the printer 102 has a job output function corresponding to the job generation software (details will be described later).

First, the outline of the operation of this embodiment will be described with reference to FIGS. 1 and 4. As shown in FIG.
-Job issuing means 10
"Job issue notification" transmission means 11
"Job issue notification" receiving means 12
Job execution instruction means 13
-Job authentication information memory 14
-Job execution information memory 15
Consists of.

  In the present embodiment, as shown in FIG. 4, the job issuing means (10) and the “job issue notification” transmitting means (11) are sequentially executed in the PC 111, and the “job issue notification” receiving means (12) is executed in the PC 103. And the job execution instructing means (13) are sequentially executed. In PC 111, user A executes job issuance to user B as a job issuer, and in PC 103, user B instructs job execution as a job recipient.

  The details of each means will be described below.

  The flowchart in FIG. 5 shows the processing procedure in the job issuing means.

  This job issuing means is easy to understand if it is considered to be incorporated in a printer driver, for example. That is, when printing is instructed on the application, it is triggered to start the operation.

  First, in step S101, a job issue instruction (on the application in use) by the user A = job issuer is input from the KBC 505. Hereinafter, input from the user A is executed from the KBC 505.

  In step S <b> 102, the user A receives information for identifying a job data transmission destination (print destination) device (in this case, the printer 102), and records the print destination device identification information in the job authentication information memory 14. As the print destination device identification information, the IP address of the print destination device or the name on the network (when there is a DNS) is used.

  Next, in step S 103, the user A inputs the designation of the job recipient and the identification information of the job recipient, and records the job recipient identification information in the job authentication information memory 14. When specifying a job recipient, an e-mail address book information or a list of network login names registered in a server, a user group, or the like is used. As job recipient identification information, an e-mail address, a login name, or the like is used. A plurality of job recipients can be designated.

  In step S <b> 104, an arbitrary password for job execution is input from the user A, and the password is recorded in the job authentication information memory 14. In step S105, a job ID for identifying the job being issued is generated, and the job ID is recorded in the job authentication information memory 14.

  In step S106, based on the data main body to be printed, the above information recorded in the job authentication information memory 14, and other job attached attributes (such as job issuer identification information and job generation date and time), Job data (including print data converted into a printer language interpretable by the printer 101) is issued, and the job data is transmitted to the print destination device in step S107. The transmitted job data is accumulated in the printer 102 (FIGS. 12 to 18 regarding the data structure of the job data issued in step 106 and FIG. 19 regarding the transmission sequence executed in step S107. To show).

  Next, the “job issue notification” transmission means will be described with reference to the flowchart of FIG. This means is a procedure for transmitting a “job issue notification” for notifying the PC 111 from the PC 111 that the job has been issued by the job issuing means.

  First, in step S201, printing destination device identification information, job ID, job recipient identification information, and password are acquired from the job authentication information memory 14.

  In step S202, the number of job recipients is substituted into a variable N. In step S203, if variable N ≠ 0, step S204 is executed, and if variable N = 0, this means is terminated.

  In step S204, the print destination device identification information, the job ID, and the password are transmitted as a “job issue notification” to the job recipient via the network. A specific method for transmitting the “job issue notification” via the network is realized by using an e-mail or a messaging service of a server or a user group.

  In step S205, the variable N is decreased by 1, and the process proceeds to step S203.

  Next, the “job issue notification” receiving means (easy to understand when considered as the PC 103 side) in the flowchart of FIG. 7 will be described.

  In step S301, the fact that the “job issue notification” has been received is displayed to user B.

  In step S302, print destination device identification information, job ID, and password are acquired from the received “job issue notification”.

  In step S303, the acquired information is recorded in the job execution information memory 15.

  Next, the job execution instructing means (PC 103 side) will be described with reference to the flowchart of FIG.

  In step S401, print destination device identification information, a job ID, and a password are acquired from the job execution information memory 15.

  In step S402, job execution instruction command data is generated based on the acquired information and job recipient = user B identification information.

  In step S403, the job execution instruction command data is transmitted to the print destination device (printer 102). The data structure of the job execution instruction command data is shown in FIG. 12, FIG. 17, FIG. 18, and the transmission sequence thereof is shown in FIG.

  On the other hand, the printer 102 has a structure as shown in FIG.

  In the figure, reference numeral 200 denotes a CPU that controls the entire apparatus. Reference numeral 202 denotes a RAM used as a work area of the CPU 200, and a job management table 202a is secured here as shown. Reference numeral 203 denotes a hard disk for storing print data as a file. Reference numeral 101 denotes the NB described above, and 204 denotes an operation panel having a switch for performing various settings and a display operation panel for displaying messages and the like. Reference numeral 205 denotes an image memory for developing a bitmap image for printing output, 206 denotes a printer engine interface, and 207 denotes a printer engine.

  FIG. 22 shows the contents of the job management table. As shown in the figure, the job management table corresponds to one line for one job, and includes a job ID, a reception time, an issuer (user A in the above embodiment), a password set by the user A, and recipients (a plurality of recipients). The print data file name stored in the HD 203 as a file.

  Since this printer 102 can set a plurality of recipients for one job, information specifying a plurality of recipients is stored in the recipient column and a print instruction is issued from each recipient. When received, a flag indicating whether or not printing is completed is provided for the recipient. In the illustrated case, there are three recipients AAA, BBB, and CCC, and “0” is set to indicate a state in which there is no print instruction from any of them. For example, when there is a print instruction from the user AAA, the print processing is performed, and when the printing is normally completed, the flag for the user AAA is set to “1”. Then, when the flags of all users become “1”, the corresponding job is deleted from the job management table 202a, and the file (print data) stored in the HD 203 is deleted.

  In the above configuration, when the printer 102 receives information about a print job from the network, the printer 102 adds the job to the job management table 202a based on the information included in the received information, and stores the actual print data in the hard disk 203. Store as.

  If there is a job execution instruction (determined by examining the header) from the network, does it exist in the management table in which the job ID, password, and request source information included therein are stored? Whether or not an authentication process is performed, and a job that passes the authentication process is printed.

  As a result, according to the present embodiment, when a document is transferred from the user A to the user B via the network, data in a format output from the printer is directly transmitted to the printer. It is only necessary to perform an operation such as printing. Therefore, it is not necessary to install the application used by the user A on the PC used by the user B who is the recipient, and the transmission is performed in an electronic data format instead of a printed document. Allows document exchange.

Second Embodiment 2
In the first embodiment, information necessary for job authentication and job execution instruction such as job ID and password is transmitted as “job issue notification” from the job issuer side = PC 111 to the job recipient side = PC 103. Job execution instruction command data was generated on the job recipient side.

  In the second embodiment, an embodiment in which job execution instruction command data itself is generated on the job issuer side = PC 111 will be described. That is, in this example, the process of generating the job execution instruction command is eliminated in the process on the job recipient side, and the job execution instruction command sent from the issuer side is simply output to the printer.

  The configuration of the job generation software related to the execution environment is the same as that of the first embodiment.

  Hereinafter, details of each means in the present embodiment will be described.

  The job issuing means is the same as in the first embodiment (see the flowchart in FIG. 5 and the first embodiment). First, the “job issue notification” transmission means will be described with reference to the flowchart of FIG.

  In step S501, print destination device identification information, job ID, job recipient identification information, and password are acquired from the job authentication information memory 14.

In step S502, the number of job recipients is substituted into a variable N. In step S503, if variable N ≠ 0, step S504 is executed, and if variable N = 0, this means is terminated. In step S504, job execution instruction command data is generated for the job recipient based on the print destination device identification information, job ID, and password (details of the data structure of the job instruction execution command data are shown in FIGS. 17 and shown in FIG.
In step S505, the job execution instruction command data is transmitted as a “job issue notification” via the network. A specific method for transmitting the “job issue notification” via the network is realized by using an e-mail or a messaging service of a server or a user group.

  In step S506, the variable N is decreased by 1 and the process proceeds to step S503.

  Next, the “job issue notification” receiving means in the flowchart of FIG. 10 will be described.

  In step S601, the fact that the “job issue notification” has been received is displayed to user B. In step S602, job execution instruction command data is acquired from the received “job issue notification”. In step S603, the acquired job execution instruction command data is recorded in the job execution information memory 15.

  Next, job execution instruction means will be described with reference to the flowchart of FIG.

  In step S701, job execution instruction command data is acquired from the job execution information memory 15. In step S702, the job execution instruction command data is transmitted to the print destination device. The job execution instruction command data transmission sequence is as shown in FIG.

  As described above, according to the second embodiment, the same effects as those of the first embodiment can be obtained, and the processing on the recipient side can be simplified.

<Third Embodiment>
In the first and second embodiments, the final printout is performed when the recipient issues a print instruction. In other words, once the issuer has issued a print job, the management of the job is up to the recipient, and the issuer cannot intervene. In some cases, there is a problem that jobs are accumulated on the printer side.

  In the third embodiment, an example for solving this will be described.

  In order to simplify the description, the network configuration is the same as in FIG. 2, and the job issuing side is the PC 111, the recipient side PC is 103, and the printer that actually prints is 102.

<< Configuration of job generation software >>
The configuration of the job generation software in the third embodiment will be described.

FIG. 23 is a conceptual configuration diagram in the third embodiment when the PC 111 is viewed as job generation software and its peripheral function units. The difference from the first embodiment (FIG. 1) is that a transfer unit 16 for “job issue notification” is added. That is, the software implemented by the PC 111 is
-Job issuing means 10
"Job issue notification" transmission means 11
"Job issue notification" receiving means 12
Job execution instruction means 13
-Job authentication information memory 14
-Job execution information memory 15
"Job issue notification" transfer means 16
Consists of.

  In the third embodiment, as shown in FIG. 4, the job issuing unit 10 and the “job issue notification” transmitting unit 11 are sequentially executed in the PC 111, and the “job issue notification” receiving unit 12 is executed in the PC 103. After that, the job execution instructing unit 13 or the “job issue notification” transferring unit 16 is executed as desired by the user. In the PC 111, the user A executes job issuance to the user B as a job issuer, and in the PC 103, the user B executes job printing or “job issue notification” as a job recipient. Instruct transfer.

  Hereinafter, details of the operation processing contents of each means will be described.

  The flowchart in FIG. 5 shows the processing procedure in the job issuing means.

  First, in step S1101, a job issue instruction (on the application in use) by the user A = job issuer is input from the KBC 505. Hereinafter, input from the user A is executed from the KBC 505.

  In step S <b> 1102, the user A receives information for identifying a job data transmission destination (print destination) device (in this case, the printer 102), and records the print destination device identification information in the job authentication information memory 14. As the print destination device identification information, the IP address of the print destination device or the name on the network (when there is a DNS) is used.

  Next, in step S1103, the user A inputs the designation of the job recipient and the identification information of the job recipient, and records the job recipient identification information in the job authentication information memory 14. When specifying a job recipient, an e-mail address book information or a list of network login names registered in a server, a user group, or the like is used. As job recipient identification information, an e-mail address, a login name, or the like is used. A plurality of job recipients can be designated.

  In step S <b> 1104, the job execution permission number is calculated based on the input number of job recipients and recorded in the job authentication information memory 14. In step S 1105, the job expiration date is input from the user A, and the job expiration date is recorded in the job authentication information memory 14. In step S 1106, an arbitrary password for job execution is input from the user A, and the password is recorded in the job authentication information memory 14.

  In step S 1107, a job ID for identifying the job being issued is generated, and the job ID is recorded in the job authentication information memory 14.

  In step S1108, based on the data main body to be printed, the above information recorded in the job authentication information memory 14, and other job attached attributes (such as job issuer identification information and job generation date / time), Job data is issued, and in step S1109, the job data is transmitted to the print destination device (printer 102). Note that the data structure of the job data issued in step S1108 is as shown in FIG. 19 regarding the transmission sequence executed in FIG. 29, FIG. 13 to FIG. 17, FIG. 30, and step S1109.

  The transmitted job data is accumulated in the printer 102, and is removed (erased) from the printer 102 when the expiration date of the input job expires or the job execution permission count becomes zero.

  The “job issue notification” transmission means in the third embodiment is the same as that in the first embodiment, and the details are referred to the first embodiment.

  Next, the “job issue notification” receiving means (processing on the PC 103 side) in the third embodiment will be described with reference to the flowchart of FIG.

  First, in step S1301, the fact that the “job issue notification” has been received is displayed to the user B. In step S1302, print destination device identification information, job ID, job expiration date, and password are acquired from the received “job issue notification”.

  In step S1303, the acquired information is recorded in the job execution information memory 15.

  Next, the job execution instruction means (PC 103 side) will be described with reference to the flowchart of FIG.

  First, in step S1401, print destination device identification information, job ID, and password are obtained from the job execution information memory 15. In step S1402, job execution instruction command data is generated based on the acquired information and job recipient = user B identification information. In step S1403, the job execution instruction command data is transmitted to the printing destination device. Next, in step S1404, job correction attribute command data is generated in order to reduce the count of the permitted number of executions of the job by one. Finally, in step S1405, the job attribute correction command data is transmitted to the printing destination device.

  The data structures of the job execution instruction command data and the job attribute correction command data are as shown in FIGS. 29, 13 to 17, and 30. The transmission sequence is as shown in FIGS.

  Next, the “job issue notification” transfer means will be described with reference to the flowchart of FIG. This means is a procedure for transferring the “job issue notification” to another user C when the “job issue notification” is received by the “job issue notification” receiving means.

  First, in step S1501, print destination device identification information, job ID, job expiration date, and password are obtained from the job execution information memory 15. In step S1502, the user B inputs a job transfer destination.

  In step S1503, job attribute correction command data for changing the job recipient of the job is generated.

  In step S1504, the job attribute correction command data is transmitted to the printing destination device.

  In step S1505, the print destination device identification information, job ID, and password are transmitted to the job transfer destination as a “job issue notification” via the network. A specific method for transmitting the “job issue notification” via the network is realized by using an e-mail or a messaging service of a server or a user group.

  It can be understood from the above processing that only the person who has received the job issue notification can transfer the job issue notification.

  The data structure of the job attribute correction command data is shown in FIGS. 29, 30, and 31, and the transmission sequence is as shown in FIG.

  On the other hand, in addition to the configuration of FIG. Then, a counter variable column for counting the job expiration date and the number of job executions is added to the job management table 202a.

  Then, the current date and time is obtained from the timer, the expiration date of each job is compared, and the job whose expiration date has passed is deleted from the memory. When a job execution command is received, a job that matches the data included in the command is read and executed (print processing based on the corresponding print data is performed).

  When there is a job attribute correction command, the corresponding record in the table corresponding to the correction location included in the command is corrected. For example, in the case of an instruction to reduce the number of job executions, the counter variable of the corresponding job is decreased by “1”, and when it becomes “0”, the job is deleted. In the case of a command indicating a change in the recipient of a job, the recipient who has instructed the change is deleted from the recipient record in the job management table, and a new recipient who has received the change instruction is registered. Processing will be performed.

  A specific processing example is shown in FIG.

  First, in step S2001, it is determined whether information is received from the network. If not, the process proceeds to step S2002, and the timer time is compared with the expiration date of each job registered in the management table 202a to determine whether there is a job that has passed the expiration date. If there is an expired job, in step S2003, the job is deleted from the management table 202a, and the print data file is deleted from the HD 203.

  If it is determined in step S2001 that some information has been received, the process proceeds to step S2004. If it is determined that the information is job issuance data, the job is received in step S2005 and the print data portion is displayed. Are stored in the HD 203 as a file. In step S2006, the job is registered in the job management table 202a.

  If it is determined that the data is not job issue data, the process advances to step S2007 to determine whether it is a job execution command. If it is determined that the command is a job execution command, the sender of the job execution command (PC 103 in the above embodiment) is included in the job recipient field indicated by the job ID specified by the command, and In addition, authentication processing is performed by determining whether the passwords also match. If this authentication process passes, in step S2009, the corresponding job is registered in the print queue.

  Although the description will be omitted, in the printer 102 according to the embodiment, when a job is registered in the print queue, a processing program for performing print processing for the job is separately operated in the registration order.

  If it is determined that the command is not a job execution command, the process advances from step S2007 to step S2010 to determine whether the command is a job correction command. As described above, the job correction command includes processes such as decrementing the counter and correcting the recipient. If it is determined that the command is not a correction command, the process proceeds to step S2011 to perform the corresponding processing. If it is determined that the command is a correction command, a correction command is issued to the job to be corrected in step S2012. Whether or not the original user has the right is determined in the same manner as in step S2008. In step S2014, the job management table 202a is checked to determine whether there is a job whose counter is "0". If there is, the job is deleted in step S2015.

  As a result, according to the third embodiment, in addition to the first embodiment, an expiration date for the job can be set on the job issuer side, so that the job accumulates in the printer indefinitely. This will effectively prevent confidentiality.

  The recipient can also give the third party the right to issue a job execution command.

  The printer 102 described in the first to third embodiments has been described as including a processing program for realizing the above processing. For example, the printer 105 in FIG. 2 is a general printer. Yes, the PC 104 to which it is connected may function as a print server, and the program of the print server may perform the same processing as the printer 102.

  In the first to third embodiments, a printer is used as an output target device. However, it is needless to say that a printer unit included in a FAX connected on a network, a printer unit included in a copier, or the like may be used.

  Moreover, although the said embodiment requires hardware, such as a network and the card or board for connecting to a network, it can be implement | achieved by the software embedded in general-purpose information processing apparatuses, such as a personal computer.

  Therefore, the present invention supplies a storage medium (or recording medium) that records software program codes for realizing the functions of the above-described embodiments to a system or apparatus, and the computer of the system or apparatus (or CPU or MPU). Needless to say, this can also be achieved by reading and executing the program code stored in the storage medium. 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. Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an operating system (OS) running on the computer based on the instruction of the program code. It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the actual processing and the processing is included.

  Furthermore, after 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, the function is determined based on the instruction of the program code. It goes without saying that the CPU or the like provided in the expansion card or the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  As described above, according to the present embodiment, when job data is issued, job attributes (particularly, identification information and password of “job recipient”) necessary for job execution permission are added to the job data. The job data is issued and transmitted to a device such as a printer, and the job attributes necessary for permission to execute the job are transferred as “job issue notification” from “job issuer” to “job recipient”. When the “recipient” instructs to execute the job, the “job recipient” is sent by sending the job execution instruction command data to which the job attribute necessary for permitting execution of the job is added and instructing the execution. It is possible to obtain job execution results (printed output results, etc.) at any timing, and the target output results can be efficiently transferred only to the “job recipient”. There is an effect that can provide such a system.

  In addition, when issuing job data, “Job attributes necessary for permitting job execution (especially identification information and password of“ job recipient ”)” and “Job attributes for managing job lifetime (job expiration date) Etc.) is added to the job data, the job data is emitted and transmitted to a device such as a printer, and the “job attribute necessary for permitting job execution” and “job attribute for managing job lifetime” are set. , “Job issue notification” is transferred from “Job issuer” to “Job recipient”, and when “Job recipient” instructs job execution, the “Job attribute necessary for job execution permission” is added. By sending the job execution instruction command data to the device and instructing the job execution, only the “job recipient” can execute the job at any timing. It is possible to obtain line results (print output results, etc.) and reflect the will of the job issuer in the lifetime of the issued job. This has the effect of providing a system with a clear job life.

  In addition, since the “Job Recipient” can further forward the “Job Issue Notification” to a third party, the portability of the issued job can be improved. This has the effect of improving the transmission efficiency.

Claims (6)

An input means for inputting output data;
Receiving means for receiving recipient identification information indicating a plurality of recipients that receive the output data input by the input means;
Storage means for storing the output data input by the input means and the recipient identification information received by the receiving means in association with each other;
The output data stored in the storage means is invalidated in response to the output data stored in the storage means being output by a plurality of recipients indicated by the recipient identification information stored in association with the output data. An output device comprising: invalidating means for converting to an output device. Counting means for counting the number of outputs of the output data;
The output device according to claim 1, further comprising: a second invalidating unit that invalidates the output data when the number of outputs counted by the counting unit exceeds a predetermined number. Management means for managing the expiration date of the output data;
The output device according to claim 1, further comprising a third invalidating unit that invalidates the output data when the output data has passed an expiration date managed by the managing unit. The output device according to claim 1, wherein the output data is print data, and the output device is a printing device. An input process for inputting output data;
A receiving step of receiving recipient identification information indicating a plurality of recipients that receive the output data input in the input step;
A storage step of storing the output data input in the input step and the recipient identification information received in the reception step in association with each other in a storage unit;
The output data stored in the storage unit is invalidated according to the output data stored in the storage unit being output by a plurality of recipients indicated by the recipient identification information stored in association with the output data. And a disabling step for converting the output device. A computer-readable storage medium storing a computer program for causing a processor in the output device to execute each step of the output device control method according to claim 5.

Images