Print apparatus, method of controlling print apparatus, and program
The system differentiates between local and cloud printers using distinct icons and information transmission based on connection state, addressing user confusion and ensuring correct printer selection.
Patent Information
- Application Number
- JP2023110141
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-07-04
- Publication Date
- 2025-01-20
AI Technical Summary
Existing printing systems fail to distinguish between local and cloud printers when using standard drivers, leading to identical icon representations, which confuses users about the connection state of their printers.
Implement a system where printers can be connected in two states - via a server (first connection state) or directly (second connection state) with distinct icons and information transmission mechanisms to differentiate between these states, ensuring icons and information are appropriately sent to the client device based on the connection type.
Enables users to easily identify the connection state of their printers, preventing confusion and ensuring correct selection for printing tasks.
Smart Images

Figure 2025008189000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a printing device, a control method for a printing device, and a program. [Background technology]
[0002] Conventionally, when a terminal device such as a personal computer issues a print instruction to a printer (printing device), a printer driver supplied by the printer or a printer vendor (printer manufacturer) that manufactures the printer is used. In recent years, a standard driver provided by an OS manufacturer that manufactures an OS may be used. By using the standard driver, a print instruction can be issued from a terminal device to a printer and printing can be performed on the printer without using a printer driver provided by a printer vendor. For example, Windows (registered trademark) is equipped with a standard driver called an "IPP class driver." Android (registered trademark) is equipped with a standard driver called "Mopria (registered trademark)." iOS (registered trademark) is equipped with a standard driver called "AirPrint (registered trademark)" as one function of the OS. Each of these standard drivers is a driver that transmits a print command that complies with a printing protocol called IPP (Internet Printing Protocol). Then, a printer that supports IPP can receive the print command and execute printing. Therefore, the standard driver is compatible with multiple types of printers and can cause each printer to execute printing.
[0003] For example, Patent Document 1 discloses a configuration in which a standard driver or a print setting extension application that operates in conjunction with the standard driver acquires icon image data representing the appearance of a printer from a printer or a cloud print service. The configuration described in Patent Document 1 makes it possible to display an icon based on the icon image data on the UI of the print setting extension application or on a printer management screen provided by the OS. In addition, it is possible to acquire the image for the icon in either case of being connected to a printer via a LAN (hereinafter referred to as a "local printer") or being connected to a printer on a cloud print service (hereinafter referred to as a "cloud printer"). [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2022-89143 A Summary of the Invention [Problem to be solved by the invention]
[0005] However, in the configuration described in Patent Document 1, when a local printer and a cloud printer are the same model, the acquired icon image is the same, and therefore the icon displayed on the printer management screen is also the same. As a result, it becomes difficult for the user to distinguish which icon represents the local printer and which icon represents the cloud printer.
[0006] The present invention has been made in view of the above problems, and has an object to provide a printing device, a printing device control method, and a program that enable a user to distinguish which connection state an icon represents for a printing device. [Means for solving the problem]
[0007] In order to achieve the above-mentioned object, the printing device of the present invention is a printing device that can take a first connection state in which it is communicatively connected to an information processing device via a server, and a second connection state in which it is communicatively connected to the information processing device without going through the server, and is characterized in that it is equipped with a storage means for storing a first icon representing the printing device in the first connection state and a second icon representing the printing device in the second connection state, the second icon having different visibility from the first icon, and a transmission means for transmitting first information including the first icon to the server in the first connection state, and for transmitting second information including the second icon to the information processing device in the second connection state. Effect of the Invention
[0008] According to the present invention, it is possible to distinguish in which connection state the icon represents a printing device. [Brief description of the drawings]
[0009] [Figure 1] 1 is a schematic diagram showing an outline of the configuration of a printing system according to a first embodiment. [Diagram 2] FIG. 2 is a block diagram showing a hardware configuration of a client computer. [Diagram 3] FIG. 2 is a block diagram showing the hardware configuration of a cloud print-compatible printer. [Figure 4] FIG. 2 is a block diagram showing a hardware configuration of the cloud print service. [Diagram 5] FIG. 11 is a sequence diagram showing a process executed among a user, a cloud print-compatible printer, and a cloud print service. [Figure 6] FIG. 11 is a diagram illustrating an example of an icon indicating a cloud print-compatible printer. [Figure 7] 10 is a flowchart showing a process executed by a cloud print-compatible printer. [Figure 8] 11 is a flowchart showing a process executed on a client computer. [Figure 9] FIG. 13 is a diagram illustrating an example of a screen displayed on a client computer. [Figure 10] FIG. 13 is a diagram showing an example (modification) of a screen displayed on a client computer. [Figure 11] 10 is a flowchart showing a process executed by a client computer according to the second embodiment. [Figure 12] FIG. 13 is a diagram illustrating an example of a screen displayed on a client computer. [Figure 13] 13 is a flowchart (modification) showing a process executed in a client computer. [Figure 14] 13 is a flowchart showing a process executed by a client computer according to the third embodiment. [Figure 15] 13 is a flowchart (modification) showing a process executed in a client computer. [Figure 16] FIG. 13 is a schematic diagram showing an outline of the configuration of a printing system according to a fourth embodiment. [Figure 17] 13 is a flowchart showing a process executed by a client computer according to the fourth embodiment. [Figure 18] 13 is a flowchart (modification) showing a process executed in a client computer. [Figure 19] FIG. 13 is a diagram showing an example of an icon indicating a cloud print-compatible printer according to the fifth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Each embodiment of the present invention will be described in detail below with reference to the drawings. However, the configurations described in each of the following embodiments are merely examples, and the scope of the present invention is not limited by the configurations described in each embodiment. For example, each part constituting the present invention can be replaced with any configuration that can exert a similar function. In addition, any configuration may be added. In addition, any two or more configurations (features) of each embodiment can be combined.
[0011] First Embodiment Hereinafter, the first embodiment will be described with reference to FIG. 1 to FIG. 10. FIG. 1 is a schematic diagram showing an outline of the configuration of a printing system according to the first embodiment. As shown in FIG. 1, the printing system 1000 includes a client computer 100, a plurality of cloud print-compatible printers 200, a print setting extension application distribution server 400, and a cloud print service 500. These are connected to each other via a network 150 so as to be able to communicate with each other. In this embodiment, the number of cloud print-compatible printers 200 is two. One of the cloud print-compatible printers 200 is referred to as a "cloud print-compatible printer 201", and the other cloud print-compatible printer 200 is referred to as a "cloud print-compatible printer 202". The cloud print-compatible printer 201 is a cloud printer connected to the client computer 100 via the cloud print service 500 so as to be able to communicate with each other. Hereinafter, the state in which the cloud print-compatible printer 201 is connected to the client computer 100 via the cloud print service 500 so as to be able to communicate with each other is referred to as a "first connection state". The cloud print-compatible printer 202 is a local printer that is connected to the client computer 100 so as to be able to communicate directly without going through the cloud print service 500, that is, connected via a local area network. Hereinafter, the state in which the printer is connected to the client computer 100 so as to be able to communicate without going through the cloud print service 500 will be referred to as a "second connection state (local connection)."
[0012] The cloud print-compatible printer 201 can also be a local printer that is communicatively connected to another client computer (not shown) different from the client computer 100 without going through the cloud print service 500. That is, the cloud print-compatible printer 202 can take the second connection state. On the other hand, the cloud print-compatible printer 202 can also be a cloud printer that is communicatively connected to the client computer 100 via the cloud print service 500. That is, the cloud print-compatible printer 202 can take the first connection state. Also, the number of cloud print-compatible printers 200 arranged is two in this embodiment, but is not limited to this and may be, for example, one or three or more.
[0013] The print setting extending application distribution server 400 is a server that executes a distribution service of an application executed on the client computer 100, and may be managed by, for example, a printer vendor (printer manufacturer) that manufactures a printer. The client computer 100 can accept a user operation that requests the installation of, for example, a print setting extending application 1052 (see FIG. 2). In this case, the print setting extending application 1052 is installed in the client computer 100 from the print setting extending application distribution server 400. Also, when an application identifier is included in an information file (Inf file) of a printer driver, the print setting extending application 1052 and the like are installed in the client computer 100 from the print setting extending application distribution server 400.
[0014] The cloud print service 500 functions as a print server system made up of multiple servers and controls printing on the print server system. The cloud print service 500 manages accounts using user IDs and passwords. Users can access the cloud print service 500 using their user IDs and passwords.
[0015] FIG. 2 is a block diagram showing a hardware configuration of a client computer. The client computer 100 shown in FIG. 2 is preferably, for example, a desktop or notebook personal computer, but is not limited thereto, and may be an information processing device such as a tablet terminal or a smartphone. The client computer 100 has a CPU 101, an input I / F 103, an output I / F 104, a communication I / F 106, a common data system bus 107, a storage device 120, an input device 121, and an output device 122. The CPU 101, the input I / F 103, the output I / F 104, the communication I / F 106, and the storage device 120 are connected to each other via the common data system bus 107 so as to be able to communicate with each other. The storage device 120 has a main storage device 102 and an auxiliary storage device 105. The main storage device 102 has a ROM 1021 and a RAM 1022.
[0016] The CPU 101 controls the entire client computer 100 according to a program stored in the ROM 1021. The RAM 1022 is also used as a work area when the CPU 101 performs various processes. The input device 121 has a keyboard 108 and a pointing device 109. The input device 121 is communicably connected to the common data system bus 107 via the input I / F 103, and is a device for a user to give various instructions to the client computer 100. The output device 122 has a monitor 110 and a panel 111. The output device 122 is communicably connected to the common data system bus 107 via the output I / F 104, and is a device for outputting data and the like. The client computer 100 is communicably connected to the network 150 via the communication I / F 106. The auxiliary storage device 105 stores an application 1051, a print setting extension application 1052, and an OS (operating system) 1053. The OS 1053 is equipped with a cloud printer driver 1057 and an IPP standard driver 1058 as standard drivers.
[0017] The application 1051 is an application capable of, for example, editing a document or creating materials for presentation. Data created using the application 1051 can be printed by the cloud print-compatible printer 200 by operating the input device 121. The print setting extension application 1052 is an application that operates in cooperation with a cloud printer driver 1057 and an IPP standard driver 1058. The print setting extension application 1052 has a function of performing print settings for the cloud print-compatible printer 200. In addition, the print setting extension application 1052 can store an icon indicating the cloud print-compatible printer 200 for each cloud print-compatible printer 200 in the auxiliary storage device 105. The icon is represented by a figure, a pictogram, or the like.
[0018] The cloud printer driver 1057 is a printer control program. If the cloud print-compatible printer 200 is connected to the cloud print service 500, that is, in the first connection state, the cloud printer driver 1057 can issue a print instruction to the cloud print-compatible printer 200 regardless of the model. In this case, the cloud print-compatible printer 200 is the cloud print-compatible printer 201, and the cloud printer driver 1057 can issue a print instruction to the cloud print-compatible printer 201. This allows printing to be performed by the cloud print-compatible printer 201. As described above, the cloud print-compatible printer 202 can also take the first connection state. In this case, the cloud printer driver 1057 can issue a print instruction to the cloud print-compatible printer 202. The IPP standard driver 1058 is a printer control program. If the cloud print-compatible printer 200 is connected by the IPP protocol, that is, in the second connection state, the IPP standard driver 1058 can issue a print instruction to the cloud print-compatible printer 200 regardless of the model. The cloud print-compatible printer 200 in this case is the cloud print-compatible printer 202, and the IPP standard driver 1058 is capable of issuing print instructions (sending a print job) to the cloud print-compatible printer 202. This allows printing to be performed by the cloud print-compatible printer 202.
[0019] FIG. 3 is a block diagram showing a hardware configuration of a cloud print-compatible printer. The cloud print-compatible printer 200 shown in FIG. 3 is preferably, for example, an MFP (Multi-Function Peripheral), but is not limited thereto, and may be an image forming device such as an SFP (Single-Function Printer). The cloud print-compatible printer 200 has a control unit 221, a storage unit 224, a network communication unit 225, a display unit 226, an operation unit 227, a printing unit (printing means) 228, a printer information storage unit (storage means) 229, and a processing unit 230. The control unit 221 has a CPU 222 and a memory 223. The control unit 221 controls the operation of the entire cloud print-compatible printer 200. The CPU 222 reads out a control program stored in the storage unit 224 and performs various controls such as print control and reading control. The memory 223 is used as a work area or a temporary storage area for expanding various control programs. The storage unit 224 stores print data, image data, various programs, and various setting information. The various programs include, for example, programs for causing a computer to execute each unit and each means (a control method of a printing device) of the cloud print-compatible printer 200. The storage unit 224 is preferably an auxiliary storage device such as an HDD (Hard Disk Drive), but is not limited thereto and may be, for example, a non-volatile memory such as an SSD (Solid State Drive). In this embodiment, hardware such as the CPU 222, memory 223, and storage unit 224 constitute a computer.
[0020] The processing unit 230 has a function of a RIP (Raster Image Processor) that expands print data received via the network 150 and generates a print image. The processing unit 230 also has an image processing ability that performs image resolution conversion and correction processing. The processing unit 230 is preferably configured with a hardware circuit (ASIC or FPGA, etc.), but is not limited to this. For example, the cloud print-compatible printer 200 may have a processor for image processing, and the processor may execute an image processing program to execute image processing and print data expansion processing. The CPU 222 may execute a program for image processing to execute image processing and print data expansion processing. Furthermore, image processing may be executed by a combination of these. The processing unit 230 also analyzes print data to generate a print image. This print image is transferred from the control unit 221 to the printing unit 228 together with a control command. The printing unit 228 can print an image based on the print image on a sheet (recording medium) fed from a paper feed cassette (not shown). Printing in the printing unit 228 is performed using one of printing materials, ink and toner. The control unit 221 also functions as a remaining amount detection unit that detects the remaining amount of printing material and as a status detection unit that detects the status of the cloud print-compatible printer 200.
[0021] The display unit 226 displays various information such as images. The operation unit 227 is composed of, for example, a liquid crystal display unit having a touch panel function, various hard keys, and the like. The display unit 226 and the operation unit 227 also function as a reception unit that receives instructions from a user. The cloud print-compatible printer 200 may also have a reading unit (not shown) that reads a document and generates a read image. In this case, the read image generated by the reading unit is stored in the storage unit 224. The control unit 221 is also connected to the network 150 via the network communication unit 225. The network communication unit 225 transmits images and information to devices on the network 150, and receives print data and information from devices on the network 150. The printer information storage unit 229 stores, for example, a hardware ID (hereinafter referred to as "HWID") that is an identifier for identifying the cloud print-compatible printer 200, printer capability information described later, and an icon indicating the cloud print-compatible printer 200. The printer information storage unit 229 may be included in the storage unit 224.
[0022] Fig. 4 is a block diagram showing the hardware configuration of a cloud print service. The cloud print service 500 shown in Fig. 4 is a service that exists on the cloud via the network 150, and has a function related to printing. The cloud print service 500 can also provide a cloud print function based on "IPP Infra". The cloud print service 500 has a printer registration unit 501, a print queue generation unit 502, a printer list generation unit 503, a search response unit 504, a print job management unit 505, a print job generation unit 506, a printer database 510, and a print job storage area 511.
[0023] When a printer registration instruction is received from the cloud print-compatible printer 201, the printer registration unit 501 causes the print queue generation unit 502 to generate a print queue. The print queue is associated with printer identification information and registered in the printer database 510. In this embodiment, the fact that the print queue and the printer identification information are associated and registered is referred to as "the printer is registered." Attributes such as the location of the printer may be added to the registered printer. The printer database 510 can also store an icon indicating the cloud print-compatible printer 200. The printer list generation unit 503 generates a list of printers registered in the printer database 510. The search response unit 504 responds with information of the printers registered in the printer database 510 in response to a printer search event from the client computer 100 to the cloud print service 500. The print job management unit 505 receives a print job from the client computer 100. Then, the print job management unit 505 directly sends the print job to the cloud print-compatible printer 201 associated with the print queue specified by the client computer 100. The print job management unit 505 may temporarily store the print job in the print job storage area 511, and send the print job when the cloud print-compatible printer 201 as the output destination is determined.
[0024] FIG. 5 is a sequence diagram showing a process executed among a user, a cloud print-compatible printer, and a cloud print service. Here, a process until the cloud print-compatible printer 201 registers an icon image (icon) representing the cloud print-compatible printer 201 in the cloud print service 500 will be described. The process based on the sequence diagram shown in FIG. 5 is started by the user 5000 instructing the cloud print-compatible printer 201 to register in the cloud print service 500. As shown in FIG. 5, in step S501, the user 5000 operates the operation unit 227 of the cloud print-compatible printer 201 to instruct the cloud print service 500 to register information about the cloud print-compatible printer 201. This allows the cloud print-compatible printer 201 to accept this instruction. Thus, in this embodiment, the operation unit 227 also functions as an operation unit for performing a registration operation of the cloud print-compatible printer 201 in the cloud print service 500. The registration operation can also be performed by accessing the WEB server function of the cloud print-compatible printer 201 from the client computer 100. In this case, the user 5000 needs to be authenticated to log in to the cloud print service 500 with his / her own account. An authentication screen provided by the cloud print service 500 is displayed on the cloud print-compatible printer 201. The user 5000 inputs user identification information and a password on the authentication screen. The user identification information and password are transmitted to an authentication server (not shown). This allows the user to be authenticated, and the user 5000 can then log in to the cloud print service 500.
[0025] In step S502, the cloud print-compatible printer 201 transmits the request for registration of the cloud print-compatible printer 201 in step S501 to the cloud print service 500 via the network communication unit 225 as a transmission unit. This allows the printer registration unit 501 of the cloud print service 500 to receive this registration request. After receiving the registration request, the printer registration unit 501 causes the print queue generation unit 502 to generate a print queue. The print queue is associated with the printer identification information and registered in the printer database 510. By generating the print queue and registering the print queue, the cloud print service 500 becomes capable of transmitting print data received from the client computer 100 to the cloud print-compatible printer 201. In addition, the cloud print service 500 notifies the cloud print-compatible printer 201 of the identification information of the print queue.
[0026] In step S503, the cloud print-compatible printer 201 inquires of the cloud print service 500 about the upload destination of the icon image representing the cloud print-compatible printer 201. This inquiry is made via the network communication unit 225. The cloud print-compatible printer 201 specifies the print queue generated in step S502 and transmits "Get-Printer-Attributes", which is an IPP operation. The print queue is specified using the identification information of the print queue received from the cloud print service 500. In addition, when inquiring about the upload destination, "printer-static-resource-directory-uri", which is an IPP attribute, is set as an argument of the operation. "printer-static-resource-directory-uri" is an argument for acquiring the URI of storage that can store information about the cloud print-compatible printer 201.
[0027] In step S504, the cloud print service 500 transmits a response in which the value of "printer-static-resource-directory-uri" is set to the cloud print-compatible printer 201 via the communication I / F 106. As a result, the cloud print-compatible printer 201 receives this response and is notified of the upload destination of the icon. The value of "printer-static-resource-directory-uri" is a value indicating the location of the storage available in correspondence with the print queue created in step S502. Specifically, a URL starting with "http" or "https" is transmitted as the response in step S504. The URL is, for example, "https: / / <URL of the cloud print service> / ipp / resource / <uniquely determined printer ID>". The printer ID is an ID issued when the print queue is created in step S502 and registered in the printer database 510. This ID may be, for example, a character string including the name of the cloud print-compatible printer 201, the serial number of the cloud print-compatible printer 201, the IP address of the cloud print-compatible printer 201, or the like. An example of a URL is "https: / / print.print-dev.com / ipp / resource / 0cc23168-d681-49b4-bc22-ef704a024aff".
[0028] In step S505, the cloud print-compatible printer 201 receives the response in step S504 and uploads the icon to the URL included in the response as the upload destination, that is, transmits the icon via the network communication unit 225 (transmission step). The icon uploaded here is stored in the printer information storage unit 229 of the cloud print-compatible printer 201.
[0029] The icons will be described with reference to FIG. 6. FIG. 6 is a diagram showing an example of an icon indicating a cloud print-compatible printer. FIG. 6(a) is a diagram showing an icon indicating a cloud print-compatible printer in a second connection state. FIG. 6(b) is a diagram showing an icon indicating a cloud print-compatible printer in a first connection state. A cloud icon (first icon) 601 shown in FIG. 6(a) is an icon indicating a cloud print-compatible printer 200 in a first connection state, that is, a cloud printer. A local icon (second icon) 602 shown in FIG. 6(b) is an icon indicating a cloud print-compatible printer 200 in a second connection state, that is, a local printer. The local icon 602 is an external perspective view (external view) that roughly imitates the external appearance of the cloud print-compatible printer 200. The cloud icon 601 includes a local icon 602 that is an external perspective view that roughly imitates the external appearance of the cloud print-compatible printer 200, and a cloud 603 that roughly imitates the external appearance of a cloud. Cloud 603 is a printer connected in the first connection state, that is, a diagram (connection state diagram) showing that it is a cloud printer, and is arranged overlapping with local icon 602. Thus, in this embodiment, cloud icon 601 and local icon 602 are different in shape. As a result, cloud icon 601 and local icon 602 have different visibility and can be easily distinguished. Note that cloud icon 601 and local icon 602 may have the same shape, but may have different colors, that is, different colors. In this case, cloud icon 601 and local icon 602 also have different visibility and can be easily distinguished. Also, cloud icon 601 and local icon 602 may each include the name, model number, and name of the manufacturer (maker) of cloud print compatible printer 200 of cloud print compatible printer 200. Also, multiple types of cloud icon 601 and local icon 602 may be prepared.
[0030] The cloud print-compatible printer 201 is a cloud printer connected in the first connection state. Therefore, in step S505, the cloud print-compatible printer 201 uploads information including the cloud icon 601 (hereinafter referred to as "first information") to the upload destination (cloud print service 500) using an HTTP PUT request. As described above, the cloud print-compatible printer 201 can also be a local printer by being connected in the second connection state. In this case, the cloud print-compatible printer 201 can transmit information including the local icon 602 (hereinafter referred to as "second information") to the other client computer. On the other hand, like the cloud print-compatible printer 201, the cloud print-compatible printer 202 can also upload the first information to the upload destination in the first connection state and transmit the second information to the client computer 100 in the second connection state. Furthermore, even if the cloud print-compatible printer 201 is in the first connection state, if the first information has already been transmitted, the cloud print-compatible printer 201 can omit transmitting the first information (the same applies to the cloud print-compatible printer 202). Furthermore, even if the cloud print-compatible printer 201 is in the second connected state, if the second information has already been transmitted, the cloud print-compatible printer 201 can omit transmitting the second information (the same applies to the cloud print-compatible printer 202).
[0031] In step S506, the cloud print-compatible printer 201 notifies the cloud print service 500 of printer capability information. The "printer capability information (sometimes simply referred to as "capability information")" refers to output information related to the output conditions of the cloud print-compatible printer 200. This output information is not particularly limited, and examples thereof include color mode setting values that can be processed by the cloud print-compatible printer 201, paper size settings, paper type settings, and finishing setting values such as stapling. In step S506, specifically, the cloud print-compatible printer 201 transmits the printer capability information to the cloud print service 500 using "Update-Output-Device-Attributes" defined in IPP. "Update-Output-Device-Attributes" is an operation in IPP that can update the value of an IPP attribute. When the printer capability information is transmitted, a value obtained by concatenating the IPP attribute "printer-icons", the name of the icon uploaded in step S505, and the path of the upload destination is obtained. This concatenated value is set in "Update-Output-Device-Attributes". For example, if the file name of the icon uploaded in step S505 is “512.png”, the file name will be “https: / / print.print-dev.com / ipp / resource / 0cc23168-d681-49b4-bc22-ef704a024aff / 512.png.” This makes it possible to notify the cloud print service that the icon uploaded in step S505 is an icon representing the cloud print-compatible printer 201.
[0032] In addition, in steps S503 to S505, the following process may be performed. In step S503, the cloud print-compatible printer 201 inquires about the free space of the upload destination in addition to the upload destination of the icon image. Specifically, the cloud print-compatible printer 201 inquires about the free space of the upload destination storage area using "printer-static-resource-k-octets-free" defined by IPP. The cloud print-compatible printer 201 can receive the upload destination and the free space of the upload destination storage area from the cloud print service 500 as a notification in step S504. In step S505, the cloud print-compatible printer 201 compares the data size of the icon image with the free space received in step S504. If the comparison result shows that the data size of the icon image is equal to or smaller than the free space, the cloud print-compatible printer 201 uploads the icon to the upload destination. On the other hand, if the comparison result shows that the data size of the icon image exceeds the free space, the cloud print-compatible printer 201 does not upload the icon.
[0033] Also, if multiple icons are uploaded in step S505, a list of URLs of the number of icons and "printer-icons" are set in "Update-Output-Device-Attributes". Then, it is preferable to send the IPP "Update-Output-Device-Attributes" to the cloud print service 500. The cloud print service 500 that receives this "Update-Output-Device-Attributes" rewrites the value of the IPP attribute "printer-icons" of the print queue with the notified value. As a result, when the OS 1053 makes a capability acquisition request for "printer-icons" to the cloud print service 500, the cloud print service 500 returns the path of the cloud icon 601 to the client computer 100. On the other hand, when the OS 1053 makes a capability acquisition request for "printer-icons" to the cloud print-compatible printer 202, the cloud print-compatible printer 202 returns the path of the local icon 602 to the client computer 100.
[0034] FIG. 7 is a flowchart showing a process executed by the cloud print-compatible printer. Here, the process executed by the cloud print-compatible printer 202 will be described as a representative of the cloud print-compatible printer 201 and the cloud print-compatible printer 202. This process is a process of determining whether the cloud print-compatible printer 202 is in the first connection state or the second connection state, and whether the cloud print-compatible printer 202 is to transmit an icon 601 for cloud use or an icon 602 for local use. The program based on the flowchart shown in FIG. 7 is started when the main power supply of the cloud print-compatible printer 202 is turned on and the cloud print-compatible printer 202 is operable. The cloud print-compatible printer 202 is connected in the second connection state and functions as a local printer, and is connected in the first connection state and functions as a cloud printer. The determination of whether the cloud print-compatible printer 202 is in the first connection state or the second connection state is performed by the CPU 222 (state determination means) based on the communication state of the network communication unit 225 of the cloud print-compatible printer 202, for example. Furthermore, the printer information storage unit 229 of the cloud print-compatible printer 202 stores a cloud icon 601 indicating that it also functions as a cloud printer, and a local icon 602 indicating that it also functions as a local printer.
[0035] As shown in FIG. 7, in step S700, the CPU 222 of the cloud print-compatible printer 202 judges whether or not there is a request to register the cloud print-compatible printer 202 to the cloud print service 500. This judgment process is executed based on whether or not a registration operation of the cloud print-compatible printer 202 has been performed on the operation unit 227. If a registration operation of the cloud print-compatible printer 202 has been performed, it is judged that there is a registration request of the cloud print-compatible printer 202. Also, if a registration operation of the cloud print-compatible printer 202 has not been performed, it is judged that there is no registration request of the cloud print-compatible printer 202. In this manner, in this embodiment, the CPU 222 also functions as an operation judgment unit that judges whether or not there is a registration operation. Then, if it is judged that there is a registration request of the cloud print-compatible printer 202 as a result of the judgment in step S700, the process proceeds to step S701. On the other hand, if it is judged that there is no registration request of the cloud print-compatible printer 202 as a result of the judgment in step S700, the process proceeds to step S707.
[0036] In step S701, when user authentication is required by the cloud print service 500, the user 5000 inputs user identification information and a password on an authentication screen provided by the cloud print service 500 to request authorization of the authority by the user 5000. After step S701 is executed, the process proceeds to step S702. Note that, if user authentication is not required, steps S701 and S702 can be omitted.
[0037] In step S702, the CPU 222 judges whether the authority requested in step S701 has been granted. If it is determined in step S702 that the authority has been granted, the process proceeds to step S703. On the other hand, if it is determined in step S702 that the authority has not been granted, the process proceeds to step S707.
[0038] In step S703, the CPU 222 transmits the registration request for the cloud print-compatible printer 202 in step S700 to the cloud print service 500 via the network communication unit 225. As a result, the printer registration unit 501 of the cloud print service 500 can receive this registration request.
[0039] In step S704, the CPU 222 inquires of the cloud print service 500 about the upload destination of the cloud icon 601 indicating the cloud print-compatible printer 202 in the first connection state via the network communication unit 225. This allows the cloud print service 500 to transmit the upload destination in response to this inquiry to the cloud print-compatible printer 202. The CPU 222 can then receive the upload destination transmitted from the cloud print service 500 via the network communication unit 225.
[0040] In step S705, the CPU 222 transmits the first information including the cloud icon 601 to the upload destination received in step S704 via the network communication unit 225. As a result, the first information is stored in the printer database 510 of the cloud print service 500. Note that in step S705, transmission of the second information including the local icon 602 is restricted. This makes it possible to prevent the cloud print service 500 from receiving the second information and erroneously storing the second information in the cloud print service 500.
[0041] In step S706, the CPU 222 transmits the printer capability information via the network communication unit 225. As a result, the printer capability information is stored in the printer database 510 of the cloud print service 500. In addition, in the printer database 510, the value of the printer's IPP attribute "printer-icons" is updated with the URL of the cloud icon 601. Note that the printer capability information is a part of the first information, but the printer capability information and the cloud icon 601 are transmitted with a time difference. This allows the printer capability information and the cloud icon 601 to be transmitted quickly. In contrast, for example, if the printer capability information and the cloud icon 601 are transmitted together in a state where the maximum communication speed between the cloud print-compatible printer 202 and the cloud print service 500 is relatively slow, it may take a long time to transmit them. Then, after performing step S706, the process ends.
[0042] In step S707 after step S700 or step S702, the CPU 222 judges whether or not a request for printer capability information has been received from the client computer 100. Thus, in this embodiment, the CPU 222 has a function as a request judgment means for judging whether or not a request for printer capability information has been received. This judgment process is executed based on whether or not the value of "printer-icons" in the IPP operation "Get-Printer-Attributes" has been requested from the client computer 100. If a request has been received from the client computer 100, it is judged that a request for printer capability information has been received. If no request has been received from the client computer 100, it is judged that a request for printer capability information has not been received. Then, if it is judged that a request for printer capability information has been received as a result of the judgment in step S707, the process proceeds to step S708. On the other hand, if it is judged that a request for printer capability information has not been received as a result of the judgment in step S707, the process ends.
[0043] In step S708, the CPU 222 transmits the value of "printer-icons" requested in step S707 to the client computer 100 via the network communication unit 225. This value is a URL indicating the local icon 602, and is included in the second information. An example of this URL is "http: / / <IP address of the printer> / icon / <icon file name>". The client computer 100 can obtain the local icon 602 from this URL using the Get method of HTTP or the like. In addition, the printer capability information is included as part of the second information. In step S708, it is preferable to transmit the local icon 602 and the printer capability information to the client computer 100 together. Incidentally, the arrangement distance between the cloud print-compatible printer 202 and the client computer 100 is usually shorter than the arrangement distance between the cloud print-compatible printer 202 and the cloud print service 500. As a result, even if the local icon 602 and printer capability information are sent together, relatively fast transmission is possible regardless of the maximum communication speed between the cloud print-compatible printer 202 and the client computer 100, for example. Note that in step S708, the transmission of the first information including the cloud icon 601 is restricted. This makes it possible to prevent the client computer 100 from receiving the first information in step S708 and storing the first information in error in the client computer 100. Note that in step S708, capability information of the cloud print-compatible printer 202 may be notified to the client computer 100 in addition to the URL used to acquire the icon image. Then, after step S708 is executed, the process ends.
[0044] As described above, the cloud print-compatible printer 202 can provide an icon according to the connection state to the cloud print service 500 and the client computer 100. Also, as described above, if it is determined in step S707 that there is no request for printer capability information, the process ends. As a result, the second information is not sent to the client computer 100, and therefore, for example, unnecessary storage of the second information in the client computer 100 can be prevented.
[0045] FIG. 8 is a flowchart showing the process executed by the client computer. Here, an icon acquisition process in which the client computer 100 acquires an icon will be described. As shown in FIG. 8, in step S800, the OS 1053 of the client computer 100 searches for the cloud print-compatible printer 200 using a predetermined protocol. This protocol is not particularly limited, and for example, WSD (Web Services for Devices) or IPP (Internet Printing Protocol) can be used. Then, the OS 1053 lists and displays the identification information of the cloud print-compatible printer 200 as the search result on the monitor 110. In addition, when a valid account of the cloud print service 500 is registered, the accessible cloud print-compatible printer 200 in the tenant of the cloud print service 500 of the account is also listed.
[0046] In step S801, the user 5000 performs a registration operation to register the cloud print-compatible printer 200 listed in step S800. Specifically, the user 5000 selects identification information of the cloud print-compatible printer 200 to be registered in the OS 1053 from the information of the cloud print-compatible printer 200 listed in step S800.
[0047] In step S802, the OS 1053 generates a print queue based on the identification information of the cloud print-compatible printer 200 selected in step S801, thereby determining the cloud print-compatible printer 200 from which the icon is to be acquired.
[0048] In step S803, the OS 1053 determines whether the cloud print-compatible printer 200 determined in step S802 is on the cloud print service 500, i.e., is a cloud print-compatible printer 200 in a first connection state. If it is determined in step S803 that the cloud print-compatible printer 200 is on the cloud print service 500, the process proceeds to step S804. On the other hand, if it is determined in step S803 that the cloud print-compatible printer 200 is not on the cloud print service 500, the process proceeds to step S806.
[0049] In step S804, the OS 1053 inquires of the cloud print service 500 about the capability information of the cloud print-compatible printer 200 determined in step S802. This allows the capability information of the cloud print-compatible printer 200 to be acquired from the cloud print service 500. The capability information also includes the URL of the storage that stores the icon. The capability information is acquired using the IPP operation "Get-Printer-Attributes". The IPP attributes to be set during this use are determined by the OS 1053. In this embodiment, the OS 1053 acquires the capability information using "Get-Printer-Attributes" in order to acquire the icon from the cloud print service 500. At this time, it is necessary to set the IPP attribute "printer-icons". Then, the OS 1053 can acquire the URL in which the icon is stored, which is included in the capability information, from the cloud print service 500. Even if the explicit IPP attribute is omitted from "Get-Printer-Attributes" in order to acquire the capability information, the values of all the IPP attributes can be acquired by setting "all".
[0050] In step S805, the OS 1053 performs an acquisition process to acquire an icon (icon image). Specifically, the OS 1053 transmits an HTTP Get request to the URL value of the IPP attribute "printer-icons" acquired in step S804. This makes it possible to attempt to acquire the cloud icon 601. Note that if multiple URLs are saved, it may be possible to attempt to acquire an icon for each of the URLs. After executing step S805, the process proceeds to step S808.
[0051] In step S806 after step S803 is executed, the OS 1053 queries the local printer existing in the same intranet as the client computer 100 for the capability information of the cloud print-compatible printer 200 determined in step S802. This makes it possible to acquire the capability information of the local printer. The capability information here is acquired using "Get-Printer-Attributes" in the same way as the capability information in step S804. At that time, attributes including the IPP attribute "printer-icons" are requested. Then, if the value of the IPP attribute "printer-icons" can be acquired correctly, the value indicates the path of the group of local icons held by the local printer.
[0052] In step S807, the OS 1053 performs an acquisition process to acquire an icon (icon image). Specifically, similar to step S805, the OS 1053 transmits an HTTP Get request to the URL value of the IPP attribute "printer-icons" acquired in step S806. This makes it possible to attempt to acquire the local icon 602. Note that if multiple URLs are saved, it may be possible to attempt to acquire an icon for each URL. After executing step S807, the process proceeds to step S808.
[0053] In step S808, OS 1053 determines whether or not the cloud icon 601 attempted to be acquired in step S805, or the local icon 602 attempted to be acquired in step S807, was successfully acquired. If it is determined in step S808 that the icon was successfully acquired, the process proceeds to step S809. On the other hand, if it is determined in step S808 that the icon was not successfully acquired, the process proceeds to step S810. Note that the process also proceeds to step S810 if a valid URL is not stored in the IPP attribute "printer-icons".
[0054] In step S809, the OS 1053 stores the file path of the storage in order to link the icon acquired in step S808 to the print queue. After step S809 is executed, the process proceeds to step S811.
[0055] In step S810, the OS 1053 stores the path of a default icon held to be linked to the print queue. This default icon is an icon stored in advance by the OS 1053. In step S810, the OS 1053 may change the icon depending on the type of the cloud print-compatible printer 200 determined in step S802. For example, if the type of the cloud print-compatible printer 200 determined in step S802 is a cloud printer, the icon of the normal cloud print-compatible printer 200 may be changed to an icon with a cloud image added thereto. After executing step S810, the process proceeds to step S811.
[0056] In step S811, the OS 1053 stores an icon in association with the print queue based on the printer name in step S800, the capability information acquired in steps S804 and S806, and the path of the icon stored in steps S809 and S810. After step S811 is executed, the process ends.
[0057] FIG. 9 is a diagram showing an example of a screen displayed on a client computer. A screen 900 shown in FIG. 9 is displayed on the monitor 110 of the client computer 100. This screen 900 includes information 901 and information 902. The information 901 includes a cloud icon 601 and a local icon 602 acquired by an icon acquisition processing program based on the flowchart shown in FIG. 8. The cloud icon 601 is an icon indicating the cloud print-compatible printer 200 connected to the client computer 100 via the cloud print service 500, i.e., in a first connection state. The local icon 602 is an icon indicating the cloud print-compatible printer 200 connected to the client computer 100 by a local connection, i.e., in a second connection state. As described above, the cloud icon 601 and the local icon 602 have different visibility. This makes it easy to distinguish which connection state the icon is in when selecting one of the cloud icon 601 and the local icon 602. For example, when the cloud print-compatible printer 200 in the first connection state is desired as the output destination, the cloud icon 601 can be selected without mistake. When the cloud print-compatible printer 200 in the second connection state is desired as the output destination, the local icon 602 can be selected without mistake. Furthermore, the information 901 includes a name 903 arranged adjacent to the cloud icon 601 and a name 904 arranged adjacent to the local icon 602. The name 903 is the name of the cloud print-compatible printer 200 in the first connection state, "cloud printer A". The name 904 is the name of the cloud print-compatible printer 200 in the second connection state, "local printer A". The names 903 and 904 allow the cloud icon 601 and the local icon 602 to be more reliably distinguished from each other.
[0058] The information 902 includes a cloud icon 905, a local icon 906, a name 907, and a name 908. Here, it is assumed that the printing system 1000 has a cloud print-compatible printer (hereinafter referred to as "another cloud print-compatible printer") different from the cloud print-compatible printer 200. The cloud icon 905 is displayed by default in place of the icon of the other cloud print-compatible printer in the first connection state when the other cloud print-compatible printer in the first connection state does not have an icon indicating the printer. The local icon 906 is displayed by default in place of the icon of the other cloud print-compatible printer in the second connection state when the other cloud print-compatible printer in the second connection state does not have an icon indicating the printer. The cloud icon 905 and the local icon 906 have different visibility. This makes it easy to distinguish which icon is the icon of the other cloud print-compatible printer in which connection state when selecting one of the cloud icon 905 and the local icon 906. For example, when a user wants to set the other cloud print-compatible printer in the first connection state as the output destination, the user can select the cloud icon 905 without mistake. Also, when another cloud print-compatible printer in the second connection state is to be used as the output destination, the local icon 906 can be selected without mistake. Also, the difference in visibility between the cloud icon 905 and the local icon 906 will be compared with the difference in visibility between the cloud icon 601 and the local icon 602. In this case, the latter icon is easier to distinguish from the other icons than the former. The name 907 is arranged adjacent to the cloud icon 905. The name 907 is the name of another cloud print-compatible printer in the first connection state, "Cloud Printer B". The name 908 is arranged adjacent to the local icon 906. The name 908 is the name of another cloud print-compatible printer in the second connection state, "Local Printer B".
[0059] In addition, when there is an icon acquisition request from the print setting expanding application 1052 for an icon acquired by an icon acquisition processing program based on the flowchart shown in FIG. 8, the OS 1053 may respond to the request. Then, the print setting expanding application 1052 may associate the print queue with the icon and store it in a local area of the print setting expanding application 1052. This "local area" is a storage area that is readable and writable on the print setting expanding application 1052. The icon stored in the local area is displayed on a printer information screen that displays printer information managed by the print setting expanding application 1052. FIG. 10 is a diagram showing an example (modified example) of a screen displayed on a client computer. A screen 1010 shown in FIG. 10 is a printer information screen. This screen 1010 is displayed by selecting the print setting expanding application 1052 on a screen that displays a list of applications installed on the client computer 100. The screen 1010 displays a list of printers associated with the print setting expanding application 1052.
[0060] The screen 1010 includes a cloud icon 601 and a name 903 related to the cloud print-compatible printer 200 in the first connection state, and a local icon 602 and a name 904 related to the cloud print-compatible printer 200 in the second connection state. The screen 1010 also includes a cloud icon 905 and a name 907 related to another cloud print-compatible printer in the first connection state, and a local icon 906 and a name 908 related to another cloud print-compatible printer in the second connection state. The screen 1010 also includes remaining ink or toner information 1011, remaining ink or toner information 1012, remaining ink or toner information 1013, and remaining ink or toner information 1014. The screen 1010 also includes status information 1015, status information 1016, status information 1017, and status information 1018.
[0061] The remaining ink or toner amount information 1011 is information included in the first information and indicates the remaining amount of ink or toner when the first information is sent from the cloud print-compatible printer 200 in the first connection state. The status information 1015 is information included in the first information and indicates the status when the first information is sent from the cloud print-compatible printer 200 in the first connection state. The remaining ink or toner amount information 1012 is information included in the second information and indicates the remaining amount of ink or toner when the second information is sent from the cloud print-compatible printer 200 in the second connection state. The status information 1016 is information included in the second information and indicates the status when the second information is sent from the cloud print-compatible printer 200 in the second connection state. The remaining ink or toner amount information 1013 is information included in the first information and indicates the remaining amount of ink or toner when the first information is sent from another cloud print-compatible printer in the first connection state. Status information 1017 is information included in the first information and indicates the status when the first information is sent from another cloud print-compatible printer in the first connection state. Remaining ink or toner amount information 1014 is information included in the second information and indicates the remaining amount of ink or toner when the second information is sent from another cloud print-compatible printer in the second connection state. Status information 1018 is information included in the second information and indicates the status when the second information is sent from another cloud print-compatible printer in the second connection state. With such remaining amount information and status information, the remaining amount and status of ink or toner of each printer can be confirmed (understood).
[0062] <Second embodiment> Hereinafter, the second embodiment will be described with reference to Figs. 11 to 13. The differences from the above-mentioned embodiment will be mainly described, and the description of the similar matters will be omitted. In the first embodiment, the icon acquired by the OS 1053 is displayed, and further, when an icon acquisition request is made from the print setting extending application 1052, the icon is displayed on the printer information screen (screen 1010) managed by the print setting extending application 1052. In this embodiment, a configuration will be described in which the icon acquired by the print setting extending application 1052 is displayed on the printer information screen, and further, the icon acquired by the OS 1053 is displayed. Fig. 11 is a flowchart showing a process executed by the client computer according to the second embodiment. An icon acquisition process in which the print setting extending application 1052 of the client computer 100 acquires an icon will be described with reference to this Fig. 11. Fig. 12 is a diagram showing an example of a screen displayed on the client computer. A screen 1200 shown in Fig. 12 is a print dialogue displayed on the monitor 110 under the control of the OS 1053 when data created on the application 1051 of the client computer 100 is printed. The screen 1200 includes a list box 1201. In the list box 1201, one printer can be selected from a plurality of printers displayed in a list. In Fig. 12, as an example, "Printer A", "Printer B", and "Printer C" are displayed in the list box 1201, and "Printer A" is selected from these. The program based on the flowchart shown in Fig. 11 is started when one printer is selected from the list box 1201 and the OS 1053 calls the print setting extension application 1052.
[0063] 11, in step S1101, the print setting extending application 1052 acquires printer capability information from the cloud print service 500. This capability information acquisition process is executed by the print setting extending application 1052 using an API provided by the OS 1053 to transmit a request to acquire printer capability information to the cloud print service 500. Specifically, the print setting extending application 1052 acquires capability information shown in a list box 1201 (see FIG. 12) from the cloud print service 500 using "Get-Printer-Attributes" defined in IPP. Note that the printer capability information may include unique information that is not defined in IPP.
[0064] In step S1102, the print setting expanding application 1052 judges whether an icon corresponding to the printer selected from the list box 1201 has already been stored, that is, whether an icon exists. This judgment process is executed based on whether the print setting expanding application 1052 has stored an icon associated with the print queue of the printer selected from the list box 1201. If an icon image corresponding to the print queue has been stored, or if a default icon image has been stored as the icon image corresponding to the print queue, it is judged that the icon has already been stored. Then, if it is judged that the icon has already been stored as a result of the judgment in step S1102, the process ends. On the other hand, if it is judged that the icon has not been stored as a result of the judgment in step S1102, the process proceeds to step S1103.
[0065] In step S1103, the print setting extension application 1052 uses an API provided by the OS 1053 to obtain the URL of a storage in which an icon corresponding to the cloud print-compatible printer 200 is stored. If the cloud print-compatible printer 200 is a cloud printer, the OS 1053 sends an IPP operation "Get-Printer-Attributes" to the cloud print service 500. At that time, the IPP attribute "printer-icons" is set as an argument of this operation. This makes it possible to request the cloud print service 500 for the value of the IPP attribute "printer-icons". The cloud print service 500 that has received the capability acquisition request sends the value of the IPP attribute "printer-icons" of the cloud print-compatible printer 200 to the client computer 100. On the other hand, if the cloud print-compatible printer 200 is a local printer, the value of the IPP attribute "printer-icons" for the local printer is acquired.
[0066] In step S1104, the print setting extension application 1052 determines whether the printer selected from the list box 1201 is the cloud print-compatible printer 200 on the cloud print service 500. This determination process is executed based on whether the driver of the printer selected from the list box 1201 is the cloud printer driver 1057 or the IPP standard driver 1058. If it is the cloud printer driver 1057, it is determined that the printer selected from the list box 1201 is the cloud print-compatible printer 200 on the cloud print service 500. If it is the IPP standard driver 1058, it is determined that the printer selected from the list box 1201 is not the cloud print-compatible printer 200 on the cloud print service 500. Then, if it is determined that the printer selected from the list box 1201 is the cloud print-compatible printer 200 on the cloud print service 500 as a result of the determination in step S1104, the process proceeds to step S1105. On the other hand, if it is determined in step S1104 that the printer is not a cloud print-compatible printer 200 on the cloud print service 500, the process proceeds to step S1106.
[0067] In step S1105, the print setting extension application 1052 sends an HTTP Get request to the URL that is the value of the IPP attribute "printer-icons" acquired in step S1103. This allows the cloud print service 500 to receive this Get request. Then, the cloud print service 500 sends the cloud icon 601 stored in the URL to the print setting extension application 1052. This allows the cloud icon 601 to be acquired from the cloud print service 500. After step S1105 is executed, the process proceeds to step S1107.
[0068] In step S1106, the print setting extension application 1052 sends a request to the URL that is the value of the IPP attribute "printer-icons" acquired in step S1103 to acquire the local icon 602. This makes it possible to acquire the local icon 602 from the local printer. After executing step S1106, the process proceeds to step S1107.
[0069] In step S1107, the print setting extension application 1052 determines whether or not the icon was acquired (received) in step S1105 or step S1106. If it is determined in step S1107 that the icon was acquired, the process proceeds to step S1108. On the other hand, if it is determined in step S1107 that the icon was not acquired, the process proceeds to step S1109.
[0070] In step S1108, the print setting expanding application 1052 associates the icon acquired in step S1105 or step S1106 with the printer selected in step S1102, and saves the icon in the local area of the print setting expanding application 1052. After step S1108 is executed, the process proceeds to step S1110.
[0071] In step S1109, the print setting expanding application 1052 stores the default icon, which is a general-purpose printer icon saved in the local area, as the printer icon here. This allows the icon provided by the print setting expanding application 1052 to be displayed even if, for example, icon acquisition cannot be executed. After step S1108 is executed, the process proceeds to step S1110.
[0072] In step S1110, the print setting extension application 1052 provides the icon acquired in the processing up to this point to the OS 1053. This allows the OS 1053 to associate the icon with the print queue of the printer selected in step S1102 and save it. The OS 1053 also stores the icon in a storage area of the OS 1053. This "storage area" refers to an area that the OS 1053 can refer to but the print setting extension application 1052 cannot refer to. After step S1110 is executed, the processing ends.
[0073] Through the above-described processing, the print setting extension application 1052 can display the screen 1010 shown in Fig. 10. Also, the icon acquired in step S1110 is provided to the OS 1053. As a result, the screen 900 shown in Fig. 9 can be displayed. In both the screen 1010 and the screen 900, the cloud icon 601 and the local icon 602 can be easily distinguished from each other.
[0074] In the flowchart shown in FIG. 11, by selecting a printer, the print setting extending application 1052 executes an icon image acquisition process. The timing of executing the icon image acquisition process is not limited to the timing of selecting a printer, and may be, for example, the timing when the user 5000 starts the print setting extending application 1052. Here, the icon image acquisition process is executed at the timing when the print setting extending application 1052 is started. FIG. 13 is a flowchart (modification) showing the process executed by the client computer. The program based on the flowchart shown in FIG. 13 is started by the user 5000 opening the print setting extending application 1052 and the OS 1053 issuing an instruction to start the print setting extending application 1052.
[0075] As shown in FIG. 13, in step S1301, the print setting extending application 1052 acquires a list of printers linked to the print setting extending application 1052. Specifically, the print setting extending application 1052 acquires information of a print queue managed by the OS 1053. Then, the print setting extending application 1052 judges whether or not the value of "package family name" stored in the property of this print queue is the same as the value of "package family name" stored by the print setting extending application 1052. "Package family name" is application identification information. The OS 1053 can call an application corresponding to the print queue selected by the user by storing the print queue and the application identification information in association with each other. The print setting extending application 1052 can specify the print queue linked to the print setting extending application 1052 by referring to the value of "device package family name" of each print queue. In step S1301, the list of printers may be acquired by using an API passed from the OS 1053 when the print setting extending application 1052 is opened.
[0076] In step S1302, the print setting extension application 1052 acquires the capabilities of each print queue in the printer list acquired in step S1301.
[0077] In step S1303, the print setting extending application 1052 determines whether an icon corresponding to each print queue in the printer list acquired in step S1301 has already been stored. Specifically, the print setting extending application 1052 determines whether an icon has been stored in the local area of the print setting extending application 1052, for example, by referring to the model name or HWID associated with the print queue. If it is determined in step S1303 that an icon corresponding to each print queue has been stored, the process proceeds to step S1312. On the other hand, if it is determined in step S1303 that an icon corresponding to each print queue has not been stored, the process proceeds to step S1304.
[0078] In step S1304, the print setting extending application 1052 selects one print queue in which an icon is not stored. Then, the print setting extending application 1052 uses an API provided by the OS 1053 to request acquisition of the URL of the storage in which an icon corresponding to the selected print queue is stored. Note that the command used in step S1304 is the same as that in step S1103. Also, the cloud print service 500 receives the URL acquisition request from the print setting extending application 1052 and transmits the URL. This allows the print setting extending application 1052 to receive the URL of the storage in which the icon is stored from the cloud print service 500. Note that the print setting extending application 1052 can also receive the URL of the storage in which the icon is stored from the local printer that has received the acquisition request.
[0079] In step S1305, the print setting extension application 1052 determines whether the printer in the print queue selected in step S1304 is the cloud print-compatible printer 200 on the cloud print service 500. If it is determined in step S1305 that the printer is the cloud print-compatible printer 200 on the cloud print service 500, the process proceeds to step S1306. On the other hand, if it is determined in step S1305 that the printer is not the cloud print-compatible printer 200 on the cloud print service 500, the process proceeds to step S1307.
[0080] In step S1306, the print setting extension application 1052 acquires the cloud icon 601 from the cloud print service 500 using the URL received in step S1304.
[0081] In step S1307, the print setting extension application 1052 acquires the local icon 602 from the local printer using the URL received in step S1304.
[0082] In step S1308, the print setting extension application 1052 determines whether or not the icon was acquired in step S1306 or step S1307. If it is determined in step S1308 that the icon was acquired, the process proceeds to step S1309. On the other hand, if it is determined in step S1308 that the icon was not acquired, the process proceeds to step S1310.
[0083] In step S1309, the print setting expanding application 1052 associates the icon acquired in step S1306 or step S1307 with the print queue selected in step S1304, and saves the icon in the local area of the print setting expanding application 1052.
[0084] In step S1310, the print setting expansion application 1052 associates a default icon with the print queue based on the HWID and COID (Compatible ID) associated with the print queue, and saves the associated default icon in the local area of the print setting expansion application 1052.
[0085] In step S1311, the print setting extending application 1052 provides the icon acquired in the processing up to this point to the OS 1053. As a result, the OS 1053 can receive the icon and save the icon in association with the print queue of the printer selected in step S1304. The OS 1053 also stores the icon in its own storage area. After step S1311 is executed, the processing returns to step S1302, and the subsequent steps are executed in sequence. Furthermore, by repeating steps S1304 to S1311, icons can be stored for all print queues corresponding to the print setting extending application 1052.
[0086] In step S1312 after step S1303, the print setting extension application 1052 displays the screen 1010 shown in Fig. 10. As described above, the cloud icon 601 and the local icon 602 can be easily distinguished from each other on the screen 1010. Note that the timing for executing the icon image acquisition process can be a combination of the timing for selecting a printer and the timing for starting the print setting extension application 1052.
[0087] <Third embodiment> Hereinafter, the third embodiment will be described with reference to FIG. 14 and FIG. 15. The differences from the above-mentioned embodiment will be mainly described, and the description of the similar matters will be omitted. In this embodiment, a configuration in which the OS 1053 and the print setting extending application 1052 each acquire an icon in order to maintain the security of the print system 1000 will be described. In this embodiment, the OS 1053 acquires an icon from the local printer or the cloud print service 500 when generating a print queue on the client computer 100. This acquisition process has been described with reference to FIG. 8, so the description here will be omitted. In this embodiment, since the OS 1053 and the print setting extending application 1052 each acquire an icon, unlike the first embodiment, there is no icon acquisition request from the print setting extending application 1052. There are two timings for the print setting extending application 1052 to acquire an icon. The first timing is the timing when a printer is selected using another application different from the print setting extending application 1052. The second timing is when the print setting extension application 1052 is selected on a list screen of applications stored in the client computer 10, and the print setting extension application 1052 is started up.
[0088] First, the process of acquiring an icon at the first timing will be described with reference to Fig. 14. Fig. 14 is a flowchart showing the process executed by a client computer according to the third embodiment. Steps S1401 to S1409 in the flowchart shown in Fig. 14 are similar to steps S1101 to S1109 in the flowchart shown in Fig. 11. The flowchart shown in Fig. 14 omits the process corresponding to step S1110 in the flowchart shown in Fig. 11, that is, the process in which the print setting extension application 1052 provides an icon to the OS 1053.
[0089] Next, the process of acquiring an icon at the second timing will be described with reference to Fig. 15. Fig. 15 is a flowchart (variation) showing the process executed by a client computer. Steps S1501 to S1510 and S1512 in the flowchart shown in Fig. 15 are similar to steps S1301 to S1310 and S1312 in the flowchart shown in Fig. 13. Furthermore, the process equivalent to step S1311 in the flowchart shown in Fig. 13, i.e., is omitted in the flowchart shown in Fig. 15.
[0090] As described above, when the OS 1053 generates a print queue on the client computer 100, the OS 1053 acquires an icon from the local printer or the cloud print service 500. This allows the print setting extending application 1052 to omit a process of providing an icon to the OS 1053. In addition, in this embodiment, the OS 1053 and the print setting extending application 1052 can each acquire an icon. As a result, the cloud icon 601 and the local icon 602 that can be distinguished from each other are displayed on both the screen provided by the print setting extending application 1052 and the screen provided by the OS 1053. Note that the print setting extending application 1052 may be capable of acquiring an icon only at one of the two timings described above. That is, the icon may be acquired only at the first timing, or may be acquired only at the second timing.
[0091] <Fourth embodiment> Hereinafter, the fourth embodiment will be described with reference to Figs. 16 to 18. The differences from the above-mentioned embodiment will be mainly described, and the description of the similar matters will be omitted. In this embodiment, a configuration in which the cloud icon 601 and the local icon 602 are acquired from the icon distribution server 1600 will be described. Fig. 16 is a schematic diagram showing an outline of the configuration of the printing system according to the fourth embodiment. As shown in Fig. 16, in this embodiment, the printing system 1000 further includes an icon distribution server 1600 communicably connected via the network 150. The icon distribution server 1600 is a server that transmits an icon corresponding to the request to the client computer 100 when an icon acquisition request is made from the client computer 100. In this embodiment, the print setting extending application 1052 acquires an icon from the icon distribution server 1600. There are two timings for the print setting extending application 1052 to acquire the icon. The first timing is a timing when a printer is selected using an application different from the print setting extending application 1052. The second timing is when the print setting extension application 1052 is selected on a list screen of applications stored in the client computer 10, and the print setting extension application 1052 is started up.
[0092] First, the process of acquiring an icon at the first timing will be described with reference to Fig. 17. Fig. 17 is a flowchart showing the process executed by a client computer according to the fourth embodiment. Steps S1701 and S1702 in the flowchart shown in Fig. 17 are similar to steps S1101 and S1102 in the flowchart shown in Fig. 11. Then, if it is determined in step S1702 that the icon has already been stored, the process ends. On the other hand, if it is determined in step S1702 that the icon has not been stored, the process proceeds to step S1703.
[0093] In step S1703, the print setting extension application 1052 determines whether the printer selected from the list box 1201 is the cloud print-compatible printer 200 on the cloud print service 500. If it is determined in step S1703 that the printer is the cloud print-compatible printer 200 on the cloud print service 500, the process proceeds to step S1704. On the other hand, if it is determined in step S1703 that the printer is not the cloud print-compatible printer 200 on the cloud print service 500, the process proceeds to step S1705.
[0094] In step S1704, the print setting extending application 1052 requests the icon distribution server 1600 to obtain the cloud icon 601. Specifically, the print setting extending application 1052 uses the HTTP Get method to inquire of the icon distribution server 1600 about the model name of the cloud print-compatible printer 200 determined in step S1703 and information about the first connection state. Then, if the icon distribution server 1600 stores the cloud icon 601 indicating the cloud print-compatible printer 200, it transmits the cloud icon 601 to the client computer 100. This allows the print setting extending application 1052 to obtain the cloud icon 601 from the icon distribution server 1600. After executing step S1704, the process proceeds to step S1706.
[0095] In step S1705, the print setting expanding application 1052 requests the icon distribution server 1600 to acquire the local-use icon 602. Specifically, the print setting expanding application 1052 queries the icon distribution server 1600 for information on the second connection state. Then, if the icon distribution server 1600 stores the local-use icon 602 indicating the corresponding cloud print-compatible printer 200, it transmits the local-use icon 602 to the client computer 100. This allows the print setting expanding application 1052 to acquire the local-use icon 602 from the icon distribution server 1600. After executing step S1705, the process proceeds to step S1706.
[0096] In step S1706, the print setting extension application 1052 determines whether or not the icon was acquired in step S1704 or step S1705. If it is determined in step S1706 that the icon was acquired, the process proceeds to step S1707. On the other hand, if it is determined in step S1706 that the icon was not acquired, the process proceeds to step S1708.
[0097] In step S1707, the print setting expanding application 1052 associates the icon acquired in step S1704 or step S1705 with the printer selected in step S1702, and saves the icon in the local area of the print setting expanding application 1052. After step S1707, the process proceeds to step S1709.
[0098] In step S1708, the print setting expanding application 1052 stores the default icon, which is a general-purpose printer icon saved in the local area, as the printer icon here. After step S1708 is executed, the process proceeds to step S1709.
[0099] In step S1709, the print setting extending application 1052 provides the icon acquired in the processing up to this point to the OS 1053. As a result, the OS 1053 associates the icon with the print queue of the printer selected in step S1702 and saves it, and also stores the icon in a storage area of the OS 1053. Through the above processing, the cloud icon 601 or the local icon 602 is stored in both the local area of the print setting extending application 1052 and the storage area of the OS 1053.
[0100] Next, the process of acquiring an icon at the second timing will be described with reference to FIG. 18. FIG. 18 is a flowchart (modification) showing the process executed by the client computer. Steps S1801 to S1803 in the flowchart shown in FIG. 18 are similar to steps S1301 to S1303 in the flowchart shown in FIG. 13. Then, as a result of the determination in step S1803, if it is determined that an icon image corresponding to each print queue is stored, the process proceeds to step S1812. Note that step S1812 is similar to step S1312 in the flowchart shown in FIG. 13. On the other hand, as a result of the determination in step S1803, if it is determined that an icon image corresponding to each print queue is not stored, the process proceeds to step S1804.
[0101] In step S1804, the print setting extension application 1052 selects one print queue for which an icon is not stored, and determines whether or not the printer of the print queue is the cloud print-compatible printer 200 on the cloud print service 500. If it is determined in step S1804 that the printer is the cloud print-compatible printer 200 on the cloud print service 500, the process proceeds to step S1805. On the other hand, if it is determined in step S1805 that the printer is not the cloud print-compatible printer 200 on the cloud print service 500, the process proceeds to step S1806.
[0102] Steps S1805 to S1810 are similar to steps S1704 to S1709 in the flowchart shown in FIG.
[0103] <Fifth embodiment> Hereinafter, the fifth embodiment will be described with reference to FIG. 19, but the differences from the above-mentioned embodiment will be mainly described, and the description of the similar matters will be omitted. In this embodiment, a configuration in which the icon acquired from the cloud print service 500 and the icon acquired from the local printer are the same will be described. FIG. 19 is a diagram showing an example of an icon indicating a cloud print-compatible printer according to the fifth embodiment. As shown in FIG. 19(a), an icon 1902 that roughly imitates the appearance of the cloud print-compatible printer 200 is acquired from the cloud print service 500. As shown in FIG. 19(b), an icon 19602 that roughly imitates the appearance of the cloud print-compatible printer 200 is also acquired from the cloud print-compatible printer 200, which is a local printer, in the same manner as in FIG. 19(a). An icon 1902 shown in Fig. 19(a) and an icon 1902 shown in Fig. 19(b) are the same icon. In this case, the print setting extending application 1052 generates an icon 1901 by adding a cloud 1903 that roughly imitates the appearance of a cloud to the icon 1902 shown in Fig. 19(a). This icon 1901 can be used as a cloud icon. On the other hand, the icon 1902 shown in Fig. 19(b) can be used as a local icon as it is.
[0104] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to the above-mentioned embodiments, and various modifications and changes are possible within the scope of the gist of the present invention. The present invention can also be realized by supplying a program that realizes one or more functions of the above-mentioned embodiments to a system or device via a network or storage medium, and having one or more processors of a computer in the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that realizes one or more functions.
[0105] The disclosure of each embodiment includes the following configurations, methods, and programs. (Configuration 1) A printing device capable of being in a first connection state in which the printing device is communicatively connected to an information processing device via a server, and in a second connection state in which the printing device is communicatively connected to the information processing device without the server, a storage means for storing a first icon indicating the printing device in the first connection state and a second icon indicating the printing device in the second connection state, the second icon having a different visibility from the first icon; a transmitting means for transmitting first information including the first icon to the server in the first connection state, and for transmitting second information including the second icon to the information processing device in the second connection state. (Configuration 2) The printing device described in configuration 1, characterized in that the transmitting means restricts the transmission of the second information when in the first connection state, and restricts the transmission of the first information when in the second connection state. (Configuration 3) An operation unit for performing a registration operation of the printing device to the server; 3. The printing device according to claim 1, further comprising: an operation determination unit that determines whether or not the registration operation has been performed. (Configuration 4) The printing device described in configuration 3, wherein the transmission means is capable of transmitting the first information when the operation judgment means determines that the registration operation has been performed, and of transmitting the second information when the operation judgment means determines that the registration operation has not been performed. (Configuration 5) A request determination unit is provided for determining whether or not the information processing device requests the output information when the operation determination unit determines that the registration operation has not been performed, The printing device described in configuration 4, wherein the transmitting means transmits the second information when the request determination means determines that there is a request for the output information, and does not transmit the second information when the request determination means determines that there is no request for the output information. (Configuration 6) The first information includes output information regarding an output condition of the printing device, 6. The printing device according to any one of configurations 1 to 5, wherein the transmission means transmits the first icon and the output information with a time difference. (Configuration 7) The second information includes output information related to an output condition of the printing device, 7. The printing device according to any one of configurations 1 to 6, wherein the transmission means transmits the second icon and the output information together. (Configuration 8) The printing device according to any one of configurations 1 to 7, wherein the first icon and the second icon have different shapes. (Configuration 9) The first icon includes an external view that roughly simulates an external view of the printing device and a connection state view that indicates the first connection state, 9. The printing device according to any one of configurations 1 to 8, wherein the second icon includes the external view. (Configuration 10) The printing device according to configuration 9, wherein the connection state diagram is a diagram that roughly mimics the appearance of a cloud. (Configuration 11) A printing means for printing on a recording medium with one of a printing material of ink and a toner; a remaining amount detection means for detecting a remaining amount of the printing material, the first information includes a remaining amount of the printing material at the time of sending the first information; 11. The printing device according to any one of configurations 1 to 10, wherein the second information includes a remaining amount of the printing material at the time the second information is sent. (Configuration 12) A status detection unit is provided for detecting a status of the printing device, the first information includes status information of the printing device at the time the first information is sent; 12. The printing device according to any one of configurations 1 to 11, wherein the second information includes status information of the printing device at the time the second information is sent. (Configuration 13) The printing device according to any one of configurations 1 to 12, further comprising a state determination means for determining whether the printing device is in the first connection state or the second connection state. (Configuration 14) A printing device described in any one of configurations 1 to 13, characterized in that the information processing device is communicatively connected to an information processing device that is capable of acquiring the first information from the server and selecting the first icon included in the first information, and is capable of acquiring the second information from the information processing device and selecting the second icon included in the second information. (Method 1) A method for controlling a printing device capable of being in a first connection state in which the printing device is communicatively connected to an information processing device via a server, and in a second connection state in which the printing device is communicatively connected to the information processing device without going through the server, comprising: a first icon indicating the printing device in the first connection state and a second icon indicating the printing device in the second connection state, the second icon having a different visibility from the first icon, The method for controlling the printing device includes: A control method for a printing device, comprising: a transmitting means for transmitting first information including the first icon to the server when in the first connection state; and transmitting second information including the second icon to the information processing device when in the second connection state. (Configuration 16) A program for causing a computer to execute each of the means of the printing device according to any one of configurations 1 to 15. [Explanation of symbols]
[0106] 100 client computers 200, 201, 202 Cloud Print compatible printers 222 CPU 225 Network Communication Department 227 Operation section 228 Printing Department 229 Printer information storage unit (storage means) 500 Cloud Print Service 601 Cloud Icon (1st Icon) 602 Local icon (second icon)
Claims
1. A printing device capable of being in a first connection state in which the printing device is communicatively connected to an information processing device via a server, and in a second connection state in which the printing device is communicatively connected to the information processing device without the server, a storage means for storing a first icon indicating the printing device in the first connection state and a second icon indicating the printing device in the second connection state, the second icon having a different visibility from the first icon; a transmitting means for transmitting first information including the first icon to the server in the first connection state, and for transmitting second information including the second icon to the information processing device in the second connection state.
2. 2. The printing device according to claim 1, wherein the transmission means restricts transmission of the second information when in the first connection state, and restricts transmission of the first information when in the second connection state.
3. an operation unit for performing a registration operation of the printing device with respect to the server; The printing apparatus according to claim 1 , further comprising an operation determination unit that determines whether or not the registration operation has been performed.
4. The printing device according to claim 3, characterized in that the transmission means is capable of transmitting the first information when the operation determination means determines that the registration operation has been performed, and of transmitting the second information when the operation determination means determines that the registration operation has not been performed.
5. a request determination means for determining whether or not there is a request for the output information from the information processing device when it is determined that the registration operation has not been performed as a result of the determination by the operation determination means, The printing device according to claim 4, characterized in that the transmitting means transmits the second information when the request determination means determines that there is a request for the output information, and does not transmit the second information when the request determination means determines that there is no request for the output information.
6. the first information includes output information related to an output condition of the printing device, 2. The printing apparatus according to claim 1, wherein the transmitting means transmits the first icon and the output information with a time difference.
7. the second information includes output information related to an output condition of the printing device, 2. The printing apparatus according to claim 1, wherein the transmission means transmits the second icon and the output information together.
8. The printing device according to claim 1 , wherein the first icon and the second icon have mutually different shapes.
9. the first icon includes an external view that roughly simulates an external view of the printing device and a connection state view that indicates that the printing device is in the first connection state; The printing device according to claim 1 , wherein the second icon includes the external view.
10. 10. The printing device according to claim 9, wherein the connection state diagram is a diagram that roughly simulates the appearance of a cloud.
11. a printing means for printing on a recording medium using one of a printing material of ink and a toner; a remaining amount detection means for detecting a remaining amount of the printing material, the first information includes a remaining amount of the printing material at the time of sending the first information; 2. The printing apparatus according to claim 1, wherein the second information includes a remaining amount of the printing material at the time the second information is sent.
12. a status detection unit for detecting a status of the printing device, the first information includes status information of the printing device at the time the first information is sent; 2. The printing device according to claim 1, wherein the second information includes status information of the printing device at the time the second information is sent.
13. 2. The printing device according to claim 1, further comprising a state determining unit that determines whether the printing device is in the first connection state or the second connection state.
14. The printing device according to claim 1, characterized in that the information processing device is communicatively connected to an information processing device capable of acquiring the first information from the server and selecting the first icon included in the first information, and acquiring the second information from the information processing device and selecting the second icon included in the second information.
15. A method for controlling a printing device capable of being in a first connection state in which the printing device is communicatively connected to an information processing device via a server, and in a second connection state in which the printing device is communicatively connected to the information processing device without the server, comprising: a first icon indicating the printing device in the first connection state and a second icon indicating the printing device in the second connection state, the second icon having a different visibility from the first icon, The method for controlling the printing device includes: A control method for a printing device, comprising a transmitting step of transmitting first information including the first icon to the server when the printing device is in the first connection state, and transmitting second information including the second icon to the information processing device when the printing device is in the second connection state.
16. A program for causing a computer to execute each of the means of the printing device according to claim 1.
Citation Information
Patent Citations
Application for providing print setting screen
JP2022089143A