Information processing device, control method for information processing device, program, and cloud printing system

Abstract

To suitably acquire status information of a printer.SOLUTION: A program which can operate in an information processing device and functions as a printing extension application for extending a printing function in a printing system having a printer capable of corresponding to a cloud printing service through the information processing device, the cloud printing service, a data conversion service, and a data conversion service makes the information processing device function as acquisition means for acquiring printer specification information for specifying a printer in the printing system, request means for requesting the data conversion service for printer status information of the printer by using the acquired printer specification information, and display control means for displaying and controlling the printer status information acquired by the request means.SELECTED DRAWING: Figure 11

Description

Technical Field

[0001] This disclosure relates to the technology of cloud printing systems.

Background Art

[0002] In recent years, for example, cloud printing systems for using printing services on the cloud, such as Universal Print (registered trademark) provided by Microsoft, have begun to spread. Along with this, the spread of printing extension applications that expand the functions of cloud printing systems or data conversion services that enable the use of printers not supported by cloud printing services on cloud printing services has also advanced.

[0003] In Patent Document 1, a system has been proposed for registering, in a server, capability information not provided by a printer for a printer registered in the server.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In a cloud printing system, a technology for suitably obtaining the status information of a printer is required.

[0006] Therefore, an object of this disclosure is to suitably obtain the status information of a printer.

Means for Solving the Problems

[0007] A program relating to one aspect of this disclosure is a program that can be operated on an information processing device and functions as a printing extension application for extending the printing function in a printing system having the information processing device, a cloud printing service, a data conversion service, and a printing device that can respond to the cloud printing service via the data conversion service, wherein the information processing device comprises: acquisition means for acquiring printer identification information that identifies the printing device in the printing system; and request means for requesting printer status information of the printing device from the data conversion service using the acquired printer identification information. In the display area of ​​a web browser, toast notification, or the print extension application, The display control means is characterized by functioning as a means for displaying and controlling the printer status information acquired by the request means. [Effects of the Invention]

[0008] According to this disclosure, printer status information can be preferably obtained. [Brief explanation of the drawing]

[0009] [Figure 1] This diagram shows an example of a cloud printing system configuration. [Figure 2] This diagram shows an example of a PC hardware configuration. [Figure 3] This diagram illustrates an example of a PC software module configuration. [Figure 4] This diagram shows an example of a sequence diagram in which an administrator registers a virtual printer. [Figure 5] This diagram shows an example of a sequence diagram for when a general user registers an actual printer. [Figure 6] This diagram shows an example of a printer status display screen. [Figure 7] This diagram shows an example of a sequence diagram for the process of displaying the printer status. [Figure 8] This diagram shows an example of a sequence diagram for the process of displaying the printer status. [Figure 9]This is a diagram showing an example of a sequence diagram of a process for displaying the status of a printer. [Figure 10] This is a diagram showing an example of the content of Get-Printer-Attributes. [Figure 11] This is a diagram showing an example of a flowchart of a process for displaying the status of a printer. [Figure 12] This is a diagram showing an example of a flowchart of a process for displaying the status of a printer. [Figure 13] This is a diagram showing an example of a flowchart of a process for displaying the status of a printer. [Figure 14] This is a diagram showing an example of a flowchart of a process for obtaining a cloud printer ID.

Embodiments for Carrying Out the Invention

[0010] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the present disclosure according to the claims, and not all combinations of the features described in these embodiments are essential for the solution means of the present disclosure. The same reference numerals are assigned to the same components, and the description thereof will be omitted.

[0011] <Embodiment 1> FIG. 1 is a diagram showing an example of the configuration of a cloud printing system. The cloud printing system in the present embodiment includes client terminals 110 and 210, printers 120 and 220, a cloud printing service 310, and a data conversion service 320. Further, these are interconnected via the Internet.

[0012] The cloud printing service 310 includes a cloud printing application 31, a file storage 312, and a database 313. In the present embodiment, as an example of the cloud printing service 310, Universal Print provided by Microsoft is assumed for explanation.

[0013] The data conversion service 320 includes a data conversion application 321, file storage 322, and a database 323. Client terminals 110 and 210 are information processing devices, such as general personal computers (hereinafter referred to as PCs or computers). Hereafter, client terminals will be referred to as PCs or computers. PCs 110 and 210 can connect to the cloud printing service 310 via the internet and use this service.

[0014] Printers 120 and 220 are connected to the data conversion service 320 via the internet. The data conversion service 320 converts print data (PDF files) contained in print jobs submitted from the cloud printing service 310 into data in a format printable by printers 120 and 220 (print setting files and PWG Raster data). The data conversion service 320 also has the function of obtaining printer status information from the printer and sending the printer status screen or printer status information (information such as ink level, online, offline, and errors) to PCs 110 and 210. The interface between the cloud printing service 310 and the data conversion service 320 is IPP Shared Infrastructure Extensions (INFRA) used by Universal Print. Printers 120 and 220 are printers that are not supported by the cloud printing service 310 (Universal Print) on their own. Therefore, they have the function of obtaining print jobs containing data in a printable format from the data conversion service 320 and printing them out. Client applications 140 and 240 are, for example, document editing applications. Print extension applications (hereinafter abbreviated as print extension apps) 180 and 280 are applications that can run on the information processing device and manage printers registered in the cloud printing service 310. In this embodiment, as an example, the Print Support Application provided by Microsoft will be used for explanation.

[0015] There are two types of user permissions for using the cloud printing service 310, namely administrators and general users. Administrators can register virtual printers with the cloud printing service 310. A virtual printer refers to a printer registered with the cloud printing service 310. In this embodiment, as will be described later, in order to use the data conversion service 320, the cloud printing service 310 will register the data conversion service 320 as a virtual printer. In the cloud printing service 310, one virtual printer is associated with one actual physical printer (referred to as a real printer). General users can register a real printer with the cloud printing service 310, or perform printing using the cloud printing service 310, etc. Note that the administrator authority also includes the authority of general users.

[0016] Figure 2 is a diagram showing an example of the hardware configuration of a PC. In this embodiment, the PC 210 will be described as an example. As shown in Figure 2, the PC 210 includes a RAM 201 which is a random access memory unit, an HDD 202 which is a hard disk drive unit, a KBD 203 which is a keyboard unit, and a CPU 204. In addition, the PC 210 includes an LCD 205 which is a display for display, an NB 207 which is a network board, and a bus 206 that connects at least each block shown in Figure 2 so that they can communicate with each other. Note that the HDD 202 is, for example, the storage unit of the PC 210. Also, the storage unit is not limited to this and may be a portable CD-ROM or an internally installed ROM, etc. The KBD 203 is, for example, the input unit of the PC 210. The CPU 204 is, for example, the control unit of the PC 110. The LCD 205 is, for example, the display unit of the PC 210 and is display-controlled by the CPU 204 or a printing extension application 280, etc. The NB 207 is, for example, the communication control unit of the PC 210.

[0017] Applications or software such as client applications 140 and 240 and the web browser 83 are stored, for example, on the HDD 202 and, as needed, read into RAM 201 and executed by the CPU 204. This allows the CPU 204 to implement the functions of the applications or software such as client applications 140 and 240 and the web browser 83.

[0018] Figure 3 is a diagram showing an example of the module configuration of PC software. In Figure 3, module 92 is the Ethernet control stack that controls Ethernet®. Module 91 is the IP Network control stack that controls the IP Network. Module 90 is the WSD control stack that controls WSD (Web Service on Devices), which provides a mechanism for discovering devices on the network. Module 88 is the PnP-X control stack that controls network plug and play. PnP-X is an abbreviation for Plug and Play Extensions. PnP-X is a feature that is standard in the Windows 10® operating system (OS) as a set of plug and play extensions that provide support for network-connected devices. Module 85 is a group of device drivers, which includes the standard driver group 87 that is included with the OS as standard, and the IHV driver group 86 provided by Independent Hardware Vendors (IHV). The standard driver group 87 includes OS standard printer drivers, scanner drivers, and network drivers, etc. The IHV driver group 86 includes IHV printer drivers, scanner drivers, network drivers, and other drivers.

[0019] Module 84 is an application / DDI interface and includes an ApplicationProgrammingInterface (API) and a DeviceDriverInterface (DDI). Module 140 is, for example, a document editing application, and Module 83 is, for example, a web browser application. Module 82 is a group of applications and includes client application 140, web browser 83, etc.

[0020] In a cloud printing system, the identifier that identifies a printer (i.e., a virtual printer) registered with the cloud printing service 310 is called the Cloud Printer ID (or Printer Identification Information). Furthermore, the printer identifier in a local printing system on the Windows OS is called the OS Printer ID, and the value of the OS Printer ID representing a single printer is different from the value of the Cloud Printer ID.

[0021] Generally, in a cloud printing system including the data conversion service 320, when displaying printer status information such as ink levels from the print extension application 180, the print extension application retrieves and displays information stored in the cloud printing service 310. The printer status information held by the cloud printing service is information received and updated from the data conversion service 320 at specific times, such as when the printer is registered or when printing. Therefore, depending on the timing of the operation to check the status information (such as pressing the update button), it may not be possible to know the latest printer status information.

[0022] In order for the print extension application 180 to obtain real-time printer status information via an update button or similar means, it is necessary to obtain the cloud printer ID used to identify the printer on the printer's cloud printing system. If the print extension application 180 can obtain the cloud printer ID, it can directly request printer status information from the data conversion service 320.

[0023] In the following embodiment, a method is described in which the print extension application 180 obtains a cloud printer ID and displays printer status information in real time. Note that in this embodiment, it is assumed that the cloud printing service 310 is used with a printer 120 that does not support the cloud printing service 310. Therefore, a method for registering the printer via the data conversion service 320, or a method for displaying the printer status, will be described.

[0024] Figure 4 is a diagram illustrating an example of a sequence diagram in which an administrator registers a virtual printer. The sequence shown in Figure 4 is performed by the CPUs of PC 210, the cloud printing service 310, and the data conversion service 320 loading program code stored on a disk device or the like into RAM and executing it. In the following descriptions of each process, "S" indicates a step in the flowchart, and the same applies to subsequent embodiments. As explained above, this embodiment assumes that a printer that does not support the cloud printing service is registered with the cloud printing service via the data conversion service 320. Therefore, in this embodiment, the data conversion service 320 provides a management screen for printer registration to PC 110.

[0025] First, in S401, PC210 executes a login request to the data conversion service 320. This is done when the administrator clicks the login button on the initial screen (not shown) provided by the data conversion service 320, which is displayed on the web browser 83 on PC210. ​​In S402, the data conversion service 320 sends a user authentication request to the cloud printing service 310.

[0026] In S403, the cloud printing service 310 responds to this user authentication request by sending a login screen to the PC 210 used by the administrator. Since the account ID and password are managed by the cloud printing service 310, user authentication is performed by the cloud printing service 310. Consequently, the cloud printing service 310 also provides the login screen. As a result, the login screen (not shown) is displayed in the web browser 83 on PC 210. In S404, when the administrator enters the account ID and password on the login screen and presses the login button, PC 210 sends the account ID and password to the cloud printing service 310.

[0027] In S405, the cloud printing service 310 searches the database 313 based on the account ID and password to perform user authentication. If the account ID and password are correct, in S406, the cloud printing service 310 sends information to the data conversion service 320 indicating that user authentication was successful.

[0028] In S407, the data conversion service 320 sends a management screen to the PC210. ​​In S408, the PC210 displays the management screen on the web browser 83 on the PC210, and when the administrator requests virtual printer registration from this management screen, the PC210 sends a virtual printer registration request to the data conversion service 320.

[0029] In S409, when the data conversion service 320 receives a virtual printer registration request, it sends the virtual printer registration request to the cloud printing service 310. In S410, the cloud printing service 310 generates a virtual printer ID that uses the data conversion service 320 as the virtual printer and registers the virtual printer ID in the database 313. In S411, the cloud service 310 sends information indicating the completion of virtual printer registration and the virtual printer ID to the data conversion service 320.

[0030] In S412, the data conversion service 320 stores the virtual printer ID in the database 323. In S413, the data conversion service sends a management screen to PC210 indicating that the virtual printer registration is complete. Upon receiving this information, PC210 displays a management screen containing the information of the registered virtual printer in the web browser 83 on PC210.

[0031] Figure 5 shows an example of a sequence diagram for when a general user registers a physical printer. The series of processes shown in the sequence in Figure 5 are performed by the CPUs of the PC 110, cloud printing service 310, data conversion service 320, and printer 120 loading program code stored in disk devices or the like into RAM and executing it.

[0032] Printer 120 has a function to issue a registration code, which is used when registering the physical printer as described later, when using itself in the cloud printing system. This diagram explains the scene after a general user has obtained a registration code by operating the operation screen of printer 120 in order to use the cloud printing system.

[0033] First, in S501, PC110 executes a login request to the data conversion service 320. This is done when a user clicks the login button on the initial screen provided by the data conversion service 320, which is displayed on the web browser 83 inside PC110. In S502, the data conversion service 320 sends a user authentication request to the cloud printing service 310.

[0034] In S503, the cloud printing service 310 responds to this user authentication request by sending a login screen to the PC 110 used by the general user, and the login screen is displayed in the web browser 83 on the PC 110. In S504, when the general user enters their account ID and password on the login screen and presses the login button, the PC 110 sends the account ID and password to the cloud printing service 310.

[0035] In S505, the cloud printing service 310 searches the database 313 based on the account ID and password to perform user authentication. If the account ID and password are correct, in S506, the cloud printing service 310 sends information to the data conversion service 320 indicating that user authentication was successful.

[0036] In S507, the data conversion service 320 sends a printer list screen to the PC 110. In S508, the PC 110 sends a real printer registration request including the virtual printer ID and a registration code to the data conversion service 320. Specifically, a general user selects the virtual printer (i.e., the data conversion service 320) registered in Figure 4 from the printer list screen. Then, when the general user enters the registration code issued by the printer 120 for the selected virtual printer, the PC 110 sends a real printer registration request to associate the selected virtual printer with the printer 120. In other words, it sends a request to associate the data conversion service 320, which is the virtual printer, with the printer 120, which is the real printer, with the cloud printing service. For this reason, in S509, the data conversion service 320 sends a real printer registration request to the cloud printing service 310.

[0037] In S510, the cloud printing service 310 generates a cloud printer ID to identify the actual printer. It then registers the cloud printer ID in the database 313 and sends this cloud printer ID to the data conversion service 320. In S511, the data conversion service 320 issues a vendor printer ID to identify printer 120 from one or more printers not supported by the cloud printing service 310 connected to it. This printer 120 is the printer corresponding to the registration code sent from PC 110 in S508. In S512, the data conversion service 320 associates the cloud printer ID and the vendor printer ID and stores them in the database 323. This allows the data conversion service 320 to identify printer 120, which is the actual printer, based on the vendor printer ID when the cloud printing service 310 specifies the cloud printer ID. In S513, the data conversion service 320 sends a printer list screen to PC 110 indicating that the actual printer registration is complete.

[0038] Figure 6 shows an example of a printer status display screen displayed by a print extension application. The printer status display screen 600 has a display area 601 and an update button 605. The display area 601 also includes a printer status display unit 602, a print job information display unit 603, and a printer ink level display unit 604.

[0039] Furthermore, the display area 601 may function as a Web View display unit that uses a Web browser to display a status screen provided by the data conversion service 320 or the cloud printing service 310. Alternatively, the display area 601 may display a display screen whose display is controlled based on printer status information received from the data conversion service 320 or the cloud printing service 310.

[0040] Furthermore, if multiple printers are registered in the cloud printing system, it is possible to manage multiple printers on a single display screen by providing separate tabs (not shown) for each printer on the printer status display screen 600.

[0041] Figure 7 is a sequence diagram showing an overview of the process by which the print extension application 180 displays the printer status. This diagram describes the process of displaying the printer status screen of the printer 120 by making the display area 601 within the print extension application 180 function as a Web View display unit. This process starts when the update button is pressed on the printer 120 management screen provided by the print extension application 180. In Figure 7, the series of user authentication processes in steps S701 to S706 are the same as the processes in steps S501 to S506 in Figure 5, so the explanation is omitted here. In addition, in S701, the print extension application 180 also requests the status of the printer 120 by specifying the cloud printer ID to the data conversion service 320, but the explanation is omitted in this sequence diagram. Details of the process of specifying the cloud printer ID for the printer status request will be described later in the flowcharts from Figure 11 onwards. The same applies to the sequence diagrams in Figures 8 and 9 described later.

[0042] In S707, the data conversion service 320 sends a printer status request to the printer 120. In S708, the printer 120 sends the printer status to the data conversion service 320. In S709, the data conversion service 320 receives the printer status and saves it to the database 323. Also, in S710, the data conversion service 320 sends the printer status screen to the PC 110.

[0043] In step S711, the print extension application 180 on PC110 receives the printer status screen and displays the printer status using the web browser function within the print extension application 180. Alternatively, in step S711, the print extension application 180 may launch the web browser 83 on PC110 and display the printer status screen in the web browser 83.

[0044] Figure 8 shows an example of a sequence diagram for the process by which the print extension application 180 displays the printer status. This figure describes the process by which the print extension application 180 displays the status information of the printer 120 sent from the data conversion service 320 using the toast notification function of the PC 110. This process starts when the update button is pressed on the printer 120 management screen provided by the print extension application 180. In Figure 8, the series of user authentication processes in steps S801 to S806 are the same as the processes in steps S501 to S506 in Figure 5, so the explanation is omitted. Also, the series of printer status requests, receptions, and saves in steps S807 to S809 are the same as steps S707 to S709 in Figure 7, so the explanation is omitted.

[0045] In S810, the data conversion service 320 uses the INFRA mechanism to send the printer status to the cloud printing service 310. Also, in S811, the cloud printing service 310 uses the INFRA mechanism to send the printer status to the PC 110. In S812, the PC 110 displays the printer status using the Windows OS toast notification function. In this embodiment, the latest printer status information is shared in the order of data conversion service, cloud printing service, and PC 110 as a general processing flow, but it is not limited to this. For example, in S811, the PC 110 may receive the status information from the data conversion service 320.

[0046] Figure 9 is a diagram illustrating an example of a sequence diagram for the process by which the print extension application 180 displays the printer status. This diagram explains the process flow in which the print extension application 180 displays the printer status in the display area 601 within the print extension application 180. This process starts when the update button is pressed on the printer 120 management screen provided by the print extension application 180. In Figure 9, the series of user authentication processes in steps S901 to S906 are the same as the processes in steps S501 to S506 in Figure 5, so the explanation is omitted. Also, the series of printer status requests, receptions, and saves in steps S907 to S909 are the same as steps S707 to S709 in Figure 7, so the explanation is omitted.

[0047] In S910, the data conversion service 320 uses the INFRA mechanism to send the printer status to the cloud printing service 310. In S911, the PC 110 uses the INFRA mechanism to send a printer status request to the cloud printing service 310. In S912, the cloud printing service 310 uses the INFRA mechanism to send the printer status to the PC 110. In S913, the print extension application 180 on the PC 110 displays the printer status in the display area 601.

[0048] In steps S911 and S912, the PC 110 sent a printer status request to the cloud printing service 310 and obtained the printer status from the cloud printing service 310, but this is not limited to this. For example, the print extension application 180 on the PC 110 may send a printer status request to the data conversion service 320 and obtain the printer status from the data conversion service 320.

[0049] Figure 10 shows an example of the contents of Get-Printer-Attributes. The xyz-cloud-printer-id key is the cloud printer ID key, which represents the cloud printer ID, and is used as the key specified when requesting information such as printer status with Get-Printer-Attributes. It is also used to refer to the value of that key from the information obtained when retrieving information such as Get-Printer-Attributes. In Figure 10, as an example, the value of the cloud printer ID key associated with printer 120 is set to "82032d34-50fd-4f6a-a7f8-f5ed9ee3f798". In this embodiment, the cloud printer ID is shown as an example in GUID format.

[0050] Figure 11 is a diagram illustrating an example of a flowchart showing the process by which the print extension application 180 displays the printer status. This diagram describes the process of displaying the printer status screen by making the display area 601 within the print extension application 180 function as a Web View display unit. The series of processes shown in the flowchart of Figure 11 are performed by the CPUs of the PC 110, the data conversion service 320, and the printer 120 loading program code stored in a disk device or the like into RAM and executing it. In this flowchart, the process starts when the print extension application 180 is launched by a general user and the update button 605 is pressed. In this embodiment, the user authentication process between the PC 110 and the data conversion service 320 is explained in the sequence diagram of Figure 7 and is therefore omitted here.

[0051] In S1101, the print extension application 180 uses the OS API to specify the cloud printer ID key (xyz-cloud-printer-id) and obtain the value of the cloud printer ID. Details of the process by which the print extension application 180 obtains the cloud printer ID will be described later with reference to Figure 14.

[0052] In S1102, the print extension application 180 generates a URL to specify the printer status screen (Web page) of the data conversion service 320, using the acquired cloud printer ID value as a query parameter. In S1103, the print extension application 180 specifies the URL and requests the printer status screen from the data conversion service 320. In S1104, the data conversion service 320 acquires the cloud printer ID specified in the URL query parameter. The data conversion service 320 then refers to the database 323 to identify the printer associated with the acquired cloud printer ID and starts the status acquisition process for the identified printer. In this embodiment, it is assumed that printer 120 has been identified.

[0053] In S1105, the data conversion service 320 sends a printer status request to the printer 120. In S1106, the printer 120 receives the printer status request. Also, in S1107, the printer 120 sends its own printer status to the data conversion service 320.

[0054] In step S1110, the data conversion service 320 receives the printer status. In step S1109, the data conversion service 320 saves the status information of the specified printer (printer 120) to the database 323. In step S1110, the data conversion service 320 generates a printer status screen and sends this printer status screen to the print extension application 180. In step S1111, the print extension application 180 receives the printer status screen. In step S1112, the print extension application 180 displays the printer status screen in the display area 601 of the display screen 600. After that, this process ends. Note that in step S1112, the print extension application 180 may launch the web browser 83 on the PC 110 and display the printer status screen in the web browser 83.

[0055] Figure 12 is an example flowchart illustrating the process by which a PC displays the printer status. This diagram describes the process by which the print extension application 180 displays printer status information of printer 120, sent from the data conversion service 320, using the toast notification function of PC 110. The series of processes shown in the flowchart of Figure 12 are performed by the CPUs of PC 110, cloud printing service 310, data conversion service 320, and printer 120 loading program code stored in disk devices, etc., into RAM and executing it. In this flowchart, the process starts when the print extension application 180 is launched by a general user and the update button 605 is pressed. Note that in S1201, it is assumed that some kind of error has occurred in the printer.

[0056] In S1202, the print extension application 180 obtains the cloud printer ID. In S1203, the print extension application 180 specifies the cloud printer ID obtained in S1202 and sends a printer status request to the data conversion service 320.

[0057] In S1204, the data conversion service 320 refers to the database 323 to identify the printer associated with the specified cloud printer ID and starts the process of obtaining the status of that printer. In this embodiment, it is assumed that printer 120 has been identified. In S1205, the data conversion service 320 sends a printer status request to printer 120.

[0058] In S1206, printer 120 receives a printer status request. In S1207, printer 120 sends its own printer status information, including error information, to data conversion service 320. In S1208, data conversion service 320 receives the printer status including error information and saves the printer status information of the specified printer (printer 120) to database 323.

[0059] In S1210, the data conversion service 320 uses the INFRA mechanism to send printer status information, including error information, to the cloud printing service 310 using Get-Printer-Attributes. In S1211, the cloud printing service 310 receives the printer status information, including error information, and saves it to the database 313.

[0060] In S1212, the cloud printing service 310 sends printer status information, including error information, to PC110. In S1213, PC110 uses the INFRA mechanism to receive the printer status information, including error information, using Get-Printer-Attributes. In S1214, PC110 displays the error information using the Windows OS toast notification function. After that, this process ends. Note that in S1214, PC110 may also notify information other than error information using the toast function. For example, it may notify that printer 120 is running low on ink.

[0061] Figure 13 is an example flowchart showing the process by which the print extension application 180 displays the printer status. This figure explains the process by which PC 110 obtains printer status information using the INFRA mechanism and displays the printer status in the display area 601 within the print extension application 180. Note that the processes S1301 to S1304 are the same as the processes S1202 to S1205 in Figure 12, so their explanation is omitted.

[0062] In S1305, printer 120 receives a printer status request. In S1306, printer 120 sends its printer status to data conversion service 320. In S1307, data conversion service 320 receives the printer status. In S1308, data conversion service 320 saves the status information of the specified printer (printer 120) to database 323.

[0063] In S1309, the data conversion service 320 uses the INFRA mechanism to send printer status information to the cloud printing service 310 using Get-Printer-Attributes. In S13110, the cloud printing service 310 receives the printer status information and saves it to the database 313.

[0064] In S1311, the print extension application 180 requests printer status information from the Windows OS (PC110), specifying the identifier (OS printer ID) that represents printer 120 within the Windows OS. PC110 can identify printer 120 from the obtained OS printer ID. In S1312, PC110 uses the INFRA mechanism to send a printer status request to the cloud printing service 310 using Get-Printer-Attributes. That is, the Windows OS within PC110 sends a printer status request to the cloud printing service 310, specifying printer 120. In S1313, the cloud printing service 310 obtains the printer status information for printer 120 by referring to the database 313. Also, in S1314, the cloud printing service 310 sends the printer status information for printer 120 to PC110.

[0065] In S1315, PC110 receives printer status information, and the Windows OS on PC110 returns the printer status information to the print extension application 180. In S1316, the print extension application 180 displays the printer status in the display area 601. After that, this process ends. In this embodiment as well, in S1312, PC110 requested printer status information from the cloud printing service 310, but it is not limited to this; it may also request and receive printer status information from the data conversion service 320. This is because both services have the latest printer status information transmitted by printer 120 in S1306.

[0066] Figure 14 is a diagram illustrating an example of a flowchart showing the process by which the print extension application 180 obtains a cloud printer ID. In other words, this process is a detailed explanation of the processes S1101, S1202, and S1301 in Figures 11, 12, and 13.

[0067] In S1401, the print extension application 180 requests the Windows OS (PC110) to obtain the cloud printer ID for printer 120. At this time, the print extension application 180 specifies the identifier representing printer 120 within the Windows OS (OS printer ID) and the cloud printer ID key (xyz-cloud-printer-id) and requests the acquisition of the cloud printer ID for printer 120. In S1402, PC110 uses the INFRA mechanism to send a Get-Printer-Attributes request to the cloud printing service 310.

[0068] In S1403, the cloud printing service 310 receives a Get-Printer-Attributes request. In S1404, the cloud printing service 310 refers to the database 313 to obtain the information to be set in Printer-Attributes (i.e., the cloud printer ID of printer 120). It also sets the value indicating the cloud printer ID of printer 120 in xyz-cloud-printer-id of Printer-Attributes and sends Get-Printer-Attributes to PC 110.

[0069] In S1405, PC110 receives Get-Printer-Attributes. In S1406, the Windows OS on PC110 obtains the cloud printer ID from Printer-Attributes and returns the cloud printer ID to the print extension application 180. In S1407, the print extension application 180 obtains the cloud printer ID returned from the Windows OS and saves it to HDD202. After that, this process ends. In this embodiment, PC110 obtains the cloud printer ID from the cloud printing service, but it may also be obtained from the data conversion service 320.

[0070] As described above, this embodiment allows for the acquisition of printer status information in a suitable manner. Specifically, the print extension application 180 acquires a cloud printer ID via the OS to identify the printer on the cloud printing system. This enables the print extension application 180 to acquire and display the status information of the printer at any time. In the above embodiment, an example of any time is described as when the user presses the update button 605, but this is not limited to this. For example, the status update may be set to automatic. That is, the print extension application 180 may perform the update process automatically at predetermined intervals.

[0071] <Other Embodiments> This disclosure can also be implemented by supplying a program that implements one or more of the functions of the embodiments described above to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be implemented by a circuit (e.g., an ASIC) that implements one or more functions.

[0072] Furthermore, in the embodiments described above, an OS equivalent to Windows® 10 was used as an example, but the system is not limited to this OS, and any OS can be used. Also, in the embodiments described above, Ethernet was used as an example of the network 4 configuration, but the system is not limited to this example, and any other network configuration such as wireless LAN, IEEE1394, Bluetooth®, etc., may be used.

[0073] Furthermore, although the above-described embodiment uses the print extension application 180, the invention is not limited to this example, and for example, the functions related to this disclosure of the print extension application 180 may be implemented using the OS standard printer driver.

[0074] Furthermore, the above-described embodiment illustrates an example of a configuration in which a personal computer and a printer are connected via the Internet, and printing is performed from the personal computer to the printer. However, the system is not limited to this example; it can also be implemented in a configuration in which a personal computer and a scanner are connected via the Internet, and a document is scanned from the personal computer to the scanner.

[0075] Although each embodiment has been described in detail above, the invention is not limited to any particular embodiment, and various modifications and changes are possible within the scope of the gist of this disclosure. [Explanation of Symbols]

[0076] 180, 280 Print Extension Applications 120, 220 printers 310 Cloud Printing Service 320 Data Conversion Services

Claims

1. A program that can operate on an information processing device and functions as a printing extension application for extending the printing function in a printing system having the information processing device, a cloud printing service, a data conversion service, and a printing device that can support the cloud printing service via the data conversion service, The aforementioned information processing device The printing system includes an acquisition means for acquiring printer identification information that identifies the printing device, A request means that uses the acquired printer identification information to request printer status information of the printing device from the data conversion service, A display control means for displaying the printer status information acquired by the request means in the display area of ​​a web browser, toast notification, or the print extension application, A program characterized by its ability to function in a certain way.

2. When the request means requests the printer status information by adding the printer-specific information to the query parameters of the URL for accessing the printer status information display screen provided by the data conversion service, The program according to claim 1, characterized in that the display control means controls the display of a web page of printer status information corresponding to the printer specific information in the display area of ​​the management screen provided by the web browser or the print extension application.

3. The acquisition means is the program according to claim 1, characterized in that it acquires the printer-specific information from the cloud printing service or the data conversion service using the IPP Shared Infrastructure Extensions (INFRA) mechanism.

4. The program according to any one of claims 1 to 3, characterized in that the printer status information includes at least one of ink level, online status, offline status, and error information.

5. The program according to any one of claims 1 to 4, characterized in that the request means requests printer status information of the printing device at predetermined intervals or when an update button is pressed on the management screen corresponding to the printing device in the print extension application.

6. The information processing device in a printing system having an information processing device, a cloud printing service, a data conversion service, and a printing device capable of supporting the cloud printing service via the data conversion service, The printing system includes an acquisition means for acquiring printer identification information that identifies the printing device, A request means that uses the acquired printer identification information to request printer status information of the printing device from the data conversion service, A display control means for controlling the display of the printer status information acquired by the request means in the display area of ​​a web browser, toast notification, or print extension application, An information processing device characterized by comprising:

7. A method for controlling the information processing device in a printing system having an information processing device, a cloud printing service, a data conversion service, and a printing device capable of supporting the cloud printing service via the data conversion service, The printing system includes an acquisition step of acquiring printer identification information to identify the printing device, A request step of requesting the data conversion service to provide printer status information of the printing device using the acquired printer identification information, A display control step that controls the display of the printer status information obtained by the request step in the display area of ​​a web browser, toast notification, or print extension application, A control method for an information processing device, characterized by comprising the following:

8. A printing system comprising an information processing device, a cloud printing service, a data conversion service, and a printing device capable of supporting the cloud printing service via the data conversion service, The aforementioned information processing device The printing system includes an acquisition means for acquiring printer identification information that identifies the printing device, A request means that uses the acquired printer identification information to request printer status information of the printing device from the data conversion service, A display control means for controlling the display of the printer status information acquired by the request means in the display area of ​​a web browser, toast notification, or print extension application, A printing system characterized by comprising the following features.

Images