IP Library Granted Patent US 12,402,023
Granted Patent B2
US 12,402,023 · App. 19/054,240 · Granted Aug 26, 2025

CSI transmission with multiple bandwidth parts

Inventors: Hua Zhou (Vienna, VA); Esmael Hejazi Dinan (McLean, VA); Alireza Babaei (Fairfax, VA); Hyoungsuk Jeon (Centreville, VA); Kyungmin Park (Vienna, VA)
Assignee: Ofinno, LLC
H04W24/02H04B7/0626H04L5/001H04L5/0057H04W24/10H04W72/0453H04W72/21H04W72/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,402,023
App. No.
19/054,240
Granted
Aug 26, 2025
Kind
B2
Abstract

Systems, apparatuses, and methods are described for wireless communications. A base station may send, to a wireless device, a medium access control (MAC) control element (CE) comprising a bandwidth part identifier field and a channel state information (CSI) report configuration field. Based on the MAC CE, the wireless device may activate the CSI report configuration for a bandwidth part indicated by the bandwidth part identifier field. The wireless device may transmit one or more CSI reports based on the CSI report configuration.

Claims (72)

1. A wireless device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the wireless device to:

receive one or more radio resource configuration (RRC) messages comprising:

one or more channel state information (CSI) reporting settings, wherein a first CSI reporting setting comprises:

a report configuration identifier;

a report type indicating a semi-persistent (SP) report type; and

a periodicity parameter indicating a reporting periodicity; and

configuration parameters of a plurality of bandwidth parts (BWPs) of a cell;

receive an SP CSI activation/deactivation medium access control (MAC) control element (CE) comprising:

a BWP indicator indicating a first BWP, of the plurality of BWPs of the cell, for which CSI reporting is triggered; and

an SP CSI activation/deactivation bit indicating activation of the CSI reporting based on the first CSI reporting setting;

receive a first downlink control information (DCI) indicating switching to the first BWP as an active BWP;

activate the first BWP of the plurality of BWPs; and

based on the SP CSI activation/deactivation MAC CE indicating the activation of the CSI reporting and based on the first BWP being the active BWP, transmit one or more SP CSI reports based on the first CSI reporting setting.

2. The wireless device of claim 1 , wherein the instructions further cause the wireless device to not transmit any SP CSI reports in response to the SP CSI activation/deactivation MAC CE before receiving the first DCI.

3. The wireless device of claim 2 , wherein the instructions further cause the wireless device to:

receive a second DCI indicating switching from the first BWP to a second BWP as the active BWP; and

in response to switching from the first BWP to the second BWP as the active BWP:

deactivate the first BWP; and

stop transmission of further SP CSI reports based on the first CSI reporting setting.

4. The wireless device of claim 2 , wherein the instructions further cause the wireless device to:

receive a second SP CSI activation/deactivation MAC CE indicating deactivation of the CSI reporting based on the first CSI reporting setting; and

stop transmission of further SP CSI reports based on the first CSI reporting setting.

5. The wireless device of claim 4 , wherein the first DCI switches both a downlink BWP and an uplink BWP based on an association between the downlink BWP and the uplink BWP that allows one activation/deactivation command to switch both the DL BWP and the UL BWP.

6. The wireless device of claim 5 , wherein the first BWP is the downlink BWP.

7. The wireless device of claim 6 , wherein the first CSI reporting setting comprises an offset parameter indicating a reporting timing offset.

8. The wireless device of claim 4 , wherein the SP CSI activation/deactivation MAC CE comprises a plurality of SP CSI activation/deactivation bits, wherein for each of the plurality of SP CSI activation/deactivation bits:

a value of 1 indicates activation of CSI reporting based on a CSI reporting setting; and

a value of 0 indicates deactivation of CSI reporting based on the CSI reporting setting.

9. The wireless device of claim 8 , wherein the SP CSI activation/deactivation MAC CE indicates the report configuration identifier of the first CSI reporting setting.

10. The wireless device of claim 1 , wherein the instructions further cause the wireless device to:

receive a second DCI indicating switching from the first BWP to a second BWP as the active BWP; and

in response to switching from the first BWP to the second BWP as the active BWP:

deactivate the first BWP; and

stop transmission of further SP CSI reports based on the first CSI reporting setting.

11. The wireless device of claim 10 , wherein the plurality of BWPs comprises a plurality of downlink BWPs and a plurality of uplink BWPs.

12. The wireless device of claim 11 , wherein the first BWP is an uplink BWP.

13. The wireless device of claim 10 , wherein the SP CSI activation/deactivation MAC CE comprises a plurality of SP CSI activation/deactivation bits, wherein for each of the plurality of SP CSI activation/deactivation bits:

a value of 1 indicates activation of CSI reporting based on a CSI reporting setting; and

a value of 0 indicates deactivation of CSI reporting based on the CSI reporting setting.

14. The wireless device of claim 13 , wherein the BWP indicator indicates the first BWP for which SP CSI reporting is triggered by the SP CSI activation/deactivation MAC CE.

15. The wireless device of claim 10 , wherein the first DCI switches both a downlink BWP and an uplink BWP based on an association between the downlink BWP and the uplink BWP that allows one activation/deactivation command to switch both the DL BWP and the uplink BWP.

16. The wireless device of claim 15 , wherein the first BWP is the downlink BWP.

17. The wireless device of claim 16 , wherein the one or more RRC messages further comprise:

one or more CSI-reference signal (CSI-RS) resource settings; and

a CSI measurement setting.

18. The wireless device of claim 17 , wherein the first CSI reporting setting comprises an offset parameter indicating a reporting timing offset.

19. The wireless device of claim 17 , wherein the SP CSI activation/deactivation MAC CE is for multiple CSI reporting settings when multiple CSI reporting settings are supported for SP CSI.

20. The wireless device of claim 1 , wherein the SP CSI activation/deactivation MAC CE indicates one or more physical uplink control channel (PUCCH) resources for the one or more SP CSI reports.

21. The wireless device of claim 20 , wherein the instructions further cause the wireless device to not transmit any SP CSI reports in response to the SP CSI activation/deactivation MAC CE before receiving the first DCI.

22. The wireless device of claim 20 , wherein the instructions further cause the wireless device to:

receive a second DCI indicating switching from the first BWP to a second BWP as the active BWP; and

in response to switching from the first BWP to the second BWP as the active BWP:

deactivate the first BWP; and

stop transmission of further SP CSI reports based on the first CSI reporting setting.

23. The wireless device of claim 22 , wherein the instructions further cause the wireless device to:

receive a second SP CSI activation/deactivation MAC CE indicating deactivation of the CSI reporting based on the first CSI reporting setting; and

stop transmission of further SP CSI reports based on the first CSI reporting setting.

24. The wireless device of claim 23 , wherein the one or more RRC messages further comprise:

one or more CSI-reference signal (CSI-RS) resource settings; and

a CSI measurement setting.

25. The wireless device of claim 24 , wherein the BWP indicator indicates the first BWP for which SP CSI reporting is triggered by the SP CSI activation/deactivation MAC CE.

26. The wireless device of claim 24 , wherein:

the first DCI switches both a downlink BWP and an uplink BWP based on an association between the downlink BWP and the uplink BWP that allows one activation/deactivation command to switch both the DL BWP and the UL BWP; and

the first BWP is the uplink BWP.

27. The wireless device of claim 26 , wherein the instructions further cause the wireless device to measure one or more CSI-RSs based on one or more CSI-RS resource settings.

28. The wireless device of claim 27 , wherein the SP CSI activation/deactivation MAC CE is for multiple CSI reporting settings when multiple CSI reporting settings are supported for SP CSI.

29. The wireless device of claim 26 , wherein the SP CSI activation/deactivation MAC CE indicates the report configuration identifier of the first CSI reporting setting.

30. The wireless device of claim 20 , wherein the SP CSI activation/deactivation MAC CE comprises a plurality of SP CSI activation/deactivation bits, wherein for each of the plurality of SP CSI activation/deactivation bits:

a value of 1 indicates activation of CSI reporting based on a CSI reporting setting; and

a value of 0 indicates deactivation of CSI reporting based on the CSI reporting setting.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 28, 2025
From: COMCAST CABLE COMMUNICATIONS, LLC
To: OFINNO, LLC
Reel/Frame 070664/0362 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 18, 2025
From: ZHOU, HUA; DINAN, ESMAEL HEJAZI; BABAEI, ALIREZA; JEON, HYOUNGSUK; PARK, KYUNGMIN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 070545/0898 →
Continuity (6)
Continuation 18487354 · Oct 16, 2023
Continuation 17476991 · Sep 16, 2021
Continuation 16185821 · Nov 9, 2018
Provisional Application 62587058 · Nov 16, 2017
Provisional Application 62583650 · Nov 9, 2017
Related Publication 20250193704A1 · Jun 12, 2025
References Cited (185)
US 8976698B2 · Chen et al. · 2015 [cited by applicant]
US 10848224B2 · Park et al. · 2020 [cited by applicant]
US 11159959B2 · Zhou et al. · 2021 [cited by applicant]
US 11394443B2 · Takeda et al. · 2022 [cited by applicant]
US 11825317B2 · Zhou et al. · 2023 [cited by applicant]
US 20170156152A1 · Nazar et al. · 2017 [cited by applicant]
US 20170195031A1 · Onggosanusi et al. · 2017 [cited by applicant]
US 20170238323A1 · Marinier et al. · 2017 [cited by applicant]
US 20170245165A1 · Onggosanusi et al. · 2017 [cited by applicant]
US 20170353223A1 · Kim et al. · 2017 [cited by applicant]
US 20170367046A1 · Papasakellariou · 2017 [cited by applicant]
US 20180006701A1 · Ahn et al. · 2018 [cited by applicant]
US 20180049047A1 · Lin et al. · 2018 [cited by applicant]
US 20180049169A1 · Lin et al. · 2018 [cited by applicant]
US 20180124687A1 · Park et al. · 2018 [cited by applicant]
US 20180124815A1 · Papasakellariou · 2018 [cited by applicant]
US 20180131493A1 · Luo et al. · 2018 [cited by applicant]
US 20180183551A1 · Chou et al. · 2018 [cited by applicant]
US 20180219664A1 · Guo et al. · 2018 [cited by applicant]
US 20190045491A1 · Zhang et al. · 2019 [cited by applicant]
US 20190045549A1 · Wu · 2019 [cited by applicant]
US 20190052377A1 · Hwang et al. · 2019 [cited by applicant]
US 20190081679A1 · Davydov et al. · 2019 [cited by applicant]
US 20190082425A1 · Li et al. · 2019 [cited by applicant]
US 20190103954A1 · Lee · 2019 [cited by examiner]
US 20190124558A1 · Ang · 2019 [cited by examiner]
US 20190132109A1 · Zhou et al. · 2019 [cited by applicant]
US 20190254110A1 · He et al. · 2019 [cited by applicant]
US 20200052868A1 · Zhang et al. · 2020 [cited by applicant]
US 20200153552A1 · Zhang et al. · 2020 [cited by applicant]
US 20200178223A1 · Kang et al. · 2020 [cited by applicant]
US 20200296656A1 · Amuru et al. · 2020 [cited by applicant]
US 20200336227A1 · Takeda · 2020 [cited by examiner]
US 20240121634A1 · Zhou et al. · 2024 [cited by applicant]
CA 3023709A1 · 2019 [cited by applicant]
EP 2672649A1 · 2013 [cited by applicant]
EP 3282633A1 · 2018 [cited by applicant]
EP 3484057A1 · 2019 [cited by applicant]
EP 3484057B1 · 2021 [cited by applicant]
EP 3787189A1 · 2021 [cited by applicant]
EP 3591887B1 · 2022 [cited by applicant]
IN 495598 · 2024 [cited by applicant]
WO 2011038243A2 · 2011 [cited by applicant]
WO 2011038243A3 · 2011 [cited by applicant]
WO 2011085230A2 · 2011 [cited by applicant]
WO 2017197155A1 · 2017 [cited by applicant]
WO 2018021834A1 · 2018 [cited by applicant]
WO 2018031638A1 · 2018 [cited by applicant]
WO 2018031924A1 · 2018 [cited by applicant]
WO 2018044116A1 · 2018 [cited by applicant]
WO 2018080260A1 · 2018 [cited by applicant]
WO 2018084544A1 · 2018 [cited by applicant]
WO 2018084571A1 · 2018 [cited by applicant]
WO 2018085145A1 · 2018 [cited by applicant]
WO 2018089117A1 · 2018 [cited by applicant]
WO 2018145019A1 · 2018 [cited by applicant]
Mar. 29, 2019—Extended European Search Report—EP 18205418.9. [cited by applicant]
Jan. 16, 2019—European Search Report—EP 18202948.8. [cited by applicant]
OPPO “SPS operations for BWP switching” Oct. 8, 2017. [cited by applicant]
Ericsson “URLLC aspects for grant-free UL transmission in NR” Feb. 12, 2017. [cited by applicant]
Jun. 28, 2019—European Extended Search Report—19166254.3. [cited by applicant]
Huawei, HiSilicon: “Bandwidth part activation and adaptation”, Sep. 18, 2017. [cited by applicant]
Interdigital, Inc.: “Remaining details of BWP”, Sep. 18, 2017. [cited by applicant]
LG Electronics: “Discussion on carrier aggregation and bandwidth parts”, Sep. 18, 2017. [cited by applicant]
R1-1718901 3GPP TSG RAN WG1 Meeting 90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: MediaTek Inc., Title: Summary of Bandwidth Part Operation. [cited by applicant]
Jul. 10, 2019—European Extended Search Report—EP 19175762.4. [cited by applicant]
3GPP TSG-RAN WG2 Meeting #102: “Email Discussion on SSB and Cell relationship”, May 21, 2018. [cited by applicant]
3GPP TSG RAN WG1 Meeting #93: “Remaining Issues on Beam Management”, May 21, 2018. [cited by applicant]
R1-1715425 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Huawei, HiSilicon, Title: Overview of bandwidth part, CA, and DC operation including SRS switching. [cited by applicant]
R1-1715492 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Fujitsu, Title: Considerations on UCI feedback for carrier aggregation. [cited by applicant]
R1-1715517 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Spreadtrum Communications, Title: Consideration on monitoring preemption indication in bandwidth parts. [cited by applicant]
R1-1715535 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Lenovo, Motorola Mobility, Title: HARQ-ACK codebook size determination for CA with different numerologies. [cited by applicant]
R1-1715648 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: vivo, Title: Remaining details for bandwidth part operation. [cited by applicant]
R1-1715692 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Guangdong OPPO Mobile Telecom, Title: Remaining issues on bandwidth part configuration and activation. [cited by applicant]
R1-1715755 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Nokia, Nokia Shanghai Bell, Title: On remaining aspects of NR CA/DC and BWPs. [cited by applicant]
R1-1715770 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: ETRI, Title: Remaining details of bandwidth part for initial access. [cited by applicant]
R1-1715774 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Panasonic, Title: Combining DRX with BWP adaptation. [cited by applicant]
R1-1715830 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: CATT, Title: Remaining aspects of CA and wider bandwidth operation. [cited by applicant]
R1-1715892 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: LG Electronics, Title: Discussion on carrier aggregation and bandwidth parts. [cited by applicant]
R1-1716019 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Samsung, Title: On Bandwidth Part Operation. [cited by applicant]
R1-1716109 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: NTT Docomo, Inc., Title: Remaining issues on bandwidth parts for NR. [cited by applicant]
R1-1716192 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: AT&T, Title: Remaining Details of Carrier Aggregation and Bandwidth Parts. [cited by applicant]
R1-1716202 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: MediaTek Inc., Title: Remaining Details on Bandwidth Part Operation in NR. [cited by applicant]
R1-1716258 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: InterDigital, Inc., Title: Remaining details of BWP. [cited by applicant]
R1-1716327 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Intel Corporation, Title: Remaining aspects for carrier aggregation and bandwidth parts. [cited by applicant]
R1-1716440 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Qualcomm Incorporated, Title: CA and BWP. [cited by applicant]
R1-1716601 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Ericsson, Title: On CA related aspects and BWP related aspects. [cited by applicant]
R1-1716647 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Convida Wireless, Title: Discussion on BWP Design. [cited by applicant]
R1-1717077 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Huawei, HiSilicon, Title: Remaining issues on bandwidth part. [cited by applicant]
R1-1717400 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Intel Corporation, Title: Remaining details for bandwidth parts. [cited by applicant]
R1-1717504 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: vivo, Title: Remaining details for bandwidth part operation. [cited by applicant]
R1-1717675 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Samsung, Title: On Bandwidth Part Operation. [cited by applicant]
R1-1717839 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: CATT, Title: Remaining aspects of BWP operation. [cited by applicant]
R1-1717972 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: LG Electronics, Title: Remaining issues on bandwidth parts. [cited by applicant]
R1-1718050 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: OPPO, Title: Remaining issues on bandwidth part configuration and activation. [cited by applicant]
R1-1718223 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: NTT Docomo, Inc., Title: Remaining issues on bandwidth parts for NR. [cited by applicant]
R1-1718327 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: MediaTek Inc., Title: Remaining Details on Bandwidth Part Operation in NR. [cited by applicant]
R1-1718365 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: InterDigital, Inc., Title: Remaining details of BWP. [cited by applicant]
R1-1718404 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: AT&T, Title: Remaining details for bandwidth parts. [cited by applicant]
R1-1718523 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Ericsson, Title: On bandwidth parties. [cited by applicant]
R1-1718580 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Qualcomm Incorporated, Title: Open Issues on BWP. [cited by applicant]
R1-1718607 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Nokia, Nokia Shanghai Bell, Title: On remaining aspects of BWPs. [cited by applicant]
R1-1715454 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: ZTE, Sanechips, Title: On NR Power Control. [cited by applicant]
R1-1715478 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Huawei, HiSilicon, Title: General considerations on UL power control design. [cited by applicant]
R1-1715505 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Mitsubishi Electric, Title: UL transmission power control. [cited by applicant]
R1-1715651 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: vivo, Title: NR UL power control framework. [cited by applicant]
R1-1715675 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Guangdong OPPO Mobile Telecom, Title: Uplink power control mechanism for NR. [cited by applicant]
R1-1715838 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: CATT, Title: NR Power Control Framework. [cited by applicant]
R1-1715902 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: LG Electronics, Title: Discussion on UL power control for NR. [cited by applicant]
R1-1716040 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Samsung, Title: On UL Power Control. [cited by applicant]
R1-1716061 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: CMCC, Title: Discussion on power control framework. [cited by applicant]
R1-1716114 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: NTT Docomo, Inc., Title: Power control framework for PUSCH. [cited by applicant]
R1-1716127 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Discussion on NR power control framework. [cited by applicant]
R1-1716451 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Qualcomm Incorporated, Title: Power control and PHR for NR. [cited by applicant]
R1-1716515 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: InterDigital Inc., Title: Further Details on Uplink Power Control. [cited by applicant]
R1-1716535 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Panasonic, Title: Discussion on NR power control framework. [cited by applicant]
R1-1716604 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Ericsson, Title: NR UL power control framework. [cited by applicant]
R1-1716606 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Ericsson, Title: Closed loop PC in NR. [cited by applicant]
R1-1717311 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Huawei, HiSilicon, Title: General considerations on UL power control design. [cited by applicant]
R1-1717408 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Intel Corporation, Title: Remaining Details on UL Power Control Framework. [cited by applicant]
R1-1717438 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: ZTE, Sanechips, Title: On NR Power Control. [cited by applicant]
R1-1717508 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: vivo, Title: Remaining issues on NR UL power control. [cited by applicant]
R1-1717692 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Samsung, Title: On UL Power Control. [cited by applicant]
R1-1717846 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: CATT, Title: NR Power Control Aspects. [cited by applicant]
R1-1717892 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: CMCC, Title: Discussion on power control framework. [cited by applicant]
R1-1717919 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Panasonic, Title: Discussion on NR power control framework. [cited by applicant]
R1-1717983 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: LG Electronics, Title: Discussion on UL power control for NR. [cited by applicant]
R1-1718031 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: OPPO, Title: On uplink power control for NR. [cited by applicant]
R1-1718228 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: NTT Docomo, Inc., Title: Power control framework for PUSCH. [cited by applicant]
R1-1718502 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: InterDigital, Inc., Title: On NR Power Control Framework. [cited by applicant]
R1-1718592 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Qualcomm Incorporated, Title: Power control and PHR for NR. [cited by applicant]
R1-1718625 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: ITL, Title: UL power control and PHR. [cited by applicant]
R1-1718652 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Ericsson, Title: NR power control framework. [cited by applicant]
R1-1718655 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Ericsson, Title: Further details on closed loop power control. [cited by applicant]
R1-1718692 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Discussion on NR power control framework. [cited by applicant]
R1-1718704 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Motorola Mobility, Lenovo, Title: On NR power control. [cited by applicant]
3GPP TS 36.413 V13.3.0 (Jun. 2016), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Appli… [cited by applicant]
3GPP TS 36.211 V14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels… [cited by applicant]
3GPP TS 36.212 V14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and … [cited by applicant]
3GPP TS 36.213 V14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer pr… [cited by applicant]
3GPP TS 36.321 V10.3.0 (Sep. 2011), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Con… [cited by applicant]
3GPP TS 36.321 V14.3.0 (Jun. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Con… [cited by applicant]
3GPP TS 36.331 V14.3.0 (Jun. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Co… [cited by applicant]
3GPP TR 38.802 V14.1.0 (Jun. 2017), Technical Report, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio Access Technology Physical Layer Aspects (Release 14). [cited by applicant]
3GPP TR 38.912 V14.0.0 (Mar. 2017), Technical Report, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio (NR) Access Technology (Release 14). [cited by applicant]
3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Title: RAN1 Chairman's Notes. [cited by applicant]
3GPP TSG RAN WG1 Meeting #93, Busan, Korea, May 21-25, 2018, Title: RAN1 Chairman's Notes. [cited by applicant]
3GPP TSG RAN WG2 NR Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Session Chair (InterDigital), Title: Report from LTE and NR User Plane Break-Out Session. [cited by applicant]
R2-1711835 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Session Chair (InterDigital), Title: Report from LTE and NR User Plane Break-Out Session. [cited by applicant]
R1-1716353 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Ericsson, Title: On dynamic triggering for CSI reports and CSI-RS. [cited by applicant]
R1-1716354 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Ericsson, Title: A comparison of CSI-RS activation schemes based on MAC CE and DCI. [cited by applicant]
R1-1716357 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Ericsson, Title: On semi-persistent CSI reporting on PUSCH. [cited by applicant]
R1-1717939 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: LG Electronics, Title: Discussion on CSI measurement. [cited by applicant]
R1-1801073 3GPP TSG RAN WG1 NR Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: RAN2, Title: LS on PDCCH order for initiation of random access. [cited by applicant]
R1-1805701 3GPP TSG RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Qualcomm Incorporated, Title: Summary of Remaining Details on RACH Procedure. [cited by applicant]
R1-1805876 3GPP TSG RAN WG1 Meeting #93, Busan, Korea, May 21-25, 2018, Source: Huawei, HiSilicon, Title: Remaining details of RACH Procedures. [cited by applicant]
R1-1807747 3GPP TSG RAN WG1 Meeting #93, Busan, Korea, May 21-25, 2018, Source: Qualcomm Incorporated, Title: Summary of Remaining Details on RACH Procedure. [cited by applicant]
R2-1800688 3GPP TSG RAN WG2 NR Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Need for PDCCH order. [cited by applicant]
Sep. 9, 2019—European Extended Search Report—EP 19174705.4. [cited by applicant]
Sep. 16, 2019—European Extended Search Report—EP 19175772.3. [cited by applicant]
R2-1712212 3GPP TSG RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: ASUSTek, Title: Details of BWP inactivity timer. [cited by applicant]
Sep. 26, 2019—European Extended Search Report—EP 19175077.7. [cited by applicant]
R1-1718581 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Qualcomm Incorporated, Title: Open Issues on CA. [cited by applicant]
Nov. 22, 2019—European Office Action—EP 18205418.9. [cited by applicant]
Jan. 3, 2020—European Extended Search Report—EP 19189782.6. [cited by applicant]
R2-1806991 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: CATT, Title: Further issues with switching of bandwidth part and random access. [cited by applicant]
R2-1809515 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: CATT, Title: Further issues with DL BWP switching for CFRA. [cited by applicant]
R2-1810513 3GPP TSG RAN WG2 NR AH1807, Montreal, Canada, Jul. 2-6, 2018, Source: Huawei, HiSilicon, Title: Clarification on RA procedure for BFR on BWPs without CBRA occasions. [cited by applicant]
Korean Patent Application No. 2017-0125585, titled “Method and Apparatus for Radio Link Failure Handling in the System Using Multiple Reference Signals”, filed Sep. 27, 2017 (application as filed and machine translation… [cited by applicant]
Korean Patent Application No. 2017-0101952, titled “Method and Apparatus for Transmitting Uplink Control Information in Wireless Communication”, filed Aug. 10, 2017 (application as filed and machine translation). [cited by applicant]
R1-171xxxx 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: MCC Support, Title: Draft Report of 3GPP TSG RAN WGI #90bis v0.1.0. [cited by applicant]
R1-1715453 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Source: ZTE, Sanechips, Title: QCL design for UL and DL MIMO. [cited by applicant]
Nov. 25, 2020—EP Search Report—20202192.9. [cited by applicant]
Zhang, U.S. Appl. No. 62/564,973, filed Sep. 28, 2017 (Year: 2017). [cited by applicant]
MCC Support: “Draft Report of 3GPP TSG RAN WG1 #90bis v0.1.0”, 3GPP Draft; DRAFT_MINUTES_REPORT_RAN1#90B_V010, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles; F-06921 Sophi… [cited by applicant]
Zte et al: “QCL design for UL and DL MIMO”, 3GPP Draft; R1-1715453 Qcl Design for UL and DL MIMO, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles; F-06921 Sophia-Antipolis C… [cited by applicant]
3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: MCC Support, Title: Draft Report of 3GPP TSG RAN WGI #90bis v0.1.0. [cited by applicant]
U.S. Appl. No. 62/567,199, filed Oct. 2, 2017 (Year: 2017). [cited by applicant]
U.S. Appl. No. 62/557,016, filed Sep. 11, 2017 (Year: 2017). [cited by applicant]
U.S. Appl. No. 62/566,537, filed Oct. 2, 2017 (Year: 2017). [cited by applicant]
U.S. Appl. No. 62/587,058, filed Nov. 16, 2017 (Year: 2017). [cited by applicant]
R1-1718784; 3GPP TSG-RAN WG1 #90bis; Prague, Czech Republic, Oct. 9-13, 2017; Source: Ericsson; Title: Summary of views on CSI reporting (agenda item 7.2.2.2); Agenda Item: 7.2.2.2; Document for: Discussion and Decision. [cited by applicant]
Extended European Search Report mailed Jul. 11, 2025 in EP Patent Application No. 25166106.2. [cited by applicant]
R1-171XXXX (R1-1719118); 3GPP TSG RAN WG1 Meeting 90bis; Prague, CZ, Oct. 9-13, 2017; Title: RAN1 session notes for agenda item 7.2 (MIMO); Source: Adhoc chair (Samsung). [cited by applicant]
R1-1705346; 3GPP TSG RAN WG1 Meeting #88bis; Spokane, USA Apr. 3-7, 2017; Agenda item: 8.1.2.3.2; Source: Samsung; Title: Discussions on CSI measurements and reporting for NR; Document for: Discussion and Decision. [cited by applicant]
Cited By (2)
US 12,707,293 US 12,713,417