IP Library Granted Patent US 12,526,724
Granted Patent B2
US 12,526,724 · App. 18/370,432 · Granted Jan 13, 2026

Information transceiving method, data transmission method and apparatuses thereof

Inventors: Su Yi (Beijing, CN); Yang Lu (Beijing, CN); Meiyi Jia (Beijing, CN)
Assignee: 1FINITY Inc.
H04W40/22H04L45/02H04W40/04
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,526,724
App. No.
18/370,432
Granted
Jan 13, 2026
Kind
B2
Abstract

An information transceiving apparatus, applicable to a first IAB-donor-node, includes a transmitter configured to transmit a first message to a second IAB-donor-node, the first message comprising a BAP address of a first node in topology of the first IAB-donor-node, and a receiver configured to receive a second message transmitted by the second IAB donor node, the second message comprising a BAP Routing ID in topology of the second IAB donor node, and a processor configured to configure BAP routing entries for nodes in its topology according to the second message.

Claims (27)

1 . An information transceiving apparatus, applicable to a first IAB (Integrated Access and Backhaul)-donor-node, the apparatus comprises: a transmitter configured to transmit a first message to a second IAB-donor-node, the first message comprising a BAP (Backhaul Adaptation Protocol) address of a first node in topology of the first IAB-donor-node; and a receiver configured to receive a second message transmitted by the second IAB donor node, the second message comprising a BAP Backhaul Adaptation Protocol) Routing ID in topology of the second IAB donor node;

and a processor configured to configure BAP routing entries for nodes in its topology according to the second message.

2 . The apparatus according to claim 1 , wherein:

the first IAB donor node is an F1-terminating donor of a third IAB node, and the second IAB donor node is a non-F1-terminating donor of the third IAB node.

3 . The apparatus according to claim 2 , wherein:

the third IAB node is a boundary IAB node, and the third IAB node needs to establish inter-donor topology redundancy for traffic offload from the F1-terminating donor to the non-F1-terminating donor.

4 . The apparatus according to claim 1 , wherein the BAP routing entries comprise a BAP Routing ID, the BAP Routing ID comprising a BAP address of an IAB-donor-DU in the topology of the second IAB-donor-node.

5 . The apparatus according to claim 1 , wherein the first message and the second message are carried by XnAP signaling.

6 . The apparatus according to claim 2 , wherein the transmitter further transmits routing mapping relationship configuration information configured according to the second message to the third IAB-node, wherein

the routing mapping relationship configuration information indicating a correspondence between a first routing ID in the topology of the first IAB donor node taken as an ingress routing ID and a second routing ID in the topology of the second IAB-donor-node taken as an egress routing ID; or

the routing mapping relationship configuration information indicating a correspondence between a second routing ID in the topology of the second IAB-donor-node taken as an ingress routing ID and a first routing ID in the topology of the first IAB-donor-node taken as an egress routing ID.

7 . The apparatus according to claim 6 , wherein the routing mapping relationship configuration information is carried by F1AP signaling.

8 . The apparatus according to claim 7 , wherein the F1AP signaling comprises:

one or multiple information elements included in BAP MAPPING CONFIGURATION message to add and/or remove the routing mapping relationship configuration information.

9 . The apparatus according to claim 8 , wherein the one or multiple information elements comprise:

an Ingress BAP Routing ID representing the BAP Routing ID to be rewritten; and

an Egress BAP Routing ID representing the BAP Routing ID used to write in BAP header.

10 . The apparatus according to claim 2 , wherein the processer configures the BAP routing entries for descendant nodes of the third IAB node.

11 . The apparatus according to claim 2 , wherein the processor further configures a mapping information of an uplink traffic type to the BAP Routing ID on descendant nodes of the third IAB node.

12 . The apparatus according to claim 11 , wherein the BAP Routing ID includes a BAP address of an IAB-donor-DU in the topology of the second IAB donor node.

13 . An information transceiving apparatus, applicable to a second IAB (Integrated Access and Backhaul)-donor-node, the apparatus comprises: a receiver configured to receive a first message transmitted by the first IAB-donor-node, the first message comprising a BAP (Backhaul Adaptation Protocol) address of a first node in topology of the first IAB-donor-node; a transmitter configured to transmit a second message to a first IAB donor node, the second message comprising a BAP Routing ID in topology of the second IAB donor node; and a processor configured to configure BAP routing entries for nodes in its topology.

14 . The apparatus according to claim 13 , wherein the processor further configures a mapping of an IP header information to the BAP Routing ID for downlink traffic on an IAB-donor-DU in the topology of the second IAB donor node.

15 . The apparatus according to claim 14 , wherein the mapping is carried in IP-to-layer-2 traffic mapping Information List information element in a BAP MAPPING CONFIGURATION message via F1AP signaling.

16 . A data transmission apparatus, applicable to a third IAB (Integrated Access and Backhaul)-node, the apparatus comprises: a third receiver configured to receive a BAP (Backhaul Adaptation Protocol) Data PDU (Protocol Data Unit); rewriting processor circuitry configured to perform BAP Routing ID rewriting on a BAP header in the BAP Data PDU according to routing mapping relationship configuration information when a predetermined condition is satisfied, wherein the rewriting processor circuitry replaces a BAP Routing ID in the BAP header with an Egress BAP Routing ID in the routing mapping relationship configuration information; and forwarding processor circuitry configured to forward the rewritten BAP Data PDU.

17 . The apparatus according to claim 16 , wherein the predetermined condition is that a DESTINATION field in the BAP Data PDU is not a BAP address of the third IAB node, and the BAP Routing ID in the BAP header matches the Ingress BAP Routing ID in the routing mapping relationship configuration information.

18 . The apparatus according to claim 17 , wherein the BAP address of the third IAB node is allocated by the second IAB donor node via RRCReconfiguration message.

19 . The apparatus according to claim 16 , wherein when a DESTINATION field in the BAP Data PDU is the BAP address of the third IAB node, the third IAB node transmits a BAP SDU with a BAP header being removed to an upper layer.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 3, 2025
From: FUJITSU LIMITED
To: 1FINITY INC.
Reel/Frame 073477/0445 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 20, 2023
From: YI, SU; LU, YANG; JIA, MEIYI
To: FUJITSU LIMITED
Reel/Frame 064963/0249 →
Continuity (2)
Continuation PCTCN2021084790 · Mar 31, 2021
Related Publication 20240015633A1 · Jan 11, 2024
References Cited (16)
US 20210051512A1 · Hampel · 2021 [cited by examiner]
US 20210058826A1 · Mao et al. · 2021 [cited by applicant]
US 20210127351A1 · Stojanovski · 2021 [cited by examiner]
US 20230106809A1 · Wu · 2023 [cited by examiner]
CN 110536351A · 2019 [cited by applicant]
CN 112398589A · 2021 [cited by applicant]
Notice of Reasons for Refusal issued by the Japan Patent Office for corresponding Japanese Patent Application No. 2023-559856, mailed on Sep. 17, 2024, with an English translation. [cited by applicant]
International Search Report and Written Opinion of the International Searching Authority issued by the China National Intellectual Property Administration for corresponding International Patent Application No. PCT/CN202… [cited by applicant]
LG Electronics, Inc., “Open Issues on topological redundancy for IAB”, Agenda Item: 13.2.3, 3GPP TSG-RAN WG3 Meeting #110-e, R3-206072, E-Meeting, Nov. 2-12, 2020. [cited by applicant]
ZTE et al., “Considerations on topology adaptation enhancements in IAB”, Agenda Item: 8.4.3, 3GPP TSG-RAN WG2 Meeting #113 electronic, R2-2101283, Online, Jan. 25-Feb. 5, 2021. [cited by applicant]
LG Electronics, Inc., “Considerations on topological redundancy for IAB”, Agenda Item: 13.2.3, 3GPP TSG-RAN WG3 Meeting #111-e, R3-210536, E-Meeting, Jan. 25-Feb. 4, 2021. [cited by applicant]
3GPP TS 38.300 V16.2.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 16)”, Jul. 2020. [cited by applicant]
3GPP TS 38.340 V16.2.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Backhaul Adaptation Protocol (BAP) specification (Release 16)”, Sep. 2020. [cited by applicant]
The Extended European search report with the Supplementary European search report and the European search opinion, issued by the European Patent Office for corresponding European Patent Application No. 21933911.6, maile… [cited by applicant]
Qualcomm Incorporated, “IAB enhancements for inter-donor topological redundancy”, Agenda Item: 13.2.3, 3GPP TSG-RAN WG3 Meeting #110-e, R3-206258, E-meeting, Nov. 2-12, 2020. [cited by applicant]
SAMSUNG (moderator), “Summary of offline discussion on topology redundancy”, Agenda Item: 13.2.3 (Topology Redundancy), 3GPP TSG-RAN WG3 #110-e, R3-207101, Online, Nov. 2-12, 2020. [cited by applicant]