JP2003308184A - Job management system, job management apparatus, data processing apparatus, job management method, data processing method, and control program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To accurately grasp a condition of job processing by a printer by managing job information on a host side and job information of the printer together even when the printer is not corresponding to a job management system used by the present printer, a job ID is not managed by the printer or the printer can not acquire the job ID. <P>SOLUTION: A new document data name is prepared, and job information is acquired from a computer and the printer, and they are merged to grasp accurate job information. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a printer, a scanner, a facsimile, a copying machine, and the like connected to a network, peripheral devices such as a multifunction device (MFP) that integrates them, and a computer for managing these devices. , About network systems.

[0002]

2. Description of the Related Art Conventionally, a job management system for an image processing system that acquires and manages a large number of job information has been developed. In order to perform appropriate job management (job account), it is necessary to acquire information on jobs executed by peripheral devices. Conventionally, the following methods have been used to obtain job information. For example, the spooler on the client computer side accumulates the data received from the driver and sequentially transmits the data to the transmission unit on the client computer side. The client computer side transmission unit receives the print data from the spooler, and transmits the job data to the device according to the job transfer method of the device if the printer is ready. Well-known job data transfer methods include the LPD protocol defined by RFC1179 and the Hewlett-Packard Co.
Printer Job L specified by company
There is an angage etc. Printer Job
In the Language, the port monitor can acquire the number of pages of the finished job by bidirectional communication with the device. Of course, a private job management method unique to the printer provider may be used.

On the other hand, there has been devised a system that uses the above-described job management system to transmit job information from the peripheral device to the client computer side and manage the job name and job ID.

[0004]

However, since the job management methods are different depending on the model of the printing apparatus or the manufacturer of the printing apparatus, when the job management is performed based on a certain job management method. In some cases, the job IDs of different job management methods cannot be grasped. Further, the printing device may not support the job ID in the first place.

As a means for solving such a problem, it is conceivable to send a job including a document name to a printing apparatus and use it instead of the job ID. However, the document name is shorter than the document name managed on the client computer side due to the memory limitation on the printing device side, and there is a problem that the document name managed on the client computer side cannot be used as it is. .

Further, due to the characteristics of a printer that can manage only such short document names, when a job based on the same document name is submitted to a printing apparatus from a plurality of client computers, the job having the same job ID or document name is regarded as the same job. However, in this case, there is a problem that the job cannot be identified and is confused.

The present invention has been made in view of at least one of these problems. One of the objects of the present invention is to provide a printing apparatus that does not support the job management method used by itself, that the printing apparatus does not manage the job ID, or that cannot acquire the job ID. It is an object of the present invention to manage the job information of the host side and the job information of the printing device together so as to accurately grasp the status of the job processing performed by the printing device.

Further, according to the present invention, since the job is transmitted by including the document name in the job to the printer, the document name managed by the client computer is managed by the printer. It is still another object to provide a mechanism for managing as possible identification information.

Further, according to the present invention, in order to acquire the usage status of the peripheral device more accurately, the job information is acquired from each of the client computer and the image forming apparatus by utilizing the existing entry of the document name of the job information. Yet another object is to provide a mechanism for realizing accurate grasp of job information.

[0010]

In order to achieve at least one of the above-mentioned objects, the present invention provides the following means for solving. According to a first aspect of the present invention, there is provided a data processing device that processes job data of a job based on document data, an image forming device that receives and outputs job data processed by the data processing device, and job information of the job. In a printing system in which a job management device to be managed is connected to a network, the data processing device manages the document name of a document as job information of one job in association with a new document name uniquely determined in the printing system. A first management means,
A transmission control unit that controls a process of transmitting the new document name as job information of the one job to the image forming apparatus via a network, and the image forming apparatus is transmitted from the data processing apparatus. , Has a second management means for managing the new document name as the job information of the one job, and the job management device,
The job information managed by the first management unit of the data processing apparatus is acquired from the data processing apparatus via the network, and the job information managed by the second management unit is stored in the network. The first document based on the second acquisition unit acquired from the image forming apparatus via the image forming apparatus, the new document name acquired by the first acquisition unit, and the new document name acquired by the second acquisition unit. The job management system is characterized in that it has a second management unit that manages the job information acquired by the acquisition unit and the job information acquired by the second acquisition unit together. .

According to a second aspect of the present invention, in a job management apparatus capable of communicating with an image forming apparatus and a data processing apparatus and managing job information of one job based on a document, the job management apparatus is based on the document name of the document. A first acquisition unit that acquires a new document name generated in the data processing apparatus as job information of the one job, and a second acquisition unit that acquires a new document name as job information of the one job from the image processing apparatus Job information acquired by the first acquisition unit based on the acquisition unit, the new document name acquired by the first acquisition unit, and the new document name acquired by the second acquisition unit, It is characterized by having a management means for managing together with the job information acquired by the second acquisition means.

According to a third aspect of the present invention, the management means includes a new document name in both the job information acquired by the first acquisition means and the job information acquired by the second acquisition means. Determination means for determining whether or not,
When the determining unit determines that both the job information acquired by the first acquiring unit and the job information acquired by the second acquiring unit include the same new document name, the managing unit determines , The job information acquired by the first acquisition unit using the new document name,
It is characterized by managing a process of merging the job information acquired by the second acquisition unit.

The invention according to claim 4 is characterized in that the management means reads the document name from the job information managed by the management means based on the new document name acquired by the second acquisition means. The job management apparatus according to claim 2 or 3.

According to a fifth aspect of the present invention, in a data processing device capable of communicating with an image forming device and processing job data of one document-based job, the document name of the document is uniquely assigned to the printing system. Management means for managing as job information of the one job corresponding to a new document name that is determined, and processing for transmitting the new document name as job information of the one job to the image forming apparatus via a network And a transmission control means.

The invention according to claim 6 has issuing means for issuing job identification information for identifying a job in the data processing apparatus, and the new document name is the job identification issued by the issuing means. It is generated by a set of information and identification information for identifying the data processing device.

According to a seventh aspect of the present invention, transmission control means for controlling a process of transmitting a new document name as job information of the one job to the image processing apparatus,
An acquisition unit that acquires a response of the job information including the new document name from the image forming apparatus, and the management unit is a job of the one job based on the new document name acquired by the acquisition unit. It is characterized by having a management means for managing information.

The invention described in claims 8 to 15 is
Since it is the invention of the method and control program of the invention described in claims 1 to 7, the description thereof will be omitted.

[0018]

BEST MODE FOR CARRYING OUT THE INVENTION (First Embodiment) An example of an embodiment of the present invention will be described in detail below with reference to the drawings.

FIG. 18 is a diagram showing an example of a system which is a premise of the embodiment of the job account system of the present invention. Printers 1807 to 1809, which are suitable examples of the image forming apparatus of the present invention, which are constituent members of FIG. 18, will be described. The operation of the printer differs depending on the function it has. For example, the printer 1807 is the most general type and prints the data received from the transmission unit on the client computer side. At the end of the job, the printer 1808 returns the total number of discharged pages of the job to the transmission unit on the client computer 1000 side. The printer 1809 stores the job information in the storage device in the printer after printing.

In the client computer shown in FIG. 18,
Printing is performed as follows. Application 1802
Operates GDI1803 (subsystem for processing graphic drawing) of the OS by calling an API (application programming interface). The printer driver 1804 converts the request from the GDI 1803 into a format suitable for the printer that prints,
Send to the spooler 1805.

In the client computer 1000, the job account client 1801 hooks (monitors and recognizes) the GDI call of the application 1802. Job account client 1801
Acquires the number of discharged sheets or the number of pages of the job issued by the application by counting the API for page break or sheet discharge. The job information acquired by this is called a hook log.

Further, the job account client 18
01 defines a protocol with a printer driver in advance and communicates with the printer driver so that the job information can be received from the printer driver in the client computer. The job information thus obtained is called a driver log.

Further, the job account client 18
01 regularly monitors the spooler, and if there is a spooled job, the information of the job is acquired by the API to acquire the number of discharged sheets or the number of pages of the job. The job information acquired by this is called an API log.

Further, the job account client 18
01 defines the protocol with the transmitter and communicates,
Gets the total number of output pages returned by the printer. The job information acquired in this way is called a transmission unit log.

In the case of a printer that stores job information in the printer, such as the printer 1809, which is a preferred example of the image forming apparatus, the job account server, which is a preferred example of the job management apparatus of the present invention, is a protocol with the printer. Job information is obtained from the printer by defining and communicating. The job information acquired in this way is called a device log. The device log is stored in the RAM or HDD in the printer, but due to the limited storage capacity, it is often not possible to store all the information such as the document name transmitted from the transmission unit. In addition to the printer, the image forming apparatus includes a facsimile, a copying machine, a copying system in which a printer, which is a type of copying machine, and a scanner are combined, and a composite machine of these.

Job account client 1801
Sets a priority order for selecting which of a hook log, a driver log, an API log, a transmission unit log, and a device log, and transmits one of them to the job account server.

The job account server 1810 selects a job log in response to a request from a person who wants to browse, and performs aggregation processing for each unit period, each device, each job issuer, and the like.

FIG. 1 is a diagram showing a device and a module configuration of a job account system showing an example of an embodiment of the present invention. The present invention is achieved in a system including a plurality of devices. Further, it goes without saying that the present invention is also applied to the case where the present invention is achieved by supplying a program to a system or an apparatus. Hook log, driver log, API for one print job
The manner in which four logs, the log and the transmission unit log, are created will be described in detail. The parts different from FIG. 18 will be described in detail below.

Reference numeral 101 denotes a client computer consisting of a standard PC or workstation, and when a printing instruction is given from the application 102, 107,
The print data is transmitted to the printer 108 or 109 via the transmission unit 107. The job account client 118, which is a software module executed by the CPU in the client computer, collects logs relating to various printing processes and sends the logs to the job account server 121 via the job log sending unit 117. At this time, the job log transmission unit, which is a part of the job account client, may control the transmission unit provided by the OS to transmit the log to the job log reception unit.

When a print instruction is issued to the application 102 in the client computer 101, the application 102 makes a GDI call for drawing in the same manner as described with reference to FIG. 103
The hook unit is incorporated by the 117 job account client, and hooks a GDI call, and stores information such as which GDI call was called by what parameter, the number of times it was called, and the like. A history created based on this information is called a hook log 111. An example of the hook log 111 is shown in FIG. The hook unit 103 changes the document name in some cases based on a predetermined judgment standard. The document name and this changing process will be described later.

The printer driver 105 converts the GDI call into print data that can be interpreted by the printer according to the print settings, sends the print data to the spooler 106, extracts the print information from the conversion content, and uses it as the driver log 112 as a job account client 117. Send to.

The job account client 117 constantly monitors the spooler 106 for jobs. If there is a job, AP specified by the OS
I is issued, print information is acquired, and it is recorded in API log 11
Get as 3.

The transmitting unit 107 is connected to the network 10 via the network.
Of the 8, 109, and 110, the printer communicates with the printer specified by any of the applications, and if the printer is in the ready state, print data is transmitted. At this time, for example, the aforementioned Printer Job Lang of HP Co.
By using the command of "age (printer job language)", the printer 109 can obtain the number of pages discharged by the job after the discharge of all the pages of the print job is completed. The transmission unit (port monitor) 106 transmits job information such as the number of pages received from the 109 printer to the 110 job account client. A print log created based on this information is referred to as a transmission unit log 114.

As described above, the job account client 110 (acquisition unit) acquires and creates four logs of the hook log, the driver log, the API log, and the transmission unit log for one print job. However, four logs are not always available. For example, if the application 102 sends print data directly to the spooler 106, the hook log 111 and the driver log 112 cannot be acquired. If the protocol is not defined between the printer driver 105 and the job account client 117, the 112 driver log cannot be acquired. Printer 10
If there is no function to notify the number of discharged pages to the transmission unit as in the case of 8, the discharged page information of the transmission unit log 114 cannot be acquired. However, by acquiring the logs in a plurality of processes related to the job, even if the logs cannot be acquired in some processes, the probability that the logs can be acquired is generally high.

The printer 108 interprets the job sent from the sending unit 107 and executes printing. Printer 109
Interprets the job sent from the transmission unit 107 and executes printing. After printing is completed, the number of ejected sheets is returned to the 107 transmission unit. The printer 110 interprets the job sent from the sending unit 107 and executes printing. After printing is completed, the job information is stored in 304 HDD (described later).

The job log merging unit 116 merges the hook log, the driver log, the API log, and the transmission unit log and sends them to the job log transmission unit 117. The merge process will be described later. The job log transmission unit 117 transmits the job log to the job log reception unit 122 of the job account server 121.

FIG. 2 is a block diagram showing an example of the configuration of the client computer and the server computer which constitute the job account system shown in FIG.
In FIG. 2, reference numeral 201 denotes a CPU, that is, a central processing unit, which performs control and arithmetic processing of the entire computer apparatus. Reference numeral 202 denotes a ROM, that is, a read-only memory, which is a storage area for information such as a system boot program. Reference numeral 203 denotes a RAM, that is, a random access memory, which is a data storage area without use restrictions. Software modules such as an operating system, an application 102, a hook unit 103, a GDI 104, a printer driver 105, a transmission unit 107, a job account client 118, Also, this is an area in which programs such as communication control are loaded from the HD unit 205 or the ROM 202 and executed by the CPU 201. 204
Is a KBC, that is, a keyboard control unit, which receives input data from the keyboard and transmits it to the CPU. 205 is CR
T, that is, a display control unit (display control means), controls display on the display device. Reference numeral 206 denotes an external storage device such as an FD, that is, a floppy (R) disk device or an HD, that is, a hard disk device, and an SRAM, that is, a non-volatile storage device. To load. Reference numeral 207 denotes a communication unit for performing network communication control, capable of communicating with other computers and peripheral devices connected to the network as described in FIG. 1, a transmission unit 107, a job log transmission unit. 117
Controlled by. Reference numeral 208 denotes a system bus, which should serve as a data path between the above-mentioned components.

In principle, the job account server 12
1 can also have a similar configuration in terms of hardware. In the job account server 121, a job log merging unit 123, a job log recording unit 124, a job log receiving unit 122, and a job log totaling unit 125 are stored in the HDD. The job log receiving unit 122 also controls the communication unit 207.

FIG. 3 is a block diagram showing an example of the configuration of a printer which constitutes the job account system shown in FIG. In FIG. 3, a controller unit 305 controls the entire printer. As an internal configuration of the controller, reference numeral 301 is a CPU, that is, a central processing unit, which controls the controller and performs arithmetic processing.
Reference numeral 302 denotes a ROM, that is, a read-only memory, which is a storage area for information such as system boot programs. Reference numeral 303 is a RAM, that is, a random access memory, which is a data storage area with no use restrictions, and 304 is a HD, that is, a nonvolatile storage device such as a hard disk or SRAM.

The RAM 303 is an area in which programs such as an operating system, communication control and engine control are loaded and executed. Reference numeral 306 denotes an engine unit of this apparatus, which performs a printing operation and an image reading operation under the control of the controller. Reference numeral 307 denotes a communication unit that controls network communication.
It is possible to communicate with the client computer and the server computer as described in. A user operation input / output unit 308 performs interactive setting work with the user. Reference numeral 309 denotes a system bus, which should serve as a data path between the above-mentioned components.

FIG. 4 is a diagram showing an example of a memory map of the job account server 121 shown in FIG. 41
Indicates a basic I / O program. Reference numeral 42 shows a memory map in a state where an operating system such as a window system is loaded into the RAM 203 and becomes executable. Four
3 shows a memory map in a state where the program of the present invention is loaded into the RAM 3 and becomes executable. Reference numeral 44 shows a memory map in a state where the relevant data is loaded into the RAM 3 and becomes executable. Reference numeral 45 shows a memory map of a work memory used by each program.

FIG. 5 is a diagram showing a configuration content of an FD in which a job account program and related data according to an embodiment of the present invention are stored. A job account program, which is an example of the embodiment of the present invention, and related data are recorded in a floppy (R) disk (FD). In the recording area 50 of the floppy (R) disk (FD), volume information 51 and directory information 5
2, an application execution file 53 and a job account program related data file 54 are recorded. The recording area 50 may be a DVD, or an HDD (not shown) in an external server connected to the computer 62 via a network, and a job account program of the present invention (in the client computer shown in FIG. 1). Each module, job Akan and server 1
It goes without saying that each module in 21) may be installed by being downloaded via a network.
The computer 62 is the same as the computer shown in FIG.

FIG. 6 shows an example of the embodiment of the present invention.
It is a figure which shows an example which loads the job account program and related data recorded on FD into a computer system. The job account program and related data recorded on the floppy (R) disk (FD) 60 can be loaded into the computer 62 via the FD drive (DKC) 61. When the floppy (R) disk (FD) 60 is set in the FD drive (DKC) 61, under the control of the operating system 42 and the basic I / O program 41, a program module for realizing this job account program, and the like. Related data is floppy (R) disk (F
D) It is read from 60, loaded into the RAM 203, and becomes usable. The computer 62 is the computer shown in FIG. 18, and the client computer 101 and the job account server 121 shown in FIG.
Can be used to realize A program module or the like for realizing the job account program corresponds to each software module in the client computer 101 or the job account server 121 described in FIG. Of course, the storage medium is not limited to the FD, but may be a DVD or a CD-R.
It goes without saying that OM and the like are included.

FIG. 7 is a diagram showing an example of a hook log in the embodiment of the present invention. In the hook log, job I
D, the application name, the number of logical pages, and the document name can be acquired. The job ID can be acquired from the GDI when the GDI is instructed to start printing, and can uniquely specify the print job of the client computer 101.

FIG. 8 is a diagram showing an example of the driver log in this embodiment. The driver log is history information that the job account client can obtain from the driver when executing printing. In the driver log, a job ID that is an identifier of a job related to printing, a paper size of print data included in the job, N-up information, information on the number of physical pages,
Both-sided and one-sided information can be acquired. Paper size, N-u
p, the number of physical pages, and double-sided / single-sided information are acquired from the print settings that are set at the time of printing or default input to the printer driver. N-up is a setting for the number of logical pages to be assigned to a sheet. The number of physical pages is a unit in which one side of the paper output at the time of printing is counted as 1.

For example, when there are four logical pages,
When 2-up printing processing is performed in double-sided printing, the number of physical pages becomes two. Then, the physical page is printed on the front and back sides of the sheet, and one sheet is output and ejected. The first and second logical pages are printed on the front side, and the third and fourth logical pages are printed on the back side.

FIG. 9 is a diagram showing an example of the API log in this embodiment. In the API log, the job ID, job owner name, and spool data size can be acquired.

FIG. 10 is a diagram showing an example of the transmission unit log in the embodiment of the present invention. The job ID can be acquired from the monitor log. 108, the number of discharged pages and the number of discharged sheets can be acquired.

Hook log, driver log, API log,
An area for recording flag information indicating whether or not the job has been processed and information indicating the type of log is provided in each of the transmission unit logs.

FIG. 11 is a flow chart showing an example of a procedure for merging logs in the embodiment of the present invention.
The operation of the job log merging unit 116 in the client computer will be described below with reference to the flowchart of FIG. The job log merging unit 116 receives each log described with reference to FIGS. 1 and 18, and records the contents in the HDD or the like. Then, the following process is periodically started at a preset cycle, and the merge process is performed for each job. In the present embodiment, the logs are merged (merged) by using the job ID as a key, but they may be merged by using a document data name or a new document data name described later as a key. In the processing of FIG. 11 below, the job log merging unit 1 is set in the client computer.
Reference numeral 16 denotes the earliest start time among the start times indicated by the entries of the start time information and the completion time information, which are included in the job information (hook log, API log, API log) obtained by each of the plurality of processes in the client device. Then, the latest completion time can be specified. And
As described above, each piece of time information is stored as job information merged and merged.

In step S1101, the job log merging unit 116 searches and specifies whether or not there is a transmission unit log (see FIG. 10) whose processed flag is not YES, that is, an unprocessed transmission unit log. If there is an unprocessed transmission unit log, the process proceeds to S1102. In step S1102, the job log merging unit 116 copies the transmission unit log identified as unprocessed in step S1101 to another temporary storage area, and sets this as log A. In S1103,
The part of the job ID is acquired from the log A. In step S1104, the job log merge unit 116 determines whether or not there is a log that has not been merged yet, that is, an unprocessed log among the logs corresponding to the job ID acquired in step S1103, based on the job ID. The determination is made by searching and specifying each log of the hook log, the driver log, and the API log. If it is determined in S1104 that there is no unprocessed log, the process ends. If the job log merging unit 116 determines in S1104 that there is an unprocessed log, the job log merging unit 116 proceeds to S1105 and then S11.
Based on the job ID, whether there is a log with a job ID equal to the job ID determined to be unprocessed in 04 (here, it is N for convenience), the driver log,
A log B is searched and specified from each log of the API log, and is referred to as a log B. If the log of the job ID equal to N is not found in each of the hook log, the driver log, and the API log in S1105, the process proceeds to S1108. In S1105,
If the job ID equal to N exists in any of the logs, the process advances to step S1106. Here, for example, S1105
In N, the job IDs included in the unprocessed log A may be specified as N in order from the smallest job ID.

In S1106, the job log merging unit 116 specifies the job ID of the log A specified in S1105.
For each item of the log corresponding to N (job information included in each log acquired for job ID N), log B
It is determined whether or not there is an item not included in the log A among the items included in. When it is determined in S1106 that there is no item in the log B that does not exist in the log A for the item of the job ID N in the log A, the job log merging unit 116 performs the process in S1108. If it is determined in S1106 that there is an item that does not exist in log A in log B, the process advances to step S1107, and job log merging unit 116 determines that the item of job ID N in log A does not exist in log A in log B. Is added to merge the data stored in the log A. Here, the processed flag of the log created by adding the item of log B to log A (hereinafter, merge log) is set to "YES", and S1108 is set.
Proceed to. Then, the item of the type of the merge log is set to "merge". 7 to 1 for the transmitter log
When the logs shown in 0 are merged one after another based on the process of FIG. 11, a merge log as shown in FIG. 12 is obtained. As shown in the figure, this merge log consists of hook log, driver log, A
It has items of PI log and transmission unit log. Figure 12
It is a figure which shows an example of the merge log of embodiment of this invention.

In step S1104 subsequent to step S1108, log A
When it is determined that the processing has been completed for all the job IDs related to (3), the processing ends. Normally, every time the merge process is completed, the job log merge unit 116 sends the merged log to the log transmission unit 116 after the process of FIG. Note that the log transmission unit 116 periodically outputs a log or in response to a request from the job log acquisition unit, the job log acquisition unit 1
22 to 22.

Next, the operation of the job account server 121 will be described. The job log acquisition unit 122 acquires and stores the job sent from the job log transmission unit 117. In addition, the printer 110 is regularly polled,
If there is job information that has not been obtained yet, obtain it. This job information is used as a device log. The device log is 30
Although it is stored in 3RAM or 304HDD, it is not desirable to store all the information such as the document name transmitted from the 107 transmission unit due to the limitation of the storage capacity. Here, it is assumed that the upper limit of the document name is 8 characters. FIG. 13 shows an example of the device log. FIG. 14 shows an example of a device log when the 103 hook unit is not operating.

The job log merging unit 123, which is a preferred example of the managing means of the present invention, merges the merge log 127 sent from the job account client with the job log receiving unit 1.
The device log 115 is received and acquired at 22 to acquire the device log 115.
Then, the job log merging unit 123 merges and manages the acquired logs. The procedure for merging will be described later. The job log recording unit 124 receives the job log from the device job log merging unit 123 and stores it in the 206HD or the like. The job log totaling unit 125 calculates the number of print pages for each unit period according to an instruction from the viewer,
Performs aggregation processing such as obtaining the number of printed pages for each owner.

The ID generating unit 126 issues an ID, which is identification information for uniquely identifying the client computer 101, which is a preferred example of the data processing device. Here, a 4-digit character string in which each digit can take 26 different values from a to z is aaaa, aaa in response to a request from the 103 hook unit.
It is issued so that the client can be uniquely identified by changing it in the order b, ..., zzzy, zzzz. Here, the new document name is created by using the combination of the host and the job ID, but a new document name (to be described later) unique to the entire printing system may be centrally issued in the job account server.

FIG. 15 is a flow chart showing an example of the procedure for changing the document name according to the embodiment of the present invention. The operation of the hook portion 103 will be described below with reference to the flowchart of FIG. In step S1501, the hook unit 103 acquires and determines information indicating whether or not the printer at the printing destination has the device log by the predetermined device management protocol, and when it determines that the printer has the device log, the hook unit 103 proceeds to step S15.
Go to 02. When the hook log unit 103 determines that the printer does not have the device log, the process ends.
In step S1502, the hook unit 103 determines whether the client ID has been acquired.
Proceeds to S1504. If not acquired, the process proceeds to S1503. Here, the client ID is identification information issued by the ID generating unit that can uniquely identify the client computer 101. Here, in S1503,
It is assumed that the hook unit 103 communicates with the ID generation unit 126 and acquires an ID that uniquely identifies the client computer from the ID generation unit. In step S1504, an in-client job ID that uniquely identifies a job in the client computer is created. Here, 0001 to 99
The numbers up to 99 shall be issued in order. Where "abc
"d0001" is a preferred example of the new document name of the present invention.

In S1505, the hook portion 103
Client ID and S determined to have been acquired in S1503
The job IDs in the client created in 1504 are combined to create a new document name, which is an example of new identification information uniquely determined in the printing system. In step S1506, the hook unit 103 stores the original document name passed from the application in the item “original document name” of the hook log. In step S1507, the document name is replaced with the new document name in step S1505.
As a result, the new document name is passed to GDI as the document name. It is preferable that all the document names in the printer driver 105, the spooler 106, the transmission unit 107, and the printer 110, which are the latter stage of the GDI process, be processed with the new document name.

Here, the reason for creating the new document name is that it is difficult to use the job ID as it is as the key of the merge process when merging the job information acquired from the printing apparatus. For example, since part of the specifications of the job management method is not disclosed, when using the account server A developed by A company, the account server developed by A company outputs the job ID from the printer developed by B company. Often unable to get. In other words, even if job information is acquired from a printer that supports an unintended job management method, it is often the case that this does not include the job ID, and this cannot be merged and used.
However, the document name created by the OS or application in the client computer and sent to the printer can often be acquired as job information.

Therefore, instead of the job ID, management can be performed on the client side, and the job I can also be managed from the printer side.
Instead of D, it is possible to manage a document name that can be acquired as a key of job information as identification information. However, using the conventional document name as it is causes a problem. Generally, the OS or application on the client side can manage more than 8 characters, and a generally used OS can give a document name of up to 255 characters. The printer can manage up to 8 characters, as described above. Also, in general,
8 document names can be used in the job management system
Up to letters. With this, 8
When a document name with more than characters is given, even if the document name given by the OS or application on the client side is different, jobs with the same document name may coexist in the printer. There is confusion. Therefore, the host ID on the account server side
Is issued and used in combination with the document name issued on the client side. As a result, a new document name that is uniquely determined in the printing system including the client computer and the printer, which is managed by the account server within 8 characters, is completed. Then, this new document name can be used in place of the job ID to identify the job. Once the new document name is generated on the client side, the printer,
This document name can be used as a job identifier in the client and account server. The job including the new document name is sent together with the print data from the client computer to the printer and processed by the printer. Then, the printer starts the printing process corresponding to the job, acquires the new document name included in the job information, and responds to the print completion and the paper discharge completion as the job information corresponding to the job. Generate and update device logs. Then, this device log including the same new document name as that transmitted from the client computer is transmitted to the job account server and the processing described later is performed.

FIG. 16 is a flowchart showing an example of a procedure for merging logs to create a final log according to the embodiment of the present invention. Using the flowchart of FIG.
Job log merge section 123 (device job log merge section)
The operation of will be described.

In S1601, the job log merging unit 123 searches for an unprocessed merge log, and if there is, it proceeds to S1602. If not, the process ends. S160
In step 2, the job log merging unit 123 determines whether the printer has a device log, and if so, S160.
Go to 3. If not provided, the process proceeds to S1607. S16
In 03, the job log merging unit 123 searches and determines whether or not there is an unprocessed device log in which the item of the document name is the same as the merge log in S1601. If it is determined, the process proceeds to S1604. If it is determined that the same log as the merge log in S1601 does not exist, the process ends.
In step S1604, the job log merging unit 123 replaces or adds the number of discharged pages in the device log to the merge log.

FIG. 13 is a diagram showing an example of a device log in the embodiment of the present invention. In step S1605, the job log merge unit 123 replaces the document name with the original document name. When applied to the device logs shown in FIGS. 12 and 13, “Document name: 2001 annual report source document name: abcd0001” is obtained.

In step S1606, the job log merging unit 123 deletes the original document name of the merge log.
This is the final log. When applied to the device logs of FIGS. 12 and 13, the result is as shown in FIG. In S1607,
The job log merging unit 123 sends the final log to the 124 job log recording unit. The device log shown in FIGS. 13 and 14 includes the actual number of ejected pages, the actual number of ejected sheets, the model name, the processing start time in the printer, the output processing time such as completion of ejection, and the like.

As described above, according to the present invention, it becomes possible to acquire more accurate document information and job information that stores paper ejection information, and it is possible to perform a stricter job account. . In other words, in the printing system managed by the account server, a mechanism for performing the merge process using the unique identification information is provided, so that the same job is used for different jobs when managing the job information and counting the number of printed sheets and the number of discharged sheets. Accurate job accounts are possible without accidentally merging and managing as jobs.

(Second Embodiment) Hereinafter, a description will be given focusing on a portion different from the first embodiment. FIG. 19 is a diagram illustrating an example of merge processing in the job log merge unit 116 according to the embodiment of this invention. The operation of the job log merging unit 116 will be described below with reference to the flowchart of FIG. The job log merging unit 116 receives and acquires each log, and records the contents in the HDD or the like in the client computer. Then, the following processing is started regularly. In step S1901, the job log merge unit 116
Searches for an unprocessed transmitter log, and if it determines that there is an unprocessed transmitter log, the process advances to step S1902. If it is determined in S1901 that there is no unprocessed transmitter log, the process ends. S1
At 902, the job log merging unit 116 copies the contents of the transmission unit log. This is log A. Here, the processed flag of the transmission unit log is set to YES. S1903
In, the job log merging unit 116 extracts and acquires the job ID from the log A. Then, in step S1904, the job log merge unit 116 determines whether or not there is a job ID related to the log A acquired in step S1903 that has not undergone merge processing and time determination processing.

If it is determined in S1904 that there are no unprocessed items, the process ends. If the job log merge unit 116 determines in S1904 that there is job information related to the unprocessed job ID, the process advances to S1905. In S1905 and subsequent steps, among the job IDs determined to be unprocessed in S1903, the job ID with the smallest number is set as N here, and the process proceeds. Then, the job log merging unit 116 identifies the log having the job ID equal to N by searching the hook log, the driver log, the API log, and the transmitting unit log, and sets the identified log as the log B. If the job log merge unit 116 determines in step S1905 that there is no log having a job ID equal to N,
In step S1912, the job ID N is marked as processed, and the process proceeds to the processing for determining other unprocessed job IDs (step S190).
4). If the job log merging unit 116 determines in S1905 that there is a log having a job ID equal to N,
After S1906, the merge process is performed.

Hereinafter, in S1906 and subsequent steps, processing is performed for the entry of the job ID N in the job information. S
At 1906, it is determined whether the start time of the log B is before the start time of the log A. If it is before the start time, S1
907, if not before the start time, S1908.
Process. In step S1907, the job log merging unit 116 rewrites the start time of the log A with the start time of the log B, and proceeds to step S1908.

In step S1908, the job log merging unit 116 determines whether the end time of the log B is later than the end time of the log A.
Proceed to 9. If it is determined that it is not later, the process proceeds to S1910. In step S1909, the job log merge unit 116
Rewrites the end time of log A to the end time of log B,
Proceeds to S1910. In step S1910, the job log merge unit 116 determines whether or not there is an item in the log B that is not in the log A. If it is determined that there is an item, the process advances to step S1911.
If it is determined that there is not, the process proceeds to S1912. S1911
In, the job log merging unit 116 adds an item in the log B that is not in the log A. Here, the processed flag of the log B is set to YES. Here, the type is merge.
When the processing of FIG. 19 is applied to the logs of FIGS. 7 to 10, the logs are as shown in FIG. This is the hook log, as shown in the figure
It has items of a driver log, an API log, and a transmitter log, and the start time of the hook log and the end time of the transmitter log. This makes it possible to grasp the throughput from the generation of one job to the completion of processing from the input of a print command to the application to the completion of paper ejection. After the processing in FIG. 19, the job log merging unit 116 sends the merged log to the 116 log transmitting unit. The job log transmission unit 117 controls the transmission control unit, which is a function of the OS, to log (merge job information).
To the job log acquisition unit 122 is controlled.

When this processing is performed, it is not necessary to arrange the order of merging logs that can be acquired in each processing of image processing / output processing in time series of the data processing order. As described above, also in this case, the new document name can be used for the merge process instead of the job ID.

As described above, in a client device that processes a job in which a plurality of data processes for one job have been performed, a plurality of job information obtained in a plurality of data processes for one job are acquired and the account client The job log merging unit 116, which is a preferred example of the specifying unit of the present invention included in each of the plurality of job information acquired by the above, can specify the earliest start time among the start times indicated by the start time information. Also,
Similar to the above process, if the job log merging unit 116 is controlled so that the latest time is overwritten with respect to the completion time, the latest completion time is left in the merge log and the latest completion time is left. You can specify the time.

As another example of this embodiment, a hook log, a driver log, an API log, and a transmission unit log, which correspond to one job ID in the item of time of each log, are arranged.
Then, the merge process is performed in this order. The item of time is
It is necessary to perform the overwrite merge processing in the order in which they are arranged.

FIG. 20 is a diagram showing an example of merge processing in the job log merge unit 123 according to the embodiment of the present invention. The operation of the job log merging unit 123 will be described below with reference to the flowchart of FIG. The merge log is transmitted to the account server device and the same processing as that of FIG. 15 is performed. That is, the new document name is stored in the merge log based on the information generated by the ID generation unit, and the old document name is backed up in the item of the old document name. Then, the job log merging unit 123
In, the final log is generated from the merge log. The following is a modification of the merge log process described above.

In S2001, the job log merging unit 123 searches and determines whether or not there is an unprocessed merge log acquired by the job log merging unit 123 from the client computer, and if it determines that there is, it proceeds to S2002. If it is determined that there is not, it ends. In step S2002, the job log merge unit determines whether the printer has the device log acquisition mechanism. If it determines that the printer has the device log acquisition mechanism, the process proceeds to step S2003. If it is determined that it is not equipped, the process proceeds to S2011. In step S2003, the job log merge unit 123 determines whether the job log merge unit 123 searches the device log acquired from the printer for an unprocessed device log that has the same document name as the merge log in step S2001. If it is determined that there is something, the process proceeds to S2004. When it is determined that there is no same thing, the process ends. In step S2004, the job log merge unit 123 adds the number of discharged pages of the device log to the merge log. In step S2005, the job log merge unit 123 replaces the document name with the original document name. When this process is applied to the device logs of FIGS. 12 and 13, “document name: 2001 annual report source document name: abcd0001” is obtained. That is, the job log merging unit 123 is a preferred example of the new document name of the present invention, abcd000.
Using the key 1 as a key, the document name "2001 annual report" created by the user in the originally stored OS or the like and used when designating the print target and the file name is read out and replaced.

FIG. 17 is a diagram showing an example of the final log in the embodiment of the present invention. In S2006, the original document name of the merge log is deleted. This is the final log. When applied to the logs of FIGS. 12 and 13, the result is as shown in FIG. In step S2007, it is determined whether the start time of the device log is before the start time of the merge log. If yes, the process proceeds to step S2008. Otherwise, it proceeds to S2009. In step S2008, the start time of the final log is set to the start time of the device log. In S2009, it is determined whether the end time of the device log is later than the end time of the merge log, and if it is determined that the end time is later, the process proceeds to S2010. If it is determined that there is no later, the process proceeds to S2011. S201
At 0, the end time of the final log is set to the end time of the device log, and the process ends.

FIG. 21 is a diagram showing an example of the final log in the embodiment of the present invention. In step S2011, the final log is transmitted to the 124 job log recording unit. The generated job log is as shown in FIG. By doing so, the job log merging unit 123 can accurately reflect and manage the output start time and the output end time in the host computer in the final log shown in FIG. 21, and perform accurate image processing. It is possible to measure the throughput from the start to the output completion. The job log merging unit 123, which is one of the applications 43, instructs the OS 42 to display the screen shown in FIG. 21 obtained by combining the logs on the display screen of the CRT 205 on the job account server 121. May be. That is, the job log merging unit 123 sets the job log to the merge log acquired from the client side and the device log acquired from the printer side.
Controls the process of displaying a list as a table on one display screen together with the document name and the document name. Since each was managed and displayed separately, the user displayed the desired screen by clicking the window system many times, but a list of the merged logs described above can be displayed. It is possible to provide a job management system that is simplified and has excellent visibility and operability.

Further, the job log merging unit 123 may acquire the logical page from the client side and the actually abolished number of discharged sheets or the number of discharged pages from the printer side. Here, the number of discharged sheets is how many sheets have been discharged, and the number of discharged pages is a number indicating how many physical pages have been discharged.

That is, the job log merging section 123 acquires a plurality of job information obtained in a plurality of data processings for one job, and the job log merging section 123
Of the start time information of each log included in the hook log, API log, API log, device log, and the start time indicated by the entry of the completion time information, which are obtained by a plurality of processes corresponding to one job acquired by , The earliest start time and the latest completion time can be specified. Then, each time information is merged and stored as merged job information as described above.

As described above, according to the present invention, the print start time and the print end time can be acquired more, and a more strict job account can be performed.

(Third Embodiment) The present invention is not effective only when the printer has a device log.
By making the document name unique, the hook log,
It is possible to merge the driver log and API log.

Further, depending on the OS, the job ID issued by the OS may not guarantee uniqueness. in this case,
The discriminating process of S2001 in FIG. 15 may be replaced with the discriminating process of “whether or not the job ID is unique?”, And if it is not unique, the document name changing process may be performed. Further, in S1101, S1901, etc., the job I
Although D uses the job ID of the transmission unit log in the above embodiment, it goes without saying that the merging process may be performed based on the job ID of another log (hook log, driver log, API log, etc.). There is also no.

As described above, according to the above-described embodiment, the job information acquired from the client computer and the job information acquired from the printer are merged and managed, so that, for example, on the computer side,
The number of physical pages and the number of logical pages can be acquired, and the number of actually discharged sheets and the number of discharged pages can be obtained on the printer side in response to the completion of actual printing. By merging and managing these pieces of information so that they can be compared, even if a printer error such as a paper jam error occurs and the number of ejected sheets does not match the number of physical pages on the computer side, one job Then, it is possible to grasp what kind of transition (the driver has properly processed, but a jam error has occurred on the printer side) has been followed. Further, in data processing, when various processing is performed for each job, for example, a job starts printing processing from PDL data and a job directly transmits data to the spooler. Even
Since the job information is acquired in a plurality of processes, a more accurate log can be acquired.

(Other Embodiments) The processing shown in the flowcharts of the respective drawings (FIG. 11, FIG. 16, FIG. 19, FIG. 20, etc.) and the respective modules shown in FIG. 1 and FIG. It is performed by each of the computers by the program installed from. And in that case, CD-ROM, flash memory, FD
The present invention is applicable even when the information group including the program is supplied to the client computer from a storage medium such as the above or from an external storage medium via a network.

As described above, by supplying the storage medium recording the program code of the software that realizes the functions of the above-described embodiment to the system or the apparatus or downloading it from the external server (not shown), It goes without saying that the object of the present invention can also be achieved by the computer (or CPU or MPU) of the system or device reading and executing the program code stored in the storage medium.

In this case, the program code itself such as the job account server or job account client program read from the storage medium realizes the novel function of the present invention, and the storage medium storing the program code is It constitutes the invention. Storage media for supplying the program code include, for example, floppy (R) disks, hard disks, optical disks, magneto-optical disks, DVDs, CD-ROMs, magnetic tapes, non-volatile memory cards, ROMs, EEPRs.
OM or the like can be used.

Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also the OS (operating system) running on the computer based on the instruction of the program code. It goes without saying that this also includes the case where the above) performs a part or all of the actual processing, and the processing realizes the functions of the above-described embodiments. Further, a program code transmitted from a predetermined external server device (not shown) via a network or read from a storage medium is a function expansion board inserted into the computer or a function expansion connected to the computer. After being written in the memory provided in the unit, the CPU or the like provided in the function expansion board or the function expansion unit performs a part or all of the actual processing based on the instruction of the program code, and by the processing, the above-described embodiment It goes without saying that the case where the function is realized is also included.

[0087]

As described above, according to the present invention, since the job information is acquired from both the peripheral device and the computer, the utilization status of the peripheral device can be acquired more accurately.
It is possible to acquire accurate job information by acquiring job information from each of the client computer and the image forming apparatus.

[Brief description of drawings]

FIG. 1 is a diagram showing a configuration of a job account system showing an example of an embodiment of the present invention.

2 is a block diagram showing an example of a configuration of a client computer and a server computer that constitute the job account system shown in FIG.

FIG. 3 is a block diagram showing an example of the configuration of a printer that constitutes the job account system shown in FIG.

FIG. 4 is a diagram showing an example of a memory map of the job account system shown in FIG.

FIG. 5 is a diagram showing a configuration content of an FD that stores a job account program and related data, which is an example of an embodiment of the present invention.

FIG. 6 is a diagram showing an example of an embodiment of the present invention, showing an example of loading a job account program and related data recorded in an FD into a computer system.

FIG. 7 is a diagram showing an example of a hook log according to the embodiment of the present invention.

FIG. 8 is a diagram showing an example of a driver log according to the embodiment of the present invention.

FIG. 9 is a diagram showing an example of an API log according to the embodiment of the present invention.

FIG. 10 is a diagram showing an example of a transmission unit log according to the embodiment of the present invention.

FIG. 11 is a flowchart illustrating an example of a procedure for merging logs according to the embodiment of this invention.

FIG. 12 is a diagram showing an example of a merge log according to the embodiment of this invention.

FIG. 13 is a diagram showing an example of a device log according to the embodiment of the present invention.

FIG. 14 is a diagram showing an example of a conventional device log.

FIG. 15 is a flowchart illustrating an example of a procedure for changing a document name according to the embodiment of this invention.

FIG. 16 is a diagram showing a process of merging logs according to the embodiment of the present invention;
It is a flow chart which shows an example of the procedure of creating the last log.

FIG. 17 is a diagram showing an example of a final log according to the embodiment of the present invention.

FIG. 18 is a diagram showing an example of a system which is a premise of the embodiment of the job account system of the present invention.

FIG. 19 is a diagram showing an example of merge processing in the job log merge unit 116 according to the embodiment of the present invention.

FIG. 20 is a diagram showing an example of merge processing in the job log merge unit 123 according to the embodiment of the present invention.

FIG. 21 is a diagram showing an example of a final log according to the embodiment of the present invention.

[Explanation of symbols]

60 Flexible Disk FD 61 Flexible Disk Drive Controller DK
C 62 Computer 111 Hook log 112 Driver log 113 API log 114 Sending part log 115 Device log 116 Job log merging part 117 Job log sending part 118 Job account client 122 Job log receiving part 123 Job log merging part 121 Job account server 126 ID generating part

Claims (15)

[Claims] 1. A data processing apparatus for processing job data of a job based on document data, an image forming apparatus for receiving and outputting job data processed by the data processing apparatus, and job management for managing job information of the job. In a printing system in which the device is connected to a network, the data processing device manages the document name of a document as job information of one job in association with a new document name uniquely determined in the printing system. And a transmission control unit that controls a process of transmitting the new document name as job information of the one job to the image forming apparatus via a network, wherein the image forming apparatus is controlled by the data processing apparatus. The name of the new document sent is used for the job name of the one job. Job management apparatus that acquires job information managed by the first management unit of the data processing apparatus from the data processing apparatus via a network. Of the job information managed by the second managing means,
Based on a second acquisition unit acquired from the image forming apparatus via a network, a new document name acquired by the first acquisition unit, and a new document name acquired by the second acquisition unit, A job management system comprising: third management means for managing together the job information acquired by the first acquisition means and the job information acquired by the second acquisition means. 2. A job management device capable of communicating with an image forming device and a data processing device, for managing job information of a single job based on a document, the job management device being generated based on the document name of the document in the data processing device. A first acquisition unit that acquires a new document name as job information of the one job; a second acquisition unit that acquires a new document name as job information of the one job from the image processing apparatus; The job information acquired by the first acquisition unit and the second acquisition unit based on the new document name acquired by the first acquisition unit and the new document name acquired by the second acquisition unit. A job management apparatus having a management unit that manages the acquired job information together. 3. The management means determines whether or not the new document name is included in both the job information acquired by the first acquisition means and the job information acquired by the second acquisition means. And the determining means determines that both the job information acquired by the first acquisition means and the job information acquired by the second acquisition means include the same new document name, The management unit uses the new document name to acquire the job information acquired by the first acquisition unit,
The job management apparatus according to claim 2, wherein the job management apparatus manages a process of merging the job information acquired by the second acquisition unit. 4. The management means reads out the document name from the job information managed by the management means, based on the new document name acquired by the second acquisition means. The job management device described in 1. 5. A data processing apparatus capable of communicating with an image forming apparatus and processing job data of one document-based job, wherein the document name of the document is associated with a new document name uniquely determined in the printing system. A management unit that manages the new document name as job information of the one job, and a transmission control unit that controls a process of transmitting the new document name as the job information of the one job to the image forming apparatus via a network. A data processing device characterized by: 6. The data processing apparatus further comprises issuing means for issuing job identification information for identifying a job, wherein the new document name is the job identification information issued by the issuing means, and the data processing apparatus. The data processing device according to claim 5, wherein the data processing device is generated by a combination with identification information for identifying the. 7. A transmission control unit that controls a process of transmitting a new document name as job information of the one job to the image processing apparatus, and a response of job information including the new document name from the image forming apparatus. 7. The acquisition means for acquiring the job information, the management means managing the job information of the one job based on the new document name acquired by the acquisition means. The described data processing device. 8. A job management method for managing job information of one document-based job capable of communicating with an image forming apparatus and a data processing apparatus, the method comprising: generating in the data processing apparatus based on a document name of the document. A first acquisition step of acquiring the created new document name as the information of the one job; a second acquisition step of acquiring the new document name as the job information of the one job from the image processing apparatus; Based on the new document name acquired in the first acquisition step and the new document name acquired in the second acquisition step, the job information acquired in the first acquisition step, and the job information acquired in the second acquisition step And a management step of managing the acquired job information together. 9. The management step determines whether or not the new document name is included in both the job information acquired in the first acquisition step and the job information acquired in the second acquisition step. When it is determined that both the determination step and the job information acquired in the first acquisition step and the job information acquired in the second acquisition step in the determination step include the new document name, the management The step manages a process of merging the job information acquired in the first acquisition step and the job information acquired in the second acquisition step by using the new document name. 8. The job management method according to item 8. 10. The management step reads out the document name from the job information managed in the management step based on the new document name acquired in the second acquisition step. Job management method described in. 11. A data processing method for processing job data of one document-based job capable of communicating with an image forming apparatus, wherein a document name of the document is associated with a new document name uniquely determined in the printing system. And a transmission control step of controlling the process of transmitting the new document name together with the job data of the one job to the image forming apparatus via the network. A data processing method comprising: 12. The data processing apparatus further comprises an issuing step for issuing job identification information for identifying a job, wherein the new document name is the job identification information issued in the issuing step, and the data processing. The data processing method according to claim 11, wherein the data processing method is generated by a combination with identification information for identifying a device. 13. A transmission control step of controlling a process of transmitting a new document name as job information of the one job to the image processing apparatus, and a response of job information including the new document name from the image forming apparatus. 13. The job information of the one job is managed in the management step based on the new document name acquired in the acquisition step. Described data processing method. 14. A control program executed in a job management apparatus capable of communicating with an image forming apparatus and a data processing apparatus, for managing job information of a single job based on a document, the control program being based on a document name of the document. A first acquisition step of acquiring a new document name generated in the data processing apparatus as information of the one job; and a second acquisition step of acquiring a new document name as job information of the one job from the image processing apparatus Of the job information acquired in the first acquisition step, based on the new document name acquired in the first acquisition step and the new document name acquired in the second acquisition step, And a management step for managing together with the job information acquired in the second acquisition step. A control program characterized by being executed by a storage device. 15. A control program executed in a data processing device capable of processing job data of a single document-based job capable of communicating with an image forming apparatus, wherein the document name of the document is uniquely determined in the printing system. A management step of managing as job information of the one job corresponding to a new document name, and a process of transmitting the new document name together with the job data of the one job to the image forming apparatus via a network A control program for causing the data processing device to execute the transmission control step.