US9235357B2 - Information processing apparatus, control method thereof, and computer-readable medium - Google Patents

Information processing apparatus, control method thereof, and computer-readable medium Download PDF

Info

Publication number
US9235357B2
US9235357B2 US13/649,406 US201213649406A US9235357B2 US 9235357 B2 US9235357 B2 US 9235357B2 US 201213649406 A US201213649406 A US 201213649406A US 9235357 B2 US9235357 B2 US 9235357B2
Authority
US
United States
Prior art keywords
print
management system
job
cancel
page
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related, expires
Application number
US13/649,406
Other languages
English (en)
Other versions
US20130100493A1 (en
Inventor
Koichiro Otsuka
Kenichiro Uotani
Atsuko Koike
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Canon Inc
Original Assignee
Canon Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Canon Inc filed Critical Canon Inc
Assigned to CANON KABUSHIKI KAISHA reassignment CANON KABUSHIKI KAISHA ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KOIKE, ATSUKO, OTSUKA, KOICHIRO, UOTANI, KENICHIRO
Publication of US20130100493A1 publication Critical patent/US20130100493A1/en
Application granted granted Critical
Publication of US9235357B2 publication Critical patent/US9235357B2/en
Expired - Fee Related legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1202—Dedicated interfaces to print systems specifically adapted to achieve a particular effect
    • G06F3/1203—Improving or facilitating administration, e.g. print management
    • G06F3/1207—Improving or facilitating administration, e.g. print management resulting in the user being informed about print result after a job submission
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1223—Dedicated interfaces to print systems specifically adapted to use a particular technique
    • G06F3/1229—Printer resources management or printer maintenance, e.g. device status, power levels
    • G06F3/1234—Errors handling and recovery, e.g. reprinting
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1278—Dedicated interfaces to print systems specifically adapted to adopt a particular infrastructure
    • G06F3/1285—Remote printer device, e.g. being remote from client or server
    • G06F3/1288—Remote printer device, e.g. being remote from client or server in client-server-printer device configuration
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1223—Dedicated interfaces to print systems specifically adapted to use a particular technique
    • G06F3/1237—Print job management
    • G06F3/1259—Print job monitoring, e.g. job status

Definitions

  • the present invention relates to an information processing apparatus, control method thereof, and computer-readable medium and, more particularly, to control for sharing the status of a print job in a print system.
  • a digital photo print system is formed from subsystems such as an order management system, print management system, and printer.
  • the order management system receives an Internet order from the home PC (Personal Computer: to be referred to as a PC hereinafter) of an end user, or a print order in a DPE shop.
  • the print order is transferred as a print job to each subsystem.
  • the print management system converts the print job into a format processable by a predetermined printer.
  • the converted print job is printed out by a dedicated printer installed in a place (laboratory) where printing is actually performed. In this system, the respective subsystems are often installed in places spaced apart from each other.
  • the subsequent print management system when the order management system transfers a print job containing a job error, the subsequent print management system outputs an instruction to the printer to cancel the print job.
  • the print management system notifies the order management system at an upper level that the error regarding the print job has occurred and the cause is a job error, or that the print job has been canceled.
  • the printer at a lower level in print processing recognizes only that a cancel instruction to the print job has been issued.
  • a display mismatch occurs between the subsystems.
  • the display unit of the print management system displays a job error, and that of the printer displays job cancellation.
  • the printer cannot recognize the situation in which the cancel instruction has been issued. Also, even when the user cancels a print job issued from each upper subsystem, for example, the printer serving as a lower subsystem cannot recognize the situation in which the cancel instruction has been issued.
  • the reason of job cancellation cannot be shared between the devices.
  • the respective subsystems are often installed in places spaced apart from each other. It is very inconvenient for an end user, operator, or the like who actually operates each subsystem, that the reason of job cancellation cannot be shared.
  • the present invention has been made to solve the conventional problems, and can share the reason of job cancellation throughout upper to lower subsystems which form a print system.
  • an information processing apparatus which transfers a print job to a lower apparatus that is included in a print system and located at a lower level in print processing, comprising: a determination unit configured to determine whether to cancel the print job; and a cancel command issuing unit configured, when the determination unit determines to cancel processing for the print job, to issue, to the lower apparatus for the print job, a cancel command to which information about a cancel reason is added.
  • a method of controlling an information processing apparatus which transfers a print job to a lower apparatus that is included in a print system and located at a lower level in print processing, comprising the steps of: determining whether to cancel the print job; and issuing, when to cancel the print job is determined in the determining step, to the lower apparatus for the print job, a cancel command to which information about a cancel reason is added.
  • a non-transitory computer-readable medium storing a program for causing a computer to function as a determination unit configured to determine whether to cancel a print job transferred to a lower apparatus that is included in a print system and located at a lower level in print processing, and a cancel command issuing unit configured, when the determination unit determines to cancel the print job, to issue, to the lower apparatus for the print job, a cancel command to which information about a cancel reason is added.
  • the reason of cancellation of a print job can be shared throughout upper to lower subsystems which form a print system.
  • FIG. 1 is a view exemplifying a system arrangement according to an embodiment
  • FIG. 2A is a block diagram exemplifying the arrangement of a print system according to the first embodiment
  • FIG. 2B is a block diagram exemplifying the arrangement of an image processing unit according to the first embodiment
  • FIG. 2C is a block diagram exemplifying the arrangement of an image processing unit according to the first embodiment
  • FIG. 3 is a chart exemplifying a command sequence when a print management system detects a job error
  • FIGS. 4A , 4 B, and 4 C are views exemplifying cancel commands
  • FIG. 5 is a chart exemplifying a command sequence when the image processing unit detects a data error
  • FIG. 6 is a chart exemplifying command sequence 1 when an order management system cancels a print job
  • FIG. 7 is a chart exemplifying command sequence 2 when the order management system cancels a print job
  • FIG. 8 is a flowchart showing the operation of the print management system when the print management system detects a job error according to the first embodiment
  • FIG. 9 is a flowchart showing the operation of the print management system when the user cancels a print job in the order management system according to the first embodiment
  • FIG. 10 is a flowchart showing the operation of the order management system according to the first embodiment
  • FIG. 11 is a flowchart showing the operation of a printer according to the first embodiment
  • FIGS. 12A and 12B are flowcharts showing the operation of the printer which changes processing depending on the form of a printed product when a data error occurs in a print job according to the first embodiment
  • FIG. 13 is a block diagram exemplifying the arrangement of a print management system according to the second embodiment
  • FIG. 14 is a flowchart showing the operation of the print management system when a printer driver exists in the print management system according to the second embodiment
  • FIG. 15 is a view showing the print form of a book according to the third embodiment.
  • FIG. 16 is a view exemplifying a print job according to the third embodiment.
  • FIG. 17 is a flowchart showing the operation of a print management system which changes processing depending on the form of a printed product when a job error occurs in a print job according to the third embodiment.
  • FIG. 18 is a flowchart showing the operation of a printer which changes processing depending on the form of a printed product when a job error occurs in a print job according to the third embodiment.
  • the connection of a print system in the embodiment will be exemplified.
  • the print system according to the embodiment includes an order management system 101 , print management system 102 , and printer 103 , which are connected via a network 104 , as shown in FIG. 1 .
  • the number of systems of each type is one in FIG. 1 , but is not limited to this.
  • a plurality of information processing apparatuses may implement processing of the order management system 101 .
  • Each system can be implemented by a general-purpose information processing apparatus such as a PC.
  • the order management system 101 receives a print order from the user, generates a print job containing print settings and image contents corresponding to the order, and issues it to the print management system 102 .
  • the print management system 102 analyzes and converts the generated print job, and issues it to the printer 103 .
  • the printer 103 prints in accordance with the print settings, and updates job status information managed in the printer 103 .
  • the printer 103 periodically notifies the print management system 102 of the job status information.
  • the printer 103 may be, for example, an MFP (MultiFunction Peripheral) having the print function.
  • the print management system 102 Upon receiving a request from the order management system 101 , the print management system 102 notifies the order management system 101 of the job status information.
  • an apparatus at a level where it executes processing earlier in a processing sequence for example, receives data first, will be described as an apparatus at an upper level, compared to another apparatus.
  • an apparatus which performs processing later will be described as an apparatus at a lower level.
  • the print system according to the embodiment includes the order management system 101 , print management system 102 , and printer 103 .
  • the print management system 102 includes an I/F 204 between the order management system 101 and the print management system 102 , a call processing unit 205 , a print management unit 206 , a status management unit 207 , a print processing unit 208 , a status processing unit 209 , and a protocol processing unit 210 .
  • the I/F 204 is an I/F at a boundary where a request from the order management system 101 is transferred to the print management system 102 .
  • the I/F 204 also includes an event notification I/F from the print management system 102 to the order management system 101 .
  • the call processing unit 205 accepts a request from the order management system 101 as an instance.
  • the call processing unit 205 returns a processing result to the accepted request. More specifically, the call processing unit 205 performs processing request acceptance/result return for initialization, setting change, end, error notification, and the like.
  • the print management unit 206 performs request acceptance/result return for a print job and other jobs.
  • the status management unit 207 performs request acceptance/result return for status acquisition and listener registration. The status management unit 207 also notifies a difference event and tracking job event by a registered listener.
  • the print processing unit 208 queues print jobs accepted by the print management unit 206 , and sequentially transfers them to the printer 103 .
  • the print processing unit 208 has an internal arrangement as shown in FIG. 2B .
  • a job management unit 212 holds job data accepted from the print management unit 206 , and converted job data.
  • a job conversion unit 213 analyzes and converts job data.
  • the job conversion unit 213 in the print processing unit 208 detects a job error in a print job.
  • a job transfer unit 214 inputs the converted job data to the protocol processing unit 210 , and acquires a response to it.
  • the status processing unit 209 queues a status acquisition request accepted by the status management unit 207 , and transfers it to the printer 103 .
  • the status processing unit 209 holds, as a status cache, a status which has been acquired from the printer 103 as a response to the status acquisition request. Further, the status processing unit 209 detects a state transition, and inputs it to an event notification unit (not shown).
  • the protocol processing unit 210 performs queuing control of requests from the respective processing units, port allocating, and transfer/reception control to/from the printer 103 .
  • an image processing unit 211 in the printer 103 has an arrangement as shown in FIG. 2C .
  • an image conversion unit 215 analyzes the print settings and content data of a print ticket.
  • the image conversion unit 215 rasterizes the content data according to the analyzed print settings.
  • a color conversion unit 216 converts the rasterized content data from RGB into CMYK.
  • a print command generation unit 217 generates a print command in the CMYK format using the converted content data, and transfers it to a printer engine 218 .
  • the printer engine 218 outputs an image in accordance with the generated print command.
  • a print job which is generated by the order management system 101 and transferred to the print management system 102 includes contents and a print ticket formed from information such as print settings and copy count setting.
  • the contents comply with, for example, JPEG (Joint Photographic Experts Group), BMP (Bit MaP), or PDF (Portable Document Format).
  • the print management unit 206 in the call processing unit 205 accepts, via the I/F 204 , a request which is a print job input from the order management system 101 to the print management system 102 .
  • the print management unit 206 generates a provisional status called a pseudo job status.
  • the pseudo job status will be explained. In general, there is a time lag until the printer 103 sends back an actual print job status after a print job is issued to the printer 103 .
  • the pseudo job status is therefore used as a provisional status until job status information is received from the printer 103 .
  • a print job which has been accepted by the print management system 102 and is queued has not been issued yet to the printer 103 , and cannot be acquired as job status information of the printer 103 .
  • the print job itself has already been issued from the order management system 101 to the print management system 102 , so the print management system 102 performs the state management.
  • the print job is transferred from the print management unit 206 to the print processing unit 208 .
  • the print processing unit 208 analyzes the print job, and converts it into a command optimized for the printer 103 .
  • the print ticket which forms the print job is analyzed and converted into a command, but no content is converted.
  • the protocol processing unit 210 transfers the converted print job to the printer 103 .
  • the image processing unit 211 in the printer 103 renders the content and prints it out in accordance with the print ticket information, that is, print settings which form the print job.
  • the printer 103 Upon receiving the print job, the printer 103 generates job status information. The printer 103 notifies the print management system 102 of the updated job status information at a periodical timing.
  • the updated job status information is transferred to the status processing unit 209 via the protocol processing unit 210 .
  • the status processing unit 209 holds the accepted job status information as a status cache.
  • the status processing unit 209 transfers the updated job status information to the status management unit 207 , and the status management unit 207 updates the managed job status information.
  • the order management system 101 is notified via the I/F 204 of the newly updated job status information. By using the notified job status information, the order management system 101 updates job status information managed by it.
  • a lower subsystem sometimes determines that a print job created as a result of a print instruction by an end user in the order management system 101 is an error job arising from data impropriety. This occurs in roughly two cases. In one case, for example, a print instruction designates double-sided print though double-sided print is impossible for a selected paper medium, or there is no content to be printed. These errors arise from impropriety of a print ticket which describes print settings. A print job error arising from impropriety of a print ticket will be called a “job error”.
  • a print-designated content in the order management system 101 has a file format which is not a print target of the printer 103 , or a file itself is corrupted.
  • an error arises from impropriety in the target content of a print job, and this error will be called a “data error”.
  • errors arising from two types of data impropriety exist.
  • the print processing unit 208 in the print management system 102 detects a job error regarding print ticket information which forms a print job.
  • the image processing unit 211 in the printer 103 detects a data error regarding an image content.
  • the order management system 101 issues a print job to the print management system 102 according to a predetermined sequence (step S 301 ).
  • the print management system 102 Upon receiving the print job, the print management system 102 issues the print job when it can start issuing the print job to the printer 103 (step S 302 ). That is, the print management system 102 can start issuing the print job to the printer 103 before the end of receiving all data of the print job from the order management system 101 . Assume that the print processing unit 208 in the print management system 102 detects a job error in the print job while issuing the print job to the printer 103 (step S 303 ). In this case, the print management system 102 cancels the issuing of the print job to the printer 103 (step S 304 ).
  • the print management system 102 detects a job error during processing of the third content and the print ticket. In this case, the print management system 102 issues a cancel command to cancel the print job issued to the printer 103 .
  • the user issues a print instruction with the following settings in the order management system 101 :
  • a file name described in a print ticket does not match the file name of a content.
  • step S 304 reason information about cancellation (to be referred to as a cancel reason hereinafter) is added to the cancel command issued by the print management system 102 . From this information, the printer 103 can recognize that the print job is canceled not by merely “job cancellation” but by cancellation owing to a “job error”.
  • the printer 103 recognizes that the print job is canceled by merely “job cancellation”, and displays “job cancellation” on the UI (User Interface) of the printer 103 .
  • UI User Interface
  • FIG. 4A exemplifies a cancel command.
  • This cancel command is a cancel command to which a cancel reason described in the xml format is added.
  • the following description represents error details corresponding to “job cancellation”:
  • the print management system 102 notifies the order management system 101 at an upper level that the job error has occurred (step S 305 ).
  • the order management system 101 Upon receiving the notification ErrorEventNotify from the print management system 102 , the order management system 101 issues a status acquisition command GetStatus to a lower system. The issued status acquisition command reaches the printer 103 via the print management system 102 . The printer 103 sends back job status information to the print management system 102 (step S 306 ).
  • the print management system 102 reflects, in data held by it, the job status information acquired from the printer 103 , and sends back the status information to the upper order management system 101 . At this time, the print management system 102 displays the “job error” information on the UI, as needed.
  • the order management system 101 also reflects the received job status information in data held by it, and displays the “job error” information on the UI, as needed.
  • FIG. 4B exemplifies the cancel reason of the cancel command and job status error information.
  • Information ⁇ cancelreason> serving as the cancel reason added to the cancel command is managed as job status error information ⁇ jobstatusdetail> in the printer 103 .
  • the printer 103 sets the job status error information ⁇ jobstatusdetail> in the status upon status acquisition, and sends it back to a system at an upper level. As a result, the error information can be unified throughout upper to lower systems.
  • the printer 103 detects that a data error has occurred.
  • An example of a command sequence when the image processing unit 211 in the printer 103 detects a data error regarding a content will be explained with reference to FIG. 5 .
  • the order management system 101 issues a print job to the print management system 102 according to a predetermined sequence (step S 401 ).
  • the print management system 102 issues the print job when it can start issuing the print job to the printer 103 (step S 402 ).
  • the printer 103 detects a data error in the received job during reception of the print job (step S 403 ). In this case, the printer 103 sends back a response “NG” to the print management system 102 (step S 404 ).
  • the print management system 102 Upon receiving the response “NG”, the print management system 102 notifies the upper order management system 101 of the error (step S 405 ). Upon receiving the notification ErrorEventNotify, the order management system 101 issues a command GetStatus to acquire job status information. The print management system 102 issues a command to the printer 103 to acquire job status information of the printer 103 (step S 406 ).
  • the printer 103 notifies the upper system of the job status information.
  • the job status information contains error detail information of a cancel job (step S 407 ).
  • the error information can therefore be shared throughout the upper to lower systems. If there is no error detail information of the cancel job, the print management system 102 and order management system 101 can only determine that the printer 103 has canceled the job at the upper levels. In this case, the print management system 102 and order management system 101 recognize that the printer 103 has performed merely “job cancellation”, and display “job cancellation” on UIs corresponding to the printer 103 .
  • the print management system 102 starts the processing upon receiving a print job of N pages from the order management system 101 .
  • the page of interest is described as the nth page.
  • the print management system 102 repeats the following processes for N pages contained in the received print job (steps S 701 to S 711 ).
  • the print management system 102 analyzes and converts the page of interest in the print job (step S 702 ).
  • the print management system 102 determines whether an error exists in the print ticket in print ticket analysis of the print job (step S 703 ). If no error exists in the print ticket (NO in step S 703 ), the print management system 102 transfers the page of interest to the printer 103 when it can transfer the page of interest (step S 710 ). Unless an error occurs, the print management system 102 repeats job conversion/transfer processing till the completion of transferring N pages. Upon completion of normally transferring all pages, the print management system 102 displays a message to this effect on the UI.
  • step S 703 the print management system 102 determines whether the page of interest is the second or subsequent page (step S 704 ). If the page of interest is the first page (NO in step S 704 ) the print management system 102 deletes the print job from the queue (step S 707 ). The process then advances to step S 708 .
  • step S 704 If the page of interest is the second or subsequent page (YES in step S 704 ), the print job has already been issued to the printer 103 . Thus, the print management system 102 issues a job cancel command to the printer 103 for the print job. At this time, the print management system 102 adds the cancel reason to the job cancel command, and transfers the job cancel command (step S 705 ). The print management system 102 determines whether the page of interest is the Nth page (step S 706 ).
  • step S 706 the print management system 102 deletes the print job from the queue (step S 707 ). Accordingly, no subsequent print job is issued even during processing of the print job. If the page of interest is the Nth page (YES in step S 706 ), the process advances to step S 708 .
  • the print management system 102 notifies the order management system 101 at an upper level of the error event (step S 708 ).
  • the print management system 102 displays the cancel reason (“job error” in this case) on the UI, and ends the processing sequence (step S 709 ).
  • the order management system 101 determines whether the print management system 102 has instructed the order management system 101 to cancel a print job until the order management system 101 issues a print job and transfers it to the print management system 102 (step S 901 ). If the order management system 101 has not received a cancel instruction (NO in step S 901 ), it determines whether the order management system 101 has received a notification that an error has been detected in a system at a lower level, including the print management system 102 , until the order management system 101 transfers the print job (step S 902 ).
  • step S 905 determines whether the user has canceled the print job. If the user has not canceled the print job (NO in step S 905 ), the order management system 101 transfers the print job to the print management system 102 (step S 909 ). After that, the processing sequence ends.
  • step S 905 the order management system 101 confirms whether the print job has not been transferred yet to the print management system 102 (step S 906 ). If the print job has not been transferred yet (YES in step S 906 ), the order management system 101 advances to step S 908 . If transfer of the print job has started (NO in step S 906 ), the order management system 101 transfers a cancel reason to the print management system 102 together with a cancel command (step S 907 ). The order management system 101 displays the cancel reason on the UI, and ends the processing. As the cancel reason displayed here, a message that the user has canceled the print job is displayed.
  • step S 903 If the order management system 101 receives a cancel instruction or error notification from the print management system 102 (YES in step S 901 or S 902 ), the process advances to step S 903 .
  • the order management system 101 acquires the cancel reason (one of “job error”, “data error”, and “user cancellation” in this case) from the print management system 102 (step S 903 ).
  • the order management system 101 displays the acquired cancel reason on the UI (step S 904 ).
  • the processing sequence then ends.
  • the operation of the printer 103 will be explained with reference to the flowchart of FIG. 11 . Note that this processing is implemented by reading out a program held in a storage unit (not shown) and executing it by the CPU (not shown) of the printer 103 .
  • the printer 103 determines whether the user has canceled a print job (step S 1001 ). If the user has not canceled the print job (NO in step S 1001 ), the printer 103 determines whether it has received a job cancel command and cancel reason from the print management system 102 (step S 1007 ). If the printer 103 has not received a cancel command (NO in step S 1007 ), it executes print processing for the print job (step S 1008 ). Upon completion of printing the print job, the printer 103 displays a message to this effect on the UI, and ends the processing sequence.
  • the printer 103 If the printer 103 has received a job cancel command and a cancel reason added to it from the print management system 102 at an upper level (YES in step S 1007 ), it deletes and cancels the print job (step S 1005 ). The printer 103 displays the cancel reason (“job error” in this case) on the UI, and ends the processing sequence (step S 1006 ).
  • step S 1001 If the user has canceled the print job (YES in step S 1001 ), the printer 103 notifies the print management system 102 that the print job has been canceled (step S 1002 ). The printer 103 confirms whether image processing for the print job has not been completed yet (step S 1003 ). If image processing has not been completed yet (YES in step S 1003 ), the printer 103 cancels image processing for the print job (step S 1004 ). Thereafter, the process advances to step S 1005 . If image processing has been completed (NO in step S 1003 ), the process advances to step S 1005 .
  • the printer 103 deletes the print job (step S 1005 ), and displays the cancel reason (“user cancellation” in this case) on the UI (step S 1006 ).
  • the operation of the printer 103 when a data error is detected in a print job will be described with reference to FIGS. 12A and 12B . Note that this processing is implemented by reading out a program held in the storage unit (not shown) and executing it by the CPU (not shown) of the printer 103 .
  • the printer 103 changes processing depending on the form setting of a printed product. Assume that the form setting is described in the print ticket. After the start of processing, the printer 103 determines whether a print job designates single sheet print (step S 1101 ). “Single sheet print” is print processing of outputting a printed material formed from one sheet. In contrast to “single sheet print”, print processing of outputting a book-like printed material formed from a plurality of pages will be described as “book print”. If the print job designates single sheet print (YES in step S 1101 ), the printer 103 performs processes in steps S 1102 to S 1112 . If the print job does not designate single sheet print (NO in step S 1101 ), the printer 103 performs processes in steps S 1113 to S 1120 .
  • the printer 103 sequentially processes, as the page of interest, N pages which form the print job (step S 1102 ). First, the printer 103 starts image processing for the first page as the page of interest (step S 1103 ). The printer 103 determines whether an error exists in the content of the page of interest (step S 1104 ). If the printer 103 detects that an error exists in the content data (YES in step S 1104 ), the printer 103 determines whether the setting can continue printing (step S 1105 ). As the setting capable of continuing printing, for example, if there is a single-sheet single-sided print setting, it can be determined that printing can continue for pages other than a page on which an error has occurred, so processing can continue.
  • step S 1105 If the setting can continue print processing (YES in step S 1105 ), the printer 103 notifies the upper print management system 102 that an error has occurred in the page of interest (step S 1106 ). The printer 103 displays the cancel reason (“data error” in this case) on the UI of the printer 103 (step S 1107 ). The process returns to step S 1103 , and the printer 103 continues image processing for subsequent pages.
  • step S 1105 If the printer 103 determines in step S 1105 that printing cannot continue (NO in step S 1105 ), it deletes the received print job (step S 1108 ). As a case in which printing cannot continue, for example, if image data on the obverse surface is improper in single-sheet double-sided print, printing on the reverse surface should not continue.
  • the printer 103 issues, to the upper print management system 102 , an error event notification that a data error has occurred (step S 1109 ).
  • the printer 103 displays the cancel reason (“data error” in this case) on the UI of the printer 103 (step S 1110 ). Thereafter, the processing sequence ends.
  • step S 1111 the printer 103 executes printing of the page of interest.
  • the printer 103 performs print processing for all pages unless an error occurs.
  • the printer 103 displays the completion of printing on the UI of the printer 103 , and ends the processing sequence.
  • the printer 103 sequentially processes, as the page of interest, N pages which form the print job (step S 1113 ). First, the printer 103 starts image processing for the first page (step S 1114 ). The printer 103 determines whether an error exists in the content of the page of interest (step S 1115 ). If the printer 103 detects that an error exists in the content data (YES in step S 1115 ), it deletes the received print job (step S 1116 ). The printer 103 notifies the upper print management system 102 of an error event representing that a data error has occurred (step S 1117 ). The printer 103 displays the cancel reason (“data error” in this case) on the UI of the printer 103 (step S 1118 ). Then, the processing sequence ends.
  • step S 1115 If no error exists in the content (NO in step S 1115 ), the printer 103 performs image processing for all pages which form the print job, unless an error occurs (step S 1119 ). The printer 103 prints the print job having undergone image processing (step S 1120 ). The printer 103 displays the completion of printing on the UI of the printer 103 , and ends the processing sequence.
  • step S 1101 the printer may not switch processing.
  • steps S 1113 to S 1120 are executed to delete a print job if an error exists in the content regardless of the form of a printed product. In other words, there is no single sheet print processing.
  • a case in which the print management system detects an error has been described as a case in which the print management system 102 issues a cancel command.
  • Another case in which the user cancels a print job in the order management system 101 after the order management system 101 issues the print job will be explained with reference to FIG. 6 .
  • the order management system 101 issues a print job to the print management system 102 according to a predetermined sequence (step S 501 ).
  • the print management system 102 issues the job when it can start issuing the print job to the printer 103 (step S 502 ). That is, the print management system 102 can start issuing the job to the printer 103 before the end of receiving all the print jobs from the order management system 101 .
  • step S 503 the order management system 101 issues a cancel command to the print management system 102 (step S 504 ).
  • the print management system 102 cancels the issuing of the print job to the printer 103 (step S 505 ).
  • a cancel reason to be added to the cancel command issued by the print management system 102 in step S 504 is as follows:
  • the print management system 102 Upon receiving a print job from the order management system 101 , the print management system 102 issues the job when it can start issuing the print job to the printer 103 . However, assume that the order management system 101 cancels the print job and the cancel command reaches the print management system 102 before the print management system 102 issues the print job. In this case, the print management system 102 does not issue the cancel command to the printer 103 .
  • FIG. 7 shows a command sequence in this case.
  • the order management system 101 issues a print job to the print management system 102 according to a predetermined sequence (step S 601 ).
  • the print management system 102 issues the job when it can start issuing the print job to the printer 103 .
  • the order management system 101 notifies the print management system 102 of the cancel command (step S 603 ).
  • the print management system 102 has not issued the print job to the printer 103 yet (step S 604 ), and determines that no cancel command need be issued.
  • the print management system 102 does not issue a cancel command to the printer 103 (step S 605 ).
  • the print management system 102 Since the target print job has been canceled, the print management system 102 notifies the upper order management system 101 of an error event (step S 606 ). In response to the notification ErrorEventNotify from the print management system 102 , the order management system 101 issues a job status acquisition command. Upon receiving the job status acquisition command, the print management system 102 issues the job status acquisition command to the printer 103 . In this case, the printer 103 has not recognized the presence of the target print job, and sends back job status information together with a cancel reason using a pseudo job status managed in the print management system 102 (step S 607 ).
  • the print management system 102 determines whether upon receiving a print job from the order management system 101 at an upper level, it has received a cancel command from the order management system 101 to cancel the print job (step S 801 ). If the print management system 102 has received the cancel command from the order management system 101 (YES in step S 801 ), it determines whether the print management system 102 has already transferred the print job to the printer 103 (step S 802 ).
  • step S 802 determines whether job conversion processing for issuing the print job to the printer 103 has already ended (step S 803 ). If the print job is being converted (NO in step S 803 ), the print management system 102 cancels the job conversion (step S 804 ). The print management system 102 deletes the print job from the queue of the print management system 102 , and cancels transfer of the print job (step S 805 ). The process then advances to step S 807 . If conversion of the print job has ended (YES in step S 803 ), the process directly advances to step S 805 .
  • step S 802 If the print management system 102 has already issued the print job to the printer 103 (NO in step S 802 ), it adds the cancel reason to a cancel command for canceling printing of the target print job, and issues the cancel command. The print management system 102 transfers the issued cancel command to the printer 103 (step S 806 ).
  • the print management system 102 displays the cancel reason (“user cancellation” in this case) on the UI of the print management system 102 , and ends the processing sequence (step S 807 ).
  • the print management system 102 If the print management system 102 has not received the cancel command from the order management system 101 (NO in step S 801 ), it confirms whether it has received a print job cancel event notification from the printer 103 . This notification is issued when, for example, the user cancels reception of a print job by operating the panel of the printer 103 while the printer 103 receives the print job. If the print management system 102 has received the cancel event notification (YES in step S 808 ), it acquires job status information from the printer 103 (step S 809 ). The print management system 102 notifies the order management system 101 at an upper level of an error event (step S 810 ). After that, the print management system 102 displays, on the UI of the print management system 102 , the cancel reason (“user cancellation” in this case) based on the cancel status acquired from the printer 103 , and ends the processing sequence (step S 811 ).
  • the print management system 102 If the print management system 102 has not received the cancel event notification from the printer 103 (NO in step S 808 ), it transfers the print job to the printer 103 (step S 812 ). If no error occurs in the print job, all the print job has been transferred to the printer 103 , and printing is completed, the print management system 102 displays the completion of transfer on the UI of the print management system 102 , and ends the processing sequence.
  • step S 903 the cancel reason acquired from the print management system 102 is “user cancellation”.
  • step S 904 the order management system 101 displays a message to this effect on the UI of the order management system 101 .
  • step S 1006 the cancel reason displayed on the UI of the printer 103 is “user cancellation”.
  • information about the reason why a print job has been canceled can be shared between the subsystems. Further, displays in the respective subsystems can be made to match each other.
  • the printer 103 includes the image processing unit 211 which renders an image content.
  • a printer driver 1201 exists in a print management system 102 .
  • the printer driver 1201 in the print management system 102 renders an image content.
  • the print management system 102 detects both a job error regarding job ticket information which forms a print job, and a job error regarding an image content.
  • a print job which is generated by an order management system 101 and transferred to the print management system 102 includes a job ticket formed from information such as print settings and copy count setting, and image contents of JPG, BMP, PDF, or the like.
  • a print management unit 206 in a call processing unit 205 accepts, via an I/F 204 , a request which is a print job input from the order management system 101 to the print management system 102 .
  • the print management unit 206 generates a pseudo job status.
  • a print processing unit 208 receives and analyzes the print job, and convers a job ticket, which forms the print job, into a command optimized for a printer 103 .
  • the printer driver 1201 renders the content.
  • the printer driver 1201 also functions as the protocol processing unit 210 in FIG. 2A according to the first embodiment.
  • the converted print job is transferred to the printer 103 and printed out.
  • the printer 103 Upon receiving the print job, the printer 103 generates job status information. The printer 103 notifies the print management system 102 of the updated job status information at a periodical timing.
  • the updated job status information is transferred to a status processing unit 209 via the printer driver 1201 , and held as a status cache.
  • the status processing unit 209 transfers the updated job status information to the status management unit 207 .
  • the status management unit 207 updates job status information managed by it.
  • the order management system 101 is notified via the I/F 204 of the updated job status information. By using the received job status information, the order management system 101 updates the managed job status information.
  • the print management system 102 detects both a job error regarding job ticket information which forms a print job, and a data error regarding a content.
  • a command sequence in this case is the same as that shown in FIG. 3 according to the first embodiment.
  • the command sequence upon a data error shown in FIG. 5 according to the first embodiment is not executed in the second embodiment.
  • command sequences when the order management system 101 cancels a print job are the same as those shown in FIGS. 6 and 7 according to the first embodiment.
  • the operation of the print management system 102 when the print management system 102 detects a job error will be described with reference to the flowchart of FIG. 14 .
  • this processing is implemented by reading out a program held in a storage unit (not shown) and executing it by the CPU (not shown) of the print management system 102 .
  • a print job is formed from N pages, and the page of interest is described as the nth page.
  • the print management system 102 starts the processing upon receiving a print job of N pages from the order management system 101 , and executes the following processes for the respective pages which form the print job (steps S 1301 to S 1309 ).
  • the print management system 102 analyzes and converts the page of interest in the print job (step S 1302 ).
  • the print management system 102 determines whether an error exists in the print ticket in print ticket analysis of the print job (step S 1303 ). This error determination corresponds to determination of whether a job error exists. If no error exists (NO in step S 1303 ), the print management system 102 transfers the page of interest to the print processing unit 208 in the print management system 102 (step S 1308 ). The print management system 102 transfers, to the print processing unit 208 , all pages which form the print job unless an error occurs in the page of interest. The process then advances to step S 1310 .
  • step S 1303 the print management system 102 determines whether the page of interest having the error is the final page (step S 1304 ). If the page of interest is the final page (YES in step S 1304 ), the process directly advances to step S 1306 . If the page of interest is not the final page (NO in step S 1304 ), the print management system 102 deletes the print job from the queue (step S 1305 ). The print management system 102 notifies the order management system 101 at an upper level of the error event (step S 1306 ). The print management system 102 displays the cancel reason (“job error” in this case) on the UI of the print management system 102 , and ends the processing sequence (step S 1307 ).
  • the print management system 102 executes the following processes for the respective pages which form the print job (steps S 1310 to S 1318 ).
  • the print management system 102 executes image processing for the page of interest (step S 1311 ).
  • the print management system 102 determines whether an error exists in the content of the page of interest (step S 1312 ). This error determination corresponds to determination of whether a data error exists. If no error exists (NO in step S 1312 ), the print management system 102 performs image processing for all pages which form the print job unless an error exists in the page of interest. Then, the process advances to step S 1319 .
  • the print management system 102 transfers the print job to the printer 103 to print. The processing sequence then ends.
  • step S 1312 determines whether the page of interest is the first page (step S 1313 ). If the page of interest on which the data error has been detected is the first page (NO in step S 1313 ), the print management system 102 deletes the print job from the queue of the print management system 102 (step S 1315 ). Then, the process advances to step S 1316 .
  • step S 1313 If the page of interest on which the data error has been detected is not the first page (YES in step S 1313 ), the print job has already been issued to the printer 103 . Hence, the print management system 102 adds the cancel reason to a job cancel command for the print job, and issues the job cancel command to the printer 103 (step S 1314 ).
  • the print management system 102 notifies the order management system 101 at an upper level of the error event (step S 1316 ).
  • the print management system 102 displays the cancel reason (“data error” in this case) on the UI of the print management system 102 , and ends the processing sequence (step S 1317 ).
  • the third embodiment will exemplify cancel processing by a print management system 102 when the print management system 102 detects a job error during issuing of a job to a printer 103 .
  • the printer 103 switches the criterion of cancellation in accordance with print settings, as represented by step S 1101 of FIG. 12A .
  • the print management system 102 switches the criterion of cancellation in accordance with print settings.
  • the overall arrangement of the system and the remaining common parts are the same as those in the first embodiment, and a description thereof will not be repeated.
  • Examples of single sheet print forms are a photo print, card, calendar, collage, poster, and portrait.
  • Examples of book print forms are saddle stitching 1401 , ring binding 1402 , adhesive binding 1403 , and single-sided print data bonding 1404 .
  • double-sided print is performed, the three sides of the printed material are cut, and the printed material is stapled at the center.
  • a printed material having undergone single- or double-sided print is ring-bound.
  • a printed material having undergone double-sided print is glued as shown in FIG. 15 , and the adhesive-bound body is wrapped with a cover.
  • a body and cover is glued as shown in FIG. 15 , and the bonded body is wrapped with a hard cover.
  • the hard cover is prepared by lamination or cardboard bonding.
  • a case in which a job is formed from four images (contents) and the print management system detects a job error or data error in the third image, as shown in FIG. 16 will be explained.
  • the print management system 102 keeps issuing the print job while skipping the page on which the error has been detected in the print job.
  • the print management system 102 notifies an order management system 101 at an upper level via a predetermined API (Application Program Interface) that printing is partially successful.
  • image data 1503 out of image data 1501 , 1502 , 1503 , and 1504 is improper.
  • the print management system 102 transfers job data of the image data 1501 and 1502 to the printer 103 , skips the image data 1503 , and then transfers job data of the image data 1504 to the printer 103 .
  • the print management system 102 issues a cancel command to cancel the issued print job upon detecting the error in the print job.
  • the print management system 102 notifies the order management system 101 at an upper level via the predetermined API that the job error has occurred.
  • the image data 1503 out of the image data 1501 , 1502 , 1503 , and 1504 is improper.
  • the print management system 102 confirms image impropriety of the image data 1503 upon transferring job data of the image data 1501 and 1502 to the printer 103 , it cancels the print job and stops printing. That is, the print management system 102 cancels the print job of the image data 1501 and 1502 during printing, and does not transfer job data of the image data 1503 and 1504 to the printer 103 .
  • cancel processing is changed depending on which of book print or single sheet print is designated as the print form. This can increase the efficiency in reprinting.
  • the print management system 102 starts the processing upon receiving a print job of N pages from the order management system 101 , and executes the following processes for the respective pages which form the print job (steps S 1601 to S 1615 ).
  • the print management system 102 analyzes the page of interest in the print job, and converts the job (step S 1602 ).
  • the print management system 102 determines whether an error exists in the print ticket in print ticket analysis of the print job (step S 1603 ). If no error exists (NO in step S 1603 ), the print management system 102 transfers the page of interest to the printer 103 (step S 1614 ). The print management system 102 analyzes and converts all the pages which form the print job, and transfers them to the printer 103 unless an error occurs in the page of interest. Then, the processing sequence ends.
  • step S 1603 the print management system 102 determines whether the print job designates single sheet print (step S 1604 ). If the print job does not designate single sheet print (NO in step S 1604 ), the process advances to step S 1609 . If the print job designates single sheet print (YES in step S 1604 ), the print management system 102 determines whether the setting can continue printing (step S 1605 ). If the setting cannot continue printing (NO in step S 1605 ), the process advances to step S 1609 . Printing cannot continue when, for example, an error is detected on the obverse surface in single-sheet double-sided print. In this case, the print management system 102 determines that printing should not continue for the page of interest on which the error has detected, and subsequent pages.
  • step S 1605 If printing can continue (YES in step S 1605 ), the print management system 102 transfers a cancel command which designates the error page, and the cancel reason to the printer 103 to print the remaining pages except for the error page (step S 1606 ).
  • the following description is an example of adding the cancel reason to the cancel command which designates the error page when the error is detected in print ticket analysis of the third page:
  • the print management system 102 notifies the order management system 101 at an upper level of the error event (step S 1607 ).
  • the print management system 102 displays the cancel reason (“job error” or “data error” in this case) on the UI (step S 1608 ).
  • the process returns to step S 1602 , and the print management system 102 continues image processing for subsequent pages.
  • step S 1609 the print management system 102 determines whether an error has been detected in analysis of the first page. If an error has been detected in the print ticket in analysis of the first page (NO in step S 1609 ), the print management system 102 deletes the print job from the queue, and cancels issuing of the print job (step S 1611 ). The process then advances to step S 1612 .
  • step S 1609 If an error has been detected in the print ticket in analysis of the second or subsequent page (YES in step S 1609 ), the print job has already been issued to the printer 103 . Thus, the print management system 102 adds the cancel reason to a job cancel command for the print job, and issues the job cancel command to the printer 103 (step S 1610 ).
  • the print management system 102 notifies the order management system 101 at an upper level of the error event (step S 1612 ).
  • the print management system 102 displays the page number and cancel reason (“job error on the nth page” in this case) on the UI of the print management system 102 (step S 1613 ). Then, the processing sequence ends.
  • the printer 103 starts processing upon receiving a print job of N pages from the print management system 102 , and executes the following processes for the respective pages which form the print job (steps S 1701 to S 1712 ).
  • the printer 103 determines whether the page of interest is an error page designated in step S 1606 of FIG. 17 (step S 1702 ). If the page of interest is an error page (YES in step S 1702 ), the printer 103 advances to step S 1710 .
  • the printer 103 skips the page of interest, and displays the cancel reason (“job error on the nth page” in this case) on the UI of the printer 103 (step S 1710 ).
  • the process returns to step S 1702 to set the next page as the page of interest. If the page of interest is not an error page (NO in step S 1702 ), the printer 103 executes image processing for the page of interest (step S 1703 ).
  • the printer 103 determines whether an error has been detected in content data in image processing (step S 1704 ). If no error exists in the content data (NO in step S 1704 ), the printer 103 prints the page of interest (step S 1711 ). The printer 103 prints unless a content error occurs in each page of the print job. The printer 103 displays the completion of the print job on the UI, and ends the processing sequence.
  • the printer 103 determines whether the setting can continue printing (step S 1705 ). If the setting can continue printing without any problem (YES in step S 1705 ), the printer 103 notifies the print management system 102 at an upper level of an error event representing that the error has occurred in the target page (step S 1706 ). The printer 103 displays the cancel reason (“data error on the nth page” in this case) on the UI of the printer 103 (step S 1707 ). The process returns to step S 1702 , and the printer 103 continues image processing for subsequent pages.
  • step S 1705 If printing cannot continue (NO in step S 1705 ), the printer 103 deletes the received print job (step S 1708 ).
  • the printer 103 notifies the print management system 102 at an upper level of an error event representing that the data error has occurred (step S 1709 ).
  • the printer 103 displays the cancel reason (“data error on the nth page” in this case) on the UI of the printer 103 (step S 1710 ). Thereafter, the processing sequence ends.
  • the setting referred to when switching the criterion (determination processing) is the form setting (single sheet print/book print) of a print job.
  • the present invention is not limited to this setting, and the criterion may be switched by referring to another print setting.
  • Determination of whether the setting can continue printing may use another condition in accordance with matching of print settings.
  • the fourth embodiment will describe an example of adding an action to a cancel command to designate the operation of a printer 103 when a print management system 102 detects a job error during issuing of a print job to the printer 103 .
  • the overall arrangement of the system and the remaining common parts are the same as those in the first embodiment, and a description thereof will not be repeated.
  • the print management system 102 adds a cancel reason to a job cancel command, and transfers the job cancel command (step S 705 ).
  • an action instruction is added instead of a cancel reason.
  • the print management system 102 issues, as an action instruction, a charging stop instruction regarding the print job to the printer 103 .
  • This can prevent charging of an unexecuted print job.
  • the printer 103 may be turned off.
  • FIG. 4C exemplifies a cancel command to which the action of the charging stop instruction is added according to the fourth embodiment.
  • the operation of the printer 103 according to the fourth embodiment is almost the same as that in the flowchart of FIG. 11 described in the first embodiment.
  • the printer 103 displays a cancel reason (“job error” in this case) to the UI (step S 1006 ).
  • the printer 103 executes processing according to an action instruction contained in a cancel command.
  • an action instruction is added in place of a cancel reason.
  • the present invention is not limited to this, and both kinds of information may be added.
  • the printer 103 can execute an action corresponding to an error to stop, for example, charging of a print job in which a job error has occurred.
  • aspects of the present invention can also be realized by a computer of a system or apparatus (or devices such as a CPU or MPU) that reads out and executes a program recorded on a memory device to perform the functions of the above-described embodiment(s), and by a method, the steps of which are performed by a computer of a system or apparatus by, for example, reading out and executing a program recorded on a memory device to perform the functions of the above-described embodiment(s).
  • the program is provided to the computer for example via a network or from a recording medium of various types serving as the memory device (for example, computer-readable medium).

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Accessory Devices And Overall Control Thereof (AREA)
US13/649,406 2011-10-21 2012-10-11 Information processing apparatus, control method thereof, and computer-readable medium Expired - Fee Related US9235357B2 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2011-232124 2011-10-21
JP2011232124A JP5918964B2 (ja) 2011-10-21 2011-10-21 情報処理装置およびその制御方法、並びにプログラム

Publications (2)

Publication Number Publication Date
US20130100493A1 US20130100493A1 (en) 2013-04-25
US9235357B2 true US9235357B2 (en) 2016-01-12

Family

ID=48135757

Family Applications (1)

Application Number Title Priority Date Filing Date
US13/649,406 Expired - Fee Related US9235357B2 (en) 2011-10-21 2012-10-11 Information processing apparatus, control method thereof, and computer-readable medium

Country Status (2)

Country Link
US (1) US9235357B2 (es)
JP (1) JP5918964B2 (es)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013196023A (ja) * 2012-03-15 2013-09-30 Canon Inc 情報処理装置、印刷システム、及び、エラー通知方法
JP6180236B2 (ja) * 2013-08-23 2017-08-16 シャープ株式会社 画像形成装置
JP6459236B2 (ja) * 2014-06-19 2019-01-30 富士ゼロックス株式会社 画像形成装置
JP5968373B2 (ja) * 2014-07-24 2016-08-10 キヤノン株式会社 印刷装置、情報処理方法及びプログラム
JP6460905B2 (ja) * 2015-04-30 2019-01-30 キヤノン株式会社 通信装置、制御方法、プログラム
JP6659158B2 (ja) * 2016-03-03 2020-03-04 キヤノン株式会社 印刷制御装置及び方法、印刷システム及びその制御方法、プログラム
JP6672959B2 (ja) * 2016-03-31 2020-03-25 ブラザー工業株式会社 印刷システム、ドライバプログラム、及びプリンタ
JP6877963B2 (ja) * 2016-11-18 2021-05-26 キヤノン株式会社 画像形成装置、画像形成装置の制御方法、およびプログラム
JP7400243B2 (ja) * 2019-07-26 2023-12-19 富士フイルムビジネスイノベーション株式会社 情報処理装置及びプログラム

Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH03224778A (ja) 1990-01-31 1991-10-03 Hitachi Ltd 印刷システム
JPH1195957A (ja) 1997-09-18 1999-04-09 Canon Inc 印刷制御装置および印刷制御方法およびコンピュータが読み出し可能なプログラムを格納した記憶媒体
JPH11134146A (ja) 1997-10-31 1999-05-21 Hitachi Ltd 印字装置における異常印字検出方式
US20030151766A1 (en) * 2002-02-13 2003-08-14 James Clough Method and apparatus for authorizing printing
US20050078165A1 (en) * 2003-10-08 2005-04-14 Konica Minolta Business Technologies, Inc. Printing device, printing method, printing program and computer-readable recording medium on which the program is recorded
US20050174595A1 (en) * 2004-02-10 2005-08-11 First Data Corporation Systems and methods for print waste management and performance measurement
JP2006504182A (ja) 2002-10-28 2006-02-02 デブラブス アーベー ネットワーク内の共用資源を使用する方法および構成
US20060136871A1 (en) * 2004-12-20 2006-06-22 O'connor Tim Method and system for holistic project management
US20060262344A1 (en) * 2005-05-18 2006-11-23 Oki Data Corporation Image forming apparatus and image forming system
US20080055636A1 (en) * 2006-08-30 2008-03-06 Canon Kabushiki Kaisha Printing system, printing apparatus, and job control method
US20080239383A1 (en) * 2007-03-28 2008-10-02 Brother Kogyo Kabushiki Kaisha Data processor saving data indicating progress status of printing process retrievable by client
US20080259387A1 (en) * 2007-04-19 2008-10-23 Canon Kabushiki Kaisha Information processing apparatus, information processing method, and storage medium
US20090086267A1 (en) * 2007-09-28 2009-04-02 Canon Kabushiki Kaisha Printing apparatus, method for controlling print job, and computer program
US20120188594A1 (en) * 2011-01-25 2012-07-26 Jessen Robert F Print Job Management Mechanism
US20120212771A1 (en) * 2011-02-23 2012-08-23 Joan Stagaman Goddard Resolution of conflicts between print jobs and printers in a print shop environment

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH03224778A (ja) 1990-01-31 1991-10-03 Hitachi Ltd 印刷システム
JPH1195957A (ja) 1997-09-18 1999-04-09 Canon Inc 印刷制御装置および印刷制御方法およびコンピュータが読み出し可能なプログラムを格納した記憶媒体
JPH11134146A (ja) 1997-10-31 1999-05-21 Hitachi Ltd 印字装置における異常印字検出方式
US20030151766A1 (en) * 2002-02-13 2003-08-14 James Clough Method and apparatus for authorizing printing
JP2006504182A (ja) 2002-10-28 2006-02-02 デブラブス アーベー ネットワーク内の共用資源を使用する方法および構成
US20050078165A1 (en) * 2003-10-08 2005-04-14 Konica Minolta Business Technologies, Inc. Printing device, printing method, printing program and computer-readable recording medium on which the program is recorded
US20050174595A1 (en) * 2004-02-10 2005-08-11 First Data Corporation Systems and methods for print waste management and performance measurement
US20060136871A1 (en) * 2004-12-20 2006-06-22 O'connor Tim Method and system for holistic project management
US20060262344A1 (en) * 2005-05-18 2006-11-23 Oki Data Corporation Image forming apparatus and image forming system
US20080055636A1 (en) * 2006-08-30 2008-03-06 Canon Kabushiki Kaisha Printing system, printing apparatus, and job control method
US20080239383A1 (en) * 2007-03-28 2008-10-02 Brother Kogyo Kabushiki Kaisha Data processor saving data indicating progress status of printing process retrievable by client
US20080259387A1 (en) * 2007-04-19 2008-10-23 Canon Kabushiki Kaisha Information processing apparatus, information processing method, and storage medium
US20090086267A1 (en) * 2007-09-28 2009-04-02 Canon Kabushiki Kaisha Printing apparatus, method for controlling print job, and computer program
US20120188594A1 (en) * 2011-01-25 2012-07-26 Jessen Robert F Print Job Management Mechanism
US20120212771A1 (en) * 2011-02-23 2012-08-23 Joan Stagaman Goddard Resolution of conflicts between print jobs and printers in a print shop environment

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Japanese Office Action issued in corresponding application No. 2011232124 on Oct. 5, 2015.

Also Published As

Publication number Publication date
JP5918964B2 (ja) 2016-05-18
JP2013089191A (ja) 2013-05-13
US20130100493A1 (en) 2013-04-25

Similar Documents

Publication Publication Date Title
US9235357B2 (en) Information processing apparatus, control method thereof, and computer-readable medium
US10546219B2 (en) Printing system, printing apparatus, printing control apparatus, and control method of printing system
US20090051947A1 (en) Printing control apparatus and method
US20120224222A1 (en) Computer Readable Information Recording Medium Storing Print Job Editing Program, Print Job Editing Apparatus, Print Job Editing Method And Printing System
US8913278B2 (en) Image forming apparatus, control method thereof, and storage medium
US8451482B2 (en) Printing system and printing method
US20200089440A1 (en) Server system that improves availability of a plurality of printers, print controller, information processing apparatus, and print service system
US20160266855A1 (en) Information processing apparatus, information processing method, and recording medium
US11055586B2 (en) Printing device that receives print data and performs printing, control method of printing device, and program
US20160224283A1 (en) Print management device, print management system, print management method and computer readable medium
US9875073B2 (en) Printing apparatus and control method therefor
US9317225B2 (en) Method and apparatus for dynamically configuring a filter pipeline for a print driver
JP2007156903A (ja) 印刷システム及びその制御方法、コンピュータプログラム、記憶媒体
US10248364B2 (en) Method and system for print device problem capture
JPH11165455A (ja) コンピュータによるプリント制御方法およびプリント制御プログラムを記録したコンピュータ読み取り可能な記録媒体、ならびにプリント制御装置
US9047552B2 (en) Forming system and image forming apparatus that generate image log data to server
JP6929715B2 (ja) 画像形成装置
US8104756B2 (en) Method and apparatus for selecting media trays for hole punching in an image production device
US9310746B2 (en) Printing apparatus, control method for printing apparatus, and storage medium
US20240069824A1 (en) Information processing system, non-transitory computer readable medium, and information processing method
US8659780B2 (en) Print management for plurality of print requests in image forming apparatus
US8773711B2 (en) Data processing apparatus, data processing method, and storage medium for controlling display setting screen based on selected printer driver
US9584684B2 (en) Image forming apparatus, method for controlling the same, and storage medium
US8619286B2 (en) System and method of avoiding conflicting printer job language processing
JP5764924B2 (ja) 情報処理装置、情報処理装置の制御方法、プログラム、記憶媒体

Legal Events

Date Code Title Description
AS Assignment

Owner name: CANON KABUSHIKI KAISHA, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:OTSUKA, KOICHIRO;UOTANI, KENICHIRO;KOIKE, ATSUKO;SIGNING DATES FROM 20120927 TO 20120928;REEL/FRAME:029708/0428

ZAAA Notice of allowance and fees due

Free format text: ORIGINAL CODE: NOA

ZAAB Notice of allowance mailed

Free format text: ORIGINAL CODE: MN/=.

ZAAA Notice of allowance and fees due

Free format text: ORIGINAL CODE: NOA

ZAAA Notice of allowance and fees due

Free format text: ORIGINAL CODE: NOA

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20240112