Information processing device, and print settings application

Abstract

To provide an information processing apparatus that prevents setting in a client terminal of a print setting in which a desired output may not be obtained from an output destination printer.SOLUTION: An information processing apparatus described in the present specification has: selection means that selects a print queue to be used from print queues registered in a server system; control means that, when a print queue is selected which receives print data transmitted by the server system not through the other server system that converts the format of the print data, displays a print setting screen on which a predetermined setting item can be set, and when a print queue is selected which receives the print data through the other server system, displays a print setting screen on which the predetermined setting item cannot be set; and transmission means that transmits, to the server system, the print data based on a print setting set through the print setting screen.SELECTED DRAWING: Figure 5

Description

Technical Field

[0004] , , , , , , , , , ,

[0001] The present invention relates to an information processing apparatus and a print setting application.

Background Art

[0002] A system for transmitting print data from a client terminal via a cloud server to a printer is known. In the above system, a user operates a printer driver installed on the client terminal to perform print settings and issue a print instruction. The printer driver installed on the client terminal transmits print data based on image data and print settings to the cloud server. The cloud server can perform printing by transmitting the received print data to the printer.

[0003] In order for a printer to receive the print data transmitted by the cloud server and execute printing, it is necessary to have a mechanism for interpreting the received print data. However, among existing printers, there are also printers that do not have a mechanism for interpreting the print data transmitted from the cloud server. Patent Document 1 discloses a cloud print system using an existing printer that cannot interpret the print data transmitted by the cloud server by using a proxy server that can interpret the print data transmitted by the cloud server. In Patent Document 1, the proxy server receives the print data from the cloud server and converts the print data into a form that can be interpreted by an existing printer. The printer receives the print data converted by the proxy server and executes printing.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] When printing via a cloud server using an existing printer that cannot interpret the print data sent by the cloud server, conversion of the print data by a proxy server is necessary. However, the print data that the proxy server receives from the cloud server may contain print settings that the proxy server cannot convert.

[0006] If a user configures a setting on their client terminal that prevents the proxy server from performing the conversion, the output may end up with settings unintended by the user.

[0007] Therefore, in view of the above problems, the present invention aims to prevent the setting of print settings on the client terminal that may result in the desired output not being obtained at the destination printer. [Means for solving the problem]

[0008] The information described herein The application is executed on an information processing device having: a selection means for selecting one printer from a plurality of printers, including the first printer registered in the server system based on a registration request sent from the first printer, and the second printer registered in the server system based on information of a second printer registered in a server different from the server included in the server system; and an acquisition means for acquiring an application for accepting value settings for print-related items based on the information of the selected printer, wherein the application includes a display step of displaying a setting object that accepts value settings for predetermined print-related items when an instruction object for displaying additional print settings is selected when the first printer is selected, and the setting object is not displayed even when the instruction object for displaying additional print settings is selected when the second printer is selected. It is characterized by the following: [Effects of the Invention]

[0009] The information processing device described in the present invention can prevent the setting of print settings on the client terminal that may result in the desired output not being obtained at the destination printer. [Brief explanation of the drawing]

[0010] [Figure 1] This figure shows an example of a system configuration in an embodiment described herein. [Figure 2] This figure shows an example of the hardware configuration of each device in the embodiments described herein. [Figure 3] This figure shows an example of the software configuration of each device in the embodiments described herein. [Figure 4]This figure shows an example of a print settings screen in the embodiments described herein. [Figure 5] This figure shows an example of an extended print settings screen in the embodiments described herein. [Figure 6] This figure shows an example of a data structure in the embodiments described herein. [Figure 7] This is a sequence diagram showing the process for registering printer information with a cloud print service in the embodiments described herein. [Figure 8] This flowchart shows the process by which a cloud print service generates a print queue in an embodiment described herein. [Figure 9] This is a sequence diagram showing the process up to executing a print using a cloud print-compatible printer in Embodiment 1 described herein. [Figure 10] This is a sequence diagram showing the process up to performing printing using a printer that does not support cloud printing, in Embodiment 1 described herein. [Figure 11] This flowchart shows the process for displaying the extended print settings screen in Embodiment 1 described herein. [Figure 12] This is a sequence diagram showing the process up to performing printing using a cloud print-compatible printer in Embodiment 2 described herein. [Figure 13] This is a sequence diagram showing the process up to performing printing using a printer that does not support cloud printing, in Embodiment 2 described herein. [Figure 14] This flowchart shows the process for displaying the extended print settings screen in Embodiment 2 described herein. [Figure 15] This flowchart shows the process for displaying the extended print settings screen in Embodiment 3 described herein. [Figure 16] This figure shows an example of the sequence for generating a print queue on a client terminal in the embodiments described herein.

Embodiments for Carrying Out the Invention

[0011] Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.

[0012] <Embodiment 1> FIG. 1 shows a configuration diagram of a printing system in cloud printing in the present embodiment. A client terminal 101, a cloud printing server 102, a cloud printing proxy server 103, a cloud printing-compatible printer 104, and a non-cloud printing-compatible printer 105 are connected via a network 106.

[0013] In FIG. 1, one client terminal 101, one cloud printing-compatible printer​​​​​​​​​​​​​​​Cloud print-compatible printer 104 and cloud print-incompatible printer 105 are devices that actually print onto physical paper. Cloud print-compatible printer 104 and cloud print-incompatible printer 105 receive print data sent by the cloud print server 102 via the network 106, convert it into image data, and print it. Cloud print-compatible printer 104 is a printer that can communicate with the cloud print server 102 using a predetermined protocol. The predetermined protocol is, for example, IPP (Internet Printing Protocol). Cloud print-incompatible printer 105 is a printer that cannot communicate using the predetermined protocol. Therefore, when printing via cloud print using cloud print-incompatible printer 105, cloud print-incompatible printer 105 communicates via the cloud print proxy server 103.

[0018] The cloud print server 102 receives print data consisting of print settings and image data from the client terminal 101, and sends the received print data to the cloud print-compatible printer 104 or the cloud print proxy server 103. The cloud print service 321 operates on the cloud print server 102.

[0019] The cloud print proxy server 103 communicates with the cloud print server 102 on behalf of the cloud print-incompatible printer 105, exchanging printer information and print data. The cloud print proxy server 103 has the cloud print proxy 331 and printer driver 332 installed.

[0020] Next, the hardware configuration of the system in this embodiment will be described using Figure 2.

[0021] Figure 2(a) is a block diagram showing the hardware configuration of the client terminal 101. The client terminal 101 includes a display unit 216, an operation unit 217, a storage unit 214, a control unit 211, and a network communication unit 215.

[0022] The memory unit 214 refers to a non-volatile storage device such as a hard disk or SSD, which is capable of storing and rewriting digital data.

[0023] The control unit 211 consists of a CPU 212 and a memory 213, and controls the overall operation of the client terminal 101. The CPU 212 loads the programs stored in the storage unit 214 into the memory 213 and executes them. The memory 213 is the main memory of the CPU 212 and is used as a work area and a temporary storage area for loading various programs.

[0024] The network communication unit 215 is a device that communicates with the external network 106 and performs input and output of digital data with external servers, client terminals, etc. via the network 106.

[0025] The display unit 216 is a device for displaying visual information to the user, such as a liquid crystal display.

[0026] The control unit 217 is a device for receiving input from the user via a keyboard, mouse, or the like. Sometimes, a device that combines the functions of both the display unit 216 and the control unit 217, such as a touch panel, is used.

[0027] Figure 2(b) is a block diagram showing the hardware configuration of the cloud print server 102. The cloud print server 102 comprises a storage unit 224, a control unit 221, and a network communication unit 225. The explanation of the storage unit 224, control unit 221, and network communication unit 225 is the same as that of the client terminal 101, so it is omitted here. In Figure 2(b), one of each is shown for the storage unit 224, control unit 221, and network communication unit 225, but a configuration with one or more of each is also possible.

[0028] Figure 2(c) is a block diagram showing the hardware configuration of the cloud print proxy server 103. The cloud print proxy server 103 includes a display unit 236, an operation unit 237, a storage unit 234, a control unit 231, and a network communication unit 235. The descriptions of the display unit 236, operation unit 237, storage unit 234, control unit 231, and network communication unit 235 are the same as those for the client terminal 101 and are therefore omitted. In Figure 2(c), one display unit 236, one operation unit 237, one storage unit 234, one control unit 231, and one network communication unit 235 are shown, but there may be one or more of each.

[0029] Figure 2(d) is a block diagram showing the hardware configuration of the cloud print-compatible printer 104. The cloud print-compatible printer 104 includes a display unit 246, an operation unit 247, a storage unit 244, a control unit 241, a network communication unit 245, and a printing unit 248.

[0030] The display unit 246 is a device that displays information to the user in real time, such as a touch panel or LEDs, which are installed in the cloud print-compatible printer 104.

[0031] The operation unit 247 is a device for receiving input from the user and may include a touch panel as well as hard keys such as a numeric keypad. The storage unit 244 and control unit 241 are equivalent to those of the client terminal 101, so their explanation will be omitted. Note that the storage unit 244 and control unit 241 may each be configured as one or more units.

[0032] The network communication unit 245 is a device that communicates with the external network 106, and its main roles are to receive print data and to send information about the status of the cloud print-compatible printer 104, such as errors, to external servers, etc.

[0033] The printing unit 248 is a device that performs a series of operations including paper feeding, printing, and paper ejection on paper prepared in a cassette or tray. The printing method is not particularly limited and can be electrophotographic or inkjet. Finishing devices such as a duplex unit, stapling, and punching used during paper ejection are also included in the printing unit 248.

[0034] In this embodiment, a single-function printer that only performs printing is described as an example of a cloud print-compatible printer 104, but a multi-function printer (all-in-one device) that also has scanning and faxing functions may also be used.

[0035] Figure 2(e) is a block diagram showing the hardware configuration of the cloud print-incompatible printer 105. The cloud print-incompatible printer 105 includes a display unit 256, an operation unit 257, a storage unit 254, a control unit 251, a network communication unit 255, and a printing unit 258.

[0036] The descriptions of the display unit 256, operation unit 257, storage unit 254, control unit 251, network communication unit 255, and printing unit 258 are the same as those for the cloud print-compatible printer 104 and are therefore omitted.

[0037] Next, the software configuration of the system in this embodiment will be described using Figure 3.

[0038] Figure 3(a) is a block diagram showing the software configuration of client terminal 101.

[0039] The client terminal 101 has a cloud print driver 311 and a print settings extension application 312. The cloud print driver 311 is software for generating print data to send to the cloud print server 102. The print settings extension application 312 is an application for extending the functionality of the cloud print driver 311 and performs processes such as controlling the display of the print settings screen. The cloud print driver 311 is downloaded by the user from the website provided by the cloud print service 321 and installed on the client terminal 101. The timing of the download and installation of the print settings extension application 312 on the client terminal 101 will be described later in Figure 16.

[0040] The cloud print driver 311 further has the following software configuration:

[0041] The Cloud Print Service I / F 31101 handles the exchange of data and commands with the Cloud Print Service 321.

[0042] The print job management unit 31102 performs processes such as generating and sending print jobs. The print job management unit 31102 generates print data in accordance with the protocol supported by the cloud print service 321 and sends this print data as a print job. For example, if the cloud print service sends and receives print data in accordance with IPP, the print settings will be set to generate print data in accordance with IPP. In addition, the file format of the image data included in the print data will also be in accordance with the file format supported by the cloud print service (for example, PDF or PWG-Raster) when generating the print data.

[0043] The UI unit 31103 is responsible for displaying the UI provided by the cloud print driver 311 and for receiving user operations from the client terminal 101. The UI unit 31103 displays the print settings screen 1300 shown in Figure 4(a). The print settings screen 1300 contains objects for performing printing using the cloud print service 321. Area 1301 in Figure 4(a) displays information about the print queues registered with the cloud print server 102. Button 1302 is a button for displaying a list of print queues registered with the cloud print server 102. The user selects button 1302 and then selects the print queue corresponding to the printer to be used for printing from the displayed print queues. Area 1303 is for setting the number of copies to print. Area 1304 is for setting the color mode. Button 1305 is a button for changing the color mode, and after selecting button 1305, the user can select the color mode for printing. The advanced settings button 1306 is a button for launching the print settings extension application 312. The print button 1307 is a button for sending a print command to the cloud print server 102. When the user selects the print button 1307, the print job management unit 31102 generates a print job. The generated print job is sent to the cloud print service 321 via the cloud print service interface 31101.

[0044] In this embodiment, the cloud print driver 311 is described as having a UI unit 31103 that displays the print settings screen 1300. However, the OS of the client terminal 101 or an application installed on the client terminal 101 may have a UI unit that displays the print settings screen 1300. In such a case, area 1301 will display print queues that the client terminal 101 can directly send print data to, in addition to the print queues registered with the cloud print server 102. When a print queue that the client terminal 101 can directly send print data to is selected, the client terminal 101 generates print data using the printer driver corresponding to the selected print queue. The generated print data is sent to the printer without going through the cloud print server 102.

[0045] The print settings extension application I / F31104 handles the exchange of data and commands with the print settings extension application 312.

[0046] The print settings extension application 312 further has the following software configuration:

[0047] The Cloud Print Service I / F 31201 handles the exchange of data and commands with the Cloud Print Service 321. The Cloud Print Service I / F 31201 obtains printer information and print settings configured on the print settings screen 1300 from the print extension application I / F 31104 of the Cloud Print Driver 311. The Cloud Print Service I / F 31201 also has the role of passing the print settings configured in the print settings extension application 312 to the Cloud Print Driver 311.

[0048] The information acquisition unit 31202 acquires information such as print queue information from the cloud print service 321.

[0049] The connection type determination unit 31203 determines whether the printer corresponding to the print queue used for printing is a printer directly connected to the cloud print service 321 or a printer connected via the cloud print proxy 331. The connection type determination unit 31203 obtains the print queue information selected in area 1301 from the cloud print driver 311 and makes a determination based on that information.

[0050] The extended print settings unit 31204 manages print settings, including printer vendor-specific print settings that are not supported by the cloud print driver 311.

[0051] The extended application UI unit 31205 is responsible for displaying the UI provided by the print settings extended application and for receiving user operations from the client terminal 101. Figure 5(a) shows an example of the print settings UI displayed by the extended application UI unit 31205 of the print settings extended application 312. The extended print settings screen 801 is displayed when the user selects the detailed settings button 1306 on the print settings screen 1300. The extended print settings screen 801 allows the user to set print settings that cannot be set on the print settings screen 1300. For example, 802 is an area for setting whether or not to punch holes in the paper to be output. When the user selects 802, the punch setting is toggled on or off. Off means that no punch holes will be punched in the paper, and On means that punch holes will be punched in the paper. Secure Print 803 is a function that starts printing when the password set in the print settings extended application 312 is entered into the printer. Area 804 is an area for entering the password required when printing using the secure print function. After the user issues a print command, the printer will start printing when the same password entered in area 804 is entered into the printer. In addition to the above settings, the extended print settings screen 801 has areas for setting the output paper size, whether or not to perform double-sided printing, and settings related to the stamp function that adds a predetermined image to the paper during printing. When the user selects the "OK" button, the extended print settings screen 801 is closed and the print settings screen 1300 is displayed.

[0052] In this embodiment, the extended print settings screen 801 displays only the settings that cannot be set on the print settings screen 1300. Alternatively, the extended print settings screen 801 could also display the settings that can be set on the print settings screen, allowing users to change the settings for those items.

[0053] The print job management unit 31206 performs processes such as generating print jobs, editing print jobs generated by the cloud print driver 311, and sending print jobs. The print job management unit 31206 of the print settings extension application 312 can edit print jobs generated by the print job management unit 31102 of the cloud print driver 311.

[0054] Figure 3(b) is a block diagram showing the software configuration of the cloud print service 321 running on the cloud print server 102.

[0055] The Account Management Unit 32101 manages the authentication of tenants and users registered with the Cloud Print Service 321. A tenant is a group to which one or more users belong. The Account Management Unit 32101 manages each user by associating their user ID with information such as the password required for authentication. Furthermore, the Account Management Unit 32101 manages the correspondence between user IDs and the tenant IDs to which the users belong.

[0056] The device management unit 32102 manages information about printers registered with the cloud print service 321. Device information is registered with the device management unit 32102 upon registration request from the printer. Figure 6(a) shows an example of device information registered with the device management unit 32102. The device ID is identification information that identifies the printer, such as the HWID (Hardware Identification Information) used to identify the printer's hardware configuration. The tenant ID is identification information for the tenant that can use the device. The printer name is the name of the device notified by the printer. The equipment configuration information is the printer's configuration information, such as whether a finisher for post-processing such as stapling or punching is connected to the printer, or whether a unit for double-sided printing is connected. The capability information indicates the functions that the printer can perform. Capability information includes information such as whether it can print in color, whether it can print double-sided, information on the locations where stapling is possible, information on the punch holes that can be used, and whether the secure print function can be used.

[0057] The print management unit 32103 is responsible for determining whether to allow or deny print job transfer requests from the cloud print-compatible printer 104 and the cloud print proxy server 103, as well as managing the transfer of print jobs.

[0058] The print queue management unit 32104 receives print jobs from external sources and stores the received print jobs in an area provided within the storage unit 224 of the cloud print server 102. The print queue management unit 32104 manages the print queue information shown in Figure 6(d). The print queue information includes the print queue name, device configuration information, capability information, connection type information, and tenant ID. The print queue name is the name of the print queue and is the name displayed on the print settings screen 1300. The device configuration information and capability information are the same as the device information in Figure 6(a). The connection type information indicates whether the print queue is a queue that sends print data to the printer without going through the cloud print proxy server 103, or a queue that sends print data to the cloud print proxy server 103. The tenant ID is identification information for tenants that can use the print queue. The device information shown in Figure 6(a) and the print queue information shown in Figure 6(d) are linked using the tenant ID as the key. The device ID is the same as the device ID in Figure 6(a) and is information for identifying the printer associated with the print queue. For example, the HWID, which identifies the printer's hardware, is registered as the device ID.

[0059] Figure 3(c) is a block diagram showing the software configuration of the cloud print proxy server 103. The cloud print proxy server 103 includes a cloud print proxy 331 and a printer driver 332.

[0060] Cloud Print Proxy 331 further has the following software configuration:

[0061] The Cloud Print Service I / F 33101 handles the exchange of data and commands between it and the Cloud Print Service 321.

[0062] The print data conversion unit 33102 performs data conversion between the cloud print service 321 and the printer driver 332 as needed.

[0063] The printer driver interface 33103 handles the exchange of data and commands between it and the printer driver 332.

[0064] Furthermore, the printer driver 332 has the following software configuration.

[0065] The print management unit 33201 converts the print data, including print settings and drawing data, received from the cloud print proxy 331 into a PDL (Page Description Language) format that the printer can process, and sends it to the printer.

[0066] Device I / F33202 handles the exchange of data and commands between the printer driver 332 and the cloud print-incompatible printer 105.

[0067] Furthermore, the print management unit 33201 manages the capability information of the cloud print-incompatible printer 105 associated with the printer driver 332. The capability information managed by the print management unit 33201 is converted into mutual exchange information that can be interpreted by the cloud print server 102 by the print data conversion unit 33102 of the cloud print proxy 331, and notified to the cloud print server 102. Figure 6(b) shows an example of mutual exchange information generated by the print data conversion unit 33102. The mutual exchange information includes the proxy ID, print queue name, device configuration information, and capability information. The proxy ID is the identification information of the cloud print proxy 331. The print queue name is the name of the print queue associated with the printer driver 332 on the cloud print proxy server 103. The device configuration information is the configuration information of the cloud print-incompatible printer 105 associated with the printer driver 332. The capability information is the capability information of the cloud print-incompatible printer 105 associated with the printer driver 332. As described above, when using the cloud print proxy server 103, the cloud print server 102 is notified of the proxy ID instead of the device ID.

[0068] The mutual exchange information shown in Figure 6(c) is an example of print data notified from the cloud print server 102 to the print data conversion unit 33102. This mutual exchange information includes print settings 1211 and drawing data 1212. The print data conversion unit 33102 converts the mutual exchange information shown in Figure 6(c) into a format that can be handled by the printer driver 332 and passes it to the printer driver 332.

[0069] Figure 3(d) is a block diagram showing the software configuration of the device control unit 341 of the cloud print-compatible printer 104.

[0070] The print data receiving unit 34101 receives print data transmitted from an external source via the network 106 and stores it in the storage unit 244 of the cloud print-compatible printer 104. The print data receiving unit 34101 can process print data in a predetermined protocol that can be generated by the cloud print server 102.

[0071] The device management unit 34102 manages options, capability information, paper levels, ink / toner levels, etc., connected to the cloud print-compatible printer 104. The device management unit 34102 can generate capability information that can be interpreted by the cloud print server 102.

[0072] The print output unit 34103 controls printing onto the paper.

[0073] The UI control unit 34104 displays the UI on the control unit 247 of the cloud print-compatible printer 104 and acquires instructions and information entered via the UI.

[0074] The Cloud Print Service I / F 34105 handles the exchange of data and commands between it and the Cloud Print Service 321.

[0075] Figure 3(e) is a block diagram showing the software configuration of the device control unit 351 of the cloud print-incompatible printer 105.

[0076] The print data receiving unit 35101 receives print data from the device I / F 33202 of the printer driver 332. The print data receiving unit 35101 does not support the format of the print data sent by the cloud print server 102 and is therefore unable to interpret the print data. In this embodiment, the printer driver of the cloud print proxy server 103 converts the print data sent by the cloud print server 102 into a format that the print data receiving unit 35101 can process. In this way, printing via the cloud print server 102 is achieved using a cloud print-incompatible printer 105.

[0077] The device management unit 35102 manages the capacity information, paper level, and ink / toner level of the cloud print-incompatible printer 105. The device management unit 35102 manages the above information in a different format than the cloud print server 102. Therefore, conversion by the cloud print proxy server 103 is required in order to notify the cloud print server 102 of the capacity information of the cloud print-incompatible printer 105.

[0078] The descriptions of the print output unit 35103 and the UI operation unit 35104 are the same as those for the cloud print-compatible printer 104, so they are omitted here.

[0079] Next, using Figure 7(b), an example of the user procedure for registering the cloud print-compatible printer 104 with the cloud print service 321 in this embodiment, as well as an example of the sequence between each software and service, will be described below.

[0080] First, the user instructs the cloud print-compatible printer 104 to register the printer from its control panel 247 (s921).

[0081] Next, the cloud print-compatible printer 104 displays a login UI for the cloud print service 321 on the control panel 247 (s922).

[0082] Next, the user enters their login information into the login UI (s923). This login information includes the user ID and password.

[0083] Next, the cloud print-compatible printer 104 sends the entered login information and authentication request to the cloud print service 321 (s924).

[0084] Next, the cloud print service 321 performs authentication based on the login information received along with the authentication request (s925). If authentication is successful, the cloud print service 321 issues an access token and sends it to the cloud print-compatible printer 104 (s926). This token is used when the cloud print-compatible printer 104 accesses the cloud print service 321 in the future. If authentication fails in s925, the sequence ends as shown in Figure 7(b).

[0085] Next, the cloud print-compatible printer 104 sends a printer registration request to the cloud print service 321 along with the received token and printer information (s927).

[0086] Cloud Print Service 321 performs printer registration (s928). Details of the printer registration process performed in s928 will be described later.

[0087] Next, the cloud print service 321 returns a registration completion status to the cloud print-compatible printer 104 after the printer registration process (s929). The cloud print-compatible printer 104 then displays the registration completion status on the control panel 247 (s930).

[0088] Next, using Figure 7(a), an example of the user procedure for registering a cloud print-incompatible printer to the cloud print service in this embodiment, as well as an example of the sequence between each software and service, will be explained. It is assumed that the cloud print proxy server 103 has the printer driver 332 installed and that a print queue corresponding to the cloud print-incompatible printer 105 has been generated. When generating the printer queue, the printer driver 332 communicates with the cloud print-incompatible printer 105 and obtains the printer's hardware ID, model name, equipment configuration information, and capability information.

[0089] First, the user selects the printer driver 332 for the cloud print-incompatible printer 105 to connect to the cloud print proxy 331 (s901).

[0090] Next, the cloud print proxy 331 requests printer information from the selected printer driver 332 (s902). Printer information includes the printer's hardware ID, model name, device configuration information, and configurable capabilities.

[0091] Next, the printer driver 332 returns printer information to the cloud print proxy 331 (s903).

[0092] Here, we will explain how to obtain the HWID of the printer, which is one of the printer information in this embodiment. The cloud print proxy 331 calls the Win32 API function OpenPrinter() to obtain the printer handle of the printer driver 332 selected in s901. Next, using the obtained printer handle of the printer driver 332, it calls the GetPrinterDriver() function to obtain DRIVER_INFO_6. The structure DRIVER_INFO_6 is generated when a print queue is created on the cloud print proxy server 103. The structure DRIVER_INFO_6 is data that contains information about the printer driver, specifically information associated with the printer driver such as the printer driver name and the printer driver installation path. This DRIVER_INFO_6 has a value called pszHardwareID, which stores the HWID of the printer driver. The cloud print proxy 331 can obtain the HWID of the printer driver 332 by obtaining the HWID stored in DRIVER_INFO_6.

[0093] In this example, the printer's hardware ID was obtained using the Win32 API, but any method that can obtain the hardware ID is acceptable.

[0094] Next, the cloud print proxy 331 stores the received printer information in association with the printer driver 332 (s904).

[0095] Next, the cloud print proxy 331 enables the printer registration button on the UI, indicating that printer registration is enabled (s905).

[0096] Next, the user presses the printer registration button to initiate printer registration. (s906)

[0097] Next, the cloud print proxy 331 displays the cloud print service 321 login UI on the UI (s907).

[0098] Next, the user enters their login information into the login UI (s908).

[0099] Next, the cloud print proxy 331 sends an authentication request to the cloud print service 321 along with the entered login information (s909).

[0100] Next, the cloud print service 321 performs authentication (s910). If authentication is successful, the cloud print service 321 issues an access token and sends it back to the cloud print proxy 331 (s911). If authentication fails, the process described in Figure 7(a) is terminated.

[0101] Next, the cloud print proxy 331 converts the stored printer information data format into a format that the cloud print service 321 can handle (s912). The format that the cloud print service 321 can handle is, for example, a format compliant with IPP.

[0102] Then, the cloud print proxy 331 sends a printer registration request to the cloud print service 321 along with the received token and the converted printer information (s913).

[0103] Next, the cloud print service 321 performs the printer registration process (s914). Details of the printer registration process will be described later.

[0104] Next, after the printer registration process is complete, the cloud print service 321 sends a registration completion status to the cloud print proxy 331 (s915).

[0105] Then, CloudPrint Proxy 331 displays the registration completion status on the UI (s916).

[0106] Figure 8(a) is a flowchart showing an example of the printer registration process performed by the cloud print service 321 in s914 in Figure 7(a) and s928 in Figure 7(b).

[0107] The process shown in Figure 8(a) is achieved when the program for the cloud print service 321, stored in the memory 224 of the cloud print server 102, is loaded into memory 223 and executed by the CPU 222.

[0108] The process described in Figure 8(a) is initiated when the cloud print service 321 receives a printer registration request from an external source via the network 106.

[0109] First, the device management unit 32102 of the cloud print service 321 receives a printer registration request (s401). The printer registration request includes device information as shown in Figure 6(g) or mutual exchange information as shown in Figure 6(b). Based on the received device information or mutual exchange information and the tenant ID corresponding to the logged-in user, the device management unit 32102 generates the device information shown in Figure 6(a).

[0110] The print queue management unit 32104 generates a print queue based on the generated device information (s402).

[0111] Next, the print queue management unit 32104 generates the print queue information shown in Figure 6(d) (s403). If the information received along with the registration request is the device information shown in Figure 6(g), the printer name is set as the print queue name. If the information received along with the registration request is the mutual exchange information shown in Figure 6(b), the print queue name in the mutual exchange information is used as the generated print queue name.

[0112] The print queue management unit 32104 determines whether the received registration request is a registration request from a cloud print-compatible printer (s404). In s404, the print queue management unit 32104 determines that the registration request is from a cloud print-compatible printer 104 if the information received with the registration request includes a device ID. On the other hand, the print queue management unit 32104 determines that the registration request is from a non-cloud print-compatible printer 105 if the information received with the registration request does not include a device ID. The determination in s404 may also be based on whether the information received with the registration request includes a proxy ID. Whether the received device ID is the device ID of the cloud print-compatible printer 104 or the proxy ID of the cloud print proxy server 103 is determined based on the string contained in the received device ID. If the received device ID contains a specific string, it is determined that the device ID is the proxy ID of the cloud print proxy server 103. On the other hand, if the received device ID does not contain a specific string, it is determined that it is the device ID of the cloud print-compatible printer 104. Furthermore, the determination in s404 only needs to be able to determine whether the printer that sent the registration request is a cloud print-compatible printer or a cloud print-incompatible printer connected via a proxy server, and is not limited to the method described above.

[0113] If the received registration request is a registration request sent by the cloud print-compatible printer 104, the print queue management unit 32104 sets information indicating that the connection type is "direct printer connection" in the print queue information (s405).

[0114] On the other hand, if the received registration request is a registration request sent by a printer 105 that does not support cloud printing, information indicating that the printer connection type is "connection via cloud print proxy" is set in the print queue information (s406). After the above processing, the cloud print service 321 terminates the printer registration process shown in Figure 8(a).

[0115] The above outlines the procedure and process for registering printer information with the Cloud Print Service 321.

[0116] After the above process, the user performs the process of generating a print queue on the client terminal 101 to submit a print job using the cloud print service 321. Here, the process of generating a print queue on the client terminal 101 will be explained using Figure 16.

[0117] The sequence shown in Figure 16 is initiated when the user operates the client terminal 101 and instructs the cloud print service 321 to search for registered printers.

[0118] When client terminal 101 receives a printer search command from cloud print service 321, it sends an authentication request to cloud print service 321 (s1604). In s1604, client terminal 101 first sends a user ID and password, or an access token to cloud print service 321, to cloud print service 321. Cloud print service 321 authenticates the user based on the information received from client terminal 101. Then, cloud print service 321 sends the authentication result to client terminal 101 (s1605). If the received authentication result is successful, client terminal 101 executes the following process. If the received authentication result is unsuccessful, client terminal 101 does not execute the following process and terminates the sequence shown in Figure 16.

[0119] The client terminal 101 sends a request to the cloud print service 321 to retrieve the print queue list (s1606). The cloud print service 321 identifies the tenant ID of the tenant to which the logged-in user belongs, based on the user ID of the user. The cloud print service 321 then identifies the device information registered in association with the identified tenant ID. The cloud print service 321 then compiles a list of printer names from the identified device information and sends it to the client terminal 101 as a print queue list (s1607).

[0120] The client terminal 101 displays a list of print queues received from the cloud print service 321 on the display unit 216. Note that when displaying the list of print queues, print queues for printers for which print jobs have already been created to send print jobs to the client terminal 101 via the cloud print service may be omitted.

[0121] The client terminal 101 then accepts the user's selection of a print queue corresponding to the print queue generated by the client terminal 101. The client terminal 101 sends a request to the cloud print service 321 to retrieve information about the selected print queue (s1608). The cloud print service 321 receives the request to retrieve print queue information and sends the print queue information of the print queue selected by the user to the client terminal 101 (s1609). The print queue information sent here is as shown in Figure 6(d). The capability information includes the functions that can be used by the printer associated with the print queue, as well as the printer's HWID.

[0122] Based on the received print queue information, the client terminal 101 generates a print queue within the client terminal 101 for sending print jobs via the cloud print service 321 (s1610).

[0123] Then, the client terminal 101 sends a request to a printer driver distribution service (not shown) to obtain printer usage information corresponding to the generated print queue (s1611). In s1611, the client terminal 101 sends the HWID included in the capability information of the printer queue information obtained from the cloud print service 321 to the printer driver distribution service in order to obtain additional information.

[0124] The printer driver distribution service is a service provided by a server system that can be accessed by a client terminal 101 via the network 106. This server system consists of one or more information processing devices having a hardware configuration similar to the cloud print server shown in Figure 2(b). The printer driver distribution service stores files containing information about printer drivers and applications for extending printer drivers. These files, for example, contain identification information for a print settings extension application used to extend the print settings screen. The printer driver distribution service stores the printer drivers and these files in association with the printer's HWID.

[0125] The printer driver distribution service identifies the file corresponding to the HWID received from client terminal 101 and sends it to the client terminal as additional information (s1612). The client terminal 101 sends a request to an application distribution service (not shown) to obtain a print settings extension application identified by the application identification information described in the received additional information file (s1613).

[0126] The application distribution service is a service provided by a server system that can be accessed by the client terminal 101 via the network 106. This server system consists of one or more information processing devices having a hardware configuration similar to the cloud print server shown in Figure 2(b). The application distribution service stores applications in association with their identification information.

[0127] The application distribution service sends the application identified by the application identification information received from the client terminal 101 to the client terminal 101 (s1614).

[0128] The client terminal 101 stores the received application in association with the print queue that generated it (s1615). This allows the application corresponding to the selected print queue to be launched when calling the print settings extension application from the print settings screen.

[0129] As shown in Figure 16, by obtaining the HWID of the printer associated with the print queue generated by the client terminal 101, it becomes possible to add and expand the information of the generated print queue from an external server.

[0130] Figure 9 is a diagram showing an example sequence of processes related to print settings and printing in this embodiment. Figure 9 shows the sequence when using a cloud print-compatible printer 104.

[0131] The user issues a command to display the print settings screen within the application (s1000). The cloud print driver 311 receives the command to display the print settings screen via the application.

[0132] The cloud print driver 311 displays the print settings screen 1300 (s1001). The print settings screen shown in Figure 4(a) is displayed.

[0133] The user operates area 1301 of the print settings screen 1300 to select the print queue corresponding to the printer to be used for printing (s1002).

[0134] The cloud print driver 311 refers to the information of the selected print queue and updates the print settings screen 1300 (s1003). Here, the cloud print driver 311 updates the print settings screen based on the print queue information obtained in the sequence shown in Figure 16. The information used to update the print settings screen includes, for example, capability information, the name of the print queue, and the HWID. Suppose that the printer associated with the selected print queue is a printer capable of both color and monochrome printing. In this case, the cloud print driver 311 displays a print settings screen in area 1304 of Figure 4(a) where the user can select either color or monochrome. On the other hand, suppose that the printer associated with the selected print queue is a monochrome printer. In this case, the cloud print driver 311 displays a print settings screen in area 1304 of Figure 4(a) where only monochrome printing is selectable.

[0135] The user operates the print settings screen 1300 to instruct the launch of the print settings extension application 312 (s1004). When the user selects the advanced settings button 1306 on the print settings screen 1300, the cloud print driver 311 launches the print settings extension application 312 associated with the selected print queue (s1005).

[0136] Next, the print settings extension application 312 performs the startup process (s1006).

[0137] Next, the print settings extension application 312 sends a request to the cloud print service 321 to acquire print queue information (s1007). The cloud print service 321 sends the print queue information corresponding to the acquisition request received from the print settings extension application 312 (Figure 6(d)) back to the print settings extension application 312 (s1008). The print settings extension application 312 refers to the connection type information of the received print queue information and determines whether the printer corresponding to the selected print queue is a printer that goes via the cloud printer proxy server (s1009). Based on this determination, the print settings extension application 312 displays the extended print settings screen (s1010). In Figure 9, since information indicating that the printer is directly connected has been added to the print queue information in s1009, the print settings extension application 312 displays the UI shown in Figure 5(a).

[0138] The user operates the print settings extension application 312 to configure the print settings and selects the "OK" button (s1011). The print settings extension application 312 executes a process to terminate the application (s1012). Then, the print settings extension application 312 sends the print settings configured on the extended print settings screen shown in Figure 5(a) to the cloud print driver 311 (s1013). The cloud print driver 311 displays the print settings screen shown in Figure 4 again. The user operates the print settings screen 1300 and selects the print button (s1014). Based on the print settings configured on the print settings screen 1300 and the print settings received from the print settings extension application 312 in s1013, the cloud print driver 311 generates print data and sends it to the cloud print service 321 (s1015). In s1015, the cloud print driver 311 generates print data based on the print settings described in accordance with IPP and image data in a predetermined format such as PDF or PWG-Raster. The cloud print driver 311 then sends the data to the cloud print service 321. The cloud print service 321 stores the received print data in association with the specified print queue.

[0139] The cloud print-compatible printer 104 sends a request to the cloud print service 321 to retrieve print data (s1016). This request may be sent by a polling process at regular intervals, or it may be triggered when a user logs in to the cloud print-compatible printer 104.

[0140] The cloud print service 321 sends the print data stored in the print queue to the cloud print-compatible printer 104 (s1017). The cloud print-compatible printer 104 prints the image based on the received print data (s1018). The cloud print-compatible printer 104 then notifies the cloud print service 321 that printing is complete (s1019).

[0141] The above is the sequence from print settings to the execution of printing on the cloud print-compatible printer 104. In Figure 9, print queue information was obtained and the connection type was determined in steps s1007 and s1008. Alternatively, the connection type could be determined based on the print queue information obtained in the process of generating a print queue on the client terminal 101 (Figure 16). In this case, steps S1007 to s1009 may be omitted.

[0142] Next, Figure 10 will be used to explain the printing sequence using the cloud print-incompatible printer 105. Note that for parts of Figure 10 that perform the same processing as in Figure 9, the same reference numerals as in Figure 9 are used, and the explanation is omitted.

[0143] Since steps S1000 to S1009 are the same as in Figure 9, their explanation will be omitted.

[0144] If the print queue information includes information indicating that the connection is via a cloud print proxy, the print settings extension application 312 displays the screen shown in Figure 5(b) (s1400). Figure 5(b) shows an example of the print settings UI of the print settings extension application 312. The extended print settings screen 811 displays a warning dialog 812 regarding the add-on finisher. For cloud print-incompatible printers 105, even if the printer's device configuration information is changed via the cloud print proxy server, this change may not be reflected in the print queue information of the cloud print service 321. Therefore, a warning dialog 812 is displayed to prompt the user to re-register the printer if the device configuration of the cloud print-incompatible printer 105 is changed.

[0145] Figure 5(c) shows the extended print settings screen 821, which appears after closing the dialog box in Figure 5(b). In the extended print settings screen 821, punch settings and secure print settings cannot be configured. The punch settings are not displayed because the device configuration information for the non-cloud print compatible printer 105 does not include information on a punchable finisher. The secure print password included in the print data generated by the cloud print driver 311 may not be converted to a format usable by the non-cloud print compatible printer. Therefore, in Figure 5(c), the secure print setting is hidden and cannot be configured. Thus, Figure 5(c) displays an extended print settings screen where certain settings that can be configured in Figure 5(a) cannot be configured, regardless of the printer's capabilities or configuration information. This prevents the output from being set to settings unintended by the user when printing using a non-cloud print compatible printer via the cloud print service 321. Items that can be configured if the printer is a cloud print compatible printer but cannot be configured if it is a non-cloud print compatible printer include blank paper saving, toner saving, stapleless binding, and print area settings. Blank page saving is a function that skips blank pages when printing image data. Toner saving is a setting to save the amount of toner used for printing. Stapleless binding is a function that binds printed papers without using staples. Print area setting is a function that sets the area of ​​the paper on which printing will take place.

[0146] When conversion of print data is required on the cloud print proxy server, the print settings extension application 312 displays an extended print settings screen that prevents the setting items that may not be convertible on the cloud print proxy server from being set. In this embodiment, by doing so, it is possible to suppress the setting of print settings that cannot be converted on the cloud print proxy server when printing is performed via the server.

[0147] Figure 5(d) shows another example of the extended print settings screen displayed by the print settings extension application 312 when a print queue that prints via a cloud print proxy server is selected. Here, the extended print settings screen 831 is displayed after closing the warning dialog regarding the add-on finisher. As described in area 822, secure print settings can be configured on the extended print settings screen 831. However, a warning message 823 is displayed stating that operation is not guaranteed when using the secure print function.

[0148] The processes described in S1011 to S1015 are the same as those shown in Figure 9.

[0149] The cloud print proxy 331 periodically sends requests to the cloud print service 321 to retrieve print data (s1401).

[0150] The cloud print service 321 refers to the print queue information and determines whether the source of the data acquisition request is the cloud print-compatible printer 104 or the cloud print proxy 331. If it determines that the source of the print data acquisition request is the cloud print proxy 331, the cloud print service 321 performs a conversion process for the print data (s1402). For example, the cloud print service converts print settings written according to IPP into a Print Ticket and converts PDF image data into XPS data.

[0151] Then, the cloud print service 321 sends the print data obtained by the conversion in s1402 to the cloud print proxy 331 (s1403). In this embodiment, the cloud print service 321 converts the format of the print data into a format that the printer driver 332 can handle. The above conversion may also be performed by the cloud print proxy 331. In that case, the cloud print service 321 sends the print data to the cloud print proxy 331 without performing the processing in s1402. The cloud print proxy 331 performs the processing equivalent to s1402 on the received print data.

[0152] The cloud print proxy 331 sends the received print data to the printer driver 332 (s1404).

[0153] The printer driver 332 performs a conversion process (s1405) to convert the received print data into drawing data that can be processed by the cloud print-incompatible printer 105. In s1405, the printer driver 332 generates PDL (Page Description Page) data based on the Print Ticket and XPS format data received from the cloud print proxy 331.

[0154] The printer driver 332 sends the generated drawing data to the cloud print-incompatible printer 105 (s1406).

[0155] Printer 105, which does not support cloud printing, performs printing based on the received drawing data (s1407).

[0156] In Figures 9 and 10, at s1007, a request to obtain print queue information is sent to the cloud print service, and the connection type is determined based on the print queue information obtained from the cloud print service. Alternatively, at the timing of s1003, the cloud print driver may obtain print queue information from the cloud print server, and at s1005, the obtained print queue information may be passed to the print extension application. In this case, the print settings extension application will perform connection type determination processing based on the connection type information of the print queue information obtained from the cloud print driver.

[0157] Next, using Figure 11, the details of the connection determination process described in Figures 9 and 10, s1009, will be explained. The process described in Figure 11 is realized when the CPU 212 of the client terminal 101 executes a program stored in memory 213 or storage unit 214.

[0158] The flow shown in Figure 11 is initiated when the print settings extension application 312 obtains print queue information from the cloud print service 321.

[0159] First, when the print settings extension application 312 obtains print queue information, it extracts information about the printer connection configuration set during printer registration from the print queue information (s501).

[0160] Next, the print settings extension application 312 determines whether the printer connection type is "direct printer connection" (s502).

[0161] If the result of the judgment is YES, the print settings extension application 312 displays the extended print settings screen 801 shown in Figure 5(a).

[0162] If the result of the judgment is NO, the print settings extension application 312 displays the extended print settings screen 811 shown in Figure 5(b) (s504). Then, the print settings extension application 312 determines whether the "OK" button in Figure 5(b) has been selected or not (s505). If the "OK" button has not been selected, the print settings extension application 312 repeats the process described in s505. If the "OK" button has been selected, the print settings extension application 312 displays the extended print settings screen 831 shown in Figure 5(c) (s506).

[0163] Furthermore, if the "OK" button is selected in Figure 5(b), and the extended print settings screen shown in Figure 5(d) is displayed, the print settings extension application 312 will display Figure 5(d) instead of Figure 5(c) in s506.

[0164] In this way, s502 performs a process to detect information indicating that the selected print queue is a queue for a cloud print-compatible printer that receives print data from the cloud print service without going through the cloud print proxy server. If this information is detected during this process, the screen shown in Figure 5(a), where a secure print password can be set, is displayed. On the other hand, if this information is not detected during the above detection process, Figure 5(c), where a secure print password cannot be set, is displayed. This prevents users from setting print settings that may not be converted correctly when the print data is converted, among the print settings that can be included in the print data generated by the cloud print driver.

[0165] As described above, the print settings extension application 312 can prevent print settings that may not be reflected in the output from being set by changing the content displayed on the UI according to the result of determining the connection type between the cloud print service 321 and the printer.

[0166] <Embodiment 2> Embodiment 1 describes an example of a method in which, when a printer is registered, the cloud print service 321 determines the printer connection type, adds the connection type information to the print queue information, and the print setting extension application 312 uses that connection type information to change the UI.

[0167] In this embodiment, when the print settings extension application 312 requests print queue information, the cloud print service 321 obtains ID information from the printer, and the print settings extension application 312 uses that ID information to determine the connection status.

[0168] Here, only the differences from Embodiment 1 will be explained.

[0169] In Embodiment 2, the process described in Figure 8(b) is performed instead of Figure 8(a) in Embodiment 1.

[0170] The process described in Figure 8(b) is achieved when the program for the cloud print service 321, stored in the memory 224 of the cloud print server 102, is loaded into memory 223 and executed by the CPU 222.

[0171] The device management unit 32102 receives a printer registration request (s411). The printer registration request includes the device information shown in Figure 6(g). In Embodiment 2, whether the printer to be registered is a cloud print-compatible printer 104 or a cloud print-incompatible printer 105, the device ID stores information that identifies the printer.

[0172] The print queue management unit 32104 generates a print queue (s412). Then, the print queue management unit 32104 generates print queue information based on the received device information (s413). Figure 6(e) shows the print queue information generated in Embodiment 2. The print queue information generated in Embodiment 2 does not include the connection configuration information shown in Figure 6(d), but it does include ID information. The ID information is empty when the print queue is generated.

[0173] The above is the process that replaces Figure 8(a) of Embodiment 1.

[0174] Next, Figure 12 will be used to explain the process in Embodiment 1 that replaces Figure 9. Parts that perform the same processing as in Figure 9 will be given the same reference numerals, and parts that differ from Embodiment 1 will be explained.

[0175] When the user selects the advanced settings button on the print settings screen 1300, the print settings extension application 312 is launched (s1006). The print settings extension application 312 sends a request to the cloud print service 321 to obtain print queue information (s1007). The cloud print service 321 sends an inquiry for ID information to the cloud print-compatible printer 104 (s1109). The cloud print-compatible printer 104 receives the inquiry for ID information and sends the printer name to the cloud print service 321 (s1110).

[0176] The cloud print service 321 adds the received ID information to the print queue information (s1111). The subsequent processing is the same as in Figure 9.

[0177] If ID information is already set in the print queue information, it is not necessary to perform the processes described in s1109 to s1111.

[0178] Next, Figure 13 will be used to explain the process that replaces Figure 10 in Embodiment 1. Parts that perform the same processing as in Figure 10 will be given the same reference numerals, and parts that differ from Embodiment 1 will be explained.

[0179] When the user selects the advanced settings button on the print settings screen 1300, the print settings extension application 312 is launched (s1006). The print settings extension application 312 sends a request to the cloud print service 321 to obtain print queue information (s1007). The cloud print service 321 sends a query for ID information to the cloud print proxy 331 (s1121).

[0180] The cloud print proxy 331 generates ID information by adding additional information to the printer name of the cloud print-incompatible printer 105 connected via the printer driver 332 (s1122). For example, if the printer name is "Printer-A", the additional information "Proxy" is added to generate ID information "Printer-A-Proxy".

[0181] The cloud print proxy 331 sends the generated ID information to the cloud print service 321 (s1123).

[0182] The cloud print service 321 adds the received ID information to the print queue information (s1124).

[0183] If ID information is already set in the print queue information, it is not necessary to perform the processes described in s1121 to s1124.

[0184] Furthermore, in the sequences shown in Figures 12 and 13, the cloud print service queries the cloud print proxy or cloud print-compatible printer for ID information when the extended printing application is launched. Alternatively, the cloud print service could query the cloud print proxy or cloud print-compatible printer for ID information when creating a print queue, and set the obtained ID information in the print queue information. In that case, when the extended print settings application is launched, it will refer to the ID information in the print queue information of the cloud print service, and will not query the cloud print proxy or cloud print-compatible printer for ID information.

[0185] Using Figure 14, we will explain the processes corresponding to s1009 in Figure 12 and s1009 in Figure 13. Each block shown in the flowchart of Figure 14 is realized when the program for the cloud print service 321, stored in the memory 224 of the cloud print server 102, is loaded into memory 223 and executed by the CPU 222.

[0186] First, the connection type determination unit 31203 of the print settings extension application 312 extracts ID information from the acquired print queue information (s601).

[0187] The connection type determination unit 31203 then determines whether or not additional information is attached to the ID information (s602). The connection type determination unit 31203 determines whether or not additional information is attached based on whether or not a specific string is included in the ID information. For example, if the ID information contains the string "Proxy", it is determined that additional information is attached, and if it does not contain the above string, it is determined that no additional information is attached. Alternatively, the printer name and printer ID may be compared, and if there is a difference, it may be determined that additional information is attached.

[0188] If it is determined that the ID information does not have any additional information attached, the extended application UI unit 31205 displays the extended print settings screen shown in Figure 5(a) (s603).

[0189] If it is determined that additional information is attached to the ID information, the extended application UI unit 31205 displays the screen shown in Figure 5(b) (s604).

[0190] The extended application UI unit 31205 determines whether the OK button has been selected (s605). The process described in s605 is repeated until the OK button is selected.

[0191] If the OK button is selected, the extended application UI unit 31205 displays the extended print settings screen shown in Figure 5(c) (s606). This completes the process related to displaying the extended print settings screen.

[0192] As described above, the print settings extension application 312 uses the ID information contained in the print queue information obtained from the cloud print service 321 to determine the connection configuration between the cloud print service 321 and the printer. Therefore, even if the connection configuration is not registered with the cloud print service 321, the extended print settings screen can be changed for cloud print-compatible printers and non-cloud print-compatible printers.

[0193] <Embodiment 3> Embodiment 1 describes an example of a method in which, when a printer is registered, the cloud print service 321 determines the printer connection type, adds the connection type information to the print queue information, and the print setting extension application 312 uses that connection type information to change the UI.

[0194] In this embodiment, we will describe a method by which the print settings extension application 312 determines the connection status using capability information included in the print queue information obtained from the cloud print service 321.

[0195] Here, we will explain the differences from Embodiment 1.

[0196] In Embodiment 3, the process shown in Figure 8(b) is performed instead of the process shown in Figure 8(a) of Embodiment 1. The process in Figure 8(b) in Embodiment 3 is different from the process in Embodiment 2, so it will be explained with reference to Figure 8(b).

[0197] The process described in Figure 8(b) is achieved when the program for the cloud print service 321, stored in the memory 224 of the cloud print server 102, is loaded into memory 223 and executed by the CPU 222.

[0198] The device management unit 32102 receives a printer registration request (s411). The printer registration request includes the device information shown in Figure 6(g). In Embodiment 3, whether the printer to be registered is a cloud print-compatible printer 104 or a cloud print-incompatible printer 105, the device ID stores information that identifies the printer. In Embodiment 3, the capabilities information also includes the image data file formats supported by the printer. For example, the cloud print-compatible printer 104 notifies the cloud print service 321 that it supports PDF and Raster, but not XPS. On the other hand, the cloud print proxy 331 notifies the cloud print-incompatible printer 105 that it supports XPS.

[0199] The print queue management unit 32104 generates a print queue (s412). Then, the print queue management unit 32104 generates print queue information based on the received device information (s413). Figure 6(f) shows the print queue information generated in Embodiment 3. The print queue information generated in Embodiment 3 does not include the connection configuration information shown in Figure 6(d), but instead includes the support file format in the capability information.

[0200] In Embodiment 3, the sequences in Figures 9 and 10 are the same as in Embodiment 1, but the details of the connection configuration determination process shown in s1009 are different, so we will explain using Figure 15.

[0201] Figure 15 shows an example of the processing of the print settings extension application 312. The processing shown in Figure 15 is achieved when the program of the print settings extension application 312, which is stored in the memory unit 214 of the client terminal 101, is loaded into memory 213 and executed by the CPU 212.

[0202] First, the connection type determination unit 31203 of the print setting extension application 312 extracts capability information from the print queue information (s701).

[0203] The connection type determination unit 31203 determines whether or not XPS files are supported based on the supported file formats of the extracted capability information (s702).

[0204] If the print queue information determines that XPS files are not supported, the extended application UI unit 31205 of the print settings extension application 312 displays the extended print settings screen shown in Figure 5(a) (s703).

[0205] On the other hand, if the print queue information determines that XPS files are supported, the extended application UI unit 31205 displays the screen shown in Figure 5(b) (s704).

[0206] The extended application UI unit 31205 determines whether the OK button has been selected (s705). The process described in s705 is repeated until the OK button is selected.

[0207] If the OK button is selected, the extended application UI unit 31205 displays the extended print settings screen shown in Figure 5(c) (s706). This completes the process related to displaying the extended print settings screen.

[0208] As described above, the print settings extension application 312 can determine the connection configuration between the cloud print service 321 and the printer by using the capability information contained in the print queue information obtained from the cloud print service 321.

[0209] Therefore, even if the connection type is not registered with the Cloud Print Service 321, the extended print settings screen can be changed between Cloud Print compatible printers and Cloud Print incompatible printers.

[0210] <Other Embodiments> In the above embodiments 1 to 3, when the print queue of the cloud print-incompatible printer 105 is selected on the print settings screen 1300 and the detailed settings button 1306 is selected, the screen shown in Figure 5(b) is displayed. Alternatively, Figure 5(b) may not be displayed, and the screen shown in Figure 5(c) or Figure 5(d) may be displayed from the print settings screen 1300.

[0211] The present invention can also be realized by performing the following process: supplying software (programs) that realize the functions of the embodiments described above to a system or device via a network or various storage media, and having the computer (or CPU, MPU, etc.) of that system or device read and execute the program code. In this case, the computer program and the storage medium storing the computer program constitute the present invention.

Claims

1. A selection means for selecting one printer from a plurality of printers, including the first printer registered in the server system based on a registration request transmitted from the first printer, and the second printer registered in the server system based on information of a second printer registered in a server different from the server included in the server system, An application executed on an information processing device having an acquisition means for acquiring an application for accepting the setting of values ​​for items related to printing based on information of one selected printer, The process includes a display step in which, when an instruction object for displaying additional print settings is selected while the first printer is selected, a settings object is displayed that accepts the setting of values ​​for predetermined items related to printing. An application characterized in that, even if the instruction object for displaying additional print settings is selected while the second printer is selected, the setting object is not displayed.

2. The application according to claim 1, characterized in that the predetermined item is an item that sets a string used to instruct the start of printing based on print data.

3. The server system generates print data in accordance with IPP, The application according to claim 1 or 2, characterized in that a server different from the server included in the server system converts the print data in accordance with the IPP into a format that can be interpreted by a printer driver installed on the different server.

4. The application according to any one of claims 1 to 3, further comprising determination means for determining whether the print queue is a print queue for a printer that receives print data via a different server, based on print queue information registered in the server system.

5. The display step is a screen for selecting the print queue to use, which is different from the print settings screen, The application according to any one of claims 1 to 4, characterized in that the predetermined items are items that cannot be set on the different screens.

6. The application according to claim 1, characterized in that the setting object is a setting object that accepts the setting of a value for the item of punch hole setting.

7. The application according to claim 1, characterized in that the setting object is a setting object that accepts the setting of a value for the stapleless binding setting item.

Images