Printing device, control method therefor, and printing system

Abstract

Provided is a printing system including a print server and a printing device. The print server is provided with: a holding unit that holds a print job in a pending state on the basis of a determination that the printing device has a release request function for requesting the print server to release the print job from the pending state; a release unit that releases the print job from the pending state on the basis of a request from the printing device or a request from a device different from the printing device; and a transmission unit that transmits the print job released from the pending state to the printing device. The printing device is provided with: a login unit that provides a login function for logging a user into the printing device; a setting unit for setting whether or not to enable the login function and whether or not to notify the print server that the printing device has the release request function; a notification unit that notifies the print server that the printing device has the release request function, on the basis of the setting to notify the print server that the printing device has the release request function; an acquisition unit that acquires the print job from the print server after the print job is released from the pending state; and a printing unit that executes printing according to the acquired print job.

Description

Printing device, control method thereof, and printing system

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

[0002] In recent years, cloud print services that allow users to submit print jobs via the cloud and send them to a printing device have become popular (see Patent Literature 1). Some cloud print services are capable of implementing a printing method that holds a print job in a reserved state and prompts the printing device to print in response to additional instructions from the user. This printing method is sometimes called reservation printing. Some printing devices have a pull print function that requests the print server to release the reserved state of a print job.

[0003] JP 2012-133489 A

[0004] Some conventional printing devices have a login function and enable the pull print function only when the login function is enabled. On such printing devices, reservation printing cannot be performed unless the login function is enabled. According to some aspects of the present invention, a technology is provided that enables reservation printing regardless of whether the login function is enabled.

[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 unit that holds the print job in a held state based on a determination that the printing device has a release request function that requests the print server to release the hold state of the print job; a release unit that releases the hold state of the print job based on a request from the printing device or a request from a device other than the printing device; and a sending unit that sends the print job whose hold state has been released to the printing device, and the printing device comprises: a login unit that provides a login function that allows a user to log in to the printing device; a setting unit that sets whether to enable the login function and whether to notify the print server that the printing device has the release request function; a notification unit that notifies the print server that the printing device has the release request function based on the setting that the printing device notifies the print server that the print device has the release request function; an acquisition unit that acquires the print job from the print server after the hold state of the print job has been released; and a printing unit that performs printing in accordance with the acquired print job.

[0006] According to the above embodiment, reservation printing can be performed regardless of whether the login function is enabled.

[0007] Other features and advantages of the present invention will become apparent from the following description taken in conjunction with the accompanying drawings, in which the same or similar elements are designated by the same reference numerals.

[0008] The accompanying drawings are incorporated into and constitute a part of the specification, illustrate embodiments of the present invention, and together with the description, serve to explain the principles of the present invention. A block diagram illustrating an example configuration of a printing system according to some embodiments. A block diagram illustrating an example hardware configuration of a computer according to some embodiments. A block diagram illustrating an example hardware configuration of a printing device according to some embodiments. A block diagram illustrating an example hardware configuration of a printing device according to some embodiments. A sequence diagram illustrating an example operation of badge release according to some embodiments. A diagram illustrating an example message used in some embodiments. A diagram illustrating an example change in a list of print jobs according to some embodiments. A diagram illustrating an example message used in some embodiments. A diagram illustrating an example message used in some embodiments. A diagram illustrating an example message used in some embodiments. A schematic diagram illustrating an example screen displayed in some embodiments. A sequence diagram illustrating an example operation of mobile release according to some embodiments. A diagram illustrating an example message used in some embodiments. A diagram illustrating an example change in a list of print jobs according to some embodiments. A diagram illustrating an example message used in some embodiments. A diagram illustrating an example message used in some embodiments. A flow diagram illustrating an example operation of a printing device according to some embodiments. A schematic diagram illustrating an example screen displayed in some embodiments.

[0009] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the invention claimed. Although multiple features are described in the embodiments, not all of these multiple features are necessarily essential to the invention, and multiple features may be combined arbitrarily. Furthermore, in the accompanying drawings, the same reference numerals are used to designate the same or similar components, and redundant explanations will be omitted.

[0010] [Configuration Example of Printing System] An example configuration of a printing system 100 according to some embodiments will be described with reference to Fig. 1 . 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 one of the printing device 103 and the printing device 104. Furthermore, the printing system 100 may include components not shown in Fig. 1 .

[0011] Each component of the printing system 100 is connected to a network 106. The print server 101 may be able to communicate 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. 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 wireless sections and / or wired sections.

[0012] The print server 101 provides a print service that transmits a print job to a printing device (e.g., the printing device 103) in accordance with 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 print jobs 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.

[0013] 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). A 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.

[0014] 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 CPS may also be called a client or a client terminal. Printing performed by submitting a print job to a logical printer may also be called cloud printing, remote printing, or remote printing.

[0015] The printing device 103 has a printing function that performs printing according to a print job. The printing may be performed on a sheet-like recording medium such as paper, or may be performed by 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.

[0016] 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. A printing device 103 with the login function may authenticate a 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.

[0017] The printing device 103 supports reservation printing. Reservation printing may refer to 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 on 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 refer to a function that requests the print server 101 to release a print job held in the print server 101 from a reserved state in response to an instruction from the user. The pull print function may also be referred to as a release request function. In the following description, the release of a print job from a reserved state by a user operating the printing device 103 is referred to as a badge release. Badge release may also be referred to as a local release, direct release, printer release, etc. The print server 101 releases a print job from a reserved state based on a request from the printing device 103. To prevent another user from starting printing of a print job submitted by the printing device 103, the printing device 103 may allow a user to perform badge release, provided that the user is logged in to the printing device 103.

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

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

[0020] 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.

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

[0022] 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 or her mobile terminal 105. The user then logs in to 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 also be used to submit a print job to the print server 101.

[0023] [Example of Hardware Configuration of Computer] An example of the 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 the print server 101, the information processing device 102, or the mobile terminal 105. The computer 200 may have the components shown in Fig. 2.

[0024] 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 that 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 that stores programs and data used in the processing by the CPU 201. The storage device 204 is a non-volatile storage device that 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. Operations by the computer 200 may be realized by the CPU 201 executing programs read from the storage device 204 to the RAM 202.

[0025] 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 devices external to the computer 200. The CPU 201, RAM 202, ROM 203, storage device 204, input I / F 205, output I / F 206, and network I / F 207 are each 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 .

[0026] [Example of Hardware Configuration of Printing Device] Referring to FIG. 3A , an example of the hardware configuration of the printing device 103 according to some embodiments will be described. The printing device 103 may have the components shown in FIG. 3A . 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 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, and setting information) used in processing by the CPU 301. The storage device 304 may be, for example, an HDD or SSD. The storage device 304 may also be referred to as 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.

[0027] 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.

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

[0029] 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, for example, with 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.

[0030] 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, RAM 302, ROM 303, storage device 304, printer I / F 305, scanner I / F 306, operation unit I / F 307, and 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 username and password entered using the operation unit 340. Alternatively or additionally, the authentication unit 309 may authenticate a user based on biometric information of the user (e.g., fingerprint, iris, facial shape, etc.) acquired using a sensor. Alternatively or additionally, the authentication unit 309 may authenticate a user by reading information from a personal identification card held by the user.

[0031] 3B , an example 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. 3B . 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.

[0032] [Overall Processing Sequence for Badge Release] The overall operation of the printing system 100 regarding the processing for executing badge release will be described with reference to Figure 4. Badge release may be executable when a printing instruction is given to a printing device that has a login function and a pull print function. Because the printing device 103 has the login function and the pull print function, badge release can be executed when a user instructs the printing device 103 to print. On the other hand, because 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 following describes the case where a printing instruction is given to the printing device 103.

[0033] In S401, the printing device 103 transmits its capability information 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, 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 a pull print function.

[0034] Information indicating 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 compliant with IPP. In message 500, the attribute "pull-print-supported" is set to "True," indicating that the printing device 103 has pull print capability. In response to receiving message 500, the print server 101 may respond with message 501 shown in Fig. 5. Message 501 represents an Update-Output-Device-Attributes Response operation compliant with IPP.

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

[0036] In S403, a user of the information processing device 102 (hereinafter referred to as 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 designated by the user may be associated with only 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 later designate which printing device to use for printing.

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

[0038] In S405, the print server 101 assigns an identification number to the print job received in S404 and saves the print job in storage (e.g., the storage device 204) of the print server 101. The print server 101 also updates a job list for managing print jobs stored in the print server 101.

[0039] The print server 101 processes the print job received in S404 by reservation printing based on the determination that the printing device 103 has the 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 also be based on whether reservation printing has been specified by the user. For example, the print server 101 may not process the print job by reservation printing if reservation printing has not been specified by the user.

[0040] On the other hand, the print server 101 determines that the printing device 103 does not have the pull print function and therefore does not process the print job received in S404 by reservation printing. 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 performed in accordance with the print job).

[0041] An example of the job list 600 after updating in S405 will be described with reference to FIG. 6 . Assume that in S405, a newly acquired print job is assigned a "job-id" of "3." The print server 101 then 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 on hold. The job list 600 also manages a print job previously submitted by the same user (Smith) that is on hold (a print job with a "job-id" of "2"). The job list 600 also manages a print job previously submitted by another user (Alice) that is on hold (a print job with a "job-id" of "1"). The print server 101 may manage print jobs by associating them 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 apparatus 102 to the print server 101 together with the print job.

[0042] In S406, the 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 password.

[0043] In S407, the printing device 103 performs a login process. Specifically, the printing device 103 authenticates the user by determining whether the information entered 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 authorization to use the printing device 103. The printing device 103 may then identify the user's cloud account name based on the username entered by the user in S406. The association between the username 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 user (Smith)'s cloud account name is "RobertSmith@example.com."

[0044] In response to the user's successful login, in step S408, the printing device 103 requests from the print server 101 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 currently 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 set to "True," indicating that a list of print jobs related to the user specified by the attribute "Requesting-user-name" or the attribute "Requesting-user-uri" is being requested. In the message 700, the attribute "Requesting-user-name" specifies the username "Smith," and the attribute "Requesting-user-uri" specifies the user's cloud account name "RobertSmith@example.com." The message 700 may specify both the attribute "Requesting-user-name" and the attribute "Requesting-user-uri," or may specify only one of them. Alternatively or in addition, the message 700 may include other information that allows the print server 101 to uniquely identify the user.

[0045] 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 response list by extracting, from the job list 600, information on print jobs (print jobs with a "job-id" of "2" or "3") associated with "RobertSmith@example.com" specified in the attribute "Requesting-user-uri." This list response may be sent using a message 701 shown in FIG. 7. The message 701 represents a Get-Jobs Response operation compliant with IPP. The message 701 includes information on print jobs with a "job-id" of "2" or "3."

[0046] In S410, the printing apparatus 103 displays the list information received in S409 on the operation unit 340. In S411, the user specifies the print job that the user wants to print from one or more print jobs (two print jobs in this example) shown in the list, and instructs the user to start printing.

[0047] In S412, the printing device 103 requests information about 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 complies with 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.

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

[0049] In S413, the printing device 103 requests 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 900 shown in FIG. 9 . The message 900 represents an Acknowledge-Job Request operation that complies with 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.

[0050] In S414, the print server 101 releases the standby 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 whose "job-id" is "2" have been 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 compliant with IPP.

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

[0052] 10 , an example of a screen displayed on the operation unit 340 of the printing device 103 during badge release will be described. In S407, the printing device 103 prompts the user to log in to the printing device 103 by displaying 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 screen 1001 on the operation unit 340. Screen 1001 indicates that Smith is currently logged in.

[0053] 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.

[0054] [Overall Processing Sequence of Mobile Release] With reference to FIG. 11 , the overall operation of the printing system 100 related to the processing for executing mobile release will be described. Mobile release may be executable when a print instruction is issued to a printing device that the print server 101 recognizes as having a pull print function. Because the printing device 103 has the pull print function, mobile release can be executed when a user issues a print instruction to the printing device 103. On the other hand, the printing device 104 does not have the pull print function. However, as described below, the printing device 104 notifies the print server 101 that it has a print function, even though it does not have the pull print function. As a result, the print server 101 recognizes the printing device 104 as having the pull print function. Therefore, mobile release can be executed even when a user issues a print instruction to the printing device 104. The following describes a case where a print instruction is issued to the printing device 103. The same description applies to a case where a print instruction is issued to the printing device 104.

[0055] 4, the operations of S401 to S405 may be the same as those of Fig. 4. When the operations of Fig. 11 are performed 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.

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

[0057] 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 authorization to use the printing device 103.

[0058] In response to the user's successful login, in S1103, the mobile terminal 105 requests a list of print jobs associated with the user currently logged in to the mobile terminal 105 from the print server 101. 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 description of the message 700 may be the same as that described above, and therefore a duplicate description will be omitted.

[0059] 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 processing in S1104 may be the same as the processing in S409 described above, and therefore a duplicated description will be omitted.

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

[0061] In S1107, the mobile terminal 105 requests the print server 101 to release the print job specified by the user in S1106 (e.g., the print job with "job-id" of "2") from the hold state. 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 compliant with 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 including the attribute "job-release-type" 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 .

[0062] 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 a "job-id" of "2" have been updated to "pending" and "job-fetchable," respectively. These attribute values ​​indicate that the printing device can acquire the print job with a "job-id" of "2." Thereafter, 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.

[0063] In S1109, the printing device 103 sends 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 whether there is a print job available for the printing device 103 to acquire. In other words, the printing device 103 inquires of the print server 101 as to whether there is a print job available for the printing device 103 to acquire. The printing device 103 may periodically send the event confirmation request to the print server 101. The event confirmation request may be sent using a message 1400 shown in FIG. 14. Message 1400 represents a Get-Notification Request operation compliant with IPP.

[0064] At this point, the print job with "job-id" "2" has been released from hold based on a request from a device other than the printing device 103 (in this example, the mobile terminal 105). The print server 101 then responds that there is a print job available for the printing device 103 to acquire. The 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.

[0065] If there are print jobs that the printing device 103 can acquire, in S1110 the printing device 103 requests a list of print jobs that the printing device 103 can acquire from the print server 101. 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 about print jobs related to all users is being requested. In addition, in the message 1500, the attribute "which-jobs" is "fetchable", which indicates that information about print jobs that the printing device 103 can acquire is being requested. The print server 101 responds to the request in S1110 with a message 701.

[0066] In S1111, the printing device 103 requests the print server 101 to retrieve the print job included in the list acquired in S1110 (for example, the 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., the Fetch-Job Request operation).

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

[0068] [Example of Printing Device Operation] With reference to Figure 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 Figure 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 Figure 16 may be performed by a dedicated integrated circuit such as an ASIC. The method of Figure 16 may be started in response to the printing device 103 being started.

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

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

[0071] The pull print notification settings 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. 17A. The screen 1700 may be displayed on the operation unit 340 of the printing device 103, for example.

[0072] 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 the 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 the user of the printing device 103 selecting the OFF button using the operation unit 340.

[0073] The screen 1700 may also be used by the user to set whether to enable the 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 the 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 the 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.

[0074] 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 the printing device 103, a password for logging in to the printing device 103, and a cloud account name. The cloud account name may be used for badge release, as described above.

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

[0076] In step S1602, if the printing device 103 determines 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 message 510 shown in FIG. 5. Message 510 represents an Update-Output-Device-Attributes Request operation compliant with IPP. In message 510, the attribute "pull-print-supported" is set to "False," 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 message 520 shown in FIG. 5. Message 520 represents an Update-Output-Device-Attributes Request operation compliant with IPP. In message 520, the attribute "pull-print-supported" is not included, indicating that the printing device 103 does not have the pull print function.

[0077] In S1604, the printing apparatus 103 determines whether the pull print notification settings have been changed. If the printing apparatus 103 determines that the pull print notification settings have been changed (YES in S1604), it transitions the process to S1601, and otherwise (NO in S1604) it repeats S1604. If it determines that the pull print notification settings have been changed, the printing apparatus 103 notifies the print server 101 whether the printing apparatus 103 has a pull print function based on the changed settings.

[0078] In the operation of FIG. 16 , it is possible to separately set whether to enable the pull print notification and whether to enable the login function. Therefore, the printing device 103 notifies the print server 101 that it has the pull print function, regardless of whether the login function is enabled, based on the setting to notify 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 it has the pull print function, regardless of whether the login function is enabled, based on the setting not to 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. If the pull print notification is disabled and the login function is disabled, the user cannot perform either badge release or mobile release.

[0079] 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 the 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.

[0080] As described above, the printing device 104 does not have a pull print function. Therefore, in the badge release method of FIG. 4 , the printing device 104 cannot request the print server 101 to release the print job from the hold state in step S412. However, even though the printing device 104 does not have a pull print function, it can notify the print server 101 that it has a 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, mobile release can be performed.

[0081] The settings for the pull print notification on 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. 17B . The screen 1710 may be displayed on a display unit of a device other than the printing device 104 (e.g., the information processing device 102 or the mobile terminal 105). 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.

[0082] 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. Because the printing device 104 does not have a login function, screen 1710 does not include a graphical object for enabling the login function.

[0083] 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.

[0084] The present invention can also be realized by a process in which a program that realizes one or more 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., an ASIC) that realizes one or more functions.

[0085] The invention is not limited to the above-described embodiments, and various changes and modifications can be made 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.

[0086] This application claims priority based on Japanese Patent Application No. 2023-098732, filed on June 15, 2023, the entire contents of which are incorporated herein by reference.

Claims

1. 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 is able to make a release request to 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 the printing device or 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, wherein the printing device comprises: a login means for providing a login function that allows a user to log in to the printing device; a setting means for making a setting to enable the login function; a notification means for notifying the print server that the printing device is able to make the release request based on the setting that the login function is enabled; an acquisition means for acquiring the print job from the print server after the held state of the print job has been released; and a printing means for executing printing in accordance with the acquired print job.

2. A printing system as described in claim 1, wherein the notification means does not notify the print server that the printing device is capable of making the release request based on a setting not to notify the print server that the printing device is capable of making the release request, regardless of a setting as to whether or not the login function is enabled.

3. The printing system according to claim 1 or 2, wherein the acquisition means further acquires, from the print server, information on a print job associated with a user currently logged in to the printing device.

4. The printing system according to any one of claims 1 to 3, wherein said holding means does not hold said print job in a hold state based on a determination that said printing device is not capable of accepting said release request.

5. A printing system as described in any one of claims 1 to 4, wherein the printing device further comprises an inquiry means for inquiring of the print server whether there is a print job that the printing device can acquire, and 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. A printing system according to any one of claims 1 to 6, wherein said notification means notifies said print server that said printing device is capable of making said release request by using a message conforming to the Internet Printing Protocol.

8. A printing system as described in any one of claims 1 to 7, wherein the setting means performs a setting to notify the print server that the printing device is capable of making the release request, and the notification means notifies the print server that the printing device is capable of making the release request, further based on the setting to notify the print server that the printing device is capable of making the release request.

9. A printing device comprising: a login means for providing a login function for logging a user into the printing device; a setting means for making a setting to enable the login function; a notification means for notifying the print server that the printing device is capable of making a release request to the print server to release a print job held by the print server based on the setting that the login function is enabled; an acquisition means for acquiring the print job from the print server after the print job has been released from the held state; and a printing means for executing printing in accordance with the acquired print job.

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

11. A control method for a printing device, comprising: a login step of providing a login function that allows a user to log in to the printing device; a setting step of making a setting to enable the login function; a notification step of notifying the print server that the printing device is capable of making a release request to the print server to release a print job held by the print server based on the setting that the login function is enabled; an acquisition step of acquiring the print job from the print server after the print job has been released from the held state; and a printing step of executing printing in accordance with the acquired print job.

Images