Maintenance of NR-based Access to Unlicensed Spectrum

Physical Layer Signals and Channels

Initial access signals/channels

R1-2001649	Remaining issues on initial access signals and channles	vivo

R1-2001702	Remaining issues on the initial access signals for NR-U	ZTE, Sanechips

R1-2001756	Discussion on the remaining issues of initial access signal/channel	OPPO

R1-2001932	Remaining issues of initial access signals and channels for NR-U	LG Electronics

R1-2002028	Initial access signals and channels	Ericsson

R1-2002114	Initial access signals and channels for NR-U	Samsung

R1-2002224	Remaining issues on Initial Access Signals and Channels for NR-U	Nokia, Nokia Shanghai Bell

R1-2002262	Remaining issues on initial access signals/channels	Spreadtrum Communications

R1-2002575	Maintainance on the initial access signals and channels	Huawei, HiSilicon

[100b-e-NR-unlic-NRU-InitSignalChannel-01] Email discussion/approval on k_SSB indication in PBCH for SSB on sync raster and off-sync raster by 4/22; if necessary, followed by endorsing the corresponding TP by 4/28 – Jing (Qualcomm)

Proposal:

Adopt the following text proposal for Section 7.4.3.1 of TS 38.211:

----------------------------------------- Begin Text Proposal -----------------------------

7.4.3.1	Time-frequency structure of an SS/PBCH block

In the time domain, an SS/PBCH block consists of 4 OFDM symbols, numbered in increasing order from 0 to 3 within the SS/PBCH block, where PSS, SSS, and PBCH with associated DM-RS are mapped to symbols as given by Table 7.4.3.1-1.

In the frequency domain, an SS/PBCH block consists of 240 contiguous subcarriers with the subcarriers numbered in increasing order from 0 to 239 within the SS/PBCH block. The quantities and represent the frequency and time indices, respectively, within one SS/PBCH block. The UE may assume that the complex-valued symbols corresponding to resource elements denoted as 'Set to 0' in Table 7.4.3.1-1 are set to zero. The quantity in Table 7.4.3.1-1 is given by . The quantity is the subcarrier offset from subcarrier 0 in common resource block to subcarrier 0 of the SS/PBCH block, where is obtained from the higher-layer parameter offsetToPointA and the 4 least significant bits of are given by the higher-layer parameter ssb-SubcarrierOffset and for SS/PBCH block type A the most significant bit of is given by in the PBCH payload as defined in clause 7.1.1 of [4, TS 38.212]. For operation with shared spectrum channel access, 4 least significant bits of are given by the higher-layer parameter ssb-SubcarrierOffset and the most significant bit of is given by in the PBCH payload as defined in clause 7.1.1 of [4, TS 38.212]. If , ; otherwise, . If ssb-SubcarrierOffset is not provided, is derived from the frequency difference between the SS/PBCH block and Point A.

--------------------------------------- End Text Proposal ---------------------------------------------------------

Proposal:

Adopt the following text proposal for Section 4.1 of TS 38.213

------------------------------------ Begin Text Proposal ----------------------------

*** Unchanged text omitted ***

is either provided by ssbPositionQCL-Relationship-r16 or, if ssbPositionQCL-Relationship-r16 is not provided, obtained from a MIB provided by a SS/PBCH block according to Table 4-1 when <24 as defined in clause 7.4.3.1 of [4, 38.211].

*** Unchanged text omitted ***

-------------------------------------- End Text Proposal --------------------------------------

DL signals and channels

R1-2001532	Maintainance on DL signals and channels	Huawei, HiSilicon

R1-2001650	Remaining issues on physical DL channel design in unlicensed spectrum	vivo

R1-2001703	Remaining issues on the DL channels for NR-U	ZTE, Sanechips

R1-2001757	Discussion on the remaining issues of DL signals and channels	OPPO

R1-2001902	Remaining issues on DL signals and channels for NR-U	MediaTek Inc.

R1-2001933	Remaining issues of DL signals and channels for NR-U	LG Electronics

R1-2001985	DL signals and channels for NR-unlicensed	Intel Corporation

R1-2002029	DL signals and channels	Ericsson

R1-2002054	Maintenance for DL signals and channels for NR-U	Panasonic Corporation

R1-2002115	DL signals and channels for NR-U	Samsung

R1-2002225	Remaining issues on DL signals and channels	Nokia, Nokia Shanghai Bell

R1-2002275	Remaining issues in DL signals and channels	Spreadtrum Communications

R1-2002320	Remaining issues of DL signals and channels	Apple

R1-2002381	Remaining issues and corrections on DL signals and channels for NR-U	Sharp

R1-2002528	TP for DL signals and channels for NR-U	Qualcomm Incorporated

R1-2002630	Text proposal for search space group switching	Google Inc.

R1-2002685	Feature lead summary for NR-U DL Signals and Channels	Moderator (Lenovo)

[100b-e-NR-unlic-NRU-DL_Signals_and_Channels-01] Email discussion/approval on processing time for switching and default SS group, including BWP switching by 4/24; if necessary, followed by endorsing the corresponding TPs by 4/30 – Alex (Lenovo)

[100b-e-NR-unlic-NRU-DL_Signals_and_Channels-02] Email discussion/approval on special states/indications in “available RB set indication” and COT duration indication/determination by 4/23; if necessary, followed by endorsing the corresponding TPs by 4/29 – Alex (Lenovo)

[100b-e-NR-unlic-NRU-DL_Signals_and_Channels-03] Email discussion/approval on CSI-RS measurements including validity/presence of periodic/semi-persistent CSI-RS by 4/24; if necessary, followed by endorsing the corresponding TPs by 4/30 – Alex (Lenovo)

[100b-e-NR-unlic-NRU-DL_Signals_and_Channels-04] Email discussion/approval on the following from prior meetings by 4/23 – Alex (Lenovo)

Capture "For search space switching, limit the switching to USS and Type-3 CSS."

Align the terminology on the RB set indicator/Available RB set Indicator in TS38.213 and TS38.212.

Align RRC parameter list with TS38.213:

Configurations of availableRB-SetPerCell-r16, CO-DurationPerCell-r16 and SearchSpaceSwitchTrigger-r16 should be added in SlotFormatCombinationsPerCell,

Propose to RAN2 to discard the “groupId” parameter defined under searchSpaceSwitchTrigger-r16, and remove the CHOICE structure

UL signals and channels

R1-2001533	Maintainance on uplink signals and channels	Huawei, HiSilicon

R1-2001651	Remaining issues on physical UL channel design in unlicensed spectrum	vivo

R1-2001704	Remaining issues on the UL channels for NR-U	ZTE, Sanechips

R1-2001758	Discussion on the remaining issues of UL signals and channels	OPPO

R1-2001875	Remaining issues on UL signals and channels for NR-U	Fujitsu

R1-2001903	Remaining issues on UL signals and channels for NR-U	MediaTek Inc.

R1-2001934	Remaining issues of UL signals and channels for NR-U	LG Electronics

R1-2001973	Remaining issues for UL signals and channels for NR-U	Lenovo, Motorola Mobility

R1-2001986	UL signals and channels for NR-unlicensed	Intel Corporation

R1-2002030	UL signals and channels	Ericsson

R1-2002075	TP for SRS configuration	CATT

R1-2002116	UL signals and channels for NR-U	Samsung

R1-2002192	Remaining Issues on UL Signals and Channels for NR-U	Nokia, Nokia Shanghai Bell

R1-2002246	UL signals and channels	ETRI

R1-2002276	Remaining issues in UL signals and channels	Spreadtrum Communications

R1-2002321	Remaining issues of UL signals and channels	Apple

R1-2002365	TPs on uplink signals in NRU	NEC

R1-2002382	Remaining issues on UL signals/channels for NR-U	Sharp

R1-2002433	Remaining issues on UL signals and channels for NR-U	NTT DOCOMO, INC.

R1-2002529	TP for UL signals and channels for NR-U	Qualcomm Incorporated

R1-2002036	Feature Lead Summary for UL Signals and Channels	Ericsson

[100b-e-NR-unlic-NRU-ULSignalsChannels-01] Email discussion/approval on the following issues

by 4/23; if necessary, followed by endorsing the corresponding TPs by 4/29 – Steve (Ericsson)

Finalize design for FDRA field of DCI 0_0 for UL resource allocation Type 2

Editorial correction on interlace configuration

[100b-e-NR-unlic-NRU-ULSignalsChannels-02] Email discussion/approval on the following issues

by 4/24; if necessary, followed by endorsing the corresponding TPs by 4/30 – Steve (Ericsson)

Capture UE procedure related to FDRA field in RAR UL grant

Editorial correction on SRS

[100b-e-NR-unlic-NRU-ULSignalsChannels-03] Email discussion/approval on the following issues

by 4/22; if necessary, followed by endorsing the corresponding TPs by 4/28 – Steve (Ericsson)

Rule for interlaced PUCCH allocation for a carrier without guard bands

Editorial (but critical) corrections on PUCCH

Physical Layer Procedure

Channel access procedures

R1-2002284	Feature lead summary on NR-U channel access procedures	Moderator (Nokia)

R1-2001534	Maintainance on the channel access procedure	Huawei, HiSilicon

R1-2001652	Remaining issues on the channel access procedures	vivo

R1-2001705	Remaining issues on the channel access procedure for NR-U	ZTE, Sanechips

R1-2001759	Discussion on the remaining issues of channel access procedure	OPPO

R1-2001935	Remaining issues of channel access procedure for NR-U	LG Electronics

R1-2001987	Channel access mechanism for NR-unlicensed	Intel Corporation

R1-2002031	Channel access procedures	Ericsson

R1-2002117	Channel access procedures for NR-U	Samsung

R1-2002193	Remaining Issues on Channel Access Procedures for NR-U	Nokia, Nokia Shanghai Bell

R1-2002247	Remaining issues on channel access procedures for NR-U	ETRI

R1-2002383	Remaining issues and corrections on channel access procedure for NR-U	Sharp

R1-2002405	Remaining issues on channel access for NR-U operation	MediaTek Inc.

R1-2002434	Remaining issues on channel access procedures for NR-U	NTT DOCOMO, INC.

R1-2002465	TP on shared spectrum in NR-U	NEC

R1-2002530	TP for Channel access procedures for NR unlicensed	Qualcomm Incorporated

R1-2002632	Remaining issues on channel access procedure for NR-U	WILUS Inc.

R1-2002684	COT sharing information in CG-UCI	Lenovo, Motorola Mobility

[100b-e-NR-unlic-NRU-ChAcc-01] Email discussion/approval on clarifications to LBT with consecutive UL transmissions by 4/23; if necessary, followed by endorsing the corresponding TPs by 4/28 – Timo (Nokia)

[100b-e-NR-unlic-NRU-ChAcc-02] Email discussion/approval on clarifications to UL to DL COT sharing by 4/24; if necessary, followed by endorsing the corresponding TPs by 4/29 – Timo (Nokia)

Enhancements to initial access procedure

R1-2001535	Maintainance on the initial access procedures	Huawei, HiSilicon

R1-2001653	Remaining issues on initial access procedure for NR-U	vivo

R1-2001706	Remaining issues on the initial access procedure for NR-U	ZTE, Sanechips

R1-2001760	Discussion on the remaining issues of enhancements to initial access procedure	OPPO

R1-2001936	Remaining issues of initial access and mobility for NR-U	LG Electronics

R1-2001988	Enhancements to initial access and mobility for NR-unlicensed	Intel Corporation

R1-2002032	Enhancements to initial access procedures	Ericsson

R1-2002118	Initial access procedures for NR-U	Samsung

R1-2002248	Remaining issues on initial access procedure for NR-U	ETRI

R1-2002263	Remaining issues on initial access procedure	Spreadtrum Communications

R1-2002278	On Enhancements to Initial Access Procedures for NR-U	Nokia, Nokia Shanghai Bell

R1-2002407	Remaining issues on initial access procedure for NR-U operation	MediaTek Inc.

R1-2002531	TP for Initial access and mobility procedures for NR-U	Qualcomm Incorporated

R1-2001701	Feature lead summary on NR-U enhancement to initial access procedures	Moderator (Charter Communications, Inc)

[100b-e-NR-unlic-NRU-InitAccessProc-01] Email discussion/approval on following issues related to SS/PBCH blocks by 4/24; if necessary, followed by endorsing the corresponding TPs by 4/29 – Amitav (Charter)

Finalize remaining details of parameter Q signalling and interpretation

Correct the citation of TS 38.104 in TS 38.213 Subclause 4.1 in relation to the definition of L_max

[100b-e-NR-unlic-NRU-InitAccessProc-02] Email discussion/approval on following issues related to RA procedure by 4/24; if necessary, followed by endorsing the corresponding TPs by 4/29 – Amitav (Charter)

MsgA PRACH-PUSCH gap for NR-U

Remaining details of RACH occasion validation for FBE access

[100b-e-NR-unlic-NRU-InitAccessProc-03] Email discussion/approval on following issues related to RRM/RLM by 4/23; if necessary, followed by endorsing the corresponding TPs by 4/28 – Amitav (Charter)

TP to 38.215 for RSSI definition

Finalize the number of OFDM symbols for RSSI measurement duration configuration

[100b-e-NR-unlic-NRU-InitAccessProc-04] Email approval of the reply LS for R1-2001237 by 4/23 - Zhipeng (Ericsson)

[100b-e-NR-unlic-NRU-InitAccessProc-05] Email approval of the corresponding TP to address LS from RAN2 in R1-2001506 by 4/23 - Jing (Qualcomm)

HARQ enhancement

R1-2001536	Maintainance on HARQ-ACK enhancement	Huawei, HiSilicon

R1-2001654	Remaining issues on HARQ operation for NR-U	vivo

R1-2001707	Remaining issues on the HARQ for NR-U	ZTE, Sanechips

R1-2001761	Discussion on the remaining issues of HARQ enhancements	OPPO

R1-2001904	Remaining issues on HARQ operation for NR-U	MediaTek Inc.

R1-2001937	Remaining issues of HARQ procedure for NR-U	LG Electronics

R1-2001974	Remaining issues for HARQ enhancement for NR-U	Lenovo, Motorola Mobility

R1-2001989	Enhancements to HARQ for NR-unlicensed	Intel Corporation

R1-2002033	HARQ enhancement	Ericsson

R1-2002119	HARQ enhancement for NR-U	Samsung

R1-2002227	Remaining issues on NR-U HARQ scheduling and feedback	Nokia, Nokia Shanghai Bell

R1-2002249	HARQ enhancement	ETRI

R1-2002306	One shot HARQ ACK feedback	InterDigital, Inc.

R1-2002384	Remaining issues and corrections on HARQ enhancement for NR-U	Sharp

R1-2002532	TP for Enhancements to Scheduling and HARQ Operation for NR-U	Qualcomm Incorporated

R1-2002631	Text proposal for enhanced dynamic HARQ procedures	Google Inc.

R1-2002696	Feature lead summary#1 on NR-U HARQ	Moderator (Huawei)

[100b-e-NR-unlic-NRU-HARQ-01] Email discussion/approval on following issues related to Type-3 HARQ-ACK codebook by 4/23; if necessary, followed by endorsing the corresponding TPs by 4/29 – David (Huawei)

Remaining details on triggering Type-3 HARQ-ACK codebook feedback with a DCI that does not schedule a PDSCH

Clarification to remove unintended limitations on Type-3 HARQ-ACK codebook usage (when no NNK1 value was received, when the UE is configured with semi-static codebook)

Clarification that Type-3 HARQ-ACK codebook feedback should be generated for all configured serving cells

[100b-e-NR-unlic-NRU-HARQ-02] Email discussion/approval on following issues related to Type-2 enhanced HARQ-ACK codebook by 4/24; if necessary, followed by endorsing the corresponding TPs by 4/30 – David (Huawei)

How to determine NFI, number of requested groups and PUCCH occasions i(g) and i((g+1) mod 2) when multiple DCIs provide these values

How is T-DAI interpreted in DCI 1_1 for the non-scheduled group when two sub-codebooks (for TB and CBG) are configured

Second HARQ-ACK information generation in case of toggled NFI for the non-scheduled group in a DCI scheduling PDSCH for another group

[100b-e-NR-unlic-NRU-HARQ-02] Email discussion/approval on handling of SPS with enhanced dynamic codebook and with NNK1 by 4/24; if necessary, followed by endorsing the corresponding TPs by 4/30 – David (Huawei)

Configured grant enhancement

R1-2001657	Feature lead summary on NRU configured grant enhancement	Moderator (vivo)

R1-2001537	Maintainance on the configured grant procedures	Huawei, HiSilicon

R1-2001655	Remaining issues on the enhancements to configured grant	vivo

R1-2001708	Remaining issues on the configured grant for NR-U	ZTE, Sanechips

R1-2001762	Discussion on the remaining issues of configured grant enhancements	OPPO

R1-2001814	Remaining issues on configured grant enhancement for NR-U	Sony

R1-2001938	Remaining issues of configured grant for NR-U	LG Electronics

R1-2001975	Remaining issues for configured grant enhancement for NR-U	Lenovo, Motorola Mobility

R1-2001990	Enhancements to configured grants for NR-unlicensed	Intel Corporation

R1-2002034	Configured grant enhancement	Ericsson

R1-2002120	Configured grant enhancement for NR-U	Samsung

R1-2002162	Clarification on NR-U configured grant enhancement	Panasonic Corporation

R1-2002194	Remaining Issues on Configured Grant Enhancement for NR-U	Nokia, Nokia Shanghai Bell

R1-2002435	Remaining issues on configured grant enhancement for NR-U	NTT DOCOMO, INC.

R1-2002533	TP for Enhancements to configured grants for NR-U	Qualcomm Incorporated

R1-2002633	Remaining issue on configured grant for NR-U	WILUS Inc.

R1-2002737	Feature lead summary#2 on NRU configured grant enhancement	Moderator (Vivo)

R1-2002745	Summary of prep email discussion on NRU-CG	Moderator (Vivo)

[100b-e-NR-unlic-NRU-CG-01] Email discussion/approval on following issues by 4/23; if necessary, followed by endorsing the corresponding TPs by 4/28 – Rakesh (Vivo)

RRC value ranges for RRC parameters

Correction related to semiPersistentOnPUSCH

Clarification on offset-r16

TP on CG-UCI transmission

[100b-e-NR-unlic-NRU-CG-02] Email discussion/approval on following issues by 4/24; if necessary, followed by endorsing the corresponding TPs by 4/29 – Rakesh (Vivo)

PUSCH repetition transmission related issues for NRU configured grant

RV determination for CG repetition

Wide-band operation

R1-2001940	Summary on maintenance of wide-band operation for NR-U	Moderator (LG Electronics)

R1-2001538	Maintainance on the wideband operation procedures	Huawei, HiSilicon

R1-2001656	Remaining issues on wideband operation in NR-U	vivo

R1-2001709	Remaining issues on the wideband operation for NR-U	ZTE, Sanechips

R1-2001763	Discussion on the remaining issues of wide-band operations	OPPO

R1-2001905	Remaining issues on wideband operation for NR-U	MediaTek Inc.

R1-2001939	Remaining issues of wide-band operation for NR-U	LG Electronics

R1-2001991	Wideband operation for NR-unlicensed	Intel Corporation

R1-2002035	Wideband operation	Ericsson

R1-2002121	Wide-band operation for NR-U	Samsung

R1-2002198	Remaining issues on Rel-16 NR-U wideband operations	Panasonic

R1-2002226	Remaining issues on Wideband operation in NR-U	Nokia, Nokia Shanghai Bell

R1-2002277	Remaining issues in wide-band operation	Spreadtrum Communications

R1-2002322	Remaining issues of wideband operation	Apple

R1-2002385	Remaining issues on wide-band operation for NR-U	Sharp

R1-2002534	TP for Wideband operation for NR-U operation	Qualcomm Incorporated

R1-2002722	Summary#2 on maintenance of wide-band operation for NR-U	Moderator (LG Electronics)

[100b-e-NR-unlic-NRU-WB-01] Email discussion/approval on following issues related to RB set and intra-cell guard band configuration by 4/23; if necessary, followed by endorsing the corresponding TPs by 4/28 – Seonwook (LGE)

Corrections based on RAN1 and RAN2 agreements, and for RB set index within a BWP

Handling of the case where “no guard band” is configured, without considering signaling aspects

[100b-e-NR-unlic-NRU-WB-02] Email discussion/approval on following issues related to CORESET and search space configuration by 4/24; if necessary, followed by endorsing the corresponding TPs by 4/29 – Seonwook (LGE)

PDCCH candidate and CCE mapping for search space configured with freqMonitorLocations-r16 (Note: Discussion on PDCCH dropping rule is deprioritized)

Corrections for CORESET and search space configured with freqMonitorLocations-r16

Others

R1-2001764	Discussion on the other remaining issues	OPPO

R1-2002576	Other Maintainance for NR-U	Huawei, HiSilicon