Information processing apparatus, control method of information processing apparatus, and computer program

Abstract

To provide an information processing apparatus that, according to an input path for a print job executed by one image forming apparatus, extends information on the image forming apparatus.SOLUTION: An information processing apparatus has: first transmission means that transmits a request for acquiring identification information on an image forming apparatus to the image forming apparatus; first receiving means that receives the identification information from the image forming apparatus having received the acquisition request; second transmission means that transmits a request for acquiring identification information on the image forming apparatus to a server device; second receiving means that receives identification information on the image forming apparatus applied with predetermined information from the server device having received the acquisition request; and acquisition means that acquires information on the image forming apparatus from another apparatus by using at least either one of the identification information received by the first receiving means and the identification information applied with the predetermined information received by the second receiving means.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, a control method for the information processing apparatus, 、 and Computer a program.

Background Art

[0002] In recent years, a general-purpose printer driver that communicates with an image forming apparatus using an industry-standard protocol such as IPP (Internet Printing Protocol) has been considered. The general-purpose printer driver can communicate with printers of a plurality of printer vendors. Therefore, by using the general-purpose printer driver, a user can send a print job to the image forming apparatus without installing a vendor-specific printer driver.

[0003] Furthermore, printing using a cloud print service has been considered. In the cloud print service, a printer driver for the cloud print service is installed in an information processing apparatus. The information processing apparatus uses the printer driver for the cloud print service to send a print job to the cloud print service, and the cloud print service sends the print job to the image forming apparatus to execute printing.

[0004] Since the above general-purpose printer driver and the printer driver for the cloud print service handle print jobs printed by image forming apparatuses of various vendors, there are limitations on items and functions that can be set as print settings.

[0005] Therefore, as in Patent Document 1, it has been considered to extend a print queue associated with the printer driver using identification information of the printer associated with the printer driver.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

SUMMARY OF THE INVENTION

PROBLEMS TO BE SOLVED BY THE INVENTION

[0007] By the way, printing via a cloud printing service and printing without going through a cloud printing service have different uses, and there are cases where different print setting extension applications are desired, or cases where only one of them desires to use a print setting extension application.

[0008] For example, cloud printing is often used for business purposes, and since printer vendor drivers cannot be used, expansion of print setting items by a print setting extension application is required.

[0009] On the other hand, local printing is often used for consumer use, and since it is assumed that basic settings are mainly used, expansion of as many print setting items as in cloud printing may not be required.

[0010] Normally, identification information for identifying the model and type of an image forming apparatus is set for each image forming apparatus.

[0011] Therefore, the same identification information is set even for a print queue that inputs a print job via a cloud printing service or a print queue that inputs a print job without going through a cloud printing service. As a result, it is conceivable that the same print setting extension application is associated with any print queue.

[0012] This Invention is an invention in view of the above problems, It is possible to download print setting applications suitable for printing via a cloud server and printing without passing through a cloud server, without having to prepare different identification information in advance for printing via a cloud server and printing without passing through a cloud server and aims to 。

MEANS FOR SOLVING THE PROBLEMS

[0013] The information processing apparatus described in this specification includes a first driver that generates print data to be transmitted to an image forming apparatus without going through a cloud server, a second driver that generates print data to be transmitted to the image forming apparatus via the cloud server, a first receiving means that receives identification information of the image forming apparatus from the image forming apparatus, and first information regarding a first print setting application that extends the function of the first driver, which is obtained based on the identification information received by the First first obtaining means, a first download means that downloads the first print setting application based on the first information obtained by the first obtaining means, a second receiving means that receives the identification information of the image forming apparatus from a predetermined server apparatus, a generating means that generates other identification information by adding predetermined information corresponding to cloud printing to the identification information received by the second receiving means, second information regarding a second print setting application that extends the function of the second driver, which allows a user to set print settings that cannot be set in the first print setting application, and a second obtaining means that obtains the second information based on the other identification information generated by the generating means, and a second download means that downloads the second print setting application based on the second information obtained by the second obtaining means.

Advantages of the Invention

[0014] This For the invention way if , it is possible to download print setting applications suitable for printing via a cloud server and printing without passing through a cloud server, without having to prepare different identification information in advance for printing via a cloud server and printing without passing through a cloud server it becomes possible to do.

Brief Description of the Drawings

[0015]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Mode for Carrying Out the Invention

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

[0017] <Embodiment 1> FIG. 1 shows a configuration diagram of a printing system in cloud printing in the present embodiment. A client terminal 101, a cloud printing server 102, an application management server 103, a cloud printing-compatible printer 104, and an online support server 105 are connected via a network 106.

[0018] In FIG. 1, one client terminal 101 and one cloud printing-compatible printer 104 are shown respectively, but there may be a plurality of client terminals 101 and cloud printing-compatible printers 104.

[0019] Also, the cloud printing server 102, the application management server 103, and the online support server 105 may be server systems composed of a plurality of information processing devices. By configuring each server as a server system composed of a plurality of information processing devices, the load can be distributed among the plurality of information processing devices.

[0020] Also, the cloud printing server 102, the application management server 103, and the online support server 105 may be virtually configured inside one physical information processing device.

[0021] The network 106 assumes a WAN such as the Internet for connection to cloud services, but all may be in a closed environment such as an in-house LAN.

[0022] The client terminal 101 is an information processing device such as a PC, tablet, or smartphone, and is a terminal directly operated by a user. Any application software can be executed on the client terminal 101.

[0023] The cloud print-compatible printer 104 is a device that actually performs printing on a recording medium such as paper, and is an image forming apparatus that converts print data received via the network 106 into image data and prints it.

[0024] The cloud print-compatible printer 104 can receive print data from the client terminal 101 via the cloud print server 102, or can also receive print data directly from the client terminal 101 without going through the cloud print server 102.

[0025] The cloud print-compatible printer 104 receives the print data generated by the cloud printer driver 311 of the client terminal 101 via the cloud print server 102. Also, the cloud print-compatible printer 104 receives the print data generated by the local printer driver 314 of the client terminal 101 without going through the cloud print server 102.

[0026] The cloud print server 102 receives a print instruction and document data from the outside. After converting the document data received by the cloud print server 102 into print data, it transmits the print data to a predetermined cloud print-compatible printer 104.

[0027] The application management server 103 holds and manages various applications. The application management server 103 receives the identification information and download request of an application from the client terminal 101, and transmits the application specified based on the received identification information to the client terminal 101.

[0028] The online support server 105 is a server device that provides an online support service 351. The online support service 351 is a server device for providing a file in which information for expanding the functions of the client terminal 101 is described to the client terminal 101.

[0029] Next, with reference to FIG. 2, the hardware configuration in the system of the present embodiment will be described.

[0030] FIG. 2(a) is a block diagram showing the hardware configuration of the client terminal 101.

[0031] The client terminal 101 includes a display unit 216, an operation unit 217, a storage unit 214, a control unit 211, and a network communication unit 215.

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

[0033] The control unit 211 is composed of a CPU 212 and a memory 213, and controls the overall operation of the client terminal 101. The CPU 212 expands the program stored in the storage unit 214 into the memory 213 and executes it. The memory 213 is the main memory of the CPU 212 and is used as a work area and a temporary storage area for expanding various programs.

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

[0035] The display unit 216 is a device for visually displaying information to the user in real time, such as a liquid crystal display. The operation unit 217 is a device for receiving an input from the user by a keyboard, a mouse, etc. A device having both functions of the display unit 216 and the operation unit 217, such as a touch panel, may be used.

[0036] Figure 2(b) is a block diagram showing the hardware configuration of the cloud print server 102. The cloud print server 102 includes a storage unit 224, a control unit 221, and a network communication unit 225.

[0037] Since the descriptions of the storage unit 224, the control unit 221, and the network communication unit 225 are the same as those of the client terminal 101, they are omitted.

[0038] Note that the cloud print server 102 is described as being composed of one information processing apparatus having the hardware configuration shown in Fig. 2(b), but the cloud print server 102 may be composed of a plurality of information processing apparatuses shown in Fig. 2(b).

[0039] Figure 2(c) is a block diagram showing the hardware configuration of the application management server 103. The application management server 103 includes a display unit 236, an operation unit 237, a storage unit 234, a control unit 231, and a network communication unit 235.

[0040] Since the descriptions of the display unit 236, the operation unit 237, the storage unit 234, the control unit 231, and the network communication unit 235 are the same as those of the client terminal 101, they are omitted.

[0041] Note that the application management server 103 is described as being composed of one information processing apparatus having the hardware configuration shown in Fig. 2(c), but the application management server 103 may be composed of a plurality of information processing apparatuses.

[0042] Figure 2(d) is a block diagram showing the hardware configuration of the cloud print-compatible printer 104. The cloud print-compatible printer 104 includes a display unit 246, an operation unit 247, a storage unit 244, a control unit 241, a network communication unit 245, and a printing unit 248.

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

[0044] The operation unit 247 is a device for receiving inputs from the user, and may include hard keys such as a numeric keypad in addition to the touch panel. Since the storage unit 244 and the control unit 241 are the same as those of the client terminal 101, their descriptions are omitted.

[0045] The network communication unit 245 is a device for communicating with an external network 106, and mainly has the role of receiving print data and transmitting information about the status of the cloud print-compatible printer 104, such as errors, to an external server or the like.

[0046] The printing unit 248 is a device that performs printing processing by performing a series of operations of feeding paper, printing, and discharging paper on the paper prepared in the cassette or tray. The printing method is not particularly limited, such as an electrophotographic method or an inkjet method. Finishing devices such as a duplex unit, stapler, and punching process used at the time of paper discharge are also included in the printing unit 248.

[0047] In this embodiment, as an example of the cloud print-compatible printer 104, a single-function printer that only performs a printing function is described, but a multi-function printer (MFP) that also has a scanner function and a FAX function may be used.

[0048] Figure 2(e) is a hardware block diagram showing details of the online support server 105. In the present embodiment, the online support server 105 is described as being configured by one information processing apparatus, but it may be configured by a plurality of information processing apparatuses. The online support server includes a display unit 256, an operation unit 257, a storage unit 254, a control unit 251, and a network communication unit 255. Since the display unit 256 and the operation unit 257 are the same as the display unit 216 and the operation unit 217 of the client terminal 101, the description thereof is omitted. The storage unit 254 is a memory device such as an HDD or an SSD. The storage unit 254 stores a file in which information for expanding the functions provided by the client terminal 101 is described.

[0049] The control unit 251 includes a CPU 252 and a memory 253. The CPU 252 controls the entire online support server 105. The memory 253 is used for the processes executed by the CPU 252. The network communication unit 255 is an interface for the online support server 105 to communicate with the client terminal 101. The online support server 105 receives an acquisition request for a file stored in the storage unit 254 via the network communication unit 255, and transmits the corresponding file to the client terminal 101.

[0050] Next, with reference to FIG. 3, the software configuration in the system of the present embodiment will be described.

[0051] FIG. 3(a) is a block diagram showing the software configuration of the client terminal 101.

[0052] The client terminal 101 includes a cloud printer driver 311, a print setting extension application 312, an OS 313, a local printer driver 314, and a document generation application 315.

[0053] The cloud printer driver 311 includes a cloud print service I / F 31101, a print job management unit 31102, a UI unit 31103, and a print setting extension application I / F 31104.

[0054] The cloud print service I / F 31101 processes the exchange of data and commands with the cloud print service 321. The cloud print service I / F 31101 transmits print data to the cloud print service 321 and receives printer information from the cloud print service.

[0055] The print job management unit 31102 performs processes such as generation of print jobs and transmission of print jobs.

[0056] The UI unit 31103 has roles such as displaying a print settings screen prepared by the cloud printer driver 311 and receiving user operations from the client terminal 101.

[0057] The print settings extension app I / F 31104 processes the exchange of data and commands with the print settings extension app 312.

[0058] The print settings extension app 312 includes an extended print settings unit 31201, an extended app UI unit 31202, and a print job management unit 31203.

[0059] The extended print settings unit 31201 manages printer vendor-specific function settings that are not supported by the cloud printer driver 311 or the local printer driver 314.

[0060] The extended app UI unit 31202 has roles such as displaying a print settings screen prepared by the print settings extension app and receiving user operations from the client terminal 101.

[0061] The print job management unit 31203 performs processes such as generation of print jobs, editing of print jobs generated by the cloud printer driver 311 or the local printer driver 314, and transmission of print jobs.

[0062] OS313 has an input / output control unit 31300, a print setting extension app management unit 31301, an extended setup information file search unit 31302, and a first additional information adding processing unit 31303.

[0063] The input / output control unit 31300 receives operations by the user of the client terminal 101.

[0064] The print setting extension app management unit 31301 manages the installation of the print setting extension app 312 and processes the exchange of data and commands. Also, the print setting extension app management unit 31301 searches for the print setting extension app 312 from the application management service 331 using the application ID (AppID) extracted from the extended setup information file (Figs. 14(a)(b)(c)).

[0065] The extended setup information file search unit 31302 searches for an extended setup information file in which the device ID held by the OS313 as a search key matches the device ID held by the extended setup information file from the online support service 351. Then, the extended setup information file search unit 31302 downloads the file found by the search.

[0066] The first additional information adding processing unit 31303 adds first additional information representing the major classification of the application to the device ID. In this embodiment, the major classification of the application is the classification of the type of application corresponding to the connected device, and if it is an application corresponding to a printer, additional information "print_" is added to the device ID. Note that "print_" is an example and other character strings, numbers, or symbols may be used.

[0067] The local printer driver 314 has a print job management unit 31401, a UI unit 31402, and a print setting extension I / F 31403.

[0068] The print job management unit 31401 performs processes such as generating a print job and sending a print job.

[0069] The UI unit 31402 has roles such as displaying the print setting screen prepared by the local printer driver 314 and receiving user operations from the client terminal 101.

[0070] The print setting extension app I / F 31104 processes the exchange of data and commands between the print setting extension app 312.

[0071] The document generation app 315 has a UI unit 31501 and is an application having functions such as document creation, editing, and display. The document generation app 315 may be an application having only the function of displaying document data.

[0072] FIG. 3(b) is a block diagram showing the software configuration of the cloud print server 102.

[0073] The account management unit 32101 manages the authentication of tenants and users registered in the cloud print service 321.

[0074] The device management unit 32102 manages device information regarding printers registered in the cloud print service 321. Examples of device information include device ID, tenant ID, printer name, device configuration information, capability information, etc. The device information will be described later with reference to FIG. 14(d).

[0075] The print management unit 32103 makes a determination as to whether to permit a print job transfer request from the cloud print-compatible printer 104, and manages the transfer of the print job.

[0076] The print queue management unit 32104 receives a print job from the outside and holds the received print job in an area prepared in the storage unit 224 of the cloud print server 102.

[0077] The second additional information adding processing unit 32105 adds second additional information representing the detailed classification of the application to the device ID.

[0078] In the present embodiment, the detailed classification of the application is the classification of the type of print queue to which the application is associated. If the print queue to which the application is associated is a cloud print queue, additional information "cloud_" is added to the device ID.

[0079] Note that "cloud_" is just an example, and other character strings, numbers, or symbols may also be used.

[0080] Figure 3(c) is a block diagram showing the software configuration of the application management server 103.

[0081] The application management server 103 has an application management service 331. The application management service 331 further has an application management I / F 33101, an application management unit 33102, and a UI unit 33103.

[0082] The application management I / F 33101 processes the exchange of data and commands performed with the OS 313 of the client terminal 101.

[0083] The application management unit 33102 manages the applications registered in the application management service 331. Also, when an application is registered in the application management service 331, the application management unit 33102 issues an application ID.

[0084] The UI unit 33103 has roles such as displaying the UI prepared by the application management service 331 and receiving user operations at the application management server 103.

[0085] Figure 3(d) is a block diagram showing the software configuration of the device control unit 341 of the cloud print compatible printer 104.

[0086] The print data receiving unit 34101 receives print data transmitted from the outside via the network 106 and stores it in the storage unit 244 of the cloud print-compatible printer 104.

[0087] The device management unit 34102 manages options, capability information, paper remaining amount, ink / toner remaining amount, etc. connected to the cloud print-compatible printer 104.

[0088] The print output unit 34103 controls the printing process onto a recording medium such as paper.

[0089] The UI operation unit 34104 displays the UI on the operation unit 247 of the cloud print-compatible printer 104 and acquires instructions and information input via the UI.

[0090] The cloud print service I / F 34105 processes the exchange of data and commands performed with the cloud print service 321.

[0091] FIG. 3(e) is a block diagram showing the software configuration of the online support server 105. The online support server 105 has an online support service 351.

[0092] The online support service 351 has an online support I / F 35101, a management unit 35102, and a UI unit 35103.

[0093] The online support I / F 35101 processes the exchange of data and commands performed with the OS 313 of the client terminal 101. It receives a search request for a file for expanding the functions of the client terminal 101 from the client terminal 101 and transmits a response to the search request to the client terminal 101.

[0094] The management department 35102 manages the extended set-up information file registered in the online support service 351. The extended set-up information file is a file in which information for extending the functions of the client terminal 101 is described. For example, the printer ID of the cloud-print-compatible printer 104 of the client terminal 101 and the application identification information of the print setting extension application 312 for extending the cloud printer driver 311 are stored.

[0095] The UI department 33103 has roles such as displaying the UI prepared by the online support service 351 and receiving the user's operations at the online support server 105.

[0096] Next, with reference to FIGS. 4, 5, 6, 7, 10, 13, and 14, an example of the procedures of the print setting extension application registrant and the user and the sequence among the respective software and services in the present embodiment will be described.

[0097] In the present embodiment, an example in which the second additional information adding process is performed in the cloud print service 321 is shown.

[0098] First, with reference to FIG. 4(a), an example of the registration of the print setting extension application to the application management service 331 and the registration process of the extended set-up information file to the online support service 351 will be described below. Here, it will be described on the assumption that the application registrant uploads an application from the information processing device to the application management server 103. This information processing device may be the client terminal 101 or another information processing device.

[0099] Here, the case where the print setting extension application 312 for extending the print settings of the cloud printer driver pre-installed in the client terminal 101 is uploaded to the application management service 331 will be described as an example.

[0100] First, the information processing apparatus receives a print setting extension app registration operation by a print setting extension app registrant from the user (S401).

[0101] Next, the information processing apparatus transmits a registration request for a print setting extension app for extending the print settings of the cloud printer driver to the application management service 331 (S402).

[0102] Next, the application management service 331 registers the print setting extension app in the storage unit 234 and generates an application ID which is identification information of the registered print setting extension app (S403).

[0103] The application management service 331 transmits the generated application ID to the information processing apparatus that has transmitted the registration request for the application (S404).

[0104] The information processing apparatus receives an operation for generating an extended setup information file created by the print setting extension app registrant (S405). The application registrant creates an extended setup information file in which the generated application ID is described. In the extended setup information file, a string in which the generated application ID and second additional information are added to the printer ID of one or a plurality of printers for which print settings can be performed using the application is described.

[0105] FIG. 14(a) is an example of an extended setup information file in which a device ID taking into account "adding second additional information to the device ID of the cloud printing printer" in the second additional information adding process is described. In this example, the application ID (AppID) of the print setting extension app for cloud printing is 000ABC. The device ID is "print_cloud_device001" taking into account that the first additional information "print_" and the second additional information "cloud_" are added.

[0106] The information processing apparatus transmits a registration request for the extended setup information file to the online support service 351 (S406).

[0107] The online support service 351 registers the extended setup information file (S407).

[0108] As described above, the print setting extension application 312 is registered in the application management service 331. Further, an extended setup information file for extending the cloud printer driver 311 using the registered print setting extension application 312 is registered in the online support service 351.

[0109] Next, with reference to FIG. 10(a), the procedure when the user registers the cloud print-compatible printer 104 in the cloud print service 321 will be described.

[0110] First, the cloud print-compatible printer 104 receives a printer registration operation for registering the cloud print-compatible printer 104 in the cloud print service 321 from the user via the UI operation unit 34104 (S1001).

[0111] Next, the cloud print-compatible printer 104 sends a printer registration request to the cloud print service 321 together with the device ID of the printer (s1002). Here, the device ID sent to the cloud print service 321 is, for example, the HWID (Hardware ID) assigned to each printer model. Note that the device ID can be any information as long as it can identify the printer model. When the cloud print service 321 receives the registration request, it sends the URL of the cloud print service 321 for printer registration to the cloud print-compatible printer 104. The user accesses the URL from the cloud print-compatible printer 104 or the information processing device, enters the user ID and password for using the cloud print service 321, and logs in to the cloud print service 321. When the user's login is successful, the cloud print service 321 sends a request to the cloud print-compatible printer 104 to obtain the information necessary for printer registration. The cloud print-compatible printer 104 sends the printer information to the cloud print service 321 in response to the request.

[0112] Next, the cloud print service 321 that has received the printer registration request registers the information of the cloud print-compatible printer 104 and generates a print queue for the cloud print-compatible printer 104 (s1003).

[0113] Next, the cloud print service 321 performs a second additional information adding process on the received device ID (s1004). Details of the second additional information adding process (s1004) will be described later with reference to FIG. 7(a). When s1003 and s1004 are completed, the device information shown in FIG. 14(d) is registered in the cloud print service 321. 1601 is a character string obtained by adding second additional information to the device ID acquired from the cloud print compatible printer 104. 1602 is identification information for identifying the tenant to which the user who can use the cloud print compatible printer specified by the device information belongs. A tenant is a group composed of one or more users. 1603 is the printer name of the printer that sent the registration request. The printer name is acquired from the cloud print compatible printer 104 based on s1001 in FIG. 10(a) or an acquisition request from the cloud print service 321, and is used as the name of the print queue. Note that the printer name may be set by another method. 1604 is information indicating the hardware configuration of the cloud print compatible printer 104. The hardware configuration is information such as whether a duplex printing unit is attached to the cloud print compatible printer 104, whether a finisher capable of stapling is attached, or whether a finisher capable of punching is attached. The device configuration information is acquired by a request for acquiring capability information sent from the cloud print service 321 to the cloud print compatible printer 104 in s1003 of FIG. 10(a). 1605 is the capability information of the cloud print compatible printer 104. The capability information is information indicating functions that the cloud print compatible printer 104 can execute, such as whether color printing is possible, whether duplex printing is possible, and whether toner saving mode can be used. The capability information is also acquired by the cloud print service 321 sending a request for acquiring capability information to the cloud print compatible printer 104 in s1003 of FIG. 10(a).

[0114] Returning to the explanation of Fig. 10(a). Next, the cloud print-compatible printer 104 receives the user's printer registration confirmation operation via the UI operation unit 34104 (s1005). Next, the cloud print-compatible printer 104 sends a printer registration status request to the cloud print service 321 (1006). Next, the cloud print service 321 returns the printer registration status to the cloud print-compatible printer 104 (s1007). Then, the cloud print-compatible printer 104 displays the printer registration status on the UI operation unit 34104 (s1008). Note that the processes described in s1005 to s1008 are a method for checking whether information on the cloud print-compatible printer 104 is registered in the cloud print service 321, and thus do not necessarily have to be performed.

[0115] Next, the details of the second additional information addition process (s1004) by the cloud print service 321 will be described below with reference to Fig. 7(a). The process shown in Fig. 7(a) is all executed by the CPU 222 after the program of the cloud print service 321 stored in the storage unit 224 of the cloud print server 102 is loaded into the memory 223.

[0116] The flow in Fig. 7(a) starts with s701 as a result of the cloud print service 321 receiving the device ID from the cloud print-compatible printer 104 via the network 106 from the outside and generating a cloud-side print queue.

[0117] The cloud print service 321 reads the data at the location where the device ID obtained from the cloud print-compatible printer 104 is stored (s701).

[0118] The cloud print service 321 determines whether it has obtained the device ID from the cloud print-compatible printer 104 (s702). If the device ID cannot be obtained, the process described in Fig. 7(a) ends.

[0119] When the device ID can be obtained, the cloud printing service 321 assigns the second additional information (“cloud_”) to the device ID and stores it in the device information (s703). The process described in s703 is executed by the second additional information assignment processing unit 32105 of the cloud printing service 321.

[0120] In this embodiment, the string “cloud_” is added as the second additional information. The string added as the second additional information may be another string of one or more characters, numbers, or symbols. As described above, in the cloud printing service 321, a predetermined string is added to the device ID of the registered printer. By doing so, it becomes possible to identify that the device ID with the predetermined string added is the device ID of the printer registered in the cloud printing service 321.

[0121] Next, with reference to FIG. 5, an example of installing the print setting extension application when the user sets up the cloud printing printer on the client terminal 101 will be described.

[0122] The OS 313 of the client terminal 101 receives a cloud printing printer setup operation by the user via the input / output control unit 31300 (s501).

[0123] The setup operation of the printer for printing is, for example, the following operations. The user gives an instruction to search for a printer to the client terminal 101. The OS 313 searches for printers registered in the cloud print service 321 and printers connected to the network 106. The OS 313 sends a request to obtain printer information registered in the cloud print service 321. The cloud print service 321 displays a login screen for the client terminal 101 to log in to the cloud print service 321. Then, the cloud print service 321 receives a user ID, password, and authentication request from the client terminal 101, performs user authentication based on the received user ID and password, and returns the result to the client terminal. Note that when the client terminal 101 accesses the cloud print service 321 using an access token, user authentication may be performed without displaying the login screen. After successful user authentication, the cloud print service 321 sends a list of printer information associated with the tenant ID to which the logged-in user belongs to the client terminal 101. Also, the OS 313 sends a search packet to the network 106 and detects a printer connected to the network 106 from the response packet. The OS 313 displays a list of the printer information obtained from the cloud print service 321 and the printer information detected by the search of the network 106, and accepts the selection of printer information from the user. The above is an example of the printer setup operation described in S501. In FIG. 5, it is assumed that the printer information of the cloud print-compatible printer 104 received from the cloud print service 321 is selected.

[0124] Next, the OS 313 sends a printer setup request to the cloud print service 321 (S502). The printer setup request includes a request to obtain the capability information and device ID of the cloud print-compatible printer 104.

[0125] In response to a printer setup request, the cloud printing service 321 transmits to the OS 313 a device ID with second additional information added by the second additional information adding process (FIG. 10, s1004) (s503).

[0126] Based on having received from the user a setup operation for a cloud printing printer at s501, the OS 313 installs the cloud printer driver 311 (s504). The installation of the cloud printer driver 311 may be started based on the printer setup operation or may be started based on the acquisition of the device ID at s503.

[0127] The OS 313 generates a print queue associated with the installed cloud printer driver 311 for the client terminal 101 (s505).

[0128] The OS 313 further performs a first additional information adding process on the received device ID with second additional information (s506). The first additional information represents the major classification of the application, that is, the classification of the type of application corresponding to the connected device. In the case of this embodiment, in order to distinguish it from the applications of other devices, the OS 313 adds first additional information (“print_”) indicating that it is an application corresponding to the printer to the device ID.

[0129] Note that “print_” is an example, and other character strings, numbers, or symbols may also be used.

[0130] As a result, if the device ID of the cloud printing compatible printer 104 is device001, the device ID after the second and first additional information adding processes becomes print_cloud_device001.

[0131] OS313 requests the online support service 351 to search for an extended setup information file containing the target device ID (s507) via the extended setup information file search section 31302. Here, OS313 sends a string obtained by concatenating the first additional information, the second additional information, and the device ID to the online support service 351 as the device ID.

[0132] As a result, since the online support service 351 has an extended setup information file containing the target device ID, it returns the extended setup information file (Fig. 14(a)) to OS313 (s508).

[0133] OS313 detects the application ID from the obtained extended setup information file (s509). By executing s509, the application ID of the print setting extension app for cloud printing is detected.

[0134] OS313 requests an application from the application management service 331 using the detected application ID (s510).

[0135] The application management service 331 returns a print setting extension app that matches the requested application ID (s511).

[0136] OS313 installs the obtained print setting extension app in association with the client - side print queue (s512). In s512, the print queue generated in s505 is associated with the application ID of the print setting extension application. This enables the activation of the print setting extension app corresponding to the call of the print queue generated in s505.

[0137] In the above description, it was described that the information of the printer registered in the cloud print service was searched in S501. Based on the search instruction received by the client terminal 101, it may be possible to search both the printer connected via the network 106 and the printer registered in the cloud print service 321.

[0138] Next, using FIG. 13(a), an example of the sequence of processes at the time of activation and print setting of the print setting extension application in the present embodiment will be described below. In FIG. 13(a), the case where the user generates document data using the document generation application 315 and instructs printing in the document generation application 315 will be described as an example.

[0139] The document generation application 315 receives a user's initial screen display operation for printing via the UI unit 31501 (S1501).

[0140] The document generation application 315 requests the OS 313 to display the initial print setting screen (S1502). The OS 313 displays a print setting screen (FIG. 15(e)) for selecting a print queue as the initial print setting screen (S1503). FIG. 15(e) is the initial print setting screen displayed by the OS 313. The area 1741 is an area for selecting a print queue to be used for printing. When the user selects the area 1741, the print queues registered in the client terminal 101 are displayed in a list. In the print queue list, both the print queue of the printer registered in the cloud print service 321 and the print queue of the printer to which the client terminal 101 can send a print job without going through the cloud print service 321 are displayed. The object 1742 is an object for starting the print setting extension application 312.

[0141] Next, the OS 313 receives a user's print queue (FIGS. 15(e), 1741) selection operation via the input / output control unit 31300 (S1504).

[0142] When a print queue is selected, the OS 313 sets, as information on the print setting extension app associated with the object 1742, the app identification information of the print setting extension app associated with the selected print queue (s1505). By doing so, when the object 1742 is selected, the print setting extension app corresponding to the set print queue can be launched. In this example, the association of the launch button is changed for the print setting extension app for cloud printing associated with the print queue of the cloud printer driver 311.

[0143] Next, the OS 313 receives the user's print setting extension app launch operation via the input / output control unit 31300 (s1506). In s1506, when the user selects the object 1742, the launch operation of the print setting extension app is performed.

[0144] The OS 313 sends a launch request to the print setting extension app 312 associated with the object 1742 (s1507).

[0145] The print setting extension app 312 for cloud printing generates a print setting screen extended according to the functions of the printer as a launch process (s1508). The OS 313 displays the UI of the print setting extension app 312 for cloud printing as a new print setting screen via the input / output control unit 31300 (s1509). FIG. 15(b) is a diagram showing an example of the new print setting screen displayed by the print setting extension app 312. In this print setting screen, settings such as paper size, number of copies, print orientation, setting of double-sided or single-sided printing, and post-processing settings such as stapling and punching, which could not be set in the initial print setting screen shown in FIG. 15(e), can be made. When the "OK" button is selected in FIG. 15(b), the screen of FIG. 15(e) is displayed. When the user selects the "Print" button on the screen of FIG. 15(e), the cloud printer driver 311 generates a print job and sends it to the cloud print service 321. The cloud print-compatible printer 104 receives the print job sent to the cloud print service 321 from the cloud print service 321 and executes the printing process.

[0146] Next, with reference to FIG. 6, an example will be described below in which when a print setting extension application for cloud printing is registered in the application management service 331 and the user performs a setup operation of a local printer at the client terminal 101. Local printing is a printing method in which a print job is directly sent to the cloud print-compatible printer 104 without using the cloud print service 321.

[0147] First, the OS 313 receives the printer setup operation of the user via the input / output control unit 31300 (s601). The process of s601 is the same as that of s501 in FIG. 5. In s601, the information of the cloud print-compatible printer 104 detected by the response to the search packet sent by the OS 313 to the network 106 is described as being selected.

[0148] When the user selects a printer, the OS 313 sends a printer setup request to the cloud print-compatible printer 104 (s602).

[0149] The cloud print-compatible printer 104 returns the device ID to the OS 313 in response to the printer setup request (s603).

[0150] Based on the fact that the OS 313 has received the setup operation of the local printer from the user in s601, the OS 313 installs the local printer driver 314 (s604).

[0151] The OS 313 generates a client-side print queue for the installed local printer driver 314 (s605).

[0152] OS313 performs the first additional information adding process on the received device ID (s606). The first additional information represents the major classification of the device ID and is added to enable discrimination of the type of device specified by the device ID. In this example, in order for OS313 to distinguish the device ID from those of other devices, OS313 adds the first additional information ("print_") indicating that it is a device ID corresponding to a printer to the device ID. For example, if the original device ID is device001, the device ID after the first additional information adding process becomes print_device001. Note that "print_" is just an example, and other character strings, numbers, or symbols may also be used.

[0153] Next, OS313 requests the online support service 351 to search for an extended setup information file containing the target device ID via the extended setup information file search section 31302 (s607).

[0154] Since the online support service 351 does not have an extended setup information file containing the target device ID, it returns "not found" to OS313 (s608). When generating a print queue for local printing, since the extended setup file is not downloaded, the print setting extension application is not acquired either.

[0155] In the area 1741 of the screen shown in FIG. 15(e), assume that the print queue generated in FIG. 6 is selected. Even if the process of FIG. 6 is performed, the print setting extension application is not installed, and the generated print queue is not associated with the print setting extension application. Therefore, when the user selects the print queue generated in FIG. 6 on the screen shown in FIG. 15(e), the object 1742 is grayed out. When the user selects the print queue generated in FIG. 6 and selects the "Print" button in FIG. 15(e), the local printer driver 314 generates a print job. The local printer driver 314 transmits the generated print job to the cloud print-compatible printer 104. The print job generated by the local printer driver is transmitted to the cloud print-compatible printer 104 without passing through the cloud print service 321.

[0156] Both FIG. 5 and FIG. 6 are processes for generating a print queue for transmitting a print job to the cloud print-compatible printer 104. By making the string of the device ID received by the client terminal 101 be a different string, it is possible to control so that the print setting extension application is installed only in one case.

[0157] As described above, by the OS 313 searching for the extended set-up information file with the device ID to which the second additional information is added, it becomes possible to control the installation of the print setting extension application according to the type of print queue.

[0158] Note that in the first embodiment, it is assumed that the first additional information is added to the device ID at the client terminal 101. The addition of the first additional information may not be performed.

[0159] <Embodiment 2> In Embodiment 1, an example in which the cloud print service 321 performs the second additional information adding process when registering a printer to the cloud print service 321 was described. In this embodiment, the OS 313 controls the second additional information adding process according to where the device ID is obtained. By doing so, even if the cloud print service 321 does not add the second additional information, the process can be changed when generating a print queue for cloud printing and when generating a print queue for local printing.

[0160] Specific processes according to this embodiment will be described with reference to FIGS. 4, 7, 8, 9, 10, 13, 14, and 16.

[0161] Here, only the differences from Embodiment 1 will be described. Since the system configuration, hardware configuration, and each processing flow are the same as those in Embodiment 1 except for some parts, the description thereof will be omitted.

[0162] FIG. 16 is a diagram showing an example of software blocks in Embodiment 2. The difference from FIG. 3 is that the OS 313 has the second additional information adding process unit 31304, and the cloud print service 321 does not have the second additional information adding process unit.

[0163] Note that regarding the registration of the print setting extension app 312 by the print setting extension app registrant to the application management service 331 in this embodiment, since it is equivalent to the sequence in FIG. 4(a), the description thereof will be omitted. Also, the extended setup information file in FIG. 14(a) is stored in the application management service 331.

[0164] Also, regarding the activation of the print setting extension app 312 and the display of the print setting screen in this embodiment, since it is equivalent to the sequence in FIG. 13(a), the description thereof will be omitted.

[0165] An example of the process of registering a printer by the user to the cloud print service 321 will be described below with reference to FIG. 10(b).

[0166] The cloud-print-compatible printer 104 receives the user's printer registration operation via the UI operation unit 34104 (s1011).

[0167] The cloud-print-compatible printer 104 sends a printer registration request to the cloud print service 321 together with the device ID of the printer (s1012).

[0168] The cloud print service 321 that has received the printer registration request generates a cloud-side print queue for the cloud-print-compatible printer 104 (s1013). Note that the processing from s1011 to s1013 is the same as the processing of s1001 to s1003 in FIG. 10(a).

[0169] The cloud-print-compatible printer 104 receives the user's printer registration confirmation operation via the UI operation unit 34104. (s1014) The cloud-print-compatible printer 104 sends a printer registration status request to the cloud print service 321 (1015). Next, the cloud print service 321 returns the printer registration status to the cloud-print-compatible printer 104 (s1016). Then, the cloud-print-compatible printer 104 displays the printer registration status on the UI operation unit 34104 (s1017). Note that the processing described in s1014 to s1017 is the same as the processing described in s1005 to s1008 in FIG. 10(a). Also, since the processing described in s1014 to s1017 is for confirming whether the registration of printer information is completed, it may not be performed.

[0170] Next, an example of the installation of the print setting extension application when the user gives an instruction to add a cloud printing printer will be described below with reference to FIG. 8.

[0171] First, the OS 313 receives a printer setup operation for cloud printing by the user via the input / output control unit 31300 (s801). Here, among the detected printer information, the printer information of the cloud print-compatible printer 104 obtained from the cloud print service 321 is selected for explanation.

[0172] The OS 313 sends a printer setup request to the cloud print service 321 (s802).

[0173] The cloud print service 321 sends a device ID to the OS 313 in response to the printer setup request (s803).

[0174] Based on having received the setup operation of the cloud printer from the user in s801, the OS 313 installs the cloud printer driver 311 (s804).

[0175] The OS 313 generates a client-side print queue for the installed cloud printer driver 311 (s805). Note that the descriptions of s801 to s805 so far are the same processing as s501 to s505 in FIG. 5.

[0176] Next, the OS 313 performs a second additional information adding process to the device ID (s806). S806 is the difference from Embodiment 1. In the case of this example, since it is the device ID obtained from the cloud print service, the OS adds the second additional information ("cloud_") to the device ID. The details of the second additional information adding process (s806) at this time will be described later with reference to FIG. 7(b).

[0177] OS313 performs a first additional information addition process on the device ID (s807). The first additional information represents the major classification of the device ID, that is, the classification corresponding to the connected device. In this example, in order to distinguish it from other devices, OS313 adds first additional information ("print_") indicating that it is an application corresponding to a printer to the device ID. Note that "print_" is just an example, and other character strings, numbers, or symbols may also be used.

[0178] When the device ID of the cloud print-compatible printer 104 is device001, through the processes of s806 and s806, the device ID becomes print_cloud_device001.

[0179] OS313 requests the online support service 351 to search for an extended setup information file containing the target device ID via the extended setup information file search section 31302 (s808).

[0180] As a result, since the online support service 351 holds an extended setup information file containing the target device ID, it returns the extended setup information file (Figure 14(a)) to OS313 (s809).

[0181] OS313 detects the application ID from the obtained extended setup information file (s810). As a result of s810, the application ID of the print setting extension application for cloud printing is detected.

[0182] OS313 requests the application management service 331 for an application using the detected application ID (s811).

[0183] The application management service 331 returns the print setting extension application that matches the requested application ID (s812).

[0184] OS313 installs the acquired print setting extension application by associating it with the client-side print queue (s813). Note that the processes described in s807 to s813 are the same as the processes in s506 to s512 described in FIG. 5.

[0185] Next, with reference to FIG. 7(b), the details of the second additional information addition process (s806) by OS313 will be described below. The processes shown in FIG. 7(b) are all executed by the CPU 222 after the program of OS313 stored in the storage unit 224 of the client terminal 101 is loaded into the memory 223.

[0186] The flow of FIG. 7(b) starts with s711 as a result of OS313 installing the cloud printer driver 311 or the local printer driver 314 to generate a client-side print queue.

[0187] First, OS313 acquires information indicating whether it has searched for the cloud print service 321 or directly searched for the cloud print-compatible printer 104 for local printing (s711). The printer information displayed on the client terminal 101 in s801 is associated with information indicating the search target. In s711, OS313 acquires the information indicating the search target associated with the printer information selected by the user.

[0188] Next, based on the information acquired in s711, it is determined whether the print queue is a print queue detected by searching for the cloud print service 321 (s712).

[0189] If it is a print queue detected by searching for the cloud print service 321, OS313 assigns the second additional information ("cloud_") to the device ID (s713).

[0190] On the other hand, in the determination result of S711, when directly searching for the cloud print-compatible printer 104 for local printing, the OS 313 does not attach the second additional information to the device ID and ends the process shown in FIG. 7(b). Note that "cloud_" is an example, and other character strings, numbers, or symbols may also be used.

[0191] Next, with reference to FIG. 9, an example of the case where the user gives an instruction to add a local printer when a print setting extension app for cloud printing is registered in the application management service 331 will be described below.

[0192] First, the OS 313 receives a local printer setup operation by the user via the input / output control unit 31300 (S901). Here, it is assumed that among the printer information displayed in the list, the printer information of the cloud print-compatible printer 104 detected by the response to the search packet output to the network 106 is selected.

[0193] Next, the OS 313 sends a printer setup request to the cloud print-compatible printer 104 (S902).

[0194] Next, the cloud print-compatible printer 104 passes the device ID to the OS 313 in response to the printer setup request (S503).

[0195] Next, based on having received the local printer setup operation from the user in S901, the OS 313 installs the local printer driver 314 (S904).

[0196] Next, the OS 313 generates a client-side print queue in the installed local printer driver 314 (S905). S901 to S905 are the same processes as S601 to S605 in FIG. 6.

[0197] Next, the OS 313 performs a second additional information adding process on the received device ID (s906). Here, the process described above with reference to FIG. 7(b) is executed. Since a print queue for local printing is selected in FIG. 9, no second additional information is added.

[0198] Next, the OS 313 further performs a first additional information adding process on the device ID (s907). The first additional information represents the major classification of the device, that is, the classification of the type of the connected device. In this example, in order to distinguish it from applications of other devices, the OS 313 adds first additional information ("print_") indicating that it is an application corresponding to a printer to the device ID. As a result, if the original device ID was device001, the device ID after the first additional information adding process becomes print_device001.

[0199] Note that "print_" is just an example, and other character strings, numbers, or symbols may be used.

[0200] Next, the OS 313 requests the online support service 351 to search for an extended set-up information file containing the target device ID via the extended set-up information file search section 31302 (s908).

[0201] As a result, since the online support service 351 does not have an extended set-up information file containing the target device ID, it returns "not found" to the OS 313 (s909). Therefore, when a print queue for cloud printing is generated, the print setting extension application for cloud printing is installed, and when a print queue for local printing is generated, the print setting extension application for cloud printing is not installed. Note that the processes described in s907 to s909 are the same as the processes described in s606 to s608 of FIG. 6.

[0202] As described above, in Embodiment 2, the OS 313 adds second additional information to the device ID. By doing so, even if the cloud print service 321 does not add the second additional information, it becomes possible to control the installation of the print setting extension application according to the type of print queue.

[0203] <Embodiment 3> In Embodiment 1, an example was described in which a print setting extension application registrant registers only a print setting extension application for cloud printing with the application management service 331. In this embodiment, an example will be described in which a print setting extension application registrant registers a plurality of print setting extension applications with the application management service 331.

[0204] For example, it is assumed that cloud printing is used in a business scenario. Therefore, it is assumed that the print setting extension application for cloud printing has a UI that enables various print settings (1711 in FIG. 15(b)) and a UI for authentication to the cloud print service (1721 in FIG. 15(c)). On the other hand, since local printing is often used in consumer use, it is assumed that there are differences such as a UI limited to basic settings (1701 in FIG. 15(a)) and no need for an authentication UI to the cloud print service for the print setting extension application for local printing. Therefore, for one printer, two print setting extension applications for cloud printing and local printing may be registered with the application management service 331.

[0205] Therefore, in this embodiment, such two print setting extension applications are registered by the print setting extension application registrant with the application management service 331. And control is performed so that the installed application changes according to whether it is a print queue for cloud printing or a print queue for local printing.

[0206] Specific processing according to this embodiment will be described with reference to FIGS. 4, 5, 10, 11, 13, 14, and 15.

[0207] Here, only the differences from Embodiment 1 will be described. Since the system configuration, hardware / software configuration, and each processing flow are the same as those in Embodiment 1 except for some parts, the description thereof will be omitted.

[0208] First, using FIG. 4(b), an example of the registration process of the print setting extension app 312 and the extended setup information file to the application management service 331 by the print setting extension app registrant in the present embodiment will be described below.

[0209] In this example, an example in which the print setting extension app registrant registers the print setting extension app 312 for cloud printing and the print setting extension app 312 for local printing to the application management service 331 is shown. Note that the processing flows of s411 to s417 up to the registration of the print setting extension app for cloud printing and the registration of the extended setup information file (File_A) are the same as the processing flows of s401 to s407 in FIG. 4(a), and thus the description thereof will be omitted.

[0210] Next, the information processing apparatus receives a registration operation of the print setting extension app for local printing by the print setting extension app registrant via the input / output control unit 31300 (s418).

[0211] Next, the information processing apparatus transmits a registration request for the print setting extension app for local printing to the application management service 331 (s419).

[0212] Next, the application management service 331 registers the print setting extension app for local printing and generates an application ID as the ID of the registered print setting extension app for local printing (s420).

[0213] Next, the application management service 331 issues the generated application ID to the print setting extension app registrant via the input / output control unit 31300 of the information processing apparatus that is the registration request source (s421).

[0214] The information processing apparatus receives a registration operation of an extended setup information file created by a print setting extension app registrant via the input / output control unit 31300 (s422). Note that the extended setup information file can combine a plurality of printers, i.e., device IDs, for one application ID.

[0215] Also, at this time, the print setting extension app registrant writes a device ID with the second additional information addition process taken into account in the extended setup information file. However, here, the applications registered in the application management service are local printing applications. Therefore, the first additional information is added to the device ID of the cloud print-compatible printer 104, and a string without the second additional information added is described in the extended setup file as the device ID.

[0216] FIG. 14(b) is an example of an extended setup information file in which a device ID taking into account the fact that "the second additional information is not given to the device ID of the local printing printer" is described in the second additional information addition process. In this example, when the application ID (AppID) of the print setting extension app for local printing is 000EFG, it is assumed that nothing is given in the second additional information addition process to the device ID, and "print_" is given in the first additional information addition process.

[0217] Next, the OS 313 sends a registration request for the extended setup information file to the online support service 351 (s423).

[0218] Then, the online support service 351 registers the extended setup information file (s424).

[0219] Note that the process of registering a printer by the user to the cloud print service 321 is equivalent to the sequence in FIG. 10(a), so the description is omitted.

[0220] The process of generating a print queue for the cloud print service on the client terminal 101 is the same as that in FIG. 5, so the description is omitted. In step s507 of FIG. 5 in this embodiment, the device ID "print_cloud_device001" is notified to the online support service, and in step s508, the extended setup file shown in FIG. 14(a) is acquired. Regarding the activation of the print setting extension app 312 and the display of the print setting screen in this embodiment, since they are equivalent to the sequence in FIG. 13(a), the description is omitted.

[0221] Next, an example of the case where the user performs a setup operation for a local printer on the client terminal 101 will be described with reference to FIG. 11. Note that the processes from s1201 to s1207 are equivalent to the processes from s601 to s607 in FIG. 6, so the description is omitted. In s1207, the device ID notified to the online support service is "print_device001" with the first additional information added.

[0222] In response to the search request for the extended setup information of the OS 313, the online support service 351 returns an extended setup information file (File_B) including the target device ID (s1208).

[0223] Next, the OS 313 detects the application ID from the acquired extended setup information file (File_B) (s1209). As a result, the application ID of the print setting extension app for local printing is detected.

[0224] Next, the OS 313 requests the application to the application management service 331 using the detected application ID (s1210).

[0225] Next, the application management service 331 returns the print setting extension app that matches the requested application ID (s1211).

[0226] Then, the OS 313 installs the acquired print setting extension application in association with the client-side print queue (s1212).

[0227] In this way, even for a print queue for sending a print job to the same cloud print-compatible printer 104, the device ID notified to the online support service 351 is changed. As a result, the client terminal 101 can install applications with different application IDs.

[0228] Next, with reference to FIG. 13(b), an example of activation of the print setting extension application and display of the print setting screen in the present embodiment will be described below.

[0229] First, the document generation application 315 receives a user's initial screen display operation for printing via the UI unit 31501 (s1521).

[0230] Next, the document generation application 315 requests the OS 313 to display the initial print setting screen (s1522).

[0231] The OS 313 displays a print setting screen (FIG. 15(e)) for selecting a print queue as the initial print setting screen (s1523).

[0232] Next, the OS 313 receives a user's print queue (FIGS. 15(e), 1741) selection operation via the input / output control unit 31300 (s1524).

[0233] Next, the OS 313 sets the application identification information of the print setting extension application associated with the selected print queue as the information of the print setting extension application associated with the object 1742 (s1525). In the present embodiment, the association of the start button is changed for the print setting extension application for local printing associated with the print queue of the local printer driver 314.

[0234] Next, the OS 313 receives the user's operation to start the print setting extension application via the input / output control unit 31300 (s1526).

[0235] Next, the OS 313 sends a start request to the print setting extension application for local printing associated with the start button (s1527).

[0236] Next, the print setting extension application 312 for local printing generates a print setting screen extended according to the functions of the printer as a start process (s1528).

[0237] The OS 313 displays the UI of the print setting extension application for local printing as a new print setting screen via the input / output control unit 31300 (s1529). FIG. 15(a) is the print setting screen displayed by the print setting extension application for local printing. Since different applications display the print setting screen in FIGS. 15(a) and 15(b), screens with different items that can be set are displayed. In this way, different applications can be started for local printing and cloud printing.

[0238] As described above, in this embodiment, when using the extended setup information file in which the device ID with the second additional information indicating the type of print queue is described, the print setting extension application for cloud printing is installed. On the other hand, when using the extended setup information file in which the device ID without the second additional information indicating the type of print queue is described, the print setting extension application for local printing is installed. Therefore, when a print queue for cloud printing is generated, the print setting extension application for cloud printing is installed, and when a print queue for local printing is generated, the print setting extension application for local printing is installed.

[0239] By the cloud printing service 321 adding second additional information to the device ID, even when there are multiple print setting extension apps for one printer, it becomes possible to control the installation of the print setting extension app according to the type of print queue.

[0240] <Embodiment 4> In Embodiment 3, an example was described in which no second additional information was added to the device ID of the local printing printer in the addition of the second additional information. In this embodiment, different second additional information is added to the device ID of the local printing printer and the device ID for cloud printing. By adding different second additional information, different device IDs can be obtained, and different extended setup files can be acquired.

[0241] Regarding the specific processing according to this embodiment, it will be described with reference to FIGS. 4, 8, 10, 12, 13, 14, and 16. Here, only the differences from Embodiment 3 will be described. Since the system configuration, hardware configuration, and each processing flow are the same as those in Embodiment 1 except for some parts, the description will be omitted.

[0242] Regarding the software configuration, as shown in FIG. 16, the difference from Embodiment 1 is that it is not the cloud printing service 321 but the OS 313 that has the second additional information adding processing unit 31304.

[0243] Also, regarding the registration of the print setting extension app 312 and the extended setup information file to the application management service 331 by the print setting extension app registrant in this embodiment, since it is equivalent to the sequence in FIG. 4(b), the description will be omitted.

[0244] Note that the extended setup information files in FIGS. 14(a) and 14(c) are stored in the application management service 331. Since FIG. 14(a) is the same as the previous description, the description will be omitted.

[0245] FIG. 14(c) is an example of an extended setup information file that describes a device ID considering "adding the second additional information to the device ID of the local printing printer" in the second additional information adding process. The application ID (AppID) "000EFG" of the printing setting extension application for local printing is described. The device ID described in the file is "print_local_device001" considering that ("local_") is added in the second additional information adding process and "print_" is added in the first additional information adding process.

[0246] The process of registering a printer by the user to the cloud print service 321 is equivalent to the sequence of FIG. 10(b), so the description is omitted.

[0247] The process of generating a print queue for cloud printing is the same as FIG. 8 except for the details of the process performed in s806, so the description is omitted.

[0248] Next, the details of the second additional information adding process (s806) by the OS 313 will be described below with reference to FIG. 7(c).

[0249] All the processes shown in FIG. 7(c) are executed by the CPU 222 after the program of the OS 313 stored in the storage unit 224 of the client terminal 101 is loaded into the memory 223. The flow of FIG. 7(c) starts with s721 as a result of the OS 313 installing the cloud printer driver 311 or the local printer driver 314 and generating a client-side print queue.

[0250] First, the OS 313 acquires information indicating the search target of the selected printer information (s721).

[0251] Next, referring to the information obtained in s721, it is determined whether the search target is the cloud printing service 321 (s722). If the search target is the cloud printing service 321, the OS 313 assigns the second additional information ("cloud_") to the device ID (s723).

[0252] On the other hand, if the search target is local, the OS 313 assigns the second additional information ("local_") to the device ID (s724). Note that "cloud_" and "local_" are just examples, and other character strings, numbers, or symbols can also be used.

[0253] Next, with reference to FIG. 12, the processing when the user gives an additional instruction for local printing in this embodiment will be described.

[0254] Note that the processing from s1401 to s1405 is equivalent to the processing from s901 to s905 in FIG. 9, so the description is omitted.

[0255] After the processing of s1405, the OS 313 performs the second additional information assignment process shown in FIG. 7(c) on the device ID (s1406). In this example, since the OS 313 directly requested the cloud printing-compatible printer 104 for local printing, the second additional information ("local_") will be assigned to the device ID.

[0256] Next, the OS 313 executes the processing after s1406. However, the processing from s1406 to s1408 is equivalent to the processing from s906 to s908 in FIG. 9, so the description is omitted. At this time, as a result of the first additional information assignment process (s1407), if the original device ID was device001, the device ID after the first additional information assignment process will be print_local_device001.

[0257] The online support service 351 returns an extended setup information file (File_B) containing the target device ID in response to the search request of s1408 (s1409).

[0258] Next, the OS 313 detects the application ID from the acquired extended setup information file (File_B) (s1410). As a result, the application ID of the print setting extension app for local printing is detected.

[0259] Next, the OS 313 requests the application from the application management service 331 using the detected application ID (s1411).

[0260] The application management service 331 returns the print setting extension app that matches the requested application ID (s1412).

[0261] Next, the OS 313 installs the acquired print setting extension app (s1412). As a result, when using the extended setup information file in which the device ID with the second additional information indicating the type of print queue for cloud printing is described, the print setting extension app for cloud printing is installed.

[0262] As shown in FIGS. 7(c), 8, and 12, in this embodiment, the second additional information to be assigned to the device ID is changed according to whether the printer information selected by the user is the printer information acquired from. By doing so, it is possible to acquire the extended setup information file suitable for the acquisition source of the printer information. As a result, it is possible to install the application suitable for the acquisition source of the printer information.

[0263] The process of starting the print setting extension app 312 and displaying the print setting screen in this embodiment is the same as the sequences in FIGS. 13(a) and 13(b), so the description is omitted.

[0264] As described above, by the OS 313 assigning different second additional information to the device ID, when there are multiple print setting extension apps for one printer, it becomes possible to control the installation of each print setting extension app according to the type of print queue.

[0265] <Embodiment 5> In Embodiment 1, an example in which the cloud print service 321 performs the second additional information adding process when registering a printer with the cloud print service 321 was described.

[0266] In this embodiment, an example in which the cloud print-compatible printer 104 executes the second additional information adding process when a print setting extension app registrant registers a plurality of print setting extension apps with the application management service 331 will be described.

[0267] Specific processes according to this embodiment will be described with reference to FIGS. 4, 5, 10, 13, and 17.

[0268] Here, only the differences from Embodiment 1 will be described. Since the system configuration, the hardware / software configuration, and each processing flow are the same as those in Embodiment 1 except for some parts, the description thereof will be omitted.

[0269] Regarding the software configuration, as shown in FIG. 17, the difference from Embodiment 1 is that the cloud print-compatible printer 104 has the second additional information adding processing unit 34106 instead of the cloud print service 321.

[0270] Note that the registration of the print setting extension app 312 by the print setting extension app registrant with the application management service 331 in this embodiment is equivalent to the sequence in FIG. 4(b), and thus the description thereof will be omitted.

[0271] Note that the extended setup information files in FIGS. 14(a) and 14(b) are stored in the application management service 331.

[0272] Using FIG. 10(c), an example of the process of registering a printer by a user with the cloud print service 321 will be described below. First, the cloud print-compatible printer 104 receives a printer registration operation from the user via the UI operation unit 34104 (s1021).

[0273] Next, the cloud print-compatible printer 104 performs a second additional information adding process on the device ID (s1022). Details of the second additional information adding process (s1022) at this time will be described with reference to FIG. 7(d). In this example, since there is an instruction to register with the cloud print service 321, the cloud print-compatible printer 104 adds second additional information ("cloud_") to the device ID.

[0274] Next, the cloud print-compatible printer 104 sends a printer registration request to the cloud print service 321 together with the device ID with the second additional information. (s1023) Next, the cloud print service 321 that has received the printer registration request registers the cloud print-compatible printer 104 and generates a cloud-side print queue for the cloud print-compatible printer 104. (s1024) Next, the cloud print-compatible printer 104 receives a printer registration confirmation operation from the user via the UI operation unit 34104 (s1025).

[0275] Next, the cloud print-compatible printer 104 sends a printer registration status request to the cloud print service 321. (1026) Next, the cloud print service 321 returns the printer registration status to the cloud print-compatible printer 104 (s1027).

[0276] Then, the cloud print-compatible printer 104 displays the printer registration status on the UI operation unit 34104 (s1028).

[0277] Next, with reference to FIG. 7(d), the details of the second additional information adding process (S1022) by the cloud print-compatible printer 104 will be described below. The processes shown in FIG. 7(d) are all executed by the CPU 242 with the program of the device control unit 341 stored in the storage unit 244 of the cloud print-compatible printer 104 loaded into the memory 243.

[0278] In the flow of FIG. 7(d), when the cloud print-compatible printer 104 receives an instruction to register with the cloud print service 321, S731 starts.

[0279] First, the cloud print-compatible printer 104 acquires extended information of the device ID (S731). The extended information of the device ID is information set from a screen displayed on the operation unit of the cloud print-compatible printer 104. FIG. 15(d) is an example of a setting screen for the extended information of the device ID. By the user selecting the object 1751, the on / off of the extension of the device ID can be switched. The user sets the on / off of the extension of the device ID, selects the "OK" button, and sets the extended information of the device ID.

[0280] Based on the information acquired in S731, the cloud print-compatible printer 104 determines whether there is an instruction to extend the device ID (S732).

[0281] If there is an instruction to extend the device ID, the cloud print-compatible printer 104 adds second additional information ("cloud_") to the device ID (S733). Note that "cloud_" is an example, and other character strings, numbers, or symbols may also be used.

[0282] If there is no instruction to extend the device ID, the cloud print-compatible printer 104 does not add the second additional information to the device ID and ends the process.

[0283] Regarding the installation of the print setting extension app when the user gives an instruction to add a cloud printing printer, since it is the same as the sequence in FIG. 5, the description is omitted. Also, regarding the installation of the print setting extension app when the user gives an instruction to add a local printing printer, since it is the same as the sequence in FIG. 11, the description is omitted.

[0284] Regarding the activation of the print setting extension app 312 and the display of the print setting screen in this embodiment, since it is equivalent to the sequences in FIGS. 13(a) and 13(b), the description is omitted.

[0285] In this embodiment, an example is shown in which the user gives an instruction to add second additional information to the device ID in advance at the UI operation unit (34014) of the cloud print-compatible printer 104. The cloud print-compatible printer 104 may automatically execute the second additional information addition process. That is, no setting is performed at the operation unit of the cloud print-compatible printer 104, and when transmitting the printer ID to the cloud print service 321, the ID with the second additional information added may be notified as the device ID.

[0286] For example, a method such as the cloud print-compatible printer 104 automatically executing the second additional information addition process when the user registers the cloud print-compatible printer 104 with the cloud print service 321 can be considered. In that case, it is not necessary for the user to give an instruction to add second additional information to the device ID in advance at the UI operation unit (34014) of the cloud print-compatible printer 104.

[0287] As a result, when using the extended setup information file in which the device ID with the second additional information indicating the type of print queue for cloud printing is described, the print setting extension app for cloud printing is installed.

[0288] Also, when using the extended setup information file that describes the device ID without the second additional information indicating the type of print queue, the print setting extension app for local printing is installed.

[0289] Therefore, when a print queue for cloud printing is generated, the print setting extension app for cloud printing is installed, and when a print queue for local printing is generated, the print setting extension app for local printing is installed.

[0290] As described above, the cloud-printing-compatible printer 104 may assign the second additional information to the device ID. By switching whether or not to assign the second additional information, when there are multiple print setting extension apps for one printer, it becomes possible to control the installation of each print setting extension app according to the type of print queue.

[0291] <Other Embodiments> The present invention is also realized by executing the following processing. 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. A first driver that generates print data to be sent to an image forming apparatus without going through a cloud server; A second driver that generates print data to be sent to the image forming apparatus via the cloud server; First receiving means for receiving identification information of the image forming apparatus from the image forming apparatus; First acquisition means for acquiring first information regarding a first print setting application that extends the function of the first driver, based on the identification information received by the first receiving means; First download means for downloading the first print setting application based on the first information acquired by the first acquisition means; Second receiving means for receiving the identification information of the image forming apparatus from a predetermined server device; Generation means for generating other identification information by adding predetermined information corresponding to cloud printing to the identification information received by the second receiving means; Second acquisition means for acquiring second information regarding a second print setting application that extends the function of the second driver, the second information enabling a user to set print settings that cannot be set by the first print setting application, based on the other identification information generated by the generation means; An information processing apparatus, characterized by comprising second download means for downloading the second print setting application based on the second information acquired by the second acquisition means.

2. Search means for searching for an image forming apparatus connected to the same network as the information processing apparatus; Further comprising display means for displaying one or more image forming apparatuses found by the search by the search means, The information processing apparatus according to claim 1, wherein the image forming apparatus corresponding to the identification information is selected from the one or more image forming apparatuses displayed by the display means.

3. The information processing apparatus according to claim 1 or 2, wherein the print settings that cannot be set by the first print setting application include staple settings.

4. The information processing apparatus according to any one of claims 1 to 3, wherein the print settings that cannot be set by the first print setting application include punch settings.

5. The first information regarding the first print setting application is associated with the image forming apparatus. The information processing apparatus according to any one of claims 1 to 4, wherein the second information regarding the second print setting application is associated with the image forming apparatus based on the other identification information generated by the generation means.

6. The information processing apparatus according to any one of claims 1 to 5, further comprising transmission means for transmitting the print setting value set by the first print setting application to the image forming apparatus without passing through the cloud server, and transmitting the print setting value set by the second print setting application to the image forming apparatus via the cloud server.

7. The information processing apparatus according to any one of claims 1 to 6, wherein the predetermined information corresponding to the cloud print is a character string indicating a cloud.

8. A control method for an information processing apparatus having a first driver that generates print data to be transmitted to an image forming apparatus without passing through a cloud server, and a second driver that generates print data to be transmitted to the image forming apparatus via the cloud server, the method comprising: a first receiving step of receiving identification information of the image forming apparatus from the image forming apparatus; a first obtaining step of obtaining first information regarding a first print setting application that extends the function of the first driver based on the identification information received in the first receiving step; a first downloading step of downloading the first print setting application based on the first information obtained in the first obtaining step; a second receiving step of receiving the identification information of the image forming apparatus from a predetermined server device; a generating step of generating other identification information by adding predetermined information corresponding to cloud print to the identification information received in the second receiving step; a second obtaining step of obtaining second information regarding a second print setting application that extends the function of the second driver, the second information allowing a user to set print settings that cannot be set by the first print setting application, based on the other identification information generated in the generating step. ​ A control method for an information processing apparatus, comprising: a second download step of downloading the second printing setting application based on the second information acquired in the second acquisition step.

9. A computer program for causing a computer of the information processing apparatus to execute a control method for the information processing apparatus, the control method comprising: a first driver for generating print data to be transmitted to the image forming apparatus without passing through a cloud server; and a second driver for generating print data to be transmitted to the image forming apparatus via the cloud server. The control method further comprises: a first receiving step of receiving identification information of the image forming apparatus from the image forming apparatus; a first acquisition step of acquiring first information regarding a first printing setting application that extends the function of the first driver based on the identification information received in the first receiving step; a first download step of downloading the first printing setting application based on the first information acquired in the first acquisition step; a second receiving step of receiving the identification information of the image forming apparatus from a predetermined server device; a generation step of generating other identification information by adding predetermined information corresponding to cloud printing to the identification information received in the second receiving step; a second acquisition step of acquiring second information regarding a second printing setting application that extends the function of the second driver, the second information allowing a user to set printing settings that cannot be set by the first printing setting application, based on the other identification information generated in the generation step; a second download step of downloading the second printing setting application based on the second information acquired in the second acquisition step.

10. The control method further comprises: a search step of searching for an image forming apparatus connected to the same network as the information processing apparatus; and a display step of displaying one or more image forming apparatuses found by the search in the search step, wherein the image forming apparatus corresponding to the identification information is selected from the one or more image forming apparatuses displayed in the display step.

11.

16. ​ The computer program according to claim 9 or 10, wherein print settings that cannot be set by the first print setting application include staple settings.

12. The computer program according to any one of claims 9 to 11, wherein print settings that cannot be set by the first print setting application include punch settings.

13. The first information regarding the first print setting application is associated with the image forming apparatus. The computer program according to any one of claims 9 to 12, wherein the second information regarding the second print setting application is associated with the image forming apparatus based on the other identification information generated in the generation step.

14. The control method is as follows. The computer program according to any one of claims 9 to 13, further comprising a transmission step of transmitting the print setting value set by the first print setting application to the image forming apparatus without passing through the cloud server, and transmitting the print setting value set by the second print setting application to the image forming apparatus via the cloud server.

15. The computer program according to any one of claims 9 to 14, wherein the predetermined information corresponding to the cloud print is a character string indicating a cloud.

Images