Printing device, control method and program

Abstract

To solve the problem that a load on a network environment is generated by an extra load generated by performing upload of icon image data and notifying the upload, when a printing device performs communication with a cloud print service.SOLUTION: Upload processing is skipped according to the need for uploading icon image data, so that the upload is performed only when needed.SELECTED DRAWING: Figure 12

Description

[Technical field]

[0001] The present invention relates to a printing device, a control method, and a program for transmitting image data to an external server. [Background technology]

[0002] In recent years, cloud print service mechanisms that allow print jobs to be submitted via the cloud and sent to a printing device are beginning to become popular (Patent Document 1). In such printing systems, an administrator first registers a printing device to the cloud print service (hereinafter also referred to as a print service or CPS) to which the administrator belongs. After that, users who are permitted to use the CPS use their respective client terminals to select a printer registered in the CPS as the output printer, configure the desired print settings, and send a print job to the CPS. The CPS that receives the print job transfers the print job to the printing device. The printing device executes printing based on the transferred print job.

[0003] These cloud printing mechanisms are specified in PWG5100.13, PWG5100.18, RFC3995, and RFC3996, among others, and define a printing protocol called IPP (Internet Printing Protocol). These standards stipulate technology that uses IPP, whereby a printing device obtains the CPS and the URL of the server that stores the printing device's icon image data. The printing device uploads the printing device's icon image data to the obtained icon data storage server, and notifies the CPS of the stored URL path information. The client terminal obtains the URL path information from the CPS and obtains the image icon data from the icon data storage server, making it easier for users to identify the printer when searching for a printer. [Prior art documents] [Patent documents]

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

[0005] Consider a case where a printing device is in a power-disabled state, with power to at least some of the hardware cut off, and the power is enabled by a user instruction. For example, since the status of the printing device, such as the amount of remaining ink or paper, is constantly changing, it is conceivable that the printing device will notify the print service of its capabilities every time it is started up. If the capability notification includes storage information for icon image data, then stored information that is no longer necessary will be notified every time the printing device is started up.

[0006] For example, when changing to high-quality icon image data, or when a change in configuration occurs based on the functions of the printing device, such as adding a paper feed tray or adding a finishing function at the time of paper ejection, the appearance of the printing device may not match the icon. In such cases, it is preferable to re-upload and update the icon image data.

[0007] Depending on the number of icon image data to be registered and the image quality, the size may become large. Except for such cases, updating registered data with the same data places unnecessary load on the network environment, and if it takes a long time to complete the upload, the startup time of the printing device will be delayed, affecting convenience.

[0008] The present invention has been made in consideration of the above-mentioned problems, and provides a mechanism for preventing a printing device from uploading unnecessary icon image data. [Means for solving the problem]

[0009] A printing device according to one embodiment of the present invention is a printing device capable of communicating via the Internet with a print service that registers the printing device in response to receiving a registration request for the printing device and provides a print job to the printing device in response to receiving a print instruction for the registered printing device, the printing device including a receiving unit that receives storage information for saving icon image data of the printing device from the print service, a storing unit that stores the icon image data of the printing device based on the storage information, and a path information for the stored icon image data of the printing device when notifying the print service of capability information of the printing device. Includes A notification means for notifying the capability information, When the notification is made by the notification means in a state where a storage event of the icon image data has not occurred, the icon image data of the printing device is not stored, and the capability information including the path information of the icon image data of the printing device that has already been stored is notified. It is characterized by: Effect of the Invention

[0010] It is possible to prevent unnecessary transmission processing of image icon data that has already been uploaded to the icon data storage server. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 illustrates an example of a printing system. [Diagram 2] FIG. 11 is a sequence diagram illustrating an example of image icon data transmission by a printing device. [Diagram 3] 13 is an example of an operation screen of a client terminal that has acquired image icon data. [Figure 4] FIG. 2 illustrates an example of a hardware configuration of a printing apparatus. [Diagram 5] 10 is a flowchart illustrating an example of control of a printing apparatus when using a cloud print service. [Figure 6] 11 is an example of a registration packet for registering a printing device. [Figure 7] 13 is an example of a packet for acquiring capability information of a cloud print service. [Figure 8] 13 is an example of a packet for uploading image icon data. [Figure 9]13 is an example of a packet for notifying a cloud print service of its capabilities. [Figure 10] 13 is an example of a packet for acquiring capability information of a printing device registered in a cloud print service. [Figure 11] 13 is an example of a packet for acquiring image icon data. [Figure 12] 5 is a flowchart showing an example of control of the printing apparatus according to the first embodiment. [Figure 13] 13 shows upload information of icon image data according to the first embodiment. [Figure 14] 10 is a flowchart showing an example of control of a printing apparatus according to a second embodiment. [Figure 15] 13 shows an example of a communication packet between the printing device 101 and the icon data storage server 103 during the deletion process of the icon image data. [Figure 16] 13 is an operational flowchart of a printing apparatus 101 according to a third embodiment. [Figure 17] 1 shows an example of information update performed between the printing device 101 and the CPS 102. [Figure 18] FIG. 2 illustrates an example of a hardware configuration of a server and a client. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, the embodiments for carrying out the present invention will be described with reference to the drawings. Note that the following embodiments do not limit the invention according to the claims, and all of the combinations of features described in the embodiments are not necessarily essential to the solution of the invention.

[0013] <First embodiment> The configuration of a printing system according to the present invention will be described with reference to FIG.

[0014] The printing system according to this embodiment includes a printing device 101, a client terminal 104, a cloud print service (hereinafter, also referred to as a print service or CPS) 102, and an icon data storage server 103. The printing device 101 communicates with the CPS 102 and the icon data storage server 103 on the Internet via a network. The network 100 may be configured by combining, for example, a communication network such as a LAN or a WAN, a cellular network (e.g., LTE or 5G), a wireless network conforming to IEEE802.11, and the like. That is, the network 100 may be configured to be capable of transmitting and receiving data, and any communication method of the physical layer may be adopted. The client terminal 104 also communicates with the CPS 102 and the icon data storage server 103 on the Internet via a communication network or a cellular network. The CPS 102 and the icon data storage server 103 also communicate via a network.

[0015] The printing device 101 has a scanning function for externally transmitting data based on an image obtained by scanning using a scanner, a printing function for printing an image on a sheet such as paper based on a print job received from an external device, and a copy function. The printing device 101 can also receive a print job via the CPS 102 and perform printing. In this embodiment, an MFP (Multi Function Peripheral) having multiple functions is exemplified as an example of the printing device, but is not limited thereto. For example, a single-function SFP (Single Function Peripheral) having only a printing function may be used. In this embodiment, printing on a sheet such as paper is exemplified as an example, but is not limited thereto, and can also be applied to print control in 3D printing, which forms a three-dimensional object based on three-dimensional shape data.

[0016] Furthermore, the printing device 101 of this embodiment has a user management function. When the user management function is enabled as an operational setting of the printing device 101, the user authenticates himself / herself at the printing device, logs in to the printing device, and uses each function of the printing device (details will be described later). The printing device 101 also has a reservation printing function for the purpose of preventing a third party from taking it away and misprinting. The reservation printing function is a function that, even if the printing device receives a print job, does not print the print job upon receiving the print job, but temporarily stores the print job in storage. In the case of a printing device in which the reservation printing function is enabled, the print job of the user is printed after the user successfully logs in.

[0017] The CPS 102 accepts a print instruction from a client terminal such as the client terminal 104, receives a print job, and saves the print job. It then notifies the printing device 101 registered in the CPS 102 that the print job has been submitted. Upon receiving the notification, the printing device 101 acquires the print job and temporarily saves it in storage. The print job saved in the printing device 101 is printed in response to the acceptance of an operation to start printing after a user logs in to the printing device 101.

[0018] Icon data storage server 103 stores image icon data (hereinafter simply referred to as icon) that represents the appearance of printing device 101. The stored icon is provided from printing device 101 to the icon data storage server. When icon data storage server 103 stores the icon, it provides URL information, which is a storage path for providing the icon, to the printing device. Client terminal 104 can obtain the icon data based on the URL information (details will be described later). Note that, although CPS 102 and icon data storage server 103 are described as separate servers in this embodiment, this is not intended to limit the invention, and the effects of the present invention can also be obtained with a single server configuration equipped with the respective server functions.

[0019] The CPS 102 and the icon data storage server 103 are illustrated as being configured as a single server. However, since it is assumed that the service will be deployed as a cloud service, it does not necessarily have to be configured as a single server, and it is assumed that the service is implemented as a system that bundles together multiple devices.

[0020] <Hardware Configuration of Printing Device 101> The hardware configuration of the printing device 101 in this embodiment will be described with reference to Fig. 4. Fig. 4 is a block diagram showing the hardware configuration of the printing device 101. The printing device 101 has a reading function for reading an image on a sheet, a file transmission function capable of transmitting the read image to an external communication device, and the like. It also has a printing function for printing an image on a sheet. It is also assumed to have a function for receiving a print job from the CPS 102 and printing it.

[0021] The control unit 110 including a central processing unit (CPU) 401 controls the overall operation of the printing device 101. The CPU 401 reads out a control program stored in a read only memory (ROM) 402 or storage 404, and performs various controls such as print control and read control. The ROM 402 stores a control program executable by the CPU 401. The random access memory (RAM) 403 is a main memory accessed by the CPU 401, and is used as a work area or a temporary storage area for expanding various control programs. The storage 404 stores print jobs, image data, various programs, and various setting information. In this way, the hardware such as the CPU 401, the ROM 402, the RAM 403, and the storage 404 constitute a so-called computer.

[0022] In the printing device 101 of this embodiment, one CPU 401 executes each process shown in the flowcharts described later using one memory (RAM 403), but other configurations are also possible. For example, each process shown in the flowcharts described later can be executed by cooperating with multiple processors, memories, and storages. Also, some of the processes can be executed using hardware circuits.

[0023] A printer I / F (interface) 407 connects a printer 411 (printer engine) and the control unit 110. The printing device 101 generates a print image and a print control command to be transferred to the printer 411 based on a print job. The printer 411 prints an image on a sheet fed from a paper feed cassette (not shown) based on the print image and print control command input via the printer I / F 407. The printing method may be an electrophotographic method in which toner is transferred to paper and fixed, or an inkjet method in which ink is ejected onto paper to print.

[0024] The scanner I / F 406 connects the scanner 410 and the control unit 110. The scanner 410 reads an original placed on an original table (not shown) and generates image data. The image data generated by the scanner 410 is printed by the printer 411, stored in the storage 404, or transmitted to an external device via the network I / F 408.

[0025] The operation unit I / F 405 connects the operation unit 409 and the control unit 110. The operation unit 409 is equipped with a liquid crystal display unit having a touch panel function, various hard keys, and the like. The operation unit 409 functions as a display unit that displays information to the user and a reception unit that receives instructions from the user. The CPU 401 cooperates with the operation unit 409 to control the display of information and the reception of user operations.

[0026] A network cable is connected to the network I / F 408, enabling communication with external devices on the network 100 or the Internet. In this embodiment, it is assumed that the network I / F 408 is a communication interface that performs wired communication compliant with Ethernet (registered trademark), but it is not limited thereto. For example, it may be a wireless communication interface compliant with the IEEE802.11 series. Also, both may be wireless communication interfaces. Further, it may be a communication interface that performs mobile communication such as 3G lines such as CDMA, 4G lines such as LTE, and 5G NR.

[0027] <Hardware Configuration of CPS 102, Icon Data Storage Server 103, and Client Terminal 104> FIG. 18 is a block diagram showing an outline of the hardware configuration of the CPS 102, the icon data storage server 103, and the client terminal 104. In FIG. 18, the CPU 701 directly or indirectly controls each device (such as ROM and RAM) connected by internal devices and executes a program for realizing the present invention. The ROM 702 stores the BIOS. The RAM (direct storage device) 703 is used as a work area and a primary storage area of the CPU 701. The indirect storage device 704 is an HDD (hard disk drive) or an SSD (solid state drive) that stores the OS, applications, and software modules, which are basic software. The input device 705 includes a keyboard and a pointing device. For example, a display is used as the output device 706. The network I / F 707 is an interface for connecting to a network. The configuration of the network I / F 707 may be a communication interface other than Ethernet connection, similar to the network I / F 408 described in FIG. 4.

[0028] <Printer Registration and Icon Use> Next, a sequence related to icon registration in this embodiment will be described with reference to Fig. 2. Note that explanations of controls similar to those of the general sequence described with reference to Fig. 2 will be omitted as appropriate. Also, details of packets to be transmitted in this sequence that are not shown as examples will be described in detail later with reference to a separate drawing.

[0029] First, in order to use the cloud print service of this embodiment, the printing device 101 registers the printing device with the CPS 102. When a user operates the operation unit 409 of the printing device 101 to perform a cloud print service registration operation (not shown), the printing device 101 connects to the CPS 102 to be registered and transmits a registration request packet to request registration (S201). When registration is complete, the CPS 102 transmits a registration request response packet to respond to the registration request (S202).

[0030] Figure 6 shows an example of an IPP packet sent in steps S201 and S202. Figure 6(A) shows a registration request packet, which is sent including "Operation:Register-Output-Device Request", which is operation information for requesting registration, and attribute information. The attribute information includes manufacturer information and model information, for example, "Requested-attributes:manufacture="Canon" model="iR-ADV"".

[0031] FIG. 6B shows a registration request response packet, which includes operation information "Operation: Register-Output-Device Response" and status information "Status Code: successful-ok". Furthermore, the registration request response packet includes identification information, for example, "Attribute: Cloud-device-id="Occ23168-d681-49b4-bc22-ef704a024aff" as attribute information. The CPS 102 issues identification information for the registered device and transmits it as attribute information. Through the above process, the printing device 101 is registered with the CPS 102 as a device compatible with the cloud print service.

[0032] Next, the printing device 101 transmits a capability acquisition request packet to the CPS 102 to inquire about capability information currently registered in the CPS 102 (S203). In response to the request in step S203, the CPS 102 transmits a capability acquisition response packet, which is capability information currently registered in the CPS 102, to the printing device 101 (S204). By the capability information inquiring process in steps S203 and S204, the printing device 101 can obtain URL information of a server in which an icon can be stored from the CPS 102. In response to the capability acquisition request, the CPS 102 issues URL information for storing an icon corresponding to the printing device 101. In this embodiment, the printing device 101 obtains URL information by making a capability acquisition request, but it may also obtain the information by a request other than capability acquisition. Note that the storage information of a server in which an icon can be stored is not limited to a URL, and may be any information that can identify a storage location.

[0033] Next, the printing device 101 transmits an image data upload request packet to the icon data storage server 103 based on the information acquired in step S204, requesting an update of the image data (S205). In response to the request from the printing device 101, the icon data storage server 103 returns the result of the icon storage status in an image data upload response packet (S206). Next, the printing device 101 transmits a capability notification request packet to the CPS 102, requesting an update of its own device's capability information, including the icon's URL information (S207). The CPS 102 transmits a capability notification request response packet as a response to the capability request from the printing device 101 (S208). If the series of sequences up to this point operates normally, the icon of the printing device 101 is stored in the icon data storage server 103, and the icon's URL information is registered in the CPS 102 as the printing device 101's capability information. The CPS 102 can register multiple printing devices, and the series of processes from step S201 to step S208 registers information of multiple printing devices in the CPS 102.

[0034] Meanwhile, client terminal 104 transmits a capability acquisition request packet to CPS 102 to acquire capability information of registered printing devices (S209). In response, CPS 102 transmits capability information of printing device 101, including icon URL information, by a capability acquisition response packet (S210).

[0035] Fig. 10 shows an example of an IPP packet sent in steps S209 and S210. Fig. 10(A) shows a capability acquisition request packet sent by the client terminal 104 to the CPS 102 in step S209, with the request being made with "Operation:Get-Printer-Attribute-Request" as operation information. Furthermore, the capability acquisition request packet is sent with the printer icon information "Printer-icon" included in the request as requested attribute information.

[0036] FIG. 10B shows an example of the capability acquisition response packet transmitted by the CPS 102 in step S210. Attributes: printer-icons=“https: / / print.microsoft.com / static-resource / Occ23168-d681-49b4-bc22-ef704a024aff / Printer-icon.png” 10B in step S210, the client terminal 104 receives the packet and obtains icon resource storage path information. The client terminal 104 accesses the icon data storage server 103 using the URL information of the icon of the printing device 101 obtained in step S210, and requests the icon using an image data acquisition request packet (S211). In response, the icon data storage server 103 transmits icon image data to the client terminal 104 using an image data acquisition response packet (S212).

[0037] Figure 11 shows examples of packets transmitted and received between the client terminal 104 and the icon data storage server 103 in steps S211 and S212. Figure 11(A) shows an image data acquisition request packet that the client terminal 104 sends to request an icon of a printing terminal using a GET operation of HTTP (Hypertext Transfer Protocol). The capability information of the printing device 101 acquired in step S210 is used as a parameter of the GET operation. Protocol: HTTP GET / Printer-icon.png HTTP / 1.1 Host:https: / / print.microsoft.com / static-resource / Occ23168-d681-49b4-bc22-ef704a024aff The icon data storage server 103 sends an HTTP response including electronic image data of the icon in an image data acquisition response packet (FIG. 11B). Through this series of processes, the client terminal 104 acquires the icon image data of the printing device 101. The client terminal 104 stores the icon image data in its own RAM 703 or indirect storage device 704, and the OS and applications of the client terminal 104 can use the icon to identify the printing device 101.

[0038] Fig. 3 is a diagram showing an example of a printing device selection screen in a printing application running on the client terminal 104. A user using the client terminal 104 launches the printing application to perform printing. To allow the user to select an available printing device, the printing application displays a list of available printing devices on the printing device selection screen in Fig. 3 together with icon images in Figs. 3(A), 3(B), and 3(C). Printing devices available to the printing application include those compatible with WSD (Web Service for Device) in addition to cloud print services, and local printing devices directly connected to the client terminal.

[0039] The OS of the client terminal 104 searches for printing devices that support each protocol, such as WSD in addition to the cloud print service, and acquires information about the devices detected by the search. If the printing devices 3A and 3C are devices that support the cloud print service, the print application displays the icons in Figures 3A and 3C using the icon data acquired in step S212 described above. For example, the printing device in Figure 3B is a printing device detected by the WSD protocol, and if the device information does not include an icon, the OS displays a generic icon for the printing device that it has prepared in advance.

[0040] As described above, by the print application displaying an icon of a printing device compatible with the cloud print service, the user can easily recognize the difference in appearance of the printing device he or she wishes to use. The icon of a printing device compatible with the cloud print service can also be used in the registration process of a printing device used by the OS or print application of the client terminal 104. By displaying the icon on a registration screen of the OS or the like, the user can easily identify the printing device he or she wishes to register by the icon.

[0041] <Icon registration process> Next, the control of the printing device 101 up to the point where the icon of the printing device 101 is updated for the CPS 102, which was explained in steps S203 to S208 in the sequence diagram of Fig. 2, will be described in detail using the flowchart of Fig. 5. Furthermore, examples of packets that are specifically communicated in the detailed explanation of each control will be described in detail using Figs.

[0042] 2, the printing device 101 starts a process of registering an icon for its own capability information when the registration to the cloud print service in the CPS 102 is completed. The effect of the present invention can be obtained by performing this icon registration process not only at the timing of the registration process to the cloud print service, but also when the printing device is powered on or a communication path with the server is established.

[0043] When the icon registration process is started, the printing device 101 transmits a capability acquisition request packet to the CPS 102 (S501) and receives a capability acquisition request response packet transmitted from the CPS 102 (S502). FIG. 7 shows an example of an IPP packet transmitted and received in the processes of steps S501 and S502. FIG. 7(A) shows a capability acquisition request packet requested by the printing device, which is transmitted by adding attribute information to the operation information "Operation:Get-Printer-Attribute-Request". The capability acquisition request packet includes a request for URL information "Requested-attributes:printer-static-resource-directory-uri" where the icon is saved as attribute information. FIG. 7(B) shows an example of an IPP capability acquisition response packet transmitted by the CPS 102 to the printing device 101. The capability acquisition response packet includes attribute information together with a status code "Status code:successful-ok" indicating success in addition to the operation information "Operation:Get-Printer-Attribute-Response". The attribute information includes storage path information, which is URL information where the resource is saved. Attributes: printer-static-resource-directory-uri=“https: / / print.microsoft.com / static-resource / Occ23168-d681-49b4-bc22-ef704a024aff” In step S502, if a status code indicating success is received, the process proceeds to step S503.

[0044] The processes in steps S503 and S504 are the same as those in steps S205 and S206 described in Fig. 2. In step S503, based on the storage path information included in the attribute information of the capability acquisition response packet received in step S502, the printing device 101 connects to the icon data storage server 103 and requests uploading of image data. Then, in step S504, the printing device 101 receives a response to the upload request from the icon data storage server 103.

[0045] Fig. 8 shows an example of an HTTP packet transmitted and received in steps S503 and S504 between the printing device 101 and the icon data storage server 103. Fig. 8(A) shows an image data upload request packet sent from the printing device 101 to the icon data storage server 103, requesting an icon update using the HTTP PUT operation. Protocol: HTTP PUT / Printer-icon.png HTTP / 1.1 Host:https: / / print.microsoft.com / static-resourse / Occ23168-d681-49b4-bc22-ef704a024aff Content-type:png Content-length:100 <Image data> (The actual image data is attached and sent.) As described above, the image data upload request packet includes icon name information, format information, image data entity, etc. The icon data storage server 103 responds to the printing device 101 with an image data upload response packet regarding the success or failure of the image data update request, which changes depending on the settings and status of the device.

[0046] FIG. 8B shows an example of a response packet when the icon update is successful, and the saved information is returned together with an HTTP success response. Protocol: HTTP HTTP / 1.1 201 Created Content-Location: / Printer-icon.png Next, the printing device 101 notifies the CPS 102 of its own capability information held by the CPS 102 that the icon image has been saved in the icon data storage server. In step S505, the attribute information to be notified includes image data storage path information, and the process proceeds to step S506. In step S506, the printing device 101 updates the capability information by sending a capability notification request packet to the CPS 102, and proceeds to step S507. In step S507, the printing device 101 receives a capability notification request response packet from the CPS 102, and exits the icon registration process.

[0047] FIG. 9 shows an example of an IPP packet transmitted and received in steps S506 and S507.

[0048] 9A shows a capability notification request packet in the case where the printing device 101 includes an image data storage path in the attribute information in step S506. This capability notification request packet includes image data path information in which icon image data is stored as requested attribute information. Operation:Update-Output-Device-Attributes Request Requested-attributes: (Omitted) printer-icons=“https: / / print.microsoft.com / static-resourse / Occ23168-d681-49b4-bc22-ef704a024aff / Printer-icon.png” FIG. 9B shows a capability notification request response packet that the printing device 101 receives from the CPS 102, which includes a successful status code in addition to the operation information "Operation: Update-Output-Device-Attributes Response."

[0049] This completes the icon image data registration process.

[0050] Thereafter, the print application on the client terminal 104 can display an icon of the printing device 101 compatible with the cloud print service, according to the details explained in the section on using an icon from the client terminal 104.

[0051] It is necessary to avoid unnecessarily uploading the same icon image data. In this regard, the processing flow when the printing device 101 is next powered on will be described with reference to FIG. 12. Note that, although the description will be given as the operation when the printing device 101 is "powered on," if the printing device 101 can switch the enable / disable setting for using the print service in cooperation with the CPS 102, the same flow may be performed when the cloud print setting of the printing device 101 is changed from disabled to enabled. In other words, the processing flow of FIG. 12 is executed when the power is turned on and when the enable / disable setting for using the print service of the CPS 102 of the printing device 101 is switched.

[0052] FIG. 12 is a flow chart illustrating the flow of the startup process when the printing device 101 is turned on, with reference to the portion that processes icon image data.

[0053] When the printing device 101 detects power-on in S1201, in S1202 the printing device 101 checks the upload history of icon image data to the icon data storage server 103. As described above, the start of the flow may be triggered when the enable / disable setting for using the print service of the CPS 102 of the printing device 101 is switched.

[0054] The upload history indicates information on whether or not icon image data stored in RAM 403 upon execution of step S1210 (described below) and / or when the printing device 101 receives the response of Fig. 8B has been uploaded to the icon data storage server 103. This information includes at least information on the icon image data files that have been uploaded to the printing device 101 up to now.

[0055] Fig. 13 shows an example of the upload information of the icon image data. Fig. 13(A) shows an example of uploading a single file, and Fig. 13(B) shows an example of uploading multiple files. Fig. 13(B) shows that different icon image data have been uploaded, in consideration of the case where the icon data displayed on the client terminal 104 side may differ depending on the usage status of the print service of the client terminal 104.

[0056] FIG. 13 shows an example of the upload information of image data, but in addition to this file information, upload date and time information and number of uploads information may be stored and managed.

[0057] If there is an upload history of icon image data, the process proceeds to step S1211, which will be described later.

[0058] Furthermore, if there is no history of uploading icon image data to the icon data storage server 103 in S1202, the printing device 101 performs processing of S1206. The printing device 101 confirms the connection destination from the CPS 102 to the icon data storage server 103 by performing processing similar to S501 in S1206 and S502 in S1207. Additionally, the printing device 101 uploads new icon image data to the icon data storage server 103 by performing processing similar to S503 in S1208 and S504 in S1209. The printing device 101 saves information on the upload history to the icon data storage server 103 in RAM 403 in S1210.

[0059] If it can be determined in S1211 from the upload history information that the icon image data has been uploaded, in S1203 the printing device 101 adds storage path information to the icon data storage server 103 from the previous time the icon image data was registered as attribute information, and performs processing similar to S506 in S1204 and S507 in S1205 to notify the CPS 102 of the icon image data information.

[0060] As explained in Figure 9(A), this is an example of indicating the storage path of icon image data using IPP communication. By adding the printer-icons attribute to other capability attribute values, an Update-Output-Device-Attributes Request is generated to notify the information.

[0061] If it cannot be determined in S1211 from the upload history information that the image data has been uploaded, an Update-Output-Device-Attributes Request that does not include the printer-icons attribute is generated and information is notified, as shown in Fig. 9C. This prevents the icon image data shown in S203, S204, S205, and S206 from being uploaded to the icon data storage server 103 every time the power is turned on.

[0062] As described above, by sending icon image data to the icon data storage server 103 only when uploading is required when the printing device 101 is powered on, efficient icon image data upload processing is performed and unnecessary delays in the startup time of the printing device 101 are prevented. The first embodiment is an embodiment that explains that an icon image data storage event occurs when the printing device 101 is first powered on after registration in the CPS 102 is completed. If uploading is completed at the time the power is turned on, the icon image data storage event does not occur. For example, if the upload ends in an error, the icon image data storage processing is executed at the time the power is turned on.

[0063] <Second embodiment> In this embodiment, the differences from the first embodiment will be described, and the similarities will not be described. The second embodiment is an example in which, in addition to the first embodiment, icon image data is uploaded to the icon data storage server 103 in response to a storage event of icon image data due to manual update. Figure 14 shows a process in which a different flow is added to the first embodiment. In S1401, the printing device 101 checks whether or not there is an instruction from the user to update the icon image data, and if there is an instruction, the process from S1206 onwards is carried out. If there is no instruction, the process from S1211 onwards is carried out.

[0064] FIG. 17 is a diagram showing a user interface for receiving an instruction to update icon image data from the user of the printing device 101. As shown in FIG.

[0065] The printing device 101 displays this on the input device 705, and is capable of receiving an instruction from the user to update the icon image data.

[0066] 17A is a screen that displays various settings required for the printing device 101 to operate the cloud printing service. When the printer registration is completed using the name shown in the printer name on the setting screen, the printer registration status becomes "registered" and the cloud printing service becomes available for operation.

[0067] Updating of icon image data is realized by providing an icon update button 1701. When icon update button 1701 is pressed, the printing device 101 displays Fig. 17(B). Fig. 17(B) shows, as an example, that the printing device 101 holds three types of icon image data 1702, 1703, and 1704, but the number of icon image data held may be one or more, and the held icon image data can be displayed.

[0068] In step S1401, the printing apparatus 101 can confirm an icon update instruction based on the input of icon image data selection from the user and the presence or absence of an event of pressing the update start button 1705.

[0069] Furthermore, in the case where S1209 is branched depending on whether the upload is successful or unsuccessful, if the upload results in failure, in S1402 the printing device 101 makes a request to the icon data storage server 103 to delete the icon image data shown in FIG.

[0070] The icon data storage server 103, which has received the request to delete the icon image data in S1403, deletes the icon image data designated by the printing device 101 and returns a response of the result.

[0071] FIG. 15 shows an example of communication packets between the printing device 101 and the icon data storage server 103 during the deletion process of the icon image data.

[0072] FIG. 15A shows an example of a request to delete icon image data sent to the icon data storage server 103. In FIG.

[0073] In this example, the HTTP DELETE operation is used, and the storage path of the icon image data to be deleted is indicated. Protocol: HTTP DELETE / Printer-icon.png HTTP / 1.1 Host:https: / / print.microsoft.com / static-resource / 0cc23168-d681-49b4-bc22-ef704a024aff FIG. 15B shows an example of a response packet returned when the icon data storage server 103 receives the request shown in FIG. 15A and deletes the target icon image data.

[0074] In this example, it is shown that icon image data has been deleted in response to an HTTP DELETE operation. Protocol: HTTP HTTP / 1.1 200 OK The printing device 101 receives the deletion result from the icon data storage server 103, and performs the processes in and after step S1208 as necessary, while retrying the upload process of the icon image data.

[0075] As described above, regardless of whether icon image data has been uploaded or not, if it is necessary to update to new icon image data, the upload process can be performed by manual instructions from the user of the printing device 101. Furthermore, even if an upload fails due to a factor on the icon data storage server 103 side, the printing device 101 can identify that it is necessary to re-upload the same icon image data as during the previous communication.

[0076] <Third embodiment> In this embodiment, the description will be limited to the differences from the first and second embodiments, and the description of the similarities will be omitted. In addition to the first and second embodiments, the third embodiment is an example in which icon image data is uploaded to the icon data storage server 103 in response to an event of storing icon image data due to automatic update.

[0077] If there is an upload record indicating that an upload has been performed at least once in S1202, and even if there is no manual icon update instruction in S1401, it is possible for the printing device 101 to automatically update the icon image data in S1601.

[0078] In practice, the upload record of S1210 is compared with the currently stored icon image data, and if there is a difference between the previously uploaded icon image data and the currently held icon image data, the printing device 101 automatically uploads the icon image data.

[0079] To explain the comparison between the upload record in S1210 and the currently stored icon image data, for example, a common hash algorithm (SHA1, SHA256, MD5, etc.) is used for each icon image data as the upload record in S1210, and the printing device 101 calculates a hash value for the icon image data. The hash value thus generated (a hash value of about several tens of bytes per icon image data) is stored as the upload record. In the icon image data comparison process in S1601, the printing device 101 calculates the hash value for the icon image data currently stored by the same means as when recording the upload, and derives a hash value. By comparing the hash value stored as the upload record with the hash value of the stored image data, it is possible to confirm whether the icon image data previously uploaded and the icon image data currently stored are the same.

[0080] This method makes it possible to confirm whether the images are identical by comparing hash values ​​of several tens of bytes, but it is also possible to retain the actual icon image data previously uploaded as the upload record in S1210 and compare it with the icon image data currently retained in S1601.

[0081] If it is determined in S1602 that the icons are different, the process of S1206 is continued, whereas if it is determined that the icons are the same, the process of 1211 is continued.

[0082] As a result, the printing device 101 can automatically determine differences in icon image data and notify only if there are differences, which means that unnecessary uploads of icon image data do not occur and there are no adverse effects on the network or the printing device 101.

[0083] <Other Examples> The present invention can also be realized by supplying a program that realizes one or more functions of each of the above-mentioned embodiments to a system or device via a network or a storage medium, and having one or more processors in a computer of the system or device read and execute the program. It can also be realized by a circuit (e.g., ASIC or FPGA) that realizes one or more functions. [Explanation of symbols]

[0084] 101 Printing device 102 Cloud Print Service 103 Icon data storage server 104 Client terminals

Claims

1. A printing device capable of communicating with a print service via the Internet, the print service registering the printing device in response to receiving a registration request for the printing device, and providing a print job to the printing device in response to receiving a print instruction for the registered printing device, a receiving means for receiving storage information for storing icon image data of the printing device from the print service; a storage means for storing icon image data of the printing device based on the storage information; a notification means for notifying the print service of capability information of the printing device, the notification means including path information of the stored icon image data of the printing device, A printing device characterized in that when a notification is made by the notification means when no icon image data storage event has occurred, the icon image data of the printing device is not stored, and capability information including path information of the icon image data of the printing device that has already been stored is notified.

2. The printing device as described in Claim 1, characterized in that if updating of the icon image data fails, a request to delete the icon image data is sent.

3. 3. The printing device according to claim 1, wherein the icon image data storage event is an event that occurs when power-on of the printing device is detected.

4. 4. The printing device according to claim 1, wherein the icon image data storage event is an event that occurs in response to a user's instruction to update the icon image data.

5. 5. The printing device according to claim 1, wherein the icon image data storage event is an event that occurs due to a change in the configuration of the printing device or a change in capability information.

6. 6. The printing apparatus according to claim 1, wherein the notification of the capability of the printing apparatus by the notification means and the reception of the print job utilize IPP (Internet Printing Protocol).

7. 7. The printing device according to claim 1, wherein after the printing device is registered, the printing device requests the stored information by transmitting a capability notification request packet of the printing device.

8. A printing device as described in any one of claims 1 to 7, characterized in that the capability information of the printing device notified by the notification means is information provided to a printing application of a client terminal that sends a print instruction to the printing device, and the printing application displays a printing device selection screen based on the provided information.

9. A method for controlling a printing device capable of communicating with a print service via the Internet, the print service registering the printing device in response to receiving a registration request for the printing device, and providing a print job to the printing device in response to receiving a print instruction for the registered printing device, the method comprising: a receiving step of receiving storage information for storing icon image data of the printing device from the print service; a storing step of storing icon image data of the printing device based on the storage information; a notification step of notifying the print service of capability information of the printing device, the notification step including path information of the stored icon image data of the printing device, A control method characterized in that, when notification is made by the notification step when no icon image data storage event has occurred, the icon image data of the printing device is not stored, and capability information including path information of the icon image data of the printing device that has already been stored is notified.

10. A program for causing a printing device to execute the control method according to claim 9.

Images