JP2000347952A - File transfer method and basic system transmission device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable an operator to easily transfer a file without taking any consideration or the connection state or a circuit fault of an NE (basic system transmission device and also to collectively transfer in block the files to all NEs which configure a network. SOLUTION: When the software incorporated into plural NEs configuring a network are updated, an operator transfers the files of a workstation to these NEs. In such a file transfer method, every NE stores the received file (11, 13) and transfers it to a basic system transmission device other than its own one that is adjacent to the direction except the file receiving direction (14, 15). If the received file is equal to the one that is already stored, the received file is not stored. Then the NE stops the transfer of the file if any other NE adjacent to the direction except the file receiving direction does not exist. Thus, the files can be transferred to all NEs configuring the network.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a file transfer method and a backbone transmission apparatus, and more particularly, to a file transfer method and a backbone transmission apparatus for transferring a file when updating embedded software of the backbone transmission apparatus.

[0002]

2. Description of the Related Art Conventionally, a network as shown in FIG. 3 has been known. In the figure, among eight backbone transmission devices (NEs) 1 to 8, NE1 is connected to NE2 and NE8 and also to the workstation 9 via a network. The file to be transferred exists on the workstation 9. NE2 is connected to NE1 and NE3, and NE3 is NE
2, NE4 and NE5, and NE5 is connected to NE3 and NE5.
6, NE6 is connected to NE5 and NE7,
E8 is connected to NE7 and NE1.

In such a network, when updating the embedded software of all the NEs 1 to 8 (hereinafter, also referred to as “firmware download” in this specification), it exists on the workstation 9. The file needs to be transferred to all NE1 to NE8.

However, conventionally, file transfer between NEs has been performed using communication between adjacent NEs. Therefore, file transfer cannot be performed to NEs that are not directly connected, and file transfer can be performed only to adjacent NEs. In the case where firmware download is performed for all NE1 to NE8 in the network of FIG.
First, the file is transferred to NE1, and then NE1 → N
E2, NE1 → NE8, NE2 → NE3, NE8 → NE
7, NE3 → NE4, NE7 → NE6, NE3 → NE5
Thus, the transfer command is issued.

[0005]

Conventionally, however, the file transfer to a certain NE has to be completed before the transfer to the next NE is possible. Therefore, the operator confirms that the transfer to each NE has been completed. Then, it is necessary to issue a command for transferring the file to the next NE. At this time, for example, if a line failure has occurred between the NE 5 and the NE 6, the operator must recognize it and take care to transfer the file from the NE 3 to the NE 5.

As described above, in the conventional file transfer method, when downloading firmware in a network to which a plurality of NEs are connected, the operator needs to consider the connection state of each NE, the line failure, etc.
The file transfer to E must be performed by issuing a command each time, and since the operator has determined the file transfer path, the operator must know the network configuration and the status of the line failure. There is a problem that the burden is large.

[0007] The present invention has been made in view of the above points,
It is an object of the present invention to provide a file transfer method and a backbone transmission device that allow an operator to easily transfer a file without considering the connection state of the NE or a line failure.

It is another object of the present invention to provide a file transfer method and a backbone transmission apparatus capable of transferring a file to all NEs constituting a network at once.

[0009]

In order to achieve the above object, a file transfer method according to the present invention is applied to a case where a plurality of backbone transmission apparatuses constituting a network are updated when embedded software is updated. In a file transfer method in which an operator transfers a file on a workstation to a backbone transmission device, each of the plurality of backbone transmission devices stores a received file and then stores the received file in a direction other than the direction in which the received file is received. To the backbone transmission device. According to the present invention, it is possible to transfer a file received by each of a plurality of trunk transmission apparatuses constituting a network to an adjacent untransferred trunk transmission apparatus.

Here, according to the present invention, when a received file has already been stored in each of the plurality of backbone transmission devices, the received file is not stored or the direction in which the file was received is not stored. When there is no other backbone transmission device adjacent in the other direction, the file transfer is stopped.

Further, according to the present invention, in order to achieve the above object, each of the plurality of trunk transmission apparatuses stores a received file, and then sends a reception completion notification to the transmission trunk transmission apparatus. The transfer source trunk transmission device that has issued and received the reception completion notification notifies the operator of the trunk transmission device whose embedded software has been updated. According to the present invention, the operator can know which backbone transmission device has completed the update of the embedded software.

[0012] In order to achieve the above object, a trunk transmission apparatus of the present invention provides a trunk transmission apparatus in which a file on a workstation is transferred by an operator when updating embedded software. When there is another backbone transmission device adjacent in a direction other than the reception direction of the received file, the received file is transferred to another backbone transmission device, and another adjacent backbone transmission is performed. When there is no device, a transfer means for stopping the transfer of the received file is provided. According to the present invention, a received file can be transferred to an adjacent untransferred trunk transmission device.

[0013]

Next, embodiments of the present invention will be described with reference to the drawings. In the present invention, the hardware configuration of the NE itself is basically the same as the conventional one, but the file transfer processing method is different. This embodiment also describes file transfer in a network having the configuration shown in FIG. In the network of FIG. 3, among the eight units 2NE1 to NE8, NE1 to NE3 and NE5 to NE8 are connected on a ring, NE4 is connected only to NE3, and each NE is connected by an optical fiber cable. The overhead part of this communication line is used for the transfer.

In the case of performing firmware download to all NEs 1 to 8 on the network, in this embodiment, the operator transfers a file existing on the workstation 9 connected to the NE 1 over the network to the NE 1, After that, a command to be transferred to all NEs in the network is issued. The NE 1 transfers a file to all adjacent NEs based on the network configuration and the line failure status. The neighbor NE transfers the file to all NEs that are further adjacent. An algorithm executed by each NE at this time is shown by a flowchart of an embodiment of the file transfer method according to the present invention shown in FIG.

First, the NE receives the file (step 11). This file is, for example, as shown in FIG.
It is composed of a file transfer source address 21, a file version 22, and firmware data 23, and is transmitted and received in a data packet format including the file. Next, the NE determines whether the received file is stored in the internal memory (step 12), and if not, stores the file in the memory for itself (step 13). In this case, when the last data packet including the firmware file has been stored, a reception completion notification is issued to the file transfer source of the file transfer source address 21 added to the data.

Next, the NE determines whether the NE is connected in a direction other than the direction in which the NE was received (step 14). N
Since E knows in advance whether or not it is connected to another NE, when an adjacent NE is connected other than in the direction in which it was received, the received file is transmitted to the adjacent NE (step 15). Step 12
If the received file is already stored, the process ends without doing anything. If the NEs other than the direction received in step 14 are not connected, only the file for the self is stored.

Therefore, when applied to the network shown in FIG. 3, the operator first issues a command to transfer a file to the NE 1 and then to all NEs in the network. Then, NE1 is the firmware download start NE, and transfers the received file to all NEs adjacent to itself, ie, NE2 and NE8. At this time, the own address is added to the file transfer source address 21 as a transmission source for each data packet obtained by dividing the file.

When the NE 2 receives the file from the NE 1 (step 11 in FIG. 1), it checks whether or not the NE 2 already has the file based on the source and version of the file (step 12 in FIG. 1). As a result, it is found that the user does not have the file, and the file is stored (step 13 in FIG. 1). Then, NE2 is connected to NE1 and NE3, and since it is known that the file has been transferred from NE1, NE2 is not transmitted to NE1.
The received file is transmitted only to E3 (steps 14 and 15 in FIG. 1). Similarly, the NE 8 stores the received file for itself and then transfers the file to the adjacent NE 7.

Similarly, NE3 stores the received file for itself, and then transfers the received file to NE4 and NE5. The NE 4 is connected only to the NE 3, and after receiving and storing the file transmitted from the NE 3, the file transfer is not performed because there is no connected NE except in the direction in which the file was received (step in FIG. 1). 14). Similarly, the NE 7 stores the file received from the NE 8 and then transfers it to the NE 6, and the NE 5 stores the file received from the NE 3 and transfers it to the NE 6.

Here, NE6 may receive the same file from NE5 and NE7, but after storing the received file for the first time, transmits the file to the opposite side, but the second time from the opposite side. Since the same received file is already stored, neither storage nor transfer of the file is performed.

In this way, the operator can transfer a file to all NE1 to NE8 by issuing a command only once. The firmware download start NE1, which is the file transfer source, notifies the operator of the NE whose download has been completed to the operator when receiving the reception completion notification from all the other NE2 to NE8.

For example, if a line failure has occurred between the NE 7 and the NE 6 when the NE 7 receives a file from the NE 8, it is regarded that there is no adjacent NE other than the NE 8, and no file transfer is performed. Even in this case, the NE 6 can receive the file transfer from the NE 5 and store the file.

As described above, in this embodiment, the file can be transferred to all the NEs constituting the network all at once by the operator issuing the command to transfer to all the NEs once. Further, the operator does not need to know the configuration of the network or the state of the line failure, and does not need to determine the file transfer route. In addition, even if a line failure has occurred somewhere in the network, the file can be transferred if it can be reached by another route.

The present invention is not limited to the above embodiment. For example, the network configuration is not limited to the ring configuration as shown in FIG. Applicable.

[0025]

As described above, according to the present invention,
Since the received file is transferred to the adjacent untransferred trunk transmission device, the operator does not need to issue a file transfer command every time as in the conventional case, and the file for all trunk transmission devices constituting the network is not required. The operator can issue a command to perform the transfer only once, and the file can be transferred to all the backbone transmission devices constituting the network.

Further, according to the present invention, the operator can transfer a file to all the trunk transmission devices constituting the network without deciding a file transfer route or knowing the configuration of the network or the status of the line failure. This can greatly reduce the burden on the operator as compared with the related art.

Further, according to the present invention, even if a line failure has occurred somewhere on the network, the file can be transferred if the backbone transmission device is connected to the line by another route, so that the operator can perform the file transfer. File transfer is possible without considering the situation of line failure.

[Brief description of the drawings]

FIG. 1 is a flowchart of an embodiment of the present invention.

FIG. 2 is a diagram showing an example of the structure of a file to be transferred.

FIG. 3 is a diagram illustrating an example of a network to which the present invention is applied.

[Explanation of symbols]

 1 to 8 backbone transmission device (NE) 9 workstation having a file to be transferred

 ────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Daisuke Suzuki 1-403 Kosugi-cho, Nakahara-ku, Kawasaki-shi, Kanagawa F-term in NEC Telecom System Corporation (reference) 5B045 BB13 BB28 BB47 5B082 HA05 5B089 GA36 GB01 HA01 JA32 JB07 KA01 KA04 KB09 KC27

Claims (6)

[Claims] 1. A file transfer method in which an operator transfers a file on a workstation to a plurality of backbone transmission devices when updating embedded software of the plurality of backbone transmission devices constituting a network. 2. The file transfer method according to claim 1, wherein each of the plurality of trunk transmission apparatuses stores the received file and transfers the file to another trunk transmission apparatus adjacent in a direction other than the direction in which the file is received. 2. The file transfer according to claim 1, wherein each of the plurality of backbone transmission apparatuses does not store the received file when the received file has already been stored. Method. 3. Each of the plurality of trunk transmission apparatuses stops transferring the file when there is no other trunk transmission apparatus adjacent in a direction other than the direction in which the file is received. 3. The file transfer method according to claim 1, wherein: 4. After each of the plurality of trunk transmission apparatuses stores the received file, the plurality of trunk transmission apparatuses issues a reception completion notification to the transmission source trunk transmission apparatus, and receives the reception completion notification. 3. The file transfer method according to claim 1, wherein the transfer source backbone transmission device notifies the operator of the backbone transfer device for which the update of the embedded software has been completed. 5. A backbone transmission apparatus in which a file on a workstation is transferred by an operator when updating embedded software, a storage unit for storing the received file, and a storage unit other than the receiving direction of the received file. When there is another backbone transmission device adjacent in the direction, the received file is transferred to the other backbone transmission device, and when there is no other backbone transmission device adjacent, the transfer of the received file is performed. A backbone transmission apparatus comprising: a transfer unit that stops. 6. The receiving means according to claim 5, further comprising a receiving completion notifying means for issuing a receiving completion notice to a transfer source backbone transmission device after the storing means finishes storing the received file. Backbone transmission equipment.