Image formation device, control method, and program thereof

Abstract

To solve a problem that a cloud printer cannot make detailed print settings, although the printer can set color / black and white, the number of copies, and papers to print.SOLUTION: Printer identification information is added when registering a printer to a cloud service, and, when a user selects the printer registered to the cloud service found by searching on a client terminal, a print setting application is automatically downloaded and installed using the printer identification information registered to the cloud service.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present invention relates to an image forming apparatus, a control method, and a program therefor. [Background technology]

[0002] Cloud printing such as Google Cloud Print is known (Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2013-238924 Summary of the Invention [Problem to be solved by the invention]

[0004] The printing settings that can be made with these cloud printers are limited to color / black and white, number of copies, and paper type; detailed printing settings cannot be made. [Means for solving the problem]

[0005] An information processing device connectable to a server system having a first print queue that manages print jobs sent to an image forming device, a searching means for searching print queues on the server system; a generating means for generating a second print queue in the information processing device, the second print queue managing print jobs to be sent to the first print queue, based on a user's selection of the first print queue found by the search; downloading means for downloading a print setting application for allowing a user to set print options included in the print job based on information associated with the first print queue found by the search; The present invention is characterized by having the following. Effect of the Invention

[0006] According to one of the various inventions described in the embodiment, detailed print settings suitable for an image forming apparatus can be made even in cloud printing using a cloud print service. [Brief description of the drawings]

[0007] [Figure 1] Hardware configuration diagram of the client computer 100 [Diagram 2] Network configuration diagram according to this embodiment [Diagram 3] Functional block diagram of cloud print service 500 [Figure 4] Sequence diagram for registering the printer 200 to the cloud print service 500 [Diagram 5] An example of a printer information database held by the cloud print service 500 [Figure 6] A flowchart showing the process of creating a print queue in the cloud print service 500 and registering printer information in the printer database 510. [Figure 7] An example of device information acquired from a printer in the cloud print service 500 [Figure 8] A sequence diagram for installing the print setting application 1052 on the client computer 100. [Figure 9] 1 is a flowchart showing a process performed by the cloud print service 500 when a print job is received from the client computer 100. [Figure 10] An example of a print job database stored in a print job storage area in the cloud print service 500 [Figure 11] 13 is a flowchart showing a process performed when the cloud print service 500 receives a printable job list request from the printer 200. [Figure 12] An example of a list of print jobs that can be printed by the requesting printer 200 in the cloud print service 500 [Figure 13] An example of an operation panel displaying a list of printable jobs received from the cloud print service 500 [Figure 14] 13 is a flowchart showing a process performed when the cloud print service 500 receives a print execution request from the printer 200. [Figure 15] An example of a UI for changing print settings DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Example 1 Fig. 1 is a hardware configuration diagram of a general computer (information processing device) showing an embodiment of the present invention. It goes without saying that the present invention can be applied to a single function, a system consisting of multiple devices, or a system in which processing is performed by connecting via a network, as long as the functions of the present invention are executed, unless otherwise specified. The client computer 100 is configured with the system shown in Fig. 1. A detailed description is given below.

[0009] The CPU 101 controls the entire device in accordance with a program stored in the ROM 1021 or RAM 1022 of the main storage device 102 or in the auxiliary storage device 105 .

[0010] The RAM 1022 is also used as a work area when the CPU 101 performs various processes. The auxiliary storage device 105 stores an operating system (OS) 1053, an application 1051, a print setting application 1052, etc. In the following description, the main storage device 102 and the auxiliary storage device 105 will be collectively referred to as the storage device.

[0011] Input devices such as a pointing device 109 such as a mouse or touch panel and a keyboard 108 are connected via the input I / F 103 and are devices that allow the user to give various instructions to the computer.

[0012] The output I / F 104 is an interface for outputting data to the outside, and outputs data to an output device such as a monitor 110 .

[0013] The printer 200 is connected through a network 150 via a communication I / F 106. A common data system bus 107 exchanges data between the I / Fs and modules. In addition, the CPU 101 executes processing based on a program stored in a storage device, thereby realizing the processing of steps in a sequence diagram described below.

[0014] 2 is a simplified network configuration diagram of the environment of a network 150 illustrating an embodiment of the present invention. A client computer 100 and a printer 200 are connected to the network 150, and are configured as the same intranet and are capable of communicating with each other. In addition, there are printers 201 and 202 connected to a different intranet, and they are connected via the Internet. A print setting application distribution server 400 is connected to the network 150, and a system capable of providing a print setting application 1052 to the client computer 100 is constructed.

[0015] The cloud print service 500 is an internet cloud print service built on a cloud (i.e., on a server system) that is a server system made up of multiple servers. In this embodiment, it is possible to connect to each intranet, and it is possible to connect to the client computer 100 and the printer 200, printer 201, and printer 202 via the internet.

[0016] The cloud print service 500 manages accounts using a user ID and a password, and a user can use this account to access the cloud print service 500. The user-managed account may be linked to a login user of the operating system 1053. In that case, there is no need to input a user ID or password.

[0017] FIG. 3 is a block diagram of a cloud print service 500 according to an embodiment of the present invention. The cloud print service 500 is a service that exists on a cloud via the Internet and is capable of providing functions related to printing. In this embodiment, the cloud print service 500 has the functions of a printer registration unit 501, a print queue generation unit 502, a printer list generation unit 503, a search response unit 504, and a printer database 510. The cloud print service 500 further has the functions of a print job management unit 505, a print job generation unit 506, and a print job storage area 511. These functions may also be present in another cloud print service that cooperates with the cloud print service 500. Although the printer 200 is described below as an example, the same processing can also be implemented with the printer 201 or the printer 202 that can be connected to the cloud print service 500.

[0018] When a printer registration instruction is received from the printer 200, the printer registration unit 501 causes a print queue generation unit 502 to generate a print queue, and registers the generated print queue in the printer database 510 in association with the printer identification information. When the printer's print queue and printer identification information are registered in this manner, this is referred to as the printer being registered. This process will be described later with reference to the sequence diagram in FIG.

[0019] Furthermore, the print job management unit 505 receives print jobs from the client computer 100 and sends the print jobs directly to the printer 200 depending on the situation. Alternatively, the print job is temporarily stored in the print job storage area 511, and when the output destination printer is determined, the print job is passed to the print job generation unit 506, which converts the print job into an appropriate file and sends the print job. The process of sending or saving a print job will be described later using the flowchart in FIG.

[0020] FIG. 4 is a sequence diagram of a process for registering the printer 200 in the cloud print service 500 according to an embodiment of the present invention.

[0021] The printer 200 is assumed to support a cloud print function (a function for receiving and printing a print job from a cloud print service) and a WebUI function for operating the printer 200. The WebUI function is a function for generating a UI and publishing it on a network. The client computer 100 is assumed to support a cloud print client function (a function for sending files to a cloud print service) and a WebUI client (e.g., a Web browser) for operating the WebUI. Furthermore, the cloud print service 500 represents a cloud print service on the Internet.

[0022] First, the user uses the WebUI client of the client computer 100 to open the WebUI of the printer 200, and selects a button on the WebUI to register the printer in the cloud print service. When this selection is made, the client computer 100 sends a cloud print service registration request 410 to the printer 200. When the printer 200 receives the request 410, it sends a cloud print service registration request 411 to the cloud print service 500. In this manner, in this embodiment, the registration request is sent from the WebUI client of the client computer 100. However, if this request can be sent by operating an input device, such as a panel, associated with the printer 200, the request does not have to be made from the client computer 100. The cloud print service registration request 410 is accompanied by information about the printer 200. The information about the printer 200 includes, for example, the name of the printer 200, a number (HWID) that identifies the printer model, a number (CategoryID) that identifies the printer type, and IP address information. In particular, the number (Category ID) that identifies the type of printer is information for identifying the model defined by the vendor that manufactured the printer.

[0023] When the cloud print service 500 receives the request 411, it causes the print queue generation unit 502 to create (412) a print queue for sending a print job to the printer 200. This print queue is created using the received information about the printer 200, which is the printer name (device name), the HWID that identifies the printer model, the Category ID that identifies the printer type, and the printer's IP address. Then, in flow 413, the information about the printer 200 is registered in the printer database 510. Details of the process of creating a print queue (412) and the process of registering the information about the printer 200 in the printer database 510 will be described later with reference to the flowchart in FIG. 6.

[0024] FIG. 5 is an example of a database 510 of printer information held by the cloud print service 500. The device name refers to the name of the printer (device name) obtained from the printer 200 at the time of registration. The HWID refers to an identifier used to identify the model of the printer 200 (an identifier unique to the model, i.e., identification information unique to the image forming device). The category ID refers to an identifier (common identification information) common to multiple devices. For example, it may be an identifier common to all vendors, or a common identifier may be registered for each type of device, such as a multifunction device or printer, within a vendor. The IP address refers to the IP address of the printer 200 to be connected.

[0025] When registration in the printer database 510 is complete, the cloud print service 500 sends a cloud print service registration request response including a registration URL for cloud print registration and a registration URL presentation request 414 to the printer 200. When the printer 200 receives the cloud print service registration request response and the registration URL presentation request 414, the printer 200 notifies the user of the registration URL information by displaying an associated panel or by printing paper 415 on which the registration URL information is written. The client computer 100 may also be notified via a WebUI.

[0026] The user accesses 416 the client service 500 located at the registration URL presented by the printer 200. At that time, since it is necessary to log in to a cloud account that can access the cloud service 500, it is necessary to input a user ID and a password.

[0027] The cloud print service 500 links the user and the printer 200 from a registration URL including a cloud account and printer information. One method of linking is, for example, linking the printer information with a user token 417. However, the method is not limited to this. Then, the user token 417 including the information of the cloud print service 500 is sent to the printer 200, and the registration process of the printer 200 to the cloud print service 500 is completed. Next, a method of providing a print setting change means suitable for the printer 200 in the client computer 100 will be described later with reference to FIG. 8.

[0028] FIG. 6 is a flowchart of the process in which the cloud service 500 according to the embodiment of the present invention creates a print queue (412 in FIG. 4) and further registers printer information in the printer database 510 (413 in FIG. 4). Unless otherwise specified, this process is performed by each processing unit of the cloud print service 500. This process starts with a registration request (411) from the printer 200 to the cloud print service 500, as described in FIG. 4. First, the print queue generation unit 502 acquires device information from the requesting printer 200 (step S601). This device information acquisition is assumed to be performed by acquiring information from the printer 200 via the network 150 using two-way communication. Furthermore, the contents of the information are assumed to be acquired in an XML-based Schema as shown in FIG. 7 as an example, but needless to say, this is not limited to this. The printer name (device name), HWID, Category ID, and the like described in FIG. 5 are mainly stored in the " <p:deviid>The device information is obtained from the information defined in " " 700. It is checked whether the obtained device information includes a model-specific identifier (HWID) (step S602). Specifically, the " <p:deviid>The determination is made based on whether there is a value defined in "MDL" 701 defined in "" 700. If there is no model-specific identifier (No in step S602), the process proceeds to the next step without creating a print queue. If there is a model-specific identifier (Yes in step 602), a model-specific print queue is created (step S603). Furthermore, the printer information of the model-specific print queue created by the printer registration unit 501 is registered in the printer database 510 (step S604). Since "Can iR-ADV CCCC" in FIG. 5 has a model-specific identifier, it is registered by this process. Next, the print queue generation unit 502 checks whether there is a category identifier (CategoryID) in the device information previously acquired (step S605). Specifically, the " <p:deviid>The printer registration unit 501 determines whether a value defined in the "CID" 702 defined in "Can OIP Common Printer" 700 exists. If there is no category identifier (No in step S605), the print queue creation process and registration process are terminated. If there is a category identifier (Yes in step S605), it is checked whether a print queue common to that category identifier has already been created (step S606). If a print queue common to the category identifier has not already been created (No in step S606), a print queue common to the category is created (step S607). Furthermore, the printer registration unit 501 registers the printer information of the created print queue common to the category in the printer database 510 (step S608). Since the "Can OIP Common Printer" in FIG. 5 does not have a model-specific identifier, it is registered by this process. If a print queue common to the category identifier has already been created (Yes in step S606), only the category identifier common to the model-specific print queue created earlier is additionally registered (step S609).

[0029] FIG. 8 is a sequence diagram of a process for installing the print setting application 1052 in the client computer 100 according to the embodiment of the present invention.

[0030] When outputting to the printer 200 using cloud print, the client computer 100 transmits a print job to the cloud print service 500. Therefore, it is necessary to generate a print queue in the client computer 100 for transmitting the print job to the cloud print service 500.

[0031] In this embodiment, a printer search function that the operating system 1053 has as a standard function is used. Normally, when a printer search is performed, printers on the same intranet are targeted. For example, in FIG. 2, when the client computer 100 performs a printer search, it can find the printer 200, but it cannot find the printers 201 and 202 that are beyond the intranet. However, in this embodiment, the client computer 100 can access the cloud print service 500. Therefore, if a printer is registered in the cloud print service 500, it can find the registered printer by printer search. In this embodiment, it is assumed that the printers 201 and 202 are registered in the cloud print service 500.

[0032] The client computer 100 performs a printer search 810, which is a standard function of the operating system 1053 described above. When the search response unit 504 of the cloud print service 500 receives the information of the printer search 810, it presents available printers to the client computer 100. To this end, the cloud print service 500 creates a printer list 811 that includes information about connectable printers. This printer information includes the above-mentioned printer name (device name), an HWID that identifies the printer model, and an IP address of the printer. The printer list that includes the printer information is created by a printer list generation unit 503 of the cloud print service 500 using information from the printer database 510.

[0033] The cloud print service 500 sends a response 812 of the created printer list to the client computer 100. At this time, the printer information included in the printer list is also sent with HWID information, which is the printer identification information shown in FIG. 5. The client computer 100 presents the user with a selection of available printers based on the printer list. The user selects a model from the presented printer list. Once the selection is made, the operating system 1053 of the client computer 100 creates a print queue for the selected model.

[0034] Furthermore, when the operating system 1053 of the client computer 100 succeeds in generating the print queue, it sends a download request 814 to the print setting application distribution server 400. At that time, the operating system 1053 sends the download request 814 for the print setting application 1052 linked to the HWID, which is the target printer identification information. In this embodiment, in the distribution server 400, the HWID included in the printer information is linked one-to-one to the print setting application 1052. The configuration is such that the corresponding print setting application 1052 is uniquely determined for a specific HWID.

[0035] Furthermore, metadata describing the association between the print setting application 1052 and the HWID included in the printer information may be stored in the distribution server 400. In this case, the appropriate print setting application 1052 is downloaded using the metadata.

[0036] When the print setting application distribution server 400 receives the download request 814, it performs a download process 815 for the client computer 100. That is, it sends a print setting application 1052 to the client computer 100. Then, the client computer 100 performs installation 816 of the print setting application 1052.

[0037] After installation, the print setting application 1052 is associated with the printer 200 on a one-to-one basis. Therefore, by storing model information and print setting information of the printer 200 in the printer 200, it becomes possible to present an appropriate print setting UI to the user. Alternatively, the print setting application 1052 may communicate with the cloud print service 500, acquire target model information and print setting information, and provide a UI using that information. When installation of the print setting application 1052 is complete, the user becomes able to change detailed print settings.

[0038] When a user uses cloud printing, a print instruction is issued from an application 1051 of the client computer 100. As a specific example, print is pressed from the file menu of the application. In normal operation of the application 1051, when a print instruction is received from a user, the application 1051 instructs the OS 1053 to display a print common dialog (a print setting screen provided by the OS). The OS 1053 receives the instruction from the application and displays the print common dialog. The print common dialog displayed by the OS 1053 allows the user to list the printers installed in the client computer 100, specify the pages to be printed, and set the number of copies. The user selects the print queue of the printer to be output from the print common dialog, and issues a print setting change instruction to the print queue by pressing a detailed settings button (object) displayed on the same screen. At that time, the installed print setting application 1052 is started, and a print setting change UI (1500 in FIG. 15) is displayed. As shown in the UI of FIG. 15, various print settings can be changed (of course, it may be configured to allow even more print settings to be changed. For example, image processing settings such as density and color, whether stamp composition is enabled, and settings for punch and staple positions). When the user changes the print settings on the print setting UI and issues a print instruction, the data to be printed is sent to cloud print service 500.

[0039] FIG. 9 is a flowchart of the process performed when the cloud print service 500 receives a print job from the client computer 100. Unless otherwise specified, each processing unit of the cloud print service 500 performs this process. First, a print job is received from the client computer 100 (step S901). The print job management unit 505 acquires print queue information of the sender of the print job (step S902). An example of a method for acquiring print queue information is a method for identifying a print queue from print job information, but is not limited to this. After acquiring the print queue information, it is determined whether the print queue is a print queue for a specific model or a print queue for a common category (step S903). For example, this determination method may be to acquire the corresponding printer information from the printer information list in FIG. 5 and determine whether the acquired printer information has a model-specific identifier (HWID). If the print queue is a model-specific print queue (Yes in step S903), the print job generation unit 506 generates a print job suitable for the destination printer (step S904). Furthermore, upon completion of generation, the print job generation unit 506 sends the generated print job to the specified printer (step S905). If it is a print queue by category (No in step S903), the print job is saved in the print job storage area 511 (step S906). In this case, the print job is not automatically sent to the printer. Only after receiving a request to obtain the print job (i.e., a transmission request) from the printer will the print job be sent to the printer as a response to the transmission request. FIG. 10 is an example of a print job database held in the print job storage area of ​​the cloud print service 500. Here, the print job ID, print job name, and print queue Category ID are registered in association with each other.

[0040] FIG. 11 is a flowchart of the process performed when the cloud print service 500 receives a printable job list request from the printer 200. Unless otherwise specified, this process is performed by each processing unit of the cloud print service 500. First, the printable job list request is received from the printer 200 (step S1101). This printable job list request includes the printer name. The print job management unit 505 that receives the request acquires a category identifier from the printer name (step S1102). In detail, the print job management unit 505 refers to the printer database 510 and acquires a category identifier (CategoryID) associated with the printer name (device name). From the acquired category identifier, the print jobs associated with it are listed (step S1103). In detail, the print job management unit 505 lists the print jobs associated with the category identifier (CategoryID) from the database of the print job storage area 511. Fig. 12 is an example of a list of print jobs that can be printed by the printer 200 that requested the printable job list, by searching for the printable print jobs from the print job database in Fig. 10. The list of print jobs that has been created (for example, the list in Fig. 12) is sent to the printer that requested the print job list (step S1104).

[0041] When the printer 200 receives the sent printable job list, it displays the list of print jobs on the operation panel. FIG. 13 shows an example of an operation panel displaying the printable job list received from the cloud print service 500. The user selects the desired print job from the operation panel and presses the print button to execute printing. Upon receiving the request to execute printing, the printer 200 makes a request to the cloud print service 500 to obtain the print job. Note that this request includes the ID of the print job to be obtained, i.e., the print job ID.

[0042] FIG. 14 is a flowchart of the process performed by the cloud print service 500 according to the embodiment of the present invention when the cloud print service 500 receives a print job acquisition request from the printer 200. Unless otherwise specified, this process is performed by each processing unit of the cloud print service 500. First, a print job acquisition request (including the print job ID of the print job to be output) is received from the printer 200 (step S1401). The print job management unit 505 that receives the request generates a print job suitable for the output destination printer 200 based on the specified print job (step S1402). Once the generation of the print job is complete, the print job is output to the printer 200 that sent the print request (step S1403).

[0043] With the above-mentioned means, it is possible to propose a framework in which a print job is uploaded to the cloud and the image forming device acquires the print job by authenticating to the cloud.

[0044] (Other Examples) 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.< / p:deviid> < / p:deviid> < / p:deviid>

Claims

1. An application executed by an information processing device that creates a print queue for an image forming device corresponding to an image forming device registered in a cloud print service in a server system and acquires an application corresponding to the image forming device, the application causes the information processing device to execute a step of displaying the print setting screen, the print setting screen being displayed when an instruction to open the print setting screen is given in a state in which the created print queue is selected, The application is characterized in that the print settings set via the print setting screen are transmitted to the server system.

2. The application according to claim 1 , wherein identification information of the image forming apparatus is received, the identification information being model information of the image forming apparatus.

3. The application described in claim 1 or 2 is characterized in that the application is acquired by the information processing device and then installed on the information processing device, and causes the information processing device to display the print setting screen when an instruction is given to open the print setting screen with the print queue selected on the information processing device on which the application is installed.

4. The application described in any one of claims 1 to 3, characterized in that the application is acquired by the information processing device and then installed on the information processing device, and is launched by the information processing device when an instruction is given to open the print setting screen with the print queue selected on the information processing device on which the application is installed, causing the information processing device to display the print setting screen.

5. The application described in any one of claims 1 to 4, characterized in that the cloud print service stores a print job including the print settings in a print queue of a registered printing device and transmits the stored print job to the printing device via the Internet.

Images