JP2022089133A - Information processing apparatus and print setting application - Google Patents

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

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

A system is known in which print data is transmitted from a client terminal to a printer via a cloud server. In the above system, the user operates the printer driver installed in the client terminal to set print settings and give print instructions. The printer driver installed on the client terminal sends image data and print data based on print settings to the cloud server. The cloud server can print by sending the received print data to the printer.

In order for the 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, some existing printers do not have a mechanism for interpreting print data transmitted from a cloud server. Patent Document 1 discloses a cloud print system using an existing printer that cannot interpret the print data transmitted by the cloud server by using a proxy server that can interpret the print data transmitted by the cloud server. is doing. 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.

Japanese Unexamined Patent Publication No. 2013-12066

When printing via the cloud server using an existing printer that cannot interpret the print data transmitted by the cloud server, it is necessary to convert the print data by the proxy server. 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.

If the user sets a setting item on the client terminal that the proxy server cannot perform the conversion, the output may be made with the setting not intended by the user.

Therefore, in view of the above problems, it is an object of the present invention to prevent the client terminal from setting print settings that may not obtain a desired output in the output destination printer.

The information processing apparatus described in the present specification goes through a selection means for selecting a print queue to be used from the print queues registered in the server system and another server system that converts the format of print data transmitted by the server system. When the print queue for receiving the print data is selected, a printer that displays a print setting screen in which predetermined setting items can be set and receives the print data via the other server system is displayed. When the toque is selected, the control means for displaying the print setting screen on which the predetermined setting item cannot be set and the print data based on the print setting set via the print setting screen are sent to the server system. It is characterized by having a transmission means for transmitting.

The information processing apparatus according to the present invention can prevent the client terminal from setting print settings that may not produce a desired output in the output destination printer.

It is a figure which shows an example of the system configuration in the embodiment described in this specification. It is a figure which shows an example of the hardware composition of each apparatus in embodiment described in this specification. It is a figure which shows an example of the software composition of each apparatus in the embodiment described in this specification. It is a figure which shows an example of the print setting screen in the embodiment described in this specification. It is a figure which shows an example of the extended print setting screen in the embodiment described in this specification. It is a figure which shows an example of the data structure in the embodiment described in this specification. In the embodiment described in the present specification, it is a sequence diagram which shows the process for registering a printer information in a cloud print service. In the embodiment described in the present specification, it is a flowchart which shows the process when the cloud print service generates a print queue. FIG. 3 is a sequence diagram showing a process up to execution of printing using a cloud print compatible printer in the first embodiment described in the present specification. In Embodiment 1 described in this specification, it is a sequence diagram which shows the process until printing is executed using the printer which does not support cloud print. It is a flowchart which shows the process at the time of displaying the extended print setting screen in Embodiment 1 described in this specification. It is a sequence diagram which shows the process until printing is executed using the cloud print compatible printer in Embodiment 2 described in this specification. In Embodiment 2 described in this specification, it is a sequence diagram which shows the process until printing is executed using the printer which does not support cloud print. It is a flowchart which shows the process at the time of displaying the extended print setting screen in Embodiment 2 described in this specification. It is a flowchart which shows the process at the time of displaying the extended print setting screen in Embodiment 3 described in this specification. In the embodiment described in the present specification, it is a figure which shows an example of the sequence at the time of generating a print queue in a client terminal.

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

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

Although FIG. 1 shows one client terminal 101, one cloud print compatible printer 104, and one cloud print non-compatible printer 105, a plurality of these may be present.

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 distributed. Further, physically, one server may be configured to virtually play the role of each server internally.

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

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

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 the 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 capable of communicating 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 a predetermined protocol. Therefore, when printing via cloud print using the printer 105 that does not support cloud print, the printer 105 that does not support cloud print communicates via the cloud print proxy server 103.

The cloud print server 102 has a 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.

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 printer information and print data. The cloud print proxy 331 and the printer driver 332 are installed in the cloud print proxy server 103.

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

FIG. 2A is a block diagram showing a 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.

The storage unit 214 refers to a non-volatile storage device such as a hard disk or SSD, and can store and rewrite digital data.

The control unit 211 is composed of a CPU 212 and a memory 213, and controls the entire 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 storage memory of the CPU 212 and is used as a work area and a temporary storage area for developing various programs.

The network communication unit 215 is a device that communicates with an external network 106, and inputs / outputs digital data to / from an external server, a client terminal, or the like via the network 106.

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

The operation unit 217 is a device for receiving input from a user using a keyboard, a mouse, or the like. A device having both functions of the display unit 216 and the operation unit 217, such as a touch panel, may be used.

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 explanations 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, and are omitted here. In addition, although FIG. 2B shows one storage unit 224, one control unit 221 and one network communication unit 225, it may be configured to have one or a plurality of each.

FIG. 2C 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 description of the display unit 236, the operation unit 237, the storage unit 234, the control unit 231 and the network communication unit 235 is omitted because they are the same as those of the client terminal 101. In FIG. 2C, the display unit 236, the operation unit 237, the storage unit 234, the control unit 231 and the network communication unit 235 are described one by one, but each of them may be one or a plurality.

FIG. 2D is a block diagram showing a 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 and a network communication unit 245, and a printing unit 248.

The display unit 246 is a device for displaying information in real time to the user, such as a touch panel and an LED provided in the cloud print compatible printer 104.

The operation unit 247 is a device for receiving input from the user, and may include a hard key such as a numeric keypad in addition to the touch panel. Since the storage unit 244 and the control unit 241 are the same as those of the client terminal 101, the description thereof will be omitted. The storage unit 244 and the control unit 241 may have one or a plurality of each.

The network communication unit 245 is a device that communicates with the external network 106, and mainly receives print data and transmits the status of the cloud print compatible printer 104 such as an error to an external server or the like. have.

The printing unit 248 is a device that performs printing processing by performing a series of operations of feeding, printing, and discharging paper prepared in a cassette or a tray. The printing method is not particularly limited, such as an electrophotographic method or an inkjet method. The printing unit 248 also includes a double-sided unit used at the time of paper ejection and a finishing device such as stapling and punching.

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

FIG. 2E is a block diagram showing a hardware configuration of a printer 105 that does not support cloud printing. The cloud print non-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.

The explanations 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 are omitted because they are the same as those of the cloud print compatible printer 104.

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

FIG. 3A is a block diagram showing a software configuration of the client terminal 101.

The client terminal 101 has a cloud print driver 311 and a print setting extension application 312. The cloud print driver 311 is software for generating print data to be transmitted to the cloud print server 102. The print setting expansion application 312 is an application for expanding the functions of the cloud print driver 311 and executes processing such as display control of the print setting screen. The cloud print driver 311 is downloaded by the user from the website provided by the cloud print service 321 and installed on the client terminal 101. The timing at which the print setting expansion application 312 is downloaded and installed on the client terminal 101 will be described later with reference to FIG.

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

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

The print job management unit 31102 performs processing such as generation of a print job and transmission of a print job. The print job management unit 31102 generates print data according 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 sends and receives print data according to IPP, the print setting is set to generate print data according to IPP. Further, as for the file format of the image data included in the print data, the print data is generated according to the file format supported by the cloud print service (for example, PDF or PWG-Raster).

The UI unit 31103 has a role of displaying the UI prepared by the cloud print driver 311 and accepting user operations from the client terminal 101. The UI unit 31103 displays the print setting screen 1300 shown in FIG. 4A. On the print setting screen 1300, an object for printing in printing using the cloud print service 321 is arranged. In the area 1301 of FIG. 4A, the information of 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 used for printing from the displayed print queue. The area 1303 is an area for setting the number of copies to be printed. Area 1304 is an area for setting a color mode. The button 1305 is a button for changing the color mode, and the user can select the color mode at the time of printing after selecting the button 1305. The detailed setting button 1306 is a button for starting the print setting expansion application 312. The print button 1307 is a button for transmitting 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.

In this embodiment, it has been described that 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 the application installed on the client terminal 101 may have a UI unit and display the print setting screen 1300. In such a case, in the area 1301, in addition to the print queue registered in the cloud print server 102, a print queue to which the client terminal 101 can directly transmit print data is 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 with the printer driver corresponding to the selected print queue. The generated print data is sent to the printer without going through the cloud print server 102.

The print setting extension application I / F 31104 processes the exchange of data and commands with the print setting extension application 312.

The print setting extension application 312 further has the following software configuration.

The cloud print service I / F3210 processes data and command exchanges with the cloud print service 321. The cloud print service I / F32011 acquires printer information and print settings set on the print setting screen 1300 from the print extension application I / F31104 of the cloud print driver 311. Further, the cloud print service I / F31201 has a role of passing the print settings set by the print setting extension application 312 to the cloud print driver 311.

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

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.

The extended print setting unit 31204 manages print settings including print settings specific to the printer vendor, which are not supported by the cloud print driver 311.

The extended application UI unit 31205 has a role of displaying a UI prepared by the print setting extended application and accepting a user's operation from the client terminal 101. FIG. 5A shows an example of the print setting UI displayed by the extended application UI unit 31205 of the print setting extended application 312. The extended print setting screen 801 is a screen displayed when the user selects the detailed setting button 1306 on the print setting screen 1300. The extended print setting screen 801 can 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 output paper. When the user selects 802, the punch setting is switched on and off. Off means that the paper is not punched, and on means that the paper is punched. The secure print 803 is a function that starts printing by inputting the password set in the print setting expansion application 312 into the printer. The area 804 is an area for inputting a password required for printing when using the secure print function. After the user gives a print instruction, when the same password as the password entered in the area 804 is input to the printer, the printer starts printing. In addition to the above setting items, the extended print setting screen 801 is set to set the output paper size used for output, set whether to perform double-sided printing, and set the stamp function for printing by adding a predetermined image to the paper. An area is provided. When the user selects the "OK" button, the extended print setting screen 801 is closed and the print setting screen 1300 is displayed.

In the present embodiment, the extended print setting screen 801 displays only the setting items that cannot be set on the print setting screen 1300. It may be possible to display setting items that can be set on the print setting screen on the extended print setting screen 801 and change the settings of those setting items.

The print job management unit 31206 performs processing such as generation of a print job, editing of the print job generated by the cloud print driver 311, and transmission of the print job. The print job management unit 31206 of the print setting expansion application 312 can edit the print job generated by the print job management unit 31102 of the cloud print driver 311.

FIG. 3B is a block diagram showing a software configuration of the cloud print service 321 operating on the cloud print server 102.

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 the user ID of each user in association with information such as a password required for authentication. Further, the account management unit 32101 manages the user ID and the tenant ID to which the user belongs in association with each other.

The device management unit 32102 manages information about the printer 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. 6A is an example of device information registered in the device management unit 32102. The device ID is identification information that identifies the printer, and is, for example, an HWID (HardWaleIntentionification Information) for specifying the hardware configuration of the printer. The tenant ID is the identification information of the tenant who can use the device. The printer name is the name of the device notified by the printer. The device configuration information is printer configuration information, such as whether a finisher for post-processing such as staples and punches is connected to the printer, and whether a unit for double-sided printing is connected to the printer. Capability information is information that indicates a function that the printer can perform. For the ability information, it is possible to use information on whether color printing is possible, whether double-sided printing is possible, position information where staples can be printed, punch hole information that can be used, and the secure print function. Information such as whether or not it can be done is included.

The print management unit 32103 determines whether or not to allow the print job delivery request from the cloud print compatible printer 104 or the cloud print proxy server 103, and manages the delivery of the print job.

The print queue management unit 32104 receives a print job from the outside, and holds 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. 6D. 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 the capability information are the same as the device information in FIG. 6A. The connection form information is information indicating whether the print queue is a queue for transmitting print data to the printer without going through the cloud print proxy server 103 or a queue for transmitting print data to the cloud print proxy server 103. .. The tenant ID is the identification information of the tenant who can use the print queue. The device information shown in FIG. 6A and the print queue information shown in FIG. 6D are associated with the tenant ID as a key. The device ID is the same as the device ID in FIG. 6A, and is information for identifying the printer associated with the print queue. For example, an HWID that identifies the hardware of the printer is registered as a device ID.

FIG. 3C is a block diagram showing a 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.

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

The cloud print service I / F 33101 processes the exchange of data and commands with and from the cloud print service 321.

The print data conversion unit 33102 converts the data exchanged between the cloud print service 321 and the printer driver 332 as necessary.

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

Further, the printer driver 332 has the following software configuration.

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 transmits the print data to the printer.

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.

Further, 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 into mutual exchange information that can be interpreted by the cloud print server 102 by the print data conversion unit 33102 of the cloud print proxy 331, and 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 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 cloud print server 102 is notified of the proxy ID instead of the device ID.

The mutual exchange information shown in FIG. 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 the print setting 1211 and the 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 the information to the printer driver 332.

FIG. 3D is a block diagram showing a software configuration of the device control unit 341 of the cloud print compatible printer 104.

The print data receiving 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 receiving unit 34101 can process print data of a predetermined protocol that can be generated by the cloud print server 102.

The device management unit 34102 manages options, capacity 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.

The print output unit 34103 controls printing on paper.

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.

The cloud print service I / F 34105 processes the exchange of data and commands with and from the cloud print service 321.

FIG. 3 (e) is a block diagram showing a software configuration of the device control unit 351 of the printer 105 that does not support cloud print.

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 by the printer driver of the cloud print proxy server 103. By doing so, printing via the cloud print server 102 is realized by using the printer 105 that does not support cloud print.

The device management unit 35102 manages the capacity information, the remaining amount of paper, and the remaining amount of ink / toner of the printer 105 that does not support cloud printing. 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 printer 105 that does not support cloud print, conversion by the cloud print proxy server 103 is required.

The description of the print output unit 35103 and the UI operation unit 35104 is omitted because they are the same as those of the cloud print compatible printer 104.

Next, using FIG. 7B, a user's procedure regarding registration of the cloud print compatible printer 104 in the cloud print service 321 in the present embodiment and an example of a sequence between each software and service will be described below.

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

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

Next, the user inputs the login information in the login UI (s923). The login information is a user ID or password.

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

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 a token for access and sends the token to the cloud print compatible printer 104 (s926). This token is a token used when the cloud print compatible printer 104 accesses the cloud print service 321 from the next time onward. If authentication fails in s925, the sequence ends as shown in FIG. 7 (b).

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).

The cloud print service 321 performs a printer registration process (s928). Details of the printer registration process executed in s928 will be described later.

Next, the cloud print service 321 returns the registration completion status to the cloud print compatible printer 104 after the printer registration process (s929). Then, the cloud print compatible printer 104 displays the registration completion status on the operation unit 247 (s930).

Next, with reference to FIG. 7A, a user's procedure regarding registration of a printer that does not support cloud print in the cloud print service in the present embodiment and an example of a sequence between each software and service will be described. It is assumed that the printer driver 332 is installed in the cloud print proxy server 103, and a print queue corresponding to the printer 105 that does not support cloud print is generated. The printer driver 332 communicates with the printer 105 that does not support cloud print when generating a printer queue, and acquires the hardware ID, model name, device configuration information, and capability information of the printer.

First, the user selects the printer driver 332 for the printer 105 that does not support cloud print to be connected by the cloud print proxy 331 (s901).

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

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

Here, a method of acquiring the HWID of the printer, 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 printer handle of the acquired printer driver 332 to acquire DRIVER_INFO_6. The structure DRIVER_INFO_6 is generated when the 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, contains information associated with the printer driver such as the printer driver name and the printer driver installation path. This DRIVER_INFO_6 has a value called pszHardwareID, and 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 the DRIVER_INFO_6.

In this embodiment, the hardware ID of the printer is acquired using Win32API, but any means may be used as long as the hardware ID can be acquired.

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

Next, the cloud print proxy 331 activates the printer registration button on the UI and indicates that the printer registration is enabled (s905).

Next, the user presses the printer registration button and instructs the printer registration. (S906).

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

Next, the user inputs the login information in the login UI (s908).

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

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

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

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).

Next, the cloud print service 321 performs a printer registration process (s914). The details of the printer registration process will be described later.

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

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

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 s928 of FIG. 7B.

The process shown in FIG. 8A 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.

The process shown in FIG. 8A is started as a result of the cloud print service 321 receiving a printer registration request from the outside via the network 106.

First, the device management unit 32102 of the cloud print service 321 accepts 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. 6A based on the received device information or the mutual exchange information and the tenant ID corresponding to the logged-in user.

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

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 in the print queue name. When the information received together with the registration request is the mutual exchange information shown in FIG. 6B, the print queue name in the mutual exchange information is used as the print queue name.

The print queue management unit 32104 determines whether or not 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 the 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 the 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. The determination in s404 may be performed based on whether or not the proxy ID is included in the information received 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, if 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. The determination in s404 is limited to the above method as long as it can be determined whether the printer that sent the registration request is a cloud print compatible printer or a cloud print non-compatible printer connected via a proxy server. Not done.

When the received registration request is the registration request transmitted by the cloud print compatible printer 104, the print queue management unit 32104 sets the connection form information of the print queue information with information indicating that the printer is directly connected (s405). ..

On the other hand, when the received registration request is a registration request transmitted by the printer 105 that does not support cloud print, information indicating that the printer connection mode is "connection via cloud print proxy" is set in the print queue information (s406). After the above processing, the cloud print service 321 ends the printer registration processing shown in FIG. 8A.

The above is the procedure and process for registering the printer information in the cloud print service 321.

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

The sequence shown in FIG. 16 is started by the user operating the client terminal 101 and instructing the search for the printer registered in the cloud print service 321.

When the client terminal 101 receives the search instruction of the printer registered in the cloud print service 321, the client terminal 101 transmits an authentication request to the cloud print service 321 (s1604). In s1604, first, the user ID and password or the access token to the cloud print service 321 are transmitted from the client terminal 101 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). When the received authentication result is the authentication success, the client terminal 101 executes the following processing. If the received authentication result is authentication failure, the client terminal 101 does not execute the following processing and ends the sequence shown in FIG.

The client terminal 101 transmits a print queue list acquisition request to the cloud print service 321 (s1606). The cloud print 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 print service 321 specifies the device information registered in association with the specified tenant ID. Then, the cloud print service 321 lists the printer names of the specified device information and transmits the list to the client terminal 101 as a list of print queues (s1607).

The client terminal 101 displays a list of print queues received from the cloud print service 321 on the display unit 216. When displaying the list of print queues, the print queues of printers for which print queues for sending print jobs to the client terminal 101 via the cloud print service may not be displayed.

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 transmits an information acquisition request for the selected print queue to the cloud print service 321 (s1608). The cloud print service 321 receives the print queue information acquisition request 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 the information shown in FIG. 6D. 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.

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

Then, the client terminal 101 transmits a request for acquisition of printer usage information 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 additional information.

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 a plurality of 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 printer driver, a file containing information about an application for extending the printer driver, and the like. In the above file, for example, the identification information of the print setting extension application for expanding the print setting screen is described. The printer driver distribution service stores the printer driver and the above file in association with the HWID of the printer.

The printer driver distribution service identifies the file corresponding to the HWID received from the client terminal 101 and transmits it to the client terminal as additional information (s1612). The client terminal 101 transmits an acquisition request of the print setting extended application identified by the identification information of the application described in the file which is the received additional information to the application distribution service (not shown) (s1613).

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 a plurality of information processing devices having the same hardware configuration as the cloud print server shown in FIG. 2 (b). The application distribution service stores the application and the identification information of the application in association with each other.

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).

The client terminal 101 stores the received application in association with the generated print queue (s1615). By doing so, when calling the print setting extension application from the print setting screen, the application corresponding to the selected print queue can be started.

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 from the external server and expanded.

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

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

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

The user operates the area 1301 of the print setting screen 1300 and selects a print queue corresponding to the printer used for printing (s1002).

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 shown in FIG. The information used for updating the print setting screen is, for example, ability information, the name of the print queue, HWID, and the like. From the selected print queue information, it is assumed that the printer associated with the print queue is a printer capable of both color printing and monochrome printing. At this time, the cloud print driver 311 displays a print setting screen in which either color or monochrome can be selected in the area 1304 of FIG. 4A. On the other hand, from the print queue information of the selected print queue, it is assumed that the printer associated with the print queue is a monochrome printer. At this time, the cloud print driver 311 displays a print setting screen in which only monochrome can be selected in the area 1304 of FIG. 4A.

The user operates the print setting screen 1300 to instruct to start the print setting extension application 312 (s1004). When the user selects the detailed setting button 1306 of the print setting screen 1300, the cloud print driver 311 activates the print setting extension application 312 associated with the selected print queue (s1005).

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

Next, the print setting extension application 312 transmits a print queue information acquisition request to the cloud print service 321 (s1007). The cloud print service 321 transmits the print queue information (FIG. 6 (d)) corresponding to the acquisition request received from the print setting expansion application 312 to the print setting expansion application 312 (s1008). The print setting extension application 312 refers to the connection form information of the received print queue information, and determines whether or not the printer corresponding to the selected print queue is a printer that goes through the cloud printer proxy server (s1009). The print setting expansion application 312 displays the extended print setting screen based on the determination (s1010). In FIG. 9, in s1009, since the information indicating that the printer is directly connected is added to the print queue information, the print setting expansion application 312 displays the UI shown in FIG. 5A.

The user operates the print setting expansion application 312 to set the print setting, and selects the "OK" button (s1011). The print setting extension application 312 executes a process for terminating the application (s1012). Then, the print setting expansion application 312 transmits the print settings set on the extended print setting screen shown in FIG. 5A to the cloud print driver 311 (s1013). The cloud print driver 311 again displays the print setting screen shown in FIG. The user operates the print setting screen 1300 to select a 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 according to IPP and image data in a predetermined format such as PDF and PWG-Raster. Then, the cloud print driver 311 transmits to the cloud print service 321. The cloud print service 321 stores the received print data in association with the designated print queue.

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 polling processing at regular time intervals, or may be triggered by the user logging in to the cloud print compatible printer 104.

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).

The above is the sequence from the print setting to the execution of printing by the cloud print compatible printer 104. In FIG. 9, print queue information was acquired at s1007 and s1008, and the connection form was determined. The connection form may be determined based on the print queue information acquired in the process of generating the print queue on the client terminal 101 (FIG. 16). In this case, S1007 to s1009 need not be performed.

Next, a printing sequence using the cloud print non-compatible printer 105 will be described with reference to FIG. The same reference numerals as those in FIG. 9 are assigned to the parts of FIG. 10 in which the same processing as in FIG. 9 is performed, and the description thereof will be omitted.

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

When the information indicating that the connection is made via the cloud print proxy is added to the print queue information, the print setting extension application 312 displays the screen shown in FIG. 5 (b) (s1400). FIG. 5B shows an example of the print setting UI of the print setting expansion application 312. The extended print setting screen 811 displays a warning dialog 812 regarding the retrofit finisher. Even if the device configuration information of the printer is changed for the printer 105 that does not support cloud print via the cloud print proxy server, the change may not be reflected in the print queue information of the cloud print service 321. Therefore, a warning dialog 812 is displayed, and when the device configuration of the cloud print non-compatible printer 105 is changed, the user is urged to register the printer again.

FIG. 5C is an extended print setting screen 821 displayed after the dialog is closed in FIG. 5B. On the extended print setting screen 821, the punch setting and the secure print setting cannot be performed. The punch setting is not displayed because the information of the finisher that can be punched is not registered in the device configuration information of the printer 105 that does not support cloud printing. The secure print password included in the print data generated by the cloud print driver 311 may not be converted into a format that can be used by a printer that does not support cloud print. Therefore, in FIG. 5C, the secure print is hidden so that it cannot be set. As described above, FIG. 5 (c) displays an extended print setting screen in which predetermined setting items that can be set cannot be set in FIG. 5 (a) regardless of the printer capacity information and configuration information. .. By doing so, when printing using a printer that does not support cloud print via the cloud print service 321, it is possible to suppress output with settings not intended by the user. Items that can be set if the printer to be used is a cloud print compatible printer, and cannot be set if the printer is not cloud print compatible include blank paper saving, toner saving, needleless binding, print area setting, etc. .. Blank page saving is a function that skips blank pages of image data and prints them. Toner saving is a setting for saving the amount of toner used for printing. Needleless binding is a function for binding output paper without using staples. The print area setting is a function for setting an area of paper on which printing is performed.

When it is necessary to convert the print data on the cloud print proxy server, the print setting extension application 312 displays the extended print setting screen that makes it impossible to set the setting items that may not be converted by the cloud print proxy server. .. In the present embodiment, by performing the above, when printing is executed via the cloud print proxy server, it is possible to suppress the setting of print settings that cannot be converted by the server.

FIG. 5D is a diagram showing another example of the extended print setting screen displayed by the print setting extended application 312 when the print queue to be printed via the cloud print proxy server is selected. Here, the extended print setting screen 831 is a screen displayed in after closing the warning dialog regarding the retrofit finisher. As described in the area 822, the secure print can be set on the extended print setting screen 831. However, a warning message 823 indicating that the operation is not guaranteed when the secure print function is used is displayed.

The process described in S1011 to S1015 is the same as in FIG.

The cloud print proxy 331 periodically sends a print data acquisition request to the cloud print service 321 (s1401).

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. When it is determined that the source of the print data acquisition request is the cloud print proxy 331, the cloud print service 321 performs the print data conversion process (s1402). For example, the cloud print service converts the print settings written according to the IPP into Print Ticket, and converts the image data in PDF format into the data in XPS format.

Then, the cloud print service 321 transmits the print data obtained by the conversion of s1402 to the cloud print proxy 331 (s1403). In the present embodiment, the cloud print service 321 converts the print data format 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 processing of s1402. The cloud print proxy 331 executes a process corresponding to s1402 on the received print data.

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

The printer driver 332 executes a conversion process of converting the received print data into drawing data that can be processed by the printer 105 that does not support cloud print (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.

The printer driver 332 transmits the generated drawing data to the printer 105 that does not support cloud printing (s1406).

The printer 105 that does not support cloud printing executes printing based on the received drawing data (s1407).

In FIGS. 9 and 10, in s1007, a print queue information acquisition request was transmitted to the cloud print service, and the connection form was 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 print queue information acquired in s1005 to the print extension application. In this case, the print setting extension application executes the connection form determination process based on the connection form information of the print queue information acquired from the cloud print driver.

Next, the details of the connection determination process described in FIG. 9 and s1009 of FIG. 10 will be described with reference to FIG. The process shown 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.

The flow of FIG. 11 is started when the print setting expansion application 312 acquires the print queue information from the cloud print service 321.

First, when the print setting expansion application 312 acquires the print queue information, it extracts the printer connection form information set at the time of printer registration from the print queue information (s501).

Next, the print setting expansion application 312 determines whether or not the printer connection form is "printer direct connection" (s502).

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

When the determination result is NO, the print setting expansion application 312 displays the extended print setting screen 811 shown in FIG. 5 (b) (s504). Then, the print setting expansion application 312 determines whether or not the "OK" button in FIG. 5B is selected (s505). If the "OK" button is not selected, the print setting extension application 312 repeats the process described in s505. When the "OK" button is selected, the print setting expansion application 312 displays the extended print setting screen 831 shown in FIG. 5 (c) (s506).

When the "OK" button is selected in FIG. 5 (b) and the extended print setting screen shown in FIG. 5 (d) is displayed, the print setting expansion application 312 is in s506 in FIG. 5 (c). FIG. 5 (d) is displayed without.

In this way, in s502, the process of detecting the information indicating that the selected print queue is the queue of the cloud print compatible printer that receives the print data from the cloud print service without going through the cloud print proxy server is performed. .. When the information is detected in the process, the screen shown in FIG. 5A in which the password for secure print can be set is displayed. On the other hand, if the information is not detected by the above detection process, FIG. 5C, in which the secure print password cannot be set, is displayed. By doing so, among the print settings that can be included in the print data generated by the cloud print driver, the user sets the setting items that may not be converted correctly when converting the print data. It can be suppressed.

As described above, the print setting expansion application 312 changes the display content on the UI according to the result of determining the connection form between the cloud print service 321 and the printer, so that the print setting may not be reflected in the output. It is possible to suppress the setting.

<Embodiment 2>
In the first embodiment, when the printer is registered, the cloud print service 321 determines the printer connection form, adds the connection form information to the print queue information, and the print setting expansion application 312 changes the UI using the connection form information. An example of the method was described.

In the present embodiment, when the print setting expansion application 312 requests print queue information, the cloud print service 321 acquires the ID information from the printer, and the print setting expansion application 312 determines the connection state using the ID information. I will explain how to do it.

Here, only the difference from the first embodiment will be described.

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

The process shown in FIG. 8B 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 the program by the CPU 222.

The device management unit 32102 receives the printer registration request (s411). The printer registration request includes the device information shown in FIG. 6 (g). In the second embodiment, the device ID stores information for identifying the printer regardless of whether the printer to be registered is the cloud print compatible printer 104 or the cloud print non-compatible printer 105.

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. 6E is the 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. 6D, but includes ID information. The ID information is empty at the timing when the print queue is generated.

The above is a process that replaces FIG. 8 (a) of the first embodiment.

Subsequently, a process alternative to FIG. 9 of the first embodiment will be described with reference to FIG. The same reference numerals are given to the parts where the same processing as in FIG. 9 is performed, and the parts different from those in the first embodiment will be described.

When the user selects the detailed setting button on the print setting screen 1300, the print setting extension application 312 is activated (s1006). The print setting extension application 312 transmits a print queue information acquisition request to the cloud print service 321 (s1007). The cloud print service 321 transmits an inquiry for ID information to the cloud print compatible printer 104 (s1109). The cloud print compatible printer 104 receives an inquiry for ID information and transmits the printer name to the cloud print service 321 (s1110).

The cloud print service 321 adds the received ID information to the print queue information (s1111). Subsequent processing is the same as in FIG.

If the ID information is already set in the print queue information, the processing described in s1109 to s1111 may not be performed.

Next, a process alternative to FIG. 10 of the first embodiment will be described with reference to FIG. The same reference numerals are given to the parts where the same processing as in FIG. 10 is performed, and the parts different from those in the first embodiment will be described.

When the user selects the detailed setting button on the print setting screen 1300, the print setting extension application 312 is activated (s1006). The print setting extension application 312 transmits a print queue information acquisition request to the cloud print service 321 (s1007). The cloud print service 321 transmits an inquiry for ID information to the cloud print proxy 331 (s1121).

The cloud print proxy 331 generates ID information by adding additional information to the printer name of the printer 105 that does not support cloud print, which is connected via the printer driver 332 (s1122). For example, when the printer name is "Printer-A", the additional information "Proxy" is added to generate the ID information "Printer-A-Proxy".

The cloud print proxy 331 transmits the generated ID information to the cloud print service 321 (s1123).

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

If the ID information is already set in the print queue information, the processing described in s1121 to s1124 may not be performed.

Further, in the sequence shown in FIGS. 12 and 13, when the extended printing application is started, the cloud print service inquires about the ID information from the cloud print proxy or the cloud print compatible printer. The ID information may be inquired from the cloud print proxy or the cloud print compatible printer at the timing of generating the print queue in the cloud print service, and the acquired ID information may be set as 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 the ID information is not inquired to the cloud print proxy or the cloud print compatible printer.

A process corresponding to s1009 in FIG. 12 and s1009 in FIG. 13 will be described with reference to FIG. 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.

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

Then, the connection form determination unit 31203 determines whether or not the ID information has additional information (s602). The connection form determination unit 31203 determines whether or not additional information is attached based on whether or not the ID information includes a specific character string. For example, if the ID information includes the character string "Proxy", it is determined that the additional information is attached, and if the above character string is not included, it is determined that the additional information is not attached. Further, 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.

When it is determined that the ID information does not have additional information, the extended application UI unit 31205 displays the extended print setting screen shown in FIG. 5A (s603).

When it is determined that the ID information includes additional information, the extended application UI unit 31205 displays the screen shown in FIG. 5 (b) (s604).

The extended application UI unit 31205 determines whether or not the OK button is selected (s605). The process described in s605 is repeated until the OK button is selected.

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 completes the process related to the display of the extended print setting screen.

As described above, the print setting expansion application 312 determines the connection form between the cloud print service 321 and the printer by 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 cloud print non-compatible printer.

<Embodiment 3>
In the first embodiment, when the printer is registered, the cloud print service 321 determines the printer connection form, adds the connection form information to the print queue information, and the print setting expansion application 312 changes the UI using the connection form information. An example of the method was described.

In the present embodiment, a method of determining the connection state by using the ability information included in the print queue information acquired from the cloud print service 321 by the print setting expansion application 312 will be described.

Here, the differences from the first embodiment will be described.

In the third embodiment, the process shown in FIG. 8 (b) is executed instead of the process shown in FIG. 8 (a) of the first embodiment. Since the process of FIG. 8 (b) in the third embodiment is different from the process of the second embodiment, it will be described with reference to FIG. 8 (b).

The process shown in FIG. 8B 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 the program by the CPU 222.

The device management unit 32102 receives the printer registration request (s411). The printer registration request includes the device information shown in FIG. 6 (g). In the third embodiment, the device ID stores information for identifying the printer regardless of whether the printer to be registered is the cloud print compatible printer 104 or the cloud print non-compatible printer 105. Further, in the third embodiment, 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 supported file formats, and does not notify XPS. On the other hand, the cloud print proxy 331 notifies XPS as a file format supported by the printer 105 that does not support cloud print.

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) is the 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. 6D, but the ability information includes the support file format.

In the third embodiment, the sequences of FIGS. 9 and 10 are the same as those of the first embodiment, but the details of the connection form determination process shown in s1009 are different, so that the sequence will be described with reference to FIG.

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

First, the connection form determination unit 31203 of the print setting expansion application 312 extracts the ability information from the print queue information (s701).

The connection form determination unit 31203 determines whether or not the XPS file is supported from the support file format of the extracted ability information (s702).

When it is determined from the print queue information that the XPS file is 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).

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

The extended application UI unit 31205 determines whether or not the OK button is selected (s705). The process described in s705 is repeated until the OK button is selected.

When the OK button is selected, the extended application UI unit 31205 displays the extended print setting screen shown in FIG. 5 (c) (s706). This completes the process related to the display of the extended print setting screen.

As described above, the print setting expansion application 312 can determine the connection mode between the cloud print service 321 and the printer by using the ability 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 cloud print non-compatible printer.

<Other embodiments>
In the above-described first to third embodiments, when the print queue of the printer 105 that does not support cloud print is selected on the print setting screen 1300 and the detailed setting button 1306 is selected, the screen shown in FIG. 5B is displayed. did. The screen shown in FIGS. 5 (c) or 5 (d) may be displayed from the print setting screen 1300 without displaying FIG. 5 (b).

The present invention is also realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiment is supplied to the system or device via a network or various storage media, and the computer (or CPU, MPU, etc.) of the system or device reads the program code. This is the process to be executed. In this case, the computer program and the storage medium in which the computer program is stored constitutes the present invention.

Claims (9)

A selection method for selecting the print queue to be used from the print queues registered in the server system,
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, a print setting screen that can set predetermined setting items is displayed. A control means for displaying a print setting screen on which the predetermined setting item cannot be set when a print queue for displaying and receiving the print data via the other server system is selected.
An information processing apparatus comprising: a transmission means for transmitting print data based on print settings set via the print setting screen to the server system. 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. The server system generates print data according to IPP and generates print data.
The information processing apparatus according to claim 1 or 2, wherein the other server system converts print data according to the IPP into a format that can be interpreted by a printer driver installed in the other server. Further having a determination means for determining whether or not the print queue is a print queue of a printer that receives print data via the other server based on the information of the print queue registered in the server system. The information processing apparatus according to any one of claims 1 to 3, wherein the information processing apparatus is characterized. The control means is a screen for selecting a print queue to be used, and displays a screen different from the print setting screen.
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 screens. An application that causes an information processing device to display a print setting screen for print data transmitted to a server system, which is executed by the information processing device.
Predetermined according to the fact that the printer selected as the printer 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. The first step of displaying the print setting screen where setting items can be set, and
Depending on whether the printer selected as the printer used for printing is a printer that receives the print data via the other server system, a print setting screen on which the predetermined setting items cannot be set is displayed. An application characterized by causing the information processing apparatus to execute the second step. The print setting screen is selected according to the selection of the object for displaying the print setting screen in the state where the print data is set to be sent to the server system having the print queue that processes the print data to be sent to the printer. Is an application that displays the information on the information processing device, and is executed by the information processing device.
A determination step of determining whether the print queue is a print queue that sends print data to another server system that changes the received print data to print data of another format and then sends the print data to the printer.
In the determination step, different print setting screens are displayed depending on whether or not the print queue is determined to be a print queue to be transmitted to the printer after changing the print data received by the print queue to print data in another format. An application characterized by having a control process and. The control step sets a predetermined setting item when it is determined in the determination step that the print data received by the print queue is not a print queue to be transmitted to the printer after being changed to print data in another format. When it is determined that the print queue is a print queue that displays a print setting screen that can be printed, changes the print data received by the print queue to print data of another format in the determination step, and then sends the print data to the printer. The application according to claim 7, wherein a print setting screen on which predetermined setting items cannot be set is displayed. Printing to the printer When the button for displaying the print setting screen is pressed while the print data is set to be sent to the server system that has the print queue to process the print data to be sent to the printer. An application that displays a setting screen on an information processing device, which is executed by the information processing device.
Detects information that identifies the print queue as a print queue that converts the received print data to print data in another format and then sends the print data to another server system that sends it to the printer. Detection process and
An application comprising a control step of displaying different print setting screens depending on whether or not the identification information can be detected in the detection step.

Images