Bandwidth adjustment method, storage medium, and electronic apparatus

Abstract

Provided in the present disclosure are a bandwidth adjustment method, a storage medium, and an electronic apparatus. The method comprises: acquiring a monitoring result, wherein the monitoring result is used for executing bandwidth adjustment on all network element nodes in a target network to perform state monitoring and determination; and when the monitoring result indicates that the bandwidth adjustment has failed, issuing to all the network element nodes a rollback command for bandwidth lossless rollback. The present disclosure solves the problem in the related art of service damage caused by execution of a forced bandwidth configuration when bandwidth adjustment exceeds a preset duration.

Description

Bandwidth adjustment method, storage medium and electronic device

[0001] This disclosure claims priority to the Chinese patent application filed with the China Patent Office on June 30, 2023, with application number 202310804887.9 and invention name “Bandwidth Adjustment Method, Storage Medium and Electronic Device”, the entire contents of which are incorporated by reference into this disclosure. Technical Field

[0002] The present disclosure relates to the field of SPN small-granularity access / aggregation products, and in particular to a bandwidth adjustment method, a storage medium, and an electronic device. Background Art

[0003] Small-granular services, carrying high-value carrier private lines and enterprise services, place high demands on operations and maintenance. Currently, small-granular services can support lossless bandwidth adjustment in complex scenarios, including those configured with OAM (operation administration and maintenance) and protection. Lossless adjustment requires end-to-end control to issue adjustment commands and initiate adjustments hop by hop. After receiving the adjustment command, each network element waits for the adjustment signal from the previous network element. Upon receiving the signal, it attempts to repeatedly trigger lossless adjustment on the next network element within a given time limit until the adjustment is successful. Lossless adjustment is achieved if the end-to-end adjustment is completed within a timeout. However, due to differences in implementation mechanisms between vendors and potential hardware defects during the exploration of emerging technologies, lossless bandwidth adjustment for small-granularity cannot be guaranteed to succeed in existing networks. If lossless bandwidth adjustment fails to complete within a timeout, existing solutions will immediately force bandwidth allocation, which can cause service damage. Although this scenario is rare, users originally expected lossless bandwidth, but ultimately suffer 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 detrimental will damage the user experience and cause customer losses.

[0004] Currently, no effective solution has been found to the problem of service damage caused by immediately executing mandatory bandwidth configuration when bandwidth adjustment exceeds a preset duration in related technologies.

[0005] Summary of the Invention

[0006] The present disclosure provides a bandwidth adjustment method, a storage medium, and an electronic device, which at least solve the problem in the related art of service damage caused by immediately executing forced bandwidth configuration when bandwidth adjustment exceeds a preset duration.

[0007] According to one embodiment of the present disclosure, 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 fallback command for lossless bandwidth fallback to all network element nodes.

[0008] According to another embodiment of the present disclosure, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when running.

[0009] According to another embodiment of the present disclosure, 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 perform the steps in any one of the above method embodiments.

[0010] Through the above steps, the process of executing bandwidth adjustment on all network element nodes in the target network is monitored, and monitoring results are obtained. The bandwidth adjustment result of the target network is determined based on the monitoring results. After the monitoring results indicate that the bandwidth adjustment has failed, a fallback command for lossless bandwidth fallback is sent to all network element nodes in the target network. The fallback command is then used to reset the bandwidth configuration of the network element node where the bandwidth adjustment has failed, so that the bandwidth configuration of the network element node where the bandwidth adjustment has failed can be changed to the bandwidth configuration before the adjustment, without affecting the subsequent configuration of the network element node. This solves the problem of service damage caused by immediately executing forced bandwidth configuration when the bandwidth adjustment exceeds the preset time in the related art. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] FIG1 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 disclosure;

[0012] FIG2 is a flow chart of a bandwidth adjustment method according to an embodiment of the present disclosure;

[0013] FIG3 is a schematic structural diagram of a bandwidth lossless adjustment system according to an embodiment of the present disclosure;

[0014] FIG4 is a schematic diagram of a flow chart of a system for lossless adjustment of PE node bandwidth according to an embodiment of the present disclosure;

[0015] FIG5 is a flow chart of a system for lossless bandwidth adjustment of a P node according to an embodiment of the present disclosure;

[0016] FIG6 is a schematic diagram of an end-to-end bandwidth increase lossless adjustment according to an optional embodiment of the present disclosure;

[0017] FIG7 is a schematic diagram of an end-to-end bandwidth increase lossless fallback according to an optional embodiment of the present disclosure;

[0018] FIG8 is a schematic diagram of an end-to-end bandwidth reduction lossless adjustment according to an optional embodiment of the present disclosure;

[0019] FIG9 is a schematic diagram of an end-to-end bandwidth reduction lossless fallback according to an optional embodiment of the present disclosure;

[0020] 10 is a schematic diagram of automatic diagnosis of a link fault in which bandwidth increase fails according to an optional embodiment of the present disclosure;

[0021] FIG11 is a schematic diagram of a lossless adjustment and rollback flow chart according to an optional embodiment of the present disclosure;

[0022] FIG12 is a schematic structural diagram of a bandwidth adjustment system according to an embodiment of the present disclosure;

[0023] FIG13 is a block diagram of a computer system structure of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0024] The present disclosure will be described in detail below with reference to the accompanying drawings and in combination with embodiments. It should be noted that, unless there is a conflict, the embodiments and features in the embodiments of the present disclosure can be combined with each other.

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

[0026] Example 1

[0027] The method embodiment provided in the first embodiment of the present disclosure can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking operation on a mobile terminal as an example, FIG1 is a hardware structure block diagram of a mobile terminal according to a bandwidth adjustment method of an embodiment of the present disclosure. As shown in FIG1 , 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 the structure shown in FIG1 is only for illustration and does not limit the structure of the above-mentioned electronic device. For example, the mobile terminal 10 may also include more or fewer components than those shown in FIG1 , or have a configuration different from that shown in FIG1 .

[0028] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / modules corresponding to the bandwidth adjustment method in the embodiment of the present disclosure. 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-mentioned 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 located 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.

[0029] The transmission device 106 is used to receive or send data via a network. A specific example of the aforementioned network may include a wireless network provided by the communications provider of the mobile terminal 10. In one embodiment, the transmission device 106 may include a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0030] In this embodiment, a bandwidth adjustment method is provided. FIG2 is a flow chart of a bandwidth adjustment method according to an embodiment of the present disclosure. As shown in FIG2 , the flow may include, but is not limited to, the following steps:

[0031] Step S202: Acquire 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;

[0032] 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. The adjustment content may be configuration information for lossless bandwidth increase or lossless bandwidth decrease of the current network element.

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

[0034] Through the above steps, the process of executing bandwidth adjustment on all network element nodes in the target network is monitored, and monitoring results are obtained. The bandwidth adjustment result of the target network is determined based on the monitoring results. After the monitoring results indicate that the bandwidth adjustment has failed, a fallback command for lossless bandwidth fallback is sent to all network element nodes in the target network. The fallback command is then used to reset the bandwidth configuration of the network element node where the bandwidth adjustment has failed, so that the network element node where the bandwidth adjustment has failed can change the bandwidth configuration to the bandwidth configuration before the adjustment, without affecting the subsequent configuration of the network element node. This solves the problem of service damage caused by immediately executing forced bandwidth configuration when the bandwidth adjustment exceeds the preset time in the related art, and achieves the effect of avoiding service damage caused by forced bandwidth configuration through the fallback process. In addition, the fallback does not affect the continuity of the original service, thereby improving user experience.

[0035] In an exemplary embodiment, the above method can be applied to a bandwidth lossless adjustment system or other systems with 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.

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

[0037] Control is responsible for distributing the configured bandwidth information of the target network between end-to-end.

[0038] 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.

[0039] The status monitoring unit is mainly used to monitor the completion of 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.

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

[0041] In an exemplary embodiment, obtaining the monitoring result includes: upon determining 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.

[0042] 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 to end. Regardless of 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.

[0043] Optionally, in actual scenarios, when performing lossless adjustment of small-granular bandwidth increase in an SPN (Slicing Packet Network, referred to as SPN) network, the control will issue a lossless bandwidth increase command to all nodes on the forwarding path. The tail node initiates the adjustment by inserting the S / CR / CA / C bits in the network element overhead of the optical fiber connection, and then completes the protocol interaction with the upstream node in sequence, thereby achieving end-to-end segment-by-segment adjustment from downstream to upstream. When performing lossless adjustment of small-granular bandwidth reduction, the head node initiates the adjustment by inserting the CR / CA / C bits in the network element overhead of the optical fiber connection, and then completes the protocol interaction with the downstream node in sequence, thereby achieving end-to-end segment-by-segment adjustment from upstream to downstream.

[0044] In an exemplary embodiment, the method further includes: determining all network element nodes in the target network that have failed bandwidth adjustment based on reported information, wherein the reported information is used to indicate information fed back by all network element nodes after performing bandwidth adjustment; obtaining target data corresponding to all network element nodes that have failed bandwidth adjustment, and determining a failure cause corresponding to the bandwidth adjustment failure based on the target data, wherein the target data includes: an adjustment direction of a link on which each network element node that has failed bandwidth adjustment is located, interaction information between each network element node that has failed bandwidth adjustment and an adjacent network element on the same link, and a bandwidth adjustment type corresponding to each network element node that has failed bandwidth adjustment, wherein the bandwidth adjustment type includes at least one of the following: lossless adjustment with bandwidth reduction and lossless adjustment with bandwidth increase;

[0045] That is, when it is determined that the bandwidth adjustment of the target network between the end-to-end fails, the network nodes in the target network that have not been successfully adjusted 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, there is a fiber link break between the N-1th node and the N-2th node, among which PE1 and 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 be adjusted and increased in the current target network. The adjustment direction is from PE1 to PE n When P n-1 The network element node receives P n-2The 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, and cannot determine whether the subsequent CR transmission fails or the peer CA reply fails. n-2 The network element node does not receive 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 a bandwidth adjustment. The control and management can infer that the adjustment command has 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.

[0046] In summary, through the above embodiments, the target data corresponding to the obtained 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 the adjustment failure in the target network can be determined, thereby improving the accuracy of adjustment failure monitoring.

[0047] In an exemplary embodiment, when the monitoring result indicates that the bandwidth adjustment fails, a fallback command for performing 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 the network element nodes, and issuing the fallback command for performing lossless bandwidth fallback hop by hop starting from the tail node to all the network element nodes; when the bandwidth adjustment type is lossless adjustment of bandwidth decrease, identifying the head node among all the network element nodes, and issuing the fallback command for performing lossless bandwidth fallback hop by hop starting from the head node to all the network element nodes.

[0048] For example, when the SPN network performs small-granularity bandwidth increase lossless adjustment, the control will issue a bandwidth lossless increase command to all nodes on the forwarding path. The tail node initiates the adjustment and completes protocol interaction with the upstream node in sequence by inserting the S / CR / CA / C bits in the network element overhead of the optical fiber connection. If it is determined that the current bandwidth increase lossless adjustment has failed, the control will issue 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 was successful, that is, the bandwidth is reduced. The last hop network element node where the previous adjustment was successful (that is, the previous tail node) is used as the first node to initiate the adjustment. By inserting the CR / CA / C bits in the network element overhead of the optical fiber connection, protocol interaction is completed with the downstream node in sequence, thereby achieving end-to-end segment-by-segment fallback from upstream to downstream.

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

[0050] Determining an adjustment duration for each of the network element nodes to execute the rollback command;

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

[0052] In an exemplary embodiment, since end-to-end lossless adjustment requires end-to-end control to issue adjustment commands and initiate adjustments hop by hop, each network element waits for the adjustment signal from the previous network element after receiving the adjustment command. After receiving the signal, it attempts to repeatedly trigger 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, the cancellation is essentially a lossless reduction of the same size on the network element node that performed a lossless increase in bandwidth; or a lossless increase of the same size on the network element node that performed a lossless decrease in bandwidth. Therefore, in order to ensure the effective execution of the rollback command, after the rollback command is issued, the adjustment duration of the rollback command executed on the network element node is counted within a preset detection time. If the adjustment duration is longer than the preset detection time, it means that the lossless command was not successfully executed. It is necessary to repeatedly issue the lossless command to the current network element node whose adjustment duration is longer than the preset detection time to ensure that all network element nodes in the target network complete the lossless rollback of bandwidth.

[0053] In an exemplary embodiment, the above method also includes: determining the preset maximum number of repeated fallbacks for the target object, and counting the number of times the fallback command corresponding to the current network element node is issued; when the number of issuances is greater than the maximum number of repeated fallbacks, 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.

[0054] In one exemplary embodiment, when the number of rollback failures reaches the user-set maximum number of repeated rollbacks (M), the device immediately reports success and forces the configuration. Specifically, to disable repeated rollbacks, the user simply sets M to 0. During forced configuration, the device reports success, preventing repeated rollbacks. Status monitoring also returns to a successful state, preventing the next execution of a user configuration adjustment command. M is an integer.

[0055] In summary, in order to avoid the target network being unable to receive other adjustment commands due to repeated issuance of fallback commands, the issuance of fallback commands is managed by setting the maximum number of repeated fallback times for the fallback command. When the fallback 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.

[0056] In an exemplary embodiment, the above method also includes: when the number of issuances is less than or equal to the 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.

[0057] After repeatedly issuing the rollback command, 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 ended to avoid subsequent adjustments being affected by the rollback command.

[0058] 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 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 the network element nodes hop by hop, wherein the source node is a head node or a tail node.

[0059] In an exemplary embodiment, when the bandwidth adjustment previously performed in the target network is a lossless adjustment to increase the bandwidth, the fallback command corresponds to a lossless adjustment to decrease the bandwidth in the opposite direction of the lossless adjustment to increase the bandwidth; and the starting adjustment point of the lossless fallback adjustment of the lossless adjustment to increase the bandwidth is the target network element node of the last hop where the last adjustment was successful. The adjustment is initiated with the target network element node as the initial node, and the protocol interaction is completed with the downstream node in sequence by inserting the CR / CA / C bits respectively in the network element overhead of the optical fiber connection, thereby realizing end-to-end segment-by-segment fallback from upstream to downstream.

[0060] Optionally, when the bandwidth adjustment previously performed in the target network is a lossless adjustment to reduce the bandwidth, the fallback command corresponds to a lossless adjustment to increase the bandwidth in the opposite direction of the lossless adjustment to reduce the bandwidth; and the starting adjustment point of the lossless fallback adjustment of the lossless adjustment to reduce the bandwidth is the target network element node of the last hop where the last adjustment was successful. The adjustment is initiated with the target network element node as the initial node, and the protocol interaction is completed with the downstream node in turn by inserting the CR / CA / C bits respectively in the network element overhead of the optical fiber connection, thereby realizing end-to-end segment-by-segment adjustment from upstream to downstream.

[0061] 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.

[0062] In summary, the lossless adjustment control module monitors the status of the process of increasing or decreasing the end-to-end service bandwidth between different network element nodes. 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. By customizing the lossless fallback strategy, the end-to-end fallback success rate is improved, and the service damage is minimized. This solves the problem of service damage caused by forced bandwidth configuration when the bandwidth adjustment exceeds the preset time in related technologies, thereby achieving the effect of not affecting the continuity of the original service during the fallback process, thereby improving user experience.

[0063] Obviously, the embodiments described above are only part of the embodiments of the present disclosure, rather than all the 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 disclosure. Specifically:

[0064] In an exemplary embodiment, Figure 3 is a schematic diagram of the structure of a lossless bandwidth adjustment system according to an embodiment of the present disclosure. The lossless bandwidth adjustment system comprises three components: a control and management module 32, a lossless adjustment control module 34, and a service forwarding entity 36. The control and management module 32 is responsible for end-to-end configuration delivery. The lossless adjustment control module 36 of each network element is configured to store received configuration information, determine whether it meets the conditions for lossless adjustment, and then 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.

[0065] In an exemplary embodiment, a small-granularity bandwidth lossless fallback system is proposed. Specifically, based on the aforementioned lossless bandwidth adjustment system, a status monitoring unit is added to the lossless adjustment control module of the bandwidth adjustment system. A set of adjustment result query and reporting interfaces are added between the control and lossless adjustment control module, and a status reporting interface is added to the service forwarding entity. These additional units and interfaces enable the triggering of network element bandwidth fallback when adjustment fails.

[0066] It should be noted that lossless bandwidth adjustment refers to a method for increasing or decreasing service bandwidth end-to-end without damaging small-granular services. Lossless bandwidth fallback refers to the process of performing lossless bandwidth adjustment in the reverse direction if adjustment fails on a link during the end-to-end adjustment process, thereby avoiding service loss. This method can increase the success rate of lossless bandwidth adjustment during small-granular service maintenance. Even if bandwidth adjustment fails, lossless fallback can be implemented without damaging the connected services.

[0067] In an exemplary embodiment, for a PE (Provider Edge) node, services are forwarded in only one direction, so only one configuration message is received for each adjustment, as shown in Figure 4, which is a flow chart of a PE node bandwidth lossless adjustment system according to an embodiment of the present disclosure. When the above-mentioned bandwidth lossless fallback system is running, it performs the following steps:

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

[0069] 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;

[0070] In step S403, the control sends a blocking adjustment status query command to the lossless adjustment control module. This adjustment status query command does not involve any configuration to the service forwarding entity; it only queries the adjustment results of the configuration command execution in the status monitoring unit. In actual applications, after the adjustment status query command is issued, the lossless adjustment control module of the PE node does not immediately respond and does not allow further configuration to be issued. This allows the network element to process only one adjustment at a time. It should be noted that the above steps S402 and S403 can actually be issued in any time sequence.

[0071] 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.

[0072] 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, allowing the adjustment to continue or to be sent back.

[0073] When the adjustment fails, the lossless adjustment control module not only reports the failure result and the network element overhead transmission and reception 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.

[0074] 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 fallen back 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 the monitoring detects that the adjustment is not successful, the configuration management module will not solidify the configuration temporarily stored for 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-issue 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.

[0075] It is understood that when the service forwarding entity reports a successful adjustment, the bandwidth modification configuration is allowed to take effect and is saved as the official configuration, thereby implementing the configuration solidification process for the successful adjustment. If the adjustment fails, the temporarily saved bandwidth modification configuration will not be converted to the official configuration. After the rollback command is issued, the configuration management unit will directly issue a reverse bandwidth adjustment configuration and delete the temporary configuration, thereby achieving consistency between the upper and lower configurations. If the adjustment fails, there is no need to solidify the configuration, and the configuration will eventually be rolled back.

[0076] In an exemplary embodiment, for a P (Provider, service provider backbone equipment, abbreviated as P) node, services have two forwarding directions, so two configuration messages will be received for each adjustment, as shown in Figure 5, which is a flow chart of a P node bandwidth lossless adjustment system according to an embodiment of the present disclosure. When the P node is running, the above-mentioned bandwidth lossless fallback system performs the following steps:

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

[0078] 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;

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

[0080] 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 unit;

[0081] 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 second direction adjustment to time out.

[0082] 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. The first adjustment result is not directly fed back to the management and control, but is only stored in the status monitoring module.

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

[0084] Step S507 : The control sends the bandwidth modification configuration for 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.

[0085] 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 bidirectional protocol interaction.

[0086] 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.

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

[0088] To facilitate understanding of the technical solutions provided by the present disclosure, embodiments of the present disclosure will be described in detail below with reference to specific scenarios.

[0089] When performing lossless bandwidth increase adjustments for small-granularity bandwidth, the control system issues lossless bandwidth increase commands to all nodes along the forwarding path. The tail node initiates the adjustment by inserting the S / CR / CA / C bits into the fiber-connected network element overhead, interacting with the upstream node in sequence to achieve end-to-end, segment-by-segment adjustments. When performing lossless bandwidth reduction adjustments for small-granularity bandwidth, the head node initiates the adjustment by inserting the CR / CA / C bits into the fiber-connected network element overhead, interacting with the downstream node in sequence to achieve end-to-end, segment-by-segment adjustments.

[0090] In an exemplary embodiment, when the bandwidth is increased, a link in the middle may be abnormal or broken, as shown in Figure 6. Figure 6 is a schematic diagram of lossless adjustment of end-to-end bandwidth increase according to an optional embodiment of the present disclosure; 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 After combining the adjustment results in both directions, the adjustment failure is reported and the service is recorded as in the adjustment failure state. n-2 Because the network elements in between have not received the adjustment signal from the downstream, they will eventually time out and fail to report. Only when all network elements report the adjustment successfully will the control consider the end-to-end bandwidth adjustment successful.

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

[0092] For the part that is successfully adjusted without loss, 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, it inserts the CR / CA / C bits in the network element overhead of the fiber connection, and completes the protocol interaction with the downstream nodes in turn, thereby achieving 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.

[0093] When a new adjustment command is actually issued, the device determines whether it is a configuration command or a rollback command by checking whether the service is in the adjustment failure state. If the service is in the adjustment failure state, it is considered a rollback command. Simply restore the underlying configuration to match the user configuration and then restore the adjustment state of the service. If the service is in the adjustment success state, it is considered an adjustment command.

[0094] In an exemplary embodiment, when the bandwidth is reduced, a link in the middle experiences abnormal interaction or fiber breakage, as shown in Figure 8. Figure 8 is a schematic diagram of an end-to-end lossless adjustment of bandwidth reduction according to an optional embodiment of the present disclosure. 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 inserted into the network element overhead of the optical fiber connection, and the protocol interaction is completed with the downstream node in sequence, thereby achieving 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.

[0095] When the end-to-end bandwidth reduction fails, the control will issue a lossless fallback command to all network elements, as shown in Figure 9. Figure 9 is a schematic diagram of a lossless fallback of end-to-end bandwidth reduction according to an optional embodiment of the present disclosure, 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, thus realizing end-to-end segment-by-segment fallback from downstream to upstream. After judging that it is a fallback 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 adjusted status of this service.

[0096] It should be noted that, during the actual adjustment process, lossless end-to-end bandwidth adjustment is performed bidirectionally. When bandwidth adjustment fails between two network elements, a device can only detect the adjustment failure between itself and its neighbor. It cannot determine whether the adjustment failure is due to a lack of synchronized adjustment between the connected devices or a link anomaly, nor can it determine which direction the link anomaly is located. The device that failed the adjustment extracts and reports overhead interaction information to the control system. The control system can then integrate the overhead transmission and reception information of both devices to perform intelligent and accurate diagnosis of the cause of the failure, clearly identifying any of the following: a link break between the peer device and the peer network element, a fiber break in the network element's sending direction, a fiber break in the network element's receiving direction, or a bidirectional fiber break in the link.

[0097] In an exemplary embodiment, according to the process of bandwidth adjustment and increase shown in FIG6 , during the increase process, S / CR / CA / C code blocks will be initiated in both directions, and link abnormalities will affect the overhead interaction of 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 transmission fails or the CA reply fails on the other end. n-2 Not received P n-1 Any code block sent cannot confirm whether the link is abnormal or the other end has not issued a bandwidth adjustment. The control and management can infer that the adjustment command has been issued successfully by combining the code block sending and receiving information of the two devices. n-1 to P n-2 A fiber breakage occurs in the link in this direction, as shown in FIG10 . FIG10 is a schematic diagram of automatic diagnosis of a link fault in which bandwidth increase fails according to an optional embodiment of the present disclosure.

[0098] It should be noted that bandwidth reduction scenarios are similar. 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, both fibers are broken.

[0099] In an exemplary embodiment, FIG11 is a schematic diagram of a lossless adjustment and rollback flow chart according to an optional embodiment of the present disclosure, which specifically includes the following steps:

[0100] Step S1102, issue adjustment or rollback; As shown in Figure 11, there are four possibilities for starting the bandwidth lossless adjustment and lossless rollback system: the user configures the bandwidth adjustment command, the adjustment of this 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 failure of the adjustment of this network element causes the control to issue a rollback command, and the rollback failure of this network element repeatedly triggers the rollback. In these two scenarios, the status monitoring is in the failure state, and the device will execute the lossless rollback 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 execution process is slightly different.

[0101] Step S1104: Determine whether it is a rollback: The network element determines whether the last adjustment failed based on the status monitoring information in the lossless adjustment control module, and thus determines whether the current adjustment is a rollback. If the last adjustment failed, the current adjustment is a rollback; if the last adjustment succeeded, the current adjustment is a configuration.

[0102] Step S1106: Timeout determination: After the service forwarding entity initiates protocol interaction, the lossless adjustment control module starts a timer to periodically detect adjustment success signals and alarms. If an adjustment success signal is detected within the timeout period, the timeout is considered complete. If an adjustment success signal is not detected within the timeout period, but an alarm indicating the absence of overhead fields such as S / CR / CA / C is detected, the adjustment is triggered again. If an adjustment success signal is not detected within the timeout period, the adjustment or fallback is considered to have timed out.

[0103] Step S1108: Check if the fallback policy is satisfied. The maximum number of repeated fallbacks, N, can be set based on user preference. When N is 0, fallback is only allowed after an adjustment failure. Re-triggering the fallback after a fallback failure is not permitted; the device immediately reports the failure and forces configuration. When N is greater than 0, not only is fallback permitted after an adjustment failure, but also a maximum of N consecutive re-triggerings are supported after a fallback failure.

[0104] Step S1110, lossless rollback: During the lossless rollback process, the table entries that were successfully configured last time can be reversed in the same manner as the lossless adjustment. For the table entries that failed to be configured last time, since they have been restored in the preprocessing, no further processing is required.

[0105] Step S1112, lossless adjustment; according to the bandwidth adjustment direction, hop-by-hop bandwidth lossless adjustment is initiated between service forwarding entities, thereby ultimately achieving end-to-end bandwidth lossless adjustment.

[0106] Step S1114: Pre-rollback preprocessing. This processing is performed only after the lossless adjustment times out. For entries that failed to be configured, the configuration must be restored to the original setting. For example, if the original bandwidth was 10 Mbps and the user issued a command to adjust it to 30 Mbps, after the network element times out during the lossless adjustment, pre-rollback processing will revert the configuration to 10 Mbps. When the lossless rollback command is subsequently issued, no further processing is required for entries that failed to be adjusted. Entries that successfully adjusted are processed during the rollback process.

[0107] Step S1116: Successful reporting: 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.

[0108] Step S1118, reporting failure; when the lossless adjustment of the service forwarding entity fails or the repeated fallback policy is met, 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.

[0109] Step S1120: Force configuration. When the number of rollback failures reaches the user-set maximum number of repeated rollbacks (N), the device immediately reports success and forces configuration. Specifically, the user can disable repeated rollbacks by simply setting N to 0. During forced configuration, the device reports success, preventing repeated rollbacks. Status monitoring also returns to a successful state, preventing the next user configuration adjustment command from being affected.

[0110] Step S1122: Whether the end-to-end adjustment is successful; after each network element reports its own adjustment results to the control, the control will consider the end-to-end adjustment successful only when all network elements are adjusted successfully or the forced configuration is successful, and the control will consider it successful and the process ends. Otherwise, the end-to-end adjustment will be considered a failure and an end-to-end rollback will be triggered. Due to the different state 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 will regard this rollback as a new adjustment process. The network element that failed to adjust or rollback last time was actively triggered to rollback, and can perceive that this is a rollback, and will trigger the rollback through the "report failure to trigger rollback" or "meet the re-rollback policy" process.

[0111] It should be noted that the above implementation supports the configuration of small-granularity OAM and small-granularity protection scenarios. Adjusting and rolling back bandwidth will not cause abnormal alarms, facilitating the management and maintenance of small-granularity services. This can also be extended to bandwidth modification for services such as FlexE.

[0112] In summary, the above implementation methods enhance the stability of existing high-value dedicated line small-granularity services. When the link is normal, even if the bandwidth lossless adjustment fails, it can still achieve a 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 easy to push to similar business scenarios.

[0113] 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 the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as read-only memory / random access memory (ROM / RAM), a magnetic disk, or an optical disk), and can include a number of instructions to enable a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present disclosure.

[0114] Example 2

[0115] This embodiment also provides a bandwidth adjustment system for implementing the above-mentioned embodiments and preferred implementations. Details already described will not be repeated. As used below, the term "module" may refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0116] FIG12 is a schematic structural diagram of a bandwidth adjustment system according to an embodiment of the present disclosure. As shown in FIG12 , the system may include:

[0117] The lossless adjustment control module 1202 is configured 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;

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

[0119] Through the above system, the process of bandwidth adjustment performed by all network element nodes in the target network is monitored, and monitoring results are obtained. The bandwidth adjustment result of the target network is determined based on the monitoring results. After the monitoring results indicate that the bandwidth adjustment has failed, a fallback command for lossless bandwidth fallback is sent to all network element nodes in the target network. The fallback command is then used to reset the bandwidth configuration of the network element node where the bandwidth adjustment has failed, so that the network element node where the bandwidth adjustment has failed can change the bandwidth configuration to the bandwidth configuration before the adjustment, without affecting the subsequent configuration of the network element node. This solves the problem of service damage caused by immediately executing forced bandwidth configuration when the bandwidth adjustment exceeds the preset time in the related art, and achieves the effect of avoiding service damage caused by forced bandwidth configuration through the fallback process. In addition, the fallback does not affect the continuity of the original service, thereby improving user experience.

[0120] 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 among all the network element nodes occurs.

[0121] 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 to end. Regardless of 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.

[0122] Optionally, in actual scenarios, when performing lossless adjustment of small-granular bandwidth increase in an SPN (Slicing Packet Network, referred to as SPN) network, the control will issue a lossless bandwidth increase command to all nodes on the forwarding path. The tail node initiates the adjustment by inserting the S / CR / CA / C bits in the network element overhead of the optical fiber connection, and then completes the protocol interaction with the upstream node in sequence, thereby achieving end-to-end segment-by-segment adjustment from downstream to upstream. When performing lossless adjustment of small-granular bandwidth reduction, the head node initiates the adjustment by inserting the CR / CA / C bits in the network element overhead of the optical fiber connection, and then completes the protocol interaction with the downstream node in sequence, thereby achieving end-to-end segment-by-segment adjustment from upstream to downstream.

[0123] In an exemplary embodiment, the lossless adjustment control module 1202 is further configured to determine all network element nodes in the target network that failed bandwidth adjustment based on reported information, wherein the reported 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 failed bandwidth adjustment, and determine the failure cause corresponding to the bandwidth adjustment failure based on the target data, wherein the target data includes: an adjustment direction of a link on which each network element node that failed bandwidth adjustment is located, interaction information between each network element node that failed bandwidth adjustment and an adjacent network element on the same link, and a bandwidth adjustment type corresponding to each network element node that failed bandwidth adjustment, wherein the bandwidth adjustment type includes at least one of the following: lossless adjustment with bandwidth reduction or lossless adjustment with bandwidth increase;

[0124] That is, when it is determined that the bandwidth adjustment of the target network between the end-to-end fails, the network nodes in the target network that have not been successfully adjusted 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, there is a fiber link break between the N-1th node and the N-2th node, among which PE1 and 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 be adjusted and increased in the current target network. The adjustment direction is from PE1 to PE n When 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, and cannot determine whether the subsequent CR transmission fails or the peer CA reply fails. n-2 The network element node does not receive 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 a bandwidth adjustment. The control and management can infer that the adjustment command has 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.

[0125] In summary, through the above embodiments, the target data corresponding to the obtained 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 the adjustment failure in the target network can be determined, thereby improving the accuracy of adjustment failure monitoring.

[0126] In an exemplary embodiment, the lossless adjustment control module 1202 is further configured to, when determining the bandwidth adjustment type corresponding to the monitoring result; in a case where 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; in a case where 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.

[0127] For example, when the SPN network performs small-granularity bandwidth increase lossless adjustment, the control will issue a bandwidth lossless increase command to all nodes on the forwarding path. The tail node initiates the adjustment and completes protocol interaction with the upstream node in sequence by inserting the S / CR / CA / C bits in the network element overhead of the optical fiber connection. If it is determined that the current bandwidth increase lossless adjustment has failed, the control will issue 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 was successful, that is, the bandwidth is reduced. The last hop network element node where the previous adjustment was successful (that is, the previous tail node) is used as the first node to initiate the adjustment. By inserting the CR / CA / C bits in the network element overhead of the optical fiber connection, protocol interaction is completed with the downstream node in sequence, thereby achieving end-to-end segment-by-segment fallback from upstream to downstream.

[0128] In an exemplary embodiment, the above-mentioned control 1204 is also configured to determine the adjustment time for each of 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.

[0129] In an exemplary embodiment, since end-to-end lossless adjustment requires end-to-end control to issue adjustment commands and initiate adjustments hop by hop, each network element waits for the adjustment signal from the previous network element after receiving the adjustment command. After receiving the signal, it attempts to repeatedly trigger 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, the cancellation is essentially a lossless reduction of the same size on the network element node that performed a lossless increase in bandwidth; or a lossless increase of the same size on the network element node that performed a lossless decrease in bandwidth. Therefore, in order to ensure the effective execution of the rollback command, after the rollback command is issued, the adjustment duration of the rollback command executed on the network element node is counted within a preset detection time. If the adjustment duration is longer than the preset detection time, it means that the lossless command was not successfully executed. It is necessary to repeatedly issue the lossless command to the current network element node whose adjustment duration is longer than the preset detection time to ensure that all network element nodes in the target network complete the lossless rollback of bandwidth.

[0130] In an exemplary embodiment, the above-mentioned control 1204 is also configured to determine the preset maximum number of repeated fallbacks for the target object, and count the number of times the fallback command corresponding to the current network element node is issued; when the number of issuances is greater than the maximum number of repeated fallbacks, 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.

[0131] In one exemplary embodiment, when the number of rollback failures reaches the user-set maximum number of repeated rollbacks (M), the device immediately reports success and forces the configuration. Specifically, to disable repeated rollbacks, the user simply sets M to 0. During forced configuration, the device reports success, preventing repeated rollbacks. Status monitoring also returns to a successful state, preventing the next execution of a user configuration adjustment command. M is an integer.

[0132] In summary, in order to avoid the target network being unable to receive other adjustment commands due to repeated issuance of fallback commands, the issuance of fallback commands is managed by setting the maximum number of repeated fallback times for the fallback command. When the fallback 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.

[0133] In an exemplary embodiment, the above-mentioned control 1204 is also configured 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; 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 failed; and end the triggering of 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 succeeded.

[0134] After repeatedly issuing the rollback command, 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 ended to avoid subsequent adjustments being affected by the rollback command.

[0135] In an exemplary embodiment, the above-mentioned control 1204 is also configured to obtain a first bandwidth adjustment signal corresponding to each network element node among all the network element nodes before issuing the fallback 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 the current bandwidth adjustment direction of the first bandwidth adjustment signal; and 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.

[0136] In an exemplary embodiment, when the bandwidth adjustment previously performed in the target network is a lossless adjustment to increase the bandwidth, the fallback command corresponds to a lossless adjustment to decrease the bandwidth in the opposite direction of the lossless adjustment to increase the bandwidth; and the starting adjustment point of the lossless fallback adjustment of the lossless adjustment to increase the bandwidth is the target network element node of the last hop where the last adjustment was successful. The adjustment is initiated with the target network element node as the initial node, and the protocol interaction is completed with the downstream node in sequence by inserting the CR / CA / C bits respectively in the network element overhead of the optical fiber connection, thereby realizing end-to-end segment-by-segment fallback from upstream to downstream.

[0137] Optionally, when the bandwidth adjustment previously performed in the target network is a lossless adjustment to reduce the bandwidth, the fallback command corresponds to a lossless adjustment to increase the bandwidth in the opposite direction of the lossless adjustment to reduce the bandwidth; and the starting adjustment point of the lossless fallback adjustment of the lossless adjustment to reduce the bandwidth is the target network element node of the last hop where the last adjustment was successful. The adjustment is initiated with the target network element node as the initial node, and the protocol interaction is completed with the downstream node in turn by inserting the CR / CA / C bits respectively in the network element overhead of the optical fiber connection, thereby realizing end-to-end segment-by-segment adjustment from upstream to downstream.

[0138] 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.

[0139] In summary, the lossless adjustment control module monitors the status of the end-to-end process of increasing or decreasing the service bandwidth between different network element nodes. 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. By customizing the lossless fallback strategy, the end-to-end fallback success rate is improved, and the service damage is minimized. This solves the problem of service damage caused by forced bandwidth configuration when the bandwidth adjustment exceeds the preset time in related technologies, thereby achieving the effect of not affecting the continuity of the original service during the fallback process, thereby improving the user experience.

[0140] It should be noted that the above modules can be implemented through 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.

[0141] To facilitate understanding of the technical solutions provided by the present disclosure, embodiments of the present disclosure will be described in detail below with reference to specific scenarios.

[0142] An embodiment of the present disclosure further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when run.

[0143] 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.

[0144] An embodiment of the present disclosure further provides an electronic device, 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 perform the steps in any of the above method embodiments.

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

[0146] 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;

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

[0148] According to one aspect of the present disclosure, a computer program product is provided, comprising a computer program / instruction containing program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via the communication portion 809 and / or installed from a removable medium 811. When the computer program is executed by the central processing unit 801, the various functions provided by the embodiments of the present disclosure are performed. The serial numbers of the embodiments of the present disclosure are for descriptive purposes only and do not represent the merits or demerits of the embodiments.

[0149] Figure 13 schematically shows a computer system structure block diagram for implementing an electronic device of an embodiment of the present disclosure. As shown in Figure 13, computer system 800 includes a central processing unit 801 (Central Processing Unit, CPU), which can perform various appropriate actions and processes according to the program stored in a read-only memory 802 (Read-Only Memory, ROM) or the program loaded from a storage portion 808 into a random access memory 803 (Random Access Memory, RAM). In the random access memory 803, various programs and data required for system operation are also stored. The central processing unit 801, the read-only memory 802 and the random access memory 803 are connected to each other via a bus 804. An input / output interface 805 (Input / Output interface, i.e., an I / O interface) is also connected to the bus 804.

[0150] The following components are connected to the input / output interface 805: an input section 806 including a keyboard, a mouse, and the like; an output section 807 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and a speaker; a storage section 808 including a hard disk; and a communication section 809 including a network interface card such as a local area network card or a modem. 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, or a semiconductor memory, is installed in the drive 810 as needed, so that a computer program read therefrom can be installed into the storage section 808 as needed.

[0151] In particular, according to an embodiment of the present disclosure, the processes described in the various method flow charts can be implemented as computer software programs. For example, an embodiment of the present disclosure includes a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for executing the methods shown in the flow charts. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 809 and / or installed from a removable medium 811. When the computer program is executed by the central processing unit 801, the various functions defined in the system of the present disclosure are performed.

[0152] It should be noted that the computer system 800 of the electronic device shown in FIG13 is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0153] 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 here.

[0154] Obviously, those skilled in the art should understand that the modules or steps of the present disclosure described above can be implemented using a general-purpose computing device, they can be concentrated on a single computing device, or distributed across a network composed of multiple computing devices, they can be implemented using program code executable by the computing device, and thus, 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 performed in a different order than herein, or they can be fabricated into separate integrated circuit modules, or multiple modules or steps can be fabricated into a single integrated circuit module for implementation. Thus, the present disclosure is not limited to any particular combination of hardware and software.

[0155] The foregoing description is merely a preferred embodiment of the present disclosure and is not intended to limit the present disclosure. Those skilled in the art will readily appreciate that various modifications and variations of the present disclosure are possible. Any modifications, equivalent substitutions, or improvements made within the principles of the present disclosure shall be included within the scope of protection of the present disclosure.

Claims

1. A bandwidth adjustment method, comprising: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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 having a computer program stored therein, wherein: When the computer program is executed by a processor, the steps of the method described in any one of claims 1 to 8 are implemented.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method according to any one of claims 1 to 8 when executing the computer program.

Images