Granted Patent B2

US 12,470,976 · App. 18/145,382 · Granted Nov 11, 2025

Inventors: Weiwei Wang (Beijing, CN); Hong Wang (Beijing, CN); Lixiang Xu (Beijing, CN)

Assignee: Samsung Electronics Co., Ltd.

H04W28/0273H04W28/0284H04W88/08

Abstract

Claims (76)

1 . A method performed by a first integrated access and backhaul (IAB) node which is a F1-terminating IAB donor node in a wireless communication system, the method comprising:

receiving, from a second IAB node which is a non-F1-terminating IAB donor node, a first message including backhaul (BH) related information for a non-F1-terminating topology associated with the second IAB node, wherein the BH related information includes at least one of information on an identity of a BH radio link control (RLC) channel, or information on a next-hop backhaul adaptation protocol (BAP) address; and

transmitting, to a third IAB node which is an IAB node connected with the first IAB node and the second IAB node, a second message including configuration information for the third IAB node, wherein the configuration information includes at least one of information indicating a type of traffic as a BAP control protocol data unit (PDU), information on an egress BH channel identity, or information indicating the non-F1-terminating topology.

2 . The method of claim 1 , further comprising:

transmitting, to the second IAB node, a request message to release traffics served by the second IAB node; and

receiving, from the second IAB node, a response message as a response to the request message,

wherein the request message includes at least one of indexes of the traffics or indexes of BH information, and

wherein the response message includes information for identifying released traffics.

3 . The method of claim 1 , further comprising:

receiving, from the second IAB node, a request message to release traffics served by the IAB node; and

transmitting, to the second IAB node, a response message as a response to the request message,

wherein the request message includes at least one of an identity indexes of the traffics or indexes of BH information, and

wherein the response message includes information for identifying released traffics.

4 . The method of claim 1 , further comprising:

transmitting, to the second IAB node, threshold configuration information,

wherein the threshold configuration information includes a threshold value of a buffer size to determine a congestion.

5 . A method performed by a second integrated access and backhaul (IAB) node which is a non-F1-terminating IAB donor node in a wireless communication system, the method comprising:

transmitting, to a first IAB node which is a F1-terminating IAB donor node, a first message including backhaul (BH) related information for a non-F1-terminating topology associated with the second IAB node, wherein the BH related information includes at least one of information on an identity of a BH radio link control (RLC) channel, or information on a next-hop backhaul adaptation protocol (BAP) address,

wherein the first message is for transmitting configuration information to a third IAB node which is an IAB node connected with the first IAB node and the second IAB node, and wherein the configuration information includes at least one of information indicating a type of traffic as a BAP control protocol data unit (PDU), information on an egress BH channel identity, or information indicating the non-F1-terminating topology.

6 . The method of claim 5 , further comprising:

receiving, from the second IAB node, a request message to release traffics served by the second IAB node; and

transmitting, to the second IAB node, a response message as a response to the request message,

wherein the request message includes at least one of indexes of the traffics or indexes of BH information, and

wherein the response message includes information for identifying released traffics.

7 . The method of claim 5 , further comprising:

transmitting, to the second IAB node, a request message to release traffics served by the IAB node; and

receiving, the second IAB node, a response message as a response to the request message,

wherein the request message includes at least one of indexes of the traffics or indexes of BH information, and

wherein the response message includes information for identifying released traffics.

8 . The method of claim 5 , further comprising:

receiving, from the second IAB node, threshold configuration information,

wherein the threshold configuration information includes a threshold value of a buffer size to determine a congestion.

9 . A first integrated access and backhaul (IAB) node which is a F1-terminating IAB donor node, the first IAB node comprising:

at least one transceiver;

at least one processor communicatively coupled to the at least one transceiver; and

at least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the first IAB node to:

receive, from a second IAB node which is a non-F1-terminating IAB donor node, a first message including backhaul (BH) related information for a non-F1-terminating topology associated with the second IAB node, wherein the BH related information includes at least one of information on an identity of a BH radio link control (RLC) channel, or information on a next-hop backhaul adaptation protocol (BAP) address; and

transmit, to a third IAB node which is an IAB node connected with the first IAB node and the second IAB node, a second message including configuration information for the third IAB node, wherein the configuration information includes at least one of information indicating a type of traffic as a BAP control protocol data unit (PDU), information on an egress BH channel identity, or information indicating the non-F1-terminating topology.

10 . The first IAB node of claim 9 ,

wherein the instructions further cause the first IAB node to:

transmit, to the second IAB node, a request message to release traffics served by the second IAB node; and

receive, from the second IAB node, a response message as a response to the request message,

wherein the request message includes at least one of indexes of the traffics or indexes of BH information, and

wherein the response message includes information for identifying released traffics.

11 . The first IAB node of claim 9 ,

wherein the instructions further cause the first IAB node to:

receive, from the second IAB node, a request message to release traffics served by the IAB node; and

transmit, to the second IAB node, a response message as a response to the request message,

wherein the request message includes at least one of indexes of the traffics or indexes of BH information, and

wherein the response message includes information for identifying released traffics.

12 . The first IAB node of claim 9 ,

wherein the instructions further cause the first IAB node to:

transmit, to the second IAB node, threshold configuration information, and

wherein the threshold configuration information includes a threshold value of a buffer size to determine a congestion.

13 . A second integrated access and backhaul (IAB) node which is a non-F1-terminating IAB donor node, the second IAB node comprising:

at least one transceiver;

at least one processor communicatively coupled to the at least one transceiver; and

at least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the second IAB node to:

transmit, to a first IAB node which is a F1-terminating IAB donor node, a first message including backhaul (BH) related information for a non-F1-terminating topology associated with the second IAB node, wherein the BH related information includes information on an identity of a BH radio link control (RLC) channel, or information on a next-hop backhaul adaptation protocol (BAP) address,

wherein the first message is for transmitting configuration information to a third IAB node which is an IAB node connected with the first IAB node and the second IAB node, and wherein the configuration information includes information indicating a type of traffic as a BAP control protocol data unit (PDU), information on an egress BH channel identity, or information indicating the non-F1-terminating topology.

14 . The second IAB node of claim 13 ,

wherein the instructions further cause the second IAB node to:

receive, from the second IAB node, a request message to release traffics served by the second IAB node; and

transmit, to the second IAB node, a response message as a response to the request message,

wherein the request message includes at least one of indexes of the traffics or indexes of BH information, and

wherein the response message includes information for identifying released traffics.

15 . The second IAB node of claim 13 ,

wherein the instructions further cause the second IAB node to:

transmit, to the second IAB node, a request message to release traffics served by the IAB node; and

receive, the second IAB node, a response message as a response to the request message,

wherein the request message includes at least one of indexes of the traffics or indexes of BH information, and

wherein the response message includes information for identifying released traffics.

16 . The second IAB node of claim 13 ,

wherein the instructions further cause the second IAB node to:

receive, from the second IAB node, threshold configuration information, and

wherein the threshold configuration information includes a threshold value of a buffer size to determine a congestion.

Assignments (1)

Priority Claims (2)

Continuity (1)

References Cited (17)