Software upgrading method and device

By adopting concurrent loading, horizontal loading, proxy loading and other strategies in large-scale software upgrades, the problem of low software upgrade efficiency in optical switching networks is solved, efficient resource utilization and gateway bottleneck relief, and software upgrade efficiency is improved.

CN119030870APending Publication Date: 2024-11-26HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310614428.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-26
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

In the scenario of large-scale software upgrade, in optical switching networks and optical transmission networks, the number of network elements is huge and the network is complex, resulting in low software upgrade efficiency and insufficient resource utilization, which easily forms a gateway bottleneck.

Method used

Adopt strategies such as concurrent loading, horizontal loading, proxy loading and parallel loading of primary and secondary gateways. By determining appropriate loading strategies and software upgrade models, optimize the allocation of communication link resources, avoid bottlenecks at the gateway, and improve the efficiency of software upgrades.

Benefits of technology

Effectively utilize communication link resources, improve software upgrade efficiency, reduce the transmission pressure of upstream network elements, avoid downstream link idleness, and improve the overall network bandwidth utilization rate.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119030870A_ABST
    Figure CN119030870A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a software upgrading method and device. The method is applied to a centralized management network, and comprises the following steps: determining a loading strategy according to the centralized management network; performing software upgrading on the centralized management network according to the loading strategy; wherein the loading strategy comprises at least one of the following items: concurrent loading, transverse loading and proxy loading. According to the software upgrading method and device provided by the invention, the loading strategy suitable for a certain centralized management network can be determined, so that each network element of the centralized management network in the software upgrading process occupies a communication link as exclusive as possible, further occupies more link bandwidth, avoids forming a bottleneck at a gateway as much as possible, and improves the software upgrading efficiency. And the software upgrading efficiency is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to network and information technology, and more specifically to a method and device for software upgrading. Background Art

[0002] With the development of network and information technology, the optical switching network (OSN) and optical transmission network (OTN) of various operators have become large-scale. For a certain operator, the number of existing network elements is usually in the hundreds of thousands, and the networking is complex. When upgrading the software, the network management system is generally used for centralized management, and the network elements under the network management system are centrally loaded. The network management system establishes point-to-point connection with each network element and loads the software, which easily forms a bottleneck at the gateway, network resources cannot be fully utilized, and the upgrade efficiency is low.

[0003] Therefore, how to make full use of the resources of each link in the scenario of large-scale software upgrade to improve the efficiency of software upgrade is an urgent problem to be solved. Summary of the invention

[0004] The embodiments of the present application provide a method and apparatus for software upgrade, so that in the scenario of large-scale software upgrade, the resources of the communication link can be fully utilized to improve the efficiency of software upgrade.

[0005] In a first aspect, a method for software upgrade is provided, which is applied to a centralized management network, and the method includes: determining a loading strategy based on the centralized management network; performing a software upgrade on the centralized management network according to the loading strategy; the loading strategy includes at least one of the following: concurrent loading, lateral loading, and proxy loading.

[0006] Exemplarily, the centralized management network may be a wavelength division optical network architecture.

[0007] It is understandable that each item in the loading strategy can be used alone or in combination, and this application does not limit this.

[0008] Based on the above scheme, a loading strategy suitable for a certain centralized management network can be determined, so that each network element of the centralized management network can monopolize the communication link as much as possible during the software upgrade process, thereby occupying more link bandwidth, avoiding bottlenecks at the gateway as much as possible, and improving the efficiency of software upgrades.

[0009] In combination with the first aspect, in certain implementations of the first aspect, the lateral loading includes: when the equipment type of the first network element and the second network element is the same, the first network element receives a first type of data from the second network element, and the first type of data is used for software upgrades of the first network element and the second network element.

[0010] It should be noted that horizontal loading includes the vertical centralized loading in the loading strategy in the above embodiment and the horizontal concurrent loading between network elements. One of the network elements of a certain type is selected for centralized loading. Subsequently, the network element that completes the centralized loading can forward the software data packet to the neighboring network element. The network element has the same device type as the neighboring network element. Therefore, the software data packet required for the software upgrade of the neighboring network element is the same as the software data packet required for the software upgrade of the network element loaded in a centralized manner. When the first network element loads the first type of data, the first network element completes the software upgrade; when the second network element loads the first type of data, the second network element completes the software upgrade.

[0011] Based on the above solution, a centralized loading and concurrent loading strategy between horizontal network elements is adopted for software upgrade, so that each network element can monopolize the communication link as much as possible, avoid bottlenecks in the gateway as much as possible, and improve the efficiency of software upgrade.

[0012] In combination with the first aspect, in certain implementations of the first aspect, the agent loading includes: when the device type of the third network element is the same as that of the fourth network element, the third network element sends second type data to the fourth network element through a fifth network element, the device type of the fifth network element is different from that of the third network element, and the second type data is used for software upgrades of the third network element and the fourth network element.

[0013] It should be noted that when the device types of two network elements are the same, the software can be upgraded by lateral loading or by proxy loading. In the specific application process, optimization selection can be made according to the policy selection mechanism in the algorithm. Among them, lateral loading is more suitable for chain networking, which can maximize the use of the links between each hop of the communication link; proxy loading is more suitable for star networking, which can make batch replication of data packages through multicast when sending them to downstream network elements.

[0014] In combination with the first aspect, in certain implementations of the first aspect, when the third network element sends the second type of data to the fourth network element through the fifth network element, the fourth network element occupies the concurrency of the fifth network element, and the concurrency of the fifth network element is used to represent the forwarding capability of the fifth network element.

[0015] It should be noted that the loading strategy may also include proxy loading. The fourth network element is a neighboring network element of the third network element. In one implementation, the fifth network element may be an upstream network element of the third network element and the fourth network element. The third network element may complete the software upgrade by loading the second type of data, and the fourth network element may also complete the software upgrade by loading the second type of data. Due to different device types, the fifth network element will not load the second type of data to complete the software upgrade. The fifth network element plays a role in data forwarding between the third network element and the fourth network element.

[0016] Exemplarily, the loading strategy of proxy loading may be applicable to a scenario where a large number of access network elements are deployed at the end.

[0017] Based on the above solution, the proxy network element (the fifth network element) obtains data and sends the data to the downstream network elements in a one-to-many manner, so that the downstream network elements do not need to obtain data from the network management when upgrading the software, thereby reducing the transmission pressure of the upstream network elements in the centralized management network.

[0018] In combination with the first aspect, in some implementations of the first aspect, the concurrent loading includes: the centralized management network includes a first subnet and a second subnet, and the network elements in the first subnet and the network elements in the second subnet are loaded concurrently.

[0019] In combination with the first aspect, in some implementations of the first aspect, the centralized management network includes a first gateway and a second gateway, the first subnet includes the first gateway, and the second subnet includes the second gateway.

[0020] It is understandable that the loading strategy may include concurrent loading of the primary and backup gateways. That is, the centralized management network may be divided into multiple subnets according to the gateways. Among them, the gateways include at least a primary gateway and a backup gateway. When the first gateway is the primary gateway, the second gateway is the backup gateway; when the first gateway is the backup gateway, the second gateway is the primary gateway. The first gateway and the second gateway may be a gateway that is directly connected to the network management in the centralized management network. Both the first gateway and the second gateway are enabled, and based on these two gateways, the centralized management network is divided into a first subnet and a second subnet with communication links that are as balanced as possible. This allows the first subnet where the first gateway is located and the second subnet where the second gateway is located to be loaded concurrently. Among them, concurrent loading can be understood as loading at the same time.

[0021] In one implementation, the link depth of the first subnet and the link depth of the second subnet are as close as possible, and the communication links of the first subnet and the communication links of the second subnet are as non-overlapping as possible.

[0022] Based on the above solution, each network element in the centralized management network is divided into multiple subnets according to the primary and standby gateways, so that multiple subnets can be loaded concurrently, thereby improving the efficiency of software upgrades.

[0023] In combination with the first aspect, in certain implementations of the first aspect, the loading strategy is determined based on the centralized management network, including: establishing a software upgrade model for the centralized management network, the software upgrade model including at least two subnets; based on information of the centralized management network, determining a minimum cost edge set through the software upgrade model, the minimum cost edge set is used to represent the loading strategy and the loading order, wherein the information of the centralized management network includes at least one of the following: the topological structure of the centralized management network, the link bandwidth of the centralized management network, and the forwarding capability of the network elements in the centralized management network.

[0024] Exemplarily, the network element corresponding to the edge set is the network element to be upgraded in the centralized management network. The minimum cost edge set can be understood as the loading strategy and loading sequence corresponding to the shortest loading time required to complete the software upgrade for a specific network architecture.

[0025] Based on the above solution, by building a model for the centralized management network and determining a certain loading strategy and loading sequence according to the model, the centralized management network can complete software upgrades at a relatively low cost.

[0026] In a second aspect, a software upgrade device is provided, comprising: a processing unit, used to determine a loading strategy based on the centralized management network; the processing unit is also used to perform software upgrade on the centralized management network according to the loading strategy; the loading strategy includes at least one of the following: concurrent loading, lateral loading, and proxy loading.

[0027] In combination with the second aspect, in certain implementations of the second aspect, the lateral loading includes: when the first network element and the second network element have the same device type, the first network element receives first type data from the second network element, and the first type data is used for software upgrades of the first network element and the second network element.

[0028] In combination with the second aspect, in certain implementations of the second aspect, the agent loading includes: when the third network element and the fourth network element have the same device type, the third network element sends second type data to the fourth network element through a fifth network element, the fifth network element and the third network element have different device types, and the second type data is used for software upgrades of the third network element and the fourth network element.

[0029] In combination with the second aspect, in certain implementations of the second aspect, when the third network element sends the second type of data to the fourth network element through the fifth network element, the fourth network element occupies the concurrency of the fifth network element, and the concurrency of the fifth network element is used to indicate the forwarding capability of the fifth network element.

[0030] In combination with the second aspect, in some implementations of the second aspect, the concurrent loading includes: the centralized management network includes a first subnet and a second subnet, and the network elements in the first subnet and the network elements in the second subnet are loaded concurrently.

[0031] In combination with the second aspect, in some implementations of the second aspect, the centralized management network includes a first gateway and a second gateway, the first subnet includes the first gateway, and the second subnet includes the second gateway.

[0032] In combination with the second aspect, in certain implementations of the second aspect, the processing unit is specifically used to establish a software upgrade model for the centralized management network, and the software upgrade model includes at least two subnets; the processing unit is also used to determine a set of edge sets with minimum cost through the software upgrade model based on information of the centralized management network, and the set of edge sets with minimum cost is used to represent the loading strategy and loading order, wherein the information of the centralized management network includes at least one of the following: the topological structure of the centralized management network, the link bandwidth of the centralized management network, and the forwarding capability of the network elements in the centralized management network.

[0033] In a third aspect, a software upgrade device is provided, comprising: a processor coupled to a memory, the memory being used to store a computer program, the processor being used to run the computer program, so that the software upgrade device executes the method in the first aspect and any possible implementation thereof.

[0034] In combination with the third aspect, in some implementations of the third aspect, the device also includes one or more of the memory and the transceiver, and the transceiver is used to receive signals and / or send signals.

[0035] In a fourth aspect, a computer-readable storage medium is provided, which includes a computer program or instructions. When the computer program or instructions are run on a computer, the method in the above-mentioned first aspect and any possible implementation thereof is executed.

[0036] In a fifth aspect, a computer program product is provided, characterized in that the computer program product comprises a computer program or instructions, and when the computer program or instructions are run on a computer, the method in the above-mentioned first aspect and any possible implementation thereof is executed.

[0037] In a sixth aspect, a chip is provided, which includes a processor and a data interface, and the processor reads instructions stored in a memory through the data interface to execute the above-mentioned first aspect and any software upgrade method that can be implemented in the first aspect.

[0038] In combination with the sixth aspect, in a possible implementation manner, the processor is coupled to the memory through an interface.

[0039] In combination with the sixth aspect, in a possible implementation, the chip system also includes a memory, in which a computer program or computer instructions are stored. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 It is a schematic diagram of a network system architecture provided in an embodiment of the present application.

[0041] Figure 2 It is a schematic diagram of a scenario provided in an embodiment of the present application.

[0042] Figure 3 It is a schematic diagram of a wavelength division optical network architecture provided in an embodiment of the present application.

[0043] Figure 4 This is a schematic diagram of a subnet architecture provided in an embodiment of the present application.

[0044] Figure 5 It is a schematic flowchart of establishing a software upgrade module provided in an embodiment of the present application.

[0045] Figure 6 It is a schematic flowchart of a software upgrade method provided in an embodiment of the present application.

[0046] Figure 7 It is an exemplary structural diagram of a software upgrading device provided in an embodiment of the present application.

[0047] Figure 8 It is an exemplary structural diagram of a software upgrading device provided in an embodiment of the present application.

[0048] Fig. 9 This is an exemplary structural diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0050] Figure 1 A network system architecture diagram provided by an embodiment of the present application is shown, in which a network management system, a gateway and a network element are included. The network management system is directly connected to the gateway in communication. The network element is a downstream network element of the gateway. Figure 1 The gateways shown in FIG. 1 or other network elements with data forwarding capabilities can be dispersed in the network architecture. Generally speaking, in order to facilitate the dispersion of management traffic, gateways are generally not concentrated in the upstream of the network architecture. Figure 1The network architecture shown in the figure adopts a centralized loading method for software upgrade, and the communication link has a long path and many hops. For example, the network management performs point-to-point loading with each gateway 1. The upstream communication link has a large load and a heavy workload for processing data, while the downstream communication link has a small load and relatively idle bandwidth. Generally speaking, the bandwidth of the downstream network element is smaller and the ability to forward data is weaker. Figure 1 When performing large-scale software upgrades in the network architecture shown, the upstream network elements close to the network management system need to process a large amount of data, resulting in bandwidth and forwarding capacity bottlenecks. In addition, the downstream communication links are often idle, making it difficult to fully utilize network resources, and the efficiency of software upgrades is low. It takes a lot of time to complete the software upgrade of the entire network.

[0051] Therefore, in order to solve the above technical problems, the present application provides a method for software upgrade, which can be applied to the network architecture of large-scale software upgrade, proposes a loading strategy, and performs upgrade arrangement based on the loading strategy, so that when the software is loaded, the resources on each communication link are evenly distributed, which can alleviate the upstream gateway forwarding bottleneck while avoiding the idleness of the downstream communication link. The bandwidth resources in the network are fully utilized, and the efficiency of software upgrade is improved.

[0052] like Figure 2 As shown, a schematic diagram of a scenario in which the software upgrade method provided in the embodiment of the present application can be applied is shown. The software upgrade method provided in the embodiment of the present application can be applied to network element upgrades in an interconnected centralized management network. Figure 2 Centralized management of network management, gateways, and various network elements (such as Figure 2 The upgraded software package can be transmitted through the communication links in the centralized management network, which may have bottleneck nodes and link multiplexing. For example, telecommunication networks, information technology (IT) facility networks.

[0053] Therefore, an embodiment of the present application provides a software upgrade method, which includes the following loading strategy.

[0054] 1. Link concurrency orchestration.

[0055] For multiple network elements under the same gateway, multiple concurrent communication links can be used to undertake upgrade tasks at the same time. If multiple network elements use one communication link during software upgrade, the concurrency of network elements that can be upgraded on this communication link depends on the forwarding capabilities of each upstream network element. In other words, the concurrency of network elements that can be upgraded on each communication link is limited by the forwarding capabilities of each upstream network element. If the concurrency of network elements that can be upgraded needs to be increased, the communication links can be managed concurrently, and the communication links in the network architecture to be upgraded can be concurrently arranged. During the software upgrade process, multiple communication links can be used for upgrades to improve the efficiency of software upgrades.

[0056] 2. The primary and standby gateways are loaded in parallel.

[0057] Generally speaking, in the network architecture, the network element that is directly connected to the network management can be understood as a gateway. The gateway can include a primary gateway and a backup gateway. In order to improve the efficiency of upgrading software, the backup gateway can also independently bear the software loading traffic of a part of the network element. Among them, in order to avoid resource waste, the network elements managed by the primary gateway and the backup gateway and the corresponding communication links do not overlap.

[0058] It can be understood that the main gateway and the backup gateway independently bear the software loading traffic of some network elements, and it can also be understood that the backup gateway assists the main gateway and independently bears the software loading traffic of the remaining network elements except for the network elements borne by the main gateway. The main gateway and the backup gateway respectively load the software traffic of their respective downstream network elements in parallel to improve the efficiency of software upgrade.

[0059] 3. Centralized loading.

[0060] For network elements of different types and layers, the above-mentioned link arrangement method is used to make the network elements in the network architecture as dispersed as possible, and each network element tries to monopolize the communication link. For network elements of the same type or the same layer, one of the network elements is selected for centralized loading, occupying a concurrency of the upstream network element of the network element. The centralized loading method can avoid the congestion of the upstream communication link caused by the transmission of software data packets of the network elements to be upgraded from the network management.

[0061] 4. Loading between neighboring network elements.

[0062] Exemplarily, one of the multiple network elements of the same type is selected for centralized loading. After the network element loads the software data package, the software data package can be loaded to the neighboring network element of the same type. This avoids the neighboring network element from directly communicating with the network management when loading the software, and avoids the occupation of the upstream communication link bandwidth and the concurrency of the upstream network element by the neighboring network element loading the software data package. The loading between neighboring network elements can release the upstream communication link to a certain extent, try not to affect the software upgrade of the upstream network element, and avoid the formation of bottlenecks at the gateway.

[0063] 5. Proxy loading.

[0064] Exemplarily, there are multiple network elements downstream of a network management system, and each network element can be divided according to type. For network elements of the same type, a proxy loading method can be adopted. That is, the proxy network element downloads the software data package from the network management system, and the proxy network element can forward the software data package to the downstream network element in a one-to-many manner. The bandwidth occupied by this proxy loading method is the sum of the bandwidths of the terminal network elements. The proxy loading method is suitable for scenarios where a large number of access network elements are deployed at the end. For example, the customer premises equipment (CPE) network element can be loaded through the central office (CO) network element proxy to achieve one-to-many concurrent loading.

[0065] For ease of understanding, Figure 3 As shown, a wavelength division optical network architecture is shown. Taking a specific wavelength division optical network as an example, the software upgrade method provided by the embodiment of the present application is specifically introduced. Among them, a wavelength division optical network includes a mixed network of multiple devices. Due to the differences in service levels, the system has a relatively clear hierarchical structure, and the network element devices at each layer can be regarded as the same type of devices. For example, Figure 3 The network architecture in the example includes a backbone layer, a convergence layer, and an access layer. The device types of the network element devices in the backbone layer are the same, the device types of the network element devices in the convergence layer are the same, and the device types of the network element devices in the access layer are the same. The symbols shown in the module are abbreviations of the device types, for example, an optical switching network (OSN) 9800U32E (such as Figure 3 U32E in), OSN9800M24 (such as Figure 3 M24 in etc. Figure 3 In the network architecture in , the deeper the number of hops, the more network elements there are, the smaller the bandwidth, and the weaker the central processing unit (CPU) resources. The number of network elements in the multiple subnets of this network architecture is about 1000. Figure 3In the network architecture shown, the uploading strategy can be applied to perform software upgrades.

[0066] Specifically:

[0067] (1) Concurrent loading of the primary and backup gateways.

[0068] For example, Figure 3 The figure shows two gateways that are directly connected to the network management, namely, the intra-province connection gateway A and the intra-province connection gateway B. Among them, the intra-province connection gateway A can be understood as the main gateway, and the intra-province connection gateway B can be understood as the backup gateway. The intra-province connection gateway A and the intra-province connection gateway B are both enabled during the software upgrade. Figure 3 The network architecture can be divided into two subnets based on the intra-province connection gateway A and the intra-province connection gateway B. The depth (number of hops) of the communication links in these two subnets should be as balanced as possible. Figure 3 The network architecture is divided into two subnets, left and right, based on the intra-provincial connection to Gateway A and the intra-provincial connection to Gateway B. These two subnets are loaded concurrently, which improves the utilization efficiency of the communication link to a certain extent.

[0069] It should be noted that concurrent loading of two subnets can be understood as loading of two subnets at the same time.

[0070] It should be understood that if only the main gateway is enabled during the software upgrade, the backup gateway serves as a backup for the main gateway and can only perform the tasks of the main gateway when the main gateway fails. Then, during the software upgrade, only the main gateway is loaded, and the loading efficiency is lower than the efficiency of concurrent loading of the main and backup gateways.

[0071] (2) Longitudinal concentrated loading.

[0072] For example, according to Figure 3 The hierarchical networking feature of a wavelength division optical network is shown, and each layer is deployed with network elements of the same device type. For example, the convergence layer is deployed with network elements of the same device type OSN9800M24, and the access layer is deployed with network elements of the same device type OSN9800M24 / OSN1800V. When upgrading the software, a certain network element can be selected from the network elements of the same device type in each layer for centralized loading, and one or more of the other network elements of the same device type in the layer are determined as network elements to be upgraded, avoiding the bottleneck of the upstream communication link, so that the network elements loaded in a centralized manner can monopolize the bandwidth of the upstream network elements, and can improve the utilization of bandwidth.

[0073] Specifically, according to the planning algorithm and based on the principle of concurrent link orchestration, a certain network element can be selected from the network elements of the same device type at each layer for centralized loading.

[0074] It should be noted that the network element selected for centralized loading may also be a network element to be upgraded.

[0075] (3) Concurrent loading between horizontal network elements.

[0076] Exemplarily, after one of the network elements of the same type is selected in each layer for centralized loading, the software data packet is horizontally forwarded to other network elements of the same type and in the same layer to be upgraded. Among them, the target network element to which the centralized loaded network element forwards the software data packet can be understood as the neighboring network element of the network element, and the software data packet required for the neighboring network element to upgrade the software is the same as the software data packet required for the centralized loaded network element to upgrade the software. Therefore, the neighboring network element can load the software according to the software data packet from the centralized loaded network element.

[0077] For example, Figure 3 The leftmost OSN9800M24 network element in the convergence layer shown in the figure is selected as the network element for centralized loading, and its adjacent right OSN9800M24 network element is its neighbor network element. The leftmost OSN9800M24 network element obtains the software data packet from the leftmost OSN9800U32E upstream network element in the backbone layer, and after centralized loading, it forwards the software data packet to the neighbor network element.

[0078] It should be noted that the neighboring network element obtains the software data package from the centralized loading network element, which can avoid all the software data packages to be upgraded being obtained directly from the network management, and to a certain extent can alleviate the forwarding pressure of the upstream communication link and avoid causing data forwarding bottlenecks.

[0079] (4) Proxy loading.

[0080] For example, the network element to be upgraded is Figure 3 In the customer terminal device CPE shown in FIG. 1 , the upstream network element of the customer terminal device is CO. The upstream network element CO can be used as a relay node. For the CPE that has been loaded, the software data package can be loaded to the neighbor network element CPE managed by the relay node CO through the relay node CO.

[0081] For example, after the leftmost network element CPE completes loading, the software data package can be loaded to the neighboring network element CPE of the leftmost network element CPE through its upstream network element (the leftmost CO network element). The neighboring network element CPE and the leftmost CPE network element are managed by the leftmost CO network element.

[0082] It should be noted that the terminal network element can load other network elements of the same layer through a one-to-many proxy loading method, avoiding sending too many software data packets from the network management as much as possible, which can alleviate the data forwarding pressure of the upstream communication link.

[0083] For ease of understanding, the following Figure 3 Taking the software upgrade of China Network Element CPE as an example, the forwarding process of the software data packet is specifically introduced.

[0084] Specifically, Figure 3 Each network element in the network architecture shown is in the optical transmission network (OTN). The network architecture is divided into two other subnets based on the main gateway connecting to gateway A in the province and the backup gateway connecting to gateway B in the province. Among them, the subnet where the main gateway connects to gateway A in the province is Figure 3 The area included by the dotted line is a subnet that includes the provincial dispatching core A network element OSN9800U64E / OSN9800U32E that is communicatively connected to the provincial A gateway. The network manager sends the software data packet to the provincial dispatching core A network element OSN9800U64E / OSN9800U32E through the provincial A gateway. Figure 3In the figure, the provincial capital core A network element OSN9800U32E and the provincial capital core B network element OSN9800U32E can be understood as network elements of the same device type, and the provincial capital core A network element OSN9800U32E is selected for centralized loading. In other words, the provincial capital core A network element OSN9800U32E accepts the software data packet from the provincial capital dispatching core A network element OSN9800U64E / OSN9800U32E. After the provincial capital core A network element OSN9800U32E is loaded, the software data packet can be sent to the neighboring network element provincial capital core B network element OSN9800U32E. In other words, the provincial capital core B network element OSN9800U32E can complete the loading according to the software data packet from the neighboring network element provincial capital core A network element OSN9800U32E. Furthermore, according to the hierarchical structure characteristics of the network structure, the provincial capital core A network element OSN9800U32E can send the software data packet to the network element OSN9800M24 of the convergence layer. Similarly, in the convergence layer, multiple network elements of the OSN9800M24 device type can be loaded in the above-mentioned loading method similar to multiple network elements of the U32E device type. The network element OSN9800M24 sends the software data packet to the network element OSN9800M24 / OSN1800V of the access layer. Similarly, in the access layer, multiple network elements of the OSN9800M24 / OSN1800V device type can be loaded in the above-mentioned loading method similar to multiple network elements of the OSN9800U32E device type. In other words, the device type of each layer of network elements is the same, and the above-mentioned vertical centralized loading and horizontal concurrent loading methods are used to complete the loading of the network elements to be upgraded in each layer. Furthermore, the network element OSN9800M24 / OSN1800V sends the software data packet to the network element CO, where one network element CO can manage one or more customer terminal devices. The network element CO sends the software data packet to the customer terminal device A. After the customer terminal device A completes the loading, the network element CO acts as a relay node and sends the software data packet to the neighboring network element customer terminal devices managed by the network element CO through the network element CO. The network element software upgrade process for the subnet where the backup gateway is located is similar to the network element software upgrade process for the subnet where the main gateway is located, and will not be repeated here.

[0085] Based on the above specific software upgrade process, Figure 3 The multiple client terminal equipment network elements shown in the network architecture complete the software upgrade, so that under certain network resource conditions, the utilization efficiency of the communication link is improved, the bottleneck of the upstream communication link is avoided, and the bandwidth can be maximized, thereby improving the efficiency of the software upgrade.

[0086] For ease of understanding, Figure 4 As shown, the subnet architecture of a certain operator is shown. Below, taking the subnet as an example, the method for software upgrade provided in the embodiment of the present application is specifically introduced.

[0087] like Figure 4 As shown in FIG. 1 , a network architecture of a subnet managed by a certain operator is shown. The network architecture includes multiple network elements. These multiple network elements can be divided into seven types of devices according to the device type, corresponding to Figure 4 The letters in . Figure 4 The line segments between the network elements are only an exemplary communication connection method. It should be understood that the network elements in the network architecture can establish communication connections with each other.

[0088] Among them, G1 and G2 represent two gateway network elements (GNE), and the concurrency of these two network elements is 5. It can be understood that gateway G1 and gateway G2 can load software data packages for 5 network elements at the same time respectively, and do not affect each other. According to the two gateway network elements G1 and G2, the network architecture is divided into two subnets (the first subnet and the second subnet) with similar communication link depth and similar hop count. Taking the first subnet as an example, the following introduces the specific process of software upgrade for the network elements in the first subnet.

[0089] In addition to the gateway G2, the first subnet also includes network element A (including network element A1, network element A2, network element A3, network element A4 and network element A5), network element B, network element C (including network element C1 and network element C2), network element D, network element E, and network element F. Specifically, network element A may be a network element of device type OSN9800U32E, network element B may be a network element of device type OSN9800M12, network element C may be a network element of device type OSN9800UPS, network element D may be a network element of device type OSN1800V, network element E may be a network element of device type OSN1800IE, and network element F may be a network element of device type CPE.

[0090] First, the first batch of proxy loading is performed. The proxy nodes for the first batch of proxy loading are network element A, that is, network element A1, network element A2 and network element A3 in the first subnet. Network element A as a proxy node can be used to forward software data packets, but network element A does not load the software data packet. Specifically, network element A1 acts as a proxy for network element D, network element A2 acts as a proxy for network element E, and network element A3 acts as a proxy for network element F. Gateway G2 sends software data packets to network element D through network element A1, sends software data packets to network element E through network element A2, and sends software data packets to network element F through network element A3. Network element D, network element E and network element F are loaded respectively. Network element B receives the software data packet from gateway G2 and loads it; network element C1 receives the software data packet from gateway G2 and loads it. Since the concurrency of gateway G2 is 5, it can be understood that gateway G2 can send software data packets to up to 5 network elements at a time. That is to say, when the first batch of agents are loaded, gateway G2 sends software data packets to five network elements (network element A1, network element A2, network element A3, network element B, and network element C1). In fact, gateway G2 needs to send software data packets to network element D, network element E, and network element F. Therefore, network element A1, network element A2, and network element A3 are selected as agent nodes, and gateway G2 sends software data packets to network element D, network element E, and network element F respectively through these three agent nodes.

[0091] After the first batch of loading processes, each network element in the first subnet has completed the loading of some network elements. Specifically, the network elements that have not completed loading include network element A1, network element A2, network element A3, network element A4, network element A5 and network element C2. In order to load the above network elements, a second batch of proxy loading is required. During the second batch of proxy loading, gateway G2 is selected as the proxy node. Gateway G2 as a proxy node can be used to forward software data packets, but gateway G2 does not load the software data packet. In the process of the second batch of proxy loading, the concurrency of gateway G2 is 5. It can be understood that gateway G2 can send software data packets to network element A1 and network element C2 respectively. Since network element A1 has the same device type as network element A2, network element A3, network element A4 and network element A5, network element A1 is selected for centralized loading. After network element A1 completes centralized loading, it sends the software data packet to neighboring network elements A2, network element A3, network element A4 and network element A5 of the same device type. After the second batch of loading, all network elements in the first subnet completed the software upgrade.

[0092] For a certain network element, the time required for the network element to complete loading can be calculated according to the following formula (1).

[0093] T=X / v / C*m*n*q Formula (1)

[0094] Among them, T represents the loading time; X represents the size of the software data packet; v represents the average bandwidth transmission rate; C represents concurrency; m represents bandwidth utilization; n represents efficiency parameter; and q represents the number of loading batches.

[0095] It should be noted that the size of the software data packets of different network elements may be different. There may be multiple other network elements between the network element and the network management, and the bandwidth transmission rate between different network elements is also different. Therefore, in formula (1), the average bandwidth transmission rate between the network element and the network management can be used for calculation. The concurrency in formula (1) can be understood as the concurrency of the upstream network element of the network element.

[0096] For example, the software data packet size of the network element OSN9800U is 1.6GB, the software data packet size of the network element OSN9800UPS is 1GB, the software data packet size of the network element OSN1800IE / OSN1800V is 0.6GB, and the software data packet size of the network element CPE is 0.4GB. The bandwidth of the 98 network is 13MB, the bandwidth of the 18 network is 2.5MB, and the bandwidth of the CPE is 0.5MB.

[0097] For example, if the concurrency of the upstream network element is 5, the software upgrade of all network elements OSN9800UPS in the network architecture needs to be loaded in 18 batches, the bandwidth utilization is 0.7, the efficiency parameter is 0.7, the software data packet size is 1GB, and the average bandwidth transmission rate is 5MBps. According to the above formula (1), the loading time is: (1GB / 5MBps / 5*0.7*0.7)*18=5015min.

[0098] It can be seen that under the conditions of fixed software data packet size, average bandwidth transmission rate, bandwidth utilization and efficiency parameters, the parameter that affects the loading time is the concurrency of the upstream network element. Therefore, reducing the concurrency of the upstream network element can reduce the loading time and improve the software upgrade efficiency of the network element.

[0099] For example, according to the above Figure 4 For example, the network element CPE can be Figure 4 NE F is shown in FIG. NE F receives software data packets from proxy node NE A3, that is, the upstream NE of NE F is NE A3. In the first batch of proxy loading processes, NE A3 only sends software data packets to NE F, that is, the concurrency of NE A3 is 1. At the same time, because the size of the software data packet of NE CPE is 0.4GB, the average bandwidth transmission rate is 0.5MBps, the bandwidth utilization is 0.7, and the efficiency parameter is 0.7. According to the above formula (1), the loading time is: 0.4GB / (0.5MBps*0.7*0.7)=222min.

[0100] For example, according to the above Figure 4 For example, the loading of the network element OSN9800U can be Figure 4 NE A1, NE A2, NE A3, NE A4, and NE A5 are shown in FIG. Since NE A1, NE A2, and NE A3 act as proxy nodes in the first batch of proxy loading processes, they do not load their own software data packages. In the second batch of proxy loading processes, NE A1 is selected for centralized loading, and the loading of NE A2, NE A3, NE A4, and NE A5 is completed according to the concurrent loading method between neighboring NEs. Among them, the concurrency of the upstream NEs of NE A is 1, and because the software data package size of NE OSN9800U is 1.6GB, the average bandwidth transmission rate is 0.5MBps, the bandwidth utilization is 0.7, and the efficiency parameter is 0.7. According to the above formula (1), the loading time is: 1.6GB / (0.5MBps*0.7*0.7)=89min.

[0101] Based on the above scheme, the above loading strategy is formulated to avoid the bottleneck of the upstream communication link, relieve the forwarding pressure of the upstream network element, improve the bandwidth utilization of the entire network architecture, and avoid the waste of bandwidth resources. Based on the above loading strategy, the concurrency of the network element is reduced, thereby reducing the loading time of the network element and improving the efficiency of the network element software upgrade.

[0102] Furthermore, based on the above loading strategy, a software upgrade model is established. The software upgrade model can be used to determine the optimal loading path for the network architecture software upgrade. The specific process of establishing the software upgrade module is as follows: Figure 5 As shown, the process of establishing the model is introduced in detail below.

[0103] S501, determining a topology map.

[0104] For example, Figure 3 It can be understood as a topological diagram. Figure 3 The figure shows a connection relationship of network devices. Since the actual communication connection relationship between network devices is relatively complex, Figure 3 Only partial connection relationships of network devices are shown.

[0105] It should be noted that the topology diagram proposed in the embodiment of the present application is a schematic diagram of the connection relationship of network devices. Under the same network architecture, the topology diagrams obtained from different network element perspectives may be different. For example, Figure 3 This is a topology diagram obtained from the gateway's perspective.

[0106] S502, divide the subnet.

[0107] Exemplarily, according to the location of each network element in the network architecture, the network devices are divided into non-overlapping subnets with relatively balanced communication links through the gateway. Exemplarily, the network devices are divided into Figure 4 The first subnet and the second subnet are shown, wherein the network devices in the first subnet do not overlap with the network devices in the second subnet, and the communication links in the first subnet and the communication links in the second subnet are relatively balanced.

[0108] It should be noted that the network architecture is divided into multiple subnets through the gateway, so that network elements (or network devices) in multiple subnets can be loaded concurrently.

[0109] S503: Determine a directed graph.

[0110] Exemplarily, based on the topology diagram, a directed graph is determined with the gateway as the vertex, each network element in the subnet as a node, and bandwidth as the weight. The nodes in the directed graph have data forwarding capabilities.

[0111] S504: Determine a software upgrade model according to the directed graph.

[0112] Exemplarily, the directed graph determined in the above step S503 is modeled, and vertex sets, edge sets, start point sets, end point sets, concurrency, end-to-end bandwidth, and loading time are defined.

[0113] It should be noted that the vertex set can be understood as a set of network elements; the starting point set can be understood as a set of gateway network elements; and the end point set can be understood as a set of network elements to be upgraded. The concurrency of a network element is related to the forwarding capability and bandwidth of the network element (concurrency = forwarding capability of the network element / bandwidth), where the forwarding capability of the network element is related to the device type of the network element and the processing capability of the CPU of the network element. For any network element to be loaded in the network architecture, the end-to-end bandwidth of the network element to be loaded is related to the link bandwidth and concurrency. For example, Figure 3 As shown, the network element to be loaded is CPE, and there are multiple communication links between the gateway and the network element CPE (for example, the communication link between the main gateway and the network element OSN9800U64E / U32E; the communication link between the network element OSN9800U64E / U32E and the network element OSN9800U32E, etc.), and the bandwidth of each communication link is divided by the concurrency to obtain the end-to-end bandwidth of the communication link. The minimum value of the end-to-end bandwidth of the multiple communication links can be understood as the end-to-end bandwidth of the network element to be loaded. The loading time can be understood as the time required for the network element to be loaded to complete the software upgrade. The loading time is related to the size of the software data packet and the end-to-end bandwidth (loading time = software data packet size / end-to-end bandwidth).

[0114] S505, determine the edge set with the minimum cost, and generate a loading strategy and loading sequence.

[0115] Exemplarily, before determining the edge set with the minimum cost, a software upgrade model is determined. The software upgrade model includes the vertex set, edge set, starting point set, end point set, concurrency, end-to-end bandwidth, and loading time defined in the above step S504. Through the above software upgrade model, a loading strategy is selected according to parameters such as the topological structure of the actual network architecture, link bandwidth, and forwarding capability of the network element. Under certain concurrency conditions, the edge set with the minimum cost is obtained, and the network element corresponding to the edge set is the network element set to be upgraded. Among them, the edge set with the minimum cost can be understood as the network element upgrade sequence corresponding to the shortest loading time required to complete the software upgrade for a specific network architecture. That is to say, for a specific network architecture, the loading strategy described above can be adopted, and the specific characteristics of the network architecture (for example, link bandwidth, forwarding capability of the network element, etc.) can be input into the software upgrade model to obtain the network element upgrade sequence with the minimum cost in the network architecture. Among them, the network element upgrade sequence can be understood as the loading sequence.

[0116] It should be noted that the loading strategy described above can be applied to different network architectures, but for a specific network architecture, there can be multiple upgrade sequences for network elements in the network architecture according to the loading strategy. Further based on the software upgrade model, the network element upgrade sequence with the minimum cost is determined from the upgrade sequences of multiple network elements, and then the optimal network element upgrade sequence for the network architecture is obtained, thereby improving the efficiency of software upgrade.

[0117] S506, upgrading the network elements to be upgraded, and removing the upgraded network elements from the destination set.

[0118] Exemplarily, the network elements to be upgraded in the end point set are subjected to software upgrade, and the network elements whose software upgrade is completed are added to the start point set and removed from the end point set.

[0119] S507: Determine whether the destination set is empty.

[0120] Exemplarily, when the endpoint set is empty, all network elements have completed the software upgrade; when the endpoint set is not empty, it means that there are still network elements to be upgraded, and the above steps S505 and S506 are continued to be executed.

[0121] It should be noted that through the above Figure 5The steps shown can obtain the loading strategy and loading order (or loading path) of a certain network architecture software upgrade. In the specific implementation process, this step can be performed online or offline. Among them, a certain network architecture may include multiple network elements. Online execution can be understood as that each time the loading strategy and loading order of a network element are generated, the above steps will be re-executed to generate the loading strategy and loading order of the next network element; offline execution can be understood as that before the network elements of the network architecture are upgraded, the loading strategy and loading order of each network element are pre-determined, and during the software upgrade process, the software of each network element is upgraded according to the determined loading strategy and loading order.

[0122] like Figure 6 As shown, a software upgrade method provided by the present application is shown. The method can be applied to a centralized management network. The method is described in detail below.

[0123] S601: Determine a loading strategy according to a centralized management network.

[0124] For example, the centralized management network can be Figure 3 The wavelength division optical network architecture shown in FIG.

[0125] S602: Perform software upgrade on the centralized management network according to the loading strategy.

[0126] Exemplarily, the loading strategy includes at least one of the following: concurrent loading, lateral loading, and proxy loading.

[0127] In one implementation, the lateral loading includes: when the first network element and the second network element have the same device type, the first network element receives first type data from the second network element, and the first type data is used for software upgrade of the first network element and the second network element.

[0128] It can be understood that horizontal loading includes the vertical centralized loading in the loading strategy in the above embodiment and the horizontal concurrent loading between network elements. One of the network elements of a certain type is selected for centralized loading. Subsequently, the network element that completes the centralized loading can forward the software data packet to the neighboring network element. The network element has the same device type as the neighboring network element. Therefore, the software data packet required for the software upgrade of the neighboring network element is the same as the software data packet required for the software upgrade of the network element loaded in a centralized manner. When the first network element loads the first type of data, the first network element completes the software upgrade; when the second network element loads the first type of data, the second network element completes the software upgrade.

[0129] Exemplarily, the first network element and the second network element may be as follows Figure 3In the OSN9800M24 network element shown, the second network element is the leftmost OSN9800M24 network element of the convergence layer, and the first network element is the right OSN9800M24 network element adjacent to the first network element. Among the multiple OSN9800M24 network elements, the leftmost OSN9800M24 network element of the convergence layer is selected for centralized loading according to the first type of data, and the right adjacent OSN9800M24 network element can also be loaded according to the first type of data.

[0130] In one implementation, the agent loading includes: when the device type of the third network element is the same as that of the fourth network element, the third network element sends the second data type to the fourth network element through the fifth network element, the device type of the fifth network element is different from that of the third network element, and the second type of data is used for software upgrades of the third network element and the fourth network element.

[0131] It should be noted that when the device types of two network elements are the same, the software can be upgraded by lateral loading or by proxy loading. In the specific application process, optimization selection can be made according to the policy selection mechanism in the algorithm. Among them, lateral loading is more suitable for chain networking, which can maximize the use of the links between each hop of the communication link; proxy loading is more suitable for star networking, which can make batch replication of data packages through multicast when sending them to downstream network elements.

[0132] In one implementation, when the third network element sends the second type of data to the fourth network element through the fifth network element, the fourth network element occupies the concurrency of the fifth network element, and the concurrency of the fifth network element is used to represent the forwarding capability of the fifth network element.

[0133] It should be noted that the loading strategy may also include the proxy loading in the above embodiment. The fourth network element is a neighboring network element of the third network element. In one implementation, the fifth network element may be an upstream network element of the third network element and the fourth network element. The third network element may complete the software upgrade by loading the second type of data, and the fourth network element may also complete the software upgrade by loading the second type of data. Due to the different device types, the fifth network element will not load the second type of data to complete the software upgrade. The fifth network element plays a role in data forwarding between the third network element and the fourth network element.

[0134] For example, Figure 3 Taking the centralized management network shown in the figure as an example, the third network element is the leftmost network element CPE, the fourth network element is the neighboring network element CPE of the network element, and the fifth network element is the leftmost network element CO. After the leftmost network element CPE completes loading, the second type of data packet can be loaded to the neighboring network element CPE of the leftmost network element CPE through its upstream network element (the leftmost CO network element). The neighboring network element CPE and the leftmost CPE network element are managed by the leftmost CO network element.

[0135] In one implementation, the concurrent loading includes: the centralized management network includes a first subnet and a second subnet, and the network elements in the first subnet and the network elements in the second subnet are loaded concurrently.

[0136] In one implementation, the centralized management network includes a first gateway and a second gateway, the first subnet includes a first network manager, and the second subnet includes a second gateway.

[0137] It is understandable that the loading strategy may include concurrent loading of the primary and backup gateways. That is, the centralized management network may be divided into multiple subnets according to the gateways. Among them, the gateways include at least a primary gateway and a backup gateway. When the first gateway is the primary gateway, the second gateway is the backup gateway; when the first gateway is the backup gateway, the second gateway is the primary gateway. The first gateway and the second gateway may be a gateway that is directly connected to the network management in the centralized management network. Both the first gateway and the second gateway are enabled, and based on these two gateways, the centralized management network is divided into a first subnet and a second subnet with communication links that are as balanced as possible. This allows the first subnet where the first gateway is located and the second subnet where the second gateway is located to be loaded concurrently. Among them, concurrent loading can be understood as loading at the same time.

[0138] For example, Figure 3 Taking the centralized management network shown in FIG. 1 as an example, the first gateway may be a gateway A connected within the province, the second gateway may be a gateway B connected within the province, and the first subnet is the subnet corresponding to the gateway A connected within the province ( Figure 3 The dotted part in the figure), the second subnet is the subnet corresponding to the B gateway within the province.

[0139] Specifically, determining a loading strategy based on a centralized management network includes: establishing a software upgrade model for the centralized management network, the software upgrade model including at least two subnets; determining a minimum cost edge set through the software upgrade model based on information of the centralized management network, the minimum cost edge set being used to represent the loading strategy and loading order, wherein the information of the centralized management network includes at least one of the following: a topological structure of the centralized management network, a link bandwidth of the centralized management network, and a forwarding capability of a network element in the centralized management network.

[0140] That is to say, it is necessary to establish a model for the centralized management network and determine a certain loading strategy and loading order based on the model, so as to complete the software upgrade of the centralized management network at a relatively low cost. Figure 5 The description is not repeated here.

[0141] Based on the above scheme, in the scenario of centralized management network software upgrade, the centralized management network can be modeled, and a specific loading strategy and loading sequence can be obtained according to the model, so that each network element in the centralized network can perform software upgrades according to a certain loading strategy and loading sequence. Under certain network resource conditions, the utilization efficiency of the communication link can be improved, bottlenecks in the upstream communication link can be avoided, and the bandwidth can be fully utilized as much as possible, thereby improving the efficiency of the software upgrade.

[0142] Figure 7 The schematic diagram of the structure of a software upgrade device 700 of an embodiment of the present application is shown. In one possible implementation, the software upgrade device 700 includes: a processing unit 710; in one possible implementation, the software upgrade device 700 may also include a transceiver unit 720 when it is necessary to complete the transmission of information and / or data. It should be understood that Figure 7 The software upgrade device shown is only an example, and may also include other units, or include Figure 7 The units in the same function are not necessarily included. Figure 7 All units in .

[0143] It should be noted that the processing unit in the embodiment of the present application may also be referred to as a processing module, and the transceiver unit may also be referred to as a transceiver module.

[0144] Figure 8 A software upgrade device 800 provided in an embodiment of the present application is shown, and the device may include a processor 810; the device may also include a transceiver 830, and the transceiver may include a transmitter and / or a receiver.

[0145] In some embodiments, the apparatus may further include a memory 820, and the processor 810, the transceiver 830 and the memory 820 are interconnected via an internal connection path. Figure 7 The related functions implemented by the processing unit 710 in the embodiment can be implemented by the processor 810, and the related functions implemented by the transceiver unit 720 can be implemented by the processor 810 controlling the transceiver 830.

[0146] In some embodiments, the processor 810 may include one or more processors, for example, one or more CPUs. When the processor is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0147] The transceiver 830 is used to send and receive data and / or signals, and receive data and / or signals. The transceiver may include a transmitter and a receiver, the transmitter is used to send data and / or signals, and the receiver is used to receive data and / or signals.

[0148] The memory 820 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable readonly memory (EPROM), and compact disc read-only memory (CD-ROM), and is used to store relevant instructions and data. The memory 820 can be a separate device or integrated in the processor 810.

[0149] Understandably, Figure 8 Only a simplified design of the software upgrade device is shown. In practical applications, the device may also include other necessary components, including but not limited to any number of transceivers, processors, controllers, memories, etc., and all devices that can implement the present application are within the protection scope of the present application.

[0150] like Fig. 9 As shown, the embodiment of the present application further provides a device 900, which may be a software upgrade device or a chip in a software upgrade device. The software upgrade device includes:

[0151] At least one input / output interface 910 and a logic circuit 920. The input / output interface 910 may be an input / output circuit, an input interface, an output interface, etc. The logic circuit 920 may be a signal processor, a chip, or other integrated circuit that can implement the method of the present application.

[0152] Among them, at least one input / output interface 910 is used for inputting or outputting signals or data. Among them, the logic circuit 920 is used for executing part or all of the steps of any method provided in the embodiments of the present application.

[0153] The embodiment of the present application also proposes a computer-readable storage medium, which stores one or more programs or instructions. When the program or instruction is executed on a computer, the computer executes the method of the above embodiment.

[0154] The embodiments of the present application further provide a computer program, which includes a program or instructions. When the computer program or instructions are executed by a computer, the computer can execute the corresponding process of the method of the above embodiment.

[0155] Those of ordinary skill in the art will appreciate that the units and steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0156] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0157] In the present application, "at least one" means one or more, and "plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0158] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

[0159] It should also be understood that the first, second and various numerical numbers involved in this document are only distinguished for the convenience of description and are not used to limit the scope of the embodiments of the present application.

[0160] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the unit is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0161] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0162] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0163] If the above functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method of each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0164] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for software upgrading, characterized in that: The method is applied to a centralized management network, and the method comprises: determining a loading strategy according to the centralized management network; performing software upgrade on the centralized management network according to the loading strategy; The loading strategy includes at least one of the following: Concurrent loading, lateral loading, and proxy loading.

2. The method according to claim 1, characterized in that: The lateral loading comprises: When the first network element and the second network element have the same device type, the first network element receives first type data from the second network element, and the first type data is used for software upgrade of the first network element and the second network element.

3. The method according to claim 1 or 2, characterized in that: The agent loading includes: When the device type of the third network element is the same as that of the fourth network element, the third network element sends second type data to the fourth network element through the fifth network element, the device type of the fifth network element is different from that of the third network element, and the second type data is used for software upgrade of the third network element and the fourth network element.

4. The method according to claim 3, characterized in that When the third network element sends the second type of data to the fourth network element through the fifth network element, the fourth network element occupies the concurrency of the fifth network element, and the concurrency of the fifth network element is used to represent the forwarding capability of the fifth network element.

5. The method according to any one of claims 1 to 4, characterized in that The concurrent loading includes: The centralized management network includes a first subnet and a second subnet, and network elements in the first subnet and network elements in the second subnet are loaded concurrently.

6. The method according to claim 5, characterized in that The centralized management network includes a first gateway and a second gateway, the first subnet includes the first gateway, and the second subnet includes the second gateway.

7. The method according to any one of claims 1 to 6, characterized in that The determining of the loading strategy according to the centralized management network includes: Establishing a software upgrade model for the centralized management network, wherein the software upgrade model includes at least two subnets; According to the information of the centralized management network, a minimum cost edge set set is determined through the software upgrade model, and the minimum cost edge set set is used to represent the loading strategy and the loading sequence, wherein the information of the centralized management network includes at least one of the following: The topological structure of the centralized management network, the link bandwidth of the centralized management network, and the forwarding capability of network elements in the centralized management network.

8. A software upgrade device, characterized in that: include: A processing unit, configured to determine a loading strategy according to the centralized management network; The processing unit is further used to perform software upgrade on the centralized management network according to the loading strategy; The loading strategy includes at least one of the following: Concurrent loading, lateral loading, and proxy loading.

9. The device according to claim 8, characterized in that The lateral loading comprises: When the first network element and the second network element have the same device type, the first network element receives first type data from the second network element, and the first type data is used for software upgrade of the first network element and the second network element.

10. The device according to claim 8 or 9, characterized in that The agent loading includes: When the device type of the third network element is the same as that of the fourth network element, the third network element sends second type data to the fourth network element through the fifth network element, the device type of the fifth network element is different from that of the third network element, and the second type data is used for software upgrade of the third network element and the fourth network element.

11. The device according to claim 3, characterized in that When the third network element sends the second type of data to the fourth network element through the fifth network element, the fourth network element occupies the concurrency of the fifth network element, and the concurrency of the fifth network element is used to represent the forwarding capability of the fifth network element.

12. The device according to any one of claims 8 to 11, characterized in that The concurrent loading includes: The centralized management network includes a first subnet and a second subnet, and network elements in the first subnet and network elements in the second subnet are loaded concurrently.

13. The device according to claim 12, characterized in that The centralized management network includes a first gateway and a second gateway, the first subnet includes the first gateway, and the second subnet includes the second gateway.

14. The device according to any one of claims 8 to 13, characterized in that The processing unit is specifically used to establish a software upgrade model for the centralized management network, wherein the software upgrade model includes at least two subnets; The processing unit is further configured to determine a minimum cost edge set set through the software upgrade model according to information of the centralized management network, wherein the minimum cost edge set set is used to represent the loading strategy and the loading sequence, wherein the information of the centralized management network includes at least one of the following: The topological structure of the centralized management network, the link bandwidth of the centralized management network, and the forwarding capability of network elements in the centralized management network.

15. A software upgrade device, characterized in that: include: A processor coupled to a memory, the memory being used to store a computer program, the processor being used to run the computer program so that the software upgrading device performs the method as claimed in any one of claims 1 to 7.

16. The device according to claim 15, characterized in that The apparatus further comprises one or more of the memory and a transceiver, wherein the transceiver is configured to receive a signal and / or transmit a signal.

17. A computer-readable storage medium, characterized in that: The computer-readable storage medium comprises a computer program or instructions, and when the computer program or instructions are run on a computer, the method according to any one of claims 1 to 7 is executed.

18. A computer program product, characterized in that The computer program product comprises a computer program or instructions, and when the computer program or instructions are run on a computer, the method as described in any one of 1 to 7 is executed.