[0002] Various embodiments generally may relate to the field of wireless communications, and particularly to uplink timing adjustment with beam switching. BACKGROUND

[0003] Current Third Generation Partnership Project (3GPP) New Radio (NR) specifications do not specifically address issues related to the definition of downlink (DL) and uplink (UL) timing when a user equipment (UE) operates with multiple beams, and issues related to the requirements for UL timing adjustment when beam switching occurs. 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;

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

[0007] Fig.4 illustrates example interfaces of baseband circuitry according to various embodiments. DETAILED DESCRIPTION

[0008] 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).

[0009] Current 3GPP NR specifications do not specifically address issues related to the definition of DL and UL timing when a UE operates with multiple beams, and issues related to the requirements for UL timing adjustment when beam switching occurs. Embodiments herein provide the related definitions of DL/UL timing when there are multiple beams and the requirements for UL timing adjustment when beam switching occurs at UE.

[0010] Embodiment 1

[0011] In a first embodiment, when a UE operates with multiple beams, the DL and UL timing is derived with a certain pair of Tx-Rx beams.

[0012] Referring to Fig.1, a process 100 according to one embodiment includes at operation 102, encode for communication with a NR evolved Node B (gNodeB) signals on multiple beams, and at operation 104, determine a timing for an uplink (UL) communication with the gNodeB based on a pair of transmit and receive beams respectively to and from the gNodeB.

[0013] Timing advance is a random access channel response (RAR or RACH Response) or Medium Access Control (MAC) Control Element (CE) that is used to control uplink signal transmission timing. The gNodeB can keep measuring the time difference between PUSCH/PUCCH/SRS reception and the subframe time and can send a 'timing advance' or TA command to the UE to change the PUSCH/PUCCH transmission to make it better aligned with the subframe timing at the network side. If PUSCH/PUCCH/SRS arrives at the network too early, the network can send a timing advance command to UE to indicate the UE should transmit a bit later, and if PUSCH/PUCCH/SRS arrives at the network too late, the network can send a timing advance command to the UE saying transmit your signal a bit earlier. [0014] MAC PDU for Timing Advance is as follows. It is one byte data and the first two bits are reserved and set to be always 0. The remaining 6 bits carries Timing Advance command value ranging from 0 to 63.

[0015] According to the 3GPP Technical Specification (TS) 38.133 V.15.0.0 (hereinafter TS 38.133), the UE transmit timing is as follows: the UE is to have the capability to follow the frame timing change of the connected New Radio (NR) evolved Node B (gNodeB). The uplink frame transmission takes place (N _TA +N _{TA offset} ) × T _c before the reception of the first detected path (in time) of the corresponding downlink frame from the reference cell. The reference cell is PSCell in case of Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (EN-DC). The UE’s initial transmit timing accuracy, maximum amount of timing change in one adjustment, minimum and maximum adjustment rate are defined as part of the UE transmit timing requirements follows below.

[0016] The UE’s initial transmission timing error is to be less than or equal to ±Te, where the timing error limit value T _e is specified in Table 1 below, which corresponds to Table 7.1.2 of TS 38.133. This requirement applies when it is the first transmission in a discontinuous reception (DRX) cycle for physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH) and sounding reference signal (SRS) or it is the PRACH transmission.

[0017] The UE is to meet the Te requirement for an initial transmission provided that at least one synchronization signal block (SSB) is available at the UE during the last 160 ms. The reference point for the UE initial transmit timing control requirement is to be the downlink timing of the reference cell minus (N _TA +N _{TA offset} ) × T _c . The downlink timing is defined as the time when the first detected path (in time) of the corresponding downlink frame is received from the reference cell. NTA for Physical Random Access Channel (PRACH) is defined as 0.

[0018] It is to be noted that ^(N _TA ^{+ N} _{TA offset} ^{) × T} _c (in Tc units) for other channels is the difference between UE transmission timing and the downlink timing immediately after when the last timing advance (discussed below) was applied. N _TA for other channels is not changed until the next timing advance is received. The value of N _{TA offset} depends on the duplex mode of the cell in which the uplink transmission takes place and the frequency range (FR). N _{TA offset} is defined in Table 2 below. Table 1: T _e Timing Error Limit

Table 2: The Value of N _{TA offset} [0019] According to some embodiments, when it is not the first transmission in a DRX cycle or there is no DRX cycle, and when it is the transmission for PUCCH, PUSCH and SRS transmission, the UE is capable of changing the transmission timing according to the received downlink frame of the reference cell except when the timing advance is applied.

[0020] When the transmission timing error between the UE and the reference timing exceeds ±Te, the UE is required to adjust its timing to within ±Te. The reference timing is ^(N _TA ^{+ N} _{TA offset} ^{) × T} _c before the downlink timing of the reference cell. All adjustments made to the UE uplink timing follow these rules: 1) The maximum amount of the magnitude of the timing change in one adjustment shall be Tq.

2) The minimum aggregate adjustment rate shall be Tp per second.

3) The maximum aggregate adjustment rate shall be T _q per [200]ms.

[0021] According to some embodiments, the maximum autonomous time adjustment step Tq and the aggregate adjustment rate Tp may be specified by Table 3.

Table 3: Tq Maximum Autonomous Time Adjustment Step and Tp Minimum Aggregate

Adjustment rate

[0022] According to various embodiments, when the UE operates with multiple beams, the downlink (DL) reference timing and uplink (UL) timing are based on a certain pair of transmit and receive (Tx-Rx) beams. For example, the base station, such as the gNodeB, may select the best Tx beam based on some criteria, and the UE chooses the corresponding Rx beam and the DL timing is derived based on this“best” Tx-Rx beam pair. When the beam switching occurs, the UE re-detects the DL reference timing.

[0023] Embodiment 2

[0024] According to a second embodiment, when a beam switch occurs, the UE needs to detect the DL timing after beam switching. In the second embodiment, when the UE detects that the DL reference timing has changed within ±D (D = ½ CP length), the UE can adjust its uplink timing up to ±D. Additionally or alternatively, when the UE detects that the DL reference timing has changed more than ±D (D = ½ CP length), the UE is allowed to initiate a random access procedure to re-obtain the DL timing. The value of threshold D is defined in table 4.

Table 4: D values for different SCS

[0025] Once a beam switch happens, the UE needs to estimate the difference between the old and the new beam and apply the difference to the UL timing. As part of beam management, the UE would have already measured the beam to which it is switching. Thus, at the time the UE decides to switch its beam it is aware of the timing delta (difference) between the old and the new beam and should be able to correct the UL timing. It is possible that the timing delta between the two beams is large, which if not corrected may cause the base station to lose timing or at the very least cause significant degradation in performance. Thus, it would be beneficial to allow for larger change in UL timing upon a beam switch than what autonomous adjustment allows. In the second embodiment, a larger change in timing for beam switch is allowed so that base station does not lose the timing, and autonomous adjustments are used to bring it within an error tolerance. As a result, on beam switch, when the UE detects that the DL timing has changed within ± ½ CP length, the UE can adjust its uplink timing up to by the changed value on reference DL timing; when UE detects that DL reference timing has changed more than ± ½ CP length, UE is allowed to initiate a random access procedure to re-obtain the DL timing.

[0026] Timing Advance

[0027] The timing advance (TA) is initiated from a gNodeB with MAC message that implies or otherwise indicates an adjustment of the TA. In some cases, this may include a TA adjustment delay. In these cases, the UE adjusts the timing of its uplink transmission timing at time slot n+[6] for a TA command received in time slot n. The same requirement applies also when the UE is not able to transmit a configured uplink transmission due to the channel assessment procedure.

[0028] With respect to TA adjustment accuracy, the UE is to adjust the timing of its transmissions with a relative accuracy better than or equal to the UE TA adjustment accuracy requirement in Table 5 below, corresponding to Table 7.3.2.2-1 of TS 38.133, to the signaled timing advance value compared to the timing of preceding uplink transmission. Table 5: UE Timing Advance adjustment accuracy

[0029] Beam Management

[0030] Beam management refers to a set of layer 1/layer 2 (L1/L2) procedures to acquire and maintain a set of transmission/reception point(s) (TRP or TRxP) and/or UE beams that can be used for DL and UL transmission/reception. Beam management includes various operations or procedures, such as beam determination, beam management, beam reporting, and beam sweeping operations/procedures. Beam determination refers to TRxP(s) or the UE’s ability to select Tx/Rx beam(s) on its own. Beam measurement refers to TRP or the UE’s ability to measure characteristics of received beamformed signals. Beam reporting refers the UE’s ability to report information of beamformed signal(s) based on beam measurement. Beam sweeping refers to operation(s) of covering a spatial area, with beams transmitted and/or received during a time interval in a predetermined manner.

[0031] Tx/Rx beam correspondence at a TRxP holds if at least one of the following conditions are satisfied: TRxP is able to determine a TRxP Rx beam for the uplink reception based on the UE’s downlink measurement on TRxP’s one or more Tx beams; and TRxP is able to determine a TRxP Tx beam for the downlink transmission based on TRxP’s uplink measurement on TRxP’s one or more Rx beams. Tx/Rx beam correspondence at a UE holds if at least one of the following is satisfied: UE is able to determine a UE Tx beam for the uplink transmission based on UE’s downlink measurement on UE’s one or more Rx beams; UE is able to determine a UE Rx beam for the downlink reception based on TRxP’s indication based on uplink measurement on UE’s one or more Tx beams; and capability indication of UE beam correspondence related information to TRxP is supported.

[0032] According to some embodiments, DL beam management may include procedures P-1, P-2, and P-3. Procedure P-1 is used to enable a UE measurement on different TRxP Tx beams to support selection of TRxP Tx beams/UE Rx beam(s). For beamforming at TRxP, procedure P- 1 typically includes a intra/inter-TRxP Tx beam sweep from a set of different beams. For beamforming at the UE, procedure P-1 typically includes a UE Rx beam sweep from a set of different beams. [0033] Procedure P-2 is used to enable UE measurement on different TRxP Tx beams to possibly change inter/intra-TRxP Tx beam(s). Procedure P-2 may be a special case of procedure P-1 wherein procedure P-2 is used for a possibly smaller set of beams for beam refinement than procedure P-1.

[0034] Procedure P-3 is used to enable UE measurement on the same TRxP Tx beam to change UE Rx beam in the case UE uses beamforming. Procedures P-1, P-2, and P-3 may be used for aperiodic beam reporting.

[0035] UE measurements based on reference signal (RS) for beam management (at least channel state information reference signal (CSI-RS)) includes measurements on beams composed of K beams (where K is a total number of configured beams), and the UE reports measurement results of N selected Tx beams (where N may or may not be a fixed number). The procedure based on RS for mobility purposes is not precluded above. Beam information that is to be reported includes measurement quantities for the N beam(s) and information indicating N DL Tx beam(s), if N < K. Other information or data may be included in or with the beam information. When a UE is configured with K’ >1 non-zero power (NZP) CSI-RS resources, a UE can report N’ CSI-RS Resource Indicators (CRIs).

[0036] The UE can trigger a mechanism to recover from beam failure, which is referred to a “beam recovery”,“beam failure recovery request procedure”, and/or the like. A beam failure event may occur when the quality of beam pair link(s) of an associated control channel falls below a threshold, when a time-out of an associated timer occurs, or the like. The beam recovery mechanism is triggered when beam failure occurs. The network may explicitly configure the UE with resources for UL transmission of signals for recovery purposes. Configurations of resources are supported where the base station (e.g., a TRP, gNodeB, or the like) is listening from all or partial directions (e.g., a random access region). The UL transmission/resources to report beam failure can be located in the same time instance as a Physical Random Access Channel (PRACH) or resources orthogonal to PRACH resources, or at a time instance (configurable for a UE) different from PRACH. Transmission of DL signal is supported for allowing the UE to monitor the beams for identifying new potential beams.

[0037] For beam failure recovery, a beam failure may be declared if one, multiple, or all serving PDCCH beams fail. The beam failure recovery request procedure is initiated when a beam failure is declared. For example, the beam failure recovery request procedure may be used for indicating to a serving gNodeB (or TRP) of a new SSB or CSI-RS when beam failure is detected on a serving SSB(s)/CSI-RS(s). A beam failure may be detected by the lower layers and indicated to a Media Access Control (MAC) entity of the UE.

[0038] Beam management also includes providing or not providing beam-related indications. When beam-related indication is provided, information pertaining to UE-side beamforming/receiving procedure used for CSI-RS-based measurement can be indicated through quasi co-location (QCL) to the UE. The same or different beams on the control channel and the corresponding data channel transmissions may be supported.

[0039] DL beam indications are based on Transmission Configuration Indication (TCI) state(s). The TCI state(s) are indicated in a TCI list that is configured by radio resource control (RRC) and/or Media Access Control (MAC) Control Element (CE).

[0040] Antenna Port Quasi Co-Location

[0041] The UE can be configured with a list of up to M TCI-State configurations within the higher layer parameter PDSCH-Config to decode PDSCH according to a detected PDCCH with downlink control channel (DCI) intended for the UE and the given serving cell, where M depends on the UE capability. Each TCI-State contains parameters for configuring a quasi co- location relationship between one or two downlink reference signals and the demodulation reference signal (DM-RS) ports of the PDSCH. The quasi co-location relationship is configured by the higher layer parameter qcl-Type1 for the first DL RS, and qcl-Type2 for the second DL RS (if configured). For the case of two DL RSs, the QCL types may not be the same, regardless of whether the references are to the same DL RS or different DL RSs. The quasi co-location types corresponding to each DL RS is given by the higher layer parameter qcl-Type in QCL-Info and may take one of the following values: QCL-TypeA: {Doppler shift, Doppler spread, average delay, delay spread}; QCL-TypeB: {Doppler shift, Doppler spread}; QCL-TypeC: {average delay, Doppler shift}; QCL-TypeD: {Spatial Rx parameter}.

[0042] The UE may receive an activation command used to map up to 8 TCI states to the codepoints of the DCI field 'Transmission Configuration Indication'. When the HARQ-ACK corresponding to the PDSCH carrying the activation command is transmitted in slot n, the indicated mapping between TCI states and codepoints of the DCI field 'Transmission Configuration Indication' should be applied starting from slot ^ + 3^ ^{^^^^^^^^,µ}

^ _^^^ +1. After the UE receives the higher layer configuration of TCI states and before reception of the activation command, the UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co- located with the SS/PBCH block determined in the initial access procedure with respect to 'QCL- TypeA', and when applicable, also with respect to 'QCL-TypeD'.

[0043] If a UE is configured with the higher layer parameter tci-PresentInDCI that is set as 'enabled' for the control resource set CORESET scheduling the PDSCH, the UE assumes that the TCI field is present in the DCI format 1_1 of the PDCCH transmitted on the CORESET. If tci- PresentInDCI is not configured for the CORESET scheduling the PDSCH or the PDSCH is scheduled by a DCI format 1_0, for determining PDSCH antenna port quasi co-location, the UE assumes that the TCI state for the PDSCH is identical to the TCI state applied for the CORESET used for the PDCCH transmission.

[0044] If the tci-PresentInDCI is set as 'enabled', when the PDSCH is scheduled by DCI format 1_1, the UE shall use the TCI-State according to the value of the 'Transmission Configuration Indication' field in the detected PDCCH with DCI for determining PDSCH antenna port quasi co- location. The UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co- located with the RS(s) in the TCI state with respect to the QCL type parameter(s) given by the indicated TCI state if the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than a threshold Threshold-Sched-Offset, where the threshold is based on reported UE capability.

[0045] For both the cases when tci-PresentInDCI is set to 'enabled' and tci-PresentInDCI is not configured, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold Threshold-Sched-Offset, the UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the RS(s) in the TCI state with respect to the QCL parameter(s) used for PDCCH quasi co-location indication of the lowest CORESET-ID in the latest slot in which one or more CORESETs within the active BWP of the serving cell are configured for the UE. If none of configured TCI states contains 'QCL-TypeD', the UE shall obtain the other QCL assumptions from the indicated TCI states for its scheduled PDSCH irrespective of the time offset between the reception of the DL DCI and the corresponding PDSCH.

[0046] For a periodic CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info, the UE shall expect that a TCI-State indicates one of the following quasi- colocation type(s):

- 'QCL-TypeC' with an SS/PBCH block and, when applicable, 'QCL-TypeD' with the same SS/PBCH block, or - 'QCL-TypeC' with an SS/PBCH block and, when applicable, 'QCL-TypeD' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with higher layer parameter repetition, or

[0047] For an aperiodic CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info, the UE shall expect that a TCI-State indicates 'QCL-TypeA' with a periodic CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, when applicable,'QCL-TypeD' with the same periodic CSI-RS resource.

[0048] For a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured without higher layer parameter trs-Info and without the higher layer parameter repetition, the UE shall expect that a TCI-State indicates one of the following quasi co-location type(s):

- 'QCL-TypeA' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, when applicable, 'QCL-TypeD' with an SS/PBCH block , or - 'QCL-TypeA' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, when applicable, 'QCL-TypeD' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter repetition, or

- 'QCL-TypeB' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info when 'QCL-TypeD' is not applicable.

[0049] For a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter repetition, the UE shall expect that a TCI-State indicates one of the following quasi co-location type(s):

- 'QCL-TypeA' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, when applicable, 'QCL-TypeD' with the same CSI-RS resource, or

- 'QCL-TypeA' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, when applicable, 'QCL-TypeD' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter repetition, or

- 'QCL-TypeC' with an SS/PBCH block and, when applicable, 'QCL-TypeD' with the same SS/PBCH block.

[0050] For the DM-RS of PDCCH, the UE shall expect that a TCI-State indicates one of the following quasi co-location type(s): - 'QCL-TypeA' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, when applicable, 'QCL-TypeD' with the same CSI-RS resource, or

- 'QCL-TypeA' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, when applicable, 'QCL-TypeD' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with higher layer parameter repetition, or

- 'QCL-TypeA' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured without higher layer parameter trs-Info and without higher layer parameter repetition, when 'QCL-TypeD' is not applicable.

[0051] For the DM-RS of PDSCH, the UE shall expect that a TCI-State indicates one of the following quasi co-location type(s):

- 'QCL-TypeA' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, when applicable, 'QCL-TypeD' with the same CSI-RS resource, or

- 'QCL-TypeA' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, when applicable, 'QCL-TypeD' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured with higher layer parameter repetition,or

- QCL-TypeA' with CSI-RS resource in a NZP-CSI-RS-ResourceSet configured without higher layer parameter trs-Info and without repetition and, when applicable, 'QCL- TypeD' with the same CSI-RS resource.

[0052] Beam Failure Recovery Request

[0053] A beam failure recovery request could be delivered over dedicated PRACH or PUCCH resources. For example, a UE can be configured, for a serving cell, with a set ^{q 0} of periodic CSI- RS resource configuration indexes by higher layer parameter Beam-Failure-Detection-RS- ResourceConfig and with a set ^{q 1} of CSI-RS resource configuration indexes and/or SS/PBCH block indexes by higher layer parameter Candidate-Beam-RS-List for radio link quality measurements on the serving cell. If there is no configuration, the beam failure detection could be based on CSI-RS or SSB, which is spatially Quasi Co-Located (QCLed) with the PDCCH Demodulation Reference Signal (DMRS). For example, if the UE is not provided with the higher layer parameter Beam-Failure-Detection-RS-ResourceConfig, the UE determines ^{q 0} to include SS/PBCH blocks and periodic CSI-RS configurations with same values for higher layer parameter TCI-StatesPDCCH as for control resource sets (CORESET) that the UE is configured for monitoring PDCCH.

[0054] The physical layer of a UE assesses the radio link quality according to a set ^{q 0} of resource configurations against a threshold Qout,LR. The threshold Qout,LR corresponds to a default value of higher layer parameter RLM-IS-OOS-thresholdConfig and Beam-failure-candidate-beam- threshold, respectively. For the set ^{q 0} , the UE assesses the radio link quality only according to periodic CSI-RS resource configurations or SS/PBCH blocks that are quasi co-located, with the DM-RS of PDCCH receptions DM-RS monitored by the UE. The UE applies the configured Qin,LR threshold for the periodic CSI-RS resource configurations. The UE applies the Qo threshold for SS/PBCH blocks after scaling a SS/PBCH block transmission power with a value provided by higher layer parameter Pc_SS.

[0055] If a beam failure indication has been received by a MAC entity from lower layers, then the MAC entity starts a beam failure recovery timer (beamFailureRecoveryTimer) and initiates a random access procedure. If the beamFailureRecoveryTimer expires, then the MAC entity indicates a beam failure recovery request failure to upper layers. If a DL assignment or UL grant has been received (e.g., on a PDCCH addressed for a cell radio network temporary identifier (C- RNTI)), then the MAC entity may stop and reset beamFailureRecoveryTimer and consider the beam failure recovery request procedure to be successfully completed.

[0056] Beam Measurement

[0057] The UE in the RRC_CONNECTED mode is to measure one or multiple beams of a cell, and to average the measurement results (e.g., power values) to derive the cell quality.

[0058] The UE derives cell measurement results by measuring one or multiple beams associated per cell as configured by the network. According to some embodiments, for all cell measurement results in RRC_CONNECTED mode, the UE may apply layer 3 filtering before using the measured results for evaluation of reporting criteria and measurement reporting. For cell measurements, the network can configure referenced signal receive power (RSRP), reference signal received quality (RSRQ), and/or signal to noise and interference ratio SINR as a trigger quantity. Reporting quantities can be the same as the trigger quantity or combinations of quantities (e.g., RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ and SINR). [0059] The network may also configure the UE to report measurement information per beam, which can either be measurement results per beam with respective beam identifier(s) or only beam identifier(s). If beam measurement information is configured to be included in measurement reports, the UE may apply the layer 3 beam filtering. However, the exact layer 1 filtering of beam measurements used to derive cell measurement results may be implementation dependent.

[0060] The UE may be configured to consider a subset of the detected beams, such as the N best beams above an absolute threshold. Filtering may take place at two different levels including at the physical layer (PHY) to derive beam quality and then at the RRC level to derive cell quality from multiple beams. Cell quality from beam measurements may be derived in the same way for the serving cell(s) and for the non-serving cell(s).

[0061] Measurement reports may contain the measurement results of the X best beams if the UE is configured to do so by the gNodeB. For channel state estimation purposes, the UE may be configured to measure CSI-RS resources and estimate a downlink channel state based on the CSI-RS measurements. The UE may feed the estimated channel state back to the gNodeB to be used in link adaptation.

[0062] An example measurement model 200 for the above embodiments is shown by way of Example in Fig.2. In Fig.2, point A at 202 includes measurements for example on beam specific samples internal to the PHY. Layer 1 (L1) filtering at 104 includes internal layer 1 filtering circuitry for filtering the inputs measured at point A. The exact filtering mechanisms and how the measurements are actually executed at the PHY may be implementation specific. The measurements (e.g., beam specific measurements) at point A ¹ at 205 are reported by the L1 filtering at 204 to layer 3 (L3) beam filtering circuitry 206 and the beam consolidation/selection circuitry 208.

[0063] The beam consolidation/selection circuitry 208 includes circuitry where beam specific measurements may be consolidated to derive cell quality. For example, if N > 1, else when N = 1 the best beam measurement may be selected to derive cell quality. The configuration of the beam may be provided by RRC signaling. A measurement (e.g., cell quality) derived from the beam-specific measurements may then be reported to L3 filtering for cell quality circuitry 210 after beam consolidation/selection at 208. In some embodiments, the reporting period at point B 209 may be equal to one measurement period at point A ¹ at 205. [0064] The L3 filtering for cell quality circuitry 210 may be configured to filter the measurements provided at point B 209. The configuration of the Layer 3 filters at 210 may be provided by the aforementioned RRC signaling or different/separate RRC signaling. In some embodiments, the filtering reporting period at point C 212 may be equal to one measurement period at point B 209. A measurement after processing in the layer 3 filter circuitry 206 is provided to the evaluation of reporting criteria circuitry 214 at point C 212. In some embodiments, the reporting rate may be identical to the reporting rate at point B 209. The resulting measurement input may be used for one or more evaluation of reporting criteria.

[0065] Evaluation of reporting criteria circuitry 214 is configured to check whether actual measurement reporting is necessary at point D 215. The evaluation can be based on more than one flow of measurements at reference point C 212. In one example, the evaluation may involve a comparison between different measurements, such as a measurement provided at point C 212 and another measurement provided at point C ¹ 212. In one embodiment, the UE may evaluate the reporting criteria at least every time a new measurement result is reported at point C, C ¹ 212. The reporting criteria configuration may be provided by the aforementioned RRC signaling (for UE measurements) or by different/separate RRC signaling. After the evaluation, measurement report information (e.g., a message) may be sent on the radio interface at point D 215.

[0066] Referring back to point A ¹ 205 measurements provided at point A ¹ are provided to L3 Beam filtering circuitry 206, which is configured to perform beam filtering of the provided measurements (e.g., beam specific measurements). The configuration of the beam filters may be provided by the aforementioned RRC signaling or different/separate RRC signaling. In embodiments, the filtering reporting period at point E 216 may be equal to one measurement period at A ¹ 205. The K beams 218 may correspond to the measurements on New Radio (NR)- synchronization signal (SS) block (SSB) or Channel State Information Reference Signal (CSI-RS) resources configured for L3 mobility by a gNodeB and detected by the UE at L1.

[0067] After processing in the beam filter measurement (e.g., beam-specific measurement), a measurement may be provided to beam selection for reporting circuitry at point E 216. This measurement may be used as an input for selecting the X measurements to be reported. In embodiments, the reporting rate may be identical to the reporting rate at point A ¹ 205. The beam selection for beam reporting circuitry 218 may be configured to select the X measurements from the measurements provided at point E 216. The configuration of this module may be provided by the aforementioned RRC signaling or different/separate RRC signaling. The beam measurement information to be included in a measurement report may be sent or scheduled for transmission on the radio interface at point F 220.

[0068] L1 filtering introduces a certain level of measurement averaging. Exactly how and when the UE performs the required measurements may be implementation specific to the point that the output at B 209 fulfils the predefined performance requirements. L3 filtering for cell quality and related parameters do not introduce any delay in the sample availability between B 209 and C 212. Measurement at point C, C ¹ 212 is the input used in the event evaluation. L3 Beam filtering and related parameters do not introduce any delay in the sample availability between E 216 and F 220.

[0069] The measurement reports include a measurement identity of an associated measurement configuration that triggered the reporting; cell and beam measurement quantities to be included in measurement reports are configured by the network (e.g., using RRC signaling); the number of non-serving cells to be reported can be limited through configuration by the network; cells belonging to a blacklist configured by the network are not used in event evaluation and reporting, and conversely when a whitelist is configured by the network, only the cells belonging to the whitelist are used in event evaluation and reporting (by contrast), when a whitelist is configured by the network, only the cells belonging to the whitelist are used in event evaluation and reporting; and beam measurements to be included in measurement reports are configured by the network (beam identifier only, measurement result and beam identifier, or no beam reporting).

[0070] Intra-frequency neighbor (cell) measurements may include SSB based intra-frequency measurement(s) and CSI-RS based intra-frequency measurements. SSB based intra-frequency measurements may be defined as an SSB based intra-frequency measurement provided the center frequency of the SSB of the serving cell and the center frequency of the SSB of the neighbor cell are the same, and the subcarrier spacing of the two SSBs is also the same. CSI-RS based intra-frequency measurements may be defined as a CSI-RS based intra-frequency measurement provided the bandwidth of the CSI-RS resource on the neighbor cell configured for measurement is within the bandwidth of the CSI-RS resource on the serving cell configured for measurement, and the subcarrier spacing of the two CSI-RS resources is the same.

[0071] Inter-frequency neighbor (cell) measurements may include SSB based inter-frequency measurement(s) and CSI-RS based inter-frequency measurements. SSB based inter-frequency measurements may be defined as an SSB based inter-frequency measurement provided the center frequency of the SSB of the serving cell and the center frequency of the SSB of the neighbor cell are different, or the subcarrier spacing of the two SSBs is different. For SSB based measurements, one measurement object corresponds to one SSB and the UE considers different SSBs as different cells. CSI-RS based inter-frequency measurements is/are measurement is defined as a CSI-RS based inter-frequency measurement provided the bandwidth of the CSI-RS resource on the neighbor cell configured for measurement is not within the bandwidth of the CSI-RS resource on the serving cell configured for measurement, or the subcarrier spacing of the two CSI-RS resources is different.

[0072] Whether a measurement is non-gap-assisted or gap-assisted depends on the capability of the UE, the active BWP of the UE and the current operating frequency. In non-gap-assisted scenarios, the UE may carry out such measurements without measurement gaps. In gap- assisted scenarios, the UE cannot be assumed to be able to carry out such measurements without measurement gaps.

[0073] Bandwidth Adaptation

[0074] With Bandwidth Adaptation (BA), the receive and transmit bandwidth of the UE need not be as large as the bandwidth (BW) of the cell and can be adjusted. The adjustment may include adjusting the width (e.g. to shrink during period of low activity to save power), the location can move in the frequency domain (e.g. to increase scheduling flexibility), and the subcarrier spacing can be ordered to change (e.g. to allow different services). A subset of the total cell bandwidth of a cell is referred to as a Bandwidth Part (BWP) and BA is achieved by configuring the UE with one or more BWP(s) and indicating which of the configured BWPs is currently an active BWP. As an example, a cell BW may be divided into a first BWP with a width of 40 MHz and subcarrier spacing of 15 kHz, a second BWP with a width of 10 MHz and subcarrier spacing of 15 kHz, and a third BWP with a width of 20 MHz and subcarrier spacing of 60 kHz.

[0075] When BA is enabled/configured, the UE acquires system information (SI) on the active BWP. To enable BA on a PCell, the gNodeB configures the UE with UL and DL BWP(s). To enable BA on SCells where carrier aggregation (CA) is used, the gNodeB at least configures the UE with DL BWP(s), and there may be no UL BWP(s) although UL BWP(s) are not precluded. For the PCell, the initial BWP is the BWP used for initial access. For the SCell(s), the initial BWP is the BWP configured for the UE to first operate at SCell activation. In paired spectrum, DL and UL can switch BWP independently. In unpaired spectrum, DL and UL switch BWP simultaneously. Switching between configured BWPs happens by means of DCI or an inactivity timer. When an inactivity timer is configured for a serving cell, the expiry of the inactivity timer associated with that cell switches the active BWP to a default BWP configured by the network.

[0076] Additionally, a gNodeB can dynamically allocate resources to UEs via the C-RNTI on PDCCH(s) for both DL and UL scheduling assignments. When the UE has enabled DL reception, the UE always monitors the PDCCH(s) in order to find possible DL assignments, and always monitors the PDCCH(s) in order to find possible grants for uplink transmission. When CA is configured, the same C-RNTI applies to all serving cells, at most one configured DL assignment can be signaled per serving cell, and at most one configured UL grant can be signaled per serving cell. In these cases, the UE is only required to monitor the PDCCH on the one active BWP and does not have to monitor PDCCH on the entire DL frequency of the cell. An independent BWP inactivity timer is used to switch the active BWP to the default one. The timer is restarted upon successful PDCCH decoding and the switch to the default BWP takes place when it expires.

[0077] When BA is configured, at most one configured DL assignment can be signaled per BWP. On each serving cell, there can be only one configured DL assignment active at a time, and multiple configured DL assignments can be simultaneously active on different serving cells only. Activation and deactivation of configured DL assignments are independent among the serving cells. Additionally, when BA is configured, at most one configured UL grant can be signaled per BWP. On each serving cell, there can be only one configured UL grant active at a time. A configured UL grant for one serving cell can either be of Type 1 or Type 2. For Type 2, activation and deactivation of configured UL grants are independent among the serving cells. When supplementary uplink (SUL) is configured, a configured UL grant can only be signaled for one of the 2 ULs of the cell.

[0078] To enable reasonable UE battery consumption when BA is configured, only one UL BWP for each uplink carrier and one DL BWP or only one DL/UL BWP pair can be active at a time in an active serving cell, all other BWPs that the UE is configured with being deactivated. On deactivated BWPs, the UE may not monitor the PDCCH, and may not transmit on PUCCH, PRACH and UL-SCH.

[0079] The BWP IE is used to configure the BWP(s) as discussed above. The network configures at least an initial BWP for each serving cell comprising at least a DL BWP and one (if the serving cell is configured with an uplink) or two (if using supplementary uplink (SUL)) UL BWP(s). The BWP IE includes individual BWP-Id IEs to refer to corresponding BWPs. The initial BWP is referred to by BWP-Id 0, and the other BWPs are referred to by BWP-Id 1 to maxNrofBWPs. Furthermore, the network may configure additional UL and/or DL BWP(s) for a serving cell. The BWP configuration is split into UL and DL parameters and into common and dedicated parameters. Common parameters (in BWP-UplinkCommon and BWP-DownlinkCommon) are cell-specific parameters and the network ensures the necessary alignment with corresponding parameters of other UEs. The common parameters of the initial BWP of the PCell are also provided via SI. For all other serving cells, the network provides the common parameters via dedicated signaling.

[0080] When configured, the UE monitors a set of PDCCH candidates in one or more control resource sets (CORESETS) on the active DL BWP on each activated serving cell according to corresponding search spaces where monitoring implies decoding each PDCCH candidate according to the monitored downlink control information (DCI) formats. A set of PDCCH candidates for the UE to monitor is defined in terms of PDCCH search spaces. A search space can be a common search space (CSS) or the UE-specific search space (USS or UE-SS). The UE monitors for PDCCH candidates in one or more of the following search spaces:

- a Type0-PDCCH CSS for a DCI format with CRC scrambled by a system information (SI) RNTI (SI-RNTI) on a primary cell; - a Type0A-PDCCH CSS for a DCI format with CRC scrambled by a SI-RNTI on a primary cell; - a Type1-PDCCH CSS for a DCI format with CRC scrambled by a RA-RNTI, or a TC- RNTI, or a C-RNTI on a primary cell; - a Type2-PDCCH CSS for a DCI format with CRC scrambled by a P-RNTI on a primary cell; - a Type3-PDCCH CSS for a DCI format with CRC scrambled by INT-RNTI, or SFI- RNTI, or TPC-PUSCH-RNTI, or TPC-PUCCH-RNTI, or TPC-SRS-RNTI, or C-RNTI, or CS-RNTI(s), or SP-CSI-RNTI; and - a UE-SS for a DCI format with CRC scrambled by C-RNTI, or CS-RNTI(s), or SP-CSI- RNTI. [0081] The UE is provided with a configuration for a CORESET for Type0-PDCCH CSS by the higher layer parameter RMSI-PDCCH-Config and a subcarrier spacing by the higher layer parameter RMSI-scs for PDCCH reception. The UE determines the CORESET and the monitoring occasions for Type0-PDCCH CSS. The Type0-PDCCH CSS is defined by the control channel element (CCE) aggregation levels (ALs) and the number of PDCCH candidates per CCE AL given in Table BWP-1. The CORESET configured for Type0-PDCCH CSS has CORESET index 0. The Type0-PDCCH CSS has search space index 0.

[0082] For Type0A-PDCCH CSS or for Type2-PDCCH CSS, the CORESET is same as the CORESET for Type0-PDCCH CSS. The UE is provided a configuration for Type0A-PDCCH CSS by the higher layer parameter osi-SearchSpace. The CCE ALs and the number of PDCCH candidates per CCE AL is given in Table BWP-1. If the UE is not provided with the osi-SearchSpace for Type0A- PDCCH CSS, the association between monitoring occasions for Type0A-PDCCH CSS and the SS/PBCH block index is the same as the association of monitoring occasions for Type0-PDCCH CSS.

[0083] The UE is provided a configuration for Type2-PDCCH CSS by the higher layer parameter paging-SearchSpace. The CCE ALs and the number of PDCCH candidates per CCE AL are given in Table BWP-1. If the UE is not provided with the paging-SearchSpace for Type2-PDCCH CSS, the association between monitoring occasions for Type2-PDCCH CSS and the SS/PBCH block index is the same as the association of monitoring occasions for Type0-PDCCH CSS,

[0084] For Type1-PDCCH CSS, the UE is provided with a configuration for a CORESET by the higher layer parameter rach-coreset-configuration and a configuration for a search space by the higher layer parameter ra-SearchSpace. If the rach-coreset-configuration is not provided to the UE, the CORESET for Type1-PDCCH CSS is the same as for Type0-PDCCH CSS. If the UE is not provided with the ra-SearchSpace for Type1-PDCCH CSS, the association between monitoring occasions for Type1-PDCCH CSS and the SS/PBCH block index is the same as the association of monitoring occasions for Type0-PDCCH CSS.

[0085] The UE may assume that the DM-RS antenna port associated with PDCCH reception in the Type0-PDCCH CSS, the Type0A-PDCCH CSS, and the Type2-PDCCH CSS, and for corresponding PDSCH receptions, and the DM-RS antenna port associated with SS/PBCH reception are quasi co-located with respect to delay spread, Doppler spread, Doppler shift, average delay, and spatial Rx parameters. The value for the DM-RS scrambling sequence initialization is the cell ID. [0086] The subcarrier spacing and the CP length for PDCCH reception with Type0A-PDCCH CSS, or Type1-PDCCH CSS, or Type2-PDCCH CSS are the same as for PDCCH reception with Type0- PDCCH CSS.

[0087] The UE may assume that the DM-RS antenna port associated with PDCCH reception and associated PDSCH reception in the Type1-PDCCH CSS are quasi co-located with the SS/PBCH block identified in initial access procedure or with a received CSI-RS with respect to delay spread, Doppler spread, Doppler shift, average delay, and spatial Rx parameters, when applicable.

[0088] If a value for the DM-RS scrambling sequence initialization for Type0A-PDCCH CSS, or Type1-PDCCH CSS, or Type2-PDCCH CSS is not provided by higher layer parameter PDCCH- DMRS-Scrambling-ID in SystemInformationBlockType1, the value is the cell ID.

[0089] When the UE is configured for DL BWP operation, the above configurations for the CSSs apply for the initial active DL BWP, and the UE can be additionally configured with a CORESET for Type0-PDCCH CSS, Type0A-PDCCH CSS, Type1-PDCCH CSS, or Type2-PDCCH CSS for each configured DL BWP on the PCell, other than the initial active DL BWP.

Table BWP-1: control channel element aggregation levels (CCE ALs) and maximum number of PDCCH candidates per CCE AL for Type0/Type0A/Type2-PDCCH CSS

[0090] For each DL BWP configured to the UE in a serving cell, the UE can be provided by higher layer signaling with P CORESETs where P£ 3. For CORESET p , 0£ p < P , the higher layer signaling provides:

- a CORESET index by higher layer parameter CORESET-ID;

- a DM-RS scrambling sequence initialization value by higher layer parameter PDCCH-DMRS-Scrambling-ID;

- a number of consecutive symbols provided by higher layer parameter CORESET- time-duration;

- a set of resource blocks provided by higher layer parameter CORESET-freq-dom; - a CCE-to-REG mapping provided by higher layer parameter CORESET-CCE-to- REG-mapping-type; - a REG bundle size, in case of interleaved CCE-to-REG mapping, provided by higher layer parameter CORESET-REG-bundle-size;

- a cyclic shift for the REG bundle interleaver by higher layer parameter CORESET- shift-index;

- an antenna port quasi co-location, from a set of antenna port quasi co-locations provided by higher layer parameter TCI-StatesPDCCH, indicating quasi co-location information of the DM-RS antenna port for PDCCH reception;

- an indication for a presence or absence of a transmission configuration indication (TCI) field for DCI format 1_0 or DCI format 1_1 transmitted by a PDCCH in CORESET p , by higher layer parameter TCI-PresentInDCI.

[0091] For each CORESET in a DL BWP of a serving cell, a respective higher layer parameter CORESET-freq-dom provides a bitmap. The bits of the bitmap have a one-to-one mapping with non-overlapping groups of 6 physical resource blocks (PRBs), in ascending order of the PRB index in the DL BWP bandwidth of N PRBs with starting position N ^start

B _WP where the first PRB of the first group of 6 PRBs has index ^6´ _^ ^{N start}

B _WP ⁶ _^ . A group of 6 PRBs is allocated to a CORESET if a corresponding bit value in the bitmap is 1; else, if a corresponding bit value in the bitmap is 0, the group of 6 PRBs is not allocated to the CORESET.

[0092] If the UE has received initial configuration of more than one TCI states by higher layer parameter TCI-StatesPDCCH containing more than one TCI states but has not received a MAC CE activation for one of the TCI states, the UE assumes that the DM-RS antenna port associated with PDCCH reception in the UE-SS is quasi co-located with the SS/PBCH block the UE identified during the initial access procedure with respect to delay spread, Doppler spread, Doppler shift, average delay, and spatial Rx parameters, when applicable.

[0093] If the UE has received higher layer parameter TCI-StatesPDCCH containing a single TCI state, the UE assumes that the DM-RS antenna port associated with PDCCH reception in the UE-SS is quasi co-located with the one or more DL RS configured by the TCI state.

[0094] For each DL BWP of a serving cell where the UE is configured to monitor PDCCH in a search space, the UE is configured the following by higher layer parameter search-space-config:

- an association between a search space set index ^s , ^{0£ s < S} , where ^{S £ 10} , and a CORESET index p ;

- for the search space set s in the CORESET p : - an indication that the search space set is a CSS set or the UE-SS set by higher layer parameter Common-search-space-flag;

- if the search space set ^s is for a CSS, an indication by higher layer parameter RNTI-monitoring to monitor PDCCH for one or more of DCI format 0_0 and DCI format 1_0 with CRC scrambled by a RNTI from RNTIs, DCI format 2_0, DCI format 2_1, DCI format 2_2, and DCI format 2_3;

- if the search space set s is the UE-SS, an indication by higher layer parameter USS-DCI-format to monitor PDCCH either for DCI format 0_0 and DCI format 1_0, or for DCI format 0_1 and DCI format 1_1;

- a number of PDCCH candidates M ⁽ L ⁾

p, _s per CCE AL L by higher layer parameters aggregationLevel1, aggregationLevel2, aggregationLevel4, aggregationLevel8, and aggregationLevel16, for CCE AL 1, CCE AL 2, CCE AL 4, CCE AL 8, and CCE AL 16, respectively;

- a PDCCH monitoring periodicity of ^k _{p , s} slots by higher layer parameter monitoringSlotPeriodicityAndOffset;

- a PDCCH monitoring offset of o slots, where 0£o _p,s < k _{p , s} , by higher layer parameter monitoringSlotPeriodicityAndOffset;

- a PDCCH monitoring pattern within a slot, indicating first symbol(s) of the CORESET within a slot for PDCCH monitoring, by higher layer parameter monitoringSymbolsWithinSlot.

[0095] If the higher layer parameter monitoringSymbolsWithinSlot indicates to the UE only one PDCCH monitoring occasion within a slot, the UE is not expected to be configured a corresponding search space set ^s for a PDCCH subcarrier spacing other than 15 kHz if the CORESET p associated with the search space s includes at least one symbol after the third slot symbol.

[0096] For a subcarrier spacing of 15 KHz, if the higher layer parameter monitoringSymbolsWithinSlot for a search space set s indicates to the UE only one PDCCH monitoring occasion in a slot for a corresponding CORESET ^p and the CORESET ^p includes at least one symbol after the third slot symbol, the UE expects that all CORESETs configured to the UE are located within at most three same consecutive symbols in the slot.

[0097] The UE determines a PDCCH monitoring occasion from the PDCCH monitoring periodicity, the PDCCH monitoring offset, and the PDCCH monitoring pattern within a slot. For search space set s in CORESET p , the UE determines that a PDCCH monitoring occasion(s) exists in a slot with number n ^µ

s _,f in a frame with number n _f if ₍ n ´ ^{frame,µ µ}

f N _slot +n _s,f -o _{p,s )} mod k _{p , s} = 0.

[0098] A PDCCH UE-SS S at CCE AL LÎ {1,2,4,8,16 } is defined by a set of PDCCH candidates for CCE AL L .

[0099] If the UE is configured with higher layer parameter CrossCarrierSchedulingConfig for a serving cell the carrier indicator field value corresponds to the value indicated by CrossCarrierSchedulingConfig.

[0100] For a DL BWP of a serving cell on which the UE monitors PDCCH candidates in the UE- SS, if the UE is not configured with a carrier indicator field, the UE is to monitor the PDCCH candidates without carrier indicator field. For a serving cell on which the UE monitors PDCCH candidates in the UE-SS, if the UE is configured with a carrier indicator field, the UE is to monitor the PDCCH candidates with carrier indicator field.

[0101] The UE is not expected to monitor PDCCH candidates on a DL BWP of a secondary cell if the UE is configured to monitor PDCCH candidates with carrier indicator field corresponding to that secondary cell in another serving cell. For the DL BWP of a serving cell on which the UE monitors PDCCH candidates, the UE is to monitor PDCCH candidates at least for the same serving cell.

[0102] Table BWP-2 provides the maximum number of PDCCH candidates, M across all CCE ALs and across all DCI formats with different size in a same search space that the UE is expected to monitor per slot and per serving cell as a function of the subcarrier spacing. Table BWP-2: Maximum number of PDCCH candidates per slot and per serving cell as a function of the subcarrier spacing value 2 ^µ ´ 15 kHz, µÎ { 0,1,2,3 } .

[0103] Table BWP-3 provides the maximum number of non-overlapped CCEs, C ^{max, slot}

P _DCCH , that the UE is expected to monitor per slot and per serving cell as a function of the subcarrier spacing, if the higher layer parameter Monitoring-symbols-PDCCH-within-slot indicates to the UE only one PDCCH monitoring occasion within a slot. CCEs are non-overlapped if the correspond to: different CORESET indexes, or different first symbols for the reception of the respective PDCCH candidates.

Table BWP-3: Maximum number of non-overlapped CCEs per slot and per serving cell as a function of the subcarrier spacing value2 ^µ ´ 15 kHz,µÎ { 0,1,2,3 } .

[0104] Denote byS _css a set of search space setss _css for CSSs in a corresponding set P _css of CORESETsp _css and byS _uss a set of search space setss _uss for UE-SSs in a corresponding setP _uss of CORESETs ^p _uss where the UE monitors PDCCH candidates in a slot. If

candidates for the CSSs andM ^uss

P _DCCH = PDCCH candidates for UE-SSs in the slot. For a search space set s associated with CORESET p , the CCE indexes for AL L corresponding to PDCCH candidatems ,n _CI of the search space set in slotn ^µ

s _,f for a serving cell corresponding to carrier indicator field valuen _CI are given by

[0105] Where for any CSS, Y _p , _n µ

s _{, f} = 0 ; for the UE-SS, Y _p,n µ

s _,f = ₍ A _p ´Y _{p, n} µ

s _{, f -1 )} mod D , Y _p,-1 = n _RNTI ¹ 0 ,A ₀ = 39827 , A ₁ = 39829 , A ₂ = 39839 , andD= 65537 ;i=0, N _{CCE , p} is the number of CCEs, numbered from 0 toN _{CCE ,p} - 1 , in CORESET p ;n _CI is the carrier indicator field value if the UE is configured with a carrier indicator field by higher layer parameter CrossCarrierSchedulingConfig for the serving cell on which PDCCH is monitored; otherwise, including for any CSS, n _CI = 0 ; m _CI 0,..., M ^{( L )}

s _,n = _{p,s , n CI} - 1 , where M ^{(L )}

p _{,s , n CI} is the number of PDCCH candidates the UE is configured to monitor for AL ^L for a serving cell corresponding to ⁿ _CI and a search space set ^s ; for any CSS, ^{M(L) = M( L )}

p _{,s, max p,s, 0} ; for the UE-SS, ^{M(L )}

p _{,s, max} is the maximum of M( L )

p,s , n _CI over all configured n _CI values for a CCE AL L of search space set s in CORESET p ; the RNTI value used for n _RNTI is defined in 3GPP TS 38.212 and in 3GPP TS 38.214.

[0106] If, for the UE, any CCE index for PDCCH candidate with index ^m _{s,n CI , 2} with AL ^L in CORESET p overlaps with any CCE index for PDCCH candidate with index ^m with AL L in CORESET p , where m _{s,nCI ,1} < m _{s, n CI , 2} , the UE is not expected to monitor the PDCCH candidate with indexm _{s,n CI , 2} .

[0107] The UE is not expected to be configured to monitor DCI format 0_1 or DCI format 1_1 in a CSS. The UE configured to monitor PDCCH candidates in a serving cell with a DCI format size with carrier indicator field and CRC scrambled by C-RNTI, where the PDCCH candidates may have one or more possible values of carrier indicator field for the DCI format size, is to assume that an PDCCH candidate with the DCI format size may be transmitted in the serving cell in any PDCCH UE specific search space corresponding to any of the possible values of carrier indicator field for the DCI format size if the UE includes in UE-NR-Capability an indication for a corresponding capability.

[0108] The UE configured with a bandwidth part indicator in DCI formats 0_1 or 1_1 is to, in case of an active DL BWP or of an active UL BWP change, determine the DCI information applicable to the new active DL BWP or UL BWP, respectively, as described infra.

[0109] For unpaired spectrum operation, if the UE is not configured for PUSCH/PUCCH transmission on serving cell c ₂ , the UE is not expected to monitor PDCCH on serving cell c ₁ if the PDCCH overlaps in time with SRS transmission (including any interruption due to uplink or downlink RF retuning time on serving cell c ₂ and if the UE is not capable of simultaneous reception and transmission on serving cell c ₁ and serving cell c ₂ .

[0110] Bandwidth Part Operation

[0111] According to 3GPP’s Technical Specification 38.213 V15.2.0 (hereinafter TS 38.213), when the UE is configured for operation in BWPs of a serving cell, the UE is configured by higher layers for the serving cell with a set of at most four BWPs for receptions by the UE (DL BWP set) in a DL bandwidth by the parameter BWP-Downlink and a set of at most four BWPs for transmissions by the UE (UL BWP set) in an UL bandwidth by the parameter BWP-Uplink for the serving cell. [0112] In TS38.213 V15.2.0, an initial active DL BWP is defined by a location and number of contiguous PRBs, a subcarrier spacing, and a cyclic prefix, for the control resource set for Type0- PDCCH common search space. For operation on the primary cell or on a secondary cell, a UE is provided an initial active UL BWP by higher layer parameter initialuplinkBWP. If the UE is configured with a supplementary carrier, the UE can be provided an initial UL BWP on the supplementary carrier by higher layer parameter initialUplinkBWP in supplementaryUplink.

[0113] If a UE has dedicated BWP configuration, the UE can be provided by higher layer parameter firstActiveDownlinkBWP-Id a first active DL BWP for receptions and by higher layer parameter firstActiveUplinkBWP-Id a first active UL BWP for transmissions on the primary cell.

[0114] In TS38.213 V15.2.0, for each DL BWP or UL BWP in a set of DL BWPs or UL BWPs, respectively, the UE is configured the following parameters for the serving cell:

- a subcarrier spacing provided by higher layer parameter DL-BWP-mu or UL- BWP-mu or a subcarrier spacing provided by higher layer parameter subcarrierSpacing

- a cyclic prefix provided by higher layer parameter DL-BWP-CP or UL-BWP-CP or a cyclic prefix provided by higher layer parameter cyclicPrefix;

- a PRB offset with respect to the PRB determined by higher layer parameters offset-pointA-low-scs and ref-scs and a number of contiguous PRBs provided by higher layer parameter DL-BWP-BW or UL-BWP-BW or a first PRB and a number of contiguous PRBs indicated by higher layer parameter locationAndBandwidth that is interpreted as RIV, settingN ^size

B _WP =275, and the first PRB is a PRB offset relative to the PRB indicated by higher layer parameters offsetToCarrier and subcarrierSpacing;

- an index in the set of DL BWPs or UL BWPs by respective higher layer parameters DL-BWP-index or UL-BWP-index or an index in the set of DL BWPs or UL BWPs by respective higher layer parameter bwp-Id;

- a set of BWP-common and a set of BWP-dedicated parameters by higher layer parameters bwp-Common and bwp-Dedicated; and/or

- according to some embodiments, DCI format 1_0 or DCI format 1_1 detection to a PDSCH reception timing values by higher layer parameter DL-data-time-domain, PDSCH reception to a HARQ-ACK transmission timing values by higher layer parameter DL-data-DL- acknowledgement, and DCI format 0_0 or DCI format 0_1 detection to a PUSCH transmission timing values by higher layer parameter UL-data-time-domain; [0115] In TS38.213 V15.2.0, for unpaired spectrum operation, a DL BWP from the set of configured DL BWPs with index provided by higher layer parameter bwp-Id for the DL BWP is linked with an UL BWP from the set of configured UL BWPs with index provided by higher layer parameter bwp-Id for the UL BWP when the DL BWP index and the UL BWP index are equal. For unpaired spectrum operation, a UE does not expect to receive a configuration where the center frequency for a DL BWP is different than the center frequency for an UL BWP when the bwp-Id of the DL BWP is equal to the bwp-Id of the UL BWP.

[0116] For each DL BWP in a set of DL BWPs on the primary cell, a UE can be configured control resource sets for every type of common search space and for UE-specific search space as described in Subclause 10.1 of TS38.213 V15.2.0. The UE does not expect to be configured without a common search space on the PCell, or on the PSCell, in the active DL BWP.

[0117] For each UL BWP in a set of UL BWPs, the UE is configured resource sets for PUCCH transmissions. The UE is to receive PDCCH and PDSCH in a DL BWP according to a configured subcarrier spacing and CP length for the DL BWP. The UE is to transmit PUCCH and PUSCH in an UL BWP according to a configured subcarrier spacing and CP length for the UL BWP.

[0118] If a BWP indicator field is configured in DCI format 1_1, the BWP indicator field value indicates the active DL BWP, from the configured DL BWP set, for DL receptions. If a BWP indicator field is configured in DCI format 0_1, the BWP indicator field value indicates the active UL BWP, from the configured UL BWP set, for UL transmissions. If a BWP indicator field is configured in DCI format 0_1 or DCI format 1_1 and indicates an UL BWP or a DL BWP different from the active UL BWP or DL BWP, respectively, the UE is to:

- for each information field in the received DCI format 0_1 or DCI format 1_1; - if the size of the information field is smaller than the one required for the DCI format 0_1 or DCI format 1_1 interpretation for the UL BWP or DL BWP that is indicated by the bandwidth part indicator, respectively, the UE prepends zeros to the information field until its size is the one required for the interpretation of the information field for the UL BWP or DL BWP prior to interpreting the DCI format 0_1 or DCI format 1_1 information fields, respectively;

- if the size of the information field is larger than the one required for the DCI format 0_1 or DCI format 1_1 interpretation for the UL BWP or DL BWP that is indicated by the bandwidth part indicator, respectively, the UE uses a number of least significant bits of DCI format 0_1 or DCI format 1_1 equal to the one required for the UL BWP or DL BWP indicated by bandwidth part indicator prior to interpreting the DCI format 0_1 or DCI format 1_1 information fields, respectively; and/or

- set the active UL BWP or DL BWP to the UL BWP or DL BWP indicated by the bandwidth part indicator in the DCI format 0_1 or DCI format 1_1, respectively.

[0119] In TS38.213 V15.2.0, a UE is to expect to detect a DCI format 0_1 indicating active UL BWP change, or a DCI format 1_1 indicating active DL BWP change, only if a corresponding PDCCH is received within the first 3 symbols of a slot.

[0120] For the primary cell, the UE can be provided by higher layer parameter defaultDownlinkBWP-Id a default DL BWP among the configured DL BWPs. If the UE is not provided a default DL BWP by higher layer parameter defaultDownlinkBWP-Id, the default DL BWP is the initial active DL BWP.

[0121] If the UE is configured for a secondary cell with higher layer parameter defaultDownlinkBWP-Id indicating a default DL BWP among the configured DL BWPs and the UE is configured with higher layer parameter bwp-InactivityTimer indicating a timer value, the UE procedures on the secondary cell are the same as on the primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

[0122] If the UE is configured by higher layer parameter bwp-InactivityTimer a timer value for the primary cell and the timer is running, the UE increments the timer every interval of 1 millisecond for frequency range 1 or every 0.5 milliseconds for frequency range 2 if the UE does not detect a DCI format for PDSCH reception on the primary cell for paired spectrum operation or if the UE does not detect a DCI format for PDSCH reception or a DCI format for PUSCH transmission on the primary cell for unpaired spectrum operation during the interval (see TS 38.321).

[0123] If the UE is configured by higher layer parameter BWP-InactivityTimer a timer value for a secondary cell and the timer is running, the UE increments the timer every interval of 1 millisecond for frequency range 1 or every 0.5 milliseconds for frequency range 2 if the UE does not detect a DCI format for PDSCH reception on the secondary cell for paired spectrum operation or if the UE does not detect a DCI format for PDSCH reception or a DCI format for PUSCH transmission on the secondary cell for unpaired spectrum operation during the interval. The UE may deactivate the secondary cell when the timer expires.

[0124] If the UE is configured by higher layer parameter firstActiveDownlinkBWP-Id a first active DL BWP and by higher layer parameter firstActiveUplinkBWP-Id a first active UL BWP on a secondary cell or supplementary carrier, the UE uses the indicated DL BWP and the indicated UL BWP on the secondary cell as the respective first active DL BWP and first active UL BWP on the secondary cell or supplementary carrier.

[0125] For paired spectrum operation, a UE does not expect to transmit HARQ-ACK information on a PUCCH resource indicated by a DCI format 1_0 or a DCI format 1_1 if the UE changes its active UL BWP on the PCell between a time of a detection of the DCI format 1_0 or the DCI format 1_1 and a time of a corresponding HARQ-ACK information transmission on the PUCCH.

[0126] The UE is also not expected to monitor PDCCH when the UE performs RRM measurements over a bandwidth that is not within the active DL BWP for the UE.

[0127] Fig. 3 illustrates an architecture of a system 300 of a network according to some embodiments. The system 300 is shown to include a user equipment (UE) 301 and a UE 302. The UEs 301 and 302 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.

[0128] The UEs 301 and 302 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 310. The UEs 301 and 302 utilize connections 303 and 304, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 303 and 304 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols.

[0129] In this embodiment, the UEs 301 and 302 may further directly exchange communication data via a ProSe interface 305. The ProSe interface 305 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).

[0130] The UE 302 is shown to be configured to access an access point (AP) 306 via connection 307. The connection 307 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 306 would comprise a wireless fidelity (WiFi®) router. In this example, the AP 306 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). [0131] The RAN 310 can include one or more access nodes that enable the connections 303 and 304. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), 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 310 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 311, 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 312.

[0132] According to some embodiments, the UEs 301 and 302 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 311 and 312 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.

[0133] The RAN 310 is shown to be communicatively coupled to a core network (CN) 320—via an S1 interface 313. In embodiments, the CN 320 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 313 is split into two parts: the S1-U interface 314, which carries traffic data between the RAN nodes 311 and 312 and the serving gateway (S-GW) 322, and the S1-mobility management entity (MME) interface 315, which is a signaling interface between the RAN nodes 311 and 312 and MMEs 321.

[0134] The CN 320 includes network elements. The term“network element” may describe a physical or virtualized equipment used to provide wired or wireless communication network services. In this embodiment, the CN 320 comprises, as network elements, the MMEs 321, the S-GW 322, the Packet Data Network (PDN) Gateway (P-GW) 323, and a home subscriber server (HSS) 324. The MMEs 321 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).

[0135] Fig. 4 illustrates example interfaces of baseband circuitry according to various embodiments. The baseband circuitry 400 may comprise processors 438-442 and a memory 444 utilized by said processors. Each of the processors 438-432 may include a memory interface, 404A-404E, respectively, to send/receive data to/from the memory 444. Baseband circuitry 400 may also include an audio digital signal processor (Audio DSP) 443.

[0136] The baseband circuitry 400 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 412 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 400), an application circuitry interface 414 (e.g., an interface to send/receive data to/from an application circuitry), an RF circuitry interface 416 (e.g., an interface to send/receive data to/from an RF circuitry), a wireless hardware connectivity interface 418 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 420 (e.g., an interface to send/receive power or control signals to/from a power management integrated circuit (PMIC).

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

[0138] 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: encode for communication with a NR evolved Node B (gNodeB) signals on multiple beams; and determine a timing for an uplink (UL) communication with the gNodeB based on a pair of transmit and receive beams respectively to and from the gNodeB.

[0139] Example 2 includes the subject matter of Example 1, and optionally, wherein the timing for the UL communication is based on a timing for a downlink (DL) communication corresponding to a time when a detected path of a corresponding DL frame is received from the gNodeB by the UE, minus a value equal to (^ _TA + ^ _{TA offset} ) × ^ _^ wherein ^ _^ corresponds to a time unit, and ^ _{TA offset} is given by: for full division duplex (FDD) in a FR1 frequency band for the UL communication, a value of 0; for time division duplex (TDD) in a FR1 frequency band for the UL communication, a value of 39936 or 25600; and for a FR2 frequency band for the UL communication, a value of 13792.

[0140] Example 3 includes the subject matter of Example 2, and optionally, wherein the processing circuitry is to adjust the timing for the UL communication such that a minimum aggregate adjustment rate is T _p per second, where T _p is equal to [5.5]*64*T _c when a subcarrier spacing (SCS) for the UL communication is 15 KHz, 30 KHz or 60 KHz in a FR1 frequency band, and where T _p is equal to [2.5]*64*T _c when the SCS for the UL communication is 60 KHz or 120 KHz in a FR2 frequency band.

[0141] Example 4 includes the subject matter of Example 1, and optionally, wherein the pair of transmit and receive beams include a transmit beam determined by the gNodeB, and a receive beam determined by the UE.

[0142] Example 5 includes the subject matter of Example 1, and optionally, wherein: the timing for the UL communication is based on a timing for a downlink (DL) communication after beam switching by the gNodeB, the timing corresponding to a time when a detected path of a corresponding DL frame is received from the gNodeB by the UE after beam switching, minus a value equal to (^ _TA + ^ _{TA offset} ) × ^ _^ where ^ _^ corresponds to a time unit; and the processing circuitry is to: determine that the timing for the DL communication after beam switching has changed as compared with a DL communication from the gNodeB before beam switching within ±D, where D = ½ cyclic prefix (CP) length); and determine the timing for the UL communication based on a timing adjustment of ±D as compared with a timing for an UL communication that corresponds to the DL communication from the gNodeB before beam switching.

[0143] Example 6 includes the subject matter of Example 5, and optionally, wherein the processing circuitry is to: determine that the timing for the DL communication after beam switching has changed as compared with a DL communication from the gNodeB before beam switching more than ±D; and initiate a random access procedure to obtain a new timing for DL communication.

[0144] Example 7 includes the subject matter of Example 5, and optionally, wherein D is based on a subcarrier spacing for the UL communication or the DL communication.

[0145] Example 8 includes the subject matter of Example 1, and optionally, wherein the processing circuitry is to cause the UE to be configured with a list of up to M transmission configuration state (TCI-State) configurations within a higher layer parameter PDSCH-Config to decode a physical downlink shared channel (PDSCH) according to a detected physical downlink control channel (PDCCH) with a downlink control information (DCI), where M is based on a capability of the UE, and where each TCI-State contains parameters for configuring a quasi co- location relationship between one or two downlink reference signals and demodulation reference signal (DM-RS) ports of the PDSCH. [0146] Example 9 includes the subject matter of Example 8, and optionally, wherein the processing circuitry is to: determine that a channel state information reference signal (CSI-RS) resource in a non-zero power (NZP) resource set; and determine, for at least one of the CSI-RS resource, DM-RS ports of a PDCCH ,or DM-RS ports of a PDSCH, a quasi-co-location type indication of the TCI-State based on a higher layer parameter configuration of the CSI-RS resource.

[0147] Example 10 includes the subject matter of Example 8, and optionally, wherein the processing circuitry is to encode for transmission to the gNodeB a beam failure recovery request based on radio link quality measurements on a serving cell of the gNodeB, the radio link quality measurements being based on at least one of: a configuration of the UE, by higher layer parameter Beam-Failure-Detection-RS-ResourceConfig, with a set ^{q 0} of periodic channel state information reference signal (CSI-RS) resource configuration indexes; or a configuration of the UE, by higher layer parameter Candidate-Beam-RS-List, with at least one of a set ^{q 1} f CSI-RS resource configuration indexes or synchronization signal physical broadcast channel (SS/PBCH) block.

[0148] Example 11 includes the subject matter of Example 10, and optionally, wherein, the radio link quality measurements are based on CSI-RS or on synchronization signal block (SSB) that is spatially quasi co-located (QCLed) with the DM-RS for the PDCCH.

[0149] Example 12 includes the subject matter of Example 1, and optionally, wherein, in a radio resource control (RRC) connected mode of the UE, the processing circuitry is to apply layer 3 filtering of measurement results on multiple beams of a serving cell corresponding to the gNodeB before using the measurement results for measurement reporting.

[0150] Example 13 includes the subject matter of Example 12, and optionally, wherein the processing circuitry is to implement the measurement reporting on a per beam basis using respective beam identifiers.

[0151] Example 14 includes the subject matter of Example 12, and optionally, wherein the layer 3 filtering may include filtering at the physical layer (PHY) level to allow a determination of beam quality, and filtering at a RRC level to allow a determination of cell quality from the multiple beams.

[0152] Example 15 includes the subject matter of Example 1, and optionally, wherein the processing circuitry is to monitor a set of physical downlink control channel PDCCH candidates (PDCCH search spaces) in one or more control resource sets (CORESETS) on an active DL bandwidth part (BW) on each activated serving cell according to corresponding search spaces, wherein monitoring includes decoding each PDCCH candidate according to monitored downlink control information (DCI) formats.

[0153] Example 16 includes the subject matter of Example 15, and optionally, wherein the PDCCH search space is a common search space (CSS) or a UE-specific search space (USS or UE- SS).

[0154] Example 17 includes the subject matter of Example 16, and optionally, wherein the PDCCH search space is a CSS of Type0-PDCCH CSS, and wherein a number of PDCCH candidates is based on control channel element (CCE) aggregation levels (ALs) (CCE ALs) corresponding to a control channel of the PDCCH.

[0155] Example 18 includes the subject matter of Example 17, and optionally, wherein the number of PDCCH candidates is 1 for a CCE AL of 4, 2 for a CCE AL of 8, and 1 for a CCE AL of 16.

[0156] Example 19 includes the subject matter of Example 15, and optionally, wherein at least one of a maximum number of PDCCH candidates per slot and per serving cell, or a maximum number of non-overlapped control channel elements per slot and per serving cell, is based on a subcarrier spacing value 2 ´ 15 kHz, where m is an integer.

[0157] Example 20 includes the subject matter of any one of Examples 1-19, and optionally, further including a front end module coupled to the RF interface.

[0158] Example 21 includes the subject matter of Example 20, and optionally, further including one or more antennas coupled to the front end module, the antennas to transmit UL communications and to receive DL communications.

[0159] Example 22 includes a method to be performed at a device of a New Radio (NR) User Equipment (UE), the method including: encoding for communication with a NR evolved Node B (gNodeB) signals on multiple beams; and determining a timing for an uplink (UL) communication with the gNodeB based on a pair of transmit and receive beams respectively to and from the gNodeB.

[0160] Example 23 includes the subject matter of Example 22, and optionally, wherein the timing for the UL communication is based on a timing for a downlink (DL) communication corresponding to a time when a detected path of a corresponding DL frame is received from the gNodeB by the UE, minus a value equal to (^ _TA + ^ _{TA offset} ) × ^ _^ wherein ^ _^ corresponds to a time unit, and ^ _{TA offset} is given by: for full division duplex (FDD) in a FR1 frequency band for the UL communication, a value of 0; for time division duplex (TDD) in a FR1 frequency band for the UL communication, a value of 39936 or 25600; and for a FR2 frequency band for the UL communication, a value of 13792.

[0161] Example 24 includes the subject matter of Example 23, and optionally, wherein the method includes adjusting the timing for the UL communication such that a minimum aggregate adjustment rate is T _p per second, where T _p is equal to [5.5]*64*T _c when a subcarrier spacing (SCS) for the UL communication is 15 KHz, 30 KHz or 60 KHz in a FR1 frequency band, and where Tp is equal to [2.5]*64*Tc when the SCS for the UL communication is 60 KHz or 120 KHz in a FR2 frequency band.

[0162] Example 25 includes the subject matter of Example 22, and optionally, wherein the pair of transmit and receive beams include a transmit beam determined by the gNodeB, and a receive beam determined by the UE.

[0163] Example 26 includes the subject matter of Example 22, and optionally, wherein: the timing for the UL communication is based on a timing for a downlink (DL) communication after beam switching by the gNodeB, the timing corresponding to a time when a detected path of a corresponding DL frame is received from the gNodeB by the UE after beam switching, minus a value equal to (^ _TA + ^ _{TA offset} ) × ^ _^ where ^ _^ corresponds to a time unit; and the method further includes: determining that the timing for the DL communication after beam switching has changed as compared with a DL communication from the gNodeB before beam switching within ±D, where D = ½ cyclic prefix (CP) length); and determining the timing for the UL communication based on a timing adjustment of ±D as compared with a timing for an UL communication that corresponds to the DL communication from the gNodeB before beam switching.

[0164] Example 27 includes the subject matter of Example 26, and optionally, wherein the method includes: determining that the timing for the DL communication after beam switching has changed as compared with a DL communication from the gNodeB before beam switching more than ±D; and initiating a random access procedure to obtain a new timing for DL communication.

[0165] Example 28 includes the subject matter of Example 26, and optionally, wherein D is based on a subcarrier spacing for the UL communication or the DL communication. [0166] Example 29 includes the subject matter of Example 22, and optionally, wherein the method includes causing the UE to be configured with a list of up to M transmission configuration state (TCI-State) configurations within a higher layer parameter PDSCH-Config to decode a physical downlink shared channel (PDSCH) according to a detected physical downlink control channel (PDCCH) with a downlink control information (DCI), where M is based on a capability of the UE, and where each TCI-State contains parameters for configuring a quasi co- location relationship between one or two downlink reference signals and demodulation reference signal (DM-RS) ports of the PDSCH.

[0167] Example 30 includes the subject matter of Example 29, and optionally, wherein the method includes: determining that a channel state information reference signal (CSI-RS) resource in a non-zero power (NZP) resource set; and determining, for at least one of the CSI- RS resource, DM-RS ports of a PDCCH ,or DM-RS ports of a PDSCH, a quasi-co-location type indication of the TCI-State based on a higher layer parameter configuration of the CSI-RS resource.

[0168] Example 31 includes the subject matter of Example 29, and optionally, wherein the method includes encoding for transmission to the gNodeB a beam failure recovery request based on radio link quality measurements on a serving cell of the gNodeB, the radio link quality measurements being based on at least one of: a configuration of the UE, by higher layer parameter Beam-Failure-Detection-RS-ResourceConfig, with a set ^{q 0} of periodic channel state information reference signal (CSI-RS) resource configuration indexes; or a configuration of the UE, by higher layer parameter Candidate-Beam-RS-List, with at least one of a set ^{q 1} of CSI-RS resource configuration indexes or synchronization signal physical broadcast channel (SS/PBCH) block.

[0169] Example 32 includes the subject matter of Example 31, and optionally, wherein, the radio link quality measurements are based on CSI-RS or on synchronization signal block (SSB) that is spatially quasi co-located (QCLed) with the DM-RS for the PDCCH.

[0170] Example 33 includes the subject matter of Example 22, and optionally, wherein, in a radio resource control (RRC) connected mode of the UE, the method includes applying layer 3 filtering of measurement results on multiple beams of a serving cell corresponding to the gNodeB before using the measurement results for measurement reporting. [0171] Example 34 includes the subject matter of Example 33, and optionally, wherein the method includes implementing the measurement reporting on a per beam basis using respective beam identifiers.

[0172] Example 35 includes the subject matter of Example 33, and optionally, wherein the layer 3 filtering may include filtering at the physical layer (PHY) level to allow a determination of beam quality, and filtering at a RRC level to allow a determination of cell quality from the multiple beams.

[0173] Example 36 includes the subject matter of Example 22, and optionally, wherein the method includes monitoring a set of physical downlink control channel PDCCH candidates (PDCCH search spaces) in one or more control resource sets (CORESETS) on an active DL bandwidth part (BW) on each activated serving cell according to corresponding search spaces, wherein monitoring includes decoding each PDCCH candidate according to monitored downlink control information (DCI) formats.

[0174] Example 37 includes the subject matter of Example 36, and optionally, wherein the PDCCH search space is a common search space (CSS) or a UE-specific search space (USS or UE- SS).

[0175] Example 38 includes the subject matter of Example 37, and optionally, wherein the PDCCH search space is a CSS of Type0-PDCCH CSS, and wherein a number of PDCCH candidates is based on control channel element (CCE) aggregation levels (ALs) (CCE ALs) corresponding to a control channel of the PDCCH.

[0176] Example 39 includes the subject matter of Example 38, and optionally, wherein the number of PDCCH candidates is 1 for a CCE AL of 4, 2 for a CCE AL of 8, and 1 for a CCE AL of 16.

[0177] Example 40 includes the subject matter of Example 36, and optionally, wherein at least one of a maximum number of PDCCH candidates per slot and per serving cell, or a maximum number of non-overlapped control channel elements per slot and per serving cell, is based on a subcarrier spacing value 2 ´ 15 kHz, where m is an integer.

[0178] Example 41 includes a machine-readable medium including code which, when executed, is to cause a machine to perform the method of any one of claims 22-40.

[0179] Example 42 includes an apparatus comprising means for causing a wireless communication device to perform the method of any one of claims 22-40. [0180] 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.