IP Library Granted Patent US 12,464,516
Granted Patent B2
US 12,464,516 · App. 17/267,127 · Granted Nov 4, 2025

Physical uplink shared channel enhancements for new radio ultra-reliable low-latency communication

Inventors: Sergey Panteleev (Nizhny Novgorod, RU); Debdeep Chatterjee (San Jose, CA); Toufiqul Islam (Santa Clara, CA); Fatemeh Hamidi-Sepehr (Santa Clara, CA)
Assignee: Apple Inc.
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,464,516
App. No.
17/267,127
Granted
Nov 4, 2025
Kind
B2
Abstract

A network device (e.g., a user equipment (UE), a new radio NB (gNB), or other network component) can process or generate a dynamic Physical Uplink Shared Channel (PUSCH) repetition indication that provides parameters about PUSCH repetition(s) for the uplink within one, two or other number of slots of a New Radio (NR) communication as an Ultra-Reliable Low-Latency Communication. The network device can also process or generate one or more multiple Configuration-Grant (CG) PUSCH configurations. The presence of a repetition level bit-field in a Downlink Control Information (DCI) carrying UL grant or activating UL configured grant PUSCH can be controlled by semi-static UE-specific RRC signaling enabling or disabling the dynamic signaling of PUSCH repetitions.

Claims (35)

1 . A baseband processor configured to, when executing instructions stored in a memory, perform operations comprising:

receiving one or more Type 2 configured grant (CG) Physical Uplink Shared Channel (PUSCH) configurations;

receiving User Equipment (UE) specific Radio Resource Control (RRC) signaling to configure a time-domain resource allocation table, wherein an entry of the time-domain resource allocation table is jointly configured with a number of repeated PUSCH transmissions in addition to a starting symbol, a length of PUSCH, and a PUSCH mapping type;

receiving a downlink control information (DCI) transmission to activate the one or more Type 2 CG PUSCH configurations, wherein the DCI includes a field pointing to the entry of the time-domain resource allocation table; and

generating, for transmission via radio frequency (RF) circuitry and in response to the DCI, the number of repeated PUSCH transmissions within a number of slots based on the one or more Type 2 CG PUSCH configurations and the entry of the time-domain resource allocation table.

2 . The baseband processor of claim 1 , wherein the operations further comprise receiving RRC signaling to enable dynamic signaling of PUSCH repetitions.

3 . The baseband processor of claim 1 , wherein the operations further comprise reinterpreting a 2-bit Redundancy Version (RV) indicator field in the DCI to determine the number of repeated PUSCH transmissions in response to being configured by higher layer signaling, wherein the DCI comprises a DCI format 0_0 or 0_1.

4 . The baseband processor of claim 1 , wherein the DCI includes a time-domain resource assignment field pointing to the entry of the time-domain resource allocation table.

5 . The baseband processor of claim 1 , wherein the operations further comprise receiving RRC signaling indicating whether to generate the number of repeated PUSCH transmissions as a Type A PUSCH repetition or a Type B PUSCH repetition.

6 . The baseband processor of claim 5 , wherein:

the Type A PUSCH repetition comprises slot-based repetitions having a same time domain allocation in repeated slots, wherein the time domain allocation includes a starting symbol, duration, and mapping type of the PUSCH and is derived from a time domain resource allocation field of the DCI; and

the Type B PUSCH repetition comprises back-to-back repetitions, wherein a starting symbol of the back-to-back repetitions other than an initial repetition is derived based on an ending symbol of a previous repetition, and wherein the back-to-back repetitions are contiguous within one or more slots.

7 . The baseband processor of claim 1 , wherein the one or more Type 2 CG PUSCH configurations convey resource allocation and transmission parameters for the number of repeated PUSCH transmissions as an ultra-reliable low latency communication (URLLC).

8 . The baseband processor of claim 1 , wherein the operations further comprise: receiving a deactivation indication in DCI, and in response to receiving the deactivation indication in the DCI, releasing a corresponding CG PUSCH configuration in a bandwidth part (BWP).

9 . The baseband processor of claim 1 , wherein the operations further comprise receiving L1 signaling or medium access control (MAC) control element (MAC CE) signaling to switch from a first Type 2 CG PUSCH configuration of the one or more Type 2 CG PUSCH configurations to a second Type 2 CG PUSCH configuration of the one or more Type 2 CG PUSCH configurations, wherein the L1 signaling includes UE specific DCI or a group-DCI where the UE is mapped to a field of the group-DCI containing UE-specific information.

10 . The baseband processor of claim 1 , wherein a total number of bits in the field of the DCI is based on a total number of entries in the time-domain resource allocation table.

11 . A non-transitory computer readable storage device storing executable instructions that, in response to execution, cause one or more processors of User Equipment (UE) to perform operations comprising:

receiving one or more Type 2 configured grant (CG) Physical Uplink Shared Channel (PUSCH) configurations;

receiving UE specific Radio Resource Control (RRC) signaling to configure a time-domain resource allocation table, wherein an entry of the time-domain resource allocation table is jointly configured with a number of repeated PUSCH transmissions in addition to a starting symbol, a length of PUSCH, and a PUSCH mapping type;

receiving a downlink control information (DCI) transmission to activate the one or more Type 2 CG PUSCH configurations, wherein the DCI includes a field pointing to the entry of the time-domain resource allocation table; and

generating, for transmission via radio frequency (RF) circuitry and in response to the DCI, the number of repeated PUSCH transmissions within a number of slots based on the one or more Type 2 CG PUSCH configurations and the entry of the time-domain resource allocation table.

12 . The non-transitory computer readable storage device of claim 11 , wherein the one or more Type 2 CG PUSCH configurations convey resource allocation and transmission parameters for the number of repeated PUSCH transmissions as an ultra-reliable low latency communication (URLLC).

13 . The non-transitory computer readable storage device of claim 11 , wherein the operations further comprise receiving one or more DCIs to activate the one or more Type 2 CG PUSCH configurations respectively.

14 . The non-transitory computer readable storage device of claim 11 , wherein the operations further comprise:

configuring a bitmap size number of the one or more Type 2 CG PUSCH configurations to be confirmed simultaneously or a number of configurations of the Type 2 CG PUSCH configured to the UE, wherein a configured grant confirmation medium access control (MAC) control element (MAC CE) format is addressed by Logical Channel ID (LCID) having a non-zero size and carries an indication of which configuration of the one or more Type 2 CG PUSCH configurations is confirmed.

15 . The non-transitory computer readable storage device of claim 14 , wherein a MAC CE signaling carries one or more indexes of one or more CG PUSCH configuration, and wherein each configuration of the one or more Type 2 CG PUSCH configurations includes a Configuration Index defined within each CG PUSCH type or across all CG PUSCH configurations provided to the UE.

16 . The non-transitory computer readable storage device of claim 11 , wherein a total number of bits in the field of the DCI is based on a total number of entries in the time-domain resource allocation table.

17 . The non-transitory computer readable storage device of claim 11 , wherein the DCI includes a time-domain resource assignment field pointing to the entry of the time-domain resource allocation table.

18 . A baseband processor configured to, when executing instructions stored in a memory, perform operations comprising:

generating, for transmission via radio frequency (RF) circuitry, one or more Type 2 configured grant (CG) Physical Uplink Shared Channel (PUSCH) configurations;

generating, for transmission via the RF circuitry, User Equipment (UE) specific Radio Resource Control (RRC) signaling to configure a time-domain resource allocation table, wherein an entry of the time-domain resource allocation table is jointly configured with a number of repeated PUSCH transmissions in addition to a starting symbol, a length of PUSCH, and a PUSCH mapping type;

generating a downlink control information (DCI) for transmission via the RF circuitry, wherein the DCI includes an indication to activate the one or more Type 2 CG PUSCH configurations and a field pointing to the entry of the time-domain resource allocation table; and

receiving a number of repeated PUSCH transmissions within a number of slots based on the one or more Type 2 CG PUSCH configurations and the entry of the time-domain resource allocation table.

19 . The baseband processor of claim 18 , wherein a total number of bits in the field of the DCI is based on a total number of entries in the time-domain resource allocation table.

20 . The baseband processor of claim 18 , wherein the DCI includes a time-domain resource assignment field pointing to the entry of the time-domain resource allocation table.

Continuity (3)
Provisional Application 62737526 · Sep 27, 2018
Provisional Application 62717659 · Aug 10, 2018
Related Publication 20210314982A1 · Oct 7, 2021
References Cited (41)
US 10034275B2 · Kim et al. · 2018 [cited by applicant]
US 20150282208A1 · Yi et al. · 2015 [cited by applicant]
US 20160182199A1 · Webb et al. · 2016 [cited by applicant]
US 20170201989A1 · Fakoorian et al. · 2017 [cited by applicant]
US 20180184468A1 · Chien et al. · 2018 [cited by applicant]
US 20180279327A1 · Ying · 2018 [cited by examiner]
US 20180332539A1 · Fan et al. · 2018 [cited by applicant]
US 20190342921A1 · Loehr · 2019 [cited by examiner]
US 20200052827A1 · Vilaipornsawai · 2020 [cited by examiner]
US 20200288464A1 · Luo · 2020 [cited by examiner]
US 20200359425A1 · Chen · 2020 [cited by examiner]
US 20210014008A1 · Takeda · 2021 [cited by examiner]
US 20210014881A1 · Aiba · 2021 [cited by examiner]
US 20210068114A1 · Xu · 2021 [cited by examiner]
US 20210076409A1 · Goto · 2021 [cited by examiner]
US 20210167930A1 · Jeon · 2021 [cited by examiner]
US 20210176018A1 · Bai · 2021 [cited by examiner]
US 20210184819A1 · Takeda · 2021 [cited by examiner]
US 20210185718A1 · Ying · 2021 [cited by examiner]
US 20210212105A1 · Takeda · 2021 [cited by examiner]
US 20210219271A1 · Takeda · 2021 [cited by examiner]
US 20210219333A1 · Xu · 2021 [cited by examiner]
US 20210235503A1 · Irukulapati · 2021 [cited by examiner]
US 20210250970A1 · Ekpenyong · 2021 [cited by examiner]
US 20210274534A1 · Takeda · 2021 [cited by examiner]
US 20210298052A1 · Namba · 2021 [cited by examiner]
US 20210377979A1 · Bhamri · 2021 [cited by examiner]
US 20220015070A1 · Chen · 2022 [cited by examiner]
US 20220053541A1 · Lei · 2022 [cited by examiner]
US 20220086882A1 · Takeda · 2022 [cited by examiner]
US 20220210824A1 · Ying · 2022 [cited by examiner]
US 20220248453A1 · Aiba · 2022 [cited by examiner]
US 20220353711A1 · Ying · 2022 [cited by examiner]
WO 2013138674A1 · 2014 [cited by applicant]
WO 2016171765A1 · 2018 [cited by applicant]
International Search Report dated Nov. 29, 2019 for International Application No. PCT/US2019/045828. [cited by applicant]
“PUSCH reliability for URLLC.” Source: Huawei, HiSilicon. Agenda Item: 7.1.3.3.4. 3GPP TSG RAN WG1 Meeting #93, Busan, Korea, May 21-25, 2018. R1-1806902. [cited by applicant]
“Remaining issues on UL data transmision for URLLC.” Source: vivo. Agenda Item: 7.1.3.3.4. 3GPP TSG RAN WG1 Meeting #92bis, Busan, Korea, May 21-25, 2018. R1-1806070. [cited by applicant]
Summary of 7.1.3.31 (resource allocation). Source: Ericsson. Agenda Item: 7.1.3.3.1. TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018. R1-1807622. [cited by applicant]
International Preliminary Report on Patentability dated Feb. 16, 2021 for International Application No. PCT/US2019/045828. [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.1.0 (Mar. 2018); http://www.3gpp.org. [cited by applicant]