JP2011082941A - Component server, image forming apparatus, and customizing system, method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a component server that facilitates sharing customized contents between different devices; and to provide an image forming apparatus, and a customizing system, method and program. <P>SOLUTION: The component server 10 that is connected with a first multifunctional machine 20 through a network 2 includes: a component storage unit 122 that sores a component with customized contents of each multifunctional machine; and a distribution unit 132 that distributes the component stored in the component storage unit 122 to the first multifunctional machine 20 and customizes it. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a component server, an image forming apparatus, a customization system, a customization method, and a customization program.

  2. Description of the Related Art Conventionally, there is known a technique for managing the customization content of an operation screen of a multifunction peripheral (MFP) as setting information on a server and distributing the setting information to the multifunction device to customize the operation screen (for example, Patent Document 1).

  However, in the technique disclosed in Patent Document 1, in order to share customization contents between different models having different functions, the server side selects and distributes necessary information for each model from the setting information. Since it is necessary, there is a problem that the processing becomes complicated.

  The present invention has been made in view of the above circumstances, and provides a component server, an image forming apparatus, a customization system, a customization method, and a customization program that can easily share customization contents among different models. For the purpose.

  In order to solve the above-described problems and achieve the object, a component server according to an aspect of the present invention is a component server connected to an image forming apparatus that forms an image via a network. Component storage means for storing components including customization contents for each model, and distribution means for distributing the components to the image forming apparatus for customization.

  An image forming apparatus according to another aspect of the present invention is an image forming apparatus connected to a component server via a network, and includes a component including customization contents for each model of the image forming apparatus from the component server. It is characterized by comprising acquisition means for acquiring and switching means for switching and starting the component with a default component.

  A customization system according to another aspect of the present invention includes the component server and the image forming apparatus.

  A customizing method according to another aspect of the present invention is a customizing method executed by a component server connected to an image forming apparatus that forms an image via a network. Component storage means for storing components including customization contents for each model is provided, and the distribution means includes a distribution step of distributing the components to the image forming apparatus for customization.

  According to another aspect of the present invention, there is provided a customization method executed by an image forming apparatus connected to a component server via a network, wherein an acquisition unit is configured to send an image of the image forming apparatus from the component server. The acquisition step of acquiring a component including customization contents for each model, and the switching means include a switching step of switching and starting the component with a default component.

  A customization program according to another aspect of the present invention is for causing a computer to execute the customization method.

  According to the present invention, there is an effect that customization contents can be easily shared with different models.

FIG. 1 is a block diagram illustrating a configuration example of a customization system according to the first embodiment. FIG. 2 is a diagram illustrating a configuration example of components. FIG. 3 is a block diagram illustrating a configuration example of the component server and the first multifunction peripheral according to the first embodiment. FIG. 4 is a diagram illustrating an example of components stored in the component storage unit of the first embodiment. FIG. 5 is a diagram showing a configuration example of the copy component shown in FIG. FIG. 6 is a diagram illustrating an example of a default copy screen. FIG. 7 is a diagram illustrating an example of a copy screen after customization. FIG. 8 is a flowchart illustrating an example of upload processing performed in the customization system of the first embodiment. FIG. 9 is a flowchart illustrating an example of distribution processing performed in the customization system according to the first embodiment. FIG. 10 is a diagram illustrating an example of components configured by functional units. FIG. 11 is a diagram illustrating an example of components configured in units of applications. FIG. 12 is a diagram illustrating an example of components configured in units of packages. FIG. 13 is a block diagram illustrating a configuration example of a customization system according to the second embodiment. FIG. 14 is a block diagram illustrating a configuration example of the component server and the first multifunction peripheral according to the second embodiment. FIG. 15 is a diagram illustrating an example of a component storage unit according to the second embodiment. FIG. 16 is a flowchart illustrating an example of upload processing performed in the customization system of the second embodiment. FIG. 17 is a flowchart illustrating an example of distribution processing performed in the customization system of the second embodiment. FIG. 18 is a diagram illustrating an example of managing components configured in functional units for each user. FIG. 19 is a diagram illustrating an example of managing components configured in units of applications for each user. FIG. 20 is a diagram illustrating an example of managing components configured in package units for each user. FIG. 21 is a block diagram illustrating a configuration example of a customization system according to the third embodiment. FIG. 22 is a block diagram illustrating a configuration example of the component server and the first multifunction peripheral according to the third embodiment. FIG. 23 is a diagram illustrating an example of a component storage unit according to the third embodiment. FIG. 24 is a flowchart illustrating an example of upload processing performed in the customization system of the third embodiment. FIG. 25 is a flowchart illustrating an example of distribution processing performed in the customization system of the third embodiment. FIG. 26 is a diagram illustrating an example in which default components and customization information configured in units of functions are managed for each user. FIG. 27 is a diagram illustrating an example in which default components and customization information configured in units of applications are managed for each user. FIG. 28 is a diagram illustrating an example of managing default components and customization information configured in units of packages for each user. FIG. 29 is a block diagram illustrating a hardware configuration example of the multifunction peripheral according to the first to third embodiments.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments of a component server, an image forming apparatus, a customization system, a customization method, and a customization program according to the present invention will be described in detail with reference to the accompanying drawings. In the following embodiment, an image forming apparatus will be described by taking a multifunction printer (MFP) having at least two functions among a printer function, a scanner function, a copy function, and a facsimile function as an example. It is not limited to. For example, the image forming apparatus may be a copying machine, a printer, a scanner device, a facsimile device, or the like.

(First embodiment)
First, the configuration of the customization system of the first embodiment will be described.

  FIG. 1 is a block diagram illustrating an example of a configuration of a customization system 1 according to the first embodiment. As shown in FIG. 1, the customization system 1 includes a component server 10 and a plurality of multifunction devices including a first multifunction device 20 and a second multifunction device 21. Each device of the customization system 1 is connected via the network 2. The network 2 can be realized by a LAN (Local Area Network) or the Internet.

  The component server 10 manages components including customization contents for each model, and distributes the components to multifunction devices such as the first multifunction device 20 and the second multifunction device 21. A multifunction device such as the first multifunction device 20 or the second multifunction device 21 acquires a component from the component server 10 and customizes the multifunction device.

  A component is an object that includes processing along with information. FIG. 2 is a diagram illustrating a configuration example of components. As shown in FIG. 2, the component of this embodiment is comprised including a common process, a functional difference, and functional difference information.

  FIG. 3 is a block diagram illustrating an example of the configuration of the component server 10 and the first multifunction device 20 according to the first embodiment. The configuration of the second multifunction device 21 is the same except for the model difference from the first multifunction device 20, and thus the description thereof is omitted. As illustrated in FIG. 3, the component server 10 includes a communication unit 110, a storage unit 120, and a control unit 130.

  The communication unit 110 communicates with a multifunction device such as the first multifunction device 20 or the second multifunction device 21 via the network 2 and can be realized by an existing communication device such as a communication interface.

  The storage unit 120 stores various programs executed by the component server 10, information used for various processes performed by the component server 10, and the like. The storage unit 120 is, for example, magnetic, optical, or electrical such as a hard disk drive (HDD), a solid state drive (SSD), a memory card, an optical disk, a read only memory (ROM), and a random access memory (RAM). It can be realized by an existing storage device that can store the data. The storage unit 120 includes a component storage unit 122.

  The component storage unit 122 stores components including customization contents for each model of the multifunction machine. FIG. 4 is a diagram illustrating an example of components stored in the component storage unit 122. In the example illustrated in FIG. 4, the component storage unit 122 stores a copy component having a copy function and a fax component having a fax function. FIG. 5 is a diagram showing a configuration example of the copy component shown in FIG. In the example illustrated in FIG. 5, the copy component includes a common process of “reading and printing a document”, a function difference of “obtaining a selection value for scaling from the function difference information”, and “of the first MFP 20. The function difference information includes “no scaling function in the model” and “function difference information in which the scaling selection value is 80, 100, 120 for the model of the second MFP 21”.

  Returning to FIG. 3, the control unit 130 controls each unit of the component server 10 and can be realized by an existing control device such as a CPU (Central Processing Unit). Control unit 130 includes a distribution unit 132 and a reception unit 134.

  The distribution unit 132 distributes the components stored in the component storage unit 122 to a multifunction device such as the first multifunction device 20 or the second multifunction device 21 and customizes the components. For example, it is assumed that the first multifunction device 20 incorporates a copy function and a FAX function, and the second multifunction device 21 incorporates only a copy function. In this case, the distribution unit 132 distributes the copy component and the fax component shown in FIG. 4 to the first multifunction device 20 to customize the first multifunction device 20, and causes the second multifunction device 21 to Only the copy component shown is distributed, and the second multifunction device 21 is customized.

  The accepting unit 134 accepts a component including customization content of the model of the multifunction device from the multifunction device such as the first multifunction device 20 or the second multifunction device 21 and stores the component in the component storage unit 122. At this time, the reception unit 134 adds or replaces the received functional difference information of the component to the functional difference information of the component stored in the component storage unit 122. For example, when the receiving unit 134 receives a copy component from the second multifunction device 21, the function difference information of the received copy component is stored in the component storage unit 122. Replace with the function difference information for different models. Further, for example, when the reception unit 134 receives a copy component from a multifunction device other than the model of the first multifunction device 20 and the second multifunction device 21, the function difference information of the received copy component is stored in the component storage unit 122. Is added to the function difference information of the copy component shown in FIG.

  As shown in FIG. 3, the first MFP 20 includes a communication unit 210, a storage unit 220, a display unit 230, an operation unit 240, a reading unit 250, a forming unit 260, and a control unit 270. Is provided.

  The communication unit 210 communicates with the component server 10 and the like via the network 2 and can be realized by an existing communication device as with the component server 10.

  The storage unit 220 stores various programs executed by the first multifunction device 20 and information used for various processes performed by the first multifunction device 20, and is similar to the component server 10 by an existing storage device. realizable. The storage unit 220 stores default components of the first multifunction device 20.

  The display unit 230 displays various screens and can be realized by an existing display device such as a touch panel display or a liquid crystal display.

  The operation unit 240 inputs various operations and can be realized by an existing input device such as a key switch or a touch panel. The display unit 230 and the operation unit 240 may be integrally realized by a touch panel display or the like.

  The reading unit 250 electrically reads a printed matter as image data, and can be realized by an existing reading device such as a scanner.

  The forming unit 260 forms image data read by the reading unit 250 or image data transmitted from a PC (Personal Computer) (not shown) and received by the communication unit 210 on a recording medium such as transfer paper. Yes, it can be realized by an existing printing apparatus such as a printer.

  The control unit 270 controls each unit of the first multifunction machine 20, and can be realized by an existing control device, like the component server 10. The control unit 270 includes an acquisition unit 272, a switching unit 274, a creation unit 276, and an upload unit 278.

  The acquisition unit 272 acquires a component including customization contents for each model of the multifunction peripheral from the component server 10.

  The switching unit 274 starts by switching the component acquired by the acquisition unit 272 to the default component. Thereby, the first multifunction device 20 is customized. For example, the switching unit 274 is displayed on the display unit 230 by switching the default copy component of the first MFP 20 stored in the storage unit 220 to the copy component acquired by the acquisition unit 272 and starting the copy component. The default copy screen as shown in FIG. 6 is switched to a customized copy screen as shown in FIG.

  The creation unit 276 customizes the first multifunction device 20 to create a component including the customization content, and stores the component in the storage unit 220. The creation unit 276 customizes the first multifunction device 20 according to an operation input from the operation unit 240, or customizes the first multifunction device 20 according to an instruction received by the communication unit 210 from a web browser of a PC (not shown). To do.

  The upload unit 278 uploads the component created by the creation unit 276 to the component server 10.

  Next, the operation of the customization system according to the first embodiment will be described. Hereinafter, the operation will be described using the component server 10 and the first multifunction device 20 as an example.

  FIG. 8 is a flowchart illustrating an example of an upload process performed in the customization system 1 according to the first embodiment.

  First, the creation unit 276 of the first multifunction device 20 customizes the first multifunction device 20, creates a component including the customization content, and stores the component in the storage unit 220 (step S100).

  Subsequently, the upload unit 278 of the first multifunction device 20 uploads the component created by the creation unit 276 to the component server 10 (step S102).

  Subsequently, the receiving unit 134 of the component server 10 receives the component from the first multifunction device 20 and stores it in the component storage unit 122 (step S104).

  FIG. 9 is a flowchart illustrating an example of distribution processing performed in the customization system 1 according to the first embodiment.

  First, the receiving unit 134 of the component server 10 receives access from the first multifunction device 20 (step S200).

  Subsequently, the distribution unit 132 of the component server 10 checks whether or not the component including the functional difference information for the model of the first multifunction device 20 is stored in the component storage unit 122 (step S202).

  When there is a component including functional difference information for the model of the first multifunction device 20 (Yes in step S202), the distribution unit 132 acquires the component from the component storage unit 122 and distributes the component (step S204).

  Subsequently, the acquisition unit 272 of the first multifunction device 20 acquires the component distributed from the component server 10 (step S206).

  Subsequently, the switching unit 274 of the first multifunction device 20 switches the component acquired by the acquisition unit 272 to the default component and starts (step S208).

  On the other hand, if there is no component including functional difference information for the model of the first multifunction device 20 in step S202 (No in step S202), the component is not distributed from the component server 10, so the first multifunction device 20 The component remains activated.

  As described above, according to the first embodiment, customization contents can be easily shared with different models by only distributing components including customization contents for each model. For example, even if the copy function of the first multifunction device 20 does not have a scaling function and the copy function of the second multifunction device 21 has a scaling function, no function sorting process is required. However, it is only necessary to distribute a copy component as shown in FIG. Further, for example, when the first MFP 20 has a FAX function and the second MFP 21 does not have a FAX function, a copy component and a Fax component as shown in FIG. 2 Fax components need only be distributed to the multifunction device 21.

  The component may be a functional component in units of functions as shown in FIG. 10, an application component in units of applications as shown in FIG. 11, or a package unit as shown in FIG. It may be a package component.

  A functional component is a minimum unit component, an application component is a combination of functional components, and a package component is a combination of application components. In the example illustrated in FIG. 11, the functional components illustrated in FIG. 10 are combined to form a transmission application component and a storage application component. In the example shown in FIG. 12, the application components shown in FIG. 11 are combined to form a package component called paperless transmission / reception. Note that application components and package components can be grouped on the component server.

  With such functional components, only necessary components can be distributed, and costs can be reduced. In addition, with such an application component, the component can be distributed in units necessary for general users, and the balance with cost is good. In addition, with such package components, the components required for the customer's desired solution can be delivered in a batch, and the work of combining the required components on the customer side and the work of ensuring the consistency of each component (version upgrade) There is no need.

(Second Embodiment)
In the second embodiment, an example in which components are managed for each user will be described. In the following, differences from the first embodiment will be mainly described, and components and components having the same functions as those of the first embodiment will be given the same names and symbols as those of the first embodiment. A description thereof will be omitted.

  FIG. 13 is a block diagram illustrating an example of the configuration of the customization system 1001 according to the second embodiment, and FIG. 14 is a block diagram illustrating an example of the configuration of the component server 1010 and the first MFP 1020 according to the second embodiment. FIG. In the component server 1010 of the second embodiment, the processing contents of the distribution unit 1132 and the reception unit 1134 of the control unit 1130, the point that the update unit 1136 is added to the control unit 1130, and the component storage unit 1122 of the storage unit 1120 The stored information is different from the component server 10 of the first embodiment. Further, in the first multifunction device 1020, the point that the login unit 1271 is added to the control unit 1270, and the processing contents of the acquisition unit 1272 and the upload unit 1278 of the control unit 1270 are the same as those of the first multifunction device 20 of the first embodiment. Is different. Accordingly, these functional units will be described below.

  The component storage unit 1122 of the component server 1010 stores the component in association with user identification information for identifying the user. FIG. 15 is a diagram illustrating an example of components stored in the component storage unit 1122. In the example shown in FIG. 15, a copy component, a fax component, a printer component, and a scanner component are stored in the default area. In the user area, a copy component, a fax component, and a scanner component are stored. The component stored in the default area is associated with user identification information indicating the default user, and the component stored in the user area is associated with user identification information indicating the user in the user area. Yes.

  Returning to FIG. 14, the reception unit 1134 of the component server 1010 receives user identification information from a multifunction peripheral such as the first multifunction peripheral 1020 or the second multifunction peripheral 1021.

  The distribution unit 1132 of the component server 1010 acquires a component associated with the user identification information received by the reception unit 1134 from the component storage unit 1122 and sends it to a multifunction device such as the first multifunction device 1020 or the second multifunction device 1021. Deliver and customize.

  When updating the component associated with the user identification information indicating the default user, the update unit 1136 of the component server 1010 is a component of the same type as the component and indicates a user other than the default user. The component associated with the information is also updated. For example, when updating the copy component stored in the default area shown in FIG. 15, the update unit 1136 also upgrades the copy component stored in the user area.

  The login unit 1271 of the first multifunction device 1020 receives user identification information from the operation unit 240 or the like and performs login processing.

  The acquisition unit 1272 of the first multifunction device 1020 transmits the user identification information received by the login unit 1271 to the component server 1010, and acquires the component corresponding to the user identification information.

  The upload unit 1278 of the first multifunction device 1020 transmits the component created by the creation unit 276 to the component server 1010 together with the user identification information received by the login unit 1271, and uploads the component.

  FIG. 16 is a flowchart illustrating an example of upload processing performed in the customization system 1001 according to the second embodiment.

  First, the creation unit 276 of the first multifunction device 1020 customizes the first multifunction device 1020 to create a component including the customization content, and stores the component in the storage unit 220 (step S300).

  Subsequently, the upload unit 1278 of the first multifunction device 1020 checks whether or not a predetermined user is logged in by the login unit 1271 (step S302).

  When a predetermined user is logged in (Yes in step S302), the upload unit 1278 of the first multifunction device 1020 includes the component created by the creation unit 276 together with the user identification information used for login by the login unit 1271. The component is transmitted to the server 1010 and uploaded (step S304).

  Subsequently, the reception unit 1134 of the component server 1010 receives the user identification information and the component from the first multifunction device 1020, and stores the component in the user area of the user indicated by the user identification information of the component storage unit 1122 (step S306).

  On the other hand, when the predetermined user is not logged in (No in step S302), the upload unit 1278 of the first multifunction peripheral 1020 uploads the component created by the creation unit 276 to the component server 1010 (step S308).

  Subsequently, the reception unit 1134 of the component server 1010 receives the component from the first multifunction device 1020 and stores it in the default area of the component storage unit 1122 (step S310).

  FIG. 17 is a flowchart illustrating an example of distribution processing performed in the customization system 1001 according to the second embodiment.

  First, the reception unit 1134 of the component server 1010 receives access from the acquisition unit 1272 of the first multifunction device 1020 (step S400).

  Subsequently, the distribution unit 1132 of the component server 1010 checks whether or not the user identification information included in the access from the first multifunction device 1020 indicates a specific user (step S402).

  When the user identification information indicates a specific user (Yes in step S402), the distribution unit 1132 indicates that the component including the functional difference information for the model of the first MFP 1020 is the user indicated by the user identification information in the component storage unit 1122. It is confirmed whether it is stored in the user area (step S404).

  If there is a component including functional difference information for the model of the first multifunction device 1020 (Yes in step S404), the distribution unit 1132 acquires the component from the user area of the component storage unit 1122 and distributes the component (step S406). ).

  Subsequently, the acquisition unit 1272 of the first MFP 1020 acquires the component distributed from the component server 1010 (step S408).

  Subsequently, the switching unit 274 of the first MFP 1020 switches the component acquired by the acquisition unit 1272 to the default component and starts up (step S410).

  On the other hand, in step S402, when the user identification information does not indicate a specific user (indicates a default user) (No in step S402), the distribution unit 1132 includes functional difference information for the model of the first MFP 1020. It is confirmed whether the component is stored in the default area of the component storage unit 1122 (step S412).

  If there is a component including functional difference information for the model of the first MFP 1020 (Yes in step S412), the distribution unit 1132 acquires the component from the default area of the component storage unit 1122 and distributes it (step S414). ).

  The subsequent processes in steps S416 and S418 are the same as the processes in steps S408 and S410. In step S404, if there is no component including the functional difference information for the model of the first MFP 1020 (No in step S404), the component is not distributed from the component server 1010. The component remains activated. The same applies when there is no component including function difference information for the model of the first multifunction peripheral 1020 in step S412 (No in step S412).

  As described above, according to the second embodiment, customization contents can be easily shared in units of users even with different models. Also, the components stored in the user area can be upgraded in the same manner as the components stored in the default area.

  As for components, functional components may be managed in units of users as shown in FIG. 18, application components may be managed in units of users as shown in FIG. 19, or packages as shown in FIG. Components may be managed on a user basis.

(Third embodiment)
In the third embodiment, an example will be described in which components are separated into a default component not including customization contents and customization information indicating customization contents, and the separated customization information is managed for each user. In the following description, differences from the second embodiment will be mainly described, and components and components having the same functions as those of the second embodiment will be given the same names and symbols as those of the second embodiment. A description thereof will be omitted.

  FIG. 21 is a block diagram illustrating an example of the configuration of the customization system 2001 according to the third embodiment, and FIG. 22 is a block diagram illustrating an example of the configuration of the component server 2010 and the first MFP 1020 according to the third embodiment. FIG. In the component server 2010 of the third embodiment, the point that the separation unit 2138 and the combining unit 2140 are added to the control unit 2130, the processing content of the update unit 2136, and the information stored in the component storage unit 2122 of the storage unit 2120 are stored. This is different from the component server 1010 of the second embodiment. Hereinafter, these functional units will be described.

  The component storage unit 2122 of the component server 2010 stores a default component that does not include customization content, and stores customization information indicating the customization content in association with user identification information. FIG. 23 is a diagram illustrating an example of components and customization information stored in the component storage unit 2122. In the example shown in FIG. 23, a default copy component, a default fax component, a default printer component, and a default scanner component are stored in the component area. The default area stores copy customization information, fax customization information, printer customization information, and scanner customization information, and the user area stores copy customization information, fax customization information, printer customization information, and scanner customization information. Has been. Each customization information stored in the default area is associated with user identification information indicating a default user, and each customization information stored in the user area is replaced with user identification information indicating a user in the user area. It is associated.

  Returning to FIG. 22, the separation unit 2138 of the component server 2010 separates the component received by the reception unit 1134 into a default component and customization information. For example, the separation unit 2138 separates the default component and the customization information using identification information that identifies the default component and the customization information included in the component received by the reception unit 1134. Then, the separation unit 2138 associates the separated customization information with the user identification information received by the reception unit 1134 and stores it in the component storage unit 2122. If the separated default component is not stored in the component storage unit 2122, the separation unit 2138 also stores the default component.

  The combining unit 2140 of the component server 2010 acquires the default component and the customization information associated with the user identification information received by the receiving unit 1134 from the component storage unit 2122 and combines them.

  When updating the default component, the update unit 2136 of the component server 2010 also updates customization information of the same type as the default component. For example, when updating the default copy component stored in the component area shown in FIG. 23, the update unit 2136 also upgrades the copy customization information stored in the default area and the user area.

  FIG. 24 is a flowchart illustrating an example of upload processing performed in the customization system 2001 according to the third embodiment.

  First, the processes of steps S500 to S504 are the same as the processes of steps S300 to S304, respectively.

  Subsequently, when the user identification information and the component are received from the first multifunction device 1020 by the reception unit 1134 of the component server 2010, the separation unit 2138 of the component server 2010 converts the component received by the reception unit 1134 into the default component and the customization information. (Step S505).

  Subsequently, the separating unit 2138 stores the separated customization information in the user area of the user indicated by the user identification information received by the receiving unit 1134 in the user area of the component storage unit 2122 (step S506).

  On the other hand, the process of step S508 is the same as the process of step S308.

  Subsequently, when a component is received from the first MFP 1020 by the reception unit 1134 of the component server 2010, the separation unit 2138 of the component server 2010 separates the component received by the reception unit 1134 into default components and customization information. (Step S509).

  Subsequently, the separation unit 2138 stores the customized information separated in the default area of the component storage unit 2122 (step S510).

  FIG. 25 is a flowchart illustrating an example of distribution processing performed in the customization system 2001 according to the third embodiment.

  First, the process of step S600 is the same as the process of step S400.

  Subsequently, the combining unit 2140 of the component server 2010 confirms whether or not the user identification information included in the access from the first multifunction device 1020 indicates a specific user (step S602).

  When the user identification information indicates a specific user (Yes in step S602), the combining unit 2140 is in the user area of the component storage unit 2122 and the user area of the user indicated by the user identification information received by the receiving unit 1134. It is confirmed whether customization information including function difference information for the model of the first multifunction device 1020 is stored (step S604).

  When the customization information including the function difference information for the model of the first MFP 1020 is in the user area (Yes in step S604), the combining unit 2140 acquires the customization information and the default component from the component storage unit 2122. Join.

  Subsequently, the distribution unit 1132 of the component server 2010 distributes the combined components (step S606).

  The subsequent processing in steps S608 and S610 is the same as the processing in steps S408 and S410.

  On the other hand, in step S602, when the user identification information does not indicate a specific user (indicates a default user) (No in step S602), the combining unit 2140 includes functional difference information for the model of the first MFP 1020. It is confirmed whether the customization information is stored in the default area of the component storage unit 2122 (step S612).

  When the customization information including the function difference information for the model of the first MFP 1020 is in the default area (Yes in step S612), the combining unit 2140 acquires the customization information and the default component from the component storage unit 2122. Join.

  Subsequently, the distribution unit 1132 distributes the combined components (step S614).

  The subsequent processing in steps S616 and S618 is the same as the processing in steps S416 and S418. If customization information including functional difference information for the model of the first multifunction device 1020 is not in the user area in step S604 (No in step S604), the component is not distributed from the component server 2010, so the first multifunction device 1020 is not distributed. Will keep the default component running. The same applies to the case where the customization information including the function difference information for the model of the first MFP 1020 is not in the default area in step S612 (No in step S612).

  As described above, according to the third embodiment, the component is separated into the default component and the customization information, and the separated customization information is managed for each user. Therefore, the customization content for each user is managed by the difference from the default component. it can. Thereby, the capacity | capacitance of the information regarding the component memorize | stored in a component server can be reduced, and even when the storage capacity of a component server is small, it can cope. Also, the customization information stored in the default area and the user area can be upgraded in the same manner as the default component.

  The default components and customization information may be managed in units of functions as shown in FIG. 26, may be managed in units of applications as shown in FIG. 27, or may be managed in units of packages as shown in FIG. May be managed. When managing default components and customization information in units of functions, separation / combination is also performed in units of functions. When managing default components and customization information in units of applications, separation / combination is also performed in units of applications. When information is managed in package units, separation / combination is also performed in package units.

(Hardware configuration)
An example of the hardware configuration of the component server and the multifunction peripheral according to the first to third embodiments will be described.

  The component servers 10, 1010, and 2010 of the first to third embodiments include a control device such as a CPU, a storage device such as a ROM and a RAM, an external storage device such as an HDD and a removable drive device, and a display such as a display. The apparatus includes an input device such as a keyboard and a mouse, and has a hardware configuration using a normal computer.

  The customization program executed by the component servers 10, 1010, and 2010 of the first to third embodiments is an installable format or executable file, and is a CD-ROM, CD-R, memory card, DVD (Digital Versatile Disk), flexible disk (FD), and the like are stored in a computer-readable storage medium and provided.

  Further, the customization program executed by the component servers 10, 1010, and 2010 of the first to third embodiments is stored on a computer connected to a network such as the Internet, and is provided by being downloaded via the network. It may be. Further, the customization program executed by the component servers 10, 1010, and 2010 of the first to third embodiments may be provided or distributed via a network such as the Internet. Further, a customization program executed by the component servers 10, 1010, and 2010 of the first to third embodiments may be provided by being incorporated in advance in a ROM or the like.

  The customization program executed by the component servers 10, 1010, and 2010 according to the first to third embodiments has a module configuration for realizing the above-described units on a computer. As actual hardware, the CPU reads out the customization program from the HDD to the RAM and executes it, so that the above-described units are realized on the computer.

  FIG. 29 is a block diagram illustrating an example of a hardware configuration of the MFP according to the first to third embodiments.

  As shown in FIG. 26, the multifunction peripheral has a configuration in which a controller 310 and an engine unit (Engine) 360 are connected by a PCI (Peripheral Component Interconnect) bus. The controller 310 is a controller that controls the entire MFP, drawing, communication, and input from the operation display unit 320. The engine unit 360 is a printer engine that can be connected to a PCI bus, and is, for example, a monochrome plotter, a 1-drum color plotter, a 4-drum color plotter, a scanner, or a fax unit. The engine unit 360 includes an image processing part such as error diffusion and gamma conversion in addition to a so-called engine part such as a plotter.

  The controller 310 includes a CPU 311, a north bridge (NB) 313, a system memory (MEM-P) 312, a south bridge (SB) 314, a local memory (MEM-C) 317, and an ASIC (Application Specific Integrated Circuit). 316 and a hard disk drive (HDD) 318, and the north bridge (NB) 313 and the ASIC 316 are connected by an AGP (Accelerated Graphics Port) bus 315. The MEM-P 312 further includes a ROM 312a and a RAM 312b.

  The CPU 311 performs overall control of the multifunction peripheral, has a chip set including the NB 313, the MEM-P 312 and the SB 314, and is connected to other devices via the chip set.

  The NB 313 is a bridge for connecting the CPU 311 to the MEM-P 312, SB 314, and AGP 315, and includes a memory controller that controls reading and writing to the MEM-P 312, a PCI master, and an AGP target.

  The MEM-P 312 is a system memory used as a memory for storing programs and data, a memory for developing programs and data, a memory for drawing printers, and the like. The ROM 312a is a read-only memory used as a program / data storage memory, and the RAM 312b is a writable / readable memory used as a program / data development memory, a printer drawing memory, or the like.

  The SB 314 is a bridge for connecting the NB 313 to a PCI device and peripheral devices. The SB 314 is connected to the NB 313 via a PCI bus, and a network interface (I / F) unit and the like are also connected to the PCI bus.

  The ASIC 316 is an IC (Integrated Circuit) for image processing having hardware elements for image processing, and has a role of a bridge for connecting the AGP 315, the PCI bus, the HDD 318, and the MEM-C 317. The ASIC 316 includes a PCI target and an AGP master, an arbiter (ARB) that forms the core of the ASIC 316, a memory controller that controls the MEM-C 317, and a plurality of DMACs (Direct Memory) that rotate image data using hardware logic. Access Controller) and a PCI unit that performs data transfer between the engine unit 360 via the PCI bus. The ASIC 316 is connected to an FCU (Fax Control Unit) 330, a USB (Universal Serial Bus) 340, and an IEEE 1394 (the Institute of Electrical and Electronics Engineers 1394) interface 350 via a PCI bus. The operation display unit 320 is directly connected to the ASIC 316.

  A MEM-C 317 is a local memory used as a copy image buffer and a code buffer, and an HDD (Hard Disk Drive) 318 is a storage for storing image data, programs, font data, and forms. It is.

  The AGP 315 is a bus interface for a graphics accelerator card that has been proposed to speed up graphics processing. The AGP 315 speeds up the graphics accelerator card by directly accessing the MEM-P 312 with high throughput. .

  Note that the customization program executed by the multifunction machine of the first to third embodiments is provided by being incorporated in advance in a ROM or the like.

  The customization program executed in the multifunction machine of the first to third embodiments is a file in an installable format or an executable format, and is a CD-ROM, flexible disk (FD), CD-R, DVD (Digital Versatile Disk). For example, the program may be provided by being recorded in a computer-readable storage medium.

  Furthermore, the customization program executed by the multifunction peripheral according to the first to third embodiments may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. . Further, the customization program executed by the MFPs of the first to third embodiments may be provided or distributed via a network such as the Internet.

  The customization program executed by the multifunction machine according to the first to third embodiments has a module configuration for realizing the above-described units on a computer. As actual hardware, the CPU 311 reads out a customization program from the ROM 312a onto the RAM 312b and executes it, whereby the above-described units are realized on the computer.

(Modification)
In the second embodiment, license information indicating the use condition of the component may be associated with the component and stored in the component storage unit. In this case, when updating the license information of the component associated with the user identification information indicating the default user, the update unit is a component of the same type as the component and indicates a user other than the default user The license information of the component associated with the identification information is also updated. For example, when updating the license information of the copy component stored in the default area shown in FIG. 15, the update unit also updates the license information of the copy component stored in the user area. When the license information does not satisfy the use conditions, the distribution unit does not distribute the component associated with the license information.

  In this way, the component license information stored in the user area can be managed in the same manner as the component license information stored in the default area. The license information may be license information managed by a license server (not shown) that manages the license information.

  Also in the first embodiment, as in the third embodiment, the component is separated into a default component not including customization contents and customization information indicating customization contents, and the separated customization information is managed for each user. You may do it.

DESCRIPTION OF SYMBOLS 1,1001,2001 Customization system 2 Network 10,1010,2010 Component server 20,1020 1st multifunction device 21,1021 2nd multifunction device 110 Communication part 120,1120,2120 Storage part 122,1122,2122 Component storage part 130, 1130, 2130 Control unit 132, 1132 Distribution unit 134, 1134 Reception unit 210 Communication unit 220 Storage unit 230 Display unit 240 Operation unit 250 Reading unit 260 Formation unit 270, 1270 Control unit 272, 1272 Acquisition unit 274 Switching unit 276 Creation unit 278 , 1278 Upload unit 310 Controller 311 CPU
312 System memory 312a ROM
312b RAM
313 North Bridge 314 South Bridge 315 AGP Bus 316 ASIC
317 Local memory 318 Hard disk drive 320 Operation display unit 330 FCU
340 USB
350 IEEE 1394 interface 360 Engine unit 1136, 2136 Update unit 1271 Login unit 2138 Separation unit 2140 Coupling unit

JP 2001-306204 A

Claims (15)

A component server connected to an image forming apparatus for forming an image via a network,
Component storage means for storing components including customization contents for each model of the image forming apparatus;
Distribution means for distributing and customizing the component to the image forming apparatus;
A component server comprising: The component storage means stores the component in association with user identification information for identifying a user,
A receiving unit that receives the user identification information from the image forming apparatus;
The component server according to claim 1, wherein the distribution unit acquires the component associated with the received user identification information from the component storage unit and distributes the component to the image forming apparatus.   The component server according to claim 1, wherein the component storage unit stores the component in a function unit, an application unit, or a package unit. The user identification information indicates a user including a default user,
When updating the component associated with the user identification information indicating the default user, the component is associated with the user identification information indicating a component other than the default user, which is a component of the same type as the component. The component server according to claim 2, further comprising an updating unit that updates a given component. The component storage means stores license information indicating use conditions of the component in association with the component,
The user identification information indicates a user including a default user,
When updating the license information of the component associated with the user identification information indicating the default user, the user identification indicating a user other than the default user, which is a component of the same type as the component The component server according to claim 2, further comprising an update unit that updates the license information of the component associated with the information. The component storage means stores a default component not including the customization content, and stores customization information indicating the customization content in association with the user identification information,
Further comprising a combining means for acquiring and combining the default component and the customization information associated with the user identification information received by the receiving means from the component storage means,
The component server according to claim 2, wherein the distribution unit distributes the combined component to the image forming apparatus. The receiving unit receives a component created in the image forming apparatus and the user identification information from the image forming apparatus;
Separating means for separating the received component into the default component and the customization information, and storing the separated customization information and the received user identification information in association with each other in the component storage means. The component server according to claim 6.   The component server according to claim 6 or 7, wherein the component storage unit stores the default component and the customization information in units of functions, applications, or packages.   The component server according to any one of claims 6 to 8, further comprising an updating unit that updates the customization information of the same type as the default component when the default component is updated. An image forming apparatus connected to a component server via a network,
An acquisition means for acquiring a component including customization contents for each model of the image forming apparatus from the component server;
Switching means for switching and starting the component with a default component;
An image forming apparatus comprising:   The image forming apparatus according to claim 10, wherein the acquisition unit transmits user identification information for identifying a user to the component server, and acquires the component corresponding to the user identification information.   A customization system comprising: the component server according to any one of claims 1 to 9; and the image forming apparatus according to claim 10 or 11. A customization method executed by a component server connected to an image forming apparatus for forming an image via a network,
The component server is
Component storage means for storing components including customization contents for each model of the image forming apparatus,
A customization method comprising: a distribution step in which distribution means distributes the component to the image forming apparatus and customizes the component. A customization method executed by an image forming apparatus connected to a component server via a network,
An acquisition step of acquiring a component including customization contents for each model of the image forming apparatus from the component server;
A switching step in which the switching means switches the component to a default component and activates the component;
A customization method characterized by including:   The customization program for making a computer perform the customization method of Claim 13 or 14.

Images