IP Library › Granted Patent US 12,382,449
Granted Patent B2
US 12,382,449 · App. 17/771,944 · Granted Aug 5, 2025

User equipments, base stations and signaling for resource allocations of enhanced uplink transmissions

Inventors: Kai Ying (Vancouver, WA); Tatsushi Aiba (Sakai, JP)
Assignee: SHARP KABUSHIKI KAISHA
H04W72/1268H04W72/23
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,382,449
App. No.
17/771,944
Filed
Apr 26, 2022
Granted
Aug 5, 2025
Kind
B2
Art Unit
2478
USPC
370/329
Abstract

A user equipment (UE) is described. The UE includes receiving circuitry configured to receive downlink control information (DCI). The DCI includes a time domain resource assignment field The UE also includes a processor. The processor is configured to determine a resource allocation based on the DCI with the time domain resource assignment field.

Claims (33)

1. A user equipment (UE) comprising:

receiving circuitry configured to:

receive radio resource control (RRC) parameters used for configuring a first allocation table and a second allocation table, each of the first allocation table and the second allocation table being used for defining a time domain allocation for a physical uplink shared channel (PUSCH) transmission, the RRC parameters including a PUSCH-Config parameter, the PUSCH-Config parameter including a first information element for a downlink control information (DCI) format 0_1 and a second information element for a DCI format 0_2, each of the first information element and the second information element being a parameter different from a PUSCH-TimeDomainResourceAllocationList parameter in the PUSCH-Config parameter and from a pusch-TimeDomainAllocationList parameter in a pusch-ConfigCommon common parameter, wherein:

starting symbol and length are indicated as a single parameter in the first allocation table, and

starting symbol and length are indicated as separate parameters in the second allocation table, and

detect, in a UE specific search space, a first DCI format comprising first information used for indicating a row index to an allocation table used for the PUSCH transmission, the first DCI format being used for scheduling of the PUSCH transmission;

transmitting circuitry configured to perform, based on the detection of the first DCI format, the PUSCH transmission based on the allocation table used for the PUSCH transmission; and

processing circuitry configured to determine, based on whether the first DCI format is the DCI format 0_1, the DCI format 0_2, or a DCI format 0_0, whether the allocation table used for the PUSCH transmission is the first allocation table, the second allocation table, or any one of other allocation tables used for defining time domain allocations for PUSCH transmissions, wherein

the processing circuitry is configured such that:

in a case that the first DCI format is the DCI format 0_1 or the DCI format 0_2, the allocation table used for the PUSCH transmission is determined based on one of the first information element and the second information element, which is configured for the first DCI format, and regardless of whether the RRC parameters include the PUSCH-TimeDomainResourceAllocationList parameter in the PUSCH-Config parameter and the pusch-TimeDomainAllocationList parameter in the pusch-ConfigCommon common parameter.

2. The UE of claim 1 , wherein

the second information element includes the separate parameters in the second allocation table, and

the processing circuitry is configured to determine, in a case that the first DCI format is the DCI format 0_2, that the allocation table used for the PUSCH transmission is the second allocation table.

3. A base station apparatus comprising:

transmitting circuitry configured to:

transmit radio resource control (RRC) parameters used for configuring a first allocation table and a second allocation table, each of the first allocation table and the second allocation table being used for defining a time domain allocation for a physical uplink shared channel (PUSCH) transmission, the RRC parameters including a PUSCH-Config parameter, the PUSCH-Config parameter including a first information element for a downlink control information (DCI) format 0_1 and a second information element for a DCI format 0_2, each of the first information element and the second information element being a parameter different from a PUSCH-TimeDomainResourceAllocationList parameter in the PUSCH-Config parameter and from a pusch-TimeDomainAllocationList parameter in a pusch-ConfigCommon common parameter, wherein:

starting symbol and length are indicated as a single parameter in the first allocation table, and

starting symbol and length are indicated as separate parameters in the second allocation table, and

transmit, in a UE specific search space, a first DCI format comprising first information used for indicating a row index to an allocation table used for the PUSCH transmission, the first DCI format being used for scheduling of the PUSCH transmission; and

receiving circuitry configured to receive the PUSCH transmission based on the allocation table used for the PUSCH transmission, wherein

whether the allocation table used for the PUSCH transmission is the first allocation table, the second allocation table, or any one of other allocation tables used for defining time domain allocations for PUSCH transmissions is determined based on whether the first DCI format is the DCI format 0_1, the DCI format 0_2, or a DCI format 0_0, and

in a case that the first DCI format is the DCI format 0_1 or the DCI format 0_2, the allocation table used for the PUSCH transmission is determined based on one of the first information element and the second information element, which is configured for the first DCI format, and regardless of whether the RRC parameters include the PUSCH-TimeDomainResourceAllocationList parameter in the PUSCH-Config parameter and the pusch-TimeDomainAllocationList parameter in the pusch-ConfigCommon common parameter.

4. The base station apparatus of claim 3 , wherein

the second information element includes the separate parameters in the second allocation table, and

in a case that the first DCI format is the DCI format 0_2, the allocation table used for the PUSCH transmission is the second allocation table.

5. A communication method of a user equipment (UE) comprising:

receiving radio resource control (RRC) parameters used for configuring a first allocation table and a second allocation table, each of the first allocation table and the second allocation table being used for defining a time domain allocation for a physical uplink shared channel (PUSCH) transmission, the RRC parameters including a PUSCH-Config parameter, the PUSCH-Config parameter including a first information element for a downlink control information (DCI) format 0_1 and a second information element for a DCI format 0_2, each of the first information element and the second information element being a parameter different from a PUSCH-TimeDomainResourceAllocationList parameter in the PUSCH-Config parameter and from a pusch-TimeDomainAllocationList parameter in a pusch-ConfigCommon common parameter, wherein:

starting symbol and length are indicated as a single parameter, and

starting symbol and length are indicated as separate parameters in the second allocation table;

detecting, in a UE specific search space, a first DCI format comprising first information used for indicating a row index to an allocation table used for the PUSCH transmission, the first DCI format being used for scheduling of the PUSCH transmission;

performing, based on the detection of the first DCI format, the PUSCH transmission based on the allocation table used for the PUSCH transmission; and

determining, based on whether the first DCI format is the DCI format 0_1, the DCI format 0_2, or a DCI format 0_0, whether the allocation table used for the PUSCH transmission is the first allocation table, the second allocation table, or any one of other allocation tables used for defining time domain allocations for PUSCH transmissions, wherein

in a case that the first DCI format is the DCI format 0_1 or the DCI format 0_2, the allocation table used for the PUSCH transmission is determined based on one of the first information element and the second information element, which is configured for the first DCI format, and regardless of whether the RRC parameters include the PUSCH-TimeDomainResourceAllocationList parameter in the PUSCH-Config parameter and the pusch-TimeDomainAllocationList parameter in the pusch-ConfigCommon common parameter.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 26, 2022
From: YING, KAI; AIBA, TATSUSHI
To: SHARP KABUSHIKI KAISHA
Reel/Frame 059739/0073 →
Continuity (2)
Provisional Application 62931990 · Nov 7, 2019
Related Publication 20220377767A1 · Nov 24, 2022
References Cited (13)
US 20190149365A1 · Chatterjee · 2019 [cited by examiner]
US 20190159213A1 · Baldemair · 2019 [cited by examiner]
US 20190253220A1 · Kim · 2019 [cited by applicant]
US 20190394759A1 · Ying et al. · 2019 [cited by applicant]
US 20210377955A1 · Baldemair · 2021 [cited by examiner]
US 20210377979A1 · Bhamri · 2021 [cited by examiner]
CN 112314025A · 2021 [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on physical layer enhancements for NR ultra-reliable and low latency case (URLLC) (Release 16)”, 3GPP TR 38.824 V16.0.0 (Mar… [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.6.0 (Jun. 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical channels and modulation(Release 15)”, 3GPP TS 38.211 V15.6.0 (Jun. 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and channel coding(Release 15)”, 3GPP TS 38.212 V15.6.0 (Jun. 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data(Release 15)”, 3GPP TS 38.214 V15.6.0 (Jun. 2019). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control(Release 15)”, 3GPP TS 38.213 V15.6.0 (Jun. 2019). [cited by applicant]