WO2013075488A1

WO2013075488A1 - Network element upgrading method and device

Info

Publication number: WO2013075488A1
Application number: PCT/CN2012/077697
Authority: WO
Inventors: 梁小英
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-11-25
Filing date: 2012-06-28
Publication date: 2013-05-30
Also published as: CN103139245A

Abstract

Disclosed are a network element upgrading method and device. The method includes: downloading an upgraded version of at least one network element which is designated to be upgraded; and after the download of the upgraded version of the at least one network element, activating the downloaded upgraded version of each network element to upgrade each network element. The present invention can be applied to solve the following problem in the related art: that the reboot operation during the upgrade of a near-end network element will cause the service of a far-end network element which takes the near-end network element as a starting point to be interrupted, and the network bandwidth should be made the best.

Description

TECHNICAL FIELD The present invention relates to the field of communications, and in particular to a network element upgrade method and apparatus. BACKGROUND In order to meet the needs of operators and the rapid changes, equipment manufacturers have to update the network software version frequently to meet new demands. On the upgrade of the NE software version, the existing upgrade solution is to automatically restart the activation version after the download version is released. After the NE downloads the software version to be upgraded, the system restarts and activates immediately. However, this solution has a large defect in the microwave transmission network: Since the microwave device is connected through the wireless link, the restart of the near-end network element (E) will cause all the remote network element services starting from E to be interrupted. During the upgrade, if the near-end NE is restarted after the download is complete, the download and service of all remote NEs will be interrupted, which is unacceptable to the operator. The restarting operation in the near-end network element upgrade in the related art may cause the interruption of the remote network element service starting from the near-end network element. Currently, no effective solution has been proposed. SUMMARY OF THE INVENTION The present invention provides a method and an apparatus for upgrading a network element, so as to solve at least the problem that the remote network element service starting from the near-end network element is interrupted due to the restart operation in the near-end network element upgrade in the related art. According to an aspect of the present invention, a method for upgrading a network element is provided, including: downloading an upgrade version of at least one network element that needs to be upgraded; and after the upgrade version of the at least one network element is downloaded, Upgrade the version of each NE to upgrade the NEs. Preferably, the downloading of the upgraded version of the at least one network element that needs to be upgraded includes: downloading the upgraded version of the at least one network element in the upgrade order. Preferably, the upgrading sequence is determined as follows: The upgrade sequence is determined according to the network element list and the network topology of the at least one network element. Preferably, the upgrading sequence is determined according to the following steps: determining the upgrade sequence according to the network element list of the at least one network element, the network topology, and the bandwidth information of the link. Preferably, determining the upgrade sequence further includes: sorting, by the at least one network element, an upgrade order of the at least one network element according to a starting point of a distance between the network element and the network management server from a remote end to a near end. Preferably, the upgrading sequence is determined as follows: The upgrade sequence is determined by a user by using a file mode configuration. Preferably, before the downloading of the upgraded version of the at least one network element that needs to be upgraded, the method includes: setting the size of the upgrade task management list according to the resource configuration information of the system for upgrading the network element, and starting the concurrent download quantity. Preferably, in the downloading process, the network management server performs real-time scheduling on the upgrade tasks of the network elements, and records the upgrade progress results of the network elements. According to another aspect of the present invention, a network element upgrading apparatus is provided, including: a downloading module, configured to perform downloading of an upgraded version of a specified at least one network element that needs to be upgraded; and an activation module configured to be at least one of the at least one After the upgraded version of the NE is downloaded, the upgraded version downloaded by each NE is activated and the NEs are upgraded. Preferably, the downloading module is further configured to sequentially download the upgraded version of the at least one network element in an upgrade order. Preferably, the downloading module is further configured to calculate the upgrade sequence according to the network element list and the network topology of the at least one network element; or, according to the network element list, the network topology, and the chain of the at least one network element The bandwidth information of the road calculates the upgrade sequence; or, the upgrade sequence is formulated by the user through file mode configuration. In the embodiment of the present invention, the upgraded version of the at least one network element that needs to be upgraded is downloaded, and after the upgraded version of the at least one network element is downloaded, the upgraded version downloaded by each network element is activated. Meta upgrade. That is, in the embodiment of the present invention, all the network elements are activated after the upgraded version is downloaded, instead of being activated after the single network element downloads the upgraded version, which avoids the downloading and service interruption of the remote network element, and improves the download speed. And the quality of the business. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a first process flowchart of a network element upgrading method according to an embodiment of the present invention; 2 is a network management network element and network element network topology diagram according to an embodiment of the present invention; FIG. 3 is a second processing flowchart of a network element upgrade method according to an embodiment of the present invention; FIG. 4 is a system software according to an embodiment of the present invention; 5 is a schematic diagram of a task management list according to an embodiment of the present invention; FIG. 6 is a flowchart of processing a network element upgrade according to Embodiment 2 of the present invention; FIG. 7 is a third embodiment according to an embodiment of the present invention. FIG. 8 is a flowchart of processing a network element upgrade according to Embodiment 4 of the present invention; and FIG. 9 is a schematic structural diagram of a network element upgrading apparatus according to an embodiment of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. As mentioned in the related art, the restart of the near-end NE will cause all the remote NE services that are started from the E to be interrupted. In the batch upgrade, if the near-end NE is downloaded, the active version is restarted. The download and business will be interrupted, which is unacceptable to operators. To solve the above technical problem, the embodiment of the present invention provides a network element upgrade method, and the processing flow thereof is as shown in the figure.

As shown in FIG. 1 , the method includes the following steps: Step S102: Step S102: Perform downloading of the upgraded version of the at least one network element that needs to be upgraded. Step S104: After the downloaded version of the at least one network element to be specified is downloaded, activate each Upgrade the NEs to upgrade the NEs. In the embodiment of the present invention, the upgraded version of the at least one network element that needs to be upgraded is downloaded, and after the upgraded version of the at least one network element is downloaded, the upgraded version downloaded by each network element is activated. Meta upgrade. That is, in the embodiment of the present invention, all the network elements are activated after the upgraded version is downloaded, instead of being activated after the single network element downloads the upgraded version, which avoids the downloading and service interruption of the remote network element, and improves the download speed. And the quality of the business. In addition, in the related art, the data volume of the version file that the network element needs to download is very large, a small number of hundreds of KB, a large tens of megabytes, or even hundreds of megabytes, so that under the condition of limited bandwidth and concurrent resources, if the network management When the number of managed NEs is large, it takes a long time to complete the upgrade of the NE software version. At present, the downloading sequence of the downloading technology is random. As shown in Figure 2, if the bandwidth of each link is 5M, then the network elements E1 and E2 are upgraded at the same time, and the bandwidth obtained by each network element is 5M. However, if E1, E11, E12, and E13 are upgraded at the same time, they will share 5M bandwidth; if E1, E11, E12, E11K E112, E121, etc. are concurrently upgraded, the problem is more serious, and bandwidth is obviously a bottleneck. In addition, if the network management server memory configuration can support up to 300 network element upgrade tasks at the same time, it can support up to 50 connection numbers for parallel download, and users want to upgrade 1000-hop network elements. At this time, it is necessary to make full use of memory and perform tasks. Reasonable scheduling can effectively improve the efficiency of the upgrade. In order to solve the bottleneck problem of the bandwidth in the downloading process, in the embodiment of the present invention, at least one network element may be sorted, and the upgrade version is downloaded in the order of the upgrade. The specific process is as shown in FIG. 3, including steps S302 to S306: Step S302: Sorting the specified at least one network element that needs to be upgraded; Step S304: Performing, in sequence, downloading the upgraded version of the specified at least one network element that needs to be upgraded; Step S306, at least one network element to be specified After the upgrade version is downloaded, the upgraded versions downloaded by each NE are activated in sequence to upgrade the NEs. In the embodiment of the present invention, when the network elements that need to be upgraded are sorted, multiple network elements can be prevented from being downloaded at the same time, and the limited bandwidth and concurrent resources can be effectively utilized to avoid network congestion or even collapse caused by simultaneous downloading of multiple network elements. The problem. The upgrade sequence may be determined in multiple ways. For example, the upgrade sequence may be determined according to the network element list and the network topology of at least one network element, and may also be based on the network element list, network topology, and link of at least one network element. The bandwidth information determines the upgrade order. In the specific implementation process, other determination manners may also be adopted, for example, sorting according to the size of the download file package required for the upgrade, and the user may formulate the upgrade sequence by using the file mode configuration, δΡ, and designating the network to be upgraded according to the instruction information of the user. Meta upgrade order, and so on. In a preferred embodiment, determining the upgrade sequence may further include: sorting, by the at least one network element, an upgrade order of the at least one network element according to a starting point of the distance between the network element and the network management server from a remote end to a near end. This step takes into account the distance between the network element and the server, and is also a preferred embodiment. In the implementation, before the download of the upgraded version of the specified NE is upgraded, set the size of the upgrade task management list based on the resource configuration information of the system upgraded by the NE, and start the number of concurrent downloads, that is, confirm that the network management server can accommodate How many network elements are downloaded at the same time and managed as such. In the network management system, the resource configuration information of the network management server is set for management, and when the network element upgrade is implemented in other systems, the corresponding resources of the system are configured. During the download process, the network management server monitors the upgrade tasks of each network element, implements real-time scheduling, and records the upgrade progress results of each network element, so that users can query the operation progress and result information at any time, and reduce manual intervention. It can be seen from the above analysis that, in the network element upgrade method provided by the embodiment of the present invention, the user sets the size of the upgrade task management list and the number of concurrent downloads according to the configuration of the network management server software and hardware resources, and the network management system further selects the network element list according to the user. The network topology (you can also use the bandwidth information of the link) to calculate the optimal upgrade sequence, and then start the upgrade task in sequence, and the task management scheduling module performs real-time scheduling on the upgrade task, thereby maximizing the use of server hardware and software. Resources and bandwidth of the entire network, minimize service interruption time, ensure the security of the upgrade, efficiently complete the upgrade of the network software version, and automatically monitor and record the progress report of the upgrade progress, so that users can query the operation progress and result information at any time. , reduce manual intervention. In order to clarify the network element upgrade method provided by the embodiment of the present invention, it will be described in detail with reference to specific embodiments. The first embodiment of the present invention separates the version downloading and activating process, and after the user ensures that the version file is normally downloaded, the activation task is started, and the upgrade order is optimized according to the topology structure in the traditional network element version upgrade, and the remote priority order is adopted. Upgrade, the network management server can schedule the version upgrade process of the NE in real time. In the embodiment of the present invention, the network element upgrade method is implemented by the following modules. For the continuous relationship of each module, refer to FIG. 4.

1: Ml version management human-computer interaction module: This module is deployed on the network management client. This module provides a human-machine interface. The user imports the version file to the M5 module, selects the NE that needs to be upgraded, and sends it to the M2 module, and sets the control parameters of the M3 module. Ml receives the upgrade progress and result information from the M4 module and presents it to the user.

2: M2 upgrade sequence optimization module: This module is deployed on the network management server. This module is based on the network topology information stored in the network management. The network topology is a graph structure starting from the network management server (for example, the network topology diagram shown in Figure 2). The breadth-first prioritization scheme is adopted before the upgrade. Bandwidth information weighting), The user-selected NEs that are received from the M1 module are sorted in order from the far-end to the near-end from the starting point, and the optimal upgrade sequence is calculated. The upgraded sequence of the NE information to be upgraded is forwarded to the M3 module. .

3: M3 version upgrade task management scheduling module: This module is deployed in the network management server, maintain a task management list, refer to Figure 5, the total task list capacity TASKtotal = TASKwait + TASKmax. The module receives information from the M2 module, creates a corresponding task object, and adds the task object to the task list. The task scheduling thread executes the state according to the current task thread (the task status information is as shown in Table 1), and the thread executes the maximum concurrent number. Monitor and schedule management of tasks. The started task thread sends a download/activation command to the M6 module.

4: M4 version upgrade progress result monitoring module: This module is deployed on the network management server. The module maintains a record for each upgrade task, including downloads and activations. The record includes the network element identification (name, IP, etc.), download/activation version number, progress/result, start time, end time, and the like. Monitor the progress and results before the end of the task, and send the progress result information to the Ml module for processing. At the end of the task, the information is persisted to a file or database for user queries.

5: M5 file library management module: This module is deployed on the network management server, which may be the logical module formed by the FTP server. This module is responsible for maintaining the version file: accepting the version file import request from the M1 module, storing the version file into the library management; accepting the version file deletion request from the Ml module, deleting the version file management; accepting the version file download request from the M6 module Download the version file from this library by the M6 module.

6: M6 command / file receiving module: This module is deployed on the network element. This module accepts instructions from the M3 module, initiates a data download request to the M5 module, receives data to the network element, or executes the load activation version according to the activation command indication. The task status in the M3 module task management list is mainly Ready and Executing status. If necessary, you can add a Scheduled status if you need to set a timed task. When the task ends, including success, failure, and cancellation, the scheduling thread removes the Task from the task list and frees memory. The task status description is shown in Table 1: Task Status Information Table

Executing execution monitoring task progress and results

Succeed/Failed/ Cancele End Move out of the task list, persistent record d

The following technical problems can be solved by using the embodiments of the present invention: the bandwidth of the high-volume network element in the prior art is a bottleneck when the version is downloaded, and the shortcoming of the remote network element is caused by the restart of the local network element, which solves the shortcomings in the prior art. Upgrade risk and upgrade time issues. In the embodiment of the present invention, the downloading and activation of the version are separated, and the version is downloaded first and then the network element is restarted to minimize the risk of upgrading. The embodiment of the present invention calculates an optimal upgrade sequence according to a network element list and a network topology structure (which may also utilize the bandwidth information of the link), or the user configures an optimal upgrade sequence, and then schedules the upgrade according to the sequence. task. According to the configuration of the network management server software and hardware resources, the user sets the size of the upgrade task management list and starts the number of concurrent downloads. The task management scheduling module performs real-time scheduling on the upgrade tasks in the most order, thereby maximizing the utilization of server hardware and software resources and the whole. The bandwidth of the network minimizes service interruption time, efficiently completes the upgrade of the NE software version, and automatically monitors and records the progress report of the upgrade progress, so that users can query the operation progress and result information at any time, and reduce manual intervention. The second embodiment is a specific embodiment of the network element upgrade. In this example, the upgrade sequence of the network element upgrade is determined by the network management server. The specific process is as shown in FIG. 6, which includes the following steps: Step S602: The user configures the software and hardware according to the network management server. For the resource status, configure the parameters of the upgrade task management list and the maximum number of concurrent connections in the M1 module, and forward the parameters of the configuration to the M3 module. In the M1 module, import the version file and select the NE to be upgraded. The NE ID to be upgraded is forwarded to the M2 module to start the upgrade. Step S604: The M2 module uses a breadth-first ordering scheme (which can be weighted by the bandwidth information of the link), and the network elements selected by the user received from the M1 module are sorted in the order from the remote end to the near end in the order of the network management server, and the calculation is performed. The optimal upgrade sequence is to forward the optimized upgrade sequence of the NE information to be upgraded to the M3 module. It is assumed that the network topology upgrade order time interval T(n) composed of n network elements is calculated, and the time depends on the algorithm complexity and the processing capacity of the network management server. Generally, Τ(η) is much smaller than that required to activate n network elements. time. Step S606: The M3 module performs real-time monitoring and scheduling management on the upgrade task thread according to parameters such as the upgrade task management list capacity TASKtota maximum concurrent number TASKmax set by the M1 module. The M3 module receives the request for upgrade information from the M2 module, detects that the current task list is empty, and immediately creates a TASKtotal task in the upgrade order to join the task list, and starts the TASKmax bar Ready state task with the highest priority at the end of the list. The scheduling thread monitors the task status in the task list in real time, and immediately removes the free memory space after the task is executed, and starts the Ready state task at the end of the list. For the download operation, assuming TASKmax, the network element download version file takes an average time Tdownload. According to this patent scheduling method, except for the last less than TASKmax tasks to be executed, the download tasks simultaneously executed in parallel at each time are TASKmax. The download of n network elements is equivalent to being divided into n/Tmax batches. All network elements complete the download time T=Tdownload* n/Tmax, plus the optimized sorting time T(n), and the total time consumption is Τ(η)+Τ . When it is detected that the current task list is TASKtotal tasks, M3 no longer creates the task object, but waits for a period of time after Twait to continue to detect the task management list to determine whether it is possible to continue to create a new task object. The calculation method of Twait is as follows: Assume that the download command response timeout time is Tack, then Twait=Tack* (TASKtotal/TASKmax-1). The started thread sends the command to the M6 module. For the activation operation, suppose TASKmax, the response timeout time of the NE to the activation command is Tack seconds, and the NE needs to restart the loading version file to make the version take effect. The average time required is Tacitve, based on this patent scheduling method, except for the last less than TASKmax tasks to be executed. In addition, the activation tasks that are simultaneously executed in parallel at each moment are TASKmax. The activation operation of n network elements can be divided into n/Tmax batches, the activation time T=Tack* n/Tmax +Tacitve, plus the optimized upgrade sequence processing time, the total time consumption T(n)+T minutes. When it is detected that the current task list is TASKtotal tasks, M3 no longer creates the task object, but waits for a period of time after Twait to continue to detect the task management list to determine whether it is possible to continue to create a new task object. The calculation method of Twait is as follows: Then T _W ait= Ta _C k * (Ttotal/Tmax-1 ). The started thread sends an activation command to the M6 module. Step S608, the M6 module receives the command from the M3 module, and if the download command is received, requests the M5 module to download the version file, and reports the download progress and the result to the M4 module; if the activation command is received, the verification is performed. The parameter and the backup version are reported to the M4 module. If the verification is correct, the NE is loaded with the version file, and the restart takes effect. Steps S610 and M4 send the NE version download/activation progress and result information to the M1 module, and the M1 module displays related information to the user, and the user can also monitor the upgrade progress and results through the M1 module, and perform corresponding management according to the progress and result information. Operation, such as canceling the download, activation after downloading, etc. The third embodiment of the second embodiment optimizes the upgrade sequence in S604. The network management server automatically calculates the optimal upgrade sequence according to the network topology information. The difference between this embodiment and the second embodiment is that before the network element version is upgraded, The optimal upgrade sequence can be configured by the user through the file mode, and the upgrade information is imported through the file, and the information includes the upgrade sequence, and the upgrade is performed in the order specified in the file. The specific process of this embodiment is shown in FIG. 7, and includes: Step S702: The user allocates the parameters of the upgrade task management list capacity and the maximum number of concurrent connections of the network management server to the M3 module according to the configuration of the network management server software and hardware, and the parameters of the configuration are forwarded to the M3 module in the M1 module. The NE that needs to be upgraded forwards the version information and the NE ID to be upgraded to the M2 module to start the upgrade. Step S704: Before upgrading the NE version, the user can configure an optimal upgrade sequence through the file mode, and import the upgrade information through the file, where the information includes the upgrade sequence, and the upgrade is performed in the order specified in the file. The optimized upgrade sequence of the NE information to be upgraded is forwarded to the M3 module. It is assumed that the network topology upgrade order time interval T(n) composed of n network elements is calculated, and the time depends on the algorithm complexity and the processing capacity of the network management server. Generally, Τ(η) is much smaller than that required to activate n network elements. time. Step S706: The M3 module performs real-time monitoring and scheduling management on the upgrade task thread according to parameters such as the upgrade task management list capacity TASKtota maximum concurrent number TASKmax set by the M1 module. The M3 module receives the request for upgrade information from the M2 module, detects that the current task list is empty, and immediately creates a TASKtotal task in the upgrade order to join the task list, and starts the TASKmax bar Ready state task with the highest priority at the end of the list. The scheduling thread monitors the task status in the task list in real time, and immediately removes the free memory space after the task is executed, and starts the Ready state task at the end of the list. For the download operation, assuming TASKmax, the network element download version file takes an average time Tdownload. According to this patent scheduling method, except for the last less than TASKmax tasks to be executed, the download tasks simultaneously executed in parallel at each time are TASKmax. The download of n network elements is equivalent to being divided into n/Tmax batches. All network elements complete the download time T=Tdownload* n/Tmax, plus the optimized sorting time T(n), and the total time consumption is Τ(η)+Τ . When it is detected that the current task list is TASKtotal tasks, M3 no longer creates the task object, but waits for a period of time after Twait to continue to detect the task management list to determine whether it is possible to continue to create a new task object. The calculation method of Twait is as follows: Assume that the download command response timeout time is Tack, then Twait=Tack* (TASKtotal/TASKmax-1). The started thread sends the command to the M6 module. For the activation operation, suppose TASKmax, the response timeout time of the NE to the activation command is Tack seconds, and the NE needs to restart the loading version file to make the version take effect. The average time required is Tacitve, based on this patent scheduling method, except for the last less than TASKmax tasks to be executed. In addition, the activation tasks that are simultaneously executed in parallel at each moment are TASKmax. The activation operation of n network elements can be divided into n/Tmax batches, the activation time T=Tack* n/Tmax +Tacitve, plus the optimized upgrade sequence processing time, the total time consumption T(n)+T minutes. When it is detected that the current task list is TASKtotal tasks, M3 no longer creates the task object, but waits for a period of time after Twait to continue to detect the task management list to determine whether it is possible to continue to create a new task object. The calculation method of Twait is as follows: Then T _W ait= Ta _C k * (Ttotal/Tmax-1 ). The started thread sends an activation command to the M6 module. Step S708: The M6 module receives the command from the M3 module, and if the download command is received, requests the M5 module to download the version file, and reports the download progress and the result to the M4 module; if the activation command is received, Check the parameters and the backup version, and report the verification result to the M4 module. If the verification is correct, the NE is loaded with the version file, and the restart takes effect. Steps S710 and M4 send the NE version download/activation progress and result information to the M1 module, and the M1 module displays related information to the user. The user can also monitor the upgrade progress and results through the M1 module, and perform corresponding management according to the progress and result information. Operation, such as canceling the download, activation after downloading, etc. The fourth embodiment differs from the second embodiment and the third embodiment in that, before upgrading the network element version, the user can configure the upgrade sequence through the human-machine interface operation module. The upgrade is performed in the order in which they are configured. The specific process of this embodiment is as shown in FIG. 8, and includes: Step S802: The user configures the resource according to the software and hardware configuration of the network management server, and configures the parameter of the upgrade task management list capacity and the maximum number of concurrent connections of the network management server in the M1 module, and configures the parameters. The parameter is forwarded to the M3 module. The M1 module imports the version file and selects the NE to be upgraded. The version information and the NE ID to be upgraded are forwarded to the M2 module to start the upgrade. Step S804: Before upgrading the NE version, the user can configure the upgrade sequence through the human-machine interface operation module. The upgrade is performed in the order in which they are configured. The optimized upgrade sequence of the NE information to be upgraded is forwarded to the M3 module. It is assumed that the network topology upgrade sequence time interval T(n) composed of n network elements is calculated, which depends on the algorithm complexity and the processing capacity of the network management server. Generally, Τ(η) is much smaller than that required to activate n network elements. time. Step S806: The M3 module performs real-time monitoring and scheduling management on the upgrade task thread according to parameters such as the upgrade task management list capacity TASKtota maximum concurrent number TASKmax set by the M1 module. The M3 module receives the request for upgrade information from the M2 module, detects that the current task list is empty, and immediately creates a TASKtotal task in the upgrade order to join the task list, and starts the TASKmax bar Ready state task with the highest priority at the end of the list. The scheduling thread monitors the task status in the task list in real time, and immediately removes the free memory space after the task is executed, and starts the Ready state task at the end of the list. For the download operation, assuming TASKmax, the network element download version file takes an average time Tdownload. According to this patent scheduling method, except for the last less than TASKmax tasks to be executed, the download tasks simultaneously executed in parallel at each time are TASKmax. The download of n network elements is equivalent to being divided into n/Tmax batches. All network elements complete the download time T=Tdownload* n/Tmax, plus the optimized sorting time T(n), and the total time consumption is Τ(η)+Τ . When it is detected that the current task list is TASKtotal tasks, M3 no longer creates the task object, but waits for a period of time after Twait to continue to detect the task management list to determine whether it is possible to continue to create a new task object. The calculation method of Twait is as follows: Suppose the download command response timeout time is Tack, Then Twait=Tack* (TASKtotal/TASKmax-1). The started thread sends the command to the M6 module. For the activation operation, suppose TASKmax, the response timeout time of the NE to the activation command is Tack seconds, and the NE needs to restart the loading version file to make the version take effect. The average time required is Tacitve, based on this patent scheduling method, except for the last less than TASKmax tasks to be executed. In addition, the activation tasks that are simultaneously executed in parallel at each moment are TASKmax. The activation operation of n network elements can be divided into n/Tmax batches, the activation time T=Tack* n/Tmax +Tacitve, plus the optimized upgrade sequence processing time, the total time consumption T(n)+T minutes. When it is detected that the current task list is TASKtotal tasks, M3 no longer creates the task object, but waits for a period of time after Twait to continue to detect the task management list to determine whether it is possible to continue to create a new task object. The calculation method of Twait is as follows: Then T _W ait= Ta _C k * (Ttotal/Tmax-1 ). The started thread sends an activation command to the M6 module. Step S808: The M6 module receives the command from the M3 module. If the download command is received, the M5 module is requested to download the version file, and the download progress and the result are reported to the M4 module; if the activation command is received, the verification is performed. The parameter and the backup version are reported to the M4 module. If the verification is correct, the NE is loaded with the version file, and the restart takes effect. Steps S810 and M4 send the NE version download/activation progress and result information to the M1 module, and the M1 module displays related information to the user. The user can also monitor the upgrade progress and results through the M1 module, and perform corresponding management according to the progress and result information. Operation, such as canceling the download, activation after downloading, etc. Regardless of the embodiment, the solution is in accordance with the essential idea of the embodiment of the present invention, and the upgrade downloading and activation process is upgraded. The upgrade scheduling sequence is optimized according to the network topology structure, and the upgrade task scheduling management is optimized according to the server configuration resources, which are all in the embodiment of the present invention. protected range. Based on the same inventive concept, an embodiment of the present invention further provides a network element upgrading apparatus, and a schematic structural diagram thereof is shown in FIG. 9, which includes: a downloading module 901, configured to perform an upgraded version on at least one network element that needs to be upgraded. The activation module 902 is coupled to the download module 901, and is configured to activate the upgrade version downloaded by each network element after the download of the upgraded version of the at least one network element is completed, and upgrade each network element. In a preferred embodiment, the downloading module 901 can also be configured to sequentially download the upgraded version of the at least one network element in the upgrade order. In a preferred embodiment, the downloading module 901 may be further configured to calculate an upgrade sequence according to the network element list and the network topology of the at least one network element; or, according to the network element list, the network topology, and the link of the at least one network element. The bandwidth information is used to calculate the upgrade sequence; or, the user configures the upgrade sequence through file configuration. From the above description, it can be seen that the present invention achieves the following technical effects: In the embodiment of the present invention, at least one network element that needs to be upgraded is downloaded, and at least one network element to be upgraded is upgraded. After the version is downloaded, activate the upgraded version of each NE to upgrade the NEs. That is, in the embodiment of the present invention, all the network elements are activated after the upgraded version is downloaded, instead of being activated after the single network element downloads the upgraded version, which avoids the downloading and service interruption of the remote network element, and improves the download speed. And the quality of the business. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention. INDUSTRIAL APPLICABILITY The present invention can be applied to the version upgrade of a network element in the communication field. On the one hand, activation is performed after all network elements have downloaded the upgraded version, instead of being activated after a single network element downloads the upgraded version, thereby avoiding The downloading and service interruption of the remote network element improves the download speed and service quality. On the other hand, by serially activating the version from the remote end to the near end, the device can be restarted during the activation process, and the remote device is taken off. The problem that the remote device cannot be upgraded can improve the efficiency of the upgrade.

Claims

Claim

1. A method for upgrading a network element, including:

Download the upgraded version of the specified at least one NE that needs to be upgraded;

After the upgrade versions of the at least one network element are downloaded, the upgraded version downloaded by each network element is activated, and the network elements are upgraded.

The method according to claim 1, wherein the downloading the upgraded version of the specified at least one network element that needs to be upgraded comprises: downloading the upgraded version of the at least one network element in the upgrade order.

The method according to claim 2, wherein the upgrading sequence is determined according to the following steps: determining the upgrading sequence according to the network element list and the network topology of the at least one network element.

The method according to claim 2, wherein the upgrading sequence is determined according to the following steps: determining the upgrading sequence according to the network element list of the at least one network element, the network topology, and the bandwidth information of the link.

The method according to claim 3 or 4, wherein determining the upgrade sequence further comprises: performing, in the order of the distance from the far end to the near end of the at least one network element according to a distance between the network element and the network management server Sort the upgrade order of at least one network element.

6. The method according to claim 2, wherein the upgrading sequence is determined as follows: The upgrading sequence is formulated by a user by file mode configuration.

The method according to any one of claims 1 to 4, wherein before the downloading of the upgraded version of the at least one network element that needs to be upgraded, the method includes: The resource configuration information sets the size of the upgrade task management list, and starts the number of concurrent downloads.

The method according to any one of claims 1 to 4, wherein, in the downloading process, the network management server performs real-time scheduling on the upgrade tasks of the network elements, and records the upgrade progress results of the network elements.

9. A network element upgrading apparatus, comprising:

The downloading module is configured to download the upgraded version of the at least one network element that needs to be upgraded. The activation module is configured to activate the upgraded version downloaded by each network element after the upgraded version of the at least one network element is downloaded. Upgrade each network element.

10. The apparatus according to claim 9, wherein the downloading module is further configured to sequentially download the upgraded version of the at least one network element in an upgrade order.

The device according to claim 10, wherein the downloading module is further configured to calculate the upgrade sequence according to a network element list and a network topology of the at least one network element; or, according to the at least one network element The network element list, the network topology, and the bandwidth information of the link calculate the upgrade sequence; or, the user upgrades the file by the file mode.