A flow control method, apparatus, node and storage medium

Abstract

The application provides a flow control method and device, a node and a storage medium. The method is applied to a congested self-access backhaul link IAB node. Downlink congestion of the congested IAB node occurs. The method comprises reporting downlink congestion information to an IAB donor through a first interface. The downlink congestion information is used for the IAB donor to slow down transmission of downlink data of a data radio bearer corresponding to the congested IAB node.

Description

Technical Field

[0001] This application relates to the field of communications, specifically to a flow control method, apparatus, node, and storage medium. Background Technology

[0002] With the application of 5G networks, Integrated Access and Backhaul (IAB) technology has been proposed. IAB enables more flexible deployment of dense New Radio (NR) cells through wireless backhaul links and relay links.

[0003] Currently, in 5G IAB scenarios, how congested IAB nodes report downlink congestion information to the IAB host node remains a technical problem that urgently needs to be solved. Summary of the Invention

[0004] This application provides a flow control method, apparatus, node, and storage medium.

[0005] In a first aspect, embodiments of this application provide a flow control method applied to a congested self-access backhaul (IAB) node, wherein the downlink of the congested IAB node is congested, comprising:

[0006] The downlink congestion information is reported to the IAB host through the first interface. The downlink congestion information is used by the IAB host to slow down the transmission of downlink data on the data radio bearer corresponding to the congested IAB node.

[0007] Secondly, embodiments of this application provide a flow control method applied to an IAB host, comprising:

[0008] Receive downlink congestion information through the first interface;

[0009] Look up the identifier information of the user equipment data radio bearer corresponding to the downlink congestion information in the mapping table;

[0010] Slow down the transmission of downlink data for the data radio bearer corresponding to the identification information of the user equipment data radio bearer.

[0011] Thirdly, embodiments of this application provide a flow control device integrated into a congested IAB node, wherein downlink congestion occurs in the congested IAB node, including:

[0012] The reporting module is configured to report downlink congestion information to the IAB host through a first interface. The downlink congestion information is used by the IAB host to slow down the transmission of downlink data on the data radio bearer corresponding to the congested IAB node.

[0013] In a fourth aspect, an embodiment of the present application provides a flow control device integrated in an IAB donor, comprising:

[0014] a receiving module configured to receive downlink congestion information through a first interface;

[0015] a searching module configured to search for identification information of a user equipment data radio bearer corresponding to the downlink congestion information in a mapping relationship table;

[0016] a slowing module configured to slow down transmission of downlink data of the data radio bearer corresponding to the identification information of the user equipment data radio bearer.

[0017] In a fifth aspect, an embodiment of the present application provides a congested IAB node, wherein a downlink of the congested IAB node is congested, comprising:

[0018] one or more processors;

[0019] a storage device configured to store one or more programs;

[0020] When the one or more programs are executed by the one or more processors, the one or more processors implement the method of the first aspect of the present application.

[0021] In a sixth aspect, an embodiment of the present application provides an IAB donor, comprising:

[0022] one or more processors;

[0023] a storage device configured to store one or more programs;

[0024] When the one or more programs are executed by the one or more processors, the one or more processors implement the method of the second aspect of the present application.

[0025] In a seventh aspect, an embodiment of the present application provides a storage medium, wherein the storage medium stores a computer program, and the computer program is executed by a processor to implement any one of the methods in the embodiments of the present application.

[0026] More details about the above embodiments and other aspects of the present application and implementation manners thereof are provided in the description of drawings, specific embodiments and claims. BRIEF DESCRIPTION OF DRAWINGS

[0027] Figure 1 a basic topology diagram of a 5G IAB provided by an embodiment of the present application;

[0028] Figure 2 a flowchart of a flow control method provided by an embodiment of the present application;

[0029] Figure 3 A flowchart of another traffic control method provided by an embodiment of the present application is shown in FIG. 6;

[0030] Figure 4 A scenario diagram of a congested IAB node reporting flow control information to an IAB donor provided by an embodiment of the present application is shown in FIG. 7;

[0031] Figure 5 A structural diagram of a traffic control device provided by an embodiment of the present application is shown in FIG. 8;

[0032] Figure 6 A structural diagram of another traffic control device provided by an embodiment of the present application is shown in FIG. 9;

[0033] Figure 7 A structural diagram of a congested IAB provided by an embodiment of the present application is shown in FIG. 10;

[0034] Figure 8 A structural diagram of an IAB donor provided by an embodiment of the present application is shown in FIG. 11. DETAILED DESCRIPTION

[0035] To make the objectives, technical solutions and advantages of the present application clearer, the embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other as long as there is no conflict.

[0036] The steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Moreover, although the logical order is shown in the flowchart, in some cases, the steps shown or described herein can be executed in an order different from that shown.

[0037] In the research topic of 5G, IAB has many technical advantages. Specifically, IAB can more flexibly deploy dense NR cells through wireless backhaul links and relay links, while the network does not need to increase the dense deployment of transmission networks accordingly. Figure 1 A basic topology diagram of a 5G IAB provided by an embodiment of the present application is shown in FIG. 12. Referring to FIG. 12, Figure 1Wherein, the access node supporting wireless access of user equipment (User Equipment, UE) and wireless backhaul of user plane or control plane data packets is called IAB node (namely IAB node), and the IAB node is composed of two parts: a distributed unit (Distributed Unit, DU) (or gNB logical function) and a mobile terminal (Mobile Terminal, MT) logical function (also called UE logical function). And the access node providing wireless backhaul function for the IAB node to enable the UE to connect to the core network is called IAB donor (namely IAB donor), and the IAB donor includes two parts of DU and centralized unit (Centralized Unit, CU), and the F1 interface is the interface between the DU and the CU, wherein the CU is composed of two parts of CU control plane (CU-Control Plane, CU-CP) and CU user plane (CU-User Plane, CU-UP), which represent the control plane and the user plane respectively. The IAB node (also called sub-IAB node, IAB sub-node, or child IAB node) can access another IAB node (also called parent IAB node, IAB parent node, or parent IAB node) or access the IAB donor through the air interface. The user plane or control plane data packets between the access nodes can be transmitted through the wireless backhaul link (namely backhaul link). Based on the problem that the congested nodes in the 5G-IAB scenario, such as the intermediate nodes, cannot report flow control information to the IAB donor, the application provides a corresponding technical solution. Wherein, the flow control information can also be called downlink flow control information, and the flow control information can be understood as downlink congestion information.

[0038] Specifically, Figure 2 A flow chart of a traffic control method provided by an embodiment of the application. The method can be applied to the case of reporting congestion information to the IAB donor. The method can be executed by the traffic control device provided by the application, which can be realized by software and / or hardware and integrated on the congested IAB node.

[0039] As Figure 2 The traffic control method provided by the application includes S210.

[0040] S210, report the downlink congestion information to the IAB donor through the first interface.

[0041] The flow control method in this embodiment is applied to a congested IAB node, where downlink congestion has occurred. The congested IAB node can report downlink congestion information to the IAB host through a first interface. The first interface is not limited, as long as the congested IAB node can report downlink congestion information to the IAB host through this first interface. The first interface can be pre-agreed upon by the congested IAB node and the IAB host.

[0042] Downlink congestion information can directly or indirectly indicate to the IAB host the downlink where congestion is occurring, allowing the IAB host to control the downlink data on that downlink and thus resolve the congestion problem. Here, the downlink congestion information is not limited to simply indicating the downlink where congestion is occurring.

[0043] Downlink congestion information may include one of the following: identification information of the backhaul link at the ingress of the congested IAB node, based on which the congested downlink can be determined; identification information of the target IAB node, where congestion has occurred on the downlink between the target IAB node and the congested IAB node, and the congested downlink can be determined based on this identification information and the ingress backhaul link; or identification information of the routes contained in the downlink where the congestion has occurred at the congested IAB node. Downlink congestion information may also include at least one of the following: the amount of data required for the backhaul link at the ingress of the congested IAB node; or the data rate required for the backhaul link at the ingress of the congested IAB node.

[0044] The downlink congestion information is used by the IAB host to slow down the transmission of downlink data on the data radio bearer corresponding to the congested IAB node.

[0045] This application provides a flow control method that reports downlink congestion information to an IAB host through a first interface. The downlink congestion information is used by the IAB host to slow down the transmission of downlink data on the data radio bearer corresponding to the congested IAB node. This method can effectively feed back downlink congestion information to the IAB host when downlink congestion occurs at the congested IAB node, thereby solving the congestion problem of the congested IAB node.

[0046] Based on the above embodiments, modified embodiments of the above embodiments are proposed. It should be noted that, in order to keep the description brief, only the differences from the above embodiments are described in the modified embodiments.

[0047] In one embodiment, the first interface includes a General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTP-U) subheader on the F1 interface between the IAB host central control unit and the IAB host central control unit, wherein the GTP-U subheader contains a GTP Tunnel Endpoint Identifier (TEID) that is either a Tunnel Endpoint Identifier assigned by the IAB host central control unit to the data radio bearer of the access user equipment of the congested IAB node, or a Tunnel Endpoint Identifier assigned by the IAB host central control unit to the congested IAB node.

[0048] The congested IAB node sends downlink congestion information through the GTP-U subheader on the F1 interface between it and the IAB host central unit (CU). The GTP-TEID contained in the GTP-U subheader can be set to the TEID assigned by the CU to the data radio bearer (DRB) of the access user equipment of the congested IAB node, or it can be set to the TEID assigned by the CU to the IAB node.

[0049] In one embodiment, the downlink congestion information includes at least one of the following: identification information of the backhaul link of the congested IAB node ingress; the amount of data required for the backhaul link of the congested IAB node ingress; and the data rate required for the backhaul link of the congested IAB node ingress.

[0050] Based on the identification information of the ingress backhaul link, downlink congestion can be identified on the egress link of the congested IAB node. The identification information of the ingress backhaul link can then be used to determine the data radio bearer corresponding to the congested IAB node. Controlling the downlink data of this data radio bearer can resolve the congestion problem.

[0051] The amount of data required for the backhaul link of a congested IAB node ingress can be the maximum amount of data that the congested IAB node ingress can receive. The data rate required for the backhaul link of a congested IAB node ingress can be the maximum data rate that the congested IAB node ingress can receive.

[0052] In one embodiment, the downlink congestion information includes at least one of the following: identification information of the target IAB node, indicating that the downlink between the target IAB node and the congested IAB node is congested; the amount of data required for the backhaul link of the congested IAB node's ingress; and the data rate required for the backhaul link of the congested IAB node's ingress.

[0053] Downlink congestion information may include a target IAB node with which congestion has occurred. Based on the target IAB node's identification information, it can be determined that congestion has occurred between the target IAB node and the congested IAB node.

[0054] In one embodiment, the downlink congestion information includes at least one of the following: identification information of routes contained in the downlink where the congested IAB node is congested; the amount of data required for the backhaul link of the ingress of the congested IAB node; and the data rate required for the backhaul link of the ingress of the congested IAB node.

[0055] This application also provides a flow control method. Figure 3 This is a flowchart illustrating another flow control method provided in an embodiment of this application. This method is applicable to situations where congestion information is received from congested IAB nodes to alleviate downlink data transmission by the congested IAB nodes. This method can be executed by the flow control device provided in this application, which can be implemented in software and / or hardware and integrated on the IAB host node.

[0056] like Figure 3 As shown, the flow control method provided in this application includes S310, S320 and S330.

[0057] S310, Receive downlink congestion information through the first interface.

[0058] The first interface includes at least one of the following: a user plane interface of the congested IAB node serving as a central unit between the access IAB node and the IAB host; a newly established user plane interface between the congested IAB node and the central unit of the IAB host.

[0059] The IAB host can receive downlink congestion information through the first interface, and this downlink congestion information can be sent by the congested IAB node. Specifically, the CU-UP in the IAB host can receive downlink congestion information through the first interface.

[0060] S320. Search the mapping table for the identifier information of the user equipment data radio bearer corresponding to the downlink congestion information.

[0061] In one example, the mapping table can be sent from the CU-CP of the IAB host to the CU-UP, and the CU-UP can look up the identification information of the user equipment data radio bearer corresponding to the downlink congestion information based on the mapping table.

[0062] The timing of CU-CP sending the mapping table is not limited here; it can be sent before the identification information of the user equipment data radio bearer corresponding to the downlink congestion information is found in the mapping table.

[0063] The mapping table is not limited here. The specific content of the mapping table can be determined based on the content included in the downlink congestion information, as long as the identification information of the user equipment data radio bearer corresponding to the downlink congestion information can be determined based on the mapping table.

[0064] S330, slow down the transmission of downlink data of the data radio bearer corresponding to the identification information of the user equipment data radio bearer.

[0065] After determining the identification information of the user equipment data radio bearer corresponding to the downlink congestion information, the IAB host can slow down the downlink data of the data radio bearer corresponding to the identification information to resolve the congestion problem of the congested IAB node.

[0066] Specifically, the method for mitigating downlink data transmission can be determined based on the information included in the downlink congestion information. In one example, if the downlink congestion information includes the amount of data required for the backhaul link of the congested IAB node ingress, the amount of data to be sent to the backhaul link of the congested IAB node ingress is determined based on this amount. If the downlink congestion information includes the data rate required for the backhaul link of the congested IAB node ingress, the data rate sent to the ingress backhaul link is determined based on this data rate, thereby achieving the technical effect of mitigating downlink data transmission.

[0067] For details not covered in this embodiment, please refer to the above embodiments; they will not be repeated here.

[0068] The flow control method provided in this application receives downlink congestion information through a first interface; searches for the identifier information of the user equipment data radio bearer corresponding to the downlink congestion information in a mapping table; and slows down the transmission of downlink data of the data radio bearer corresponding to the identifier information of the user equipment data radio bearer. Using this method, upon receiving downlink congestion information, based on the mapping table and the downlink congestion information, the downlink data of the data radio bearer corresponding to the identifier information of the user equipment data radio bearer can be slowed down to resolve the congestion problem of the IAB node.

[0069] Based on the above embodiments, modified embodiments of the above embodiments are proposed. It should be noted that, in order to keep the description brief, only the differences from the above embodiments are described in the modified embodiments.

[0070] In one embodiment, the IAB host includes a centralized unit control plane (CU-CP) and a centralized unit user plane (CU-UP); the mapping table is a mapping table sent from the CU-CP to the CU-UP.

[0071] In one embodiment, the downlink congestion information includes at least one of the following: identification information of the backhaul link of the congested IAB node ingress; the amount of data required for the backhaul link of the congested IAB node ingress; and the data rate required for the backhaul link of the congested IAB node ingress.

[0072] The mapping table includes at least one of the following: a mapping relationship between the identification information of the backhaul link at the ingress of each IAB node in the IAB network and the identification information of the corresponding user equipment data radio bearer, such as the correspondence between the ingress (i.e., Ingess) backhaul (BH) radio link control (RLC) channel identifier (ID) and the UE DRB ID; a mapping relationship between the identification information of the backhaul link at the ingress of each IAB node in the IAB network and the identification information of the backhaul link at the corresponding egress, and a mapping relationship between the identification information of the backhaul link at the egress of the IAB host and the identification information of the corresponding user equipment data radio bearer, such as the mapping relationship between the Ingress BH RLC channel ID and the egress (i.e., Egress) BH RLC channel ID and the mapping relationship between the Egress BH RLC channel ID and the UE DRB ID.

[0073] It is important to note that an IAB-node can receive downlink data from the previous IAB-node or IAB-Donor via the ingress BH RLC Channel. After processing, the downlink data is forwarded to the next IAB-node or IAB-Donor via the corresponding egress BH RLCChannel.

[0074] In one embodiment, the downlink congestion information includes at least one of the following: identification information of the target IAB node, wherein the downlink between the target IAB node and the congested IAB node is congested; the amount of data required for the backhaul link of the congested IAB node ingress; and the data rate required for the backhaul link of the congested IAB node ingress.

[0075] The mapping table includes at least one of the following: a mapping relationship between the transmission link between each IAB node and the next-hop IAB node in the IAB network and the identification information of the user equipment data radio bearer corresponding to the transmission link between each IAB node and the next-hop IAB node in the user equipment IAB network; a mapping relationship between the identification information of the backhaul link at the ingress of each IAB node in the IAB network and the identification information of the backhaul link at the corresponding egress; and a mapping relationship between the identification information of the backhaul link at the egress of the IAB host and the identification information of the corresponding user equipment data radio bearer.

[0076] In one embodiment, the downlink congestion information includes at least one of the following: identification information of routes contained in the downlink where the congested IAB node is congested; the amount of data required for the backhaul link of the congested IAB node ingress; and the data rate required for the backhaul link of the congested IAB node ingress.

[0077] The mapping table includes a mapping relationship between routing identifiers and identification information of user data radio bearers in the IAB network. The routing identifier is the identification information of the route from the access user equipment to the IAB host in the IAB network.

[0078] In one embodiment, if the downlink congestion information includes the identification information of the backhaul link of the congested IAB node ingress, it is determined that the egress link of the congested IAB node is congested; if the downlink congestion information includes the data volume required for the backhaul link of the congested IAB node ingress, the data volume to be sent to the backhaul link of the congested IAB node ingress is determined based on the data volume required for the backhaul link of the congested IAB node ingress; if the downlink congestion information includes the data rate required for the backhaul link of the congested IAB node ingress, the data rate of the backhaul link of the congested IAB node ingress is determined based on the data rate required for the backhaul link of the congested IAB node ingress; if the downlink congestion information includes the identification information of the target IAB node, it is determined that the downlink link between the congested IAB node and the target IAB node is congested; if the downlink congestion information includes the identification information of the routes contained in the downlink link where the congested IAB node is congested, it is determined that the route corresponding to the identification information of the route contained in the downlink link where the congested IAB node is congested occurs when it passes through the congested IAB node.

[0079] The following is an exemplary description of embodiments of this application: Figure 4 This application provides an example diagram illustrating a scenario where a congested IAB node reports flow control information to the IAB host. (See also...) Figure 4 The IAB network includes three IAB nodes and an IAB host, with IAB node 2 being a congested IAB node. The method described in this application can be a process handling method for IABs applicable to new wireless systems.

[0080] One embodiment of this application provides a flow control processing method, i.e., a flow control method. In this method, a congested IAB node reports flow control information of the congested path to the CU-UP of the IAB host. The IAB host CU-CP sends a mapping table of Ingress BH RLC channel IDs and UE DRB IDs (lists) of each IAB sub-node in the IAB network to the CU-UP via the E1 interface. The CU-UP parses the flow control information and the mapping table to perform downlink flow control processing. The E1 interface is the interface between the CU-UP and the CU-CP. The UE DRB IDs may include at least one. Multiple UE DRB IDs are represented in list form. In this application, the E1 interface is the interface between the CU-UP and the CU-CP.

[0081] Example 1: With Figure 4 Taking the IAB topology shown as an example, the downlink between IAB node 2 and IAB node 3 is congested.

[0082] S1 and IAB node 2 determine to trigger the downlink flow control feedback process. IAB node 2 will report the following information, i.e., downlink flow control information: the identification information of backhaul link 2, such as the Ingress BH RLC Channel2 ID; the expected data size (i.e., the desired buffer size) of backhaul link 2, such as the Ingress BH RLC Channel2, which is the required data amount expressed in bytes. In addition, the downlink congestion information may also include the data rate required by backhaul link 2, such as the desired data rate of Ingress BH RLCChannel2, expressed in bytes.

[0083] S2 and IAB node2 report downlink congestion information via the GTP-U subheader on the F1 interface between IAB node2 and the IAB host central unit. The GTP TEID contained in the GTP-U subheader is the TEID assigned by the CU to the access UE DRB of the congested IAB node, or it can be set to the TEID assigned by the CU to IAB node2.

[0084] S3, IAB Donor CU-UP, upon receiving downlink flow control feedback from IAB node2 (i.e., downlink congestion information), considers that the egress link (i.e., the egress link) of IAB Node2's Ingress BH RLC Channel2 ID is experiencing downlink congestion; considers the desired buffer size in bytes to be the total amount of data that IAB Donor CU-UP needs to send to the backhaul link corresponding to Ingress BH RLC Channel2 ID; considers the desired data rate in bytes to be the total amount of data that Ingress BH RLC Channel2 ID expects to receive within a certain period of 1 second.

[0085] S4. The IAB Donor CU-UP receives from E1 the mapping table of Ingress BH RLC channel ID and UE DRB ID of each IAB sub-node (i.e., IAB Node) in the IAB network, sent by the IAB Donor CU-CP. Table 1 is the mapping table of Ingress BH RLC channel ID and UE DRB ID of IAB Node in the IAB topology.

[0086] Table 1. Mapping Relationship between Ingess BH RLC channel ID and UE DRB ID of IAB Node in IAB Topology

[0087] IAB Node ID Ingress RLC Channel ID (list) UE DRB ID (list) 1. 2. 3.

[0088] S5. As shown in Table 1, the IAB Node ID can be understood as the identification information of each IAB node in the IAB network, which includes the identification information of congested IAB nodes. The IAB Donor CU-UP queries the UE DRB ID (list) corresponding to Ingress BH RLC Channel2 in the mapping table between Ingress BH RLC channelID and UE DRB ID of the IAB Node.

[0089] S6, IAB Donor CU-UP slows down the downlink data transmission of the UE DRB ID (list) corresponding to Ingress BH RLC Channel2.

[0090] In another embodiment of this application, the congested IAB node reports the flow control information of the congested path to the CU-UP of the IAB host. The IAB host CU-CP sends the mapping relationship between the Ingress BH RLC channel and the Egress BH RLC channel of each IAB sub-node in the IAB network and the mapping relationship between the egress BH RLC channel ID and the UE DRB ID (list) of the IAB host to the CU-UP through the E1 interface. The CU-UP parses the flow control information and the mapping relationship table and performs downlink flow control processing.

[0091] Example 2: with Figure 2 Taking the IAB topology shown as an example, downlink congestion occurs between IAB node2 and IAB node3. Only the differences from Example 1 are shown here; similarities are not repeated.

[0092] The IAB Donor CU-UP receives from E1 a mapping table of Ingress BH RLC channel IDs and Egress BH RLC channel IDs for each IAB sub-node in the IAB network, sent by the IAB Donor CU-CP. It also receives a mapping table of Egress BH RLC channel IDs and UE DRB IDs for the IAB Donor. Table 2 shows the mapping table of Ingress BH RLC channel IDs and Egress BH RLC channel IDs for the IAB sub-nodes. Table 3 shows the mapping table of Egress BH RLC channel IDs and UE DRB IDs for the IAB Donor.

[0093] It should be noted that the specific content to be filled in each form in this application can be determined based on the actual deployment of the IAB network, and is not limited here.

[0094] Table 2. Mapping Relationship between Ingress BH RLC Channel ID and Egress BH RLC Channel ID of IAB Sub-nodes

[0095]

[0096] Table 3 Mapping Relationship between IAB Donor's Egress BH RLC Channel ID and UE DRB ID

[0097]

[0098] The IAB Donor CU-UP queries and derives the UE DRB ID (list) corresponding to Ingress BH RLC Channel2 using Tables 2 and 3 above; the query and derivation process is as follows: Figure 2 For example:

[0099] 1. The IAB Donor CU-UP learns from the downlink flow control information, i.e. downlink congestion information, reported by IAB node2 that BHRLC Channel2 is congested on the egress link corresponding to the IAB node2 sub-node.

[0100] 2. The IAB Donor CU-UP queries Table 2 for the row containing Egress RLC Channel ID = BH RLC Channel2, and finds the corresponding IAB Node ID = 1 and Ingress RLC Channel ID = 1.

[0101] 3. The IAB Donor CU-UP continued to search Table 2 for the row containing Egress RLC Channel ID = BH RLCChannel1, and found that there was no row in the table that met the requirements;

[0102] 4. The IAB Donor CU-UP continues to query the row containing Egress RLC Channel ID = BH RLCChannel1 in Table 3 to obtain IAB Node ID = IAB Donor, and the UE DRB ID (list) of the corresponding row;

[0103] IAB Donor CU-UP slows down downlink data transmission for the UE DRB ID(list) corresponding to Ingress BH RLC Channel2.

[0104] In another embodiment of this application, the congested IAB node sends flow control information of the congestion path to the CU-UP of the IAB host. The CU-CP of the IAB host sends the mapping relationship of UE DRB IDs corresponding to the transmission links between each IAB node in the IAB network and the next-hop IAB node to the CU-UP through the E1 interface. The CU-UP parses the flow control information and the mapping table and performs downlink flow control processing.

[0105] In another embodiment of this application, the congested IAB node sends flow control information of the congested path to the CU-UP of the IAB host. The IAB host CU-CP sends the mapping relationship between the Ingress BH RLC channel and the Egress BH RLC channel of each IAB child node in the IAB network and the mapping relationship between the egress BH RLC channel ID and the UE DRB ID of the IAB host to the CU-UP through the E1 interface. The CU-UP parses the flow control information and the mapping relationship table and performs downlink flow control processing.

[0106] Example 3: with Figure 2 Taking the IAB topology shown as an example, the downlink between IAB node2 and IAB node3 is congested.

[0107] When IAB node2 decides to trigger the downlink flow control feedback process, IAB node2 will report the following information: IAB Node 3 identifier, i.e., the identifier information of the target IAB node; the desired buffer size in bytes of Ingress BH RLC Channel2; and optionally, the data rate required by Ingress BH RLC Channel2.

[0108] IAB node2 reports downlink congestion information via the GTP-U header on the F1 interface between IAB node2 and the IAB host central unit. The GTP-U header contains the GTP TEID, which is the TEID assigned by the CU to the access UE DRB of the congested IAB node, or it can be set to the TEID assigned by the CU to IAB node2.

[0109] When the IAB Donor CU-UP receives downlink flow control feedback from IAB node2, it assumes: that the downlink between IAB Node2 and IAB Node3 is congested; that the desired buffer size of Ingress BH RLC Channel2 is equal to the total amount of data that the IAB Donor CU-UP needs to send to the Ingress BH RLC Channel2 ID; and that the required data rate of Ingress BH RLC Channel2 is equal to the total amount of data that the Ingress BH RLC Channel2 ID expects to receive within a certain period of time, which can be 1 second.

[0110] The IAB Donor CU-UP receives from E1 the transmission links between each IAB node and the next-hop IAB node in the IAB network sent by the IAB Donor CU-CP, and the mapping relationship between the identification information of the user equipment data radio bearer, that is, the transmission links between each IAB sub-node and the next-hop IAB node, such as the Egress link (list) and UE DRB ID mapping table. Table 4 is the Egress link (list) and UE DRB ID mapping table of IAB Node in the IAB topology.

[0111] Table 4. Mapping Relationship between Egress Links (List) of IAB Nodes and UE DRB IDs in the IAB Topology

[0112] IAB Node ID Egress link (list) UE DRB ID (list) 1. 2. 3.

[0113] The IAB Donor CU-UP queries the mapping table between the Egress link (list) and UE DRB ID of the IAB Node to find the UE DRB ID (list) corresponding to the downlink between IAB Node2 and IAB Node3; the IAB Donor CU-UP slows down the downlink data transmission of the UE DRB ID (list) corresponding to the downlink between IAB Node2 and IAB Node3.

[0114] In another embodiment of this application, the congested IAB node sends flow control information of the congested path to the CU-UP of the IAB host. The IAB host CU-CP sends the mapping relationship between the Ingress BH RLC channel and the Egress BH RLC channel of each IAB sub-node in the IAB network and the mapping relationship between the egress BH RLC channel ID and the UE DRB ID (list) of the IAB host to the CU-UP through the E1 interface. The CU-UP parses the flow control information and the mapping relationship table and performs downlink flow control processing.

[0115] Example 4: Figure 2 Taking the IAB topology shown as an example, downlink congestion occurs between IAB node2 and IAB node3. This example only shows the differences from Embodiment 3; the similarities are not repeated.

[0116] The IAB Donor CU-UP receives from E1 the mapping table of Ingress BH RLC channel ID and Egress BH RLC channel ID of each IAB sub-node in the IAB network, sent by the IAB Donor CU-CP, as well as the mapping table of Egress BH RLC channel ID and UE DRB ID of the IAB Donor. Table 5 is the mapping table of Ingress BH RLC channel ID and Egress BH RLC channel ID of the IAB sub-node, and Table 6 is the mapping table of Egress BH RLC channel ID and UE DRB ID of the IAB Donor.

[0117] Table 5. Mapping Relationship between Ingress BH RLC Channel ID and Egress BH RLC Channel ID of IAB Sub-nodes

[0118]

[0119] Table 6. Mapping Relationship between IAB Donor's Egress BH RLC channel ID and UE DRB ID

[0120]

[0121] The IAB Donor CU-UP queries and derives the UE DRB ID(list) corresponding to Ingress BH RLC Channel2 using Tables 5 and 6 above; the query and derivation process is as follows: Figure 2 For example:

[0122] 1. The IAB Donor CU-UP learned from the downlink flow control information reported by IAB node2 that BH RLC Channel2 was congested on the egress link corresponding to the IAB node2 child node;

[0123] 2. The IAB Donor CU-UP queries Table 5 for the row containing Egress RLC Channel ID = BH RLC Channel2, and obtains the corresponding IAB Node ID = 1 and Ingress RLC Channel ID = 1.

[0124] 3. The IAB Donor CU-UP continued to search Table 5 for the row containing Egress RLC Channel ID = BH RLCChannel1, and found that there was no row in the table that met the requirements;

[0125] 4. The IAB Donor CU-UP continues to query the row containing Egress RLC Channel ID = BH RLCChannel1 in Table 6 to obtain IAB Node ID = IAB Donor, and the UE DRB ID (list) of the corresponding row;

[0126] IAB Donor CU-UP slows down the transmission of downlink data for the UE DRB ID(list) corresponding to the downlink between IAB Node2 and IAB Node3.

[0127] In another embodiment of this application, the congested IAB node sends flow control information of the congested path to the CU-UP of the IAB host. The CU-CP of the IAB host sends the routing identifiers in the IAB network, such as the mapping relationship between link route IDs (list) and UE DRB IDs (list), to the CU-UP via the E1 interface. The CU-UP parses the flow control information and the mapping relationship table and performs downlink flow control processing. In this application, "(list)" can indicate that the number of corresponding information is at least one, and can be represented in list form.

[0128] by Figure 2 Taking the IAB topology shown as an example, the downlink between IAB node2 and IAB node3 is congested.

[0129] IAB node2 determines to trigger the downlink flow control feedback process. IAB node2 will report the following information: downlink congestion information: Routing ID (list); desired buffer size of Ingress BH RLC Channel2. Downlink congestion information may also include: desired data rate of Ingress BH RLC Channel2.

[0130] IAB node2 reports downlink congestion information via the GTP-U header on the F1 interface between IAB node2 and the IAB host central unit. The GTP-U header contains the GTP TEID, which is the TEID assigned by the CU to the access UE DRB of the congested IAB node, or it can be set to the TEID assigned by the CU to IAB node2.

[0131] When the IAB Donor CU-UP receives downlink flow control feedback from IAB node2, it assumes: congestion has occurred on the routing ID(list) link via IAB Node2; the desired buffer size in bytes for Ingress BH RLC Channel2 is the total amount of data that IAB Donor CU-UP needs to send to Ingress BH RLC Channel2 ID; and the desired data rate in bytes for Ingress BH RLC Channel2 is the total amount of data that Ingress BH RLCChannel2 ID expects to receive within a certain period of 1 second.

[0132] The IAB Donor CU-UP receives routing identifiers in the IAB network sent by the IAB Donor CU-CP from the E1, such as the mapping table of Routing ID and UE DRB ID (list). Table 7 shows the mapping relationship between Routing ID and UE DRB ID (list) in the IAB topology.

[0133] Table 7. Mapping relationship between Routing ID and UE DRB ID (list) in IAB topology

[0134] Routing ID (list) UE DRB ID (list) 1. 2. 3.

[0135] The IAB Donor CU-UP queries the mapping table between Routing ID and UE DRB ID in the IAB network to find the UE DRB ID (list) corresponding to the Routing ID (list) via IAB Node2; the IAB Donor CU-UP slows down the transmission of downlink data via the Routing ID (list) corresponding to the UE DRB ID (list) via IAB Node2.

[0136] This application provides a flow control device. Figure 5 This is a schematic diagram of a flow control device provided in an embodiment of this application. The flow control device provided in this embodiment can be integrated into a congested IAB node, where the downlink of the congested IAB node is congested. Figure 5 As shown, the device includes: a reporting module 51, configured to report downlink congestion information to the IAB host through a first interface, wherein the downlink congestion information is used by the IAB host to slow down the transmission of downlink data of the data radio bearer corresponding to the congested IAB node.

[0137] The flow control device provided in this application embodiment is used to achieve, for example...Figure 2 The flow control method of the illustrated embodiment, the flow control device provided in this embodiment, and its implementation principle and technical effects are similar. Figure 2 The flow control method shown in the embodiment is similar and will not be described again here.

[0138] Based on the above embodiments, modified embodiments of the above embodiments are proposed. It should be noted that, in order to keep the description brief, only the differences from the above embodiments are described in the modified embodiments.

[0139] In one embodiment, the first interface includes a General Data Radio System Pipeline Protocol (GTP-U) subheader on the F1 interface between the congested IAB node and the IAB host central control unit, wherein the GTP-U subheader contains a GTP-U pipe endpoint identifier that is either a pipe endpoint identifier allocated by the IAB host central control unit for the data radio bearer of the congested IAB node accessing the user equipment, or a pipe endpoint identifier allocated by the IAB host central control unit for the congested IAB node.

[0140] The congested IAB node serves as the user plane interface between the access IAB node and the centralized unit of the IAB host.

[0141] The newly established user plane interface between the congested IAB node and the centralized unit of the IAB host.

[0142] In one embodiment, the downlink congestion information includes at least one of the following:

[0143] The identification information of the backhaul link at the ingress of the congested IAB node;

[0144] The amount of data required for the backhaul link at the congested IAB node ingress;

[0145] The data rate required for the backhaul link at the congested IAB node ingress.

[0146] In one embodiment, the downlink congestion information includes at least one of the following:

[0147] The identification information of the target IAB node indicates that the downlink between the target IAB node and the congested IAB node is congested.

[0148] The amount of data required for the backhaul link at the congested IAB node ingress;

[0149] The data rate required for the backhaul link at the congested IAB node ingress.

[0150] In one embodiment, the downlink congestion information includes at least one of the following:

[0151] The identification information of the routes contained in the downlink where the congestion occurs at the congested IAB node;

[0152] The amount of data required for the backhaul link at the congested IAB node ingress;

[0153] The data rate required for the backhaul link at the congested IAB node ingress.

[0154] This application also provides a flow control device. Figure 6 This is a schematic diagram of another flow control device provided in an embodiment of this application. This device can be integrated into an IAB host, such as... Figure 6 As shown, the device includes: a receiving module 61, configured to receive downlink congestion information through a first interface; a lookup module 62, configured to look up the identification information of the user equipment data radio bearer corresponding to the downlink congestion information in a mapping table; and a mitigation module 63, configured to mitigate the transmission of downlink data of the data radio bearer corresponding to the identification information of the user equipment data radio bearer.

[0155] Based on the above embodiments, modified embodiments of the above embodiments are proposed. It should be noted that, in order to keep the description brief, only the differences from the above embodiments are described in the modified embodiments.

[0156] In one embodiment, the IAB host includes a centralized unit control plane (CU-CP) and a centralized unit user plane (CU-UP); the mapping table is a mapping table sent from the CU-CP to the CU-UP.

[0157] In one embodiment, the downlink congestion information includes at least one of the following: identification information of the backhaul link of the congested IAB node ingress; the amount of data required for the backhaul link of the congested IAB node ingress; and the data rate required for the backhaul link of the congested IAB node ingress.

[0158] The mapping table includes at least one of the following:

[0159] The mapping relationship between the identification information of the backhaul link at the entrance of each IAB node in the IAB network and the identification information of the corresponding user equipment data radio bearer;

[0160] The mapping relationship between the identification information of the backhaul link at the ingress of each IAB node in the IAB network and the identification information of the corresponding egress backhaul link, and the mapping relationship between the identification information of the backhaul link at the egress of the IAB host and the identification information of the corresponding user equipment data radio bearer.

[0161] In one embodiment, the downlink congestion information includes at least one of the following: identification information of the target IAB node, wherein the downlink between the target IAB node and the congested IAB node is congested; the amount of data required for the backhaul link of the congested IAB node ingress; and the data rate required for the backhaul link of the congested IAB node ingress.

[0162] The mapping table includes at least one of the following:

[0163] The mapping relationship between the transmission link between each IAB node and the next-hop IAB node in the IAB network and the identification information of the user equipment data radio bearer corresponding to the transmission link between each IAB node and the next-hop IAB node in the user equipment IAB network.

[0164] The mapping relationship between the identification information of the backhaul link at the ingress of each IAB node in the IAB network and the identification information of the corresponding egress backhaul link, and the mapping relationship between the identification information of the backhaul link at the egress of the IAB host and the identification information of the corresponding user equipment data radio bearer.

[0165] In one embodiment, the downlink congestion information includes at least one of the following: identification information of routes contained in the downlink where the congested IAB node is congested; the amount of data required for the backhaul link of the congested IAB node ingress; and the data rate required for the backhaul link of the congested IAB node ingress.

[0166] The mapping table includes a mapping relationship between routing identifiers and identification information of user data radio bearers in the IAB network. The routing identifier is the identification information of the route from the access user equipment to the IAB host in the IAB network.

[0167] In one embodiment, if the downlink congestion information includes the identification information of the backhaul link at the ingress of the congested IAB node, it is determined that the egress link of the congested IAB node is congested.

[0168] If the downlink congestion information includes the amount of data required for the backhaul link of the congested IAB node ingress, the amount of data to be sent to the backhaul link of the congested IAB node ingress is determined based on the amount of data required for the backhaul link of the congested IAB node ingress.

[0169] If the downlink congestion information includes the data rate required for the backhaul link of the congested IAB node ingress, the data rate of the backhaul link of the congested IAB node ingress is determined based on the data rate required for the backhaul link of the congested IAB node ingress.

[0170] If the downlink congestion information includes the identification information of the target IAB node, it is determined that the downlink link between the congested IAB node and the target IAB node is congested.

[0171] If the downlink congestion information includes the identification information of routes contained in the downlink where the congested IAB node is congested, it is determined that the route corresponding to the identification information of the route contained in the downlink where the congested IAB node is congested is congested when it passes through the congested IAB node.

[0172] This application provides a congested IAB node. Figure 7 A schematic diagram of a congestion IAB provided in an embodiment of this application is shown below. Figure 7 As shown, the congestion IAB node provided in this application includes one or more processors 71 and a storage device 72; the processors 71 in the congestion IAB node can be one or more. Figure 7 Taking a processor 71 as an example; a storage device 72 is used to store one or more programs; the one or more programs are executed by the one or more processors 71, causing the one or more processors 71 to perform as described in this application. Figure 2 The method is described above.

[0173] The congested IAB node also includes: communication device 73, input device 74, and output device 75.

[0174] The processor 71, storage device 72, communication device 73, input device 74, and output device 75 in the congested IAB node can be connected via a bus or other means. Figure 7 Taking the example of a connection between China and Israel via a bus.

[0175] Input device 74 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 congested IAB node. Output device 75 may include display devices such as a display screen.

[0176] The communication device 73 may include a receiver and a transmitter. The communication device 73 is configured to perform information transmission and reception communication under the control of the processor 71. The information includes, but is not limited to, downlink congestion information.

[0177] Storage device 72, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the methods described in the embodiments of this application (e.g., reporting module 51 in a flow control device). Storage device 72 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required for at least one function; the data storage area may store data created based on the use of the congestion IAB node, etc. Furthermore, storage device 72 may include high-speed random access memory and may also include 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, storage device 72 may further include memory remotely located relative to processor 71, and these remote memories can be connected to the congestion IAB node via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0178] This application provides an IAB host. Figure 8 This is a schematic diagram of the structure of an IAB host provided in an embodiment of this application. Figure 8 As shown, the IAB host provided in this application includes one or more processors 81 and a storage device 82; the processors 81 in the IAB host can be one or more, Figure 8 Taking a processor 81 as an example; a storage device 82 is used to store one or more programs; the one or more programs are executed by the one or more processors 81, causing the one or more processors 81 to perform as described in this application. Figure 3 The method described.

[0179] The IAB host also includes: communication device 83, input device 84 and output device 85.

[0180] The processor 81, storage device 82, communication device 83, input device 84, and output device 85 in the IAB host can be connected via a bus or other means. Figure 8 Taking the example of a connection between China and Israel via a bus.

[0181] Input device 84 can be used to receive input numerical or character information, and to generate key signal inputs related to user settings and function control of the IAB host. Output device 85 may include display devices such as a display screen.

[0182] The communication device 83 may include a receiver and a transmitter. The communication device 83 is configured to perform information transmission and reception communication under the control of the processor 81. The information includes, but is not limited to, congestion information.

[0183] Storage device 82, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the methods described in the embodiments of this application (e.g., the receiving module 61, the lookup module 62, and the mitigation module 63 in the flow control device). Storage device 82 may include a program storage area and a data storage area, wherein the program storage area may store the operating system and at least one application program required for a function; the data storage area may store data created according to the use of the IAB host, etc. In addition, storage device 82 may include high-speed random access memory and may also include 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, storage device 82 may further include memory remotely located relative to processor 81, and these remote memories can be connected to the IAB host via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0184] This application also provides a storage medium storing a computer program that, when executed by a processor, implements any of the methods described in this application. Examples include methods applied to IAB nodes in a congestion-prone self-access backhaul link and methods applied to IAB hosts. The method applied to IAB nodes in a congestion-prone self-access backhaul link includes: reporting downlink congestion information to the IAB host via a first interface, the downlink congestion information being used by the IAB host to slow down the transmission of downlink data on the data radio bearer corresponding to the congested IAB node.

[0185] The method applied to the IAB host includes: receiving downlink congestion information through a first interface; searching for the identification information of the user equipment data radio bearer corresponding to the downlink congestion information in a mapping table; and slowing down the transmission of downlink data of the data radio bearer corresponding to the identification information of the user equipment data radio bearer.

[0186] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. For example, a computer-readable storage medium can be—but is not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable CD-ROM, optical storage device, magnetic storage device, or any suitable combination thereof. The computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0187] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in connection with an instruction execution system, apparatus, or device.

[0188] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, radio frequency (RF), etc., or any suitable combination thereof.

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

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

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

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

[0193] 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 on memory. 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 Video Disc (DVD) or Compact Disk (CD)), 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), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

[0194] 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 this application. Therefore, the proper scope of this application will be determined by the claims.

Claims

1. A flow control method, characterized in that, This applies to congested self-access backhaul (IAB) nodes, where downlink congestion occurs at the congested IAB node, including: The downlink congestion information is reported to the IAB host through the first interface. The downlink congestion information is used by the IAB host to look up the identification information of the user equipment data radio bearer according to the mapping relationship table, and to slow down the transmission of downlink data of the data radio bearer corresponding to the identification information of the user equipment data radio bearer. The IAB host includes a centralized unit control plane (CU-CP) and a centralized unit user plane (CU-UP). The mapping table is sent from the CU-CP of the IAB host to the CU-UP. The mapping table is used to determine the identification information of the user equipment data radio bearer corresponding to downlink congestion information. The downlink congestion information includes at least one of the following: The identification information of the backhaul link at the ingress of the congested IAB node; The amount of data required for the backhaul link at the congested IAB node ingress; The data rate required for the backhaul link at the congested IAB node ingress. Alternatively, the downlink congestion information may include at least one of the following: The identification information of the target IAB node indicates that the downlink between the target IAB node and the congested IAB node is congested. The amount of data required for the backhaul link at the congested IAB node ingress; The data rate required for the backhaul link at the congested IAB node ingress. Alternatively, the downlink congestion information may include at least one of the following: The identification information of the routes contained in the downlink where the congestion occurs at the congested IAB node; The amount of data required for the backhaul link at the congested IAB node ingress; The data rate required for the backhaul link at the congested IAB node ingress.

2. The method according to claim 1, characterized in that, The first interface includes: The General Data Radio System Pipeline Protocol (GTP-U) subheader on the F1 interface between the congested IAB node and the IAB host central control unit, wherein the GTP-U subheader contains a GTP-U pipe endpoint identifier that is either a pipe endpoint identifier allocated by the IAB host central control unit for the data radio bearer of the access user equipment of the congested IAB node or a pipe endpoint identifier allocated by the IAB host central control unit for the congested IAB node.

3. A flow control method, characterized in that, Applied to IAB hosts, including: Receive downlink congestion information through the first interface; Look up the identifier information of the user equipment data radio bearer corresponding to the downlink congestion information in the mapping table; Slow down the transmission of downlink data of the data radio bearer corresponding to the identification information of the user equipment data radio bearer; The downlink congestion information includes at least one of the following: identification information of the backhaul link of the congested IAB node ingress; the amount of data required for the backhaul link of the congested IAB node ingress; and the data rate required for the backhaul link of the congested IAB node ingress. Alternatively, the downlink congestion information may include at least one of the following: the identification information of the target IAB node, the downlink between the target IAB node and the congested IAB node being congested; the amount of data required for the backhaul link at the ingress of the congested IAB node; and the data rate required for the backhaul link at the ingress of the congested IAB node. Alternatively, the downlink congestion information may include at least one of the following: identification information of routes contained in the downlink of the congested IAB node; the amount of data required for the backhaul link of the congested IAB node ingress; and the data rate required for the backhaul link of the congested IAB node ingress. The IAB host includes a centralized unit control plane (CU-CP) and a centralized unit user plane (CU-UP). The mapping table is sent from the CU-CP of the IAB host to the CU-UP, and the mapping table is used to determine the identification information of the user equipment data radio bearer corresponding to downlink congestion information.

4. The method according to claim 3, characterized in that, The mapping table includes at least one of the following: The mapping relationship between the identification information of the backhaul link at the entrance of each IAB node in the IAB network and the identification information of the corresponding user equipment data radio bearer; The mapping relationship between the identification information of the backhaul link at the ingress of each IAB node in the IAB network and the identification information of the corresponding egress backhaul link, and the mapping relationship between the identification information of the backhaul link at the egress of the IAB host and the identification information of the corresponding user equipment data radio bearer.

5. The method according to claim 3, characterized in that, The mapping table includes at least one of the following: The mapping relationship between the transmission link between each IAB node and the next-hop IAB node in the IAB network and the identification information of the user equipment data radio bearer; The mapping relationship between the identification information of the backhaul link at the ingress of each IAB node in the IAB network and the identification information of the corresponding egress backhaul link, and the mapping relationship between the identification information of the backhaul link at the egress of the IAB host and the identification information of the corresponding user equipment data radio bearer.

6. The method according to claim 3, characterized in that, The mapping table includes a mapping relationship between routing identifiers and identification information of user data radio bearers in the IAB network. The routing identifier is the identification information of the route from the access user equipment to the IAB host in the IAB network.

7. The method according to claim 3, further comprising: If the downlink congestion information includes the identification information of the backhaul link at the ingress of the congested IAB node, it is determined that the egress link of the congested IAB node is congested. If the downlink congestion information includes the amount of data required for the backhaul link of the congested IAB node ingress, the amount of data to be sent to the backhaul link of the congested IAB node ingress is determined based on the amount of data required for the backhaul link of the congested IAB node ingress. If the downlink congestion information includes the data rate required for the backhaul link of the congested IAB node ingress, the data rate of the backhaul link of the congested IAB node ingress is determined based on the data rate required for the backhaul link of the congested IAB node ingress. If the downlink congestion information includes the identification information of the target IAB node, it is determined that the downlink link between the congested IAB node and the target IAB node is congested. If the downlink congestion information includes the identification information of routes contained in the downlink where the congested IAB node is congested, it is determined that the route corresponding to the identification information of the route contained in the downlink where the congested IAB node is congested is congested when it passes through the congested IAB node.

8. A flow control device, characterized in that, Integrated into a congested IAB node, where the downlink of the congested IAB node is congested, the device includes: The reporting module is configured to report downlink congestion information to the IAB host through a first interface. The downlink congestion information is used by the IAB host to look up the identification information of the user equipment data radio bearer according to the mapping relationship table, and to slow down the transmission of downlink data of the data radio bearer corresponding to the identification information of the user equipment data radio bearer. The IAB host includes a centralized unit control plane (CU-CP) and a centralized unit user plane (CU-UP). The mapping table is sent from the CU-CP of the IAB host to the CU-UP. The mapping table is used to determine the identification information of the user equipment data radio bearer corresponding to downlink congestion information. The downlink congestion information includes at least one of the following: The identification information of the backhaul link at the ingress of the congested IAB node; The amount of data required for the backhaul link at the congested IAB node ingress; The data rate required for the backhaul link at the congested IAB node ingress. Alternatively, the downlink congestion information may include at least one of the following: The identification information of the target IAB node indicates that the downlink between the target IAB node and the congested IAB node is congested. The amount of data required for the backhaul link at the congested IAB node ingress; The data rate required for the backhaul link at the congested IAB node ingress. Alternatively, the downlink congestion information may include at least one of the following: The identification information of the routes contained in the downlink where the congestion occurs at the congested IAB node; The amount of data required for the backhaul link at the congested IAB node ingress; The data rate required for the backhaul link at the congested IAB node ingress.

9. A flow control device, characterized in that, Integrated into the IAB host, including: The receiving module is configured to receive downlink congestion information through the first interface; The lookup module is configured to search for the identifier information of the user equipment data radio bearer corresponding to the downlink congestion information in the mapping relationship table; The mitigation module is configured to slow down the transmission of downlink data of the data radio bearer corresponding to the identification information of the user equipment data radio bearer; The downlink congestion information includes at least one of the following: The identification information of the backhaul link at the ingress of the congested IAB node; The amount of data required for the backhaul link at the congested IAB node ingress; The data rate required for the backhaul link at the congested IAB node ingress. Alternatively, the downlink congestion information may include at least one of the following: The identification information of the target IAB node indicates that the downlink between the target IAB node and the congested IAB node is congested. The amount of data required for the backhaul link at the congested IAB node ingress; The data rate required for the backhaul link at the congested IAB node ingress. Alternatively, the downlink congestion information may include at least one of the following: The identification information of the routes contained in the downlink where the congestion occurs at the congested IAB node; The amount of data required for the backhaul link at the congested IAB node ingress; The data rate required for the backhaul link at the congested IAB node ingress. The IAB host includes a centralized unit control plane (CU-CP) and a centralized unit user plane (CU-UP). The mapping table is sent from the CU-CP of the IAB host to the CU-UP, and the mapping table is used to determine the identification information of the user equipment data radio bearer corresponding to downlink congestion information.

10. A congested IAB node, characterized in that, The downlink of the congested IAB node is congested, including: One or more processors; Storage device for storing 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-2.

11. An IAB host, characterized in that, include: One or more processors; Storage device for storing 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 3-7.

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

Images