Bandwidth adjustment method and network device
By using overhead fields in the communication network to achieve bandwidth adjustment, the problem of low bandwidth adjustment efficiency when the network management system manages multiple networks is solved, the efficiency and reliability of bandwidth adjustment are improved, and the flexible adjustment of service bandwidth is ensured.
Patent Information
- Application Number
- PCT/CN2024/095501
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-06-02
- Filing Date
- 2024-05-27
- Publication Date
- 2024-12-05
AI Technical Summary
In the field of communication, when the network management system manages multiple networks, the uplink and downlink bandwidth efficiency of the service is low, especially when the network management system is offline, it cannot perform bandwidth adjustment, resulting in low reliability.
Bandwidth adjustment is achieved by using overhead fields (including mode fields and bandwidth adjustment fields) between source nodes, sink nodes and intermediate nodes, allowing source nodes to initiate uplink and downlink bandwidth adjustments, reducing the load of network management systems. And bandwidth adjustment can still be performed when the network management system is offline.
It improves the efficiency and reliability of bandwidth adjustment, reduces the interaction complexity of the network management system, ensures flexible adjustment of service bandwidth, and can even make effective adjustments when the network management system is offline.
Smart Images

Figure CN2024095501_05122024_PF_FP_ABST
Abstract
Description
Bandwidth adjustment method and network device
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on June 2, 2023, with application number 202310654584.3 and application name “A Bandwidth Adjustment Method and Network Device”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communication technology, and in particular to a bandwidth adjustment method and a network device. Background Art
[0003] In the communications field, network management systems manage multiple networks, each of which carries multiple services. When the channel bandwidth (including uplink and downlink bandwidth) of a service needs to be adjusted, the network management system sends a bandwidth adjustment request to the source node and sink node in the network transmitting the service. After receiving the bandwidth adjustment request, the source node and sink node adjust the uplink or downlink bandwidth of the service. Because the network management system manages multiple networks, when the uplink and downlink bandwidth of a service need to be adjusted, the network management system sends bandwidth adjustment requests to both the source node and sink node separately, resulting in low bandwidth adjustment efficiency.
[0004] Summary of the Invention
[0005] The present application provides a bandwidth adjustment method and a network device, which can solve the above problems.
[0006] In a first aspect, the present application provides a bandwidth adjustment method. The method can be applied to a source node and includes: receiving a bandwidth adjustment request, the bandwidth adjustment request being used to instruct adjustment of the bandwidth of a first service; determining, based on the bandwidth adjustment request, a value of an overhead field in first service data, the overhead field including a mode field and a bandwidth adjustment field, the value of the mode field representing one of multiple bandwidth adjustment modes, the multiple bandwidth adjustment modes including unidirectional bandwidth adjustment and bidirectional bandwidth adjustment, the value of the bandwidth adjustment field representing an increase in bandwidth or a decrease in bandwidth; sending the first service data to a destination node via an intermediate node; the destination node being configured to, upon receiving the first service data, adjust the bandwidth of the first service based on the value of the overhead field.
[0007] In the above implementation, the overhead field includes a mode field and a bandwidth adjustment field, which can be used to implement unidirectional or bidirectional bandwidth adjustment. Furthermore, compared to related technologies where the source node and sink node initiate uplink and downlink bandwidth adjustments respectively, this solution initiates both uplink and downlink bandwidth adjustments from the source node. This allows both uplink and downlink bandwidth adjustments to be indicated within the same overhead, thereby improving bandwidth adjustment efficiency.
[0008] In combination with the first aspect, in one possible implementation, the unidirectional bandwidth adjustment includes reducing the uplink bandwidth, increasing the uplink bandwidth, reducing the downlink bandwidth, and increasing the downlink bandwidth; the bidirectional bandwidth adjustment includes reducing the uplink bandwidth and reducing the downlink bandwidth, increasing the uplink bandwidth and increasing the downlink bandwidth, reducing the uplink bandwidth and increasing the downlink bandwidth, and increasing the uplink bandwidth and reducing the downlink bandwidth.
[0009] In the above implementation, various types of bandwidth adjustments can be implemented through the mode field to meet the requirements of various bandwidth adjustment scenarios.
[0010] In combination with the first aspect, in a possible implementation, when adjusting the bandwidth of the first service includes reducing the uplink bandwidth of the first service and / or increasing the downlink bandwidth of the first service, before determining the value of the overhead field in the first service data according to the bandwidth adjustment request, the method also includes: reducing the uplink bandwidth of the first service and / or increasing the downlink bandwidth of the first service according to the bandwidth adjustment request.
[0011] In combination with the first aspect, in a possible implementation, when adjusting the bandwidth of the first service includes increasing the uplink bandwidth of the first service and / or reducing the downlink bandwidth of the first service, the method further includes: receiving second service data sent by the intermediate node, the value of the mode field in the second service data is different from the value of the mode field in the first service data, and the host node is used to send the second service data to the intermediate node after adjusting the bandwidth of the first service; increasing the uplink bandwidth of the first service and / or reducing the downlink bandwidth of the first service according to the value of the overhead field in the second service data.
[0012] In combination with the first aspect, in a possible implementation manner, the overhead field further includes a timeslot adjustment quantity field for uplink bandwidth and / or a timeslot adjustment quantity field for downlink bandwidth.
[0013] With reference to the first aspect, in a possible implementation manner, receiving the bandwidth adjustment request includes: receiving the bandwidth adjustment request from a user-side node, or receiving the bandwidth adjustment request from a network management system.
[0014] In the above implementation, the source node receives bandwidth adjustment requests from the user side, which reduces the network management system's involvement in the bandwidth adjustment process and reduces the complexity of interactions during the bandwidth adjustment process. Furthermore, this solution can address the issue of bandwidth adjustment being unable to be performed when the network management system is offline, thereby improving the reliability of bandwidth adjustment.
[0015] In a second aspect, the present application also provides a bandwidth adjustment method. The method can be applied to an intermediate node and includes: receiving first service data sent by a source node, where the value of an overhead field in the first service data is determined by the source node based on a received bandwidth adjustment request, where the bandwidth adjustment request is used to indicate adjustment of the bandwidth of the first service; the overhead field includes a service identifier of the first service, the mode field, the bandwidth adjustment field, and the bandwidth increment field; and sending the first service data to a destination node, where the destination node is configured to adjust the bandwidth of the first service based on the value of the overhead field after receiving the first service data.
[0016] In combination with the second aspect, in one possible implementation, the unidirectional bandwidth adjustment includes reducing the uplink bandwidth, increasing the uplink bandwidth, reducing the downlink bandwidth, or increasing the downlink bandwidth; the bidirectional bandwidth adjustment includes reducing the uplink bandwidth and reducing the downlink bandwidth, increasing the uplink bandwidth and increasing the downlink bandwidth, reducing the uplink bandwidth and increasing the downlink bandwidth, and increasing the uplink bandwidth and reducing the downlink bandwidth.
[0017] In combination with the second aspect, in a possible implementation, when adjusting the bandwidth of the first service includes reducing the uplink bandwidth of the first service and / or increasing the downlink bandwidth of the first service, before sending the first service data to the host node, the method also includes: reducing the uplink bandwidth of the first service and / or increasing the downlink bandwidth of the first service according to the value of the overhead field in the first service data.
[0018] In combination with the second aspect, in a possible implementation, when adjusting the bandwidth of the first service includes increasing the uplink bandwidth of the first service and / or reducing the downlink bandwidth of the first service, the method further includes: receiving second service data sent by the destination node, the destination node being used to send the second service data after adjusting the bandwidth of the first service, the value of the mode field in the second service data being different from the value of the mode field in the first service data; increasing the uplink bandwidth of the first service and / or reducing the downlink bandwidth of the first service according to the value of the overhead field in the second service data.
[0019] In combination with the second aspect, in a possible implementation manner, the overhead field further includes a timeslot adjustment quantity field for uplink bandwidth and / or a timeslot adjustment quantity field for downlink bandwidth.
[0020] With reference to the second aspect, in a possible implementation manner, the source node is configured to receive the bandwidth adjustment request from a user-side node or from a network management system.
[0021] In a third aspect, the present application also provides a bandwidth adjustment method. The method can be applied to a destination node and includes: receiving first service data sent by an intermediate node, wherein the value of an overhead field in the first service data is determined by the source node based on a received bandwidth adjustment request, wherein the bandwidth adjustment request is used to indicate adjustment of the bandwidth of the first service; the overhead field includes a service identifier of the first service, the mode field, the bandwidth adjustment field, and the bandwidth increment field; and adjusting the bandwidth of the first service based on the value of the overhead field in the first service data.
[0022] In combination with the third aspect, in one possible implementation, the unidirectional bandwidth adjustment includes reducing the uplink bandwidth, increasing the uplink bandwidth, reducing the downlink bandwidth, or increasing the downlink bandwidth; the bidirectional bandwidth adjustment includes reducing the uplink bandwidth and reducing the downlink bandwidth, increasing the uplink bandwidth and increasing the downlink bandwidth, reducing the uplink bandwidth and increasing the downlink bandwidth, and increasing the uplink bandwidth and reducing the downlink bandwidth.
[0023] In combination with the third aspect, in a possible implementation, when adjusting the bandwidth of the first service includes increasing the uplink bandwidth of the first service and / or reducing the downlink bandwidth of the first service, after adjusting the bandwidth of the first service according to the value of the overhead field in the first service data, the method further includes: determining second service data, the value of the pattern field in the second service data is different from the value of the pattern field in the first service data; sending the second service data to the source end node via the intermediate node, and the intermediate node and the source end node are used to increase the uplink bandwidth of the first service and / or reduce the downlink bandwidth of the first service according to the value of the overhead field in the second service data.
[0024] In combination with the third aspect, in a possible implementation, the overhead field further includes a timeslot adjustment quantity field for uplink bandwidth and / or a timeslot adjustment quantity field for downlink bandwidth.
[0025] With reference to the third aspect, in a possible implementation manner, the source node is configured to receive the bandwidth adjustment request from a user-side node or from a network management system.
[0026] In a fourth aspect, the present application further provides a bandwidth adjustment device. The bandwidth adjustment device can be applied to a source node. The bandwidth adjustment device includes a receiving module, an adjustment module, and a sending module.
[0027] The receiving module is used to receive a bandwidth adjustment request, where the bandwidth adjustment request is used to instruct adjustment of the bandwidth of the first service.
[0028] The adjustment module is used to determine the value of the overhead field in the first service data according to the bandwidth adjustment request, where the overhead field includes a mode field and a bandwidth adjustment field. The value of the mode field represents one of multiple bandwidth adjustment modes, where the multiple bandwidth adjustment modes include unidirectional bandwidth adjustment and bidirectional bandwidth adjustment. The value of the bandwidth adjustment field represents increasing the bandwidth or decreasing the bandwidth.
[0029] The sending module is used to send the first service data to the destination node via the intermediate node; the destination node is used to adjust the bandwidth of the first service according to the value of the overhead field after receiving the first service data.
[0030] In combination with the fourth aspect, in one possible implementation, the unidirectional bandwidth adjustment includes reducing the uplink bandwidth, increasing the uplink bandwidth, reducing the downlink bandwidth, and increasing the downlink bandwidth; the bidirectional bandwidth adjustment includes reducing the uplink bandwidth and reducing the downlink bandwidth, increasing the uplink bandwidth and increasing the downlink bandwidth, reducing the uplink bandwidth and increasing the downlink bandwidth, and increasing the uplink bandwidth and reducing the downlink bandwidth.
[0031] In combination with the fourth aspect, in a possible implementation, when adjusting the bandwidth of the first service includes reducing the uplink bandwidth of the first service and / or increasing the downlink bandwidth of the first service, before determining the value of the overhead field in the first service data according to the bandwidth adjustment request, the adjustment module is also used to: reduce the uplink bandwidth of the first service and / or increase the downlink bandwidth of the first service according to the bandwidth adjustment request.
[0032] In combination with the fourth aspect, in a possible implementation, when adjusting the bandwidth of the first service includes increasing the uplink bandwidth of the first service and / or reducing the downlink bandwidth of the first service, the receiving module is also used to: receive second service data sent by the intermediate node, the value of the mode field in the second service data is different from the value of the mode field in the first service data, and the host node is used to send the second service data to the intermediate node after adjusting the bandwidth of the first service; the receiving module is also used to: increase the uplink bandwidth of the first service and / or reduce the downlink bandwidth of the first service according to the value of the overhead field in the second service data.
[0033] In combination with the fourth aspect, in a possible implementation, the overhead field further includes a timeslot adjustment quantity field for uplink bandwidth and / or a timeslot adjustment quantity field for downlink bandwidth.
[0034] With reference to the fourth aspect, in a possible implementation manner, the receiving module is specifically configured to: receive the bandwidth adjustment request from a user-side node, or receive the bandwidth adjustment request from a network management system.
[0035] In a fifth aspect, the present application provides a bandwidth adjustment device. The bandwidth adjustment device can be applied to an intermediate node. The bandwidth adjustment device can include a receiving module and a sending module.
[0036] Among them, the receiving module is used to receive the first service data sent by the source end node, and the value of the overhead field in the first service data is determined by the source end node based on the received bandwidth adjustment request, and the bandwidth adjustment request is used to indicate the adjustment of the bandwidth of the first service; the overhead field includes the service identifier of the first service, the mode field, the bandwidth adjustment field and the bandwidth increment field.
[0037] The sending module is configured to send the first service data to a destination node, and the destination node is configured to adjust the bandwidth of the first service according to the value of the overhead field after receiving the first service data.
[0038] In combination with the fifth aspect, in one possible implementation, the unidirectional bandwidth adjustment includes reducing the uplink bandwidth, increasing the uplink bandwidth, reducing the downlink bandwidth, or increasing the downlink bandwidth; the bidirectional bandwidth adjustment includes reducing the uplink bandwidth and reducing the downlink bandwidth, increasing the uplink bandwidth and increasing the downlink bandwidth, reducing the uplink bandwidth and increasing the downlink bandwidth, and increasing the uplink bandwidth and reducing the downlink bandwidth.
[0039] In combination with the fifth aspect, in a possible implementation, when adjusting the bandwidth of the first service includes reducing the uplink bandwidth of the first service and / or increasing the downlink bandwidth of the first service, before sending the first service data to the host node, the device also includes an adjustment module, and the adjustment module is used to: reduce the uplink bandwidth of the first service and / or increase the downlink bandwidth of the first service according to the value of the overhead field in the first service data.
[0040] In conjunction with the fifth aspect, in one possible implementation, when adjusting the bandwidth of the first service includes increasing the uplink bandwidth of the first service and / or decreasing the downlink bandwidth of the first service, the receiving module is further configured to: receive second service data sent by the destination node, the destination node being configured to send the second service data after adjusting the bandwidth of the first service, the value of the mode field in the second service data being different from the value of the mode field in the first service data. The adjustment module is further configured to increase the uplink bandwidth of the first service and / or decrease the downlink bandwidth of the first service based on the value of the overhead field in the second service data.
[0041] In combination with the fifth aspect, in a possible implementation, the overhead field further includes a timeslot adjustment quantity field for uplink bandwidth and / or a timeslot adjustment quantity field for downlink bandwidth.
[0042] With reference to the fifth aspect, in a possible implementation manner, the source node is configured to receive the bandwidth adjustment request from a user-side node or from a network management system.
[0043] In a sixth aspect, the present application provides a bandwidth adjustment device, which can be applied to a sink node and includes: a receiving module and an adjustment module.
[0044] Among them, the receiving module is used to receive the first service data sent by the intermediate node, and the value of the overhead field in the first service data is determined by the source end node based on the received bandwidth adjustment request, and the bandwidth adjustment request is used to indicate the adjustment of the bandwidth of the first service; the overhead field includes the service identifier of the first service, the mode field, the bandwidth adjustment field and the bandwidth increment field.
[0045] The adjustment module is configured to adjust the bandwidth of the first service according to the value of the overhead field in the first service data.
[0046] In combination with the sixth aspect, in one possible implementation, the unidirectional bandwidth adjustment includes reducing the uplink bandwidth, increasing the uplink bandwidth, reducing the downlink bandwidth, or increasing the downlink bandwidth; the bidirectional bandwidth adjustment includes reducing the uplink bandwidth and reducing the downlink bandwidth, increasing the uplink bandwidth and increasing the downlink bandwidth, reducing the uplink bandwidth and increasing the downlink bandwidth, and increasing the uplink bandwidth and reducing the downlink bandwidth.
[0047] In conjunction with the sixth aspect, in a possible implementation, when adjusting the bandwidth of the first service includes increasing the uplink bandwidth of the first service and / or reducing the downlink bandwidth of the first service, after adjusting the bandwidth of the first service according to the value of the overhead field in the first service data, the adjustment module is further used to: determine the second service data, the value of the mode field in the second service data is different from the value of the mode field in the first service data. The device also includes a sending module. The sending module is used to send the second service data to the source node via the intermediate node, and the intermediate node and the source node are used to increase the uplink bandwidth of the first service and / or reduce the downlink bandwidth of the first service according to the value of the overhead field in the second service data.
[0048] In combination with the sixth aspect, in a possible implementation manner, the overhead field further includes a timeslot adjustment quantity field for uplink bandwidth and / or a timeslot adjustment quantity field for downlink bandwidth.
[0049] With reference to the sixth aspect, in a possible implementation manner, the source node is configured to receive the bandwidth adjustment request from a user-side node or from a network management system.
[0050] In a seventh aspect, the present application further provides a network device. The network device includes: a processor and a memory, the processor being configured to execute a computer program stored in the memory to implement the method described in the first aspect and any optional embodiment thereof, or the method described in the second aspect and any optional embodiment thereof, or the method described in the third aspect and any optional embodiment thereof.
[0051] In an eighth aspect, the present application provides a bandwidth adjustment device. The bandwidth adjustment device includes a processor and a memory. The processor is configured to execute a computer program stored in the memory to implement the method described in the first aspect and any optional embodiment thereof, or the method described in the second aspect and any optional embodiment thereof, or the method described in the third aspect and any optional embodiment thereof.
[0052] In the ninth aspect, the present application provides a computer-readable storage medium, which stores instructions. When the computer-readable storage medium is run on a computer, it enables the computer to implement the method described in the first aspect and any optional embodiment thereof, or implement the method described in the second aspect and any optional embodiment thereof, or implement the method described in the third aspect and any optional embodiment thereof.
[0053] In the tenth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to implement the method described in the first aspect and any optional embodiment thereof, or the method described in the second aspect and any optional embodiment thereof, or the method described in the third aspect and any optional embodiment thereof.
[0054] Any of the devices, computer storage media, or computer program products provided above are used to execute the method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding schemes in the corresponding methods provided above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0055] FIG1 is a schematic diagram of the structure of a metropolitan area transmission network using a small-granularity dedicated line technology provided in an embodiment of the present application;
[0056] FIG2 is a schematic diagram of the structure of a communication path in a metropolitan area transmission network provided in an embodiment of the present application;
[0057] FIG3a is a schematic diagram of a frame structure of a segment layer in a metropolitan area transmission network provided by an embodiment of the present application;
[0058] FIG3 b is a schematic structural diagram of a fine-grained basic unit of a segment layer provided in an embodiment of the present application;
[0059] FIG3c is a schematic structural diagram of a payload area of a segment layer provided in an embodiment of the present application;
[0060] FIG3d is a schematic diagram of the structure of an overhead field of a segment layer provided by the present application;
[0061] FIG4 is a schematic structural diagram of a bandwidth adjustment system in a related art provided by this application;
[0062] FIG5a is a schematic diagram of an overhead field when reducing uplink bandwidth in a related technology provided by the present application;
[0063] FIG5b is a schematic diagram of an overhead field when increasing uplink bandwidth in a related technology provided by this application;
[0064] FIG6 is a schematic structural diagram of a bandwidth adjustment system provided in an embodiment of the present application;
[0065] FIG7 is a schematic diagram of the structure of an overhead field of a segment layer provided in an embodiment of the present application;
[0066] FIG8a is a flowchart of reducing uplink bandwidth and reducing downlink bandwidth provided by an embodiment of the present application;
[0067] FIG8b is a schematic diagram of an overhead field when both uplink bandwidth and downlink bandwidth are reduced, provided by an embodiment of the present application;
[0068] FIG8c is a schematic diagram of another overhead field when both uplink bandwidth and downlink bandwidth are reduced, provided by an embodiment of the present application;
[0069] FIG8 d is a schematic diagram of another overhead field when both uplink bandwidth and downlink bandwidth are reduced, provided by an embodiment of the present application;
[0070] FIG9a is a flow chart of increasing uplink bandwidth and downlink bandwidth according to an embodiment of the present application;
[0071] FIG9b is a schematic diagram of an overhead field when increasing both uplink bandwidth and downlink bandwidth, provided by an embodiment of the present application;
[0072] FIG9c is a schematic diagram of another overhead field when increasing uplink bandwidth and downlink bandwidth according to an embodiment of the present application;
[0073] FIG9 d is a schematic diagram of another overhead field when increasing both uplink bandwidth and downlink bandwidth according to an embodiment of the present application;
[0074] FIG10a is a flowchart of another method for increasing uplink bandwidth and downlink bandwidth provided by an embodiment of the present application;
[0075] FIG10b is a schematic diagram of another overhead field when increasing uplink bandwidth and downlink bandwidth provided by an embodiment of the present application;
[0076] FIG10c is a schematic diagram of another overhead field when increasing both uplink bandwidth and downlink bandwidth according to an embodiment of the present application;
[0077] FIG10d is a schematic diagram of another overhead field when increasing uplink bandwidth and downlink bandwidth according to an embodiment of the present application;
[0078] FIG11a is a flow chart of reducing uplink bandwidth and increasing downlink bandwidth provided by an embodiment of the present application;
[0079] FIG11b is a schematic diagram of an overhead field when reducing the uplink bandwidth and increasing the downlink bandwidth according to an embodiment of the present application;
[0080] FIG12a is a flow chart of increasing uplink bandwidth and reducing downlink bandwidth provided by an embodiment of the present application;
[0081] FIG12b is a schematic diagram of an overhead field when increasing the uplink bandwidth and reducing the downlink bandwidth provided by an embodiment of the present application;
[0082] FIG13a is a flow chart of reducing downlink bandwidth provided by an embodiment of the present application;
[0083] FIG13b is a schematic diagram of an overhead field for reducing downlink bandwidth provided by an embodiment of the present application;
[0084] FIG13c is a schematic diagram of another overhead field for reducing downlink bandwidth provided by an embodiment of the present application;
[0085] FIG14a is a flow chart of increasing downlink bandwidth provided by an embodiment of the present application;
[0086] FIG14b is a schematic diagram of an overhead field when increasing downlink bandwidth provided by an embodiment of the present application;
[0087] FIG14c is a schematic diagram of another overhead field for increasing downlink bandwidth provided by an embodiment of the present application;
[0088] FIG15a is a flowchart of reducing uplink bandwidth provided by an embodiment of the present application;
[0089] FIG15b is a schematic diagram of an overhead field when reducing uplink bandwidth provided by an embodiment of the present application;
[0090] FIG15c is a schematic diagram of another overhead field for reducing uplink bandwidth provided by an embodiment of the present application;
[0091] FIG16a is a flow chart of increasing uplink bandwidth provided by an embodiment of the present application;
[0092] FIG16b is a schematic diagram of an overhead field when increasing uplink bandwidth provided by an embodiment of the present application;
[0093] FIG16c is a schematic diagram of another overhead field for increasing uplink bandwidth provided by an embodiment of the present application;
[0094] FIG17 is a schematic structural diagram of a bandwidth adjustment device provided in an embodiment of the present application;
[0095] FIG18 is a schematic structural diagram of a network device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0096] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.
[0097] In the description of the embodiments of the present application, words such as "exemplary," "for example," or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary," "for example," or "for example" in the embodiments of the present application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary," "for example," or "for example" is intended to present the relevant concepts in a concrete manner.
[0098] In the description of the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, B exists alone, and A and B exist at the same time. In addition, unless otherwise specified, the term "plurality" means two or more. For example, "multiple systems" refers to two or more systems, and "multiple screen terminals" refers to two or more screen terminals.
[0099] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly identifying the technical features being referred to. Thus, features specified as "first" or "second" may explicitly or implicitly include one or more of such features. The terms "include," "comprising," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.
[0100] Before introducing the embodiments of the present application, some terms in the present application are explained below.
[0101] A provider edge (PE) is a network device located at the edge of the network and connected to user devices. An edge network device (hereinafter referred to as a PE node) is configured with one or more user network interfaces (UNIs) and multiple network-to-network interfaces (NNIs). The UNIs of the PE node connect to user-side devices (or user-side nodes), and the NNIs of the PE node connect to the NNIs of intermediate network devices. Customer premise equipment (CPE) can include wireless terminal access equipment (CPE) and servers.
[0102] An intermediate network device (provider, P) is a network device located within the network (between two edge network devices). An intermediate network device (hereinafter referred to as a node P) is configured with a network-side interface (NNI). The NNI of the node P is connected to the NNI of the PE node or to the NNI interface of another intermediate node. Intermediate network devices can include network devices with routing capabilities, such as routers.
[0103] It should be noted that when the node PE sends user data to the node P, the node PE can be called a source node. When the node PE receives user data from the node P, the node PE can be called a sink node.
[0104] A node's network resources (such as bandwidth) can be divided into multiple logical resources. The logical resources used by each node on the communication path to carry the same service are called a dedicated slice for that service. In other words, a dedicated slice carries a single service. Dedicated slices are isolated from each other to ensure network security and reliability.
[0105] The metropolitan transport network (MTN) is a communications network that, while being compatible with the Ethernet protocol stack, meets differentiated requirements such as hard isolation, low latency, and high reliability. MTN uses 66B code blocks for time-division multiplexing, slotting, and switching, achieving hard isolation of slices.
[0106] An MTN includes multiple nodes, including the aforementioned multiple PE nodes and multiple P nodes. In specific applications, the bandwidth of each node is divided into multiple time slots (hereinafter referred to as macro channels). For example, a network with 100 Gbps bandwidth can be divided into 20 time slots, each with a bandwidth of 5 Gbps. For another example, a network with 50 Gbps bandwidth can be divided into 10 time slots, each with a bandwidth of 5 Gbps.
[0107] A timeslot carries a service. If the bandwidth of the service is smaller than the timeslot's bandwidth, the timeslot's bandwidth is larger and underutilized, resulting in wasted bandwidth resources. For example, if the timeslot's bandwidth is 5 Gbps and the bandwidth of the service carried by the timeslot is less than 1 Gbps, the timeslot's bandwidth is clearly underutilized.
[0108] In order to avoid bandwidth waste caused by the inability to fully utilize time slots with larger bandwidth, small-granularity dedicated line technology was developed.
[0109] Small-granularity dedicated line technology, based on MTN, further divides the 5Gbps bandwidth time slots in MTN into multiple Mbps-level sub-time slots. Small-granularity dedicated line technology can provide Mbps-level small-granularity service carrying capacity.
[0110] A node's sub-timeslot carries a single service. Sub-timeslots carrying the same service on each node are called a dedicated slice. This allows a single large channel's time slot to carry multiple services, fully utilizing bandwidth resources. In specific applications, the number of sub-timeslots required for a node to carry a service can be calculated based on the service's bandwidth. Sub-timeslots can then be configured to carry the service on the node based on this number.
[0111] FIG1 is a schematic structural diagram of an MTN using a small-granularity dedicated line technology provided in an embodiment of the present application.
[0112] The MTN shown in Figure 1 includes multiple dedicated slice lines (e.g., dedicated slice lines 1 to N), each of which is used to carry one service. For example, as shown in Figure 1, dedicated slice line 1 can carry a service between user 11 and user 12, and dedicated slice line 2 can carry a service between user 21 and user 22. In addition, if a pair of users has multiple services, these multiple services can be carried by multiple dedicated slice lines.
[0113] The services of each slice dedicated line are transmitted through one or more sub-time slots of each node in a communication path in the MTN shown in Figure 1. The communication path includes two nodes PE and one or more nodes P, and the two nodes PE are connected to two user-side devices respectively.
[0114] Taking slice dedicated line 1 as an example, slice dedicated line 1 is used to carry services between user 11 and user 12. The services of slice dedicated line 1 can be transmitted through one or more sub-time slots including two edge network devices PE (such as PE1 and PE2 shown in Figure 2) and multiple intermediate network devices (such as P1 and P2 shown in Figure 2). The UNI of node PE1 and the UNI of node PE2 are respectively connected to the device on the user side (not shown in the figure). One NNI of node PE1 is connected to an NNI of node P1. Another NNI of node P1 is connected to an NNI of node P2; another NNI of node P2 is connected to an NNI of node PE2; node PE1 and node PE2 also communicate with the network management system. Among them, when node PE1 sends data to node P1, node PE1 is the source node of the data; when PE2 receives data from node P2, node PE2 is the destination node of the data.
[0115] The physical coding sublayer in the Ethernet physical layer of MTN shown in Figure 1 is divided into a section layer and a path layer. The frames of the section layer and path layer of MTN can be encoded based on the 66B coding type.
[0116] The following takes the MTN shown in FIG1 as an example and describes the frame structure of the segment layer in combination with FIG3a.
[0117] Figure 3a is a schematic diagram of the frame structure of a 100Gbps MTN segment layer, provided in an embodiment of the present application. As shown in Figure 3a, the MTN segment layer frame structure may include one segment overhead code block (SOH) and 20,460 payload code blocks. The overhead code block and the payload code block may be encoded using a 66B encoding type. The 20,460 payload code blocks may be divided into 20 time slots, for example, slots 0 to 19. Each time slot has a bandwidth of 5Gbps, and each time slot transmits 1,023 payload code blocks.
[0118] Each time slot, slot 0 through slot 19, can include multiple fine-grained basic units (FG-BUs) and one or more idle code blocks (IDLEs). IDLEs are located between two FG-BUs. For example, slot 0 can include 20 FG-BUs, as shown in Figure 3a, with one IDLE between every two FG-BUs. Within a frame, IDLEs can be added or removed to adjust the transmission rate of that frame.
[0119] The following is an introduction to the fine-grained basic unit FG-BU.
[0120] Figure 3b is a schematic diagram of the structure of a fine-grained basic unit (FG-BU) provided in an embodiment of the present application. The FG-BU has a fixed length and specifically includes 197 code blocks, each of which is 66 bits. These 197 code blocks include one start code block, 195 data code blocks, and one end code block.
[0121] As shown in Figure 3c, the 7 bytes and 195 data code blocks in the end code block constitute the payload area, carrying a total length of 1567 (195 × 8 + 7 = 1567) bytes. The payload area of the fine-grained basic unit (FG-BU) includes 7 bytes of overhead (OH) and 1560 bytes of payload. To avoid wasting bandwidth resources, each large channel (time slots 0 to 19) in each node of the MTN network is divided into multiple sub-time slots at a smaller bandwidth granularity. Specifically, the payload (1560 bytes) of the FG-BU of the MTN section layer frame is divided into 24 sub-time slots (or FG-slots) as shown in Figure 3c. Each sub-time slot carries a payload of 65 bytes (eight 65b code blocks). Thus, the MTN section layer frame can provide 480 sub-time slots. When a timeslot is 5 Gbps, the nominal rate of each sub-timeslot is 10.1 Mbps, the service bandwidth provided by the sub-timeslot is 10 Mbps, and 0.11 Mbps of the sub-timeslot is used to carry the operation administration maintenance (OAM) information of the sub-timeslot.
[0122] In specific applications, the number of sub-timeslots required to carry the service is calculated based on the actual bandwidth of the service carried by the slice dedicated line. For example, if the bandwidth provided by the sub-timeslot is 10Mbps and the bandwidth of the service is 100Mbps, 10 sub-timeslots need to be allocated to the service.
[0123] The overhead OH in the FG-BU can contain 56 bits of data, which can be used to carry sub-timeslot management information for the MTN segment layer frame. This management information can include, for example, bandwidth configuration information for a service or bandwidth adjustment information for a service. Bandwidth configuration information for a service refers to configuring one or more sub-timeslots to carry the service. Bandwidth adjustment information for a service refers to adjusting the number of timeslots used to carry the service. Increasing service bandwidth refers to increasing the number of sub-timeslots used to carry the service, while decreasing service bandwidth refers to decreasing the number of sub-timeslots used to carry the service. In other words, adjusting service bandwidth can be achieved by adjusting the number of sub-timeslots used to carry the service.
[0124] The fields included in the overhead OH are described in detail below with reference to FIG. 3 d .
[0125] As shown in Figure 3d, the fields of the overhead OH may include: multiframe indicator (MFI), overhead channel usage indication (Flag), last element indication (LE), time slot addition notification (downstream done, DD), time slot validation indication (commit CMT), time slot adjustment request (REQ), time slot adjustment response (acknowledge character, ACK), general communications channel (GCC), service number (FG-client identity, FG-client ID), sub-time slot number (FG-slot identity, FG-slot ID), element number (EN), cyclic redundancy check code (cyclic redundancy check, CRC).
[0126] As shown in Figure 3d, the FG-client ID, FG-slot ID, and EN share the same 33-bit segment with the GCC. For example, when the Flag value is 11, the 33 bits following the ACK are the GCC; when the Flag value is 00, the 33 bits following the ACK are the FG-client ID, FG-slot ID, and EN, respectively.
[0127] The following describes the specific meaning of each field.
[0128] 1. MFI: A 6-bit field-numbering (MFI) field indicating the number of each FG-BU in a multiframe. If the current FG-BU is the first in the multiframe, the MFI is 0. The MFI of each subsequent FG-BU increments by 1. In the scenario shown in Figure 2, a 5 Gbps timeslot includes 20 FG-BUs, so the decimal value of the MFI ranges from 0 to 19.
[0129] 2. Flag: This 2-bit field indicates that the 33 bits following the ACK are used for the FG-client ID, FG-slot ID, and either the EN or GCC. The default Flag value is 11. If slot adjustment is required, the Flag value is 00. Furthermore, only when the Flag value is 00 can the DD, CMT, REQ, and ACK fields carry valid information with a value of 1. After the DD, CMT, REQ, and ACK fields with a value of 1 have been sent, the Flag value returns to 11, and the DD, CMT, REQ, and ACK fields return to their default value of 0.
[0130] 3) LE: 1 bit, used to indicate whether this is the last bandwidth adjustment during a batch adjustment. For example, when LE = 1, it indicates the last bandwidth adjustment. When LE = 0, it indicates a non-last bandwidth adjustment. During a batch adjustment, for example, N adjustments, LE is 0 for the 1st to the (N-1th) adjustments; for the Nth adjustment, LE is 1.
[0131] 4. DD: 1 bit, used by the downstream node to notify the upstream node to increase timeslots when increasing bandwidth. For example, when DD is 1, it indicates that the downstream node needs to increase bandwidth (increase the number of timeslot adjustments). When DD is 1, the overhead Flag should be 00, and the FG-client ID and FG-slot ID information involved in the adjustment should be carried in the overhead.
[0132] 5. CMT: A 1-bit field used to indicate that a timeslot adjustment has taken effect. For example, when CMT is 1, it indicates that a timeslot adjustment has taken effect. When CMT is 1, the overhead Flag value should be 00, and the FG-client ID and FG-slot ID information related to the adjustment should be included in the overhead.
[0133] 6) REQ: 1 bit, used to indicate a bandwidth adjustment request. For example, when REQ is 1, it indicates a bandwidth adjustment request. When REQ is 1, the overhead Flag should be 00, and the FG-client ID and FG-slot ID information involved in the adjustment should be included in the overhead.
[0134] 7. ACK: 1 bit, used to indicate receipt of a REQ. For example, when ACK is 1, it indicates receipt of a bandwidth adjustment request. When ACK is 1, the overhead Flag should be 00, and the FG-client ID and FG-slot ID information involved in the adjustment should be included in the overhead.
[0135] 8) GCC: 33 bits in length, used to represent management information between nodes. The management information may include connectivity information between nodes.
[0136] 9. FG-client ID: This 12-bit field is used to identify the service requiring bandwidth adjustment. In specific applications, the first two bits are reserved; the remaining 10 bits indicate the service ID requiring bandwidth adjustment. FG-client ID values of all 0s or all 1s are invalid. Values other than all 0s or all 1s are valid and can be used normally.
[0137] 10. FG-slot ID: This 12-bit field indicates the sub-timeslot to be adjusted. In specific applications, the first two bits of the 12-bit field are reserved, and the remaining 10 bits indicate the sub-timeslot to be adjusted. For the 5 Gbps timeslot shown in Figure 2, the decimal value range of the FG-slot ID is 0 to 479.
[0138] 11) EN: 9 bits long, used to indicate the number of timeslots to be adjusted. In specific applications, EN can be used in conjunction with LE to specify the number of timeslots to be adjusted during batch timeslot adjustment.
[0139] 12).CRC: 7 bits in length, calculated from the first 41 bits (including the field after the Flag, excluding the initial 2-bit reserved bit and 6-bit MFI).
[0140] In addition, as shown in Figure 3d, the OH also includes two reserved fields (RES), namely a 2-bit RES and a 1-bit RES. The 2-bit RES is located before the MFI, and the 1-bit RES is located between the LE and the DD.
[0141] Based on the format of the OH field shown in Figure 3d, each node can reduce or increase the bidirectional channel bandwidth of the slice dedicated line transmission service through the OH field of the FG-BU.
[0142] Taking the slice dedicated line 1 described in Figure 1 as an example, the following describes how each node adjusts the bidirectional channel bandwidth of the service transmitted by the slice dedicated line 1.
[0143] Figure 4 is a schematic diagram of the structure of a bandwidth adjustment system provided by an embodiment of the present application. As shown in Figure 4, the bandwidth adjustment system includes a network management system and a communication path, and one or more sub-time slots of each node in the communication path transmit the service corresponding to the slice dedicated line 1.
[0144] The network management system is used to manage MTN's dedicated slice lines and the users of each dedicated slice line. For example, it authenticates and authorizes users 11 and 12 of dedicated slice line 1, and performs service configuration and bandwidth adjustment on dedicated slice line 1.
[0145] Each node in communication path 1 stores an uplink time slot table and a downlink time slot table. The uplink time slot table is used to record the services carried by the uplink time slots, and the downlink time slot table is used to record the services carried by the downlink time slots. Specifically, the uplink time slot table may include the time slot identifiers of the uplink time slots and the service identifiers of the services carried by the uplink time slots, and the downlink time slot table may include the time slot identifiers of each downlink time slot and the service identifiers of the services carried by the downlink time slots.
[0146] In one embodiment, when the user 11 needs to adjust the uplink bandwidth and / or downlink bandwidth of the first service, the user 11 may perform an operation on the user interface of the network management system and send a bandwidth adjustment request to the network management system.
[0147] Among them, one or more slice dedicated lines carried by the communication path include slice dedicated line 1.
[0148] The bandwidth adjustment request may include a service identifier of the first service, uplink bandwidth adjustment information, and / or downlink bandwidth adjustment information. The uplink bandwidth adjustment information may include an uplink target bandwidth or an uplink bandwidth increment; and the downlink bandwidth adjustment information may include a downlink target bandwidth or a downlink bandwidth increment.
[0149] After receiving the bandwidth adjustment request, the network management system determines whether to send the bandwidth adjustment request to the source node PE1 or the sink node PE2 based on the bandwidth adjustment rules. The bandwidth adjustment rules include starting bandwidth reduction at the source node of the slice dedicated line and increasing bandwidth at the sink node of the slice dedicated line. Furthermore, for user 11, node PE1 is the source node, and node PE2 is the sink node. Therefore, when the bandwidth adjustment request indicates a decrease in the uplink bandwidth of the first service or an increase in the downlink bandwidth of the first service, the network management system sends the bandwidth adjustment request to node PE1; when the bandwidth adjustment request indicates an increase in the uplink bandwidth of the first service or a decrease in the downlink bandwidth of the first service, the network management system sends the bandwidth adjustment request to node PE2.
[0150] Taking the example of a bandwidth adjustment request indicating a reduction in the uplink bandwidth of a first service, after receiving the bandwidth adjustment request, node PE1 reduces the uplink bandwidth of the first service in accordance with the bandwidth adjustment request and then sends a timeslot adjustment request (REQ) message (see Figure 5a) to node P. Node P reduces the uplink bandwidth of the first service in accordance with the REQ message and then sends an ACK message (see Figure 5a) to node PE1, indicating that node P has successfully reduced the uplink bandwidth of the first service. After receiving the ACK message, node PE1 sends a CMT message (see Figure 5a) to node P, indicating that the updated timeslot table takes effect in the next multiframe. After receiving the CMT message, node P sends the REQ message (see Figure 5a) to node PE2. Node PE2 also reduces the uplink bandwidth of the first service in accordance with the REQ message and then sends an ACK message (see Figure 5a) to node P. After receiving the ACK message, node P sends the CMT message (see Figure 5a) to node PE2.
[0151] In this way, slice dedicated line 1 completes the task of reducing the uplink bandwidth of the first service. When each node sends the various messages shown in Figure 5a, it carries the various messages through the FG-BU. Specifically, the value of the OH field in the FG-BU can be used to represent the various messages.
[0152] Taking a bandwidth adjustment request indicating an increase in the uplink bandwidth of a first service as an example, after receiving the bandwidth adjustment request and determining that the uplink bandwidth of the first service needs to be increased based on the bandwidth adjustment request, node PE2 sends a Timeslot Increase Notification (DD) message, as shown in Figure 5b, to node P. After receiving the DD message, node P sends a Timeslot Adjustment Request (REQ) message, as shown in Figure 5b, to node PE2. Based on the REQ message, node PE2 increases the uplink bandwidth of the first service and then sends an ACK message, as shown in Figure 5b, to node P. This ACK message indicates that node PE2 has successfully increased the uplink bandwidth of the first service. After receiving the ACK message, node P sends a CMT message, as shown in Figure 5b, to node PE2. This CMT message indicates that the updated timeslot table takes effect in the next multiframe. After sending the CMT message, node P sends a DD message, as shown in Figure 5b, to node PE1. After receiving the DD message, node PE1 sends a REQ message, as shown in Figure 5b, to node P. Node P also increases the uplink bandwidth of the first service based on the REQ message and then sends an ACK message, as shown in Figure 5b, to node PE1. After receiving the ACK message, node PE1 sends the CMT message shown in Figure 5b to node P. After sending the CMT message, node PE1 increases the uplink bandwidth of the first service. In this way, slice dedicated line 1 completes the task of increasing the uplink bandwidth of the first service. When each node sends the various messages shown in Figure 5b, it carries them through different FG-BUs. Specifically, different messages can be represented by the values of the OH field in different FG-BUs.
[0153] Among them, adjusting the bandwidth of the first service by each node in the slice dedicated line refers to updating the uplink time slot table and / or downlink time slot table stored by the node according to the bandwidth adjustment information. When the bandwidth adjustment request indicates to adjust the uplink and downlink bandwidth of the service, the node updates the stored uplink / downlink time slot table, including reducing the uplink time slot carrying the service in the uplink time slot table, or reducing the downlink time slot carrying the service in the downlink time slot table; when the bandwidth adjustment method is to increase the uplink / downlink bandwidth of the service, the node updates the stored uplink / downlink time slot table, including increasing the uplink time slot carrying the service in the uplink time slot table, or increasing the downlink time slot carrying the service in the downlink time slot table.
[0154] As can be seen from the bandwidth adjustment process described above, when reducing or increasing the uplink or downlink bandwidth, the network management system must send bandwidth adjustment requests to both the source and sink nodes in the dedicated slice line, allowing the slice line to adjust the bidirectional bandwidth of the service. The network management system manages a large number of dedicated slice lines, and sending two bandwidth adjustment requests to both the source and sink nodes places a high load on the system. Furthermore, when the network management system is offline, users cannot communicate with the system, making it impossible to adjust service bandwidth, and bandwidth adjustment reliability is low.
[0155] To this end, an embodiment of the present application provides a bandwidth adjustment method that can solve the above problems.
[0156] In a bandwidth adjustment method provided in an embodiment of the present application, as shown in Figure 6, a user directly sends a bandwidth adjustment request to the source node PE1 through a user-side node. The source node PE1 initiates unidirectional or bidirectional bandwidth adjustment, which can reduce the load on the network management system and improve the reliability of bandwidth adjustment. Unidirectional bandwidth adjustment includes reducing the upstream bandwidth, reducing the downstream bandwidth, increasing the upstream bandwidth, and increasing the downstream bandwidth; bidirectional bandwidth adjustment includes reducing the upstream bandwidth and reducing the downstream bandwidth, increasing the upstream bandwidth and increasing the downstream bandwidth, reducing the upstream bandwidth and increasing the downstream bandwidth, and increasing the upstream bandwidth and reducing the downstream bandwidth.
[0157] To achieve the above purpose, the embodiment of the present application defines the 2-bit RES field in the OH field shown in Figure 3d as a mode option (MO) field, and defines the 1-bit RES field in Figure 3d as a bandwidth adjustment (BA) field, to obtain the OH field with the structure shown in Figure 7.
[0158] In Figure 7, different values of the MO field indicate different bandwidth adjustment modes. When the MO field value is 11 or 10, it indicates bidirectional bandwidth adjustment; when the MO field value is 01 or 00, it indicates unidirectional bandwidth adjustment.
[0159] Among them, when the value of the MO field is 11, it can indicate bidirectional symmetrical bandwidth adjustment, that is, the adjustment method of the uplink bandwidth and the downlink bandwidth is the same, and the number of time slot adjustments of the uplink bandwidth and the downlink bandwidth is equal.
[0160] Among them, when the value of the MO field is 10, it can indicate bidirectional asymmetric bandwidth adjustment, that is, the adjustment methods of the uplink bandwidth and the downlink bandwidth are different, or the number of time slot adjustments is different.
[0161] Among them, when the value of the MO field is 01, it can indicate adjustment of the downlink bandwidth.
[0162] Among them, when the value of the MO field is 00, it may indicate adjustment of the uplink bandwidth.
[0163] In Figure 7, different values of the BA field indicate different adjustment methods. For example, a BA value of 0 indicates a bandwidth reduction, while a BA value of 1 indicates a bandwidth increase. When MO is 10, the BA field value indicates the uplink bandwidth adjustment method, and the DD field value indicates the downlink bandwidth adjustment method. That is, when MO is 10, a BA value of 1 indicates an uplink bandwidth increase, a BA value of 0 indicates an uplink bandwidth decrease, a DD value of 1 indicates an downlink bandwidth increase, and a DD value of 0 indicates a downlink bandwidth decrease.
[0164] Based on the introduction of the above fields, the source node can determine the value of the MO field and the value of the BA field according to the bandwidth adjustment request, and instruct the intermediate node and the sink node to adjust the unidirectional bandwidth or make the same adjustment to the bidirectional bandwidth through the MO field and the BA field. In addition, the source node can determine the value of the MO field, the value of the BA field, and the value of the DD field according to the bandwidth adjustment request, and instruct the intermediate node and the sink node to make different adjustments to the bidirectional bandwidth through the values of the MO field, the BA field, and the DD field.
[0165] The following describes how to reduce both the upstream and downstream bandwidths as an example.
[0166] FIG8a is a flow chart of a bandwidth adjustment method provided by an embodiment of the present application. The method is used to reduce both uplink bandwidth and downlink bandwidth, and includes the following steps S801 to S813.
[0167] In S801 , the node PE1 receives a bandwidth adjustment request from a user-side node. If it is determined that the bandwidth adjustment request indicates to reduce the uplink bandwidth of the first service and to reduce the downlink bandwidth of the first service, step S802 is executed.
[0168] In this embodiment, as shown in FIG6 , user 11 may send the bandwidth adjustment request to the user-side node through the terminal device. After receiving the bandwidth adjustment request, the user-side node sends it to node PE1 .
[0169] In this step, taking the bandwidth adjustment request including the service identifier of the first service and the target channel bandwidth of the first service as an example, the target channel bandwidth may include an uplink target bandwidth and a downlink target bandwidth. Node PE1 may calculate the uplink bandwidth increment and the downlink bandwidth increment for the first service based on the uplink target bandwidth and the downlink target bandwidth, as well as the current uplink bandwidth and downlink bandwidth of the first service. Then, based on the uplink bandwidth increment and the downlink bandwidth increment of the first service, it is determined whether the bandwidth adjustment request indicates a reduction in both the uplink bandwidth and the downlink bandwidth of the first service. For example, if both the uplink bandwidth increment and the downlink bandwidth increment are less than 0, then S802 is executed if it is determined that the bandwidth adjustment request indicates a reduction in both the uplink bandwidth and the downlink bandwidth of the first service. Furthermore, if the bandwidth adjustment request includes the uplink bandwidth increment and the downlink bandwidth increment of the first service, node PE1 may directly determine whether the bandwidth adjustment request indicates a reduction in both the uplink bandwidth and the downlink bandwidth of the first service.
[0170] In S802, node PE1 reduces the uplink bandwidth of the first service according to the bandwidth adjustment request, and then sends a first timeslot adjustment request REQ message to node P. The first REQ message is used to instruct node P and node PE2 to reduce the uplink bandwidth of the first service and reduce the downlink bandwidth of the first service.
[0171] In this step, node PE1 can determine the number of time slots to adjust the uplink bandwidth and downlink bandwidth of the first service based on the uplink bandwidth increment, the downlink bandwidth increment, and the bandwidth of the sub-timeslot. For example, if the uplink bandwidth increment of the first service in the bandwidth adjustment request is -20 Mbps, and the service bandwidth provided to the user by the sub-timeslot is 10 Mbps, calculation shows that two sub-timeslots need to be reduced. Therefore, the number of time slots to adjust the uplink bandwidth of the first service is 2.
[0172] The node PE1 adjusts the number of time slots of the uplink bandwidth of the first service and reduces the uplink sub-time slots for transmitting the first service in the uplink time slot table, thereby reducing the uplink bandwidth of the first service.
[0173] In this step, after reducing the uplink bandwidth of the first service, the node PE1 may send an FG-BU to the node P. The OH field in the FG-BU indicates the first REQ message, and the bandwidth of the first service is adjusted through the first REQ message.
[0174] If it is determined that the uplink and downlink bandwidths of the first service are to be reduced, and the timeslot adjustment amounts for both are equal, the format of the first REQ message is shown in Figure 8b , as described above with respect to Figure 7 . In the first REQ message shown in Figure 8b , the value of the MO field is 11, the value of the BA field is 0, the value of the LE field is 1, the value of the REQ field is 1, the values of the DD field, the CMT field, and the ACK field are all the default value of 0, the value of the FG-slot ID field does not indicate a timeslot identifier, the value of the EN field indicates the timeslot adjustment amounts for the uplink and downlink bandwidths of the first service, and the value of the FG-client ID field indicates the service identifier of the first service in the bandwidth adjustment request.
[0175] If it is determined that the uplink and downlink bandwidths of the first service are to be reduced, and the timeslot adjustment amounts for the two services are unequal, the format of the first REQ message is shown in Figure 8c, as described above with respect to Figure 7. In the first REQ message shown in Figure 8c, the value of the MO field is 10, the value of the BA field is 0, the value of the REQ field is 1, the value of the LE field is 1, the values of the FG-slot ID field and the value of the EN field represent the timeslot adjustment amounts for the uplink bandwidth and the downlink bandwidth of the first service, respectively, and the value of the FG-client ID field represents the service identifier of the first service in the bandwidth adjustment request.
[0176] In addition, in other embodiments, when the number of time slot adjustments for the uplink bandwidth of the first service is equal to the number of time slot adjustments for the downlink bandwidth of the first service, for example, both are N (N is a positive integer), node PE1 can send N first REQ messages. Figure 8d shows the format of the Nth first REQ message. In the Nth first REQ message shown in Figure 8d, the value of the MO field is 11, the value of the BA field is 0, the value of the LE field is 1, the value of the REQ field is 1, the values of the DD field, the CMT field, and the ACK field are all the default value 0, the value of the FG-client ID field represents the service identifier of the first service in the bandwidth adjustment request, the value of the FG-slot ID field represents the time slot identifier of the Nth uplink sub-time slot for transmitting the first service reduced in the uplink time slot table by node PE1, and the value of the EN field represents the number of time slot adjustments for the uplink bandwidth and downlink bandwidth of the first service. Among them, the difference between the 1st to N-1th first REQ messages (not shown in Figure 8d) and the Nth first REQ message shown in Figure 8d is that the value of the LE field in the 1st to N-1th first REQ messages is 0, and the value of the FG-slot ID field in the 1st to N-1th first REQ messages respectively represents the time slot identifiers of the 1st to Nth uplink sub-time slots for transmitting the first service reduced by node PE1 in the uplink time slot table.
[0177] It should be noted that the values of the MFI field, Flag field, and CRC field in each message shown in Figures 8b to 8d can be determined based on the functional description of each field above in this application and according to actual needs. Furthermore, this embodiment of the application does not specifically limit the values of fields other than the OH field in each FG-BU. The values of fields other than the OH field in each FG-BU can be determined based on actual service data.
[0178] In S803, after receiving the first REQ message sent by node PE1, node P reduces the uplink bandwidth of the first service according to the first REQ message, and then sends a first timeslot adjustment ACK message to node PE1. The first ACK message indicates that node P has successfully reduced the uplink bandwidth of the first service.
[0179] In this step, the node P reduces the uplink bandwidth of the first service according to the first REQ message, including determining to reduce the uplink bandwidth of the first service and reducing the downlink bandwidth of the first service according to the value of the MO field, the value of the BA field, and the value of the FG-client ID field in the OH field.
[0180] When the first REQ message shown in Figure 8b is received, the time slot adjustment number of the uplink bandwidth of the first service is determined according to the value of the EN field in the first REQ message. According to the time slot adjustment number of the uplink bandwidth of the first service, the uplink sub-time slot for transmitting the first service is reduced in the uplink time slot table, thereby reducing the uplink bandwidth of the first service.
[0181] When the first REQ message shown in Figure 8c is received, the time slot adjustment number of the uplink bandwidth of the first service is determined according to the value of the FG-slot ID field in the first REQ message, and the uplink sub-time slot for transmitting the first service is reduced in the uplink time slot table according to the time slot adjustment number of the uplink bandwidth of the first service, thereby reducing the uplink bandwidth of the first service.
[0182] In addition, in other embodiments, when node P receives N first REQ messages, node P determines the time slot identifier of the uplink sub-time slot to be reduced based on the value of the FG-slot ID field in each first REQ message, and reduces the uplink sub-time slot for transmitting the first service in the uplink time slot table based on the time slot identifier, thereby reducing the uplink bandwidth of the first service.
[0183] In this step, after reducing the uplink bandwidth of the first service, the node P sends an FG-BU to the node PE1. The OH field in the FG-BU indicates the first ACK message.
[0184] When the first REQ message has the structure shown in FIG8b or FIG8c, node P may set the value of the REQ field in the first REQ message shown in FIG8b or FIG8c to 0 and the value of the ACK field to 1 to obtain the first ACK message shown in FIG8b or FIG8c.
[0185] In addition, in other embodiments, when the node P receives N first REQ messages, the node P may set the value of the REQ field in the Nth first REQ message shown in FIG8 d to 0 and the value of the ACK field to 1 to obtain the first ACK message.
[0186] In S804 , after receiving the first ACK message sent by the node P, the node PE1 sends one or more first time slot validity indication CMT messages to the node P.
[0187] In this step, node PE1 can send three FG-BUs to node P. The OH field in each FG-BU represents a first CMT message. The formats of the three first CMT messages are the same. The three first CMT messages are used to indicate that the updated uplink time slot table takes effect in the next multiframe.
[0188] Specifically, when the first REQ message has the structure shown in FIG8b or FIG8c, node PE1 can set the value of the ACK field in the first ACK message shown in FIG8b or FIG8c to 0 and the value of the CMT field to 1, respectively, to obtain the first CMT message shown in FIG8b or FIG8c.
[0189] In addition, in other embodiments, when the node PE1 receives the first ACK message as shown in FIG. 8 d , the node PE1 may send the first CMT message as shown in FIG. 8 d .
[0190] In S805 , after receiving the first CMT message sent by the node PE1 , the node P sends a first REQ message to the node PE2 .
[0191] In this step, the introduction of node P sending the third REQ message to node PE2 can refer to the description of node PE1 sending the first REQ message to node P in S802, which will not be repeated here.
[0192] In S806 , after receiving the first REQ message sent by the node P, the node PE2 reduces the uplink bandwidth of the first service according to the values of the various fields in the first REQ message, and then sends a first ACK message to the node P.
[0193] In this step, the introduction of node PE2 reducing the uplink bandwidth of the first service and sending the first ACK message can refer to the description of node P reducing the uplink bandwidth of the first service and sending the first ACK message in S803 above, which is not repeated here.
[0194] In S807, after receiving the first ACK message sent by the node PE2, the node P sends one or more first CMT messages to the node PE2.
[0195] In this step, the introduction of node P sending the first CMT message can refer to the description of node PE1 sending the first CMT message in the aforementioned S804, which will not be repeated here.
[0196] In S808, after receiving the first CMT message sent by node P, node PE2 reduces the downlink bandwidth of the first service according to the first REQ message, and then sends a second REQ message to node P. The second REQ message is used to instruct node P and node PE1 to reduce the downlink bandwidth of the first service.
[0197] In this step, when the first REQ message has the structure shown in FIG8b or FIG8c, node PE2 reduces the downlink bandwidth of the first service according to the first REQ message, including determining the time slot adjustment number of the downlink bandwidth of the first service according to the value of the EN field in the first REQ message, and reducing the downlink sub-time slot for transmitting the first service in the downlink time slot table according to the time slot adjustment number of the downlink bandwidth of the first service, thereby reducing the downlink bandwidth of the first service.
[0198] In addition, in other embodiments, when node PE2 receives N first REQ messages, node PE2 can determine the time slot adjustment number of the downlink bandwidth of the first service based on the value of the EN field in the Nth first REQ message, and then reduce N downlink sub-time slots for transmitting the first service in the downlink time slot table, thereby reducing the downlink bandwidth of the first service.
[0199] In this step, after reducing the uplink bandwidth of the first service, the node PE2 may send an FG-BU to the node P. The OH field in the FG-BU indicates the second REQ message.
[0200] Specifically, node PE2 can set the value of the MO field in the first REQ message shown in Figure 8b or Figure 8c to 00, thereby obtaining the second REQ message shown in Figure 8b or Figure 8c. Furthermore, in other embodiments, when node PE2 receives N first REQ messages, node PE2 can set the value of the MO field in the N first REQ messages to 00, and modify the value of the FG-slot ID field in each of the N first REQ messages to the value corresponding to the time slot identifier of the N downlink sub-time slots transmitting the first service reduced in the downlink time slot table by node PE2, thereby obtaining N second REQ messages. Figure 8d shows the format 8d of the Nth second REQ message. Node PE2 can send N FG-BUs to node P, with the OH field in each FG-BU representing a second REQ message.
[0201] In S809 , after receiving the second REQ message sent by the node PE2 , the node P reduces the downlink bandwidth of the first service according to the second REQ message, and then sends a second ACK message to the node PE2 .
[0202] In this step, node P reduces the downlink bandwidth of the first service based on the second REQ message, including determining the reduction in the downlink bandwidth of the first service based on the values of the MO field, the BA field, and the FG-client ID field in the second REQ message. When the first REQ message has the structure shown in Figure 8b or Figure 8c, node P determines the number of time slots to adjust the downlink bandwidth of the first service based on the value of the EN field in the second REQ message. Based on the number of time slots adjusted for the downlink bandwidth of the first service, node P reduces the downlink sub-time slots for transmitting the first service from the downlink time slot table, thereby reducing the downlink bandwidth of the first service.
[0203] In addition, in other embodiments, when node P receives N second REQ messages, node P determines the time slot identifier of the downlink sub-time slot to be reduced based on the value of the FG-slot ID field in each second REQ message, and reduces the downlink sub-time slot for transmitting the first service in the downlink time slot table based on the time slot identifier, thereby reducing the downlink bandwidth of the first service.
[0204] In this step, after reducing the downlink bandwidth of the first service, node P sends an FG-BU to node PE2. The OH field in the FG-BU represents the second ACK message. When the first REQ message has the structure shown in Figure 8b or 8c, node P can set the REQ field in the second REQ message to 0 and the ACK field to 1, resulting in the second ACK message shown in Figure 8b or 8c.
[0205] In addition, in other embodiments, when node P receives N second REQ messages, node P can set the value of the REQ field in the Nth second REQ message shown in Figure 8d to 0 and the value of the ACK field to 1 to obtain the second ACK message shown in Figure 8d.
[0206] In S1801, after receiving the second ACK message sent by node P, node PE2 sends one or more second CMT messages to node P.
[0207] In this step, node PE2 can send three FG-BUs to node P. The OH field in each FG-BU represents a second CMT message. The three second CMT messages have the same format and are used to indicate that the updated downlink timeslot table takes effect in the next multiframe. Specifically, when the second ACK message has the structure shown in Figure 8b or Figure 8c, node PE2 can set the value of the ACK field to 0 and the value of the CMT field to 1 in the second ACK message shown in Figure 8b or Figure 8c, respectively, to obtain the second CMT message shown in Figure 8b or Figure 8c.
[0208] In addition, in other embodiments, when the node PE2 receives the second ACK message as shown in FIG. 8 d , the format of the second CMT message sent by the node PE2 is as shown in FIG. 8 d .
[0209] In S811, after receiving the second CMT message sent by the node PE2, the node P sends a second REQ message to the node PE1.
[0210] In this step, the introduction of the node P sending the second REQ message can refer to the introduction of the node PE2 sending the second REQ message in the aforementioned S808, which will not be repeated here.
[0211] In S812 , after receiving the second REQ message sent by the node P, the node PE1 reduces the downlink bandwidth of the first service according to the second REQ message, and then sends a second ACK message to the node P.
[0212] In this step, the description of node PE1 reducing the downlink bandwidth of the first service and sending the second ACK message can refer to the description of node P reducing the downlink bandwidth of the first service and sending the second ACK message in S809, which will not be repeated here.
[0213] In S813 , after receiving the second ACK message sent by the node PE1 , the node P sends one or more second CMT messages to the node PE1 .
[0214] In this step, the introduction of node P sending one or more second CMT messages to node PE1 can refer to the description of node PE2 sending one or more second CMT messages to node P in the aforementioned S1801, which will not be repeated here.
[0215] The following takes increasing the uplink bandwidth and increasing the downlink bandwidth as an example for a detailed description.
[0216] FIG9 a is a flow chart of a bandwidth adjustment method provided by an embodiment of the present application. The method is used to increase both uplink bandwidth and downlink bandwidth, and includes the following steps S901 to S913.
[0217] In S901 , the node PE1 receives a bandwidth adjustment request from a user-side node. If it is determined that the bandwidth adjustment request indicates to increase the uplink bandwidth of the first service and to increase the downlink bandwidth of the first service, step S902 is executed.
[0218] In this embodiment, as shown in FIG6 , user 11 may send the bandwidth adjustment request to the user-side node through the terminal device. After receiving the bandwidth adjustment request, the user-side node sends it to node PE1 .
[0219] In this step, taking the bandwidth adjustment request as an example, where the service identifier of the first service and the target channel bandwidth of the first service are included, the target channel bandwidth may include an uplink target bandwidth and a downlink target bandwidth. Node PE1 may calculate the uplink bandwidth increment and the downlink bandwidth increment for the first service based on the uplink target bandwidth and the downlink target bandwidth, as well as the current uplink bandwidth and downlink bandwidth of the first service. Then, based on the uplink bandwidth increment and the downlink bandwidth increment of the first service, it is determined whether the bandwidth adjustment request indicates an increase in both the uplink bandwidth and the downlink bandwidth of the first service. For example, if both the uplink bandwidth increment and the downlink bandwidth increment are greater than 0, it is determined that the bandwidth adjustment request indicates an increase in both the uplink bandwidth and the downlink bandwidth of the first service, and S902 is executed. Furthermore, if the bandwidth adjustment request includes the uplink bandwidth increment and the downlink bandwidth increment of the first service, node PE1 may directly determine whether the bandwidth adjustment request indicates an increase in both the uplink bandwidth and the downlink bandwidth of the first service.
[0220] In S902, node PE1 increases the downlink bandwidth of the first service according to the bandwidth adjustment request, and then sends a third timeslot adjustment request REQ message to node P. The third REQ message is used to instruct node P and node PE2 to increase the uplink bandwidth and downlink bandwidth of the first service.
[0221] In this step, node PE1 can determine the timeslot adjustment number for the uplink bandwidth and the timeslot adjustment number for the downlink bandwidth of the first service based on the uplink bandwidth increment, the downlink bandwidth increment, and the bandwidth of the sub-timeslot. Then, node PE1 adds a downlink sub-timeslot for transmitting the first service to the downlink timeslot table based on the timeslot adjustment number for the downlink bandwidth of the first service, thereby increasing the downlink bandwidth of the first service.
[0222] In this step, after increasing the downlink bandwidth of the first service, the node PE1 may send an FG-BU to the node P. The OH field in the FG-BU indicates the third REQ message. The bandwidth of the first service is adjusted through an REQ message.
[0223] If it is determined that the uplink and downlink bandwidths of the first service are to be increased, and the timeslot adjustment amounts for both are equal, the format of the third REQ message is shown in Figure 9b, as described above with respect to Figure 7. In the third REQ message shown in Figure 9b, the value of the MO field is 11, the value of the BA field is 1, the value of the LE field is 1, the value of the REQ field is 1, the values of the DD field, the CMT field, and the ACK field are all the default values of 0, the value of the FG-slot ID field does not indicate a timeslot identifier, and the value of the EN field indicates the timeslot adjustment amounts for the uplink and downlink bandwidths of the first service.
[0224] If it is determined that the uplink and downlink bandwidths of the first service are to be increased, and the timeslot adjustment amounts for the two are unequal, the format of the third REQ message is shown in FIG9c , as described above with respect to FIG7 . In the third REQ message shown in FIG9c , the MO field has a value of 10, the BA field has a value of 1, the LE field has a value of 1, the REQ field has a value of 1, the DD field, the CMT field, and the ACK field all have default values of 0, and the values of the FG-slot ID field and the EN field represent the timeslot adjustment amounts for the uplink bandwidth and the downlink bandwidth of the first service, respectively.
[0225] In addition, in other embodiments, when the number of time slot adjustments for the uplink bandwidth of the first service is equal to the number of time slot adjustments for the downlink bandwidth of the first service, for example, both are N, node PE1 can send N third REQ messages. Figure 9d shows the format of the Nth third REQ message. In the Nth third REQ message, the value of the MO field is 11, the value of the BA field is 1, the value of the LE field is 1, the value of the FG-client ID field represents the service identifier of the first service in the bandwidth adjustment request; the value of the FG-slot ID field represents the time slot identifier of the Nth downlink sub-time slot for transmitting the first service added by node PE1 in the downlink time slot table, and the value of the EN field represents the number of time slot adjustments. The value of the REQ field is 1, and the values of the DD field, CMT field, and ACK field are all default values 0.
[0226] It should be noted that the values of the MFI field, Flag field, and CRC field in each REQ message shown in Figures 9b to 9d can be determined based on the functional description of each field above in this application and according to actual needs. Furthermore, this embodiment of the application does not specifically limit the values of fields other than the OH field in each FG-BU. The values of fields other than the OH field in each FG-BU can be determined based on actual service data.
[0227] In S903, after receiving the third REQ message sent by node PE1, node P increases the downlink bandwidth of the first service according to the third REQ message, and then sends a third timeslot adjustment acknowledgement ACK message to node PE1. The third ACK message is used to indicate that the downlink bandwidth of the first service is increased successfully.
[0228] In this step, node P increases the downlink bandwidth of the first service based on the third REQ message, including determining to increase both the uplink bandwidth and the downlink bandwidth of the first service based on the value of the MO field, the value of the BA field, and the value of the FG-client ID field in the OH field. Then, node P determines the timeslot adjustment number for the downlink bandwidth of the first service based on the value of the EN field in the third REQ message, and adds a downlink sub-timeslot for transmitting the first service to the downlink timeslot table based on the timeslot adjustment number for the downlink bandwidth of the first service, thereby increasing the downlink bandwidth of the first service. Furthermore, in other embodiments, when node P receives N third REQ messages, node P determines the timeslot identifier of the downlink sub-timeslot to be added based on the value of the FG-slot ID field in each third REQ message, and adds the downlink sub-timeslot for transmitting the first service to the downlink timeslot table based on the timeslot identifier, thereby increasing the downlink bandwidth of the first service.
[0229] In this step, after increasing the downlink bandwidth of the first service, node P sends an FG-BU to node PE1. The OH field in the FG-BU represents the third ACK message. Node P can set the REQ field in the third REQ message shown in FIG9b to 0 and the ACK field to 1, thereby obtaining the third ACK message shown in FIG9b.
[0230] In addition, in other embodiments, when node P receives N third REQ messages, the Nth third REQ message is shown in Figure 9d, for example, node P can set the value of the REQ field in the Nth third REQ message to 0 and set the value of the ACK field to 1 to obtain the third ACK message shown in Figure 9d.
[0231] In S904 , after receiving the third ACK message sent by the node P, the node PE1 sends one or more third time slot validity indication CMT messages to the node P.
[0232] In this step, node PE1 can send three FG-BUs to node P. The OH field in each FG-BU represents a third CMT message, as shown in Figure 9b . The three third CMT messages have the same format and indicate that the updated downlink timeslot table takes effect in the next multiframe. Specifically, node PE1 can set the ACK field value to 0 and the CMT field value to 1 in the third ACK message, as shown in Figure 9b , to obtain the third CMT message shown in Figure 9b .
[0233] In addition, in other embodiments, when the node PE1 receives the third ACK message as shown in FIG. 9 d , the format of the third CMT message sent by the node PE1 is as shown in FIG. 9 d .
[0234] In S905 , after receiving the third CMT message sent by the node PE1 , the node P sends a third REQ message to the node PE2 .
[0235] In this step, the introduction of node P sending the third REQ message to node PE2 can refer to the description of node PE1 sending the third REQ message to node P in S902, which will not be repeated here.
[0236] In S906 , the node PE2 receives the third REQ message sent by the node P, increases the downlink bandwidth of the first service according to the values of the fields in the third REQ message, and then sends a third ACK message to the node P.
[0237] In this step, the introduction of node PE2 increasing the downlink bandwidth of the first service and sending the third ACK message can refer to the description of node P increasing the uplink bandwidth of the first service and sending the increase ACK message in S903 above, which is not repeated here.
[0238] In S907 , after receiving the third ACK message sent by the node PE2 , the node P sends one or more third CMT messages to the node PE2 .
[0239] In this step, the introduction of the node P sending the third CMT message can refer to the description of the node PE1 sending the third CMT message in the aforementioned S904, which will not be repeated here.
[0240] In S908, after receiving the third CMT message sent by node P, node PE2 increases the uplink bandwidth of the first service according to the third REQ message, and then sends a fourth REQ message to node P. The fourth REQ message is used to instruct node P and node PE1 to increase the uplink bandwidth of the first service.
[0241] In this step, node PE2 increases the uplink bandwidth of the first service in response to the third REQ message, including determining a timeslot adjustment number for the uplink bandwidth of the first service based on the value of the FG-slot ID field in the third REQ message. Based on the timeslot adjustment number for the uplink bandwidth of the first service, node PE2 adds an uplink sub-timeslot for transmitting the first service to the uplink timeslot table, thereby increasing the uplink bandwidth of the first service. Furthermore, in other embodiments, when node PE2 receives N third REQ messages, node PE2 adds N uplink sub-timeslots for transmitting the first service to the uplink timeslot table, thereby increasing the uplink bandwidth of the first service.
[0242] In this step, after increasing the uplink bandwidth of the first service, node PE2 can send an FG-BU to node P. The OH field in the FG-BU represents the fourth REQ message shown in Figure 9b. Node PE2 can set the value of the MO field in the third REQ message shown in Figure 9b to 00 to obtain the fourth REQ message shown in Figure 9b.
[0243] In addition, in other embodiments, when node PE2 receives N third REQ messages, node PE2 may set the value of the MO field in the N third REQ messages to 00, and modify the value of the FG-slot ID field in each of the N third REQ messages to the value corresponding to the time slot identifier of the N uplink sub-time slots for transmitting the first service added by node PE2 in the uplink time slot table, thereby obtaining N fourth REQ messages. The format of the Nth fourth REQ message is shown in FIG. 9d. Node PE2 may send N FG-BUs to node P, with the OH field in each FG-BU representing a fourth REQ message.
[0244] In S909 , after receiving the fourth REQ message sent by the node PE2 , the node P increases the uplink bandwidth of the first service according to the fourth REQ message, and then sends a fourth ACK message to the node PE2 .
[0245] In this step, the node P increases the uplink bandwidth of the first service according to the fourth REQ message, including determining to increase the uplink bandwidth of the first service according to the value of the MO field, the value of the BA field, and the value of the FG-client ID field in the fourth REQ message.
[0246] Then, based on the value of the FG-slot ID field in the fourth REQ message, the number of timeslot adjustments for the uplink bandwidth of the first service is determined, and an uplink sub-timeslot for transmitting the first service is added to the uplink timeslot table according to the number of timeslot adjustments for the uplink bandwidth of the first service, thereby increasing the uplink bandwidth of the first service. Furthermore, in other embodiments, when node P receives N fourth REQ messages, node P determines the timeslot identifier of the uplink sub-timeslot to be added based on the value of the FG-slot ID field in each fourth REQ message, and adds the uplink sub-timeslot for transmitting the first service to the uplink timeslot table based on the timeslot identifier, thereby increasing the uplink bandwidth of the first service.
[0247] In this step, after increasing the uplink bandwidth of the first service, node P sends an FG-BU to node PE2. The OH field in the FG-BU represents the fourth ACK message. Node P may set the value of the REQ field in the fourth REQ message to 0 and the value of the ACK field to 1 to obtain the fourth ACK message. Furthermore, in other embodiments, when node P receives N fourth REQ messages, such as the Nth REQ message shown in FIG9d , node P may set the value of the REQ field in the Nth fourth REQ message to 0 and the value of the ACK field to 1 to obtain the fourth ACK message.
[0248] In S910 , after receiving the fourth ACK message sent by the node P, the node PE2 sends one or more fourth CMT messages to the node P.
[0249] In this step, node PE2 can send three FG-BUs to node P. The OH field in each FG-BU represents a fourth CMT message shown in Figure 9b. The formats of the three fourth CMT messages are the same. The three fourth CMT messages are used to indicate that the updated uplink time slot table takes effect in the next multiframe.
[0250] Specifically, the node PE2 may respectively set the value of the ACK field in the fourth ACK message shown in FIG. 9 b to 0 and the value of the CMT field to 1 to obtain the fourth CMT message shown in FIG. 9 b .
[0251] In addition, in other embodiments, when the node PE2 receives the fourth ACK message as shown in FIG. 9 d , the format of the fourth CMT message sent by the node PE2 is as shown in FIG. 9 d .
[0252] In S911, after receiving the fourth CMT message sent by the node PE2, the node P sends a fourth REQ message to the node PE1.
[0253] In this step, the introduction of the node P sending the fourth REQ message can refer to the introduction of the node PE2 sending the fourth REQ message in the aforementioned S908, which will not be repeated here.
[0254] In S912 , after receiving the fourth REQ message sent by the node P, the node PE1 increases the uplink bandwidth of the first service according to the fourth REQ message, and then sends a fourth ACK message to the node P.
[0255] In this step, the description of node PE1 reducing the downlink bandwidth of the first service and sending the second ACK message can refer to the description of node P reducing the downlink bandwidth of the first service and sending the second ACK message in S909, which will not be repeated here.
[0256] In S913 , after receiving the fourth ACK message sent by the node PE1 , the node P sends one or more fourth CMT messages to the node PE1 .
[0257] In this step, the introduction of node P sending one or more fourth CMT messages to node PE1 can refer to the description of node PE2 sending one or more fourth CMT messages to node P in the aforementioned S910, which will not be repeated here.
[0258] FIG10 a is a flow chart of a bandwidth adjustment method provided in an embodiment of the present application. The method is used to increase both uplink bandwidth and downlink bandwidth, and includes the following steps S1001 to S1019.
[0259] In S1001 , the node PE1 receives a bandwidth adjustment request from a user-side node, and executes S1002 if it is determined that the bandwidth adjustment request indicates to increase the uplink bandwidth and the downlink bandwidth of the first service.
[0260] The specific process in this step can refer to the introduction in the aforementioned S901 and will not be repeated here.
[0261] In S1002, the node PE1 sends a first time slot addition notification DD message to the node P. The first DD message is used to notify the node P and the node PE2 to send a third REQ message.
[0262] In this step, the node PE1 may send an FG-BU to the node P. The OH field in the FG-BU indicates the first DD message. The first DD message is used to notify the node P and the node PE2 to adjust the bandwidth of the first service.
[0263] When it is determined that the uplink and downlink bandwidths of the first service are to be increased and the timeslot adjustments for both are equal, the format of the first DD message is shown in FIG10b , as described above with respect to FIG7 . In the first DD message shown in FIG10b , the MO field has a value of 11, the BA field has a value of 1, the LE field has a value of 1, the FG-client ID field has a value indicating the service identifier in the bandwidth adjustment request, the DD field has a value of 1, the REQ field, the CMT field, and the ACK field have a default value of 0, the FG-slot ID field has a value not indicating a timeslot identifier, and the EN field has a value indicating the timeslot adjustments for the uplink and downlink bandwidths of the first service.
[0264] If it is determined that the uplink and downlink bandwidths of the first service are to be increased and the timeslot adjustment amounts for the two are unequal, the format of the first DD message is shown in Figure 10c, as described above with respect to Figure 7. In the first DD message shown in Figure 10c, the value of the MO field is 10, the value of the BA field is 1, the value of the LE field is 1, the value of the FG-client ID field indicates the service identifier in the bandwidth adjustment request, the value of the DD field is 1, the values of the REQ field, the CMT field, and the ACK field are all the default values of 0, and the values of the FG-slot ID field and the EN field indicate the timeslot adjustment amounts for the uplink and downlink bandwidths of the first service, respectively.
[0265] In addition, in other embodiments, when the number of time slot adjustments for the uplink bandwidth of the first service is equal to the number of time slot adjustments for the downlink bandwidth of the first service, for example, both are N, node PE1 may send N first DD messages, where the Nth first DD message is shown in FIG10d. In the Nth first DD message shown in FIG10d, the value of the MO field is 11, the value of the BA field is 1, the value of the LE field is 1, the value of the FG-client ID field represents the service identifier in the bandwidth adjustment request, the value of the FG-slot ID field represents the time slot identifier of the Nth downlink time slot to be added corresponding to the downlink bandwidth, the value of the EN field represents the number of time slot adjustments for the uplink bandwidth and downlink bandwidth of the first service, the value of the DD field is 1, and the values of the REQ field, the CMT field, and the ACK field are all the default value 0. The difference between the 1st first DD message to the N-1th first DD message and the Nth first DD message is that the value of the LE field in the 1st first DD message to the N-1th first DD message is 0, and the value of the FG-slot ID field in the 1st first DD message to the N-1th first DD message respectively represents the time slot identifiers of the 1st to the N-1th downlink time slots to be added corresponding to the downlink bandwidth.
[0266] It should be noted that the values of the MFI field, Flag field, and CRC field in each DD message shown in Figures 10b to 10d can be determined based on the functional description of each field above in this application and according to actual needs. Furthermore, this embodiment of the application does not specifically limit the values of other fields in each FG-BU except the OH field. The values of other fields in each FG-BU except the OH field can be determined based on actual service data.
[0267] In S1003 , after receiving the first DD message sent by the node PE1 , the node P sends a third REQ message to the node PE1 .
[0268] In this step, after receiving the first DD message shown in FIG10b or FIG10c, node P may send an FG-BU to node PE1. The value of the OH field in the FG-BU indicates the third REQ message. Node P may set the value of the REQ field in the first DD message shown in FIG10b or FIG10c to 1, thereby obtaining the third REQ message shown in FIG10b or FIG10c.
[0269] In addition, in other embodiments, after receiving the first DD message shown in Figure 10d, node P may send N FG-BUs to node PE1, where the value of the OH field in each FG-BU represents a third REQ message. Node P may set the value of the REQ field in the N received first DD messages to 1, thereby obtaining N third REQ messages. For example, setting the value of the REQ field in the Nth first DD message shown in Figure 10d to 1 results in the Nth third REQ message shown in Figure 10d.
[0270] In S1004, after receiving the third REQ message sent by node P, node PE1 increases the downlink bandwidth of the first service according to the third REQ message, and then sends a third ACK message to node P. The third ACK message is used to indicate that the downlink bandwidth of the first service is increased successfully.
[0271] In this step, the introduction of the node PE1 increasing the downlink bandwidth of the first service can refer to the introduction in the aforementioned S902, which will not be repeated here.
[0272] In this step, after increasing the downlink bandwidth of the first service, node P can send an FG-BU to node PE1. The OH field in the FG-BU represents the third ACK message. Node P can set the value of the REQ field in the third REQ message shown in Figure 10b or Figure 10c to 0 and the value of the ACK field to 1, thereby obtaining the third ACK message shown in Figure 10b or Figure 10c.
[0273] In addition, in other embodiments, when node P receives N third REQ messages, the Nth third REQ message is shown in Figure 10d, for example, node P can set the value of the REQ field in the Nth third REQ message to 0 and set the value of the ACK field to 1 to obtain the third ACK message shown in Figure 10d.
[0274] In S1005 , after receiving the third ACK message sent by the node PE1 , the node P sends one or more third CMT messages to the node PE1 .
[0275] In this step, node PE1 can send three FG-BUs to node P. The value of the OH field in each FG-BU represents a third CMT message, and the format of the third CMT messages in the three FG-BUs is the same. Specifically, node PE1 can set the value of the ACK field to 0 and the value of the CMT field to 1 in the third ACK message shown in Figure 10b or Figure 10c, respectively, to obtain the third CMT message shown in Figure 10b or Figure 10c.
[0276] In addition, in other embodiments, when node PE1 receives the third ACK message as shown in Figure 10d, node PE1 can set the value of the ACK field in the third ACK message as shown in Figure 10d to 0 and the value of the CMT field to 1, respectively, to obtain the third CMT message as shown in Figure 10d.
[0277] In S1006 , after sending the third CMT message to the node PE1 , the node P sends the first DD message to the node PE2 .
[0278] In this step, the introduction of node P sending the first DD message to node PE2 can refer to the description of node PE1 sending the first DD message to node P in S1002 above, which will not be repeated here.
[0279] In S1007 , after receiving the first DD message sent by the node P, the node PE2 sends a third REQ message to the node P.
[0280] In this step, the introduction of node PE2 sending the third REQ message to node P can refer to the description of node P sending the third REQ message to node PE1 in S1003 above, which will not be repeated here.
[0281] In S1008 , after receiving the third REQ message sent by the node PE2 , the node P increases the uplink bandwidth of the first service according to the third REQ message, and then sends a third ACK message to the node PE2 .
[0282] In this step, the introduction of node P increasing the uplink bandwidth of the first service and sending the third ACK message to node PE2 can refer to the description of node PE1 increasing the uplink bandwidth of the first service and sending the third ACK message to node P in S1004 above, which will not be repeated here.
[0283] In S1009 , after receiving the third ACK message sent by node P, node PE2 sends one or more third CMT messages to node P.
[0284] In this step, the introduction of node PE2 and node P sending one or more third CMT messages can refer to the description of node P and node PE1 sending one or more third CMT messages in the aforementioned S1005, which will not be repeated here.
[0285] In S1010 , after sending the third CMT message, the node PE2 increases the downlink bandwidth of the first service according to the first DD message sent by the node P.
[0286] In this step, the introduction of the node PE2 increasing the downlink bandwidth of the first service can refer to the description of the node PE1 increasing the downlink bandwidth of the first service in S1004 above, which will not be repeated here.
[0287] In S1011 , after increasing the downlink bandwidth of the first service, the node PE2 sends a second DD message to the node P. The second DD message is used to notify the node P and the node PE1 to send a fourth REQ message.
[0288] In this step, the node PE2 may send an FG-BU to the node P. The OH field in each FG-BU represents a second DD message, so as to instruct the node P to send the second DD message.
[0289] When the node PE2 receives the first DD message shown in FIG. 10b or FIG. 10c , the node PE2 may set the value of the MO field in the first DD message shown in FIG. 10b or FIG. 10c to 00 to obtain the second DD message shown in FIG. 10b or FIG. 10c .
[0290] In this embodiment, when node PE2 receives N first DD messages, node PE2 may set the value of the MO field in the N first DD messages to 00, modify the value of the FG-slot ID to the timeslot identifier of the sub-timeslot to be added corresponding to the uplink bandwidth, and obtain N second DD messages. For example, the value of the MO field in the Nth first DD message shown in Figure 10d is set to 00, and the value of the FG-slot ID is modified to the timeslot identifier of the Nth sub-timeslot to be added corresponding to the uplink bandwidth, to obtain the Nth second DD message shown in Figure 10d.
[0291] In S1012 , after receiving the second DD message sent by the node PE2 , the node P sends a fourth REQ message to the node PE2 .
[0292] In this step, node P may send an FG-BU to node PE2, where the OH field in the FG-BU indicates the fourth REQ message. Node P may set the value of the REQ field in the second DD message shown in FIG10b or FIG10c to 1, thereby obtaining the fourth REQ message shown in FIG10b or FIG10c.
[0293] In addition, when node P receives N second DD messages, the value of the REQ field in the N second DD messages is set to 1, thereby obtaining N fourth REQ messages. For example, the value of the REQ field in the Nth second DD message shown in FIG10d is set to 1, thereby obtaining the Nth fourth REQ message shown in FIG10d.
[0294] In S1013 , after receiving the fourth REQ message sent by the node P, the node PE2 increases the uplink bandwidth of the first service according to the fourth REQ message, and then sends a fourth ACK message to the node P.
[0295] In this step, the description of how node PE2 increases the uplink bandwidth of the first service can be found in the description of S908 above and will not be repeated here. After increasing the uplink bandwidth of the first service, node PE2 can send an FG-BU to node P. The value of the OH field in this FG-BU represents the fourth ACK message. Specifically, node PE2 can set the value of the REQ field in the fourth REQ message shown in Figure 10b or Figure 10c to 0 and the value of the ACK field to 1, resulting in the fourth ACK message shown in Figure 10b or Figure 10c.
[0296] In addition, in other embodiments, when node PE2 receives N fourth REQ messages, the Nth fourth REQ message is shown in Figure 10d, and node PE2 can set the value of the REQ field in the Nth fourth REQ message to 0 and set the value of the ACK field to 1 to obtain the fourth ACK message shown in Figure 10d.
[0297] In S1014, after receiving the fourth ACK message sent by the node PE2, the node P sends one or more fourth CMT messages to the node PE2.
[0298] In this step, the node PE2 may send three FG-BUs to the node P. The value of the OH field in each FG-BU represents a fourth CMT message, and the formats of the three fourth CMT messages are the same.
[0299] Specifically, the node PE2 may respectively set the value of the ACK field to 0 and the value of the CMT field to 1 in the fourth ACK message shown in FIG. 10b or FIG. 10c , to obtain the fourth CMT message shown in FIG. 10b or FIG. 10c .
[0300] In addition, in other embodiments, when node PE2 receives the fourth ACK message shown in Figure 10d, node PE1 can set the value of the ACK field in the fourth ACK message shown in Figure 10d to 0 and the value of the CMT field to 1, respectively, to obtain the fourth CMT message shown in Figure 10d.
[0301] In S1015 , after sending the fourth CMT message to the node PE1 , the node P sends the second DD message to the node PE2 .
[0302] In this step, the introduction of node P sending the second DD message to node PE2 can refer to the introduction of node PE2 sending the second DD message to node P in S1011 above, which will not be repeated here.
[0303] In S1016 , after receiving the second DD message sent by node P, node PE1 sends a fourth REQ message to node P.
[0304] In this step, the description of node PE1 sending the fourth REQ message to node P can refer to the description of node P sending the fourth REQ message to node PE2 in S1012 above, which will not be repeated here.
[0305] In S1017 , after receiving the fourth REQ message sent by the node PE1 , the node P increases the uplink bandwidth of the first service according to the fourth REQ message, and then sends a fourth ACK message to the node PE1 .
[0306] In this step, the introduction of node P increasing the uplink bandwidth and sending the fourth ACK message can refer to the introduction of node PE2 increasing the uplink bandwidth and sending the fourth ACK message in S1013 above, which will not be repeated here.
[0307] In S1018 , after receiving the fourth ACK message sent by node P, node PE1 sends one or more fourth CMT messages to node P.
[0308] In this step, the introduction of node PE1 sending the fourth CMT message can refer to the introduction of node P sending the fourth CMT message in the aforementioned S1014, which will not be repeated here.
[0309] In S1019 , the node PE1 increases the uplink bandwidth of the first service according to the second DD message sent by the node P.
[0310] In this step, the node PE1 increases the uplink bandwidth of the first service. The above description of the node P increasing the uplink bandwidth of the first service in S1017 can be referred to, and will not be repeated here.
[0311] In the method embodiments shown in Figures 8a, 9a, and 10a above, the source node in the slice dedicated line receives a bandwidth adjustment request from the user side indicating that the same adjustment method is used for the bidirectional bandwidth. The mode field and bandwidth adjustment field in the FG-BU are used to instruct the intermediate node and the destination node to reduce or increase the bidirectional bandwidth. This can reduce the number of times the network management system participates in bandwidth adjustment, reduce the load on the network management system, and improve the reliability of bandwidth adjustment. In addition, in the above method embodiment, the FG-slotID field and EN field in the OH field are used to indicate the number of time slot adjustments, which can achieve batch adjustment of the uplink bandwidth and downlink bandwidth when the number of time slot adjustments is different.
[0312] The following is a detailed description using the example of reducing the uplink bandwidth and increasing the downlink bandwidth.
[0313] FIG11a is a flow chart of a bandwidth adjustment method provided in an embodiment of the present application. The method is used to reduce the uplink bandwidth and increase the downlink bandwidth, and the method includes S1101-S1107.
[0314] In S1101 , the node PE1 receives a bandwidth adjustment request from a user-side node. If it is determined that the bandwidth adjustment request indicates to reduce the uplink bandwidth of the first service and increase the downlink bandwidth of the first service, step S1102 is executed.
[0315] In this embodiment, as shown in FIG6 , user 11 may send the bandwidth adjustment request to the user-side node through the terminal device. After receiving the bandwidth adjustment request, the user-side node sends it to node PE1 .
[0316] In this step, taking the bandwidth adjustment request as an example, where the service identifier of the first service and the target channel bandwidth of the first service are included, the target channel bandwidth may include an uplink target bandwidth and a downlink target bandwidth. Node PE1 may calculate the uplink bandwidth increment and the downlink bandwidth increment for the first service based on the uplink target bandwidth and the downlink target bandwidth, as well as the current uplink bandwidth and downlink bandwidth of the first service. Then, based on the uplink bandwidth increment and the downlink bandwidth increment of the first service, it is determined whether the bandwidth adjustment request indicates a decrease in the uplink bandwidth of the first service and an increase in the downlink bandwidth of the first service. For example, if the uplink bandwidth increment is less than 0 and the downlink bandwidth increment is greater than 0, it is determined that the bandwidth adjustment request indicates a decrease in the uplink bandwidth of the first service and an increase in the downlink bandwidth of the first service, and S1102 is executed. Furthermore, if the bandwidth adjustment request includes the uplink bandwidth increment and the downlink bandwidth increment of the first service, node PE1 may directly determine whether the bandwidth adjustment request indicates a decrease in the uplink bandwidth of the first service and an increase in the downlink bandwidth of the first service.
[0317] In S1102, node PE1 reduces the uplink bandwidth of the first service and increases the downlink bandwidth of the first service according to the bandwidth adjustment request, and then sends a fifth timeslot adjustment request REQ message to node P. The fifth REQ message is used to instruct to reduce the uplink bandwidth of the first service and increase the downlink bandwidth of the first service.
[0318] In this step, the node PE1 may determine the timeslot adjustment number of the uplink bandwidth and the timeslot adjustment number of the downlink bandwidth of the first service according to the uplink bandwidth increment, the downlink bandwidth increment and the bandwidth of the sub-timeslot.
[0319] Then, node PE1 reduces the uplink sub-timeslots for transmitting the first service in the uplink time slot table based on the number of time slots adjusted for the uplink bandwidth of the first service, thereby reducing the uplink bandwidth of the first service. Furthermore, node PE1 adds the downlink sub-timeslots for transmitting the first service in the downlink time slot table based on the number of time slots adjusted for the downlink bandwidth of the first service, thereby increasing the downlink bandwidth of the first service.
[0320] In this step, after reducing the uplink bandwidth of the first service and increasing the downlink bandwidth of the first service, node PE1 can send an FG-BU to node P. The OH field in the FG-BU represents the fifth REQ message shown in Figure 11b, to instruct node P and the host node PE2 to reduce the uplink bandwidth of the first service and increase the downlink bandwidth of the first service.
[0321] Specifically, when reducing the uplink bandwidth of the first service and increasing its downlink bandwidth, according to the aforementioned description of FIG. 7 , the format of the fifth REQ message is shown in FIG. 11b . In the fifth REQ message shown in FIG. 11b , the value of the MO field is 10, the value of the BA field is 0, the value of the LE field is 1, the value of the FG-client ID field represents the service identifier in the bandwidth adjustment request, the values of the FG-slot ID field and the EN field represent the number of time slots adjusted for the uplink bandwidth and downlink bandwidth of the first service, respectively, the value of the REQ field is 1, and the values of the DD field, CMT field, and ACK field are all the default value of 0. The values of the MFI field, Flag field, and CRC field in the fifth REQ message can be determined based on the functional description of each field above in this application and according to actual needs.
[0322] In S1103, node P reduces the uplink bandwidth of the first service and increases the downlink bandwidth of the first service according to the fifth REQ message sent by node PE1, and then sends a fifth timeslot adjustment acknowledgement ACK message to node PE1. The fifth ACK message is used to indicate that the reduction of the uplink bandwidth of the first service and the increase of the downlink bandwidth of the first service are successful.
[0323] In this step, node P reduces the uplink bandwidth of the first service and increases the downlink bandwidth of the first service according to the fifth REQ message sent by node PE1, including: determining to reduce the uplink bandwidth of the first service and to increase the downlink bandwidth of the first service based on the values of the MO field, the BA field, and the DD field in the fifth REQ message. Then, node P determines the timeslot adjustment number for the uplink bandwidth of the first service and the timeslot adjustment number for the downlink bandwidth of the first service based on the values of the FG-slot ID field and the EN field in the fifth REQ message, reducing the uplink sub-timeslot for transmitting the first service in the uplink timeslot table according to the timeslot adjustment number for the uplink bandwidth of the first service, thereby reducing the uplink bandwidth of the first service; and increasing the downlink sub-timeslot for transmitting the first service in the downlink timeslot table according to the timeslot adjustment number for the downlink bandwidth of the first service, thereby increasing the downlink bandwidth of the first service.
[0324] In this step, after reducing the uplink bandwidth of the first service and increasing the downlink bandwidth of the first service, node P sends an FG-BU to node PE1. The OH field in the FG-BU represents the fifth ACK message shown in Figure 11b. Node P can set the value of the REQ field in the fifth REQ message shown in Figure 11b to 0 and the value of the ACK field to 1, thereby obtaining the fifth ACK message shown in Figure 11b.
[0325] In S1104 , after receiving the fifth ACK message sent by node P, node PE1 sends one or more fifth CMT messages to node P.
[0326] In this step, node PE1 can send three FG-BUs to node P. The OH field in each FG-BU represents a fifth CMT message shown in Figure 11b. The format of the fifth CMT messages in the three FG-BUs is the same. The three fifth CMT messages are used to indicate that the updated uplink time slot table and downlink time slot table take effect in the next multiframe.
[0327] Specifically, the node PE1 may respectively set the value of the ACK field to 0 and the value of the CMT field to 1 in the fifth ACK message shown in FIG. 11 b , to obtain the fifth CMT message shown in FIG. 11 b .
[0328] In S1105 , after receiving the fifth CMT message sent by the node PE1 , the node P sends a fifth REQ message to the node PE2 .
[0329] In this step, the introduction of node P sending the fifth REQ message to node PE2 can refer to the description of node PE1 sending the fifth REQ message to node P in S1102 above, which will not be repeated here.
[0330] In S1106 , after receiving the fifth REQ message sent by node PE2 , node PE2 reduces the uplink bandwidth of the first service and increases the downlink bandwidth of the first service according to the fifth REQ message, and then sends a fifth ACK message to node P.
[0331] In this step, the introduction of node PE2 reducing the uplink bandwidth of the first service and increasing the downlink bandwidth of the first service and sending the fifth ACK message to node P can refer to the description of node P reducing the uplink bandwidth of the first service and increasing the downlink bandwidth of the first service and sending the fifth ACK message to node P in the aforementioned S1103, which will not be repeated here.
[0332] In S1107 , after receiving the fifth ACK message sent by the node PE2 , the node P sends a fifth CMT message to the node PE2 .
[0333] In this step, the introduction of node P sending the fifth CMT message to node PE2 can refer to the description of node PE1 sending the fifth CMT message to node P in the above S1104.
[0334] The following takes increasing the upstream bandwidth and reducing the downstream bandwidth as an example for detailed description.
[0335] Figure 12a is a flow chart of a bandwidth adjustment method provided by an embodiment of the present application. The method is used to increase the uplink bandwidth of a first service and reduce the downlink bandwidth of the first service, and the method may include S1201-S1208.
[0336] In S1201 , the node PE1 receives a bandwidth adjustment request from a user-side node. If it is determined that the bandwidth adjustment request indicates to increase the uplink bandwidth of the first service and decrease the downlink bandwidth of the first service, step S1202 is executed.
[0337] In this embodiment, as shown in FIG6 , user 11 may send the bandwidth adjustment request to the user-side node through the terminal device. After receiving the bandwidth adjustment request, the user-side node sends it to node PE1 .
[0338] In this step, taking the bandwidth adjustment request as an example, where the service identifier of the first service and the target channel bandwidth of the first service are included, the target channel bandwidth may include an uplink target bandwidth and a downlink target bandwidth. Node PE1 may calculate the uplink bandwidth increment and the downlink bandwidth increment for the first service based on the uplink target bandwidth and the downlink target bandwidth, as well as the current uplink bandwidth and downlink bandwidth of the first service. Then, based on the uplink bandwidth increment and the downlink bandwidth increment of the first service, it is determined whether the bandwidth adjustment request indicates an increase in the uplink bandwidth of the first service and a decrease in the downlink bandwidth of the first service. For example, if the uplink bandwidth increment is greater than 0 and the downlink bandwidth increment is less than 0, it is determined that the bandwidth adjustment request indicates an increase in the uplink bandwidth of the first service and a decrease in the downlink bandwidth of the first service, and S1202 is executed. Furthermore, if the bandwidth adjustment request includes the uplink bandwidth increment and the downlink bandwidth increment of the first service, node PE1 may directly determine whether the bandwidth adjustment request indicates an increase in the uplink bandwidth of the first service and a decrease in the downlink bandwidth of the first service.
[0339] In S1202, the node PE1 sends a sixth REQ message to the node PE2 via the node P. The sixth REQ message is used to instruct to increase the uplink bandwidth of the first service and to reduce the downlink bandwidth of the first service.
[0340] In this step, the node PE1 may send an FG-BU to the node P, where the OH field in the FG-BU indicates the sixth REQ message.
[0341] Specifically, the format of the sixth REQ message is shown in Figure 12b. In the case where it is determined to increase the uplink bandwidth of the first service and reduce the downlink bandwidth of the first service, according to the aforementioned description of Figure 7, the format of the sixth REQ message is shown in Figure 12b. In the sixth REQ message shown in Figure 12b, the value of the MO field is 10, the value of the BA field is 1, the value of the LE field is 1, the value of the FG-client ID field represents the service identifier in the bandwidth adjustment request, the value of the FG-slot ID field and the value of the EN field represent the time slot adjustment number of the uplink bandwidth and the time slot adjustment number of the downlink bandwidth of the first service, respectively, the value of the REQ field is 1, the values of the DD field, the CMT field, and the ACK field are all the default value 0, and the values of the MFI field, the Flag field, and the CRC field can be determined according to actual needs based on the functional description of each field above in this application.
[0342] The node PE1 may determine the timeslot adjustment number of the uplink bandwidth and the timeslot adjustment number of the downlink bandwidth of the first service according to the uplink bandwidth increment, the downlink bandwidth increment, and the bandwidth of the sub-timeslot.
[0343] After receiving the sixth REQ message sent by node PE1, node P determines to increase the uplink bandwidth of the first service and reduce the downlink bandwidth of the first service according to the value of the MO field, the value of the BA field, and the value of the DD field in the sixth REQ message, and then sends the sixth REQ message to node PE2.
[0344] In S1203 , after receiving the sixth REQ message sent by the node P, the node PE2 increases the uplink bandwidth of the first service and decreases the downlink bandwidth of the first service according to the sixth REQ message, and then sends the sixth REQ message to the node P.
[0345] In this step, node PE2 increases the uplink bandwidth of the first service and reduces the downlink bandwidth of the first service according to the sixth REQ message, including determining to increase the uplink bandwidth of the first service and reduce the downlink bandwidth of the first service according to the value of the MO field, the value of the BA field, and the value of the DD field in the sixth REQ message.
[0346] Then, based on the value of the FG-slot ID field and the value of the EN field in the sixth REQ message, the time slot adjustment number of the uplink bandwidth of the first service and the time slot adjustment number of the downlink bandwidth of the first service are determined, and the uplink sub-time slot for transmitting the first service is added to the uplink time slot table according to the time slot adjustment number of the uplink bandwidth of the first service, thereby increasing the uplink bandwidth of the first service, and the downlink sub-time slot for transmitting the first service is reduced in the downlink time slot table according to the time slot adjustment number of the downlink bandwidth of the first service, thereby reducing the downlink bandwidth of the first service.
[0347] In this step, after increasing the uplink bandwidth of the first service and reducing the downlink bandwidth of the first service, the node PE2 sends an FG-BU to the node P. The OH field in the FG-BU indicates a sixth REQ message.
[0348] In S1204 , after receiving the sixth REQ message sent by the node PE2 , the node P increases the uplink bandwidth of the first service and decreases the downlink bandwidth of the first service according to the sixth REQ message, and then sends a sixth ACK message to the node PE2 .
[0349] In this step, the introduction of node P increasing the uplink bandwidth of the first service and reducing the downlink bandwidth of the first service can refer to the description of node PE2 increasing the uplink bandwidth of the first service and reducing the downlink bandwidth of the first service in S1203 above, which is not repeated here.
[0350] In this step, after increasing the uplink bandwidth of the first service and reducing the downlink bandwidth of the first service, node P sends an FG-BU to node PE2. The OH field in the FG-BU represents the sixth ACK message shown in Figure 12b. Specifically, node P can set the value of the REQ field in the sixth REQ message shown in Figure 12b to 0 and the value of the ACK field to 1, thereby obtaining the sixth ACK message shown in Figure 12b.
[0351] In 1205 , after receiving the sixth ACK message sent by node P, node PE2 sends one or more sixth CMT messages to node P.
[0352] In this step, node PE2 can send three FG-BUs to node P. The OH field in each FG-BU represents a sixth CMT message shown in Figure 12b. The three sixth CMT messages are used to indicate that the updated uplink time slot table and downlink time slot table take effect in the next multiframe.
[0353] Specifically, the node PE2 may respectively set the value of the ACK field in the sixth ACK message shown in FIG. 12 b to 0 and the value of the CMT field to 1, thereby obtaining the sixth CMT message shown in FIG. 12 b .
[0354] In 1206, after receiving the sixth CMT message sent by the node PE2, the node P sends a sixth REQ message to the node PE1.
[0355] In this step, the introduction of node P sending the sixth REQ message to node PE1 can refer to the description of node PE2 sending the sixth REQ message to node P in S1203 above, which will not be repeated here.
[0356] In 1207 , after receiving the sixth REQ message sent by the node P, the node PE1 increases the uplink bandwidth of the first service and decreases the downlink bandwidth of the first service according to the sixth REQ message, and then sends a sixth ACK message to the node P.
[0357] In this step, the introduction of node PE1 increasing the uplink bandwidth of the first service and reducing the downlink bandwidth of the first service and sending the sixth ACK message to node P can refer to the description of node P increasing the uplink bandwidth of the first service and reducing the downlink bandwidth of the first service and sending the sixth ACK message to node PE2 in the aforementioned S1204, which will not be repeated here.
[0358] In 1208, after receiving the sixth ACK message sent by the node PE1, the node P sends one or more sixth CMT messages to the node PE1.
[0359] In this step, the introduction of node P sending one or more sixth CMT messages to node PE1 can refer to the description of node PE2 sending the sixth CMT message to node P in S1205 above, which will not be repeated here.
[0360] In the method embodiments shown in Figures 11a and 12a above, the source node in the slice dedicated line receives a bandwidth adjustment request from the user side indicating that different adjustment methods are used for the bidirectional bandwidth. The mode field and bandwidth adjustment field in the FG-BU are used to instruct the intermediate node and the destination node to adjust the bidirectional bandwidth. This can reduce the number of times the network management system participates in bandwidth adjustment, reduce the load on the network management system, and improve the reliability of bandwidth adjustment. In addition, in the above method embodiment, the FG-slotID field and EN field in the OH field are used to indicate the number of time slot adjustments, which can achieve batch adjustment of time slots for uplink and downlink bandwidth, as well as batch adjustment of uplink and downlink bandwidth under different time slot adjustment numbers.
[0361] In other embodiments, when adjusting the bidirectional bandwidth of a service, if the time slot adjustment number of the uplink bandwidth and the time slot adjustment number of the downlink bandwidth of the service to be adjusted are equal and not 1, only the EN field in the OH field can be used to indicate the time slot adjustment number, and the FG-slot field is not used (for example, all 0s) or is used to indicate other functions.
[0362] The following describes how to reduce the downlink bandwidth as an example.
[0363] Figure 13a is a flow chart of a bandwidth adjustment method provided by an embodiment of the present application. The method is used to reduce the downlink bandwidth of a first service, and the method may include S1301-S1308.
[0364] In S1301 , the node PE1 receives a bandwidth adjustment request from a user-side node. If it is determined that the bandwidth adjustment request indicates to reduce the downlink bandwidth of the first service, step S1302 is executed.
[0365] In this embodiment, as shown in Figure 6, user 11 can send the bandwidth adjustment request to the user-side node through the terminal device, and the user-side node sends the bandwidth adjustment request to node PE1 after receiving the bandwidth adjustment request. The bandwidth adjustment request may include the service identifier of the first service and the downlink target bandwidth of the first service.
[0366] In this step, the bandwidth adjustment request includes the service identifier of the first service and the downlink target bandwidth of the first service. Node PE1 can calculate the downlink bandwidth increment for the first service based on the downlink target bandwidth and the current downlink bandwidth of the first service. Then, based on the downlink bandwidth increment for the first service, it is determined whether the bandwidth adjustment request indicates a decrease in the downlink bandwidth of the first service. For example, if the downlink bandwidth increment is less than 0, it is determined that the bandwidth adjustment request indicates a decrease in the downlink bandwidth of the first service, and S1302 is executed. Furthermore, if the bandwidth adjustment request includes the downlink bandwidth increment for the first service, node PE1 can directly determine whether the bandwidth adjustment request indicates a decrease in the downlink bandwidth of the first service.
[0367] In 1302 , the node PE1 sends a seventh REQ message to the node PE2 via the node P. The seventh REQ message is used to instruct to reduce the downlink bandwidth of the first service.
[0368] In this step, the node PE1 may send an FG-BU to the node P. The OH field in the FG-BU indicates the seventh REQ message shown in FIG13 b .
[0369] In the event that the downlink bandwidth of the first service is determined to be reduced, according to the aforementioned description regarding FIG. 7 , the value of the MO field in the seventh REQ message shown in FIG. 13b is 01, and the value of the BA field is 0. The value of the LE field in the seventh REQ message is 1. The value of the FG-client ID field in the seventh REQ message represents the service identifier in the bandwidth adjustment request. The FG-slot ID field in the seventh REQ message is not used, and the value of the EN field represents the number of time slots to adjust the downlink bandwidth of the first service. The value of the REQ field in the seventh REQ message is 1. The values of the DD field, CMT field, and ACK field in the seventh REQ message are all the default values of 0. The values of the MFI field, Flag field, and CRC field in the seventh REQ message can be determined according to actual needs based on the functional description of each field above in this application.
[0370] The node PE1 may determine the number of time slots to adjust the downlink bandwidth of the first service according to the downlink bandwidth increment and the bandwidth of the sub-time slot.
[0371] After receiving the seventh REQ message sent by the node PE1, the node P determines to reduce the downlink bandwidth of the first service according to the values of the MO field and the BA field in the seventh REQ message, and then sends the seventh REQ message to the node PE2.
[0372] In addition, in other embodiments, node PE1 may send N seventh REQ messages to node P, with the Nth seventh REQ message being shown in FIG13c . In the Nth seventh REQ message shown in FIG13c , the value of the MO field is 01, the value of the BA field is 0, the value of the LE field is 1, the value of the FG-client ID field represents the service identifier in the bandwidth adjustment request, the value of the FG-slot ID field represents the time slot identifier of the Nth downlink sub-time slot to be reduced for the aforementioned first service, the value of the EN field represents the time slot adjustment amount, the value of the REQ field is 1, and the values of the DD field, CMT field, and ACK field are all default values of 0. Unlike the Nth seventh REQ message, the value of the LE field in the 1st to N-1th seventh REQ messages is 0, and the value of the FG-slot ID field represents the time slot identifiers of the 1st to N-1th downlink sub-time slots to be reduced for the aforementioned first service.
[0373] After receiving N seventh REQ messages (shown in Figure 13c) sent by node PE1, node P determines to reduce the downlink bandwidth of the first service based on the values of the MO field and the BA field in the seventh REQ message, and sequentially sends N seventh REQ messages to node PE2. Specifically, node P may send N FG-BUs to node PE2, with the value of the OH field in each FG-BU representing one seventh REQ message.
[0374] It should be noted that the values of the MFI field, Flag field, and CRC field in each message shown in Figures 13b and 13c can be determined based on the functional description of each field above in this application and according to actual needs. Furthermore, this embodiment of the application does not specifically limit the values of fields other than the OH field in each FG-BU. The values of fields other than the OH field in each FG-BU can be determined based on actual service data.
[0375] In S1303 , after receiving the seventh REQ message sent by the node P, the node PE2 reduces the downlink bandwidth of the first service according to the seventh REQ message, and then sends an eighth REQ message to the node P.
[0376] In this step, node PE2 reduces the downlink bandwidth of the first service according to the seventh REQ message, including determining the reduction in the downlink bandwidth of the first service based on the values of the MO field and the BA field in the seventh REQ message, then determining the timeslot adjustment number for the downlink bandwidth of the first service based on the value of the EN field in the seventh REQ message, and reducing the downlink sub-timeslots for transmitting the first service in the downlink timeslot table according to the timeslot adjustment number for the downlink bandwidth of the first service, thereby reducing the downlink bandwidth of the first service. After reducing the downlink bandwidth of the first service, node PE2 sends an FG-BU to node P. The value of the OH field in the FG-BU represents the eighth REQ message shown in Figure 13b. Node PE2 can set the value of the MO field in the seventh REQ message shown in Figure 13b to 00, thereby obtaining the eighth REQ message shown in Figure 13b.
[0377] In addition, in other embodiments, when node PE2 receives N seventh REQ messages, node PE2 reduces the downlink bandwidth of the first service according to the seventh REQ messages, including: determining to reduce the downlink bandwidth of the first service according to the value of the MO field and the value of the BA field in each seventh REQ message, then obtaining the timeslot identifier to be reduced according to the value of the FG-slot ID field in each seventh REQ message, and reducing the downlink sub-timeslot for transmitting the first service in the downlink timeslot table according to the timeslot identifier to be reduced, thereby reducing the downlink bandwidth of the first service. After reducing the downlink bandwidth of the first service, node PE2 may set the value of the MO field in the N seventh REQ messages to 00, obtain N eighth REQ messages, and send N FG-BUs to node P. The value of the OH field in each FG-BU represents an eighth REQ message. The Nth eighth REQ message is shown in FIG13c.
[0378] In S1304 , after receiving the eighth REQ message sent by the node PE2 , the node P reduces the downlink bandwidth of the first service according to the eighth REQ message, and then sends an eighth ACK message to the node PE2 .
[0379] In this step, node P reduces the downlink bandwidth of the first service based on the eighth REQ message, including determining the reduction in the downlink bandwidth of the first service based on the values of the MO field and the BA field in the eighth REQ message, then determining the timeslot adjustment number for the downlink bandwidth of the first service based on the value of the EN field in the eighth REQ message, and reducing the downlink sub-timeslots for transmitting the first service in the downlink timeslot table according to the timeslot adjustment number for the downlink bandwidth of the first service, thereby reducing the downlink bandwidth of the first service. After reducing the downlink bandwidth of the first service, node P sends an FG-BU to node PE2. The value of the OH field in the FG-BU represents the eighth ACK message shown in Figure 13b. Node PE2 can set the value of the ACK field in the eighth REQ message shown in Figure 13b to 1 and the value of the REQ field to 0, thereby obtaining the eighth ACK message shown in Figure 13b.
[0380] In addition, in other embodiments, when node P receives N eighth REQ messages, node P reduces the downlink bandwidth of the first service according to the eighth REQ messages, including: determining to reduce the downlink bandwidth of the first service according to the value of the MO field and the value of the BA field in each eighth REQ message, then obtaining the timeslot identifier to be reduced according to the value of the FG-slot ID field in each eighth REQ message, and reducing the downlink sub-timeslot for transmitting the first service in the downlink timeslot table according to the timeslot identifier to be reduced, thereby reducing the downlink bandwidth of the first service. After reducing the downlink bandwidth of the first service, node P may set the value of the ACK field in the Nth eighth REQ message shown in FIG13c to 1 and the value of the REQ field to 0, thereby obtaining the eighth ACK message shown in FIG13c, and send an FG-BU to node PE2, wherein the value of the OH field in the FG-BU represents the eighth REQ message shown in FIG13c.
[0381] In S1305 , after receiving the eighth ACK message sent by node P, node PE2 sends one or more eighth CMT messages to node P.
[0382] In this step, node PE2 may send three FG-BUs to node P. The value of the OH field in each FG-BU represents an eighth CMT message shown in FIG13b . Node PE2 may set the value of the ACK field in the eighth ACK message shown in FIG13b to 0 and the value of the CMT field to 1, thereby obtaining the eighth CMT message shown in FIG13b .
[0383] In addition, in other embodiments, when node PE2 receives the eighth ACK message shown in Figure 13c, node PE2 can also set the value of the ACK field in the eighth ACK message shown in Figure 13c to 0 and the value of the CMT field to 1 to obtain the eighth CMT message shown in Figure 13c.
[0384] In S1306 , after receiving the eighth CMT message sent by the node PE2 , the node P sends an eighth REQ message to the node PE1 .
[0385] In this step, the introduction of node P sending the eighth REQ message to node PE1 can refer to the description of node PE2 sending the eighth REQ message to node P in S1303 above, which will not be repeated here.
[0386] In S1307 , after receiving the eighth REQ message sent by the node P, the node PE1 reduces the downlink bandwidth of the first service according to the eighth REQ message, and then sends an eighth ACK message to the node P.
[0387] In this step, the introduction of node PE1 reducing the downlink bandwidth of the first service and sending the eighth ACK message to node P can refer to the description of node P reducing the downlink bandwidth of the first service and sending the eighth ACK message to node P in S1304, which will not be repeated here.
[0388] In S1308 , after receiving the eighth ACK message sent by the node PE1 , the node P sends an eighth CMT message to the node PE1 .
[0389] In this step, the introduction of node P sending the eighth CMT message to node PE1 can refer to the description of node PE2 sending the eighth CMT message to node P in S1305 above, which will not be repeated here.
[0390] The following describes how to increase the downlink bandwidth as an example.
[0391] FIG14a shows a bandwidth adjustment method provided by an embodiment of the present application, which is used to increase the downlink bandwidth of a first service, and includes steps S1401 to S1407.
[0392] In S1401 , the node PE1 receives a bandwidth adjustment request from a user-side node. If it is determined that the bandwidth adjustment request indicates to increase the downlink bandwidth of the first service, step S1402 is executed.
[0393] In this embodiment, as shown in FIG6 , user 11 may send the bandwidth adjustment request to the user-side node through the terminal device. After receiving the bandwidth adjustment request, the user-side node sends it to node PE1 .
[0394] In this step, the bandwidth adjustment request includes the service identifier of the first service and the downlink target bandwidth of the first service. Node PE1 can calculate the downlink bandwidth increment for the first service based on the downlink target bandwidth and the current downlink bandwidth of the first service. Then, based on the downlink bandwidth increment for the first service, it is determined whether the bandwidth adjustment request indicates a decrease in the downlink bandwidth of the first service. For example, if the downlink bandwidth increment is greater than 0, it is determined that the bandwidth adjustment request indicates an increase in the downlink bandwidth of the first service, and S1402 is executed. Furthermore, if the bandwidth adjustment request includes the downlink bandwidth increment for the first service, node PE1 can directly determine whether the bandwidth adjustment request indicates an increase in the downlink bandwidth of the first service.
[0395] In 1402 , the node PE1 increases the downlink bandwidth of the first service according to the bandwidth adjustment request, and then sends a ninth REQ message to the node P. The ninth REQ message is used to instruct to increase the downlink bandwidth of the first service.
[0396] In this step, node PE1 can determine the number of time slots to adjust the downlink bandwidth of the first service based on the downlink bandwidth increment and the bandwidth of the sub-time slot. Then, node PE1 adds the downlink sub-time slot for transmitting the first service to the downlink time slot table based on the number of time slots adjusted for the downlink bandwidth of the first service, thereby increasing the downlink bandwidth of the first service.
[0397] In this step, after increasing the downlink bandwidth of the first service, node PE1 can send an FG-BU to node P. The OH field in the FG-BU represents the ninth REQ message shown in Figure 14b, instructing node P and the sink node PE2 to increase the downlink bandwidth of the first service. Specifically, according to the above description of Figure 7, in the case of increasing the downlink bandwidth of the first service, the value of the MO field in the ninth REQ message shown in Figure 14b is 01, the value of the BA field is 1, the value of the LE field is 1, the value of the FG-client ID field represents the service identifier in the bandwidth adjustment request, the FG-slot ID field is not used (does not represent the time slot identifier), the value of the EN field represents the number of time slots adjusted for the downlink bandwidth of the first service, the value of the REQ field is 1, and the values of the DD field, CMT field, and ACK field are all the default value 0.
[0398] In addition, in other embodiments, node PE1 may send N FG-BUs to node P, with the OH field in each FG-BU representing the ninth REQ message. The Nth ninth REQ message is shown in FIG14c . In the Nth ninth REQ message shown in FIG14c , the MO field has a value of 01, the BA field has a value of 1, the FG-client ID field has a value representing the service identifier in the bandwidth adjustment request, the FG-slot ID field has a value representing the time slot identifier of the downlink sub-time slot for transmitting the first service added by node PE1 to the downlink time slot table, the REQ field has a value of 1, the DD field, the CMT field, and the ACK field all have default values of 0, the LE field has a value of 1, and the EN field has a value representing the number of time slot adjustments, N. Unlike the Nth ninth REQ message, in the 1st to N-1th ninth REQ messages, the LE field has a value of 0, and the FG-slot ID field has a value representing the time slot identifiers of the 1st to N-1th downlink sub-time slots for transmitting the first service added by node PE1 to the downlink time slot table.
[0399] It should be noted that the values of the MFI field, Flag field, and CRC field in each message shown in Figures 14b and 14c can be determined based on the functional description of each field above in this application and according to actual needs. Furthermore, this embodiment of the application does not specifically limit the values of fields other than the OH field in each FG-BU. The values of fields other than the OH field in each FG-BU can be determined based on actual service data.
[0400] In S1403 , after receiving the ninth REQ message sent by the node PE1 , the node P increases the downlink bandwidth of the first service according to the ninth REQ message, and then sends a ninth ACK message to the node PE1 .
[0401] In this step, node P increases the downlink bandwidth of the first service according to the ninth REQ message, including determining to increase the downlink bandwidth of the first service according to the value of the MO field and the value of the BA field in the ninth REQ message, and then determining the time slot adjustment number of the downlink bandwidth of the first service according to the value of the EN field in the ninth REQ message, and adding a downlink sub-time slot for transmitting the first service in the downlink time slot table according to the time slot adjustment number of the downlink bandwidth of the first service to increase the downlink bandwidth of the first service.
[0402] In this step, after increasing the downlink bandwidth of the first service, node P sends an FG-BU to node PE1. The value of the OH field in the FG-BU represents the ninth ACK message shown in Figure 14b. Node P can set the value of the REQ field in the ninth REQ message shown in Figure 14b to 0 and the value of the ACK field to 1 to obtain the ninth ACK message shown in Figure 14b.
[0403] In addition, in other embodiments, when node P receives N ninth REQ messages, node P determines to increase the downlink bandwidth of the first service based on the values of the MO field and the BA field in the N ninth REQ messages, then determines the timeslot identifier to be added based on the value of the FG-slot ID field in the N ninth REQ messages, and adds the downlink sub-timeslot for transmitting the first service to the downlink timeslot table according to the timeslot identifier to be added for the first service, thereby increasing the downlink bandwidth of the first service. After increasing the downlink bandwidth of the first service, node P sends an FG-BU to node P, and the value of the OH field in the FG-BU represents the ninth ACK message shown in Figure 14c. Node P can set the value of the REQ field in the Nth ninth REQ message shown in Figure 14c to 0 and the value of the ACK field to 1, thereby obtaining the ninth ACK message shown in Figure 14c.
[0404] In S1404 , after receiving the ninth ACK message sent by node P, node PE1 sends a ninth CMT message to node P.
[0405] In this step, node PE1 may send three FG-BUs to node P. The value of the OH field in each FG-BU represents the ninth CMT message shown in FIG14b . Node PE1 may set the value of the ACK field in the ninth ACK message shown in FIG14b to 0 and the value of the CMT field to 1, thereby obtaining the ninth CMT message shown in FIG14b .
[0406] In addition, in other embodiments, node PE1 may send an FG-BU to node P, where the value of the OH field in the FG-BU represents the ninth CMT message shown in FIG14c . Node PE1 may set the value of the ACK field in the ninth ACK message shown in FIG14c to 0 and the value of the CMT field to 1, thereby obtaining the ninth CMT message shown in FIG14c .
[0407] In S1405 , after receiving the ninth CMT message sent by PE1 , node P sends a ninth REQ message to node PE2 .
[0408] In this step, the introduction of the node P sending the ninth REQ message to PE2 can refer to the description of the node PE1 sending the ninth REQ message in S1402 above, which will not be repeated here.
[0409] In S1406 , after receiving the ninth REQ message sent by the node P, the node PE2 increases the downlink bandwidth of the first service according to the ninth REQ message, and then sends a ninth ACK message to the node P.
[0410] In this step, the introduction of node PE2 increasing the downlink bandwidth of the first service and sending the ninth ACK message to node P can refer to the description of node P increasing the downlink bandwidth of the first service and sending the ninth ACK message to node PE1 in S1403 above, which is not repeated here.
[0411] In S1407 , after receiving the ninth ACK message sent by the node PE2 , the node P sends a ninth CMT message to the node PE2 .
[0412] In this step, the introduction of node P sending the ninth CMT message can refer to the description of node PE4 sending the ninth CMT message in the aforementioned S1404.
[0413] The following describes how to reduce the uplink bandwidth as an example.
[0414] FIG15 a shows a bandwidth adjustment method provided by an embodiment of the present application, which is used to reduce the uplink bandwidth of a first service, and includes S1501 to S1507.
[0415] In S1501 , the node PE1 receives a bandwidth adjustment request from a user-side node. If it is determined that the bandwidth adjustment request indicates to reduce the uplink bandwidth of the first service, step S1502 is executed.
[0416] In this embodiment, as shown in FIG6 , user 11 may send the bandwidth adjustment request to the user-side node through the terminal device. After receiving the bandwidth adjustment request, the user-side node sends it to node PE1 .
[0417] In this step, the bandwidth adjustment request includes the service identifier of the first service and the uplink target bandwidth of the first service. Node PE1 can calculate the uplink bandwidth increment for the first service based on the uplink target bandwidth and the current uplink bandwidth of the first service. Then, based on the uplink bandwidth increment for the first service, it is determined whether the bandwidth adjustment request indicates a reduction in the uplink bandwidth of the first service. For example, if the uplink bandwidth increment is less than 0, it is determined that the bandwidth adjustment request indicates a reduction in the uplink bandwidth of the first service, and S1502 is executed. Furthermore, if the bandwidth adjustment request includes the uplink bandwidth increment for the first service, node PE1 can directly determine whether the bandwidth adjustment request indicates a reduction in the uplink bandwidth of the first service.
[0418] In 1502 , the node PE1 reduces the uplink bandwidth of the first service according to the bandwidth adjustment request, and then sends a tenth REQ message to the node P. The tenth REQ message is used to instruct the node P and the node PE2 to reduce the uplink bandwidth of the first service.
[0419] In this step, node PE1 can determine the timeslot adjustment number for the uplink bandwidth of the first service based on the uplink bandwidth increment and the bandwidth of the sub-timeslot. Then, node PE1 reduces the uplink sub-timeslot for transmitting the first service in the uplink timeslot table based on the timeslot adjustment number for the uplink bandwidth of the first service, thereby reducing the uplink bandwidth of the first service.
[0420] In this step, after reducing the uplink bandwidth of the first service, node PE1 can send an FG-BU to node P. The OH field in the FG-BU represents the tenth REQ message shown in Figure 15b, instructing node P and sink node PE2 to reduce the uplink bandwidth of the first service. Specifically, according to the aforementioned description of Figure 7, in the case of reducing the uplink bandwidth of the first service, the value of the MO field in the tenth REQ message shown in Figure 15b is 00, the value of the BA field is 0, the value of the LE field is 1, the value of the FG-client ID field represents the service identifier in the bandwidth adjustment request, the FG-slot ID field does not represent the time slot identifier, the value of the EN field represents the number of time slots to adjust the uplink bandwidth of the first service, the value of the REQ field is 1, and the values of the DD field, CMT field, and ACK field are all the default value 0.
[0421] In addition, in other embodiments, node PE1 may send N FG-BUs to node P, with the OH field in each FG-BU representing a tenth REQ message. Figure 15c illustrates the Nth tenth REQ message. In the Nth tenth REQ message shown in Figure 15c, the MO field has a value of 00, the BA field has a value of 0, the FG-client ID field has a value representing the service identifier in the bandwidth adjustment request, the FG-slot ID field has a value representing the timeslot identifier of the Nth uplink sub-timeslot for transmitting the first service, which is reduced from the uplink timeslot table by node PE1, the REQ field has a value of 1, the DD field, the CMT field, and the ACK field all have a default value of 0, the LE field has a value of 1, and the EN field has a value representing the number of timeslot adjustments, N. Similarly, unlike the Nth tenth REQ message, in the 1st to the N-1th tenth REQ messages, the LE field has a value of 0, and the FG-slot ID field has a value representing the timeslot identifiers of the 1st to the N-1th uplink sub-timeslots for transmitting the first service, which are reduced from the uplink timeslot table by node PE1.
[0422] It should be noted that the values of the MFI field, Flag field, and CRC field in each message shown in Figures 15b and 15c can be determined based on the functional description of each field above in this application and according to actual needs. Furthermore, this embodiment of the application does not specifically limit the values of fields other than the OH field in each FG-BU. The values of fields other than the OH field in each FG-BU can be determined based on actual service data.
[0423] In S1503 , after receiving the tenth REQ message sent by the node PE1 , the node P reduces the uplink bandwidth of the first service according to the tenth REQ message, and then sends the tenth ACK message to the node PE1 .
[0424] In this step, node P reduces the uplink bandwidth of the first service according to the tenth REQ message, including: determining to reduce the uplink bandwidth of the first service according to the value of the MO field and the value of the BA field in the tenth REQ message, and then determining the time slot adjustment number of the uplink bandwidth of the first service according to the value of the EN field in the tenth REQ message, and reducing the uplink sub-time slot for transmitting the first service in the uplink time slot table according to the time slot adjustment number of the uplink bandwidth of the first service to reduce the uplink bandwidth of the first service.
[0425] In this step, after reducing the uplink bandwidth of the first service, node P sends an FG-BU to node PE1. The value of the OH field in the FG-BU represents the tenth ACK message shown in Figure 15b. Node P can set the value of the REQ field in the tenth REQ message shown in Figure 15b to 0 and the value of the ACK field to 1 to obtain the tenth ACK message shown in Figure 15b.
[0426] In addition, in other embodiments, when node P receives N tenth REQ messages, node P determines to reduce the uplink bandwidth of the first service based on the values of the MO field and the BA field in the N tenth REQ messages, then determines the timeslot identifier to be reduced based on the value of the FG-slot ID field in the N tenth REQ messages, and reduces the uplink sub-timeslot for transmitting the first service in the uplink timeslot table according to the timeslot identifier to be reduced, thereby reducing the uplink bandwidth of the first service. After reducing the uplink bandwidth of the first service, node P sends an FG-BU to node P, and the value of the OH field in the FG-BU represents the tenth ACK message shown in Figure 15c. Node P can set the value of the REQ field in the N tenth REQ message shown in Figure 15c to 0 and the value of the ACK field to 1, thereby obtaining the tenth ACK message shown in Figure 15c.
[0427] In S1504 , after receiving the tenth ACK message sent by node P, node PE1 sends the tenth CMT message to node P.
[0428] In this step, node PE1 may send an FG-BU to node P. The value of the OH field in the FG-BU represents the tenth CMT message shown in Figure 15b . Node PE1 may set the value of the ACK field in the tenth ACK message shown in Figure 15b to 0 and the value of the CMT field to 1, thereby obtaining the tenth CMT message shown in Figure 15b .
[0429] In addition, in other embodiments, node PE1 may send an FG-BU to node P, where the value of the OH field in the FG-BU represents the tenth CMT message shown in FIG15c . Node PE1 may set the value of the ACK field in the tenth ACK message shown in FIG15c to 0 and the value of the CMT field to 1, thereby obtaining the tenth CMT message shown in FIG15c .
[0430] In S1505 , after receiving the tenth CMT message sent by PE1 , node P sends the tenth REQ message to node PE2 .
[0431] In this step, the introduction of the node P sending the tenth REQ message to PE2 can refer to the description of the node PE1 sending the tenth REQ message in S1502 above, which will not be repeated here.
[0432] In S1506 , after receiving the tenth REQ message sent by the node P, the node PE2 reduces the uplink bandwidth of the first service according to the tenth REQ message, and then sends a tenth ACK message to the node P.
[0433] In this step, the introduction of node PE2 reducing the uplink bandwidth of the first service and sending the tenth ACK message to node P can refer to the description of node P reducing the uplink bandwidth of the first service and sending the tenth ACK message to node PE1 in S1503 above, which is not repeated here.
[0434] In S1507 , after receiving the tenth ACK message sent by the node PE2 , the node P sends the tenth CMT message to the node PE2 .
[0435] In this step, the introduction of node P sending the tenth CMT message can refer to the description of node PE4 sending the tenth CMT message in the aforementioned S1504.
[0436] The following is a detailed introduction using increasing the uplink bandwidth as an example.
[0437] Figure 16a is a flow chart of a bandwidth adjustment method provided by an embodiment of the present application. The method is used to increase the uplink bandwidth of a first service, and the method may include S1601-S1608.
[0438] In S1601 , the node PE1 receives a bandwidth adjustment request from a user-side node. If it is determined that the bandwidth adjustment request indicates to increase the uplink bandwidth of the first service, step S1602 is executed.
[0439] In this embodiment, as shown in Figure 6, user 11 can send the bandwidth adjustment request to the user-side node through the terminal device, and the user-side node sends the bandwidth adjustment request to node PE1 after receiving the bandwidth adjustment request. The bandwidth adjustment request may include the service identifier of the first service and the uplink target bandwidth of the first service.
[0440] In this step, the bandwidth adjustment request includes the service identifier of the first service and the uplink target bandwidth of the first service. Node PE1 can calculate the uplink bandwidth increment for the first service based on the uplink target bandwidth and the current uplink bandwidth of the first service. Then, based on the uplink bandwidth increment for the first service, it is determined whether the bandwidth adjustment request indicates an increase in the uplink bandwidth of the first service. For example, if the uplink bandwidth increment is less than 0, it is determined that the bandwidth adjustment request indicates an increase in the uplink bandwidth of the first service, and S1602 is executed. Furthermore, if the bandwidth adjustment request includes the uplink bandwidth increment for the first service, node PE1 can directly determine whether the bandwidth adjustment request indicates an increase in the uplink bandwidth of the first service.
[0441] In 1602 , the node PE1 sends an eleventh REQ message to the node PE2 via the node P. The eleventh REQ message is used to instruct to increase the uplink bandwidth of the first service.
[0442] In this step, node PE1 can send an FG-BU to node P. The OH field in the FG-BU represents the eleventh REQ message. Specifically, the format of the eleventh REQ message is shown in Figure 16b. In the case of determining to increase the uplink bandwidth of the first service, according to the aforementioned description of Figure 7, the value of the MO field in the eleventh REQ message shown in Figure 16b is 01, and the value of the BA field is 0; the value of the LE field in the eleventh REQ message is 1; the value of the FG-client ID field in the eleventh REQ message represents the service identifier in the bandwidth adjustment request; the FG-slot ID field in the eleventh REQ message does not represent the time slot identifier, and the value of the EN field represents the number of time slots adjusted for the uplink bandwidth of the first service. The value of the REQ field in the eleventh REQ message is 1; the values of the DD field, CMT field, and ACK field in the eleventh REQ message are all default values of 0. The values of the MFI field, Flag field, and CRC field in the eleventh REQ message can be determined according to actual needs based on the functional description of each field above in this application.
[0443] The node PE1 may determine the number of time slots to adjust the uplink bandwidth of the first service according to the uplink bandwidth increment and the bandwidth of the sub-time slot.
[0444] After receiving the eleventh REQ message sent by the node PE1, the node P determines to increase the uplink bandwidth of the first service according to the values of the MO field and the BA field in the eleventh REQ message, and then sends the eleventh REQ message to the node PE2.
[0445] In addition, in other embodiments, node PE1 may send N eleventh REQ messages to node P, with the Nth eleventh REQ message being shown, for example, in FIG16c. In the Nth eleventh REQ message shown in FIG16c, the value of the MO field is 01, the value of the BA field is 0, the value of the LE field is 1, the value of the FG-client ID field represents the service identifier in the bandwidth adjustment request, the value of the FG-slot ID field represents the time slot identifier of the Nth uplink sub-time slot to be added for transmitting the first service, the value of the REQ field is 1, the values of the DD field, the CMT field, and the ACK field are all default values of 0, and the value of the EN field represents the number of time slot adjustments. Unlike the Nth eleventh REQ message, in the 1st to N-1th REQ messages, the value of the LE field is 0, and the values of the FG-slot ID field represent the time slot identifiers of the 1st to N-1th uplink sub-time slots to be added for transmitting the first service, respectively.
[0446] After receiving N eleventh REQ messages from node PE1, node P determines to increase the uplink bandwidth of the first service based on the values of the MO field and the BA field in the eleventh REQ message, and sequentially sends N eleventh REQ messages to node PE2. Specifically, node P may send N FG-BUs to node PE2, with the value of the OH field in each FG-BU representing an eleventh REQ message.
[0447] It should be noted that the values of the MFI field, Flag field, and CRC field in each message shown in Figures 16b and 16c can be determined based on the functional description of each field above in this application and according to actual needs. Furthermore, this embodiment of the application does not specifically limit the values of fields other than the OH field in each FG-BU. The values of fields other than the OH field in each FG-BU can be determined based on actual service data.
[0448] In S1603 , after receiving the eleventh REQ message sent by the node P, the node PE2 increases the uplink bandwidth of the first service according to the eleventh REQ message, and then sends the eleventh REQ message to the node P.
[0449] In this step, node PE2 increases the uplink bandwidth of the first service according to the eleventh REQ message, including determining the increase in the uplink bandwidth of the first service according to the values of the MO field and the BA field in the eleventh REQ message, then determining the timeslot adjustment number for the uplink bandwidth of the first service according to the value of the EN field in the eleventh REQ message, and adding an uplink sub-timeslot for transmitting the first service to the uplink timeslot table according to the timeslot adjustment number for the uplink bandwidth of the first service, thereby increasing the uplink bandwidth of the first service. After increasing the uplink bandwidth of the first service, node PE2 sends an FG-BU to node P. The value of the OH field in the FG-BU represents the eleventh REQ message shown in Figure 16b.
[0450] In addition, in other embodiments, when node PE2 receives N eleventh REQ messages, node PE2 increases the uplink bandwidth of the first service according to the eleventh REQ message, including determining the increase in the uplink bandwidth of the first service according to the value of the MO field and the value of the BA field in each eleventh REQ message, then obtaining the time slot identifier to be added according to the value of the FG-slot ID field in each eleventh REQ message, and adding an uplink sub-time slot for transmitting the first service to the uplink time slot table according to the time slot identifier to be added, so as to increase the uplink bandwidth of the first service. After increasing the uplink bandwidth of the first service, node PE2 can send N FG-BUs to node P, where the value of the OH field in each FG-BU represents an eleventh REQ message as shown in Figure 16c.
[0451] In S1604 , after receiving the eleventh REQ message sent by the node PE2 , the node P increases the uplink bandwidth of the first service according to the eleventh REQ message, and then sends the eleventh ACK message to the node PE2 .
[0452] In this step, node P increases the uplink bandwidth of the first service based on the eleventh REQ message, including determining the increase in the uplink bandwidth of the first service based on the values of the MO field and the BA field in the eleventh REQ message, then determining the number of time slots to adjust the uplink bandwidth of the first service based on the value of the EN field in the eleventh REQ message, and adding an uplink sub-time slot for transmitting the first service to the uplink time slot table according to the number of time slots adjusted for the uplink bandwidth of the first service, thereby increasing the uplink bandwidth of the first service. After increasing the uplink bandwidth of the first service, node P sends an FG-BU to node PE2. The value of the OH field in the FG-BU represents the eleventh ACK message shown in Figure 16b. Node PE2 can set the value of the ACK field in the eleventh REQ message shown in Figure 16b to 1 and the value of the REQ field to 0, thereby obtaining the eleventh ACK message shown in Figure 16b.
[0453] In addition, in other embodiments, when node P receives N eleventh REQ messages, node P increases the uplink bandwidth of the first service according to the eleventh REQ message, including: determining to increase the uplink bandwidth of the first service according to the value of the MO field and the value of the BA field in each eleventh REQ message, then obtaining the timeslot identifier to be added according to the value of the FG-slot ID field in each eleventh REQ message, and adding an uplink sub-timeslot for transmitting the first service to the uplink timeslot table according to the timeslot identifier to be added, thereby increasing the uplink bandwidth of the first service. After increasing the uplink bandwidth of the first service, node P may set the value of the ACK field in the Nth eleventh REQ message shown in FIG16c to 1 and the value of the REQ field to 0, thereby obtaining the eleventh ACK message shown in FIG16c, and send an FG-BU to node PE2, wherein the value of the OH field in the FG-BU represents the eleventh REQ message shown in FIG16c.
[0454] In S1605 , after receiving the eleventh ACK message sent by node P, node PE2 sends one or more eleventh CMT messages to node P.
[0455] In this step, node PE2 sends three FG-BUs to node PE2. The value of the OH field in each FG-BU represents an eleventh CMT message, as shown in Figure 16b. The format of the eleventh CMT messages in the three FG-BUs is the same. Node PE2 can set the value of the ACK field in the eleventh ACK message, as shown in Figure 16b, to 0 and the value of the CMT field to 1, resulting in the eleventh CMT message shown in Figure 16b.
[0456] In addition, in other embodiments, when node PE2 receives the eleventh ACK message shown in Figure 16c, node PE2 can also set the value of the ACK field in the eleventh ACK message shown in Figure 16c to 0 and the value of the CMT field to 1 to obtain the eleventh CMT message shown in Figure 16c; set the value of the ACK field in the eleventh ACK message shown in Figure 16c to 0 and the value of the CMT field to 1 to obtain the eleventh CMT message shown in Figure 16c.
[0457] In S1606 , after receiving the eleventh CMT message sent by the node PE2 , the node P sends the eleventh REQ message to the node PE1 .
[0458] In this step, the introduction of the node P sending the eleventh REQ message to the node PE1 can refer to the description of the node PE2 sending the eleventh REQ message to the node P in S1603 above, which will not be repeated here.
[0459] In S1607 , after receiving the eleventh REQ message sent by the node P, the node PE1 increases the uplink bandwidth of the first service according to the eleventh REQ message, and then sends the eleventh ACK message to the node P.
[0460] In this step, the introduction of node PE1 increasing the uplink bandwidth of the first service and sending the eleventh ACK message to node P can refer to the description of node P increasing the uplink bandwidth of the first service and sending the eleventh ACK message to node P in S1604 above, which will not be repeated here.
[0461] In S1608 , after receiving the eleventh ACK message sent by the node PE1 , the node P sends the eleventh CMT message to the node PE1 .
[0462] In this step, the introduction of node P sending the eleventh CMT message to node PE1 can refer to the description of node PE2 sending the eleventh CMT message to node P in S1605 above, which will not be repeated here.
[0463] In the method embodiments shown in Figures 13a, 14a, 15a, and 16a, the source node in a dedicated slice line receives a bandwidth adjustment request from the user side indicating a unidirectional bandwidth adjustment. It then uses the mode field and bandwidth adjustment field in the FG-BU to instruct the intermediate node and sink node to adjust the uplink or downlink bandwidth. Furthermore, the source node notifies the sink node to reduce the downlink bandwidth or increase the uplink bandwidth. This reduces the number of times the network management system must participate in bandwidth adjustments, reduces the load on the network management system, and improves the reliability of bandwidth adjustments.
[0464] Based on the aforementioned method embodiments, embodiments of the present application further provide a bandwidth adjustment device. This bandwidth adjustment device can be applied to a source node, a sink node, or an intermediate node to implement the aforementioned methods shown in Figures 8a, 9a, 10a, 11a, 12a, 13a, 14a, 15a, and 16a.
[0465] 17 is a schematic diagram of the structure of a bandwidth adjustment device 1700 provided in an embodiment of the present application. The bandwidth adjustment device 1700 may include a receiving module 1701 , an adjustment module 1702 , and a sending module 1703 .
[0466] When bandwidth adjustment apparatus 1700 is applied to a source node, receiving module 1701 is configured to receive a bandwidth adjustment request instructing adjustment of the bandwidth of a first service. Adjustment module 1702 is configured to determine the value of an overhead field in the first service data based on the bandwidth adjustment request. The overhead field includes a mode field and a bandwidth adjustment field. The value of the mode field indicates one of multiple bandwidth adjustment modes, including unidirectional bandwidth adjustment and bidirectional bandwidth adjustment. The value of the bandwidth adjustment field indicates an increase or decrease in bandwidth. Transmission module 1703 is configured to transmit the first service data to a destination node via an intermediate node. Upon receiving the first service data, the destination node is configured to adjust the bandwidth of the first service based on the value of the overhead field.
[0467] When bandwidth adjustment apparatus 1700 is applied to an intermediate node, receiving module 1701 is configured to receive first service data sent by a source node. Transmitting module 1703 is configured to transmit the first service data to a sink node. Adjustment module 1703 is configured to adjust the bandwidth of the first service based on the value of an overhead field in the first service data and / or second service data sent by the sink node.
[0468] When the bandwidth adjustment device 1700 is applied to an intermediate node, the receiving module 1701 is used to receive the first service data sent by the intermediate node. The adjustment module 1703 is used to adjust the bandwidth of the first service according to the value of the overhead field in the first service data. When adjusting the bandwidth of the first service includes increasing the uplink bandwidth of the first service and / or reducing the downlink bandwidth of the first service, after adjusting the bandwidth of the first service according to the value of the overhead field in the first service data, the adjustment module 1703 is further used to: determine the second service data, the value of the mode field in the second service data is different from the value of the mode field in the first service data. The sending module 1702 is used to send the second service data to the source end node via the intermediate node, wherein the intermediate node and the source end node are used to increase the uplink bandwidth of the first service and / or reduce the downlink bandwidth of the first service according to the value of the overhead field in the second service data.
[0469] It should be noted that the bandwidth adjustment device 1700 provided in the embodiment shown in FIG17 is merely an example of the division of the aforementioned functional modules when performing the bandwidth adjustment method. In actual applications, the aforementioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to perform all or part of the functions described above. Furthermore, the bandwidth adjustment device provided in the above embodiment and the aforementioned method embodiments share the same concept. The specific implementation process is detailed in the method embodiments and will not be further described here.
[0470] FIG18 is a schematic diagram of the hardware structure of a network device 1800 provided in an embodiment of the present application.
[0471] The network device 1800 may be the above-mentioned source node, intermediate node, or sink node. Referring to Figure 18 , the network device 1800 includes a processor 1801, a memory 1802, a communication interface 1803, and a bus 1804. The processor 1801, the memory 1802, and the communication interface 1803 are connected to each other via the bus 1804. The processor 1801, the memory 1802, and the communication interface 1803 may also be connected using other connection methods besides the bus 1804.
[0472] Among them, the memory 1802 can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), flash memory, optical storage, hard disk, etc.
[0473] Processor 1801 may be a general-purpose processor that reads and executes content stored in a memory (e.g., memory 1802) to perform specific steps and / or operations. For example, the general-purpose processor may be a central processing unit (CPU). Processor 1801 may include at least one circuit to implement the steps in each of the aforementioned methods.
[0474] Communication interface 1803 includes input / output (I / O) interfaces, physical interfaces, and logical interfaces, which are used to interconnect components within network device 1800, as well as interfaces for interconnecting network device 1800 with other devices (e.g., other network devices or user equipment). The physical interfaces may be Ethernet interfaces, fiber optic interfaces, ATM interfaces, etc.
[0475] The bus 1804 may be any type of communication bus for interconnecting the processor 1801 , the memory 1802 , and the communication interface 1803 , such as a system bus.
[0476] The above-mentioned devices can be provided on separate chips, or at least partially or entirely on the same chip. Whether to provide each device independently on different chips or to integrate them on one or more chips often depends on the product design requirements. The embodiments of this application do not limit the specific implementation of the above-mentioned devices.
[0477] The network device 1800 shown in FIG18 is merely exemplary. During implementation, the network device 1800 may further include other components, which are not listed one by one herein.
[0478] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The 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 the present invention 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 computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive (SSD)).
[0479] It is understood that the various numerical numbers involved in the embodiments of the present application are only for the convenience of description and are not intended to limit the scope of the embodiments of the present application. It should be understood that in the embodiments of the present application, the order of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0480] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of this application in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of this application. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of this application should be included in the scope of protection of this application.
Claims
1. A bandwidth adjustment method, characterized in that: Applied to a source node, the method comprises: receiving a bandwidth adjustment request, where the bandwidth adjustment request is used to instruct adjustment of a bandwidth of a first service; determining, according to the bandwidth adjustment request, a value of an overhead field in the first service data, the overhead field comprising a mode field and a bandwidth adjustment field, the value of the mode field representing one of a plurality of bandwidth adjustment modes, the plurality of bandwidth adjustment modes comprising unidirectional bandwidth adjustment and bidirectional bandwidth adjustment, the value of the bandwidth adjustment field representing increasing bandwidth or decreasing bandwidth; The first service data is sent to a destination node via an intermediate node; and the destination node is configured to adjust a bandwidth of the first service according to a value of the overhead field after receiving the first service data.
2. The method according to claim 1, characterized in that The unidirectional bandwidth adjustment includes reducing the uplink bandwidth, increasing the uplink bandwidth, reducing the downlink bandwidth, and increasing the downlink bandwidth; The bidirectional bandwidth adjustment includes reducing the uplink bandwidth and reducing the downlink bandwidth, increasing the uplink bandwidth and increasing the downlink bandwidth, reducing the uplink bandwidth and increasing the downlink bandwidth, and increasing the uplink bandwidth and reducing the downlink bandwidth.
3. The method according to claim 1 or 2, characterized in that: When adjusting the bandwidth of the first service includes reducing the uplink bandwidth of the first service and / or increasing the downlink bandwidth of the first service, before determining the value of the overhead field in the first service data according to the bandwidth adjustment request, the method further includes: The uplink bandwidth of the first service is reduced and / or the downlink bandwidth of the first service is increased according to the bandwidth adjustment request.
4. The method according to claim 1 or 2, characterized in that: When adjusting the bandwidth of the first service includes increasing the uplink bandwidth of the first service and / or reducing the downlink bandwidth of the first service, the method further includes: receiving second service data sent by the intermediate node, wherein a value of a mode field in the second service data is different from a value of a mode field in the first service data, and the destination node is configured to send the second service data to the intermediate node after adjusting a bandwidth of the first service; The uplink bandwidth of the first service is increased and / or the downlink bandwidth of the first service is decreased according to the value of the overhead field in the second service data.
5. The method according to any one of claims 1 to 4, characterized in that: The overhead field also includes a timeslot adjustment quantity field for uplink bandwidth and / or a timeslot adjustment quantity field for downlink bandwidth.
6. The method according to any one of claims 1 to 5, characterized in that: The receiving a bandwidth adjustment request comprises: The bandwidth adjustment request is received from a user-side node or from a network management system.
7. A bandwidth adjustment method, characterized in that: Applied to an intermediate node, the method includes Receive first service data sent by a source node, where a value of an overhead field in the first service data is determined by the source node according to a received bandwidth adjustment request, where the bandwidth adjustment request is used to indicate adjustment of the bandwidth of the first service; the overhead field includes a service identifier of the first service, the mode field, the bandwidth adjustment field, and the bandwidth increment field; The first service data is sent to a destination node, and the destination node is configured to adjust a bandwidth of the first service according to a value of the overhead field after receiving the first service data.
8. The method according to claim 7, characterized in that The unidirectional bandwidth adjustment includes reducing the uplink bandwidth, increasing the uplink bandwidth, reducing the downlink bandwidth, or increasing the downlink bandwidth; The bidirectional bandwidth adjustment includes reducing the uplink bandwidth and reducing the downlink bandwidth, increasing the uplink bandwidth and increasing the downlink bandwidth, reducing the uplink bandwidth and increasing the downlink bandwidth, and increasing the uplink bandwidth and reducing the downlink bandwidth.
9. The method according to claim 7 or 8, characterized in that: When adjusting the bandwidth of the first service includes reducing the uplink bandwidth of the first service and / or increasing the downlink bandwidth of the first service, before sending the first service data to the sink node, the method further includes: The uplink bandwidth of the first service is reduced and / or the downlink bandwidth of the first service is increased according to the value of the overhead field in the first service data.
10. The method according to claim 7 or 8, characterized in that: When adjusting the bandwidth of the first service includes increasing the uplink bandwidth of the first service and / or reducing the downlink bandwidth of the first service, the method further includes: receiving second service data sent by the sink node, the sink node being used to send the second service data after adjusting the bandwidth of the first service, wherein a value of a mode field in the second service data is different from a value of a mode field in the first service data; The uplink bandwidth of the first service is increased and / or the downlink bandwidth of the first service is decreased according to the value of the overhead field in the second service data.
11. The method according to any one of claims 7 to 10, characterized in that: The overhead field also includes a timeslot adjustment quantity field for uplink bandwidth and / or a timeslot adjustment quantity field for downlink bandwidth.
12. The method according to any one of claims 7 to 11, characterized in that: The source node is used to receive the bandwidth adjustment request from a user-side node or receive the bandwidth adjustment request from a network management system.
13. A bandwidth adjustment method, characterized in that: Applied to a sink node, the method comprises: Receive first service data sent by an intermediate node, where a value of an overhead field in the first service data is determined by a source node according to a received bandwidth adjustment request, where the bandwidth adjustment request is used to indicate adjustment of the bandwidth of the first service; the overhead field includes a service identifier of the first service, the mode field, the bandwidth adjustment field, and the bandwidth increment field; The bandwidth of the first service is adjusted according to the value of the overhead field in the first service data.
14. The method according to claim 13, characterized in that The unidirectional bandwidth adjustment includes reducing the uplink bandwidth, increasing the uplink bandwidth, reducing the downlink bandwidth, or increasing the downlink bandwidth; The bidirectional bandwidth adjustment includes reducing the uplink bandwidth and reducing the downlink bandwidth, increasing the uplink bandwidth and increasing the downlink bandwidth, reducing the uplink bandwidth and increasing the downlink bandwidth, and increasing the uplink bandwidth and reducing the downlink bandwidth.
15. The method according to claim 13 or 14, characterized in that When adjusting the bandwidth of the first service includes increasing the uplink bandwidth of the first service and / or reducing the downlink bandwidth of the first service, after adjusting the bandwidth of the first service according to the value of the overhead field in the first service data, the method further includes: Determine second business data, wherein a value of a mode field in the second business data is different from a value of a mode field in the first business data; The second service data is sent to the source node via the intermediate node, and the intermediate node and the source node are used to increase the uplink bandwidth of the first service and / or reduce the downlink bandwidth of the first service according to the value of the overhead field in the second service data.
16. The method according to any one of claims 13 to 15, characterized in that: The overhead field also includes a timeslot adjustment quantity field for uplink bandwidth and / or a timeslot adjustment quantity field for downlink bandwidth.
17. The method according to any one of claims 13 to 16, characterized in that: The source node is used to receive the bandwidth adjustment request from a user-side node or receive the bandwidth adjustment request from a network management system.
18. A network device, characterized in that: The network device comprises: a processor and a memory, wherein the processor is used to execute a computer program stored in the memory to implement the method described in any one of claims 1 to 6, or the method described in any one of claims 7 to 12, or the method described in any one of claims 13 to 17.
19. A computer-readable storage medium, characterized in that: The method comprises instructions, which, when executed on a computer, enable the computer to implement any one of the methods of claims 1 to 6, or any one of the methods of claims 7 to 12, or any one of the methods of claims 13 to 17.
20. A computer program product, characterized in that The computer program product comprises program codes, and when a computer runs the computer program product, the computer implements the method described in any one of claims 1 to 6, or implements the method described in any one of claims 7 to 12, or implements the method described in any one of claims 13 to 17.
Citation Information
Patent Citations
Bandwidth adjusting method and device
CN113098651A
Channel bandwidth adjustment method, device and system, electronic equipment and readable medium
CN114285752A
Bandwidth adjustment method and device, storage medium and electronic device
CN115412782A
Bandwidth adjusting method and system for OSU service
CN116192646A
Bandwidth adjustment method, apparatus and system, electronic device, and readable storage medium
WO2022078208A1
