The client computers 111, 113, 115 are user interfaces, which are configured for submitting print jobs for users.
The print server 101 stores predetermined printing tactics, and is configured for capturing and checking the print jobs submitted. The printing tactics specifies requirements of a valid print job, in order to determine if the print job submitted is a valid print job or an invalid print job. The print server 101 is also configured for instructing the printers 105 to execute the valid print jobs.
The database server 102 is configured for storing information of all the print jobs.
The printers 105 can be laser printers, ink-jet printers, wire printers, or any other type of printers. The printers 105 are configured for executing the valid print jobs.
The capturing module 302 is configured for capturing print jobs submitted by the client computers 111, 113, 115.
The checking module 304 is configured for checking the captured print jobs. In detail, the checking module 304 checks the captured print jobs according to the printing tactics. The printing tactics mainly includes: a print period, a file size, a number of pages, color modes, and file types (details will be described in relation to
The saving module 306 is configured for recording information of all the captured print jobs, and saving the information in the database server 102. The information of a print job includes: time of the print job when being captured, an owner of the print job, a title of the print job, content of the print job, a file size, a number of pages, color modes, checking result and so on. The checking result is either valid or invalid herein.
The printing module 308 is configured for instructing the printers 105 to execute the valid print jobs
The printing module 308 is further configured for adding watermarks to the valid print jobs executed. In detail, on instructing the printers 105, the printing module 305 adds watermarks to corresponding print jobs, according to the content of the print jobs saved. Actually, the watermarks, used like background, are part of information of the print jobs.
The column for print period 411 specifies a period of time during which printing is allowable. For instance, the data of the print period 411 can be set as 8:00-17:00. If a user submits a print job beyond this period, the print job will not be allowed.
The column for file size 412 specifies allowable size of a print job. For instance, the data of the file size 412 can be set as 10 MB. If a user submits a print job beyond this size, the print job will not be allowed.
The column for number of pages 413 specifies allowable pages of a print job. For instance, the data of the number of pages 413 can be set as 100 pages/day. Users only can print 100 pages in one day.
The column for color modes 414 specifies allowable color modes of a print job. In general, the color modes typically include CMYK and RGB herein.
The column for file types 415 specifies file types of print jobs that are allowable. For instance, the data of the file types 415 can be set as .doc, .pdf, and .tif.
The printing tactics table illustrated is exemplary of the preferred embodiment of the present invention. In alternative embodiments, the printing tactics table may include one or more other columns in lieu of and/or in addition to the above-described columns 411, 412, 413, 414, 415. Such other columns can provide other data on printing tactics. Furthermore, the printing tactics table may be replaced by two or more similar tables.
In step S502, the capturing module 302 captures print jobs submitted by the client computers 111, 113, 115.
In step S503, the checking module 304 checks the captured print jobs. In detail, the checking module 304 checks the captured print jobs according to the printing tactics. The printing tactics includes, for example, a print period, a file size, a number of pages, color modes, and file types. The checking module 304 marks a print job as valid, only if the print job satisfies all the printing tactics. Otherwise if the print job does not satisfy all the printing tactics, the checking module 304 marks the print job as invalid. In step S503, valid print jobs and invalid print jobs of the print jobs captured are all marked.
In step S504, the saving module 304 records information of all the captured print jobs, and saves the information in the database server 102. The information of a print job includes: time of the print job when being captured, an owner of the print job, a title of the print job, content of the print job, a file size, a number of pages, color modes, checking result and so on. The checking result is either valid or invalid herein.
In step S505, the printing module 305 instructs the printers 105 to execute the valid print jobs, and add watermarks to the print jobs at the same time. In detail, on instructing the printers 105, the printing module 305 adds watermarks to corresponding print jobs according to content of the print jobs saved. Actually, the watermarks, which are used like background, are part of information of the print jobs. For instance, the printing module 308 can add time of a print job when being captured and an owner of the print job as watermark (referring to
Although the present invention has been specifically described on the basis of a preferred embodiment and a preferred method, the invention is not to be construed as being limited thereto. Various changes or modifications may be made to said embodiment and method without departing from the scope and spirit of the invention.
Number | Date | Country | Kind |
---|---|---|---|
200610200842.7 | Sep 2006 | CN | national |