JP4859465B2 - Software updating method and mobile terminal device - Google Patents

Description

  The present invention relates to a mobile terminal apparatus having a communication function and a software update method thereof.

  Currently, mobile phones, which are a type of mobile terminal device, have various functions such as phone calls, e-mail, web browsing, personal information management, memos, camera photography, and are carried by many users. Recently, even models equipped with functions such as radio and television broadcast reception and music playback have appeared.

  Regardless of the number of functions, all mobile phones are controlled by a computer program (software in a broad sense). Such a computer program is stored in a nonvolatile manner in a memory built in the mobile phone.

  Software (hereinafter, also simply referred to as software) is generally upgraded in order to correct a bug called a bug or add or improve a function.

  Normally, software updates for electronic devices are performed by installing the software in the electronic device from a medium on which a new version of the software is recorded, or replacing the built-in ROM. Many mobile phones do not allow the user to perform such work.

  Therefore, recently, a model equipped with a function of rewriting the software of the mobile phone with OTA (Over The Air) has been sold. “With OTA” means wireless using the communication function of the mobile phone. As a result, the software can be updated without placing a special burden on the user or the store. Specifically, software rewriting is realized by a method of downloading the difference file between the upgrade software and the main body program of the mobile phone and updating the software of the main body of the mobile phone only for the difference.

  Conventionally, there have been various problems in implementing the software update function. For example, since the main body program is rewritten after the start of software update execution, if the update is successful, the mobile phone functions as a new version, but if the update fails, the mobile phone cannot be turned on. . In other words, if software update fails due to a memory device failure or write failure, it cannot be recovered. In order to recover, it is necessary to execute a software load via a conventional serial cable, which is difficult for general users.

  In an electronic device whose operation is controlled by firmware, when updating a program with firmware update data received via an external connection interface, the original function can be immediately used for a program that has been destroyed or lost when the update process failed. In order to recover, a technology has been proposed in which the program object to be updated is saved to an external server, and if the process fails after the update process, the saved pre-update object is received from the external server and written back to the ROM. (See Patent Document 1).

In addition, when one of the two update programs in each of the two areas storing the software update program updates the application software and the other update program by downloading via a predetermined communication means, the update is performed at an unexpected stop. Even if there is a failure or failure in a new program downloaded by updating, the old update program on the side that performed the update process remains intact, so a technology that can be updated again at startup etc. has been proposed (See Patent Document 2).
JP-A-2005-235110 JP 2005-284902 A

  In the technique described in Patent Document 1, when updating fails, a normal program temporarily does not exist in the terminal until the previously saved program is written back. It is not preferable in the terminal device.

  In the technique described in Patent Document 2, update programs are prepared twice, but the program itself for realizing the function of the terminal device called “application software” in the same document is a single program. It is prepared only in. Therefore, when the update process of the application software fails and the storage area is damaged, there is a problem that the apparatus cannot be operated at all until the update process is successful again.

  In such a background, the present invention can perform update processing without saving software externally, and even if the update processing fails, the use of the terminal is not restricted for a long time and the mobile device has a communication function. The present invention intends to provide a terminal device software updating method and a terminal device.

It Luso software updating method in the present invention is a software update method of a mobile terminal device having a communication function, in nonvolatile memory, respectively, a first for storing a main-unit program including an update engine for updating software And a second memory area, and when the software is updated, the difference data between the version of one main body program and the version of the new main body program is downloaded, and one update engine of the first and second memory areas is operated The main body program is updated with the differential data by executing the update engine in the working memory area, and when the update is successful, the updated main body program is selected as the current main body program. When the update fails, it is included in the update engine in the working memory area. Download the difference data between the version of the other body program and the version of the new body program by the download function, update the body program with the difference data by executing the update engine in the working memory area, and update If the update is successful, the updated main program is selected as the current main program.

  In this configuration, when the update fails, the download function included in the update engine in the working memory area downloads the difference data between the version of the other main body program and the version of the new main body program. Even if the update of the main body program in the memory area fails, the main body program can be continuously updated in the other memory area.

A second software update method according to the present invention is a software update method for a mobile terminal device having a communication function, and stores a main program including an update engine for software update in a nonvolatile memory. Difference data between the versions of both the main body program and the new main body program using one of the main body programs in the first and second memory areas when updating the software. , Expand one update engine in the first and second memory areas into a work memory area, execute the update engine in the work memory area, and execute the main body program with one difference data Update, and when the update is successful, select the updated main program as the current main program. When the update fails, the update engine in the working memory area is executed to update the main program with the other difference data. When the update is successful, the updated main program is selected as the current main program. It is characterized by doing.

  In this configuration, when the software is updated, the difference data between both the main program version and the new main program version in the first and second memory areas is downloaded. When the update fails, the other main body program can be immediately updated without newly downloading the other difference data. This is particularly useful when the versions of the main body programs in the first and second memory areas are different.

  In any one of the software update methods described above, if the basic engine function including outgoing / incoming calls is included in the update engine, the terminal device can be used even during the update process.

  The present invention also provides a mobile terminal apparatus that implements each of the software update methods.

  According to the present invention, by duplicating the memory area for storing the main body program, it is possible to perform the update process without saving the main program to be updated outside, and even if the update process fails, it is not included in the update target. The mobile terminal device can be operated using the other body program. Therefore, use of the terminal is not restricted for a long time. In addition, the update process can be performed again for the main program that has not been updated.

  Even if the update of one main body program is successful, if the other main body program that has not been updated is valid, the user can select the other main body program as the current main body program. Become.

  If the basic engine function including outgoing / incoming calls is included in the update engine, the terminal device can be used even during the update process.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, preferred embodiments of the invention will be described in detail with reference to the drawings.

  FIG. 1 shows a schematic hardware configuration of a mobile phone according to an embodiment of the present invention.

  The mobile phone 10 includes a control unit 11, an audio processing unit 12, a microphone 13, a speaker 14, a storage unit 15, a communication unit 16, an antenna 17, an operation unit 18, and a display unit 19.

  The control unit 11 includes a processor such as a CPU and a DSP, and controls each unit of the mobile phone 10. The voice processing unit 12 performs voice processing such as a call and music reproduction under the control of the control unit 11, and performs voice input from the microphone 13 and voice output to the speaker 14. The storage unit 15 is a part that stores programs and data, and in the present embodiment, includes a first flash memory 15a, a RAM 15b, and a second flash memory 15c. The first flash memory 15 a is a rewritable nonvolatile memory that stores a program executed by the control unit 11. The RAM 15 b is a memory that temporarily stores programs and data and is used by the control unit 11. In the present embodiment, the RAM 15b is used to copy the update program in the first flash memory 15a into the RAM 15b and execute it when updating the program in the first flash memory 15a, as will be described later. The second flash memory 15c is a rewritable nonvolatile memory that stores various data such as a telephone directory, electronic mail, web contents, music, and images. The communication unit 16 is a part that performs radio transmission and reception with a base station (not shown) via the antenna 17 under the control of the control unit 11. The operation unit 18 includes a numeric keypad, various control keys, a jog dial, and the like, and has a function of inputting user instructions and information to the control unit 11. The display unit 19 includes a display device such as an LCD or an organic EL, for example, and has a function of displaying visible information such as text and images (still images and moving images) to the user.

  FIG. 2 shows a memory configuration of the first flash memory 15a. The program installed in the cellular phone is stored in the first flash memory 15a, and the boot area 21a at the head of the memory address in the memory space 21 is turned on when power is turned on (boot). ) Stores the code to be processed. The main body program is stored in an area 21b following the boot area 21a. The flash memory may have a spare area 21c subsequent to the area 21b (however, this is the same although not particularly shown in the following drawings). Usually, the process branches from the Boot process to the main body program, and the operation of the mobile phone is started. In the software update, the main program part is subject to update (rewrite). In the present embodiment, the “main program” is a program stored in advance in the internal memory at the time of shipment of the mobile phone, and does not include software such as an application program added by the user after sales.

  In addition, the main body program is rewritten in units of blocks in the software update. At this time, if a phenomenon such as device failure or writing failure occurs in a certain block, there is a block whose main body program itself is being updated, and the program is in an inexecutable state. For example, in the example of FIG. 2, the block 1 and the block 2 have been successfully updated, but the block 3 has failed to be rewritten. At this time, the main body program runs out of control while the block 3 is being executed.

  As shown in FIG. 3, the software update engine part is implemented as a part of the main body program. That is, prior to software update, the update engine as update software that is a part of the main body program in the flash memory is temporarily copied into the RAM, and the update engine in the area in the RAM is executed to update the software. Is realized. For example, when updating from version V1.0 to V1.2, a difference file from V1.0 to V1.2 is downloaded, the update engine is expanded on the RAM, and software update is executed.

  In the present embodiment, as shown in FIG. 4A, by having two storage areas (area 21b and area 21d) for the main body program of the mobile phone, it is possible to recover when the software update fails. That is, when the memory area is doubled, the memory capacity for the main body program is doubled. However, when the software update fails, the unupdated area is used for the main body program before the update. Startup is possible. The main body programs # 1 and # 2 stored in the areas 21b and 21d are initially of the same version, but both versions may be different with the update.

  Since it is possible to grasp that the process of program # 1 has failed due to the software update process, if the process of program # 1 fails, a flag (update failure flag) is set, and the boot process as shown in FIG. Is implemented to jump to the main program # 2 with reference to the update failure flag. The flag storage area can be provided in any available nonvolatile storage area. With such a configuration, even when software update fails, it can be normally used as a mobile phone. That is, in this example, the main program # 2 can be selected as the current main program by setting the update failure flag. Initially, the update failure flag is reset, and the main body program # 1 becomes the current main body program.

  The opportunity for software update is when there is a software update notification from the communication carrier or the like to the mobile phone, or from a mobile phone to the communication carrier or the like by a user operation. In the former case, the software update process is activated automatically or subject to user confirmation. In the latter case, the software update process is started according to the user's instruction.

  FIG. 5 shows a processing flow at the time of software update in the present embodiment.

  First, update difference data is downloaded from the server (S11). In this case, the version information of the main body program currently stored in the mobile phone is sent to the server, and the difference data from this version to the update destination version is specified. As will be described later, when two versions are different, there may be a mode in which difference data is downloaded only for one version and a mode in which difference data for both versions is downloaded. Which aspect is adopted may be determined in advance or may be selectable by the user. When downloading the difference data for only one of the versions, it may be determined in advance according to a predetermined condition whether the old or new version is to be updated, or the user can select it. Also good.

  After the download is completed, the mobile phone is reset once, and then it is confirmed by boot processing whether an update file (the above difference data) exists (S12). This can be performed by checking the existence of the update file itself, setting and checking a flag, and the like.

  If the update file exists, the update processing engine in any of the main body programs in the first flash memory 15a is expanded on the RAM 15b (S13). Therefore, control is transferred from the main body program to the update processing engine on the RAM, the update processing is started on the RAM (S14), and the software update processing is executed (S15).

  The main body program of the mobile phone is upgraded every time a defect or the like needs to be corrected. In the present embodiment, only the difference file is placed on the server for software update. By executing the update of the difference file in this way, the file size to be downloaded is reduced, and as a result, the download time and software update time can be shortened. For example, as a guide for the file size, the main body program can be updated with a difference file of about 512 Kbytes relative to the main body program of 32 Mbytes.

Here, for example, it is assumed that the main body program has been upgraded from V1.0 to V1.1 and further to V1.2. In this case, the following three files are placed on the server.
Difference file from V1.0 to V1.1 (1)
Difference file from V1.0 to V1.2 (2)
Difference file from V1.1 to V1.2 (3)

  If the shipping software version of the mobile phone is V1.0 and the version of the main body program held in the mobile phone is also V1.0 on both sides as shown in FIG. 6, the mobile phone is the latest software. Download the difference file (3) to V1.2 on one side and execute software update.

Next, consider a case where software V1.3 is released. In this case, the following files will be placed on the server.
Difference file from V1.0 to V1.1 (1)
Difference file from V1.0 to V1.2 (2)
Difference file from V1.1 to V1.2 (3)
Difference file from V1.0 to V1.3 (4)
Difference file from V1.1 to V1.3 (5)
Difference file from V1.2 to V1.3 (6)

  At this time, as shown in FIG. 7, when updating the software, the mobile phone has a difference file (for example, a difference from V1.2 to V1.3) from one of the currently held main body program versions to the latest version. Download the file (6)) and execute the software update.

When there are two different versions of the main body program that are valid, if the old and new versions are to be updated in advance according to the predetermined conditions, the predetermined conditions are as follows: Can be considered.
a) Update the newer version. In general, the new version often requires less difference data from the latest version, and this method is advantageous from the viewpoint of the amount of difference data.
b) Update the older version. When only the newer version is to be updated, it is conceivable that the older version will not be updated and the two versions will be greatly separated. This method can prevent such an adverse effect.
c) As a compromise of the above methods a) and b), when the version difference between the two surfaces is a predetermined number (for example, 1, 2, etc.), the newer version is to be updated, and the current difference exceeds the predetermined number. If it is, update the older version. According to this method, the advantages of both methods a) and b) can be enjoyed.

  If the software update fails (this is largely due to memory corruption), the above update process can be performed on the other side. In this case, the memory area becomes unusable. As shown in FIG. 8, when rewriting (V1.2 → V1.3) of the surface of the main body program # 1 fails, the main body program # 2 of V1.0 on the other surface is updated. In order to update this area, a difference file (4) from V1.0 to V1.3 is newly required. For this purpose, the V1.0 main body program is activated to newly download a difference file (4) of V1.0 → V1.3.

  Thus, even if the update of one page fails, the update of the other page can be performed, and the user can perform the software update without interrupting the update operation.

  In the above description, when updating the software, the mobile phone extracts the difference data from the latest version of the main body program currently held on the mobile phone side from the server at the time of acquisition, and only the predetermined difference data is stored in the server. Assuming that software is downloaded from

  Next, a modified example of such an operation will be described.

  In this side salute, when downloading the difference file from V1.2 to V1.3, the difference file from V1.0 to V1.3 is also downloaded together, and the update from V1.2 to V1.3 fails. At that time, the difference file of V1.0 → V1.3 is used.

  If it is necessary to return to the original version for some reason even after the software update is successful, it is possible to downgrade to the original version even after the software update according to the user's instruction. For example, when the version V1.1 is stored as the main body program # 1 and the version V1.0 is stored as the main body program # 2 as shown in FIG. 9A, the normal startup is performed as shown in FIG. 9B. The main program # 1 is executed. However, it is assumed that the content of the version upgrade is contrary to the user's intention or that the version needs to be restored for some reason. In this case, a flag (old version use flag) can be set so that the main body program # 2 (old version) is designated by a user operation. (This old version use flag is different from the update failure flag described above). As shown in FIG. 9C, when the power is turned on next time, the Boot code determines the old version use flag, and jumps to the jump destination so that the main program # 2 is mounted. It becomes possible to return.

  In addition, restriction information indicating whether or not it is allowed to return to the old version at the time of software update is also transmitted from the server side, stored in a predetermined storage area, and the old version is used by the user based on this restriction information. You may make it control so that a flag can be set. Such restriction information is useful when it is not preferable to use an old version due to bug correction or data update.

  Conventionally, since the software update is executed in a situation not intended by the user, the user has not known whether the software has been updated. I couldn't know which version of the main program is currently running. Therefore, in the present embodiment, when both main body programs in the first and second memory areas are valid, the user is allowed to select one of the main body programs. Therefore, the user can select the version by adding the mobile phone version information to the selection menu. The user can recognize the version information of the main program being operated. However, regarding the selection of an older version, it is possible to regulate when the use of the old version is not preferable due to the old version use flag.

  Since only the software update process is executed during the rewriting, the telephone function cannot be used until the software update is completed. The update time depends on how much difference data is present, but usually 2 to 5 minutes are required, and since no incoming or outgoing calls are possible at that time, the user has the possibility of opportunity loss.

  However, the main body memory of the mobile phone requires a relatively large capacity, but it is not so large if only the telephone function is provided. The main body program of the mobile phone is currently about 32 Mbytes, but can be realized with a capacity of about 1 Mbyte for realizing the basic functions as a telephone. Therefore, by adding a basic telephone function including outgoing / incoming calls to the update engine, the basic telephone function can be operated even during software update, and the user does not need to be aware of the update time. Execution of the telephone basic function during software update temporarily stops the software update process or executes both processes in parallel by time division.

  For this reason, as shown in FIG. 10, by implementing the basic functions of the telephone in the update engine, basic functional operations can be realized even during software rewriting. The main process of software update is writing to the flash memory, and is executed in coexistence with the telephone basic function. In the configuration itself in which the basic telephone function is included in the update engine so that the basic telephone function can be executed even during software update, it is not necessary to make the main body program area two-sided.

According to the present embodiment, the following effects can be obtained.
1) Since the software update is performed using the difference data, the communication time for downloading and the update processing time can be shortened.
2) By adopting the two-surface configuration of the main body program, the operation can be continued by using the main body program on the other surface of the surface that failed to be updated for some reason after the version update by software update.
3) Similarly, by adopting a two-sided configuration of the main body program, even if the updating of the main body program on one side fails, the main body program can be updated on the other side.
4) Even after a successful version update by software update, it is possible to revert to an older version with conditions. In addition, by attaching conditions, it is possible to suppress the return to the old version when it is inconvenient for the telecommunications carrier.
5) By adding the basic telephone function to the update engine, the basic function of the telephone can be used even during software update. This is effective even when the software main body has one surface. In addition, when two software bodies are managed, even if one software update fails, the second software update can be executed continuously.

  The preferred embodiments of the present invention have been described above, but various modifications and changes other than those mentioned above can be made. For example, by referring to the update failure flag in the boot process, it is possible to prevent the update process from being activated if either of the main body programs is destroyed. (This process can eliminate the possibility of breaking the main program on both sides.)

It is a figure which shows the schematic hardware constitutions of the mobile telephone which concerns on embodiment of this invention. It is a figure which shows the memory structure of the 1st flash memory used in the mobile telephone of FIG. It is a figure which shows a mode that the software update engine part is mounted as a part of main body program. In an embodiment of the present invention, it is a figure for explaining restoration at the time of software update failure by two sides of a main part program. It is a figure which shows the processing flow at the time of the software update in embodiment of this invention. In an embodiment of the present invention, it is a figure showing a situation of software update when versions of two main body programs are the same. It is a figure which shows a mode that the software update of FIG. 6 failed. FIG. 8 is a diagram illustrating a state of updating the main body program on the other surface following FIG. 7. In embodiment of this invention, it is explanatory drawing of version down after version upgrade succeeds by software update. It is explanatory drawing of the modification of embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... Mobile phone, 11 ... Control part, 12 ... Audio | voice processing part, 13 ... Microphone, 14 ... Speaker, 15 ... Memory | storage part, 15a ... 1st flash memory, 15b ... RAM, 15c ... 2nd flash memory, 16 ... Communication Part, 17 ... antenna, 18 ... operation part, 19 ... display part, 21 ... memory space, 21a ... boot area, 21b ... area, 21c ... area, 21d ... area

Claims (7)

A software update method for a mobile terminal device having a communication function,
First and second memory areas for storing a main body program including an update engine for software update are provided in the nonvolatile memory,
When updating the software, download the difference data between the version of the main program and the new version of the main program,
Expanding one update engine of the first and second memory areas into a working memory area;
Update the main body program with the difference data by executing an update engine in the working memory area,
When the update is successful, select the updated main program as the current main program,
When the update fails, the download function included in the update engine in the working memory area downloads the difference data between the version of the other body program and the version of the new body program,
Update the main body program with the difference data by executing an update engine in the working memory area,
A software update method, comprising: selecting an updated main body program as an active main body program when the update is successful. A software update method for a mobile terminal device having a communication function,
First and second memory areas for storing a main body program including an update engine for software update are provided in the nonvolatile memory,
Using either of the main body programs in the first and second memory areas at the time of software update, download both differential data of both the main body program version and the new main body program version,
Expanding one update engine of the first and second memory areas into a working memory area;
Execute the update engine in the working memory area, update the main body program with one difference data,
When the update is successful, select the updated main program as the current main program,
When the update fails, the update engine in the working memory area is executed to update the main body program with the other difference data,
A software update method, comprising: selecting an updated main body program as an active main body program when the update is successful. 3. The software update method according to claim 2, wherein the update engine includes a basic telephone function including outgoing / incoming calls. A mobile terminal device having a communication function,
A non-volatile memory having first and second memory areas for storing a main body program including an update engine for software update;
Working memory,
Control means for accessing the nonvolatile memory and the working memory,
The control means downloads the difference data between the version of one main body program and the version of the new main body program at the time of software update, and sets one update engine of the first and second memory areas as a working memory area. Expand and execute the update engine in the working memory area, update the main body program with the difference data, and when the update is successful, select the updated main body program as the current main body program, and update When it fails, the download function included in the update engine in the working memory area downloads the difference data between the version of the other main body program and the new main body program version, and the update engine in the working memory area is downloaded. Execute, update the main body program with the difference data, and update Successful mobile terminal apparatus characterized by selecting a body program after the update as the current of the main program when the. A mobile terminal device having a communication function,
A non-volatile memory having first and second memory areas for storing a main body program including an update engine for software update;
Working memory,
Control means for accessing the nonvolatile memory and the working memory,
The control means uses the main body program in the first and second memory areas at the time of software update, and downloads both differential data between both the main body program version and the new main body program version, One update engine of the first and second memory areas is expanded into a work memory area, the update engine in the work memory area is executed, and the main body program is updated with one difference data, and updated. When the update succeeds, the updated main program is selected as the current main program, and when the update fails, the update engine in the working memory area is executed to update the main program with the other difference data. When the update is successful, the updated main program is selected as the current main program. Mobile terminal device. Mobile terminal apparatus according to claim 4 or 5, characterized in that the addition of the basic telephone function including initiate and receive the update engine. If the first and second both body program memory area is valid, the mobile terminal device according to claim 4 or 5, characterized in that it comprises means for selecting either of the main body program to the user .

Images