IP Library › Granted Patent US 12,439,321
Granted Patent B2
US 12,439,321 · App. 18/400,683 · Granted Oct 7, 2025

Method and apparatus for transmitting data to a network node in a wireless communication system

Inventor: Milos Tesanovic (Staines, GB)
Assignee: Samsung Electronics Co., Ltd.
H04W40/22H04L45/48H04W28/0268H04W28/0284
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,439,321
App. No.
18/400,683
Granted
Oct 7, 2025
Kind
B2
Abstract

A method of operating a first node in a wireless communication network is provided. The method comprises: receiving an ingress data packet; determining routing; and transmitting the ingress data packet. Determining routing may comprise determining a next hop node for the ingress data packet taking account of first level routing information indicating target next hop nodes. Alternatively, determining routing may comprise determining, for a target next hop node, a channel on which to transmit the ingress data packet taking account of second level routing information.

Claims (50)

1. A method of operating a first node in a wireless communication network, the method comprising:

receiving a data packet;

receiving a routing information from an integrated access backhaul (IAB) donor node;

receiving a mapping information from the IAB donor node;

determining a next hop for the data packet, based on a backhaul adaptation protocol (BAP) address of the next hop comprised in the routing information;

determining an egress radio link control (RLC) channel for the data packet, based on the mapping information including the BAP address of the next hop, an identifier (ID) of an ingress RLC channel and an ID of an egress RLC channel; and

transmitting the data packet to the next hop.

2. The method of claim 1 , wherein the first node comprises an IAB node arranged to communicate backhaul traffic wirelessly with at least one of a parent node or a child node; and

wherein the data packet comprises an IAB data packet.

3. The method of claim 2 , wherein the IAB data packet is received from an uplink or downlink node.

4. The method of claim 1 , wherein for uplink communication, the routing information further comprises, for each target next hop for an uplink, a cell identifier or a cell group identifier of a cell supported by the target next hop to which the first node attaches.

5. The method of claim 1 , wherein for downlink communication the routing information comprises, for each target next hop for a downlink, at least one of:

a cell-radio network temporary identifier (C-RNTI) of the target next hop;

a C-RNTI of the target next hop combined with a cell identifier or a cell group identifier of a cell supported by the first node to which the target next hop attaches; or

a BAP address of the target next hop.

6. The method of claim 5 , wherein the BAP address of the target next hop comprises an IAB specific address.

7. The method of claim 5 , wherein the routing information is dynamically assigned according to whether the BAP address of the target next hop is shorter than the C-RNTI or the C-RNTI combined with the cell identifier or the cell group identifier.

8. The method according to claim 7 , further comprising deciding which identifier to use from among the C-RNTI or the C-RNTI combined with the cell identifier or the cell group identifier, based on signaling incurred by a required reconfiguration.

9. The method of claim 1 , wherein the mapping information comprises a unique identifier assigned to each RLC channel by the IAB donor node.

10. The method of claim 1 , wherein the determining of the next hop comprises determining the next hop based on at least one of:

current status of egress backhaul (BH) links; or

feedback received from child nodes on downstream congestion.

11. A first node in a wireless communication network, the first node comprising:

a transceiver; and

at least one processor operably coupled with the transceiver, the at least one processor configured to:

receive, by controlling the transceiver, a data packet;

receive, by controlling the transceiver, a routing information from an integrated access backhaul (IAB) donor node;

receive, by controlling the transceiver, a mapping information from the IAB donor node;

determine a next hop for the data packet, based on a BAP address of the next hop comprised in the routing information;

determine an egress RLC channel for the data packet, based on the mapping information including the BAP address of the next hop, an ID of an ingress RLC channel and an ID of an egress RLC channel; and

transmit, by controlling the transceiver, the data packet to the next hop.

12. The first node of claim 11 , wherein the first node is an IAB node arranged to communicate backhaul traffic wirelessly with at least one of a parent node or a child node; and

wherein the data packet comprises an IAB data packet.

13. The first node of claim 12 , wherein the IAB data packet is received from an uplink or downlink node.

14. The first node of claim 11 , wherein for uplink communication, the routing information further comprises, for each target next hop for an uplink, a cell identifier or a cell group identifier of a cell supported by the target next hop to which the first node attaches.

15. The first node of claim 11 , wherein for downlink communication the routing information comprises, for each target next hop for a downlink, at least one of:

a cell-radio network temporary identifier (C-RNTI) of the target next hop;

a C-RNTI of the target next hop combined with a cell identifier or a cell group identifier of a cell supported by the first node to which the target next hop attaches; or

a BAP address of the target next hop.

16. The first node of claim 15 , wherein the BAP address of the target next hop comprises an IAB specific address.

17. The first node of claim 15 , wherein the routing information is dynamically assigned according to whether the BAP address of the target next hop is shorter than the C-RNTI or the C-RNTI combined with the cell identifier or the cell group identifier.

18. The first node of claim 17 , wherein the at least one processor is further configured to decide which identifier to use from among the C-RNTI or the C-RNTI combined with the cell identifier or the cell group identifier, based on signaling incurred by a required reconfiguration.

19. The first node of claim 11 , wherein the mapping information comprises a unique identifier assigned to each RLC channel by the IAB donor node.

20. A non-transitory computer readable storage medium comprising instructions that, when executed by a processor of a first node, cause the first node to:

receive a data packet;

receive a routing information from an integrated access backhaul (IAB) donor node;

receive a mapping information from the IAB donor node;

determine a next hop for the data packet, based on a BAP address of the next hop comprised in the routing information;

determine an egress RLC channel for the data packet, based on the mapping information including the BAP address of the next hop, an identifier (ID) of an ingress RLC channel and an ID of an egress RLC channel; and

transmit the data packet to the next hop.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 29, 2023
From: TESANOVIC, MILOS
To: SAMSUNG ELECTRONICS CO., LTD.
Reel/Frame 065983/0688 →
Priority Claims (1)
GB 1906212 · May 2, 2019 · national
Continuity (3)
Continuation 15929417 · Apr 30, 2020
Related Publication 20240137837A1 · Apr 25, 2024
Related Publication 20240236811A9 · Jul 11, 2024
References Cited (58)
US 9049137B1 · Markine · 2015 [cited by examiner]
US 20070072604A1 · Wang · 2007 [cited by applicant]
US 20070280258A1 · Rajagopalan et al. · 2007 [cited by applicant]
US 20090129323A1 · Chen et al. · 2009 [cited by applicant]
US 20100157888A1 · Aggarwal et al. · 2010 [cited by applicant]
US 20110019669A1 · Ma et al. · 2011 [cited by applicant]
US 20130322457A1 · Budhia et al. · 2013 [cited by applicant]
US 20140169265A1 · Park et al. · 2014 [cited by applicant]
US 20160154756A1 · Dodson et al. · 2016 [cited by applicant]
US 20170188400A1 · Tian et al. · 2017 [cited by applicant]
US 20180063827A1 · Soysal et al. · 2018 [cited by applicant]
US 20180092139A1 · Novlan et al. · 2018 [cited by applicant]
US 20180159702A1 · Song · 2018 [cited by applicant]
US 20180337846A1 · Lee et al. · 2018 [cited by applicant]
US 20180359802A1 · Cho et al. · 2018 [cited by applicant]
US 20190007185A1 · Cao et al. · 2019 [cited by applicant]
US 20190098673A1 · Goyal et al. · 2019 [cited by applicant]
US 20200120725A1 · Mildh et al. · 2020 [cited by applicant]
US 20200314014A1 · Calciu et al. · 2020 [cited by applicant]
US 20200351750A1 · Majmundar et al. · 2020 [cited by applicant]
US 20200351930A1 · Luo et al. · 2020 [cited by applicant]
US 20200382982A1 · Yao et al. · 2020 [cited by applicant]
US 20210014768A1 · Hong · 2021 [cited by applicant]
US 20210092667A1 · Zhu et al. · 2021 [cited by applicant]
US 20210105698A1 · Jactat · 2021 [cited by applicant]
US 20210126991A1 · Huang et al. · 2021 [cited by applicant]
US 20210235291A1 · Byun et al. · 2021 [cited by applicant]
US 20210377805A1 · Liu · 2021 [cited by examiner]
US 20210377930A1 · Liu · 2021 [cited by examiner]
US 20220014976A1 · Luo · 2022 [cited by examiner]
US 20240073158A1 · Agrawal · 2024 [cited by examiner]
CN 108353039A · 2018 [cited by applicant]
CN 110475267A · 2019 [cited by applicant]
CN 110505160A · 2019 [cited by applicant]
CN 111727662A · 2020 [cited by applicant]
CN 109842440B · 2021 [cited by applicant]
CN 111865802B · 2022 [cited by applicant]
EP 3813320A1 · 2021 [cited by applicant]
EP 3813460A1 · 2021 [cited by applicant]
GB 2574875A · 2019 [cited by applicant]
JP 2014138215A · 2014 [cited by applicant]
WO 2018212845A1 · 2018 [cited by applicant]
WO 2019139524A1 · 2019 [cited by applicant]
WO 2019141356A1 · 2019 [cited by applicant]
Communication under Rule 71(3) EPC dated Jun. 26, 2024, in connection with European Application No. 20799331.2, 35 pages. [cited by applicant]
The First Office Action dated Sep. 10, 2024, in connection with Chinese Application No. 202080031307.1, 16 pages. [cited by applicant]
3GPP TR 38.874 1.0.0 (Dec. 2018), Technical Report, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on Integrated Access and Backhaul; (Release 15), 2018, 111 pages. [cited by applicant]
Samsung, “Qos framework in IAB network,” R3-190437, 3GPP TSG-RAN WG3 Meeting #103, Athens, Greece, Feb. 25-Mar. 1, 2019, 7 pages. [cited by applicant]
3GPP TR 38.874 V16.0.0 (Dec. 2018), Technical Report, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Study on Integrated Access and Backhaul; (Release 16), Dec. 2018, 111 pag… [cited by applicant]
International Search Report and the Written Opinion of the International Searching Authority dated Aug. 26, 2020, in connection with International Patent Application No. PCT/KR2020/005634, 12 pages. [cited by applicant]
Supplementary European Search Report dated May 13, 2022, in connection with European Patent Application No. 20799331.2, 10 pages. [cited by applicant]
Search Report dated Oct. 17, 2019, in connection with United Kingdom Patent Application No. GB1906212.4, 2 pages. [cited by applicant]
Examination Report under Section 18(3) dated Aug. 5, 2021, in connection with United Kingdom Patent Application No. GB 1906212.4, 3 pages. [cited by applicant]
Ericsson, “Backhaul Link Identifier for Packet Forwarding in IAB Networks,” R2-1903959, 3GPP TSG-RAN WG2 Meeting #105bis, Apr. 8-12, 2019, 3 pages. [cited by applicant]
Huawei et al., “Routing function and configuration,” R2-1905115, 3GPP TSG-RAN WG2 meeting #105bis, Apr. 8-12, 2019, 6 pages. [cited by applicant]
ZTE Corporation et al., “Consideration on Routing in IAB,” R2-1904601, 3GPP TSG-RAN WG2 #105bis, Apr. 8-12, 2019, 4 pages. [cited by applicant]
Communication under Rule 71(3) EPC dated Nov. 18, 2024, in connection with European Patent Application No. 20799331.2, 34 pages. [cited by applicant]
Communication under Rule 71(3) EPC dated Apr. 16, 2025, in connection to European Application No. 20799331.2, 33 pages. [cited by applicant]
Cited By (1)
US 12,696,171