Image forming apparatus, control method, and program thereof

Abstract

This application provides detailed print settings suitable for image forming machines when using cloud printing services. [Solution] In the server system, an information processing device that acquires applications corresponding to image forming machines registered with the cloud print service executes an application that displays a print settings screen when instructed to open the print settings screen with the created print queue selected, and then sends the configured print settings to the server system.

Description

Technical Field

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

Background Art

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

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Printing settings that can be performed with such cloud printers cannot be detailed in terms of color / black and white, number of copies, and paper type.

Means for Solving the Problems

[0005] The application executed by an information processing apparatus that acquires an application corresponding to an image forming apparatus registered in a cloud print service in a server system, the application being an application that causes the information processing apparatus to execute a step of displaying the print setting screen that is displayed when it is instructed to open the print setting screen with the created print queue selected, and the print settings set via the print setting screen being transmitted to the server system.

Effects of the Invention

[0006] According to one of the various inventions described in the embodiments, detailed print settings suitable for an image forming apparatus are possible even in cloud printing using a cloud print service. [Brief explanation of the drawing]

[0007] [Figure 1] Hardware configuration diagram for client computer 100 [Figure 2] Network configuration diagram in this embodiment [Figure 3] Functional block diagram for Cloud Print Service 500 [Figure 4] Sequence diagram for registering printer 200 with cloud print service 500. [Figure 5] An example of a printer information database maintained by Cloud Print Service 500 [Figure 6] Flowchart diagram 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 obtained from a printer in Cloud Print Service 500. [Figure 8] Sequence diagram for installing the print settings application 1052 on client computer 100. [Figure 9] Flowchart diagram of the process performed by the cloud print service 500 when it receives a print job from client computer 100. [Figure 10] An example of a print job database held in the print job storage area of ​​Cloud Print Service 500. [Figure 11] Flowchart diagram showing the processing when Cloud Print Service 500 receives a printable job list request from printer 200. [Figure 12] An example of a print job list available to the requesting printer 200 in Cloud Print Service 500. [Figure 13] An example of an operation panel displaying a list of printable jobs received from Cloud Print Service 500. [Figure 14]Flowchart diagram of the process when the cloud printing service 500 receives a print execution request from the printer 200 [Figure 15] An example of the UI for changing print settings

Mode for Carrying Out the Invention

[0008] 〔Example 1〕 FIG. 1 is a hardware configuration diagram of a general computer (information processing device) showing an embodiment of the present invention. Unless otherwise specified, as long as the functions of the present invention are executed, whether it is a single function, a system composed of multiple devices, or a system in which connections are made and processing is performed via a network, it is needless to say that the present invention can be applied. The client computer 100 is configured by the system shown in FIG. 1. A detailed description will be given below.

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

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

[0011] Input devices such as a pointing device 109 typified by a mouse or touch panel and a keyboard 108 are connected through the input I / F 103 and are devices for a 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 connection with the printer 200 is made via the communication I / F 106 through the network 150. Also, 107 is a common data system bus for data exchange between the I / Fs and modules. Additionally, by the CPU 101 executing processing based on the programs stored in the storage device, the processing of the steps in the sequence diagram described later is realized.

[0014] FIG. 2 is a network configuration diagram simplifying the environment of the network 150 showing an embodiment of the present invention. The network 150 is connected to a client computer 100 and a printer 200, which are configured in the same intranetwork and are in a communicable state. Also, there are printers 201 and 202 connected to another intranet and connected through the Internet. A print setting application distribution server 400 is connected to the network 150, and a system is constructed that can provide the print setting application 1052 to the client computer 100.

[0015] The cloud print service 500 is an Internet cloud print service constructed on the cloud (i.e., on the server system), which is a server system composed 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, the printer 200, the printer 201, and the printer 202 through the Internet.

[0016] The cloud print service 500 manages accounts using user IDs and passwords, and users can use these accounts to access the cloud print service 500. Also, the user-managed account may be associated with the logged-in user of the operating system 1053. In that case, there is no need to input the user ID or password.

[0017] Figure 3 is a block diagram of a cloud print service 500 illustrating an embodiment of the present invention. The cloud print service 500 is a service located on the cloud via the internet and is capable of providing printing-related functions. In this embodiment, it 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. Furthermore, it 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 located in another cloud print service that works in conjunction with the cloud print service 500. The following description uses printer 200 as an example, but similar processing can be implemented with printers 201 and 202 that can connect to the cloud print service 500.

[0018] When the printer 200 issues a printer registration instruction, the printer registration unit 501 instructs the print queue generation unit 502 to generate a print queue, and then registers the generated print queue in the printer database 510, linked to the printer identification information. This process, where the printer's print queue and printer identification information are linked and registered, is referred to as the printer being registered. This process will be described later using the sequence diagram in Figure 4.

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

[0020] Figure 4 is a sequence diagram of the process of registering a printer 200, which represents an embodiment of the present invention, with a cloud print service 500.

[0021] Printer 200 is assumed to support cloud printing functionality (the ability to receive and print print jobs from a cloud printing service) and WebUI functionality for operating Printer 200. WebUI functionality is the ability to generate a user interface and publish it on the network. Client computer 100 is assumed to support cloud printing client functionality (the ability to send files to the cloud printing service) and WebUI client functionality (e.g., a web browser) for operating the WebUI. Cloud printing service 500 represents a cloud printing service on the internet.

[0022] The user first uses the WebUI client on client computer 100 to open the WebUI of printer 200 and selects a button on the WebUI to register the printer with the cloud print service. Once this selection is made, client computer 100 sends a cloud print service registration request 410 to printer 200. Upon receiving request 410, printer 200 sends a cloud print service registration request 411 to the cloud print service 500. Thus, in this embodiment, the registration request is sent from the WebUI client on client computer 100. However, if the request can be sent by operating an input device attached to printer 200, such as a panel, it is not necessary for the client computer 100 to make the request. The cloud print service registration request 410 is accompanied by information about printer 200. This information includes, for example, the name of printer 200, a number identifying the printer model (HWID), a number identifying the type of printer (CategoryID), and IP address information. In particular, the Category ID, which identifies the type of printer, is information used by the printer manufacturer to identify the model.

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

[0024] Figure 5 shows an example of the printer information database 510 held by the cloud print service 500. The device name refers to the name of the printer (device name) obtained from the printer 200 during registration. The HWID refers to the identifier used to identify the model of the printer 200 (a model-specific identifier, i.e., identification information unique to the image forming apparatus). The CategoryID refers to an identifier common to multiple devices (common identification information). For example, it could be a vendor-common identifier, or a vendor could register common identifiers for each type, such as multifunction devices and printers. The IP address refers to the IP address of the connected printer 200.

[0025] Once registration with the printer database 510 is complete, the cloud print service 500 sends a cloud print service registration request response and a registration URL presentation request 414, which includes a registration URL for cloud print registration, to the printer 200. Upon receiving the cloud print service registration request response and registration URL presentation request 414, the printer 200 notifies the user of the registration URL information via an accompanying panel display or by printing a paper document 415 containing the registration URL information. Alternatively, it may notify the client computer 100 via the WebUI.

[0026] The user accesses the client service 500 located at the registration URL provided by the printer 200. To do so, the user must be logged into a cloud account that allows access to the cloud service 500, and therefore must enter their user ID and password.

[0027] The cloud print service 500 links the user and printer 200 using a registration URL that includes the cloud account and printer information. One method of linking is to link the printer information with the user token 417. However, it is not limited to this method. The user token 417, which includes the information of the cloud print service 500, is then sent to the printer 200, completing the registration process of the printer 200 with the cloud print service 500. Next, a method for providing a means of changing print settings suitable for the printer 200 on the client computer 100 will be described later using Figure 8.

[0028] Figure 6 is a flowchart illustrating the process by which a cloud service 500, representing an embodiment of the present invention, creates a print queue (412 in Figure 4) and then registers printer information in the printer database 510 (413 in Figure 4). Unless otherwise specified, this process is performed by each processing unit of the cloud print service 500. The timing of the start of this process begins with the registration request from the printer 200 to the cloud print service 500 (411), as explained in Figure 4. First, the print queue generation unit 502 obtains device information from the requesting printer 200 (step S601). This device information acquisition is assumed to be performed by obtaining information from the printer 200 using bidirectional communication via the network 150. Furthermore, while it is assumed that the information content will be obtained in an XML-based schema as shown in Figure 7 as an example, it goes without saying that it is not limited to this. The printer name (device name), HWID, CategoryID, etc., as explained in Figure 5, are mainly in the schema shown in Figure 7. <p:deviid>The information is obtained from the information defined in 700. Check whether the obtained device information has a model-specific identifier (HWID) (step S602). Specifically, the schema shown in Figure 7 is <p:deviid>The determination is made based on whether there is a value defined in "MDL" 701, which is defined in "700". If there is no model-specific identifier (No in step S602), the printer 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). "Can iR-ADV CCCC" in Figure 5 has a model-specific identifier, so 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 obtained earlier (step S605). Specifically, the " <p:deviid>The determination is made based on whether there is a value defined in "CID" 702 as defined in "700". 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). "Can OIP Common Printer" in Figure 5 is registered by this process because it does not have a model-specific identifier. If a print queue common to the category identifier has already been created (Yes in step S606), only the category identifier common to the category is added to the previously created model-specific print queue (step S609).

[0029] Figure 8 is a sequence diagram illustrating the process of installing a print settings application 1052 on a client computer 100, which represents an embodiment of the present invention.

[0030] When client computer 100 uses cloud printing to output to printer 200, it sends a print job to cloud printing service 500. Therefore, client computer 100 needs to create a print queue to send the print job to cloud printing service 500.

[0031] In this embodiment, the printer discovery function, which is a standard feature of the operating system 1053, is utilized. Normally, when performing a printer discovery, printers on the same intranet are targeted. For example, in Figure 2, when client computer 100 performs a printer discovery, it can find printer 200, but it cannot find printers 201 and 202 which are located beyond the intranet. However, in this embodiment, client computer 100 has access to the cloud print service 500. Therefore, if the printers are registered with the cloud print service 500, the printer discovery can find the registered printers. In this embodiment, it is assumed that printers 201 and 202 are registered with the cloud print service 500.

[0032] The client computer 100 performs printer discovery 810, a standard function of the operating system 1053 described above. When the discovery response unit 504 of the cloud print service 500 receives the information from printer discovery 810, it presents the client computer 100 with available printers. To do this, the cloud print service 500 creates a printer list 811 that includes information on connectable printers. This printer information includes the printer name (device name), the HWID that identifies the printer model, and the printer's IP address. The printer list containing printer information is created by the 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 to the client computer 100 containing the created printer list. At this time, the printer information included in the printer list also includes the HWID information, which is the printer identification information shown in Figure 5. The client computer 100 then presents the user with a selection of available printers based on the printer list. The user selects a printer model from the presented list. Once the selection is made, the operating system 1053 of the client computer 100 creates a print queue for that model.

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

[0035] Furthermore, the distribution server 400 may store metadata containing the linking information between the print settings application 1052 and the HWID included in the printer information. In that case, the system will use that metadata to download the appropriate print settings application 1052.

[0036] When the print settings application distribution server 400 receives a download request 814, it performs a download process 815 to the client computer 100. That is, it sends the print settings application 1052 to the client computer 100. The client computer 100 then installs the print settings application 1052 816.

[0037] After installation, the print settings application 1052 is linked one-to-one with the printer 200. Therefore, by storing the printer 200's model information and print settings information, it becomes possible to present the user with an appropriate print settings UI. Alternatively, the print settings application 1052 may communicate with the cloud print service 500 to obtain the target model information and print settings information, and use that information to provide the UI. Once the installation of the print settings application 1052 is complete, the user will be able to make detailed print setting changes.

[0038] When a user uses Cloud Print, they issue a print command from application 1051 on client computer 100. For example, they might click Print from the application's File menu. Normally, when application 1051 receives a print command from the user, it instructs OS 1053 to display the print common dialog (the OS-provided print settings screen). OS 1053, upon receiving the instruction from the application, displays the print common dialog. The print common dialog displayed by OS 1053 allows the user to view a list of printers installed on client computer 100, specify the pages to print, and set the number of copies. The user selects the print queue for the desired printer from the print common dialog and clicks the advanced settings button (object) displayed on the same screen to instruct a change in print settings for that print queue. At this point, the installed print settings application 1052 is launched, and the print settings change UI (1500 in Figure 15) is displayed. The UI in Figure 15 allows users to change various print settings as shown in the figure (of course, it could be configured to allow even more print settings, such as image processing settings like density and color, whether or not to enable stamp compositing, and settings for punch and staple positions). When a user changes the print settings on the print settings UI and issues a print command, the data to be printed is sent to the Cloud Print Service 500.

[0039] Figure 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, this process is performed by the various processing units of the cloud print service 500. First, the cloud print service 500 receives the print job from the client computer 100 (step S901). The print job management unit 505 obtains the print queue information of the source of the print job (step S902). One example of how to obtain the print queue information is to identify the print queue from the print job information, but it is not limited to this. Once the print queue information is obtained, it is determined whether the print queue is a model-specific print queue or a category-common print queue (step S903). One way to determine this is, for example, to obtain the relevant printer information from the printer information list in Figure 5 and determine whether there is a model-specific identifier (HWID) in the obtained printer information. 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, once generation is complete, the print job generation unit 506 sends the generated print job to the designated printer (step S905). If it is a category-based print queue (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 from the printer to retrieve a print job (i.e., a transmission request) will the print job be sent to the printer as a response to that transmission request. Figure 10 shows an example of the 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 associated and registered.

[0040] Figure 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 cloud print service 500 receives a printable job list request from the printer 200 (step S1101). This printable job list request includes the printer name. The print job management unit 505, upon receiving the request, obtains a category identifier from the printer name (step S1102). More specifically, the print job management unit 505 refers to the printer database 510 to obtain the category identifier (CategoryID) associated with the printer name (device name). The print jobs associated with the obtained category identifier are listed (step S1103). More specifically, the print job management unit 505 lists the print jobs associated with the category identifier (CategoryID) from the database in the print job storage area 511. Figure 12 is an example of a list of printable jobs that the printer 200 requesting the printable job list has searched for and listed from the print job database in Figure 10. The created list of print jobs (for example, the list in Figure 12) is sent to the requesting printer (step S1104).

[0041] When the printer 200 receives the submitted list of printable jobs, it displays the list of print jobs on its control panel. Figure 13 shows an example of a control panel displaying the list of printable jobs received from the cloud print service 500. The user selects the desired print job from the control panel and presses the print button to execute the print. Upon receiving the print request, the printer 200 sends a request to the cloud print service 500 to retrieve the print job. This request includes the ID of the print job to be retrieved, i.e., the print job ID.

[0042] Figure 14 is a flowchart illustrating the processes performed by the cloud print service 500 when it receives a print job acquisition request from the printer 200, illustrating an embodiment of the present invention. Unless otherwise specified, this process is performed by each processing unit of the cloud print service 500. First, the cloud print service 500 receives a print job acquisition request (including the print job ID of the print job to be output) from the printer 200 (step S1401). The print job management unit 505, upon receiving the request, generates a print job suitable for the 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 made the print request (step S1403).

[0043] Through the above means, it becomes possible to propose a framework in which print jobs are uploaded to the cloud, and the image forming apparatus retrieves the print jobs by authenticating with the cloud.

[0044] (Other examples) The present invention can also be realized by supplying a program that implements one or more of the functions of the above-described embodiments to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be realized by a circuit (e.g., an ASIC) that implements one or more functions.< / p:deviid> < / p:deviid> < / p:deviid>

Claims

1. The application is executed by an information processing device that acquires applications corresponding to image forming apparatuses registered in the cloud print service on the server system, The application is an application that causes the information processing device to perform the step of displaying the print settings screen, which is displayed when the created print queue is selected and the device is instructed to open the print settings screen, An application characterized in that the print settings configured via the print settings screen are sent to the server system.

2. The application according to claim 1, characterized in that it receives identification information of the image forming apparatus, and the identification information is model information of the image forming apparatus.

3. The application according to claim 1 or 2, characterized in that the application is acquired by the information processing device and then installed on the information processing device, and when the information processing device on which the application is installed is instructed to open the print settings screen while the print queue is selected, the information processing device displays the print settings screen.

4. The application described in any one of claims 1 to 3 is characterized in that it is acquired by the information processing device and installed on the information processing device, is started by the information processing device when it is instructed to open the print settings screen with the print queue selected on the information processing device on which the application is installed, and causes the information processing device to display the print settings screen.

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

Images