Control method of information processing device, program, and information processing device

Abstract

To provide a control method of an information processing device capable of displaying in detail a state of a printing device with an extended application associated with a printer driver that can communicate with any printing devices of different types, a program, and an information processing device.SOLUTION: In a control method of a host computer 101 including: a standard driver 202 that can communicate with any printing devices of different types with an Internet Printing Protocol; and an extended application 204 which extends a function of the standard driver 202 in association with the standard driver 202, the extended application 204 acquires status information of a printing device connected with the host computer 101 by a method different from the communication with the Internet Printing Protocol, and the extended application 204 displays a status information notification window 701 on the basis of the acquired status information.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to a control method for an information processing device, a program, and an information processing device. [Background technology]

[0002] There is a known technology that uses a printer driver installed on a host computer as control software for the printing device to issue print instructions to a printing device connected to the host computer. In this technology, an operating system (hereinafter referred to as "OS"), which is basic software, is installed in the host computer, and the printer driver is configured according to specifications defined by the OS and is called by the OS to operate. In more detail, for example, a printer driver specific to the model that conforms to the OS specifications is provided by the printing device vendor (manufacturer), and the printer driver uses the OS to obtain information about the status of the printing device (hereinafter referred to as "status information") and displays it on the computer screen. This allows the printing device vendor to provide a means for users to check the status information.

[0003] Furthermore, in recent years, Windows® has come standard with a class driver (hereinafter also referred to as a "standard driver") that can be commonly used for each printing device provided by multiple vendors, that is, for each printing device of different models. The standard driver is included in the OS package, and can be easily used by connecting any printing device to the host computer. Therefore, when Windows® is installed as the OS on the host computer, there is no need to separately install a model-specific printer driver in order to issue a print instruction. For this reason, the standard driver is highly convenient.

[0004] The standard driver also obtains status information from the printing device connected to the host computer using a standard communication protocol. More specifically, the standard driver obtains status information from the host computer by communicating with the printing device according to a communication standard such as the Internet Printing Protocol (hereinafter referred to as "IPP"). This allows a user using the standard driver to check status information according to the capabilities of the printing device connected to the host computer, even though the user is using a single standard driver.

[0005] Furthermore, a standard driver can be associated with an application for function extension (hereinafter referred to as an "extension application"). The extension application can be provided by the printing device vendor. By providing an extension application, the printing device vendor can provide functions (i.e., extended functions) that cannot be realized by the standard driver alone. Patent Document 1 describes a method for utilizing model-specific functions by acquiring information about the model-specific functions in a general-purpose driver. Patent Document 2 describes a method for providing a monitor program that acquires status information of a printing device by switching between communication protocols and displaying the information on a terminal screen. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2020-4159 A [Patent Document 2] JP 2017-68659 A Summary of the Invention [Problem to be solved by the invention]

[0007] Incidentally, model-specific printer drivers provided by printing device vendors can use communication protocols (hereafter referred to as "vendor protocols") that are uniquely defined by the printing device vendor. By using the vendor protocol, model-specific printer drivers can also obtain status information related to vendor-specific or model-specific functions, making it possible to provide detailed information about the status of the printing device.

[0008] In contrast, standard drivers that can be used regardless of the model of printing device use the standard communications standard IPP, so it may not be possible to obtain status information related to vendor-specific or model-specific functions, and it may not be possible to provide detailed information about the status of the printing device. Also, extension applications provided by printing device vendors may or may not be able to use vendor protocols, depending on the type of standard driver and the type of communications interface. However, because extension applications extend the functions of the standard driver, they are required to provide a function that allows users to accurately check status information even if they cannot use vendor protocols.

[0009] The present invention has been made in consideration of the above problems, and has an object to provide a method and program for controlling an information processing device that can display the status of a printing device in detail using an extended application associated with a printer driver that can communicate with any of different models of printing devices, and an information processing device. [Means for solving the problem]

[0010] In order to achieve the above-mentioned object, the control method of an information processing device of the present invention is a control method of an information processing device having a printer driver capable of communicating with any printing device of a different model using a first protocol, and an extension application associated with the printer driver and extending the functions of the printer driver, characterized in that it comprises a first acquisition step in which the extension application acquires first status information of a printing device connected to the information processing device using a method other than communication using the first protocol, and a display control step in which the extension application displays a status information notification screen based on the first status information. Effect of the Invention

[0011] According to the present invention, the status of a printing device can be displayed in detail using an extension application associated with a printer driver that can communicate with any of different models of printing devices. [Brief description of the drawings]

[0012] [Figure 1] FIG. 2 is a block diagram showing a hardware configuration of the printing system. [Diagram 2] FIG. 2 is a block diagram illustrating the software configuration of the printing system according to the first embodiment. [Diagram 3] 13 is a flowchart of a display process of a status information notification screen. [Figure 4] 13 is a flowchart of a connection mode specifying process. [Diagram 5] 13 is a flowchart of a process for determining a status information acquisition method. [Figure 6] 11 is a flowchart of a status information complementation process in the first embodiment. [Figure 7] FIG. 13 is a diagram showing an example of a status information notification screen when the communication protocol is a vendor protocol in the first embodiment, and is a diagram showing an example of detailed guidance that can be displayed on the display unit by the notification unit. [Figure 8]13 is a diagram showing an example of a status information notification screen when the communication protocol is IPP and the status information complementation process is not performed, and is a diagram showing an example of guidance that can be displayed on the display unit by the notification unit. FIG. [Figure 9] 11A and 11B are diagrams illustrating an example of a display when a notification unit displays a list of candidate error removal methods for a paper jam error on a display unit in the status information complementation process in the first embodiment. [Figure 10] FIG. 11 is a diagram showing an example of a status information notification screen when the communication protocol is IPP and the status information completion process is performed in the first embodiment, and is a diagram showing an example of detailed guidance that the notification unit can display on the display unit. [Figure 11] FIG. 11 is a block diagram for explaining the software configuration of a printing system according to second and third embodiments. [Figure 12] 13 is a flowchart of a status information complementation process in the second embodiment. [Figure 13] FIG. 13 is a diagram showing an example of a status information notification screen when the communication protocol is a vendor protocol in the second embodiment, and is a diagram showing an example of detailed guidance that can be displayed on the display unit by the notification unit. [Figure 14] 13 is a diagram showing an example of a status information notification screen when the communication protocol is IPP and the status information complementation process is not performed, and is a diagram showing an example of guidance that can be displayed on the display unit by the notification unit. FIG. [Figure 15] FIG. 11 is a diagram showing an example of a status information notification screen when the communication protocol is IPP and the status information completion process is performed in the second embodiment, and is a diagram showing an example of detailed guidance that the notification unit can display on the display unit. [Figure 16] 13 is a flowchart of a status information complementation process according to the third embodiment. [Figure 17] 13 is a diagram showing an example of a status information notification screen when the communication protocol is IPP and the status information complementation process is not performed, and is a diagram showing an example of guidance that can be displayed on the display unit by the notification unit. FIG. [Figure 18]FIG. 13 is a diagram showing an example of a status information notification screen when the communication protocol is IPP and the status complementation process is performed in the third embodiment, and is a diagram showing an example of appropriate guidance that the notification unit can display on the display unit. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Each embodiment of the present invention will be described in detail below with reference to the drawings. However, the configurations described in each of the following embodiments are merely examples, and the scope of the present invention is not limited by the configurations described in each embodiment. For example, each part constituting the present invention can be replaced with any configuration that can exert a similar function. In addition, any configuration may be added. In addition, any two or more configurations (features) of each embodiment can be combined.

[0014] <<First embodiment>> The first embodiment will be described below with reference to FIGS.

[0015] <Printing system hardware configuration> Fig. 1 is a block diagram showing the hardware configuration of a printing system. As shown in Fig. 1, the printing system includes a host computer 101 and a printing device 102. The host computer 101 is an example of an information processing device, and includes an input interface 110, a CPU 111, a ROM 112, a RAM 113, an external storage device 114, an output interface 115, and an input / output interface 116. Input devices such as a pointing device 117 and a keyboard 118 are connected to the input interface 110, and a display device such as a display unit 119 is connected to the output interface 115. An initialization program and the like are stored in the ROM 112.

[0016] The external storage device 114 stores application programs, an OS, standard drivers, and various other data. The RAM 113 is used as a work memory when the various programs stored in the external storage device 114 are executed, and the various programs are operable within the host computer 101. In the first embodiment, the CPU 111 executes processes according to the procedures of the programs stored in the ROM 112, thereby executing the functions of the host computer 101 described below and the processes shown in the flowcharts described below. The printing device 102 is connected to the host computer 101 via an input / output interface 116.

[0017] Here, the host computer 101 and the printing device 102 are configured separately, but they may be configured as a single information processing device. The printing device 102 may also have other functions (e.g., a scanner) that use IPP as a communication protocol. As mentioned above, IPP stands for Internet Printing Protocol, which is a standard communication specification. The host computer 101 may be a desktop personal computer, a smartphone, or a notebook computer.

[0018] <Software-centric printing system configuration> FIG. 2 is a block diagram for explaining the software configuration of a printing system. Here, the explanation is based on the premise that the printing system uses a host computer 101 equipped with Microsoft (registered trademark) Windows (registered trademark) 11 as the OS. In FIG. 2(a), the host computer 101 has a drawing application 201, a standard driver 202 (printer driver), and print function information 203 as its software configuration. Note that FIG. 2(a) is a diagram showing the software configuration of a general printing system in the case where the extension application 204 in FIG. 2(b) is not associated with the standard driver 202 and the printing device 102. Note that the extension application 204 is provided by the vendor of the printing device 102 as described above.

[0019] The drawing application 201 is software that creates content (drawing data) to be printed. The drawing application 201 corresponds to, for example, a word processing application or a spreadsheet application. When the drawing application 201 receives a print request from a user, it issues a print instruction to the OS. The print instruction includes print setting information for instructing the operation of the standard driver 202 and the printing device 102. The print setting information is also called a Print Ticket. In order to output the print setting information, the drawing application 201 can display a print setting screen provided by the standard driver 202, the OS, or the drawing application 201.

[0020] The print setting screen includes setting items indicating print functions that can be set and control items indicating their setting values ​​according to capability information (information that can be set as print settings) acquired from the standard driver 202. The capability information is also called Print Capabilities (hereinafter, referred to as "PC"). The standard driver 202 determines the PC based on the print function information 203. The print function information 203 is data indicating all print functions that can be set, their setting values, and the print functions in which the exclusive relationships between the setting values ​​are described. The print function information 203 is also called PDC (Print Device Capabilities). The print function information 203 is included in a configuration file of the standard driver 202, and is arranged in the external storage device 114 as an unchangeable file. Alternatively, the print function information 203 can be dynamically generated by the standard driver 202 or the OS.

[0021] In more detail, the standard driver 202 or the OS can be configured to acquire printing device attribute data from the printing device 102, and generate printing capability information 203 according to the attribute information in the acquired printing device attribute data. When the printing capability information 203 is dynamically generated, the generated printing capability information 203 can be edited. Note that the printing device attribute data acquired from the printing device 102 is a response acquired by issuing a Get-Printer-Attributes operation of IPP (Internet Print Protocol) to the printing device 102. The response includes attribute information indicating functions that can be specified by the printing device 102 (the capabilities of the printing device 102), and setting values ​​related to the attribute information. The response is saved in the RAM 113.

[0022] By configuring in this manner, the standard driver 202 can be configured to allow the user to specify print functions available on a printing device according to the printing device connected to the host computer 101. In other words, even when printing devices with different functions or printing devices provided by different vendors are connected to the host computer 101, the standard driver 202 can be configured to allow the user to specify print functions available on the connected printing device. Note that here, a configuration using an IPP Class Driver that is installed as standard in Windows (registered trademark) 11 will be described as the standard driver 202.

[0023] The IPP Class Driver is a printer driver that executes print processing according to the specifications of a standard print protocol called IPP (first protocol), and is included in the OS package. The IPP Class Driver is not a printer driver specific to the model of the printing device 102, but a printer driver that can be commonly used for each printing device provided by multiple vendors, that is, for each printing device of different models. The IPP Class Driver acquires capability information of the connected printing device 102 and generates print function information 203 based on the capability information so that the user can specify the print functions supported by the printing device 102 connected to the host computer 101.

[0024] The OS generates intermediate data based on a print instruction output from the drawing application 201, and passes the intermediate data to the standard driver 202. Note that the data output by the drawing application 201 for printing is data in the Graphic Device Interface format (GDI format data) or data in the XML Paper Specification format (XPS format data). When an IPP Class Driver is used as the standard driver 202, if the data output by the drawing application 201 is GDI format data, the OS converts the GDI format data output from the drawing application 201 into XPS format data. Then, the OS passes the converted XPS format data to the standard driver 202 as intermediate data.

[0025] On the other hand, if the data output by the drawing application 201 is XPS format data, the OS passes the XPS format data as intermediate data to the standard driver 202. The intermediate data includes drawing data, which is information about a picture to be formed on paper, and print setting information set by the user. The standard driver 202 converts the passed intermediate data into print data that can be interpreted by the printing device 102, and sends it to the printing device 102. The print data includes drawing data, which is information about a picture to be formed on paper, and print setting attribute information (attribute information that specifies print settings) generated based on the print setting information set by the user. The print setting attribute information includes attribute information that indicates functions that can be specified by the printing device 102 (the capabilities of the printing device 102) and setting values ​​related to the attribute information.

[0026] The printing device 102 prints on paper based on the print data sent from the standard driver 202. At this time, the printing device 102 forms the drawing data included in the print data on paper in accordance with the print setting attribute information included in the print data. The print setting attribute information includes information on the print quality (priority on image quality, priority on speed, etc.), the size of the drawing data, and the drawing position (margins).

[0027] FIG. 2B is a diagram showing the software configuration of the printing system when the extension application 204 is associated with the standard driver 202 and the printing device 102. Configurations not specifically mentioned below are the same as those in FIG. 2A. The extension application 204 is software for extending the functions of the standard driver 202, and is software that is not included (bundled) in the OS in advance. Therefore, the user needs to operate the host computer 101 to download the extension application 204 from a server on the Internet to the host computer 101 and install it. Alternatively, the extension application 204 may be automatically installed in the host computer 101 based on the connection of the printing device 102 to the host computer 101.

[0028] In this case, when the printing device 102 is connected to the host computer 101, the OS acquires device identification information from the printing device 102. The OS downloads the extension application 204 corresponding to the acquired device identification information from a server on the Internet to the host computer 101 and installs it. That is, the standard driver 202 and the extension application 204 are held as separate files in the host computer 101. Note that the standard driver 202 and the extension application 204 may be updated and upgraded, but these update processes are also performed at different times. That is, in the host computer 101, the timing at which the standard driver 202 is updated is different from the timing at which the extension application 204 is updated. Also, in the host computer 101, the trigger for updating the standard driver 202 is different from the trigger for updating the extension application 204. Note that when the extension application 204 is installed, the OS associates the extension application 204 with the standard driver 202 and the printing device 102.

[0029] The extension application 204 described in the first embodiment has a print setting screen extension unit 205, a skip control unit 206, a print function extension unit 207, a print data editing unit 208, and a notification unit 209. The extension application 204 also has shared information 210 that can be commonly accessed by each of the units 205 to 209. The shared information 210 is actually a file stored in the external storage device 114, or information saved in the RAM 113. The extension application 204 writes and reads information to and from the shared information 210 by using an API (Application Program Interface) provided by the OS.

[0030] The extension application 204 may terminate its operation each time the processing of each of the units 205 to 209 is completed. In this case, the OS will start the extension application 204 each time it receives a request to use each of the units 205 to 209. Other configurations are also possible. For example, the OS may terminate the operation of the extension application 204 when the processing of the print setting screen extension unit 205 is completed, but may keep the extension application 204 running even after the processing of the skip control unit 206 is completed. Furthermore, the extension application 204 may cancel processing during the processing of each of the units 205 to 209. When the extension application 204 cancels processing, the job being processed in the print queue is deleted by the OS.

[0031] When the drawing application 201 receives a print request from a user, it issues a print instruction to the OS. In this configuration, as in the configuration of FIG. 2(a), the drawing application 201 can display a print setting screen. However, in this configuration, the print setting screen provided by the extended application 204 is displayed. More specifically, the print setting screen provided by the print setting screen extension unit 205 of the extended application 204 is displayed. Note that whether the print setting screen provided by the print setting screen extension unit 205 is displayed depends on the user's operation. In addition, when the drawing application 201 receives a print request from a user and issues a print instruction to the OS, the OS activates the skip control unit 206.

[0032] The skip control unit 206 performs skip control processing to determine whether or not to skip the conversion processing in the standard driver 202. After the skip control processing in the skip control unit 206, the OS generates intermediate data based on the print instruction output from the drawing application 201, and passes the intermediate data to the standard driver 202. Here, if the conversion processing in the standard driver 202 is not skipped, the intermediate data is converted by the standard driver 202 into print data that can be interpreted by the printing device 102, and the print data is passed to the print data editing unit 208.

[0033] On the other hand, when the conversion process in the standard driver 202 is skipped, the intermediate data is passed to the print data editing unit 208 without being converted into print data by the standard driver 202. This makes it possible for the intermediate data to be processed by the print data editing unit 208. The print data editing unit 208 edits the intermediate data passed from the standard driver 202 or the print data processed by the standard driver 202. Taking layout printing as an example of the editing content, the print data editing unit 208 changes the layout of the intermediate data or print data based on the print setting information for layout printing received from the OS.

[0034] Furthermore, the print data editing unit 208 can display a UI screen on the display unit 119, and can display the intermediate data or the layout result of the print data as a preview screen. Note that in the print data editing unit 208, the print data is not sent to the printing device 102 while the preview screen is open, and the print data sending process is performed when the preview screen is closed. After the print data editing unit 208 edits the print data, the print data is passed to the printing device 102. The printing device 102 prints on paper based on the accepted print data. Note that when the conversion process in the standard driver 202 is skipped, the print data editing unit 208 converts the passed intermediate data into print data that can be interpreted by the printing device 102. However, the intermediate data may be converted into print data by using a function provided by the OS.

[0035] The extension application 204 has a print function extension unit 207. The print function extension unit 207 can edit the print function information 203 (PDC) generated by the standard driver 202 or the OS. This allows the print function extension unit 207 to add functions provided by the extension application 204 and functions supported by the printing device 102 that are not supported by the standard driver 202. Furthermore, the print function extension unit 207 can add an exclusive relationship between the setting values ​​of the print functions. The OS starts the print function extension unit 207 when the extension application 204 is first associated with the standard driver 202 and the printing device 102. Furthermore, the OS may start the print function extension unit 207 at other times, such as when the OS is started. In this way, in a case where an optional device (e.g., a finisher) is added to the printing device 102 later and the functions related to printing are extended, the print function extension unit 207 can detect the extended function and add it to the print function information 203.

[0036] The extension application 204 also has a notification unit 209. The notification unit 209 displays a notification to the user in response to an error occurring in the printing device 102. For example, when an out-of-paper error occurs in the printing device 102, the standard driver 202 detects the out-of-paper error, and the OS uses a notification function of the OS called a toast notification to display a message on the display unit 119. When the user selects this toast notification with the pointing device 117 or the like, the notification unit 209 of the extension application 204 is called by the OS, and a UI screen of the notification unit 209 is displayed on the display unit 119.

[0037] On the UI screen of the notification unit 209, for example, a detailed message of a no-paper error and a paper refilling method are displayed. However, the notification unit 209 can display a notification to the user even when an error does not occur in the printing device 102. Note that once the extended application 204 transmits print data to the printing device 102, it cannot display a screen such as a guide associated with the print data during processing of each of the units 205 to 209. In addition, the configuration of the extended application 204 for realizing the first embodiment is not limited to having all of the above-mentioned functions (units), and may have only a part of the functions or other functions. In other words, it can be said that the extended application 204 has at least one function of the functions of each of the units 205 to 209. In addition, the extended application 204 may be simply called printing software.

[0038] As described above, the function of the print setting screen expansion unit 205 is to display a setting screen. The function of the skip control unit 206 is to control whether or not to skip the conversion process in the standard driver 202. The function of the print data editing unit 208 is to edit print data input to the printing device 102. The function of the print function expansion unit 207 is to expand functions that can be specified in the standard driver 202. The function of the notification unit 209 is to display a UI screen in response to an error occurrence in the printing device 102. Examples of UI screens displayed on the display unit 119 by the notification unit 209 include the status information notification screens 701 in FIGS. 7, 8, 10, 13, 14, 15, 17, and 18, which will be described later, and the candidate list screen 901 in FIG. 9, which will be described later.

[0039] <Status notification processing by notification unit> When a user makes a print request on the drawing application 201 to a print queue linked to the extended application 204, print processing is started on the printing device 102. At this time, for example, if an error occurs inside the printing device 102, the OS displays a toast notification indicating the occurrence of the error on the display unit 119. When the user selects this toast notification with the pointing device 117 or the like, the OS calls the notification unit 209 of the extended application 204. FIG. 3 is a flowchart of a display process of a status information notification screen that is performed when the notification unit 209 (first acquisition means) (display control means) of the extended application 204 is called from the OS.

[0040] The flowchart of the display process of the status information notification screen (method of controlling the information processing device) is realized by the CPU 111 (computer) expanding the program stored in the ROM 112 into the RAM 113 and executing it. This also applies to the flowcharts of the processes shown in Figs. 4, 5, 6, 12, and 16 described later. When the display process of the status information notification screen is started, first, in step S301, the notification unit 209 of the extension application 204 performs a process of identifying the connection type. In this process, the connection type between the printing device 102 and the input / output interface 116 of the host computer 101 in the print queue for which the user has made a print request is identified. Note that a detailed explanation of step S301 will be given in the explanation of Fig. 4 described later.

[0041] In step S302, the notification unit 209 performs a process for determining a status information acquisition method (determination step). In the process for determining a status information acquisition method, a communication protocol to be used in communication with the printing device 102 is determined according to the connection form identified in step S301. Note that step S302 will be described in detail later with reference to FIG. 5. The notification unit 209 may be configured to store the execution result after executing steps S301 and S302 once, rather than executing them every time status information is acquired, and thereafter refer to the execution result.

[0042] In step S303, the notification unit 209 communicates with the printing device 102 using the communication protocol determined in step S302, and acquires status information (second status information) from the printing device 102 (second acquisition step). In more detail, if the communication protocol determined in step S302 is a vendor protocol, the notification unit 209 acquires the status information of the printing device 102 by communication using the vendor protocol. As described above, the vendor protocol refers to a communication protocol that is uniquely defined by the vendor of the printing device 102. On the other hand, if the communication protocol determined in step S302 is IPP, that is, if the extension application 204 cannot communicate using the vendor protocol, the notification unit 209 acquires the status information of the printing device 102 by communication using IPP. As described above, the status information of the printing device 102 acquired by communication using the vendor protocol includes status information related to functions specific to the vendor or model, and is therefore more detailed than the status information of the printing device 102 acquired by communication using IPP.

[0043] In step S304, the notification unit 209 performs a process of complementing the status information (first acquisition process). A detailed description of step S304 will be given in the description of FIG. 6 described later. In this process, if the communication protocol determined in step S302 is IPP, information that cannot be acquired by communication using IPP is acquired as status complement information (first status information). In other words, if the extension application 204 cannot communicate using the vendor protocol, detailed status information equivalent to the status information acquired by communication using the vendor protocol is acquired by a method different from communication using IPP. In this way, the notification unit 209 compensates for the fact that communication using the vendor protocol is not possible, that is, the fact that detailed status information cannot be acquired. In step S305, the notification unit 209 generates a status information notification screen, which is a guide screen of the printing device 102, based on the acquired status information and status complement information, and displays it on the display unit 119 (display control process). Thereafter, the display process of the status information notification screen ends.

[0044] 4 is a flowchart of the connection mode specification process of the notification unit 209 in step S301. In the connection mode specification process, first, in step S401, the notification unit 209 specifies the type of the standard driver 202 assigned to the print queue. The types of the standard driver 202 whose functions can be extended by the extension application 204 include the above-mentioned IPP Class Driver (second printer driver) and also the UP Class Driver (first printer driver). The notification unit 209 can perform the specification in step S401 from the name of the standard driver 202. The UP Class Driver is a printer driver that is installed as standard in Windows (registered trademark) 11 and is used for printing using a cloud service provided by Microsoft (registered trademark).

[0045] In step S402, the notification unit 209 identifies the type of communication interface (communication port) assigned to the print queue. After that, the connection type identification process ends, and the process returns to the display process of the status information notification screen in Fig. 3. Note that the types of communication interfaces include a USB port (hereinafter referred to as "USB"), a WSD port (hereinafter referred to as "WSD"), and a TCP / IP port (hereinafter referred to as "TCP / IP"). USB stands for Universal Serial Bus. WSD stands for Web Service for Device. TCP / IP stands for Transmission Control Protocol / Internet Protocol.

[0046] 5 is a flowchart of the status information acquisition method determination process of the notification unit 209 in step S302. The status information acquisition method determination process determines whether the vendor protocol (second protocol) is available based on the type of the standard driver 202 and the type of the communication interface identified in steps S401 and S402. In the status information acquisition method determination process, first, in step S501, the notification unit 209 determines whether the type of the standard driver 202 identified in step S401 is an UP Class Driver. If the notification unit 209 determines that the type of the standard driver 202 identified in step S401 is an UP Class Driver, the process proceeds to step S502. On the other hand, if the notification unit 209 determines that the type of the standard driver 202 identified in step S401 is not an UP Class Driver, the process proceeds to step S503.

[0047] In step S502, the notification unit 209 determines the status information acquisition method to be "IPP (vendor protocol cannot be used)" regardless of the type of communication interface identified in step S402. This determination is made because, if the type of the standard driver 202 is a UP Class Driver, the extension application 204 cannot directly communicate with the printing device 102 using the vendor protocol to acquire status information. Thereafter, the process of determining the status information acquisition method ends, and the process returns to the display process of the status information notification screen in FIG. 3. In this case, the extension application 204 communicates with the printing device 102 via a cloud service not provided by the vendor of the printing device 102 (i.e., a cloud service provided by Microsoft (registered trademark)).

[0048] In step S503, the notification unit 209 determines whether the type of the communication interface identified in step S402 is USB (a specified communication interface). If the notification unit 209 determines that the type of the communication interface identified in step S402 is not USB, the process proceeds to step S504. On the other hand, if the notification unit 209 determines that the type of the communication interface identified in step S402 is USB, the process proceeds to step S505. In step S504, the notification unit 209 determines the status information acquisition method to be "vendor protocol." In this case, the type of the communication interface identified in step S402 is WSD, TCP / IP, or the like. Thereafter, the process of determining the status information acquisition method ends, and the process returns to the display process of the status information notification screen in FIG. 3.

[0049] In step S505, the notification unit 209 determines whether an identification ID (Identification), which is information specific to the model of the printing device 102 and is required when connecting via USB, is registered in the extension application 204. The identification ID (identification information) is set for each printing device by the printing device vendor and is provided to prevent unauthorized communication and use. If the notification unit 209 determines that the identification ID of the printing device 102 is registered in the extension application 204, the process proceeds to step S506. On the other hand, if the notification unit 209 determines that the identification ID of the printing device 102 is not registered in the extension application 204, the process proceeds to step S507.

[0050] In step S506, the notification unit 209 determines the status information acquisition method to be "vendor protocol". After that, the process of determining the status information acquisition method ends, and the process returns to the display process of the status information notification screen in FIG. 3. In step S507, the notification unit 209 determines the status information acquisition method to be "IPP (vendor protocol cannot be used)". In other words, if the type of communication interface identified in step S402 is USB, and the identification ID of the printing device 102 is not registered in the extension application 204, the extension application 204 cannot use the vendor protocol for the printing device 102. After that, the process of determining the status information acquisition method ends, and the process returns to the display process of the status information notification screen in FIG. 3.

[0051] Fig. 6 is a flowchart of the status information complementation process of the notification unit 209 in step S304. Fig. 6 describes an example of the status information complementation process in a situation where a paper jam error has occurred in the printing device 102, but application examples of this status information complementation process are not limited to paper jam errors. For example, if an out-of-paper error occurs in a printing device of a model with multiple paper feed ports, the status information is complemented by a similar process. That is, in the status information complementation process of Fig. 6, status information indicating the state of the printing process of the printing device 102 connected to the host computer 101 is complemented.

[0052] In the status information complementation process of FIG. 6, first, in step S601, the notification unit 209 determines whether the status information acquisition method determined in step S302 is IPP. If the notification unit 209 determines that the status information acquisition method determined in step S302 is not IPP, detailed status information has already been acquired by communication using the vendor protocol. Therefore, in this case, the status information complementation process ends, and the process returns to the display process of the status information notification screen in FIG. 3. On the other hand, if the notification unit 209 determines that the status information acquisition method determined in step S302 is IPP, the process proceeds to step S602. In this case, since the notification unit 209 cannot communicate using the vendor protocol, it acquires detailed status information by performing a status information complementation process in step S304 as described below.

[0053] In step S602, the notification unit 209 determines whether a paper jam error has occurred in the printing device 102. This determination is made based on the status information already acquired in IPP communication in step S303. If the notification unit 209 determines that a paper jam error has not occurred in the printing device 102, the status information complementation process ends, and the process returns to the display process of the status information notification screen in FIG. 3. In this case, only the status information already acquired in IPP communication in step S303 is displayed on the display unit 119. On the other hand, if the notification unit 209 determines that a paper jam error has occurred in the printing device 102, the process proceeds to step S603.

[0054] In step S603, the notification unit 209 acquires a list of error clearing methods candidates held by the extension application 204 when a paper jam error occurs. In detail, the vendor may want to inform the user of several methods for removing the jammed paper, such as methods for removing the jammed paper near the paper feed port or paper discharge port of the printing device, or methods for removing the jammed paper without removing a part of the printing device, depending on how easy it is to remove the jammed paper. Therefore, the extension application 204 internally holds a list of error clearing methods candidates when a paper jam error occurs. Note that such information may be held as model-specific information within the extension application 204, or may be held for all paper feed ports as model-independent information and dynamically determined from paper feed port information acquired by communication via IPP.

[0055] In step S604, the notification unit 209 displays the list of error recovery method candidates (candidate list) acquired in step S603 on the display unit 119 in a format selectable by the user. Ideally, it would be desirable to uniquely display detailed error recovery methods to be provided in accordance with the status information acquired from the printing device 102. However, in IPP communication, it may not be possible to display detailed error recovery methods, so in this way, the list of error recovery method candidates is displayed to the user, and the user is prompted to select an error recovery method, thereby supplementing the necessary information.

[0056] In step S605, the notification unit 209 accepts a user's selection operation for the list of error recovery method candidates displayed on the display unit 119 in step S604. The user selects a method that best matches the error situation and is easiest to recover from the list of error recovery method candidates displayed on the display unit 119 in step S604 using the pointing device 117 or the like. When the user selects one error recovery method from the list of error recovery method candidates displayed on the display unit 119, the process proceeds to step S606. In step S606, the notification unit 209 determines detailed guidance to be displayed on the display unit 119 corresponding to the selected error recovery method from information held inside the extended application 204. With this determination, the notification unit 209 obtains information that cannot be obtained by communication using IPP. After that, the completion process of the status information is completed, and the process returns to the display process of the status information notification screen in FIG. 3.

[0057] 7 is an example of a status information notification screen 701 when the communication protocol is a vendor protocol, and is a diagram showing an example of detailed guidance that the notification unit 209 can display on the display unit 119. In the case of FIG. 7, detailed status information is acquired through communication using a vendor protocol that is uniquely defined by the vendor of the printing device 102, so the status supplement information is not acquired in step S304. The status information notification screen 701 is made up of a status message 702, a browser launch button 703, a print cancel button 704, a remaining ink level indicator 705, an ink icon 706, and a browser launch button 707. When the browser launch button 703 is operated by a user using the pointing device 117 or the like, a Web manual is displayed on the display unit 119.

[0058] When a print cancel button 704 is operated by a user using the pointing device 117 or the like, a cancel instruction is issued for the job being printed. When a browser launch button 707 is operated by a user using the pointing device 117 or the like, a purchase site for ink, which is a consumable, is displayed on the display unit 119. A remaining amount display 705 is an indication of the remaining amount of ink installed in the printing device 102. An ink icon 706 is an indication of a warning when the remaining amount of ink is low. When communication is performed using a vendor protocol, the status information notification screen 701 in FIG. 7 can inform the user of detailed measures for the occurring error by the status message 702. At the same time, the status information notification screen 701 in FIG. 7 can guide the user to a Web manual by the browser launch button 703.

[0059] Fig. 8 is an example of a status information notification screen 701 when the communication protocol is IPP and the status information complementation process of step S304 is not performed, and is a diagram showing an example of guidance that the notification unit 209 can display on the display unit 119. Note that the status information notification screen 701 in Fig. 8 is not an example of a screen displayed by executing the display process of the status information notification screen in Fig. 3, but an example of a screen realized by conventional technology (i.e., a comparative example). 801 is a status message. 802 is an ink icon that is a warning display when the remaining ink is low.

[0060] When communication is performed using IPP, only generic status information indicating a paper jam, called a media-jam-error, is acquired, and therefore the status information notification screen 701 in Fig. 8 can only provide simple information such as a status message 801. Also, the browser launch button 703 in Fig. 7 is a function that transmits status information to a Web manual site and provides the user with detailed error resolution methods using a Web manual, but it does not exist on the status information notification screen 701 in Fig. 8. This is because when communication is performed using IPP, detailed status information cannot be transmitted, and therefore the Web manual site cannot be used. Note that configurations not specifically mentioned above are equivalent to those in Fig. 7.

[0061] FIG. 9 is a diagram showing a display example when the notification unit 209 displays a list of candidate error clearing methods for a paper jam error on the display unit 119 in the status information complementation process in step S304. In detail, the candidate list screen 901 in FIG. 9 shows a screen displayed in step S604. The candidate list screen 901 in FIG. 9 is composed of a message group 902, a list 903, and a selection completion button 904. The message group 902 describes a simple status message and a message to prompt the user to select a position where the paper is visible. The list 903 displays the list of candidate error clearing methods acquired in step S603. In the list 903, the user selects one error clearing method from the list of candidate error clearing methods using a radio button. The selection completion button 904 is for indicating that the user's selection has been completed. When the selection completion button 904 is operated by a user using the pointing device 117 or the like, details of the error resolution method selected in the list 903 are displayed on the display unit 119, for example, as in a status information notification screen 701 of Figure 10 described later.

[0062] FIG. 10 is an example of a status information notification screen 701 when the communication protocol is IPP and the status information complementation process of step S304 is performed, and is a diagram showing an example of detailed guidance that the notification unit 209 can display on the display unit 119. The status information notification screen 701 of FIG. 10 displays a status message 1001 by performing the status information complementation process of step S304 according to the flowchart of FIG. 6. The status information notification screen 701 of FIG. 10 can provide the user with detailed guidance equivalent to the status message 702 when the communication protocol is the vendor protocol by using the status message 1001. In addition, the status information notification screen 701 of FIG. 10 displays the above-mentioned browser start button 703 by performing the status information complementation process of step S304 according to the flowchart of FIG. 6. Therefore, the status information notification screen 701 of FIG. 10 can guide the user to the Web manual by using the browser start button 703. Note that configurations not specifically mentioned above are equivalent to those of FIG. 7 and FIG. 8.

[0063] As described above, in the first embodiment, in the host computer 101, the extension application 204 is associated with the standard driver 202 that can communicate with any printing device of a different model via IPP. Furthermore, even when communicating with the printing device 102 connected to the host computer 101 via IPP, the extension application 204 displays the status of the printing device 102 in the same level of detail as when communicating with the printing device 102 via vendor protocol.

[0064] In more detail, the extended application 204 displays a list of candidate error recovery methods based on the status information of the printing device 102 acquired through IPP communication, and accepts a user's selection operation on the list of candidate error recovery methods. As a result, even when communicating with the printing device 102 through IPP, the extended application 204 can acquire new information using a method other than IPP communication, thereby enabling detailed status notification as shown on the status information notification screen 701 in Fig. 10. In other words, even if communication through a vendor protocol uniquely defined by the vendor of the printing device 102 is not possible, the extended application 204 can enable detailed status notification by utilizing a user's selection operation on the list of candidate error recovery methods.

[0065] In the first embodiment, the extension application 204 switches the communication protocol used in communication with the printing device 102 between the vendor protocol and IPP depending on the type of the standard driver 202 and the type of the communication interface. Furthermore, when the communication protocol used in communication with the printing device 102 is the vendor protocol, the extension application 204 provides detailed guidance to the user using status information of the printing device 102 acquired through communication using the vendor protocol. On the other hand, when the communication protocol used in communication with the printing device 102 is IPP, the extension application 204 provides detailed guidance to the user by accepting user input and complementing the information. In this way, the extension application 204 can notify the user of the status as detailed as possible, regardless of the type of the standard driver 202 and the type of the communication interface.

[0066] <<Second embodiment>> The second embodiment will be described below with reference to Figs. 11 to 15. Here, the differences from the first embodiment will be mainly described. In the first embodiment, the extended application 204 was required to internally hold the necessary information. That is, in the first embodiment, the extended application 204 is required to hold all the information specific to the printing device that guarantees the operation. Therefore, in the first embodiment, regular release of the extended application 204 to the market is essential in anticipation of the case where the number of models that the extended application 204 targets increases or the case where the information held by the extended application 204 has an error and needs to be corrected. In consideration of this point, in the second embodiment, the necessary information is held externally, such as in a server. Furthermore, the extended application 204 can provide detailed guidance to the user when an error occurs in the printing device 102 by referring to the information held externally as necessary, in the same manner as in the first embodiment. Note that configurations and processes not mentioned below are the same as those in the previous embodiments, and therefore will not be described.

[0067] Fig. 11 is a block diagram for explaining the software configuration of the printing system in the second and third embodiments. In the printing system in the second and third embodiments, an extension application 204 is configured to be associated with a standard driver 202 and the printing device 102. Furthermore, a notification unit 209 is configured to acquire necessary information from a database of an external management server 1101 (server) that holds service information related to the printing device 102 and information unique to the printing device 102. Note that the configuration in Fig. 11 other than the above is the same as Fig. 2(b) of the first embodiment, and therefore description thereof will be omitted.

[0068] FIG. 12 is a flowchart of the status information complementation process (step S304) of the notification unit 209 in the second embodiment. In FIG. 12, the status information complementation process in a situation where an out-of-ink error occurs in the printing device 102 is described as an example, but the application example of this status information complementation process is not limited to an out-of-ink error. For example, status information as to whether firmware newer than the firmware currently in use exists and is usable, which is determined from the printer name of the printing device 102 and the version of the firmware used by the printing device 102, is complemented by a similar process. In other words, in the status information complementation process of FIG. 12, status information indicating the status of the printing device 102 connected to the host computer 101, the status of the printing process of the printing device 102, the status of consumables (ink) installed in the printing device 102, etc. is complemented.

[0069] In the status information complementation process of FIG. 12, step S601 is executed first, and is the same process as in the first embodiment, so description thereof will be omitted. In step S601 of FIG. 12, if the notification unit 209 determines that the status information acquisition method determined in step S302 is IPP, the process proceeds to step S1201. In step S1201, the notification unit 209 determines whether an out-of-ink error has occurred in the printing device 102. This determination is made based on the status information already acquired in step S303 by communication using IPP. In the case where the notification unit 209 determines that an out-of-ink error has not occurred in the printing device 102, the status information complementation process ends, and the process returns to the display process of the status information notification screen in FIG. 3. In this case, only the status information already acquired in step S303 by communication using IPP is displayed on the display unit 119. In contrast, if the notification unit 209 determines that an out-of-ink error has occurred in the printing device 102, the process proceeds to step S1202.

[0070] In step S1202, the notification unit 209 determines whether or not the printer name of the printing device 102 and destination information regarding the main body of the printing device 102 (hereinafter referred to as "main body destination information") have been acquired by acquiring the status information by IPP in step S303. If the notification unit 209 determines that the printer name and main body destination information of the printing device 102 have not been acquired by acquiring the status information by IPP in step S303, the status information complementation process ends. Thereafter, the process returns to the display process of the status information notification screen in FIG. 3. Note that in this case, only the status information already acquired by communication by IPP in step S303 is displayed on the display unit 119. On the other hand, if the notification unit 209 determines that the printer name and main body destination information of the printing device 102 have been acquired by acquiring the status information by IPP in step S303, the process proceeds to step S1203.

[0071] In step S1203, the notification unit 209 transmits the printer name and main body destination information of the printing device 102 already acquired in step S303 to the external management server 1101, and acquires, as a response value, a list of ink model numbers that can be installed in the printing device 102. In this way, the notification unit 209 acquires information that cannot be acquired through IPP communication. Thereafter, the status information complementation process ends, and the process returns to the display process of the status information notification screen in FIG. 3.

[0072] FIG. 13 is an example of a status information notification screen 701 when the communication protocol is a vendor protocol, and is a diagram showing an example of detailed guidance that the notification unit 209 can display on the display unit 119. In the case of FIG. 13, detailed status information is acquired by communication using a vendor protocol that is uniquely defined by the vendor of the printing device 102, so the status supplement information of step S304 is not acquired. The status information notification screen 701 of FIG. 13 can provide detailed guidance regarding an ink-out error by a status message 1301. In addition, the status information notification screen 701 of FIG. 13 displays an installed ink model number display button 1302. When the installed ink model number display button 1302 is operated by a user using the pointing device 117 or the like, a separate screen showing a list of ink model numbers installed in the printing device 102 is displayed on the display unit 119. However, the notification unit 209 may not display the installed ink model number display button 1302, and may display the model number in the status information notification screen 701 of FIG. 13. Configurations not specifically mentioned above are the same as those in FIG.

[0073] FIG. 14 is an example of a status information notification screen 701 when the communication protocol is IPP and the status information complementation process of step S304 is not performed, and is a diagram showing an example of guidance that the notification unit 209 can display on the display unit 119. Note that the status information notification screen 701 in FIG. 14 is not an example of a screen displayed by executing the display process of the status information notification screen in FIG. 3, but an example of a screen realized by a conventional technique (i.e., a comparative example). When communication is performed by IPP, only general-purpose status information according to the IPP standard can be acquired, so the status information notification screen 701 in FIG. 14 can only provide simple guidance such as a status message 1401. For the same reason, the status information notification screen 701 in FIG. 14 cannot display the mounted ink model number display button 1302 in FIG. 13. Note that configurations not specifically mentioned above are equivalent to those in FIG. 7 and FIG. 8.

[0074] Fig. 15 is an example of a status information notification screen 701 when the communication protocol is IPP and the status information complementation process of step S304 has been performed, and is a diagram showing an example of detailed guidance that the notification unit 209 can display on the display unit 119. The status information notification screen 701 of Fig. 15 displays a status message 1501 including the ink model number that is the subject of the currently occurring no-ink error, as a result of the status information complementation process of step S304 being performed according to the flowchart of Fig. 12. The status information notification screen 701 of Fig. 15 can provide the user with detailed guidance equivalent to that of the status message 1301 when the communication protocol is a vendor protocol, by using the status message 1501.

[0075] Furthermore, the status information notification screen 701 in Fig. 15 displays the above-mentioned mounted ink model number display button 1302 as a result of the status information complementation process in step S304 being performed according to the flowchart in Fig. 12. Therefore, on the status information notification screen 701 in Fig. 15, the mounted ink model number display button 1302 causes a separate screen showing a list of the ink model numbers mounted on the printing device 102 to be displayed on the display unit 119. Note that configurations not specifically mentioned above are the same as those in Figs. 7 and 8.

[0076] As described above, in the second embodiment, similarly to the first embodiment, an extension application 204 is associated with a standard driver 202 capable of communicating with any printing device of a different model via IPP in the host computer 101. Furthermore, even when communicating with a printing device 102 connected to the host computer 101 via IPP, the extension application 204 displays the status of the printing device 102 in the same detail as when communicating with the printing device 102 via vendor protocol.

[0077] In more detail, the extension application 204 acquires a list of model numbers of inks that can be installed in the printing device 102 from a database of the external management server 1101 based on the status information of the printing device 102 acquired through IPP communication. As a result, even when the extension application 204 communicates with the printing device 102 through IPP, it is possible to provide a detailed status notification as shown on a status information notification screen 701 in FIG. 15 by acquiring new information using a method other than IPP communication.

[0078] <<Third embodiment>> Hereinafter, the third embodiment will be described with reference to Figs. 16 to 18. In the first embodiment, the extension application 204 holds the necessary information, and in the second embodiment, the external management server 1101 holds the necessary information. In addition, this information is information specific to the printing device 102. However, when a user actually uses the printing device 102, the user may be subscribed to a service provided by the vendor of the printing device 102. In this case, in addition to the information specific to the printing device 102, it is necessary to consider information specific to the user. In consideration of this point, in the third embodiment, information such as what services are provided to the printing device 102 is held by the external management server 1101.

[0079] Furthermore, the extended application 204 refers to information stored in an external management server 1101 or the like when generating a status information notification screen, displays the service provision status, and allows the user to select the service subscription status. In this way, in the third embodiment, appropriate guidance is provided to the user. The following description will focus on the differences from the second embodiment. Therefore, the configurations and processes not mentioned below are the same as those in the second embodiment, and will not be described here.

[0080] FIG. 16 is a flowchart of the status information complementation process (step S304) of the notification unit 209 in the third embodiment. In the status information complementation process in FIG. 16, step S601 is executed first, and the description thereof will be omitted since it is the same process as in the first embodiment. Note that, in step S601 in FIG. 16, if the notification unit 209 determines that the status information acquisition method determined in step S302 is IPP, the process proceeds to step S1601. In step S1601, the notification unit 209 transmits the printer name and main body destination information acquired in step S303 to the external management server 1101. Furthermore, in step S1601, the notification unit 209 acquires the status of the service provided by the vendor of the printing device 102 to the printing device 102 (hereinafter, referred to as "provision status of the service to the printing device 102") as a response value of the transmission. Note that the determination process in step S1202 in FIG. 12 may be performed between step S601 and step S1601.

[0081] In step S1602, the notification unit 209 determines whether the service provision status for the printing device 102 acquired in step S1601 affects the configuration and display of the status information notification screen 701. This determination is made, for example, based on a table stored in the extended application 204 indicating the relationship between the impact on the configuration and display of the status information notification screen 701 and the service, and on the table and the service provision status for the printing device 102. Note that such a determination formula may be stored in a database of the external management server 1101, and the notification unit 209 of the extended application 204 may refer to the determination result in the external management server 1101.

[0082] If the notification unit 209 determines that the service provision status for the printing device 102 acquired in step S1601 does not affect the configuration and display of the status information notification screen 701, the status information complementation process ends. Thereafter, the process returns to the display process for the status information notification screen in Fig. 3. In this case, only the status information already acquired through IPP communication in step S303 is displayed on the display unit 119. On the other hand, if the notification unit 209 determines that the service provision status for the printing device 102 acquired in step S1601 will affect the configuration and display of the status information notification screen 701, the process proceeds to step S1603.

[0083] In step S1603, the notification unit 209 displays on the display unit 119 a screen for the user to select the subscription status of a service from a list of services (candidate list) provided to the printing device 102. In step S1604, the notification unit 209 accepts a user's selection operation for the subscription status of the service. In step S1605, the notification unit 209 determines the configuration and display of the status information notification screen 701 from the user's selection operation. In this way, the notification unit 209 obtains information that cannot be obtained by IPP communication. Thereafter, the status information complementation process ends, and the process returns to the display process of the status information notification screen in FIG. 3. In the following, a case will be described in which the vendor of the printing device 102 provides a flat-rate ink service to the printing device 102 and the user subscribes to the service. Therefore, in the status information complementation process in FIG. 16, status information indicating the state of the printing device 102 connected to the host computer 101 is complemented.

[0084] FIG. 17 is an example of a status information notification screen 701 when the communication protocol is IPP and the status information complementation process of step S304 is not performed, and is a diagram showing an example of guidance that the notification unit 209 can display on the display unit 119. Note that the status information notification screen 701 of FIG. 17 is not an example of a screen displayed by executing the display process of the status information notification screen of FIG. 3, but an example of a screen realized by the conventional technology (i.e., a comparative example). If a flat-rate service for ink, which is a consumable item, is provided to the printing device 102 by the vendor of the printing device 102 and the user is subscribed to the service, the browser launch button 707 that displays the ink purchase site should not be displayed. However, the browser launch button 707 is displayed on the status information notification screen 701 of FIG. 17. Note that configurations not specifically mentioned above are the same as those of FIG. 7.

[0085] Fig. 18 is an example of a status information notification screen 701 when the communication protocol is IPP and the status information complementation process of step S304 has been performed, and is a diagram showing an example of appropriate guidance that the notification unit 209 can display on the display unit 119. By performing the status information complementation process of step S304 according to the flowchart of Fig. 16, the above-mentioned browser launch button 707 is hidden only for users who have subscribed to the ink flat-rate service, as in the status information notification screen 701 of Fig. 18. Note that configurations not specifically mentioned above are the same as those in Fig. 7.

[0086] As described above, in the third embodiment, as in the first and second embodiments, in the host computer 101, the extension application 204 is associated with the standard driver 202 that can communicate with any printing device of a different model via IPP. Furthermore, even when communicating with the printing device 102 connected to the host computer 101 via IPP, the extension application 204 displays the status of the printing device 102 with the same appropriateness as when communicating with the printing device 102 via vendor protocol. In detail, on the status information notification screen 701 in FIG. 18, the browser launch button 707 that displays the ink purchase site is appropriately displayed or hidden according to the user's subscription status to the ink flat-rate service.

[0087] Furthermore, in the third embodiment, the extended application 204 acquires the service provision status for the printing device 102 from the database of the external management server 1101 based on the status information of the printing device 102 acquired through IPP communication. Furthermore, the extended application 204 displays a list of services provided to the printing device 102 and accepts a user's selection operation regarding the subscription status of the service. As a result, even when communicating with the printing device 102 through IPP, the extended application 204 can acquire new information using a method other than IPP communication, thereby enabling appropriate status notification as in the status information notification screen 701 in FIG. 18.

[0088] In this way, the extended application 204 can display a list of candidates by referencing data managed in a database of the external management server 1101, and the user can select a candidate that matches his or her own situation, thereby providing appropriate guidance. In other words, the extended application 204 can provide appropriate guidance by determining whether the user has subscribed to a service provided to the printing device 102 through a combination of use of the database of the external management server 1101 and a selection operation by the user.

[0089] <<Other>> Although the preferred embodiments of the present invention have been described above, the present invention is not limited to the above-mentioned embodiments, and various modifications and changes are possible within the scope of the gist of the present invention. Here, a case will be described in which the type of the standard driver 202 is a UP Class Driver, and the printing device 102 can communicate with the cloud service using a communication protocol equivalent to a vendor protocol. In this case, the host computer 101 and the printing device 102 cannot communicate directly, but the cloud service can obtain status information of the printing device 102 from the printing device 102 using a communication protocol equivalent to the vendor protocol. Therefore, the extended application 204 may obtain status information of the printing device 102 from the cloud service using a communication protocol different from IPP. In this way, when an error occurs in the printing device 102, the extended application 204 can obtain new information using a method other than IPP communication, thereby enabling detailed status notification.

[0090] The extended application 204 may also acquire new information by combining information from the above-mentioned cloud service and information from a database of the external management server 1101. The extended application 204 may also acquire new information by combining information from the above-mentioned cloud service and a user's selection operation on a candidate list related to the information. The extended application 204 may also acquire new information by combining information from the above-mentioned cloud service, information from a database of the external management server 1101, and a user's selection operation on a candidate list related to the information. The extended application 204 may also acquire new information by combining multiple pieces of information that can be acquired by communication using IPP when communication using the vendor protocol is not possible.

[0091] The present invention can also be realized by a process in which a program for realizing one or more functions of each of the above-mentioned embodiments is supplied to a system or device via a network or a storage medium, and one or more processors of a computer in the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) for realizing one or more functions.

[0092] The disclosure of each embodiment includes the following methods, programs, and configurations. (Method 1) A method for controlling an information processing apparatus having a printer driver capable of communicating with any printing device of a different model using a first protocol, and an extension application associated with the printer driver for extending a function of the printer driver, comprising: a first acquisition step in which the extension application acquires first status information of a printing device connected to the information processing device using a method other than communication according to the first protocol; A control method for an information processing device, comprising: a display control step of the extended application displaying a status information notification screen based on the first status information. (Method 2) A second acquisition step in which the extension application acquires second status information of a printing device connected to the information processing device through communication using the first protocol, The control method for an information processing device described in Method 1, characterized in that in the display control process, the extended application displays the status information notification screen based on the first status information and the second status information. (Method 3) A control method for an information processing device described in Method 1 or 2, characterized in that the first status information is information indicating at least one of the status of a printing device connected to the information processing device, the status of printing processing, and the status of consumables installed in a printing device connected to the information processing device. (Method 4) The method for controlling an information processing device according to any one of Methods 1 to 3, wherein the first status information is information that cannot be acquired through communication according to the first protocol. (Method 5) A control method for an information processing device described in any one of Methods 1 to 4, characterized in that in the first acquisition process, the extended application acquires the first status information by utilizing a server database as a method other than communication via the first protocol. (Method 6) A control method for an information processing device described in any one of Methods 1 to 4, characterized in that in the first acquisition process, the extended application acquires the first status information by using a cloud service as a method other than communication by the first protocol. (Method 7) A control method for an information processing device described in any one of Methods 1 to 4, characterized in that in the first acquisition process, the extended application acquires the first status information by utilizing a user's selection operation on a candidate list as a method other than communication via the first protocol. (Method 8) A control method for an information processing device described in any one of Methods 1 to 4, characterized in that in the first acquisition process, the extended application acquires the first status information by combining at least two of a server database, a cloud service, and a user's selection operation on a candidate list as a method other than communication via the first protocol. (Method 9) The method for controlling an information processing device according to any one of Methods 1 to 8, wherein the first protocol is the Internet Printing Protocol. (Method 10) A control method for an information processing device described in Method 2, characterized in that in the first acquisition process, when the extended application is unable to communicate via a second protocol different from the first protocol, it acquires the first status information using a method other than communication via the first protocol. (Method 11) A control method for an information processing device described in Method 10, characterized in that in the second acquisition process, the extended application acquires the second status information by communication via the first protocol when communication via the second protocol is not possible. (Method 12) A method comprising the steps of: determining whether the extended application is capable of communicating using the second protocol; 12. The method for controlling an information processing device according to method 10 or 11, characterized in that in the determination step, the extension application determines that communication via the second protocol is not possible if the type of the printer driver is a first printer driver. (Method 13) A control method for an information processing device described in Method 12, characterized in that in the determination process, the extension application determines that communication via the second protocol is not possible when the type of the printer driver is a second printer driver different from the first printer driver and the type of the communication interface with the printing device connected to the information processing device is a specified communication interface and identification information necessary for the specified communication interface for the printing device connected to the information processing device is not registered in the extension application. (Method 14) The first protocol is the Internet Printing Protocol; 14. The method for controlling an information processing device according to any one of Methods 10 to 13, wherein the second protocol is a vendor protocol uniquely defined by a vendor of a printing device connected to the information processing device. (Program 1) A program for causing a computer to execute each step of the method for controlling an information processing device according to any one of Methods 1 to 14. (Configuration 1) An information processing apparatus having a printer driver capable of communicating with any printing device of a different model using a first protocol, and an extension application associated with the printer driver for extending a function of the printer driver, a first acquisition means for acquiring first status information of a printing device connected to the information processing device by the extension application using a method other than communication according to the first protocol; The information processing device according to claim 1, further comprising: a display control means for controlling display of a status information notification screen based on the first status information, wherein the extension application is configured to display the status information notification screen based on the first status information. [Explanation of symbols]

[0093] 101 Host computer (information processing device) 102 Printing device 202 Standard driver (printer driver) 204 Extended Applications 701 Status Information Notification Screen

Claims

1. A method for controlling an information processing apparatus having a printer driver capable of communicating with any printing apparatus of a different model using a first protocol, and an extension application associated with the printer driver for extending a function of the printer driver, comprising: a first acquisition step in which the extended application acquires first status information of a printing device connected to the information processing device using a method other than communication according to the first protocol; A control method for an information processing device, comprising: a display control step of the extended application displaying a status information notification screen based on the first status information.

2. a second acquisition step in which the extension application acquires second status information of a printing device connected to the information processing device through communication using the first protocol; 2. The method according to claim 1, wherein in the display control step, the extended application displays the status information notification screen based on the first status information and the second status information.

3. 2. The control method for an information processing device according to claim 1, characterized in that the first status information is information indicating at least one of the status of a printing device connected to the information processing device, the status of a printing process, and the status of consumables installed in a printing device connected to the information processing device.

4. 2. The method according to claim 1, wherein the first status information is information that cannot be acquired through communication according to the first protocol.

5. The control method for an information processing device according to claim 1, characterized in that in the first acquisition process, the extended application acquires the first status information by utilizing a server database as a method other than communication using the first protocol.

6. The control method for an information processing device according to claim 1, characterized in that, in the first acquisition process, the extended application acquires the first status information by using a cloud service as a method other than communication using the first protocol.

7. The control method for an information processing device according to claim 1, characterized in that in the first acquisition process, the extended application acquires the first status information by utilizing a user's selection operation on a candidate list as a method other than communication via the first protocol.

8. The control method for an information processing device as described in claim 1, characterized in that in the first acquisition process, the extended application acquires the first status information by combining at least two of a server database, a cloud service, and a user's selection operation on a candidate list as a method other than communication using the first protocol.

9. 2. The method according to claim 1, wherein the first protocol is an Internet Printing Protocol.

10. The control method for an information processing device according to claim 2, characterized in that in the first acquisition process, when the extended application is unable to communicate using a second protocol different from the first protocol, it acquires the first status information using a method other than communication using the first protocol.

11. The control method for an information processing device according to claim 10, characterized in that in the second acquisition step, the extended application acquires the second status information by communication using the first protocol when communication using the second protocol is not possible.

12. determining whether the extended application is capable of communicating according to the second protocol; 11. The method according to claim 10, wherein in the determining step, the extension application determines that communication according to the second protocol is not possible when the type of the printer driver is a first printer driver.

13. The control method for an information processing device according to claim 12, characterized in that in the determination process, the extended application determines that communication via the second protocol is not possible when the type of the printer driver is a second printer driver different from the first printer driver and the type of the communication interface with the printing device connected to the information processing device is a specified communication interface and identification information necessary for the specified communication interface for the printing device connected to the information processing device is not registered in the extended application.

14. the first protocol is the Internet Printing Protocol; 11. The method according to claim 10, wherein the second protocol is a vendor protocol that is uniquely defined by a vendor of a printing device connected to the information processing device.

15. 2. A program for causing a computer to execute each step of the method for controlling an information processing device according to claim 1.

16. An information processing apparatus having a printer driver capable of communicating with any printing device of a different model using a first protocol, and an extension application associated with the printer driver for extending a function of the printer driver, a first acquisition means for acquiring first status information of a printing device connected to the information processing device by the extension application using a method other than communication according to the first protocol; The information processing apparatus according to claim 1, further comprising: a display control unit configured to display a status information notification screen based on the first status information, the display control unit configured to display a status information notification screen based on the first status information.

Images