JP2008066887A - Image processor, image processing method, and image processing program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an image processor easy to add or change a part of a function, by separating physical management from logical management for the function. <P>SOLUTION: The image processor can add a plug-in having a filter arranged at each processing composed of jobs related to image processing. The image processor comprises a plug-in management means for registering and managing a plug-in which actualizes basic functions possessed by the image processor and a plug-in having the filter and a filter management means for registering and managing information for the filter. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an image processing apparatus, an image processing method, and an image processing program.

  Conventionally, in an image processing apparatus having a plurality of functions, such as an image forming apparatus, a device is provided for each function, and further, a control means such as software for controlling these devices and a means for processing an image are required. . In recent years, as the functions of image processing apparatuses have diversified and the types and grades of image processing apparatuses have increased, the number of combinations of devices included in the image processing apparatuses has increased. Therefore, it is necessary to develop a control means and a means for processing an image for each of these combinations, and the labor or time involved in the development has increased. Thus, a technique for efficiently developing an image processing apparatus and increasing the productivity of the image processing apparatus is disclosed.

For example, in Japanese Patent No. 3679349 (Patent Document 1), in an image forming apparatus which is an example of an image processing apparatus, a function realizing unit is divided into a function specific unit and a unit commonly used between the functions. Accordingly, a technique for efficiently developing an image forming apparatus and improving the productivity of the image forming apparatus is disclosed. More specifically, an application such as a printer application, a copy application, or a scanner application is provided for each function of the image forming apparatus, and a service module is provided for each service commonly used in a plurality of applications. According to the configuration of Patent Document 1, when a device that realizes the function of the image forming apparatus is added or changed, the corresponding application is added or updated without affecting other applications. Can be added or changed.
Japanese Patent No. 3679349

  However, in the technology such as the image forming apparatus disclosed in Patent Document 1, each time the function of the image forming apparatus is added or changed, in addition to the application corresponding to the added function, the application It is necessary to change the service module and user interface related to the system, and there is a problem that the effect of reducing the labor related to development is small.

  For example, in Patent Document 1, when an operation panel included in an image processing apparatus is changed, it may be necessary to change all user interfaces related to applications included in the image processing apparatus.

  In the above-mentioned Patent Document 1, there is another problem that when the application means or service module is changed, the image forming apparatus must be restarted, and the configuration of the apparatus is not easily changed.

  The present invention has been invented in order to solve these problems in view of the above points, and is an image processing apparatus in which functions can be easily added or changed. An object of the present invention is to provide an image processing apparatus in which a part of functions can be easily added or changed by separating the management.

  In order to achieve the above object, the image processing apparatus of the present invention employs the following configuration.

  An image processing apparatus according to the present invention is an image processing apparatus capable of adding a plug-in having a filter provided for each process constituting a job related to image processing, and manages the plug-in by registering and managing the plug-in And filter management means for registering and managing information related to the filter.

  Accordingly, it is possible to provide an image processing apparatus having both a physical management unit and a logical management unit.

  In order to achieve the above object, the plug-in management unit included in the image processing apparatus of the present invention includes a plug-in address holding unit that holds an address where the plug-in is stored, and a filter included in the plug-in. And a plug-in management table holding means for holding a plug-in management table for managing an operation object corresponding to the operation.

  Accordingly, it is possible to provide an image processing apparatus having a plug-in having a filter and means for physically managing the operation of the filter.

  In order to achieve the above object, the filter management means included in the image processing apparatus of the present invention is a filter management table holding means for holding a filter management table for managing functions of the filter and functional objects corresponding to the functions. It can be set as the structure which has these.

  Thereby, an image processing apparatus having means for logically managing the function of the filter can be provided.

  In order to achieve the above object, the image processing apparatus of the present invention further includes a case where a user interface corresponding to the filter is included in a plug-in different from the filter, and the image When the processing device is activated or when a plug-in having the filter is added, the plug-in managing means registers and manages the plug-in having the filter and the plug-in having the user interface. Can be configured.

  Accordingly, it is possible to provide an image processing apparatus that updates the contents of a managed plug-in when the image processing apparatus is activated and when a plug-in is added.

  In order to achieve the above object, the image processing apparatus of the present invention further includes a case where a user interface corresponding to the filter is included in a plug-in different from the filter, and the image When the processing apparatus is activated or when a plug-in having the filter is added to the image processing apparatus, the filter management unit registers and manages the filter, and the filter acquires the user interface. It is possible to configure so as to have UI management means for managing them.

  Thereby, when the filter and the UI of the filter are included in different plug-ins, it is possible to provide an image processing apparatus that manages the UI of the filter.

  In order to achieve the above object, the image processing apparatus of the present invention further includes a case where a user interface corresponding to the filter is included in a plug-in different from the filter, and the plug When deleting a plug-in, the plug-in managing means deletes the registration of the plug-in having the filter and the plug-in having the user interface, and the filter managing means is configured to delete the registration of the filter. Can do.

  Thereby, when a filter is deleted, it is possible to provide an image processing apparatus that deletes registration of a filter UI managed by the filter.

  In order to achieve the above object, the image processing method of the present invention is an image processing method in an image processing apparatus to which a plug-in having a filter provided for each process constituting a job related to image processing can be added. The plug-in management step for registering and managing the plug-in and the filter management step for registering and managing the information related to the filter can be employed.

  In order to achieve the above object, the image processing method of the present invention is further characterized in that the plug-in management step includes a plug-in address holding step for holding an address where the plug-in is stored, and the plug-in includes: And a plug-in management table holding step for holding a plug-in management table for managing an operation object corresponding to the operation of the filter.

  In order to achieve the above object, in the image processing method of the present invention, the filter management step further includes a filter management table for holding a filter management table for managing the function of the filter and a function object corresponding to the function. It can be set as the structure which has a holding step.

  In order to achieve the above object, the image processing method of the present invention further includes a case where a user interface corresponding to the filter is included in a plug-in different from the filter, and the image When the processing apparatus is activated or when a plug-in having the filter is added, the plug-in management step registers and manages the plug-in having the filter and the plug-in having the user interface. Can be configured.

  In order to achieve the above object, the image processing method of the present invention further includes a case where a user interface corresponding to the filter is included in a plug-in different from the filter, and the image When a processing device is activated or a plug-in having the filter is added to the image processing device, the filter management step registers and manages the filter, and the filter acquires the user interface. It is possible to adopt a configuration having a UI management step to be managed.

  In order to achieve the above object, the image processing method of the present invention further includes a case where a user interface corresponding to the filter is included in a plug-in different from the filter, and the plug When deleting a plug-in, the plug-in management step deletes the registration of the plug-in having the filter and the plug-in having the user interface, and the filter management step is configured to delete the registration of the filter. Can do.

  In order to achieve the above object, the image processing program of the present invention can be configured as an image processing program for causing a computer to execute the image processing method according to any one of claims 7 to 12. .

  According to the image processing apparatus of the present invention, it is an image processing apparatus in which a function can be easily added or changed, and a part of the function is added or changed by separating physical management and logical management of the function. Can be provided.

  Embodiments of the present invention will be described below with reference to the drawings.

(Example of configuration of means for executing job of MFP 1)
FIG. 1 shows an example of the configuration of a means for executing a job of the image processing apparatus of the present invention. FIG. 1 is an example of a software configuration for realizing a job of a multifunction peripheral (hereinafter referred to as “MFP”) 1 as an image processing apparatus. Here, the MFP refers to an image forming apparatus that realizes a plurality of functions such as a printer, a copy, a scanner, or a facsimile in a single casing.

  In FIG. 1, the software in the MFP 1 includes a user interface unit 10, a control unit 20, a function implementation unit 30, a device service unit 40, and a device control unit 50. 1 is based on the calling relationship between the units. That is, basically, the upper layer in the figure calls the lower layer.

  The user interface unit 10 is a part on which a function for receiving an execution request for a job (for example, copying, printing, scanning, facsimile transmission) is implemented. For example, the user interface unit 10 is referred to as a local user interface (hereinafter referred to as “local UI”). ) Unit 11 and communication server unit 12. For example, the local UI unit 11 receives a request input via an operation panel (not shown). The communication server unit 12 receives a request via a network from a client PC (not shown), for example. The request accepted by the user interface unit 10 is transmitted to the control unit 20.

  The control unit 20 is a part in which a function for controlling processing for executing a requested job is implemented. The control unit 20 includes, for example, a plug-in management unit 210 and a request management unit 220. The plug-in management unit 210 manages a physical address such as a unit for executing a job mounted on the MFP 1 and an operation of the unit.

  In the present embodiment, the “plug-in” managed by the plug-in management unit 210 is a program or device corresponding to a function newly added to the basic function of the MFP 1 and the MFP 1 has. Includes programs or devices that support basic functions. That is, the plug-in management unit 210 is a unit that manages physical addresses of programs or devices corresponding to basic functions and additional functions of the MFP 1 and their operations.

  The request management unit 220 connects the filters included in the function realization unit 30 according to the requested job, and controls the execution of the job based on the connected filter. In the present embodiment, the “job of MFP1” is synonymous with a service in one unit (until a request is input and a final output is obtained) provided to the user by MFP1, Software is synonymous with an application that provides a single unit of service.

  The function implementation unit 30 is a part on which a component group that executes a part of a job provided in the MFP 1 is mounted. That is, one job is expressed by combining components in the function realization unit 30. In the present embodiment, each component is referred to as a “filter”. This is because the software architecture is based on an architecture called “pipe & filter” when the means for executing jobs of the MFP 1 is implemented by software.

  FIG. 2 is a diagram for explaining the concept of the pipe and filter architecture. In FIG. 2, “F” indicates a filter, and “P” indicates a pipe. As shown in the figure, each filter is connected by a pipe. The filter converts the input data and outputs the result. The pipe transmits the data output from the filter to the next filter.

  In the MFP 1 according to the present embodiment, each function is regarded as a series of “conversions” for a document (data). An MFP job can be generalized as being composed of document input, processing, and output. Therefore, “input”, “processing”, and “output” are regarded as “conversion”, and a software component that realizes one “conversion” is configured as a filter. Each filter is independent, and basically there is no dependency relationship (call relationship) between the filters. Therefore, it is possible to add (install) or delete (uninstall) in units of filters.

  In FIG. 1, the function implementation unit 30 includes a plurality of filters and filter management means 330 that manages the filters. The filter management unit 330 is a unit that manages, for each filter described later, a function of the filter and an object that realizes the function in association with each other.

  The function realizing unit 30 further includes a reading filter 301, a stored document reading filter 302, a mail receiving filter 303, a facsimile receiving filter 304, a PC document receiving filter 305, and a report filter 306 as filters for realizing input.

  The reading filter 301 controls reading of image data by the scanner and outputs the read image data. A stored document read filter 302 reads document data (image data) stored in the storage device of the MFP 1 and outputs the read data. The mail reception filter 303 receives an e-mail and outputs data included in the e-mail. The facsimile reception filter 304 controls facsimile reception and outputs received print data. The report filter 306 outputs setting information, history information, and the like of the MFP 1 as, for example, data formatted in a table format.

  The function implementation unit 30 also includes a document processing filter 311 and a document conversion filter 312 as filters that realize processing of image data. The document processing filter 311 performs predetermined image conversion processing (aggregation, enlargement, reduction, etc.) on the input data and outputs it. The document conversion filter 312 converts the data format of the image data. The document conversion filter 312, for example, performs rendering processing, that is, converts the input PostScript data into bitmap data and outputs it.

  The function implementation unit 30 also includes a print filter 321, a stored document registration filter 322, a mail transmission filter 323, a facsimile transmission filter 324, a PC document transmission filter 325, and a preview filter 326 as filters that realize output.

  The print filter 321 causes the plotter to output (print) the input data. The stored document registration filter 322 stores the input data in a storage device in the MFP 1, for example, a hard disk device. The mail transmission filter 323 transmits the input data attached to the e-mail. The facsimile transmission filter 324 transmits the input data by facsimile. The PC document transmission filter 325 transmits the input data by facsimile. The preview filter 326 causes the input data to be preview-displayed on an operation panel (not shown) via the local UI unit 11.

  The device service unit 40 is a part in which lower-level functions that are used in common are mounted from each filter in the function realization unit 30, and includes a data management unit 41. The data management unit 41 represents various databases. For example, it corresponds to a database in which user information is registered, a database in which documents or image data are stored, and the like.

  The device unit 50 includes a unit that controls a device provided for each device included in the MFP 1.

(Functional configuration diagram related to registration of plug-in and filter of MFP 1)
FIG. 3 is a diagram illustrating an example of a functional configuration related to registration of a plug-in included in the MFP 1 and registration of a filter included in the plug-in. The user interface unit 10, the control unit 20, and the like of the MFP 1 illustrated in FIG. And it is an example of the functional configuration of the user interface unit 10a, the control unit 20a, and the function realization unit 30a corresponding to the function realization unit 30.

  3 includes a filter management plug-in 339 and a filter plug-in 340. The filter plug-in 349 is, for example, a software unit when adding a filter to the MFP 1. The filter plug-in 349 includes a filter 340 and a plug-in registration request unit 344. The filter plug-in 349 may further include a plurality of filters and may have a user interface corresponding to the filter 340.

  The filter 340 includes an action object acquisition unit 341 and a filter registration request unit 342. The filter 340 may further include user interface management means (hereinafter referred to as “UI management means”) 343. The filter 340 also includes a main processing unit (not shown) that executes the function of the filter 340.

  The action object acquisition unit 341 is a unit that acquires action objects of other filters managed by the plug-in management unit 210. Acquiring an operation object of another filter is, for example, a program that acquires an execution program for operating another filter, or sets an instruction for operating another filter and outputs it to another filter Is to get. As a result, one filter can make an operation request to another filter or other means via the plug-in management means 210.

  The filter registration request unit 342 is a unit that requests the filter management unit 330 to register the filter 340 when the filter plug-in 349 is added to the MFP 1 or when the MFP 1 is activated. The filter registration request unit 342 makes a registration request for the function of the filter 340 and a function object corresponding to the function. The filter registration request unit 342 makes a registration request for the filter 340 by acquiring the filter registration object 332. Acquisition of the filter registration object 332 is performed by the action object acquisition unit 341.

  The UI management unit 343 is a unit that manages a user interface corresponding to the filter 340. In FIG. 3, the user interface corresponding to the filter 340 is included in a plug-in different from the filter plug-in 349. However, the image processing apparatus of the present invention is not limited to this, and the filter 340 has the user interface. May be.

  The plug-in registration request unit 344 is a unit that requests the plug-in management unit 210 to register the filter 340 when the filter plug-in 349 is added to the MFP 1 or when the MFP 1 is activated. The plug-in registration request unit 344 makes a registration request for the action of the filter 340 and the action object. With the action object, another filter or the like can instruct the filter 340 to execute the process, set the process, or the like. When the filter 340 is implemented by, for example, object-oriented programming, the action object may be configured as a public service.

  The plug-in registration request unit 344 may also be configured to be included in the filter 340. Thereby, even in a plug-in including a plurality of filters, it is possible to realize a configuration in which a filter operation and an operation object registration request corresponding to the operation are made for each filter.

  The filter management plug-in 339 is a plug-in having filter management means 330. The filter management plug-in 332 may include a filter registration object 332. The filter management means 330 is a means for managing the function of the filter of the function realization unit 30a, and has a filter management table holding means 331. The filter management table holding unit 331 is a unit that holds a filter management table in which functions of filters such as the filter 340 and functional objects corresponding to the functions are registered. By referring to the filter management table, it is possible to know the functions of the MFP 1 and the function objects that realize the functions.

  The filter registration object 332 is an action object used when a filter such as the filter 340 is registered in the filter management unit 330. When the filter acquires the filter registration unit 332 via the plug-in management unit 210, the filter can be registered in the filter management unit 330.

  3 includes a plug-in management unit 210 and a request management unit 220. The plug-in management unit 210 includes a plug-in address holding unit 211 and a plug-in management table holding unit 212. The plug-in address holding unit 211 is a unit that holds and manages an address at which a plug-in already added to the MFP 1 is stored. The plug-in address holding unit 211 holds the name of the plug-in and the address where the plug-in is stored in association with each other.

  The plug-in management table 212 is means for registering and managing the operation of the filter included in the function realization unit 30a and the operation object corresponding to the operation. The operation of the filter is, for example, execution of processing for realizing the filter function or setting for the processing. The action object may be, for example, a program that receives an instruction to execute the process and outputs the instruction to the function object that realizes the function. The action object may also be a program for defining setting conditions for realizing the function.

  The request management unit 220 selects a filter that realizes a job execution request or the like input from the user interface unit 10a from the filters registered in the plug-in management unit 210, and performs a process of connecting them. It is. The request management unit 220 may further control the processing.

  The user interface unit 10 a includes a user interface plug-in (hereinafter referred to as “UI plug-in”) 119. The user interface unit 10a may further include a plug-in 139 of a filter user interface (hereinafter referred to as “UI”). The UI plug-in 119 is a means for realizing a user interface. In this embodiment, the user interface realized by the UI plug-in 119 is a local user interface such as an operation panel provided in the MFP 1, but the UI plug-in included in the image processing apparatus of the present invention is connected to the MFP 1. It may be a plug-in that realizes a communication server that displays on a client PC or the like and receives an input.

  The UI plug-in 119 includes a user interface 111 and a filter management table acquisition unit 112. The user interface 111 is a unit that implements a function of controlling display on a display unit such as an operation panel or receiving an instruction input from the input unit. The filter management table acquisition unit 112 is a unit that acquires the filter management table held by the filter management table holding unit 331. The filter management table acquisition unit 112 acquires a table from the filter management table holding unit 112 after all the filters included in the function implementation unit 30a are registered in the filter management table. The filter management table acquisition unit 112 acquires the filter management table after the filter is registered in the filter management table when the filter is added to the function implementation unit 30a.

  The filter UI plug-in 139 includes a filter UI 131. The filter UI 131 is means for realizing a user interface function corresponding to one of the filters of the function realizing unit 30a. The filter UI 131 includes, for example, display screen data to be displayed on the operation panel, and control means for receiving an instruction or the like input from the operation panel.

  4 and 5 are diagrams for explaining the logical correspondence between the filter and the UI of the filter.

  FIG. 4 shows an example in which the filter has a user interface function corresponding to the filter. In FIG. 4, the plug-in management unit 210 registers and manages each of the local UI unit 11, the request management unit 220, the data management unit 41, the filter management unit 330, and the memory 42 as one plug-in. On the other hand, the filter management means 330 registers and manages the filters 350a to 350c. The filters 350a to 350c have filter UIs 151a to 151c, respectively, and the UI of each filter is managed by the corresponding filter.

  FIG. 5 shows an example in which a filter and a user interface corresponding to the filter are included in different plug-ins. In FIG. 5, as in FIG. 4, the plug-in management unit manages the local UI unit 11, the request management unit 220, the data management unit 41, the filter management unit 330, and the memory 42, and further from the filter UI 161a. 161c is managed. On the other hand, the filter management means registers and manages the filters 360a to 360c. The filters 360a to 360c correspond to the filter UIs 161a to 161c, respectively.

  FIG. 6 is a diagram for explaining the physical configuration of the filter and the UI of the filter. FIG. 6A is a diagram for explaining a physical configuration in the case of FIG. 4, and the plug-in management unit 210 manages the filters 350a to 350c. On the other hand, FIG. 6B is a diagram for explaining the physical configuration in the case of FIG. 5. The plug-in management unit 210 manages the filters 360a to 360c, and further manages the filter UIs 161a to 161c. To do.

(Process when MFP 1 is activated (part 1))
FIGS. 7 to 15 are diagrams for explaining processing when the MFP 1 is activated, in which a filter and a UI of the filter are included in one plug-in.

  FIG. 7 is a sequence diagram illustrating an example of processing for registering a filter included in a plug-in in the plug-in management unit 210. In step S 101 of FIG. 7, the MFP 1 is turned on and an activation instruction is input to the plug-in management unit 210. Progressing to step S102 following step S101, the plug-in management unit 210 acquires a list of plug-ins whose addresses are held in the plug-in address holding unit 211.

  FIG. 8 is a list of plug-ins and plug-in addresses held by the plug-in address holding unit 211. In FIG. 8, the names of plug-ins that have been added (installed) to the MFP 1 are associated with the locations where the plug-ins are stored. In the example of FIG. 8, the path name of the file having the JAVA (registered trademark) execution format in the file system on the storage device is shown as the plug-in storage location. Is not limited to the example of FIG. For example, the plug-in may be a program described in another program language of JAVA (registered trademark) and converted into an execution format. For example, when the plug-in is configured as a program, the storage location may be an address such as a sector on the storage device.

  In step S103 following step S102 of FIG. 7, an instruction to generate the filter management unit 330 is output from the plug-in management unit 210, and the filter management unit 330 is generated. Note that “generation of means” means that when the means is configured as a program, the program is expanded (loaded) on the memory, and when the means is configured as hardware such as a device. Is to turn on the power of the apparatus.

  Progressing to step S104 following step S103, the filter management means 330 outputs a plug-in registration request to the plug-in management means 210. The registration request for the plug-in having means is an operation object registration request for the action and the action that the means has. Progressing to step S105 following step S104, the plug-in management unit 210 registers the operation of the filter management unit 330 in the plug-in management table.

  Proceeding to step S106 following step S105, the plug-in management unit 210 outputs an instruction to generate the filter 350a, and the filter 350a is generated. Note that “filter generation” means that when a plug-in having a filter is configured as a program, the program is loaded (loaded) on a memory. When the device is configured as hardware, the device is turned on.

  Progressing to step S107 following step S106, a plug-in registration request is output from the plug-in registration request unit included in the plug-in including the filter 350a to the plug-in management unit 210. The registration request for a plug-in having a filter is an operation object registration request corresponding to the operation and the operation of the filter. Progressing to step S108 following step S107, the plug-in management unit 210 registers the operation object corresponding to the operation of the filter 350a and the operation in the plug-in management table.

  Proceeding to step S109 following step S108, the plug-in management unit 210 outputs an instruction to generate the filter 350b, and the filter 350b is generated. Progressing to step S110 following step S109, a plug-in registration request is output from the plug-in registration request unit included in the plug-in including the filter 350b to the plug-in management unit 210. Progressing to step S111 following step S110, the plug-in management unit 210 registers the operation object corresponding to the operation of the filter 350b and the operation in the plug-in management table.

  Progressing to step S112 following step S111, the plug-in management unit 210 outputs an instruction to initialize the unit to the filter management unit 330, and the filter management unit 330 executes the initialization. Note that “initialization of means” means, for example, when a means is configured as a program, it is to initialize variables when the program is executed, and further, an initial value in one program It is a setting.

  Progressing to step S113 following step S112, the plug-in management unit 210 outputs an instruction to initialize the filter 350a to the filter 350a, and the filter 350a executes initialization. Note that “initialization of the filter” means that, for example, when the filter is configured as a program, a variable used when the program is executed is initialized, and the initial value in one program is It is a setting.

  Progressing to step S114 following step S113, the filter 350a sets a filter name. The setting of the filter name is a name of a function such as “print” or “read”. Subsequent to step S114, the process proceeds to step S115, where the filter 350a outputs a filter UI generation instruction to the filter UI 151a to generate the filter UI 151a. After the filter UI 151a is generated, an initialization instruction may be output from the filter 350a to the filter UI 151a in a step (not shown), and the filter UI 151a may perform initialization.

  The processing from step S116 to step S118 subsequent to step S115 is processing related to the filter 350b, and is the same processing as processing from step S113 to step S115, which is processing related to the filter 350a. .

  Note that in steps S101 to S118, the filter management unit 330, the filter 350a, and the filter 350b are generated, respectively, a plug-in registration request, and a plug-in management unit 210. The processing is performed in order, but the processing order among the filter management unit 330, the filter 350a, and the filter 350b is not limited and may be executed asynchronously.

  The plug-in management table included in the plug-in management unit 210 is generated by the processing from step S101 to step S118.

(Information output at the time of registration request to plug-in management means)
FIG. 9 shows information output when a registration request is made to the plug-in management means. FIGS. 9A and 9B are examples of tables output from the filter management unit 330 to the plug-in management unit 210 when a registration request is made by the filter management unit 330 in step S104 of FIG. is there. In the example of FIG. 9A, the operations of the filter management means 330 include “filter registration”, “filter search”, “filter deletion”, “filter update”, and “filter list acquisition”, and their operations. Is output to the plug-in management unit 210.

  In the example of FIG. 9B, the “filter management service” operation and an operation object corresponding to the operation are output at the time of a registration request as a window for receiving the operation of the filter management unit 330. When the operation of FIG. 9B is registered by the plug-in management unit 210, the unit that gives an instruction to the filter management unit performs “registration”, “search”, and “deletion” with respect to the “filter management service”. The filter management means operates by inputting an instruction of “update” or “list acquisition”.

  FIGS. 9C and 9D show the plug-in management means 210 from the plug-in registration request means included in the plug-in including the filter 350a at the time of the registration request made by the filter 350a in step S107 of FIG. It is an example of the table output. In the example of FIG. 9C, as the operation of the filter 350a, “UI acquisition of the filter 350a”, “setting of the filter 350a”, “execution of the filter 350a”, and operation objects corresponding to these operations are plug-in management. Output to means 210.

  In the example of FIG. 9D, the “filter 350a service” operation and an operation object corresponding to the operation are output as a window for receiving the operation of the filter 350a upon registration request. When the operation of FIG. 9D is registered by the plug-in management unit 210, the unit or the filter that gives an instruction to the filter 350a has “UI acquisition” “setting” or “filter 350a service”. By inputting an instruction such as “execute”, the filter 350a operates.

  The registration request may output the address or name of the motion object instead of the motion object, or the specification of the control command for the motion object.

(Example of plug-in management table)
FIG. 10 is an example of a plug-in management table held by the plug-in management table holding unit 212 included in the plug-in management unit 210. FIG. 10A is an example of a plug-in management table in which the operations of filters and means are listed, and is an example when the table of FIG. 9A or 9C is registered. FIG. 10B shows an example in which one service is registered as an operation as a window for each filter and means, and the table of FIG. 9B or 9D is registered. This is an example of the case.

(Sequence of an example of processing for registering a filter in the filter management means 330)
FIG. 11 is a sequence diagram illustrating an example of processing for registering a filter in the filter management unit 330. The processing in FIG. 11 is normally executed following the processing in steps S101 to S118 in FIG. 7, but must be executed at least after the filter management means 330 is registered in the plug-in management table. In step S201, the plug-in management unit 210 outputs an activation instruction to the filter management unit 330, and the filter management unit 330 is activated. Note that “means activation” means that when a means is configured as a program, the means is provided with other means in the MFP 1 or information on the operation of the filter, etc. This means setting the variables related to the means.

  Progressing to step S202 following step S201, the plug-in management unit 210 outputs an activation instruction to the filter 350a, and the filter 350a is activated. Note that “activation of a filter” means that if the filter is configured as a program, information about other means of the MFP 1 or the operation of the filter is given to the filter so that the filter This means setting the variables related to the means.

  Progressing to step S203 following step S202, a filter registration object acquisition request is output from the filter 350a to the plug-in management unit 210. Progressing to step S204 following step S203, a filter registration object is retrieved from the plug-in management table of the plug-in management table holding unit 212 of the plug-in management unit 210. Progressing to step S205 following step S204, the filter registration object is transmitted from the plug-in management means 210 to the filter 350a.

  Progressing to step S206 following step S205, the filter registration request unit included in the filter 350a outputs a registration request for the filter 350a based on the filter registration object to the filter management unit 330. The filter registration request is a function object registration request corresponding to a filter function and function.

  Progressing to step S207 following step S206, the filter management table holding unit 331 of the filter management unit 330 registers the filter 350a in the filter management table and starts management. The registration of a filter is registration of a function object corresponding to the function of the filter and the function.

  Through the above steps S202 to S207, the filter 350a is activated and registered in the filter management table.

  Steps S208 to S213 following step S207 are processes registered in the filter management table when the filter 350b is activated, and are the same as the processes related to the filter 350a from steps S202 to S207. Omitted.

  Note that in steps S202 to S213, the filter 305a and the filter 305b are respectively a startup step, a filter registration object acquisition request step, a step in which a filter registration object is searched by the plug-in management unit 210, and a filter registration object. The processing is performed in the order of the obtaining step, the filter registration request step, and the step in which the filter is registered by the filter management means 330. The processing is performed asynchronously regardless of the order of processing between the filters 305a and 305b. Also good.

(Example of filter management table)
FIG. 12 is an example of the filter management table. In FIG. 12, “read” and “print” are registered as the names of the functions of the filter, and “read object” and “print object” are registered as the corresponding objects.

(Sequence of an example of processing in which a local UI and request management means are registered in the plug-in management means 210)
FIG. 13 is a sequence diagram of an example of processing in which the operations of the local UI unit 11 and the request management unit 220 are registered in the plug-in management unit 210. In FIG. 13, following the power-on of the MFP 1 in step S101 and the acquisition of the plug-in list by the plug-in management unit 210 in step S102, in steps S303 to S310, the local UI unit 11 and the request management unit 220 are related. A generation step, a plug-in registration request step, a registration step by the plug-in management means, and an initialization step are performed. The processing in each of the local UI unit 11 and the request management unit 220 is the same as the processing related to the filter management unit 330 in steps S103 to S105 and S112 in FIG.

  In steps S303 to S310, the steps related to the local UI unit 11 and the request management unit 220 are executed in the order shown in FIG. 13, but the processing between the local UI unit 11 and the request management unit 220 is performed. The order of and the order of the processes in steps S103 to S118 in FIG.

(Example of processing in which the local UI unit 11 acquires the filter management table)
FIG. 14 is a sequence diagram of an example of the activation of the local UI unit 11 and the request management unit 220 and the process in which the local UI unit 11 acquires the filter management table. The processing from step S401 to step S409 in FIG. 14 is performed after all plug-ins included in MFP 1 are initialized.

  In step S401, an activation instruction is output from the plug-in management unit 210 to the request management unit 220, and the request management unit 220 is activated. The activation instruction from the plug-in management unit 210 is accompanied by a plug-in management table held by the plug-in management table holding unit 212. As a result, the request management unit 220 can obtain all plug-in operations of the MFP 1 and object information related to the operations.

  In the processing from step S402 to step S409 performed after step S401, the local UI unit 11 is activated to acquire the filter management table. The processing from step S402 to step S409 is performed after the activation of other plug-ins and means other than the plug-in having user interface means such as the local UI part 11 of the user interface unit 10 is completed, and the filter management means 330 has. The table holding means 331 must be executed after obtaining the functions of these means and filters and the objects related to the functions. As a result, the user interface unit included in the local UI unit 11 and the like can acquire and display all the information related to the functions included in the MFP 1.

  In step S402, an activation instruction is output from the plug-in management unit 210 to the local UI unit 11, and the local UI unit 11 is activated. In step S403 following step S402, the local UI unit 11 outputs a filter management table acquisition object acquisition request to the plug-in management unit 210. Progressing to step S404 following step S403, the plug-in management unit 210 searches for a filter management table acquisition object registered in the plug-in management table holding unit 212.

  In step S405 following step S404, the filter management table acquisition object is transmitted from the plug-in management unit 210 to the local UI unit 11. Progressing to step S406 following step S405, the filter management table acquisition unit 112 of the local UI unit 11 outputs a filter management table acquisition request to the filter management unit 330.

  In step S407 following step S406, the filter management unit 330 acquires the filter management table included in the filter management table holding unit 331. Progressing to step S408 following step S407, the filter management table 330 transmits the filter management table to the local UI unit 11.

  In step S409 following step S408, the local UI unit 11 outputs an operation screen of the MFP 1 to a display device such as an operation panel based on the filter management table acquired in step S408, and displays the operation screen.

  13 and 14 illustrate the processing of the local UI unit 11 as an example of the user interface, but the processing for generating a display on the client PC can be easily understood from FIGS. 13 and 14. .

(Example of operation screen of MFP 1)
FIG. 15 is an example of an operation screen of the MFP 1 and is an example of a screen displayed on the operation panel. The operation screen of FIG. 15 includes three areas of “request panel”, “input selection panel”, and “output selection panel”. The request panel is a screen that displays processing executed by the MFP 1. In the example of FIG. 15, execution of three processes of an image reading process, a process of printing and outputting the read image, and a process of sending the read image by mail is displayed in association with each other. The request panel further displays buttons such as “install”, “uninstall”, and “setting”.

  The input selection panel is an area for selecting a function for inputting an image to the MFP 1, and displays two buttons “read” and “stored document read”. “Reading” corresponds to acquisition of image data by the scanner, and “read document storage” corresponds to reading and acquiring image data stored in the storage device of the MFP 1.

  The output selection panel is an area for selecting a function for outputting an image from the MFP 1 and displays four buttons of “print”, “stored document registration”, “mail transmission”, and “FAX transmission”. “Print” corresponds to output from the plotter, and “Registered document” corresponds to storing image data in the storage device of the MFP 1. “Mail transmission” corresponds to sending an image data file attached to a mail, and “FAX transmission” corresponds to sending an image by facsimile.

  The functions corresponding to the buttons displayed on the input selection panel and the output selection panel are as follows. The local UI unit 11 uses the filter management table acquired in step S408 in FIG. It is matched.

(Operation of MFP 1 based on input to local UI unit 11 (filter setting process))
FIGS. 16 to 18 are a sequence of exemplary processes when the MFP 1 activated by the processes of FIGS. 7 to 15 executes a job based on an input to the local UI unit 11.

  FIG. 16 is a sequence diagram of an example of filter setting processing for realizing a job. FIG. 16 illustrates an example of processing in which a local UI for setting the filter 350a is displayed on the operation panel when the operator inputs to the operation panel.

  Steps S501 to S503 in FIG. 16 are sequences for preparing for receiving an instruction input from the operation panel when the display on the operation panel is in an initial state. In step S 501, a request object acquisition request is output from the local UI unit 11 to the plug-in management unit 210. The request object is an action object for accepting a request such as an instruction from the operator of the MFP 1 input via the user interface and selecting and executing a function that realizes the request.

  Proceeding to step S502 following step S501, the plug-in management unit 210 searches for the request object from the action objects held in the plug-in table holding unit 212. In step S503 following step S502, the request object is transmitted from the plug-in management unit 210 to the local UI unit 11.

  Since the processing from step S501 to step S503 is executed when the operation panel display is in the initial state, the operation screen or the like is already displayed on the operation panel, and the local UI unit 11 acquires the request object. If it is, it may be omitted.

  Steps S504 to S511 are processes for obtaining the filter UI 151a and displaying it on the operation panel. For example, one filter is selected on the operation screen of FIG. 15, and the “set” button is pressed. This process is executed when

  In step S504 following step S503, the local UI unit 11 transmits a filter UI acquisition object acquisition request to the plug-in management unit 210. Proceeding to step S505 following step S504, the plug-in management unit 210 searches the action object held in the plug-in table holding unit 212 for a filter UI acquisition object corresponding to the filter UI 151a. In step S506 following step S505, a filter UI acquisition object is transmitted from the plug-in management unit 210 to the local UI unit 11.

  In step S507 following step S506, the local UI unit 11 transmits a filter UI acquisition request to the filter 350a based on the filter UI acquisition object acquired in step S506. Progressing to step S508 following step S507, a UI acquisition request is output from the filter 350a to the filter UI 151a. In step S509 following step S508, the filter UI 151a outputs the filter UI object to the filter 350a. Progressing to step S510 following step S509, the filter UI object is output from the filter 350a to the local UI unit 11. Progressing to step S511 following step S510, the local UI unit 11 displays the filter UI screen acquired in step S510 on the operation panel.

  FIG. 17 is an example of a filter UI screen, which is an example of a “read” filter. In FIG. 17, “color mode”, “paper size”, and “single / double-sided” when executing the “read” function can be set by selecting corresponding buttons. After selecting the button, by pressing the “return” button, the display on the operation panel returns to the operation screen described in FIG. 15, and the “read” filter is set based on the selection. .

  Steps S512 to S514 in FIG. 16 are filter setting processing. In step S512, the local UI unit 11 sets the filter 350a for the request object acquired in step S503. Thereby, the input from the operation panel can be processed as a setting request to the filter 350a.

  After the setting of the filter 350a is selected by the button on the operation panel, the process proceeds to step S513 following step S512, and the content selected on the operation panel is output from the local UI unit 11 to the filter UI 151a as a setting request. . It should be noted that step S513 may be executed subsequent to pressing a button indicating that the selection such as a “setting” button (not shown) displayed on the operation panel is finished. Progressing to step S514 following step S513, the setting content is output from the filter UI 151a to the filter 350a, and the setting is performed based on the content acquired by the filter 350a.

(Operation of MFP 1 based on input to local UI unit 11 (filter execution process))
FIG. 18 is a sequence diagram illustrating an example of processing in which the MFP 1 realizes the function of the filter 350a based on an instruction input from the operation panel or the like to the local UI unit 11. In FIG. 18, the MFP 1 realizes the function of the filter 350a based on the pressing of the “Start” button on the operation screen of FIG.

  Following the pressing of the “Start” button on the operation panel by the operator, in step S601, the local UI unit 11 outputs a request, which is an instruction to start function implementation, to the request management unit 220. In step S602 following step S601, the request management unit 220 selects the filter corresponding to the job and the setting content for each filter based on the content of the request acquired from the local UI unit 11.

  Proceeding to step S603 following step S602, the request management unit 220 transmits an acquisition request for the execution object of the filter selected at step S602 to the plug-in management unit 210. In step S604 following step S603, the plug-in management unit 210 searches for an execution object of the filter requested in step S603.

  Progressing to step S605 following step S604, the execution object of the filter is transmitted from the plug-in management unit 210 to the request management unit 220. Progressing to step S606 following step S605, the request management unit 220 outputs an execution request to the filter 350a based on the execution object of the filter acquired in step S605. Progressing to step S607 following step S606, the filter 350a implements the function of the filter 350a based on the execution request acquired in step S606.

  Through the processing from step S601 to step S607, processing for realizing the functions of the MFP 1 is performed in accordance with an instruction input by the operator from the operation panel or the like.

(Example of processing to install a filter including the filter UI)
FIGS. 19 to 21 are diagrams for explaining processing when a filter including a filter UI is added to the MFP 1. FIG. 19 is an example of a screen displayed on the operation panel during processing, and FIG. FIG. 21 shows the contents of plug-ins managed by the plug-in address holding means 211.

  FIG. 19A shows that the “install” operation has been selected on the operation panel. When “Install” is selected, the operation panel display is switched to the screen shown in FIG. FIG. 19B is a list of functions that can be added to the MFP 1. The MFP 1 may acquire a list of functions that can be added by communicating with an external server (not shown) by the communication server 12. The MFP 1 may also obtain a list of filters that are stored in the storage device of the MFP 1 and are not added as functions of the MFP 1, and obtain a list of functions corresponding to them. FIG. 19B shows that the “FAX transmission” function is selected by the operator as a function to be added. When the operator selects a function to be added as shown in FIG. 19B, a process for installing a filter is started.

  In step S701 of FIG. 20, as shown in FIG. 19A, the “install” displayed on the operation panel is selected by the operator, and the display of the operation panel is switched to the screen of FIG. 19B. Progressing to step S702 following step S701, a filter displayed on the operation panel is selected by the operator, and a button for instructing start of installation is further pressed.

  Progressing to step S703 following step S702, an installation request is output from the local UI unit 11 to the plug-in management unit 210. In step S704 following step S703, the plug-in management unit 210 downloads the plug-in corresponding to the filter to be installed. The plug-in management unit 210 may download the plug-in from an external server (not shown) by the communication server 12 or may acquire a plug-in stored in a storage device (not shown) included in the MFP 1. 20 is an example in which the plug-in is configured as a program, but when the plug-in is configured as a device, the device to be added is connected to the MFP 1 instead of downloading the program. You may comprise so that a process may be performed.

  Proceeding to step S705 following step S704, an instruction to generate the filter 350a is output from the plug-in management unit 210, and the filter 350a is generated. Progressing to step S706 following step S705, the plug-in management unit 210 causes the plug-in address holding unit 211 to store the address of the plug-in having the filter 350a.

  Progressing to step S707 following step S706, the filter 350a outputs a plug-in registration request having the filter 350a to the plug-in managing means 210. Progressing to step S708 following step S707, the plug-in management unit 210 registers the operation of the filter 350a and the operation object corresponding to the operation in the plug-in management table.

  Following step S709, the process proceeds to step S710. In step S710, processing relating to initialization of the filter 350a is performed. Since the process of step S710 is the same as the process of step S113 to step S115 of FIG. 7, description is abbreviate | omitted here.

  Following step S710, the process proceeds to step S711. In step S711, processing related to activation of the filter 350a and registration in the filter management means 330 is performed. Since the process of step S711 is the same as the process of step S202 to step S207 in FIG. 11, description is abbreviate | omitted here.

  Progressing to step S712 following step S711. In step S712, the display on the operation panel is updated by the local UI unit 11. Since the process of step S712 is the same as the process of step S406 to step S408 in FIG. 14, description thereof is omitted here.

  FIG. 19C is an example of the operation screen after being updated by the local UI unit 11 in step S712. 19A, a “FAX transmission” button is added to the output selection panel.

  Through the processing from step S701 to step S712, the filter 350a is added to the MFP 1 and its function can be executed. As is clear from FIG. 20, the process related to the filter 350a when the MFP 1 is activated and the process when the filter 350a is added to the MFP 1 are substantially the same. More specifically, after the plug-in is downloaded (after step S705), an additional process (step S706) is added to the plug-in address holding unit 211, which is different from the case where the MFP 1 is activated. It is.

  That is, since the process is substantially the same when the MFP 1 is activated and when a filter is added to the MFP 1, the means for realizing the process can be shared, and the means for realizing the process. When configured as a program, the capacity of the storage device storing the program can be reduced. Further, by adding to the plug-in address holding unit 211, the newly added filter is reflected when the MFP 1 is activated next time.

  FIG. 21 is a diagram illustrating the contents of the plug-in address holding unit 211 before and after the plug-in having the filter 350a is added to the MFP 1. FIG. 21A shows the contents of the plug-in address holding unit 211 before the filter 350a is added. In FIG. 21A, names of “request management”, “filter management”, “local UI”, and “filter 350b”, which are plug-ins of the MFP 1, and storage locations of these plug-ins are shown.

  FIG. 21B is an example of an address of a plug-in corresponding to the screen of FIG. 19B, for example, and an addable plug-in acquired by the MFP 1 communicating with an external server or the like. It is a list.

  FIG. 21C shows the contents held by the plug-in address holding unit 211 after the plug-in having the filter 350a is added to the MFP 1, and has been updated in step S706 of FIG.

(Process of deleting the filter 350a from the MFP 1)
FIG. 22 is a sequence diagram illustrating an example of processing for deleting the filter 350a from the MFP 1. In FIG. 22, the filter 350a of the MFP 1 is deleted based on the deletion instruction from the operation panel or the like.

  In step S801 in FIG. 22, the local UI unit 11 outputs a request to uninstall the filter 350a to the plug-in management unit 210 based on an instruction to delete (uninstall) the filter 350a input from the operation panel or the like. .

  In step S802 following step S801, the plug-in management unit 210 transmits a stop request to the filter 350a. When the filter 350a is configured as a program, the stop request may be deletion of the program, or the address of the program may be deleted from the management table of the storage device storing the program. Further, when the filter 350a is configured as a device, the power supply to the device may be stopped.

  In step S803 following step S802, the plug-in management unit 210 outputs a deletion request from the filter management table to the filter management unit 330. In step S804 following step S803, the plug-in management unit 210 deletes the operation of the filter 350a and the registration of the operation object corresponding to the operation from the plug-in management table held by the plug-in management table holding unit 212. On the other hand, in step S805 following step S803, the filter management unit 330 deletes the function of the filter 350a and the registration of the operation object corresponding to the function from the filter management table held by the filter management table holding unit 331.

  In step S806 following step S804, the plug-in management unit 210 deletes information such as an address where the plug-in having the filter 350a held by the plug-in address holding unit 211 is stored.

  The processing from step S807 to step S810 following step S806 is processing in which the local UI unit 11 updates the display on the operation panel or the like, and is the same as the processing from step S406 to step S409 in FIG. Description is omitted.

  With the processes from step S801 to step S810, the process of deleting the filter 350a from the MFP 1 is completed.

(Processing when MFP 1 having a filter for realizing the printing function is activated)
FIG. 23 is a sequence diagram of an example of processing when the MFP 1 having the print 350d that is a filter for realizing the print function is activated. Since it can be easily understood from FIGS. 7 and 11 that the MFP 1 is activated so as to realize the printing function by the processing of FIG. 23, the description thereof is omitted here.

(Process when MFP 1 is activated (part 2))
FIGS. 24 to 27 are diagrams for explaining processing when the MFP 1 is activated, in which the filter and the UI of the filter are included in different plug-ins.

FIG. 24 is a sequence diagram of an example of processing for registering a filter included in a plug-in and a UI of the filter in the plug-in management unit 210. In step S901 in FIG. 24, the MFP 1 is turned on and an activation instruction is input to the plug-in management unit 210.
The processing from step S903 to step S908 in FIG. 24 is substantially the same as the processing from step S103 to step S108 in FIG. 7, and the processing related to the filter 350a in FIG. 7 is the processing related to the filter 360a in FIG. Since others are the same, description is abbreviate | omitted here.

  Following step S908, the process proceeds to step S909, where an instruction to generate the filter UI 161a is output from the plug-in management unit 210, and the filter UI 161a is generated. In step S910 following step S909, a plug-in registration request is output from the filter UI 161a to the plug-in management unit 210, and an operation included in the filter UI 161a and an operation object corresponding to the operation are requested to be registered. The Progressing to step S911 following step S910, the plug-in management unit 210 registers the operation of the filter UI 161a and the operation object corresponding to the operation in the plug-in management table.

  Proceeding to step S912 following step S911, an instruction to initialize the unit is output from the plug-in management unit 210 to the filter management unit 330, and the filter management unit 330 executes initialization. Progressing to step S913 following step S912, the plug-in management unit 210 outputs an instruction to initialize the filter 360a to the filter 360a, and the filter 360a executes initialization. Progressing to step S914 following step S913, the filter 360a sets the filter name.

  Note that the processing from step S903 to step S914 is executed in the order shown in the figure, while the processing related to the filter management means 330, the processing related to the filter 360a, and the processing related to the filter UI 161a are executed in the order shown in the figure. The order of processing between the filter 360a and the UI 161a of the filter is not limited and may be asynchronous.

  Progressing to step S915 following step S914, a filter UI acquisition object acquisition request is transmitted from the filter 360a to the plug-in management unit 210. In step S916 following step S915, the plug-in management unit 210 searches the plug-in management table included in the plug-in management table holding unit 212 for a filter UI 161a acquisition object. Proceeding to step S917 following step S916, the filter UI 161a acquisition object is transmitted from the plug-in management unit 210 to the filter 360a.

  Proceeding to step S918 following step S917, a filter UI acquisition request is output from the filter 360a to the filter UI 161a by the filter UI 161a acquisition object acquired in step S917. Progressing to step S919 following step S918, the filter UI 161a outputs the filter UI object to the filter 360a. Progressing to step S920 following step S919, a filter object set request is output from the filter 360a to the filter UI 161a based on the filter UI object acquired in step S919, and the filter UI 161a sets the filter object. .

  A plug-in management table for plug-ins such as filters of the MFP 1 is generated by the processing from step S901 to step S920, and is included in a plug-in different from the filter 360a by the processing from S915 to step S920. A filter UI 161a is set for the filter 360a.

(Example of plug-in address when the filter and UI of the filter are included in different plug-ins)
FIG. 25 shows an example of the plug-in address held by the plug-in address holding unit 211 when the filter and the UI of the filter are included in different plug-ins. In FIG. 25, in addition to the example of FIG. 8, the address of a plug-in having a filter UI is stored. More specifically, in addition to the addresses at which plug-ins corresponding to “filter 360a” and “filter 360b” are stored, plug-ins corresponding to “UI of filter 360a” and “UI of filter 360b” are stored. Address is retained.

(Operation object when the filter and UI of the filter are included in different plug-ins)
FIG. 26 is an example of an action object when the filter and the UI of the filter are included in different plug-ins. In step S907 and step S910 in FIG. 24, the plug-in management means together with the plug-in registration request. It is an example of the information output.

  FIG. 26A is a table of actions of the filter 360a and action objects corresponding to the actions. On the other hand, FIG. 26B is an operation object table corresponding to the operation of the filter UI 161a which is the UI of the filter 360a. If the filter UI is included in a plug-in different from the filter, the filter UI also makes a registration request to the plug-in management unit 210 in addition to the filter. Thereby, the plug-in management unit 210 can manage the UI of the filter.

(Registration in the filter management means 330 when the filter and the UI of the filter are included in different plug-ins)
FIG. 27 is a sequence diagram of an example of registration processing in the filter management unit 330 when the filter and the filter UI are included in different plug-ins. Steps S1001 to S1008 in FIG. 27 are substantially the same as the processes in steps S201 to S208 in FIG. More specifically, the process related to the filter 360a in FIG. 27 is the same as the process related to the filter 350a in FIG. 11, and the other processes are the same in FIG. 11 and FIG. .

  27, the function and the like of the filter 360a are registered in the filter management table held by the filter management table holding unit 331. On the other hand, the function of the filter UI 161a and the function object corresponding to the function are not registered in the filter management table, and the filter 360a manages the filter UI 161a.

  When the MFP 1 is activated, processing such as generation and activation of the local UI unit 11 and the request management unit 220 is executed in addition to the processing of FIGS. 24 and 27. Since processing such as generation of the means 220 is the same as the processing of FIGS. 13 and 14, the description thereof is omitted here.

(Example of processing to install a filter when the filter and the UI of the filter are included in different plug-ins)
FIG. 28 is a sequence diagram of an example of additional processing such as filtering on the MFP 1 when the filter and the UI of the filter are included in different plug-ins. In FIG. 28, the filter 360 a and the like are added to the MFP 1 based on the “install” instruction input from the operation panel by the operator. The display on the operation panel is the same as when the filter and the UI of the filter in FIG. 20 are included in one plug-in.

  In step S1101 in FIG. 28, as shown in FIG. 19A, the “install” displayed on the operation panel is selected by the operator, and the display on the operation panel is switched to FIG. 19B. Subsequent to step S1101, the process proceeds to step S1102, where a filter displayed on the operation panel is selected by the operator, and a button for instructing start of installation is further pressed.

  Proceeding to step S1103 following step S1102, the local UI unit 11 outputs an installation request to the plug-in management unit 210. In step S1104 following step S1103, the plug-in management unit 210 downloads a plug-in corresponding to the filter to be installed and a plug-in corresponding to the filter UI. The plug-in management unit 210 may download the plug-in from an external server (not shown) by the communication server 12 or may acquire a plug-in stored in a storage device (not shown) included in the MFP 1. In the example of FIG. 28, the plug-in is configured as a program. However, when the plug-in is configured as a device, an additional device is connected to the MFP 1 instead of downloading the program. You may comprise so that a process may be performed.

  Progressing to step S1105 following step S1104, an instruction to generate the filter 360a is output from the plug-in management unit 210, and the filter 360a generates. Progressing to step S1106 following step S1105, an instruction to generate the filter UI 161a is output from the plug-in management unit 210, and the filter UI 161a is generated.

  In step S1107 following step S1106, the plug-in management unit 210 causes the plug-in address holding unit 211 to store the address of the plug-in having the filter 360a and the address of the plug-in having the filter UI 161a.

  Progressing to step S1108 following step S1107, the filter 360a outputs a plug-in registration request having the filter 360a to the plug-in managing means 210. Progressing to step S1109 following step S1108, the plug-in management unit 210 registers the operation of the filter 360a and the operation object corresponding to the operation in the plug-in management table.

  Progressing to step S1110 subsequent to step S1109, the filter UI 161a outputs a plug-in registration request having the filter UI 161a to the plug-in management unit 210. Progressing to step S1111 following step S1110, the plug-in management unit 210 registers the operation of the filter UI 161a and the operation object corresponding to the operation in the plug-in management table.

  Progressing to step S1112 following step S1111. In step S1112, processing relating to initialization of the filter 360a and the filter UI 161a is performed. Since the process of step S1112 is the same as the process of step S912 to step S920 of FIG. 24, description thereof is omitted here.

  Following step S1112, the process proceeds to step S1113. In step S <b> 1113, processing related to activation of the filter 360 a and the filter UI 161 a and registration in the filter management unit 330 is performed. Since the process of step S1113 is the same as the process of step S1002 to step S1008 in FIG. 27, description is abbreviate | omitted here.

  Following step S1113, the process proceeds to step S1114. In step S <b> 1114, the display on the operation panel is updated by the local UI unit 11. Since the process of step S1114 is the same as the process of step S406 to step S409 in FIG. 14, description thereof is omitted here.

  Through the processing from step S1101 to step S1114, the filter 360a and the filter UI 161a are added to the MFP 1 and the functions thereof can be executed. As is apparent from FIG. 28, the processing related to the filter 360a and the filter UI 161a when the MFP 1 is activated is substantially the same as the processing when the filter 360a and the filter UI 161a are added to the MFP 1. More specifically, after the plug-in is downloaded (after step S1105), an additional process (step S1107) is added to the plug-in address holding unit 210, which is different from the case where the MFP 1 is activated. It is.

  That is, since the process is substantially the same when the MFP 1 is activated and when a filter is added to the MFP 1, the means for realizing the process can be shared, and the means for realizing the process. When configured as a program, the capacity of the storage device storing the program can be reduced. Further, by adding to the plug-in address holding unit 211, the newly added filter is reflected when the MFP 1 is activated next time.

  FIG. 29 is a diagram illustrating the contents of the plug-in address holding unit 211 before and after the filter 350a is added to the MFP 1. Note that, in FIGS. 29A to 29C, information regarding the plug-ins of the filter management unit 330 and the request management unit 210 is omitted. FIG. 29A shows the contents of the plug-in address holding unit 211 before the filter 360a is added. In FIG. 29A, the names of “filter 360a” and “filter UI 161a” and the storage locations of these plug-ins are shown.

  FIG. 29B is a list of plug-ins that can be added, acquired by the MFP 1 communicating with an external server or the like. In FIG. 29B, “filter 360a” and “filter 360c” are shown as plug-in names, and the plug-in storage locations corresponding to the respective filters and the plug-in storage corresponding to the filter UI are stored. The location is shown. Thus, the filter and the filter UI are downloaded and added based on the selection of the function (name of the filter) to be installed by the operator.

  FIG. 29C shows the contents held by the plug-in address holding means 211 after the plug-in having the filter 360a and the plug-in having the filter UI 161a are added to the MFP 1, and the steps of FIG. The contents updated in S1114.

(Process of deleting filter 360a from MFP 1)
FIG. 30 is a sequence diagram illustrating an example of processing for deleting the filter 360a from the MFP 1. In FIG. 30, the filter 360a of the MFP 1 is deleted based on the deletion instruction from the operation panel or the like.

  In step S1201 of FIG. 30, the local UI unit 11 outputs a request to uninstall the filter 360a to the plug-in management unit 210 based on an instruction to delete (uninstall) the filter 360a input from the operation panel or the like. .

  In step S1202 following step S1201, the plug-in management unit 210 transmits a stop request to the filter 360a. When the filter 360a is configured as a program, the stop request may be deletion of the program, or the address of the program may be deleted from the management table of the storage device storing the program. Further, when the filter 360a is configured as a device, the power supply of the device may be stopped.

  Subsequent to step S1202 or before or after step S1202, in step S1203, the plug-in management unit 210 transmits a stop request to the filter 360a. The content of the stop request is substantially the same as that of the filter 360a. Progressing to step S1204 following step S1203, the plug-in management unit 210 outputs a deletion request from the filter management table to the filter management unit 330.

  In step S1205 following step S1204, the plug-in management unit 210 deletes the operation of the filter 360a and the filter UI 161a and the registration of the operation object corresponding to the operation from the plug-in management table. On the other hand, in step S1206 following step S1204, the filter management unit 330 deletes the function of the filter 360a and the registration of the function object corresponding to the function from the filter management table held by the filter management table holding unit 331.

  In step S1207 following step S1205, the plug-in management unit 210 uses the plug-in address holding unit 211 to store information such as addresses stored in the plug-in having the filter 360a and the plug-in having the filter UI 161a. Delete from the information held by.

  The processing from step S1208 to step S1211 following step S1207 is processing in which the local UI unit 11 updates the display on the operation panel or the like, and is the same as the processing in step S1114 in FIG. To do.

  The process of deleting the filter 360a and the filter UI 161a from the MFP 1 is completed by the processes in steps S1201 to S1211. The operator can delete the filter UI 161a together with the filter 360a by inputting an instruction to delete the filter 360a from the operation panel at or before step S1201.

Although the best mode for carrying out the invention has been described above, the present invention is not limited to the embodiment described in the best mode. Modifications can be made without departing from the spirit of the present invention.

6 illustrates an example of a configuration of a unit that executes a job of the MFP 1. The figure for demonstrating the concept of a pipe & filter architecture. 2 is a diagram illustrating an example of a functional configuration related to registration of a plug-in included in the MFP 1 and registration of a filter included in the plug-in. FIG. 2 is a diagram of a logical correspondence between a filter and a filter UI (part 1). FIG. 2 is a diagram (2) showing a logical correspondence between a filter and a filter UI. The figure of the example of a physical structure of a filter and UI of a filter. The sequence of the example of the process in which the filter which a plug-in has registered into the plug-in management means 210 is registered. An example of a list of plug-ins and plug-in addresses held by the plug-in address holding unit 211 (part 1). An example of information output when a registration request is sent to the plug-in management means (part 1). Example of plug-in management table. Sequence of an example of processing for registering a filter in the filter management unit 330 (part 1). An example of a filter management table. A sequence of an example of processing in which operations of the local UI unit 11 and the request management unit 220 are registered in the plug-in management unit 210. The sequence of the example of the process of starting the local UI part 11 and the request management means 220, and the local UI part 11 acquiring a filter management table. 6 is an example of an operation screen displayed on an operation panel of the MFP 1. Sequence of an example of filter setting processing that implements a job. An example of a UI screen of a filter. A sequence of an example of processing in which the MFP 1 executes the filter 350a. 6 illustrates an example of a screen displayed on the operation panel during processing when a filter including a filter UI is added to the MFP 1. Sequence of an example of processing when adding a filter to the MFP 1 (part 1). FIG. 6 is a diagram for explaining the contents of plug-in address holding means 211 before and after a filter 350a is added to MFP1. 10 is a sequence example of processing for deleting the filter 350a from the MFP 1; The sequence of the example of a process in case MFP1 which has the printing 350d which is a filter which implement | achieves a printing function is started. A sequence of an example of processing in which a filter included in a plug-in and a filter UI are registered in the plug-in management unit 210. An example of a list of plug-ins and plug-in addresses held by the plug-in address holding unit 211 (part 2). An example (part 2) of information output at the time of a registration request to the plug-in management means. Sequence of an example of processing for registering a filter in the filter management unit 330 (part 2). Sequence example of processing for adding a filter to MFP 1 (part 2) The figure explaining the content of the plug-in address holding means 211 before and after the filter 360a is added to the MFP 1 10 is a sequence example of processing for deleting the filter 360a from the MFP 1;

Explanation of symbols

1 MFP
DESCRIPTION OF SYMBOLS 10, 10a User interface part 11 Local UI part 12 Communication server 20, 20a Control part 30, 30a Function realization part 40 Device service part 41 Data management means 42 Memory 50 Device part 111 User interface 112 Filter management table acquisition means 119 UI plug-in 131 Filter UI
139 Filter UI plug-ins 151a, 151b, 151c, 161a, 161b, 161c Filter plug-in 210 Plug-in management means 211 Plug-in address holding means 212 Plug-in management table holding means 220 Request management means 220 Request management means 221 Job Generation means 330 Filter management means 331 Filter management table holding means 332 Filter registration object 340 Filter 341 Action object acquisition means 342 Filter registration request means 343 UI management means 344 Plug-in registration request means 349 Filter plug-ins 350a, 350b, 350c, 360a 360b, 360c filter

Claims (13)

An image processing apparatus capable of adding a plug-in having a filter provided for each process constituting a job related to image processing,
Plug-in managing means for registering and managing the plug-in;
An image processing apparatus comprising: filter management means for registering and managing information relating to the filter. The plug-in management means includes
Plug-in address holding means for holding an address where the plug-in is stored;
The image processing apparatus according to claim 1, further comprising: a plug-in management table holding unit that holds a plug-in management table that manages an operation of a filter included in the plug-in and an operation object corresponding to the operation. The filter management means includes
The image processing apparatus according to claim 1, further comprising: a filter management table holding unit that holds a filter management table that manages a function of the filter and a function object corresponding to the function. When the user interface corresponding to the filter is included in a plug-in different from the filter, and when the image processing apparatus is activated or when a plug-in having the filter is added,
The plug-in management means includes
The image processing apparatus according to claim 1, wherein the plug-in having the filter and the plug-in having the user interface are registered and managed. The user interface corresponding to the filter is included in a plug-in different from the filter, and the image processing apparatus is activated or the plug-in having the filter is added to the image processing apparatus. If added,
The filter management means registers and manages the filter,
The image processing apparatus according to claim 1, wherein the filter includes a UI management unit that acquires and manages the user interface. When the user interface corresponding to the filter is included in a plug-in different from the filter, and the plug-in is deleted,
The plug-in management means deletes the registration of the plug-in having the filter and the plug-in having the user interface,
The image processing apparatus according to claim 1, wherein the filter management unit deletes the registration of the filter. An image processing method in an image processing apparatus capable of adding a plug-in having a filter provided for each process constituting a job related to image processing,
A plug-in management step for registering and managing the plug-in;
And a filter management step for registering and managing information relating to the filter. The plug-in management step includes
A plug-in address holding step for holding an address where the plug-in is stored;
8. The image processing method according to claim 7, further comprising: a plug-in management table holding step for holding a plug-in management table for managing an operation of a filter included in the plug-in and an operation object corresponding to the operation. The filter management step includes:
8. The image processing method according to claim 7, further comprising a filter management table holding step for holding a filter management table for managing the function of the filter and a function object corresponding to the function. When the user interface corresponding to the filter is included in a plug-in different from the filter, and when the image processing apparatus is activated or when a plug-in having the filter is added,
The plug-in management step includes
8. The image processing method according to claim 7, wherein the plug-in having the filter and the plug-in having the user interface are registered and managed. The user interface corresponding to the filter is included in a plug-in different from the filter, and the image processing apparatus is activated or the plug-in having the filter is added to the image processing apparatus. If added,
The filter management step registers and manages the filter,
The image processing method according to claim 7, wherein the filter includes a UI management step of acquiring and managing the user interface. When the user interface corresponding to the filter is included in a plug-in different from the filter, and the plug-in is deleted,
The plug-in management step deletes the registration of the plug-in having the filter and the plug-in having the user interface;
8. The image processing method according to claim 7, wherein the filter management step deletes the registration of the filter.   An image processing program for causing a computer to execute the image processing method according to any one of claims 7 to 12.

Images