Congestion handling methods, apparatus, equipment and storage media

Abstract

This application provides a congestion handling method, apparatus, device, and storage medium. The method is applied to a first node and includes: receiving congestion information, wherein the congestion information is used by the first node to perform congestion handling; and performing congestion handling based on the congestion information.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a congestion handling method, apparatus, device, and storage medium. Background Technology

[0002] Release 17 supports inter-donor migration of IAB nodes and enhanced multipath transmission for IAB nodes. The complex topology provides more data transmission paths, but also increases the likelihood of data congestion. Summary of the Invention

[0003] The congestion handling method, apparatus, device, and storage medium provided in this application are intended to solve the problem of data transmission after path congestion.

[0004] In a first aspect, embodiments of this application provide a congestion handling method, the method being applied to a first node, comprising:

[0005] Receive congestion information, wherein the congestion information is used by the first node to perform congestion processing;

[0006] Congestion processing is performed based on the congestion information.

[0007] Secondly, embodiments of this application provide a congestion handling method, the method being applied to a second node, comprising:

[0008] Determine congestion information, wherein the congestion information includes downlink congestion information or uplink congestion information;

[0009] The congestion information is sent to the first node via the F1AP interface.

[0010] Thirdly, embodiments of this application provide a congestion handling method, the method being applied to a third node, including:

[0011] Determine congestion information, wherein the congestion information includes downlink congested data radio bearer (DRB) information;

[0012] The congestion information is sent to the first node via the E1AP interface.

[0013] Fourthly, embodiments of this application provide a congestion handling apparatus, the apparatus being configured at a first node, comprising:

[0014] The receiving module is configured to receive congestion information, wherein the congestion information is used by the first node for congestion processing;

[0015] The processing module is configured to perform congestion processing based on the congestion information.

[0016] Fifthly, embodiments of this application provide a congestion handling apparatus, the apparatus being configured at a second node, comprising:

[0017] The first determining module is configured to determine congestion information, wherein the congestion information includes downlink congestion information or uplink congestion information;

[0018] The first sending module is configured to send the congestion information to the first node via the F1AP interface.

[0019] Sixthly, embodiments of this application provide a congestion handling apparatus, the apparatus being configured at a third node, comprising:

[0020] The second determining module is configured to determine congestion information, wherein the congestion information includes downlink congested data radio bearer (DRB) information;

[0021] The second sending module is configured to send the congestion information to the first node via the E1AP interface.

[0022] In a seventh aspect, embodiments of this application provide an apparatus, comprising:

[0023] One or more processors;

[0024] Memory, used to store one or more programs;

[0025] When the one or more programs are executed by the one or more processors, the one or more processors perform the method as provided in any of the embodiments of this application.

[0026] Eighthly, embodiments of this application provide a storage medium storing a computer program that, when executed by a processor, implements the method described in any of the embodiments of this application.

[0027] Further details regarding the above embodiments and other aspects of this application, as well as their implementations, are provided in the accompanying drawings, detailed description, and claims. Attached Figure Description

[0028] Figure 1 This is a flowchart of a congestion handling method provided in an embodiment of this application;

[0029] Figure 2 This is a flowchart of a congestion handling method provided in an embodiment of this application;

[0030] Figure 3 This is a flowchart of a congestion handling method provided in an embodiment of this application;

[0031] Figure 4This is a schematic diagram of downlink end-to-end flow control performed by the control plane provided in an embodiment of this application;

[0032] Figure 5 This is a schematic diagram of downlink end-to-end flow control performed by the control plane provided in an embodiment of this application;

[0033] Figure 6 This is a schematic diagram of downlink end-to-end flow control performed by the control plane provided in an embodiment of this application;

[0034] Figure 7 This is a schematic diagram of uplink end-to-end flow control performed by the control plane provided in an embodiment of this application;

[0035] Figure 8 This is a schematic diagram of the structure of a congestion processing device provided in an embodiment of this application;

[0036] Figure 9 This is a schematic diagram of the structure of a congestion processing device provided in an embodiment of this application;

[0037] Figure 10 This is a schematic diagram of the structure of a congestion processing device provided in an embodiment of this application;

[0038] Figure 11 This is a schematic diagram of the structure of a device provided in an embodiment of this application. Detailed Implementation

[0039] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in detail below with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be arbitrarily combined with each other.

[0040] The steps illustrated in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases the steps shown or described may be performed in a different order than that presented here.

[0041] In one embodiment, this embodiment provides a congestion handling method, which is mainly applied to a first node, such as... Figure 1 As shown, the congestion handling method provided in this embodiment mainly includes steps S11 and S12.

[0042] S11. Receive congestion information, wherein the congestion information is used by the first node to perform congestion processing;

[0043] S12. Perform congestion processing based on the congestion information.

[0044] In this embodiment, the first node is CU-CP.

[0045] In one exemplary implementation, the congestion information includes one or more of the following:

[0046] Downlink congestion information, uplink congestion information, downlink congestion data radio bearer (DRB) information.

[0047] In one exemplary implementation, the downlink congestion information includes one or more of the following:

[0048] Radio backhaul (RLC) channel identifier for congested links;

[0049] The route identifier for the congested link;

[0050] IAB child node identifier of the congested link;

[0051] Downlink data transmission efficiency of congested links.

[0052] In one exemplary implementation, downlink data transmission efficiency includes one or more of the following:

[0053] The ratio of actual downlink cache to supported downlink cache;

[0054] The ratio of the data rate of the outgoing radio backhaul RLC channel to the data rate of the incoming radio backhaul RLC channel.

[0055] In one exemplary implementation, the uplink congestion information includes one or more of the following:

[0056] Radio backhaul (RLC) channel identifier for congested links;

[0057] Link identifier of the congested link;

[0058] IAB child node identifier of the congested link;

[0059] Buffer Status Report (BSR) reported by child nodes of congested links;

[0060] Uplink data transmission efficiency of congested links.

[0061] In one exemplary embodiment, the radio backhaul RLC channel identifier includes an ingress radio backhaul RLC channel identifier and / or an egress radio backhaul RLC channel identifier.

[0062] In one exemplary implementation, the IAB sub-node identifier includes a Wireless Backhaul Adaptor Protocol (BAP) address and / or an IP address.

[0063] In one exemplary implementation, the uplink data transmission efficiency includes the ratio of the actual uplink cache to the uplink cache that can be supported.

[0064] In one exemplary implementation, the downlink congested data radio bearer (DRB) information includes one or more of the following:

[0065] DRB indicator for congestion;

[0066] The identifier of the UE to which the congestion DRB belongs;

[0067] Congested GPRS tunneling protocol tunnel endpoint identifier;

[0068] The amount of data required to congest the DRB;

[0069] The rate at which the DRB is congested.

[0070] In one exemplary implementation, the method of receiving link congestion information includes one of the following:

[0071] Receive downlink or uplink congestion information sent by the second node through the F1AP interface;

[0072] Receive downlink congestion data radio bearer DRB information sent by the third node through the E1AP interface.

[0073] The second node refers to the IAB node. The second node can be a node where the link between it and its child nodes is congested, or a node where downlink transmission on a BH RLC channel between it and its child nodes is congested.

[0074] The three nodes refer to the IAB nodes that are themselves congested in the DRB.

[0075] In one embodiment, this embodiment provides a congestion handling method, which is mainly applied to a second node, such as... Figure 2 As shown, the congestion handling method provided in this embodiment mainly includes steps S21 and S22.

[0076] S21. Determine congestion information, wherein the congestion information includes downlink congestion information or uplink congestion information;

[0077] S22. The congestion information is sent to the first node via the F1AP interface.

[0078] In one exemplary implementation, the congestion information includes one or more of the following:

[0079] Downlink congestion information, uplink congestion information, downlink congestion data radio bearer (DRB) information.

[0080] In one exemplary implementation, the downlink congestion information includes one or more of the following:

[0081] Radio backhaul (RLC) channel identifier for congested links;

[0082] The route identifier for the congested link;

[0083] IAB child node identifier of the congested link;

[0084] Downlink data transmission efficiency of congested links.

[0085] In one exemplary implementation, downlink data transmission efficiency includes one or more of the following:

[0086] The ratio of actual downlink cache to supported downlink cache;

[0087] The ratio of the data rate of the outgoing radio backhaul RLC channel to the data rate of the incoming radio backhaul RLC channel.

[0088] In one exemplary implementation, the uplink congestion information includes one or more of the following:

[0089] Radio backhaul (RLC) channel identifier for congested links;

[0090] Link identifier of the congested link;

[0091] IAB child node identifier of the congested link;

[0092] Buffer Status Report (BSR) reported by child nodes of congested links;

[0093] Uplink data transmission efficiency of congested links.

[0094] In one exemplary embodiment, the radio backhaul RLC channel identifier includes an ingress radio backhaul RLC channel identifier and / or an egress radio backhaul RLC channel identifier.

[0095] In one exemplary implementation, the IAB sub-node identifier includes a Wireless Backhaul Adaptor Protocol (BAP) address and / or an IP address.

[0096] In one exemplary implementation, the uplink data transmission efficiency includes the ratio of the actual uplink cache to the uplink cache that can be supported.

[0097] In one embodiment, this embodiment provides a congestion handling method, which is mainly applied to a third node, such as... Figure 3 As shown, the congestion handling method provided in this embodiment mainly includes steps S31 and S32.

[0098] S31. Determine congestion information, wherein the congestion information includes downlink congested data radio bearer (DRB) information;

[0099] S32. The congestion information is sent to the first node via the E1AP interface.

[0100] In one exemplary implementation, the downlink congested data radio bearer (DRB) information includes one or more of the following:

[0101] DRB indicator for congestion;

[0102] The identifier of the UE to which the congestion DRB belongs;

[0103] Congested GPRS tunneling protocol tunnel endpoint identifier;

[0104] The amount of data required to congest the DRB;

[0105] The rate at which the DRB is congested.

[0106] The method by which the first node handles congestion based on congestion information, the information interaction between the second node and the first node, and the information interaction between the third node and the first node can be specifically described in the following embodiments, and will not be repeated in this embodiment.

[0107] In one embodiment, a control plane method for downlink end-to-end congestion handling is provided. Figure 4 This example illustrates the situation using one of the links as an example.

[0108] Step 1: Downlink data arrives at CU-UP from the core network. CU-UP then transmits the downlink data to IAB3 via each IAB node. IAB3 monitors the downlink data transmission to its child nodes. It detects congestion on the downlink between IAB3 and its child node IAB4; smooth downlink transmission between IAB3 and its child node IAB5; and smooth downlink transmission between IAB3 and its child node IAB6.

[0109] Step 2: IAB3 will aggregate the downlink congestion information detected by it and its child nodes, and then report it to CU-CP via F1AP message.

[0110] The downlink congestion information includes one or more of the following:

[0111] Link identifier of the congested link; for example: route ID.

[0112] IAB child node identifier of the congested link;

[0113] Downlink data transmission efficiency of congested links.

[0114] Downlink data transmission efficiency includes one or more of the following:

[0115] The ratio of actual downlink cache to supported downlink cache;

[0116] The ratio of the data rate of the outgoing radio backhaul RLC channel to the data rate of the incoming radio backhaul RLC channel.

[0117] The IAB sub-node identifier includes the Wireless Backhaul Adaptor Protocol (BAP) address and / or IP address.

[0118] Step 3: CU-CP receives downlink transmission congestion information sent by IAB3, and identifies the downlink congestion link between IAB3 and IAB4 from this information. At the same time, CU-CP also learns that the downlink transmission between IAB3 and its child node IAB5, and between IAB3 and its child node IAB6, is unimpeded.

[0119] Step 4: CU-CP, based on the overall network topology, selects to remap the downlink data transmitted on the original path (IAB3->IAB4) link at IAB3 to the path (IAB3->IAB5) link for transmission.

[0120] Specifically, CU-CP sends a new [BAP MAPPING CONFIGURATION] F1 message to IAB-Donor DU to reconfigure the routing ID of the downlink data originally to be transmitted to the path (IAB3->IAB4) link. That is, it modifies the correspondence between the IP header and the BAP routing ID so that the data is ultimately transmitted through the path (IAB3->IAB5) link.

[0121] In addition, CU-CP sends a new [BAP MAPPING CONFIGURATION] F1 message to IAB3 to reconfigure the mapping table at IAB3, so that the outgoing BH RLC channel corresponding to the ingress BH RLC channel of the downlink data transmitted on the original path (IAB3->IAB4) link at IAB3 is the BH RLC channel on the path (IAB3->IAB5).

[0122] Step 5: The IAB-Donor DU receives the new routing configuration information, updates it, and simultaneously sends an acknowledgment message back to the CU-CP. Then, it transmits the IP data packet to the new routing path.

[0123] Step 6: IAB3 receives and updates the new traffic mapping configuration information and simultaneously sends an acknowledgment message back to CU-CP. Then, it transmits the newly received downlink data from the original path (IAB3->IAB4) link to the newly configured egress BH RLC channel on the new path (IAB3->IAB5) link.

[0124] In one embodiment, a control plane method for downlink end-to-end congestion handling is provided. Figure 5 This example will be used to illustrate the concept. In this embodiment, congestion in one of the BH RLC channels will be used as an example.

[0125] Step 1: Downlink data arrives at CU-UP from the core network. CU-UP transmits the downlink data to IAB3 via various IAB nodes, and IAB3 then transmits the downlink data to UE3 via IAB4. The IAB detects the downlink data transmission status via the BH RLC channel to IAB4. It detects congestion in the downlink transmission of BH RLC channel 2 between IAB3 and its child node IAB4.

[0126] Step 2: IAB3 will summarize the downlink transmission congestion information detected in BH RLC channel 2 and then report it to CU-CP via F1AP message.

[0127] The downlink congestion information includes one or more of the following:

[0128] Radio backhaul (RLC) channel identifier for congested links;

[0129] The route identifier for the congested link; for example: route ID.

[0130] IAB child node identifier of the congested link;

[0131] Downlink data transmission efficiency of congested links.

[0132] Downlink data transmission efficiency includes one or more of the following:

[0133] The ratio of actual downlink cache to supported downlink cache;

[0134] The ratio of the data rate of the outgoing radio backhaul RLC channel to the data rate of the incoming radio backhaul RLC channel.

[0135] The wireless backhaul RLC channel identifier includes the ingress wireless backhaul RLC channel identifier and / or the egress wireless backhaul RLC channel identifier.

[0136] The IAB sub-node identifier includes the Wireless Backhaul Adaptor Protocol (BAP) address and / or IP address.

[0137] Step 3: CU-CP receives downlink transmission congestion link information sent by IAB3 and identifies the outgoing BH RLC channel 2 with downlink congestion from the congestion link information.

[0138] Step 4: CU-CP, considering the overall network topology, selects to remap the downlink data originally transmitted from IAB3 to the path exit BH RLC channel 2 to either exit BH RLC channel 1 or exit BH RLC channel 3 for transmission. Specifically, CU-CP sends a new [BAP MAPPING CONFIGURATION] F1 message to IAB3, reconfiguring the mapping table at IAB3 so that the exit BH RLC channel corresponding to the ingress BH RLC channel of the downlink data originally transmitted from IAB3 to path exit BH RLC channel 2 is either exit BH RLC channel 1 or exit BH RLC channel 3.

[0139] Step 5: IAB3 receives the new traffic mapping configuration information, updates it, and sends an acknowledgment message back to CU-CP. Then, it transmits the newly received downlink data originally transmitted to path exit BH RLC channel 2 to the new path exit BH RLC channel 1 or exit BH RLC channel 3.

[0140] In one embodiment, a control plane method for downlink end-to-end congestion handling is provided. Figure 6 Let's take an example to illustrate.

[0141] Step 1: Downlink data arrives at CU-UP from the core network. CU-UP transmits the downlink data to IAB3 through each IAB node. IAB3 then sends the downlink data to the UE.

[0142] Step 2: IAB3 sends DDDS information back to CU-UP. DDDS contains the amount of data required for the UE's DRB, the required data rate, and the SN information of data packets successfully transmitted over the air interface.

[0143] Step 3: CU-UP receives DDDS from IAB3, determines which DRBs of UE2 accessing IAB3 are congested, and summarizes them into downlink transmission congestion indication information.

[0144] The downlink congestion data radio bearer (DRBs) information includes one or more of the following:

[0145] DRB indicator for congestion;

[0146] The identifier of the UE to which the congested DRB belongs;

[0147] Congested GPRS tunneling protocol tunnel endpoint identifier;

[0148] The amount of data required to congest the DRB;

[0149] The rate at which the DRB is congested.

[0150] Step 4: CU-UP sends downlink transmission congestion indication information to CU-CP via E1AP message.

[0151] Step 5: The CU-CP receives the downlink transmission congestion indication information sent by the CU-UP and replies with an acknowledgment response. The CU-CP, considering the overall network topology, replans new downlink transmission paths for the congested DRB within the IAB network. This can be done by modifying the QoS flow to DRB mapping at the CU-UP, transmitting data from the originally congested downlink DRB through other DRBs. Alternatively, the routing ID of the IP packets at the Donor DU can be modified, transmitting the originally congested downlink packets through alternative routing paths. After replanning the paths, the CU-CP sends the updated QoS flow to DRB mapping table to the CU-UP via E1AP, or sends the updated routing table to the IAB Donor DU node via F1AP.

[0152] Step 6: The CU-UP receives and updates the new QoS flow to DRB mapping table and simultaneously sends an acknowledgment message back to the CU-CP. Then, the CU-UP transmits the QoS flow data packets to the new DRB. Alternatively, the IAB-Donor DU receives and updates the new routing configuration information and simultaneously sends an acknowledgment message back to the CU-CP. Then, the IAB-Donor DU transmits the IP data packets to the new routing path.

[0153] In one embodiment, a control plane method for uplink end-to-end congestion handling is provided. Figure 7 Let's take an example to illustrate.

[0154] The first step involves uplink data traveling from UE1 to access node IAB1, then through IAB2 / IAB3 to IAB4->DonorDU, and finally to the CU-UP core network for further transmission. IAB4 assesses the uplink data volume requests for BSR from its child nodes and allocates uplink resources to each child IAB node based on available uplink resources. If the uplink data volume at IAB2 is large, and IAB4 lacks sufficient uplink resources for allocation, link congestion will occur between uplink IAB2 and IAB4.

[0155] Step 2: IAB4 detects congestion on the uplink link between IAB2 and IAB4. IAB4 summarizes the uplink congestion information and then reports it to CU-CP via an F1AP message.

[0156] The uplink congestion information includes one or more of the following:

[0157] Radio backhaul (RLC) channel identifier for congested links;

[0158] The link identifier of the congested link; for example: route ID;

[0159] IAB child node identifier of the congested link;

[0160] Buffer Status Report (BSR) reported by child nodes of congested links;

[0161] Uplink data transmission efficiency of congested links.

[0162] The wireless backhaul RLC channel identifier includes the ingress wireless backhaul RLC channel identifier and / or the egress wireless backhaul RLC channel identifier.

[0163] The IAB sub-node identifier includes the Wireless Backhaul Adaptor Protocol (BAP) address and / or IP address.

[0164] The uplink data transmission efficiency includes the ratio of the actual uplink cache to the uplink cache that can be supported.

[0165] Step 3: CU-CP receives uplink congestion information from IAB4 and identifies a congested uplink link between IAB4 and IAB2. Simultaneously, CU-CP also learns that the uplink transmission between IAB4 and its child node IAB3 is unimpeded.

[0166] Step 4: CU-CP, considering the overall network topology, remaps the uplink data originally transmitted from IAB1 to the path (IAB1->IAB2) link to the path (IAB1->IAB3) link. This allows UE1's data to directly reach the IAB Donor-DU via IAB3 before being transmitted via CU-UP, thus alleviating link congestion between IAB2 and IAB4. Specifically, CU-CP sends a new F1 message to IAB1, modifying the routing ID of the data packets transmitted from UE1 to IAB1 and configuring a new mapping table for IAB1. This ensures that the egress BH RLC channel corresponding to the uplink data originally intended for transmission from IAB1 to the path (IAB1->IAB2) link is the BH RLC channel on the path (IAB1->IAB3).

[0167] Step 5: IAB1 receives the new routing configuration information and mapping configuration table, updates them, and simultaneously replies with an acknowledgment message to CU-CP. Then, it transmits UE1's uplink data packets to the new routing path.

[0168] In one embodiment, this embodiment provides a congestion processing device, which is mainly applied to a first node, such as... Figure 8 As shown, the congestion handling device provided in this embodiment mainly includes a receiving module 81 and a processing module 82.

[0169] The receiving module 81 is configured to receive congestion information, wherein the congestion information is used by the first node to perform congestion processing.

[0170] Processing module 82 is configured to perform congestion processing based on the congestion information.

[0171] In one exemplary implementation, the congestion information includes one or more of the following:

[0172] Downlink congestion information, uplink congestion information, downlink congestion data radio bearer (DRB) information.

[0173] In one exemplary implementation, the downlink congestion information includes one or more of the following:

[0174] Radio backhaul (RLC) channel identifier for congested links;

[0175] The route identifier for the congested link;

[0176] IAB child node identifier of the congested link;

[0177] Downlink data transmission efficiency of congested links.

[0178] In one exemplary implementation, downlink data transmission efficiency includes one or more of the following:

[0179] The ratio of actual downlink cache to supported downlink cache;

[0180] The ratio of the data rate of the outgoing radio backhaul RLC channel to the data rate of the incoming radio backhaul RLC channel.

[0181] In one exemplary implementation, the uplink congestion information includes one or more of the following:

[0182] Radio backhaul (RLC) channel identifier for congested links;

[0183] Link identifier of the congested link;

[0184] IAB child node identifier of the congested link;

[0185] Buffer Status Report (BSR) reported by child nodes of congested links;

[0186] Uplink data transmission efficiency of congested links.

[0187] In one exemplary embodiment, the radio backhaul RLC channel identifier includes an ingress radio backhaul RLC channel identifier and / or an egress radio backhaul RLC channel identifier.

[0188] In one exemplary implementation, the IAB sub-node identifier includes a Wireless Backhaul Adaptor Protocol (BAP) address and / or an IP address.

[0189] In one exemplary implementation, the uplink data transmission efficiency includes the ratio of the actual uplink cache to the uplink cache that can be supported.

[0190] In one exemplary implementation, the downlink congested data radio bearer (DRB) information includes one or more of the following:

[0191] DRB indicator for congestion;

[0192] The identifier of the UE to which the congested DRB belongs;

[0193] Congested GPRS tunneling protocol tunnel endpoint identifier;

[0194] The amount of data required to congest the DRB;

[0195] The rate at which the DRB is congested.

[0196] In one exemplary implementation, the method of receiving link congestion information includes one of the following:

[0197] Receive downlink or uplink congestion information sent by the second node through the F1AP interface;

[0198] Receive downlink congestion data radio bearer DRB information sent by the third node through the E1AP interface.

[0199] The congestion processing apparatus provided in this embodiment can execute the congestion processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the method. Technical details not described in detail in this embodiment can be found in the congestion processing method provided in any embodiment of the present invention.

[0200] It is worth noting that in the embodiments of the congestion handling device described above, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of this application.

[0201] In one embodiment, this embodiment provides a congestion processing device, which is mainly applied to a second node, such as... Figure 9 As shown, the congestion processing device provided in this embodiment mainly includes a first determining module 91 and a first sending module 92.

[0202] The first determining module 91 is configured to determine congestion information, wherein the congestion information includes downlink congestion information or uplink congestion information;

[0203] The first sending module 92 is configured to send the congestion information to the first node via the F1AP interface.

[0204] In one exemplary implementation, the congestion information includes one or more of the following:

[0205] Downlink congestion information, uplink congestion information, downlink congestion data radio bearer (DRB) information.

[0206] In one exemplary implementation, the downlink congestion information includes one or more of the following:

[0207] Radio backhaul (RLC) channel identifier for congested links;

[0208] The route identifier for the congested link;

[0209] IAB child node identifier of the congested link;

[0210] Downlink data transmission efficiency of congested links.

[0211] In one exemplary implementation, downlink data transmission efficiency includes one or more of the following:

[0212] The ratio of actual downlink cache to supported downlink cache;

[0213] The ratio of the data rate of the outgoing radio backhaul RLC channel to the data rate of the incoming radio backhaul RLC channel.

[0214] In one exemplary implementation, the uplink congestion information includes one or more of the following:

[0215] Radio backhaul (RLC) channel identifier for congested links;

[0216] Link identifier of the congested link;

[0217] IAB child node identifier of the congested link;

[0218] Buffer Status Report (BSR) reported by child nodes of congested links;

[0219] Uplink data transmission efficiency of congested links.

[0220] In one exemplary embodiment, the radio backhaul RLC channel identifier includes an ingress radio backhaul RLC channel identifier and / or an egress radio backhaul RLC channel identifier.

[0221] In one exemplary implementation, the IAB sub-node identifier includes a Wireless Backhaul Adaptor Protocol (BAP) address and / or an IP address.

[0222] In one exemplary implementation, the uplink data transmission efficiency includes the ratio of the actual uplink cache to the uplink cache that can be supported.

[0223] The congestion processing apparatus provided in this embodiment can execute the congestion processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the method. Technical details not described in detail in this embodiment can be found in the congestion processing method provided in any embodiment of the present invention.

[0224] It is worth noting that in the embodiments of the congestion handling device described above, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of this application.

[0225] In one embodiment, this embodiment provides a congestion processing device, which is mainly applied to a third node, such as... Figure 10 As shown, the congestion processing device provided in this embodiment mainly includes a second determining module 101 and a second sending module 102.

[0226] The second determining module 101 is configured to determine congestion information, wherein the congestion information includes downlink congested data radio bearer (DRB) information;

[0227] The second sending module 102 is configured to send the congestion information to the first node via the E1AP interface.

[0228] In one exemplary implementation, the downlink congested data radio bearer (DRB) information includes one or more of the following:

[0229] DRB indicator for congestion;

[0230] The UE identifier to which the congestion DRB belongs;

[0231] Congested GPRS tunneling protocol tunnel endpoint identifier;

[0232] The amount of data required to congest the DRB;

[0233] The rate at which the DRB is congested.

[0234] The congestion processing apparatus provided in this embodiment can execute the congestion processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the method. Technical details not described in detail in this embodiment can be found in the congestion processing method provided in any embodiment of the present invention.

[0235] It is worth noting that in the embodiments of the congestion handling device described above, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of this application.

[0236] This application also provides a device. Figure 11 This is a schematic diagram of the structure of a device provided in an embodiment of this application, such as... Figure 11 As shown, the device includes a processor 111, a memory 112, an input device 113, an output device 114, and a communication device 115; the number of processors 111 in the device can be one or more. Figure 11 Taking a processor 111 as an example; the processor 111, memory 112, input device 113, and output device 114 in the device can be connected via a bus or other means. Figure 11 Taking the example of a connection between China and Israel via a bus.

[0237] The memory 112, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules. The processor 111 executes various functional applications and data processing of the device by running the software programs, instructions, and modules stored in the memory 112, thereby implementing any of the methods provided in the embodiments of this application.

[0238] The memory 112 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on device usage. Furthermore, the memory 112 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 112 may further include memory remotely located relative to the processor 111, which can be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0239] Input device 113 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the device. Output device 114 may include display devices such as a display screen.

[0240] The communication device 115 may include a receiver and a transmitter. The communication device 115 is configured to perform information transmission and reception communication under the control of the processor 111.

[0241] It should be noted that, when the aforementioned device is the first node, the processor 111 executes various functional applications and data processing by running programs stored in the system memory 112, such as implementing the congestion handling method provided in the embodiments of this application, which includes:

[0242] Receive congestion information, wherein the congestion information is used by the first node to perform congestion processing;

[0243] Congestion processing is performed based on the congestion information.

[0244] Of course, those skilled in the art will understand that the processor 111 can also implement the technical solutions of the congestion handling methods provided in any embodiment of this application. The hardware structure and functions of this device can be found in the explanation of this embodiment.

[0245] It should be noted that, when the aforementioned device is a second node, the processor 111 executes various functional applications and data processing by running programs stored in the system memory 112, such as implementing the congestion handling method provided in the embodiments of this application, which includes:

[0246] Determine congestion information, wherein the congestion information includes downlink congestion information or uplink congestion information;

[0247] The congestion information is sent to the first node via the F1AP interface.

[0248] Of course, those skilled in the art will understand that the processor 111 can also implement the technical solutions of the congestion handling methods provided in any embodiment of this application. The hardware structure and functions of this device can be found in the explanation of this embodiment.

[0249] It should be noted that, when the aforementioned device is a third node, the processor 111 executes various functional applications and data processing by running programs stored in the system memory 112, such as implementing the congestion handling method provided in the embodiments of this application, which includes:

[0250] Determine congestion information, wherein the congestion information includes downlink congested data radio bearer (DRB) information;

[0251] The congestion information is sent to the first node via the E1AP interface.

[0252] Of course, those skilled in the art will understand that the processor 111 can also implement the technical solutions of the congestion handling methods provided in any embodiment of this application. The hardware structure and functions of this device can be found in the explanation of this embodiment.

[0253] In one exemplary embodiment, this application also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a congestion handling method applied to a first node, including:

[0254] Receive congestion information, wherein the congestion information is used by the first node to perform congestion processing;

[0255] Congestion processing is performed based on the congestion information.

[0256] Of course, the computer-executable instructions provided in the embodiments of this application are not limited to the method operations described above, but can also perform related operations in the congestion handling method provided in any embodiment of this application.

[0257] In one exemplary embodiment, this application also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a congestion handling method applied to a second node, including:

[0258] Determine congestion information, wherein the congestion information includes downlink congestion information or uplink congestion information;

[0259] The congestion information is sent to the first node via the F1AP interface.

[0260] Of course, the computer-executable instructions provided in the embodiments of this application are not limited to the method operations described above, but can also perform related operations in the congestion handling method provided in any embodiment of this application.

[0261] In one exemplary embodiment, this application also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a congestion handling method applied to a third node, including:

[0262] Determine congestion information, wherein the congestion information includes downlink congested data radio bearer (DRB) information;

[0263] The congestion information is sent to the first node via the E1AP interface.

[0264] Of course, the computer-executable instructions provided in the embodiments of this application are not limited to the method operations described above, but can also perform related operations in the congestion handling method provided in any embodiment of this application.

[0265] Based on the above description of the implementation methods, those skilled in the art can clearly understand that this application can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0266] The above description is merely an exemplary embodiment of this application and is not intended to limit the scope of protection of this application.

[0267] Those skilled in the art will understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0268] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0269] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0270] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored in memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Multifunction Discs, DVDs, or CDs), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), programmable logic devices (FGPAs), and processors based on multi-core processor architectures.

[0271] A detailed description of exemplary embodiments of this application has been provided above through exemplary and non-limiting examples. However, various modifications and adjustments to the above embodiments will be apparent to those skilled in the art when considered in conjunction with the accompanying drawings and claims, without departing from the scope of the invention. Therefore, the proper scope of the invention will be determined by the claims.

Claims

1. A congestion handling method, characterized in that, The method is applied to the first node and includes: Receive congestion information, wherein the congestion information is used by the first node to perform congestion processing; the first node is a CU-UP node; Congestion processing is performed based on the congestion information; The congestion information includes downlink congestion information, uplink congestion information, and downlink congested data radio bearer (DRB) information; the downlink congestion information includes the downlink data transmission efficiency of the congested link; the uplink congestion information includes the uplink data transmission efficiency of the congested link; and the uplink data transmission efficiency includes the ratio of actual uplink buffer to supportable uplink buffer. One of the following methods can be used to receive link congestion information: Receive downlink congestion information or uplink congestion information sent by the second node through the F1AP interface; wherein, the second node is the IAB node that detected the link congestion; Receive downlink congestion data radio bearer (DRB) information sent by a third node through the E1AP interface; wherein the third node is an IAB node or CU-UP node that is experiencing DRB congestion.

2. The method according to claim 1, characterized in that, The downlink congestion information includes one or more of the following: Radio backhaul (RLC) channel identifier for congested links; The route identifier for the congested link; IAB child node identifier of the congested link.

3. The method according to claim 2, characterized in that... Downlink data transmission efficiency includes one or more of the following: The ratio of actual downlink cache to supported downlink cache; The ratio of the data rate of the outgoing radio backhaul RLC channel to the data rate of the incoming radio backhaul RLC channel.

4. The method according to claim 1, characterized in that, The uplink congestion information includes one or more of the following: Radio backhaul (RLC) channel identifier for congested links; Link identifier of the congested link; IAB child node identifier of the congested link; Buffer Status Report (BSR) reported by child nodes of congested links.

5. The method according to claim 2 or 4, characterized in that... The wireless backhaul RLC channel identifier includes the ingress wireless backhaul RLC channel identifier and / or the egress wireless backhaul RLC channel identifier.

6. The method according to claim 2 or 4, characterized in that... The IAB sub-node identifier includes the Wireless Backhaul Adaptor Protocol (BAP) address and / or IP address.

7. The method according to claim 1, characterized in that, The downlink congestion data radio bearer (DRB) information includes one or more of the following: DRB indicator for congestion; The UE identifier to which the congestion DRB belongs; GPRS tunneling protocol tunnel endpoint identifier for congested DRB; The amount of data required to congest the DRB; The rate at which the DRB is congested.

8. A congestion handling method, characterized in that, The method is applied to the second node, including: Determine congestion information, wherein the congestion information includes uplink congestion information and downlink congestion information; wherein the downlink congestion information includes the downlink data transmission efficiency of the congested link; the uplink congestion information includes the uplink data transmission efficiency of the congested link; wherein the uplink data transmission efficiency includes: the ratio of actual uplink buffer to the supportable uplink buffer; The congestion information is sent to the first node via the F1AP interface; wherein the second node is an IAB node that detects link congestion, and the first node is a CU-UP node.

9. A congestion handling method, characterized in that, The method is applied to the third node, including: Determine congestion information, wherein the congestion information includes downlink congested data radio bearer (DRB) information; The congestion information is sent to the first node via the E1AP interface; wherein the third node is either the IAB node or the CU-UP node that is experiencing DRB congestion, and the first node is a CU-UP node; The downlink congestion data radio bearer DRB information includes one or more of the following: DRB indicator for congestion; The UE identifier to which the congestion DRB belongs; GPRS tunneling protocol tunnel endpoint identifier for congested DRB; The amount of data required to congest the DRB; The rate at which the DRB is congested.

10. A congestion handling apparatus, characterized in that, The device is configured at the first node and includes: The receiving module is configured to receive congestion information, wherein the congestion information is used by the first node for congestion processing; the first node is a CU-UP node. The processing module is configured to perform congestion processing based on the congestion information; The congestion information includes downlink congestion information, uplink congestion information, and downlink congested data radio bearer (DRB) information; the downlink congestion information includes the downlink data transmission efficiency of the congested link; the uplink congestion information includes the uplink data transmission efficiency of the congested link; and the uplink data transmission efficiency includes the ratio of actual uplink buffer to supportable uplink buffer. One of the following methods can be used to receive link congestion information: Receive downlink congestion information or uplink congestion information sent by the second node through the F1AP interface; wherein, the second node is the IAB node that detected the link congestion; Receive downlink congestion data radio bearer (DRB) information sent by a third node through the E1AP interface; wherein the third node is an IAB node or CU-UP node that is experiencing DRB congestion.

11. A congestion handling apparatus, characterized in that, The device is configured at the second node and includes: The first determining module is configured to determine congestion information, wherein the congestion information includes uplink congestion information and downlink congestion information; wherein the downlink congestion information includes the downlink data transmission efficiency of the congested link; the uplink congestion information includes the uplink data transmission efficiency of the congested link; wherein the uplink data transmission efficiency includes the ratio of the actual uplink buffer to the supportable uplink buffer. The first sending module is configured to send the congestion information to the first node via the F1AP interface; wherein the second node is an IAB node that detects link congestion, and the first node is a CU-UP node.

12. A congestion handling device, characterized in that, The device is configured at the third node and includes: The second determining module is configured to determine congestion information, wherein the congestion information includes downlink congested data radio bearer (DRB) information; The second sending module is configured to send the congestion information to the first node via the E1AP interface; wherein the third node is an IAB node or a CU-UP node that has experienced DRB congestion, and the first node is a CU-UP node; The downlink congestion data radio bearer DRB information includes one or more of the following: DRB indicator for congestion; The UE identifier to which the congestion DRB belongs; GPRS tunneling protocol tunnel endpoint identifier for congested DRB; The amount of data required to congest the DRB; The rate at which the DRB is congested.

13. A congestion handling device, characterized in that, include: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-9.

14. A storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1-9.

Images