Signal transmission / reception method, device, and communication system
By sending congestion reports to the IAB-donor CU, the IAB node's load status is indicated, facilitating control plane-based methods that alleviate long-term congestion and optimize network performance.
Patent Information
- Application Number
- JP2023540638
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-01-13
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2041-01-13
AI Technical Summary
Congestion occurs in IAB nodes due to mismatched ingress and egress data rates, and existing congestion mitigation methods are inadequate in addressing long-term congestion and uplink congestion.
An IAB node sends a congestion report message to a donor central unit (IAB-donor CU) indicating the load status of its communication link, allowing the CU to implement control plane-based methods for congestion alleviation, including routing reconfiguration and backhaul radio link control.
The solution effectively alleviates long-term data congestion, reduces data loss, and optimizes network performance by enabling dynamic resource management and reallocation.
Smart Images

Figure 0007589820000002 
Figure 0007589820000003 
Figure 0007589820000004
Abstract
Description
[Technical field]
[0001] The present invention relates to the technical field of communications. [Background technology]
[0002] In the next generation radio access network (NG-RAN), the IAB (Integrated access and backhaul) can realize the function of radio relay. The IAB node (IAB-node) supports access and backhaul through New Radio (NR). The NR backhaul terminal point on the network side is called IAB-donor, which represents one network device (e.g., gNB) that supports the IAB function.
[0003] An IAB node may be connected to an IAB-donor through one or more hops. These multi-hop connections may form a Directed Acyclic Graph (DAG) topology with the IAB-donor as the root node. The IAB-donor is responsible for performing centralized resource management, topology management, and routing management in the IAB network topology.
[0004] The IAB-node supports the functionality of a gNB-DU (distributed unit), and the IAB-node DU is also referred to as the IAB-DU, which is the termination point of the radio access (NR access) interface to the user equipment (UE) and the next hop IAB-node, and is also the termination point of the F1 protocol to the gNB-CU (central unit) on the IAB-donor. The IAB-DU can serve normal UEs and IAB child nodes.
[0005] In addition to the gNB-DU functions, the IAB-node also supports some UE functions, which are called IAB-MT (Mobile Termination), and the IAB-MT includes, for example, physical layer, layer 2, RRC and NAS functions, which allow it to connect to a gNB-DU of another IAB-node or IAB-donor, to a gNB-CU on the IAB-donor, and to connect to the core network. The IAB-MT can support, for example, UE physical layer, access stratum (AS), radio resource control (RRC) layer and non-access stratum (NAS) layer functions, which allow it to connect to an IAB parent node.
[0006] Figure 1 is a diagram showing an IAB topology. As shown in Figure 1, in the IAB topology 10, an IAB-node 100 includes an IAB-MT functional unit 101 and an IAB-DU functional unit 102, an adjacent node on the interface of the IAB-DU functional unit 102 is called a child node, for example, the child nodes 201, 202, and 203 shown in Figure 1, and the IAB-DU functional unit 102 and the child nodes 201, 202, and 203 can communicate with each other via an air interface (Uu), and an adjacent node on the interface of the IAB-MT functional unit 101 is called a parent node, for example, the parent nodes 301 and 302 shown in Figure 1, and the IAB-MT functional unit 101 and the parent nodes 301 and 302 can communicate with each other via an air interface (Uu).
[0007] 1, the direction from the IAB-node 100 to the child nodes 201, 202, 203 is referred to as the downstream direction, and the direction from the IAB-node 100 to the parent nodes 301, 302 is referred to as the upstream direction. An IAB-donor (not shown) performs centralized resource, topology, and routing management for the IAB topology 10.
[0008] It should be noted that the introduction of the above background art is intended to clearly and completely explain the technical solutions of the present invention, and to facilitate understanding thereof by those skilled in the art, and these technical solutions are described in the background art of the present invention, and therefore should not be construed as being known to those skilled in the art. Summary of the Invention [Problem to be solved by the invention]
[0009] Congestion can occur when there is a mismatch between the ingress and egress data rates of an IAB node.
[0010] The inventors of the present invention have found that the congestion mitigation methods in the prior art have some limitations, such as being unable to solve long-term congestion problems, being limited in the specific congestion mitigation methods that can be selected, and being unable to mitigate uplink congestion.
[0011] In view of at least one of the above problems, embodiments of the present invention provide a signal transmission / reception method, apparatus and communication system, in which an IAB node (IAB-node) sends a congestion report message to a donor central unit (IAB-donor CU), so that the donor central unit (IAB-donor CU) can adopt a method based on a control plane (CP) to alleviate congestion of the IAB-node. [Means for solving the problem]
[0012] According to one aspect of an embodiment of the present invention, there is provided a signal transmitting / receiving device applied to an IAB node, comprising: a first transceiver unit for transmitting a congestion report message to a donor central unit (IAB-donor CU) of the IAB node; The congestion report message is used to indicate the load condition of the communication link of the IAB node.
[0013] According to another aspect of the embodiment of the present invention, there is provided a signal transmitting / receiving device adapted for a donor central unit (IAB-donor CU), comprising: a third transceiver unit for receiving a congestion report message transmitted by an IAB node; The congestion report message is used to indicate the load condition of the communication link of the IAB node.
[0014] According to another aspect of an embodiment of the present invention, there is provided a method for transmitting and receiving a signal, the method comprising: an IAB node (IAB) sending a congestion report message to a donor central unit (IAB-donor CU) of the IAB node; The congestion report message is used to indicate the load condition of the communication link of the IAB node.
[0015] According to another aspect of an embodiment of the present invention, there is provided a method for transmitting and receiving a signal, the method comprising: A donor central unit (IAB-donor CU) receives a congestion report message transmitted by an IAB node (IAB); The congestion report message is used to indicate the load condition of the communication link of the IAB node. Effect of the Invention
[0016] The advantageous effects of the embodiment of the present invention are at least as follows: an IAB-node sends a congestion report message to an IAB-donor CU, so that the IAB-donor CU can adopt a CP-based method to alleviate congestion of the IAB-node.
[0017] Specific embodiments of the present invention are disclosed in detail below with reference to the following description and drawings, which show how the principles of the present invention may be employed, but are not limited in scope to these embodiments, which may include various changes, modifications, and alternatives within the scope of the appended claims.
[0018] Additionally, features described and / or illustrated in one embodiment may be used in the same or similar manner in one or more other embodiments, may be combined with features in the other embodiments, or may be substituted for features in the other embodiments.
[0019] It should be noted that terms such as "comprise / have" when used in this specification refer to the presence of a feature, element, step, or assembly, but do not exclude the presence or addition of one or more other features, elements, steps, or assemblies. [Brief description of the drawings]
[0020] Elements and features depicted in one drawing or one embodiment of the invention may be combined with elements and features shown in one or more other drawings or embodiments, and in the drawings, like symbols are used to indicate corresponding parts in several drawings and to indicate corresponding parts used in multiple embodiments. [Figure 1] FIG. 1 illustrates an IAB topology. [Diagram 2] FIG. 1 illustrates hop-by-hop downlink flow control. [Diagram 3] 2 is a diagram showing a signal transmission and reception method in an embodiment of the first aspect of the present invention. [Figure 4] A figure showing that the load condition of the downlink is indicated by a congestion report message in an embodiment of the first aspect of the present invention. [Diagram 5] A figure showing that the load condition of the uplink is indicated by a congestion report message in an embodiment of the first aspect of the present invention. [Figure 6] FIG. 13 illustrates an IAB-donor CU 6 triggering an IAB node 3 to send a congestion report message through request information. [Figure 7] A diagram showing the IAB-donor CU 6 sending congestion reporting configuration information to the IAB node 3. [Figure 8]FIG. 2 is another diagram showing that the IAB-donor CU 6 triggers the IAB node 3 to send a congestion report message by request information. [Figure 9] 11A and 11B are diagrams illustrating a method of transmitting and receiving signals in an embodiment of the second aspect. [Figure 10] FIG. 13 is a diagram illustrating a signal transmitting and receiving device according to an embodiment of a third aspect. [Figure 11] FIG. 13 illustrates a signal transmitting and receiving device according to an embodiment of the fourth aspect. [Figure 12] FIG. 2 is a diagram illustrating a configuration of a network device according to an embodiment of the present invention. [Figure 13] FIG. 2 is a diagram illustrating a terminal device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0021] The above and other features of the present invention will become apparent from the following detailed description and the accompanying drawings, in which: While the specification and drawings disclose certain embodiments of the present invention, these are illustrative of only some of the embodiments which may employ the principles of the present invention, and it is to be understood that the present invention is not limited to the described embodiments, but rather includes all modifications, variations and alternatives which fall within the scope of the appended claims.
[0022] In an embodiment of the present invention, the term "communication network" or "wireless communication network" may refer to a network conforming to any communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), etc.
[0023] Additionally, communications between devices in the communications system may be performed according to any stage of communications protocol, including, but not limited to, the following communications protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G, New Radio (NR), and / or other conventional or future developed communications protocols.
[0024] In the embodiment of the present invention, the term "network device" refers to a device that connects a terminal device to a communication network and provides services to the terminal device in a communication system, for example, the network device may include, but is not limited to, a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobile management entity (MME), a network gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.
[0025] Among them, the base station may include, but is not limited to, the following: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), 5G base station (gNB), etc., and may further include RRH (Remote Radio Head), RRU (Remote Radio Unit), relay, or low power node (e.g., femto, pico, etc.). In addition, the term "base station" may include some or all of the functions thereof, and each base station can provide communication coverage for a specific geographical area. The term "cell" may refer to a base station and / or the area it covers, depending on the context of the term.
[0026] In the embodiments of the present invention, the term "User Equipment" (UE) or "Terminal Equipment" (TE) refers to a device that accesses a communication network and receives services from the network, for example, via a network device. A User Equipment may be fixed or mobile, and may also be called a Mobile Station (MS), a terminal, a Subscriber Station (SS), an Access Terminal (AT), a station, etc.
[0027] Among these, user devices may include, but are not limited to, the following: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine type communication devices, laptop computers, cordless telephones, smartphones, smart watches, digital cameras, etc.
[0028] Furthermore, for example, in a scenario such as IoT (Internet of Things), the terminal device may further be a device or apparatus that performs monitoring or measurement, and may include, for example, an MTC (Machine Type Communication) terminal, an in-vehicle communication terminal, a D2D (Device to Device) terminal, an M2M (Machine to Machine) terminal, etc., but is not limited to these.
[0029] Additionally, the term "network side" or "network device side" refers to the side of a network, or may be a base station or a core network device, and may include one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the side of a user or terminal, or may be a UE, and may include one or more terminal devices as described above.
[0030] In the embodiment of the present invention, the higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, for example, referred to as an RRC message, including, for example, MIB, system information, dedicated RRC messages, or referred to as an RRC information element (RRC IE). The higher layer signaling may also be, for example, F1-C signaling, or referred to as an F1AP protocol, although the present invention is not limited thereto.
[0031] Various embodiments of the present invention will now be described with reference to the accompanying drawings, in which: It should be noted that these embodiments are merely illustrative and are not intended to limit the present invention.
[0032] <Example of the first aspect> In an IAB network, there are two mitigation methods for downlink congestion: (1) hop-by-hop downlink flow control, which is implemented by the backhaul adaptation protocol (BAP) control protocol data unit (PDU) of the BAP sublayer; and (2) end-to-end flow control, which is implemented by the downlink data delivery status (DDDS) of the new radio (NR) user plane protocol layer.
[0033] Figure 2 is a diagram showing hop-by-hop downlink flow control. As shown in Figure 2, when an IAB node 3 experiences congestion in the downlink direction, for example, when a buffer load exceeds a certain (predetermined) threshold, the IAB node 3 can send a flow control feedback to a parent node, i.e., an IAB node 5. The flow control feedback information is sent in the form of a BAP Control PDU. The parent node (i.e., the IAB node 5) can adjust (adjust) the downlink data rate based on the feedback information to realize flow control, thereby achieving the purpose of congestion mitigation.
[0034] Also, in Figure 2, IAB node 3 and IAB node 4 are both child nodes of IAB node 5, IAB node 5 is a child node of IAB donor node 6a, IAB node 2 is a child node of IAB node 3 and IAB node 4, and IAB node 1 is a child node of IAB node 2.
[0035] The above two congestion mitigation methods have some limitations, for example, hop-by-hop flow control can only mitigate short-term congestion and cannot resolve long-term congestion, and DDDS cannot provide information about the node where congestion occurs, so the congestion mitigation methods that can be selected are limited, and the above hop-by-hop and end-to-end flow control can only mitigate downlink congestion.
[0036] In view of at least the above limitations, in one embodiment of a first aspect of the present invention, a method for transmitting and receiving a signal is provided.
[0037] FIG. 3 illustrates a method for transmitting and receiving signals in an embodiment of the present invention. As shown in FIG. 3, the method includes the following operations (steps):
[0038] Operation 301: An IAB node (IAB) sends a congestion report message to a donor central unit (IAB-donor CU) of the IAB node, where the congestion report message is used to indicate a load state of a communication link of the IAB node.
[0039] According to an embodiment of the first aspect of the present invention, the IAB transmits a congestion report message to the IAB-donor CU to indicate the load state of the communication link, so that the IAB-donor CU can perform a congestion mitigation method based on a control plane (CP), for example, the IAB-donor CU can perform routing reconfiguration, and / or backhaul radio link control (BH RLC) channel mapping, and / or resource reallocation, etc., based on the congestion message, thereby mitigating long-term data congestion, reducing data loss, and optimizing network performance.
[0040] As shown in FIG. 3, the method may further include the following operations.
[0041] Operation 302: An IAB node (IAB) communicates with a child node and / or a parent node via a communication link.
[0042] In operation 302, the communication link may be an uplink or a downlink, whereby the congestion report message in operation 301 may indicate the loading condition of the uplink and / or the downlink.
[0043] FIG. 4 is a diagram showing that the load state of the downlink is indicated by a congestion report message in an embodiment of the first aspect of the present invention.
[0044] As shown in Fig. 4, when congestion occurs in the downlink of an IAB node 3, for example, when a buffer load exceeds a certain threshold, the IAB node 3 indicates the load state of the downlink of the IAB node 3 by sending a congestion report message to a donor central unit (IAB-donor CU) 6. Also, the explanation of the other nodes in Fig. 4 is the same as the related explanation of Fig. 2.
[0045] FIG. 5 is a diagram showing that the load state of the uplink is indicated by a congestion report message in an embodiment of the first aspect of the present invention.
[0046] As shown in Fig. 5, when congestion occurs in the uplink of the IAB node 3, for example, when the buffer load exceeds a certain threshold, the IAB node 3 indicates the load state of the uplink of the IAB node 3 by sending a congestion report message to the IAB-donor central unit (IAB-donor CU) 6. Also, the explanation of the other nodes in Fig. 5 is the same as the related explanation of Fig. 2.
[0047] In FIGS. 4 and 5, the operation of the IAB node 3 sending a congestion report message to the donor central unit (IAB-donor CU) 6 corresponds to operation 301 in FIG.
[0048] In the following description of an embodiment of the first aspect, the IAB of operation 301 is, for example, IAB node 3 in FIGS.
[0049] In at least one embodiment, the content of the congestion report message sent by the IAB node 3 may include: buffer size (buffer size refers to the status of a buffer such as a BH RLC channel in the congestion report message); and / or buffer occupation; and / or available buffer size (available buffer size refers to the maximum flow that the transmitting end of the IAB node 3 should transmit); and / or available data rate (available data rate refers to the maximum flow data rate that the transmitting end of the IAB node 3 should use, where available data rate may also be referred to as desired data rate); and / or information for indicating that congestion has occurred in the communication link (for example, the information may be a simple indication information for indicating that congestion has occurred in the communication link).
[0050] As shown in FIG. 3, the method may further include the following operations.
[0051] Operation 303: The IAB node sends a congestion clear indication to a donor central unit (IAB-donor CU), where the congestion clear indication is used to indicate that the communication link of the IAB node is in a non-congested state.
[0052] For example, when the uplink or downlink of the IAB node 3 recovers from a congested state to a normal state (e.g., when the buffer load is below a certain threshold), the IAB node 3 can send congestion clear indication information to the IAB-donor CU 6.
[0053] It should be noted that the above-mentioned FIG. 3 is for illustrative purposes only to explain an embodiment of the present invention, but the present invention is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, or the number of operations can be increased or decreased. In addition, those skilled in the art are not limited to the description of FIG. 3, and may make appropriate modifications based on the above content. For example, operation 301 may be executed before operation 302.
[0054] In at least one embodiment, the congestion report message may include an information element (IE) that is used to carry a list of congestion status information, which may be named, for example, Congestion Information List IE.
[0055] The list of congestion status information may include multiple congestion status information, and each congestion status information includes the content of a congestion report message to be reported at a predetermined granularity. The granularity may be, for example, each BH RLC channel; or each routing ID; or each communication link. The BH RLC channel or communication link in the congestion status information may be on the IAB-DU side or on the IAB-MT side.
[0056] The congestion status information may further include information for indicating a traffic direction. For example, when the granularity is BH RLC channel, the content of the congestion report message is reported for each BH RLC channel, and the congestion status information may have one information for indicating a traffic direction to indicate the traffic direction represented by the congestion status information, where the information for indicating the traffic direction may be information for indicating an uplink or a downlink, or may be information for indicating an ingress or an egress; or, for example, when the granularity is communication link, the congestion status information may have one information for indicating a traffic direction, where the information for indicating the traffic direction may be information for indicating that the communication link is an ingress link or an egress link, or may be information for indicating that the communication link is an uplink or a downlink.
[0057] Furthermore, since the uplink and downlink can be distinguished by the routing ID, when the granularity is the routing ID, there is no need to add information for indicating the service direction to the congestion state information.
[0058] In at least one embodiment, one piece of congestion status information in the list of congestion status information may include: a BH RLC channel ID or a routing ID or a link ID, and the content of a corresponding congestion report message, where one congestion report message may include congestion report information of different granularities. Note that, since the BH RLC channel indicator is unique for each link, the BH RLC channel indicator referred to in the present invention actually refers to a combination of the link indicator and the BH RLC channel indicator, for example, the link indicator+BH RLC channel indicator.
[0059] Table 1 is an example of the format of the Congestion Information IE in the congestion report message. The "O" in Presence indicates that it is optional, for example, "O" indicates that only one may be selected for the granularity or report content of each entry in the list of Congestion Information IEs. In Table 1, the link indicator is not directly used, but the prior-hop node BAP address or the next-hop node BAP address is used to replace the link indicator equivalently.
[0060] [Table 1] In at least one embodiment, the congestion report message sent for the uplink and the congestion report message sent for the downlink may have the same message format, e.g., the format of the Congestion Information IE for the uplink and the downlink is the same (e.g., both are in the format shown in Table 1).
[0061] In at least one embodiment, when the IAB node 3 receives polling / request information from the IAB-donor CU 6, the IAB node 3 sends the congestion report message to the IAB-donor CU.
[0062] The request information may include a granularity of the congestion status information in the congestion report message, and / or a BH RLC channel indicator, and / or a routing indicator, and / or a link indicator. For each BH RLC channel indicator or link indicator, the request message may further include an indication of uplink or downlink, or an indication of ingress or egress. If the request information includes a granularity (i.e., the request information indicates a granularity of the congestion status information), the IAB node 3 may generate a congestion report message according to the granularity, and if the request message includes a BH RLC channel indicator, a routing indicator, or a link indicator, the IAB node 3 may generate a congestion report message corresponding to these indicators.
[0063] Additionally, the request information may further include an interval period and / or a duration, such that the IAB node 3 can transmit the congestion report message at the transmission interval period within the duration.
[0064] Fig. 6 is a diagram showing that the IAB-donor CU 6 triggers the IAB node 3 to send a congestion report message by the request information. As shown in Fig. 6, in operation 601, the IAB-donor CU 6 sends the request information to the DU of the IAB node 3, the name of the request information is, for example, CONGESTION REPORT POLLING or CONGESTION REPORT REQUEST, and in operation 602, the DU of the IAB node 3 generates and sends a congestion report message to the IAB-donor CU 6 based on the granularity, and / or BH RLC channel indicator, and / or routing indicator, and / or link indicator in the request information.
[0065] In at least another embodiment, when a predefined condition of the IAB node 3 is satisfied, the IAB node 3 sends the congestion report message to the IAB-donor CU.
[0066] In one embodiment, the predetermined condition includes that the buffer load corresponding to the granularity of the congestion status information in the congestion report message exceeds a first threshold and continues for a first period of time, where the first period of time can be realized by using a timer 1. For example, when a certain granularity of the buffer load reaches a first threshold 1, the timer 1 is started or restarted, when the timer 1 expires, the congestion report message is triggered, and when the buffer load falls below the first threshold 1, the timer 1 is stopped when it is running.
[0067] In another embodiment, the predetermined condition includes: the buffer load of the IAB node 3 for the same indicator (e.g., link indicator, BH RLC channel indicator, routing indicator) exceeds a second threshold within a second period of time; It is sent becauseThe number or instance of the backhaul adaptation protocol control protocol (BAP) sub-layer flow control feedback exceeds a third threshold. Wherein, the second period can be realized by a timer 2 corresponding to the indicator. For example, the counter of the number or instance of flow control feedback for a certain indicator of the BAP sub-layer is initialized to an initial value (for example, the initial value is 0), and each time the BAP sub-layer starts one flow control feedback for the indicator, the counter of the number or instance of flow control feedback is incremented by 1, and the timer 2 is started or restarted. When the counter reaches the third threshold 3, the transmission of a congestion report message is triggered. When the timer 2 expires, the counter is reset to the initial value. The timer 2 is the interval between two flow control feedbacks, and the timer 2 is used to indirectly realize the second period. Also, if the time is long enough (for example, the second timer expires) after one flow control feedback is sent, it means that the congestion corresponding to the flow control feedback of the previous transmission has already recovered normally, so the timer starts counting again when the flow control feedback is sent next time. In addition, the related art can be referred to for the operation of sending BAP sub-layer flow control feedback when the buffer load of the IAB node 3 exceeds the second threshold.
[0068] As shown in FIG. 3, in at least one embodiment, the method may further include the following operations.
[0069] Operation 304: An IAB node (IAB) receives congestion reporting configuration information sent by a donor central unit (IAB-donor CU).
[0070] For example, IAB node 3 receives IAB-donor CU 6 sending congestion reporting configuration information.
[0071] The congestion report configuration information is used to configure: parameters required for certain conditions for the IAB node 3 to determine when to send a congestion report message; and / or parameters or settings required for the IAB node 3 to send a congestion report message.
[0072] Among them, the parameters necessary for the predetermined conditions for the IAB node 3 to determine the timing of transmitting a congestion report message include, for example, the granularity in the above-mentioned predetermined conditions, and / or the first threshold 1, and / or the second threshold, and / or the third threshold 3, and / or the initial value of a timer, etc. The parameters or settings necessary for the IAB node 3 to transmit a congestion report message include, for example, the granularity in the congestion report message, etc.
[0073] Moreover, as shown in FIG. 3, the method may further include the following operations.
[0074] Operation 305: The IAB node (IAB) sends a configuration confirmation to the donor central unit (IAB-donor CU).
[0075] The setting confirmation information is used to confirm that the IAB node 3 has received the congestion reporting setting information.
[0076] Figure 7 is a diagram showing that the IAB-donor CU 6 sends congestion reporting configuration information to the IAB node 3. As shown in Figure 7, in operation 701, the IAB-donor CU 6 sends congestion reporting configuration information to the DU of the IAB node 3, and the name of the congestion reporting configuration information is, for example, CONGESTION REPORTING CONFIGURATION, and in operation 702, the DU of the IAB node 3 sends configuration acknowledgement information to the IAB-donor CU 6, and the name of the configuration acknowledgement information is, for example, CONGESTION REPORTING CONFIGURATION ACKNOWLEDGE.
[0077] The operations 701 and 702 in Fig. 7 or the operations 304 and 305 in Fig. 3 may be referred to as a Congestion Reporting Configuration procedure. The Congestion Reporting Configuration procedure may use control plane signaling, for example, the IAB node 3 may receive congestion reporting configuration information through F1 interface application protocol (F1 application protocol (F1AP), defined in TS38.473) signaling. The Congestion Reporting Configuration procedure may be a newly added IAB procedure, and the procedure may use non-User Equipment (UE) related signaling.
[0078] In at least one embodiment, the congestion report message in operation 301 may be carried in control plane signaling.
[0079] In one embodiment, the control plane signaling may include, for example, F1 interface application protocol signaling, i.e., whether the uplink or downlink load condition is a load condition, F1AP signaling is used to carry the congestion report message, and the congestion report message is sent from the DU part of the IAB node 3 to the IAB-donor CU 6. Wherein, the congestion report message for the uplink is generated from the IAB-MT of the IAB node 3, and the IAB-DU collocated with the IAB-MT in the IAB node 3 sends the congestion report message for the uplink generated by the IAB-MT to the IAB-donor-CU 6.
[0080] In one example, a new IAB elementary procedure may be added to the F1AP service to transmit and receive congestion report messages between the gNB-DU and the gNB-CU, and the newly added procedure may be named a Congestion Reporting procedure, in which all consideration factors of the gNB-DU are suitable for the IAB-DU and the IAB-donor-DU, and the gNB-CU refers to the IAB-donor-CU.
[0081] In another example, a new IAB procedure may not be added, but an existing procedure may be used to realize transmission and reception of congestion report messages between the IAB node 3 and the IAB-donor CU 6. For example, the existing procedure may be a gNB-DU Status Indication procedure, and congestion status information may be added to the content of the existing procedure, for example, redesigning the gNB-DU Overload Information IE.
[0082] In this embodiment, not only can F1AP signaling be used to carry congestion report messages for all uplink and downlink load conditions, but also F1AP signaling can be used to transmit congestion report requests for uplink and downlink, and can also be used for congestion report configuration procedures for uplink and downlink.
[0083] For example, as shown in Fig. 6, the DU of the IAB node 3 receives a congestion report request for uplink and downlink from the IAB-donor CU 6 by F1AP signaling, and also transmits a congestion report message to the IAB-donor CU 6 by F1AP signaling. Also, as shown in Fig. 7, the DU of the IAB node 3 receives a congestion report setting for uplink and downlink by F1AP signaling, and also transmits setting confirmation information by F1AP signaling.
[0084] In another embodiment, the control plane signaling may include signaling in a radio resource control (RRC) message. For example, for downlink, i.e., for a link on the DU side of the IAB node, the congestion report message on the BH RLC channel or the downlink routing ID may be carried in an F1AP message, and for uplink, i.e., for a link on the MT side of the IAB node, the congestion report message on the BH RLC channel or the uplink routing ID may be carried in an RRC message. That is, for downlink, the procedures shown in Figures 6 and 7 may be used, and for uplink, a procedure similar to Figures 6 and 7 may be realized by an RRC message between the MT of the IAB node 3 and the IAB-donor CU 6.
[0085] For example, Figure 8 is another diagram showing that the IAB-donor CU 6 triggers the IAB node 3 to send a congestion report message by the request information. As shown in Figure 8, in operation 801, the IAB-donor CU 6 sends request information to the MT of the IAB node 3, the name of the request information is, for example, CONGESTION REPORT POLLING or CONGESTION REPORT REQUEST, and in operation 802, the MT of the IAB node 3 generates a congestion report message based on the granularity, and / or BH RLC channel indicator, and / or routing indicator, and / or link indicator in the request information, and sends it to the IAB-donor CU 6 by an RRC message.
[0086] In addition, the MT of the IAB node 3 may generate a congestion report message and transmit it by an RRC message when a predetermined condition is satisfied, not when request information is received. In a scenario using an RRC message, the predetermined condition may be an event type.
[0087] When congestion reporting is performed using an RRC message for the uplink, the Congestion Reporting Configuration procedure may use dedicated signaling in the RRC message, such as RRCReconfiguration or RRCResume, and the procedure may refer to the definition in standard TS38.331, and the procedure may include configuration information content, such as granularity in the congestion report message, and / or the above-mentioned first threshold 1 (i.e., the buffer load threshold), and / or the above-mentioned second threshold, and / or the above-mentioned third threshold 3, and / or the initial value of the above-mentioned timer, etc.
[0088] According to an embodiment of the first aspect of the present invention, the IAB transmits a congestion report message to the IAB-donor CU to indicate the load state of the communication link, so that the IAB-donor CU can perform a congestion mitigation method based on a control plane (CP), for example, the IAB-donor CU can perform routing reconfiguration, and / or backhaul radio link control (BH RLC) channel mapping, and / or resource reallocation, etc., based on the congestion message, thereby mitigating long-term data congestion, reducing data loss, and optimizing network performance.
[0089] <Example of the second aspect> In view of at least the same problems as in the embodiment of the first aspect, in an embodiment of a second aspect of the present invention, a method for transmitting and receiving signals is provided, which corresponds to the method according to the embodiment of the first aspect.
[0090] Hereinafter, the signal transmission and reception method in the embodiment of the second aspect of the present invention will be described from the side of the donor central unit (IAB-donor CU) 6 in FIG. 4 and FIG. 5 by taking the scenario in FIG. 4 and FIG. 5 as an example.
[0091] FIG. 9 illustrates a method for transmitting and receiving signals in an embodiment of the second aspect. As shown in FIG. 9, the method includes the following operations.
[0092] Operation 901: A donor central unit (IAB-donor CU) receives a congestion report message sent by an IAB node (IAB), which is used to indicate a load state of a communication link of the IAB node.
[0093] In at least one embodiment, the content of the congestion report message includes: buffer size; and / or buffer occupation; and / or available buffer size; and / or available data rate; and / or information indicating that congestion has occurred on the communication link.
[0094] As shown in FIG. 9, the method further includes the following operations.
[0095] Operation 902: A donor central unit (IAB-donor CU) further receives congestion clear indication information transmitted by the IAB node, where the congestion clear indication information is used to indicate that the communication link of the IAB node is in a non-congested state.
[0096] In at least one embodiment, the congestion report message may include an information element (IE), which is used to carry a list of congestion status information. The granularity of the congestion status information is each backhaul radio link control (BH RLC) channel, and / or each routing ID, and / or each communication link. Wherein, when the granularity of the congestion status information is each backhaul radio link control (BH RLC) channel or each communication link, the congestion status information further includes information for indicating a service direction (e.g., uplink or downlink, egress or ingress).
[0097] The congestion report message for the uplink and the congestion report message for the downlink have the same message format, for example, the format of the Congestion Information IE in the congestion report message is the same.
[0098] As shown in FIG. 9, the method further includes the following operations.
[0099] Operation 903: A donor central unit (IAB-donor CU) sends polling information to the IAB node (IAB), and receives the congestion report message sent by the IAB node (IAB) if the donor central unit has sent the polling information.
[0100] Wherein, the request information includes: a granularity of congestion status information in the congestion report message, and / or a backhaul radio link control (BH RLC) channel indicator, and / or a routing indicator, and / or a link indicator in the congestion status information, and the request information further includes a transmission interval period of the congestion report message, and / or a duration for transmitting the congestion report message in the period.
[0101] As shown in FIG. 9, the method further includes the following operations.
[0102] Operation 904: A donor central unit (IAB-donor CU) sends congestion reporting configuration information to the IAB node (IAB).
[0103] Wherein, the congestion reporting configuration information is used to configure the following: parameters required for a predetermined condition for the IAB node (IAB) to determine the timing of sending the congestion report message, and / or parameters or settings required for the IAB node (IAB) to send the congestion report message. The congestion reporting configuration information can be transmitted by F1AP signaling or dedicated signaling in an RRC message.
[0104] In at least one embodiment, the congestion report message is carried in control plane signaling.
[0105] The control plane signaling includes F1AP signaling, for example, the congestion report message for uplink and downlink can both be carried in F1AP signaling, where an IAB procedure can be newly added to the F1AP to transmit the congestion report message.
[0106] The control plane signaling may include RRC messages, e.g., for the downlink, congestion report messages may all be carried to the F1 AP, and for the uplink loading conditions, congestion report messages are carried in Radio Resource Control (RRC) messages.
[0107] In addition, the donor central unit (IAB-donor CU) may send congestion report configuration information to the IAB node (IAB) by dedicated signaling in a Radio Resource Control (RRC) message, and the configuration information is the same as described above and is used, for example, to configure the following: parameters required for certain conditions for the IAB node (IAB) to determine the timing of sending the congestion report message, and / or parameters or settings required for the IAB node (IAB) to send the congestion report message.
[0108] According to an embodiment of the second aspect of the present invention, the IAB sends a congestion report message to the IAB-donor CU to indicate the load state of the communication link, so that the IAB-donor CU can perform a congestion mitigation method based on the control plane (CP), for example, the IAB-donor CU can perform routing reconfiguration, and / or backhaul radio link control (BH RLC) channel mapping, and / or resource reallocation, etc., based on the congestion message, thereby mitigating long-term data congestion, reducing data loss, and optimizing network performance.
[0109] <Example of the third aspect> In an embodiment of the present invention, a signal transmitting / receiving device is provided. The device may be, for example, an IAB node, or one or more components disposed in an IAB node, for example, IAB-node 3 in Fig. 4 or Fig. 5. The device corresponds to the method in the embodiment of the first aspect.
[0110] FIG. 10 is a diagram showing a signal transmitting / receiving device in an embodiment of the present invention. As shown in FIG. 10, a signal transmitting / receiving device 1000 includes:
[0111] A first transceiver unit 1001: sends a congestion report message to a donor central unit (IAB-donor CU) of an IAB node, and the congestion report message is used to indicate the load status of a communication link of the IAB node.
[0112] The contents of the congestion report message include: buffer size; and / or buffer occupation; and / or available buffer size; and / or available data rate; and / or information indicating that congestion has occurred on the communication link.
[0113] In at least one embodiment, the first transceiver unit 1001 further transmits congestion clear indication information to a donor central unit (IAB-donor CU), where the congestion clear indication information is used to indicate that the communication link of the IAB node is in a non-congested state.
[0114] In at least one embodiment, the congestion report message includes an information element (IE) that is used to carry a list of congestion status information, where the granularity of the congestion status information is for each backhaul radio link control (BH RLC) channel, and / or for each routing ID, and / or for each communication link.
[0115] The congestion report message for uplink and the congestion report message for downlink have the same message format.
[0116] When the granularity of the congestion status information is each Backhaul Radio Link Control (BH RLC) channel or each communication link, the congestion status information further includes information for indicating a service direction.
[0117] When the IAB node (IAB) receives request (polling) information from the donor central unit (IAB-donor CU), or when a predetermined condition of the IAB node (IAB) is satisfied, the IAB node (IAB) sends the congestion report message.
[0118] The request information includes a granularity of congestion status information in a congestion report message, and / or a backhaul radio link control (BH RLC) channel indicator, and / or a routing indicator, and / or a link indicator in the congestion status information. The request information further includes a transmission interval period of the congestion report message, and / or a duration for transmitting the congestion report message in the period.
[0119] The predetermined condition may also be: a buffer load corresponding to the granularity of the congestion status information in the congestion report message exceeds a first threshold and continues for a first period; or a buffer load for the same indicator (e.g., a link indicator, a BH RLC channel indicator, a routing indicator) of the IAB node exceeds a second threshold within a second period. It is sent becauseThe number or instances of Backhaul Adaptation Protocol (BAP) sub-layer flow control feedback exceed a third threshold.
[0120] As shown in FIG. 10, the apparatus 1000 further includes:
[0121] A second transceiver unit 1002: receives congestion reporting configuration information sent by a donor central unit (IAB-donor CU).
[0122] The congestion reporting configuration information is used to configure the following: parameters required for a predetermined condition for the IAB node (IAB) to determine the timing of sending the congestion report message, and / or parameters or settings required for the IAB node (IAB) to send the congestion report message. The congestion reporting configuration information is received by F1 interface application protocol signaling.
[0123] In at least one embodiment, the congestion report message is carried in control plane signaling.
[0124] The control plane signaling includes F1 interface application protocol signaling, for example, for uplink and downlink, the congestion report message can be carried by F1AP signaling, whereby an IAB procedure can be newly added to the F1 interface application protocol to transmit the congestion report message.
[0125] The control plane signaling may include RRC messages, e.g., for the downlink, congestion report messages may all be carried to the F1 AP, and for the uplink loading conditions, congestion report messages are carried in Radio Resource Control (RRC) messages.
[0126] In addition, the second transceiver unit 1002 can receive congestion report configuration information from the IAB-donor CU by dedicated signaling in a radio resource control (RRC) message, and the configuration information is the same as described above, for example, used to set parameters required for a certain condition for the IAB node (IAB) to determine the timing of sending the congestion report message, and / or parameters or settings required for the IAB node (IAB) to send the congestion report message.
[0127] According to an embodiment of the third aspect of the present invention, the IAB sends a congestion report message to the IAB-donor CU to indicate the load state of the communication link, so that the IAB-donor CU can perform a congestion mitigation method based on the control plane (CP), for example, the IAB-donor CU can perform routing reconfiguration, and / or backhaul radio link control (BH RLC) channel mapping, and / or resource reallocation, etc., based on the congestion message, thereby mitigating long-term data congestion, reducing data loss, and optimizing network performance.
[0128] <Example of the fourth aspect> In an embodiment of the present invention, a signal transmitting / receiving device is provided, which may be, for example, a donor central unit (IAB-donor CU) or one or more sites arranged in the donor central unit (IAB-donor CU), for example, the IAB-donor CU 6 in Fig. 4 or Fig. 5. The signal transmitting / receiving device corresponds to the signal transmitting / receiving method described in the embodiment of the second aspect.
[0129] FIG. 11 is a diagram showing a signal transmitting and receiving device in an embodiment of the fourth aspect. As shown in FIG. 11, the device includes:
[0130] A third transceiver unit 1101: for receiving a congestion report message sent by an IAB node (IAB), the congestion report message being used to indicate a load status of a communication link of the IAB node.
[0131] In at least one embodiment, the content of the congestion report message includes buffer size; and / or buffer occupation; and / or available buffer size; and / or available data rate; and / or information to indicate that congestion has occurred on the communication link.
[0132] The third transceiver unit 1101 may further receive congestion clear indication information sent by the IAB node, where the congestion clear indication information is used to indicate that the communication link of the IAB node is in a non-congested state.
[0133] In at least one embodiment, the congestion report message may include an information element (IE), which is used to carry a list of congestion status information. The granularity of the congestion status information is each backhaul radio link control (BH RLC) channel, and / or each routing ID, and / or each communication link. Wherein, when the granularity of the congestion status information is each backhaul radio link control (BH RLC) channel or each communication link, the congestion status information further includes information for indicating a service direction (e.g., uplink or downlink, egress or ingress).
[0134] The congestion report message for the uplink and the congestion report message for the downlink have the same message format, for example, the format of the Congestion Information IE in the congestion report message is the same.
[0135] As shown in FIG. 11, the apparatus 1100 further includes:
[0136] A fourth transceiver unit 1102: sends polling information to the IAB node (IAB); and receives the congestion report message sent by the IAB node (IAB) when the polling information is sent.
[0137] Wherein, the request information includes: a granularity of congestion status information in the congestion report message, and / or a backhaul radio link control (BH RLC) channel indicator, and / or a routing indicator, and / or a link indicator in the congestion status information, and the request information further includes a transmission interval period of the congestion report message, and / or a duration for transmitting the congestion report message in the period.
[0138] As shown in FIG. 11, the apparatus 1100 further includes:
[0139] A fifth transceiver unit 1103: sends congestion reporting configuration information to the IAB node (IAB).
[0140] Wherein, the congestion reporting configuration information is used to set the following: parameters required for a predetermined condition for the IAB node (IAB) to determine the timing of sending the congestion report message, and / or parameters or settings required for the IAB node (IAB) to send the congestion report message. The congestion reporting configuration information can be sent by F1 interface application protocol signaling or dedicated signaling in an RRC message.
[0141] In at least one embodiment, the congestion report message is carried in control plane signaling.
[0142] The control plane signaling includes F1 interface application protocol signaling, for example, for uplink and downlink, the congestion report message may be carried by F1AP signaling, whereby an IAB procedure may be newly added to the F1 interface application protocol to transmit the congestion report message.
[0143] The control plane signaling may include RRC messages, e.g., for the downlink, congestion report messages may all be carried to the F1 AP, and for the uplink loading conditions, congestion report messages are carried in Radio Resource Control (RRC) messages.
[0144] In addition, the fifth transceiver unit 1103 can send congestion report configuration information to the IAB node (IAB) by dedicated signaling in a radio resource control (RRC) message, and the configuration information is the same as described above, for example, used to set parameters required for certain conditions for determining when the IAB node (IAB) sends the congestion report message, and / or parameters or settings required for the IAB node (IAB) to send the congestion report message.
[0145] According to an embodiment of the fourth aspect of the present invention, the IAB transmits a congestion report message to the IAB-donor CU to indicate the load state of the communication link, so that the IAB-donor CU can perform a congestion mitigation method based on the control plane (CP), for example, the IAB-donor CU can perform routing reconfiguration, and / or backhaul radio link control (BH RLC) channel mapping, and / or resource reallocation, etc., based on the congestion message, thereby mitigating long-term data congestion, reducing data loss, and optimizing network performance.
[0146] For convenience, only the connection relationships or signal directions between the components or modules are shown in the signal transmission devices 1000 and 1100, but various related technologies such as bus connection may be adopted as understood by those skilled in the art. These components or modules may be realized by hardware such as a processor, a memory, a transmitter, a receiver, etc., but the implementation of the present invention is not limited thereto.
[0147] In addition, although the above-mentioned embodiments are provided to exemplify the embodiments of the present invention, the present invention is not limited to these, and appropriate modifications may be made based on the above-mentioned embodiments. For example, each of the above-mentioned embodiments may be implemented alone, or a plurality of the above-mentioned embodiments may be combined.
[0148] <Example of the fifth aspect> An embodiment of the present invention further provides a communication system, for which reference can be made to FIG. 1, and the description of the same contents as those of the embodiments of the first to fourth aspects will be omitted.
[0149] In some embodiments, the communication system may include:
[0150] A donor central unit (IAB-donor CU): including a signal transceiver 1100 according to the embodiment of the fourth aspect; and IAB node: includes the signal transmitting / receiving device 1000 described in the embodiment of the third aspect.
[0151] Wherein, the IAB node (IAB) may include an IAB-MT functional unit and an IAB-DU functional unit, wherein the IAB-MT functional unit may have the same configuration as the terminal device, and the IAB-DU functional unit and the donor central unit (IAB-donor CU) may have the same units as the network device.
[0152] Fig. 12 is a block diagram of a network device in an embodiment of the present invention. As shown in Fig. 12, the network device 1200 may include a processor 1210 (e.g., a central processing unit CPU) and a memory 1220, and the memory 1220 is connected to the processor 1210. The memory 1220 can store various data, and can further store a program 1230 for information processing, and can execute the program 1230 under the control of the processor 1210.
[0153] For example, the processor 1210 may be configured to execute a program to implement a method for implementing the IAB-DU in the embodiment of the first aspect or the IAB-donor CU in the embodiment of the second aspect.
[0154] In addition, as shown in Fig. 12, the network device 1200 may further include a transceiver 1240, an antenna 1250, etc., among which, the functions of these components are similar to those of the prior art, so detailed description thereof will be omitted here. It is not necessary for the network device 1200 to include all the components shown in Fig. 12. In addition, the network device 1200 may further include components not shown in Fig. 12, and the prior art can be referred to for this.
[0155] FIG. 13 is a diagram illustrating a terminal device according to an embodiment of the present invention. As shown in FIG. 13, the terminal device 1300 may include a processor 1310 and a memory 1320. The memory 1320 stores data and programs, and is connected to the processor 1310. It should be noted that the diagram is merely an example, and other types of structures may be used to supplement or replace the structures to realize the telecommunication function or other functions. For example, the processor 1310 may be configured to execute a program to realize the method of performing IAB-MT described in the embodiment of the first aspect.
[0156] As shown in Fig. 13, the terminal device 1300 may further include a communication module 1330, an input unit 1340, a display 1350, a power supply 1360, etc. Among them, the functions of these components are similar to those of the prior art, so detailed descriptions thereof are omitted here. It is not necessary for the terminal device 1300 to include all the components shown in Fig. 13. In addition, the terminal device 1300 may further include components not shown in Fig. 13, and reference can be made to the prior art for such components.
[0157] An embodiment of the present invention further provides a computer program, which, when executed in an IAB, causes the IAB to perform the method for transmitting and receiving signals according to the embodiment of the first aspect.
[0158] An embodiment of the present invention further provides a storage medium storing a computer program, wherein the computer program causes the IAB to perform the method for transmitting and receiving signals according to the embodiment of the first aspect.
[0159] In an embodiment of the present invention, a computer program is further provided, which, when executed in an IAB-donor CU, causes the IAB-donor CU to perform a method according to an embodiment of the second aspect.
[0160] An embodiment of the present invention further provides a storage medium storing a computer program, wherein the computer program causes the IAB-donor CU to perform the method described in the embodiment of the second aspect.
[0161] The above-mentioned devices and methods may be realized by software or hardware, or may be realized by a combination of hardware and software. The present invention further relates to a computer-readable program as described below, which, when executed by a logic component, causes the logic component to realize the above-mentioned device or component, or causes the logic component to realize the above-mentioned various methods or steps. The logic component may be, for example, an FPGA (Field Programmable Gate Array), a microprocessor, a processor for use in a computer, etc. The present invention further relates to a storage medium, such as a hard disk, a magnetic disk, an optical hard disk, a DVD, a flash memory, etc., storing the above-mentioned program.
[0162] Additionally, one or more combinations of the functional blocks depicted in the figures and / or one or more combinations of the functional blocks may be implemented as a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic component, a discrete gate or transistor logic component, a discrete hardware assembly, or any other suitable combination for performing the functions described herein. Also, one or more combinations of the functional blocks depicted in the figures and / or one or more combinations of the functional blocks may be further configured as a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in communication with a DSP, or any other configuration.
[0163] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to such embodiments, and any modifications to the present invention fall within the technical scope of the present invention as long as they do not depart from the spirit of the present invention.
[0164] Furthermore, with respect to the above-mentioned embodiments, the following supplementary notes are disclosed.
[0165] (Appendix 1) A method for transmitting and receiving a signal, comprising: an IAB node (IAB) sending a congestion report message to a donor central unit (IAB-donor CU) of the IAB node; The congestion report message is used to indicate a load condition of a communication link of the IAB node.
[0166] (Appendix 2) 2. The method according to claim 1, comprising: The content of the congestion report message is: buffer size; and / or buffer occupation; and / or available buffer size; and / or available data rate; and / or including information for indicating that congestion will occur on the communications link.
[0167] (Appendix 3) 2. The method according to claim 1, comprising: The method further comprises: The IAB node sends a congestion clear indication to the donor central unit (IAB-donor CU); The congestion clearing indication information is used to indicate that the communication link of the IAB node is in a non-congested state.
[0168] (Appendix 4) 2. The method according to claim 1, comprising: A method, wherein the congestion report message for uplink and the congestion report message for downlink have the same message format.
[0169] (Appendix 5) 2. The method according to claim 1, comprising: The congestion report message includes an information element (IE), which is used to carry a list of congestion status information; The method, wherein the granularity of the congestion status information is per Backhaul Radio Link Control (BH RLC) channel, and / or per Routing ID, and / or per communication link.
[0170] (Appendix 6) 6. The method according to claim 5, When the granularity of the congestion status information is per backhaul radio link control (BH RLC) channel or per communication link, The method, wherein the congestion status information further comprises information for directing service direction.
[0171] (Appendix 7) 2. The method according to claim 1, comprising: The method includes: when the IAB node (IAB) receives request (polling) information from the donor central unit (IAB-donor CU) or when a predetermined condition of the IAB node (IAB) is satisfied, the IAB node (IAB) sends the congestion report message.
[0172] (Appendix 8) 8. The method according to claim 7, The method, wherein the request information includes a granularity of congestion status information in the congestion report message, and / or a Backhaul Radio Link Control (BH RLC) channel indicator in the congestion status information, and / or a routing indicator, and / or a link indicator.
[0173] (Appendix 9) 8. The method according to claim 7, The method, wherein the request information further includes a periodicity between transmission of the congestion report message and / or a duration for transmitting the congestion report message at the periodicity.
[0174] (Appendix 10) 8. The method according to claim 7, The predetermined condition is: A buffer load corresponding to the granularity of the congestion status information in the congestion report message exceeds a first threshold and continues for a first period of time; or Within a second period, the buffer load for the same indicator of the IAB node (IAB) exceeds a second threshold. Sent due to exceeding The method includes a number or instances of Backhaul Adaptation Protocol (BAP) sub-layer flow control feedback exceeding a third threshold.
[0175] (Appendix 11) 2. The method according to claim 1, comprising: The method further comprises: The IAB node (IAB) receives congestion reporting configuration information of the donor central unit (IAB-donor CU) transmission; A method in which the congestion report setting information is used to set parameters required for predetermined conditions for the IAB node (IAB) to determine the timing of sending the congestion report message, and / or parameters or settings required for the IAB node (IAB) to send the congestion report message.
[0176] (Appendix 12) 12. The method according to claim 11, The congestion reporting configuration information is received through F1 interface application protocol signaling.
[0177] (Appendix 13) 2. The method according to claim 1, comprising: The congestion report message is sent by F1 interface application protocol signaling.
[0178] (Appendix 14) 14. The method according to claim 13, comprising: A method for transmitting the congestion report message in an IAB procedure newly added to the F1 interface application protocol.
[0179] (Appendix 15) 2. The method according to claim 1, comprising: A method, wherein the congestion report message is carried in a Radio Resource Control (RRC) message regarding uplink loading conditions.
[0180] (Appendix 16) 12. The method according to claim 11, The congestion reporting configuration information is received by dedicated signaling in an RRC message.
[0181] (Appendix 17) A method for transmitting and receiving a signal, comprising: A donor central unit (IAB-donor CU) receives a congestion report message transmitted by an IAB node (IAB); The congestion report message is used to indicate a load condition of a communication link of the IAB node.
[0182] (Appendix 18) 18. The method according to claim 17, comprising: The content of the congestion report message is: buffer size; and / or buffer occupation; and / or available buffer size; and / or available data rate; and / or including information indicative of congestion occurring on the communications link.
[0183] (Appendix 19) 18. The method according to claim 17, comprising: The method further comprises: The donor central unit (IAB-donor CU) further includes receiving congestion clear indication information of the IAB node transmission; The congestion clearing indication information is used to indicate that the communication link of the IAB node is in a non-congested state.
[0184] (Appendix 20) 18. The method according to claim 17, comprising: A method, wherein the congestion report message for uplink and the congestion report message for downlink have the same message format.
[0185] (Appendix 21) 18. The method according to claim 17, comprising: The congestion report message includes an information element (IE), which is used to carry a list of congestion status information; The method, wherein the granularity of the congestion status information is per Backhaul Radio Link Control (BH RLC) channel, and / or per Routing ID, and / or per communication link.
[0186] (Appendix 22) 22. The method according to claim 21, When the granularity of the congestion status information is per backhaul radio link control (BH RLC) channel or per communication link, The method, wherein the congestion status information further includes information for indicating an uplink or a downlink.
[0187] (Appendix 23) 18. The method according to claim 17, comprising: The method further comprises: The donor central unit (IAB-donor CU) sends polling information to the IAB node (IAB); and receiving the congestion report message sent by the IAB node (IAB) when the polling information is sent.
[0188] (Appendix 24) 24. The method according to claim 23, comprising: The method, wherein the request information includes a granularity of congestion status information in the congestion report message, and / or a Backhaul Radio Link Control (BH RLC) channel indicator in the congestion status information, and / or a routing indicator, and / or a link indicator.
[0189] (Appendix 25) 24. The method of claim 23, The method, wherein the request information further includes a periodicity between transmission of the congestion report message and / or a duration for transmitting the congestion report message at the periodicity.
[0190] (Appendix 26) 18. The method according to claim 17, comprising: The method further comprises: The donor central unit (IAB-donor CU) sends congestion reporting configuration information to the IAB node (IAB); A method in which the congestion report setting information is used to set parameters required for predetermined conditions for the IAB node (IAB) to determine the timing of sending the congestion report message, and / or parameters or settings required for the IAB node (IAB) to send the congestion report message.
[0191] (Appendix 27) 27. The method according to claim 26, comprising: The congestion reporting configuration information is sent by F1 interface application protocol signaling.
[0192] (Appendix 28) 18. The method according to claim 17, comprising: The congestion report message is sent by F1 interface application protocol signaling.
[0193] (Appendix 29) 29. The method according to claim 28, comprising: A method for transmitting the congestion report message in an IAB procedure newly added to the F1 interface application protocol.
[0194] (Appendix 30) 18. The method according to claim 17, comprising: A method, wherein the congestion report message is carried in a Radio Resource Control (RRC) message regarding uplink loading conditions.
[0195] (Appendix 31) 27. The method according to claim 26, comprising: The donor central unit (IAB-donor CU) sends congestion reporting configuration information to the IAB node (IAB) by dedicated signaling in a Radio Resource Control (RRC) message.
Claims
1. A signal transmitting / receiving device applied to an IAB (Integrated Access and Backhaul) node (IAB-node), comprising: a transmitter for transmitting a congestion report message to a donor central unit (IAB-donor CU) of the IAB node; the congestion report message is used to indicate a load condition of a communication link of the IAB node; the congestion report message includes an information element, the information element being used to carry a list of congestion status information; The device, wherein the granularity of the congestion status information is for each backhaul radio link control channel, and / or for each routing ID, and / or for each communication link.
2. 2. The apparatus of claim 1, The content of the congestion report message is: Buffer size; and / or Buffer occupancy; and / or available buffer size; and / or available data rate; and / or The apparatus further comprises information indicative of congestion occurring on the communication link.
3. 2. The apparatus of claim 1, The transmitter further transmits a congestion clear indication to the donor central unit; The congestion clear indication information is used to indicate that the communication link of the IAB node is in a non-congested state.
4. 2. The apparatus of claim 1, The congestion state information is A Next-Hop BAP Address for identifying said communication link; and / or An apparatus comprising a backhaul radio link control channel (BH RLC CH) ID.
5. 2. The apparatus of claim 1, When the IAB node receives request information of the donor central unit or when a predetermined condition of the IAB node is satisfied, the IAB node sends the congestion report message.
6. 6. The apparatus of claim 5, The apparatus, wherein the request information includes a granularity of congestion status information in the congestion report message, and / or a backhaul radio link control channel indicator, and / or a routing indicator, and / or a link indicator in the congestion status information.
7. 6. The apparatus of claim 5, The predetermined condition is: A buffer load corresponding to the granularity of the congestion status information in the congestion report message exceeds a first threshold and continues for a first period of time; or and within a second time period, a number of instances of Backhaul Adaptation Protocol Control Protocol Sublayer flow control feedback transmitted due to a buffer load of the IAB node for a same indicator exceeding a second threshold exceeds a third threshold.
8. 2. The apparatus of claim 1, A receiver for receiving congestion reporting configuration information transmitted by the donor central unit, An apparatus, wherein the congestion report setting information is used to set parameters required for predetermined conditions for the IAB node to determine the timing of transmitting the congestion report message, and / or parameters or settings required for the IAB node to transmit the congestion report message.
9. 9. The apparatus of claim 8, The congestion reporting configuration information is received by F1 interface application protocol signaling.
10. 2. The apparatus of claim 1, The congestion report message is transmitted by F1 interface application protocol signaling.
11. 11. The apparatus of claim 10, A device that transmits the congestion report message in a gNB-DU Status Indication procedure.
12. 2. The apparatus of claim 1, For uplink load conditions, the congestion report message is carried in a radio resource control message.
13. 9. The apparatus of claim 8, The congestion reporting configuration information is received by dedicated signaling in an RRC message.
14. A device for transmitting and receiving signals, applied to a donor central unit of an IAB node, comprising: a receiver for receiving a congestion report message transmitted by an IAB node; the congestion report message is used to indicate a load condition of a communication link of the IAB node; the congestion report message includes an information element, the information element being used to carry a list of congestion status information; The device, wherein the granularity of the congestion status information is for each backhaul radio link control channel, and / or for each routing ID, and / or for each communication link.
15. 15. The apparatus of claim 14, The content of the congestion report message is: Buffer size; and / or Buffer occupancy; and / or available buffer size; and / or available data rate; and / or The apparatus further comprises information indicative of congestion occurring on the communication link.
16. 15. The apparatus of claim 14, When the granularity of the congestion status information is each backhaul radio link control channel or each communication link, the congestion status information further includes information for indicating an uplink or a downlink.
17. 15. The apparatus of claim 14, a transmitter for transmitting request information to the IAB node; An apparatus that receives the congestion report message sent by the IAB node when the request information is sent.
18. 15. The apparatus of claim 14, a transmitter for transmitting congestion reporting configuration information to the IAB node; An apparatus, wherein the congestion report setting information is used to set parameters required for predetermined conditions for the IAB node to determine the timing of transmitting the congestion report message, and / or parameters or settings required for the IAB node to transmit the congestion report message.
Citation Information
Patent Citations
Backpressure signaling for wireless communications
WO2019190650A1
