IP Library › Granted Patent US 12,610,418
Granted Patent B2
US 12,610,418 · App. 17/797,376 · Granted Apr 21, 2026

Updating radio resource control connections in IAB network

Inventor: Atsushi Ishii (Vancouver, WA)
Assignee: SHARP KABUSHIKI KAISHA
H04W76/19H04W36/0033H04W36/0064
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,610,418
App. No.
17/797,376
Granted
Apr 21, 2026
Kind
B2
Abstract

An IAB node communicates over at least two radio interfaces including a first interface and a second interface, the first interface being configured to establish a radio resource control (RRC) connection with a donor node, the second interface being configured to serve one or more cells to communicate with one or more child nodes. In an example embodiment and mode the IAB node comprises processor circuitry and transmitter circuitry. The processor circuitry is configured to establish an RRC connection with a first donor node, and perform an update of the RRC connection to be used for a second donor node. The transmitter circuitry is configured to transmit, using the second interface, a re-establishment indication, upon performing the update of the RRC connection. The re-establishment indication is used to request that each of the one or more child nodes initiate an RRC re-establishment procedure. During the RRC re-establishment procedure, the one or more cells are considered as candidate cells.

Claims (17)

1 . An integrated access and backhaul (IAB) node which communicates over at least two radio interfaces including a first interface and a second interface, the first interface being configured to establish a radio resource control (RRC) connection with at least one donor node, the second interface being configured to serve one or more cells to communicate with one or more child nodes, the IAB node comprising:

processor circuitry configured to:

establish an RRC connection with a first donor node, and

perform an update of the RRC connection to be used for a second donor node; and

transmitter circuitry configured to transmit, using the second interface, a re-establishment indication upon performing the update of the RRC connection,

wherein:

the re-establishment indication is used to request that each of the one or more child nodes initiates an RRC re-establishment procedure, and

the RRC re-establishment procedure is performed, by each of the one or more child nodes based on the re-establishment indication, without avoiding or de-prioritizing the one or more cells.

2 . The IAB node of claim 1 , wherein performing the update of the RRC connection includes performing an RRC re-establishment procedure to connect to the second donor node.

3 . The IAB node of claim 1 , wherein the update of the RRC connection includes an RRC reconfiguration and performing the update of the RRC connection comprises performing a sync procedure to sync to the second donor node.

4 . The IAB node of claim 1 , wherein the second donor node is different from the first donor node.

5 . The IAB node of claim 1 , wherein the re-establishment indication is different from a backhaul radio link failure (RLF) indication, the backhaul RLF indication being used to inform the one or more child nodes of a failure of a recovery from an RLF.

6 . A child node that communicates with an integrated access and backhaul (IAB) node, the child node comprising:

receiver circuitry configured to receive, from the IAB node, a re-establishment indication; and

processor circuitry configured to initiate an RRC re-establishment procedure based on the re-establishment indication,

wherein the RRC re-establishment procedure is performed without avoiding or de-prioritizing one or more cells served by the IAB node.

7 . The child node of claim 6 , wherein the re-establishment indication is different from a backhaul radio link failure (RLF) indication, the backhaul RLF indication being used to notify that the IAB node fails to recover from an RLF.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 30, 2022
From: ISHII, ATSUSHI
To: SHARP KABUSHIKI KAISHA
Reel/Frame 061262/0734 →
Continuity (2)
Provisional Application 62975687 · Feb 12, 2020
Related Publication 20230098848A1 · Mar 30, 2023
References Cited (29)
US 20210160735A1 · Fujishiro · 2021 [cited by examiner]
US 20220191960A1 · Wu · 2022 [cited by examiner]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn application protocol (XnAP)(Release 16)”, 3GPP TS 38.423 V16.0.0 (Dec. 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification(Release 15)”, 3GPP TS 38.331 V15.8.0 (Dec. 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP)(Release 16)”, 3GPP TS 38.473 V16.0.0 (Dec. 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Link Control (RLC) protocol specification(Release 15)”, 3GPP TS 38.322 V15.5.0 (Mar. 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification(Release 15)”, 3GPP TS 38.323 V15.6.0 (Jun. 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E-UTRA and NR; Service Data Adaptation Protocol (SDAP) specification(Release 15)”, 3GPP TS 37.324 V15.1.0 (Sep. 2018). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2(Release 16)”, 3GPP TS 38.300 V16.0.0 (Dec. 2019). [cited by applicant]
LG Electronics, “Resolving open issues on BH RLF”, R2-1916169, 3GPP TSG-RAN WG2 Meeting #108, Reno, USA, Nov. 17-23, 2019. [cited by applicant]
LG Electronics, “BH RLF Notification Terminaton Layer”, R2-1916168, 3GPP TSG-RAN WG2 Meeting #108, Reno, USA, Nov. 17-23, 2019. [cited by applicant]
Futurewei, “Cell Selection for Backhaul RLF Recovery”, R2-1916061, 3GPP TSG-RAN WG2 meeting #108, Reno, Nevada, USA Nov. 18-22, 2019. [cited by applicant]
Samsung, “Remaining issues on IAB RLF”, R2-1916057, 3GPP TSG RAN WG2 Meeting #108, Reno, USA, Nov. 18-22, 2019. [cited by applicant]
Ericsson, “Further details on Backhaul link RLF Notification Types to Downstream Node(s)”, R2-1915783, 3GPP TSG-RAN WG2 #108, Reno, USA, Nov. 18-22, 2019. [cited by applicant]
Sharp, “Issue of loop topology after RLF”, R2-1915766, 3GPP TSG RAN WG2 Meeting #108, Reno, NV, U.S.A., Nov. 18-22, 2019. [cited by applicant]
Nokia et al., “BH link failure handling”, R2-1915700, 3GPP TSG-RAN WG2 Meeting #108, Reno, USA, Nov. 18-22, 2019. [cited by applicant]
Kyocera, “Possible issues on Backhaul RLF handling”, R2-1915598, 3GPP TSG-RAN WG2 #108, Reno, USA, Nov. 18-22, 2019. [cited by applicant]
Ericsson, “Further details on Backhaul link RLF Notification Types to Downstream Node(s)”, R2-1915477, 3GPP TSG-RAN WG2 #108, Reno, USA, Nov. 18-22, 2019. [cited by applicant]
Huawei et al., “Backhaul RLF Recovery”, R2-1915461, 3GPP TSG-RAN WG2 meeting #108, Reno, US, Nov. 18-22, 2019. [cited by applicant]
Lenovo et al., “RLF notification to downstream IAB node”, R2-1915129, 3GPP TSG-RAN WG2 Meeting #108, Reno, Nevada, USA, Nov. 18-22, 2019. [cited by applicant]
Lenovo et al., “Cell selection for IAB RLF recovery”, R2-1915128, 3GPP TSG-RAN WG2 Meeting #108, Reno, Nevada, USA, Nov. 18-22, 2019. [cited by applicant]
Zte et al., “Discussion on IAB BH RLF handling”, R2-1915119, 3GPP TSG RAN WG2 Meeting #108, Reno, USA, Nov. 18-22, 2019. [cited by applicant]
Zte et al., “Discussion on BAP control PDU”, R2-1915115, 3GPP TSG RAN WG2 Meeting #108, Reno, USA, Nov. 18-22, 2019. [cited by applicant]
Nec, “IAB backhaul RLF handling”, R2-1914975, 3GPP TSG-RAN WG2 #108, Reno, USA, Nov. 18-22, 2019. [cited by applicant]
Vivo, “Discussion on IAB BH RLF report mechanism”, R2-1914920, 3GPP TSG-RAN WG2 Meeting #108, Reno, USA, Nov. 18-22, 2019. [cited by applicant]
Kimba Dit Adamou et al., “LS on BH RLF notification verification”, R2-1914919, 3GPP TSG-RAN WG2 Meeting #108, Reno, USA, Nov. 18-22, 2019. [cited by applicant]
Vivo, “Remaining issues on BH RLF notification ”, R2-1914918, 3GPP TSG-RAN WG2 Meeting #108, Reno, USA, Nov. 18-22, 2019. [cited by applicant]
Intel Corporation, “Further discussion on Backhaul RLF handling”, R2-1914737, 3GPP TSG RAN WG2 Meeting #108, Reno, U.S.A., Nov. 18-22, 2019. [cited by applicant]
Catt, “On Remaining Open Issues of IAB BH RLF”, R2-1914383, 3GPP TSG-RAN WG2 Meeting#108, Reno, USA, Nov. 18-22, 2019. [cited by applicant]