Printing device, control method for the same, and printing system

Abstract

To provide a technique that can execute holding printing by using a printing device not having a pull-print function.SOLUTION: A printing system including a print server and a printing device is provided. The print server comprises: a maintaining unit that maintains a print job in a holding state on the basis of a determination that a printing device has a cancellation request function of requesting the print server to cancel the holding state of the print job; a cancellation unit that cancels the holding state of the print job on the basis of a request from a device different from the printing device; and a transmission unit that transmits the print job for which the holding state is cancelled to the printing device. The printing device comprises: a notification unit that notifies the print server of the fact that the printing device has the cancellation request function despite the fact that the printing device does not have the cancellation request function; an acquisition unit that acquires the print job from the print server after the holding state of the print job is cancelled on the basis of the request from the device different from the printing device; and a printing unit that executes printing according to the acquired print job.SELECTED DRAWING: Figure 17

Description

[Technical field]

[0001] The present invention relates to a printing apparatus, a control method thereof, and a printing system. [Background technology]

[0002] In recent years, cloud print services that allow print jobs to be submitted via the cloud and sent to a printing device are becoming popular (Patent Document 1). Some cloud print services are capable of implementing a printing method that holds a print job in a reserved state and causes the printing device to execute printing in response to additional instructions from a user. This type of printing method may be called reserved printing. Some printing devices have a pull print function that requests that the print job held in the print server be released from the reserved state. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2012-133489 A Summary of the Invention [Problem to be solved by the invention]

[0004] Some print servers can execute reservation printing only for print jobs that specify a printing device with a pull print function. In such print servers, reservation printing cannot be executed using a printing device that does not have a pull print function. According to some aspects of the present invention, a technique is provided for enabling reservation printing to be executed using a printing device that does not have a pull print function. [Means for solving the problem]

[0005] According to some embodiments, there is provided a printing system including a print server and a printing device, wherein the print server comprises: a holding means for holding the print job in a held state based on a determination that the printing device has a release request function for requesting the print server to release the held state of the print job; a release means for releasing the held state of the print job based on a request from a device other than the printing device; and a sending means for sending the print job whose held state has been released to the printing device, and the printing device comprises: a notification means for notifying the print server that the printing device has the release request function even though the printing device does not have the release request function; an acquisition means for acquiring the print job from the print server after the held state of the print job is released based on a request from a device other than the printing device; and a printing means for performing printing in accordance with the acquired print job. Effect of the Invention

[0006] According to the above embodiment, reservation printing can be performed using a printing device that does not have a pull print function. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a block diagram illustrating an example of the configuration of a printing system according to some embodiments. [Diagram 2] FIG. 2 is a block diagram illustrating an example of a hardware configuration of a computer according to some embodiments. [Diagram 3] FIG. 2 is a block diagram illustrating an example of the hardware configuration of a printing apparatus according to some embodiments. [Figure 4] FIG. 11 is a sequence diagram illustrating an example of a badge release operation according to some embodiments. [Diagram 5] FIG. 4 illustrates an example message used in some embodiments. [Figure 6] 10A and 10B are diagrams illustrating examples of changes to a list of print jobs according to some embodiments. [Figure 7] FIG. 4 illustrates an example message used in some embodiments. [Figure 8]FIG. 4 illustrates an example message used in some embodiments. [Figure 9] FIG. 4 illustrates an example message used in some embodiments. [Figure 10] Schematic diagrams illustrating an example of a screen displayed in some embodiments. [Figure 11] FIG. 11 is a sequence diagram illustrating an example of the operation of a mobile release according to some embodiments. [Figure 12] FIG. 4 illustrates an example message used in some embodiments. [Figure 13] 10A and 10B are diagrams illustrating examples of changes to a list of print jobs according to some embodiments. [Figure 14] FIG. 4 illustrates an example message used in some embodiments. [Figure 15] FIG. 4 illustrates an example message used in some embodiments. [Figure 16] FIG. 11 is a flow diagram illustrating an example of the operation of a printing device according to some embodiments. [Figure 17] Schematic diagrams illustrating an example of a screen displayed in some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, the embodiments will be described in detail with reference to the attached drawings. Note that the following embodiments do not limit the invention according to the claims. Although the embodiments describe a number of features, not all of these features are essential to the invention, and the features may be combined in any manner. Furthermore, in the attached drawings, the same reference numbers are used for the same or similar configurations, and duplicated descriptions are omitted.

[0009] [Printing system configuration example] With reference to Fig. 1, an example configuration of a printing system 100 according to some embodiments will be described. The printing system 100 includes, for example, a print server 101, an information processing device 102, a printing device 103, a printing device 104, and a mobile terminal 105. The number of components of the printing system 100 is not limited to the example of Fig. 1. For example, the printing system 100 may not include either the printing device 103 or the printing device 104. Furthermore, the printing system 100 may have components not shown in Fig. 1.

[0010] Each component of the printing system 100 is connected to a network 106. The print server 101 may be capable of communicating with each of the information processing device 102, the printing device 103, the printing device 104, and the mobile terminal 105 through the network 106. The communication between the print server 101 and these other devices may be performed using messages conforming to the Internet Printing Protocol (IPP). The network 106 may be a local area network (LAN), a wide area network (e.g., the Internet), a cellular network, or any combination thereof, and may be, for example, the Internet. The network 106 may include a wireless section or a wired section.

[0011] The print server 101 provides a print service that transmits a print job to any printing device (e.g., the printing device 103) according to a print job generated by the information processing device 102. For example, the print server 101 provides a logical printer to the information processing device 102 and accepts a print job for the logical printer. A logical printer is a virtual printing device (e.g., a printer object) provided by the print server 101. A logical printer may also be called a cloud printer. In contrast to a logical printer, a physical printing device such as the printing device 103 may also be called a physical printer.

[0012] The print server 101 may be a server in an on-premise environment connected to the network 106, or may be a server in a cloud computing environment (hereinafter simply referred to as cloud). The print service provided by the print server 101 in the cloud may be called a cloud print service (hereinafter referred to as CPS). One example of a cloud print service is Universal Print (registered trademark) provided by Microsoft Corporation. In the following description, a case where the print server 101 is in the cloud will be described. However, the following description also applies to a case where the print server 101 is in an on-premise environment.

[0013] The information processing device 102 provides a printing function to a user of the information processing device 102. The information processing device 102 may be a personal computer (PC), a smartphone, or another device. The information processing device 102 may specify a physical printer connected to the same LAN as the output destination, or may specify a logical printer provided by the print server 101 as the output destination. When a logical printer is specified as the output destination, a physical printer (e.g., the printing device 103) associated with the logical printer performs printing (e.g., paper ejection). The information processing device 102 using the CPS may be called a client or a client terminal. Printing performed by submitting a print job to a logical printer may also be called cloud print, remote print, or remote printing.

[0014] The printing device 103 has a printing function that performs printing according to a print job. The printing may be printing on a sheet-like recording medium such as paper, or may be forming a three-dimensional object (so-called three-dimensional printing). The printing method may be an electrophotographic method, an inkjet method, a thermal transfer method, or another method.

[0015] The printing device 103 may further have a login function. The login function may be a function that allows a user to log in to the printing device. The printing device 103 having the login function may authenticate the user and provide processing according to the user who has been successfully authenticated. For example, the printing device 103 may request the user to input a user name and password.

[0016] The printing device 103 supports reservation printing. The reservation printing may be a printing method in which a print job sent from the information processing device 102 to the print server 101 is held in a reserved state in the print server 101, and the printing device 103 starts printing in response to an additional instruction from the user. The printing device 103 has a pull print function to support reservation printing. The pull print function may be a function that requests the print server 101 to release the reserved state of a print job held in the print server 101 in response to an instruction from the user. The pull print function may be called a release request function. In the following description, the release of the reserved state of a print job performed by a user operating the printing device 103 is represented as a badge release. The badge release may be called a local release, a direct release, a printer release, or the like. The print server 101 releases the reserved state of a print job based on a request from the printing device 103. In order to prevent the printing of a print job submitted by another user from being started, the printing device 103 may allow the user to execute the badge release on the condition that the user is logged in to the printing device 103.

[0017] In addition to or instead of badge release, the print server 101 may release the hold state of the print job based on a request from a device (e.g., the mobile terminal 105) other than the printing device 103. In the following description, the release of the hold state based on a request from a device other than the printing device 103 is referred to as mobile release. Mobile release may also be called remote release or indirect release.

[0018] Printing device 103 may further include at least one of a scanner function and a fax function as a main function. A printing device having multiple main functions in this way may be called a multifunction peripheral (MFP).

[0019] The printing device 104 has a printing function, similar to the printing device 103. However, unlike the printing device 103, the printing device 104 does not have a login function or a pull print function. The printing device 104 may be a dedicated machine (SFP: Single Function Printer) that has only a printing function as its main function.

[0020] The mobile terminal 105 provides a function for executing the mobile release to a user of the mobile terminal 105. The mobile terminal 105 may be a laptop computer, a smartphone, or other device. For example, an application providing a function for executing the mobile release may be installed on the mobile terminal 105. The mobile terminal 105 may have a login function for logging the user into the mobile terminal 105. The mobile terminal 105 may allow the user to execute the mobile release on the condition that the user is logged into the mobile terminal 105.

[0021] In a typical scenario, a user who has performed reservation printing for the printing device 103 using the information processing device 102 approaches the printing device 103 with his / her mobile terminal 105. The user then logs into the mobile terminal 105. The user causes the printing device 103 to start printing by executing mobile release using the mobile terminal 105. In this example, mobile release is executed using the mobile terminal 105, but mobile release may also be executed using a device that is not intended for mobile use (e.g., a desktop computer). The mobile terminal 105 may be used to submit a print job to the print server 101.

[0022] [Example of computer hardware configuration] An example of a hardware configuration of a computer 200 according to some embodiments will be described with reference to Fig. 2. The computer 200 may be used as a print server 101, an information processing device 102, or a mobile terminal 105. The computer 200 may have the components shown in Fig. 2.

[0023] The central processing unit (CPU) 201 is a general-purpose processing circuit that controls the overall operation of the computer 200. The random access memory (RAM) 202 is a volatile memory circuit, and is used as a temporary storage area such as a work area for processing by the CPU 201. The read-only memory (ROM) 203 is a non-volatile memory circuit, and stores programs and data used in the processing by the CPU 201. The storage device 204 is a non-volatile storage device, and stores programs and data used in the processing by the CPU 201. The storage device 204 may be, for example, a hard disk drive (HDD) or a solid state drive (SSD). The storage device 204 may also be called a secondary storage device. The operations of the computer 200 may be realized by the CPU 201 executing a program read from the storage device 204 to the RAM 202.

[0024] The input interface (I / F) 205 is an I / F for exchanging signals with the input device 210. The input device 210 is a device that obtains input from a user of the computer 200. The input device 210 may be, for example, a keyboard, a touch panel, a microphone, a mouse, or any combination thereof. The output I / F 206 is an I / F for exchanging signals with the output device 220. The output device 220 is a device that provides information to a user of the computer 200. The output device 220 may be, for example, a display, a speaker, or any combination thereof. The network I / F 207 is an I / F for communicating with a device outside the computer 200. Each of the CPU 201, the RAM 202, the ROM 203, the storage device 204, the input I / F 205, the output I / F 206, and the network I / F 207 is connected to a system bus 208. In the example of FIG. 2, the input device 210 and the output device 220 are shown as devices separate from the computer 200. Alternatively, computer 200 may include input device(s) 210 and output device(s) 220 .

[0025] [Example of hardware configuration of printing device] With reference to FIG. 3(a), a hardware configuration example of the printing device 103 according to some embodiments will be described. The printing device 103 may have the components shown in FIG. 3(a). The CPU 301 is a general-purpose processing circuit that controls the overall operation of the printing device 103. The RAM 302 is a volatile memory circuit and is used as a temporary storage area such as a work area for processing by the CPU 301. The ROM 303 is a non-volatile memory circuit and stores programs and data used in the processing by the CPU 301. The storage device 304 is a non-volatile storage device and stores programs and data (e.g., print jobs, image data, setting information) used in the processing by the CPU 301. The storage device 304 may be, for example, an HDD or SSD. The storage device 304 may also be called a secondary storage device. The operation of the printing device 103 may be realized by the CPU 301 executing a program read from the storage device 304 to the RAM 302.

[0026] Printer I / F 305 is an I / F for exchanging signals with printer engine 320. Printer engine 320 performs printing based on signals (e.g., image signals and print commands) supplied from control unit 310 via printer I / F 305. Printing may be electrophotographic printing in which toner is transferred and fixed on paper, inkjet printing in which ink is ejected onto paper to print, or three-dimensional printing.

[0027] Scanner I / F 306 is an I / F for exchanging signals with scanner engine 330. Scanner engine 330 supplies a signal (e.g., an image signal) obtained by reading an original to control unit 310 via scanner I / F 306. CPU 301 may process the image signal supplied from scanner engine 330 and supply a recording image signal obtained thereby to printer engine 320. CPU 301 may also generate image data based on the image signal supplied from scanner engine 330 and transmit this to an external device.

[0028] The operation unit I / F 307 is an I / F for exchanging signals with the operation unit 340. The operation unit 340 is a device that acquires input from a user of the printing device 103 and provides information to the user of the printing device 103. The operation unit 340 may be configured with, for example, a display panel (e.g., a liquid crystal display), a speaker, a touch panel, a keyboard, buttons, a touch screen, or any combination of these.

[0029] The network I / F 308 is an I / F for communicating with devices external to the printing device 103. The control unit 310 is configured with the CPU 301, the RAM 302, the ROM 303, the storage device 304, the printer I / F 305, the scanner I / F 306, the operation unit I / F 307, and the network I / F 308. Each component included in the control unit 310 is connected to a system bus. The authentication unit 309 authenticates a user who uses the printing device 103. For example, the authentication unit 309 may authenticate a user based on a user name and a password input using the operation unit 340. Alternatively or in addition to this, the authentication unit 309 may authenticate a user based on biometric information of the user (e.g., a fingerprint, an iris, a face shape, etc.) acquired using a sensor. Alternatively or in addition to this, the authentication unit 309 may authenticate a user by reading information from a personal identification card held by the user.

[0030] With reference to Fig. 3(b), an example of the hardware configuration of the printing device 104 according to some embodiments will be described. The printing device 104 may have the components shown in Fig. 3(b). The printing device 104 differs from the printing device 103 in that it does not have a scanner I / F 306, an operation unit I / F 307, an authentication unit 309, a scanner engine 330, or an operation unit 340, but may be similar to the printing device 103 in other respects.

[0031] [Overall process sequence for badge release] With reference to Fig. 4, the overall operation of the printing system 100 regarding the process of executing badge release will be described. Badge release may be executable when printing is instructed to a printing device having a login function and a pull print function. Since the printing device 103 has a login function and a pull print function, badge release can be executed when a user instructs the printing device 103 to print. On the other hand, since the printing device 104 does not have a login function, badge release cannot be executed when a user instructs the printing device 104 to print. The case where printing is instructed to the printing device 103 will be described below.

[0032] In S401, the printing device 103 transmits capability information of the printing device 103 to the print server 101. The print server 101 receives this capability information. The capability information may include information indicating functions supported by the printing device 103. In the operation of FIG. 4, it is assumed that the capability information transmitted in S401 includes information indicating that the printing device 103 has a pull print function. Based on the capability information, the print server 101 determines that the printing device 103 has the pull print function.

[0033] The information indicating that the printing device 103 has the pull print function may be sent using a message 500 shown in Fig. 5. The message 500 represents an Update-Output-Device-Attributes Request operation conforming to the IPP. In the message 500, the attribute "pull-print-supported" is set to "True", thereby indicating that the printing device 103 has the pull print function. In response to receiving the message 500, the print server 101 may respond with a message 501 shown in Fig. 5. The message 501 represents an Update-Output-Device-Attributes Response operation conforming to the IPP.

[0034] In S402, in response to a request from the information processing device 102, the print server 101 transmits to the information processing device 102 printer information of a virtual printer corresponding to one or more printing devices registered in the print server 101. The information processing device 102 receives this printer information. The one or more printing devices registered in the print server 101 include the printing device 103.

[0035] In S403, a user of the information processing device 102 (in the following description, assumed to be Smith) instructs the information processing device 102 to print a print object (e.g., a document) on a virtual printer provided by the print server 101. At this point, the virtual printer specified by the user may be associated only with the printing device 103, or may be associated with multiple printing devices including the printing device 103. When the virtual printer is associated with multiple printing devices, the user may be able to specify later which printing device to use for printing.

[0036] In S404, the information processing apparatus 102 (for example, its print application or operating system) generates a print job according to instructions from the user, and transmits this print job to the print server 101. The print server 101 receives this print job.

[0037] In S405, the print server 101 assigns an identification number to the print job received in S404, and stores the print job in storage (for example, the storage device 204) of the print server 101. In addition, the print server 101 updates a job list for managing the print jobs held in the print server 101.

[0038] The print server 101 processes the print job received in S404 by reservation printing based on the determination that the printing device 103 has a pull print function. Specifically, the print server 101 holds the print job received in S404 in a reserved state. Processing the print job by reservation printing may be further based on reservation printing being specified by the user. For example, the print server 101 may not process the print job by reservation printing if reservation printing is not specified by the user.

[0039] On the other hand, the print server 101 does not process the print job received in S404 by reservation printing based on the determination that the printing device 103 does not have the pull print function. Specifically, the print server 101 does not hold the print job received in S404 in a reserved state. In this case, the print job is processed by the printing device 103 without any additional instructions from the user (i.e., printing is executed according to the print job).

[0040] With reference to FIG. 6, an example of the job list 600 after the update in S405 will be described. Assume that in S405, "3" is assigned to the "job-id" of the newly acquired print job. Then, the print server 101 sets the "job-state" and "job-state-reason" of this print job to "pending-hold" and "job-fetchable-by-user, job-release-wait", respectively. This indicates that this print job is in a hold state. The job list 600 also manages a print job (a print job with "job-id" of "2") that was submitted in the past by the same user (Smith) and is in a hold state. The job list 600 also manages a print job (a print job with "job-id" of "1") that was submitted in the past by another user (Alice) and is in a hold state. The print server 101 may manage print jobs in association with the user's cloud account name. For example, Smith's cloud account name is "RobertSmith@example.com". The cloud account name may be sent from the information processing device 102 to the print server 101 together with the print job.

[0041] In S406, a user (Smith) logs in to the printing device 103 to cause the printing device 103 to execute printing in accordance with the print job held by the print server 101. For example, the user uses the operation unit 340 of the printing device 103 to input a user name and a password.

[0042] In S407, the printing device 103 performs a login process. Specifically, the printing device 103 authenticates the user by determining whether the information input by the user in S406 matches information stored in the printing device 103. If the user authentication is successful, the printing device 103 may further determine whether the user has authority to use the printing device 103. Thereafter, the printing device 103 may identify the user's cloud account name based on the user name input by the user in S406. The association between the user name and the cloud account name may be set in advance and stored in the storage device 304 of the printing device 103. For example, the printing device 103 identifies that the cloud account name of the user (Smith) is "RobertSmith@example.com".

[0043] In response to the user successfully logging in, in S408, the printing device 103 requests the print server 101 to send a list of print jobs associated with the user currently logged in to the printing device 103. The print jobs associated with the user currently logged in to the printing device 103 include print jobs submitted by the user and in a pending state. This request may be sent using a message 700 shown in FIG. 7. The message 700 represents a Get-Jobs Request operation conforming to IPP. In the message 700, the attribute "my-jobs" is "True", which indicates that a list of print jobs is requested for a user specified by the attribute "Requesting-user-name" or the attribute "Requesting-user-uri". In the message 700, the user name "Smith" is specified in the attribute "Requesting-user-name", and the cloud account name of this user "RobertSmith@example.com" is specified in the attribute "Requesting-user-uri". Both the "Requesting-user-name" and "Requesting-user-uri" attributes may be specified in message 700, or only one of them may be specified. Alternatively or additionally, message 700 may include other information that allows print server 101 to uniquely identify the user.

[0044] In S409, the print server 101 responds to the printing device 103 with a list of print jobs associated with the user specified in S408. For example, the print server 101 generates the responding list by extracting information of print jobs (print jobs with "job-id" of "2" or "3") associated with "RobertSmith@example.com" specified in the attribute "Requesting-user-uri" from the job list 600. This list response may be sent using a message 701 shown in Fig. 7. The message 701 represents a Get-Jobs Response operation conforming to IPP. The message 701 includes information of print jobs with "job-id" of "2" or "3".

[0045] In S410, the printing device 103 displays the list information received in S409 on the operation unit 340. In S411, the user specifies a print job that the user wishes to print from one or more print jobs (two print jobs in this example) shown in the list, and issues an instruction to start printing.

[0046] In S412, the printing device 103 requests information on the print job specified by the user in S410 (e.g., the print job whose "job-id" is "2") from the print server 101. The print server 101 receives this request. This request may be sent using a message 800 shown in FIG. 8. The message 800 represents a Fetch-Job Request operation that conforms to IPP. In the message 800, the attribute "job-id" indicates the requested print job. The attribute "Requesting-user-uri" of the message 800 indicates the cloud account name of the user currently logged in to the printing device 103.

[0047] In response to the request received in S412, the print server 101 responds with information about the requested print job. The print device 103 receives this response. This response may be sent using message 801 shown in Figure 8. Message 801 represents an IPP-compliant Fetch-Job Response operation.

[0048] In S413, the printing device 103 requests the print job specified by the user in S410 (e.g., a print job with a "job-id" of "2") from the print server 101. The print server 101 receives this request. This request may be sent using a message 900 shown in FIG. 9. The message 900 represents an Acknowledge-Job Request operation that conforms to IPP. In the message 900, the attribute "job-id" indicates the requested print job. The attribute "Requesting-user-uri" of the message 900 indicates the cloud account name of the user currently logged in to the printing device 103.

[0049] In S414, the print server 101 releases the waiting state of the print job specified by the printing device 103. Specifically, the print server 101 updates the job list 600 to a job list 601 as shown in FIG. 6. In the job list 601, the "job-state" and "job-state-reason" of the print job with a "job-id" of "2" are updated to "processing" and "none", respectively. Thereafter, the print server 101 transmits an acknowledgement response to the request received in S413. The printing device 103 receives this acknowledgement response. This acknowledgement response may be transmitted using a message 901 shown in FIG. 9. The message 901 represents an Acknowledge-Job Response operation conforming to IPP.

[0050] In S415, the print server 101 transmits the print job specified by the printing device 103 to the printing device 103. The printing device 103 receives this print job. In S416, the printing device 103 executes printing in accordance with the received print job (for example, performs paper ejection processing).

[0051] An example of a screen displayed on the operation unit 340 of the printing device 103 during badge release will be described with reference to Fig. 10. In S407, the printing device 103 prompts the user to log in to the printing device 103 by displaying a screen 1000 on the operation unit 340. Thereafter, in response to the user (Smith) logging in to the printing device 103, the printing device 103 displays a screen 1001 on the operation unit 340. The screen 1001 indicates that Smith is currently logged in.

[0052] In response to the user selecting "Job List" on screen 1001, the printing device 103 executes S408 (request for job list). The printing device 103 generates screen 1002 including a list of print jobs acquired in response to this request, and displays it on the operation unit 340. Screen 1002 includes a list of print jobs associated with the user (Smith) currently logged in to the printing device 103.

[0053] [Overall process sequence for mobile release] With reference to FIG. 11, the overall operation of the printing system 100 regarding the process of executing the mobile release will be described. The mobile release may be executable when printing is instructed to a printing device that the print server 101 recognizes as having a pull print function. Since the printing device 103 has a pull print function, the mobile release can be executed when the user instructs the printing device 103 to print. On the other hand, the printing device 104 does not have a pull print function. However, as described later, the printing device 104 notifies the print server 101 that it has a print function, even though it does not have a pull print function. As a result, the print server 101 recognizes that the printing device 104 has a pull print function. Therefore, even when the user instructs the printing device 104 to print, the mobile release can be executed. Below, the case where printing is instructed to the printing device 103 will be described. The same explanation applies to the case where printing is instructed to the printing device 104.

[0054] The operations of S401 to S405 may be the same as those in Fig. 4, and therefore redundant explanations will be omitted. When the operations in Fig. 11 are executed by the printing device 104, in S401, the printing device 104 notifies the print server 101 that it has a pull print function, even though it does not have the pull print function.

[0055] In S1001, a user (Smith) logs into a mobile terminal 105 (e.g., an application that provides a mobile release) to cause a printing device 103 to execute printing according to a print job held by a print server 101. For example, the user uses an input device 210 of the mobile terminal 105 to input a cloud account name (RobertSmith@example.com) and a password.

[0056] In S1102, the mobile terminal 105 performs a login process. Specifically, the mobile terminal 105 authenticates the user by determining whether the information entered by the user in S1101 matches information stored in the mobile terminal 105. If the user authentication is successful, the mobile terminal 105 may further determine whether the user has the authority to use the printing device 103.

[0057] In response to the user successfully logging in, in S1103, the mobile terminal 105 requests the print server 101 to send a list of print jobs associated with the user currently logged in to the mobile terminal 105. The print jobs associated with the user currently logged in to the mobile terminal 105 include print jobs submitted by this user and in a pending state. This request may be sent using a message 700 shown in Fig. 7. The explanation regarding the message 700 may be the same as that described above, and therefore a duplicate explanation will be omitted.

[0058] In S1104, the print server 101 responds with a list of print jobs associated with the user specified in S1103 to the mobile terminal 105. The process of S1104 may be the same as the process of S409 described above, and therefore a duplicated description will be omitted.

[0059] In S1105, the mobile terminal 105 displays the list information received in S1104 on the output device 220. This list includes only information about print jobs associated with the user (Smith) currently logged in to the mobile terminal 105, similar to screen 1002 in Fig. 10. In S1106, the user specifies the print job that the user wishes to print from one or more print jobs (two print jobs in this example) shown in the list, and issues an instruction to start printing.

[0060] In S1107, the mobile terminal 105 requests the print server 101 to release the hold state of the print job (e.g., the print job whose "job-id" is "2") specified by the user in S1106. The print server 101 receives this request. This request may be sent using a message 1200 shown in FIG. 12. The message 1200 represents a Release-Job Request operation conforming to IPP. In the message 1200, the attribute "job-id" indicates the print job to be released from the hold state. The attribute "Requesting-user-uri" of the message 1200 indicates the cloud account name of the user currently logged in to the mobile terminal 105. The attribute "job-release-type" of the message 1200 indicates the identifier of the application that created the message 1200. The message 1200 includes the attribute "job-release-type", which indicates that the request to release the hold state was made by a device other than the printing device (in this example, the mobile terminal 105). The value of the attribute “job-release-type” can be any value recognized by printing system 100 .

[0061] In S1108, the print server 101 releases the waiting state of the print job specified by the mobile terminal 105. Specifically, the print server 101 updates the job list 600 to a job list 1300 as shown in FIG. 13. In the job list 1300, the "job-state" and "job-state-reason" of the print job with "job-id" of "2" are updated to "pending" and "job-fetchable", respectively. These attribute values ​​indicate that the print job with "job-id" of "2" can be acquired by the printing device. After that, the print server 101 transmits an acknowledgement response to the request received in S1107. The mobile terminal 105 receives this acknowledgement response. This acknowledgement response may be transmitted using a message 1201 shown in FIG. 12. The message 1201 represents a Release-Job Response operation conforming to IPP.

[0062] In S1109, the printing device 103 transmits an event confirmation request to the print server 101. The print server 101 receives this event confirmation request. The event confirmation request may be an inquiry as to whether an event related to the printing device 103 has occurred. The event related to the printing device 103 may include the presence of a print job that the printing device 103 can acquire. In other words, the printing device 103 inquires of the print server 101 as to whether there is a print job that the printing device 103 can acquire. The printing device 103 may periodically transmit the event confirmation request to the print server 101. The event confirmation request may be transmitted using a message 1400 shown in FIG. 14. The message 1400 represents a Get-Notification Request operation that complies with IPP.

[0063] At this point, the print job with "job-id" "2" has been released from hold based on a request from a device other than printing device 103 (in this example, mobile terminal 105). Print server 101 then responds that there is a print job available for printing device 103 to acquire. Printing device 103 receives this response. This response may be sent using message 1401 shown in FIG. 14. Message 1401 represents an IPP-compliant Get-Notification Response operation.

[0064] If there is a print job that the printing device 103 can acquire, in S1110 the printing device 103 requests the print server 101 for a list of print jobs that the printing device 103 can acquire. The print server 101 receives this request. This request may be sent using a message 1500 shown in FIG. 15. The message 1500 represents a Get-Jobs Request operation that complies with IPP. In the message 1500, the attribute "my-jobs" is "False", which indicates that information on print jobs related to all users is requested. Also, in the message 1500, the attribute "which-jobs" is "fetchable", which indicates that information on print jobs that the printing device 103 can acquire is requested. The print server 101 responds to the request in S1110 with a message 701.

[0065] In S1111, the printing device 103 requests the print server 101 to send a print job included in the list acquired in S1110 (e.g., a print job whose "job-id" is "2"). The print server 101 receives this request. This request may be made by message 800 in FIG. 8 (i.e., a Fetch-Job Request operation).

[0066] In S1112, the print server 101 transmits the print job specified by the printing device 103 to the printing device 103. The printing device 103 receives this print job. In S1113, the printing device 103 executes printing in accordance with the received print job (for example, performs paper ejection processing).

[0067] [Example of printing device operation] With reference to Fig. 16, an example of a control method for controlling the printing device 103 so that the control unit 310 of the printing device 103 notifies the print server 101 of the capability information of the printing device 103 will be described. Each step of the method of Fig. 16 may be performed by the CPU 301 of the printing device 103 executing a program loaded into the memory (e.g., RAM 302) of the printing device 103. Alternatively, some or all of the steps of the method of Fig. 16 may be performed by a dedicated integrated circuit such as an ASIC. The method of Fig. 16 may be started in response to the printing device 103 being started.

[0068] In S1601, the printing device 103 determines whether it is set to notify the print server 101 that the printing device 103 has a pull print function. In the following description, notifying the print server 101 that the printing device 103 has a pull print function is referred to as a pull print notification. When the printing device 103 is set to perform a pull print notification, the pull print notification is represented as being valid. When the printing device 103 is set not to perform a pull print notification, the pull print notification is represented as being invalid. If it is determined that the pull print notification is valid ("YES" in S1601), the printing device 103 transitions the process to S1602, and otherwise ("NO" in S1601, for example, when it is determined that the pull print notification is invalid), the printing device 103 transitions the process to S1603.

[0069] The pull print notification settings may be stored in memory (e.g., RAM 202) of printing device 103. The default value of the pull print notification may be enabled or disabled. Upon startup, printing device 103 may use the pull print notification setting value previously set by the user, or may use the default value.

[0070] The settings of the pull print notification may be changeable by the user of the printing device 103. An example of a screen 1700 for setting the pull print notification will be described with reference to Fig. 17(a). The screen 1700 may be displayed on the operation unit 340 of the printing device 103, for example.

[0071] The screen 1700 includes an ON button for enabling the pull print notification and an OFF button for disabling the pull print notification. The printing device 103 enables the pull print notification in response to a user of the printing device 103 selecting the ON button using the operation unit 340. The printing device 103 disables the pull print notification in response to a user of the printing device 103 selecting the OFF button using the operation unit 340.

[0072] The screen 1700 may further be used for the user to set whether or not to enable a login function of the printing device 103. The screen 1700 includes an ON button for enabling the login function and an OFF button for disabling the login function. The printing device 103 enables the login function in response to a user of the printing device 103 selecting the ON button using the operation unit 340. The printing device 103 disables the login function in response to a user of the printing device 103 selecting the OFF button using the operation unit 340. When the login function is enabled, the printing device 103 may allow the user to use the printing device 103 only when the user logs in to the printing device 103.

[0073] Screen 1700 may further be used to transition to screen 1701 for registering or editing user account information. Screen 1700 includes a user registration setting button for transitioning to screen 1701. Screen 1701 is used to register or edit user account information. The account information may include, for each user, a username for logging in to printing device 103, a password for logging in to printing device 103, and a cloud account name. The cloud account name may be used for badge release, as described above.

[0074] In S1602, if it is determined that the pull print notification is valid, the printing device 103 notifies the print server 101 that the printing device 103 has pull print capability. This notification may correspond to S401 in Fig. 4 or Fig. 11. As described above, the notification that the printing device 103 has pull print capability may be sent using message 500 shown in Fig. 5. Message 500 represents an Update-Output-Device-Attributes Request operation that conforms to IPP.

[0075] In S1602, when it is determined that the pull print notification is invalid, the printing device 103 notifies the print server 101 that the printing device 103 does not have the pull print function. The notification that the printing device 103 does not have the pull print function may be sent using a message 510 shown in FIG. 5. The message 510 represents an Update-Output-Device-Attributes Request operation conforming to IPP. In the message 510, the attribute "pull-print-supported" is "False", thereby indicating that the printing device 103 does not have the pull print function. Alternatively, the notification that the printing device 103 does not have the pull print function may be sent using a message 520 shown in FIG. 5. The message 520 represents an Update-Output-Device-Attributes Request operation conforming to IPP. In the message 520, the attribute "pull-print-supported" is not included, thereby indicating that the printing device 103 does not have the pull print function.

[0076] In S1604, the printing device 103 determines whether the pull print notification setting has been changed. If it is determined that the pull print notification setting has been changed ("YES" in S1604), the printing device 103 transitions the process to S1601, and otherwise ("NO" in S1604) repeats S1604. If it is determined that the pull print notification setting has been changed, the printing device 103 notifies the print server 101 whether the printing device 103 has a pull print function based on the changed setting.

[0077] In the operation of FIG. 16, it is possible to set whether to enable the pull print notification and whether to enable the login function separately. Therefore, the printing device 103 notifies the print server 101 that the printing device 103 has the pull print function, regardless of whether the login function is enabled, based on the setting that the printing device 103 notifies the print server 101 that the printing device 103 has the pull print function. On the other hand, the printing device 103 does not notify the print server 101 that the printing device 103 has the pull print function, regardless of whether the login function is enabled, based on the setting that the printing device 103 does not notify the print server 101 that the printing device 103 has the pull print function. When the pull print notification is enabled and the login function is enabled, the user can perform both badge release and mobile release. When the pull print notification is enabled and the login function is disabled, the user cannot perform either badge release or mobile release. When the pull print notification is disabled and the login function is enabled, the user cannot perform badge release, but can perform mobile release. When the pull print notification is disabled and the login function is disabled, the user cannot perform either badge release or mobile release.

[0078] The control method of Fig. 16 may be executed by the printing device 104. In this case, each step of the method of Fig. 16 may be performed by the CPU 301 of the printing device 104 executing a program loaded into a memory (e.g., RAM 302) of the printing device 104. Alternatively, some or all of the steps of the method of Fig. 16 may be performed by a dedicated integrated circuit such as an ASIC. The method of Fig. 16 may be started in response to the printing device 103 being started.

[0079] As described above, the printing device 104 does not have a pull print function. Therefore, in the method of FIG. 4 related to badge release, the printing device 104 cannot request the print server 101 to release the hold state of the print job in S412. However, the printing device 104 can notify the print server 101 that it has a print function, even though it does not have a pull print function. As a result, the print server 101 recognizes that the printing device 104 has a pull print function. Therefore, even if the user instructs the printing device 104 to print, the user can execute mobile release.

[0080] The settings of the pull print notification in the printing device 104 may be changeable by the user. An example of a screen 1710 for setting the pull print notification will be described with reference to FIG. 17(b). The screen 1710 may be displayed on a display unit of a device (e.g., the information processing device 102 or the mobile terminal 105) other than the printing device 104. The printing device 104 may be capable of providing a remote user interface (RUI) to display the screen 1710 on another device. Alternatively, the printing device 104 may be provided with a display unit for displaying the screen 1710.

[0081] The method for setting the pull print notification using screen 1710 may be the same as that for screen 1700, and therefore a duplicated description will be omitted. Since the printing device 104 does not have a login function, screen 1710 does not include a graphical object for enabling the login function.

[0082] In the above example, the printing device 104 does not have a pull print function because it does not have a login function. The printing device 104 may not have a login function because it does not have a user authentication function, or may not have a login function because it does not have an operation unit for inputting a user name and password.

[0083] <Other embodiments> The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions.

[0084] <Summary of the embodiment> [Item 1] A printing system including a print server and a printing device, The print server includes: a holding unit that holds the print job in a hold state based on a determination that the printing device has a release request function for requesting the print server to release the hold state of the print job; a release means for releasing the hold state of the print job based on a request from a device other than the printing device; a transmission means for transmitting the print job, the hold state of which has been released, to the printing device; The printing device includes: a notification means for notifying the print server that the printing device has the release request function even though the printing device does not have the release request function; an acquisition unit that acquires the print job from the print server after the print job is released from a hold state based on a request from a device other than the printing device; a printing unit that executes printing according to the acquired print job. [Item 2] 2. The printing system according to item 1, wherein the printing device does not have a login function that allows a user to log in to the printing device. [Item 3] the printing device further includes a setting unit for setting whether to notify the print server that the printing device has the release request function, The notification means is notifying the print server that the printing device has the release request function based on a setting to notify the print server that the printing device has the release request function; The printing system of item 1 or 2, wherein the printing device notifies the print server that it does not have the release request function based on the fact that it is not set to notify the print server that it has the release request function. [Item 4] 4. The printing system according to any one of items 1 to 3, wherein the holding unit does not hold the print job in a hold state based on a determination that the printing device does not have the release request function. [Item 5] The printing device further includes an inquiry unit that inquires of the print server whether there is a print job that the printing device can acquire, The printing system described in any one of items 1 to 4, wherein the printing server further includes a response means for responding to a query from the query means that there is a print job that the printing device can acquire when the hold state of the print job is released based on a request from a device other than the printing device. [Item 6] 6. The printing system according to any one of items 1 to 5, wherein the device that sends the request to release the print job from a held state has a login function that allows a user to log in to the device. [Item 7] 7. The printing system according to any one of items 1 to 6, wherein the notification unit notifies the print server that the printing device has the release request function by using a message conforming to the Internet Printing Protocol. [Item 8] 1. A printing device, comprising: a notification means for notifying the print server that the printing device has a release request function for requesting the print server to release a print job held by the print server, even though the printing device does not have the release request function; an acquisition unit that acquires the print job from the print server after the print job is released from a hold state based on a request from a device other than the printing device; a printing unit that executes printing in accordance with the acquired print job. [Item 9] A program for causing a computer to function as each of the means of the printing device described in item 8. [Item 10] A method for controlling a printing device, comprising: a notification step of notifying the print server that the printing device has a release request function for requesting the print server to release a print job held by the print server, even though the printing device does not have the release request function; an acquisition step of acquiring the print job from the print server after the print job is released from a hold state based on a request from a device other than the printing device; a printing step of executing printing in accordance with the acquired print job.

[0085] The invention is not limited to the above-described embodiments, and various modifications and variations are possible without departing from the spirit and scope of the invention. Accordingly, the following claims are appended to apprise the public of the scope of the invention. [Explanation of symbols]

[0086] 101 print server, 102 information processing device, 103 printing device, 104 printing device, 105 mobile terminal

Claims

1. A printing system including a print server and a printing device, The print server includes: a holding unit that holds the print job in a hold state based on a determination that the printing device has a release request function for requesting the print server to release the hold state of the print job; a release means for releasing the hold state of the print job based on a request from a device other than the printing device; a transmission means for transmitting the print job, the hold state of which has been released, to the printing device; The printing device includes: a notification means for notifying the print server that the printing device has the release request function even though the printing device does not have the release request function; an acquisition unit that acquires the print job from the print server after the print job is released from a hold state based on a request from a device other than the printing device; a printing unit that executes printing according to the acquired print job.

2. The printing system according to claim 1 , wherein the printing device does not have a login function that allows a user to log in to the printing device.

3. the printing device further includes a setting unit for setting whether to notify the print server that the printing device has the release request function, The notification means includes: notifying the print server that the printing device has the release request function based on a setting to notify the print server that the printing device has the release request function; 2. The printing system according to claim 1, wherein the printing device notifies the print server that the printing device does not have the release request function based on the fact that the printing device has the release request function not being set to notify the print server.

4. 2. The printing system according to claim 1, wherein the holding unit does not hold the print job in a hold state when it is determined that the printing device does not have the release request function.

5. The printing device further includes an inquiry unit that inquires of the print server whether there is a print job that the printing device can acquire, The printing system according to claim 1 , wherein the print server further comprises a response means for responding to an inquiry from the inquiry means that there is a print job that the printing device can acquire when the hold state of the print job is released based on a request from a device other than the printing device.

6. The printing system according to claim 1 , wherein the device that transmits the request to release the print job from a held state has a login function that allows a user to log in to the device.

7. 2. The printing system according to claim 1, wherein said notification means notifies said print server that said printing device has said release request function by using a message conforming to an Internet Printing Protocol.

8. 1. A printing device, comprising: a notification means for notifying the print server that the printing device has a release request function for requesting the print server to release a print job held by the print server, even though the printing device does not have the release request function; an acquisition unit that acquires the print job from the print server after the print job is released from a hold state based on a request from a device other than the printing device; a printing unit that executes printing in accordance with the acquired print job.

9. A program for causing a computer to function as each of the means of the printing device according to claim 8.

10. A method for controlling a printing device, comprising: a notification step of notifying the print server that the printing device has a release request function for requesting the print server to release a print job held by the print server, even though the printing device does not have the release request function; an acquisition step of acquiring the print job from the print server after the print job is released from a hold state based on a request from a device other than the printing device; A printing step of executing printing in accordance with the acquired print job.

Images