U.S. patent application number 11/688674 was filed with the patent office on 2007-12-13 for remote monitoring system for quickly dealing with bug.
Invention is credited to Hiroshi HOZUMI.
Application Number | 20070285689 11/688674 |
Document ID | / |
Family ID | 38631306 |
Filed Date | 2007-12-13 |
United States Patent
Application |
20070285689 |
Kind Code |
A1 |
HOZUMI; Hiroshi |
December 13, 2007 |
REMOTE MONITORING SYSTEM FOR QUICKLY DEALING WITH BUG
Abstract
A printing apparatus remote monitoring system includes a center
system that remotely monitors a plurality of printing apparatuses,
and a plurality of monitoring mediation apparatuses that mediate
communications between the plurality of printing apparatuses and
the center system. The center system includes a bug countermeasure
policy storage device that stores software bug information created
in the printing apparatus linking with a bug countermeasure policy.
The software bug information includes type of the printing
apparatus, a version of firmware implemented in the printing
apparatus, and abnormal information possibly caused in combination
between the printing apparatus and the firmware.
Inventors: |
HOZUMI; Hiroshi; (Tokyo,
JP) |
Correspondence
Address: |
OBLON, SPIVAK, MCCLELLAND MAIER & NEUSTADT, P.C.
1940 DUKE STREET
ALEXANDRIA
VA
22314
US
|
Family ID: |
38631306 |
Appl. No.: |
11/688674 |
Filed: |
March 20, 2007 |
Current U.S.
Class: |
358/1.9 |
Current CPC
Class: |
G06F 11/0793 20130101;
G06F 3/1293 20130101; G06F 11/0748 20130101; G06F 11/0733 20130101;
H04N 1/00973 20130101 |
Class at
Publication: |
358/001.9 |
International
Class: |
H04N 1/60 20060101
H04N001/60 |
Foreign Application Data
Date |
Code |
Application Number |
Mar 20, 2006 |
JP |
2006-077676 |
Claims
1: An printing apparatus remote monitoring system, comprising: a
center system configured to remotely monitor at least two printing
apparatuses; and at least two monitoring mediation apparatuses each
configured to mediate communications between the at least two
printing apparatuses and the center system; wherein said center
system includes a bug countermeasure policy storage device
configured to store software bug information created in the
printing apparatus linking with a bug countermeasure policy, said
software bug information including type information of the printing
apparatus, version information of firmware implemented in the
printing apparatus, and abnormal information possibly caused in
combination between the printing apparatus and the firmware, said
bug countermeasure policy including policy to update to firmware
having taken bug countermeasure and collects debug log, said
software bug information and bug countermeasure policy being
updated from a terminal provided at the center system, wherein said
monitoring mediation apparatus obtains type information and
firmware version information of the responsible printing apparatus
from the responsible printing apparatus or an inputting apparatus,
said monitoring mediation apparatus notifying the center system of
the type information and the firmware version information while
requesting the center system for software bug information and bug
countermeasure policy corresponding to the printing apparatus,
wherein said center system extracts software bug information and
bug countermeasure policy in accordance with the type information
and the firmware version information of the printing apparatus upon
receiving the type information and the firmware version information
from the monitoring mediation apparatus, and wherein said
monitoring mediation apparatus includes a storing device, said
monitoring mediation apparatus receiving the software bug
information and bug countermeasure policy from the center system
and stores linkage between the software bug information and the bug
countermeasure policy in the storing device.
2: The printing apparatus remote monitoring system, as claimed in
claim 1, wherein said printing apparatus includes a storing device,
and reads and operates the firmware installed in the storing
device, said printing apparatus transmitting abnormal information
representing abnormality to the mediation apparatus in charge of
the printing apparatus when detecting the abnormality, wherein said
monitoring mediation apparatus retrieves bug countermeasure policy
coincident with the abnormal information included in the firmware
version information, the software information, and the type
information of the printing apparatus in the storing device upon
receiving the abnormality information from the responsible printing
apparatus, and wherein the bug countermeasure policy is executed in
the printing apparatus that has outputted the abnormal
information.
3: The printing apparatus remote monitoring system as claimed in
claim 1, wherein said monitoring mediation apparatus instructs the
responsible printing apparatus that outputs the abnormal
information to update bug countermeasure policy completed firmware
when bug countermeasure policy determined is to update to the
countermeasure completed firmware, or instructs the responsible
printing apparatus to update to debug log collection use firmware
when bug countermeasure policy determined is to update to the debug
log collection use firmware, or pick up debug log from the printing
apparatus using the debug log collection use firmware over a
prescribed time period, and instructs updating of the ordinal
operation use firmware after the prescribed time period has elapsed
when the bug countermeasure policy determined is to collection
debug log for the prescribed time period, and wherein said printing
apparatus updates a current firmware stored in the storage device
to the receipt firmware in accordance with instruction of the
firmware update upon receiving the firmware from the monitoring
mediation apparatus, said printing apparatus executing the updated
firmware, and picking up prescribed debug log when the updated
software requests to pick up debug log, and transmits the debag log
to the monitoring mediation apparatus in charge of the printing
apparatus.
4: The printing apparatus remote monitoring system as claimed in
claim 3, wherein said monitoring mediation apparatus obtains and
stores the debug log from the printing apparatus in a storage, and
reads and transmits the debag log to the center system when a
prescribed unit of the debug log is accumulated.
5: The printing apparatus remote monitoring system as claimed in
any one of claims 3 and 4, wherein prescribed protocol for
collecting debug log from the printing apparatus is included in the
bug countermeasure policy when the bug countermeasure policy is to
collect debug log over a prescribed time period, and wherein said
monitoring mediation apparatus designates the prescribed protocol
included in the bug countermeasure policy to the printing apparatus
when collecting the debug log from the printing apparatus, and
wherein said printing apparatus outputs the debug log in accordance
with the prescribed protocol.
6: Printing apparatus remote monitoring system as claimed in claim
5, wherein said printing apparatus stores positive and negative
setting information for allowing and inhibiting the firmware update
or the debug log collection in the storage device, said printing
apparatus including a monitor interface for changing the settings
via the interface, wherein said printing apparatus notifies the
positive and negative setting information when either the firmware
update or the debug log collection is instructed by the monitoring
mediation apparatus, and wherein the mediation apparatus reads the
contact name of the monitor that has issued the report from the
storage storing the contact name upon receiving the report, said
mediation apparatus urging the printing apparatus to change the
settings and permit the update firmware and the debug log
collection to the contact name.
Description
CROSS REFERENCE TO RELATED APPLICATION
[0001] This application claims priority under 35 USC .sctn.119 to
Japanese Patent Application No. 2006-077676 filed on Mar. 20, 2006,
the entire contents of which are hereby incorporating by
reference.
BACKGROUND OF THE INVENTION
[0002] 1. Field of the Invention
[0003] The present invention relates to a remote printing apparatus
monitoring system, and in particular, to the remote printing
apparatus monitoring system suitable for monitoring printing
apparatuses that operate in accordance with firmware.
[0004] 2. Discussion of the Background Art
[0005] A conventional remote monitoring system for monitoring image
printing apparatuses includes a mediation apparatus between the
image printing apparatus and a remote monitoring center. The
mediation apparatus collects counter log of a number of sheets
printed in the image printing apparatus as a monitoring objective
as well as condition information by means of protocol, such as
HTTPS/SOAP, MIB, etc. (HTTPS=HyperTextTransferProtocolover SSL,
SOAP=Simple Object Access Protocol, MIB=Management Information
Base)
[0006] Otherwise, the mediation apparatus receives a report from
the image printing apparatus and notifies the center of the report
when the printing apparatus causes abnormality, thereby controlling
the printing apparatus monitoring system.
[0007] In such a conventional system, however, a sensor can easily
detect almost all of the reports, such as malfunction of parts the
printing apparatus is caused by potential software bug, etc.
[0008] Further, when abnormality caused in, such a cause is
summarized as software error and is reported. Thus, the abnormality
sometimes is neglected until a serious problem.
[0009] Further, debug log need to be collected to analyze an
abnormal condition of the printing apparatus. Such debug log is
temporarily stored in storage and quickly disappears after a
prescribed time period from the storage. Since debug log is
voluminous and becomes significant if the entire debug log is
continuously collected. In addition, debug log outputted to the
storage is insufficient for analysis depending on a problem.
[0010] Then, a note type PC (personal computer) or similar devices
including a log collection use tool is disposed, upon a contract,
in a customer site that possibly causes a problem.
[0011] The note type PC continuously picks up and stores log in a
HDD (Hard Disk Drive), and is collected after a while. Otherwise,
log output use firmware is temporarily installed in the customer
site to pick up log.
[0012] Further, when firmware capable of resolving a problem is
released, a customer suffering the problem cannot recognize such a
release. Thus, the customer that needs update of the firmware can
be neglected for a longtime.
SUMMARY OF THE PRESENT INVENTION
[0013] Accordingly, an object of the present invention is to
improve such background arts technologies and provides a new and
novel remote monitoring system for quickly dealing with bug.
[0014] Such a new and novel printing apparatus remote monitoring
system includes a center system that remotely monitors a plurality
of printing apparatuses, and a plurality of monitoring mediation
apparatuses that mediate communications between the plurality of
printing apparatuses and the center system.
[0015] The center system includes a bug countermeasure policy
storage device that stores software bug information created in the
printing apparatus linking with a bug countermeasure policy. The
software bug information includes a type of the printing apparatus,
a version of firmware implemented in the printing apparatus, and
abnormal information possibly caused in combination between the
printing apparatus and the firmware.
[0016] The bug countermeasure policy includes a policy to update to
firmware having taken bug countermeasure and collects debug log.
The software bug information and bug counter measure policy are
updated from a terminal provided at the center system. The
monitoring mediation apparatus obtains type information and
firmware version information of the responsible printing apparatus
therefrom or an inputting apparatus. The monitoring mediation
apparatus notifies the center system of the type and the firmware
version while requesting the center system for software bug
information and bug countermeasure policy corresponding to the
printing apparatus.
[0017] The center system extracts software bug information and bug
countermeasure policy in accordance with the type and the firmware
version of the printing apparatus upon receiving the type and the
firmware version from the monitoring mediation apparatus.
[0018] The monitoring mediation apparatus includes a storing device
and the monitoring mediation apparatus receives the software bug
information and bug countermeasure policy from the center system
and stores linkage between the software bug information and the bug
countermeasure policy in the storing device.
BRIEF DESCRIPTION OF DRAWINGS
[0019] A more complete appreciation of the present invention and
many of the attendant advantages thereof will be readily obtained
as the same becomes better understood by reference to the following
detailed description when considered in connection with the
accompanying drawings, wherein:
[0020] FIG. 1 is a block chart illustrating a remote printing
apparatus monitoring system according to one embodiment of the
present invention;
[0021] FIGS. 2A to 2C collectively illustrates an exemplary table
showing combination of software bug information and bug
countermeasure policy stored in a bug countermeasure policy storing
device of FIG. 1;
[0022] FIG. 3 is a flowchart illustrating an exemplary operation of
the remote printing apparatus monitoring system of FIG. 1;
[0023] FIG. 4 is a flowchart illustrating another exemplary
operation of the remote printing apparatus monitoring system of
FIG. 1;
[0024] FIG. 5 is a flowchart illustrating still another exemplary
operation of the remote printing apparatus monitoring system of
FIG. 1; and
[0025] FIG. 6 is a flowchart illustrating yet another exemplary
operation of the remote printing apparatus monitoring system of
FIG. 1.
PREFERRED EMBODIMENTS OF THE PRESENT INVENTION
[0026] Referring now to the drawing, wherein like reference
numerals designate identical or corresponding parts throughout
several views, in particular in FIG. 1, an exemplary remote
printing apparatus monitoring system is described. The remote
printing apparatus monitoring system includes a plurality of image
printing apparatuses 10, a center system 20 that remotely monitors
the image printing apparatuses 10, and a mediation apparatus (i.e.,
a monitoring mediation apparatus) 30 that mediates communications
between a responsible image printing apparatus 10 and the center
system 20. 40 denotes a terminal for a printing apparatus
controller that controls the image printing apparatus 10. The image
printing apparatus 10 and the mediation apparatus 30 are connected
to communicate with each other by LAN (Local Area Network). As a
matter of convenience, one set of the image printing apparatus 10
and the mediation apparatus 30 is described. However, plural sets
are practically employed. Each of the mediation apparatuses 30
communicates with a plurality of responsible image printing
apparatuses 10, while communicating with the center system 20. The
LAN connecting the image printing apparatuses 10 to the mediation
apparatus 30 is further connected to the center system via
Internet.
[0027] The center system 120 includes a bug countermeasure policy
storage device 21 including registration of linkage between
software bug information of the image printing apparatus 10 and a
policy of countermeasure against each of software bugs. The center
system 20 includes a debug log storing device 22 that obtains and
stores debug log picked up in the image printing apparatus 10, a
firmware storage device 23 that stores several kinds of firmware
used by the image printing apparatus 10, and a designer terminal 24
that allows a designer or the like to update the contents of the
bug countermeasure policy storage device 21 and refer to the
contents of the debug log stored in the debug log storage device
22. The designer terminal 24 can be located at everywhere as far as
the designer can operate and browse information stored in the
storage.
[0028] FIGS. 2 and 3 each illustrates the linkage between the
software bug information registered in the bug countermeasure
policy storage device 21 and the bug countermeasure policy.
[0029] The software bug information includes a linkage between a
type of the image printing apparatus 10, a version of software
implemented in the printing apparatus, and abnormal information
possibly occurred in combination of a printing apparatus and
firmware. The type includes a classification of a model, such as
AAAA, etc., and a model number, such as 00000 to 200000, etc., of
the image printing apparatus 10. The firmware version includes a
classification of a number, such as 1.01, etc. The abnormal
information includes a classification of combination of a code,
such as SC001, etc., which represents an abnormal condition, and an
occurrence frequency.
[0030] The abnormal condition includes specified service call,
parse error, and abnormality of collected information or the like.
Further, the occurrence frequency includes quick response to every
occurrence, response when occurred a prescribed times, and response
when continuously occurred for a prescribed time period, or the
like.
[0031] The bug countermeasure policy may include updating to
prescribed bug countermeasure taken firmware, collecting debug log
with a prescribed command, such as rsh (remote shell) command,
etc., and collecting debug log with a prescribed protocol, such as
HTTPS/SOAP, etc.
[0032] The bug countermeasure policy may also include updating to
log collection use special firmware (firmware specialized in a
function of collecting debug log) and then collecting debug log.
Further, when bug countermeasure policy includes collection of
debug log, a collection time period, such as one-month, snap shot,
a week, etc., is registered.
[0033] Further, a debug number may be registered as an identifier
identifying the collected debug log along with another identifier
identifying a contact name, such as designer XXX, etc., to be
notified of the debug log.
[0034] An collection time period for the debug log may be set to
the snap shot, a few hours, a designated date, and soon. To extract
only necessary information among collected log, a plurality of
regular expression can be designated for limiting a number of
logs.
[0035] These software bug information and bug countermeasure policy
may be updated through the designer terminal 24 as needed. The
designer operates the designer terminal 24 to register software bug
information and bug countermeasure policy in a bug countermeasure
policy storing device 21 in accordance with a bug found during
development, evaluation, and implementation of the firmware.
[0036] The designer preferably registers a bug countermeasure
policy in accordance with software bug information based on the
below described determinations.
[0037] First, when bug is already known and bug countermeasure
firmware has been released, updating to the bug countermeasure
firmware is selected as a bug countermeasure policy.
[0038] Second, when bug is already known but is negligible, a bug
countermeasure policy is not registered.
[0039] Third, when bug is already known but is not yet taken a
countermeasure even if a debug log use firmware has been released,
a bug countermeasure policy is to update to debug log collection
use firmware, execute and collect debug log for a prescribed time
period, and returns to ordinary operation use firmware.
[0040] Fourth, when bug is unknown and debug log collection
firmware has been released, a bug countermeasure policy is to
update to debug log collection use firmware, and collect debug log
for a prescribed time period, and then returns to an ordinary
operation use firmware.
[0041] The bug countermeasure policies determined as above are
registered in the bug countermeasure policy storing device 21 while
linking with a model, a model number, a firmware version, an
abnormality condition, and an occurrence frequency.
[0042] Now, an exemplary configuration of an image printing
apparatus 10 is described. The image printing apparatus 10 includes
an abnormality detection reporting device 11 that detects
abnormality during firmware implementation and notifies a mediation
apparatus 30 of a code representing the abnormality. The image
printing apparatus 10 also includes a firmware updating device 12
that receives an instruction from the mediation apparatus 30 and
updates to prescribed firmware in accordance with the instruction
in the firmware storing device 14. The image printing apparatus 10
further includes a debug log storage device 13 that stores debug
logs picked up during implementation of the firmware, and a
firmware storage device 14 that stores firmware read and
implemented when the image printing apparatus 10 starts
operation.
[0043] Further, the storage device 15 stores settings if update of
firmware and collection of debug log are each allowed or not.
[0044] Now, an exemplary configuration of the mediation apparatus
30 is described. The mediation apparatus 30 includes a responsible
printing apparatus information storage device 31 that stores
printing apparatus information related to a plurality of image
printing apparatuses 10 that the mediation apparatus is responsible
for. The responsible printing apparatus information storage device
31 includes registrations of a model, a model number, a firmware
version, and a contact name of a person in charge of a printing
apparatus 10 that the mediation apparatus 30 is responsible
for.
[0045] The mediation apparatus 30 includes a bug countermeasure
policy storage device 32 that extracts and stores only software bug
information and bug countermeasure policies corresponding to the
responsible printing apparatus registered in the responsible
printing apparatus information storage device 31 among those stored
in the bug countermeasure policy storage device 21. Further, the
mediation apparatus 30 includes a debug log storage device 33 that
stores debug log collected from the image printing apparatus
10.
[0046] The above-mentioned image printing apparatus 10, the center
system 20, and the mediation apparatus 30 collectively realizes
various functions and operations and serves as an operation device
when a processing device, such as a processor, etc., executes
program, such as firmware, etc.
[0047] Further, each of the storage devices is arranged in a
storing region of a storing apparatus.
[0048] Further, communications between the printing apparatuses and
the center system are executed via a prescribed communication
apparatus in accordance with communication protocol.
[0049] Now, an exemplary operation of the above-mentioned
configuration is specifically described with reference to FIGS. 4
to 7, wherein an exemplary operation of a printing apparatus remote
monitoring system with the above-mentioned configuration is
illustrated.
[0050] As shown, first to fourth terminals in FIG. 3 are connected
to corresponding parts in FIG. 4, respectively. Eleventh to
fourteenth terminals in FIG. 5 are connected to corresponding parts
in FIG. 6, respectively.
[0051] Initially, an exemplary operation when a mediation apparatus
30 acquires abstract of bug countermeasure policy from a center
system 20 is described with reference to FIGS. 4 and 5.
[0052] When instructed to take care of an image printing apparatus
10 (Model AAAA, Model number 000001), the mediation apparatus 30
acquires model, model number, firmware version information, and
contact name information of a printing apparatus monitor of the
image printing apparatus 10.
[0053] The mediation apparatus 30 links with each other and
registers these information in the responsible printing apparatus
information storage device 31.
[0054] The mediation apparatus 30 notifies the center system 20 of
the registration of the image printing apparatus 10. Upon receiving
the notification, the center system 20 executes information
processing regarding the registration of the image printing
apparatus 10. When the information processing is completed, the
center system 20 notifies the mediation apparatus 30 of the effect
that the information processing related to the registration of the
image printing apparatus 10 is completed (registration Okay). Upon
receiving the notification, the mediation apparatus 30 instructs
the image printing apparatus 10 to change a prescribed registration
parameter, such as an IP address of the responsible mediation
apparatus, etc. When the instruction is received and the
registration parameter has been changed as instructed, the image
printing apparatus 10 receiving the instruction notifies the
mediation apparatus 30 of the effect that registration parameter
has been changed. Upon receiving the notification, the mediation
apparatus 30 notifies the center system 20 of the effect that the
registration parameter has been changed in the image printing
apparatus 10 as notification of registration completion.
[0055] In response to the reception of the registration completion
notification, the center system 20 returns a response to the
mediation apparatus 30.
[0056] Upon receiving the response, the mediation apparatus 30
reads a model, a model number, and firmware version information of
the image printing apparatus 10, registered just before, from the
responsible printing apparatus information storage device 31, and
transmits such information to the center system 20. Then, the
mediation apparatus 30 requests a bug countermeasure policy
corresponding to the image printing apparatus 10 to the center
system 20.
[0057] The center system 20 with the request then extracts software
bug information and a bug countermeasure policy linked to a
combination of a model, a model number, and firmware version
information of the image printing apparatus 10, which are received
from the mediation apparatus 30, from the bug countermeasure policy
storage device 21.
[0058] Then, the center system 20 transmits thus extracted software
bug information and bug countermeasure policy to the mediation
apparatus 30 as a related bug information confirmation
response.
[0059] Upon receiving the software bug information and bug
countermeasure policy from the center system 20, the mediation
apparatus 30 registers linkage of the software bug information and
bug countermeasure policy in the bug countermeasure policy storage
device 32 (Related bug information DB writing). Thus, since the
mediation apparatus 30 only extracts and holds bug countermeasure
policy needed for the responsible image printing apparatus 10,
quantity of information can be reduced.
[0060] Now, an exemplary operation executed when an image printing
apparatus 10 detects abnormal information is described with
reference to FIGS. 6 and 7.
[0061] When abnormality occurs during running of firmware in an
image printing apparatus 10 (e.g. Model AAAA, Model Number 000001),
an abnormality detection reporting device 11 recognizes an abnormal
condition, and reports such an effect to the mediation apparatus 30
with a code (SC001) representing the abnormality. Upon receiving
the report, the mediation apparatus 30 returns a response to the
image printing apparatus 10 as the report sender, and notifies the
center system 20 of the effect that the image printing apparatus 10
assigned the Model AAAA and Model Number 000001 outputs the
abnormality condition SC001.
[0062] Upon receiving the notification, the center system 20
returns a response to the mediation apparatus 30 as the report
sender. The mediation apparatus 30 then notifies the image printing
apparatus 10, which has outputted the report, of the effect that
the reporting to the center system 20 is completed.
[0063] Upon receiving the notification, the image printing
apparatus 10 returns a response to the mediation apparatus 30.
[0064] Upon receiving the response, the mediation apparatus 30
obtains and learns the model, the model number, and the firmware
version information from the responsible printing apparatus
information storage device 21.
[0065] The mediation apparatus then checks if software bug
information formed from a combination of the model, the model
number, the firmware version information, and the code SC001 is
registered in the bug countermeasure policy storage device 32
(i.e., Bug information pattern matching).
[0066] If the software bug information is registered in the bug
countermeasure policy storage device 32 and an occurrence frequency
is suitable to take measure, the mediation apparatus 30 reads bug
countermeasure policy linked with the software bug information from
the bug countermeasure policy storage device 32, and executes bug
countermeasure policy designated there as described below.
[0067] In a first exemplary operation, when the bug countermeasure
policy designates updating to firmware enabling to pick up an
increased number of analysis use debug logs (herein below, referred
to as enriched version firmware), the mediation apparatus requests
the log enriched version firmware to the center system 20.
[0068] Upon receiving the request, the center system 20 reads and
provides the log enriched version firmware from the firmware
storage device 23 to the mediation apparatus 30 as a requester
(i.e., downloading of firmware).
[0069] The mediation apparatus 30 stores the log enriched version
firmware provided by the center system 20 in a storage device, and
transmits the log enriched version firmware to the image printing
apparatus 10 that has outputted the above-mentioned report together
with an instruction to update firmware.
[0070] Upon receiving the log enriched version firmware with the
instruction, the firmware updating device 12 of the image printing
apparatus 10 updates and stores the log enriched version firmware
in the firmware storage device 14.
[0071] The image printing apparatus 10 is then rebooted.
[0072] The image printing apparatus 10 restarts operating by
reading the log enriched version firmware from the firmware storage
device 14, and notifies the mediation apparatus 30 of the effect
that the firmware update is completed (i.e., firmware updated
result notification). Upon receiving the notification, the
mediation apparatus 30 notifies the center system 20 of the effect
that the firmware update is completed in the image printing
apparatus 10 (i.e., log enriched version firmware updated result
notification).
[0073] Upon receiving the notification, the center system 20
returns a response to the mediation apparatus 30.
[0074] Now, the second exemplary operation is described.
[0075] The mediation apparatus 30 requests the image printing
apparatus 10 to acquire debug log when collection of debug log is
designated as a bug countermeasure policy corresponding to the
report of the image printing apparatus 10.
[0076] Thus, the image printing apparatus 10 is requested to
provide the debug log using prescribed protocol defined by the bug
countermeasure policy.
[0077] The image printing apparatus 10 in the course of
implementation of the log enriched version firmware is then
controlled to write volatile debug log per module in a small memory
region serving as a debug log storage device 13 or displayed on a
laboratory use screen.
[0078] When the mediation apparatus 30 requests collection of debug
log, the image printing apparatus 10 reads and transmits debug log
stored in the debug log storage device 13 or outputted onto the
laboratory use screen as needed in accordance with designated
protocol.
[0079] The mediation apparatus 30 stores debug log received from
the image printing apparatus 10 in the debug log storage device 33,
and reads and notifies the debug log to the center system 20 from
the debug log storage device 33 in a unit when an amount of the
storage of the debug log reaches a prescribed level. The center
system 20 confirms a debug log reporting destination registered in
the bug countermeasure policy storage device 21 with reference to
the software bug information of the image printing apparatus 10
that outputs debug log.
[0080] The above-mentioned operation for collecting debug log is
executed over a debug log collection time period defined by bug
countermeasure policy.
[0081] The third exemplary operation is now described.
[0082] Upon detecting elapse of the debug log collection time
period after starting collection of the debug log as defined in the
bug countermeasure policy, the mediation apparatus 30 requests the
center system 20 to provided the newest firmware in accordance with
the model and/or model number of the image printing apparatus
10.
[0083] Upon receiving the request, the center system 20 reads the
newest firmware from the firmware storage device 23 in accordance
with the model and/or model number of the image printing apparatus
10, and transmits the newest to the mediation apparatus 30 as a
requester (Downloading of the newest firmware). The mediation
apparatus 30 stores the newest firmware provided by the center
system 20 in a storage device and transmits the newest to the image
printing apparatus 10 along with an instruction of updating the
firmware.
[0084] Upon receiving the instruction in the image printing
apparatus 10, the firmware updating device 12 updates to and stores
the newest firmware received from the mediation apparatus 30 in the
firmware storage device 14. The image printing apparatus 10 is then
rebooted. The image printing apparatus 10 starts operating by
reading the newest firmware from the firmware storage device 14,
and notifies the mediation apparatus 30 of the effect that the
firmware update is completed (i.e., firmware updated result
notification). The mediation apparatus 30 then notifies the center
system 20 of the effect that the firmware update is completed in
the image printing apparatus 10 (i.e., the newest firmware updated
result notification). The center system 20 then returns a response
to the mediation apparatus 30.
[0085] The newest firmware can be the same as a version of firmware
before being updated to the log enriched version firmware. That is,
the firmware before being updated to the log enriched version
firmware operates again.
[0086] Now, the fourth exemplary operation is described.
[0087] As a result of the above-mentioned bug information pattern
matching, when the bug countermeasure policy corresponding to the
software bug information only represents that firmware is to be
updated to the newest firmware, the above-mentioned third exemplary
operation is executed regardless of the debug log collection time
period.
[0088] When software bug is already known and countermeasure there
against is already taken, such a bug countermeasure policy is
generally adopted.
[0089] Now, the fifth exemplary operation is described.
[0090] As a result of the above-mentioned bug information pattern
matching, when the bug countermeasure policy corresponding to the
software bug information only represents that debug log is to be
collected, the above-mentioned second exemplary operation is
executed. An ordinal operation use firmware other than the log
enriched version firmware sometimes includes a simple debug log
pick up function. In this situation, only collection of debug log
can be a bug countermeasure policy for a model for which log
enriched version firmware has not yet been released.
[0091] The sixth exemplary operation is now described.
[0092] As a result of the above-mentioned bug information pattern
matching, when matching software bug information has not yet been
registered, the mediation apparatus 30 sends a query to the center
system 20 as to if matching software bug information has been
registered at the present moment in the center system 20.
[0093] The center system 20 receiving the query confirms if
software bug information and bug countermeasure policy of the query
have been registered at the present moment in the bug
countermeasure policy storing device 21, and reads and transmits
these software bug information and bug countermeasure policy to the
mediation apparatus 30 if the determination is positive.
[0094] The mediation apparatus 30 having received the transmission
stores these software bug information and bug countermeasure policy
in the bug countermeasure policy storage device 32. Then, the
above-mentioned first to fifth operations are executed in
accordance with the bug countermeasure policy.
[0095] Now, the seventh exemplary operation for rejecting firmware
update or the like is described
[0096] Possibility of firmware update or an operation accompanied
by debug log collection may be set to the image printing apparatus
10. Specifically, a monitor of the image printing apparatus 10 can
set information if the operations are rejected via a monitor
interface provided by the image printing apparatus 10.
[0097] Then, the image printing apparatus 10 stores positive and
negative setting information as to firmware update or the like in a
storage device.
[0098] The image printing apparatus 10 receives the positive and
negative settings via an operation panel of the image printing
apparatus 10 or the monitor interface provided to an external
printing apparatus monitoring terminal 40.
[0099] The image printing apparatus 10 then updates settings in the
storage device in accordance with a change.
[0100] For example, the monitor can set in accordance with security
policy of the respective customers, such as inhibition of update to
the newest firmware, inhibition of updating to the log enriched
version firmware, inhibition of debug log collection, etc.
[0101] Thus, the image printing apparatus 10 reports the effect to
the mediation apparatus 30 that an operation corresponding to a
prescribed request is inhibited when requested from the mediation
apparatus 30.
[0102] Upon receiving the report, the mediation apparatus 30 reads
a contact name of the monitor of the image printing apparatus 10
that has issued the report from a responsible printing apparatus
information storage device 31, and creates and transmits a mail to
sound if such setting can be changed to the contact name. A
currently set inhibition condition, reasons for necessity of
firmware update or debug log collection, and a link, such as URL,
WebUI, etc., for accessing an interface to change the inhibition
setting are automatically inserted into the sounding mail.
[0103] Then, the mediation apparatus 30 monitors canceling of the
inhibition setting in the image printing apparatus 10.
[0104] When the monitor cancels inhibition setting for the firmware
update or the debug log collection, the image printing apparatus 10
reports the effect to the mediation apparatus 30.
[0105] Upon receiving the report, the mediation apparatus 30
restarts execution of bug countermeasure policy, which is
previously scheduled, and executes a prescribed applicable
operation among the above-mentioned first to sixth operations.
[0106] Now, the eighth exemplary operation related to a method for
collecting debug log is described.
[0107] The center system 20 or the designer terminal 24 may request
collection of debug log to the mediation apparatus 30 while
designating the image printing apparatus 10.
[0108] The mediation apparatus 30 then reads and provides debug log
of the designated image printing apparatus 10 from the debug log
storage device 33 to the center system 20 or the designer terminal
24.
* * * * *