KR20120117504A - Communication system and method for updating software thereof - Google Patents

Abstract

PURPOSE: A communication system and a software updating method in the communication system are provided to control a cycle which a terminal connects to a version update server, thereby allowing the terminal to confirm whether or not update by using a received version file. CONSTITUTION: An update managing server(120) disperses an update file for updating software, version information for explaining the update file, and a version file including cycle setting information in a dispersion update server(130). A terminal(140) receives the version file from the dispersion update server in an update determining cycle for determining whether or not update. The terminal determines a next update determining cycle by using the cycle setting information included in the version file. The terminal updates the corresponding software. [Reference numerals] (120) Update managing server; (123) DM server; (125) DL server; (130) Distribution update server; (140) Terminal; (210) Update determining period; (215,225) Version file request; (220,230) Version file transmission; (235) Version file check; (240) Determining the update determining period according to a version file; (245) Checking whether or not of update; (250) Update request; (255) Transmitting information for a update file to be updated; (260) Update file request; (265) Update file transmission; (270) Update; (275) Update result transmission

Description

COMMUNICATION SYSTEM AND METHOD FOR UPDATING SOFTWARE THEREOF}

The present invention relates to a communication system and a method for updating software in the communication system. In particular, a terminal using a distributed server determines whether to update, and receives a corresponding update file according to the determination result and relates to a method for updating software and a communication system for performing the same.

Firmware refers to a program that controls and manages hardware. Firmware is distinct from hardware in that it is a program, but it is a special program that distinguishes itself from general applications in that it controls and manages hardware. In other words, firmware has both software and hardware characteristics. Firmware is typically stored in ROM, or flash memory.

Typically, a terminal capable of performing various functions has built-in firmware for performing the corresponding function. The firmware is often used to mount a single small program rather than using a large program such as an operating system. Since such a firmware is a small program, it is frequently updated for the purpose of improving the error of the firmware itself, improving the performance of the system, or adding a function.

To this end, the terminal periodically checks whether there is a firmware update version in the update management server. However, as the number of users using terminals increases, the number of terminals also increases. That is, the number of terminals checking whether there is a firmware update version is increased. Therefore, the load on the update management server increases.

Therefore, the present invention distributes the update file to a plurality of servers, the terminal proposes a method for updating data through the distributed server.

In order to solve the above problems, in the communication system of the present invention, in the data update method, the update management server distributes an update file for updating software and a version file including version information and period setting information for describing the update file. Distributing to an update server, receiving a version file from the distributed update server in an update determination cycle for determining whether to update, and using the period setting information included in the version file Determining a next update determination cycle and updating the corresponding software.

In addition, in order to solve the above problems, the data update method in the terminal of the present invention comprises the steps of receiving a version file in the update determination cycle is set to determine whether the update, and using the cycle setting information of the received version file And a step of setting an update determination cycle and updating the corresponding software using the version information of the version file.

In order to solve the above problems, the data update terminal of the present invention uses a communication unit which receives a version file at an update determination cycle set to determine whether to update, and the period setting information of the version file received through the communication unit. And setting a next update determination period, and including a control unit for updating the corresponding software using the version information of the version file, and a storage unit for storing the updated software.

According to the present invention, even if an update is not required in the terminal, a load that may be generated on the update management server is reduced. In addition, the terminal may adjust the period of access to the version update server to check whether the update using the received version file.

1 is a diagram illustrating a configuration of an update performing communication system according to an embodiment of the present invention.
2 illustrates a signal flow for performing an update between communication systems according to an embodiment of the present invention.
3 is a diagram illustrating a method of transmitting an update file of an administrator terminal according to an embodiment of the present invention.
4 is a diagram illustrating period setting information of a version file according to an embodiment of the present invention;
5 is a diagram illustrating a configuration of a terminal according to an embodiment of the present invention.
6 is a diagram illustrating a data update method of a terminal according to an embodiment of the present invention.

The manager terminal provides the terminal with firmware, which is software supplied by a carrier or a terminal manufacturer. The manager terminal may update the software and provide the same to the terminal. To this end, the manager terminal transmits the corresponding update file to the update management server when the software is updated by the carrier or the terminal manufacturer. The manager terminal also configures a version file for describing the updated software.

The update file is a file for updating software installed in the terminal. More specifically, the update file contains data added or changed due to the update in the original software, which is called the delta value. Therefore, software update means to reflect the delta value to the software. The 'version file' includes version information on a version of the recently updated software and period setting information for calculating a period for checking whether the terminal is updated. Here, the version information is expressed as meta information such as a version value required for software update, a representative version value of the entire software, a version value of each part constituting the software, a model information of a terminal on which the software is to be installed, and a customer code.

The update management server stores the original of the update file and the version file transmitted from the administrator terminal. The update management server manages software updates by performing update communication with the terminal. In addition, the update management server may distribute the update file and the version file transmitted from the administrator terminal to the distributed update server. Accordingly, when a plurality of terminals periodically check for updates, the load of the update management server may be distributed.

The distributed update server stores the version file and the update file distributed from the update management server. In addition, when the update file is requested from the terminal, the distributed update server may deliver the requested update file to the terminal.

The term 'terminal' refers to an information processing apparatus capable of processing data transmitted and received from the outside. And the terminal includes all information processing apparatus capable of performing a specific software update, such as firmware. Herein, the terminal may include a router, an access point (AP), a portable terminal, and the like.

Hereinafter, the operation principle of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear. The following terms are defined in consideration of the functions of the present invention, and may be changed according to the intentions or customs of the user, the operator, and the like. Therefore, the definition should be based on the contents throughout this specification.

1 is a diagram illustrating a configuration of an update performing communication system according to an embodiment of the present invention.

Referring to FIG. 1, the communication system includes a manager terminal 110, an update management server 120, a distributed update server 130, and a terminal 140. The manager terminal 110 may provide the updated software to the terminal 140. To this end, the manager terminal 110 transmits the update file and the version file for the updated software to the update management server 120 in step 150. Then, the update management server 120 distributes and stores the update file and the version file in the distributed update server 130 in step 160.

In step 170, the terminal 140 periodically checks whether an update is made through the version file stored in the distributed update server 130. If the software needs to be updated, the terminal 140 performs a connection for update with the update management server 120 in step 180. When receiving information on which version of the update file is to be updated from the update management server 120, the terminal 140 transmits a message requesting the update file to the distributed update server 130. In operation 190, the distributed update server 130 transmits the corresponding update file to the terminal 140. Accordingly, the terminal 140 may update the software by using the received update file.

According to the present invention, the manager terminal 110 transmits the update file for the changed software and the corresponding version file to the update management server 120. The update management server 120 distributes the update file and the version file to the distributed update server 130. Then, the terminal 140 receives a version file from the distributed update server 130 in an update determination cycle for determining whether to update. The terminal 140 sets an update determination cycle for determining whether to update the next update using the received version file.

Next, the terminal 140 determines whether the version information of the version file and the version information of the currently stored software are the same. If the version information is the same, the terminal 140 does not perform the update and waits until the next update determination cycle. However, if the version information is not the same, the terminal 140 downloads the update file from the distributed update server 130 and performs the update. Therefore, the update determination cycle for accessing the distributed update server for determining whether to update each terminal varies. In addition, a plurality of terminals may be prevented from accessing the update management server 120 to determine whether to update.

2 is a diagram illustrating a signal flow for performing an update between communication systems according to an embodiment of the present invention.

Referring to FIG. 2, a signal flow for updating data between the update management server 120, the distributed update server 130, and the terminal 140 will be described. The update management server 120 may be composed of a device management (DM) server 123 and a download server (DL) 125. Here, the DM server 123 may perform a function of managing the terminal 140. Typically, the DM server 123 receives a software update request from the terminal 140, receives a software update result of the terminal 140, and performs a function of managing version information of the terminal 140. The DL server 125 stores the update file and the version file, and performs a function of transferring the update file and the version file to the terminal 140 as necessary.

When the update determination cycle is set in step 210, the terminal 140 transmits a message requesting a version file to the distributed update server 130 in step 215. The distributed update server 130 then delivers the requested version file to the terminal 140 in step 220. In this case, if the version file is not transmitted from the distributed update server 130, the terminal 140 requests the version file from the update management server 120 as in step 225. The update management server 120 then transmits the requested version file to the terminal 140 in step 230. Steps 225 to 230 may not be performed when the version file is successfully received from the distributed update server 130.

The terminal 140 checks the version file received in step 235. In addition, the terminal 140 determines the next update determination cycle using the version file identified in step 240. In more detail, the terminal 140 selects a next update determination cycle using the period setting information included in the version file.

Next, the terminal 140 checks the version information included in the version file in step 245 to confirm whether or not the software is updated. In other words, the terminal 140 determines whether the version corresponding to the current software and the version received through the version file are the same.

If the stored version is different from the received version, the terminal 140 transmits a message requesting the software update to the update management server 120 in step 250. Then, the update management server 120 checks the update file required for the update in the terminal 140. In operation 255, the update management server 120 transmits information on the update file to be downloaded to the terminal 140. In other words, the update management server 120 transmits information on what is a delta value required for updating in the terminal 140.

In step 260, the terminal 140 requests the update file to the distributed update server 130 based on the information received from the update management server 120. In operation 265, the distributed update server 130 transmits the corresponding update file to the terminal 140. Thereafter, the terminal 140 updates the software using the update file received in step 270. In operation 275, the terminal 140 transmits a message about the update result to the update management server 120. At this time, the update result includes information on whether the update is successful and the version of the currently updated software.

3 is a diagram illustrating a method of transmitting an update file of an administrator terminal according to an exemplary embodiment of the present invention.

Referring to FIG. 3, when the software is changed by the terminal manufacturer or the communication service provider in step 310, the manager terminal 110 stores a recent update file corresponding to the changed software. In addition, the manager terminal 110 changes the corresponding update information. Next, the manager terminal 110 reconstructs the version file including the cycle setting information together with the update information changed in step 320. In this case, the manager terminal 110 updates the version information corresponding to the version of the currently updated file and the period setting information for calculating the update determination cycle in the terminal 140 with the version file. Next, the manager terminal 110 transmits the version file and the update file to the update management server 120 in step 330. The update management server 120 then distributes the version file and the update file to the distributed update server 130.

4 is a diagram illustrating period setting information of a version file according to an embodiment of the present invention.

Referring to FIG. 4, the version file may be configured in the form of extensible markup language (xml). The version file may be composed of version information (Versioninfo) 410 and period setting information (polling) 450. In this case, the version information 410 includes information related to the Uniform Resource Locator (URL) 420, the firmware 430, and the last updated version 440. The period setting information 450 includes information on a period 453, a time 455, and a time range 457.

The URL 430 of the version information 410 is information corresponding to the address of the update management server 120 or the distributed update server 130 that stores the version file. That is, the URL 420 is information delivered in case the address of the server storing the version file is changed.

The terminal 140 stores the URL 420 corresponding to the server where the update file is located. When determining whether to update, the terminal 140 accesses a server corresponding to the stored URL. Therefore, when the URL 420 is changed, the manager terminal 110 transmits a version file in which the information about the changed URL 420 is updated, to the update management server 120. The update management server 120 then distributes the version file whose URL 420 has been changed to each distributed update server 130. When the version file is received from the distributed update server 130 in the update determination cycle, the terminal 140 checks the URL 420 of the version information 410. Next, the terminal 140 compares the checked URL 420 with the stored URL. If the URL 420 is changed, the terminal 140 may access the distributed update server 130 corresponding to the changed URL 420 and receive the version file again.

The firmware 430 of the version information 410 is information indicating what software is to be updated.

The latest updated version 440 of the version information 410 is the last version information of the update file. The terminal 140 may determine whether to update by comparing the version of the stored software with the latest update version 440 of the downloaded version file.

The period 453 of the period setting information 450 is configured on a date basis and is used by the terminal 140 to select a date for accessing the distributed update server 130 to determine whether to update the next. For example, assume that 7 is set as the period 453. Since the period 453 of the downloaded version file is set to 7, the terminal 140 randomly selects one day from seven days within the current date. In addition, the terminal 140 accesses the distributed update server 130 at the selected date, receives a version file, and determines whether to update using the received version file.

The time 455 of the period setting information 450 is used to calculate the time 455 to access the distributed update server 130 to determine whether to update the next time, based on a 24 hour period. In this case, the time 455 is based on the time of the region where the terminal 140 is located. For example, assume that the time 455 is set to 15 and the terminal 140 is located in Korea. Since the time 455 of the downloaded version file is set to 15, the terminal 140 connects to the distributed update server 130 at 3 pm Korea time, receives the version file, and updates using the received version file. Determine whether or not.

The time range 457 of the period setting information 450 is a range set based on the time 455 of the period setting information 450 to prevent the terminals 140 from simultaneously accessing the designated time 455. Is set. For example, assume that time range 457 is set to three hours. Since the time range 457 of the downloaded version file is set to 3 hours, the terminal 140 selects and updates an arbitrary time point within a 3 hour range based on the time 455 of the period setting information 450. Can be determined.

The manager terminal 110 constructs a version file including the version information 410 and the period setting information 450, and transmits the version file to the update management server 120. The update management server 120 distributes the corresponding version file to each distributed update server 130 and delivers it. Then, the terminal 140 receives a version file in connection with the distributed update server 130 in the update determination cycle. Next, the terminal 140 calculates an update determination period for determining whether the next update is performed using the period setting information 450 included in the version file. In more detail, the terminal 140 analyzes the received version file. The terminal 140 compares the period 453 of the version file with the stored period. If the period 453 is changed, the terminal 140 selects an arbitrary date within the changed period 453 based on the current date as a date for determining whether to update the next. On the other hand, if the period has not changed, the terminal 140 selects a date for determining whether to update the next date as much as the stored period based on the current date. Accordingly, dates for accessing the distributed update server 130 to the terminals 140 may be distributed.

If a date to determine whether to update next is selected, the terminal 140 selects a time 455 to receive a version file from the distributed update server 130. At this time, the terminal 140 checks the time 455 and the time range 457 of the version file, and selects an arbitrary time within the time range 457 set based on the time 455 of the version file. Accordingly, time for accessing the distributed update server 130 by the terminals 140 may be distributed.

The terminal 140 sets the selected date and time as the next update determination cycle through these processes. When the set update determination cycle arrives, the terminal 140 may receive a version file from the distributed update server 130, set the update determination cycle again, and perform an update. That is, the timing at which the terminal 140 determines the update may continue to change.

5 is a diagram illustrating a configuration of a terminal according to an embodiment of the present invention.

Referring to FIG. 5, the terminal 140 includes a communication unit 510, a control unit 520, and a storage unit 530.

The communication unit 510 may perform communication for update with the update management server under the control of the controller 520, or may be connected to the distributed update server. The communication unit 510 may receive a version file or an update file from the distributed update server under the control of the controller 520.

The controller 520 controls the overall operation and status of the components constituting the terminal 140. According to the present invention, when an update determination cycle for determining whether to update the software arrives, the controller 520 controls the communication unit 510 to request a version file from the distributed update server. When the version file is received, the controller 520 may check the version file, set a next update determination cycle, and perform a software update.

In order to set the update determination cycle, the controller 520 includes an update determination cycle checker 525. The update determination cycle checker 525 may select the next update determination cycle using cycle setting information included in the version file.

First, the update determination period checking unit 525 checks the contents of the period in the period setting information. The update determination period checking unit 525 determines whether the checked period and the previously stored period are the same. If the period is changed, the update determination period checker 525 randomly selects a date to check whether to update from among the dates in the changed period based on the current date.

The update determination cycle checker 525 randomly selects a time range based on the time to access the distributed update server on the selected date. The update determination period checking unit 525 checks the next update determination cycle through the selected date, time, and time range, and stores the checked update determination cycle.

When the next update determination cycle is set through the update determination cycle checker 525, the controller 520 determines whether to update the software. According to the determination result, the controller 520 receives the corresponding update file and updates the corresponding software using the received update file.

The storage unit 530 stores software and data generated for the operation of the components constituting the terminal 140 under the control of the controller 520. Here, the storage unit 530 stores period setting information regarding a URL where the version file is located and a period for accessing the distributed update server for updating. Here, the period setting information includes a period, date, and time for the terminal 140 to access the distributed update server. The storage unit 530 stores the updated software under the control of the control unit 520.

The terminal 140 having such a configuration receives a version file from the distributed update server at a set cycle to check whether there is a new version of software. In addition, the terminal 140 sets the next update determination cycle using the period setting information included in the received version file. Next, the terminal 140 checks the version information of the version file to determine whether there is a new version of the software. If there is no new version of the software, the terminal 140 waits until the update determination cycle. However, if a new version of the software exists, the terminal 140 communicates with the update management server for software update. When the information on the version of the file to be updated is received from the update management server, the terminal 140 downloads the update file of the version from the distributed update server. The terminal 140 updates the downloaded update file to the corresponding software.

6 is a diagram illustrating a data update method of a terminal according to an embodiment of the present invention.

Referring to FIG. 6, the terminal 140 performs a firmware update mode in step 610. The firmware update mode refers to a mode in which a mode in which a terminal is periodically upgraded by a user is selected or a standby state is performed. Next, the terminal 140 determines whether the current time corresponds to the update determination cycle in step 615.

If the update determination cycle corresponds, the terminal 140 requests a version file from the distributed update server in step 620. In operation 630, the terminal 140 determines whether a version file is received. If the version file is not received, the terminal 140 requests the version file to the update management server in step 635. The terminal 140 receives a version file from the update management server.

When the version file is received, the terminal 140 checks the version information and the version information of the version file received in step 640. In operation 645, the terminal 140 determines whether the URL of the version information is changed. That is, the terminal 140 determines whether the stored URL and the URL of the checked period setting information are the same. If the URL is changed, the terminal 140 returns to step 620 and requests a version file from the distributed update server corresponding to the changed URL.

On the other hand, if the URL has not changed, the terminal 140 checks the contents of the cycle from the cycle setting information in step 650. In addition, the terminal 140 determines whether the cycle checked in step 655 is changed. At this time, the terminal 140 determines whether the checked period and the previously stored period are the same. If the period is changed, the terminal 140 randomly selects a date to check whether to update from among the dates of the changed period based on the current date in step 660.

If the date to check whether the update is selected or the period is not changed in step 655, the terminal 140 is within the time range based on the time set based on the terminal 140 ID from the date to check whether the update in step 665. Randomly selects a time to connect to the distributed update server. In operation 670, the terminal 140 checks the next update determination cycle according to the selected date, time, and time range, and stores the checked update determination cycle.

Next, the terminal 140 determines whether the update should be performed by comparing the version included in the version file with the version of the current software in step 675. If the update is to be performed, the terminal 140 receives the update file in step 680 and updates the software using the received update file. The terminal 140 stores the updated software. At this time, the terminal 140 communicates with the update management server for the update. When a message regarding which version of the update file should be downloaded from the update management server is received, the terminal 140 requests the distributed update server for the version of the update file. When the update file is downloaded from the distributed update server, the terminal 140 may update the software by using the downloaded update file.

While the present invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not limited to the disclosed embodiments, but is capable of various modifications within the scope of the invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined by the scope of the appended claims, and equivalents thereof.

Claims (12)

In the data update method of the communication system,
The update management server distributes an update file for updating the software, a version file including version information and cycle setting information for describing the update file, to a distributed update server,
Receiving, by the terminal, the version file from the distributed update server in an update determination cycle for determining whether to update;
And determining, by the terminal, a next update determination cycle using the period setting information included in the version file, and updating the corresponding software. The method of claim 1, wherein the period setting information is
And at least one of a period, a time, and a time range. The method of claim 1, wherein the receiving of the version file comprises:
Checking a URL (Uniform Resource Locator) of the received version file;
Requesting the version file from the update management server if the URL and the stored URL are not the same;
Receiving the version file from the update management server. The method of claim 1, wherein the updating of the software is
Comparing the version information with the stored version information;
And if the version information is not the same as the stored version information, updating the corresponding software. In the data update method of the terminal,
Receiving a version file at an update determination cycle set to determine whether to update;
Setting a next update determination cycle using cycle setting information of the received version file;
And updating the corresponding software using the version information of the version file. The method of claim 5, wherein the period setting information is
And at least one of a period, a time, and a time range. The method of claim 5, wherein the receiving of the version file comprises:
Checking a URL (Uniform Resource Locator) of the received version file;
If the URL and the stored URL are not the same, requesting the version file from an update management server;
Receiving the version file from the update management server. 6. The process of claim 5, wherein updating the software is
Comparing the version information with the stored version information;
And if the version information is not the same as the stored version information, updating the corresponding software. A communication unit which receives a version file at an update determination cycle set to determine whether to update;
A control unit for setting a next update determination cycle using period setting information of the version file received through the communication unit, and updating the corresponding software using version information of the version file;
And a storage unit for storing the updated software. The method of claim 9, wherein the period setting information is
And at least one of a period, a time, and a time range. 10. The apparatus of claim 9, wherein the control unit
Check the Uniform Resource Locator (URL) of the received version file, and if the URL and the stored URL are not the same, control the communication unit to request the version file from the update management server, and the version file from the update management server. And a data update terminal. 10. The apparatus of claim 9, wherein the control unit
Comparing the version information with the stored version information, and if the version information is not the same as the stored version information, updating the corresponding software.

Images