Printing device, control method for printing device, program, and cloud printing system

Abstract

A printing device according to the present invention communicates with a cloud printing server that provides a cloud printing service. The printing device includes a registration means for registering the printing device at the cloud printing server and a transmission means that transmits printer information for the registered printing device to the cloud printing server. The printer information that is transmitted by the transmission means includes information in which information about the remaining amount of a recording material for the printing device is defined in a first format and information in which information about the remaining amount of the recording material for the printing device is defined in a second format.

Description

Printing device, printing device control method, program, and cloud print system

[0001] The present invention relates to a printing device, a printing device control method, a program, and a cloud printing system in a cloud printing service.

[0002] In conventional printing services, printing is achieved by a user directly sending a print job from a client terminal such as a PC to a multifunction peripheral. In recent years, however, a cloud print service (see Patent Literature 1) has been proposed that utilizes cloud services provided over the Internet.

[0003] JP 2023-71252 A

[0004] The printing device 101, which supports local printing as described later in FIG. 4, transmits a printer information response 404 to the client terminal 100. Toner information is set in the printer information response 404 using attribute values ​​that can be interpreted by the client terminal 100. The client terminal 100 interprets the toner information and displays the toner information of the printing device 101.

[0005] On the other hand, the printing device 101 that supports cloud printing in FIG. 3 (described later) transmits printer information 321 to the cloud print service 200. Toner information is set in the printer information 321 using attribute values ​​that can be interpreted by the cloud print service 200. The attribute values ​​that can be interpreted by the cloud print service 200 may differ from the attribute values ​​that can be interpreted by the client terminal 100. The client terminal 100 receives the printer information 321 that includes toner information from the cloud print service 200. However, if the client terminal 100 cannot interpret the toner information from the cloud print service 200, there is a problem in that it cannot display the toner information of the printing device 101.

[0006] In order to solve at least one of the above problems, the present invention provides a printing device that can display toner information on a client terminal even if the printing device supports local printing and cloud printing.

[0007] A printing device that communicates with a cloud print server that provides a cloud print service, the printing device having a registration means for registering the printing device with the cloud print server and a transmission means for transmitting printer information of the registered printing device to the cloud print server, wherein the transmission means transmits the printer information including information regarding the remaining amount of recording material of the printing device defined in a first format and information regarding the remaining amount of recording material of the printing device defined in a second format.

[0008] According to the present invention, it is possible to display toner information for cloud printing on the client terminal 100 for the printing device 101 that supports local printing and cloud printing.

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

[0010] The accompanying drawings are incorporated into and constitute a part of the specification, illustrate embodiments of the present invention, and together with the description are used to explain the principles of the present invention.

[0023] Figure 1 is a sequence diagram of cloud print registration for a printing device. Figure 2 is a sequence diagram of cloud print registration for a printing device. Figure 3 is a sequence diagram of cloud print startup for a printing device. Figure 4 is a sequence diagram of cloud print printing for a printing device. Figure 5 is a sequence diagram of local print processing. An example of a local printer information display screen displayed on a client terminal. An example of a cloud printer information display screen displayed on a client terminal. A hardware configuration diagram of a printing device. A software configuration diagram of a printing device. A diagram illustrating the operation panel of a printing device. A diagram illustrating standard toner attributes of a printing device. A diagram illustrating extended toner attributes of a printing device. A diagram illustrating an AirPrint setting screen for a printing device. A flowchart of when a printing device starts up. A flowchart of when a printing device receives a printer information request for local print. A flowchart of when a client terminal displays local printer information. A flowchart of when a client terminal displays cloud printer information. An example of an information display screen for a local printer and a cloud printer displayed on a client terminal. A flowchart of when a client terminal displays local printer information in an embodiment. A flowchart of when a client terminal displays cloud printer information in an embodiment.

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

[0012] The cloud print operation sequence will be described with reference to Figures 1A to 3. Figures 1A and 1B are diagrams showing the cloud print registration sequence of a printing device.

[0013] The printing device 101 is assumed to support a cloud print function and a Web UI function for operating the printing device 101. The client terminal 100 is assumed to support a cloud print client function and a Web UI client for operating the Web UI. The cloud device registration service 102 is assumed to be a service on the Internet provided by a cloud print server.

[0014] First, a user uses a Web UI client of the client terminal 100 to send a cloud device registration request 110 to the printing apparatus 101 via the Web UI. Upon receiving the cloud device registration request 110, the printing apparatus 101 sends a device code generation request 111 to the cloud device registration service 102. Upon receiving the device code generation request 111, the cloud device registration service 102 sends a device code generation response 112 to the printing apparatus 101. The device code generation response 112 includes a device code 130, a user code 131, and a verification URL 132 generated by the cloud device registration service 102. Upon receiving the device code generation response 112, the printing apparatus 101 sends a cloud device registration response 113 to the client terminal 100. The cloud device registration response 113 includes the user code 131 and the verification URL 132 generated by the cloud device registration service 102.

[0015] When the client terminal 100 receives the cloud device registration response 113, it displays a user code 131 and a verification URL 132 on the Web UI client. The user operates the Web UI client to access the displayed verification URL 132. Then, by inputting a cloud account 133 and the user code 131, it transmits a cloud device registration approval request 114 to the cloud device registration service 102. When the cloud device registration service 102 receives the cloud device registration approval request 114, it associates the administrator of the printing device 101 being registered as the cloud account 133 and manages it as having been approved for registration. Then, the cloud device registration service 102 transmits a cloud device registration approval response 115 to the client terminal 100.

[0016] The printing device 101 sends an access token request 116 to the cloud device registration service 102. The access token request 116 includes a device code 130 generated by the cloud device registration service 102. Upon receiving the access token request 116, the cloud device registration service 102 generates an access token 134. This access token 134 is used in subsequent registration processes and serves as proof of authorization for the registration processes. The cloud device registration service 102 sends an access token response 117 to the printing device 101. The access token response 117 includes the access token 134 generated by the cloud device registration service 102.

[0017] The printing device 101 transmits a registration request 118 to the cloud device registration service 102. The registration request 118 includes a device name 135 and a device type 136. An access token 134 is also added to the HTTP header of the registration request 118. The device name 135 is the device name set in the printing device 101. The device type 136 indicates the device type of the printing device 101, and is set to "printer" in the cloud print service 200. The cloud print service 200 is assumed to be an Internet service provided by a cloud print server. Upon receiving the registration request 118, the cloud device registration service 102 determines whether the access token 134 is the token that the cloud device registration service 102 itself responded to in the access token response 117. This allows the cloud device registration service 102 to confirm whether the transmitted registration request 118 is authorized. If the cloud device registration service 102 determines that the registration request is authorized as a result of the above confirmation, it transmits a registration response 119 to the printing device 101 and starts the registration process for the printing device 101.

[0018] The printing device 101 sends a registration status request 120 to the cloud device registration service 102. The registration status request 120 also has an access token 134 added to its HTTP header. When the cloud device registration service 102 receives the registration status request 120, it checks the access token 134 in the same way as when it received the registration request 118, and if it determines that the registration request is authorized, it continues the following processing. If registration is complete, the cloud device registration service 102 sends a registration status response 121 to the printing device 101. The access token response 117 includes a print service URL 137, a notification service URL 138, and a print service resource ID 139. The print service URL 137 is endpoint information indicating the endpoint of the cloud print service 200. The notification service URL 138 is endpoint information indicating the endpoint of the cloud print event notification service 201. The print service resource ID 139 is unique information issued by the cloud device registration service to obtain an access token for using the print service. The cloud print event notification service 201 is assumed to be a service on the Internet provided by a cloud print server.

[0019] Next, the printing device 101 obtains an access token for using the cloud print service 200. The printing device 101 transmits a Nonce request 122 to the cloud device registration service 102. A Nonce is random data that is valid only once and is used for authentication. Upon receiving the Nonce request 122, the cloud device registration service 102 generates a Nonce 140 and transmits a Nonce response 123 to the printing device 101. The Nonce response 123 includes the Nonce 140.

[0020] When the printing device 101 receives the Nonce 140 in the Nonce response 123, it generates a JasonWebToken (JWT) 141. The JWT is a signature added to Base64-encoded authentication information expressed in JSON format. The printing device 101 then transmits an access token request 124 to the cloud device registration service 102. The access token request 124 includes the print service resource ID 139 received from the cloud device registration service 102 and the JWT 141 generated by the printing device 101.

[0021] When the cloud device registration service 102 receives the access token request 124, it verifies the generated Nonce 140 and the JWT 141 received from the printing device 101 to authenticate the printing device 101. The cloud device registration service 102 generates an access token 142 based on the print service resource ID 139 included in the access token request 124 and sends an access token response 125 to the printing device 101. The access token response 125 includes the access token 142. At this point, the cloud device registration process of the printing device 101 is completed.

[0022] Next, a description will be given of Fig. 2. Fig. 2 is a cloud print startup sequence diagram for the printing apparatus 101. The description will be given assuming that communication in this sequence uses the Internet Printing Protocol (IPP), which is a printing protocol using HTTP.

[0023] The printing device 101 sends a printer information transmission request 210 to the cloud print service 200. The IPP operation is Update-Output-Device-Attributes. The printer information transmission request 210 includes printer information 220. The printer information 220 is information expressed by printer-description, which is an IPP attribute group. The printer information 220 also includes toner (recording material) information of the printing device 101.

[0024] The printing apparatus 101 sends a job information send request 211 to the cloud print service 200. The IPP operation is Update-Active-Jobs. The job information send request 211 includes job information 221. The job information 221 includes job-ids and output-device-job-states, which are IPP attributes. job-ids indicates the ID of the job, and output-device-job-states indicates the state of the job.

[0025] The printing device 101 sends an event notification registration request 212 to the cloud print event notification service 201. The IPP operation is Create-Printer-Subscription. The event notification registration request 212 includes a job reception event 222 that indicates the type of event to be notified. The job reception event 222 includes job-fetchable, which is an IPP attribute. job-fetchable is an event type that indicates that a receivable job exists in the cloud print service.

[0026] The printing apparatus 101 sends an event acquisition request 213 to the cloud print event notification service 201. The IPP operation is Get-Notifications. The event acquisition request 213 includes a job reception event 222 as the type of event to be acquired. The job reception event 222 includes job-fetchable, which is an IPP attribute.

[0027] Next, a description will be given of Fig. 3. Fig. 3 is a sequence diagram of cloud print by the printing apparatus 101. The description will be given assuming that communication by the printing apparatus 101 in this sequence uses IPP, which is a printing protocol using HTTP.

[0028] The client terminal 100 sends a cloud printer information request 300 to the cloud print service 200. The cloud printer information request 300 includes a cloud account 133. Upon receiving the cloud printer information request 300, the cloud print service 200 sends a cloud printer information response 301 to the client terminal 100. The cloud printer information response 301 includes a cloud printer ID 320 that the cloud account 133 is permitted to use and printer information 321 that indicates information about that printer. The printer information 321 also includes toner (recording material) information for the printing device 101.

[0029] In response to a print operation by a user, the client terminal 100 transmits a print request 302 to the cloud print service 200. The print request 302 includes a cloud printer ID 320 that identifies the printer, print data 322, and a cloud account 133 that identifies the user.

[0030] When the cloud print event notification service 201 detects that a print job addressed to the printing device 101 has been generated in the cloud print service 200, it transmits an event response 303 to the printing device 101. The event response 303 includes a job reception event 323 as the event type. The IPP operation is Get-Notifications Response. The job reception event 323 includes job-fetchable, which is an IPP attribute.

[0031] When the printing device 101 receives the event response 303, it sends a print job request 304 to the cloud print service 200. The IPP operation is Get-Jobs. When the cloud print service 200 receives the print job request 304, it sends a print job response 305 to the printing device 101. The IPP operation is Get-Jobs Response. The print job response 305 includes a job ID 324 that indicates a downloadable job.

[0032] When the printing apparatus 101 receives the print job response 305, it sends a print job attribute request 306 to the cloud print service 200. The IPP operation is Fetch-Job. The print job attribute request 306 includes a job ID 324 that specifies the target job.

[0033] When the cloud print service 200 receives the print job attribute request 306, it sends a print job attribute response 307 to the printing apparatus 101. The IPP operation is Fetch-Job Response. The print job attribute response 307 includes job attributes 325 of the job ID 324. The job attributes 325 are information expressed in Job-Template-attributes, which is an IPP attribute group.

[0034] When the printing apparatus 101 receives the print job attribute response 307, it sends a print job data request 308 to the cloud print service 200. The IPP operation is Fetch-Document. The print job data request 308 includes a job ID 324 that specifies the target job.

[0035] When the cloud print service 200 receives the print job data request 308, it transmits a print job data response 309 to the printing apparatus 101. The IPP operation is Fetch-Document Response. The print job data response 309 includes job data 326 of the job ID 324.

[0036] So far, the operational sequence of cloud printing has been explained. Meanwhile, the printing device 101 has also conventionally supported a local printing function. Local printing will be explained below. FIG. 4 is a processing sequence diagram of local printing in which a print job is sent directly from a conventional client terminal to the printing device. The protocol used between the client terminal and the printing device is IPP.

[0037] The client terminal 100 transmits a printer search request 401 to search for a printer on the network. Upon receiving the printer search request 401, the printing device 101 transmits a printer search response 402 to the client terminal 100. The client terminal 100 discovers the printing device 101 by receiving the printer search response 402.

[0038] Next, the client terminal 100 sends a printer information request 403 to the discovered printing device 101. When the printing device 101 receives the printer information request 403, it sends a printer information response 404 to the client terminal 100. The printer information response 404 includes printer information 412. The printer information 412 also includes toner (recording material) information of the printing device 101. The printer information 412 also includes capability information that indicates the capabilities of the printing device 101.

[0039] This allows the client terminal 100 to obtain capability information of the printing device 101. This capability information also includes information indicating whether the printing device 101 supports printing from the client terminal 100. If the client terminal 100 determines that the capability information of the printing device 101 supports printing from the client terminal 100, it performs control such as displaying the printing device 101 in a printer selection list. This allows the user to send a print job from the client terminal 100 to the printing device 101.

[0040] Then, when the user performs an operation to send a print job to the printing device 101, the client terminal 100 sends a print request 405 to the printing device 101. The print request 405 also includes print data 413. When the printing device 101 receives the print request 405, it sends a print response 406 to the client terminal 100. The printing device 101 also prints the print data 413 received in the print request 405.

[0041] The client terminal 100 uses the printer information 412 of the local printer acquired by the sequence of Fig. 4 to display information about the printing device 101 on the display panel of the client terminal 100. Fig. 5 shows an example of a display screen of the printer information of the local printer displayed on the client terminal 100.

[0042] A name area 501 displays the name of the printing device 101. A location area 502 displays the location of the printing device 101. A model area 503 displays the model of the printing device 101.

[0043] A supply information display area 504 displays toner (recording material) information for the printing device 101. A field 505 displays the name and remaining amount of black toner for the printing device 101. A field 506 displays the name and remaining amount of cyan toner for the printing device 101. A field 507 displays the name and remaining amount of magenta toner for the printing device 101. A field 508 displays the name and remaining amount of yellow toner for the printing device 101. All of this information is included in the printer information 412.

[0044] 3, the client terminal 100 displays information about the printing device 101 on the display panel of the client terminal 100. FIG. 6 shows an example of a cloud printer information display screen displayed on the client terminal 100.

[0045] Areas 501 to 503 are the same as those described in FIG. 5. In FIG. 5, the supply information display area 504 displays toner information for the printing device 101. In FIG. 6, the supply information display area 504 cannot display toner information and displays "No information available." This is because the printer information 321 sent via the cloud may not include toner information supported by the client terminal 100. This can occur even if both the local print system and the cloud print system are IPP-based, because the IPP attributes used by the two systems are different.

[0046] In the embodiment, the cloud device registration service 102, the cloud print service 200, and the cloud print event notification service 201 may be services implemented by different servers. Also, one service may be implemented by multiple servers. The cloud print server may be one server or multiple servers, and the term "server system" refers to a device that provides each service and is configured by one or multiple servers.

[0047] Furthermore, "send to the cloud print service 200" is synonymous with "send to the cloud print server," and "receive from the cloud print service 200" is synonymous with "receive from the cloud print server." Similarly, the cloud device registration service 102 and the cloud print event notification service 201 are synonymous with "cloud print server." Furthermore, a system including the client terminal 100, printing device 101, and cloud print server is called a cloud print system.

[0048] First, the hardware configuration of the printing device 101 according to the present invention will be described with reference to Fig. 7. The printing device 101 includes a control unit 701, a printer 707, a scanner 709, and an operation panel 711. The control unit 701 includes a CPU 702, a RAM 703, a ROM 704, an HDD 714, a printer I / F 706, a scanner I / F 708, an operation panel I / F 710, and a network I / F 712. The blocks within the control unit 701 are connected via a system bus 705.

[0049] A control unit 701 including a CPU 702 controls the overall operation of the printing apparatus 101. The CPU 702 reads control programs stored in a ROM 704 and performs various types of control, such as communication control. A RAM 703 is used as a temporary storage area, such as the main memory and work area, of the CPU 701. A HDD 714 stores data, various programs, and various information tables.

[0050] The printer I / F 706 serves as an interface for outputting an image signal to a printer 707 (printer engine). The scanner I / F 708 serves as an interface for inputting a read image signal from a scanner 709 (scanner engine). The CPU 702 processes the image signal input from the scanner I / F 708 and outputs it to the printer I / F 706 as a print image signal.

[0051] The operation panel I / F 710 connects the operation panel 711 to the control unit 701. The operation panel 711 is equipped with a liquid crystal display unit with touch panel functionality, a keyboard, and the like. The network I / F 712 transmits information to external terminals such as the client terminal 100 and the cloud print service 200, and receives various types of information from these external devices. The blocks within the control unit 701 are connected via a system bus 705.

[0052] The software configuration of the printing apparatus 101 will be described with reference to Fig. 8. Each functional unit shown in Fig. 8 is realized by the CPU 302 of the printing apparatus 101 reading a control program stored in the ROM 704 into the RAM 703 and executing it. The software of the printing apparatus 101 includes an operation control unit 800, a cloud print service registration control unit 801, a cloud print printing control unit 802, a cloud print job information management unit 803, a cloud print event control unit 804, a cloud print device information management unit 805, a storage unit 806, an image processing unit 807, a print processing unit 808, a local print search control unit 809, a local print printing control unit 810, a local print device information management unit 812, and a toner information management unit 813.

[0053] The operation control unit 800 controls the operation panel 711. It displays an operation menu on the operation panel 711 and waits for instructions to be input by the user, notifies other functional units of the received instructions, and displays the instruction results on the operation panel 711. The cloud print service registration control unit 801 controls the process of registering the printing device 101 with the cloud device registration service 102 in response to a cloud device registration request 110 received from the client terminal 100.

[0054] The cloud print control unit 802 transfers the print data 134 received from the cloud print service 200 to the image processing unit 807. The image processing unit 807 performs processing to render the print job into image data for printing.

[0055] A print processing unit 808 performs processing to print the image data rendered by the image processing unit 807. A cloud print job information management unit 803 manages job information of the printing apparatus 101 and notifies the cloud print service 200 of the information.

[0056] A cloud print event control unit 804 controls event transmission and event reception processing between the printing apparatus 101 and the cloud print event notification service 201. A cloud print device information management unit 805 manages device information of the printing apparatus 101 and notifies the cloud print service 200 of the device information.

[0057] In response to instructions from other functional units, the storage unit 806 stores designated data in the ROM 704 or the HDD 714, or reads out stored data. Examples of data managed by the storage unit 806 include ID information for identifying a device and QR Code (registered trademark) image information.

[0058] A local print search control unit 809 receives a printer search request 401 from the client terminal 100 and controls the process of transmitting a printer search response 402. A local print printing control unit 810 transfers print data 413 transmitted from the client terminal 100 in the print request 405 to the image processing unit 807.

[0059] A local print job information management unit 811 manages job information received by the printing apparatus 101 via local printing and notifies the client terminal 100. A local print device information management unit 812 manages device information of the printing apparatus 101 and notifies the client terminal 100.

[0060] The operation panel 711 of the printing apparatus 101 will be described with reference to Fig. 9. The operation panel 711 is provided with a display panel 905, directional keys 906, an OK key 907, a numeric keypad 908, a black and white button 909, a color button 910, a stop button 911, a menu button 912, and a status check / cancel button 913. The display panel 905 is a display panel that uses an LCD or the like. A copy button 901, a fax button 902, and a scan button 903 are displayed on the display panel 905.

[0061] The copy button 901 is a button that is operated when making a copy using the printing device 101, and operating the copy button 901 displays a copy operation screen on the display panel 905. The fax button 902 is a button that is operated when making a fax using the printing device 101, and operating the fax button 902 displays a fax operation screen on the display panel 905. The scan button 903 is a button that is operated when making a scan using the printing device 101, and operating the scan button 903 displays a scan operation screen on the display panel 905. The display panel 905 also displays a dialog box for interacting with the user. The display panel 905 also displays QR code images and the like.

[0062] The numeric keypad 908 is used to input numbers, etc. The OK key 907 is used when deciding the display content of the display panel 905, etc. The directional keys 906 are used when selecting a menu, etc., displayed on the display panel 905. The black and white button 909 and color button 910 are used when executing black and white copying and color copying, respectively. The stop button 911 is used to stop processing. The menu button 912 is used to display a menu screen for setting the printing device 101. The status check / cancel button 913 is used when checking the status of the printing device 101, such as a list of print jobs received by the printing device 101.

[0063] The standard toner attributes of the printing device 101 will be described with reference to FIG. 10. FIG. 10 shows the standard toner attributes of the Internet Printing Protocol (IPP). Toner is one form of recording material. The recording material may also be ink. The IETF Printer MIB v2 [RFC3805] defines the MIB objects prtMarkerSuppliesTable and prtMarkerColorantTable. The printer-supply attribute 1001 in FIG. 10 is the same as that set in these MIB objects prtMarkerSuppliesTable and prtMarkerColorantTable.

[0064] The same number of pieces of information as the number of toners are set in a list as the value of the printer-supply attribute 1001. For each piece of information, type, max capacity, level, class, unit, and colorant name are set.

[0065] "type" indicates the type of colorant (recording material), and in this embodiment, "toner" is set to indicate toner. "maxcapacity" indicates the maximum capacity of the colorant, and in this embodiment, "100" is set to indicate 100%. "level" indicates the current capacity of the colorant, and in this embodiment, "100" is set to indicate 100% for black toner and cyan toner. "level" is set to "50" is set to indicate 50% for magenta toner and yellow toner.

[0066] "class" indicates whether the colorant is consumed or replenished, and in this embodiment, "supplyThatIsConsumed" is set, indicating that it is consumed. Examples of replenished items include waste toner. "unit" indicates the unit of the values ​​set in "maxcapacity" and "level," and in this embodiment, "percent" is set. "colorantname" indicates the color of the colorant, and in this embodiment, black, cyan, magenta, and yellow are set.

[0067] The IETF Printer MIB v2 [RFC3805] defines a MIB object, prtMarkerSuppliesTable. The printer-supply-description attribute 1002 is also the same as that set in this MIB object, prtMarkerSuppliesTable.

[0068] The printer-supply-description attribute 1002 also has the same number of pieces of information set in a list as the number of toners. The name of the toner is set for each piece of information. In this embodiment, the toner name set for black toner is "Conon Toner T104 Black Toner," and for cyan toner is "Conon Toner T104 Cyan Toner." Furthermore, the toner name set for magenta toner is "Conon Toner T104 Magenta Toner," and the toner name set for yellow toner is "Conon Toner T104 Yellow Toner."

[0069] The extended toner attributes of the printing device 101 will be described with reference to FIG. 11. FIG. 11 shows the extended toner attributes of the Internet Printing Protocol (IPP). The extended toner attributes are used, for example, when an AirPrint client acquires toner information. The toner-colors attribute 1101 is set with a list of the same number of pieces of information as the number of toners. Each piece of information represents the color of the toner in RGB. In this embodiment, "#000000" is set to indicate black, "#00FFFF" to indicate cyan, "#FF00FF" to indicate magenta, and "#FFFF00" to indicate yellow.

[0070] The toner-levels attribute 1102 is set with a list of information equal in number to the number of toners. Each piece of information represents the current capacity of the toner as a percentage. In this embodiment, 100, which indicates 100%, is set for black toner and cyan toner. Also, 50, which indicates 50%, is set for magenta toner and yellow toner.

[0071] The toner-names attribute 1103 is set with a list of information equal in number to the number of toners. The name of the toner is set for each piece of information. In this embodiment, the toner name set for black toner is "Conon Toner T104 Black Toner," and for cyan toner is "Conon Toner T104 Cyan Toner." Furthermore, the toner name set for magenta toner is "Conon Toner T104 Magenta Toner," and the toner name set for yellow toner is "Conon Toner T104 Yellow Toner."

[0072] The standard toner attributes in Fig. 10 and the extended toner attributes in Fig. 11 are one form of format for information relating to the remaining amount of recording material. The standard toner attributes are described in the format defined in Fig. 10, and the extended toner attributes are described in the format defined in Fig. 11. Then, information relating to toner according to the two formats is transmitted using the method shown in Fig. 13, which will be described later.

[0073] 12 shows an AirPrint print setting screen on the printing apparatus 101. AirPrint is an OS standard printing function for Apple products. The AirPrint print setting menu shown on a print setting screen 1201 is displayed on the operation panel 905 of the printing apparatus 101.

[0074] The AirPrint setting is a setting for enabling or disabling AirPrint, which is a printing system supported by the printing apparatus 101. When this setting is set to ON, the printing apparatus 101 operates as an AirPrint-supporting printing apparatus.

[0075] The operation when the printing device 101 starts up will be described with reference to Fig. 13. Fig. 13 corresponds to the cloud print startup sequence in Fig. 2 and shows a flow when the printing device 101, which supports cloud print, sends printer information 220 to the cloud print service 200.

[0076] The processing described below is realized, for example, by the CPU 702 of the printing apparatus 101 reading a program stored in the ROM 704 into the RAM 703 and executing it. In the following, the step numbers of each process included in the flowcharts are indicated by numbers beginning with "S." This also applies to the subsequent flowcharts.

[0077] In S1301, the toner information management unit 813 of the printing apparatus 101 acquires toner information of the printing apparatus 101. In S1302, the cloud print device information management unit 805 of the printing apparatus 101 generates the standard toner attributes described in Fig. 10. Then, the toner information acquired in S1301 is set to the generated standard toner attributes.

[0078] In step S1303, the cloud print device information management unit 805 of the printing apparatus 101 generates Printer Description Attributes. The Printer Description Attributes is an IPP attribute group, and is information set in the printer information 220.

[0079] In S1304, the cloud print device information management unit 805 of the printing apparatus 101 acquires the AirPrint setting from the storage unit 806. In S1305, the cloud print device information management unit 805 of the printing apparatus 101 determines the AirPrint setting acquired in S1304. If the AirPrint setting is ON (YES), the process proceeds to S1306, and if the AirPrint setting is OFF (NO), the process proceeds to S1308.

[0080] If the AirPrint setting is ON, in step S1306, the cloud print device information management unit 805 of the printing apparatus 101 generates the extended toner attribute described with reference to Fig. 11. Then, the toner information acquired in step S1302 is set in the generated extended toner attribute.

[0081] In S1307, the cloud print device information management unit 805 of the printing apparatus 101 sets the extended toner attributes generated in S1306 to the Printer Description Attributes generated in S1303.

[0082] In S1308, the cloud print device information management unit 805 of the printing apparatus 101 transmits the generated Printer Description Attributes to the cloud print service 200. The flow in Fig. 13 is a flow when the printing apparatus 101 is registered in the cloud print server, but after the printing apparatus 101 is registered, the AirPrint setting of the printing apparatus 101 may be changed between ON and OFF. If the AirPrint setting is changed from OFF to ON after the printing apparatus 101 is registered, Printer Description Attributes including the extended toner attributes may be transmitted to the cloud print server.

[0083] The operation when the printing device 101 receives a printer information request for local printing will be described with reference to Fig. 14. Fig. 14 shows the flow when the printing device 101, which supports the local print function in Fig. 4, receives a printer information request 403 from the client terminal 100 and transmits a printer information response 404. The printer information response 404 that the printing device 101 transmits to the client terminal 100 includes printer information 412.

[0084] 14 is realized, for example, by the CPU 702 of the printing apparatus 101 reading out a program stored in the ROM 704 into the RAM 703 and executing it. In S1401, the toner information management unit 813 of the printing apparatus 101 acquires toner information of the printing apparatus 101. In S1402, the local print device information management unit 812 of the printing apparatus 101 generates the standard toner attributes described in Fig. 10. Then, the toner information acquired in S1401 is set to the generated standard toner attributes.

[0085] In S1403, the local print device information management unit 812 of the printing apparatus 101 generates Printer Description Attributes. The Printer Description Attributes is an IPP attribute group, and is information set in the printer information 412. In S1404, the local print device information management unit 812 of the printing apparatus 101 acquires AirPrint settings from the storage unit 806.

[0086] In step S1405, the local print device information management unit 812 of the printing apparatus 101 determines the AirPrint setting acquired in step S1404. If the AirPrint setting is ON (YES), the process proceeds to step S1406. If the AirPrint setting is OFF (NO), the process proceeds to step S1408.

[0087] If the AirPrint setting is ON, in step S1406, the local print device information management unit 812 of the printing apparatus 101 generates the extended toner attribute described with reference to Fig. 11. Then, the toner information acquired in step S1402 is set in the generated extended toner attribute.

[0088] In step S1407, the local print device information management unit 812 of the printing apparatus 101 sets the extended toner attributes generated in step S1406 to the Printer Description Attributes generated in step S1403. In step S1408, the local print device information management unit 812 of the printing apparatus 101 transmits the generated Printer Description Attributes to the client terminal 100.

[0089] In this embodiment, whether the printing device 101 supports the local print function or the cloud print function, the printing device 101 generates toner information based on both standard toner attributes and extended toner attributes. The client terminal 100 can obtain toner information based on both standard toner attributes and extended toner attributes from either the printing device 101 that supports the local print function or the printing device 101 that supports the cloud print function.

[0090] In the following embodiments, the description will be given on the assumption that the printing system of the client terminal 100 is AirPrint. In the AirPrint client, toner information is obtained from the extended toner attributes.

[0091] The flow when the client terminal 100 displays information about a local printer will be described with reference to Fig. 15. Fig. 15 shows the flow of the client terminal 100 when the printing device 101, which supports the local print function in Fig. 4, receives a printer information request 403 from the client terminal 100 and transmits a printer information response 404. The printer information response 404 that the client terminal 100 receives from the printing device 101 includes printer information 412.

[0092] 15 is realized, for example, by the CPU of the client terminal 100 reading out a program stored in a storage device into RAM and executing it. In S1501, the client terminal 100 transmits a printer information request 403 to the printing device 101.

[0093] In S1502, the client terminal 100 receives the printer information response 404 from the printing device 101. The printer information response 404 includes printer information 412. In S1503, the client terminal 100 analyzes the received printer information 412 and acquires the name, location, and model information of the printer.

[0094] In S1504, the client terminal 100 determines whether the extended toner attribute is included in the received printer information 412. If the extended toner attribute is included in the printer information 412 (YES), the process proceeds to S1505, and if the extended toner attribute is not included (NO), the process proceeds to S1506. If the extended toner attribute is included, in S1505, the client terminal 100 acquires the toner name and toner level information from the extended toner attribute.

[0095] In S1506, the client terminal 100 generates a printer information screen using the acquired printer name, location, model, toner name, and toner level information. If the toner name and toner level information cannot be acquired, a message stating "No information available" is displayed in the supply information display area 504. In S1507, the client terminal 100 displays the printer information screen generated in S1506.

[0096] The flow when the client terminal 100 displays cloud printer information will be described with reference to Fig. 16. Fig. 16 shows the flow when the client terminal 100 of Fig. 3 uses the cloud print service. The client terminal 100 sends a cloud printer information request 300 to the cloud print service 200 and receives a cloud printer information response 301 from the cloud print service 200. The cloud printer information response 301 includes printer information 321.

[0097] 16 is realized, for example, by the CPU of the client terminal 100 reading out a program stored in a storage device into RAM and executing the program. In S1601, the client terminal 100 transmits a cloud printer information request 300 to the cloud print service 200.

[0098] In S1602, the client terminal 100 receives a cloud printer information response 301 from the cloud print service 200. The printer information response 301 includes printer information 321. In S1603, the client terminal 100 analyzes the received printer information 321 and acquires the name, location, and model information of the printer.

[0099] In S1604, the client terminal 100 determines whether the extended toner attribute is included in the received printer information 321. If the extended toner attribute is included in the printer information 321 (YES), the process proceeds to S1605, and if the extended toner attribute is not included (NO), the process proceeds to S1606.

[0100] In S1605, the client terminal 100 acquires the toner name and toner level information from the extended toner attributes. In S1606, the client terminal 100 generates a printer information screen using the acquired printer name, location, model, toner name, and toner level information. If the toner name and toner level information cannot be acquired, a message stating "No information available" is displayed in the supply information display area 504. In S1607, the client terminal 100 displays the printer information screen generated in S1606.

[0101] 17 is an example of an information display screen for a local printer and a cloud printer displayed on the client terminal 100. A name area 1701 displays the name of the printing device 101. A location area 1702 displays the location of the printing device 101. A model area 1703 displays the model of the printing device 101.

[0102] A supply information display area 1704 displays toner information for the printing device 101. 1705 displays the name and remaining amount of black toner for the printing device 101. 1706 displays the name and remaining amount of cyan toner for the printing device 101. 1707 displays the name and remaining amount of magenta toner for the printing device 1701. 1708 displays the name and remaining amount of yellow toner for the printing device 101.

[0103] This information is included in printer information 412 for local printers and printer information 321 for cloud printers. In this embodiment, the printing device 101 generates toner information using both standard toner attributes and extended toner attributes. The client terminal 100 can obtain toner information using both standard toner attributes and extended toner attributes from both a printing device 101 that supports the local print function and a printing device 101 that supports the cloud print function. In this manner, if the printing system of the client terminal 100 is AirPrint, the client terminal can receive toner information as printer information and display it using extended toner attributes. In this embodiment, the explanation has been given on the assumption that the printing system of the client terminal 100 is AirPrint.

[0104] In the following second embodiment, it is assumed that the printing system of the client terminal 100 is Mopria. Mopria is the standard printing for the Android OS. The Mopria client acquires toner information from the standard toner attributes.

[0105] The flow when the client terminal 100 in Example 2 displays information about a local printer will be described with reference to Fig. 18. Fig. 18 shows the flow of the client terminal 100 when the printing device 101 compatible with the local print function in Fig. 4 receives a printer information request 403 from the client terminal 100 and transmits a printer information response 404. The printer information response 404 that the client terminal 100 receives from the printing device 101 includes printer information 412.

[0106] In S1801, the client terminal 100 sends a printer information request 403 to the printing device 101. In S1802, the client terminal 100 receives a printer information response 404 from the printing device 101. The printer information response 404 includes printer information 412. In S1803, the client terminal 100 analyzes the received printer information 321 and acquires the name, location, and model information of the printer.

[0107] In S1804, the client terminal 100 determines whether the standard toner attributes are included in the received printer information 321. If the standard toner attributes are included in the received printer information 321 (YES), the process proceeds to S1805, and if the standard toner attributes are not included (NO), the process proceeds to S1806. In S1805, the client terminal 100 acquires the toner name and toner level information from the standard toner attributes.

[0108] In S1806, the client terminal 100 generates a printer information screen using the acquired printer name, location, model, toner name, and toner level information. If the toner name and toner level information cannot be acquired, a message stating "No information available" is displayed in the supply information display area 504. In S1807, the client terminal 100 displays the printer information screen generated in S1806.

[0109] The flow when the client terminal 100 in the second embodiment displays information about a cloud printer will be described with reference to Fig. 19. Fig. 19 shows the flow when the client terminal 100 in Fig. 3 uses a cloud print service. The client terminal 100 sends a cloud printer information request 300 to the cloud print service 200 and receives a cloud printer information response 301 from the cloud print service 200. The cloud printer information response 301 includes printer information 321.

[0110] In S1901, the client terminal 100 transmits a cloud printer information request 300 to the cloud print service 200. In S1902, the client terminal 100 receives a cloud printer information response 301 from the cloud print service 200. The printer information response 301 includes printer information 321.

[0111] In S1903, the client terminal 100 analyzes the received printer information 321 and acquires the printer name, location, and model information. In S1904, the client terminal 100 determines whether the received printer information 321 includes standard toner attributes. If the printer information 321 includes standard toner attributes (YES), the process proceeds to S1905; if the printer information 321 does not include standard toner attributes (NO), the process proceeds to S1906. In S1905, the client terminal 100 acquires the toner name and toner level information from the standard toner attributes.

[0112] In S1906, the client terminal 100 generates a printer information screen using the acquired printer name, location, model, toner name, and toner level information. If the toner name and toner level information cannot be acquired, the client terminal 100 displays a message in the supply information display area 504 saying that there is no information.

[0113] In S1907, the client terminal 100 displays the printer information screen generated in S1906. The local printer and cloud printer information display screen displayed on the client terminal 100 in the second embodiment is the same as that shown in FIG. 17, and therefore description thereof will be omitted.

[0114] In this embodiment, the printing device 101 generates toner information using both standard toner attributes and extended toner attributes. The client terminal 100 can obtain toner information using both standard toner attributes and extended toner attributes from both the printing device 101 that supports the local print function and the printing device 101 that supports the cloud print function. In this way, if the printing system of the client terminal 100 is Mopria, the client terminal can receive toner information as printer information and display it using the standard toner attributes.

[0115] In the present invention, the printing device 101 generates toner information based on both standard toner attributes and extended toner attributes. The client terminal 100 can obtain toner information based on both standard toner attributes and extended toner attributes from both the printing device 101 that supports the local print function and the printing device 101 that supports the cloud print function. In the present invention, regardless of the printing system of the client terminal 100 and regardless of whether the printing device 101 is a local printer or has the cloud print function, the client terminal 100 can receive and display the toner information as printer information.

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

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

[0118] This application claims priority based on Japanese Patent Application No. 2024-075413, filed May 7, 2024, the entire contents of which are incorporated herein by reference.

[0119] 100: Client terminal, 101: Printing device, 200: Cloud print service, 201: Cloud print event notification service

Claims

1. A printing device that communicates with a cloud print server that provides a cloud print service, comprising: a registration means for registering the printing device with the cloud print server; and a transmission means for transmitting printer information of the registered printing device to the cloud print server, wherein the transmission means transmits the printer information including information regarding the remaining amount of recording material of the printing device defined in a first format and information regarding the remaining amount of recording material of the printing device defined in a second format.

2. The printing device according to claim 1, wherein said transmission means includes information defined in said first format and information defined in said second format in the printer information according to the print settings of said printing device.

3. The printing device according to claim 2, wherein the print settings are OS standard print settings.

4. A printing device as described in claim 2 or 3, wherein even if the printing settings of the printing device are changed after the registration of the printing device by the registration means, the transmission means transmits the printer information including information regarding the remaining amount of recording material of the printing device defined in a first format and information regarding the remaining amount of recording material of the printing device defined in a second format.

5. The printing device according to any one of claims 1 to 4, wherein the first format is Internet Printing Protocol (IPP) standard toner attributes, and the second format is IPP extended toner attributes.

6. A control method for a printing device that communicates with a cloud print server that provides a cloud print service, wherein a registration means registers the printing device in the cloud print server, a transmission means transmits printer information of the registered printing device to the cloud print server, and the transmission means transmits the printer information including information regarding the remaining amount of recording material of the printing device defined in a first format and information regarding the remaining amount of recording material of the printing device defined in a second format.

7. A program for operating a computer of a printing device that communicates with a cloud print server that provides a cloud print service, the program causing the computer to function as: a registration means for registering the printing device with the cloud print server; and a transmission means for transmitting printer information of the registered printing device to the cloud print server, the transmission means transmitting the printer information including information regarding the remaining amount of recording material of the printing device defined in a first format and information regarding the remaining amount of recording material of the printing device defined in a second format.

8. A cloud print system including a cloud print server that provides a cloud print service, a printing device, and a client terminal, wherein the printing device has a registration means for registering the printing device in the cloud print server, and a transmission means for transmitting printer information of the registered printing device to the cloud print server, wherein the transmission means transmits the printer information to the cloud print server, the printer information including information regarding the remaining amount of recording material of the printing device defined in a first format and information regarding the remaining amount of recording material of the printing device defined in a second format, and the cloud print server transmits the received printer information to the client terminal.

9. The cloud print system according to claim 8, wherein the client terminal displays information about the remaining amount of recording material based on the printer information received from the cloud print server.

10. The cloud print system according to claim 8 or 9, wherein the client terminal displays information regarding the remaining amount of recording material based on the printer information received from the cloud print server and the printing system supported by the client terminal.

11. The cloud print system according to any one of claims 8 to 10, wherein the client terminal displays information about the remaining amount of recording material based on either the information defined in the first format or the information defined in the second format of the printer information received from the cloud print server.

Images