COMMUNICATION SYSTEM, COMMUNICATION CONTROL DEVICE, AND CONTROL PROGRAM UPDATE METHOD
The communication system efficiently updates control programs by segregating the basic and unique parts into non-volatile and volatile memories, respectively, addressing the slow writing speed of non-volatile memories and reducing update time.
Patent Information
- Application Number
- JP2020109528
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-06-25
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2040-06-25
AI Technical Summary
Writable nonvolatile memories like FROM are slower to write to than volatile memories like DRAM, leading to increased writing time when the size of firmware increases due to addition of functions or debugging information.
A communication system with a communication control device that includes a non-volatile memory for storing a basic part of the control program and a volatile memory for storing a unique part, where the update control unit writes the basic part to the non-volatile memory and the unique part to the volatile memory during updates.
This approach suppresses the increase in update time of the control program even if its size increases, by leveraging the faster writing speed of volatile memory for the unique part.
Smart Images

Figure 0007581667000001 
Figure 0007581667000002 
Figure 0007581667000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a communication system, a communication control device, and a control program update method. [Background technology]
[0002] Patent Document 1 discloses a method for updating firmware (control program) of a network device. In the method disclosed in Patent Document 1, when an accessory device is added to a main device, which is a network device, the firmware for the main device is downloaded from a service site, the firmware is temporarily stored in a working RAM area inside the main device, and the downloaded firmware is written to a FROM (Flash Read Only Memory) inside the main device. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2003-167742 A Summary of the Invention [Problem to be solved by the invention]
[0004] However, write-enabled non-volatile memory such as FROM is slower to write than volatile memory such as DRAM (Dynamic Random Access Memory), etc. Therefore, when the size of the firmware increases due to the addition of functions or debug information, the time required to write to FROM also increases. [Means for solving the problem]
[0005] A communication system according to one aspect of the present disclosure is a communication system including a communication control device that controls communication with an opposing device, the communication control device including a non-volatile memory that stores a basic part that is part of a control program of the communication control device, a volatile memory that stores a unique part that is a part other than the basic part of the control program, and an update control unit that updates the control program, and when updating the control program, the update control unit writes the basic part of a new control program to the non-volatile memory and writes the unique part of the new control program to the volatile memory without writing it to the non-volatile memory.
[0006] A communication control device according to one aspect of the present disclosure is a communication control device that controls communication with an opposing device, and is equipped with a non-volatile memory that stores a basic part that is part of a control program of the communication control device, a volatile memory that stores a unique part that is a part other than the basic part of the control program, and an update control unit that updates the control program, and when updating the control program, the update control unit writes the basic part of a new control program to the non-volatile memory and writes the unique part of the new control program to the volatile memory without writing it to the non-volatile memory.
[0007] A control program update method according to one aspect of the present disclosure is a control program update method in a communication control device that controls communication with a counterpart device, and includes the steps of: writing a basic part of a new control program into a non-volatile memory that stores a basic part that is part of the control program; and writing a unique part of the new control program that is a part other than the basic part into a volatile memory that stores the unique part of the control program without writing the unique part into the non-volatile memory.
[0008] The present disclosure can be realized not only as a communication system having the above-mentioned characteristic configuration, but also as a communication control device included in the communication system, or as a control program update method having characteristic processes in the communication system as steps. Furthermore, the present disclosure can be realized as a computer program executed by the communication control device. Effect of the Invention
[0009] According to the present disclosure, even if the size of a control program increases, an increase in the update time of the control program can be suppressed. [Brief description of the drawings]
[0010] [Figure 1] 1 is a diagram illustrating an example of an overall configuration of a network system according to an embodiment. [Diagram 2] 2 is a block diagram showing an example of an internal configuration of a station side device according to an embodiment; [Diagram 3] FIG. 4 is a schematic diagram showing an example of a configuration of a control program according to the embodiment. [Figure 4] FIG. 2 is a functional block diagram showing an example of functions of a line control device according to the present embodiment. [Diagram 5] FIG. 11 is a diagram showing an example of the configuration of a first configuration list. [Figure 6] FIG. 11 is a diagram showing an example of the configuration of a second configuration list. [Figure 7] 10 is a flowchart showing an example of a procedure for updating a control program of a line control device according to an embodiment; [Figure 8A] 4 is a flowchart showing an example of a start-up sequence of the line control device according to the embodiment. [Figure 8B] 4 is a flowchart showing an example of a start-up sequence of the line control device according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] <Overview of the embodiment of the present disclosure> Below, an overview of the embodiments of the present disclosure will be listed and described.
[0012] (1) The communication system according to the present embodiment is a communication system including a communication control device that controls communication with a partner device, the communication control device including a non-volatile memory that stores a basic part that is a part of a control program of the communication control device, a volatile memory that stores a unique part that is a part other than the basic part of the control program, and an update control device that updates the control program, and when updating the control program, the update control device writes the basic part of a new control program to the non-volatile memory, and writes the unique part of the new control program to the volatile memory without writing it to the non-volatile memory. As a result, only the basic part of the control program is written to the non-volatile memory, which has a low write speed, and the unique part is written to the volatile memory, which has a high write speed. Therefore, even if the size of the control program increases, the increase in the update time of the control program can be suppressed.
[0013] (2) In the communication system according to this embodiment, the communication control device may include a first acquisition unit that acquires the basic part of the new control program when the basic part needs to be updated, and the update control unit may write the acquired basic part of the new control program to the non-volatile memory. This makes it possible to update only the basic part without updating the unique part, for example, when only the basic part needs to be updated. This reduces the time required to write the unique part, and further suppresses an increase in the time required to update the control program.
[0014] (3) In the communication system according to this embodiment, the communication control device may include a second acquisition unit that acquires the unique part of the new control program when the unique part needs to be updated, and the update control unit may write the acquired unique part of the new control program to the volatile memory without writing it to the non-volatile memory. This makes it possible to update only the unique part without updating the basic part, for example, when only the unique part needs to be updated. This reduces the time required to write the basic part, and further suppresses an increase in the time required to update the control program.
[0015] (4) In the communication system according to the present embodiment, the communication control device may include a first consistency determination unit, which executes a first consistency determination process in a startup sequence for starting the control program to determine whether the basic part of the started control program is consistent with the basic part of a control program stored in a providing device that provides a control program for update, and the update control unit may write the basic part of the control program provided by the providing device to the non-volatile memory when a result of the first consistency determination process is negative. This allows the basic part to be written to the non-volatile memory, for example, not only when the basic part has not been updated, but also when a part or all of the basic part in the non-volatile memory is damaged or lost.
[0016] (5) In the communication system according to the present embodiment, the communication control device includes a second consistency determination unit, which executes a second consistency determination process in a startup sequence for starting the control program to determine whether the unique part of the started control program is consistent with a unique part of a control program stored in a providing device that provides an update control program, and the update control unit may write the unique part of the control program provided by the providing device to the volatile memory without writing it to the non-volatile memory when a result of the second consistency determination process is negative. This makes it possible to write the unique part to the volatile memory, for example, not only when the unique part has not been updated, but also when a part or all of the unique part of the volatile memory has been damaged or lost.
[0017] (6) In the communication system according to the present embodiment, when a part of the unique part of the control program is provided from the providing device, the update control unit may write the part of the unique part provided to the volatile memory without writing it to the non-volatile memory, and the communication control device may start the part of the unique part written to the volatile memory. This makes it possible to write only the necessary part of the unique part to the non-volatile memory, thereby preventing an increase in the writing time.
[0018] (7) In the communication system according to the present embodiment, the basic part may include a boot loader, an operating system, and a program used in the second consistency determination process, and the unique part may include a program used to control communication with the opposing device. As a result, a basic function part of the control program is included in the basic part, and a function part unique to the communication control device is included in the unique part. Therefore, a part or all of the function addition part that causes an increase in the size of the control program can be included in the unique part, and an increase in the update time of the control program can be suppressed.
[0019] (8) The communication system according to the present embodiment may further include a management device that manages the plurality of communication control devices, and the management device may transmit a control program for updating to the plurality of communication control devices. In this way, the management device can be used to smoothly update the control programs of the plurality of communication control devices.
[0020] (9) The communication control device according to the present embodiment is a communication control device that controls communication with an opposing device, and includes a non-volatile memory that stores a basic part that is a part of a control program of the communication control device, a volatile memory that stores a unique part that is a part other than the basic part of the control program, and an update control unit that updates the control program. When updating the control program, the update control unit writes the basic part of a new control program to the non-volatile memory, and writes the unique part of the new control program to the volatile memory without writing it to the non-volatile memory. As a result, only the basic part of the control program is written to the non-volatile memory, which has a low write speed, and the unique part is written to the volatile memory, which has a high write speed. Therefore, even if the size of the control program increases, the increase in the update time of the control program can be suppressed.
[0021] (10) A control program update method according to this embodiment is a control program update method in a communication control device that controls communication with a partner device, and includes the steps of: writing a basic part of a new control program to a non-volatile memory that stores a basic part that is a part of the control program; and writing a unique part of the new control program, which is a part other than the basic part, to a volatile memory that stores the unique part of the control program, without writing the unique part to the non-volatile memory. As a result, only the basic part of the control program is written to the non-volatile memory, which has a low write speed, and the unique part is written to the volatile memory, which has a high write speed. Therefore, even if the size of the control program increases, an increase in the update time of the control program can be suppressed.
[0022] <Details of the embodiment of the present disclosure> Hereinafter, the details of the embodiments of the present invention will be described with reference to the drawings. Note that at least some of the embodiments described below may be combined in any desired manner.
[0023] In the following embodiment, an example will be described in which the communication system is an optical communication station device. However, the communication system is not limited to the optical communication device. The communication system according to the present embodiment may be a communication device other than the optical communication device, such as a wireless communication device or a wired communication device.
[0024] [1. Network system configuration] Fig. 1 is a diagram showing an example of the overall configuration of a network system according to this embodiment. As shown in Fig. 1, a network system 10 is an optical access system, and includes an optical line terminal (OLT) 11, a plurality of optical network units (ONUs) 12, and a passive optical network (PON) line 13. Note that in this embodiment, an Ethernet PON such as GE-PON (Gigabit Ethernet-PON) and 10G-EPON (10 Gigabit Ethernet PON) will be described ("Ethernet" and "ETHERNET" are registered trademarks).
[0025] An upper network 50 such as the Internet is connected to the L2 switch 23 (see FIG. 2) of the OLT 11.
[0026] A user communication device capable of Ethernet communication can be connected to a UNI (User Network Interface) port (not shown) of the ONU 12. The number and type of user communication devices connected to the ONU 12 are not particularly limited. For example, the user communication device may be a terminal such as a personal computer, or a relay device such as a router or a gateway. In other words, the ONU 12 may be connected to a network via a relay device.
[0027] A plurality of PON lines 13 are connected to the OLT 11. The PON line 13 is an optical communication line equipped with an optical splitter 14 and optical fibers 15 and 16. The PON line 13 includes one trunk optical fiber 15 and a plurality of branch optical fibers 16. Each of the optical fibers 15 and 16 is connected to the optical splitter 14. An optical signal transmitted from the OLT 11 passes through the trunk optical fiber 15 of the PON line 13 and is branched by the optical splitter 14. The branched optical signal is transmitted to each ONU 12 through the branch optical fibers 16.
[0028] The optical signals transmitted from each ONU 12 pass through branch optical fibers 16 and are converged by the optical splitter 14. The converged optical signals are transmitted to the OLT 11 through the trunk optical fiber 15. The optical splitter 14 used in the PON line 13 does not require an external power supply and passively branches or multiplexes optical signals from the input optical signals.
[0029] After the connection between the OLT 11 and the ONU 12 is established, the user communication device can access the upper network 50 via the ONU 12 and the OLT 11. The upstream optical signals transmitted to the branch optical fibers 16 are merged in the optical splitter 14. Therefore, multiplexing is required to prevent collisions between optical signals of the same wavelength after merging. In the network system 10, time division multiplexing is performed in accordance with the MPCP. Specifically, the OLT 11 calculates the upstream transmission start time and the permitted transmission amount of data stored inside the ONU 12 based on the control frame (report) transmitted from each ONU 12.
[0030] Next, OLT 11 transmits a control frame (gate) with an indication signal inserted to each ONU 12 via PON line 13. Each ONU 12 notifies OLT 11 of the length of data in its own buffer in a report at the time specified by the gate. Each ONU 12 receives the gate with the indication signal inserted from OLT 11. Based on the indication signal, each ONU 12 transmits the data in its own buffer together with a report to OLT 11.
[0031] [2. Internal structure of OLT] FIG. 2 is a block diagram showing an example of the internal configuration of the OLT 11. As shown in FIG. As shown in FIG. 2, the OLT 11 includes one management device 21, a plurality of line controllers 22, and an L2 switch .
[0032] [2.1. Configuration of line control device] The line control device 22 controls communication in the PON line 13. The line control device 22 is, for example, a "PON unit" that operates as an OSU (Optical Subscriber Unit) of the PON. The line control device 22 is, for example, a circuit module that can be attached and detached in the housing of the OLT 11. The line control device 22 is a communication control device that controls communication with the ONU 12, which is the opposing device.
[0033] The line controller 22 includes a processor 221 , a non-volatile memory 222 , a volatile memory 223 , a PON processing unit 224 , a PHY 225 which is a transceiver, and an optical transceiver 226 .
[0034] The volatile memory 223 is, for example, a dynamic random access memory (DRAM). The volatile memory 223 may be a static random access memory (SRAM). The non-volatile memory 222 is, for example, a flash read only memory (FROM). The non-volatile memory 222 may be an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), or a hard disk. The non-volatile memory 222 stores a basic part 310 that is a part of a control program 300 (see FIG. 3) that is a computer program. The volatile memory 223 stores a specific part 320 that is a part of the control program 300 other than the basic part 310. The processor 221 is a CPU. Each function of the line control device 22 is realized by the processor 221 executing the control program 300. A detailed configuration of the control program 300 will be described later.
[0035] The PHY 225 is a device corresponding to the physical layer in the OSI reference model, for example, a transceiver for backplane Ethernet. The PHY 225 is connected to the PHY 215, which is a transceiver of the management device 21. The PHY 225 and the PHY 215 are connected to the processor 221 and the processor 211, respectively. This allows the processor 221 of the line control device 22 to communicate with the processor 211 of the management device 21.
[0036] The optical transceiver 226 is an optical device (for example, a pluggable optical transceiver) including a circuit for transmitting and receiving an optical signal. The optical transceiver 226 is optically connected to the trunk optical fiber 15 (see FIG. 1) and electrically connected to the PON processing unit 224. The optical transceiver 226 converts between optical and electrical signals. That is, the optical transceiver 226 converts an upstream optical signal from the ONU 12 into an electrical signal. The optical transceiver 226 converts a downstream electrical signal from the PON processing unit 224 into an optical signal.
[0037] The PON processing unit 224 is made up of an integrated circuit that executes predetermined communication processing in accordance with the PON communication standard. When the upstream signal is a control frame (report) from an ONU 12, the PON processing unit 224 determines the upstream transmission start time and permitted transmission amount for the ONU 12, and notifies the ONU 12 of the control frame (gate).
[0038] If the frame included in the upstream signal is a data frame to the upper network 50 , the PON processing unit 224 transmits the frame to the L2 switch 23 . If a frame included in the downstream signal is a data frame for the ONU 12, the PON processing unit 224 causes the optical transceiver 226 to transmit the frame.
[0039] The L2 switch 23 is made up of an integrated circuit that determines a transmission port according to the destination of a received L2 layer frame. When a frame contained in a downstream signal from the upper network 50 is addressed to an ONU 12 , the L2 switch 23 transmits the frame to the corresponding PON processing unit 224 .
[0040] When a frame included in the upstream signal from the PON processing unit 224 is a data frame to the upper network 50 , the L2 switch 23 transmits the frame to the upper network 50 .
[0041] [2.2. Management device configuration] The management device 21 is connected to a plurality of line control devices 22 and manages each of the line control devices 22. The management device 21 manages updates of the control programs 300 in the line control devices 22. The management device 21 is, for example, a circuit module that can be attached to and detached from the housing of the OLT 11.
[0042] The management device 21 includes a processor 211 , a non-volatile memory 212 , a volatile memory 213 , an interface 214 , and a PHY 215 .
[0043] The volatile memory 213 is, for example, a DRAM. The volatile memory 213 may be, for example, an SRAM. The nonvolatile memory 212 is, for example, a FROM. The nonvolatile memory 212 may be, for example, an EPROM, an EEPROM, or a hard disk. The nonvolatile memory 212 stores a computer program for realizing the functions of the management device 21. The processor 211 is a CPU. Each function of the management device 21 is realized by the processor 211 executing the computer program stored in the nonvolatile memory 212.
[0044] The PHY 215 is a device corresponding to the physical layer in the OSI reference model, for example, a transceiver for backplane Ethernet. The PHY 215 is connected to the PHY 225, which is a transceiver of each line controller 22. This allows the processor 211 of the management device 21 to communicate with the processor 221 of the line controller 22.
[0045] The interface 214 can exchange data with external devices. The interface 214 is an input / output device, and includes, for example, a Universal Serial Bus (USB) port or an SD card slot. Furthermore, the interface 214 may be a network interface, for example, an Ethernet interface. A flash memory (USB memory) 24 connectable to a USB port and a flash memory (SD card) 25 connectable to an SD card slot are connected to the interface 214. Furthermore, the interface 214 is connected to a maintenance terminal 26 or a server 27 via a management network 51.
[0046] [3. Control program configuration] 3 is a schematic diagram showing an example of the configuration of a control program according to this embodiment. As described above, the control program 300 includes a basic part 310 and a specific part 320.
[0047] The basic part 310 is a framework of the control program 300, and includes a boot loader 311 and an OS (operating system) 312. Furthermore, the basic part 310 includes a communication control program (PG) 313, a module control PG 314, an update control PG 315, a first consistency determination PG 316, and a second consistency determination PG 317. The communication control PG 313 is a program or program module for controlling communication with the ONU 12. The module control PG 314 is a program or program module for controlling each component of the line control device 22, and includes a plurality of device drivers. The update control PG 315 is a program or program module for controlling the update of the control program 300. The first consistency determination PG 316 is a program or program module for determining whether or not the basic part 310 needs to be updated. The second consistency determination PG 317 is a program or program module for determining whether or not the unique part 320 needs to be updated. Furthermore, the basic part 310 includes first configuration information 318 indicating files that constitute the basic part 310. The first configuration information 318 includes a communication control program (PG) 313, a module control program 314, an update control program 315, a first consistency determination program 316, a second consistency determination program 317, and the file names and paths (absolute paths) of the libraries used by each of these programs.
[0048] The basic part 310 is stored in the non-volatile memory 222 of the line controller 22 .
[0049] The unique part 320 is a part that realizes functions unique to the line control device 22, and includes an alarm management PG 321, a line management PG 322, a line control PG 323, debug information 324, and second configuration information 325. The alarm management PG 321 is a program or program module for detecting and notifying an abnormality occurring in communication in the PON line 13. The line management PG 322 is a program or program module for managing communication in the PON line 13. The line control PG 323 is a program or program module for controlling communication in the PON line 13. The debug information 324 is data used for debugging the control program 300. The second configuration information 325 includes the file names and paths (absolute paths) of the alarm management PG 321, the line management PG 322, the line control PG 323, and libraries used by each of these programs.
[0050] The unique part 320 is stored in the volatile memory 223 of the line controller 22 .
[0051] [4. Functions of the line control device] 4 is a functional block diagram showing an example of the functions of the line control device according to this embodiment. The line control device 22 has the functions of a first list request unit 231, a first list creation unit 232, a first consistency determination unit 233, a first acquisition unit 234, an update control unit 236, a second list request unit 237, a second list creation unit 238, a second consistency determination unit 239, and a second acquisition unit 240.
[0052] The management device 21 can receive update program data 330, which is data for updating the control program 300, from an external device connected to the interface 214. That is, when distribution of a new version of the update program data 330 starts, the external device transmits the update program data 330 to the management device 21. The update program data 330 is stored in the nonvolatile memory 212. The update program data 330 stored in the nonvolatile memory 212 is transmitted to each line control device 22, and each line control device 22 uses the update program data 330 to update the control program 300.
[0053] The update program data 330 includes the basic part 310 and the unique part 320 of the new version of the control program 300. In other words, the update program data 330 of the entire control program 300 including the basic part 310 and the unique part 320 is stored in the non-volatile memory 212. When updating the control program 300, there are cases where only the basic part 310 is updated, or only the unique part 320 is updated. When only the basic part 310 is updated, the update program data 330 includes only the updated part of the basic part 310. When only the unique part 320 is updated, the update program data 330 includes only the updated part of the unique part 320.
[0054] The update program data 330 includes a first configuration list 310A and a second configuration list 320A. FIG. 5 is a diagram showing an example of the configuration of the first configuration list. The first configuration list 310A is a table including a file name field and a hash value field. The file name field stores the file name and path (absolute path of the installation destination) of each file (boot loader 311, OS 312, communication control PG 313, module control PG 314, update control PG 315, first consistency determination PG 316, second consistency determination PG 317, libraries used by each program, etc.) that constitute the new version of the basic part 310. The hash value field stores a hash value calculated for each file. The hash value is used to verify the identity of the file. That is, the hash value is calculated for each file that constitutes the basic part 310 by applying the contents of the file to a hash function. The hash value is a value calculated by an existing cryptographic hash function such as MD5 (Message Digest Algorithm 5), SHA (Secure Hash Algorithm 1)-1, SHA-256, etc. Instead of the hash value, a value calculated by an error detection code algorithm such as CRC (Cyclic Redundancy Check) can also be used.
[0055] 6 is a diagram showing an example of the configuration of the second configuration list. The second configuration list 320A is a table including a file name field and a hash value field. The file name field stores the file name and path (absolute path of the installation destination) of each file (alarm management PG 321, line management PG 322, line control PG 323, debug information 324, libraries used by each program, etc.) that configures the unique part 320 of the new version. The hash value field stores a hash value calculated for each file.
[0056] The first list request unit 231 requests the first configuration list 310A from the management device 21. The management device 21 transmits the first configuration list 310A to the requesting line control device 22. The first list request unit 231 receives the first configuration list 310A transmitted from the management device 21.
[0057] The first list creation unit 232 creates a first configuration list for the control program 300 (hereinafter also referred to as the "current program") currently in operation. Specifically, the first list creation unit 232 calculates a hash value for each configuration file of the basic unit 310 stored in the non-volatile memory 222. The first list creation unit 232 creates a first configuration list including the file name of each file and the calculated hash value.
[0058] The first consistency determination unit 233 executes a first consistency determination process to determine whether the basic part 310 of the current program is consistent with the basic part 310 of a new version of a control program (hereinafter also referred to as the "new program"). Specifically, the first consistency determination unit 233 compares the first configuration list 310A transmitted from the management device 21 with the first configuration list created by the first list creation unit 232, and determines whether the two match. If the two match, the basic part 310 of the new program and the basic part 310 of the current program are identical (matched), and if they do not match, the basic part 310 of the new program and the basic part 310 of the current program are not identical (not matched).
[0059] For example, the result of the first consistency determination process will be negative not only when the basic part 310 is updated, but also when some of the files of the basic part 310 in the non-volatile memory 222 are damaged or lost.
[0060] The first acquisition unit 234 acquires the basic part 310 of the new program when the basic part 310 needs to be updated. In other words, when the first consistency determination unit 233 determines that the basic part 310 of the new program does not match the basic part 310 of the current program, the first acquisition unit 234 requests the management device 21 for update program data 330 including the basic part 310 of the new program. The management device 21 transmits the update program data 330 to the line control device 22 that has made the request. The first acquisition unit 234 receives the update program data 330 transmitted from the management device 21.
[0061] When updating the control program 300, the update control unit 236 writes the basic part 310 of the new program to the non-volatile memory 222, and writes the unique part 320 of the new program to the volatile memory 223. That is, the update control unit 236 writes the basic part 310 acquired by the first acquisition unit 234 to the non-volatile memory 222. Furthermore, the update control unit 236 writes the unique part 320 acquired by the second acquisition unit 240 to the volatile memory 223, as described below.
[0062] If the result of the first consistency determination process is negative in the start-up sequence of the control program 300, the update control unit 236 writes the basic part 310 of the new program provided by the management device 21 to the non-volatile memory 222. As a result, the basic part 310 installed in the non-volatile memory 222 is updated to the basic part 310 of the new version.
[0063] For example, even if the basic part 310 is not upgraded but some files of the basic part 310 in the non-volatile memory 222 are corrupted or lost, the first acquisition unit 234 requests the management device 21 for the latest version of the basic part 310 of the control program 300. If the corrupted basic part 310 is the latest version, the acquired version of the basic part 310 is the same as the version of the corrupted basic part 310. Therefore, in this case, the basic part 310 is not upgraded but the current version of the basic part 310 is restored.
[0064] The second list request unit 237 requests the second configuration list 320A from the management device 21. The management device 21 transmits the second configuration list 320A to the requesting line control device 22. The second list request unit 237 receives the second configuration list 320A transmitted from the management device 21.
[0065] The second list creation unit 238 creates a second configuration list for the current program. Specifically, the second list creation unit 238 calculates a hash value for each configuration file of the unique part 320 stored in the volatile memory 223. The second list creation unit 238 creates a second configuration list including the file name of each file and the calculated hash value.
[0066] The second consistency determination unit 239 executes a second consistency determination process to determine whether the unique part 320 of the current program is consistent with the unique part 320 of the new program. Specifically, the second consistency determination unit 239 compares the second configuration list 320A transmitted from the management device 21 with the second configuration list created by the second list creation unit 238, and determines whether the two match. If the two match, the unique part 320 of the new program and the unique part 320 of the current program are identical (matched), and if they do not match, the unique part 320 of the new program and the unique part 320 of the current program are not identical (not matched).
[0067] For example, when the volatile memory 223 is a DRAM, periodic refresh (memory retention operation) is required to prevent loss of retained information. For this reason, the memory controller in the processor 211 periodically issues a refresh command. For example, when the basic unit 310 is restarted, a refresh command may not be issued during a part of the startup sequence. For this reason, when the basic unit 310 is restarted, the information retained in the DRAM cannot necessarily be guaranteed. In other words, during the period when the refresh is not performed, a part or all of the information stored in the volatile memory 223 may be damaged or lost. In this way, even when some files in the unique unit 320 in the volatile memory 223 are damaged or lost, the result of the second consistency determination process is negative.
[0068] The second acquisition section 240 acquires the unique part 320 of the new program when it is necessary to update the unique part 320. In other words, when the second consistency determination section 239 determines that the unique part 320 of the new program does not match the unique part 320 of the current program, the second acquisition section 240 requests the management device 21 for update program data 330 including the unique part 320 of the new program. The management device 21 transmits the update program data 330 to the line control device 22 that has made the request. The second acquisition section 240 receives the update program data 330 transmitted from the management device 21.
[0069] The update control unit 236 writes the unique part 320 acquired by the second acquisition unit 240 into the volatile memory 223.
[0070] If the result of the second consistency determination process is negative in the start-up sequence of the control program 300, the update control unit 236 writes the unique part 320 of the new program provided by the management device 21 into the volatile memory 223. As a result, the unique part 320 installed in the volatile memory 223 is updated to the unique part 320 of the new version.
[0071] For example, even if the specific part 320 is not upgraded but some files of the specific part 320 in the volatile memory 223 are corrupted or lost, the second acquisition unit 240 requests the management device 21 for the latest version of the specific part 320 of the control program 300. If the corrupted specific part 320 is the latest version, the acquired version of the specific part 320 is the same as the version of the corrupted specific part 320. Therefore, in this case, the specific part 320 is not upgraded but the current version of the specific part 320 is repaired.
[0072] [5. Operation of the line control device] FIG. 7 is a flowchart showing an example of a procedure for updating a control program of the line control device according to the present embodiment.
[0073] The processor 221 requests the first configuration list 310A of the new program from the management device 21. Upon receiving the request, the processor 211 of the management device 21 reads the first configuration list 310A from the non-volatile memory 212 and transmits it to the requesting line control device 22. The line control device 22 receives the first configuration list 310A transmitted from the management device 21 (step S101).
[0074] The processor 221 creates a first configuration list of the current program (step S102). In this process, the processor 221 reads the first configuration information from the non-volatile memory 222 and calculates a hash value for each configuration file in the basic unit 310. The processor 221 creates the first configuration list by combining the file name of the first configuration information with the calculated hash value.
[0075] The processor 221 compares the received first configuration list 310A with the created first configuration list (step S103).
[0076] If the received first configuration list 310A does not match the created first configuration list (NO in step S104), the processor 221 determines that the basic part 310 of the new program and the basic part 310 of the current program are not consistent. In this case, the processor 221 requests the management device 21 for update program data 330. Upon receiving the request, the processor 211 of the management device 21 reads the update program data 330 from the non-volatile memory 212 and transmits it to the line control device 22 that made the request. The line control device 22 receives the update program data 330 transmitted from the management device 21 (step S105).
[0077] The processor 221 deletes the basic part 310 of the current program from the non-volatile memory 222 (step S106). Here, when a part of the basic part 310 is updated, the processor 221 can delete only the part to be updated.
[0078] The processor 221 writes the configuration files of the basic part 310 included in the received update program data 330 to the non-volatile memory 222 (step S107). If the update program data 330 is a compressed archive file, the processor 221 decompresses the update program data, obtains the configuration files of the basic part 310, and writes these files to the non-volatile memory 222.
[0079] When the installation of the basic part 310 is completed, the processor 221 restarts the line control device 22 (step S108). If the update target of the control program 300 includes not only the basic part 310 but also the specific part 320, the update of the specific part 320 is executed after the line control device 22 is restarted.
[0080] If the received first configuration list 310A and the created first configuration list match (YES in step S104), the processor 221 determines that the basic part 310 of the new program and the basic part 310 of the current program are consistent. In this case, there is no need to update the basic part 310.
[0081] The processor 221 requests the second configuration list 320A of the new program from the management device 21. Upon receiving the request, the processor 211 of the management device 21 reads the second configuration list 320A from the non-volatile memory 212 and transmits it to the requesting line control device 22. The line control device 22 receives the second configuration list 320A transmitted from the management device 21 (step S109).
[0082] The processor 221 creates a second configuration list of the current program (step S110). In this process, the processor 221 reads the second configuration information from the volatile memory 223 and calculates a hash value for each configuration file of the unique part 320. The processor 221 creates the second configuration list by combining the file names in the second configuration information with the calculated hash values.
[0083] The processor 221 compares the received second configuration list 320A with the created second configuration list (step S111).
[0084] If the received second configuration list 320A does not match the created second configuration list (NO in step S112), the processor 221 determines that the unique part 320 of the new program and the unique part 320 of the current program are not consistent. In this case, the processor 221 requests the management device 21 for update program data 330. Upon receiving the request, the processor 211 of the management device 21 reads the update program data 330 from the non-volatile memory 212 and transmits it to the line control device 22 that made the request. The line control device 22 receives the update program data 330 transmitted from the management device 21 (step S113).
[0085] If the update program data 330 has already been received in step S105, the process of step S113 can be omitted.
[0086] The processor 221 deletes the unique part 320 of the current program from the volatile memory 223 (step S114). Here, when a part of the unique part 320 is updated, the processor 221 can delete only the part to be updated.
[0087] The processor 221 writes the configuration files of the unique part 320 included in the received update program data 330 to the volatile memory 223 (step S115). If the update program data 330 is a compressed archive file, the processor 221 decompresses the update program data, obtains the configuration files of the unique part 320, and writes these files to the volatile memory 223. This completes the update (or repair) of the unique part 320.
[0088] When the installation of the unique part 320 is completed, the processor 221 restarts the updated part of the unique part 320 (step S116). This eliminates the need to restart the entire control program 300. This makes it possible to avoid a temporary stop in the function of the line control device 22 caused by the restart of the basic part 310. This completes the update operation of the control program 300.
[0089] Next, a description will be given of the start-up sequence of the line control device 22. Figures 8A and 8B are flowcharts showing an example of the start-up sequence of the line control device according to this embodiment. Figure 8A shows the first half of the start-up sequence, and Figure 8B shows the second half thereof.
[0090] The processor 221 reads the boot loader 311 from the nonvolatile memory 222 and starts the boot loader 311 (step S201). The processor 221 reads the OS 312 from the nonvolatile memory 222 and starts the OS 312 (step S202). Note that starting up the programs (the boot loader 311, the OS 312, the communication control PG 313, the module control PG 314, the update control PG 315, the first consistency determination PG 316, and the second consistency determination PG 317) stored in the nonvolatile memory 222 includes transferring the programs from the low-speed nonvolatile memory 222 to the high-speed volatile memory 223 and then executing them.
[0091] The processor 221 reads the communication control PG 313 from the nonvolatile memory 222, and starts the communication control PG 313. The processor 221 reads the module control PG 314 from the nonvolatile memory 222, and starts the module control PG 314 (step S203).
[0092] The processor 221 reads the first consistency determination PG 316 from the non-volatile memory 222, and starts the first consistency determination PG 316 (step S204).
[0093] The processor 221 requests the first configuration list 310A of the new program from the management device 21. Upon receiving the request, the processor 211 of the management device 21 reads the first configuration list 310A from the non-volatile memory 212 and transmits it to the requesting line control device 22. The line control device 22 receives the first configuration list 310A transmitted from the management device 21 (step S205).
[0094] The processor 221 creates a first configuration list of the current program (step S206). In this process, the processor 221 reads the first configuration information from the non-volatile memory 222 and calculates a hash value for each configuration file in the basic unit 310. The processor 221 creates the first configuration list by combining the file name of the first configuration information with the calculated hash value.
[0095] The processor 221 compares the received first configuration list 310A with the created first configuration list (step S207).
[0096] If the received first configuration list 310A does not match the created first configuration list (NO in step S208), the processor 221 determines that the basic part 310 of the new program and the basic part 310 of the current program are not consistent. In this case, the processor 221 reads the update control PG 315 from the non-volatile memory 222 and starts the update control PG 315 (step S209). The processor 221 requests the management device 21 for update program data 330. Upon receiving the request, the processor 211 of the management device 21 reads the update program data 330 from the non-volatile memory 212 and transmits it to the line control device 22 that made the request. The line control device 22 receives the update program data 330 transmitted from the management device 21 (step S210).
[0097] The processor 221 deletes the basic part 310 of the current program from the non-volatile memory 222 (step S211). If a part of the basic part 310 between the new program and the current program is inconsistent, the processor 221 can delete only the inconsistent part of the basic part 310.
[0098] The processor 221 writes the configuration files of the basic part 310 included in the received update program data 330 to the non-volatile memory 222 (step S212). If the update program data 330 is a compressed archive file, the processor 221 decompresses the update program data, obtains the configuration files of the basic part 310, and writes these files to the non-volatile memory 222. This completes the update or repair of the basic part 310.
[0099] When the installation of the basic part 310 is completed, the processor 221 restarts the line control device 22 (step S213). If the update target of the control program 300 includes not only the basic part 310 but also the specific part 320, the update of the specific part 320 is executed after the line control device 22 is restarted.
[0100] If the received first configuration list 310A and the created first configuration list match (YES in step S208), the processor 221 determines that the basic part 310 of the new program and the basic part 310 of the current program are consistent. In this case, there is no need to update the basic part 310.
[0101] The processor 221 reads the second consistency determination program 317 from the non-volatile memory 222, and starts the second consistency determination program 317 (step S214).
[0102] The processor 221 requests the second configuration list 320A of the new program from the management device 21. Upon receiving the request, the processor 211 of the management device 21 reads the second configuration list 320A from the non-volatile memory 212 and transmits it to the requesting line control device 22. The line control device 22 receives the second configuration list 320A transmitted from the management device 21 (step S215).
[0103] The processor 221 creates a second configuration list of the current program (step S216). In this process, the processor 221 reads the second configuration information from the volatile memory 223 and calculates a hash value for each configuration file of the unique part 320. The processor 221 creates the second configuration list by combining the file names in the second configuration information with the calculated hash values.
[0104] The processor 221 compares the received second configuration list 320A with the created second configuration list (step S217).
[0105] If the received second configuration list 320A does not match the created second configuration list (NO in step S218), the processor 221 determines that the unique part 320 of the new program and the unique part 320 of the current program are not consistent. In this case, the processor 221 reads the update control PG 315 from the non-volatile memory 222 and starts the update control PG 315 (step S219). The processor 221 requests the management device 21 for update program data 330. Upon receiving the request, the processor 211 of the management device 21 reads the update program data 330 from the non-volatile memory 212 and transmits it to the line control device 22 that made the request. The line control device 22 receives the update program data 330 transmitted from the management device 21 (step S220).
[0106] If the update program data 330 has already been received in step S210, the process of step S220 can be omitted.
[0107] The processor 221 deletes the unique part 320 of the current program from the volatile memory 223 (step S221). If a part of the unique part 320 between the new program and the current program is inconsistent, the processor 221 can delete only the inconsistent part of the unique part 320.
[0108] The processor 221 writes the configuration files of the unique part 320 included in the received update program data 330 to the volatile memory 223 (step S222). If the update program data 330 is a compressed archive file, the processor 221 decompresses the update program data, obtains the configuration files of the unique part 320, and writes these files to the volatile memory 223. This completes the update or repair of the unique part 320.
[0109] If the received second configuration list 320A matches the created second configuration list (YES in step S218), the processor 221 determines that the unique part 320 of the new program and the unique part 320 of the current program are consistent. In this case, the processor 221 reads the update control PG 315 from the non-volatile memory 222 and starts the update control PG 315 (step S223). However, the unique part 320 is not updated.
[0110] After step S222 or S223, the processor 221 reads out the alarm management PG 321 from the volatile memory 223 and starts up the alarm management PG 321. The processor 221 reads out the line management PG 322 from the volatile memory 223 and starts up the line management PG 322. The processor 221 reads out the line control PG 323 from the volatile memory 223 and starts up the line control PG 323 (step S224). This completes the start-up sequence of the line control device 22.
[0111] [6. Modifications] In the above-described embodiment, the basic part 310 and the unique part 320 are updated separately, but the present invention is not limited to this. When the control program 300 is to be updated for both the basic part 310 and the unique part 320, the basic part 310 and the unique part 320 can be updated together. That is, the processor 221 may write the basic part 310 included in the update program data 330 to the non-volatile memory 222, and write the unique part 320 to the volatile memory 223.
[0112] In the above-mentioned embodiment, the configuration in which the management device 21 and the multiple line control devices 22 are arranged in one housing has been described, but the present invention is not limited to this. One management device 21 and one line control device 22 may be provided in the housing of the OLT 11. Furthermore, the configuration in which the management device 21 is omitted may be used. For example, multiple line control devices 22 may be arranged in the housing of the OLT 11, one line control device 22 may function as a master device, and the other line control devices 22 may function as slave devices. The update program data 330 may be stored in the non-volatile memory of the master device, and when updating the control program in the slave device, the master device may provide the update program data 330 to the slave device. As yet another example, the line control device 22 may download the update program data from an external device (USB memory 24, SD card 25, maintenance terminal 26, server 27, etc.).
[0113] Furthermore, the management device 21 and the line control device 22 may each be a device having an independent housing, and the management device 21 and the line control device 22 may be connected to each other via a communication network.
[0114] [7. Effects] As described above, the OLT 11 includes the line control device 22. The line control device 22 controls communication with the ONU 12, which is the opposite device. The line control device 22 includes a non-volatile memory 222, a volatile memory 223, and an update control unit 236. The non-volatile memory 222 stores a basic part 310 that is a part of the control program 300 of the line control device 22. The volatile memory 223 stores a unique part 320 that is a part other than the basic part 310 of the control program 300. The update control unit 236 updates the control program 300. When updating the control program 300, the update control unit 236 writes the basic part 310 of the new control program 300 to the non-volatile memory 222, and writes the unique part 320 of the new control program 300 to the volatile memory 223 without writing it to the non-volatile memory 222. As a result, only the basic part 310 of the control program 300 is written to the non-volatile memory 222, which has a low writing speed, and the specific part 320 is written to the volatile memory 223, which has a high writing speed. Therefore, even if the size of the control program 300 increases, an increase in the update time for the control program 300 can be suppressed.
[0115] The line control device 22 may include a first acquisition unit 234. The first acquisition unit 234 acquires the basic part 310 of the new control program 300 when the basic part 310 needs to be updated. The update control unit 236 may write the acquired basic part 310 of the new control program 300 to the non-volatile memory 222. Thereby, for example, when only the basic part 310 needs to be updated, it is possible to update only the basic part 310 without updating the unique part 320. Therefore, the writing time of the unique part 320 is reduced, and an increase in the update time of the control program 300 can be further suppressed.
[0116] The line control device 22 may include a second acquisition unit 240. The second acquisition unit 240 acquires the unique part 320 of the new control program 300 when the unique part 320 needs to be updated. The update control unit 236 may write the acquired unique part 320 of the new control program 300 to the volatile memory 223 without writing it to the non-volatile memory 222. Thereby, for example, when only the unique part 320 needs to be updated, it is possible to update only the unique part 320 without updating the basic part 310. Therefore, the writing time of the basic part 310 is reduced, and an increase in the update time of the control program 300 can be further suppressed.
[0117] The line control device 22 may include a first consistency determination unit 233. In a start sequence for starting the control program 300, the first consistency determination unit 233 executes a first consistency determination process for determining whether or not the basic part 310 of the running control program 300 is consistent with the basic part 310 of the control program 300 held in the management device 21 that provides the control program 300 for update. When the result of the first consistency determination process is negative, the update control unit 236 may write the basic part 310 of the control program 300 provided by the management device 21 to the non-volatile memory 222. This allows the basic part 310 to be written to the non-volatile memory 222, for example, not only when the basic part 310 has not been updated, but also when a part or all of the basic part 310 of the non-volatile memory 222 has been damaged or lost.
[0118] The line control device 22 may include a second consistency determination unit 239. In a start sequence for starting the control program 300, the second consistency determination unit 239 executes a second consistency determination process for determining whether or not the unique part 320 of the running control program 300 is consistent with the unique part 320 of the control program 300 held in the management device 21 that provides the control program 300 for update. When the result of the second consistency determination process is negative, the update control unit 236 may write the unique part 320 of the control program 300 provided from the management device 21 to the volatile memory 223 without writing it to the non-volatile memory 222. This allows the unique part 320 to be written to the volatile memory 223, for example, not only when the unique part 320 has not been updated, but also when a part or all of the unique part 320 of the volatile memory 223 has been damaged or lost.
[0119] When a part of the unique part 320 of the control program 300 is provided from the management device 21, the update control unit 236 may write the part of the provided unique part 320 to the volatile memory 223 without writing it to the non-volatile memory 222. The line control device 22 may start the part of the unique part 320 written to the volatile memory 223. This makes it possible to write only the necessary part of the unique part 320 to the volatile memory 223, thereby suppressing an increase in the writing time.
[0120] The basic part 310 may include a boot loader 311, an OS 312, and a program used in the second consistency determination process. The unique part 320 may include a program used to control communication with the ONU 12. As a result, the basic function part of the control program 300 is included in the basic part 310, and the function part unique to the line control device 22 is included in the unique part 320. Therefore, a part or all of the function addition part that causes an increase in the size of the control program 300 can be included in the unique part 320, and an increase in the update time of the control program 300 can be suppressed. Furthermore, since the unique part 320 is updated more frequently than the basic part 310, an increase in the update time can be suppressed over the operation period of the line control device 22.
[0121] The OLT 11 may further include a management device 21. The management device 21 manages a plurality of line control devices 22. The management device 21 may transmit an update control program 300 to the line control device 22. This allows the use of the management device 21 to smoothly update the control programs 300 of the plurality of line control devices 22.
[0122] [8. Additional Notes] The embodiments disclosed herein are illustrative in all respects and are not restrictive. The scope of the present invention is defined by the claims rather than the above-described embodiments, and includes the meaning equivalent to the claims and all modifications within the scope thereof. [Explanation of symbols]
[0123] 10 Network Systems 11 Station equipment (communication network) 12 Home equipment 13 PON lines 14 Optical splitter 15 Trunk optical fiber 16 optical fiber branches 21 Management device 22 Line control device (communication control device) 23 L2 Switch 24 Flash memory (USB memory) 25 Flash memory (SD card) 26 Maintenance terminal 27 Server 50 Top Networks 51 Management Network 211 Processor 212 Non-volatile memory 213 Volatile Memory 214 Interface (IF) 215 PHY 221 Processor 222 Non-volatile memory 223 Volatile Memory 224 PON Processing Unit 225 PHY 226 Optical Transceiver (TRx) 231 First List Request Section 232 First Listing Department 233 First consistency determination section 234 First acquisition part 236 Update control section 237 Second List Request Section 238 Second Listing Division 239 Second consistency determination section 240 Second acquisition part 300 Control Program 310 Basic part 310A First Configuration List 311 Bootloader 312 Operating System (OS) 313 Communication Control Program 314 Module Control Program 315 Update Control Program 316 First Consistency Assessment Program 317 Second Consistency Assessment Program 318 First Configuration Information 320 Inherent Part 320A 2nd Configuration List 321 Alarm Management Program 322 Line Management Program 323 Line Control Program 324 Debugging Information 325 Second Configuration Information 330 Update Program Data
Claims
1. A communication system including a communication control device that controls communication with an opposing device, The communication control device includes: a non-volatile memory for storing a basic part which is a part of a control program of the communication control device; a volatile memory that stores a unique portion of the control program other than the basic portion; an update control unit that updates the control program; Equipped with when updating the unique part of the control program, the update control unit deletes the unique part of the control program before the update from the volatile memory, and writes the unique part of a new control program to the volatile memory without writing it to the non-volatile memory. Communication systems.
2. the communication control device includes a first acquisition unit that acquires the basic part of the new control program when the basic part needs to be updated; the update control unit writes the basic part of the acquired new control program into the non-volatile memory; The communication system according to claim 1 .
3. the communication control device includes a second acquisition unit that acquires the unique part of the new control program when the unique part needs to be updated; the update control unit writes the unique part of the acquired new control program to the volatile memory without writing it to the non-volatile memory; The communication system according to claim 1 or 2.
4. A communication system including a communication control device that controls communication with an opposing device, The communication control device includes: a non-volatile memory for storing a basic part which is a part of a control program of the communication control device; a volatile memory that stores a unique portion of the control program other than the basic portion; an update control unit that updates the control program; A first consistency determination unit; Equipped with when updating the control program, the update control unit writes a basic part of the new control program to the non-volatile memory, and writes a unique part of the new control program to the volatile memory without writing the unique part to the non-volatile memory; the first consistency determination unit executes a first consistency determination process in a startup sequence for starting the control program to determine whether or not the basic part of the started control program is consistent with a basic part of a control program stored in a providing device that provides an update control program; the update control unit writes a basic part of the control program provided by the providing device into the non-volatile memory when a result of the first consistency determination process is negative; Communication systems.
5. A communication system including a communication control device that controls communication with an opposing device, The communication control device includes: a non-volatile memory for storing a basic part which is a part of a control program of the communication control device; a volatile memory that stores a unique portion of the control program other than the basic portion; an update control unit that updates the control program; A second consistency determination unit; Equipped with when updating the control program, the update control unit writes a basic part of the new control program to the non-volatile memory, and writes a unique part of the new control program to the volatile memory without writing the unique part to the non-volatile memory; the second consistency determination unit executes a second consistency determination process in a startup sequence for starting the control program to determine whether or not the unique part of the started control program is consistent with a unique part of a control program stored in a providing device that provides an update control program; when a result of the second consistency determination process is negative, the update control unit writes the unique part of the control program provided by the providing device to the volatile memory without writing the unique part to the non-volatile memory; Communication systems.
6. when a part of a unique part of the control program is provided from the providing device, the update control unit writes the part of the unique part provided to the volatile memory without writing the part to the non-volatile memory; the communication control device activates a part of the unique part written in the volatile memory; 6. The communication system according to claim 5.
7. The basic unit includes a boot loader and an operating system, the unique unit includes a program used to control communication with the opposing device; A communication system according to any one of claims 1 to 6.
8. A management device that manages the plurality of communication control devices, the management device transmits an update control program to the communication control device; A communication system according to any one of claims 1 to 3.
9. A communication control device that controls communication with an opposing device, a non-volatile memory for storing a basic part which is a part of a control program of the communication control device; a volatile memory that stores a unique portion of the control program other than the basic portion; an update control unit that updates the control program; Equipped with when updating the unique part of the control program, the update control unit deletes the unique part of the control program before the update from the volatile memory, and writes the unique part of a new control program to the volatile memory without writing it to the non-volatile memory. Communications control device.
10. A control program update method in a communication control device that controls communication with an opposing device, comprising: When updating a specific part of a control program including a basic part stored in a non-volatile memory and a specific part stored in a volatile memory, a step of deleting the specific part of the control program before the update from the volatile memory; writing a unique part of a new control program to the volatile memory without writing it to the non-volatile memory; Including, A method for updating a control program.
Citation Information
Patent Citations
Information processor
JP2000284956A
Firmware update system, firmware update method, firmware update program and recording medium
JP2003167742A
Communication device and information processing method
JP2019192171A
