JP4837374B2 - Mobile phone software update result display method and mobile phone capable of displaying software update results - Google Patents

Description

  The present invention relates to updating of mobile phone software.

  In addition to the conventional voice call, the functions provided by the mobile phone are provided with various functions such as transmission / reception of mail, connection to the Internet, and purchase of contents. As a result, software (firmware) that controls the mobile phone and provides various functions becomes large and complex, and the need to modify the program or add new functions is increasing. In order to respond to this requirement, a software update server is provided in a communication network, and update software is distributed to mobile phones using the network.

The software update is started when the user confirms whether there is software to be updated from the mobile phone to the update server. When there is software to be updated, the user selects whether to immediately update the software or to make a scheduled update by setting a date and time later. When the reservation update is selected, the user registers the update date and time in the update server, and ends the communication with the update server.
When the reservation date / time is reached, the update server starts communication with the reserved mobile phone. In the mobile phone, preparation for reception is made by a communication request from the update server, and a session with the update server is established. Thereafter, the update software is downloaded from the update server to the mobile phone, and the mobile phone updates its own software with the received update software.
The literature regarding network devices and automatic program updates includes the following.
JP 2004-62555 A

The mobile phone cannot be used during the software update period. However, by using the reservation update function and setting the software update date / time to an arbitrary date / time, it is possible to avoid the disadvantage caused by the inability to use the mobile phone. Therefore, the update date and time of the reservation update is set to a time when the possibility of using the mobile phone is low, such as a bedtime. All software reservation updates are automatically performed without user intervention.
The reservation update process is started by issuing a notification for starting software update from the update server to the mobile phone at the reservation date and time. The mobile phone that has received the update start notification connects to the server, downloads and installs the update program according to a predetermined procedure, reports the result to the update server, and ends all the processes.
In the course of the update process, several conditions are checked, such as whether the remaining battery level of the mobile phone is sufficient or whether the mobile phone is roaming overseas. When all the conditions are satisfied, the update program is downloaded and installed. Further, when any of the conditions is not satisfied, or when some trouble occurs during the update operation such as program download, the update server stops the update process and disconnects the connection with the mobile phone.

The cellular phone that has made the reservation update notifies the user of the result by displaying “update success” or “update failure”. However, as described above, there are a plurality of reasons why the update process fails. Therefore, in the configuration in which only the result of “update failure” is presented, when the user updates again, it is difficult to remove the cause of the failure and the same failure may be repeated.
The present invention reserves the date and time for starting the update of the mobile phone software, and when the reservation time is reached, the update processing is automatically performed without any user intervention. An apparatus and a method for presenting a message to a user are provided. In addition, the present invention provides an apparatus and a method that do not require a complicated configuration by using information to be presented as information transmitted from a server during a software update process or information selected in a mobile phone. Is.

The mobile phone reservation update starts when the server notifies the mobile phone of the start of the reservation update when the reservation date / time is reached. Thereafter, the process automatically proceeds until the update process is completed regardless of the success / failure of the update. Since the reservation update is performed without user intervention, it has a function of notifying the user of the update result. However, when the update fails, it is necessary to remove the cause of the failure and execute the software update again, and it is desirable that detailed information for identifying the cause of the failure is presented to the user.
Various guidance is displayed in the process of executing the reservation update, and course information is provided. When it is determined that the reservation update cannot be executed, the reason is displayed as guidance and presented to the user. As a method for informing the cause of the failure of the software update, a method of interrupting the update process while the above guidance is displayed and maintaining the guidance display can be considered. However, if the process is stopped at the guidance display step, the processing function of the mobile phone remains occupied by the software update process, and there is a possibility that other processes such as incoming calls cannot be performed.

  The present invention provides a configuration that presents detailed information regarding the result of a reservation update and the cause of the failure to the user with a simple configuration without affecting other processing such as incoming calls. is there. Specifically, the guidance data that presents important information such as the cause of failure displayed in the process of renewing the reservation is saved, and the guidance is later re-established based on the saved data at the request of the user. To display.

  The present invention retains guidance data that presents important information displayed during the update process in software reservation updates that are automatically executed without user intervention. Thus, the configuration in which the guidance is redisplayed from the data makes it possible to present detailed information regarding the reservation update executed to the user without affecting other processing such as incoming calls.

FIG. 1 is a schematic diagram of a system for updating mobile phone software (firmware). The update server includes a device management server (DM server 11) and a download server (DL server 12). In response to an update request from the mobile phone (10), the DM server (11) is connected to an update function (DM client) in the mobile phone (10), and exchanges control and update programs between them. In addition, when an update is reserved, the DM client of the mobile phone (10) is activated by notifying the start of the update to the mobile phone (10) at the reservation date and time, and a control and update program between the two Give and receive.
The DM server (11) is provided with a model table for storing information on software that can be used for each model of telephone used in the mobile phone system. FIG. 1B is an example of a model table. The latest program that can be used by the cellular phone model 1 is software A version 2.5, and the model 2 is software B version 1.8. Has been.
The DL server (12) holds update software, and the requested software is downloaded to the mobile phone (10) via the DM server (11) or directly according to an instruction from the DM server (11). . When software of a specific model is updated, the corresponding part of the model table is corrected and stored in the DL server (12).

The connection format between the DM server (11) and the mobile phone (10) includes the format performed by OMA-DM (Open Mobile Alliance Device Management) shown in FIG. 2 (a) and the format shown in FIG. 2 (b). There is a format that is performed by OMA-DL.
The start notification in the case of OMA-DM is made through the route of the DM server (11), the push proxy server (14), the short message service center (13), and the mobile phone (10), and the software download is performed by the DM server (11 ), WAP proxy (17), GPRS gateway node (16), GPRS service node (15), and cellular phone (10).
The start notification in the case of OMA-DL is made through the route of the DM server (11), the push proxy server (14), the short message service center (13), and the mobile phone (10), and the software download is performed by the DL server (12 ), WAP proxy (17), GPRS gateway node (16), GPRS service node (15), and cellular phone (10).

The outline of the format shown in FIG. 2 (a) is as follows.
(1) Software update is started when the user selects software update from the mobile phone menu screen and issues an update request to the DM server, and the update date and time reserved by the user. The DM server may be started by notifying the mobile phone of an update start.
(2) The mobile phone transmits its model and installed software information to the DM server. The DM server refers to the model table illustrated in FIG. 1B and determines appropriate update software for the model. At this stage, the user is requested to input a personal identification number and the validity of the user is verified.
(3) The determined update software is acquired from the DL server and transmitted to the mobile phone.
(4) When the software download is completed, the DM server instructs the execution of the software installation. In response to this instruction, the mobile phone installs the downloaded update software and updates its own software.
(5) When the software update is completed, the mobile phone notifies the DM server of the result.

The outline of the format shown in FIG. 2 (b) is as follows.
(1) Software update is started when the user selects software update from the mobile phone menu screen and issues an update request to the DM server, and the update date and time reserved by the user. The DM server may be started by notifying the mobile phone of an update start.
(2) The mobile phone transmits its model and installed software information to the DM server. The DM server refers to the model table illustrated in FIG. 1B and determines appropriate update software for the model. At this stage, the user is requested to input a personal identification number and the validity of the user is verified.
(3) The DM server transmits the determined update software information and the DL server address information storing the update software to the mobile phone.
(4) The DM server instructs the mobile phone to download the update software.
(5) The mobile phone requests download information regarding the update software from the DL server based on the DL server address transmitted from the DM server.
(6) The DL server transmits download information to the mobile phone.
(7) The mobile phone requests the DL server to download the update software based on the transmitted download information.
(8) The mobile phone downloads the update software from the DL server.
(9) The mobile phone transmits the download result information to the DL server.
(10) The mobile phone installs the downloaded update software and reports the result to the DM server.

3A and 3B, the user selects the software update from the menu screen of the mobile phone, so that the update software is downloaded from the update server and the mobile phone software (firmware) is downloaded. The process to update is shown. FIG. 3A shows a process of the format shown in FIG. 2A, in which both control data exchange and program download are performed using the OMA-DM between the DM server and the DM client. FIG. 3-2 shows control data exchange between the DM server and the DM client using OMA-DM, and download of the program between the DL server and the DL client using OMA-DL. The process of the format shown in b) is shown.
FIGS. 4-1 to 4-5 show details of the processing flow based on the display screen displayed on the mobile phone in the processing shown in FIGS. 3-1 and 3-2. Hereinafter, the processing of FIG. 3A will be described with reference to FIGS.

Fig. 3-1 (1): Screen [AN-01] in Fig. 4-1 is an example of a menu screen of a mobile phone. When the user moves the cursor to “software update” and operates the “select” key, the software update process is started.
When the update process is started, the remaining battery level is inspected. If the battery runs out during software update, especially during software rewrite, and the rewrite does not end normally, a fatal failure occurs in the mobile phone, such as inability to start up. Therefore, the remaining battery level is inspected before starting the software update process. When it is determined that there is a possibility that the battery update is low and the software update operation cannot be completed, the screen proceeds to screen [AN-03], and a warning screen is presented. 01].
When it is determined that the remaining battery level is sufficient, the screen [AN-02] gives a notice when updating the software. When the user selects “No” to cancel the software update, the screen enters the standby state shown in FIG. 4-5 [DN-01] via the screen [AN-04]. When the user selects “Yes”, the mobile phone control program activates the DM client responsible for the software update process and transfers control.
The DM server checks whether the mobile phone is roaming. Since software cannot be updated during roaming, the screen [AD-04] is presented and the update process is terminated.

FIG. 3-1 (2): When the mobile phone is not roaming, the DM server starts a software update process with the DM client of the mobile phone. The DM server sends a command instructing the user to present a contract and display a guidance requesting a response.
FIG. 3-1 (3): The DM client displays the screen [AD-01] according to the above command, and transmits the user's response to the DM server. When the user does not accept the contract (select “No”), the screen [AD-09] is displayed.
Fig. 3-1 (4): When the user accepts the contract (selects "Yes"), the screen [AD-02] is displayed to request a personal identification number. When the user selects “Cancel”, the screen [AD-10] is displayed.
Fig. 3-1 (5): When the user inputs the personal identification number (PIN) and performs the "OK" key operation, the input personal identification number is transmitted to the DM server and stored in correspondence with the mobile phone. It is compared with the PIN number. If the security code is incorrect, the screen [AD-07] or [AD-08] or [AD-12] is displayed.

FIG. 3-1 (6): When the password is determined to be valid, the DM server requests the DM client for information such as the mobile phone model and software version.
FIG. 3-1 (7): The DM client transmits information about the mobile phone model and the current software version to the DM server. The DM server refers to the model table illustrated in FIG. 1B and detects whether there is update software available for the mobile phone. If the software used by the mobile phone is the latest and no update software is available, the screen [AD-05] shown in FIG. 4-3 is displayed and the update process is terminated.
In addition, the DM server checks whether or not a reservation for software update has been made on the telephone. If a reservation has already been made, the screen [AD-06] is displayed to the user and an answer is given as to whether or not to continue the software update process. If the user decides not to continue the software update process, screen [AD-11] is displayed.

Fig. 3-1 (8): If it is determined by searching the model table that there is software to be updated on the phone, the DM server displays the screen [AD-03] on the mobile phone, and the user To specify the software update method. In this example, there are three options: “1. update now”, “2. reservation update”, and “3. reservation cancellation”.
“1. Update Now” is for continuously updating the software, and “2. Reservation Update” is for the user to specify the date and time for updating the software and make a reservation. When the reserved date and time arrives, the DM server connects to the reserved mobile phone and updates the software. 5 and 6 show the flow of reservation update. “3. Cancellation of reservation” is to change the reservation date and time set by the reservation update. 7 and 8 show a reservation canceling flow. When cancel is selected on screen [AD-03], screen [AD-13] is displayed.

FIG. 3-1 (9): When “1. Update Now” is selected on the screen [AD-03], software update processing is started. The update server checks the usage status of the update server or the communication system. If these are in a congested state and it is determined that the update process cannot be started immediately, the screen [CD-01] is displayed. When it is determined that the update process is possible, the DM server starts downloading the update software.
The following is an example of the process of downloading the update software from the DM server to the DM client shown in FIG.
FIG. 3-1 (10): The DM server acquires update software selected from the model table based on the model information of the mobile phone and the version information of the program being used from the DL server, and downloads it to the DM client. At that time, the mobile phone displays the screen [CN-01] in FIG. 4-4.
FIG. 3-1 (11): When the download is completed, the DM client reports the download result to the DM server.

FIG. 3-1 (12): When the download ends normally, the DM server instructs the DM client to install the downloaded software. The DM client displays screens [CN-02] and [CN-03] to inform the user that the software is being rewritten. When software rewriting is complete, the screen [CN-04] is displayed and the mobile phone is restarted.
Fig. 3-1 (13): The restarted mobile phone displays the screen [CN-05], checks whether the update software is functioning normally, and reports the test result to the DM server.

FIG. 3-2 (10 ′): The DM server sends the address of the DL server and information about the update software to the DM client.
FIG. 3-2 (11 ′): The DM client returns a response (10 ′) to the DM server.
FIG. 3-2 (12 ′): The DM server instructs the DM client to download the update software and install the downloaded update software.
FIG. 3-2 (13 ′): The DM client returns a response (12 ′) to the DM server.
FIG. 3-2 (14 ′): The DL client requests information for downloading the update software to the DL server based on the DL server address transmitted from the DM server in (10 ′).
FIG. 3-2 (15 ′): The DL server returns the information (14 ′) to the DL client.
FIG. 3-2 (16 ′): The DL client requests the DL server to download the update software based on the information returned in (15 ′).
FIG. 3-2 (17 ′): The DL server downloads the update software to the DL client.
Fig. 3-2 (18 '): When the download of the update software is completed, the downloaded result is reported.
FIG. 3-2 (19 ′): The DL server returns the response (18 ′). The mobile phone also installs software.
FIG. 3-2 (20 ′): The DM client reports the end of the update process to the DM server.

  When the screen [A-D-03] of FIG. 4-3 is displayed and the user selects “2. Reservation update”, the reservation processing shown in FIGS. 5 and 6 is started. The DM server is provided with a reservation table that stores whether or not an update reservation is registered for each mobile phone and, if registered, the registration date and time. By performing the reservation process, information indicating that the reservation update is registered and the registration date and time are stored in the column corresponding to the mobile phone that has performed the reservation process in the reservation table. The processing of FIG. 5 will be described below with reference to FIG.

FIG. 5 (1): The DM server that received the reservation update instruction from the mobile phone displays the screen [BD-01] in FIG. 6 on the mobile phone, and requests the reservation date and time desired by the user, that is, the software update. Find the date and time. The date and time can be specified by a method in which the user directly inputs using the numeric keys, or a method in which the DM server presents several candidate dates and the user selects. The screen [BD-01] has a format in which the DM server presents candidate dates and times.
FIG. 5 (2): The desired reservation date and time selected by the user is transmitted to the DM server. The DM server determines whether or not software update processing is possible at the specified date and time. If the software update process cannot be performed for some reason, the screen [BD-04] is displayed, and another date / time selection or the end of the reservation process is requested.
FIG. 5 (3): When the update process is possible at the date and time designated by the user, the user is asked to confirm the user with confirmation of the reservation on the screen [BD-02].
FIG. 5 (4): When the user confirms, the DM server registers the designated date and time in the reservation table as the software update reservation date and time of the mobile phone.
FIG. 5 (5): The server displays the screen [BD-03] on the mobile phone, notifies that the registration of the reservation has been completed, and ends the process.

When the screen [AD-03] of FIG. 4-3 is displayed and the user selects “3. Cancel reservation”, the reservation cancel processing shown in FIG. 7 and FIG. 8 is started.
FIG. 7 (1): The DM server that has received the reservation cancellation instruction from the mobile phone reads the update reservation date and time registered corresponding to the mobile phone from the reservation table. If the update reservation date / time is not registered in the reservation table, the screen [BD-08] in FIG. 8 is displayed. Create a screen [BD-06] from the registered update reservation date and send it to the mobile phone.
FIG. 7 (2): The user confirms the screen [BD-06], and transmits a reservation cancellation confirmation to the DM server.
FIG. 7 (3): The DM server that has received the confirmation deletes the registered update reservation date and time, displays the screen [BD-07], notifies the cancellation of the reservation, and ends the process.

  The DM server is provided with a reservation table for storing whether or not an update reservation is registered for each mobile phone and, if registered, the registration date and time. By monitoring this reservation table, the DM server updates the reservation for the mobile phone whose registration date / time is reached. 9 and 10 show reservation update processing. The process shown in FIG. 9 will be described below with reference to FIG.

Fig. 9 (1): When it is detected that the update reservation time registered in the reservation table is reached, the DM server starts the software update to the mobile phone via the short message service center (SMSC). Notice. As a result, the DM client is activated on the mobile phone. The DM client checks the remaining battery level of the mobile phone and determines whether or not the remaining capacity is sufficient to download and install the update software. If it is determined that the remaining battery level is not sufficient, the screen [CD-03] in FIG. 10 is displayed and the updating process is terminated. When it is determined that the remaining battery level is sufficient, the screen [CD-02] is displayed and the software update is continued.
FIG. 9 (2): The DM client displays the screen [CD-02] and notifies the user of the execution of the update process. If the user selects “No”, the update process is canceled. If the user selects “Yes” or does not respond within a predetermined time, the DM server is requested to continue the update process.
FIG. 9 (3): When a request to continue update processing is transmitted from the DM client of the mobile phone, the DM server checks whether the mobile phone is roaming. When roaming, display the screen [CD-04] and finish the software update. The DM server acquires the mobile phone model and software version information from the DM client, and detects whether there is update software available for the mobile phone. If the software used by the mobile phone is the latest, the screen [CD-05] is displayed and the update process is terminated. When the software to be downloaded and installed is determined, the processing from the screen [CN-01] in FIG. 4-4 is executed.
FIG. 9 (4): The mobile phone checks whether the update software is functioning normally, and reports the check result to the DM server.

  You cannot use your mobile phone while updating the software. Therefore, it is conceivable to reserve the time for performing the update process in a time zone where the possibility of using the mobile phone is low, such as while sleeping. In such a case, for example, even when the user requests input such as the screen [C-D-02] in FIG. 10, the user cannot respond to the request. Therefore, a timer that sets the time to wait for the user's response is provided, and if the response from the user is not within the set time of the timer, it is considered that the user has received an approval response and the reservation update process is continued. The configuration is as follows. In addition, when the update date and time starts when the reservation date / time is reached, the registration information of the update reservation is deleted regardless of whether or not the update processing has ended normally.

  During the software update process, on the mobile phone, “Start software update at reserved time” on the screen [CD-02] in FIG. 10 or “Customers roaming overseas” on the screen [CD-04]. "This service cannot be used" is displayed. The text data to be displayed is stored in a table format in the mobile phone, and the DM client selects and displays it appropriately according to the progress of the process, and is set in the command sent from the update server Some texts are extracted and displayed by DM clients. In FIG. 10, “the software update starts at the reserved time” is the former, and “the customer who is roaming overseas cannot use this service” is the latter.

In many cases, the reservation update is set to a date and time when the mobile phone is not used, for example, a bedtime. Accordingly, in the reservation update processing procedure shown in FIG. 9 and FIG. 10, the user does not necessarily select “Yes” or “No” or operate the “Confirm” key, and the selection or key operation is not performed for a predetermined time. If this happens, the process proceeds as if the user had given consent. In order to inform the user whether or not the reservation update performed during sleep is successful, when the reservation update fails, the update as shown in the screen [DN-01 '] in Fig. 4-5 (b) It is done to make a screen to notify failure.
In the above method, the user can only know the fact that the reservation update has failed, and cannot know the cause of the failure. As the reservation update progresses, a lot of guidance is displayed on the display screen of the mobile phone for presenting information regarding the progress of the update to the user. These guidances include information that informs the cause of the software update failure. The present invention adopts a configuration in which detailed information displayed as guidance is stored in a mobile phone and redisplayed at the request of the user later.

FIG. 11 is a diagram illustrating an overview of display control according to the present embodiment. Reference numeral 50 denotes a guidance table stored together with the control program in the mobile phone, and a guidance to be displayed is appropriately selected as the program progresses. 51 shows a state in which “software update completed” is selected from the guidance table 50 to display the screen [CN-06] of FIG. 4-4.
Some mobile phone guidance is transmitted from an update server. In this format, the guidance to be displayed is included in the command transmitted from the server, and the mobile phone that has received the command extracts and displays the guidance text included in the command. Reference numeral 52 in FIG. 11 is an example of a command including a guidance sentence. When the DM server checks whether or not the mobile phone is in overseas roaming in the processing flow in FIG. Command to send to This command includes a guidance sentence “Customers who are roaming overseas cannot use this service”. In step 53, the guidance is extracted.
The guidance selected from the guidance table or the guidance extracted from the command is stored in the display buffer 54 and displayed by the display control unit 55. 54 is an example in which “the customer who is roaming overseas cannot use this service” extracted from the command 52 is stored and displayed. In this example, the screen [CD-04] in FIG. 10 is displayed.

  In this embodiment, a save buffer 56 is provided in parallel with the display buffer 54. The save buffer 56 may be an independent register or may be secured as a data area in the memory. In the process of displaying the reservation update, in the step of displaying the guidance including important information, the guidance data is stored in the display buffer 54 and displayed and also stored in the save buffer 56. FIG. 11 shows a process (57) of storing guidance data of “Customer who is roaming overseas cannot perform this service” in the display buffer 54 and storing in the save buffer 56 indicating the reason why the reservation update could not be performed. ing. When the user performs an operation for confirming the result of the reservation update later, the guidance data stored in the save buffer 56 is transferred to the display buffer 54 (58). As a result, the mobile phone displays the guidance “Customers who are roaming overseas cannot perform this service”, and the user can know that the reservation update was not executed and the cause.

FIG. 12 is a processing flow of reservation update according to the present embodiment. FIG. 13 shows the flow of processing on a display screen, which corresponds to FIG. 4-5 (b). In the reservation update of this embodiment, the screens [CD-02], [CD-03], [CD-04], [CD-05] in FIG. 10 and the screen [CN-06] in FIG. 4-4 are used. The forward (E1) is changed to (E1 ′) in FIG. Hereinafter, the processing of this embodiment will be described with reference to FIGS.
Details of the processing flow shown in FIG. 12 will be described.

Step 101: When the registration update registration date and time is reached and the start of the reservation update is notified from the update server, the cellular phone activates the DM client and starts the update process.
Step 102: Check whether the battery capacity of the mobile phone is sufficient for the software update process. When the battery is insufficient, the process proceeds to step 103. When the battery is sufficient, the process proceeds to step 104.
Step 103: The guidance on the screen [CD-03] in FIG. 10, “The battery level is insufficient, please update the software again after charging” is displayed, and the process proceeds to Step 113.
Step 104: Display the screen [CD-02] in FIG. 10 and wait for a predetermined time. If there is no response from the user within the time, the process proceeds to Step 105.
Step 105: The update server determines whether the mobile phone is roaming and transmits the result to the mobile phone. When roaming is in progress, the process proceeds to step 106, and when not roaming, the process proceeds to step 107.
Step 106: Guidance on the screen [CD-04] in FIG. 10 that roaming is in progress and software cannot be updated is displayed, and the process proceeds to Step 113.
Step 107: The mobile phone transmits its model and software information to the update server. The update server checks whether there is software to be updated and sends the result to the mobile phone. If the software being used is the latest, the process proceeds to step 108. If the software being used is not the latest and there is software to be downloaded and installed, the process proceeds to step 109.
Step 108: A guidance is displayed on the screen [CD-05] in FIG. 10 indicating that the software being used is the latest and it is not necessary to update, and the process proceeds to Step 113.
Step 109: The update server checks whether the network is in a congestion state. When in a congested state, the mobile phone proceeds to step 110 and proceeds to step 111 when the network is not congested.
Step 110: The mobile phone displays that it is in a congested state and cannot be updated, and proceeds to Step 113.
Step 111: The mobile phone downloads the update software from the update server and installs it.
Step 112: The mobile phone displays the update result shown in the screen [CN-06] in FIG. 4-4.
Step 113: Arrival at step 113 corresponds to (E1 ′) in FIG. When the arrival at this step is from Steps 103, 106, 108, and 110, guidance indicating the cause of the update not being performed is displayed on the mobile phone display. In the case from step 112, guidance on the result of the update is displayed on the display. The display data of these guidances is held in the display buffer 54 of FIG. 11, and this display data is saved in the save buffer 56 in step 113 (FIG. 13-300).
Step 114: The mobile phone displays a “notification screen” indicating that the reservation has been updated, and enters a standby state (FIG. 13-301).

Step 120: After waking up, the user recognizes that the reservation update has been automatically performed on the mobile phone notification screen, and operates the confirmation key in Step 121 (FIG. 13-302).
Step 122: The mobile phone transfers the display data stored in the save buffer 56 to the display buffer 54 and controls the display circuit (FIG. 13-303). By this processing, the display saved in the save buffer 56 in step 113, that is, the cause of not performing the update or the result of executing the update is displayed on the display screen (FIG. 13-304).
Step 123: The user visually recognizes the displayed information and operates the confirmation key.
Step 124: The mobile phone erases the contents of the save buffer 56 (FIG. 13-305) and displays a normal standby screen (FIG. 13-306).

In the above embodiment, in the reservation update operation, the guidance data displayed on the display screen is copied from the display buffer to the save buffer. As another configuration, when the display data is read from the guidance table 50 of FIG. 11, the item number of the guidance table 50 is stored, and in the example of FIG. 11, (N) is stored. If the display data is from a reception command from the DM server, the display character string can be extracted from the reception data in the reception buffer and displayed.
Further, instead of the configuration in which the guidance data is saved in the save buffer, a configuration in which part or the whole of the screen is saved as image data and the screen is reproduced based on a request from the user is also possible.

There is a reservation update as a method of downloading and installing update software on a mobile phone. In this method, a user reserves an arbitrary date and time, such as a bedtime, in the update server, and when the reservation date and time is reached, the mobile phone is activated from the update server, so that the update software can be used without user intervention. Is downloaded from the update server to the mobile phone and installed. In the reservation update, regardless of the failure / success of the update process, the process proceeds without user intervention, so that a user such as sleeping cannot know detailed information regarding the update process. Updating the mobile phone software is an important task, and when the update process fails, it is necessary to perform the update process again. However, since the user cannot know the cause of the update process failure, the failure is repeated due to the same cause even if the update process is re-executed.
In the software update process, a lot of guidance is displayed during the update process. The information displayed by guidance includes a lot of important information related to the failure or success of the update process, such as the battery status of the mobile phone and the status of the update system. According to the present invention, in a reservation update in which update software is downloaded and installed without user intervention, a guidance including information on the failure or success of the update process is selected from the guidance displayed in the process of the reservation update. It has the structure preserve | saved in. With this configuration, a user who has recognized that a software reservation update has been performed can know detailed information regarding the execution result of the reservation update by instructing to redisplay the guidance information stored in the mobile phone. Even if the update process is re-executed, the failure is not repeated due to the same cause.

Overview of software update system to which the present invention is applied Overview diagram of communication between update server and mobile phone First processing diagram for software update Second processing diagram for software update Software update processing flow chart (1) Software update processing flow chart (2) Software update processing flow chart (3) Software update processing flow chart (4) Software update processing flow chart (5) The figure which shows the processing of registration of software reservation update Software reservation update registration process flow diagram Reservation cancellation processing diagram Reservation cancellation processing flow chart Processing diagram of reservation update execution Processing flow diagram of reservation update execution Conceptual diagram of software update result display means according to the present invention Flow chart of software update result display control according to the invention Display processing diagram to which the software update result display control according to the invention is applied

Claims (4)

A method of displaying update information of automatic software update for automatically updating software of a mobile phone by update software stored in an update server in the mobile phone,
By executing the program stored in the memory in the mobile phone by the control unit of the mobile phone,
Downloading update software from the update server by receiving notification of reservation update start from the update server, and installing the downloaded software;
Displaying guidance during the download and installation process;
Determining the success or failure of the download or installation;
A step of saving guidance information displayed when the determination step determines whether the download or installation is successful or unsuccessful;
Detecting an operation requesting display of update information of automatic update by an operator;
A method of displaying update information of software automatic update by executing a step of displaying information of the saved guidance in response to the detecting step detecting the operation by an operator. The method of claim 1, comprising:
The mobile phone controller
A method of displaying on a display screen information instructing an operation for requesting display of update information of automatic update by an operator when the mobile phone is set in a standby state at the end of the step of saving guidance information. A mobile phone comprising control means, storage means for storing software, communication means for communicating with an update server, display means for displaying guidance, and input means,
The control means downloads the update software from the update server by receiving a notification of reservation update start from the update server by the communication means, and installs the downloaded software;
Means for displaying guidance in the process of download and installation on the display means;
A means of determining the success or failure of the download or installation;
Means for saving guidance information displayed when the determination means determines success or failure of download or installation;
Means for detecting an input requesting display of update information of automatic update from the input means;
A mobile phone comprising: means for displaying the saved guidance information on the display means in response to the means for detecting the requested input detecting that the request has been detected. The mobile phone according to claim 3,
The control means displays information for instructing an operation for requesting display of update information of automatic update on the display means when the mobile phone is placed in a standby state upon completion of the means for saving guidance information. Mobile phone with means.

Images