CONTROL RESOURCE SET SELECTION FOR CHANNEL STATE INFORMATION REFERENCE

SIGNAL-BASED RADIO LINK MONITORING

CROSS REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of and priority from U.S. Provisional Patent

Application No. 62/720,025 entitled "CORESET SELECTION FOR CSI-RS BASED RLM" filed August 20, 2018, the entire disclosure of which is incorporated herein by reference.

FIELD

[0002] Various embodiments generally may relate to the field of wireless communications, and particularly to Control Resource Set (CORESET) selection.

BACKGROUN D

[0003] In the third generation partnership project (3GPP) (N R) specification, in some scenarios, it may be possible that a configured channel state information reference signal (CSI-RS) is quasi co-located (QCL'ed) with multiple CORESETs. Each CORESET has a set of parameters of which the subcarrier spacing (SCS), number of orthogonal frequency division multiplexing (OFDM) symbols, bandwidth and cyclic prefix (CP) length will be used to determine hypothetical physical downlink control channel (PDCCH) block error rate (BLER). To avoid ambiguity, the rule(s) on how to determine CORESET should be clarified.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Fig. 1 illustrates a process to be performed by a device, such as a baseband processing circuitry, of a UE, according to some embodiments;

[0005] Fig. 2 illustrates an architecture of a system of a network according to some embodiments; and

[0006] Fig. 3 illustrates example interfaces of a baseband circuitry according to some embodiments. DETAILED DESCRIPTION

[0007] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrase "A or B" means (A), (B), or (A and B).

[0008] One or more embodiments described herein are related to one or more third generation partnership project (3GPP) specifications. Examples of these specifications include, but are not limited to, one or more 3GPP New Radio (N R) specifications and one or more specifications directed and/or related to RANI and/or fifth generation (5G) mobile networks/systems.

[0009] As previously noted, in some scenarios, it may be possible that a configured channel state information reference signal (CSI-RS) is quasi co-located (QCLed) with multiple CORESETs. Each CORESET has a set of parameters of which the subcarrier spacing (SCS), number of orthogonal frequency division multiplexing (OFDM) symbols, bandwidth and cyclic prefix (CP) length will be used to determine a hypothetical physical downlink control channel (PDCCH) block error rate (BLER). To avoid ambiguity, the rule(s) on how to determine CORESET should be clarified.

[0010] Embodiments herein provide mechanisms to select one or more CORESETs when CSI- RS is QCLed with multiple CORESETs.

[0011] As mentioned previously, it could be possible that a configured CSI-RS is QCLed with multiple CORESETs. Additionally, a New Radio (NR) evolved Node B (gNodeB/gNodeB) can configure more than one CORESET for a user equipment (UE). Meanwhile, one CSI-RS based radio link monitoring-reference signal (RLM-RS) may be QCLed with one synchronization signal block (SSB), and the SSB may be QCLed with another CORESET. Therefore, the latter CSI-RS can be QCLed to multiple CORESETs. [0012] Each CORESET has a set of parameters of which the SCS, number of OFDM symbols, bandwidth and CP length will be used to determine the hypothetical PDCCH BLER. These parameters of the multiple CORSETs may be the same or totally different. The parameters of each CORESET would determine a hypothetical PDCCH BLER. For each CORESET, the threshold to declare out-of-sync (OOS) for the RLM will be different. To avoid ambiguity, embodiments herein provide mechanisms for determining CORESET.

[0013] In a first embodiments, the gNode B may sends an indication to the UE to tell the U E which CORESET will be (or should be) chosen. In this embodiment, the U E will calculate the hypothetical PDCCH BLER, and the OOS indication is triggered when the BLER is higher than an OOS threshold.

[0014] In a second embodiments, the UE randomly chooses one CORESET if there are multiple candidate CORESETs from which to choose. In this embodiment, the UE will calculate the hypothetical PDCCH BLER, and the OOS indication is triggered when the BLER is higher than the OOS threshold.

[0015] In a third embodiments, the U E checks all the CORESETs, and the OOS indication is triggered only if all the BLERs from all CORESETs are higher than the OOS threshold.

[0016] Radio Link Monitoring (RLM) Aspects

[0017] Section 5 of TS 38.213 V15.2.0 (Section 5), "Radio Link Monitoring (RLM") refers to mechanisms used by the UE for monitoring the downlink (DL) radio link quality of a primary cell for the purpose of indicating out-of-sync/in-sync status to higher layers. The UE is not required to monitor the downlink radio link quality in DL bandwidth parts (BWPs) other than the active DL BWP on the primary cell.

[0018] According to Section 5, if the UE is configured with a secondary cell group (SCG), and the parameter rlf-TimersAndConstants is provided by the higher layers and is not set to release, the downlink radio link quality of the primary secondary cell (PSCell) of the SCG is monitored by the U E for the purpose of indicating out-of-sync/in-sync status to higher layers. The UE is not required to monitor the downlink radio link qua lity in DL BWPs other than the active DL BWP.

[0019] According to Section 5, the UE can be configured for each DL BWP of an SpCell with a set of resource indexes, through a corresponding set of higher layer parameters RadioLinkMonitoringRS, for radio link monitoring by higher layer parameter failureDetectionResources. The UE is provided by higher layer parameter RadioLinkMonitoringRS, with either a CSI-RS resource configuration index (by higher layer parameter csi-RS-tndex), or a synchronization signal (SS) physical broadcast channel (PBCH) (SS/PBCH) block index (by higher layer parameter ssb-lndex). The UE can be configured with up to a number L^ _K _^ _M RadioLinkMonitoringRS for link recovery (LR) procedures, as discussed below, and radio link monitoring. From the L^ _K _^ _M RadioLinkMonitoringRS, up to a number / _RLM RadioLinkMonitoringRS can be used for radio link monitoring depending on a maximum number L of candidate SS/PBCH blocks per half frame, and up to two RadioLinkMonitoringRS can be used for link recovery procedures.

[0020] According to Section 5, if the UE is not provided higher layer parameter RadioLinkMonitoringRS and the UE is provided by higher layer parameter TCt-state for PDCCH (with TCI referring to transmission configuration indication), one or more reference signals (RSs) that include one or more of a CSI-RS and/or a SS/PBCH block:

[0021] - the UE uses for radio link monitoring the RS provided for the active TCI state for PDCCH if the active TCI state for PDCCH includes only one RS;

[0022] - if the active TCI state for PDCCH includes two RSs, the UE expects that one RS has QCL-TypeD and the UE uses the one RS for radio link monitoring; the UE does not expect both RS to have QCL-TypeD

[0023] - the UE is not required to use for radio link monitoring an aperiodic RS

[0024] According to Section 5, the UE is not expected to use more than /n^ _M RadioLinkMonitoringRS for radio link monitoring when the UE is not provided higher layer pa ra m ete r RadioLinkMonitoringRS.

[0025] Values of L^ _K _^ _M and for different values of L are given in Table 5-1 of TS 38.213 V15.2.0.

[0026] According to Section 5, for a CSI-RS resource configuration, the higher layer parameter powerControiOffsetSS\s not applicable and a UE expects to be provided only 'No CDM' from higher layer parameter cdm-Type, only Ί' and '3' from higher layer parameter density, and only Ί port' from higher layer parameter nrofPorts, with CDM referring to code division multiplexing.

[0027] According to Section 5, in non-discontinuous reception (non-DRX) mode operation, the physical layer in the UE assesses once per indication period the radio link quality, evaluated over the previous time period against thresholds (Q _out and Qi _n ) configured by higher layer parameter rlmlnSyncOutOfSyncThreshold. The UE determines the indication period as the maximum between the shortest periodicity for radio link monitoring resources and 10 msec.

[0028] According to Section 5, in DRX mode operation, the physical layer in the UE assesses once per indication period the radio link quality, evaluated over the previous time period, against thresholds (Q _out and Qi _n ) provided by higher layer parameter rlmlnSyncOutOfSyncThreshold. The UE determines the indication period as the maximum between the shortest periodicity for radio link monitoring resources and the DRX period.

[0029] According to Section 5, the physical layer in the UE indicates, in frames where the radio link quality is assessed, out-of-sync to higher layers when the radio link quality is worse than the threshold Q _out for all resources in the set of resources for radio link monitoring. When the radio link quality is better than the threshold Qi _n for any resource in the set of resources for radio link monitoring, the physical layer in the UE indicates, in frames where the radio link quality is assessed, in-sync to higher layers.

[0030] According to an embodiment, a device of the UE, such as a baseband processor or other circuitry, is to decode a signal from a NR evolved node B (gNodeB) including an indication of one or more control resource sets (CORESETs), to select a CORESET based on the indication and to determine a downlink radio link quality based on the CORESET.

[0031] Referring to Fig. 2, a process 100 is shown for a method embodiment as described above. Operation 102 includes decoding a signal from a N R evolved node B (gNodeB) including an indication of one or more control resource sets (CORESETs). Operation 104 includes selecting a CORESET based on the indication. Operation 106 includes determining a downlink radio link quality based on the CORESET.

[0032] According to one embodiment, the UE is to monitor the downlink link quality based on the reference signal in the configured RLM-RS resource(s) in order to detect the downlink radio link quality of the PCell and PSCell. The configured RLM-RS resources can be all SSBs, or all CSI- RSs, or a mix of SSBs and CSI-RSs. The U E is not required to perform RLM outside the active DL BWP. The reference signal for RLM is a resource out of the set of resources configured for RLM by higher layer parameter RLM-RS-List.

[0033] According to an embodiment, on each RLM-RS resource, the UE is to estimate the downlink radio link quality and compare it to the thresholds Q _out and Qm for the purpose of monitoring downlink radio link quality of the cell. The threshold Q _out is defined as the level at which the downlink radio link cannot be reliably received and is to correspond to the out-of- sync block error rate (BLER _0Ut ) as defined in Table RLM.1-1 below. For SSB based radio link monitoring, Q _0U t_ssB is derived based on the hypothetical PDCCH transmission parameters listed in Table RLM.2-1 below. For CSI-RS based radio link monitoring, Q _ou t_csi-Rs is derived based on the hypothetical PDCCH transmission parameters listed in Table RLM.3-1 below.

[0034] The threshold Q _m is defined as the level at which the downlink radio link quality can be significantly more reliably received than at Q _out and is to correspond to the in-sync block error rate (BLERm) as defined in Table RLM.1-1. For SSB based radio link monitoring, Q _m sse is derived based on the hypothetical PDCCH transmission parameters listed in Table RLM .2-2. For CSI-RS based radio link monitoring, Qin csi-Rs is derived based on the hypothetical PDCCH transmission parameters listed in Table RLM.3-2.

[0035] According to an embodiment, the out-of-sync block error rate (BLER _0U t) and in-sync block error rate (BLERm) are determined from the network configuration via parameter RLM- IS-OOS-thresholdConfig signaled by higher layers. The network can configure one of the two pairs of out-of-sync and in-sync block error rates which are shown in Table RLM.1-1 below. When the U E is not configured with RLM-IS-OOS-thresholdConfig from the network, the U E determines out-of-sync and in-sync block error rates from Configuration #0 in Table RLM.1-1 as a default.

Table RLM.1-1: Out-of-sync and in-sync block error rates

[0036] According to an embodiment, the UE is to be able to monitor up to a value XRLM-RS RLM- RS resources of the same or different types in each corresponding carrier frequency range, where XRLM-RS is specified in Table RLM.1-2, and meets the requirements as specified below.

Table RLM.1-2: Maximum number of RLM-RS resources XRLM-RS

[0037] Requirements for SSB based radio link monitoring

[0038] According to one embodiment, each SSB based RLM-RS resource is configured for a PCell and/or a PSCell provided that the SSBs configured for RLM are actually transmitted within UE active DL BWP during an entire evaluation period as explained further below in the context of Tables RLM.2-3 and RLM.2-4.

Table RLM.2-1: PDCCH transmission parameters for out-of-sync

Table RLM.2-2: PDCCH transmission parameters for in-sync

[0039] Minimum Requirements

[0040] According to an embodiment, the UE is to be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last T _E v _ai u _ate-o u _t _ss _B [ms] period becomes worse than the threshold Q _0U t_ssB within TEvaiuate_out_ssB [ms] evaluation period. [0041] UE is to be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last TE _Va iuatejn_ssB [ms] period becomes better than the threshold Qm_ssB within T _Eva iuatejn_ssB [ms] evaluation period.

[0042] TEvaiuate_out_ssB and TEvaiuatejn_ssB are defined in Table RLM.2-3 herein for FR1

(corresponding to a frequency range from 410 MHz - 7125 MHz).

[0043] T _Evaiuate-out _ss _B and T _Evaiuatejn _ss _B are defined in Table RLM.2-4 herein for FR2 with

N=l, if the SSB configured for RLM is spatially QCLed and TDMed (time division multiplexed) to CSI-RS resources configured for BM, and the QCL association is known to UE;

N=FFS, otherwise.

For FR1,

P=l/(1 - T _SS B/MGRP), when in the monitored cell there are measurement gaps configured for intra-frequency, inter-frequency or inter-RAT measurements, which are overlapping with some but not all occasions of the SSB; and

P=1 when in the monitored cell there are no measurement gaps overlapping with any occasion of the SSB.

For FR2,

P=l/(1 - Tsse/TsMTCperiod), when RLM-RS is not overlapped with measurement gap and RLM-RS is partially overlapped with SMTC occasion (TSSB < TsMTCperiod).

P is Psharing factor, when RLM-RS is not overlapped with measurement gap and RLM-RS is fully overlapped with SMTC period (TSSB = TsMTCperiod).

P is 1/(1- TSSB/MG RP - Tsse/TsMTCperiod), when RLM-RS is partially overlapped with measurement gap and RLM-RS is partially overlapped with SMTC occasion (T _SS B < TsMTCperiod) and SMTC occasion is not overlapped with measurement gap, and

TsMTCperiod ¹ MGRP OG

TsMTCperiod = MGRP and TSSB < 0.5*TsMTCperiod

P is 1/(1- TSSB /MGRP)* P _{sharing factor} , when RLM-RS is partially overlapped with measurement gap and RLM-RS is partially overlapped with SMTC occasion (TSSB < Ts _MTCperiod ) and SMTC occasion is not overlapped with measurement gap and Ts _MTCperiod = MGRP and TSSB = 0.5*TsMTCperiod

P is 1/{1- TSSB /min (Ts _MTCperiod ,MGRP)}, when RLM-RS is partially overlapped with measurement gap and RLM-RS is partially overlapped with SMTC occasion (TSSB < Ts _MTCpe ri _od ) and SMTC occasion is partially overlapped with measurement gap (Ts _MTCpe ri _od < MGRP)

P is 1/(1- TSSB /MG RP)* Psharing factor, when RLM-RS is partially overlapped with measurement gap and RLM-RS is fully overlapped with SMTC occasion (TSSB = Ts _MTCpe ri _od ) and SMTC occasion is partially overlapped with measurement gap (Ts _MTCpe ri _od < MGRP)

Psharing factor is FFS

[0044] According to an embodiment, a longer evaluation period may be expected if the combination of RLM-RS, SMTC occasion and measurement gap configurations does not meet pervious conditions.

Table RLM.2-3: Evaluation period T _Ev aiuate_out and T _Ev aiuatejn for FR1

Table RLM.2-4: Evaluation period T _EvaiU ate_out and T _EvaiU atejn for FR2

[0045] Requirements for CSI-RS based radio link monitoring

[0046] According to one embodiment, each CSI-RS based RLM-RS resource may be configured for a PCell and/or a PSCell provided that the CSI-RSs configured for RLM are actually transmitted within UE active DL BWP during the entire evaluation period specified below. Table RLM.3-1: PDCCH transmission parameters for out-of-sync

Table RLM.3-2: PDCCH transmission parameters for in-sync

[0047] Minimum requirements

[0048] According to an embodiment, the UE is to be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last TEvaiuate_out_csi-Rs [ms] period becomes worse than the threshold Q _ou t_csi-Rs within TEvaiuate_out_csi-Rs [ms] evaluation period.

[0049] UE is to be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last TE _Va iuatejn_csi-Rs [ms] period becomes better than the threshold Qin_csi-Rs within T _Eva iuatejn_csi-Rs [ms] evaluation period.

TEvaluate_out_CSI-RS and TEvaluateJn _cs i-Rs are defined in Table RLM.3-3 for FR1.

T _E vaiuate_out_csi-Rs and T _Eva iuatejn_csi-Rs are defined in Table RLM.3-4 for FR2, where

N=l, if the CSI-RS resource configured for RLM is spatially QCLed and TDMed to CSI-RS resources configured for BM or SSBs configured for BM, and the QCL association is known to UE;

N=FFS, otherwise.

For FR1,

P=l/(1 - TCSI-RS/MG RP), when in the monitored cell there are measurement gaps configured for intra-frequency, inter-frequency or inter-RAT measurements, which are overlapping with some but not all occasions of the CSI-RS; and

P=1 when in the monitored cell there are no measurement gaps overlapping with any occasion of the CSI-RS.

For FR2,

P=l, when RLM-RS is not overlapped with measurement gap and also not overlapped with SMTC occasion.

P=l/(1 - TCSI-RS/MG RP) , when RLM-RS is partially overlapped with measurement gap and RLM-RS is not overlapped with SMTC occasion (TCSI-RS < MGRP)

P=l/(1 - when RLM-RS is not overlapped with measurement gap and RLM-RS is partially overlapped with SMTC occasion < TsMTCperiod).

P is Psharing factor, when RLM-RS is not overlapped with measurement gap and RLM-RS is fully overlapped with SMTC occasion (T _CS I-R _S = TsMTCperiod).

/TsMTCperiod), when RLM-RS is partially overlapped with measurement gap and RLM-RS is partially overlapped with SMTC occasion (TCSI-RS < Ts _MTCperiod ) and SMTC occasion is not overlapped with measurement gap and TsMTCperiod ¹ MGRP OG

TsMTCperiod = MGRP and Tcsi-RS < 0.5*TsMTCperiod

P is 1/(1- TCSI-RS /MGRP)* Psharing factor, when RLM-RS is partially overlapped with measurement gap and RLM-RS is partially overlapped with SMTC occasion (TCSI-RS < TsMTCperiod) and SMTC occasion is not overlapped with measurement gap and TsMTCperiod = MGRP and TCSI- RS = 0.5*TsMTCperiod

P is 1/{1- TCSI-RS /min (Ts _MTCpe ri _od ,MGRP)}, when RLM-RS is partially overlapped with measurement gap and RLM-RS is partially overlapped with SMTC occasion (TCSI-RS < Ts _MTCpe ri _od ) and SMTC occasion is partially overlapped with measurement gap (Ts _MTCpe ri _od < MGRP)

P is 1/( 1- TCSI-RS /MGRP)* Psharing factor, when RLM-RS is partially overlapped with measurement gap and RLM-RS is fully overlapped with SMTC occasion (TCSI-RS = TsMTCperiod) and SMTC occasion is partially overlapped with measurement gap (TsMTCperiod < MG RP)

Psharing factor is FFS

[0050] According to an embodiment, longer evaluation period would be expected if the combination of RLM-RS, SS/PBCH Block Measurement Time Configuration (SMTC) occasion and measurement gap configurations does not meet pervious conditions.

[0051] The values of M ₀ u _t and Mm used in Table RLM .3-3 and Table RLM.3-4 are defined as:

Mout = 20 and Mm = 10, if the CSI-RS resource configured for RLM is transmitted with Density =3.

Table RLM.3-3: Evaluation period TEvaiuate_out and TEvaiuatejn for FR1

Table RLM.3-4: Evaluation period TEvaiuate_out and T _Ev aiuatejn for FR2

[0052] TCSI-RS refers to the sub-frame configuration cycle, and is a cell specific parameter configured by the higher layer signaling, and is used along with other parameters to define the CSI-RS. TDRX refers to the discontinuous reception cycle.

[0053] Minimum requirement for LI indication

[0054] According to an embodiment, when the downlink radio link quality on all the configured RLM-RS resources is worse than Q _out , Layer 1 of the UE is to send an out-of-sync indication for the cell to the higher layers. A Layer 3 filter is to be applied to the out-of-sync indications.

[0055] According to an embodiment, when the downlink radio link quality on at least one of the configured RLM-RS resources is better than Q _m , Layer 1 of the UE is to send an in-sync indication for the cell to the higher layers. A Layer 3 filter is to be applied to the in-sync indications.

[0056] According to an embodiment, the out-of-sync and in-sync evaluations for the configured RLM-RS resources is to be performed. Two successive indications from Layer 1 is to be separated by at least Tmdicationjntervai.

[0057] According to an embodiment, when DRX is not used Tindicationjntervai is max(10ms, TRLM- RS,M ), where TRLM.M is the shortest periodicity of all configured RLM-RS resources for the monitored cell, which corresponds to TSSB if the RLM-RS resource is SSB, or TCSI-RS if the RLM-RS resource is CSI-RS.

[0058] According to an embodiment, in case DRX is used, upon start of T310 timer, the UE is to monitor the configured RLM-RS resources for recovery using the evaluation period and Layer 1 indication interval corresponding to the non-DRX mode until the expiry or stop of T310 timer.

[0059] Scheduling availability of UE during radio link monitoring [0060] According to an embodiment, when the reference signal to be measured for RLM has different subcarrier spacing than PDSCH/PDCCH and on frequency range FR2, there may be restrictions on the scheduling availability as described below.

[0061] Scheduling availability of UE performing radio link monitoring with a same subcarrier spacing as PDSCH/PDCCH on FR1

[0062] There are no scheduling restrictions due to radio link monitoring performed with a same subcarrier spacing as PDSCH/PDCCH on FR1.

[0063] Scheduling availability of UE performing radio link monitoring with a different subcarrier spacing than PDSCH/PDCCH on FR1

[0064] According to an embodiment, for a UE which support simultaneousRxDataSSB- DiffNumerology [14] there are no restrictions on scheduling availability due to radio link monitoring based on SSB as RLM-RS. For a UE which does not support simultaneousRxDataSSB- DiffNumerology [14] the following restrictions may apply due to radio link monitoring based on SSB as RLM-RS. The UE is not expected to transmit PUCCH/PUSCH or receive PDCCH/PDSCH on SSB symbols to be measured for radio link monitoring. When intra-band carrier aggregation is performed, the scheduling restrictions apply to all serving cells on the band due to radio link monitoring performed on FR1 serving PCell or PSCell in the same band. When inter-band carrier aggregation within FR1 is performed, there are no scheduling restrictions on FR1 serving cell(s) in the bands due to radio link monitoring performed on FR1 serving PCell or PSCell in different bands.

[0065] Scheduling availability of UE performing radio link monitoring on FR2

[0066] According to an embodiment, the following scheduling restriction applies due to radio link monitoring on an FR2 serving PCell and/or PSCell.

[0067] The UE is not expected to transmit PUCCH/PUSCH or receive PDCCH/PDSCH on RLM-RS symbols to be measured for radio link monitoring, except for RMSI PDCCH/PDSCH and PDCCH/PDSCH which is not required to be received by RRC_CONN ECTED mode UE.

[0068] Scheduling availability of UE performing radio link monitoring on FR1 or FR2 in case of FR1-FR2 inter-band CA

[0069] There are no scheduling restrictions on FR1 serving cell(s) due to radio link monitoring performed on FR2 serving PCell and/or PSCell.

[0070] There are no scheduling restrictions on FR2 serving cell(s) due to radio link monitoring performed on FR1 serving PCell and/or PSCell. [0071] Link Recovery Procedures

[0072] According to Section 5, A UE can be provided, for a serving cell, with a set q ₀ of periodic CSI-RS resource configuration indexes by higher layer paramet erfailureDetectionResources and with a set q of periodic CSI-RS resource configuration indexes and/or SS/PBCH block indexes by higher layer parameter candidateBeamRSList for radio link quality measurements on the serving cell. If the UE is not provided with higher layer paramet er failureDetectionResources, the UE determines the set to include SS/PBCH block indexes and periodic CSI-RS resource configuration indexes with same values as the RS indexes in the RS sets indicated by the TCI states for respective control resource sets that the UE uses for monitoring PDCCH. The UE expects the set q ₀ to include up to two RS indexes and, if there are two RS indexes, the set q ₀ includes only RS indexes with QCL-TypeD configuration for the corresponding TCI states. The UE expects single port RS in the set .

[0073] According to Section 5, the threshold corresponds to the default value of higher layer parameter rlmlnSyncOutOfSyncThreshold and to the value provided by higher layer parameter rsrp-ThresholdSSB, respectively..

[0074] According to Section 5, the physical layer in the UE assesses the radio link quality according to the set ¾ of resource configurations against the threshold For the set ¾, the UE assesses the radio link quality only according to periodic CSI-RS resource configurations or SS/PBCH blocks that are quasi co-located, as described in, with the DM-RS of PDCCH receptions monitored by the UE. The UE applies the Q _m.LR threshold to the Ll-RSRP measurement obtained from a SS/PBCH block. The UE applies the Q _m.LR threshold to the Ll- RSRP measurement obtained for a CSI-RS resource after scaling a respective CSI-RS reception power with a value provided by higher layer parameter powerControlOffsetSS.

[0075] According to Section 5, the physical layer in the UE provides an indication to higher layers when the radio link quality for all corresponding resource configurations in the set ¾ that the UE uses to assess the radio link quality is worse than the threshold The physical layer informs the higher layers when the radio link quality is worse than the threshold with a periodicity determined by the maximum between the shortest periodicity of periodic CSI-RS configurations or SS/PBCH blocks in the set q ₀ that the UE uses to assess the radio link quality and 2 msec. [0076] According to Section 5, upon request from higher layers, the UE provides to higher layers the periodic CSI-RS configuration indexes and/or SS/PBCH block indexes from the set q and the corresponding Ll-RSRP measurements that are larger than or equal to the corresponding thresholds.

[0077] According to Section 5, a UE may be provided with a control resource set through a link to a search space set provided by higher layer parameter recoverySearchSpaceld, as described in Subclause 10.1, for monitoring PDCCH in the control resource set. If the UE is provided higher layer para mete r recoverySearchSpaceld, the UE does not expect to be provided another search space set for monitoring PDCCH in the control resource set associated with the search space set provided by recoverySearchSpaceld.

[0078] According to Section 5, the UE may receive by higher layer parameter PRACH- ResourceDedicatedBFR, a configuration for PRACH transmission as described in Subclause 8.1. For PRACH transmission in slot n and according to antenna port quasi co-location parameters associated with periodic CSI-RS configuration or SS/PBCH block with index q _ncw provided by higher layers, the UE monitors PDCCH in a search space provided by higher layer parameter recoverySearchSpaceld for detection of a DCI format with CRC scrambled by C-RNTI starting from slot « + 4 within a window configured by higher layer parameter BeamFailureRecoveryConfig. For the PDCCH monitoring and for the corresponding PDSCH reception, the UE assumes the same antenna port quasi-collocation parameters with index until the UE receives by higher layers an activation for a TCI state or any of the parameters TCI- StatesPDCCFI-ToAddlist and/or TCI-StatesPDCCFI-ToReleaseList. After the UE detects a DCI format with CRC scrambled by C-RNTI in the search space provided by recoverySearchSpaceld, the UE monitors PDCCH candidates in the search space provided by recoverySearchSpaceld until the UE receives a MAC CE activation command for a TCI state or higher layer parameters TCI-StatesPDCCFI-ToAddlist and/or TCI-StatesPDCCFI-ToReleaseList.

[0079] According to Section 5, if the UE is not provided a control resource set for a search space set provided recoverySearchSpaceld or if the UE is not provided recoverySearchSpaceld, the UE does not expect to receive a PDCCH order triggering a PRACH transmission.

[0080] Fig. 2 illustrates an architecture of a system 200 of a network in accordance with some embodiments. The system 200 is shown to include a user equipment (UE) 201 and a UE 202. The UEs 201 and 202 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, or any computing device including a wireless communications interface. These UEs could include NR UEs. The UEs 201 and 202 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 210. The UEs 201 and 202 utilize connections 203 and 204, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 203 and 204 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols.

[0081] In this embodiment, the UEs 201 and 202 may further directly exchange communication data via a ProSe interface 205. The ProSe interface 205 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

[0082] The UE 202 is shown to be configured to access an access point (AP) 206 via connection 207. The connection 207 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 206 would comprise a wireless fidelity (WiFi ^® ) router. In this example, the AP 206 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0083] The RAN 210 can include one or more access nodes that enable the connections 203 and 204. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNodeB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN 210 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 211, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 212.

[0084] In accordance with some embodiments, the UEs 201 and 202 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 211 and 212 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0085] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 211 and 212 to the UEs 201 and 202, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time- frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.

[0086] The RAN 210 is shown to be communicatively coupled to a core network (CN) 220—via an SI interface 213. In embodiments, the CN 220 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the SI interface 213 is split into two parts: the Sl-U interface 214, which carries traffic data between the RAN nodes 211 and 212 and the serving gateway (S-GW) 222, and the Sl-mobility management entity (MME) interface 215, which is a signaling interface between the RAN nodes 211 and 212 and MMEs 221. The CN 220 includes network elements. The term "network element" may describe a physical or virtualized equipment used to provide wired or wireless communication network services. The term "network element" may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, router, switch, hub, bridge, radio network controller, radio access network device, gateway, server, VNF, NFVI, and/or the like.

[0087] In this embodiment, the CN 220 comprises, as network elements, the MMEs 221, the S- GW 222, the Packet Data Network (PDN) Gateway (P-GW) 223, and a home subscriber server (FISS) 224. The MMEs 221 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 221 may manage mobility aspects in access such as gateway selection and tracking area list management. The FISS 224 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 220 may comprise one or several FHSSs 224, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the FISS 224 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0088] The S-GW 222 may terminate the SI interface 213 towards the RAN 210, and routes data packets between the RAN 210 and the CN 220. In addition, the S-GW 222 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter- 3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[0089] The P-GW 223 may terminate an SGi interface toward a PDN. The P-GW 223 may route data packets between the EPC network 223 and external networks such as a network including the application server 230 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 225. Generally, the application server 230 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW 223 is shown to be communicatively coupled to an application server 230 via an IP communications interface 225. The application server 230 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 201 and 202 via the CN 220.

[0090] The P-GW 223 may further be a node for policy enforcement and charging data collection. Policy and Charging Enforcement Function (PCRF) 226 is the policy and charging control element of the CN 220. The PCRF 226 may be communicatively coupled to the application server 230 via the P-GW 223. The application server 230 may signal the PCRF 226 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.

[0091] Fig. 3 illustrates an example of infrastructure equipment 300 in accordance with various embodiments. The infrastructure equipment 300 (or "system 300") may be implemented as a base station, radio head, RAN node, etc., such as the RAN nodes 211 and/or AP 206 shown and described previously. In other examples, the system 300 could be implemented in or by a UE, application server(s) 230, and/or any other element/device discussed herein. The system 300 may include one or more of application circuitry 305, baseband circuitry 310, one or more radio front end modules 315, memory circuitry 320, power management integrated circuitry (PMIC) 345, power tee circuitry 330, network controller circuitry 335, network interface connector

320, satellite positioning circuitry 345, and user interface 350. In some embodiments, the device 300 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for CRAN, vBBU, or other like implementations).

[0092] As used herein, the term "circuitry" may refer to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (FICPLD), a structured ASIC, or a programmable System on Chip (SoC)), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. In addition, the term "circuitry" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0093] The terms "application circuitry" and/or "baseband circuitry" may be considered synonymous to, and may be referred to as, "processor circuitry." As used herein, the term "processor circuitry" may refer to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. The term "processor circuitry" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer- executable instructions, such as program code, software modules, and/or functional processes.

[0094] Furthermore, the various components of the core network 220 (may be referred to as "network elements." The term "network element" may describe a physical or virtualized equipment used to provide wired or wireless communication network services. The term "network element" may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, gateway, server, virtualized VNF, NFVI, and/or the like.

[0095] Application circuitry 305 may include one or more central processing unit (CPU) cores and one or more of cache memory, low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input/output (I/O or 10), memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC) or similar, Universal Serial Bus (USB) interfaces, Mobile Industry Processor Interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports.

[0096] Additionally or alternatively, application circuitry 305 may include circuitry such as, but not limited to, one or more a field-programmable devices (FPDs) such as field-programmable gate arrays (FPGAs) and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like.

[0097] User interface circuitry 350 may include one or more user interfaces designed to enable user interaction with the system 300 or peripheral component interfaces designed to enable peripheral component interaction with the system 300. Peripheral component interfaces may include, but are not limited to, a nonvolatile memory port, a universal serial bus (USB) port, an audio jack, a power supply interface, etc.

[0098] The radio front end modules (RFEMs) 315 may comprise a millimeter wave RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the millimeter wave RFEM. The RFICs may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module 315. The RFEMs 315 may incorporate both millimeter wave antennas and sub-millimeter wave antennas.

[0099] The memory circuitry 320 may include one or more of volatile memory including dynamic random access memory (DRAM) and/or synchronous dynamic random access memory (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc., and may incorporate the three- dimensional (3D) cross-point (XPOINT) memories from Intel ^® and Micron ^® .

[0100] The PMIC 325 may include voltage regulators, surge protectors, power alarm detection circuitry, and one or more backup power sources such as a battery or capacitor.

[0101] The network controller circuitry 335 may provide connectivity to a network using a standard network interface protocol such as Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), or some other suitable protocol. Network connectivity may be provided to/from the infrastructure equipment 300 via network interface connector 340 using a physical connection, which may be electrical (commonly referred to as a "copper interconnect"), optical, or wireless.

[0102] The positioning circuitry 345 may include circuitry to receive and decode signals transmitted by one or more navigation satellite constellations of a global navigation satellite system (GNSS).

[0103] The components shown by Fig. 3 may communicate with one another using interface circuitry. As used herein, the term "interface circuitry" may refer to, is part of, or includes circuitry providing for the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, for example, buses, input/output (I/O) interfaces, peripheral component interfaces, network interface cards, and/or the like.

[0104] For one or more embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of one or more of the preceding figures, or some other figure herein may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof.

[0105] The examples set forth herein are illustrative and not exhaustive.

[0106] Example 1 includes a device of a New Radio (NR) User Equipment (UE), the device including a Radio Frequency (RF) interface, and processing circuitry coupled to the RF interface, the processing circuitry to: decode a signal from a NR evolved node B (gNodeB) including an indication of one or more control resource sets (CORESETs); select a CORESET based on the indication; and determine a downlink radio link quality based on the CORESET.

[0107] Example 2 includes the subject matter of Example 1, and optionally, wherein the signal includes a reference signal (RS) in one or more radio link monitoring (RLM) reference signal

(RLM-RS) resources, wherein the one or more RLM-RS resources include at least one of all synchronization signal block (SSB) resources, all channel state information (CSI) reference signal (CSI-RS) resources, or a mixture of SSB and CSI-RS resources, and wherein the processing circuitry is to determine the downlink radio link quality based on the RS.

[0108] Example 3 includes the subject matter of Example 2, and optionally, wherein the processing circuitry is to determine the downlink radio link quality for each RLM-RS resource of the one or more RLM-RS resources by estimating the downlink radio link quality and comparing it to thresholds Q _out and Qm, wherein Q _ou t corresponds to an out-of-sync block error rate (BLER _0U t) and Qm corresponds to an in-sync block error rate (BLERm).

[0109] Example 4 includes the subject matter of Example 3, and optionally, wherein the processing circuitry is to determine BLER _0U t and BLERm based on a network configuration via a higher layer parameter, or based on a configuration number.

[0110] Example 5 includes the subject matter of Example 3, and optionally, wherein the one or more RLM-RS resources include synchronization signal block (SSB) resources, and the processing circuitry is to: determine whether the downlink radio link quality estimated over a last T _E vaiuate_out_ssB [ms] period becomes worse than a threshold Q _0U t_ssB within a T _Eva iuate_out_ssB [ms] evaluation period; and determine whether the downlink radio link quality estimated over a last T Evaiuatejn_ssB [ms] period becomes better than a threshold Q sse within a TEvaiuatejn_ssB [ms] evaluation period, wherein TEvaiuate_out_ssB and TEvaiuatejn_ssB are based on whether a carrier frequency range for the one or more RLM-RS resources corresponds to a NR FR1 carrier frequency range or a NR FR2 carrier frequency range.

[0111] Example 6 includes the subject matter of Example 3, and optionally, herein the one or more RLM-RS resources include CSI-RS resources, and the processing circuitry is to: determine whether the downlink radio link quality estimated over a last TEvaiuate_out_csi-Rs [ms] period becomes worse than a threshold within a TEvaiuate_out_csi-Rs [ms] evaluation period; and determine whether the downlink radio link quality estimated over a last TEvaiuatejn_csi-Rs [ms] period becomes better than a threshold Qin_csi-Rs within a TEvaiuatejn_csi-Rs [ms] evaluation period, wherein T _Eva iuate_out_csi-RA and T _Ev aiuatejn_csi-Rs are based on whether a carrier frequency range for the one or more RLM-RS resources corresponds to a NR FR1 carrier frequency range or a NR FR2 carrier frequency range.

[0112] Example 7 includes the subject matter of Example 3, and optionally, wherein an evaluation period for estimation of the downlink radio link quality is based on whether a carrier frequency range for the one or more RLM-RS resources corresponds to a NR FR1 carrier frequency range or a NR FR2 carrier frequency range.

[0113] Example 8 includes the subject matter of Example 7, and optionally, wherein the evaluation period is further based on whether a reception configuration includes a discontinuous reception mode (DRX mode).

[0114] Example 9 includes the subject matter of Example 8, and optionally, wherein the evaluation period is further based on at least one a sub-frame configuration cycle TCSI-RS, or a discontinuous reception cycle TDRX.

[0115] Example 10 includes the subject matter of Example 2, and optionally, wherein the processing circuitry is to cause the UE to monitor up to XRLM-RS RLM-RS resources in each corresponding carrier frequency range, wherein XRLM-RS is 2 for NR FR1 carrier frequency ranges less than or equal to 3 GHz, 4 for NR FR1 carrier frequency ranges above 3 GHz, and 8 for NR FR2 carrier frequency ranges.

[0116] Example 11 includes the subject matter of Example 1, and optionally, wherein the one or more CORESETs include a plurality of candidate CORESETs, and wherein the processing circuitry is to randomly choose the CORESET from the plurality of candidate CORESETs.

[0117] Example 12 includes the subject matter of Example 3, and optionally, wherein the processing circuitry is to determine a hypothetical physical downlink control channel (PDCCH) block error rate (BLER) based on the CORESET, and to trigger an out-of-sync (OOS) indication in response to a determination that the BLER is higher than a OOS threshold.

[0118] Example 13 includes the subject matter of Example 12, and optionally, wherein the processing circuitry is to determine respective hypothetical PDCCH BLERs for respective ones of a plurality of candidate CORESETs, and to trigger an out-of-sync (OOS) indication in response to a determination that all of the respective PDCCH BLERs are higher than a OOS threshold.

[0119] Example 14 includes the subject matter of Example 13, and optionally, wherein the processing circuitry has a Layer 1 circuitry, and wherein the Layer 1 circuitry to send the OOS indication to a Layer 3 circuitry of the UE for filtering.

[0120] Example 15 includes the subject matter of Example 14, and optionally, wherein the processing circuitry is to trigger an in-sync indication in response to a determination that the BLER is lower than a OOS threshold, and the Layer 1 circuitry to send the in-sync indication to the Layer 3 circuitry of the UE for filtering. [0121] Example 16 includes the Example of any one of Examples 1-15, further including a front end module.

[0122] Example 17 includes the subject matter of Example 16, and optionally, further including one or more antennas coupled to the front end module.

[0123] Example 18 includes a method to be performed at a device of a New Radio (NR) User Equipment (UE), the method including: decoding a signal from a NR evolved node B (gNodeB) including an indication of one or more control resource sets (CORESETs); selecting a CORESET based on the indication; and determining a downlink radio link quality based on the CORESET.

[0124] Example 19 includes the subject matter of Example 18, and optionally, wherein the signal includes a reference signal (RS) in one or more radio link monitoring (RLM) reference signal (RLM-RS) resources, wherein the one or more RLM-RS resources include at least one of all synchronization signal block (SSB) resources, all channel state information (CSI) reference signal (CSI-RS) resources, or a mixture of SSB and CSI-RS resources, and wherein the method further includes determining the downlink radio link quality based on the RS.

[0125] Example 20 includes the subject matter of Example 19, and optionally, wherein the method further includes determining the downlink radio link quality for each RLM-RS resource of the one or more RLM-RS resources by estimating the downlink radio link quality and comparing it to thresholds Q _ou t and Qm, wherein Q _ou t corresponds to an out-of-sync block error rate (BLER _0U t) and Qm corresponds to an in-sync block error rate (BLERm).

[0126] Example 21 includes the subject matter of Example 20, and optionally, wherein the method further includes determining BLER _0U t and BLERm based on a network configuration via a higher layer parameter, or based on a configuration number.

[0127] Example 22 includes the subject matter of Example 20, and optionally, wherein the one or more RLM-RS resources include synchronization signal block (SSB) resources, and the method further includes: determining whether the downlink radio link quality estimated over a last T _Eva iuate_out_ssB [ms] period becomes worse than a threshold Q _0U t_ssB within a T _Eva iuate_out_ssB [ms] evaluation period; and determining whether the downlink radio link quality estimated over a last T _Eva iuatejn_ssB [ms] period becomes better than a threshold Q sse within a T _E vaiuatejn_ssB [ms] evaluation period, wherein T _Eva iuate_out_ssB and T _Eva iuatejn_ssB are based on whether a carrier frequency range for the one or more RLM-RS resources corresponds to a NR FR1 carrier frequency range or a NR FR2 carrier frequency range. [0128] Example 23 includes the subject matter of Example 20, and optionally, wherein the one or more RLM-RS resources include CSI-RS resources, and the method further includes: determining whether the downlink radio link quality estimated over a last TEvaiuate_out_csi-Rs [ms] period becomes worse than a threshold Q _ou t_csi-Rs within a TEvaiuate_out_csi-Rs [ms] evaluation period; and determining whether the downlink radio link quality estimated over a last T Evaiuatejn_csi-Rs [ms] period becomes better than a threshold Q _in _csi-Rs within a T _Eva iuatejn_csi-Rs [ms] evaluation period, wherein T _Eva iuate_out_csi-RA and T _Eva iuatejn_csi-Rs are based on whether a carrier frequency range for the one or more RLM-RS resources corresponds to a NR FR1 carrier frequency range or a NR FR2 carrier frequency range.

[0129] Example 24 includes the subject matter of Example 20, and optionally, wherein an evaluation period for estimation of the downlink radio link quality is based on whether a carrier frequency range for the one or more RLM-RS resources corresponds to a NR FR1 carrier frequency range or a NR FR2 carrier frequency range.

[0130] Example 25 includes the subject matter of Example 24, and optionally, wherein the evaluation period is further based on whether a reception configuration includes a discontinuous reception mode (DRX mode).

[0131] Example 26 includes the subject matter of Example 25, and optionally, wherein the evaluation period is further based on at least one a sub-frame configuration cycle TCSI-RS, or a discontinuous reception cycle TDRX.

[0132] Example 27 includes the subject matter of Example 19, and optionally, wherein the method further includes causing the UE to monitor up to XRLM-RS RLM-RS resources in each corresponding carrier frequency range, wherein XRLM-RS is 2 for NR FR1 carrier frequency ranges less than or equal to 3 GHz, 4 for NR FR1 carrier frequency ranges above 3 GHz, and 8 for NR FR2 carrier frequency ranges.

[0133] Example 28 includes the subject matter of Example 18, and optionally, wherein the one or more CORESETs include a plurality of candidate CORESETs, and wherein the method further includes randomly choosing the control resource set (CORESET) from the plurality of candidate CORESETs.

[0134] Example 29 includes the subject matter of Example 20, and optionally, wherein the method further includes determining a hypothetical physical downlink control channel (PDCCH) block error rate (BLER) based on the CORESET, and triggering an out-of-sync (OOS) indication in response to a determination that the BLER is higher than a OOS threshold. [0135] Example 30 includes the subject matter of Example 29, and optionally, wherein the method further includes determining respective hypothetical PDCCH BLERs for respective ones of a plurality of candidate CORESETs, and triggering an out-of-sync (OOS) indication in response to a determination that all of the respective PDCCH BLERs are higher than a OOS threshold.

[0136] Example 31 includes the subject matter of Example 30, and optionally, wherein the method includes using a Layer 1 circuitry of the UE to send the OOS indication to a Layer 3 circuitry of the UE for filtering.

[0137] Example 32 includes the subject matter of Example 31, and optionally, wherein the method further includes triggering an in-sync indication in response to a determination that the BLER is lower than a OOS threshold, and using the Layer 1 circuitry to send the in-sync indication to the Layer 3 circuitry of the UE for filtering.

[0138] Example 33 includes a device of a New Radio (NR) User Equipment (UE), the device including: means for decoding a signal from a NR evolved node B (gNodeB) including an indication of one or more control resource sets (CORESETs); means for selecting a CORESET based on the indication; and means for determining a downlink radio link quality based on the CORESET.

[0139] Example 34 includes the subject matter of Example 33, and optionally, wherein the signal includes a reference signal (RS) in one or more radio link monitoring (RLM) reference signal (RLM-RS) resources, wherein the one or more RLM-RS resources include at least one of all synchronization signal block (SSB) resources, all channel state information (CSI) reference signal (CSI-RS) resources, or a mixture of SSB and CSI-RS resources, and wherein the device further includes means for determining the downlink radio link quality based on the RS.

[0140] Example 35 includes the subject matter of Example 34, and optionally, wherein the device further includes means for determining the downlink radio link quality for each RLM-RS resource of the one or more RLM-RS resources by estimating the downlink radio link quality and comparing it to thresholds Q _out and Qi _n , wherein Q _out corresponds to an out-of-sync block error rate (BLER _0U t) and Qm corresponds to an in-sync block error rate (BLE Rm).

[0141] Example 36 includes the subject matter of Example 35, and optionally, wherein the device further includes means for determining BLER _0U t and BLERin based on a network configuration via a higher layer parameter, or based on a configuration number.

[0142] Example 37 includes the subject matter of Example 35, and optionally, wherein the one or more RLM-RS resources include synchronization signal block (SSB) resources, and the device further includes: means for determining whether the downlink radio link quality estimated over a last T _Eva iuate_out_ssB [ms] period becomes worse than a threshold Q _0U t_ssB within a T _Eva iuate_out_ssB [ms] evaluation period; and means for determining whether the downlink radio link quality estimated over a last T _Eva iuatejn_ssB [ms] period becomes better than a threshold Qm_ssB within a T _E vaiuatejn_ssB [ms] evaluation period, wherein T _Eva iuate_out_ssB and T _Eva iuatejn_ssB are based on whether a carrier frequency range for the one or more RLM-RS resources corresponds to a NR FR1 carrier frequency range or a NR FR2 carrier frequency range.

[0143] Example 38 includes the subject matter of Example 35, and optionally, wherein the one or more RLM-RS resources include CSI-RS resources, and the device further includes: means for determining whether the downlink radio link quality estimated over a last T _Eva iuate_out_csi-Rs [ms] period becomes worse than a threshold Q _ou t_csi-Rs within a T _Eva iuate_out_csi-Rs [ms] evaluation period; and means for determining whether the downlink radio link quality estimated over a last T _Evaiuat ejn_csi-Rs [ms] period becomes better than a threshold Q _in _csi-Rs within a T _Evaiuat ejn_csi- RS [ms] evaluation period, wherein T _Evaiuate _out_csi-RA and T _Evaiuate jn_csi-Rs are based on whether a carrier frequency range for the one or more RLM-RS resources corresponds to a NR FR1 carrier frequency range or a NR FR2 carrier frequency range.

[0144] Example 39 includes the subject matter of Example 35, and optionally, wherein an evaluation period for estimation of the downlink radio link quality is based on whether a carrier frequency range for the one or more RLM-RS resources corresponds to a NR FR1 carrier frequency range or a NR FR2 carrier frequency range.

[0145] Example 40 includes the subject matter of Example 39, and optionally, wherein the evaluation period is further based on whether a reception configuration includes a discontinuous reception mode (DRX mode).

[0146] Example 41 includes the subject matter of Example 40, and optionally, wherein the evaluation period is further based on at least one a sub-frame configuration cycle TCSI-RS, or a discontinuous reception cycle TDRX.

[0147] Example 42 includes the subject matter of Example 34, and optionally, wherein the device further includes means for causing the UE to monitor up to XRLM-RS RLM-RS resources in each corresponding carrier frequency range, wherein XRLM-RS is 2 for NR FR1 carrier frequency ranges less than or equal to 3 GHz, 4 for NR FR1 carrier frequency ranges above 3 GHz, and 8 for NR FR2 carrier frequency ranges. [0148] Example 43 includes the subject matter of Example 33, and optionally, wherein the one or more CORESETs include a plurality of candidate CORESETs, and wherein the device further includes means for randomly choosing a control resource set (CORESET) from the plurality of candidate CORESETs.

[0149] Example 44 includes the subject matter of Example 35, and optionally, wherein the device further includes means for determining a hypothetical physical downlink control channel (PDCCH) block error rate (BLER) based on the CORESET, and means for triggering an out-of-sync (OOS) indication in response to a determination that the BLER is higher than a OOS threshold.

[0150] Example 45 includes the subject matter of Example 34, and optionally, wherein the device further includes means for determining respective hypothetical PDCCH BLERs for respective ones of a plurality of candidate CORESETs, and means for triggering an out-of-sync (OOS) indication in response to a determination that all of the respective PDCCH BLERs are higher than a OOS threshold.

[0151] Example 46 includes the subject matter of Example 45, and optionally, wherein the device includes means for sending the OOS indication to a Layer 3 circuitry of the UE for filtering.

[0152] Example 47 includes the subject matter of Example 46, and optionally, wherein the device further includes means for triggering an in-sync indication in response to a determination that the BLER is lower than a OOS threshold, and means for sending the in-sync indication to the Layer 3 circuitry of the UE for filtering.

[0153] Example 48 includes a device of a New Radio (NR) gNodeB, the device including a Radio Frequency (RF) interface, and processing circuitry coupled to the RF interface, the processing circuitry to: encode a signal to a User Equipment (U E) including an indication of one or more control resource sets (CORESETs) to allow the UE to select a CORESET based on the one or more CORESETs; and process the signal for transmission to the UE by way of the RF interface.

[0154] Example 49 includes the subject matter of Example 48, and optionally, wherein the signal includes a reference signal (RS) in one or more radio link monitoring (RLM) reference signal (RLM-RS) resources, wherein the one or more RLM-RS resources include at least one of all synchronization signal block (SSB) resources, all channel state information (CSI) reference signal (CSI-RS) resources, or a mixture of SSB and CSI-RS resources. [0155] Example 50 includes the subject matter of Example 48, and optionally, the processing circuitry further to decode at least one of an out-of-sync (OOS) indication from the UE or an in sync indication from the UE.

[0156] Example 51 includes the subject matter of any one of Examples 48-50, further including a front end module.

[0157] Example 52 includes the subject matter of Example 16, and optionally, further including one or more antennas coupled to the front end module.

[0158] Example 53 includes a method to be performed at a New Radio (N R) evolved Node B (gNodeB) the method including: encoding a signal to a User Equipment (UE) including an indication of one or more control resource sets (CORESETs) to allow the UE to select a CORESET based on the one or more CORESETs; and processing the signal for transmission to the UE.

[0159] Example 54 includes the subject matter of Example 53, and optionally, wherein the signal includes a reference signal (RS) in one or more radio link monitoring (RLM) reference signal (RLM-RS) resources, wherein the one or more RLM-RS resources include at least one of all synchronization signal block (SSB) resources, all channel state information (CSI) reference signal (CSI-RS) resources, or a mixture of SSB and CSI-RS resources.

[0160] Example 55 includes the subject matter of Example 53, and optionally, further including decoding at least one of an out-of-sync (OOS) indication from the UE or an in-sync indication from the U E.

[0161] Example 56 includes a machine-readable medium including code which, when executed, is to cause a machine to perform the method of any one of Examples 18-32 and 53- 55.

[0162] Example 57 includes a device including means to perform the method of any one of Examples 18-32 and 53-55.

[0163] Example 58 may include a signal as described in or related to any of the Examples above, or portions or parts thereof.

[0164] Example 59 may include a signal in a wireless network as shown and described herein.

[0165] Example 60 may include a method according to any of any one of the Examples 18-32 and 53-55 above, wherein the method or any portion thereof is implemented in or by a UE or a gNodeB.

[0166] Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.