Source: http://www.google.com/patents/US20010029529?dq=7,468,661
Timestamp: 2014-07-23 08:53:57
Document Index: 321125348

Matched Legal Cases: ['art 11', 'art 12', 'art 15', 'art 21', 'art 31', 'art 34', 'art 35', 'art 44', 'art 11', 'art 12', 'art 15', 'art 15', 'art 21', 'art 31', 'art 34', 'art 35', 'art 44', 'art 13', 'art 14', 'art 15', 'art 16', 'art 17', 'art 18', 'art 21', 'art 31', 'art 32', 'art 34', 'art 35', 'art 36', 'art 37', 'art 38', 'art 39', 'art 44', 'art 45', 'art 15', 'art 13', 'art 16', 'art 21', 'art 31', 'art 34', 'art 35', 'art 16', 'art 14', 'art 15', 'art 15', 'art 21', 'art 31', 'art 34', 'art 35', 'art 37', 'art 38', 'art 45', 'art 37', 'art 37', 'art 37', 'art 37', 'art 17', 'art 21', 'art 21', 'art 18', 'art 13', 'art 15', 'art 15', 'art 18', 'art 15', 'art 31', 'art 34', 'art 35', 'art 16', 'art 32', 'art 17', 'art 18', 'art 39', 'art 15', 'art 16', 'art 19', 'art 20', 'art 21', 'art 22', 'art 31', 'art 33', 'art 34', 'art 35', 'art 40', 'art 41', 'art 43', 'art 46', 'art 46', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 19', 'art 15', 'art 19', 'art 21', 'art 41', 'art 33', 'art 22', 'art 21', 'art 42', 'art 20', 'art 20', 'art 15', 'art 43', 'art 15', 'art 16', 'art 21', 'art 22', 'art 23', 'art 24', 'art 25', 'art 26', 'art 27', 'art 31', 'art 33', 'art 34', 'art 35', 'art 40', 'art 46', 'art 47', 'art 15', 'art 46', 'art 40', 'art 25', 'art 26', 'art 23', 'art 33', 'art 27', 'art 15', 'art 25', 'art 21', 'art 25', 'art 27', 'art 24', 'art 23', 'art 33', 'art 27']

Patent US20010029529 - Remote maintenance apparatus, terminal connected to the apparatus and ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign in<nobr>Advanced Patent Search</nobr>PatentsA remote maintenance apparatus is provided. The remote maintenance apparatus includes: a first obtaining part which obtains configuration information of terminals sent from the terminals; a storing part which stores the configuration information while bringing the configuration information into correspondence...http://www.google.com/patents/US20010029529?utm_source=gb-gplus-sharePatent US20010029529 - Remote maintenance apparatus, terminal connected to the apparatus and computer readable medium for realizing the apparatus and the terminalAdvanced Patent SearchPublication numberUS20010029529 A1Publication typeApplicationApplication numberUS 09/813,962Publication dateOct 11, 2001Filing dateMar 22, 2001Priority dateMar 31, 2000Also published asUS7343401Publication number09813962, 813962, US 2001/0029529 A1, US 2001/029529 A1, US 20010029529 A1, US 20010029529A1, US 2001029529 A1, US 2001029529A1, US-A1-20010029529, US-A1-2001029529, US2001/0029529A1, US2001/029529A1, US20010029529 A1, US20010029529A1, US2001029529 A1, US2001029529A1InventorsIkuko Tachibana, Akira Ohtsuka, Hideki Ise, Kazuhiro Matsushita, Hideki Yoshida, Kazuhiko ItohOriginal AssigneeIkuko Tachibana, Akira Ohtsuka, Hideki Ise, Kazuhiro Matsushita, Hideki Yoshida, Kazuhiko ItohExport CitationBiBTeX, EndNote, RefManReferenced by (9), Classifications (11), Legal Events (4) External Links: USPTO, USPTO Assignment, EspacenetRemote maintenance apparatus, terminal connected to the apparatus and computer readable medium for realizing the apparatus and the terminalUS 20010029529 A1Abstract A remote maintenance apparatus is provided. The remote maintenance apparatus includes: a first obtaining part which obtains configuration information of terminals sent from the terminals; a storing part which stores the configuration information while bringing the configuration information into correspondence with generation information; a second obtaining part which obtains configuration information of a failed terminal; and an extraction part which extracts difference information between configuration information obtained by the second obtaining part and configuration information stored in the storing part which has older generation. Images(18) Claims(17)
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0043] In the following, the principle of the present invention will be described. [0044] The remote maintenance apparatus (which will be called a maintenance server in embodiments) includes: a first obtaining part which obtains configuration information of terminals sent from the terminals; a storing part which stores the configuration information obtained by the first obtaining part while bringing the configuration information into correspondence with generation information; a second obtaining part which obtains configuration information of a failed terminal which is associated with failure information which is sent from the failed terminal, or, which obtains configuration information of the failed terminal by identifying the newest configuration information of the failed terminal which is stored in the storing part; and an extraction part which extracts difference information between configuration information obtained by the second obtaining part and configuration information stored in the storing part. [0045] In this configuration, the remote maintenance apparatus may have an issuing part which issues, to a terminal, an instruction for the terminal to send configuration information when a configuration information ID sent from the terminal is not the same as the newest configuration information ID which is stored in the storing part. [0046] In addition, the remote maintenance apparatus may include a collection part which collects start date and time information, and, end date and time information of maintenance work performed in terminals, and a generation part which generates evaluation information of maintenance work from the date and time information collected by the collection part. [0047] In the above-mentioned remote maintenance server, the first obtaining part obtains configuration information associated with user information sent from the terminal, and obtains changed configuration information when a configuration of the terminal is changed, and stores the configuration information in the storing part. In addition, the obtaining part obtains configuration information sent in response to the instruction issued by the issuing part and stores the configuration information in the storing part. [0048] According to the process of the first obtaining part, the storing part stores the configuration information of each terminal while bringing it into correspondence with generation information. [0049] In response to this, the second obtaining part obtains configuration information of a failed terminal which is associated with failure information which is sent from the failed terminal, or, obtains configuration information of the failed terminal by identifying the newest configuration information of the failed terminal which is stored in the storing part. Then, the extraction part extracts difference information between configuration information obtained by the second obtaining part and configuration information stored in the storing part which has older generation. [0050] In addition, the remote maintenance apparatus may configured in the following way. [0051] The remote maintenance apparatus includes: an obtaining part which obtains configuration information of terminals sent from the terminals; a storing part which stores the newest configuration information of each terminal obtained by the obtaining part; a generation part which identifies terminals to which resources are distributed on the basis of the resources and configuration information stored in the storing part, and generates a list describing correspondence between the resources and the terminals to which the resources are distributed; and a distribution part which distributes the resources described in the list to the terminals described in the list. [0052] In this configuration, the storing part stores newest configuration information according to the processes of the obtaining part. Then, the generation part identifies terminals to which resources are distributed on the basis of the resources and configuration information stored in the storing part, and generates a list describing correspondence between the resources and the terminals to which the resources are distributed. [0053] Then, the distribution part sends a part pertinent to a terminal in the list to the terminal. When the terminal sends a distribution request of resources in response to this, the distribution part distributes the resources. In addition, when resources are requested by a terminal, the distribution part identifies the resources which should be sent to the terminal by searching the list and distributes the resources. [0054] Accordingly, when new resources to be distributed are generated, the remote maintenance server identifies terminals to which the resources are distributed according to configuration information of the terminals, then, distributes the resources to the terminal. Thus, the resources which should be distributed to each terminal can be distributed speedily. [0055] A terminal which is connected to the remote maintenance apparatus via a network includes: an input part which inputs user information; a collection part which collects apparatus information of the terminal and configuration information of the terminal when the input part inputs the user information; and a send part which sends the apparatus information and the configuration information, and the user information to the remote maintenance apparatus while maintaining correspondences of the apparatus information, the configuration information and the user information. [0056] In this configuration, the terminal may include a detection part which detects start and end of maintenance work or detects start date and time information and end date and time information of maintenance work; and a notification part which notifies the remote maintenance apparatus of information detected by the detection part. [0057] In this configuration, the collection part collects changed configuration information when a configuration of the terminal is changed, and the send part sends said changed configuration information to the remote maintenance apparatus while bringing the configuration information into correspondence with the apparatus information. In addition, the collection part collects configuration information when a configuration information ID stored in the terminal is not the same as a configuration information ID stored in the remote maintenance apparatus, and the send part sends the configuration information collected at this time to the remote maintenance apparatus while bringing the configuration information into correspondence with the apparatus information. [0058] Accordingly, when the user information is registered in the remote maintenance apparatus, the terminal collects configuration information and sends it to the remote maintenance apparatus. After that, the terminal collects configuration information and sends it to the remote maintenance apparatus every time when the configuration is changed. Thus, the remote maintenance apparatus can manage the newest configuration information of the terminal and can perform generation management of the configuration information of the terminal. Therefore, a maintenance worker can obtain configuration information at the time of failure and before the failure accurately and easily. [0059] The terminal can be also configured in the following way. [0060] The terminal may include: an obtaining part which obtains resources distributed from the remote maintenance apparatus; a setting part which sets the resources in an application waiting state or in an immediate execution state; a control part which executes the resources when conditions for releasing the application waiting state is satisfied or when the resources are set in the immediate execution state. [0061] In this configuration, the terminal may includes: an obtaining part which obtains information on the resources from the remote maintenance apparatus; a judging part which judges whether resources in the application waiting state is unnecessary or not according to the information obtained by the obtaining part; and a release part which releases the application waiting state of the resources when the judging part judges that the resources are unnecessary. [0062] In this configuration, the setting part sets the resources in an application waiting state or in an immediate execution state. When the obtaining part obtains the resources from the remote maintenance apparatus, the control part sets the resources in the application waiting state if the setting part sets the resources in the application waiting state, and, executes the resources when conditions for releasing the application waiting state is satisfied or when the resources are set in the immediate execution state by the setting part. [0063] Then, the release part releases the application waiting state of the resources when the judging part judges that the resources are unnecessary according to the information on distribution resources obtained by the obtaining part. [0064] Accordingly, the terminal sets the resources in an application waiting state or in an immediate execution state. According to the setting, the terminal sets the resources in the application waiting state and executes the resources when conditions for releasing the application waiting state is satisfied or when the resources are in immediate execution state. Therefore, a request of a user who wants to execute the newly distributed resources from a time can be met. [0065] In the following, the present invention will be described in detail according to following embodiments. [0066]FIG. 1 shows an embodiment of the present invention relating to user registration. As shown in this figure, a system of the present invention includes at least one terminal 10 which is connected to a network 80 and at least one maintenance server 30. [0067] As shown in this figure, the terminal 10 includes a user registration part 11, an information input part 12, an information collection part 15, a send part 21 and apparatus information 300. The maintenance server 30 includes a receive part 31, an information storing part 34, a generation management part 35 and a display part 44. Specifically speaking, functions of the terminal 10 and functions of the maintenance server 30 are realized by programs. The programs can be stored in a computer readable recording medium such as a semiconductor memory. [0068] According to a process flowchart shown in FIG. 2, a user registration process performed in this system of the present invention will be described. [0069] When a user buys the terminal 10, the user launches the user registration part 11 of the terminal 10 in response to a registration request of user information. Then, the terminal 10 displays an input screen for user information shown in FIG. 3. After that, the terminal 10 obtains the user registration information 200 necessary for user registration by receiving input data for the input screen by using the information input part 12. [0070] Next, in synchronization with this process, the information collection part 15 is launched so that the information collection part 15 collects the apparatus information 300 for identifying the terminal 10 which is burn into ROM and the like, and the configuration information 400 of hardware and software which are implemented in the terminal 10. [0071] The apparatus information is configured by an apparatus ID and an apparatus series name and the like for example as shown in FIG. 4A. The configuration information 400 includes information on hardware and software implemented in the terminal 10 as shown in FIG. 4B for example. That is, these apparatus information and configuration information are collected. [0072] Next, the terminal 10 sends the user registration information 200 which is received, and the apparatus information 300 and the configuration information 400 which are collected to the maintenance server 30 via the network 80 by using the send part 21 while keeping correspondence between them. [0073] In response to the process of the terminal 10, the maintenance server 30 receives the user registration information 200, the apparatus information 300 and the configuration information 400 which are sent from the terminal 10 by using the receive part 31. Then, the maintenance server 30 stores the user registration information 200 and the configuration information 400 by using the apparatus information 300 as a key by using the information storing part 34 while allocating generation information by using the generation management part 35. [0074] In this way, according to the present invention, the maintenance server 30 obtains the configuration information 400 of the terminal 10 at the time when the user gets the terminal 10 by collecting the configuration information 400 in synchronization with registration of user information. [0075] Accordingly, when the user wants to connect an add-on RAID hard disk drive (HDD) after registration of user information and the user makes an inquiry about the add-on of the HDD to a support center, an operator of the support center can recommend available hard disk drives speedily and appropriately by displaying the configuration information 400 of the terminal 10 of the user by using the display part 44 of the maintenance server 30. [0076]FIG. 5 shows an embodiment on maintenance according to the present invention. In the figure, the same reference numerals are used to identify features corresponding to those in FIG. 1. [0077] As shown in this figure, the terminal 10 includes a schedule part 13, an abnormal event monitoring part 14, an information collection part 15, a configuration change checking part 16, a maintenance start notification part 17, maintenance end notification part 18, the send part 21 and the apparatus information 300. [0078] The maintenance server 30, as shown in this figure, includes a receive part 31, a result notification part 32, an information storing part 34, the generation management part 35, a configuration change checking part 36, a failure analyzing part 37, a change part indicating part 38, a maintenance time compilation part 39, a display part 44, a maintenance worker notification part 45, the apparatus information 300 and the configuration information 400 which are registered by the configuration as shown in FIG. 1. [0079] Specifically speaking, functions of the terminal 10 and functions of the maintenance server 30 are realized by programs. The programs can be stored in a computer readable recording medium such as a semiconductor memory. [0080] First, processes of the present invention will be described according to a flowchart shown in FIG. 6. [0081] There is a case in which the configuration of the terminal 10 is changed, for example, due to installing an additional hard disk drive in the terminal 10 according to the embodiment shown in FIG. 1. Taking it into account, the terminal 10 launches the information collection part 15 according to the schedule part 13 after a lapse of a time since the system is launched (or immediately, or periodically). Thus, the terminal 10 collects the apparatus information 300 for identifying the terminal 10 and configuration information of hardware and software at the time (the configuration information 410, for example). [0082] Next, the configuration change checking part 16 is launched and the terminal 10 determines whether the configuration information is changed. When the terminal 10 determines that the configuration information is changed, new configuration information (for example, configuration information 410) is set as current configuration information. Then, the terminal 10 launches the send part 21 to send the collected apparatus information 300 and the new configuration information to the maintenance server 30 via the network 80 while bringing the collected apparatus information 300 into correspondence with the new configuration information. [0083] In response to the process of the terminal 10, the maintenance server 30 receives the apparatus information 300 and the configuration information (the configuration information 410 for example) which are sent from the terminal 10 by using the receive part 31. Then, the maintenance server 30 stores the apparatus information 300 and the configuration information 400 (the configuration information 410 for example) by using the apparatus information 300 as a key with the information storing part 34 while allocating generation information by using the generation management part 35. [0084] If this process is performed every time when the system is launched, new configuration information at the time of configuration change can be sent to the maintenance server 30 even when the configuration is changed after powering off the terminal 10. In addition, when the configuration is changed without powering off, if the change of the configuration can be detected, new configuration information can be sent to the maintenance server 30 at the time of configuration change by performing the above-mentioned process when the configuration is changed. [0085] However, in reality, there is a case in which a maintenance worker launches the system multiple times when additional hardware is installed or software is revised. For example, after the maintenance worker installs additional hardware into an erroneous portion and launches the system, the maintenance worker finds the error and changes the portion for installing the hardware, and, then, the maintenance worker launches the system. In addition, when a plurality of additional hardware components are installed, the system is launched multiple times. Thus, it is desirable that the process of collecting the configuration information and sending it to the maintenance server 30 is performed after a lapse of a time. [0086] Accordingly, new configuration information 410 is obtained according to the embodiment shown in FIG. 1, for example, when an additional hard disk drive of the terminal 10 is installed. Then, it is detected, by the configuration change checking part 16, that the hard disk drive is installed by comparing the new configuration information with the configuration information 400 which is obtained before the hard disk drive is installed. Accordingly, the apparatus information 300 and the new configuration information 410 is sent to the maintenance server 30. [0087] In addition, when new configuration information is obtained due to adding software, deleting software, changing versions or the like, the apparatus information 300 and the new configuration information 410 are sent to the maintenance server 30. [0088] Then, the maintenance server 30 manages, by generation, the configuration information sent from the terminal 10 by using the apparatus information 300 as a key as shown in FIG. 7. [0089] In the following, a process performed when a trouble occurs in the terminal will be described with reference to a process flowchart shown in FIG. 8. [0090] When failure, such as failure of the HDD, occurs in the terminal 10, the abnormal event monitoring part 14 detects the failure so that the terminal 10 launches the information collection part 15. Then, the information collection part 15 collects the apparatus information 300 for identifying the terminal 10, configuration information (for example, configuration information 420) of hardware and software at the time when the failure occurred, and failure information 500. [0091] Next, the terminal sends the apparatus information 300, the configuration information at the time of the failure (for example, the configuration information 420) and the failure information 500 to the maintenance server 30 via the network 80 by using the send part 21 while maintaining correspondence between them. [0092] In response to this process of the terminal 10, the maintenance server 30 receives the apparatus information 300, the configuration information (for example, the configuration information 420) and the failure information 500 from the terminal 10 by using the receive part 31. Then, the information storing part 34 in the maintenance server stores the apparatus information 300, the configuration information (for example, the configuration information 420) and the failure information 500 by using the apparatus information as a key while allocating generation information by using the generation management part 35. [0093] Next, the maintenance server 30 analyzes the received failure information so as to analyze a cause of the failure (DEAD) of the HDD for example by using the failure analyzing part 37. In addition, the maintenance server 30 analyzes the configuration information at the time of the failure (for example, configuration information 420) by using the a change part indicating part 38 so that a part at which the HDD to be changed should be installed is indicated. Then, the maintenance server launches the maintenance worker notification part 45 so as to notify a maintenance worker of the indicated part. [0094] Accordingly, the maintenance server 30 obtains the configuration information of the terminal 30 at the time of occurrence of the failure according to which information the maintenance server 30 performs a failure analyzing process. [0095] As described above as shown in FIG. 8, the terminal 10 collects the configuration information at the time of occurrence of the failure and sends it to the maintenance server 10. However, as is understood from description mentioned before, since the maintenance sever 30 continuously keeps track of newest configuration information of the terminal 10, the process of sending the configuration information at the time of occurrence of the failure can be omitted. [0096] The failure analyzing part 37 performs centralized management of failure information sent from the terminal 10. When a search request of failure information is issued by an operator who operates the maintenance server 30 by specifying an apparatus ID, failure occurrence date and time or the like, the failure analyzing part 37 searches failure information for information which satisfies the request. Then, a list of the searched information is displayed. When specific failure information is selected from the list, detailed information (dump data and the like) on the failure information is displayed. [0097] In addition, the failure analyzing part 37 extracts difference information between configuration information at the time of occurrence of the failure and newest configuration information (configuration information one generation before) which has been collected before the occurrence of the failure. The failure analyzing part 37 shows the difference information to the operator so as to aid the operator to analyze the failure. In addition, it is possible, according to instruction of the operator, that difference information between configuration information at the time of occurrence of the failure and configuration information collected earlier than the configuration information one generation before. [0098] That is, as shown in FIG. 9, configuration information which is common to both of configuration information at the time of occurrence of the failure and configuration information before the failure is displayed with green for example as shown by {circle over (1)} in the figure. Configuration information which is described only in the configuration information before occurrence of the failure is displayed with blue for example as shown by {circle over (2)} in the figure. Configuration information which is described only in the configuration information at the time of occurrence of the failure is displayed with red for example as shown by {circle over (3)} in the figure. Accordingly, the above-mentioned difference information can be displayed to the operator. [0099] A combination of software programs or a combination of hardware and software programs often becomes a cause of a failure of hardware or software of the terminal 10. Thus, by displaying the difference information, a maintenance worker can find a cause of a failure easily. [0100] Receiving a dispatch instruction from the maintenance server 30, the maintenance worker goes to the terminal 10 where the failure occurs to repair it. At this time, the terminal 10 displays a control menu shown in FIG. 10. The maintenance worker starts to perform maintenance work by clicking �maintenance work start button� (not shown in FIG. 10) provided in the control menu. [0101] By clicking the maintenance work start button, the maintenance start notification part 17 obtains date and time information (time information) of the start of the maintenance work. Then, the send part 21 sends the date and time information (time information) of the start of the maintenance work to the maintenance server 30. In this process, the send part 21 may sends only information which indicates that the maintenance work starts since date and time information can be obtained by the maintenance server 30. The above process can be applied to date and time information of the end of the maintenance work. [0102] Then, the maintenance worker performs maintenance work such as changing a hard disk drive. When the maintenance work is finished, the maintenance worker clicks �maintenance work end button� which is provided in the control menu shown in FIG. 10. [0103] By clicking the maintenance work end button, the maintenance end notification part 18 obtains date and time information (time information) of the end of the maintenance work. In addition, when the maintenance work finished, the schedule part 13 launches the information collection part 15. [0104]FIG. 11 shows a flowchart of a process which is performed subsequent to the above-mentioned process. [0105] When the maintenance worker finished the maintenance work, the terminal 10 launches the information collection part 15 so as to collect the apparatus information 300 for identifying the terminal 10 and configuration information (configuration information 430 for example) of software programs and hardware after the end of the maintenance work. [0106] Next, the terminal sends the date and time information on the end of the maintenance work which is obtained by the maintenance end notification part 18 and the apparatus information 300/configuration information (configuration information 430 for example) which are collected by the information collection part 15 to the maintenance server 30 via the network 80. [0107] After that, the maintenance server 30 receives the apparatus information 300/the configuration information (configuration information 430 for example) which are sent from the terminal 10 by using the receive part 31. Then, the maintenance server 30, by using the information storing part 34, stores the apparatus information 300/the configuration information (configuration information 430 for example) by using the apparatus information as a key while allocating generation information by using the generation management part 35. [0108] Next, the maintenance server 30 compares configuration information (the configuration information 420 for example) at the time of occurrence of the failure and the configuration information (the configuration information 430 for example) at the time when the maintenance work ends by using the configuration change checking part 16 so that the maintenance server obtains difference information. Then, the maintenance server 30 checks the difference information against the failure information 500 which indicates causes of the failure so that the maintenance server 30 checks, for example, whether the hard disk drive is properly changed. After that, the maintenance server 30 notifies the maintenance worker of the result of the checking by using the result notification part 32. [0109] In addition, when the maintenance server 30 receives the date and time information of the start of the maintenance work which is sent from the maintenance start notification part 17 of the terminal 10 and the date and time information of the end of the maintenance work which is sent from the maintenance end notification part 18 of the terminal 10, the maintenance server 30 compiles dispatching time and maintenance work time shown in FIG. 12 for each maintenance worker, each apparatus series and each failure by using the maintenance time compilation part 39 so that the maintenance server 30 generates evaluation information necessary for evaluating problems or efficiency of the maintenance work. In this process, the dispatching time is defined as time from occurrence of a failure until the start of the maintenance work, and the maintenance work time is defined as time from the start of the maintenance work until the end of the maintenance work. [0110] At this time, when a plurality of service companies are used, skill of each company can be evaluated by compiling the dispatching time and the maintenance work time for each company. As mentioned above, according to the present invention, efficient maintenance work against occurrence of failures can be realized. [0111]FIG. 13 shows an embodiment in which software revising work is performed. In FIG. 10, the same reference numerals are used to identify features corresponding to those in FIG. 1 and FIG. 5. [0112] The terminal 10 includes an information collection part 15, a configuration change checking part 16, a periodic connection part 19, a software application part 20, a send part 21, a receive part 22, apparatus information 300, and software programs 600 which are distributed from the maintenance server 30. [0113] The maintenance server 30 includes a receive part 31, a send part 33, an information storing part 34, a generation management part 35, an object list generation part 40, an object list checking part 41, a distribution monitoring part 43, a registration part 46 and software programs to be distributed to the terminal 10. [0114] Specifically speaking, functions of the terminal 10 and functions of the maintenance server 30 are realized by programs. The programs can be stored in a computer readable recording medium such as a semiconductor memory. [0115] For example, when a cause of a failure exists in firmware of the hard disk drive, the firmware is revised for removing the cause of the failure. At this time, firmware should be revised for all terminals which use the same hard disk drive since the same failure may occur in terminals which use the same hard disk drive. [0116] For this purpose, the maintenance server 30 shown in FIG. 13, by using the registration part 46, launches the object list generation part 40 when the maintenance server 30 registers a new software program (including firmware, microprograms, and including those in which version number is revised) so that a correspondence between the new software program and terminals 10 to which the new software program is downloaded is added to the object list 700 for managing destinations for downloading software. [0117] As shown in FIG. 14A, the object list 700 is configured such that the terminals 10 to which software programs are distributed are managed by managing series names of the terminals 10, software program names to be distributed to the terminals 10 and versions of the software programs. [0118] As mentioned above, the maintenance server 30 is configured so as to perform generation management of configuration information of each terminal 10. In the configuration information in which the generation is managed, configuration information IDs (which are notified by the terminals 10) are managed for the newest configuration information. However, configuration information other than the newest configuration information also can be managed by using the configuration information ID. [0119] That is, the maintenance server 30 is configured to manage, for every terminal 10, series names of the terminals 10, IDs of the newest configuration information and the configuration information (software programs/software program versions/implementation positions) by using apparatus information as a key as shown in FIG. 14B. [0120] Accordingly, when a new software program (which has attribute information which includes series name of the terminal to which the new software program is applied, software program name, and software version) is registered from design departments and the like, the object list generation part 40 searches a file shown in FIG. 14B for a terminals 10 which have the series name to which the registered software program is applied. Then, the object list generation part 40 searches the searched terminals 10 in the file shown in FIG. 14B for terminals 10 having the newly registered software program. In addition, the object list generation part 40 searches the searched terminals 10 in the file shown in FIG. 14B for terminals 10 which have older version software than the version of the newly registered software. Then, relationship between the searched terminals 10 and the series name/software program name/software version of the newly registered software program is added to the object list 700 shown in FIG. 14A. [0121] When a notification of software change (notification of change of configuration information) is sent from a terminal 10, if a software program (having the same software program name/series name) managed by the maintenance server 30 is newer that the notified software program, the object list generation part 40 adds relationship between ID of the terminal 10 which sent the notification and the series name/software program name/software version of the new software to the object list 700 in order to download the new software program to the terminal 10. [0122] When the object list generation part 40 downloaded the software program according to the object list 700, the object list generation part 40 deletes the corresponding record from the object list 700. [0123]FIG. 15 shows a flowchart of processes performed in this embodiment. [0124] The terminal 10 connects to the maintenance server 30 by using the periodic connection part 19 at predetermined time and collects the apparatus information 300 for identifying the terminal 10 by using the information collection part 15. [0125] As for the periodic connection part 19, the connection period is set by interacting with the user on setting screen shown in FIG. 16. Next, the terminal 10 sends the collected apparatus information 300 to the maintenance server 300 via the network 80 by using the send part 21. [0126] When receiving the apparatus information, the maintenance server 30 checks whether the received apparatus information has been registered in the object list 700 (shown in FIG. 14A) by using the object list checking part 41. When the apparatus information has been registered, it is necessary to distribute the registered software program 600 which is indicated by the apparatus information. Thus, the maintenance server 30 sends the registered software program 600 to the terminal 10 which sent the apparatus information by using the send part 33. [0127] Then, the terminal 10 receives the software program 600 sent from the maintenance server 30 by using the receive part 22. Next, the terminal 10 sends a receive result to the maintenance server 30 by using the send part 21. The maintenance server 30 stores distribution state of the software program 600 by using a distribution monitoring part 42. [0128] The software program 600 which is downloaded in the terminal 10 like the above-mentioned way is applied in the terminal 10 by the software application part 20 according to a timing specified by the user by using a setting screen shown in FIG. 17, wherein a timing such as apply immediately, apply when the system is launched on Monday or the like can be selected. Then, the software program 600 enters in an execution state. [0129] Although it is assumed that same timing is set to every received software program as for the setting screen shown in FIG. 17, the screen may be configured such that various timings can be set according to types of the software programs and the like. [0130] After the software program is applied to the terminal 10 by the software application part 20, the terminal 10 collects the apparatus information 300 for identifying the terminal 10 and configuration information of hardware and software after maintenance process by using the information collection part 15. Then, the terminal 10 sends the application result, the apparatus information 300 and the configuration information to the maintenance server 30 via the network 80. After receiving these information, the maintenance server 30 stores the application state of the software program by using the application monitoring part 43. [0131] According to the present invention, the software program 600 in which the version is upgraded can be distributed to the terminal 10 efficiently. Although distribution of the software program 600 is performed when the terminal 10 connects to the maintenance server 30, the software program 600 can also be distributed when the maintenance server 30 connects to the terminal 10. [0132] The software programs are distributed by the above-mentioned way. For example, when the maintenance server 30 distributes the software program before the terminal 10 collects and sends configuration information due to change of hardware configuration, the distributed software program may be not necessary or should not be used in some cases for the reason that configuration information stored in the maintenance server 30 which was used for judgment of distribution is different from configuration information of the terminal 10. [0133] Therefore, in the present invention, the maintenance-server 30 checks whether configuration information of the terminal 10 and the newest configuration information stored in the maintenance server 30 is the same by using the configuration information ID stored in the terminal 10, the newest configuration information ID stored in the maintenance server 30 and the object list 700 (shown in FIG. 14A) which describes software list to be distributed. After that, the maintenance server 30 distributes only necessary software program. In addition, when distribution of a software program waiting to be applied by the terminal 10 is stopped by the maintenance server 30 due to version up of the software program, the waiting state is released. [0134]FIG. 18 shows an embodiment of the present invention for realizing the process. In FIG. 18, the same reference numerals are used to identify features corresponding to those in FIG. 1, FIG. 5 and FIG. 13. [0135] As shown in the figure, the terminal 10 includes an information collection part 15, a configuration change checking part 16, a send part 21, a receive part 22, a software distribution request part 23, a software delete part 24, a configuration information ID checking part 25, a software list checking part 26, a software application waiting part 27 and apparatus information 300. [0136] The maintenance server 30 includes a receive part 31, a send part 33, an information storing part 34, a generation management part 35, an object list generation part 40, a registration part 46 and a distribution stop part 47. [0137] Specifically speaking, functions of the terminal 10 and functions of the maintenance server 30 are realized by programs. The programs can be stored in a computer readable recording medium such as a semiconductor memory. [0138] According to this embodiment, when the information collection part 15 collects configuration information, the terminal 10 generates a configuration information ID (information including timestamps, versions and the like) which becomes control information of configuration information 400. Then, the terminal 10 updates the newest configuration information ID which is stored and sends the configuration information 400 to the maintenance server 30 via the network 80 with the configuration information ID while keeping correspondence between the configuration information 400 and the apparatus information 300. The maintenance server 30 receives it and stores the configuration information to which the configuration information ID is assigned. [0139] When the new software program 600 in which the version is updated is registered by the registration part 46, as mentioned above, the maintenance server 30 generates the object list 700 which manages destinations of download of the software program by using the object list generation part 40. In order to realize this embodiment, the maintenance server 30 sends, to each terminal 10, pertinent parts (parts relating to the terminals 10 to which the software program is to be sent) of the object list 700 and a configuration information ID 800 of configuration information which is source information on which the pertinent parts of the object list 700 are generated. [0140] When the terminal 10 receives the pertinent parts of the object list 700 and the configuration information ID, the terminal 10 checks whether the stored newest configuration information ID agrees with received configuration information ID by using the configuration information ID checking part 25. When the terminal 10 determines that they are the same, the terminal 10 extracts a software program 600 (which has not been distributed so far) which is not waiting for being applied from software programs which are described in the pertinent part of the received object list by using the software list checking part 26. Then, the terminal 10 requests the distribution of the extracted software program 600 to the maintenance server 30 by using the software distribution request part 23. [0141] Receiving the distribution request, the maintenance server 30 distributes the software program 600 which is requested to the terminal 10 by using the send part 33. [0142] When the terminal receives the software program 600, the terminal 10 sets the software program 600 in an application waiting state according to the timing set from the setting screen shown in FIG. 17 by using the software application waiting part 27. When the timing is set as immediate execution, the software program 600 is applied and executed immediately. When a timing condition for executing the software program 600 is satisfied, the state of the software program 600 is changed from application waiting to execution state. [0143] After that, when configurations of software or hardware is changed in the terminal 10, the terminal 10 creates changed configuration information 410 and the configuration information ID 810 by launching the information collection part 15. [0144] Meanwhile, the maintenance server 30 recreates the object list 700 and sends it to the terminal 10 in such cases when the distribution of the software program is stopped or when a new version software program 610 is newly registered. [0145] In these cases, the changed configuration information 410 and the configuration information ID 810 in the terminal 10 has not been sent to the maintenance server 30, configuration information ID described in the object list 700 which is sent to the terminal 10 is the configuration information ID 800 which was sent before. [0146] Accordingly, when the terminal receives the pertinent part of the object list 700 and the configuration information ID sent from the maintenance server 30, the terminal 10 detects disagreement in configuration information IDs by the configuration information ID checking part 25. [0147] When the terminal detects the disagreement in configuration information IDs, the terminal 10 sends the changed configuration information 410 and the configuration information ID 810 to the maintenance server 30 by using the send part 21 in order to notify the maintenance server that the configuration information is changed. [0148] Then, the maintenance server 30 receives and stores the newest configuration information 410 and the configuration information ID 810 of the terminal 10. Then, the maintenance server 30 recreates the object list 700 according to the new configuration information 410, and, sends the recreated object list 700 and the configuration information ID 810 of the configuration information 410 which is a source for re-creating the object list 700 to the terminal 10. [0149] After the terminal 10 receives the pertinent part of the object list 700 and the configuration information ID 810, then, the terminal 10 determines that the configuration information IDs are the same by configuration information ID checking part 25. [0150] Then, when the terminal 10 recognizes, according to the received object list 700, that the software program 600 which is waiting for being applied is removed from distribution objects due to update to the software program 610, the terminal 10 cancels the application waiting state of the software program 600 by using the software application waiting part 27 or deletes the software program 600 by using the software delete part 24. [0151] Then, the terminal 10 determines, according to the received object list 700, that there is the software program 610 which is not received from the maintenance server 30, and requests distribution of the software 610 to the maintenance server 30 by using the software distribution request part 23. [0152] Receiving the distribution request, the maintenance server 30 distributes the software program 610 which is requested to the terminal 10 by using the send part 33. [0153] When the terminal 10 receives the software program 610, the terminal 10 sets the software program 610 in the application waiting state according to the timing set from the setting screen shown in FIG. 17 by using the software application waiting part 27. [0154] After that, for example, when a case occurs where the software program 610 disappears for some reasons in the terminal 10, the terminal 10 requests distribution of the software program 610 according to the object list 700 sent from the maintenance server 30. Then, the terminal 10 receives the software program 610 sent in response to the request, and sets the software program 610 in application waiting state for applying the disappeared software again. [0155] While a configuration is adopted in which the terminal 10 determined whether the configuration information IDs are the same in this embodiment, a following configuration can also be adopted. That is, the terminal 10 periodically sends, for example, apparatus information and configuration information ID to the maintenance server 30, and, the maintenance server 30 determines whether the configuration information IDs are the same. When the maintenance server 30 detects disagreement, the terminal 10 sends the configuration information to the maintenance server 30. [0156] As mentioned above, according to the present invention, a configuration is realized in which the maintenance server 30 can grasp configuration information of each terminal 10 accurately. [0157] Specifically speaking, this configuration is realized such that, when user information is registered from the terminal 10, the maintenance server 30 obtains configuration information of the initial configuration of the terminal 10. After that, the maintenance server 30 obtains configuration information of the terminal 10 every time the configuration of the terminal 10 is changed. Then, the maintenance server 10 checks whether the configuration information of the terminal 10 is different from that stored in the maintenance server by using the configuration information ID. When, they are different, the maintenance server obtains configuration information of the terminal 10 at the time. [0158] In addition, according to the present invention, by performing generation management of the configuration information of each terminal 10 which is grasped accurately by the maintenance server 30, a configuration in which searching for failure causes can be performed easily is realized. [0159] To realize this configuration, specifically speaking, the maintenance server 30 performs generation management of configuration information obtained from the terminal 10, and extracts difference information between configuration information at the time of failure of the terminal 10 and the generation managed configuration information, and outputs the difference information. [0160] Since there are many cases where failure of hardware or software of the terminal 10 is due to combination of software programs, combination of software and hardware and the like, the search for the cause of failure becomes easy by using the difference information. [0161] In addition, according to the present invention, a configuration is realized in which the maintenance server grasps configuration information of each terminal 10 accurately, and distributes software programs which are changed due to failure and the like efficiently by using the configuration information. [0162] To realize this configuration, specifically speaking, when a new software program is generated, the maintenance server 30 searches for terminals 10 which have a series to which the software program is applied according to configuration information of each terminal 10. Then, the maintenance server 30 searches the searched terminals 10 for terminals 10 which have the software program. After that, the maintenance server 30 searches the searched terminals 10 for terminals 10 which have the older version software program than the software program so that the maintenance server prepares a list of the terminals 10 to which the software program is distributed. [0163] Then, when distribution of a software program is requested by the terminal 10, the maintenance server 30 determines and distributes the software program by searching the list. Or, the maintenance server notifies the terminals 10 of the list, and, when distribution of a software program is requested by the terminals 10 in response to the notification, the maintenance server distributes the software program. [0164] In addition, according to the present invention, a configuration is realized in which software programs can be applied in the way the user wishes. This configuration is realized by the way in which the terminal 10 sets the application waiting state or the immediate execution state for resources distributed from the maintenance server 30. Then, the terminal 10 controls timing of application of the resources distributed from the maintenance server 30 on the basis of the settings. In addition, when a software program which is in the application waiting state becomes unnecessary, the terminal 10 releases the waiting state. [0165] In addition, according to the present invention, a configuration is realized in which skill of each maintenance worker or level of each service company can be evaluated objectively and speedily. [0166] To realize this configuration, the maintenance server 30 collects and compiles date and time information of start and end of maintenance work. [0167] As mentioned above, according to the present invention, the cause of failure of terminals connected to a network can be searched speedily. In addition, according to the present invention, resources to be downloaded can be downloaded speedily to each terminal connected to a network. In addition, according to the present invention, configuration information of terminals at the time of failure and configuration information before the failure can be obtained accurately and easily. In addition, according to the present invention, application of resources can be controlled in the way the user wishes. Further, according to the present invention, skill of each maintenance worker or level of each service company can be evaluated objectively and speedily. [0168] The present invention is not limited to the specifically disclosed embodiments, and variations and modifications may be made without departing from the scope of the invention. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7707278 *Nov 20, 2001Apr 27, 2010University Of SurreyReconfiguration management architectures for mobile communication systemsUS7761794 *Jan 22, 2004Jul 20, 2010Cisco Technology, Inc.Integrated audit and configuration techniquesUS7882180 *Jan 9, 2004Feb 1, 2011Canon Kabushiki KaishaMonitoring apparatus for image forming apparatus, control method executed by the monitoring apparatus, program for implementing the control method, and management apparatus, control method executed by the management apparatus, and program for implementing the control methodUS8024618 *Mar 30, 2007Sep 20, 2011Apple Inc.Multi-client and fabric diagnostics and repairUS20100036942 *Oct 30, 2007Feb 11, 2010Thomson LicensingMethod for indicating a service interruption sourceUS20110225563 *Mar 15, 2011Sep 15, 2011Electronics And Telecommuncations Research InstituteSystem for accessing and sharing user defined contents and method of the sameEP1331570A1 *Jan 18, 2002Jul 30, 2003Hewlett-Packard CompanyData processing system and method for controlling display devicesEP1782250A1 *May 27, 2005May 9, 2007Samsung Electronics Co., Ltd.Management system of monitorWO2005048005A2 *Oct 19, 2004May 26, 2005Ixi Mobile R & D LtdReal time system update in a mobile communication network* Cited by examinerClassifications U.S. Classification709/220, 709/223, 714/E11.173International ClassificationG06F11/273, G06F15/177Cooperative ClassificationG06F11/0709, G06F11/2294, G06F11/0748European ClassificationG06F11/22R, G06F11/07P1L, G06F11/07P1ALegal EventsDateCodeEventDescriptionAug 10, 2011FPAYFee paymentYear of fee payment: 4Aug 5, 2008CCCertificate of correctionJul 13, 2001ASAssignmentOwner name: FUJITSU LIMITED, JAPANFree format text: CORRECTIVE ASSIGNMENT, PREVIOUSLY RECORDED AT REEL 011632 FRAME 0052;ASSIGNORS:TACHIBANA, IKUKO;OHTSUKA, AKIRA;ISE, HIDEKI;AND OTHERS;REEL/FRAME:011779/0043Effective date: 20010315Mar 22, 2001ASAssignmentOwner name: FUJITSU LIMITED, JAPANFree format text: INVALID ASSIGNMENT;ASSIGNORS:TACHIBANA, IKUKO;OHTSUKA, AKIRA;ISE, HIDEKI;AND OTHERS;REEL/FRAME:011632/0052Effective date: 20010315RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google