JP2007293737A - Method for registering and managing software resource, electronic equipment, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To install an application, while utilizing past experiences concerning application registering processing. <P>SOLUTION: When a registered application is uninstalled, the reason of the uninstallation is recorded in a registration log (S40-S48). In the succeeding registration of the application, whether the same kind of application has been uninstalled previously or not is determined by retrieving the registration log (S80). When previously uninstalled (S80-YES), a user is notified of the deletion reason (S85) and subsequent processing is performed according to user instruction based on the notification (S86). <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a software resource registration management method, an electronic device, and a program. More specifically, it is a registration management method for managing software resources incorporated in an electronic device, and installs (including registration / update) and uninstalls software resources such as application programs, files, etc. on a user's device. The present invention relates to a control mechanism in the case of (deletion).

  Today, with the development of information processing technology, software resources such as application programs, files, etc. are installed and used (including embedded / updated) on devices used by users on various devices, and they meet specified conditions. Uninstallation (deletion) of things and things that are no longer necessary (see, for example, Patent Documents 1 to 6).

Japanese Patent Laid-Open No. 2003-241928 JP-A-2005-044000 JP-A-11-085578 JP 2001-051835 A JP 2001-356912 A JP 2004-127281 A

  For example, in Patent Document 1, an application is installed from a server for a necessary function on a client device, and a billing process related to the use of the application is automatically uninstalled based on a usage time limit or a usage count limit. A mechanism for adjusting the billing process according to the uninstallation is disclosed.

  Patent Document 2 discloses a mechanism for monitoring the usage status of an application on a client device by a server device and automatically uninstalling an application with a low usage frequency based on the usage status. .

  Patent Document 3 discloses a mechanism for setting a deletion condition for each file, monitoring the deletion condition, and automatically uninstalling a file that satisfies the deletion condition.

  Japanese Patent Application Laid-Open No. 2004-228620 determines whether an application module is functioning normally on the target medium, and automatically uninstalls the application module if the application module does not function normally. Is disclosed. For example, if an application has been upgraded to a problematic version, it will be uninstalled automatically.

  As described above, in Patent Documents 1 to 4, some application is installed with a limited period, conditions such as the number of times of use, frequency, and deletion conditions, and the use period expires or meets the set conditions such as the number of times of use and frequency. If a failure occurs due to installation of an application or if a failure occurs due to installation of an application, the application is automatically uninstalled.

  However, as in the mechanisms described in Patent Documents 1 to 4, if software resources such as applications are automatically uninstalled when the uninstall conditions are met, the applications are automatically uninstalled. Sometimes the user could not know why it was uninstalled.

  For this reason, an application that has been automatically uninstalled will be re-executed without knowing the reason for uninstalling it. Automatic uninstallation of Windows happen again. In effect, the installation process is wasted.

  For example, at the next installation, if you set the same time limit and number of use as the previous time and install it again, if the usage period expires or it meets the conditions such as the number of use and frequency, it will be uninstalled again. It will be installed and will be repeated without knowing the same thing, it is not easy to use.

  Also, despite the fact that the application was automatically uninstalled because of upgrading the application to a problematic version, it is impossible to prevent the inconvenience of upgrading to the version that causes the problem again. The version that causes the problem must be uninstalled automatically, and again, the same thing will be repeated without knowing it, which is inconvenient.

  Also, if a failure occurs during the installation process and the installation process is interrupted, if you try to install the same application again, the installation process will be interrupted again because of the same problem. As a result, the installation work is wasted.

  Also, a failure occurred during the installation process, but when you finally completed the installation process while searching for a way to remove the failure, when you tried to upgrade the application, because of the same failure, In the same way, the upgrade process is temporarily interrupted, and in the same way, the upgrade process must be completed while searching again for a method for canceling the failure, and the upgrade process, which is an example of the installation process, is inefficient. There is also a problem.

  Also, in the same vendor's word processor (word processor), spreadsheet, database, presentation, and other related (family) applications, for example, a failure occurred during the process of installing word processing software. In other words, when the installation process is completed, if you try to install another affiliated application (for example, spreadsheet software), the installation process will be temporarily suspended due to the same failure. There is also a problem that the installation process of the affiliated software is not efficient because the installation process must be completed while searching again for the release method.

  On the other hand, for example, in Patent Document 5, by setting an evaluation standard for the status of application registration processing such as installation, update, and uninstallation, it is possible to prevent unexpected processing from being performed in each processing. The mechanism is disclosed. In addition, when the evaluation criterion indicates failure, a mechanism for stopping the subsequent processing and notifying the user of the cause of the failure is also disclosed.

  According to the mechanism described in Patent Document 5, the installation state of each file is evaluated based on the evaluation condition, and if the evaluation result indicates failure in application registration processing (installation, update, uninstallation), Since the processing is stopped and the cause of the failure is notified to the user, there is an advantage that no unnecessary processing is performed on the memory of the user machine.

  However, the notification of the cause of the failure is related only to the application registration process at that time, and the previous failure experience is not utilized in the registration process again. For example, if you try to install an application that has failed to install again under the same conditions, the evaluation result will indicate that the installation has failed, and the subsequent processing will stop and the user will be notified of the same cause of failure again. The experience of the previous failure is never utilized.

  Further, in Patent Document 6, it is determined whether or not an application to be installed can be installed based on application information (version check, resource check, etc.) related to an application used in the apparatus, and the installable application is displayed on the operation panel. There is disclosed a mechanism for displaying and accepting a selection and notifying the user of the reason for the inability to install an application that cannot be installed.

  According to the mechanism described in Patent Document 6, by displaying an installable application on the operation panel, it is possible to prevent an application that cannot be installed from being installed for some reason, and the installation is impossible. By knowing the reason, for example, when installation cannot be performed because a certain device is not mounted on the multifunction device, it is possible to take a countermeasure such as mounting the device.

  However, the notification is related only to the application registration process at that time, similarly to the mechanism described in Patent Document 5, and the previous installation impossible experience is not utilized during the registration process again. For example, if an application that cannot be installed is to be installed again under the same conditions, the user is only notified again that the installation is impossible, and the previous experience of not being installed is not utilized.

  In this way, in the conventional application registration process (installation, update, uninstallation), the actual situation is that the experience of the previous registration process is not utilized at the time of the next registration process. There is a problem that repeated processing must be repeated.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a mechanism that can make use of the experience that has occurred in the process of past application registration during the current registration process.

  In the mechanism according to the present invention, first, when executing registration processing of software resources such as application installation, update, and uninstallation, the registration processing history is associated with the software resources and stored in a predetermined storage medium. Save it.

  For example, information about failures that occurred when installing software resources, how to resolve failures that occurred when registration processing was continued while resolving failures, and reasons for deletion when software resources were deleted are saved as registration history. It is good.

  When the next software resource registration process (especially the installation process) is executed, whether or not the history of the software resource of the same type as the next software resource is stored in the storage medium prior to the installation process. If the history of the same type of software resource as the next software resource is stored in the storage medium, the history information is notified to the user. Then, the subsequent processing related to the registration processing is executed in accordance with the user instruction based on this notification.

  For example, you can continue the installation while referring to the past registration history related to the application you are installing this time, or you can restart the installation after changing the installation or uninstallation conditions. Can be canceled (suspended).

  In other words, when installation processing of an application is requested, the installation processing is not executed immediately, but based on the registration history whether or not the same type of application related to the application to be installed this time has been registered before. When the registration history exists, the user is notified of the registration history information, and the subsequent processing is performed according to the user instruction based on the notification. In short, the registration process is executed with reference to the past registration history related to the application to be installed this time.

  The mechanism according to the present invention can be realized by software using an electronic computer (computer), and a program for this purpose and a recording medium storing this program can also be extracted as an invention. The program may be provided by being stored in a computer-readable storage medium, or may be provided by distribution via wired or wireless communication means.

  According to the present invention, since the registration process is executed with reference to the past registration history related to the application to be installed this time, the registration process can be executed using the past experience.

  For example, by referring to the failure at the time of the previous installation, it is possible to predict a failure that may occur at the time of the current installation, and it is possible to execute the installation process while taking measures in consideration thereof.

  Also, by referring to the troubleshooting method that was taken when the registration process was continued while resolving the failure, the installation process was started after taking the resolution method in advance at the time of this installation. Installation process can be realized.

  Further, by referring to the reason for deleting an application, it is possible to prevent an unnecessary application from being installed accidentally or a problematic application from being installed in advance.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

<Configuration example of electronic equipment>
FIG. 1 is a functional block diagram illustrating a configuration example of an electronic device corresponding to the software resource registration management function of the present embodiment. The electronic device 100 may be any one of a printer, a copier, a FAX apparatus, a mobile phone, a digital camera, a personal computer, a CD (compact disc) recorder, a DVD recorder, an MD recorder, and the like.

  The electronic apparatus 100 according to the present embodiment is not limited to a part of various functional units configured by a hardware processing circuit, and uses a mechanism similar to that of an electronic computer (computer) based on a program code that realizes the function. And can be realized as software.

  By adopting a mechanism for executing predetermined processing (especially software resource registration management processing in this embodiment) by software, a part of each functional element configured by a hardware processing circuit can be removed. Further, it is possible to enjoy the advantage that the processing procedure can be easily changed without changing the hardware. On the other hand, it is possible to construct an accelerator system with a higher speed by using a hardware processing circuit. Even if the processing is complicated, the accelerator system can prevent a reduction in processing speed and can obtain a high throughput.

  When the software resource registration management processing function is executed by software with the same mechanism as an electronic computer, a computer (such as an embedded microcomputer) in which a program constituting the software is incorporated in dedicated hardware, or CPU (Central Processing Unit), logic circuit, ROM (Read Only Memory) that is a read-only storage unit, RAM (Random Access Memory) that is an example of a volatile storage unit that can be written and read at any time, or System on a chip (SOC) that implements a desired system by mounting functions such as a storage device such as a RAM (described as NVRAM), which is an example of a nonvolatile storage unit, on a single chip ) Or a configuration that can execute various functions by installing various programs And installed from the recording medium.

  The recording medium causes a state change of energy such as magnetism, light, electricity, etc. according to the description contents of the program to the reading device provided in the hardware resource of the computer, and in the form of a signal corresponding to the change. The program description can be transmitted to the reader.

  For example, a magnetic disk (including a flexible disk FD), an optical disk (CD-ROM (Compact Disc-Read Only Memory)), a DVD on which a program is recorded, which is distributed to provide a program to a user separately from a computer. (Including Digital Versatile Disc), magneto-optical disc (including MD (Mini Disc)), or package media (portable storage media) made of semiconductor memory, etc. It may be configured by a ROM, a hard disk, or the like in which a program is recorded, which is provided to the user in a state of being recorded.

  The program constituting the software is not limited to being provided via the recording medium without using the recording medium, and may be provided via a wired or wireless communication network.

  For example, a storage medium in which a program code of software that realizes a software resource registration management processing function is supplied to a system or apparatus, and the computer (or CPU or MPU) of the system or apparatus stores the program code in the storage medium The same effect as in the case where the hardware processing circuit is used is also achieved by reading and executing. In this case, the program code itself read from the storage medium realizes a software resource registration management processing function.

  Further, not only the software resource registration management processing function is realized by executing the program code read by the computer, but also an OS (Operating Systems; basic software) operating on the computer based on the instruction of the program code. May perform part or all of the actual processing, and the software resource registration management processing function may be realized by the processing.

  Further, after the program code read from the storage medium is written in a memory provided in a function expansion card inserted into the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. The CPU or the like provided in the card or the function expansion unit may perform part or all of the actual processing, and the software resource registration management processing function may be realized by the processing.

  The program is provided as a file describing a program code that realizes the software resource registration management processing function. In this case, the program is not limited to being provided as a batch program file, and the hardware of the system configured by the computer Depending on the configuration, it may be provided as an individual program module.

  For example, the electronic device 100 configured as a computer system includes a system control unit 102 that controls the operation of the entire apparatus. The system control unit 102 according to the present embodiment has not only a function of controlling the operation of the entire apparatus but also a function of managing registration processing (install / update / uninstall) of various application software used in the electronic device 100. ing.

  Specifically, the system control unit 102 includes a controller unit (control unit) 104, a hard disk device (HDD) 118 or an optical / magnetic disk device 119 shown in the figure, a flexible disk (FD) drive, a CD that is not shown in the figure. A recording / reading control unit 106 for reading and recording data from a predetermined storage medium such as a ROM (Compact Disk ROM) drive and a semiconductor memory controller;

  The controller unit 104 includes a CPU 112, a ROM 113 that is a read-only storage unit, a RAM 115 that is an example of a volatile storage unit that can be written and read at any time, and a RAM (NVRAM) that is an example of a nonvolatile storage unit. 116).

  In the above description, the “volatile storage unit” means a storage unit in which the stored contents are lost when the power of the apparatus is turned off. On the other hand, the “nonvolatile storage unit” means a storage unit in a form that keeps stored contents even when the main power supply of the apparatus is turned off. Any memory device can be used as long as it can retain the stored contents. The semiconductor memory device itself is not limited to a nonvolatile memory device, and a backup power supply is provided to make a volatile memory device “nonvolatile”. You may comprise as follows.

  Further, the present invention is not limited to a semiconductor memory element, and may be configured using a medium such as a magnetic disk or an optical disk. For example, the hard disk device 118 and the optical / magnetic disk device 119 can be used as a nonvolatile storage unit. In addition, it is possible to use as a nonvolatile storage unit by adopting a configuration for reading information from a recording medium such as a CD-ROM.

  In addition, the electronic device 100 configured with a mechanism similar to that of the computer system includes an instruction receiving unit 152 as a functional unit that forms a user interface such as receiving an operation instruction of the device, a guidance screen (operation menu) during operation, and a device. A display output unit 154 that presents predetermined information such as an operation state and a processing result to the user, and an interface unit (IF unit) 190 that performs an interface function with each functional unit.

  The interface unit 190 includes, for example, a user interface unit 192 having an operation panel unit 192a and an operation key unit 192b, protocol control, in addition to a system bus 191 that is a transfer path of processing data (including image data) and control data. And a communication interface unit 194 that performs an interface function with a network and a device interface unit that performs an interface function with other external devices.

  The communication interface unit 194 exchanges data between computers through a network controller that controls a wired network 142 such as a LAN (Local Area Network) or a WAN (Wide Area Network), or a public line network (for example, a telephone line). It has a communication control function such as a modem 144 used for the Note that the network 142 is not limited to a wired type, and may be a wireless type network 146.

  The device interface unit controls various device devices, as will be described later.

  As the instruction receiving unit 152, for example, the operation key unit 192b of the user interface unit 192 can be used. Alternatively, a keyboard 152a, a mouse 152b, or the like can be used.

  Although not shown, the user interface unit 192, the keyboard 152a, and the mouse 152b are connected to the system bus 191 via a device interface unit that controls key input from the keyboard 152a and input from a pointing device such as the mouse 152b. Connected.

  The display output unit 154 includes a display control unit and a display device. As the display device, for example, the operation panel unit 192a of the user interface unit 192 can be used. Alternatively, another display unit 154a made of CRT (Cathode Ray Tube) or LCD (Liquid Crystal Display) may be used.

  For example, the display control unit displays guidance information, a list of information taken from various media by the recording / reading control unit 106, and the like on the operation panel unit 192a and the display unit 154a. It is also used as a display device when notifying the operator of various types of information. Note that the display unit 154a having a touch panel on the display surface may be used to configure the instruction receiving unit 152 that inputs predetermined information with a fingertip or a pen.

  In addition to the above-described function units, the electronic device 100 is also provided with a specific function unit corresponding to the device function. As an example, if the electronic device 100 is constructed as an image forming apparatus having a print output function, a copy function, and the like, an image processing unit 180 that executes processing such as compression / decompression processing and processing of image data, an original image The image reading unit 182 that prints image information and the image information is printed out and presented to the user, based on an image read by the image reading unit 182 or print data acquired via the communication interface unit 194, or the like. An image recording unit (image forming unit) 184 that outputs an image to an output medium (for example, printing paper) may be provided.

  The image reading unit 182 and the image recording unit 184 are connected to the system bus 191 via a scanner interface unit 196 and a printer interface unit 197 as device interface units that form the interface unit 190.

  In addition to these, for example, an audio device 188 that emits audio information is connected to the system bus 191 via an audio interface unit 198 that controls input / output of audio signals.

  A USB device 189 such as a USB memory conforming to the USB (Universal Serial Bus) standard is connected to the system bus 191 via a USB interface unit 199 that controls data input / output with the USB device 189.

  Various devices such as the image processing unit 180, the image reading unit 182, the image recording unit 184, the audio device 188, and the USB device 189 have an application program corresponding to them and an application program (for operating system) that controls the entire controller unit 104. And other software related to image forming processing such as copying, printers, scanners, and facsimiles.

  Each application for each of these devices can be added (installed), changed in specifications (small changes within the same version such as version upgrades and bug fixes), or deleted (uninstalled) for each application. It is possible to add, change specifications, or delete each module that constitutes.

  Further, as a specific functional element of the present embodiment, the controller unit 104 includes a registration information determination unit 172 that determines whether or not an application can be registered based on information in the application registration management table, a determination result of the registration information determination unit 172, and an application An application registration management unit 170 including a notification control unit 174 that notifies the user of past registration processing history of the same type of application stored as a registration management table with display information or audio information is provided.

  When the controller unit 104 executes the registration process of the software resource, the registration information determination unit 172 determines that the history of the software resource of the same type as the software resource to be installed is stored in the application information storage unit 160. In this case, the notification control unit 174 notifies the user of the history information, and controls to execute subsequent processing related to the installation processing according to the user instruction received by the instruction receiving unit 152 based on this notification. It has the function of a registration processing control unit.

  Note that the function of the application registration management unit 170 including the registration information determination unit 172 and the notification control unit 174 and the function of the controller unit 104 including these can be realized by software.

  Here, the same kind of application is not limited to an application whose version and revision within the version (specifications) are exactly the same as the application used for the installation process of this time. Updates for bug fixes and improvements (minor changes / Build), and word processors (word processors) from the same vendor, spreadsheets, databases, and related applications (such as family) such as presentations.

  In short, all faults and uninstall conditions that may have been applied in the same way are included in the same type of application.

  Note that the registration permission determination process itself is based on the application registration processing evaluation conditions such as the mechanism described in Patent Document 5 or the application related to the application used in the apparatus such as the mechanism described in Patent Document 6. These installation determination criteria, such as based on information, may be registered as an application registration management table and determined based on the application registration management table (evaluation conditions and application information). Here, the specific explanation is omitted.

  However, as a specific procedure at the time of registration processing (installation / update / uninstallation) of the present embodiment, whether the requested registration processing can be installed without any problem, or may cause trouble in the installation processing. This is characterized in that it is determined with reference to the registration history of the same kind of application registered in the application registration management table.

  Based on the registration information of the application registration management table, the past installation history of the file to be installed / updated / uninstalled is evaluated, and the installation of the application file for which installation / update / uninstallation is requested based on the evaluation result If it is estimated from the registration history of the same kind of application registered in the application registration management table that the installation can be performed as it is, and it is estimated from the registration history of the same kind of application registered in the application registration management table that By notifying the user of the contents of the registration history, problems associated with the installation process can be prevented in advance, and unnecessary work can be omitted.

  Since the installation process is controlled by referring to the information in the application registration management table, user confirmation prior to installation / update / uninstallation and user operations associated with installation / update / uninstallation are basically unnecessary. The work time can be shortened and various problems such as multiple installations and data loss due to human error can be avoided.

  In addition, based on the notified contents of the registration history, it is possible to continue the more appropriate installation process by reflecting the experience that occurred in the process of the previous application installation in the current installation process. For example, it is possible to adjust conditions related to application deletion, such as a time limit condition and a frequency condition, so that unnecessary uninstallation does not occur again.

  In addition, if it is estimated from the contents of the registration history that the installation process cannot be completed, if a notification to that effect is given in advance, it is not necessary to perform a useless installation process.

  In addition, by registering in advance the method for resolving problems that may occur until the installation process is completed from the contents of the registration history, registration of related applications of the same vendor at the time of version upgrade, reinstallation, etc. Sometimes the installation process can run smoothly.

  In such a configuration, the CPU 112 controls the entire system via the system bus 191. The ROM 113 stores various fixed data including a control program used by the CPU 112. The RAM 115 is configured by an SRAM (Static Random Access Memory) or the like, stores program control variables, data for various processes, and the like, data obtained by calculation according to a predetermined application program, data obtained from the outside, and the like. Is temporarily stored, and is used for a work memory or the like when the CPU 112 performs data processing or the like.

  The NVRAM 116 stores control parameters and processed data, and is backed up. In particular, in the configuration of the present embodiment, the function of the application information storage unit 160 that stores the application registration management table is configured.

  In electronic device 100 having such a configuration, for example, a program for causing a computer to execute a software resource registration management processing function is distributed through a recording medium such as a CD-ROM. Alternatively, this program may be stored in the FD instead of the CD-ROM. In addition, an MO drive may be provided to store the program in the MO, or the program may be stored in another recording medium such as a nonvolatile semiconductor memory card such as a flash memory. Furthermore, the program may be downloaded from another server or the like via a network such as the Internet, or may be updated or updated.

  As a recording medium for providing the program, in addition to FD and CD-ROM, optical recording medium such as DVD, magnetic recording medium such as MD, magneto-optical recording medium such as PD, tape medium, and magnetic recording A semiconductor memory such as a medium, an IC card, or a miniature card can be used. Some or all of the functions for realizing the software resource registration management processing function can be stored in an FD or CD-ROM as an example of a recording medium.

  Further, the storage device such as the hard disk device 118 and the optical / magnetic file holds programs, various applications, user data and control management data such as font data and user files, or data acquired by the device itself or acquired from the outside. An area for temporarily storing a large amount of data or the like is included, and reading / writing of data is controlled by the recording / reading control unit 106 which functions as an input / output interface.

  With such a configuration, the software resource registration management processing program is installed in the RAM 115 from a readable recording medium such as a CD-ROM in which a program for executing the software resource registration management processing function is stored according to a predetermined command. Further, the software resource registration management processing program is started by an instruction or automatic processing by the operator via the instruction receiving unit 152.

  The CPU 112 performs processing according to the software resource registration management processing method described later in accordance with this software resource registration management processing program, stores the processing results in a storage device such as the RAM 115 or the hard disk device 118, and if necessary, an operation panel unit or CRT, Information is presented and output on a display device such as an LCD. By using a recording medium recorded with a program for executing the software resource registration management processing method, a software resource registration management processing system can be constructed universally without changing the existing system.

  Not only the configuration using such a computer, but also the configuration of the electronic device 100 that can execute the software resource registration management processing function by a combination of dedicated hardware that performs processing of each functional unit. You can also.

<Processing Procedure; First Embodiment>
FIG. 2 is a diagram for explaining a first embodiment of processing focusing on the software resource registration management function for the electronic device 100. Here, FIG. 2 is a flowchart showing an example of the processing procedure of the first embodiment for realizing the software resource registration management function.

  In the first embodiment, a history of failures that occurred during installation processing, and when the processing was continued while solving the failures, an application registration management table (flow chart) using the resolution method taken at that time as a registration history. Is stored in a registration log), and the registration process is executed by referring to the registration history of the application registration management table at the next registration process of the same kind of application.

  For example, when the application registration management unit 170 receives a first installation request for an application in the same type of application (S10), the registration information determination unit 172 first determines whether or not the application can be registered. Is determined based on the evaluation conditions and application information (S11). This point is the same as the mechanism described in Patent Documents 5 and 6.

  If registration is possible without any failure (S12-YES), the application registration management unit 170 installs the first module constituting the application program (S14), and the module's The registration history is recorded in the application information storage unit 160 as an application registration management table (S16). All modules are processed in the same manner for each module as long as no failure occurs (S28).

  On the other hand, if the registration information determination unit 172 determines that the evaluation condition corresponds to failure or registration is not possible in the application information, the registration process cannot be continued after removing the failure (S12-). (YES, S18-NO), the application registration management unit 170 interrupts the installation process (S20), and records the failure reason in the application information storage unit 160 as an application registration management table (S22).

  In addition, the application registration management unit 170 continues the registration process if the registration information determination unit 172 determines that registration is possible on the evaluation condition and application information, but the registration information determination unit 172 causes another failure on the way. If it is detected that the registration process cannot be continued after removing the failure (S12-YES, S18-NO), the installation process is interrupted (S20). Further, the reason for the failure is recorded in the application registration management table (S22).

  On the other hand, when the registration information determination unit 172 continues the registration process based on the determination that the registration information determination unit 172 determines that registration is possible on the evaluation condition and the application information, the registration information determination unit 172 If it is determined that another failure has occurred, and it is determined that the registration process can be continued after removing the failure (S12-YES, S18-YES), the failure is removed (cancelled). The installation process is executed (S24), and the reason for the failure and the failure release method taken at that time are recorded in the application registration management table (S26). All the modules are processed in the same manner for each module (S28).

  By following such a procedure, for example, the history of the installation process is recorded for each module as the application registration management table.

  In order to distinguish the applications, all modules of the same application are collected and given one identifier. This identifier may be any identifier that can uniquely identify an application. Typical examples include an application ID (IDentification) and an application name. In addition, the identifier attached to the application may be given so that the creation source of the application is unique, or the checksum of the files constituting the application may be used as the identifier. In addition to the identifier, for example, a vendor name, registration date / time, version information, and other setting information may be added as attribute information.

  As can be seen from the above, the installation process history recorded for each module includes information on whether the installation was successful or failed, if it failed, the reason for failure (failure reason), and failure. In the case where the failure is canceled and the processing is continued, the failure cancellation method is included. Failure reasons include failure due to other factors in addition to interruption of installation processing from the aspect of evaluation conditions and application information.

  Next, when the application registration management unit 170 further receives an application installation request (S60), first, the registration information determination unit 172 searches the application registration management table (S62), and selects an application that is desired to be installed. It is determined whether there is a registration history of the same kind of application (S80).

  Whether or not the application registration history recorded in the application registration management table is the same type as the application to be installed is determined by the identifier attached to the application and attribute information such as vendor name and version information. May be determined by comparing.

  If the registration information determination unit 172 determines that the registration history of the same type application does not exist (S80-NO), the application registration management unit 170 is the first installation request for an application in another type of application. Judgment is made, and the installation process is continued in accordance with the procedure of steps S10 to S28 described above (S82).

  On the other hand, when the registration information determination unit 172 determines that the registration history of the same type of application exists (S80-YES), the application registration management unit 170 records the application registration management table 170 in the application registration management table stored in the application information storage unit 160. The contents of the registered history are read and notified to the user via the notification control unit 174 (S84).

  Upon receiving this notification, the user decides whether to continue the registration as it is, whether to continue the registration after changing the conditions, or to cancel the registration, and to determine the decision content via the instruction receiving unit 152. input.

  When the application registration management unit 170 receives the user determination via the instruction reception unit 152, the application registration management unit 170 executes a registration process according to the instruction content (S86).

  By doing this, if you have tried to install the same kind of application in the past, you can refer to the registration history information related to the installation process of the same kind of application before the actual installation process. Based on the above, it is possible to adjust the installation process of the application this time, so that a more appropriate registration process can be executed. As a result, the convenience of the device for the user can be improved.

  For example, when a certain application is installed, information for identifying the application, the fact of the failure occurring during the installation process, and the reason for the failure are recorded as a registration history in the application registration management table.

  Then, when the same application is installed again, the registration history in the application registration management table is searched to determine whether the installed application has ever been installed. If it is found that the application to be installed has not been installed or uninstalled, the application is automatically installed.

  On the other hand, when it is found that the installed application has a history of installation processing so far, the user is notified accordingly. By doing so, it is possible to notify the user in advance that the installation process this time is inappropriate and the same failure as the previous time may occur.

  Here, in the mechanisms described in Patent Documents 5 and 6, it is determined whether or not the installation is possible. If the installation is impossible, the registration process is interrupted and the user is notified accordingly. At first glance, the mechanism is similar.

  However, with the mechanisms described in Patent Documents 5 and 6, whether or not installation is possible is determined based on the pre-set installation conditions of the application to be registered this time without referring to the past registration history of the same type application. Therefore, if it is determined that the installation is possible, the registration process is executed even though the installation has failed in the past. At this time, in actuality, it is possible that some kind of failure occurs due to a cause other than the evaluation standard or application information, and the registration process cannot be completed as in the previous case.

  In other words, in the mechanisms described in Patent Documents 5 and 6, in the past, although the registration process was started without being determined to be impossible to install, a failure occurred during the installation process and the installation process was interrupted. Even so, when trying to install the same application again, it will not be determined that installation is impossible, and the registration process will be started and the installation process will be interrupted again due to the same failure. As a result, the installation work is wasted.

  On the other hand, in the case of the processing procedure of the first embodiment, the registration processing history is also left for the registration failure triggered by such a failure, based on the registration history in advance. There is a difference in that it is possible to notify whether or not the processing can be completed.

  For example, even if the installation process can be successful from the aspect of evaluation conditions and application information, the registration process of the same kind of application is performed based on the contents of the registration history information presented in advance because of another failure. If it is known that it cannot be completed (if it can be inferred), the registration process is forcibly interrupted so that the useless registration process does not have to be continued.

  Also, if a failure has occurred during the past installation process, but the installation process is eventually completed while searching for a method for canceling the failure, the failure history and the cancellation method are associated with each other and registered. Stored in the application registration management table as a history.

  After that, when trying to register the application (version upgrade, reinstallation, or registration of the affiliated application), based on the registration history, notify the user in advance of the possibility of failure and how to cancel it, Registration processing can be completed while the cause of the failure is canceled before the failure occurs, and the processing can be executed smoothly, so that the work efficiency can be improved.

<Processing Procedure; Second Embodiment>
FIG. 3 is a diagram for explaining a second embodiment of processing focusing on the software resource registration management function for the electronic device 100. Here, FIG. 3 is a flowchart showing an example of a processing procedure of the second embodiment for realizing the software resource registration management function.

  In the second embodiment, an uninstall history is stored as a registration history in an application registration management table (referred to as a registration log in the flowchart), and the uninstall history of the application registration management table is stored during the next registration process of the same type application. It is characterized in that registration processing is executed with reference to (an example of registration history).

  First, it is assumed that an application is installed according to the procedures of steps S10 to S28 of the first embodiment. At the time of this installation, automatic uninstall conditions for the application can be set as necessary.

  Here, the “uninstall condition” is, for example, the expiration date, the use frequency limit, the use frequency, the deletion condition, whether or not functioning normally (see Patent Documents 1 to 4), and the like. In addition to this, for example, when a failure occurs during installation or when a problematic version is installed, it is also included in the application uninstall conditions.

  When these automatic uninstallation conditions are set, the automatic uninstallation conditions are registered in the application registration management table (S30).

  In this state, when the application registration management unit 170 receives an uninstall request for an already installed application (S40), first, when the uninstall request for the application matches a predetermined uninstall condition. It is determined whether it is an automatic uninstallation to be performed or according to an instruction from the user (S42).

  When performing automatic uninstallation (S42-YES), the reason for the automatic uninstallation, that is, the uninstallation condition is detected (S44), and the application is automatically uninstalled and the reason for the uninstallation (registration history) Is recorded in the application information storage unit 160 as an application registration management table (S48).

  On the other hand, in the case of manual uninstallation based on an instruction from the user, after asking the user for the reason for uninstallation (S46), the application is uninstalled according to the user instruction, and input from the user via the instruction receiving unit 152 The reason for manual uninstallation (which is an example of a registration history) is recorded in the application information storage unit 160 as an application registration management table (S48).

  In addition to manual text input using the keyboard 152a, the manual uninstallation user inputs the reason in advance as a menu and presents it to the display output unit 154 in a list format, and the keyboard 152a and mouse 152b are displayed from the menu list. You may make it select by.

  In other words, when automatic uninstallation is performed, the detected automatic uninstallation conditions are automatically recorded in the registration log.When manual uninstallation is performed, the reason is manually recorded. Regardless, when an installed application is uninstalled for some reason, the reason for the uninstallation is recorded in the registration log for each application.

  By following such a procedure, as the application registration management table, for example, the reason for uninstallation is recorded for each application as a kind of registration history in association with the identifier of the application. The application identifier and other attribute information are the same as those in the first embodiment.

  Thereafter, when the application registration management unit 170 receives an installation request for the same type of application, the deletion history of the same type of application recorded in the application registration management table, i.e. It is notified to the user via the notification control unit 174 whether it has been uninstalled for the reason.

  Specifically, when the application registration management unit 170 receives an installation request for a certain application (S60), the registration information determination unit 172 first searches the application registration management table (S62), and the application that is desired to be installed. It is determined whether there is a registration history of the same type of application (S80).

  Whether or not the application registration history recorded in the application registration management table is the same type as the application to be installed is determined by the identifier attached to the application and attribute information such as vendor name and version information. May be determined by comparing.

  If the registration information determination unit 172 determines that the registration history of the same type application does not exist (S80-NO), the application registration management unit 170 is the first installation request for an application in another type of application. Judgment is made, and the installation process is continued in accordance with the procedure of steps S10 to S28 described above (S82).

  On the other hand, when the registration information determination unit 172 determines that the registration history of the same type of application exists (S80-YES), the application registration management unit 170 records the application registration management table 170 in the application registration management table stored in the application information storage unit 160. Among the contents of the registered history, at least the previous deletion reason is read out and notified to the user via the notification control unit 174 (S85).

  Upon receiving this notification, the user decides whether to continue the registration as it is, whether to continue the registration after changing the conditions, or to cancel the registration, and to determine the decision content via the instruction receiving unit 152. input.

  When the application registration management unit 170 receives the user determination via the instruction reception unit 152, the application registration management unit 170 executes a registration process according to the instruction content (S86).

  For example, if it is known from the notification based on the registration log that it was uninstalled because it was an unnecessary application last time, and it is determined that it is an unnecessary application this time as well, the unnecessary application is mistakenly Installation can be prevented in advance. Further, if it is known from the notification based on the registration log that the previous application was a problem application, it can be prevented from being installed again.

  As described above, according to the processing procedure of the second embodiment, if the same kind of application has been uninstalled in the past, the registration history information related to the uninstall process of the same kind of application is obtained prior to the current installation process. It can be referred to, and the installation process of this application can be adjusted based on the registration history information information (especially related to uninstallation), so that a more appropriate registration process can be executed. . As a result, the convenience of the device for the user can be improved.

  For example, when an application is uninstalled, information for identifying the application and the reason for uninstallation (deletion reason) are recorded in the application registration management table as a registration history.

  Then, when the same application is installed again, the registration history of the application registration management table is searched to determine whether the installed application has been uninstalled so far. If it is found that the application to be installed has not been installed or uninstalled, the application is automatically installed.

  On the other hand, when it is found that the application to be installed has been uninstalled so far, the user is notified accordingly. By doing this, it is possible to inform the user in advance that the current installation process is inappropriate and may be uninstalled again.

  Here, in the mechanisms described in Patent Documents 5 and 6, it is determined whether or not the installation is possible. If the installation is impossible, the registration process is interrupted and the user is notified accordingly. At first glance, the mechanism is similar.

  However, in the mechanisms described in Patent Documents 5 and 6, the application itself to be registered this time is set in advance without referring to the past registration history of the same type of application (in particular, the previous uninstall reason in this example). Judgment is made based on the installation conditions that are installed to prevent installation of unnecessary applications by mistake or installation of problematic applications. It is not utilized at all.

  On the other hand, according to the processing procedure of the second embodiment, it is possible to know in advance why the application to be installed has been uninstalled in the past. When installing, there is an advantage that the installation process can be executed based on the past experience.

  For example, since it is notified in advance that the application has been automatically uninstalled after a failure has occurred during installation, it is possible to prevent re-installation without knowing it. In addition, it is notified in advance that the application has been automatically uninstalled because you installed the problematic version, so it is possible to prevent you from upgrading the application without knowing it it can.

  As an additional effect, as described in Patent Document 1, when associating automatic uninstall conditions with charge processing (including discount conditions), automatic uninstall for the current installation due to the relationship with the charge conditions You can also adjust the selection of conditions. In other words, there is an advantage that the user can be given suggestions regarding the selection of the billing method before installing the application.

  At this time, the application registration management unit 170 presents a menu list indicating the relationship between the automatic uninstallation condition and the billing process to the display output unit 154, and the keyboard 152a and the mouse 152b are used from the menu list. You may make it select.

  For example, in the last time, because it was installed by setting a deadline setting and usage limit, it was found that it was automatically uninstalled when it met the automatic uninstallation conditions. When it is loosened or not desired, it can be installed by setting different conditions from the previous one, so that the degree of reinstallation caused by being automatically uninstalled can be reduced.

It is a functional block diagram which shows the example of 1 structure of the electronic device corresponding to the software resource registration management function of this embodiment. It is a flowchart which shows an example of the process sequence of 1st Embodiment which implement | achieves a software resource registration management function. It is a flowchart which shows an example of the process sequence of 2nd Embodiment which implement | achieves a software resource registration management function.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 100 ... Electronic device, 102 ... System control part, 104 ... Controller part, 106 ... Recording / reading control part, 152 ... Instruction reception part, 154 ... Display output part, 160 ... Application information storage part, 170 ... Application registration management part, 172 ... Registration information determination unit, 174 ... Notification control unit

Claims (6)

A registration management method for managing software resources incorporated in an electronic device,
When executing the registration process of the software resource, the history of the registration process is stored in a predetermined storage medium in association with the software resource,
When executing the registration process of the next software resource, it is determined whether or not a history of the same kind of software resource as the next software resource is stored in the storage medium,
If a history of software resources of the same type as the next software resource is stored in the storage medium, the history information is notified to the user,
A registration management method comprising: performing subsequent processing related to the registration processing in accordance with an instruction of the user based on the notification. An electronic device having a registration management function for managing software resources incorporated therein,
An application information storage unit that stores a history of the registration process of the software resource in association with the software resource;
A registration information determination unit that determines whether or not a history of the software resource is stored in the application information storage unit;
A notification control unit for notifying the user of history information stored in the application information storage unit;
An instruction receiving unit that receives an instruction from the user based on the notification from the notification control unit, and
When the registration information determination unit determines that a history of software resources of the same type as the next software resource is stored in the application information storage unit when performing registration processing of the next software resource, the notification An electronic device characterized in that the control unit notifies the user of the history information, and performs subsequent processing related to the registration processing in accordance with the user instruction received by the instruction receiving unit based on the notification. The application information storage unit stores information on a failure that occurred when the software resource is incorporated as a history of the registration process,
The notification control unit, when the registration information determination unit determines that the information related to the failure for the same type of software resource as the next software resource is stored in the application information storage unit, The electronic device according to claim 2, wherein the electronic device is notified. When the registration process is continued while eliminating the failure, the application information storage unit stores, as the history of the registration process, a method for resolving the failure that occurred when incorporating the software resource,
When the registration information determination unit determines that the failure resolution method for the same type of software resource as the next software resource is stored in the application information storage unit, the notification control unit determines the cancellation method. The electronic device according to claim 3, wherein the electronic device is notified. The application information storage unit stores the reason for deletion when the software resource is deleted as the history of the registration process,
The notification control unit notifies the user of the reason for deletion when the registration information determination unit determines that the deletion reason for the software resource of the same type as the next software resource is stored in the application information storage unit. The electronic device according to claim 2, wherein: A program for performing registration management processing for managing software resources incorporated in an electronic device using a computer,
The computer,
A registration information determination unit that determines whether a history of registration processing for the software resource is stored in a predetermined storage medium;
A notification control unit for notifying a user of history information stored in the storage medium;
An instruction receiving unit that receives an instruction from the user based on the notification from the notification control unit;
When the registration information determination unit determines that a history of software resources of the same type as the next software resource is stored in the storage medium when performing registration processing of the next software resource, the notification control unit As a registration processing control unit for notifying the user of the history information and controlling the subsequent processing related to the registration processing in accordance with the user instruction received by the instruction receiving unit based on the notification. A program characterized by functioning.

Images