JP2023057089A - Printing device, method for controlling printing device, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce user's time and effort for deleting a print job on a printing device that can perform printing by receiving print data from a print service using IPP (Internet Printing Protocol).

SOLUTION: A printing device displays a list of print jobs held on a print service, requests the print service for transmitting print data corresponding to a print job selected from the list when receiving an instruction of canceling the selected print job from a user, and does not print the print data received from the print service.

SELECTED DRAWING: Figure 12

COPYRIGHT: (C)2023,JPO&INPIT

Description

The present invention relates to a printing apparatus, a printing apparatus control method, and a program.

In recent years, in addition to a method in which a client sends image data directly to a printing device, there is a method in which a printing device prints by downloading print data from a printing service provided by a print server on a network such as the cloud. Widespread. Specifically, a client terminal such as a mobile device transmits print data to a print service, the print service converts the print data into print data in the format of the printing device, and the printing device downloads the converted print data. Printing is done by For example, in FIG. 1, 102 is a client terminal, 101 is a print service, and 100 is a printer. In such a configuration, the print service can be either in the cloud or on-premises.

In the case of pull printing with the configuration shown in FIG. 1, for example, a user comes in front of a printing device, logs in to the printing device using a user ID and password, and checks whether the print service has a job for that user. inquire. After the user's job list is displayed on the operation panel of the printing device based on the response from the printing service, the user selects the job to be printed and selects the "Print" button, and the printing device receives the corresponding job from the printing service. There is a way to get the job and print it.

On the other hand, when the user wants to cancel printing, the user selects the job to be deleted from the user's job list and instructs the user to cancel the job. Then, the printing device sends a cancel command to the print service, and the print service deletes the corresponding job. There is a method (Patent Document 1).

As an example of a printing system having such a network configuration, PWG5100.18 proposes a configuration called IPP-Infra using IPP (Internet Printing Protocol) as a printing protocol. IPP is a printing protocol for exchanging print data between a remote computer and a printing apparatus using the HTTP protocol used on the Internet.
(https://ftp.pwg.org/pub/pwg/candidates/cs-ippinfra10-20150619-5100.18.pdf)
IPP-Infra defines Client for transmitting image data, Infrastructure for holding image data, Proxy for acquiring image data, and Output Device for printing image data. Here, the Proxy and Output Device may be the same terminal. If the configuration of IPP-Infra is applied to FIG. 1, Infrastructure corresponds to 101 printing services, Proxy/Output Device to 100 printing devices, and Client to 102 client terminals.

JP 2017-170895 A

However, in the configuration of IPP-Infra, when a user wants to cancel (delete) a print job, IPP-Infra has a limitation that the printing device cannot send a job cancellation command to the print service.

FIG. 3 is a diagram showing operations and entities that should correspond to them, defined in the IPP-Infra specifications. MUST means "must be implemented", MUST NOT means "must not be implemented", and MAY means "whether or not it is implemented". For example, an operation "Create-Job" means an operation to generate a print job, and means that this operation must be implemented by Client and Infrastructure, but not by Proxy.

According to this, it is stipulated that a Proxy corresponding to a printing device must not execute a Cancel-Job operation for canceling a job (MUST NOT).

Therefore, even if the user comes to the printer and wants to cancel an arbitrary job, he or she cannot cancel the job. I have no choice but to get it. Therefore, there is a problem that it takes time for the user to cancel the job.

SUMMARY OF THE INVENTION It is an object of the present invention to reduce the user's trouble in deleting a print job in a printing apparatus that can receive print data from a print service using IPP (Internet Printing Protocol) and perform printing. .

A printing device according to an embodiment of the present invention is a printing device that can receive a print job from a print service using IPP (Internet Printing Protocol) and execute printing, and is held in the print service. display control means for displaying a list of print jobs displayed; acceptance means for accepting a print instruction for a print job selected from the displayed list; and printing selected as a target of the print instruction when the print instruction is accepted a print control means for requesting a job from the print service using IPP and causing the printing means to print the print job, and receiving a cancel instruction for the print job selected from the displayed list. and the print control means uses IPP to request the print job selected as the target of the cancel instruction from the print service, but the print job selected as the target of the cancel instruction is not printed. do.

According to the present invention, in a printing apparatus that can receive print data from a print service using IPP (Internet Printing Protocol) and perform printing, it is possible to reduce the user's trouble in deleting a print job. .

1 is a diagram showing the configuration of a network in this embodiment; FIG. 2 is a hardware configuration diagram of a printing apparatus according to the embodiment; FIG. An example of an operation defined by PWG FIG. 10 is a sequence diagram for inputting print data in the first embodiment; 4 is a sequence diagram of job printing in the first embodiment; FIG. 4 is a sequence diagram of job cancellation in the first embodiment; FIG. FIG. 10 is a sequence diagram of a cloud administrator canceling a job according to the first embodiment; 8 is a sequence diagram of job cancellation from the client terminal in the first embodiment; FIG. FIG. 10 is a sequence diagram for canceling a job during job printing according to the first embodiment; 4 is a flowchart for displaying a job list according to the first embodiment; 6 is a flowchart for job printing in the first embodiment; 4 is a flowchart for canceling a job in the first embodiment; 4 is an example of a screen of the operation panel of the printing apparatus according to the first embodiment; 4 is an example of a screen of a cloud operation panel in the first embodiment; FIG. 10 is a flowchart of job cancellation in the second embodiment; FIG. FIG. 11 is a sequence diagram of job cancellation in the second embodiment; FIG. 2 is a software configuration diagram of the printing apparatus according to the embodiment; FIG. 11 is a sequence diagram of job cancellation in the third embodiment; FIG. 12 is a sequence diagram of print processing in the fourth embodiment; FIG. 14 is a sequence diagram of job cancellation in the fourth embodiment;

BEST MODE FOR CARRYING OUT THE INVENTION The best mode for carrying out the present invention will be described below with reference to the drawings. It should be noted that the following embodiments do not limit the invention according to the claims, and not all combinations of features described in the embodiments are essential to the solution of the invention.

(Embodiment 1)
In this embodiment, IPP (Internet Printing Protocol)-Infra is used to obtain print data from a print service on the cloud and print it.

<Hardware configuration>
FIG. 1 shows an example of a cloud print system according to this embodiment. 100 is a printer. A print service 101 is provided on the Internet. A client terminal 102 is a user's operation terminal. The printing device 100 is registered with the printing service 101 in advance by the owner of the printing device 100 . A user selects the printing apparatus 100 registered with the print service 101 from the client terminal 102 and transmits print data to the print service 101 via an access point or a mobile base station. The printing apparatus 100 receives print data transmitted by the user via the print service 101 and performs printing. Although not shown, the client terminal operated by the user can use the print service 101 not only from the client terminal 102 but also from a plurality of client terminals such as general-purpose personal computers and smart phones. The printing device 100 and the client terminal 102 are connected to the printing service 101 via the Internet. As described above, the IPP-Infra configuration is applied to the printing system in FIG. 1, where the printing apparatus 100 corresponds to Proxy and Output Device, the printing service 101 corresponds to Infrastructure, and the client terminal corresponds to Client.

Next, the configuration of the printing apparatus 100 will be described with reference to FIG.

The CPU 201 reads control programs stored in the ROM 203 and executes various processes for controlling the operation of the printing apparatus 100 . The ROM 203 stores control programs. A RAM 202 is used as a main memory of the CPU 201 and a temporary storage area such as a work area. The HDD 204 stores various data such as print data and scanned images.

Note that in the case of the printing apparatus 100, one CPU 201 is assumed to execute each process shown in a flow chart to be described later, but other modes may also be used. For example, a plurality of CPUs may work together to execute each process shown in a flowchart to be described later.

In the printing apparatus 100 , the printer 206 executes print processing based on print data received from an external device, a scanned image generated by the scanner 213 , and the like. A scanner 213 reads a document and generates a scanned image. A scanned image generated by the scanner 213 is printed by the printer 206 or stored in the HDD 204 .

An operation unit 209 includes a liquid crystal display unit having a touch panel function and a keyboard, and displays various screens to be described later. A user can input instructions and information to the printing apparatus 100 via the operation unit 209 .

The wireless LAN chip 211 realizes communication with an external device by wireless LAN communication, and has connection types such as wireless infrastructure and wireless direct as wireless LAN connection types.

The wired LAN interface 214 communicates with an external device such as a PC terminal via a wired LAN chip 215 via a wired LAN.

<Software configuration>
FIG. 17 is a simplified diagram showing an example of the software configuration of the printing apparatus 100 according to the present embodiment, which is realized by developing the program stored in the ROM 203 in the RAM 202 and executing the program by the CPU 201. FIG. A UI processing unit 1701 generates an image for displaying a job list display screen and a job history screen as shown in FIG. The UI processing unit 1701 also notifies the job processing unit 1703 and the network communication processing unit 1702 of an event in which the user presses a “print” button or a “cancel” button. Furthermore, the UI processing unit 1701 receives a notification about a change in job status from the job processing unit 1703, and reflects it on the job list display screen and the job history screen. A network communication processing unit 1702 controls network communication such as IPP with an external terminal such as a server that provides the print service 101 through a wireless LAN or a wired LAN. For example, it acquires a print job from a print service and transfers the received image data to the job processing unit 1703 . A job processing unit 1703 interprets received image data and executes print processing. Also, the UI processing unit 1701 is notified of job completion and error events.

Although not shown, the client terminal 102 is equipped with a web browser that transmits an HTML request and displays a screen based on the HTML received as a response. The print service 101 also has a function for registering the printing apparatus 100, a function for converting print data designated for printing from the client terminal 102 into a print job, and a print job selected from among the plurality of registered printing apparatuses 100. It has the ability to provide print jobs to the device 100 . Further, the print service 101 has a web server function, and provides a user interface for referring to and setting job statuses saved in the print service 101 and load statuses of the print service via a web browser. These functions are also functions provided by a software configuration, and the software configuration is realized by expanding a program stored in ROM into RAM and executing the program by the CPU.

<Job Submission Procedure>
FIG. 4 shows a sequence diagram for inputting print data from the client terminal 102 to the print service 101. As shown in FIG. A web browser corresponding to the print service 101 is installed in the client terminal 102, and a printing device registered with the print service 101 can be selected from the print menu of the web browser. Then, the user selects image data to be printed from the client terminal 102 (401), selects "print" from the property screen of the image data (402), and the print data is transmitted from the client terminal to the print service 101. (403). In IPP, print data is transmitted by Print-Job operation or Create-Job operation. User information for identifying the user operating the client terminal 102 is included in Requesting-user-name of this operation. This allows the print service 101 to identify which user is requesting printing from the client terminal 102 . The print service that has received the print data creates a print job, saves it in a storage area within the print service, and holds the processing status of the job as a Pending state (404).

FIG. 14 is an example of a screen displaying the processing status of the print service 101. As shown in FIG. As described above, a web server is installed in the print service 101, and the administrator logs in from the web server to refer to and set the job status and load status of the print service saved in the print service 101 via a browser. can do. When a print job is received from the client terminal 102, the state (A) in which no print job exists is changed to the state (B) in which two print jobs are received from the client. At this time, the time when the job was received is shown in the Date area, the job status is shown in the Status area, Requesting-user-name of the IPP attribute included in the job is shown in the Owner area, and Job-name of the IPP attribute is shown in the JobName area.

<Job list display procedure>
Next, a process of displaying a print job list saved in the print service 101 by the user operating the printing apparatus 100 will be described with reference to the flowchart of FIG. First, the user logs into the printing apparatus 100 in S1001. For example, as shown in FIG. 13A, login is performed by entering a user ID and password from the operation unit 209 of the printing apparatus 100, or by touching the printing apparatus 100 with a card in which the user ID and password are stored. There is a way. When the login is successful, operation icons permitted for the user are displayed on the operation unit 209 as shown in FIG. 13B, and the user can select any icon to perform a desired operation. The cloud print of this embodiment can be operated by selecting the "CloudPRINT" icon in FIG. 13B. When "CloudPRINT" is pressed, the job list display screen shown in FIG. 13C is displayed. Here, a list of print jobs of the logged-in user is displayed.

The CPU 201 of the printing apparatus 100 internally transmits a job list acquisition request to the print service 101 in S1002. The job list acquisition request is realized by the IPP Get-Jobs operation and Get-Documents operation. In this operation, the My-Jobs attribute is set to True, and the user information of the logged-in user is stored in the Requesting-user-name and Requesting-uri attributes. Only print jobs whose attribute values match the user attribute values of print jobs stored in the print service 101 are transmitted from the print service 101 to the printing apparatus 100 .

If the print job list can be acquired in S1003, the CPU 201 displays the acquired job list on the operation unit 209 as shown in FIG. 13C in S1004. Here, a job list of the user “Alice” who is logged in to the printing apparatus 100 is displayed. Then, in S1005, the CPU 201 enters a state of waiting for user's operation. When the user selects an arbitrary job and selects "Print", the process proceeds to the flowchart of FIG. 11, and when the user selects "Cancel", the process proceeds to the flowchart of FIG. In S1003, if the print job corresponding to the logged-in user of the printing apparatus 100 is not registered in the print service 101 and the print job list is not sent, or if the job list screen in FIG. Back" is selected, the process ends.

<Print procedure>
FIG. 5 shows a sequence diagram from when the printing apparatus 100 acquires a job from the printing service 101 to printing.

When the user logs into the printing apparatus 100 (500) and selects "CloudPRINT" from the menu screen shown in FIG. 13B, a job list acquisition request is transmitted to the printing service 101 (502). As a response to the received job list acquisition request, the print service 101 transmits a list of print jobs linked to the logged-in user of the printing apparatus 100 to the printing apparatus 100 (503). The printing apparatus 100 displays the job list screen shown in FIG. 13C based on the received information (504). As will be described later, the job list screen of FIG. 13C is a screen that can receive a print instruction and a cancel instruction of a print job from the user. The processes up to this point are realized by performing the processes of S1001 to S1004 in FIG. 10 described above.

When "Print" is pressed (505) while a job to be printed is selected from the job list screen of FIG. (506). The screen at this time is FIG. 13G, and the status of only the print job whose JobName is "AA.pdf" among the two print jobs has changed from "pending" to "processing".

Next, the printing apparatus 100 transmits a job status update notification to the print service 101 so that JobStatus=Processing (507). This operation is implemented by sending an Update-Job-Status operation. The print service 101 that receives this operation changes the status of the job to "Processing" as shown in FIG. 14C (508).

Subsequently, the printing apparatus 100 transmits a job acquisition request to the print service 101 to acquire the print job selected by the user for printing (509). In IPP, a job acquisition request is made using operations such as Fetch-Job, Acknowledge-Job, Fetteh-Document, and Acknowledge-Document.

The print service 101 that has received the job acquisition request transmits job data to the printing apparatus 100 (510), and the printing apparatus 100 starts print processing based on the received print data (511). When the print processing is normally completed, the printing apparatus 100 changes the status of the job on the job list display screen to "Completed" (512) as shown in FIG. 13(H). Also, the time when the print processing is completed, the result, the user name, and the job name are saved as a job history, and the job history screen is updated as shown in FIG. 13I (513).

Finally, the printing device 100 sends an Update-Job-Status operation to the printing service 101 so that JobStatus=Completed (514). The print service 101 that receives this operation changes the status to "Completed" as shown in FIG. 14D (515).

Through the above processing, the print data transmitted from the client terminal 102 to the print service 101 can be acquired by the printing apparatus 100 and printed.

<Job cancellation procedure proposed by the present invention>
FIG. 6 shows a sequence diagram for canceling (deleting) a print job registered in the print service 101 without starting printing on the printing apparatus 100 . Since 601 to 604 in FIG. 6 are the same as 501 to 504 in FIG. 5, description thereof is omitted.

When "Cancel" is pressed (605) with at least one job selected from the job list screen of FIG. (606) is changed to the (canceling) state. The screen at this time is FIG. 13D, and the status of only the print job whose JobName is "AA.pdf" among the two print jobs has changed from "pending" to "Cancelling".

Next, the printing apparatus 100 transmits an Update-Job-Status operation to the print service 101 so that the JobStatus becomes Processing (607). The print service 101 that receives this operation changes the status of the job to "Processing" as shown in FIG. 14C (608).

Subsequently, the printing apparatus 100 transmits a job acquisition request to the print service 101 in order to acquire print data corresponding to the print job selected to be canceled (609). In IPP, a job acquisition request is made using operations such as Fetch-Job, Acknowledge-Job, Fetteh-Document, and Acknowledge-Document.

The print service 101 that has received the job acquisition request transmits job data to the printing apparatus 100 (610). The printing apparatus 100 reads and discards the received print data in the network layer without executing print processing based on the received print data (611). Internally, the image data received by the network communication processing unit 1702 is discarded, and the image data is not transferred to the job processing unit 1703 . For printing, the corresponding job is deleted from the job status screen as shown in FIG. 13(E). Also, at this time, as shown in FIG. 13F, no trace of the print processing of the job remains in the job history.

Finally, the printing apparatus 100 sends an Update-Job-Status operation to the print service 101 so that the JobStatus becomes Canceled (cancellation completed) (612). The print service 101 that receives this operation changes the status of the job to "Cancelled" as shown in FIG. 14E (613).

As described above, when cancel is selected before execution of printing in the printing apparatus 100, the corresponding job is acquired from the print service 101 and discarded internally, thereby pseudo-cancelling the job on the print service 101. can be done. Therefore, even a protocol such as IPP-Infra that prohibits the Cancel-Job operation in the printing apparatus can be canceled by the same operation procedure as the protocol that permits the cancel operation.

<Other Job Cancellation Procedures>
There are other job cancellation procedure methods than those proposed by the present invention. For example, as shown in FIG. 7, there is a method in which an administrator of the print service 101 accesses the print service 101, directly designates a job saved in the print service 101, and deletes the job. In this case, any user with administrator authority can operate.

Specifically, the administrator logs in to the web server of the print service 101 using a web browser such as a PC (701), and displays a list of jobs (702). The screen at this time is shown in FIG. Then, when a job to be canceled is selected from the job list displayed as shown in FIG. 14B and "Cancel" is pressed (703), cancellation processing is performed on the print service 101 (704). Then, the print service 101 changes the status of the job to "Cancelled" as shown in FIG. 14F (705).

In addition, there is another method of canceling a job from the client terminal 102 as shown in FIG. Specifically, from the client terminal 102 operated by the user who submitted the job, the job status saved in the print service 101 is confirmed by a spooler or the like (801, 802, 803). Then, the user selects a job to be canceled and gives a cancellation instruction (804), and the client terminal 102 transmits a Cancel-Jobs operation to the print service 101 (805). The client terminal 102 changes the status of the corresponding job to "Cancelling" (806), and the print service 101 performs cancellation processing (807). When the client terminal 102 receives the notification of cancellation completion from the print service 101 (808), it changes the status of the corresponding job to "Cancelled". The print service 101 also changes the status of the job to "Cancelled" when the cancel process is completed. As described above, the IPP-Infra regulations permit a cancel operation from the client, so this operation is possible. Also, instead of the Cancel-Jobs operation, a cancel-type operation such as Cancel-My-Jobs or Cancel-Job may be used. The print service 101 that has received the cancel operation changes the status of the job to "Cancelled" as shown in FIG. 14F.

<Procedure for canceling a job after starting print processing>
6 to 8 illustrate examples of canceling a print job saved in the print service 101 without starting printing. FIG. 9 shows a sequence in which printing by the printing apparatus 100 is canceled (stopped) during the printing process after starting printing. Note that processing 901 to 911 up to the start of printing is the same as processing 501 to 511 in FIG. 5, so description thereof will be omitted.

After starting print processing (911) in the printing apparatus 100, the user selects "Cancel" from the operation unit 209 for the job being printed as shown in FIG. 13G (912). The printing apparatus 100 changes the status of the job to "Cancelling" (913) and performs cancellation processing (914). Internally, the job processing unit 1703 cancels the image data transferred from the network communication processing unit 1702 to the job processing unit 1703 . When the cancellation process is completed, the printing apparatus 100 changes the status of the job to "Cancelled" as shown in FIG. 13J (915). Also, the time when the cancellation process is completed, the result, the user name and the job name are recorded as a job history, and the job history screen is updated as shown in FIG. 13K (916).

Finally, the printing apparatus 100 sends an Update-Job-Status operation to the print service 101 so that JobStatus=Cancelled (917). The print service 101 that has received this operation changes the status to "Cancelled" as shown in FIG. 14E (918).

In the case of this operation, some sheets may be printed and ejected before canceling. In addition, there are problems such as the cancellation history remaining in the job history and the need to cancel multiple jobs at the same time. have a nature.

Therefore, in the present invention, by adopting the method shown in FIG. 6, the job on the print service 101 can be canceled from the printing apparatus 100 without causing the above problem.

<Flow of Print Job Execution in Printing Apparatus 100>
A flowchart of the printing apparatus 100 when executing a print job selected by the user from the job list screen shown in FIG. 13C will be described with reference to FIG.

In S1101, the CPU 201 that has detected that "Print" has been selected from the job list screen changes the status of the corresponding job on the job list screen to "Processing" (see FIG. 13G). In step S1102, the CPU 201 transmits an Update-Job-Status operation to the print service 101 so that JobStatus=Processing.

In step S<b>1103 , the CPU 201 transmits a job acquisition request to the print service 101 . In IPP, a job acquisition request is made using operations such as Fetch-Job, Acknowledge-Job, Fetteh-Document, and Acknowledge-Document. In S1104, if job acquisition fails due to line instability or disconnection, the CPU 201 resends the job acquisition request. Although not shown, if the job acquisition request is sent a predetermined number of times and the job acquisition is not successful, the processing of this flowchart ends with an error.

If the job acquisition is successful in S1104, the CPU 201 starts print processing in S1105. Internally, image data is transferred from the network communication processing unit 1702 to the job processing unit 1703, and print processing is started in the job processing unit 1703. FIG.

If the print processing is normally completed in S1106, in S1107 the CPU 201 changes the status of the job on the job list screen to "Completed" as shown in FIG. 13H. In step S1108, the CPU 201 saves the print processing completion time, result, user name, and job name as a log. In step S1109, the CPU 201 transmits an Update-Job-Status operation to the print service 101 so that JobStatus=Completed.

In S1106, when the CPU 201 detects that the user has selected "Cancel" from the operation unit 209 for the job being printed on the screen of FIG. 13G, the CPU 201 executes cancellation processing of the job (S1114). . Internally, the job processing unit 1703 cancels the image data transferred from the network communication processing unit 1702 to the job processing unit 1703 . In S1115, the CPU 201 changes the status of the job to "Cancelled" as shown in FIG. 13J. Further, in S1116, the CPU 201 records the time when the cancel process was completed, the result, the user name, and the job name as a log in the job history. In step S1117, the CPU 201 transmits an Update-Job-Status operation to the print service 101 so that the JobStatus becomes Canceled.

Also, in S1106, if a drawing error or the like occurs during print processing and the print processing ends abnormally, the CPU 201 performs error processing in S1110. In S1111, the CPU 201 changes the status of the job to "Aborted" as shown in FIG. 13L. In step S<b>1112 , the CPU 201 records the time when the cancellation process was completed, the result, the user name, and the job name as a log in the job history. In step S1113, the CPU 201 transmits an Update-Job-Status operation to the print service 101 so that the JobStatus becomes Canceled. In this case, both the print service 101 side and the printing apparatus 100 side log the error as an error in the history.

<Print Job Cancellation Flow in Printing Apparatus 100>
A flowchart of the printing apparatus 100 when canceling a print job selected by the user from the job list screen shown in FIG. 13C will be described with reference to FIG.

First, in step S1201, the CPU 201 that has detected that "Cancel" has been selected from the job list screen changes the status of the corresponding job on the job list screen to "Cancelling" (see FIG. 13D). Note that when selecting a job to be canceled from the job status list, one job may be selected, or a plurality of jobs may be selected at the same time.

Next, in step S1202, the CPU 201 transmits an Update-Job-Status operation to the print service 101 so that the JobStatus becomes Processing. Next, in step S<b>1203 , the CPU 201 transmits a job acquisition request for the job to be canceled to the print service 101 . In IPP, a job acquisition request is made using operations such as Fetch-Job, Acknowledge-Job, Fetteh-Document, and Acknowledge-Document. In S1204, if image data transfer fails due to line instability or disconnection, the CPU 201 retransmits the job acquisition request. Although not shown, if the job acquisition request is sent a predetermined number of times and the job acquisition is not successful, the processing of this flowchart ends with an error.

If the job acquisition is successful in S1204, the CPU 201 does not print the received image data in S1205, but discards the received image data in the network layer. Internally, the image data received by the network communication processing unit 1702 is deleted. In other words, image data is not transferred from the network communication processing unit 1702 to the job processing unit 1703 . Then, in S1206, the CPU 201 deletes the job from the job list screen as shown in FIG. 13E. Also, at this time, as shown in FIG. 13F, no trace of the print processing of the job remains in the job history.

Finally, in S1207, the CPU 201 transmits an Update-Job-Status operation to the print service 101 so that JobStatus becomes Canceled.

If the job does not disappear on the print service 101 side even if Canceled is sent in the Update-Job-Status operation, Aborted may be sent. It may be possible to switch the transmission status depending on which status the job on the print service 101 side is deleted.

As described above, when cancel is selected before printing is started in the printing apparatus 100, the corresponding print data is acquired from the print service 101, and the network communication processing unit 1702 discards the print data. You can cancel the above jobs. Therefore, even with a protocol such as IPP-Infra that prohibits the Cancel-Job operation from the printing apparatus, it is possible to delete the job on the print service 101 from the printing apparatus before starting print processing.

(Embodiment 2)
Next, a second embodiment will be described. This embodiment will be described on the premise that the print service 101 has a function of canceling the job when the print service 101 receives a canceled job status. FIG. 15 is a flow chart of the printing apparatus 100 in this embodiment. Also, FIG. 16 shows a sequence diagram in this embodiment. The processing from 1601 to 1604 is the same processing as 501 to 504 in FIG. 5, 610 to 604 in FIG. 6, and 901 to 904 in FIG. 9, so the description is omitted.

"Cancel" is pressed while a job is selected from the job list screen (1605), and the CPU 201 detects this and changes the status of the corresponding job on the job list screen to "Cancelling" (S1501, 1606). After a predetermined period of time, the CPU 201 changes the status of the corresponding job on the job list screen to "Cancelled" (S1502, 1607).

Next, in S1503, the CPU 201 transmits an Update-Job-Status operation to the print service 101 so that JobStatus=Cancelled (1608). Upon receiving this operation, the print service 101 determines that this job has been canceled by the printing apparatus 100, and cancels and deletes the job from the storage area of the print service as well (1609). The print service 101 then changes the status of the job to "Cancelled".

According to this embodiment, even if the printing apparatus 100 does not acquire a job from the printing service 101 as in the first embodiment, only the job status needs to be notified, thus reducing the processing load on the printing apparatus side.

(Embodiment 3)
A third embodiment will now be described with reference to FIG. In the first embodiment, when a cancel instruction is received from the user before printing starts, the image data received by the network communication processing unit 1702 is discarded internally, and the image data is not transferred to the job processing unit 1703 . In this embodiment, an example will be described in which the network communication processing unit 1702 does not discard the received image data, and after transferring the image data to the job processing unit 1703, the job processing unit 1703 cancels the image data.

FIG. 18 shows a sequence diagram in this embodiment. Since the processing of 1801 to 1810 is the same as the processing of 601 to 610 in FIG. 6, the explanation is omitted.

The CPU 201 that has successfully acquired image data from the print service 101 in 1810 starts print processing, but immediately executes cancellation processing. Internally, image data is transferred from the network communication processing unit 1702 to the job processing unit 1703, and the job processing unit 1703 executes print processing and cancellation processing.

The printing apparatus 100 starts print processing based on the received image data (1811), and changes the status of the job on the job list screen to "Cancelling" (1812). Further, the printing apparatus 100 performs cancellation processing for the job (1813). When the cancellation process is completed, the status of the job in question on the job list screen is changed to "Cancelled" (1814), and the job is logged as a canceled job and saved in the job history (1815). Finally, the printing apparatus 100 sends an Update-Job-Status operation to the print service 101 so that the JobStatus becomes Canceled (1816). The print service 101 that receives this operation changes the status of the job to "Cancelled" (1817).

According to the present embodiment, as in the first embodiment, even with a protocol such as IPP-Infra that prohibits job cancellation from the printing apparatus, before starting print processing, the printing apparatus sends a request to the print service 101. can be deleted.

<Job cancellation for push printing>
In the above-described first to third embodiments, "pull printing", in which print data is obtained from the print service 101 and printed when a user issues a print instruction in the printing apparatus 100, has been described as an example. Job cancellation in “push printing” in which print data is automatically acquired from the print service 101 and printed without the user giving a print instruction in the printing apparatus 100 will be described here. In the case of push printing, when the user inputs print data from the client terminal 102 to the print service 101, the printing apparatus 100 is immediately notified of the job input, and the printing process is executed. Therefore, unlike pull printing, immediate printing is possible.

FIG. 19 shows a sequence diagram of push printing. Processing 1901 to 1903 until print data is input from the client terminal 102 to the print service 101 is the same as 401 to 403 in FIG.

When the print service 101 receives the print data from the client terminal 102, it generates a print job and notifies the printing apparatus 100 that the print job has been submitted (1904). Since the print service 101 sends a push notification to the printing apparatus 100 in the office or home, it is assumed that a protocol such as constant connection or long polling for continuously establishing a session is used. The printing apparatus 100 that has received the notification of the print job changes the status of the corresponding job on the job list display screen to "Processing" (1905).

Next, the printing apparatus 100 transmits a job status update notification to the print service 101 so that JobStatus=Processing (1906). This operation is implemented by sending an Update-Job-Status operation. The print service 101 that receives this operation changes the status of the job to "Processing" (1907).

Subsequently, the printing apparatus 100 transmits a job acquisition request to the print service 101 to acquire the input print job for printing (1908). In IPP, a job acquisition request is made using operations such as Fetch-Job, Acknowledge-Job, Fetteh-Document, and Acknowledge-Document.

The print service 101 that has received the job acquisition request transmits job data to the printing apparatus 100 (1909), and the printing apparatus 100 starts print processing based on the received print data (1910). When the print processing is normally completed, the printing apparatus 100 changes the status of the job on the job list display screen to "Completed" (1911). Also, the time when the print processing is completed, the result, the user name, and the job name are saved as a job history (1912).

Finally, the printing apparatus 100 sends an Update-Job-Status operation to the print service 101 so that JobStatus=Completed (1913). The print service 101 that receives this operation changes the status of the job to "Completed" (1914).

The above processing enables push printing using the IPP-Infra configuration.

Next, FIG. 20 shows a sequence for canceling a job in push printing. In the case of push printing, since printing is started without a user giving a print instruction to the printing apparatus 100, it cannot be canceled before printing is started. Therefore, as in the processing of FIG. 9, the printing is canceled after the start of printing. Processes 2001 to 2010 up to the start of printing are the same as 1901 to 1910 in FIG.

After starting print processing (2010) in the printing apparatus 100, the user selects "Cancel" from the operation unit 209 for the job being printed (2011). The printing apparatus 100 changes the status of the job to "Cancelling" (2012) and performs cancellation processing (2013). Internally, the job processing unit 1703 cancels the image data transferred from the network communication processing unit 1702 to the job processing unit 1703 .

When the cancellation process is completed, the printing apparatus 100 changes the status of the job to "Cancelled" (2014). Also, the time when the cancellation process is completed, the result, the user name and the job name are recorded as a job history (2015).

Finally, the printing device 100 sends an Update-Job-Status operation to the printing service 101 so that JobStatus=Cancelled (2016). The print service 101 that receives this operation changes the corresponding job status to "Cancelled" (2017).

Note that the user can set in advance in the printing apparatus 100 whether to perform pull printing or push printing. When pull printing is set, the sequence of any one of the first to third embodiments described above is executed, and when push printing is set, the sequences of FIGS. 19 and 20 are executed. becomes.

As described above, according to the above-described embodiments, in a printing device that acquires print data from a print service using IPP and performs printing, when the user issues a cancel instruction, the printing device prints the corresponding print data. Retrieve and delete from service. This makes it possible to cancel a protocol, such as IPP-Infra, in which the Cancel-Job operation is prohibited in the printing apparatus, using the same operation procedure as a protocol in which the cancel operation is permitted. Therefore, when there is an unnecessary print job, the user does not have to start up the client terminal to delete it, or ask the administrator of the print service to delete it. can be reduced.

<Other embodiments>
The present invention supplies a program that implements one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in the computer of the system or apparatus reads and executes the program. It can also be realized by processing to It can also be implemented by a circuit (for example, ASIC) that implements one or more functions.

Claims (23)

A printing device capable of receiving a print job from a print service using IPP (Internet Printing Protocol) and executing printing,
display control means for displaying a list of print jobs held in the print service;
receiving means for receiving a print instruction for a print job selected from the displayed list;
a print control unit that, when the print instruction is accepted, requests the print job selected as the target of the print instruction from the print service using IPP, and causes the print unit to print the print job. ,
When a cancellation instruction for a print job selected from the displayed list is accepted, the print control means requests the print job selected as the target of the cancellation instruction from the print service using IPP. A printing apparatus, wherein a print job selected as a target of a cancel instruction is not printed. 2. The printing apparatus according to claim 1, wherein the print job is a print job sent by requesting the print service for which the print instruction has been accepted. 3. The printing apparatus according to claim 1, wherein the cancel instruction is an instruction for erasing the print job. When an instruction to cancel the print job selected from the displayed list is received, the print control means requests the selected print job from the print service using IPP, and the print service transmits the request according to the request. 4. The printing apparatus according to claim 1, wherein incoming print jobs are received, but the received print jobs are not printed. When an instruction to cancel the print job selected from the displayed list is received, the print control means requests the selected print job from the print service using IPP, and the print service transmits the request according to the request. 4. The print job according to claim 1, wherein the received print job is not printed by discarding the received print job without providing the received print job to the printing means. The described printing device. 6. The method according to any one of claims 1 to 5, wherein when the print job selected as the target of the cancellation instruction is not printed, the print service is notified that the print job has been canceled. The described printing device. When the print job selected as the target of the cancel instruction by the print control means is not printed, the print job selected as the target of the cancel instruction is deleted from the list and is not printed in the print job history. 7. The printing apparatus according to any one of claims 1 to 6, characterized in that it does not record any time. A printing device capable of receiving a print job from a print service and executing printing,
display control means for displaying a list of print jobs held in the print service;
receiving means for receiving a print instruction for a print job selected from the displayed list;
a print control unit that, when the print instruction is accepted, requests the print service for the print job selected as the target of the print instruction, and causes the print unit to print the print job;
When a cancellation instruction for a print job selected from the displayed list is received, the print control means requests the print service selected as the target of the cancellation instruction from the print service, but the print job is the target of the cancellation instruction. A printing device, wherein a print job selected as is not printed. 9. The printing apparatus according to claim 8, wherein the print job is a print job transmitted by requesting the print service for which the print instruction has been received. 10. The printing apparatus according to claim 8, wherein the cancel instruction is an instruction for deleting the print job. When an instruction to cancel the print job selected from the displayed list is accepted, the print control means requests the selected print job from the print service, and according to the request, the print job transmitted from the print service. 11. The printing apparatus according to any one of claims 8 to 10, wherein the received print job is not printed. When an instruction to cancel the print job selected from the displayed list is accepted, the print control means requests the selected print job from the print service, and according to the request, the print job transmitted from the print service. 12. The printing apparatus according to any one of claims 8 to 11, wherein the received print job is not printed by discarding the received print job without providing it to the printing means. . 13. The method according to any one of claims 8 to 12, wherein when the print job selected as the target of the cancellation instruction is not printed, the print service is notified that the print job has been canceled. The described printing device. When the print job selected as the target of the cancel instruction by the print control means is not printed, the print job selected as the target of the cancel instruction is deleted from the list and is not printed in the print job history. 14. The printing apparatus according to any one of claims 8 to 13, wherein the recording is not performed when the A control method for a printing device capable of receiving a print job from a print service and executing printing, comprising:
a display control step of displaying a list of print jobs held in the print service;
a receiving step of receiving a print instruction for a print job selected from the displayed list;
a print control step of, when the print instruction is accepted, requesting the print service for the print job selected as the target of the print instruction, and causing a printing unit to print the print job;
When an instruction to cancel the print job selected from the displayed list is received, the print control step requests the print service for the print job selected as the target of the cancel instruction, but the cancel instruction is issued. A control method, wherein a print job selected as a target of is not printed. 16. The control method according to claim 15, wherein the print job is a print job sent by requesting the print service for which the print instruction has been accepted. 17. The control method according to claim 15, wherein the cancel instruction is an instruction for erasing the print job. When an instruction to cancel the print job selected from the displayed list is accepted, the print control step causes the print service to request the selected print job, and the print service transmits the request. 18. A control method as claimed in any one of claims 15 to 17, characterized in that a print job is received, but the received print job is not printed. When an instruction to cancel the print job selected from the displayed list is accepted, the print control step causes the print service to request the selected print job, and the print service transmits the request. 19. The method according to any one of claims 15 to 18, wherein the received print job is not printed by causing the print job to be received but discarding the received print job without providing it to the printing means. control method. 20. The method according to any one of claims 15 to 19, wherein when the print job selected as the target of the cancellation instruction is not printed, the print service is notified that the print job has been canceled. The control method described in . When the print job selected as the target of the cancel instruction by the print control means is not printed, the print job selected as the target of the cancel instruction is deleted from the list and is not printed in the print job history. 21. A control method according to any one of claims 15 to 20, characterized in that it is not recorded as . A program for causing a printing device to execute the control method according to any one of claims 15 to 21. 15. The printing service according to any one of claims 1 to 14, wherein the print service is a system provided on a cloud, and transmits a print job requested by the printing device to the printing device. printing device.

Images