Bandwidth adjustment method, electronic device, and storage medium

Abstract

The present application provides a bandwidth adjustment method, an electronic device, and a computer readable storage medium. The bandwidth adjustment method comprises: when alarm information is detected, executing a lossy bandwidth adjustment operation on a target service on the basis of first bandwidth adjustment information, wherein the first bandwidth adjustment information at least comprises one of the following: a bandwidth adjustment type and a time slot number to be adjusted.

Description

Bandwidth adjustment method, electronic device and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on the Chinese patent application with application number 202410051948.3 and application date of January 12, 2024, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby introduced into this application as a reference. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a bandwidth adjustment method, electronic device, and storage medium. Background Art

[0004] A key characteristic of Ethernet services is bandwidth variability. This requires the optical transport network (OTN) that carries Ethernet to support bandwidth adjustment to improve service carrying efficiency. Currently, lossless bandwidth adjustment technology based on timeslot adjustment has been developed for OTN, but it has limitations and can only meet the requirements of lossless bandwidth adjustment in non-protection scenarios. For OTN with protection, how to adjust service bandwidth is a technical challenge that needs to be solved.

[0005] Summary of the Invention

[0006] Embodiments of the present application provide a bandwidth adjustment method, an electronic device, and a computer-readable storage medium for implementing OTN service bandwidth adjustment in a protection scenario.

[0007] In a first aspect, an embodiment of the present application provides a bandwidth adjustment method, the method comprising:

[0008] When the alarm information is detected, a lossy bandwidth adjustment operation is performed on the target service according to the first bandwidth adjustment information, where the first bandwidth adjustment information includes at least one of the following: a bandwidth adjustment type and a timeslot number to be adjusted.

[0009] In a second aspect, an embodiment of the present application provides an electronic device, including:

[0010] one or more processors;

[0011] A memory having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the bandwidth adjustment method as described in the first aspect.

[0012] In a third aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the bandwidth adjustment method as described in the first aspect is implemented.

[0013] Embodiments of the present application provide a bandwidth adjustment method, electronic device, and computer-readable storage medium. Upon detecting an alarm, lossy bandwidth adjustment is performed on a target service based on first bandwidth adjustment information. The first bandwidth adjustment information includes at least one of the following: a timeslot adjustment type and the timeslot number to be adjusted. In other words, upon the occurrence of an alarm, a node on the protection channel initiates lossy bandwidth adjustment for the service. This allows the service bandwidth on the protection channel to be quickly adjusted after the alarm is resolved, minimizing losses. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings are used to provide a further understanding of the technical solution of the present application and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the technical solution of the present application and do not constitute a limitation on the technical solution of the present application.

[0015] FIG1 is a schematic diagram of an OTN with protection scenario provided in an embodiment of the present application;

[0016] FIG2 is a flow chart of a bandwidth adjustment method provided in an embodiment of the present application;

[0017] FIG3 is a flow chart of another bandwidth adjustment method provided in an embodiment of the present application;

[0018] FIG4 is a schematic diagram of a single-point failure scenario of a protection channel provided by an embodiment of the present application;

[0019] FIG5 is a schematic diagram of a multi-point failure scenario of a protection channel provided by an embodiment of the present application;

[0020] FIG6 is a schematic diagram of a service scenario without protection provided in an embodiment of the present application;

[0021] FIG7 is a schematic diagram of fgOTN overhead provided in an embodiment of the present application;

[0022] FIG8 is a schematic diagram of ODU lossless overhead provided in an embodiment of the present application;

[0023] FIG9 is a schematic diagram of an OSU service OAM frame format according to an embodiment of the present application;

[0024] FIG10 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0025] In order to enable those skilled in the art to better understand the technical solution of the present application, the technical solution provided by the present application is described in detail below with reference to the accompanying drawings.

[0026] Example embodiments will be described more fully hereinafter with reference to the accompanying drawings, but the described example embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete and will fully convey the scope of this application to those skilled in the art.

[0027] As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0028] The terms used herein are used only to describe specific embodiments and are not intended to limit this application. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It will also be understood that when the terms "comprising" and / or "made of" are used in this specification, they specify the presence of features, wholes, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or groups thereof.

[0029] In the following description, reference is made to “some embodiments”, which describes a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0030] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and the present application, and will not be interpreted as having an idealized or overly formal meaning, unless clearly defined in the examples of the present application.

[0031] To facilitate a better understanding of the solutions of the embodiments of the present application, the relevant technologies are first introduced below.

[0032] The Optical Transport Network (OTN) is a high-capacity, high-speed communications network based on optical fiber transmission. It uses optical technology to convert data into optical signals for transmission over optical fibers, supporting large-scale data communications. Based on the ITU-TG.709 OTN frame structure, OTN technology supports the mapping and transparent transmission of various client signals, such as Synchronous Digital Hierarchy (SDH), Asynchronous Transfer Mode (ATM), and Ethernet.

[0033] A key feature of the Optical Transport Network (OTN) is its layered nature. The OTN is divided into multiple network layers, each serving as a service layer and a client layer. Client signals are transmitted between these layers, and each layer has its own overhead, used to detect the quality of the signal at that layer. According to ITU-T G.709, OTN is divided into the client signal layer, optical channel payload unit (OPU), optical channel data unit (ODU), optical channel transport unit (OTU), optical channel layer (OCH), optical multiplex section layer (OMS), and optical transmission section layer (OTS). Each of these layers serves as a client layer, while the other serves as a service layer.

[0034] Please refer to Figure 1, which shows a schematic diagram of an OTN with protection scenario. The OTN is equipped with a working channel and a protection channel between the source node (end A) and the sink node (end Z). Its protection principle is 1+1 protection switching. That is, under normal circumstances, OTN services are transmitted through the nodes of the working channel. When the working channel transmission is interrupted or the performance degrades to a certain extent, the system switching equipment automatically transfers the main signal of the OTN service to the protection channel for transmission. This allows the receiving end to still receive normal signals and is unaware of any network abnormalities.

[0035] A key characteristic of Ethernet services is that bandwidth can vary. This requires that the OTN network (OTN) that carries Ethernet support lossless bandwidth adjustment. Currently, lossless bandwidth adjustment technology based on timeslot adjustment has been developed for OTN. However, this technology has limitations and can only meet the lossless bandwidth adjustment requirements of OTN services without protection. For OTN services with protection, there is no service bandwidth adjustment solution that fully meets user needs.

[0036] On the one hand, adjusting the protocol requires overhead support. In a 1+1 protection scenario, a concurrent selection mechanism is used. The sink node selects services from the working channel, and services from the protection channel are not transmitted downstream. Therefore, the overhead content cannot be directly transmitted along with the services. Therefore, additional overhead termination and regeneration processing, as well as complex inter-board communication mechanisms, are required. To meet protection requirements, the overall processing mechanism becomes extremely complex.

[0037] On the other hand, adjustments require a certain amount of time. Lossless bandwidth adjustment based on flexible-rate optical digital units (ODUflex) takes about minutes to adjust, while the lossless bandwidth adjustment time based on fine-grained flexible-rate optical digital units (fgODUflex) is reduced to seconds. However, if the service encounters an abnormality during the adjustment process, the protocol will fail. Currently, there is a lack of solutions that can quickly restore services to minimize losses.

[0038] Generally speaking, lossless adjustment mechanisms cannot fully implement overhead protocols or effectively handle abnormal situations such as service interruptions. Directly modifying service configurations often results in service damage, which is the case with lossy adjustment. However, using lossless protocols with specialized adjustment processing allows for lossless bandwidth changes, which is the case with lossless adjustment. Relatively speaking, lossy adjustment is more direct, convenient, and fast, while lossless adjustment interaction and processing are more complex and time-consuming.

[0039] In traditional OTN, a hitless adjustment mechanism for ODUflex (GFP) based on packet services is defined. G.7044 (also known as G.HAO) defines relevant content in the overhead of high- and low-order services to complete the link connection adjustment negotiation (LCR) and bandwidth adjustment (BWR) protocols, achieving lossless bandwidth adjustment.

[0040] fgOTN's lossless adjustment mechanism is similar to G.HAO, but adds the requirement for single-point adjustment triggering at the source node. Using the per-hop triggering fgLCR adjustment mechanism, relevant protocol information is forwarded hop-by-hop using high-order service layer overhead, negotiating bandwidth adjustments for the entire service from the source node to the sink node.

[0041] The Optical Service Unit (OSU) standard also includes provisions for lossless bandwidth adjustment. For protection scenarios, adjustments can only be made after receiving adjustment overhead responses from both the working and protection channels. Due to the inherent characteristics of OSU services, there's no need to utilize high-level service layer overhead to convey protocol content requiring no bandwidth adjustment. Instead, unified OAM frames are used for processing, requiring only low-level service information. This simplifies the overall process and supports single-point adjustment triggering at the source node.

[0042] Compared with lossless bandwidth adjustment protocols, bandwidth adjustment for OTN services in protection scenarios currently requires resolving the problem of protocol unreachability at certain nodes under abnormal circumstances, as well as the issue of how to resume protocol execution after the abnormal situation disappears.

[0043] Based on this, embodiments of the present application provide a bandwidth adjustment method, an electronic device, and a computer-readable storage medium, which aim to solve the problem of service bandwidth adjustment in an OTN protection scenario.

[0044] Please refer to Figure 2, which is a flow chart of a bandwidth adjustment method provided in an embodiment of the present application. As shown in Figure 2, the bandwidth adjustment method includes the following steps:

[0045] Step S101: When an alarm is detected, a lossy bandwidth adjustment operation is performed on a target service according to first bandwidth adjustment information, where the first bandwidth adjustment information includes at least one of the following: a bandwidth adjustment type and a timeslot number to be adjusted.

[0046] The alarm information may include forward service alarm information and reverse service alarm information.

[0047] It should be noted that the forward service alarm information represents the service alarm information received in the forward direction, and the reverse service alarm information represents the service alarm information received in the reverse direction. The forward direction described in the embodiment of the present application can be understood as the same transmission direction as the first bandwidth adjustment information, or as the direction from upstream to downstream; the reverse direction described in the embodiment of the present application can be understood as the opposite transmission direction to the first bandwidth adjustment information, or as the direction from downstream to upstream.

[0048] The target service described in the embodiment of the present application may be a bidirectional service, including forward transmission from end A to end Z, and reverse transmission from end Z to end A. The alarm information described in the embodiment of the present application may be a near-end service alarm information, indicating that the service signal upstream in the alarm reception detection direction has failed; or a far-end service alarm information, indicating that the service signal in the direction opposite to the alarm detection reception direction has failed. In the embodiment of the present application, any one of the near-end and far-end alarm information for the service received in the forward direction and the near-end and far-end alarm information for the service received in the reverse direction may trigger the node in the OTN to perform a lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information.

[0049] Exemplarily, the alarm information includes at least one of the following: loss of signal LOS alarm information, loss of frame LOF alarm information, loss of multiframe LOM alarm information, alarm indication signal AIS, disconnect indication signal OCI, lock indication signal LCK, backward defect indication BDI alarm information.

[0050] The meanings of the above warning messages are as follows:

[0051] (1) LOS (Loss of Signal) alarm information, that is, signal loss, usually occurs when the receiving end cannot detect the signal transmitted by the sending end;

[0052] (2) LOF (loss of frame) alarm information, that is, frame loss. For example, if the expected framing byte cannot be found for 5 consecutive frames, a LOF alarm signal will appear;

[0053] (3) LOM (loss of multiframe) alarm information: when the multiframe alignment byte is wrong, the LOM alarm signal will appear;

[0054] (4) Alarm Indication Signal (AIS), which is a signal transmitted downstream indicating that a defect has been detected upstream;

[0055] (5) A disconnection indication signal OCI, which is transmitted downstream to indicate that the upstream signal is not connected to the path terminal source;

[0056] (6) Lock indication signal LCK, used to indicate that the upstream signal is in a locked state and no signal can pass;

[0057] (7) Backward defect indication (BDI) alarm information is used to indicate the signal failure status detected at the terminal sink function.

[0058] It is understandable that any service alarms in the forward and reverse directions of the protocol initiation direction indicate that the service has been damaged and the conditions for lossless adjustment are no longer met, and can serve as trigger conditions for lossy adjustment.

[0059] Exemplarily, the first bandwidth adjustment information can be encapsulated in the overhead of the service layer signal. The current node receives the service layer signal from the upstream node, and then parses the first bandwidth adjustment information from the overhead of the service layer signal, and then adjusts the bandwidth of the target service according to the first bandwidth adjustment information.

[0060] Exemplarily, the first bandwidth adjustment information may include a bandwidth adjustment type, which includes bandwidth increase and bandwidth decrease. If the bandwidth adjustment type is bandwidth increase, the time slot mapped to the target service needs to be increased; if the bandwidth adjustment type is bandwidth decrease, the time slot mapped to the target service needs to be decreased. The first bandwidth adjustment information may also include the time slot number to be adjusted. The current node performs the adjustment operation corresponding to the bandwidth adjustment type on the time slot corresponding to the time slot number to be adjusted.

[0061] For example, the time slots currently mapped to the target service include time slots 1, 5, and 6. The bandwidth adjustment type currently required is to increase the bandwidth, and the time slot number to be adjusted is 7. Then, time slot 7 is added to the time slot mapped to the target service. After that, the client signal of the target service will be mapped to the branch time slots numbered 1, 5, 6, and 7 in the service layer signal, thereby achieving the purpose of increasing the bandwidth of the target service.

[0062] For another example, the time slots currently mapped to the target service include time slots 1, 5, and 6. The bandwidth adjustment type currently required is to reduce the bandwidth, and the time slot number to be adjusted is 1. Then, time slot 1 is deleted from the time slots mapped to the target service. After that, the client signal of the target service will be mapped to the branch time slots numbered 5 and 6 in the service layer signal, thereby achieving the purpose of reducing the bandwidth of the target service.

[0063] It should be noted that, in some descriptions of the embodiments of the present application, the first bandwidth adjustment information may also be referred to as a bandwidth adjustment request, or as a high-order bandwidth adjustment message.

[0064] According to the solution of the embodiment of the present application, when an alarm message appears in the channel, the conditions for lossless bandwidth adjustment cannot be met, and when the nodes in the channel receive the first bandwidth adjustment message, the nodes in the channel initiate a lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment message. For nodes that cannot receive the first bandwidth adjustment message due to an abnormal situation, they can receive the first bandwidth adjustment message after the abnormal situation is eliminated, and initiate a lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment message, thereby completing the overall bandwidth adjustment of the target service in the channel, and achieving the purpose of quickly restoring the service after the abnormal situation is eliminated to minimize losses. The embodiment of the present application does not have to wait for the host node to transmit the bandwidth adjustment response message upstream and receive the bandwidth adjustment response message at the source node like the traditional lossless bandwidth adjustment process before completing the bandwidth adjustment operation. This will consume a lot of time and is not conducive to the service returning to normal as soon as possible.

[0065] Exemplarily, the lossy bandwidth adjustment operation includes directly performing a lossy configuration adjustment of the time slot mapping parameters corresponding to the target service locally based on the time slot number to be adjusted. The time slot mapping parameters may include the time slot number mapped to the target service. In a specific implementation, the current node may modify the time slot number information locally mapped to the target node based on the first bandwidth adjustment information.

[0066] In the embodiment of the present application, after performing the lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information, the following steps may be further included:

[0067] Step S102: Send second bandwidth adjustment information to the upstream node, where the second bandwidth adjustment information includes at least one of the following: bandwidth adjustment response information and an adjusted time slot number.

[0068] In the embodiment of the present application, the second bandwidth adjustment information is used by the current node to feed back to the upstream node the result of bandwidth adjustment performed according to the first bandwidth adjustment information.

[0069] It should be noted that, in some descriptions of the embodiments of the present application, the second bandwidth adjustment information may also be referred to as a bandwidth adjustment response message.

[0070] Exemplarily, the second bandwidth adjustment information may be located in the overhead of the service layer signal, and the bandwidth adjustment response information may be indicated as a lossy bandwidth adjustment response result through the first field value or as a lossless bandwidth adjustment response result through the second field value. For example, the bandwidth adjustment response information corresponding to the time slot may be indicated by a specific bit in the overhead. If the value of the bit is 01, it indicates that lossless bandwidth adjustment has been completed for the corresponding time slot; if the value of the bit is 11, it indicates that lossy bandwidth adjustment has been completed for the corresponding time slot.

[0071] It should be noted that the first bandwidth adjustment information and the second bandwidth adjustment information described in the embodiment of the present application can both be carried by a multiframe composed of a series of service layer signal frames. Specifically, the multiframe contains n service layer signal frames, and the overhead of each service layer signal frame corresponds to the bandwidth adjustment information of a time slot, so n service layer signal frames correspond to the bandwidth adjustment information of n time slots. The bandwidth adjustment information and bandwidth adjustment response information corresponding to the time slot number are indicated by dividing specific bit positions in the overhead of a service layer signal frame.

[0072] The embodiment of the present application may further include the following steps:

[0073] Step S103: Send the first bandwidth adjustment information to a downstream node according to the first bandwidth adjustment information;

[0074] Step S104: Receive second bandwidth adjustment information returned by the downstream node according to the first bandwidth adjustment information, where the second bandwidth adjustment information includes at least one of the following: bandwidth adjustment response information and an adjustment time slot number.

[0075] Exemplarily, the current node forwards the first bandwidth adjustment information to the downstream node so that the adjacent downstream node also performs lossy bandwidth adjustment on the target service according to the first bandwidth adjustment information, and sends the second bandwidth adjustment information to the current node after completing the lossy bandwidth adjustment, so that the current node knows that the adjacent downstream node has completed the bandwidth adjustment of the target service.

[0076] It should be noted that the first bandwidth adjustment information sent by the current node to the downstream node may be the same as the first bandwidth adjustment information received from the upstream node.

[0077] In the embodiment of the present application, after sending the first bandwidth adjustment information to the downstream node, the following steps may also be included:

[0078] When the second bandwidth adjustment information sent by the downstream node is not received, the first bandwidth adjustment information is continuously sent to the downstream node until the second bandwidth adjustment information is received.

[0079] For example, an abnormality occurs in a downstream node adjacent to the current node, resulting in the inability to receive or unable to receive the first bandwidth adjustment information sent by the current node, that is, the adjustment cannot be performed according to the first bandwidth adjustment information sent by the current node; if the current node cannot receive the second bandwidth adjustment information sent by the downstream node, the first bandwidth adjustment information is resent to the downstream node again, and in this way, the first bandwidth adjustment information is continuously sent to the downstream node until the second bandwidth adjustment information sent by the downstream node is received.

[0080] Please refer to Figure 3, which is a flow chart of a bandwidth adjustment method provided by an embodiment of the present application. As shown in Figure 3, the bandwidth adjustment method includes the following steps S201-S207:

[0081] Step S201: A second node sends first bandwidth adjustment information to a first node, wherein the second node is an upstream node of the first node, and the first bandwidth adjustment information is used to instruct bandwidth adjustment for a target service;

[0082] Step S202: The first node detects the alarm information and adjusts the lossy bandwidth of the target service according to the first bandwidth adjustment information;

[0083] Step S203: After successfully performing lossy bandwidth adjustment on the target service, the first node sends second bandwidth adjustment information to the second node, so that the second node no longer sends the first bandwidth adjustment information to the first node.

[0084] Step S204: The first node sends first bandwidth adjustment information to a third node, where the third node is a downstream node of the first node.

[0085] Step S205: The third node does not receive the first bandwidth adjustment information sent by the first node due to an abnormality, and the first node does not receive the second bandwidth adjustment information returned by the first node, and continues to send the first bandwidth adjustment information to the third node;

[0086] Step S206: After the abnormality is resolved, the third node receives the first bandwidth adjustment information sent by the first node, and performs lossy bandwidth adjustment on the target service according to the first bandwidth adjustment information;

[0087] Step S207: After successfully performing lossy bandwidth adjustment on the target service, the third node sends second bandwidth adjustment information to the second node, so that the first node no longer sends the first bandwidth adjustment information to the third node.

[0088] In the embodiment of the present application, performing a lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information includes: performing a unidirectional lossy bandwidth adjustment operation or a bidirectional lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information.

[0089] It can be understood that, for unidirectional lossy bandwidth adjustment, after receiving the first bandwidth adjustment information from the upstream node, the current node performs lossy bandwidth adjustment of the forward service on the target service.

[0090] It can be understood that bidirectional lossy bandwidth adjustment includes lossy bandwidth adjustment for forward and reverse services. That is, after the current node receives the first bandwidth adjustment information from the upstream node, it can simultaneously perform lossy bandwidth adjustment for the forward and reverse services on the target service. This can shorten the bandwidth adjustment time for the bidirectional service and improve the bandwidth adjustment efficiency.

[0091] In a possible embodiment of the present application, when the alarm information is detected, performing the lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information may include the following steps S301-S303:

[0092] Step S301: receiving first bandwidth adjustment information from an upstream node;

[0093] Step S302: When the alarm information is not detected, a lossless bandwidth adjustment operation is performed on the target service according to the first bandwidth adjustment information;

[0094] Step S303: When the alarm information is detected during the execution of the lossless bandwidth adjustment operation, the lossless bandwidth adjustment operation is terminated, and a lossy bandwidth adjustment operation is performed on the target service according to the first bandwidth adjustment information.

[0095] It is understandable that after the current node receives the first bandwidth adjustment information from the upstream node, if the alarm information is not detected, a lossless bandwidth adjustment operation is performed on the target service; if an alarm information is detected during the lossless bandwidth adjustment operation, the lossless bandwidth adjustment operation is switched to a lossy bandwidth adjustment operation to minimize the impact of the channel abnormality on the service bandwidth adjustment and reduce service losses.

[0096] In a possible embodiment of the present application, when the alarm information is detected, performing the lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information may include the following steps S401-S402:

[0097] Step S401: After detecting the alarm information, receiving the first bandwidth adjustment information from an upstream node;

[0098] Step S402: Perform a lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information.

[0099] It can be understood that when the current node receives the first bandwidth adjustment information from the upstream node after detecting the alarm information, the current node directly performs a lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information to minimize the impact of the abnormality on the service bandwidth adjustment and reduce service losses.

[0100] In a possible embodiment of the present application, the first bandwidth adjustment information further includes a bandwidth adjustment identifier BWR_IND, the target service is a fine-grained optical transport network (fgOTN) service, and the method further includes:

[0101] When the alarm information is not detected, starting from detecting that the BWR_IND is the first indication value, after a preset number of service layer bytes have passed, a lossless bandwidth adjustment operation is performed on the target service according to the first bandwidth adjustment information.

[0102] Exemplarily, an embodiment of the present application also provides a lossless bandwidth adjustment mechanism for a flexible rate fine-grained ODU (fgODUflex). In fgOTN, when a node detects that the value of BWR_IND changes from 0 to 1, it starts with the service layer byte block (16-byte block) at which the value of BWR_IND changes from 0 to 1, and counts 118 service layer byte blocks in the fine-grained optical channel data tributary unit (fgODTU) used to carry the fgODUflex service. After this position, the number of time slots of the fgODTU is switched to complete the bandwidth adjustment of the fgODUflex. The above scheme provides a method for determining the position of the fgODTU after the fgODUflex rate changes.

[0103] It should be noted that the transmission channel of the target service includes a working channel and a protection channel. The embodiment of the present application is applied to the first node in the OTN, where the first node can be any node in the protection channel.

[0104] It is understandable that, when the working channel is normal and the protection channel is abnormal, the working channel performs the lossless bandwidth adjustment operation of the target service, and the protection channel performs the lossy bandwidth adjustment operation of the target service. This can avoid the situation where once an abnormality occurs in the working channel and it is necessary to switch to the protection channel to transmit the target service, the protection channel fails to adjust the bandwidth of the target service in time due to the abnormality, causing losses to the target service.

[0105] For example, in a link failure scenario, the current node detects an alarm and receives a first bandwidth adjustment message from an upstream node. It then forwards the first bandwidth adjustment message to the downstream node. The current node initiates lossy bandwidth adjustment on its own. After completing the lossy bandwidth adjustment, it sends a second bandwidth adjustment message to the upstream node, indicating the completion of the lossy bandwidth adjustment. Upon receiving the second bandwidth adjustment message, the upstream node stops sending the first bandwidth adjustment message to itself. Upon failing to detect the first bandwidth adjustment message, the current node stops sending the second bandwidth adjustment message to the upstream node, completing the lossy bandwidth adjustment between the upstream node and the current node. The upstream node continues sending bandwidth adjustment messages to the current node until it receives the second bandwidth adjustment message from the current node. Similarly, the current node continues sending the first bandwidth adjustment message to the downstream node through the same process. After receiving the second bandwidth adjustment message from the downstream node, the current node stops sending the first bandwidth adjustment message to the downstream node. Following the above process, lossy adjustment can be completed on all links except for the link where the message is unreachable due to the failed link. The first bandwidth adjustment message can include the bandwidth adjustment type and the number and sequence of the adjusted time slots, carried and indicated via the bandwidth adjustment overhead of the higher-order service layer.

[0106] In the embodiment of the present application, when an alarm is detected, lossy bandwidth adjustment is performed to quickly complete the bandwidth adjustment operation and avoid further service damage. This lossy bandwidth adjustment includes at least one of the following: unidirectional lossy adjustment and bidirectional lossy adjustment. Based on the alarm indication signal and bandwidth adjustment overhead, adjustment information is exchanged and bandwidth adjustment processing is performed between adjacent nodes to complete the lossy bandwidth adjustment process. In the embodiment of the present application, each link performs lossy bandwidth adjustment independently, without any mutual influence or correlation.

[0107] It should be noted that, based on existing protocols, lossless bandwidth adjustments are unidirectional and initiated by the upstream node. However, in the embodiment of the present application, due to the link failure, the node does not care whether the bandwidth adjustment is initiated by endpoint A or endpoint Z; as long as a bandwidth adjustment request is received, the node will perform a bidirectional bandwidth adjustment.

[0108] It should be noted that the execution effects are different depending on whether one-way lossy bandwidth adjustment or two-way lossy bandwidth adjustment is performed. Considering that the one-way lossless adjustment protocol of the service needs to be independently initiated from the two endpoints A and Z respectively, when a single point failure occurs in the service (forward, reverse, bidirectional), all nodes can still receive the adjustment message from endpoint A or endpoint Z, and can also monitor the alarm information. Therefore, all nodes can perform lossy adjustment according to the trigger conditions. When there are multiple point failures in the service, some nodes will not be able to complete the lossy bandwidth adjustment because the adjustment information is unreachable. Adjacent nodes need to maintain the lossy adjustment state and wait for the service to recover. After the message is reachable, the lossy bandwidth adjustment of the link between the unreachable nodes will be performed. Due to the service failure itself, the lossy bandwidth adjustment will not introduce more service damage. Since all nodes are coordinated to maintain the same status, it can shorten the time for the service to return to normal.

[0109] The solutions of the embodiments of the present application are described below through specific examples.

[0110] Example 1: Bandwidth Adjustment in Fault Scenario

[0111] The embodiments of this application are applicable to scenarios where the working channel is normal and the protection channel is faulty, or scenarios where both the working channel and the protection channel are faulty. The embodiments of this application use the existing lossless processing flow for normal channels to maintain compatibility, and adopt special processing for faulty channels. The specific process is as follows:

[0112] The first node receives a forward high-order bandwidth adjustment message (see the LCR protocol) from the second node (upstream node) and also receives forward / reverse service alarm information, indicating that the service has failed and the normal lossless bandwidth adjustment process can no longer be implemented. Therefore, special processing is performed. The first node directly performs lossy bandwidth adjustment based on the forward high-order bandwidth adjustment message, initiates the high-order lossy adjustment protocol on the downstream line port, passes the forward high-order bandwidth adjustment message to the third node (downstream node), and forwards it hop by hop, ultimately completing the bandwidth adjustment operation for the entire service. In the event of a single point of failure in the service, performing bidirectional lossy bandwidth adjustment can complete the adjustment of all nodes. Performing unidirectional lossy bandwidth adjustment requires that all faults disappear before the adjustment of all nodes is completed. Users can choose the appropriate adjustment method according to their needs.

[0113] After performing lossy bandwidth adjustment, low-order services may be interrupted. Information can only be transmitted via high-order bandwidth adjustment messages. To resolve state inconsistencies caused by message unreachability, nodes that failed to complete the adjustment must maintain the adjustment state. This ensures that overall service status remains consistent after the fault is resolved. If the LCR protocol for lossy bandwidth adjustment succeeds, the adjustment state is exited. If the LCR protocol for lossy bandwidth adjustment fails, high-order bandwidth adjustment messages are continuously sent to maintain the adjustment state.

[0114] After receiving the high-order bandwidth adjustment message and completing the lossy bandwidth adjustment, the downstream node sends a high-order adjustment protocol (LCR) segment layer response message (such as TSGS information for fgOTN services) to notify the upstream node that the bandwidth adjustment for this segment is complete.

[0115] If the failure affecting the transmission of service bandwidth adjustment messages is resolved, the downstream node that previously failed the high-level adjustment protocol (LCR) can receive and execute the high-level adjustment protocol because the service has recovered. It can continue to perform lossy adjustment and complete the previously unfinished service bandwidth adjustment process. This ensures the consistency of the overall service status.

[0116] For OSU or fgOTN client layer signals, the lossless bandwidth adjustment protocol initiated from a single source end performs adjustment processing on the service in one direction. Therefore, if bidirectional bandwidth adjustment is required, the adjustment protocol needs to be initiated at both bidirectional source ends.

[0117] In some cases, when performing bidirectional lossy bandwidth adjustment, the nodes on both sides of the link to be adjusted may initiate a high-level adjustment protocol for lossy adjustment. After the other end receives it, because the adjustment bandwidth requested by both sides is the same, the bidirectional adjustment requirements are also consistent, and it can be processed normally.

[0118] In some cases, during the lossless bandwidth adjustment process, if the adjustment process is not completed and an alarm is detected while waiting for the status update (it may be an alarm caused by a line failure or an alarm caused by inconsistency between the upstream adjusted service and the local configuration), the exception handling process is directly entered, that is, it is directly switched to executing lossy bandwidth adjustment.

[0119] The High-Level Regulation (LCR) protocol here follows the same high-order link negotiation protocol used for lossless adjustment of ODU and fgOTN services. This protocol uses bandwidth adjustment control protocol content transmitted over high-order links. As the service layer for low-order services, the high-order link acts as a conduit, ensuring normal operation. Protocol message transmission is unaffected by the status of the low-order services undergoing bandwidth adjustment. The specific protocol content is reused or improved upon the existing LCR protocol. For OSU services, where LCR negotiation is unnecessary, similar functionality can be implemented using OAM frames.

[0120] Example 2: Bandwidth adjustment in resource-scarce scenarios

[0121] If resources are insufficient on a certain section of the protection channel, existing technical requirements dictate that both the working and protection channels must be operational before lossless bandwidth adjustment can be performed. This process is complex. Without restrictions and verification of the service status of the protection channel, it is possible that the working channel can be adjusted, but the protection channel cannot due to insufficient bandwidth.

[0122] When the working channel completes the bandwidth adjustment, the service rate is changed, but the protection channel cannot complete the bandwidth adjustment, and the rate remains in the previous state. Therefore, the protection channel will generate an alarm due to the mismatch of the service rate. According to the solution of the embodiment of the present application, when the alarm is generated, the protection channel will automatically perform lossy adjustment. Lossy adjustment can be performed for segments with sufficient bandwidth resources, but segments with insufficient resources cannot be adjusted, and the alarm can be reported to the management and control equipment. At the same time, since the high-order adjustment protocol (LCR) is not successfully executed in the segment with insufficient resources, the high-order adjustment protocol (LCR) adjustment state is maintained, and the adjustment is performed after the resources are released and sufficient bandwidth is available.

[0123] In specific implementation, the compatibility of old and new functions can be achieved through a function switch. For example, for a protection node that can receive both working channel information and protection channel information, the function switch can be used to choose whether to wait for confirmation of the normal state of the protection channel or not to wait for confirmation of the normal state of the protection channel. If you choose to wait for confirmation of the normal state of the protection channel, then according to the traditional process, when the protection channel state is abnormal, the high-order adjustment protocol (LCR) fails to execute, but lossy adjustment will not be triggered. If you choose not to wait for confirmation of the normal state of the protection channel, then according to the solution of the embodiment of the present application, the working channel performs lossless adjustment normally, the protection channel performs lossless adjustment before the alarm is detected, and performs lossy adjustment after the alarm is detected. After the alarm is eliminated, the bandwidth adjustment of all nodes in the channel can be quickly completed, reducing the business loss caused by the alarm.

[0124] Example 3: Bandwidth adjustment in protocol abnormality scenarios

[0125] If the lossless adjustment protocol cannot be processed normally for some reason, it will have a timeout rollback mechanism to ensure that the business can be restored.

[0126] Therefore, it is possible to consider the problem of a protection channel node being unable to process the protocol normally, resulting in a protocol anomaly and inability to complete bandwidth adjustment. According to the solution of the embodiment of the present application, this problem can also be solved. For example, after other normal nodes perform lossless bandwidth adjustment, an alarm is generated due to bandwidth mismatch, triggering the execution of lossy adjustment. The link between the abnormal node and the adjacent node cannot process the protocol normally, leaving the high-level adjustment protocol (LCR) in an incomplete state, and an alarm is reported, prompting the user to handle it.

[0127] Example 4: Bandwidth Adjustment for Single-Point Failure Scenario of Protection Channel

[0128] Please refer to Figure 4, which is a schematic diagram of a single-point failure scenario of a protection channel provided by an embodiment of the present application. When the working channel completes the lossless adjustment normally, the protection channel cannot complete the lossless adjustment protocol due to a fault. When the working channel completes the lossless adjustment and switches to the new service rate, a service alarm for the protection channel will be triggered. The protection channel node performs bidirectional lossy adjustment based on the received adjustment request (carrying the first bandwidth adjustment information) and the received service alarm. Since there is only a single point of failure, all nodes can receive the adjustment protocol initiated from both ends, and the nodes at both ends of the fault-free link can complete the lossy adjustment and return to normal processing status. However, the nodes at both ends of the faulty link cannot complete the high-order adjustment protocol, are in a waiting state, and continue to send adjustment requests. When the fault disappears, the link protocol where the fault occurs can communicate with each other, but because the rate adjustment is not completed, there is still a service alarm, which can trigger the execution of lossy adjustment. After the lossy adjustment is completed, all nodes and the overall service return to normal.

[0129] Example 5: Bandwidth Adjustment for Multiple Failures in Protection Channels

[0130] Please refer to Figure 5, which is a schematic diagram of a multi-point failure scenario for a protection channel according to an embodiment of the present application. In the event of multiple failures in the protection channel, some nodes may not receive bandwidth adjustment requests and thus be unable to complete lossy adjustments. However, neighboring nodes will continue to send bandwidth adjustment requests. As service recovers, these nodes can perform lossy adjustments upon receiving these requests. Once the failures disappear, service returns to normal.

[0131] In the event of a fault, the neighboring node continues to send adjustment requests, but cannot receive a response from the other end, and cannot complete the adjustment. The adjustment request state continues to be sent. The relevant processing states for unidirectional and bidirectional faults are similar and are not described separately here.

[0132] Similar to the principle of performing one-way lossy adjustment upon receiving an alarm, after completing the adjustment in one direction, the other direction must wait for the adjustment request in the other direction to be processed. Therefore, in a fault scenario, it is necessary to wait for the fault to recover before completing the adjustment of all nodes. Effectively, bidirectional lossy adjustment is simpler to operate because it performs service adjustments in both directions at once, allowing for faster service recovery.

[0133] Example 6: Bandwidth adjustment in scenarios with insufficient protection channel resources

[0134] When a section of the protection channel has insufficient resources and cannot complete lossless bandwidth adjustment, the processing scenario is consistent with the business failure scenario. Due to insufficient resources, the relevant links cannot complete the adjustment. The nodes on both sides continue to send adjustment requests and notify the control of the abnormal situation. After the resource coordination is completed, the adjustment is successful and the normal state is restored.

[0135] Example 7: Alarm occurs during lossless adjustment of a service without protection

[0136] Please refer to Figure 6, which is a schematic diagram of a business scenario without protection provided by an embodiment of the present application. For businesses without protection, the bandwidth adjustment solution provided by the embodiment of the present application can also be supported, and the overall business bandwidth adjustment is completed through lossy adjustment operations.

[0137] For management and control, issuing a single adjustment command for the entire service generally results in a guaranteed adjustment result, regardless of whether the service's current alarm status is normal. This simplifies the judgment and exception handling of operations issued at the management and control level, avoiding issues with coordination between management and various network elements in abnormal scenarios. This achieves a certain degree of decoupling, simplifies business processes, and facilitates overall implementation.

[0138] The following describes the improvements to the lossless bandwidth adjustment protocol according to the embodiments of the present application.

[0139] Please refer to Figure 7, which is a schematic diagram of the fgOTN overhead provided by an embodiment of the present application. As shown in Figure 7, for fgOTN services, the CTRL field in the existing high-order overhead can be reused to send a bandwidth adjustment request (i.e., the first bandwidth adjustment information), and the TSGS in the existing high-order overhead can be reused to respond to the single-hop bandwidth adjustment result (i.e., the second bandwidth adjustment information). The newly defined overhead field value indicates that the lossy adjustment is completed, which is distinguished from the existing lossless adjustment. For example, based on the TSGS modification, the previously reserved value of 11 can be used as a response message for the lossy adjustment. There is no need to wait for the BWR adjustment. After the adjustment of this section is successful, the adjustment state can be exited. Other methods can also be used to interact with information to complete the protocol interaction. The specific interaction form is not limited.

[0140] During the lossless adjustment process, the BWR protocol is used to notify all nodes to perform a unified lossless switch. Currently, this is indicated by the BWR_IND overhead changing from 0 to 1, triggering the switching of the number of timeslots at the desired specific position in the frame structure.

[0141] An embodiment of the present application provides a lossless bandwidth adjustment mechanism for fgODUflex. After detecting that the value of BWR_IND changes from 0 to 1, a method for determining the position of the fgODTU after the fgODUflex rate changes is as follows: starting from the 16-byte block where the value of BWR_IND changes from 0 to 1, the 16-byte blocks used to carry the fgODUflex service in 118 fgODTUs are counted, and the number of timeslots of the fgODTU is switched after this position.

[0142] Because BWR_IND is a low-level overhead, there's a delay between the specific location of high-level timeslot adjustments and the processing. This approach uses a simple counting and fixed delay, simplifying the process. Previous solutions required complex calculations to determine the location. Simply put, after detecting the overhead and counting a fixed number of code blocks, rate switching is performed, eliminating the need for complex location calculations.

[0143] If an alarm occurs before triggering the lossless adjustment timeslot switch, it is considered that the lossless operation cannot be completed and lossy switching is performed. After the lossless bandwidth adjustment timeslot switch has been executed, the bandwidth lossless adjustment has been completed and no further lossy adjustment is required.

[0144] Please refer to Figure 8, which is a schematic diagram of the ODU lossless overhead provided by an embodiment of the present application. As shown in Figure 8, similar to the fgOTN solution, the ODU lossless adjustment overhead definition can use CTRL to initiate a high-order LCR adjustment request. The RES byte can be used to add a new overhead value to indicate the completion of forced lossy adjustment. In the case of lossy adjustment, there is no need to wait for BWR adjustment; the adjustment state can be exited after the current segment adjustment is successful. Other methods of information exchange can also be used to complete the protocol interaction, and the specific interaction form is not limited.

[0145] Please refer to Figure 9, which shows a schematic diagram of the OAM frame format for OSU services provided in an embodiment of the present application. OSU lossless adjustment does not have distinct LCR and BWR processes, and specifies a method for exiting adjustment in the event of a failure. However, this solution can be made compatible with the present application by adding a function switch. This function switch can be used to determine whether, in the event of a failure during adjustment, adjustment is exited and restored to the unadjusted state, or lossy adjustment is performed directly to the target bandwidth.

[0146] As shown in Figure 9, when performing lossy adjustment, existing OAM frames can be expanded to complete link adjustment negotiation hop by hop and pass it on to the next hop. For example, in the OAM function definition area, the BW_ADJ_ACK value can be expanded, and a new protocol message type for lossy adjustment completion acknowledgement can be added. If a failure or other reason prevents the adjustment from being completed on the current hop, the adjustment protocol will continue to be sent.

[0147] The embodiment of the present application further provides an electronic device, as shown in FIG10 , wherein the electronic device 1400 includes:

[0148] one or more processors 1410;

[0149] The memory 1420 stores one or more programs. When the one or more programs are executed by the one or more processors 1410 , the one or more processors 1410 implement the bandwidth adjustment method described in any of the above embodiments.

[0150] The memory 1420 is a non-transient network system that can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory 1420 may include a high-speed random access memory and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory 1420 may optionally include a memory 1420 remotely located relative to the processor 1410, and these remote memories 1420 may be connected to the processor 1410 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0151] The memory 1420 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1420 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1420 and is called by the processor 1410 to execute the methods of the embodiments of this application.

[0152] The processor 1410 can be implemented using a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in any of the above embodiments.

[0153] In some embodiments, the electronic device further comprises:

[0154] Input / output interface, used to realize information input and output;

[0155] Communication interface, used to realize communication interaction between this device and other devices, which can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, Wi-Fi, Bluetooth, etc.);

[0156] A bus that transmits information between various components of the device (e.g., the processor 1410, memory 1420, input / output interfaces, and communication interfaces);

[0157] The processor 1410 , the memory 1420 , the input / output interface, and the communication interface can be communicatively connected to each other within the device via a bus.

[0158] An embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the bandwidth adjustment method described in any of the above embodiments.

[0159] An embodiment of the present application further provides a computer program product, including a computer program or computer instructions, which are stored in a computer-readable storage medium. A processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium, and the processor executes the computer program or computer instructions, so that the computer device implements the bandwidth adjustment method described in any of the above embodiments.

[0160] The system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of the system architecture and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

[0161] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0162] Those skilled in the art will appreciate that all or some of the steps and systems in the method disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, and the computer-readable medium can include computer storage media (or non-transitory media) and communication media (or temporary media). As known to those skilled in the art, the term computer storage media is included in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data) and is volatile and non-volatile, removable, and non-removable. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, digital versatile disks (DVD), or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage, or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0163] The above description of some embodiments of the present application with reference to the accompanying drawings does not limit the scope of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and essence of the present application shall be within the scope of the present application.

Claims

1. A bandwidth adjustment method, the method comprising: In case of detecting an alarm message, performing a lossy bandwidth adjustment operation on a target service according to first bandwidth adjustment information, the first bandwidth adjustment information including at least one of the following: bandwidth adjustment type, slot number to be adjusted.

2. The method according to claim 1, wherein After performing the lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information, the method further comprises: Sending second bandwidth adjustment information to an upstream node, the second bandwidth adjustment information including at least one of the following: bandwidth adjustment response information, adjusted slot number.

3. The method according to claim 2, wherein, The second bandwidth adjustment information is located in the overhead of the service layer signal, and the bandwidth adjustment response information is represented as a lossy bandwidth adjustment response result by a first field value or as a lossless bandwidth adjustment response result by a second field value.

4. The method according to claim 1, wherein The method further comprises: Sending the first bandwidth adjustment information to a downstream node according to the first bandwidth adjustment information; Receiving second bandwidth adjustment information returned by the downstream node according to the first bandwidth adjustment information, the second bandwidth adjustment information including at least one of the following: bandwidth adjustment response information, adjusted slot number.

5. The method according to claim 4, wherein, After sending the first bandwidth adjustment information to the downstream node, the method further comprises: When the second bandwidth adjustment information sent by the downstream node is not received, continuously sending the first bandwidth adjustment information to the downstream node until the second bandwidth adjustment information is received.

6. The method according to claim 1, wherein, Performing the lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information includes: Performing a unidirectional lossy bandwidth adjustment operation or a bidirectional lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information.

7. The method according to claim 1, wherein, In case of detecting an alarm message, performing a lossy bandwidth adjustment operation on a target service according to first bandwidth adjustment information includes: Receiving the first bandwidth adjustment information from an upstream node; When the alarm message is not detected, performing a lossless bandwidth adjustment operation on the target service according to the first bandwidth adjustment information; When the alarm message is detected during the execution of the lossless bandwidth adjustment operation, terminating the execution of the lossless bandwidth adjustment operation and performing a lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information.

8. The method according to claim 1, wherein, In case of detecting an alarm message, performing a lossy bandwidth adjustment operation on a target service according to first bandwidth adjustment information includes: After detecting the alarm message, receiving the first bandwidth adjustment information from an upstream node; Performing a lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information.

9. The method according to claim 1, wherein The alarm message includes a forward service alarm message and a reverse service alarm message.

10. The method according to claim 1, wherein, The alarm message includes at least one of the following: loss of signal LOS alarm message, loss of frame LOF alarm message, loss of multiple frame LOM alarm message, alarm indication signal AIS, disconnect indication signal OCI, lock indication signal LCK, backward defect indication BDI alarm message.

11. The method according to claim 1, wherein, The first bandwidth adjustment information further includes a bandwidth adjustment identifier BWR_IND, the target service is a fine-grained optical transport network fgOTN service, and the method further comprises: When the alarm information is not detected, starting from detecting that the BWR_IND is the first indication value, after a preset number of service layer bytes, a lossless bandwidth adjustment operation is performed on the target service according to the first bandwidth adjustment information.

12. The method according to claim 1, wherein The lossy bandwidth adjustment operation includes: directly performing a lossy configuration adjustment on the slot mapping parameter corresponding to the target service locally according to the slot number to be adjusted.

13. The method according to claim 1, wherein The transmission channel of the target service includes a working channel and a protection channel, and the method is applied to a first node, and the first node is a node in the protection channel.

14. An electronic device, comprising: One or more processors; A memory having stored thereon one or more programs, which when executed by the one or more processors cause the one or more processors to implement the bandwidth adjustment method according to any one of claims 1-13.

15. A computer-readable storage medium having stored thereon a computer program, which when executed by a processor implements the bandwidth adjustment method according to any one of claims 1-13.

Images