Patent Description:
Various embodiments generally may relate to the field of wireless communications, and particularly to Control Resource Set (CORESET) selection.

In the third generation partnership project (3GPP) (NR) 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.

"<NPL>, is directed to link adaptation on downlink control channels. A communication component sends first data indicating a first downlink control channel to a mobile device. Said first data can comprise a first COREST indication for decoding the first downlink control channel. A network device can determine a second CORESET indication for the mobile device whereby the second CORESET indication can comprise a second parameter that can be determined based on a condition of an environment associated with the mobile device.

The present invention is defined by the attached independent claims. Other preferred embodiments may be found in the dependent claims.

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).

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 (NR) specifications and one or more specifications directed and/or related to RAN1 and/or fifth generation (<NUM>) mobile networks/systems.

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.

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

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.

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.

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

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.

In a third embodiments, the UE checks all the CORESETs, and the OOS indication is triggered only if all the BLERs from all CORESETs are higher than the OOS threshold.

Section <NUM> of TS <NUM> V15. <NUM> (Section <NUM>), "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.

According to Section <NUM>, 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 UE 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 BWPs other than the active DL BWP.

According to Section <NUM>, 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-Index), or a synchronization signal (SS) physical broadcast channel (PBCH) (SS/PBCH) block index (by higher layer parameter ssb-Index). The UE can be configured with up to a number NLR-RLM RadioLinkMonitoringRS for link recovery (LR) procedures, as discussed below, and radio link monitoring. From the NLR-RLM RadioLinkMonitoringRS, up to a number NRLM 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.

According to Section <NUM>, if the UE is not provided higher layer parameter RadioLinkMonitoringRS and the UE is provided by higher layer parameter TCI-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:.

According to Section <NUM>, the UE is not expected to use more than NRLM RadioLinkMonitoringRS for radio link monitoring when the UE is not provided higher layer parameter RadioLinkMonitoringRS.

Values of NLR-RLM and NRLM for different values of L are given in Table <NUM>-<NUM> of TS <NUM> V15.

According to Section <NUM>, for a CSI-RS resource configuration, the higher layer parameter powerControlOffsetSSis not applicable and a UE expects to be provided only 'No CDM' from higher layer parameter cdm-Type, only '<NUM>' and '<NUM>' from higher layer parameter density, and only '<NUM> port' from higher layer parameter nrofPorts, with CDM referring to code division multiplexing.

According to Section <NUM>, 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 (Qout and Qin) 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 <NUM> msec.

According to Section <NUM>, 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 (Qout and Qin) provided by higher layer parameter rlmInSyncOutOfSyncThreshold. The UE determines the indication period as the maximum between the shortest periodicity for radio link monitoring resources and the DRX period.

According to Section <NUM>, 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 Qout for all resources in the set of resources for radio link monitoring. When the radio link quality is better than the threshold Qin 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.

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.

Referring to <FIG>, a process <NUM> is shown for a method embodiment as described above. Operation <NUM> includes decoding a signal from a NR evolved node B (gNodeB) including an indication of one or more control resource sets (CORESETs). Operation <NUM> includes selecting a CORESET based on the indication. Operation <NUM> includes determining a downlink radio link quality based on the CORESET.

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 UE 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.

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 Qout and Qin for the purpose of monitoring downlink radio link quality of the cell. The threshold Qout 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 (BLERout) as defined in Table RLM. <NUM>-<NUM> below. For SSB based radio link monitoring, Qout_SSB is derived based on the hypothetical PDCCH transmission parameters listed in Table RLM. <NUM>-<NUM> below. For CSI-RS based radio link monitoring, Qout_CSI-RS is derived based on the hypothetical PDCCH transmission parameters listed in Table RLM. <NUM>-<NUM> below.

The threshold Qin is defined as the level at which the downlink radio link quality can be significantly more reliably received than at Qout and is to correspond to the in-sync block error rate (BLERin) as defined in Table RLM. <NUM>-<NUM>. For SSB based radio link monitoring, Qin_SSB is derived based on the hypothetical PDCCH transmission parameters listed in Table RLM. <NUM>-<NUM>. For CSI-RS based radio link monitoring, Qin_CSI-RS is derived based on the hypothetical PDCCH transmission parameters listed in Table RLM. <NUM>-<NUM>.

According to an embodiment, the out-of-sync block error rate (BLERout) and in-sync block error rate (BLERin) 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. <NUM>-<NUM> below. When the UE is not configured with RLM-IS-OOS-thresholdConfig from the network, the UE determines out-of-sync and in-sync block error rates from Configuration #<NUM> in Table RLM. <NUM>-<NUM> as a default.

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. <NUM>-<NUM>, and meets the requirements as specified below.

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. <NUM>-<NUM> and RLM. <NUM>-<NUM>.

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 TEvaluate_out_SSB [ms] period becomes worse than the threshold Qout_SSB within TEvaluate_out_SSB [ms] evaluation period.

UE is to be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last TEvaluate_in_SSB [ms] period becomes better than the threshold Qin_SSB within TEvaluate_in_SSB [ms] evaluation period.

TEvaluate_out_SSB and TEvaluate_in_SSB are defined in Table RLM. <NUM>-<NUM> herein for FR1 (corresponding to a frequency range from <NUM> - <NUM>).

TEvaluate_out_SSB and TEvaluate_in_SSB are defined in Table RLM. <NUM>-<NUM> herein for FR2 with.

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.

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.

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 TEvaluate_out_CSI-RS [ms] period becomes worse than the threshold Qout_CSI-RS within TEvaluate_out_CSI-RS [ms] evaluation period.

UE is to be able to evaluate whether the downlink radio link quality on the configured RLM-RS resource estimated over the last TEvaluate_in_CSI-RS [ms] period becomes better than the threshold Qin_CSI-RS within TEvaluate_in_CSI-RS [ms] evaluation period.

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.

The values of Mout and Min used in Table RLM. <NUM>-<NUM> and Table RLM. <NUM>-<NUM> are defined as:.

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.

According to an embodiment, when the downlink radio link quality on all the configured RLM-RS resources is worse than Qout, Layer <NUM> of the UE is to send an out-of-sync indication for the cell to the higher layers. A Layer <NUM> filter is to be applied to the out-of-sync indications.

According to an embodiment, when the downlink radio link quality on at least one of the configured RLM-RS resources is better than Qin, Layer <NUM> of the UE is to send an in-sync indication for the cell to the higher layers. A Layer <NUM> filter is to be applied to the in-sync indications.

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 <NUM> is to be separated by at least TIndication_interval.

According to an embodiment, when DRX is not used TIndication_interval is max(<NUM>, 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.

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 <NUM> indication interval corresponding to the non-DRX mode until the expiry or stop of T310 timer.

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.

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

According to an embodiment, for a UE which support simultaneousRxDataSSB-DiffNumerology [<NUM>] 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 [<NUM>] 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.

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

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_CONNECTED mode UE.

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

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

According to Section <NUM>, A UE can be provided, for a serving cell, with a set q<NUM> of periodic CSI-RS resource configuration indexes by higher layer parameter failureDetectionResources and with a set q<NUM> 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 parameter failureDetectionResources, the UE determines the set q<NUM> 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<NUM> to include up to two RS indexes and, if there are two RS indexes, the set q<NUM> includes only RS indexes with QCL-TypeD configuration for the corresponding TCI states. The UE expects single port RS in the set q<NUM>.

According to Section <NUM>, the threshold Qout,LR corresponds to the default value of higher layer parameter rlmlnSyncOutOfSyncThreshold and to the value provided by higher layer parameter rsrp-ThresholdSSB, respectively.

According to Section <NUM>, the physical layer in the UE assesses the radio link quality according to the set q<NUM> of resource configurations against the threshold Qout,LR. For the set q<NUM>, 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 Qin,LR threshold to the L1-RSRP measurement obtained from a SS/PBCH block. The UE applies the Qin,LR threshold to the L1-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.

According to Section <NUM>, 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 q<NUM> that the UE uses to assess the radio link quality is worse than the threshold Qout,LR. The physical layer informs the higher layers when the radio link quality is worse than the threshold Qout,LR with a periodicity determined by the maximum between the shortest periodicity of periodic CSI-RS configurations or SS/PBCH blocks in the set q<NUM> that the UE uses to assess the radio link quality and <NUM> msec.

According to Section <NUM>, 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<NUM> and the corresponding L1-RSRP measurements that are larger than or equal to the corresponding thresholds.

According to Section <NUM>, 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 <NUM>, for monitoring PDCCH in the control resource set. If the UE is provided higher layer parameter 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.

According to Section <NUM>, the UE may receive by higher layer parameter PRACH-ResourceDedicatedBFR, a configuration for PRACH transmission as described in Subclause <NUM>. 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 qnew 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 n+<NUM> 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 qnew until the UE receives by higher layers an activation for a TCI state or any of the parameters TCI-StatesPDCCH-ToAddlist and/or TCI-StatesPDCCH-ToReleaseList. After the UE detects a DCI format with CRC scrambled by C-RNTI in the search space provided by recoverySearchSpaceId, the UE monitors PDCCH candidates in the search space provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for a TCI state or higher layer parameters TCI-StatesPDCCH-ToAddlist and/or TCI-StatesPDCCH-ToReleaseList.

According to Section <NUM>, if the UE is not provided a control resource set for a search space set provided recoverySearchSpaceId or if the UE is not provided recoverySearchSpaceId, the UE does not expect to receive a PDCCH order triggering a PRACH transmission.

<FIG> illustrates an architecture of a system <NUM> of a network in accordance with some embodiments. The system <NUM> is shown to include a user equipment (UE) <NUM> and a UE <NUM>. The UEs <NUM> and <NUM> 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 <NUM> and <NUM> may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) <NUM>. The UEs <NUM> and <NUM> utilize connections <NUM> and <NUM>, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections <NUM> and <NUM> are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols.

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 <NUM> is shown to be communicatively coupled to a core network (CN) <NUM> -via an S1 interface <NUM>. In embodiments, the CN <NUM> may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the S1 interface <NUM> is split into two parts: the S1-U interface <NUM>, which carries traffic data between the RAN nodes <NUM> and <NUM> and the serving gateway (S-GW) <NUM>, and the S1-mobility management entity (MME) interface <NUM>, which is a signaling interface between the RAN nodes <NUM> and <NUM> and MMEs <NUM>. The CN <NUM> 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.

In this embodiment, the CN <NUM> comprises, as network elements, the MMEs <NUM>, the S-GW <NUM>, the Packet Data Network (PDN) Gateway (P-GW) <NUM>, and a home subscriber server (HSS) <NUM>.

<FIG> illustrates an example of infrastructure equipment <NUM> in accordance with various embodiments. The infrastructure equipment <NUM> (or "system <NUM>") may be implemented as a base station, radio head, RAN node, etc., such as the RAN nodes <NUM> and/or AP <NUM> shown and described previously. In other examples, the system <NUM> could be implemented in or by a UE, application server(s) <NUM>, and/or any other element/device discussed herein. The system <NUM> may include one or more of application circuitry <NUM>, baseband circuitry <NUM>, one or more radio front end modules <NUM>, memory circuitry <NUM>, power management integrated circuitry (PMIC) <NUM>, power tee circuitry <NUM>, network controller circuitry <NUM>, network interface connector <NUM>, satellite positioning circuitry <NUM>, and user interface <NUM>. In some embodiments, the device <NUM> 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).

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 (HCPLD), 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.

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.

Furthermore, the various components of the core network <NUM> (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.

Application circuitry <NUM> 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 IO), 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.

Additionally or alternatively, application circuitry <NUM> 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.

User interface circuitry <NUM> may include one or more user interfaces designed to enable user interaction with the system <NUM> or peripheral component interfaces designed to enable peripheral component interaction with the system <NUM>. 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..

The radio front end modules (RFEMs) <NUM> 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 <NUM>. The RFEMs <NUM> may incorporate both millimeter wave antennas and sub-millimeter wave antennas.

The memory circuitry <NUM> 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®.

The PMIC <NUM> may include voltage regulators, surge protectors, power alarm detection circuitry, and one or more backup power sources such as a battery or capacitor.

The network controller circuitry <NUM> 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 <NUM> via network interface connector <NUM> using a physical connection, which may be electrical (commonly referred to as a "copper interconnect"), optical, or wireless.

The positioning circuitry <NUM> may include circuitry to receive and decode signals transmitted by one or more navigation satellite constellations of a global navigation satellite system (GNSS).

The components shown by <FIG> 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.

Claim 1:
A device of a User Equipment, UE, (<NUM>, <NUM>), the device including a processor configured to:
decode (<NUM>) a first signal from a base station configuring a plurality of control resource sets, CORESETs;
receive an indication of one of the configured plurality of CORESETs to be used for radio link monitoring, RLM;
select (<NUM>) a CORESET based on the indication; and
determine (<NUM>) a downlink radio link quality based on the CORESET.