Application, information processing apparatus, and method of controlling information processing apparatus

The application addresses the challenge of distinguishing between direct and cloud-connected printers by displaying unique icon images, improving user comprehension of printer connections and settings.

JP2024165286AInactive Publication Date: 2024-11-28CANON KK
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023081355
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-17
Publication Date
2024-11-28
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Existing standard printer drivers provided by OS platforms do not distinguish between printers connected directly and those connected via a cloud print service, making it difficult for users to differentiate between the two when displaying printer icons.

Method used

An application that obtains and displays distinct icon images based on identification information from the printer, allowing differentiation between printers connected directly and those connected via a cloud print service.

Benefits of technology

Enables users to visually distinguish between different printer connection methods, enhancing user understanding of printer functionality and settings.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024165286000001_ABST
    Figure 2024165286000001_ABST
Patent Text Reader

Abstract

To provide an application for displaying an icon image corresponding to a printer driver to be used, in displaying an icon image of a printer.SOLUTION: An application causes an information processing apparatus to execute: a first acquisition step of acquiring an icon image of a first printer based on identification information acquired from the first printer; a second acquisition step of acquiring an icon image of a second printer based on identification information of the second printer acquired from a server; and a first control step of causing display means to display the acquired icon images of the first and the second printers.SELECTED DRAWING: Figure 8
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an application, an information processing device, and a method for controlling an information processing device. [Background technology]

[0002] Traditionally, printing has been performed using drivers provided by printer vendors (printer manufacturers). In recent years, by using standard drivers provided by manufacturers that provide operating systems, it has become possible to print without using drivers provided by printer vendors. For example, Windows (registered trademark) is equipped with a standard driver called an IPP class driver. Android (registered trademark) is equipped with a standard driver called mopria (registered trademark). In addition, iOS (registered trademark) is equipped with a standard driver called AirPrint (registered trademark) as one of the OS functions. These standard drivers are drivers that transmit print commands that comply with a printing protocol called IPP (Internet Printing Protocol). Therefore, printers that support IPP can receive such print commands and execute printing. The characteristic of such standard drivers is that they can execute printing on multiple models of printers from multiple printer vendors that are compatible with the printing protocol. In other words, they are compatible with multiple models of printers.

[0003] In Patent Document 1, in an information processing device capable of communicating with a printer, a driver installed in the information processing device acquires icon image data representing the external appearance of the printer from the printer. The driver then provides the icon image data to an OS. The document describes how the OS is then able to display the icon on a printer management screen (for example, a device and printer screen) provided by the OS. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2022-89143 A Summary of the Invention [Problem to be solved by the invention]

[0005] There may be multiple types of standard printer drivers provided by the OS. For example, both a printer driver that generates print data to be sent directly to a printer connected to the same network as the information processing device and a printer driver that generates print data to be sent to a printer via a cloud print service may be provided. In this case, if the same icon image is displayed regardless of which printer driver is used, it is difficult for a user to distinguish whether the printer is a directly connected printer or a printer connected via a cloud print service by looking at the icon image.

[0006] The application described in this application aims to display an icon image of a printer corresponding to the printer driver being used when displaying the icon image of the printer. [Means for solving the problem]

[0007] An application according to an embodiment of the present invention includes a first acquisition step of acquiring an icon image of a first printer based on identification information acquired from the first printer, a second acquisition step of acquiring an icon image of a second printer based on identification information of a second printer acquired from a server, and a first control step of displaying the acquired icon image of the first printer and the acquired icon image of the second printer on a display means. The present invention is characterized in that the information processing device executes the above steps. Effect of the Invention

[0008] According to the application described in this specification, when displaying a printer icon image, it is possible to display an icon image corresponding to the printer driver being used. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of a network configuration of the present embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration according to the present embodiment. [Diagram 3] 11 is a sequence diagram showing a sequence from installation of an extended application to arrangement of an icon image in the present embodiment. [Figure 4] 11 is a diagram showing an example of a screen related to a printer to be used that is displayed by the OS in the present embodiment. FIG. [Diagram 5] FIG. 4 is a diagram showing an example of an icon image in the present embodiment. [Figure 6] 4 is a diagram showing an example of information constituting device capability information in the present embodiment. FIG. [Figure 7] 11 is a diagram showing an example of information constituting an extended setup information file of the present embodiment. FIG. [Figure 8] 13 is a diagram illustrating an example of a UI in which a print setting expanding application 312 of the present embodiment displays an icon image for each queue. [Figure 9] 11 is a flowchart illustrating an example of a process performed by a print setting expanding application 312 in the present embodiment until an icon image is acquired. [Figure 10] 11 is a flowchart illustrating an example of a process performed by a print setting expanding application 312 in the present embodiment until an icon image is acquired. [Figure 11] 11 is a diagram showing an example of a path of an icon image stored in an OS in this embodiment. FIG. [Figure 12] 2 is a diagram illustrating an example of a file system managed by an online support service in the present embodiment. [Figure 13]6 is a diagram showing an example of a sequence executed when a printing device and a client terminal are connected in the embodiment. [Figure 14] 1A and 1B are diagrams illustrating an example of a print process using a print setting extending application in the present embodiment. [Figure 15] 5 is a diagram showing an example of a print setting screen provided by a file generation application in the embodiment. FIG. [Figure 16] 5 is a diagram showing an example of a print setting screen displayed by a print setting extending application in the embodiment. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

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

[0012] Although FIG. 1 illustrates one client terminal 101 and one cloud print-compatible printer 104, there may be a plurality of client terminals 101 and a plurality of cloud print-compatible printers 104.

[0013] Furthermore, the cloud print server 102, the application management server 103, and the online support server 105 may be a server system configured with a plurality of information processing devices. By configuring each server as a server system configured with a plurality of information processing devices, it is possible to distribute the load to a plurality of information processing devices.

[0014] Furthermore, the cloud print server 102, the application management server 103, and the online support server 105 may be virtually configured within one physical information processing apparatus.

[0015] The network 107 is assumed to be a WAN such as the Internet for connecting to cloud services, but may be a closed environment such as an in-house LAN.

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

[0017] The cloud print-compatible printer 104 is a device that actually prints on a recording medium such as paper, and is an image forming apparatus that converts print data received via a network 107 into image data and prints the image data. The printer 106 has a similar hardware configuration to the cloud print-compatible printer 104.

[0018] The printer 106 is communicably connected to the client terminal 101 without going through a cloud print service 321. The client terminal 101 generates print data to be sent to the cloud print-compatible printer 104 via the cloud print service 321 using a cloud printer driver 311. The client terminal 101 generates print data to be sent to the printer 106 using a local printer driver 313.

[0019] The cloud print-compatible printer 104 may be able to receive and print print data generated by the local printer driver 313 without going through the cloud print service 321. Also, the printer 106 may receive print data generated by the cloud printer driver 311 via the cloud print service 321.

[0020] The cloud print server 102 receives print instructions and print data from an external device. The cloud print server 102 then transmits the received print data to a predetermined cloud print-compatible printer 104.

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

[0022] 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 the client terminal 101 with a file in which information for extending the functions of the client terminal 101 is described. A vendor (manufacturer) that provides the cloud print-compatible printer 104 or the printer 106 registers information for extending the print function provided by the operating system of the client terminal 101 in advance in the online support service 351. Reference numerals 1201 to 1203 in FIG. 12 denote extended setup information files and icon images registered in the online support service 351 by the vendor that provides the printer. Reference numeral 1201 denotes the extended setup information file shown in FIG. 7. Reference numerals 1202 and 1203 denote icon image data that is stored in association with print queue information when the client terminal 101 installs the extended setup information file 700.

[0023] Next, the hardware configuration of the system of this embodiment will be described with reference to FIG.

[0024] FIG. 2A is a block diagram showing an example of the hardware configuration of the client terminal 101. As shown in FIG.

[0025] 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 .

[0026] The storage unit 214 refers to a non-volatile storage device such as a hard disk or SSD, and is capable of storing and rewriting digital data.

[0027] 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 loads programs stored in the storage unit 214 into the memory 213 and executes them. The memory 213 is the main storage memory of the CPU 212 and is used as a work area and a temporary storage area for loading various programs.

[0028] The network communication unit 215 is a device for communicating with the external network 107, and inputs and outputs digital data to and from external servers, client terminals, and the like via the network 107.

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

[0030] 2B is a block diagram showing an example of a 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.

[0031] The description of the storage unit 224, the control unit 221, and the network communication unit 225 is omitted because they are the same as those of the client terminal 101.

[0032] Although the cloud print server 102 is described as being configured with one information processing device having the hardware configuration shown in FIG. 2(b), the cloud print server 102 may also be configured with multiple information processing devices as shown in FIG. 2(b).

[0033] 2C is a block diagram showing an example of a 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.

[0034] The display unit 236, operation unit 237, storage unit 234, control unit 231, and network communication unit 235 are the same as those in the client terminal 101, and therefore will not be described here.

[0035] Although the application management server 103 will be described as being configured from one information processing device having the hardware configuration shown in FIG. 2(c), the application management server 103 may be configured from a plurality of information processing devices.

[0036] 2D is a block diagram showing an example of a 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.

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

[0038] The operation unit 247 is a device for receiving input from a user, and may include hard keys such as a numeric keypad in addition to a touch panel. The storage unit 244 and the control unit 241 are the same as those in the client terminal 101, and therefore a description thereof will be omitted.

[0039] The network communication unit 245 is a device that communicates with the external network 107, and is mainly responsible for 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.

[0040] The printing unit 248 is a device that performs printing processing by carrying out a series of operations such as paper feeding, printing, and paper ejection on paper prepared in a cassette or tray. The printing method is not particularly limited, and may be an electrophotographic method or an inkjet method. Finishing devices such as a duplex unit, stapler, and puncher used when ejecting paper are also included in the printing unit 248.

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

[0042] The hardware configuration of the printer 106 shown in FIG. 1 is the same as that shown in FIG.

[0043] FIG. 2(e) is a hardware block diagram showing an example of the online support server 105. In this embodiment, the online support server 105 is described as being configured with one information processing device, but may be configured with multiple information processing devices. The online support server is configured with a display unit 256, an operation unit 257, a storage unit 254, a control unit 251, and a network communication unit 255. The display unit 256 and the operation unit 257 are similar to the display unit 216 and the operation unit 217 of the client terminal 101, and therefore description thereof will be omitted. The storage unit 254 is a memory device such as an HDD or SSD. The storage unit 254 stores a file containing information for expanding the functions provided by the client terminal 101.

[0044] The control unit 251 is composed of a CPU 252 and a memory 253. The CPU 252 controls the entire online support server 105. The memory 253 is used for processing 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 a request to acquire a file stored in the memory unit 254 via the network communication unit 255, and transmits the corresponding file to the client terminal 101.

[0045] Next, an example of a user procedure and a sequence between each software and print service in this embodiment will be described with reference to Fig. 3. Note that, here, the cloud print-compatible printer 104 is registered in the cloud print service 321, and the cloud print service 321 is used to obtain an icon.

[0046] First, the cloud print-compatible printer 104 accepts a printer registration operation from a user to register the cloud print-compatible printer 104 in the cloud print service 321. In accordance with the printer registration operation, the cloud print-compatible printer 104 transmits printer device identification information and a printer registration request to the cloud print service 321 (S3001). Here, the device identification information transmitted to the cloud print service 321 is, for example, a HWID (hardware ID) assigned to each printer model. Note that the device identification information may be any information as long as it can identify the printer model.

[0047] When the cloud print service 321 receives the registration request, it transmits 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 an information processing device, inputs a 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 transmits a request to the cloud print-compatible printer 104 to obtain information required for printer registration. The cloud print-compatible printer 104 transmits printer information to the cloud print service 321 in response to the request.

[0048] Next, the cloud print service 321 registers information about the cloud print-compatible printer 104 and generates a print queue for the cloud print-compatible printer 104. At this time, the cloud print service 321 acquires capability information about the cloud print-compatible printer 104 and links it to the generated print queue. The capability information is information that indicates the functions that the printer has, and refers to information necessary for the user to set as print settings when printing, such as double-sided printing capability information, color printing capability information, and staple capability information. As a specific example, it is assumed here that IPP is used as the communication protocol. The cloud print-compatible printer 104 transmits capability information to the cloud print service 321 using attribute values ​​defined in IPP. Note that attribute values ​​that are not defined in IPP are notified to the cloud print service 321 as they are.

[0049] Next, the installation of the print setting extension application 312 that is performed when the user performs a setup operation on the client terminal 101 for printing with the cloud print-compatible printer 104 will be described.

[0050] The OS 313 of the client terminal 101 accepts a cloud print-compatible printer setup operation by a user. The cloud print-compatible printer setup operation is, for example, the following operation.

[0051] The OS 313 of the client terminal 101 receives an instruction to add a printer from the user (S3002).

[0052] 4 shows a screen displayed by the OS 313 of the client terminal 101 for managing information on print queues registered in the OS 313 of the client 101. When the user selects a button 401, an instruction to search for a printer is input to the OS 313.

[0053] The OS 313 that has received the printer search instruction determines whether or not it holds a token for acquiring information from the cloud print service 321 .

[0054] If the token is not held, the OS 313 displays a screen for inputting user information (login name, password) and transmits the user information input via the screen to the cloud print service 321 to request user authentication and an access token (S3003).

[0055] The cloud print service 321 performs authentication processing (S3004) using the user information received from the client terminal 101. Upon completing the authentication processing, the cloud print service 321 notifies the client terminal 101 of the result of the authentication processing.

[0056] If the user authentication is successful, the OS 313 obtains an access token from the cloud print service 321 (S3005).

[0057] If the user authentication fails in S3004, the cloud print service 321 notifies the OS 313 of the client terminal 101 of an authentication error (S3006).

[0058] The OS 313 of the client terminal 101 stops the process based on the received authentication error information (S3007), and ends the process shown in FIG.

[0059] If the client terminal 101 already holds the access token, the OS 313 of the client terminal 101 advances the process to step S3008 and searches for printers registered in the cloud print service 321 and printers connected to the network 107.

[0060] The OS 313 of the client terminal 101 assigns an access token and transmits a request to obtain information about the printers registered in the cloud print service 321 (S3008).

[0061] The cloud print service 321 identifies the tenant ID to which the user belongs, which is identified by the access token attached to the acquisition request, and generates a list of printers linked to the tenant ID to which the user belongs.

[0062] The OS 313 of the client terminal 101 acquires the printer list generated by the cloud print service 321 and the device identification information of each printer (S3009).

[0063] The OS 313 displays a printer list on the client terminal 101 based on the printer information acquired from the cloud print service 321 and the printer information detected by searching the network 107. In 402 in Fig. 4, the printer information received from the cloud print service 321 and the printers that can be searched for on the local network are displayed in a list.

[0064] Next, the user selects printer information of a printer that the user wishes to register in the client terminal 101 from the displayed printers. The OS 313 transmits a capability information request of the selected cloud print-compatible printer 104 to the cloud print service 321 (S3010). The OS 313 decides which attribute to inquire about.

[0065] The cloud print service 321 responds to the OS 313 with the capability information of the cloud print-compatible printer 104 (S3011). The capability information of the cloud print-compatible printer 104 may be capability information acquired when the printer is registered, or the latest capability information may be acquired from the cloud print-compatible printer 104 when an inquiry is made from the OS 313.

[0066] If the cloud print service 321 does not store capability information for an attribute inquired by the OS 313 of the client terminal 101, the cloud print service 321 does not respond to the OS 313.

[0067] Next, the OS 313 initiates the installation of a cloud printer driver 311 that generates print data to be sent to the printer selected by the user.

[0068] The OS 313 generates a print queue for the cloud printer driver 311 having basic device capability information included with the OS 313 (S3012). The device capability information refers to definition information required to generate print setting capability information for the printer driver, for example, information written in XML such as PrintDeviceCapabilites. FIG. 6A is a diagram showing an example of device capability information included with the OS 313. Reference numeral 601 indicates capability information related to the number of copies. Here, it is shown that the minimum number of copies is 1 copy, and the maximum number is 999 copies. Reference numeral 602 indicates capability information related to paper size. "Feature" indicates the function name. "Option" indicates information on options that can be selected for the function. It is shown that there are two selectable paper sizes, "A4" and "LETTER". This information is linked to the print queue and is managed by the OS 313.

[0069] Thereafter, the OS 313 updates the device capability information constituting the cloud printer driver 311 using the capability information acquired from the cloud print service 321. FIG. 6B is a diagram showing an example of device capability information updated using the capability information acquired from the cloud print service 321. Reference numeral 603 indicates the paper size after the update. To the "PageMediaSize", "Option" other than "A4" and "LETTER" is added as a paper size printable by the cloud print-compatible printer 104. The OS 313 registers the printer's HWID, device capability information, and identification information of the printer driver to be used in association with the print queue.

[0070] With the above, the installation of the cloud print driver 311 is completed.

[0071] Next, the OS 313 starts the process of installing an application that is linked to the printer and that extends the cloud print driver.

[0072] First, the OS 313 performs processing for adding additional identification information to the device identification information. This processing is necessary when acquiring the extended setup information file 700 from the online support server 105. The additional identification information may be any character string that is different from normal device identification information.

[0073] In this embodiment, in order to distinguish the application from applications of other devices, the OS 313 adds additional identification information ("PrinterApp_") indicating that the application is compatible with the printer to the device identification information.

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

[0075] As a result, for example, if the device identification information of the cloud print-compatible printer 104 is device001, the device identification information after the additional identification information addition process becomes PrinterApp_device001.

[0076] Next, the OS 313 transmits a search request for the extended setup information file 700 to the online support service 351 (S3013). The OS 313 transmits to the online support service 351 the device identification information with the additional identification information added thereto.

[0077] If the online support service 351 has the extended setup information file 700 including the target device identification information, the online support service 351 transmits the extended setup information file 700 to the OS 313 (S3014). Furthermore, in S3014, the online support service 351 transmits an icon image corresponding to the extended setup information file to the client terminal 101.

[0078] FIG. 7 is an example of an extended setup information file 700 in which device identification information is written that takes into account that "additional identification information is added to the device identification information of a cloud print-compatible printer" in the additional identification information adding process.

[0079] Reference numeral 701 denotes application identification information of a print setting extension application corresponding to the extended setup information file 700 .

[0080] Reference numeral 702 denotes device identification information of the device corresponding to the extended setup information file 700. This describes the device identification information after the additional identification information "PrinterApp_" has been added. The online support service 351 identifies the extended setup information file in which the same PrinterHardwareId 702 as the device identification information received from the client terminal 101 is written.

[0081] DDInstall 703 indicates that there is additional information about the printer identified by PrinterHardwareId 701. It is described that DeviceIconProperty is the additional information. DeviceIconProperty is information indicating that the icon image of the printer is registered in the online support service 351.

[0082] DeviceIconProperty 704 is information indicating the file name of the icon image and where the data of the icon image is to be stored in the client terminal 101 after it is acquired. DIRID 13 is identification information of a directory designated when the client terminal 101 stores the icon image.

[0083] 7A shows an example in which one icon image is associated with one device of an HWID, but multiple icon images may be associated with one device of an HWID.

[0084] For example, one printer may be compatible with both the cloud printer driver 311 and the local printer driver 313. In this case, if the same icon image is displayed when the printer driver to be used is the cloud printer driver 311 and when the local printer driver 313, it becomes difficult to distinguish which printer driver is to be used. Therefore, in this embodiment, different icon images are displayed when the cloud printer driver 311 is used and when the local printer driver 313 is used.

[0085] In order to display different icon images for the cloud printer driver 311 and the local printer driver 313, the DDInstall 703 and DeviceIconProperty 704 in the extended setup information file are changed as shown in FIG. 7B.

[0086] DDInstall 705 is information written in the extended setup information file in place of DDInstall 703 in Fig. 7A. DeviceIconProperty 706 is information written in the extended setup information file in place of 704 in Fig. 7A.

[0087] “AddProperty=CloudDeviceIconProperty” indicates that there is an icon image to be used when generating a print queue that uses the cloud printer driver 311. The file name of the icon image is “vendor1.icon”, and the client terminal 101 stores the icon image in a directory identified by DIRID 13.

[0088] “AddProperty=LocalDeviceIconProperty” indicates that there is an icon image to be used when generating a print queue that uses the local printer driver 313. The file name of the icon image is “vendor2.icon”, and the client terminal 101 stores this icon image in DIRID 13.

[0089] FIG. 5 is a diagram showing an example of an icon image obtained using the extended setup information file 700. As shown in FIG.

[0090] Fig. 5(a) is an icon image associated with a print queue that uses the cloud printer driver 311. Fig. 5(a) is an image that corresponds to "vendor1.ico" in Fig. 7(b). Here, an image of a cloud is superimposed on an image that resembles a printer so that it is clear that the cloud print service 321 is being used.

[0091] Fig. 5(b) is an icon image associated with a print queue that uses the local printer driver 313. Fig. 5(b) is an image corresponding to "vendor2.ico" in Fig. 7(b). Because the local printer driver 313 communicates directly with the printer and does not go through the cloud print service 321, no cloud image is added, and the image resembles a printer.

[0092] The above-mentioned method of specifying an icon is merely an example, and any method may be used as long as it is a method for acquiring an icon image using an extended setup information file.

[0093] As described above, the online support service 351 provides the icon image, together with the extended setup information file, to the client terminal 101. This makes it possible for the client terminal 101 to display an icon image corresponding to the printer to be used for printing.

[0094] Returning to the explanation of Fig. 3, the OS 313 installs the extended setup information (S3015). In S3015, the OS 313 reads the contents of the extended setup information file and writes them to the registry.

[0095] Next, the OS 313 stores the icon image acquired from the online support service 351 in a directory specified by the extended setup information file. If there are multiple icon images specified in the extended setup information file, the multiple icon images are saved in the directory specified by the extended setup information file.

[0096] After the icon image is downloaded, it is stored in a directory specified by the extended setup information file 700. However, it is possible that the directory specified by the extended setup information file is not an area that the print setting extension application 312 can access.

[0097] Therefore, in this embodiment, the OS 313 further stores the stored icon image in a predetermined directory. The predetermined directory is, for example, QueuePropertyBag (not shown). QueuePropertyBag is an architecture installed in Windows, and is a data store for defining properties or data BLOBs (Binary Large OBjects) for read-only use by drivers and applications.

[0098] However, in this case, the icon image may be stored for each extended setup information, not for each queue, or the area may not be differentiated when multiple icon images are acquired. In this way, the print setting extension application 312 can use the icon image acquired when the extended setup information file 700 is installed.

[0099] Next, the OS 313 transmits a request to the application management service 331 to acquire an application whose application ID matches the application ID identified from the extended setup information file 700 (S3017).

[0100] If the application management service 331 stores a print setting extension application corresponding to the requested application ID, the application management service 331 returns the print setting extension application 312 to the client terminal 101 (S3018). The print setting extension application 312 sent in S3018 is an application identified by the application ID.

[0101] The OS 313 installs the acquired print setting extension application 312 in association with the print queue on the client side (S3019). Specifically, an application ID is stored in the registry of the OS 313 as print queue information, and when the generated print queue is called, the OS 313 uses this information to start the installed print setting extension application 312.

[0102] If the application management service 331 does not hold a print setting extension application corresponding to the requested application ID, the OS 313 completes the installation of the cloud print driver and stops the application installation process (S3020). The process up to S3020 is related to the installation of the print setting extension application 312.

[0103] After the print setting extending application 312 is installed in the OS 313, the print setting extending application 312 is started by the user (S3021). The print setting extending application 312 is started by being selected by the user on an application list screen or a menu screen provided by the OS 313. Note that the print setting extending application may be started at a timing other than the above.

[0104] When the print setting expanding application 312 is started, it acquires the icon image stored in S3016 (S3022). The process executed by the print setting expanding application 312 in S3022 will be described later with reference to FIG.

[0105] The print setting extension application 312 displays the acquired icon image on the application (S3023).

[0106] The above is a series of steps for registering the cloud print-compatible printer 104 in the cloud print service 321, generating a print queue that uses the cloud print service 321 in the client terminal 101, and installing the print setting extension application 312.

[0107] Next, a flow of installing the local printer driver 313 and the print setting extension application 312 will be described with reference to Fig. 13. The same reference numerals as in Fig. 3 are used to denote the steps of performing the same processes as in Fig. 3.

[0108] In S1301, the OS 313 searches for printers connected to the network 107. In S1302, the printer 106 responds to the search sent by the OS 313. The OS 313 displays a list of the responding printers and accepts the selection of the printer from the user. In S1303, the OS 313 sends a capability information acquisition request to the printer selected by the user. In S1303, the OS 313 inquires about the capability information of the printer 106 using a Get-Printer-Attributes operation defined in IPP. In S1304, the printer 106 responds with the capability information. In S1305, the OS 313 installs the local printer driver 313 and generates a print queue that associates the local printer driver 313 with the device identification information and capability information of the printer 106.

[0109] The subsequent processes are the same as those in FIG. 3, and the acquisition of the icon image and the like are also the same as in the case where the cloud printer driver 311 is used.

[0110] In FIG. 1 of this embodiment, the cloud print-compatible printer 104 and the printer 106 are described as different printers. The cloud print-compatible printer 104 may be capable of printing print data generated by the local printer driver 313. For example, assume that the client terminal 101 and the cloud print-compatible printer 104 are connected to the same network. When the client terminal 101 performs a printer search using a search function of the OS, it detects the cloud print-compatible printer 104. When the user selects the cloud print-compatible printer 104 from the search results, the OS generates a print queue that transmits the print data generated by the local printer driver 313 to the cloud print-compatible printer 104 without going through the cloud print service 321. The print queue generation process and the installation process of the print setting extension app 312 are the same as those in FIG. 13.

[0111] FIG. 14 is a schematic diagram for explaining a print process using the print setting extension application 312 installed in the client terminal 101 in the sequence of FIG. 3 or FIG.

[0112] The print setting extension application 312 stores software modules 1404 to 1409 and shared information 1410. Each module will be described below.

[0113] The file generation application is an application for processing document data, data for presentation, spreadsheets, etc., and is installed on the client terminal 101 to output image data to be printed.

[0114] The print data generation software 1402 is software provided by the OS 313 of the client terminal 101. The print data generation software 1402 executes a process of converting the value of the print setting into an attribute value defined by a predetermined protocol, and a process of converting the image data output by the file generation application 1401 into data of a predetermined format. The predetermined protocol is, for example, Internet Printing Protocol. The predetermined format is, for example, PDF or PWG-Raster. The print capability information 1403 is device capability information of the cloud print compatible printer 104 and the printer 106. The print capability information 1403 is also called PDC. The OS 313 executes the Get-Printer-Attributes operation of IPP to acquire functions (attribute information) and setting values ​​(attribute values) that can be used by the printer 106. The OS 313 writes the acquired attribute information and attribute values ​​that can be interpreted by the OS 313 into the print capability information 1403. Print settings and capability information based on the print function information 1403 are provided to a file generation application 1401 and a print setting extension application 312 .

[0115] Here, the printing device connected to the client terminal 101 will be described as the printer 106, but the cloud print server 102 may be connected instead of the printer 106.

[0116] The print setting extension application 312 provides four main functions: extension of print function information 1403, display of a print setting screen, editing of print data, and display of a management screen of a printing device.

[0117] First, the extension of the print function information 1403 will be described. The capability information acquisition unit 1408 communicates with the printer 106 to acquire the capability information of the printer 106. The capability information acquisition unit 1408 acquires the capability information from the printer 106 using the Get-Printer-Attributes operation. The OS 313 also has a function for acquiring capability information from the printer 106, but the capability information acquisition unit 1408 can also acquire capability information about setting items and setting values ​​that the OS 313 does not acquire. For example, the capability information acquisition unit 1408 acquires capability information about a user-defined paper size registered in the printer by the user and about stapleless binding, which binds paper without using staples. The capability information acquired by the capability information acquisition unit 1408 is written to the print function information 1403 by the print function extension unit 1406.

[0118] Next, the display of the print setting screen by the print setting extension application 312 will be described. For example, the file generation application 1401 displays the print setting screen shown in FIG. 15. 1501 is an area for selecting a print queue to be used for printing. 1502 is an area for the file generation application 1401 to display based on capability information provided by the OS 313, and accepts settings for the number of copies, paper size, and color mode. 1502 is displayed using PrintCapabilities generated based on the print function information 1403. 1503 displays a preview image of a file output by the file generation application. 1504 is an object for starting the print setting extension application 312 corresponding to the print queue selected in 1501. When the user selects 1504, a start instruction is input to the print setting extension application 312. The print setting screen extension unit displays the print setting screen shown in FIG. 16.

[0119] The print setting screen extension unit 1404 acquires PrintCapabilities and PrintTicket based on the print function information 1403 from the OS 313, and displays the print setting screen shown in FIG. 16. The PrintCapabilities include settable functions and setting values. The PrintTicket describes the setting values ​​set for each function. 1601 is displayed based on the PrintCapabilities and PrintTicket acquired from the OS 313. The print setting screen shown in FIG. 16 is scrollable, and objects for setting setting items that are not displayed are displayed by scrolling the screen. In the print setting screen shown in FIG. 16, setting values ​​can be set for setting items that cannot be set on the print setting screen provided by the file generation application 1401 or the OS 313. Setting items that cannot be set on the print setting screen provided by the file generation application 1401 or the OS 313 include, for example, setting items related to bookbinding printing and setting items for stapleless binding.

[0120] An object 1602 is used to confirm the print settings set via the print setting screen provided by the print setting screen extension unit 1404 and to instruct the end of displaying that screen. When 1602 is selected, the print setting screen extension unit 1404 writes the setting values ​​set via the screen shown in Fig. 16 to the PrintTicket. This completes the process related to displaying the print setting screen.

[0121] Next, editing of print data will be described. When 1505 in Fig. 15 is selected, the file generation application 1401 outputs image data to be printed. The file generation application 1401 outputs data in GDI format or data in XPS format. When the data output by the file generation application 1401 is data in GDI format, the OS 313 converts the data output by the file generation application 1401 into intermediate data in XPS format. The OS 313 starts the skip control unit 1405. The skip control unit 1405 notifies the print data generation software 1402 of a flag indicating whether or not PDL data generation is to be performed by the print data generation software 1402.

[0122] When an instruction to skip the PDL data generation process is given, print data generation software 1402 converts the setting values ​​written in the PrintTicket to attribute values ​​defined in IPP, and sends the converted attribute values ​​and intermediate data to print data editing unit 1407. When an instruction to skip the PDL data generation process is not given, print data generation software 1402 performs processing to convert the intermediate data to PDL data. It sends the converted PDL data and information in which the PrintTicket has been converted into attribute values ​​defined in IPP to print data editing unit 1407.

[0123] The print data editing unit 1407 edits the PDL data received from the print data generation software 1402. Editing the PDL data includes layout processing for consolidating image data of multiple pages onto one page, and processing for adding an image or character string specified by the user to the image data. Furthermore, the print data editing unit 1407 converts setting values ​​included in the PrintTicket acquired from the OS 313 that have not been converted by the print data generation software 1402 into attribute values ​​defined in the IPP into attribute values ​​defined in the IPP.

[0124] If skip control unit 1405 has instructed print data generation software 1402 to skip the PDL data generation process, print data editing unit 1407 converts the intermediate data into PDL data. The converted PDL data is sent to printer 106 together with the attribute values ​​converted by print data generation software 1402 and print data editing unit 1407. This completes the process of editing and sending print data.

[0125] Next, the display of the management screen of the printing device will be described. The management screen of the printing device is displayed in the following two situations. The first is when the OS 313 receives a notification from the printer 106, the user selects a pop-up display displayed by the OS 313, and the OS 313 notifies the notification unit 1409 according to the selection. The other is when an instruction to start the print setting extension application 312 is given from the home screen provided by the OS 313. In this case, the management screen display unit 1411 operates and displays the management screen shown in FIG. 8. FIG. 8 displays the print queues stored in association with the print setting extension application 312. From the screen shown in FIG. 8, it is possible to check the status of consumables of each printing device and status information indicating whether printing is possible. Furthermore, when a print queue is selected, the device setting screen of the corresponding printing device may be displayed. In this embodiment, the management screen display unit 1411 displays an image corresponding to the printing device associated with the print queue using an icon image acquired from an online support service.

[0126] 9 is a flowchart showing a process in which the print setting extension application 312 displays an icon image acquired from the online support service 351. The process shown in the flowchart in FIG. 9 is realized by the CPU 212 executing a program provided by the print setting extension application 312.

[0127] 9 is started by the management screen display unit 1411 being executed in response to a user operation starting up the print setting extending application 312. The user selects the print setting extending application 312 from a menu screen provided by the OS 313, and starts up the print setting extending application 312.

[0128] The CPU 212 receives a list of print queues stored in association with the print setting extension application 312 from the OS 313 (S901). The list of print queues includes the names of the print queues.

[0129] The CPU 212 determines whether there is any print queue included in the print queue list received from the OS 313 and for which icon images have not been acquired (S902). If icon images have been acquired for all print queues acquired from the OS 313, the CPU 212 proceeds to step S911, which will be described later. If there is any print queue for which icon images have not been acquired, the CPU 212 proceeds to step S903.

[0130] The CPU 212 selects one print queue for which an icon image has not been acquired, and refers to the extended setup information file of the selected print queue to determine whether an icon image is stored (S903). The CPU 212 determines whether the icon image specified in the extended setup information file is stored in the QueuePropertyBag.

[0131] If the extended setup information file contains DeviceIconProperty, the CPU 212 determines that an icon image is stored. On the other hand, if the extended setup information file does not contain DeviceIconProperty, the CPU 212 determines that an icon image is not stored. If it is determined in S903 that an icon image is not stored, the CPU 212 executes the process described in S904.

[0132] The CPU 212 acquires a default icon image provided by the OS 313 (S904). The CPU 212 acquires a default icon image prepared by the OS 313 using an API provided by the OS 313, and stores the default icon image in an area that the print setting extending application 312 can refer to in association with the print queue. In the present embodiment, it has been described that an icon image provided by the OS 313 is used when there is no printer-specific icon image. When there is no printer-specific icon image, a default image previously stored by the print setting extending application 312 may be acquired as an icon image and stored in association with the print queue.

[0133] The CPU 212 determines whether or not there are multiple icon images specified in the extended setup information file (S905). The CPU 212 refers to AddProperty of DDInstall in the extended setup information file. If multiple DeviceIconProperty are written as AddProperty, the CPU 212 determines that there are multiple icon images. On the other hand, if there is only one DeviceIconProperty, the CPU 212 executes the process described in S906.

[0134] The CPU 212 acquires the icon image acquired from the online support service 351, and stores the icon image in an area accessible by the print setting extension application 312 in association with the print queue (S906). The CPU 212 acquires the icon image specified by the file name of the icon image described in the extended setup information file from the QueuePropertyBag. In this embodiment, the CPU 212 acquires the icon image from the QueuePropertyBag, but the CPU 212 may acquire the icon image from a directory in which the icon image is stored.

[0135] If the extended setup information file includes information on a plurality of icon images, the CPU 212 determines whether the printer driver linked to the print queue is the cloud printer driver 311 (S907).

[0136] If the printer driver associated with the print queue is not the cloud printer driver 311, the CPU 212 executes the process described in S908. The CPU 212 acquires an icon image for local printing, and stores the image in an area that the print setting extension application 312 can refer to in association with the print queue (S908). The CPU 212 acquires an icon image with a file name specified by LocalDeviceIconProperty in the extended setup information file from the QueuePropertyBag. The CPU 212 stores the acquired icon image in an area that the print setting extension application 312 can refer to in association with the print queue. Note that, although the icon image is read from the QueuePropertyBag in this embodiment, the icon image may be acquired from a directory in which the CPU 212 has saved the icon image. If the driver associated with the print queue is the local printer driver 313, an icon image of only the printer image is acquired as shown in FIG. 5B.

[0137] If the printer driver associated with the print queue is the cloud printer driver 311, the CPU 212 executes the process described in S909. The CPU 212 acquires an icon image of the file name specified by CloudDeviceIconProperty in the extended setup information file from the QueuePropertyBag. The CPU 212 stores the acquired icon image in an area that can be referenced by the print setting extension application 312 in association with the print queue (S909). Note that, although the icon image is read from the QueuePropertyBag in this embodiment, the icon image may be acquired from a directory in which the CPU 212 has saved the icon image. If the driver associated with the print queue is the cloud printer driver 311, the icon image in FIG. 5(a) is acquired.

[0138] The CPU 212 determines whether or not there is a print queue for which icon image acquisition has not been completed in the print queue list received from the OS 313 (S910). If there is a print queue for which icon image acquisition has not been completed, the CPU 212 selects one print queue for which icon image acquisition has not been completed and returns the process to S903. By repeating the processes of S903 to S910, it is possible to acquire an icon image for a print queue linked to the print setting extension application 312.

[0139] If there is no print queue for which acquisition of an icon image has not been completed, the CPU 212 advances the process to step S911.

[0140] The CPU 212 displays the print queues and icon images on the display unit 216 (S911). Reference numeral 801 in Fig. 8 represents an example in which the print setting extending application 312 displays an icon image. Fig. 8 shows a state in which one print setting extending application 312 is linked to four print queues.

[0141] A print queue 802 is a print queue linked to the local printer driver 313, and the icon image shown in Fig. 5(b) is displayed. A print queue 803 is a print queue linked to the cloud printer driver 311, and the icon image shown in Fig. 5(a) is displayed. By changing the image depending on the linked printer driver, it becomes easy to identify which print queue is linked to which printer driver on the screen displayed by the print setting extension application 312.

[0142] The print queues 804 and 805 are assigned icon images that are assigned when an icon image cannot be acquired from the online support service 351. The icon images associated with the print queues 804 and 805 are the icon images assigned in S904 of Fig. 9. When a default icon image is assigned, the icon image is also changed depending on whether the printer driver associated with the print queue is the cloud printer driver 311 or the local printer driver 313. In this way, it is possible to distinguish and display which print queue is connected to the cloud print service 321.

[0143] The icon images acquired in S904, S906, S908, and S909 may be stored, and the next time the print setting extension application 312 is launched, the process may proceed to No in S902, and the screen may be displayed without acquiring the icon images.

[0144] 9 has described the process when the print setting extending application 312 is started from a home screen provided by the OS. When the print setting extending application 312 is started from a screen provided by a file generation application that generates document data, data for presentation, or the like, the print setting extending application 312 may acquire an icon image. When a predetermined user operation is accepted on a screen displayed by the file generation application, the process shown in FIG. 9 is executed. At this time, in S901, all print queues associated with the print setting extending application 312 are not notified, but one print queue selected by the file generation application is notified to the print setting extending application 312. The print setting extending application 312 executes the process from S902 onward for the notified one print queue.

[0145] 9 may be performed when the print setting extending application 312 is started from a print setting screen provided by the OS 313, instead of from a file generation application. In this case, similarly to when the print setting extending application 312 is started from a file generation application, in S901, one print queue selected by the OS 313 is notified to the print setting extending application 312. The print setting extending application 312 executes the processes from S902 onward for the notified one print queue.

[0146] In this way, a method of acquiring one icon image has been presented in which the icon image to be acquired is changed depending on the extended setup information and the type of driver.

[0147] In the above embodiment, the case has been described where an icon image is stored in an area called QueuePropertyBag, and the print setting extending application reads and uses the icon image. The storage destination of the icon image is not limited to the above. For example, a storage area for each print queue may be prepared in the storage unit 214. At this time, the CPU 212 stores the icon image acquired in S3014 of FIG. 3 in a storage area provided for each print queue. The print setting extending application 312 acquires the icon image from the storage area of ​​the print queue associated with the application.

[0148] The acquired icon image may be stored in a DLL file. In this case, an API for acquiring the icon image using the print queue as an argument may be prepared, and the print setting extension application 312 may acquire the icon image using the API. Also, instead of using the above-mentioned API, the icon image may be acquired using an API that uses the file path where the icon image is stored as an argument. For example, it is assumed that the print queue information is managed as shown in FIG. 11. Reference numeral 1101 in FIG. 11 is a screen that displays the print queue information provided by the OS of the client terminal 101. Property 1102 indicates which information related to the print queue is displayed in Value 1103. Here, it is "Class icon Path", and it indicates that the file path where the icon image is stored is displayed in Value 1103. The print setting extension application 312 may acquire the icon image from the location indicated by the Value of Classicon Path.

[0149] As described above, in this embodiment, a method has been described in which the print setting extension application 312 acquires and displays an icon image acquired when installing a generic printer driver that is different from the printer driver of the vendor that provides the printer. In this embodiment, by changing the icon image according to the type of printer driver used, it becomes possible for the user to visually recognize that the print queues used have different functions.

[0150] <Embodiment 2> In the first embodiment, a case where two icon images, one for local printing and one for cloud printing, are linked to an extended setup information file, has been described. In the second embodiment, a method for displaying the icon image for local printing and the icon image for cloud printing in a distinguishable manner, even if the only icon image linked to the extended setup information file is the icon image for local printing, will be described.

[0151] For example, this assumes a case where a printer does not originally support cloud printing and does not have an icon image with a cloud as shown in Figure 5(a), but the printer later becomes compatible with cloud printing through an update to its firmware.

[0152] 10 is a flowchart showing the processing that is realized by the CPU 212 executing a program provided by the print setting extending application 312 in the second embodiment. Note that the hardware configuration of each device is the same as that of the first embodiment, and the same reference numerals as those of the first embodiment are used for blocks showing the same processing as that of the first embodiment.

[0153] In S907, the CPU 212 determines whether the printer driver associated with the print queue is a cloud printer driver. If the printer driver associated with the print queue is a cloud printer driver, the CPU 212 determines whether an icon image for cloud printing is stored (S1001). For example, the CPU 212 refers to the extended setup information file, and if "CloudDeviceIconProperty" exists in "AddProperty", it determines that an icon image for cloud printing is stored.

[0154] When it is determined that the icon image for cloud printing is not stored, the CPU 212 generates an icon image for cloud printing using the icon image for local printing (S1002). The CPU 212 refers to the extended setup information file and acquires the icon image for local printing from the registry or QuepropertyBag. The icon image for local printing is, for example, the image shown in FIG. 5(b). Furthermore, the CPU 212 acquires the image shown in FIG. 5(c) from a storage area that the print setting extension application 312 can reference. Here, an image of a cloud is described as an example of an image indicating the use of the cloud print service, but other images may be used. For example, an image showing the logo of the cloud print service may be used. The CPU 212 adds the image shown in FIG. 5(c) stored in the print setting extension application 312 to the acquired image for local printing, and stores the image in a storage area that the print setting extension application 312 can reference. In this way, even if the image shown in FIG. 5(a) is not included in the extended setup information file, the icon image for local printing and the icon image for cloud printing can be displayed separately.

[0155] This allows the print setting extending application 312 to display icon images corresponding to queues of different models. Also, even if the queues are of the same model, different icon images can be displayed depending on whether the driver linked to the queue is a local printer driver or a cloud printer driver. Also, the print setting extending application 312 acquires icon images using the mechanism of an extended setup information file that links the print setting extending application 312 to a standard driver. In this way, the latest icon images can be provided to the user without updating the print setting extending application 312. Furthermore, this eliminates the need for the print setting extending application 312 to hold a large number of icon images, which is expected to prevent the application from becoming heavy and lead to improved user convenience.

[0156] (Other Examples) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions.

Claims

1. a first acquisition step of acquiring an icon image of the first printer based on identification information acquired from the first printer; a second acquisition step of acquiring an icon image of the second printer based on identification information of the second printer acquired from the server; a first control step of displaying the acquired icon image of the first printer and the acquired icon image of the second printer on a display means; An application characterized by causing an information processing device to execute the above.

2. The application according to claim 1, characterized in that the information processing device is caused to execute a second control step of causing the display means to display a print setting screen for setting print settings to be sent to the first printer without going through the server.

3. The application according to claim 2, characterized in that the information processing device is caused to execute a third control step of causing the display means to display a print setting screen for setting print settings to be transmitted to the second printer via the server.

4. 3. The application according to claim 2, wherein the print settings set by the application are provided to an operating system of the information processing apparatus.

5. 5. The application according to claim 4, wherein the print settings are used in generating print data by a printer driver provided by a vendor of the operating system.

6. 6. The application according to claim 5, wherein the print data includes print settings defined in a predetermined protocol, and is transmitted to the first printer in accordance with the predetermined protocol.

7. 7. The application according to claim 6, wherein the predetermined protocol is the Internet Printing Protocol.

8. an acquisition means for acquiring an icon image of a first printer based on identification information acquired from the first printer, and acquiring an icon image of a second printer based on identification information of a second printer acquired from a server; a control means for displaying the acquired icon image of the first printer and the acquired icon image of the second printer on a display means; An information processing device having the above configuration.

9. a first acquisition step of acquiring an icon image of the first printer based on identification information acquired from the first printer; a second acquisition step of acquiring an icon image of the second printer based on identification information of the second printer acquired from the server; a first control step of displaying the acquired icon image of the first printer and the acquired icon image of the second printer on a display means; 13. A method for controlling an information processing apparatus comprising the steps of:

Citation Information

Patent Citations

  • Application for providing print setting screen

    JP2022089143A