IP Library Granted Patent US 12,376,111
Granted Patent B2
US 12,376,111 · App. 17/632,009 · Granted Jul 29, 2025

Method and apparatus for transmitting information on an uplink channel

Inventors: Hyejung Jung (Northbrook, IL); Joachim Löhr (Wiesbaden, DE); Vijay Nangia (Woodridge, IL); Hossein Bagheri (Urbana, IL)
Assignee: Lenovo (Singapore) Pte. Ltd.
H04W72/21H04L1/1812H04L5/0044H04L5/0053H04W72/1268H04W72/23H04W72/542H04W72/569
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,376,111
App. No.
17/632,009
Granted
Jul 29, 2025
Kind
B2
Abstract

A PUCCH configuration including information of at least one PUCCH resource can be received ( 310 ) at a UE. An UL grant for at least one high-priority PUSCH can be received ( 320 ). The UL grant can indicate the UE to include a CSI report in the at least one high-priority PUSCH. A particular PUSCH of the at least one high-priority PUSCH can overlap with a PUCCH resource of the at least one PUCCH resource. A determination can be made ( 330 ) as to whether there is UCI to transmit on the PUCCH resource. The particular PUSCH can be transmitted ( 340 ) according to the UL grant by including the CSI report in the particular PUSCH when there is UCI to transmit on the PUCCH resource.

Claims (44)

1. A method performed by a user equipment (UE), the method comprising:

receiving a physical uplink control channel (PUCCH) configuration including information of at least one PUCCH resource;

receiving an uplink grant for at least one high-priority physical uplink shared channel (PUSCH), the uplink grant indicating for the UE to include a channel state information (CSI) report in the at least one high-priority PUSCH, wherein the at least one high-priority PUSCH overlaps with the at least one PUCCH resource, and wherein the at least one PUCCH resource is a low-priority PUCCH resource;

determining that there is uplink control information (UCI) to transmit on the physical uplink control channel at least one PUCCH resource, wherein the UCI comprises a scheduling request (SR); and

transmitting the at least one high-priority PUSCH without including the UCI based at least in part on the at least one high-priority PUSCH failing to comprise uplink data.

2. The method of claim 1 , further comprising cancelling an UCI transmission on the at least one PUCCH resource.

3. The method of claim 1 , further comprising:

multiplexing the UCI with the at least one high-priority PUSCH based at least in part on the UCI comprising at least one of the SR or hybrid automatic repeat request (HARQ) acknowledgement (ACK) information.

4. The method of claim 3 , wherein the UCI comprises an additional CSI report, and wherein multiplexing the UCI comprises multiplexing the UCI excluding the additional CSI report in the at least one high-priority PUSCH.

5. The method of claim 3 , further comprising determining whether there is an uplink-shared channel associated with the PUSCH comprises the uplink data, wherein multiplexing the UCI comprises multiplexing the at least one of the SR or the HARQ ACK information with the at least one high-priority PUSCH based at least in part on the uplink-shared channel failing to comprise the uplink data.

6. The method of claim 1 , wherein the CSI report comprises an aperiodic CSI report in the at least one high-priority PUSCH.

7. The method of claim 1 , wherein the CSI report comprises a semi-persistent CSI report, wherein the at least one high-priority PUSCH comprises semi-persistently occurring PUSCH resources, and wherein transmitting the at least one high-priority PUSCH comprises transmitting the CSI report on a semi-persistently occurring PUSCH resource of the semi-persistently occurring PUSCH resources.

8. The method of claim 1 , wherein the at least one PUCCH resource corresponds to a high priority PUCCH, and wherein transmitting the at least one high-priority PUSCH comprises transmitting the at least one high-priority PUSCH when the at least one PUCCH resource corresponds to the high priority PUCCH.

9. The method of claim 8 , wherein the at least one high-priority PUSCH is associated with an uplink-shared channel comprising the uplink data, and wherein transmitting the at least one high-priority PUSCH comprises transmitting the at least one high-priority PUSCH based at least in part on the at least one high-priority PUSCH being associated with the uplink-shared channel and the physical uplink control channel at least one PUCCH resource corresponds to the high priority PUCCH.

10. The method of claim 9 , wherein the UCI comprises at least one of the SR or hybrid automatic repeat request (HARQ) acknowledgement (ACK) information, or an additional CSI report, and wherein transmitting the at least one high-priority PUSCH comprises:

multiplexing the HARQ ACK information with the at least one high-priority PUSCH based at least in part on the UCI comprising the HARQ ACK information;

excluding the SR from the at least one high-priority PUSCH based at least in part on the UCI comprising the SR; and

excluding the additional CSI report from the at least one high-priority PUSCH based at least in part on the UCI comprising the additional CSI report.

11. The method of claim 1 , wherein the UCI comprises hybrid automatic repeat request (HARQ) acknowledgement (ACK) information, and wherein the at least one high-priority PUSCH comprises a low-priority uplink-shared channel and the HARQ ACK information of the UCI.

12. The method of claim 11 , further comprising indicating that the low-priority uplink-shared channel is transmitted on the at least one high-priority PUSCH.

13. The method of claim 12 , wherein the indicating comprises applying a scrambling sequence to the at least one high-priority PUSCH, where the scrambling sequence corresponds to the low-priority uplink-shared channel.

14. The method of claim 1 , wherein the PUCCH configuration includes a SR resource configuration, wherein the SR resource configuration comprises the at least one PUCCH resource and is associated with a SR configuration, wherein the SR configuration corresponds to at least one logical channel, and wherein the method further comprises determining a priority of the at least one PUCCH resource based at least in part on at least one priority of the at least one logical channel.

15. A user equipment (UE) for wireless communication, comprising:

at least one memory; and

at least one processor coupled with the at least one memory and configured to cause the UE to:

receive a physical uplink control channel (PUCCH) configuration including information of at least one PUCCH resource;

receive an uplink grant for at least one high-priority physical uplink shared channel (PUSCH), the uplink grant indicating for the UE to include a channel state information (CSI) report in the at least one high-priority PUSCH, wherein the at least one high-priority PUSCH overlaps with of the at least one PUCCH resource, and wherein the at least one PUCCH resource is a low-priority PUCCH resource;

determine that there is uplink control information (UCI) to transmit on the at least one PUCCH resource, wherein the UCI comprises a scheduling request (SR); and

transmit the at least one high-priority PUSCH without including the UCI based at least in part on the at least one high-priority PUSCH failing to comprise uplink data.

16. The UE of claim 15 , wherein the at least one processor is further configured to cause the UE to cancel an UCI transmission on the at least one PUCCH resource.

17. The UE of claim 15 , wherein the at least one processor is further configured to cause the UE to multiplex the UCI with the at least one high-priority PUSCH based at least in part on the UCI comprising at least one of the SR or hybrid automatic repeat request (HARQ) acknowledgement (ACK) information.

18. The UE of claim 15 , wherein the CSI report comprises an aperiodic CSI report in the at least one high-priority PUSCH.

19. A processor for wireless communication, comprising:

at least one controller coupled with at least one memory and configured to cause the processor to:

receive a physical uplink control channel (PUCCH) configuration including information of at least one PUCCH resource;

receive an uplink grant for at least one high-priority physical uplink shared channel (PUSCH), the uplink grant indicating for the processor to include a channel state information (CSI) report in the at least one high-priority PUSCH, wherein the at least one high-priority PUSCH overlaps with PUCCH resource, and wherein the at least one PUCCH resource is a low-priority PUCCH resource;

determine that there is uplink control information (UCI) to transmit on the at least one PUCCH resource, wherein the UCI comprises a scheduling request (SR); and

transmit the at least one high-priority PUSCH without including the UCI based at least in part on the at least one high-priority PUSCH failing to comprise uplink data.

20. A network equipment (NE) for wireless communication, comprising:

at least one memory; and

at least one processor coupled with the at least one memory and configured to cause the NE to:

transmit a physical uplink control channel (PUCCH) configuration including information of at least one PUCCH resource;

transmit an uplink grant for at least one high-priority physical uplink shared channel (PUSCH), the uplink grant indicating for a user equipment (UE) to include a channel state information (CSI) report in the at least one high-priority PUSCH, wherein the at least one high-priority PUSCH overlaps with the at least one PUCCH resource, and wherein the at least one PUCCH resource is a low-priority PUCCH resource; and

receive the at least one high-priority PUSCH without uplink control information (UCI) based at least in part on the at least one high-priority PUSCH failing to comprise uplink data, wherein the UCI comprises a scheduling request (SR).

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 1, 2022
From: JUNG, HYEJUNG; LÖHR, JOACHIM; NANGIA, VIJAY; BAGHERI, HOSSEIN
To: LENOVO (SINGAPORE) PTE. LTD.
Reel/Frame 058846/0117 →
Continuity (2)
Provisional Application 62886324 · Aug 13, 2019
Related Publication 20220279538A1 · Sep 1, 2022
References Cited (40)
US 12323981B2 · Jung et al. · 2025 [cited by applicant]
US 20150264678A1 · Yin et al. · 2015 [cited by applicant]
US 20170034850A1 · Rico Alvarino · 2017 [cited by examiner]
US 20190230690A1 · Akkarakaran et al. · 2019 [cited by applicant]
US 20200037314A1 · Xiong · 2020 [cited by examiner]
US 20200274637A1 · Li · 2020 [cited by examiner]
US 20210329663A1 · Wong · 2021 [cited by applicant]
US 20220159701A1 · Islam · 2022 [cited by examiner]
US 20220279538A1 · Jung et al. · 2022 [cited by applicant]
US 20230179342A1 · Zhang · 2023 [cited by applicant]
CN 107211439A · 2017 [cited by applicant]
CN 114175563A · 2020 [cited by applicant]
CN 114208352A · 2022 [cited by applicant]
EP 4014405A1 · 2020 [cited by applicant]
EP 4014406A1 · 2022 [cited by applicant]
IN 242022 · 2022 [cited by applicant]
WO 2018203686A1 · 2018 [cited by applicant]
WO 2021028872A1 · 2021 [cited by applicant]
WO 2021028873A1 · 2021 [cited by applicant]
U.S. Appl. No. 17/632,022, filed Apr. 25, 2024 , “Non-Final Office Action”, U.S. Appl. No. 17/632,022, Apr. 25, 2024, 14 pages. [cited by applicant]
U.S. Appl. No. 17/632,022, filed Aug. 1, 2024 , “Notice of Allowance”, U.S. Appl. No. 17/632,022, Aug. 1, 2024, 5 pages. [cited by applicant]
202080054522.3 , “Foreign Office Action”, CN Application No. 202080054522.3, Apr. 19, 2024, 14 pages. [cited by applicant]
202080054522.3 , “Foreign Office Action”, CN Application No. 202080054522.3, Sep. 22, 2023, 13 pages. [cited by applicant]
20760554.4 , “Communication Pursuant to Article 94(3) EPC”, EP Application No. 20760554.4, Apr. 11, 2024, 4 pages. [cited by applicant]
20760555.1 , “Communication Pursuant to Article 94(3) EPC”, EP Application No. 20760555.1, Apr. 23, 2024, 8 pages. [cited by applicant]
Huawei , et al., “Discussion on partially overlapped PUCCH and PUSCH”, 3GPP TSG RAN WG1 Meeting #92, R1-1801788, Athens, Greece, Feb. 2018, 5 pages. [cited by applicant]
Huawei , et al., “Enhancements to scheduling/HARQ”, 3GPP TSG RAN WG1 Meeting #97, R1-1906060, Reno, USA, May 2019, 9 pages. [cited by applicant]
Institute for Information Indust , “Enhancement on HARQ-ACK feedback for URLLC”, 3GPP TSG RAN WG1 #96, R1-1902742, Athens, Greece, Feb. 2019, 5 pages. [cited by applicant]
PCT/IB2020/057648 , “International Search Report and Written Opinion”, PCT Application No. PCT/IB2020/057648, Feb. 18, 2021, 10 pages. [cited by applicant]
PCT/IB2020/057649 , “International Search Report and Written Opinion”, PCT Application No. PCT/IB2020/057649, Feb. 18, 2021, 11 pages. [cited by applicant]
Sony , “Multiple HARQ-ACK PUSCH transmissions in a slot”, 3GPP TSG RAN WG1 #96bis, R1-1904235, Xi'an, China, Apr. 2019, 5 pages. [cited by applicant]
Intel Corporation, On enhancements to intra-UE multiplexing for IIoT, R1-1902499, 3GPP TSG RAN WG1 Meeting#96, Athens, Greece, Feb. 25-Mar. 1, 2019. [cited by applicant]
Yeung, Notice of References Cited, PTO-892, U.S. Appl. No. 17/362,022, U.S. Patent and Trademark Office, Apr. 25, 2024. [cited by applicant]
“Corrected Notice of Allowability”, U.S. Appl. No. 17/632,022, Feb. 20, 2025, 2 pages. [cited by applicant]
“Notice of Allowance”, U.S. Appl. No. 17/632,022, Feb. 5, 2025, 5 pages. [cited by applicant]
“Foreign Office Action”, CN Application No. 202080056730.7, Dec. 23, 2024, 28 pages. [cited by applicant]
Jung, et al., “Pursuant to MPEP § 2001.06(b) the applicant brings the following co-pending application to the Examiner's attention:”, U.S. Appl. No. 62/886,324, filed Aug. 13, 2019, 31 pages. [cited by applicant]
Nokia, et al., “On enhanced HARQ-ACK feedback for URLLC”, 3GPP TSG RAN WG1 Meeting #94-bis, R1-1810667, Chengdu, P.R. China, Oct. 2018, 4 pages. [cited by applicant]
“Corrected Notice of Allowability”, U.S. Appl. No. 17/632,022, filed Apr. 2, 2025, 2 pages. [cited by applicant]
“Corrected Notice of Allowability”, U.S. Appl. No. 17/632,022, filed May 14, 2025, 2 pages. [cited by applicant]
Cited By (1)
US 12,593,336