JP5821217B2 - Image forming apparatus, management method, management program, and recording medium - Google Patents

Description

  The present invention relates to an image forming apparatus, a management method, a management program, and a recording medium.

  2. Description of the Related Art In recent years, an image forming apparatus that uses a publicly disclosed API (Application Program Interface) to develop and install a new application program after shipment has become common. An application program (hereinafter referred to as “extended application”) developed using such an API can realize a complicated workflow, and can improve the user's business efficiency (for example, Patent Document 1).

  On the other hand, the image forming apparatus generally has an event notification mechanism for notifying the user of the start or end of a requested job or the occurrence of an abnormality in the image forming apparatus or a decrease in the remaining amount of consumables. (For example, patent document 2).

  Regarding the change in the state of the extended application as described above, it is convenient for the user if it can be a notification target in the same manner as the event related to the existing function of the image forming apparatus. At this time, if the event notification mechanism is implemented for each extended application, resources of limited devices are consumed inefficiently.

  In addition, if an event notification mechanism is implemented for each extended application, the expandability and maintainability of the event notification mechanism are impaired. This is because a modification for extending the event notification mechanism is required for each extended application.

  Furthermore, there are events that cannot be notified by the extended application itself regarding changes in its own state. For example, when the extended application ends abnormally, the extended application itself may not be able to notify the event.

  The present invention has been made in view of the above points, and an object thereof is to provide an image forming apparatus, a management method, a management program, and a recording medium capable of appropriately managing a change in state relating to an application program. .

  Therefore, in order to solve the above-described problem, the image forming apparatus monitors the state of the application program based on the list information of the installed application programs and detects a change in the state, and the detected state It is determined by the generation determination unit that determines whether or not the change in the condition matches the generation condition of the event information stored in the first storage unit and the generation determination unit, the change in the state matches the generation condition. A generation unit that generates event information indicating a change in the state, and an output unit that outputs the event information.

  In such an image forming apparatus, it is possible to appropriately manage a change in state related to the application program.

  According to the present invention, it is possible to appropriately manage a change in state related to an application program.

It is a figure which shows the structural example of the apparatus management system of 1st embodiment. 1 is a diagram illustrating an example of a hardware configuration of an image forming apparatus according to an embodiment of the present invention. FIG. 3 is a diagram illustrating a software configuration example of an image forming apparatus according to a first embodiment. 1 is a diagram illustrating an example of a functional configuration of an image forming apparatus according to a first embodiment. FIG. 6 is a sequence diagram for explaining an example of a processing procedure executed by the image forming apparatus according to the first embodiment. It is a figure which shows the structural example of the production | generation rule memory | storage part of 1st embodiment. It is a figure which shows the structural example of the output rule memory | storage part of 1st embodiment. It is a figure which shows the structural example of the apparatus management system of 2nd embodiment. It is a figure which shows the function structural example of the image forming apparatus in 2nd embodiment. FIG. 10 is a sequence diagram for explaining an example of a processing procedure executed by the image forming apparatus according to the second embodiment. It is a figure which shows the structural example of the production | generation rule memory | storage part of 2nd embodiment. It is a figure which shows the structural example of the output rule memory | storage part of 2nd embodiment. It is a figure which shows the structural example of the apparatus management system of 3rd embodiment. It is a figure which shows the function structural example of the image forming apparatus in 3rd embodiment. FIG. 10 is a sequence diagram for explaining an example of a processing procedure executed by an image forming apparatus according to a third embodiment. It is a figure which shows the function structural example of the event output part in 4th embodiment. It is a figure which shows the example of a display of a corresponding | compatible information setting screen. It is a figure which shows an example of the setting screen of an output method mounting part.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a configuration example of a device management system according to the first embodiment. In the device management system 1 in FIG. 1, one or more image forming apparatuses 10, an event management server 20, and an administrator terminal 30 are each a network 50 such as a LAN (Local Area Network) (whether wired or wireless). It is connected so that it can communicate via.

  The image forming apparatus 10 is a multifunction machine that realizes two or more functions of printing, scanning, copying, FAX transmission / reception, and the like with a single casing. However, a device having any one function alone may be used as the image forming apparatus 10. The image forming apparatus 10 can be installed or uninstalled with a program for the purpose of function expansion or the like.

  The event management server 20 is a computer having a management function of information indicating various events that occur in the image forming apparatus 10 (hereinafter referred to as “event information”). That is, in the present embodiment, the event management server 20 is a default output destination (or notification destination) for event information of the image forming apparatus 10. Note that an event refers to, for example, a change in the state of the image forming apparatus 10. The state of the image forming apparatus 10 includes not only a change in the state of hardware resources of the image forming apparatus 10 but also a change in the state of software.

  The administrator terminal 30 is an information processing apparatus such as a PC used by the administrator of the image forming apparatus 10. In the present embodiment, the administrator terminal 30 is an output destination of highly urgent event information.

  FIG. 2 is a diagram illustrating a hardware configuration example of the image forming apparatus according to the embodiment of the present invention. In FIG. 1, the image forming apparatus 10 includes hardware such as a controller 11, a scanner 12, a printer 13, a modem 14, an operation panel 15, a network interface 16, and an SD card slot 17.

  The controller 11 includes a CPU 111, a RAM 112, a ROM 113, an HDD 114, an NVRAM 115, and the like. The ROM 113 stores various programs and data used by the programs. The RAM 112 is used as a storage area for loading a program, a work area for the loaded program, and the like. The CPU 111 realizes various functions by processing a program loaded in the RAM 112. The HDD 114 records programs and various data used by the programs. In the NVRAM 115, various setting information and the like are recorded.

  The scanner 12 is hardware (image reading means) for reading image data from a document. The printer 13 is hardware (printing means) for printing print data on printing paper. The modem 14 is hardware for connecting to a telephone line, and is used to execute transmission / reception of image data by FAX communication. The operation panel 15 is hardware including input means such as buttons for accepting input from the user, display means such as a liquid crystal panel, and the like. The liquid crystal panel may have a touch panel function. In this case, the liquid crystal panel also functions as an input unit. The network interface 16 is hardware for connecting to a network such as a LAN (whether wired or wireless). The SD card slot 17 is used for reading a program recorded on the SD card 80. That is, in the image forming apparatus 10, not only the program recorded in the ROM 113 but also the program recorded in the SD card 80 can be loaded into the RAM 112 and executed. The SD card 80 may be replaced by another recording medium (for example, a CD-ROM or a USB (Universal Serial Bus) memory). That is, the type of recording medium corresponding to the positioning of the SD card 80 is not limited to a predetermined one. In this case, the SD card slot 17 may be replaced by hardware corresponding to the type of recording medium.

  FIG. 3 is a diagram illustrating a software configuration example of the image forming apparatus according to the first embodiment. In FIG. 1, the image forming apparatus 10 includes one or more extended applications 121, a monitoring unit 122, an event notification unit 123, and the like.

  The extended application 121 is an application program that is installed in the image forming apparatus 10. For example, the extended application 121 is created using a predetermined API (Application Program Interface) that the image forming apparatus 10 has.

  The monitoring unit 122 monitors the state of the image forming apparatus 10. For example, the monitoring unit 122 monitors the state of each extended application 121. The monitoring unit 122 generates event information indicating a change in the state of the extended application 121 and inputs the event information to the event notification unit 123. Note that event information that can be notified by each extended application 121 is input from each extended application 121 to the event notification unit 123.

  The event notification unit 123 outputs (or notifies) the input event information to an event output destination (or notification destination). In the first embodiment, the event output destination is the event management server 20 or the administrator terminal 30.

  Note that the monitoring unit 122 and the event notification unit 123 are realized by processing executed by the CPU 111 by a program installed in the image forming apparatus 10.

  FIG. 4 is a diagram illustrating a functional configuration example of the image forming apparatus according to the first embodiment. In the figure, the monitoring unit 122 includes an extended application monitoring unit 131, an event generation determination unit 132, a generation rule storage unit 133, and the like.

  The extended application monitoring unit 131 monitors the state of each extended application 121. The extended application 121 to be monitored can be identified based on information stored in the installation information storage unit 124. That is, when the extended application 121 is installed, the attribute information of the extended application 121 is recorded in the installation information storage unit 124. When the extended application 121 is uninstalled, the attribute information of the extended application 121 is deleted from the installation information storage unit 124. Therefore, the installation information storage unit 124 stores a list of attribute information of the extended application 121 installed in the image forming apparatus 10. Note that the installation information storage unit 124 can be realized using, for example, the HDD 114 or the NVRAM 115.

  When a change occurs in the state of the extended application 121, the event generation determination unit 132 uses the generation rule storage unit 133 to determine whether to generate event information related to the change. The generation rule storage unit 133 stores event information generation rules. The event information generation rule is information indicating what kind of event information should be generated when a change in state occurs. The generation rule storage unit 133 can be realized using, for example, the HDD 114 or the NVRAM 115.

  The event notification unit 123 includes an event generation unit 141, an event analysis unit 142, an output method determination unit 143, an event output unit 144, and the like.

  The event generation unit 141 generates event information as specified by the extended application 121 or the extended application monitoring unit 131. The event analysis unit 142 analyzes event information generated by the event generation unit 141. The output method determination unit 143 uses the output rule storage unit 145 to determine the event information output method (or output form). The output rule storage unit 145 stores output rules. The output rule is information indicating an output method (or output form) of event information according to the content of the event information. The output rule storage unit 145 can be realized using the HDD 114 or the NVRAM 115, for example. The event output unit 144 outputs event information according to the output method (or output form) determined by the output method determination unit 143.

  Hereinafter, a processing procedure executed by the image forming apparatus 10 according to the first embodiment will be described. FIG. 5 is a sequence diagram for explaining an example of a processing procedure executed by the image forming apparatus according to the first embodiment.

  The extended application monitoring unit 131 periodically monitors the state of each extended application 121 whose attribute information is recorded in the installation information storage unit 124 (S101). For example, when the extended application monitoring unit 131 detects that an extended application 121 has stopped (S102), the extended application monitoring unit 131 requests the event generation determination unit 132 to determine whether or not to generate event information (S103). At this time, the extended application monitoring unit 131 notifies the event generation determination unit 132 of what kind of state change has occurred with respect to the extended application 121. Here, it is notified that the extended application 121 has been stopped.

  The event generation determination unit 132 refers to the generation rule storage unit 133 to determine whether or not to generate event information and what kind of event information should be generated, and the determination result is used as the extended application monitoring unit 131. (S104).

  FIG. 6 is a diagram illustrating a configuration example of the generation rule storage unit according to the first embodiment. The figure shows an example in which two generation rules, generation rule 1 and generation rule 2, are recorded.

  Each generation rule includes a generation condition, a generation content, and the like. The generation condition is a condition for generating event information in response to a change in the state of the extended application 121. It can be said that the generation condition is a notification condition of event information. This is because determining whether to generate event information is equivalent to determining whether to notify event information. The generation content is the content of event information to be generated in accordance with a change in state that matches the generation condition. In the present embodiment, the event information includes information such as id, urgency level, and message. id is an identifier of event information. The urgency level is the urgency of the state change indicated by the event information. The message is an arbitrary character string indicating a change in state indicated by the event information.

  In the drawing, the generation rule 1 is described in parentheses (extended application monitoring unit), and the generation rule 2 is described in parentheses (extended application). This is that the generation rule 1 is a generation rule related to a change in state detected by the extended application monitoring unit 131, and the generation rule 2 is a generation rule related to state conversion detected by each extended application 121 itself. Show.

  Here, an example in which the extended application monitoring unit 131 detects the stop of the extended application 121 is described. Therefore, the change (that is, stop) of the state of the extended application 121 matches the generation condition of the generation rule 1. Therefore, the event generation determination unit 132 outputs the generation content of the generation rule 1 to the extended application monitoring unit 131.

  Subsequently, the extended application monitoring unit 131 specifies the generation content and requests the event generation unit 141 to generate event information (S105). In response to the request, the event generation unit 141 generates event information in which a unique number is set for each event information in the id, “high” is set in the urgency level, and the reason for the stop is set in the message. The event generation unit 141 outputs the generated event information (hereinafter referred to as “target event information”) to the event analysis unit 142 (S106). The reason for the stop may be notified from the extended application monitoring unit 131 to the event generation unit 141 together with the request in step S105, for example.

  Subsequently, the event analysis unit 142 analyzes the target event information, and acquires values of id, urgency level, and message from the target event information. Subsequently, the event analysis unit 142 specifies each acquired value and requests the output method determination unit 143 to determine the output method of the target event information (S107).

  Subsequently, the output method determination unit 143 determines the output method of the target event information based on the designated id, the urgency level, or the message value and the output rule stored in the output rule storage unit 145.

  FIG. 7 is a diagram illustrating a configuration example of the output rule storage unit according to the first embodiment. The figure shows an example in which two output rules, output rule 1 and output rule 2, are recorded.

  Each output rule includes application conditions, an output method, and the like. The application condition is a condition for applying the output rule. The output method is an output method when the output rule is applied.

  The urgency level of the target event information is “high”. Therefore, both output rules 1 and 2 apply here. Therefore, the output method determination unit 143 outputs two output methods, “send mail to administrator” and “forward to event management server”, to the event analysis unit 142 (S108). Note that “urgency level = high / medium / low” in the output rule 2 in FIG. 7 indicates that the urgency level is “high”, “medium”, or “low”. In addition, for convenience, the value of the output method is written in a language that can be understood by humans, but may be an identifier indicating each output method.

  Subsequently, the event analysis unit 142 specifies the target event information and the two output methods that are the determination results by the output method determination unit 143, and requests the event output unit 144 to output the target event information (S109). . Subsequently, the event output unit 144 outputs the target event information by a designated output method. In other words, the event output unit 144 transfers the target event information to the event management server 20 (S110). In addition, the event output unit 144 transmits an e-mail including the target event information to the e-mail address of the administrator (S111). The administrator's e-mail address may be included as a parameter of the output method of the output rule 1, or may be recorded in the HDD 114 or the like as setting information of the event output unit 144, for example.

  As described above, according to the present embodiment, even when a change in state that cannot be supplemented by the extended application 121 itself, such as a stop (particularly, an abnormal system stop) occurs, the extended application monitoring is performed. The change is detected by the unit 131. Therefore, event information that cannot be notified by the extended application 121 can be notified. Moreover, the change of the state made into notification object can be limited with a production | generation rule. Therefore, it is possible to avoid complications due to notification of event information for all changes. Also, according to the output rule, the output destination of the event information is distributed according to the content of the event information. As a result, for example, flexible event information management such as promptly telling an administrator about a change in a state of high urgency, and accumulating in the event management server 20 about a change in a state of low urgency. A form can be realized. Note that the list of event information stored in the event management server 20 may be viewable at an arbitrary timing by, for example, a Web page.

  The subsequent steps S121 and subsequent steps are processing procedures that are executed when a serious (that is, highly urgent) internal error occurs in the extended application 121. When an internal error occurs, the extended application 121 itself refers to the generation rule storage unit 133 to determine whether event information needs to be generated. This is because the extended application monitoring unit 131 cannot detect an internal error. The occurrence of an internal error corresponds to the generation condition of generation rule 2 in FIG. Therefore, the extended application 121 specifies the generation content of the generation rule 2 and requests the event generation unit 141 to generate event information (S121). At this time, the urgency level is set to “high”. As described above, the processing after step S121 is processing in response to the occurrence of a “serious” internal error.

  In steps S122 to S127, the same processing procedure as in steps S106 to S111 described above is executed. That is, the urgency level of the event information to be processed in S122 to S127 is “high”, which is the same as the urgency level of the event information to be processed in S106 to S111. Further, as apparent from FIG. 7, application conditions are set for the urgency level in each output rule of the present embodiment. Therefore, event information for notifying a serious internal error of the extended application 121 is transferred to the event management server 20 (S126), and is transmitted by e-mail to the administrator's e-mail address (S127).

  Subsequent steps S131 and subsequent steps are processing procedures executed when a minor (that is, less urgent) internal error occurs in the extended application 121. In this case, the extended application 121 refers to the generation rule storage unit 133 to determine whether event information needs to be generated. The occurrence of an internal error corresponds to the generation condition of generation rule 2 in FIG. Therefore, the extended application 121 specifies the generation content of the generation rule 2 and requests the event generation unit 141 to generate event information (S131). At this time, the urgency level is set to “medium” or “low”. As described above, the processing after step S131 is processing according to the occurrence of a “minor” internal error.

  In steps S132 to S136, basically the same processing procedure as in steps S106 to S111 described above is executed. However, the urgency level of event information corresponding to a minor internal error is “medium” or “low”. Therefore, only the output rule 2 is applied to the event information. As a result, the event information is transferred to the event management server 20 (S136), but is not transmitted to the administrator's e-mail address.

  As described above, regarding the change in state detected internally by the extended application 121, the event information is generated and output by the same mechanism as the change in state detected by the extended application monitoring unit 131. Therefore, it is not necessary to implement the mechanism for each extended application 121.

  Next, a second embodiment will be described. In the second embodiment, differences from the first embodiment will be described. Therefore, the points not particularly mentioned may be the same as those in the first embodiment.

  FIG. 8 is a diagram illustrating a configuration example of a device management system according to the second embodiment. In FIG. 8, the same parts as those in FIG.

  In the device management system 2 shown in FIG. 8, event management servers 20 a and 20 b are connected to a network 50. The event management server 20 a is a computer that manages event information regarding errors or abnormalities of the extended application 121. The error includes a stop of the extended application 121, an illegal operation of the extended application 121, and the like. On the other hand, the event management server 20b is a computer that manages event information related to changes in states other than errors.

  FIG. 9 is a diagram illustrating a functional configuration example of the image forming apparatus according to the second embodiment. 9, parts that are the same as the parts shown in FIG. 4 are given the same reference numerals, and explanation thereof is omitted.

  9, the extended application monitoring unit 131 includes an extended application setting monitoring unit 151, a device setting monitoring unit 152, and the like. The extended application setting monitoring unit 151 monitors setting information of each extended application 121. The device setting monitoring unit 152 monitors setting information of the image forming apparatus 10. Note that the setting information of the extended application 121 and the setting information of the image forming apparatus 10 are recorded in the HDD 114 or the NVRAM 115, for example. The setting information of the image forming apparatus 10 refers to setting information that affects a plurality of extended applications 121 and functions other than the extended applications 121. That is, the setting information of the image forming apparatus 10 refers to setting information shared by a plurality of functions or setting information related to a function shared by a plurality of functions.

  Hereinafter, a processing procedure executed by the image forming apparatus 10 according to the second embodiment will be described. FIG. 10 is a sequence diagram for explaining an example of a processing procedure executed by the image forming apparatus according to the second embodiment.

  The extended application setting monitoring unit 151 acquires setting information (hereinafter referred to as “application setting information”) of each extended application 121 whose attribute information is recorded in the installation information storage unit 124 (S201, S202). Subsequently, the device setting monitoring unit 152 acquires setting information of the image forming apparatus 10 (hereinafter referred to as “device setting information”) (S203, S204). Note that steps S201 to S204 are executed periodically or in response to the update of the setting information of any extension application 121 or the setting information of the image forming apparatus 10.

  The extended application monitoring unit 131 compares or collates the acquired application setting information with the device setting information, and determines whether there is a mismatch with respect to the combination of both. What state is inconsistent may be set in an external file or the like, or may be defined in the logic of the extended application monitoring unit 131.

  When inconsistency is detected, the extended application monitoring unit 131 requests the event generation determination unit 132 to determine whether or not to generate event information (S205). At this time, the extended application monitoring unit 131 notifies the event generation determination unit 132 that a mismatch has occurred between the application setting information and the device setting information. The event generation determination unit 132 refers to the generation rule storage unit 133 to determine whether or not to generate event information and what kind of event information should be generated, and the determination result is used as the extended application monitoring unit 131. (S206).

  FIG. 11 is a diagram illustrating a configuration example of a generation rule storage unit according to the second embodiment. In the figure, the generation rule 2 has a generation condition that the combination of application setting information and device setting information is invalid. Therefore, the event generation determination unit 132 outputs the generation content of the generation rule 2 to the extended application monitoring unit 131.

  Subsequently, the extended application monitoring unit 131 specifies the generation content and requests the event generation unit 141 to generate event information (S207). In response to the request, the event generation unit 141 generates event information in which a unique number is set for each event information in the id, “error” is set in the type, and an invalid reason is set in the message. In addition, the event generation unit 141 sets “mail transmission” as the output method and sets the administrator's mail address as the output destination for the event information. The event generation unit 141 outputs the generated event information (hereinafter referred to as “target event information”) to the event analysis unit 142 (S208). The reason for the injustice may be notified from the extended application monitoring unit 131 to the event generation unit 141 together with the request in step S207, for example.

  Subsequently, the event analysis unit 142 analyzes the target event information, and acquires values of id, type, message, output method, and output destination from the event information. Subsequently, the event analysis unit 142 specifies each acquired value and requests the output method determination unit 143 to determine the output method of the target event information (S209).

  Subsequently, the output method determination unit 143 outputs the target event information output method based on the designated id, type, message, output method, or output destination value and the output rule stored in the output rule storage unit 145. Determine.

  FIG. 12 is a diagram illustrating a configuration example of the output rule storage unit according to the second embodiment. In the figure, the application condition of the output rule 1 is that the type of the target event information is “error”. Therefore, the output rule 1 is applied to the target event information. Further, the transmission method of the target event information is “mail transmission”. Therefore, the output rule 3 is also applied to the target event information. Therefore, the output method determination unit 143 outputs two output methods, “transfer to error server” and “send specified address mail”, to the event analysis unit 142 (S210). The “error server” indicates the event management server 20a.

  Subsequently, the event analysis unit 142 specifies the target event information and the two output methods that are the determination results of the output method determination unit 143, and requests the event output unit 144 to output the target event information (S211). . Subsequently, the event output unit 144 outputs the target event information by a designated output method. In other words, the event output unit 144 transfers the target event information to the event management server 20a (S212). In addition, the event output unit 144 transmits an e-mail including the target event information to the e-mail address of the administrator (S213).

  Subsequent steps S221 and subsequent steps are processing procedures executed when an internal error occurs in the extended application 121. In this case, the extended application 121 refers to the generation rule storage unit 133 to determine whether event information needs to be generated. The occurrence of an internal error corresponds to the generation condition of generation rule 3 in FIG. Therefore, the extended application 121 specifies the generation content of the generation rule 3 and requests the event generation unit 141 to generate event information (S221). Therefore, the event generation unit 141 generates event information in which a unique number is set for each event information in the id, “error” is set in the type, and the reason for the error is set in the message (S222).

  In steps S223 to S226, basically the same processing procedure as in steps S210 to S212 described above is executed. However, the event information corresponds only to the application condition of the output rule 1 in FIG. Accordingly, the event information is transferred to the event management server 20a (S226), but is not transmitted to the administrator's e-mail address.

  Subsequent steps S231 and subsequent steps are processing procedures executed in accordance with the execution of the processing of the extended application 121. In this case, the extended application 121 refers to the generation rule storage unit 133 to determine whether event information needs to be generated. The execution of the process corresponds to the generation condition of the generation rule 4 in FIG. Therefore, the extended application 121 specifies the generation content of the generation rule 3 and requests the event generation unit 141 to generate event information (S231). Therefore, the event generation unit 141 generates event information in which a unique number is set for each event information in the id, “log” is set in the type, and the processing content is set in the message (S232).

  Thereafter, in steps S233 to S236, basically the same processing procedure as that in steps S223 to S226 described above is executed. However, the event information corresponds to the application condition of the output rule 2 in FIG. Therefore, the event information is transferred to the event management server 20b (S236).

  As described above, according to the setting contents of the generation rule and the output rule, it is possible to distinguish the transfer destination between the event information indicating an error and the event information that is a mere log.

  Next, a third embodiment will be described. In the third embodiment, differences from the first or second embodiment will be described. Accordingly, the points not particularly mentioned may be the same as those in the first or second embodiment.

  FIG. 13 is a diagram illustrating a configuration example of a device management system according to the third embodiment. In FIG. 13, the same parts as those in FIG.

  The device management system 3 illustrated in FIG. 13 does not include the event management server 20. However, this does not indicate that the form in which the event management server 20 is included and the third embodiment are in an exclusive relationship. The event management server 20 may be connected to the network 50.

  FIG. 14 is a diagram illustrating a functional configuration example of the image forming apparatus according to the third embodiment. In FIG. 14, the same parts as those in FIG.

  In FIG. 14, the image forming apparatus 10 includes an event holding unit 125. The event holding unit 125 temporarily holds event information using the HDD 114, for example. That is, in the third embodiment, the event information generated by the event generation unit 141 is not necessarily output immediately to the output destination but can be temporarily stored in the event storage unit 125.

  Hereinafter, a processing procedure executed by the image forming apparatus 10 according to the third embodiment will be described. FIG. 15 is a sequence diagram for explaining an example of a processing procedure executed by the image forming apparatus according to the third embodiment.

  In the same figure, the event information generated by the event generation unit 141 is input to the event analysis unit 142, and the processing procedure after the output method for the event information is determined is shown. Therefore, the processing procedure before the processing procedure shown in the figure may be the same as the processing procedure described in the first or second embodiment (for example, steps S101 to S108 in FIG. 5).

  The event analysis unit 142 designates the event information generated by the event generation unit 141 and its output method, and requests the event output unit 144 to output the event information (S301). The event output unit 144 requests the event holding unit 125 to hold the event information and the output method regardless of the designated output method (S302). The event holding unit 125 records the event information in the HDD 114, for example. However, the event output unit 144 immediately outputs event information having high urgency such as event information having an urgency level of “high” or event information having a type of “error” according to an output method. You may perform the output process previously.

  Steps S301 and S302 are executed every time event information is generated. On the other hand, step S303 and subsequent steps are periodically executed. Therefore, event information generated in a regular cycle is held by the event holding unit 125.

  In step S <b> 303, the event analysis unit 142 requests the output method determination unit 143 to acquire the number of event information that is held (not yet output). The output method determination unit 143 inquires of the event holding unit 125 about the number of cases (S304). In response to the inquiry, the event holding unit 125 responds with the number of event information currently held (S305). The output method determination unit 143 returns the number of cases to the event analysis unit 142 (S306).

  When the number of cases reaches a predetermined number (for example, 10 cases), the event analysis unit 142 acquires each event information held by the event holding unit 125 and its output method (S307, S308). Subsequently, the event analysis unit 142 specifies the event information and the output method thereof, and requests the event output unit 144 to output the event information (S309). Here, it is preferable that the request in step S309 and the request in step S301 can be identified by the event output unit 144 so that steps S302 and after are not repeated. For example, in steps S309 and S301, the method called for the event output unit 144 may be different, and the arguments for the method may be different.

  Subsequently, the event output unit 144 outputs each event information by the designated output method (S310). For example, the event output unit 144 transmits an email including the event information to the administrator's email address.

  Subsequently, the event analysis unit 142 requests the event holding unit 125 to delete each piece of event information acquired in step S308 (S311). As a result, each event information is excluded from the holding target so as not to be output redundantly.

  As described above, according to the third embodiment, event information is temporarily held in the image forming apparatus 10 and is periodically output. Therefore, for example, when the output destination of event information is limited to the administrator terminal 30 as in the device management system 3, the complexity due to frequent notification of event information to the administrator terminal 30 is reduced. Can do.

  Next, a fourth embodiment will be described. In the fourth embodiment, the expandability of the event output unit 144 will be described. The fourth embodiment is implemented in combination with each of the above embodiments.

  In each of the above embodiments, the output destination of various event information can be changed according to the definition of the output rule. However, the output method that can be defined in the output rule is limited to the range of implementation of the event output unit 144. In other words, if the output method that can be handled by the event output unit 144 can be easily expanded, the types of output methods that can be defined in the output rule can be easily increased. .

  Therefore, in the fourth embodiment, the event output unit 144 has a configuration as shown in FIG.

  FIG. 16 is a diagram illustrating a functional configuration example of the event output unit according to the fourth embodiment. In the figure, the event output unit 144 includes an interface unit 161, one or more output method implementation units 162, a correspondence information storage unit 163, and the like.

  Each output method mounting unit 162 is a mounting corresponding to one output method. For example, a certain output method implementation unit 162 transmits event information by e-mail addressed to the administrator's e-mail address. Another output method implementation unit 162 transfers event information to the event management server 20.

  The interface unit 161 serves as an interface with the event analysis unit 142 and the like. In other words, the interface unit 161 accepts an event information output request from the event analysis unit 142 in which event information and an output method thereof are specified. The interface unit 161 causes the output method implementation unit 162 corresponding to the designated output method to output the event information.

  The correspondence information storage unit 163 stores correspondence information between the output method and the output method mounting unit 162. That is, the interface unit 161 refers to the correspondence information storage unit 163 and specifies the output method mounting unit 162 corresponding to the output method. Note that the correspondence information storage unit 163 can be realized using the HDD 114 or the NVRAM 115, for example.

  In the configuration as shown in FIG. 16, if the output method mounting unit 162 is a program module that can be dynamically linked, a new output method can be easily added. That is, if the output method mounting unit 162 according to the new output method is mounted and the corresponding information regarding the output method mounting unit 162 is registered in the corresponding information storage unit 163, basically, the existing part is not modified. A new output method can be made effective.

  The setting for the correspondence information storage unit 163 may be performed, for example, via a correspondence information setting screen that the interface unit 161 displays on the operation panel 15 or the supervisor terminal 30 or the like.

  FIG. 17 is a diagram illustrating a display example of the correspondence information setting screen. In the drawing, the correspondence information setting screen 510 includes a correspondence information list 511, an edit button 512, a delete button 513, an output method input area 514, an explanation input area 515, a mounting name input area 516, an add button 517, and the like.

  The correspondence information list 511 displays a list of correspondence information stored in the correspondence information storage unit 163. Each correspondence information includes items such as an output method, a description, and a mounting name. The output method is a character string for identifying the output method. That is, the character string is set as the output method of the output rule storage unit 145. The contents of the figure correspond to the output rule storage unit 145 of FIG. The description is a character string that describes the contents of the output method. The implementation name is a program module name of the output method implementation unit 162 corresponding to the output method.

  When one of the correspondence information check buttons 511 b is checked in the correspondence information list 511 and the delete button 513 is pressed, the correspondence information is deleted from the correspondence information storage unit 163. When the edit button 512 is pressed, the output method, description, and implementation name of the corresponding information are displayed in the output method input area 514, the description input area 515, or the implementation name input area 516, and can be edited. It becomes. When the add button 517 is pressed after editing, the edited correspondence information is added to the correspondence information storage unit 163. For example, when the output method implementation unit 162 is upgraded, the output method implementation unit 162 after the upgrade can be validated by updating the implementation name with the module name after the upgrade.

  In addition, when the output method input area 514, the description input area 515, and the mounting name input area 516 are empty, when a value is input to each area and the add button 517 is pressed, new correspondence information is stored in the correspondence information storage area. Part 163 is recorded.

  Setting of setting information unique to each output method mounting unit 162 may be performed via a setting screen displayed on the operation panel 15 or the supervisor terminal 30 by each output method mounting unit 162.

  FIG. 18 is a diagram illustrating an example of a setting screen of the output method mounting unit. The setting screen 520 in FIG. 11 includes an output method display area 521, an explanation display area 522, a mounting name display area 523, an update button 524, an administrator address input area 525, an OK button 526, and the like.

  In the output method display area 521, the description display area 522, and the mounting name display area 523, the output method, description, or mounting name of the output method mounting unit 162 that is currently set is displayed.

  The administrator address input area 524 is an area for inputting an administrator's mail address. That is, the setting screen 520 in FIG. 18 is an example of a setting screen related to the output method mounting unit 162 that performs mail transmission to the administrator. Therefore, for the output method mounting unit 162 related to another output method, an input area related to setting information unique to the other output method mounting unit 162 is displayed. When the OK button 526 is pressed, the mail address input in the administrator address input area 524 is set in the output method implementation unit 162.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

1, 2, 3 Device management system 10 Image forming apparatus 11 Controller 12 Scanner 13 Printer 14 Modem 15 Operation panel 16 Network interface 17 SD card slot 20, 20a, 20b Event management server 30 Administrator terminal 80 SD card 111 CPU
112 RAM
113 ROM
114 HDD
115 NVRAM
121 Extended Application 122 Monitoring Unit 123 Event Notification Unit 124 Installation Information Storage Unit 125 Event Holding Unit 131 Extended Application Monitoring Unit 132 Event Generation Determination Unit 133 Generation Rule Storage Unit 141 Event Generation Unit 142 Event Analysis Unit 143 Output Method Determination Unit 144 Event Output Unit 151 extended application setting monitoring unit 152 device setting monitoring unit 161 interface unit 162 output method mounting unit 163 correspondence information storage unit

JP 2005-269619 A JP 2004-187008 A

Claims (10)

Monitoring means for monitoring the status of the application program based on list information of installed application programs and detecting a change in the status;
Generation determination means for determining whether or not the detected change in state matches a generation condition of event information stored in the first storage means;
A generation unit configured to generate event information indicating the change in the state when the generation determination unit determines that the change in the state matches the generation condition;
Holding means for holding event information indicating conversion of a state that matches a generation condition excluding a part of the generation conditions among the event information generated by the generation means;
An output means for outputting the event information when the number of event information held by the holding means reaches a predetermined number ;
The output means outputs the event information that matches the part of the generation conditions immediately according to the generation by the generation means ,
The partial generation conditions include that the application program has stopped and that an error has occurred with respect to the application program.
Image forming apparatus.   The image according to claim 1, wherein the output unit selects an output destination of the event information with reference to a second storage unit that stores information indicating an output destination of the event information according to the content of the event information. Forming equipment.   The monitoring unit compares the first setting information related to the application program with the second setting information related to the image forming apparatus, and determines the mismatch of the combination of the first setting information and the second setting information. The image forming apparatus according to claim 1, wherein the image forming apparatus is detected. A monitoring procedure for monitoring the state of the application program based on a list of installed application programs and detecting a change in the state;
A generation determination procedure for determining whether the detected change in the state matches a generation condition of event information stored in the first storage unit;
In the generation determination procedure, when it is determined that the state change matches the generation condition, a generation procedure for generating event information indicating the state change;
Among the event information generated by the generation procedure, a holding procedure for holding event information indicating conversion of a state that matches a generation condition excluding a part of the generation conditions in a holding unit;
When the number of pieces of event information held by the holding unit reaches a predetermined number , the image forming apparatus executes an output procedure for outputting the event information,
The output procedure outputs event information that matches the part of the generation conditions immediately according to the generation by the generation procedure ,
The partial generation conditions include that the application program has stopped and that an error has occurred with respect to the application program.
Management method.   5. The management according to claim 4, wherein the output procedure selects an output destination of the event information with reference to a second storage unit that stores information indicating an output destination of the event information according to contents of the event information. Method.   The monitoring procedure compares the first setting information related to the application program and the second setting information related to the image forming apparatus, and determines a mismatch between the combination of the first setting information and the second setting information. The management method according to claim 4 or 5 to be detected. A monitoring procedure for monitoring the state of the application program based on a list of installed application programs and detecting a change in the state;
A generation determination procedure for determining whether the detected change in the state matches a generation condition of event information stored in the first storage unit;
In the generation determination procedure, when it is determined that the state change matches the generation condition, a generation procedure for generating event information indicating the state change;
Among the event information generated by the generation procedure, a holding procedure for holding event information indicating conversion of a state that matches a generation condition excluding a part of the generation conditions in a holding unit;
When the number of event information items held by the holding unit reaches a predetermined number , the image forming apparatus executes an output procedure for outputting the event information,
The output procedure outputs event information that matches the part of the generation conditions immediately according to the generation by the generation procedure ,
The partial generation conditions include that the application program has stopped and that an error has occurred with respect to the application program.
Management program.   The management according to claim 7, wherein the output procedure selects an output destination of the event information with reference to a second storage unit that stores information indicating an output destination of the event information according to a content of the event information. program.   The monitoring procedure compares the first setting information related to the application program and the second setting information related to the image forming apparatus, and determines a mismatch between the combination of the first setting information and the second setting information. The management program according to claim 7 or 8 to be detected.   A computer-readable recording medium on which the management program according to any one of claims 7 to 9 is recorded.

Images