Printer, control method for printer and program

Abstract

To enable a secure print via a cloud printing service.SOLUTION: A client terminal 101 is provided with a print setting extension application 312 as an application that extends a function of a printer driver 311 to issue a print job for printing on a printer registered in a cloud print server 102 via the cloud print server 102 that registers the printer based on instructions sent by a user operating the printer side. The print setting extension application 312 issues a print job that requires password input at the printer side for printing as a print job for Cloud Print (S606, S607).SELECTED DRAWING: Figure 11B

Description

[Technical field]

[0001] The present invention relates to a technique for printing via a cloud print service. [Background technology]

[0002] There is a known system in which a printer driver installed in a client terminal is used as printer control software to print to a printer connected to the client terminal. An operating system (hereafter referred to as "OS"), which is the basic software, is installed in the client terminal, and the printer driver is configured according to the specifications defined by the OS. By providing a printer driver that conforms to the OS specifications, a printer vendor can obtain a means of issuing print instructions to the printer.

[0003] However, in recent years, operating systems have begun to provide generic printer drivers and methods for issuing print instructions using industry-standard protocols such as IPP (Internet Printing Protocol). In addition, with the spread of cloud services, printing devices are also equipped with network communication functions, and cloud print services are being provided that allow users to issue print instructions from their terminals via the Internet. When users log in to cloud print services on the Internet from various terminals, they can print to printers registered with the cloud print service. In such an environment, printers that are compatible with cloud print services and printers that are not compatible with cloud print services coexist. For this reason, a method of using a proxy is available as a method for connecting printers that are not compatible with cloud print services to the cloud print service.

[0004] On the other hand, there is a printing format called secure printing, in which the user enters a password into the printer driver when printing, and then prints only when the same password is entered into the printer afterwards. This eliminates the worry of others stealing or looking at the printed documents.

[0005] Patent Document 1 proposes a technique for secure printing using the IPP protocol. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2019-181865 A Summary of the Invention [Problem to be solved by the invention]

[0007] However, the technology in Patent Document 1 is related to communication between an IPP-compatible printer and a client PC, and does not realize secure printing via a cloud print service. Conventional systems have not been able to perform secure printing via a cloud print service.

[0008] The present invention has been made to solve the above-mentioned problems, and an object of the present invention is to provide a mechanism that enables secure printing via a cloud print service. [Means for solving the problem]

[0009] The present invention is an application that extends the functionality of a printer driver to issue a print job to be printed on a printer registered on a cloud print server via a cloud print server that registers the printer based on instructions sent by a user operating the printer, and is characterized in that the application causes a computer on which the printer driver operates to function as an issuing means for issuing a print job that requires the input of a password on the printer side when printing. Effect of the Invention

[0010] According to the present invention, it is possible to perform secure printing via a cloud print service. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a configuration diagram of a cloud print system according to an embodiment of the present invention. [Figure 2A] FIG. 2 is a hardware configuration diagram of each device in the cloud print system. [Figure 2B] FIG. 2 is a hardware configuration diagram of each device in the cloud print system. [Figure 3A] FIG. 2 is a diagram illustrating the software configuration of each device in the cloud print system. [Figure 3B] FIG. 2 is a diagram illustrating the software configuration of each device in the cloud print system. [Figure 4A] 11 is a sequence diagram showing a process for registering printer information of a printer not compatible with cloud printing in a cloud printing service. [Figure 4B] 11 is a sequence diagram showing a process for registering printer information of a cloud print-compatible printer in a cloud print service. [Diagram 5] 11 is a flowchart of a printer registration process by the cloud print service. [Figure 6] FIG. 11 is a sequence diagram from starting the print setting extension app to displaying the print setting extension UI. [Figure 7] A diagram showing an extended print setting UI. [Figure 8] FIG. 13 is a diagram showing the printer UI when performing secure printing. [Figure 9] 10 is a flowchart showing a process in which a printer driver transmits printer information. [Figure 10] 10 is a flowchart showing a process of requesting printer registration to a cloud print service. [Figure 11A] 10 is a flowchart showing a process in which a print setting extension application displays a UI. [Figure 11B] 10 is a flowchart showing a process in which a print setting extension application issues a print job. [Figure 12] 6 is a flowchart showing a process in which a printer driver issues a print job. [Figure 13] 11A and 11B are diagrams showing capability information and a PrintTicket relating to secure printing. [Figure 14] FIG. 11 is a diagram showing capability information and IPP attributes relating to secure printing. [Figure 15] 5A and 5B are diagrams showing data structures of device information and print queue information. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing an example of the configuration of a cloud print system according to an embodiment of the present invention.

[0013] As shown in Fig. 1, 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. Note that, although Fig. 1 shows one each of the client terminal 101, the cloud print-compatible printer 104, and the cloud print non-compatible printer 105, 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. An information processing device operated by a user, such as a PC (personal computer), a tablet computer, or a smartphone, 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.

[0016] The cloud print-compatible printer 104 and the cloud print-incompatible printer 105 are devices that actually print on physical paper. The cloud print-compatible printer 104 and the cloud print-incompatible printer 105 receive print data sent by the cloud print server 102 via the network 106, convert it into image data, and print it.

[0017] 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, the Internet Printing Protocol (IPP). The cloud print non-compatible printer 105 is a printer that cannot communicate using the above-mentioned predetermined protocol. Therefore, when printing is performed using the cloud print non-compatible printer 105 via the cloud print server 102, 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 configured with print settings and drawing data from the client terminal 101 and transmitting the received print data to a cloud print-compatible printer 104 or a cloud print proxy server 103 . The cloud print service 321 runs 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 Figures 2A and 2B. Hereinafter, Figures 2A and 2B will be collectively referred to as "Figure 2."

[0021] FIG. 2A is a block diagram showing an example of the hardware configuration of the client terminal 101. As shown in FIG. The client terminal 101 includes a display unit 216 , an operation unit 217 , an auxiliary storage unit 214 , a control unit 211 , and a network communication unit 215 .

[0022] The auxiliary storage unit 214 refers to a non-volatile storage device such as a hard disk or SSD (solid state drive), and is capable of storing and rewriting digital data. The control unit 211 has a CPU 212 and a memory 213, and controls the overall operation of the client terminal 101. The CPU 212 loads a program stored in the auxiliary storage unit 214 into the memory 213 and executes it. The memory 213 is the main memory of the CPU 212 and is used as a work area and a temporary storage area for loading various programs.

[0023] 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. 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 via a keyboard, a pointing device (for example, a 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.

[0024] FIG. 2B is a block diagram showing an example of the hardware configuration of the cloud print server 102. The cloud print server 102 includes a display unit 226, an operation unit 227, an auxiliary storage unit 224, a control unit 221, and a network communication unit 225. The explanations of the display unit 226, the operation unit 227, the auxiliary storage unit 224, the control unit 221, and the network communication unit 225 are omitted because they are the same as those of the client terminal 101. Note that, although one each of the auxiliary storage unit 224, the control unit 221, and the network communication unit 225 is shown in FIG. 2B, the configuration may include one or more of each.

[0025] FIG. 2C is a block diagram showing an example of the hardware configuration of the cloud print proxy server 103. As shown in FIG. The cloud print proxy server 103 includes a display unit 236, an operation unit 237, an auxiliary storage unit 234, a control unit 231, and a network communication unit 235. Descriptions of the display unit 236, the operation unit 237, the auxiliary 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. In Fig. 2(c), one each of the display unit 236, the operation unit 237, the auxiliary storage unit 234, the control unit 231, and the network communication unit 235 is shown, but there may be one or more of each.

[0026] FIG. 2D is a block diagram showing an example of 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 , an auxiliary storage unit 244 , a control unit 241 , a network communication unit 245 , and a printing unit 248 .

[0027] 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. The operation unit 247 is a device for accepting input from a user, and may include hard keys such as a numeric keypad in addition to a touch panel.

[0028] Description of the auxiliary storage unit 244 and the control unit 241 will be omitted since they are the same as those in the client terminal 101. Note that the configuration may include one or more auxiliary storage units 244 and control units 241. 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.

[0029] 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 to electrophotographic or inkjet printing. Finishing devices such as a duplex unit, stapler, and puncher used when ejecting paper are also included in the printing unit 248.

[0030] 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. However, a multifunction printer (multifunction device) that also has a scanner function and a fax function may be used as the cloud print-compatible printer 104.

[0031] FIG. 2E is a block diagram showing an example of the hardware configuration of the cloud print non-compatible printer 105. The non-cloud print compatible printer 105 includes a display unit 256 , an operation unit 257 , an auxiliary storage unit 254 , a control unit 251 , a network communication unit 255 , and a printing unit 258 . The display unit 256, operation unit 257, auxiliary 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.

[0032] Next, the software configuration of the system of this embodiment will be described with reference to Figures 3A and 3B. Hereinafter, Figures 3A and 3B will be collectively referred to as "Figure 3."

[0033] FIG. 3A is a block diagram showing an example of the software configuration of the client terminal 101. As shown in FIG. The client terminal 101 has, as its software configuration, a cloud print driver 311, a print setting extension application 312, and an OS (Operating System) 313. The CPU 212 of the client terminal 101 loads these pieces of software from the auxiliary storage unit 214 to the memory 213 and executes them, thereby realizing the respective functions of the client terminal 101.

[0034] The cloud print driver 311 is software for generating print data to be sent to the cloud print server 102 . The print setting extension application 312 is an application program (hereinafter, "application") for extending the functions of the cloud print driver 311, and executes processes such as display control of a print setting screen. The OS 313 controls the overall software and hardware of the client terminal 101. Both the cloud print driver 311 and the print setting extension application 312 are installed in the OS 313 and managed.

[0035] The cloud print driver 311 further has the following software configuration. The cloud print service I / F unit 31101 processes the exchange of data and commands with the cloud print service 321.

[0036] The print job management unit 31102 performs processes such as generating a print job and transmitting the print job. The print job management unit 31102 generates print data in accordance with a protocol supported by the cloud print service 321, and transmits the print data as a print job. For example, when transmitting and receiving print data in accordance with IPP, the print job management unit 31102 generates print data with print settings in accordance with IPP. Also, as for the file format of image data included in the print data, the print job management unit 31102 generates print data in accordance with a file format (e.g., PDF or PWG-Raster) supported by the cloud print service. Also, when transmitting and receiving print data in accordance with XPS (XML Paper Specification), for example, the print job management unit 31102 generates print data with print settings as PrintTicket. In this way, the print job management unit 31102 can issue a print job for printing on a printer registered in the cloud print service 321 via the cloud print service 321.

[0037] The UI unit 3103 has a role of displaying a UI (user interface) prepared by the cloud print driver 311 and accepting user operations from the client terminal 101. The print data format management unit 31104 manages the format of the print data output by the cloud print driver 311. Specifically, the print data format management unit 31104 manages whether the print data is output in the IPP format or in the XPS format.

[0038] The print setting extension application 312 further has the following software configuration. The cloud print service I / F unit 31201 processes the exchange of data and commands with the cloud print service 321. The cloud print service I / F unit 31201 acquires printer information and print settings set in the print setting UI from the cloud print driver 311. The cloud print service I / F unit 31201 also has a role of passing print settings set in the print setting extension app 312 to the cloud print driver 311.

[0039] The extended print job management unit 31202 performs processes such as generating print jobs, editing print jobs generated by the print job management unit 31102 of the cloud print driver 311, and transmitting print jobs.

[0040] The extended application UI unit 31203 has a role of displaying a UI prepared by the print setting extended application 312 and accepting user operations from the client terminal 101. Compared with the print settings displayed by the UI unit 31103, the print settings displayed by the extended application UI unit 31203 display additional print settings, such as print settings specific to a printer vendor, according to the printer that performs printing via the cloud print server 102. An example of the print setting extended UI displayed by the print setting extended application 312 will be described later with reference to FIG. 7.

[0041] FIG. 3B is a block diagram showing an example of the software configuration of the cloud print server 102. The cloud print server 102 has, as its software configuration, a cloud print service 321 and an OS 322. The CPU 222 of the cloud print server 102 loads these pieces of software from the auxiliary storage unit 224 to the memory 223 and executes them, thereby realizing the respective functions of the cloud print server 102.

[0042] The cloud print service 321 further includes the following software configuration. 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.

[0043] The device management unit 32102 manages information (device information) about printers already 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. Here, the device information will be described with reference to Fig. 15(a).

[0044] FIG. 15A is a diagram showing an example of device information registered in the device management unit 32102. The device ID is identification information unique to 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 equipment 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 punch holes that can be used, and whether the secure print function can be used.

[0045] We now return to the explanation of FIG. A print job 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.

[0046] The print queue management unit 32104 receives a print job from an external device, and stores the received print job in an area prepared in the auxiliary storage unit 224 of the cloud print server 102. The print queue management unit 32104 manages the print queue information shown in Fig. 15(b). The print queue information will now be described with reference to Fig. 15(b).

[0047] FIG. 15B is a diagram showing an example of device information registered in the device management unit 32102. The print queue information includes a print queue name, device configuration information, capability information, print data format, and tenant ID. The print queue name is a name that can identify the print queue. The device configuration information and capability information are the same as the device information in FIG. 15(a). The print data format indicates the print data format that is optimal for the print job handled by the print queue. In this embodiment, the types of print data format include IPP and XPS, but are not limited to these. The tenant ID is identification information of a tenant that can use the print queue. The device information in FIG. 15(a) and the print queue information in FIG. 15(b) are linked together using the tenant ID as a key.

[0048] We now return to the explanation of FIG. The OS 322 controls the overall software and hardware of the cloud print server 102 .

[0049] FIG. 3C is a block diagram showing an example of the software configuration of the cloud print proxy server 103. The cloud print proxy server 103 has, as its software configuration, a cloud print proxy 331, a printer driver 332, and an OS 333. The CPU 232 of the cloud print proxy server 103 loads these pieces of software from the auxiliary storage unit 234 to the memory 233 and executes them, thereby realizing each function in the cloud print proxy server 103.

[0050] The cloud print proxy 331 further has the following software configuration. The cloud print service I / F unit 33101 processes data and command exchange with the cloud print service 321.

[0051] The UI unit 33102 controls the UI of the cloud print proxy 331. Specifically, the UI unit 33102 controls a UI for displaying a list of printer drivers 332 installed in the cloud print proxy server 103 and registering a printer driver 332 selected therein in the cloud print service 321. The registration of the printer driver 332 will be described later with reference to FIG. The printer driver I / F unit 33103 processes data and commands exchanged with the printer driver 332 .

[0052] The printer driver 332 has the following software configuration. The print job management unit 33201 converts the print data, including the print settings and drawing data, sent from the cloud print proxy 331 into print data written in a PDL that can be processed by the printer, and sends the print data to the printer. Note that PDL is an abbreviation for Page Description Language.

[0053] The UI unit 33202 controls the UI of the printer driver 332. This UI enables the print settings to be edited. The capability response unit 33203 provides the capabilities of the printer driver 332 and the non-cloud print compatible printer 105 to the cloud print proxy 331 .

[0054] The device I / F unit 33204 processes the exchange of data and commands between the printer driver 332 and the non-cloud print compatible printer 105. The OS 333 controls the overall software and hardware of the cloud print proxy server 103 .

[0055] 3(d) is a block diagram showing an example of the software configuration of the device control unit 341 of the cloud print-compatible printer 104. The CPU 242 of the cloud print-compatible printer 104 loads the device control unit 341 as software from the auxiliary storage unit 244 to the memory 243 and executes it, thereby realizing the function of the cloud print-compatible printer 104.

[0056] The print data receiving unit 34101 receives print data transmitted from an external source via the network 106, and stores the print data in the auxiliary 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 the cloud print server 102 can generate.

[0057] The device management unit 34102 manages options connected to the cloud print-compatible printer 104, capability information, remaining amount of paper, remaining amount of ink / toner, and the like. The print output unit 34103 prints 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.

[0058] The capability response unit 34105 transmits print setting capabilities that can be specified by the cloud print-compatible printer 104 when printing to the cloud print service 321 via the cloud print service I / F unit 34106. The cloud print service I / F unit 34106 processes data and command exchange with the cloud print service 321.

[0059] 3(e) is a block diagram showing an example of the software configuration of the device control unit 351 of the non-cloud print compatible printer 105. The CPU 252 of the non-cloud print compatible printer 105 loads the device control unit 351 as software from the auxiliary storage unit 254 to the memory 253 and executes it, thereby realizing the function of the non-cloud print compatible printer 105.

[0060] The print data receiving unit 35101 receives print data from the device I / F unit 33204 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 332 of the cloud print proxy server 103 into a format that can be processed by the print data receiving unit 35101. In this manner, printing via the cloud print server 102 is achieved using the non-cloud print compatible printer 105.

[0061] The device management unit 35102, 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.

[0062] Next, a sequence for registering the non-cloud print compatible printer 105 in the cloud print service 321 will be described with reference to FIG. 4A. 4A is a diagram showing an example of a user's procedure and a sequence between each piece of software and service regarding the registration of the non-cloud print compatible printer 105 to the cloud print service 321. It is assumed that the 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.

[0063] First, the user operates the cloud print proxy 331 to select the printer driver 332 for the cloud print non-compatible printer 105 to be connected, and the cloud print proxy 331 accepts the selection operation (S901).

[0064] Next, the cloud print proxy 331 requests printer information from the printer driver 332 selected in S901 (S902). The printer information includes the printer's hardware ID, model name, device configuration information, and configurable capability information. Next, the printer driver 332 returns the printer information to the cloud print proxy 331 (S903). Next, the cloud print proxy 331 stores the received printer information in association with the printer driver 332 (S904).

[0065] Next, the cloud print proxy 331 enables the printer registration button on the UI, and notifies the user that the printer registration has been enabled (S905). Next, the user presses the printer registration button that has been enabled in S905 above to instruct printer registration, and the registration instruction is accepted by the cloud print proxy 331 (S906).

[0066] Next, the cloud print proxy 331 displays a login UI for the cloud print service 321 on the UI (S907). Next, the user inputs login information into the login UI, and the input is accepted by the cloud print proxy 331 (S908).

[0067] Next, the cloud print proxy 331 transmits an authentication request to the cloud print service 321 together with the login information input in S908 above (S909). Next, the cloud print service 321 performs authentication processing based on the authentication request in S909 (S910). If the authentication in S910 above is successful, the cloud print service 321 issues an access token and returns it to the cloud print proxy 331 (S911). This token is used the next time the cloud print proxy 331 accesses the cloud print service 321. Note that if the authentication in S910 fails, the process shown in FIG. 4A ends.

[0068] Next, the cloud print proxy 331 converts the data format of the printer information stored in S904 above 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. Then, the cloud print proxy 331 transmits a printer registration request to the cloud print service 321 together with the token received in S911 and the converted printer information (S913).

[0069] Next, the cloud print service 321 performs a printer registration process based on the printer registration request in S913 (S914). The printer registration process executed in S914 will be described in detail later. Next, after the printer registration process in S914, the cloud print service 321 returns a registration completion status to the cloud print proxy 331 (S915). Then, the cloud print proxy 331 displays the registration completion status on the UI (S916).

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

[0071] First, the user issues a printer registration instruction to the cloud print-compatible printer 104 from the operation unit 247 thereof, and the cloud print-compatible printer 104 accepts the instruction (S921). Next, the cloud print-compatible printer 104 displays a login UI for the cloud print service 321 on the operation unit 247 that has been instructed to register the printer in S921 (S922).

[0072] Next, the user inputs login information into the login UI displayed in S922 above, and the login information is accepted by the cloud print-compatible printer 104 (S923). The login information includes a user ID and a password. Next, the cloud print-compatible printer 104 transmits the login information entered in S923 above and an authentication request to the cloud print service 321 (S924).

[0073] Next, the cloud print service 321 performs authentication processing based on the login information received together with the authentication request in S924 (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 processing shown in FIG. 4B ends.

[0074] Next, the cloud print-compatible printer 104 transmits a printer registration request to the cloud print service 321 together with the token received in S926 and its own printer information (S927). The cloud print service 321 performs a printer registration process based on the printer registration request received in S927 (S928). The printer registration process executed in S928 will also be described in detail later.

[0075] 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).

[0076] As described above, the cloud print server 102 (cloud print service 321) registers a printer based on an instruction (request) sent by a user operating the printer.

[0077] Next, a description will be given of the printer registration process (S914, S928) by the cloud print service 321. This printer registration process corresponds to the process in which the cloud print service 321 registers a printer in response to a printer registration request. Fig. 5 is a flowchart showing an example of a printer registration process by the cloud print service 321. The process shown in Fig. 5 is realized by loading a program of the cloud print service 321 stored in the auxiliary storage unit 224 of the cloud print server 102 into the memory 223 and executing it by the CPU 222. Note that this process is started as a result of the cloud print service 321 receiving a printer registration request from the outside via the network 106.

[0078] First, the cloud print service 321 accepts a printer registration request (S101), and proceeds to S102. In S102, the cloud print service 321 generates a print queue from the printer information received together with the printer registration request accepted in S101.

[0079] Next, the cloud print service 321 generates print queue information (S103). An example of the print queue information is shown in Fig. 15(b). The print data format in the print queue information is determined to be optimal based on the capability information included in the printer registration request.

[0080] Next, the sequence from the start of the print setting expansion application 312 to the display of the print setting expansion UI will be described with reference to FIG. FIG. 6 is a diagram showing an example of a user's procedure from starting the print setting expansion application 312 to displaying the print setting expansion UI and a sequence between each piece of software and service in this embodiment.

[0081] First, the user issues an instruction to display a print setting UI in an application, and the cloud print driver 311 receives the instruction to display the print setting UI via the application (S1001).

[0082] The cloud print driver 311 displays the print setting UI in response to the print setting UI display instruction received in S1001 (S1002). The user operates the print setting UI displayed in S1002 above to instruct the print setting extension application 312 to be launched (S1003). When the user selects a detailed settings button (not shown) in the print setting UI, the cloud print driver 311 accepts the instruction to launch the print setting extension application 312.

[0083] In response to the instruction to start the print setting expanding application 312 received in S1003, the cloud print driver 311 instructs the print setting expanding application 312 to start up (S1004). In response to this, the print setting expanding application 312 starts up.

[0084] The started print setting extension application 312 transmits a request to obtain print queue information to the cloud print service 321 (S1005). The cloud print service 321 transmits the print queue information (FIG. 15B) corresponding to the acquisition request received from the print setting extending application 312 in S1005 to the print setting extending application 312 (S1006). The print setting expansion application 312 displays the print setting expansion UI as shown in FIG. 7 based on the print queue information (FIG. 15B) acquired in S1006 (S1007).

[0085] FIG. 7 is a diagram showing an example of the print setting expansion UI that the print setting expansion application 312 displays in step S1007 of FIG. The print setting expansion UI 801 is an example of a print setting expansion UI of the print setting expansion application 312 that displays a secure print function and a punch function of a post-installed finisher.

[0086] Reference numeral 802 denotes a UI for setting the punch function, which is one of the print settings of the post-installation finisher. The print setting extension application 312 displays the UI 802 for the punch function only when the capability information acquired from the cloud print service 321 includes the punch function.

[0087] Reference numeral 803 denotes a UI for setting a secure print function, which is one of the print settings. Reference numeral 804 denotes an area for entering a password, which is necessary for the secure print function. The print setting extension application 312 displays the UI 803 for the secure print function and the area 804 for entering a password only when the capability information of the print queue information (FIG. 15(b)) acquired from the cloud print service 321 includes the secure print function.

[0088] When a user issues a print instruction by entering a password in the password input area 804 at the time of printing, the user can output a printed matter by entering the same password on the operation unit 247 of the cloud print-compatible printer 104. Similarly, when printing on the cloud print non-compatible printer 105, the user can output a printed matter by entering the same password on the operation unit 257 of the cloud print non-compatible printer 105.

[0089] 8 is a diagram showing an example of a UI that the UI operation unit 34104 of the cloud print-compatible printer 104 displays on the display unit 246 during secure print printing. Note that the UI that the UI operation unit 35104 of the cloud print non-compatible printer 105 displays on the display unit 256 during secure print printing is also similar, so a description thereof will be omitted here.

[0090] FIG. 8A shows a UI displayed by the UI operation unit 34104 when the user inputs a password in the password input area 804 of the print setting expanding application 312 on the client terminal 101 and issues a print instruction.

[0091] The UI operation unit 34104 displays a secure print screen 805 in response to a user operation. A print job list 806 is displayed on the secure print screen 805, and the name of the document for which the user has issued a print instruction is selectable. The UI operation unit 34104 also displays a delete button 807 and a print button 808. When the delete button 807 is pressed with the name of a document selected in the print job list 806, the print job is deleted by the device control unit 341. Also, when the print button 808 is pressed with the name of a document selected in the print job list 806, the UI operation unit 34104 displays a screen such as that shown in FIG. 8(b).

[0092] FIG. 8B shows an example of a UI that is displayed by the UI operation unit 34104 when the user selects a print job of a document name that the user wants to print from the print job list 806 and presses the print button 808.

[0093] The UI operation unit 34104 displays a password input area 809, a cancel button 810, and a print button 811. The user can print by inputting the same password that was input into the password input area 804 (FIG. 7) of the print setting extension application 312 into the password input area 809 of the cloud print-compatible printer 104 and pressing the print button 811.

[0094] Next, the processing flow relating to the secure print processing in this embodiment will be described with reference to the flowcharts shown in FIGS. 9 is a flowchart illustrating a part of the process when the printer driver 332 transmits printer information to the cloud print proxy 331 in S903 of Fig. 4A. The process shown in Fig. 9 is executed by the CPU 232 after the program of the printer driver 332 stored in the auxiliary storage unit 234 of the cloud print proxy server 103 is loaded into the memory 233.

[0095] First, the printer driver 332 acquires its own capability information using the capability response unit 33203 (S201). The capability information includes print setting capabilities that can be specified from outside the printer driver 332. Next, the printer driver 332 checks whether the capability information acquired in S201 includes a secure print capability (S202). If the secure print capability is not included (No in S202), the printer driver 332 proceeds to the process of S208.

[0096] On the other hand, if secure print capability is included (Yes in S202), the printer driver 332 inserts secure print capability information into the printer information to generate the printer information (S203).

[0097] Next, the printer driver 332 acquires a hash algorithm of a secure print password that the printer driver 332 can receive from an external source (S204). The hash algorithm generally refers to an algorithm name such as MD5, SHA-1, or SHA-2. In a non-cloud print environment, the printer driver 332 uses the UI unit 33202 to prompt the user to enter a password when printing. However, in a cloud print environment such as the present embodiment, the printer driver 332 runs on the cloud print proxy server 103, and therefore cannot display a UI to prompt the user to enter a password. For this reason, the printer driver 332 needs to receive a password from an external source as part of print settings in a print job. The printer driver 332 of the present embodiment can process passwords received from an external source not only in plain text (unencrypted data) but also in hash values ​​(encrypted data). In this way, the hash algorithm of a hash value that can be received as a password is the information acquired in S204.

[0098] Note that the hash algorithm of the hash value that the printer driver can receive must match the hash algorithm of the hash value that the connected non-cloud print compatible printer 105 can receive. If the method of generating the hash value that the non-cloud print compatible printer 105 can receive is not a common hash algorithm, the algorithm name can be any name that can identify the generation method. The processing flow of the printer driver 332 when actually receiving a print job will be described later with reference to FIG. 12.

[0099] Next, the printer driver 332 checks whether the receivable hash algorithm exists (S205). If the receivable hash algorithm exists (Yes in S205), the printer driver 332 advances the process to S206. In S206, printer driver 332 generates printer information by inserting a receivable hash algorithm as capability information. Note that printer driver 332 of this embodiment can also receive passwords without hashing (plain text) even if a receivable hash algorithm exists. Therefore, printer driver 332 also inserts capability information indicating that plain text passwords can be received, and generates printer information (S207).

[0100] On the other hand, if there is no receivable hash algorithm (No in S205), the printer driver 332 generates printer information by inserting capability information indicating that only the plaintext password can be received (S207).

[0101] Finally, the printer driver 332 generates printer information including capability information other than secure printing, and transmits the information to the cloud print proxy 331 (S208). The capability information in the printer information transmitted here will be described with reference to FIG. 13A(a).

[0102] FIG. 13A is a diagram showing an example of the capability information in the printer information transmitted in S208 of FIG. The capability information exemplified in FIG. 13(a) indicates that a secure print specification can be received, and that a password can receive a hash value converted by the SHA-2 (sha2) hash algorithm and plain text.

[0103] As described above, by the printer driver 332 transmitting to the outside world that it is capable of receiving the password as a hash value, the printer driver 332 can be adapted to an environment in which it cannot display a UI, such as the cloud print environment of this embodiment.

[0104] Fig. 10A is a flowchart illustrating a part of the process when the cloud print proxy 331 makes a printer registration request to the cloud print service 321 in S913 of Fig. 4A. The process shown in Fig. 10A is executed by the CPU 232 after the program of the cloud print proxy 331 stored in the auxiliary storage unit 234 of the cloud print proxy server 103 is loaded into the memory 233.

[0105] First, the cloud print proxy 331 connects to the cloud print service 321 using the token information acquired in S911 of FIG. 4A (S301). Next, the cloud print proxy 331 acquires the printer information acquired from the printer driver 332 in S903 of Fig. 4A (S302). This printer information includes the capabilities related to the secure print. Then, the cloud print proxy 331 transmits a printer registration request to the cloud print service 321 together with the printer information acquired in S302 (S303).

[0106] Fig. 10B is a flowchart illustrating a part of the process when the cloud print-compatible printer 104 makes a printer registration request to the cloud print service 321 in S927 of Fig. 4B. The process shown in Fig. 10B is executed by the CPU 242 after the program of the device control unit 341 stored in the auxiliary storage unit 244 of the cloud print-compatible printer 104 is loaded into the memory 243.

[0107] First, the device control unit 341 acquires its own capability information using the capability response unit 34105 (S401). Next, the device control unit 341 checks whether the capability information acquired in S401 includes a secure print capability (S402). If the secure print capability is not included (No in S401), the device control unit 341 proceeds to S408.

[0108] On the other hand, if secure print capability is included (Yes in S402), the device control unit 341 inserts secure print capability information to generate printer information (S403). Next, the device control unit 341 acquires a hash algorithm for a secure print password that the device control unit 341 can receive from an external device (S404). As described above, the hash algorithm may be a general algorithm name, or may be any name that can identify the generation method.

[0109] Next, the device control unit 341 checks whether or not a plaintext password can be received in addition to the password hash value (S405). This is because the administrator setting in the cloud print-compatible printer 104 can disable reception of a plaintext password.

[0110] If the plaintext password can also be received (Yes in S405), the device control section 341 advances the process to S406. In S406, the device control unit 341 generates printer information by inserting capability information indicating that it is capable of receiving a password of a hash value and also a password in plain text as its own capability information, and proceeds to S408.

[0111] On the other hand, if the plaintext password cannot be received (No in S405), the device control section 341 advances the process to S407. In S407, the device control unit 341 generates printer information by inserting capability information that allows reception of only the password of its own capability information hash value, and proceeds to S408.

[0112] In S408, the device control unit 341 connects to the cloud print service 321 using the token information acquired in S926 of FIG. 4B. Next, the device control unit 341 transmits a printer registration request to the cloud print service 321 together with the printer information generated up to this point (S409). The capability information in the printer information transmitted here will be described with reference to FIG.

[0113] FIG. 14A is a diagram showing an example of capability information in the printer information to be transmitted. The capability information exemplified in FIG. 14(a) indicates that a secure print specification can be received, and that only a hash value converted by the SHA-2 (sha2) hash algorithm can be received as a password.

[0114] Fig. 11A is a flowchart illustrating a process in which the print setting extension application 312 displays the print setting extension UI 801 in S1007 of Fig. 6. The process illustrated in Fig. 11A is executed by the CPU 212 after the program of the print setting extension application 312 stored in the auxiliary storage unit 214 of the client terminal 101 is loaded into the memory 213.

[0115] First, the print setting extension application 312 acquires capability information from the print queue information acquired in S1006 of FIG. 6 (S501). Next, the print setting extension application 312 checks whether secure printing is possible by referring to the capability information acquired in S501 (S502). If secure printing is not possible (No in S502), the print setting extension application 312 proceeds to S505 without displaying the secure printing setting UI 803.

[0116] On the other hand, if secure printing is possible (Yes in S502), the print setting extension application 312 advances the process to S503. In S503, the print setting extension application 312 further refers to the capability information and checks whether there is a problem with the format of the password that can be received. For example, when transmission of a password in plain text is prohibited, it is determined that there is a problem if no hash algorithm is specified. In addition, even if a hash algorithm is specified, it is also determined that there is a problem if the print setting extension application 312 does not know the hash algorithm or if it is known that the hash algorithm cannot be generated for some reason.

[0117] If it is determined that there is a problem with the format of the receivable password (No in S503), the print setting extension application 312 advances the process to S505 without displaying the secure print setting UI 803. In this way, even if the print queue has a secure print function, if the print setting extension application 312 cannot process it correctly, the user cannot specify secure print itself.

[0118] On the other hand, if it is determined that there is no problem with the format of the receivable password (Yes in S503), the print setting extension application 312 advances the process to S504. In S504, the print setting extension application 312 displays the secure print setting UI 803 and the password input area 804, and advances the process to S505. In S505, the print setting extension application 312 displays a setting UI other than the secure print setting, and ends the process of this flowchart.

[0119] 11B is a flowchart illustrating a process performed by the print setting extending application 312 when the user specifies print settings and issues a print instruction using the print setting extension UI 801 shown in FIG. 7 on the client terminal 101. The process shown in FIG. 11B is executed by the CPU 212 after the program of the print setting extending application 312 stored in the auxiliary storage unit 214 of the client terminal 101 is loaded into the memory 213.

[0120] First, the print setting extension application 312 checks whether a secure print password has been entered in the password entry field 804 in the print setting in the print setting extension UI 801 (S601).

[0121] If the secure print password has not been entered (No in S601), the print setting extension application 312 advances the process to S608. In S608, the print setting extension application 312 issues a print job without specifying secure printing, and ends the process of this flowchart.

[0122] On the other hand, if a secure print password has been input (Yes in S601), the print setting extension application 312 advances the process to S602. In S602, the print setting expansion application 312 acquires the input secure print password character string.

[0123] Next, the print setting extension application 312 checks whether a transmittable hash algorithm exists (S603). Note that the transmittable hash algorithm is included in the print queue information that the print setting extension application 312 acquired from the cloud print service 321 in S1006 of FIG.

[0124] If a transmittable hash algorithm exists (Yes in S603), the print setting extension application 312 advances the process to S604. In S604, the print setting expansion application 312 converts the password character string acquired in S602 above into a hash value using the hash algorithm, and the process proceeds to S605.

[0125] On the other hand, if there is no hash algorithm that can be transmitted (No in S603), the print setting extension application 312 treats the password acquired in S602 above as the character string (plain text) as it was entered (i.e., does not convert it to a hash value) and proceeds to S605.

[0126] In S605, the print setting expansion application 312 checks the print data format included in the print queue information. If the print data format is XPS (XPS in S605), the print setting expansion application 312 advances the process to S606. In step S606, the print setting extension application 312 embeds the password in a PrintTicket and issues a print job. Examples of the PrintTicket are shown in FIGS.

[0127] FIG. 13B shows an example of a PrintTicket when a print job is issued with a plaintext password. FIG. 13C shows an example of a PrintTicket when a print job is issued using a password that is not in plain text but has been converted using the SHA-2 hash algorithm.

[0128] Returning now to the explanation of FIG. 11B. On the other hand, if the print data format is IPP (XPS in S605), the print setting extension application 312 advances the process to S607. In step S607, the print setting extension application 312 embeds the password in an IPP attribute and issues a print job. Examples of the IPP attribute are shown in FIG.

[0129] FIG. 14B is a diagram showing an example of IPP attributes when a print job is issued with a plaintext password. FIG. 14C is a diagram showing an example of IPP attributes when a print job is issued using a password that is not in plain text but is converted using the SHA-2 hash algorithm.

[0130] In the case of printing to the cloud print-compatible printer 104, the print job issued in FIG. 11B is transmitted to the cloud print-compatible printer 104 via the cloud print service 321. On the other hand, in the case of printing to the cloud print non-compatible printer 105, the print job issued in Fig. 11B is sent to the cloud print proxy 331 via the cloud print service 321. The cloud print proxy 331 acquires the print job at a cloud print service I / F unit, and sends the print job to the printer driver 332 at a printer driver I / F unit. Then, the printer driver 332 receives the print job from the cloud print proxy 331, and sends the print job to the cloud print non-compatible printer 105 (details will be described later with reference to Fig. 12).

[0131] As described above, by using the print setting extension application 312, a print job that requires a password to be entered on the printer side when printing can be issued as a print job to be printed on a printer registered in the cloud print service 321 via the cloud print service 321. This makes it possible to realize secure printing via the cloud print service 321.

[0132] As described above, printers capable of secure printing via the cloud print service 321 are not limited to the cloud print-compatible printer 104 that is directly registered with the cloud print service 321. Secure printing via the cloud print service 321 is also possible with the cloud print-incompatible printer 105 that is indirectly registered with the cloud print service 321 via the cloud print proxy 331 and printer driver 332.

[0133] To achieve this, the printer driver 332 of this embodiment is provided with a new function of receiving print data together with a password required to print the print data from the cloud print proxy 331. Conventionally, there has been no printer driver that receives print data together with a password required to print the print data, as the printer driver 332 does. For this reason, the conventional printer driver has not been able to achieve secure printing via the cloud print service 321 using the cloud print non-compatible printer 105. To solve this problem, the printer driver 332 is newly provided with the above-mentioned new function (the function of receiving print data and a password) and the function of sending the print data and a password to the printer.

[0134] Incidentally, there have been print servers in the past that receive a password along with print data and send it to a printer. However, in this type of print server, the print queue simply passes the received print data and password to the printer, and this is not done by the printer driver. In this embodiment, the printer driver 332 receives the print data and password, converts (generates) the print data into print data that can be processed by the printer 105, and passes the password to the printer 105 along with the converted print data. This configuration is clearly different from the conventional one.

[0135] As described above, secure print passwords include hashed passwords (encrypted passwords) and plaintext passwords (unencrypted passwords). That is, printer driver 332 receives encrypted and unencrypted passwords. If an unencrypted password is received, it is desirable to encrypt it in printer driver 332 before sending it to the printer for highly secure printing. However, a system that encrypts passwords across the board is inconvenient because it means that an encrypted password needs to be further encrypted. To solve this new problem, a new system is required for printer driver 332 of this embodiment. This will be described in detail below.

[0136] 12 is a flowchart showing the process of the printer driver 332 that has acquired a print job. The process shown in FIG. 12 is executed by the CPU 232 after the program of the printer driver 332 stored in the auxiliary storage unit 234 of the cloud print proxy server 103 is loaded into the memory 233.

[0137] First, the printer driver 332 acquires a print job in the print job management section 33201 (S701). Next, the printer driver 332 checks whether or not the print job acquired in S701 has a secure print setting (S702). If the secure print setting is not present (No in S702), the printer driver 332 advances the process to S709. In S709, the printer driver 332 generates a PDL without secure print settings from the print job acquired in S701 above, and advances the process to S710.

[0138] On the other hand, if there is a secure print setting, the printer driver 332 advances the process to S703. In S703, the printer driver 332 checks whether the password in the print job is a hash value or plain text. If it is a hash value (Yes in S703), the printer driver 332 advances the process to S704. In S704, the printer driver 332 checks whether the hash algorithm corresponding to the password is appropriate. If the hash algorithm matches a hash algorithm that can be interpreted by the cloud print non-compatible printer 105, it is determined to be appropriate, and if it does not match, it is determined to be inappropriate.

[0139] If the hash algorithm is appropriate (Yes in S704), the printer driver 332 advances the process to S707. In S707, the printer driver 332 generates a PDL by embedding the hash value of the password as is, and proceeds to S710.

[0140] On the other hand, if the hash algorithm is not appropriate (No in S704), the printer driver 332 advances the process to S706. In S706, the printer driver 332 generates a PDL for an input value error, and proceeds to S710. The PDL for an input value error includes a control command for displaying an error on the cloud print non-compatible printer 105. This allows the user to know that an error has occurred in the print job due to an invalid input value.

[0141] Furthermore, if the password in the print job is not a hash value but is plain text in S703 (No in S703), the printer driver 332 advances the process to S705. In S705, the printer driver 332 converts the password into a hash value using a predetermined hash algorithm, and the process proceeds to S708. In S708, the printer driver 332 embeds the hash value converted in S705 above into the PDL to generate a PDL, and the process proceeds to S710.

[0142] Finally, the printer driver 332 transmits the PDL generated in S706, S707, S708, or S709 to the cloud print non-compatible printer 105 (S710).

[0143] As described above, when the password in the print job received by the printer driver 332 is a hash value, the printer driver 332 transmits the hash value as is to the cloud print non-compatible printer 105. When the password in the print job received by the printer driver 332 is in plain text, the printer driver 332 converts the password into a hash value and transmits the hash value to the cloud print non-compatible printer 105. This configuration makes it possible to use secure printing even in an environment where the printer driver 332 cannot display a UI. That is, the above-mentioned problem is solved, and secure printing via the cloud print service 321 can be performed even on the cloud print non-compatible printer 105. And, instead of transmitting the password in plain text, secure printing can also be performed using a hash algorithm appropriate for passing through the cloud print service. This improves security in the cloud print system.

[0144] As described above, secure printing can be performed via the cloud print server. Furthermore, when performing secure printing via the cloud print server with a non-cloud print compatible printer, the printer driver in the cloud print proxy server can appropriately encrypt the secure print password as necessary. This makes it possible to appropriately perform secure printing via the cloud print server even when printing with a non-cloud print compatible printer.

[0145] In the above embodiment, the print setting extending application 312 acquires a hash algorithm of a password that can be received by the cloud print-compatible printer 104 or the cloud print proxy 331 via the cloud print service 321. However, the print setting extending application 312 may be configured to hash the password using a predetermined hash algorithm without acquiring the hash algorithm via the cloud print service 321.

[0146] It goes without saying that the configurations and contents of the various data described above are not limited to those described above, and the data may have various configurations and contents depending on the application and purpose. Although one embodiment has been described above, the present invention can be embodied, for example, as a system, an apparatus, a method, a program, a storage medium, etc. Specifically, the present invention may be applied to a system composed of multiple devices, or may be applied to an apparatus composed of a single device. Furthermore, any combination of the above-described embodiments is also included in the present invention.

[0147] (Other embodiments) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions. Furthermore, the present invention may be applied to a system made up of a plurality of devices, or to an apparatus made up of a single device. The present invention is not limited to the above-mentioned embodiment, and various modifications (including organic combinations of the embodiments) are possible based on the spirit of the present invention, and are not excluded from the scope of the present invention. In other words, the present invention includes all configurations that combine the above-mentioned embodiments and their modifications. [Explanation of symbols]

[0148] 101 Client terminals 311 Cloud Print Driver 312 Print setting extension app 102 Cloud Print Server 103 Cloud Print Proxy Server 331 Cloud Print Proxy 332 Printer Driver 104 Cloud Print Compatible Printers 105 Printer not compatible with Cloud Print

Claims

1. An application that extends the function of a printer driver for issuing a print job to be printed on a printer registered on a cloud print server via a cloud print server that registers the printer based on an instruction sent by a user operating the printer side, As the print job, an issuing means for issuing a print job that requires input of a password on the printer side when printing is provided. An application for functioning the computer on which the printer driver runs.

2. further causing the computer to function as a providing means for providing a user interface for accepting input of the password; 2. The application according to claim 1, wherein said issuing means issues said print job using said input password when said password is input via said user interface.

3. 3. The application according to claim 2, wherein said issuing means issues said print job by encrypting said password.

4. An acquisition unit for acquiring an algorithm for encrypting the password from the cloud print server, 4. The application according to claim 3, wherein the issuing means encrypts the password using the algorithm acquired by the acquiring means.

5. 5. The application according to claim 4, wherein the algorithm acquired by the acquisition unit is transmitted from the registered printer to the cloud print server.

6. A printer driver for transmitting print data to a printer, a receiving means for receiving the print data together with a password required for printing the print data; a transmission means for transmitting to the printer the password together with print data that can be processed by the printer based on the print data received by the reception means; Printer drivers allow your computer to function.

7. 7. The printer driver according to claim 6, wherein, when the password received by the receiving means is an encrypted password, the transmitting means transmits the password to the printer without further encrypting it.

8. 8. The printer driver according to claim 7, wherein said transmitting means, when the password received by said receiving means is an unencrypted password, encrypts the password and transmits it to said printer.

9. the computer is a computer on which a program runs to communicate with a print server using a predetermined protocol and receive the print data and the password; 9. The printer driver according to claim 6, wherein the receiving means receives the print data and the password from the program.

10. 6. An information processing device in which the application according to claim 1 is installed.

11. 10. An information processing device in which the printer driver according to claim 6 is installed.

Images