WO2020110767A1 - 情報処理装置、サーバ装置、制御方法、制御プログラム - Google Patents

情報処理装置、サーバ装置、制御方法、制御プログラム Download PDF

Info

Publication number
WO2020110767A1
WO2020110767A1 PCT/JP2019/044805 JP2019044805W WO2020110767A1 WO 2020110767 A1 WO2020110767 A1 WO 2020110767A1 JP 2019044805 W JP2019044805 W JP 2019044805W WO 2020110767 A1 WO2020110767 A1 WO 2020110767A1
Authority
WO
WIPO (PCT)
Prior art keywords
printer driver
application
image forming
extended application
information processing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2019/044805
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
洋史 菊地
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Canon Inc
Original Assignee
Canon Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Canon Inc filed Critical Canon Inc
Priority to CN201980077365.5A priority Critical patent/CN113168296B/zh
Priority to EP19890441.9A priority patent/EP3893102B1/en
Publication of WO2020110767A1 publication Critical patent/WO2020110767A1/ja
Priority to US17/328,424 priority patent/US11625205B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1202—Dedicated interfaces to print systems specifically adapted to achieve a particular effect
    • G06F3/1203—Improving or facilitating administration, e.g. print management
    • G06F3/1205—Improving or facilitating administration, e.g. print management resulting in increased flexibility in print job configuration, e.g. job settings, print requirements, job tickets
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1223—Dedicated interfaces to print systems specifically adapted to use a particular technique
    • G06F3/1224—Client or server resources management
    • G06F3/1225—Software update, e.g. print driver, modules, plug-ins, fonts
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1223—Dedicated interfaces to print systems specifically adapted to use a particular technique
    • G06F3/1229—Printer resources management or printer maintenance, e.g. device status, power levels
    • G06F3/123—Software or firmware update, e.g. device firmware management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1278—Dedicated interfaces to print systems specifically adapted to adopt a particular infrastructure
    • G06F3/1285—Remote printer device, e.g. being remote from client or server
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1223—Dedicated interfaces to print systems specifically adapted to use a particular technique
    • G06F3/1229—Printer resources management or printer maintenance, e.g. device status, power levels
    • G06F3/1231—Device related settings, e.g. IP address, Name, Identification

Definitions

  • the present invention relates to an information processing device, a server device, etc. that communicate with an image forming device.
  • An operating system is installed in the host computer, the printer driver is configured according to the specifications defined by the OS, and is called by the OS to operate.
  • a vendor who provides a printing apparatus can provide a means for instructing a printer to print using the OS by providing a printer driver suitable for the printing apparatus that conforms to the specifications of the OS.
  • a printer driver called a universal printer driver is known as a printer driver for controlling a plurality of types of printing apparatuses having different functions (Patent Document 1).
  • the universal printer driver as disclosed in Patent Document 1 is provided for each vendor that provides a printing device. However, it is difficult for one universal printer driver to support printing devices of vendors that provide different printing devices.
  • Non-Patent Document 1 a so-called common printer driver that uses a mechanism compliant with IPP typified by the above-mentioned IPP Everywhere (registered trademark) (Non-Patent Document 1).
  • an information processing apparatus in which a printer driver can be installed and which can communicate with a server apparatus and an image forming apparatus, a receiving unit that receives identification information of the image forming apparatus and a receiving unit that receives the receiving information.
  • the transmitting means for transmitting the identification information of the image forming apparatus to the server apparatus, and the identification information of the image forming apparatus which is the extended application transmitted from the server apparatus and transmitted by the transmitting means.
  • An information processing apparatus having an execution unit that executes processing for associating the corresponding extended application with the printer driver is disclosed as an example.
  • an extended application that can utilize the function of the image forming apparatus can be associated with a predetermined printer driver.
  • FIG. 3 illustrates an example of a printing system according to the first exemplary embodiment. It is a block diagram which shows the hardware constitutions of a client computer. It is a block diagram which shows the software structure of a client computer.
  • FIG. 3 is a diagram showing a relationship with a printer, a printer queue, and a print extension application.
  • FIG. 9 is a flow chart of association between printer queue generation and a print extension application. It is a related flowchart of a printer driver and a print extension application of the related art.
  • FIG. 6 is a flow chart of associating a printer driver and a print extension application according to the embodiment. It is a flowchart of the process which an extended application search server performs.
  • FIG. 6 is a correspondence table between a printer HWID and a print extension application. It is a figure which shows an example of the printing system in 2nd Embodiment.
  • FIG. 7 is a flow chart of associating a common printer driver with a print extension application. It is a flowchart of the process which an extended application delivery server performs.
  • FIG. 8 is a flowchart of a process of determining whether the print extension application supports a printer queue.
  • FIG. 1 is a diagram showing an example of a printing system according to the present invention.
  • the printing system according to the present exemplary embodiment includes a client computer 101, a printer A 102 that receives print data in a page description language (PDL) format, and performs printing, and various servers.
  • the various servers specifically include a distribution server 105 that distributes the extended application and a search server 106 that acquires a desired extended application from the distribution server 105. Further, it includes a driver distribution server 107 that distributes the driver, and a metadata distribution server 308 that distributes a device management unit (hereinafter, referred to as metadata) associated with the driver.
  • the devices can communicate with each other through a network 104 including a Wide Area Network (WAN).
  • WAN Wide Area Network
  • the printers 102 and 103 may be single-function printers having only a printing function or multifunction printers having a printing function, a scanning function, and a copying function.
  • the client computer 101 is not limited to one unit, but a plurality of client computers 101 may be connected to the network 104.
  • the client computer 101 can send print data to the printer 102 or the like.
  • the printer driver may be a scanner driver.
  • the printer extension application may be a scanner extension application.
  • FIG. 2 is a block diagram showing the hardware configuration of the client computer 101 of FIG.
  • the client computer 101 has a CPU (Central Processing Unit) 201, a RAM (Random Access Memory) 202, an external memory 209, and a ROM (Read Only Memory) 203.
  • CPU Central Processing Unit
  • RAM Random Access Memory
  • ROM Read Only Memory
  • the control unit 200 including the CPU 201 controls the operation of the entire client computer 101.
  • the CPU 201 expands a program stored in the ROM 203 or the external memory 209 in the RAM 202, and executes the program to perform various controls such as control of a UI screen, generation of print data, and transfer of print data.
  • the ROM 203 stores a control program, a boot program, etc. that can be executed by the CPU 201.
  • the RAM 202 is a main memory of the CPU 201, and is used as a work area or a temporary storage area for developing various programs.
  • the external memory 209 connected to the control unit 200 via the external memory I/F 208 stores the OS 210, the application 212, the application execution environment 213, the printer driver 211, and the like.
  • an auxiliary storage device such as a HDD (Hard Disk Drive) is assumed as the external memory 209, but a nonvolatile memory such as SSD (Solid State Drive) may be used instead of the HDD.
  • a nonvolatile memory such as SSD (Solid State Drive) may be used instead of the HDD.
  • the hardware such as the CPU 201, the ROM 203, the RAM 202, and the external memory 209 configures a so-called computer.
  • the operation input device I/F 204 is an interface that controls the operation input device 205 such as a keyboard, a pointing device (mouse), and a touch input device.
  • the operation input device 205 functions as a reception unit that receives an operation from the user.
  • the display I/F 206 controls the display of the screen on the display 207.
  • the display 207 functions as a display unit that displays information to the user.
  • the control unit 200 is connected to the network 104 via the network I/F 214.
  • the network I/F 214 transmits print data to a printer on the network 104 and receives extended applications and printer drivers from various servers on the network 104.
  • the data communication with the external terminal on the network 104 is, for example, wireless communication conforming to the IEEE 802.11 series, mobile communication system such as LTE or 5G, or communication via a cable such as a LAN cable.
  • the software in the client computer 101 is composed of three layers, an OS 210, an application execution environment 213, and an application 212.
  • the OS 210 is mainly composed of a printing system 337, a printer driver 211, an external setting file group 352, and a thread pool 355.
  • the metadata 320 included in the external setting file group 352 has a print extension application identifier of the print extension application 300 and an HWID (HardwareId) identifier of the printer queue 308 of the printer driver 211, and has a role of associating each.
  • HWID HardwareId
  • the printer driver 211 made by Microsoft (registered trademark) and the print extension application 300 cannot be associated with each other by the metadata 320.
  • the registry 353 is an area in which a setting group of the OS 210 is described. Values can be entered in the Key And Value system, and settings for each printer queue can be entered. In the registry 353, a policy setting indicating whether to activate or deactivate the background task activation by the print activation application launcher 350, the identifier of the print extension application 300 associated with the printer driver 211, and the like are registered. There is. The settings registered in the registry 353 can be changed via the setting screen of the OS 210.
  • the printer queue 308 is an area where a print job is temporarily stored when printing is performed using a printer existing in the network 104, and a plurality of printer queues 308 can exist. In this embodiment, it is assumed that printer queues corresponding to the printers 102 and 103 have been created.
  • the spooler 325 is a module that temporarily stores and manages an XPS (XML Paper Specification) file that is print target data printed from any of the applications 212.
  • the XPS file saved in the spooler 325 is converted to PDL (Page Description Language) through the filter pipeline manager 335, and then transmitted to the printer 102 through the spooler 325.
  • PDL Peage Description Language
  • the filter pipeline manager 335 is a module that loads one or more filters 330 and converts an XPS file into a PDL file.
  • the filter pipeline manager 335 is configured as a part of the print architecture (also referred to as a print system) provided by the OS 210.
  • the OS 210 reads one or more filters 330, which are one of the elements configuring the printer driver 211, based on the definition of the filter config 336, and generates a PDL using the one or more filters.
  • the PDL for example, PCL or PDF can be adopted.
  • the configuration module 331 is a module that creates and changes a PrintTicket (also called a print ticket). Further, the module 331 has a prohibition function of restricting settings that cannot be combined. The configuration module also manages PrintCapabilities, which is printer capability information.
  • the detailed print setting UI unit 304, the print activation background task unit 305, and the print activation UI unit 303 of the print extension application 300 can call the API provided by the configuration module 331. By calling the API, each unit can acquire the PrintTicket and PrintCapabilities in the XML (Extensible Markup Language) format.
  • XML Extensible Markup Language
  • the printer driver 211 provides the OS 211 with a device function text file 332 in which prohibition rules and device functions are described and a script file 333.
  • the operation of the configuration module 331 is customized based on the files 332 and 333.
  • the print start application launcher 350 is a module that controls the execution of the background task provided by the print start background task unit 305 and the like.
  • the launcher 350 activates the print-time activation background task unit 305 when the OS 210 detects that the user has input a print start instruction and performs printing. If the registry 353 stores a setting for disabling the activation of the background task, the OS 210 suppresses the execution of the background task.
  • the printer driver 211 includes a filter 330, a filter config 336, a script file 333, a device function text file 332, and an INF 361, and is stored in the driver storage area 370.
  • the filter 330 is a filter called by the filter pipeline manager 335, and has a function of converting the input XPS file into PDL and outputting it.
  • the filter config 336 is a definition file referenced by the filter pipeline manager 335, and describes the order of calling one or more filters 330.
  • the script file 333 and the device function text file 332 are files called by the configuration module 331, and the operation of the configuration module 331 can be customized.
  • the INF 361 is a text file in which setting information for installing the printer driver 211 is described.
  • the thread pool 355 is a module that stores threads used when various modules of the applications 212 and the OS 210 are executed.
  • the application execution environment 213 includes a desktop application execution environment 323 and a touch application execution environment 301.
  • the touch application execution environment 301 is an execution environment for executing the touch application 321 and the print extension application 300 that operate on the OS 210, which is a type of application 212 described later.
  • the execution environment 301 is an execution environment for operating the extended application distributed from the distribution server 105, and controls the execution of the extended application.
  • the desktop application execution environment 323 is an execution environment for executing a desktop application 322 which is a kind of the application 212 described later.
  • the desktop application execution environment 323 controls execution of applications that can be executed from the desktop.
  • the application 212 includes three types of applications: a touch application 321, a print extension application 300, and a desktop application 322.
  • the touch application 321 is an application that operates in the touch application execution environment 301.
  • the touch application 321 is downloaded and installed in the client computer 101 through an application distribution system published on the Internet.
  • the touch application 321 is packaged and signed with a necessary module group, and calls to the API in the OS 210 are restricted.
  • the print extension application 300 is a kind of the touch application 321, and operates on the touch application execution environment 301 similarly to the touch application 321.
  • the OS 210 acquires the print extension application 300 from the application distribution system via the Internet.
  • the print extension application 300 according to the present embodiment has a print UI display function for displaying a customized UI when printing.
  • the print extension application 300 can be associated with the printer driver 211 provided by the printer vendor via the metadata 320. Further, in the case of being associated with a common printer driver commonly used for printers provided by a plurality of printer vendors, the association is performed using the INF 361 and the registry 353. This will be described later with reference to FIG.
  • the print extension application 300 includes a tile application unit 302, a detailed print setting UI unit 304, a print activation background task unit 305, and a print activation UI unit 303.
  • the tile application unit 302 is a UI unit that is executed in response to receiving a user operation for starting the extension application 300, and provides functions such as status display of registered printers.
  • the detailed print setting UI unit 304 is a UI unit that is executed in response to the reception of the detailed print setting event issued by the OS 210.
  • the detailed print setting UI unit 304 generates and displays a print setting UI based on PrintTicket and PrintCapabilities acquired from the configuration module 331 through the API.
  • the UI unit 304 appropriately changes the setting of PrintTicket according to the user operation, and returns it to the configuration module 331.
  • the background task part 305 activated at the time of printing is a component corresponding to the background task to be executed when a print event is issued.
  • the task provided by the task unit 305 has a limited lifetime and is forcibly terminated by the OS 210 after a certain period of time has elapsed.
  • the background task unit 305 activated at the time of printing can acquire and read/write the PrintTicket through the API of the configuration module 331. It is defined that the background task determines whether or not to activate the print-time activation UI unit 303, and requests the OS 210 to activate the print-time activation UI unit 303, which is a component of the foreground task, as necessary. .. Further, by reading/writing the changed value to/from the app store 334, the value can be transferred to/from the print start UI unit 303. If the launcher 350 determines not to activate the print activation UI unit 303, the launcher 350 generates print data without activating the print extension application 300.
  • the print startup UI unit 303 started by the background task can edit the XPS or PrintTicket, which is the data to be printed, and return it to the OS 210.
  • the OS 210 boots the print boot UI unit 303.
  • the print startup UI unit 303 can acquire the PrintTicket and PrintCapabilities and change the setting, and can also acquire the XPS file of the data to be printed.
  • the print activation UI unit 303 displays a UI for confirming the printing, a UI for allowing the user to input a setting that has not been input, and the like.
  • the setting file 362 is a file in which setting values of the print extension application 300 are described.
  • a print extension application identifier uniquely indicating the print extension application 300 and a custom setting file to be used are described.
  • the custom setting file 363 is a setting file that describes service settings that the print extension application 300 can use for the printer driver 211.
  • the common printer driver is, for example, a common printer driver compatible with a printer compatible with Mozilla (registered trademark) that can perform printing using IPP.
  • a user having a printer compatible with Mozilla (registered trademark) can easily perform printing using the common printer driver without installing a printer driver manufactured by a printer vendor.
  • the common printer driver does not depend on the printer vendor, it can be similarly used for the printer of any printer vendor.
  • FIG. 4 is a diagram showing a relationship between the print queues 502 and 503 of the common printer driver for the printer A 102 and the printer B 103 and the print extension application 300.
  • the printer queue 502 of the common printer driver corresponds to the printer A 102
  • the printer queue 503 of the common printer driver corresponds to the printer B 103.
  • the common printer driver generates print data and issues a print job for both printers.
  • the common printer driver can acquire a certain amount of capability information from the printer A 102 and the printer B 103 and can perform print settings according to each capability.
  • the common printer driver has few types of print settings that can be set in order to support a plurality of printers of a plurality of vendors.
  • the print expansion application 300 supplements this.
  • the print extension application 602 for printer A is the print extension application 300 specialized for printer A
  • the print extension application 603 for printer B is the print extension application 300 specialized for printer B.
  • the print extension application 300 is created by a printer vendor.
  • the common printer driver is software that does not depend on the type of printer, but the print extension application 300 can make finer print settings for each printer.
  • a flow for associating the print extension application 300 according to the printer type with the common printer driver is required. The flow of association will be described later with reference to FIG. Note that “association” specifically means that the OS 210 registers the identifier of the print extension application 300 associated with the printer driver 211 in the registry 353, for example.
  • the identifier of the print extension application 300 to be associated with the identifier of the printer driver 211 can be registered in association with each other. It is possible to register not only a one-to-one correspondence table but also a plurality of extended applications in association with the printer driver 211.
  • the OS 21 can display the detailed print setting UI section of the associated print extension application 300 and the print start UI section 303 when the printer driver 211 is used.
  • FIG. 5 is a diagram showing a flow for associating the common printer driver with the print extension application.
  • FIG. 5 shows processing of the OS 210 of the client computer 101. The processing of the OS 210 described here is loaded into the RAM 202 and executed by the CPU 201.
  • the OS 210 searches for the printer in the network and displays it for the user (S101).
  • the printer is introduced into the OS 210, for example, a new printer is discovered on the network or the local interface and a predetermined event occurs. Alternatively, the printer installation may be started according to the user's instruction.
  • the OS 210 receives a user input from all the searched printers for which printer the printer driver 211 is to be installed (S102).
  • the OS 210 installs the printable printer driver 211 in the printer specified by the user and creates the printer queue 308 (S103).
  • the OS 210 acquires the print extension application 300 based on the HWID of the printer and associates it with the printer queue 308 generated in S103 (S105).
  • S105 printer queue 308 generated in S103
  • FIG. 6 is a flow chart showing the processing of the OS 210 as a comparative example regarding the processing of S105 in the OS 210.
  • the processing of the OS 210 described here is also loaded into the RAM 202 and executed by the CPU 201.
  • the OS 210 inquires of the metadata delivery server 108 whether the corresponding metadata 320 exists based on the HWID of the printer (S301).
  • the OS 210 confirms whether the metadata 320 exists (S302), and when it does not exist, the processing ends. If the metadata 320 corresponding to the HWID acquired in S104 exists, the OS 210 downloads the metadata 320 (S303). Then, the metadata 320 is associated with the printer queue 308 (S304).
  • the OS 210 refers to the downloaded metadata 320 and acquires the application identifier of the print extension application 300 from the metadata 320 (S305). Then, the OS 210 makes an inquiry about the print extension application 300 to the extension application distribution server 107 based on the application identifier (S306). The OS 210 confirms whether the print extension application 300 exists (S307). When it is confirmed in S307 that there is not, the processing ends. When it is confirmed that the print extension application 300 exists in S307, the OS 210 downloads the print extension application 300 (S308). Next, the OS 210 installs the downloaded print extension application 300 (S309). Further, the OS 210 associates the installed print extension application 300 with the printer queue 308 (S310). In this way, the printer queue 308 and the print extension application 300 are associated with each other via the metadata 320.
  • FIG. 7 is a flowchart showing the processing of the OS 210 in this embodiment regarding the processing of S106 of FIG. 5 in the OS 210.
  • the processing of the OS 210 described here is also loaded into the RAM 202 and executed by the CPU 201.
  • the OS 210 inquires of the search server 106 whether or not the corresponding print extension application 300 exists based on the printer HWID acquired in S104 (S201).
  • the OS 210 confirms whether the print extension application 300 corresponding to the HWID exists (S202). If it is confirmed in S202 that it does not exist, the process ends.
  • the OS 210 downloads the print extension application 300 (S203).
  • the OS 210 confirms whether the downloaded print extension application 300 corresponds to the printer driver 211 (S204). Specifically, the OS 201 transmits the HWID of the printer acquired in S104 to the search server 106. In response to this, the OS 210 receives the list of print extension applications 300 corresponding to the HWID. As a result, it is confirmed in S202 whether there is an application corresponding to the HWID.
  • the OS 210 first acquires the corresponding driver identifier from the downloaded print extension application 300 (S801).
  • the print extension application 300 holds the identifier of the corresponding printer driver. As a result, the print extension application 300 can avoid being associated with an unexpected printer driver.
  • the OS 210 confirms whether the driver identifier of the printer queue 308 exists in the corresponding driver identifier (S802). When it is confirmed that the print queue exists in step S ⁇ b>802, the OS 210 determines that the print extension application 300 corresponds to the printer queue 308. If it is confirmed in step S ⁇ b>802 that it does not exist, the OS 210 determines that the print extension application 300 does not support the printer queue 308.
  • the OS 210 ends without associating.
  • the OS 210 installs the downloaded print extension application 300 (S205).
  • the OS 210 associates the installed print extension application 300 with the printer queue 308 (S206).
  • the OS 210 does not use the metadata 320 for associating the printer queue 308 and the print extension application 300, but directly associates them.
  • the printer queue 308 of the common printer driver made by Microsoft registered trademark
  • the OS 210 can also perform the process of FIG. 6 and the process of FIG. 7 separately when making the association. For example, whether the relevant metadata 320 exists in the metadata delivery server 108 or not may be used to determine whether to perform association using the metadata 320 or directly associate with the print extension application 300.
  • the printer driver to be associated is a vendor printer driver
  • the process of FIG. 6 may be performed
  • the printer driver is a common printer driver
  • the process of FIG. 7 may be performed. By doing so, it is possible to support the association with the common printer driver while utilizing the assets of the conventional metadata 320.
  • the extended search server can have a hardware configuration similar to that of FIG. Specifically, this is a process performed by the search server 106 when the OS 210 of the client computer 101 inquires the print extension application 300 corresponding to the HWID in S201 of FIG.
  • the processing of the search server 106 described here is loaded into the RAM existing in the search server 106 and executed by the CPU in the search server 106.
  • the search server 106 accepts a request for the print extension application 300 with an HWID from any client computer 101 (S401).
  • the search server 106 acquires the correspondence table between the HWID and the print extension application held therein (S402).
  • the search server 106 holds the correspondence table between the printer HWID and the print extension application shown in FIG.
  • the printer HWID 501 is a unique ID for each printer model, and different IDs are provided for different printer models.
  • the print extension application name 502 is the name of the print extension application and is a name that can be easily identified by general users.
  • the application identifier (AppID) 503 is an identifier managed by the distribution server 105, and the distribution server 105 can specify the corresponding print extension application 300 from all extension applications by the application identifier.
  • the correspondence table shown in FIG. 10 can be updated every time the print extension application 300 is newly developed and registered. For example, the update correspondence table is transmitted from the external device to the distribution server 105 via the network. Then, the old correspondence table can be updated in the distribution server 105 using the new correspondence table.
  • a printer vendor can simultaneously register one HWID of a printer to be associated when registering one print extension application 300. Furthermore, a plurality of application identifiers may be provided for the HWID of one printer. In any case, the registered content is added to the correspondence table of FIG. In the example of FIG. 10, one application identifier is registered for each printer. Also, for example, PrinterAAA may be allowed to appear twice in column 501. This means providing a plurality of extended printer applications for one printer.
  • the search server 106 When the search server 106 obtains the correspondence table, the search server 106 confirms whether the print extension application 300 corresponding to the HWID received from the client computer 101 exists in the correspondence table (S403).
  • the search server 106 searches the table of FIG. 10 and confirms that the identifier of the application corresponding to PrinterAAA is AAA01. Then, the search server 106 can notify the client of AAA01 and the print extension application name PrintAppAAA.
  • the HWID here is acquired by the client computer from the printer.
  • the search server 106 returns an error to the requesting client computer 101 (S409), and ends the processing. If it is confirmed in S403 that the print extension application 300 exists, the search server 106 acquires the application identifier of the print extension application 300 (S404). Then, the search server 106 inquires of the distribution server 105 about the print extension application 300 based on the application identifier (S405). The search server 106 confirms whether the print extension application 300 requested by the distribution server 105 exists (S406). If it is confirmed in S406 that it does not exist, the search server 106 returns an error to the requesting client computer 101 (S409).
  • the search server 106 downloads the print extension application 300 (S407). Then, the search server 106 enables the acquired print extension application 300 to be downloaded from the requesting client computer 101 (S408). Then, in step S408, the client computer is notified of the list of downloadable print extension applications 300.
  • the print extension application may be listed in multiple lists. In response to this notification, the client computer may automatically confirm that the print extension application 300 exists and download it (S308).
  • the search server 106 performs the process of FIG.
  • the distribution server 105 can provide the appropriate print extension application 300 for both the common printer driver and the printer driver manufactured by the printer vendor without changing the operation.
  • the method in which the search server 106 downloads the actual print extension application 300 in advance in S407 has been described.
  • S407 it is also possible to adopt a method of enabling download from the extended application distribution server after the acquisition request from the client computer 101 arrives without downloading.
  • the processing flow performed by the distribution server 105 will be described with reference to FIG. Specifically, the process is performed by the distribution server 105 when the client computer 101 makes an inquiry to the distribution server 105 in S306 of FIG. 7 or when the search server 106 makes an inquiry to the distribution server 105 in S405 of FIG.
  • the processing of the distribution server 105 described here is loaded into a RAM (not shown) existing in the distribution server 105 and executed by a CPU (not shown) in the distribution server 105.
  • the distribution server 105 receives a print extension application request by an application identifier from any client computer 101 or search server 106 (S501). When the request arrives, the distribution server 105 confirms whether the print extension application 300 having the application identifier is held (S502).
  • the distribution server 105 If not stored, the distribution server 105 returns an error to the requesting client computer 101 or the search server 106 (S501) and ends the processing. If it is held, the distribution server 105 identifies the print extension application 300 having the specified application identifier (S503). Then, the distribution server 105 enables the specified print extension application 300 to be downloaded from the request source (S501). In this way, the distribution server 105 may perform the same processing regardless of the request source. When downloadable, the extended application can be downloaded in response to a request from the client computer 101.
  • the same reference numerals denote the same devices and functions unless otherwise specified.
  • the description will focus on the parts that are different from the first embodiment.
  • the example in which the search server 106 performs the process of searching for the print extension application 300 corresponding to the HWID has been described.
  • the existence of the search server 106 is not essential.
  • the distribution server 105 can also be implemented by having the function of the search server 106, it will be described as a second embodiment. That is, it is possible that 105 and 106 are integrated.
  • FIG. 11 shows the configuration of the printing system in the second embodiment. Although the configuration is almost the same as that of FIG. 1 in the first embodiment, the difference is that the search server 106 does not exist. Since the details of each component have been described above, they are omitted here. The contents described with reference to FIGS. 2 to 5 and 7 in the first embodiment can also be applied to the second embodiment, and the description thereof will be omitted.
  • FIG. 12 is a flowchart showing in more detail the process of S105 of FIG. 5 in the OS 210 of the client computer 101.
  • the processing of the OS 210 described here is also loaded into the RAM 202 and executed by the CPU 201.
  • the difference from FIG. 7 is S601.
  • the point where the OS 210 makes an inquiry about the existence of the print extension application 300 based on the HWID of the printer is not the search server 106 but the distribution server 105 (S601). Since the other processes (S602 to S606) are the same as the processes (S202 to S206) in the first embodiment, the description thereof will be omitted.
  • the OS 210 of the client computer 101 performing such processing, it is not necessary to separately set up the search server 106 in the system.
  • FIG. 12 shows a flow performed by the distribution server 105 when the client computer 101 makes an inquiry to the distribution server 105 in S306 of FIG. 6 or S601 of FIG.
  • the processing of the distribution server 105 described here is loaded into a RAM (not shown) existing in the distribution server 105 and executed by a CPU (not shown) in the distribution server 105.
  • the distribution server 105 receives a print extension application request from any client computer 101 (S701).
  • the distribution server 105 confirms whether the request is a print extension application request by the application identifier (S702).
  • the distribution server 105 identifies the print extended application 300 having the designated application identifier from the print extended applications 300 held by itself (S703).
  • the distribution server 105 then confirms whether the request is a print extended application request by HWID (S704).
  • the distribution server 105 identifies the print extended application 300 having the specified HWID from the print extended applications 300 held by itself (S705). Then, the distribution server 105 confirms whether or not it owns the specified print extension application 300 (S706). If it is held, the distribution server 105 enables the specified print extension application to be downloaded from the requesting client computer 101 (S707). If it is not held, the distribution server 105 returns an error to the client computer 101 that made the request (S702).
  • the client computer 101 which is an example of an information processing device, can install a printer driver 211, which is an example of a printer driver. Further, it is possible to communicate with the distribution server 105, which is an example of a server device. It is also possible to communicate with the printer A 102 and the printer B 103, which are examples of image forming apparatuses.
  • the printer driver 211 may be a common printer driver or a universal printer driver that can support a plurality of printers.
  • the network I/F 214 receives the HWID, which is an example of the identification information of the image forming apparatus. Further, the network I/F 214 transmits the HWID received via the network I/F 214 to the distribution server 105.
  • the network I/F 214 is an example of transmitting means and receiving means.
  • the print extension application 300 is an example of an extension application.
  • the print extension application 300 transmitted from the distribution server 105 and also the print extension application 300 corresponding to the HWID transmitted by the network I/F 214 is referred to as a program A.
  • the CPU 201 executes a process of associating the program A with the printer driver 211.
  • the CPU 201 is an example of execution means.
  • the client computer 101 may check whether the print extension application 300 transmitted from the distribution server 105 corresponds to the printer driver 211.
  • the print extension application 300 may be installed on condition that it is confirmed to be compatible.
  • An example of the identification information of the print extension application 300 is an application identifier.
  • the application identifier may be transmitted to the distribution server 105, and the receiving unit may receive the print extension application 300 corresponding to the identification information from the distribution server 105. Further, the print extension application 300 may be acquired through different routes depending on whether the printer driver installed in 101 is a common printer driver that can be used by the plurality of printers A and B or not.
  • An example of the control unit is the CPU 201.
  • Multiple print extension applications can be associated with the HWID that is the printer identification information. Further, the CPU 201 may execute a process of associating the plurality of print extension applications corresponding to the transmitted HWID with the printer driver 211.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Accessory Devices And Overall Control Thereof (AREA)
  • Facsimiles In General (AREA)
  • Stored Programmes (AREA)
PCT/JP2019/044805 2018-11-30 2019-11-15 情報処理装置、サーバ装置、制御方法、制御プログラム Ceased WO2020110767A1 (ja)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201980077365.5A CN113168296B (zh) 2018-11-30 2019-11-15 信息处理装置、服务器装置、控制方法、以及控制程序
EP19890441.9A EP3893102B1 (en) 2018-11-30 2019-11-15 Information processing device, server device, control method, and control program
US17/328,424 US11625205B2 (en) 2018-11-30 2021-05-24 Information processing apparatus, server apparatus, control method, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2018225490A JP7282507B2 (ja) 2018-11-30 2018-11-30 情報処理装置、サーバ装置、制御方法、制御プログラム
JP2018-225490 2018-11-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/328,424 Continuation US11625205B2 (en) 2018-11-30 2021-05-24 Information processing apparatus, server apparatus, control method, and storage medium

Publications (1)

Publication Number Publication Date
WO2020110767A1 true WO2020110767A1 (ja) 2020-06-04

Family

ID=70853138

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2019/044805 Ceased WO2020110767A1 (ja) 2018-11-30 2019-11-15 情報処理装置、サーバ装置、制御方法、制御プログラム

Country Status (5)

Country Link
US (1) US11625205B2 (enExample)
EP (1) EP3893102B1 (enExample)
JP (1) JP7282507B2 (enExample)
CN (1) CN113168296B (enExample)
WO (1) WO2020110767A1 (enExample)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022118733A1 (ja) * 2020-12-03 2022-06-09 キヤノン株式会社 情報処理装置、ならびに、印刷設定アプリケーション
JP7682682B2 (ja) * 2021-04-16 2025-05-26 キヤノン株式会社 情報処理装置、情報処理装置の制御方法、ならびにコンピュータプログラム
JP2023059509A (ja) * 2021-10-15 2023-04-27 シャープ株式会社 情報処理装置
JP2024072109A (ja) * 2022-11-15 2024-05-27 キヤノン株式会社 印刷システム、情報処理装置、制御方法、並びにプログラム

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004151816A (ja) * 2002-10-29 2004-05-27 Konica Minolta Holdings Inc ホスト装置
JP2006260356A (ja) * 2005-03-18 2006-09-28 Ricoh Co Ltd 画像形成システム、画像形成装置、端末装置、管理装置及び端末装置のドライバの更新方法
JP2014219736A (ja) * 2013-05-01 2014-11-20 キヤノン株式会社 管理システム、管理システムの制御方法、及びプログラム
JP2015135658A (ja) 2013-12-16 2015-07-27 キヤノン株式会社 情報処理装置、情報処理方法、及びコンピュータプログラム
JP2017027322A (ja) * 2015-07-22 2017-02-02 キヤノン株式会社 情報処理装置及びプログラム

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4371673B2 (ja) * 2003-02-28 2009-11-25 キヤノン株式会社 プログラムインストール方法およびサーバ装置
JP4196782B2 (ja) * 2003-08-26 2008-12-17 セイコーエプソン株式会社 画像処理装置及び画像処理をコンピュータに実行させる画像処理プログラム
GB2482903A (en) * 2010-08-19 2012-02-22 Software Imaging Technology Ltd A print engine
US8773674B2 (en) * 2010-09-17 2014-07-08 Xerox Corporation Method and apparatus to provide enhanced printing for newly launched devices in a universal printer driver
JP5943571B2 (ja) * 2011-09-09 2016-07-05 キヤノン株式会社 印刷システム、プリンター、プリントサーバー、及びその方法
JP5174268B1 (ja) * 2011-10-14 2013-04-03 キヤノン株式会社 ネットワークシステム及びクライアント装置とその方法
JP2014056353A (ja) * 2012-09-11 2014-03-27 Canon Inc 情報処理装置、プログラム、インストール方法
JP6080593B2 (ja) * 2013-02-19 2017-02-15 キヤノン株式会社 情報処理装置及びその方法
JP6184212B2 (ja) * 2013-07-12 2017-08-23 キヤノン株式会社 情報処理装置および制御方法およびプログラム
US9894230B2 (en) * 2014-05-30 2018-02-13 Kyocera Document Solutions Inc. Image formation device which can be expanded and image forming method for expanding an image formation device
US10942686B2 (en) * 2018-11-19 2021-03-09 Palo Alto Research Center Incorporated Printer recommendation system
JP7275760B2 (ja) * 2019-03-29 2023-05-18 ブラザー工業株式会社 画像処理システム

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004151816A (ja) * 2002-10-29 2004-05-27 Konica Minolta Holdings Inc ホスト装置
JP2006260356A (ja) * 2005-03-18 2006-09-28 Ricoh Co Ltd 画像形成システム、画像形成装置、端末装置、管理装置及び端末装置のドライバの更新方法
JP2014219736A (ja) * 2013-05-01 2014-11-20 キヤノン株式会社 管理システム、管理システムの制御方法、及びプログラム
JP2015135658A (ja) 2013-12-16 2015-07-27 キヤノン株式会社 情報処理装置、情報処理方法、及びコンピュータプログラム
JP2017027322A (ja) * 2015-07-22 2017-02-02 キヤノン株式会社 情報処理装置及びプログラム

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
IPP IMPLEMENTOR'S GUIDE V2.0, Retrieved from the Internet <URL:https://ftp.pwg.org/pub/pwg/candidates/cs-ippig20-20150821-5100.19.pdf>
See also references of EP3893102A4

Also Published As

Publication number Publication date
US20210279016A1 (en) 2021-09-09
JP2020087324A (ja) 2020-06-04
CN113168296A (zh) 2021-07-23
EP3893102A4 (en) 2022-11-09
EP3893102A1 (en) 2021-10-13
EP3893102B1 (en) 2025-02-19
US11625205B2 (en) 2023-04-11
CN113168296B (zh) 2024-06-07
JP7282507B2 (ja) 2023-05-29

Similar Documents

Publication Publication Date Title
US11520546B2 (en) Print processing system and control method
JP7691456B2 (ja) プログラム、情報処理装置の制御方法及び情報処理装置
US8850459B2 (en) Information processing apparatus, information processing method, and program
JP4587132B2 (ja) 制御機器設定方法及びプログラム
US11625205B2 (en) Information processing apparatus, server apparatus, control method, and storage medium
US10089102B2 (en) Information processing apparatus, method, and program
US10356267B2 (en) Information processing apparatus, control method, and storage medium
US20120281251A1 (en) Method and system for configuring printer drivers for multiple printing devices
US20150356380A1 (en) System, printing apparatus, control method, and recording medium
US8670135B2 (en) Information processing apparatus and control method when installing a printer driver
JP2011159232A (ja) 画像処理装置、消耗品発注方法、及び消耗品発注プログラム
US8345273B2 (en) Information processing apparatus for managing an expansion module, control method therefor, and program for executing the method
JP2009181337A (ja) 画像形成システム、管理装置、画像形成装置、画像形成方法、及び画像形成プログラム
EP2234014A2 (en) Information processing apparatus, information processing method, and information processing system
JP7604529B2 (ja) 情報処理装置および制御方法およびプログラム
JP7585381B2 (ja) 情報処理装置および制御方法およびプログラム
JP2021043547A (ja) 情報処理装置および情報処理装置の制御方法ならびにプログラム
US12197798B2 (en) Information processing apparatus registers printer driver for a selected image forming apparatus with administrator authority, control method of information processing apparatus, and non-transitory computer-readable storage medium
JP7756698B2 (ja) 情報処理装置とその制御方法、およびコンピュータプログラム
US20250013401A1 (en) Image forming apparatus communicably connected with management server managing application, method for controlling image forming apparatus, storage medium, and management system
JP7071189B2 (ja) 情報処理装置、情報処理装置の制御方法及びプログラム
JP2006154908A (ja) 単一ドライバ印刷システム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19890441

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019890441

Country of ref document: EP

Effective date: 20210630