Patent Grant
9442711
The present application claims priority to and incorporates by reference the entire contents of Japanese Patent Application No. 2010-208531 filed in Japan on Sep. 16, 2010 and Japanese Patent Application No. 2011-146599 filed in Japan on Jun. 30, 2011.
1. Field of the Invention
The present invention relates to a communication device, an update method, and a computer program product.
2. Description of the Related Art
In recent years, with an increasing demand to cut back on expenses and time spent for business trips, call terminals for performing a teleconference through a communication network such as the Internet are widely prevailed. Each call terminal designates the call terminal of the destination to start a call, and hence transmission and reception of image data and voice data are performed. In this way, the teleconference is performed.
In each call terminal, firmware (a computer program) is regularly updated to improve call confidentiality and operability. A method of updating a computer program in the call terminal is disclosed in U.S. Pat. No. 6,847,403. U.S. Pat. No. 6,847,403 discloses a technology for automatically updating a computer program according to update information obtained by gaining access to an update server, without requiring an operation from a user.
However, in the call terminal according to the related art, when there is a computer program that needs to be updated in the call terminal according to the update information obtained by gaining access to the update server, an automatic update of the computer program starts. For this reason, the user cannot select time to update the computer program. Therefore, in the call terminal according to the related art, since updating the computer program may take a certain length of time, the demand of the user who wants to put off the update and to perform the teleconference first.
It is an object of the present invention to at least partially solve the problems in the conventional technology.
According to an aspect of the present invention, there is provided a communication device including: a receiving unit that receives metainformation indicating an update from an update information providing device to provide information related to the update; a determining unit that determines, on the basis of the received metainformation, whether an update needed for the communication device exists; a notifying unit that notifies, when the update exists, a user of existence of the update; an operation unit that receives, when the update exists, a selection operation as to whether the update is to be executed from the user; and an update processing unit that executes, when the selection operation to execute the update is received by the operation unit, the update on the basis of the received metainformation.
According to another aspect of the present invention, there is provided an update method that is executed by a communication device. The update method includes receiving metainformation indicating an update from an update information providing device to provide information related to the update; determining, on the basis of the received metainformation, whether an update needed for the communication device exists; notifying a user of existence of the update when the update exists; receiving, from the user, a selection operation as to whether the update is to be executed when the update exists; and executing, when the selection operation to execute the update is received at the receiving, the update on the basis of the received metainformation.
According to still another aspect of the present invention, there is provided a computer program product including a non-transitory computer-readable medium having computer-readable program codes recorded in the medium for causing a computer to execute: receiving metainformation indicating an update from an update information providing device to provide information related to the update; determining, on the basis of the received metainformation, whether an update needed for the computer exists; notifying a user of existence of the update when the update exists; receiving, from the user, a selection operation as to whether the update is to be executed when the update exists; and executing, when the selection operation to execute the update is received at the receiving, the update on the basis of the received metainformation.
The above and other objects, features, advantages and technical and industrial significance of this invention will be better understood by reading the following detailed description of presently preferred embodiments of the invention, when considered in connection with the accompanying drawings.
Hereinafter, embodiments of a method and a computer program that can improve convenience of a user will be described in detail with reference to the accompanying drawings.
First Embodiment
Specifically, the remote communication management server 50 manages communication addresses of the call terminals 11aa to 11ac, 11ba to 11bc, 11ca to 11cc, and 11da to 11dc and the repeaters 30a, 30b, 30c, and 30d and information of the call terminals relayed by the repeaters 30a, 30b, 30c, and 30d and call statuses of the call terminals. For example, when the call terminal 11aa calls the call terminal 11ca, the remote communication management server 50 requests the repeater 30a to relay a call to the call terminal 11ca. The repeater 30a notifies the remote communication management server 50 that a call of the call terminal 11aa starts, and acquires, from the remote communication management server 50, the communication address of the repeater 30c to relay a call to the call terminal 11ca. Next, the repeater 30a requests the repeater 30c to relay a call to the call terminal 11ca and the repeater 30c starts a communication session with the call terminal 11ca. Then, the repeater 30c notifies the remote communication management server 50 of the start of the communication session with the call terminal 11ca.
In this way, a call between the call terminal 11aa and the call terminal 11ca is started through the repeaters 30a and 30c. The remote communication management server 50 manages a call between the call terminal 11aa and the call terminal 11ca. For example, when the call terminal flab inquires of the remote communication management server 50 about a call status of the call terminal 11aa or the call terminal 11ca, the remote communication management server 50 returns that the call terminal 11aa or the call terminal 11ca are on-line and calling each other.
In the description below, reference numerals that are obtained by removing alphanumerical characters assigned after the numerical characters are used when an arbitrary device among the devices of the same type is described. For example, the call terminals 11aa to 11ac, 11ba to 11bc, 11ca to 11cc, and 11da to 11dc are abbreviated as a call terminal 11. The repeaters 30a to 30d are abbreviated as a repeater 30.
The update server 60 is an update information providing device that manages information related to update of the computer program or various setting information of the call terminal 11 and provides the information according to a request by the call terminal 11. Examples of the information that is related to the update include data files of all the versions, from the past to the latest, of the computer programs or the various setting information of the call terminal 11 and metadata (metainformation) where contents of the update for each version are described. The data of all of the versions is managed as the information related to the update by the update server 60 because update timing depends on each call terminal 11.
For example, it may be sufficient for the call terminal 11 that frequently executes the update to perform the update with a latest version. However, the call terminal 11 that has a long update interval may execute the update after several times of updating has been done for the versions. In this case, instead of executing directly the update with the latest version, the update may be first performed with an older version on which the latest version is dependent. As such, since the call terminal 11 may first execute the update with the older version on which the latest version is dependent, the update server 60 manages data of all of the versions as the information related to the update.
Note that there are two kinds of updates: a normal update and a compulsory update. The normal update is an update that is executed for the purpose of removing obstacles, such as bug fixing, or function addition.
The compulsory update is an update that is compulsorily executed in association with a change of a device or a function to which the current functions of the call terminal 11 cannot respond. For example, there may be a change that can be executed, on the side of the repeater 30, in the data format or the video codec of a voice or an image that is transmitted and received at the time of calling or a version-up of the repeater 30 related to an update of an encoder. Further, a communication protocol with the repeater 30 may be changed. The changes listed above may cause a change in the structure of the voice, the image, and the video, a communication method with the repeater 30 associated to the change in the communication protocol, or the function of the repeater 30. Accordingly, a call that is an original function of the call terminal 11 may not be realized with the call terminal 11 before an update. In such an occasion, therefore, the compulsory update is executed on the call terminal 11 to match the version of the repeater 30 after the update.
When a problem occurs in the security on the side of the repeater 30 such as a security hole that is found in the repeater 30, for example, an update in response to the security hole may be executed on the side of the repeater 30. In this case again, since the call terminal 11 before the update may not execute even a call, the compulsory update is executed on the call terminal 11so as to match the version of a computer program that copes with the security hole on the side of the repeater 30.
Next, the hardware configuration of the call terminal 11 will be described.
The CPU 101 controls an operation of the call terminal 11 by uncompressing a computer program 104 having been stored in the ROM 102 or the storage unit 105 to the RAM 103 and sequentially executing the computer program 104. The storage unit 105 is a hard disk drive (HDD) or a solid state drive (SSD) and stores data to be readable/writable. Specifically, the storage unit 105 stores the computer program 104 to be executed by the CPU 101 or the various setting information thereof. In the updating, the computer program 104 or the various setting information that is stored in the storage unit 105 is updated.
The media drive 107 is a drive device that performs a read/write operation on media 106 such as an optical disk. The operation unit 108 is a keyboard, various operation keys, and a touch panel staked on a display 13 and receives an operation input by the user. The network I/F 111 is an interface that is connected to the communication network 2 and performs data communication. The image sensor element I/F 112 is an interface that is connected to a camera 12 that is a digital camera and acquires an image captured by the camera 12. The voice input/output I/F 113 is an interface that is connected to a microphone 14 and a speaker 15 and performs a voice input by the microphone 14 or a voice output by the speaker 15. The display I/F 114 is an interface that is connected to the display 13 such as a liquid crystal display (LCD) and outputs display data to the display 13.
In this embodiment, the display 13 is used. However, instead of the display 13, another display apparatus such as a projector may be connected to configure the embodiment.
The call terminal 11 outputs, under control of the CPU 101 executing the computer program 104, an image acquired by using the camera 12 or a voice input from the microphone 14 to the repeater 30 through the network I/F 111 during the calling with another call terminal. The call terminal 11 outputs, by the speaker 15, a voice that has been transmitted from another terminal, relayed by the repeater 30 and input through the network I/F 111, and displays an image from another call terminal on the display 13. Thereby, the call terminal 11 realizes a call with another call terminal through images and voices, that is so-called a teleconference.
Next, the hardware configuration of the repeater 30, the remote communication management server 50, and the update server 60 will be described.
The CPU 201 uncompresses a computer program stored in the ROM 202 or the storage unit 204 to the RAM 203, sequentially executes the computer program, and performs a central control of an operation of the self device. The storage unit 204 is an HDD or an SSD and stores data to be readable/writable. For example, in the update server 60, information that is related to an update is stored in the storage unit 204.
The display 205 is, for example, an LCD. The network I/F 206 is an interface that is connected to the communication network 2 and performs data communication. The keyboard 207 and the mouse 208 receive an operation input by the user. The media drive 209 is a drive device, such as an optical disk, to perform a read/write operation on media 210. The CD-ROM drive 211 is a drive device that performs a read operation on a CD-ROM 213. For example, in the update server 60, latest information that is related to an update is provided by the media 210 or the CD-ROM 213 and is stored in the storage unit 204.
Next, the functional configuration of the call terminal 11 and the update server 60 that is realized by executing a computer program by the CPU 101 or the CPU 201 will be described.
The transmitter/receiver 1101 exchanges data with the update server 60 through the communication network 2. Specifically, the transmitter/receiver 1101 starts a communication session using a predetermined communication protocol, on the basis of the communication address of the update server 60 preset in the setting information of the storage unit 105 or the communication address of the update server 60 acquired by an inquiry to the remote communication management server 50, and exchanges data with the update server 60. By exchanging the data with the update server 60, the transmitter/receiver 1101 acquires information related to an update that is managed by the update server 60.
The user interface unit 1102 is an interface that controls a voice output by the speaker 15, a display screen of the display 13, and an operation input from the user through the operation unit 108 and controls information transfer between the user and the call terminal 11. Specifically, the user interface unit 1102 includes a user notifying unit 1104 that notifies the user of various types of information through the voice output by the speaker 15 and the display screen of the display 13 and an operation-input receiving unit 1105 that receives an operation input by the user through the operation unit 108.
The update unit 1103 functions as a determining unit and an update processing unit and updates the computer program 104 or various setting information stored in the storage unit 105, on the basis of the information related to an update acquired from the update server 60 by the transmitter/receiver 1101. The update that is executed by the update unit 1103 will be described in detail in the explanation of an update process (step S16).
The transmitter/receiver 601 exchanges data with the call terminal 11 through the communication network 2. Specifically, the transmitter/receiver 601 starts a communication session using a predetermined communication protocol in response to a request from the call terminal 11 through the communication network 2 and exchanges the data with the call terminal 11.
The update data providing unit 602 provides information related to an update managed by the update server 60 to the call terminal 11 in response to a request from the call terminal 11 transmitting/receiving data by the transmitter/receiver 601.
Here, an operation of the call terminal 11 that is executed by the functional configuration described above will be described in detail.
As illustrated in
The update unit 1103 starts to confirm the update of the self device, at the time of starting after turning on the power supply at step S1 (step S3). In the description below, the update of the computer program is exemplified. However, it is needless to say that the various setting information is also updated in the same way.
If the confirmation of the update starts, the update unit 1103 requests, via the transmitter/receiver 1101, the update server 60 to provide metadata of a computer program of the latest version (step S4), and acquires the metadata provide by the update data providing unit 602 in response to the request (step S5).
Here, the details of the metadata will be described below.
In the item “version”, a version number such as “1.0.1” is written. In the item “dependency”, a version number indicating other version, such as “1.0.0”, that has mutual dependency with “1.0.1”, is written. Therefore, a version that has dependency with the current version can be traced by checking the version number written in the data item of the “dependency”. In the item “description”, the details of the version such as “It is sample data.” is written. In the item “files”, a list of computer programs (data files) becoming objects of the update managed by the update server 60 and storage places thereof or a checksum of the data files is written. Therefore, the update unit 1103 acquires the data files by the transmitter/receiver 1101, on the basis of contents written in the data items of the “files”. As a result, the update unit 1103 can update the version that is written in the metadata. In the “scriptname”, a name of a script that is executed when an update is executed is written. In the “require_reboot”, a flag (“true” or “false”) indicating whether the device should reboot after executing the update is written. In the “force_update”, a flag (“true” or “false”) indicating whether the update is a compulsory update is written.
The update of the computer program 104 is associated with control of the devices such as the network I/F 111, the image sensor element I/F 112, the voice input/output I/F 113, and the display I/F 114. In the update associated with the control of the devices, the reboot is needed after the update. Therefore, “true” is written in the item “require_reboot”. As described above, the update of the computer program 104 include the normal update and the compulsory update. When the compulsory update should be executed, “true” is written in the “force_update”.
Next, the update unit 1103 confirms whether a version dependency exists, on the basis of contents described in the data item of the “dependency” of the acquired metadata (step S6). As illustrated in
Next, the update unit 1103 determines whether the version dependency exists as a result of the confirmation at step S6 (step S7). When the version dependency exists (Yes at step S7), the update unit 1103 requests the update server 60 to provide the metadata of the computer program on the version dependency by the transmitter/receiver 1101 (step S8), acquires the metadata on the version dependency provided by the update data providing unit 602 in response to the request (step S9), and returns the process to step S6. Therefore, the update unit 1103 sequentially traces versions with which the latest version has dependency and acquires metadata that is related to the versions.
Next, the update unit 1103 compares the version number written in the “version” of the metadata of the latest version and the version number of the computer program 104 stored in the storage unit 105 included in the self device and determines whether the update of the self device exists (that is, whether an update has been completed) (step S10). Specifically, when the version number of the latest version matches the version number of the computer program 104, because the version of the computer program 104 is the latest version, it is determined that an update needed for the self device does not exist (that is, the update has been completed). When the version number of the latest version does not match the version number of the computer program 104, because the version of the computer program 104 is an old version, it is determined that an update needed for the self device exists (that is, the update has not been completed yet). When the update needed for the self device does not exist (No at step S10), because the update does not need to be executed, execution of the normal operation is continued (step S19).
When the update of the self device exists (Yes at step S10), the update unit 1103 notifies the user interface unit 1102 of information related to the update (step S11). Specifically, the update unit 1103 notifies the user interface unit 1102 of the data items other than the data items that do not need to be notified to the user, such as the “files” or the “scriptname”, among the metadata of the latest version and the version dependency of the latest version, as the information related to the update.
The user notifying unit 1104 of the user interface unit 1102 displays existence of the update needed for the self device on the starting screen of the display 13, on the basis of the information related to the update notified by the update unit 1103 at step S11, and notifies the user of the existence of the update (step S12).
Here, the details of the starting screen will be described below.
The user notifying unit 1104 displays, when “true” is written in the “force_update” among the data items included as the information related to the update, information indicating that the update existing on the self device is the compulsory update on the starting screen G1 and notifies the user of the information. Specifically, the information indicating that the update is the compulsory update may be displayed on the status screen G12 and the list displayed on the main screen G11 may be grayed out to notify the user that an operation other than the update is invalid.
When an operation instruction to perform various setting such as an update is received by the operation-input receiving unit 1105 of the user interface unit 1102 according to the notification to the user at step S12, the user interface unit 1102 displays a setting screen on the display 13 (step S13).
When the selection operation of the setting button G26 is executed at step S13, the user interface unit 1102 displays a confirmation screen to confirm execution of the update on the display 13 (step S14).
Returning to
When the operation button G34 to cancel the execution of the update processes is selected and the selection of the operation button G35 is not performed (No at step S15), the update unit 1103 determines whether the compulsory update is included in the update processes that have not been executed, on the basis of the described content in the item “force_update” included in the acquired metadata (step S17). When the compulsory update is included (Yes at step S17), the update unit 1103 executes an end process to end the process of the self device (step S18) and turns off the power supply to the device. As such, when the compulsory update is not executed, because even a call cannot be executed, the power supply of the device is turned off to prevent in advance an unnecessary operation from being executed. In contrast, when the compulsory update is not included (No at step S17), because the update unit 1103 does not execute the update at the current time, execution of a normal operation is continued. Thereby, the user may perform the call with more preference to the update.
That is, in the call terminal 11, when the update of the self device exists, existence of the update is notified to the user by the user notifying unit 1104 of the user interface unit 1102. The call terminal 11 receives a selection operation as to whether the update is to be executed from the user using the operation-input receiving unit 1105. When the selection operation to execute the update is performed, an update process is executed by the update unit 1103. Therefore, the user can selectively execute the update of the call terminal 11 when the update exists in the self device.
Here, the details of the update process (step S16) will be described below.
As illustrated in
Next, the update unit 1103 acquires a file list of computer programs being objects of the update and a checksum of the files from the item “files” included in the acquired metadata (step S101). When plural versions of metadata in a dependency relation are acquired, the processes at step S101 to S106 are executed in the order of the version numbers.
Next, the update unit 1103 acquires a file containing the file list acquired at step S101 (step S102) and confirms the checksum of the acquired files (step S103). Then, the update unit 1103 notifies the user interface unit 1102 of a progress status of the update (step S104). The notification of the progress status is used to notify the user of the file, among a plurality of files included in the file list, up to which the processes at steps S102 and S103 have ended. When an update is performed for a plurality of versions among which the version dependency exists, the notification may be performed on up to which version the update has been executed already. The user interface unit 1102 displays the notified progress status of the update on a screen of the display 13 to notify the user of the progress status of the update.
In addition, remaining time for the update or a current line speed may be displayed in real time on the update screen G4. In this case, the user can clearly grasp the details of the progress status of the update.
Next, the update unit 1103 determines whether an error occurs (step S105). When the error occurs (Yes at step S105), the process at steps S101 to S106 are skipped and the process sequence proceeds to step S107. At step S105, in addition to the error (for example, difference of the checksum at step S103) that occurs due to some factor during the execution of the update, it is determined that an error occurs even when the update is stopped by the operation of the operation button G42 on the update screen G4 or the version resulted from the update executed at steps S102 and S103 needs to reboot the self device. Therefore, when the update is executed consecutively in order of the version numbers, the processes at steps S101 to S106 are skipped at a step where the update of the version that needs to reboot the self device is executed.
When the error does not occur (No at step S105), the update unit 1103 determines whether the update has been completed for all the versions related to the acquired metadata (step S106). When the update has not been completed for all the versions (No at step S106), the process returns to step S101 and the update process continues. When the update has been completed for all the versions (Yes at step S106), the processes at steps S101 to S106 are skipped and the process sequence proceeds to step S107.
At step S107, the update unit 1103 notifies the user interface unit 1102 of the results of the update at steps S106 and S107. The user interface unit 1102 displays the notified results of the update on the screen of the display 13 to notify the user of the results of the update.
Next, the update unit 1103 determines whether the reboot is needed, on the basis of the written contents of the “require_reboot” included in the metadata having been written in executing the update at steps S101 to S106 (step S108). When the reboot is not needed (No at step S108), the update unit 1103 ends the update process without performing the reboot (step S109). When the reboot is needed (Yes at step S108), the update unit 1103 reboots the self device and ends the process (step S110). As such, when an update requiring the reboot is executed, the reboot is automatically executed after the update, without an operation by the user.
As such, in this embodiment, when an update to be executed in the call terminal 11 exists, the user can select execution of the update, thereby the user-friendliness can be improved.
Modification
In the embodiment described above, when an update exists, a selection operation as to whether the update is to be executed is received by the user, irrespective of whether the update is compulsory. When the update is not executed, the process of the self device ends.
However, when an update exists and is compulsory, the update may be executed without notifying the user of existence of the update. Specifically, the process at step S17 illustrated in
Since a call may not be executed in a situation where the compulsory update is not executed, the update is executed with the highest priority. Therefore, in this case, the update is preferably executed without requiring confirmation of the user.
(Second Embodiment)
The update unit 1403 executes an update of the computer program 104 or various setting information stored in the storage unit 105 on the basis of the update-related information acquired from the transmitter/receiver 1101 through the update server 60. An execution process of the compulsory update performed by the update unit 1403 according to the present embodiment is different from that of the first embodiment. That is, when the compulsory update exists, the update unit 1403 according to this embodiment changes a screen to a compulsory update screen to let the user select, on the compulsory update screen, any one of execution of the compulsory update, change to a setting screen, and turning off of the power supply. Further, the meanings and the objects of the normal update and the compulsory update are the same as those of the first embodiment. The structure and the contents of the metadata are also the same as those of the first embodiment.
The update server 60 includes a transmitter/receiver 601 and an update data providing unit 602 as main components and the configuration and the function thereof are the same as those of the first embodiment.
Next, the exterior configuration of the call terminal 1411 will be described.
On a top surface of the casing 1100 on a right wall surface 1130 side, an operation panel 1150 is formed. On the operation panel 1150, a plurality of operation buttons 108a to 108e functioning as the operation unit 108, a power switch 109, an alarm lamp 119, and a voice output surface 1151 to output a voice from an incorporated speaker are formed.
On a left wall surface 1140 side of the casing 1100, a storage portion 1160 that functions as a concave portion to store the arm 1200 and the camera housing 1300 is formed. To the casing 1100 of the call terminal 1411, the display 13 is connected through a cable.
The arm 1200 is attached to the casing 1100 through a torque hinge 1210 so that the arm 1200 can rotate in an up-down direction, in a range of a tilt angle θ1, 135 degrees, with respect to the casing 1100.
The camera 12 is incorporated in the camera housing 1300 and the camera can capture images of the user, a document, and a room. In the camera housing 1300, a torque hinge 1310 is formed. The camera housing 1300 is attached to the arm 1200 through the torque hinge 1310. The camera housing 1300 is configured to be rotatable in horizontal and vertical directions, in the range of a panning angle θ2 within ±180 degrees with respect to the state illustrated in
Next, an operation of the call terminal 1411 according to this embodiment having the above-described configuration will be described in detail.
When it is determined that the version dependency does not exist at step S7 (No at step S1501), the update unit 1403 determines whether the “force_update” of the acquired metadata is set to “true” and determines whether the update is the compulsory update (step S1501).
When the “force_update” of the acquired metadata is not set to “true” and the update is a normal update (No at step S1501), similarly to the first embodiment, the update unit 1403 confirms the existence of the update (normal update) (step S10). The following processes are executed in the same way as the first embodiment. However, when the normal update is not executed at step S15 (No at step S15), because it has been confirmed whether the compulsory update exists at step S1501, unlikely to the first embodiment, the process ends without confirming whether the compulsory update exists (step S18).
The processes (steps S1 to S4) that are executed by the user interface unit 1102 and the starting screen, the setting screen, and the confirmation screen that are displayed during the processes are the same as those of the first embodiment.
At step S1501, when the “force_update” of the metadata is set to “true” (Yes at step S1501), the update unit 1403 notifies the user interface unit 1102 of the information related to the compulsory update (step S1701). Specifically, similarly to the first embodiment, the update unit 1403 notifies the user interface unit 1102 of the data items other than the data items that do not need to be notified to the user, such as the “files” or the “scriptname”, in the metadata of the latest version and the version on which the latest version depends, as the information related to the update.
The user notifying unit 1104 of the user interface unit 1102 displays existence of the update needed for the self device on the starting screen of the display 13, on the basis of the information related to the update notified by the update unit 1403 at step S1602, and notifies the user of the existence of the update (step S1602). The contents of the starting screen are the same as those of the first embodiment.
If the information is notified to the user at step S1701, the user interface unit 1102 displays the confirmation screen to confirm the execution of the update on the display 13 (step S1603). The setting screen of the update screen in the first embodiment is not displayed.
In this case, only the update button G75 is displayed as a button displayed on the confirmation screen G70 of the compulsory update and the operation button G34 for the cancellation that is displayed on the confirmation screen G3 of the normal update is not displayed. This is because the update needs to be executed in the case of the compulsory update. However, a screen may be changed to a setting screen by the operation button corresponding to the menu key of the operation unit 108 or the power supply may be turned off by pressing the power switch 109.
Returning to
Meanwhile, at step S1702, when the operation button G75 is not pressed and the operation button of the operation unit 108 is pressed (No at step S1702), display of the setting screen or power shutdown is performed according to the pressed operation button (step S1705).
Next, the update process that is executed at steps S16 and S1703 will be described in detail.
The processes (steps S101 to S105) from the acquisition of the file list and the checksum from the acquired metadata to the determination of the occurrence of the error are the same as those of the first embodiment.
When the error does not occur at step S105 (No at step S105), the update unit 1403 determines whether “true” is set to the item “require_reboot” included in the metadata and determines whether the reboot is needed (step S1801).
In this embodiment, the item “require_reboot” of the metadata indicates whether the reboot is needed before executing an update following the previously executed update. During the update process illustrated in
When “true” is set to the item “require_reboot” and the reboot is needed (Yes at step S1801), the reboot of the call terminal 1411 is performed (step S1802).
The update unit 1403 determines whether the update for all the versions has been completed (step S106). When the update for all the versions has not been completed yet (No at step S106), the process proceeds to step S101 and continues to execute the update process. When the update for all the versions has been completed (Yes at step S106), the update unit 1403 notifies the user interface unit 1102 of the update result at steps S106 and S107 (step S107). The user interface unit 1102 displays the notified result of the update on a screen of the display 13 and notifies the user of the result of the update.
As the result of the normal update, the screen of
If the update unit 1403 notifies the user interface unit 1102 of the update result, the update unit 1403 ends the update process (step S109). That is, in this embodiment, since the rebooting process in the course of the update processes of one version (steps S101 to S105, S180, and S1802) is executed, the reboot is not executed after the update result is notified, unlikely to the first embodiment.
As such, in this embodiment, in addition to the first embodiment, when the call terminal 1411 needs to execute the compulsory update, because the call terminal 1411 executes the compulsory update without allowing the user to select the cancellation of the update, the original function of the call terminal 1411 can be avoided from being not capable of executing due to an update of the device other than the call terminal 1411, such as the repeater 30.
In the first and second embodiments, the remote communication management server 50 and the update server 60 are configured to be separated from each other. However, the present invention is not limited thereto. For example, a server device may be provided and the server device may have a function of the remote communication management server 50 and a function of the update server 60.
According to the present invention, when an update to be executed exists in a communication device, a user can select whether or not to execute the update. This improves the convenience of the user.
Although the invention has been described with respect to specific embodiments for a complete and clear disclosure, the appended claims are not to be thus limited but are to be construed as embodying all modifications and alternative constructions that may occur to one skilled in the art that fairly fall within the basic teaching herein set forth.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2010-208531 | Sep 2010 | JP | national |
| 2011-146599 | Jun 2011 | JP | national |
| Number | Name | Date | Kind |
|---|---|---|---|
| 6847403 | Forsberg, Jr. et al. | Jan 2005 | B1 |
| 6976251 | Meyerson | Dec 2005 | B2 |
| 7620948 | Rowe et al. | Nov 2009 | B1 |
| 8375385 | Harel et al. | Feb 2013 | B1 |
| 20010020295 | Satoh | Sep 2001 | A1 |
| 20040187103 | Wickham et al. | Sep 2004 | A1 |
| 20040230968 | Masunaga | Nov 2004 | A1 |
| 20040255291 | Sierer et al. | Dec 2004 | A1 |
| 20060031828 | Won et al. | Feb 2006 | A1 |
| 20060069836 | Seo et al. | Mar 2006 | A1 |
| 20080256525 | Ellsworth et al. | Oct 2008 | A1 |
| 20090217375 | Joosten et al. | Aug 2009 | A1 |
| 20090235242 | Kawaguchi | Sep 2009 | A1 |
| 20100011060 | Hilterbrand et al. | Jan 2010 | A1 |
| 20100153941 | Borissov et al. | Jun 2010 | A1 |
| 20110088026 | Swann | Apr 2011 | A1 |
| 20110173598 | Cassapakis et al. | Jul 2011 | A1 |
| 20110289499 | Haubold et al. | Nov 2011 | A1 |
| 20120210313 | Cooley et al. | Aug 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 10-240539 | Sep 1998 | JP |
| 2003-99264 | Apr 2003 | JP |
| 2005-228200 | Aug 2005 | JP |
| 2006-178881 | Jul 2006 | JP |
| 2008-90723 | Apr 2008 | JP |
| 2008-186147 | Aug 2008 | JP |
| 2009-211269 | Sep 2009 | JP |
| Entry |
|---|
| Office Action mailed Jan. 27, 2015, in Japanese Patent Application No. 2011-146599. |
| Number | Date | Country | |
|---|---|---|---|
| 20120072895 A1 | Mar 2012 | US |
