Server apparatus and method for controlling firmware update via wireless communication

Abstract

To efficiently update a plurality of firmware in a terminal including a dedicated module for radio communication.SOLUTION: The method includes: receiving a firmware update request from the terminal; and performing a firmware update process based on dependency information between a plurality of pieces of second firmware for controlling a communication module of the terminal and a plurality of pieces of first firmware for controlling an application module of the terminal. In the step of performing update processing, when a difference between a first version representing a group to which the updated first firmware belongs and a second version representing a group to which the installed first firmware belongs is 2 or more, the first firmware installed in the terminal is updated to the latest first firmware included in a group of a third version larger than the second version by 1.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present disclosure relates to a server apparatus and method for controlling firmware updates of a communication device via wireless communication. [Background technology]

[0002] Conventionally, configurations for controlling firmware updates via wireless communication have been known. For example, Japanese Patent Application Laid-Open Publication No. 2019-200620 (Patent Document 1) discloses a configuration that can provide update firmware to a slave device in a group of wireless communication devices that make up a field area network (FAN) via firmware over the air (FOTA). Note that an FAN is a system that collects meter reading data or controls meters via a network formed by multiple smart meters in a field. Also, FOTA is a technology that performs firmware updates wirelessly. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-200620 Summary of the Invention [Problem to be solved by the invention]

[0004] In wireless communication via a telecommunications carrier's base station, a terminal device is required to function as an interface between the base station and a user network (for example, a local area network (LAN) installed on the premises or site where the user is located). The functions of the terminal device may include not only the function of realizing wireless communication with the base station, but also various functions other than wireless communication. The terminal device may be configured with a general-purpose module that realizes these functions, or with a dedicated module (communication module) for wireless communication and a control module that comprehensively realizes the functions of the terminal device. From the perspective of distributing the processing load in the terminal device, the latter configuration of the terminal device is preferable.

[0005] For the firmware of the communication module and the firmware of the control module to operate normally, the two versions must be consistent in light of the dependency (compatibility) between the two versions. Therefore, the update process for both must be designed so that the two versions are consistent after the update (after either a successful update or an unsuccessful update). Note that when the two versions are consistent, the control module firmware can call the communication function of the firmware of the communication module. Firmware is software that is pre-installed in a device that includes hardware, including a processor, in order to control that hardware.

[0006] Although it is possible to avoid inconsistencies between the two firmware versions after updating by simply updating each firmware version one by one to the target version, if the firmware has not been updated for a long time and there are multiple versions between the current version and the target version, this simple update process may require repeated updates to versions that are only temporarily stored in the terminal device and restarts, which may lengthen the time required for the firmware update to an extent that is unacceptable to the user.

[0007] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to improve the efficiency of updating multiple firmware in a terminal device equipped with a dedicated module for wireless communication. [Means for solving the problem]

[0008] The server device disclosed herein is a server device for controlling firmware updates in a terminal device that connects a base station and a user network via wireless communication. The terminal device includes an application module and a communication module. The application module executes first firmware to realize the functions of the terminal device. The communication module executes second firmware and performs wireless communication under the control of the application module. The server device includes a control unit and a storage unit. The control unit receives a firmware update request from the terminal device via the base station. The storage unit stores dependency information between multiple first firmwares for the application module and multiple second firmwares for the communication module. The dependency information includes information on correspondence between the multiple first firmwares and the multiple second firmwares, and information on multiple groups to which the multiple first firmwares respectively belong. The update request includes information on the first firmware and second firmware installed in the terminal device, and information on the first firmware and second firmware after the update. The control unit instructs the terminal device to update to the updated first firmware and second firmware in a first case where the difference between a first version representing the group to which the updated first firmware belongs and a second version representing the group to which the installed first firmware belongs is 1 or less. In the second case where the difference is 2 or more, the control unit instructs the terminal device to update to the latest first firmware included in a group of third versions that are 1 greater than the second version.

[0009] The disclosed method is a method for controlling firmware updates in a terminal device that connects a base station and a user network via wireless communication. The terminal device includes an application module and a communication module. The application module executes first firmware to realize the functions of the terminal device. The communication module executes second firmware and performs wireless communication under the control of the application module. The method includes the steps of receiving a firmware update request from the terminal device via the base station and performing a firmware update process based on dependency information between multiple second firmwares for controlling the communication module and multiple first firmwares for controlling the application module. The dependency information includes information on the correspondence between the multiple second firmwares and the multiple first firmwares, and information on multiple groups to which the multiple first firmwares respectively belong. The update request includes information on the second firmware and first firmware installed in the terminal device, and information on the second firmware and first firmware after the update. The step of performing the update process involves, in a first case where the difference between a first version representing the group to which the updated first firmware belongs and a second version representing the group to which the installed first firmware belongs is 1 or less, updating the first firmware and second firmware installed in the terminal device to the updated first firmware and second firmware, respectively, and, in a second case where the difference is 2 or more, updating the first firmware installed in the terminal device to the latest first firmware included in a group of a third version that is 1 greater than the second version. [Effects of the Invention]

[0010] According to the present disclosure, it is possible to efficiently update multiple pieces of firmware in a terminal device that includes a dedicated module for wireless communication. [Brief explanation of the drawings]

[0011] [Figure 1]FIG. 1 is a diagram illustrating an example of the configuration of a firmware management system according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of the server device and the terminal device of FIG. [Figure 3] FIG. 3 is a diagram showing, in a table format, an example of the dependency information stored in the dependency information DB of FIG. [Figure 4] FIG. 4 is a flowchart showing an example of the flow of processing performed by the CPU of FIG. 2 when the server device receives a firmware update request from a terminal device. [Figure 5] FIG. 5 is a flowchart showing an example of a specific processing flow of the inspection processing of FIG. [Figure 6] FIG. 6 is a flowchart showing an example of a specific processing flow of the version correction processing of FIG. [Figure 7] FIG. 7 is a flowchart showing an example of a specific processing flow of the version upgrade processing of FIG. [Figure 8] FIG. 8 is a diagram illustrating an example of a firmware update procedure in a terminal device. [Figure 9] FIG. 9 is a diagram showing the versions of the application firmware and the communication firmware when the update procedure of FIG. 8 fails midway. [Figure 10] FIG. 10 is a diagram showing an example of a firmware update procedure in the terminal device after the application firmware has been updated in FIG. DETAILED DESCRIPTION OF THE INVENTION

[0012] [Description of the embodiments of the present disclosure] First, embodiments of the present disclosure will be listed and described.

[0013] (1) A server device according to an embodiment of the present disclosure is a server device for controlling firmware updates in a terminal device that connects a base station and a user network via wireless communication. The terminal device includes an application module and a communication module. The application module executes first firmware to realize the functions of the terminal device. The communication module executes second firmware and performs wireless communication under the control of the application module. The server device includes a control unit and a storage unit. The control unit receives a firmware update request from the terminal device via the base station. The storage unit stores dependency information between multiple first firmwares for the application module and multiple second firmwares for the communication module. The dependency information includes information on the correspondence between the multiple first firmwares and the multiple second firmwares, and information on multiple groups to which the multiple first firmwares respectively belong. The update request includes information on the first firmware and second firmware installed in the terminal device, and information on the first firmware and second firmware after the update. The control unit instructs the terminal device to update to the updated first firmware and second firmware in a first case where the difference between a first version representing a group to which the updated first firmware belongs and a second version representing a group to which the installed first firmware belongs is equal to or less than 1. In a second case where the difference is equal to or greater than 2, the control unit instructs the terminal device to update to the latest first firmware included in a group of a third version that is 1 greater than the second version.

[0014] In the server device, when updating firmware in a terminal device, the update process for the first firmware is switched based on the difference in major versions before and after the update, thereby reducing the number of firmware updates while maintaining the difference between the registration numbers of the first firmware and the second firmware within the guaranteed operation range. Because a simple update process of updating both firmware versions one by one to the target version is not required, updating multiple firmware versions in the terminal device can be made more efficient.

[0015] (2) In the server device of (1) above, the control unit may instruct the terminal device to update the installed second firmware to the second firmware corresponding to the oldest first firmware included in the third version group, and then to update to the second firmware corresponding to the latest first firmware included in the group.

[0016] In the above server device, even if the procedure for updating the second firmware fails, the combination of the first firmware and the second firmware in the terminal device can be maintained within the guaranteed operation range.

[0017] (3) In the server device of (1) or (2) above, the dependency information may include a plurality of registration numbers each indicating an order in which the plurality of first firmwares and the plurality of second firmwares were registered in the storage unit. Based on the update request, the control unit may acquire the first registration number of the second firmware installed in the terminal device, the second registration number of the second firmware after the update, and the third registration number of the first firmware installed in the terminal device, and if the third registration number is smaller than the first registration number, may instruct the terminal device to update to the first firmware with the fourth registration number that is the largest between the first registration number and the second registration number.

[0018] According to the above server device, it is possible to prevent the difference between the registration number of the first firmware and the registration number of the second firmware in the terminal device from widening to the extent that the operation is outside the guaranteed range.

[0019] (4) In the server device of (1) or (2) above, one of the first firmware update and the second firmware update may be started after the other has been completed.

[0020] According to the above server device, even if either the update of the first firmware or the update of the second firmware fails, it is possible to maintain communication between the terminal device and the server device.

[0021] (5) Another embodiment of the present disclosure provides a method for controlling firmware updates in a terminal device that connects a base station and a user network via wireless communication. The terminal device includes an application module and a communication module. The application module executes first firmware to implement the functions of the terminal device. The communication module executes second firmware and performs wireless communication under the control of the application module. The method includes the steps of receiving a firmware update request from the terminal device via the base station and performing a firmware update process based on dependency information between multiple second firmwares for controlling the communication module and multiple first firmwares for controlling the application module. The dependency information includes information on the correspondence between the multiple second firmwares and the multiple first firmwares, and information on multiple groups to which the multiple first firmwares respectively belong. The update request includes information on the second firmware and first firmware installed in the terminal device, and information on the second firmware and first firmware after the update. The step of performing the update process involves, in a first case where the difference between a first version representing the group to which the updated first firmware belongs and a second version representing the group to which the installed first firmware belongs is 1 or less, updating the first firmware and second firmware installed in the terminal device to the updated first firmware and second firmware, respectively, and, in a second case where the difference is 2 or more, updating the first firmware installed in the terminal device to the latest first firmware included in a group of a third version that is 1 greater than the second version.

[0022] In the above method, when updating firmware in a terminal device, the update process for the first firmware is switched based on the difference in major versions before and after the update, thereby reducing the number of firmware updates while maintaining the difference between the registration numbers of the first firmware and the second firmware within the guaranteed operation range. Because a simple update process of updating both firmware versions one by one to the target version is not required, updating multiple firmware versions in a terminal device can be made more efficient.

[0023] [Details of the embodiments of the present disclosure] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference numerals, and description thereof will not be repeated.

[0024] Fig. 1 is a diagram illustrating an example of the configuration of a firmware management system 1000 according to an embodiment of the present disclosure. As illustrated in Fig. 1, the firmware management system 1000 includes a server device 100, a terminal device 200, and a base station Bs. Note that the firmware management system 1000 may include multiple terminal devices 200, or may include multiple base stations Bs.

[0025] The base station Bs performs wireless communication with the terminal device 200. The wireless communication is, for example, cellular communication (5G, 4G, or LTE (Long Term Evolution)) conforming to the 3GPP (3rd Generation Partnership Project). The base station Bs is connected to a network NW. The network NW includes the Internet, a LAN, a WAN (Wide Area Network), or a cloud system.

[0026] The terminal device 200 is installed in a factory Fa. The facility where the terminal device 200 is installed may be a residence, an office, a research facility, or a commercial facility.

[0027] A camera Cm and a sensor Sn that monitor the line Ln are connected to the terminal device 200. Other devices may also be connected to the terminal device 200. The sensor Sn includes, for example, a temperature sensor, a humidity sensor, a human presence sensor, a pressure sensor, or a vibration sensor. The terminal device 200, the camera Cm, and the sensor Sn are connected to one another via a user network (for example, a LAN). Data acquired by the camera Cm and the sensor Sn is uploaded to a database (not shown) connected to the network NW via the terminal device 200.

[0028] The server device 100 is a FOTA server that stores firmware for the terminal device 200. The server device 100 is connected to a network NW. In response to a firmware update request from the terminal device 200, the server device 100 transmits information about the firmware to be downloaded to the terminal device 200.

[0029] Fig. 2 is a diagram showing an example of the hardware configuration of the server device 100 and the terminal device 200 of Fig. 1. As shown in Fig. 2, the server device 100 includes a CPU 110 (controller) and a nonvolatile memory 120 (storage unit). The nonvolatile memory 120 includes, for example, a flash memory or a hard disk. The nonvolatile memory 120 stores an application firmware DB (database) 121, a cellular communication firmware DB 122, and a firmware dependency information DB 123.

[0030] The CPU 110 functions as a firmware transmission scheduling unit 112 and a firmware transmission unit 113. The firmware transmission scheduling unit 112 receives a firmware update request from the terminal device 200, determines the firmware to be downloaded and the timing of the download, and transmits an update firmware list including this information to the terminal device 200. The firmware transmission unit 113 receives a firmware download request from the terminal device 200, and transmits the requested firmware data to the terminal device 200.

[0031] The terminal device 200 includes an application module 210 and a communication module 220. The application module 210 functions as, for example, CPE (Customer Premises Equipment). The application module 210 includes a main CPU (Central Processing Unit) 211 and a non-volatile memory 217. Application firmware Fw1 (first firmware) is installed in the non-volatile memory 217. The non-volatile memory 217 includes, for example, a flash memory or a hard disk. The main CPU 211 executes the application firmware Fw1 to implement the functions of the terminal device 200. The main CPU 211 implements a firmware update function included in the functions as a firmware update management unit 212.

[0032] The communication module 220 includes a communication CPU 221 and a nonvolatile memory 223. Communication firmware Fw2 (second firmware) is installed in the nonvolatile memory 223. The nonvolatile memory 223 includes, for example, a flash memory or a hard disk. The communication CPU 221 executes the communication firmware Fw2 and performs wireless communication with the base station Bs under the control of the application module 210. The communication CPU 221 realizes such wireless communication functions as a communication function unit 222.

[0033] The firmware update management unit 212 includes an update request unit 213, an information acquisition unit 214, a download execution unit 215, and an installation execution unit 216. The update request unit 213 outputs a download request for firmware Fw1 and Fw2 to the information acquisition unit 214. In response to the download request, the information acquisition unit 214 acquires version information for the firmware Fw1 and Fw2 and transmits an update request including the version information to the server device 100 via the communication function unit 222. The version information includes information about the application firmware Fw1 and communication firmware Fw2 installed in the terminal device 200, as well as information about the updated application firmware Fw1 and communication firmware Fw2. The download execution unit 215 receives an update firmware list from the server device 100 via the information acquisition unit 214. The download execution unit 215 transmits a download request for the firmware specified in the update firmware list to the server device 100 at a timing specified in the update firmware list. The download execution unit 215 outputs the firmware received from the server device 100 to the installation execution unit 216. The installation execution unit 216 installs the firmware into the nonvolatile memories 217 and 223.

[0034] Fig. 3 is a diagram showing in table form an example of dependency information stored in the dependency information DB of Fig. 2. As shown in Fig. 3, the items in the column of dependency information include revision (RV), registration number of communication firmware, version of communication firmware, registration number of application firmware, version of application firmware (AM), and major version.

[0035] Each column of the dependency information contains the corresponding versions of the communication firmware and the application firmware. The version is composed of a main version on the left side of the period and a sub-version on the right side of the period. The larger the main version, the newer the version that includes the main version. If the main version is the same, the larger the sub-version, the newer the version composed of the main version and the sub-version.

[0036] A revision is a number assigned to each column by version control software. The higher the revision, the newer the information contained in the column specified by that revision. A communication firmware version indicates the revision order of the communication firmware. A version of application firmware indicates the revision order of the application firmware. A major version indicates the group to which the application firmware belongs and to which the communication module corresponding to that application firmware belongs. The higher the major version, the newer the group of application firmware specified by that major version.

[0037] The registration number of the communication firmware Fw2 and the registration number of the application firmware Fw1 indicate the order of the firmware registered in the nonvolatile memory 120. The larger the registration number, the newer the firmware specified by the registration number.

[0038] When the major version of the application firmware is equal to or higher than the major version of the communication firmware, the combination of the application firmware and the communication firmware is guaranteed to operate in the terminal device 200. For example, the combination of application firmware version 1.7 (registration number 13) and each of the communication firmware versions 1.0 to 1.4 is guaranteed to operate in the terminal device 200.

[0039] Furthermore, even if the major version of the application firmware is smaller than the major version of the communication firmware, if the difference between the major versions of the application firmware and the communication firmware is 1 and the registration number of the communication firmware is the smallest registration number of the communication firmware included in the major version of the communication firmware, the combination of the application firmware and the communication firmware is guaranteed to operate in the terminal device 200. For example, the combination of each of application firmware versions 1.0 (registration number 2) to 1.3 (registration number 7) and communication firmware version 1.3 (registration number 8) is guaranteed to operate in the terminal device 200.

[0040] According to the registration numbers of the dependency information shown in Figure 3, communication firmware 1.0 to 1.8 and application firmware 1.0 to 1.15 are registered in non-volatile memory 120 in the following order: communication firmware 1.0 (registration number 1), application firmware 1.0 (registration number 2), communication firmware 1.1 (registration number 3), application firmware 1.1 (registration number 4), communication firmware 1.2 (registration number 5), application firmware 1.2 (registration number 6), application firmware 1.3 (registration number 7), ..., application firmware 1.13 (registration number 22), application firmware 1.14 (registration number 23), communication firmware 1.8 (registration number 24), and application firmware 1.15 (registration number 25).

[0041] Major version 1 includes application firmware 1.0 to 1.3. Major version 2 includes application firmware 1.4 to 1.7. Major version 3 includes application firmware 1.8 to 1.11. Major version 4 includes application firmware 1.12 to 1.15.

[0042] 4 is a flowchart showing an example of the flow of processing performed by the CPU 110 of FIG. 2 when the server device 100 receives a firmware update request from the terminal device 200. In the following, steps will simply be abbreviated as S.

[0043] 4, in S100, the CPU 110 acquires version information of each firmware of the terminal device 200 included in the update request of the terminal device 200, and proceeds to S200. In S200, the CPU 110 checks the consistency of the versions of each firmware of the terminal device 200, and proceeds to S300. In S300, the CPU 110 creates an update firmware list, and proceeds to S400. In S400, the CPU 110 transmits the update firmware list to the terminal device 200, and ends the process.

[0044] Fig. 5 is a flowchart showing an example of a specific processing flow of the inspection processing S200 of Fig. 4. As shown in Fig. 5, in S210, CPU 110 performs a version correction processing and advances the processing to S210. In S220, CPU 110 performs a version upgrade processing and returns the processing to a main routine (not shown).

[0045] Fig. 6 is a flowchart showing an example of a specific processing flow of the version correction processing S210 of Fig. 5. As shown in Fig. 6, in S211, the CPU 110 acquires the registration number SN1 (first registration number) of the (current) communication firmware FW2 installed in the communication module, and proceeds to processing S212. In S212, the CPU 110 acquires the registration number SN2 (second registration number) of the updated communication firmware FW2, and proceeds to processing S213. In S213, the CPU 110 acquires the registration number SN3 (third registration number) of the current application firmware FW1, and proceeds to processing S214.

[0046] In S214, CPU 110 determines whether registration number SN3 is smaller than registration number SN1. If registration number SN3 is smaller than registration number SN1 (YES in S214), CPU 110 instructs terminal device 200 to install application firmware with the largest registration number (fourth registration number) between registration numbers SN1 and SN2 in S215, and returns processing to the main routine. If registration number SN3 is equal to or larger than registration number SN1 (NO in S214), CPU 110 returns processing to the main routine.

[0047] By performing the version correction process shown in Figure 6, it is possible to timely prevent the difference between the registration number of the application firmware Fw1 and the registration number of the communication firmware Fw2 in the terminal device 200 from widening beyond the guaranteed operating range.

[0048] Fig. 7 is a flowchart showing an example of a specific processing flow of the version upgrade process S220 in Fig. 5. In S221, the CPU 110 acquires the major version MV1 (first version) of the updated application firmware FW1, and proceeds to S222. In S222, the CPU 110 acquires the major version MV2 (second version) of the current application firmware FW1, and proceeds to S223.

[0049] In S223, CPU 110 determines whether the difference between major version MV1 and major version MV2 (=MV1-MV2) is less than 2. If the difference between major version MV1 and major version MV2 is 2 or greater (NO in S223), CPU 110 instructs terminal device 200 in S224 to update application firmware Fw1 to the latest version included in the major version (third version) that is 1 greater than major version MV1, and proceeds to process S225. In S225, CPU 110 waits until the update of application firmware Fw1 in terminal device 200 is complete, and then returns the process to S221.

[0050] If the difference between major version MV2 and major version MV1 is less than 2 (YES in S223), CPU 110 instructs terminal device 200 to update application firmware Fw1 in S226, and returns the process to the main routine.

[0051] 7, the difference between the registration number of the application firmware Fw1 and the registration number of the communication firmware Fw2 can be maintained within the guaranteed operation range while suppressing the number of firmware updates in the update process in the terminal device 200. Since a simple update process of updating each of the firmware one by one to the target version is not required, it is possible to efficiently update the multiple firmwares Fw1 and Fw2 in the terminal device 200 that includes a dedicated module for wireless communication. Note that the processes shown in FIGS. 6 and 7 may be performed in the terminal device 200.

[0052] Fig. 8 is a diagram showing an example of a firmware update procedure in the terminal device 200. Fig. 8 shows an update procedure from revision 00 to revision 15. That is, the current versions of the application firmware Fw1 and communication firmware Fw2 in the terminal device 200 are 1.0 and 1.0, respectively, and the updated versions of the application firmware Fw1 and communication firmware Fw2 are 1.15 and 1.8, respectively.

[0053] As shown in Figure 8, the update procedure from revision 00 to revision 15 is divided into update procedures Up1, Up2, and Up3. Update procedure Up1 is the update procedure from revision 00 to revision 07. Update procedure Up2 is the update procedure from revision 07 to revision 11. Update procedure Up3 is the update procedure from revision 11 to revision 15.

[0054] The update procedure Up1 is an update procedure from major version 1 to 2. In the update procedure Up1, the communication firmware FW2 is updated in this order from version 1.0 to 1.3 to 1.4, and then the application firmware FW1 starts to be updated from version 1.0 to 1.7.

[0055] The update procedure Up2 is an update procedure from major version 2 to 3. In the update procedure Up2, the communication firmware FW2 is updated to versions 1.4, 1.5, and 1.6 in this order, and then the application firmware FW1 starts to be updated from version 1.7 to 1.11.

[0056] The update procedure Up3 is an update procedure from major version 3 to 4. In the update procedure Up3, the communication firmware FW2 is updated to versions 1.6, 1.7, and 1.8 in this order, and then the application firmware FW1 starts to be updated from version 1.11 to 1.15.

[0057] As described above, in each of the update procedures Up1, Up2, and Up3, the communication firmware Fw2 is first updated to the oldest version of the communication firmware Fw2 included in the target major version, and then updated to the latest version of the communication firmware Fw2 included in the target major version. As a result, even if the update procedure for the communication firmware Fw2 fails, the combination of the application firmware Fw1 and the communication firmware Fw2 in the terminal device 200 can be maintained within the guaranteed operation range.

[0058] Furthermore, in each of the update procedures Up1, Up2, and Up3, the update of the application firmware Fw1 is started after the communication firmware Fw2 is updated. In this way, by not updating the application firmware Fw1 and the communication firmware Fw2 in parallel but starting the update of one after the update of the other is completed, it is possible to maintain communication between the terminal device 200 and the server device 100 even if one of the updates fails. Note that the update of the application firmware Fw1 may be started after the communication firmware Fw2 is updated.

[0059] FIG. 9 is a diagram showing the versions of the application firmware FW1 and the communication firmware FW2 when the update procedure Up1 in FIG. 8 fails midway. As shown in FIG. 9, the update of the communication firmware FW2 from version 1.3 to 1.4 fails in the update procedure Up1. Because the update procedure Up1 is canceled, the registration number of the current communication firmware FW2 in the terminal device 200 becomes 8, and the registration number of the current application firmware FW1 becomes 2. The registration number of the current application firmware FW1 is smaller than the registration number of the current communication firmware FW2. Therefore, the application firmware FW1 is updated to the application firmware FW1 with the registration number 11, which is the largest between the registration number 1 of the current communication firmware FW2 and the registration number 12 of the updated communication firmware FW2. As a result, the firmware FW1 and FW2 installed in the terminal device 200 correspond to revision 06.

[0060] Fig. 10 is a diagram showing an example of a firmware update procedure in the terminal device 200 after the application firmware Fw1 has been updated in Fig. 9. As shown in Fig. 10, the update procedure from revision 06 to 15 is changed to update procedures Up4 and Up5. Update procedure Up4 is an update procedure from revision 06 to revision 11. Update procedure Up5 is an update procedure from revision 11 to revision 15.

[0061] The update procedure Up4 is an update procedure from major version 2 to 3. In the update procedure Up4, the communication firmware FW2 is updated to versions 1.3, 1.5, and 1.6 in this order, and then the application firmware FW1 is updated from version 1.6 to 1.11.

[0062] The update procedure Up5 is an update procedure from major version 3 to 4. In the update procedure Up5, the communication firmware FW2 is updated to versions 1.6, 1.7, and 1.8 in this order, and then the application firmware FW1 is updated from version 1.11 to 1.15.

[0063] As described above, the server device and method according to the embodiment can efficiently update firmware in a terminal device that includes a dedicated module for wireless communication.

[0064] The embodiments disclosed herein are illustrative in all respects and should not be considered limiting. The scope of the present invention is defined by the claims rather than the above-described embodiments, and it is intended to include any modifications within the scope of the claims and meanings equivalent to the claims. [Explanation of symbols]

[0065] 100 Server device 112 Firmware transmission scheduling unit 113 Firmware transmission unit 120,217,223 Non-volatile memory 121 Application firmware DB 122 Cellular communication firmware DB 123 Firmware Dependency DB 200 Terminal Device 210 Application Modules 211 Main CPU 212 Firmware Update Management Unit 213 Update request section 214 Information Acquisition Department 215 Download execution unit 216 Installation execution unit 220 Communication Module 221 Communication CPU 222 Communication Function Unit 1000 Firmware Management System Bs base station Commercial Camera DB dependency information Fw1 Application firmware Fw2 communication firmware Ln Line NW Network Sn sensor

Claims

1. A server device for controlling firmware updates in a terminal device that connects a base station and a user network via wireless communication, comprising: The terminal device an application module that executes first firmware to realize the functions of the terminal device; a communication module that executes second firmware and is controlled by the application module to perform the wireless communication; The server device a control unit that receives a firmware update request from the terminal device via the base station; a storage unit that stores dependency information between a plurality of first firmwares for the application module and a plurality of second firmwares for the communication module; the dependency information includes information on a correspondence relationship between the plurality of first firmwares and the plurality of second firmwares, and information on a plurality of groups to which the plurality of first firmwares respectively belong; the update request includes information about the first firmware and the second firmware installed in the terminal device, and information about the first firmware and the second firmware after the update; The control unit In a first case where a difference between a first version representing a group to which the updated first firmware belongs and a second version representing a group to which the installed first firmware belongs is 1 or less, instruct the terminal device to update to the updated first firmware and second firmware; In a second case where the difference is 2 or more, the server device instructs the terminal device to update to the latest first firmware included in a group of third versions that are 1 greater than the second version.

2. The server device described in claim 1, wherein the control unit instructs the terminal device, in the second case, to update the installed second firmware to the second firmware corresponding to the oldest first firmware included in the third version group, and then to update it to the second firmware corresponding to the latest first firmware included in the group.

3. the dependency information includes a plurality of registration numbers each representing an order in which the plurality of first firmwares and the plurality of second firmwares were registered in the storage unit, The control unit acquiring, based on the update request, a first registration number of the second firmware installed in the terminal device, a second registration number of the second firmware after the update, and a third registration number of the first firmware installed in the terminal device; 3. The server device according to claim 1, wherein if the third registration number is smaller than the first registration number, the server device instructs the terminal device to update to the first firmware of the fourth registration number that is the largest between the first registration number and the second registration number.

4. The server device according to claim 1 , wherein one of the first firmware update and the second firmware update is started after the other is completed.

5. A method for controlling firmware update in a terminal device that connects a base station and a user network via wireless communication, comprising: The terminal device an application module that executes first firmware to realize the functions of the terminal device; a communication module that executes second firmware and is controlled by the application module to perform the wireless communication; The method comprises: receiving a firmware update request from the terminal device via the base station; performing a firmware update process based on dependency information between a plurality of second firmwares for controlling the communication module and a plurality of first firmwares for controlling the application module; the dependency information includes information on a correspondence relationship between the plurality of second firmwares and the plurality of first firmwares, and information on a plurality of groups to which the plurality of first firmwares respectively belong; the update request includes information about the second firmware and the first firmware installed in the terminal device, and information about the second firmware and the first firmware after the update; The step of performing the update process includes: In a first case where the difference between a first version representing a group to which the updated first firmware belongs and a second version representing a group to which the installed first firmware belongs is 1 or less, updating the first firmware and the second firmware installed in the terminal device to the updated first firmware and the second firmware, respectively; In a second case where the difference is 2 or more, the method updates the first firmware installed in the terminal device to the latest first firmware included in a group of third versions that are one version greater than the second version.

Images