Bandwidth adjustment method, electronic equipment and storage medium

Abstract

The invention provides a bandwidth adjustment method, electronic equipment and a computer readable storage medium, and the bandwidth adjustment method comprises the steps: executing a lossy bandwidth adjustment operation on a target service according to first bandwidth adjustment information under the condition that alarm information is detected, the first bandwidth adjustment information at least comprises one of the following information: a bandwidth adjustment type and a time slot number needing to be adjusted. According to the embodiment of the invention, under the condition that the alarm occurs, the node at the protection channel side starts the lossy bandwidth adjustment for the service, so that the service bandwidth adjustment of the service at the protection channel side can be quickly completed after the alarm is eliminated, and the service loss is reduced as much as possible.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a bandwidth adjustment method, an electronic device, and a storage medium. Background Art

[0002] An important feature of Ethernet services is that the bandwidth will change, which requires the optical transport network (OTN) carrying Ethernet to support the bandwidth adjustment of services and improve the service carrying efficiency. Currently, a lossless bandwidth adjustment technology based on time slot adjustment has been developed for OTN, but there are some limitations. It can only meet the lossless bandwidth adjustment requirements in non-protected scenarios. For OTN in protected scenarios, how to perform service bandwidth adjustment is a technical problem that needs to be solved currently. Summary of the Invention

[0003] Embodiments of this application provide a bandwidth adjustment method, an electronic device, and a computer-readable storage medium for implementing the bandwidth adjustment of OTN services in a protected scenario.

[0004] In a first aspect, embodiments of this application provide a bandwidth adjustment method, and the method includes:

[0005] When an alarm message is detected, perform a lossy bandwidth adjustment operation on a target service according to first bandwidth adjustment information, where the first bandwidth adjustment information includes at least one of the following: bandwidth adjustment type, time slot number to be adjusted.

[0006] In a second aspect, embodiments of this application provide an electronic device, including:

[0007] One or more processors;

[0008] A memory storing one or more programs thereon, when the one or more programs are executed by the one or more processors, enabling the one or more processors to implement the bandwidth adjustment method as described in the first aspect.

[0009] In a third aspect, embodiments of this application provide a computer-readable storage medium storing a computer program thereon, where the computer program, when executed by a processor, implements the bandwidth adjustment method as described in the first aspect.

[0010] An embodiment of the present application provides a bandwidth adjustment method, an electronic device, and a computer-readable storage medium. When an alarm message 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: time slot adjustment type, time slot number to be adjusted. That is, when an alarm occurs, a node on the protection channel side starts a lossy bandwidth adjustment for the service, so that after the alarm is eliminated, the service bandwidth adjustment on the protection channel side can be quickly completed, minimizing losses as much as possible. Description of the Drawings

[0011] The drawings are used to provide a further understanding of the technical solutions 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 solutions of the present application, and do not constitute a limitation to the technical solutions of the present application.

[0012] Figure 1 It is a schematic diagram of an OTN with a protection scenario provided by an embodiment of the present application;

[0013] Figure 2 It is a schematic flowchart of a bandwidth adjustment method provided by an embodiment of the present application;

[0014] Figure 3 It is a schematic flowchart of another bandwidth adjustment method provided by an embodiment of the present application;

[0015] Figure 4 It is a schematic diagram of a single-point failure scenario of a protection channel provided by an embodiment of the present application;

[0016] Figure 5 It is a schematic diagram of a multi-point failure scenario of a protection channel provided by an embodiment of the present application;

[0017] Figure 6 It is a schematic diagram of a service scenario without protection provided by an embodiment of the present application;

[0018] Figure 7 It is a schematic diagram of fgOTN overhead provided by an embodiment of the present application;

[0019] Figure 8 It is a schematic diagram of ODU lossless overhead provided by an embodiment of the present application;

[0020] Figure 9 It is a schematic diagram of the OSU service OAM frame format provided by an embodiment of the present application;

[0021] Figure 10 It is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application. Detailed Embodiments

[0022] To enable those skilled in the art to better understand the technical solution of this application, the technical solution provided by this application will be described in detail below with reference to the accompanying drawings.

[0023] In the following, example embodiments will be described more fully with reference to the accompanying drawings. However, the described example embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. On the contrary, 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.

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

[0025] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit this application. As used herein, the singular forms "a" and "the" are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that when the terms "comprises" and / or "consists of" are used in this specification, it specifies the presence of the features, integers, steps, operations, elements, and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or their groups.

[0026] In the following description, reference is made to "some embodiments", which describe a subset of all possible embodiments. However, it can be understood that "some embodiments" can be the same subset or different subsets of all possible embodiments, and can be combined with each other without conflict.

[0027] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one 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 this application, and will not be interpreted as having an idealized or overly formal meaning unless expressly so defined in the embodiments of this application.

[0028] To facilitate a better understanding of the solution of the embodiments of this application, the related art will be introduced first below.

[0029] The Optical Transport Network (OTN) is a high-capacity and high-speed communication network based on optical fiber transmission. It uses optical technology to convert data into optical signals for transmission in optical fibers and can support large-scale data communication requirements. Based on the OTN frame structure of ITU-T G.709, OTN technology can support the mapping and transparent transmission of various client signals, such as Synchronous Digital Hierarchy (SDH), Asynchronous Transfer Mode (ATM), Ethernet, etc.

[0030] One of the main features of the optical transport network OTN is the hierarchical nature of the network. The optical transport network is divided into multiple network levels, and each level serves as both a service layer and a client layer for each other. Client signals are transmitted between different levels, and each level has its own overhead for detecting the quality of the signals at that level. According to the provisions of 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). Among the above layers, the former is the client layer of the latter, and the latter is the service layer of the former.

[0031] Please refer to Figure 1 , which is a schematic diagram of an OTN with a protection scenario. There are a working channel and a protection channel set between the source node (A end) and the sink node (Z end) of this OTN. 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 transmission of the working channel is interrupted or the performance deteriorates to a certain extent, the system switching device automatically transfers the main signal of the OTN service to the protection channel for transmission, so that the receiving end can still receive normal signals without feeling that the network has an abnormality.

[0032] An important feature of Ethernet services is that the bandwidth will change, which requires the OTN carrying Ethernet to support lossless bandwidth adjustment. Currently, a lossless bandwidth adjustment technology based on time slot adjustment has been developed for OTN, but there are some limitations. It can only meet the lossless bandwidth adjustment requirements of OTN services in non-protected scenarios. For OTN with a protection scenario, there is still no service bandwidth adjustment scheme that fully meets the user's needs.

[0033] On the one hand, adjusting the protocol requires overhead support. In the 1+1 protection scenario, the concurrent selection and reception mechanism is adopted. The sink node selects the services on the working channel, and the services on the protection channel will not be transmitted downstream. Therefore, the overhead content cannot be directly transmitted along with the services. So, it is also necessary to add the processing of terminating and regenerating the overhead, as well as a complex inter-board communication mechanism. To meet the requirements of protection, the overall processing mechanism becomes very complex.

[0034] On the other hand, adjustment takes a certain amount of time. Based on the lossless bandwidth adjustment of the flexible rate optical digital unit (ODUflex), it takes about a minute-level adjustment process. The lossless bandwidth adjustment time based on the fine-grained flexible rate optical digital unit (fgODUflex) is reduced and can be in the second level. However, if an exception occurs to the service during the adjustment process, it will cause the protocol to fail. Currently, there is still a lack of a solution that can quickly restore the service to minimize losses.

[0035] Generally speaking, the lossless adjustment mechanism cannot fully implement the overhead protocol or effectively handle exceptions such as service interruptions. If the configuration of the service is directly modified, it usually causes damage to the service, corresponding to lossy adjustment. By adding special processing related to adjustment to the lossless protocol, the lossless change of the service bandwidth can be achieved, corresponding to lossless adjustment. Relatively speaking, lossy adjustment is more direct, more convenient, and faster, while lossless adjustment has more complex interaction and processing and takes longer.

[0036] In traditional OTN, a lossless bandwidth adjustment mechanism for ODUflex based on packet services (GFP) (Hitless Adjustment of ODUflex(GFP)) is defined. Refer to G.7044 (also known as G.HAO). By defining relevant content in the overhead of high-order and low-order services, the link connection resize (LCR) and bandwidth resize (BWR) protocols are completed to achieve lossless bandwidth adjustment.

[0037] The lossless adjustment mechanism of fgOTN is similar to G.HAO, but it adds the requirement of single-point triggering adjustment at the source node. The per-segment triggering fgLCR adjustment mechanism is used, and the relevant protocol information is forwarded hop by hop using the high-order service layer overhead from the source node to the sink node for the negotiation of the bandwidth adjustment of the entire service.

[0038] In the Optical Service Unit (OSU) standard, there are also some regulations on lossless bandwidth adjustment. For the protected scenario, the adjustment overhead response of both the working and protection channels must be received simultaneously before adjustment can be performed. Due to the characteristics of OSU services, there is no need to separately use the higher-order service layer overhead to transmit the content of the bandwidth adjustment protocol without using a unified OAM frame for processing. Therefore, only the lower-order service carries information, and the overall process will be simpler, and it also supports the requirement of single-point triggering adjustment at the source node.

[0039] Compared with the lossless bandwidth adjustment protocol, for the OTN service bandwidth adjustment in the protected scenario, currently, it is necessary to solve the problem that the protocol of some nodes is unreachable in abnormal situations, and the problem of how the protocol resumes execution after the abnormal situation disappears.

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

[0041] Please refer to Figure 2 , Figure 2 which is a schematic flowchart of a bandwidth adjustment method provided by the embodiments of the present application. As Figure 2 shown, the bandwidth adjustment method includes the following steps:

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

[0043] Among them, the alarm message may include a forward service alarm message and a reverse service alarm message.

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

[0045] The target service described in the embodiments of this application may be a two-way 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 embodiments of this application may be proximal service alarm information, indicating the failure of the service signal upstream of the alarm receiving detection direction; or distal service alarm information, indicating the failure of the service signal in the direction opposite to the alarm detection receiving direction. In the embodiments of this application, any one of the proximal and distal alarm information of the forward-received service and the proximal and distal alarm information of the reverse-received service can trigger a node in the OTN to perform a lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information.

[0046] 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), Out-of-Service Indication (OCI), Lock Indication Signal (LCK), and Backward Defect Indication (BDI) alarm information.

[0047] The meanings of the above various alarm information are as follows:

[0048] (1) LOS (Loss Of Signal) alarm information, that is, signal loss. Usually, when the receiving end cannot detect the signal transmitted by the sending end, the LOS alarm signal appears;

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

[0050] (3) LOM (loss of multiframe) alarm information. When the multiframe alignment byte is incorrect, the LOM alarm signal will appear;

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

[0052] (5) Out-of-Service Indication (OCI), which is transmitted downstream to indicate that the upstream signal is not connected to the path termination source;

[0053] (6) Lock Indication Signal (LCK), which is used to indicate that the upstream signal is in a locked state and no signal can pass through;

[0054] (7) Backward Defect Indication (BDI) alarm information, which is used to indicate the signal failure state detected at the terminal sink function.

[0055] It can be understood that any service alarm occurring in the forward and reverse directions of the protocol initiation direction indicates that the service has been damaged and the lossless adjustment condition is no longer met, and it can be used as a trigger condition for lossy adjustment.

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

[0057] Exemplarily, the first bandwidth adjustment information may include a bandwidth adjustment type, and the bandwidth adjustment type includes increasing bandwidth and decreasing bandwidth types. If the bandwidth adjustment type is increasing bandwidth, then it is necessary to increase the time slots mapped by the target service; if the bandwidth adjustment type is decreasing bandwidth, then it is necessary to decrease the time slots mapped by the target service. The first bandwidth adjustment information may also include the time slot number to be adjusted, and the current node performs an adjustment operation corresponding to the bandwidth adjustment type on the time slot corresponding to the time slot number to be adjusted.

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

[0059] For another example, the time slots currently mapped by the target service include time slots 1, 5, and 6. The current bandwidth adjustment type to be performed is decreasing bandwidth, and the time slot number to be adjusted is 1. Then, time slot 1 is deleted from the time slots mapped by the target service. After that, the client signal of the target service will be mapped to the tributary time slots numbered 5 and 6 in the service layer signal, achieving the purpose of decreasing the bandwidth of the target service.

[0060] 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 may be referred to as a high-order bandwidth adjustment message.

[0061] According to the solution of the embodiment of the present application, when an alarm message appears in the channel, the condition for lossless bandwidth adjustment cannot be met, and when a node in the channel receives the first bandwidth adjustment information, the node in the channel starts a lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information. For a node that cannot receive the first bandwidth adjustment information due to an abnormal situation, it can receive the first bandwidth adjustment information after the abnormal situation is eliminated, and start a lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information, so as to complete the overall bandwidth adjustment of the target service in the channel, 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 sink node to transmit a bandwidth adjustment response message upstream and for the source node to receive the bandwidth adjustment response message to complete the bandwidth adjustment operation as in the traditional lossless bandwidth adjustment process, which will consume a lot of time and is not conducive to the service returning to normal as soon as possible.

[0062] Exemplarily, 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. Among them, the slot mapping parameter may include the slot number mapped by the target service. Specifically, the current node can modify the slot number information mapped by the target node locally according to the first bandwidth adjustment information.

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

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

[0065] In the embodiment of the present application, the second bandwidth adjustment information is used for the current node to feedback the result of bandwidth adjustment according to the first bandwidth adjustment information to the upstream node.

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

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

[0068] It should be noted that both the first bandwidth adjustment information and the second bandwidth adjustment information described in the embodiments of the present application can be carried by a multi-frame composed of a series of service layer signal frames. Specifically, the multi-frame includes n service layer signal frames, and the overhead of each service layer signal frame correspondingly carries the bandwidth adjustment information of one time slot. Therefore, the n service layer signal frames correspond to the bandwidth adjustment information of n time slots. In the overhead of a service layer signal frame, by dividing specific bit positions, the bandwidth adjustment information and the bandwidth adjustment response information corresponding to the time slot number are indicated.

[0069] The embodiments of the present application may further include the following steps:

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

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

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

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

[0074] In the embodiments of the present application, after sending the first bandwidth adjustment information to the downstream node, the following steps may further be included:

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

[0076] Exemplarily, an exception occurs in the downstream node adjacent to the current node, resulting in the inability to receive or the inability 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 re-sent to the downstream node again. 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.

[0077] Please refer to Figure 3 , Figure 3It is a schematic flowchart of a bandwidth adjustment method provided by an embodiment of the present application. As Figure 3 shown, the bandwidth adjustment method includes the following steps S201 - S207:

[0078] Step S201, the second node sends the first bandwidth adjustment information to the first node, where the second node is the upstream node of the first node, and the first bandwidth adjustment information is used to indicate bandwidth adjustment for the target service;

[0079] Step S202, the first node detects the alarm information and performs lossy bandwidth adjustment on the target service according to the first bandwidth adjustment information;

[0080] Step S203, after the first node successfully performs lossy bandwidth adjustment on the target service, it sends the 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;

[0081] Step S204, the first node sends the first bandwidth adjustment information to the third node, where the third node is the downstream node of the first node;

[0082] Step S205, since the third node fails to receive the first bandwidth adjustment information sent by the first node due to an exception, and the first node fails to receive the second bandwidth adjustment information returned by the first node, it continuously sends the first bandwidth adjustment information to the third node;

[0083] Step S206, after the exception is lifted, 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;

[0084] Step S207, after the third node successfully performs lossy bandwidth adjustment on the target service, it sends the 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.

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

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

[0087] It can be understood that the two-way lossy bandwidth adjustment includes the lossy bandwidth adjustment of the forward and reverse services. That is to say, after the current node receives the first bandwidth adjustment information from the upstream node, it can perform the lossy bandwidth adjustment of the forward and reverse services on the target service at the same time, which can shorten the bandwidth adjustment time of the two-way service and improve the bandwidth adjustment efficiency.

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

[0089] Step S301: Receive the first bandwidth adjustment information from the upstream node;

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

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

[0092] It can be understood that after the current node receives the first bandwidth adjustment information from the upstream node, if the alarm information is not detected, the lossless bandwidth adjustment operation is performed on the target service; if the alarm information is detected during the lossless bandwidth adjustment operation, then switch from the lossless bandwidth adjustment operation to the lossy bandwidth adjustment operation to minimize the impact of channel anomalies on the service bandwidth adjustment and reduce the loss of the service.

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

[0094] Step S401: After detecting the alarm information, receive the first bandwidth adjustment information from the upstream node;

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

[0096] It can be understood that when the current node receives the first bandwidth adjustment information from the upstream node in the case of having detected the alarm information, at this time, directly perform the lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information to minimize the impact of anomalies on the service bandwidth adjustment and reduce the loss of the service.

[0097] 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:

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

[0099] Exemplarily, an embodiment of the present application further 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, starting from the service layer byte block (16-byte block) where the value of BWR_IND changes from 0 to 1, count the service layer byte blocks used to carry the fgODUflex service in 118 fine-grained optical channel data tributary units (fgODTUs), and perform a time slot number switch of the fgODTUs after this position to complete the bandwidth adjustment of the fgODUflex. The above solution provides a method for determining the position of the fgODUflex in the fgODTU after the rate change.

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

[0101] It can be understood that when the working channel is normal and the protection channel is abnormal, the working channel performs a lossless bandwidth adjustment operation on the target service, and the protection channel performs a lossy bandwidth adjustment operation on the target service. This can avoid losses to the target service when the working channel suddenly fails and needs to be switched to the protection channel for transmission of the target service, because the bandwidth of the target service was not adjusted in time due to an abnormal reason in the protection channel before.

[0102] For example, in a link failure scenario, the current node detects an alarm message and also receives first bandwidth adjustment information sent by the upstream node. Then, the current node continues to forward the first bandwidth adjustment information to the downstream node. The current node initiates lossy bandwidth adjustment at this node. After completing the lossy bandwidth adjustment, the current node sends second bandwidth adjustment information to the upstream node to indicate the completion of the lossy bandwidth adjustment. After receiving the second bandwidth adjustment information, the upstream node stops sending the first bandwidth adjustment information to this node. After the current node can no longer detect the first bandwidth adjustment information, it stops sending the second bandwidth adjustment information to the upstream node, thus completing the lossy bandwidth adjustment between the upstream node and the current node. Before receiving the second bandwidth adjustment information sent by the current node, the upstream node continuously sends bandwidth adjustment messages to the current node. Similarly, the processing flow for the current node to continue sending the first bandwidth adjustment information to the downstream node is the same. After receiving the second bandwidth adjustment information sent by the downstream node, the current node stops sending the first bandwidth adjustment message to the downstream node. According to the above process, except for the links related to the nodes where messages cannot be reached due to the faulty link, lossy adjustment can be completed for other links. The first bandwidth adjustment information may include the bandwidth adjustment type, as well as the number and serial numbers of the adjusted time slots, and is carried and indicated through the bandwidth adjustment overhead of the high-order service layer.

[0103] The solution of the embodiment of the present application performs lossy bandwidth adjustment when an alarm is detected to quickly complete the bandwidth adjustment operation and avoid more damage to services. The lossy bandwidth adjustment includes at least one of the following: unidirectional lossy adjustment and bidirectional lossy adjustment. Based on the alarm indication signal and the bandwidth adjustment overhead, adjustment information interaction and bandwidth adjustment processing are performed between adjacent nodes to complete the lossy bandwidth adjustment process. In the embodiment of the present application, each link independently performs lossy bandwidth adjustment without mutual influence and association.

[0104] It should be noted that based on the existing protocol, lossless bandwidth adjustment is always a unidirectional adjustment initiated by the upstream node. However, in the embodiment of the present application, due to a 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, a bidirectional bandwidth adjustment is performed.

[0105] It should be noted that, according to different operations of performing unidirectional lossy bandwidth adjustment and bidirectional lossy bandwidth adjustment, the execution effects are also different. Considering that the service unidirectional lossless adjustment protocol needs to be initiated independently from both endpoints A and Z directions, when a single-point failure (forward, reverse, or bidirectional) occurs in the service, all nodes can still receive the adjustment messages 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 multiple-point failures occur in the service, some nodes cannot complete the lossy bandwidth adjustment because the adjustment information is unreachable. Adjacent nodes need to maintain the lossy adjustment state. After the service is restored and the message is reachable, the lossy bandwidth adjustment of the link between the unreachable nodes is 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 state, it can actually shorten the time for the service to return to normal.

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

[0107] Embodiment 1: Bandwidth adjustment for fault scenarios

[0108] The scenarios applicable to the embodiments of the present application include: the scenario where the working channel is normal + the protection channel fails, or the scenario where both the working channel and the protection channel fail. The embodiments of the present application follow the existing lossless processing process for normal channels to maintain compatibility, and adopt special processing for faulty channels. The specific process is as follows:

[0109] The first node receives the forward high-order bandwidth adjustment message (which can refer to the LCR protocol) sent by the second node (upstream node), and also receives the forward / reverse service alarm information, indicating that the service has failed and the normal lossless bandwidth adjustment process can no longer be realized. Therefore, special processing is performed. The first node directly performs lossy bandwidth adjustment according to the forward high-order bandwidth adjustment message, and starts the high-order lossy adjustment protocol at the downstream line port to pass the forward high-order bandwidth adjustment message to the third node (downstream node), forwarding hop by hop, and finally completing the bandwidth adjustment operation of the overall service. In the case of a single-point service failure, performing bidirectional lossy bandwidth adjustment can complete the adjustment of all nodes, and performing unidirectional lossy bandwidth adjustment requires all faults to disappear before all nodes can be adjusted. Users can choose to perform the appropriate adjustment method according to their needs.

[0110] After performing lossy bandwidth adjustment, low-order services may experience interruption, and information can only be transmitted through high-order bandwidth adjustment messages. At the same time, to address the inconsistent state caused by unreachable messages, for nodes that have not been successful, the adjustment state needs to be maintained to ensure that the overall service state can be consistent after troubleshooting. If the LCR protocol for lossy adjustment is successful, the adjustment state is exited. If the LCR protocol for lossy bandwidth adjustment is not successful, high-order bandwidth adjustment messages are continuously sent to maintain the adjustment state.

[0111] After the downstream node receives the high-order bandwidth adjustment message and completes the lossy bandwidth adjustment, it sends an acknowledgment message (such as the TSGS information for the fgOTN service) at the high-order adjustment protocol (LCR) section layer to notify the upstream node that the bandwidth adjustment for this segment is complete.

[0112] If the fault affecting the transmission of service bandwidth adjustment messages is restored, the downstream nodes that previously had an unsuccessful high-order adjustment protocol (LCR) can receive and execute the high-order adjustment protocol due to service restoration, and can continue to perform lossy adjustment to complete the previously unfinished service bandwidth adjustment process. This can ensure the consistency of the overall service state.

[0113] For OSU or fgOTN client layer signals, the lossless bandwidth adjustment protocol initiated from a single point at the source end is for one-way adjustment of the service. Therefore, to perform two-way bandwidth adjustment, adjustment protocols need to be initiated at both two-way source ends to complete.

[0114] In some cases, when performing two-way lossy bandwidth adjustment, the high-order adjustment protocols for lossy adjustment may be initiated by the nodes on both sides of the link to be adjusted. After the peer receives it, because the requested adjustment bandwidth on both sides is the same and the requirements for two-way adjustment are also the same, it can be processed normally.

[0115] 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 state update (which may be an alarm caused by a line fault or an alarm caused by the inconsistency between the service after upstream adjustment and the local configuration), the abnormal handling process is directly entered, that is, directly switched to perform lossy bandwidth adjustment.

[0116] Here, the high-order adjustment protocol (LCR) follows the protocol for high-order link negotiation in the lossless adjustment of ODU and fgOTN services, that is, based on the bandwidth adjustment control protocol content transmitted over the high-order link. The high-order link serves as the service layer for low-order services and acts as a pipeline, which can ensure normal state and that the transmission of protocol messages is not affected by whether the state of the low-order service actually undergoing bandwidth adjustment is normal. The specific protocol content is reused or improved based on the existing LCR protocol. For OSU services, there is no LCR negotiation process, and a similar function can be achieved through OAM frames.

[0117] Embodiment 2: Bandwidth adjustment in a scenario of insufficient resources

[0118] If a certain section of the protection channel has insufficient resources, according to the processing requirements of the existing technology, it is necessary to ensure that both the working channel and the protection channel are normal before performing lossless bandwidth adjustment, but the processing is very complex. If there is no restriction and the service status of the protection channel is not confirmed, it may occur that the working channel can complete the adjustment, but the protection channel cannot complete the adjustment due to insufficient bandwidth.

[0119] When the working channel completes the bandwidth adjustment, the service rate changes, while the protection channel still maintains the previous state because it cannot complete the bandwidth adjustment. 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, for the processing requirements in the case of an alarm, the protection channel will automatically perform lossy adjustment. Lossy adjustment can be performed for sections with sufficient bandwidth resources, but adjustment cannot be performed for sections with insufficient resources, and an alarm can be reported to the management and control device. At the same time, since the high-order adjustment protocol (LCR) of the section with insufficient resources has not been successfully executed, the adjustment state of the high-order adjustment protocol (LCR) is maintained, and the adjustment is performed again after sufficient bandwidth is available after the resource is released.

[0120] In specific implementation, the compatibility of the new and old functions can be achieved through a function switch. For example, for a protection node that can receive both the working channel information and the protection channel information, the function switch can be used to select whether to wait for confirmation of the normal state of the protection channel or not. If it is selected to wait for confirmation of the normal state of the protection channel, then according to the traditional process, when the protection channel status is abnormal, the high-order adjustment protocol (LCR) fails to execute, but no lossy adjustment is triggered. If it is selected 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 can normally perform lossless adjustment, 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 service loss caused by the alarm.

[0121] Embodiment 3: Bandwidth adjustment in a scenario where the protocol is abnormal

[0122] If the lossless adjustment protocol cannot be normally processed due to certain reasons, there is an overtime rollback mechanism itself to ensure that the service can be restored.

[0123] Therefore, it is possible to consider the problem that a certain protection channel node fails to process the protocol normally, resulting in an abnormal protocol and unable to complete the bandwidth adjustment. According to the solution of the embodiment of the present application, the problem can also be solved. For example, after other normal nodes perform lossless bandwidth adjustment, an alarm is triggered due to bandwidth mismatch, and lossy adjustment is triggered to be executed. The link between the abnormal node and the adjacent node cannot process the protocol normally, keeps the high-order adjustment protocol (LCR) in an unfinished state, and reports an alarm to prompt the user to process it.

[0124] Embodiment 4: Bandwidth adjustment in the case of a single-point failure of the protection channel

[0125] Please refer to Figure 4 , Figure 4 , which is a schematic diagram of a single-point failure scenario of the protection channel provided by the embodiment of the present application. When the working channel normally completes lossless adjustment and the protection channel fails to complete the lossless adjustment protocol due to a fault, when the working channel completes lossless adjustment and switches to a new service rate, a service alarm of the protection channel will be triggered. The protection channel node performs two-way lossy adjustment according to the received adjustment request (carrying the first bandwidth adjustment information) and the received service alarm. Since there is only a single-point failure, all nodes can receive the adjustment protocol initiated from both ends. The nodes at both ends of the fault-free link can complete the lossy adjustment and restore the normal processing state. However, the nodes at both ends of the faulty link cannot complete the high-order adjustment protocol and are in a waiting state, continuously sending adjustment requests. When the fault disappears, the protocol of the link where the fault is located can communicate, but because the rate adjustment is not completed, there is still a service alarm, and lossy adjustment can be triggered to be executed. After the lossy adjustment is completed, all nodes and the overall service return to the normal state.

[0126] Embodiment 5: Bandwidth adjustment in the case of multiple-point failures of the protection channel

[0127] Please refer to Figure 5 , Figure 5 , which is a schematic diagram of a multiple-point failure scenario of the protection channel provided by the embodiment of the present application. In the case of multiple faults in the protection channel, some nodes may not receive the bandwidth adjustment request and cannot complete the lossy adjustment, but the adjacent nodes will continuously send the bandwidth adjustment request. As the service resumes, the lossy adjustment can be executed after receiving the request. When the faults disappear one by one, the process of the service returning to normal.

[0128] In the case of a fault, the adjacent nodes continuously send adjustment requests, but cannot receive the response from the opposite end and cannot complete the adjustment, and keep the state of continuously sending adjustment requests. The relevant processing states of single-directional faults and two-way faults are similar and will not be elaborated separately here.

[0129] Similar to the principle of performing unidirectional lossy adjustment when receiving an alarm, a single-direction adjustment is completed, and the other direction needs to wait for the adjustment request of the other direction to be connected. Therefore, in a fault scenario, it is necessary to wait for the fault to be restored to complete the adjustment of all nodes. In terms of effect, because the bidirectional lossy adjustment performs service adjustment processing in two directions at a time, the operation is simpler and the service can return to normal faster.

[0130] Embodiment Six: Bandwidth Adjustment in the Scenario of Insufficient Protection Channel Resources

[0131] When a certain section of the protection channel has insufficient resources and lossless bandwidth adjustment cannot be completed, the processing scenario is the same as the service fault scenario. The relevant links with insufficient resources cannot complete the adjustment. The two sides of the nodes continuously send adjustment requests and notify the management and control of the abnormal situation at the same time. After waiting for the resource coordination to be completed, the adjustment is successful and the normal state is restored.

[0132] Embodiment Seven: An Alarm Occurs during the Lossless Adjustment of a Service without Protection

[0133] Please refer to Figure 6 , Figure 6 , which is a schematic diagram of the service scenario without protection provided by the embodiments of the present application. For a service without protection, the bandwidth adjustment scheme provided by the embodiments of the present application can also be supported, and the overall service bandwidth adjustment is completed through lossy adjustment operations.

[0134] For the management and control, after issuing an adjustment instruction for the entire service once, a definite adjustment result can basically be obtained, without considering whether the current alarm status of the service is normal, and the adjustment can ultimately be completed. This simplifies the determination and exception handling of the issuing operation at the management and control level, avoids the problems of cooperation between the management and control and each network element in abnormal scenarios, realizes a certain degree of decoupling, simplifies the service process, and facilitates the overall implementation.

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

[0136] Please refer to Figure 7 , Figure 7 which is a schematic diagram of the fgOTN overhead provided by the embodiments of the present application. As Figure 7As shown in the figure, for the fgOTN service, the existing CTRL field in the higher-order overhead can be reused to send a bandwidth adjustment request (i.e., the first bandwidth adjustment information), and the existing TSGS in the higher-order overhead can be reused to reply to the single-hop bandwidth adjustment result (i.e., the second bandwidth adjustment information). The value of the newly defined overhead field indicates that the lossy adjustment is completed, which is distinguished from the existing lossless adjustment. For example, based on the modification of TSGS, the previously reserved value of 11 can be used as the reply message for the lossy adjustment. Without waiting for the BWR adjustment, the adjustment state can be exited after the successful adjustment of this paragraph. Other methods can also be used to interact information, as long as the protocol interaction is completed, and the specific interaction form is not limited.

[0137] During the lossless adjustment process, the BWR protocol is used to notify all nodes to perform a unified lossless switch. Currently, it is indicated by the change of the BWR_IND overhead from 0 to 1, triggering the switching of the number of time slots at a specific position expected in the frame structure.

[0138] The 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, the method for determining the position of fgODUflex after the rate change in fgODTU is as follows: starting from the 16-byte block where the value of BWR_IND changes from 0 to 1, count 118 16-byte blocks used to carry the fgODUflex service in fgODTU, and perform the switching of the number of time slots of fgODTU after this position.

[0139] Since BWR_IND belongs to the lower-order overhead, there is a problem of delayed processing with the specific position of the higher-order time slot adjustment operation. Adopting simple counting for fixed-delay processing simplifies the processing flow. The previous scheme required calculating and determining the position, which was relatively complex. Briefly described, it is: after detecting the overhead and counting a fixed number of code blocks, the rate is switched without complex position calculation.

[0140] Before triggering the time slot switch for lossless adjustment, if an alarm occurs, it is considered that the lossless operation cannot be completed, and a lossy switch is performed. After the time slot switch for lossless bandwidth adjustment has been executed, the bandwidth lossless adjustment has been completed, and there is no need to perform lossy adjustment processing anymore.

[0141] Please refer to Figure 8 , Figure 8 which is the schematic diagram of the ODU lossless overhead provided by the embodiment of the present application. As Figure 8As shown, similar to the fgOTN solution, the ODU lossless adjustment overhead is defined. A high-order LCR adjustment request can be initiated using CTRL, and the RES byte can be utilized to add new overhead values to indicate the completion of forced lossy adjustment. In the case of lossy adjustment, there is no need to wait for BWR adjustment, and the adjustment state can be exited after the current segment adjustment is successful. Other methods can also be used to interact information, as long as the protocol interaction is completed, and the specific interaction form is not limited.

[0142] Please refer to Figure 9 , Figure 9 FIG. is a schematic diagram of the OSU service OAM frame format provided by an embodiment of the present application. There is no obvious LCR and BWR process in the OSU lossless adjustment, and it is stipulated to exit the adjustment in case of a fault. However, the solution of the present invention can also be compatible by adding a function switch. According to the function switch, it can be distinguished whether to exit the adjustment and restore to the unadjusted state or directly perform lossy adjustment to the target bandwidth when a fault is encountered during the adjustment process.

[0143] As Figure 9 shown, when actually performing lossy adjustment, it can be extended based on the existing OAM frame, and the adjustment negotiation of the current hop link can be completed hop by hop and passed to the next hop. For example, in the OAM function definition area, the BW_ADJ_ACK value is extended to add a new protocol message type for the acknowledgment of the completion of lossy adjustment. If the adjustment cannot be completed at the current hop due to a fault or other reasons, the adjustment protocol will be continuously sent.

[0144] An embodiment of the present application also provides an electronic device. As Figure 10 shown, the electronic device 1400 includes:

[0145] One or more processors 1410;

[0146] A memory 1420, on which one or more programs are stored. 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.

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

[0148] 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), etc. The memory 1420 can store an operating system and other application programs. When implementing the technical solutions provided in the embodiments of this specification through software or firmware, the relevant program codes are stored in the memory 1420 and are called by the processor 1410 to execute the methods of the embodiments of the present application.

[0149] The processor 1410 can be implemented in ways such as 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.

[0150] In some embodiments, the electronic device further includes:

[0151] An input / output interface for implementing information input and output;

[0152] A communication interface for implementing communication interaction between this device and other devices. Communication can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.);

[0153] A bus for transmitting information between various components of the device (such as the processor 1410, the memory 1420, the input / output interface, and the communication interface);

[0154] Among them, the processor 1410, the memory 1420, the input / output interface, and the communication interface can achieve communication connections with each other inside the device through the bus.

[0155] An embodiment of the present application also provides a computer-readable storage medium storing computer-executable instructions for executing the bandwidth adjustment method described in any of the above embodiments.

[0156] An embodiment of the present application also provides a computer program product including a computer program or computer instructions. The computer program or computer instructions are stored in a computer-readable storage medium. The processor of the 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, causing the computer device to execute the bandwidth adjustment method described in any of the above embodiments.

[0157] The system architecture and application scenarios described in the embodiments of this application are to more clearly illustrate the technical solutions of the embodiments of this application, and do not constitute a limitation to the technical solutions provided by the embodiments of this application. As can be known to those skilled in the art, with the evolution of the system architecture and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are equally applicable to similar technical problems.

[0158] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing 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 methods. Among them, any reference to a memory, storage, database, or other medium used in the embodiments provided in this application can include non-volatile and / or volatile memories. Non-volatile memories can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memories can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.

[0159] Those of ordinary skill in the art will understand that all or some of the steps and systems disclosed in the above methods can be implemented as software, firmware, hardware, and appropriate combinations thereof. Some or all of the 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 can be implemented as hardware, or can be implemented as an integrated circuit, such as an application specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include a computer storage medium (or non-transitory medium) and a communication medium (or transitory medium). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those of ordinary skill in the art that communication media typically includes computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and can include any information delivery medium.

[0160] Some embodiments of the present application have been illustrated above with reference to the accompanying drawings, which do not limit the scope of the present invention. Any modifications, equivalent replacements, and improvements made by those skilled in the art without departing from the scope and essence of the present invention shall fall within the scope of the claims 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, characterized in that, 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, characterized in that 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 The 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, characterized in that, The performing the lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information in case of detecting an alarm message 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 process of performing 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, characterized in that The performing the lossy bandwidth adjustment operation on the target service according to the first bandwidth adjustment information in case of detecting an alarm message 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 multiframe LOM alarm message, alarm indication signal AIS, out-of-service connection indication signal OCI, lock indication signal LCK, backward defect indication BDI alarm message.

11. The method according to claim 1, characterized in that, 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 the detection of the BWR_IND being 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, characterized in that 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