Bandwidth adjustment method and related apparatus

Abstract

The present application relates to the technical field of communications. Disclosed is a bandwidth adjustment method, which can realize the dynamic adjustment of a data-bearing pipeline bandwidth and meet the dynamic change requirements of service scenarios. In the method, a negotiation mechanism for bandwidth adjustment is introduced between two communication apparatuses in a fine granularity metro transport network (fgMTN), the two communication apparatuses negotiate a bandwidth adjustment by means of handshake communication and simultaneously configure a new bandwidth for a data-bearing pipeline at a specific time point, and a new time slot allocation method after the bandwidth of the data-bearing pipeline is adjusted is designated during negotiation, thus ensuring that the data-bearing pipeline can be normally used after the bandwidth thereof is adjusted, and thereby realizing the dynamic adjustment of a data-bearing pipeline bandwidth and meeting the dynamic change requirements of service scenarios.

Description

A bandwidth adjustment method and related apparatus

[0001] This application claims priority to Chinese Patent Application No. 202311666973.4, filed with the State Intellectual Property Office of China on December 5, 2023, entitled "A Bandwidth Adjustment Method and Related Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a bandwidth adjustment method and related apparatus. Background Technology

[0003] Traditional leased network technologies fall into two main categories: packet switching and circuit switching. Packet switching divides the data to be transmitted into many packets of a certain length, each labeled with an address, allowing many different data packets to be transmitted over a shared physical line. Circuit switching, generally based on time-division multiplexing (TDM) technology, interleaves different data into different time periods, transmitting them along the same channel. This allows each user to have dedicated bandwidth resources and provides good isolation.

[0004] Fine Granularity Metro Transport Network (fgMTN) is a network leased line architecture based on circuit switching technology. In fgMTN, the network leased line is divided into multiple large-granularity pipes according to bandwidth, and each large-granularity pipe is used to carry data from one or more small-granularity customers. Generally, the bandwidth of a large-granularity pipe is between 1 gigabyte (G) and 10 G.

[0005] Currently, in fgMTN, the bandwidth of large-granularity pipes is usually configured uniformly by the network management system, making it impossible to dynamically adjust the bandwidth of large-granularity pipes. Summary of the Invention

[0006] This application provides a bandwidth adjustment method that enables dynamic adjustment of the bandwidth of the data carrying pipeline to meet the dynamically changing needs of business scenarios.

[0007] This application provides a bandwidth adjustment method applied to a first communication device in an fgMTN. Specifically, the bandwidth adjustment method includes the following steps: First, the first communication device sends a first request message to a second communication device. The first request message indicates the time slot allocation method after bandwidth adjustment of the first bearer channel. The first bearer channel is the data bearer channel in the fgMTN. The time slot allocation method after bandwidth adjustment of the first bearer channel indicates the correspondence between small-granularity clients using the first bearer channel and the time slots provided after bandwidth adjustment, i.e., indicating which time slots are used to transmit data from the corresponding small-granularity clients. Furthermore, since there is a direct proportional relationship between the bandwidth of the first bearer channel and the total number of time slots, when the time slot allocation method after bandwidth adjustment of the first bearer channel is indicated through the first request message, the adjusted bandwidth of the first bearer channel can also be indicated simultaneously (i.e., the adjusted bandwidth of the first bearer channel can be determined based on the total number of time slots in the time slot allocation method).

[0008] Then, if the second communication device confirms that it supports the time slot allocation method indicated by the first request information, the first communication device receives the first response information sent by the second communication device, which is used to indicate that the second communication device supports the time slot allocation method.

[0009] Secondly, the first communication device sends a second request message to the second communication device, instructing the second communication device to configure the time slot allocation method to take effect at a preset time point. In this way, the first communication device can send data to the second communication device at the preset time point according to the time slot allocation method negotiated between the first and second communication devices and the adjusted bandwidth of the first bearer channel. For example, if the bandwidth of the first bearer channel is increased, the first communication device also needs to increase its data transmission rate when sending data to the second communication device based on the new time slot allocation method, thus ensuring that data is sent to the second communication device based on the adjusted bandwidth of the first bearer channel. The second communication device then receives the data sent by the first communication device at the preset time point according to the time slot allocation method negotiated between the first and second communication devices and the adjusted bandwidth of the first bearer channel, thereby ensuring lossless data transmission between the first and second communication devices through the first bearer channel and avoiding data packet loss due to time slot misalignment.

[0010] In this solution, a bandwidth adjustment negotiation mechanism is introduced between two communication devices in fgMTN. The two communication devices negotiate the bandwidth adjustment through a handshake and simultaneously configure new bandwidth for the data bearer pipeline at a specific time point. During the negotiation process, the new time slot allocation method after the bandwidth of the data bearer pipeline is adjusted is specified to ensure that the data bearer pipeline can be used normally after the bandwidth is adjusted. This enables dynamic adjustment of the bandwidth of the data bearer pipeline and meets the dynamic needs of business scenarios.

[0011] In one possible implementation, the first bearer pipe is a data bearer pipe within the fgMTN network leased line. The network leased line comprises multiple data bearer pipes, and the first bearer pipe is used to carry the service data of one or more small-granularity customers. That is, the first bearer pipe is actually one of several large-granularity pipes divided from the network leased line, capable of carrying the service data of different small-granularity customers.

[0012] In this solution, by dynamically adjusting the bandwidth of the data bearer pipeline in the network leased line, the bandwidth of the data bearer pipeline can change dynamically with the customer's bandwidth demand, thus meeting the dynamically changing needs of the business scenario.

[0013] In one possible implementation, the time slot allocation method specifically includes the correspondence between the small-granularity overhead multiframe indicator (fgOMFI) and the small-granularity customer identifier. The fgOMFI is used to indicate the sequence number of the overhead information after the bandwidth of the first bearer pipe is adjusted. The total number of overhead information in one period after the bandwidth of the first bearer pipe is adjusted is related to the adjusted bandwidth value.

[0014] In one possible implementation, the preset time point is the time point after the first communication device sends the second request information and the fgOMFI corresponding to the first bearer channel is 0. Specifically, since the first communication device carries fgOMFI in the OH field of each frame during the process of sending frames to the second communication device through the first bearer channel, and the value of fgOMFI will continuously poll within a certain range as the number of frames increases (i.e., the first communication device inserts values ​​of fgOMFI within a specific range into the frames in turn), the first communication device can use the time point when fgOMFI is 0 in the frame carried by the first bearer channel as the boundary node to trigger the simultaneous configuration of the time slot allocation method of the two communication devices.

[0015] Alternatively, the preset time point can be the start time of the data plane time slot after the first communication device sends the second request information. Here, a data plane time slot refers to the time slot corresponding to a complete time slot cycle of the data plane. That is, the preset time point can actually be the start time of the Nth time slot cycle after the first communication device sends the second request information, where N is an integer greater than or equal to 1. For example, the preset time point can be the start time of the next time slot cycle after the first communication device sends the second request information. Optionally, in some embodiments, the preset time point can also be the time point where the start of the data frame and the start of the time slot cycle coincide.

[0016] In this scheme, by configuring the negotiated time slot allocation method to take effect at the boundary time of the time slot period, it is possible for both the first and second communication devices to trigger the new time slot allocation method to take effect at the same time node, ensuring that the first and second communication devices can subsequently transmit data based on the new time slot allocation method.

[0017] In one possible implementation, after the bandwidth of the first bearer channel is adjusted, the number of small-granularity clients using the first bearer channel changes. The time slot allocation method after the bandwidth adjustment of the first bearer channel is used to indicate the correspondence between the changed small-granularity clients and the time slots corresponding to the first bearer channel.

[0018] In this solution, during the process of adjusting the bandwidth of the data bearer pipeline, the changes of small-granularity customers in the data bearer pipeline are reflected in the time slot allocation method. This avoids the need for communication devices to negotiate the changes of small-granularity customers in the data bearer pipeline, thereby reducing message overhead between communication devices.

[0019] In one possible implementation, after the bandwidth of the first bearer channel is adjusted, the number of small-granularity customers using the first bearer channel remains unchanged, but the number of time slots corresponding to the target small-granularity customers using the first bearer channel changes. Here, the target small-granularity customers can refer to some or all of the small-granularity customers using the first bearer channel. The change in the number of time slots corresponding to the target small-granularity customers represents a change in the bandwidth corresponding to the target small-granularity customers.

[0020] In this solution, during the process of adjusting the bandwidth of the data bearer pipeline, the bandwidth changes of small-granularity customers in the data bearer pipeline are simultaneously reflected in the time slot allocation method. This avoids the need for communication devices to negotiate the bandwidth adjustment of small-granularity customers in the data bearer pipeline separately, thereby reducing message overhead between communication devices.

[0021] In one possible implementation, the first request information is also used to request the second communication device to adjust the bandwidth of the first bearer channel.

[0022] In other words, the first request information simultaneously instructs the second communication device to adjust the bandwidth of the first bearer channel and the time slot allocation method after the bandwidth adjustment. Thus, when the second communication device receives the first request information and recognizes that it instructs the second communication device to adjust the bandwidth of the first bearer channel, it can confirm that the time slot allocation method indicated in the first request information is actually the time slot allocation method corresponding to the adjusted bandwidth of the first bearer channel.

[0023] In one possible implementation, the first request information indicates a request for the second communication device to adjust the bandwidth of the first bearer channel via a target bit in the overhead (OH) field of the frame. The target bit can be, for example, an existing bit in the frame's overhead field or a reserved bit.

[0024] In this scheme, by using the target bit in the OH field of the frame to indicate the requesting communication device to adjust the bandwidth of the data bearer channel, it is possible to simultaneously indicate the requesting communication device to adjust the bandwidth of the data bearer channel and the time slot allocation method after the bandwidth adjustment in the same request information, thereby improving the communication efficiency between communication devices.

[0025] In one possible implementation, before the first communication device sends a first request message to the second communication device, the method further includes: the first communication device sending a third request message to the second communication device, the third request message being used to request the second communication device to adjust the bandwidth of the first bearer channel; and the first communication device receiving a third response message sent by the second communication device, the third response message being used to instruct the second communication device to support adjusting the bandwidth of the first bearer channel.

[0026] In other words, when the first communication device needs to adjust the bandwidth of the first bearer channel, it first sends a request message to the second communication device to request the second communication device to cooperate in adjusting the bandwidth of the first bearer channel, so as to confirm whether the second communication device can support adjusting the bandwidth of the first bearer channel.

[0027] In one possible implementation, before the first communication device sends the first request information to the second communication device, the first communication device generates a time slot table for the OH plane. The time slot table for the OH plane is used to indicate the time slot corresponding to the first carrier pipeline and the OH information that needs to be transmitted in the time slot corresponding to the first carrier pipeline. The OH information is the information in the OH field of the frame.

[0028] Then, the first communication device transmits OH information to the data plane based on the OH plane's time slot table, enabling the data plane to send a first request message or a second request message in the time slot corresponding to the first bearer channel. That is, when the first communication device sends a frame to the second communication device on the data plane, the first communication device transmits OH information to the data plane based on the OH plane's time slot table. In this way, the data plane can organize the acquired OH information into the content of the OH field of the frame and send it out in the time slot corresponding to the first bearer channel, thereby realizing the transmission of the aforementioned first request message, second request message, or third request message.

[0029] In this solution, based on the time slot table of the OH plane, it is possible to determine which OH information (i.e., the contents of the first request information, the second request information, and the third request information) needs to be transmitted in which time slots (i.e., the time slot corresponding to the first carrier pipeline), thereby ensuring that the time slot table of the data plane does not need to be modified, and ensuring that the business data of small-granular customers can be sent normally.

[0030] In one possible implementation, the first communication device generates a spare time slot table for the data plane based on the time slot allocation method. The spare time slot table for the data plane is used to indicate the time slot distribution of small-granular customers in the first bearer channel after bandwidth adjustment. Furthermore, the first communication device switches the spare time slot table for the data plane to the main time slot table at a preset time point.

[0031] In this solution, by pre-generating a backup time slot table for the data plane and then switching the pre-generated backup time slot table to the primary time slot table at a preset time point, the efficiency of time slot table switching is improved. This ensures that service data is transmitted normally according to the old time slot allocation method before the preset time point and according to the new time slot allocation method after the preset time point, ensuring that the bandwidth adjustment process does not affect the normal transmission of service data.

[0032] A second aspect of this application provides a bandwidth adjustment method applied to a second communication device in an fgMTN, comprising: the second communication device receiving first request information sent by a first communication device, the first request information indicating a time slot allocation method after bandwidth adjustment of a first bearer channel, the time slot allocation method indicating the correspondence between small-granularity clients using the first bearer channel and the time slots provided after bandwidth adjustment of the first bearer channel, the first bearer channel being a data bearer channel in the fgMTN; the second communication device sending first response information to the first communication device, the first response information indicating that the second communication device supports the time slot allocation method; and the second communication device receiving second request information sent by the first communication device, the second request information indicating that the second communication device configures the time slot allocation method to take effect at a preset time point.

[0033] In one possible implementation, the first bearer pipe is a data bearer pipe in the network leased line of fgMTN, the network leased line includes multiple data bearer pipes, and the first bearer pipe is used to carry the business data of one or more small-granularity customers.

[0034] In one possible implementation, the time slot allocation method specifically includes the correspondence between the small-granularity overhead multiframe indicator (fgOMFI) and the small-granularity customer identifier. The fgOMFI is used to indicate the sequence number of the overhead information after the bandwidth of the first bearer pipe is adjusted. The total number of overhead information in one period after the bandwidth of the first bearer pipe is adjusted is related to the adjusted bandwidth value.

[0035] In one possible implementation, the preset time point is the time point after the first communication device sends the second request information and the fgOMFI corresponding to the first bearer pipe is 0; or, the preset time point is the time point at which the next round of data plane time slots begins after the first communication device sends the second request information.

[0036] In one possible implementation, after the bandwidth of the first bearer is adjusted, the small-granularity customers using the first bearer change; the time slot allocation method is used to indicate the correspondence between the changed small-granularity customers and the time slots corresponding to the first bearer.

[0037] In one possible implementation, after the bandwidth of the first bearer is adjusted, the number of time slots corresponding to the target small-granularity customers using the first bearer changes.

[0038] In one possible implementation, the first request information is also used to request the second communication device to adjust the bandwidth of the first bearer channel.

[0039] In one possible implementation, the first request information indicates a request for the second communication device to adjust the bandwidth of the first bearer channel via the target bit in the OH field of the frame.

[0040] In one possible implementation, before the second communication device receives the first request information sent by the first communication device, the second communication device receives the third request information sent by the first communication device, the third request information being used to request the second communication device to adjust the bandwidth of the first bearer channel; the second communication device sends the third response information to the first communication device, the third response information being used to instruct the second communication device to support the adjustment of the bandwidth of the first bearer channel.

[0041] A third aspect of this application provides a communication device, characterized in that the device is a first communication device in fgMTN, and the device includes: a transmitting module, configured to transmit first request information to a second communication device, the first request information being used to indicate a time slot allocation method after the bandwidth of a first bearer channel is adjusted, the time slot allocation method being used to indicate the correspondence between small-granularity clients using the first bearer channel and the time slots provided after the bandwidth of the first bearer channel is adjusted, the first bearer channel being a data bearer channel in fgMTN; a receiving module, configured to receive first response information transmitted by the second communication device, the first response information being used to indicate that the second communication device supports the time slot allocation method; the transmitting module is further configured to transmit second request information to the second communication device, the second request information being used to indicate that the second communication device configures the time slot allocation method to take effect at a preset time point.

[0042] In one possible implementation, the first bearer pipe is a data bearer pipe in the network leased line of fgMTN, the network leased line includes multiple data bearer pipes, and the first bearer pipe is used to carry the business data of one or more small-granularity customers.

[0043] In one possible implementation, the time slot allocation method specifically includes the correspondence between the small-granularity overhead multiframe indicator (fgOMFI) and the small-granularity customer identifier. The fgOMFI is used to indicate the sequence number of the overhead information after the bandwidth of the first bearer pipe is adjusted. The total number of overhead information in one period after the bandwidth of the first bearer pipe is adjusted is related to the adjusted bandwidth value.

[0044] In one possible implementation, the preset time point is the time point after the first communication device sends the second request information and the fgOMFI corresponding to the first bearer pipe is 0;

[0045] Alternatively, the preset time point is the time point at which the data plane time slot begins after the first communication device sends the second request information.

[0046] In one possible implementation, after the bandwidth of the first bearer is adjusted, the small-granularity customers using the first bearer change; the time slot allocation method is used to indicate the correspondence between the changed small-granularity customers and the time slots corresponding to the first bearer.

[0047] In one possible implementation, after the bandwidth of the first bearer is adjusted, the number of time slots corresponding to the target small-granularity customers using the first bearer changes.

[0048] In one possible implementation, the first request information is also used to request the second communication device to adjust the bandwidth of the first bearer channel.

[0049] In one possible implementation, the first request information indicates a request for the second communication device to adjust the bandwidth of the first bearer pipe via the target bit in the overhead (OH) field of the frame.

[0050] In one possible implementation, before sending the first request information to the second communication device, the sending module is further configured to send a third request information to the second communication device, the third request information being used to request the second communication device to adjust the bandwidth of the first bearer channel; the receiving module is further configured to receive a third response information sent by the second communication device, the third response information being used to indicate that the second communication device supports adjusting the bandwidth of the first bearer channel.

[0051] In one possible implementation, the device further includes: a processing module;

[0052] The processing module is used to generate a time slot table for the OH plane. The time slot table for the OH plane is used to indicate the time slot corresponding to the first carrier pipe and the OH information that needs to be transmitted in the time slot corresponding to the first carrier pipe. The OH information is the information in the OH field of the frame.

[0053] The processing module is also used to transmit OH information to the data plane based on the OH plane's time slot table, so that the data plane can send a first request information or a second request information in the time slot corresponding to the first carrier pipeline.

[0054] In one possible implementation, the device further includes: a processing module;

[0055] The processing module is used to generate a spare time slot table for the data plane. The spare time slot table for the data plane is used to indicate the time slot distribution of small-granular customers in the first bearer pipeline after bandwidth adjustment.

[0056] The processing module is also used to switch the backup time slot table of the data plane to the main time slot table at a preset time point.

[0057] A fourth aspect of this application provides a communication device, which is a second communication device in fgMTN, and the device includes: a receiving module, configured to receive first request information sent by a first communication device, the first request information being used to indicate a time slot allocation method after the bandwidth of a first bearer channel is adjusted, the time slot allocation method being used to indicate the correspondence between small-granularity clients using the first bearer channel and the time slots provided after the bandwidth of the first bearer channel is adjusted, the first bearer channel being a data bearer channel in fgMTN; a sending module, configured to send first response information to the first communication device, the first response information being used to indicate that the second communication device supports the time slot allocation method; and a receiving module, further configured to receive second request information sent by the first communication device, the second request information being used to indicate that the second communication device configures the time slot allocation method to take effect at a preset time point.

[0058] In one possible implementation, the first bearer pipe is a data bearer pipe in the network leased line of fgMTN, the network leased line includes multiple data bearer pipes, and the first bearer pipe is used to carry the business data of one or more small-granularity customers.

[0059] In one possible implementation, the time slot allocation method specifically includes the correspondence between the small-granularity overhead multiframe indicator (fgOMFI) and the small-granularity customer identifier. The fgOMFI is used to indicate the sequence number of the overhead information after the bandwidth of the first bearer pipe is adjusted. The total number of overhead information in one period after the bandwidth of the first bearer pipe is adjusted is related to the adjusted bandwidth value.

[0060] In one possible implementation, the preset time point is the time point after the first communication device sends the second request information and the fgOMFI corresponding to the first bearer pipe is 0;

[0061] Alternatively, the preset time point is the time point at which the data plane time slot begins after the first communication device sends the second request information.

[0062] In one possible implementation, after the bandwidth of the first bearer is adjusted, the small-granularity customers using the first bearer change; the time slot allocation method is used to indicate the correspondence between the changed small-granularity customers and the time slots corresponding to the first bearer.

[0063] In one possible implementation, after the bandwidth of the first bearer is adjusted, the number of time slots corresponding to the target small-granularity customers using the first bearer changes.

[0064] In one possible implementation, the first request information is also used to request the second communication device to adjust the bandwidth of the first bearer channel.

[0065] In one possible implementation, the first request information indicates a request for the second communication device to adjust the bandwidth of the first bearer channel via the target bit in the OH field of the frame.

[0066] In one possible implementation, before receiving the first request information sent by the first communication device, the receiving module is further configured to receive a third request information sent by the first communication device, the third request information being used to request the second communication device to adjust the bandwidth of the first bearer channel; the sending module is further configured to send a third response information to the first communication device, the third response information being used to instruct the second communication device to support adjusting the bandwidth of the first bearer channel.

[0067] A fifth aspect of this application provides a communication device including a processor and a memory. The memory stores program code, and the processor invokes the program code in the memory to cause the communication device to perform a method as described in any of the embodiments of the first or second aspect.

[0068] A sixth aspect of this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform a method as described in any of the embodiments of the first aspect.

[0069] The seventh aspect of this application provides a computer program product that, when run on a computer, causes the computer to perform a method as described in any of the embodiments of the first aspect.

[0070] This application provides a chip, including one or more processors. Part or all of the processors are used to read and execute computer instructions stored in a memory to perform the methods in any possible implementation of any of the above aspects. Optionally, the chip also includes a memory. Optionally, the chip also includes a communication interface, with the processor connected to the communication interface. The communication interface is used to receive data and / or information to be processed, the processor obtains the data and / or information from the communication interface, processes the data and / or information, and outputs the processing results through the communication interface. Optionally, the communication interface is an input / output interface or a bus interface. The methods provided in this application are implemented by one chip or by multiple chips working together.

[0071] The solutions provided in the second to eighth aspects above are used to implement or cooperate with the methods provided in the first aspect above, and therefore can achieve the same or corresponding beneficial effects as the first aspect, which will not be elaborated here. Attached Figure Description

[0072] Figure 1 is a schematic diagram of an application scenario provided by an embodiment of this application;

[0073] Figure 2 is a schematic diagram illustrating data transmission between communication devices according to an embodiment of this application;

[0074] Figure 3 is a schematic diagram of a possible data transport pipeline division provided in an embodiment of this application;

[0075] Figure 4 is a flowchart illustrating a bandwidth adjustment method provided in an embodiment of this application;

[0076] Figure 5 is a schematic diagram of a frame format provided in an embodiment of this application;

[0077] Figure 6 is a schematic diagram of the format of an OH field provided in an embodiment of this application;

[0078] Figure 7 is a schematic diagram of a communication device negotiating bandwidth reduction according to an embodiment of this application;

[0079] Figure 8 is a schematic diagram of a communication device negotiating increased bandwidth according to an embodiment of this application;

[0080] Figure 9 is a schematic diagram showing the change in time slot allocation method before and after the bandwidth of a data bearer pipeline is increased, according to an embodiment of this application.

[0081] Figure 10 is a schematic diagram showing the change in time slot allocation method before and after the bandwidth reduction of a data bearer pipe provided in an embodiment of this application;

[0082] Figure 11 is a schematic diagram showing the change in time slot allocation method before and after the bandwidth reduction of another data bearer pipe provided in the embodiment of this application;

[0083] Figure 12 is a schematic diagram of the interaction between the OH surface and the data surface provided in an embodiment of this application;

[0084] Figure 13 is a schematic diagram of the format of a bearing pipeline mapping table provided in an embodiment of this application;

[0085] Figure 14 is a time slot table for a single load-bearing pipe provided in an embodiment of this application;

[0086] Figure 15 is a schematic diagram of a time slot table for a data plane provided in an embodiment of this application;

[0087] Figure 16 is a schematic diagram of a time slot table for an OH plane provided in an embodiment of this application;

[0088] Figure 17 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0089] Figure 18 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0090] Figure 19 is a schematic diagram of the structure of a network device provided in an embodiment of this application. Detailed Implementation

[0091] The embodiments of this application are described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. As those skilled in the art will understand, with the development of technology and the emergence of new scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0092] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. In the embodiments of this application, the term "at least one" refers to one or more, and "more than one" refers to two or more.

[0093] The term “exemplary” as used herein means “serving as an example, embodiment, or illustration.” Any embodiment illustrated herein as “exemplary” is not necessarily to be construed as superior to or better than other embodiments.

[0094] To facilitate a better understanding of the technical solution of this application by those skilled in the art, a brief introduction is first given to some relevant technologies and technical terms involved in the technical solution of this application.

[0095] Figure 1 illustrates an application scenario provided by an embodiment of this application. The application scenario of this application embodiment will be described below with reference to the accompanying drawings.

[0096] As shown in Figure 1, the system includes a network management device 100, a communication device 101, and a communication device 102. Communication devices 101 and 102 can be network devices or chips installed within network devices. These network devices include, but are not limited to: core routers, edge routers, optical transport network (OTN) transmission equipment, OTN optical service units (OSUs), and, for specific scenarios, Internet Protocol Radio Access Network (IPRAN) and Packet Transport Network (PTN) box-type or chassis-type switch equipment.

[0097] As shown in Figure 1, the network management device 100 can be used to send control or management information to the communication device 101 or the communication device 102, such as information about changes in small-granularity clients or changes in the bandwidth of small-granularity clients. Communication devices 101 and 102 can transmit data to each other. Both communication devices 101 and 102 can include a transmitting module and a receiving module. That is, either communication device 101 or communication device 102 can act as the transmitting end 121 in Figure 2, and in some cases, it can also act as the receiving end 122 in Figure 2.

[0098] Please refer to Figure 2, which is a schematic diagram illustrating data transmission between communication devices according to an embodiment of this application. As shown in Figure 2, the solution of this embodiment can be applied between the sending end 121 and the receiving end 122. In this embodiment, one or more services (such as service 1, service 2... service m in Figure 2) can be multiplexed at the sending end. The multiplexed data is then transmitted to the receiving end 122, where it is demultiplexed to recover the individual services. In this embodiment, the services between the sending end 121 and the receiving end 122 can be dynamically adjusted, such as adding services, deleting services, increasing service bandwidth, or decreasing service bandwidth. In this embodiment, the sending end interface and the receiving end interface can be an fgMTN interface, an OTN interface, an Ethernet interface, or a pipe partitioned from these interfaces.

[0099] Please refer to Figure 3, which is a schematic diagram of a possible data transport pipeline partitioning provided in an embodiment of this application. As shown in Figure 3, based on Figure 2, the interface of the sending end 121 and the interface of the receiving end 122 can be partitioned into pipelines. In this embodiment, two terms are defined: large-granularity pipeline and small-granularity pipeline. These are relative terms; a large-granularity pipeline can be divided into one or more small-granularity pipelines, and the bandwidth of the large-granularity pipeline is usually greater than or equal to the bandwidth of the small-granularity pipeline. Specifically, the large-granularity pipeline between the sending end 121 and the receiving end 122 can be divided into multiple small-granularity pipelines, each of which can be used to carry service data. Generally, a small-granularity pipeline can be understood as a logical pipeline. A small-granularity pipeline is used to carry the service data of a small-granularity user (such as one or more services under a small-granularity user), while a large-granularity pipeline can be used to carry the service data of multiple small-granularity users.

[0100] For example, the bandwidth of a large-granularity pipeline can be, for instance, 1 to 10 gigabits per second (Gbps) or other bandwidth values. Furthermore, since the minimum bandwidth for small-granularity services is typically 10 megabits per second (Mbps), a 5Gbps large-granularity pipeline can provide 480 small-granularity time slots to carry small-granularity services. Similarly, a 1Gbps large-granularity pipeline can provide 96 small-granularity time slots to carry small-granularity services.

[0101] In practical applications, small-granularity customers lease a portion of the bandwidth of a dedicated network line. Based on the bandwidth leased by each small-granularity customer, a unique large-granularity pipeline can be assigned to each customer, thus carrying the business data of each small-granularity customer. Generally, one large-granularity pipeline can carry the business data of multiple small-granularity customers. Furthermore, to ensure the resource utilization of the large-granularity pipeline, its bandwidth is often equal to the total bandwidth leased by the multiple small-granularity customers it carries. However, as customer business dynamics change, the customers leasing dedicated network lines may change, and the bandwidth leased by each customer may also change, making it difficult to match the bandwidth of the large-granularity pipeline with the total bandwidth leased by the small-granularity customers it carries.

[0102] Based on this, this application provides a bandwidth adjustment method. By introducing a bandwidth adjustment negotiation mechanism between two communication devices in fgMTN, the two communication devices negotiate the bandwidth adjustment through a handshake communication method and simultaneously configure new bandwidth for the data bearer pipeline (i.e., the large-granularity pipeline mentioned above) at a specific time point. In the negotiation process, the new time slot allocation method after the bandwidth of the data bearer pipeline is adjusted is specified to ensure that the data bearer pipeline can be used normally after the bandwidth is adjusted, thereby realizing the dynamic adjustment of the bandwidth of the data bearer pipeline and meeting the dynamic changes in business scenarios.

[0103] Please refer to Figure 4, which is a flowchart illustrating a bandwidth adjustment method provided in an embodiment of this application. As shown in Figure 4, the bandwidth adjustment method includes the following steps 401-404.

[0104] Step 401: The first communication device sends a first request message to the second communication device. The first request message is used to indicate the time slot allocation method after the bandwidth of the first bearer is adjusted. The time slot allocation method is used to indicate the correspondence between small-particle customers using the first bearer and the time slots provided after the bandwidth of the first bearer is adjusted.

[0105] In this embodiment, when the first communication device wishes to adjust the bandwidth of the first bearer channel between the first communication device and the second communication device, the first communication device sends a first request message to the second communication device to negotiate with the second communication device on how to adjust the bandwidth of the first bearer channel. Here, the first communication device is, for example, a sender of service data, and the second communication device is, for example, a receiver of service data; that is, the first communication device transmits service data to the second communication device through the first bearer channel.

[0106] Optionally, the first bearer pipe is the data bearer pipe in the fgMTN network leased line. The network leased line includes multiple data bearer pipes, and the first bearer pipe is used to carry the service data of one or more small-granularity customers. That is, the first bearer pipe is the large-granularity pipe described above, used to carry small-granularity service data. The bandwidth of the first bearer pipe can be, for example, 1 to 10 Gbps or other bandwidth values, such as 1 Gbps or 5 Gbps. In this embodiment, the bandwidth of the first bearer pipe can vary in 1 Gbps granularity, for example, from 1 Gbps to 2 Gbps, 5 Gbps, 10 Gbps, or from 5 Gbps to 2 Gbps, 1 Gbps, etc. The bandwidth of the first bearer pipe can also vary in other bandwidth granularities, for example, from 5 Gbps to 10 Gbps when the variation granularity is 5 Gbps. In short, this embodiment does not limit the granularity of the bandwidth variation of the first bearer pipe, nor does it limit the range of variation of the first bearer pipe. For ease of description, this embodiment will be described below using the example of the bandwidth of the first bearer channel changing from 1Gbps to 5Gbps and from 5Gbps to 1Gbps.

[0107] Since the bandwidth of the small-granularity services carried by the first bearer channel is usually fixed, the number of small-granularity time slots provided by the first bearer channel is also fixed when the bandwidth of the first bearer channel is fixed. For example, when the bandwidth of the first bearer channel is 5Gbps and the bandwidth of the small-granularity channel is 10Mbps, the first bearer channel can provide 480 small-granularity time slots to carry small-granularity services; when the bandwidth of the first bearer channel is 1Gbps and the bandwidth of the small-granularity channel is 10Mbps, the first bearer channel can provide 96 small-granularity time slots to carry small-granularity services. Therefore, when the bandwidth of the first bearer channel is adjusted, the number of small-granularity time slots that the first bearer channel can provide will change. Correspondingly, when the number of small-granularity time slots that the first bearer channel can provide changes, the correspondence between the small-granularity time slots provided by the first bearer channel after the bandwidth adjustment and the small-granularity customers will often change as well. Therefore, the first communication device can use the first request information to indicate the time slot allocation method after the bandwidth of the first bearer channel is adjusted, so that the second communication device can subsequently receive the data transmitted by the first communication device based on the new time slot allocation method.

[0108] It should be noted that this article uses a small-particle pipeline with a bandwidth of 10Mbps as an example to determine the number of time slots corresponding to the first bearer pipeline under various bandwidths (for example, the first bearer pipeline can provide 480 time slots when it is 5Gbps). In practical applications, the bandwidth of the small-particle pipeline can also be other values, such as 5Mbps or 20Mbps, and this embodiment does not specifically limit it.

[0109] For example, assume that the bandwidth of the first bearer is 1Gbps before adjustment, and the 96 time slots provided by the first bearer are allocated to small-granularity customer 1 and small-granularity customer 2 respectively. Among them, small-granularity customer 1 corresponds to 32 of the 96 time slots, and the time slot number corresponding to small-granularity customer 1 is an integer multiple of 3 (that is, small-granularity customer corresponds to time slot 0, time slot 3, time slot 6... time slot 93); small-granularity customer 2 corresponds to the other 64 of the 96 time slots, that is, small-granularity customer corresponds to time slot 1, time slot 2, time slot 4, time slot 5... time slot 95.

[0110] Therefore, after the bandwidth of the first bearer channel is adjusted to 5Gbps, the number of time slots provided by the first bearer channel will increase from 96 to 480. Even if the 480 time slots provided after the bandwidth adjustment are still allocated to small-granularity customer 1 and small-granularity customer 2, the correspondence between these 480 time slots and small-granularity customer 1 and small-granularity customer 2 will change. For example, if small-granularity customer 1 still corresponds to 32 time slots out of the 480, then the time slot number corresponding to small-granularity customer 1 can be an integer multiple of 15 (i.e., small-granularity customer corresponds to time slot 0, time slot 15, time slot 30... time slot 465); small-granularity customer 2 corresponds to the other 448 time slots out of the 480, i.e., small-granularity customer corresponds to time slot 1, time slot 2... time slot 14... time slot 479.

[0111] It should be noted that the bandwidth of the first bearer channel is directly proportional to the number of time slots it provides. Therefore, when the time slot allocation method for the first bearer channel is specified, its bandwidth can actually be determined based on the number of time slots included in that allocation method. For example, if the first request information indicates a time slot allocation method of 480 time slots, the adjusted bandwidth of the first bearer channel can be determined to be 5Gbps; if the first request information indicates a time slot allocation method of 96 time slots, the adjusted bandwidth of the first bearer channel can be determined to be 1Gbps.

[0112] Step 402: The second communication device sends a first response message to the first communication device. The first response message is used to indicate that the second communication device supports the time slot allocation method.

[0113] After the second communication device receives the first request information sent by the first communication device, if the second communication device can identify the content indicated by the first request information sent by the first communication device, and the second communication device can support the time slot allocation method after the first bearer adjusts the bandwidth, then the second communication device can send the first response information to the first communication device to indicate that it supports the time slot allocation method indicated by the first communication device.

[0114] Step 403: The first communication device sends a second request message to the second communication device. The second request message is used to instruct the second communication device to configure the time slot allocation method to take effect at a preset time point.

[0115] Upon receiving the first response information from the second communication device, the first communication device can confirm that the second communication device supports the adjustment of the bandwidth of the first bearer channel and the new time slot allocation method after the bandwidth adjustment. Therefore, in order to facilitate the simultaneous data transmission of the first and second communication devices using the new time slot allocation method, the first communication device sends a second request information to the second communication device to instruct the second communication device to configure the time slot allocation method to take effect at a preset time point.

[0116] Step 404: The first communication device and the second communication device configure the time slot allocation method to take effect at a preset time point.

[0117] Specifically, the first and second communication devices can configure a time slot table generated based on a negotiated time slot allocation method on the data plane at a preset time point. The time slot table configured by the first communication device guides its data transmission, while the time slot table configured by the second communication device guides its data reception. Thus, the first communication device transmits data to the second communication device at the preset time point according to the negotiated time slot allocation method and the adjusted bandwidth of the first bearer channel. For example, if the bandwidth of the first bearer channel is increased, the first communication device also needs to increase its data transmission rate when transmitting data to the second communication device based on the new time slot allocation method, ensuring that data transmission is based on the adjusted bandwidth of the first bearer channel. The second communication device receives the data transmitted by the first communication device at the preset time point according to the negotiated time slot allocation method and the adjusted bandwidth of the first bearer channel, thereby ensuring lossless data transmission between the first and second communication devices through the first bearer channel and avoiding data packet loss due to time slot misalignment. For example, if the bandwidth of the first bearer channel is increased, the second communication device also needs to increase its data reception rate when receiving data based on the new time slot allocation method, so as to ensure that the data is received based on the adjusted bandwidth of the first bearer channel.

[0118] The above embodiments describe the time slot allocation method after the first communication device and the second communication device negotiate the adjustment of the bearer bandwidth. To facilitate the second communication device's accurate identification that the first request information sent by the first communication device is for indicating the time slot allocation method after the bearer bandwidth adjustment, this embodiment provides multiple implementation methods.

[0119] In one possible implementation, the first request information sent by the first communication device is also used to request the second communication device to adjust the bandwidth of the first bearer channel.

[0120] In other words, the first request information simultaneously instructs the second communication device to adjust the bandwidth of the first bearer channel and the time slot allocation method after the bandwidth adjustment. Thus, upon receiving the first request information, if the second communication device recognizes that the first request information instructs for adjusting the bandwidth of the first bearer channel, it can confirm that the time slot allocation method indicated in the first request information is actually the time slot allocation method corresponding to the adjusted bandwidth of the first bearer channel. For example, the first request information instructs the second communication device to adjust the bandwidth of the first bearer channel through the target bit in the overhead (OH) field of the frame. The target bit is, for example, an existing bit or a reserved bit in the overhead field of the frame. Setting the value of the target bit in the OH field to 1 in the frame sent by the first communication device to the second communication device indicates that the current request is for the second communication device to adjust the bandwidth of the first bearer channel.

[0121] Please refer to Figures 5 and 6. Figure 5 is a schematic diagram of a frame format provided in an embodiment of this application; Figure 6 is a schematic diagram of an OH field format provided in an embodiment of this application. In fgMTN, the format of a frame sent by the first communication device to the second communication device is shown in Figure 5. The frame includes multiple fields, namely a Block Type S0 field, a reservation field, an OH field, a payload field, and a Block Type T7 field. The OH field can be used to carry the content of the first request information mentioned in this embodiment, while the payload field is used to carry the business data of small-granularity customers.

[0122] As shown in Figure 6, the OH field in a frame can be defined as multiple parts, including Fine Granularity Overhead Multiframe Indication (fgOMFI), Fine Granularity Overhead Client Identity Document (fgClientID), Reserved (Res), Expansion Notification (S), Adjustment Request (CR), Adjustment Acknowledgement (CA), and Adjustment Commit (C) bits.

[0123] The target bit used to indicate a request for the second communication device to adjust the bandwidth of the first bearer channel can be, for example, a reserved bit in the OH field of the frame, or a CR / CA / C / S bit in the OH field of the frame. That is, the function of requesting bandwidth adjustment can be implemented by defining the reserved bit in the OH field of the frame to notify the other communication device to adjust the bandwidth of the data bearer channel; or the function of extending the existing bit can be used to notify the other communication device to adjust the bandwidth of the data bearer channel.

[0124] Optionally, the time slot allocation method indicated in the first request information specifically includes the correspondence between fgOMFI and small-granularity customer identifiers, where fgOMFI is used to indicate the sequence number of overhead information after the bandwidth adjustment of the first bearer pipe. The total number of overhead information items within one cycle after the bandwidth adjustment of the first bearer pipe is related to the adjusted bandwidth value. For example, if the adjusted bandwidth of the first bearer pipe is 1Gbps, the total number of overhead information items within one cycle after the bandwidth adjustment is 96, and the sequence number of the overhead information items after the bandwidth adjustment is 0–95. If the adjusted bandwidth of the first bearer pipe is 5Gbps, the total number of overhead information items within one cycle after the bandwidth adjustment is 480, and the sequence number of the overhead information items after the bandwidth adjustment is 0–479.

[0125] Generally, in the OH field of a frame, fgOMFI and the small-granularity customer identifier are used to indicate the correspondence between time slots and small-granularity customers. For example, if fgOMFI is 5 and the small-granularity customer identifier is 1 in the OH field of a frame, it means that the 5th time slot corresponds to small-granularity customer 1, that is, the 5th time slot of the current data transmission pipeline is used to carry the service data of small-granularity customer 1. During normal communication, the first communication device and the second communication device will carry fgOMFI and the small-granularity customer identifier in the OH field of each frame. The fgOMFI carried in the OH field of the frame will continuously change within a range as the number of frames increases (for example, fgOMFI is 0 in the 1st frame, fgOMFI is 1 in the 2nd frame... fgOMFI is 95 in the 96th frame, and fgOMFI is 0 in the 97th frame), thereby indicating the correspondence between the current data transmission pipeline time slots and small-granularity customers, so that the first communication device and the second communication device can confirm the consistency of the correspondence between time slots and small-granularity customers.

[0126] When the first request information indicates a request for the second communication device to adjust the bandwidth of the first bearer channel by using the target bit in the OH field of the frame, if the target bit in the OH field of the frame received by the second communication device is 1, the second communication device can confirm that the current request is to adjust the bandwidth of the first bearer channel. Therefore, the OH field of the frame actually indicates the time slot allocation method after the bandwidth of the first bearer channel is adjusted, rather than the time slot allocation method of the current bandwidth of the first bearer channel.

[0127] In another possible implementation, before the first communication device sends a first request message to the second access device instructing the time slot allocation method after the first bearer pipe adjusts its bandwidth, the first communication device and the second access device first negotiate whether the bandwidth adjustment of the first bearer pipe can be performed.

[0128] For example, in the embodiment corresponding to Figure 4 described above, before the first communication device sends the first request information to the second communication device, the first communication device sends a third request information to the second communication device. The third request information is used to request the second communication device to adjust the bandwidth of the first bearer channel. That is, when the first communication device needs to adjust the bandwidth of the first bearer channel, it first sends a request information to the second communication device to request the second communication device to cooperate in adjusting the bandwidth of the first bearer channel, so as to confirm whether the second communication device can support adjusting the bandwidth of the first bearer channel.

[0129] After receiving the third request information, if the second communication device supports adjusting the bandwidth of the first bearer channel, the second communication device sends a third response information to the first communication device. The third response information is used to indicate that the second communication device supports adjusting the bandwidth of the first bearer channel.

[0130] In this way, after the first communication device receives the third response information, it can confirm that the second communication device supports adjusting the bandwidth of the first bearer channel, and then continue to send the aforementioned first request information to the second communication device to indicate the specific time slot allocation method after the bandwidth of the first bearer channel is adjusted.

[0131] Optionally, the aforementioned third request information and third response information are carried through reserved bits in the OH field of the frame. For example, when the first communication device sends a frame to the second communication device, it can set the reserved bit in the OH field of the frame shown in Figure 6 to 1, thereby requesting the second communication device to adjust the bandwidth of the first bearer channel.

[0132] Alternatively, the third request information and the third response information can be carried by defining new bits in the OH field of the frame. That is, by defining new bits, the request to the other side's communication device to adjust the bandwidth of the data bearer channel can be realized, or the response to the other side's communication device itself can support adjusting the bandwidth of the data bearer channel.

[0133] Similarly, in the above embodiments, the first request information sent by the first communication device, the first response information sent by the second communication device, and the second request information sent by the first communication device can all be carried by defining new bits in the frame OH field.

[0134] For example, the first request message sets the CR bit in the OH field of the message to 1 to indicate that the current notification to the second communication device is about the adjusted time slot allocation method of the first bearer channel; the first response message sets the CA bit in the OH field of the message to 1 to indicate that the second communication device supports the adjusted time slot allocation method of the first bearer channel; the second request message sets the C bit in the OH field of the message to 1 to indicate that the second communication device configures the time slot allocation method to take effect at a preset time point. Optionally, in the above embodiments, after the first communication device and the second communication device negotiate the time slot allocation method, the preset time point at which the first communication device and the second communication device configure the time slot allocation method to take effect can be implemented in various ways.

[0135] For example, the preset time point can be the time point after the first communication device sends the second request information and the fgOMFI corresponding to the first bearer channel is 0. Specifically, since the first communication device carries fgOMFI in the OH field of each frame during the process of sending frames to the second communication device through the first bearer channel, and the value of fgOMFI will continuously poll within a certain range as the number of frames increases (that is, the first communication device inserts the value of fgOMFI within a specific range into the frames in turn), the first communication device can use the time point when fgOMFI is 0 in the frame carried by the first bearer channel as the boundary node to trigger the simultaneous configuration of the time slot allocation method of the two communication devices.

[0136] For example, the preset time point is the start time of the data plane time slot after the first communication device sends the second request information. Here, a data plane time slot refers to the time slot corresponding to a complete time slot cycle of the data plane. That is, the preset time point can actually be the start time of the Nth time slot cycle after the first communication device sends the second request information, where N is an integer greater than or equal to 1. For example, the preset time point is the start time of the next time slot cycle after the first communication device sends the second request information. Optionally, in some embodiments, the preset time point can also be the time point where the start of the data frame and the start of the time slot cycle coincide.

[0137] Generally, the total number of time slots in a data plane time slot round is fixed (i.e., the time slot period is fixed), and the total number of time slots is related to the bandwidth of the data bearer pipeline. For example, the number of time slots corresponding to the first bearer pipeline with a bandwidth of 5Gbps in a data plane time slot round is 5*96.

[0138] The above describes the process of negotiating bandwidth adjustments between two communication devices and configuring the bandwidth adjustment to take effect at a preset time. To facilitate understanding, the following will use specific examples to explain in detail how communication devices achieve the negotiation process in scenarios of bandwidth increase and decrease.

[0139] Please refer to Figure 7, which is a schematic diagram of a communication device negotiating a reduction in bandwidth according to an embodiment of this application. As shown in Figure 7, the process of the first communication device and the second communication device negotiating a reduction in the bandwidth of the first bearer channel includes the following steps 701-706. Specifically, the first communication device and the second communication device negotiate to reduce the bandwidth of the first bearer channel from 5Gbps to 1Gbps.

[0140] Step 701: The first communication device sends request information 1 to the second communication device to request the second communication device to adjust the bandwidth of the first bearer channel.

[0141] In this embodiment, request information 1 is, for example, the third request information in the above embodiment. The method by which the first communication device sends request information 1 to the second communication device can be as follows: For at least one frame sent by the first communication device to the second communication device through the first bearer channel, the first communication device sets the value of the D.CR bit in the OH field of the frame to 1, thereby instructing the second communication device to adjust the bandwidth of the first bearer channel carrying the current frame. The D.CR bit can be a reserved bit in the OH field of the frame (for example, any reserved bit after fgClientID in the frame shown in Figure 6) or a newly defined bit. That is, in this embodiment, a reserved bit can be defined as the D.CR bit used to instruct the other communication device to adjust the bandwidth of the data bearer channel.

[0142] It should be noted that after the first communication device begins sending request information 1 to the second communication device, the first communication device may continuously carry request information 1 in the frames sent to the second communication device through the first bearer channel, that is, continuously set the value of the D.CR bit in the OH field of the frame to 1, until it receives a response from the second communication device; or, the first communication device may continuously carry request information 1 in the frames sent to the second communication device through the first bearer channel until it still does not receive a response from the second communication device after sending a certain number of frames or for a certain period of time. In this case, it can be assumed that the second communication device does not support adjusting the bandwidth of the first bearer channel, and thus the request to the second communication device to adjust the bandwidth of the first bearer channel is stopped. Alternatively, the first communication device may carry request information 1 in the frames sent to the second communication device through the first bearer channel within a finite number of time slot windows, instead of continuously sending request information 1.

[0143] Step 702: The second communication device sends response information 1 to the first communication device to indicate that the second communication device supports adjusting the bandwidth of the first bearer channel.

[0144] After the second communication device receives the frame carrying request information 1 through the first bearer channel, if the second communication device itself can recognize that the frame sent by the first communication device is a request for the second communication device to adjust the bandwidth of the first bearer channel, and the second communication device is currently able to support adjusting the bandwidth of the first bearer channel, then the second communication device can send back response information 1 (response information 1 is, for example, the third response information mentioned above) to the first communication device to indicate that the second communication device supports adjusting the bandwidth of the first bearer channel.

[0145] Specifically, the method by which the second communication device sends response information 1 to the first communication device can be as follows: For at least one frame sent by the second communication device to the first communication device through the first bearer channel, the second communication device sets the value of the D.CA bit in the OH field of the frame to 1, thereby indicating that the second communication device supports adjusting the bandwidth of the first bearer channel carrying the current frame. The D.CA bit can be a reserved bit in the OH field of the frame (e.g., the reserved bit after fgClientID in the frame shown in Figure 6) or a newly defined bit. That is, in this embodiment, a reserved bit can be defined as a D.CR bit used to indicate support for adjusting the bandwidth of the data bearer channel. It should be noted that the D.CA bit mentioned in step 2 is different from the D.CR bit mentioned in step 1.

[0146] Furthermore, after the second communication device receives the frame carrying request information 1 through the first bearer channel, if the second communication device cannot recognize that the frame sent by the first communication device is a request for the second communication device to adjust the bandwidth of the first bearer channel, or if the second communication device can recognize the frame sent by the first communication device but does not support adjusting the bandwidth of the first bearer channel itself (e.g., insufficient resources), then the second communication device may either not send a response message to the first communication device, or send a pre-agreed rejection message to the first communication device to instruct the second communication device to refuse to adjust the bandwidth of the first bearer channel.

[0147] Step 703: The first communication device sends request information 2 to the second communication device to indicate the time slot allocation method after the first bearer pipe adjusts its bandwidth.

[0148] After receiving response information 1 from the second communication device, the first communication device can confirm that the second communication device supports adjusting the bandwidth of the first bearer channel. Therefore, the first communication device continues to send request information 2 (request information 2 being, for example, the first request information mentioned above) to the second communication device to further indicate the time slot allocation method after the bandwidth of the first bearer channel is adjusted. Since the bandwidth of the data bearer channel is directly proportional to the number of time slots, after indicating the time slot allocation method after the bandwidth of the first bearer channel is adjusted through request information 2, the corresponding bandwidth can be determined based on the number of time slots in the time slot allocation method. This is equivalent to request information 2 simultaneously indicating the adjusted bandwidth of the first bearer channel. Optionally, the network management device can also send the adjusted bandwidth of the first bearer channel to the second communication device in advance, so that after receiving the time slot allocation method indicated by request information 2, the second communication device can verify whether the adjusted bandwidths of the first bearer channel indicated by the network management device and the first communication device are the same.

[0149] Specifically, the method by which the first communication device sends request information 2 to the second communication device can be as follows: for the frame sent by the first communication device to the second communication device through the first bearer channel, the first communication device sets the value of the CR bit in the OH field of the frame (as shown in Figure 6) to 1; and the first communication device carries the time slot allocation method after the first bearer channel adjusts the bandwidth through the fgOMFI field and the fgClientID field of the frame.

[0150] Specifically, when the bandwidth of the first bearer channel changes from 5Gbps to 1Gbps, the value of fgOMFI in the frame's fgOMFI field changes alternately within the range of 0-95 as the frame increases, thus indicating the 96 time slots corresponding to the first bearer channel bandwidth becoming 1Gbps. Furthermore, the fgClientID in the frame's fgClientID field changes with the value of the fgOMFI field, thus indicating the small-granularity client corresponding to each time slot. In other words, in the frame's OH field, the fgOMFI field can actually be used to indicate the sequence number of each time slot provided after the first bearer channel bandwidth adjustment, while fgClientID can be used to indicate the small-granularity client corresponding to the time slot indicated by the fgClientID field. In this way, by sending 96 frames to the second communication device, with each frame's OH field carrying a different fgOMFI value and a corresponding fgClientID value, the first communication device can indicate the time slot allocation method after the first bearer channel bandwidth adjustment.

[0151] As shown in Figure 7, in step 701, during the transmission of request information 1 by the first communication device, the value of fgOMFI varies within the range of 0-479, and the value of fgClientID is Pre-fgClientID. That is, the fgOMFI field and fgClientID are used to indicate the time slot allocation method before the bandwidth adjustment of the first bearer pipe. In this step, during the transmission of request information 2 by the first communication device, the value of fgOMFI varies within the range of 0-95, and the value of fgClientID is Target-fgClientID. That is, the fgOMFI field and fgClientID are used to indicate the time slot allocation method after the bandwidth adjustment of the first bearer pipe.

[0152] It should be noted that the range of fgOMFI corresponding to the time slot allocation method after the bandwidth adjustment of the first bearer pipe will change compared to the time slot allocation method before the bandwidth adjustment (for example, when the bandwidth of the first bearer pipe changes from 5Gbps to 1Gbps, the range of fgOMFI corresponding to the time slot allocation method will change from 0-479 to 0-95). Therefore, in order to ensure that the second communication device can receive frames normally during the bandwidth negotiation period, the first communication device may start sending request information 2 to the second communication device when fgOMFI is 0 in the next round. Furthermore, when the first communication device starts sending request information 2 to the second communication device, the range of fgOMFI in the frames sent by the first communication device changes from 0-479 to 0-95.

[0153] It is worth noting that in step 703, the first communication device actually transmits the adjusted time slot allocation method (i.e., the new time slot allocation method) of the first bearer channel through the OH field of the frame. Furthermore, the frame sent by the first communication device to the second communication device also carries data from small-granularity clients (i.e., the data carried by the payload field of the frame). Before the new time slot allocation method takes effect, the first communication device still sends data from small-granularity clients to the second communication device according to the previously negotiated time slot allocation method, and the second communication device also receives data from small-granularity clients according to the previously negotiated time slot allocation method, thereby ensuring the normal transmission of small-granularity client data.

[0154] Step 704: The second communication device sends response information 2 to the first communication device to indicate that the second communication device supports the time slot allocation method after the first bearer pipe adjusts its bandwidth.

[0155] Upon receiving request information 2 from the first communication device and confirming that it can support the new time slot allocation method indicated by the first communication device, the second communication device sends response information 2 (response information 2 being, for example, the first response information mentioned above) to the first communication device, indicating that it supports the time slot allocation method after the bandwidth adjustment of the first bearer. If the second communication device cannot support the new time slot allocation method indicated by the first communication device, the second communication device will not send a response information or will send a rejection information to the first communication device, thereby terminating the bandwidth adjustment.

[0156] Specifically, the method by which the second communication device sends response information 2 to the first communication device can be as follows: for each frame sent by the second communication device to the first communication device through the first bearer channel, the second communication device sets the value of the CA bit in the OH field of the frame (as shown in Figure 6) to 1.

[0157] Step 705: The first communication device sends request information 3 to the second communication device to instruct the second communication device to take effect the new time slot allocation method at a preset time point.

[0158] After the first communication device receives the response information 2 from the second communication device, the first communication device can confirm that the second communication device supports the time slot allocation method after the first bearer pipe bandwidth is adjusted. Therefore, the first communication device continues to send request information 3 (request information 3 is, for example, the second request information mentioned above) to the second communication device so that the first communication device and the second communication device can take effect at the same time (i.e., the time slot allocation method after the first bearer pipe bandwidth is adjusted), thereby ensuring the normal transmission and reception of frames.

[0159] Specifically, the method by which the first communication device sends request information 3 to the second communication device can be as follows: for each frame sent by the first communication device to the second communication device through the first bearer channel, the first communication device sets the value of the C bit in the OH field of the frame (as shown in Figure 6) to 1.

[0160] It should be noted that after receiving response information 2 from the second communication device, the first communication device can perform preparation work on the data plane to transmit data using the new time slot allocation method. For example, it can generate a time slot table on the data plane based on the new time slot allocation method, so that it can quickly switch to transmitting data using the new time slot allocation method at a preset time point. Alternatively, the first communication device can also perform preparation work on the data plane to transmit data using the new time slot allocation method immediately after receiving response information 2; this embodiment does not specifically limit this step.

[0161] Similarly, after receiving request information 2 or request information 3 sent by the first communication device, the second communication device can also perform preparation work on the data plane to receive data in a new time slot allocation mode, such as generating a time slot table on the data plane based on the new time slot allocation mode, so as to quickly switch to receiving data in the new time slot allocation mode at a preset time point.

[0162] Step 706: The first communication device and the second communication device take effect at a preset time point with the new time slot allocation method.

[0163] In this embodiment, step 706 is similar to step 404 described above. Please refer to step 404 for details, which will not be repeated here.

[0164] In other words, during the negotiation of the new time slot allocation method between the first and second communication devices, only the time slot allocation method indicated in the OH field changes. The first and second communication devices still actually transmit and receive data on the data plane according to the previously negotiated time slot allocation method (meaning the time slot allocation method on the OH plane is different from the time slot allocation method actually implemented on the data plane). After the new time slot allocation method takes effect, the first and second communication devices can transmit and receive data according to the new time slot allocation method. Furthermore, the above example describes the bandwidth of the first bearer channel varying from 5Gbps (i.e., 5*1Gbps) to 1Gbps in 1Gbps granularity. In some possible examples, the bandwidth of the first bearer channel can also vary flexibly within a certain bandwidth range in granularity with other bandwidth values; this embodiment does not limit this. For example, the bandwidth of the first bearer channel can vary from 10Gbps (i.e., 2*5Gbps) to 5Gbps (i.e., 1*5Gbps) in 5Gbps granularity.

[0165] Please refer to Figure 8, which is a schematic diagram of a communication device negotiating an increase in bandwidth according to an embodiment of this application. As shown in Figure 8, the process of the first communication device and the second communication device negotiating an increase in the bandwidth of the first bearer channel includes the following steps 800-806.

[0166] Step 800: The second communication device sends a request message 0 to the first communication device to request the first communication device to initiate bandwidth adjustment negotiation for the first bearer channel.

[0167] In this embodiment, the method by which the second communication device sends request information 0 to the first communication device can be as follows: for each frame sent by the second communication device to the first communication device through the first bearer channel, the second communication device sets the value of the DS bit in the OH field of the frame to 1. The DS bit used in this step can be a newly defined bit in the OH field of the frame.

[0168] It should be noted that step 800 is optional. In fact, the first communication device can directly send a request to the second communication device to adjust the bandwidth of the data bearer channel.

[0169] Step 801: The first communication device sends request information 1 to the second communication device to request the second communication device to adjust the bandwidth of the first bearer channel.

[0170] Step 802: The second communication device sends response information 1 to the first communication device to indicate that the second communication device supports adjusting the bandwidth of the first bearer channel.

[0171] In this embodiment, steps 801-802 are similar to steps 701-702 described above. Please refer to steps 701-702 above for details, which will not be repeated here.

[0172] Step 803: The first communication device sends request information 2 to the second communication device to indicate the time slot allocation method after the first bearer pipe adjusts its bandwidth.

[0173] In this embodiment, the difference between step 803 and step 703 is that the time slot allocation method indicated by request information 2 in step 803 is an allocation method of 480 time slots (i.e., 0-479 time slots), while the time slot allocation method indicated by request information 2 in step 703 is an allocation method of 96 time slots (i.e., 0-95 time slots).

[0174] As shown in Figure 8, in step 803, the bandwidth of the first carrying pipe changes from 1Gbps to 5Gbps, so the range of fgOMFI changes from 0-96 to 0-479.

[0175] Step 804: The second communication device sends response information 2 to the first communication device to indicate that the second communication device supports the time slot allocation method after the first bearer pipe adjusts its bandwidth.

[0176] Step 805: The first communication device sends request information 3 to the second communication device to instruct the second communication device to take effect the new time slot allocation method at a preset time point.

[0177] Step 806: The first communication device and the second communication device take effect at a preset time point with the new time slot allocation method.

[0178] In this embodiment, steps 804-806 are similar to steps 704-706 described above. Please refer to steps 704-706 for details, which will not be repeated here.

[0179] The above sections described the process of bandwidth adjustment negotiation between communication devices in scenarios of bandwidth increase and decrease. The following section will describe various possible scenarios when negotiating time slot allocation methods between communication devices, comparing the new allocation method with the old one.

[0180] Scenario 1: After the bandwidth of the data bearer pipeline is adjusted, the number of small-granularity customers using the data bearer pipeline remains unchanged, but the number of time slots corresponding to some or all small-granularity customers changes.

[0181] For example, in the above embodiments, after the bandwidth of the first bearer channel is adjusted, the number of small-granularity customers using the first bearer channel does not change, but the number of time slots corresponding to the target small-granularity customers using the first bearer channel changes. Here, the target small-granularity customers can refer to some or all of the small-granularity customers using the first bearer channel.

[0182] For example, please refer to Figure 9, which is a schematic diagram of the change in time slot allocation before and after the bandwidth of a data bearer pipeline is increased according to an embodiment of this application. As shown in Figure 9, before the bandwidth of the data bearer pipeline is increased, the bandwidth of the data bearer pipeline is 1Gbps, corresponding to 96 time slots (i.e., time slot 0 to time slot 95), and the 96 time slots are allocated to small-granularity customer 1 and small-granularity customer 2 respectively. Among them, the time slot number corresponding to small-granularity customer 1 is an integer multiple of 3, i.e., time slot 0, time slot 3, time slot 6... time slot 93, and small-granularity customer 1 corresponds to a total of 32 time slots. The time slots corresponding to small-granularity customer 2 are the other time slots in the 96 time slots excluding the time slots occupied by small-granularity customer 1, i.e., time slot 1, time slot 2, time slot 4, time slot 5... time slot 94, time slot 95, and small-granularity customer 1 corresponds to a total of 64 time slots.

[0183] After the bandwidth of the data transport pipeline increased from 1Gbps to 5Gbps, corresponding to 480 time slots (i.e., time slots 0 to 479), these 480 time slots are still allocated to small-granularity customer 1 and small-granularity customer 2. The number of time slots corresponding to small-granularity customer 1 remains unchanged, i.e., small-granularity customer 1 still corresponds to 32 time slots. Furthermore, the time slot numbers corresponding to small-granularity customer 1 are integer multiples of 15, i.e., small-granularity customer 1 corresponds to time slots 0, 15, 30, ... 465. The time slots corresponding to small-granularity customer 2 are the remaining time slots of the 480 time slots excluding those occupied by small-granularity customer 1, i.e., time slots 1, 2, ... 14, ... 479, for a total of 448 time slots for small-granularity customer 2.

[0184] In other words, in the example shown in Figure 9, the number of time slots corresponding to small-granular customer 1 has not changed, while the number of time slots corresponding to small-granular customer 2 has changed, specifically from 64 time slots to 448 time slots.

[0185] For example, please refer to Figure 10, which is a schematic diagram of the change in time slot allocation before and after the bandwidth reduction of a data bearer pipeline according to an embodiment of this application. As shown in Figure 10, before the bandwidth of the data bearer pipeline is reduced, the bandwidth of the data bearer pipeline is 5Gbps, corresponding to 480 time slots (i.e., time slot 0 to time slot 479), and the 480 time slots are allocated to small-granularity customer 1, small-granularity customer 2, and small-granularity customer 3, respectively. Among them, the time slot number corresponding to small-granularity customer 1 is 3N, the time slot number corresponding to small-granularity customer 2 is 3N+1, and the time slot number corresponding to small-granularity customer 3 is 3N+2, where N is an integer and 0≤N≤159. That is, each small-granularity customer corresponds to 160 time slots.

[0186] After the bandwidth of the data transport pipeline is reduced, it changes from 5Gbps to 1Gbps, corresponding to 96 time slots (i.e., time slots 0 to 95). These 96 time slots are allocated to small-granularity customers 1, 2, and 3. The time slot number corresponding to small-granularity customer 1 is 3M, that of small-granularity customer 2 is 3M+1, and that of small-granularity customer 3 is 3M+2, where M is an integer and 0≤N≤31. That is, each small-granularity customer corresponds to 32 time slots.

[0187] In other words, in the example shown in Figure 10, the number of time slots corresponding to small granular customer 1, small granular customer 2 and small granular customer 3 has changed, from 160 time slots to 32 time slots.

[0188] Scenario 2: After the bandwidth of the data bearer pipeline is adjusted, the small-granularity customers using the data bearer pipeline change.

[0189] For example, in the above embodiments, compared to before the bandwidth adjustment, the number of small-granularity clients using the first bearer channel changes after the bandwidth adjustment. Furthermore, the time slot allocation method indicated by the first communication device in the first request information is used to indicate the correspondence between the changed small-granularity clients and the time slots corresponding to the first bearer channel.

[0190] For example, before the bandwidth of the first bearer pipe is adjusted, the small-granularity customers using the first bearer pipe include small-granularity customers 1 to 5; after the bandwidth of the first bearer pipe is adjusted, the small-granularity customers using the first bearer pipe include small-granularity customers 1 to 10; or, before the bandwidth of the first bearer pipe is adjusted, the small-granularity customers using the first bearer pipe include small-granularity customers 1 to 15; after the bandwidth of the first bearer pipe is adjusted, the small-granularity customers using the first bearer pipe include small-granularity customers 1 to 5; or, before the bandwidth of the first bearer pipe is adjusted, the small-granularity customers using the first bearer pipe include small-granularity customers 1 to 5, and after the bandwidth of the first bearer pipe is adjusted, the small-granularity customers using the first bearer pipe include small-granularity customers 1 to 4 and small-granularity customer 6. That is, as the bandwidth of the first bearer pipe is adjusted, the change in the small-granularity customers using the first bearer pipe can mean that the number of small-granularity customers increases or decreases, or that small-granularity customers are replaced, etc. This embodiment does not make specific limitations here.

[0191] Please refer to Figure 11, which is a schematic diagram illustrating the change in time slot allocation before and after the bandwidth reduction of another data bearer pipeline provided in this application embodiment. As shown in Figure 11, before the bandwidth of the data bearer pipeline is reduced, the bandwidth of the data bearer pipeline is 5Gbps, corresponding to 480 time slots (i.e., time slot 0 to time slot 479), and these 480 time slots are allocated to small-granularity customer 1, small-granularity customer 2, and small-granularity customer 3, respectively. The time slot number corresponding to small-granularity customer 1 is 3N, the time slot number corresponding to small-granularity customer 2 is 3N+1, and the time slot number corresponding to small-granularity customer 3 is 3N+2, where N is an integer and 0≤N≤159. That is, each small-granularity customer corresponds to 160 time slots.

[0192] After the bandwidth of the data transport pipeline is reduced, it changes from 5Gbps to 1Gbps, corresponding to 96 time slots (i.e., time slot 0 to time slot 95). These 96 time slots are allocated to small-granularity customer 1 and small-granularity customer 2, respectively. That is, the customers corresponding to the data transport pipeline change from small-granularity customer 1, small-granularity customer 2, and small-granularity customer 3 to small-granularity customer 1 and small-granularity customer 2. The time slot number corresponding to small-granularity customer 1 is 3M, and the time slot numbers corresponding to small-granularity customer 2 are 3M+1 and 3M+2, where M is an integer and 0≤N≤31.

[0193] In other words, in the example shown in Figure 11, small-granularity customer 1 changes from corresponding 160 time slots to corresponding 32 time slots, small-granularity customer 2 changes from corresponding 160 time slots to corresponding 64 time slots, while small-granularity customer 3 no longer uses the data carrying pipeline.

[0194] As described in the above embodiments, during the bandwidth adjustment negotiation process between the first and second communication devices, the negotiation content is carried by the OH field in the frame, while the payload field in the frame can normally carry the service data of small-granularity clients. Based on this, the following will describe how the first and second communication devices ensure that the data plane can transmit the service data of small-granularity clients normally while simultaneously transmitting the negotiation content during the negotiation process.

[0195] For example, before the first communication device sends the first request information to the second communication device, the first communication device generates an OH plane time slot table. The OH plane time slot table is used to indicate the time slots corresponding to the first carrier pipeline and the OH information to be transmitted in the time slots corresponding to the first carrier pipeline. The OH information is the information in the OH field of the frame. Here, the OH plane time slot table is relative to the data plane time slot table. The data plane time slot table is usually used to guide which small-granular customer data should be sent in each time slot; while the OH plane time slot table is used to guide which OH information should be sent in each time slot corresponding to the first carrier pipeline.

[0196] Then, the first communication device transmits OH information to the data plane based on the OH plane's time slot table, enabling the data plane to send a first request message, a second request message, or a third request message in the time slot corresponding to the first bearer channel. That is, when the first communication device sends a frame to the second communication device on the data plane, the first communication device transmits OH information to the data plane based on the OH plane's time slot table. This allows the data plane to organize the acquired OH information into the content of the frame's OH field in the time slot corresponding to the first bearer channel and send it out, thereby realizing the transmission of the aforementioned first, second, or third request message. It should be noted that the content of the OH plane's time slot table may change at different stages (i.e., the process of sending different request messages), thus enabling the data plane to transmit different request messages.

[0197] Understandably, a single network leased line typically includes multiple data bearer channels, each corresponding to a certain number of time slots. Within a complete time slot period corresponding to the network leased line, including all time slots corresponding to each data bearer channel, by arranging these time slots in a specific way, the service data carried by each data bearer channel can be transmitted in turn. Generally, the time slot table of the data plane is used to record the arrangement of time slots corresponding to all data bearer channels within a complete time slot period corresponding to the network leased line. Therefore, based on the time slot table of the OH plane, it is possible to determine in which time slots (i.e., the time slot corresponding to the first bearer channel) which OH information (i.e., the contents of the first request information, second request information, and third request information) needs to be transmitted, thereby ensuring that the time slot table of the data plane does not need any modification, ensuring that the service data of small-granularity customers can be sent normally, with only the content of the OH field in the frame corresponding to the small-granularity customer changing.

[0198] Similarly, before sending the first response information and the third response information, the second communication device may also pre-generate the corresponding OH plane time slot table, thereby transmitting the corresponding OH information to the data plane to ensure that the data plane can send the aforementioned first response information and third response information in the time slot corresponding to the first carrier pipe.

[0199] Optionally, to improve the efficiency of the first communication device in configuring the new time slot allocation method, the first communication device may generate a spare time slot table for the data plane based on the time slot allocation method indicated in the first request information. This spare time slot table for the data plane is used to indicate the time slot distribution of small-granularity customers in the first bearer channel after bandwidth adjustment. In addition, this spare time slot table for the data plane is also used to indicate the time slot distribution of other data bearer channels in the network leased line.

[0200] Then, at a preset time point, the first communication device switches the backup time slot table of the data plane to the main time slot table, thereby enabling the first communication device to send service data based on the new time slot allocation method after the preset time point.

[0201] In this solution, by pre-generating a backup time slot table for the data plane and then switching the pre-generated backup time slot table to the primary time slot table at a preset time point, the efficiency of time slot table switching is improved. This ensures that service data is transmitted normally according to the old time slot allocation method before the preset time point and according to the new time slot allocation method after the preset time point, ensuring that the bandwidth adjustment process does not affect the normal transmission of service data.

[0202] For example, please refer to Figure 12, which is a schematic diagram of the interaction between the OH plane and the data plane provided in an embodiment of this application. As shown in Figure 12, the OH plane includes a set of bearer pipeline mapping tables and a set of OH plane time slot tables (hereinafter referred to as OH time slot tables in Figure 12); the data plane includes a set of bearer pipeline mapping tables and a set of data plane time slot tables (hereinafter referred to as data time slot tables in Figure 12). The OH plane can send OH information to the data plane based on the OH plane time slot tables, thereby enabling the data plane to obtain the content carried in the OH field of the fgMTN frame. Based on the data plane time slot tables, the small-granularity client corresponding to each time slot can be determined, and thus the data content to be sent in each time slot can be determined.

[0203] Each set of transport pipeline mapping tables and time slot tables has a primary and a backup table. Specifically, a transport pipeline mapping table consists of a primary table and a backup table, and a time slot table consists of a primary table and a backup table. Based on this primary-backup table structure, the backup table can be pre-built and switched to the primary table at a specific time point, thus preventing changes to the transport pipeline mapping table or time slot table content from affecting the normal transmission of business data.

[0204] For example, during bandwidth adjustment, the switching between primary and backup time slot tables can be achieved through a corresponding primary table identifier register for both the OH plane and the data plane time slot tables. For instance, when the value of the primary table identifier register is 0, it indicates that time slot table A of the OH plane is the primary table; when the value of the primary table identifier register is 1, it indicates that time slot table B of the OH plane is the primary table. Therefore, by modifying the value of the primary table identifier register, a fast switching between primary and backup tables can be achieved.

[0205] The bearer pipeline mapping table for the OH plane and the bearer pipeline mapping table for the data plane serve the same purpose: guiding the generation of the time slot table. Please refer to Figure 13, which is a schematic diagram of the format of a bearer pipeline mapping table provided in an embodiment of this application. As shown in Figure 13, the bearer pipeline mapping table typically includes multiple rows, each indicating the time slot affiliation at a 1G granularity. It should be noted that indicating the time slot affiliation at a 1G granularity is merely one possible example; in practical applications, each row can also indicate the time slot affiliation at 1G, 2G, or 5G granularity, specifically related to the granularity value of the data bearer pipeline bandwidth variation. This embodiment does not specifically limit this.

[0206] In Figure 13, assuming the network device interface bandwidth is 100Gbps, the bearer pipeline mapping table contains 100 rows. The first column of the bearer pipeline mapping table indicates the row identifier in the time slot table. The second column indicates the bearer pipeline identifier corresponding to the current time slot table row identifier, i.e., the data bearer pipeline corresponding to each time slot in the time slot table. The third column indicates which row and time slot of the data bearer pipeline the current time slot table row identifier corresponds to.

[0207] For example, in Figure 13, when the time slot table row identifier is 0, the bearer pipe identifier is A and the bearer pipe row identifier is 0, indicating that the 0th row of the time slot table belongs to data bearer pipe A, and this row of time slots is the 0th row of time slots within data bearer pipe A itself. When the time slot table row identifier is 1, the bearer pipe identifier is B and the bearer pipe row identifier is 0, indicating that the 1st row of the time slot table belongs to data bearer pipe B, and this row of time slots is the 0th row of time slots within data bearer pipe B itself. When the time slot table row identifier is 2, the bearer pipe identifier is A and the bearer pipe row identifier is 1, indicating that the 2nd row of the time slot table belongs to data bearer pipe A, and this row of time slots is the 1st row of time slots within data bearer pipe A itself.

[0208] Please refer to Figure 14, which shows a time slot table for a single data bearer provided in an embodiment of this application. As shown in Figure 14, any data bearer can be divided into X*96 time slots, where X is an integer greater than or equal to 1. For example, when the bandwidth of the data bearer is 1Gbps, it can be divided into 96 time slots; when the bandwidth is 5Gbps, it can be divided into 5*96 (i.e., 480) time slots. Therefore, the time slot table for a single bearer can include one or more rows, each row representing the correspondence between the 96 time slots in the current row and the small-granularity clients. Therefore, based on the time slot table for a single bearer and the bearer mapping table shown in Figure 13, the data bearer corresponding to each row of time slots in the time slot table and the small-granularity clients corresponding to each time slot in each row can be determined.

[0209] Please refer to Figures 15 and 16. Figure 15 is a schematic diagram of a time slot table for the data plane provided in an embodiment of this application; Figure 16 is a schematic diagram of a time slot table for the OH plane provided in an embodiment of this application. Referring first to Figure 15, the time slot table for the data plane indicates the arrangement of all time slots of a network leased line within a time slot period. Specifically, the time slot table for the data plane includes multiple rows, and each row includes 96 columns. The number of rows in the time slot table for the data plane is related to the bandwidth of the network leased line, and one row corresponds to 1Gbps bandwidth, that is, a 100Gbps bandwidth network leased line corresponds to 100 rows. Furthermore, each row includes 96 columns (i.e., 0-95) to indicate the 96 time slots corresponding to each 1Gbps granularity of bandwidth. Therefore, each table in the data plane's time slot table corresponds to a unique time slot, and all tables in the entire data plane's time slot table can indicate all time slots within a complete time slot cycle (i.e., one round of data plane time slots). Furthermore, each table in the data plane's time slot table records the information of the time slot corresponding to that table. Therefore, by polling the data plane's time slot table in a certain order, the data transport pipeline corresponding to each time slot and the small-granularity clients under that data transport pipeline can be determined, thereby enabling the round-robin transmission of business data from small-granularity clients.

[0210] Referring again to Figure 16, the time slot table of the OH plane indicates the corresponding OH information for each time slot, that is, it indicates the OH information that needs to be transmitted in each time slot. Based on the time slot table of the OH plane, the first communication device can determine the OH information that needs to be transmitted in the time slot to which the first carrier pipeline belongs, and transmit the corresponding OH information to the data plane in advance. This enables the data plane to organize the acquired OH information into the content of the OH field of the frame in the time slot to which the first carrier pipeline belongs and send it out, thereby realizing the transmission of the first request information, the second request information, or the third request information mentioned above.

[0211] The bandwidth adjustment method provided by the embodiments of this application has been described above. The device used to perform the above bandwidth adjustment method will be described below.

[0212] Please refer to Figure 17, which is a schematic diagram of a communication device provided in an embodiment of this application. In one possible example, the communication device is a first communication device in fgMTN, and the communication device includes: a sending module 1701, used to send a first request message to a second communication device, the first request message being used to indicate the time slot allocation method after the bandwidth of the first bearer pipe is adjusted, the time slot allocation method being used to indicate the correspondence between small-granularity clients using the first bearer pipe and the time slots provided after the bandwidth of the first bearer pipe is adjusted, the first bearer pipe being the data bearer pipe in fgMTN; a receiving module 1702, used to receive a first response message sent by the second communication device, the first response message being used to indicate that the second communication device supports the time slot allocation method; the sending module 1701 is also used to send a second request message to the second communication device, the second request message being used to indicate that the second communication device configures the time slot allocation method to take effect at a preset time point.

[0213] In one possible implementation, the first bearer pipe is a data bearer pipe in the network leased line of fgMTN, the network leased line includes multiple data bearer pipes, and the first bearer pipe is used to carry the business data of one or more small-granularity customers.

[0214] In one possible implementation, the time slot allocation method specifically includes the correspondence between the small-granularity overhead multiframe indicator (fgOMFI) and the small-granularity customer identifier. The fgOMFI is used to indicate the sequence number of the overhead information after the bandwidth of the first bearer pipe is adjusted. The total number of overhead information in one period after the bandwidth of the first bearer pipe is adjusted is related to the adjusted bandwidth value.

[0215] In one possible implementation, the preset time point is the time point after the first communication device sends the second request information and the fgOMFI corresponding to the first bearer pipe is 0;

[0216] Alternatively, the preset time point is the time point at which the data plane time slot begins after the first communication device sends the second request information.

[0217] In one possible implementation, after the bandwidth of the first bearer is adjusted, the small-granularity customers using the first bearer change; the time slot allocation method is used to indicate the correspondence between the changed small-granularity customers and the time slots corresponding to the first bearer.

[0218] In one possible implementation, after the bandwidth of the first bearer is adjusted, the number of time slots corresponding to the target small-granularity customers using the first bearer changes.

[0219] In one possible implementation, the first request information is also used to request the second communication device to adjust the bandwidth of the first bearer channel.

[0220] In one possible implementation, the first request information indicates a request for the second communication device to adjust the bandwidth of the first bearer pipe via the target bit in the overhead (OH) field of the frame.

[0221] In one possible implementation, before sending the first request information to the second communication device, the sending module 1701 is further configured to send a third request information to the second communication device, the third request information being used to request the second communication device to adjust the bandwidth of the first bearer channel; the receiving module 1702 is further configured to receive a third response information sent by the second communication device, the third response information being used to instruct the second communication device to support adjusting the bandwidth of the first bearer channel.

[0222] In one possible implementation, the device further includes: a processing module 1703;

[0223] Processing module 1703 is used to generate a time slot table for the OH plane. The time slot table for the OH plane is used to indicate the time slot corresponding to the first carrier pipe and the OH information that needs to be transmitted in the time slot corresponding to the first carrier pipe. The OH information is the information in the OH field of the frame.

[0224] The processing module 1703 is also used to transmit OH information to the data plane based on the time slot table of the OH plane, so that the data plane can send the first request information or the second request information in the time slot corresponding to the first carrier pipeline.

[0225] In one possible implementation, the device further includes: a processing module 1703;

[0226] Processing module 1703 is used to generate a spare time slot table for the data plane. The spare time slot table for the data plane is used to indicate the time slot distribution of small-particle customers in the first bearer pipeline after bandwidth adjustment.

[0227] The processing module 1703 is also used to switch the backup time slot table of the data plane to the main time slot table at a preset time point.

[0228] Please refer to Figure 18, which is a schematic diagram of a communication device provided in an embodiment of this application. In one possible example, the communication device is a second communication device in fgMTN, and the communication device includes: a receiving module 1801, used to receive a first request information sent by a first communication device, the first request information being used to indicate the time slot allocation method after the bandwidth of the first bearer pipe is adjusted, the time slot allocation method being used to indicate the correspondence between small-granularity clients using the first bearer pipe and the time slots provided after the bandwidth of the first bearer pipe is adjusted, the first bearer pipe being the data bearer pipe in fgMTN; a sending module 1802, used to send a first response information to the first communication device, the first response information being used to indicate that the second communication device supports the time slot allocation method; the receiving module 1801 is also used to receive a second request information sent by the first communication device, the second request information being used to indicate that the second communication device configures the time slot allocation method to take effect at a preset time point.

[0229] In one possible implementation, the first bearer pipe is a data bearer pipe in the network leased line of fgMTN, the network leased line includes multiple data bearer pipes, and the first bearer pipe is used to carry the business data of one or more small-granularity customers.

[0230] In one possible implementation, the time slot allocation method specifically includes the correspondence between the small-granularity overhead multiframe indicator (fgOMFI) and the small-granularity customer identifier. The fgOMFI is used to indicate the sequence number of the overhead information after the bandwidth of the first bearer pipe is adjusted. The total number of overhead information in one period after the bandwidth of the first bearer pipe is adjusted is related to the adjusted bandwidth value.

[0231] In one possible implementation, the preset time point is the time point after the first communication device sends the second request information and the fgOMFI corresponding to the first bearer pipe is 0;

[0232] Alternatively, the preset time point is the time point at which the data plane time slot begins after the first communication device sends the second request information.

[0233] In one possible implementation, after the bandwidth of the first bearer is adjusted, the small-granularity customers using the first bearer change; the time slot allocation method is used to indicate the correspondence between the changed small-granularity customers and the time slots corresponding to the first bearer.

[0234] In one possible implementation, after the bandwidth of the first bearer is adjusted, the number of time slots corresponding to the target small-granularity customers using the first bearer changes.

[0235] In one possible implementation, the first request information is also used to request the second communication device to adjust the bandwidth of the first bearer channel.

[0236] In one possible implementation, the first request information indicates a request for the second communication device to adjust the bandwidth of the first bearer channel via the target bit in the OH field of the frame.

[0237] In one possible implementation, before receiving the first request information sent by the first communication device, the receiving module 1801 is further configured to receive a third request information sent by the first communication device, the third request information being used to request the second communication device to adjust the bandwidth of the first bearer channel; the sending module 1802 is further configured to send a third response information to the first communication device, the third response information being used to instruct the second communication device to support adjusting the bandwidth of the first bearer channel.

[0238] Figure 19 is a schematic diagram of a network device provided in an embodiment of this application. The network device is equipped with the communication device shown in Figure 17 or 18 above, and the network device is implemented using a general bus architecture.

[0239] The network device includes at least one processor 1901, a communication bus 1902, a memory 1903, and at least one communication interface 1904.

[0240] Optionally, the processor 1901 is a general-purpose CPU, NP, microprocessor, or one or more integrated circuits for implementing the solutions of this application, such as application-specific integrated circuits (ASICs), programmable logic devices (PLDs), or combinations thereof. The aforementioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), generic array logic (GAL), or any combination thereof.

[0241] The communication bus 1902 is used to transmit information between the aforementioned components. The communication bus 1902 is divided into an address bus, a data bus, and a control bus. For ease of illustration, it is represented by only one thick line in the figure, but this does not indicate that there is only one bus or one type of bus.

[0242] Optionally, memory 1903 is read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions. Alternatively, memory 1903 is random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions. Alternatively, memory 1903 is electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited to these. Optionally, memory 1903 exists independently and is connected to processor 1901 via communication bus 1902. Optionally, memory 1903 and processor 1901 are integrated together.

[0243] Communication interface 1904 uses any transceiver-like device for communicating with other devices or communication networks. Communication interface 1904 includes a wired communication interface. Optionally, communication interface 1904 also includes a wireless communication interface. The wired communication interface is, for example, an Ethernet interface. The Ethernet interface is an optical interface, an electrical interface, or a combination thereof. The wireless communication interface is a wireless local area network (WLAN) interface, a cellular network communication interface, or a combination thereof, etc.

[0244] In a specific implementation, as one example, processor 1901 includes one or more CPUs, such as CPU0 and CPU1 as shown in FIG19.

[0245] In a specific implementation, as one example, the network device includes multiple processors, such as processor 1901 and processor 1905 as shown in Figure 19. Each of these processors is either a single-core processor (single-CPU) or a multi-core processor (multi-CPU). Here, a processor refers to one or more devices, circuits, and / or processing cores used to process data (such as computer program instructions).

[0246] In some embodiments, memory 1903 is used to store program code 1919 for executing the scheme of this application, and processor 1901 executes the program code 1919 stored in memory 1903. That is, the network device implements the above-described method embodiments through processor 1901 and program code 1919 in memory 1903.

[0247] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. Wherein, "A refers to B" means that A is the same as B or A is a simple variation of B.

[0248] The terms "first" and "second," etc., used in the specification and claims of this application are used to distinguish different objects, not to describe a specific order of objects, and should not be construed as indicating or implying relative importance. For example, "first speed limit lane" and "second speed limit lane" are used to distinguish different speed limit lanes, not to describe a specific order of speed limit lanes, and should not be construed as the first speed limit lane being more important than the second speed limit lane.

[0249] In the embodiments of this application, unless otherwise stated, "at least one" means one or more, and "multiple" means two or more.

[0250] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented in software, they can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0251] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A bandwidth adjustment method, characterized in that, A first communication device applied in a small-granularity metropolitan area network (fgMTN) includes: The first communication device sends a first request message to the second communication device. The first request message is used to indicate the time slot allocation method after the bandwidth of the first bearer is adjusted. The time slot allocation method is used to indicate the correspondence between small-granularity clients using the first bearer and the time slots provided after the bandwidth of the first bearer is adjusted. The first bearer is the data bearer in the fgMTN. The first communication device receives a first response information sent by the second communication device, the first response information being used to indicate that the second communication device supports the time slot allocation method; The first communication device sends a second request message to the second communication device, the second request message being used to instruct the second communication device to configure the time slot allocation method to take effect at a preset time point.

2. The method according to claim 1, characterized in that, The first bearer pipe is the data bearer pipe in the network leased line of the fgMTN. The network leased line includes multiple data bearer pipes, and the first bearer pipe is used to carry the business data of one or more small-granularity customers.

3. The method according to claim 1 or 2, characterized in that, The time slot allocation method specifically includes the correspondence between the small-granularity overhead multiframe indicator (fgOMFI) and the small-granularity customer identifier. The fgOMFI is used to indicate the sequence number of the overhead information after the bandwidth of the first bearer pipe is adjusted. The total number of overhead information in one period after the bandwidth of the first bearer pipe is adjusted is related to the adjusted bandwidth value.

4. The method according to claim 3, characterized in that, The preset time point is the time point after the first communication device sends the second request information and the fgOMFI corresponding to the first bearer pipe is 0. Alternatively, the preset time point is the time point at which the data plane time slot begins after the first communication device sends the second request information.

5. The method according to any one of claims 1-4, characterized in that, After the bandwidth of the first bearer channel is adjusted, the small-granularity customers using the first bearer channel change; The time slot allocation method is used to indicate the correspondence between the changed small particle customers and the time slots corresponding to the first carrying pipeline.

6. The method according to any one of claims 1-5, characterized in that, After the bandwidth of the first bearer channel is adjusted, the number of time slots corresponding to the target small-granularity customers using the first bearer channel changes.

7. The method according to any one of claims 1-6, characterized in that, The first request information is also used to request the second communication device to adjust the bandwidth of the first bearer channel.

8. The method according to claim 7, characterized in that, The first request information indicates a request for the second communication device to adjust the bandwidth of the first bearer channel by using the target bit in the overhead (OH) field of the frame.

9. The method according to any one of claims 1-6, characterized in that, Before the first communication device sends the first request information to the second communication device, the method further includes: The first communication device sends a third request message to the second communication device, the third request message being used to request the second communication device to adjust the bandwidth of the first bearer channel; The first communication device receives a third response message sent by the second communication device, the third response message being used to instruct the second communication device to support adjusting the bandwidth of the first bearer channel.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: The first communication device generates a time slot table for the OH plane. The time slot table for the OH plane is used to indicate the time slot corresponding to the first carrier pipeline and the OH information that needs to be transmitted in the time slot corresponding to the first carrier pipeline. The OH information is the information in the OH field of the frame. The first communication device transmits OH information to the data plane based on the time slot table of the OH plane, so that the data plane sends the first request information or the second request information in the time slot corresponding to the first carrier pipeline.

11. The method according to any one of claims 1-10, characterized in that, The method further includes: The first communication device generates a spare time slot table for the data plane, which is used to indicate the time slot distribution of small-particle customers in the first bearer pipeline after bandwidth adjustment. The first communication device switches the backup time slot table of the data plane to the main time slot table at the preset time point.

12. A bandwidth adjustment method, characterized in that, A second communication device used in fgMTN includes: The second communication device receives a first request message sent by the first communication device. The first request message is used to indicate the time slot allocation method after the bandwidth of the first bearer is adjusted. The time slot allocation method is used to indicate the correspondence between small-granularity clients using the first bearer and the time slots provided after the bandwidth of the first bearer is adjusted. The first bearer is the data bearer in the fgMTN. The second communication device sends a first response message to the first communication device, the first response message being used to indicate that the second communication device supports the time slot allocation method; The second communication device receives a second request message sent by the first communication device. The second request message is used to instruct the second communication device to configure the time slot allocation method to take effect at a preset time point.

13. The method according to claim 12, characterized in that, The first bearer pipe is the data bearer pipe in the network leased line of the fgMTN. The network leased line includes multiple data bearer pipes, and the first bearer pipe is used to carry the business data of one or more small-granularity customers.

14. The method according to claim 12 or 13, characterized in that, The time slot allocation method specifically includes the correspondence between the small-granularity overhead multiframe indicator (fgOMFI) and the small-granularity customer identifier. The fgOMFI is used to indicate the sequence number of the overhead information after the bandwidth of the first bearer pipe is adjusted. The total number of overhead information in one period after the bandwidth of the first bearer pipe is adjusted is related to the adjusted bandwidth value.

15. The method according to claim 14, characterized in that, The preset time point is the time point after the first communication device sends the second request information and the fgOMFI corresponding to the first bearer pipe is 0. Alternatively, the preset time point is the time point at which the data plane time slot begins after the first communication device sends the second request information.

16. The method according to any one of claims 12-15, characterized in that, After the bandwidth of the first bearer channel is adjusted, the small-granularity customers using the first bearer channel change; The time slot allocation method is used to indicate the correspondence between the changed small particle customers and the time slots corresponding to the first carrying pipeline.

17. The method according to any one of claims 12-16, characterized in that, After the bandwidth of the first bearer channel is adjusted, the number of time slots corresponding to the target small-granularity customers using the first bearer channel changes.

18. The method according to any one of claims 12-17, characterized in that, The first request information is also used to request the second communication device to adjust the bandwidth of the first bearer channel.

19. The method according to claim 18, characterized in that, The first request information indicates a request for the second communication device to adjust the bandwidth of the first bearer channel by using the target bit in the OH field of the frame.

20. The method according to any one of claims 12-17, characterized in that, Before the second communication device receives the first request information sent by the first communication device, the method further includes: The second communication device receives a third request message sent by the first communication device, the third request message being used to request the second communication device to adjust the bandwidth of the first bearer channel; The second communication device sends a third response message to the first communication device, the third response message being used to instruct the second communication device to support adjusting the bandwidth of the first bearer channel.

21. A communication device, characterized in that, The device is a first communication device in fgMTN, and the device includes multiple functional modules that interact with each other to implement the method as described in any one of claims 1-11.

22. A communication device, characterized in that, The device is a second communication device in fgMTN, and the device includes multiple functional modules that interact with each other to implement the method as described in any one of claims 12-20.

23. A network device comprising a processor and a memory, the memory for storing program code, the processor for calling the program code in the memory to cause the network device to perform the method as claimed in any one of claims 1-20.

24. A computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-20.

25. A computer program product, characterized in that, Includes program code that, when a computer runs the computer program product, causes the computer to perform the method as described in any one of claims 1-20.

Images