JP4813170B2 - Mobile phone software reservation update method and mobile phone with software reservation update function - Google Patents

Description

  The present invention relates to updating of mobile phone software.

  In recent years, functions provided by mobile phones include various functions such as transmission / reception of mail, connection to the Internet, and purchase of contents in addition to conventional voice calls. As a result, the software 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 while the software is being updated. However, by using the reservation update function, it is possible to arbitrarily set the software update date and time and to avoid the disadvantage caused by the inability to use the mobile phone. When the software update communication is started from the server when the reservation date and time are reached, or when the mobile phone is not performing any other processing, that is, in the standby state, the connection between the two is immediately established, and the update software is downloaded and Installation starts. However, software update processing cannot be performed when the mobile phone is performing other processing such as during a call or while an application is being executed.

If the mobile phone does not immediately respond to the software update start notification from the update server due to use such as in use, the update server waits for a response from the mobile phone. However, it is a heavy burden on the system that the update server waits for a mobile phone response for a long time. Therefore, the reservation update is configured to stop the update process when the mobile phone does not respond to the update start notification from the server within a predetermined time.
When the update process is canceled, the reservation update registration registered in the update server becomes invalid, and the user needs to redo the update process. However, users who use mobile phones for other purposes, such as calls, are very aware that software update start notifications have been received from the update server, and that software update processing has been canceled due to a timeout. It is difficult to. As a result, it is not recognized that the software has not been updated, and the state in which the important software has not been updated continues.
The software update process is a process for rewriting the control program of the mobile phone. If the rewrite fails, the mobile phone cannot be activated and has a serious influence. Therefore, it is necessary to alert the user not to perform an operation that affects the rewriting of the program such as turning off the power of the mobile phone during the software update process.

In a mobile phone in which the user can reserve the software update date and time at an arbitrary date and time, when the reservation date is reached and the update server notifies the start of the software update process, the display screen of the mobile phone is displayed. A display (pictogram) indicating that the notification has been received is displayed.
In addition, the present invention prevents a user from performing an inadvertent operation by displaying a display (pict) indicating that the software is being updated on the display screen of the mobile phone during the software update. Calls attention.

The present invention displays a pictograph indicating that the update start notification has been received on the screen of the mobile phone when the update date and time is notified from the server to the mobile phone. This display allows the user to recognize that the update reservation date and time has come, and to stop the use of the mobile phone and execute the update process. Also, even if the user does not stop using the mobile phone and the server stops the software update process due to a timeout, the pict display indicates that the software update has failed and the update is The user is informed that it needs to be done.
As a result, it is possible to prevent a state in which important software is not updated from continuing.
In another embodiment of the present invention, a pictograph indicating that the software is being updated is displayed to alert the user not to perform an inadvertent operation.

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 for storing whether or not an update reservation is registered corresponding to 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 for 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.

A mobile phone cannot execute a call or other application and a software update process at the same time. The reservation update shown in FIG. 9 and FIG. 10 is a reservation date and time, and when the update server notifies the start of software update, the mobile phone is in a standby state and can respond immediately to the notification. .
The update server transmits an update start notification to the mobile phone, and then waits for a response from the mobile phone for a predetermined time. If no response is made from the mobile phone within this time, the update server stops the update process and invalidates the registration information for the reservation update. In this case, the user needs to redo the software update request from the mobile phone.
However, with a conventional mobile phone, the software update reservation date and time becomes available while the mobile phone is being used, and the user cannot know the fact even if an update processing notification is received from the update server. The user continues to use the mobile phone, and the update server times out the waiting time, and important software is not updated.

When the mobile phone receives an update start notification from the update server, the display of the notification (update reservation pictograph) indicating the reception of the notification is displayed. It is possible for the user to recognize that the software update reservation date has been reached and that the update server has notified the start of the update.
In addition, a timer that is activated when an update start notification is received from the update server is provided on the mobile phone, and if the user stops using the mobile phone or uses other applications within the set time of the timer, the timer is updated. The process can be started. Furthermore, even if the timer setting timed out and the update process was canceled, by maintaining the display of the update reservation pictogram, the user was notified of the start of the update and did not respond to the notification Can be recognized.

  FIG. 11 is a diagram showing processing of the mobile phone that is the update reservation time and notified of the start of update from the update server. FIGS. 12A and 12B are diagrams illustrating the time history when the start of the reservation update is notified, and when the mobile phone cannot respond to the start notification due to a call or other application being executed. It is. FIG. 12A shows the time history when the user of the mobile phone stops using the mobile phone within the timer setting time and responds to the update start notification from the update server. FIG. 12-2 shows the time history when the use of the mobile phone becomes longer than the timer setting time and the reservation update becomes invalid.

  The update server is provided with a reservation table for managing the presence / absence of reservation update registration for each mobile phone. When the reservation update is registered from the mobile phone according to the processing shown in FIGS. 5 and 6, the update server records the reservation registration on the mobile phone and the reservation date and time in the reservation table. The update server always inspects the reservation table, extracts the mobile phone that has the registered update date and time, and notifies the start of the reservation update. The mobile phone that has received this notification starts processing from step 101 in FIG.

Step 101: The mobile phone receives a reservation update start notification from the update server. A receiving function such as SMS is a function independent of a normal voice call or other application execution function. Therefore, even when the mobile phone is in use such as during a call, it is possible to receive a reservation update start notification and perform related processing.
Step 102: The reservation update start notification is received, and the receiving unit displays on the display screen that the notification has been received (update reservation pictograph). An example is shown in FIG. 12-1 (a). Like the pictogram indicating the charging status of the battery or the radio wave intensity, the pictogram preferably does not harm the application display.
Step 103: Upon receipt of the reservation update start notification, the reception function unit determines whether the mobile phone is in a standby state, that is, whether the user is not using the mobile phone for a call or the like. If it is determined that it is in a standby state, the process proceeds to step 104.
Step 104: It is determined whether or not the battery of the mobile phone is sufficient for the software update process. If it is determined that the remaining battery level is insufficient, the process proceeds to step 105 to display the screen [CD-03] in FIG. 10 and stop the update process. At that time, the display of the update reservation picture is stopped.
Step 108: If it is determined in step 104 that the remaining battery level is sufficient, the process proceeds to step 108, and the screen [CD-02] shown in FIG. 10 is displayed to ask for user confirmation. If the user selects “No” and indicates the intention not to update, the process proceeds to step 106, the display of the update reservation picture is stopped, and the update process is stopped. If the user selects “Yes” in step 107 or does not respond for a predetermined time, the process proceeds to step 109.
Step 109: Check whether the mobile phone is roaming. When roaming is in progress, the process proceeds to step 110 to display the screen [CD-04] shown in FIG. 10, stops displaying the update reservation pictogram, and ends the software update.
Step 111: The DM server of the update server and the DM client of the mobile phone display the screen [CN-01] of FIG. 4-4, and download the software according to the processing shown in FIG. .
Step 112: The screens [CN-02] and [CN-03] shown in FIG. 4-4 are displayed, and the downloaded update software is installed.
Step 113: The screens [CN-04] to [CN-06] shown in FIG. 4-4 are displayed and post-update processing is performed. Next, the standby scene [DN-01] in FIG. 4-5 is displayed and all the processes are completed. The update reservation pictograph is deleted when the mobile phone is restarted.
Step 114: If it is determined in step 103 that the mobile phone is in use, the user stops using the mobile phone and waits for software update. At this time, the update server is in a state of waiting for a response from the mobile phone, and the load on the update server increases as the wait state becomes longer. Therefore, this waiting time is set to, for example, 5 minutes in consideration of the system use situation or capability. In step 114, a timer for detecting the elapse of the set time is started. A similar timer is also provided in the update server, and this timer is started when the start of reservation update is notified. If there is no response from the mobile phone within the set time of the timer, the reservation update is canceled and the reservation update registration recorded in the reservation table is deleted.
Step 115: It is determined whether or not the use of the mobile phone is finished. If it is determined that the process has been completed, the process proceeds to step 104 and the software update process is started. If it is still in use, go to step 116.
Step 116: Check the timer to determine whether the set time has elapsed. If not, the process proceeds to step 115. When the set time elapses and the timer times out, the process proceeds to step 117.
Step 117: After the set time elapses, the reception unit of the mobile phone stops the process while continuing to display the update reservation pictograph.

FIG. 12A shows the time history when a mobile phone that has been reserved for update at the date and time T1 receives a notification of the start of a reservation update from the update server during execution of the application and terminates the application within a predetermined time. FIG.
At the date and time T1, the update server notifies the mobile phone of the start of reservation update. When the update server notifies, the update server starts a timer that measures a time for waiting for a response from the mobile phone, for example, 5 minutes.
The mobile phone that has received the reservation update start notification displays a reservation update pictogram (FIG. 11, step 102), and determines whether the mobile phone is in use (FIG. 11, step 103). Since the mobile phone is executing an application, a reservation update picture is displayed on the display screen of the mobile phone together with the screen of the application, as shown in FIG. The user who is executing the application recognizes that the software update reservation date and time has been notified by the reservation update pictograph displayed on the application screen.

The cellular phone starts a timer for measuring a predetermined time (5 minutes in this embodiment) (FIG. 11, step 114) and waits for the end of the application (FIG. 11, step 115 and step 116).
When the user stops executing the application at the time T2 before the timer times out, the mobile phone recognizes that the use of the mobile phone has ended in step 115, stops the timer, and proceeds to step 104. When the update process of the mobile phone software is started in step 104, the mobile phone returns a response to the reservation update start notification to the server as a response to the update server. Upon receiving this response, the update server stops the timer for measuring the response wait time and starts connection with the mobile phone. When the connection between the update server and the mobile phone is taken and the download of the update software is started, a display notifying the start of the reservation update shown in (b) is made on the mobile phone. When the update process is completed, as shown in (c), the display of the update reservation picture is stopped and the normal standby screen is displayed. In addition, FIG. (B) is an example which continues displaying the update reservation pictograph on the screen during the update execution, but it is also possible to have a configuration in which the display of the update reservation pictograph is stopped when the connection between the update server and the mobile phone is established. .

FIG. 12-2 shows that a mobile phone that has been reserved for update at the date and time T11 has received a reservation update start notification from the update server, but the application execution by the user has become longer than the predetermined time, It is a figure which shows the time course when update becomes invalid.
At the date and time T11, the update server notifies the mobile phone of the start of reservation update and sets a timer for waiting for a response. On the mobile phone, a reservation update pictograph is displayed together with the application screen (FIG. (A)), and a timer for waiting for the end of use of the mobile phone is set.
When the date and time T12 is reached, the mobile phone determines that the timer has timed out in step 116 of FIG. In step 117, the receiving unit that has started the function upon receiving the notification of the reservation update start from the update server stops the function. However, the update reservation pictogram is not deleted, but the reservation update pictogram is continuously displayed on the application screen as shown in FIG.
The server waits for a response waiting timer, stops the software update process for the mobile phone, and deletes the registered reservation information.
When the date and time T13 is reached and the user ends the application, the screen becomes a standby screen. However, the reservation update picture displayed in step 102 continues to be displayed together with the standby screen as shown in FIG. This display is configured to be erased when the user performs confirmation input.

  In this embodiment, a software update start notification is received from the update server, and an update reservation picture is displayed on the display screen of the mobile phone. When the scheduled software update date and time set by the user is reached and the update server receives a notification to start the software update, the mobile phone is in use and the update is immediately responded to the notification from the update server. Even if it cannot start, the above update reservation pictograph is displayed on the display screen, so that the user can recognize that the update start notification has been received from the update server because the software update is scheduled. It becomes. In this embodiment, the update reservation pictograph is continuously displayed even after the software update is canceled due to a timeout. With this configuration, it is possible to notify the user that it is necessary to redo the software update request.

  The first embodiment displays an update reservation pictograph when the mobile phone receives a reservation update start notification from the server, informs that the update reservation time has come, and ensures that the reservation update is performed. is there. However, the software update process is a process necessary for the maintenance and management of the mobile phone, but downloading or installing the program is an operation that is a heavy load on the mobile phone itself or the mobile phone system. Also, failure to install the update program will have a fatal effect on the mobile phone. Therefore, it is necessary to inform the user that the software is being updated, and to alert the user not to perform an operation that greatly affects the software update, such as a power interruption. In the second embodiment, during software update work, a display (software update pictograph) indicating that software update work is being performed is displayed on the mobile phone so that the user is not allowed to perform an operation that affects the update work. Be careful.

FIG. 13A corresponds to FIG. 4A of the first embodiment ([AN-02] and thereafter omitted), and FIG. 13B corresponds to FIG. 4-5 of the first embodiment. It is an outline.
The screen [AN-01] in FIG. 13A is the same screen as [AN-01] in FIG. 4A. The user moves the cursor to “software update” and operates the “select” key. Thus, the software update process is started. In the second embodiment, when “software update” is selected, processing of “software update pictogram display” is performed. With this process, the software update pictograph is displayed on the screen of the mobile phone as shown in the screens [AN-02 ′], [AN-03 ′], and [AN-04 ′]. Although omitted in FIG. 13A, the software update pictograph is similarly displayed on the screen corresponding to the display screen of the mobile phone illustrated in the first embodiment.
By visually recognizing this pictogram, the user can be careful that the software is currently being updated and the power is not cut off. As shown in FIG. 13B, before the software update process is completed and the mobile phone screen is set to the standby screen, the software update pictograph is deleted. This process informs the user that the software update process has been completed.
The software update pictogram of the second embodiment may be shared with the reservation update pictogram of the first embodiment, or both pictograms may be different.

The present invention displays a pictograph indicating that an update start notification has been sent from the server on the mobile phone screen when the update start notification is made from the update server to the mobile phone set for update reservation. To do. This pictographic display informs the user that the scheduled date and time for the update has been reached, and prompts the user to stop using the mobile phone. Alternatively, even when the update cannot be performed, it is possible to notify that the update operation needs to be performed again. With this configuration, it is possible to prevent a state in which important software is not updated from continuing.
Further, according to the present invention, when a software update operation is being performed, a display indicating that the software is being updated is performed. With this configuration, the user can be careful not to perform an operation that may cause a serious obstacle to the mobile phone, such as turning off the power of the mobile phone during software update.

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 Processing flow chart of reservation update execution on mobile phone) Processing diagram of reservation update execution on mobile phone (1) Processing diagram of reservation update execution on mobile phone (2) Other processing flow diagram of update execution on mobile phone

Claims (6)

A mobile phone software reservation update method for downloading update software stored in an update server at a reservation date and time,
The mobile phone controller
Receiving a notification of reservation update start from the update server;
In response to the receiving step, displaying an update reservation and starting a reservation update ;
A first determination step of determining whether or not the mobile phone is in use;
If it is determined in the first determination step that the mobile phone is not in use, the update software is downloaded, the mobile phone software is updated with the downloaded update software, and the update reservation is indicated at the end of the update Erasing the display and ending the reservation update ; and
A step of measuring a predetermined time when the mobile phone is determined to be in use by the first determination step ;
A confirmation input detection step for detecting whether or not there is an input for confirming the update reservation by the user within the predetermined time, and that there is an input for confirmation within the predetermined time by the confirmation input detection step. The step of erasing the display indicating the update reservation and ending the reservation update when detected,
A second determination step for determining whether or not the use of the mobile phone is stopped within the predetermined time;
When it is determined in the second determination step that the use of the mobile phone is stopped within the predetermined time, the update software is downloaded, the mobile phone software is updated with the downloaded update software, and the update is completed. Sometimes erasing the display indicating the update reservation and ending the reservation update;
When it is determined in the second determination step that the use of the mobile phone has not been stopped within the predetermined time, the reservation update is terminated while the update reservation is displayed, and the use of the mobile phone is stopped. A method of reserving and updating mobile phone software that executes a step of waiting and setting a standby state . The reservation renewal method according to claim 1,
A step of detecting that the software update process has been started and displaying that the software is being updated; and
A reservation updating method including a step of detecting an end of software update work and erasing a display indicating that the software update work is in progress. The reservation renewal method according to claim 2,
The reservation update method, wherein the display indicating the update reservation and the display indicating that the software is being updated are the same display . A mobile phone that downloads update software stored in an update server at a reservation date and time,
Means for receiving notification of reservation update start from the update server;
Means for displaying the update reservation in response to the receiving step and starting the reservation ;
First determination means for determining whether or not the mobile phone is in use;
When it is determined by the first determination means that the mobile phone is not in use, the software is downloaded, the mobile phone software is updated with the downloaded update software, and the update reservation is displayed at the end of the update. To delete the reservation and end the reservation update ,
Means for measuring a predetermined time when the first determination means determines that the mobile phone is in use;
Confirmation input detection means for detecting whether or not there is an input for confirming the update reservation by the user within the predetermined time;
Means for erasing the display indicating the update reservation and ending the reservation update when the confirmation input detection means detects the input to be confirmed ; and
Second determination means for determining whether or not the use of the mobile phone is stopped within the predetermined time counting;
When it is determined by the second determination means that the use of the mobile phone has been stopped within the predetermined time, the update software is downloaded, and the display indicating the update reservation is deleted and the reservation update is ended at the end of the download. Means to
When it is determined by the second determination means that the use of the mobile phone has not been stopped within the predetermined time, the reservation update is terminated while the update reservation is displayed, and the use of the mobile phone is stopped. A mobile phone consisting of means to wait for The mobile phone according to claim 4,
Means for detecting that the software update process has been started and displaying that software update work is in progress;
A mobile phone having means for detecting the end of software update work and deleting a display indicating that software update work is in progress. The reservation update method according to claim 5,
The display showing the update reservation and the display showing that the software is being updated are the same display .

Images