Information processing apparatus, printing apparatus, control method for the information processing apparatus, and program

Abstract

To install an application on an information processing device used by a user without the user searching for the application corresponding to a printing device registered with a cloud print service.SOLUTION: An information processing device according to the present specification can communicate with a first server system that receives a registration request transmitted by a printing device that has accepted operation to register information with the first server system. The information processing device includes: identifying means for identifying application identification information corresponding to model information on the printing device; acquisition means for acquiring an application of the identified application identification information from a third server system; display means for displaying a print setting screen generated by the acquired application; and transmission means for transmitting print setting set via the print setting screen to the first server system.SELECTED DRAWING: Figure 6

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, a printing apparatus that executes printing based on print settings made in the information processing apparatus, and a control method and program for the information processing apparatus.

Background Art

[0002] There is known a printing system in which a user registers information of a printing apparatus in advance with a cloud printing service, and transmits print data to the printing apparatus via the cloud printing service for printing. The user accesses the cloud printing service from an information processing apparatus such as a PC, selects a printing apparatus to be used for printing from the printing apparatuses registered in the cloud printing service, and instructs printing of the print data.

[0003] The information processing apparatus generates a print job and puts it into a print queue on the cloud printing service. The printing apparatus accesses the cloud printing service, acquires the print job spooled in the print queue generated on the cloud printing service, and outputs it (Patent Document 1).

[0004] Representative examples of cloud printing services include, for example, Google Cloud Print (registered trademark) (Patent Document 1), Microsoft Hybrid Cloud Print (registered trademark), uniFLOW Online (registered trademark), and the like.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] When performing printing using a cloud printing service, the user makes printing settings on a printing settings screen provided by the cloud printing service or a printing settings screen provided by standard software such as an OS. However, on the printing settings screens provided by the cloud printing service or the OS as described above, only standard setting items can be set.

[0007] It is conceivable to use a printing extension application to expand the printing settings screens provided by the cloud printing service or the OS so that items other than standard items can also be set. However, in order to use the above application, the user has to search for an application corresponding to the printer registered with the cloud printing service from the service that distributes the application and install it on the client terminal.

[0008] An object of the present invention is to install the application corresponding to the printing device registered with the cloud printing service on the information processing device used by the user without the user searching for the application.

Means for Solving the Problem

[0009] The program described in this specification is a program of an application executed on the information processing device that can communicate with a server system that transmits print data received from the information processing device to a printing device. The application causes the information processing device to acquire identification information of the printing device, and acquire identification information of an application corresponding to the identification information of the printing device, and acquire an application corresponding to the identification information of the application, so that it is installed on the information processing device. The application causes the information processing device to display a printing settings screen that displays setting items that cannot be set on other printing settings screens provided by the OS of the information processing device. The printing settings set via the printing settings screen are transmitted to the server system. and capability information corresponding to the identification information of the printing device characterized in that wherein, when the identification information of the application corresponding to the setting items included in the capability information is obtained in a state where the application is installed in the information processing device, the version information of the application installed in the information processing device is compared with the version information of the distributed application, and the application having version information indicating that it is newer than the installed application is installed in the information processing device it does so.

Figure 1

Advantages of the Invention

[0010] According to the present invention, the application corresponding to the printing device registered in the cloud printing service can be installed on the information processing device used by the user without the user searching for the application.

Brief Description of the Drawings

[0011]

Figure 2

Figure 3A

Figure 3B

Figure 3C

Figure 4

Figure 5A

Figure 5B

Figure 5C

Figure 6

Figure 7

Figure 8A

Figure 8B

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Embodiments for Carrying Out the Invention

[0012] FIG. 1 is a hardware configuration diagram of a client computer (information processing apparatus) that uses a cloud print service in this embodiment. Detailed description will be given below.

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

[0014] The RAM 1022 is also used as a work area when the CPU 101 performs various processes. The auxiliary storage device 105 stores a cloud driver 1050, an operating system (OS) 1053, applications 1051, print extension applications 1052, and the like. In the following description, the main storage device 102 and the auxiliary storage device 105 are collectively referred to as a storage device.

[0015] Input devices such as a pointing device 109 typified by a mouse touch panel and a keyboard 108 are connected to the system bus 107 through the input I / F 103 and are devices for a user to give various instructions to the computer.

[0016] The output I / F 104 is an interface for outputting data to the outside and outputs data to output devices such as a monitor 110 and a panel 111. Further, the client computer 100 has a photographing function and is equipped with a camera 112.

[0017] The client computer 100 is connected to a printer 200 and each system, which will be described later in FIG. 2, through the network 150 via the communication I / F 106. Further, 107 is a common data system bus for data exchange between I / Fs and modules.

[0018] FIG. 2 is a schematic diagram of a printing system that simplifies the network environment showing the present embodiment.

[0019] The client computer 100 and the printer 200 are connected to the network 150 and are connected to the same intranetwork and are in a communicable state.

[0020] In addition, printers 201 and 202 are connected to another intranet 204, and the network 150 is connected to the intranet 204 through the Internet 203. The Internet 203 is connected to a printer driver distribution service 300, a print extension application distribution service 400, and a cloud print service 500.

[0021] The printer driver distribution service 300 is a server system composed of one or more information processing devices that execute a service for distributing printer drivers to the client computer 100 in a web-based manner. The client computer 100 searches for the printer 200 using a protocol such as WSD (Web Services for Devices) or IPP (Internet Printing Protocol). The client computer 100 obtains and installs a printer driver based on the printer identification information and model information of the discovered printer 200 from the printer driver distribution service 300. The printer drivers registered in the printer driver distribution service 300 are updated by the printer vendor. The client computer 100 automatically or manually obtains a newer version of the printer driver from the printer driver distribution service 300 and updates the installed printer driver.

[0022] The print extension application distribution service 400 is a server system composed of one or more information processing devices that execute a service for distributing applications executed on the client computer 100. A print extension application is an application for extending the printing functions provided by a cloud print service or an operating system (OS). In the printing functions provided by a cloud print service or an OS, only standard functions that can be used with printers of any vendor, such as color mode and duplex printing, can be set for printing. By using a print extension application, printing functions that cannot be set in the printing functions provided by a cloud print service or an OS, such as functions like stitchless stapling, poster printing, and saddle stitching, can be utilized.

[0023] When the client computer 100 receives a user operation requesting the installation of a print extension application, it accesses the print extension application distribution service 400 to install the print extension application. Also, when an application identifier is described in the Inf (Information) file of the printer driver installed on the client computer 100, the installation of the print extension application is performed. The application identifier is application identification information for identifying an application corresponding to a printer registered in the cloud print service 500 among the applications registered in the print extension application distribution service 400. The client computer 100 accesses the print extension application distribution service 400 to install the print extension application corresponding to the identifier described in the Inf file.

[0024] The cloud print service 500 is a service constructed on the cloud, which is a server system composed of one or more information processing devices. In this embodiment, the cloud print service 500 can be connected to each intranet, and can be connected to the client computer 100, printers 200, 201, and 202 through the Internet. The cloud print service 500 performs account management using a user ID and password, and the client computer 100 accesses the cloud print service 500 using the account information input by the user.

[0025] In this embodiment, it is assumed that the client computer 100 has previously stored the URLs of the cloud print service 500 and the print extension application distribution service 400. Also, it is assumed that the cloud print service 500 has previously stored the URL of the printer driver distribution service 300.

[0026] FIG. 3A is a diagram showing an example of the functional blocks of the printer driver distribution service 300. The printer driver distribution service 300 is a server system composed of one or more information processing devices having the same configuration as the information processing device shown in FIG. 1. The printer driver registration unit 301 and the printer driver response unit 302 are realized by the CPU of the information processing device constituting the printer driver distribution service 300 executing a program.

[0027] The printer driver distribution service 300 is a service existing on the cloud through the Internet, and enables the distribution of packages related to printer drivers to external services and the client computer 100. The package related to the printer driver is, for example, a printer driver or a driver extension package.

[0028] When the printer driver registration unit 301 receives an instruction to register a package related to a printer driver from an external service or the client computer 100, it registers the uploaded package in the printer driver database 310. The printer driver registration unit 301 registers, for example, a printer driver distributed by a printer vendor or the like, or a driver extension package for extending the printer driver in the printer driver database 310.

[0029] When the printer driver response unit 302 receives a request to obtain a printer driver or an extension package from an external service or the client computer 100, it obtains the corresponding package from the printer driver database 310 and responds. For example, assume that the printer driver response unit 302 receives a request for a printer driver corresponding to the printer 200 for which a print queue has been generated from the client computer 100. The printer driver response unit 302 reads out the printer driver corresponding to the printer 200 from the printer driver database 310 and transmits it to the client computer 100. The printer driver response unit 302 can also receive a request to obtain a driver extension package for extending the installed printer driver from the client computer 100. In that case, the printer driver response unit 302 reads out the driver extension package corresponding to the requested printer driver from the printer driver database 310 and transmits it to the client computer 100.

[0030] The printer driver database 310 stores the database described later with reference to FIG. 5B. In addition to printer drivers corresponding to various printers, the printer driver database 310 also stores the driver extension package 303.

[0031] The driver extension package 303 is an example of a package distributed from the printer driver distribution service 300. The driver extension package 303 has a driver information section 304 and a device capability information section 305. The driver information section 304 has information such as the HWID and COID (Compatible ID) for identifying the printer, information indicating that the package is a driver extension package, and the version of the driver extension package 303. The device capability information section 305 has the device capability information and the prohibition information of the corresponding printer 200. The device capability information is, for example, information on whether the printer 200 supports color printing or duplex printing. The capability information included in the driver extension package 303 includes, in addition to the above capability information, whether or not the vendor-specific stitchless binding is possible, whether or not the center binding is possible, and whether or not the mixed paper printing using multiple types of paper is possible.

[0032] Figure 3B is a diagram showing an example of the functional blocks of the print extension application distribution service 400. The application registration unit 401 and the application response unit 402 are realized by the CPU of one or more information processing devices constituting the print extension application distribution service 400 executing a program.

[0033] The print extension application distribution service 400 is a service existing on the cloud through the Internet, and enables the distribution of the print extension application to external services and the client computer 100. Note that the print extension application distribution service 400 is not limited to the print extension application 1052, and other applications may be distributed.

[0034] When the application registration unit 401 receives a registration instruction for the print extension application 1052 from an external service or the client computer 100, it registers the uploaded application in the application database 410.

[0035] When there is a request to obtain the print extension application 1052 from an external service or the client computer 100, the application response unit 402 obtains the corresponding application from the application database 410 and transmits it to the requester.

[0036] The application database 410 is a database in which information on print setting applications distributed by a vendor or the like and received a registration request from an external service or the client computer 100 is registered. Details of the information registered in the application database 410 will be described later with reference to FIG. 5C.

[0037] The print extension application 1052 in the present embodiment has a configuration file section 10521 and an execution file section 10522. The configuration file section 10521 has information such as application identification information for identifying the print extension application 1052 and HWID or COID for identifying the corresponding printer 200. The execution file section 10522 is an execution file section of the print extension application 1052. The execution file section 10522 can receive a print setting UI (User Interface) or a push notification from an external service and display a print setting screen.

[0038] FIG. 3C is a functional block diagram of a cloud print service 500 showing an embodiment of the present invention. Each functional block is realized by a CPU of one or more information processing apparatuses constituting the cloud print service 500 executing a program.

[0039] The cloud printing service 500 is a service that exists on the cloud through the Internet and enables the provision of functions related to printing. 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. Also, these functions may be in another cloud printing service that cooperates with the cloud printing service 500.

[0040] Hereinafter, taking the case of registering the printer 200 with the cloud printing service 500 and performing printing using the printer 200 as an example, the same processing can be realized with printers 201 and 202 that can be connected to the cloud printing service 500.

[0041] When there is a printer registration instruction from the printer 200, the printer registration unit 501 uses the 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. The fact that the print queue of the printer and the printer identification information are registered in association with each other is described as the printer being registered. Various attributes may be added to the printer registered here. Various attributes include, for example, the location of the printer.

[0042] The print queue generation unit 502 generates a print queue on the cloud printing service 500 according to the control of the printer registration unit 501. When the client computer 100 sends a print instruction to the cloud printing service 500, a print job is registered in the print queue generated by the print queue generation unit 502.

[0043] The printer list generation unit 503 generates a list of registered printers. It generates a list of printers when, for example, a list of printers registered with the cloud printing service 500 is requested from the client computer 100.

[0044] The discovery response unit 504 responds to the client computer 100 with information on registered printers based on printer discovery for the cloud print service 500 from the client computer 100. The discovery response unit 504 passes the discovery result to the printer list generation unit 503 to generate a printer list. Then, the printer list generated by the printer list generation unit 503 is returned to the client computer 100.

[0045] The print job management unit 505 receives image data and print settings from the client computer 100, and transmits the print job generated by the print job generation unit 506 to the printer 200. Also, the print job management unit 505 stores the print job generated by the print job generation unit 506 in the print job storage area 511.

[0046] The printer database 510 is a database that stores information on printers registered in the cloud print service 500. The content stored in the printer database 510 will be described later with reference to FIG. 5A.

[0047] First, the process of registering the printer 200 with the cloud print service 500 will be described.

[0048] FIG. 4 is a sequence diagram of the process of registering the printer 200 with the cloud print service 500 according to an embodiment of the present invention. In this embodiment, the client computer 100 accesses the printer 200 and operates the printer 200 to send a registration request for the printer 200 to the cloud print service 500.

[0049] The printer 200 supports a cloud print function (a function of receiving a print job from a cloud print service and printing it) and a WebUI function for operating the printer 200 from the client computer 100. The WebUI function is a function of generating a UI and publishing it on the network. The client computer 100 supports a cloud print client function (a function of sending a file to a cloud print service) and a WebUI client (e.g., a web browser) for operating the WebUI. Also, the cloud print service 500 represents a cloud print service on the Internet.

[0050] First, the user uses the WebUI client of the client computer 100 to open the WebUI of the printer 200, and on the WebUI, selects a button for registering the printer with the cloud print service. When this selection is made, in S410, the client computer 100 sends a registration request to the cloud print service to the printer 200.

[0051] In S411, when the printer 200 receives the registration request to the cloud print service in S410, it sends a registration request to the cloud print service to the cloud print service 500. Thus, in this embodiment, a registration request for the printer 200 from the WebUI client of the client computer 100 to the cloud print service 500 is sent. It may also be possible to send this request by operating from an input device associated with the printer 200, for example, a panel. In this case, without making a request from the client computer 100, the printer 200 sends a registration request for the printer to the cloud print service 500.

[0052] In S411, the cloud print service registration request sent to the cloud print service 500 is accompanied by the information of the printer 200. The information of the printer 200 includes the name of the printer 200, the information (HWID) for identifying the printer model, and the COID for identifying the type of printer such as an inkjet printer or a laser printer. Further, the printer information includes the IP address information and the capability information file regarding the functions standardized by IPP or the like.

[0053] When the cloud print service 500 receives the registration request in S411, in S412, it causes the print queue generation unit 502 to create a print queue for sending a print job to the printer 200. The printer registration unit 501 registers the printer information and the capability information in the printer database 510 and generates a record of the printer for which the registration request has been made. Further, the print queue generation unit 502 generates the print queue. This print queue is created using the printer name (device name), the HWID for identifying the printer model, the COID, and the IP address of the printer, which are the information of the received printer 200.

[0054] Next, in S413, the cloud print service 500 sends a download request for the driver extension package 303 to the printer driver distribution service 300. This is a request for receiving the driver extension package 303 corresponding to the printer registered in the cloud print service 500. The cloud print service 500 sends the driver extension package 303 download request, the HWID, and the COID of the printer 200 to the printer driver distribution service 300.

[0055] In S414, based on the received HWID and COID, the printer driver distribution service 300 transmits the corresponding driver extension package 303 to the cloud print service 500. The printer driver distribution service 300 identifies, from the printer driver database 310, a driver extension package that is a package with an extension flag of TRUE and matches the received HWID, from the printer driver database shown in FIG. 5B. If a driver extension package with an extension flag of TRUE but that matches the received HWID cannot be identified, the printer driver distribution service 300 identifies a driver extension package that has an extension flag of TRUE and matches the received COID. Then, the printer driver distribution service 300 transmits the identified printer extension package to the cloud print service 500. Note that if the driver extension package can be identified only by the HWID, in S413, it may be sufficient to transmit only the HWID to the printer driver distribution service 300.

[0056] FIG. 5B is an example of a printer driver database 310 held by the printer driver distribution service 300. The package name refers to the name of the package obtained from the driver information unit 304 at the time of registration. The HWID refers to identification information (model-specific identification information) used when identifying the model of the printer 200. The COID is identification information for identifying the category of the printer that uses the driver. The package refers to the name of a package including the driver extension package 303. The package may be information such as a file path as long as it can identify the driver or driver extension package corresponding to the record. The extension indicates whether the driver extension package 303 is an extension file. When the extension is "FALSE", the package is not an extension package but a printer driver. On the other hand, when the extension is "TRUE", the package is not a printer driver but a package for extending the driver. The application identifier is identification information of an application used when extending the print setting screen using the capability information stored in the printer extension package. In the present embodiment, only the printer extension package has an application identifier, but the printer driver may have an application identifier.

[0057] Note that the printer driver database shown in FIG. 5B is updated by the printer driver registration unit 301. When registering a package in the printer driver database 310, the printer driver registration unit 301 analyzes the driver information unit 304. The printer driver registration unit 301 obtains information such as the package name, HWID, COID, and whether it is a driver extension package, and registers it in the printer driver database 310 together with the driver extension package 303.

[0058] At S415, the cloud print service 500 analyzes the device capability information section 305 of the downloaded driver extension package 303 and expands the print queue. The cloud print service 500 obtains the capability information of the printer 200 from the device capability information section 305 of the driver extension package 303. Then, the cloud print service 500 updates the capability information of the printer corresponding to the print queue of the printer information in the printer database 510. At S415, the cloud print service 500 rewrites the capability information associated with the print queue with the capability information obtained from the driver extension package. Note that the cloud print service 500 may add the capability information regarding the setting items not associated with the print queue among the capability information obtained from the driver extension package to the capability information corresponding to the print queue. Also, the cloud print service 500 may obtain information indicating the hardware configuration of the printer 200 from the printer 200 and determine the capability information from the capability information and the hardware configuration information included in the driver extension package. Also, the cloud print service 500 may obtain information indicating the hardware configuration of the printer 200 from the printer 200 and determine the capability information from the capability information and the hardware configuration information included in the driver extension package.

[0059] By the above processing, the print queue is expanded with vendor-specific device capability information for the printer 200 registered in the cloud print service 500. Then, at S416, the printer database 510 is updated with the information of the expanded printer 200. By the above processing, the capability information expanded by the driver extension package is registered in the printer database 510 as the capability information corresponding to the print queue.

[0060] FIG. 5A is an example of a printer 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 at the time of registration. The HWID refers to an identifier (model-specific identifier) used to identify the model of the printer 200. The COID is identification information for identifying the category of the printer, such as whether the printer 200 is an inkjet printer or a laser beam printer. The IP address refers to the IP address of the destination printer. The package refers to the package name of the driver extension package 303 used for the extension of the print queue corresponding to the printer. If not extended, it is null. Further, although not shown, the capability information of the device and the like are registered in the database in JSON (JavaScript (registered trademark) Object Notation) format. When the capability information of the printer is extended by the driver extension package, the extended capability information is stored. The format in which the capability information of the device is stored is not limited to JSON and may be other data formats. Also, FIG. 5A may store the information of the printer in association with the information of the user who can use the printer.

[0061] FIG. 9 is an example of the capability information stored in association with the print queue. As an example, the capability information is in JSON format, and each setting represents a function. Also, each function has options that can be set in array format.

[0062] 901 indicates the standard capability information defined by IPP or the like. "Duplex" is a setting item related to the duplex function, indicating that it has "Duplex" representing duplex printing and "One-Sided" representing single-sided printing as options for the setting item. "Color" is a setting item related to color printing, indicating that it has "Mono" representing black-and-white printing and "Color" representing color printing as options. "Orientation" is a setting item related to the orientation of the paper used for printing, indicating that it has "Portrait" representing the vertical direction and "Landscape" representing the horizontal direction as options. The capability information described in 901 is the standard setting items and options defined by IPP or the like that can be provided from the printer 200 to the cloud print service 500. By expanding the device's capability information using the driver extension package, even the standard setting items defined by IPP or the like described in 901 can have vendor-specific options. For example, by expanding "Staple", which is a setting item related to paper binding, in addition to "Staple left top" indicating single-point binding at the upper left corner, which is a standard option, "Saddle Stitch" indicating saddle stitching can be set.

[0063] 902 is the capability information extended by the driver extension package 303, for example, the capability information regarding vendor-specific setting items. The functions are Extension_Setting1 and Extension_Setting2, and the options are Exntension_option1 and Extension_option2. As the Extension setting, for example, there are settings regarding stitch binding without needles, and settings regarding mixed paper types where multiple types of paper are mixed in one job. For the mixed paper function, a character string indicating mixed paper is entered into "Extension_Setting1". And for "Exntension_option1", a character string indicating an option to use A3 and A4 paper, and for "Exntension_option2", a character string indicating an option to use B4 and B5 paper are entered. By referring to the file shown in FIG. 9, the print extension application can provide a print setting screen for setting vendor-specific setting items.

[0064] Here, let's return to the explanation in FIG. 4. In S417, when the registration to the printer database 510 is completed, the cloud print service 500 sends a cloud print service registration request response including the registration URL for cloud print registration and a registration URL presentation request to the printer 200.

[0065] In S418, the printer 200 receives the cloud print service registration request response and the registration URL presentation request, and the printer 200 outputs the registration URL information. In S418, the printer 200 displays the URL on the monitor 110, or prints a sheet with the registration URL information described thereon to notify the user of the registration URL. Also, the printer 200 may notify the registration URL to the client computer 100 via the WebUI.

[0066] In S419, the user accesses the cloud print service 500 located at the registration URL presented by the printer 200. At this time, since it is necessary to log in to the cloud account that can access the cloud print service 500, it is necessary to input the user ID and password.

[0067] The cloud print service 500 associates the user with the printer 200 from the registration URL including the cloud account and printer information. As a method of association, for example, there is a method of associating the printer information with the user token. However, it is not limited to this method. And in S420, the cloud print service 500 sends the user token including the information of the cloud print service 500 to the printer 200, and ends the registration process of the printer 200 to the cloud print service 500. The printer 200 accesses the cloud print service 500 using the user token hereafter.

[0068] Next, the process when generating the print queue of the printer 200 registered in the cloud print service 500 and installing the print extension application on the client computer 100 will be described.

[0069] FIG. 6 is a sequence diagram of the process of installing the print extension application 1052 on the client computer 100 showing an embodiment of the present invention.

[0070] On the client computer 100, when outputting to the printer 200 using cloud print, a print job is sent to the cloud print service 500. Therefore, it is necessary to generate a print queue for sending a print job to the cloud print service 500 on the client computer 100.

[0071] In this embodiment, the operating system 1053 uses its printer search function, which is a standard function, to generate a print queue for printers registered with the cloud print service 500. Usually, when performing printer search, printers on the same intranet are targeted. For example, in FIG. 2, when the client computer 100 performs printer search, it can find the printer 200, but it cannot find the printers 201 and 202 beyond the intranet. In this embodiment, the client computer 100 can access the cloud print service 500. When printers are registered with the cloud print service 500, they can be found through printer search. In this embodiment, in addition to the aforementioned printer 200, the printers 201 and 202 are registered with the cloud print service 500, and these printers can also be found using the printer search function of the OS.

[0072] The client computer 100 performs printer search, which is a standard function of the aforementioned operating system 1053 (S610). In S610, the client computer 100 searches for printers registered with the cloud print service 500 in addition to printers on the same intranet as the client computer 100. The client computer 100 accesses the cloud print service and sends a list request for printer information registered on the cloud print service to the cloud print service 500.

[0073] When the search response unit 504 of the cloud print service 500 receives the printer search information, it presents the printers available to the client computer 100. To do this, the cloud print service 500 generates a printer list including printer information that can be used by the user accessing the cloud print service 500 from the client computer 100 (S611). This printer information is the name (device name) of the printer described above, the HWID that identifies the printer model, and the IP address of the printer. The creation of the printer list including the printer information is created by the printer list generation unit 503 of the cloud print service 500 using the information in the printer database 510.

[0074] The cloud print service 500 returns the created printer list to the client computer 100 (S612). At this time, the cloud print service 500 also transmits, along with the printer information included in the printer list, information such as the HWID and COID, which are the printer identification information described in FIG. 5A. The client computer 100 causes the monitor 110 to display a selection screen for the printers available to the user based on the printer list. The user selects the printer to be used from the presented list of printers.

[0075] The operating system 1053 of the client computer 100 installs the cloud driver 1050 used in the cloud print service 500 and generates a print queue for the selected printer (S613). The client computer 100 acquires information on the printer selected by the user from the cloud print service 500 and generates a print queue using this information. The client computer 100 generates a print queue based on the HWID, COID, IP address, and printer capability information acquired from the cloud print service 500. If the cloud driver 1050 has already been installed on the client computer 100, the client computer 100 does not install the cloud driver 1050. The client computer 100 generates a print queue using the already installed cloud driver and the printer information acquired from the cloud print service 500.

[0076] When the operating system 1053 of the client computer 100 successfully generates a print queue, it requests the printer driver distribution service 300 to download the driver extension package 303 (S614). The client computer 100 sends a request to the cloud print service 500 to acquire the HWID, COID, and driver extension package. Note that the client computer 100 may send only either the HWID or the COID to the cloud print service 500.

[0077] When the printer driver distribution service 300 receives a download request, it performs a download process on the client computer 100 (S615). The printer driver distribution service 300 identifies a package that matches the HWID received from the driver extension package registered in the printer driver database 310 and transmits it to the client computer 100. If there is no package that matches the received HWID among the driver extension packages, the printer driver distribution service 300 identifies a driver extension package that matches the received COID. Then, the printer driver distribution service 300 transmits the identified printer extension package to the client computer 100.

[0078] In S616, the operating system 1053 of the client computer 100 installs the driver extension package 303 and expands the capability information of the print queue generated based on the aforementioned cloud driver 1050 (S616). The client computer updates the capability information corresponding to the print queue with the device capability information of the printer extension package. That is, the print queue is expanded with vendor-specific device capabilities for the printer 200 registered in the cloud print service 500. If printer capability information has not been obtained from the cloud print service, the print queue is expanded by associating the capability information included in the driver extension package with the print queue. If capability information has been obtained from the cloud print service 500, the print queue is expanded by overwriting the capability information obtained from the cloud print service 500 with the capability information included in the driver extension package. Also, when capability information has been obtained from the cloud print service 500, the print queue may be expanded by adding the capability information included in the driver extension package that is not included in the capability information obtained from the cloud print service. Furthermore, based on the above capability information and the hardware configuration information of the printer, the functions that the printer can execute may be registered as capability information in the print queue.

[0079] Next, the client computer 100 sends a download request to the print extension application distribution service 400 (S617). At this time, the operating system 1053 makes a download request for the print extension application 1052 associated with the target printer based on the identifier information of the aforementioned print extension application 1052. In the present embodiment, in the print extension application distribution service 400, the identifier information of the print extension application 1052 in the driver extension package 303 and the print extension application 1052 are associated one-to-one.

[0080] Also, in the print extension application distribution service 400, metadata describing the linking information between the identifier information of the print extension application 1052 and the HWID included in the printer information may be stored. In that case, an appropriate print extension application 1052 can be downloaded using the metadata.

[0081] When the print extension application distribution service 400 receives the download request, it performs a download process on the client computer 100 (S618). The application response unit 402 identifies the application corresponding to the application identifier notified from the client computer 100 from the application database 410 shown in FIG. 5C. The application response unit 402 transmits the identified print extension application to the client computer. The client computer 100 installs the print extension application 1052 (S619).

[0082] FIG. 5C is an example of an application database 410 held by the print extension application distribution service 400. The application name is the name of the application registered in the database including the print extension application 1052. The application identifier is information for identifying the application including the print extension application 1052. The app package is the stored file path of the application including the print extension application 1052. The app package may be the stored folder name of the application as long as it can identify the package of the registered print extension application.

[0083] The application database 410 is updated by the application registration unit 401. The application registration unit 401 analyzes the configuration file unit 10521 and obtains the application name and the application identifier. The application registration unit 401 registers the above information in the application database 410 together with the print extension application 1052.

[0084] After installation, the print extension application 1052 on the client computer 100 is associated with the printer 200 on a one-to-one basis. Therefore, in the printer 200, by holding the model information and print setting information of the printer 200, it becomes possible to present an appropriate print setting UI to the user. Alternatively, the print extension application 1052 may communicate with the cloud print service 500, obtain the target model information and print setting information, and provide a UI using that information. When the installation of the print extension application 1052 is completed, the user can make detailed print setting changes.

[0085] Note that in this embodiment, after the client computer 100 generates a print queue, the client computer accesses the printer driver distribution service and obtains a driver extension package. The client computer 100 may not expand the print queue on the client computer even if it obtains information on the expanded print queue from the cloud print service 500. In this case, the client computer 100 omits S614 to S616. Further, after the client computer 100 obtains information on the expanded print queue from the cloud print service 500, it may execute the processes described in S614 to S616.

[0086] Next, a case where the user operates the client computer 100 to perform printing via the cloud print service 500 will be described.

[0087] When a user uses Cloud Print, a print instruction is issued from the application 1051 of the client computer 100. As a specific example, the "Print" button is selected from the file menu of the application. In accordance with the print instruction from the user, the application 1051 instructs the operating system 1053 to display the print common dialog (print setting screen provided by the OS) shown in FIG. 8A. The operating system 1053 receives the instruction from the application 1051 and displays the print common dialog. The print common dialog displayed by the operating system 1053 enables the user to view a list of printers for which a print queue has been generated on the client computer 100, specify the pages to be printed, and set the number of copies. In the area 801, the name of the print queue generated on the client computer 100 is displayed. In the area 801, in addition to the print queues of printers connected to the client computer 100 via the intranet, the print queues of printers that can be used for printing via the Cloud Print service 500 are displayed. In the print common dialog, the user can only set page specifications and the number of copies regardless of which printer is used. In addition, in the common dialog shown in FIG. 8A, settings such as double-sided printing and color mode, which are standard setting items defined by IPP or the like, may be made.

[0088] In order for the user to make print settings that cannot be set in the print common dialog, the user selects the print queue of the printer to be output from the print common dialog and selects the detailed settings button (object) 800 displayed on the same screen. When the user selects the "Detailed Settings" button, the installed print extension application 1052 is launched, and the print setting screen shown in FIG. 8B is displayed. In the print setting screen provided by the print extension application 1052, for example, print settings that cannot be set in the print common dialog, such as image processing settings such as density and color tone, the availability of stamp composition, and the settings of punch position and staple position, can be made.

[0089] Here, with reference to FIG. 8B, the print settings screen provided by the print extension application 1052 will be described.

[0090] When the user selects the "Detailed Settings" button 800 of the print common dialog, the print extension application 1052 acquires the capability information associated with the print queue on the client computer 100 created in the cloud print service 500.

[0091] Based on the acquired capability information, the execution file section 10522 generates the print settings screen shown in FIG. 8B. 803 is the print settings section, which can change the print settings based on the capability information of the print queue. 804 is the extended settings, which is the generated operation section based on the capability information extended by the driver extension package 303. 805 is an area for switching the displayed screen and changing the items to be set. 806 is the OK button, and when pressed, the setting information is confirmed and the confirmed setting information is passed to the OS 1053.

[0092] In the print common dialog, when the user selects the "Print" button 802, the image data, the print settings set in the print common dialog, and the print settings set in the print extension application are sent to the print queue. If the print queue set in the area 801 is the print queue of the printer registered in the cloud print service 500, the client computer 100 sends the image data and the print settings to the print queue of the cloud print service 500 for that printer.

[0093] Next, the process when the user operates the printer to print will be described. When the user logs in to the printer 200, the printer 200 sends a request to the cloud print service 500 to acquire the bibliographic information of the print jobs registered in the print queue of the cloud print service 500. The bibliographic information obtained here is the information necessary for the UI display of the printer 200, such as the file name of the image data, the number of copies in color mode, and the generation date and time of the print job.

[0094] The cloud print service 500 generates a printable job list from the bibliographic information of the print jobs stored in the print queue. Then, the cloud print service 500 sends the generated printable job list to the printer 200. When the printer 200 receives the printable job list sent by the cloud print service 500, the list of the print jobs is displayed on the operation panel. FIG. 7 is an example of the operation panel that displays the printable job list received from the cloud print service 500. "aaa.doc" to "jjj.pdf" are print jobs in the cloud print service. The user selects a desired print job from the operation panel and presses the print button 701 to execute printing. The printer 200 that has received the print execution accepts a print job acquisition request from the cloud print service 500. Note that this acquisition request includes the ID of the print job to be acquired, that is, the print job ID. Hereinafter, printing is realized by executing the process shown in FIG. 10.

[0095] FIG. 10 is a flowchart of the process performed by the cloud print service 500 when receiving a print job acquisition request from the printer 200 in the cloud print service 500 showing this embodiment. Unless otherwise specified, this process is performed in each processing unit of the cloud print service 500. First, the print job management unit 505 receives a print job acquisition request (including the print job ID of the print job to be output) from the printer 200 (S1001).

[0096] The print job management unit 505 that has received the request identifies the specified print job from the print job storage area 511. The print job management unit 505 passes the identified print job to the print job generation unit 506 to generate a print job suitable for the output destination printer 200 (S1002).

[0097] The print job management unit 505 acquires the generated print job from the print job generation unit 506 and sends the print job to the printer 200 that is the source of the print request (S1003).

[0098] In this embodiment, it is assumed that the user operates the printer 200 and the printer 200 obtains the selected print job from the cloud print service 500. It is also possible that the printer 200 periodically accesses the cloud print service 500 and obtains the print jobs managed in association with the print queue of the printer 200 from the cloud print service 500.

[0099] Through the above processing, the print jobs registered in the cloud print service 500 are executed.

[0100] Here, the details of the print queue expansion process in the cloud print service 500 shown in FIG. 4 will be described.

[0101] FIG. 12 is a flowchart showing the process of registering the printer 200 with the cloud print service 500 and the cloud print service expanding the print queue. The process shown in FIG. 12 is realized by the CPU of one or more information processing apparatuses constituting the cloud print service 500 executing a program.

[0102] The printer registration unit 501 determines whether or not a registration request has been received from the printer 200 (S1201). If a registration request has been received from the printer 200, the printer registration unit 501 advances the process to S1202. On the other hand, if a registration request has not been received from the printer 200, the printer registration unit 501 continues the process described in S1201.

[0103] The printer registration unit 501 acquires meta information and device capability information from the printer and registers them in the printer database 510 (S1202). The meta information is, for example, the HWID or COID of the printer 200. Also, the meta information acquired from the printer 200 stores the version of the file of the device capability information provided by the printer 200. The device capability information acquired from the printer 200 is information such as whether double-sided printing is possible or not, whether monochrome printing or color printing is possible or not, and the orientation of the paper used for printing, and is capability information standardized by IPP or the like. The printer registration unit 501 registers the acquired meta information and device capability information in the printer database 510. Further, in S1202, the cloud print service 500 may receive the hardware configuration of the printer 200 from the printer 200.

[0104] The print queue generation unit 502 acquires meta information and device capability information from the printer registration unit 501 and generates a print queue for the printer 200 (S1203).

[0105] The printer registration unit 501 sends a request to the printer driver distribution service 300 to acquire a driver extension package (S1204). The printer registration unit 501 sends the HWID and COID included in the meta information acquired from the printer 200 together with the request to acquire the driver extension package. In this embodiment, both the HWID and COID are sent to the printer driver distribution service, but only one of them may be sent to the printer driver distribution service.

[0106] The printer registration unit 501 determines whether it has acquired a driver extension package from the printer driver distribution service (S1205). For example, when the cloud print service 500 receives a response from the printer driver distribution service 300 indicating that there is no corresponding driver extension package, the printer registration unit 501 determines that it has not acquired the driver extension package. Also, when a request to acquire the driver extension package is sent and the driver extension package is not acquired even after a predetermined time has elapsed, the printer registration unit 501 may determine that it has not acquired the driver extension package. If the printer registration unit 501 has not acquired the driver extension package, the printer registration unit 501 ends the flowchart shown in FIG. 12.

[0107] If the printer registration unit 501 has acquired the driver extension package, the printer registration unit 501 executes the process described in S1206.

[0108] The printer registration unit 501 determines whether the device capability information file included in the driver extension package acquired from the printer driver distribution service 300 is newer than the device capability information file acquired from the printer 200 (S1206). The printer registration unit 501 compares the version of the device capability information file acquired from the printer driver distribution service 300 with the version of the device capability information file acquired from the printer 200. If the device capability information file acquired from the printer driver distribution service 300 is a newer file than the device capability information acquired from the printer 200, the printer registration unit 501 executes the process described in S1207. Note that whether the device capability information file acquired from the printer driver distribution service 300 is newer than the device capability information file acquired from the printer 200 may be determined by something other than the version of the file. For example, the generation date of the device capability information file acquired from the printer 200 may be compared with the generation date of the device capability information file acquired from the printer driver distribution service 300.

[0109] The printer registration unit 501 updates the device capability information registered in the printer database 510 with the device capability information file obtained from the printer driver distribution service 300 (S1207). Further, the printer registration unit 501 transmits the device capability information in the device capability information file to the print queue generation unit 502 and updates the device capability information corresponding to the print queue. The printer registration unit 501 overwrites the device capability information in the printer database 510 with the device capability information included in the driver extension package. Also, the printer registration unit 501 may add to the device capability information the portions of the capability information included in the driver extension package that are not included in the device capability information obtained from the printer. Regarding the print queue generation unit 502 as well, the device capability information associated with the print queue may be overwritten with the capability information included in the driver extension package, or capability information not included in the capability information obtained from the device may be added. Further, in S1202, when receiving the hardware configuration of the printer 200, the printer database may be updated with the capabilities that can be executed by the printer 200 in consideration of the hardware configuration as capability information.

[0110] By doing as shown in FIG. 12, among the capability information obtained from the printer and the capability information included in the driver extension package, the new capability information can be registered in the cloud print service 500. Note that in FIG. 12, it is assumed that the new capability information among the device capability information obtained from the printer 200 and the capability information obtained from the printer driver distribution service 300 is registered in the cloud print service 500. It is also possible to always register the capability information included in the driver extension package obtained from the printer driver distribution service 300 in the cloud print service 500.

[0111] Next, the details of the process of installing the print extension application on the client computer 100 shown in FIG. 6 will be described.

[0112] FIG. 13 is a flowchart showing the process by which the client computer 100 installs a print extension application. Each process is realized by the CPU of the client computer 100 executing a program. Note that the process described in FIG. 13 is started when the user operates the client computer 100 to search for a printer that the client computer 100 can use.

[0113] The CPU 101 sends a request to the Cloud Print Service 500 to obtain a list of printer information registered in the Cloud Print Service 500 (S1301). The CPU 101 accesses the URL of the pre-registered Cloud Print Service 500 to obtain information on printers that can be used by the user who uses the client computer 100. Note that in S1301, the client computer 100 accesses the Cloud Print Service 500 using the access token obtained in advance. If there is no access token, the client computer 100 displays a screen requesting the input of an ID and password to log in to the Cloud Print Service 500. The client computer 100 requests authentication using the ID and password entered by the user and obtains an access token.

[0114] The CPU 101 determines whether it has received a list of printers from the Cloud Print Service 500 (S1302). If the list of printers cannot be obtained, the CPU 101 ends the process described in FIG. 13. If the list of printers can be obtained, the CPU 101 proceeds to S1303.

[0115] The CPU 101 displays the information in the received printer list and accepts the selection of a printer by the user (S1303).

[0116] The CPU 101 sends a request to obtain the meta information and capability information of the selected printer to the Cloud Print Service (S1304). The CPU 101 obtains the meta information and capability information of the selected printer from the Cloud Print Service 500, and generates a print queue on the client computer 100.

[0117] The CPU 101 sends a request to obtain the HWID, COID, and driver extension package included in the obtained meta information to the Printer Driver Distribution Service 300 (S1305). Then, the CPU 101 obtains a driver extension package that matches the transmitted HWID or COID from the Printer Driver Distribution Service 300. In S1305, it is also possible to send only either the HWID or the COID to the Printer Driver Distribution Service.

[0118] The CPU 101 determines whether or not the driver information section 304 of the obtained driver extension package contains an application identifier (application ID), which is the identification information of the print extension application (S1306). If the application identifier is not included, the CPU 101 ends the process described in FIG. 13.

[0119] If the driver extension package contains an application identifier, the CPU 101 determines whether the application with the identifier is installed on the client computer 100 (S1307). If the application is installed on the client computer 100, the CPU 101 determines whether the installed print extension application is the latest (S1308). In S1308, the CPU 101 accesses the print extension application distribution service 400 to obtain the version information of the print extension application distributed therefrom, and compares it with the version of the print extension application already installed. If the version of the installed application is the same as the distributed application, the CPU 101 determines that the installed application is the latest and ends the process shown in FIG. 13. If the version of the distributed application is newer than the installed application, the CPU 101 executes the process described in S1309. In this embodiment, it is determined whether the installed application is the latest based on the version information of the application. It may also be determined whether the application installed on the client computer 100 is the latest based on the distribution start date and time of the application.

[0120] The CPU 101 asks the user whether to install the application distributed by the print extension application distribution service (S1309). If the print extension application is not installed, the CPU 101 ends the process described in FIG. 13. If installation is to be performed, the CPU 101 acquires the application with the application identifier included in the driver extension package from the print extension application distribution service 400 and installs it on the client computer 100 (S1310). In this embodiment, the user is asked whether to install the application. In S1309, the CPU 101 may execute the process of S1310 without asking the user.

[0121] Note that in FIG. 13, in S1305, it is assumed that the client computer 100 acquires the driver extension package from the printer driver distribution service. The client computer 100 may acquire information on the driver extension package from the cloud print service 100 and perform the processes after S1306 based on the driver extension package.

[0122] By executing the process described in FIG. 13, it is possible to install on the client computer 100 a print extension application that can perform vendor-specific print settings in addition to standard print settings.

[0123] Finally, the process when the driver extension package 303 registered in the printer driver database of the printer driver distribution service 300 is updated will be described. FIG. 11 is a sequence diagram showing the process when the driver extension package registered in the printer driver distribution service 300 is updated.

[0124] When the driver extension package distributed by a vendor or the like is registered in the printer driver database 310 by the printer driver registration unit 301 of the printer driver distribution service 300, the driver extension package 303 is updated. When the driver extension package 303 registered in the printer driver distribution service 300 is updated, it is desirable to also update the driver extension package corresponding to the print queue registered in the cloud print service 500. Therefore, the following process is performed to update the driver extension package registered in the cloud print service 500.

[0125] The client computer 100 accesses the cloud print service 500 and sends a login request to the cloud print service 500 (S1101). The user accesses the cloud print service 500, enters the user ID and Password, and logs in to the cloud print service 500. The cloud print service 500 performs user authentication based on the entered user ID and Password.

[0126] When the user authentication is successful, the cloud print service 500 sends a request to the printer driver distribution service 300 to obtain driver extension package information about the printer information associated with the user (S1102). The cloud print service 500 sends the HWID and COID of the printer associated with the user logged in to the printer driver distribution service 300. In S1102, the cloud print service 500 may send either the HWID or the COID. The printer driver distribution service 300 sends the package information of the driver extension package associated with the HWID received from the cloud print service 500 to the cloud print service 500 (S1103). The printer driver distribution service 300 sends the package information of the driver extension package stored in the printer driver database 310. The package information sent here is the version information of the driver extension package, the latest update date and time information, etc.

[0127] The cloud printing service 500 compares the package information of the received driver extension package with the driver extension package information stored in association with the print queue, and determines whether an update of the driver extension package is necessary. The cloud printing service 500 compares, for example, the version of the driver extension package registered in the printer database 510 with the version information of the driver extension package received from the printer driver distribution service. If the version received from the printer driver distribution service 300 indicates a newer version, the process described in S1104 is executed. The cloud printing service 500 may also compare the update date and time of the driver extension package received from the printer driver distribution service 300 with the update date and time of the driver extension package stored in the printer database 510. If the update date and time received from the printer driver distribution service 300 is later, the cloud printing service 500 executes the process described in S1104. If the installed driver extension package in the cloud printing service 500 is the latest, the processes after S1104 are not performed, and the sequence shown in FIG. 11 ends.

[0128] The cloud printing service 500 causes the client computer 100 to display a screen for asking the user whether to update the driver extension package that needs to be updated (S1104). In S1104, for example, information on printers that require an update of the driver extension package is listed, and the user is allowed to select a printer for which the driver extension package is to be updated.

[0129] When the user requests an update of the driver extension package, the client computer 100 sends a request to update the driver extension package for the printer indicated by the user to the cloud printing service 500 (S1105).

[0130] The cloud printing service 500 sends a request to the printer driver distribution service 300 to obtain a driver extension package (S1106). In S1106, the cloud printing service 500 sends the HWID and COID of the printer for which an update has been instructed by the user to the printer driver distribution service 300. Note that in S1106, the cloud printing service 500 may send only either the HWID or the COID to the printer driver distribution service.

[0131] The printer driver distribution service 300 sends the driver extension package identified based on the instructed HWID to the cloud printing service 500 (S1107). The cloud printing service 500 updates the driver extension package received with the driver extension package previously stored in association with the printer information. Thereby, the driver extension package registered in the cloud printing service 500 can be updated to the latest one registered in the printer driver distribution service 300. Note that in the above example, the driver extension package was updated according to the update instruction by the user. When the driver extension package distributed by the printer driver distribution service 300 is updated, a new driver extension package may be installed in the cloud printing service 500 without inquiring the user.

[0132] The cloud printing service 500 also installs the updated driver extension package on the client computer 100 (S1108). The client computer 100 obtains the updated driver extension package from the cloud printing service 500 and updates the information of the driver extension package stored in the client computer 100.

[0133] Note that in FIG. 11, at S1102 where the user logs in to the cloud printing service, a request is made to obtain driver extension package information registered in the printer driver distribution service 300. It may also be that the cloud printing service 500 sends a request to the printer driver distribution service 300 to obtain driver extension package information at predetermined intervals or at a fixed date and time.

[0134] Also, in FIG. 11, it is assumed that the process described in S1102 is executed at the timing when the user logs in. The process after S1102 may be executed when the user who has logged in to the cloud printing service 500 has the authority to manage printer information in the cloud printing service 500.

[0135] By executing the above process, a print extension application for performing print settings that cannot be set in the standard print settings screen provided by the cloud printing service or the OS can be installed on the client computer 100. Also, by using the application identification information included in the driver extension package seeded from the driver distribution service, the application can be installed without the user having to manually search for the print extension application.

[0136] (Other Embodiments) The present invention is also realized by executing the following process. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or device via a network or various storage media, and a computer (or CPU, MPU, etc.) of the system or device reads and executes the program code. In this case, the computer program and the storage medium storing the computer program constitute the present invention.

Claims

1. An information processing device, capable of communicating with a server system that transmits print data received from the information processing device to a printing device; acquiring identification information of the printing device, acquiring identification information of an application corresponding to the identification information of the printing device and capability information corresponding to the identification information of the printing device, and acquiring the application corresponding to the identification information of the application, thereby installing the application; By executing the application, a print setting screen is displayed that displays setting items that cannot be set on other print setting screens provided by an OS of the information processing device and that are included in the capability information; The print settings set via the print setting screen are transmitted to the server system, When an application corresponding to the identification information of the application is installed on the information processing device and the identification information of the application is acquired, the information processing device compares version information of the application installed on the information processing device with version information of the application distributed, and the application having version information indicating that the application is newer than the installed application is installed on the information processing device.

2. A method for controlling an information processing device, the information processing device being capable of communicating with a server system that transmits print data received from the information processing device to a printing device, acquiring identification information of the printing device, acquiring identification information of an application corresponding to the identification information of the printing device and capability information corresponding to the identification information of the printing device, and acquiring the application corresponding to the identification information of the application, thereby installing the application; By executing the application, a print setting screen is displayed that displays setting items that cannot be set on other print setting screens provided by an OS of the information processing device and that are included in the capability information; The print settings set via the print setting screen are transmitted to the server system; A control method for an information processing device, characterized in that when identification information of an application is obtained while an application corresponding to the identification information of the application is installed on the information processing device, version information of the application installed on the information processing device is compared with version information of the application distributed, and the application having version information indicating that it is newer than the installed application is installed on the information processing device.

Images