Bandwidth adjustment method, storage medium and electronic device

Abstract

The embodiment of the invention provides a bandwidth adjustment method, a storage medium and an electronic device, and the method comprises the steps: obtaining a monitoring result which is used for carrying out the bandwidth adjustment of all network element nodes in a target network, and carrying out the state monitoring determination; and under the condition that the monitoring result indicates that the bandwidth adjustment fails, issuing a fallback command of bandwidth lossless fallback to all the network element nodes. Through application of the method and the device, the problem of service damage caused by execution of bandwidth forced configuration when the bandwidth adjustment exceeds the preset duration in related technologies is solved, and the effect of reducing the service damage caused by the bandwidth adjustment is further achieved.

Description

Technical Field

[0001] The present application relates to the field of SPN small-granularity access / aggregation products, and more specifically, to a bandwidth adjustment method, a storage medium, and an electronic device. Background Art

[0002] The high-value operator private lines and enterprise services carried by small-granular services have put forward high requirements for operation and maintenance. At present, small-granular services can support bandwidth lossless adjustment in complex scenarios such as OAM (operation administration and maintenance, configuration, management, maintenance, referred to as OAM) and protection. Lossless adjustment requires end-to-end control to issue adjustment commands and initiate adjustment hop by hop. After receiving the adjustment command, each network element waits for the adjustment signal of the previous network element. After receiving the signal, it tries to trigger lossless adjustment to the next network element repeatedly within a given time limit until the adjustment is successful. And if the end-to-end adjustment is completed within the timeout, lossless adjustment can be achieved. However, due to differences in the implementation mechanisms of different manufacturers and possible hardware defects in the exploration of emerging technologies, small-granular bandwidth lossless adjustment cannot be guaranteed to succeed in the existing network. When the above-mentioned bandwidth lossless adjustment is not completed due to timeout, the existing technical solution will immediately perform bandwidth forced configuration, which will cause service damage, so that the service will be damaged when the adjustment fails. Although the probability of this scenario is small, users originally expected bandwidth lossless, but it eventually led to service damage. For users who are more concerned about business stability and are not in a hurry to modify bandwidth, not giving them the final decision on whether the modification is lossy will damage the user experience and cause customer losses.

[0003] In the related art, there is no effective solution to the problem of service damage caused by immediately executing mandatory bandwidth configuration when bandwidth adjustment exceeds a preset time. Summary of the invention

[0004] The embodiments of the present application provide a bandwidth adjustment method, a storage medium, and an electronic device, so as to at least solve the problem of service damage caused by immediately executing bandwidth mandatory configuration when bandwidth adjustment exceeds a preset time in the related art.

[0005] According to one embodiment of the present application, a bandwidth adjustment method is provided, comprising: obtaining monitoring results, wherein the monitoring results are used to perform status monitoring and determination on bandwidth adjustment performed on all network element nodes in a target network; and when the monitoring results indicate that the bandwidth adjustment has failed, issuing a bandwidth lossless fallback command to all network element nodes.

[0006] According to another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when run.

[0007] According to another embodiment of the present application, an electronic device is provided, which may include a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0008] Through the above steps, the process of executing bandwidth adjustment of all network element nodes in the target network is monitored, and the monitoring result is obtained. The bandwidth adjustment result of the target network is determined by the monitoring result, and after the monitoring result indicates that the bandwidth adjustment fails, a fallback command for lossless bandwidth fallback is sent to all network element nodes in the target network, and then the bandwidth configuration of the network element node that fails to adjust the bandwidth is reset by using the fallback command, so that the network element node that fails to adjust the bandwidth can change the bandwidth configuration to the bandwidth configuration before the adjustment, which does not affect the subsequent configuration of the network element node, solves the problem of service damage caused by immediately executing bandwidth forced configuration when the bandwidth adjustment exceeds the preset time in the related art, and achieves the effect of avoiding service damage caused by bandwidth forced configuration through the fallback process, and the above fallback does not affect the continuity of the original service, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 It is a schematic diagram of a hardware structure block diagram of a mobile terminal according to a bandwidth adjustment method of an embodiment of the present application;

[0010] Figure 2 is a flow chart of a bandwidth adjustment method according to an embodiment of the present application;

[0011] Figure 3 is a structural schematic diagram of a bandwidth lossless adjustment system according to an embodiment of the present application;

[0012] Figure 4 It is a flow chart of a system for lossless adjustment of PE node bandwidth according to an embodiment of the present application;

[0013] Figure 5 It is a flow chart of a P node bandwidth lossless adjustment system according to an embodiment of the present application;

[0014] Figure 6 is a schematic diagram of lossless adjustment of end-to-end bandwidth increase according to an optional embodiment of the present application;

[0015] Figure 7is a schematic diagram of end-to-end bandwidth increase and lossless fallback according to an optional embodiment of the present application;

[0016] Figure 8 is a schematic diagram of an end-to-end bandwidth reduction lossless adjustment according to an optional embodiment of the present application;

[0017] Fig. 9 is a schematic diagram of end-to-end bandwidth reduction lossless fallback according to an optional embodiment of the present application;

[0018] Fig.10 is a schematic diagram of automatic diagnosis of link failure in bandwidth increase failure according to an optional embodiment of the present application;

[0019] Fig.11 is a schematic diagram of a lossless adjustment and rollback flow chart according to an optional embodiment of the present application;

[0020] Fig.12 is a structural diagram of a bandwidth adjustment system according to an embodiment of the present application;

[0021] Fig.13 is a block diagram of a computer system structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0022] The present application will be described in detail below with reference to the accompanying drawings and in combination with embodiments. It should be noted that the embodiments and features in the embodiments of the present application can be combined with each other without conflict.

[0023] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0024] Example 1

[0025] The method embodiment provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, Figure 1 1 is a hardware structure block diagram of a mobile terminal according to a bandwidth adjustment method of an embodiment of the present application. Figure 1 As shown, the mobile terminal 10 may include one or more (only one is shown in the figure) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. It can be understood by those skilled in the art that Figure 1 The structure shown is for illustration only and does not limit the structure of the above electronic device. Figure 1More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0026] The memory 104 can be used to store software programs and modules of application software, such as program instructions / modules corresponding to the bandwidth adjustment method in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implementing the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the mobile terminal 10 via a network. Examples of the above-mentioned network may include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0027] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the mobile terminal 10. In one example, the transmission device 106 may include a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0028] In this embodiment, a bandwidth adjustment method is provided. Figure 2 is a flow chart of a bandwidth adjustment method according to an embodiment of the present application, such as Figure 2 As shown, the process may include, but is not limited to, the following steps:

[0029] Step S202, obtaining monitoring results, wherein the monitoring results are used to monitor and determine the status of bandwidth adjustment performed on all network element nodes in the target network;

[0030] As an optional implementation, before status monitoring is performed on all network element nodes in the target network, the adjustment content obtained by all network element nodes needs to be determined, and the above adjustment content may be configuration information for lossless bandwidth increase or lossless bandwidth reduction of the current network element;

[0031] Step S204: When the monitoring result indicates that the bandwidth adjustment fails, a bandwidth lossless fallback command is issued to all network element nodes.

[0032] Through the above steps, the process of executing bandwidth adjustment of all network element nodes in the target network is monitored, and the monitoring result is obtained. The bandwidth adjustment result of the target network is determined by the monitoring result, and after the monitoring result indicates that the bandwidth adjustment fails, a fallback command for lossless bandwidth fallback is sent to all network element nodes in the target network, and then the bandwidth configuration of the network element node that fails to adjust the bandwidth is reset by using the fallback command, so that the network element node that fails to adjust the bandwidth can change the bandwidth configuration to the bandwidth configuration before the adjustment, which does not affect the subsequent configuration of the network element node, solves the problem of service damage caused by immediately executing bandwidth forced configuration when the bandwidth adjustment exceeds the preset time in the related art, and achieves the effect of avoiding service damage caused by bandwidth forced configuration through the fallback process, and the above fallback does not affect the continuity of the original service, thereby improving the user experience.

[0033] In an exemplary embodiment, the above method can be applied in a bandwidth lossless adjustment system or other systems having similar functions to the bandwidth lossless adjustment system, wherein the above bandwidth lossless adjustment system includes: management and control, a lossless adjustment control module, and a service forwarding entity.

[0034] The lossless adjustment control module at least includes a configuration management unit and a status monitoring unit.

[0035] Control is responsible for issuing the configuration bandwidth information of the target network between end-to-end.

[0036] Each network element corresponds to a lossless adjustment control module. The configuration management unit mainly temporarily stores the configuration bandwidth information sent by the management to the lossless adjustment control module, and sends the configuration bandwidth information to the business forwarding entity for execution of the adjustment operation. After the business forwarding entity completes the protocol interaction and determines that the lossless adjustment is successful, the configuration bandwidth information is solidified as the actual application bandwidth of the network element corresponding to the current lossless adjustment control module.

[0037] The status monitoring unit is mainly used to complete the protocol interaction between network elements and report the adjustment results in real time, and then trigger the lossless fallback process of bandwidth adjustment in the event of adjustment failure.

[0038] The service forwarding entity is responsible for the hop-by-hop protocol overhead interaction between different network elements in the target network.

[0039] In an exemplary embodiment, obtaining the monitoring result includes: in a case where it is determined that bandwidth adjustment failure of at least one network element node among all the network element nodes occurs, determining that the monitoring result is bandwidth adjustment failure of the target network.

[0040] That is to say, the adjustment result of each network element node in the target network after performing lossless bandwidth adjustment is monitored to determine the final adjustment result of the target network between end and end. No matter whether the target network element node performs lossless bandwidth increase adjustment or lossless bandwidth decrease adjustment, as long as one network element node fails to adjust, the bandwidth modification of the target network fails.

[0041] Optionally, in actual scenarios, when the SPN (Slicing Packet Network, referred to as SPN) network performs lossless adjustment of small-granular bandwidth increase, the control will send a bandwidth lossless increase command to all nodes on the forwarding path, and the tail node will initiate the adjustment, inserting the S / CR / CA / C bits in the network element overhead of the optical fiber connection, and completing the protocol interaction with the upstream node in turn, so as to achieve end-to-end segment-by-segment adjustment from downstream to upstream. When the small-granular bandwidth is reduced and lossless adjustment is performed, the adjustment is initiated by the head node, and the CR / CA / C bits are inserted in the network element overhead of the optical fiber connection, and the protocol interaction is completed with the downstream node in turn, so as to achieve end-to-end segment-by-segment adjustment from upstream to downstream.

[0042] In an exemplary embodiment, the method further includes: determining all network element nodes in the target network where bandwidth adjustment fails based on the reported information, wherein the reported information is used to indicate information fed back by all network element nodes after bandwidth adjustment is performed; acquiring target data corresponding to all network element nodes where bandwidth adjustment fails, so as to determine the failure cause corresponding to the bandwidth adjustment failure based on the target data, wherein the target data includes: the adjustment direction of the link where each network element node where bandwidth adjustment fails is located, the interaction information between each network element node where bandwidth adjustment fails and the adjacent network element on the same link, and the bandwidth adjustment type corresponding to each network element node where bandwidth adjustment fails, wherein the bandwidth adjustment type includes at least one of the following: lossless adjustment with bandwidth reduction and lossless adjustment with bandwidth increase;

[0043] That is, when it is determined that the bandwidth adjustment of the target network between the end and the end fails, the network nodes in the target network that have not been adjusted successfully are determined through the reporting information reported by each network element node after completing the protocol interaction, and then the target data corresponding to the target network element node where the bandwidth adjustment failed is obtained. For example, assuming that the target network includes N network element nodes, and the optical fiber link is broken between the N-1th node and the N-2th node, the PE 1、 PE n Corresponding to the network element nodes of the service provider edge equipment, P2 to P n-1 The network element node corresponding to the backbone equipment of the service provider is to adjust the bandwidth of the current target network to increase the bandwidth, and the adjustment direction is from PE1 to PE n When; in P n-1 The network element node receives Pn-2 The network element node sends the S code block, but does not receive the CA code block, so P n-1 The network element node can only determine that the link is normal when the S code block is sent, but cannot determine whether its own CR transmission fails or the peer CA reply fails. n-2 The network element node did not receive the P n-1 Any code block sent by the network element node cannot confirm whether the link is abnormal or the other end has not issued any bandwidth adjustment. However, the control can infer that the adjustment commands have been issued successfully by integrating the code block sending and receiving information of the two network element nodes. n-1 To P n-2 The link in this direction has a fiber break.

[0044] In summary, through the above embodiments, the target data corresponding to the acquired network element nodes can be used to clearly determine the adjustment status between adjacent network element nodes on the same adjustment path. By judging the adjustment status, the cause of adjustment failure in the target network can be determined, thereby improving the accuracy of adjustment failure monitoring.

[0045] In an exemplary embodiment, when the monitoring result indicates that the bandwidth adjustment fails, a fallback command for lossless bandwidth fallback is issued to all network element nodes, including: determining the bandwidth adjustment type corresponding to the monitoring result; when the bandwidth adjustment type is lossless adjustment of bandwidth increase, identifying the tail node among all network element nodes, and issuing the fallback command for lossless bandwidth fallback hop by hop from the tail node to all network element nodes; when the bandwidth adjustment type is lossless adjustment of bandwidth decrease, identifying the head node among all network element nodes, and issuing the fallback command for lossless bandwidth fallback hop by hop from the head node to all network element nodes.

[0046] For example, when the SPN network performs small-granular bandwidth increase lossless adjustment, the control will send a bandwidth lossless increase command to all nodes on the forwarding path, and the tail node will initiate the adjustment. By inserting S / CR / CA / C bits in the network element overhead of the optical fiber connection, the protocol interaction is completed with the upstream node in turn. When it is determined that the current bandwidth increase lossless adjustment has failed, the control will send a lossless fallback command to all network elements. At this time, it is necessary to perform a reverse bandwidth lossless adjustment operation on the part where the lossless adjustment is successful, that is, the bandwidth is reduced, and the last hop network element node (that is, the previous tail node) of the last successful adjustment is used as the first node of the current adjustment to initiate the adjustment. By inserting CR / CA / C bits in the network element overhead of the optical fiber connection, the protocol interaction is completed with the downstream node in turn, thereby realizing end-to-end segment-by-segment fallback from upstream to downstream.

[0047] In an exemplary embodiment, the method further comprises:

[0048] Determine an adjustment time for each of the network element nodes to execute the rollback command;

[0049] When the adjustment time is longer than the preset detection time, the rollback command is repeatedly sent to the current network element node.

[0050] In an exemplary embodiment, since the lossless adjustment between end-to-end requires the control of end-to-end adjustment commands and hop-by-hop adjustment, each network element waits for the adjustment signal of the previous network element after receiving the adjustment command, and after receiving the signal, tries to repeatedly trigger the lossless adjustment to the next network element within a given time limit until the adjustment is successful. In addition, since the rollback command actually triggers the cancellation of bandwidth adjustment for each network element node that has performed bandwidth adjustment in turn, the cancellation is essentially to perform the same size of lossless bandwidth reduction on the network element node that performs bandwidth lossless increase; or to perform the same size of lossless bandwidth increase on the network element node that performs bandwidth lossless reduction. Therefore, in order to ensure the effective execution of the rollback command, after the rollback command is issued, the adjustment time of the rollback command executed on the network element node is counted within the preset detection time. When the adjustment time is longer than the preset detection time, it means that the lossless command has not been successfully executed, and the lossless command needs to be repeatedly issued to the current network element node whose adjustment time is longer than the preset detection time to ensure that all network element nodes in the target network complete the lossless return of bandwidth.

[0051] In an exemplary embodiment, the above method also includes: determining the preset maximum number of repeated backoff times for the target object, and counting the number of times the backoff command corresponding to the current network element node is issued; when the number of issuances is greater than the maximum number of repeated backoff times, forcibly configuring the current network element node, wherein the forced configuration is used to indicate that the bandwidth of the current network element node is adjusted to a preset fixed bandwidth.

[0052] In an exemplary embodiment, when the number of rollback failures reaches the maximum repeated rollback limit M set by the user, the device will immediately report success and force configuration. In particular, if the user prohibits repeated rollback, he only needs to set M to 0. When forced configuration, the device will report success, so that the rollback will not be triggered repeatedly. The status monitoring will also be restored to a successful state so as not to affect the execution of the next user configuration adjustment command, where M is an integer.

[0053] In summary, in order to avoid the target network being unable to receive other adjustment commands due to repeated issuance of rollback commands, the issuance of rollback commands is managed by setting the maximum number of repeated rollback times for the rollback command. When the rollback cannot be completed effectively, forced configuration is used to ensure that the configuration in the target network is valid so as not to affect the execution of the next user configuration adjustment command.

[0054] In an exemplary embodiment, the above method also includes: when the number of issuances is less than or equal to a preset maximum number of repeated fallbacks, obtaining the execution result of the most recent repeatedly issued fallback command received by the current network element node; when it is determined that the execution result indicates that the fallback of the current network element node has failed, repeatedly triggering the issuance of the fallback command; when it is determined that the execution result indicates that the fallback of the current network element node has been successful, ending the triggering of the issuance of the fallback command.

[0055] After the rollback command is repeatedly issued, the execution result of each repeated rollback command is monitored in real time to ensure that after the rollback is successfully executed, the issuance of the rollback command is quickly terminated to avoid the impact of the rollback command on subsequent adjustments.

[0056] In an exemplary embodiment, after issuing a fallback command for lossless bandwidth fallback to all the network element nodes, the method further includes: obtaining a first bandwidth adjustment signal corresponding to each of the network element nodes among all the network element nodes before issuing the fallback command; determining a second bandwidth adjustment signal corresponding to the first bandwidth adjustment signal, wherein the second bandwidth adjustment signal is determined by reversely adjusting the current bandwidth adjustment direction of the first bandwidth adjustment signal; and forwarding the second bandwidth adjustment signal from a source node to all network element nodes hop by hop, wherein the source node is a head node or a tail node.

[0057] In an exemplary embodiment, when the bandwidth adjustment previously performed in the target network is a lossless adjustment of increasing the bandwidth, the fallback command corresponds to a lossless adjustment of decreasing the bandwidth in the opposite direction of the lossless adjustment of increasing the bandwidth; and the starting adjustment point of the lossless fallback adjustment of the lossless adjustment of increasing the bandwidth is the target network element node of the last hop of the last successful adjustment. The target network element node is used as the initial node to initiate the adjustment, and the CR / CA / C bits are respectively inserted in the network element overhead of the optical fiber connection, and the protocol interaction is completed with the downstream nodes in turn, thereby realizing end-to-end segment-by-segment fallback from upstream to downstream.

[0058] Optionally, when the bandwidth adjustment previously performed in the target network is a lossless adjustment of reducing the bandwidth, the fallback command corresponds to a lossless adjustment of increasing the bandwidth in the opposite direction of the lossless adjustment of reducing the bandwidth; and the starting adjustment point of the lossless fallback adjustment of the lossless adjustment of reducing the bandwidth is the target network element node of the last hop of the last successful adjustment. The target network element node is used as the initial node to initiate the adjustment, and the CR / CA / C bits are respectively inserted in the network element overhead of the optical fiber docking, and the protocol interaction is completed with the downstream nodes in turn, thereby realizing end-to-end and segment-by-segment adjustment from upstream to downstream.

[0059] It should be noted that the initial node for the reverse adjustment of the above-mentioned bandwidth increase lossless adjustment is the tail node of the previous adjustment; the initial node for the reverse adjustment of the above-mentioned bandwidth decrease lossless adjustment is the head node of the previous adjustment; the above is for determining the adjustment direction as a fixed direction.

[0060] In summary, the process of increasing or decreasing the service bandwidth end-to-end between different network element nodes is monitored through the lossless adjustment control module. When a link adjustment fails during the end-to-end adjustment process, the bandwidth lossless fallback operation is triggered, that is, the lossless fallback mechanism is executed after the lossless adjustment fails. The end-to-end fallback success rate is improved by customizing the lossless fallback strategy, and the service damage is minimized. The problem of service damage caused by forced bandwidth configuration when the bandwidth adjustment exceeds the preset time in the related technology is solved, thereby achieving the effect that the fallback process does not affect the continuity of the original service, thereby improving the user experience.

[0061] Obviously, the embodiments described above are only some embodiments of the present application, not all embodiments. In order to better understand the above method, the above process is described below in conjunction with the embodiments, but it is not intended to limit the technical solutions of the embodiments of the present application, specifically:

[0062] In an exemplary embodiment, Figure 3 It is a structural diagram of a bandwidth lossless adjustment system according to an embodiment of the present application. The above-mentioned bandwidth lossless adjustment system consists of three parts, namely, control 32, lossless adjustment control module 34, and service forwarding entity 36. Among them, control 32 is responsible for end-to-end configuration delivery. The lossless adjustment control module 36 of each network element is used to save the received configuration information, determine whether it meets the conditions for lossless adjustment, and deliver the configuration to the service forwarding entity 36. The service forwarding entity 36 of each network element is responsible for hop-by-hop protocol overhead interaction.

[0063] In an exemplary embodiment, a small-granular bandwidth lossless fallback system is proposed. Specifically, based on the above-mentioned bandwidth lossless adjustment system, an additional state monitoring unit is required in the lossless adjustment control module in the bandwidth lossless adjustment system, a set of adjustment result query and reporting interfaces are added between the control and the lossless adjustment control module, and a state reporting interface is added to the service forwarding entity. The function of triggering the network element bandwidth fallback when the adjustment fails is realized through the above-mentioned newly added units and interfaces.

[0064] It should be noted that lossless bandwidth adjustment refers to a method of increasing or decreasing service bandwidth end-to-end without damaging small-granular services, and lossless bandwidth fallback refers to the process of reversely performing lossless bandwidth adjustment when a link adjustment fails during the end-to-end adjustment process, thereby avoiding service damage. The above method can enhance the success rate of lossless bandwidth adjustment during small-granular service maintenance, and even if bandwidth adjustment fails, lossless fallback can be achieved without damaging the connected part of the service.

[0065] In an exemplary embodiment, for a PE (Provider Edge, service provider edge device, referred to as PE) node, the service has only one forwarding direction, so only one configuration message will be received for one adjustment, such as Figure 4 As shown, Figure 4 The following is a flow chart of a PE node bandwidth lossless adjustment system according to an embodiment of the present application. When the above bandwidth lossless fallback system is running, the following steps are performed:

[0066] Step S401: When the management and control configures bandwidth adjustment, the original processing logic remains unchanged, and the management and control sends bandwidth modification configuration to the lossless adjustment control module as needed;

[0067] Step S402: The configuration management unit in the lossless adjustment control module temporarily stores the bandwidth modification configuration and sends the bandwidth modification configuration to the service forwarding entity;

[0068] Step S403, the control sends a new blocking adjustment status query command to the lossless adjustment control module; the adjustment status query command does not involve configuration to the service forwarding entity, but only queries the adjustment result of the execution of the configuration command in the status monitoring unit. In actual application, after the adjustment status query command is sent, the PE node lossless adjustment control module does not respond immediately, nor does it allow other configurations to be sent, so that the network element can only process one adjustment at a time. It should be noted that the above steps S402 and S403 actually support sending in any timing.

[0069] Step S404: The lossless adjustment control module waits for the service forwarding entity to complete the protocol interaction between network elements and report the adjustment result.

[0070] Step S405: The lossless adjustment control module returns the reported adjustment result to the management and control in the form of a message, and then releases the configuration blocking state, and can continue to adjust or send a rollback.

[0071] When the adjustment fails, the lossless adjustment control module not only reports the failure result and the network element overhead receiving and sending status for management and control to analyze the cause of the failure, but also caches the adjustment failure status information in the status monitoring unit.

[0072] In an exemplary embodiment, when the fallback message sent by the control is exactly the same as the adjustment message, the lossless adjustment control module will determine whether the control message belongs to a fallback and which direction needs to be fellback based on the last adjustment result information cached in the status monitoring unit, thereby determining the actual operation of the service forwarding entity, and finally updating the status monitoring according to the fallback result. If it is monitored that the adjustment is not successful, the configuration management module will not solidify the configuration temporarily stored in this adjustment, because when the adjustment fails, the configuration is not fully effective in the service forwarding entity, and is inconsistent with the actual configuration of the service forwarding entity. While waiting for the control to send an end-to-end fallback command, the lossless adjustment control module of the network element only needs to restore the previous configuration and re-send the reverse configuration to trigger the reverse bandwidth modification of the service forwarding entity to achieve consistency between the upper and lower parts. If the adjustment is successful, it can be considered that the configuration temporarily stored in the configuration management module has taken effect in the service forwarding entity, and the upper and lower configurations are consistent. The configuration cache can be directly solidified to become the real configuration.

[0073] It is understandable that when the service forwarding entity reports the adjustment successfully, the above bandwidth modification configuration is allowed to take effect and transferred to the formal configuration to realize the configuration solidification process of the successful adjustment. If the adjustment fails, the temporary bandwidth modification configuration will not be converted to the formal configuration. After waiting for the rollback command to be issued, the configuration management unit will directly issue a reverse bandwidth adjustment configuration and delete the temporary storage, so as to achieve the consistency of the upper and lower configurations. If the adjustment fails, there is no need to solidify, and the configuration will eventually be rolled back.

[0074] In an exemplary embodiment, for a P (Provider, service provider backbone equipment, referred to as P) node, the service has two forwarding directions, so one adjustment will receive two pieces of configuration information, such as Figure 5 As shown, Figure 5 This is a flow chart of a P node bandwidth lossless adjustment system according to an embodiment of the present application. When the bandwidth lossless fallback system is running at the P node, the following steps are performed:

[0075] Step S501: When the control configures bandwidth adjustment, the original processing logic remains unchanged, and the control sends the bandwidth modification configuration of the first direction to the lossless adjustment control module as needed;

[0076] Step S502: The configuration management unit in the lossless adjustment control module temporarily stores the bandwidth modification configuration and sends the bandwidth modification configuration to the service forwarding entity;

[0077] Step S503: The control sends a first query command to the lossless adjustment control module;

[0078] Step S504: the lossless adjustment control module immediately reports the adjustment result of the execution of the first configuration command in the status monitoring unit to the management and control;

[0079] It should be noted that after the first query command is issued, the P node should return immediately to avoid configuration blocking, rather than waiting for the actual adjustment result of the service forwarding entity. Otherwise, blocking the issuance of the second configuration command will cause the adjustment timeout in the second direction.

[0080] Step S505: The lossless adjustment control module waits for the service forwarding entity to complete the protocol interaction between network elements and report the first adjustment result, and does not directly feed back the first adjustment result to the management and control, but only saves it in the status monitoring module.

[0081] Step S506: The control sends a second query command to the lossless adjustment control module;

[0082] Step S507: The control sends the bandwidth modification configuration of the second direction to the lossless adjustment control module as needed; that is, for the P node, the bandwidth modification configurations sent in two directions together constitute one adjustment.

[0083] Step S508: The lossless adjustment control module sends the second configuration command to the service forwarding entity to instruct the service forwarding entity to complete the two-way protocol interaction.

[0084] Step S509: The lossless adjustment control module waits for the service forwarding entity to complete the protocol interaction between network elements and report the second adjustment result.

[0085] Step S510: The lossless adjustment control module returns the reported adjustment result to the management and control in the form of a message, wherein the second adjustment result report will integrate the results of the two protocol interactions of the first adjustment result and the second adjustment result.

[0086] To facilitate the understanding of the technical solution provided by the present application, a detailed explanation will be given below in combination with embodiments of specific scenarios.

[0087] When the SPN (Slicing Packet Network, referred to as SPN) network performs lossless adjustment of small-granular bandwidth increase, the control will send a lossless bandwidth increase command to all nodes on the forwarding path, and the tail node will initiate the adjustment, inserting the S / CR / CA / C bits in the network element overhead of the optical fiber connection, and completing the protocol interaction with the upstream node in turn, so as to achieve end-to-end segment-by-segment adjustment from downstream to upstream. When the small-granular bandwidth is reduced and lossless, the adjustment is initiated by the head node, inserting the CR / CA / C bits in the network element overhead of the optical fiber connection, and completing the protocol interaction with the downstream node in turn, so as to achieve end-to-end segment-by-segment adjustment from upstream to downstream.

[0088] In an exemplary embodiment, when the bandwidth increases, a link in the middle may have abnormal interaction or fiber breakage, such as Figure 6 shown. Figure 6 is a schematic diagram of an end-to-end bandwidth increase lossless adjustment according to an optional embodiment of the present application; n To P n-1 Direction adjustment is successful, PE n The network element will report the adjustment success to the control. n-1 To P n-2 Direction adjustment failed, P n-1 Based on the adjustment results in both directions, the adjustment failure is reported and the service is recorded as being in the adjustment failure state. n-2 Since the network elements in between have not received the adjustment signal from the downstream, they will eventually time out and report failure. Only when each network element reports the adjustment successfully, the control will consider that the end-to-end bandwidth adjustment is successful.

[0089] In an exemplary embodiment, when the end-to-end bandwidth increase fails, the control will issue a lossless fallback command to all network elements, such as Figure 7 shown. Figure 7 is a schematic diagram of end-to-end bandwidth increase and lossless fallback according to an optional embodiment of the present application;

[0090] For the parts that are successfully adjusted, such as P n-1 To PE n The device side will perform a reverse bandwidth lossless adjustment operation, that is, the bandwidth is reduced. n-1 As the first node to initiate the adjustment, the CR / CA / C bits are inserted into the network element overhead of the fiber connection, and the protocol interaction is completed with the downstream nodes in turn, so as to achieve end-to-end segment-by-segment fallback from upstream to downstream. n-2 -P n-1 In the meantime, since the adjustment on the device side was not successful in the first place, there is no need to roll back.

[0091] When a new adjustment command is actually issued, the device side determines whether the issued command is a configuration command or a rollback command by querying whether the service is in the adjustment failure state. If it is in the adjustment failure state, it is considered that the issued command is a rollback command. You only need to restore the underlying configuration to be consistent with the user configuration, and then restore the adjustment state of the service. If it is in the adjustment success state, it is considered that the issued command is an adjustment command.

[0092] In an exemplary embodiment, when the bandwidth is reduced, a link in the middle is abnormal or a fiber is broken, such as Figure 8 shown. Figure 8This is a schematic diagram of an end-to-end bandwidth reduction lossless adjustment according to an optional embodiment of the present application. The bandwidth reduction scenario is similar to the bandwidth increase failure fallback scenario. The adjustment is initiated by the head node, and the CR / CA / C bits are respectively inserted in the network element overhead of the optical fiber docking, and the protocol interaction is completed with the downstream node in turn, thereby realizing end-to-end segment-by-segment adjustment from upstream to downstream. n-1 To P n-2 Interaction failure or disconnection will lead to P n-2 , P n-1 PE n The node reported that the adjustment failed, and ultimately the management and control considered that the end-to-end adjustment failed.

[0093] When the end-to-end bandwidth reduction fails, the control will issue a lossless fallback command to all network elements, such as Fig. 9 shown. Fig. 9 is a schematic diagram of end-to-end bandwidth reduction lossless fallback according to an optional embodiment of the present application, P n-2 The processing flow to PE1 is similar to that of bandwidth increase. By inserting S / CR / CA / C bits in the network element overhead of the optical fiber connection, the protocol interaction is completed with the upstream node in turn, so as to achieve end-to-end segment-by-segment rollback from downstream to upstream. After judging that it is a rollback command according to the service adjustment status, P n-2 , P n-1 PE n Simply restore the underlying configuration to be consistent with the user configuration, and then restore the adjustment status of this service.

[0094] It should be noted that in the actual adjustment process, the end-to-end bandwidth lossless adjustment is performed bidirectionally. When the bandwidth adjustment between two network elements fails, the device side can only perceive that the adjustment failure has occurred between itself and its neighbor, but it cannot determine whether the adjustment failure is due to the failure of the docking device to adjust synchronously or the link is abnormal, nor can it know which direction the link is abnormal. After the device that failed to adjust extracts the overhead interaction information and reports it to the control, the control can integrate the overhead transmission and reception information of the two devices to achieve intelligent and accurate diagnosis of the cause of the failure, and clarify which of the following situations is the cause of the adjustment failure: the peer device control link is broken, and the peer network element has not issued the adjustment; the fiber is broken in the sending direction of the network element; the fiber is broken in the receiving direction of the network element; the link is broken in both directions.

[0095] In an exemplary embodiment, according to Figure 6 As shown in the process of bandwidth adjustment and increase, it can be seen that during the increase process, S / CR / CA / C code blocks will be initiated in both directions, and link abnormalities will affect the overhead interaction in both directions at the same time. n-1 To P n-2 For example, if the optical fiber in the direction is broken, the device side P n-1 Receive P n-2S code blocks are sent, but CA code blocks are not received, so P n-1 It can only be determined that the link is normal when the S code block is sent, but it cannot be determined whether the subsequent CR sending of the device fails or the CA reply of the peer fails. n-2 Not received P n-1 Any code blocks sent cannot confirm whether the link is abnormal or the other end has not issued any bandwidth adjustment. However, the control can infer that the adjustment commands have been issued successfully by integrating the code block sending and receiving information of the two devices. n-1 To P n-2 The link in this direction has a fiber break, such as Fig.10 As shown, Fig.10 It is a schematic diagram of automatic diagnosis of link fault due to bandwidth increase failure according to an optional embodiment of the present application.

[0096] It should be noted that the bandwidth reduction scenario is similar to this. If only CR is received in one direction and no code blocks are received in the other direction, it can be considered that a single fiber is broken in the direction where no code blocks are received. If no code blocks are received in both directions, then both fibers are broken.

[0097] In an exemplary embodiment, Fig.11 It is a schematic diagram of a lossless adjustment and rollback flow chart according to an optional embodiment of the present application, which specifically includes the following steps:

[0098] Step S1102: Send adjustment or rollback; Fig.11 As shown in the figure, there are four possibilities for starting the lossless bandwidth adjustment and lossless fallback system: the user configures the bandwidth adjustment command, the adjustment of the network element is successful, but the end-to-end adjustment fails (other network elements fail), resulting in the control issuing the adjustment. In these two scenarios, the status monitoring in the lossless adjustment control module is in the success state, and the device will execute the lossless adjustment process. The adjustment failure of the network element causes the control to issue a fallback command, and the fallback failure of the network element repeatedly triggers the fallback. In these two scenarios, the status monitoring is in the failure state, and the device will execute the lossless fallback process. In fact, there is no difference in the configuration messages issued by the control in the four scenarios, but there is a difference in the status monitoring, so the setting execution process is slightly different.

[0099] Step S1104: Determine whether it is a rollback: the network element determines whether the last adjustment failed according to the status monitoring information in the lossless adjustment control module, and thus determines whether this adjustment is a rollback. If it failed last time, this time is a rollback; if it succeeded last time, this time is a configuration.

[0100] Step S1106, whether it is timed out: After the service forwarding entity starts the protocol interaction, the lossless adjustment control module will start the timer to regularly detect the adjustment success signal and alarm status. If the adjustment success signal is detected within the timeout period, it is considered that there is no timeout. If the adjustment success signal is not detected within the timeout period but the overhead S / CR / CA / C and other field alarms are not received, the adjustment will be triggered repeatedly. If the adjustment success signal is not detected within the timeout period, it is considered that the adjustment or fallback has timed out.

[0101] Step S1108: Whether the rollback policy is satisfied; the maximum number of repeated rollbacks N can be set according to user preferences. When N is 0, it means that rollback is only allowed after adjustment failure, but re-triggering of rollback is not allowed when rollback fails. The device will immediately report the failure and force configuration. When N is greater than 0, it means that not only can rollback be allowed after adjustment failure, but also up to N consecutive re-triggering of rollback is supported after rollback failure.

[0102] Step S1110, lossless rollback: During the lossless rollback, the table items that were successfully configured last time can be reversely adjusted in a lossless manner. For the table items that failed to be configured last time, since they have been restored in the preprocessing, they do not need to be processed again.

[0103] Step S1112, lossless adjustment: According to the bandwidth adjustment direction, hop-by-hop bandwidth lossless adjustment is initiated between service forwarding entities, thereby finally achieving end-to-end bandwidth lossless adjustment.

[0104] Step S1114, pre-processing before rollback; this processing will be executed only after the lossless adjustment times out. For the table items that failed to be configured this time, the configuration needs to be restored to the original configuration. For example, if the original bandwidth is 10M, the user sends a command to adjust it to 30M. After the network element times out in the lossless adjustment, the rollback pre-processing needs to roll back the configuration to 10M. When the lossless rollback command is subsequently issued, no further processing is required for the table items that failed to be adjusted. For the table items that were successfully adjusted, they are processed during the rollback process.

[0105] Step S1116, reporting success: When the lossless adjustment is successful, the rollback is successful, or the forced configuration is successful, the network element adjustment success will be reported. At the same time, the status monitoring in the lossless adjustment control module is restored to a successful state.

[0106] Step S1118, report failure; when the lossless adjustment of the service forwarding entity fails or meets the repeated fallback strategy, the lossless adjustment failure of the network element will be reported, and the failure will be recorded in the status monitoring module. It should be noted that the first query of the P node will be returned immediately, and only the adjustment failure status of one direction will be recorded here. The comprehensive adjustment result of both directions will not be returned until the adjustment of the second direction is completed. If any direction of the P device is not adjusted successfully, it is considered that the current network element adjustment has failed, and a fallback will be triggered. The failure information will include the code block information actually received by the network element for management and control to analyze the cause of the link abnormality.

[0107] Step S1120, forced configuration; when the number of rollback failures reaches the maximum repeated rollback limit N set by the user, the device will immediately report success and force configuration. In particular, if the user prohibits repeated rollback, he only needs to set N to 0. When forced configuration, the device will report success, so that the rollback will not be triggered repeatedly. The status monitoring will also be restored to a successful state, so as not to affect the execution of the next user configuration adjustment command.

[0108] Step S1122, whether the end-to-end adjustment is successful; after each network element reports its own adjustment results to the control, all network elements are adjusted successfully or the forced configuration is successful, the control will consider the end-to-end success and the process ends. Otherwise, the end-to-end adjustment will be considered to have failed and the end-to-end rollback will be triggered. Due to the different status monitoring saved by each network element itself, the network element that successfully adjusted last time was passively triggered to rollback, and it cannot perceive that this is a rollback operation, and it will regard this rollback as a new adjustment process. The network element that failed to adjust or rollback last time actively triggered the rollback, and can perceive that this is a rollback, and will trigger the rollback through the "report failure to trigger rollback" or "satisfy the re-rollback strategy" process.

[0109] It should be noted that the above implementation supports the configuration of small-granularity oam and small-granularity protection scenarios, and will not cause abnormal alarms when adjusting and rolling back bandwidth, which is convenient for the management and maintenance of small-granularity services. It can also be extended to bandwidth modification of services such as FlexE.

[0110] In summary, the above implementation methods have enhanced the stability of existing high-value private line small-granularity services. When the link is normal, if the bandwidth lossless adjustment fails, it can also achieve non-packet loss fallback configuration, which greatly enhances the security and convenience of operation and maintenance operations. Operation and maintenance personnel can modify the bandwidth at any time with one click. Even if a link failure occurs during adjustment, the connected network segments can still achieve lossless fallback, which can minimize the damage. When the adjustment fails, the management and control can automatically complete the end-to-end link fault diagnosis and analysis. The incremental implementation scheme of the newly added query / response command and status monitoring unit does not need to change the original complex configuration interface, which is convenient for horizontal promotion to similar business scenarios.

[0111] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory / random access memory (ROM / RAM), a disk, or an optical disk), and may include a number of instructions to enable a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0112] Example 2

[0113] In this embodiment, a bandwidth adjustment system is also provided, which is used to implement the above embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0114] Fig.12 is a schematic diagram of the structure of a bandwidth adjustment system according to an embodiment of the present application, such as Fig.12 As shown, the system may include:

[0115] The lossless adjustment control module 1202 is used to obtain monitoring results, wherein the monitoring results are used to monitor and determine the status of bandwidth adjustment performed on all network element nodes in the target network;

[0116] Management and control 1204 is used to send a bandwidth lossless fallback command to all network element nodes when the monitoring result indicates that the bandwidth adjustment fails.

[0117] Through the above system, the process of executing bandwidth adjustment of all network element nodes in the target network is monitored, and the monitoring result is obtained. The bandwidth adjustment result of the target network is determined by the monitoring result, and after the monitoring result indicates that the bandwidth adjustment fails, a fallback command for lossless bandwidth fallback is sent to all network element nodes in the target network, and then the bandwidth configuration of the network element node that fails to adjust the bandwidth is reset by using the fallback command, so that the network element node that fails to adjust the bandwidth can change the bandwidth configuration to the bandwidth configuration before the adjustment, which does not affect the subsequent configuration of the network element node, solves the problem of service damage caused by immediately executing bandwidth forced configuration when the bandwidth adjustment exceeds the preset time in the related art, and achieves the effect of avoiding service damage caused by bandwidth forced configuration through the fallback process, and the above fallback does not affect the continuity of the original service, thereby improving the user experience.

[0118] In an exemplary embodiment, the lossless adjustment control module 1202 is further configured to determine that the monitoring result is a bandwidth adjustment failure of the target network when it is determined that bandwidth adjustment failure of at least one network element node occurs in all the network element nodes.

[0119] That is to say, the adjustment result of each network element node in the target network after performing lossless bandwidth adjustment is monitored to determine the final adjustment result of the target network between end and end. No matter whether the target network element node performs lossless bandwidth increase adjustment or lossless bandwidth decrease adjustment, as long as one network element node fails to adjust, the bandwidth modification of the target network fails.

[0120] Optionally, in actual scenarios, when the SPN (Slicing Packet Network, referred to as SPN) network performs lossless adjustment of small-granular bandwidth increase, the control will send a bandwidth lossless increase command to all nodes on the forwarding path, and the tail node will initiate the adjustment, inserting the S / CR / CA / C bits in the network element overhead of the optical fiber connection, and completing the protocol interaction with the upstream node in turn, so as to achieve end-to-end segment-by-segment adjustment from downstream to upstream. When the small-granular bandwidth is reduced and lossless adjustment is performed, the adjustment is initiated by the head node, and the CR / CA / C bits are inserted in the network element overhead of the optical fiber connection, and the protocol interaction is completed with the downstream node in turn, so as to achieve end-to-end segment-by-segment adjustment from upstream to downstream.

[0121] In an exemplary embodiment, the lossless adjustment control module 1202 is further used to determine all network element nodes in the target network that fail to adjust bandwidth based on the reporting information, wherein the reporting information is used to indicate information fed back by all network element nodes after performing bandwidth adjustment; obtain target data corresponding to all network element nodes that fail to adjust bandwidth, so as to determine the failure cause corresponding to the failure of bandwidth adjustment based on the target data, wherein the target data includes: the adjustment direction of the link where each network element node that fails to adjust bandwidth is located, the interaction information between each network element node that fails to adjust bandwidth and the adjacent network element on the same link, and the bandwidth adjustment type corresponding to each network element node that fails to adjust bandwidth, and the bandwidth adjustment type includes at least one of the following: lossless adjustment with bandwidth reduction and lossless adjustment with bandwidth increase;

[0122] That is, when it is determined that the bandwidth adjustment of the target network between the end and the end fails, the network nodes in the target network that have not been adjusted successfully are determined through the reporting information reported by each network element node after completing the protocol interaction, and then the target data corresponding to the target network element node where the bandwidth adjustment failed is obtained. For example, assuming that the target network includes N network element nodes, and the optical fiber link is broken between the N-1th node and the N-2th node, the PE 1、 PE n Corresponding to the network element nodes of the service provider edge equipment, P2 to P n-1 The network element node corresponding to the backbone equipment of the service provider is to adjust the bandwidth of the current target network to increase the bandwidth, and the adjustment direction is from PE1 to PE n When; in P n-1 The network element node receives P n-2 The network element node sends the S code block, but does not receive the CA code block, so P n-1 The network element node can only determine that the link is normal when the S code block is sent, but cannot determine whether its own CR transmission fails or the peer CA reply fails. n-2 The network element node did not receive the P n-1 Any code block sent by the network element node cannot confirm whether the link is abnormal or the other end has not issued any bandwidth adjustment. However, the control can infer that the adjustment commands have been issued successfully by integrating the code block sending and receiving information of the two network element nodes. n-1 To P n-2 The link in this direction has a fiber break.

[0123] In summary, through the above embodiments, the target data corresponding to the acquired network element nodes can be used to clearly determine the adjustment status between adjacent network element nodes on the same adjustment path. By judging the adjustment status, the cause of adjustment failure in the target network can be determined, thereby improving the accuracy of adjustment failure monitoring.

[0124] In an exemplary embodiment, the lossless adjustment control module 1202 is also used to determine the bandwidth adjustment type corresponding to the monitoring result; when the bandwidth adjustment type is bandwidth increase lossless adjustment, identify the tail node among all the network element nodes, and start from the tail node to send a fallback command for bandwidth lossless fallback to all the network element nodes hop by hop; when the bandwidth adjustment type is bandwidth reduction lossless adjustment, identify the head node among all the network element nodes, and start from the head node to send a fallback command for bandwidth lossless fallback to all the network element nodes hop by hop.

[0125] For example, when the SPN network performs small-granular bandwidth increase lossless adjustment, the control will send a bandwidth lossless increase command to all nodes on the forwarding path, and the tail node will initiate the adjustment. By inserting S / CR / CA / C bits in the network element overhead of the optical fiber connection, the protocol interaction is completed with the upstream node in turn. When it is determined that the current bandwidth increase lossless adjustment has failed, the control will send a lossless fallback command to all network elements. At this time, it is necessary to perform a reverse bandwidth lossless adjustment operation on the part where the lossless adjustment is successful, that is, the bandwidth is reduced, and the last hop network element node (that is, the previous tail node) of the last successful adjustment is used as the first node of the current adjustment to initiate the adjustment. By inserting CR / CA / C bits in the network element overhead of the optical fiber connection, the protocol interaction is completed with the downstream node in turn, thereby realizing end-to-end segment-by-segment fallback from upstream to downstream.

[0126] In an exemplary embodiment, the above-mentioned control 1204 is also used to determine the adjustment time for each network element node among all the network element nodes to execute the fallback command; when the adjustment time is greater than the preset detection time, the fallback command is repeatedly sent to the current network element node.

[0127] In an exemplary embodiment, since the lossless adjustment between end-to-end requires the control of end-to-end adjustment commands and hop-by-hop adjustment, each network element waits for the adjustment signal of the previous network element after receiving the adjustment command, and after receiving the signal, tries to repeatedly trigger the lossless adjustment to the next network element within a given time limit until the adjustment is successful. In addition, since the rollback command actually triggers the cancellation of bandwidth adjustment for each network element node that has performed bandwidth adjustment in turn, the cancellation is essentially to perform the same size of lossless bandwidth reduction on the network element node that performs bandwidth lossless increase; or to perform the same size of lossless bandwidth increase on the network element node that performs bandwidth lossless reduction. Therefore, in order to ensure the effective execution of the rollback command, after the rollback command is issued, the adjustment time of the rollback command executed on the network element node is counted within the preset detection time. When the adjustment time is longer than the preset detection time, it means that the lossless command has not been successfully executed, and the lossless command needs to be repeatedly issued to the current network element node whose adjustment time is longer than the preset detection time to ensure that all network element nodes in the target network complete the lossless return of bandwidth.

[0128] In an exemplary embodiment, the above-mentioned control 1204 is also used to determine the preset maximum number of repeated backoff times for the target object, and to count the number of times the backoff command corresponding to the current network element node is issued; when the number of issuances is greater than the maximum number of repeated backoff times, the current network element node is forcibly configured, wherein the forced configuration is used to indicate that the bandwidth of the current network element node is adjusted to a preset fixed bandwidth.

[0129] In an exemplary embodiment, when the number of rollback failures reaches the maximum repeated rollback limit M set by the user, the device will immediately report success and force configuration. In particular, if the user prohibits repeated rollback, he only needs to set M to 0. When forced configuration, the device will report success, so that the rollback will not be triggered repeatedly. The status monitoring will also be restored to a successful state so as not to affect the execution of the next user configuration adjustment command, where M is an integer.

[0130] In summary, in order to avoid the target network being unable to receive other adjustment commands due to repeated issuance of rollback commands, the issuance of rollback commands is managed by setting the maximum number of repeated rollback times for the rollback command. When the rollback cannot be completed effectively, forced configuration is used to ensure that the configuration in the target network is valid so as not to affect the execution of the next user configuration adjustment command.

[0131] In an exemplary embodiment, the above-mentioned control 1204 is also used to obtain the execution result of the most recent repeatedly issued fallback command received by the current network element node when the number of issuances is less than or equal to the preset maximum number of repeated fallbacks; when it is determined that the execution result indicates that the fallback of the current network element node has failed, repeatedly trigger the issuance of the fallback command; when it is determined that the execution result indicates that the fallback of the current network element node has been successful, end the triggering of the issuance of the fallback command.

[0132] After the rollback command is repeatedly issued, the execution result of each repeated rollback command is monitored in real time to ensure that after the rollback is successfully executed, the issuance of the rollback command is quickly terminated to avoid the impact of the rollback command on subsequent adjustments.

[0133] In an exemplary embodiment, the above-mentioned control 1204 is also used to obtain the first bandwidth adjustment signal corresponding to each network element node among all the network element nodes before issuing the fallback command; determine the second bandwidth adjustment signal corresponding to the first bandwidth adjustment signal, wherein the second bandwidth adjustment signal is determined by reversely adjusting the current bandwidth adjustment direction of the first bandwidth adjustment signal; forward the second bandwidth adjustment signal from the source node to all network element nodes hop by hop, wherein the source node is the head node or the tail node.

[0134] In an exemplary embodiment, when the bandwidth adjustment previously performed in the target network is a lossless adjustment of increasing the bandwidth, the fallback command corresponds to a lossless adjustment of decreasing the bandwidth in the opposite direction of the lossless adjustment of increasing the bandwidth; and the starting adjustment point of the lossless fallback adjustment of the lossless adjustment of increasing the bandwidth is the target network element node of the last hop of the last successful adjustment. The target network element node is used as the initial node to initiate the adjustment, and the CR / CA / C bits are respectively inserted in the network element overhead of the optical fiber connection, and the protocol interaction is completed with the downstream nodes in turn, thereby realizing end-to-end segment-by-segment fallback from upstream to downstream.

[0135] Optionally, when the bandwidth adjustment previously performed in the target network is a lossless adjustment of reducing the bandwidth, the fallback command corresponds to a lossless adjustment of increasing the bandwidth in the opposite direction of the lossless adjustment of reducing the bandwidth; and the starting adjustment point of the lossless fallback adjustment of the lossless adjustment of reducing the bandwidth is the target network element node of the last hop of the last successful adjustment. The target network element node is used as the initial node to initiate the adjustment, and the CR / CA / C bits are respectively inserted in the network element overhead of the optical fiber docking, and the protocol interaction is completed with the downstream nodes in turn, thereby realizing end-to-end and segment-by-segment adjustment from upstream to downstream.

[0136] It should be noted that the initial node for the reverse adjustment of the above-mentioned bandwidth increase lossless adjustment is the tail node of the previous adjustment; the initial node for the reverse adjustment of the above-mentioned bandwidth decrease lossless adjustment is the head node of the previous adjustment; the above is for determining the adjustment direction as a fixed direction.

[0137] In summary, the process of increasing or decreasing the service bandwidth end-to-end between different network element nodes is monitored through the lossless adjustment control module. When a link adjustment fails during the end-to-end adjustment process, the bandwidth lossless fallback operation is triggered, that is, the lossless fallback mechanism is executed after the lossless adjustment fails. The end-to-end fallback success rate is improved by customizing the lossless fallback strategy, and the service damage is minimized. The problem of service damage caused by forced bandwidth configuration when the bandwidth adjustment exceeds the preset time in the related technology is solved, thereby achieving the effect that the fallback process does not affect the continuity of the original service, thereby improving the user experience.

[0138] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0139] To facilitate the understanding of the technical solution provided by the present application, a detailed explanation will be given below in combination with embodiments of specific scenarios.

[0140] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0141] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0142] An embodiment of the present application further provides an electronic device, which may include a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0143] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0144] S1, obtaining monitoring results, wherein the monitoring results are used to monitor and determine the status of bandwidth adjustment performed on all network element nodes in the target network;

[0145] S2: When the monitoring result indicates that the bandwidth adjustment fails, a bandwidth lossless rollback command is issued to all network element nodes.

[0146] According to one aspect of the present application, a computer program product is provided, the computer program product comprising a computer program / instruction, the computer program / instruction comprising a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 809, and / or installed from the removable medium 811. When the computer program is executed by the central processing unit 801, various functions provided by the embodiments of the present application are executed. The above serial numbers of the embodiments of the present application are only for description and do not represent the advantages and disadvantages of the embodiments.

[0147] Fig.13 The computer system structure block diagram of the electronic device used to implement the embodiment of the present application is schematically shown. Fig.13As shown, the computer system 800 includes a central processing unit 801 (CPU), which can perform various appropriate actions and processes according to the program stored in the read-only memory 802 (ROM) or the program loaded from the storage part 808 to the random access memory 803 (RAM). Various programs and data required for system operation are also stored in the random access memory 803. The central processing unit 801, the read-only memory 802 and the random access memory 803 are connected to each other through a bus 804. The input / output interface 805 (Input / Output interface, i.e., I / O interface) is also connected to the bus 804.

[0148] The following components are connected to the input / output interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a local area network card, a modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the input / output interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed so that a computer program read therefrom is installed into the storage section 808 as needed.

[0149] In particular, according to an embodiment of the present application, the process described in each method flow chart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer readable medium, and the computer program contains a program code for executing the method shown in the flow chart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 809, and / or installed from the removable medium 811. When the computer program is executed by the central processor 801, various functions defined in the system of the present application are executed.

[0150] It should be noted that Fig.13 The computer system 800 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0151] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.

[0152] Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.

[0153] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principles of the present application shall be included in the protection scope of the present application.

Claims

1. A bandwidth adjustment method, characterized in that: include: Acquire monitoring results, wherein the monitoring results are used to perform status monitoring and determination on bandwidth adjustment of all network element nodes in the target network; When the monitoring result indicates that the bandwidth adjustment fails, a bandwidth lossless rollback command is issued to all network element nodes.

2. The method according to claim 1, characterized in that Obtain monitoring results, including: In the case that bandwidth adjustment failure occurs in at least one network element node among all the network element nodes, it is determined that the monitoring result is bandwidth adjustment failure of the target network.

3. The method according to claim 2, characterized in that The method further comprises: Determine all network element nodes in the target network that have failed to adjust bandwidth based on the reporting information, wherein the reporting information is used to indicate information fed back by all network element nodes after performing bandwidth adjustment; Obtain target data corresponding to all network element nodes where the bandwidth adjustment fails, so as to determine the failure cause corresponding to the bandwidth adjustment failure based on the target data, wherein the target data includes: the adjustment direction of the link where each network element node where the bandwidth adjustment fails is located, the interaction information between each network element node where the bandwidth adjustment fails and the adjacent network element on the same link, and the bandwidth adjustment type corresponding to each network element node where the bandwidth adjustment fails, wherein the bandwidth adjustment type includes at least one of the following: lossless adjustment with bandwidth reduction and lossless adjustment with bandwidth increase.

4. The method according to claim 1, characterized in that: When the monitoring result indicates that the bandwidth adjustment fails, issuing a rollback command for performing lossless bandwidth rollback to all network element nodes includes: Determining a bandwidth adjustment type corresponding to the monitoring result; In the case where the bandwidth adjustment type is bandwidth increase lossless adjustment, identifying an end node among all the network element nodes, and sending a fallback command for bandwidth lossless fallback hop by hop from the end node to all the network element nodes; In the case where the bandwidth adjustment type is lossless adjustment of bandwidth reduction, a head node among all the network element nodes is identified, and a rollback command for performing lossless bandwidth rollback is sent hop by hop from the head node to all the network element nodes.

5. The method according to claim 1, characterized in that: The method further comprises: Determine an adjustment time for each of the network element nodes to execute the rollback command; When the adjustment time is longer than the preset detection time, the rollback command is repeatedly sent to the current network element node.

6. The method according to claim 5, characterized in that The method further comprises: Determine the preset maximum number of repeated rollbacks for the target object, and count the number of times the rollback command corresponding to the current network element node is issued; In a case where the number of sending times is greater than the maximum number of repeated backoff times, the current network element node is forcibly configured, wherein the forcible configuration is used to instruct to adjust the bandwidth of the current network element node to a preset fixed bandwidth.

7. The method according to claim 6, characterized in that The method further comprises: When the number of times of sending is less than or equal to the preset maximum number of repeated backoff times, obtaining the execution result of the most recent time the current network element node receives the repeatedly sent backoff command; In a case where it is determined that the execution result indicates that the current network element node fails to roll back, repeatedly triggering the issuance of the rollback command; When it is determined that the execution result indicates that the current network element node has successfully rolled back, the triggering of the rollback command is terminated.

8. The method according to claim 1, characterized in that After sending a fallback command for performing bandwidth lossless fallback to all network element nodes, the method further includes: Acquire a first bandwidth adjustment signal corresponding to each network element node among all the network element nodes before issuing the rollback command; Determine a second bandwidth adjustment signal corresponding to the first bandwidth adjustment signal, wherein the second bandwidth adjustment signal is determined by reversely adjusting a current bandwidth adjustment direction of the first bandwidth adjustment signal; The second bandwidth adjustment signal is forwarded hop by hop from a source node to all network element nodes, wherein the source node is a head node or a tail node.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program implements the steps of the method described in any one of claims 1 to 8 when executed by a processor.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method described in any one of claims 1 to 8 are implemented.

Images