IP Library Granted Patent US 12,336,018
Granted Patent B2
US 12,336,018 · App. 17/441,631 · Granted Jun 17, 2025

Random access channel configuration in an integrated access and backhaul network

Inventors: Lili Wei (Portland, OR); Qian Li (Beaverton, OR); Geng Wu (Portland, OR)
Assignee: Apple Inc.
H04W74/0841H04W72/0446H04W74/0866H04W76/20H04W88/14
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,336,018
App. No.
17/441,631
Granted
Jun 17, 2025
Kind
B2
Abstract

Disclosed are methods, systems, apparatus, and computer programs for communicating new random access channel (RACH) configurations for a node in an integrated access and backhaul (IAB) network. In one aspect, a method includes receiving a Radio Resource Control (RRC) message from the IAB node; determining, based on the RRC message, a new random access channel (RACH) configuration; and in response to determining the new RACH configuration, initiating a random access procedure with the IAB node using the new RACH configuration.

Claims (42)

1. A method comprising:

receiving, by a first integrated access and backhaul (IAB) node, a Radio Resource Control (RRC) message from a second IAB node, the RRC message comprising an information element (IE) having fields specifying a slot offset and a subframe offset of a backhaul random access channel (RACH) periodicity to an existing RACH configuration, wherein the slot offset comprises a prach-SlotOffset field specifying a slot-based offset of the backhaul RACH periodicity to the existing RACH configuration, and the subframe offset comprises a prach-SubframeOffset field specifying a subframe-based offset of the backhaul RACH periodicity to the existing RACH configuration;

determining, while maintaining the existing RACH configuration, a new RACH configuration that includes the slot offset and the subframe offset from the RRC message; and

in response to determining the new RACH configuration:

determining to stop using the existing RACH configuration; and

initiating a random access procedure with the IAB node using the new RACH configuration with the slot offset and the subframe offset, the initiating comprising determining a new slot number or a new subframe number based at least on the slot offset or the subframe offset, an existing slot number or an existing subframe number for the existing RACH configuration, and a number of slots or subframes in a frame.

2. The method of claim 1 , wherein determining, based on the RRC message, the new RACH configuration comprises:

determining a scaling factor that has a value selected from {1, 2, 4, 8, 16, 32, 64} based on the RRC message.

3. The method of claim 2 , wherein the scaling factor defines an adjustment to the periodicity included in the existing RACH configuration associated with the IAB node.

4. The method of claim 1 , wherein determining, based on the RRC message, the new RACH configuration comprises:

determining a frame-based offset that has a value selected from (0 . . . 63) based on the RRC message.

5. The method of claim 4 , wherein the frame-based offset defines an adjustment to a frame number included in the existing RACH configuration associated with the IAB node, wherein the frame number identifies a frame containing backhaul traffic.

6. The method of claim 1 , wherein determining, based on the RRC message, the new RACH configuration comprises:

determining the slot offset or the subframe offset based on the RRC message.

7. The method of claim 6 , wherein the slot offset or the subframe offset defines an adjustment to the existing slot number or the existing subframe number included in the existing RACH configuration, wherein the existing slot number or the existing subframe number identifies a slot or a subframe containing backhaul traffic.

8. The method of claim 1 , wherein the RRC message is a RACH-ConfigGeneric message.

9. The method of claim 1 , wherein the RRC message is a RACH-ConfigDedicated message.

10. The method of claim 1 , wherein the RRC message comprises one or more of:

a prach-scalingFactor field specifying a scaling factor of the backhaul RACH periodicity to the existing RACH configuration, or

a prach-FrameOffset field specifying a frame-based offset of the backhaul RACH periodicity to the existing RACH configuration.

11. A method comprising:

determining, by an apparatus for an integrated access and backhaul (IAB) node with an existing random access channel (RACH) configuration, a new RACH configuration that includes a slot offset and a subframe offset;

generating, in response to determining the new RACH configuration for the IAB node, a message comprising an information element (IE) having fields specifying a slot offset and a subframe offset of a backhaul RACH periodicity to the existing RACH configuration, wherein the slot offset comprises a prach-SlotOffset field specifying a slot-based offset of the backhaul RACH periodicity to the existing RACH configuration, and the subframe offset comprises a prach-SubframeOffset field specifying a subframe-based offset of the backhaul RACH periodicity to the existing RACH configuration; and

transmitting the message comprising the slot offset and the subframe offset to the IAB node to cause the IAB node to determine a new slot number or a new subframe number for the new RACH configuration based at least on the slot offset or the subframe offset, an existing slot number or an existing subframe number for the existing RACH configuration, and a number of slots or subframes in a frame.

12. The method of claim 11 , wherein:

the new RACH configuration includes a scaling factor that has a value selected from {1, 2, 4, 8, 16, 32, 64}; and

generating the message comprises generating the message comprising a) the slot offset or the subframe offset for the new RACH configuration, and b) the scaling factor.

13. The method of claim 11 , wherein:

determining the new RACH configuration comprises determining the new RACH configuration that includes a frame-based offset that has a value selected from (0 . . . 63); and

generating the message comprises generating the message comprising a) the slot offset or the subframe offset for the new RACH configuration, and b) the frame-based offset.

14. The method of claim 11 , wherein the new RACH configuration includes the slot offset or the subframe offset that identifies a slot or a subframe containing backhaul traffic.

15. The method of claim 11 , wherein the message is a Radio Resource Control (RRC) message.

16. The method of claim 15 , wherein the RRC message is a RACH-ConfigGeneric message.

17. The method of claim 15 , wherein the RRC message is a RACH-ConfigDedicated message.

18. The method of claim 11 , wherein determining, by the apparatus, the RACH configuration comprises determining, by an IAB parent node or by one or more processors, the RACH configuration.

19. An apparatus comprising one or more processors configured to perform operations comprising:

determining, for an integrated access and backhaul (IAB) node with an existing random access channel (RACH) configuration, a new RACH configuration that includes a slot offset and a subframe offset;

generating, in response to determining the new RACH configuration for the IAB node, a message comprising an information element (IE) having fields specifying a slot offset and a subframe offset of a backhaul RACH periodicity to the existing RACH configuration, wherein the slot offset comprises a prach-SlotOffset field specifying a slot-based offset of the backhaul RACH periodicity to the existing RACH configuration, and the subframe offset comprises a prach-SubframeOffset field specifying a subframe-based offset of the backhaul RACH periodicity to the existing RACH configuration; and

transmitting the message comprising the slot offset and the subframe offset to the IAB node to cause the IAB node to determine a new slot number or a new subframe number for the new RACH configuration based at least on the slot offset or the subframe offset, an existing slot number or an existing subframe number for the existing RACH configuration, and a number of slots or subframes in a frame.

20. The apparatus of claim 19 , wherein:

the new RACH configuration includes a scaling factor that has a value selected from {1, 2, 4, 8, 16, 32, 64}; and

generating the message comprises generating the message comprising a) the slot offset or the subframe offset for the new RACH configuration, and b) the scaling factor.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 20, 2022
From: INTEL CORPORATION
To: APPLE INC.
Reel/Frame 061730/0163 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 6, 2022
From: WEI, LILI; LI, QIAN; WU, GENG
To: INTEL CORPORATION
Reel/Frame 061335/0204 →
Continuity (2)
Provisional Application 62842417 · May 2, 2019
Related Publication 20220150983A1 · May 12, 2022
References Cited (47)
US 20200015274A1 · Islam · 2020 [cited by examiner]
US 20210298088A1 · Qi · 2021 [cited by examiner]
US 20210400661A1 · Harada · 2021 [cited by examiner]
CN 105075146 · 2015 [cited by applicant]
CN 108353342 · 2018 [cited by applicant]
Samsung (Support of RACH Occasions and Periodicity for IAB RACH, R1-1904416, Apr. 2019). [cited by examiner]
Qualcomm (Enhancements to support NR backhaul links, R1-1813417, Nov. 2018). [cited by examiner]
Qualcomm005 (Updated proposal for RACH extension for IAB, R1-1905005, Apr. 2019). [cited by examiner]
[No Author Listed], “3GPP TR 38.874 V 16.0.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Study on Integrated Access and Backhual; (Release 16),” 3GPP, Dec. 2018, 11 pages. [cited by applicant]
[No Author Listed], “3GPP Ts 38.211 V 15.5.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical Channels and Modulation; (Release 15),” Mar. 2019, 96 pages. [cited by applicant]
[No Author Listed], “Chairman's notes of AI 6.2.1 Additional MTC Enhancements,” 3GPP TSG RAN WG1 Meeting #96bis, R1-1905566, Xi'an, China, Apr. 8-12, 2019, 7 pages. [cited by applicant]
[No Author Listed], “Chairman's notes of AI 6.2.2 Additional Enhancements for NB-IOT,” 3GPP TSG RAN WG1 Meeting #96bis, R1-1905567, Xi'an, China, Apr. 8-12, 2019, 5 pages. [cited by applicant]
[No Author Listed], “Chairman's notes of AI 6.2.3 DL MIMO efficiency enhancements for LTE,” 3GPP TSG RAN WG1 Meeting #96bis, R1-1905568, Xi'an, China, Apr. 8-12, 2019, 2 pages. [cited by applicant]
[No Author Listed], “Chairman's notes of AI 7.1.2 Maintenance for MIMO,” 3GPP TSG RAN WG1 Meeting #96bis, R1-1905797, Xi'an, China, Apr. 8-12, 2019, 2 pages. [cited by applicant]
[No Author Listed], “Chairman's notes of AI 7.1.5 Maintenance for UL power control, ” 3GPP TSG RAN WG1 Meeting #96bis, R1-1905799, Xi'an, China, Apr. 8-12, 2019, 1 page. [cited by applicant]
[No Author Listed], “Chairman's notes of AI 7.2.8 Enhancements on MIMO for NR,” 3GPP TSG RAN WG1 Meeting #96bis, R1-1905803, Xi'an, China, Apr. 8-12, 2019, 13 pages. [cited by applicant]
[No Author Listed], 3GPP TS 38.331 V 15.5.1, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15), Apr. 2019, 491 p… [cited by applicant]
Ad-hoc Chair (Samsung), “Chairman's notes of AI 6.2.1 Additional MTC Enhancements,” 3GPP TSG RAN WG1 Meeting #96, R1-1903664, Athens, Greece, Feb. 25-Mar. 1, 2019, 6 pages. [cited by applicant]
Ad-hoc Chair (Ericsson), “Chairman's notes of AI 6.1.1 Maintenance of E-UTRA Release 8-14,” 3GPP TSG-RAN WG1 Meeting #96 Tdoc, R1-1903524, Athens, Greece, Feb. 25-Mar. 1, 2019, 2 pages. [cited by applicant]
Ad-hoc Chair (Ericsson), “Chairman's notes of AI 6.1.1 Maintenance of E-UTRA Release 8-14,” 3GPP TSG-RAN WG1 Meeting #96bis, Tdoc R1-1905564, Xi'an, China, Apr. 8-12, 2019, 2 pages. [cited by applicant]
Ad-hoc Chair (Ericsson), “Chairman's notes of AI 6.1.2 Maintenance of E-UTRA Release 15,” 3GPP TSG-RAN WG1 Meeting #96, Tdoc R1-1903525, Athens, Greece, Feb. 25-Mar. 1, 2019, 2 pages. [cited by applicant]
Ad-hoc Chair (Ericsson), “Chairman's notes of AI 6.1.2 Maintenance of E-UTRA Release 15,” 3GPP TSG-RAN WG1 Meeting #96bis, Tdoc R1-1905565, Xi'an, China, Apr. 8-12, 2019, 1 page. [cited by applicant]
Ad-hoc Chair (Ericsson), “Chairman's notes of AI 6.2.4 LTE-based 5G Terrestrial Broadcast,” 3GPP TSG-RAN WG1 Meeting #96bis, Tdoc R1-1905569, Xi'an, China, Apr. 8-12, 2019, 3 pages. [cited by applicant]
Ad-hoc Chair (Ericsson), “Chairman's notes of AI 6.2.4 Study on LTE-based 5G Terrestrial Broadcast,” 3GPP TSG-RAN WG1 Meeting #96, Tdoc R1-1903657, Athens, Greece, Feb. 25-Mar. 1, 2019, 2 pages. [cited by applicant]
Ad-hoc Chair (Ericsson), “Chairman's notes of AI 6.2.5 Others,” 3GPP TSG-RAN WG1 Meeting #96, Tdoc R1-1903658, Athens, Greece, Feb. 25-Mar. 1, 2019, 1 page. [cited by applicant]
Ad-hoc Chair (Ericsson), “Chairman's notes of AI 7.1.4 Maintenance for NR-LTE co-existence,” 3GPP TSG-RAN WG1 Meeting #96 Tdoc, R1-1903626, Athens, Greece, Feb. 25-Mar. 1, 2019, 2 pages. [cited by applicant]
Ad-hoc Chair (Ericsson), “Chairman's notes of AI 7.1.4 Maintenance for NR-LTE co-existence,” 3GPP TSG-RAN WG1 Meeting #96bis, Tdoc R1-1905798, Xi'an, China, Apr. 8-12, 2019, 1 page. [cited by applicant]
Ad-hoc Chair (Ericsson), “Chairman's notes of AI 7.2.10 Study on NR positioning support,” 3GPP TSG-RAN WG1 Meeting #96, Tdoc R1-1903632, Athens, Greece, Feb. 25-Mar. 1, 2019, 5 pages. [cited by applicant]
Ad-hoc Chair (Ericsson), “Chairman's notes of AI 7.2.10 Study on NR positioning support,” 3GPP TSG-RAN WG1 Meeting #96bis, Tdoc R1-1905804, Xi'an, China, Apr. 8-12, 2019, 5 pages. [cited by applicant]
Ad-hoc Chair (Ericsson), “Chairman's notes of AI 7.2.2 Study on NR-based Access to Unlicensed Spectrum,” 3GPP TSG-RAN WG1 Meeting #96 Tdoc, R1-1903629, Athens, Greece, Feb. 25-Mar. 1, 2019, 8 pages. [cited by applicant]
Ad-hoc Chair (Ericsson), “Chairman's notes of AI 7.2.2 Study on NR-based Access to Unlicensed Spectrum,” 3GPP TSG-RAN WG1 Meeting #96bis, Tdoc R1-1905801, Xi'an, China, Apr. 8-12, 2019, 10 pages. [cited by applicant]
Ad-hoc Chair (Ericsson), “Chairman's notes of AI 7.2.5 Study on solutions for NR to support Non Terrestrial Network (NTN), ” 3GPP TSG-RAN WG1 Meeting #96bis, Tdoc R1-1905802, Xi'an, China, Apr. 8-12, 2019, 7 pages. [cited by applicant]
Ad-Hoc chair (NTT Docomo, Inc.), “Chairman's notes of AI 7.1.7,” 3GPP TSG RAN WG1 #96bis, R1-1905800, Xi'an, China, Apr. 8-12, 2019, 6 pages. [cited by applicant]
Ad-Hoc chair (NTT Docomo, Inc.), “Chairman's notes of AI 7.1.7,” 3GPP TSG RAN WG1 Meeting #96, R1-1903628, Athens, Greece, Feb. 25-Mar. 1, 2019, 2 pages. [cited by applicant]
Ad-hoc Chair (Samsung), “Chairman's notes of AI 6.2.1 Additional MTC Enhancements, ” 3GPP TSG RAN WG1 Meeting #96, R1-1903526, Athens, Greece, Feb. 25-Mar. 1, 2019, 6 pages. [cited by applicant]
Ad-hoc Chair (Samsung), “Chairman's notes of AI 6.2.1 Additional MTC Enhancements, ” 3GPP TSG RAN WG1 Meeting #96, R1-1903526, Athens, Greece, Feb. 25-Mar. 1, 2019, 7 pages. [cited by applicant]
Ad-hoc Chair (Samsung), “Chairman's notes of AI 6.2.2 Additional Enhancements for NB-IoT,” 3GPP TSG RAN WG1 Meeting #96, R1-1903527, Athens, Greece, Feb. 25-Mar. 1, 2019, 5 pages. [cited by applicant]
Ad-hoc Chair (Samsung), “Chairman's notes of AI 6.2.2 Additional Enhancements for NB-IoT,” 3GPP TSG RAN WG1 Meeting #96, R1-1903663, Athens, Greece, Feb. 25-Mar. 1, 2019, 5 pages. [cited by applicant]
Ad-hoc Chair (Samsung), “Chairman's notes of AI 6.2.3 DL MIMO efficiency enhancements for LTE,” 3GPP TSG RAN WG1 Meeting #96, R1-1903656, Athens, Greece, Feb. 25-Mar. 1, 2019, 2 pages. [cited by applicant]
Ad-hoc Chair (Samsung), “Chairman's notes of AI 7.1.2 Maintenance for MIMO,” 3GPP TSG RAN WG1 Meeting #96, R1-1903625, Athens, Greece, Feb. 25-Mar. 1, 2019, 5 pages. [cited by applicant]
Ad-hoc Chair (Samsung), “Chairman's notes of AI 7.1.5 Maintenance for UL power control,” 3GPP TSG RAN WG1 Meeting #96, R1-1903627, Athens, Greece, Feb. 25-Mar. 1, 2019, 2 pages. [cited by applicant]
Ad-hoc Chair (Samsung), “Chairman's notes of AI 7.2.5 Cross Link Interference (CLI) handling and Remote Interference Management (RIM) for NR,” 3GPP TSG RAN WG1 Meeting #96, R1-1903630, Athens, Greece, Feb. 25-Mar. 1, 20… [cited by applicant]
Ad-hoc Chair (Samsung), “Chairman's notes of AI 7.2.8 Enhancements on MIMO for NR,” 3GPP TSG RAN WG1 Meeting #96, R1-1903631, Athens, Greece, Feb. 25-Mar. 1, 2019, 9 pages. [cited by applicant]
International Preliminary Report on Patentability in International Appln. No. PCT/US2020/031183, dated Nov. 11, 2021, 7 pages. [cited by applicant]
International Search Report and Written Opinion in International Appln. No. PCT/US2020/031183, dated Aug. 5, 2020, 13 pages. [cited by applicant]
Qualcomm Incorporated, “Updated proposal for RACH extension for IAB,” 3GPP TSG RAN WG1 Meeting #96, R1-1905005 Xi'an, China, Apr. 8-12, 2019, 8 pages. [cited by applicant]
Samsung, “Support of RACH Occasions and Periodicity for IAB RACH,” 3GPP TSG RAN WG1 #96bis, R1-1904416, Xi'an, China Apr. 8-12, 2019, 7 pages. [cited by applicant]