IP Library Granted Patent US 12,225,541
Granted Patent B2
US 12,225,541 · App. 17/716,300 · Granted Feb 11, 2025

Method and user equipment for hybrid automatic repeat request process identity selection

Inventor: Heng-Li Chin (Taipei, TW)
Assignee: SHARP KABUSHIKI KAISHA
H04W72/23H04L1/1812H04W72/1268H04W72/566H04W80/02
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,225,541
App. No.
17/716,300
Granted
Feb 11, 2025
Kind
B2
Abstract

A method and a user equipment for HARQ process ID selection are provided. The method includes: receiving a configuration message to configure a Configured Grant (CG) configuration and a set of HARQ process IDs that is available for the CG configuration, the set of HARQ process IDs including a first HARQ process ID for retransmission and a second HARQ process ID for initial transmission; determining that a CG physical uplink shared channel (PUSCH) corresponding to the CG configuration becomes available for transmission; selecting, based on a first HARQ process ID selection procedure, the first HARQ process ID or the second HARQ process ID from the set of HARQ process IDs for the CG PUSCH; and transmitting, based on the selected first or second HARQ process ID, a first Medium Access Control (MAC) Protocol Data Unit (PDU) for retransmission or a second MAC PDU for initial transmission on the CG PUSCH.

Claims (48)

1. A method performed by a User Equipment (UE) for Hybrid Automatic Repeat Request (HARQ) process Identity (ID) selection, the method comprising:

receiving a configuration message to configure a Configured Grant (CG) configuration and a set of HARQ process IDs that is available for the CG configuration, the set of HARQ process IDs including a first HARQ process ID and a second HARQ process ID;

determining a CG physical uplink shared channel (PUSCH) corresponding to the CG configuration;

selecting, based on a first HARQ process ID selection procedure, the first HARQ process ID or the second HARQ process ID for the CG PUSCH in a case that a Logical Channel (LCH)-based prioritization indication, a CG retransmission timer, and an Information Element (IE) for enabling the first HARQ process ID selection procedure are configured; and

transmitting, based on the selected first or second HARQ process ID, a first Medium Access Control (MAC) Protocol Data Unit (PDU) for retransmission or a second MAC PDU for initial transmission on the CG PUSCH, wherein the first HARQ process ID selection procedure includes:

determining a priority of first data multiplexed in the first MAC PDU as a first priority of the first HARQ process ID;

determining a priority of second data to be multiplexed in the second MAC PDU as a second priority of the second HARQ process ID;

selecting, based on the first priority and the second priority, the first HARQ process ID or the second HARQ process ID for the CG PUSCH; and

prioritizing the first HARQ process ID over the second HARQ process ID in a case that the first priority is equal to the second priority.

2. The method of claim 1 , wherein:

the first data is from a first set of LCHs,

the second data is from a second set of LCHs,

the priority of the first data is determined based on an LCH with a highest LCH priority among the first set of LCHs, and

the priority of the second data is determined based on an LCH with a highest LCH priority among the second set of LCHs.

3. The method of claim 1 , wherein the first HARQ process ID selection procedure further includes:

selecting the first HARQ process ID for the CG PUSCH in a case that the first priority is higher than the second priority; and

selecting the second HARQ process ID for the CG PUSCH in a case that the second priority is higher than the first priority.

4. The method of claim 1 , wherein the IE is configured for the CG configuration or for a MAC entity of the UE.

5. The method of claim 1 , further comprising:

selecting, based on a second HARQ process ID selection procedure, the first HARQ process ID or the second HARQ process ID for the CG PUSCH in a case that at least one of the LCH-based prioritization indication, the CG retransmission timer, and the IE is not configured, wherein the second HARQ process ID selection procedure includes:

prioritizing the first HARQ process ID over the second HARQ process ID.

6. The method of claim 5 , wherein prioritizing the first HARQ process ID over the second HARQ process ID comprises:

selecting the first HARQ process ID for the CG PUSCH.

7. A User Equipment (UE) for Hybrid Automatic Repeat Request (HARQ) process Identity (ID) selection, the UE comprising:

at least one processor; and

at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the UE to:

receive a configuration message to configure a Configured Grant (CG) configuration and a set of HARQ process IDs that is available for the CG configuration, the set of HARQ process IDs including a first HARQ process ID and a second HARQ process ID;

determine a CG physical uplink shared channel (PUSCH) corresponding to the CG configuration;

select, based on a first HARQ process ID selection procedure, the first HARQ process ID or the second HARQ process ID for the CG PUSCH in a case that a Logical Channel (LCH)-based prioritization indication, a CG retransmission timer, and an Information Element (IE) for enabling the first HARQ process ID selection procedure are configured; and

transmit, based on the selected first or second HARQ process ID, a first Medium Access Control (MAC) Protocol Data Unit (PDU) for retransmission or a second MAC PDU for initial transmission on the CG PUSCH, wherein the first HARQ process ID selection procedure includes:

determining a priority of first data multiplexed in the first MAC PDU as a first priority of the first HARQ process ID;

determining a priority of second data to be multiplexed in the second MAC PDU as a second priority of the second HARQ process ID;

selecting, based on the first priority and the second priority, the first HARQ process ID or the second HARQ process ID for the CG PUSCH; and

prioritizing the first HARQ process ID over the second HARQ process ID in a case that the first priority is equal to the second priority.

8. The UE of claim 7 , wherein:

the first data is from a first set of LCHs,

the second data is from a second set of LCHs,

the priority of the first data is determined based on an LCH with a highest LCH priority among the first set of LCHs, and

the priority of the second data is determined based on an LCH with a highest LCH priority among the second set of LCHs.

9. The UE of claim 7 , wherein the first HARQ process ID selection procedure further includes:

selecting the first HARQ process ID for the CG PUSCH from the set of HARQ process IDs in a case that the first priority is higher than the second priority; and

selecting the second HARQ process ID for the CG PUSCH in a case that the second priority is higher than the first priority.

10. The UE of claim 7 , wherein the IE is configured for the CG configuration or for a MAC entity of the UE.

11. The UE of claim 7 , wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to:

select, based on a second HARQ process ID selection procedure, the first HARQ process ID or the second HARQ process ID for the CG PUSCH in a case that at least one of the LCH-based prioritization indication, the CG retransmission timer, and the IE is not configured, wherein the second HARQ process ID selection procedure includes:

prioritizing the first HARQ process ID over the second HARQ process ID.

12. The UE of claim 11 , wherein prioritizing the first HARQ process ID over the second HARQ process ID comprises:

selecting the first HARQ process ID for the CG PUSCH.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 24, 2024
From: FG INNOVATION COMPANY LIMITED
To: SHARP KABUSHIKI KAISHA
Reel/Frame 069028/0473 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 8, 2022
From: CHIN, HENG-LI
To: FG INNOVATION COMPANY LIMITED
Reel/Frame 059543/0612 →
Continuity (2)
Provisional Application 63173240 · Apr 9, 2021
Related Publication 20220338241A1 · Oct 20, 2022
References Cited (24)
US 20180159668A1 · Phuyal et al. · 2018 [cited by applicant]
US 20190289638A1 · Kung · 2019 [cited by examiner]
US 20200154469A1 · Chin et al. · 2020 [cited by applicant]
US 20210105096A1 · Chin et al. · 2021 [cited by applicant]
US 20220158765A1 · Lu · 2022 [cited by examiner]
US 20220158769A1 · Gou et al. · 2022 [cited by applicant]
US 20220294576A1 · Kuo · 2022 [cited by examiner]
US 20230058734A1 · Xiao · 2023 [cited by examiner]
US 20230198678A1 · Fu · 2023 [cited by examiner]
US 20230269772A1 · Chen · 2023 [cited by examiner]
US 20240014951A1 · Loehr · 2024 [cited by examiner]
WO 2020192624A1 · 2020 [cited by applicant]
WO 2021027917 · 2021 [cited by applicant]
Ericsson, CG timer handling upon de-prioritization of bundled Pusch, 3GPP TSG-RAN WG2 #113bis-e, Electronic meeting, Apr. 12, 2021-Apr. 20, 2021, Tdoc R2-2103427, the whole document. [cited by applicant]
CMCC, Discussion on the remaining issue for uplink enhancements for URLLC in UCE, 3GPP TSG-RAN WG2 # 113bis electronic, Online, Apr. 12-Apr. 20, 2021, R2-2103688, the whole document. [cited by applicant]
3GPP TR 38.889, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on NR-based access to unlicensed spectrum (Release 16)”, V16.0.0 (Dec. 2018). [cited by applicant]
3GPP TS 38.213 “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 16)”, V16.4.0 (Dec. 2020). [cited by applicant]
3GPP TS 38.214, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 16)”, V16.2.0 (Jun. 2020). [cited by applicant]
3GPP TS 38.212, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and channel coding (Release 16)”, V16.2.0 (Jun. 2020). [cited by applicant]
3GPP TS 38.331, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 16)”, V16.1.0 (Jul. 2020). [cited by applicant]
Nokia, Nokia Shanghai Bell, “Revised WID: Enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication (URLLC) support for NR”, 3GPP TSG RAN Meeting #88e Electronic meeting, Jun. 29-Jul.… [cited by applicant]
3GPP TS 38.321, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 16)”, V16.3.0 (Dec. 2020). [cited by applicant]
3GPP TS 38.211, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical channels and modulation (Release 16)”, V16.2.0 (Jun. 2020). [cited by applicant]
3GPP TS 37.213, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Physical ayer procedures for shared spectrum channel access (Release 16)”, V16.2.0 (Jun. 2020). [cited by applicant]