Communication device and communication method

Abstract

This communication device comprises: a firmware information acquisition unit that acquires firmware information relating to at least one piece of firmware held by a communication package mounted in the communication device; a determination unit that, on the basis of the firmware information acquired by the firmware information acquisition unit, determines whether the at least one piece of firmware is appropriate or not for the communication package; and a firmware application unit that, if the determination unit determines that the at least one piece of firmware is not appropriate for the communication package, acquires firmware appropriate for the communication package and applies the firmware to the communication package.

Description

Communication device and communication method

[0001] The present invention relates to a communication device and a communication method.

[0002] In a communication device, each communication package installed in the communication device stores its own firmware. The firmware of each communication package is designed to be updatable in response to future service expansions and specification changes. Therefore, even for the same communication package, multiple firmware versions are applicable. Furthermore, if the communication device is a chassis type, the communication device will be equipped with multiple communication packages, and each communication package will operate with its own firmware. In order to update the firmware, it is necessary to install the communication package in the communication device and perform the update. Conventionally, a communication device such as that described in Patent Document 1 has been known, for example.

[0003] Patent No. 4298716

[0004] The communication packages used for replacement in the event of a failure are managed at multiple maintenance bases for communication devices installed in various locations, and may not be installed in the communication devices, and the firmware in the communication packages may not be up to date. Therefore, it is necessary to manage the firmware installed in the communication packages used for replacement in the event of a failure, and inserting a communication package with incorrect firmware into a communication device may cause a failure.

[0005] Furthermore, even if a communication package is the same, different firmware is installed depending on the type of communication service. This requires the management of communication packages equipped with each firmware, potentially resulting in an increase in the number of communication package types and complex management. While it is possible to remotely transfer and update the appropriate firmware when a communication package is newly installed in a communication device, this requires both on-site and remote workers to perform the process, resulting in the firmware transfer time and communication interruptions. In addition, to improve worker efficiency, multiple firmware files, such as FPGA (Field Programmable Gate Array) files, application files, OS (Operating System), and middleware, are packaged into a single firmware file, resulting in a large firmware file size and long transfer times. When firmware is divided into smallest units, the firmware application order and management become complicated.

[0006] In view of the above circumstances, the present invention aims to provide a technology that enables a communication device to operate using a communication package that holds appropriate firmware, even if the communication package installed in the communication device holds inappropriate firmware.

[0007] One aspect of the present invention is a communications device comprising: a firmware information acquisition unit that acquires firmware information regarding at least one firmware held by a communications package installed in the communications device; a judgment unit that determines whether the at least one firmware is appropriate for the communications package based on the firmware information acquired by the firmware information acquisition unit; and a firmware application unit that, when the judgment unit determines that at least one of the at least one firmware is not appropriate for the communications package, acquires appropriate firmware for the communications package and applies it to the communications package.

[0008] Another aspect of the present invention is a communication method used in a communication device, comprising: a firmware information acquisition step of acquiring firmware information regarding at least one firmware held by a communication package mounted on the communication device; a determination step of determining whether the at least one firmware is appropriate for the communication package based on the firmware information acquired in the firmware information acquisition step; and a firmware application step of acquiring appropriate firmware for the communication package and applying it to the communication package if it is determined in the determination step that at least one of the at least one firmware is not appropriate for the communication package.

[0009] According to the present invention, even if the communication package installed in the communication device holds inappropriate firmware, the communication device can be operated using a communication package holding appropriate firmware.

[0010] FIG. 1 is a schematic configuration diagram of a communication system according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of a configuration file stored in a configuration file holding unit of a communication device control unit of a communication device according to the embodiment. FIG. 3 is a sequence diagram showing processing performed in a communication system according to the embodiment. FIG. 4 is a flowchart showing an example of processing by a communication device control unit of a communication device according to the embodiment. FIG. 5 is a flowchart showing another example of processing by a communication device control unit of a communication device according to the embodiment. FIG. 6 is a diagram explaining one aspect of the present embodiment. FIG. 7 is a diagram explaining another aspect of the present embodiment. FIG. 8 is a diagram explaining yet another aspect of the present embodiment. FIG. 9 is a diagram explaining yet another aspect of the present embodiment.

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0012] 1 is a schematic diagram of a communication system 100 according to an embodiment of the present invention. The communication system 100 includes a server 10 and a communication device 20. The server 10 and the communication device 20 are configured by a PC (Personal Computer) or the like, and are capable of communicating with each other via a wireless network or the like.

[0013] The server 10 includes a firmware holding unit 11 and a transmission / reception unit 12. The firmware holding unit 11 is connected to the transmission / reception unit 12. The firmware holding unit 11 includes a storage device such as a hard disk drive (HDD). The firmware holding unit 11 stores firmware for controlling various versions of applications (also referred to as apps), middleware, an operating system (OS), and a field programmable gate array (FPGA). The transmission / reception unit 12 is connected to the firmware holding unit 11. The transmission / reception unit 12 transmits and receives data to and from a communication device 20, etc., via a wireless network, etc.

[0014] The communication device 20 includes a communication device control unit 21. The communication device control unit 21 includes a CPU (Central Processing Unit). The communication device control unit 21 includes a transmission / reception unit 211, an operation version management unit 212, a configuration definition file storage unit 213, a compatibility determination unit 214, a transmission / reception unit 215, a firmware separation unit 216, a firmware storage unit 217, and a firmware combination unit 218.

[0015] The transmission / reception unit 211 is connected to the compatibility determination unit 214 and the firmware separation unit 216. The transmission / reception unit 211 transmits and receives data to and from the server 10, etc., via a wireless network, etc. The operation version management unit 212 is connected to the compatibility determination unit 214. The operation version management unit 212 includes a memory, etc., and stores the version of firmware held by the communication package 22 installed in the communication device 20, etc.

[0016] The configuration file holding unit 213 is connected to the compatibility determination unit 214. The configuration file holding unit 213 includes a memory and stores a configuration file (also referred to as correspondence information) that associates a communication package with firmware appropriate for that communication package. The firmware appropriate for the communication package is, for example, the latest version of firmware distributed for the communication package.

[0017] 2 is a diagram showing an example of a configuration file stored in the configuration file holding unit 213 of the communication device control unit 21 of the communication device 20 according to this embodiment. In the configuration file shown in Fig. 2, a firmware version (e.g., "A"), a hardware version number (e.g., "01"), a firmware version number (e.g., "111"), an OS configuration (e.g., "OS(1)"), a middleware configuration (e.g., "middleware(1)"), an application configuration (e.g., "application(1)"), and an FPGA configuration (e.g., "FPGA(1)") are associated with each other.

[0018] Based on the configuration definition file shown in Figure 2, for example, it can be seen that the firmware appropriate for a communication package identified by the hardware version number "01" and the firmware version number "111" is the OS firmware identified by "OS(1)", the middleware firmware identified by "middleware(1)", the application firmware identified by "application(1)", and the FPGA firmware identified by "FPGA(1)".

[0019] 1, compatibility determination unit 214 is connected to transmission / reception unit 211, operation version management unit 212, configuration file holding unit 213, transmission / reception unit 215, firmware holding unit 217, and firmware combination unit 218. Compatibility determination unit 214 determines whether the firmware held by communication package 22 installed in communication device 20 is appropriate based on the configuration file (see FIG. 2) stored in configuration file holding unit 213.

[0020] The transmitting / receiving unit 215 is connected to the compatibility determination unit 214 and the firmware combining unit 218. The transmitting / receiving unit 215 is connected to the communications package 22 by wire, and inputs and outputs data between the communications package 22. The firmware separating unit 216 is connected to the transmitting / receiving unit 211 and the firmware holding unit 218. The firmware separating unit 216 separates firmware that is inappropriate for the communications package 22 from the communications package 22, among firmware held by the communications package 22.

[0021] The firmware holding unit 217 is connected to the compatibility determination unit 214 and the firmware separation unit 216. The firmware holding unit 217 includes a storage device such as a memory. The firmware holding unit 11 stores firmware for controlling various versions of applications, middleware, OSs, and FPGAs. Note that the number of firmwares stored in the firmware holding unit 217 of the communication device 20 is smaller than the number of firmwares stored in the firmware holding unit 11 of the server 10.

[0022] The firmware combining unit 218 is connected to the compatibility determining unit 214 and the transmitting / receiving unit 215. The firmware combining unit 218 combines appropriate firmware held in the communication package 22 with appropriate firmware held in the firmware holding unit 217 or appropriate firmware acquired from the firmware holding unit 11 of the server 10.

[0023] The communication package 22 in Fig. 1 includes a communication package control unit 221, a hardware information management unit 222, a transmission / reception unit 223, and a firmware holding unit 224. Although Fig. 1 shows a case where the communication device 20 includes one communication package, the communication device 20 can also be equipped with multiple communication packages at the same time. Furthermore, the communication package 22 equipped in the communication device 20 can be replaced with another communication package.

[0024] The communication package control unit 221 is connected to a hardware information management unit 222, a transmission / reception unit 223, and a firmware holding unit 224. The communication package control unit 221 has a CPU and controls each unit of the communication package 22. The hardware information management unit 222 is connected to the communication package control unit 221. The hardware information management unit 222 has a storage device such as a memory and stores information about the hardware that makes up the communication package 22.

[0025] The transmitting / receiving unit 223 is connected to the communication package control unit 221 and the firmware holding unit 224. The transmitting / receiving unit 223 is connected to the communication device control unit 21 by wire, and inputs and outputs data to and from the communication device control unit 21. The firmware holding unit 224 is connected to the transmitting / receiving unit 223 and the firmware holding unit 224. The firmware holding unit 224 includes a storage device such as a memory, and stores at least one firmware for driving the communication package 22. The firmware stored in the firmware holding unit 224 may include firmware that is appropriate for the communication package 22 (for example, the latest firmware) as well as firmware that is not appropriate for the communication package 22 (for example, firmware that is not the latest).

[0026] 3 is a sequence diagram showing the processing performed in communication system 100 according to this embodiment. First, the configuration file is confirmed and updated between server 10 and communication device control unit 21 (step S101). For example, communication device control unit 21 periodically (e.g., every hour) checks with server 10, where the latest configuration file is stored, to keep the configuration file stored in configuration file holding unit 213 of communication device control unit 21 up to date.

[0027] On the other hand, when the communications package 22 is loaded into the communications device 20 and activated (step S102), it transmits an activation notification to the communications device 20 (step S103). Next, the communications device 20 inquires of the communications package 22 about the versions of the hardware and firmware included in the communications package 22 (step S104). In response, the communications package 22 confirms the versions of the hardware and firmware included in the communications package 22 and replies to the communications device control unit 21 (step S105).

[0028] Next, the communication device control unit 21 determines whether the firmware held by the communications package 22 is appropriate based on the configuration definition file (see FIG. 2) (step S106). If it is determined in step S106 that the firmware held by the communications package 22 is appropriate, the communication device control unit 21 instructs the communications package 22 to start its own startup (step S107), and in response to the instruction, the communications package 22 starts its startup (step S109).

[0029] On the other hand, if it is determined in step S106 that the firmware held by the communication package 22 is not appropriate, the communication device control unit 21 determines whether appropriate firmware is held in the communication package 22 in the firmware holding unit 217 of the communication device control unit 21 (step S108).

[0030] If it is determined in step S108 that the firmware holding unit 217 holds firmware appropriate for the communications package 22, the communications device control unit 21 reads the appropriate firmware from the firmware holding unit 217 and outputs it to the communications package 22 (step S110), and the communications package 22 applies the appropriate firmware and restarts itself (step S111). Thereafter, the communications package 22 notifies the communications device control unit 21 of the version of the firmware held by the communications package 22 (step S112).

[0031] On the other hand, if it is determined in step S108 that the firmware storage unit 217 does not store firmware appropriate for the communications package 22, the communications device control unit 21 identifies a portion that is insufficient for constructing appropriate firmware (step S113). For example, the communications device control unit 21 identifies inappropriate firmware (e.g., firmware that is not the latest) among at least one piece of firmware included in the communications package 22. The communications device control unit 21 then requests appropriate firmware corresponding to the inappropriate firmware identified in step S113 from the server 10 (step S114). In response, the server 10 reads the appropriate firmware from the firmware storage unit 217 and transmits it to the communications device control unit 21 (step S115).

[0032] Next, the communication device control unit 21 combines the appropriate firmware of the communications package 22 with the appropriate firmware received from the server 10 (step S116). Then, the communication device control unit 21 outputs the combined appropriate firmware to the communications package 22 (step S117). The communications package 22 applies the combined appropriate firmware and restarts the communications package 22 (step S118). Thereafter, the communications package 22 notifies the communications device control unit 21 of the firmware version held by the communications package 22 (step S119).

[0033] 4 is a flowchart showing an example of processing by the communication device control unit of the communication device according to this embodiment. First, when the communication package 22 is installed in the communication device 20, the operating version management unit 212 activates the communication package 22 (step S201). Next, the operating version management unit 212 checks the versions of the hardware and firmware of the communication package 22 activated in step S201 by inquiring of the communication package 22 (step S202). Next, the compatibility determination unit 214 determines whether the firmware held by the communication package 22 is appropriate based on the configuration file (see FIG. 2 ) stored in the configuration file holding unit 213 (step S203).

[0034] If it is determined that the firmware held by the communications package 22 is appropriate (i.e., if "YES" in step S203), the compatibility determination unit 214 continues the operation of the communications package 22 (step S204). In step S204, for example, if all firmware held by the communications package 22 is the latest version, the firmware is determined to be appropriate.

[0035] On the other hand, if it is determined that the firmware held by the communications package 22 is inappropriate (i.e., if "NO" in step S203), the compatibility determination unit 214 determines whether appropriate firmware is held in the firmware holding unit 217 of the communications device control unit 21 (step S205). In step S204, for example, if at least one piece of firmware held by the communications package 22 is not the latest, the firmware is determined to be inappropriate. If it is determined that appropriate firmware is held in the firmware holding unit 217 (i.e., if "YES" in step S205), the processing of step S208, which will be described later, is performed.

[0036] On the other hand, if it is determined that the firmware holding unit 217 does not hold the appropriate firmware (i.e., if the answer is "NO" in step S205), the transmitting / receiving unit 211 requests the appropriate firmware from the server 10 (step S206), and receives the appropriate firmware sent in response to the request from the server 10 (step S207).

[0037] Thereafter, the firmware combining unit 218 combines the appropriate firmware held by the communication package 22 with the appropriate firmware corresponding to the inappropriate firmware held by the communication package 22, and the transmitting / receiving unit 215 outputs the combined appropriate firmware to the communication package 22 (step S208), restarts the communication package 22, and starts operation of the communication package 22 (step S209).

[0038] 5 is a flowchart showing another example of the processing of the communication device control unit of the communication device according to this embodiment. First, the transmitting / receiving unit 211 inquires about the latest configuration file information of the server 10 (step S301). Next, based on the latest configuration file information returned from the server 10, the configuration file holding unit 213 determines whether the held configuration file is the latest (step S302).

[0039] If the configuration file held by configuration file holding unit 213 is the latest (i.e., if "YES" in step S302), the processing of step S304 described below is performed. On the other hand, if the configuration file held by configuration file holding unit 213 is not the latest (i.e., if "NO" in step S302), the latest configuration file is requested from and received by server 10 (step S303).

[0040] Configuration file storage unit 213 then determines whether a predetermined time (e.g., one hour) has elapsed (step S304). If the predetermined time has not elapsed (i.e., if "NO" in step S304), step S304 is performed again. On the other hand, if the predetermined time has elapsed (i.e., if "YES" in step S304), step S301 is performed.

[0041] In this embodiment, an operating version management unit 212 (also referred to as a firmware information acquisition unit) acquires hardware and firmware versions (also referred to as firmware information) related to at least one firmware 22 held in a communications package 22 installed in the communications device 20. Furthermore, a compatibility determination unit 214 (also referred to as a determination unit) determines whether at least one piece of firmware is appropriate for the communications package 22 based on the hardware and firmware versions related to the at least one firmware 22 acquired by the operating version management unit 212. Furthermore, if the compatibility determination unit 214 determines that at least one piece of firmware for the communications package 22 is not appropriate, a firmware combination unit 218 (also referred to as a firmware application unit) acquires appropriate firmware for the communications package 22 and applies it to the communications package 22.

[0042] In this embodiment, the communication device 20 further includes a firmware holding unit 217 that holds in advance firmware applicable to the communication package 22. When the compatibility determination unit 214 determines that at least one piece of firmware is not appropriate for the communication package 22, the firmware combination unit 214 acquires appropriate firmware for the communication package 22 from the firmware holding unit 217 or the server 10 (also referred to as an external device), combines it with the appropriate firmware held in the communication package 22, and applies it to the communication package.

[0043] In this embodiment, the communication device 20 further includes a configuration file holding unit 213 (also referred to as a correspondence information storage unit) that stores a configuration file (also referred to as correspondence information) that associates the communication package 22 with appropriate firmware for the communication package 22. The compatibility determination unit 214 determines whether or not at least one piece of firmware is appropriate for the communication package 22, based on the hardware and firmware versions for the at least one piece of firmware 22 acquired by the operating version management unit 212 and the configuration file stored in the configuration file holding unit 213.

[0044] 6 , firmware to be output to the communication package 22 (e.g., firmware related to app (3), middleware (1), and OS (1)) can be constructed by combining firmware (e.g., firmware related to OS (1), app (1), app (2), middleware (1), FPGA (1), and app (3)) stored in the firmware storage unit 217. Also, firmware to be output to the communication package 22 (e.g., firmware related to app (4), middleware (1), and OS (1)) can be constructed by combining firmware (e.g., firmware related to OS (1), app (1), app (2), middleware (1), FPGA (1), and app (3)) stored in the firmware storage unit 217 with firmware (e.g., firmware related to app (4)) received from the server 10.

[0045] As a result, even if the communication package installed in the communication device 20 holds inappropriate firmware, the communication device 20 can be operated using a communication package holding appropriate firmware.

[0046] Furthermore, according to the communication device 20 of this embodiment, even if a communication package 22 containing inappropriate firmware is inserted into the communication device 20, the firmware can be automatically updated, making it easier to manage the communication package 22 when it is stored.

[0047] Furthermore, when transferring firmware from the server 10, only the portion that needs to be updated is transmitted to the communication device 20, thereby shortening the transmission time and shortening the time during which communication by the communication device 20 is interrupted. Therefore, even when new firmware is released, this is effective in cases where the portion to be changed is limited to the application. Furthermore, since there is no need to store duplicate OSs, etc. in the firmware storage unit 217, memory can be used efficiently and more firmware can be immediately supported. Furthermore, this eliminates the need for operators to manage multiple firmware combinations.

[0048] In the case of packaged firmware FW1 as shown in the left diagram of FIG. 7 , firmware FW2 may hold firmware related to OS (1), middleware (1), application (1), and FPGA (1), while firmware FW3 may hold firmware related to OS (1), middleware (1), application (2), and FPGA (1). In other words, firmware FW2 and firmware FW3 may hold firmware related to OS (1), middleware (1), and FPGA (1) in duplicate, which may result in memory usage being strained. In this embodiment, it is preferable to hold one copy each of the OS (1), middleware (1), and FPGA (1) that are duplicated between firmware FW2 and firmware FW3, as in firmware FW4 shown in the right diagram of FIG. 7 . By dividing and combining firmware in this way, it is possible to support a large number of firmwares with a small amount of data.

[0049] In this embodiment, the firmware stored in the firmware holding unit 217 of the communication device control unit 21 of the communication device 20 may be adjusted as shown in FIG. 8 . For example, in FIG. 8 , if the firmware holding unit 217 normally stores firmware related to app (1), OS (1), middleware (1), and FPGA (1), and the likelihood of the firmware related to OS (1), middleware (1), and FPGA (1) being changed is significantly lower than the likelihood of the firmware related to the apps being changed, the firmware holding unit 217 may store firmware related to app (1), app (2), app (3), and app (4). In this way, by storing firmware that is more likely to be changed in the firmware holding unit 217 of the communication device control unit 21, it is possible to increase the number of firmware combinations that can be quickly adapted.

[0050] Furthermore, in this embodiment, when storing data in the firmware storage unit 217 of the communication device control unit 21 of the communication device 20 or the firmware storage unit 224 of the communication package 22, the data storage order may be taken into consideration, as shown in the diagram from the upper right of FIG. 9 to the diagram from the lower right of FIG. 9. In other words, if the data storage order is not taken into consideration, the result will be as shown in the diagram from the upper left of FIG. 9 to the diagram from the lower right of FIG. 9, where the area used by the original app is insufficient for the modified app, and the entire memory must be relocated. On the other hand, if data with fewer variables is allocated from the beginning, the result will be as shown in the diagram from the upper right of FIG. 9 to the diagram from the lower right of FIG. 9, where the memory rewrite range can be minimized even if the size of the modified app increases. In other words, in order to reduce costs, the communication device 20 often has only the minimum amount of memory necessary and does not have ample usable capacity. Furthermore, unlike general environments such as PCs, the embedded software of the communication device 20 is equipped with operations required to perform basic device functions, but rarely includes functions related to efficient memory use (such as memory management and garbage collection), and therefore requires efficient use of limited memory. Therefore, the memory of the communication package 22 must be rewritten when the firmware is updated, and rewriting only the changed parts can speed up the writing process. However, if the firmware capacity increases or decreases, depending on the memory usage area, it may be necessary to reallocate memory in addition to the changed parts. Therefore, by allocating firmware with a low probability of change first, memory can be used quickly and efficiently even when a firmware update is required.

[0051] At least some of the functions of the server 10, communication control unit 21, and communication package 22 in the above-described embodiment may be implemented by a computer. In this case, a program for implementing this function may be recorded on a computer-readable recording medium, and the program may be loaded and executed by a computer system. The term "computer system" as used herein includes hardware such as an operating system (OS) and peripheral devices. The term "computer-readable recording medium" also refers to portable media such as flexible disks, optical magnetic disks, read-only memories (ROMs), and CD-ROMs, as well as storage devices such as hard disks built into computer systems. Furthermore, the term "computer-readable recording medium" may also include media that dynamically store programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or telephone lines, and media that store programs for a fixed period of time, such as volatile memory within the computer systems that serve as the server or client in such cases. Furthermore, the above program may be one that realizes part of the functions described above, or may be one that can realize the functions described above in combination with a program already recorded in a computer system, or may be one that is realized using a programmable logic device such as an FPGA.

[0052] Although an embodiment of the present invention has been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and includes designs within the scope of the gist of the present invention.

[0053] The present invention can be applied to communication devices and communication methods that require the communication device to operate using a communication package that holds appropriate firmware, even if the communication package installed in the communication device holds inappropriate firmware.

[0054] DESCRIPTION OF SYMBOLS 10...Server, 11...Firmware holding unit, 12...Transmitting / receiving unit, 20...Communication device, 21...Communication device control unit, 22...Communication package, 100...Communication system, 211...Transmitting / receiving unit, 212...Operation version management unit, 213...Configuration definition file holding unit, 214...Compatibility determination unit, 215...Transmitting / receiving unit, 216...Firmware separation unit, 217...Firmware holding unit, 218...Firmware combination unit, 221...Communication package control unit, 222...Hardware information management unit, 223...Transmitting / receiving unit, 224...Firmware holding unit

Claims

1. A communications device comprising: a firmware information acquisition unit that acquires firmware information regarding at least one piece of firmware held by a communications package installed in the communications device; a judgment unit that determines whether the at least one piece of firmware is appropriate for the communications package based on the firmware information acquired by the firmware information acquisition unit; and a firmware application unit that, when the judgment unit determines that the at least one piece of firmware is not appropriate for the communications package, acquires appropriate firmware for the communications package and applies it to the communications package.

2. The communication device of claim 1, further comprising a firmware holding unit that holds firmware applicable to the communication package in advance, and when the determination unit determines that the at least one firmware is not appropriate for the communication package, the firmware application unit obtains appropriate firmware for the communication package from the firmware holding unit or an external device, combines it with the appropriate firmware held by the communication package, and applies it to the communication package.

3. The communication device of claim 1, further comprising a correspondence information storage unit that stores correspondence information that associates the communication package with appropriate firmware for the communication package, and the judgment unit determines whether or not the at least one firmware is appropriate for the communication package based on the firmware information acquired by the firmware information acquisition unit and the correspondence information stored in the correspondence information storage unit.

4. A communication method used in a communication device, comprising: a firmware information acquisition step of acquiring firmware information relating to at least one piece of firmware held by a communication package mounted on the communication device; a determination step of determining whether or not the at least one piece of firmware is appropriate for the communication package based on the firmware information acquired in the firmware information acquisition step; and a firmware application step of acquiring appropriate firmware for the communication package and applying it to the communication package if it is determined in the determination step that the at least one piece of firmware is not appropriate for the communication package.

Images