WO2020015572A1 - Downlink data transmission control method and system - Google Patents

Abstract

Provided are a downlink data transmission control method and a system. Said method comprises: if a first relay node satisfies a reporting trigger condition, the first relay node sending a request message or a downlink transmission state to an upper node of the first relay node; and the upper node adjusting, according to the request message or the downlink transmission state, downlink data sent to the first relay node.

Description

Control method and system for downlink data transmission

Cross-reference to related applications

This application claims the priority of Chinese Patent Application No. 201810803600.X filed in China on July 20, 2018, the entire contents of which are hereby incorporated by reference.

Technical field

The present disclosure relates to the field of communication technologies, and in particular, to a method and system for controlling downlink data transmission.

Background technique

The fifth generation (5th Generation, 5G) communication system introduces a relay architecture. In the relay architecture, the terminal accesses the anchor node through one or more relay nodes, such as: anchor base station (Donor, NB, DgNB), And in the relay architecture, the sending of downlink data is mainly controlled by the upper node. However, in actual applications, there may be sufficient resources between an upper node and its lower nodes, so that the upper node always sends data to the lower node, but at this time, it may appear that the lower node and its lower nodes (or Insufficient conditions such as insufficient resources between the terminals, or problems with the link cause the lower-level node to cache a large amount of data, and even the cache crashes or overflows, causing congestion in downlink data transmission.

Summary of the invention

The embodiments of the present disclosure provide a method and a system for controlling downlink data transmission to solve the problem of congestion in sending downlink data.

In order to achieve the above object, an embodiment of the present disclosure provides a method for controlling downlink data transmission, including:

If the first relay node meets a reporting trigger condition, the first relay node sends a request message or a downlink sending status to an upper node of the first relay node;

The upper node adjusts the downlink data sent to the first relay node according to the request message or the downlink sending status.

Optionally, the reporting trigger condition includes at least one of the following:

A downlink abnormality, a downlink scheduling abnormality, a downlink resource abnormality, a periodic trigger configuration, an available buffer abnormality, receiving a request message sent by a second relay node, and receiving a downlink sending status sent by the second relay node.

Optionally, the available cache exceptions include:

The number of available buffers is less than or equal to the preset number threshold; or

The available buffer ratio is less than or equal to the preset ratio threshold.

Optionally, the request message includes:

A rate limit request message, where the rate limit request message is used to request the upper node to reduce the rate of sending downlink data to the first relay node; or

The suspension sending request message is used to request the upper node to temporarily stop sending downlink data to the first relay node.

Optionally, the rate limit request message includes an identifier of the terminal, a data radio bearer (DRB) identifier of the terminal, and a downlink transmission rate, wherein the first relay node and the upper node There is a DRB corresponding to the terminal; or

The transmission suspension request message includes an identifier of a terminal and a DRB identifier of the terminal, wherein a DRB corresponding to the terminal exists between the first relay node and the upper node.

Optionally, the rate limit request message includes a downlink transmission rate of a Radio Link Control (RLC) channel, where the RLC channel exists between the first relay node and the superior node, and The RLC channel aggregates DRBs of multiple terminals, and the quality of service (QOS) attributes of the DRBs of the multiple terminals match; or

The suspension sending request message includes an identifier of an RLC channel, wherein the RLC channel exists between the first relay node and the superior node, the RLC channel aggregates DRBs of multiple terminals, and the multiple terminals The DROS matches the QOS attributes.

Optionally, the rate limit request message or the suspension of sending request message further includes an identifier of a target terminal and / or a DRB identifier of the target terminal, and the target terminal cannot normally send the first relay node. A terminal for downlink data; the method further includes:

The first relay node reconfigures a new RLC channel for the target terminal according to a configuration message sent by the anchor node.

Optionally, the method further includes:

If the downlink transmission of the first relay node returns to normal, the first relay node sends a downlink transmission request message to the upper node, so that the upper node continues to send downlink data to the first relay node, Or resume the rate of sending downlink data to the first relay node.

Optionally, the downlink sending status includes at least one of the following:

The number of available caches, the available cache ratio, and the highest Packet Data Convergence Protocol (PDCP) serial number (SN), where the highest PDCP is the highest PDCP that is successfully sent to the lower node or terminal in order. SN.

Optionally, if there is a second relay node between the first relay node and the terminal, if the first relay node meets a reporting trigger condition, the first relay node sends the first relay node to the first relay node. Before an upper node of a relay node sends a request message or a downlink sending status, the method further includes:

Receiving, by the first relay node, a request message or a downlink sending status sent by the second relay node, and reducing the rate of sending downlink data to the second relay node, or suspending the second relay node to the second relay node Send downlink data.

An embodiment of the present disclosure further provides a control system for downlink data transmission, including:

A first relay node, configured to: if the first relay node meets a reporting trigger condition, send a request message or a downlink sending status to an upper node of the first relay node;

The upper node is configured to adjust downlink data sent to the first relay node according to the request message or the downlink sending status.

Optionally, the reporting trigger condition includes at least one of the following:

A downlink abnormality, a downlink scheduling abnormality, a downlink resource abnormality, a periodic trigger configuration, an available buffer abnormality, receiving a request message sent by a second relay node, and receiving a downlink sending status sent by the second relay node.

Optionally, the available cache exceptions include:

The number of available buffers is less than or equal to the preset number threshold; or

The available buffer ratio is less than or equal to the preset ratio threshold.

Optionally, the request message includes:

A rate limit request message, where the rate limit request message is used to request the upper node to reduce the rate of sending downlink data to the first relay node; or

The suspension sending request message is used to request the upper node to temporarily stop sending downlink data to the first relay node.

Optionally, the rate limit request message includes an identifier of the terminal, a DRB identifier of the terminal, and a downlink transmission rate, wherein a DRB corresponding to the terminal exists between the first relay node and the superior node ;or

The transmission suspension request message includes an identifier of a terminal and a DRB identifier of the terminal, wherein a DRB corresponding to the terminal exists between the first relay node and the upper node.

Optionally, the rate limit request message includes a downlink transmission rate of an RLC channel, wherein the RLC channel exists between the first relay node and the superior node, and the RLC channel aggregates DRBs of multiple terminals , The QOS attributes of the DRBs of the plurality of terminals match; or

The suspension sending request message includes an identifier of an RLC channel, wherein the RLC channel exists between the first relay node and the superior node, the RLC channel aggregates DRBs of multiple terminals, and the multiple terminals The DROS matches the QOS attributes.

Optionally, the rate limit request message or the suspension of sending request message further includes an identifier of a target terminal and / or a DRB identifier of the target terminal, and the target terminal cannot normally send the first relay node. Terminal for downlink data;

The first relay node is further configured to reconfigure a new RLC channel for the target terminal according to a configuration message sent by the anchor node.

Optionally, the first relay node is further configured to send a downlink transmission request message to the upper node if the downlink transmission of the first relay node returns to normal, so that the upper node continues to send to the first node. The relay node sends downlink data, or resumes the rate of sending downlink data to the first relay node.

Optionally, the downlink sending status includes at least one of the following:

The number of available buffers, the ratio of available buffers, and the highest PDCP SN, where the highest PDCP SN is the highest PDCP SN that is successfully sent to the lower-level node or terminal in order.

Optionally, if there is a second relay node between the first relay node and the terminal, the first relay node is further configured to receive a request message or a downlink sending status sent by the second relay node, And reduce the rate of sending downlink data to the second relay node, or suspend sending downlink data to the second relay node.

An embodiment of the present disclosure further provides a node, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor, wherein the transceiver is configured to execute any of the foregoing. The steps performed by the first relay node in the method for controlling downlink data transmission according to the item.

An embodiment of the present disclosure further provides a node, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor, wherein the transceiver is configured to execute any of the foregoing. The steps performed by the superior relay node in the method for controlling downlink data transmission according to the item.

An embodiment of the present disclosure further provides a computer-readable storage medium having stored thereon a computer program, where the computer program is executed by a processor, and the first relay node in the control method for implementing any one of the foregoing downlink data transmissions. Or the steps performed by the superior node.

In the embodiment of the present disclosure, if the first relay node meets a reporting trigger condition, the first relay node sends a request message or a downlink sending status to an upper node of the first relay node; The request message or the downlink sending status adjusts downlink data sent to the first relay node. In this way, the upper node can adjust the downlink data according to the request message or the downlink sending status, to avoid congestion in sending the downlink data.

BRIEF DESCRIPTION OF THE DRAWINGS

1 is a schematic diagram of a network structure applicable to an embodiment of the present disclosure;

2 is a flowchart of a method for controlling downlink data transmission according to an embodiment of the present disclosure;

3 is a schematic diagram of a bearer provided by an embodiment of the present disclosure;

4 is another schematic diagram of a bearer provided by an embodiment of the present disclosure;

5 is a schematic diagram of downlink status feedback provided by an embodiment of the present disclosure;

6 is a structural diagram of a control system for downlink data transmission according to an embodiment of the present disclosure;

7 is a structural diagram of a node provided by an embodiment of the present disclosure;

8 is another structural diagram of a node provided by an embodiment of the present disclosure;

9 is another structural diagram of a node provided by an embodiment of the present disclosure;

10 is another structural diagram of a node provided by an embodiment of the present disclosure;

11 is another structural diagram of a node provided by an embodiment of the present disclosure;

12 is another structural diagram of a node provided by an embodiment of the present disclosure;

FIG. 13 is another structural diagram of a node provided by an embodiment of the present disclosure.

detailed description

In order to make the technical problems, technical solutions, and advantages of the present disclosure clearer, the following describes in detail with reference to the accompanying drawings and specific embodiments.

Referring to FIG. 1, FIG. 1 is a schematic diagram of an applicable network structure according to an embodiment of the present disclosure. As shown in FIG. 1, the terminal 11 includes at least one relay node 12 and an anchor node 13. The terminal 11 passes through at least one The relay node 12 accesses the anchor node 13. The terminal 11 may be a user terminal (User Equipment) or other terminal equipment, such as a mobile phone, a tablet computer, a laptop computer, and a personal digital assistant (PDA). 2. Terminal-side devices such as mobile Internet devices (Mobile Internet Devices, MIDs) or wearable devices (Wearable Devices). It should be noted that the specific types of terminals are not limited in the embodiments of the present disclosure. Taking the terminal 11 shown in FIG. 1 as an entity including Service Data Adaptation Protocol (SDAP), PDCP, RLC, and Media Access Control (MAC) as examples, the relay connected to the terminal 11 The node 12 includes a distributed unit (DU) and a mobile terminal (MT). Among them, the DU includes RLC and MAC and is responsible for communicating with the terminal 11. The MT includes an adaptation layer (Adapt), RLC And MAC, responsible for communicating with the superior node; and the relay node 12 connected between the relay node 12 and the anchor node 13 includes DU and MT, among which DU includes Adapt, RLC, and MAC, and is responsible for communicating with the lower node MT includes Adapt, RLC, and MAC, and is responsible for communicating with superior nodes. In addition, the relay node 12 may also be called an integrated access backhaul node (Integrated Access Backhaul node, IAB node). The anchor node 13 includes a DU and a Centralized Unit (CU). Among them, the DU includes Adapt, RLC, and MAC, and is responsible for communicating with lower-level nodes. The CU includes SDAP and PDCP, and is responsible for communicating with the terminal 11. In addition, the anchor node 13 may be an IAB-donor, an anchor base station (Donor NB, DgNB), or the like. It should be noted that the specific types of the relay node 12 and the anchor node 13 are not limited in the embodiment of the present disclosure, and the internal structures of the relay node 12 and the anchor node 13 are not limited to the structure shown in FIG. 1 FIG. 1 only illustrates that the terminal 11 accesses the anchor node 13 through the two relay nodes 12 as an example.

FIG. 2 is a flowchart of a method for controlling downlink data transmission according to an embodiment of the present disclosure. As shown in FIG. 2, the method includes the following steps:

201. If the first relay node meets a reporting trigger condition, the first relay node sends a request message or a downlink sending status to an upper node of the first relay node;

202. The upper node adjusts the downlink data sent to the first relay node according to the request message or the downlink sending status.

The first relay node may be a relay node connected to a terminal, or may be a relay node connected between another relay node and an anchor node, and the upper node may be a relay node or Anchor node.

The above-mentioned reporting trigger condition may be configured by the anchor node, for example, a periodic trigger configuration, or an event-based trigger configuration, or the above-mentioned reporting trigger configuration may be pre-defined by a protocol or pre-configured by the first relay node, for example: An abnormality occurs in downlink transmission or insufficient resources available in the downlink.

The above request message may be a request message requesting to reduce the rate of sending downlink data, or a request message requesting to suspend sending downlink data. The downlink transmission state may be a downlink transmission state of the first relay node, for example, a downlink transmission rate or a highest PDCP SN number of downlink transmission data.

After the upper-level node receives the request message or the downlink sending status, it may adjust the downlink data sent to the first relay node, for example, reduce the rate of sending the downlink data to the first relay node, Or suspend sending downlink data to the first relay node, etc. Of course, the downlink data here may refer to downlink data of a certain terminal or multiple terminals. The one or more terminals may be terminals that the first relay node cannot normally send downlink data, for example, a terminal with an abnormal link with the first relay node, or the first relay node cannot schedule downlink resources. Terminals, or terminals where a large amount of data is stored in the cache of the first relay node, and so on.

Through the above steps, it is possible to increase the control of the downlink transmission by the upper node through the request message or the downlink transmission state, thereby improving the effect of the downlink data control and avoiding the congestion of the downlink data transmission. It should be noted that, in the embodiments of the present disclosure, downlink data control may also be referred to as downlink flow control.

As an optional implementation manner, the reporting trigger condition includes at least one of the following:

A downlink abnormality, a downlink scheduling abnormality, a downlink resource abnormality, a periodic trigger configuration, an available buffer abnormality, receiving a request message sent by a second relay node, and receiving a downlink sending status sent by the second relay node.

The above-mentioned downlink abnormality may refer to a downlink failure, a poor downlink channel quality, or a low downlink transmission rate. In addition, the above-mentioned downlink may be a downlink between the first relay node and the terminal, or a downlink between the first relay node and a subordinate node thereof.

The foregoing downlink scheduling abnormality may be that there are too many terminals served by the first relay node, resulting in scheduling difficulties and a decrease in downlink rate.

The foregoing downlink resource abnormality may be insufficient downlink resources, and it is impossible to schedule sufficient resources for some terminals.

The above-mentioned periodic triggering configuration may be a periodic triggering condition configured by the anchor node, for example, sending a downlink sending status to a superior node every specific period of time.

The above available cache exceptions may include:

The number of available buffers is less than or equal to the preset number threshold; or

The available buffer ratio is less than or equal to the preset ratio threshold.

The preset number threshold and the preset ratio threshold (for example, 60% or 50%, etc.) may be configured by an anchor node or defined by a protocol. The above-mentioned available buffer quantity may be counted in units of bytes. For example, when the available buffer quantity of the first relay node is less than a specific number of bytes, a request message or a downlink sending status is sent to an upper node. Of course, the above number of available caches can also be understood as the cache is about to overflow.

The second relay node may be a lower node of the first relay node, for example, a relay node connected to a terminal. When the above-mentioned request message or downlink transmission status sent by the second relay node is received, it may indicate that the downlink transmission between the second relay node and the terminal is abnormal, or that the second relay node buffers an excessive amount, so that The upper node sends a request message or a downlink transmission state, so that the upper node adjusts the sending of the downlink data. It should be noted that, for the request message and the downlink sending status sent by the second relay node, refer to the request message and the downlink sending status in step 201, and details are not described herein.

As an optional implementation manner, the request message includes:

A rate limit request message, where the rate limit request message is used to request the upper node to reduce the rate of sending downlink data to the first relay node; or

The suspension sending request message is used to request the upper node to temporarily stop sending downlink data to the first relay node.

The rate limiting request message may include a rate limiting parameter, and the rate limiting parameter may include a restricted object, for example, at least one of an identifier of the terminal, a DRB identifier of the terminal, and a downlink transmission rate. Here, the terminal may be a terminal where the first relay node cannot normally send downlink data, for example, a terminal with an abnormal link with the first relay node, or a terminal where the first relay node cannot schedule downlink resources, or a large amount of data A terminal stored in a buffer of the first relay node, and the like. Or the above rate limiting parameter may include: a downlink transmission rate of the RLC channel or an identifier of the RLC channel.

In the same way, the sending suspension request message may also include the rate limiting parameter.

After receiving the rate limiting request message, the upper-level node may reduce the rate of sending downlink data to the first relay node. Of course, the reduction here may be reducing the rate of downlink data of the terminal corresponding to the rate limiting parameter. If the suspension sending request message is received, sending the downlink data to the first relay node may be suspended. Of course, the suspension here may be the suspension of sending the downlink data of the terminal corresponding to the above rate limiting parameter.

In an optional solution, the rate limit request message includes an identifier of a terminal, a data radio bearer DRB identifier of the terminal, and a downlink transmission rate, where the first relay node and the upper node exist and communicate with each other. The DRB corresponding to the terminal is described.

In this way, the rate limit request message may be used to make a higher-level node reduce a rate of sending downlink data of a specific terminal.

In another optional solution, the suspension sending request message includes an identifier of a terminal and a DRB identifier of the terminal, wherein a DRB corresponding to the terminal exists between the first relay node and the upper node.

In this way, the suspension sending request message may cause a higher-level node to suspend downlink data transmission of a specific terminal.

It should be noted that the DRB corresponding to the terminal between the first relay node and the upper node may be a one-to-one correspondence between the bearer of the terminal and the bearer between the relay nodes, and the bearer between the relay nodes. One-to-one correspondence with the bearer from the relay node to the anchor node. In other words, bearers are not aggregated in this scenario. For example, as shown in Figure 3, the terminal is a UE as an example, and UE1, UE2, and UE3 are connected to IAB1. DRB1 is used to carry Voice over Internet Protocol (VOIP) services, and DRB2 is used for web browsing ), And DRB3 is used to carry data streaming, and the data bearer between IAB1 and IAB2, and the data bearer between IAB2 and anchor node are unchanged. It should be noted that the data bearer between IAB1 and IAB2, and the data bearer between IAB2 and the anchor node may also be called RLC channels (RLC-Channel).

In practical applications, if the scheduling of the DRB1 bearer of Terminal 1 is difficult, such as the wireless link failure of Terminal 1, or the channel quality is low, or the number of IAB1 terminals causes scheduling difficulties and the rate decreases, DRB1 has been sending downstream data, so IAB1's buffer will overflow. In this way, the rate limiting parameter of the DRB1 of the terminal 1 can be feedbacked from the lower-level node IAB1 to the higher-level node IAB2 through the rate limiting request message. The rate limit parameter includes the terminal ID + terminal DRB ID + rate, thereby reducing the rate at which IAB2 sends downstream to IAB1. In addition, if the buffer of IAB2 is about to overflow, IAB2 sends feedback to the anchor node and modifies DRB1 of terminal 1.

The IAP1 can send the IAP2 to the IAB2 by sending the pause request message, and the pause request message includes the terminal ID + the terminal DRB ID. After receiving the message, IAB2 stops sending the bearer for the UE. In addition, if the memory of IAB2 is about to overflow, IAB2 then sends a request to Donor IAB node to suspend sending DR1 of UE1.

In another optional solution, the rate limit request message includes a downlink transmission rate of an RLC channel, wherein the RLC channel exists between the first relay node and the superior node, and the RLC channel aggregates multiple The DRBs of the terminals, and the QOS attributes of the DRBs of the multiple terminals match.

The RLC channel is an RLC channel that aggregates DRBs of terminals that the first relay node cannot normally send downlink data to. In addition, the matching of the QOS attributes of the DRBs of the multiple terminals may be that the QOS attributes of the DRBs of the multiple terminals are similar or the same.

In this embodiment, it is possible to reduce the rate at which a higher-level node sends downlink data on the RLC channel by using a downlink sending rate.

In another optional solution, the suspension sending request message includes an identifier of an RLC channel, wherein the RLC channel exists between the first relay node and the superior node, and the RLC channel aggregates multiple terminals. The DRB of the plurality of terminals matches the QOS attributes of the DRBs.

For the RLC channel herein, reference may be made to the description in the previous embodiment, and details are not described herein. In this embodiment, the identification of the RLC channel can be used to allow the upper node to suspend sending downlink data on the RLC channel.

It should be noted that the existence of the RLC channel (RLC Channel) between the first relay node and the superior node may be an RLC channel between the first relay node and the superior node that aggregates multiple terminals. For example, as shown in Figure 4, the terminal is a UE, and UE1, UE2, and UE3 are connected to IAB1. DRB1 is used to carry VOIP services, DRB2 is used for web browsing, and DRB3 is used. For carrying data streams, these DRBs are aggregated into one bearer on the link between IAB1 and IAB2, for example: RLC channel. Because the scheduling of the same RLC channel is the same, the flow control between IAB1-IAB2 and IAB2-anchor IAB can only be based on the control of the RLC channel. When the DRB1 of the terminal 1 is congested, the IAB1 cannot schedule sufficient resources to the DRB1 of the terminal 1 at this time, and at this time IAB2 is still sending downlink data to the IAB1, and at this time the IAB1 buffer will overflow.

And through the above-mentioned rate limiting request message, it is possible to implement that the lower-level node IAB1 feedbacks the rate-limiting parameters of the RLC Channel1 to the higher-level node IAB2. In order to reduce the rate of downlink sending of the entire RLC channel1 to IAB1. In addition, if the cache of IAB2 is about to overflow, IAB2 sends feedback to Donor IAB node and modifies RLC channel1.

And through the suspension sending request message, IAB1 can send a suspension sending request message to IAB2, and the suspension request message can include RLC Channel1. After receiving the message, IAB2 stops sending the RLC Channel1 for the UE. In addition, if the IAB2 cache is about to overflow, IAB2 sends a request to the Donor IAB node to suspend sending RLC Channel1.

It should be noted that, in the above two embodiments, the upper node is not limited to reduce the rate at which the upper node sends downlink data on the RLC channel, or suspend sending the downlink data on the RLC channel. Because the RLC channel may also include the DRB of the terminal where the first relay node can normally send downlink data, for example, the RLC channel aggregates the DRBs of terminal 1, terminal 2, and terminal 3, where the first relay node cannot normally Terminal 1 and terminal 2 send downlink data, but can send downlink data to terminal 3 normally. Then, in this case, in order to avoid DRB of other terminals and unable to send downlink data, or reduce the rate of sending downlink data, the first relay node may reconfigure the RLC channel for terminals that cannot normally send downlink data. For example, the rate limit request message or the suspension of sending request message further includes an identifier of a target terminal and / or a DRB identifier of the target terminal, and the target terminal cannot normally send downlink data for the first relay node. Terminal; the method further includes:

The first relay node reconfigures a new RLC channel for the target terminal according to a configuration message sent by the anchor node.

Wherein, reconfiguring a new RLC channel for the target terminal according to the configuration message sent by the anchor node may be reconfiguring a bearer mapping rule between the first relay node and a superior node according to the configuration message, and relaying the first relay The DRB of the target terminal where the node cannot normally send downlink data is remapped to a separate RLC channel, so as not to affect the terminal that normally sends downlink data, so as to improve the performance of the communication system.

In this embodiment, in the scenario of bearer aggregation, the bearers of different terminals with similar attributes are aggregated in an RLC channel, so a RLC channel transmission limitation (such as rate limit or stop sending) will cause Bearers of other terminals cannot send downlink. So this is unfair. In this scenario, the anchor IAB needs to reconfigure the mapping rules. As shown in FIG. 4, when the anchor IAB receives the rate limit request message (terminal ID + bearer ID) or suspends sending the request message (terminal ID + bearer ID), the anchor IAB reconfigures the bearers of IAB1 and IAB2. The mapping rule remaps bearer1 of terminal 1 and bearers of all other UEs that cannot send normally to a single RLC channel.

In the foregoing embodiment, as another optional solution, the method further includes:

If the downlink transmission of the first relay node returns to normal, the first relay node sends a downlink transmission request message to the upper node, so that the upper node continues to send downlink data to the first relay node, Or resume the rate of sending downlink data to the first relay node.

Wherein, the normal return of the downlink transmission of the first relay node may be that after the first relay node cannot normally send downlink data to some terminals, it may normally send uplink data to these terminals, for example, the downlink of the terminal resumes. Further, after the buffer of the first relay node is cleared, or is about to be cleared, the first relay node sends a downlink sending request message to the upper node.

For example, in the scenario shown in FIG. 3, when IAB1 can send downlink data to DRB1 of terminal 1, the buffer in IAB1 has been cleared, and IAB1 sends a continue sending request message to IAB2. At this time, IAB2 continues to send DRB1 of UE1. IAB2 also sends a Continue Send Request message to the anchor IAB, so that IAB2 can continue to send data packets to IAB1, and only IAB1 can send data packets to the terminal.

In the scenario shown in FIG. 4, when IAB1 can send downlink data to DRB1 of terminal 1, the buffer in IAB1 has been cleared, and IAB1 sends a request to continue sending to IAB2. The message contains RLC Channel1. At this time, IAB2 continues to send RLC Channel1 of UE1. IAB2 also sends a Continue Send Request message to Donor IAB, which contains RLC Channel1. In this way, IAB2 can continue to send data packets to IAB1, and only IAB1 can send data packets to the terminal.

In this embodiment, the communication performance of the communication system can be improved by using the foregoing downlink transmission request message.

As an optional implementation manner, the downlink sending status includes at least one of the following:

The number of available buffers, the ratio of available buffers, and the highest PDCP SN, where the highest PDCP SN is the highest PDCP SN that is successfully sent to the lower-level node or terminal in order.

The highest PDCP SN may be the highest PDCP SN in the data that the first relay node sends to the lower node or terminal in a preset order and successfully reaches the lower node or terminal.

When the upper node receives the above-mentioned downlink transmission state, it can adjust the transmission rate to the first relay node in a timely manner according to the content included in the downlink transmission state, so as to increase the control of the downlink data. For example, when the number of available buffers is relatively small, the downlink transmission rate can be reduced, or the transmission can be suspended, otherwise, the normal transmission rate can be guaranteed, or the transmission rate can be increased.

For example, as shown in FIG. 5, IAB2 sends a downlink data packet to IAB1, and IAB1 feeds back the downlink sending status to IAB2. This feedback status can be triggered in two ways:

1. Periodic triggering; the triggering period can be configured by Donor NB.

2. Event triggering; among them, the triggering condition can also be configured by Donor gNB, which can be as follows:

Threshold of the number of available buffers, such as the number of bytes

Available cache percentage threshold, such as 60%.

The message parameters of the downlink sending status feedback may include: available buffer, the percentage of available buffer, and the highest PDCP SN number that is successfully transmitted to the lower-level node. In this way, by feeding back the above message, the superior IAB node can adjust the sending speed in a timely manner by itself.

As an optional implementation manner, if there is a second relay node between the first relay node and the terminal, if the first relay node meets a reporting trigger condition, the first relay node Before the node sends a request message or a downlink transmission status to an upper node of the first relay node, the method further includes:

Receiving, by the first relay node, a request message or a downlink sending status sent by the second relay node, and reducing the rate of sending downlink data to the second relay node, or suspending the second relay node to the second relay node Send downlink data.

In this implementation manner, if a request message or a downlink sending status sent by a lower node is received, the rate of sending downlink data to the second relay node may be reduced, or the sending of downlink data to the second relay node may be suspended. To improve the control of downlink data. For the request message or downlink sending status sent by the second relay node, refer to the request message and downlink sending status in step 201, and details are not described herein. And if the request message or the downlink transmission status is received, it is confirmed that the request condition is met, and the trigger condition is reported, and the request message or the downlink transmission status is sent to an upper node of the first relay node, so that the upper node is In the downlink sending state, the downlink data sent to the first relay node is adjusted.

Of course, in this embodiment, the behavior of the first relay node may also refer to the behavior of IAB2 in the scenarios shown in FIG. 3 and FIG. 4, and details are not described herein.

It should be noted that various optional implementation modes described in the embodiments of the present disclosure can be implemented independently or in combination with each other, which is not limited.

In the embodiment of the present disclosure, if the first relay node meets a reporting trigger condition, the first relay node sends a request message or a downlink sending status to an upper node of the first relay node, so that the upper node pairs And adjusting the downlink data sent to the first relay node. In this way, the upper node can adjust the downlink data according to the request message or the downlink sending status, to avoid congestion in sending the downlink data.

Please refer to FIG. 6, which is a structural diagram of a control system for downlink data transmission according to an embodiment of the present disclosure. As shown in FIG. 6, it includes a first relay node 601 and an upper node 602.

The first relay node 601 is configured to send a request message or a downlink sending status to an upper node of the first relay node if the first relay node meets a reporting trigger condition.

The upper node 602 is configured to adjust downlink data sent to the first relay node according to the request message or the downlink sending status.

Optionally, the reporting trigger condition includes at least one of the following:

A downlink abnormality, a downlink scheduling abnormality, a downlink resource abnormality, a periodic trigger configuration, an available buffer abnormality, receiving a request message sent by a second relay node, and receiving a downlink sending status sent by the second relay node.

Optionally, the available cache exceptions include:

The number of available buffers is less than or equal to the preset number threshold; or

The available buffer ratio is less than or equal to the preset ratio threshold.

Optionally, the request message includes:

A rate limit request message, where the rate limit request message is used to request the upper node to reduce the rate of sending downlink data to the first relay node; or

The suspension sending request message is used to request the upper node to temporarily stop sending downlink data to the first relay node.

Optionally, the rate limit request message includes an identifier of the terminal, a DRB identifier of the terminal, and a downlink transmission rate, and there is a correspondence between the first relay node 601 and the upper node 602 corresponding to the terminal. DRB; or

The transmission suspension request message includes an identifier of the terminal and a DRB identifier of the terminal, wherein a DRB corresponding to the terminal exists between the first relay node 601 and the upper node 602.

Optionally, the rate limit request message includes a downlink transmission rate of an RLC channel, wherein the RLC channel exists between the first relay node 601 and the superior node 602, and the RLC channel aggregates multiple terminals The DRB of the plurality of terminals matches the QOS attributes of the DRBs; or

The transmission suspension request message includes an identifier of an RLC channel, wherein the RLC channel exists between the first relay node 601 and the superior node 602, and the RLC channel aggregates DRBs of multiple terminals, and the multiple The QOS attributes of the DRB of each terminal match.

Optionally, the rate limit request message or the suspension of sending request message further includes an identifier of a target terminal and / or a DRB identifier of the target terminal, and the target terminal cannot normally send the first relay node. Terminal for downlink data;

The first relay node 601 is further configured to reconfigure a new RLC channel for the target terminal according to a configuration message sent by the anchor node.

Optionally, the first relay node 601 is further configured to send a downlink transmission request message to the upper node if the downlink transmission of the first relay node returns to normal, so that the upper node continues to send to the first node. A relay node sends downlink data, or resumes the rate of sending downlink data to the first relay node.

Optionally, the downlink sending status includes at least one of the following:

The number of available buffers, the ratio of available buffers, and the highest PDCP SN, where the highest PDCP SN is the highest PDCP SN that is successfully sent to the lower-level node or terminal in order.

Optionally, if there is a second relay node between the first relay node 601 and the terminal, the first relay node is further configured to receive a request message or a downlink transmission status sent by the second relay node. And reduce the rate of sending downlink data to the second relay node, or suspend sending downlink data to the second relay node.

It should be noted that this embodiment is a system embodiment corresponding to the embodiment shown in FIG. 2. For specific implementation, refer to the related description of the embodiment shown in FIG. 2. In order to avoid repetitive description, this embodiment No further details are needed, and the same beneficial effects can be achieved.

Please refer to FIG. 7, which is a structural diagram of a node provided by an embodiment of the present disclosure. The node is a first relay node. As shown in FIG. 7, the node 700 includes:

A first sending module 701, configured to: if the first relay node meets a reporting trigger condition, send a request message or a downlink sending status to an upper node of the first relay node, so that the upper node is opposite to the first node; The downlink data sent by the first relay node is adjusted.

Optionally, the reporting trigger condition includes at least one of the following:

A downlink abnormality, a downlink scheduling abnormality, a downlink resource abnormality, a periodic trigger configuration, an available buffer abnormality, receiving a request message sent by a second relay node, and receiving a downlink sending status sent by the second relay node.

Optionally, the available cache exceptions include:

The number of available buffers is less than or equal to the preset number threshold; or

The available buffer ratio is less than or equal to the preset ratio threshold.

Optionally, the request message includes:

A rate limit request message, where the rate limit request message is used to request the upper node to reduce the rate of sending downlink data to the first relay node; or

The suspension sending request message is used to request the upper node to temporarily stop sending downlink data to the first relay node.

Optionally, the rate limit request message includes an identifier of the terminal, a data radio bearer DRB identifier of the terminal, and a downlink transmission rate, wherein the first relay node and the upper node are connected to the terminal. The corresponding DRB; or

The transmission suspension request message includes an identifier of a terminal and a DRB identifier of the terminal, wherein a DRB corresponding to the terminal exists between the first relay node and the upper node.

Optionally, the rate limit request message includes a downlink transmission rate of a radio link control RLC channel, wherein the RLC channel exists between the first relay node and the superior node, and the RLC channel aggregates multiple The DRBs of the terminals, and the quality of service QOS attributes of the DRBs of the multiple terminals match; or

The suspension sending request message includes an identifier of an RLC channel, wherein the RLC channel exists between the first relay node and the superior node, the RLC channel aggregates DRBs of multiple terminals, and the multiple terminals The DROS matches the QOS attributes.

Optionally, the rate limit request message or the suspension of sending request message further includes an identifier of a target terminal and / or a DRB identifier of the target terminal, and the target terminal cannot normally send the first relay node. A terminal for downlink data; as shown in FIG. 8, the node 700 further includes:

A configuration module 702 is configured to reconfigure a new RLC channel for the target terminal according to a configuration message sent by the anchor node.

Optionally, as shown in FIG. 9, the node 700 further includes:

The second sending module 703 is configured to send a downlink sending request message to the upper node if the downlink sending of the first relay node returns to normal, so that the upper node continues to send downlink data to the first relay node. Or resume the rate of sending downlink data to the first relay node.

Optionally, the downlink sending status includes at least one of the following:

The number of available buffers, the ratio of available buffers, and the highest PDCP SN, where the highest PDCP SN is the highest PDCP SN that is successfully sent to the lower-level node or terminal in order.

Optionally, if there is a second relay node between the first relay node and the terminal, as shown in FIG. 10, the node 700 further includes:

A processing module 704, configured to receive a request message or a downlink sending status sent by the second relay node, and reduce a rate of sending downlink data to the second relay node, or suspend sending to the second relay node Downstream data.

It should be noted that this embodiment is an implementation manner of the first relay node corresponding to the embodiment shown in FIG. 2. For a specific implementation manner, refer to the related description of the embodiment shown in FIG. 2. In order to avoid repetition, It is noted that this embodiment will not repeat the details and can also achieve the same beneficial effects.

Please refer to FIG. 11, which is another structural diagram of a node provided by an embodiment of the present disclosure. The node is an upper node. As shown in FIG. 11, the node 1100 includes:

The receiving module 1101 is configured to receive a request message or a downlink sending status sent by a first relay node;

The adjusting module 1102 is configured to adjust the downlink data sent to the first relay node according to the request message or the downlink sending status.

Optionally, the request message includes:

A rate limit request message, where the rate limit request message is used to request the upper node to reduce the rate of sending downlink data to the first relay node; or

The suspension sending request message is used to request the upper node to temporarily stop sending downlink data to the first relay node.

Optionally, the rate limit request message includes an identifier of the terminal, a data radio bearer DRB identifier of the terminal, and a downlink transmission rate, wherein the first relay node and the upper node are connected to the terminal. The corresponding DRB; or

The transmission suspension request message includes an identifier of a terminal and a DRB identifier of the terminal, wherein a DRB corresponding to the terminal exists between the first relay node and the upper node.

Optionally, the rate limit request message includes a downlink transmission rate of a radio link control RLC channel, wherein the RLC channel exists between the first relay node and the superior node, and the RLC channel aggregates multiple The DRBs of the terminals, and the quality of service QOS attributes of the DRBs of the multiple terminals match; or

The suspension sending request message includes an identifier of an RLC channel, wherein the RLC channel exists between the first relay node and the superior node, the RLC channel aggregates DRBs of multiple terminals, and the multiple terminals The DROS matches the QOS attributes.

Optionally, the downlink sending status includes at least one of the following:

The number of available buffers, the ratio of available buffers, and the highest PDCP sequence number SN that were successfully sent to the lower node or terminal in order.

It should be noted that this embodiment is an implementation manner of a higher-level node corresponding to the embodiment shown in FIG. 2. For a specific implementation manner, refer to a related description of the embodiment shown in FIG. 2. In order to avoid repetitive description, this embodiment The embodiment is not described repeatedly, and the same beneficial effects can also be achieved.

Please refer to FIG. 12. FIG. 12 is another structural diagram of a node provided by an embodiment of the present disclosure. The node is a first relay node and includes a transceiver 1210, a memory 1220, a processor 1200, and a memory 1220. A program that can run on the processor 1200,

The transceiver 1210 is configured to: if the first relay node meets a reporting trigger condition, send a request message or a downlink sending status to an upper node of the first relay node, so that the upper node is opposite to the The downlink data sent by the first relay node is adjusted.

The transceiver 1210 may be used to receive and send data under the control of the processor 1200.

In FIG. 12, the bus architecture may include any number of interconnected buses and bridges, and one or more processors specifically represented by the processor 1200 and various circuits of the memory represented by the memory 1220 are linked together. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, so they are not described further herein. The bus interface provides an interface. The transceiver 1210 may be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.

The processor 1200 is responsible for managing the bus architecture and general processing, and the memory 1220 may store data used by the processor 1200 when performing operations.

It should be noted that the memory 1220 is not limited to only the first relay node, and the memory 1220 and the processor 1200 may be separated in different geographical locations.

Optionally, the reporting trigger condition includes at least one of the following:

A downlink abnormality, a downlink scheduling abnormality, a downlink resource abnormality, a periodic trigger configuration, an available buffer abnormality, receiving a request message sent by a second relay node, and receiving a downlink sending status sent by the second relay node.

Optionally, the available cache exceptions include:

The number of available buffers is less than or equal to the preset number threshold; or

The available buffer ratio is less than or equal to the preset ratio threshold.

Optionally, the request message includes:

A rate limit request message, where the rate limit request message is used to request the upper node to reduce the rate of sending downlink data to the first relay node; or

The suspension sending request message is used to request the upper node to temporarily stop sending downlink data to the first relay node.

Optionally, the rate limit request message includes an identifier of the terminal, a DRB identifier of the terminal, and a downlink transmission rate, wherein a DRB corresponding to the terminal exists between the first relay node and the superior node ;or

The transmission suspension request message includes an identifier of a terminal and a DRB identifier of the terminal, wherein a DRB corresponding to the terminal exists between the first relay node and the upper node.

Optionally, the rate limit request message includes a downlink transmission rate of an RLC channel, wherein the RLC channel exists between the first relay node and the superior node, and the RLC channel aggregates DRBs of multiple terminals , The QOS attributes of the DRBs of the plurality of terminals match; or

The suspension sending request message includes an identifier of an RLC channel, wherein the RLC channel exists between the first relay node and the superior node, the RLC channel aggregates DRBs of multiple terminals, and the multiple terminals The DROS matches the QOS attributes.

Optionally, the rate limit request message or the suspension of sending request message further includes an identifier of a target terminal and / or a DRB identifier of the target terminal, and the target terminal cannot normally send the first relay node. A terminal for downlink data; the transceiver 1210 is further configured to:

Re-configure a new RLC channel for the target terminal according to a configuration message sent by the anchor node.

Optionally, the transceiver is further configured to:

If the downlink transmission of the first relay node returns to normal, sending a downlink transmission request message to the upper node, so that the upper node continues to send downlink data to the first relay node, or resumes sending to the first node. The rate at which the relay node sends downlink data.

Optionally, the downlink sending status includes at least one of the following:

The number of available buffers, the ratio of available buffers, and the highest PDCP SN, where the highest PDCP SN is the highest PDCP SN that is successfully sent to the lower-level node or terminal in order.

Optionally, if there is a second relay node between the first relay node and the terminal, if the first relay node meets a reporting trigger condition, the first relay node sends the first relay node to the first relay node. Before an upper node of a relay node sends a request message or a downlink sending status, the transceiver 1210 is further configured to:

Receiving a request message or a downlink sending status sent by the second relay node, and reducing the rate of sending downlink data to the second relay node, or suspending sending downlink data to the second relay node.

It should be noted that the first relay node in this embodiment may be the first relay node in any of the method embodiments in the embodiments of the present disclosure, and the first relay node in the method embodiments in the embodiments of the present disclosure Any implementation manner of the method can be implemented by the foregoing first relay node in this embodiment, and the same beneficial effects are achieved, and details are not described herein again.

Please refer to FIG. 13, which is another structural diagram of a node provided by an embodiment of the present disclosure. As shown in FIG. 13, the node is an upper node and includes a transceiver 1310, a memory 1320, a processor 1300, and a storage node. A program on the memory 1320 and executable on the processor, wherein:

The transceiver 1310 is configured to receive a request message or a downlink sending status sent by a first relay node; and perform downlink data sent to the first relay node according to the request message or the downlink sending status. Adjustment;

or,

The transceiver 1310 is configured to receive a request message or a downlink transmission status sent by a first relay node;

The processor 1300 is configured to read a program in the memory 1320 and execute the following processes:

And adjusting the downlink data sent to the first relay node according to the request message or the downlink sending status.

Optionally, the request message includes:

A rate limit request message, where the rate limit request message is used to request the upper node to reduce the rate of sending downlink data to the first relay node; or

The suspension sending request message is used to request the upper node to temporarily stop sending downlink data to the first relay node.

Optionally, the rate limit request message includes an identifier of the terminal, a DRB identifier of the terminal, and a downlink transmission rate, wherein a DRB corresponding to the terminal exists between the first relay node and the superior node ;or

The suspension sending request message includes an identifier of the terminal and a DRB identifier of the terminal, wherein a DRB corresponding to the terminal exists between the first relay node and the upper node.

Optionally, the rate limit request message includes a downlink transmission rate of an RLC channel, wherein the RLC channel exists between the first relay node and the superior node, and the RLC channel aggregates DRBs of multiple terminals , The QOS attributes of the DRBs of the plurality of terminals match; or

The suspension sending request message includes an identifier of an RLC channel, wherein the RLC channel exists between the first relay node and the superior node, the RLC channel aggregates DRBs of multiple terminals, and the multiple terminals The DROS matches the QOS attributes.

Optionally, the rate limit request message or the suspension of sending request message further includes an identifier of a target terminal and / or a DRB identifier of the target terminal, and the target terminal cannot normally send downlink information for the first relay node. Data terminal; the transceiver 1310 is further configured to:

If the upper node is an anchor node, sending a configuration message to the first relay node, so that the first relay node reconfigures a new RLC channel for the target terminal.

Optionally, the transceiver is further configured to:

Receive a downlink transmission request message sent by the first relay node, and continue to send downlink data to the first relay node according to the downlink transmission request message, or resume sending downlink data to the first relay node s speed.

Optionally, the downlink sending status includes at least one of the following:

The number of available buffers, the ratio of available buffers, and the highest PDCP SN, where the highest PDCP SN is the highest PDCP SN that is successfully sent to the lower-level node or terminal in order.

It should be noted that the above-mentioned upper node in this embodiment may be an upper node of any implementation in the method embodiment in this embodiment of the disclosure, and any implementation of the upper node in the method embodiment in this embodiment of the disclosure may be implemented by this The implementation of the above-mentioned upper node in the example, and the same beneficial effects are achieved, will not be repeated here.

An embodiment of the present disclosure also provides a computer-readable storage medium having stored thereon a computer program, which when executed by a processor, implements a method for controlling downlink data transmission on a first relay node side provided by an embodiment of the present disclosure. Step, or when the program is executed by a processor, the steps in the method for controlling downlink data transmission on the upper node side provided by the embodiment of the present disclosure are implemented.

In the several embodiments provided in this application, it should be understood that the disclosed methods and devices may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.

In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may be separately physically included, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware, or in the form of hardware plus software functional units.

The above integrated unit implemented in the form of a software functional unit may be stored in a computer-readable storage medium. The above software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute a part of the method for processing an information data block according to the embodiments of the present disclosure step. The aforementioned storage media include: U disks, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks or compact discs, and other media that can store program codes .

The above is an optional implementation of the present disclosure. It should be noted that, for those of ordinary skill in the art, without departing from the principles described in the present disclosure, several improvements and retouches can be made. These improvements and retouches It should also be regarded as the scope of protection of this disclosure.

Claims (23)

A method for controlling downlink data transmission includes: If the first relay node meets a reporting trigger condition, the first relay node sends a request message or a downlink sending status to an upper node of the first relay node; The upper node adjusts the downlink data sent to the first relay node according to the request message or the downlink sending status. The method according to claim 1, wherein the reporting trigger condition comprises at least one of the following: A downlink abnormality, a downlink scheduling abnormality, a downlink resource abnormality, a periodic trigger configuration, an available buffer abnormality, receiving a request message sent by a second relay node, and receiving a downlink sending status sent by the second relay node. The method of claim 2, wherein the available cache exception comprises: The number of available buffers is less than or equal to the preset number threshold; or The available buffer ratio is less than or equal to the preset ratio threshold. The method of claim 1, wherein the request message comprises: A rate limit request message, where the rate limit request message is used to request the upper node to reduce the rate of sending downlink data to the first relay node; or The suspension sending request message is used to request the upper node to temporarily stop sending downlink data to the first relay node. The method according to claim 4, wherein the rate limit request message includes an identifier of a terminal, a data radio bearer DRB identifier of the terminal, and a downlink transmission rate, wherein the first relay node and the upper node There is a DRB corresponding to the terminal; or The transmission suspension request message includes an identifier of a terminal and a DRB identifier of the terminal, wherein a DRB corresponding to the terminal exists between the first relay node and the upper node. The method according to claim 4, wherein the rate limit request message includes a downlink transmission rate of a radio link control RLC channel, and wherein the RLC channel exists between the first relay node and the upper node The RLC channel aggregates DRBs of multiple terminals, and the quality of service QOS attributes of the DRBs of the multiple terminals match; or The suspension sending request message includes an identifier of an RLC channel, wherein the RLC channel exists between the first relay node and the superior node, the RLC channel aggregates DRBs of multiple terminals, and the multiple terminals The DROS matches the QOS attributes. The method according to claim 6, wherein the rate limit request message or the pause sending request message further comprises: an identifier of a target terminal and / or a DRB identifier of the target terminal, and the target terminal is the first A terminal where a relay node cannot normally send downlink data; the method further includes: The first relay node reconfigures a new RLC channel for the target terminal according to a configuration message sent by the anchor node. The method according to any one of claims 4 to 7, further comprising: If the downlink transmission of the first relay node returns to normal, the first relay node sends a downlink transmission request message to the upper node, so that the upper node continues to send downlink data to the first relay node, Or resume the rate of sending downlink data to the first relay node. The method according to any one of claims 1 to 3, wherein the downlink sending status includes at least one of the following: The number of available buffers, the ratio of available buffers, and the highest packet data aggregation protocol PDCP sequence number SN, where the highest PDCP SN is the highest PDCP SN that is successfully sent to the lower node or terminal in order. The method according to any one of claims 1 to 7, wherein if there is a second relay node between the first relay node and the terminal, the if the first relay node meets a reporting trigger condition , Before the first relay node sends a request message or a downlink transmission status to an upper node of the first relay node, the method further includes: Receiving, by the first relay node, a request message or a downlink sending status sent by the second relay node, and reducing the rate of sending downlink data to the second relay node, or suspending the second relay node to the second relay node Send downlink data. A control system for downlink data transmission includes: A first relay node, configured to: if the first relay node meets a reporting trigger condition, send a request message or a downlink sending status to an upper node of the first relay node; The upper node is configured to adjust the downlink data sent to the first relay node according to the request message or the downlink sending status. The system according to claim 11, wherein the reporting trigger condition comprises at least one of the following: A downlink abnormality, a downlink scheduling abnormality, a downlink resource abnormality, a periodic trigger configuration, an available buffer abnormality, receiving a request message sent by a second relay node, and receiving a downlink sending status sent by the second relay node. The system of claim 12, wherein the available cache exceptions include: The number of available buffers is less than or equal to the preset number threshold; or The available buffer ratio is less than or equal to the preset ratio threshold. The system of claim 11, wherein the request message comprises: A rate limit request message, where the rate limit request message is used to request the upper node to reduce the rate of sending downlink data to the first relay node; or The suspension sending request message is used to request the upper node to temporarily stop sending downlink data to the first relay node. The system according to claim 14, wherein the rate limit request message includes an identity of a terminal, a DRB identity of the terminal, and a downlink transmission rate, and wherein the first relay node and the upper node exist A DRB corresponding to the terminal; or The transmission suspension request message includes an identifier of a terminal and a DRB identifier of the terminal, wherein a DRB corresponding to the terminal exists between the first relay node and the upper node. The system according to claim 14, wherein the rate limit request message includes a downlink transmission rate of an RLC channel, wherein the RLC channel exists between the first relay node and the superior node, and the RLC Channel aggregation of DRBs of multiple terminals whose QOS attributes match; or The suspension sending request message includes an identifier of an RLC channel, wherein the RLC channel exists between the first relay node and the superior node, the RLC channel aggregates DRBs of multiple terminals, and the multiple terminals The DROS matches the QOS attributes. The system according to claim 16, wherein the rate limit request message or the pause sending request message further comprises: an identifier of a target terminal and / or a DRB identifier of the target terminal, and the target terminal is the first A terminal where a relay node cannot normally send downlink data; The first relay node is further configured to reconfigure a new RLC channel for the target terminal according to a configuration message sent by the anchor node. The system according to any one of claims 14 to 17, wherein the first relay node is further configured to send a downlink transmission request to the upper node if the downlink transmission of the first relay node returns to normal. Message, so that the upper node continues to send downlink data to the first relay node, or resumes the rate of sending downlink data to the first relay node. The system according to any one of claims 11 to 13, wherein the downlink transmission status includes at least one of the following: The number of available buffers, the ratio of available buffers, and the highest PDCP SN, where the highest PDCP SN is the highest PDCP SN that is successfully sent to the lower-level node or terminal in order. The system according to any one of claims 11 to 17, wherein if there is a second relay node between the first relay node and the terminal, the first relay node is further configured to receive the first relay node. The request message or downlink sending status sent by the two relay nodes, and the rate of sending downlink data to the second relay node is reduced, or sending the downlink data to the second relay node is suspended. A node includes: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor, wherein the transceiver is configured to execute any one of claims 1 to 10 The steps performed by the first relay node in the method for controlling downlink data transmission. A node includes: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor, wherein the transceiver is configured to execute any one of claims 1 to 10 The steps performed by the superior relay node in the method for controlling downlink data transmission. A computer-readable storage medium having stored thereon a computer program, wherein when the computer program is executed by a processor, the first relay node or the first relay node in the method for controlling downlink data transmission according to any one of claims 1 to 10 Describe the steps performed by the superior node.

Images