JP7788935B2 - Station side device and firmware update method - Google Patents

Description

This disclosure relates to a station device and a firmware update method.

In general, in an optical communication system, a central office device is connected to an optical splitter via an optical fiber, and multiple subscriber devices are connected to the optical splitter via multiple optical fibers.

The optical line terminal (OLT) is the parent station in an optical communications system and is installed, for example, in a telephone exchange. The optical line terminal (OLT) is also called an OLT (Optical Line Terminal). The subscriber station (ONT) is the child station in an optical subscriber line system and is installed, for example, in a subscriber's home. The subscriber station (ONT) is also called an ONU (Optical Network Unit).

The OLT is equipped with boards according to function, such as a control board or an interface board with the ONU. The firmware (hereafter referred to as F/W) for each board is upgraded to add or modify functions to the board, or to deal with discontinued parts.

In particular, when production of LSIs (Large Scale Integrations), FPGAs (Field Programmable Gate Arrays), or CPUs (Central Processing Units) that affect S/W (Software) functions is discontinued, two boards with different specifications will exist before and after the change in these components. In this case, simply creating firmware that is compatible with both boards would roughly double the firmware size, so they are often managed separately as firmware for the old version and firmware for the new version. In this case, the OLT will contain boards with different versions that perform the same functions, but by transferring the corresponding firmware to the OLT, individual version upgrades can be achieved.

Carrier communication networks are made up of a wide variety of communication devices, and maintenance and operation are carried out using an Element Management System (EMS) that manages the devices, or a Network Management System (NMS) that manages the entire network. However, introducing a separate EMS for each device increases the burden on maintenance personnel, and leads to increased implementation and maintenance costs.

Non-Patent Document 1 discloses technology that establishes a network management infrastructure that can be commonly applied to devices from different vendors with different operation and maintenance needs, and then builds and introduces each EMS based on this infrastructure to achieve consistent management of operations and maintenance.

Yoshifumi Kato et al., "Transport Network Management Infrastructure Technology Aiming to Standardize Management of Diverse Devices," NTT Technical Journal Publishing, August 2015, Internet <URL: https://www.ntt.co.jp/journal/1508/files/jn201508042.pdf>

Non-Patent Document 1 describes how maintenance and operation efficiency can be improved by building a system that absorbs differences between equipment from different vendors, but does not mention what to do if changes occur to the equipment that affect the operating company's control system.

For example, some control systems have a function that allows updates only with firmware that has a unique name associated with the board type, in order to prevent unauthorized firmware updates. In this case, for example, a lower-level interface board (hereinafter referred to as IF) can only receive firmware named IF.PKG.

If the OLT vendor is forced to switch to manufacturing boards that run on a new, incompatible version of firmware due to reasons such as the discontinuation of component production, then not only the OLT but also the EMS in operation will need to be modified to link and register the new version of firmware's unique name, for example, IF-B.PKG, in addition to the name of the old version of firmware, IF.PKG. This will incur development costs not only for the OLT vendor but also for the operating company.

Therefore, one or more aspects of the present disclosure aim to make it possible to easily introduce new firmware.

A station device according to a first aspect of the present disclosure comprises a first functional unit that performs an update with first firmware, a second functional unit that performs an update with second firmware that is newer than the first firmware, a receiving unit that receives a firmware combination module that includes a unique name of the first firmware but not a unique name of the second firmware in a common file header that is a header of a common file area that includes the first firmware and the second firmware, and receives an update instruction after receiving the firmware combination module, a memory unit that stores the firmware combination module, a file dividing unit that divides the first firmware and the second firmware from the firmware combination module when the update instruction is received, and a file transfer unit that transfers the first firmware to the first functional unit and the second firmware to the second functional unit, causing the first functional unit and the second functional unit to perform an update.

A station device according to a second aspect of the present disclosure includes a first functional unit that performs an update using first firmware, a second functional unit that performs an update using second firmware that is newer than the first firmware, a receiving unit that receives a firmware combination module that includes a unique name of the first firmware but not the unique name of the second firmware in a common file header, which is the header of a common file area that includes the second firmware but not the first firmware, and receives an update instruction after receiving the firmware combination module, a storage unit that stores the firmware combination module, a file dividing unit that divides the second firmware from the firmware combination module when the update instruction is received, and a file transfer unit that transfers the second firmware to the first functional unit and the second functional unit, wherein the first functional unit does not perform an update using the second firmware, and the second functional unit performs an update using the second firmware.

A firmware update method according to a first aspect of the present disclosure is characterized in that a receiving unit receives a firmware combination module that includes a unique name of the first firmware but does not include a unique name of the second firmware in a common file header, which is a header of a common file area that includes a first firmware and a second firmware that is newer than the first firmware; after the receiving unit receives the firmware combination module, the receiving unit receives an update instruction; when the update instruction is received, a file dividing unit divides the first firmware and the second firmware from the firmware combination module; a file transfer unit transfers the first firmware to a first functional unit that performs an update with the first firmware; the file transfer unit transfers the second firmware to a second functional unit that performs an update with the second firmware; and causes the first functional unit and the second functional unit to perform the update.

A firmware update method according to a second aspect of the present disclosure includes a receiving unit receiving a firmware combination module that includes a second firmware that is newer than a first firmware but that includes a unique name of the first firmware but does not include a unique name of the second firmware in a common file header, which is the header of a common file area that does not include the first firmware; after the receiving unit receives the firmware combination module, the receiving unit receives an update instruction; when the update instruction is received, a file dividing unit divides the second firmware from the firmware combination module; a file transfer unit transfers the second firmware to a first functional unit that performs an update with the first firmware and a second functional unit that performs an update with the second firmware; the first functional unit does not perform an update using the second firmware, and the second functional unit performs an update using the second firmware.

According to one or more aspects of the present disclosure, new firmware can be easily introduced.

1 is a block diagram schematically illustrating a configuration of an optical communication system according to first and second embodiments. FIG. 2 is a block diagram schematically showing the configuration of a control board and a lower-level I/F board in the first and second embodiments. FIG. 2 is a schematic diagram showing the format of a F/W binding module. 10 is a flowchart showing an operation of downloading firmware with a unique name that is not associated with a control device and is not registered to a second lower I/F board in the optical communication system according to the first embodiment. FIG. 10 is a schematic diagram showing a decision matrix table in the second embodiment. 10 is a flowchart showing an operation of downloading firmware simultaneously to all lower I/F boards in the second embodiment.

Embodiment 1.
FIG. 1 is a block diagram schematically illustrating a configuration of an optical communication system 100 according to the first embodiment.
The optical communication system 100 includes a control device 110 and an optical line terminal (OLT) 120 as a central office device.
The control device 110 and the OLT 120 are connected to a network such as a LAN (Local Area Network).

The control device 110 is a device used in a system that operates the maintenance and management of the OLT 120. Here, the firmware used by the OLT 120 is linked to and managed by the board, which is the functional unit to which that firmware can be applied. In other words, the firmware used by the OLT 120 can be maintained or managed by registering it in the control device 110.

The OLT 120 includes a communication board 121, a control board 130 that functions as a control unit, and multiple lower-level interface boards (lower-level I/F boards) 140 that function as multiple interface units. In this case, it is possible that the communication board 121 and the control board 130 have their functions on the same board. The OLT 120 may also include a higher-level interface board 122 or an optional function board 123 as necessary.
The control board 130 and the lower I/F board 140 are electrically connected by a transmission medium 124 and a backboard board (not shown).

The communication board 121 communicates with the control device 110. For example, the communication board 121 functions as a receiver that receives the firmware integration module or update instructions described below.

FIG. 2 is a block diagram showing a schematic configuration of the control board 130 and the lower I/F board 140 according to the first embodiment.
In Figure 2, in order to simply explain embodiment 1, of the multiple lower I/F boards 140 shown in Figure 1, the lower I/F board 140 that is updated with firmware that can be recognized by the control device 110 is referred to as the first lower I/F board 140#1, and the lower I/F board 140 that is updated with firmware that cannot be recognized by the control device 110 and is incompatible with the firmware for the first lower I/F board 140#1 is referred to as the second lower I/F board 140#2.

The specific name of the firmware for the first downstream I/F board 140#1 is IF.PKG, and the specific name of the firmware for the second downstream I/F board 140#2 is IF-B.PKG.
The IF.PKG has been registered in the control device 110 as being associated with the first lower-level I/F board 140#1, but the IF-B.PKG has not been registered in the control device 110 as being associated with the second lower-level I/F board 140#2.

The control board 130 includes an FTP (File Transfer Protocol) work area unit 131, an argument inspection unit 134, a file inspection function unit 135, a file transfer unit 136, and an OLT internal status monitoring unit 137.

The FTP work area unit 131 transmits and receives data files to and from the control device 110 via the communication board 121 .
Here, the FTP work area unit 131 includes a memory 132 and a file division unit 133 .

The memory 132 functions as a storage unit that stores data files sent and received between the control device 110 .
The file division unit 133 divides the file of the firmware link module, which is a data file stored in the memory 132 .

The argument inspecting unit 134 checks to see which lower I/F board 140 the firmware update instruction is directed to by the firmware connection module.
The file inspection function unit 135 inspects the individual files that are the divided firmware binding modules.
The file transfer unit 136 transfers individual files.
The OLT internal state monitoring unit 137 monitors the state of the OLT 120 .

The first lower I/F board 140#1 and the second lower I/F board 140#2 have the same configuration, and therefore will be described here as a lower I/F board 140.
The lower level I/F board 140 includes a file acquisition unit 141 , a file inspection unit 142 , a non-volatile storage area unit 143 , and a board status notification unit 144 .

The file acquisition unit 141 acquires individual files from the control board 130 .
The file inspection unit 142 checks the file header of the acquired individual file and inspects the individual file.
The non-volatile storage area unit 143 stores the acquired individual files.
The board state notification unit 144 notifies the control board 130 of the state.

3 is a schematic diagram showing an example of the format of a combined firmware module that includes firmware for an IF.PKG and firmware for an IF-B.PKG.
3 includes a common file header section 161 that stores a common file header for identifying the F/W link module 160, an individual file header section 162 that stores an individual file header that identifies the individual file for the first lower I/F board 140#1, a main body 163 that stores an IF.PKG that is the F/W for the first lower I/F board 140#1, an individual file header section 164 that stores an individual file header that identifies the individual file for the second lower I/F board 140#2, and a main body 165 that stores an IF-B.PKG that is the F/W for the second lower I/F board 140#2. Here, the individual file header section 162, the main body 163, the individual file header section 164, and the main body 165 are also referred to as a common file area.

Note that while the F/W link module 160 shown in Figure 3 is configured in a format for storing two individual files, the number of individual files stored does not need to be two; at least one file needs to be stored. An individual file is a file that includes an individual file header and the main body of the F/W.

Next, the operation will be described.
4 is a flowchart showing an operation of downloading IF-B.PKG, which is firmware with a unique name that is not registered and is linked to the control device 110, to the second lower I/F board 140#2 in the optical communication system 100 according to the first embodiment.

First, in accordance with instructions from the operator, the control device 110 transfers the F/W combination module 160, which includes IF.PKG, the F/W for the first downstream I/F board 140#1 provided by the OLT vendor, and IF-B.PKG, the F/W for the second downstream I/F board 140#2, to the FTP work area 131 of the control board 130 of the OLT 100 (S10). Here, the unique name of the F/W combination module 160 is assumed to be IF.PKG. In other words, the common file header section 161 includes the unique name of the IF.PKG, but not the unique name of the IF-B.PKG.

Next, in accordance with instructions from the operator, the control device 110 sends a F/W update command to the OLT 120, which is an update instruction instructing the second lower I/F board 140#2 to update its F/W (S11). The F/W update command here may include an instruction to update the IF.PKG.

Next, the argument inspecting unit 134 of the control board 130 determines whether the F/W update command sent in step S11 is an instruction to update the F/W of the IF.PKG (S12). For example, the argument inspecting unit 134 may make this determination based on whether the F/W update command includes an instruction to update the IF.PKG. If the F/W update command is not an instruction to update the F/W of the IF.PKG (No in S12), processing proceeds to step S13. If the F/W update command is an instruction to update the F/W of the IF.PKG (Yes in S12), processing proceeds to step S14.

In step S13, the control board 130 does not split the file for the firmware coupling module, and continues to store the data file received in step S10 as is in the FTP work area section 131.

In step S14, the file divider 133 of the control board 130 checks the file header of the F/W coupling module and separates it into IF.PKG, which is the F/W for the first lower I/F board 140#1, and IF-B.PKG, which is the F/W for the second lower I/F board 140#2. For example, as shown in FIG. 3, the common file header section 161 of the F/W coupling module 160 contains a linking marker as an identification marker. Therefore, the file divider 133 confirms that the common file header section 161 contains a linking marker, and also checks the individual markers, which are identification markers, contained in the individual file header sections 162 and 164, thereby separating the IF.PKG and IF-B.PKG.

If the firmware integration module 160 is not used and only a single firmware is transmitted, the file division unit 133 does not divide the file and proceeds to the next step.
Also, for example, if the file header contains neither a link marker nor an individual marker, the file division unit 133 deletes such a data file and ends the process.

Next, the file inspection function unit 135 of the control board 130 checks the individual file header section 162 of the divided IF.PKG to determine whether the IF.PKG is firmware to be transferred to the second lower I/F board 140#2 (S15). If the IF.PKG is not firmware to be transferred to the second lower I/F board 140#2 (No in S15), processing proceeds to step S16. If the IF.PKG is firmware to be transferred to the second lower I/F board 140#2 (Yes in S15), processing proceeds to step S18.

In step S16, the file inspection function unit 135 of the control board 130 checks the individual file header section 164 of the divided IF-B.PKG to determine whether the IF-B.PKG is firmware to be transferred to the second lower I/F board 140#2. If the IF-B.PKG is not firmware to be transferred to the second lower I/F board 140#2 (No in S16), processing proceeds to step S17. If the IF-B.PKG is firmware to be transferred to the second lower I/F board 140#2 (Yes in S16), processing proceeds to step S18.

In step S17, the file inspection function unit 135 of the control board 130 determines that there are no updated files, and the file transfer unit 136 notifies the board status notification unit 144 of the second subordinate I/F board 140#2 that there are no updated files. Processing then ends.

In step S18, the file transfer unit 136 of the control board 130 transfers the IF-B.PKG to the second lower-level I/F board 140#2 in accordance with the determination made by the file inspection function unit 135. The transferred IF-B.PKG is received by the file acquisition unit 141 of the second lower-level I/F board 140#2.

Next, the file inspection unit 142 of the second downstream I/F board 140#2 determines whether the received IF-B.PKG is normal (S19). For example, series information is stored in the individual file header, and if the received firmware is not part of a series that the file inspection unit 142 recognizes, it determines that the firmware is an invalid file. If the received IF-B.PKG is abnormal (No in S19), processing proceeds to step S20. If the received IF-B.PKG is normal (Yes in S19), processing proceeds to step S21.

In step S20, the file reconciliation unit 142 of the second downstream I/F board 140#2 notifies the board status notification unit 144 of the firmware update failure. In this case, the board status notification unit 144 of the second downstream I/F board 140#2 responds to the OLT internal status monitoring unit 137 of the control board 130 with a firmware update error. The OLT internal status monitoring unit 137, which receives this response, retains information indicating the firmware update error. By monitoring the information from the OLT internal status monitoring unit 137, the operator of the control device 110 can learn that the firmware update to the second downstream I/F board 140#2 has resulted in an error.

On the other hand, in step S21, the file inspection unit 142 of the second lower I/F board 140#2 stores the received IF-B.PKG in the non-volatile storage area unit 143, thereby updating the firmware of the second lower I/F board 140#2. Then, processing proceeds to step S22.

In step S22, the board status notification unit 144 of the second downstream I/F board 140#2 responds to the OLT internal status monitoring unit 137 of the control board 130 that the firmware update has been completed. Upon receiving this response, the OLT internal status monitoring unit 137 retains information indicating the completion of the firmware update. By monitoring the information from the OLT internal status monitoring unit 137, the operator of the control device 110 can know that the firmware update to the second downstream I/F board 140#2 has been completed.

As described above, according to the first embodiment, by combining the IF.PKG and IF-B.PKG and transferring them to the OLT 120 as an IF.PKG registered in the control device 110, the control board 130 of the OLT 120 can split them into two files and download the firmware of the IF-B.PKG, which is a unique name not registered in the control device 110, to the second lower I/F board 140#2. Therefore, even if additional board versions are added in the future due to device vendor circumstances, only the internal processing of the OLT 120 needs to be changed, which has the effect of reducing development costs for the control device 110.

Note that while embodiment 1 has been described as being applied to updating the firmware of the lower I/F board 140, embodiment 1 can also be applied to functional units that have firmware within the OLT 120 controlled by the EMS, such as the upper interface board 122, optional function board 123, or control board 130.

In other words, the first lower-level I/F board 140#1 or another board functions as a first functional unit that is updated with the first firmware, and the second lower-level I/F board 140#2 or another board functions as a second functional unit that is updated with the second firmware. As described above, the control board 130 can update the function of the first functional unit with the first firmware, and can update the function of the second functional unit with the second firmware. Here, the second firmware is newer than the first firmware. Therefore, the first firmware is registered in the control device 110, which is another device used for maintenance or management, and the second firmware is not registered in the control device 110, which is another device used for maintenance or management.

The communication board 121 receives a firmware combination module that includes the unique name of the first firmware but does not include the unique name of the second firmware in a common file header, which is the header of a common file area that includes the first firmware and the second firmware, and after receiving the firmware combination module, functions as a receiving unit that receives an update instruction.
The memory 132 also functions as a storage unit that stores the firmware binding module.
Then, when an update instruction is received, the file dividing unit 133 divides the first firmware and the second firmware from the firmware combination module, and the file transfer unit 136 transfers the first firmware to the first functional unit and the second firmware to the second functional unit, causing the first functional unit and the second functional unit to perform the update.

The file inspection function unit 135 also performs a recognition process to recognize the first firmware or the second firmware by checking the header of the data file divided from the firmware combination module.
The OLT internal state monitoring unit 137 functions as a monitoring unit that performs a monitoring process to monitor whether the OLT 120 is provided with the first functional unit or the second functional unit.
Then, the file transfer unit 136 transfers the first firmware or the second firmware according to the results of the recognition process and the monitoring process.

Embodiment 2.
In the first embodiment, by dividing the firmware combination module within the control board 130, firmware updates for boards with unregistered versions were realized without affecting the control device 110. However, if only the firmware for the second lower I/F board 140#2 is stored in the FTP work area 131 of the control board 130 and an instruction for all-slot simultaneous download is issued, the first lower I/F board 140#1 responds that there are no update files, and firmware updates for the other lower I/F boards 140 thereafter are halted. In the second embodiment, taking such a case into account, the all-slot simultaneous download can be continued even if the received data file is only an update file for a lower I/F board 140 of a different board version.

1, an optical communication system 200 according to the second embodiment includes a control device 110 and an optical line terminal (OLT) 220 as a station side device. The control device 110 and the OLT 220 are connected to a network.
The control device 110 in the optical communication system 200 according to the second embodiment is similar to the control device 110 in the optical communication system 100 according to the first embodiment.

The OLT 220 includes a communication board 121, a control board 230 that functions as a control unit, and a plurality of lower I/F boards 140 that function as a plurality of interface units. The OLT 220 may also include a higher-level interface board 122 or an optional function board 123, as necessary.
The control board 230 and the lower I/F board 140 are electrically connected by a transmission medium 124 and a backboard board (not shown).

The communication board 121 and downstream I/F board 140 of the OLT 220 in embodiment 2 are the same as the communication board 121 and downstream I/F board 140 of the OLT 120 in embodiment 1.

FIG. 2 shows a schematic configuration of a control board 230 and a lower I/F board 140 according to the second embodiment.
The control board 230 includes an FTP work area unit 131 , an argument inspecting unit 134 , a file inspecting function unit 235 , a file transferring unit 136 , and an OLT internal state monitoring unit 137 .
The FTP work area unit 131, argument inspection unit 134, file transfer unit 136, and OLT internal state monitoring unit 137 of the control board 230 in embodiment 2 are similar to the FTP work area unit 131, argument inspection unit 134, file transfer unit 136, and OLT internal state monitoring unit 137 of the control board 130 in embodiment 1.

The file inspection function unit 235 inspects the individual files that are divided F/W combined modules. In embodiment 2, the file inspection function unit 235 controls processing in the file transfer unit 136 according to the type of lower I/F board 140 implemented in the OLT 220 and the contents of the received F/W, in accordance with the determination matrix table shown in Figure 5.

In FIG. 5, the first lower I/F board 140#1 is denoted as "IF-A," the second lower I/F board 140#2 is denoted as "IF-B," and lower I/F boards 140 other than the first lower I/F board 140#1 and the second lower I/F board 140#2 are denoted as "IF-N." Furthermore, the firmware of lower I/F boards 140 other than the first lower I/F board 140#1 and the second lower I/F board 140#2 is denoted as IF-N.PKG.

Next, the operation will be described.
FIG. 6 is a flowchart showing the operation of downloading firmware simultaneously to all of the lower I/F boards 140 in the second embodiment.

First, in accordance with instructions from the operator, the control device 110 transfers the F/W coupling module 160, which contains only IF-B.PKG, the F/W for the second lower I/F board 140#2 provided by the OLT vendor, to the FTP work area 131 of the control board 130 of the OLT 100 (S30). Here, it is assumed that the name of the F/W coupling module 160 is IF.PKG.

Next, in accordance with instructions from the operator, the control device 110 sends an all-slot simultaneous F/W update command to the OLT 220, instructing all lower-level I/F boards 140 to update their firmware (S31). This command includes an instruction to update the IF.PKG that has been registered and associated with the control device 110.

Next, the argument inspector 134 of the control board 230 confirms that the all-slot simultaneous firmware update command sent in step S31 is an instruction to update the firmware of the IF.PKG, and the file divider 133 of the control board 230 checks the file header of the firmware combination module and divides IF-B.PKG, which is the firmware for the second lower I/F board 140#2 (S32).

After dividing the F/W combined module, the file inspection function unit 235 of the control board 230 checks the individual file headers and recognizes the divided IF-B.PKG. The file inspection function unit 235 also checks what type of lower I/F board 140 is installed in the OLT 220 by querying the OLT internal status monitoring unit 137. The file inspection function unit 235 then determines the lower I/F board 140 to which the F/W will be transferred, according to the matrix table shown in Figure 5, based on the contents of the F/W contained in the received F/W combined module and the type of installed lower I/F board 140 (S33). Here, IF-B. Since only IF-B.PKG is held and the first lower I/F board 140#1 and second lower I/F board 140#2 are implemented, the file inspection function unit 235 decides to transfer IF-B.PKG to the first lower I/F board 140#1 and second lower I/F board 140#2.

Next, the file transfer unit 136 of the control board 230 transfers the IF-B.PKG to each of all lower-level I/F boards 140 in accordance with the determination result of the file inspection function unit 135 (S34). The transferred IF-B.PKG is received by the file acquisition unit 141 of the lower-level I/F board 140.

Next, the file inspection unit 142 of the lower I/F board 140 determines whether the received IF-B.PKG is normal (S35). If the received IF-B.PKG is not normal (No in S35), processing proceeds to step S36. If the received IF-B.PKG is normal (Yes in S35), processing proceeds to step S37. Here, the file inspection unit 142 of the first lower I/F board 140#1 determines that the received IF-B.PKG is not normal, and the file inspection unit 142 of the second lower I/F board 140#2 determines that the received IF-B.PKG is normal.

In step S36, the file inspection unit 142 of the downstream I/F board 140 does not perform the firmware update, discards the sent firmware, and notifies the board status notification unit 144 that the firmware update is incomplete. In this case, the board status notification unit 144 of the downstream I/F board 140 responds to the OLT internal status monitoring unit 137 of the control board 230 that the firmware update is incomplete. Upon receiving this response, the OLT internal status monitoring unit 137 retains information indicating that the firmware update is incomplete. By monitoring the information from the OLT internal status monitoring unit 137, the operator of the control device 110 can know that the firmware update to the downstream I/F board 140 is incomplete.

On the other hand, in step S37, the file inspection unit 142 stores the received IF-B.PKG in the non-volatile storage area unit 143, thereby updating the firmware of the lower I/F board 140. Then, processing proceeds to step S38.

In step S38, the board status notification unit 144 of the downstream I/F board 140 responds to the OLT internal status monitoring unit 137 of the control board 230 that the firmware update has been completed. Upon receiving this response, the OLT internal status monitoring unit 137 retains information indicating that the firmware update has been completed. By monitoring the information from the OLT internal status monitoring unit 137, the operator of the control device 110 can learn that the firmware update to the downstream I/F board 140 has been completed.

Next, the OLT internal status monitoring unit 137 of the control board 230 periodically obtains the firmware update status of the downstream I/F boards 140, and when it confirms that the firmware update has been completed for the downstream I/F boards 140 to be updated, it instructs only the downstream I/F boards 140 for which the update has been completed to reset the board (S39). Upon receiving such an instruction, the file reconciliation unit 142 of the downstream I/F board 140 resets the downstream I/F board 140. At this time, the downstream I/F board 140 that notified in step S36 that the update was not complete is not subject to resetting because the update is not complete.

As described above, according to the second embodiment, even if the firmware coupling module only stores firmware for the second lower-level I/F board 140#2, updates can be performed on the second lower-level I/F board 140#2.

As explained above, when a simultaneous download is performed for all slots in the OLT, file transfer is also performed for lower-level I/F boards 140 that do not have files to be updated. Therefore, even if there is a lower-level I/F board 140 that is determined to not have files to be updated, the simultaneous download will not stop and the update can be performed. This allows the operator of the control device 110 to carry out firmware update work efficiently.

As described above, in embodiment 1, the first lower-level I/F board 140#1 or other board functions as a first functional unit that performs updates with first firmware, and the second lower-level I/F board 140#2 or other board functions as a second functional unit that performs updates with second firmware that is different from the first firmware.
The communication board 121 then receives a firmware combination module that includes the unique name of the first firmware but does not include the unique name of the second firmware in a common file header, which is the header of a common file area that includes the second firmware but does not include the first firmware, and after receiving the firmware combination module, functions as a receiving unit that receives an update instruction.

The memory 132 functions as a storage unit that stores the firmware combination module, and the file division unit 133 divides the second firmware from the firmware combination module when an update instruction is received. The file transfer unit 136 sends the divided second firmware to the first function unit and the second function unit.

Then, the first functional unit does not perform an update using the second firmware, and the second functional unit performs an update using the second firmware.
In addition, the OLT internal status monitoring unit 137 functions as a monitoring unit that resets the second functional unit that has been updated using the second firmware, and does not reset the first functional unit that has not been updated using the second firmware.

100, 200 Optical communication system, 110 Control device, 120 OLT, 121 Communication board, 122 Upper interface board, 123 Optional function board, 140#1 First lower I/F board, 140#2 Second lower I/F board, 130, 230 Control board, 131 FTP work area unit, 132 Memory, 133 File division unit, 134 Argument inspection unit, 135, 235 File inspection function unit, 136 File transfer unit, 137 OLT internal status monitoring unit, 140 Lower I/F board, 141 File acquisition unit, 142 File inspection unit, 143 Non-volatile storage area unit, 144 Board status notification unit.

Claims (6)

a first function unit that performs updating with first firmware;
a second function unit that updates the first firmware with second firmware that is newer than the first firmware;
a receiving unit that receives a firmware combination module that includes a unique name of the first firmware but does not include a unique name of the second firmware in a common file header that is a header of a common file area that includes the first firmware and the second firmware, and receives an update instruction after receiving the firmware combination module;
a storage unit that stores the firmware binding module;
a file dividing unit that divides the first firmware and the second firmware from the firmware combination module when the update instruction is received;
a file transfer unit that transfers the first firmware to the first functional unit and the second firmware to the second functional unit, thereby causing the first functional unit and the second functional unit to perform updates. a file inspection function unit that performs a recognition process to recognize the first firmware or the second firmware by checking the header of the data file divided from the firmware combination module;
a monitoring unit that performs a monitoring process to monitor whether the optical line terminal is provided with the first functional unit or the second functional unit,
2. The optical line terminal according to claim 1, wherein the file transfer unit transfers the first firmware or the second firmware in accordance with a result of the recognition process and a result of the monitoring process. a first function unit that performs updating with first firmware;
a second function unit that updates the first firmware with second firmware that is newer than the first firmware;
a receiving unit that receives a firmware combination module that includes a unique name of the first firmware but does not include a unique name of the second firmware in a common file header that is a header of a common file area that includes the second firmware but does not include the first firmware, and receives an update instruction after receiving the firmware combination module;
a storage unit that stores the firmware binding module;
a file division unit that divides the second firmware from the firmware combination module when the update instruction is received;
a file transfer unit that transfers the second firmware to the first function unit and the second function unit;
The optical line terminal according to claim 1, wherein the first function unit does not perform an update using the second firmware, and the second function unit performs an update using the second firmware. 4. The optical line terminal according to claim 3, further comprising a monitoring unit that causes the second functional unit that has performed an update using the second firmware to perform a reset, and that does not cause the first functional unit that has not performed an update using the second firmware to perform a reset. a receiving unit receives a firmware combination module including a unique name of the first firmware but not a unique name of the second firmware in a common file header, which is a header of a common file area including a first firmware and a second firmware that is newer than the first firmware;
the receiving unit receives an update instruction after receiving the firmware combination module;
a file dividing unit dividing the first firmware and the second firmware from the firmware combination module when the update instruction is received;
a file transfer unit transferring the first firmware to a first function unit that updates the first firmware;
a file transfer unit transferring the second firmware to a second function unit that performs an update with the second firmware, and causing the first function unit and the second function unit to perform the update. a receiving unit receives a firmware combination module including second firmware newer than the first firmware but including a unique name of the first firmware but not a unique name of the second firmware in a common file header that is a header of a common file area not including the first firmware;
the receiving unit receives an update instruction after receiving the firmware combination module;
a file dividing unit dividing the second firmware from the firmware combination module when the update instruction is received;
a file transfer unit transfers the second firmware to a first function unit that performs updating with the first firmware and a second function unit that performs updating with the second firmware;
A firmware update method, characterized in that the first functional unit does not perform an update using the second firmware, and the second functional unit performs an update using the second firmware.