Information processing device 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 technology]

[0002] There is a known system in which print data is sent from a client terminal to a printer via a cloud server. In the above system, a user operates a printer driver installed on the client terminal to set print settings and issue a print instruction. The printer driver installed on the client terminal sends image data and print data based on the print settings to the cloud server. The cloud server can then print by sending the received print data to the printer.

[0003] In order for a printer to receive print data sent by a cloud server and execute printing, it is necessary for the printer to have a mechanism for interpreting the received print data. However, some existing printers do not have a mechanism for interpreting print data sent from a cloud server. Patent Document 1 discloses a cloud print system using an existing printer that cannot interpret print data sent by a cloud server, by utilizing a proxy server that can interpret print data sent 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 the 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] JP 2013-12066 A Summary of the Invention [Problem to be solved by the invention]

[0005] When printing via a cloud server using an existing printer that cannot interpret the print data transmitted by the cloud server, the print data needs to be converted by a proxy server. However, the print data received by the proxy server from the cloud server may contain print settings that the proxy server cannot convert.

[0006] If a user sets a setting item on a client terminal that the proxy server cannot convert, there is a possibility that output will be made with settings that the user does not intend.

[0007] In view of the above-mentioned problems, the present invention has an object to prevent print settings that may not produce the desired output on the destination printer from being set on a client terminal. [Means for solving the problem]

[0008] The information processing device described in this specification includes: a selection means for selecting one piece of printer information from information of a first printer registered in a server system based on a registration request transmitted from a first printer and information of a second printer registered in the server system based on a registration request transmitted from another server system; and a display control for displaying an object for receiving settings of a setting value of a predetermined setting item on a display unit based on the selection of the information of the first printer by the selection means, and not displaying the object on the display unit based on the selection of the information of the second printer by the selection means. The present invention is characterized by having a means. Effect of the Invention

[0009] The information processing apparatus according to the present invention can prevent print settings that may not provide a desired output on the output destination printer from being set on the client terminal. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 illustrates an example of a system configuration according to an embodiment described in this specification. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of each device in the embodiment described in this specification. [Diagram 3] FIG. 2 is a diagram illustrating an example of the software configuration of each device in the embodiment described in this specification. [Figure 4]FIG. 4 is a diagram showing an example of a print setting screen in the embodiment described in this specification. [Diagram 5] FIG. 13 illustrates an example of an extended print setting screen in the embodiment described herein. [Figure 6] FIG. 2 illustrates an example of a data structure in accordance with an embodiment described herein. [Figure 7] 1 is a sequence diagram illustrating a process for registering printer information in a cloud print service in an embodiment described in this specification. [Figure 8] 1 is a flowchart illustrating a process when a cloud print service generates a print queue in the embodiment described herein. [Figure 9] FIG. 11 is a sequence diagram showing a process up to executing printing using a cloud print-compatible printer in the first embodiment described in this specification. [Figure 10] FIG. 11 is a sequence diagram showing a process up to printing using a cloud print non-compatible printer in the first embodiment described in this specification. [Figure 11] 11 is a flowchart showing a process for displaying an extended print setting screen in the first embodiment described in this specification. [Figure 12] FIG. 11 is a sequence diagram showing a process up to printing execution using a cloud print-compatible printer in the second embodiment described in this specification. [Figure 13] FIG. 11 is a sequence diagram showing a process up to printing using a cloud print non-compatible printer in the second embodiment described in this specification. [Figure 14] 11 is a flowchart showing a process for displaying an extended print setting screen in the second embodiment described in this specification. [Figure 15] 13 is a flowchart showing a process for displaying an extended print setting screen in the third embodiment described in this specification. [Figure 16] 1 is a diagram showing an example of a sequence for generating a print queue in a client terminal in the embodiment described in this specification. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0012] <Embodiment 1> 1 shows the configuration of a printing system for cloud print in this 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 non-compatible printer 105 are connected via a network 106.

[0013] FIG. 1 illustrates one each of a client terminal 101, a cloud print-compatible printer 104, and a cloud print non-compatible printer 105, but there may be multiple 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 may be a server system composed of multiple information processing devices. By configuring each server with multiple information processing devices, the processing load can be distributed. Also, a single physical server may be configured to internally virtually fulfill the role of each server.

[0015] The network 106 is assumed to be a WAN such as the Internet, but may also be a closed environment such as an in-house LAN.

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

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

[0018] The cloud print server 102 has a role of receiving print data consisting 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 on behalf of the non-cloud print compatible printer 105, and exchanges printer information, print data, etc. In the cloud print proxy server 103, a cloud print proxy 331 and a printer driver 332 are installed.

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

[0021] 2A 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 SSD, and is capable of storing and rewriting 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 loads programs stored in the storage unit 214 into the memory 213 and executes them. The memory 213 is the main storage 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 for communicating with the external network 106, and inputs and outputs digital data to and from external servers, client terminals, and the like via the network 106.

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

[0026] The operation unit 217 is a device for receiving input from a user via a keyboard, mouse, etc. A device having the functions of both the display unit 216 and the operation unit 217, such as a touch panel, may also be used.

[0027] Fig. 2B is a block diagram showing a 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. The description of the storage unit 224, the control unit 221, and the network communication unit 225 is omitted because they are the same as those of the client terminal 101. Note that, although Fig. 2B shows one each of the storage unit 224, the control unit 221, and the network communication unit 225, the configuration may include one or more of each.

[0028] Fig. 2(c) is a block diagram showing a 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 explanations of the display unit 236, the operation unit 237, the storage unit 234, the control unit 231, and the network communication unit 235 are omitted because they are the same as those of the client terminal 101. Fig. 2(c) shows one each of the display unit 236, the operation unit 237, the storage unit 234, the control unit 231, and the network communication unit 235, but there may be one or more of each.

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

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

[0032] The network communication unit 245 is a device that communicates with the external network 106, and mainly serves to receive print data and transmit information about the status of the cloud print-compatible printer 104, such as errors, to an external server or the like.

[0033] The printing unit 248 is a device that performs printing processing by carrying out a series of operations such as paper feeding, printing, and paper ejection on paper prepared in a cassette or tray. The printing method is not particularly limited, and may be electrophotographic or inkjet. Finishing devices such as a duplex unit, stapler, and puncher used when ejecting paper are also included in the printing unit 248.

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

[0035] 2E is a block diagram showing a hardware configuration of the non-cloud print compatible printer 105. The non-cloud print compatible 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 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 of the cloud print-compatible printer 104, and therefore will not be described here.

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

[0038] FIG. 3A 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 extending application 312. The cloud print driver 311 is software for generating print data to be sent to the cloud print server 102. The print setting extending application 312 is an application for extending the functions of the cloud print driver 311, and executes processes such as display control of a print setting screen. The cloud print driver 311 is downloaded by the user from a website provided by a cloud print service 321, and installed in the client terminal 101. The timing at which the print setting extending application 312 is downloaded and installed in 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 generating print jobs and sending print jobs. The print job management unit 31102 generates print data that complies with a protocol supported by the cloud print service 321, and sends the print data as a print job. For example, when the cloud print service transmits and receives print data in accordance with IPP, the print job management unit 31102 generates print data with print settings that comply with IPP. In addition, the print job management unit 31102 generates print data for the file format of image data included in the print data in accordance with a file format (e.g., PDF or PWG-Raster) supported by the cloud print service.

[0043] The UI unit 31103 has a role of displaying a UI prepared by the cloud print driver 311 and accepting user operations from the client terminal 101. The UI unit 31103 displays a print setting screen 1300 shown in FIG. 4A. Objects for performing printing in printing using the cloud print service 321 are arranged on the print setting screen 1300. An area 1301 in FIG. 4A displays information on print queues registered in the cloud print server 102. A button 1302 is a button for displaying a list of print queues registered in the cloud print server 102. A user selects the button 1302 and selects a print queue corresponding to a printer to be used for printing from the displayed print queues. An area 1303 is an area for setting the number of copies to be printed. An area 1304 is an area for setting a color mode. A button 1305 is a button for changing the color mode, and after selecting the button 1305, a user can select a color mode for printing. An advanced settings button 1306 is a button for starting the print setting 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 the present embodiment, the cloud print driver 311 has a UI unit 31103 and displays the print setting screen 1300. The OS of the client terminal 101 or an application installed in the client terminal 101 may have a UI unit and display the print setting screen 1300. In such a case, the area 1301 displays print queues to which the client terminal 101 can directly send print data in addition to print queues registered in the cloud print server 102. When a print queue to which the client terminal 101 can directly send 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 application I / F 31104 processes the exchange of data and commands with the print setting extension application 312 .

[0046] The print setting extension application 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 printer information and print settings set on the print setting 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 a role of passing the print settings set by the print setting extension application 312 to the cloud print driver 311.

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

[0049] The connection mode 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 a cloud print proxy 331. The connection mode determination unit 31203 obtains 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 application UI unit 31205 has a role of displaying a UI prepared by the print setting extending application and accepting a user operation from the client terminal 101. FIG. 5A shows an example of a print setting UI displayed by the extended application UI unit 31205 of the print setting extending application 312. The extended print setting screen 801 is a screen that is displayed when the user selects the detailed setting button 1306 on the print setting screen 1300. The extended print setting screen 801 allows the user to set print settings that cannot be set on the print setting 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 switched between on and off. Off means that no punch holes are made in the paper, and on means that punch holes are made in the paper. The secure print 803 is a function that starts printing by inputting a password set in the print setting extending application 312 to the printer. An area 804 is an area for inputting a password required for printing when using the secure print function. After the user issues a print instruction, the printer will start printing when the same password as that entered in area 804 is entered into the printer. In addition to the above setting items, the extended print setting screen 801 also has areas for setting the output paper size to be used for output, whether or not to perform double-sided printing, and settings related to the stamp function that adds and prints a specified image on the paper. When the user selects the "OK" button, the extended print setting screen 801 is closed and the print setting screen 1300 is displayed.

[0052] In this embodiment, the extended print setting screen 801 displays only the setting items that cannot be set on the print setting screen 1300. The extended print setting screen 801 may also display setting items that can be set on the print setting screen, and the settings of these setting items may be changed.

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

[0054] FIG. 3B is a block diagram showing the software configuration of a cloud print service 321 that operates on the cloud print server 102.

[0055] The account management unit 32101 manages 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 each user's user ID in association with information such as a password required for authentication. Furthermore, the account management unit 32101 manages the user ID in association 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 in response to a registration request from the printer. FIG. 6A shows an example of 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 identifying the hardware configuration of the printer. The tenant ID is identification information of a tenant that can use the device. The printer name is the name of the device notified by the printer. The device configuration information is configuration information of the printer, such as whether a finisher that performs post-processing such as stapling and punching is connected to the printer, and whether a unit for double-sided printing is connected. The capability information is information indicating functions that the printer can execute. The capability information includes information such as whether color printing is possible, whether double-sided printing is possible, information on the position where stapling can be performed, information on available punch holes, and whether a secure print function can be used.

[0057] A print management unit 32103 determines whether or not 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 a print job from an external source and stores the received print job 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 shown in FIG. 6(d). The print queue information includes a print queue name, device configuration information, capability information, connection type information, and a 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 type information is information indicating whether the print queue is a queue that transmits print data to a printer without going 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 a tenant that can use the print queue. The device information shown in FIG. 6(a) and the print queue information shown in FIG. 6(d) are linked with 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 a printer associated with the print queue. For example, the HWID that identifies the printer hardware is registered as the device ID.

[0059] 3C 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] The cloud print proxy 331 further has the following software configuration.

[0061] The cloud print service I / F 33101 processes data and command exchange with the cloud print service 321.

[0062] A print data conversion unit 33102 converts data exchanged between the cloud print service 321 and the printer driver 332 as necessary.

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

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

[0065] The print manager 33201 converts print data including 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 transmits the converted data to the printer.

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

[0067] In addition, the print management unit 33201 manages the capability information of the non-cloud print 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 mutual exchange information that can be interpreted by the cloud print server 102, and is notified to the cloud print server 102. FIG. 6B is a diagram showing an example of mutual exchange information generated by the print data conversion unit 33102. The mutual exchange information includes a proxy ID, a print queue name, device configuration information, and capability information. The proxy ID is identification information of the cloud print proxy 331. The print queue name is the name of the print queue linked to the printer driver 332 on the cloud print proxy server 103. The device configuration information is configuration information of the non-cloud print compatible printer 105 associated with the printer driver 332. The capability information is capability information of the non-cloud print compatible printer 105 associated with the printer driver 332. As described above, when passing through the cloud print proxy server 103, the cloud print server 102 is notified of the proxy ID instead of the device ID.

[0068] 6C 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 FIG. 6C into a format that can be handled by the printer driver 332, and passes it to the printer driver 332.

[0069] FIG. 3D 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 the outside via the network 106, and stores the print data in the storage unit 244 of the cloud print-compatible printer 104. The print data receiving 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, remaining amount of paper, remaining amount of ink / toner, 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 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 data and command exchange with the cloud print service 321.

[0075] FIG. 3E 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 is unable to interpret the print data. In this embodiment, the print data transmitted by the cloud print server 102 is converted by the printer driver of the cloud print proxy server 103 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 the cloud print non-compatible printer 105.

[0077] The device management unit 35102 manages the capability information, remaining amount of paper, and remaining amount of ink / toner of the non-cloud print 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 non-cloud print compatible printer 105, conversion by the cloud print proxy server 103 is required.

[0078] The print output unit 35103 and the UI operation unit 35104 are the same as those of the cloud print-compatible printer 104, and therefore will not be described here.

[0079] Next, an example of a user's procedure for registering the cloud print-compatible printer 104 in the cloud print service 321 in this embodiment and a sequence between each piece of software and service will be described below with reference to FIG. 7B.

[0080] First, the user issues an instruction to register the printer 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 for 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 includes a user ID and a password.

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

[0084] Next, the cloud print service 321 performs authentication processing 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 transmits the token to the cloud print-compatible printer 104 (s926). This token is used the next time the cloud print-compatible printer 104 accesses the cloud print service 321. Note that if the authentication fails in s925, the sequence shown in FIG. 7B ends.

[0085] Next, the cloud print-compatible printer 104 transmits 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 a printer registration process (s928). The printer registration process executed in s928 will be described in detail later.

[0087] Next, after the printer registration process, 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, an example of a user's procedure for registering a non-cloud print compatible printer to the cloud print service in this embodiment and a sequence between each piece of software and service will be described with reference to Fig. 7(a). It is assumed that a printer driver 332 is installed in the cloud print proxy server 103 and a print queue corresponding to the non-cloud print compatible printer 105 is generated. When generating the printer queue, the printer driver 332 communicates with the non-cloud print compatible printer 105 and acquires the printer's hardware ID, model name, device configuration information, and capability information.

[0089] First, the user selects the printer driver 332 for the cloud print non-compatible printer 105 to be connected, using 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, and configurable capability information.

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

[0092] Here, a method of acquiring the printer HWID, which is one of the printer information in this embodiment, will be described. The cloud print proxy 331 calls the OpenPrinter() function of Win32API to acquire the printer handle of the printer driver 332 selected in s901. Next, the GetPrinterDriver() function is called using the acquired printer handle of the printer driver 332 to acquire 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 including information on the printer driver, and specifically, it is filled with 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 acquire the HWID of the printer driver 332 by acquiring the HWID stored in DRIVER_INFO_6.

[0093] In this embodiment, the printer hardware ID is obtained using Win32API, but any means may be used as long as the hardware ID can be obtained.

[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, and indicates that the printer registration has been enabled (s905).

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

[0097] Next, the cloud print proxy 331 displays a login UI for the cloud print service 321 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 is unsuccessful, the process shown in FIG. 7A ends.

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

[0102] Then, the cloud print proxy 331 transmits 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). The printer registration process will be described in detail 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. 8A is a flowchart showing an example of the printer registration process executed by the cloud print service 321 in S914 of FIG. 7A and in S928 of FIG.

[0107] The process shown in FIG. 8A is realized by loading a 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 the program by the CPU 222.

[0108] The process illustrated in FIG. 8A is started when the cloud print service 321 receives 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 mutual exchange 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 mutual exchange 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 print queue information shown in Fig. 6(d) (s403). If 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. If the information received together with the registration request is the mutual exchange information shown in Fig. 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, when the information received together with the registration request includes a device ID, the print queue management unit 32104 determines that the registration request is a registration request from the cloud print-compatible printer 104. 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 non-compatible printer 105. Note that the determination in s404 may be made based on whether the information received together 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 a character string included in the received device ID. When the received device ID includes a specific character string, the device ID is determined to be 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, the device ID is determined to be the device ID of the cloud print-compatible printer 104. Note that the determination in s404 is not limited to the above method as long as it can 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.

[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 "printer direct connection" to the connection type information of the print queue information (s405).

[0114] On the other hand, if the received registration request is a registration request sent by the cloud print non-compatible printer 105, information indicating that the printer connection mode is "connection via cloud print proxy" is set in the print queue information (s406). After the above process, 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 print service 321.

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

[0117] The sequence shown in FIG. 16 is started when the user operates the client terminal 101 and issues an instruction to search for printers registered in the cloud print service 321.

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

[0119] The client terminal 101 transmits a request to obtain a print queue list to the cloud print service 321 (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 logged-in user. The cloud print service 321 then identifies device information registered in association with the identified tenant ID. The cloud print service 321 then makes a list of printer names in the identified device information and transmits the list 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 print service 321 on the display unit 216. When displaying the list of print queues, it is not necessary to display the print queues of printers for which print queues for sending print jobs to the client terminal 101 via the cloud print service have already been created.

[0121] Then, the client terminal 101 accepts from the user a selection of a print queue corresponding to the print queue generated by the client terminal 101. The client terminal 101 transmits an information acquisition request for the selected print queue to the cloud print service 321 (s1608). The cloud print service 321 receives the request to acquire the print queue information and transmits the print queue information of the print queue selected by the user to the client terminal 101 (s1609). The print queue information transmitted here is information as shown in FIG. 6(d). The capability information stores the functions that can be used by the printer linked to the print queue, as well as the HWID of the printer.

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

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

[0124] The printer driver distribution service is a service provided by a server system that the client terminal 101 can access via the network 106. The server system is composed of one or more information processing devices having the same hardware configuration as the cloud print server shown in FIG. 2(b). The printer driver distribution service stores a file in which information about the printer driver and an application for extending the printer driver is described. The file contains, for example, identification information for a print setting extension application for extending a print setting screen. The printer driver distribution service stores the printer driver and the file in association with the printer's HWID.

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

[0126] The application distribution service is a service provided by a server system that the client terminal 101 can access via the network 106. The server system is composed of one or more information processing devices having the same hardware configuration as the cloud print server shown in Fig. 2(b). The application distribution service stores applications and identification information of the applications in association with each other.

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

[0128] The client terminal 101 associates the received application with the generated print queue and stores it (s1615). In this way, when the print setting extended application is called from the print setting screen, the application corresponding to the selected print queue can be started.

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

[0130] Fig. 9 is a diagram showing an example of a sequence showing a process related to print settings and print processing in this embodiment. Fig. 9 shows a sequence in the case where the cloud print-compatible printer 104 is used.

[0131] The user instructs the application to display a print setting screen (s1000). The cloud print driver 311 accepts 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.

[0133] The user operates an area 1301 on a print setting 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 setting screen 1300 (s1003). Here, the cloud print driver 311 updates the print setting screen based on the print queue information acquired in the sequence described in FIG. 16. Information used to update the print setting screen includes, for example, capability information, the name of the print queue, and HWID. It is assumed that the printer linked to the print queue is capable of both color printing and monochrome printing from the selected print queue information. In this case, the cloud print driver 311 displays a print setting screen in which either color or monochrome can be selected in the area 1304 in FIG. 4(a). On the other hand, it is assumed that the printer linked to the print queue is a monochrome printer from the print queue information of the selected print queue. In this case, the cloud print driver 311 displays a print setting screen in which only monochrome can be selected in the area 1304 in FIG. 4(a).

[0135] The user operates the print setting screen 1300 to instruct the print setting extension application 312 to be launched (s1004). When the user selects the detailed settings button 1306 on the print setting screen 1300, the cloud print driver 311 launches the print setting extension application 312 linked to the selected print queue (s1005).

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

[0137] Next, the print setting extending application 312 transmits an acquisition request for print queue information to the cloud print service 321 (s1007). The cloud print service 321 transmits print queue information (FIG. 6(d)) corresponding to the acquisition request received from the print setting extending application 312 to the print setting extending application 312 (s1008). The print setting extending application 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 goes through a cloud printer proxy server (s1009). The print setting extending application 312 displays an extended print setting screen based on the determination (s1010). In FIG. 9, since information indicating a direct printer connection is added to the print queue information in s1009, the print setting extending application 312 displays the UI shown in FIG. 5(a).

[0138] The user operates the print setting extension application 312 to set print settings and selects the "OK" button (s1011). The print setting extension application 312 executes a process for terminating the application (s1012). Then, the print setting extension application 312 transmits the print settings set on the extended print setting screen shown in FIG. 5(a) to the cloud print driver 311 (s1013). The cloud print driver 311 displays the print setting screen shown in FIG. 4 again. The user operates the print setting 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 setting screen 1300 and the print settings received from the print setting extension application 312 in s1013, and transmits the print data 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. Then, the cloud print driver 311 transmits the print 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 transmits a print data acquisition request to the cloud print service 321 (s1016). The acquisition request may be transmitted by a polling process at regular intervals, or may be transmitted when the user logs in to the cloud print-compatible printer 104.

[0140] The cloud print service 321 transmits 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). After that, 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 print setting to printing being executed by the cloud print-compatible printer 104. In Fig. 9, print queue information was acquired in s1007 and s1008, and the connection type determination process was performed. The connection type may be determined based on the print queue information acquired in the process of generating a print queue in the client terminal 101 (Fig. 16). In this case, steps S1007 to s1009 do not need to be performed.

[0142] Next, a printing sequence using the cloud print non-compatible printer 105 will be described with reference to Fig. 10. Note that in Fig. 10, the same reference numerals as in Fig. 9 are used for the steps performing the same processes as in Fig. 9, and the description thereof will be omitted.

[0143] Since steps S1000 to S1009 are the same as those in FIG. 9, the description thereof will be omitted.

[0144] When information indicating that the connection is via a cloud print proxy is added to the print queue information, the print setting extension application 312 displays the screen shown in FIG. 5B (s1400). FIG. 5B shows an example of the print setting UI of the print setting extension application 312. The extended print setting screen 811 displays a warning dialog 812 regarding a post-installation finisher. Even if the printer configuration information of the non-cloud print compatible printer 105 is changed via the cloud print proxy server, 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 register the printer again if the device configuration of the non-cloud print compatible printer 105 has been changed.

[0145] FIG. 5C shows the extended print setting screen 821 displayed after the dialog is closed in FIG. 5B. In the extended print setting screen 821, punch settings and secure print settings cannot be performed. The punch setting is not displayed because the information of a finisher capable of punching is not registered in the device configuration information of the non-cloud print compatible printer 105. There is a possibility that the secure print password included in the print data generated by the cloud print driver 311 is not converted to a format usable by the non-cloud print compatible printer. Therefore, in FIG. 5C, secure print is hidden so that it cannot be set. In this way, FIG. 5C displays an extended print setting screen in which a certain setting item that can be set in FIG. 5A cannot be set, regardless of the printer's capability information and configuration information. In this way, when printing is performed using a non-cloud print compatible printer via the cloud print service 321, output with settings unintended by the user is suppressed. Items that can be set if the printer used is a cloud print compatible printer, but cannot be set if the printer is a non-cloud print compatible printer, include blank paper saving, toner saving, stapleless binding, print area setting, and the like. The blank page save function skips blank pages from the image data when printing. The toner save function saves the amount of toner used for printing. The stapleless binding function binds output papers without using staples. The print area setting function sets the area on the paper where printing will be performed.

[0146] When print data needs to be converted in the cloud print proxy server, the print setting extension application 312 displays an extended print setting screen that prevents setting items that may not be converted by the cloud print proxy server from being set. In this embodiment, by doing as described above, when printing is performed via the cloud print proxy server, it is possible to prevent print settings that cannot be converted by the server from being set.

[0147] 5D is a diagram showing another example of the extended print setting screen displayed by the print setting extension application 312 when a print queue for printing via a cloud print proxy server is selected. Here, the extended print setting screen 831 is a screen displayed after the warning dialogue regarding the post-installation finisher is closed. As shown in area 822, the extended print setting screen 831 allows the user to configure secure print settings. However, a warning message 823 is displayed to the effect that operation is not guaranteed when using the secure print function.

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

[0149] The cloud print proxy 331 periodically transmits a request to obtain print data to the cloud print service 321 (s1401).

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

[0151] Then, the cloud print service 321 transmits 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 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 in s1402. The cloud print proxy 331 performs a process equivalent 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 (s1405) to convert the received print data into rendering data that can be processed by the non-cloud print compatible 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 transmits the generated drawing data to the non-cloud print compatible printer 105 (s1406).

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

[0156] 9 and 10, in s1007, a print queue information acquisition request is sent to the cloud print service, and the connection type is determined based on the print queue information acquired from the cloud print service. At the timing of s1003, the cloud print driver may acquire the print queue information from the cloud print server, and pass the acquired print queue information to the print extension application in s1005. In this case, the print setting extension application executes the connection type determination process based on the connection type information of the print queue information acquired from the cloud print driver.

[0157] Next, the connection determination process described in Fig. 9 and s1009 in Fig. 10 will be described in detail 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 in FIG. 11 starts when the print setting extension application 312 acquires print queue information from the cloud print service 321.

[0159] First, when the print setting expansion application 312 acquires the print queue information, it extracts the information on the printer connection mode that was set when the printer was registered from the print queue information (s501).

[0160] Next, the print setting expanding application 312 determines whether the printer connection mode is a "printer direct 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 extending application 312 displays the extended print setting screen 811 shown in FIG. 5(b) (s504). Then, the print setting extending application 312 determines whether or not the "OK" button in FIG. 5(b) is selected (s505). If the "OK" button is not selected, the print setting extending application 312 repeats the process described in s505. If the "OK" button is selected, the print setting extending application 312 displays the extended print setting screen 831 shown in FIG. 5(c) (s506).

[0163] In addition, when the “OK” button is selected in FIG. 5(b), in order to display the extended print setting screen shown in FIG. 5(d), the print setting extension application 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 going through a cloud print proxy server. If the process detects the information, the screen shown in FIG. 5(a) is displayed, which allows the user to set a secure print password. On the other hand, if the information is not detected in the above detection process, the screen shown in FIG. 5(c) is displayed, which does not allow the user to set a secure print password. This makes it possible to prevent the user from setting a setting item that may not be converted correctly 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, the print setting extension app 312 changes the content displayed on the UI depending on the result of determining the connection form between the cloud print service 321 and the printer, thereby preventing print settings that may not be reflected in the output from being set.

[0166] <Embodiment 2> In the first embodiment, an example of a method has been described in which, when a printer is registered, the cloud print service 321 determines the printer connection mode, adds the connection mode information to the print queue information, and the print setting extension application 312 uses the connection mode information to change the UI.

[0167] In this embodiment, a method will be described in which, when the print setting extending application 312 requests print queue information, the cloud print service 321 acquires ID information from the printer, and the print setting extending application 312 uses the ID information to determine the connection state.

[0168] Here, only the differences from the first embodiment will be explained.

[0169] In the second embodiment, the process shown in FIG. 8(b) is executed instead of the process shown in FIG. 8(a) in the first embodiment.

[0170] The process shown in FIG. 8B is implemented by loading a 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.

[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 the second embodiment, whether the printer to be registered is the cloud print compatible printer 104 or the cloud print incompatible 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 print queue information generated in the second embodiment. The print queue information generated in the second embodiment does not include the connection form information shown in Fig. 6(d), but instead includes ID information. The ID information is empty when the print queue is generated.

[0173] The above is an alternative process to that shown in FIG. 8(a) of the first embodiment.

[0174] Next, a process replacing that of Fig. 9 in the first embodiment will be described with reference to Fig. 12. The same reference numerals are given to the parts that perform the same processes as in Fig. 9, and the parts that differ from the first embodiment will be described.

[0175] When the user selects the detailed settings button on the print setting screen 1300, the print setting extension application 312 is started (s1006). The print setting extension application 312 sends a request to obtain 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 processing is the same as that in FIG.

[0177] If ID information has already been set in the print queue information, the processes from s1109 to s1111 do not need to be performed.

[0178] Next, a process replacing that of Fig. 10 in the first embodiment will be described with reference to Fig. 13. The same reference numerals are given to the parts that perform the same processes as in Fig. 10, and the parts that differ from the first embodiment will be described.

[0179] When the user selects the detailed settings button on the print setting screen 1300, the print setting extension application 312 is started (s1006). The print setting extension application 312 sends a request to obtain 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 non-cloud print compatible 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 called "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] If ID information has already been set in the print queue information, the processes from s1121 to s1124 do not need to be performed.

[0184] 12 and 13, the cloud print service inquired about ID information to the cloud print proxy or the cloud print-compatible printer when the extended print application was launched. The cloud print proxy or the cloud print-compatible printer may be inquired about ID information when a print queue is generated in the cloud print service, and the acquired ID information may be set in the print queue information. In that case, when the print setting extended app is launched, the ID information in the print queue information of the cloud print service is referenced, and no inquiry about ID information is made to the cloud print proxy or the cloud print-compatible printer.

[0185] Using Fig. 14, the process corresponding to s1009 in Fig. 12 and s1009 in Fig. 13 will be described. Each block shown in the flowchart in Fig. 14 is realized by loading a 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 state 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 ID information contains the character string "Proxy", it is determined that additional information is attached, and if the above character string is not included, it is determined that additional information is not attached. Also, 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 no additional information is attached to the ID information, the extended application UI unit 31205 displays the extended print setting screen shown in FIG. 5A (s603).

[0189] If it is determined that the ID information has additional 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 or not the OK button is selected (S605). The process of 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). This ends the process related to the display of the extended print setting screen.

[0192] As described above, the print setting extension application 312 determines the connection form between the cloud print service 321 and the printer by using 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 a cloud print-compatible printer and a cloud print-incompatible printer.

[0193] <Embodiment 3> In the first embodiment, an example of a method has been described in which, when a printer is registered, the cloud print service 321 determines the printer connection mode, adds the connection mode information to the print queue information, and the print setting extension application 312 uses the connection mode information to change the UI.

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

[0195] Here, differences from the first embodiment will be described.

[0196] In the third embodiment, the process shown in Fig. 8(b) is executed instead of Fig. 8(a) in the first embodiment. The process shown in Fig. 8(b) in the third embodiment is different from the process in the second embodiment, and will be described with reference to Fig. 8(b).

[0197] The process shown in FIG. 8B is implemented by loading a 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.

[0198] The device management unit 32102 receives a printer registration request (s411). The printer registration request includes the device information shown in FIG. 6G. In the third embodiment, whether the printer to be registered is the cloud print-compatible printer 104 or the cloud print non-compatible printer 105, information for identifying the printer is stored in the device ID. Also, in the third embodiment, the file format of 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 file formats it supports, but does not notify XPS. On the other hand, the cloud print proxy 331 notifies the cloud print non-compatible printer 105 of XPS as the file format it supports.

[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 print queue information generated in the third embodiment. The print queue information generated in the third embodiment does not include the connection form information shown in Fig. 6(d), but instead includes supported file formats in the capability information.

[0200] In the third embodiment, the sequences of Figs. 9 and 10 are similar to those of the first embodiment, but the details of the connection mode determination process shown in s1009 are different, and will be described with reference to Fig. 15.

[0201] Fig. 15 shows an example of processing of the print setting extending application 312. The processing shown in Fig. 15 is realized by loading a program of the print setting extending 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 determining unit 31203 of the print setting extending application 312 extracts capability information from the print queue information (s701).

[0203] The connection mode determining unit 31203 determines whether or not XPS files are supported based on the supported file format in the extracted capability information (s702).

[0204] If it is determined from the print queue information that XPS files are not supported, the extended application UI unit 31205 of the print setting extended application 312 displays the extended print setting screen shown in FIG. 5A (s703).

[0205] On the other hand, if it is determined from the print queue information that XPS files are supported, the extended application UI unit 31205 displays the screen shown in FIG. 5B (s704).

[0206] The extended application UI unit 31205 determines whether or not the OK button is selected (S705). The process of S705 is repeated until the OK button is selected.

[0207] When the OK button is selected, the extended application UI unit 31205 displays the extended print setting screen shown in Fig. 5C (s706). This ends the process relating to the display of the extended print setting screen.

[0208] As described above, the print setting extension application 312 can determine the connection state 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 a cloud print-compatible printer and a cloud print-incompatible printer.

[0210] <Other embodiments> In the above-described first to third embodiments, when the print queue of the non-cloud print compatible printer 105 is selected on the print setting screen 1300 and the detailed settings button 1306 is selected, the screen shown in Fig. 5(b) is displayed. It is also possible to display the screen shown in Fig. 5(c) or Fig. 5(d) from the print setting screen 1300 without displaying Fig. 5(b).

[0211] The present invention can also be realized by executing the following process. That is, software (programs) that realize the functions of the above-described embodiments are supplied to a system or device via a network or various storage media, and the 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 on which the computer program is stored constitute the present invention.

Claims

1. a selection means for selecting one of printer information from information on a first printer registered in the server system based on a registration request transmitted from the first printer and information on a second printer registered in the server system based on a registration request transmitted from another server system; an information processing apparatus comprising: a display control means for displaying an object that accepts the setting of a setting value for a specified setting item on a display unit based on the selection of information of the first printer by the selection means; and a display control means for not displaying the object on the display unit based on the selection of information of the second printer by the selection means.

2. 2. The information processing apparatus according to claim 1, further comprising a transmitting means for transmitting image data, the information about the first printer, and a setting value set via the object to the server system when a print instruction is given with the information about the first printer selected, and for transmitting the image data and the information about the second printer to the server system when a print instruction is given with the information about the second printer selected.

3. 3. The information processing apparatus according to claim 1, wherein the predetermined setting item is a character string input to the first printer in order for the first printer to start printing based on image data acquired from the server system.

4. The server system generates print data to be transmitted in accordance with IPP; 4. The information processing apparatus according to claim 1, wherein the other server system converts the print data transmitted in accordance with the IPP into a format that can be interpreted by a printer driver installed in the other server system.

5. a storage means for storing information about the first printer and information indicating that the first printer is a printer that receives image data without passing through the other server system in association with each other; 5. The information processing apparatus according to claim 1, further comprising a determination unit that determines whether the first printer is a printer that receives print data via the other server system based on the information stored in the storage unit.

6. 6. The information processing apparatus according to claim 1, wherein the display control means displays both the information about the first printer and the information about the second printer on the display unit without displaying the object.

7. The information processing device according to any one of claims 1 to 6, characterized in that when information about the first printer is selected, the display control means displays the object and other objects for setting other specified setting items, and when information about the second printer is selected, displays the other objects without displaying the object.

8. the second printer is a printer that does not support the print data transmitted by the server system; 8. The information processing apparatus according to claim 1, wherein the other server system is a server system that converts the print data transmitted by the other server system into a format supported by the second printer.

9. 9. The information processing apparatus according to claim 8, wherein the first printer is a printer that supports the print data transmitted by the server system.

10. 10. The information processing apparatus according to claim 1, wherein the other server system is a server system in which information about the second printer is registered.

11. An application for causing an information processing device to display a print setting screen for setting print setting values ​​of print data to be transmitted to a server system that stores information on a first printer registered in the server system based on a registration request transmitted from a first printer to the server system and information on a second printer registered in the server system based on a registration request transmitted from another server system to the server system, the application being executed by the information processing device, a first step of displaying a first object for setting a first setting item and a second object for setting a second setting item when the information of the first printer is selected; and a second step of displaying the second object without displaying the first object for setting a specified setting item when information of the second printer is selected.

12. An application that displays a print setting screen on an information processing device in response to selection of an object for displaying a print setting screen in a state in which information of a printer registered in a server system is selected as information of the printer to which print data is to be transmitted, the application being executed by the information processing device, a determining step of determining whether the selected printer information is information of a printer that receives the print data from another server system that converts the received print data into print data in another format and then transmits the converted data to the printer; and a control step of controlling whether or not to display an object for setting a setting value of a predetermined setting item based on a result of the determination in the determination step.

13. The application according to claim 12, characterized in that the control step displays the object for setting the setting value of the specified setting item when it is determined in the determination step that the printer information is not information of a printer that receives the print data from the other server system, and displays the object when it is determined in the determination step that the printer information is information of a printer that receives the print data from the other server system.

14. An application that displays a print setting screen on an information processing device in response to selection of an object for displaying a print setting screen in a state in which information of a printer registered in a server system is selected as information of the printer to which print data is to be transmitted, the application being executed by the information processing device, a detection step of detecting that the information on the printer is information on a printer that receives print data transmitted by the server system via another server system; and a control step of controlling display of an object for setting a setting value of a predetermined setting item according to a result of the detection step.

15. a registration means for receiving a registration request from a first printer and registering information about the first printer, and for receiving a registration request from another server system for a second printer and registering information about the second printer; a first display control means for causing a display unit to display information about the first printer and information about the second printer registered by the registration means; a second display control means for displaying an object for setting a predetermined setting item on the display unit when the information of the first printer is selected, and for not displaying the object when the information of the second printer is selected; a transmission means for transmitting print data, which is transmitted from an information processing device with information about the first printer specified, to the first printer, and transmitting print data, which is transmitted from the information processing device with information about the second printer specified, to the other server system; a conversion means for converting the print data received by the other server system into a format supported by the second printer; and second transmission means for transmitting the print data converted by the conversion means to the second printer.

16. An application for accepting settings of values ​​for items related to printing, The application is The printer information can be installed in an information processing device that allows the user to select one piece of printer information from a plurality of pieces of printer information including printer information of a first printer registered in a server system based on a registration request transmitted from the first printer and printer information of a second printer registered in the server system based on printer information of the second printer registered in a server different from a server constituting the server system, The information processing device in which the application is installed, functioning as a means for displaying a setting object that accepts setting of values ​​for predetermined items related to printing in response to selection of an instruction object for displaying additional print settings with the printer information of the first printer selected; An application characterized in that even if the instruction object for displaying additional print settings is selected while printer information for the second printer is selected, the setting object is not displayed by the application.

17. An application installed in an information processing device that allows a user to select one piece of printer information from a plurality of pieces of printer information including printer information of a first printer registered in a server system based on a registration request transmitted from the first printer and printer information of a second printer registered in the server system based on printer information of the second printer registered in a server different from a server constituting the server system, the application causes the information processing device to display a setting object that accepts setting of values ​​for predetermined items related to printing in response to a selection of an instruction object for displaying additional print settings with the printer information of the first printer selected; An application characterized in that even if the instruction object for displaying additional print settings is selected while printer information for the second printer is selected, the setting object is not displayed by the application.

18. The application according to claim 16 or 17, characterized in that a server other than a server constituting the server system registers capability information that does not include some capability information related to printing of the second printer in the server system as capability information of the second printer.

19. An application according to any one of claims 16 to 18, characterized in that the capability information of a second printer registered in the server system by a server other than a server constituting the server system does not include capability information for punching processing using a finisher.

20. 20. The application according to claim 16, wherein the setting object is a setting object that accepts a value setting for an item of punch hole setting.

21. 20. The application according to claim 16, wherein the setting object is a setting object that accepts a value setting for an item of stapleless binding setting.

22. 20. The application according to claim 16, wherein the setting object is a setting object that accepts a value setting for a print area setting item.

23. 20. The application according to claim 16, wherein the setting object is a setting object that accepts a value setting for a blank paper saving setting item.

24. 24. The application according to claim 16, wherein the setting object causes the information processing device to perform display based on capability information of a printer registered in the server system.

25. An application according to any one of claims 16 to 24, characterized in that when a print instruction is given with the printer information of the first printer selected, image data and values ​​set via the setting object are transmitted to the server system.

26. 26. The application according to claim 25, wherein when a print instruction is given with printer information of the second printer selected, the application causes the image data to be transmitted to the server system.

27. The server system generates print data to be transmitted in accordance with IPP; An application according to any one of claims 16 to 26, characterized in that a server other than the server constituting the server system converts print data transmitted in accordance with the IPP into a format that can be interpreted by a printer driver installed on a server other than the server constituting the server system.

28. the second printer is a printer that does not support the print data transmitted by the server system; 28. The application according to claim 16, wherein a server different from the servers constituting the server system is a server that converts the print data sent by the server system into a format supported by the second printer.

Images