Information processing apparatus and print setting 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

[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 to a printer via a cloud server 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 printing 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 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 performing printing via a cloud server using an existing printer that cannot interpret the print data transmitted by the cloud server, conversion of the print data by a proxy server is required. However, the print data received by the proxy server from the cloud server may include print settings that the proxy server cannot perform the conversion for.

[0006] If the user sets, on the client terminal, a setting item for which the proxy server cannot perform the conversion, there is a possibility that output will be made with settings unintended by the user.

[0007] Therefore, in view of the above problems, an object of the present invention is to suppress the situation where print settings that may prevent a desired output from being obtained at the output destination printer are set on the client terminal.

Means for Solving the Problems

[0008] The information processing apparatus described in this specification includes: a selection means for selecting a print queue to be used from the print queues registered in the server system; when a print queue that receives the print data without passing through another server system that converts the format of the print data transmitted by the server system is selected, a print setting screen that can set predetermined setting items is displayed, and when a printer queue that receives the print data via the other server system is selected, a control means for displaying a print setting screen that cannot set the predetermined setting items; and a transmission means for transmitting print data based on the print settings set via the print setting screen to the server system.

Effects of the Invention

[0009] The information processing apparatus described in the present invention can suppress the situation where print settings that may prevent a desired output from being obtained at the output destination printer are set on the client terminal.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Mode 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 Print in the present embodiment. A client terminal 101, a Cloud Print server 102, a Cloud Print proxy server 103, a Cloud Print-compatible printer 104, and a Cloud Print-incompatible printer 105 are connected via a network 106.

[0013] In FIG. 1, one client terminal 101, one Cloud Print-compatible printer 104, and one Cloud Print-incompatible printer 105 are shown respectively, but there may be a plurality of these.

[0014] The Cloud Print server 102 and the Cloud Print proxy server 103 may be a server system composed of one information processing device or a server system composed of a plurality of information processing devices. By configuring each server with a plurality of information processing devices, the processing load can be dispersed. Also, physically, one server may be configured to virtually play the roles of each server internally.

[0015] The network 106 assumes a WAN such as the Internet, but may also be a closed environment such as a corporate LAN.

[0016] A PC, tablet, or smartphone operated by a user operates as the client terminal 101. Any application software can be executed on the client terminal 101. The cloud print driver 311 and the print settings extension application 312 are installed on the client terminal 101.

[0017] The cloud print-compatible printer 104 and the cloud print-incompatible printer 105 are devices that actually print on physical paper. The cloud print-compatible printer 104 and the cloud print-incompatible printer 105 receive print data transmitted by the cloud print server 102 via the network 106, convert it into image data, and print it. The 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). The cloud print-incompatible printer 105 is a printer that cannot communicate using a predetermined protocol. Therefore, when printing via cloud print using the cloud print-incompatible printer 105, the cloud print-incompatible printer 105 communicates via the cloud print proxy server 103.

[0018] The cloud print server 102 has the role of receiving print data composed of print settings and image data from the client terminal 101 and transmitting 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 instead of the printer 105 that does not support cloud print, and exchanges information such as printer information and print data. The cloud print proxy server 103 has a cloud print proxy 331 and a printer driver 332 installed therein.

[0020] Next, the hardware configuration in the system of this embodiment will be described with reference to FIG. 2.

[0021] FIG. 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 storage unit 214 refers to a non-volatile storage device such as a hard disk or an SSD, and can store and rewrite digital data.

[0023] The control unit 211 is composed of a CPU 212 and a memory 213, and controls the overall operation of the client terminal 101. The CPU 212 expands the program stored in the storage unit 214 into the memory 213 and executes it. The memory 213 is the main memory of the CPU 212 and is used as a temporary storage area for expanding work areas and various programs.

[0024] The network communication unit 215 is a device that communicates with an external network 106, and inputs and outputs digital data with an external server, a client terminal, 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 operation unit 217 is a device for receiving input from the user by means of a keyboard, a mouse, etc. A device having both functions of the display unit 216 and the operation unit 217, such as a touch panel, may also be used.

[0027] Figure 2(b) is a block diagram showing the hardware configuration of the cloud print server 102. The cloud print server 102 includes a storage unit 224, a control unit 221, and a network communication unit 225. Since the descriptions of the storage unit 224, the control unit 221, and the network communication unit 225 are the same as those of the client terminal 101, they are omitted. In FIG. 2(b), the storage unit 224, the control unit 221, and the network communication unit 225 are each described one by one, but each may have one or more.

[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. Since the descriptions of the display unit 236, the operation unit 237, the storage unit 234, the control unit 231, and the network communication unit 235 are the same as those of the client terminal 101, they are omitted. In FIG. 2(c), the display unit 236, the operation unit 237, the storage unit 234, the control unit 231, and the network communication unit 235 are each described one by one, but each may have one or more.

[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 for displaying information to the user in real time, such as a touch panel or an LED provided in the cloud print-compatible printer 104.

[0031] The operation unit 247 is a device for receiving input from the user, and may include hard keys such as a numeric keypad in addition to the touch panel. Since the storage unit 244 and the control unit 241 are equivalent to those of the client terminal 101, the description thereof is omitted. Note that the storage unit 244 and the control unit 241 may each have one or more configurations.

[0032] The network communication unit 245 is a device for communicating with an external network 106, and mainly has a role of receiving print data and transmitting the state of the cloud print-compatible printer 104 such as an error to an external server or the like.

[0033] The printing unit 248 is a device that performs printing processing by performing a series of operations of paper feeding, printing, and paper discharging on the paper prepared in the cassette or tray. The printing method is not particularly limited, such as an electrophotographic method or an inkjet method. Finishing devices such as a duplex unit, stapler, and punching process used at the time of paper discharge are also included in the printing unit 248.

[0034] In this embodiment, as an example of the cloud print-compatible printer 104, a single-function printer that performs only a printing function is described, but a multifunction printer (MFP) that also has a scanner function and a FAX function may be used.

[0035] FIG. 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 description of the display unit 256, the operation unit 257, the storage unit 254, the control unit 251, the network communication unit 255, and the printing unit 258 is omitted because it is equivalent to that of the cloud print-compatible printer 104.

[0037] Next, the software configuration in the system of this embodiment will be described with reference to FIG. 3.

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

[0039] The client terminal 101 has a cloud print driver 311 and a print setting extension app 312. The cloud print driver 311 is software for generating print data to be transmitted to the cloud print server 102. The print setting extension app 312 is an application for extending the functions of the cloud print driver 311, and executes processes such as display control of the print setting screen. Note that 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 at which the print setting extension app 312 is downloaded and installed on the client terminal 101 will be described later with reference to FIG. 16.

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

[0041] The cloud print service I / F 31101 processes the exchange of data and commands with the cloud print service 321.

[0042] The print job management unit 31102 performs processes such as generation of a print job and transmission of the print job. The print job management unit 31102 generates print data conforming to the protocol supported by the cloud print service 321, and transmits the print data as a print job. For example, when the cloud print service performs transmission and reception of print data in accordance with IPP, the print job management unit 31102 generates print data conforming to IPP for the print settings. Also, with respect to the file format of the image data included in the print data, the print job management unit 31102 generates print data in accordance with the file formats supported by the cloud print service (for example, PDF or PWG-Raster).

[0043] The UI unit 31103 has roles such as displaying the UI prepared by the cloud print driver 311 and receiving user operations from the client terminal 101. The UI unit 31103 displays the print settings screen 1300 shown in FIG. 4(a). On the print settings screen 1300, objects for performing printing in printing using the cloud print service 321 are arranged. In the area 1301 of FIG. 4(a), information on the print queue registered in the cloud print server 102 is displayed. The button 1302 is a button for displaying a list of print queues registered in the cloud print server 102. The user selects the button 1302 and selects the print queue corresponding to the printer to be used for printing from the displayed print queues. The area 1303 is an area for setting the number of copies to be printed. The area 1304 is an area for setting the color mode. The button 1305 is a button for changing the color mode. After the user selects the button 1305, the user can select the color mode at the time of printing. The detailed settings button 1306 is a button for starting the print settings extension application 312. The print button 1307 is a button for sending a print instruction 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 transmitted to the cloud print service 321 via the cloud print service I / F 31101.

[0044] In addition, in this embodiment, the description has been given assuming that the cloud print driver 311 has the UI unit 31103 and displays the print setting screen 1300. However, the OS of the client terminal 101 or an application installed in the client terminal 101 may have the UI unit and display the print setting screen 1300. In such a case, in the area 1301, in addition to the print queues registered in the cloud print server 102, print queues to which the client terminal 101 can directly transmit print data are displayed. When a print queue to which the client terminal 101 can directly transmit print data is selected, the client terminal 101 generates print data using a printer driver corresponding to the selected print queue. The generated print data is sent to the printer without passing through the cloud print server 102.

[0045] The print setting extension app I / F 31104 processes the exchange of data and commands with the print setting extension app 312.

[0046] The print setting extension app 312 further has the following software configuration.

[0047] The cloud print service I / F 31201 processes the exchange of data and commands with the cloud print service 321. The cloud print service I / F 31201 acquires information on the printer and print settings set on the print setting screen 1300 from the print extension app I / F 31104 of the cloud print driver 311. In addition, the cloud print service I / F 31201 has a role of passing the print settings set in the print setting extension app 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 form 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 form determination unit 31203 acquires the print queue information selected in the area 1301 from the cloud print driver 311, and makes a determination based on the information.

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

[0051] The extended app UI section 31205 has roles such as displaying the UI provided by the print settings extension app and receiving user operations from the client terminal 101. FIG. 5(a) shows an example of the print settings UI displayed by the extended app UI section 31205 of the print settings extension app 312. The extended print settings screen 801 is a screen displayed when the user selects the detailed settings button 1306 on the print settings screen 1300. The extended print settings screen 801 can set print settings that cannot be set on the print settings screen 1300. For example, 802 is an area for setting whether to punch holes in the output paper. When the user selects 802, the on / off of the punch setting is toggled. Off means not punching holes in the paper, and on means punching holes in the paper. Secure Print 803 is a function where printing starts by inputting the password set in the print settings extension app 312 into the printer. Area 804 is an area for inputting the password required at the time of printing when using the Secure Print function. After the user gives a print instruction, when the same password as the password input in area 804 is input into the printer, the printer starts printing. In addition to the above setting items, the extended print settings screen 801 is provided with areas for setting the output paper size used for output, setting whether to perform double-sided printing, and setting related to the stamp function of adding a predetermined image to the paper and 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] Note that in this embodiment, the extended print settings screen 801 only displays setting items that cannot be set on the print settings screen 1300. It is also possible that the extended print settings screen 801 also displays setting items that can be set on the print settings screen and the settings of those setting items can be changed.

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

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

[0055] The account management unit 32101 manages the authentication of tenants and users registered in the cloud print service 321. A tenant is a group to which one or more users belong. The account management unit 32101 manages by associating information such as the user ID of each user and the password required for authentication. Further, the account management unit 32101 manages by associating the user ID with the tenant ID to which the user belongs.

[0056] The device management unit 32102 manages information about printers registered in the cloud print service 321. The device information is registered in the device management unit 32102 by a registration request from the printer. Fig. 6(a) is an example of the device information registered in the device management unit 32102. The device ID is identification information for identifying the printer, such as HWID (HardWare Identification Information) for specifying the hardware configuration of the printer. The tenant ID is identification information for the tenant who can use the device. The printer name is the name of the device notified from the printer. The device configuration information is the configuration information of the printer, such as whether a finisher for performing post-processing such as stapling or punching is connected to the printer, or whether a unit for performing duplex printing is connected. The capability information is information indicating the functions that the printer can execute. The capability information includes information such as whether color printing is possible, whether duplex printing is possible, information on the positions where stapling can be performed, information on the punch holes that can be used, and whether the secure print function can be used.

[0057] The print management unit 32103 makes a determination as to whether to permit a print job transfer request from the cloud print-compatible printer 104 or the cloud print proxy server 103, and manages the transfer of the print job.

[0058] The print queue management unit 32104 receives print jobs from the outside and holds the received print jobs in an area prepared in the storage unit 224 of the cloud print server 102. The print queue management unit 32104 manages the print queue information described in FIG. 6(d). The print queue information includes a print queue name, device configuration information, capability information, connection form information, and tenant ID. The print queue name is the name of the print queue and is the name displayed on the print setting screen 1300. The device configuration information and capability information are the same as the device information in FIG. 6(a). The connection form information is information indicating whether the print queue is a queue that transmits print data to the printer without passing through the cloud print proxy server 103 or a queue that transmits print data to the cloud print proxy server 103. The tenant ID is identification information of the tenant that can use the print queue. The device information described in FIG. 6(a) and the print queue information described in FIG. 6(d) are linked using the tenant ID as a key. The device ID is the same as the device ID in FIG. 6(a) and is information for identifying the printer associated with the print queue. For example, the HWID that identifies the hardware of the printer is registered as the device ID.

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

[0060] The cloud print proxy 331 further has the following software configuration.

[0061] The cloud print service I / F 33101 processes the exchange of data and commands performed between 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 necessary.

[0063] The printer driver I / F 33103 processes the exchange of data and commands with the printer driver 332.

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

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

[0066] The device I / F 33202 processes the exchange of data and commands between the printer driver 332 and the cloud-print non-compatible printer 105.

[0067] Also, the print management unit 33201 manages the capability information of the cloud-print non-compatible printer 105 associated with the printer driver 332. The capability information managed by the print management unit 33201 is converted by the print data conversion unit 33102 of the cloud print proxy 331 into interchange information interpretable by the cloud print server 102 and notified to the cloud print server 102. FIG. 6(b) is a diagram showing an example of the interchange information generated by the print data conversion unit 33102. The interchange information includes a proxy ID, a 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 non-compatible printer 105 corresponding to the printer driver 332. The capability information is the capability information of the cloud-print non-compatible printer 105 corresponding to the printer driver 332. As described above, when passing through the cloud print proxy server 103, the proxy ID is notified to the cloud print server 102 instead of the device ID.

[0068] The mutual exchange information described in FIG. 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 described in FIG. 6(c) into a format that can be handled by the printer driver 332 and passes it to the printer driver 332.

[0069] FIG. 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 reception unit 34101 receives print data transmitted from the outside via the network 106 and stores it in the storage unit 244 of the cloud print-compatible printer 104. The print data reception unit 34101 can process print data of a predetermined protocol that can be generated by the cloud print server 102.

[0071] The device management unit 34102 manages options, capability information, paper remaining amount, ink / toner remaining amount, 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 on paper.

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

[0074] The cloud print service I / F 34105 processes the exchange of data and commands performed with the cloud print service 321.

[0075] FIG. 3(e) is a block diagram showing the software configuration of the device control unit 351 of the non-cloud print-compatible 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 transmitted by the cloud print server 102 and cannot interpret the print data. In the present embodiment, the print data transmitted by the cloud print server 102 is converted into a format that can be processed by the print data receiving unit 35101 using the printer driver of the cloud print proxy server 103. By doing so, printing via the cloud print server 102 is realized using the cloud print non-compatible printer 105.

[0077] The device management unit 35102 manages the capability information, remaining paper amount, and remaining ink / toner amount of the cloud print non-compatible printer 105. The device management unit 35102 manages the above information in a format different from that of the cloud print server 102. Therefore, in order to notify the cloud print server 102 of the capability information of the cloud print non-compatible printer 105, conversion by the cloud print proxy server 103 is required.

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

[0079] Next, with reference to Fig. 7(b), an example of the user procedure for registering the cloud print compatible printer 104 with the cloud print service 321 in the present embodiment and the sequence between each software and service will be described below.

[0080] First, the user instructs printer registration from the operation unit 247 of the cloud print compatible printer 104 (s921).

[0081] Next, the cloud print compatible printer 104 displays a login UI to the cloud print service 321 on the operation unit 247 (s922).

[0082] Next, the user inputs login information into the login UI (s923). The login information is the user ID and password.

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

[0084] Next, the cloud print service 321 performs an authentication process based on the login information received together with the authentication request (s925). If the authentication is successful, the cloud print service 321 issues an access token and sends the token 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 after the next time. Note that in s925, if the authentication fails, the sequence shown in FIG. 7(b) ends.

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

[0086] The cloud print service 321 performs printer registration processing (s928). Details of the printer registration processing executed in s928 will be described later.

[0087] Next, after the printer registration processing, the cloud print service 321 returns a registration completion status to the cloud print-compatible printer 104 (s929). Then, the cloud print-compatible printer 104 displays the registration completion status on the operation unit 247 (s930).

[0088] Next, with reference to Fig. 7(a), an example of the user procedure for registering a cloud print-incompatible printer to the cloud print service in this embodiment and the sequence among each software and service will be described. It is assumed that a printer driver 332 is installed in the cloud print proxy server 103 and a print queue corresponding to the cloud print-incompatible printer 105 is generated. When generating the print queue, the printer driver 332 communicates with the cloud print-incompatible printer 105 to obtain the printer's hardware ID, model name, device configuration information, and capability information.

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

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

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

[0092] Here, a method for obtaining the HWID of a printer, which is one of the printer information in this embodiment, will be described. The cloud print proxy 331 calls the OpenPrinter() function of the Win32API to obtain the printer handle of the printer driver 332 selected in s901. Next, the GetPrinterDriver() function is called using the obtained printer handle of the printer driver 332 to obtain DRIVER_INFO_6. The structure DRIVER_INFO_6 is generated when a print queue is generated in the cloud print proxy server 103. The structure DRIVER_INFO_6 is data containing printer driver information. Specifically, it contains information associated with the printer driver, such as the printer driver name and the installation path of the printer driver. This DRIVER_INFO_6 has a value called pszHardwareID, in which the HWID of the printer driver is stored. 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 embodiment, the Win32API is used to obtain the hardware ID of the printer, but any means can be used as long as the hardware ID can be obtained.

[0094] Next, the cloud print proxy 331 associates and saves the received printer information with the printer driver 332 (s904).

[0095] Next, the cloud print proxy 331 enables the printer registration button on the UI and indicates that printer registration has become effective (s905).

[0096] Next, the user presses the printer registration button to instruct 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 inputs login information into the login UI (s908).

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

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

[0101] Next, the cloud print proxy 331 converts the data format of the saved printer information 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 conforming to IPP.

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

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

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

[0105] Then, the cloud print proxy 331 displays the registration completion status on the UI (s916).

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

[0107] The processing shown in FIG. 8(a) is realized by the program of the cloud print service 321 stored in the storage unit 224 of the cloud print server 102 being loaded into the memory 223 and executed by the CPU 222.

[0108] The processing described in FIG. 8(a) is started as a result of the cloud print service 321 receiving a printer registration request from the outside 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 the device information shown in FIG. 6(g) or the interchange information shown in FIG. 6(b). The device management unit 32102 generates the device information shown in FIG. 6(a) based on the received device information or interchange information and the tenant ID corresponding to the logged-in user.

[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 FIG. 6(d) (s403). When the information received together with the registration request is the device information shown in FIG. 6(g), the printer name is set as the print queue name. When the information received together with the registration request is the interchange information shown in FIG. 6(b), the print queue name generated from the interchange information is used as the 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 a registration request from the cloud print-compatible printer 104 when the information received together with the registration request includes a device ID. On the other hand, when the information received together with the registration request does not include a device ID, the print queue management unit 32104 determines that the registration request is a registration request from the cloud print-incompatible printer 105. Note that the determination in s404 may be made based on whether the received information includes a proxy ID together with the registration request. 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 character string included in the received device ID. When the received device ID includes a specific character string, it is determined that the device ID is the proxy ID of the cloud print proxy server 103. On the other hand, when the received device ID does not include a specific character string, it is determined that the device ID is the device ID of the cloud print-compatible printer 104. Note that 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 above method.

[0113] When 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 "direct printer connection" in the connection form information of the print queue information (s405).

[0114] On the other hand, when the received registration request is a registration request sent by the cloud print-incompatible printer 105, information indicating "connection via cloud print proxy" is set in the printer connection form in the print queue information (s406). After the above processing, the cloud print service 321 ends the printer registration process shown in Fig. 8(a).

[0115] The above is the procedure and process for registering printer information in the cloud printing service 321.

[0116] After the above processing, the user performs a print queue generation process for submitting a print job using the cloud printing service 321 on the client terminal 101. Here, the print queue generation process on the client terminal 101 will be described with reference to FIG. 16.

[0117] The sequence shown in FIG. 16 starts when the user operates the client terminal 101 and instructs to search for the printers registered in the cloud printing service 321.

[0118] When the client terminal 101 receives a search instruction for the printers registered in the cloud printing service 321, it sends an authentication request to the cloud printing service 321 (s1604). In s1604, first, the client terminal 101 sends the user ID and password, or an access token to the cloud printing service 321, to the cloud printing service 321. The cloud printing service 321 authenticates the user based on the information received from the client terminal 101. Then, the cloud printing service 321 sends the authentication result to the client terminal 101 (s1605). If the received authentication result indicates successful authentication, the client terminal 101 executes the following processing. If the received authentication result indicates failed authentication, the client terminal 101 does not execute the following processing and ends the sequence shown in FIG. 16.

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

[0120] The client terminal 101 displays the list of print queues received from the cloud printing service 321 on the display unit 216. When displaying the list of print queues, it may not display the print queue of the printer for which a print queue for sending a print job to the client terminal 101 via the cloud printing service has already been created.

[0121] Then, the client terminal 101 accepts the selection of the print queue corresponding to the print queue generated by the client terminal 101 from the user. The client terminal 101 sends a request to obtain information on the selected print queue to the cloud printing service 321 (s1608). The cloud printing service 321 receives the request to obtain information on the print queue and sends the print queue information of the print queue selected by the user to the client terminal 101 (s1609). Note that the print queue information transmitted here is the information as shown in FIG. 6(d). In the capability information, in addition to the functions that can be used by the printer associated with the print queue, the HWID of the printer is stored.

[0122] The client terminal 101 generates a print queue for sending a print job via the cloud printing service 321 in the client terminal 101 based on the received print queue information (s1610).

[0123] Then, the client terminal 101 sends a request to obtain usage information of the printer corresponding to the generated print queue to a printer driver distribution service (not shown) (s1611). In s1611, in order to obtain additional information, 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.

[0124] The printer driver distribution service is a service provided by a server system that can be accessed by the client terminal 101 via the network 106. The server system is composed of one or more information processing devices having a hardware configuration similar to that of the cloud print server shown in Fig. 2(b). The printer driver distribution service stores files in which information about printer drivers and applications for extending printer drivers is described. For example, the identification information of a print setting extension application for extending the print setting screen is described in the above file. The printer driver distribution service stores the printer driver and the above file in association with the HWID of the printer.

[0125] The printer driver distribution service identifies the file corresponding to the HWID received from the client terminal 101 and sends it to the client terminal as additional information (s1612). The client terminal 101 sends a request to obtain a print setting extension application identified by the identification information of the application described in the received file (which is the additional information) to an application distribution service (not shown) (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. The server system is composed of one or more information processing devices having a hardware configuration similar to that of the cloud print server shown in FIG. 2(b). The application distribution service stores an application in association with identification information of the application.

[0127] The application distribution service transmits the application identified by the identification information of the application 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 the application (s1615). By doing so, when the print setting extension application is called from the print setting screen, the application corresponding to the selected print queue can be launched.

[0129] As shown in FIG. 16, by acquiring the HWID of the printer associated with the print queue generated by the client terminal 101, the information of the generated print queue can be added and extended from an external server.

[0130] FIG. 9 is a diagram showing an example of a sequence showing the processes related to print setting and print processing in the present embodiment. FIG. 9 is a sequence when the cloud print-compatible printer 104 is used.

[0131] The user gives an instruction to display the print setting screen in the application (s1000). The cloud print driver 311 receives the instruction to display the print setting screen via the application.

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

[0133] The user operates the area 1301 of the print settings screen 1300 to select a 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 described in FIG. 16. The information used for updating the print settings screen is, for example, capability information, the name of the print queue, HWID, etc. Suppose that from the selected print queue information, the printer associated with the print queue is a printer that can perform both color printing and monochrome printing. At this time, the cloud print driver 311 displays a print settings screen in which either color or monochrome can be selected in the area 1304 of FIG. 4(a). On the other hand, suppose that from the print queue information of the selected print queue, the printer associated with the print queue is a monochrome printer. At this time, the cloud print driver 311 displays a print settings screen in which only monochrome can be selected in the area 1304 of FIG. 4(a).

[0135] The user operates the print settings screen 1300 to instruct the activation of the print settings extension app 312 (s1004). When the user selects the detailed settings button 1306 of the print settings screen 1300, the cloud print driver 311 activates the print settings extension app 312 associated with the selected print queue (s1005).

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

[0137] Next, the print settings extension app 312 sends a request to obtain print queue information to the cloud print service 321 (s1007). The cloud print service 321 sends the print queue information (Fig. 6(d)) corresponding to the acquisition request received from the print settings extension app 312 to the print settings extension app 312 (s1008). The print settings extension app 312 refers to the connection form information of the received print queue information and determines whether the printer corresponding to the selected print queue is a printer that passes through the cloud printer proxy server (s1009). The print settings extension app 312 displays an extended print settings screen based on the determination (s1010). In Fig. 9, in s1009, since information indicating that the printer is directly connected is added to the print queue information, the print settings extension app 312 displays the UI shown in Fig. 5(a).

[0138] The user operates the print settings extension app 312 to perform print settings and selects the "OK" button (s1011). The print settings extension app 312 executes processing to terminate the app (s1012). Then, the print settings extension app 312 sends the print settings set on the extended print settings screen shown in Fig. 5(a) to the cloud print driver 311 (s1013). The cloud print driver 311 displays the print settings screen shown in Fig. 4 again. The user operates the print settings screen 1300 and selects the print button (s1014). The cloud print driver 311 generates print data based on the print settings set on the print settings screen 1300 and the print settings received from the print settings extension app 312 in s1013, 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 and PWG-Raster. Then, the cloud print driver 311 sends it 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 acquire print data to the cloud print service 321 (s1016). The acquisition request may be sent by polling processing at regular intervals, or may be triggered by the user logging in to the cloud print-compatible printer 104.

[0140] The cloud print service 321 sends the print data stored in association with the print queue to the cloud print-compatible printer 104 (s1017). The cloud print-compatible printer 104 prints an image based on the received print data (s1018). Thereafter, the cloud print-compatible printer 104 notifies the cloud print service 321 of the completion of printing (s1019).

[0141] The above is the sequence from the print settings until printing is executed by the cloud print-compatible printer 104. In FIG. 9, print queue information is acquired in s1007 and s1008, and a connection form determination process is performed. It is also possible to perform a determination of the connection form based on the print queue information acquired in the process of generating a print queue on the client terminal 101 (FIG. 16). In this case, S1007 to s1009 may not be performed.

[0142] Next, with reference to FIG. 10, the printing sequence using the cloud print-incompatible printer 105 will be described. Regarding the parts in FIG. 10 where the same processing as in FIG. 9 is performed, the same reference numerals as in FIG. 9 are given, and the description is omitted.

[0143] Since S1000 to S1009 are the same as in FIG. 9, the description is omitted.

[0144] When information indicating that the print queue information is connected via the cloud print proxy is added, the print settings extension app 312 displays the screen shown in Fig. 5(b) (s1400). Fig. 5(b) shows an example of the print settings UI of the print settings extension app 312. The extended print settings screen 811 displays a warning dialog 812 regarding the finisher. For the cloud print non-compatible printer 105 via the cloud print proxy server, even if the device configuration information of the printer is changed, the change may not be reflected in the print queue information of the cloud print service 321. Therefore, the warning dialog 812 is displayed to prompt the user to re-register the printer if the device configuration of the cloud print non-compatible printer 105 is changed.

[0145] FIG. 5(c) shows an extended print settings screen 821 that is displayed after closing the dialog in FIG. 5(b). In the extended print settings screen 821, punch settings and secure print settings cannot be made. Regarding punch settings, they are not displayed because information on a finisher capable of punching is not registered in the device configuration information of the cloud print non-compatible printer 105. There is a possibility that the password for secure printing included in the print data generated by the cloud print driver 311 cannot be converted into a format usable by the cloud print non-compatible printer. Therefore, in FIG. 5(c), the secure print setting is hidden so that it cannot be set. Thus, in FIG. 5(c), an extended print settings screen is displayed in which predetermined setting items that can be set in FIG. 5(a) cannot be set regardless of the printer's capability information and configuration information. By doing so, when printing using a cloud print non-compatible printer via the cloud print service 321, it is possible to prevent output with unintended settings. Items that can be set if the printer to be used is a cloud print compatible printer and cannot be set if it is a cloud print non-compatible printer include white paper saving, toner saving, stitch without pins, print area setting, etc. White paper saving is a function that skips white paper pages in image data and prints. Toner saving is a setting for saving the amount of toner used for printing. Stitch without pins is a function that stitches the output paper without using staples when binding. Print area setting is a function that sets the area on the paper where printing is performed.

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

[0147] FIG. 5(d) is a diagram showing another example of the extended print settings screen displayed by the print settings extension app 312 when a print queue for printing via the cloud print proxy server is selected. Here, the extended print settings screen 831 is a screen displayed after closing the warning dialog regarding the finisher. As described in the area 822, secure print settings can be made on the extended print settings screen 831. However, a warning message 823 is displayed stating that the operation guarantee during the use of the secure print function is not provided.

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

[0149] The cloud print proxy 331 periodically sends a request to the cloud print service 321 to obtain 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 is determined that the source of the print data acquisition request is the cloud print proxy 331, the cloud print service 321 performs print data conversion processing (s1402). For example, the cloud print service converts print settings written according to IPP into a Print Ticket and converts PDF format image data into XPS format data.

[0151] Then, the cloud print service 321 transmits the print data obtained by the conversion of s1402 to the cloud print proxy 331 (s1403). In this embodiment, in the cloud print service 321, the format of the print data is converted into a format that can be handled by the printer driver 332. The above conversion may be performed by the cloud print proxy 331. In that case, the cloud print service 321 transmits the print data to the cloud print proxy 331 without performing the process of s1402. The cloud print proxy 331 executes a process corresponding to s1402 on the received print data.

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

[0153] The printer driver 332 executes a conversion process of converting the received print data into rendering data that can be processed by the cloud print non - compliant printer 105 (s1405). 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 transmits the generated rendering data to the cloud print non - compliant printer 105 (s1406).

[0155] The cloud print non - compliant printer 105 executes printing based on the received rendering data (s1407).

[0156] Note that in FIGS. 9 and 10, in s1007, a request for obtaining print queue information is sent to the cloud print service, and based on the print queue information obtained from the cloud print service, the connection form is determined. At the timing of s1003, the cloud print driver may obtain print queue information from the cloud print server and pass the print queue information obtained in s1005 to the print extension application. In this case, the print setting extension application executes connection form determination processing based on the connection form information of the print queue information obtained from the cloud print driver.

[0157] Next, the details of the connection determination process described in s1009 of FIGS. 9 and 10 will be described with reference to FIG. 11. The process described in FIG. 11 is realized by the CPU 212 of the client terminal 101 executing a program stored in the memory 213 or the storage unit 214.

[0158] The flow of FIG. 11 starts when the print setting extension application 312 obtains print queue information from the cloud print service 321.

[0159] First, when the print setting extension application 312 obtains the print queue information, it extracts the information on the printer connection form set at the time of printer registration from the print queue information (s501).

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

[0161] If the determination result is YES, the print setting extension application 312 displays the extended print setting screen 801 shown in FIG. 5(a).

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

[0163] Note that in FIG. 5(b), if the "OK" button is selected and an extended print setting screen shown in FIG. 5(d) is to be displayed, the print setting extension app 312 displays FIG. 5(d) instead of FIG. 5(c) in s506.

[0164] In this way, in s502, a process is performed to detect information indicating that the selected print queue is a queue of a cloud print-compatible printer that receives print data from the cloud print service without passing through the cloud print proxy server. If the information is detected in this process, the screen shown in FIG. 5(a) where the password for secure printing can be set is displayed. On the other hand, if the information is not detected in the above detection process, FIG. 5(c) where the password for secure printing cannot be set is displayed. By doing so, it is possible to prevent the user from setting setting items that may not be correctly converted when converting the print data among the print settings that can be included in the print data generated by the cloud print driver.

[0165] As described above, by changing the display content on the UI according to the result of the print setting extension app 312 determining the connection form between the cloud print service 321 and the printer, it is possible to prevent a print setting that may not be reflected in the output from being set.

[0166] <Embodiment 2> In Embodiment 1, an example of a method was described in which, when a printer is registered, the Cloud Print Service 321 determines the printer connection form, adds connection form information to the print queue information, and the Print Settings Extension App 312 uses the connection form information to change the UI.

[0167] In this embodiment, a method will be described in which, when the Print Settings Extension App 312 requests print queue information, the Cloud Print Service 321 acquires ID information from the printer, and the Print Settings Extension App 312 determines the connection state using the ID information.

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

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

[0170] The process described in FIG. 8(b) is realized by the program of the Cloud Print Service 321 stored in the storage unit 224 of the Cloud Print Server 102 being loaded into the 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 FIG. 6(g). In Embodiment 2, even if the printer to be registered is the Cloud Print-compatible Printer 104 or the non-Cloud Print-compatible Printer 105, information for identifying the printer is stored in the device ID.

[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). FIG. 6(e) shows the print queue information generated in Embodiment 2. Instead of including the connection form information shown in FIG. 6(d), the print queue information generated in Embodiment 2 includes ID information. The ID information is empty at the timing when the print queue is generated.

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

[0174] Subsequently, the process that replaces FIG. 9 of Embodiment 1 will be described with reference to FIG. 12. The same reference numerals are given to the parts where the same processes as in FIG. 9 are performed, and the parts different from Embodiment 1 will be described.

[0175] When the user selects the detailed settings button on the print settings screen 1300, the print settings extension app 312 is launched (s1006). The print settings extension app 312 sends a request to acquire print queue information to the cloud print service 321 (s1007). The cloud print service 321 sends an inquiry about ID information to the cloud print-compatible printer 104 (s1109). The cloud print-compatible printer 104 receives the inquiry about 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 processes are the same as those in FIG. 9.

[0177] Note that when ID information is already set in the print queue information, the processes described from s1109 to s1111 do not have to be performed.

[0178] Next, the process that replaces FIG. 10 of Embodiment 1 will be described with reference to FIG. 13. The same reference numerals are given to the parts where the same processes as in FIG. 10 are performed, and the parts different from Embodiment 1 will be described.

[0179] When the user selects the detailed settings button on the print settings screen 1300, the print settings extension app 312 is launched (s1006). The print settings extension app 312 sends a request to acquire print queue information to the cloud print service 321 (s1007). The cloud print service 321 sends an inquiry about 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 non-compatible printer 105 connected via the printer driver 332 (s1122). For example, when the printer name is "Printer-A", additional information "Proxy" is added to generate ID information "Printer-A-Proxy".

[0181] The cloud print proxy 331 transmits 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] Note that if ID information is already set in the print queue information, the processes described from s1121 to s1124 may not be performed.

[0184] Also, in the sequences shown in FIGS. 12 and 13, when the extended print application is started, the cloud print service makes an inquiry about ID information to the cloud print proxy or the cloud print compatible printer. It is also possible to inquire about ID information to the cloud print proxy or the cloud print compatible printer at the timing when the cloud print service generates a print queue, and set the acquired ID information in the print queue information. In that case, when the print setting extension application is started, the ID information of the print queue information of the cloud print service is referred to, and no inquiry about ID information is made to the cloud print proxy or the cloud print compatible printer.

[0185] Using FIG. 14, the processes corresponding to s1009 in FIG. 12 and s1009 in FIG. 13 will be described. Each block shown in the flowchart of FIG. 14 is realized by loading the program of the cloud print service 321 stored in the storage unit 224 of the cloud print server 102 into the memory 223 and executing it by the CPU 222.

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

[0187] Then, the connection form determination unit 31203 determines whether additional information is attached to the ID information (s602). The connection form determination unit 31203 determines whether additional information is attached based on whether a specific character string is included in the ID information. For example, if the character string "Proxy" is included in the ID information, it is determined that additional information is attached, and if the above character string is not included, it is determined that no additional information is attached. Also, the printer name and the 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 no additional information is attached to the ID information, the extended application UI unit 31205 displays the extended print setting screen shown in FIG. 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 FIG. 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] When the OK button is selected, the extended application UI unit 31205 displays the extended print setting screen shown in FIG. 5(c) (s606). Thus, the process related to the display of the extended print setting screen ends.

[0192] As described above, the print setting extension app 312 determines the connection form between the cloud print service 321 and the printer using the ID information included in the print queue information acquired from the cloud print service 321. Therefore, even if the connection form is not registered in the cloud print service 321, the extended print setting screen can be changed between the cloud print-compatible printer and the non-cloud print-compatible printer.

[0193] <Embodiment 3> In Embodiment 1, an example of a method was described in which, at the time of printer registration, the cloud print service 321 discriminates the printer connection form, adds the connection form information to the print queue information, and the print setting extension app 312 changes the UI using the connection form information.

[0194] In this embodiment, a method will be described in which the print setting extension app 312 determines the connection state using the capability information included in the print queue information acquired from the cloud print service 321.

[0195] Here, the differences from Embodiment 1 will be described.

[0196] In Embodiment 3, the process described in FIG. 8(b) is executed instead of FIG. 8(a) of Embodiment 1. Since the process of FIG. 8(b) in Embodiment 3 is different from the process in Embodiment 2, it will be described with reference to FIG. 8(b).

[0197] The process described in FIG. 8(b) is realized by the program of the cloud print service 321 stored in the storage unit 224 of the cloud print server 102 being loaded into the memory 223 and executed by the CPU 222.

[0198] The device management unit 32102 receives a registration request for a printer (s411). The printer registration request includes the device information shown in FIG. 6(g). In Embodiment 3, whether the printer to be registered is the cloud print-compatible printer 104 or the non-cloud print-compatible printer 105, information for identifying the printer is stored in the device ID. Also, in Embodiment 3, the file format of the image data supported by the printer is described as the capability information. For example, the cloud print-compatible printer 104 notifies the cloud print service 321 of PDF and Raster as the supported file formats and does not notify XPS. On the other hand, the cloud print proxy 331 notifies XPS as the file format supported by the non-cloud print-compatible printer 105.

[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). FIG. 6(f) shows the print queue information generated in Embodiment 3. Instead of including the connection form information shown in FIG. 6(d), the supported file format is included in the capability information in the print queue information generated in Embodiment 3.

[0200] In Embodiment 3, the sequences in FIGS. 9 and 10 are the same as those in Embodiment 1, but since the details of the connection form determination process shown in s1009 are different, it will be described with reference to FIG. 15.

[0201] FIG. 15 shows an example of the processing of the print setting extension application 312. The processing shown in FIG. 15 is realized by loading the program of the print setting extension application 312 stored in the storage unit 214 of the client terminal 101 into the memory 213 and executing it by the CPU 212.

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

[0203] The connection form determination unit 31203 determines whether the XPS file is supported from the support file format of the extracted capability information (s702).

[0204] When it is determined that the XPS file is not supported from the print queue information, the extended app UI unit 31205 of the print setting extension app 312 displays the extended print setting screen shown in Fig. 5(a) (s703).

[0205] On the other hand, when it is determined that the XPS file is supported from the print queue information, the extended app UI unit 31205 displays the screen shown in Fig. 5(b) (s704).

[0206] The extended app 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] When the OK button is selected, the extended app UI unit 31205 displays the extended print setting screen shown in Fig. 5(c) (s706). The process related to the display of the extended print setting screen ends here.

[0208] As described above, the print setting extension app 312 can determine the connection form between the cloud print service 321 and the printer by using the capability information included in the print queue information acquired from the cloud print service 321.

[0209] Therefore, even if the connection form is not registered in the cloud print service 321, the extended print setting screen can be changed between the cloud print compatible printer and the cloud print non-compatible printer.

[0210] <Other Embodiments> In the above-described Embodiment 1 to Embodiment 3, when the print queue of the cloud print non-compatible printer 105 is selected on the print setting screen 1300 and the detailed setting button 1306 is selected, it is assumed that the screen shown in FIG. 5(b) is displayed. Instead of displaying FIG. 5(b), it is also possible to display the screen shown in FIG. 5(c) or FIG. 5(d) from the print setting screen 1300.

[0211] The present invention can also be realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or device via a network or various storage media, and a computer (or CPU, MPU, etc.) of the system or device reads and executes the program code. In this case, the computer program and the storage medium storing the computer program constitute the present invention.

Claims

1. selection means for selecting a print queue to be used from the print queues registered in the server system; control means for displaying a print setting screen on which predetermined setting items can be set when a print queue that receives the print data without going through another server system that converts the format of the print data transmitted by the server system is selected, and displaying a print setting screen on which the predetermined setting items cannot be set when a print queue that receives the print data via the other server system is selected; transmission means for transmitting print data based on the print settings set via the print setting screen to the server system, an information processing apparatus characterized by comprising.

2. The information processing apparatus according to claim 1, wherein the predetermined setting item is an item for setting a character string used for instructing the start of printing based on the print data.

3. The server system generates print data conforming to IPP, The information processing apparatus according to claim 1 or 2, wherein the other server system converts the print data conforming to IPP into a format that can be interpreted by a printer driver installed in the other server.

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

5. The control means displays a screen different from the print setting screen for selecting a print queue to be used, The information processing apparatus according to any one of claims 1 to 4, wherein the predetermined setting item is a setting item that cannot be set on the different screen.

6. An application for causing an information processing apparatus to display a print setting screen of print data to be transmitted to a server system, the application being executed by the information processing apparatus, a first step of displaying a print setting screen on which predetermined setting items can be set according to the fact that the printer selected as the printer to be used for printing is a printer that receives the print data without going through another server system that converts the format of the print data transmitted by the server system; A second step of displaying a print setting screen that cannot set the predetermined setting items according to the fact that the printer selected as the printer to be used for printing is a printer that receives the print data via the other server system, and causing the information processing apparatus to execute the same. An application characterized by that.

7. An application for causing an information processing apparatus to display the print setting screen in response to selection of an object for displaying the print setting screen in a state where a setting for transmitting print data to a server system having a print queue for processing print data to be transmitted to a printer is set, and executed by the information processing apparatus, A determination step of determining whether the print queue is a print queue that transmits print data to another server system that changes the received print data to print data in another format and then transmits it to the printer; An application characterized by having a control step of displaying different print setting screens according to whether or not it is determined in the determination step that the print queue is a print queue that changes the received print data to print data in another format and then transmits it to the printer.

8. The control step is to display a print setting screen that can set a predetermined setting item when it is determined in the determination step that the print queue is not a print queue that changes the received print data to print data in another format and then transmits it to the printer, and in the determination step, when it is determined that the print queue is a print queue that changes the received print data to print data in another format and then transmits it to the printer, the application according to claim 7, characterized in that a print setting screen that cannot set the predetermined setting item is displayed.

9. An application for causing an information processing apparatus to display the print setting screen in response to a button for displaying the print setting screen being pressed in a state where a setting for transmitting print data to a server system having a print queue for processing print data to be transmitted to a printer is set, and executed by the information processing apparatus, A detection step of detecting information for identifying that the print queue is a print queue that transmits print data to another server system that changes the received print data to print data in another format and then transmits it to a printer; An application characterized by having a control step of displaying different print setting screens according to whether or not the information for identification can be detected in the detection step.

Images