JP2009026011A - Built-in apparatus, reinstallation method of software, and reinstallation program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reinstall software for restoring a system to its original condition without carrying out great additional installation of a storage area when a fault and the like occurs. <P>SOLUTION: A package acquisition part 102 acquires a software package through a network 101. A package information holding part 105 holds package information of a software package in its acquisition. An installation part 103 installs the acquired software package in an application field 104. A reinstallation control part 107 makes the installation part 103 reinstall a software package reacquired by using the package information acquired via the package acquisition part 102 in an application field 104, from which an already installed software package is erased by a deletion part 106. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an embedded device such as a mobile phone, a software reinstallation method, and a reinstallation program.

  Conventionally, in the case of an embedded device that incorporates an OS and operates autonomously, when restoring the system, for example, a method of backing up a system file shown in Patent Document 1 or a backup of an installation package (software package) shown in Patent Document 2 How to do is known.

  FIG. 5 is a diagram for explaining a conventional method for restoring a system by backing up a system file.

  In the processing unit 1 shown in FIG. 5, the file monitoring unit 11 monitors the shared file at the time of program installation, and if there is a change, passes the change content to the extraction information management unit 4. The extracted information management unit 4 manages the extracted information passed from the file monitoring unit 11 and backs it up to the storage device 6 via the OS 5. When a system failure occurs, the restoration processing unit 8 performs the restoration process by causing the extraction information management unit 4 to extract information stored in the storage device 6.

  FIG. 6 is a diagram for explaining a conventional re-installation method for backing up an installation package.

  In FIG. 6, the deinstaller 31 in the computer device 30 re-installs the installer 33, software 34, and deinstaller 31 installed on the fixed disk 3 of the computer device 30 on an external recording medium or the like according to the installation information 32. Save as installation software 35. Further, installation information 32a necessary for re-installation is created and stored from the registry information 36 and installation information 32 of the corresponding software 34 registered in the registry. If user data 37 created by the software 34 exists, the user data 37 is also saved. The reinstallation software 35 is used to reinstall the computer device 30.

That is, when deleting the installation software 38 installed in the computer device 30 (deinstallation), the computer device 30 shown in FIG.
Japanese Patent Laid-Open No. 9-146762 (page 9, FIG. 1) JP 2006-260163 A (page 24, FIG. 11)

  However, in the conventional configuration described above, it is necessary to back up the system file in the storage device 6 and to retain the installation software 38 to be deleted as the reinstallation software 35.

  For this reason, a storage area for storing backup and reinstallation software is required in the system itself, and in an embedded device such as a mobile phone, when implementing the above reinstallation technology, the expensive storage area must be increased more than twice. I had a problem that I had to.

  The present invention has been made in view of such points, and can be safely installed in the original state by re-installing the software in the event of a failure without significantly increasing the storage area. An object of the present invention is to provide a device, a software reinstallation method, and a reinstallation program.

  The embedded device of the present invention includes a package acquisition unit that acquires the software package via a network in an embedded device that installs and uses at least one software package, and acquisition of the software package when the software package is acquired Acquisition destination information holding means for holding destination information, installation means for installing the acquired software package in an application area of a storage unit, deletion means for deleting the software package installed in the application area, and deletion means The software area re-acquired by the package acquisition means using the acquisition destination information in the application area from which the installed software package is deleted via The A package employs a configuration having a re-installation control means for re-installed by the installation unit.

  In the software reinstallation method of the present invention, when acquiring the software package via a network, an acquisition destination information holding step of acquiring and holding acquisition destination information of the software package to be acquired, and the acquired software package When there is an installation step for installing in the application area of the storage unit and a re-installation instruction for the software package, a deletion step for deleting the software package installed in the application area, and using the acquired acquisition source information, Re-acquisition step for re-acquiring the previously acquired software package from the acquisition location indicated by the acquisition location information, and re-installing the re-acquired software package in the application area It was to have the installation steps.

  In addition, when acquiring the software package via a network, the program of the present invention acquires and holds the acquisition destination information of the acquired software package, and stores the acquired software package in the application area of the storage unit. When there is an installation procedure and an instruction to reinstall the software package, the acquisition step indicated by the acquisition source information uses the deletion step of deleting the software package installed in the application area and the acquired acquisition source information. The computer is caused to execute a procedure for reacquiring the previously acquired software package and a procedure for reinstalling the reacquired software package in the application area.

  As described above, according to the present invention, the software can be safely reinstalled and the system can be returned to the original state in the event of a failure without significantly increasing the storage area.

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

FIG. 1 is a functional block diagram of an embedded device according to an embodiment of the present invention.
The embedded device is a device to which an embedded system in which a program is embedded in a ROM and operated by a CPU is applied, and is described here as a mobile phone.

  In FIG. 1, an embedded device 100 is operated by a system in which a reinstallation program is applied to an OS, and is connected to a network 101.

  The embedded device 100 includes a package acquisition unit 102 that acquires an application package via the network 101, an installation unit 103, a user application area 104, a package information holding unit 105, a deletion unit 106, and a reinstallation control unit 107. A package information acquisition unit 108, a defect determination unit 109, and a defect notification unit 111.

  The package acquisition unit 102 acquires a software package to be operated on the OS by downloading via the network 101, and outputs it to the installation unit 103. In addition, the package acquisition unit 102 can access the server 200 via the network 101 and acquire information stored in the server 200.

  The package information acquisition unit 108 extracts package information related to the software package from the software package acquired by the package acquisition unit 102 and causes the package information holding unit 105 to hold the package information.

  The installation unit 103 installs the software package (specifically, the acquired software application) acquired via the package acquisition unit 102 in the user application area 104 of the storage unit 90 to make it operable.

  In addition, the installation unit 103 receives an instruction to reinstall the software package acquired by the package acquisition unit 102 from the reinstallation control unit 107, and stores the software package acquired again by the package acquisition unit 102 in the user application area 104. Reinstall.

  The user application area 104 is a readable / writable area in the storage unit 90, and the software package acquired by the package acquisition unit 102 via the installation unit 103 is installed and stored. The software package stored in the user application area 104 is incorporated into the OS program and starts on the OS. In addition to the user application area in which a software package (also referred to as “application”) is installed, the storage unit 90 includes a system area in which a system program is stored, and a user such as a phone book and a camera image used in the application. And a data area in which data is stored.

  The package information holding unit 105 holds the package information acquired from the software package by the package information acquisition unit 108. As the package information holding unit 105, an area different from the user application area 104 in which an application is installed in the storage unit 90 is used. For example, the package information holding unit 105 uses a user data area in the storage unit 90 that stores data such as a telephone directory and camera-captured images that are unlikely to cause problems in the system itself even when used. The package information holding unit 105 may be provided anywhere as long as it is readable and writable in the storage unit 90. For example, UnionFS (registered trademark) which is a system that can stack a plurality of directories and handle them as one directory. ) Or the file technology of KNOPPIX (registered trademark), it may exist in a system area that is read-only in the storage unit 90.

  The package information held by the package information holding unit 105 includes information on the location of the acquired software package. Specifically, the package information is information on the acquisition destination that indicates the location of the software package existing on the Internet, and includes, for example, the type of information, server name, port number, folder name, file name, and the like. .

  Here, the package information holding unit 105 saves the name of the installed software package and the URL (Uniform Resource Locator) indicating the location (acquisition source) as the package information to be held.

  FIG. 2 is a diagram illustrating an example of a storage format of package information (also referred to as “download information”) held by the package information holding unit.

  In FIG. 2, the names (names) of packages installed in the system of the embedded device 100 are described together with the download sources (url) of the respective packages.

  As shown in FIG. 2, in the package information holding unit 105, the download source (url) is http: // www. hogehoge. com / browser / mobile / hogehoge10. jar, a package with a name (name) of “hogehoge Full Browser” and a download source (url) of http: // www. fog. com / download / foguequest30. A package having a name (name) of “Fog Quest” which is a jar is recorded.

  The package information holding unit 105 that holds such package information is read by the reinstallation control unit 107.

  The deletion unit 106 deletes all installed applications (installed software applications) stored in the user application area 104 in accordance with a full deletion instruction from the reinstallation control unit 107.

  In response to the reinstallation instruction, the reinstallation control unit 107 reinstalls the previously installed software using the deletion unit 106, the installation unit 103, the package acquisition unit 102, and the package information holding unit 105.

  Here, the reinstallation instruction input to the reinstallation control unit 107 is defect determination information indicating the occurrence of a system defect from the defect determination unit 109. That is, in the present embodiment, when the failure determination information is input, that is, when a system failure occurs, the reinstallation control unit 107 reinstalls the software package installed in the user application area 104.

  Specifically, when a system failure occurs, the reinstallation control unit 107 instructs the deletion unit 106 to delete all the applications stored in the user application area 104, and deletes all installed applications in the user application area 104. Let

  In addition, when a failure occurs, the reinstallation control unit 107 acquires package information from the package information holding unit 105, and uses the acquired package information to send the package information to the package acquisition unit 102 via the network 101. Re-download the software package indicated by the package information.

  Further, the reinstallation control unit 107 instructs the installation unit 103 to reinstall the software package when a failure occurs. That is, the reinstallation control unit 107 causes the installation unit 103 to reinstall the software package re-downloaded (re-acquired) by the package acquisition unit 102 in the user application area 104.

  Note that the defect determination information input to the reinstallation control unit 107 may be input from the user via an operation unit (not shown). For example, the operation unit connected to the reinstallation control unit 107 reinstalls the failure determination information by pressing a predetermined key (the power button ON while pressing the numbers “1” + “5” + “9”). You may make it output to the control part 107. FIG. The reinstallation control unit 107 accepts the input defect determination information as reinstallation instruction information, and performs reinstallation control.

  In addition, when a system failure occurs, the reinstallation control unit 107 acquires package information from the package information holding unit 105, and notifies the defect information as information indicating a combination of software packages when the failure occurs. Output to the unit 111. That is, the reinstallation control unit 107 causes the failure notification unit 111 to notify the external device (server 200) of the combination of applications in which a failure has occurred. Note that the server 200 can be accessed by other embedded devices configured in the same manner as in the present embodiment via the network 101, and the combination information of the software that is stored in the server 200 is a package of another embedded device. Acquired by the acquisition unit. As a result, the user of the embedded device can recognize the combination of applications in which the problem occurs, and can avoid the occurrence of a system problem due to the installation of the software package.

  The defect determination unit 109 detects and determines a defect that has occurred, for example, when the application downloaded by the package acquisition unit 102 via the network 101 is activated in the embedded device 100, and has a defect. In this case, the failure determination information is output to the reinstallation control unit 107.

  The defect notifying unit 111 notifies the external device via the network 101 of the system state (a combination of an installed application and a native application) in a state where the defect has occurred, based on the determination result of the defect occurrence by the defect determining unit 109. Specifically, when the failure determination unit 109 determines that a failure in the system, here, a failure in the system that occurs when a new software package is installed, the software package installed at that time Information indicating the already installed software package is notified to the server 200 connected to the network 101 as defect information.

  The package acquisition unit 102, the installation unit 103, the user application area 104, the package information holding unit 105, the deletion unit 106, the reinstallation control unit 107, the package information acquisition unit 108, the defect determination unit 109, and the defect notification unit 111. The functional block is realized as an LSI that is an integrated circuit.

  Each of these blocks may be individually made into one chip, or may be made into one chip so as to include a part or all of them. Although referred to as LSI here, it may be called IC (Integrated Circuit), system LSI (Large Scale Integration), super LSI, or ultra LSI depending on the degree of integration.

  Further, the method of circuit integration is not limited to LSI's, and implementation using dedicated circuitry or general purpose processors is also possible. A field programmable gate array (FPGA) that can be programmed after manufacturing the LSI, or a reconfigurable processor that can reconfigure the connection and setting of circuit cells inside the LSI may be used. Further, if integrated circuit technology comes out to replace LSI's as a result of the advancement of semiconductor technology or a derivative other technology, it is naturally also possible to carry out function block integration using this technology. Biotechnology can be applied.

  Next, a software re-installation operation in the embedded device of the present invention will be described.

  First, a method for installing a software application in the embedded device 100 will be described with reference to FIG.

  FIG. 3 is a flowchart showing an operation during normal installation in the embedded device according to the embodiment of the present invention.

  At the time of normal installation in the embedded device 100, first, the package acquisition unit 102 downloads and acquires a software application package (installation package) from the network 101 (step S11).

  In step S <b> 12, the package information acquisition unit 108 extracts package information from the installation package acquired by the package acquisition unit 102 and records it as download information in the package information holding unit 105.

  In the example shown in FIG. 2, the name (name) of the package installed in the system is “hogehoge Full Browser”, and the download source (url) is http: // www. hogehoge. com / browser / mobile / hogehoge10. jar. In addition, the package installed before this hogehog full browser has a download source (url) of http: // www. fog. com / download / foguequest30. It is recorded as Fog Quest which is jar.

  As described above, the package information holding unit 105 records information about the download destinations of all installed software packages (installed packages).

  In step S <b> 13, the installation unit 103 installs the installation package input by the package acquisition unit 102 in the user application area 104 and ends the process.

  As described above, in the embedded device 100 according to the present embodiment, when information resources (here, software application packages) are acquired (downloaded) from the outside via the network 101 and installed, the location information of the acquired information resources ( For example, url) is recorded.

  When a plurality of software application packages are installed, the application information holding unit 105 records download destination information (package information) indicating the location of each installed application package.

  Next, an operation for re-installing an already installed software package (also referred to as an installation application) when a system failure occurs will be described.

  FIG. 4 is a flowchart showing an operation for re-installing the installation package in the embedded device according to the embodiment of the present invention.

  As shown in FIG. 4, in the embedded device 100, when the installation package is reinstalled, for example, when a system failure occurs, the failure determination unit 109 detects the system failure and notifies the reinstallation control unit 107. , A signal to that effect is output.

  For example, in the embedded device 100 having the installation package shown in FIG. 2, if a system failure occurs when a newly acquired software package is installed in the user application area 104, the failure determination unit 109 detects and determines it. And output to the reinstallation control unit 107.

  In step S <b> 21, the reinstallation control unit 107 deletes all the contents stored in the user application area 104 in the deletion unit 106. In other words, in step S21, upon receiving an instruction from the reinstallation control unit 107, the deletion unit 106 deletes all user application areas.

  In step S <b> 22, the reinstallation control unit 107 acquires package information from the package information holding unit 105.

  In step S <b> 23, the reinstallation control unit 107 causes the package acquisition unit 102 to download the installation package from the network 101 again using the acquired package information. The downloaded re-installation package is output to the installation unit 103.

  In step S <b> 24, the reinstallation control unit 107 instructs the installation unit 103 to install the reinstalled reload package again in the user application area 104. In response to this, the installation unit 103 installs the reinstallation package again in the user application area 104 from which all installed software has been deleted.

  In step S <b> 25, the reinstallation control unit 107 determines from the package information in the package information holding unit 105 whether there is an installation package (software package) that has not been installed yet.

  In step S25, if there is no package that has not been reinstalled (step S25: No), the process ends. If there is a package that has not been reinstalled (step S25: Yes), the process proceeds to step S26.

  In step S26, the reinstallation control unit 107 acquires package information (information indicating an acquisition destination) of a package (installation package) that has not been reinstalled from the package information holding unit 105, and proceeds to step S23. In step S23, the package acquisition unit 102 re-downloads the installation package that exists in the acquired package information (reinstallation package acquisition destination).

  In step S26, the reinstallation unit 107 installs all the package information held in the package information holding unit 105. However, the present invention is not limited to this, and an operation operated by the user on the reinstallation unit 107 is not limited thereto. May be connected to each other, and a package to be installed by the user may be selected through the operation of the operation unit, and the reinstallation unit 107 may install the package.

  As described above, the embedded device 100 performs the process of step S25 on all the package information (information indicating the download destination illustrated in FIG. 2) held by the package holding unit 105, thereby bringing the system into a state before the occurrence of the system failure. return.

  That is, the reinstallation control unit 107 restores the system to the state before the installation of the software package that caused the system malfunction by the installation by reinstalling the installation package.

  As described above, in the embedded device 100 according to the present embodiment, in the embedded device that installs and uses at least one software package, the package acquisition unit 102 acquires the software package via the network 101. The acquisition destination information holding unit (package information holding unit) 105 holds the acquisition destination information (package information) of the software package when the software package is acquired. The installation unit 103 installs the acquired software package in the application area (user application area) 104 of the storage unit 90. The reinstallation control unit 107 causes the deletion unit 106 to delete the software package installed in the application area 104. Further, the reinstallation control unit 107 causes the package acquisition unit 102 to re-acquire the software package in the application area 104 in which the installed software package is deleted via the deletion unit 106 using the acquisition destination information (package information). Are reinstalled by the installation unit 103. Further, the defect determination unit 109 determines the occurrence of a defect in the system of the device itself when the software package is installed, and the reinstallation control unit 107 reinstalls the software package based on the determination of the occurrence of the defect. Here, the reinstallation control unit 107 uses the acquisition destination information other than the acquisition destination information of the software package installed immediately before the occurrence of the defect to re-install the software package to be reinstalled in the package acquisition unit 102. I get it.

  In other words, when acquiring the software package via the network 101, the embedded device 100 stores the acquisition destination information holding step for acquiring and holding the acquisition destination information of the software package to be acquired, and the acquired software package. When there is an installation step for installing in the application area of the unit 90 and a re-installation instruction for the software package, a deletion step for deleting the software package installed in the application area, and using the acquired acquisition source information, A reacquisition step for reacquiring the previously acquired software package from the acquisition destination indicated by the acquisition destination information, and the reacquired software package is reinstalled in the application area. To re-installing the software and a re-installation step that.

  Therefore, according to the embedded device 100 of the present embodiment, a large storage area such as a backup area is required by holding only the information (download information) of the download destination of the installed information resource (software package). However, it is possible to recover from the system malfunction by returning to the original state when the system malfunction occurs, that is, the state before the malfunction occurred. In other words, unlike the conventional case, in order to configure a backup area etc., the software can be reinstalled in the event of a malfunction, etc. without significantly increasing the storage area, and the system can be safely returned to the state before the malfunction occurred. Can do.

  For example, in the embedded device 100, when hogehoge and Fogue Quest are already installed in the application area, and another software package is newly installed in addition to these, a system failure occurs due to a combination of software (applications). To do. In this case, in the embedded device 100, the deletion unit 106 deletes all the software packages (hogehoge and Fogue Quest) already installed in the application area, and indicates the acquisition destination of the installed software packages (hogehoge and Fogue Quest). The software package is re-acquired using the package information, and then the re-acquired software package (hogehoge and Fogue Quest) is reinstalled, so that the embedded device 100 can restore the system before the occurrence of the failure. it can.

  Also, in the present embodiment, unlike the conventional case, the software can be reinstalled and the system can be restored without saving each file transaction in the storage unit.

  In the present embodiment, the package acquisition unit 102 uses the package information to download the installation package. However, a newer version of the installation package is downloaded to the network 101 than the information recorded as the package information. If there is package information, the latest installation package may be downloaded.

  That is, the embedded device 100 according to the present embodiment includes a failure determination unit 109 that determines whether a failure has occurred in the device itself after the software package is installed, and the reinstallation control unit 107 determines whether a failure has occurred, 102 causes the latest version of the software package to be reacquired from the acquisition destination indicated by the acquisition destination information to be acquired. As a result, if a malfunction occurs in the device itself, the latest version of the software to be reinstalled is acquired and installed, thereby avoiding the occurrence of a system malfunction when the software package that caused the malfunction is installed again. .

  Further, in the embedded device 100 of the present embodiment, it has been described that re-installation is performed when a system failure occurs. However, the present invention is not limited to this, and package information that is information on the acquisition destination of software to be reinstalled is stored. Reinstallation may be performed under any conditions as long as the software package is reinstalled from the acquisition destination indicated by the package information.

  For example, an operation unit connected to the reinstallation control unit 107 may be provided, and a reinstallation instruction may be input to the reinstallation control unit 107 by a user operation via the operation unit. Specifically, in a system in which the software packages A and B of the application are installed, there may be situations where it is desired to return to the state before the software package C is installed after the software package C is installed. In this case, the reinstallation control unit 107 reinstalls the software A and B via the operation unit.

  In addition, when using the embedded device 100 of the present embodiment, there are situations where it is desired to use the same software on the same system as the embedded device before the change when replacing the embedded device, such as changing the model of the mobile phone. obtain. In this case, by configuring the change destination device in the same configuration as in the present embodiment, software will be automatically reinstalled on the change destination device, and the change destination device is the same as the previous model. Embedded devices can be used.

  Further, in the embedded device 100 according to the present embodiment, the failure notification unit 111 notifies the server 200 of download information held at the time when a system failure occurs.

  In other words, in the embedded device 100, when a failure occurrence is determined by the failure determination unit 109, an external device (to which the software package installed in the application area (user application area) 104 is connected to the network 101 when the failure occurs ( Server) 200 is provided.

  Thereby, the package acquisition unit of another system in another embedded device or the like can acquire the information from the server 200 via the network 101. Therefore, it is possible to warn other users before downloading the software package of a combination of software that causes a system malfunction.

  Specifically, when a failure occurs, the reinstallation unit 107 reads a package from the package holding unit 105, outputs the read package information to the package acquisition unit 102, and passes through the package acquisition unit 102 having a communication function. The server 200 on the network 101 is notified. The package information notified to the server 200 is acquired by a package acquisition unit of another embedded device (system) that can be accessed via the network 101 as with the embedded device 100.

  Based on the acquired package information, other embedded devices can detect a system failure that occurs when installing the software package at the source indicated by the package information, and can avoid the same failure.

  In addition, the package information holding unit 105 stores setting information indicating the use setting state when the user changes the use setting for the software (application) installed in the embedded device 100 together with the package information. May be. Thus, even after the installed software is reinstalled due to the occurrence of a system failure, the embedded device 100 can set the installed application to the same setting state as before the failure by using the setting information.

  The package information holding unit 105 may be provided in an external storage device connected to the embedded device or a storage medium that can be detachably connected to the embedded device.

  In this embodiment, the embedded device is described as a mobile phone. However, the present invention is not limited to this, and any embedded device may be used as long as it can be connected to a network. For example, the embedded device may be a mobile phone, a portable information device, a car navigation system, a home phone, a portable game machine, a home game machine, an HDD recorder, a DVD recorder, a set top box, a sewing machine, or the like. Moreover, it is good also as communication equipment, karaoke equipment, etc. as business equipment.

  The embedded device according to the present invention is not limited to the above embodiment, and can be implemented with various modifications.

  For example, the embedded device according to the present invention can be installed in a communication terminal apparatus and a base station apparatus in a wireless communication system, and thereby, a wireless communication terminal having the same operational effects as described above can be provided. .

  Here, the case where the present invention is configured by hardware has been described as an example, but the present invention can also be realized by software. For example, a function similar to that of the apparatus according to the present invention can be realized by describing the algorithm of the retransmission method according to the present invention in a program language, storing the program in a memory, and causing the information processing means to execute the algorithm. it can.

  In other words, the reinstallation program has a procedure for storing package acquisition destination information for reinstallation, a procedure for deleting the user application area, and a procedure for determining occurrence of a system malfunction. If a defect is determined, the user application area is deleted, the software package is downloaded from the network 101 based on the stored package acquisition destination information, and the installation is performed again. In this way, by retaining only the package acquisition destination information in the system, it is possible to recover when a system malfunction occurs.

  The present embodiment can also be applied to a software package (application) to which the sandbox technology is applied.

  Such a reinstallation program can perform system recovery without requiring a large storage area, and is useful for an embedded device having a limited storage area. Moreover, it can be applied not only to system recovery but also to hardware replacement.

  The embedded device, the software reinstallation method, and the reinstallation program according to the present invention have the effect of being able to restore the system in which the software is installed without requiring a large storage area, and can be connected to a network. Useful as equipment.

Functional block diagram of an embedded device according to an embodiment of the present invention The figure which shows an example of the preservation | save format of the package information which a package information holding part hold | maintains The flowchart which shows the operation | movement at the time of normal installation in the embedded apparatus which concerns on one embodiment of this invention The flowchart which shows the operation | movement which reinstalls the installation package in the embedded apparatus which concerns on one embodiment of this invention Diagram for explaining the conventional system file backup method Diagram for explaining conventional re-installation support method

Explanation of symbols

DESCRIPTION OF SYMBOLS 90 Memory | storage part 100 Embedded apparatus 101 Network 102 Package acquisition part 103 Installation part 104 User application area 105 Package information holding part 106 Deletion part 107 Reinstallation control part 108 Package information acquisition part 109 Defect determination part 111 Defect notification part

Claims (7)

In embedded devices that install and use at least one software package,
Package acquisition means for acquiring the software package via a network;
Acquisition destination information holding means for holding acquisition destination information of the software package when the software package is acquired;
Installation means for installing the acquired software package in the application area of the storage unit;
Deleting means for deleting the software package installed in the application area;
Reinstallation in which the software package re-acquired by the package acquisition unit using the acquisition source information is reinstalled by the installation unit in the application area in which the software package already installed through the deletion unit is deleted Control means;
Built-in equipment with. A failure determination means for determining the occurrence of a failure in the system of the device itself when the software package is installed;
The embedded device according to claim 1, wherein the re-installation control unit re-installs the software package when it is determined that a problem has occurred. A failure determination means for determining occurrence of a failure in the device itself after installing the software package;
The embedded device according to claim 1, wherein the reinstallation control unit causes the package acquisition unit to acquire the latest version of the software package to be reacquired from the acquisition destination indicated by the acquisition destination information, based on the determination of occurrence of a defect.   The reinstallation control unit causes the package acquisition unit to reacquire the software package for reinstallation using acquisition destination information other than the acquisition destination information of the software package installed immediately before the occurrence of the malfunction. The embedded device according to claim 2.   The failure notification unit according to claim 2, further comprising: a failure notification unit configured to notify an external device connected to the network of a software package installed in the application area when a failure occurs by the failure determination unit. Embedded equipment. An acquisition destination information holding step of acquiring and holding acquisition destination information of the software package to be acquired when acquiring the software package via a network;
An installation step of installing the acquired software package in the application area of the storage unit;
If there is an instruction to reinstall the software package, a deletion step of deleting the software package installed in the application area;
A reacquisition step for reacquiring the previously acquired software package from the acquisition destination indicated by the acquisition destination information using the acquired acquisition destination information;
A software re-installation method comprising: a re-install step of re-installing the re-acquired software package in the application area. When acquiring the software package via the network, acquiring and holding acquisition destination information of the software package to be acquired; and
A procedure for installing the acquired software package in an application area of a storage unit;
If there is an instruction to reinstall the software package, a deletion step of deleting the software package installed in the application area;
Using the acquired acquisition destination information, from the acquisition destination indicated by the acquisition destination information, a procedure for reacquiring the previously acquired software package;
A procedure for causing the re-acquired software package to be reinstalled in the application area;
Reinstall program to make computer run.

Images