IP Library Granted Patent US 12,389,418
Granted Patent B2
US 12,389,418 · App. 17/916,685 · Granted Aug 12, 2025

Resource attribute configuration

Inventors: Majid Ghanbarinejad (Chicago, IL); Hyejung Jung (Northbrook, IL); Vijay Nangia (Woodridge, IL)
Assignee: Lenovo (Singapore) Pte. Ltd.
H04W72/23H04W72/52
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,389,418
App. No.
17/916,685
Granted
Aug 12, 2025
Kind
B2
Abstract

Apparatuses, methods, and systems are disclosed for resource attribute configuration. One method includes receiving a first configuration for a resource. The first configuration includes a first parameter indicating a time-domain attribute associated with the resource, and the time-domain attribute is hard, soft, and/or unavailable. The method includes receiving a second configuration for the resource. The second configuration includes a second parameter indicating a frequency-domain attribute associated with the resource, and the frequency-domain attribute is hard, soft, and/or unavailable. The method includes determining an attribute for the resource based on the time-domain attribute and the frequency-domain attribute. The attribute is hard, soft, and/or unavailable. The method includes, in response to determining that the attribute is soft: determining whether the resource is indicated as available; and performing an operation on the resource.

Claims (56)

1. An apparatus for wireless communication, the apparatus comprising an integrated access and backhaul (IAB) node, the apparatus further comprising:

a processor; and

a memory coupled to the processor, the processor configured to cause the apparatus to:

receive a first configuration associated with a symbol, wherein the first configuration comprises a first indication of whether the symbol is hard, soft, or unavailable;

receive a second configuration associated with a set of resource blocks (RBs) on the symbol, wherein the second configuration comprises a second indication of whether the set of RBs is hard, soft, or unavailable; and

determine, for an IAB distributed unit (IAB-DU) of the IAB node, whether to perform a communication on the set of RBs in the symbol based at least in part on the first indication and the second indication.

2. The apparatus of claim 1 , wherein the processor configured to further cause the apparatus to:

receive a control message comprising a third indication that indicates available or unavailable; and

determine, for the IAB-DU, whether to perform the communication on the set of RBs in the symbol further based on the third indication.

3. The apparatus of claim 2 , wherein the IAB-DU is determined to perform the communication on the set of RBs in the symbol in response to:

the first indication indicating that the symbol is soft;

the second indication indicating that the set of RBs is soft; and

the third indication indicating available.

4. The apparatus of claim 2 , wherein the IAB-DU is determined not to perform the communication on the set of RBs in the symbol in response to:

the first indication indicating that the symbol is soft;

the second indication indicating that the set of RBs is soft; and

the third indication indicating unavailable.

5. The apparatus of claim 2 , wherein the control message comprises a bitmap field associated with a plurality of sets of RBs, the plurality of sets of RBs includes the set of RBs, and a bit in the bitmap field indicates whether the set of RBs is available.

6. The apparatus of claim 2 , wherein the control message comprises an availability indication downlink control information (DCI) message from a parent node of the IAB node.

7. The apparatus of claim 1 , wherein the communication is a transmission, a reception, or a combination thereof.

8. The apparatus of claim 1 , wherein the first configuration is a time-domain configuration.

9. The apparatus of claim 1 , wherein the second configuration is a frequency-domain configuration.

10. A method at an integrated access and backhaul (IAB) node, the method comprising:

receiving a first configuration associated with a symbol, wherein the first configuration comprises a first indication of whether the symbol is hard, soft, or unavailable;

receiving a second configuration associated with a set of resource blocks (RBs) on the symbol, wherein the second configuration comprises a second indication of whether the set of RBs is hard, soft, or unavailable; and

determining, for an IAB distributed unit (IAB-DU) of the IAB node, whether to perform a communication on the set of RBs in the symbol based at least in part on the first indication and the second indication.

11. The method of claim 10 , further comprising:

receiving a control message comprising a third indication that indicates available or unavailable; and

determining, for the IAB-DU, whether to perform the communication on the set of RBs in the symbol further based on the third indication.

12. The method of claim 11 , wherein the IAB-DU is determined to perform the communication on the set of RBs in the symbol in response to:

the first indication indicating that the symbol is soft;

the second indication indicating that the set of RBs is soft; and

the third indication indicating available.

13. The method of claim 11 , wherein the IAB-DU is determined not to perform the communication on the set of RBs in the symbol in response to:

the first indication indicating that the symbol is soft;

the second indication indicating that the set of RBs is soft; and

the third indication indicating unavailable.

14. The method of claim 11 , wherein the control message comprises a bitmap field associated with a plurality of sets of RBs, the plurality of sets of RBs includes the set of RBs, and a bit in the bitmap field indicates whether the set of RBs is available.

15. The method of claim 10 , wherein the communication is a transmission, a reception, or a combination thereof.

16. The method of claim 10 , wherein the first configuration is a time-domain configuration.

17. The method of claim 10 , wherein the second configuration is a frequency-domain configuration.

18. An apparatus for wireless communication, the apparatus comprising an integrated access and backhaul (IAB) node, the apparatus further comprising:

a processor; and

a memory coupled with the processor, the processor configured to cause the apparatus to:

receive a time-domain configuration associated with a symbol, wherein the time-domain configuration comprises a first indication of whether the symbol is hard, soft, or unavailable;

receive a frequency-domain configuration associated with a set of resource blocks (RBs) on the symbol, wherein the frequency-domain configuration comprises a second indication of whether the set of RBs is hard, soft, or unavailable;

receive a control message comprising a third indication that indicates available or unavailable; and

determine, for an IAB distributed unit (IAB-DU) of the IAB node, whether to perform a transmission, a reception, or a combination thereof on the set of RBs in the symbol based on the first indication, the second indication, and the third indication.

19. The apparatus of claim 18 , wherein the IAB-DU is determined to perform the transmission, the reception, or the combination thereof on the set of RBs in the symbol in response to:

the first indication indicating that the symbol is soft;

the second indication indicating that the set of RBs is soft; and

the third indication indicating available.

20. The apparatus of claim 18 , wherein the IAB-DU is determined not to perform the transmission, the reception, or the combination thereof on the set of RBs in the symbol in response to:

the first indication indicating that the symbol is soft;

the second indication indicating that the set of RBs is soft; and

the third indication indicating unavailable.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 29, 2025
From: LENOVO (SINGAPORE) PTE. LTD.
To: EDGEWOOD IP, LLC
Reel/Frame 074118/0091 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 13, 2022
From: GHANBARINEJAD, MAJID; JUNG, HYEJUNG; NANGIA, VIJAY
To: LENOVO (SINGAPORE) PTE. LTD.
Reel/Frame 061417/0270 →
Continuity (2)
Provisional Application 63004192 · Apr 2, 2020
Related Publication 20230164793A1 · May 25, 2023
References Cited (23)
US 12185280B2 · Yokomakura · 2024 [cited by examiner]
US 20190305923A1 · Luo · 2019 [cited by examiner]
US 20210345303A1 · Ying · 2021 [cited by examiner]
US 20220061006A1 · Liu · 2022 [cited by examiner]
US 20220191863A1 · Miao · 2022 [cited by examiner]
CN 111901871A · 2020 [cited by applicant]
WO 2020032578A1 · 2020 [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Study on Integrated Access and Backhaul; (Release 16),” 3GPP TR 38.874 V16.0.0, Dec. 2018, pp. 1-111 (Year: 2018). [cited by examiner]
PCT/IB2021/052668, “Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching authority, or the Declaration”, International Searching Authority, Jun. 29, 2021,… [cited by applicant]
Intel Corporation, “Overview on RAN1 related issues in IAB”, 3GPP TSG RAN WG1 #92bis R1-1804755, Apr. 16-Apr. 20, 2018, pp. 1-15. [cited by applicant]
Intel Corporation, “Phy layer enhancement for Nr Iab” 3GPP Tsg Ran WG1 #93 R1-1806551, May 21-May 25, 2018, pp. 1-17. [cited by applicant]
Huawei, Hisilicon, “Physical layer design for NR IAB”, 3GPP TSG RAN WG1 Meeting #94 R1-1808101, Aug. 20-24, 2018, pp. 1-14. [cited by applicant]
Lenovo, Motorola Mobility, “Discussion on resource partitioning for IAB network”, 3GPP TSG RAN WG1 Meeting #94 R1-1808551, Aug. 20-24, 2018, pp. 1-3. [cited by applicant]
CMCC, “Discussions on enhancements to support NR Backhaul links”, 3GPP TSG RAN WG1 Meeting #94 R1-1808836, Aug. 20-24, 2018, pp. 1-9. [cited by applicant]
Qualcomm Incorporated, “Enhancements to support NR backhaul links”, 3GPP TSG RAN WG1 Meeting #94 R1-1809442, Aug. 20-24, 2018, pp. 1-19. [cited by applicant]
Lenovo, Motorola Mobility, “Discussion on resource partitioning for IAB network” 3GPP TSG RAN WG1 Ad-Hoc Meeting 1901 R1-1900394, Jan. 21-25, 2019, pp. 1-8. [cited by applicant]
Moderator (At&T), “Summary of [104-e-NR-eIAB-01]—3rd Checkpoint”, 3GPP TSG RAN WG1 #104-e R1-2101891, Jan. 25-Feb. 5, 2021, pp. 1-51. [cited by applicant]
Qualcomm, “New WID on Enhancements to Integrated Access and Backhaul”, 3GPP TSG RAN Meeting #86 RP-193251, Dec. 9-12, 2019, pp. 1-5. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical channels and modulation (Release 16)”, 3GPP TS 38.211 V16.0.0, Dec. 2019, pp. 1-129. [cited by applicant]
3GPP, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15), 3GPP TS 38.213 V15.7.0, Sep. 2019, pp. 1-108. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 16)”, 3GPP TS 38.214 V16.0.0, Dec. 2019, pp. 1-147. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; User Equipment (UE) radio access capabilities (Release 15)”, 3GPP TS 38.306 V15.8.0, Dec. 2019, pp. 1-60. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15)”, 3GPP TS 38.331 V15.9.0, Mar. 2020, pp. 1-536. [cited by applicant]